| TDoc | Title | Source |
|---|---|---|
| R1-2100000 | Draft Agenda of RAN1#104-e meeting | RAN1 Chair |
| R1-2101668 | RAN1#104-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2101669 | Additional Guidelines for RAN1#104 e-Meeting Management | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2100002 | Highlights from RAN#90-e | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2100001 | Report of RAN1#103-e meeting | ETSI MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2100003 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2100004 | LS on inter-donor topology redundancy | RAN3, Samsung |
| R1-2100005 | LS on Rel-16 NR Positioning Correction | RAN3, Huawei |
| R1-2100006 | Reply LS on LS on signalling of satellite backhaul connection | RAN3, Huawei |
| R1-2100007 | LS on Phase noise and other RF Impairment modelling | RAN4, Ericsson |
| R1-2100008 | LS on measuring CSI-RS during SCell activation. | RAN4, Ericsson |
| R1-2100009 | LS on SL switching priority | RAN4, Xiaomi |
| R1-2100010 | LS response on cell-grouping UE capability for synchronous NR-DC | RAN4, Apple |
| R1-2100011 | LS on DC location reporting for intra-band UL CA | RAN4, Nokia |
| R1-2100012 | LS on removing restriction on configuring UL MIMO for SUL band | RAN4, CMCC |
| R1-2100013 | LS on TCI state indication at Direct SCell activation | RAN4, MediaTek |
| R1-2100014 | AN-PDB and PER targets for satellite access | SA2, Qualcomm |
| R1-2100015 | LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | SA2, Tencent |
| R1-2100016 | LS on Use of Inclusive Language in 3GPP | SA, Intel |
| R1-2100017 | LS on Physical layer assisted lightweight AKA (PL-AKA) protocol for the Internet of things | SA3, Ericsson |
| R1-2100018 | LS on multi-TRP description in Stage-2 | RAN2, Nokia |
| R1-2100019 | LS on capability for extended RAR window monitoring | RAN2, Qualcomm |
| R1-2100020 | LS on Paging Enhancement | RAN2, MediaTek |
| R1-2100021 | LS to RAN1 on SL DRX design | RAN2, ZTE |
| R1-2100022 | LS on the use of simultaneous CSI-RS resources and ports | RAN2, Ericsson |
| R1-2100023 | LS on half-duplex operation | RAN2, Nokia |
| R1-2100024 | Reply LS on propagation delay compensation enhancements | RAN2, Nokia |
| R1-2100025 | LS on physical layer aspects of small data transmission | RAN2, ZTE |
| R1-2100026 | LS on overlapped data and SR are of equal L1 priority | RAN2, Huawei |
| R1-2100027 | Reply LS on power control for NR-DC | RAN2, vivo |
| R1-2100028 | Reply LS on Direct Discovery and Relay | RAN2, OPPO |
| R1-2100029 | Reply LS on defined values for V field in the Release 14 specification of MAC header | RAN2, Huawei |
| R1-2100030 | Reply LS on Full slot formats support in TDD UL-DL configuration | RAN2, Qualcomm |
| R1-2100031 | Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission | RAN2, Ericsson |
| R1-2100032 | IEEE 1609 WG Liaison Message to 3GPP regarding defined values for V field in the Release 14 specification of MAC header | IEEE Vehicular Technology/Intelligent Transportation System 1609 WG |
| R1-2100080 | Discussion on the physical layer aspects of small data transmission | ZTE, Sanechips |
| R1-2100085 | [DRAFT] Reply LS on half-duplex operation | ZTE |
| R1-2100088 | [DRAFT] Reply LS on overlapped data and SR of equal L1 priority | ZTE |
| R1-2100089 | Discussion on overlapped data and SR of equal L1 priority | ZTE |
| R1-2100125 | Discussion on LS on multi-TRP description in Stage-2 | OPPO |
| R1-2100138 | Draft reply LS on per-table MCS range for mode-2 | OPPO |
| R1-2100139 | Draft reply LS on SL switching priority | OPPO |
| R1-2100311 | Discussion on LS from RAN2 on SL DRX design | CATT, GOHIGH |
| R1-2100312 | Discussion on RAN3 LS on Rel-16 NR Positioning Correction | CATT |
| R1-2100313 | Draft Reply LS on Rel-16 NR Positioning Correction | CATT |
| R1-2100314 | Draft Reply LS on RAN1 agreement on pre-emption | CATT, GOHIGH |
| R1-2100315 | Draft Reply LS on per table MCS range for mode-2 | CATT, GOHIGH |
| R1-2100316 | Draft Reply LS on SL switching priority | CATT, GOHIGH |
| R1-2100317 | Discussion on physical layer aspects of small data transmission | CATT |
| R1-2100318 | Discussion on overlapped data and SR of equal L1 priority | CATT |
| R1-2100319 | Draft reply LS on half-duplex operation | CATT |
| R1-2100403 | Draft reply LS on use of simultaneous CSI-RS resources and ports | CATT |
| R1-2100501 | On physical layer aspects of small data transmission | Nokia, Nokia Shanghai Bell |
| R1-2100502 | On TCI state indication for Scells | Nokia, Nokia Shanghai Bell |
| R1-2100503 | On DC location reporting | Nokia, Nokia Shanghai Bell |
| R1-2100504 | On half-duplex operation | Nokia, Nokia Shanghai Bell |
| R1-2100513 | Draft reply LS on SL DRX design | LG Electronics |
| R1-2100627 | Discussion on LS on small data transmission | Intel Corporation |
| R1-2100727 | [Draft] Reply LS on overlapped data and SR are of equal L1 priority | Nokia |
| R1-2100832 | [Draft] Reply LS on SA WG2 assumptions AN-PDB and PER targets for satellite access | THALES |
| R1-2100887 | Draft reply LS on Rel-16 updated RAN4 UE features lists for LTE and NR | LG Electronics |
| R1-2100888 | Discussion on RAN4 LS on measuring CSI-RS during SCell activation | LG Electronics |
| R1-2100889 | Discussion on RAN2 LS on capability for extended RAR window monitoring | LG Electronics |
| R1-2100910 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2100923 | [Draft] Reply LS to RAN2 on SL DRX design | ZTE, Sanechips |
| R1-2100935 | [Draft] Reply LS on SL switching priority | ZTE, Sanechips |
| R1-2100961 | About reply LS on inter-donor topology redundancy in IAB | ZTE, Sanechips |
| R1-2101090 | [Draft] Reply LS on SL switching priority | Xiaomi |
| R1-2101147 | Draft reply LS on TCI state indication at Direct SCell activation | vivo |
| R1-2101148 | Draft reply LS on SL switching priority | vivo |
| R1-2101149 | Discussion on switching between LTE SL and NR SL | vivo |
| R1-2101150 | Draft reply LS on per-table MCS range for mode-2 | vivo |
| R1-2101151 | Draft reply LS on SL DRX design | vivo |
| R1-2101152 | Discussion on Paging enhancement | vivo |
| R1-2101153 | Draft reply LS on Rel-16 NR Positioning Correction | vivo |
| R1-2101154 | Reply LS on overlapped data and SR with equal L1 priority | vivo |
| R1-2101155 | Draft reply LS on on inter-donor topology redundancy | vivo |
| R1-2101156 | Draft reply LS on measuring CSI-RS during SCell activation | vivo |
| R1-2101157 | Draft reply LS on New Standardized 5QIs for 5G-AIS | vivo |
| R1-2101158 | Discussion on Configuration for CA Half duplex operation | vivo |
| R1-2101159 | Discussion on RAN1 impacts for small data transmisison | vivo |
| R1-2101163 | Draft reply LS on half-duplex operation | Samsung |
| R1-2101164 | Discussion on measuring CSI-RS during Scell activation | Samsung |
| R1-2101165 | Discussion on physical layer aspects of small data transmission | Samsung |
| R1-2101166 | Draft reply LS on overlapped data and SR are of equal L1 priority | Samsung |
| R1-2101167 | Draft reply LS on inter-donor topology redundancy | Samsung |
| R1-2101168 | Draft reply LS on per-table MCS range for mode-2 | Samsung |
| R1-2101169 | Draft reply LS on SL switching priority | Samsung |
| R1-2101170 | Draft reply LS on the use of simultaneous CSI-RS resources and ports | Samsung |
| R1-2101250 | Discussion on SRS carrier information | Huawei, HiSilicon |
| R1-2101251 | [Draft] Reply LS on Rel-16 NR Positioning Correction | Huawei |
| R1-2101267 | RA and CG based small data transmission | Huawei, HiSilicon |
| R1-2101276 | Draft reply LS on overlapped data and SR with equal L1 priority for Rel-16 URLLC | Huawei, HiSilicon |
| R1-2101277 | Discussion on overlapped data and SR with equal L1 priority for Rel-16 URLLC | Huawei, HiSilicon |
| R1-2101287 | Discussion on RAN4 LS on measuring CSI-RS during SCell activation | Nokia, Nokia Shanghai Bell |
| R1-2101303 | Draft Reply LS on the use of simultaneous CSI-RS resources and ports | Ericsson |
| R1-2101319 | Draft LS response on New Standardized 5QIs for AIS | Ericsson |
| R1-2101335 | Discussion on measuring CSI-RS during SCell activation | Apple |
| R1-2101336 | [Draft] LS reply on measuring CSI-RS during SCell activation | Apple |
| R1-2101337 | Draft reply LS on newly proposed 5QIs for 5G-AIS | Apple |
| R1-2101338 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2101405 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2101410 | Discussion on new standardized 5QIs for 5G-AIS from SA2 | OPPO, Tencent, China Mobile, China Telecom, China Unicom |
| R1-2101411 | [Draft] Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | OPPO |
| R1-2101427 | Reply to RAN4 LS on SL Switching Priority | Qualcomm Incorporated |
| R1-2101428 | Reply to RAN2 LS on per-table MCS range for mode-2 | Qualcomm Incorporated |
| R1-2101429 | Reply to RAN2 LS on SL DRX design | Qualcomm Incorporated |
| R1-2101430 | Reply to RAN2 LS on SDT resource configuration | Qualcomm Incorporated |
| R1-2101502 | Discussion of Response LS on Overlapped Data and SR of Equal L1 Priority | Ericsson Inc. |
| R1-2101518 | [DRAFT] LS reply on physical layer aspects of small data transmission | Ericsson |
| R1-2101528 | Discussion on LS on overlapping data and SR with same L1 priority | Intel Corporation |
| R1-2101645 | Discussion on the feasibility and limitations of paging subgrouping | ZTE , Sanechips |
| R1-2101667 | [Draft] Reply LS on Paging Enhancement | Nokia, Nokia Shanghai Bell |
| R1-2101704 | [Draft] LS on per-table MCS range for mode-2 | Ericsson |
| R1-2101705 | [Draft] LS on SL DRX design | Ericsson |
| R1-2101706 | [Draft] LS on SL switching priority | Ericsson |
| R1-2101719 | Discussion on LS on AN-PDB and PER targets for satellite access | Intel Corporation |
| R1-2101734 | Discussion on RAN2 LS on per-table MCS range for mode-2 | Huawei, HiSilicon |
| R1-2101735 | Discussion on RAN4 LS on SL switching priority | Huawei, HiSilicon |
| R1-2101736 | Discussion on RAN2 LS on DRX impact | Huawei, HiSilicon |
| R1-2101737 | Discussion on UE capability xDD differentiation for SUL/SDL bands | Huawei, HiSilicon |
| R1-2101741 | Discussion on TCI state indication at Direct SCell activation | Huawei, HiSilicon |
| R1-2101742 | Discussion on use of simultaneous CSI-RS resources and ports | Huawei, HiSilicon |
| R1-2101745 | Discussion on LS on half-duplex operation | Huawei, HiSilicon |
| R1-2101746 | Discussion on LS on paging enhancement | Huawei, HiSilicon |
| R1-2101747 | Discussion on measuring CSI-RS during SCell activation | Huawei, HiSilicon |
| R1-2101748 | Discussion on the AN-PDB and PER targets for satellite access | Huawei, HiSilicon |
| R1-2101749 | Discussion on inter-donor topology redundancy | Huawei, HiSilicon |
| R1-2101750 | On changes to multi-TRP description in Stage-2 | Huawei, HiSilicon |
| R1-2101753 | Discussion on LS on new standardized 5QIs for 5G-AIS | Huawei, HiSilicon |
| R1-2101765 | LS on XR-Traffic Models | SA4, Qualcomm |
| R1-2101785 | Draft reply LS on SL DRX design | LG Electronics |
| R1-2101821 | RAN1#104-e preparation phase on LSs | RAN1 Chair |
| R1-2101915 | [Draft] Reply LS on Rel-16 NR Positioning Correction | Huawei |
| R1-2101953 | Draft Reply LS on the use of simultaneous CSI-RS resources and ports | Ericsson |
| R1-2101962 | Reply LS on the use of simultaneous CSI-RS resources and ports | RAN1, Ericsson |
| R1-2101975 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | RAN1, OPPO |
| R1-2101976 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | RAN1, OPPO |
| R1-2102063 | void | MCC ETSI |
| R1-2102071 | LS to capture Text Proposal for TR 38.857 | RAN2, Ericsson |
| R1-2102075 | [DRAFT] LS reply on physical layer aspects of small data transmission | ZTE |
| R1-2102076 | Summary on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2102125 | LS reply on physical layer aspects of small data transmission | RAN1, ZTE |
| R1-2102147 | LS to capture Text Proposal for TR 38.857 | RAN2, Ericsson |
| R1-2102148 | Reply LS on Rel-16 NR positioning Correction | RAN2, Huawei |
| R1-2102208 | Moderator summary of [104-e-AI5-LS-02] for the reply LS to R1-200023 | Moderator (Nokia) |
| R1-2102271 | Response LS to RAN1 on the resource reservation period | RAN2, LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2100086 | Discussion on Rel-17 UL Tx Switching | ZTE |
| R1-2100126 | Dsicussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2101270 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2100081 | Draft CR on clarification of TPC command for PUCCH | ZTE |
| R1-2100559 | Clarification on power control for NB-IoT | ZTE |
| R1-2101281 | Correction on spectral efficiency of 1024QAM | Huawei, HiSilicon |
| R1-2101508 | Correction for support of 1024QAM for PDSCH | Qualcomm Incorporated |
| R1-2101577 | Discussion on UCI multiplexing for partial PUSCH mode 1 | Samsung, Huawei, HiSilicon |
| R1-2101578 | Draft 36.212 CR on UCI multiplexing for partial PUSCH mode 1 | Samsung, Huawei, HiSilicon |
| R1-2101812 | RAN1#104-e preparation phase on Maintenance of E-UTRA Releases 8-15 | Ad-Hoc Chair (Ericsson) |
| R1-2101943 | Correction on spectral efficiency of 1024QAM | Huawei, HiSilicon |
| R1-2101944 | Correction on spectral efficiency of 1024QAM | Huawei, HiSilicon |
| R1-2101945 | Correction for support of 1024QAM for PDSCH | Qualcomm Incorporated |
| R1-2101946 | Correction for support of 1024QAM for PDSCH | Qualcomm Incorporated |
| R1-2101947 | Feature lead summary on [104-e-LTE-6.1CRs-03] | Moderator (Huawei) |
| R1-2101977 | CR on clarification of TPC command for PUCCH | ZTE, Qualcomm |
| R1-2101978 | CR on clarification of TPC command for PUCCH | ZTE, Qualcomm |
| R1-2101979 | CR on clarification of TPC command for PUCCH | ZTE, Qualcomm |
| R1-2101980 | CR on clarification of TPC command for PUCCH | ZTE, Qualcomm |
| R1-2101981 | Clarification on power control for NB-IoT | ZTE, Ericsson |
| R1-2101982 | Clarification on power control for NB-IoT | ZTE, Ericsson |
| R1-2101983 | Summary of email discussion [104-e-LTE-6.1CRs-02] on R1-2100559 (NB-IoT) | Moderator (ZTE) |
| R1-2101984 | Corrections on UCI multiplexing for partial PUSCH mode 1 | Samsung, Huawei, HiSilicon |
| R1-2101985 | Corrections on UCI multiplexing for partial PUSCH mode 1 | Samsung, Huawei, HiSilicon |
| R1-2101986 | Summary of [104-e-LTE-6.1CRs-04] on UCI multiplexing for partial PUSCH mode 1 | Moderator (Samsung) |
| R1-2102183 | Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2102184 | Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100560 | Clarification on DCI size alignment for MTC | ZTE |
| R1-2100561 | Corrections on scheduling enhancement for MTC | ZTE |
| R1-2100761 | Corrections on multicast gap in Multiple TB | Lenovo, Motorola Mobility |
| R1-2101279 | Corrections on multi-TB scheduling for eMTC | Huawei, HiSilicon |
| R1-2101702 | PUR maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2102037 | FL summary for PUR email [104-e-LTE-eMTC5-01] | Moderator (Sierra Wireless) |
| R1-2102038 | PUR correction on PUSCH Repetition Adjustment | Moderator (Sierra Wireless), Ericsson, Huawei, HiSilicon |
| R1-2102039 | PUR correction on PUSCH Repetition Adjustment and Zero Padding Procedures | Moderator (Sierra Wireless), Ericsson, Huawei, HiSilicon |
| R1-2102109 | PUR correction on PUSCH Repetition Adjustment | Moderator (Sierra Wireless), Ericsson, Huawei, HiSilicon, ZTE |
| R1-2102110 | PUR correction on PUSCH Repetition Adjustment and Zero Padding Procedures | Moderator (Sierra Wireless), Ericsson, Huawei, HiSilicon, ZTE |
| R1-2102157 | Correction on HARQ process number for SPS validation when multi-TB is configured | Moderator (Ericsson), ZTE, sanechips, Ericsson, Lenovo, Motorola Mobility |
| R1-2102203 | Correction on multicast gap in multi-TB scheduling in LTE-MTC | Moderator (Ericsson), Lenovo, Motorola mobility, Qualcomm, Ericsson, ZTE |
| R1-2102219 | FL summary for Multi-TB issues for Rel-16 LTE-MTC | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100562 | Clarification on DCI size alignment for NB-IoT | ZTE |
| R1-2100563 | Corrections on scheduling enhancement for NB-IoT | ZTE |
| R1-2101282 | Correction on transmission scheme for NPDSCH configured by PUR-RNTI | Huawei, HiSilicon |
| R1-2101703 | PUR maintenance issues for Rel-16 NB-IoT | Ericsson |
| R1-2102065 | Correction on determination of number of scheduled TB for SC-MTCH | Moderator (ZTE), Sanechips, Nokia, Ericsson, Lenovo, Motorola Mobility |
| R1-2102066 | Summary of email discussion [104-e-LTE-NB_IoTenh3-02] | Moderator (ZTE) |
| R1-2102210 | Correction on transmission scheme for NPDSCH configured by PUR-RNTI | Moderator (Huawei), Huawei, Hisilicon, ZTE, Sanechips, Ericsson |
| R1-2102211 | PUR correction on DCI size alignment | Moderator (Huawei), Huawei, Hisilicon, ZTE, Sanechips, Ericsson |
| R1-2102212 | PUR correction on parameter name for DL carrier | Moderator (Huawei), Huawei, Hisilicon, ZTE, Sanechips, Ericsson |
| R1-2102213 | Feature lead summary #1 on [104-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100320 | Draft CR to 36.214 on corrections for Reference Point for eNB Rx – Tx time difference | CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2100082 | Discussion on UL skipping for PUSCH | ZTE |
| R1-2100083 | Draft CR on Type-2 HARQ-ACK codebook in physical uplink shared channel | ZTE |
| R1-2100084 | Discussion on Ambiguity Issues for UE Features with Cross-Carrier Operation | ZTE |
| R1-2100283 | Discussion on closed-loop power control with an absolute TPC command | ZTE |
| R1-2100284 | Draft CR on closed-loop power control with an absolute TPC command | ZTE |
| R1-2100321 | Discussion on PUSCH skipping | CATT |
| R1-2100322 | Correction on HARQ-ACK transmission in PUCCH | CATT |
| R1-2100323 | Correction on HARQ-ACK transmission in PUCCH | CATT |
| R1-2100324 | Correction on HARQ-ACK transmission in PUSCH | CATT |
| R1-2100325 | Correction on HARQ-ACK transmission in PUSCH | CATT |
| R1-2100326 | Correction on UCI multiplexing with PUCCH overriding | CATT |
| R1-2100327 | Correction on HARQ-ACK/SR/CSI multiplexing in a PUCCH | CATT |
| R1-2100328 | Correction to UE CSI computation time | CATT |
| R1-2100329 | Correction on UE sounding procedure | CATT |
| R1-2100404 | Discussion on UE FG ambiguity in case of cross-carrier operation | vivo |
| R1-2100405 | Discussion on PUSCH skipping with overlapping UCI on PUCCH in Rel-16 | vivo |
| R1-2100406 | Draft CR for Msg3 retransmission power control | vivo |
| R1-2100407 | Draft CR on PUCCH closed loop power control | vivo |
| R1-2100580 | Clarification on back-to-back PUSCHs scheduling restriction in Rel-15 | MediaTek Inc. |
| R1-2100610 | Clarification on Numerology for Active DL and UL BWPs | MediaTek Inc. |
| R1-2100616 | Draft CR on prioritization between SRS and PUCCH | LG Electronics |
| R1-2100754 | PUSCH skipping with UCI (without LCH and PHY prioritization) (Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2100796 | Discussion on UL skipping for CG PUSCH | Spreadtrum Communications |
| R1-2101134 | 38.213 CR on DCI ordering in a search space set | Nokia, Nokia Shanghai Bell |
| R1-2101135 | Draft 38.212 CR on NNZC indicator field for type-II CSI reporting | MediaTek Inc. |
| R1-2101136 | Draft 38.214 CR on CSI request constraint per slot | MediaTek Inc. |
| R1-2101145 | Discussion on CG collision with UCI and DG | Ericsson |
| R1-2101160 | Discussion on Rel-15 beamswitchtiming capability reporting and QCL assumption for aperiodic TRS | vivo |
| R1-2101161 | Correction on QCL assumption for aperiodic TRS | vivo |
| R1-2101171 | Draft CR on configured grant based PUSCH | Samsung |
| R1-2101275 | Correction on the search space configuration of PUCCH-SCell | Huawei, HiSilicon |
| R1-2101339 | Clarification of FG3-5b with Cross Carrier Operation | Apple |
| R1-2101340 | Clarification on the PUSCH scheduling constraint in Rel-15 | Apple |
| R1-2101341 | Discussions on PUSCH skipping | Apple |
| R1-2101431 | Discussion on CSI-RS ambiguities | Qualcomm Incorporated |
| R1-2101432 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2101433 | Clarification on UE Features with Cross-Carrier Operation | Qualcomm Incorporated |
| R1-2101434 | Clarification on Cancellation due to SFI, PDSCH, or CSI-RS | Qualcomm Incorporated |
| R1-2101529 | Correction on MCS values for PT-RS time density determination in TS 38.214 | Sharp |
| R1-2101580 | Discussion on skipping vs UCI multiplexing on configured PUSCH | NTT DOCOMO, INC. |
| R1-2101722 | Draft CR on Type-1 HARQ-ACK for PDSCH repetition with different SCSs in DL and UL | Ericsson |
| R1-2101723 | Draft CR on Type-1 HARQ-ACK for PDSCH repetition with different SCSs in DL and UL | Ericsson |
| R1-2101739 | Discussion on remaining issues of UL skipping for CG PUSCH | Huawei, HiSilicon |
| R1-2101743 | Correction on PUSCH frequency hopping in 38.214 | Huawei, HiSilicon |
| R1-2101744 | Correction on out-of-order HARQ operation in 38.214 | Huawei, HiSilicon |
| R1-2101768 | RAN1#104-e preparation phase initial summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2101769 | RAN1#104-e preparation phase final summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2101861 | Summary of [104-e-NR-7.1CRs-09] Correction on UE sounding procedure | Moderator (CATT) |
| R1-2101888 | Summary of [104-e-NR-7.1CRs-06] Correction on MCS values for PT-RS time density determination in TS 38.214 | Moderator (Sharp) |
| R1-2101927 | CR on Type-1 HARQ-ACK for PDSCH repetition with different SCSs in DL and UL | Ericsson, Samsung |
| R1-2101928 | Moderator summary of Email discussion [104-e-NR-7.1CRs-14] | Moderator (Ericsson) |
| R1-2101929 | Summary of [104-e-NR-7.1CRs-04] Correction on the search space configuration of PUCCH-Scell | Moderator (Huawei) |
| R1-2101930 | Correction on MCS values for PT-RS time density determination in TS 38.214 | Sharp |
| R1-2101931 | Correction on MCS values for PT-RS time density determination in TS 38.214 | Sharp |
| R1-2101935 | Correction on the search space configuration of PUCCH-SCell | Huawei, HiSilicon |
| R1-2101936 | Correction on the search space configuration of PUCCH-SCell | Huawei, HiSilicon |
| R1-2101963 | Correction on UCI multiplexing with PUCCH overriding | CATT |
| R1-2101966 | Summary on [104-e-NR-7.1CRs-07] | Moderator (ZTE) |
| R1-2101967 | Summary of [104-e-NR-7.1CRs-08] Correction on UCI multiplexing with PUCCH overriding | Moderator (CATT) |
| R1-2101968 | Summary of [104-e-NR-7.1CRs-15] Draft CR on Type-2 HARQ -ACK codebook in physical uplink shared channel | Moderator (CATT) |
| R1-2101988 | Correction for cancellation due to PDSCH/CSI-RS/SFI | Qualcomm |
| R1-2101989 | Correction for cancellation due to PDSCH/CSI-RS/SFI | Qualcomm |
| R1-2101990 | Correction for cancellation due to PDSCH/CSI-RS/SFI | Qualcomm Incorporated |
| R1-2101991 | Correction for cancellation due to PDSCH/CSI-RS/SFI | Qualcomm Incorporated |
| R1-2101997 | Correction on UE sounding procedure | CATT, ZTE |
| R1-2102025 | Summary of [104-e-NR-7.1CRs-16] Draft CR for Msg3 retransmission power control for Rel-15 | Moderator (vivo) |
| R1-2102053 | Summary of [104-e-NR-7.1CRs-12] Discussion on CSI-RS ambiguities | Moderator (Qualcomm) |
| R1-2102085 | LS on Interpretation of UE Features in Case of Cross-Carrier Operation | RAN1, ZTE |
| R1-2102086 | Summary of [104-e-NR-7.1CRs-02] on Ambiguity Issues for UE Features with Cross-Carrier Operation | Moderator (ZTE) |
| R1-2102123 | Summary of email discussion [104-e-NR-7.1CRs-05]: clarification of cancellation due to SFI, PSDCH, or CSI-RS | Moderator (Qualcomm) |
| R1-2102152 | LS on numerology for active DL and UL BWPs | RAN1, MediaTek |
| R1-2102154 | Moderator summary on [104-e-NR-7.1CRs-09] Correction on UE sounding procedure (round 2) | Moderator (CATT) |
| R1-2102169 | Moderator summary of [104-e-NR-7.1CRs-17] 38.213 CR on DCI ordering in a search space | Moderator (Nokia) |
| R1-2102170 | 38.213 CR on DCI ordering in a search space set | Nokia, Nokia Shanghai Bell |
| R1-2102178 | 38.214 CR on CSI request constraint per slot | MediaTek Inc. |
| R1-2102179 | Summary for [104-e-NR-7.1CRs-11] Clarification on CSI request constraint per slot | Moderator (MediaTek) |
| R1-2102185 | Session notes for 7.1 (Maintenance of Release 15 NR) | Ad-hoc Chair (Samsung) |
| R1-2102225 | Summary of email discussion [104-e-NR-7.1CRs-03] on the clarification of PUSCH scheduling restriction | Moderator (Apple Inc.) |
| R1-2102246 | Summary of [104-e-NR-7.1CRs-01] Discussion on UL skipping for PUSCH for Rel-16 | Moderator (vivo) |
| R1-2102249 | LS on UL skipping for PUSCH in Rel-16 | RAN1, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2100256 | Alignment of notation | Ericsson |
| R1-2102232 | Alignment of notation | Ericsson |
| R1-2102233 | Alignment CR for TS 38.212 | Huawei |
| R1-2102234 | Editorial corrections for 38.213 | Samsung |
| R1-2102235 | Editorial corrections for 38.214 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2100243 | Correction on DMRS configuration for MsgA | Huawei, HiSilicon |
| R1-2101408 | FL summary on the maintenance of 2-step RACH | Moderator (ZTE) |
| R1-2101526 | Draft CR to 38.213 on corrections for 2-step RACH | Ericsson |
| R1-2101573 | Discussion on remaining issues on 2-step RACH | Spreadtrum Communications |
| R1-2101897 | Summary of email discussion for [104-e-NR-2step-RACH-01] | Moderator (ZTE) |
| R1-2101898 | Draft CR on DMRS configuration for MsgA in 38.214 | Moderator (ZTE) |
| R1-2101899 | Draft CR on transmission timing adjustment procedure in 38.213 | Moderator (ZTE) |
| R1-2101964 | CR on DMRS configuration for MsgA in 38.214 | Moderator (ZTE), Huawei, HiSilicon |
| R1-2101965 | CR on transmission timing adjustment procedure in 38.213 | Moderator (ZTE), Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2100071 | Text proposals on type-3 HARQ-ACK codebook and multi-PUSCH scheduling | ZTE, Sanechips |
| R1-2100072 | Remaining issue on the channel access for FBE | ZTE, Sanechips |
| R1-2100147 | Discussion on the remaining issues of channel access procedure | OPPO |
| R1-2100148 | Text proposals on type-3 HARQ-ACK codebook | OPPO |
| R1-2100199 | Maintenance on channel access procedures for NR Unlicensed | Huawei, HiSilicon |
| R1-2100240 | Maintenance on DL signals and channels for NR Unlicensed | Huawei, HiSilicon |
| R1-2100331 | Correction on Type-3 HARQ-ACK codebook | CATT |
| R1-2100332 | Correction on power control for HARQ-ACK transmission | CATT |
| R1-2100408 | Maintenance on HARQ operation for NR-U | vivo |
| R1-2100409 | TP on frequency hopping for NR-U configured grant | vivo |
| R1-2100628 | Remaining issues on NR-U | Intel Corporation |
| R1-2100818 | Maintenance of DL signals and channels for NR-U | Spreadtrum Communications |
| R1-2100890 | Remaining issues of channel access procedure and DL signals and channels for NR-U | LG Electronics |
| R1-2100891 | Remaining issues of HARQ procedure for NR-U | LG Electronics |
| R1-2101072 | Remaining issues on UL transmissions | ETRI |
| R1-2101172 | Correction on the condition to use Type 1 DL channel access | Samsung |
| R1-2101173 | Correction on the use of subCarrierSpacingCommon in NR-U | Samsung |
| R1-2101247 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2101283 | Feature Lead Summary on Channel Access Procedures for NR-U | Moderator (Nokia) |
| R1-2101284 | Corrections on Channel Access Procedures for NR-U | Nokia, Nokia Shanghai Bell |
| R1-2101304 | Corrections related to DL, UL, and channel access | Ericsson |
| R1-2101305 | Discussion on LS from RAN4 on measuring CSI-RS during SCell activation | Ericsson |
| R1-2101332 | Feature lead summary for enhancements to initial access procedures | Moderator (Charter Communications) |
| R1-2101435 | Invalid SSB in FBE | Qualcomm Incorporated |
| R1-2101530 | Correction to FDRA field description | Sharp |
| R1-2101531 | Correction on FBE COT definition | Sharp |
| R1-2101651 | Remaining issues for multi PUSCHs in NR-U | ASUSTeK |
| R1-2101652 | Remaining issues for CG PUSCH in NR-U | ASUSTeK |
| R1-2101671 | Correction on DL/UL channel access procedure for NR-U | WILUS Inc. |
| R1-2101770 | Feature lead summary#1 on NR-U HARQ and Multi-PUSCH maintenance | Moderator (Huawei) |
| R1-2101795 | Feature lead summary for Maintenance of UL Signals and Channels | Moderator (Ericsson) |
| R1-2101796 | FL summary for initial access signals and channels | Moderator (Qualcomm) |
| R1-2101797 | Preparation phase email discussion summary | Moderator (Qualcomm) |
| R1-2101828 | Feature lead summary#1 on NR-U CG | Moderator (vivo) |
| R1-2101872 | Feature lead summary for [104-e-NR-NRU-01] Email discussion/approval on DL signals and channels | Moderator (Lenovo) |
| R1-2101873 | Feature lead summary for [104-e-NR-NRU-05] Email discussion/approval on reply LS to R1-2100008 | Moderator (Lenovo) |
| R1-2101950 | Summary on [104-e-NR-NRU-04] Email discussion on editorial changes for init access, CG and UL | Moderator (Qualcomm) |
| R1-2101992 | Feature lead summary#2 on NR-U HARQ and Multi-PUSCH maintenance | Moderator (Huawei) |
| R1-2101993 | Correction of Type-3 HARQ-ACK codebook generation for a PDSCH with one transport block for a configuration with a maximum number of two TBs | Moderator (Huawei), CATT |
| R1-2101994 | Correction of UE reception of DL control when a DCI indicates a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH | Moderator (Huawei), CATT |
| R1-2101995 | Correction on PUCCH power control for enhanced Type-2 HARQ-ACK codebook and for Type-3 HARQ-ACK codebook | Moderator (Huawei), CATT |
| R1-2101996 | Correction on joint configuration of semi-static repetitions and multi-pusch scheduling | Moderator (Huawei), vivo, ASUSTeK, Lenovo |
| R1-2102009 | Correction on DM-RS presence with PDSCH mapping type B | Moderator (Lenovo), Huawei, Spreadtrum, ZTE, Ericsson |
| R1-2102010 | Correction on search space set group switching without channel occupancy duration field | Moderator (Lenovo), Ericsson, ZTE |
| R1-2102011 | Reply LS on measuring CSI-RS during SCell activation | RAN1, Lenovo |
| R1-2102040 | Correction on usage of subCarrierSpacingCommon for unlicensed | Moderator (Qualcomm), Samsung |
| R1-2102041 | Correction on description of FDRA field size in DCI 0_0 | Moderator (Qualcomm), Sharp, Ericsson |
| R1-2102042 | Correction on description of FDRA field size in DCI 0_1 | Moderator (Qualcomm), Sharp, Ericsson |
| R1-2102116 | Correction on LBT for consecutive UL transmission triggered by DL assingments | Moderator (Nokia), ETRI, WILUS, Huawei, HiSilicon |
| R1-2102117 | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy | Moderator (Nokia), Ericsson, Intel |
| R1-2102118 | Correction on Channel Occupancy Time for Semi-Static Channel Access | Moderator (Nokia), Sharp |
| R1-2102119 | Correction on Channel Access for Multi-Channel transmission | Moderator (Nokia), LGE, Huawei, HiSilicon |
| R1-2102120 | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy | Moderator (Nokia), Ericsson, Intel |
| R1-2102121 | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy in RAR | Moderator (Nokia), Ericsson, Intel |
| R1-2102133 | Feature Lead Summary#2 on Channel Access Procedures for NR-U | Moderator (Nokia) |
| R1-2102186 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2101259 | Discussion on inter-band DC for Rel-16 IAB | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2100135 | Draft TP on physical strucutre for NR sidelink | OPPO |
| R1-2100136 | Remaining open issues and corrections for physical layer procedure | OPPO |
| R1-2100137 | Remaining open issues and corrections for mode 1 and mode 2 RA | OPPO |
| R1-2100204 | Remaining details of sidelink resource allocation mode 2 | Huawei, HiSilicon |
| R1-2100333 | Discussion and TPs on sidelink synchronization mechanism and physical layer structure in NR V2X | CATT, GOHIGH |
| R1-2100334 | Discussion and TPs on resource allocation in NR V2X | CATT, GOHIGH |
| R1-2100335 | Discussion and TPs on physical layer procedures in NR V2X | CATT, GOHIGH |
| R1-2100410 | Maintenance on physical layer structure for NR sidelink | vivo |
| R1-2100411 | Maintenance on resource allocation mechanisms for NR sidelink | vivo |
| R1-2100412 | Maintenance on NR sidelink synchronization and procedures | vivo |
| R1-2100514 | Discussion on essential corrections in physical layer structure | LG Electronics |
| R1-2100515 | Discussion on essential corrections in resource allocation for Mode 1 and 2 | LG Electronics |
| R1-2100516 | Discussion on essential corrections in physical layer procedure | LG Electronics |
| R1-2100629 | Correction to FD-OCC for PSCCH | Intel Corporation |
| R1-2100630 | Corrections to Mode-2 resource allocation | Intel Corporation |
| R1-2100631 | Corrections to sidelink procedures | Intel Corporation |
| R1-2100734 | A remaining issue on Mode-1 resource allocation for NR sidelink | Fujitsu |
| R1-2100735 | Remaining issues on physical layer procedures for NR sidelink | Fujitsu |
| R1-2100799 | Remaining issues in NR sidelink mode 2 resource allocation | Spreadtrum Communications |
| R1-2100800 | Remaining issues on sidelink physical layer procedure | Spreadtrum Communications |
| R1-2100936 | Remaining issues on sidelink synchronization | ZTE, Sanechips |
| R1-2100937 | Remaining issues on mode1 | ZTE, Sanechips |
| R1-2100938 | The slot set for SL resource allocation procedure | ZTE, Sanechips |
| R1-2100945 | Remaining issues on resource allocation mode 2 | NEC |
| R1-2101073 | Remaining issues on resource allocation mode 2 for NR V2X | ETRI |
| R1-2101174 | Maintenance for NR Sidelink Physical Layer Structure | Samsung |
| R1-2101175 | Draft CR on Sidelink Physical Duration to Logical Slot Conversion | Samsung |
| R1-2101176 | Maintenance for NR Sidelink Mode 2 Operation | Samsung |
| R1-2101344 | Remaining Issues of Sidelink Physical Layer Procedures | Apple |
| R1-2101345 | Remaining Issue of Mode 1 Resource Allocation | Apple |
| R1-2101346 | Remaining Issues of Mode 2 Resource Allocation | Apple |
| R1-2101436 | Remaining Issues in Mode 1 Resource Allocation | Qualcomm Incorporated |
| R1-2101437 | Remaining Issues in Mode 2 Resource Allocation | Qualcomm Incorporated |
| R1-2101438 | Remaining Issues in Physical Layer Procedure | Qualcomm Incorporated |
| R1-2101532 | Remaining issues on physical layer structure and procedures for NR sidelink | Sharp |
| R1-2101533 | Remaining issues on resource allocation for NR sidelink | Sharp |
| R1-2101534 | Remaining issues on synchronization mechanism for NR sidelink | Sharp |
| R1-2101571 | Remaining issues on sidelink mode 2 | ASUSTeK |
| R1-2101581 | Maintenance for resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2101582 | Maintenance for sidelink synchronization and mode 2 | NTT DOCOMO, INC. |
| R1-2101583 | Maintenance for sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2101649 | Remaining issues on type-1 HARQ-ACK codebook considering multiple sidelink reosurce pools | ASUSTeK |
| R1-2101650 | Remaining issues on sidelink procedure | ASUSTeK |
| R1-2101707 | Draft_CR_TS38.212 | Ericsson |
| R1-2101708 | Draft_CR_TS38.213 | Ericsson |
| R1-2101709 | Draft_CR_TS38.306 | Ericsson |
| R1-2101732 | Correction on PSBCH payload generation | Huawei, HiSilicon |
| R1-2101733 | Correction on determination of PSFCH resources based on a set of configured PRBs | Huawei, HiSilicon |
| R1-2101759 | Remaining details for Resource allocation for sidelink - Mode 2 | Nokia, Nokia Shanghai Bell |
| R1-2101760 | Remaining details for Physical layer structure for sidelink | Nokia, Nokia Shanghai Bell |
| R1-2101800 | Feature lead summary #1 on AI 7.2.4 Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2101807 | Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2101808 | Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2101809 | Feature lead summary on Mode-2 resource allocation issues in Rel.16 5G V2X | Moderator (Intel Corporation) |
| R1-2101853 | Feature lead summary#1 for physical layer procedure aspects in AI 7.2.4 | Moderator (LG Electronics) |
| R1-2101921 | [Draft] LS on the resource reservation period | LG Electronics |
| R1-2101922 | LS on the resource reservation period | RAN1, LG Electronics |
| R1-2102017 | Reply LS on per-table MCS range for mode-2 | RAN1, OPPO |
| R1-2102034 | Reply LS on SL switching priority | RAN1, Xiaomi |
| R1-2102043 | Feature lead summary#1 for Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2102044 | Discussion for [104-e-NR-5G_V2X-01] SL max data rate | Moderator (Samsung) |
| R1-2102045 | [Draft] LS on maximum data rate for NR sidelink | Samsung |
| R1-2102069 | Corrections related to prioritization between uplink and sidelink | Moderator (LG Electroincs), ZTE, Sanechips, NTT DOCOMO, Huawei, HiSilicon, Ericsson |
| R1-2102070 | Corrections related to the sidelink resource reservation period | Moderator (LG Electroincs), Huawei, HiSilicon, Ericsson, Samsung, NTT DOCOMO, ZTE, Sanechips |
| R1-2102091 | Outcome of email discussion [104-e-NR-5G_V2X-04] | Moderator (Intel Corporation) |
| R1-2102092 | Correction to pre-emption condition for Mode-2 resource allocation | Moderator (Intel Corporation), Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO |
| R1-2102095 | Determination of indexes for slots for S-SS/PSBCH block transmission(s) | Moderator (CATT), ZTE, Sanechips, Qualcomm |
| R1-2102096 | Restrictions of the slots for S-SSB transmission/reception | Moderator (CATT), NTT DOCOMO, Huawei, HiSilicon, vivo, OPPO, MediaTek, ZTE, Sanechips |
| R1-2102097 | Clarification on Sidelink SSID | Moderator (CATT), Ericsson |
| R1-2102098 | Correction on Sidelink Broadcast channel | Moderator (CATT), Huawei, HiSilicon, Ericsson |
| R1-2102108 | Feature lead summary#3 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2102114 | [Draft] LS on SL HARQ-ACK reporting to the gNB | Ericsson |
| R1-2102115 | [Draft] Correction of SL HARQ-ACK information reporting to the gNB in Mode 1 | Moderator (Ericsson), NTT DOCOMO, OPPO, Ericsson |
| R1-2102129 | Feature lead summary #2 on AI 7.2.4 Sidelink synchronization mechanism | Moderator (CATT) |
| R1-2102135 | Correction of SL HARQ-ACK information reporting to the gNB in Mode 1 | Moderator (Ericsson), NTT DOCOMO, OPPO, Ericsson |
| R1-2102137 | LS on maximum data rate for NR sidelink | RAN1, Samsung |
| R1-2102176 | LS on SL HARQ-ACK reporting to the gNB | RAN1, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2100090 | Draft CR on resource allocation for uplink transmission with configured grant | ZTE |
| R1-2100091 | Remaining issues on intra-UE multiplexing in Rel-16 URLLC | ZTE |
| R1-2100092 | Discussion on the timing for secondary cell activation and deactivation | ZTE |
| R1-2100178 | Text proposal for intra UE prioritization timeline | OPPO |
| R1-2100179 | Remaining issues on scheduling and HARQ | OPPO |
| R1-2100180 | Remaining issues on DL SPS enhancement | OPPO |
| R1-2100265 | Intra-UE Multiplexing and Prioritization for Rel-16 URLLC | Ericsson |
| R1-2100266 | Maintenance of UCI for NR URLLC | Ericsson |
| R1-2100267 | Maintenance of Scheduling/HARQ for NR URLLC | Ericsson |
| R1-2100336 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2100337 | Remaining issues on UCI enhancements | CATT |
| R1-2100338 | Remaining issues on intra-UE prioritization | CATT |
| R1-2100413 | Maintenance on UCI enhancements | vivo |
| R1-2100414 | Maintenance on Scheduling/HARQ | vivo |
| R1-2100415 | Maintenance on intra-UE prioritization | vivo |
| R1-2100632 | On remaining details for handling CG-DG PUSCH overlaps | Intel Corporation |
| R1-2100736 | A remaining issue on timing for applying SCell activation or deactivation | Fujitsu |
| R1-2100756 | URLLC/IIoT PUSCH skipping (with LCH and/or PHY prioritization configured) | Nokia, Nokia Shanghai Bell |
| R1-2100792 | Remaining issues of PDCCH enhancements for URLLC | Spreadtrum Communications |
| R1-2100793 | Remaining issues of CG-PUSCH enhancements for URLLC | Spreadtrum Communications |
| R1-2100826 | Maintenance of Rel-16 URLLC intra-UE and inter-UE prioritization/ multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2100827 | Draft CRs on timing of SCell activation/deactivation for sub-slot PUCCH and number of PUCCHs with HARQ-ACK in a slot/sub-slot | Nokia, Nokia Shanghai Bell |
| R1-2100829 | PUSCH skipping | InterDigital, Inc. |
| R1-2100898 | PHR issues related to URLLC/IIOT WI | LG Electronics |
| R1-2100899 | Remaining issues of other aspects for URLLC/IIOT | LG Electronics |
| R1-2101091 | Correction on UE procedure for reporting HARQ-ACK | Xiaomi |
| R1-2101177 | Maintanence on PDCCH as PDSCH SLIV reference | Samsung |
| R1-2101178 | Maintanence on SPS PDSCH | Samsung |
| R1-2101179 | Draft CR on SPS release for PDSCH with aggregation | Samsung |
| R1-2101262 | Corrections on PDCCH enhancements | Huawei, HiSilicon |
| R1-2101263 | Remaining issues on UCI enhancements | Huawei, HiSilicon |
| R1-2101264 | PHY prioritization/multiplexing with consideration of UL skipping | Huawei, BUPT, China Southern Power Grid, HiSilicon |
| R1-2101347 | Remaining issues on UCI and PUSCH enhancements for eURLLC | Apple |
| R1-2101348 | PUSCH skipping considering physical layer priority & LCH based prioritization | Apple |
| R1-2101439 | Remaining issue on HARQ and scheduling for URLLC | Qualcomm Incorporated |
| R1-2101440 | Remaining issues on eCG enhancements for URLLC | Qualcomm Incorporated |
| R1-2101535 | Correction on inconsistence between TS 38.213 and TS 38.331 in terms of the dci-FormatsExt for NR URLLC | Sharp |
| R1-2101536 | Remaining issue on PDSCH rate matching for DCI format 1_0 for NR URLLC | Sharp |
| R1-2101584 | Corrections on UCI enhancement for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2101585 | Corrections on scheduling/HARQ for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2101586 | Corrections on enhanced configured grant transmission for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2101670 | Summary#1 on UCI enhancements for R16 URLLC | Moderator (OPPO) |
| R1-2101763 | Feature lead summary on PUSCH enhancements for NR eURLLC in AI 7.2.5 | Moderator (Apple Inc.) |
| R1-2101814 | Summary of email discussion on preparation phase for Rel-16 URLLC/IIoT | Moderator (Huawei) |
| R1-2101815 | Feature lead summary on PDCCH enhancements | Moderator (Huawei) |
| R1-2101824 | Summary on Others for URLLC and IIOT | Moderator (LG Electronics) |
| R1-2101825 | Summary of [104-e-NR-L1enh-URLLC-05] | Moderator (LG Electronics) |
| R1-2101840 | Summary #1 of the Remaining Issues on HARQ and Scheduling Enhancements for URLLC | Moderator (Qualcomm) |
| R1-2101841 | Summary#1 of email thread [104-e-NR-L1enh-URLLC-02] | Moderator (OPPO) |
| R1-2101881 | PUSCH skipping considering physical layer priority & LCH based prioritization | Apple |
| R1-2102104 | CR on Timing for secondary cell activation / deactivation with sub-slot PUCCH | Moderator (OPPO), CATT, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2102105 | CR on number of PUCCHs with HARQ-ACK in a slot | Moderator (OPPO), NTT DOCOMO, ZTE |
| R1-2102106 | Summary of email discussion [104-e-NR-L1enh-URLLC-03] on PUSCH enhancements for NR eURLLC | Moderator (Apple Inc.) |
| R1-2102107 | Correction on Part 2 CSI dropping for UCI multiplexing on PUSCH repetition Type B | Moderator (Apple Inc.) |
| R1-2102150 | [Draft] Reply LS on overlapped data and SR are of equal L1 priority | vivo |
| R1-2102151 | Email discussion summary on [104-e-NR-L1enh-URLLC-06] for intra-UE prioritization | Moderator (vivo) |
| R1-2102187 | Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) | Ad-hoc Chair (Samsung) |
| R1-2102216 | Final summary of [104-e-NR-L1enh-URLLC-05] | Moderator (LG Electronics) |
| R1-2102221 | Summary #1 of email discussion [104-e-NR-L1enh-URLLC-01] on remaining issues on PDCCH enhancements | Moderator (Huawei) |
| R1-2102222 | Correction on dci-FormatsExt in section 10.1 in TS 38.213 | Moderator (Huawei), Sharp |
| R1-2102223 | Correction on PDSCH resource mapping with RE symbol level granularity | Moderator (Huawei), Sharp |
| R1-2102227 | Summary of [104-e-NR-L1enh-URLLC-04] on remaining issues on Scheduling & HARQ enhancements | Moderator (Qualcomm) |
| R1-2102228 | Active time duration of NZP CSI-RS resource | Qualcomm Incorporated |
| R1-2102229 | Resolving collision with semi-static DL and SSB symbols | Qualcomm Incorporated |
| R1-2102230 | Correction on PUCCH resource determination in section 9.2.1 in TS 38.213 | Moderator (LG Electronics), Samsung |
| R1-2102244 | Reply LS on overlapped data and SR are of equal L1 priority | RAN1, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2100113 | Text proposals for default close loop index for different TRPs | OPPO |
| R1-2100114 | Text proposals for overlapping between uplink signals | OPPO |
| R1-2100115 | Text Proposals for Multi-beam Operation Enhancement | OPPO |
| R1-2100279 | Maintenance of multi-beam operation | ZTE |
| R1-2100280 | Draft CR on UL full power transmission Mode 1 | ZTE |
| R1-2100281 | Maintenance of Multi-TRP enhancements | ZTE |
| R1-2100298 | Maintenance on multi-TRP transmission | Lenovo, Motorola Mobility |
| R1-2100339 | Corrections to multi-beam operation | CATT |
| R1-2100340 | On remaining issues of multi-TRP/panel transmission | CATT |
| R1-2100416 | Maintenance on multi beam related issues | vivo |
| R1-2100417 | Maintenance on multi TRP | vivo |
| R1-2100418 | Maintenance on default QCL issues and multi TRP | vivo |
| R1-2100617 | Draft CR on multi-TRP/panel transmission | LG Electronics |
| R1-2100633 | Correction for multi TRP PDCCH prioritization | Intel Corporation |
| R1-2100634 | Draft CR for clarification of scheme 2a/2b | Intel Corporation |
| R1-2101180 | On maintenance of Rel.16 multi-beam operation | Samsung |
| R1-2101181 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2101182 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2101183 | On UL full power transmission | Samsung |
| R1-2101256 | Remaining issues for multi-TRP in Rel-16 | Huawei, HiSilicon |
| R1-2101271 | Corrections on Type II CSI reporting in Rel-16 | Huawei, HiSilicon |
| R1-2101272 | Corrections on Scell BFR in Rel-16 | Huawei, HiSilicon |
| R1-2101349 | Remaining issues on Rel-16 Multi-TRP enhancement | Apple |
| R1-2101441 | Remaining Issues on Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2101565 | Interoperation between cross-carrier scheduling and multiple TRPs | ASUSTeK |
| R1-2101688 | Draft CR on DL SPS based PDSCH repetitions | Ericsson |
| R1-2101690 | Maintenance for multi-DCI based multi-TRP in Rel-16 | Ericsson |
| R1-2101691 | Maintenance for single-DCI based multi-TRP in Rel-16 | Ericsson |
| R1-2101923 | Moderator summary of [104-e-NR-eMIMO-05] Email discussion/approval of a potential reply LS to R1-2100018 | Moderator (Nokia) |
| R1-2101924 | Reply LS on multi-TRP description in Stage-2 | RAN1, Nokia |
| R1-2102000 | CR on Default TCI state of Scheme 3 and Scheme 4 | Moderator (OPPO), ZTE |
| R1-2102001 | CR on DMRS | Moderator (OPPO), ZTE |
| R1-2102002 | CR on HARQ-ACK | Moderator (OPPO), vivo, CATT |
| R1-2102003 | CR on multi-TRP | Moderator (OPPO), LG Electronics, CATT, Intel |
| R1-2102004 | CR on PDSCH QCL | Moderator (OPPO), Apple |
| R1-2102012 | Summary of [104-e-NR-eMIMO-02] Email Discussion | Moderator (OPPO) |
| R1-2102013 | Summary of [104-e-NR-eMIMO-03] Email Discussion | Moderator (OPPO) |
| R1-2102014 | Summary of [104-e-NR-eMIMO-04] Email Discussion | Moderator (OPPO) |
| R1-2102020 | CR on L1-SINR based beam measurement | Moderator (Apple), CATT |
| R1-2102021 | Corrections on Scell BFR in Rel-16 | Moderator (Apple), Huawei, HiSilicon |
| R1-2102022 | Summary of [104-e-NR-eMIMO-01] Maintenance and TPs for Multi-beam | Moderator (Apple) |
| R1-2102188 | Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100341 | Draft TS38.213 CR on UE behavior of DRX group configuration | CATT |
| R1-2101258 | Remaining issues for Rel-16 UE power saving | Huawei, HiSilicon |
| R1-2101552 | Maintenance for Rel-16 UE power savings | Ericsson |
| R1-2102029 | Final Summary of Rel-16 UE power saving | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100127 | Text Proposals on NR Positioning | OPPO |
| R1-2100282 | Maintenance of NR positioning support | ZTE |
| R1-2100342 | Discussion and TP on remaining issues in NR positioning | CATT |
| R1-2100419 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2100552 | Draft CR on the usage of the term cell | Nokia, Nokia Shanghai Bell |
| R1-2100707 | Editorial CR on Rel-16 NR positioning | LG Electronics |
| R1-2101731 | Corrections to positioning SRS and higher layer parameters | Huawei, HiSilicon |
| R1-2101758 | Maintenance of NR positioning support | Ericsson |
| R1-2101831 | Summary on email discussion [104-e-NR-Pos-04] for R1-2100320 | Moderator (CATT) |
| R1-2101835 | Feature Leads Summary for NR Positioning Maintenance – AI 7.2.8 | Moderator (Intel Corporation), CATT, Ericsson, Qualcomm |
| R1-2101836 | Summary of E-mail Discussion [104-e-NR-Pos-01] | Moderator (Intel Corporation) |
| R1-2101882 | Corrections to 36.214 for Reference Point for eNB Rx – Tx time difference | CATT |
| R1-2101918 | Reply LS on Rel-16 NR Positioning Correction | RAN1, Huawei |
| R1-2101919 | Summary of E-mail Discussion [104-e-NR-Pos-02] | Moderator (Ericsson) |
| R1-2101925 | Summary of [104-e-NR-Pos-03] for the reply LS to R1-2100005 | Moderator (Huawei) |
| R1-2102026 | Output #1 for email discussion [104-e-NR-Pos-02] | Moderator (Ericsson) |
| R1-2102158 | CR for the configuration of semi-persistent SRS | Moderator (Ericsson), ZTE |
| R1-2102159 | CR for the configuration of DL-PRS as the spatial relation of periodic and semi-persistent positioning SRS | Moderator (Ericsson), vivo |
| R1-2102160 | CR for the configuration of SRS for positioning in SRS carrier switching | Moderator (Ericsson), Huawei, HiSilicon |
| R1-2102162 | CR on DL PRS resource indication in activation command for semi-persistent SRS for positioning and amount of DL PRS resource sets per TRP | Moderator (Intel Corporation), Nokia, Nokia Shanghai Bell, CATT |
| R1-2102163 | CR on timestamp reference in NR positioning measurement report | Moderator(Intel Corporation), vivo |
| R1-2102164 | CR on measurement gap configuration for NR positioning | Moderator (Intel Corporation), vivo, Huawei |
| R1-2102189 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| R1-2102205 | CR for the configuration of semi-persistent SRS | Moderator (Ericsson), ZTE |
| R1-2102206 | CR for the configuration of DL-PRS as the spatial relation of periodic and semi-persistent positioning SRS | Moderator (Ericsson), vivo |
| R1-2102207 | CR for the configuration of SRS for positioning in SRS carrier switching | Moderator (Ericsson), Huawei, HiSilicon |
| R1-2102251 | CR on DL PRS resource indication in activation command for semi-persistent SRS for positioning and amount of DL PRS resource sets per TRP | Moderator (Intel Corporation), Nokia, Nokia Shanghai Bell, CATT |
| R1-2102252 | CR on timestamp reference in NR positioning measurement report | Moderator (Intel Corporation), vivo |
| R1-2102253 | CR on measurement gap configuration for NR positioning | Moderator (Intel Corporation), vivo, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2100093 | Maintenance of Rel-16 MR-DC and CA | ZTE |
| R1-2100420 | Maintenance on MR-DC and CA enhancements | vivo |
| R1-2100584 | Remaining issues on Rel-16 uplink power control for supporting NR-NR dual-connectivity | MediaTek Inc. |
| R1-2100585 | Remaining issues on Rel-16 carrier aggregation | MediaTek Inc. |
| R1-2101442 | Remaining issue on NR-DC power-control | Qualcomm Incorporated |
| R1-2101443 | Remaining issues on SCell dormancy and cross-carrier scheduling | Qualcomm Incorporated |
| R1-2101553 | Maintenance for Rel-16 MR-DC and CA enhancements | Ericsson |
| R1-2101751 | Corrections on SCell dormancy in TS 38.212 | Huawei, HiSilicon |
| R1-2101771 | FL summary on support of unaligned frame boundary for R16 NR inter-band CA | Moderator (CMCC) |
| R1-2101792 | Moderator summary of MR DC-CA pre-meeting preparation phase | Moderator (Nokia) |
| R1-2102015 | Reply LS on TCI state indication at Direct SCell activation | RAN1, MediaTek |
| R1-2102155 | CR to 38.213 on PRACH handling for NR-DC power control | Moderator (Ericsson), MediaTek, Qualcomm |
| R1-2102156 | CR to 38.213 on HARQ-ACK priority determination for SCell dormancy indication | Moderator (Ericsson), ZTE |
| R1-2102190 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2102217 | [104-e-NR-MRDC-CA-02] Email discussion/approval on cross-carrier triggering scheduling and A-CSI RS triggering, and unaligned CA | Moderator (Nokia) |
| R1-2102218 | Additional timing delay for applying QCL relation on the PDSCH with cross-carrier scheduling with different SCS | Moderator (Nokia), MediaTek, Qualcomm |
| R1-2102240 | Summary of Email discussion [104-e-NR-MRDC-CA-01] | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100094 | Discussion on NR Rel-16 UE Features | ZTE |
| R1-2100140 | Correction for V2X UE feature list | OPPO |
| R1-2100522 | Remaining details of Rel-16 NR UE features | Ericsson |
| R1-2100554 | Discussion on NR Rel-16 UE features | LG Electronics |
| R1-2100635 | Remaining issue on UE features | Intel Corporation |
| R1-2101184 | On NR Rel.16 UE features | Samsung |
| R1-2101249 | Updates on NR UE Features | Nokia, Nokia Shanghai Bell |
| R1-2101273 | Remaining details of Rel-16 NR UE features | Huawei, HiSilicon |
| R1-2101342 | Discussions on NR Rel-16 UE features | Apple |
| R1-2101343 | Discussion on Rel-16 UE features for mobility enhancement | Apple |
| R1-2101444 | Discussion on NR Rel-16 UE features | Qualcomm Incorporated |
| R1-2101517 | Correction on half-DuplexTDD-CA-SameSCS-r16 | CATT |
| R1-2101587 | Remaining issues on Rel-16 NR UE features | NTT DOCOMO, INC. |
| R1-2101588 | Summary on UE features for two-step RACH | Moderator (NTT DOCOMO, INC.) |
| R1-2101589 | Summary on UE features for NR-U | Moderator (NTT DOCOMO, INC.) |
| R1-2101590 | Summary on UE features for URLLC/IIoT | Moderator (NTT DOCOMO, INC.) |
| R1-2101591 | Summary on UE features for NR positioning | Moderator (NTT DOCOMO, INC.) |
| R1-2101592 | Summary on UE features for MR-DC/CA | Moderator (NTT DOCOMO, INC.) |
| R1-2101593 | Summary on UE features for CLI/RIM | Moderator (NTT DOCOMO, INC.) |
| R1-2101594 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2101595 | Summary on NR UE features for others | Moderator (NTT DOCOMO, INC.) |
| R1-2101685 | Remaining issues on Rel-16 eMIMO UE features | vivo |
| R1-2101772 | Summary of UE features for 5G V2X | Moderator (AT&T) |
| R1-2101773 | Summary of UE features for eMIMO | Moderator (AT&T) |
| R1-2101774 | Summary of UE features for NR mobility enhancements | Moderator (AT&T) |
| R1-2101832 | Summary on [104-e-NR-UEFeature-NRU-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2101833 | Summary on [104-e-NR-UEFeature-URLLCIIoT-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2101834 | Summary on [104-e-NR-UEFeature-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2101939 | Reply LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN1, LG Electronics |
| R1-2102006 | Updated RAN1 UE features list for Rel-16 NR after RAN1#104-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2102007 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104-e | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2102047 | Summary of email discussion/approval [104-e-NR-UEFeatures-MobEnh-01] | Moderator (AT&T) |
| R1-2102048 | Summary of email discussion/approval [104-e-NR-UEFeatures-eMIMO-01] | Moderator (AT&T) |
| R1-2102049 | Summary of email discussion/approval [104-e-NR-UEFeatures-eMIMO-02] | Moderator (AT&T) |
| R1-2102050 | Summary of email discussion/approval [104-e-NR-UEFeatures-eMIMO-03] | Moderator (AT&T) |
| R1-2102051 | Summary of email discussion/approval [104-e-NR-UEFeatures-eMIMO-04] | Moderator (AT&T) |
| R1-2102052 | Session Notes of AI 7.2.11 | Ad-Hoc Chair (AT&T) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100087 | Remaining issues of Rel-16 UL Tx Switching | ZTE |
| R1-2100116 | Enhancement on uplink power control for M-TRP | OPPO |
| R1-2100117 | Text Proposals for Tx Switching between Two Uplink Carriers | OPPO |
| R1-2100330 | Correction on half-duplex operation in CA with unpaired spectrum | CATT |
| R1-2100505 | DRAFT38.213CR, Correction to the configuration of half duplex operation for unpaired spectrum in CA | Nokia, Nokia Shanghai Bell |
| R1-2100700 | Draft TP for half-duplex operation | ZTE |
| R1-2101162 | Draft CR on correction of RRC parameter name | vivo |
| R1-2101445 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2101554 | Maintenance for Rel-16 UL Tx Switching | Ericsson |
| R1-2101596 | Summary on Rel-16 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2101738 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2101752 | Corrections on CCS with different subcarrier spacings for PDCCH and PDSCH in TS 38.214 | Huawei, HiSilicon |
| R1-2101782 | Summary of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2102005 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2102057 | Correction on uplink Tx switching | Moderator (China Telecom), Huawei, HiSilicon |
| R1-2102058 | LS on uplink Tx switching | RAN1, China Telecom |
| R1-2102126 | Correction on uplink Tx switching | Moderator (China Telecom), ZTE, CATT |
| R1-2102149 | [104-e-NR-TxSwitching-01] Summary of email discussion on maintenance of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| TDoc | Title | Source |
|---|---|---|
| R1-2102191 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| R1-2102250 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100044 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2100063 | Discussions on Rel-17 Beam Management | InterDigital, Inc. |
| R1-2100118 | Enhancements on Multi-beam Operation | OPPO |
| R1-2100208 | Enhancements on multi-beam operation | Huawei, HiSilicon |
| R1-2100273 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2100285 | Enhancements on Multi-beam Operation | ZTE |
| R1-2100343 | Enhancements on multi-beam operation | CATT |
| R1-2100421 | Further discussion on multi beam enhancement | vivo |
| R1-2100534 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2100588 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2100618 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2100636 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2100737 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2100779 | Enhancements on multi-beam operations | AT&T |
| R1-2100783 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2100844 | Further enhancement on multi-beam operation | Sony |
| R1-2100949 | Discussion on multi-beam operation | NEC |
| R1-2100964 | Discussion on Enhancements for Multi-beam Operation | Asia Pacific Telecom, FGI |
| R1-2101005 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2101023 | Discussion on multi-beam operation | ASUSTeK |
| R1-2101032 | Enhancements on multi-beam operation | CMCC |
| R1-2101092 | Enhancements on multi-beam operation | Xiaomi |
| R1-2101185 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2101186 | Multi-Beam Enhancements | Samsung |
| R1-2101313 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2101350 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2101414 | Multi-beam Enhancements | Convida Wireless |
| R1-2101446 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2101597 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2101644 | Enhancements on Multi-Beam Operation | TCL Communication Ltd |
| R1-2101856 | Moderator summary#2 for multi-beam enhancement (round 1) | Moderator (Samsung) |
| R1-2101913 | Moderator summary#3 for multi-beam enhancement (round 2) | Moderator (Samsung) |
| R1-2101969 | Moderator summary#4 for multi-beam enhancement (round 2B) | Moderator (Samsung) |
| R1-2102008 | DRAFT LS on Agreements Pertaining to L1/L2-Centric Inter-Cell Mobility | Samsung |
| R1-2102054 | Moderator summary#5 for multi-beam enhancement (round 3) | Moderator (Samsung) |
| R1-2102112 | Moderator summary#6 for multi-beam enhancement (round 3B) | Moderator (Samsung) |
| R1-2102209 | LS on Agreements Pertaining to L1/L2-Centric Inter-Cell Mobility | RAN1, Samsung |
| R1-2102247 | DRAFT LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
| R1-2102248 | LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN1, Samsung |
| R1-2102257 | Moderator summary for [104-e-Post-R17-eMIMO-01] | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100038 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2100064 | Discussion on M-TRP Enhancements for PDCCH, PUCCH, and PUSCH | InterDigital, Inc. |
| R1-2100119 | Enhancements on Multi-TRP based enhancement for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2100209 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2100274 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2100286 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2100344 | Enhancements on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2100422 | Further discussion on enhancement of MTRP operation | vivo |
| R1-2100535 | On multi-TRP enhancements for PDCCH and PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2100582 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | MediaTek Inc. |
| R1-2100619 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2100637 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2100738 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2100784 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2100845 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2100950 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2100965 | Discussion on Enhancements on Multi-TRP for Uplink Channels | Asia Pacific Telecom, FGI |
| R1-2101006 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2101033 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2101093 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Xiaomi |
| R1-2101187 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2101351 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2101415 | Multi-TRP Enhancements for PDCCH, PUCCH and PUSCH | Convida Wireless |
| R1-2101447 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2101537 | Enhancements on Multi-TRP PUSCH | Sharp |
| R1-2101598 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2101653 | Discussion on enhancement on Multi-TRP PDCCH | ASUSTeK |
| R1-2101654 | On PDCCH, PUCCH and PUSCH enhancements | Ericsson |
| R1-2101662 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2101784 | Summary of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2101838 | Discussion Summary for mTRP PDCCH Reliability Enhancements | Moderator (Qualcomm) |
| R1-2101839 | Summary #2 of email discussions [104-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2101900 | Summary #2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2101954 | Summary #3 of email discussions [104-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2102060 | Summary #3 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100039 | Clarification on network synchronization for inter-cell multi-TRP operation | FUTUREWEI, InterDigital |
| R1-2100065 | Synchronization Analysis for M-TRP Inter-cell Operation and RRC Configurations | InterDigital, Inc. |
| R1-2100120 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2100210 | Enhancements on inter-cell multi-TRP operations in Rel-17 | Huawei, HiSilicon |
| R1-2100275 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2100287 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2100345 | Inter-cell operation for multi-TRP/panel | CATT |
| R1-2100423 | Further discussion on inter-cell MTRP operation | vivo |
| R1-2100620 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2100638 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2100785 | Discussion on enhancement multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2100846 | Considerations on inter-cell operation | Sony |
| R1-2100966 | Discussion of enhancements on Multi-TRP inter-cell operation | Asia Pacific Telecom, FGI |
| R1-2101007 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2101034 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2101094 | Enhancement on Inter-cell Multi-TRP operations | Xiaomi |
| R1-2101144 | Enhancement on Multi-TRP inter-cell operation | Ericsson |
| R1-2101188 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2101352 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2101448 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2101599 | Discussion on inter-cell multi-TRP operations | NTT DOCOMO, INC. |
| R1-2101829 | Feature lead summary on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2101934 | Feature lead summary#2 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2102084 | Feature lead summary#3 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100040 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2100066 | Discussion on M-TRP Beam Management Enhancements | InterDigital, Inc. |
| R1-2100121 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2100211 | Multi-panel reception for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2100276 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2100288 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2100346 | Enhancements on beam management for multi-TRP | CATT |
| R1-2100424 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2100589 | Enhancements on beam management for multi-TRP | MediaTek Inc. |
| R1-2100621 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2100639 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2100739 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2100780 | Enhancements on beam management for multi-TRP | AT&T |
| R1-2100786 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2100847 | Considerations on beam management for multi-TRP | Sony |
| R1-2100951 | Discussion on beam management for multi-TRP | NEC |
| R1-2100967 | Discussion of enhancements on beam management for Multi-TRP | Asia Pacific Telecom, FGI |
| R1-2101008 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2101026 | Discussion on beam management for multi-TRP | ASUSTeK |
| R1-2101035 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2101074 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2101095 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2101189 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2101353 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2101416 | On Per-TRP Beam Failure Recovery | Convida Wireless |
| R1-2101449 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2101568 | Discussion on beam management for multi-TRP | ITRI |
| R1-2101600 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2101686 | On beam management enhancements for simultaneous multi-TRP transmission with multi-panel reception | Ericsson |
| R1-2101775 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2101862 | Moderator summary on beam management for M-TRP (round 0) | Moderator (CATT) |
| R1-2101973 | Moderator summary on beam management for M-TRP (round 1) | Moderator (CATT) |
| R1-2102153 | Moderator summary on beam management for M-TRP (round 2) | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100041 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2100067 | Enhancements for M-TRP Transmission to Support HST-SFN in Rel-17 | InterDigital, Inc. |
| R1-2100122 | Enhancements on HST-SFN deployment | OPPO |
| R1-2100212 | Enhancements for high speed train for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2100289 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2100347 | Discussion on enhancements for HST-SFN deployment | CATT |
| R1-2100425 | Further discussion and evaluation on HST-SFN schemes | vivo |
| R1-2100622 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2100640 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2100787 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2100848 | Considerations on HST-SFN operation for multi-TRP | Sony |
| R1-2100952 | Discussion on HST-SFN deployment | NEC |
| R1-2100988 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2101009 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2101036 | Enhancements on HST-SFN deployment | CMCC |
| R1-2101143 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2101190 | Enhancements on HST-SFN | Samsung |
| R1-2101354 | Views on Rel-17 HST enhancement | Apple |
| R1-2101450 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2101601 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2101865 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2102056 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2102139 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2102214 | Summary#4 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100042 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2100068 | Flexible SRS Transmission and Antenna Switching | InterDigital, Inc. |
| R1-2100123 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2100213 | Enhancements on SRS for Rel-17 | Huawei, HiSilicon |
| R1-2100277 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2100290 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2100348 | Discussion on SRS enhancement for Rel-17 | CATT |
| R1-2100426 | Further discussion on SRS enhancement | vivo |
| R1-2100590 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2100623 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2100641 | Discussion on SRS enhancements | Intel Corporation |
| R1-2100788 | Considerations on SRS enhancement | Spreadtrum Communications |
| R1-2100849 | Considerations on SRS flexibility, coverage and capacity | Sony |
| R1-2100953 | Discussion on SRS enhancement | NEC |
| R1-2101010 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2101037 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2101096 | Discussion on SRS enhancements | Xiaomi |
| R1-2101191 | Enhancements on SRS | Samsung |
| R1-2101355 | Views on Rel-17 SRS enhancement | Apple |
| R1-2101451 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2101519 | SRS Performance and Potential Enhancements | Ericsson |
| R1-2101538 | Enhancements on SRS flexibility, coverage and capacity | Sharp |
| R1-2101602 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2101684 | Enhancements on SRS for coverage and capacity | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101783 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2101914 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2101917 | FL summary #3 on SRS enhancements | Moderator (ZTE) |
| R1-2102079 | FL summary #4 on SRS enhancements | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100043 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2100069 | CSI Enhancements for the Support of NCJT MTRP | InterDigital, Inc. |
| R1-2100124 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2100214 | CSI Enhancements for Rel-17 | Huawei, HiSilicon, China Unicom |
| R1-2100291 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2100349 | Further discussion on CSI enhancements for Rel-17 | CATT |
| R1-2100427 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2100536 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2100583 | CSI enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2100624 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2100642 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2100789 | Discussion on CSI enhancement for multi-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2100850 | Further considerations on CSI enhancements | Sony |
| R1-2100954 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2100989 | CSI enhancements for mTRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2101011 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2101038 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2101192 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2101356 | Views on Rel-17 CSI enhancement | Apple |
| R1-2101452 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2101603 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2101687 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | Ericsson |
| R1-2101857 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2101884 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei) |
| R1-2101885 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei) |
| R1-2101886 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei) |
| R1-2102061 | Summary of CSI enhancements for MTRP and FDD (Round 3) | Moderator (Huawei) |
| R1-2102062 | Summary of CSI enhancements for MTRP and FDD (Round 4) | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100070 | Further Results on Multi-Panel UE Performance in a Multi-TRP Deployment | InterDigital, Inc. |
| R1-2100278 | HARQ feedback of SPS PDSCH reception in multi-DCI based multiple TRPs | Lenovo, Motorola Mobility |
| R1-2100292 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2100350 | Evaluation of enhancements for multi-TRP | CATT |
| R1-2100428 | Discussion on IRC receiver performance | vivo |
| R1-2100537 | On FDD channel reciprocity in real-world scenarios | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101193 | Additional enhancements for multi-beam | Samsung |
| R1-2101274 | Further details on CSI Enhancements for Rel-17 | Huawei, HiSilicon, China Unicom |
| R1-2101318 | Additional simulation results on multi-beam operation | Ericsson |
| R1-2101497 | Further considerations for MIMO | Qualcomm Incorporated |
| R1-2101604 | Discussion on UL dense deployment | NTT DOCOMO, INC. |
| R1-2101761 | On FDD channel reciprocity in real-world scenarios | Fraunhofer IIS, Fraunhofer HHI |
| TDoc | Title | Source |
|---|---|---|
| R1-2102192 | Session notes for 8.2 (Study on supporting NR from 52.6 GHz to 71 GHz) | Ad-Hoc Chair (Ericsson) |
| R1-2102259 | TR 38.808 v101: Study on supporting NR from 52.6 GHz to 71 GHz | Intel Corporation |
| R1-2102260 | TR 38.808 v110: Study on supporting NR from 52.6 GHz to 71 GHz | Rapporteur (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100051 | Considerations on initial access for additional SCS in Beyond 52.6GHz | FUTUREWEI |
| R1-2100057 | Initial access enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100073 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100149 | Discusson on initial access aspects | OPPO |
| R1-2100200 | Initial access signals and channels for 52-71GHz band | Huawei, HiSilicon |
| R1-2100257 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2100299 | Some views on initial access aspects for 52.6-71GHz | CAICT |
| R1-2100370 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2100429 | Discussions on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2100541 | Initial access aspects | TCL Communication Ltd. |
| R1-2100607 | Initial access aspects for NR operations in 52.6-71 GHz | MediaTek Inc. |
| R1-2100643 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2100740 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2100781 | Further Discussion of Initial Access Aspects | AT&T |
| R1-2100825 | Discussion on initial access aspects for NR from 52.6GHz to 71GHz | Spreadtrum Communications |
| R1-2100836 | Discussions on initial access aspects | InterDigital, Inc. |
| R1-2100892 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2100939 | Discussion on initial access aspects supporting NR from 52.6 to 71GHz | NEC |
| R1-2101109 | On initial access aspects for NR from 52.6GHz to 71GHz | Xiaomi |
| R1-2101194 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101286 | Discussion on Initial access aspects for NR beyond 52.6 GHz | CEWiT |
| R1-2101306 | Initial Access Aspects | Ericsson |
| R1-2101372 | On Initial access signals and channels | Apple |
| R1-2101417 | Consideration for NR Initial Access from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2101453 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101605 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101672 | Discussion on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2101826 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2101827 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2101905 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2101970 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2101971 | Summary #4 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2102073 | [Draft] LS on beam switching gap for 60 GHz band | Intel Corporation |
| R1-2102202 | LS on beam switching gap for 60 GHz band | RAN1, Intel Corporation |
| R1-2102238 | Summary #5 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100058 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100074 | Discussion on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100150 | Discussion on PDCCH monitoring | OPPO |
| R1-2100241 | Enhancement on PDCCH monitoring | Huawei, HiSilicon |
| R1-2100258 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2100371 | PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2100430 | Discussions on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2100608 | PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2100644 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2100817 | Discussion on PDCCH monitoring enhancement for NR beyond 52.6 GHz | Spreadtrum Communications |
| R1-2100837 | Discussions on PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2100851 | PDCCH enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2100893 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2101110 | PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2101195 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101307 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2101321 | Discussion on PDCCH monitoring enhancements for NR above 52.6GHz | CEWiT |
| R1-2101373 | PDCCH monitoring enhancements for NR between 52.6GHz and 71 GHz | Apple |
| R1-2101418 | Consideration for PDCCH Monitoring for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2101454 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101606 | PDCCH monitoring enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101874 | Feature lead summary for [104-e-NR-52-71GHz-02] Email discussion/approval on PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2102142 | Feature lead summary#2 for [104-e-NR-52-71GHz-02] on PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2102242 | Feature lead summary#3 for [104-e-NR-52-71GHz-02] on PDCCH monitoring enhancements | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100059 | Enhancements to PUCCH formats 0/1/4 for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100075 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100151 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2100239 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2100259 | Enhancements for PUCCH formats | Nokia, Nokia Shanghai Bell |
| R1-2100372 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2100431 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2100487 | Discussion on PUCCH Channel enhancements | FUTUREWEI |
| R1-2100609 | PUCCH formats 0/1/4 enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2100645 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2100819 | Discussion on enhancements for PUCCH format 0/1/4 for above 52.6GHz | Spreadtrum Communications |
| R1-2100838 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2100894 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2101196 | Enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101308 | PUCCH enhancements | Ericsson |
| R1-2101374 | Enhancements for PUCCH formats 0/1/4 for NR between 52.6GHz and 71 GHz | Apple |
| R1-2101455 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101607 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101673 | Discussion on PUCCH enhancement for PUCCH format 0/1/4 | WILUS Inc. |
| R1-2101794 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2101916 | FL Summary#2 for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2102111 | FL Summary#3 for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2102127 | FL Summary#4 for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100052 | Beam management for shared spectrum access in Beyond 52.6GHz | FUTUREWEI |
| R1-2100060 | Beam-management enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100076 | Discussion on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100152 | Discussion on beam management | OPPO |
| R1-2100203 | Discussion on the beam management procedures for 52-71GHz band | Huawei, HiSilicon |
| R1-2100260 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2100373 | Beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2100432 | Discussions on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2100646 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2100839 | Discussions on beam management for new SCSs | InterDigital, Inc. |
| R1-2100852 | Beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2100895 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2101111 | Discussion on beam management in NR from 52.6 GHz to 71GHz | Xiaomi |
| R1-2101197 | Beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101309 | Beam Management for New SCSs | Ericsson |
| R1-2101375 | On beam management for new SCSs | Apple |
| R1-2101419 | On Beam Management for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2101456 | Beam management for new SCS for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101608 | Beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101895 | Discussion summary of [104-e-NR-52-71GHz-04] | Moderator (InterDigital, Inc.) |
| R1-2102016 | Discussion summary#2 of [104-e-NR-52-71GHz-04] | Moderator (InterDigital, Inc.) |
| R1-2102100 | Discussion summary#3 of [104-e-NR-52-71GHz-04] | Moderator (InterDigital, Inc.) |
| R1-2102144 | Discussion summary#4 of [104-e-NR-52-71GHz-04] | Moderator (InterDigital, Inc.) |
| R1-2102243 | Discussion summary#5 of [104-e-NR-52-71GHz-04] | Moderator (InterDigital, Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100050 | Considerations for higher SCS in Beyond 52.6 GHz | FUTUREWEI |
| R1-2100061 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100077 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100153 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2100201 | PDSCH/PUSCH enhancments for 52-71GHz band | Huawei, HiSilicon |
| R1-2100261 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2100300 | Discussions on PDSCH and PUSCH enhancements for 52.6-71GHz | CAICT |
| R1-2100374 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2100433 | Discussions on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2100553 | PT-RS enhancements for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2100605 | On Enhancements of PDSCH Reference Signals | MediaTek Inc. |
| R1-2100647 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2100741 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2100820 | Discussion on PDSCH and PUSCH enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2100840 | Discussions on PDSCH/PUSCH enhancements | InterDigital, Inc. |
| R1-2100853 | PDSCH/PUSCH enhancements for NR from 52.6GHz to 71GHz | Sony |
| R1-2100896 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2100940 | PDSCH enhancements on supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2101112 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2101198 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101310 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2101320 | Enhancements on Reference Signals for PDSCH/PUSCH for NR beyond 52.6 GHz | CEWiT |
| R1-2101330 | PDSCH-PUSCH Enhancement Aspects for NR beyond 52.6 GHz | Charter Communications |
| R1-2101376 | PDSCH/PUSCH enhancements for NR between 52.6GHz and 71 GHz | Apple |
| R1-2101457 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101609 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101674 | Discussion on PDSCH/PUSCH enhancements for NR beyond 52.6GHz | WILUS Inc. |
| R1-2101776 | Summary of PDSCH/PUSCH enhancements (Bandwidth/Timeline/Reference signals) | Moderator (vivo) |
| R1-2101780 | Discussions on PDSCH/PUSCH enhancements | InterDigital, Inc. |
| R1-2101799 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2101819 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2101858 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2101883 | Discussion summary #1 of [104-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2101958 | PDSCH-PUSCH Enhancement Aspects for NR beyond 52.6 GHz | Charter Communications |
| R1-2101972 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2102072 | Discussion summary #2 of [104-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2102080 | Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2102090 | [Draft] LS on the maximum/minimum channel bandwidth and channelization for NR operation in 52.6 to 71 GHz | vivo |
| R1-2102128 | LS on the maximum/minimum channel bandwidth and channelization for NR operation in 52.6 to 71 GHz | RAN1, vivo |
| R1-2102237 | Discussion summary #3 of [104-e-NR-52-71GHz-05] | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100053 | Considerations on channel access for shared spectrum Beyond 52.6 GHz | FUTUREWEI |
| R1-2100062 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2100078 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100154 | Discussion on channel access mechanism | OPPO |
| R1-2100202 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2100262 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2100301 | Discussions on channel access mechanism for 52.6G-71 GHz | CAICT |
| R1-2100375 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2100434 | Discussions on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2100542 | Channel access mechanism | TCL Communication Ltd. |
| R1-2100648 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2100742 | Considerations on channel access mechanism for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2100755 | Channel access for multi-beam operation | PANASONIC |
| R1-2100782 | Further Discussion of Channel Access Mechanisms | AT&T |
| R1-2100821 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2100841 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2100854 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2100897 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2100941 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2101113 | Channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2101199 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101311 | Channel Access Mechanisms | Ericsson |
| R1-2101331 | Channel access mechanisms | Charter Communications |
| R1-2101377 | Channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2101420 | On Channel Access Mechanism for Extending Current NR to 71 GHz | Convida Wireless |
| R1-2101458 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101569 | Discussion on LBT mode | ITRI |
| R1-2101610 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101798 | FL summary on channel access mechanism for 60GHz band | Moderator (Qualcomm) |
| R1-2101887 | Email discussion summary for channel access for 52.6-71GHz | Moderator (Qualcomm) |
| R1-2101942 | Email discussion summary#2 for channel access for 52.6-71GHz | Moderator (Qualcomm) |
| R1-2102081 | Email discussion summary#3 for channel access for 52.6-71GHz | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100079 | Evaluation results for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2100155 | Discussion on other aspects | OPPO |
| R1-2100263 | Simulation Results | Nokia, Nokia Shanghai Bell |
| R1-2100435 | Discussions on frequency range definition for 52.6-71GHz | vivo |
| R1-2100842 | Efficient beam management based on FR2 | InterDigital, Inc. |
| R1-2101200 | Discussion on the synchronization raster for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2101268 | Link level and system evaluation results for 52-71 GHz | Huawei, HiSilicon |
| R1-2101312 | NR channelization for 52.6 - 71 GHz band | Ericsson |
| R1-2101498 | Other aspects of NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2101611 | Potential enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2101820 | Evaluation results for 52.6 to 71GHz | ZTE, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R1-2101689 | Revised Rel-17 NR IIoT/URLLC Work Plan | Nokia (Rapporteur) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100101 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2100181 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2100226 | UE feedback enhancements for HARQ-ACK | Huawei, BUPT, China Southern Power Grid, HiSilicon |
| R1-2100268 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2100302 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2100376 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2100436 | HARQ-ACK enahncements for Rel-17 URLLC | vivo |
| R1-2100574 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2100649 | UE HARQ feedback enhancements for URLLC/IIoT | Intel Corporation |
| R1-2100728 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2100803 | Discussion on physical Layer feedback enhancements | Spreadtrum Communications |
| R1-2100855 | Considerations on HARQ-ACK enhancements for URLLC | Sony |
| R1-2100880 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2100911 | Discussion on UE feedback enhancements for HARQ-ACK | China Telecom |
| R1-2100920 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2100948 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2100968 | Discussion on UE feedback enhancements for HARQ-ACK | Asia Pacific Telecom, FGI |
| R1-2100993 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2101013 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic Corporation |
| R1-2101039 | Discussion on UE feedback enhancements for HARQ-ACK | CMCC |
| R1-2101075 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2101114 | UE feedback enhancement for HARQ-ACK | Xiaomi |
| R1-2101201 | On HARQ-ACK reporting enhancements | Samsung |
| R1-2101290 | HARQ-ACK enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2101378 | Views on UE feedback enhancements for HARQ-ACK | Apple |
| R1-2101459 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2101539 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2101612 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2101675 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | WILUS Inc. |
| R1-2101817 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2101818 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100037 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2100102 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2100182 | CSI feedback enhancements for URLLC | OPPO |
| R1-2100227 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2100269 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2100377 | CSI feedback enhancements | CATT |
| R1-2100437 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2100575 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2100650 | CSI feedback enhancements for URLLC/IIoT | Intel Corporation |
| R1-2100790 | Discussion on CSI feedback enhancements | Spreadtrum Communications |
| R1-2100830 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2100835 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2100856 | Considerations on CSI feedback enhancements | Sony |
| R1-2100881 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2100994 | CSI feedback enhancements for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2101014 | Discussion on CSI feedback enhancements | Panasonic Corporation |
| R1-2101040 | Discussion on CSI feedback enhancements for URLLC | CMCC |
| R1-2101202 | Improving MCS Selection for URLLC | Samsung |
| R1-2101379 | Views on CSI feedback enhancements | Apple |
| R1-2101460 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2101613 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2101811 | Feature lead summary #1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2101879 | Feature lead summary #2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2101961 | Feature lead summary #3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2102131 | Feature lead summary #4 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100054 | Further considerations on UE initiated COT for FFP | FUTUREWEI |
| R1-2100103 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2100183 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2100229 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, BUPT, China Southern Power Grid, HiSilicon |
| R1-2100270 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2100378 | Enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2100438 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2100543 | Enhancements for unlicensed band URLLC/IIoT | TCL Communication Ltd. |
| R1-2100576 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2100626 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2100651 | Discussion on enhancements to URLLC/IIoT in unlicensed band | Intel Corporation |
| R1-2100691 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2100791 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2100857 | Considerations on unlicensed URLLC | Sony |
| R1-2100882 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2100995 | Enhancements for unlicensed band IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2101015 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2101076 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2101115 | Enhancement for unlicensed band URLLC/IIoT | Xiaomi |
| R1-2101203 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2101291 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2101333 | Unlicensed spectrum operation for URLLC/IIoT | Charter Communications |
| R1-2101380 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2101461 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2101540 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2101614 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2101676 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2101830 | Summary#1 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| R1-2101902 | Summary#2 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| R1-2101955 | Summary#3 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| R1-2102064 | Summary#4 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| R1-2102173 | Summary#5 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| R1-2102175 | Summary#6 - URLLC/IIoT operation on Unlicensed Band | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100104 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2100184 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2100228 | Intra-UE multiplexing enhancements | Huawei, BUPT, China Southern Power Grid, HiSilicon |
| R1-2100271 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2100303 | Considerations of intra UE multiplexing | CAICT |
| R1-2100379 | Intra-UE multiplexing and prioritization | CATT |
| R1-2100439 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2100577 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2100652 | Considerations on intra-UE multiplexing and prioritization | Intel Corporation |
| R1-2100692 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2100729 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2100804 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2100831 | Intra-UE Multiplexing/Prioritization | InterDigital, Inc. |
| R1-2100858 | Considerations on intra-UE UL multiplexing | Sony |
| R1-2100883 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2100921 | Intra-UE Multiplexing and Prioritization | TCL Communication Ltd. |
| R1-2100970 | Discussion on Intra-UE multiplexing/prioritization | Asia Pacific Telecom, FGI |
| R1-2100996 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2101016 | Discussion on Intra-UE multiplexing and prioritization of different priority | Panasonic Corporation |
| R1-2101041 | Discussion on intra-UE multiplexing or prioritization | CMCC |
| R1-2101077 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2101116 | Intra-UE multiplexing prioritization for URLLC/IIoT | Xiaomi |
| R1-2101204 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2101381 | Views on Intra-UE Multiplexing/Prioritization | Apple |
| R1-2101462 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2101541 | Enhancements on intra-UE UCI multiplexing and PUSCH prioritization | Sharp |
| R1-2101570 | Discussion on intra-UE multiplexing | ITRI |
| R1-2101615 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2101677 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2101842 | Summary#1 of email thread [104-e-NR-R17-IIoT_URLLC-04] | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100105 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2100185 | Enhancements for Propagation Delay Compensation | OPPO |
| R1-2100272 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2100380 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2100440 | Discussion on propagation delay compensation enhancements | vivo |
| R1-2100578 | Discussion on propagation delay compensation for time synchronization | MediaTek Inc. |
| R1-2100653 | Propagation delay compensation analysis and design considerations | Intel Corporation |
| R1-2100730 | Discussion on enhancements for propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2100884 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2101078 | Propagation delay compensation enhancements | ETRI |
| R1-2101205 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2101265 | Enhancements for support of time synchronization | Huawei, BUPT, China Southern Power Grid, HiSilicon |
| R1-2101382 | Orphan symbol treatment in unlicensed spectrum access | Apple |
| R1-2101463 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2101816 | Feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2101896 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2102224 | Draft LS on UE transmit timing error | Huawei |
| R1-2102245 | LS on UE transmit timing error | RAN1, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2102193 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100156 | Discusson on timing relationship enhancement | OPPO |
| R1-2100222 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2100244 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2100304 | Timing relationship enhancements to support NTN | CAICT |
| R1-2100381 | Timing relationship enhancement for NTN | CATT |
| R1-2100441 | Discussion on timing relationship enhancements for NR-NTN | vivo |
| R1-2100496 | Timing relationship enhancements for NTN | Zhejiang Lab |
| R1-2100594 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2100654 | On timing relationship enhancements for NR NTN | Intel Corporation |
| R1-2100703 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2100757 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2100807 | Consideration on timing relationship enhancements | Spreadtrum Communications |
| R1-2100859 | Calculation of timing relationship offsets | Sony |
| R1-2100912 | Discussion on Timing Relationship Enhancements in NR-NTN | China Telecom |
| R1-2100922 | On timing relationship enhancements for NTN | Ericsson |
| R1-2100971 | Timing relationship enhancements in NTN | Asia Pacific Telecom, FGI, III, ITRI |
| R1-2100984 | On timing relationship for NTN | InterDigital, Inc. |
| R1-2101024 | NTN Timing relationship enhancement | Panasonic Corporation |
| R1-2101042 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2101117 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2101206 | Timing relationship enhancements for NTN | Samsung |
| R1-2101296 | Further views on DL-UL timing relationship for NTN operation | Nokia, Nokia Shanghai Bell |
| R1-2101383 | Enhancement on Timing Relationship in NTN | Apple |
| R1-2101464 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2101616 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2101694 | Discussion on Timing Relationship Enhancements for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101793 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2101904 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2102019 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2102078 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100157 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2100223 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2100245 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2100305 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2100382 | UL time and frequency compensation for NTN | CATT |
| R1-2100442 | Discussion on UL time and frequency synchronization enhancements for NR-NTN | vivo |
| R1-2100520 | Considerations on UL timing and frequency synchronization in NR NTN | THALES |
| R1-2100540 | UL time synchronization acquisition for NTN | Mitsubishi Electric RCE |
| R1-2100595 | UE Time and frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2100655 | On UL synchronization for NR NTN | Intel Corporation |
| R1-2100704 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2100758 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2100808 | Consideration on enhancements on UL time and frequency synchronization | Spreadtrum Communications |
| R1-2100860 | Enhancement for UL time synchronization | Sony |
| R1-2100927 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2100972 | UL time and frequency synchronization in NTN | Asia Pacific Telecom, FGI |
| R1-2100985 | On UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2101043 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2101079 | Discussion on UL timing synchronization for NTN | ETRI |
| R1-2101118 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2101207 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2101297 | Time and frequency synchronization for NTN systems | Nokia, Nokia Shanghai Bell |
| R1-2101384 | Discussion on Uplink Time and Frequency Synchronization for NTN | Apple |
| R1-2101465 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2101648 | Discussion on UL time and frequency synchronization for NTN | PANASONIC R&D Center Germany |
| R1-2101716 | UL time synchronization methods for NTN systems | CEWiT, IITM, IITH, Tejas Networks |
| R1-2101717 | UL time synchronization methods for NTN systems | CEWiT, IITM, IITH, Tejas Networks, Reliance Jio |
| R1-2101805 | FL Summary#1 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2101871 | FL Summary#2 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2101938 | FL Summary#3 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2102028 | FL Summary#4 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2102140 | FL Summary#5 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2102182 | FL Summary#6 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2102215 | FL Summary#7 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2102263 | LS on NTN UL time and frequency synchronization requirements | RAN1, Thales |
| R1-2102264 | Moderator summary for [104-e-Post-R17-NTN-01] Email discussion on LS to RAN4 on NTN UL time and frequency synchronization requirements | Moderator (Thales) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100158 | Discussion on HARQ enhancement | OPPO |
| R1-2100224 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2100246 | Discussion on HARQ for NR-NTN | ZTE |
| R1-2100306 | Enhancements on HARQ to support NTN | CAICT |
| R1-2100383 | HARQ operation enhancement for NTN | CATT |
| R1-2100443 | Discussion on HARQ enhancements for NR-NTN | vivo |
| R1-2100485 | INTELLIGENT PACKET REPETITION IN MOBILE SATELLITE SERVICE (MSS) LINKS TO OVERCOME CHANNEL BLOCKAGES | Ligado Networks |
| R1-2100491 | Discussion on HARQ enhancement for NTN | BUPT |
| R1-2100596 | HARQ in NR-NTN | MediaTek Inc. |
| R1-2100656 | On HARQ enhancements for NR NTN | Intel Corporation |
| R1-2100705 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2100759 | Enhancements on HARQ for NTN | Lenovo, Motorola Mobility |
| R1-2100809 | Consideration on enhancements on HARQ | Spreadtrum Communications |
| R1-2100861 | Enhancements on HARQ for NTN | Sony |
| R1-2100913 | Discussion on HARQ Enhancements in NR-NTN | China Telecom |
| R1-2100928 | On HARQ enhancements for NTN | Ericsson |
| R1-2100973 | Enhancements on HARQ in NTN | Asia Pacific Telecom, FGI |
| R1-2100986 | On HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2101025 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2101044 | Enhancements on HARQ for NTN | CMCC |
| R1-2101080 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2101119 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2101208 | Enhancements on HARQ for NTN | Samsung |
| R1-2101289 | Discussion on HARQ for NTN | THALES |
| R1-2101298 | On HARQ operation for NTN systems | Nokia, Nokia Shanghai Bell |
| R1-2101385 | Discussion on HARQ Enhancements for NTN | Apple |
| R1-2101466 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2101781 | Summary of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2101903 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2102055 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2102143 | Summary#4 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100159 | Discussion on other aspects | OPPO |
| R1-2100247 | Discussion on additional enhancement for NR-NTN | ZTE |
| R1-2100264 | IoT NTN Observations and Proposals | Lockheed Martin |
| R1-2100307 | Discusson on beam management of NTN | CAICT |
| R1-2100384 | Beam management and other aspects for NTN | CATT |
| R1-2100444 | Discussion on other aspects for NR-NTN | vivo |
| R1-2100597 | Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2100598 | Summary #1 of 8.4.4 Other Aspects of NR-NTN | MediaTek Inc. |
| R1-2100706 | Discussions on other aspects of NTN | LG Electronics |
| R1-2100723 | Discussion on channel models for marine and inland river scenes | GDCNI |
| R1-2100760 | Discussion on other aspects for NTN | Lenovo, Motorola Mobility |
| R1-2100862 | Discussion on beam management and polarization for NTN | Sony |
| R1-2100929 | On other enhancements for NTN | Ericsson |
| R1-2100974 | Scrambling sequence enhancement in NTN | Asia Pacific Telecom, FGI, ITRI |
| R1-2100987 | On feeder link switch and beam management for NTN | InterDigital, Inc. |
| R1-2101045 | Other Aspects for NTN | CMCC |
| R1-2101120 | Discussion on other design aspects for NTN | Xiaomi |
| R1-2101209 | Remaining issues for NTN | Samsung |
| R1-2101260 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2101288 | Beam management and BWP operation in NTN | THALES |
| R1-2101295 | SSB, beam management and polarization signaling for NTN | PANASONIC |
| R1-2101299 | Additional aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101386 | Other Aspects of NR NTN | Apple |
| R1-2101467 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2101693 | Discussion on Beam Management for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101806 | Summary #1 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2101901 | Summary #1 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2101952 | [Draft] Reply LS on AN-PDB and PER targets for satellite access | Qualcomm |
| R1-2101960 | Summary #2 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2102033 | Summary #2 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2102074 | Reply LS on AN-PDB and PER targets for satellite access | RAN1, Qualcomm |
| R1-2102141 | Summary #3 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2102194 | Session notes for 8.5 (Study on NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2102261 | TR 38.857 v101: Study on NR positioning enhancements | Ericsson |
| R1-2102262 | TR 38.857 v110: Study on NR positioning enhancements | Ericsson |
| R1-2102267 | TR 38.857 v110: Study on NR positioning enhancements | Rapporteur (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100128 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2100195 | Enhancement to mitigate gNB and UE Rx/Tx timing error | Huawei, HiSilicon |
| R1-2100293 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2100308 | Disussion on accuracy improvements of NR positioning enhancements | CAICT |
| R1-2100385 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | CATT |
| R1-2100445 | Discussion on methods for RX/TX timing delay mitigating | vivo |
| R1-2100548 | Initial views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2100657 | Mitigation of UE and gNB Tx/Rx timing errors | Intel Corporation |
| R1-2100697 | Positioning enhancement by UE Assistance | TCL Communication Ltd. |
| R1-2100708 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2100752 | Techniques to improve accuracy in the presence of UE Rx/Tx and/or gNB Rx/Tx timing delays | InterDigital, Inc. |
| R1-2101046 | Discussion on gNB/UE Rx/Tx timing delay mitigation solutions | CMCC |
| R1-2101131 | On methods for Rx/Tx timing delays mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101140 | The mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2101210 | Discussion on accuracy improvements on timing based positioning solutions | Samsung |
| R1-2101387 | Positioning accuracy enhancements under UE and/or gNB Tx/Rx timing errors | Apple |
| R1-2101468 | Enhancements on Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2101527 | NR positioning enhancements by mitigating timing delays | China Telecom |
| R1-2101754 | Techniques mitigating UE Rx/Tx timing delays | Ericsson |
| R1-2101764 | FL summary of accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2101951 | FL summary#2 of accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2102035 | FL summary#3 of accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2102122 | FL summary#4 of accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2102201 | [DRAFT] LS on UE/TRP Tx/Rx Timing Errors | CATT |
| R1-2102204 | FL summary#5 of accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100129 | Enhancements for UL AoA Positioning | OPPO |
| R1-2100237 | Enhancement for UL AoA positioning | Huawei, HiSilicon |
| R1-2100294 | Accuracy improvement for UL-AoA positioning solutions | ZTE |
| R1-2100386 | Discussion on accuracy improvements for UL-AoA positioning solutions | CATT |
| R1-2100446 | Discussion on potential enhancements for UL-AoA method | vivo |
| R1-2100488 | Discussion on improving the accuracy of UL AoA positioning solutions | FUTUREWEI |
| R1-2100497 | Accuracy improvements for UL-AoA positioning solutions | BUPT |
| R1-2100549 | Initial views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2100658 | NR positioning enhancements for UL-AoA method | Intel Corporation |
| R1-2100659 | NR positioning enhancements for DL-AoD method | Intel Corporation |
| R1-2100709 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2100753 | Discussions on techniques to improve accuracy for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2100863 | Discussion on accuracy improvements for UL-AoA positioning method | Sony |
| R1-2101047 | Discussion on UL-AoA enhancement | CMCC |
| R1-2101132 | UL-AoA positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101211 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2101388 | Accuracy enhancements for DL-AoD positioning technique | Apple |
| R1-2101469 | Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2101617 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2101755 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2101859 | Feature Lead Summary #1 for NR Positioning UL-AoA Enhancements | Moderator (Intel Corporation) |
| R1-2101860 | Feature Lead Summary #2 for NR Positioning UL-AoA Enhancements | Moderator (Intel Corporation) |
| R1-2102036 | Feature Lead Summary #3 for NR Positioning UL-AoA Enhancements | Moderator (Intel Corporation) |
| R1-2102046 | Feature Lead Summary #4 for NR Positioning UL-AoA Enhancements | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100130 | Enhancements for DL-AoD positioning | OPPO |
| R1-2100238 | Enhancement for DL AoD positioning | Huawei, HiSilicon |
| R1-2100295 | Accuracy improvements for DL-AoD positioning solutions | ZTE |
| R1-2100387 | Discussion on accuracy improvements for DL-AoD positioning solutions | CATT |
| R1-2100447 | Discussion on potential enhancements for DL-AoD method | vivo |
| R1-2100489 | Discussion on improving the accuracy of DL AoD positioning solutions | FUTUREWEI |
| R1-2100550 | Initial views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2100710 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2100750 | Accuracy improvements for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2100864 | Discussion on accuracy improvements for DL-AoD positioning method | Sony |
| R1-2101048 | Discussion on DL-AoD enhancement | CMCC |
| R1-2101121 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2101133 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101141 | Accuracy enhancement for DL-AOD technique | MediaTek Inc. |
| R1-2101212 | Accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2101389 | Accuracy enhancements for UL-AoA positioning technique | Apple |
| R1-2101470 | Potential Enhancements on DL-AoD positioning | Qualcomm Incorporated |
| R1-2101501 | Potential DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2101618 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2101756 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2101920 | FL summary for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2102027 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2102093 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2102181 | FL summary #4 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2102239 | FL summary #5 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100131 | Discussion on NR Positioning Enhancements | OPPO |
| R1-2100296 | Other accuracy enhancements for NR positioning | ZTE |
| R1-2100388 | Potential techniques for Rel-17 positioning enhancements | CATT |
| R1-2100448 | Discussion on idle and inactive states positioning | vivo |
| R1-2100551 | Additional views on positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2100711 | Discussion on latency and efficiency enhancement for NR positioning | LG Electronics |
| R1-2100751 | Discussions on LOS/NLOS detection | InterDigital, Inc. |
| R1-2101142 | Solving the synchronization error by the combination of measurements for DL-TDOA and UL-TDOA | MediaTek Inc. |
| R1-2101213 | Discussion on differential beamforming for positioning enhancement | Samsung |
| R1-2101252 | Considerations on other enhancements for positioning accuracy | Huawei, HiSilicon |
| R1-2101499 | Other asprects of positioning enhancements | Qualcomm Incorporated |
| R1-2101757 | PRS with Cyclic shifts | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2100033 | WI work plan for RedCap | Rapporteur (Ericsson) |
| R1-2102220 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2102269 | TR 38.875 v1.1.0: Study on support of reduced capability NR devices; for information | Ericsson |
| R1-2102270 | TR 38.875 v1.1.0: Study on support of reduced capability NR devices; for information | Rapporteur (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100034 | UE complexity reduction for RedCap | Ericsson |
| R1-2100046 | Complexity reduction features for RedCap UEs | FUTUREWEI |
| R1-2100165 | Discussion on UE complexity reduction | OPPO |
| R1-2100230 | Potential solutions for UE complexity reduction | Huawei, HiSilicon |
| R1-2100389 | Discussion on UE complexity reduction features | CATT |
| R1-2100449 | Discussion on UE Complexity reduction | vivo, Guangdong Genius |
| R1-2100499 | UE complexity reduction | Nokia, Nokia Shanghai Bell |
| R1-2100564 | UE complexity reduction for Reduced Capability NR devices | ZTE |
| R1-2100579 | On complexity reduction features for NR RedCap UEs | MediaTek Inc. |
| R1-2100625 | Discussion on RedCap features | NEC |
| R1-2100660 | On UE complexity reduction for RedCap devices | Intel Corporation |
| R1-2100772 | UE complexity reduction features for RedCap | Lenovo, Motorola Mobility |
| R1-2100823 | Discussion on UE complexity reduction features | Spreadtrum Communications |
| R1-2100843 | UE complexity reduction | Panasonic Corporation |
| R1-2100865 | UE complexity reduction for Redcap devices | Sony |
| R1-2100900 | Discussion on complexity reduction of reduced capability NR devices | LG Electronics |
| R1-2100969 | Discussion on UE complexity reduction | Asia Pacific Telecom, FGI |
| R1-2101049 | Discussion on UE complexity reduction | CMCC |
| R1-2101122 | Discussion on the complexity reduction for Redcap | Xiaomi |
| R1-2101214 | UE complexity reduction | Samsung |
| R1-2101390 | On UE complexity reduction features for RedCap | Apple |
| R1-2101471 | Complexity Reduction for RedCap Devices | Qualcomm Incorporated |
| R1-2101507 | Discussion on UE complexity reduction features | InterDigital, Inc. |
| R1-2101542 | Discussion on UE complexity reduction | Sharp |
| R1-2101619 | Discussion on UE complexity reduction for RedCap | NTT DOCOMO, INC. |
| R1-2101640 | Potential enhancement for UE complexity reduction | TCL Communication Ltd. |
| R1-2101659 | Discussion on UE complexity reduction | ASUSTeK |
| R1-2101718 | Discussion on UE complexity reduction | China Unicom |
| R1-2101766 | Complexity Reduction for RedCap Devices | Qualcomm Incorporated |
| R1-2101777 | Discussion on UE complexity reduction | OPPO |
| R1-2101849 | FL summary #1 for UE complexity reduction for RedCap | Moderator (Ericsson) |
| R1-2101850 | FL summary #2 for UE complexity reduction for RedCap | Moderator (Ericsson) |
| R1-2101851 | FL summary #3 for UE complexity reduction for RedCap | Moderator (Ericsson) |
| R1-2101852 | FL summary #4 for UE complexity reduction for RedCap | Moderator (Ericsson) |
| R1-2102094 | [Draft] LS on Half-duplex FDD switching time for RedCap UE | Ericsson |
| R1-2102145 | FL summary #5 for UE complexity reduction for RedCap | Moderator (Ericsson) |
| R1-2102146 | LS on Half-duplex FDD switching time for RedCap UE | RAN1, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2100035 | Higher layer support for RedCap | Ericsson |
| R1-2100166 | Mechanism in higher&PHY layer for Reduced Capability NR Devices | OPPO |
| R1-2100231 | RAN1 aspects of RedCap UE type and identification | Huawei, HiSilicon |
| R1-2100390 | Discussion on high layer support for RedCap UE | CATT |
| R1-2100450 | Higher layer support for RedCap NR devices | vivo, Guangdong Genius |
| R1-2100500 | Higher layer support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2100565 | Higher layer support of Reduced Capability NR devices | ZTE |
| R1-2100661 | On higher layer support for RedCap devices | Intel Corporation |
| R1-2100773 | Higher layer support of Reduced Capability NR devices | Lenovo, Motorola Mobility |
| R1-2100822 | Discussion on Higher layer support of RedCap UE | Spreadtrum Communications |
| R1-2100901 | Higher layer support for reduced capability NR devices | LG Electronics |
| R1-2101050 | Discussion on early identification of RedCap UEs | CMCC |
| R1-2101123 | Discussion on the higher layer support for Redcap | Xiaomi |
| R1-2101215 | UE capability report and access barring for Redcap UE | Samsung |
| R1-2101322 | Design consideration for Higher layer support of RedCap | Sierra Wireless, S.A. |
| R1-2101334 | UE identification for redcap devices | Sony |
| R1-2101391 | On Higher Layer Support of Redcap Devices | Apple |
| R1-2101472 | Higher layer support for RedCap devices | Qualcomm Incorporated |
| R1-2101506 | Higher layer support for Reduced Capability NR devices | InterDigital, Inc. |
| R1-2101620 | Discussion on higher layer support of RedCap | NTT DOCOMO, INC. |
| R1-2101660 | Higher layer support of reduced capability NR devices | ASUSTeK |
| R1-2101678 | Discussion on higher layer support of Redcap UE | WILUS Inc. |
| R1-2101724 | UE type definition for RedCap UEs | FUTUREWEI |
| TDoc | Title | Source |
|---|---|---|
| R1-2100036 | Other aspects of RedCap | Ericsson |
| R1-2100167 | Other considerations for reduced UE capability | OPPO |
| R1-2100310 | Consideration on reduced capability bandwidth reduction | TCL Communication Ltd. |
| R1-2100391 | Views on potential UE complexity reduction features | CATT |
| R1-2100451 | Discussion on reduced capability signalling | vivo, Guangdong Genius |
| R1-2100506 | Coverage recovery aspects for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2100566 | NR UE features for RedCap | ZTE |
| R1-2100693 | Reduced PDCCH monitoring for REDCAP NR devices | NEC |
| R1-2100902 | Other aspects of reduced capability NR devices | LG Electronics |
| R1-2100997 | PDCCH monitoring at reduced capability UE | Lenovo, Motorola Mobility |
| R1-2101051 | Discussion on network access control of RedCap devices | CMCC |
| R1-2101124 | Discussion on the coverage recovery for Redcap | Xiaomi |
| R1-2101216 | Remaining issues for Redcap | Samsung |
| R1-2101248 | Discussions on PDCCH monitoring for reduced capability devices | CEWiT |
| R1-2101266 | Potential solutions for UL coverage recovery | Huawei, HiSilicon |
| R1-2101473 | Design principles for RedCap devices | Qualcomm Incorporated |
| R1-2101543 | Discussion on other issues for reduced capability UEs | Sharp |
| R1-2101575 | PDCCH monitoring at reduced capability UE | Lenovo, Motorola Mobility |
| R1-2101621 | Discussion on coverage recovery for RedCap | NTT DOCOMO, INC. |
| R1-2101661 | Discussion on other consideration for reduced capability UE | ASUSTeK |
| R1-2101725 | UE capability framework for RedCap UEs | FUTUREWEI |
| TDoc | Title | Source |
|---|---|---|
| R1-2101940 | [Draft] Reply LS on Paging Enhancement | MediaTek |
| R1-2102136 | Reply LS on Paging Enhancement | RAN1, MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R1-2100168 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2100216 | Paging enhancement(s) for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2100392 | Paging enhancement for UE power saving | CATT |
| R1-2100452 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2100523 | Discussion on power saving enhancements for paging | ZTE , Sanechips |
| R1-2100544 | Potential paging enhancements | TCL Communication Ltd. |
| R1-2100591 | Design of paging early indication for idle/inactive-mode UE power saving | MediaTek Inc. |
| R1-2100662 | On paging enhancements for UE power saving | Intel Corporation |
| R1-2100824 | Discussion on potential paging enhancements | Spreadtrum Communications |
| R1-2100866 | Paging enhancement in Idle/Inactive state | Sony |
| R1-2100903 | Discussion on potential paging enhancements | LG Electronics |
| R1-2100998 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2101052 | Discussion on paging early indication design | CMCC |
| R1-2101125 | Paging enhancement for power saving | Xiaomi |
| R1-2101217 | Discussion on paging enhancements | Samsung |
| R1-2101300 | On paging enhancement | Panasonic |
| R1-2101392 | Paging early indication for idle/inactive-mode UE | Apple |
| R1-2101474 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2101503 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2101555 | Design of Paging Enhancements | Ericsson |
| R1-2101622 | Discussion on paging enhancements | NTT DOCOMO, INC. |
| R1-2101664 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2101787 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2101948 | Summary for Paging Enhancements | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100169 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2100217 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2100393 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2100453 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2100524 | TRS for RRC idle and inactive UEs | ZTE , Sanechips |
| R1-2100545 | TRS/CSI-RS occasion(s) for idle/inactive UEs | TCL Communication Ltd. |
| R1-2100592 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2100663 | TRS/CSI-RS functionality during idle/inactive mode | Intel Corporation |
| R1-2100814 | Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2100867 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Sony |
| R1-2100904 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2100999 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2101053 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2101126 | On TRS/CSI-RS occasion(s) for idle/inactive UEs | Xiaomi |
| R1-2101218 | Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2101219 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2101301 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2101393 | Indication of TRS/CSI-RS for idle/inactive-mode UE power saving | Apple |
| R1-2101475 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2101504 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2101544 | On TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2101556 | Provisioning of TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2101623 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2101665 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2100394 | Details of PEI configuration | CATT |
| R1-2100454 | Discussion on paging grouping | vivo |
| R1-2100525 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE , Sanechips |
| R1-2101557 | Modeling of Network Power Consumption | Ericsson |
| R1-2101740 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2100170 | DCI-based power saving adaptation solutions | OPPO |
| R1-2100218 | Extension(s) to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2100395 | PDCCH monitoring adaptation | CATT |
| R1-2100455 | Discussion on DCI-based power saving adaptation in connected mode | vivo |
| R1-2100498 | Extension to Rel-16 DCI-based power sabing adaptation during DRX Active Time | GDCNI |
| R1-2100526 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE , Sanechips |
| R1-2100593 | On enhancements to DCI-based UE power saving during DRX active time | MediaTek Inc. |
| R1-2100664 | Discussion on PDCCH monitoring reduction techniques during active time | Intel Corporation |
| R1-2100815 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2100905 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2100980 | Discussion on extension(s) to Rel-16 DCI-based power saving adaptation | Asia Pacific Telecom, FGI |
| R1-2101000 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2101054 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2101220 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2101285 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2101302 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2101394 | Enhanced DCI-based power saving adaptation | Apple |
| R1-2101476 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2101505 | PDCCH monitoring reduction in Active Time | InterDigital, Inc. |
| R1-2101558 | Design of active time power savings mechanisms | Ericsson |
| R1-2101567 | Power saving adaptation during Active Time | ASUSTeK |
| R1-2101624 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2101666 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2101893 | FL summary#1 of power saving for Active Time | Moderator (vivo) |
| R1-2101894 | FL summary#2 of power saving for Active Time | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100171 | Discussion on RLM relaxation | OPPO |
| R1-2100396 | System overhead analysis of PEI and TRS/CSI-RS for IDLE mode UE | CATT |
| R1-2100456 | Discussion on RLM/BFD/RRM relaxation | vivo |
| R1-2100527 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE , Sanechips |
| R1-2100816 | Discussion on other power saving techniques | Spreadtrum Communications |
| R1-2101257 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2101500 | Other power saving techniques | Qualcomm Incorporated |
| R1-2101559 | Evaluation results for UE power saving schemes | Ericsson |
| R1-2101720 | Paging indication based on sub-time units | InterDigital, Inc. |
| TDoc | Title | Source |
|---|---|---|
| R1-2100914 | Work plan for Rel-17 WI on NR coverage enhancements | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R1-2101625 | PUSCH enhancements for coverage enhancements | NTT DOCOMO, INC. |
| TDoc | Title | Source |
|---|---|---|
| R1-2100095 | Discussion on enhanced PUSCH repetition type A | ZTE |
| R1-2100172 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2100196 | Coverage enhancements for PUSCH repetition typeA | Huawei, HiSilicon |
| R1-2100397 | Discussion on enhancements on PUSCH repetition type A | CATT |
| R1-2100457 | Discussion on enhancement for PUSCH repetition type A | vivo |
| R1-2100665 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2100712 | Discussions on PUSCH repetition type A enhancements | LG Electronics |
| R1-2100731 | PUSCH repetition for coverage enhancements | InterDigital, Inc. |
| R1-2100915 | Enhancements on PUSCH repetition type A | China Telecom |
| R1-2100942 | Discussion on enhancements on PUSCH repetition type A | NEC |
| R1-2101001 | Enhancements on PUSCH repetition type A | Lenovo, Motorola Mobility |
| R1-2101017 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2101055 | Discussion on enhancements on PUSCH repetition type A | CMCC |
| R1-2101127 | Enhancements on PUSCH repetiton type A | Xiaomi |
| R1-2101221 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2101327 | Design Considerations for Enhancements on PUSCH repetition | Sierra Wireless, S.A. |
| R1-2101395 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2101407 | PUSCH Repetitions for Coverage Enhancement | Indian Institute of Tech (H) |
| R1-2101477 | Enhancements on PUSCH repetition type A | Qualcomm Incorporated |
| R1-2101520 | PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2101545 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2101641 | Enhancements on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2101656 | Enhancements on PUSCH repetiton type A | Xiaomi |
| R1-2101679 | Discussion on enhancements on PUSCH repetition type A | WILUS Inc. |
| R1-2101710 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2102113 | FL Summary on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100096 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2100173 | Supporting TB over multi-slot PUSCH | OPPO |
| R1-2100232 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2100398 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2100458 | Discussion on PUSCH TB processing over multiple slots | vivo |
| R1-2100666 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2100713 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2100732 | TB processing over multi-slot PUSCH | InterDigital, Inc. |
| R1-2100743 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2100916 | Discussion on TB processing over multi-slot PUSCH | China Telecom |
| R1-2100943 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2101002 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2101018 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2101056 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2101128 | Joint channel estimation for PUSCH | Xiaomi |
| R1-2101222 | TB processing over multi-slot PUSCH | Samsung |
| R1-2101328 | Design Considerations for TB processing over multi-slot PUSCH | Sierra Wireless, S.A. |
| R1-2101396 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2101406 | On TB processing over multiple slots for PUSCH | Indian Institute of Tech (H) |
| R1-2101478 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2101521 | TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2101546 | TB processing over multi-slot PUSCH | Sharp |
| R1-2101642 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2101646 | Discussion on TB processing over multi-slot PUSCH | MediaTek Inc. |
| R1-2101680 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2101711 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102241 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100097 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2100174 | Joint channel estimation for PUSCH | OPPO |
| R1-2100233 | Discussion on Joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2100399 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2100459 | Discussion on Joint channel estimation for PUSCH | vivo |
| R1-2100558 | Potential techniques for PUSCH coverage enhancement | Potevio Company Limited |
| R1-2100667 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2100714 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2100733 | Discussions on joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2100797 | Considerations on joint channel estimation over multi-PUSCH | Spreadtrum Communications |
| R1-2100917 | Discussion on joint channel estimation for PUSCH | China Telecom |
| R1-2101003 | Enhancements for DM-RS bundling for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2101020 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2101057 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2101223 | Joint channel estimation for PUSCH | Samsung |
| R1-2101329 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless, S.A. |
| R1-2101397 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2101479 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2101522 | Joint Channel Estimation for PUSCH | Ericsson |
| R1-2101547 | Joint channel estimation for PUSCH | Sharp |
| R1-2101643 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2101681 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2101712 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2101778 | Joint channel estimation for PUSCH | OPPO |
| R1-2102161 | [104-e-NR-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100098 | Discussion on coverage enhancements for PUCCH | ZTE |
| R1-2100175 | PUCCH enhancements for coverage | OPPO |
| R1-2100198 | PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2100400 | Discussion on PUCCH enhancements | CATT |
| R1-2100460 | Discussion on PUCCH enhancements | vivo |
| R1-2100668 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2100715 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2100747 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2100798 | Considerations on PUCCH coverage enhancement | Spreadtrum Communications |
| R1-2100918 | Discussion on PUCCH enhancements | China Telecom |
| R1-2101021 | Discussion on PUCCH enhancement for NR coverage enhancement | Panasonic Corporation |
| R1-2101058 | Discussion on PUCCH enhancements | CMCC |
| R1-2101081 | PUCCH enhancements | ETRI |
| R1-2101129 | PUCCH enhancement | Xiaomi |
| R1-2101224 | PUCCH enhancements | Samsung |
| R1-2101398 | PUCCH coverage enhancement | Apple |
| R1-2101480 | PUCCH coverage enhancements | Qualcomm Incorporated |
| R1-2101523 | PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2101548 | Dynamic PUCCH repetition factor indication | Sharp |
| R1-2101576 | Enhancements for PUCCH repetition | Lenovo, Motorola Mobility |
| R1-2101626 | PUCCH enhancements for coverage enhancements | NTT DOCOMO, INC. |
| R1-2101682 | Discussion on PUCCH enhancements for coverage enhancement | WILUS Inc. |
| R1-2101713 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2101813 | FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100099 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2100176 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2100197 | Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2100401 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2100461 | Discussion on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2100490 | Target of PUSCH Msg.3 coverage enhancements | SoftBank Corp. |
| R1-2100669 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2100716 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2100748 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2100919 | Discussion on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2100944 | Discussion on PUSCH repetitions for Msg3 | NEC |
| R1-2101022 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2101059 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2101082 | PUSCH coverage enhancement | ETRI |
| R1-2101130 | Type A PUSCH repetitions for Msg3 | Xiaomi |
| R1-2101225 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2101399 | Discussion on msg3 PUSCH repetition | Apple |
| R1-2101481 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2101524 | Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2101549 | Type A PUSCH repetitions for Msg3 | Sharp |
| R1-2101627 | Type A PUSCH repetitions for Msg3 for coverage enhancements | NTT DOCOMO, INC. |
| R1-2101683 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2101714 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2102226 | Feature lead summary on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100100 | Discussion on PUSCH and Msg3 enhancements for Redcap UEs | ZTE |
| R1-2100177 | Other considerations for coverage enhancement | OPPO |
| R1-2100402 | Views on reusing PUSCH enhancements for Msg3 | CATT |
| R1-2100462 | Enhanced Contention resolution mechanism for CBRA procedure with MSG3 PUSCH repetition | vivo |
| R1-2100749 | Discussion on the number of HARQ processes for VoIP | InterDigital, Inc. |
| R1-2100868 | Association of dual polarized SSBs | Sony |
| R1-2101226 | Discussion on PRACH enhancements for msg3 improvement | Samsung |
| R1-2101253 | Views on handling potential overlaps with other WIs | Huawei, HiSilicon |
| R1-2101525 | Other Coverage Enhancements for PUSCH | Ericsson |
| R1-2101715 | On the scope of RAN1 LS on phase and power requirements for joint channel estimation/DM-RS bundling of PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2101280 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R1-2102195 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100253 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2100507 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2100567 | Discussion on UL and DL 16QAM for NB-IoT | ZTE |
| R1-2100581 | Consideration on CQI report and Repetition applicability for 16QAM in R17 | MediaTek Inc. |
| R1-2100762 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2101324 | Design considerations to support 16-QAM for NB-IOT | Sierra Wireless, S.A. |
| R1-2101509 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2101698 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2101868 | Feature lead summary #1 on 104-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2102030 | Feature lead summary #2 on 104-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100254 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2100508 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2100568 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | ZTE |
| R1-2101325 | Design considerations to support 14-HARQ Feature for LTE-M | Sierra Wireless, S.A. |
| R1-2101510 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2101699 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson, AT&T, SoftBank, Telefónica, Verizon |
| R1-2101845 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-02] 1st check point | Moderator (Ericsson) |
| R1-2101846 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-02] 2nd check point | Moderator (Ericsson) |
| R1-2101847 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-02] 3rd check point | Moderator (Ericsson) |
| R1-2101848 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-02] final | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100255 | Support of a max DL TBS of 1736 bits in LTE-MTC | Huawei, HiSilicon |
| R1-2100509 | Support of a maximum DL TBS of 1736 bits for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2100569 | DL TBS increase for eMTC | ZTE |
| R1-2100869 | Support of 1736 bit maximum DL TBS for eMTC | Sony |
| R1-2101326 | Design considerations to support DL TBS of 1736 bits for LTE-M | Sierra Wireless, S.A. |
| R1-2101511 | Support of larger TBS for eMTC | Qualcomm Incorporated |
| R1-2101700 | Support of a maximum DL TBS of 1736 bits in LTE-MTC | Ericsson |
| R1-2101908 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-03] 1st check point | Moderator (Sony) |
| R1-2102124 | Feature Lead Summary [104-e-LTE-Rel17_NB_IoT_eMTC-03] 2nd check point | Moderator (Sony) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100570 | Channel quality report for 16QAM in NB-IoT | ZTE |
| R1-2101278 | Channel quality reporting in NB-IoT to support 16QAM | Huawei, HiSilicon |
| R1-2101701 | Compendium of 16-QAM simulation results in UL and DL for NB-IoT | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2101482 | Workplan for Rel-17 IAB | Qualcomm Incorporated |
| R1-2102196 | Session notes for 8.10 (Enhancements to Integrated Access and Backhaul) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100219 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2100463 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2100670 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2100690 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2100717 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2100777 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2100833 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2100958 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2100990 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2101083 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2101227 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2101483 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2101628 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2101695 | Resource multiplexing and DC in enhanced IAB | Ericsson |
| R1-2101855 | Summary #1 of [104-e-NR-eIAB-01] | Moderator (AT&T) |
| R1-2101880 | Reply LS on inter-donor topology redundancy | RAN1, Samsung |
| R1-2101889 | Summary of [104-e-NR-eIAB-01] – 1st Checkpoint | Moderator (AT&T) |
| R1-2101890 | Summary of [104-e-NR-eIAB-01] – 2nd Checkpoint | Moderator (AT&T) |
| R1-2101891 | Summary of [104-e-NR-eIAB-01] – 3rd Checkpoint | Moderator (AT&T) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100220 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2100464 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2100671 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2100718 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2100744 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Fujitsu |
| R1-2100778 | Enhancements for IAB interference management | AT&T |
| R1-2100834 | Other enhancements for simultaneous operation of IAB Parent and Child | Nokia, Nokia Shanghai Bell |
| R1-2100955 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2100959 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2100991 | Timing, interference, and power control in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2101084 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2101228 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2101484 | On enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2101629 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2101696 | Timing, CLI and power control in enhanced IAB | Ericsson |
| R1-2101810 | Enhancements for IAB interference management | AT&T |
| R1-2101878 | Summary #1 of [104-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| R1-2101909 | Summary #2 of [104-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| R1-2102031 | Summary #3 of [104-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| R1-2102172 | Summary #4 of [104-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100221 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2100465 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2100960 | Discussion on multiplexing capability for IAB | ZTE, Sanechips |
| R1-2101085 | Other enhancements to eIAB | ETRI |
| R1-2101697 | Response to RAN3 LS on inter-donor topology redundancy | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2101229 | On Sidelink Enhacement Work Item | Samsung |
| R1-2102024 | Summary of [104-e-NR-R17-SL-LS-01] regarding potential reply to LS in R1-2100021 | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100722 | V2X channel model and scenario updates | GDCNI |
| R1-2101230 | On Resource Allocation Enhancements | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2100141 | Power saving mechanism in NR sidelink | OPPO |
| R1-2100205 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2100309 | Considerations on partial sensing in NR V2X | CAICT |
| R1-2100351 | Discussion on resource allocation for power saving | CATT, GOHIGH |
| R1-2100466 | Resource allocation for sidelink power saving | vivo |
| R1-2100486 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2100492 | Discussion on resource allocation for power saving | Zhejiang Lab |
| R1-2100517 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2100538 | Sidelink resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2100546 | Resource allocation for power saving | TCL Communication Ltd. |
| R1-2100612 | Resource allocation for sidelink power saving | MediaTek Inc. |
| R1-2100672 | Design of sidelink power saving solutions | Intel Corporation |
| R1-2100687 | Resource allocation mechanisms for power saving | Ericsson |
| R1-2100696 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2100701 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2100745 | Considerations on partial sensing and DRX in NR V2X | Fujitsu |
| R1-2100766 | Sidelink resource allocation for Power saving | Lenovo, Motorola Mobility |
| R1-2100801 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2100870 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2100924 | Discussion on sidelink power saving | ZTE, Sanechips |
| R1-2100946 | Discussion on resource allocation for power saving | NEC |
| R1-2100962 | Discussion on resource allocation for power saving | Hyundai Motors |
| R1-2100981 | Resource allocation for power saving | InterDigital, Inc. |
| R1-2101060 | Discussion on resource allocation for power saving | CMCC |
| R1-2101086 | Discussion on resource allocation for power saving | ETRI |
| R1-2101097 | Discussion on sidelink resource allocation for power saving | Xiaomi |
| R1-2101231 | On Resource Allocation for Power Saving | Samsung |
| R1-2101357 | Sidelink Resource Allocation for Power Saving | Apple |
| R1-2101400 | Discussion on Reduce Power Consumption for Sidelink | ROBERT BOSCH GmbH |
| R1-2101412 | FL summary for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| R1-2101422 | On NR Sidelink Resource Allocation for Power Saving | Convida Wireless |
| R1-2101485 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2101550 | Discussion on resource allocation for power saving | Sharp |
| R1-2101572 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2101630 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2101663 | Resource allocation for power saving with partial sensing in NR sidelink enhancement | ITL |
| R1-2101788 | Considerations on partial sensing and DRX in NR V2X | Fujitsu |
| R1-2101790 | Resource allocation for sidelink power saving | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2100047 | Views on resource allocation enhancements for sidelink communication | FUTUREWEI |
| R1-2100142 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2100206 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2100352 | Discussion on feasibility and benefits for mode 2 enhancements | CATT, GOHIGH |
| R1-2100467 | Discussion on mode-2 enhancements | vivo |
| R1-2100493 | Inter-UE coordination for mode 2 | Zhejiang Lab |
| R1-2100518 | Discussion on feasibility and benefits for mode 2 enhancements | LG Electronics |
| R1-2100539 | Inter-UE coordination in mode 2 sidelink resource allocation | Nokia, Nokia Shanghai Bell |
| R1-2100547 | Feasibility and benefits for mode 2 enhancements | TCL Communication Ltd. |
| R1-2100606 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2100673 | On feasibility and benefits of inter-UE coordination for sidelink mode-2 design | Intel Corporation |
| R1-2100688 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2100702 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2100746 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2100767 | Sidelink resource allocation for Reliability enhancement | Lenovo, Motorola Mobility |
| R1-2100802 | Discussion on feasibility and benefit of mode 2 enhancements | Spreadtrum Communications |
| R1-2100828 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2100871 | Discussion on reliability and latency enhancements for mode 2 | Sony |
| R1-2100925 | Discussion on inter-UE coordination | ZTE, Sanechips |
| R1-2100947 | Discussion on feasibility and benefits for mode 2 enhancements | NEC |
| R1-2100963 | Discussion on feasibility and benefits for mode 2 enhancements | Hyundai Motors |
| R1-2100982 | On inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2101004 | Mode 2 enhancements in sidelink | Panasonic Corporation |
| R1-2101061 | Discussion on reliability and latency enhancements for mode-2 resource allocation | CMCC |
| R1-2101087 | Discussion on feasibility and benefits for mode 2 enhancements | ETRI |
| R1-2101098 | Feasibility and benefits for mode2 enhancements | Xiaomi |
| R1-2101232 | On Feasibility and Benefits for Mode2 Enhancements | Samsung |
| R1-2101358 | Inter-UE Coordination for Mode 2 Resource Allocation | Apple |
| R1-2101401 | Discussion on Sidelink Mode-2 Resource Allocation Enhancements | ROBERT BOSCH GmbH |
| R1-2101409 | Inter-UE coordination for mode 2 enhancement | ITL |
| R1-2101423 | On NR Sidelink Resource Allocation Mode 2 Enhancement | Convida Wireless |
| R1-2101486 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2101551 | Discussion on feasibility and benefits for mode 2 enhancements | Sharp |
| R1-2101574 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2101631 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2101647 | Feasibility and benefits for NR Sidelink mode 2 enhancements | CEWiT |
| R1-2101786 | Discussion on feasibility and benefits for mode 2 enhancements | LG Electronics |
| R1-2101791 | Discussion on mode-2 enhancements | vivo |
| R1-2101804 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2101843 | Feature lead summary for AI 8.11.1.2 Feasibility and benefits for mode 2 enhancements | Moderator (LG Electronics) |
| R1-2101910 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2101911 | Discussion on mode-2 enhancements | vivo |
| R1-2101926 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2101941 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2102165 | Draft LS on Mode 2 enhancements in NR sidelink | LG Electronics |
| R1-2102166 | Detailed observations from evaluation results | Moderator (LG Electronics) |
| R1-2102167 | Feature lead summary for AI 8.11.1.2 Feasibility and benefits for mode 2 enhancements | Moderator (LG Electronics) |
| R1-2102168 | LS on Mode 2 enhancements in NR sidelink | RAN1, LG Electronics |
| R1-2102268 | Feature lead summary for AI 8.11.1.2 Feasibility and benefits for mode 2 enhancements | Moderator (LG Electronics) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100143 | Remaining issues in sidelink evaluation methdology for power saving | OPPO |
| R1-2100353 | Remaining issues on sidelink evaluation methodology | CATT, GOHIGH |
| R1-2100468 | Other aspects on SL enhancements | vivo |
| R1-2100519 | Discussion on remaining aspects of sidelink evaluation methodology update for power saving | LG Electronics |
| R1-2100689 | Remaining evaluation assumptions and methodology for power saving | Ericsson |
| R1-2100926 | Discussion on remaining issues for sidelink evaluation methodology | ZTE, Sanechips |
| R1-2100983 | On SL multi-carrier operation and remaining issues for simulation methodology update | InterDigital, Inc. |
| R1-2101099 | Discussion on remaining issues of sidelink evaluation methodology | Xiaomi |
| R1-2101233 | On Sidelink Issues and RAN1 Impacts | Samsung |
| R1-2101254 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2101801 | FL summary #1 on other issues in NR Sidelink enhancement | Moderator (CATT) |
| R1-2102130 | FL summary #2 on other issues in NR Sidelink enhancement | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2101062 | Updated NR MBS work plan | CMCC |
| R1-2102197 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100048 | Discussion on PDCCH aspects for group scheduling | FUTUREWEI |
| R1-2100106 | Discussion on mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2100144 | Group scheduling for NR Multicast and Broadcast Services | OPPO |
| R1-2100189 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2100354 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2100469 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2100510 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2100613 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2100674 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2100698 | Views on group scheduling for NR MBS | Google Inc. |
| R1-2100768 | Discussion on group scheduling mechanism for NR MBS | Lenovo, Motorola Mobility |
| R1-2100805 | Discussion on MBS group scheduling for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2100872 | Considerations on MBS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2100906 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2100956 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | ETRI |
| R1-2101063 | Discussion on group scheduling mechanisms | CMCC |
| R1-2101234 | On mechanisms to support group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2101359 | Discussion on group scheduling mechanism for RRC_connected UEs | Apple |
| R1-2101424 | On group scheduling mechanism for NR multicast and broadcast | Convida Wireless |
| R1-2101487 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2101579 | Discussion on group scheduling for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2101658 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2101726 | Mechanisms to support group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2101767 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101854 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101867 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101875 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101907 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101937 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2101974 | Summary#7 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2102032 | Summary#8 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2102099 | Summary#9 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2102171 | Summary#10 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100049 | Discussion on improving reliability for RRC_CONNECTED UEs | FUTUREWEI |
| R1-2100107 | Discussion on mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2100145 | UL feedback for RRC-CONNECTED UEs in MBMS | OPPO |
| R1-2100190 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2100355 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2100470 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2100511 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2100557 | Reliability improvement for RRC_CONNECTED UEs in MBS | Potevio Company Limited |
| R1-2100614 | Discussion on HARQ operation for NR MBS reliable transmission | MediaTek Inc. |
| R1-2100675 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2100699 | Views on retransmission procedure for NR MBS | Google Inc. |
| R1-2100769 | Discussion on reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2100806 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2100907 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2100957 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | ETRI |
| R1-2101064 | Discussion on reliability improvement | CMCC |
| R1-2101235 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2101360 | Discussion on MBS reliability improvement for RRC_connected UEs | Apple |
| R1-2101425 | On reliability enhancement for NR multicast and broadcast | Convida Wireless |
| R1-2101488 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2101637 | Study on the reliability for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2101727 | Discussion on reliability mechanisms for NR MBS | Ericsson |
| R1-2101837 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2101906 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2101987 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2102082 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2102134 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100108 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2100146 | Discussion on support for IDLE and INACTIVE state UEs | OPPO |
| R1-2100191 | Discussion on multicast support for IDLE/INACTIVE UEs | Huawei, HiSilicon |
| R1-2100356 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | CATT, CBN |
| R1-2100471 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE Ues | vivo |
| R1-2100512 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2100615 | Common frequency resource for NR PTM transmission | MediaTek Inc. |
| R1-2100676 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2100770 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2100873 | Considerations on MBS functions for RRC_IDLE UEs | Sony |
| R1-2100908 | Basic function for broadcast/multicast | LG Electronics |
| R1-2101065 | Discussion on NR MBS in RRC_IDLE/ RRC_INACTIVE states | CMCC |
| R1-2101236 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2101361 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Apple |
| R1-2101426 | On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R1-2101489 | Views on group scheduling for Multicast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2101638 | Basic functions for MBS for RRC_IDLE/RRC_INACTIVE UEs | CHENGDU TD TECH LTD. |
| R1-2101721 | Feature lead summary on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2101728 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2101876 | Feature lead summary#2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2101877 | Feature lead summary#3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2102067 | Feature lead summary#4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2102068 | Feature lead summary#5 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| R1-2102180 | Feature lead summary#6 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/ RRC_INACTIVE states | Moderator (BBC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100109 | Consideration on performance enhancement for RRC_IDLE/INACTIVE UEs | ZTE |
| R1-2100357 | Discussion on other issues for MBS | CATT |
| R1-2100472 | Other issues for Rel-17 MBS | vivo |
| R1-2100909 | Other aspects for MBS | LG Electronics |
| R1-2101639 | Effects of NR MBS on PDSCH and PDCCH | CHENGDU TD TECH LTD. |
| R1-2101729 | Assumptions for Performance Evaluations of NR-MBS | Ericsson |
| R1-2101730 | LTE SC-PTM design as a reference for NR MBS in IDLE/INACTIVE | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2101560 | Work plan for Rel17 WI on NR Dynamic spectrum sharing (DSS) | Ericsson |
| R1-2102198 | Sesson notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100110 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2100186 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2100193 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2100358 | Discussion on cross-carrier scheduling from Scell to Pcell | CATT |
| R1-2100473 | Discussion on Scell scheduling Pcell | vivo |
| R1-2100677 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2100694 | Discussion on cross carrier scheduling for NR DSS | NEC |
| R1-2100719 | Om cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2100794 | Discussion on cross-carrier scheduling from SCell to PCell | Spreadtrum Communications |
| R1-2100885 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2100992 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2101066 | Discussion on cross-carrier scheduling from SCell to Pcell | CMCC |
| R1-2101088 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2101100 | Discussion on Cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2101237 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2101292 | USS monitoring in sSCell and PCell | InterDigital, Inc. |
| R1-2101362 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2101490 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2101561 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2101632 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2101655 | Discussion on cross-carrier scheduling from Scell to Pcell | ASUSTeK |
| R1-2101863 | Summary of Email discussion [104-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2102018 | Summary#2 of Email discussion [104-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2102101 | Summary#3 of Email discussion [104-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2102236 | Summary#4 of Email discussion [104-e-NR-DSS-01] | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100111 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | ZTE |
| R1-2100187 | Discussion on multi-cell PDSCH scheduling via a single DCI | OPPO |
| R1-2100194 | Discussion on multi-carrier scheduling using single PDCCH | Huawei, HiSilicon |
| R1-2100359 | Discussion on multi-cell PDSCH scheduling via a single DCI | CATT |
| R1-2100474 | Discussion on joint scheduling | vivo |
| R1-2100611 | On Multi-cell PDSCH Scheduling via Single DCI | MediaTek Inc. |
| R1-2100678 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2100720 | On support of Single DCI scheduling two cells | Nokia, Nokia Shanghai Bell |
| R1-2100771 | Discussion on multi-cell PDSCH scheduling via a single DCI | Lenovo, Motorola Mobility |
| R1-2100886 | Discussion on multi-cell PDSCH scheduling via a single DCI | LG Electronics |
| R1-2101089 | Discussion on multi-cell PDSCH scheduling via a single DCI | ETRI |
| R1-2101238 | Considerations for scheduling on two cells using a single DCI format | Samsung |
| R1-2101293 | On the support of single DCI scheduling multi-cell | InterDigital, Inc. |
| R1-2101363 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | Apple |
| R1-2101491 | Multi-cell PDSCH scheduling via a single DCI | Qualcomm Incorporated |
| R1-2101562 | Study on single DCI scheduling PDSCH on multiple cells | Ericsson |
| R1-2101633 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | NTT DOCOMO, INC. |
| R1-2101657 | Discussion on multi-cell PDSCH scheduling via a single DCI | ASUSTeK |
| R1-2101789 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | ZTE |
| R1-2101864 | Feature lead summary#1 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| R1-2101912 | Feature lead summary#2 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| R1-2102083 | Feature lead summary#3 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| R1-2102138 | Feature lead summary#4 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100045 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2100112 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2100188 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2100192 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2100360 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | CATT |
| R1-2100475 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2100679 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2100695 | Discussion on efficient activation mechanism for SCells | NEC |
| R1-2100721 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2100795 | Discussion on efficient activation/de-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2101067 | Discussion on efficient activation/de-activation mechanism for SCells | CMCC |
| R1-2101239 | On efficient activation/de-activation mechanism for Scells | Samsung |
| R1-2101294 | Fast SCell Activation | InterDigital, Inc. |
| R1-2101364 | On Efficiency Activation/De-activation for SCells in CA | Apple |
| R1-2101492 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2101563 | Reduced Latency SCell Activation | Ericsson |
| R1-2101566 | Efficient activation/deactivation of SCell | ASUSTeK |
| R1-2101634 | Discussion on efficient activation/deactivation mechanism for SCells | NTT DOCOMO, INC. |
| R1-2101932 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2101933 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100055 | XR traffic model | FUTUREWEI |
| R1-2100132 | Discussion on the XR traffic models for evaluation | OPPO |
| R1-2100207 | Discussion on applications and traffic model for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2100361 | XR traffic model | CATT |
| R1-2100476 | Discussion on traffic models of XR | vivo |
| R1-2100528 | Discussion on Traffic Model for XR evaluations | ZTE , Sanechips |
| R1-2100555 | Discussion on traffic model for XR study | LG Electronics |
| R1-2100571 | Discussion on XR applications and traffic models | InterDigital, Inc. |
| R1-2100680 | On traffic model for XR | Intel Corporation |
| R1-2100724 | On Traffic Model for XR study | Nokia, Nokia Shanghai Bell |
| R1-2100775 | XR Traffic Model Considerations | AT&T |
| R1-2100879 | Discussion on XR Applications and Evaluation Assumptions | Sony |
| R1-2101101 | Discussion on Traffic model for XR evaluation | Xiaomi |
| R1-2101137 | Traffic Model for XR and CG | MediaTek Inc. |
| R1-2101240 | XR Applications and Traffic Models | Samsung |
| R1-2101314 | Traffic model for XR | Ericsson |
| R1-2101365 | Views on XR traffic models | Apple |
| R1-2101493 | XR Traffic Models | Qualcomm Incorporated |
| R1-2101635 | Discussion on traffic model for XR | NTT DOCOMO, INC. |
| R1-2102077 | Views on XR traffic models | Apple |
| R1-2102254 | Email discussion/approval for traffic model and capacity KPI for XR | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100056 | XR evaluation methodology | FUTUREWEI |
| R1-2100133 | Discussion on the XR evaluation methodology | OPPO |
| R1-2100242 | Discussion on evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2100362 | Evaluation methodology and performance index for XR | CATT |
| R1-2100477 | Discussion on evaluation methodologies of XR | vivo |
| R1-2100529 | On XR Evaluation Methodology | ZTE , Sanechips |
| R1-2100556 | Discussion on evaluation assumption for XR study | LG Electronics |
| R1-2100572 | Discussion on Evaluation Methodology for XR | InterDigital, Inc. |
| R1-2100586 | On Evaluation Methodology for XR and CG | MediaTek Inc. |
| R1-2100681 | On evaluation methodology for XR | Intel Corporation |
| R1-2100725 | Development of the Evaluation Methodology for XR Study | Nokia, Nokia Shanghai Bell |
| R1-2100776 | XR Evaluation Assumptions | AT&T |
| R1-2101102 | Discussion on evaluation methodology for XR services | Xiaomi |
| R1-2101241 | XR Evaluation Methodology and KPIs | Samsung |
| R1-2101315 | Evaluation methodology for XR | Ericsson |
| R1-2101366 | Views on XR evaluation methodology | Apple |
| R1-2101494 | Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2101636 | Discussion on evaluation methodology for XR | NTT DOCOMO, INC. |
| R1-2101762 | Evaluation methodology for XR | Ericsson |
| R1-2101866 | Evaluation Methodology including identification of KPIs of interest for relevant deployment scenarios | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100363 | Evaluation results of XR performance | CATT |
| R1-2100478 | Initial performance evaluation results of XR | vivo |
| R1-2100530 | Preliminary Performance Evaluation Results for XR | ZTE , Sanechips |
| R1-2100587 | Initial Performance and Evaluation Results for XR and CG | MediaTek Inc. |
| R1-2100682 | Initial results for XR | Intel Corporation |
| R1-2100726 | Initial Performance Evaluation Results | Nokia, Nokia Shanghai Bell |
| R1-2101068 | Discussion on XR evaluation | CMCC |
| R1-2101255 | Initial evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2101316 | Initial XR performance evaluation results | Ericsson |
| R1-2101495 | Initial XR Performance Evaluation Results | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2100134 | Discussion on the support of XR/CG service in sidelink-unlicensed | OPPO |
| R1-2100364 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2100479 | Challenges and potential enhancements of XR | vivo |
| R1-2100531 | Considerations on XR specific enhancements | ZTE , Sanechips |
| R1-2100573 | Discussion on potential enhancements for supporting XR | InterDigital, Inc. |
| R1-2101103 | Discussion on potential enhancement for supporting XR | Xiaomi |
| R1-2101269 | Other aspects for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2101317 | Mobility and XR applications | Ericsson |
| R1-2101367 | Views on potential enhancements for XR | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2100599 | Rel-17 IoT NTN Work Plan | MediaTek Inc. |
| R1-2100774 | Market expectations for IoT over NTN | NOVAMINT |
| R1-2101138 | Skeleton TR 36.763 Study on NB-IoT / eMTC for NTN (Release 17) | MediaTek Inc. |
| R1-2101139 | Text Proposal for TR 36.673 chapter related to RAN1 | MediaTek Inc. |
| R1-2101779 | Market expectations for IoT over NTN | NOVAMINT |
| R1-2102177 | Text proposal for TR 36.763 for RAN1#104-e Agreements | Rapporteur (MediaTek) |
| R1-2102199 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| R1-2102231 | TR36.763 Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) | Rapporteur (MediaTek) |
| R1-2102255 | Text proposal for TR 36.763 for RAN1#104-e Agreements | Rapporteur (MediaTek) |
| R1-2102256 | TR36.763 Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) | Rapporteur (MediaTek) |
| R1-2102258 | Text proposal for TR 36.763 for RAN1#103e Agreements | Rapporteur (MediaTek) |
| R1-2102272 | TR36.763 Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) | Rapporteur (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100160 | Discussion on scenarios applicable to NB-IoT/eMTC | OPPO |
| R1-2100225 | Application scenarios of IoT in NTN | Huawei, HiSilicon |
| R1-2100248 | Discussion on the scenarios and assumption for IoT-NTN | ZTE |
| R1-2100365 | Applicable scenarios to NB-IoT/eMTC | CATT |
| R1-2100480 | Discussion on scenarios applicable to NB-IoT/eMTC for NTN | vivo |
| R1-2100494 | Scenarios applicable to NB-IoT/eMTC | Zhejiang Lab |
| R1-2100521 | Discussion on NB-IoT NTN scenarios with small satellites / CubeSats | Sateliot, Gatehouse, Thales, Kepler |
| R1-2100533 | Discussion on NB-IoT NTN scenarios with small satellites | Sateliot, Gatehouse |
| R1-2100600 | IoT NTN scenarios | MediaTek Inc. |
| R1-2100874 | Scenarios for IoT-NTN | Sony |
| R1-2100930 | On scenarios and evaluations for NB-IoT and eMTC based NTN | Ericsson |
| R1-2100975 | Scenarios applicable to NB-IoT in NTN | Asia Pacific Telecom, FGI |
| R1-2101012 | Feasibility of the large, single-beam small sats / CubeSats scenario | THALES |
| R1-2101019 | Feasibility of the large, single-beam small sats / CubeSats scenario | Thales, Sateliot, GateHouse |
| R1-2101027 | Scenarios and evalutions for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101069 | Discussion on scenarios for IoT NTN | CMCC |
| R1-2101104 | Discussion on the scenarios of NBIoT and eMTC over NTN | Xiaomi |
| R1-2101146 | IoT NTN Link Budget | Eutelsat S.A. |
| R1-2101242 | On Scenarios applicable to NB-IoT/eMTC | Samsung |
| R1-2101368 | On Link Budget of IoT NTN | Apple |
| R1-2101413 | Discussion on scenarios for NB-IoT and eMTC over NTN | CAICT |
| R1-2101512 | Scenarios applicable to NB-IoT/eMTC | Qualcomm Incorporated |
| R1-2101802 | Summary#1 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2101869 | Summary#2 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2101998 | Summary#3 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2102102 | Summary#4 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2102265 | Summary#5 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100161 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2100234 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2100249 | Discussion on the synchronization for IoT-NTN | ZTE |
| R1-2100366 | Time and frequency synchronization for NB-IoT/eMTC | CATT |
| R1-2100481 | Discussion on time and frequency synchronization enhancements on NB-IoT/eMTC for NTN | vivo |
| R1-2100601 | UE Time and frequency Synchronisation for IoT NTN | MediaTek Inc. |
| R1-2100683 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2100763 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2100810 | Consideration on enhancements to time and frequency synchronization | Spreadtrum Communications |
| R1-2100875 | Time and frequency synchronisation enhancements for IoT-NTN | Sony |
| R1-2100931 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2100976 | Time and frequency synchronization to NB-IoT in NTN | Asia Pacific Telecom, FGI |
| R1-2101028 | Enhancements to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101070 | Discussion on enhancements for IoT NTN | CMCC |
| R1-2101105 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2101243 | On enhancements to time and frequency synchronization | Samsung |
| R1-2101369 | Discussion on Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2101402 | Time/Frequency Synchronization for IoT NTN | InterDigital, Inc. |
| R1-2101513 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2101692 | Discussion on enhancement of time and frequency synchronization for NB-IoT over satellite | Fraunhofer IIS, Fraunhofer HHI |
| R1-2101803 | Summary#1 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2101870 | Summary#2 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2101999 | Summary#3 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2102103 | Summary#4 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2102266 | Summary#5 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100162 | Discussion on timing relationship enhancements | OPPO |
| R1-2100235 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2100250 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2100367 | Timing relationship enhancement for NB-IoT/eMTC | CATT |
| R1-2100482 | Discussion on timing relationship enhancements on NB-IoT/eMTC for NTN | vivo |
| R1-2100495 | Timing relationship enhancements to support NB-IoT/eMTC in Non-Terrestrial Network | Zhejiang Lab |
| R1-2100602 | Timing relationship enhancements | MediaTek Inc. |
| R1-2100684 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2100764 | Timing relationship enhancements for IoT NTN | Lenovo, Motorola Mobility |
| R1-2100811 | Consideration on timing relationship enhancements | Spreadtrum Communications |
| R1-2100876 | Timing relationship for IoT-NTN | Sony |
| R1-2100932 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2100977 | Timing relationship enhancements to NB-IoT in NTN | Asia Pacific Telecom, FGI |
| R1-2101029 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101106 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2101244 | On timing relationship enhancements | Samsung |
| R1-2101370 | Discussion on Timing Relationship Enhancement in IoT NTN | Apple |
| R1-2101403 | On timing relationship enhancement for IoT NTN | InterDigital, Inc. |
| R1-2101514 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2101844 | FL summary of AI 8.15.3 | Moderator (Sony) |
| R1-2101949 | FL summary#2 of AI 8.15.3 | Moderator (Sony) |
| R1-2102174 | FL summary#3 of AI 8.15.3 | Moderator (Sony) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100163 | Discussion on HARQ enhancements | OPPO |
| R1-2100236 | Discussion on HARQ enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2100251 | Discussion on HARQ for IoT-NTN | ZTE |
| R1-2100368 | HARQ operation enhancement for NB-IoT/eMTC | CATT |
| R1-2100483 | Discussion on HARQ enhancements on NB-IoT/eMTC for NTN | vivo |
| R1-2100603 | Enhancement on HRQ | MediaTek Inc. |
| R1-2100685 | On HARQ enhancements for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2100765 | HARQ enhancement for IoT NTN | Lenovo, Motorola Mobility |
| R1-2100812 | Consideration on enhancements on HARQ | Spreadtrum Communications |
| R1-2100877 | HARQ issues for IoT-NTN | Sony |
| R1-2100933 | On HARQ enhancements for IoT NTN | Ericsson |
| R1-2100978 | Enhancements on HARQ to NB-IoT in NTN | Asia Pacific Telecom, FGI |
| R1-2101030 | HARQ for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101107 | Discussion on the HARQ enhancement for IoT NTN | Xiaomi |
| R1-2101245 | On enhancements on HARQ | Samsung |
| R1-2101323 | NTN IoT HARQ Considerations | Sierra Wireless, S.A. |
| R1-2101371 | Discussion on HARQ Enhancement in IoT NTN | Apple |
| R1-2101404 | HARQ enhancement for IoT NTN | InterDigital, Inc. |
| R1-2101515 | Enhancements on HARQ | Qualcomm Incorporated |
| R1-2101822 | Summary#1 for enhancements on HARQ | Moderator (Samsung) |
| R1-2101956 | Summary#2 for enhancements on HARQ | Moderator (Samsung) |
| R1-2101957 | Summary#3 for enhancements on HARQ | Moderator (Samsung) |
| R1-2102132 | Summary#4 for enhancements on HARQ | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100164 | Discussion on other aspects | OPPO |
| R1-2100252 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2100604 | Others | MediaTek Inc. |
| R1-2100813 | Consideration on other design aspects for IOT NTN | Spreadtrum Communications |
| R1-2100878 | Power consumption of IoT-NTN | Sony |
| R1-2100934 | On evaluation assumptions for NB-IoT and eMTC based NTN | Ericsson |
| R1-2100979 | NB-IoT modifications to support the NTN deployment | Asia Pacific Telecom, FGI |
| R1-2101031 | Link budget analysis for UE power class 6 for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2101108 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| R1-2101261 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| R1-2101516 | Other aspects for NTN IOT | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2100215 | On support of DL 1024QAM for NR FR1 | Huawei, HiSilicon |
| R1-2100369 | DL 1024QAM for NR FR1 | CATT |
| R1-2100484 | On supporting DL 1024QAM for NR FR1 | vivo |
| R1-2100532 | Discussion on DL 1024QAM for NR FR1 | ZTE , Sanechips |
| R1-2100686 | Support of 1024QAM | Intel Corporation |
| R1-2101071 | Discussion on DL 1024QAM for NR FR1 | CMCC |
| R1-2101246 | On remaining issues of DL 1024QAM for NR FR1 | Samsung |
| R1-2101421 | Support for NR DL 1024 QAM in FR1 | Nokia, Nokia Shanghai Bell |
| R1-2101496 | 1024-QAM for NR PDSCH | Qualcomm Incorporated |
| R1-2101564 | 1024QAM for NR DL | Ericsson |
| R1-2101823 | Initial summary for introduction of 1024QAM for NR DL | Moderator(Ericsson) |
| R1-2101892 | Summary for introduction of 1024QAM for NR DL | Moderator(Ericsson) |
| R1-2101959 | Summary#2 for introduction of 1024QAM for NR DL | Moderator(Ericsson) |
| R1-2102023 | First Set of Agreed TPs for support of 1024QAM in NR DL | Moderator(Ericsson) |
| R1-2102059 | Summary#3 for introduction of 1024QAM for NR DL | Moderator(Ericsson) |
| R1-2102087 | Second Set of Agreed TPs for support of 1024QAM in NR DL | Moderator(Ericsson) |
| R1-2102088 | LS on Introduction of DL 1024QAM for NR | RAN1, Ericsson |
| R1-2102089 | Final Summary for introduction of 1024QAM for NR DL | Moderator(Ericsson) |
| R1-2102200 | Session notes for 8.16 (Introduction of DL 1024QAM for NR FR1) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2100297 | Discussion on issues of NR codeword mapping | ZTE |