| 2 | Approval of Agenda | |
|---|---|---|
| R1-2005200 | Draft Agenda of RAN1#102-e meeting | RAN1 Chair |
| R1-2007036 | Additional Guidelines for RAN1#102 e-Meeting Management | RAN1 Chair |
| R1-2007037 | RAN1#102-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| 3 | Highlights from RAN plenary | |
| R1-2005202 | Highlights from RAN#88-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2005201 | Report of RAN1#101-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2005203 | LS on Detail MIMO MAC CE operations | RAN2, Samsung |
| R1-2005204 | LS to RAN1 on signalling SFN bits for random access response | RAN2, Ericsson |
| R1-2005205 | LS reply on PUR transmission for NB-IoT/eMTC | RAN2, Ericsson |
| R1-2005206 | LS to RAN1 on physical layer related agreements | RAN2, LG Electronics |
| R1-2005207 | LS on capability bits for E-CID measurements | RAN2, Huawei |
| R1-2005208 | LS on UE capability xDD differentiation for SUL/SDL bands | RAN2, Samsung |
| R1-2005209 | LS on NR SRS carrier switching | RAN2, Qualcomm |
| R1-2005210 | Reply LS on DCP | RAN2, Huawei |
| R1-2005211 | LS on power sharing for LTE Mobility Enhancements | RAN2, Ericsson |
| R1-2005212 | Reply LS on XDD-FRX Differentiation | RAN2, Qualcomm |
| R1-2005213 | LS reply to RAN4 on UE declaring beam failure due to LBT failures during active TCI switching | RAN2, Ericsson |
| R1-2005214 | Reply LS on inter-frequency measurement without gap | RAN2, Huawei |
| R1-2005215 | Reply LS on SCell dormancy requirement scope | RAN2, Ericsson |
| R1-2005216 | LS Reply on UL RTOA reference time | RAN3, Ericsson |
| R1-2005217 | Reply LS on Aperiodic SRS | RAN3, Intel |
| R1-2005218 | Response LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN3, ZTE |
| R1-2005219 | LS on inter-frequency measurement requirement without MG | RAN4, Huawei |
| R1-2005220 | LS on Clarification on UE behavior after receiving the MAC CE deactivation command for semi-persistent CSI reporting in NR-U | RAN4, Nokia |
| R1-2005221 | LS on RAN4 IAB-MT feature list agreement | RAN4, Qualcomm |
| R1-2005222 | LS on intra/inter-frequency measurement for NR positioning | RAN4, Huawei |
| R1-2005223 | Reply LS to RAN2 on UL-SL Prioritization | RAN4, Futurewei |
| R1-2005224 | LS on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | RAN4, Huawei |
| R1-2005225 | LS on Rel-16 RAN4 UE features lists for NR and LTE | RAN4, NTT DOCOMO |
| R1-2005226 | Reply LS to RAN2 on dormant BWP | RAN4, Futurewei |
| R1-2005227 | LS on measurement gaps for NR positioning | RAN4, Ericsson |
| R1-2005228 | Response LS on criterion of pathloss measurement failure for power control of SRS for positioning | RAN4, Ericsson |
| R1-2005229 | LS on CSI-RS based intra-frequency and inter-frequency Measurement definition | RAN4, CATT |
| R1-2005230 | LS on impact of NTA offset on UE Rx-Tx time difference measurement | RAN4, Ericsson |
| R1-2005231 | LS on Sidelink Positioning for advanced V2X applications | SAE AA TC, AT&T, LG Electronics |
| R1-2005232 | Information regarding Harmonised Standard EN 303 687 (license-exempt 6 GHz operation) | ETSI BRAN TC, Ericsson |
| R1-2005315 | Discussion of RAN4 LS on UL-SL prioritization | ZTE, Sanechips |
| R1-2005324 | Draft reply on LS on Detail MIMO MAC CE operations | vivo |
| R1-2005325 | Draft reply on LS on clarification of transparent diversity feasibility | vivo |
| R1-2005326 | Draft reply on LS on Clarification on UE behavior after receiving the MAC CE deactivation command for semi-persistent CSI reporting in NR-U | vivo |
| R1-2005466 | Draft reply LS on NR SRS carrier switching | ZTE |
| R1-2005491 | Draft reply LS on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | ZTE |
| R1-2005492 | Draft reply LS on detail MIMO MAC CE operations | ZTE |
| R1-2005505 | Discussion on reply LS on DCP | vivo |
| R1-2005518 | Draft reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | ZTE |
| R1-2005553 | Discussion for NR SRS carrier switching on SUL | ZTE |
| R1-2005649 | Discussion on the LS from RAN2 on physical layer related agreements | CATT |
| R1-2005650 | Draft reply LS to RAN2 on MIMO MAC CE operations | CATT |
| R1-2005651 | Draft reply LS to RAN4 on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | CATT |
| R1-2005652 | Draft reply LS to RAN2 on NR SRS carrier switching | CATT |
| R1-2005653 | Draft reply LS to RAN3 on inter-gNB exchange of SRS configuration | CATT |
| R1-2005654 | Discussion on NR SRS carrier switching on SUL carrier | CATT |
| R1-2005655 | Discussion on signaling SFN bits for random access response | CATT |
| R1-2005818 | [Draft] Reply LS on Detail MIMO MAC CE operations | Lenovo, Motorola Mobility |
| R1-2005994 | Discussion on LS on Detail MIMO MAC CE operations | OPPO |
| R1-2005995 | Discussion on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | OPPO |
| R1-2006001 | Discussion on reply LS for maximum data rate calculation for NR sidelink | OPPO |
| R1-2006077 | [Draft] Reply LS on remaining eMIMO issues | Samsung |
| R1-2006078 | [Draft] Reply LS on NR SRS carrier switching | Samsung |
| R1-2006079 | [Draft] Reply LS on CSI-RS only beam correspondence | Samsung |
| R1-2006080 | [Draft] Reply LS on clarification of transparent diversity feasibility | Samsung |
| R1-2006081 | [Draft] Reply LS on Rel-16 UE feature lists | Samsung |
| R1-2006082 | [Draft] Reply LS on UE capability xDD differentiation for SUL/SDL bands | Samsung |
| R1-2006083 | [Draft] Reply LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | Samsung |
| R1-2006185 | On LTE DAPS power coordination | Qualcomm Incorporated |
| R1-2006334 | [DRAFT] Reply LS on UL PC for NR-DC | ZTE |
| R1-2006335 | [DRAFT] Reply LS on UE capability xDD differentiation for SUL/SDL bands | ZTE |
| R1-2006336 | [DRAFT] Reply LS on power sharing for LTE mobility enhancements | ZTE |
| R1-2006337 | Discussion on uplink power sharing for LTE mobility enhancements | ZTE |
| R1-2006432 | [Draft] Reply LS on SL UE capability | Ericsson |
| R1-2006450 | Draft reply to the LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | Nokia, Nokia Shanghai-Bell |
| R1-2006451 | On inter-gNB exchange of SRS configuration for CLI measurement. | Nokia, Nokia Shanghai-Bell |
| R1-2006590 | Draft reply LS on Detail MIMO MAC CE operations | LG Electronics |
| R1-2006591 | Draft reply LS on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | LG Electronics |
| R1-2006617 | Draft LS reply on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | Ericsson |
| R1-2006647 | Discussion on LS to RAN1 on signaling SFN bits for random access response | LG Electronics |
| R1-2006679 | Draft LS response on Detail MIMO MAC CE operations | Ericsson |
| R1-2006757 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2006758 | Draft reply LS on updated Rel-16 LTE and NR parameter lists | Qualcomm Incorporated |
| R1-2006759 | Discussion of the LS about cancelled ACK for MAC deactivation | Qualcomm Incorporated |
| R1-2006925 | Power sharing for LTE mobility enhancements | Huawei, HiSilicon |
| R1-2006926 | [DRAFT] LS reply to RAN2 on power sharing for LTE mobility enhancements | Huawei, HiSilicon |
| R1-2006931 | [Draft] Reply LS on E-CID measurement capability | Huawei, HiSilicon |
| R1-2006932 | [Draft] Reply LS on AP SRS support | Huawei, HiSilicon |
| R1-2006934 | Draft LS reply on UE capability xDD differentiation for SUL/SDL bands | Huawei, HiSilicon |
| R1-2006935 | Discussion on UE capability xDD differentiation for SUL/SDL bands | Huawei, HiSilicon |
| R1-2006937 | Discussion on URLLC and IIoT performance evaluation in response to 5G-ACIA | Huawei, HiSilicon |
| R1-2006938 | Draft reply LS on feasibility of UL FPT modes and transparent TxD for certain UE implementations | Huawei, HiSilicon |
| R1-2006939 | [Draft] Reply LS on CSI-RS only beam correspondence | Huawei, HiSilicon |
| R1-2006940 | Discussion on UE behavior after receiving the MAC CE deactivation command for semi-persistent CSI reporting in NR-U | Huawei, HiSilicon |
| R1-2006943 | Draft reply LS on detail MIMO MAC CE operations | Huawei, HiSilicon |
| R1-2006944 | Discussion on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | Huawei, HiSilicon |
| R1-2006945 | Discussion on NR SRS carrier switching | Huawei, HiSilicon |
| R1-2006952 | LS on CSI-RS only beam correspondence | RAN4, Huawei |
| R1-2006953 | LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation | 5G Alliance for Connected Industries and Automation (5G-ACIA), Bosch, Ericsson |
| R1-2007044 | [102-e-LS-AI5-04] Discussion on NR SRS carrier switching | Moderator (Qualcomm Incorporated) |
| R1-2007045 | Reply LS on Rel-16 UE feature lists | RAN2, Intel |
| R1-2007050 | RAN1#102-e preparation phase on LSs | RAN1 Chair |
| R1-2007183 | LS on Rel-16 RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2007185 | Summary of email discussion [102-e-LS-AI5-07] on 5G-ACIA LS | Moderator (Ericsson) |
| R1-2007186 | LS on RAN1 discussion on simulations for 5G-ACIA | RAN1, Ericsson |
| R1-2007187 | Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN1, ZTE |
| R1-2007197 | Reply LS on remaining eMIMO issues | RAN1, Samsung |
| R1-2007202 | Summary of e-mail discussion on the LS for remaining eMIMO issues | Moderator (Samsung) |
| R1-2007227 | Reply LS on Rel-16 RAN1 UE feature lists for 5G V2X service | RAN4, LG Electronics |
| R1-2007266 | LS on UE capability | RAN2, OPPO |
| R1-2007293 | Summary of [102-e-LS-AI5-05] discussions for a reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | Moderator (ZTE) |
| R1-2007314 | Summary of [102-e-LS-AI5-03] whether reply LS to R1-2005208 is needed or not | Moderator (Samsung) |
| R1-2007320 | LS on additional DC location reporting for intra-band UL CA | RAN4, Qualcomm |
| R1-2007321 | [Draft] LS reply on NR SRS carrier switching | Qualcomm |
| R1-2007395 | LS reply on NR SRS carrier switching | RAN1, Qualcomm |
| R1-2007420 | LS response on power sharing for LTE mobility enhancements | RAN1, Ericsson |
| R1-2007427 | Email discussion on CSI-RS only beam correspondence | Moderator (Huawei) |
| R1-2007428 | Reply LS on CSI-RS only beam correspondence | RAN1, Huawei |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2005996 | Discussion on Tx Switching between Two Uplink Carriers | OPPO |
| R1-2006333 | Remaining Maintenance Issues of UL Tx Switching | ZTE |
| R1-2006582 | Summary of uplink Tx switching | China Telecommunications |
| R1-2006661 | Maintenance for UL Tx Switching | Ericsson |
| R1-2006760 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2006933 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2006978 | Summary#2 of uplink Tx switching | China Telecommunications |
| R1-2007402 | [102-e-LS-TxSwitching-01] Email discussion/approval on maintenance of uplink Tx switching thread #1 | Moderator (China Telecom) |
| R1-2007403 | [102-e-LS-TxSwitching-02] Email discussion/approval on maintenance of uplink Tx switching thread #2 | Moderator (China Telecom) |
| R1-2007410 | Correction on uplink Tx switching | Moderator (China Telecom) |
| 5.2 | RAN1 Aspects for RF Requirement Enhancements for FR2 | |
| R1-2005443 | Enhancement on FR2 MPE mitigation | ZTE |
| 6.1 | Maintenance of E-UTRA Releases 8 – 15 | |
| R1-2005656 | Correction on semi-open-loop | CATT |
| R1-2005923 | Correction on CFI related parameter names alignment between TS 36.331 and TS 36.213 | Motorola Mobility, Lenovo, Qualcomm Incorporated |
| R1-2006186 | Applicability of fields to CSS in eMTC | Qualcomm Incorporated |
| R1-2006550 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 | Sharp |
| R1-2006923 | Correction on PDSCH starting position for BL/CE UEs and starting symbol for MPDCCH of an MBSFN subframe | Huawei, HiSilicon |
| R1-2006924 | Correction on SPDCCH monitoring of an MBSFN subframe | Huawei, HiSilicon |
| R1-2007000 | RAN1#102-e preparation phase on Maintenance of E-UTRA Releases 8-15 | Ad-Hoc Chair (Ericsson) |
| R1-2007127 | Correction on semi-open-loop | CATT |
| R1-2007128 | Correction on semi-open-loop | CATT |
| R1-2007129 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 | Sharp |
| R1-2007130 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 | Sharp |
| R1-2007131 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 | Sharp |
| R1-2007164 | Correction on CFI related parameter names alignment between TS 36.331 and TS 36.213 | Motorola Mobility, Lenovo, Qualcomm Incorporated |
| R1-2007165 | Correction on CFI related parameter names alignment between TS 36.331 and TS 36.213 | Motorola Mobility, Lenovo, Qualcomm Incorporated |
| R1-2007166 | Correction on SPDCCH monitoring of an MBSFN subframe | Huawei, HiSilicon, Qualcomm |
| R1-2007167 | Correction on SPDCCH monitoring of an MBSFN subframe | Huawei, HiSilicon, Qualcomm |
| R1-2007230 | Applicability of fields to CSS in eMTC | Qualcomm Incorporated |
| R1-2007231 | Applicability of fields to CSS in eMTC | Qualcomm Incorporated |
| R1-2007232 | Applicability of fields to CSS in eMTC | Qualcomm Incorporated |
| R1-2007371 | Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) | Ad-Hoc Chair (Ericsson) |
| 6.2 | Maintenance of E-UTRA Release 16 | |
| R1-2007372 | Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) | Ad-hoc Chair (Samsung) |
| 6.2.1 | Maintenance of Additional MTC Enhancements | |
| R1-2005469 | Remaining issues for transmission in preconfigured UL resources for MTC | ZTE |
| R1-2005470 | Remaining issues on scheduling enhancement for MTC | ZTE |
| R1-2005503 | Clarification on Resource reservation filed in LTE-MTC SPS Release DCI | ZTE |
| R1-2005555 | PUR maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2005815 | Corrections regarding RAN2 LS reply on PUR | Huawei, HiSilicon |
| R1-2006187 | Maintenance on PUR | Qualcomm Incorporated |
| R1-2006188 | Maintenance on multi-TB scheduling | Qualcomm Incorporated |
| R1-2006417 | Corrections on transmission in preconfigured UL resources for eMTC | Huawei, HiSilicon |
| R1-2006418 | Corrections on multi-TB scheduling for eMTC | Huawei, HiSilicon |
| R1-2006471 | Multi-TB maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2007295 | Feature lead email summary [102-e-LTE-eMTC5-01] | Moderator (Sierra Wireless) |
| R1-2007296 | Feature lead email summary [102-e-LTE-eMTC5-02] | Moderator (Sierra Wireless) |
| R1-2007297 | Clarifications for the PUR UE-specific search space | Moderator (Sierra Wireless) |
| R1-2007298 | Corrections on PUR collision handling | Moderator (Sierra Wireless) |
| R1-2007299 | Add PUR allocation procedures to UL resource allocation type 5 | Moderator (Sierra Wireless) |
| R1-2007300 | Clarifications for PUR Repetition Adjustment | Moderator (Sierra Wireless) |
| R1-2007304 | FL summary for Multi-TB early termination aspects for LTE-MTC | Moderator (Ericsson) |
| R1-2007305 | FL summary for Multi-TB minor corrections for LTE-MTC | Moderator (Ericsson) |
| R1-2007306 | FL summary for Resource reservation field in SPS release DCI in LTE-MTC and NB-IoT | Moderator (Ericsson) |
| R1-2007307 | Number of HARQ processes in multi-TB scheduling in CE mode B in TDD in LTE-MTC | Moderator (Ericsson) |
| R1-2007308 | Multi-TB scheduling and PUR spanning PUSCH transmission in LTE-MTC | Moderator (Ericsson) |
| R1-2007309 | Missing 'else' in RV determination in UL multi-TB scheduling in LTE-MTC | Moderator (Ericsson) |
| 6.2.2 | Maintenance of Additional Enhancements for NB-IoT | |
| R1-2005471 | Remaining issues for transmission in preconfigured UL resources for NB-IoT | ZTE |
| R1-2005472 | Remaining issues on scheduling enhancement for NB-IoT | ZTE |
| R1-2005504 | Clarification on Resource reservation filed in NB-IoT SPS Release DCI | ZTE |
| R1-2005556 | PUR maintenance issues for Rel-16 NB-IoT | Ericsson |
| R1-2005816 | Corrections regarding RAN2 LS reply on PUR | Huawei, HiSilicon |
| R1-2006189 | Maintenance on PUR | Qualcomm Incorporated |
| R1-2006419 | Corrections on transmission in preconfigured UL resources for NB-IoT | Huawei, HiSilicon |
| R1-2006420 | Corrections on higher layer parameters for additional NB-IoT enhancements | Huawei, HiSilicon |
| R1-2007026 | TP on terms and higher layer parameters for NB-IoT | Moderator (Huawei) |
| R1-2007027 | TP on PUR-RNTI for NB-IoT | Moderator (Huawei) |
| R1-2007155 | Feature lead summary #1 on [102-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| R1-2007156 | Text Proposal for Issue#1 in [102-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| R1-2007157 | Text Proposal for Issue#2 in [102-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| R1-2007158 | Feature lead summary #1 on [102-e-LTE-NB_IoTenh3-02] | Moderator (Huawei) |
| R1-2007159 | Text Proposal for Issue#4 in [102-e-LTE-NB_IoTenh3-02] | Moderator (Huawei) |
| R1-2007211 | Corrections on L1 adjustment on the NPUSCH repetition number | Moderator (Huawei) |
| R1-2007212 | Corrections on PUR collision handling | Moderator (Huawei) |
| R1-2007213 | Corrections on NPDSCH/NPDCCH interference randomization | Moderator (Huawei) |
| R1-2007270 | Feature summary on [102-e-LTE-NB_IoTenh3-03] | Moderator (Huawei) |
| R1-2007271 | Correction on configuration of multiTB-Gap | Moderator (Huawei) |
| R1-2007272 | Correction on NPDSCH | Moderator (Huawei) |
| R1-2007405 | Correction on terms and higher layer parameters for NB-IoT in 36.211 | Moderator (Huawei) |
| R1-2007406 | Correction on terms and higher layer parameters for NB-IoT in 36.212 | Moderator (Huawei) |
| R1-2007407 | Correction on terms and higher layer parameters for NB-IoT in 36.213 | Moderator (Huawei) |
| R1-2007408 | Correction on PUR-RNTI for NB-IoT in 36.212 | Moderator (Huawei) |
| R1-2007409 | Correction on PUR-RNTI for NB-IoT for NB-IoT in 36.213 | Moderator (Huawei) |
| 6.2.3 | Maintenance of DL MIMO efficiency enhancements for LTE | |
| R1-2005817 | Corrections on additional SRS symbols | Huawei, HiSilicon |
| R1-2006592 | Text proposals on additional SRS symbols | LG Electronics |
| R1-2006690 | Maintenance on additional SRS symbols | Ericsson |
| R1-2007028 | Feature summary on LTE DL MIMO efficiency enhancement | Moderator (Huawei) |
| R1-2007273 | Feature summary on [102-e-LTE-LTE_DL_MIMO_EE-01] | Moderator (Huawei) |
| R1-2007274 | Feature summary on [102-e-LTE-LTE_DL_MIMO_EE-02] | Moderator (Huawei) |
| R1-2007275 | TP to 36.211 on higher layer parameters for additional SRS | Moderator (Huawei) |
| R1-2007276 | TP to 36.213 on higher layer parameters for additional SRS | Moderator (Huawei) |
| R1-2007277 | TP to 36.211 on terminology of additional SRS | Moderator (Huawei) |
| R1-2007278 | Correction on higher layer parameters for additional SRS in 36.211 | Moderator (Huawei) |
| R1-2007279 | Correction on higher layer parameters for additional SRS in 36.213 | Moderator (Huawei) |
| R1-2007280 | Correction on terminology of additional SRS | Moderator (Huawei) |
| R1-2007373 | Session notes for 6.2.3 (Maintenance of DL MIMO efficiency enhancements for LTE) | Ad-hoc Chair (Samsung) |
| 6.2.4 | Maintenance of LTE-based 5G Terrestrial Broadcast | |
| R1-2005424 | TS 36.300 correction for the new numerologies of LTE-based 5G terrestrial broadcast | ZTE |
| R1-2006190 | Correction for PBCH repetition | Qualcomm Incorporated |
| R1-2006416 | Corrections to LTE-based 5G Terrestrial Broadcast | Huawei, HiSilicon |
| R1-2007041 | Feature lead summary for LTE-based 5G terrestrial broadcast | Moderator (Qualcomm Incorporated) |
| R1-2007042 | Summary of 102-e-LTE_TerrBcast-01 | Moderator (Qualcomm Incorporated) |
| R1-2007043 | Summary of 102-e-LTE_TerrBcast-02 | Moderator (Qualcomm Incorporated) |
| R1-2007154 | LS on updates to TS 36.300 on terrestrial broadcast | RAN1, Qualcomm |
| R1-2007190 | Correction for PBCH repetition | Moderator (Qualcomm Incorporated) |
| R1-2007191 | Correction on MBSFN region | Moderator (Qualcomm Incorporated) |
| R1-2007374 | Session notes for 6.2.4 (Maintenance of LTE-based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Ericsson) |
| 6.2.5 | LTE Rel-16 UE Features | |
| R1-2005473 | Remaining issues on LTE Rel-16 UE Features | ZTE |
| R1-2005943 | Summary of Other UE features for LTE | Moderator (AT&T) |
| R1-2006002 | Discussion on remaining issues of LTE feature list for 5G_V2X_NRSL | OPPO |
| R1-2006191 | Remaining issues for V2X UE Features | Qualcomm Incorporated |
| R1-2006461 | Updated RAN1 UE features list for Rel-16 LTE | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2006966 | Summary on UE features for eMTC | Moderator (NTT DOCOMO) |
| R1-2007139 | LS on updated Rel-16 RAN1 UE features lists for LTE | RAN1, AT&T, NTT DOCOMO |
| R1-2007140 | Updated RAN1 UE features list for Rel-16 LTE | Moderators (AT&T, NTT DOCOMO) |
| R1-2007163 | Updated RAN1 UE features list for Rel-16 LTE including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO) |
| R1-2007328 | Updated RAN1 UE features list for Rel-16 LTE | Moderators (AT&T, NTT DOCOMO) |
| R1-2007329 | LS on updated Rel-16 RAN1 UE features lists for LTE | RAN1, AT&T, NTT DOCOMO |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2005327 | Disucssion on PUSCH skipping with overlapping UCI on PUCCH | vivo |
| R1-2005328 | Draft 38.213 CR on PUSCH skipping with overlapping UCI on PUCCH | vivo |
| R1-2005444 | Draft CR on PTRS for TS 38.212 | ZTE |
| R1-2005445 | Draft CR on DMRS description for TS 38.211 | ZTE |
| R1-2005446 | Discussion on determining P0 for a Msg3 PUSCH retransmission | ZTE |
| R1-2005447 | Draft CR on determining P0 for a Msg3 PUSCH retransmission in TS 38.213 | ZTE |
| R1-2005448 | Discussion on determining real or virtual PHR for PUSCH | ZTE |
| R1-2005493 | Discussion on determining PHR for PUSCH in CA | ZTE |
| R1-2005494 | Draft CR on determining PHR for PUSCH in CA | ZTE |
| R1-2005618 | Clarification on Numerology for Active DL and UL BWPs | MediaTek Inc. |
| R1-2005630 | Draft CR on correction for Msg3 PUSCH retransmission power control | MediaTek Inc. |
| R1-2005631 | Clarification on valid configurations of PUCCH SR resources for multiplexing with HARQ-ACK/CSI | MediaTek Inc. |
| R1-2005657 | Correction on sounding procedure between component carriers | CATT |
| R1-2005658 | Correction on SRS power control | CATT |
| R1-2005659 | Correction on SRS power control | CATT |
| R1-2005660 | Correction on the definition for timeline condition | CATT |
| R1-2005661 | Correction for UCI on Msg3 PUSCH | CATT |
| R1-2005662 | Correction for PUCCH repetition transmission | CATT |
| R1-2005663 | Correction for PUCCH repetition transmission without corresponding PDCCH | CATT |
| R1-2006033 | Discussion on the QCL assumption for paging reception | OPPO |
| R1-2006034 | Draft CR on the QCL assumption for paging reception | OPPO |
| R1-2006069 | Correction on UCI multiplexing timeline | OPPO |
| R1-2006084 | 38.213 DRAFT CR (Rel-16, F) on PRACH power ramping suspension | Samsung |
| R1-2006085 | 38.213 DRAFT CR (Rel-15, F) on msg3 power determination | Samsung |
| R1-2006086 | 38.213 DRAFT CR (Rel-16, A) on msg3 power determination | Samsung |
| R1-2006087 | Discussion on msg3 power determination | Samsung |
| R1-2006088 | 38.211 DRAFT CR (Rel-16, F) on k_SSB calculation | Samsung |
| R1-2006089 | 38.213 DRAFT CR (Rel-16, F) on determination of the presence of CORESET#0 | Samsung |
| R1-2006090 | 38.213 DRAFT CR (Rel-16, F) on determination of the number of RS for RLM | Samsung |
| R1-2006330 | Correction on CSI transmission in PUCCH format 2 | ZTE |
| R1-2006331 | Discussion on dynamic PUSCH skipping with overlapping UCI on PUCCH in Rel-16 | ZTE |
| R1-2006332 | Interpretation of UE Features in Case of Cross-Carrier Operation | ZTE |
| R1-2006467 | 38.212CRdraft (Rel-16,F) RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) | Nokia, Nokia Shanghai Bell |
| R1-2006468 | 38.214CRdraft (Rel-16,F) Corrections to PDSCH PRB bundling notation (Rel-15 origin) | Nokia, Nokia Shanghai Bell |
| R1-2006476 | Draft CR on Measurement Restriction for L1-RSRP | Apple |
| R1-2006477 | Discussion on SRS collision handling | Apple |
| R1-2006478 | Draft CR on SRS collision handling | Apple |
| R1-2006479 | Discussion on cross CG CSI measurement for AP-CSI | Apple |
| R1-2006480 | Draft CR on cross CG CSI measurement for AP-CSI | Apple |
| R1-2006680 | Draft 38.214 CR on PUSCH skipping with overlapping UCI on PUCCH | vivo |
| R1-2006691 | CR on uplink transmission combination with PUCCH | NTT DOCOMO, INC. |
| R1-2006761 | Draft CR on CSI report with deactivated or decondigured resources | Qualcomm Incorporated |
| R1-2006762 | Dicussion on CSI report with deactivated or decondifgured resources | Qualcomm Incorporated |
| R1-2006851 | Clarification on which UE capability component indicates the number of supported simultaneous CSI calculations N_CPU | Nokia, Nokia Shanghai Bell |
| R1-2006852 | Clarification of PTRS port association for PUSCH | Nokia, Nokia Shanghai Bell |
| R1-2006872 | 38.212CRdraft (Rel-16,F) RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) | Nokia, Nokia Shanghai Bell |
| R1-2006902 | UL skipping and overlapping PUSCH/PUCCH | Ericsson, Nokia, Nokia Shanghai Bell |
| R1-2006936 | Correction on supplementary uplink in 38.213 | Huawei, HiSilicon |
| R1-2006941 | Correction on PDCCH candidate colliding with RB-symbol level RMR in TS38.213 | Huawei, HiSilicon |
| R1-2006942 | Correction on configuration of CORESET and search space in TS38.213 | Huawei, HiSilicon |
| R1-2006958 | RAN1#102-e preparation phase on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2006959 | RAN1#102-e preparation phase output on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2007082 | Correction on the definition for timeline condition | CATT |
| R1-2007083 | Correction on the definition for timeline condition | CATT |
| R1-2007084 | Correction for PUCCH repetition transmission | CATT |
| R1-2007085 | Correction on UCI bit sequence generation | ASUSTeK |
| R1-2007132 | CR on Measurement Restriction for L1-RSRP | Apple |
| R1-2007133 | CR on Measurement Restriction for L1-RSRP | Apple |
| R1-2007134 | CR on PTRS for TS 38.212 | ZTE |
| R1-2007135 | CR on PTRS for TS 38.212 | ZTE |
| R1-2007141 | Email Discussion Summary of [102-e-NR-7.1CRs-01] | Moderator (ZTE) |
| R1-2007147 | Correction on sounding procedure between component carriers | CATT |
| R1-2007148 | Correction on sounding procedure between component carriers | CATT |
| R1-2007149 | CR on determination of the number of RS for RLM | Samsung |
| R1-2007150 | Summary for [102-e-NR-7.1CRs-10] Determination of the number of RS for RLM | Moderator (Samsung) |
| R1-2007168 | Clarification on which UE capability component indicates the number of supported simultaneous CSI calculations N_CPU | Nokia, Nokia Shanghai Bell |
| R1-2007169 | Clarification on which UE capability component indicates the number of supported simultaneous CSI calculations N_CPU | Nokia, Nokia Shanghai Bell |
| R1-2007170 | CR on determining P0 for a PUSCH retransmission corresponding to a RAR UL grant in TS 38.213 | ZTE |
| R1-2007171 | CR on determining P0 for a PUSCH retransmission corresponding to a RAR UL grant in TS 38.213 | ZTE |
| R1-2007194 | PRACH power ramping suspension | Samsung |
| R1-2007200 | Summary of [102-e-NR-7.1CRs-13] Correction on PRACH power ramping suspension | Moderator (Samsung) |
| R1-2007214 | Corrections to PDSCH PRB bundling notation (Rel-15 origin) | Nokia, Nokia Shanghai Bell |
| R1-2007215 | Summary for [102-e-NR-7.1CRs-04] Correction on the definition for timeline condition | Moderator (CATT) |
| R1-2007249 | Summary for [102-e-NR-7.1CRs-08] QCL assumption for paging reception | Moderator (OPPO) |
| R1-2007316 | Correction on SRS carrier switching | CATT |
| R1-2007317 | Correction on SRS carrier switching | CATT |
| R1-2007318 | Correction on SRS carrier switching | CATT |
| R1-2007319 | Correction on SRS carrier switching | CATT |
| R1-2007333 | Email Discussion Summary of [102-e-NR-7.1CRs-07] | Moderator (ZTE) |
| R1-2007334 | LS on Interpretation of UE Features in Case of Cross-Carrier Operation | RAN1, ZTE |
| R1-2007335 | Summary of email discussion [102-e-NR-7.1CRs-11]-phase 1 | Moderator (vivo) |
| R1-2007336 | Summary of email discussion [102-e-NR-7.1CRs-11]-phase 2 | Moderator (vivo) |
| R1-2007337 | Correction on 38.214 for PUSCH with UL skipping | Moderator (vivo) |
| R1-2007338 | LS on PUSCH with UL skipping | RAN1, vivo |
| R1-2007375 | Session notes for 7.1 (Maintenance of Release 15 NR) | Ad-hoc Chair (Samsung) |
| R1-2007401 | Correction on supplementary uplink in 38.213 | Huawei, HiSilicon |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2005314 | Draft 38.215 CR Correction of SS-RSARP definition | Keysight Technologies UK Ltd |
| R1-2007052 | Draft 38.215 CR Correction of SS-RSARP definition | Keysight Technologies UK Ltd |
| R1-2007061 | Correction of SS-RSARP definition | Keysight Technologies UK Ltd |
| R1-2007088 | Correction of SS-RSARP definition | Keysight Technologies |
| R1-2007451 | Corrections on 5G V2X sidelink features | Qualcomm |
| R1-2007452 | Corrections to V2X | Ericsson |
| R1-2007453 | Corrections on 5G V2X sidelink features | Huawei |
| R1-2007454 | Corrections on Sidelink | Samsung |
| R1-2007455 | Corrections on 5G V2X sidelink features | Nokia |
| R1-2007456 | Corrections to V2X measurement definitions | Intel Corporation |
| R1-2007457 | Corrections to MIMO enhancements | Ericsson |
| R1-2007458 | Corrections to MIMO enhancements | Huawei |
| R1-2007459 | Corrections on MIMO enhancements | Samsung |
| R1-2007460 | Corrections to MIMO enhancements | Nokia |
| R1-2007461 | Corrections to CSI-SINR definition | Intel Corporation |
| R1-2007462 | Corrections to NR positioning support | Ericsson |
| R1-2007463 | Corrections to NR positioning support | Nokia |
| R1-2007464 | Corrections to NR positioning measurement definitions | Intel Corporation |
| R1-2007465 | Corrections to NR-based access to unlicensed spectrum | Ericsson |
| R1-2007466 | Corrections to NR-based access to unlicensed spectrum | Huawei |
| R1-2007467 | Corrections on shared spectrum channel access | Samsung |
| R1-2007468 | Corrections to NR-based access to unlicensed spectrum | Nokia |
| R1-2007469 | Corrections to NR-based access to unlicensed spectrum | Ericsson |
| R1-2007470 | Corrections on NR eURLLC | Huawei |
| R1-2007471 | Corrections on Ultra Reliable Low Latency Communications Enhancements | Samsung |
| R1-2007472 | Corrections on NR URLLC support | Nokia |
| R1-2007474 | Corrections on 5G V2X sidelink features | Nokia |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2005329 | Remaining issues on 2-step RACH | vivo |
| R1-2005605 | Text proposal on the modulation order of MsgB PDSCH | ZTE, Sanechips |
| R1-2005606 | FL summary on the maintenance of the 2-step RACH | Moderator (ZTE) |
| R1-2005664 | Remaining issues on 2-step RACH for NR | CATT |
| R1-2006091 | Remaining issues for two step RACH for NR | Samsung |
| R1-2006284 | Remaining issues on channel structure for 2-step RACH | Spreadtrum Communications |
| R1-2006407 | Remaining issues for 2-step RACH | Huawei, HiSilicon |
| R1-2006609 | Maintenance of Two step RACH | Ericsson |
| R1-2006692 | Maintenance for Two-step RACH | NTT DOCOMO, INC. |
| R1-2007096 | Summary of email discussion [102-e-NR-2step-RACH-01] | Moderator (ZTE) |
| R1-2007097 | Summary of email discussion [102-e-NR-2step-RACH-02] | Moderator (ZTE) |
| R1-2007098 | Draft CR on 2-step RACH for 38.211 | Moderator (ZTE) |
| R1-2007099 | Draft CR on 2-step RACH for 38.213 | Moderator (ZTE) |
| R1-2007100 | Draft CR on 2-step RACH for 38.214 | Moderator (ZTE) |
| R1-2007236 | CR on 2-step RACH for 38.211 | Moderator (ZTE) |
| R1-2007237 | CR on 2-step RACH for 38.213 | Moderator (ZTE) |
| R1-2007238 | CR on 2-step RACH for 38.214 | Moderator (ZTE) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2007376 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| 7.2.2.1.1 | Initial access signals/channels | |
| R1-2005330 | Remaining issues on initial access signals and channles | vivo |
| R1-2005597 | Remaining issues on the initial access signals for NR-U | ZTE, Sanechips |
| R1-2005789 | Maintenance on initial access signals and channels | Huawei, HiSilicon |
| R1-2005904 | Remaining issues on Initial Access Signals and Channels for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2005910 | Initial access signals and channels | Ericsson |
| R1-2006017 | Discussion on the remaining issues of initial access signal/channel | OPPO |
| R1-2006092 | Initial access signals and channels for NR-U | Samsung |
| R1-2006288 | Remaining issues on initial access signals | Spreadtrum Communications |
| R1-2006298 | Remaining issues of initial access signals and channels for NR-U | LG Electronics |
| R1-2006993 | FL summary for initial signals and channels for NR-U | Moderator (Qualcomm) |
| R1-2007093 | Email discussion summary on NR-U initial access signals and channels | Moderator (Qualcomm) |
| R1-2007192 | Email discussion summary#2 on NR-U initial access signals and channels | Moderator (Qualcomm) |
| 7.2.2.1.2 | DL signals and channels | |
| R1-2005331 | Remaining issues on physical DL channel design in unlicensed spectrum | vivo |
| R1-2005598 | Remaining issues on the DL channels for NR-U | ZTE, Sanechips |
| R1-2005807 | Maintenance on DL signals and channels | Huawei, HiSilicon |
| R1-2005844 | DL signals and channels for NR-unlicensed | Intel Corporation |
| R1-2005905 | Remaining issues on DL signals and channels | Nokia, Nokia Shanghai Bell |
| R1-2005911 | DL signals and channels | Ericsson |
| R1-2006018 | Discussion on the remaining issues of DL signals and channels | OPPO |
| R1-2006093 | DL signals and channels for NR-U | Samsung |
| R1-2006273 | Remaining issues in DL signals and channels for NR-U | Spreadtrum Communications |
| R1-2006299 | Remaining issues of DL signals and channels for NR-U | LG Electronics |
| R1-2006350 | Remaining issues on DL signals and channels for NR-U | ETRI |
| R1-2006483 | Remaining issues of DL signal and channels | Apple |
| R1-2006553 | Remaining issues on DL signals/channels for NR-U | Sharp |
| R1-2006836 | TP for DL signals and channels for NR-U | Qualcomm Incorporated |
| R1-2006862 | Maintenance for DL signals and channels for NR-U | Panasonic Corporation |
| R1-2006875 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2007143 | Summary of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-01] | Moderator (Lenovo) |
| R1-2007144 | Summary of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-02] | Moderator (Lenovo) |
| R1-2007145 | Summary of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-03] | Moderator (Lenovo) |
| R1-2007146 | Summary of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-04] | Moderator (Lenovo) |
| R1-2007257 | Summary#2 of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-01] | Moderator (Lenovo) |
| R1-2007258 | Summary#2 of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-02] | Moderator (Lenovo) |
| R1-2007259 | Summary#2 of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-03] | Moderator (Lenovo) |
| R1-2007260 | Summary#2 of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-04] | Moderator (Lenovo) |
| R1-2007357 | Summary#3 of email discussion [102-e-NR-unlic-NRU-DL_Signals_and_Channels-03] | Moderator (Lenovo) |
| 7.2.2.1.3 | UL signals and channels | |
| R1-2005332 | Remaining issues on physical UL channel design in unlicensed spectrum | vivo |
| R1-2005599 | Remaining issues on the UL channels for NR-U | ZTE, Sanechips |
| R1-2005808 | Maintenance on UL signals and channels | Huawei, HiSilicon |
| R1-2005826 | Text proposals for UL signals and channels for NR-U | Lenovo, Motorola Mobility |
| R1-2005912 | UL signals and channels | Ericsson |
| R1-2005913 | Feature Lead Summary for UL Signals and Channels | Ericsson |
| R1-2006019 | Discussion on the remaining issues of UL signals and channels | OPPO |
| R1-2006094 | UL signals and channels for NR-U | Samsung |
| R1-2006300 | Remaining issues of UL signals and channels for NR-U | LG Electronics |
| R1-2006371 | Remaining Issues on UL Signals & Channels for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2006554 | Remaining issues on UL signals/channels for NR-U | Sharp |
| R1-2007029 | FL Summary for [102-e-NRU-unlic-NRU-ULSignalsChannels] Email discussion/approval | Moderator (Ericsson) |
| R1-2007108 | FL Summary#2 for [102-e-NRU-unlic-NRU-ULSignalsChannels] Email discussion/approval | Moderator (Ericsson) |
| 7.2.2.2.1 | Channel access procedures | |
| R1-2005333 | Remaining issues on the channel access procedures | vivo |
| R1-2005600 | Remaining issues on the channel access procedure for NR-U | ZTE, Sanechips |
| R1-2005809 | Maintenance on channel access procedures | Huawei, HiSilicon |
| R1-2005914 | Channel access procedures | Ericsson |
| R1-2006020 | Discussion on the remaining issues of channel access procedure | OPPO |
| R1-2006095 | Channel access procedures for NR-U | Samsung |
| R1-2006301 | Remaining issues of channel access procedure for NR-U | LG Electronics |
| R1-2006351 | Remaining issues on channel access procedures for NR-U | ETRI |
| R1-2006370 | Remaining Issues on Channel Access Procedures for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2006675 | Feature Lead Summary on Channel Access Procedures for NR-U | Moderator (Nokia) |
| R1-2006763 | TP for Channel access procedures for NR unlicensed | Qualcomm Incorporated |
| R1-2006881 | Remaining issues on channel access procedure for NR-U | WILUS Inc. |
| R1-2007222 | Feature lead summary#1 on email discussion [102-e-NR-unlic-NRU-ChAcc-01] | Moderator (Nokia) |
| R1-2007223 | Feature lead summary#1 on email discussion [102-e-NR-unlic-NRU-ChAcc-02] | Moderator (Nokia) |
| R1-2007267 | Feature lead summary#2 on email discussion [102-e-NR-unlic-NRU-ChAcc-01] | Moderator (Nokia) |
| R1-2007291 | Feature lead summary#2 on email discussion [102-e-NR-unlic-NRU-ChAcc-02] | Moderator (Nokia) |
| R1-2007396 | Feature lead summary#3 on email discussion [102-e-NR-unlic-NRU-ChAcc-01] | Moderator (Nokia) |
| 7.2.2.2.2 | Enhancements to initial access procedure | |
| R1-2005334 | Remaining issues on initial access procedure for NR-U | vivo |
| R1-2005601 | Remaining issues on the initial access procedure for NR-U | ZTE, Sanechips |
| R1-2005756 | TPs on DCI reserved bits length in NR-U | NEC |
| R1-2005810 | Maintenance on initial access procedures | Huawei, HiSilicon |
| R1-2005915 | Enhancements to initial access procedures | Ericsson |
| R1-2006021 | Discussion on the remaining issues of enhancements to initial access procedure | OPPO |
| R1-2006096 | Initial access procedures for NR-U | Samsung |
| R1-2006449 | On Enhancements to Initial Access Procedures for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2006648 | Feature lead summary of enhancements to initial access procedures | Moderator (Charter Communications) |
| R1-2006764 | TP for Initial access and mobility procedures for NR-U | Qualcomm Incorporated |
| R1-2007113 | Outcome of email discussion [102-e-NR-unlic-NRU-InitAccessProc-01] | Moderator (Charter Communications) |
| R1-2007424 | Reply LS on UE declaring beam failure due to LBT failures during active TCI switching | RAN1, Nokia |
| 7.2.2.2.3 | HARQ enhancement | |
| R1-2005335 | Remaining issues on HARQ operation for NR-U | vivo |
| R1-2005602 | Remaining issues on the HARQ for NR-U | ZTE, Sanechips |
| R1-2005811 | Maintenance on HARQ-ACK enhancement | Huawei, HiSilicon |
| R1-2005827 | Text proposals for HARQ enhancement for NR-U | Lenovo, Motorola Mobility |
| R1-2005845 | Enhancements to HARQ for NR-unlicensed | Intel Corporation |
| R1-2005907 | Remaining issues on NR-U HARQ scheduling and feedback | Nokia, Nokia Shanghai Bell |
| R1-2005916 | HARQ enhancement | Ericsson |
| R1-2006022 | Discussion on the remaining issues of HARQ enhancements | OPPO |
| R1-2006097 | HARQ enhancement for NR-U | Samsung |
| R1-2006302 | Remaining issues of HARQ procedure for NR-U | LG Electronics |
| R1-2006555 | Remaining issues and corrections on HARQ enhancement for NR-U | Sharp |
| R1-2006765 | TP for Enhancements to Scheduling and HARQ Operation for NR-U | Qualcomm Incorporated |
| R1-2006900 | Text proposal for enhanced dynamic HARQ procedures | Google, Inc. |
| R1-2006983 | Feature lead summary#1 on NR-U HARQ maintenance | Moderator (Huawei) |
| R1-2007070 | Feature lead summary#1 on 102-e-NR-unlic-NRU-HARQ-01 | Moderator (Huawei) |
| R1-2007071 | Feature lead summary#1 on 102-e-NR-unlic-NRU-HARQ-02 | Moderator (Huawei) |
| R1-2007101 | TP for NR-U maintenance email thread 102-e-NR-unlic-NRU-HARQ-01 | Moderator (Huawei) |
| R1-2007102 | TP for NR-U maintenance email thread 102-e-NR-unlic-NRU-HARQ-02 | Moderator (Huawei) |
| R1-2007390 | Feature lead summary#2 on 102-e-NR-unlic-NRU-HARQ-02 | Moderator (Huawei) |
| 7.2.2.2.4 | Configured grant enhancement | |
| R1-2005336 | Remaining issues on the enhancements to configured grant | vivo |
| R1-2005337 | Feature lead summary on NRU configured grant enhancement | Moderator (vivo) |
| R1-2005603 | Remaining issues on the configured grant for NR-U | ZTE, Sanechips |
| R1-2005812 | Maintenance on the configured grant procedures | Huawei, HiSilicon |
| R1-2005828 | Text proposals for configured grant enhancement for NR-U | Lenovo, Motorola Mobility |
| R1-2005917 | Configured grant enhancement | Ericsson |
| R1-2006023 | Discussion on the remaining issues of configured grant enhancements | OPPO |
| R1-2006098 | Configured grant enhancement for NR-U | Samsung |
| R1-2006303 | Remaining issues of configured grant for NR-U | LG Electronics |
| R1-2006766 | TP for Enhancements to configured grants for NR-U | Qualcomm Incorporated |
| R1-2006866 | Remaining issues for DFI in NR-U | ASUSTeK |
| R1-2007112 | Feature lead summary#2 on NRU configured grant enhancement | Moderator (vivo) |
| R1-2007195 | Feature lead summary#3 on NRU configured grant enhancement | Moderator (vivo) |
| 7.2.2.2.5 | Wide-band operation | |
| R1-2005538 | Remaining issue on wideband operation | Fujitsu |
| R1-2005604 | Remaining issues on the wideband operation for NR-U | ZTE, Sanechips |
| R1-2005813 | Maintenance on the wideband operation procedures | Huawei, HiSilicon |
| R1-2005829 | Text proposals for wideband operation for NR-U | Lenovo, Motorola Mobility |
| R1-2005906 | Remaining issues on Wideband operation in NR-U | Nokia, Nokia Shanghai Bell |
| R1-2005918 | Wideband operation | Ericsson |
| R1-2006024 | Discussion on the remaining issues of wide-band operations | OPPO |
| R1-2006556 | Remaining corrections for wideband operation for NR-U | Sharp |
| R1-2006767 | TP for Wideband operation for NR-U operation | Qualcomm Incorporated |
| R1-2006967 | Summary on maintenance of wide-band operation for NR-U | Moderator (LG Electronics) |
| R1-2007058 | Summary of email discussion [102-e-NR-unlic-NRU-WB] | Moderator (LG Electronics) |
| 7.2.2.3 | Other | |
| R1-2005919 | A harmonized energy detection threshold for 6 GHz license-exempt spectrum | Ericsson |
| R1-2006025 | Discussion on the other remaining issues | OPPO |
| R1-2006409 | Discussion on the basic feature groups for NRU | Huawei, HiSilicon |
| 7.2.3 | Maintenance of Integrated Access and Backhaul for NR | |
| R1-2005316 | Remaining issues in IAB resource multiplexing | ZTE, Sanechips |
| R1-2006377 | Text proposal on PDCCH monitoring in IAB | LG Electronics |
| R1-2006997 | Feature Lead Summary #1 of 7.2.3 Maintenance of Integrated Access and Backhaul for NR | Moderator (AT&T) |
| R1-2007115 | Summary of [102-e-NR-IAB-01] | Moderator (AT&T) |
| R1-2007116 | Summary of [102-e-NR-IAB-02] | Moderator (AT&T) |
| R1-2007229 | Clarify starting slot within DCI 2_5 indication | Moderator (AT&T) |
| R1-2007377 | Session notes for 7.2.3 (Maintenance of Integrated Access and Backhaul for NR) | Ad-hoc Chair (Samsung) |
| 7.2.4.1 | Physical layer structure for sidelink | |
| R1-2005292 | Remaining details on physical layer structure for the sidelink | FUTUREWEI |
| R1-2005307 | Remaining issues of NR sidelink physical layer structure | ZTE, Sanechips |
| R1-2005338 | Remaining issues on physical layer structure for NR sidelink | vivo |
| R1-2005646 | Discussion on sidelink physical layer structure | MediaTek Inc. |
| R1-2005667 | Remaining issues on physical layer structure for NR sidelink | CATT |
| R1-2005740 | Discussion on essential corrections in physical layer structure | LG Electronics |
| R1-2005761 | TP on 1st symbol duplication for AGC | NEC |
| R1-2005786 | Remaining issues of V2X PHY layer structure | Mitsubishi Electric RCE |
| R1-2005796 | Remaining details of sidelink physical layer structure | Huawei, HiSilicon |
| R1-2005846 | Remaining opens for NR-V2X sidelink physical layer structure | Intel Corporation |
| R1-2005997 | Remaining issues on physical structure for NR sidelink | OPPO |
| R1-2006074 | Remaining issues on PHY structure for NR V2X | InterDigital, Inc. |
| R1-2006099 | On Physical Layer Structures for NR Sidelink | Samsung |
| R1-2006107 | Feature lead summary#1 for agenda item 7.2.4.1 Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2006108 | Feature lead summary#2 for agenda item 7.2.4.1 Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2006254 | Remaining issues for sidelink physical layer structure | Spreadtrum Communications |
| R1-2006433 | TPs related to PHY structures | Ericsson |
| R1-2006484 | On Remaining Issues of Sidelink Physical Layer Structure | Apple |
| R1-2006535 | Remaining issue on physical layer structure for sidelink in NR V2X | Panasonic Corporation |
| R1-2006557 | Remaining issues on physical layer structure for NR sidelink | Sharp |
| R1-2006584 | Remaining issues on sidelink physical layer structure on NR V2X | ASUSTeK |
| R1-2006693 | Maintenance for sidelink physical layer structure | NTT DOCOMO, INC. |
| R1-2006768 | Sidelink Physical Layer Structure | Qualcomm Incorporated |
| R1-2007160 | Text Proposal for PSCCH and 2nd SCI related issue including their RS | Moderator (Samsung) |
| R1-2007161 | Text Proposal for max data rate for SL and TBS | Moderator (Samsung) |
| R1-2007162 | Text Proposal for PSFCH sequence related | Moderator (Samsung) |
| R1-2007348 | [Draft] Reply LS on maximum data rate for NR sidelink | Samsung |
| R1-2007353 | Reply LS on maximum data rate for NR sidelink | RAN1, Samsung |
| 7.2.4.2.1 | Mode 1 | |
| R1-2005293 | Remaining details on mode-1 resource allocation | FUTUREWEI |
| R1-2005317 | Remaining issues in Mode-1 | ZTE, Sanechips |
| R1-2005339 | Remaining issues on mode 1 resource allocation mechanism | vivo |
| R1-2005539 | Remaining issues on mode 1 resource allocation for NR V2X | Fujitsu |
| R1-2005668 | Remaining issues on Mode 1 resource allocation in NR V2X | CATT |
| R1-2005741 | Discussion on essential corrections in resource allocation for Mode 1 | LG Electronics |
| R1-2005797 | Remaining details of sidelink resource allocation mode 1 | Huawei, HiSilicon |
| R1-2005847 | Remaining opens for NR-V2X sidelink resource allocation Mode 1 | Intel Corporation |
| R1-2005998 | Remaining issues of mode 1 resource allocation for NR-V2X | OPPO |
| R1-2006075 | Remaining Issues on NR Sidelink Mode 1 Resource Allocation | InterDigital, Inc. |
| R1-2006100 | On Mode 1 for NR Sidelink | Samsung |
| R1-2006198 | Remaining issues on mode 1 resource allocation mechanism | CMCC |
| R1-2006263 | Remaining issues in NR sidelink mode 1 resource allocation | Spreadtrum Communications |
| R1-2006352 | Resource allocation mode 1 for NR V2X | ETRI |
| R1-2006434 | Open issues and corrections on Mode 1 resource allocation | Ericsson |
| R1-2006485 | On Remaining Issues of Mode 1 Resource Allocation | Apple |
| R1-2006558 | Remaining issues on resource allocation mode 1 for NR sidelink | Sharp |
| R1-2006694 | Maintenance for resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2006769 | Sidelink Resource Allocation Mode 1 | Qualcomm Incorporated |
| R1-2006867 | Miscellaneous issues for Mode 1 resource allocation in NR V2X | ASUSTeK |
| R1-2006960 | Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2006961 | Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2007415 | TPs for 38.212 for the agreements in [102-e-NR-5G_V2X_NRSL-Mode-1-01] | Moderator (Ericsson) |
| R1-2007416 | TPs for 38.213 for the agreements in [102-e-NR-5G_V2X_NRSL-Mode-1-01] | Moderator (Ericsson) |
| R1-2007417 | TPs for 38.213 for the agreements in [102-e-NR-5G_V2X_NRSL-Mode-1-02] | Moderator (Ericsson) |
| R1-2007418 | TP for 38.214 for the agreements in [102-e-NR-5G_V2X_NRSL-Mode-1-02] | Moderator (Ericsson) |
| 7.2.4.2.2 | Mode 2 | |
| R1-2005318 | Remaining issues in mode 2 | ZTE, Sanechips |
| R1-2005340 | Remaining issues on mode 2 resource allocation mechanism | vivo |
| R1-2005540 | Remaining details on mode 2 resource allocation for NR V2X | Fujitsu |
| R1-2005593 | Remaining details on mode-2 resource allocation | FUTUREWEI |
| R1-2005669 | Remaining issues on Mode 2 resource allocation in NR V2X | CATT |
| R1-2005742 | Discussion on essential corrections in resource allocation for Mode 2 | LG Electronics |
| R1-2005798 | Remaining details of sidelink resource allocation mode 2 | Huawei, HiSilicon |
| R1-2005848 | Remaining opens for NR-V2X sidelink resource allocation Mode 2 | Intel Corporation |
| R1-2006004 | Discussion on remaining open issues in mode 2 | OPPO |
| R1-2006076 | Remaining Issues on NR Sidelink Mode 2 Resource Allocation | InterDigital, Inc. |
| R1-2006101 | On Mode 2 for NR Sidelink | Samsung |
| R1-2006264 | Remaining issues in NR sidelink mode 2 resource allocation | Spreadtrum Communications |
| R1-2006353 | Resource allocation mode 2 for NR V2X | ETRI |
| R1-2006435 | Open issues and corrections on Mode 2 resource allocation | Ericsson |
| R1-2006559 | Remaining issues on resource allocation mode 2 for NR sidelink | Sharp |
| R1-2006695 | Maintenance for resource allocation mechanism mode 2 | NTT DOCOMO, INC. |
| R1-2006770 | Sidelink Resource Allocation Mode 2 | Qualcomm Incorporated |
| R1-2006864 | Remaining issues for Mode 2 resource allocation in NR V2X | ASUSTeK |
| R1-2006976 | FL summary#1 of issues for 7.2.4.2.2 – V2X Mode 2 | Moderator (Intel Corporation) |
| R1-2007219 | Outcome and TPs from email discussion [102-e-NR-5G_V2X_NRSL-Mode-2-01] | Moderator (Intel Corporation) |
| R1-2007220 | Outcome and TPs from email discussion [102-e-NR-5G_V2X_NRSL-Mode-2-02] | Moderator (Intel Corporation) |
| R1-2007221 | Outcome and TPs from email discussion [102-e-NR-5G_V2X_NRSL-Mode-2-03] | Moderator (Intel Corporation) |
| R1-2007303 | [draft] Reply LS to RAN2 on physical layer related agreements | Intel Corporation |
| R1-2007389 | Reply LS to RAN2 on physical layer related agreements Intel Corporation | RAN1, Intel Corporation |
| 7.2.4.2.3 | Other | |
| R1-2005341 | Remaining issues for resource allocation | vivo |
| R1-2006399 | Remaining details of pre-emption | Huawei, HiSilicon |
| R1-2006436 | Other outstanding resource allocation issues | Ericsson |
| 7.2.4.3 | Sidelink synchronization mechanism | |
| R1-2005308 | Remaining issues of Synchronization | ZTE, Sanechips |
| R1-2005342 | Remaining issues on sidelink synchronization mechanism | vivo |
| R1-2005647 | Discussion on sidelink based synchronization mechanism | MediaTek Inc. |
| R1-2005670 | Remaining issues on sidelink synchronization mechanism in NR V2X | CATT |
| R1-2005743 | Discussion on essential corrections in sidelink synchronization mechanism | LG Electronics |
| R1-2005799 | Remaining details of sidelink synchronization mechanisms | Huawei, HiSilicon |
| R1-2005999 | Remaining issues of synchronization for NR-V2X | OPPO |
| R1-2006102 | On Synchronization Mechanisms for NR Sidelink | Samsung |
| R1-2006437 | Corrections on sidelink synchronization mechanism | Ericsson |
| R1-2006560 | Remaining issues on synchronization mechanism for NR sidelink | Sharp |
| R1-2006948 | Feature lead summary#1 on AI 7.2.4.3 Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2007368 | Feature lead summary#2 on AI 7.2.4.3 Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2007369 | Text proposal from Email discussion thread #01 for AI 7.2.4.3 Sidelink synchronization mechanism | Moderator (CATT) |
| 7.2.4.4 | In-device coexistence between LTE and NR sidelinks | |
| R1-2005319 | Remaining issues of in-device coexistence | ZTE, Sanechips |
| R1-2005343 | Remaining issues on In-device coexistence between NR and LTE sidelinks | vivo |
| R1-2005744 | Discussion on essential corrections in in-device coexistence | LG Electronics |
| R1-2005800 | Remaining details of in-device coexistence between LTE and NR sidelinks | Huawei, HiSilicon |
| R1-2006005 | FDM-based semi-static power split for in-device coexistence | OPPO |
| R1-2006103 | On In-device Coexistence between LTE and NR Sidelink | Samsung |
| R1-2006438 | Correction for in-device coexistence in SL | Ericsson |
| R1-2006771 | In-device Coexistence between LTE and NR sidelink | Qualcomm Incorporated |
| R1-2006772 | FL Summary of In-device Coexistence Aspects in NR-V2X | Qualcomm Incorporated |
| R1-2006869 | Discussion on processing time restriction for in-device coexistence | ASUSTeK |
| R1-2006910 | Remaining details of In-device coexistence between LTE and NR sidelinks | Nokia, Nokia Shanghai Bell |
| R1-2007198 | Feature-lead Summary of Discussion for In-device Coexistence Aspects in NR-V2X | Moderator (Qualcomm) |
| R1-2007199 | Text Proposals for In-device Coexistence Aspects in NR-V2X | Moderator (Qualcomm) |
| 7.2.4.5 | Physical layer procedures for sidelink | |
| R1-2005320 | Remaining issues in PHY procedures for Rel-16 sidelink | ZTE, Sanechips |
| R1-2005344 | Remaining issues on physical layer procedure for NR sidelink | vivo |
| R1-2005594 | Remaining details on physical procedures for sidelink | FUTUREWEI |
| R1-2005671 | Remaining issues on physical layer procedures for NR V2X | CATT |
| R1-2005745 | Discussion on essential corrections in physical layer procedure | LG Electronics |
| R1-2005801 | Remaining details of physical layer procedures for sidelink | Huawei, HiSilicon |
| R1-2005849 | Remaining opens for NR-V2X sidelink physical layer procedures | Intel Corporation |
| R1-2006000 | Remaining issues of physical layer procedure for NR-V2X | OPPO |
| R1-2006104 | On Physical Layer Procedures for NR Sidelink | Samsung |
| R1-2006179 | Remaining issues on NR SL physical layer procedures | InterDigital, Inc. |
| R1-2006265 | Remaining issues on sidelink physical layer procedure | Spreadtrum Communications |
| R1-2006354 | Physical layer procedures for sidelink | ETRI |
| R1-2006439 | Open issues and corrections for SL Physical layer procedures | Ericsson |
| R1-2006486 | On Remaining Issues of Sidelink Physical Layer Procedures | Apple |
| R1-2006536 | Remaining issue on physical layer procedures for sidelink in NR V2X | Panasonic Corporation |
| R1-2006561 | Remaining issues on physical layer procedures for NR sidelink | Sharp |
| R1-2006586 | Remaining issues on sidelink physical layer procedure on NR V2X | ASUSTeK |
| R1-2006696 | Maintenance for on sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2006773 | Physical layer procedures for sidelink | Qualcomm Incorporated |
| R1-2006957 | Feature lead summary#1 for AI 7.2.4.5 Physical layer procedures for sidelink | Moderator (LG Electronics) |
| R1-2007349 | Text proposal from Email discussion thread #1 for AI 7.2.4.5 Physical layer procedures for sidelink | Moderator (LG Electronics) |
| R1-2007350 | Text proposal from Email discussion thread #2 for AI 7.2.4.5 Physical layer procedures for sidelink | Moderator (LG Electronics) |
| 7.2.4.6 | QoS management for sidelink | |
| R1-2005321 | Remaining issues on QoS | ZTE, Sanechips |
| R1-2005345 | Remaining issues on QoS management for sidelink | vivo |
| R1-2005802 | Remaining details of QoS management for NR sidelink | Huawei, HiSilicon |
| R1-2006006 | Remaining open issues in QoS management | OPPO |
| R1-2006105 | On QoS Management for NR Sidelink | Samsung |
| R1-2006180 | Remaining Issues on Congestion Control and QoS Management for NR-V2X | InterDigital, Inc. |
| R1-2006440 | Correction for SL QoS management | Ericsson |
| R1-2006962 | Feature Lead Summary#1 for 7.2.4.6 QoS management for sidelink | Moderator (Nokia) |
| 7.2.4.7 | Support of NR Uu controlling LTE sidelink | |
| R1-2005322 | Remaining issues on NR Uu control LTE sidelink | ZTE, Sanechips |
| R1-2005803 | Remaining details of NR Uu control for LTE sidelink | Huawei, HiSilicon |
| R1-2006007 | Remaining open issues in NR Uu controlling LTE sidelink | OPPO |
| R1-2006106 | On NR Uu controling for LTE sidelink | Samsung |
| R1-2006441 | Open issue for NR Uu controlling LTE sidelink transmissions | Ericsson |
| R1-2006562 | Remaining issues on support of NR Uu controlling LTE sidelink | Sharp |
| R1-2007421 | FL summary #1 on NR Uu scheduling LTE sidelink | Moderator (FUTUREWEI) |
| 7.2.4.8 | Other | |
| R1-2005346 | Remaining aspects for NR V2X | vivo |
| R1-2006008 | Corrections for NR-V2X power control | OPPO |
| R1-2006181 | Remaining Issues on Sidelink RLF | InterDigital, Inc. |
| R1-2006400 | Remaining details of sidelink RRC Parameter List | Huawei, HiSilicon |
| R1-2006442 | Discussion on maximum data rate on SL | Ericsson |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC | |
| R1-2007378 | Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) | Ad-hoc Chair (Samsung) |
| 7.2.5.1 | PDCCH enhancements | |
| R1-2005347 | PDCCH enhancements for URLLC | vivo |
| R1-2005413 | Remaining issues on PDCCH enhancements for NR URLLC | ZTE |
| R1-2005506 | Remaining Issue of PDCCH Enhancements for NR URLLC | Ericsson |
| R1-2005672 | Remaining issues on PDCCH enhancements | CATT |
| R1-2005790 | Corrections on PDCCH enhancement for URLLC | Huawei, HiSilicon |
| R1-2005850 | Remaining corrections for PDCCH enhancements for URLLC | Intel Corporation |
| R1-2006051 | PDCCH enhancements for URLLC | OPPO |
| R1-2006109 | Maintenance on PDCCH enhancements | Samsung |
| R1-2006278 | Remaining issues of PDCCH enhancements for URLLC | Spreadtrum Communications |
| R1-2006487 | Remaining issues on PDCCH enhancements | Apple |
| R1-2006549 | Remaining Issues on PDCCH Enhancements for Rel-16 URLLC | Quectel |
| R1-2006563 | Remaining issues on PDCCH enhancements for NR URLLC | Sharp |
| R1-2006774 | Remaining issues on PDCCH Enhancements for URLLC | Qualcomm Incorporated |
| R1-2006865 | Remaining issue for TCI field | ASUSTeK |
| R1-2006882 | Remaining issues on PDCCH for NR URLLC | WILUS Inc. |
| R1-2006968 | Feature lead summary#1 on PDCCH enhancements | Moderator (Huawei) |
| R1-2007004 | Feature lead summary#2 on PDCCH enhancements | Moderator (Huawei) |
| R1-2007066 | Summary #1 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design | Moderator (Huawei) |
| R1-2007067 | Summary #1 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2007118 | Summary #2 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design | Moderator (Huawei) |
| R1-2007119 | Summary #2 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2007226 | Summary #3 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2007250 | Summary #4 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2007251 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-2 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | Moderator (Huawei) |
| R1-2007252 | Text proposal for TS 38.213 Section 10 as outcome of issue B-5-3 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | Moderator (Huawei) |
| R1-2007253 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-5-4 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | Moderator (Huawei) |
| R1-2007254 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-5-6 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | Moderator (Huawei) |
| R1-2007255 | Summary #3 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design | Moderator (Huawei) |
| R1-2007256 | Text proposal for TS 38.212 Section 7.3.1.0 as outcome of issue A-1 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] | Moderator (Huawei) |
| R1-2007443 | Summary #5 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability | Moderator (Huawei) |
| R1-2007444 | Text proposal for TS 38.213 Section 10 as outcome of issue B-1 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | Moderator (Huawei) |
| 7.2.5.2 | UCI enhancements | |
| R1-2005348 | UCI enhancements for URLLC | vivo |
| R1-2005414 | Remaining issues on UL control enhancements for NR URLLC | ZTE |
| R1-2005507 | Remaining Issue of UCI Enhancements for NR URLLC | Ericsson |
| R1-2005541 | Remaining issues on UCI enhancements for URLLC | Fujitsu |
| R1-2005549 | Maintenance of Rel-16 URLLC UCI enhancements | Nokia, Nokia Shanghai Bell |
| R1-2005673 | Remaining issues on UCI enhancements | CATT |
| R1-2005792 | Corrections on UCI enhancement | Huawei, HiSilicon |
| R1-2005851 | Remaining details on UCI enhancements for URLLC | Intel Corporation |
| R1-2006052 | UCI enhancements for URLLC | OPPO |
| R1-2006110 | Maintenance on UCI enhancements | Samsung |
| R1-2006279 | Remaining issues of UCI enhancements for URLLC | Spreadtrum Communications |
| R1-2006472 | UCI enhancements for URLLC | InterDigital, Inc. |
| R1-2006488 | Remaining Issues on UCI Enhancements for eURLLC | Apple |
| R1-2006653 | Remaining issue on the HARQ-ACK/PUSCH priority | ITRI |
| R1-2006697 | Maintainance for UCI enhancement for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2006775 | Remaining issues on UCI Enhancements for URLLC | Qualcomm Incorporated |
| R1-2006971 | Summary#1 on UCI enhancements for R16 URLLC | Moderator (OPPO) |
| R1-2007053 | Summary#1 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-01] | Moderator (OPPO) |
| R1-2007054 | Summary#1 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-02] | Moderator (OPPO) |
| R1-2007072 | Summary#2 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-01] | Moderator (OPPO) |
| R1-2007073 | Summary#2 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-02] | Moderator (OPPO) |
| R1-2007240 | Summary#3 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-02] | Moderator (OPPO) |
| R1-2007394 | Summary#3 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-01] | Moderator (OPPO) |
| R1-2007447 | Summary#4 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-01] | Moderator (OPPO) |
| R1-2007448 | Summary#4 of email thread [102-e-NR-L1enh_URLLC-UCI_Enh-02] | Moderator (OPPO) |
| 7.2.5.3 | PUSCH enhancements | |
| R1-2005349 | PUSCH enhancements for URLLC | vivo |
| R1-2005415 | Remaining issues on PUSCH enhancements for NR URLLC | ZTE |
| R1-2005508 | Remaining Issue of PUSCH Enhancements for NR URLLC | Ericsson |
| R1-2005674 | Remaining issues on PUSCH enhancements | CATT |
| R1-2005793 | Corrections on PUSCH enhancement | Huawei, HiSilicon |
| R1-2006053 | PUSCH enhancements for URLLC | OPPO |
| R1-2006111 | Remaining issues for PUSCH enhancement | Samsung |
| R1-2006489 | Remaining Issues on PUSCH enhancements for eURLLC | Apple |
| R1-2006490 | Feature lead summary #1 on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) | Moderator (Apple) |
| R1-2006776 | Remaining issues on PUSCH enhancements for URLLC | Qualcomm Incorporated |
| R1-2006883 | Remaining issues on PUSCH enhancement for NR URLLC | WILUS Inc. |
| R1-2006992 | Feature lead summary #2 on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) | Moderator (Apple) |
| R1-2007025 | Summary of Email Discussion [102-e-NR-L1enh-URLLC-PUSCH_Enh-01] | Moderator (Apple Inc.) |
| R1-2007174 | Summary#2 of Email Discussion [102-e-NR-L1enh-URLLC-PUSCH_Enh-01] | Moderator (Apple Inc.) |
| 7.2.5.4 | Enhancements to scheduling/HARQ | |
| R1-2005350 | Enhancement for Scheduling/HARQ | vivo |
| R1-2005416 | Remaining issues on scheduling/HARQ enhancements for NR URLLC | ZTE |
| R1-2005509 | Remaining Issue of Scheduling/HARQ for NR URLLC | Ericsson |
| R1-2005550 | Maintenance of Rel-16 URLLC intra-UE prioritization enhancements | Nokia, Nokia Shanghai Bell |
| R1-2005632 | On the retransmission of a cancelled UL TB | MediaTek Inc. |
| R1-2005675 | Remaining issues on intra-UE prioritization | CATT |
| R1-2005852 | Remaining details on Scheduling & HARQ enhancements for URLLC | Intel Corporation |
| R1-2006054 | Enhancements to scheduling and HARQ | OPPO |
| R1-2006112 | Maintenance on scheduling/HARQ enhancements | Samsung |
| R1-2006280 | Remaining issues of enhancements to scheduling/HARQ | Spreadtrum Communications |
| R1-2006294 | Remaining issues of Enhancements to scheduling/HARQ for NR URLLC | LG Electronics |
| R1-2006389 | Corrections on operation of HARQ | Huawei, HiSilicon |
| R1-2006491 | TB CRC Handling in case of Cancellation of Initial Transmission in eURLLC | Apple |
| R1-2006633 | Remaining issues on scheduling/HARQ enhancements | Asia Pacific Telecom co. Ltd |
| R1-2006698 | Maintenance for scheduling/HARQ for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2006777 | Remaining issues on HARQ and scheduling for URLLC | Qualcomm Incorporated |
| R1-2007033 | Summary of the Remaining Issues on HARQ and Scheduling Enhancements for URLLC: Preparation Phase | Moderator (Qualcomm Incorporated) |
| R1-2007034 | Summary #1 of [102-e-NR-L1enh-URLLC-Scheduling and HARQ-01] | Moderator (Qualcomm Incorporated) |
| R1-2007035 | Summary #1 of [102-e-NR-L1enh-URLLC-Scheduling and HARQ-02] | Moderator (Qualcomm Incorporated) |
| R1-2007429 | Summary #2 of [102-e-NR-L1enh-URLLC-Scheduling and HARQ-01] | Moderator (Qualcomm Incorporated) |
| R1-2007430 | Summary #2 of [102-e-NR-L1enh-URLLC-Scheduling and HARQ-02] | Moderator (Qualcomm Incorporated) |
| R1-2007431 | Endorsed TP for [102-e-NR-L1enh-URLLC-Scheduling and HARQ-01] | Moderator (Qualcomm Incorporated) |
| R1-2007432 | Summary #3 of [102-e-NR-L1enh-URLLC-Scheduling and HARQ-02] | Moderator (Qualcomm Incorporated) |
| 7.2.5.5 | Enhanced inter UE Tx prioritization/multiplexing | |
| R1-2005351 | UL inter UE Tx prioritization for URLLC | vivo |
| R1-2005417 | Remaining issues on UL inter-UE multiplexing between eMBB and URLLC | ZTE |
| R1-2005510 | Remaining Issue of Inter-UE Prioritization and Multiplexing of UL Transmissions | Ericsson |
| R1-2005676 | Remaining issues on inter-UE UL multiplexing | CATT |
| R1-2005791 | Corrections on UL inter-UE multiplexing | Huawei, HiSilicon |
| R1-2006055 | Inter UE Tx prioritization and multiplexing | OPPO |
| R1-2006113 | Maintenance on inter-UE multiplexing | Samsung |
| R1-2006355 | Enhanced inter UE Tx prioritization/multiplexing | ETRI |
| R1-2006492 | Remaining Issues on Inter-UE Cancellation for eURLLC | Apple |
| R1-2006660 | Inter-UE prioritization/multiplexing | InterDigital, Inc. |
| R1-2006778 | Remaining issues on uplink Inter-UE Tx Multiplexing and Prioritization | Qualcomm Incorporated |
| R1-2006980 | Summary of UL inter UE Tx prioritization – Preparing phase | Moderator (vivo) |
| R1-2007077 | Summary of [102-e-NR-L1enh-URLLC-InterUE-01] Remaining issues on inter-UE prioritization/multiplexing | Moderator (vivo) |
| R1-2007208 | Summary#2 of [102-e-NR-L1enh-URLLC-InterUE-01] Remaining issues on inter-UE prioritization/multiplexing | Moderator (vivo) |
| 7.2.5.6 | Enhanced UL configured grant transmission | |
| R1-2005418 | Remaining issues on enhancements for UL configured grant transmission | ZTE |
| R1-2005511 | Remaining Issue of Enhancements to UL Configured Grant Transmission for NR URLLC | Ericsson |
| R1-2005677 | Corrections on Enhanced UL configured grant transmission | CATT |
| R1-2006056 | Configured grant enhancements for URLLC | OPPO |
| R1-2006493 | Remaining issues on enhanced UL configured grant transmission | Apple |
| R1-2006657 | Corrections for configured grant PUSCH | vivo |
| R1-2006969 | Feature lead summary on URLLC enhanced configured grant transmission | Moderator (vivo) |
| R1-2007178 | Email discussion #01 for remaining issues on URLLC enhanced configured grant transmission | Moderator (vivo) |
| R1-2007218 | Text proposal for TS 38.214 based on [102-e-NR-L1enh-URLLC-eCG-01] | Moderator (vivo) |
| 7.2.5.7 | Other | |
| R1-2005352 | Other issues for URLLC | vivo |
| R1-2005419 | Remaining issues on SPS enhancements | ZTE |
| R1-2005512 | Remaining Issue of Other Enhancements for NR URLLC/IIoT | Ericsson |
| R1-2005551 | Maintenance of Rel-16 URLLC/IIoT SPS enhancements | Nokia, Nokia Shanghai Bell |
| R1-2005678 | Remaining issues on SPS enhancements | CATT |
| R1-2005775 | Remaining issues on DL SPS enhancement for URLLC | NEC |
| R1-2006057 | DL SPS enhancement | OPPO |
| R1-2006114 | Maintenance on IIoT SPS enhancements | Samsung |
| R1-2006295 | Remaining issues of other aspects for URLLC/IIOT | LG Electronics |
| R1-2006296 | Summary on maintenance of other aspects for URLLC/IIOT | Moderator (LG Electronics) |
| R1-2006390 | Corrections on other aspects for URLLC/IIOT enhancements | Huawei, HiSilicon |
| R1-2006564 | PUCCH resource determination for SPS PDSCH receptions for NR URLLC | Sharp |
| R1-2006634 | Remaining issues on DL SPS enhancements | Asia Pacific Telecom co. Ltd |
| R1-2006699 | Maintainance for SPS enhancement for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2006779 | Remaining issues on uplink collision handling and SPS for URLLC | Qualcomm Incorporated |
| R1-2006884 | Remaining Issues on SPS PDSCH for NR URLLC | WILUS Inc. |
| R1-2007124 | Summary#1 of [102-e-NR-L1enh-URLLC-IIoTenh-01] | Moderator (LG Electronics) |
| R1-2007224 | Text proposals on agreements from [102-e-NR-L1enh-URLLC-IIoTenh-01] | Moderator (LG Electronics) |
| R1-2007346 | Summary#2 of [102-e-NR-L1enh-URLLC-IIoTenh-01] | Moderator (LG Electronics) |
| R1-2007347 | Text proposals on agreements from [102-e-NR-L1enh-URLLC-IIoTenh-01] | Moderator (LG Electronics) |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2005353 | Remaining issues on Multi beam operation | vivo |
| R1-2005354 | Remaining issues on Multi TRP operation | vivo |
| R1-2005355 | Miscelleneous corrections on Rel-16 MIMO | vivo |
| R1-2005449 | Maintenance of multi-beam operation | ZTE |
| R1-2005450 | Maintenance of full power UL transmission | ZTE |
| R1-2005451 | Maintenance of Multi-TRP enhancements | ZTE |
| R1-2005554 | Remaining issues on NR MIMO | InterDigital, Inc. |
| R1-2005559 | Remaining issues on multi-beam operation | Sony |
| R1-2005624 | Remaining issues on multi-beam operation | MediaTek Inc. |
| R1-2005679 | Remaining issues on multi-beam operation enhancement | CATT |
| R1-2005819 | Maintenance on multi-TRP operation | Lenovo, Motorola Mobility |
| R1-2005853 | Corrections to multi TRP | Intel Corporation |
| R1-2005924 | Maintenance on MU-CSI Enhancements | Lenovo, Motorola Mobility |
| R1-2005975 | Text proposals for enhancements on multi-TRP and panel Transmission | OPPO |
| R1-2005976 | Text proposals for Multi-beam Operation Enhancement | OPPO |
| R1-2005977 | Discussion and Text proposals for full TX power UL transmission | OPPO |
| R1-2006115 | On maintenance of Rel.16 MU CSI enhancements and multi-beam operation | Samsung |
| R1-2006116 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2006117 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2006118 | On UL full power transmission | Samsung |
| R1-2006249 | Remaining issues on CSI enhancement for MU-MIMO | Spreadtrum Communications |
| R1-2006256 | Discussion on remaining issues on UL full power transmission | Spreadtrum Communications |
| R1-2006257 | Discussion on remaining issues for multi-TRP operation | Spreadtrum Communications |
| R1-2006395 | Remaining issues for Multi-TRP in Rel-16 | Huawei, HiSilicon |
| R1-2006396 | Remaining issues on multi-beam enhancements in R16 | Huawei, HiSilicon |
| R1-2006397 | Remaining issues on UL full power transmission in R16 | Huawei, HiSilicon |
| R1-2006494 | Remaining issues on Multi-TRP enhancement | Apple |
| R1-2006495 | Remaining issues on Beam Management | Apple |
| R1-2006496 | Remaining issues on Rel-16 full power transmission | Apple |
| R1-2006497 | FL Summary on SCell BFR and L1-SINR | Apple |
| R1-2006551 | Corrections for enhancements on MIMO for NR | Sharp |
| R1-2006588 | Discussion on remaining issues of multi-TRP/panel transmission | CATT |
| R1-2006593 | Text proposals on enhancements on multi-TRP/panel transmission | LG Electronics |
| R1-2006594 | Remaining issues on multi beam operation | LG Electronics |
| R1-2006595 | Discussions on full Tx power UL transmission | LG Electronics |
| R1-2006608 | Corrections for Full Power UL Transmission | Ericsson |
| R1-2006635 | Maintenance of SCell Beam Failure Recovery | Asia Pacific Telecom co. Ltd |
| R1-2006688 | Remaining issues on single-DCI based Multi-TRP | Ericsson |
| R1-2006689 | Remaining issues on multi-DCI based Multi-TRP | Ericsson |
| R1-2006700 | Remaining issues on multi-TRP/panel transmission | NTT DOCOMO, INC. |
| R1-2006701 | PUCCH/PDCCH beam after CBRA-BFR in Rel.16 | NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2006780 | Remaining issues on MU-CSI enhancement, UL full power, and low PAPR RS | Qualcomm Incorporated |
| R1-2006781 | Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2006782 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2006840 | Correction of RRC parameter name for AP-TRS | Nokia, Nokia Shanghai Bell |
| R1-2006841 | Maintenance of Rel-16 CSI enhancement | Nokia, Nokia Shanghai Bell |
| R1-2006842 | Maintenance of Rel-16 Multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2006979 | Summary#2 for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2006984 | Text proposal on MU.1 issue for Rel.16 NR_eMIMO MU CSI | Moderator (Samsung) |
| R1-2007005 | Text proposals on MB.3 issue for Rel.16 NR_eMIMO Multi-Beam | Moderator (LG Electronics) |
| R1-2007006 | Summary#1 of email thread [102-e-NR-eMIMO-01] | Moderator (LG Electronics) |
| R1-2007007 | Summary#1 of email thread [102-e-NR-eMIMO-02] | Moderator (LG Electronics) |
| R1-2007051 | Summary of [102-e-NR-eMIMO-09] Reply LS on feasibility of ULFPTx modes and transparent TxD for certain UE implementations | Moderator (Huawei) |
| R1-2007086 | Outcome of email thread [102-e-NR-eMIMO-01] | Moderator (LG Electronics) |
| R1-2007087 | Outcome of email thread [102-e-NR-eMIMO-02] | Moderator (LG Electronics) |
| R1-2007092 | Text proposal on default PL RS for Rel.16 NR_eMIMO Multi-Beam | Moderator (LG Electronics) |
| R1-2007114 | Feature lead summary#1 on ULFPTx | Moderator (vivo) |
| R1-2007120 | Text Proposal for TS 38.214 in [102-e-NR-eMIMO-04] | Moderator (OPPO) |
| R1-2007121 | Text Proposal for TS 38.211 in [102-e-NR-eMIMO-05] | Moderator (OPPO) |
| R1-2007122 | Text Proposal for TS 38.213 in [102-e-NR-eMIMO-05] | Moderator (OPPO) |
| R1-2007123 | Text Proposal for TS 38.214 in [102-e-NR-eMIMO-05] | Moderator (OPPO) |
| R1-2007203 | LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission | RAN1, LG Electronics |
| R1-2007245 | Reply LS on feasibility of UL FPT modes and transparent TxD for certain UE implementations | RAN1, Huawei |
| R1-2007288 | Text proposal on MB.10 issue for Rel.16 NR_eMIMO MB2 | Moderator (Apple) |
| R1-2007345 | Summary on 102-e-NR-eMIMO-08 | Moderator (vivo) |
| R1-2007379 | Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| 7.2.7 | Maintenance of UE Power Saving for NR | |
| R1-2005356 | Remaining issues for Rel-16 UE power saving | vivo |
| R1-2005519 | Remaining issues on Rel-16 power saving | ZTE |
| R1-2005680 | Remaining issues on UE Power Saving | CATT |
| R1-2005804 | Remaining issues on PDCCH based power saving | Huawei, HiSilicon |
| R1-2005854 | Remaining issues on UE Power Saving for NR | Intel Corporation |
| R1-2005957 | TP on DRX adaptation for alignment | NEC |
| R1-2006119 | On maintenance of UE power saving | Samsung |
| R1-2006289 | Remaining issues on UE power saving | Spreadtrum Communications |
| R1-2006662 | Maintenance for UE power savings | Ericsson |
| R1-2006702 | Maintenance for UE power saving | NTT DOCOMO, INC. |
| R1-2006783 | Remainign issues in Rel-16 UE power saving | Qualcomm Incorporated |
| R1-2006894 | On open issues related to Rel-16 UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2007281 | Summary of NR UE power saving [102-e_NR_NR_UE_Pow_Sav_01] | Moderator (CATT) |
| R1-2007282 | Summary of NR UE power saving [102-e_NR_NR_UE_Pow_Sav_02] | Moderator (CATT) |
| R1-2007360 | DL Channel Combination associated with DCI format 2_6 monitoring | Moderator (CATT) |
| R1-2007361 | Alignment of RRC parameter ps-RNTI | Moderator (CATT) |
| R1-2007362 | Type-3 CSS monitoring with PS-RNTI on primary cell | Moderator (CATT) |
| R1-2007363 | RRM measurements when drx-onDurationTimer does not start | Moderator (CATT) |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2005357 | Remaining issues on DL RS for NR positioning | vivo |
| R1-2005358 | Remaining issues on physical layer procedure for NR positioning | vivo |
| R1-2005452 | Maintenance of NR positioning | ZTE |
| R1-2005681 | Remaining issues on DL PRS and measurements for NR Positioning | CATT |
| R1-2005682 | Remaining issues on UL SRS and UL procedures for NR Positioning | CATT |
| R1-2005780 | Discussion on QCL for PRS | ZTE |
| R1-2005795 | NR positioning corrections | Huawei, HiSilicon |
| R1-2005806 | RAN1 inputs to RAN3 on SRS support | Huawei, HiSilicon |
| R1-2005978 | Remaining Issues on measurements and procedure for NR Positioning | OPPO |
| R1-2005979 | Remaining Issues on RS for Positioning | OPPO |
| R1-2006120 | On remaining issues for Rel.16 positioning | Samsung |
| R1-2006199 | Remaining issues on DL PRS processing order | CMCC |
| R1-2006372 | Discussion on remaining issues on simultaneous SRS transmission and PRS processing priority for NR positioning | LG Electronics |
| R1-2006373 | Discussion on remaining issues on QCL and spatial relation information for NR positioning | LG Electronics |
| R1-2006425 | Maintenance on measurements for NR positioning | Nokia, Nokia Shanghai Bell |
| R1-2006426 | Priority of Assistance Data | Nokia, Nokia Shanghai Bell |
| R1-2006784 | Maintenance on DL Reference Signals for NR Positioning | Qualcomm Incorporated |
| R1-2006911 | Maintenance of rel16 reference signals for NR positioning | Ericsson |
| R1-2006912 | Maintenance of rel16 Physical-layer procedures to support UE - gNB measurements | Ericsson |
| R1-2006996 | Feature lead summary for NR positioning maintenance AI 7.2.8 | Moderator (Intel), Ericsson, CATT, Qualcomm |
| R1-2007095 | Summary of Email Discussion [102-e-NR-Pos-03] NR positioning measurements | Moderator (Qualcomm) |
| R1-2007104 | Feature lead summary for maintenance of UL SRS and L1 procedures for NR positioning | Moderator (Ericsson) |
| R1-2007125 | Feature lead summary #1 for email discussion [102-e-NR-Pos-01] | Moderator (Intel) |
| R1-2007380 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| 7.2.9 | Maintenance of NR Mobility Enhancements | |
| R1-2005422 | Remaining issues on NR mobility enhancements in physical layer | ZTE |
| R1-2005627 | Remaining issues on Rel-16 mobility enhancement | MediaTek Inc. |
| R1-2005794 | Remaining issues on DAPS-HO | Huawei, HiSilicon |
| R1-2005843 | Remaining issues on mobility enhancements | Ericsson |
| R1-2005855 | corrections to NR mobility enhancements | Intel Corporation |
| R1-2005942 | Issue summary for Rel-16 NR mobility enhancements | Moderator (Intel Corporation) |
| R1-2006121 | Remaining issues on NR Mobility Enhancements | Samsung |
| R1-2006498 | Remaining issue on NR mobility enhancements | Apple |
| R1-2006785 | Maintenance on NR mobility enhancements | Qualcomm Incorporated |
| R1-2006895 | Remaining physical layer aspects of dual active protocol stack based HO | Nokia, Nokia Shanghai Bell |
| R1-2007039 | Discussion summary of [102-e-NR-Mob-Enh-01] | Moderator (Intel Corporation) |
| R1-2007040 | Discussion summary of [102-e-NR-Mob-Enh-02] | Moderator (Intel Corporation) |
| R1-2007079 | Discussion summary#2 of [102-e-NR-Mob-Enh-01] | Moderator (Intel Corporation) |
| R1-2007080 | Discussion summary#2 of [102-e-NR-Mob-Enh-02] | Moderator (Intel Corporation) |
| R1-2007247 | Discussion summary#3 of [102-e-NR-Mob-Enh-01] | Moderator (Intel Corporation) |
| R1-2007248 | Discussion summary#3 of [102-e-NR-Mob-Enh-02] | Moderator (Intel Corporation) |
| R1-2007365 | Discussion summary #4 of [102-e-NR-Mob-Enh-01] | Moderator (Intel Corporation) |
| R1-2007366 | Discussion summary #4 of [102-e-NR-Mob-Enh-02] | Moderator (Intel Corporation) |
| R1-2007381 | Session notes for 7.2.9 (Maintenance of NR Mobility Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2007398 | Discussion summary #5 of [102-e-NR-Mob-Enh-01] | Moderator (Intel Corporation) |
| R1-2007399 | Discussion summary #5 of [102-e-NR-Mob-Enh-02] | Moderator (Intel Corporation) |
| R1-2007433 | CR on correction half duplex operation during DAPS HO | Moderator (Intel Corporation) |
| R1-2007434 | CR on correction on uplink power sharing for DAPS HO | Moderator (Intel Corporation) |
| R1-2007435 | CR on correction on PDCCH monitoring for DAPS HO | Moderator (Intel Corporation) |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2005359 | Remaining issues on Scell dormancy like behavior | vivo |
| R1-2005360 | Remaining issues on MR-DC | vivo |
| R1-2005420 | Remaining Issues of Power Control for NR-DC | ZTE |
| R1-2005421 | Remaining Issues of SCell Dormancy and Cross-carrier Scheduling | ZTE |
| R1-2005625 | Remaining issues on Rel-16 uplink power control for supporting NR-NR dual-connectivity | MediaTek Inc. |
| R1-2005626 | Remaining issues on Rel-16 carrier aggregation | MediaTek Inc. |
| R1-2005665 | PDCCH location for SCell dormancy | CATT |
| R1-2005788 | Remaining issues on CA | Huawei, HiSilicon |
| R1-2005805 | UL power control for NR-NR dual connectivity | Huawei, HiSilicon |
| R1-2005856 | Remaining issues on MR-DC & eCA | Intel Corporation |
| R1-2005958 | TP on SCell dormancy for alignment | NEC |
| R1-2005981 | Text proposals for UL Power Sharing for NR-DC | OPPO |
| R1-2006035 | Remaining issues for Scell dormancy | OPPO |
| R1-2006122 | Maintenance on UL Power Control for NR-DC | Samsung |
| R1-2006123 | On maintenance of Scell dormancy and CCS with different SCSs | Samsung |
| R1-2006285 | Remaining issues on Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements | Spreadtrum Communications |
| R1-2006297 | Remaining issue on cross-carrier scheduling with different numerology | LG Electronics |
| R1-2006430 | Remaining issues on Efficient CA design | Nokia, Nokia Shanghai Bell |
| R1-2006481 | Remaining issues of UL Power Control for NN-DC | Apple |
| R1-2006552 | Corrections for SCell Dormancy | Sharp |
| R1-2006663 | Maintenance for reduced latency Scell management for NR CA | Ericsson |
| R1-2006664 | Maintenance for remaining aspects of MR-DC | Ericsson |
| R1-2006752 | Feature lead summary #1 on UL Power Control for NN-DC | Moderator (Apple) |
| R1-2006753 | Remaining issue for cross-carrier scheduling | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2006786 | Remaining issues on SCell dormancy | Qualcomm Incorporated |
| R1-2006787 | Remaining issues on NR-DC power-control | Qualcomm Incorporated |
| R1-2006879 | Discussion for Rel-16 DC uplink power control | Nokia, Nokia Shanghai Bell |
| R1-2006974 | FL summary on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH | Moderator (Nokia) |
| R1-2006975 | FL summary on cross-carrier scheduling with different numerology | Moderator (Nokia) |
| R1-2006995 | Summary of efficient and low latency serving cell configuration/activation/setup | Moderator(Ericsson) |
| R1-2006999 | Outcome of preparation discussion on UL Power Control for NN-DC | Moderator (Apple) |
| R1-2007008 | FL summary on support of unaligned frame boundary for R16 NR inter-band CA | Moderator (CMCC) |
| R1-2007062 | Draft Summary of Email discussion [102-e-NR-MRDC-CA-Dormancy-01] | Moderator(Ericsson) |
| R1-2007142 | Outcome of email discussion on UL Power Control for NN-DC | Moderator (Apple Inc.) |
| R1-2007188 | Correction of uplink power control for NR-DC | Moderator (Apple Inc.) |
| R1-2007242 | [102-e-NR-MRDC-CA-Cross-CC-Unaligned-CA] email discussion summary | Moderator (Nokia) |
| R1-2007243 | Corrections on Cross-carrier Scheduling with Different Numerologies | Moderator (Nokia) |
| R1-2007261 | Reply LS on UL PC for NR-DC | RAN1, Apple |
| R1-2007351 | CR on Power Control for NR-DC | Moderator (Apple) |
| R1-2007382 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2007436 | Summary of Email discussion [102-e-NR-MRDC-CA-Dormancy-01] | Moderator (Ericsson) |
| R1-2007437 | Summary of Email discussion [102-e-NR-MRDC-CA-Dormancy-02] | Moderator (Ericsson) |
| R1-2007438 | CR to 38.212 on RRC parameter alignment for SCell dormancy | Moderator (Ericsson) |
| R1-2007439 | CR to 38.213 on RRC parameter alignment for SCell dormancy | Moderator (Ericsson) |
| R1-2007440 | CR to 38.213 on BWP triggering via SCell dormancy indication | Moderator (Ericsson) |
| R1-2007441 | CR to 38.213 on HARQ-ACK processing timeline for DCI format 1_1 with Scell dormancy indication without scheduling PDSCH | Moderator (Ericsson) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2005294 | Remaining details of features for Rel-16 V2X | FUTUREWEI |
| R1-2005361 | Remaining issues on Rel-16 UE features | vivo |
| R1-2005423 | Discussion on NR Rel-16 UE Features | ZTE |
| R1-2005666 | Remaining issues on Rel-16 UE features | CATT |
| R1-2005781 | Views on Rel-16 UE features | MediaTek Inc. |
| R1-2005814 | Remaining details of Rel-16 NR UE features | Huawei, HiSilicon |
| R1-2005857 | Rel-16 UE feature | Intel Corporation |
| R1-2005944 | Summary of UE features for IAB | Moderator (AT&T) |
| R1-2005945 | Remaining details of UE features for IAB | AT&T |
| R1-2005946 | Summary of UE features for 5G V2X | Moderator (AT&T) |
| R1-2005947 | Summary of UE features for eMIMO | Moderator (AT&T) |
| R1-2005948 | Summary of UE features for UE power savings | Moderator (AT&T) |
| R1-2005949 | Summary of UE features for NR mobility enhancements | Moderator (AT&T) |
| R1-2005980 | Discussion on Rel-16 UE features | OPPO |
| R1-2006003 | Discussion on remaining issues of NR feature list for 5G_V2X_NRSL | OPPO |
| R1-2006124 | Remaining issues on NR Rel-16 UE features | Samsung |
| R1-2006195 | LS on UE behavior for P/SP-CSI-RS reception in NR-U | RAN1, MediaTek Inc. |
| R1-2006462 | Updated RAN1 UE features list for Rel-16 NR | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2006482 | Discussions on NR Rel-16 UE features | Apple |
| R1-2006646 | Discussion on NR Rel-16 UE features | LG Electronics |
| R1-2006677 | Remaining aspects of Rel-16 UE features | Nokia, Nokia Shanghai Bell |
| R1-2006703 | Discussion on NR Rel-16 UE features | NTT DOCOMO, INC. |
| R1-2006704 | Summary on [101-e-Post-NR-UE-Features-11] | Moderator (NTT DOCOMO, INC.) |
| R1-2006705 | Summary on [101-e-Post-NR-UE-Features-12] | Moderator (NTT DOCOMO, INC.) |
| R1-2006706 | Summary on [101-e-Post-NR-UE-Features-13] | Moderator (NTT DOCOMO, INC.) |
| R1-2006707 | Summary on [101-e-Post-NR-UE-Features-14] | Moderator (NTT DOCOMO, INC.) |
| R1-2006708 | Summary on UE features for two-step RACH | Moderator (NTT DOCOMO, INC.) |
| R1-2006709 | Summary on UE features for NR-U | Moderator (NTT DOCOMO, INC.) |
| R1-2006710 | Summary on UE features for URLLC/IIoT | Moderator (NTT DOCOMO, INC.) |
| R1-2006711 | Summary on UE features for NR positioning | Moderator (NTT DOCOMO, INC.) |
| R1-2006712 | Summary on UE features for MR-DC/CA | Moderator (NTT DOCOMO, INC.) |
| R1-2006713 | Summary on UE features for CLI/RIM | Moderator (NTT DOCOMO, INC.) |
| R1-2006714 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2006715 | Summary on NR UE features for others | Moderator (NTT DOCOMO, INC.) |
| R1-2006788 | Discussion on NR Rel-16 UE features | Qualcomm Incorporated |
| R1-2006874 | Remaining details of Rel-16 NR UE features | Ericsson |
| R1-2006954 | Summary on [101-e-Post-NR-UE-Features-08] | Moderator (AT&T) |
| R1-2006955 | Summary on [101-e-Post-NR-UE-Features-09] | Moderator (AT&T) |
| R1-2006956 | Summary on [101-e-Post-NR-UE-Features-10] | Moderator (AT&T) |
| R1-2007012 | Summary on [102-e-NR-UEFeatures-2Step-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007013 | Summary on [102-e-NR-UEFeatures-NRU-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007014 | Summary on [102-e-NR-UEFeatures-NRU-02] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007015 | Summary on [102-e-NR-UEFeatures-URLLC/IIoT-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007016 | Summary on [102-e-NR-UEFeatures-URLLC/IIoT-02] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007017 | Summary on [102-e-NR-UEFeatures-Positioning-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007018 | Summary on [102-e-NR-UEFeatures-MRDCCA-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007019 | Summary on [102-e-NR-UEFeatures-CLI/RIM-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007020 | Summary on [102-e-NR-UEFeatures-TEI-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007021 | Summary on [102-e-NR-UEFeatures-TEI-02] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007022 | Summary on [102-e-NR-UEFeatures-Others-01] 7.2.11 | Moderator (NTT DOCOMO) |
| R1-2007136 | LS on updated Rel-16 RAN1 UE features lists for NR | RAN1, AT&T, NTT DOCOMO |
| R1-2007137 | Updated RAN1 UE features list for Rel-16 NR | Moderators (AT&T, NTT DOCOMO) |
| R1-2007138 | Updated RAN1 UE features list for Rel-16 NR including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO) |
| R1-2007204 | Summary of email discussion/approval [102-e-NR-UEFeatures-PowSav-01] | Moderator (AT&T) |
| R1-2007205 | Summary of email discussion/approval [102-e-NR-UEFeatures-MobEnh-01] | Moderator (AT&T) |
| R1-2007206 | Summary of email discussion/approval [102-e-NR-UEFeatures-MobEnh-02] | Moderator (AT&T) |
| R1-2007207 | Session Notes of AI 7.2.11 | Ad-Hoc Chair (AT&T) |
| R1-2007326 | Updated RAN1 UE features list for Rel-16 NR including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO) |
| R1-2007327 | LS on updated Rel-16 RAN1 UE features lists for NR | RAN1, AT&T, NTT DOCOMO |
| R1-2007339 | Reply LS on UE capability | RAN1, OPPO |
| R1-2007450 | Session Notes for NR UE Features | Ad-Hoc (NTT DOCOMO) |
| 7.2.12 | Other | |
| R1-2005362 | Discussion on flexible NR bandwidth | vivo |
| R1-2005453 | Maintenance of Rel-16 NR TEIs | ZTE |
| R1-2005982 | Discussion on the introduction of new bandwidths of CSI-RS for tracking | OPPO |
| R1-2006408 | Flexible TRS bandwidth configuration for 10 MHz in Rel-16 | Huawei, HiSilicon |
| R1-2006431 | On remaining NR TEI issues | Nokia, Nokia Shanghai Bell |
| R1-2006585 | Discussion on UCI bit sequence generation | ASUSTeK |
| R1-2006716 | Summary on Rel-16 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2006789 | Discussion of flexible NR UE bandwidth TEI and UL skipping | Qualcomm Incorporated |
| R1-2006837 | Discussion of flexible NR UE bandwidth TEI and UL skipping | Qualcomm Incorporated |
| R1-2006906 | Introduction of Flexible TRS bandwidth for BWP of 52 RBs | Vodafone |
| R1-2006964 | Discussion on UCI bit sequence generation | ASUSTeK |
| R1-2007023 | Summary on [102-e-NR-TEIs-01] 7.2.12 | Moderator (NTT DOCOMO) |
| R1-2007024 | Summary on [102-e-NR-TEIs-02] 7.2.12 | Moderator (NTT DOCOMO) |
| R1-2007324 | Correction on aperiodic CSI-RS triggering with beam switching timing of 224 and 336 | Moderator (NTT DOCOMO) |
| R1-2007325 | Introduction of flexible TRS bandwidth for BWP of 52 RBs | Moderator (NTT DOCOMO) |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2006125 | High-level work plan for Rel.17 FeMIMO WI | Moderator (Samsung) |
| R1-2006126 | Moderator summary for Rel.17 FeMIMO EVM offline | Moderator (Samsung) |
| R1-2007383 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2005246 | Enhancements on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2005290 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2005363 | Discussion on multi beam enhancement | vivo |
| R1-2005454 | Enhancements on Multi-beam Operation | ZTE |
| R1-2005482 | Enhancements on Multi-beam Operation | InterDigital, Inc. |
| R1-2005560 | Considerations on the enhancement of multi-beam operation | Sony |
| R1-2005619 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2005683 | Discussion on enhancement on multi-beam operation | CATT |
| R1-2005750 | Discussion on multi-beam operation | NEC |
| R1-2005782 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005820 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2005842 | Enhancements to multi-beam operation | Ericsson |
| R1-2005858 | Enhancements on Multi-Beam Operation | Intel Corporation |
| R1-2005954 | Enhancements on Multi-Beam Operation | AT&T |
| R1-2005983 | Enhancements on Multi-beam Operation | OPPO |
| R1-2006127 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2006128 | Multi-Beam Enhancements | Samsung |
| R1-2006200 | Enhancements on multi-beam operation | CMCC |
| R1-2006248 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2006499 | On Beam Management enhancement | Apple |
| R1-2006540 | Enhancements on multi-beam operation | Beijing Xiaomi Electronics |
| R1-2006565 | Enhancement on multi-beam operation for UE with multi-panel | Sharp |
| R1-2006596 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2006636 | Discussion on Enhancements for Multi-beam Operation | Asia Pacific Telecom co. Ltd |
| R1-2006717 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2006790 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2006843 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2006950 | Enhancements on Multi-Beam Operation | Intel Corporation |
| R1-2006951 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2006985 | Moderator summary for multi-beam enhancement: proposal categorization | Moderator (Samsung) |
| R1-2006991 | Multi-Beam Enhancements | Samsung |
| R1-2007151 | Moderator summary#2 for multi-beam enhancement: EVM | Moderator (Samsung) |
| R1-2007189 | Moderator summary#2 for multi-beam enhancement: category | Moderator (Samsung) |
| R1-2007370 | Moderator summary for multi-beam enhancement: advanced beam acquisition | Moderator (Samsung) |
| 8.1.2 | Enhancements for Multi-TRP Deployment | |
| R1-2006718 | Discussion on UL dense deployment | NTT DOCOMO, INC. |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2005285 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2005364 | Discussion on enhancement on PDCCH, PUCCH, PUSCH in MTRP scenario | vivo |
| R1-2005455 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2005483 | Discussion on Multi-TRP Physical Channel Enhancements | InterDigital, Inc. |
| R1-2005542 | Enhancements on Multi-TRP for PUCCH and PUSCH | Fujitsu |
| R1-2005561 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2005621 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | MediaTek Inc. |
| R1-2005684 | Discussion on enhancements on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2005728 | Discussion on multi-TRP enhancement | China Telecom |
| R1-2005751 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2005783 | On multi-TRP enhancements for PDCCH and PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005821 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2005859 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2005984 | Enhancements on Multi-TRP based enhancement for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2006129 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2006201 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2006258 | Discussion on enhancements on multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2006365 | Discussion on Multi-TRP | TCL Communication Ltd. |
| R1-2006367 | On PDCCH, PUCCH and PUSCH robustness | Ericsson |
| R1-2006391 | Enhancements on Multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2006500 | On multi-TRP reliability enhancement | Apple |
| R1-2006543 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Beijing Xiaomi Electronics |
| R1-2006566 | Enhancement on multi-TRP operation for PDCCH and PUSCH | Sharp |
| R1-2006597 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2006627 | Multi-TRP Enhancements for PDCCH, PUCCH and PUSCH | Convida Wireless |
| R1-2006637 | Discussion on enhancements on multi-TRP for uplink channels | Asia Pacific Telecom co. Ltd |
| R1-2006719 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2006791 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2006844 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2006868 | Discussion on enhancement on M-TRP | ASUSTeK |
| R1-2006901 | Discussion on multi-TRP/multi-panel transmission | TCL Communication Ltd. |
| R1-2007179 | Summary of EVM discussion for mTRP PDCCH reliability enhancements | Moderator (Qualcomm) |
| R1-2007180 | Summary #1 of email discussion [102-e-NR-feMIMO-02] | Moderator (Qualcomm) |
| R1-2007181 | Summary #2 of email discussion [102-e-NR-feMIMO-02] | Moderator (Qualcomm) |
| R1-2007182 | Summary of AI:8.1.2.1 Enhancements for Multi-TRP URLLC for PUCCH and PUSCH | Moderator (Nokia, Nokia Shanghai Bell) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2005286 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2005365 | Discussion on inter-cell MTRP operation | vivo |
| R1-2005456 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2005484 | TCI/QCL Enhancements for M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2005562 | Considerations on inter-cell operation | Sony |
| R1-2005685 | Discussion on multi-TRP/panel inter-cell operation | CATT |
| R1-2005822 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2005860 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2005985 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2006130 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2006202 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2006259 | Discussion on enhancement multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2006368 | On inter-cell operation for mTRP | Ericsson |
| R1-2006392 | Enhancements on inter-cell Multi-TRP operations in Rel-17 | Huawei, HiSilicon |
| R1-2006501 | On Inter-cell multi-TRP operation | Apple |
| R1-2006545 | Enhancement on Inter-cell Multi-TRP operations | Beijing Xiaomi Electronics |
| R1-2006567 | Enhancement on inter-cell multi-TRP operation | Sharp |
| R1-2006598 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2006720 | Discussion on inter-cell multi-TRP operations | NTT DOCOMO, INC. |
| R1-2006792 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2006845 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2007313 | Feature lead summary on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2005287 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2005366 | Discussion on MTRP multibeam enhancement | vivo |
| R1-2005457 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2005485 | Discussion on Beam Management Enhancements for Multi-TRP | InterDigital, Inc. |
| R1-2005563 | Considerations on beam management for multi-TRP | Sony |
| R1-2005620 | Enhancements on beam management for multi-TRP | MediaTek Inc. |
| R1-2005686 | Discussion on enhancements on beam management for multi-TRP | CATT |
| R1-2005752 | Discussion on beam management for multi-TRP | NEC |
| R1-2005784 | On beam management enhancements for multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005823 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2005861 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2005955 | Views on beam management enhancement for multi-TRP | AT&T |
| R1-2005986 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2006131 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2006203 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2006260 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2006393 | Enhancements on multi-TRP for multi-panel reception in Rel-17 | Huawei, HiSilicon |
| R1-2006502 | On multi-TRP BM enhancement | Apple |
| R1-2006546 | Enhancement on beam management for Multi-TRP | Beijing Xiaomi Electronics |
| R1-2006599 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2006638 | Discussion of enhancements on beam management for multi-TRP | Asia Pacific Telecom co. Ltd |
| R1-2006654 | Discussion on beam management for Multi-TRP | ITRI |
| R1-2006681 | On beam management enhancements for simultaneous multi-TRP transmission with multi-panel reception | Ericsson |
| R1-2006721 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2006793 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2006846 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2007294 | Summary on email discussion on beam management for simultaneous multi-TRP transmission with multiple Rx panels | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2005367 | Evaluation and discussion on HST-SFN schemes | vivo |
| R1-2005458 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2005486 | Enhanced M-TRP for HST-SFN | InterDigital, Inc. |
| R1-2005564 | Considerations on HST-SFN operation for multi-TRP | Sony |
| R1-2005592 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2005687 | Discussion on enhancements on HST-SFN deployment | CATT |
| R1-2005753 | Discussion on HST-SFN deployment | NEC |
| R1-2005862 | On HST SFN enhancements | Intel Corporation |
| R1-2005925 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2005987 | Enhancements on HST-SFN deployment | OPPO |
| R1-2006132 | Enhancements on HST-SFN | Samsung |
| R1-2006204 | Enhancements on HST-SFN deployment | CMCC |
| R1-2006261 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2006394 | Enhancements on Multi-TRP for high speed train in Rel-17 | Huawei, HiSilicon |
| R1-2006475 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2006503 | Views on Rel-17 HST enhancement | Apple |
| R1-2006600 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2006722 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2006794 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2006847 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2007201 | Summary of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2007244 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2007315 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2007393 | Summary of HST-SFN evaluation assumptions after RAN1#102-e | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2005247 | Enhancements on SRS for Rel-17 | Huawei, HiSilicon |
| R1-2005288 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2005368 | Discussion on SRS enhancement | vivo |
| R1-2005459 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2005487 | Discussion on SRS Enhancements | InterDigital, Inc. |
| R1-2005565 | Considerations on SRS flexibility, coverage and capacity | Sony |
| R1-2005622 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2005688 | Discussion on enhancements on SRS flexibility, coverage and capacity | CATT |
| R1-2005754 | Discussion on SRS enhancement | NEC |
| R1-2005824 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2005863 | Discussion on SRS enhancements | Intel Corporation |
| R1-2005988 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2006133 | Enhancements on SRS | Samsung |
| R1-2006205 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2006255 | Considerations on SRS enhancement | Spreadtrum Communications |
| R1-2006364 | Discussion on enhancement of SRS in Rel. 17 further enhanced MIMO | CEWiT |
| R1-2006504 | Views on Rel-17 SRS enhancement | Apple |
| R1-2006568 | Enhancement on SRS | Sharp |
| R1-2006601 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2006610 | SRS Performance and Potential Enhancements | Ericsson |
| R1-2006723 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2006795 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2006848 | Enhancements on SRS in Rel-17 | Nokia, Nokia Shanghai Bell |
| R1-2006963 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2007076 | FL summary on SRS enhancements | Moderator (ZTE) |
| R1-2007173 | FL summary#2 on SRS enhancements | Moderator (ZTE) |
| R1-2007234 | FL summary#3 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2005248 | Enhancements on CSI for Rel-17 | Huawei, HiSilicon |
| R1-2005289 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2005369 | Evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2005460 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2005488 | On Type II Port Selection Codebook Enhancement | InterDigital, Inc. |
| R1-2005566 | Considerations on CSI enhancements | Sony |
| R1-2005623 | CSI enhancement for NCJT | MediaTek Inc. |
| R1-2005689 | CSI enhancements on for MTRP and FR1 FDD with partial reciprocity | CATT |
| R1-2005755 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2005785 | On FDD channel reciprocity in real-world scenarios | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005864 | On CSI enhancements for MTRP and FDD reciprocity | Intel Corporation |
| R1-2005926 | CSI enhancements for mTRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2005956 | CSI enhancements: FDD reciprocity and multi-TRP | AT&T |
| R1-2005989 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2006134 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2006206 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2006262 | Discussion on CSI enhancement for multiple TRP/Panel transmission | Spreadtrum Communications |
| R1-2006505 | Views on Rel-17 CSI enhancement | Apple |
| R1-2006569 | Enhancement on CSI measurement and reporting | Sharp |
| R1-2006602 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2006685 | On CSI enhancements in Rel-17 feMIMO | Ericsson |
| R1-2006724 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2006796 | CSI enhancements for MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2006849 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2006973 | Discussion Summary for CSI enhancements MTRP and FR1 FDD reciprocity | Moderator (Huawei) |
| R1-2006998 | On FDD channel reciprocity in real-world scenarios | Fraunhofer IIS, Fraunhofer HHI |
| R1-2007268 | Technical Categorization for CSI enhancements for MTRP and FR1 FDD reciprocity | Huawei |
| 8.1.5 | Other | |
| R1-2005291 | Sounding enhancement for interference probing in TDD cooperative MIMO | FUTUREWEI |
| R1-2005370 | Discussion on higher layer aspects for multi-TRP enhancement | vivo |
| R1-2005461 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2005489 | Evaluation of Multi-TRP MIMO Deployment with Multi-panel UEs | InterDigital, Inc. |
| R1-2005825 | HARQ feedback of SPS PDSCH reception in multi-DCI based multiple TRPs | Lenovo, Motorola Mobility |
| R1-2006135 | Simulation results for multi-beam enhancements | Samsung |
| R1-2006369 | Critical MIMO issue from observations in field | Ericsson |
| R1-2006414 | Discussion on field measurement and evaluation assumptions for FDD CSI enhancements in Rel-17 | Huawei, HiSilicon |
| R1-2006570 | Considerations on TRS for HST-SFN scenario | Sharp |
| R1-2006838 | Discussion of further enhancements on MIMO for NR | Qualcomm Incorporated |
| R1-2006949 | Critical MIMO issue from observations in field | Ericsson LM |
| R1-2006965 | Discussion on field measurement and evaluation assumptions for FDD CSI enhancements in Rel-17 | Huawei, HiSilicon |
| R1-2007011 | Simulation results for multi-beam enhancements | Samsung |
| 8.2 | Study on supporting NR from 52.6GHz to 71 GHz | |
| R1-2005865 | Draft TR 38.808 v002: Study on supporting NR from 52.6 GHz to 71 GHz | Intel Corporation |
| R1-2007340 | Draft TR 38.808 v002: Study on supporting NR from 52.6 GHz to 71 GHz | Intel Corporation |
| R1-2007384 | Session notes for 8.2 (Study on supporting NR from 52.6 GHz to 71 GHz) | Ad-Hoc Chair (Ericsson) |
| 8.2.1 | Required changes to NR using existing DL/UL NR waveform | |
| R1-2005239 | Discussion on potential physical layer impacts for NR beyond 52.6 GHz | Lenovo, Motorola Mobility |
| R1-2005241 | PHY design in 52.6-71 GHz using NR waveform | Huawei, HiSilicon |
| R1-2005280 | Considerations on phase noise for numerology selection | FUTUREWEI |
| R1-2005371 | Discussion on requried changes to NR using existing DL/UL NR waveform | vivo |
| R1-2005543 | Consideration on required changes to NR using existing NR waveform | Fujitsu |
| R1-2005567 | Considerations on bandwidth and subcarrier spacing for above 52.6 GHz | Sony |
| R1-2005607 | Discussion on the required changes to NR for above 52.6GHz | ZTE, Sanechips |
| R1-2005643 | On required changes to NR using existing DL/UL NR waveform for operation in 60GHz band | MediaTek Inc. |
| R1-2005699 | System Analysis of NR opration in 52.6 to 71 GHz | CATT |
| R1-2005734 | Physical layer design for NR 52.6-71GHz | Beijing Xiaomi Software Tech |
| R1-2005764 | Study on the required changes to NR using existing DL/UL NR waveform | NEC |
| R1-2005766 | Required changes to NR using existing DL/UL NR waveform | TCL Communication Ltd. |
| R1-2005787 | On phase noise compensation for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2005866 | Discussion on Required Changes to NR in 52.6 – 71 GHz | Intel Corporation |
| R1-2005920 | On NR operations in 52.6 to 71 GHz | Ericsson |
| R1-2006026 | discusson on DL/UL NR waveform for 52.6GHz to 71GHz | OPPO |
| R1-2006136 | Design aspects for extending NR to up to 71 GHz | Samsung |
| R1-2006237 | Required changes to NR using existing DL/UL NR waveform in 52.6GHz ~ 71GHz | CMCC |
| R1-2006274 | Discussion on required changes to NR using existing NR waveform | Spreadtrum Communications |
| R1-2006304 | Consideration on required physical layer changes to support NR above 52.6 GHz | LG Electronics |
| R1-2006452 | Consideration on supporting above 52.6GHz in NR | InterDigital, Inc. |
| R1-2006512 | On Required changes to NR above 52.6 GHz using the existing DL/UL NR Waveform | Apple |
| R1-2006628 | On NR operation between 52.6 GHz and 71 GHz | Convida Wireless |
| R1-2006649 | 60 GHz DL and UL waveform evaluations | Charter Communications |
| R1-2006725 | Evaluation Methodology and Required Changes on NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2006797 | NR using existing DL-UL NR waveform to support operation between 52p6 GHz and 71 GHz | Qualcomm Incorporated |
| R1-2006853 | Discussions on required changes on supporting NR from 52.6GHz to 71 GHz | CAICT |
| R1-2006885 | Discussion on physical layer aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2006907 | Required changes to NR using existing DL/UL NR waveform | Nokia, Nokia Shanghai Bell |
| R1-2006982 | Issue Summary for physical layer changes for supporting NR from 52.6 GHz to 71 GHz | Moderator (Intel Corporation) |
| R1-2006986 | Discussion on Required Changes to NR in 52.6 – 71 GHz | Intel Corporation |
| R1-2006989 | On required changes to NR using existing DL/UL NR waveform for operation in 60GHz band | MediaTek Inc. |
| R1-2007038 | Discussion summary of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| R1-2007046 | On NR operations in 52.6 to 71 GHz | Ericsson |
| R1-2007109 | Discussion summary#2 of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| R1-2007246 | Discussion summary#3 of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| R1-2007289 | Discussion summary#4 of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| R1-2007364 | Discussion summary #5 of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| R1-2007397 | Discussion summary #6 of [102-e-NR-52-71-Waveform-Changes] | Moderator (Intel Corporation) |
| 8.2.2 | Channel access mechanism | |
| R1-2005240 | Discussion on channel access for NR beyond 52.6 GHz | Lenovo, Motorola Mobility |
| R1-2005242 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2005282 | Considerations on directional LBT and spatial reuse | FUTUREWEI |
| R1-2005323 | Considerations on channel access mechanism | Transsion Holdings |
| R1-2005372 | Discussion on channel access mechanism | vivo |
| R1-2005568 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2005608 | Discussion on the channel access mechanism for above 52.6GHz | ZTE, Sanechips |
| R1-2005700 | Channel Access Mechanism in support of NR operation in 52.6 to 71 GHz | CATT |
| R1-2005735 | Channel access mechanism for NR on 52.6-71 GHz | Beijing Xiaomi Software Tech |
| R1-2005765 | Study on the channel access mechanism | NEC |
| R1-2005767 | Channel access mechanism | TCL Communication Ltd. |
| R1-2005867 | Channel Access Procedure for NR in 52.6 - 71 GHz | Intel Corporation |
| R1-2005921 | Channel Access Mechanism | Ericsson |
| R1-2005950 | Channel access mechanisms for NR from 52.6-71GHz | AT&T |
| R1-2006027 | discussion on channel access mechanism | OPPO |
| R1-2006137 | Channel access mechanism for 60 GHz unlicensed spectrum | Samsung |
| R1-2006275 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2006305 | Considerations on channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2006453 | On Channel access mechanisms | InterDigital, Inc. |
| R1-2006513 | On Channel Access Mechanisms for Unlicensed Access above 52.6 GHz | Apple |
| R1-2006571 | Channel access mechanism | Sharp |
| R1-2006629 | On Channel Access for NR Supporting From 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2006650 | Channel access considerations for the indoor scenario | Charter Communications |
| R1-2006655 | Discussion on channel access mechanism | ITRI |
| R1-2006726 | Channel Access Mechanism for NR in 60 GHz unlicensed spectrum | NTT DOCOMO, INC. |
| R1-2006798 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2006854 | Discussions on channel access mechanism on supporting NR from 52.6GHz to 71 GHz | CAICT |
| R1-2006871 | Discussion on channel access mechanism for NR from 52.6GHz to 71 GHz | Potevio |
| R1-2006886 | Discussion on channel access for NR-unlicensed beyond 52.6GHz | WILUS Inc. |
| R1-2006908 | NR coexistence mechanisms for 60 GHz unlicensed band | Nokia, Nokia Shanghai Bell |
| R1-2006994 | FL summary for channel access mechanism for 52.6GHz to 71GHz | Moderator (Qualcomm) |
| R1-2007094 | Email discussion summary on channel access of 52.6-71GHz band | Moderator (Qualcomm) |
| R1-2007193 | Email discussion summary on channel access of 52.6-71GHz band | Moderator (Qualcomm) |
| R1-2007483 | [102-e-Post-NR-CovEnh-02] Phase 3: initial collection of simulation results for enhancements | Moderator (China Telecom) |
| 8.2.3 | Other | |
| R1-2005373 | Evaluation on different numerologies for NR using existing DL/UL NR waveform | vivo |
| R1-2005609 | Preliminary simulation results for above 52.6GHz | ZTE, Sanechips |
| R1-2005868 | Considerations on performance evaluation for NR in 52.6-71GHz | Intel Corporation |
| R1-2005922 | On phase noise compensation for OFDM | Ericsson |
| R1-2006028 | discussion on other aspects | OPPO |
| R1-2006138 | Remaining details on evaluation assumptions | Samsung |
| R1-2006454 | Evaluation results for above 52.6GHz in NR | InterDigital, Inc. |
| R1-2006727 | Potential Enhancements for NR on 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2006909 | Simulation Results for NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2006928 | Link level and System level evaluation for NR system operating in 52.6GHz to 71GHz | Huawei, HiSilicon |
| R1-2007009 | Summary of evaluation related issues on supporting NR from 52.6 GHz to 71 GHz | Moderator (vivo) |
| R1-2007047 | On phase noise compensation for OFDM | Ericsson |
| R1-2007078 | Discussion summary of [102-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2007126 | Discussion summary#2 of [102-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2007292 | Discussion summary#3 of [102-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2007342 | Discussion summary#4 of [102-e-NR-52-71-Evaluations] | Moderator (vivo) |
| R1-2007485 | Collection of evaluation results on supporting NR from 52.6 GHz to 71 GHz | Moderator (vivo) |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2006338 | Work Plan for Rel-17 NR IIoT/URLLC Enhancements WI | Nokia, Nokia Shanghai Bell |
| 8.3.1.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2005243 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2005374 | HARQ-ACK enahncements for Rel-17 URLLC | vivo |
| R1-2005431 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2005513 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2005569 | HARQ-ACK enhancement to reduce retransmission time | Sony |
| R1-2005633 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2005701 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2005760 | Enhancements on URLLC HARQ-ACK feedback | NEC |
| R1-2005869 | UE HARQ feedback enhancements in Release 17 URLLC/IIoT | Intel Corporation |
| R1-2005929 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2005967 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2006058 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2006070 | UE HARQ-ACK feedback enhancements | InterDigital, Inc. |
| R1-2006139 | HARQ-ACK feedback enhancements for Rel-17 URLLC/IIoT | Samsung |
| R1-2006207 | Discussion on UE feedback enhancements for HARQ-ACK | CMCC |
| R1-2006252 | Discussion on necessity and support of physical layer feedback enhancements | Spreadtrum Communications |
| R1-2006314 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2006339 | On the necessity and support of Rel-17 URLLC HARQ-ACK feedback enhancements | Nokia, Nokia Shanghai Bell |
| R1-2006342 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic Corporation |
| R1-2006514 | UE feedback enhancements for HARQ-ACK | Apple |
| R1-2006572 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2006639 | Discussion on HARQ-ACK enhancements | Asia Pacific Telecom co. Ltd |
| R1-2006728 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2006799 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2006887 | Discussion on HARQ-ACK enhancement for IIoT/URLLC | WILUS Inc. |
| R1-2006899 | HARQ enhancement for SPS | Google, Inc. |
| R1-2007059 | Feature lead summary #1 on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2007107 | Feature lead summary #2 on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2007216 | Feature lead summary #3 on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2007354 | Feature lead summary #4 on Rel-17 HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.1.2 | CSI feedback enhancements | |
| R1-2005244 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2005281 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2005375 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2005432 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2005514 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2005552 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2005570 | Considerations on CSI feedback enhancements | Sony |
| R1-2005634 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2005702 | CSI feedback enhancements | CATT |
| R1-2005776 | CSI feedback enhancement | NEC |
| R1-2005870 | CSI feedback enhancements in Release 17 URLLC/IIoT | Intel Corporation |
| R1-2005930 | CSI feedback enhancements | Lenovo, Motorola Mobility |
| R1-2006059 | Enhancement for CSI feedback | OPPO |
| R1-2006071 | CSI feedback enhancements for enhanced URLLC/IIoT | InterDigital, Inc. |
| R1-2006140 | CSI feedback enhancements for URLLC | Samsung |
| R1-2006208 | Discussion on CSI feedback enhancements | CMCC |
| R1-2006276 | Discussion on CSI feedback enhancements | Spreadtrum Communications |
| R1-2006315 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2006343 | Discussion on CSI feedback enhancements | Panasonic Corporation |
| R1-2006515 | CSI feedback enhancements for URLLC | Apple |
| R1-2006573 | CSI feedback enhancements for eURLLC | Sharp, NICT |
| R1-2006729 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2006800 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2007064 | Feature lead summary #1 on CSI feedback enhancements for Rel-17 URLLC/IIoT | Moderator (InterDigital) |
| R1-2007110 | Feature lead summary #2 on CSI feedback enhancements for Rel-17 URLLC/IIoT | Moderator (InterDigital) |
| R1-2007286 | Feature lead summary#3 on CSI feedback enhancements for Rel-17 URLLC/IIoT | Moderator (InterDigital) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2005376 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2005433 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2005515 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2005571 | Enhancements for unlicensed band URLLC/IIoT | Sony |
| R1-2005635 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2005703 | Enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2005736 | UL transmission for URLLC on unlicensed band | Beijing Xiaomi Software Tech |
| R1-2005768 | Enhancements for unlicensed band URLLC/IIoT | TCL Communication Ltd. |
| R1-2005871 | Uplink enhancements for URLLC operating in unlicensed spectrum | Intel Corporation |
| R1-2005931 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2006060 | Enhancement for unlicensed band URLLC/IIoT | OPPO |
| R1-2006072 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2006141 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2006247 | On UL Enhancements for IIoT/URLLC in Unlicensed Controlled Environment | Nokia, Nokia Shanghai Bell |
| R1-2006277 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2006316 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2006344 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2006356 | Discussion on enhancements for URLLC in unlicensed bands | ETRI |
| R1-2006516 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2006574 | Potential enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2006651 | Considerations for unlicensed IIoT | Charter Communications |
| R1-2006730 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2006801 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2006888 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2006929 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2007069 | Summary#1 on enhancements for unlicensed band URLLC/IIoT for R17 | Moderator (Ericsson) |
| R1-2007228 | Summary#2 on enhancements for unlicensed band URLLC/IIoT for R17 | Moderator (Ericsson) |
| R1-2007301 | Summary#3 on enhancements for unlicensed band URLLC/IIoT for R17 | Moderator (Ericsson) |
| R1-2007332 | Summary#4 on enhancements for unlicensed band URLLC/IIoT for R17 | Moderator (Ericsson) |
| R1-2007391 | Summary#5 on enhancements for unlicensed band URLLC/IIoT for R17 | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2005245 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2005377 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2005434 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2005516 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2005572 | Considerations on intra-UE UL multiplexing & prioritisation | Sony |
| R1-2005636 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2005704 | Intra-UE multiplexing and prioritization | CATT |
| R1-2005737 | Intra-UE multiplexing/prioritization | Beijing Xiaomi Software Tech |
| R1-2005777 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2005872 | Intra-UE multiplexing and prioritization in Release 17 URLLC/IIoT | Intel Corporation |
| R1-2005932 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2006061 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2006073 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2006142 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2006209 | Discussion on intra-UE multiplexing/prioritization | CMCC |
| R1-2006251 | Discussion on Intra-UE Multiplexing/Prioritization | Spreadtrum Communications |
| R1-2006317 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2006340 | On Rel-17 UL intra-UE prioritization and multiplexing enhancements for traffic with different priorities | Nokia, Nokia Shanghai Bell |
| R1-2006345 | Discussion on Intra-UE multiplexing and prioritization of different priority | Panasonic Corporation |
| R1-2006517 | Intra-UE Multiplexing/Prioritization for URLLC | Apple |
| R1-2006575 | Enhancements on intra-UE multiplexing and prioritization | Sharp |
| R1-2006656 | Discussion on intra-UE multiplexing | ITRI |
| R1-2006731 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2006802 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2006870 | Intra-UE multiplexing for URLLC | Potevio |
| R1-2006889 | Discussion on Intra-UE multiplexing/prioritization for IIoT/URLLC | WILUS Inc. |
| R1-2007055 | Summary#1 on Intra-UE Multiplexing/Prioritization for R17 IIoT/URLLC | Moderator (OPPO) |
| R1-2007075 | Summary#1 of email thread [102-e-NR-IIOT_URLLC_enh-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2005378 | Other issues for Rel-17 URLLC | vivo |
| R1-2005435 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2005517 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2005705 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2006062 | Enhancement for Propagation Delay Compensation | OPPO |
| R1-2006143 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2006341 | Discussion on RAN1 involvement in propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2006357 | On processing time for shared COT acquisition for unlicensed URLLC in FBE | ETRI |
| R1-2006518 | Discussion on Orphan symbol handling for unlicensed spectrum | Apple |
| R1-2006803 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2006930 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2007068 | Summary#1 of email discussion [102-e-NR-IIOT_URLLC_enh-05] | Moderator (Huawei) |
| R1-2007445 | Draft LS on propagation delay compensation enhancements | Huawei |
| R1-2007446 | LS on propagation delay compensation enhancements | RAN1, Huawei |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2005306 | NR_NTN_solutions work plan | THALES |
| R1-2006676 | NR NTN Reference scenarios definition for Rel-17 normative phase | THALES |
| R1-2007385 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| 8.4.1 | Timing relationship enhancements | |
| R1-2005265 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2005495 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2005548 | NR-NTN: Timing Relationship Enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005573 | Calculation of timing relationship offsets | Sony |
| R1-2005706 | Timing relationship enhancement for NTN | CATT |
| R1-2005833 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2005873 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2005963 | Discussion on timing relationship for NTN | ZTE |
| R1-2006029 | discusson on timing relationship enhancement | OPPO |
| R1-2006144 | On Timing relationship enhancements | Samsung |
| R1-2006210 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2006325 | Timing relationship enhancement for NTN | Panasonic Corporation |
| R1-2006358 | Discussion on timing relationships for NTN | ETRI |
| R1-2006378 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2006421 | DL-UL timing relationship for NTN operation | Nokia, Nokia Shanghai Bell |
| R1-2006464 | On basic assumptions and timing relationship enhancements for NTN | Ericsson |
| R1-2006519 | On Timing Relationship Enhancement in NTN | Apple |
| R1-2006589 | Discussion on the timing relationship for NTN | Beijing Xiaomi Mobile Software |
| R1-2006640 | Discussion on timing relationship enhancements for NTN | Asia Pacific Telecom co. Ltd |
| R1-2006804 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2006855 | Timing relationship enhancements to support NTN | CAICT |
| R1-2006981 | Feature lead summary on timing relationship enhancements | Moderator (Ericsson) |
| R1-2007074 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2007176 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2007323 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2005266 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2005496 | UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc., Eutelsat |
| R1-2005502 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2005574 | Enhancement for UL time synchronization | Sony |
| R1-2005707 | Discussion for UL time and frequency compensation | CATT |
| R1-2005834 | Discussion on NTN TA indication | Lenovo, Motorola Mobility |
| R1-2005874 | On UL time and frequency synchronization for NTN | Intel Corporation |
| R1-2005902 | Discussion on PRACH sequences | Mitsubishi Electric RCE |
| R1-2005964 | Discussion on UL synchronization for NTN | ZTE |
| R1-2006030 | discussion on UL time and frequency synchronization | OPPO |
| R1-2006145 | On Enhancements on UL time and frequency synchronization | Samsung |
| R1-2006211 | Enhancements on uplink timing advance for NTN | CMCC |
| R1-2006326 | UL timing advance and frequency synchronization for NTN | Panasonic Corporation |
| R1-2006359 | Discussion on UL timing advance for NTN | ETRI |
| R1-2006379 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2006422 | Discussion on UL time and frequency synchronization for NTN | Nokia, Nokia Shanghai Bell |
| R1-2006520 | On Timing Advance for NTN | Apple |
| R1-2006603 | Discussion on UL time and frequency synchronization for NTN | Beijing Xiaomi Mobile Software |
| R1-2006619 | On UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2006641 | Discussion on UL time and frequency synchronization for NTN | Asia Pacific Telecom co. Ltd |
| R1-2006674 | Considerations on UL timing and frequency synchronization | THALES |
| R1-2006805 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2006856 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2007057 | Feature lead summary on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2007217 | Feature lead summary#2 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2007290 | Feature lead summary#3 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| 8.4.3 | Enhancements on HARQ | |
| R1-2005267 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2005302 | Evaluation assumptions for NR coverage enhancement evaluation | Nokia, Nokia Shanghai Bell |
| R1-2005312 | Discussion on HARQ for NTN | Nomor Research GmbH, Thales |
| R1-2005497 | HARQ in NR-NTN | MediaTek Inc. |
| R1-2005575 | Enhancements on delay-tolerant HARQ | Sony |
| R1-2005708 | HARQ operation enhancement for NTN | CATT |
| R1-2005835 | Enhancements on HARQ for NTN | Lenovo, Motorola Mobility |
| R1-2005875 | On HARQ enhancements for NTN | Intel Corporation |
| R1-2005965 | Discussion on HARQ for NTN | ZTE |
| R1-2006031 | discussion on HARQ enhancement | OPPO |
| R1-2006146 | On Enhancements on HARQ | Samsung |
| R1-2006212 | Enhancements on HARQ for NTN | CMCC |
| R1-2006327 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2006360 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2006380 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2006423 | Discussion on HARQ stalling avoidance | Nokia, Nokia Shanghai Bell |
| R1-2006465 | On HARQ enhancements for NTN | Ericsson |
| R1-2006521 | On HARQ Enhancement for NTN | Apple |
| R1-2006604 | Discussion on the enhancement on HARQ for NTN | Beijing Xiaomi Mobile Software |
| R1-2006642 | Discussion on HARQ enhancements for NTN | Asia Pacific Telecom co. Ltd |
| R1-2006806 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2006857 | Enhancements on HARQ to support NTN | CAICT |
| R1-2007056 | Summary of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2007196 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2007311 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| 8.4.4 | Other | |
| R1-2005268 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2005311 | Considerations on PAPR requirements for NR NTN downlink transmission | THALES |
| R1-2005313 | Study Cases for System-Level Simulations in NTN WI | Nomor Research GmbH, Thales |
| R1-2005498 | Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2005547 | NR-NTN: Physical Random Access Channel | Fraunhofer IIS, Fraunhofer HHI |
| R1-2005576 | Discussion on beam management and BWP operation for NTN | Sony |
| R1-2005709 | Discussion for beam management and feeder link switch enhancement | CATT |
| R1-2005836 | Discussion on NTN beam management | Lenovo, Motorola Mobility |
| R1-2005876 | On pre-compensation capabilities and beam management for NTN | Intel Corporation |
| R1-2005966 | Discussion on additional enhancement for NTN | ZTE |
| R1-2006032 | discussion on other aspects | OPPO |
| R1-2006147 | Remaining issues for NTN | Samsung |
| R1-2006213 | Discussion on implicit compatibility to support ATG scenarios in NTN | CMCC |
| R1-2006328 | Beam management, PRACH enhancement and polarization for NTN | Panasonic |
| R1-2006381 | Considerations on PRACH, CSI and polarization signaling in NTN | LG Electronics |
| R1-2006424 | Clarification of NTN assumptions | Nokia, Nokia Shanghai Bell |
| R1-2006466 | On other enhancements for NTN | Ericsson |
| R1-2006605 | Discussion on the beam management for NTN | Beijing Xiaomi Mobile Software |
| R1-2006620 | On feeder link switch | InterDigital, Inc. |
| R1-2006643 | Discussion on reference timing delivery for NTN | Asia Pacific Telecom co. Ltd |
| R1-2006678 | Other RAN1 aspects for NR NTN | THALES |
| R1-2006807 | SSB arrangements, BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2006858 | Discussion on beam management of NTN | CAICT |
| R1-2007002 | Summary of AI 8.4.4 on Others Aspects of NR NTN | Moderator (MediaTek) |
| R1-2007060 | Summary#2 of AI 8.4.4 on Others Aspects of NR NTN | Moderator (MediaTek) |
| R1-2007152 | Summary#3 of AI 8.4.4 on Others Aspects of NR NTN | Moderator (MediaTek) |
| R1-2007233 | Summary#4 of AI 8.4.4 on Others Aspects of NR NTN | Moderator (MediaTek) |
| 8.5 | Study on NR Positioning Enhancements | |
| R1-2006913 | TP for additional scenarios and channel models in TR 38.857 | Ericsson |
| R1-2007386 | Session notes for 8.5 (Study on NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2007486 | Outcome of RAN WG1 e-mail discussion [102-e-Post-NR-ePos-01] | Moderator (Intel Corporation) |
| 8.5.1 | Additional scenarios for evaluation | |
| R1-2005251 | Additional consideration on evaluation methodology | Huawei, HiSilicon |
| R1-2005283 | Remaining Issues on Evaluation Assumptions | FUTUREWEI |
| R1-2005379 | Discussion on additional scenarios for NR positioning evaluation | vivo |
| R1-2005462 | Evaluation assumptions for NR positioning enhancements | ZTE |
| R1-2005577 | Remaining Issues on Scenarios for Evaluation of NR Positioning | Sony |
| R1-2005710 | Remaining issues on additional scenarios for evaluation of NR Positioning Enhancements | CATT |
| R1-2005877 | Remaining details on additional scenarios for NR positioning evaluations | Intel Corporation |
| R1-2005990 | Discussion on Scenarios for Evaluation | OPPO |
| R1-2006066 | Additionnal scenarios for evaluation | BUPT |
| R1-2006148 | Additional scenarios for evaluation | Samsung |
| R1-2006214 | Remaining issues on target performance requirement of IIoT use case | CMCC |
| R1-2006238 | UE mobility model for evaluation | InterDigital, Inc. |
| R1-2006374 | Discussion on additional scenarios for evaluation for NR positioning | LG Electronics |
| R1-2006427 | Additional scenarios for evaluation of NR positioning | Nokia, Nokia Shanghai Bell |
| R1-2006458 | Additional scenarios for evaluation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2006808 | Considerations on Additional Scenarios for Evaluation | Qualcomm Incorporated |
| R1-2006914 | Remaining details on additional scenarios for evaluation | Ericsson |
| R1-2007103 | FL summary for additional scenarios for evaluation of NR positioning enhancements | Moderator (Ericsson) |
| R1-2007209 | FL summary#2 for additional scenarios for evaluation of NR positioning enhancements | Moderator (Ericsson) |
| R1-2007285 | FL summary#3 for additional scenarios for evaluation of NR positioning enhancements | Moderator (Ericsson) |
| R1-2007367 | FL summary#4 for additional scenarios for evaluation of NR positioning enhancements | Moderator (Ericsson) |
| 8.5.2 | Evaluation of achievable positioning accuracy and latency | |
| R1-2005252 | Performance evaluation for Rel-17 positioning | Huawei, HiSilicon |
| R1-2005380 | Evaluation of achievable positioning accuracy and latency | vivo |
| R1-2005463 | Evaluation results based on NR Rel-16 positioning | ZTE |
| R1-2005578 | Initial Views on Evaluation of Positioning Accuracy and Latency | Sony |
| R1-2005711 | Discussion of evaluation of NR positioning performance | CATT |
| R1-2005878 | NR Positioning Performance in I-IoT Scenarios | Intel Corporation |
| R1-2005991 | Evaluation of NR positioning in IIOT scenario | OPPO |
| R1-2006067 | Evaluation of achievable positioning accuracy and latency | BUPT |
| R1-2006149 | Evaluation of achievable positioning accuracy and latency | Samsung |
| R1-2006197 | Evaluation of DL-TDOA and DL-AoD techniques under IIOT scenarios | MediaTek Inc. |
| R1-2006215 | Discussion on achievable positioning latency | CMCC |
| R1-2006239 | Discussion on evaluation of latency | InterDigital, Inc. |
| R1-2006323 | Considerations for Positioning Latency Evaluation | Lenovo, Motorola Mobility |
| R1-2006375 | Discussion on evaluation of achievable positioning accuracy and latency for NR positioning | LG Electronics |
| R1-2006428 | Initial results on evaluation of achievable positioning accuracy and latency | Nokia, Nokia Shanghai Bell |
| R1-2006459 | Evaluation of positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2006623 | Positioning evaluation results for additional commercial use cases | CEWiT |
| R1-2006809 | Evaluation of achievable Positioning Accuracy & Latency | Qualcomm Incorporated |
| R1-2006915 | Evaluation of achievable positioning accuracy and latency | Ericsson |
| R1-2006970 | Discussion of evaluation of NR positioning performance | CATT |
| R1-2007105 | Feature lead summary #1 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] | Moderator (Intel) |
| R1-2007262 | Feature lead summary #2 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] | Moderator (Intel Corporation) |
| R1-2007263 | Draft LS on Latency of NR Positioning Protocols | Intel Corporation |
| R1-2007264 | LS on Latency of NR Positioning Protocols | RAN1, Intel Corporation |
| R1-2007358 | Feature lead summary #3 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] | Moderator (Intel Corporation) |
| R1-2007359 | Template for collection of NR positioning evaluation results | Moderator (Intel Corporation) |
| R1-2007413 | Template for collection of NR positioning evaluation results | Moderator (Intel Corporation) |
| 8.5.3 | Potential positioning enhancements | |
| R1-2005253 | Positioning enhancement in Rel-17 | Huawei, HiSilicon |
| R1-2005284 | Positioning Enhancements | FUTUREWEI |
| R1-2005381 | Discussion on potential positioning enhancements | vivo |
| R1-2005464 | Discussion on potential NR positioning enhancements | ZTE |
| R1-2005579 | Discussion on Positioning Enhancements | Sony |
| R1-2005712 | Discussion of NR positioning enhancements | CATT |
| R1-2005769 | Potential positioning enhancements | TCL Communication Ltd. |
| R1-2005879 | Potential Enhancements of NR Positioning Design | Intel Corporation |
| R1-2005992 | Discussions on NR Positioning Enhancements | OPPO |
| R1-2006068 | Potential positioning enhancements | BUPT |
| R1-2006150 | Potential positioning enhancements | Samsung |
| R1-2006194 | Views on positioning enhancement for Rel-17 | MediaTek Inc. |
| R1-2006216 | Discussion on potential positioning enhancements | CMCC |
| R1-2006240 | Discussion on potential positioning enhancements | InterDigital, Inc. |
| R1-2006250 | Discussion on potential positioning enhancements | Spreadtrum Communications |
| R1-2006324 | On Potential NR Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2006376 | Discussion on potential enhancements for NR positioning | LG Electronics |
| R1-2006429 | Views on potential positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2006460 | Potential positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2006522 | Initial Views on Potential Positioning Enhancements | Apple |
| R1-2006547 | Potential positioning enhancements | Beijing Xiaomi Electronics |
| R1-2006621 | Discussion on positioning enhancements for Rel 17 | CEWiT |
| R1-2006732 | Discussion on potential techniques for NR Positioning Enhancements | NTT DOCOMO, INC. |
| R1-2006810 | Potential Positioning Enhancements for NR Rel-17 Positioning | Qualcomm Incorporated |
| R1-2006859 | Discussion on Potential positioning enhancements | CAICT |
| R1-2006916 | Potential positioning enhancements | Ericsson |
| R1-2006972 | FL Summary for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2007111 | FL Summary#2 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2007172 | FL Summary#3 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2007210 | FL Summary#4 for Potential Positioning Enhancements | Moderator (CATT) |
| R1-2007343 | FL Summary#5 for Potential Positioning Enhancements | Moderator (CATT) |
| 8.5.4 | Other | |
| R1-2005382 | Discussion on power consumption model for NR positioning enhancements | vivo |
| R1-2005465 | Channel state estimation based on prior channel information | ZTE |
| R1-2005713 | Discussion of NLOS channel modelling and network time synchronization for NR positioning | CATT |
| R1-2005993 | Analysis of NR Positioning for IIOT Scenarios | OPPO |
| R1-2006151 | Uplink Transmission Based Relative Positioning | Samsung |
| R1-2006241 | Discussion on positioning during idle/inactive mode | InterDigital, Inc. |
| R1-2006398 | Analysis of positioning service latency | Huawei, HiSilicon |
| R1-2006523 | Analysis for L1 Positioning Latency | Apple |
| R1-2006917 | PRS with cyclic shifts | Ericsson |
| 8.6 | Study on Support of Reduced Capability NR Devices | |
| R1-2005233 | TR38.875 skeleton updates for Study on support of reduced capability NR devices | Ericsson |
| R1-2007476 | FL summary #1 for RedCap evaluation templates | Moderators (Ericsson, Apple, Qualcomm) |
| R1-2007477 | FL summary #2 for RedCap evaluation templates | Moderators (Ericsson, Apple, Qualcomm) |
| R1-2007478 | FL summary #3 for RedCap evaluation templates | Moderators (Ericsson, Apple, Qualcomm) |
| R1-2007481 | FL summary #4 for RedCap evaluation templates | Moderators (Ericsson, Apple, Qualcomm) |
| R1-2007482 | FL summary on initial collection of RedCap evaluation results | Moderators (Ericsson, Apple, Qualcomm) |
| 8.6.1 | Potential UE complexity reduction features | |
| R1-2005234 | Potential UE complexity reduction features for RedCap | Ericsson |
| R1-2005269 | Potential UE complexity reduction features | Huawei, HiSilicon |
| R1-2005277 | Complexity reduction features for RedCap UEs | FUTUREWEI |
| R1-2005383 | Discussion on complexity reduction for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2005474 | Potential UE complexity reduction features | ZTE |
| R1-2005525 | UE complexity reduction features | Nokia, Nokia Shanghai Bell |
| R1-2005580 | On potential complexity reduction techniques for NR devices | Sony |
| R1-2005637 | On complexity reduction features for NR RedCap UEs | MediaTek Inc. |
| R1-2005714 | Discussion on potential UE complexity reduction features | CATT |
| R1-2005770 | Potential UE complexity reduction features | TCL Communication Ltd. |
| R1-2005830 | On UE complexity reduction features for RedCap | Lenovo, Motorola Mobility |
| R1-2005880 | On complexity reduction for RedCap UEs | Intel Corporation |
| R1-2005937 | Reduced Capability UE Complexity Reduction Features | Sierra Wireless, S.A. |
| R1-2005959 | Rel-16 UE power saving features for RedCap | NEC |
| R1-2005968 | Discussion on the complexity reduction for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2006036 | Discussion on UE complexity reduction | OPPO |
| R1-2006152 | UE complexity reduction | Samsung |
| R1-2006196 | Discussion on potential UE complexity reduction features | Panasonic Corporation |
| R1-2006217 | Discussion on potential UE complexity reduction features | CMCC |
| R1-2006272 | Discussion on potential UE complexity reduction features | Spreadtrum Communications |
| R1-2006306 | Discussion on potential UE complexity reduction features | LG Electronics |
| R1-2006524 | UE Complexity Reduction Features for RedCap | Apple |
| R1-2006538 | Complexity reduction features for reduced capability NR devices | InterDigital, Inc. |
| R1-2006542 | On impacts of UE bandwidth reduction | Quectel |
| R1-2006576 | Discussion on Potential UE complexity reduction features | Sharp |
| R1-2006644 | Discussion on potential UE complexity reduction features | Asia Pacific Telecom co. Ltd |
| R1-2006682 | Complexity reduction features for RedCap UE | Sequans Communications |
| R1-2006733 | Discussion on potential UE complexity reduction features for RedCap | NTT DOCOMO, INC. |
| R1-2006811 | Complexity Reduction for RedCap Devices | Qualcomm Incorporated |
| R1-2006988 | UE Complexity Reduction Features for RedCap | Apple |
| R1-2007031 | UE complexity reduction | Samsung |
| R1-2007090 | FL summary #1 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2007177 | FL summary #2 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2007269 | FL summary #3 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2007302 | FL summary #4 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| R1-2007331 | FL summary #5 for Potential UE complexity reduction features for RedCap | Moderator (Ericsson) |
| 8.6.2 | Reduced PDCCH monitoring | |
| R1-2005235 | Reduced PDCCH monitoring for RedCap | Ericsson |
| R1-2005270 | Power saving for reduced capability devices | Huawei, HiSilicon |
| R1-2005384 | Reduced PDCCH monitoring for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2005475 | Consideration on reduced PDCCH monitoring | ZTE |
| R1-2005526 | Reduced PDCCH monitoring | Nokia, Nokia Shanghai Bell |
| R1-2005591 | Power savings for RedCap UEs | FUTUREWEI |
| R1-2005638 | Discussion on reduced PDCCH monitoring for NR RedCap UEs | MediaTek Inc. |
| R1-2005715 | Discussion on PDCCH monitoring reduction | CATT |
| R1-2005771 | Reduced PDCCH monitoring | TCL Communication Ltd. |
| R1-2005778 | Reduced PDCCH monitoring for REDCAP NR devices | NEC |
| R1-2005779 | Reduced PDCCH Monitoring for RedCap UEs | Fraunhofer HHI, Fraunhofer IIS |
| R1-2005881 | On reduced PDCCH monitoring for RedCap UEs | Intel Corporation |
| R1-2005933 | PDCCH monitoring at reduced capability UE | Lenovo, Motorola Mobility |
| R1-2005969 | Discussion on reduced PDCCH monitoring for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2006037 | Discussion on reduced monitoring for PDCCH | OPPO |
| R1-2006153 | Reduced PDCCH monitoring | Samsung |
| R1-2006218 | Discussion on reduced PDCCH monitoring | CMCC |
| R1-2006286 | Discussion on reduced PDCCH monitoring | Spreadtrum Communications |
| R1-2006307 | Discussion on PDCCH monitoring for reduced capability NR devices | LG Electronics |
| R1-2006525 | Reduced PDCCH Monitoring for RedCap Devices | Apple |
| R1-2006539 | Reduced PDCCH monitoring for reduced capability NR devices | InterDigital, Inc. |
| R1-2006606 | PDCCH Monitoring for Reduced Capability Devices | GDCNI |
| R1-2006607 | PDCCH Monitoring for Reduced Capability Devices | GDCNI |
| R1-2006683 | Reduced PDCCH monitoring for RedCap UE | Sequans Communications |
| R1-2006734 | Discussion on reduced PDCCH monitoring for RedCap | NTT DOCOMO, INC. |
| R1-2006812 | PDCCH Monitoring Reduction and Power Saving for RedCap Devices | Qualcomm Incorporated |
| R1-2006839 | PDCCH Monitoring for Reduced Capability Devices | GDCNI |
| R1-2006850 | PDCCH Monitoring for Reduced Capability Devices | GDCNI |
| R1-2006890 | Discussion on PDCCH monitoring for RedCap UE | WILUS Inc. |
| R1-2006947 | On power saving and battery lifetime enhancement for NR Redcap devices | Sony |
| R1-2007030 | Feature lead summary #1 on reduced PDCCH monitoring | Moderator (Apple Inc.) |
| R1-2007184 | Feature lead summary #2 on reduced PDCCH monitoring | Moderator (Apple Inc.) |
| R1-2007284 | Feature lead summary #3 on reduced PDCCH monitoring | Moderator (Apple Inc.) |
| R1-2007344 | Feature lead summary #4 on reduced PDCCH monitoring | Moderator (Apple Inc.) |
| R1-2007426 | Feature lead summary #5 on reduced PDCCH monitoring | Moderator (Apple Inc.) |
| 8.6.3 | Coverage recovery and capacity impact | |
| R1-2005236 | Coverage recovery and capacity impact for RedCap | Ericsson |
| R1-2005271 | Functionality for coverage recovery | Huawei, HiSilicon |
| R1-2005278 | Coverage recovery for RedCap | FUTUREWEI |
| R1-2005385 | Discussion on functionality for coverage recovery | vivo, Guangdong Genius, GDCNI |
| R1-2005476 | Discussion on coverage recovery for RedCap UE | ZTE |
| R1-2005527 | Functionality for coverage recovery | Nokia, Nokia Shanghai Bell |
| R1-2005581 | Coverage recovery and capacity impact of Redcap devices | Sony |
| R1-2005596 | Coverage recovery and capacity impact | Panasonic Corporation |
| R1-2005639 | Discussion on coverage recovery for NR RedCap UEs | MediaTek Inc. |
| R1-2005716 | Discussion on coverage recovery | CATT |
| R1-2005757 | Discussion on coverage recovery and capacity impact | NEC |
| R1-2005772 | Coverage recovery and capacity impact | TCL Communication Ltd. |
| R1-2005831 | On coverage recovery for RedCap | Lenovo, Motorola Mobility |
| R1-2005882 | On coverage recovery for RedCap UEs | Intel Corporation |
| R1-2005970 | Discussion on coverage recovery for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2006038 | Discussion on functionality for coverage recovery | OPPO |
| R1-2006154 | Coverage recovery for low capability device | Samsung |
| R1-2006219 | Discusison on coverage recovery for reduced capability NR devices | CMCC |
| R1-2006290 | Discussion on coverage recovery and capacity impact | Spreadtrum Communications |
| R1-2006308 | Discussion on the coverage recovery of reduced capability NR devices | LG Electronics |
| R1-2006363 | Considerations for coverage recovery | ITL |
| R1-2006526 | Functionality for Coverage Recovery for RedCap | Apple |
| R1-2006541 | PDCCH coverage enhancement for reduced capability NR devices | InterDigital, Inc. |
| R1-2006577 | Coverage recovery for reduced capability UEs | Sharp |
| R1-2006630 | On coverage recovery for reduced capability UEs | Convida Wireless |
| R1-2006684 | Coverage recovery for RedCap UE | Sequans Communications |
| R1-2006735 | Discussion on coverage recovery for RedCap | NTT DOCOMO, INC. |
| R1-2006813 | Coverage Recovery for RedCap Devices | Qualcomm Incorporated |
| R1-2006891 | Discussion on Coverage Recovery for RedCap UE | WILUS Inc. |
| R1-2007081 | Coverage Recovery for RedCap Devices | Qualcomm Incorporated |
| R1-2007091 | FL summary on coverage recovery and capacity impact for NR RedCap | Moderator (Qualcomm) |
| R1-2007153 | FL summary#2 on coverage recovery and capacity impact for NR RedCap | Moderator (Qualcomm) |
| R1-2007312 | FL summary#3 on coverage recovery and capacity impact for NR RedCap | Moderator (Qualcomm) |
| 8.6.4 | Framework and Principles for Reduced Capability | |
| R1-2005237 | Framework and principles for RedCap | Ericsson |
| R1-2005279 | Framework for RedCap UEs | FUTUREWEI |
| R1-2005386 | Framework and Principles for Reduced Capability | vivo, Guangdong Genius |
| R1-2005477 | Views on Framework and Principles for Reduced Capability | ZTE |
| R1-2005528 | Framework and Principles for Reduced Capability | Nokia, Nokia Shanghai Bell |
| R1-2005640 | On the framework for RedCap UEs | MediaTek Inc. |
| R1-2005717 | Framework and principles for reduced capability NR devices | CATT |
| R1-2005832 | On Framework and Principles for RedCap | Lenovo, Motorola Mobility |
| R1-2005883 | Introducing NR RedCap UEs: Overall framework | Intel Corporation |
| R1-2005971 | Discussion on framework and principles for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2006039 | Consideration on reduced UE capability | OPPO |
| R1-2006155 | Framework and Principles for Reduced Capability | Samsung |
| R1-2006220 | Discussion on principles and framework of reduced capability NR | CMCC |
| R1-2006287 | Discussion on Framework and Principles for Reduced Capability | Spreadtrum Communications |
| R1-2006309 | Consideration on the framework to support reduced capability NR devices | LG Electronics |
| R1-2006388 | Discussion on Framework and Principles for Reduced Capability | Panasonic |
| R1-2006406 | Framework and principles for reduced capability devices | Huawei, HiSilicon |
| R1-2006686 | Framework and principles for RedCap UE | Sequans Communications |
| R1-2006814 | Standardization Framework and Design Principles for RedCap Devices | Qualcomm Incorporated |
| R1-2007330 | Summary on [102-e-NR-RedCap-04] | Moderator (NTT DOCOMO) |
| 8.6.5 | Other | |
| R1-2005238 | Identification and access restriction for RedCap | Ericsson |
| R1-2005387 | RRM relaxation for Reduced Capability NR devices | vivo, Guangdong Genius |
| R1-2005478 | Discussion on access control for Reduced Capability NR devices | ZTE |
| R1-2005718 | Identification and access restriction for reduced capability NR devices | CATT |
| R1-2005934 | Aspects related to bandwidth reduction | Lenovo, Motorola Mobility |
| R1-2005960 | CBW for RedCap | NEC |
| R1-2005972 | Discussion on the access control and configuration for reduced capability device | Beijing Xiaomi Software Tech |
| R1-2006040 | Other considerations for reduced UE capability | OPPO |
| R1-2006156 | Access barring and UE capability | Samsung |
| R1-2006270 | Consideration on power saving for reduced capability NR devices | Spreadtrum Communications |
| R1-2006310 | Support and control of initial cell access for reduced capability NR devices | LG Electronics |
| R1-2006411 | Other aspects for reduced capability devices | Huawei, HiSilicon |
| R1-2006687 | Access restriction for reduced capability NR devices | InterDigital, Inc. |
| R1-2007283 | Summary on [102-e-NR-RedCap-05] | Moderator (Intel) |
| 8.7 | UE Power Saving Enhancements | |
| R1-2005614 | Work plan for UE power saving enhancements | MediaTek Inc. |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2005262 | Paging enhancement(s) for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2005388 | Discussion on paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2005520 | Discussion on power saving enhancements for paging | ZTE |
| R1-2005582 | Considerations on paging enhancements | Sony |
| R1-2005615 | Evaluation methodology and paging enhancement for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2005719 | Paging enhancement for UE power saving | CATT |
| R1-2005738 | Paging enhancement for power saving | Beijing Xiaomi Software Tech |
| R1-2005773 | Potential paging enhancements | TCL Communication Ltd. |
| R1-2005884 | On paging enhancements for UE power saving | Intel Corporation |
| R1-2005935 | Power efficient paging | Lenovo, Motorola Mobility |
| R1-2006041 | Paging enhancements for power saving | OPPO |
| R1-2006157 | On potential paging enhancements | Samsung |
| R1-2006221 | Discussion on paging enhancement | CMCC |
| R1-2006291 | Discussion on potential paging enhancements | Spreadtrum Communications |
| R1-2006311 | Discussion on potential paging enhancements | LG Electronics |
| R1-2006385 | Potential paging enhancements for idle/inactive-mode UE power saving | Panasonic |
| R1-2006527 | Potential paging enhancements for idle/inactive-mode UE power saving | Apple |
| R1-2006544 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2006665 | Discussion on potential paging enhancements for UE power savings | Ericsson |
| R1-2006736 | Discussion on paging enhancements | NTT DOCOMO, INC. |
| R1-2006815 | Paging enhancements and evaluation methodology | Qualcomm Incorporated |
| R1-2006896 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2007063 | Summary for potential paging enhancements | MediaTek |
| R1-2007355 | Draft LS on evaluation methodology for UE power saving enhancements | MediaTek |
| R1-2007356 | LS on evaluation methodology for UE power saving enhancements | RAN1, MediaTek |
| R1-2007425 | LS on evaluation methodology for UE power saving enhancements | RAN1, MediaTek |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2005263 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2005389 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2005521 | Reference signal for RRC idle and inactive UEs | ZTE |
| R1-2005583 | On the usage of TRS/CSI-RS for the UE in Idle Mode | Sony |
| R1-2005616 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2005720 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2005739 | Discussion on TRS CSI-RS occasions for idle/inactive UEs | Beijing Xiaomi Software Tech |
| R1-2005885 | Discussion on TRS/CSI-RS reception during idle/inactive mode | Intel Corporation |
| R1-2006042 | RS occasion for idle/inactive UEs | OPPO |
| R1-2006158 | On TRS/CSI-RS occasion(s) for idle/inactive Ues | Samsung |
| R1-2006222 | Discussion on potential TRS CSI-RS occasion(s) for idle/inactive UEs | CMCC |
| R1-2006269 | Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2006312 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2006386 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive Ues | Panasonic |
| R1-2006528 | Indication of TRS/CSI-RS for idle/inactive-mode UE power saving | Apple |
| R1-2006666 | Provisioning of potential TRS/CSI-RS occasion(s) for Idle/Inactive UEs | Ericsson |
| R1-2006737 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2006816 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2006897 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2007475 | Summary for TRS/CSI-RS occasion(s) for idle/inactive Ues | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2005390 | Discussion on paging grouping | vivo |
| R1-2005522 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE |
| R1-2006412 | Initial analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2006667 | High-level UE energy consumption profiling | Ericsson |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2005264 | Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2005391 | Discussion on DCI-based power saving adaptation | vivo |
| R1-2005523 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE |
| R1-2005617 | Evaluation methodology and enhancement for connected mode UE power saving | MediaTek Inc. |
| R1-2005721 | PDCCH monitoring adaptation | CATT |
| R1-2005886 | On PDCCH monitoring reduction techniques during active time | Intel Corporation |
| R1-2005936 | Potential enhancement to DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2006043 | DCI-based adaptation for PDCCH | OPPO |
| R1-2006159 | On enhancements of power saving techniques during DRX active time | Samsung |
| R1-2006223 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2006271 | Discussion on power saving techniques for connected-mode UE | Spreadtrum Communications |
| R1-2006313 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2006387 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2006529 | PDCCH based power saving enhancements for connected-mode Ues | Apple |
| R1-2006548 | PDCCH-based power saving signal design considerations | InterDigital, Inc. |
| R1-2006668 | Discussion on potential enhancements for power savings during active time | Ericsson |
| R1-2006738 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2006755 | Power saving adaptation during Active Time | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2006817 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2006898 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2006946 | Power saving enhancements for connected mode UEs | Sony |
| R1-2007032 | Evaluation methodology and enhancement for connected mode UE power saving | MediaTek Inc. |
| R1-2007065 | FL summary of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Moderator (vivo) |
| R1-2007117 | FL summary#2 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Moderator (vivo) |
| R1-2007225 | FL summary#3 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Moderator (vivo) |
| R1-2007400 | FL summary#4 of potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Moderator (vivo) |
| R1-2007419 | LS on evaluation methodology for connected mode UE power saving enhancement | RAN1, vivo, MediaTek |
| 8.7.3 | Other | |
| R1-2005392 | Discussion on RLM/BFD relaxation | vivo |
| R1-2005524 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE |
| R1-2006044 | Discussion on RLM Relaxation | OPPO |
| R1-2006404 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2006669 | Evaluation of UE power saving schemes | Ericsson |
| 8.8 | Study on NR coverage enhancement | |
| R1-2005729 | Updated work plan for Study on NR coverage enhancements | China Telecom |
| R1-2005730 | TR 38.830 v0.0.2 Study on NR coverage enhancements | China Telecom |
| 8.8.1 | Baseline coverage performance using LLS | |
| R1-2006242 | Discussion on simulation assumptions for VoIP | InterDigital, Inc. |
| R1-2007479 | [102-e-Post-NR-CovEnh-01] Summary on email discussion/approval of remaining simulation assumptions | Moderator (SoftBank, Nokia) |
| R1-2007484 | [102-e-Post-NR-CovEnh-02] Summary on email discussion/approval of initial collection of simulation results for baseline | Moderator (SoftBank, Nokia) |
| 8.8.1.1 | FR1 | |
| R1-2005256 | Evaluation on the baseline performance for FR1 | Huawei, HiSilicon |
| R1-2005297 | Baseline coverage evaluation of UL and DL channels – FR1 | Nokia, Nokia Shanghai Bell |
| R1-2005393 | Evaluation on NR coverage performance for FR1 | vivo |
| R1-2005425 | Discussion on baseline coverage performance for FR1 | ZTE |
| R1-2005644 | Discussion on scenarios for FR1 baseline performance evaluation | MediaTek Inc. |
| R1-2005722 | Baseline coverage performance for FR1 | CATT |
| R1-2005731 | Baseline performance for NR coverage enhancements for FR1 | China Telecom |
| R1-2005887 | Discussion on baseline coverage performance for FR1 | Intel Corporation |
| R1-2005939 | FR1 PUSCH Coverage Performance | Sierra Wireless, S.A. |
| R1-2006045 | Evaluation on NR coverage performance for FR1 | OPPO |
| R1-2006160 | Baseline coverage performance using LLS for FR1 | Samsung |
| R1-2006224 | Discussion on the baseline performance in FR1 | CMCC |
| R1-2006243 | FR1 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2006346 | Baseline coverage performance analysis in FR1 | Panasonic Corporation |
| R1-2006455 | Baseline coverage performance for uplink | Indian Institute of Tech (H) |
| R1-2006530 | Evaluation on FR1 coverage performance | Apple |
| R1-2006534 | Baseline coverage performance for FR1 | Xiaomi Technology |
| R1-2006578 | Evaluation results of coverage for FR1 Urban scenario | Sharp |
| R1-2006611 | Link and System Evaluation of Coverage for FR1 | Ericsson |
| R1-2006645 | Views on target performance metric and values for FR1 coverage enhancements | SoftBank Corp. |
| R1-2006652 | Baseline coverage performance for FR1 | Charter Communications |
| R1-2006739 | Baseline coverage performance for FR1 | NTT DOCOMO, INC. |
| R1-2006818 | Baseline FR1 coverage performance | Qualcomm Incorporated |
| R1-2006990 | Baseline coverage performance analysis in FR1 | Panasonic Corporation |
| R1-2007010 | Baseline coverage performance for FR1 | CATT |
| R1-2007048 | Link and System Evaluation of Coverage for FR1 | Ericsson |
| R1-2007106 | Baseline coverage performance for FR1 | Charter Communications |
| R1-2007449 | [102-e-NR-CovEnh-01] Summary on A.I. 8.8.1.1 baseline coverage performance using LLS for FR1 | Moderator (SoftBank) |
| R1-2007480 | [102-e-Post-NR-CovEnh-02] Summary on email discussion/approval of Phase 1 - link budget template | Moderator (SoftBank) |
| 8.8.1.2 | FR2 | |
| R1-2005257 | Evaluation on the baseline performance for FR2 | Huawei, HiSilicon |
| R1-2005298 | Baseline coverage evaluation of UL and DL channels – FR2 | Nokia, Nokia Shanghai Bell |
| R1-2005394 | Evaluation on NR coverage performance for FR2 | vivo |
| R1-2005426 | Discussion on baseline coverage performance for FR2 | ZTE |
| R1-2005490 | Evaluation on NR coverage performance for FR2 | China Unicom |
| R1-2005723 | Baseline coverage performance for FR2 | CATT |
| R1-2005888 | Discussion on baseline coverage performance for FR2 | Intel Corporation |
| R1-2006046 | Evaluation on NR coverage performance for FR2 | OPPO |
| R1-2006161 | Baseline coverage performance using LLS for FR2 | Samsung |
| R1-2006225 | Discussion on the baseline performance in FR2 | CMCC |
| R1-2006244 | FR2 baseline coverage performance using LLS | InterDigital, Inc. |
| R1-2006533 | Baseline coverage performance for FR2 | Beijing Xiaomi Mobile Software |
| R1-2006612 | Link and System Evaluation of Coverage for FR2 | Ericsson |
| R1-2006740 | Baseline coverage performance for FR2 | NTT DOCOMO, INC. |
| R1-2006819 | Baseline FR2 coverage performance | Qualcomm Incorporated |
| R1-2007049 | Link and System Evaluation of Coverage for FR2 | Ericsson |
| R1-2007414 | FL Summary of Baseline Coverage Evaluation of DL and UL for FR2 | Moderator (Nokia) |
| 8.8.2.1 | PUSCH coverage enhancement | |
| R1-2005258 | Discussion on the potential coverage enhancement solutions for PUSCH | Huawei, HiSilicon |
| R1-2005299 | Discussion on potential approaches and solutions for NR PUSCH coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2005395 | Discussion on Solutions for PUSCH coverage enhancement | vivo |
| R1-2005427 | Discussion on potential techniques for PUSCH coverage enhancements | ZTE |
| R1-2005584 | On PUSCH coverage enhancement techniques | Sony |
| R1-2005724 | Discussion on potential techniques for PUSCH coverage enhancement | CATT |
| R1-2005732 | Potential solutions for PUSCH coverage enhancements | China Telecom |
| R1-2005758 | Discussion on PUSCH coverage enhancement | NEC |
| R1-2005889 | Discussion on potential techniques for PUSCH coverage enhancement | Intel Corporation |
| R1-2005938 | Potential techniques for PUSCH coverage enhancements | Sierra Wireless, S.A. |
| R1-2006047 | Consideration on PUSCH coverage enhancement | OPPO |
| R1-2006162 | PUSCH coverage enhancement | Samsung |
| R1-2006226 | Discussion on the PUSCH coverage enhancement | CMCC |
| R1-2006245 | PUSCH coverage enhancement | InterDigital, Inc. |
| R1-2006253 | Potential solutions for PUSCH coverage enhancement | Spreadtrum Communications |
| R1-2006348 | Discussion on PUSCH coverage enhancements | Panasonic Corporation |
| R1-2006456 | PUSCH coverage enhancements | Indian Institute of Tech (H) |
| R1-2006531 | On potential techniques for PUSCH coverage enhancement | Apple |
| R1-2006579 | PUSCH coverage enhancement | Sharp |
| R1-2006613 | PUSCH coverage enhancement | Ericsson |
| R1-2006741 | Potential techniques for PUSCH coverage enhancements | NTT DOCOMO, INC. |
| R1-2006820 | Potential coverage enhancement techniques for PUSCH | Qualcomm Incorporated |
| R1-2006877 | Discussion on potential techniques for coverage enhancement | LG Electronics |
| R1-2006892 | Discussion on potential techniques for PUSCH coverage enhancement | WILUS Inc. |
| R1-2006977 | Potential coverage enhancement techniques for PUSCH | Qualcomm Incorporated |
| R1-2007404 | [102-e-NR-CovEnh-03] Email discussion/approval on PUSCH coverage enhancement | Moderator (China Telecom) |
| 8.8.2.2 | PUCCH coverage enhancement | |
| R1-2005273 | Discussion on the potential coverage enhancement solutions for PUCCH | Huawei, HiSilicon |
| R1-2005300 | Discussion on potential approaches and solutions for NR PUCCH coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2005396 | Discussion on Solutions for PUCCH coverage enhancement | vivo |
| R1-2005428 | Discussion on potential techniques for PUCCH coverage enhancements | ZTE |
| R1-2005585 | On PUCCH coverage enhancement techniques | Sony |
| R1-2005725 | Discussion on potential techniques for PUCCH coverage enhancement | CATT |
| R1-2005759 | Discussion on PUCCH coverage enhancement | NEC |
| R1-2005890 | Discussion on potential techniques for PUCCH coverage enhancement | Intel Corporation |
| R1-2006048 | Consideration on PUCCH coverage enhancement | OPPO |
| R1-2006163 | PUCCH coverage enhancement | Samsung |
| R1-2006227 | Discussion on the PUCCH coverage enhancement | CMCC |
| R1-2006246 | PUCCH coverage enhancement | InterDigital, Inc. |
| R1-2006349 | Discussion on PUCCH coverage enhancements | Panasonic Corporation |
| R1-2006457 | PUCCH coverage enhancements | Indian Institute of Tech (H) |
| R1-2006580 | PUCCH coverage enhancement | Sharp |
| R1-2006614 | PUCCH coverage enhancement | Ericsson |
| R1-2006742 | Potential techniques for PUCCH coverage enhancements | NTT DOCOMO, INC. |
| R1-2006821 | Potential coverage enhancement techniques for PUCCH | Qualcomm Incorporated |
| R1-2006880 | Limitations of NR short block-length codes for PUCCH coverage enhancement | EURECOM |
| R1-2006893 | Discussion on potential techniques for PUCCH coverage enhancement | WILUS Inc. |
| R1-2007175 | Discussion on potential techniques for PUCCH coverage enhancement | Intel Corporation |
| R1-2007473 | FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.2.3 | Coverage enhancement for channels other than PUSCH and PUCCH | |
| R1-2005274 | Discussion on the potential coverage enhancement solutions for other channels | Huawei, HiSilicon |
| R1-2005301 | Discussion on potential approaches and solutions for NR coverage enhancement: other channels than PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2005397 | Discussion on coverage enhancement for channels other than PUCCH and PUSCH | vivo |
| R1-2005429 | Discussion on potential techniques for channels other than PUSCH and PUCCH | ZTE |
| R1-2005586 | Coverage enhancement for channels other than PUSCH and PUCCH | Sony |
| R1-2005726 | Disucssion on coverage enhancement for channels other than PUSCH and PUCCH | CATT |
| R1-2005891 | Discussion on NR coverage enhancement for other physical channels | Intel Corporation |
| R1-2006049 | Enhancement on NR channels for coverage | OPPO |
| R1-2006164 | Coverage enhancement for channels other than PUSCH and PUCCH | Samsung |
| R1-2006292 | Coverage enhancement for initial access | InterDigital, Inc. |
| R1-2006532 | On potential techniques for PDCCH and PDSCH coverage enhancement | Apple |
| R1-2006615 | Coverage enhancement for channels other than PUSCH and PUCCH | Ericsson |
| R1-2006743 | Potential techniques for coverage enhancement for channels other than PUSCH and PUCCH | NTT DOCOMO, INC. |
| R1-2006822 | Potential coverage enhancement techniques for other channels | Qualcomm Incorporated |
| R1-2007392 | Feature lead summary on coverage enhancement for channels other than PUSCH and PUCCH | Moderator (ZTE) |
| 8.8.3 | Other | |
| R1-2005259 | Discussions on simulation assumptions for VoIP | Huawei, HiSilicon |
| R1-2005303 | Evaluation assumptions for NR coverage enhancement evaluation | Nokia, Nokia Shanghai Bell |
| R1-2005398 | Considerations on Evaluation Assumptions for Coverage Enhancements | vivo |
| R1-2005430 | Discussion on evaluation methodology for NR coverage | ZTE |
| R1-2005727 | Discussion on the methodology for baseline coverage performance using LLS | CATT |
| R1-2005733 | Remaining issues on evaluation methodology for NR coverage enhancements | China Telecom |
| R1-2005892 | Discussion on simulation assumptions for NR coverage enhancement | Intel Corporation |
| R1-2006050 | Functionality of Coverage Enhancement and other SI/WI | OPPO |
| R1-2006293 | Reducing PDCCH load of coverage-limited UEs | InterDigital, Inc. |
| R1-2006616 | Evaluation methodology for coverage enhancements | Ericsson |
| R1-2006823 | Other coverage enhancement aspects | Qualcomm Incorporated |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2006447 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R1-2007387 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (Samsung) |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2005304 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2005479 | Discussion on UL and DL 16QAM for NB-IoT | ZTE |
| R1-2005529 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2005557 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2005648 | Considerations on support of 16QAM for NB-IOT | MediaTek Inc. |
| R1-2005837 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2005941 | Design consideration to support 16-QAM for NB-IOT | Sierra Wireless, S.A. |
| R1-2005974 | Initial discussion on support of 16 QAM for NB-IoT | Beijing Xiaomi Software Tech |
| R1-2006192 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2007239 | Feature lead summary on 102-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2005305 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2005480 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | ZTE |
| R1-2005530 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2005558 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2005940 | Design considerations to support 14-HARQ for LTE-M | Sierra Wireless, S.A. |
| R1-2005973 | Initial discussion on support of additional PDSCH scheduling delay for introduction of 14 HARQ processes in DL for eMTC | Beijing Xiaomi Software Tech |
| R1-2006193 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2007265 | Feature Lead Summary: [102-e-LTE-Rel17_NB_IoT_eMTC-02] | Moderator (Ericsson) |
| 8.9.3 | Other | |
| R1-2005481 | DL TBS increase for eMTC | ZTE |
| R1-2006448 | Channel quality reporting in NB-IoT to support 16QAM | Huawei, HiSilicon |
| R1-2006463 | On the support of a maximum DL TBS of 1736 bits in LTE-MTC | Ericsson |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2006824 | Workplan for Rel-17 IAB | Qualcomm Incorporated |
| R1-2007388 | Session notes for 8.10 (Enhancements to Integrated Access and Backhaul) | Ad-hoc Chair (Samsung) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2005260 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2005399 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2005467 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2005535 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2005893 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2005927 | Enhancements to resource multiplexing for IAB | Lenovo, Motorola Mobility |
| R1-2005951 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2006165 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2006228 | Discussion on resource multiplexing in the simultaneous operation | CMCC |
| R1-2006329 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2006361 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2006382 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2006744 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2006825 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2006903 | IAB enhancements to resource multiplexing | Ericsson |
| R1-2007241 | Summary #1 of [102-e-NR-eIAB-01] | Moderator (AT&T) |
| R1-2007322 | Summary #2 of [102-e-NR-eIAB-01] | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2005261 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2005400 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2005468 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2005536 | Other enhancements for simultaneous operation of IAB Parent and Child | Nokia, Nokia Shanghai Bell |
| R1-2005544 | Timing alignment for simultaneous operation of IAB-node’s child and parent links | Fujitsu |
| R1-2005894 | Discussion on IAB Backhaul DL Power Control | Intel Corporation |
| R1-2005928 | Enhancements for simultaneous operation in IAB systems | Lenovo, Motorola Mobility |
| R1-2005952 | Enhancements for IAB interference management | AT&T |
| R1-2006166 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2006229 | Discussion on the enhancement for simultaneous operation | CMCC |
| R1-2006347 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2006383 | Discussion on Other Enhancements for Simultaneous Operation | LG Electronics |
| R1-2006581 | Power Control: It’s an Enhancement, and Here’s Our Views | Sharp |
| R1-2006745 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2006826 | On enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2006904 | Other enhancements for simultaneous child and parent link operation in IAB | Ericsson |
| R1-2007287 | Summary of [102-e-NR-eIAB-02] | Moderator (Qualcomm) |
| R1-2007310 | Summary#2 of [102-e-NR-eIAB-02] | Moderator (Qualcomm) |
| R1-2007352 | Summary#3 of [102-e-NR-eIAB-02] | Moderator (Qualcomm) |
| 8.10.3 | Other | |
| R1-2005401 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2005953 | Measurement results for IAB multi-panel transmission and reception | AT&T |
| R1-2006384 | Discussion on RACH procedure for IAB enhancement | LG Electronics |
| R1-2006403 | Considerations on enhancement of guard symbols for IAB | Huawei, HiSilicon |
| R1-2006622 | SDM scheme and antenna configuration for IAB node | ZTE, Sanechips |
| R1-2006905 | Enhancements to IAB for NR – overview of Rel-17 WI | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2005746 | Work plan for WI on NR sidelink enhancement | LG Electronics |
| R1-2006167 | On Sidelink Enhacement Work Item | Samsung |
| 8.11.1 | Sidelink evaluation methodology update for power saving | |
| R1-2005254 | Sidelink evaluation methodology update for power saving | Huawei, HiSilicon |
| R1-2005309 | Analysis on sidelink evaluation methodology | ZTE, Sanechips |
| R1-2005402 | Discussion on sidelink evaluation methodology | vivo |
| R1-2005499 | Discussion of sidelink evaluation methodology update for power saving | Nokia, Nokia Shanghai Bell |
| R1-2005595 | Sidelink evaluation updates for V2X | FUTUREWEI |
| R1-2005610 | Discussion on sidelink evaluation methodology for power saving | ITRI |
| R1-2005641 | Evaluation methodology for sidelink power saving | MediaTek Inc. |
| R1-2005690 | Discussion on evaluation methodology for sidelink enhancement | CATT |
| R1-2005747 | Discussion on sidelink evaluation methodology update for power saving | LG Electronics |
| R1-2005838 | Discussion on sidelink evaluation methodology update for power saving | Lenovo, Motorola Mobility |
| R1-2005895 | Sidelink evaluation methodology update for UE power saving | Intel Corporation |
| R1-2006012 | Discussion on evaluation methodology for SL power saving | OPPO |
| R1-2006168 | On Sidelink Evaluation Methodology Updates for Power Saving | Samsung |
| R1-2006182 | V2X Channel Model Updates for Pedestrians | InterDigital, Inc. |
| R1-2006266 | Sidelink evaluation methodology for power saving | Spreadtrum Communications |
| R1-2006443 | Evaluation assumptions and methodology for power saving | Ericsson |
| R1-2006506 | On Sidelink Power Consumption Model | Apple |
| R1-2006624 | Discussion on sidelink evaluation methodology update for power Saving | Xiaomi |
| R1-2006746 | Discussion on sidelink evaluation methodology for power saving | NTT DOCOMO, INC. |
| R1-2006827 | Evaluation Methodology for Power Saving in Sidelink | Qualcomm Incorporated |
| R1-2007003 | V2X Channel Model Updates for Pedestrians | InterDigital, Inc. |
| R1-2007411 | Summary for AI 8.11.1 SL evaluation methodology update for power saving | Moderator (LG Electronics) |
| 8.11.2 | Resource allocation enhancement | |
| R1-2006169 | On Resource Allocation Enhacements | Samsung |
| 8.11.2.1 | Resource allocation for power saving | |
| R1-2005275 | Sidelink resource allocation for Power saving | Lenovo, Motorola Mobility |
| R1-2005295 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2005310 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2005403 | Resource allocation for sidelink power saving | vivo |
| R1-2005500 | Discussion of sidelink resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2005545 | Considerations on partial sensing in NR-V2X | Fujitsu |
| R1-2005587 | Resource allocation for power saving | Sony |
| R1-2005642 | Power saving techniques for sidelink | MediaTek Inc. |
| R1-2005691 | Discussion on resource allocation for power saving | CATT |
| R1-2005748 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2005762 | Views on resource allocation for power saving | NEC |
| R1-2005839 | Sidelink resource allocation for Power saving | Lenovo, Motorola Mobility |
| R1-2005896 | Sidelink enhancements for UE power saving | Intel Corporation |
| R1-2006009 | Power saving mechanisms for NR SL | OPPO |
| R1-2006170 | On Resource Allocation for Power Saving | Samsung |
| R1-2006183 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2006230 | Discussion on resource allocation for power saving | CMCC |
| R1-2006267 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2006401 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2006444 | Resource allocation mechanisms for power saving | Ericsson |
| R1-2006507 | On Resource Allocation for Power Saving | Apple |
| R1-2006625 | Discussion on resource allocation for power saving | Xiaomi |
| R1-2006747 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2006828 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2006860 | Considerations on partial sensing in NR V2X | CAICT |
| R1-2006873 | Resource allocation for power saving with partial sensing in NR sidelink enhancement | ITL |
| R1-2006878 | Sidelink Resource Allocation to Reduce Power Consumption | ROBERT BOSCH GmbH |
| 8.11.2.2 | Feasibility and benefits for mode 2 enhancements | |
| R1-2005255 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2005276 | Sidelink resource allocation for Reliability enhancement | Lenovo, Motorola Mobility |
| R1-2005296 | Views on resource allocation enhancements for sidelink communication | FUTUREWEI |
| R1-2005404 | Discussion on mode-2 enhancements | vivo |
| R1-2005501 | Discussion of sidelink resource allocation mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2005537 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2005546 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2005588 | High-level concepts for mode 2 enhancements | Sony |
| R1-2005612 | Considerations on Mode 2 Latency Enhancement | ITRI |
| R1-2005645 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2005692 | Discussion on feasibility and benefits for mode 2 enhancements | CATT |
| R1-2005749 | Discussion on feasibility and benefits for mode 2 enhancements | LG Electronics |
| R1-2005763 | Views on feasibility and benefits for mode 2 enhancements | NEC |
| R1-2005774 | Feasibility and benefits for mode 2 enhancements | TCL Communication Ltd. |
| R1-2005840 | Sidelink resource allocation for Reliability enhancement | Lenovo, Motorola Mobility |
| R1-2005897 | On feasibility and benefits of sidelink enhancements targeting Mode 2 reliability and latency | Intel Corporation |
| R1-2005903 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2005961 | Inter-UE coordination in mode-2 | ZTE, Sanechips |
| R1-2006010 | Discussion on feasibility and benefits of mode 2 enhancements | OPPO |
| R1-2006171 | On Feasibility and Benefits for Mode2 Enhancements | Samsung |
| R1-2006184 | NR SL Mode 2 enhancement for reliability improvement | InterDigital, Inc. |
| R1-2006231 | Discussion on reliability and latency enhancements for mode-2 resource allocation | CMCC |
| R1-2006268 | Discussion on feasibility and benefit of mode 2 enhancements | Spreadtrum Communications |
| R1-2006445 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2006508 | Mode 2 Resoruce Allocation with Inter-UE Coordination | Apple |
| R1-2006537 | Mode 2 enhancements in sidelink | Panasonic Corporation |
| R1-2006587 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2006626 | Discussion on Mode 2 enhancement for enhanced reliability and reduced latency | Xiaomi |
| R1-2006748 | Discussion on sidelink resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2006829 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2006876 | Sidelink Resource Allocation Enhancements | ROBERT BOSCH GmbH |
| R1-2006922 | On Resource Allocation Mode 2 Enhancement for NR Sidelink | Convida Wireless |
| R1-2007412 | Summary for AI 8.11.2.2 Feasibility and benefits for mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.3 | Other | |
| R1-2005405 | Discussion on sidelink DRX | vivo |
| R1-2005611 | Discussion on enhancement for NR V2X | ITRI |
| R1-2005613 | Discussion on collaboration among sidelink UEs for mode-2 resource allocation | ITRI |
| R1-2005841 | Discussion on potential sidelink DRX impacts in RAN1 | Lenovo, Motorola Mobility |
| R1-2005962 | Potential impact of DRX enhancement to RAN1 discussion | ZTE, Sanechips |
| R1-2006011 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2006172 | On Sidelink Issues and RAN1 Impacts | Samsung |
| R1-2006402 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2006446 | Other resource allocation topics | Ericsson |
| R1-2006618 | On multi-carrier operation for SL | InterDigital, Inc. |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2006232 | NR MBS work plan | CMCC, Huawei, HiSilicon |
| R1-2007001 | FL summary on NR Multicast and Broadcast Services | Moderator (CMCC) |
| R1-2007089 | Summary#1 on NR Multicast and Broadcast Services | Moderator (CMCC) |
| R1-2007235 | Summary#2 on NR Multicast and Broadcast Services | Moderator (CMCC) |
| R1-2007341 | Summary#3 on NR Multicast and Broadcast Services | Moderator (CMCC) |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2005249 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2005406 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2005436 | Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2005531 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2005589 | Considerations on MBMS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2005693 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2005898 | Group Scheduling for NR-MBS | Intel Corporation |
| R1-2006013 | Group scheduling for NR Multicast and Broadcast Services | OPPO |
| R1-2006173 | On Mechanisms to support group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2006233 | Discussion on group scheduling mechanisms in NR MBS | CMCC |
| R1-2006320 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2006631 | On group scheduling mechanism for NR multicast and broadcast | Convida Wireless |
| R1-2006830 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2006918 | Mechanism for group scheduling of RRC_CONNECTED UEs in NR | Ericsson |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2005250 | Mechanisms to improve reliablity for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2005407 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2005437 | Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2005532 | Mechanisms for 5G Multicast / Broadcast Reliability Improvements for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2005590 | Considerations on MBMS reliability for RRC_CONNECTED UEs | Sony |
| R1-2005694 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2005899 | Mechanisms to Improve Reliability for NR-MBS | Intel Corporation |
| R1-2006014 | UL feedback for RRC-CONNECTED UEs in MBMS | OPPO |
| R1-2006174 | On Mechanisms to improve reliability for RRC_CONNECTED Ues | Samsung |
| R1-2006234 | Discussion on reliability improvement in NR MBS | CMCC |
| R1-2006321 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2006632 | On reliability enhancement for NR multicast and broadcast | Convida Wireless |
| R1-2006831 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2006863 | HARQ-based time-interleaving for NR Multicast/Broadcast | BBC |
| R1-2006919 | Mechanisms to improve reliability for RRC_CONNECTED UEs receiving PTM transmission | Ericsson |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2005272 | Discussion on multicast support for IDLE/INACTIVE UEs | Huawei, HiSilicon |
| R1-2005408 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | vivo |
| R1-2005438 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2005533 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2005695 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | CATT |
| R1-2006015 | Discussion on enhancements for IDLE and INACTIVE state UEs | OPPO |
| R1-2006175 | On Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2006235 | Discussion on NR MBS in RRC_IDLE RRC_INACTIVE states | CMCC |
| R1-2006322 | Basic function for broadcast/multicast | LG Electronics |
| R1-2006832 | Views on group scheduling for Multicast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2006920 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Ericsson |
| 8.12.4 | Other | |
| R1-2005439 | Preliminary Simulation Results of Rel-17 MBS | ZTE |
| R1-2005534 | Simulation assumptions and evaluation scenarios for 5G Multicast Services | Nokia, Nokia Shanghai Bell |
| R1-2006016 | PUCCH resource allocation for UL feedback in MBMS | OPPO |
| R1-2006236 | On R17 NR MBS WI | CMCC |
| R1-2006410 | Performance evaluation of HARQ for NR multicast | Huawei, HiSilicon |
| R1-2006658 | Other issues for Rel-17 MBS | vivo |
| R1-2006861 | MIMO support in NR Multicast/Broadcast | BBC |
| R1-2006921 | Assumptions for Performance Evaluations of NR-MBS | Ericsson |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2006415 | Work plan for Further MR-DC Enhancements | Huawei |
| R1-2006670 | Work plan for Rel17 WI on NR Dynamic spectrum sharing (DSS) | Ericsson |
| R1-2007442 | Summary of NR Dynamic spectrum sharing (DSS) in Email discussion [102-e-NR-DSS-DC_enh2-01] | Moderator (Ericsson) |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2005409 | Discussion on Scell scheduling Pcell | vivo |
| R1-2005440 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2005696 | Disucssion on cross-carrier scheduling from Scell to Pcell | CATT |
| R1-2005900 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2006063 | Cross-carrier scheduling | OPPO |
| R1-2006176 | Cross-carrier scheduling from SCell to Pcell | Samsung |
| R1-2006281 | Discussion on cross-carrier scheduling from Scell to Pcell | Spreadtrum Communications |
| R1-2006318 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2006362 | Discussion on cross-carrier scheduling for NR DSS | ETRI |
| R1-2006366 | Discussion on Cross-carrier scheduling from SCell to PCell | Beijing Xiaomi Mobile Software |
| R1-2006405 | Discussion on the PDCCH of SCell scheduling PDSCH or PUSCH on P(S)Cell | Huawei, HiSilicon |
| R1-2006469 | Cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2006473 | SCell scheduling PCell | InterDigital, Inc. |
| R1-2006509 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2006671 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2006749 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2006756 | Discussion on PDCCH of SCell scheduling PDSCH or PUSCH on PCell | ASUSTeK |
| R1-2006833 | Views on cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| 8.13.2 | Multi-cell PDSCH scheduling via a single DCI | |
| R1-2005410 | Discussion on joint scheduling | vivo |
| R1-2005441 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | ZTE |
| R1-2005628 | On Multi-cell PDSCH scheduling via a single DCI | MediaTek Inc. |
| R1-2005697 | Discussion on multi-cell PDSCH scheduling via a single DCI | CATT |
| R1-2005901 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2005909 | On support of Single DCI scheduling two cells | Nokia, Nokia Shanghai Bell |
| R1-2006064 | Multi-cell PDSCH scheduling via a single DCI | OPPO |
| R1-2006177 | On the use of one DCI format for scheduling on two cells | Samsung |
| R1-2006282 | Discussion on multi-cell PDSCH scheduling via a single DCI | Spreadtrum Communications |
| R1-2006319 | Discussion on multi-cell PDSCH scheduling via a single DCI | LG Electronics |
| R1-2006413 | Discussion on the PDCCH of P(S)Cell/SCell scheduling PDSCH on mulitple cells using a single DCI | Huawei, HiSilicon |
| R1-2006474 | A single DCI scheduling multi-cell | InterDigital, Inc. |
| R1-2006510 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | Apple |
| R1-2006583 | Discussion on multi-cell PDSCH scheduling via a single DCI | ASUSTeK |
| R1-2006672 | Discussion on single DCI scheduling PDSCH on multiple cells | Ericsson |
| R1-2006750 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | NTT DOCOMO, INC. |
| R1-2006834 | Views on multi-cell PDSCH scheduling via a single DCI | Qualcomm Incorporated |
| R1-2006987 | Discussion on joint scheduling | vivo |
| 8.13.3 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2005411 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2005442 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2005629 | On supporting efficient activation mechanism for SCells in NR CA | MediaTek Inc. |
| R1-2005698 | Disucssion on efficient activation/de-activation mechanism for Scell in NR CA | CATT |
| R1-2005908 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2006065 | Efficient activation/de-activation for Scell | OPPO |
| R1-2006178 | On efficient activation/de-activation mechanism for Scells | Samsung |
| R1-2006283 | Discussion on efficient activation/de-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2006511 | Views on Rel-17 DSS SCells efficient activation/de-activation | Apple |
| R1-2006673 | Reduced Latency SCell Activation | Ericsson |
| R1-2006751 | Discussion on efficient activation/deactivation mechanism for SCells | NTT DOCOMO, INC. |
| R1-2006754 | Efficient activation/deactivation of SCell | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2006835 | Views on efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2006927 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2007422 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2007423 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| 8.14 | Other | |
| R1-2005412 | Views on XR and Cloud Gaming evaluation | vivo |
| R1-2006470 | Extension of the Dynamic Spectrum Sharing (DSS) WID | Nokia, Nokia Shanghai Bell |
| R1-2006659 | Preliminary views on IoT over NTN | ZTE |