| TDoc | Title | Source |
|---|---|---|
| R1-2000150 | Draft Agenda of RAN1#100-e meeting | RAN1 Chair |
| R1-2000390 | RAN1#100-e Meeting_x00B_Timelines, Scope, Process | RAN1 Chair, MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2000151 | Report of RAN1#99 meeting | ETSI MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2000152 | LS reply on PUR transmission for NB-IoT/eMTC | RAN2, Ericsson |
| R1-2000153 | Feedback on RAN1 agreements on PUR | RAN2, Qualcomm |
| R1-2000154 | Reply LS on support of high peak data rate for Cat-M1 Ues in HD-FDD | RAN2, Qualcomm |
| R1-2000155 | LS on CLI measurements UE capabilities | RAN2, Qualcomm |
| R1-2000156 | LS on consistent Uplink LBT failure detection mechanism | RAN2, Qualcomm |
| R1-2000157 | Reply LS on signalling of sidelink RSRP and CSI | RAN2, LG Electronics |
| R1-2000158 | Response LS on additional high layer information for sidelink physical layer operations | RAN2, LG Electronics |
| R1-2000159 | Response LS on TX resource (re-)selection and MAC related agreements | RAN2, LG Electronics |
| R1-2000160 | Reply LS on sidelink synchronization under multiple synchronization sources with different timing | RAN2, Qualcomm |
| R1-2000161 | Reply LS on UL-SL prioritization | RAN2, OPPO |
| R1-2000162 | LS to RAN1 for clarification of PUCCH configuration | RAN2, Huawei |
| R1-2000163 | LS on Uplink skipping | RAN2, vivo |
| R1-2000164 | LS on default codebook parameters | RAN2, Nokia |
| R1-2000165 | LS on secondary DRX group | RAN2, Ericsson |
| R1-2000166 | LS on RAN2 progress on Scell uplink behaviour of the UE in dormancy | RAN2, Intel |
| R1-2000167 | Response LS on SL RLM/RLF | RAN2, InterDigital |
| R1-2000168 | LS on clarification of CLI resource configuration | RAN2, LG Electronics |
| R1-2000169 | LS on updates for TS 36.300 and TS 38.300 | RAN2, Huawei |
| R1-2000170 | Reply LS on clarification of OAM requirements for RIM | RAN3, Nokia |
| R1-2000171 | Reply LS on Tx DC location | RAN4, Huawei |
| R1-2000172 | Response LS on Reference Point for Timing Related Measurements in FR2 | RAN4, CATT |
| R1-2000173 | Reply LS on applicable timing for pathloss RS activated/updated by MAC-CE | RAN4, Apple |
| R1-2000174 | Reply LS to RAN2 on UL-SL Prioritization | RAN4, Futurewei |
| R1-2000175 | Reply to LS on UE capabilities on DAPS HO | RAN4, Qualcomm Incorporated |
| R1-2000176 | LS on UE capabilities and RRC signalling on Tx switching period delay | RAN4, Apple |
| R1-2000177 | LS on channel raster for NR V2X UE | RAN4, CATT |
| R1-2000178 | LS on clarifying NR PC5 priority level | SA2, LG Electronics |
| R1-2000179 | Reply LS on Response LS on SL RLM/RLF | SA2, Qualcomm |
| R1-2000202 | Draft reply LS on contention window update in Initiating device channel access mechanism of EN301 893 | Huawei |
| R1-2000246 | Draft reply LS on default Type I codebook parameters | ZTE |
| R1-2000247 | Draft Reply LS on NR V2X resource pool configuration and selection | vivo |
| R1-2000298 | On the misalignment between RAN1 and RAN2 about UL skipping | vivo |
| R1-2000299 | Drat reply LS on UL skipping | vivo |
| R1-2000300 | Draft Reply LS on default codebook parameters | vivo |
| R1-2000301 | Draft Reply LS on NR V2X resource pool configuration and selection | vivo |
| R1-2000353 | [DRAFT] Reply LS on Clarification of PUCCH Configuration | ZTE |
| R1-2000414 | Discussion on the RAN2 LS on Consistent Uplink LBT Failure Detection Mechanism | Nokia, Nokia Shanghai Bell |
| R1-2000416 | Discussion on the RAN2 LS on Consistent Uplink LBT Failure Detection Mechanism | Nokia, Nokia Shanghai Bell |
| R1-2000508 | Draft reply LS on clarification of CLI resource configuration | ZTE |
| R1-2000509 | Draft reply LS on CL measurements UE capabilites | ZTE |
| R1-2000510 | Draft reply LS on secondary DRX group | ZTE |
| R1-2000551 | DRAFT Reply LS on default codebook parameters | Nokia |
| R1-2000560 | Discussion on default codebook parameters | OPPO |
| R1-2000598 | Discussion on PUCCH Configuration | Samsung |
| R1-2000599 | Discussion on CLI Measurements UE Capabilities | Samsung |
| R1-2000600 | [DRAFT] LS response to RAN2 LS on clarification of CLI resource configuration | Samsung |
| R1-2000601 | Draft reply to RAN2 LS on default codebook parameters | Samsung |
| R1-2000648 | Discussion on consistent uplink LBT failure detection mechanism for NR-U | LG Electronics |
| R1-2000649 | Discussion on LS from RAN2 regarding SCell uplink behaviour of the UE in dormancy | LG Electronics |
| R1-2000650 | Discussion on clarification of CLI resource configuration | LG Electronics |
| R1-2000651 | Discussion on UE capability for CLI-RSSI and SRS-RSRP measurement | LG Electronics |
| R1-2000788 | [Draft] Reply LS on UL-SL prioritization | LG Electronics |
| R1-2000795 | Draft reply LS on CLI measurements UE capabilities | Nokia |
| R1-2000811 | Discussion on RAN2 LS on SCell uplink behaviour of the UE in dormancy | Futurewei |
| R1-2000947 | Draft reply LS on clarification of PUCCH configuration | Qualcomm Incorporated |
| R1-2000948 | Draft reply LS on CLI resource configuration | Qualcomm Incorporated |
| R1-2000949 | Dicussion on switched UL impact in RAN1 | Qualcomm Incorporated |
| R1-2001083 | Draft LS response on secondary DRX group | Ericsson |
| R1-2001084 | On secondary DRX group | Ericsson |
| R1-2001096 | Discussion on the feasibility of received interference power measurement in NR | Huawei, HiSilicon |
| R1-2001097 | Draft Reply LS on the feasibility of received interference power measurement | Huawei |
| R1-2001108 | draft Reply LS on clarification of CLI resource configuration | Huawei |
| R1-2001116 | Draft Reply LS for clarification of PUCCH configuration | Huawei |
| R1-2001122 | RAN1#100-e preparation phase on incoming LS | RAN1 Chair |
| R1-2001123 | RAN1#100-e preparation phase output on incoming LS | RAN1 Chair |
| R1-2001219 | Dicussion on switched UL impact in RAN1 | Qualcomm Incorporated |
| R1-2001236 | LS to RAN1 on Support of 2-step CFRA | RAN2, ZTE |
| R1-2001237 | LS to RAN1 on NR-U PRACH root sequence for 2-step RA | RAN2, Ericsson |
| R1-2001293 | Summary email discussion [100e-5LS-02] | vivo |
| R1-2001298 | Draft Reply LS on NR V2X resource pool configuration and selection | vivo |
| R1-2001304 | Reply LS on NR V2X resource pool configuration and selection | RAN1, vivo |
| R1-2001306 | Reply LS for clarification of PUCCH configuration | RAN1, Huawei |
| R1-2001307 | Reply LS on default codebook parameters | RAN1, Nokia |
| R1-2001318 | Summary of email discussion on [5LS-05] clarification of CLI resource configuration | LG Electronics |
| R1-2001319 | Reply LS on clarification of CLI resource configuration | LG Electronics |
| R1-2001376 | Reply LS on UL skipping | RAN1, vivo |
| R1-2001481 | Outcome of email thread [100e-5LS-01] Reply LS for clarification of PUCCH configuration | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000248 | Potential RAN1 impact to support TDM switching between the 1Tx and 2Tx UL carriers | vivo |
| R1-2000302 | Potential RAN1 impact to support TDM switching between the 1Tx and 2Tx UL carriers | vivo |
| R1-2000354 | Remaining Issues on Support of Tx Switching between Two Uplink Carriers | ZTE |
| R1-2000515 | Remaining issues on UL switching | CATT |
| R1-2000552 | On Tx switching between two uplink carriers | Nokia, Nokia Shanghai Bell |
| R1-2000597 | Remaining issues on support of Tx switching between two uplink carriers | China Telecommunications |
| R1-2000792 | Introduction of switched uplink operation | Nokia, Nokia Shanghai Bell |
| R1-2000882 | Summary of Tx switching between two uplink carriers | China Telecommunications |
| R1-2000883 | RAN1 aspects of UL Tx switching | Ericsson |
| R1-2000940 | Discussion on Tx Switching between Two Uplink Carriers | OPPO |
| R1-2001026 | Discussion on the remaining issues of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2001132 | Remaining Issues on Support of Tx Switching between Two Uplink Carriers | ZTE |
| R1-2001204 | Summary#2 of Tx switching between two uplink carriers | China Telecommunications |
| R1-2001274 | [100e-5.1LS-TxSwitching-02] Email discussion/approval on remaining issues on PUSCH preparation procedure | China Telecom |
| R1-2001275 | [100e-5.1LS-TxSwitching-03] Email discussion/approval on remaining issues on inter-band UL CA | China Telecom |
| R1-2001276 | [100e-5.1LS-TxSwitching-04] Email discussion/approval on remaining issues on inter-band EN-DC without SUL | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R1-2000245 | Enhancement on FR2 MPE mitigation | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2000214 | Correction on the resource block pair definition for 1.25 kHz subcarrier spacing | Huawei, HiSilicon |
| R1-2000222 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2000223 | Correction on Msg3 NPUSCH for NB-IoT EDT | Huawei, HiSilicon |
| R1-2000381 | Clarification of UL Gap for Rel-13 eMTC | ZTE |
| R1-2000867 | Correction on priority value in LTE V2X | Sharp |
| R1-2000933 | Correction on conditions for indicating Type 2 channel access procedure | WILUS Inc. |
| R1-2001110 | Correction on Rel-15 NWUS/MWUS | Huawei, HiSilicon |
| R1-2001112 | Inclusion of NWUS, MWUS, and RSS in TS 36.201 | Huawei, HiSilicon |
| R1-2001113 | Correction to measurements for inter-RAT handover | Huawei, HiSilicon |
| R1-2001126 | RAN1#100-e preparation phase on LTE Rel-15 (& earlier) CRs | Ad-hoc chair (Ericsson) |
| R1-2001127 | RAN1#100-e preparation phase output on LTE Rel-15 (& earlier) CRs | Ad-hoc chair (Ericsson) |
| R1-2001224 | Correction on priority value in LTE V2X | Sharp |
| R1-2001305 | Correction on conditions for indicating Type 2 channel access procedure | WILUS Inc. |
| R1-2001321 | Correction on the resource block pair definition for 1.25 kHz subcarrier spacing | Huawei, HiSilicon |
| R1-2001322 | Correction on the resource block pair definition for 1.25 kHz subcarrier spacing | Huawei, HiSilicon |
| R1-2001323 | Correction on the resource block pair definition for 1.25 kHz subcarrier spacing | Huawei, HiSilicon |
| R1-2001324 | Correction to measurements for inter-RAT handover | Huawei, HiSilicon |
| R1-2001325 | Correction on priority value in LTE V2X | Sharp |
| R1-2001326 | Correction on Msg3 NPUSCH for NB-IoT EDT | Huawei, HiSilicon |
| R1-2001327 | Correction on Rel-15 NWUS/MWUS | Huawei, HiSilicon |
| R1-2001328 | Inclusion of NWUS, MWUS, and RSS in TS 36.201 | Huawei, HiSilicon |
| R1-2001329 | Correction on priority value in LTE V2X | Sharp |
| R1-2001330 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001331 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001332 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001333 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001334 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001335 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs | Huawei, HiSilicon |
| R1-2001336 | Correction on Msg3 NPUSCH for NB-IoT EDT | Huawei, HiSilicon |
| R1-2001337 | Correction on Rel-15 NWUS/MWUS | Huawei, HiSilicon |
| R1-2001378 | Clarification on MPDCCH monitoring during UL gaps | ZTE, Sanechips |
| R1-2001379 | Clarification on MPDCCH monitoring during UL gaps | ZTE, Sanechips |
| R1-2001380 | Clarification on MPDCCH monitoring during UL gaps | ZTE, Sanechips |
| R1-2001381 | Clarification on MPDCCH monitoring during UL gaps | ZTE, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R1-2001427 | Miscellaneous corrections for Rel-16 LTE-MTC features in 36.211 | Ericsson |
| R1-2001428 | Miscellaneous corrections for Rel-16 NB-IoT features in 36.211 | Ericsson |
| R1-2001429 | Corrections to LTE terrestrial broadcast | Ericsson |
| R1-2001430 | Corrections to DL MIMO efficiency enhancements for LTE | Ericsson |
| R1-2001431 | Miscellaneous corrections for Rel-16 eMTC features in 36.212 | Futurewei |
| R1-2001432 | Miscellaneous corrections for Rel-16 NB-IoT features in 36.212 | Futurewei |
| R1-2001433 | Corrections to Additional MTC Enhancements for LTE | Motorola Mobility |
| R1-2001434 | Corrections to Additional enhancements for NB-IoT | Motorola Mobility |
| R1-2001435 | Corrections to single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA | Motorola Mobility |
| R1-2001436 | Corrections to DL MIMO efficiency enhancements for LTE | Motorola Mobility |
| R1-2001477 | Updated consolidated parameter list for Rel-16 LTE | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R1-2000227 | Corrections on UE-group wake-up signal | Huawei, HiSilicon |
| R1-2000368 | Clarification of group WUS for MTC | ZTE |
| R1-2000700 | UE-group wake-up signal | Qualcomm Incorporated |
| R1-2000815 | Feature lead summary for UE-group WUS | Qualcomm Incorporated |
| R1-2001066 | Clarification of UE-group wake-up signal for MTC | Nokia, Nokia Shanghai Bell |
| R1-2001196 | Updated feature lead summary for UE-group WUS | Qualcomm Incorporated |
| R1-2001249 | FL Summary of email discussion [100e-LTE-eMTC5-GroupWUS-01] | Qualcomm |
| R1-2001250 | FL Summary of email discussion [100e-LTE-eMTC5-GroupWUS-02] | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R1-2000219 | Corrections on transmission in preconfigured UL resources | Huawei, HiSilicon |
| R1-2000369 | Remaining issues on transmission in preconfigured UL resources for eMTC | ZTE |
| R1-2000506 | LTE-M Pre-configured UL Resources Design Considerations | Sierra Wireless, S.A. |
| R1-2000701 | Support for transmission in preconfigured UL resources | Qualcomm Incorporated |
| R1-2000907 | Remaining issues on transmission in preconfigured UL resources for eMTC | NTT DOCOMO, INC. |
| R1-2001054 | Corrections for Preconfigured UL resources for LTE-MTC | Ericsson |
| R1-2001147 | LTE-M Preconfigured UL Resources Summary RAN1 #100-e | Sierra Wireless |
| R1-2001199 | LTE-M Preconfigured UL Resources Summary#2 RAN1 #100-e | Sierra Wireless |
| R1-2001347 | TP on missing starting RV for the initial PUR transmission | Sierra Wireless |
| TDoc | Title | Source |
|---|---|---|
| R1-2000220 | Corrections on scheduling of multiple transport blocks | Huawei, HiSilicon |
| R1-2000370 | Remaining issues on scheduling enhancement for MTC | ZTE |
| R1-2000507 | LTE-M Multiple Transport Block Grant Design Considerations | Sierra Wireless, S.A. |
| R1-2000652 | Remaining issues on multiple transport blocks scheduling in MTC | LG Electronics |
| R1-2000702 | Scheduling of multiple DL/UL transport blocks | Qualcomm Incorporated |
| R1-2001055 | Corrections for Multi-TB scheduling for LTE-MTC | Ericsson |
| R1-2001056 | Feature lead summary for Multi-TB scheduling for LTE-MTC | Ericsson |
| R1-2001086 | Remaining details on STUF for eMTC multiple TB scheduling | Futurewei |
| R1-2001185 | Feature lead summary#2 for Multi-TB scheduling for LTE-MTC | Ericsson |
| R1-2001214 | Scheduling of multiple DL/UL transport blocks | Qualcomm Incorporated |
| R1-2001220 | Feature lead summary#3 for Multi-TB scheduling for LTE-MTC | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000221 | Corrections on eMTC co-existence with NR | Huawei, HiSilicon |
| R1-2000371 | Remaining issues on LTE-MTC resource reservation | ZTE |
| R1-2000703 | Coexistence of LTE-MTC with NR | Qualcomm Incorporated |
| R1-2001057 | Corrections for NR coexistence performance improvements for LTE-MTC | Ericsson |
| R1-2001058 | Feature lead summary for NR coexistence performance improvements for LTE-MTC | Ericsson |
| R1-2001186 | Feature lead summary#2 for NR coexistence performance improvements for LTE-MTC | Ericsson |
| R1-2001221 | Feature lead summary#3 for NR coexistence performance improvements for LTE-MTC | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000372 | Correction on MPDCCH performance improvement | ZTE |
| R1-2000704 | MPDCCH performance improvement | Qualcomm Incorporated |
| R1-2001020 | Feature lead summary #1 on MPDCCH performance improvement | Huawei |
| R1-2001059 | Corrections for MPDCCH performance improvement for LTE-MTC | Ericsson |
| R1-2001177 | Feature lead summary #2 on MPDCCH performance improvement | Huawei |
| R1-2001277 | Feature lead summary #1 on [100e-LTE-eMTC5-MPDCCH-improvement-01] | Huawei |
| R1-2001278 | Feature lead summary #1 on [100e-LTE-eMTC5-MPDCCH-improvement-02] | Huawei |
| R1-2001279 | Feature lead summary #1 on [100e-LTE-eMTC5-MPDCCH-improvement-03] | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000228 | Corrections on CE Mode A and B improvements for non-BL UEs | Huawei, HiSilicon |
| R1-2000373 | Correction on CSI-RS based CSI feedback for non-BL UE | ZTE |
| R1-2000653 | Remaining issues on CE mode A and B improvements for non-BL UEs | LG Electronics |
| R1-2000654 | FL summary of CE mode A and B improvements for non-BL UEs | LG Electronics |
| R1-2001060 | Corrections for CE mode improvements for non-BL UEs for LTE-MTC | Ericsson |
| R1-2001205 | FL summary#2 of CE mode A and B improvements for non-BL UEs | LG Electronics |
| R1-2001247 | FL summary#3 of CE mode A and B improvements for non-BL UEs | LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2000229 | Corrections on use of LTE control channel region for DL transmission | Huawei, HiSilicon |
| R1-2000374 | Correction on use of LTE control channel region | ZTE |
| R1-2001052 | Feature lead summary on use of LTE control channel region | Nokia, Nokia Shanghai Bell |
| R1-2001188 | Feature lead summary#2 on use of LTE control channel region | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2000375 | Remaining issues on RSS for measurement improvement | ZTE |
| R1-2000580 | Use of RSS for measurement in Connected Mode | Sony |
| R1-2000705 | Measurements based on RSS | Qualcomm Incorporated |
| R1-2000791 | Summary of the use of RSS for measurement improvements | Sony Europe B.V. |
| R1-2001152 | Feature Lead Summary of the use of RSS for measurement improvements | Sony Europe B.V. |
| R1-2001175 | Issues for email discussion on the use of RSS for measurement improvements | Sony Europe B.V. |
| TDoc | Title | Source |
|---|---|---|
| R1-2000215 | Corrections on UE-group wake-up signal | Huawei, HiSilicon |
| R1-2000376 | Clarification of group WUS for NB-IoT | ZTE |
| R1-2000706 | UE-group wake-up signal | Qualcomm Incorporated |
| R1-2000790 | Feature lead summary of Group WUS for NB-IoT | Ericsson |
| R1-2001187 | Feature lead summary#2 of Group WUS for NB-IoT | Ericsson |
| R1-2001222 | Feature lead summary#3 of Group WUS for NB-IoT | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000216 | Corrections on transmission in preconfigured UL resources | Huawei, HiSilicon |
| R1-2000377 | Remaining issues on transmission in preconfigured UL resources for NB-IoT | ZTE |
| R1-2000707 | Support for transmission in preconfigured UL resources | Qualcomm Incorporated |
| R1-2000908 | Remaining issues on transmission in preconfigured UL resources for NB-IoT | NTT DOCOMO, INC. |
| R1-2001021 | Feature lead summary #1 on transmission in pre-configured UL resources | Huawei |
| R1-2001061 | Corrections for Preconfigured UL resources for NB-IoT | Ericsson |
| R1-2001087 | PUR and interactions with legacy features | Futurewei |
| R1-2001165 | Feature lead summary #2 on transmission in pre-configured UL resources | Huawei |
| R1-2001251 | Feature lead summary #3 on transmission in pre-configured UL resources | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000217 | Corrections on scheduling of multiple DL/UL transport blocks | Huawei, HiSilicon |
| R1-2000378 | Remaining issues on scheduling enhancement for NB-IoT | ZTE |
| R1-2000708 | Scheduling of multiple DL/UL transport blocks | Qualcomm Incorporated |
| R1-2001062 | Corrections for Multi-TB scheduling for NB-IoT | Ericsson |
| R1-2001130 | FL summary on Multiple TB scheduling enhancement for NB-IoT | ZTE |
| R1-2001201 | FL summary#2 on Multiple TB scheduling enhancement for NB-IoT | ZTE |
| R1-2001398 | TP for gaps of multicast for multiple TB scheduling of NB-IoT | ZTE |
| R1-2001399 | TP for miscellaneous changes for multiple TB scheduling of NB-IoT | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2000218 | Corrections on coexistence of NB-IoT with NR | Huawei, HiSilicon |
| R1-2000379 | Remaining issues on NB-IoT resource reservation | ZTE |
| R1-2000709 | Coexistence of NB-IoT with NR | Qualcomm Incorporated |
| R1-2001022 | Feature lead summary #1 on coexistence of NB-IoT with NR | Huawei |
| R1-2001063 | Corrections for NR coexistence performance improvements for NB-IoT | Ericsson |
| R1-2001178 | Feature lead summary #2 on coexistence of NB-IoT with NR | Huawei |
| R1-2001280 | Feature lead summary #1 on [100e-LTE-NB_IOTenh3-NR-Coexistence-01] | Huawei |
| R1-2001281 | Feature lead summary #1 on [100e-LTE-NB_IOTenh3-NR-Coexistence-02] | Huawei |
| R1-2001282 | Feature lead summary #1 on [100e-LTE-NB_IOTenh3-NR-Coexistence-03] | Huawei |
| R1-2001339 | Feature lead summary #2 on [100e-LTE-NB_IOTenh3-NR-Coexistence-02] | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000380 | Correction of NRS on a non-anchor carrier for paging | ZTE |
| R1-2000814 | Feature lead summary for NRS in non-anchor carrier | Qualcomm Incorporated |
| R1-2001019 | Corrections on presence of NRS on a non-anchor carrier for paging | Huawei, HiSilicon |
| R1-2001271 | Outcome of email thread [100e-LTE-NB_IOTenh3-NRS-01] - Issues for NRS in non-anchor | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2001114 | Further considerations on RRC parameter lists for NB-IoT | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2001139 | Feature summary on LTE DL MIMO efficiency enhancement | Huawei |
| R1-2001179 | Feature summary#2 on LTE DL MIMO efficiency enhancement | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000225 | Corrections on additional SRS symbols | Huawei, HiSilicon |
| R1-2000559 | Maintenance for additional SRS symbols | Nokia, Nokia Shanghai Bell |
| R1-2000594 | Remaining issues on additional SRS symbols | Lenovo, Motorola Mobility |
| R1-2000655 | Text proposals on additional SRS symbols | LG Electronics |
| R1-2000710 | Additional SRS symbols | Qualcomm Incorporated |
| R1-2000717 | Corrections to SRS | Intel Corporation |
| R1-2000942 | Maintenance for additional SRS symbols | Ericsson |
| R1-2001283 | Feature summary #1 on [100e-LTE_DL_MIMO_EE-AddSRS-01] | Huawei |
| R1-2001284 | Feature summary #1 on [100e-LTE_DL_MIMO_EE-AddSRS-02] | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000226 | Remaining issues of additional SRS symbols | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000713 | Updated TR 36.976 | Qualcomm Incorporated |
| R1-2001151 | Summary of issues for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| R1-2001197 | Updated summary of issues for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| R1-2001230 | TR 36.976 Overall description of LTE-based 5G broadcast | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000213 | Corrections to 36.211 and 36.213 for the 0.37kHz subcarrier spacing MBSFN | Huawei, HiSilicon |
| R1-2000711 | Support of longer numerologies for rooftop reception | Qualcomm Incorporated |
| R1-2001272 | Outcome of email thread [100e-LTE_TerrBcast-02] - Issues for 300us numerology | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000712 | Corrections for CAS reception | Qualcomm Incorporated |
| R1-2001273 | Outcome of email thread [100e-LTE_TerrBcast-03] - Issues for CAS | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2001111 | Text proposal for new numerology in TS 36.201 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000224 | On LTE UE features in Rel-16 | Huawei, HiSilicon |
| R1-2000574 | Discussion on LTE Rel-16 UE Features | ZTE |
| R1-2000714 | Views on UE features | Qualcomm Incorporated |
| R1-2000909 | RAN1 UE features list for Rel-16 LTE | NTT DOCOMO, INC., AT&T |
| R1-2001485 | RAN1 UE features list for Rel-16 LTE after RAN1#100-e | Moderator (AT&T, NTT DOCOMO, INC.) |
| R1-2001486 | LS on Rel-16 RAN1 UE features lists for LTE | RAN1, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2001124 | RAN1#100-e preparation phase on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2001125 | RAN1#100-e preparation phase output NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2001474 | Corrections to 38.213 including alignment of terminology across specifications in RAN1#100-e | Samsung |
| R1-2001476 | CR on UL PTRS density selection | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000602 | Discussion on SSB-RO association | Samsung |
| R1-2000603 | Draft CR on SSB-RO association | Samsung |
| R1-2001098 | Correction on ATF measurements for SS RSRPB | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000237 | Correction of SRS bandwidth | Ericsson |
| R1-2000604 | Draft CR on TCI state for PDCCH during RA procedure | Samsung |
| R1-2000656 | Clarification of the maximum number of CSI-RS resources in resource setting | LG Electronics |
| R1-2000744 | Correction on TRS configuration to TS38.214 | CMCC |
| R1-2000778 | PUCCH Spatial Relation after CBRA BFR | Nokia, Nokia Shanghai Bell |
| R1-2000840 | Draft CR on QCL Assumption for DL PT-RS and DMRS | Apple |
| R1-2000841 | Draft CR on QCL Indication for CSI-RS | Apple |
| R1-2000842 | Draft CR on UL PTRS density selection | Apple |
| R1-2000868 | Clarification on UE assumptions for deriving the CQI index | Sharp |
| R1-2000944 | Clarification on number of occupied CPUs and delay requirements for CSI reports using PUSCH | Nokia, Nokia Shanghai Bell |
| R1-2000950 | Draft CR on resource and port occupation of duplicate CSI-RS resource | Qualcomm Incorporated |
| R1-2000951 | Discussion on CR on resource and port occupation of duplicate CSI-RS resource | Qualcomm Incorporated |
| R1-2000998 | Clarification of PTRS port association for PUSCH | Nokia, Nokia Shanghai Bell |
| R1-2001082 | Correction on CSI-RS resource set configuration | Ericsson |
| R1-2001133 | PUCCH Spatial Relation after CBRA BFR | Nokia, Nokia Shanghai Bell |
| R1-2001210 | Draft CR on UL PTRS density selection | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2000249 | Draft 38.213 CR on UL skipping | vivo |
| R1-2000303 | Draft 38.214 CR on UL skipping | vivo |
| R1-2000415 | Correction on PDCCH Blind Detection for NR-DC | ZTE |
| R1-2000486 | Correction on multiplexing HARQ-ACK/SR/CSI in a PUCCH determined based on PRI | OPPO |
| R1-2000487 | Correction on multiplexing HARQ-ACK/SR/CSI in a multi-CSI-PUCCH | OPPO |
| R1-2000516 | Clarification for processing order of UL multiplexing and cancellation | CATT |
| R1-2000517 | Correction on the definition for timeline condition | CATT |
| R1-2000518 | Correction for PUCCH repetition transmission | CATT |
| R1-2000553 | Draft 38.211 CR Intra-slot frequency hopping with 1-symbol PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2000555 | Draft 38.212 CR Correction to dynamic frequency domain resource allocation type selection | Nokia, Nokia Shanghai Bell |
| R1-2000556 | Draft 38.214 CR Corrections to PDSCH PRB bundling | Nokia, Nokia Shanghai Bell |
| R1-2000558 | Draft 38.214 CR Correction to TBS determination when 3824| Nokia, Nokia Shanghai Bell |
|
| R1-2000579 | Clarification on UE behaviour with no transmission of UL-SCH | Fujitsu Limited |
| R1-2000718 | Clarification on UE features on BWP operations | Intel Corporation |
| R1-2000808 | Clarification for N_info | Ericsson |
| R1-2000869 | Correction on rate matching output sequence length | Sharp |
| R1-2000870 | Correction on removal of padding bits in DCI size alignment procedure | Sharp |
| R1-2000952 | Draft CR on clarifying A-CSI multiplexing on PUSCH with slot aggregation | Qualcomm Incorporated |
| R1-2000994 | UL grant overridden between configured grant and RAR grant | ASUSTeK |
| R1-2001032 | Clarification on UCI multiplexing on PUSCH | Huawei, HiSilicon |
| R1-2001100 | Correction on PDCCH candidate colliding with RB-symbol level RMR in TS38.213 | Huawei, HiSilicon |
| R1-2001101 | Correction on rate-matching for PDSCH/PDSCH with SPS in TS38.214 | Huawei, HiSilicon |
| R1-2001115 | Correction on PUSCH with a Type 1 configured grant | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000554 | Draft 36.213 CR Correction on PUSCH and PDSCH scheduling with CSS | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2001099 | Correction on resetting accumulation of closed-loop power control | Huawei, HiSilicon |
| R1-2001473 | Correction on resetting accumulation of closed-loop power control | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2001074 | Discussion of need for correction for inconsistent shadow fading parameters in NTN rural scenario | Nokia, Nokia Shanghai Bell |
| R1-2001075 | Correction for inconsistent shadow fading parameters in NTN rural scenario | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2000557 | Draft 38.215 CR Introduction of UE UTRAN FDD measurements for SRVCC from NR to UMTS | Nokia, Nokia Shanghai Bell |
| R1-2001053 | Editorial corrections to MIMO enhancements | Ericsson |
| R1-2001355 | RAN1 input on Rel-16 WIs (except NR-U) related changes for 38.300 running CR | Nokia |
| R1-2001356 | LS to RAN2 on Rel-16 WIs (except NR-U) related changes for 38.300 running CR | RAN1, Nokia |
| R1-2001437 | Corrections to NR-based access to unlicensed spectrum | Ericsson |
| R1-2001438 | Corrections to L1-SINR definitions | Intel Corporation |
| R1-2001439 | Corrections to NR positioning support | Intel Corporation |
| R1-2001440 | Corrections to cross layer interference measurements | Intel Corporation |
| R1-2001441 | Corrections on NR - U | Nokia |
| R1-2001442 | Corrections on NR V2X | Nokia |
| R1-2001443 | Corrections on Cross-carrier Scheduling with Different Numerologies | Nokia |
| R1-2001444 | Corrections on NR URLLC support | Nokia |
| R1-2001445 | Corrections on NR enhanced MIMO | Nokia |
| R1-2001446 | Corrections on Industrial IoT | Nokia |
| R1-2001447 | Corrections of cross-slot scheduling restriction and CSI/L1-RSRP measurement outside active time | Nokia |
| R1-2001448 | Corrections on two-step RACH after RAN1#100-e | Nokia |
| R1-2001449 | Corrections of NR positioning support | Nokia |
| R1-2001450 | Corrections on two-step RACH | Samsung |
| R1-2001451 | Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies | Samsung |
| R1-2001452 | Corrections on integrated access and backhaul | Samsung |
| R1-2001453 | Corrections on Industrial IoT | Samsung |
| R1-2001454 | Corrections on MIMO enhancements | Samsung |
| R1-2001455 | Corrections on Mobility Enhancements | Samsung |
| R1-2001456 | Corrections on shared spectrum channel access | Samsung |
| R1-2001457 | Corrections on Positioning | Samsung |
| R1-2001458 | Corrections on Sidelink | Samsung |
| R1-2001459 | Corrections on UE power savings | Samsung |
| R1-2001460 | Corrections on Ultra Reliable Low Latency Communications Enhancements | Samsung |
| R1-2001461 | Corrections for Rel-16 NR-U after RAN1#100-e | Huawei |
| R1-2001462 | Corrections for NR MIMO after RAN1#100-e | Huawei |
| R1-2001463 | Corrections for URLLC after RAN1#100-e | Huawei |
| R1-2001464 | Corrections for power saving after RAN1#100-e | Huawei |
| R1-2001465 | Corrections on 5G V2X sidelink features after RAN1#100-e | Huawei |
| R1-2001466 | Corrections to integrated access and backhaul for NR | Ericsson |
| R1-2001467 | Corrections to NR positioning support | Ericsson |
| R1-2001468 | Corrections to two-step RACH | Ericsson |
| R1-2001469 | Corrections to cross-carrier scheduling with different numerologies | Ericsson |
| R1-2001470 | Corrections to NR-based access to unlicensed spectrum | Ericsson |
| R1-2001471 | Corrections to V2X | Ericsson |
| R1-2001472 | Corrections to MIMO enhancements | Ericsson |
| R1-2001475 | Introduction of half-duplex operation in CA with unpaired spectrum | Samsung |
| R1-2001478 | Updated consolidated parameter list for Rel-16 NR | Qualcomm |
| R1-2001479 | LS on updated Rel-16 LTE and NR parameter lists | RAN1, Qualcomm |
| R1-2001480 | Corrections to V2X measurement definitions | Intel Corporation |
| TDoc | Title | Source |
|---|---|---|
| R1-2000250 | Remaining issues on channel structure for 2-step RACH | vivo |
| R1-2000304 | Remaining issues on channel structure for 2-step RACH | vivo |
| R1-2000476 | Discussion on Channel Structure for Two-Step RACH | OPPO |
| R1-2000605 | Channel Structure for Two-Step RACH | Samsung |
| R1-2000657 | Remaining details of Channel Structure for 2-step RACH | LG Electronics |
| R1-2000719 | Remaining details of channel structure for 2-step RACH | Intel Corporation |
| R1-2000809 | FL summary on the maintenance of the 2-step RACH channel structure | ZTE |
| R1-2000819 | Channel Structure Related Corrections For 2-Step RACH | Ericsson |
| R1-2000843 | Remaining issues on channel structure for 2-step RACH | Apple |
| R1-2000910 | Maintenance for Channel Structure for Two-Step RACH | NTT DOCOMO, INC. |
| R1-2001029 | Corrections on channel structure of 2-step RACH | Huawei, HiSilicon |
| R1-2001073 | RAN1 terminology alignment for two-step RACH | Nokia, Nokia Shanghai Bell |
| R1-2001206 | FL summary#2 on the maintenance of the 2-step RACH channel structure | ZTE |
| R1-2001368 | Outcome of email thread [100e-NR-2step-RACH-ChStructure-01] | ZTE |
| R1-2001369 | Outcome of email thread [100e-NR-2step-RACH-ChStructure-02] | ZTE |
| R1-2001370 | Outcome of email thread [100e-NR-2step-RACH-ChStructure-03] | ZTE |
| R1-2001371 | Editorial TPs for 2-step RACH | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2000251 | Remaining issues on procedure for 2-step RACH | vivo |
| R1-2000305 | Remaining issues on procedure for 2-step RACH | vivo |
| R1-2000397 | Remaining issues of the 2-step RACH procedures | ZTE, Sanechips |
| R1-2000477 | Remaining issues for procedure of 2-step RACH | OPPO |
| R1-2000581 | Differentiating between MsgB carrying RRC and other messages | Sony |
| R1-2000606 | Procedure for Two-step RACH | Samsung |
| R1-2000658 | Remaining details of Procedure for 2-step RACH | LG Electronics |
| R1-2000720 | Remaining details of procedure for 2-step RACH | Intel Corporation |
| R1-2000810 | FL summary on the maintenance of the 2-step RACH procedures | ZTE |
| R1-2000820 | Procedure Related Corrections for 2-Step RACH | Ericsson |
| R1-2000844 | Remaining issues on 2-step RACH procedure | Apple |
| R1-2000911 | Maintenance for Procedure for Two-step RACH | NTT DOCOMO, INC. |
| R1-2001030 | Corrections on procedure of 2-step RACH | Huawei, HiSilicon |
| R1-2001207 | FL summary#2 on the maintenance of the 2-step RACH procedures | ZTE |
| R1-2001229 | Outcome of email thread [100e-NR-2step-RACH-Procedure-03] | ZTE |
| R1-2001372 | Summary of email thread [100e-NR-2step-RACH-Procedure-01] | ZTE |
| R1-2001373 | Outcome of email thread [100e-NR-2step-RACH-Procedure-02] | ZTE |
| R1-2001374 | Outcome of email thread [100e-NR-2step-RACH-Procedure-04] | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2000659 | Remaining details of designing 2-step RACH for NR-U | LG Electronics |
| R1-2000821 | msgA PUSCH Configuration in 2-step CFRA | Ericsson |
| R1-2001102 | Further considerations on 2-step RACH | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2001299 | RAN1 input on NR-U related changes for 38.300 running CR | Qualcomm (rapporteur) |
| R1-2001300 | LS to RAN2 on NR-U related changes for 38.300 running CR | RAN1, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R1-2000252 | Remaining issues on initial access signals and channles | vivo |
| R1-2000306 | Remaining issues on initial access signals and channles | vivo |
| R1-2000393 | Maintenance on the initial access signals for NR-U | ZTE, Sanechips |
| R1-2000418 | Remaining issues on initial access signals/channels | Spreadtrum Communications |
| R1-2000467 | Discussion on the remaining issues of initial access signal/channel | OPPO |
| R1-2000500 | Remaining issues on Initial Access Signals and Channels for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2000607 | Initial access signals and channels for NR-U | Samsung |
| R1-2000660 | Remaining issues of initial access signals and channels for NR-U | LG Electronics |
| R1-2000823 | Initial access signals and channels | Ericsson |
| R1-2000953 | TP for Initial access signals and channels for NR-U | Qualcomm Incorporated |
| R1-2001036 | Corrections on the initial access signals and channels | Huawei, HiSilicon |
| R1-2001150 | FL summary of 7.2.2.1.1 NR-U initial access signals and channels | Qualcomm |
| R1-2001256 | Outcome of email thread [100e-NR-unlic-NRU-InitSignalsChannels-01] | Qualcomm |
| R1-2001257 | Outcome of email thread [100e-NR-unlic-NRU-InitSignalsChannels-02] | Qualcomm |
| R1-2001258 | Outcome of email thread [100e-NR-unlic-NRU-InitSignalsChannels-03] | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R1-2000195 | Corrections on PDCCH/GC-PDCCH monitoring procedure in TS38.213 | Huawei, HiSilicon |
| R1-2000253 | Remaining issues on physical DL channel design in unlicensed spectrum | vivo |
| R1-2000307 | Remaining issues on physical DL channel design in unlicensed spectrum | vivo |
| R1-2000394 | Maintenance on the DL channels for NR-U | ZTE, Sanechips |
| R1-2000435 | Remaining issues on DL signals and channels for NR-U operation | MediaTek Inc. |
| R1-2000468 | Discussion on the remaining issues of DL signals and channels | OPPO |
| R1-2000501 | Remaining issues on DL signals and channels | Nokia, Nokia Shanghai Bell |
| R1-2000505 | Text proposal on Rel-16 PDSCH DMRS | Panasonic Corporation |
| R1-2000608 | DL signals and channels for NR-U | Samsung |
| R1-2000661 | Remaining issues of DL signals and channels for NR-U | LG Electronics |
| R1-2000723 | DL signals and channels for NR-unlicensed | Intel Corporation |
| R1-2000769 | Remaining issues on DL signals and channels for NR-U | ETRI |
| R1-2000824 | DL signals and channels | Ericsson |
| R1-2000871 | Remaining issues and corrections on DL signals and channels for NR-U | Sharp |
| R1-2000954 | TP for DL signals and channels for NR-U | Qualcomm Incorporated |
| R1-2001001 | Remaining issues on search space set switching | Google Inc. |
| R1-2001047 | Feature lead summary for NR-U DL Signals and Channels | Lenovo, Motorola Mobility |
| R1-2001193 | Feature lead summary#2 for NR-U DL Signals and Channels | Lenovo, Motorola Mobility |
| R1-2001340 | Feature Lead Summary: Email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-01] on COT duration indication | Lenovo, Motorola Mobility |
| R1-2001341 | Feature Lead Summary: Email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-02] on available LBT bandwidth/RB set | Lenovo, Motorola Mobility |
| R1-2001342 | Feature Lead Summary: Email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-03] on search space set monitoring/switching | Lenovo, Motorola Mobility |
| R1-2001343 | Feature Lead Summary: Email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-04] on dropping/shifting of DM-RS | Lenovo, Motorola Mobility |
| R1-2001387 | Agreements from email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-01] on COT duration indication | Lenovo, Motorola Mobility |
| R1-2001388 | Agreements from email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-02] on available LBT bandwidth/RB set | Lenovo, Motorola Mobility |
| R1-2001389 | Agreements from email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-03] on search space set monitoring/switching | Lenovo, Motorola Mobility |
| R1-2001390 | Agreements from email discussion [100e-NR-unlic-NRU-DL_Signals_and_Channels-04] on dropping/shifting of DM-RS | Lenovo, Motorola Mobility |
| TDoc | Title | Source |
|---|---|---|
| R1-2000196 | Corrections on uplink signals and channels | Huawei, HiSilicon |
| R1-2000254 | Remaining issues on physical UL channel design in unlicensed spectrum | vivo |
| R1-2000308 | Remaining issues on physical UL channel design in unlicensed spectrum | vivo |
| R1-2000410 | Remaining Issues on UL Signals and Channels for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2000436 | Remaining issues on UL signals and channels for NR-U operation | MediaTek Inc. |
| R1-2000469 | Discussion on the remaining issues of UL signals and channels | OPPO |
| R1-2000591 | Text proposals for UL signals and channels for NR-U | Lenovo, Motorola Mobility |
| R1-2000609 | UL signals and channels for NR-U | Samsung |
| R1-2000647 | TP for SRS configuration | CATT |
| R1-2000662 | Remaining issues of UL signals and channels for NR-U | LG Electronics |
| R1-2000770 | UL signals and channels | ETRI |
| R1-2000825 | UL signals and channels | Ericsson |
| R1-2000831 | Feature Lead Summary for UL Signals and Channels | Ericsson |
| R1-2000872 | Remaining issues and corrections on UL signals and channels for NR-U | Sharp |
| R1-2000955 | TP for UL signals and channels for NR-U | Qualcomm Incorporated |
| R1-2001203 | Feature Lead Summary#2 for UL Signals and Channels | Ericsson |
| R1-2001308 | Outcome of email thread [100e-NR-unlic-NRU-ULSignalsChannels-01] | Ericsson |
| R1-2001309 | Outcome of email thread [100e-NR-unlic-NRU-ULSignalsChannels-02] | Ericsson |
| R1-2001310 | Outcome of email thread [100e-NR-unlic-NRU-ULSignalsChannels-03] | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000197 | Corrections on the channel access procedure in TS 37.213 | Huawei, HiSilicon |
| R1-2000255 | Remaining issues on the channel access procedures | vivo |
| R1-2000309 | Remaining issues on the channel access procedures | vivo |
| R1-2000392 | Maintenance on the channel access procedure for NR-U | ZTE, Sanechips |
| R1-2000411 | Remaining Issues on Channel Access Procedures for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2000437 | Remaining issues on channel access for NR-U operation | MediaTek Inc. |
| R1-2000470 | Discussion on the remaining issues of channel access procedure | OPPO |
| R1-2000544 | Remaining issues on channel access procedures | Fujitsu |
| R1-2000610 | Channel access procedures for NR-U | Samsung |
| R1-2000663 | Remaining issues of channel access procedure for NR-U | LG Electronics |
| R1-2000724 | Channel access mechanism for NR-unlicensed | Intel Corporation |
| R1-2000767 | Remaining issues on CP extension | NEC |
| R1-2000799 | Feature Lead’s Summary on Channel Access Procedures | Nokia |
| R1-2000826 | Channel access procedures | Ericsson |
| R1-2000873 | Remaining issues and corrections on channel access procedure for NR-U | Sharp |
| R1-2000912 | Channel access procedures for NR-U | NTT DOCOMO, INC. |
| R1-2000934 | Remaining issues on channel access procedure for NR-U | WILUS Inc. |
| R1-2000956 | TP for Channel access procedures for NR unlicensed | Qualcomm Incorporated |
| R1-2001088 | Corrections to channel access procedures | Futurewei |
| R1-2001202 | Feature Lead’s Summary#2 on Channel Access Procedures | Nokia |
| R1-2001311 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-01] | Nokia |
| R1-2001312 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-02] | Nokia |
| R1-2001313 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-03] | Nokia |
| R1-2001314 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-04] | Nokia |
| R1-2001396 | TPs for CP extension from email discussion [100e-NR-unlic-NRU-ChAccess-03] | Nokia |
| R1-2001397 | Reply LS on consistent Uplink LBT failure detection mechanism | RAN1, Nokia |
| R1-2001482 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-02] | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000198 | Corrections on the RACH procedure in TS 38.213 | Huawei, HiSilicon |
| R1-2000256 | Remaining issues on initial access procedure for NR-U | vivo |
| R1-2000310 | Remaining issues on initial access procedure for NR-U | vivo |
| R1-2000395 | Maintenance on the initial access procedure for NR-U | ZTE, Sanechips |
| R1-2000419 | Remaining issues on initial access procedure | Spreadtrum Communications |
| R1-2000438 | Remaining issues on initial access procedure for NR-U operation | MediaTek Inc. |
| R1-2000471 | Discussion on the remaining issues of enhancements to initial access procedure | OPPO |
| R1-2000499 | On Enhancements to Initial Access Procedures | Nokia, Nokia Shanghai Bell |
| R1-2000611 | Initial access procedures for NR-U | Samsung |
| R1-2000664 | Remaining issues of initial access and mobility for NR-U | LG Electronics |
| R1-2000725 | Enhancements to initial access and mobility for NR-unlicensed | Intel Corporation |
| R1-2000771 | Remaining issues on initial access procedure for NR-U | ETRI |
| R1-2000827 | Enhancements to initial access procedures | Ericsson |
| R1-2000957 | TP for Initial access and mobility procedures for NR-U | Qualcomm Incorporated |
| R1-2001144 | Feature lead summary for NR-U initial access procedures | Charter Communications |
| R1-2001315 | Outcome of email thread [100e-NR-unlic-NRU-InitAccessProc-01] | Charter Communications |
| R1-2001316 | Outcome of email thread [100e-NR-unlic-NRU-InitAccessProc-02] | Charter Communications |
| R1-2001317 | Outcome of email thread [100e-NR-unlic-NRU-InitAccessProc-03] | Charter Communications |
| R1-2001357 | LS on SSB index and candidate SSB index for NR-U | RAN1, Samsung, Charter Communications |
| R1-2001375 | LS on NR-U enhancements to initial access procedures | RAN1, Charter Communications |
| TDoc | Title | Source |
|---|---|---|
| R1-2000199 | Corrections on HARQ-ACK feedback | Huawei, HiSilicon |
| R1-2000257 | Remaining issues on HARQ operation for NR-U | vivo |
| R1-2000311 | Remaining issues on HARQ operation for NR-U | vivo |
| R1-2000391 | Maintenance on the HARQ for NR-U | ZTE, Sanechips |
| R1-2000412 | Discussion on remaining issues on HARQ enhancement for NR-U | Beijing Xiaomi Mobile Software |
| R1-2000439 | Remaining issues on Enhancements to HARQ for NR-U operation | MediaTek Inc. |
| R1-2000472 | Discussion on the remaining issues of HARQ enhancements | OPPO |
| R1-2000503 | Remaining issues on NR-U HARQ scheduling and feedback | Nokia, Nokia Shanghai Bell |
| R1-2000592 | Text proposals for HARQ enhancement for NR-U | Lenovo, Motorola Mobility |
| R1-2000612 | HARQ enhancement for NR-U | Samsung |
| R1-2000665 | Remaining issues of HARQ procedure for NR-U | LG Electronics |
| R1-2000726 | Enhancements to HARQ for NR-unlicensed | Intel Corporation |
| R1-2000828 | HARQ enhancement | Ericsson |
| R1-2000849 | Remaining issues on HARQ enhancement | Apple |
| R1-2000874 | Remaining issues and corrections on HARQ enhancement for NR-U | Sharp |
| R1-2000958 | TP for Enhancements to Scheduling and HARQ Operation for NR-U | Qualcomm Incorporated |
| R1-2000997 | Correction on HARQ process | ASUSTeK |
| R1-2001000 | Remaining issues on NR-U HARQ procedures | Google Inc. |
| R1-2001043 | Feature lead summary#1 on NR-U HARQ and multi-PUSCH scheduling | Huawei |
| R1-2001191 | Feature lead summary#2 on NR-U HARQ and multi-PUSCH scheduling | Huawei |
| R1-2001268 | Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-02 (Type-3 HARQ-ACK codebook) | Huawei |
| R1-2001269 | Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-01 (enhanced Type-2 HARQ-ACK codebook) | Huawei |
| R1-2001270 | Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-03 (multi-PUSCH scheduling with DCI 0_1) | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000200 | Corrections on the configured grant procedures | Huawei, HiSilicon |
| R1-2000258 | Remaining issues on the enhancements to configured grant | vivo |
| R1-2000312 | Remaining issues on the enhancements to configured grant | vivo |
| R1-2000396 | Maintenance on the configured grant for NR-U | ZTE, Sanechips |
| R1-2000413 | Remaining Issues on Configured Grant Enhancement for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2000473 | Discussion on the remaining issues of configured grant enhancements | OPPO |
| R1-2000593 | Text proposals for configured grant enhancement for NR-U | Lenovo, Motorola Mobility |
| R1-2000613 | Configured grant enhancement for NR-U | Samsung |
| R1-2000666 | Remaining issues of configured grant for NR-U | LG Electronics |
| R1-2000693 | Clarification on HARQ-ACK feedback for PUSCH in DFI | Panasonic Corporation |
| R1-2000727 | Enhancements to configured grants for NR-unlicensed | Intel Corporation |
| R1-2000800 | Feature lead summary on NRU configured grant enhancement | vivo |
| R1-2000829 | Configured grant enhancement | Ericsson |
| R1-2000913 | Configured grant enhancement for NR-U | NTT DOCOMO, INC. |
| R1-2000959 | TP for Enhancements to configured grants for NR-U | Qualcomm Incorporated |
| R1-2001166 | Summary of 100e-Prep-email discussion on NRU configured grant enhancement | vivo |
| R1-2001252 | FL summary of [100e-NR-unlic-NRU-CG-01] email thread | vivo |
| R1-2001253 | FL summary of [100e-NR-unlic-NRU-CG-02] email thread | vivo |
| R1-2001254 | FL summary of [100e-NR-unlic-NRU-CG-03] email thread | vivo |
| R1-2001295 | Editorial corrections (NR-U) | vivo |
| R1-2001411 | Outcome of discussion on [100e-NR-unlic-NRU-CG-02] – TP for 38.214 | vivo |
| R1-2001412 | Outcome of discussion on [100e-NR-unlic-NRU-CG-03] – TP for 38.214 | vivo |
| R1-2001413 | Outcome of discussion on [100e-NR-unlic-NRU-CG-03] – TP for 38.213 | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2000201 | Corrections on the wideband operation procedures | Huawei, HiSilicon |
| R1-2000259 | Remaining issues on wideband operation in NR-U | vivo |
| R1-2000313 | Remaining issues on wideband operation in NR-U | vivo |
| R1-2000474 | Discussion on the remaining issues of wide-band operations | OPPO |
| R1-2000502 | Remaining issues on Wideband operation in NR-U | Nokia, Nokia Shanghai Bell |
| R1-2000543 | Remaining issues on Rel-16 NR-U wideband operations | PANASONIC R&D Center Germany |
| R1-2000614 | Wide-band operation for NR-U | Samsung |
| R1-2000667 | Remaining issues of wide-band operation for NR-U | LG Electronics |
| R1-2000668 | Summary on maintenance of wide-band operation for NR-U | LG Electronics |
| R1-2000728 | Wideband operation for NR-unlicensed | Intel Corporation |
| R1-2000772 | Remaining issues on wideband operation for NR-U | ETRI |
| R1-2000794 | Maintenance on the wideband operation for NR-U | ZTE, Sanechips |
| R1-2000830 | Wideband operation | Ericsson |
| R1-2000875 | Remaining issues on wide-band operation for NR-U | Sharp |
| R1-2000960 | TP for Wideband operation for NR-U operation | Qualcomm Incorporated |
| R1-2000999 | Remaining issues on Rel-16 NR-U wideband operations | Panasonic |
| R1-2001163 | Summary#2 on maintenance of wide-band operation for NR-U | LG Electronics |
| R1-2001358 | Summary of email discussion [100e-NR-unlic-NRU-WideBand-01] on CORESET and SS set configuration for NR-U wideband operation | LG Electronics |
| R1-2001359 | Summary of email discussion [100e-NR-unlic-NRU-WideBand-02] on CSI-RS for NR-U wide-band operation | LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2000475 | Discussion on the other remaining issues | OPPO |
| R1-2001107 | Other corrections for NR-U | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000961 | Clarifications on IAB resource management | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000796 | Maintenance of Rel-16 IAB RACH enhancement | Nokia, Nokia Shanghai Bell |
| R1-2001037 | Corrections on RACH occasions and periodicities for backhaul RACH resources | Huawei, HiSilicon |
| R1-2001135 | Summary of 7.2.3.2 - Extensions of RACH occasions and periodicities for backhaul RACH resources | Qualcomm |
| R1-2001183 | Summary#2 of 7.2.3.2 - Extensions of RACH occasions and periodicities for backhaul RACH resources | Qualcomm |
| R1-2001297 | Outcome of email discussions [100e-NR-IAB-RACH-01] | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000260 | Remaining aspects for resource multiplexing among backhaul and access links | vivo |
| R1-2000314 | Remaining aspects for resource multiplexing among backhaul and access links | vivo |
| R1-2000400 | Remaining issues in IAB resource multiplexing | ZTE, Sanechips |
| R1-2000669 | Text proposals on IAB resource multiplexing | LG Electronics |
| R1-2000745 | Remaining issues on mechanisms for resource multiplexing among backhaul and access links | CMCC |
| R1-2000797 | Maintenance of Rel-16 IAB Resource Multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2001038 | Corrections on resource multiplexing among backhaul and access links | Huawei, HiSilicon |
| R1-2001092 | Corrections on Mechanisms for resource multiplexing among backhaul and access links | Ericsson |
| R1-2001136 | Summary of 7.2.3.3 – Mechanisms for resource multiplexing among backhaul and access links | AT&T |
| R1-2001160 | Summary#2 of 7.2.3.3 – Mechanisms for resource multiplexing among backhaul and access links | AT&T |
| R1-2001425 | Final summary of 7.2.3.3 – Mechanisms for resource multiplexing among backhaul and access links | AT&T |
| TDoc | Title | Source |
|---|---|---|
| R1-2000798 | Maintenance of Rel-16 IAB Case-1 timing | Nokia, Nokia Shanghai Bell |
| R1-2000806 | FL summary on remaining issues in IAB case-1 timing | ZTE, Sanechips |
| R1-2001195 | FL summary#2 on remaining issues in IAB case-1 timing | ZTE, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R1-2000789 | On mandatory features for BS-like IAB-nodes | Ericsson |
| R1-2001105 | Corrections on other aspects of IAB | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000352 | TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.1.0 | Huawei |
| R1-2001218 | TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.1.0 | Huawei |
| R1-2001223 | TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.1.0 | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000181 | Remaining details of sidelink physical layer structure | Huawei, HiSilicon |
| R1-2000261 | Remaining issues on physical layer structure for NR sidelink | vivo |
| R1-2000315 | Remaining issues on physical layer structure for NR sidelink | vivo |
| R1-2000382 | Remaining details of Physical layer structure for sidelink | Nokia, Nokia Shanghai Bell |
| R1-2000398 | Remaining issues of NR sidelink physical layer structure | ZTE, Sanechips |
| R1-2000420 | Remaining issues of physical layer structure for sidelink | Spreadtrum Communications |
| R1-2000428 | Physical layer structure for sidelink | TCL Communication Ltd. |
| R1-2000445 | Discussion on sidelink physical layer structure | MediaTek Inc. |
| R1-2000489 | Draft text proposals on physical layer structure for NR-V2X | OPPO |
| R1-2000520 | Remaining issues on physical layer structure for NR sidelink | CATT |
| R1-2000545 | Remaining issues on physical layer structure for sidelink | Fujitsu |
| R1-2000564 | Remaining details on physical layer structure for the sidelink | Futurewei |
| R1-2000582 | Physical layer structure for NR sidelink | Sony |
| R1-2000615 | On Physical Layer Structures for NR Sidelink | Samsung |
| R1-2000729 | Remaining opens of sidelink physical structure for NR V2X design | Intel Corporation |
| R1-2000746 | Remaining issues on physical layer structure for sidelink | CMCC |
| R1-2000764 | Remaining issues on physical layer structure | NEC |
| R1-2000781 | Discussion on physical layer structure for NR sidelink | LG Electronics |
| R1-2000813 | Remaining details of V2X PHY layer structure | Mitsubishi Electric RCE |
| R1-2000834 | Remaining Issues on Physical Layer Structure for NR V2X | InterDigital, Inc. |
| R1-2000850 | Remaining details on NR V2X physical layer structure | Apple |
| R1-2000876 | Remaining issues on physical layer structure for NR sidelink | Sharp |
| R1-2000898 | Discussion on SCI content for 5G V2X | Xiaomi Communications |
| R1-2000903 | Remaining details of Physical layer structure design for sidelink | AT&T |
| R1-2000914 | Remaining issues on sidelink physical layer structure | NTT DOCOMO, INC. |
| R1-2000962 | Considerations on Physical Layer aspects of NR V2X | Qualcomm Incorporated |
| R1-2000992 | Remaining issue on physical layer structure for sidelink in NR V2X | Panasonic Corporation |
| R1-2001007 | Physical layer structure for NR sidelink | Ericsson |
| R1-2001070 | Remaining issues in NR Sidelink Structures | Lenovo, Motorola Mobility |
| R1-2001148 | Feature lead summary#1 for agenda item 7.2.4.1 Physical layer structure for sidelink | Samsung |
| R1-2001149 | Feature lead summary#2 for agenda item 7.2.4.1 Physical layer structure for sidelink | Samsung |
| R1-2001213 | Considerations on Physical Layer aspects of NR V2X | Qualcomm Incorporated |
| R1-2001400 | Text Proposal for PSSCH DMRS | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2000182 | Remaining details of sidelink resource allocation mode 1 | Huawei, HiSilicon |
| R1-2000262 | Remaining issues on mode 1 resource allocation mechanism | vivo |
| R1-2000316 | Remaining issues on mode 1 resource allocation mechanism | vivo |
| R1-2000383 | Remaining details of Resource allocation for sidelink - Mode 1 | Nokia, Nokia Shanghai Bell |
| R1-2000402 | Remaining issues in mode 1 resource allocation | ZTE, Sanechips |
| R1-2000421 | Remaining issues in NR sidelink mode 1 resource allocation | Spreadtrum Communications |
| R1-2000429 | Resource allocation for NR sidelink Mode 1 | TCL Communication Ltd. |
| R1-2000446 | NR Sidelink Mode-1 resource allocation | MediaTek Inc. |
| R1-2000490 | Remaining issues of mode 1 resource allocation for NR-V2X | OPPO |
| R1-2000521 | Remaining issues on Mode 1 resource allocation in NR V2X | CATT |
| R1-2000546 | Remaining issues on mode 1 resource allocation for NR V2X | Fujitsu |
| R1-2000565 | Remaining details on mode-1 resource allocation | Futurewei |
| R1-2000616 | On Mode 1 for NR Sidelink | Samsung |
| R1-2000699 | Mode-1 resource allocation for NR V2X | ITL |
| R1-2000730 | Remaining Issues in Mode-1 Resource Allocation | Intel Corporation |
| R1-2000747 | Remaining issues on mode 1 resource allocation mechanism | CMCC |
| R1-2000765 | Remaining issues on resource allocation Mode 1 | NEC |
| R1-2000777 | Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 | Ericsson |
| R1-2000779 | Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 | Ericsson |
| R1-2000782 | Discussion on resource allocation for Mode 1 | LG Electronics |
| R1-2000835 | Remaining Issues on NR Sidelink Mode 1 Resource Allocation | InterDigital, Inc. |
| R1-2000851 | Remaining details on mode 1 resource allocation | Apple |
| R1-2000877 | Remaining issues on resource allocation mode 1 for NR sidelink | Sharp |
| R1-2000899 | On Sidelink HARQ report of V2x communications | Xiaomi Communications |
| R1-2000904 | Remaining details of resource allocation mode-1 for NR sidelink | AT&T |
| R1-2000915 | Remaining issues on resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2001008 | Resource Allocation Mode 1 for NR SL | Ericsson |
| R1-2001072 | Remaining issues in NR sidelink Mode 1 | Lenovo, Motorola Mobility |
| R1-2001093 | On Resource Allocation Mode 1 for NR V2X | Convida Wireless |
| R1-2001118 | On Resource Allocation Mode 1 for NR V2X | Convida Wireless |
| R1-2001153 | Discussion on resource allocation for Mode 1 | LG Electronics |
| R1-2001285 | Feature lead summary#3 on Resource allocation for NR sidelink Mode 1 | Ericsson |
| R1-2001367 | Feature lead summary#4 on Resource allocation for NR sidelink Mode 1 | Ericsson |
| R1-2001410 | Text proposal for TS 38.213 endorsed in [100e-NR-5G_V2X_NRSL-RA_Mode1-02] | Ericsson |
| R1-2001414 | Text proposal for TS 38.213 endorsed in [100e-NR-5G_V2X_NRSL-RA_Mode1-03] | Ericsson |
| R1-2001415 | Text proposal for TS 38.214 endorsed in [100e-NR-5G_V2X_NRSL-RA_Mode1-01] | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000183 | Remaining details of sidelink resource allocation mode 2 | Huawei, HiSilicon |
| R1-2000263 | Remaining issues on mode 2 resource allocation mechanism | vivo |
| R1-2000317 | Remaining issues on mode 2 resource allocation mechanism | vivo |
| R1-2000384 | Remaining details of Resource allocation for sidelink - Mode 2 | Nokia, Nokia Shanghai Bell |
| R1-2000403 | Remaining issues in mode 2 resource allocation | ZTE, Sanechips |
| R1-2000422 | Remaining issues in NR sidelink mode 2 resource allocation | Spreadtrum Communications |
| R1-2000430 | Resource allocation for NR sidelink Mode 2 | TCL Communication Ltd. |
| R1-2000447 | On sidelink mode-2 resource allocation | MediaTek Inc. |
| R1-2000493 | Discussion on remaining open issue for mode 2 | OPPO |
| R1-2000522 | Remaining issues on Mode 2 resource allocation in NR V2X | CATT |
| R1-2000542 | Remaining Issues On Sidelink Mode 2 Resource Allocation | Panasonic Corporation |
| R1-2000547 | Remaining details on mode 2 resource allocation for NR V2X | Fujitsu |
| R1-2000563 | Remaining Issues in Resource Allocation for Mode 2 NR V2X | Fraunhofer HHI, Fraunhofer IIS |
| R1-2000566 | Remaining details on mode-2 resource allocation | Futurewei |
| R1-2000583 | Resource allocation mechanism for NR sidelink Mode 2 | Sony |
| R1-2000617 | On Mode 2 for NR Sidelink | Samsung |
| R1-2000695 | Remaining Issues on NR Sidelink Mode 2 Resource Allocation | ITRI |
| R1-2000731 | Remaining opens of resource allocation mode-2 for NR V2X design | Intel Corporation |
| R1-2000783 | Discussion on resource allocation for Mode 2 | LG Electronics |
| R1-2000836 | Remaining Issues on NR Sidelink Mode 2 Resource Allocation | InterDigital, Inc. |
| R1-2000852 | Remaining details on mode 2 resource allocation | Apple |
| R1-2000878 | Remaining issues on resource allocation mode 2 for NR sidelink | Sharp |
| R1-2000900 | On resource reservation in Mode 2 resource allocation | Xiaomi Communications |
| R1-2000905 | Remaining details of resource allocation mode-2 for NR sidelink | AT&T |
| R1-2000916 | Remaining issues on resource allocation mechanism mode 2 | NTT DOCOMO, INC. |
| R1-2000963 | Sidelink Resource Allocation Mechanism for NR V2X | Qualcomm Incorporated |
| R1-2000996 | Remaining issue for Mode 2 resource allocation in NR V2X | ASUSTeK |
| R1-2001006 | Remain details on mode-2 resource allocation for NR V2X | ITL |
| R1-2001009 | Resource allocation Mode 2 for NR SL | Ericsson |
| R1-2001090 | Remaining issues for Mode 2 resource (re-)selection of periodic transmission | ROBERT BOSCH GmbH |
| R1-2001138 | FL summary of critical issues for 7.2.4.2.2 – V2X Mode 2 | Intel |
| R1-2001170 | FL summary#2 of critical issues for 7.2.4.2.2 – V2X Mode 2 | Intel |
| R1-2001344 | Outcome of email thread [100e-NR-5G_V2X_NRSL-RA_Mode2-01] | Intel Corporation |
| R1-2001345 | Outcome of email thread [100e-NR-5G_V2X_NRSL-RA_Mode2-02] | Intel Corporation |
| R1-2001346 | Outcome of email thread [100e-NR-5G_V2X_NRSL-RA_Mode2-03] | Intel Corporation |
| TDoc | Title | Source |
|---|---|---|
| R1-2000184 | On remaining details of pre-emption mechanism | Huawei, HiSilicon |
| R1-2000264 | Remaining aspects for resource allocation | vivo |
| R1-2000318 | Remaining aspects for resource allocation | vivo |
| R1-2000494 | On other aspects of mode 2 resource allocation | OPPO |
| R1-2000618 | Open Issues on Mode 1 and Mode 2 for NR Sidelink | Samsung |
| R1-2001010 | Other outstanding resource allocation issues | Ericsson |
| R1-2001018 | Discussion on simultaneous configuration of Mode 1 and Mode 2 for a UE | ASUSTeK |
| TDoc | Title | Source |
|---|---|---|
| R1-2000185 | Remaining details of sidelink synchronization mechanisms | Huawei, HiSilicon |
| R1-2000265 | Remaining issues on sidelink synchronization mechanism | vivo |
| R1-2000319 | Remaining issues on sidelink synchronization mechanism | vivo |
| R1-2000385 | Remaining details of Sidelink synchronization mechanism | Nokia, Nokia Shanghai Bell |
| R1-2000399 | Remaining issues of Synchronization | ZTE, Sanechips |
| R1-2000423 | Remaining issues in synchronization mechanism for NR V2X | Spreadtrum Communications |
| R1-2000448 | Discussion on sidelink based synchronization mechanism | MediaTek Inc. |
| R1-2000491 | Remaining issues of synchronization for NR-V2X | OPPO |
| R1-2000523 | Remaining issues on sidelink synchronization mechanism in NR V2X | CATT |
| R1-2000548 | Corrections on sidelink synchronization procedure | Fujitsu |
| R1-2000567 | Remaining details on synchronization for sidelink | Futurewei |
| R1-2000619 | On Synchronization Mechanisms for NR Sidelink | Samsung |
| R1-2000696 | Remaining Issues on Sidelink Synchronization for NR V2X Communication | ITRI |
| R1-2000732 | Remaining opens of sidelink synchronization for NR V2X design | Intel Corporation |
| R1-2000748 | Remaining issues on sidelink synchronization mechanisms | CMCC |
| R1-2000784 | Discussion on NR sidelink synchronization mechanism | LG Electronics |
| R1-2000832 | Feature lead summary on AI 7.2.4.3 Sidelink synchronization mechanism | CATT |
| R1-2000833 | Feature lead summary#2 on AI 7.2.4.3 Sidelink synchronization mechanism | CATT |
| R1-2000879 | Remaining issues on synchronization mechanism for NR sidelink | Sharp |
| R1-2000917 | Remaining issues on sidelink synchronization mechanism | NTT DOCOMO, INC. |
| R1-2000964 | Synchronization mechanism enhancment for cluster merge | Qualcomm Incorporated |
| R1-2001011 | Synchronization mechanism for NR SL | Ericsson |
| R1-2001363 | Feature lead summary#3 on AI 7.2.4.3 Sidelink synchronization mechanism – Email discussions outcomes | CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2000186 | Remaining details of in-device coexistence between LTE and NR sidelinks | Huawei, HiSilicon |
| R1-2000266 | Remaining issues on In-device coexistence between NR and LTE sidelinks | vivo |
| R1-2000320 | Remaining issues on In-device coexistence between NR and LTE sidelinks | vivo |
| R1-2000386 | Remaining details of In-device coexistence between LTE and NR sidelinks | Nokia, Nokia Shanghai Bell |
| R1-2000449 | In-device coexistence between LTE and NR sidelinks | MediaTek Inc. |
| R1-2000495 | Remaining open issues on in-device coexistence | OPPO |
| R1-2000569 | Remaining details on in-device coexistence between LTE and NR sidelinks | Futurewei |
| R1-2000620 | On In-device Coexistence between LTE and NR Sidelink | Samsung |
| R1-2000965 | Feature Lead summary of In-device Coexistence Aspects in NR-V2X (AI 7.2.4.4) | Qualcomm Incorporated |
| R1-2001089 | In-device coexistence between LTE and NR sidelinks | Ericsson |
| R1-2001212 | Feature Lead summary#2 of In-device Coexistence Aspects in NR-V2X (AI 7.2.4.4) | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000187 | Remaining details of physical layer procedures for sidelink | Huawei, HiSilicon |
| R1-2000267 | Remaining issues on physical layer procedure for NR sidelink | vivo |
| R1-2000321 | Remaining issues on physical layer procedure for NR sidelink | vivo |
| R1-2000387 | Remaining details of Physical layer procedures for sidelink | Nokia, Nokia Shanghai Bell |
| R1-2000401 | Remaining issues on PHY procedures for Rel-16 sidelink | ZTE, Sanechips |
| R1-2000424 | Remaining issues in physical layer procedures for sidelink | Spreadtrum Communications |
| R1-2000431 | Physical layer procedures for sidelink | TCL Communication Ltd. |
| R1-2000492 | Remaining issues of physical layer procedure for NR-V2X | OPPO |
| R1-2000524 | Remaining issues on physical layerprocedures for NR V2X | CATT |
| R1-2000549 | Remaining issues on physical layer procedures | Fujitsu |
| R1-2000562 | Remaining Issues in Physical Layer Procedures for NR V2X | Fraunhofer HHI, Fraunhofer IIS, Continental Automotive GmbH |
| R1-2000568 | Remaining details on physical procedures for sidelink | Futurewei |
| R1-2000584 | Physical layer procedures for NR sidelink | Sony |
| R1-2000621 | On Physical Layer Procedures for NR Sidelink | Samsung |
| R1-2000697 | Remaining Issues on Physical Layer Procedures in NR Sidelink | ITRI |
| R1-2000733 | Remaining Issues and Corrections in Sidelink Procedures | Intel Corporation |
| R1-2000749 | Remaining issues on physical layer procedures for sidelink | CMCC |
| R1-2000766 | Remaining issues on physical layer procedure | NEC |
| R1-2000785 | Discussion on physical layer procedure for NR sidelink | LG Electronics |
| R1-2000837 | Remaining Issues on Physical Layer Procedures for NR V2X | InterDigital, Inc. |
| R1-2000839 | Summary of critical issues for AI 7.2.4.5 Physical layer procedures for sidelink | LG Electronics Inc. |
| R1-2000853 | Remaining details on physical layer procedures for NR V2X sidelink | Apple |
| R1-2000880 | Remaining issues on physical layer procedures for NR sidelink | Sharp |
| R1-2000901 | On procedures for 5G V2x communications | Xiaomi Communications |
| R1-2000906 | Remaining details of physical layer procedures for sidelink | AT&T |
| R1-2000918 | Remaining issues on sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2000966 | Physical layer procedures for sidelink | Qualcomm Incorporated |
| R1-2000993 | Remaining issue on physical layer procedures for sidelink in NR V2X | Panasonic Corporation |
| R1-2001012 | Physical layer procedures for NR sidelink | Ericsson |
| R1-2001017 | Remaining issues on sidelink physical layer procedure on NR V2X | ASUSTeK |
| R1-2001045 | On PSFCH of NR Sidelink | CAICT |
| R1-2001071 | Remaining issues in NR Sidelink Physical Layer Procedures | Lenovo, Motorola Mobility |
| R1-2001134 | Summary of critical issues for AI 7.2.4.5 Physical layer procedures for sidelink | LG Electronics Inc. |
| R1-2001140 | Feature lead summary for AI 7.2.4.5 Physical layer procedures for sidelink | LG Electronics |
| R1-2001338 | Feature lead summary#2 for AI 7.2.4.5 Physical layer procedures for sidelink | LG Electronics |
| R1-2001426 | LS on sidelink HARQ | RAN1, LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2000188 | Remaining details of QoS management for NR sidelink | Huawei, HiSilicon |
| R1-2000268 | Remaining issues on QoS management for sidelink | vivo |
| R1-2000322 | Remaining issues on QoS management for sidelink | vivo |
| R1-2000388 | Remaining details of QoS management for sidelink | Nokia, Nokia Shanghai Bell |
| R1-2000404 | Remaining issues on NR sidelink congestion control | ZTE, Sanechips |
| R1-2000496 | Remaining open issues on channel occupancy ratio | OPPO |
| R1-2000525 | Remaining issues on congestion control in NR V2X | CATT |
| R1-2000570 | Remaining details of QoS for sidelink | Futurewei |
| R1-2000622 | On QoS Management for NR Sidelink | Samsung |
| R1-2000694 | Aspects of Sidelink Channel Occupancy Ratio Evaluation | Continental Automotive GmbH, Fraunhofer HHI, Fraunhofer IIS |
| R1-2000698 | Remaining issues on congestion control for sidelink QoS management | ITRI |
| R1-2000734 | Remaining details of QoS and congestion control for NR V2X design | Intel Corporation |
| R1-2000786 | Discussion on QoS management for NR sidelink | LG Electronics |
| R1-2000838 | Remaining Issues on Congestion Control and QoS Management for NR-V2X | InterDigital, Inc. |
| R1-2001013 | QoS management for NR sidelink | Ericsson |
| R1-2001091 | Feature Lead Summary for AI 7.2.4.6 QoS management | Nokia, Nokia Shanghai Bell |
| R1-2001181 | Summary of email discussion 100e-Prep-NR-5G_V2X_NRSL-QoS | Nokia |
| R1-2001294 | Outcome of email discussions [100e-NR-5G_V2X_NRSL-QoS] | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000189 | Remaining details of NR Uu control for LTE sidelink | Huawei, HiSilicon |
| R1-2000269 | Remaining issues on support of NR Uu controlling LTE sidelink | vivo |
| R1-2000323 | Remaining issues on support of NR Uu controlling LTE sidelink | vivo |
| R1-2000389 | Remaining details of NR Uu controlling LTE sidelink | Nokia, Nokia Shanghai Bell |
| R1-2000450 | Support of NR-Uu controlling LTE sidelink | MediaTek Inc. |
| R1-2000497 | On DCI signalling to control LTE sidelink | OPPO |
| R1-2000526 | Remaining issues on NR Uu controlling LTE sidelink | CATT |
| R1-2000571 | Remaining details on the support of NR Uu controlling LTE sidelink | Futurewei |
| R1-2000623 | On NR Uu Controlling LTE Sidelink | Samsung |
| R1-2000787 | Discussion on NR Uu controlling LTE sidelink | LG Electronics |
| R1-2000822 | Summary of critical issues for NR Uu scheduling LTE sidelink | Futurewei |
| R1-2000854 | On size alignment of DCI format 3_1 | Apple |
| R1-2001014 | NR UU controlling LTE sidelink transmissions | Ericsson |
| R1-2001159 | Update of summary of critical issues for NR Uu scheduling LTE sidelink | Futurewei |
| R1-2001245 | Update#2 of summary of critical issues for NR Uu scheduling LTE sidelink | Futurewei |
| R1-2001394 | TP for TS38.213 to capture the outcome of [100e-NR-5G_V2X_NRSL-NRUuSchedulingLTESL-01] | Futurewei |
| R1-2001395 | TP for TS38.212 to capture the outcome of [100e-NR-5G_V2X_NRSL-NRUuSchedulingLTESL-02] | Futurewei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000270 | Remaining aspects for NR V2X | vivo |
| R1-2000324 | Remaining aspects for NR V2X | vivo |
| R1-2000498 | Discussion on UE feature list for Release16 5G-V2X | OPPO |
| R1-2000572 | Other remaining issues on sidelink | Futurewei |
| R1-2000624 | Details on frequency resource indication of PSSCH | Samsung |
| R1-2000967 | Syncronisation details for NR-V2X | Qualcomm Incorporated |
| R1-2001015 | Remaining details on resource pool determination | Ericsson |
| R1-2001095 | Remaining details of sidelink RRC Parameter List | Huawei, HiSilicon |
| R1-2001198 | Syncronisation details for NR-V2X | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000230 | Remaining Issue of PDCCH Enhancements for NR URLLC | Ericsson |
| R1-2000271 | PDCCH enhancements for URLLC | vivo |
| R1-2000325 | PDCCH enhancements for URLLC | vivo |
| R1-2000355 | Remaining issues on PDCCH enhancements for NR URLLC | ZTE |
| R1-2000425 | Discussion on remain issues of PDCCH enhancements for URLLC | Spreadtrum Communications |
| R1-2000432 | Maintenance of Rel-16 URLLC PDCCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2000451 | Remaining issues on PDCCH enhancements | MediaTek Inc. |
| R1-2000479 | PDCCH enhancements for URLLC | OPPO |
| R1-2000527 | Remaining issues on PDCCH enhancements | CATT |
| R1-2000587 | PDCCH enhancements for NR URLLC | Panasonic Corporation |
| R1-2000625 | Remaining issues for PDCCH enhancements | Samsung |
| R1-2000670 | Remaining issues of PDCCH enhancements for NR URLLC | LG Electronics |
| R1-2000735 | Remaining aspects on Rel-16 PDCCH enhancements for URLLC | Intel Corporation |
| R1-2000793 | PDCCH enhancement for URLLC | China Unicom |
| R1-2000855 | Remaining Details on PDCCH Enhancements | Apple |
| R1-2000881 | Remaining issues on PDCCH enhancements for NR URLLC | Sharp |
| R1-2000896 | Discussion on remaining issues of PDCCH enhancements for URLLC | Spreadtrum Communications |
| R1-2000919 | Remaining issues for PDCCH enhancements for Rel.16 URLLC | NTT DOCOMO, INC. |
| R1-2000935 | Remaining issues on PDCCH enhancement for NR URLLC | WILUS Inc. |
| R1-2000968 | Remaining issues on PDCCH Enhancements for URLLC | Qualcomm Incorporated |
| R1-2000995 | Remaining issue for TCI field | ASUSTeK |
| R1-2001023 | Corrections on PDCCH enhancement for URLLC | Huawei, HiSilicon |
| R1-2001044 | Feature lead summary#1 on PDCCH enhancements | Huawei |
| R1-2001164 | Feature lead summary#2 on PDCCH enhancements | Huawei |
| R1-2001404 | Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-01] on remaining issues on DCI format | Huawei |
| R1-2001405 | Text proposal on Antenna port(s) for TS 38.212 Section 7.3.1.1.3 & 7.3.1.2.3 | Huawei |
| R1-2001406 | Text proposal on resource allocation type 1 for TS 38.212 Section 7.3.1.1.3 & 7.3.1.2.3 | Huawei |
| R1-2001407 | Text proposal on resource allocation type 1 for TS 38.214 Section 5.1.2.2.2 & 6.1.2.2.2 | Huawei |
| R1-2001408 | Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-02] on remaining issues on PDCCH candidate overbooking and dropping | Huawei |
| R1-2001409 | Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-03] on remaining issue on enhanced PDCCH monitoring capability | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2000231 | Remaining Issue of UCI Enhancements for NR URLLC | Ericsson |
| R1-2000272 | UCI enhancements for URLLC | vivo |
| R1-2000326 | UCI enhancements for URLLC | vivo |
| R1-2000356 | Remaining issues on UL control enhancements for NR URLLC | ZTE |
| R1-2000405 | Maintenance of Rel-16 URLLC UCI enhancements | Nokia, Nokia Shanghai Bell |
| R1-2000409 | Discussion on remaining issues on UCI enhancement for URLLC | Beijing Xiaomi Mobile Software |
| R1-2000426 | Discussion on remain issues of UCI enhancements for URLLC | Spreadtrum Communications |
| R1-2000452 | Remaining issues on UCI enhancements | MediaTek Inc. |
| R1-2000480 | UCI enhancements for URLLC | OPPO |
| R1-2000528 | Remaining issues on UCI enhancements | CATT |
| R1-2000550 | Remaining issues on UCI enhancements for URLLC | Fujitsu |
| R1-2000588 | Remaining issue on UCI enhancement | Panasonic Corporation |
| R1-2000626 | Remaining issues for UCI enhancements | Samsung |
| R1-2000671 | Remaining issues of UCI enhancements for NR URLLC | LG Electronics |
| R1-2000736 | Remaining details on UCI enhancements for URLLC | Intel Corporation |
| R1-2000750 | Remaining issues on UCI enhancements for URLLC | CMCC |
| R1-2000775 | Remaining issues on UCI enhancements for NR URLLC | Asia Pacific Telecom co. Ltd |
| R1-2000816 | UCI enhancements for URLLC | InterDigital, Inc. |
| R1-2000897 | Discussion on remaining issues of UCI enhancements for URLLC | Spreadtrum Communications |
| R1-2000920 | Discussion on the priority index for the HARQ-ACK codebook | NTT DOCOMO, INC. |
| R1-2000936 | Remaining issues on UCI enhancement for NR URLLC | WILUS Inc. |
| R1-2000969 | Remaining issues on UCI Enhancements for URLLC | Qualcomm Incorporated |
| R1-2001016 | Summary#1 on UCI enhancements for R16 URLLC | OPPO |
| R1-2001027 | Corrections on UCI enhancement | Huawei, HiSilicon |
| R1-2001226 | Summary of email thread [100e-NR-L1enh_URLLC-UCI_Enh-01] | OPPO |
| R1-2001227 | Summary of email thread [100e-NR-L1enh_URLLC-UCI_Enh-02] | OPPO |
| R1-2001228 | Summary of email thread [100e-NR-L1enh_URLLC-UCI_Enh-03] | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2000232 | Remaining Issue of PUSCH Enhancements for NR URLLC | Ericsson |
| R1-2000273 | PUSCH enhancements for URLLC | vivo |
| R1-2000327 | PUSCH enhancements for URLLC | vivo |
| R1-2000357 | Remaining issues on PUSCH enhancements for NR URLLC | ZTE |
| R1-2000406 | Maintenance of PUSCH enhancements for Rel-16 NR URLLC | Nokia, Nokia Shanghai Bell |
| R1-2000408 | Summary #1 for maintenance of PUSCH enhancements in Rel-16 NR URLLC | Nokia, Nokia Shanghai Bell |
| R1-2000481 | PUSCH enhancements for URLLC | OPPO |
| R1-2000529 | Remaining issues on PUSCH enhancements | CATT |
| R1-2000585 | On DMRS of segmented PUSCH | Sony |
| R1-2000589 | Remaining issues on URLLC PUSCH enhancement | Panasonic Corporation |
| R1-2000627 | Remaining issues for PUSCH enhancements | Samsung |
| R1-2000672 | Remaining issues of PUSCH enhancements for NR URLLC | LG Electronics |
| R1-2000751 | Remaining issues on PUSCH enhancements for URLLC | CMCC |
| R1-2000807 | PUSCH enhancements for URLLC | China Unicom |
| R1-2000856 | Remaining details of PUSCH enhancements | Apple |
| R1-2000902 | Frequency hopping in PUSCH repetition | Motorola Mobility, Lenovo |
| R1-2000921 | Remaining issues for PUSCH enhancements for Rel.16 URLLC | NTT DOCOMO, INC. |
| R1-2000937 | Remaining issues on PUSCH repetition type B for NR URLLC | WILUS Inc. |
| R1-2000970 | Remaining issues on PUSCH enhancements for URLLC | Qualcomm Incorporated |
| R1-2001028 | Corrections on PUSCH enhancement | Huawei, HiSilicon |
| R1-2001046 | Remaining Issues of PUSCH Enhancements for NR URLLC | CAICT |
| R1-2001085 | Remaining details on PUSCH enhancements for URLLC | Intel Corporation |
| R1-2001162 | Summary #2 for maintenance of PUSCH enhancements in Rel-16 NR URLLC | Nokia, Nokia Shanghai Bell |
| R1-2001401 | Summary of email discussion [100e-NR-L1enh_URLLC-PUSCH_Enh-01] | Nokia |
| R1-2001402 | Summary of email discussion [100e-NR-L1enh_URLLC-PUSCH_Enh-02] | Nokia |
| R1-2001403 | Summary of email discussion [100e-NR-L1enh_URLLC-PUSCH_Enh-03] | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000233 | Remaining Issue of Scheduling/HARQ for NR URLLC | Ericsson |
| R1-2000274 | Enhancement for Scheduling/HARQ | vivo |
| R1-2000328 | Enhancement for Scheduling/HARQ | vivo |
| R1-2000358 | Remaining issues on scheduling/HARQ enhancements for NR URLLC | ZTE |
| R1-2000482 | Discussion on Out-of-Order HARQ | OPPO |
| R1-2000530 | Remaining issues on out-of-order scheduling/HARQ | CATT |
| R1-2000590 | Remaining issues on out-of-order HARQ and PUCCH overlapping | Panasonic Corporation |
| R1-2000628 | Remaining issues for scheduliung/HARQ enhancements | Samsung |
| R1-2000673 | Remaining issues of Enhancements to scheduling/HARQ for NR URLLC | LG Electronics |
| R1-2000737 | Remaining details on scheduling and HARQ enhancements for URLLC | Intel Corporation |
| R1-2000752 | Remaining issues on scheduling and HARQ | CMCC |
| R1-2000971 | Summary of the remaining issues on HARQ and scheduling enhancements for URLLC | Qualcomm Incorporated |
| R1-2001031 | Corrections on operation of out-of-order | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000234 | Remaining Issue of Inter-UE Prioritization and Multiplexing of UL Transmissions | Ericsson |
| R1-2000275 | UL inter UE Tx prioritization for URLLC | vivo |
| R1-2000329 | UL inter UE Tx prioritization for URLLC | vivo |
| R1-2000359 | Remaining issues on UL inter-UE multiplexing between eMBB and URLLC | ZTE |
| R1-2000433 | Maintenance of Rel-16 URLLC Enhanced inter UE Tx prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2000453 | Remaining issues on enhanced inter UE Tx prioritization/multiplexing | MediaTek Inc. |
| R1-2000483 | Inter UE Tx prioritization and multiplexing | OPPO |
| R1-2000531 | Remaining issues on inter-UE UL multiplexing | CATT |
| R1-2000586 | On the granularity of overlapping Reference Region for UL CI | Sony |
| R1-2000629 | Remaining issues for inter-UE multiplexing | Samsung |
| R1-2000674 | Remaining issues of UL inter UE Tx prioritization | LG Electronics |
| R1-2000738 | Remaining details on enhanced inter-UE multiplexing | Intel Corporation |
| R1-2000753 | Remaining issues on inter UE Tx prioritization/multiplexing | CMCC |
| R1-2000801 | Summary of UL inter UE Tx prioritization for URLLC | vivo |
| R1-2000857 | Remaining Details on Enhanced Inter-UE Prioritization/Multiplexing | Apple |
| R1-2000938 | Remaining issues on UL cancellation indication for NR URLLC | WILUS Inc. |
| R1-2000972 | Remaining issues on uplink Inter-UE Tx Multiplexing and Prioritization | Qualcomm Incorporated |
| R1-2001025 | Corrections on UL inter-UE multiplexing | Huawei, HiSilicon |
| R1-2001094 | Inter-UE prioritization/multiplexing | InterDigital, Inc. |
| R1-2001180 | Summary#2 of UL inter UE Tx prioritization for URLLC | vivo |
| R1-2001290 | Summary of email discussion [100e-NR-L1enh_URLLC-Inter_UE-01] | vivo |
| R1-2001291 | Summary of email discussion [100e-NR-L1enh_URLLC-Inter_UE-02] | vivo |
| R1-2001292 | Summary of email discussion [100e-NR-L1enh_URLLC-Inter_UE-03] | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2000235 | Remaining Issue of Enhancements to UL Configured Grant Transmission for NR URLLC | Ericsson |
| R1-2000276 | Enhanced UL configured grant transmissions for URLLC | vivo |
| R1-2000330 | Enhanced UL configured grant transmissions for URLLC | vivo |
| R1-2000360 | Remaining issues on enhancements for UL configured grant transmission | ZTE |
| R1-2000434 | Maintenance of Rel-16 URLLC Configured Grant enhancements | Nokia, Nokia Shanghai Bell |
| R1-2000484 | Configured grant enhancements for URLLC | OPPO |
| R1-2000532 | Remaining issues on enhanced UL configured grant transmission | CATT |
| R1-2000630 | Remaining issues for configued grant | Samsung |
| R1-2000675 | Remaining issues of Enhanced UL configured grant transmission for NR URLLC | LG Electronics |
| R1-2000922 | Remaining issues for enhanced Configured grant for Rel.16 URLLC | NTT DOCOMO, INC. |
| R1-2000923 | Summary on remaining issues for Rel.16 enhanced configured grant | NTT DOCOMO, INC. |
| R1-2001024 | Corrections on configured grant transmission | Huawei, HiSilicon |
| R1-2001171 | Summary#2 on remaining issues for Rel.16 enhanced configured grant | NTT DOCOMO, INC. |
| R1-2001422 | Outcome of email discussion on [100e-NR-L1enh_URLLC-eCG-01] | NTT DOCOMO |
| R1-2001423 | Outcome of email discussion on [100e-NR-L1enh_URLLC-eCG-02] | NTT DOCOMO |
| R1-2001424 | Outcome of email discussion on [100e-NR-L1enh_URLLC-eCG-03] | NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2000236 | Remaining Issue of DL SPS Enhancements for NR URLLC | Ericsson |
| R1-2000277 | Other issues for URLLC | vivo |
| R1-2000331 | Other issues for URLLC | vivo |
| R1-2000407 | Maintenance of Rel-16 URLLC/IIoT SPS enhancements | Nokia, Nokia Shanghai Bell |
| R1-2000485 | DL SPS enhancement | OPPO |
| R1-2000533 | Remaining issues on DL SPS enhancement | CATT |
| R1-2000631 | Remaining issues for DL SPS and PHR | Samsung |
| R1-2000676 | Remaining issues of other aspects for URLLC/IIOT | LG Electronics |
| R1-2000677 | Summary on maintenance of other aspects for URLLC/IIOT | LG Electronics |
| R1-2000776 | Remaining issues on DL SPS enhancements | Asia Pacific Telecom co. Ltd |
| R1-2000924 | PUCCH resource determination for HARQ-ACK for SPS PDSCH | NTT DOCOMO, INC. |
| R1-2000943 | Remaining RAN1 issues on IIoT related enhancements | ZTE |
| R1-2001065 | Remaining Issues on DL SPS Enhancements for NR URLLC | CAICT |
| R1-2001078 | Remaining details on enhanced UL CG PUSCH and DL SPS for URLLC | Intel Corporation |
| R1-2001106 | Corrections on other aspects for URLLC/IIOT enhancements | Huawei, HiSilicon |
| R1-2001184 | Summary#2 on maintenance of other aspects for URLLC/IIOT | LG Electronics |
| R1-2001225 | Summary#3 on maintenance of other aspects for URLLC/IIOT | LG Electronics |
| R1-2001382 | Outcome of email thread [100e-NR-L1enh_URLLC-SPS_enh-01] | LG Electronics |
| R1-2001383 | Outcome of email thread [100e-NR-L1enh_URLLC-SPS_enh-02] | LG Electronics |
| R1-2001384 | Outcome of email thread [100e-NR-L1enh_URLLC-SPS_enh-03] | LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2000205 | Remaining issues on MU-CSI in R16 | Huawei, HiSilicon |
| R1-2000238 | Maintenance of CSI enhancement for MU-MIMO support | ZTE |
| R1-2000278 | Discussion on remaining issues on MU-CSI and text proposals | vivo |
| R1-2000332 | Discussion on remaining issues on MU-CSI | vivo |
| R1-2000456 | Text proposals for CSI enhancements for MU-MIMO support | OPPO |
| R1-2000534 | Remaining issues on CSI enhancement for MU-MIMO | CATT |
| R1-2000632 | Correction on CSI part 2 payload in 38.212 | Samsung |
| R1-2000678 | Text proposals on CSI Enhancement for MU-MIMO Support | LG Electronics |
| R1-2000858 | Remaining issues for Rel-16 Type II CSI enhancement | Apple |
| R1-2000939 | Remaining issues for MU-CSI | Ericsson |
| R1-2000973 | Remaining issues on CSI enhancement for MU-MIMO support | Qualcomm Incorporated |
| R1-2000987 | Maintenance on Rel-16 CSI enhancements | Nokia, Nokia Shanghai Bell |
| R1-2001119 | Text proposals for Rel. 16 Type-II CSI enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2001129 | Feature lead summary for MU-MIMO CSI | Samsung |
| R1-2001157 | Feature lead summary#2 for MU-MIMO CSI | Samsung |
| R1-2001215 | Feature lead summary for [100e-NR-eMIMO-MUCSI-01] | Samsung |
| R1-2001216 | Feature lead summary for [100e-NR-eMIMO-MUCSI-02] | Samsung |
| R1-2001217 | Feature lead summary for [100e-NR-eMIMO-MUCSI-03] | Samsung |
| R1-2001362 | Feature lead summary#2 for [100e-NR-eMIMO-MUCSI-03] | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2000204 | Remaining issues on multi-TRP in R16 | Huawei, HiSilicon |
| R1-2000239 | Maintenance of enhancements on multi-TRP transmission | ZTE |
| R1-2000279 | Discussion on remaining issues on M-TRP and text proposals | vivo |
| R1-2000333 | Discussion on remaining issues on M-TRP and text proposals | vivo |
| R1-2000457 | Text proposals for enhancements on multi-TRP and panel Transmission | OPPO |
| R1-2000535 | Remaining issues on Multi-TRP/panel transmission for Rel-16 | CATT |
| R1-2000595 | Remaining issues on multi-TRP/panel transmission | Lenovo, Motorola Mobility |
| R1-2000633 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2000679 | Text proposals on enhancements on multi-TRP/panel transmission | LG Electronics |
| R1-2000739 | Correction to multi TRP operation | Intel Corporation |
| R1-2000754 | Maintenance for multi-TRP/panel transmission | CMCC |
| R1-2000773 | UCI enhancements | ETRI |
| R1-2000812 | TP on Multi-TRP/Panel Transmission | Futurewei |
| R1-2000859 | Remaining issues for Multi-TRP enhancement | Apple |
| R1-2000865 | Summary #1 of Multi-TRP/Panel Transmission | OPPO |
| R1-2000925 | Remaining issues on multi-TRP/panel transmission | NTT DOCOMO, INC. |
| R1-2000941 | Corrections for multi-TRP transmission | Ericsson |
| R1-2000974 | Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2000988 | Maintenance of Rel-16 Multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2001169 | Summary #2 of Multi-TRP/Panel Transmission | OPPO |
| R1-2001348 | Text Proposal 1 for [100e-NR-eMIMO-multiTRP-02] | OPPO |
| R1-2001349 | Text Proposal 2 for [100e-NR-eMIMO-multiTRP-02] | OPPO |
| R1-2001360 | Text Proposal 1 for [100e-NR-eMIMO-multiTRP-03] | OPPO |
| R1-2001361 | Text Proposal 2 for [100e-NR-eMIMO-multiTRP-03] | OPPO |
| R1-2001377 | Outcome of email thread [100e-NR-eMIMO-multiTRP-01] | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2000203 | Remaining issues on multi-beam enhancements in R16 | Huawei, HiSilicon |
| R1-2000240 | Maintenance of enhancements on multi-beam operation | ZTE |
| R1-2000280 | Discussion on remaining issues on Multi-Beam and text proposals | vivo |
| R1-2000334 | Discussion on remaining issues on Multi-Beam and text proposals | vivo |
| R1-2000458 | Remaining issues on Multi-beam Operation Enhancement | OPPO |
| R1-2000596 | Remaining issues on Scell beam failure recovery | Lenovo, Motorola Mobility |
| R1-2000634 | On Rel.16 support for multibeam operation | Samsung |
| R1-2000680 | Text proposals on multi-beam operation | LG Electronics |
| R1-2000681 | Summary on Rel-16 Multi-Beam 1 maintenance | LG Electronics |
| R1-2000740 | Correction to multi beam operation | Intel Corporation |
| R1-2000755 | Maintenance for multi-beam operation | CMCC |
| R1-2000860 | Remaining issues for Multi-beam enhancement | Apple |
| R1-2000861 | Feature lead summary on SCell BFR and L1-SINR | Apple |
| R1-2000926 | Remaining issues on multi-beam operation | NTT DOCOMO, INC. |
| R1-2000975 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2000989 | Maintenance of Rel-16 Beam Management | Nokia, Nokia Shanghai Bell |
| R1-2001079 | On the timing for pathloss RS activation | Ericsson |
| R1-2001120 | Enhancements on UE multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2001161 | Revised summary on Rel-16 Multi-Beam 1 maintenance | LG Electronics |
| R1-2001172 | Summary of discussion topic A on Rel-16 MB1 | LG Electronics |
| R1-2001173 | Summary of discussion topic B on Rel-16 MB2 | LG Electronics |
| R1-2001174 | Summary of discussion topic C on Rel-16 MB3 | LG Electronics |
| R1-2001182 | Feature lead summary#2 on SCell BFR and L1-SINR | Apple |
| R1-2001259 | Outcome of email thread [100e-NR-eMIMO-MB-01] | LG Electronics |
| R1-2001260 | Outcome of email thread [100e-NR-eMIMO-MB-02] | LG Electronics |
| R1-2001261 | Outcome of email thread [100e-NR-eMIMO-MB-03] | LG Electronics |
| R1-2001262 | Outcome of email thread [100e-NR-eMIMO-MB-04] | Apple |
| R1-2001263 | Outcome of email thread [100e-NR-eMIMO-MB-05] | Apple |
| R1-2001264 | Outcome of email thread [100e-NR-eMIMO-MB-06] | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2000241 | Maintenance of full power UL transmission | ZTE |
| R1-2000281 | Discussion on remaining issues on ULFP and text proposals | vivo |
| R1-2000335 | Discussion on remaining issues on ULFP and text proposals | vivo |
| R1-2000459 | Text proposals for full TX power UL transmission | OPPO |
| R1-2000536 | Remaining issues on UL full power transmission | CATT |
| R1-2000635 | Correction on UL full power transmission | Samsung |
| R1-2000682 | Discussion on full Tx power UL transmission | LG Electronics |
| R1-2000741 | Correction to Full Tx Power UL Transmission | Intel Corporation |
| R1-2000756 | Discussion on full TX power UL transmission | CMCC |
| R1-2000802 | Feature lead summary on UL full power transmission | vivo |
| R1-2000818 | Corrections for Full Power UL Transmission | Ericsson |
| R1-2000862 | Remaining issues for UL full power transmission enhancement | Apple |
| R1-2000927 | Remaining issues on full Tx power UL transmission | NTT DOCOMO, INC. |
| R1-2000976 | Remaining issues on full power UL transmission | Qualcomm Incorporated |
| R1-2000990 | Maintenance of Rel-16 Full TX Power UL transmission | Nokia, Nokia Shanghai Bell |
| R1-2001041 | Remaining issues on UL full power transmission in R16 | Huawei, HiSilicon |
| R1-2001167 | Summary of 100e-Prep-email discussion on UL full power transmission | vivo |
| R1-2001209 | Feature lead summary#2 on UL full power transmission | vivo |
| R1-2001255 | FL summary of [100e-NR-eMIMO-ULFPTx-01] email thread | vivo |
| R1-2001296 | Editorial corrections (NR-MIMO) to 38.214 | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2000242 | Maintenance of low PAPR RS | ZTE |
| R1-2000460 | Text proposals for low PAPR RS | OPPO |
| R1-2000757 | Maintenance for low PAPR RS | CMCC |
| R1-2000768 | Remaining issues on low PAPR RS | NEC |
| R1-2000774 | Enhanced inter UE Tx prioritization/multiplexing | ETRI |
| R1-2000780 | Feature lead summary of low PAPR RS | Ericsson |
| R1-2000945 | Corrections in low PAPR RS for pi/2 BPSK PUSCH | Indian Institute of Tech (H) |
| R1-2000991 | Corrections on Low PAPR RS | Nokia, Nokia Shanghai Bell |
| R1-2001042 | Remaining issues on Low PAPR DMRS sequence in R16 | Huawei, HiSilicon |
| R1-2001076 | Remaining issue on low PAPR RS | Ericsson |
| R1-2001158 | Summary of critical issues for low PAPR RS maintenance | Ericsson |
| R1-2001238 | Output of email thread [100e-NR-eMIMO-lowPAPR-01] - TP for TS 38.211 | Ericsson |
| R1-2001239 | Output of email thread [100e-NR-eMIMO-lowPAPR-02] - TP#1 to 38.211 | Ericsson |
| R1-2001240 | Output of email thread [100e-NR-eMIMO-lowPAPR-02] - TP#2 to 38.212 | Ericsson |
| R1-2001241 | Output of email thread [100e-NR-eMIMO-lowPAPR-02] - TP#3 to 38.211 | Ericsson |
| R1-2001242 | Output of email thread [100e-NR-eMIMO-lowPAPR-03] - TP for TS 38.211 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000282 | Discussion on Rel-16 MIMO UE features | vivo |
| R1-2000336 | Discussion on Rel-16 MIMO UE features | vivo |
| R1-2000427 | Real life MIMO issue from observations in field | Ericsson |
| R1-2000461 | Remaining issues on multi-TRP and panel Transmission | OPPO |
| R1-2000636 | Issues on utilizing CSI-IM for interference measurement | Samsung |
| R1-2000683 | Clarification of the maximum number of CSI-RS resources in resource setting | LG Electronics |
| R1-2001103 | Remaining issues on R16 MIMO | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000210 | Corrections on PDCCH based power saving | Huawei, HiSilicon |
| R1-2000283 | Maintenance of PDCCH-based power saving signal | vivo |
| R1-2000337 | Maintenance of PDCCH-based power saving signal | vivo |
| R1-2000417 | Clarification on power saving signal | Spreadtrum Communications |
| R1-2000443 | Remaining issues on PDCCH-based power saving signal | MediaTek Inc. |
| R1-2000478 | Remaining issues for power saving signal | OPPO |
| R1-2000511 | Remaining issues on WUS PDCCH | ZTE |
| R1-2000537 | Remaining issues on the Power Saving Signals/Channels | CATT |
| R1-2000637 | Remaining issues for PDCCH-based power saving signal/channel | Samsung |
| R1-2000684 | Remaining issues on PDCCH-based power saving signal/channel | LG Electronics |
| R1-2000742 | Remaining details of PDCCH-based power saving signal/channel | Intel Corporation |
| R1-2000758 | Discussion on DCI format 2_6 monitoring | CMCC |
| R1-2000817 | Remaining Issues for PDCCH-based Power Saving Signal/Channel | InterDigital, Inc. |
| R1-2000866 | Work split between 38.213 and 38.321 on DRX operation with PS-RNTI configuration | NEC |
| R1-2000884 | Remaining issues for WUS | Ericsson |
| R1-2000928 | Maintenance for PDCCH-based power saving signal/channel | NTT DOCOMO, INC. |
| R1-2001048 | On open issues related to DCI format 2_6 | Nokia, Nokia Shanghai Bell |
| R1-2001137 | Summary of PDCCH-based Power Saving Signal/Channel | CATT |
| R1-2001190 | Summary of preparation phase discussion on AI-7.2.7.1 PDCCH-based power saving signal/channel | CATT |
| R1-2001248 | Summary of Phase 1 Discussion on PDCCH-based Power Saving Signal/Channel | CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2000180 | Corrections on cross-slot scheduling based power saving | Huawei, HiSilicon |
| R1-2000284 | Maintenance of procedure of cross-slot scheduling power saving techniques | vivo |
| R1-2000338 | Maintenance of procedure of cross-slot scheduling power saving techniques | vivo |
| R1-2000444 | Remaining issues on cross-slot scheduling adaptation | MediaTek Inc. |
| R1-2000455 | Clarification on cross-slot scheduling | Spreadtrum Communications |
| R1-2000512 | Remaining issues on cross-slot scheduling power saving techniques | ZTE |
| R1-2000538 | Remaining issues on Power saving scheme with cross-slot scheduling | CATT |
| R1-2000638 | Remaining issues for corss-slot scheduling power saving techniques | Samsung |
| R1-2000685 | Remaining issues on procedure of cross-slot scheduling power saving techniques | LG Electronics |
| R1-2000715 | Remaining issues for cross-slot scheduling | OPPO |
| R1-2000743 | Remaining details of cross-slot scheduling for power saving | Intel Corporation |
| R1-2000759 | Corrections on cross-slot scheduling procedure | CMCC |
| R1-2000863 | Remaining Issues on Cross Slot Scheduling Technique for UE Power Saving | Apple |
| R1-2000885 | Remaining issues for cross-slot scheduling | Ericsson |
| R1-2000929 | Maintenance for procedure of cross-slot scheduling power saving techniques | NTT DOCOMO, INC. |
| R1-2000977 | Remaining issues in cross-slot scheduling power saving | Qualcomm Incorporated |
| R1-2001049 | Procedure of cross-slot scheduling power saving techniques | Nokia, Nokia Shanghai Bell |
| R1-2001141 | Summary#1 for cross-slot scheduling power saving techniques | MediaTek |
| R1-2001211 | Summary#2 for cross-slot scheduling power saving techniques | MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R1-2000211 | Corrections on UE adaptation to maximum MIMO layers | Huawei, HiSilicon |
| R1-2000285 | Maintenance of UE adaptation to maximum number of MIMO layers | vivo |
| R1-2000339 | Maintenance of UE adaptation to maximum number of MIMO layers | vivo |
| R1-2000803 | Summary of UE adaptation to maximum number of MIMO layers | vivo |
| R1-2000886 | Maintenance issues for MIMO layer signaling per BWP | Ericsson |
| R1-2001050 | On open issues for per-BWP DL MIMO layers | Nokia, Nokia Shanghai Bell |
| R1-2001189 | Summary#2 of UE adaptation to maximum number of MIMO layers | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2000286 | Other issues for UE power saving | vivo |
| R1-2000340 | Other issues for UE power saving | vivo |
| R1-2000513 | Views on power saving enhancement | ZTE |
| R1-2000887 | Discussion on UE features for Rel-16 power savings | Ericsson |
| R1-2001104 | Other Remaining issues for Rel-16 Power saving | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000190 | Maintenance of DL PRS for NR positioning | Huawei, HiSilicon |
| R1-2000243 | Maintenance on DL reference signals for NR positioning | ZTE |
| R1-2000287 | Discussion on remaining issues on DL RS for NR positioning | vivo |
| R1-2000341 | Discussion on remaining issues on DL RS for NR positioning | vivo |
| R1-2000462 | Remaining Issues on DL Positioning Reference Signal | OPPO |
| R1-2000539 | Remaining issues on DL PRS for NR Positioning | CATT |
| R1-2000575 | TP on DL Reference Signals | Futurewei |
| R1-2000639 | DL reference signals for NR Positioning | Samsung |
| R1-2000686 | Remaining issues of DL reference signals for NR Positioning | LG Electronics |
| R1-2000760 | Corrections on DL PRS resource set parameters | CMCC |
| R1-2000804 | Correction of DL PRS sequence generation | Nokia, Nokia Shanghai Bell |
| R1-2001002 | Maintenance of rel16 DL reference signals for NR positioning | Ericsson |
| R1-2001142 | Feature lead summary for AI 7.2.8.1 – DL Reference Signals for NR Positioning | Intel |
| R1-2001176 | Feature lead summary#2 for AI 7.2.8.1 – DL Reference Signals for NR Positioning | Intel |
| R1-2001233 | Output of email thread [100e-NR-Pos-DL-PRS-01] | Intel |
| R1-2001234 | Text proposal to TS 38.211 based on outcome of [100e-NR-Pos-DL-PRS-01] | Intel |
| R1-2001235 | Output of email thread [100e-NR-Pos-DL-PRS-02] | Intel |
| TDoc | Title | Source |
|---|---|---|
| R1-2000191 | Maintenance of SRS for NR positioning | Huawei, HiSilicon |
| R1-2000288 | Discussion on remaining issues on UL RS for NR positioning | vivo |
| R1-2000342 | Discussion on remaining issues on UL RS for NR positioning | vivo |
| R1-2000463 | Remaining Issues on UL Positioning Reference Signal | OPPO |
| R1-2000540 | Remaining issues on UL SRS for NR Positioning | CATT |
| R1-2000576 | TP on UL Reference Signals | Futurewei |
| R1-2000640 | UL reference signals for NR Positioning | Samsung |
| R1-2000687 | Remaining issues of UL reference signals for NR Positioning | LG Electronics |
| R1-2000761 | Discussions on UL SRS for positioning collision rules | CMCC |
| R1-2001003 | Maintenance of rel16 UL reference signals for NR positioning | Ericsson |
| R1-2001128 | FL Summary for UL Reference Signals for NR Positioning | Ericsson |
| R1-2001194 | Revised FL Summary for UL Reference Signals for NR Positioning | Ericsson |
| R1-2001286 | Outcome of email thread [100e-NR-Pos-ULRS-01] | Ericsson |
| R1-2001287 | Outcome of email thread [100e-NR-Pos-ULRS-02] | Ericsson |
| R1-2001288 | Outcome of email thread [100e-NR-Pos-ULRS-03] | Ericsson |
| R1-2001289 | Outcome of email thread [100e-NR-Pos-ULRS-04] | Ericsson |
| R1-2001386 | LS on outcome of email discussions on aperiodic SRS for positioning configuration from RAN1#100e | RAN1, Ericsson |
| R1-2001483 | LS on outcome of email discussions on aperiodic SRS for positioning configuration from RAN1#100e | RAN1, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000192 | Maintenance of NR positioning measurements | Huawei, HiSilicon |
| R1-2000289 | Discussion on remaining issues on UE and gNB measurements for NR positioning | vivo |
| R1-2000343 | Discussion on remaining issues on UE and gNB measurements for NR positioning | vivo |
| R1-2000464 | Remaining Issues on Measurements for NR Positioning | OPPO |
| R1-2000541 | Remaining issues on NR Positioning Measurements | CATT |
| R1-2000577 | TP on Measurements | Futurewei |
| R1-2000641 | UE and gNB measurements for NR Positioning | Samsung |
| R1-2000688 | Remaining issues of UE and gNB measurements for NR Positioning | LG Electronics |
| R1-2000805 | Maintainence of Measurement Definitions | Nokia, Nokia Shanghai Bell |
| R1-2000932 | FL Summary of Remaining issues on NR Positioning Measurements | CATT |
| R1-2000978 | Maintenace on UE and gNB measurements for NR Positioning | Qualcomm Incorporated |
| R1-2001004 | Maintenance of rel16 Physical-layer procedures to support UE - gNB measurements | Ericsson |
| R1-2001156 | FL Summary#2 of Remaining issues on NR Positioning Measurements | CATT |
| R1-2001243 | Output of email thread [100e-NR-Pos-Measurements-01] | CATT |
| R1-2001244 | Text proposal to TS 38.215 based on outcome of [100e-NR-Pos-Measurements-01] | CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2000193 | Maintenance of physical layer procedures to support positioning measurements | Huawei, HiSilicon |
| R1-2000244 | Maintenance on physical layer procedures for NR positioning | ZTE |
| R1-2000290 | Discussion on remaining issues on on physical-layer procedures for NR positioning | vivo |
| R1-2000344 | Discussion on remaining issues on on physical-layer procedures for NR positioning | vivo |
| R1-2000465 | Remaining Issues on Physical Layer Procedures for NR Positioning | OPPO |
| R1-2000578 | TP on Measurement Procedures | Futurewei |
| R1-2000642 | Physical-layer procedures to support UE/gNB measurements | Samsung |
| R1-2000689 | Remaining issues of Physical-layer preocedures to support UE/gNB measurements | LG Electronics |
| R1-2000762 | Discussions on TA adjustment on timing measurements | CMCC |
| R1-2001005 | Maintenance of rel16 UE and gNB measurements for NR Positioning | Ericsson |
| R1-2001077 | Remaining opens on NR Positioning physical layer procedures | Intel Corporation |
| R1-2001143 | Summary of remaining issues on PHY procedures for NR positioning measurements | Qualcomm |
| R1-2001168 | Summary#2 of remaining issues on PHY procedures for NR positioning measurements | Qualcomm |
| R1-2001364 | Summary of Email Discussion [100e-NR-Pos-PHY procedures-01]: PRS reception procedure | Qualcomm Incorporated |
| R1-2001365 | Summary of Email Discussion [100e-NR-Pos-PHY procedures-02]: UE procedure for determining slot format | Qualcomm Incorporated |
| R1-2001366 | Summary of Email Discussion [100e-NR-Pos-PHY procedures-03]: UE procedures for SRS for positioning | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2000194 | RAN procedures for NR positioning | Huawei, HiSilicon |
| R1-2000291 | Discussion on parameter assumptions and evaluations for NR positioning enhancements | vivo |
| R1-2000345 | Discussion on parameter assumptions and evaluations for NR positioning enhancements | vivo |
| R1-2000466 | Discussion on RE mapping in reference signal for NR positioning | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2000946 | Issue Summary for NR Mobility Enhancements | Intel Corporation |
| R1-2001200 | Issue Summary#2 for NR Mobility Enhancements | Intel Corporation |
| TDoc | Title | Source |
|---|---|---|
| R1-2000206 | Remaining issues on DAPS-HO | Huawei, HiSilicon |
| R1-2000366 | Remaining issues on NR mobility enhancements in physical layer | ZTE |
| R1-2000442 | On DAPS HO for mobility enhancement | MediaTek Inc. |
| R1-2000643 | Remaining issues for NR Mobility Enhancement | Samsung |
| R1-2000864 | On remaining issues on NR mobility enhancements | Apple |
| R1-2000979 | Maintenance for NR mobility enhancements | Qualcomm Incorporated |
| R1-2001051 | Remaining physical layer aspects of dual active protocol stack based HO | Nokia, Nokia Shanghai Bell |
| R1-2001080 | Correction to UL power sharing for DAPS HO | Ericsson |
| R1-2001246 | Email discussion summary for NR Mobility Enhancements | Intel Corporation |
| TDoc | Title | Source |
|---|---|---|
| R1-2000207 | Remaining PHY aspects for CHO | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2000292 | Remaining issues on uplink power control for NR-NR DC | vivo |
| R1-2000346 | Remaining issues on uplink power control for NR-NR DC | vivo |
| R1-2000361 | Remaining Issues on NR-DC Power Control | ZTE |
| R1-2000440 | On UL Power Control for NN-DC | MediaTek Inc. |
| R1-2000561 | Text proposals for UL Power Sharing for NR-DC | OPPO |
| R1-2000644 | Power Control for NR-DC | Samsung |
| R1-2000721 | Remaining issues on uplink power control for NN-DC | Intel Corporation |
| R1-2000845 | On remaining issues of UL Power Control for NN-DC | Apple |
| R1-2000846 | FL summary on UL Power Control for NN-DC | Apple |
| R1-2000888 | Remaining issues for NR-DC UL Power Control | Ericsson |
| R1-2000980 | Remaining issues on uplink power control for NR-DC | Qualcomm Incorporated |
| R1-2001039 | UL power control for NR-NR dual connectivity | Huawei, HiSilicon |
| R1-2001067 | Maintenance of rel-16 DC power control | Nokia, Nokia Shanghai Bell |
| R1-2001208 | FL summary#2 on UL Power Control for NN-DC | Apple |
| R1-2001301 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-ULPC-01] | Apple |
| R1-2001302 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-ULPC-02] | Apple |
| R1-2001303 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-ULPC-03] | Apple |
| R1-2001421 | LS on uplink power control for NR-NR Dual-Connectivity | RAN1, Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2000362 | Remaining Issues on Single Tx Switched Uplink Solution for EN-DC | ZTE |
| R1-2000690 | Remaining issue on single TX-switched UL for EN-DC | LG Electronics |
| R1-2000847 | On remaining issues on single Tx transmission EN-DC | Apple |
| R1-2000848 | FL summary of remaining issues on enhancements for single Tx transmission in EN-DC | Apple |
| R1-2000889 | Remaining issues for single Tx UL enhancements | Ericsson |
| R1-2000981 | Remaining issues for EN-DC Single-Tx TDM Operation | Qualcomm Incorporated |
| R1-2001040 | Enhancements for single UL operation for EN-DC | Huawei, HiSilicon |
| R1-2001391 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-SingleTx-01] | Apple |
| R1-2001392 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-SingleTx-02] | Apple |
| R1-2001393 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-SingleTx-03] | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2000208 | Corrections on efficient and low latency serving cell configuration/activation/setup | Huawei, HiSilicon |
| R1-2000293 | Remaining issues on Scell dormancy like behavior | vivo |
| R1-2000347 | Remaining issues on Scell dormancy like behavior | vivo |
| R1-2000363 | Remaining Issues on Fast SCell Activation | ZTE |
| R1-2000504 | Remaining issues on Efficient CA design | Nokia, Nokia Shanghai Bell |
| R1-2000645 | Remaining issues for support of efficient and low latency serving cell configuration/activation/setup | Samsung |
| R1-2000716 | Discussion on default behavior of Scell dormancy | OPPO |
| R1-2000722 | Remaining issues on SCell dormancy behavior | Intel Corporation |
| R1-2000890 | Remaining issues for reduced latency Scell management for NR CA | Ericsson |
| R1-2000891 | Summary of efficient and low latency serving cell configuration/activation/setup | Ericsson |
| R1-2000982 | Remaining issues for SCell dormancy | Qualcomm Incorporated |
| R1-2001192 | Summary#2 of efficient and low latency serving cell configuration/activation/setup | Ericsson |
| R1-2001416 | Summary of email discussion [100e-NR-LTE_NR_DC_CA_enh-ScellDormancy-01] | Ericsson |
| R1-2001417 | Summary of email discussion [100e-NR-LTE_NR_DC_CA_enh-ScellDormancy-02] | Ericsson |
| R1-2001418 | Summary of email discussion [100e-NR-LTE_NR_DC_CA_enh-ScellDormancy-03] | Ericsson |
| R1-2001419 | Text proposals from email discussion [100e-NR-LTE_NR_DC_CA_enh-ScellDormancy-01] | Ericsson |
| R1-2001420 | Text proposals from email discussion [100e-NR-LTE_NR_DC_CA_enh-ScellDormancy-02] | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000294 | Remaining issues on aperiodic CSI-RS triggering | vivo |
| R1-2000348 | Remaining issues on aperiodic CSI-RS triggering | vivo |
| R1-2001033 | Corrections on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH | Huawei, HiSilicon |
| R1-2001081 | On the handling of beamSwitchTiming values of 224 and 336 | Ericsson |
| R1-2001145 | FL summary on cross-carrier scheduling with different numerology | Nokia, Nokia Shanghai Bell |
| R1-2001146 | FL summary update on cross-carrier scheduling with different numerology | Nokia, Nokia Shanghai Bell |
| R1-2001350 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-X-CC-A-CSI-RS-01] | Nokia |
| R1-2001351 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-X-CC-A-CSI-RS-02] | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000295 | Remaining issues on unaligned frame boundary for CA | vivo |
| R1-2000349 | Remaining issues on unaligned frame boundary for CA | vivo |
| R1-2000364 | Remaining Issues on ASync CA | ZTE |
| R1-2000441 | On inter-band CA with unaligned frame boundary | MediaTek Inc. |
| R1-2000519 | Correction on HARQ-ACK codebook for inter-band CA with unaligned frame boundary | CATT |
| R1-2000691 | Remaining issue on unaligned CA with slot alignment | LG Electronics |
| R1-2000763 | Remaining issues on support of unaligned frame boundary with slot alignment and partial SFN alignment | CMCC |
| R1-2000892 | Remaining issues for inter-band CA with unaligned frame boundary | Ericsson |
| R1-2001034 | Corrections on unaligned frame boundary with slot alignment and partial SFN alignment for R16 NR inter-band CA | Huawei, HiSilicon |
| R1-2001131 | FL summary on support of unaligned frame boundary for R16 NR inter-band CA | CMCC |
| R1-2001154 | FL summary#2 on support of unaligned frame boundary for R16 NR inter-band CA | CMCC |
| R1-2001265 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Unaligned_CA-01] | CMCC |
| R1-2001266 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Unaligned_CA-02] | CMCC |
| R1-2001267 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Unaligned_CA-03] | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2000296 | Remaining issues on cross-carrier scheduling with mix numerologies | vivo |
| R1-2000350 | Remaining issues on cross-carrier scheduling with mix numerologies | vivo |
| R1-2000365 | Remaining Issues on Cross-carrier Scheduling with Mixed Numerologies | ZTE |
| R1-2000646 | Remaining issues for cross-carrier scheduling with different numerology | Samsung |
| R1-2000893 | Remaining issues for cross-carrier scheduling with different numerologies | Ericsson |
| R1-2000983 | CR for default QCL assumption for Rel-16 cross-carrier scheduling | Qualcomm Incorporated |
| R1-2000985 | Discussion on support of cross-carrier scheduling with different numerology | ASUSTeK |
| R1-2001035 | Corrections on cross-carrier scheduling with different numerology | Huawei, HiSilicon |
| R1-2001068 | FL summary on cross-carrier scheduling with different numerology | Nokia, Nokia Shanghai Bell |
| R1-2001069 | FL summary update on cross-carrier scheduling with different numerology | Nokia, Nokia Shanghai Bell |
| R1-2001352 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Cross-CCScheduling-01] | Nokia |
| R1-2001353 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Cross-CCScheduling-02] | Nokia |
| R1-2001354 | Outcome of email thread [100e-NR-LTE_NR_DC_CA_enh-Cross-CCScheduling-03] | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2000209 | Discussion on Cross-carrier triggering PDCCH order | Huawei, HiSilicon |
| R1-2000894 | Data rate handling for intra-FR NR-DC | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2000212 | On NR UE features in Rel-16 | Huawei, HiSilicon |
| R1-2000297 | On Rel-16 UE features | vivo |
| R1-2000351 | On Rel-16 UE features | vivo |
| R1-2000367 | Discussion on NR Rel-16 UE Features | ZTE |
| R1-2000454 | Views on Rel-16 UE feature list | MediaTek Inc. |
| R1-2000488 | Discussion on Rel-16 UE features | OPPO |
| R1-2000930 | RAN1 UE features list for Rel-16 NR | NTT DOCOMO, INC., AT&T |
| R1-2001117 | On Rel-16 UE Features | Ericsson LM |
| R1-2001484 | RAN1 UE features list for Rel-16 NR after RAN1#100-e | Moderator (AT&T, NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2000147 | void | ETSI MCC |
| R1-2000148 | void | ETSI MCC |
| R1-2000149 | void | ETSI MCC |
| R1-2000514 | On the TBS issue and the TEI issue of half-duplex operation in CA | ZTE |
| R1-2000573 | Features for Rel-16 V2X | Futurewei |
| R1-2000692 | Remaining details of CLI measurement and reporting at a UE | LG Electronics |
| R1-2000895 | Remaining issues for DSS | Samsung, KDDI, Nokia, Nokia Shanghai Bell |
| R1-2000931 | Summary on NR Rel-16 TEI related discussion | NTT DOCOMO, INC. |
| R1-2000984 | Discussion on Rel-16 NR UE features | Qualcomm Incorporated |
| R1-2000986 | Remaining issues for Rel-16 maintenance and TEI | Ericsson |
| R1-2001064 | On remaining NR TEI issues | Nokia, Nokia Shanghai Bell |
| R1-2001109 | Further details of Rel-16 UE features for MIMO | Huawei, HiSilicon |
| R1-2001121 | On remaining NR TEI issues | Nokia, Nokia Shanghai Bell |
| R1-2001155 | Output summary on NR Rel-16 TEI after RAN1#100-e preparation phase | NTT DOCOMO, INC. |
| R1-2001231 | Outcome of email thread [100e-NR-TEICRs-01] | NTT DOCOMO |
| R1-2001232 | Outcome of email thread [100e-NR-TEICRs-02] | NTT DOCOMO |
| R1-2001320 | LS on CLI measurement and reporting | LG Electronics |
| R1-2001385 | Endorsed TP in [100e-NR-TEICRs-02] | Nokia, Nokia Shanghai Bell |