| 2 | Approval of Agenda | |
|---|---|---|
| R1-2200850 | Draft Agenda of RAN1#108-e meeting | RAN1 Chair |
| R1-2200852 | RAN1#108-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2200853 | Additional Guidelines for RAN1#108-e-Meeting Management | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2200851 | Report of RAN1#107b-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2200854 | LS on TRS-based SCell activation details | RAN2, OPPO |
| R1-2200855 | Reply LS on R17 NR MG enhancements – Concurrent MG | RAN2, MediaTek |
| R1-2200856 | Response LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | RAN2, Intel |
| R1-2200857 | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN2, Qualcomm, Datang Mobile |
| R1-2200858 | Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | RAN2, Nokia |
| R1-2200859 | LS on MPE information signalling | RAN2, Nokia |
| R1-2200860 | LS on NR-U channel information and procedures | RAN3, Samsung |
| R1-2200861 | Reply LS Reply on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | RAN3, ZTE |
| R1-2200862 | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | SA2, CATT |
| R1-2200863 | Reply LS on Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | SA2, Huawei |
| R1-2200864 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2200865 | LS on UL-MIMO coherence for Rel-17 Tx switching | RAN4, China Telecom |
| R1-2200866 | LS on PEMAX for NR-V2X | RAN4, Huawei, CATT |
| R1-2200867 | LS on NCSG | RAN4, Apple |
| R1-2200868 | LS on NR NTN Neighbor Cell and Satellite Information | RAN4, Qualcomm |
| R1-2200869 | Reply LS on NTN UL time and frequency synchronization requirements | RAN4, Xiaomi |
| R1-2200870 | Reply LS on combination of open and closed loop TA control in NTN | RAN4, Qualcomm |
| R1-2200871 | LS on interruption for PUCCH SCell activation in invalid TA case | RAN4, MediaTek, CATT |
| R1-2200872 | LS on UE capability for supporting single DCI transmission schemes for multi-TRP | RAN4, Apple |
| R1-2200873 | LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN5, Huawei |
| R1-2200874 | Reply LS on initial access for 60 GHz | RAN2, Intel |
| R1-2200875 | LS on NTN-specific SIB | RAN2, Huawei |
| R1-2200876 | Reply LS on the use of NCD-SSB or CSI-RS in DL BWPs for RedCap UEs | RAN2, Ericsson |
| R1-2200877 | LS on RSRP measurement before Msg1 or MsgA retransmission | RAN2, Ericsson |
| R1-2200878 | Response LS on the reporting of the Tx TEG association information | RAN2, CATT |
| R1-2200879 | LS on Stage 2 description for Coverage Enhancements | RAN2, China Telecom |
| R1-2200880 | LS to RAN1 on Inter-UE coordination | RAN2, Intel |
| R1-2200881 | Reply LS on the L1 aspects of small data transmission | RAN2, ZTE |
| R1-2200882 | LS on MBS issues | RAN2, Huawei |
| R1-2200883 | Reply LS on NR NTN Neighbor Cell and Satellite Information | RAN2, Qualcomm |
| R1-2200884 | LS on PDCCH Skipping in RRC_CONNECTED | RAN2, Samsung |
| R1-2200885 | LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | RAN2, Qualcomm |
| R1-2200886 | LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | RAN2, Samsung |
| R1-2200887 | LS on feMIMO RRC parameters | RAN2, Ericsson |
| R1-2200888 | LS on MBS SPS | RAN2, OPPO |
| R1-2200889 | Reply LS on latency improvement for PRS measurement with MG | RAN2, Nokia |
| R1-2200890 | LS on RAN2 agreements for TRS-based Scell activation | RAN2, OPPO |
| R1-2200891 | Reply LS on NR-U channel information and procedures | RAN2, Samsung |
| R1-2200892 | LS on PDC for Time Synchronization | RAN2, ZTE |
| R1-2200893 | LS to RAN4 on RLM/BFD relaxation for ePowSav | RAN2, vivo |
| R1-2200894 | LS for the channelization for up to 71 GHz | RAN4, CATT |
| R1-2200895 | LS on Rel-17 FeMIMO SRS related impact | RAN4, Huawei |
| R1-2200896 | LS on the PL-RS configuration of PUCCH SCell to be activated | RAN4, Apple |
| R1-2200897 | Reply LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71 GHz | RAN4, vivo |
| R1-2200898 | Reply LS on use of NCD-SSB for RedCap UE | RAN4, ZTE |
| R1-2200899 | Reply LS on lower Rx beam sweeping factor for latency improvement | RAN4, CATT |
| R1-2200900 | LS on SRS for multi-RTT positioning | RAN4, Huawei |
| R1-2200901 | LS reply on UL SRS-RSRPP definition | RAN4, Ericsson |
| R1-2200902 | Reply LS on reporting of the Tx TEG association information | RAN4, Huawei |
| R1-2200903 | LS on the applicability of PRS processing window in RRC_INACTIVE state | RAN4, CATT |
| R1-2200904 | Reply LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE | RAN4, vivo |
| R1-2200905 | Reply LS on reporting and definition of DL PRS path RSRP | RAN4, Nokia Bell Labs |
| R1-2200906 | LS on range of power control parameters for eIAB | RAN4, Samsung |
| R1-2200907 | LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | RAN4, Samsung |
| R1-2200908 | Reply LS on Maximum duration for DMRS bundling | RAN4, Qualcomm |
| R1-2200909 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2200910 | Further reply LS on R17 NR MG enhancements – Concurrent MG | RAN4, MediaTek inc. |
| R1-2200911 | LS on R17 MG enhancement - NCSG | RAN4, Apple |
| R1-2200912 | LS on DRX cycle used in PRS measurement in RRC_INACTIVE state | RAN4, Qualcomm |
| R1-2200913 | LS on signalings for enabling RLM and BFD relaxation in R17 UE power saving | RAN4, vivo |
| R1-2201009 | Draft reply LS on reporting of the Tx TEG association information | Huawei |
| R1-2201010 | Draft reply LS on SRS for multi-RTT positioning | Huawei |
| R1-2201039 | Draft reply LS on TRS-based Scell activation | vivo |
| R1-2201040 | Draft reply LS on PEMAX for NR-V2X | vivo |
| R1-2201041 | Draft reply LS on MPE information signaling | vivo |
| R1-2201042 | Draft Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | vivo |
| R1-2201043 | Draft reply LS UE capability for supporting single DCI transmission schemes for multi-TRP | vivo |
| R1-2201044 | Draft reply LS on Rel-17 FeMIMO SRS related impact | vivo |
| R1-2201045 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | vivo |
| R1-2201046 | Draft reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance | vivo |
| R1-2201047 | Discussion on PDCCH skipping | vivo |
| R1-2201048 | Draft LS reply on PDCCH skipping | vivo |
| R1-2201049 | Draft LS reply on Enhanced TCI state indication for UE-specific PDCCH MAC CE | vivo |
| R1-2201050 | Draft LS reply on feMIMO RRC parameters | vivo |
| R1-2201051 | Draft LS reply on UL BWP with PRACH resources only for RACH with Msg3 repetition | vivo |
| R1-2201052 | Draft reply LS on the applicability of PRS processing window in RRC_INACTIVE state | vivo |
| R1-2201053 | Draft reply LS on SRS for multi-RTT positioning | vivo |
| R1-2201054 | Draft reply LS on reporting of the Tx TEG association information | vivo |
| R1-2201055 | Draft reply LS on MBS SPS | vivo |
| R1-2201056 | Draft reply LS on MBS issues | vivo |
| R1-2201057 | Draft reply LS on NRU channel information and procedures | vivo |
| R1-2201058 | Draft reply LS on the L1 aspects of small data transmission | vivo |
| R1-2201059 | Discussion on RAN4 LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | vivo |
| R1-2201060 | Draft reply LS on the PL-RS configuration of PUCCH SCell to be activated | vivo |
| R1-2201061 | Draft reply LS on interruption for PUCCH SCell activation in invalid TA case | vivo |
| R1-2201141 | Discussion on PDCCH skipping in RRC_CONNECTED | ZTE, Sanechips |
| R1-2201142 | Draft reply LS on PDCCH skipping in RRC_CONNECTED | ZTE, Sanechips |
| R1-2201148 | [Draft] Reply LS on TRS-based SCell activation details | ZTE |
| R1-2201149 | [Draft] Reply LS on interruption for PUCCH SCell activation in invalid TA case | ZTE |
| R1-2201150 | [Draft] Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | ZTE |
| R1-2201151 | [Draft] Reply LS on MBS issues | ZTE |
| R1-2201152 | [Draft] Reply LS on MBS SPS | ZTE |
| R1-2201153 | [Draft] Reply LS on RAN2 agreements for TRS-based Scell activation | ZTE |
| R1-2201155 | [Draft] Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | ZTE |
| R1-2201156 | Discussion on CORESET#0 impact of CBW narrower than 40MHz of n79 | ZTE |
| R1-2201157 | [Draft] Reply LS on Stage 2 description for Coverage Enhancements | ZTE |
| R1-2201158 | [Draft] Reply LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | ZTE |
| R1-2201159 | [Draft] Reply LS on the PL-RS configuration of PUCCH SCell to be activated | ZTE |
| R1-2201183 | Draft Reply LS to RAN2 on NTN-specific SIB | THALES |
| R1-2201202 | Draft reply LS on MPE information signalling | ZTE |
| R1-2201203 | Draft reply LS to RAN3 on TCI State Update for L1/L2-Centric Inter-Cell Mobility | ZTE |
| R1-2201204 | Draft reply LS on feMIMO RRC parameters | ZTE |
| R1-2201205 | Draft reply LS to RAN2 on Positioning Reference Units (PRUs) | ZTE |
| R1-2201206 | Draft reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP | ZTE |
| R1-2201207 | Draft reply LS on the reporting of the Tx TEG association information | ZTE |
| R1-2201208 | Draft reply LS on enhanced TCI state indication for UE-specific PDCCH MAC CE | ZTE |
| R1-2201209 | Draft reply LS on lower Rx beam sweeping factor for latency improvement | ZTE |
| R1-2201210 | Draft reply LS on SRS for multi-RTT positioning | ZTE |
| R1-2201211 | Draft reply LS on the applicability of PRS processing window in RRC_INACTIVE state | ZTE |
| R1-2201212 | Draft reply LS on reporting and definition of DL PRS path RSRP | ZTE |
| R1-2201213 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Huawei |
| R1-2201214 | Draft reply LS on NTN-specific SIB | Huawei |
| R1-2201232 | Discussion on LS on UE capability for supporting single DCI transmission schemes for multi-TRP | OPPO |
| R1-2201233 | Discussion on LS on configuration of p-MaxEUTRA and p-NR-FR1 | OPPO |
| R1-2201234 | Discussion on LS on MPE information signalling | OPPO |
| R1-2201235 | Discussion on LS on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | OPPO |
| R1-2201236 | Discussion on LS on enhanced TCI state indication for UE-specific PDCCH MAC CE | OPPO |
| R1-2201237 | Discussion on LS on feMIMO RRC parameters | OPPO |
| R1-2201246 | Discussion on "response LS on Positioning Reference Units (PRUs) for enhancing positioning performance" | OPPO |
| R1-2201247 | Discussion on "Response LS on the reporting of the Tx TEG association information" | OPPO |
| R1-2201248 | Discussion on "LS on SRS for multi-RTT positioning" | OPPO |
| R1-2201249 | Discussion on "LS on the applicability of PRS processing window in RRC_INACTIVE state" | OPPO |
| R1-2201250 | Discussion on LS about PEMAX for NR-V2X | OPPO |
| R1-2201251 | Draft Reply LS on PEMAX for NR-V2X | OPPO |
| R1-2201261 | Discussion on the LS from RAN2 of MBS SPS | OPPO |
| R1-2201262 | Draft LS reply on MBS SPS | OPPO |
| R1-2201263 | Discussion on the LS from RAN2 of MBS CFR for MCCH/MTCH | OPPO |
| R1-2201264 | Draft LS reply on MBS CFR for MCCH/MTCH | OPPO |
| R1-2201274 | Discussion on reply LS for NR NTN Neighbor Cell and Satellite Information | OPPO |
| R1-2201300 | Discussion on RAN2 LS on fast SCell activation | OPPO |
| R1-2201305 | [Draft] Reply LS on P_EMAX for NR-V2X | CATT, GOHIGH |
| R1-2201306 | Draft reply LS on feMIMO RRC parameters | CATT |
| R1-2201307 | Discussion on feMIMO RRC parameters | CATT |
| R1-2201308 | Draft reply LS on interruption for PUCCH SCell activation in invalid TA case | CATT |
| R1-2201309 | Discussion on SRS for multi-RTT positioning | CATT |
| R1-2201310 | Draft reply LS on SRS for multi-RTT positioning | CATT |
| R1-2201311 | Discussion on the applicability of PRS processing window in RRC_INACTIVE state | CATT |
| R1-2201312 | Draft reply LS on the applicability of PRS processing window in RRC_INACTIVE state | CATT |
| R1-2201313 | Discussion on reporting and definition of DL PRS path RSRP | CATT |
| R1-2201314 | Draft reply LS on reporting and definition of DL PRS path RSRP | CATT |
| R1-2201315 | Discussion on PRU for enhancing positioning performance | CATT |
| R1-2201316 | Draft reply LS on the PRU for enhancing positioning performance | CATT |
| R1-2201317 | Discussion on the reporting of the Tx TEG association information | CATT |
| R1-2201318 | Draft reply LS on the reporting of the Tx TEG association information | CATT |
| R1-2201320 | Discussion on LS from RAN2 on Inter-UE coordination | CATT, GOHIGH |
| R1-2201321 | Discussion of RAN2 LS on PDCCH skipping in RRC_CONNECTED | CATT |
| R1-2201322 | Draft reply LS on PDCCH skipping in RRC_CONNECTED | CATT |
| R1-2201323 | Discussion on Reply LS on MBS issue of SPS | CATT |
| R1-2201378 | Draft reply LS on the L1 aspects of small data transmission | CATT |
| R1-2201432 | Discussion on CORESET#0 impact of CBW narrower than 40MHz of n79 | FUTUREWEI |
| R1-2201451 | [Draft] Reply LS on MPE information signalling | Lenovo, Motorola Mobility |
| R1-2201452 | [Draft] Reply LS TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | Lenovo, Motorola Mobility |
| R1-2201453 | [Draft] Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP | Lenovo, Motorola Mobility |
| R1-2201454 | Discussion on RAN2 LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Lenovo, Motorola Mobility |
| R1-2201455 | [Draft] Reply LS on feMIMO RRC parameters | Lenovo, Motorola Mobility |
| R1-2201460 | About reply LS on range of power control parameters for eIAB | ZTE, Sanechips |
| R1-2201523 | Draft reply LS on the PL-RS configuration of PUCCH SCell to be activated | Samsung |
| R1-2201524 | Draft reply LS on range of power control parameters for eIAB | Samsung |
| R1-2201529 | [Draft] Reply LS on Rel-17 FeMIMO SRS related impact | Lenovo, Motorola Mobility |
| R1-2201563 | Draft reply LS on MPE information signalling | LG Electronics |
| R1-2201564 | Draft reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP | LG Electronics |
| R1-2201565 | Draft reply LS on feMIMO RRC parameters | LG Electronics |
| R1-2201566 | Draft reply LS on Rel-17 FeMIMO SRS related impact | LG Electronics |
| R1-2201610 | Discussion on range of power control parameters for eIAB | ETRI |
| R1-2201619 | Discussion on LS related to enhanced TCI state indication for UE-specific PDCCH MAC CE | Ericsson |
| R1-2201620 | Discussion on LS related to CORESET#0 impact of CBW narrower than 40MHz of n79 | Ericsson |
| R1-2201628 | Draft reply LS on feMIMO RRC parameters | Ericsson |
| R1-2201629 | Discussion related to LS on feMIMO RRC parameters | Ericsson |
| R1-2201640 | Discussion on RAN2 LS on NR NTN Neighbor Cell and Satellite Information | Panasonic Corporation |
| R1-2201675 | Discussion on Stage 2 description for Coverage Enhancements | Intel Corporation |
| R1-2201676 | Discussion on LS reply on RRC parameters for feMIMO | Intel Corporation |
| R1-2201677 | Discussion on LS CORESET#0 impact of CBW narrower than 40MHz of n79 | Intel Corporation |
| R1-2201678 | [Draft] Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | Intel Corporation |
| R1-2201679 | Discussion on reply LS for separate BWP for RedCap UEs supporting SDT | Intel Corporation |
| R1-2201742 | Discussion on LS from RAN3 on NR-U channel information and procedures | Ericsson |
| R1-2201743 | Draft Reply LS to RAN3 on NR-U channel information and procedures | Ericsson |
| R1-2201747 | Draft reply LS on Enhanced TCI State Indication for UE specific PDCCH MAC CE | Apple |
| R1-2201748 | Draft reply LS on FeMIMO RRC Parameters | Apple |
| R1-2201749 | Draft reply LS on MPE Information Signaling | Apple |
| R1-2201750 | Draft reply LS on TCI Update for L1/L2 Centric Inter-Cell Mobility | Apple |
| R1-2201751 | Draft reply LS on UE Capability for supporting single DCI transmission scheme for multi-TRP | Apple |
| R1-2201752 | Discussion on RAN4 LS on PEMAX for NR-V2X | Apple |
| R1-2201753 | Discussion on RAN2 LS on Inter-UE Coordination | Apple |
| R1-2201754 | Discussion on RAN2 LS on NTN-specific SIB | Apple |
| R1-2201813 | Discussion on LS on MBS issues | Spreadtrum Communications |
| R1-2201814 | Discussion on LS on MBS SPS | Spreadtrum Communications |
| R1-2201822 | Discussion on Positioning Reference Units (PRUs) for enhancing positioning performance | InterDigital, Inc. |
| R1-2201828 | Discussion on RAN2 LS on PDCCH skipping in RRC_CONNECTED | CMCC |
| R1-2201829 | Discussion on RAN2 LS on MBS SPS | CMCC |
| R1-2201830 | Draft reply LS on MBS SPS | CMCC |
| R1-2201831 | Discussion on RAN2 LS on MBS issues | CMCC |
| R1-2201832 | Draft reply LS on MBS issues | CMCC |
| R1-2201833 | Discussion on RAN2 LS on feMIMO RRC parameters | CMCC |
| R1-2201834 | Discussion on RAN2 LS on enhanced TCI state indication for UE-specific PDCCH MAC CE | CMCC |
| R1-2201835 | Discussion on RAN2 LS on MPE information signaling | CMCC |
| R1-2201836 | Discussion on RAN3 LS on TCI state update for L1L2-centric inter-Cell mobility | CMCC |
| R1-2201837 | Discussion on RAN4 LS on Rel-17 FeMIMO SRS related impact | CMCC |
| R1-2201838 | Discussion on RAN2 LS on Positioning Reference Units (PRUs) for enhancing positioning performance | CMCC |
| R1-2201839 | Discussion on RAN4 LS on the applicability of PRS processing window in RRC_INACTIVE state | CMCC |
| R1-2201840 | Discussion on RAN2 LS on NTN-specific SIB | CMCC |
| R1-2201841 | Discussion on RAN4 LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | CMCC |
| R1-2201842 | Discussion on RAN2 LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | CMCC |
| R1-2201843 | Discussion on RAN2 LS on Stage 2 description for Coverage Enhancements | CMCC |
| R1-2201927 | Discussion on RAN2 LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | Xiaomi |
| R1-2201928 | Discussion on RAN2 LS on Stage 2 description for Coverage Enhancements | Xiaomi |
| R1-2201972 | Draft Reply LS on NR-U channel information and procedures | Samsung |
| R1-2201973 | Discussion on CORESET#0 impact of CBW narrower than 40MHz of n79 | Samsung |
| R1-2201974 | Draft Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | Samsung |
| R1-2201975 | Draft Reply to RAN2 LS on PDCCH Skipping in RRC_CONNECTED | Samsung |
| R1-2201976 | Draft Reply LS on MPE information signalling | Samsung |
| R1-2201977 | Draft Reply LS on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | Samsung |
| R1-2201978 | Draft Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP | Samsung |
| R1-2201979 | Draft Reply LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Samsung |
| R1-2201980 | Draft Reply LS on feMIMO RRC parameters | Samsung |
| R1-2201981 | Draft Reply LS on Rel-17 FeMIMO SRS related impact | Samsung |
| R1-2201982 | Draft Reply LS to RAN4 on PEMAX for NR-V2X | Samsung |
| R1-2201983 | Draft Reply LS to RAN1 on Inter-UE coordination | Samsung |
| R1-2201984 | Discussion on reply LS for configuration of p-MaxEUTRA and p-NR-FR1 | Samsung |
| R1-2202049 | [draft] Reply LS on interruption for PUCCH SCell activation in invalid TA case | MediaTek Inc. |
| R1-2202056 | Discussion on RAN2 LS on feMIMO RRC parameters (MultiBeam) | MediaTek Inc. |
| R1-2202060 | Discussion on RAN4 LS on CORESET#0 configuration in n79 | MediaTek Inc. |
| R1-2202066 | Discussion on RAN2 LS on PDCCH Skipping in RRC_CONNECTED | MediaTek Inc. |
| R1-2202077 | Discussion on RAN2 LS on MBS CFR design for MCCH and MTCH | MediaTek Inc. |
| R1-2202078 | Discussion on RAN2 LS on MBS SPS | MediaTek Inc. |
| R1-2202095 | Draft Reply LS to RAN4 on UE capability for supporting single DCI transmission schemes for multi-TRP | Qualcomm Incorporated |
| R1-2202096 | Draft Reply LS to RAN2 on feMIMO RRC parameters | Qualcomm Incorporated |
| R1-2202097 | [Draft] Reply to RAN4 LS on PEMAX for NR-V2X | Qualcomm Incorporated |
| R1-2202098 | Draft Reply LS to RAN2 on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Qualcomm Incorporated |
| R1-2202099 | Draft Reply LS to RAN4 on Rel-17 FeMIMO SRS related impact | Qualcomm Incorporated |
| R1-2202100 | Draft Reply LS on NR NTN Neighbor Cell and Satellite Information | Qualcomm Incorporated |
| R1-2202101 | Draft Reply LS to RAN2 on NTN-specific SIB | Qualcomm Incorporated |
| R1-2202102 | Draft Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Qualcomm Incorporated |
| R1-2202103 | Draft Reply LS on interruption for PUCCH SCell activation in invalid TA case | Qualcomm Incorporated |
| R1-2202104 | Draft Reply to RAN4 LS on SRS for multi-RTT positioning | Qualcomm Incorporated |
| R1-2202105 | Draft Reply to RAN4 LS on reporting and definition of DL PRS path RSRP | Qualcomm Incorporated |
| R1-2202106 | Draft Reply to RAN2 LS on the reporting of the Tx TEG association information | Qualcomm Incorporated |
| R1-2202107 | Draft Reply LS on CORESET#0 Impact of CBW Narrower than 40 MHz of n79 | Qualcomm Incorporated |
| R1-2202108 | Draft Reply to RAN2 LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Qualcomm Incorporated |
| R1-2202109 | Draft Reply to RAN4 LS on the applicability of PRS processing window in RRC_INACTIVE state | Qualcomm Incorporated |
| R1-2202204 | [Draft] Reply LS on NTN-specific SIB | ZTE |
| R1-2202205 | Discussion on LS on neighbor cell and satellite information | ZTE |
| R1-2202214 | Discussion on RAN4 LS on PEMAX for NR-V2X | Xiaomi |
| R1-2202215 | Discussion on PDCCH skipping | Ericsson |
| R1-2202251 | Discussion on LS on PEMAX for NR-V2X | LG Electronics |
| R1-2202260 | [Draft] LS on PEMAX for NR-V2X | Ericsson |
| R1-2202261 | Discussion on RAN4 LS on PEMAX for NR-V2X | Ericsson |
| R1-2202268 | On interruption for PUCCH SCell activation in invalid TA case | Nokia, Nokia Shanghai Bell |
| R1-2202269 | On configuration of p-MaxEUTRA and p-NR-FR1 | Nokia, Nokia Shanghai Bell |
| R1-2202274 | Discussion on RAN2 LS to RAN1 on inter-UE coordination | Ericsson |
| R1-2202288 | Discussion on RAN2 LS on NR NTN Neighbor Cell and Satellite Information | LG Electronics |
| R1-2202289 | Discussion on RAN2 LS on NTN-specific SIB | LG Electronics |
| R1-2202296 | Draft Reply LS on Positioning Reference Units (PRUs) for enhancing positioning | LG Electronics |
| R1-2202297 | Draft Reply LS on the reporting of the Tx TEG association information | LG Electronics |
| R1-2202298 | Discussion on the applicability of PRS processing window in RRC_INACTIVE state | LG Electronics |
| R1-2202304 | Draft reply LS on Msg3 repetition in coverage enhancement | LG Electronics |
| R1-2202307 | Draft reply LS on range of power control parameters for eIAB | LG Electronics |
| R1-2202308 | Draft LS reply on Rel-17 FeMIMO SRS related impact | Nokia, Nokia Shanghai Bell |
| R1-2202309 | Draft LS reply on feMIMO RRC parameters | Nokia, Nokia Shanghai Bell |
| R1-2202310 | Draft LS reply on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Nokia, Nokia Shanghai Bell |
| R1-2202311 | Draft LS reply on UE capability for supporting single DCI transmission schemes for multi-TRP | Nokia, Nokia Shanghai Bell |
| R1-2202312 | Draft LS reply on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | Nokia, Nokia Shanghai Bell |
| R1-2202313 | Draft LS reply on MPE information signalling | Nokia, Nokia Shanghai Bell |
| R1-2202323 | Draft reply to LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Ericsson |
| R1-2202324 | Draft reply to LS on MPE information signalling | Ericsson |
| R1-2202325 | On CORESET#0 configuration for n79 with CBW narrower than 40MHz | Nokia, Nokia Shanghai Bell |
| R1-2202326 | Draft reply to LS on UE capability for supporting single DCI transmission schemes for multi-TRP | Ericsson |
| R1-2202327 | Draft reply to Response LS on the reporting of the Tx TEG association information | Ericsson |
| R1-2202332 | Discussion on RAN3 LS for NR-U channel information and procedures | LG Electronics |
| R1-2202333 | Discussion on LS on PDCCH Skipping in RRC_CONNECTED | LG Electronics |
| R1-2202358 | Discussion on RAN4 LS on PEMAX for NR V2X | Nokia, Nokia Shanghai Bell |
| R1-2202375 | [Draft] Reply LS on interruption for PUCCH SCell activation in invalid TA case | Ericsson |
| R1-2202379 | About the LS on PEMAX for NR-V2X | ZTE, Sanechips |
| R1-2202380 | About LS on Inter-UE coordination from RAN2 | ZTE, Sanechips |
| R1-2202400 | views on LS on SRS for multi-RTT positioning | Ericsson |
| R1-2202401 | views on LS on the applicability of PRS processing window in RRC_INACTIVE state | Ericsson |
| R1-2202406 | Regarding RAN4’s LS on range of power control parameters for eIAB | Ericsson |
| R1-2202414 | Draft Reply LS on UL BWP with PRACH Resources Only for RACH with Msg3 Repetition | Ericsson |
| R1-2202415 | Draft Reply LS on Stage 2 Description for Coverage Enhancements | Ericsson |
| R1-2202428 | Discussion on RAN2 LS on PDCCH Skipping in RRC_CONNECTED | Huawei, HiSilicon |
| R1-2202429 | Remaining issues on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R1-2202430 | On PL-RS configuration of PUCCH SCell to be activated | Huawei, HiSilicon |
| R1-2202433 | Discussion on MBS issues asked by RAN2 | Huawei, HiSilicon |
| R1-2202434 | DRAFT LS reply about the MBS issues | Huawei, HiSilicon |
| R1-2202435 | Discussion on the incoming LS about MBS SPS | Huawei, HiSilicon |
| R1-2202436 | DRAFT LS reply about MBS SPS | Huawei, HiSilicon |
| R1-2202441 | Discussion on LS on PEMAX for NR-V2X | Huawei, HiSilicon |
| R1-2202445 | Discussion on LS to RAN1 on Inter-UE coordination | Huawei, HiSilicon |
| R1-2202446 | Discussion on RAN2 LS on SL resource selection with DRX | Huawei, HiSilicon |
| R1-2202452 | Discussion on RAN3 questions of NR-U channel information and procedures | Huawei, HiSilicon |
| R1-2202454 | Discussion on the functionality of PRU | Huawei, HiSilicon |
| R1-2202455 | Discussion on TEG related higher layer parameters | Huawei, HiSilicon |
| R1-2202456 | Discussion on low latency PRS measurement with MG | Huawei, HiSilicon |
| R1-2202457 | Discussion on use of MIMO-SRS for Multi-RTT positioning | Huawei, HiSilicon |
| R1-2202458 | Discussion on definition of UL SRS-RSRP | Huawei, HiSilicon |
| R1-2202459 | Discussion on condition of Tx TEG association change | Huawei, HiSilicon |
| R1-2202460 | Discussion on PRS processing window in RRC_INACTIVE state | Huawei, HiSilicon |
| R1-2202461 | Discussion on DL PRS-RSRPP definition | Huawei, HiSilicon |
| R1-2202462 | Discussion on UL BWP with PRACH resources only for RACH with Msg3 repetition | Huawei, HiSilicon |
| R1-2202463 | Discussion on LS on Stage 2 description for Coverage Enhancements | Huawei, HiSilicon |
| R1-2202464 | Discussion on interruption for PUCCH SCell activation in invalid TA case | Huawei, HiSilicon |
| R1-2202466 | Views on MPE information signalling | Huawei, HiSilicon |
| R1-2202467 | Views on TCI State Update for L1L2-Centric Inter-Cell Mobility | Huawei, HiSilicon |
| R1-2202468 | Views on UE capability for supporting single DCI transmission schemes for multi-TRP | Huawei, HiSilicon |
| R1-2202469 | Views on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Huawei, HiSilicon |
| R1-2202470 | Views on feMIMO RRC parameters | Huawei, HiSilicon |
| R1-2202472 | On CORESET#0 impact of smaller CBW of n79 | Huawei, HiSilicon |
| R1-2202473 | Discussion on NTN-specific SIB | Huawei, HiSilicon |
| R1-2202474 | Discussion on NTN Neighbor Cell measurement and Satellite Information | Huawei, HiSilicon |
| R1-2202475 | Discussion on the range of power control parameters for eIAB | Huawei, HiSilicon |
| R1-2202481 | Draft Reply to RAN2 LS on PDCCH skipping in RRC_CONNECTED | Qualcomm Incorporated |
| R1-2202506 | Incoming LS handling for RAN1#108-e | RAN1 Chair |
| R1-2202588 | Reply LS on Rel-17 RAN1 and RAN4 feature list | RAN2, Intel |
| R1-2202598 | [108-e-AI5-LS-02] Email discussion for incoming LS on PUCCH SCell activation in invalid TA case | Moderator (MediaTek Inc.) |
| R1-2202599 | Reply LS on interruption for PUCCH SCell activation in invalid TA case | RAN1, MediaTek |
| R1-2202620 | LS to RAN1 on positioning issues needing further input | RAN2, Intel |
| R1-2202694 | Draft Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | Samsung |
| R1-2202695 | Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | RAN1, Samsung |
| R1-2202716 | Summary of email discussion for incoming LS on CORESET#0 impact of CBW narrower than 40MHz of n79 | Moderator (Samsung) |
| R1-2202727 | LS on MBS broadcast reception on SCell | RAN2, Huawei |
| R1-2202756 | LS on further questions on feMIMO RRC parameters | RAN2, Ericsson |
| R1-2202768 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Moderator (Huawei) |
| R1-2202769 | Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN1, Huawei |
| R1-2202777 | [Draft] Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Moderator (Huawei) |
| R1-2202778 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | RAN1, Huawei |
| R1-2202815 | Reply LS on Maximum duration for DMRS bundling | RAN4, Qualcomm Incorporated |
| R1-2202891 | LS on HARQ process for MCCH and Broadcast MTCH(s) | RAN2, Samsung |
| R1-2202901 | Reply LS on PDCCH Blind Detection in CA | RAN2, HiSilicon |
| R1-2202919 | Summary of email discussion [108-e-AI5-LSs-05] on cross PUCCH-group CSI reporting related UE capability | Moderator (Huawei) |
| R1-2202920 | Summary of email discussion [108-e-AI5-LSs-01] on reply LS to R1-2200873 | Moderator (Huawei) |
| R1-2202935 | LS on TP to introduce Rel-17 SL DRX for TR 37.985 | RAN2, Huawei |
| R1-2202938 | Summary of email discussion [108-e-AI5-LSs-01] for incoming LS on PL-RS configuration of PUCCH SCell to be activated | Moderator (Apple) |
| R1-2202982 | Introduction of carrier BW smaller than 40 MHz for n79 | Samsung |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2200973 | Discussion on the remaining issues of UL Tx switching | Huawei, HiSilicon |
| R1-2201062 | Remaining issues on Rel-17 Tx switching enhancements | vivo |
| R1-2201154 | Maintenance of Rel-17 UL Tx switching | ZTE |
| R1-2201238 | Discussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2202110 | Remaining issues of Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2202491 | Discussion on the remaining issues of UL Tx switching | Huawei, HiSilicon |
| R1-2202866 | [108-e-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2202995 | Corrections on UL Tx Switching enhancements | Nokia |
| 5.2 | RAN1 Aspects for NR small data transmissions in INACTIVE state | |
| R1-2200975 | Physical layer aspects of SDT | Huawei, HiSilicon |
| R1-2201063 | Remaining RAN1 related issues for NR small data transmissions in RRC INACTIVE state | vivo |
| R1-2201400 | Discussion on the remaining physical layer issues of small data transmission | ZTE Corporation |
| R1-2201533 | Discussion on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2201651 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2201667 | RAN1 aspects for NR small data transmissions in INACTIVE state | Ericsson |
| R1-2201680 | Remaining issues on physical layer aspects of small data transmission | Intel Corporation |
| R1-2201924 | Discussion on physical layer aspects of small data transmission | xiaomi |
| R1-2201985 | Discussion on PHY Aspects for NR small data transmissions in INACTIVE state | Samsung |
| R1-2202111 | Draft reply LS to RAN2 on the SDT BWP configuration for RedCap UE | Qualcomm Incorporated |
| R1-2202334 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2202411 | Physical layer aspects for small data transmissions | Lenovo |
| R1-2202653 | Summary on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2202654 | Comments collection on RRC parameters for small data transmission | Moderator (ZTE) |
| R1-2202655 | [Draft] Reply LS on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2202656 | Reply LS on the physical layer aspects of small data transmission | RAN1, ZTE |
| R1-2202979 | Corrections to small data transmissions in RRC_INACTIVE state | Ericsson |
| R1-2202987 | Corrections on small data transmission in RRC_INACTIVE state for NR | Samsung |
| R1-2202996 | Corections on NR small data transmissions in INACTIVE state | Nokia |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2200972 | Correction on closed-loop power control for PUSCH repetitions and PUCCH repetitions | Huawei, HiSilicon |
| R1-2200974 | Correction on bit interleaving length for PUSCH transmission | Huawei, HiSilicon |
| R1-2201026 | CR on reference resource bandwidth in sub-band CQI reporting | Nokia, Nokia Shanghai Bell |
| R1-2201027 | SPS PDSCH activation and PUCCH resource selection for the 1st SPS PDSCH | Nokia, Nokia Shanghai Bell |
| R1-2201028 | Draft 38.213 CR on SPS PDSCH activation and PUCCH resource selection for the 1st SPS PDSCH | Nokia, Nokia Shanghai Bell |
| R1-2201029 | Absolute TPC timeline and support of absolute TPC with DCI format 2_2 | Nokia, Nokia Shanghai Bell |
| R1-2201030 | TPC accumulation, interpretation of K_PUSCH(i) | Nokia, Nokia Shanghai Bell |
| R1-2201031 | Correction of K_PUSCH(i) in TPC accumulation | Nokia, Nokia Shanghai Bell |
| R1-2201064 | Maintenance on SRS carrier switching | vivo |
| R1-2201143 | Correction on Type-2 HARQ-ACK codebook for Rel-15 | ZTE |
| R1-2201144 | Draft 38.211 CR on common resource block for CSI-RS for mobility | ZTE |
| R1-2201145 | Draft 38.211 CR on common resource block for CSI-RS for mobility | ZTE |
| R1-2201146 | Discussion on HARQ-ACK multiplexing on PUSCH | ZTE |
| R1-2201147 | Discussion on the determination of the number of part 2 CSI report | ZTE |
| R1-2201319 | Draft CR on Type II CSI feedback | CATT |
| R1-2201324 | Discussion on HARQ-ACK multiplexing in PUSCH without PUCCH | CATT |
| R1-2201383 | Correction on Type-2 HARQ-ACK codebook for Rel-16 | ZTE |
| R1-2201384 | Clarification on power control adjustment for PUSCH/PUCCH repetitions | ZTE |
| R1-2201385 | Clarification on PUCCH resource determination for the first SPS PDSCH | ZTE |
| R1-2201450 | Discussion on SRS carrier switching | ZTE |
| R1-2201649 | Correction to RI bitwidth for non-PMI based CSI feedback | Nokia, Nokia Shanghai Bell |
| R1-2201681 | Discussion on SRS carrier switching | Intel Corporation |
| R1-2201755 | On Remaining Issues for PUSCH UCI Multiplexing without HARQ-ACK PUCCH | Apple |
| R1-2201986 | Discussion on ambiguity for SRS carrier switching. | Samsung |
| R1-2201987 | Correction on notation for power control | Samsung |
| R1-2201988 | UCI multiplexing in PUSCH with repetitions | Samsung |
| R1-2201989 | Draft CR on UCI multiplexing in PUSCH with repetitions | Samsung |
| R1-2202050 | On rate matching pattern of DSS under TDD LTE scenario | MediaTek Inc. |
| R1-2202112 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2202113 | Clarification on PDCCH monitoring for Case 1-2 | Qualcomm Incorporated |
| R1-2202114 | Correction on time-domain resource allocation for Msg.3 PUSCH scheduled by RAR UL grant | Qualcomm Incorporated |
| R1-2202115 | Remaining issues for HARQ-ACK multiplexing on PUSCH without PUCCH | Qualcomm Incorporated |
| R1-2202116 | Clarification on HARQ-ACK PUCCH resource for SPS PDSCH | Qualcomm Incorporated |
| R1-2202117 | Clarification on TPC Command Handling and Applicability of Group Common DCI 2_2 for Absolute TPC commands | Qualcomm Incorporated |
| R1-2202182 | Corrections on frequency hopping procedure for a PUSCH scheduled by RAR UL grant or by DCI format 0_0 with TC-RNTI | Sharp |
| R1-2202183 | Corrections on Intra-slot frequency hopping for PUCCH transmission | Sharp |
| R1-2202184 | Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | Sharp |
| R1-2202368 | Clarification on PUSCH with UCI Only and DMRS Multiplexing | MediaTek Inc. |
| R1-2202374 | HARQ-ACK multiplexing on PUSCH without PUCCH | Ericsson |
| R1-2202431 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | Huawei, HiSilicon |
| R1-2202449 | Correction on effect time of absolute TPC for PUSCH transmissions | Huawei, HiSilicon |
| R1-2202450 | Discussion on the CSI omission | Huawei, HiSilicon |
| R1-2202451 | Clarification on the initial BWP switching | Huawei, HiSilicon |
| R1-2202507 | Rel-15 NR maintenance handling for RAN1#108-e | RAN1 Chair |
| R1-2202597 | [108-e-NR-CRs-11] Issue#14 on rate matching pattern of DSS under TDD LTE scenario | Moderator (MediaTek Inc.) |
| R1-2202615 | Summary of [108-e-NR-CRs-12]: UCI multiplexing in PUSCH with repetitions | Moderator (Samsung) |
| R1-2202624 | Summary of [108-e-NR-CRs-09] | Moderator (Samsung) |
| R1-2202628 | Summary of email discussion [108-e-NR-CRs-15]: Corrections on Intra-slot frequency hopping for PUCCH transmission | Moderator (Sharp) |
| R1-2202631 | [108-e-NR-CRs-10] Issue#2 CR on reference resource bandwidth in sub-band CQI reporting | Moderator (Nokia) |
| R1-2202632 | Summary of [108-e-NR-CRs-13]: Clarification on PDCCH monitoring for Case 1-2 | Moderator (Qualcomm Incorporated) |
| R1-2202633 | Summary of [108-e-NR-CRs-14]: Correction on time-domain resource allocation for Msg.3 PUSCH scheduled by RAR UL grant | Moderator (Qualcomm Incorporated) |
| R1-2202652 | Summary of [108-e-NR-CRs-16] Issue#21 on the initial BWP switching | Moderator (Huawei) |
| R1-2202697 | Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | Moderator (Sharp), Qualcomm Incorporated, CATT |
| R1-2202698 | Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | Moderator (Sharp), Qualcomm Incorporated, CATT |
| R1-2202699 | Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | Moderator (Sharp), Qualcomm Incorporated, CATT |
| R1-2202715 | Feature lead summary#1 on [108-e-NR-CRs-04] Issue#5 Maintenance on SRS carrier switching | Moderator (vivo) |
| R1-2202719 | Summary of [108-e-NR-CRs-08]: Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | Moderator (Sharp) |
| R1-2202748 | Summary of [108-e-NR-CRs-07] Issue#9 Discussion on the determination of the number of part 2 CSI report | Moderator (HiSilicon) |
| R1-2202754 | FL summary [108-e-NR-CRs-05] on common resource block for CSI-RS for mobility | Moderator (ZTE) |
| R1-2202795 | Feature lead summary#2 on [108-e-NR-CRs-04] Issue#5 Maintenance on SRS carrier switching | Moderator (vivo) |
| R1-2202832 | Summary of email discussion [108-e-NR-CRs-01] on bit interleaving length for PUSCH transmission | Moderator (Huawei) |
| R1-2202833 | [108-e-NR-CRs-02] Issue#3 SPS PDSCH activation and PUCCH resource selection for the 1st SPS PDSCH | Moderator (Nokia) |
| R1-2202834 | Summary of [108-e-NR-CRs-03] Issue#4 Absolute TPC timeline and support of absolute TPC with DCI format 2_2 | Moderator (ZTE Corporation) |
| R1-2202835 | Summary for [108-e-NR-CRs-06] Issue #8: Discussion on HARQ-ACK multiplexing on PUSCH | Moderator (Apple) |
| R1-2202898 | Clarification of the SPS PDSCH activation and HARQ-ACK transmission for the 1st SPS PDSCH | Moderator (Nokia) |
| R1-2202899 | Clarification of the SPS PDSCH activation and HARQ-ACK transmission for the 1st SPS PDSCH | Moderator (Nokia) |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2202944 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2202945 | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | Samsung |
| R1-2202999 | Rel-16 editorial corrections for TS 38.214 | Nokia |
| R1-2203000 | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | Nokia |
| R1-2203004 | Rel-16 editorial corrections for TS 37.213 | Ericsson |
| R1-2203005 | Rel-16 editorial corrections for TS 37.213 (mirrored to Rel-17) | Ericsson |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2201065 | Draft CR on BFR with 2-step RACH | vivo |
| R1-2201066 | Draft CR on BFR with 2-step RACH | vivo |
| R1-2202505 | Summary of preparation phase email discussion for Rel-16 2-step RACH | Moderator (ZTE) |
| R1-2202621 | Summary of email discussion on draft CRs for 2-step RACH | Moderator (vivo) |
| R1-2202779 | Session notes for 7.2.1 (Maintenance of Two step RACH for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2201067 | Discussion on channel access procedures for consecutive UL transmissions | vivo |
| R1-2201068 | Correction on channel access procedures for consecutive UL transmission(s) | vivo |
| R1-2201069 | Correction on channel access procedures for consecutive UL transmission(s) | vivo |
| R1-2201070 | Discussion on frequency hopping for PUSCH with a configured grant | vivo |
| R1-2201071 | Draft CR on frequency hopping for PUSCH with a configured grant | vivo |
| R1-2201072 | Draft CR on frequency hopping for PUSCH with a configured grant | vivo |
| R1-2201291 | Correction on Type-3 HARQ-ACK codebook | OPPO |
| R1-2201292 | Draft CR on unit of CP extension | OPPO |
| R1-2201325 | Correction on RRC parameter for multi-PUSCH scheduling | CATT |
| R1-2201396 | Correction on semi-static channel access procedure in TS 38.213 | ZTE, Sanechips |
| R1-2201397 | Correction on semi-static channel access procedure in TS 37.213 | ZTE, Sanechips |
| R1-2201398 | Clarification on frequency hopping for CG-PUSCH | ZTE, Sanechips |
| R1-2201622 | Discussion on the frequency hopping for CG-PUSCH in unlicensed band | Huawei, HiSilicon |
| R1-2201623 | Corrections on frequency hopping for CG-PUSCH in TS38.214 | Huawei, HiSilicon |
| R1-2201990 | Correction on HARQ timing parameters | Samsung |
| R1-2202492 | Preparation phase email discussion summary for Rel.16 NR-U | Moderator (Qualcomm Incorporated) |
| R1-2202671 | Summary for [108-e-R16-NR-U-01] Email discussion/approval on possible LS response to R1-2200860 | Moderator (Samsung) |
| R1-2202672 | [Draft] Reply LS on NR-U channel information and procedures | Samsung |
| R1-2202673 | Reply LS on NR-U channel information and procedures | RAN1, Samsung |
| R1-2202686 | Email discussion summary for editorial changes to be recommended to the specification editors for NR-U | Moderator (Qualcomm Incorporated) |
| R1-2202740 | Correction on channel access procedures for consecutive UL transmissions | Moderator (vivo), Huawei, HiSilicon, Lenovo, Motorola Mobility, ZTE, Sanechips, Intel |
| R1-2202741 | Correction on channel access procedures for consecutive UL transmissions | Moderator (vivo), Huawei, HiSilicon, Lenovo, Motorola Mobility, ZTE, Sanechips, Intel |
| R1-2202742 | Correction on frequency hopping for PUSCH with a configured grant | Moderator (vivo), Huawei, HiSilicon, Ericsson, Samsung, Intel, Lenovo, Motorola Mobility, LG Electronics, ZTE, Sanechips |
| R1-2202743 | Correction on frequency hopping for PUSCH with a configured grant | Moderator (vivo), Huawei, HiSilicon, Ericsson, Samsung, Intel, Lenovo, Motorola Mobility, LG Electronics, ZTE, Sanechips |
| R1-2202744 | Summary of Email discussion on [108-e-R16-NR-U-02] | Moderator (vivo) |
| R1-2202745 | Summary of Email discussion on [108-e-R16-NR-U-03] | Moderator (vivo) |
| R1-2202780 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Huawei) |
| R1-2202805 | Corrections on HARQ-ACK timing parameters for Rel-16 | Moderator (Samsung), ZTE, Sanechips, Lenovo |
| R1-2202806 | Corrections on HARQ-ACK timing parameters for Rel-17 | Moderator (Samsung), ZTE, Sanechips, Lenovo |
| R1-2202807 | Summary of [108-e-R16-NR-U-04] Email discussion/approval on corrections on HARQ-ACK timing parameters | Moderator (Samsung) |
| 7.2.3 | Maintenance of Integrated Access and Backhaul for NR | |
| R1-2202407 | Draft CR on properties of tdd-UL-DL-ConfigurationDedicated and tdd-UL-DL-configurationDedicated-IAB-MT | Ericsson |
| R1-2202819 | CR on properties of tdd-UL-DL-ConfigurationDedicated and tdd-UL-DL-configurationDedicated-IAB-MT | Moderator (Qualcomm), Ericsson |
| R1-2202820 | CR on properties of tdd-UL-DL-ConfigurationDedicated and tdd-UL-DL-configurationDedicated-IAB-MT | Moderator (Qualcomm), Ericsson |
| 7.2.4 | Maintenance for 5G V2X with NR sidelink | |
| R1-2201073 | Draft CR on UE procedure for receiving HARQ-ACK on sidelink | vivo |
| R1-2201074 | Draft CR on UE procedure for receiving HARQ-ACK on sidelink | vivo |
| R1-2201252 | Draft CR for Corrections for HARQ reporting to higher layer | OPPO |
| R1-2201253 | Draft CR for Corrections for Type-1 codebook generation in PUCCH | OPPO |
| R1-2201461 | Correction of SL type 1 HARQ-ACK codebook for boundary of resource pool period | NTT DOCOMO, INC. |
| R1-2201600 | Correction on the parameter name for SL BWP configuration in TS 38.213 | ZTE, Sanechips |
| R1-2201601 | Corrections of the parameters for configuring and indicating the additional MCS table in TS 38.214 | ZTE, Sanechips |
| R1-2201602 | Correction for determining sidelink HARQ-ACK information bits in TS 38.213 | ZTE, Sanechips |
| R1-2201603 | Editorial modification for PSFCH power control in TS 38.213 | ZTE, Sanechips |
| R1-2201604 | Correction on SL Type-1 and Type-2 HARQ-ACK codebook in TS 38.213 | ZTE, Sanechips |
| R1-2201991 | Draft CR on TS 38.214 on Tscal value | Samsung |
| R1-2202118 | Draft CR on CBR Calculation | Qualcomm Incorporated |
| R1-2202119 | Draft CR on Receiving TDD-pattern bits in a dedicated or FDD band | Qualcomm Incorporated |
| R1-2202185 | Correction on DCI size alignment for sidelink | Sharp |
| R1-2202186 | Clarification on simultaneous PSFCH transmission and reception | Sharp |
| R1-2202187 | Clarification on the condition to tigger re-evaluation in mode 2 | Sharp |
| R1-2202357 | Draft CR on corrections on SL timing | Nokia, Nokia Shanghai Bell |
| R1-2202440 | Correction on misalignment for RRC parameters for SL BWP | Huawei, HiSilicon |
| R1-2202442 | Addition of Rel-16 NR V2X bands to TR 37.985 | Huawei, HiSilicon |
| R1-2202443 | Correction on misalignment for RRC parameters for using TRIV | Huawei, HiSilicon |
| R1-2202516 | Moderator Summary #1 of 38.214 alignment CR considering R1-2201601 and R1-2202443 | Moderator (ZTE) |
| R1-2202517 | Moderator Summary #2 of 38.214 alignment CR considering R1-2201601 and R1-2202443 | Moderator (ZTE) |
| R1-2202518 | Moderator Summary #3 of 38.214 alignment CR considering R1-2201601 and R1-2202443 | Moderator (ZTE) |
| R1-2202600 | Summary of email discussion [108-e-R16-V2X-07], Corrections on SL timing | Moderator (Nokia) |
| R1-2202614 | Summary for email discussion [108-e-R16-V2X-05] | Moderator (OPPO) |
| R1-2202626 | [108-e-R16-V2X-02] Alignment CR on TS 38.213 on Rel-16 V2X issues | Moderator (vivo) |
| R1-2202627 | [108-e-R16-V2X-04] UE procedure for receiving HARQ-ACK on sidelink | Moderator (vivo) |
| R1-2202657 | Summary of [108-e-R16-V2X-06] | Moderator (Sharp) |
| R1-2202674 | Addition of Rel-16 NR V2X bands to TR 37.985 | Huawei (editor), ZTE, Sanechips |
| R1-2202675 | Addition of Rel-16 NR V2X bands to TR 37.985 | Huawei (editor), ZTE, Sanechips |
| R1-2202684 | FL summary on [108-e-R16-V2X-08] Addition of Rel-16 NR V2X bands to TR 37.985 | Moderator (Huawei) |
| R1-2202688 | CR on UE procedure for receiving HARQ-ACK on sidelink | Moderator (vivo), Apple, Huawei, HiSilicon, Ericsson, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2202689 | CR on UE procedure for receiving HARQ-ACK on sidelink | Moderator (vivo), Apple, Huawei, HiSilicon, Ericsson, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2202721 | CR on corrections on SL timing | Moderator (Nokia), Nokia Shanghai Bell, vivo, ZTE, Sanechips, Ericsson, Huawei, HiSilicon, Samsung |
| R1-2202722 | CR on corrections on SL timing | Moderator (Nokia), Nokia Shanghai Bell, vivo, ZTE, Sanechips, Ericsson, Huawei, HiSilicon, Samsung |
| R1-2202735 | Draft Reply LS to RAN4 on PEMAX for NR-V2X | Moderator (HiSilicon) |
| R1-2202736 | Reply LS to RAN4 on PEMAX for NR-V2X | RAN1, HiSilicon |
| R1-2202749 | Summary of [108-e-R16-V2X-01] Email discussion on response for incoming LS on PEMAX for NR-V2X in R1-2200866 | Moderator (HiSilicon) |
| R1-2202816 | Reply LS to RAN4 on PEMAX for NR-V2X | RAN1, HiSilicon |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC (Incl. maintenance for IIoT) | |
| R1-2200998 | UE Procedures for UCI Multiplexing and Prioritization | Ericsson |
| R1-2200999 | Interaction of MAC and PHY for Intra-UE Multiplexing/Prioritization | Ericsson |
| R1-2201000 | Physical Layer Intra-UE Multiplexing/Prioritization and UL Skipping | Ericsson |
| R1-2201001 | Resolving Overlapping SPS HARQ-ACK with Repetition | Ericsson |
| R1-2201075 | Discussion on SRS resource indication for Type 1 CG | vivo |
| R1-2201076 | Draft 38.214 CR on Parameter Indication for Type 1 CG | vivo |
| R1-2201160 | Discussion on UE procedures for UCI multiplexing and prioritization | ZTE |
| R1-2201293 | Discussion and draft CR on scheduling and HARQ enhancement | OPPO |
| R1-2201294 | Remaining issues on intra-UE prioritization and multiplexing | OPPO |
| R1-2201326 | Discussion on intra-UE multiplexing/prioritization for eURLLC | CATT |
| R1-2201402 | [Draft CR] Correction on UE procedure for intra-UE prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2201403 | Clarification on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | Nokia, Nokia Shanghai Bell |
| R1-2201624 | Corrections on SRS | Huawei, HiSilicon |
| R1-2201625 | Remaining issues on UL prioritization and UL skipping | Huawei, HiSilicon |
| R1-2201626 | Remaining issues on UCI multiplexing and prioritization | Huawei, HiSilicon |
| R1-2201627 | Remaining issues on UL prioritization cases related to SP-CSI | Huawei, HiSilicon |
| R1-2201656 | Clarification on HARQ-ACK for SPS PDSCH | Ericsson Inc. |
| R1-2201756 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple |
| R1-2201821 | 38.213 corrections on RRC parameter for URLLC | ASUSTeK |
| R1-2201823 | 38.214 corrections on RRC parameter for URLLC | ASUSTeK |
| R1-2201992 | Remaining issues on intra-UE multiplexing/prioritization | Samsung |
| R1-2202120 | Draft CR on SRS resource set trigger for DCI format 2_3 | Qualcomm Incorporated |
| R1-2202188 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by DCI format 0_0 | Sharp |
| R1-2202439 | Corrections on BWP switching using DCI format 0_2/1_2 | Huawei, HiSilicon |
| R1-2202570 | Summary of preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2202629 | Summary#1 of email discussion [108-e-R16-URLLC-05] Miscellaneous corrections on Rel-16 URLLC | Moderator (Huawei) |
| R1-2202630 | Final summary of email discussion [108-e-R16-URLLC-05] Miscellaneous corrections on Rel-16 URLLC | Moderator (Huawei) |
| R1-2202680 | Correction on determination of SRS resource set triggered by DCI format 2_3 | Moderator (Huawei), HiSilicon, Qualcomm |
| R1-2202681 | Correction on determination of SRS resource set triggered by DCI format 2_3 | Moderator (Huawei), HiSilicon, Qualcomm |
| R1-2202700 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by fallbackRAR UL grant | Moderator (Sharp), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Apple, ZTE |
| R1-2202701 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by fallbackRAR UL grant | Moderator (Sharp), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Apple, ZTE |
| R1-2202718 | Summary of [108-e-R16-URLLC-06]: Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant | Moderator (Sharp) |
| R1-2202729 | Summary of [108-e-NR-L1enh-URLLC-02] Discussion on remaining issues on UL prioritization and UL skipping | Moderator (vivo) |
| R1-2202730 | Draft Reply LS on Intra UE Prioritization Scenario | Moderator (vivo) |
| R1-2202733 | Summary of [108-e-R16-URLLC-04] Issue#6: Discussion on determination of SRS resource set triggered by DCI format 2_3 | Moderator (Huawei) |
| R1-2202734 | Reply LS on Intra UE Prioritization Scenario | RAN1, vivo |
| R1-2202772 | Summary of [108-e-R16-URLLC-03] Issue#4: Clarification on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | Moderator (Nokia) |
| R1-2202916 | Summary of email discussion [108-e-R16-URLLC-01] on UCI multiplexing and prioritization in Rel-16 | Moderator (Apple) |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2201327 | Draft CR on Type II and enhanced Type II CSI feedback | CATT |
| R1-2201631 | Draft CR on indicated TCI states for single-DCI based MTRP schemes | vivo |
| R1-2201632 | Draft CR on indicated TCI states for single-DCI based MTRP schemes | vivo |
| R1-2201993 | Correction on frequency granularity of CSI based on Rel.16 Type II codebooks | Samsung |
| R1-2202121 | Discussion on coefficients partition in eT2 CSI | Qualcomm Incorporated |
| R1-2202314 | Correction in the number of NZC mapped in Group 1 and 2, 38.212 | Nokia, Nokia Shanghai Bell |
| R1-2202315 | Correction in the number of NZC mapped in Group 1 and 2, 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2202504 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2202690 | Draft reply LS on UE Capability for supporting single DCI transmission scheme for multi-TRP | Moderator (Apple) |
| R1-2202691 | Reply LS on UE Capability for supporting single DCI transmission scheme for multi-TRP | RAN1, Apple |
| R1-2202709 | Summary of [108-e-R16-MIMO-01] for incoming LS on UE capability for supporting single DCI transmission schemes for multi-TRP in R1-2200872 | Moderator (Apple) |
| R1-2202750 | Summary of [108-e-R16-MIMO-02] MT.1 | Moderator (vivo) |
| R1-2202751 | CR on correction of indicated TCI states for single-DCI based MTRP schemes | Moderator (vivo) |
| R1-2202752 | CR on correction of indicated TCI states for single-DCI based MTRP schemes | Moderator (vivo) |
| R1-2202797 | CR on PMI indexing correction in Type II and eType II CSI | Moderator (Qualcomm Incorporated), CATT, ZTE, Ericsson |
| R1-2202798 | CR on PMI indexing correction in Type II and eType II CSI | Moderator (Qualcomm Incorporated), CATT, ZTE, Ericsson |
| R1-2202799 | Correction of NZC partitioning in eType II CSI | Moderator (Qualcomm Incorporated), Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R1-2202800 | Correction of NZC partitioning in eType II CSI | Moderator (Qualcomm Incorporated), Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R1-2202801 | Correction of NZC partitioning in eType II CSI | Moderator (Qualcomm Incorporated), Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R1-2202802 | Correction of NZC partitioning in eType II CSI | Moderator (Qualcomm Incorporated), Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R1-2202803 | Summary of [108-e-R16-MIMO-03] NZC partitioning and PMI indexing correction for eT2 CSI (final) | Moderator (Qualcomm Incorporated) |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2201077 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2202267 | Draft CR on reference point for UL SRS-RSRP | CATT |
| R1-2202387 | Maintenance for NR positioning support | Ericsson |
| R1-2202420 | Correction to expected RSTD | Huawei, HiSilicon |
| R1-2202453 | Correction to UL SRS-RSRP | Huawei, HiSilicon |
| R1-2202519 | Summary of the preparation phase for Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2202613 | Summary on email discussion [108-e-R16-Pos-01] for the proposals in the draft CRs in R1-2202267 and R1-2202453 | Moderator (CATT) |
| R1-2202661 | Draft CR on reference point for UL SRS-RSRP | Moderator (CATT), Huawei, HiSilicon |
| R1-2202662 | CR on reference point for UL SRS-RSRP | Moderator (CATT), Huawei, HiSilicon |
| R1-2202663 | CR on reference point for UL SRS-RSRP | Moderator (CATT), Huawei, HiSilicon |
| R1-2202682 | Summary of the e-mail discussion [108-e-R16-Pos-02] on Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2202781 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Huawei) |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2202427 | Correction on Rel-16 UE Power Saving | Huawei, HiSilicon |
| R1-2202509 | [108-e-Prep-AI7.2.10] Preparation phase summary for Rel-16 NR MR-DC & CA maintenance | Moderator (Nokia) |
| R1-2202782 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2202844 | Correction on Rel-16 UE dormancy adaptation | Moderator (Huawei), HiSilicon |
| R1-2202845 | Correction on Rel-16 UE dormancy adaptation | Moderator (Huawei), HiSilicon |
| R1-2202871 | Discussion on correction for Rel-16 UE dormancy adaptation | Moderator (Huawei) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2201462 | Correction on UE feature list for NR positioning and eMIMO | NTT DOCOMO, INC. |
| R1-2201757 | Rel-16 UE feature remaining issue | Apple |
| R1-2202084 | On UE capability of maximum number of layers for multi-TRP | MediaTek Inc. |
| R1-2202180 | Rel-16 UL MIMO coherence capability | Qualcomm Incorporated |
| R1-2202508 | Summary on Rel-16 NR UE features related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2202510 | Summary on [108-e-R16-UE-features-MIMO-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2202511 | Summary on [108-e-R16-UE-features-MIMO-02] | Moderator (NTT DOCOMO, INC.) |
| R1-2202512 | Summary on [108-e-R16-UE-features-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2202643 | Summary on [108-e-R16-UE-features-Others-02] | Moderator (NTT DOCOMO, INC.) |
| R1-2202763 | Updated RAN1 UE features list for Rel-16 NR after RAN1#108-e | Moderator (NTT DOCOMO, INC.) |
| R1-2202764 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#108-e | RAN1, NTT DOCOMO |
| 7.2.12 | Other | |
| R1-2202051 | Clarification on PUSCH with UCI Only and DMRS Multiplexing | MediaTek Inc. |
| 8 | Release 17 | |
| R1-2201431 | TEI17: Introduction of Timing advance (TA) PRACH based solution for NR UL E-CID [NRTADV] | Intel Corporation |
| R1-2202539 | DRAFT LS on updated Rel-17 LTE and NR higher-layers parameter list | Moderator (Ericsson) |
| R1-2202540 | Consolidated higher layers parameter list for Rel-17 LTE | Moderator (Ericsson) |
| R1-2202541 | Consolidated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| R1-2202542 | LS on updated Rel-17 LTE and NR higher-layers parameter list | RAN1, Ericsson |
| R1-2202543 | Summary of Email discussion on Rel-17 RRC parameters for LS to RAN2 | Moderator (Ericsson) |
| R1-2202544 | Collection of updated higher layers parameter list for Rel-17 LTE and NR | Moderator (Ericsson) |
| R1-2202757 | DRAFT LS on updated Rel-17 LTE and NR higher-layers parameter list | Moderator (Ericsson) |
| R1-2202758 | Consolidated higher layers parameter list for Rel-17 LTE | Moderator (Ericsson) |
| R1-2202759 | Consolidated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| R1-2202760 | LS on updated Rel-17 LTE and NR higher-layers parameter list | RAN1, Ericsson |
| R1-2202761 | Collection of updated higher layers parameter list for Rel-17 LTE and NR | Moderator (Ericsson) |
| R1-2202913 | Recommendations for RAN1 RRC Parameter Preparation | Moderator (Ericsson) |
| 8.1 | Maintenance on Further enhancements on MIMO for NR | |
| R1-2202717 | Draft LS on feMIMO RRC parameters | Ericsson |
| R1-2202720 | LS on feMIMO RRC parameters | RAN1, Ericsson |
| R1-2202728 | Draft LS response on MPE information signalling | Moderator (Nokia) |
| R1-2202731 | Moderator summary for LS reply to RAN2 on MPE information signalling | Moderator (Nokia) |
| R1-2202732 | LS response on MPE information signaling | RAN1, Nokia |
| R1-2202766 | Draft LS on feMIMO RRC parameters | Ericsson |
| R1-2202804 | TP for TS 38.300 on Rel-17 NR FeMIMO | Moderator (Samsung) |
| R1-2202865 | TP on Rel-17 NR FeMIMO for TS 38.300 | RAN1, Samsung |
| R1-2202900 | Moderator summary for LS reply to RAN2 on feMIMO RRC parameters | Moderator (Ericsson) |
| R1-2202903 | LS on feMIMO RRC parameters | RAN1, Ericsson |
| R1-2202976 | Corrections to MIMO enhancements | Ericsson |
| R1-2202981 | Corrections on further enhancements on MIMO for NR | Samsung |
| R1-2202991 | Correction on further enhancements on MIMO for NR | Nokia |
| R1-2203003 | Corrections on Further enhancements on MIMO for NR in TS 38.212 | Huawei |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2200929 | Remaining issues on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2200996 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2201078 | Maintenance on multi beam enhancement | vivo |
| R1-2201185 | Remaining issues on multi-beam enhancements | ZTE |
| R1-2201223 | Enhancements on Multi-beam Operation | OPPO |
| R1-2201328 | Discussion on remaining issues on Rel-17 multi-beam operation | CATT |
| R1-2201425 | Remaining issues in enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2201426 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2201463 | Remaining issues on multi-beam operation | NTT DOCOMO, INC. |
| R1-2201534 | Remaining issues on multi-beam enhancements | Spreadtrum Communications |
| R1-2201567 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2201575 | Remaining issues on Multi-beam Operation | Sony |
| R1-2201644 | Remaining issues on multi-beam enhancements | Ericsson |
| R1-2201682 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2201758 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2201844 | Remaining issues of enhancements on multi-beam operation | CMCC |
| R1-2201896 | Discussion on remaining issues on multi-beam operation | NEC |
| R1-2201943 | Remaining issues on multi-beam operation enhancement | Xiaomi |
| R1-2201994 | Moderator Summary for Maintenance on Rel-17 Multi-Beam | Moderator (Samsung) |
| R1-2201995 | Moderator Summary for Offline Discussion on Rel-17 Multi-Beam | Moderator (Samsung) |
| R1-2201996 | Maintenance on Rel-17 Multi-Beam | Samsung |
| R1-2202057 | Remaining issues on Rel-17 multi-beam operation | MediaTek Inc. |
| R1-2202122 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2202316 | Maintenance of enhancements for Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2202607 | Moderator Summary#2 for Maintenance on Rel-17 Multi-Beam: Round1 | Moderator (Samsung) |
| R1-2202677 | Moderator Summary#3 for Maintenance on Rel-17 Multi-Beam: Round2 | Moderator (Samsung) |
| R1-2202692 | Draft reply LS to RAN3 on TCI State Update for L1/L2-Centric Inter-Cell Mobility | ZTE |
| R1-2202693 | Reply LS to RAN3 on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN1, ZTE |
| R1-2202723 | Email Discussion Summary of [108-e-R17-MIMO-01] Response to RAN3 LS R1-2200861 | Moderator (ZTE) |
| R1-2202762 | Moderator Summary#4 for Maintenance on Rel-17 Multi-Beam: Round3 | Moderator (Samsung) |
| R1-2202765 | Follow-up LS on feMIMO RRC parameters | RAN1, Ericsson |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2200930 | Remaining issues on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2200992 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2201079 | Maintenance on Multi-TRP for PDCCH, PUCCH and PUSCH enhancements | vivo |
| R1-2201186 | Remaining issues on multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2201224 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2201329 | Discussion on remaining issues on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2201427 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2201464 | Remaining issues on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2201535 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2201568 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2201683 | Maintenance of multi-TRP PDCCH, PUCCH and PUSCH enhancements | Intel Corporation |
| R1-2201759 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2201845 | Remaining issues of enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2201897 | Discussion on remaining issues on multi-TRP for PUCCH and PUSCH | NEC |
| R1-2201939 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | Xiaomi |
| R1-2201959 | Remaining issues on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2201997 | Maintenance on Rel-17 Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2202123 | Remaining details of Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2202266 | Remaining issues on PDCCH, PUSCH and PUCCH enhancements for multi-TRP | Ericsson |
| R1-2202284 | Remaining issues for mTRP PDCCH and PUSCH | ASUSTeK |
| R1-2202317 | Maintenance of enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2202595 | Summary #1 of [108-e-R17-MIMO-02] Email discussion for maintenance on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2202596 | Summary #2 of [108-e-R17-MIMO-02] Email discussion for maintenance on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2202636 | Summary #1 for mTRP PUCCH/PUSCH Enhancements | Moderator (Nokia) |
| R1-2202637 | Summary #2 for mTRP PUCCH/PUSCH Enhancements | Moderator (Nokia) |
| R1-2202902 | Summary #3 for mTRP PUCCH/PUSCH Enhancements | Moderator (Nokia) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2200931 | Remaining issues on inter-cell multi-TRP operation in Rel-17 | Huawei, HiSilicon |
| R1-2200993 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2201080 | Maintenance on inter-cell MTRP operation | vivo |
| R1-2201187 | Remaining issues on multi-TRP inter-cell operation | ZTE |
| R1-2201225 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2201330 | Discussion on remaining issues on inter-cell operation for multi-TRP/panel | CATT |
| R1-2201428 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2201465 | Remaining issues on inter-cell multi-TRP operation | NTT DOCOMO, INC. |
| R1-2201536 | Discussion on enhancements on multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2201569 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2201621 | Finalizing Multi-TRP inter-cell operation | Ericsson |
| R1-2201684 | Maintenance of multi-TRP inter-cell operation | Intel Corporation |
| R1-2201760 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2201846 | Remaining issues of enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2201941 | Maintenance on multi-TRP Inter-cell Operation | Xiaomi |
| R1-2201998 | Maintenance on Rel-17 Inter-cell Multi-TRP | Samsung |
| R1-2202124 | Remaining details of Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2202318 | Maintenance of enhancements enabling inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2202660 | Feature lead summary#1 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2202714 | Feature lead summary#2 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2202725 | LS on RRC parameters update for IE SSB-MTCAdditionalPCI-r17 | RAN1, vivo |
| R1-2202887 | Feature lead summary#3 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2200932 | Remaining issues on beam management for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2200994 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2201081 | Maintenance on MTRP multibeam enhancement | vivo |
| R1-2201188 | Remaining issues on beam management for Multi-TRP | ZTE |
| R1-2201226 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2201331 | Remaining issues on beam failure recovery for multi-TRP | CATT |
| R1-2201429 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2201435 | Remaining issues of enhancements on beam management for multi-TRP | Fujitsu |
| R1-2201466 | Remaining issues on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2201537 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2201570 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2201576 | Remaining issues on beam management for multi-TRP | Sony |
| R1-2201685 | Maintenance of multi-TRP beam management | Intel Corporation |
| R1-2201761 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2201847 | Remaining issues of enhancements on beam management for multi-TRP | CMCC |
| R1-2201944 | Remaining issues on beam management for Multi-TRP enhancement | Xiaomi |
| R1-2201999 | Maintenance on Rel-17 Beam Management for Multi-TRP | Samsung |
| R1-2202059 | Remaining issues on beam management for multi-TRP | MediaTek Inc. |
| R1-2202125 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2202246 | Remaining issues on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2202272 | Remaining issues on beam management enhancements for multi-TRP | Ericsson |
| R1-2202319 | Maintenance of enhancements for Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2202612 | Moderator summary #1 on enhancements of beam management for multi-TRP | Moderator (CATT) |
| R1-2202667 | Moderator summary #2 on enhancements of beam management for multi-TRP | Moderator (CATT) |
| R1-2202814 | Moderator summary #3 on enhancements of beam management for multi-TRP | Moderator (CATT) |
| R1-2202941 | [Draft] Additional LS response to RAN2 on beam management for multi-TRP | Moderator (CATT) |
| R1-2202942 | Additional LS response to RAN2 on beam management for multi-TRP | RAN1, CATT |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2200933 | Remaining issues on HST multi-TRP deployment in Rel-17 | Huawei, HiSilicon |
| R1-2201082 | Maintenance on HST-SFN schemes | vivo |
| R1-2201189 | Remaining issues on multi-TRP HST enhancements | ZTE |
| R1-2201227 | Enhancements on HST-SFN deployment | OPPO |
| R1-2201332 | Discussion on remaining issues on Rel-17 HST-SFN | CATT |
| R1-2201467 | Remaining issues on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2201538 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2201571 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2201618 | Finalizing Multi-TRP HST-SFN enhancements | Ericsson |
| R1-2201686 | Maintenance of HST-SFN enhancements | Intel Corporation |
| R1-2201848 | Remaining issues of enhancements on HST-SFN deployment | CMCC |
| R1-2201945 | Remaining issues on HST-SFN deployment enhancement | Xiaomi |
| R1-2202000 | Maintenance on Rel-17 HST-SFN | Samsung |
| R1-2202088 | Enhancements for HST-SFN deployment | Lenovo |
| R1-2202126 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2202320 | Maintenance of enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2202494 | Maintenance of enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2202545 | Summary#1 of AI: 8.1.2.4 Maintenance on enhancements for HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2202649 | Summary#2 of AI: 8.1.2.4 Maintenance on enhancements for HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2202755 | Summary#3 of AI: 8.1.2.4 Maintenance on enhancements for HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2202808 | Summary#4 of AI: 8.1.2.4 Maintenance on enhancements for HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2202809 | Draft reply LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Moderator (Intel Corporation) |
| R1-2202810 | Reply LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | RAN1, Intel Corporation |
| R1-2202914 | Agreed TPs to TS 38.213 and TS 38.214 for HST-SFN enhancements | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2200934 | Remaining issues on SRS enhancement in Rel-17 | Huawei, HiSilicon |
| R1-2200995 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2201083 | Maintenance on SRS enhancement | vivo |
| R1-2201190 | Remaining issues on SRS enhancements | ZTE |
| R1-2201201 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2201228 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2201333 | Discussion on remaining issues on SRS Enhancements for Rel-17 | CATT |
| R1-2201430 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2201468 | Remaining issues on SRS enhancement | NTT DOCOMO, INC. |
| R1-2201539 | Considerations on SRS enhancements | Spreadtrum Communications |
| R1-2201572 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2201630 | Maintenance for feMIMO SRS | Ericsson |
| R1-2201687 | Remaining Details on SRS enhancements | Intel Corporation |
| R1-2201762 | Views on Rel-17 SRS enhancement | Apple |
| R1-2201849 | Remaining issues on SRS enhancement | CMCC |
| R1-2201898 | Discussion on remaining issues on SRS enhancement | NEC |
| R1-2201940 | Discussion on SRS enhancements | Xiaomi |
| R1-2202001 | Maintenance on Rel-17 SRS | Samsung |
| R1-2202127 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2202321 | Maintenance of enhancements for SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2202625 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2202767 | FL summary #3 on SRS enhancements | Moderator (ZTE) |
| R1-2202904 | FL summary #4 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2200935 | Remaining issues on CSI enhancement in Rel-17 | Huawei, HiSilicon |
| R1-2201084 | Maintenance on MTRP CSI and Partial reciprocity | vivo |
| R1-2201191 | Remaining issues on CSI enhancements for multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2201229 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2201334 | Maintenance of CSI enhancement on FDD CSI and Multi-TRP/panel Transmission | CATT |
| R1-2201469 | Remaining issues on CSI enhancements | NTT DOCOMO, INC. |
| R1-2201540 | Discussion on CSI enhancements for M-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2201573 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2201850 | Remaining issues of enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2202002 | Maintenance on Rel-17 CSI enhancements | Samsung |
| R1-2202089 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo |
| R1-2202128 | Remaining details of mTRP CSI | Qualcomm Incorporated |
| R1-2202276 | Remaining issues on multi-TRP CSI | Ericsson |
| R1-2202322 | Maintenance of enhancements for CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2202645 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei) |
| R1-2202646 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei) |
| R1-2202647 | TP of Rel-17 CSI Enhancement for TS 38.212 | Moderator (Huawei) |
| R1-2202648 | TP of Rel-17 CSI Enhancement for TS 38.214 | Moderator (Huawei) |
| R1-2202771 | TP of Rel-17 CSI Enhancement of FeType II for TS 38.214 | Moderator (Huawei) |
| 8.1.5 | Other | |
| R1-2201763 | On Further MIMO enhancement beyond Rel-17 | Apple |
| R1-2201851 | Discussion on RRC parameters of Rel-17 FeMIMO | CMCC |
| R1-2202003 | Other Potential Enhancements for Rel-17 Multi-beam | Samsung |
| R1-2202423 | Alignment of field names between specifications | Huawei, HiSilicon |
| 8.2 | Maintenance on Supporting NR from 52.6GHz to 71 GHz | |
| R1-2202687 | Email discussion summary for RRC parameters for NR beyond 52.6GHz | Moderator (Qualcomm Incorporated) |
| R1-2202783 | Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) | Ad-Hoc Chair (Huawei) |
| R1-2202949 | Corrections on extending NR operation to 71 GHz | Samsung |
| R1-2202954 | Corrections to NR in the 52.6 – 71 GHz range | Ericsson |
| R1-2202956 | Corrections of the features extending NR operation to 71 GHz | Ericsson |
| R1-2202960 | Corrections on NR extensions of current NR operation to 71GHz | Nokia |
| R1-2202998 | Corrections to SS-RSRQ and RSSI measurement definitions | Intel Corporation |
| R1-2203001 | Correction on extension of current NR operation to 71 GHz in 38.212 | Huawei |
| 8.2.1 | Initial access aspects | |
| R1-2200952 | Remaining issue of initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200987 | On the remaining issues in initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2201032 | Remaining issues for initial access operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2201085 | Remaining issues on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2201265 | Discussion on remaining issue for initial access aspects | OPPO |
| R1-2201351 | Remaining issues on Initial access aspects for up to 71GHz operation | CATT |
| R1-2201388 | Remaining issues on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201470 | Remaining issues on initial access aspects for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201541 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2201596 | Maintenance on initial access aspects for NR from 52.6 GHz to 71 GHz | Panasonic Corporation |
| R1-2201662 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2201688 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2201734 | Initial Access Aspects | Ericsson |
| R1-2201764 | On remaining issues for initial access | Apple |
| R1-2201901 | Remaining issues on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2202004 | Maintenance on initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202129 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2202189 | Initial access aspects | Sharp |
| R1-2202335 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2202501 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2202502 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2202503 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2202683 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2200953 | Remaining issues of PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200988 | On the remaining issues in multi-slot PDCCH monitoring for Beyond 52.6GHz | FUTUREWEI |
| R1-2201033 | Remaining issues for PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2201086 | Remaining issues on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2201266 | Discussion on remaining issue for PDCCH monitoring enhancement | OPPO |
| R1-2201352 | Remaining issues on PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2201389 | Remaining issues on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201471 | Remaining issues on PDCCH monitoring enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201542 | Remaining issues on the PDCCH monitoring enhancements for 52.6 to 71GHz | Spreadtrum Communications |
| R1-2201593 | Remaining Issues on PDCCH monitoring Enhancements in FR2-2 | TCL Communication |
| R1-2201663 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201689 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2201735 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2201765 | On remaining issues for PDCCH Monitoring | Apple |
| R1-2201899 | Remaining issues on PDCCH enhancement for NR operation from 52.6GHz to 71GHz | NEC |
| R1-2201914 | Remaining issues on PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2202005 | Maintenance on PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202072 | Remaining discussion on PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2202130 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2202190 | PDCCH monitoring enhancements | Sharp |
| R1-2202234 | Remaining issues of PDCCH monitoring enhancements for above 52.6GHz | Transsion Holdings |
| R1-2202273 | PDCCH monitoring for NR operation from 52.6 to 71 GHz | Panasonic |
| R1-2202336 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2202409 | Remaining issues on PDCCH for NR from 52.6 GHz to 71GHz | Lenovo |
| R1-2202412 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2202413 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2202712 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2202713 | Feature lead summary #4 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2200954 | Remaining issues of PUCCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2201034 | Remaining issues for enhanced PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2201267 | Discussion on remaining issue for enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2201390 | Remaining issues on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201736 | PUCCH enhancements | Ericsson |
| R1-2201737 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Ericsson |
| 8.2.4 | Beam management for new SCSs | |
| R1-2200955 | Remaining issues of beam management enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200989 | Remaining issues in Beam Management for Beyond 52.6GHz | FUTUREWEI |
| R1-2201035 | Remaining issues for beam management for new SCSs | InterDigital, Inc. |
| R1-2201036 | Discussion Summary #1 for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| R1-2201087 | Remaining issues on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2201268 | Discussion on remaining issue for beam management for new SCSs | OPPO |
| R1-2201353 | Remaining issues on beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2201391 | Remaining issues on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201472 | Remaining issues on Beam based operation for new SCSs for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201577 | Remaining issues on beam management enhancement for NR Beyond 52.6GHz | Sony |
| R1-2201664 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2201690 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2201738 | Beam Management for New SCSs | Ericsson |
| R1-2201766 | Beam Management for New SCSs | Apple |
| R1-2201942 | Maintenance on beam management for new SCSs | Xiaomi |
| R1-2202006 | Maintenance on beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202073 | Remaining discussion on beam management for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2202131 | Beam management for new SCS | Qualcomm Incorporated |
| R1-2202337 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2202478 | Remaining issues on beam-management for NR from 52.6 GHz to 71GHz | Lenovo |
| R1-2202875 | Discussion Summary #2 for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2200956 | Remaining issues of PDSCH/PUSCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200990 | Remaining issues in PDSCH/PUSCH enhancements for Beyond 52.6GHz | FUTUREWEI |
| R1-2201037 | Remaining issues for PDSCH/PUSCH enhancements to supporting 52.6-71 GHz band in NR | InterDigital, Inc. |
| R1-2201088 | Remaining issues on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2201269 | Discussion on remaining issue for PDSCH/PUSCH enhancements | OPPO |
| R1-2201354 | Remaining issues on PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2201392 | Remaining issues on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201433 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2201436 | Remaining issues of multi-PDSCH scheduling via a single DCI | Fujitsu |
| R1-2201473 | Remaining issues on PDSCH/PUSCH enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201665 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201691 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2201739 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2201767 | On remaining issues for PDSCH PUSCH Enhancements | Apple |
| R1-2201900 | Remaining issues on PDSCH enhancement for NR operation from 52.6GHz to 71GHz | NEC |
| R1-2201915 | Remaining issues on PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2202007 | Maintenance on PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202074 | Remaining discussion on multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2202132 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2202283 | Discussion on multi-PUSCH scheduling | ASUSTeK |
| R1-2202338 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2202339 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2202490 | Remaining issues of PDSCH/PUSCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2202560 | Discussion summary #1 of [108-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2202679 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2202796 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2200957 | Remaining issues of channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2200991 | Remaining Issues in Channel Access for Beyond 52.6 GHz | FUTUREWEI |
| R1-2201038 | Remaining issues for channel access mechanisms | InterDigital, Inc. |
| R1-2201089 | Remaining issues on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2201270 | Discussion on remaining issue for channel access mechanism | OPPO |
| R1-2201355 | Remaining issues on channel access mechanism for up to 71GHz operation | CATT |
| R1-2201393 | Remaining issues on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201474 | Remaining issues on Channel access mechanism for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201543 | Remaining issues on channel access mechanism for 52.6GHz to 71 GHz | Spreadtrum Communications |
| R1-2201578 | Remaining issues on channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2201594 | Remaining issues on channel access for NR in 60GHz unlicensed band | TCL Communication |
| R1-2201666 | Remaining issues on channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2201692 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2201740 | Channel Access Mechanisms | Ericsson |
| R1-2201768 | Remaining details on channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2201902 | Remaining issues on channel access mechanism supporting NR from 52.6 to 71 GHz | NEC |
| R1-2201916 | Remaining issues on channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2202008 | Maintenance on channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202065 | Remaining issue for channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2202133 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2202235 | Remaining issues of channel access mechanism for above 52.6GHz | Transsion Holdings |
| R1-2202244 | Remaining issue on channel access scheme for above 52.6GHz | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2202275 | Discussion on sharing of directional channel occupancy | Panasonic |
| R1-2202340 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2202410 | Remaining issues on channel access for NR from 52.6 GHz to 71GHz | Lenovo |
| R1-2202484 | Remaining issue on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2202493 | FL summary on channel access for NR beyond 52.6GHz, version 1 | Moderator (Qualcomm Incorporated) |
| R1-2202685 | FL summary on channel access for NR beyond 52.6GHz, version 2 | Moderator (Qualcomm Incorporated) |
| R1-2202876 | FL summary on channel access for NR beyond 52.6GHz, version 3 | Moderator (Qualcomm Incorporated) |
| 8.2.7 | Other | |
| R1-2201394 | Discussion on RRC parameters for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2202437 | Discussion on the channel raster and sync raster in FR2-2 | Huawei, HiSilicon |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2202775 | Summary of [108-e-R17-RRC-IIoT-URLLC] Email discussion on Rel-17 RRC parameters for IIoT and URLLC | Moderator (Nokia) |
| R1-2202776 | List of agreements of Rel-17 URLLC/IIoT WI (post RAN1#108-e) | WI rapporteur (Nokia) |
| R1-2202950 | Corrections on IIoT/URLLC enhancements in NR | Samsung |
| R1-2202957 | Corrections of the semi-static channel access mode with UE initiating channel occupancy | Ericsson |
| R1-2202961 | Corrections on enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Nokia |
| R1-2202965 | Corrections on enhanced IIoT and URLLC in 38.212 | Huawei |
| R1-2202977 | Corrections to IIoT and URLLC enhancements | Ericsson |
| 8.3.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2200959 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2201002 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2201017 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2201020 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2201021 | Remaining issues for HARQ-ACK feedback enhancements | New H3C Technologies Co., Ltd. |
| R1-2201090 | Remaining issues on HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2201161 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2201295 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2201356 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2201475 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2201544 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2201579 | Remaining issues on HARQ-ACK enhancements for URLLC | Sony |
| R1-2201599 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2201608 | Discussion on remaining issues on PUCCH carrier switching | Panasonic |
| R1-2201611 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2201693 | Open issues on UE HARQ feedback enhancements | Intel Corporation |
| R1-2201769 | Remaining issues in UE feedback enhancements for HARQ-ACK | Apple |
| R1-2201903 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2202009 | Maintenance on HARQ-ACK feedback enhancements | Samsung |
| R1-2202134 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2202341 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2202773 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2202774 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2200961 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2201022 | Remaining issues on enhancements for unlicensed band URLLC/IIoT | New H3C Technologies Co., Ltd. |
| R1-2201401 | Discussion on unlicensed band URLLC/IIoT | ZTE Corporation |
| R1-2201694 | Remaining Clarifications to Enable URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2202135 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2202363 | Remaining issues on enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2202536 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2202537 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2202538 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2200960 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2201003 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2201018 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201023 | Intra-UE multiplexing and prioritization | New H3C Technologies Co., Ltd. |
| R1-2201091 | Remaining issues on intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2201162 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2201296 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2201357 | Intra-UE multiplexing and prioritization | CATT |
| R1-2201379 | Discussion on intra-UE multiplexing with different priorities | Panasonic Corporation |
| R1-2201439 | Discussion on remaining issue for intra-UE multiplexing | China Telecom |
| R1-2201476 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2201545 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2201580 | Remaining issues on intra-UE multiplexing & prioritisation | Sony |
| R1-2201612 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2201654 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2201695 | Remaining Open Details of Intra-UE Uplink Channel Multiplexing and Prioritization | Intel Corporation |
| R1-2201770 | Views on Intra-UE Multiplexing/Prioritization | Apple |
| R1-2201904 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2202010 | Maintenance on Intra-UE Multiplexing/Prioritization | Samsung |
| R1-2202093 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo |
| R1-2202136 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2202191 | Channel collision handling and intra-UE UCI multiplexing with different priorities | Sharp |
| R1-2202243 | Discussion on intra-UE multiplexing and prioritization | ITRI |
| R1-2202342 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2202485 | Remaining issues on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2202575 | Summary #1 of email thread [108-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2202584 | Summary#1 of email thread [108-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2202644 | Summary#2 of email thread [108-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2202707 | Summary #2 of email thread [108-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2202770 | Summary #3 of email thread [108-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2202830 | Summary#3 of email thread [108-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2201004 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2201019 | On remaining issues of propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2201024 | Discussion on propagation delay compensation enhancements | New H3C Technologies Co., Ltd. |
| R1-2201163 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2201297 | Remaining issues for PDC | OPPO |
| R1-2201696 | Open issues for RTT-based propagation delay compensation | Intel Corporation |
| R1-2202343 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2202438 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2202571 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2202572 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2202812 | Feature lead summary#3 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2202813 | Feature lead summary#4 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2202932 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| 8.4 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2201184 | TP for RAN1 additions to the stg2 CR for TS 38.300 | THALES |
| R1-2202489 | MEO Scenarios and Characteristics | HUGHES Network Systems Ltd |
| R1-2202784 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
| R1-2202836 | RAN1 NR NTN additions for TS 38.300 | Moderator (Thales) |
| R1-2202837 | Draft LS on NR-NTN TP for TS 38.300 | Moderator (Thales) |
| R1-2202838 | LS on NR-NTN TP for TS 38.300 | RAN1, Thales |
| R1-2202872 | Email discussion on NR-NTN TP for TS 38.300 | Moderator (Thales) |
| R1-2202909 | Summary of [108-e-R17-RRC-NR-NTN] Email discussion on Rel-17 RRC parameters for NR to support NTN | Moderator (Thales) |
| R1-2202910 | RAN WG1 Agreements under 8.4 up to eMeeting RAN1#108-e | WI rapporteur (Thales) |
| R1-2202978 | Corrections to NR NTN support | Ericsson |
| R1-2202984 | Corrections on non-terrestrial network operation in NR | Samsung |
| R1-2202992 | Corrections on solutions for NR to support non-terrestrial networks (NTN) | Nokia |
| 8.4.1 | Timing relationship enhancements | |
| R1-2200937 | Maintenance on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2201215 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2201271 | Discussion on remaining issue for timing relationship enhancement | OPPO |
| R1-2201358 | Remaining issues on timing relationship enhancements for NTN | CATT |
| R1-2201546 | Discussion on timing relationship enhancements for NTN | Spreadtrum Communications |
| R1-2201645 | Maintenance aspects of time relations for Rel-17 NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201744 | Remaining issues on timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2201771 | Remaining Issues of Timing Relationship Enhancements for NR NTN | Apple |
| R1-2201804 | On timing relationship maintenance issues for NR NTN | Ericsson Hungary Ltd |
| R1-2201852 | Remaining issues on timing relationship enhancements for NTN | CMCC |
| R1-2201921 | Remaining issues on the timing relationship for NTN | Xiaomi |
| R1-2201969 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2202011 | Maintenance issues on Timing relationship enhancements for NTN | Samsung |
| R1-2202137 | Remaining Issues on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2202206 | Remaining issues of timing relationship for NR-NTN | ZTE |
| R1-2202241 | Remaining issues on timing relationship enhancement for NTN | Baicells |
| R1-2202285 | Remaining issues on timing relationship enhancements in NTN | LG Electronics |
| R1-2202360 | Remaining issues on timing relationship enhancements for NTN | NEC |
| R1-2202526 | FL summary #1 on NTN timing relationships | Moderator (Huawei) |
| R1-2202606 | FL summary #2 on NTN timing relationships | Moderator (Huawei) |
| R1-2202696 | Draft reply LS on NTN-specific SIB | Moderator (Huawei) |
| R1-2202794 | Draft reply LS on NTN-specific SIB | Moderator (Huawei) |
| R1-2202811 | FL summary #5 on NTN timing relationships | Moderator (Huawei) |
| R1-2202843 | Reply LS on NTN-specific SIB | RAN1, Huawei |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2200938 | Maintenance on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2201011 | Maintenance on UL timing and frequency synchronization in NTN | THALES |
| R1-2201216 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2201272 | Discussion on remaining issue for UL time and frequency synchronization | OPPO |
| R1-2201359 | Remaining issues on UL time and frequency synchronization enhancement for NTN | CATT |
| R1-2201387 | Enhancements on UL time and frequency synchronization | PANASONIC R&D Center Germany |
| R1-2201477 | Remaining issues on UL time and frequency synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2201547 | Discussion on enhancements on UL time and frequency synchronization for NTN | Spreadtrum Communications |
| R1-2201581 | Discussion on ambiguity of common TA calculation | Sony |
| R1-2201646 | Maintenance aspects of time and frequency synchronization for Rel-17 NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201745 | Remaining issues on UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2201772 | Remaining Issues of Uplink Time and Frequency Synchronization for NR NTN | Apple |
| R1-2201805 | On UL time and frequency synchronization maintenance issues for NTN | Ericsson Hungary Ltd |
| R1-2201853 | Remaining issues on enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2201922 | Remaining issues on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2202012 | Maintenance issues on UL time and frequency synchronization for NTN | Samsung |
| R1-2202138 | Remaining issues on UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2202207 | Remaining issues of UL synchronization for NR-NTN | ZTE |
| R1-2202286 | Remaining issues on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2202359 | Remaining issues on UL time and frequency synchronization enhancement for NTN | Baicells |
| R1-2202361 | Remaining issues on UL time synchronization for NR NTN | NEC |
| R1-2202551 | FL Summary #1 :Enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2202552 | FL Summary #2 :Enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2202553 | FL Summary #3 :Enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2202710 | Draft Reply LS to RAN2 on NR NTN Neighbour Cell and Satellite Information | Moderator (Thales) |
| R1-2202711 | Draft Reply LS to RAN2 on NR NTN Neighbour Cell and Satellite Information | Moderator (Thales) |
| R1-2202873 | Reply LS to RAN2 on NR NTN Neighbour Cell and Satellite Information | RAN1, Thales |
| R1-2202908 | FL Summary #4 :Enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| 8.4.3 | Enhancements on HARQ | |
| R1-2200939 | Maintenance on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2201092 | Remaining issues on HARQ enhancements for NR-NTN | vivo |
| R1-2201273 | Discussion on remaining issue for HARQ enhancements | OPPO |
| R1-2201360 | Remaining issues on HARQ operation enhancement for NTN | CATT |
| R1-2201478 | Remaining issues on HARQ enhancements for NR NTN | NTT DOCOMO, INC. |
| R1-2201548 | Discussion on enhancements on HARQ for NTN | Spreadtrum Communications |
| R1-2201633 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2201647 | Maintenance aspects related to HARQ for Rel-17 NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201746 | Remaining issues on HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2201773 | Remaining Issue of HARQ Enhancements for NR NTN | Apple |
| R1-2201806 | On HARQ maintenance issues for NR NTN | Ericsson Hungary Ltd |
| R1-2201854 | Remaining issues on enhancements on HARQ for NTN | CMCC |
| R1-2201923 | Discussion on HARQ for NTN | Xiaomi |
| R1-2201960 | Remaining issues on enhancements on HARQ to support NTN | CAICT |
| R1-2202013 | Maintenance issues on HARQ aspects for NTN | Samsung |
| R1-2202139 | Remaining issues on HARQ for NTN | Qualcomm Incorporated |
| R1-2202208 | Remaining issues of HARQ for NR-NTN | ZTE |
| R1-2202242 | Remaining issues on HARQ enhancement for NTN | Baicells |
| R1-2202287 | Remaining issues on HARQ enhancements in NTN | LG Electronics |
| R1-2202362 | Remaining issues on HARQ enhancements for NR NTN | NEC |
| R1-2202622 | Summary#1 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2202623 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| 8.4.4 | Other | |
| R1-2201479 | Remaining issues on other aspects for NR NTN | NTT DOCOMO, INC. |
| R1-2201648 | Maintenance aspects of RRC parameters for Rel-17 NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201812 | On other maintenance issues for NR NTN | Ericsson Hungary Ltd |
| R1-2201855 | Other Aspects for NTN | CMCC |
| R1-2202209 | Remaining issues of additional enhancement for NR-NTN | ZTE |
| R1-2202364 | Remaining issues for NR NTN | NEC |
| R1-2202424 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2202601 | Summary#1 of discussion on maintenance related to signaling of polarization information | Moderator (OPPO) |
| 8.5 | Maintenance on NR Positioning Enhancements | |
| R1-2202495 | FL Summary for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2202496 | FL Summary #2 for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2202785 | Session notes for 8.5 (Maintenance on NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2202846 | [DRAFT] LS on frequency information of SRS for positioning resources | Moderator(CATT) |
| R1-2202847 | LS on frequency information of SRS for positioning resources | RAN1, CATT |
| R1-2202848 | [DRAFT] Reply LS on positioning issues needing further input | Moderator (CATT, Intel) |
| R1-2202849 | Reply LS on positioning issues needing further input | RAN1, CATT, Intel |
| R1-2202985 | Corrections on positioning enhancements in NR | Samsung |
| R1-2202993 | Correction on NR Positioning Enhancements | Nokia |
| R1-2202997 | Corrections to DL PRS-RSRPP and UL SRS-RSRPP measurement definitions | Intel Corporation |
| 8.5.1 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | |
| R1-2200920 | Maintenance of Rx/Tx timing error | Huawei, HiSilicon |
| R1-2201093 | Maintenance on enhancements for RX/TX timing delay mitigating | vivo |
| R1-2201193 | Remaining issues on timing delay mitigation for NR positioning | ZTE |
| R1-2201239 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2201361 | Remaining issues on mitigating UE and gNB Rx/Tx timing errors | CATT |
| R1-2201582 | Remaining Issues on Mitigating Rx/Tx Timing Delays | Sony |
| R1-2201634 | Maintenance of mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2201697 | Maintenance for mitigation UE Rx/Tx and/or gNB Rx/Tx timing delays | Intel Corporation |
| R1-2201824 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2201856 | Remaining issues on UE/gNB Rx/Tx timing errors mitigation | CMCC |
| R1-2202014 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2202140 | Maintenance for Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2202291 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2202366 | Maintenance for Rx/Tx timing delays mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2202370 | Tx/Rx timing error mitigation maintenance issues | Lenovo, Motorola Mobility |
| R1-2202389 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2202497 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2202498 | FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2202499 | FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2202500 | FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2202658 | Draft reply LS on SRS for multi-RTT positioning | Moderator (Huawei) |
| R1-2202659 | Reply LS on SRS for multi-RTT positioning | RAN1, Huawei |
| R1-2202911 | [DRAFT] Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance | Moderator(CATT) |
| R1-2202912 | Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN1, CATT |
| R1-2202921 | [DRAFT] LS on multiple measurement instances | Moderator(CATT) |
| R1-2202922 | LS on multiple measurement instances | RAN1, CATT |
| 8.5.2 | Accuracy improvements for UL-AoA positioning solutions | |
| R1-2200921 | Correction to SRS-RSRP and SRS-RSRPP | Huawei, HiSilicon |
| R1-2201094 | Maintenance on enhancements for UL-AoA method | vivo |
| R1-2201194 | Remaining issues on UL-AOA positioning solutions | ZTE |
| R1-2201240 | Enhancements for UL AoA Positioning | OPPO |
| R1-2201362 | Remaining issues on enhancements for UL-AoA positioning method | CATT |
| R1-2201635 | Maintenance of enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2201698 | Maintenance of Rel.17 NR positioning solutions for UL-AoA method | Intel Corporation |
| R1-2201825 | Remaining issues for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2201857 | Remaining issues on UL-AoA enhancements | CMCC |
| R1-2202015 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2202141 | Maintenance on Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2202292 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2202390 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2202520 | Feature Lead Summary#1 for E-mail Discussion [108-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2202521 | Feature Lead Summary#2 for E-mail Discussion [108-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2202522 | Feature Lead Summary#3 for E-mail Discussion [108-e-NR-ePos-02] | Moderator (Intel Corporation) |
| 8.5.3 | Accuracy improvements for DL-AoD positioning solutions | |
| R1-2200922 | Maintenance of DL-AoD enhancements | Huawei, HiSilicon |
| R1-2201095 | Maintenance on enhancements for DL-AoD method | vivo |
| R1-2201195 | Remaining issues on DL-AoD positioning solutions | ZTE |
| R1-2201241 | Enhancements for DL-AoD positioning | OPPO |
| R1-2201363 | Remaining issues on enhancements for DL-AoD positioning method | CATT |
| R1-2201636 | Maintenance of enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2201699 | Maintenance of Rel.17 NR positioning solutions for DL-AoD method | Intel Corporation |
| R1-2201826 | Remaining issues for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2201858 | Remaining issues on DL-AoD enhancements | CMCC |
| R1-2201946 | Remaining issues on accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2202016 | Discussion on accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2202142 | Maintenance on Potential Enhancements for DL-AoD positioning | Qualcomm Incorporated |
| R1-2202293 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2202367 | Maintenance for Rel-17 DL-AoD | Fraunhofer IIS, Fraunhofer HHI |
| R1-2202371 | DL-AoD Positioning Maintenance | Lenovo, Motorola Mobility |
| R1-2202391 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2202603 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2202604 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2202605 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| 8.5.4 | Latency improvements for both DL and DL+UL positioning methods | |
| R1-2200923 | Maintenance of PRS measurement outside MG | Huawei, HiSilicon |
| R1-2201096 | Maintenance on latency enhancement for NR positioning | vivo |
| R1-2201196 | Remaining issues on latency reduction for NR positioning | ZTE |
| R1-2201242 | Enhancements on Latency Reduction in NR Positioning | OPPO |
| R1-2201364 | Remaining issues on latency reduction for NR positioning | CATT |
| R1-2201480 | Remaining issues on latency improvements for both DL and DL+UL positioning methods | NTT DOCOMO, INC. |
| R1-2201583 | Remaining Issues on Latency Improvements for Positioning Methods | Sony |
| R1-2201637 | Maintenance of PHY Latency Reductions | Nokia, Nokia Shanghai Bell |
| R1-2201774 | Remaining issues on Rel-17 positioning latency reduction | Apple |
| R1-2201827 | Latency improvements for both DL and DL+UL positioning methods | InterDigital, Inc. |
| R1-2201859 | Remaining issues on latency enhancements | CMCC |
| R1-2201947 | Remaining issues on latency improvements for both DL and DL+UL positioning method | Xiaomi |
| R1-2202017 | Discussion on latency improvements for both DL and DL+UL positioning methods | Samsung |
| R1-2202143 | Maintenance on Latency Improvements for Positioning | Qualcomm Incorporated |
| R1-2202294 | Discussion on latency improvements for NR positioning | LG Electronics |
| R1-2202392 | Latency improvements for both DL and DL+UL positioning methods | Ericsson |
| R1-2202513 | Summary #1 of [108-e-R17-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2202514 | Summary #2 of [108-e-R17-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2202515 | Summary #3 of [108-e-R17-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2202841 | Draft LS on the dropping rule of DL signals/channels for capability 1B and 2 | Moderator (Huawei) |
| R1-2202842 | LS on the dropping rule of DL signals/channels for capability 1B and 2 | RAN1, Huawei |
| 8.5.5 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | |
| R1-2200924 | Maintenance of multi-path enhancements | Huawei, HiSilicon |
| R1-2201097 | Maintenance on enhancements for multipath/NLOS mitigation | vivo |
| R1-2201197 | Remaining issues on NLOS and Multi-path mitigation for NR positioning | ZTE |
| R1-2201243 | Discussion on multipath/NLOS mitigation for NR positioning | OPPO |
| R1-2201365 | Remaining issues on information reporting from UE and gNB for multipath/NLOS mitigation | CATT |
| R1-2201481 | Remaining issues on multipath/NLOS mitigation for NR positioning | NTT DOCOMO, INC. |
| R1-2201638 | Maintenance of LoS/NLoS Identification and Mitigation | Nokia, Nokia Shanghai Bell |
| R1-2201700 | Maintenance of Rel.17 NR positioning solutions for NLOS/multipath mitigation | Intel Corporation |
| R1-2201890 | Remaining issues for multipath/NLOS mitigation for positioning | InterDigital, Inc. |
| R1-2201948 | Remaining issues on potential enhancements for multipath/NLOS mitigation | Xiaomi |
| R1-2202018 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Samsung |
| R1-2202144 | Maintenance on Multipath Reporting in NR Positioning | Qualcomm Incorporated |
| R1-2202393 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2202556 | Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2202557 | Feature Lead Summary #2 for Maintenance of multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2202558 | Feature Lead Summary #3 for Maintenance of multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2202559 | Feature Lead Summary #4 for Maintenance of multipath/NLOS mitigation | Moderator (Nokia) |
| 8.5.6 | Other | |
| R1-2201098 | Maintenance on inactive state positioning and on-demand PRS | vivo |
| R1-2201198 | Remaining issues on items led by RAN2 for NR positioning | ZTE |
| R1-2201244 | Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS | OPPO |
| R1-2201366 | Remaining issues on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state | CATT |
| R1-2201440 | Discussion on remaining issue for on-demand DL PRS | China Telecom |
| R1-2201639 | Maintenance of Inactive Mode Positioning and on-demand PRS | Nokia, Nokia Shanghai Bell |
| R1-2201701 | Maintenance of Rel.17 NR positioning solutions for RRC_INACTIVE UEs | Intel Corporation |
| R1-2201860 | Remaining issues on RAN2-led items | CMCC |
| R1-2201891 | Remaining issues for on-demand PRS | InterDigital, Inc. |
| R1-2201910 | Discussion on enhancements of INACTIVE mode positioning and on-demand PRS | CAICT |
| R1-2201949 | Remaining issues on positioning for UE in RRC_INACTIVE state | Xiaomi |
| R1-2202019 | Discussion on demand positioning and positioning in inactive state | Samsung |
| R1-2202145 | Maintenance on enhancements Related to On Demand PRS And Positioning in RRC Inactive State | Qualcomm Incorporated |
| R1-2202295 | Discussion on other enhancements for positioning | LG Electronics |
| R1-2202372 | On-Demand PRS and RRC_INACTIVE Positioning Maintenance | Lenovo, Motorola Mobility |
| R1-2202394 | Further details for on-demand PRS reception and SRS in RRC_INACTIVE | Ericsson |
| R1-2202421 | Maintenance of RRC_INACTIVE state positioning | Huawei, HiSilicon |
| R1-2202523 | Feature Lead Summary#1 for E-mail Discussion [108-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2202524 | Feature Lead Summary#2 for E-mail Discussion [108-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2202525 | Feature Lead Summary#3 for E-mail Discussion [108-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2202618 | [Draft] Reply LS on the applicability of PRS processing window in RRC_INACTIVE state | Moderator (CATT) |
| R1-2202619 | Reply LS on the applicability of PRS processing window in RRC_INACTIVE state | RAN1, CATT |
| 8.6 | Maintenance on Support of Reduced Capability NR Devices | |
| R1-2202533 | FL summary on RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2202534 | Draft RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2202535 | RAN1 agreements for Rel-17 NR RedCap | WI Rapporteur (Ericsson) |
| R1-2202786 | Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2202936 | Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2202986 | Corrections on the introduction of UEs with reduced capabilities in NR | Samsung |
| R1-2202994 | Corrections on NR reduced capability NR devices | Nokia |
| 8.6.1 | UE complexity reduction | |
| R1-2202146 | Remaining Issues on UE Complexity Reduction | Qualcomm Incorporated |
| 8.6.1.1 | Aspects related to reduced maximum UE bandwidth | |
| R1-2200917 | Remaining issues on reduced maximum UE bandwidth | Huawei, HiSilicon |
| R1-2200985 | Remaining aspects of Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2201099 | Remaining issues on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2201136 | Bandwidth reduction for reduced capability NR devices | ZTE, Sanechips |
| R1-2201277 | Remaining issues on reduced UE bandwidth | OPPO |
| R1-2201367 | Remaining issues on reduced maximum UE bandwidth | CATT |
| R1-2201404 | Aspects related to reduced maximum UE bandwidth | Nokia, Nokia Shanghai Bell |
| R1-2201441 | Remaining issues on reduced maximum UE bandwidth for RedCap | China Telecom |
| R1-2201482 | Remaining issues on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2201549 | Discussion on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2201590 | Aspects related to reduced maximum UE bandwidth for RedCap | Panasonic Corporation |
| R1-2201605 | Remaining issues on BWP operation for RedCap | NEC |
| R1-2201668 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2201702 | On reduced BW support for RedCap | Intel Corporation |
| R1-2201775 | Reduced maximum UE bandwidth for Redcap | Apple |
| R1-2201861 | Remaining issues of reduced maximum UE bandwidth | CMCC |
| R1-2201955 | Discussion on the remaining issues of reduced UE bandwidth for RedCap | Xiaomi |
| R1-2201970 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2202020 | UE complexity reduction | Samsung |
| R1-2202061 | On reduced bandwidth for NR RedCap UEs | MediaTek Inc. |
| R1-2202192 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2202250 | Remaining issues on reduced maximum UE bandwidth | InterDigital, Inc. |
| R1-2202344 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2202382 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2202528 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2202529 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2202530 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2202531 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2202532 | FL summary #5 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2202885 | [Draft] LS on operation with and without SSB for RedCap UE | Moderator (Ericsson) |
| R1-2202886 | LS on operation with and without SSB for RedCap UE | RAN1, Ericsson |
| 8.6.1.2 | Other aspects | |
| R1-2201100 | Remaining issues on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2201137 | HD-FDD for reduced capability NR devices | ZTE, Sanechips |
| R1-2201278 | Other remaining issues for Reduced Capability NR Devices | OPPO |
| R1-2201368 | Remaining issues on other aspects related to complexity reduction | CATT |
| R1-2201405 | Other Aspects | Nokia, Nokia Shanghai Bell |
| R1-2201483 | Remaining issues on other aspects for RedCap | NTT DOCOMO, INC. |
| R1-2201525 | Other aspects for complexity reduction for RedCap Ues | Samsung |
| R1-2201550 | Discussion on other aspects for RedCap | Spreadtrum Communications |
| R1-2201591 | Other aspects for RedCap UE complexity reduction | Panasonic Corporation |
| R1-2201669 | Other UE complexity reduction aspects for RedCap | Ericsson |
| R1-2201703 | On other aspects of complexity reduction for RedCap Ues | Intel Corporation |
| R1-2201776 | Other UE complexity reduction aspects for RedCap | Apple |
| R1-2201862 | Remaining issues of collision handling of HD-FDD operation | CMCC |
| R1-2201956 | Discussion on the remaining issues of HD-FDD | Xiaomi |
| R1-2202193 | Discussion on duplex operation for RedCap UEs | Sharp |
| R1-2202345 | Other aspects related to the UE complexity reduction for RedCap | LG Electronics |
| R1-2202418 | Remaining issues on HD-FDD for RedCap UEs | Huawei, HiSilicon |
| R1-2202583 | FL summary #1 on other aspects of UE complexity reduction for RedCap | Moderator (Qualcomm) |
| R1-2202668 | FL summary #2 on other aspects of UE complexity reduction for RedCap | Moderator (Qualcomm) |
| R1-2202669 | FL summary #3 on other aspects of UE complexity reduction for RedCap | Moderator (Qualcomm) |
| R1-2202897 | FL summary #4 on other aspects of UE complexity reduction for RedCap | Moderator (Qualcomm) |
| 8.6.2 | RAN1 aspects for RAN2-led features for RedCap | |
| R1-2200918 | On RAN1 aspects of RAN2 led issues for RedCap | Huawei, HiSilicon |
| R1-2201138 | Higher layer support of Reduced Capability NR devices | ZTE, Sanechips |
| R1-2201279 | Higher layer related issues for Reduced Capability NR Devices | OPPO |
| R1-2201369 | Remaining issues on higher layer support of RedCap | CATT |
| R1-2201406 | Remaining Issues for Higher Layer Support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2201670 | RAN1 aspects for RAN2-led features for RedCap | Ericsson |
| R1-2201863 | Remaining issues for higher layer support of RedCap UE | CMCC |
| R1-2201957 | Discussion on the remaining issues of RAN2-led features for RedCap | Xiaomi |
| R1-2201971 | RAN1 aspects for RAN2-led features for RedCap | Lenovo, Motorola Mobility |
| R1-2202021 | RAN1 aspects for RAN2-led features for RedCap | Samsung |
| R1-2202147 | Remaining Issues on Cross-layer Design for RedCap Devices | Qualcomm Incorporated |
| R1-2202194 | RAN1 aspects for RAN2-led features for RedCap | Sharp |
| R1-2202383 | On RAN2 related aspects | Nordic Semiconductor ASA |
| R1-2202546 | FL summary #1 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| R1-2202589 | FL summary #2 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| R1-2202678 | FL summary #3 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| 8.6.3 | Other | |
| R1-2201671 | On further NR RedCap UE complexity reduction | Ericsson |
| R1-2201864 | Remaining issues of other aspects for RedCap UE | CMCC |
| R1-2201892 | Remaining aspects for RedCap | ZTE, Sanechips |
| R1-2201958 | Discussion on the fast BWP switching for RedCap | Xiaomi |
| R1-2202419 | On RedCap UE BWP configuration | Huawei, HiSilicon |
| 8.7 | Maintenance on UE Power Saving Enhancements | |
| R1-2202787 | Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2202933 | Collection of RAN1 agreements for UE power saving enhancements for NR (post RAN1 #108-e) | WI Rapporteur (MediaTek) |
| R1-2202953 | Corrections on UE power savings enhancements in NR | Samsung |
| R1-2202964 | Corrections on NR UE Power Saving Enhancements | Nokia |
| R1-2202969 | Corrections on UE power saving enhancements in 38.212 | Huawei |
| R1-2202975 | Corrections on NR UE Power Saving Enhancements | Qualcomm |
| R1-2203008 | Summary of email discussion on Rel-17 RRC parameters for UE power saving | Moderator (MediaTek) |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2200944 | Remaining issues on Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2201101 | Remaining issues on paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2201130 | Remaining issues of power saving enhancements for paging | ZTE, Sanechips |
| R1-2201280 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2201370 | Remaining issues of Paging enhancement for UE power saving | CATT |
| R1-2201484 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2201551 | Discussion on potential paging enhancements for UE power saving | Spreadtrum Communications |
| R1-2201641 | On remaining issues of paging enhancement | Panasonic |
| R1-2201705 | Discussion on remaining aspects of the design of paging enhancements | Intel Corporation |
| R1-2201777 | Remaining issues on paging enhancements for idle/inactive UEs | Apple |
| R1-2201865 | Remaining issues on paging early indication | CMCC |
| R1-2201917 | Remaining issues on paging enhancement for power saving | Xiaomi |
| R1-2202022 | Maintenance on paging enhancements | Samsung |
| R1-2202067 | Summary#1 for Maintenance on Paging Enhancements | Moderator (MediaTek) |
| R1-2202068 | Maintenance on Paging Enhancements | MediaTek Inc. |
| R1-2202148 | Remaining issues on paging early indication design | Qualcomm Incorporated |
| R1-2202216 | Maintenance for Paging Enhancements | Ericsson |
| R1-2202236 | Discussion on PEI Design | Transsion Holdings |
| R1-2202247 | Remaining issues on paging enhancements | InterDigital, Inc. |
| R1-2202328 | Open items on paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2202346 | Discussion on potential paging enhancements | LG Electronics |
| R1-2202384 | On paging early indication | Nordic Semiconductor ASA |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2200945 | Remaining issue on assistance TRS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2201102 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2201131 | Remaining issues of TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2201281 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2201371 | Remaining issues of TRS/CSI-RS for paging enhancement | CATT |
| R1-2201485 | Discussion on TRS/CSI-RS occasion for idle/inactive Ues | NTT DOCOMO, INC. |
| R1-2201552 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2201642 | Remaining issues on enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2201706 | Discussion on the remaining details of TRS/CSI-RS occasions in idle/inactive time | Intel Corporation |
| R1-2201778 | Remaining issues on indication of TRS configurations for idle/inactive UEs | Apple |
| R1-2201866 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | CMCC |
| R1-2201918 | Remaining issues on TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2202023 | Maintenance on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2202024 | Moderator Summary#1 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2202069 | Maintenance on TRS/CSI-RS Information for idle/inactive UEs | MediaTek Inc. |
| R1-2202149 | Remaining issues on idle and inactive TRS | Qualcomm Incorporated |
| R1-2202195 | Remaining issues on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2202217 | Maintenance for TRS occasion provisioning for Idle/Inactive UEs | Ericsson |
| R1-2202248 | Remaining issues on TRS/CSI-RS occasions for idle/inactive UEs | InterDigital, Inc. |
| R1-2202329 | Open issues on n TRS information forto IDLE/INACTIVE mode UEs | Nokia, Nokia Shanghai Bell |
| R1-2202347 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2202385 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2202650 | Moderator Summary #2 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2202651 | Moderator Summary #3 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2201132 | Simulation results of UE power saving in RRC idle and inactive state | ZTE, Sanechips |
| R1-2202218 | Modeling of NR gNB power consumption | Ericsson |
| R1-2202426 | Evaluation of power saving gain for IDLE mode power saving enhancements in Rel-17 | Huawei, HiSilicon |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2200946 | Remaining issues on the extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2201103 | Remaining issues on DCI-based power saving adaptation in connected mode | vivo |
| R1-2201133 | Remaining issues of PDCCH monitoring adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2201282 | Remaining issues for DCI-based power saving adaptation | OPPO |
| R1-2201372 | Remaining issues of PDCCH monitoring adaptation | CATT |
| R1-2201486 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2201553 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2201613 | Remaining issues on DCI-based power saving adaptation during DRX active time | ETRI |
| R1-2201643 | Remaining issues for extensions to Rel-16 DCI-based power saving adaptation during DRX Active Time | Panasonic |
| R1-2201707 | Discussion on remaining aspects of power saving in active time | Intel Corporation |
| R1-2201779 | Remaining details on enhanced DCI-based power saving adaptation | Apple |
| R1-2201867 | Remaining issues on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2201919 | Remaining issues on PDCCH monitoring adaptation for power saving | Xiaomi |
| R1-2202025 | Maintenance on DCI-based power saving techniques | Samsung |
| R1-2202070 | Maintenance on DCI-based PDCCH Monitoring Adaptation | MediaTek Inc. |
| R1-2202094 | Enhanced DCI based power saving adaptation | Lenovo |
| R1-2202150 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2202219 | Maintenance for active time power savings mechanisms | Ericsson |
| R1-2202249 | Remaining issues on DCI-based power saving adaptation | InterDigital, Inc. |
| R1-2202330 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2202348 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2202365 | Remaining issues on DCI-based power saving adaptation | NEC |
| R1-2202386 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2202573 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202574 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202738 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202739 | FL summary#4 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202894 | FL summary#5 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202895 | Final FL summary of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2202896 | [Draft] LS reply on PDCCH skipping | vivo |
| R1-2202905 | LS reply on PDCCH skipping | RAN1, vivo |
| 8.7.3 | Other | |
| R1-2201893 | Discussion on power saving for RRC connected UE | ZTE, Sanechips |
| R1-2202220 | Evaluation results for UE power saving schemes | Ericsson |
| R1-2202476 | Discussion on UE assumption of TRS availability | Huawei, HiSilicon |
| 8.8 | NR coverage enhancement | |
| R1-2202788 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2202867 | Reply LS on Stage 2 description for Coverage Enhancements | RAN1, China Telecom |
| R1-2202868 | [108-e-R17-CovEnh-06] Summary of email discussion for incoming LS on Stage 2 description for Coverage Enhancements | Moderator (China Telecom) |
| R1-2202948 | Corrections on coverage enhancements in NR | Samsung |
| R1-2202959 | Corrections on NR coverage enhancements | Nokia |
| R1-2202967 | Corrections on coverage enhancements in 38.212 | Huawei |
| 8.8.1.1 | Enhancements on PUSCH repetition type A | |
| R1-2200966 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2201012 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2201104 | Remaining issues on enhancement for PUSCH repetition type A | vivo |
| R1-2201164 | Discussion on remaining issues for enhanced PUSCH repetition type A | ZTE |
| R1-2201283 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2201373 | Remaining issues on enhancements on PUSCH repetition type A | CATT |
| R1-2201380 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2201442 | Remaining issues on PUSCH repetition type A enhancements | China Telecom |
| R1-2201487 | Remaining issues on enhancements on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2201554 | Discussion on enhancements for PUSCH repetition Type A | Spreadtrum Communications |
| R1-2201657 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2201708 | Remaining details of enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2201780 | Remaining issues on PUSCH repetition type A enhancement | Apple |
| R1-2201868 | Remaining issues on PUSCH repetition type A enhancement | CMCC |
| R1-2201961 | Remaining Issues for PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2202026 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2202151 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2202196 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2202239 | Discussion on PUSCH repetition type A enhancement | TCL Communication Ltd. |
| R1-2202299 | Discussions on PUSCH repetition type A enhancements | LG Electronics |
| R1-2202486 | Remaining issues on enhancements for PUSCH repetition Type A | WILUS Inc. |
| R1-2202566 | FL Summary #1 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2202567 | FL Summary #2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2202568 | FL Summary #3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2202569 | FL Summary #4 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2200967 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2201013 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201105 | Remaining issues on PUSCH TB processing over multiple slots | vivo |
| R1-2201165 | Discussion on remaining issues for TB processing over multi-slot PUSCH | ZTE |
| R1-2201284 | Further considerations for TB over multi-slot PUSCH | OPPO |
| R1-2201374 | Remaining issues on TB processing over multi-slot PUSCH | CATT |
| R1-2201381 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2201488 | Remaining issues on TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2201658 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2201709 | Remaining details on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2201781 | Remaining issues on TB processing over multi-slot PUSCH | Apple |
| R1-2201869 | Remaining issues on TB processing over multi-slot PUSCH | CMCC |
| R1-2201905 | Discussion on remaining issue of TBoMS | NEC |
| R1-2201925 | Remaining issues on TB processing over multi-slot PUSCH | Xiaomi |
| R1-2201962 | Remaining Issues for TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2202027 | TB processing over multi-slot PUSCH | Samsung |
| R1-2202152 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2202197 | TB processing over multi-slot PUSCH | Sharp |
| R1-2202240 | Discussion on TBoMS PUSCH | TCL Communication Ltd. |
| R1-2202300 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2202487 | Remaining issues for TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2202527 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2202638 | FL summary #2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2202639 | FL summary #3 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2202640 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2200968 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2201014 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201106 | Remaining issues on joint channel estimation for PUSCH | vivo |
| R1-2201166 | Discussion on remaining issues for joint channel estimation for PUSCH | ZTE |
| R1-2201285 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2201375 | Remaining issues on joint channel estimation for PUSCH | CATT |
| R1-2201434 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2201443 | Remaining issues on joint channel estimation | China Telecom |
| R1-2201444 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2201489 | Remaining issues on joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2201555 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2201659 | Discussion on joint channel estimation | InterDigital, Inc. |
| R1-2201710 | Remaining details on joint channel estimation for PUSCH | Intel Corporation |
| R1-2201782 | Remaining issues on cross-slot channel estimation for PUSCH | Apple |
| R1-2201870 | Remaining issues on joint channel estimation for PUSCH | CMCC |
| R1-2201912 | Remaining issues on joint channel estimation for PUSCH | Xiaomi |
| R1-2201963 | Remaining Issues for Joint Channel Estimation for PUSCH | Ericsson |
| R1-2202028 | Joint channel estimation for PUSCH | Samsung |
| R1-2202085 | Discussion on Joint channel estimation over multi-slot | MediaTek Inc. |
| R1-2202153 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2202198 | Joint channel estimation for PUSCH | Sharp |
| R1-2202237 | Discussion on joint channel estimation for PUSCH | TCL Communication Ltd. |
| R1-2202301 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2202616 | FL Summary#2 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2202617 | FL Summary#3 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2202869 | FL Summary#4 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2202870 | [108-e-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.2 | PUCCH enhancements | |
| R1-2200969 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2201015 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201107 | Remaining issues on PUCCH enhancements | vivo |
| R1-2201167 | Discussion on remaining issues for coverage enhancements for PUCCH | ZTE |
| R1-2201286 | PUCCH enhancements for coverage | OPPO |
| R1-2201376 | Remaining issues on PUCCH enhancement | CATT |
| R1-2201382 | Discussion on the interaction between inter-slot frequency hopping and DMRS bundling | Panasonic Corporation |
| R1-2201445 | Remaining issues on inter-slot frequency hopping with inter-slot bundling | China Telecom |
| R1-2201490 | Remaining issues on PUCCH enhancement | NTT DOCOMO, INC. |
| R1-2201556 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2201660 | Discussion on PUCCH enhancements | InterDigital, Inc. |
| R1-2201711 | Remaining details on PUCCH enhancements | Intel Corporation |
| R1-2201783 | Remaining issues on PUCCH coverage enhancement | Apple |
| R1-2201871 | Remaining issues on PUCCH enhancements | CMCC |
| R1-2201913 | Remaining issues on PUCCH enhancements | Xiaomi |
| R1-2201964 | Remaining Issues for PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2202029 | PUCCH enhancements | Samsung |
| R1-2202154 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2202199 | PUCCH coverage enhancement | Sharp |
| R1-2202238 | Discussion on PUCCH enhancements | TCL Communication Ltd. |
| R1-2202302 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2202488 | Remaining issues on PUCCH enhancements for coverage enhancement | WILUS Inc. |
| R1-2202555 | FL summary #1 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2202676 | FL summary #2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2202753 | FL summary #3 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2200970 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2201016 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2201108 | Remaining issues on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2201168 | Discussion on remaining issues for Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2201287 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2201377 | Remaining issues on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2201446 | Remaining issues on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2201491 | Remaining issues on type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2201661 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2201712 | Remaining details on Msg3 PUSCH repetition | Intel Corporation |
| R1-2201872 | Remaining issues on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2201926 | Remaining issues on Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2201965 | Remaining Issues for Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2202030 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2202200 | Type A PUSCH repetitions for Msg3 | Sharp |
| R1-2202303 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2202592 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2202593 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2202594 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2202828 | [Draft] Reply LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | Moderator (ZTE) |
| R1-2202829 | Reply LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | RAN1, ZTE |
| 8.8.4 | Other | |
| R1-2201169 | Discussion on RRC parameters for coverage enhancement | ZTE |
| R1-2201966 | Frequency Hopping for TBoMS | Ericsson |
| R1-2202448 | On futher potential coverage enhancements | Huawei, HiSilicon |
| 8.9 | Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2202789 | Session notes for 8.9 (Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2202939 | RAN1 agreements of Additional enhancements for NB-IoT and LTE-MTC | WI rapporteur (Huawei) |
| R1-2202971 | Correction to additional enhancements for NB-IoT and eMTC | Ericsson |
| R1-2202972 | Correction to additional enhancements for NB-IoT and LTE-MTC | FUTUREWEI |
| R1-2202974 | Corrections to Additional Enhancements for NB-IoT and LTE-MTC | Motorola Mobility |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2200976 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2201135 | Discussion on remaining issues for NB-IoT 16QAM | ZTE, Sanechips |
| R1-2201407 | Support of 16-QAM for unicast in UL and DL for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2201650 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2201968 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2202076 | Remaining issue for support 16QAM in NB-IOT R17 | MediaTek Inc. |
| R1-2202277 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2202878 | Feature lead summary on 108-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2202879 | Draft LS on use of CQI table for NB-IoT DL 16QAM | Moderator (Huawei) |
| R1-2202880 | LS on use of CQI table for NB-IoT DL 16QAM | RAN1, Huawei |
| R1-2202881 | Text proposals for NB-IoT 16QAM | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2200977 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2201894 | Remaining issues for introduction of 14-HARQ processes in DL for eMTC | ZTE, Sanechips |
| R1-2202278 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2202369 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2202634 | Feature Lead Summary [108-e-R17-NB-IoT-eMTC-02]: 1st checkpoint | Moderator (Ericsson) |
| R1-2202635 | Feature Lead Summary [108-e-R17-NB-IoT-eMTC-02]: Final checkpoint | Moderator (Ericsson) |
| R1-2202888 | Clarification on PDSCH scheduling delay for 14-HARQ processes | Moderator (ZTE), Sanechips, Ericsson, Lenovo |
| R1-2202889 | Correction of parameter name for 14-HARQ processes | Moderator (ZTE), Sanechips, Ericsson, Lenovo |
| 8.9.3 | Other | |
| R1-2202280 | Clarification on the support of 16-QAM for NB-IoT in TS 36.212 | Ericsson |
| R1-2202281 | Clarification on the support of 16-QAM for NB-IoT in TS 36.213 | Ericsson |
| R1-2202477 | Further considerations on Rel-17 NB-IoT and eMTC enhancements | Huawei, HiSilicon |
| 8.10 | Maintenance on Enhancements to Integrated Access and Backhaul | |
| R1-2202155 | Text proposals for RAN1 related IAB updates to TS 38.300 | Qualcomm Incorporated |
| R1-2202726 | [Draft] LS on upper layers parameters for Rel-17 eIAB | Qualcomm |
| R1-2202737 | LS on upper layers parameters for Rel-17 eIAB | RAN1, Qualcomm |
| R1-2202884 | LS on IAB related RAN1 TP for TS 38.300 | RAN1, Qualcomm |
| R1-2202890 | LS on upper layers parameters for Rel-17 eIAB | RAN1, Qualcomm |
| R1-2202907 | Summary of [108-e-R17-RRC-eIAB] Email discussion on Rel-17 RRC parameters for eIAB | Moderator (Qualcomm) |
| R1-2202943 | RAN1 decisions for Rel-17 eIAB | WI rapporteur (Qualcomm) |
| R1-2202947 | LS on upper layers parameters for Rel-17 eIAB | RAN1, Qualcomm |
| R1-2202980 | Corrections on eIAB | Samsung |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2200926 | Remaining issues on resource multiplexing between backhaul and access | Huawei, HiSilicon |
| R1-2201109 | Remaining issues on enhancement to resource multiplexing between child and parent links | vivo |
| R1-2201456 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2201492 | Remaining issues on resource multiplexing | NTT DOCOMO, INC. |
| R1-2201526 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2201614 | Discussion on IAB resource multiplexing maintenance | ETRI |
| R1-2201673 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2201713 | Frequency-domain Resource Multiplexing for IAB | Intel Corporation |
| R1-2202090 | Resource multiplexing in enhanced IAB systems | Lenovo |
| R1-2202156 | Remaining issues on resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2202305 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2202402 | Resource multiplexing and dual connectivity in enhanced IAB | Ericsson |
| R1-2202547 | Feature lead summary #1 of 8.10.1 | Moderator (AT&T) |
| R1-2202702 | Feature lead summary #2 of 8.10.1 | Moderator (AT&T) |
| R1-2202818 | Feature lead summary #3 of 8.10.1 | Moderator (AT&T) |
| R1-2202874 | Feature lead summary #4 of 8.10.1 | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2200927 | Remaining issues on enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2201110 | Remaining issues on other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2201457 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2201493 | Remaining issues on IAB timing mode | NTT DOCOMO, INC. |
| R1-2201527 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2201615 | Discussion on eIAB simultaneous operation maintenance | ETRI |
| R1-2201674 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Nokia, Nokia Shanghai Bell |
| R1-2201714 | Other Enhancements for Simultaneous Operation of IAB | Intel Corporation |
| R1-2202157 | Remaining issues on enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2202306 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2202403 | Timing in enhanced IAB | Ericsson |
| R1-2202670 | FL summary #1 of [108-e-R17-eIAB-02] | Moderator (Qualcomm) |
| R1-2202831 | FL summary #2 of [108-e-R17-eIAB-02] | Moderator (Qualcomm) |
| R1-2202877 | Reply LS on range of power control parameters for eIAB | RAN1, Samsung |
| 8.10.3 | Other | |
| R1-2201458 | Remaining issue on higher layers parameter list for Rel-17 IAB | ZTE, Sanechips |
| R1-2202404 | Higher layer parameters (RRC, MAC-CE, F1AP, XnAp) for enhanced IAB | Ericsson |
| R1-2202422 | Other enhancements for IAB | Huawei, HiSilicon |
| 8.11 | NR Sidelink enhancement | |
| R1-2202708 | [108-e-R17-RRC-Sidelink] Summary of email discussion on Rel-17 RRC parameters for sidelink enhancement | Moderator (LG Electronics) |
| R1-2202952 | Corrections on sidelink enhancements in NR | Samsung |
| R1-2202963 | Corrections on NR Sidelink enhancements | Nokia |
| R1-2202966 | Corrections on NR sidelink enhancement in 38.212 | Huawei |
| R1-2203006 | Corrections to SL CBR measurement definition | Intel Corporation |
| R1-2203007 | Introduction of Rel-17 sidelink enhancements and concurrent Uu-PC5 bands | Huawei |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2200963 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2200980 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2200982 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2201111 | Remaining issues on resource allocation for sidelink power saving | vivo |
| R1-2201254 | Remaining essential issues on power saving RA | OPPO |
| R1-2201335 | Remaining issues on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2201386 | Remaining Issues on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2201437 | Discussion on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2201494 | Remaining issues on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2201530 | Remaining issues on resource allocation for power saving | InterDigital, Inc. |
| R1-2201557 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2201584 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2201616 | Discussion on resource allocation for power saving | ETRI |
| R1-2201715 | Remaining opens of sidelink resource allocation schemes for UE power saving | Intel Corporation |
| R1-2201784 | Remaining Issues of Sidelink Resource Allocation for Power Saving | Apple |
| R1-2201819 | Remaining issues on partial sensing and SL DRX impact | ASUSTeK |
| R1-2201873 | Remaining issues on resource allocation for power saving | CMCC |
| R1-2201906 | Discussion on resource allocation for power saving | NEC |
| R1-2201929 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2202031 | On Resource Allocation for Power Saving | Samsung |
| R1-2202063 | Resource allocation for sidelink power saving | MediaTek Inc. |
| R1-2202158 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2202201 | Discussion on resource allocation for power saving | Sharp |
| R1-2202230 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2202252 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2202262 | Remaining aspects of resource allocation procedures for power saving | Ericsson |
| R1-2202373 | Remains on resource allocation for power saving in NR sidelink enhancement | ITL |
| R1-2202376 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2202482 | Resource allocation for power saving | Fraunhofer HHI |
| R1-2202561 | FL summary #1 for AI 8.11.1.1 – NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2202562 | FL summary #2 for AI 8.11.1.1 – NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2202563 | FL summary #3 for AI 8.11.1.1 – NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2202564 | FL summary #4 for AI 8.11.1.1 – NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2202565 | FL summary for AI 8.11.1.1 – NR sidelink resource allocation for power saving (EOM) | Moderator (OPPO) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2200964 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2200981 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200983 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2201112 | Remaining issues on mode-2 enhancements | vivo |
| R1-2201182 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2201255 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2201336 | Remaining issues on Inter-UE coordination for Mode 2 enhancements | CATT, GOHIGH |
| R1-2201438 | Discussion on inter-UE coordination for Mode 2 enhancements | Fujitsu |
| R1-2201495 | Remaining issues on sidelink resource allocation for reliability and latency | NTT DOCOMO, INC. |
| R1-2201531 | Discussions on remaining issues for Mode 2 inter-UE coordination | InterDigital, Inc. |
| R1-2201558 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2201585 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2201617 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2201716 | Remaining opens of sidelink inter-UE coordination schemes | Intel Corporation |
| R1-2201785 | Remaining Issues of Inter-UE Coordination | Apple |
| R1-2201820 | Remaining issues on V2X mode 2 enhancements | ASUSTeK |
| R1-2201874 | Remaining issues on inter-UE coordination for mode 2 enhancement | CMCC |
| R1-2201907 | Discussion on mode 2 enhancements | NEC |
| R1-2201920 | Discussion on inter-UE coordination | Xiaomi |
| R1-2202032 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2202086 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2202159 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2202202 | Discussion on inter-UE coordination for mode 2 enhancements | Sharp |
| R1-2202231 | Inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2202245 | Inter-UE coordination for mode 2 enhancements | ITL |
| R1-2202253 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2202254 | Feature lead summary #1 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202255 | Feature lead summary #2 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202256 | Feature lead summary #3 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202257 | Feature lead summary #4 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202258 | Feature lead summary #5 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202263 | Details on mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2202356 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2202377 | Remaining issues on the inter-UE coordination | ZTE, Sanechips |
| R1-2202483 | Inter-UE coordination for Mode 2 enhancements | Fraunhofer HHI |
| R1-2202665 | Feature lead summary #6 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2202666 | Feature lead summary #7 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.2 | Other | |
| R1-2201113 | Other aspects on SL enhancements | vivo |
| R1-2201337 | Discussion on the status of Rel-17 Sidelink enhancements | CATT, GOHIGH |
| R1-2201532 | On gNB-designated resources for inter-UE coordination and sensing in SL DRX | InterDigital, Inc. |
| R1-2202033 | Discussion on Sidelink Enhancement | Samsung |
| R1-2202264 | Additional considerations on resource allocation for power saving and inter-UE coordination | Ericsson |
| R1-2202378 | Consideration on UE-A for inter-UE coordination | ZTE, Sanechips |
| R1-2202444 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| 8.12 | Maintenance on NR Multicast and Broadcast Services | |
| R1-2202664 | Summary of email discussion on Rel-17 RRC parameters for NR MBS | Moderator (CMCC, Huawei, BBC) |
| R1-2202790 | Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| R1-2202946 | Agreements for NR MBS up to RAN1#108 | WI rapporteur (CMCC) |
| R1-2202951 | Corrections on the introduction of multicast-broadcast services in NR | Samsung |
| R1-2202955 | Corrections to NR support of multicast and broadcast services | Ericsson |
| R1-2202958 | Corrections to NR support of multicast and broadcast services | Qualcomm |
| R1-2202962 | Corrections on NR Multicast and Broadcast Services | Nokia |
| R1-2202968 | Corrections on NR Multicast and Broadcast Services in 38.212 | Huawei |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2200948 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2201006 | Remaining Issues on Group Scheduling Mechanisms for RRC_CONNECTED Ues supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2201114 | Remaining issues on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2201170 | Maintenance of Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2201257 | Discussion on remaining issues of group scheduling mechanism for RRC_CONNECTED UEs | OPPO |
| R1-2201338 | Remaining issue on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2201496 | Remaining issues on group scheduling mechanisms for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2201592 | Discussion on RAN2 LS on MBS SPS | TD Tech, Chengdu TD Tech |
| R1-2201607 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2201717 | Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2201786 | Remaining issues on MBS group scheduling mechanism for RRC_connected UEs | Apple |
| R1-2201815 | Discussion on the remaining issues on MBS group scheduling for RRC_CONNETED UEs | Spreadtrum Communications |
| R1-2201875 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2201876 | Remaining issues on group scheduling mechanisms for RRC_CONNECTED UEs | CMCC |
| R1-2201908 | Remaining Issues on Group Scheduling Mechanisms for RRC_CONNECTED UEs | NEC |
| R1-2201931 | Remaining issues on group scheduling for RRC_CONNECTED UEs | Xiaomi |
| R1-2202034 | Maintenance on group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2202079 | Remaining issues on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2202160 | Maintenance on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2202227 | Remaining issues on group scheduling mechanism for RRC_CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2202232 | Correction on group scheduling for RRC_CONNECTED UEs | ETRI |
| R1-2202331 | Corrections of MBS for RRC_CONNECTED UEs | Google Inc. |
| R1-2202349 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2202396 | Mechanisms to support MBS group scheduling for RRC_CONNECTED UEs | Ericsson |
| R1-2202580 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2202581 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2202582 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2202590 | LS on RRC parameters for NR MBS | RAN1, CMCC |
| R1-2202591 | Reply LS on MBS SPS | RAN1, CMCC |
| R1-2202641 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2202642 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2202746 | FL summary#1 on MBS broadcast reception on SCell | Moderator (Huawei) |
| R1-2202747 | FL summary#2 on MBS broadcast reception on SCell | Moderator (Huawei) |
| R1-2202821 | DRAFT LS reply on MBS broadcast reception on SCell | Moderator (Huawei) |
| R1-2202822 | LS reply on MBS broadcast reception on SCell | RAN1, Huawei |
| R1-2202827 | Summary#7 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2200949 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2201007 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2201115 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2201171 | Maintenance of Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2201258 | Remaining issues on UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2201339 | Remaining issue on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2201497 | Remaining details on HARQ-ACK feedback procedure for multicast | NTT DOCOMO, INC. |
| R1-2201595 | Open issues on reliability for NR MBS | TD Tech, Chengdu TD Tech |
| R1-2201718 | Reliability for RRC_CONNECTED UEs | Intel Corporation |
| R1-2201787 | Remaining issues on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2201816 | Discussion on the remaining issues on mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2201877 | Remaining issues on reliability improvement for RRC_CONNECTED UEs | CMCC |
| R1-2201909 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2202035 | Maintenance on mechanisms to improve reliability | Samsung |
| R1-2202080 | Remaining issues on improve multicast reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2202161 | Maintenance on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2202228 | Remaining issues on reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2202233 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED UEs | ETRI |
| R1-2202350 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2202397 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Ericsson |
| R1-2202576 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2202577 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2202578 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2202579 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2202883 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2200950 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2201008 | Remaining Issues on Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE UEs | Nokia, Nokia Shanghai Bell |
| R1-2201116 | Remaining issues on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | vivo |
| R1-2201172 | Maintenance of Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2201259 | Discussion on remaining issues of basic functions for RRC_IDLE/RRC_INACTIVE UEs | OPPO |
| R1-2201340 | Remaining issues on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | CATT |
| R1-2201498 | Remaining issues on basic functions for broadcast | NTT DOCOMO, INC. |
| R1-2201597 | Discussion on basic functions for broadcast mode | TD Tech, Chengdu TD Tech |
| R1-2201719 | Broadcast for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2201788 | Remaining issues on MBS for RRC_IDLE/RRC_INACTIVE UEs | Apple |
| R1-2201817 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | Spreadtrum Communications |
| R1-2201878 | Remaining issues on NR MBS in RRC_IDLE/RRC_INACTIVE states | CMCC |
| R1-2201932 | Remaining issues on broadcast and multicast for RRC_IDLERRC_INACTIVE UEs | Xiaomi |
| R1-2202036 | Maintenance on broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2202081 | Remaining issues on MBS broadcast reception for RRC_IDLE and INACTIVE UEs | MediaTek Inc. |
| R1-2202162 | Maintenance on group scheduling for Broadcast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2202229 | Remaining issues on basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2202351 | Basic function for broadcast/multicast | LG Electronics |
| R1-2202398 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2202548 | Feature Lead summary #1 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2202549 | Feature Lead summary #2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2202550 | Feature Lead summary #3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2202610 | DRAFT LS reply about the MBS issues | Moderator (Huawei) |
| R1-2202611 | LS reply about the MBS issues | RAN1, Huawei |
| R1-2202817 | Feature Lead summary #4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| 8.12.4 | Other | |
| R1-2201117 | Other issues for Rel-17 MBS | vivo |
| R1-2201173 | Discussion on RRC parameters of Rel-17 MBS | ZTE |
| R1-2201341 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2201598 | Discussion on typical configuration for broadcast mode | TD Tech, Chengdu TD Tech |
| R1-2201609 | Discussion on further improvements for MBS | ASUSTeK |
| R1-2201933 | Other remaining issues for MBS | Xiaomi |
| R1-2202352 | Other aspects for MBS | LG Electronics |
| R1-2202399 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| R1-2202432 | Views on overall configurations for multicast | Huawei, HiSilicon |
| 8.13 | Maintenance on NR Dynamic spectrum sharing (DSS) | |
| R1-2202791 | Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2202940 | Summary of RAN1 agreements for Rel17 NR DSS WI | WI rapporteur (Ericsson) |
| R1-2202983 | Corrections on dynamic spectrum sharing enhancements in NR | Samsung |
| R1-2202990 | Corrections on NR Dynamic Spectrum Sharing enhancements | Nokia |
| R1-2203002 | Corrections on NR dynamic spectrum sharing enhancements in 38.212 | Huawei |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2200914 | Discussion on PDCCH scheduling from Scell | Huawei, HiSilicon |
| R1-2201118 | Remaining issues on Scell scheduling Pcell | vivo |
| R1-2201174 | Maintenance of Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2201298 | Discussion on cross-carrier scheduling from SCell to PCell | OPPO |
| R1-2201499 | Remaining issues on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2201720 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2201721 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2201879 | Remaining issues on cross-carrier scheduling from SCell to PCell | CMCC |
| R1-2201935 | Remaining issues on cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2202037 | Remaining details of cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2202052 | On Cross-Carrier Scheduling from sSCell to P(S)Cell | MediaTek Inc. |
| R1-2202091 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo |
| R1-2202163 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2202221 | Maintenance of enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2202270 | Remining issues on sSCell to Pcell scheduling | Nokia, Nokia Shanghai Bell |
| R1-2202353 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2202602 | Summary#1 of Email discussion [108-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2202840 | Summary#4 of Email discussion [108-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2202906 | Summary#5 of Email discussion [108-e-NR-DSS-01] | Moderator (Ericsson) |
| 8.13.2 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2200915 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2200997 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2201119 | Remaining issues on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2201175 | Maintenance of Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2201299 | Discussion on efficient activation/de-activation for SCell | OPPO |
| R1-2201500 | Discussion on efficient activation deactivation mechanism for Scells | NTT DOCOMO, INC. |
| R1-2201936 | Remaining issues on efficient activation and de-activation mechanism for SCell in NR CA | Xiaomi |
| R1-2202164 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2202222 | Maintenance for efficient SCell activation | Ericsson |
| R1-2202271 | On RAN2 LSs to RAN1 on TRS-based SCell activation | Nokia, Nokia Shanghai Bell |
| R1-2202354 | Discussion on fast and efficient SCell activation in NR CA | LG Electronics |
| R1-2202465 | TP on stage 2 description for Rel-17 efficient Scell activation of NR CA | Huawei, HiSilicon |
| R1-2202608 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2202609 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2202703 | [Draft] LS on Stage 2 description for fast SCell activation | Moderator (Huawei) |
| R1-2202704 | LS on Stage 2 description for fast SCell activation | RAN1, Huawei |
| R1-2202705 | [Draft] Reply LS on RAN2 agreements for TRS-based Scell activation | Moderator (Huawei) |
| R1-2202706 | Reply LS on RAN2 agreements for TRS-based Scell activation | RAN1, Huawei |
| R1-2202918 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2202934 | Summary of agreements for Rel-17 feMR-DC WI | WI Rapporteur (Huawei) |
| 8.13.3 | Other | |
| R1-2201937 | Remaining issue on dynamic spectrum sharing | Xiaomi |
| R1-2202223 | Evaluation of PDCCH enhancement for DSS | Ericsson |
| R1-2202417 | Remaining issues on the efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| 8.14 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2201220 | List of IoT over NTN Rel-17 RRC parameters | Moderator (MediaTek Inc.) |
| R1-2202792 | Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Huawei) |
| R1-2202937 | List of RAN1 agreements for Rel-17 IoT NTN (Post RAN1#108-e) | WI Rapporteur (MediaTek) |
| R1-2202970 | Correction to NB-IoT and LTE-MTC over NTN | Ericsson |
| R1-2202973 | Corrections to NB-IoT/eMTC support for Non-Terrestrial Networks | Motorola Mobility |
| 8.14.1 | Enhancements to time and frequency synchronization | |
| R1-2200941 | Maintenance on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2201217 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2201219 | Summary #1 of AI 8.14.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2201275 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2201342 | Remaining issues on time and frequency synchronization enhancement for IoT over NTN | CATT |
| R1-2201559 | Discussion on enhancements to time and frequency synchronization for IOT NTN | Spreadtrum Communications |
| R1-2201587 | Remaining issues of time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201652 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2201789 | Remaining Issues of Uplink Time and Frequency Synchronization for IoT NTN | Apple |
| R1-2201808 | On time and frequency synchronization maintenance issues for IoT over NTN | Ericsson Hungary Ltd |
| R1-2201880 | Remaining issues on enhancements to time and frequency synchronization for IoT NTN | CMCC |
| R1-2201950 | Remaining issues on UL time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2202210 | Remaining issues of synchronization for NR-NTN | ZTE |
| R1-2202408 | Maintenance of IoT-NTN time and frequency synchronisation | Sony |
| R1-2202479 | Enhancements to time and frequency synchronization | Mavenir |
| R1-2202724 | Summary #2 of AI 8.14.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2202839 | Summary #3 of AI 8.14.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2202915 | Summary #4 of AI 8.14.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2202917 | RAN1 IoT NTN additions for TS 36.300 | Moderator (MediaTek) |
| R1-2202930 | Draft LS on IoT-NTN TP for TS 36.300 | Moderator (MediaTek) |
| R1-2202931 | LS on IoT-NTN TP for TS 36.300 | RAN1, MediaTek |
| 8.14.2 | Timing relationship enhancements | |
| R1-2200942 | Maintenance on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2201218 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2201276 | Discussion on timing relationship enhancements | OPPO |
| R1-2201343 | Remaining issues on timing relationship enhancement for IoT over NTN | CATT |
| R1-2201586 | Maintenance of IoT-NTN timing relationships | Sony |
| R1-2201588 | Remaining issues of timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201653 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2201790 | Remaining Issues of Timing Relationship Enhancement for IoT NTN | Apple |
| R1-2201809 | On timing relationship maintenance issues for IoT over NTN | Ericsson Hungary Ltd |
| R1-2201881 | Remaining issues on timing relationship enhancements for IoT NTN | CMCC |
| R1-2202211 | Remaining issues of timing relationship for IoT-NTN | ZTE |
| R1-2202480 | Timing relationship enhancements | Mavenir |
| R1-2202585 | FL summary 1 of AI 8.14.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2202586 | FL summary 2 of AI 8.14.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2202587 | FL summary 3 of AI 8.14.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| 8.14.3 | Other | |
| R1-2201589 | Discussion on other aspects for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201810 | Mobile IoT in the 5G future – NB-IoT and eMTC for NTN | Ericsson Hungary Ltd |
| R1-2201951 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| R1-2202425 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| 8.15 | Maintenance on New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast | |
| R1-2202793 | Session notes for 8.15 (Maintenance on New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Huawei) |
| 8.15.1 | PMCH allocation of 6/7/8 MHz and corresponding MBSFN reference signals | |
| R1-2201655 | Updates to 36.976 and 36.300 | Qualcomm Incorporated |
| R1-2202823 | Summary of 108-e-R17-LTE-5G-Bcast-01 | Moderator (Qualcomm Incorporated) |
| R1-2202824 | [DRAFT] LS on updates to 36.300 from LTE_terr_bcast_bands_part1 | Moderator (Qualcomm Incorporated) |
| R1-2202825 | LS on updates to 36.300 from LTE_terr_bcast_bands_part1 | RAN1, Qualcomm |
| R1-2202826 | Introduction of Rel-17 enhancements | Qualcomm Incorporated (Editor) |
| 8.16 | Rel-17 UE Features | |
| R1-2202447 | On support of UE feature(s) for 32 HARQ processes in Rel-17 work items | Huawei, HiSilicon |
| R1-2202858 | Summary of UE features for 32 HARQ processes | Moderator (AT&T) |
| R1-2202882 | Session Notes for 8.16 (Rel-17 UE Features) | Ad-Hoc Chair (NTT DOCOMO, INC.) |
| R1-2202923 | UE capability IE list for Rel-17 NR for existing Rel. 15/16 feature groups | Moderator (Ericsson) |
| R1-2202924 | LS on updated Rel-17 RAN1 UE features list for LTE | RAN1, NTT DOCOMO, AT&T |
| R1-2202925 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #108-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2202926 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #108-e including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2202927 | LS on updated Rel-17 RAN1 UE features list for NR | RAN1, NTT DOCOMO, AT&T |
| R1-2202928 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #108-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2202929 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #108-e including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO, INC.) |
| 8.16.1 | UE features for further enhancements on NR-MIMO | |
| R1-2200936 | Rel-17 UE features for further NR MIMO enhancements | Huawei, HiSilicon |
| R1-2201120 | Discussion on remaining issues of FeMIMO features | vivo |
| R1-2201199 | UE features for feMIMO | ZTE |
| R1-2201230 | UE features for further enhancements on NR-MIMO | OPPO |
| R1-2201344 | On UE features for Rel-17 feMIMO | CATT |
| R1-2201408 | On UE features for further enhancements on NR-MIMO | Nokia, Nokia Shanghai Bell |
| R1-2201501 | Discussion on Rel.17 FeMIMO UE features | NTT DOCOMO, INC. |
| R1-2201562 | Discussion on UE features for FeMIMO | Spreadtrum Communications |
| R1-2201574 | Discussion on Rel-17 UE feature for NR FeMIMO | LG Electronics |
| R1-2201723 | On UE features for feMIMO | Intel Corporation |
| R1-2201791 | Views on Rel-17 FeMIMO UE features | Apple |
| R1-2201882 | Discussion on UE features for FeMIMO | CMCC |
| R1-2201952 | Discussion on UE features for FeMIMO | Xiaomi |
| R1-2202038 | Views on UE features for Rel-17 NR FeMIMO | Samsung |
| R1-2202058 | UE Features for further enhancements on NR MIMO | MediaTek Inc. |
| R1-2202092 | Discussion on UE features for FeMIMO | Lenovo |
| R1-2202165 | Discussion on FeMIMO UE features | Qualcomm Incorporated |
| R1-2202282 | Discussion on UE features for FeMIMO | Ericsson |
| R1-2202554 | Proposal on UE Feature for Rel-17 Unified TCI | Samsung |
| R1-2202850 | Summary of UE features for further enhancements on NR-MIMO | Moderator (AT&T) |
| R1-2202859 | Session Notes for Agenda Item 8.16.1 | Ad-Hoc Chair (AT&T) |
| 8.16.2 | UE features for supporting NR from 52.6 GHz to 71 GHz | |
| R1-2200958 | Rel-17 UE features for extension to 71 GHz | Huawei, HiSilicon |
| R1-2201121 | Discussions on UE features for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2201302 | Discussion on UE features for FR2-2 | OPPO |
| R1-2201395 | Discussion on UE features for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2201409 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2201502 | Views on Rel-17 UE features for supporting NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2201727 | Discussion on UE capability for extending NR up to 71 GHz | Intel Corporation |
| R1-2201741 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2201792 | Views on Rel-17 Beyond 52.6 GHz UE features | Apple |
| R1-2202039 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2202075 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | MediaTek Inc. |
| R1-2202166 | UE features for NR from 52.6 Ghz to 71 Ghz | Qualcomm Incorporated |
| R1-2202355 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2202851 | Summary of UE features for supporting NR from 52.6 GHz to 71 GHz | Moderator (AT&T) |
| R1-2202860 | Session Notes for Agenda Item 8.16.2 | Ad-Hoc Chair (AT&T) |
| 8.16.3 | UE features for enhanced IIoT and and URLLC | |
| R1-2200962 | Rel-17 UE features for enhanced IIoT/URLLC | Huawei, HiSilicon |
| R1-2201005 | Rel-17 UE Features for IIoT/URLLC | Ericsson |
| R1-2201025 | UE features for IIoT and URLLC | New H3C Technologies Co., Ltd. |
| R1-2201122 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2201176 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2201301 | Discussion on UE features for IIoT and URLLC | OPPO |
| R1-2201346 | Discussion on UE features of enhanced IIoT and URLLC | CATT |
| R1-2201410 | On UE features for enhanced IIoT and and URLLC | Nokia, Nokia Shanghai Bell |
| R1-2201503 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2201514 | Summary on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2201560 | UE features for enhanced IIoT and and URLLC | Spreadtrum Communications |
| R1-2201728 | Discussion on UE capability for enhanced IIoT and URLLC | Intel Corporation |
| R1-2201793 | Views on UE features for enhanced IIoT and and URLLC | Apple |
| R1-2202040 | UE features for enhanced IIoT and URLLC | Samsung |
| R1-2202083 | Views on UE features for enhanced IIoT and URLLC | MediaTek Inc. |
| R1-2202167 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| 8.16.4 | UE features for NR NTN | |
| R1-2200940 | Rel-17 UE features for NR NTN | Huawei, HiSilicon |
| R1-2201222 | UE features for NR NTN | MediaTek Inc. |
| R1-2201303 | Discussion on UE features for NTN-NR | OPPO |
| R1-2201411 | On UE features for NR NTN | Nokia, Nokia Shanghai Bell |
| R1-2201504 | Discussion on Rel.17 UE features for NR NTN | NTT DOCOMO, INC. |
| R1-2201729 | On UE features for NR NTN | Intel Corporation |
| R1-2201794 | Views on Rel-17 NR NTN UE Features | Apple |
| R1-2201807 | On UE features for NR NTN | Ericsson Hungary Ltd |
| R1-2202041 | UE features for NR NTN | Samsung |
| R1-2202168 | UE features for NR NTN | Qualcomm Incorporated |
| R1-2202212 | Discussion on UE feature for NR-NTN | ZTE |
| R1-2202290 | Discussion on Rel-17 UE feature for NR NTN | LG Electronics |
| R1-2202852 | Summary of UE features for NR NTN | Moderator (AT&T) |
| R1-2202861 | Session Notes for Agenda Item 8.16.4 | Ad-Hoc Chair (AT&T) |
| 8.16.5 | UE features for NR positioning enhancements | |
| R1-2200925 | Remaining issues of Rel-17 positioning UE feature | Huawei, HiSilicon |
| R1-2201123 | Discussion on UE features for NR positioning enhancements | vivo |
| R1-2201200 | UE features for NR positioning enhancements | ZTE |
| R1-2201245 | UE features for NR positioning enhancements | OPPO |
| R1-2201347 | Remaining issues on Rel-17 UE features for NR Positioning enhancements | CATT |
| R1-2201412 | On UE features for NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201447 | UE features for Rel-17 NR positioning enhancements | China Telecom |
| R1-2201505 | Discussion on Rel-17 UE features for NR positioning enhancements | NTT DOCOMO, INC. |
| R1-2201730 | UE features for Rel.17 NR positioning enhancements | Intel Corporation |
| R1-2201795 | Views on UE features for NR positioning enhancements | Apple |
| R1-2201883 | Discussion on UE features for NR positioning enhancement | CMCC |
| R1-2201953 | Discussion on UE features for NR Positioning Enhancements | Xiaomi |
| R1-2202042 | UE features for NR positioning enhancements | Samsung |
| R1-2202169 | UE features for NR positioning enhancements | Qualcomm Incorporated |
| R1-2202388 | Views on NR positioning enhancements UE features | Ericsson |
| R1-2202853 | Summary of UE features for NR positioning enhancements | Moderator (AT&T) |
| R1-2202862 | Session Notes for Agenda Item 8.16.5 | Ad-Hoc Chair (AT&T) |
| 8.16.6 | UE features for REDCAP | |
| R1-2200919 | Rel-17 UE features for RedCap | Huawei, HiSilicon |
| R1-2200986 | Discussions of UE features for RedCap | FUTUREWEI |
| R1-2201124 | Discussion on UE feature for NR REDCAP | vivo, Guangdong Genius |
| R1-2201139 | Discussion on RedCap UE features | ZTE, Sanechips |
| R1-2201290 | Rel-17 RedCap UE features | OPPO |
| R1-2201348 | Discussion on Rel-17 UE features for RedCap | CATT |
| R1-2201413 | On UE features for REDCAP | Nokia, Nokia Shanghai Bell |
| R1-2201506 | Discussion on UE features for RedCap | NTT DOCOMO, INC. |
| R1-2201515 | Summary on UE features for REDCAP | Moderator (NTT DOCOMO, INC.) |
| R1-2201606 | Discussion on UE feature for RedCap | NEC |
| R1-2201672 | UE features for RedCap | Ericsson |
| R1-2201731 | On UE features for Rel-17 RedCap | Intel Corporation |
| R1-2201796 | UE features for RedCap | Apple |
| R1-2201884 | Discussion on UE features for RedCap | CMCC |
| R1-2201954 | Discussion on UE features on RedCap | Xiaomi |
| R1-2202043 | UE feature for RedCap | Samsung |
| R1-2202062 | UE features for REDCAP | MediaTek Inc. |
| R1-2202170 | UE features for RedCap | Qualcomm Incorporated |
| 8.16.7 | UE features for UE power saving enhancements | |
| R1-2200947 | Rel-17 UE features for UE power saving enhancements | Huawei, HiSilicon |
| R1-2201125 | Discussion on UE features for UE power saving enhancements | vivo |
| R1-2201134 | Discussion on UE feature for UE power saving enhancements | ZTE, Sanechips |
| R1-2201288 | Rel-17 UE Power Saving features | OPPO |
| R1-2201349 | Discussion on UE feature of UE Power saving enhancements for NR | CATT |
| R1-2201414 | On UE features for UE power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201507 | Discussion on Rel-17 UE features for UE power saving | NTT DOCOMO, INC. |
| R1-2201516 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2201732 | Discussion on UE features related to UE Power Saving | Intel Corporation |
| R1-2201797 | Views on UE features for Rel-17 UE power saving | Apple |
| R1-2201885 | Discussion on UE features for UE power saving enhancements | CMCC |
| R1-2202044 | UE features for UE power saving enhancements | Samsung |
| R1-2202053 | On UE features for UE power saving enhancements | MediaTek Inc. |
| R1-2202171 | UE features for UE power saving enhancements | Qualcomm Incorporated |
| R1-2202224 | UE features for UEPS | Ericsson |
| 8.16.8 | UE features for NR coverage enhancement | |
| R1-2200971 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2201126 | Discussion on UE features for NR coverage enhancement | vivo |
| R1-2201177 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2201289 | Rel-17 Coverage Enhancement UE features | OPPO |
| R1-2201350 | Discussion on Rel-17 UE features for NR coverage enhancement | CATT |
| R1-2201415 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2201448 | UE features for Rel-17 NR coverage enhancements | China Telecom |
| R1-2201508 | Discussion on Rel.17 UE features for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2201517 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2201561 | UE features for NR coverage enhancement | Spreadtrum Communications |
| R1-2201733 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2201798 | Views on Rel-17 Coverage Enhancement UE Features | Apple |
| R1-2201886 | Discussion on Rel.17 UE features for NR coverage enhancement | CMCC |
| R1-2201911 | UE features for NR coverage enhancement | Xiaomi |
| R1-2201967 | UE Features for NR Coverage Enhancement | Ericsson |
| R1-2202045 | UE features for NR coverage enhancement | Samsung |
| R1-2202087 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| R1-2202172 | UE Features for Coverage Enhancements | Qualcomm Incorporated |
| R1-2202203 | UE feature for Rel-17 coverage enhancement | Sharp |
| 8.16.9 | UE features for NB-IoT and LTE-MTC enhancements | |
| R1-2200978 | Rel-17 UE features for NB-IoT and LTE-MTC enhancements | Huawei, HiSilicon |
| R1-2201140 | Discussion on LTE-M and NB-IoT UE features | ZTE, Sanechips |
| R1-2201416 | On UE features for NB-IoT and LTE-MTC enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201509 | Discussion on UE features for NB-IoT and LTE-MTC enhancements | NTT DOCOMO, INC. |
| R1-2201518 | Summary on UE features for NB-IoT and LTE-MTC enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2202173 | UE features for NB-IoT and LTE-MTC enhancements | Qualcomm Incorporated |
| R1-2202279 | On UE features for NB-IoT and LTE-MTC enhancements | Ericsson |
| R1-2202892 | [DRAFT] LS on UE capability for 16QAM for NB-IoT | Qualcomm |
| R1-2202893 | LS on UE capability for 16QAM for NB-IoT | RAN1, Qualcomm |
| 8.16.10 | UE features for IAB enhancements | |
| R1-2200928 | Rel-17 UE features for IAB | Huawei, HiSilicon |
| R1-2201417 | On UE features for IAB enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201459 | Discussion on NR Rel-17 IAB MT Features | ZTE, Sanechips |
| R1-2201528 | UE features for NR IAB | Samsung |
| R1-2201724 | UE features for IAB | Intel Corporation |
| R1-2202174 | UE features for IAB enhancements | Qualcomm Incorporated |
| R1-2202405 | UE features for enhanced IAB | Ericsson |
| R1-2202854 | Summary of UE features for IAB enhancements | Moderator (AT&T) |
| 8.16.11 | UE features for NR sidelink enhancement | |
| R1-2200965 | Rel-17 UE features for NR sidelink enhancement | Huawei, HiSilicon |
| R1-2200984 | UE features for NR sidelink enhancement | FUTUREWEI |
| R1-2201127 | UE features for NR sidelink enhancement | vivo |
| R1-2201256 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2201345 | Remaining issues on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2201418 | On UE features for NR sidelink enhancement | Nokia, Nokia Shanghai Bell |
| R1-2201510 | Discussion on Rel.17 UE features for NR SL enhancement | NTT DOCOMO, INC. |
| R1-2201519 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2201704 | UE features for Rel.17 NR sidelink enhancements | Intel Corporation |
| R1-2201799 | Views on Rel-17 NR Sidelink UE Features | Apple |
| R1-2201887 | Discussion on UE features for NR sidelink enhancement | CMCC |
| R1-2201930 | Discussion on Rel-17 UE features on sidelink enhancement | Xiaomi |
| R1-2202046 | On UE features for NR sidelink enhancement | Samsung |
| R1-2202064 | UE features for NR sidelink enhancements | MediaTek Inc. |
| R1-2202175 | UE Features for Sidelink Enhancements | Qualcomm Incorporated |
| R1-2202259 | Discussion on UE features for NR sidelink enhancement | LG Electronics |
| R1-2202265 | UE features for NR sidelink enhancements | Ericsson |
| R1-2202381 | Discussion on UE features for NR sidelink enhancement | ZTE, Sanechips |
| 8.16.12 | UE features for NR MBS | |
| R1-2200951 | Rel-17 UE features for NR MBS | Huawei, HiSilicon |
| R1-2201128 | Discussion on UE features for MBS | vivo |
| R1-2201178 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2201260 | Discussion on UE features for NR MBS | OPPO |
| R1-2201419 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2201511 | Discussion on Rel-17 UE features for NR MBS | NTT DOCOMO, INC. |
| R1-2201520 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2201722 | UE Features for NR MBS | Intel Corporation |
| R1-2201800 | Views on Rel-17 MBS UE Features | Apple |
| R1-2201818 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2201888 | Discussion on UE features for NR MBS | CMCC |
| R1-2201934 | Discussion on UE features for NR MBS | Xiaomi |
| R1-2202047 | UE features for NR MBS | Samsung |
| R1-2202082 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2202176 | UE features for MBS | Qualcomm Incorporated |
| R1-2202395 | views on NR MBS UE features | Ericsson |
| 8.16.13 | UE features for DSS | |
| R1-2200916 | Rel-17 UE features for DSS and MR-DC | Huawei, HiSilicon |
| R1-2201129 | Discussion on UE features for DSS | vivo |
| R1-2201179 | Discussion on Rel-17 UE features for DSS | ZTE |
| R1-2201420 | On UE features for DSS and LTE NR DC enhancements | Nokia, Nokia Shanghai Bell |
| R1-2201725 | UE features for DSS | Intel Corporation |
| R1-2201801 | Views on Rel-17 DSS UE features | Apple |
| R1-2201889 | Discussion on UE features for DSS | CMCC |
| R1-2201938 | Discussion on UE features for NR DSS | Xiaomi |
| R1-2202048 | UE features for DSS | Samsung |
| R1-2202054 | On UE features for DSS | MediaTek Inc. |
| R1-2202177 | UE features for DSS and LTE_NR_DC_enh2 | Qualcomm Incorporated |
| R1-2202225 | UE features for DSS and CA enhancements | Ericsson |
| R1-2202855 | Summary of UE features for DSS | Moderator (AT&T) |
| R1-2202863 | Session Notes for Agenda Item 8.16.13 | Ad-Hoc Chair (AT&T) |
| 8.16.14 | UE features for IoT over NTN | |
| R1-2200943 | Rel-17 UE features for IoT over NTN | Huawei, HiSilicon |
| R1-2201221 | UE features for IoT over NTN | MediaTek Inc. |
| R1-2201304 | Discussion on UE features for NTN-IoT | OPPO |
| R1-2201421 | On UE features for IoT over NTN | Nokia, Nokia Shanghai Bell |
| R1-2201726 | On UE features for IOT over NTN | Intel Corporation |
| R1-2201802 | Views on Rel-17 IoT over NTN UE Features | Apple |
| R1-2201811 | On UE features for IoT over NTN | Ericsson Hungary Ltd |
| R1-2202178 | UE features for IoT over NTN | Qualcomm Incorporated |
| R1-2202213 | Discussion on UE feature for IoT-NTN | ZTE |
| R1-2202856 | Summary of UE features for IoT over NTN | Moderator (AT&T) |
| R1-2202864 | Session Notes for Agenda Item 8.16.14 | Ad-Hoc Chair (AT&T) |
| 8.16.15 | UE features for LTE based 5G terrestrial broadcast | |
| R1-2200979 | Rel-17 UE features for LTE based 5G terrestrial broadcast | Huawei, HiSilicon |
| R1-2201180 | Discussion on Rel-17 UE features for LTE based 5G terrestrial broadcast | ZTE |
| R1-2201422 | On UE features for LTE based 5G terrestrial broadcast | Nokia, Nokia Shanghai Bell |
| R1-2201512 | Discussion on UE features for LTE based 5G terrestrial broadcast | NTT DOCOMO, INC. |
| R1-2201521 | Summary on UE features for LTE based 5G terrestrial broadcast | Moderator (NTT DOCOMO, INC.) |
| R1-2202179 | UE features for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| 8.16.16 | UE features for DL 1024QAM for NR FR1 | |
| R1-2201423 | On UE features for DL 1024QAM for NR FR1 | Nokia, Nokia Shanghai Bell |
| R1-2202226 | UE features for DL 1024-QAM | Ericsson |
| R1-2202857 | Summary of UE features for DL 1024QAM for NR FR1 | Moderator (AT&T) |
| 8.16.17 | Other | |
| R1-2201181 | Discussion on other Rel-17 UE features | ZTE |
| R1-2201231 | Discussion on Rel-17 UE feature for Tx Switching enhancement | OPPO |
| R1-2201424 | On Remaining Rel-17 UE features | Nokia, Nokia Shanghai Bell |
| R1-2201449 | UE features for Rel-17 Tx switching | China Telecom |
| R1-2201513 | Discussion on other UE feature related discussions | NTT DOCOMO, INC. |
| R1-2201522 | Summary on other UE feature related discussions | Moderator (NTT DOCOMO, INC.) |
| R1-2201803 | Rel-17 UE features on cross PUCCH group CSI report | Apple |
| R1-2202055 | On UE features for others | MediaTek Inc. |
| R1-2202181 | UE features for Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2202471 | Rel-17 UE features for UL Tx switching | Huawei, HiSilicon |
| 8.17 | Other | |
| R1-2201192 | Initial views on Rel-18 MIMO evolution | ZTE |
| R1-2201399 | Use cases and applications on Carrier Phase Based Positioning for NR | Locaila , Dankook Univ. |
| R1-2201895 | Remaining issues of DL 1024QAM for NR FR1 | ZTE, Sanechips |
| R1-2202071 | Discussion on Rel-18 network energy savings | MediaTek Inc. |
| R1-2202416 | Selected Rel-18 MIMO Evolution Topics | Ericsson |
| R1-2202988 | Corrections on further Multi-RAT Dual-Connectivity enhancements | Nokia |
| R1-2202989 | Corrections on DL 1024QAM for NR FR1 | Nokia |