| TDoc | Title | Source |
|---|---|---|
| R1-2208320 | Draft Agenda of RAN1#110bis-e meeting | RAN1 Chair |
| R1-2208323 | RAN1#110b-e Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2208324 | Additional Guidelines for RAN1#110bis e-Meeting Management | RAN1 Chair |
| R1-2208998 | Draft Agenda of RAN1#110bis-e meeting | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2208322 | Highlights from RAN#97e | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2208321 | Report of RAN1#110 meeting | ETSI MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2208325 | LS on support of positioning in FR2-2 | RAN2, Samsung |
| R1-2208326 | LS on SR config for MG (de-)activation request MAC CE | RAN2, Huawei |
| R1-2208327 | LS on the progress of NCR identification and authorization | RAN2, ZTE |
| R1-2208328 | LS on switching option capability for UL 2Tx-2Tx switching | RAN2, Qualcomm |
| R1-2208329 | LS on resource pool index in DCI Format 3_0 | RAN2, vivo |
| R1-2208330 | LS to RAN1 on TP to TR 37.985 | RAN2, ZTE |
| R1-2208331 | LS on L1/L2-based inter-cell mobility | RAN2, MediaTek |
| R1-2208332 | Reply LS on RAN feedback for low latency | RAN2, Huawei |
| R1-2208333 | LS on LCS framework for Network verified UE location (NTN) | RAN2, Thales |
| R1-2208334 | LS on Pose Information for XR | RAN2, Nokia |
| R1-2208335 | LS on XR-awareness in RAN | RAN2, Qualcomm |
| R1-2208336 | Reply LS on CCA configurations of neighbour cells | RAN2, Nokia |
| R1-2208337 | LS to RAN4 on capability for PRS measurement without MG | RAN2, Intel |
| R1-2208338 | LS on Terminology Alignment for Ranging/Sidelink Positioning | SA2, Xiaomi |
| R1-2208339 | LS on FS_5MBS_Ph2 progress | SA2, Huawei |
| R1-2208341 | Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN4, Huawei |
| R1-2208342 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2208343 | LS on Feature Group 6-1a “bwp-WithoutRestriction” | RAN4, Qualcomm |
| R1-2208344 | void | ETSI MCC |
| R1-2208345 | void | ETSI MCC |
| R1-2208346 | Reply LS on MTTD for multi-DCI multi-TRP with two Tas | RAN4, Ericsson |
| R1-2208347 | Reply LS on interference modelling for duplex evolution | RAN4, Samsung, CMCC, Qualcomm |
| R1-2208348 | LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | RAN4, vivo |
| R1-2208349 | LS reply on TCI assumption for RSSI measurement for FR2-2 | RAN4, Apple |
| R1-2208350 | Reply LS on DL-PRS measurements with reduced samples capability | RAN4, CATT |
| R1-2208351 | Reply LS on the UE/TRP TEG framework | RAN4, CATT |
| R1-2208352 | Reply LS for the minimum guard period between two SRS resources for antenna switching | RAN4, CATT |
| R1-2208353 | LS Reply on UE antenna gain for NR NTN coverage enhancement | RAN4, Ericsson |
| R1-2208354 | LS on active TCI state list for UL TCI | RAN4, Nokia |
| R1-2208355 | Reply LS on SSB measurement for L1-RSRP on inter-cell beam management | RAN4, Samsung |
| R1-2208384 | On the incoming RAN2 LS R1-2205728 on IUC and non-preferred resources | FUTUREWEI |
| R1-2208414 | Discussion on DMRS bundling | Huawei, HiSilicon |
| R1-2208415 | Draft Reply LS to RAN1/RAN2 on DMRS bundling | Huawei, HiSilicon |
| R1-2208532 | Draft reply LS on active TCI list for UL TCI | Spreadtrum Communications |
| R1-2208579 | Draft Reply LS on support of positioning in FR2-2 | vivo |
| R1-2208580 | Draft Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | vivo |
| R1-2208581 | Draft Reply LS on MBS SPS configuration on SCell | vivo |
| R1-2208582 | Draft Reply LS on TCI assumption for RSSI measurement for FR2-2 | vivo |
| R1-2208583 | Draft reply LS on active TCI state list for UL TCI | vivo |
| R1-2208584 | Draft reply LS on Pemax,c of S-SSB transmission | vivo |
| R1-2208585 | Draft reply LS on Per-FS L1 feature for NR sidelink discovery BC-list | vivo |
| R1-2208586 | Draft reply LS on IUC with non-preferred resource set | vivo |
| R1-2208587 | [DRAFT] Reply LS on resource pool index in DCI Format 3_0 | vivo |
| R1-2208703 | Draft reply LS on TCI assumption for RSSI measurement for FR2-2 | ZTE, Sanechips |
| R1-2208714 | Draft reply LS on Pemax,c of S-SSB transmission | ZTE, Sanechips |
| R1-2208715 | Draft reply LS on IUC with non-preferred resource set | ZTE, Sanechips |
| R1-2208727 | LS on Per-FS L1 feature for NR sidelink discovery BC-list | RAN2, OPPO |
| R1-2208750 | Draft reply LS on active TCI state list for UL TCI | Lenovo |
| R1-2208757 | Draft reply LS to RAN4 on active TCI state list for UL TCI | ZTE |
| R1-2208758 | Discussion on issues raised in RAN4 LS on active TCI state list for UL TCI | ZTE |
| R1-2208799 | Discussion on LS on active TCI state list for UL TCI | OPPO |
| R1-2208804 | Draft reply LS on support of positioning in FR2-2 | OPPO |
| R1-2208807 | Discussion on the LS on IUC with non-preferred resource set | OPPO |
| R1-2208808 | Draft reply LS on IUC with non-preferred resource set | OPPO |
| R1-2208809 | Discussion on the LS on Per-FS L1 feature for NR sidelink discovery BC-list | OPPO |
| R1-2208810 | Draft reply LS on Per-FS L1 feature for NR sidelink discovery BC-list | OPPO |
| R1-2208811 | Discussion on the reply LS from RAN2 on priority for IUC | OPPO |
| R1-2208812 | Discussion on the LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | OPPO |
| R1-2208813 | Draft reply LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | OPPO |
| R1-2208814 | Discussion on resource pool index in DCI Format 3_0 for SL discovery | OPPO |
| R1-2208815 | Discussion on TP to TR37.985 for inclusion of SL relay description | OPPO |
| R1-2208888 | Draft reply LS on active TCI state list for UL TCI | LG Electronics |
| R1-2208909 | Discussion on support of positioning in FR2-2 | CATT |
| R1-2208910 | Draft reply LS on support of positioning in FR2-2 | CATT |
| R1-2208911 | Draft Reply LS on IUC with non-preferred resource set | CATT, GOHIGH |
| R1-2208912 | Discussion on Reply LS on IUC with non-preferred resource set | CATT, GOHIGH |
| R1-2208913 | Draft Reply LS on resource pool index in DCI Format 3_0 | CATT, GOHIGH |
| R1-2208914 | Draft Reply LS on TP to 37.985 | CATT, GOHIGH |
| R1-2208944 | Draft reply LS on active TCI state list for UL TCI | CATT |
| R1-2209171 | Draft reply LS on resource pool index in DCI Format 3_0 | ZTE, Sanechips |
| R1-2209172 | Discussion on resource pool index in DCI format 3_0 | ZTE, Sanechips |
| R1-2209181 | Discussion on reply LS from RAN4 on the minimum guard period between two SRS resources for antenna switching | Ericsson |
| R1-2209182 | Draft LS response on TCI assumption for RSSI measurement for FR2-2 | Ericsson |
| R1-2209183 | Discussion on LS response on TCI assumption for RSSI measurement for FR2-2 | Ericsson |
| R1-2209206 | Draft Reply LS on support of positioning in FR2-2 | ZTE |
| R1-2209207 | Discussion on support of positioning in FR2-2 for Rel-17 | ZTE |
| R1-2209208 | Draft Reply LS on Terminology Alignment for Sidelink Positioning | ZTE |
| R1-2209253 | [Draft] Reply LS on Per-FS L1 feature for NR sidelink discovery BC-list | xiaomi |
| R1-2209435 | Discussion on RAN4 LS on TCI assumption for RSSI measurement for FR2-2 | LG Electronics |
| R1-2209461 | Discussion on RAN4 LS on DMRS bundling | ZTE |
| R1-2209462 | [Draft] Reply LS to RAN4 on DMRS bundling | ZTE |
| R1-2209477 | Discussion on LS on Pemax,c of S-SSB transmission when multiple pools are configured in a carrier | LG Electronics |
| R1-2209552 | Discussion on RAN2 LS on IUC with Non-preferred Resource Set | Apple |
| R1-2209553 | Draft Reply LS to RNA2 on IUC with Non-preferred Resource Set | Apple |
| R1-2209554 | Draft reply LS on active TCI state list for UL TCI | Apple |
| R1-2209668 | [Draft] Reply to LS on Multicarrier Operation with DMRS Bundling | Ericsson |
| R1-2209687 | Draft reply LS on on active TCI state list for UL TCI | Samsung |
| R1-2209765 | Draft reply LS on Per-FS L1 feature for NR sidelink discovery BC-list | ZTE, Sanechips |
| R1-2209774 | Draft reply LS on TP to TR 37.985 | ZTE, Sanechips |
| R1-2209820 | Discussion on the RAN4 LS on L3-RSSI measurement | Huawei, HiSilicon |
| R1-2209842 | Discussion on support of positioning in FR2-2 | Huawei, HiSilicon |
| R1-2209843 | Discussion on terminology alignment for ranging/SL positioning | Huawei, HiSilicon |
| R1-2209844 | Discussion on LS on Per-FS L1 feature for NR sidelink discovery BC-list | Huawei, HiSilicon |
| R1-2209867 | Discussion on LS reply on TCI assumption for RSSI measurement for FR2-2 | NTT DOCOMO, INC. |
| R1-2210033 | [Draft] Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | xiaomi |
| R1-2210040 | Discussion on RAN4 LS on Pemax,c of S-SSB transmission | Nokia, Nokia Shanghai Bell |
| R1-2210091 | Draft reply LS on active TCI state list for UL TCI | Ericsson |
| R1-2210116 | [Draft] Reply LS on IUC with non-preferred resource set | Ericsson |
| R1-2210117 | Discussion on LS on IUC with non-preferred resource set | Ericsson |
| R1-2210118 | [Draft] Reply LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | Ericsson |
| R1-2210119 | Discussion on LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | Ericsson |
| R1-2210120 | [Draft] Reply LS on Per-FS L1 feature for NR sidelink discovery BC-list | Ericsson |
| R1-2210121 | [Draft] Reply LS on TP to TR 37.985 | Ericsson |
| R1-2210122 | Discussion on LS on TP to TR 37.985 | Ericsson |
| R1-2210123 | [Draft] Reply LS on resource pool index in DCI Format 3_0 | Ericsson |
| R1-2210180 | Multicarrier Operation with DMRS Bundling | Ericsson |
| R1-2210205 | Discussion on RAN2 LS on resource pool index in DCI format 3_0 | Huawei, HiSilicon |
| R1-2210206 | Discussion on LS on IUC with non-preferred resource set | Huawei, HiSilicon |
| R1-2210217 | Discussion LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | Huawei, HiSilicon |
| R1-2210218 | Discussion on the RAN4 LS on active TCI state list for UL TCI | Huawei, HiSilicon |
| R1-2210234 | Draft Reply to RAN2 LS on IUC with non-preferred resource set | Qualcomm Incorporated |
| R1-2210235 | Draft Reply to RAN2 LS on Per-FS L1 feature for NR sidelink discovery BC-list | Qualcomm Incorporated |
| R1-2210236 | Draft Reply to RAN4 LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier | Qualcomm Incorporated |
| R1-2210237 | Draft Reply on support of positioning in FR2-2 | Qualcomm Incorporated |
| R1-2210419 | Moderator Summary of [110bis-e-AI5-LSs-01] Email discussion on resource pool index in DCI Format 3_0 | Moderator (vivo) |
| R1-2210487 | Corrections on resource pool index | Moderator (vivo) |
| R1-2210493 | [DRAFT] Reply LS on TP to TR 37.985 | Huawei |
| R1-2210494 | Reply LS on TP to TR 37.985 | RAN1, Huawei |
| R1-2210524 | Corrections on resource pool index | Moderator (vivo), OPPO, Qualcomm, CATT, GOHIGH, Ericsson, Huawei, HiSilicon |
| R1-2210525 | Moderator's summary for [110bis-e-AI5-LSs-02] Email discussion on TP for TR37.985 | Moderator (Huawei) |
| R1-2210529 | [DRAFT] Reply LS on resource pool index in DCI Format 3_0 | vivo |
| R1-2210585 | Reply LS on resource pool index in DCI Format 3_0 | RAN1, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2208446 | Discussion on the collision of overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2208447 | Correction on the collision of overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2208533 | Collision of overlapped PUCCHs with repetition | Spreadtrum Communications |
| R1-2208730 | Clarification of CSI reporting (Rel-15) | Ericsson |
| R1-2208867 | Discussion on collision handling for overlapping PUCCHs with repetitions | OPPO |
| R1-2208915 | Collision handling of more than two overlapping PUCCHs with repetition | CATT |
| R1-2209030 | PUCCH collision handling for more than two overlapped PUCCHs with repetition | Intel Corporation |
| R1-2209184 | Discussion on PUSCH TDRA misalignment issue | ZTE, Sanechips |
| R1-2209185 | Correction on TDRA misalignment of PUSCH | ZTE, Sanechips |
| R1-2209254 | Corrections on the RSRP of the downlink pathloss reference for PRACH power control | xiaomi |
| R1-2209463 | Discussion on more than two overlapping PUCCHs with repetitions | ZTE |
| R1-2209512 | [R15] Draft CR on PDCCH monitoring of Type1-PDCCH CSS set for a DL BWP | MediaTek Inc. |
| R1-2209513 | [R16] Draft CR on PDCCH monitoring of Type1-PDCCH CSS set for a DL BWP | MediaTek Inc. |
| R1-2209514 | [R17] Draft CR on PDCCH monitoring of Type1-PDCCH CSS set for a DL BWP | MediaTek Inc. |
| R1-2209515 | On maximum supported CSI-RS Resource in beamManagementSSB-CSI-RS | MediaTek Inc. |
| R1-2209555 | On alignment of understanding for BM across multiple cells with different SCS | Apple |
| R1-2209556 | Draft LS on beamManagementSSB-CSI-RS | Apple |
| R1-2209688 | Discussion on more than two overlapping PUCCHs with repetitions | Samsung |
| R1-2209836 | On parallel transmission of PRACH and SRS/PUCCH/PUSCH | Huawei, HiSilicon |
| R1-2209848 | Discussion on SRS carrier switching | Huawei, HiSilicon |
| R1-2209849 | Correction on parallel transmission of PRACH and SRS/PUCCH/PUSCH | Huawei, HiSilicon |
| R1-2209932 | Issue on PUCCH overlapping with PUCCH with repetitions | Qualcomm Incorporated |
| R1-2209933 | Discussion on even and odd CSI subband index definition | Qualcomm Incorporated |
| R1-2209934 | Draft CR on Clarification on timelines for group power control command | Qualcomm Incorporated |
| R1-2210424 | [110bis-e-NR-R15-05] Email discussion summary for PDCCH monitoring of Type1-PDCCH CSS set for a DL BWP | Moderator (MediaTek Inc.) |
| R1-2210473 | [110bis-e-NR-R15-02] Discussion on clarification of CSI reporting | Moderator (Ericsson) |
| R1-2210490 | FL summary of email discussion on RSRP of the downlink pathloss reference for PRACH power control | Moderator (Xiaomi) |
| R1-2210526 | Summary of [110bis-e-NR-R15-06] Discussion on alignment of understanding for BM across multiple cells with different SCS | Moderator (Apple Inc.) |
| R1-2210546 | Summary of discussion on PUSCH TDRA misalignment issue | Moderator (ZTE) |
| R1-2210678 | Correction on parallel transmission of PRACH and SRS/PUCCH/PUSCH | Moderator (Huawei), Samsung, Nokia, Nokia Shanghai Bell |
| R1-2210716 | [110bis-e-NR-R15-08] - Discussion on timeline for group power control command | Moderator (Qualcomm Incorporated) |
| R1-2210740 | Summary of [110bis-e-NR-R15-01] Discussion on PUCCH collision handling for more than two overlapped PUCCHs with repetition | Moderator (Samsung) |
| R1-2210741 | Correction on overlapping PUCCHs with repetitions of a same priority | Moderator (Samsung) , Huawei, HiSilicon, OPPO, CATT, vivo, Intel, ZTE, Apple |
| R1-2210742 | Correction on overlapping PUCCHs with repetitions of a same priority | Moderator (Samsung) , Huawei, HiSilicon, OPPO, CATT, vivo, Intel, ZTE, Apple |
| R1-2210745 | Summary of [110bis-e-NR-R15-07] Discussion on parallel transmission of PRACH and SRS/PUCCH/PUSCH | Moderator (Huawei) |
| R1-2210746 | [Draft] LS on a Rel-17 RRC parameter intraBandNC-PRACH-simulTx-r17 | Huawei |
| R1-2210747 | LS on a Rel-17 RRC parameter intraBandNC-PRACH-simulTx-r17 | RAN1, Huawei |
| R1-2210771 | Correction on overlapping PUCCHs with repetitions of a same priority | Moderator (Samsung) , Huawei, HiSilicon, OPPO, CATT, vivo, Intel, ZTE, Apple |
| R1-2210772 | Correction on overlapping PUCCHs with repetitions of a same priority | Moderator (Samsung) , Huawei, HiSilicon, OPPO, CATT, vivo, Intel, ZTE, Apple |
| R1-2210776 | Correction on SCS configuration for parallel transmission of PRACH and SRS/PUCCH/PUSCH | Moderator (Huawei), Samsung |
| R1-2210777 | Correction on SCS configuration for parallel transmission of PRACH and SRS/PUCCH/PUSCH | Moderator (Huawei), Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2208458 | Correction on UL prioritization cases related to SP-CSI | Huawei, HiSilicon |
| R1-2208459 | Correction on Priority rules for CSI reports in TS 38.214 | Huawei, HiSilicon |
| R1-2208869 | Draft CR on subcarrier spacing for UE beam update after CBRA based BFR | |
| R1-2208870 | Draft CR on candidate beam detection reference signal | |
| R1-2209173 | Correction on SL BWP in TS 38.213 | ZTE, Sanechips |
| R1-2209464 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH for Rel-16 NR-U | ZTE |
| R1-2209465 | Correction on cancellation of PUSCH repetitions due to DAPS handover | ZTE |
| R1-2209557 | Clarification of aperiodic CSI report with dormant BWP | Apple |
| R1-2209558 | On Rel-16 UL Tx switching for PUCCH with HARQ-ACK | Apple |
| R1-2209689 | Draft CR for Intra-UE prioritization related to SP-CSI | Samsung |
| R1-2209690 | Discussion on Intra-UE prioritization related to SP-CSI | Samsung |
| R1-2209800 | On definition of defer duration and conditions of new back-off | Sharp, Ericsson |
| R1-2209829 | Correction on power control for PSCCH/PSSCH/PSFCH/S-SSB in TS 38.213 | Huawei, HiSilicon |
| R1-2209841 | Discussion on the PRS search window | Huawei, HiSilicon |
| R1-2209935 | Discussion on Rel-16 span-based PDCCH monitoring capability | Qualcomm Incorporated |
| R1-2209936 | Discussion on an issue on DL-PRS Search Window Definitions | Qualcomm Incorporated |
| R1-2210144 | [Draft CR] Clarification on intra-UE prioritization for PUSCH with SP-CSI | Nokia, Nokia Shanghai Bell |
| R1-2210172 | Maintenance for NR positioning support | Ericsson |
| R1-2210190 | Correction to UE type “SwitchedUL” and simultaneous transmission on two UL bands | Nokia, Nokia Shanghai Bell |
| R1-2210342 | Summary #1 of PRS Search Window Issue | Moderator (Qualcomm Incorporated) |
| R1-2210444 | Moderator Summary #1 of [110bis-e-NR-R16-06] Discussion on SL BWP | Moderator (ZTE) |
| R1-2210445 | Moderator Summary #2 of [110bis-e-NR-R16-06] Discussion on SL BWP | Moderator (ZTE) |
| R1-2210453 | Moderator summary of [110bis-e-NR-R16-13] discussion | Moderator (vivo) |
| R1-2210454 | Draft reply LS on Pemax,c of S-SSB transmission | Moderator (vivo) |
| R1-2210469 | Correction on SL BWP in TS 38.213 | ZTE, Sanechips |
| R1-2210470 | Correction on SL BWP in TS 38.213 | ZTE, Sanechips |
| R1-2210491 | Summary of [110bis-e-NR-R16-08] Discussion on the definition of defer duration and conditions of new back-off | Moderator (Sharp) |
| R1-2210498 | Summary of [110bis-e-NR-R16-03] Discussion on correction for cancellation of PUSCH repetitions due to DAPS handover | Moderator (ZTE) |
| R1-2210513 | Correction on SL BWP in TS 38.213 | Moderator (ZTE), Huawei, HiSilicon, Samsung, vivo, Ericsson, Nokia, Nokia Shanghai Bell, OPPO |
| R1-2210514 | Correction on SL BWP in TS 38.213 | Moderator (ZTE), Huawei, HiSilicon, Samsung, vivo, Ericsson, Nokia, Nokia Shanghai Bell, OPPO |
| R1-2210549 | Reply LS on Pemax,c of S-SSB transmission | RAN1, vivo |
| R1-2210613 | Correction on HARQ-ACK multiplexing on multi-PUSCHs without PUCCH for Rel-16 NR-U | Moderator (ZTE), Samsung |
| R1-2210614 | Correction on HARQ-ACK multiplexing on multi-PUSCHs without PUCCH for Rel-16 NR-U | Moderator (ZTE), Samsung |
| R1-2210615 | Moderator summary of [110bis-e-NR-R16-07] | Moderator (ZTE) |
| R1-2210618 | LS on DL PRS search window | RAN1, Qualcomm |
| R1-2210641 | Summary of [110bis-e-NR-R16-10] on UL Tx switching for PUCCH with HARQ-ACK | Moderator (Apple) |
| R1-2210644 | Summary of [110bis-e-NR-R16-11] UE type “SwitchedUL” and simultaneous transmission on two UL bands | Moderator (Nokia) |
| R1-2210653 | Summary of [110bis-e-NR-R16-09] Discussion on clarification of aperiodic CSI report with dormant BWP | Moderator (Apple Inc.) |
| R1-2210654 | CR on aperiodic CSI report with dormant BWP | Moderator (Apple), Samsung, Intel, vivo |
| R1-2210655 | CR on aperiodic CSI report with dormant BWP | Moderator (Apple), Samsung, Intel, vivo |
| R1-2210656 | CR on aperiodic CSI report with dormant BWP | Moderator (Apple), Samsung, Intel, vivo |
| R1-2210657 | CR on aperiodic CSI report with dormant BWP | Moderator (Apple), Samsung, Intel, vivo |
| R1-2210712 | Summary on 110bis-e-NR-R16-01 - Intra-UE prioritization related to SP-CSI | Moderator (Huawei) |
| R1-2210713 | Correction on UL prioritization cases related to SP-CSI | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2210714 | Correction on UL prioritization cases related to SP-CSI | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2210743 | Summary of Discussion on Span-Based PDCCH Monitoring Capability | Moderator (Qualcomm) |
| R1-2210784 | Rel-16 Corrections for sensing slot in channel access procedures | Ericsson |
| R1-2210785 | Rel-16 Corrections for sensing slot in channel access procedures (mirrored to Rel-17) | Ericsson |
| R1-2210788 | Rel-16 editorial corrections for TS 38.214 | Nokia |
| R1-2210789 | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | Nokia |
| R1-2210798 | Summary on email discussion 110bis-e-NR-R16-04 | Moderator (Google) |
| R1-2210799 | Summary on email discussion 110bis-e-NR-R16-05 | Moderator (Google) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210783 | Rel-17 editorial corrections for TS 38.213 | Samsung |
| R1-2210786 | Rel-17 editorial corrections for TS 38.212 | Huawei |
| R1-2210787 | Corrections to NR support of multicast and broadcast services | Ericsson |
| R1-2210790 | Rel-17 editorial corrections for TS 38.214 | Nokia |
| R1-2210794 | Editorial corrections to NB-IoT/eMTC support for Non-Terrestrial Networks | Motorola Mobility |
| TDoc | Title | Source |
|---|---|---|
| R1-2208340 | Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP PUCCH/PUSCH enhancement | Moderator (Nokia) |
| R1-2208474 | Correction on determination of two QCL-TypeD properties | Huawei, HiSilicon |
| R1-2208475 | Correction on PUCCH resource determination for HARQ-ACK | Huawei, HiSilicon |
| R1-2208534 | Draft CR on PL-RS for unified TCI framework | Spreadtrum Communications |
| R1-2208535 | Draft CR on PL-RS determination for CA case | Spreadtrum Communications |
| R1-2208536 | Correction on the indicated TCI state for uplink channel | Spreadtrum Communications |
| R1-2208588 | Discussion on the QCL assumption of the PDSCH not following the indicated TCI state | vivo |
| R1-2208589 | Draft CR on the QCL assumption of the PDSCH not following the indicated TCI state | vivo |
| R1-2208590 | Draft CR on the rate match mechanism for PDSCH for inter-cell beam measurement | vivo |
| R1-2208591 | Draft CR on the UE behavior when PDCCH candidate overlaps with SSBs for inter-cell beam measurement in the same REs | vivo |
| R1-2208592 | Correction on the CORESETs overlapping issue | vivo |
| R1-2208593 | Correction on the CORESETs overlapping issue for PDCCH repetition | vivo |
| R1-2208751 | Draft CR on beam indication of SRS resource on unified TCI framework to TS38.214 | Lenovo |
| R1-2208752 | Draft CR on M-TRP Type 1 configured grant PUSCH to TS38.214 | Lenovo |
| R1-2208753 | Draft CR on non codebook SRS resource on unified TCI framework to TS38.214 | Lenovo |
| R1-2208754 | Draft CR on reference of MAC CE in TS38.321 for SRS resource on unified TCI framework to TS38.214 | Lenovo |
| R1-2208755 | Draft CR on not activating two TCI states for CORESET#0 associated with SS#0 for Type 0/0A/2 CSS to TS38.213 | Lenovo |
| R1-2208756 | Draft CR on PHR with unified TCI in TS 38.213 | Lenovo |
| R1-2208759 | Draft CR on overlapping symbols between UL signals and non-serving cell SSB in TS 38.213 | ZTE |
| R1-2208760 | Draft CR on default QCL assumption in HST-SFN in TS 38.214 | ZTE |
| R1-2208761 | Draft CR on cross CC power control for unified TCI in TS 38.213 | ZTE |
| R1-2208762 | Draft CR on SRS closed loop power control shared with PUSCH in TS 38.213 | ZTE |
| R1-2208763 | Draft CR on UE capability parameter for mTRP-CSI in TS 38.214 | ZTE |
| R1-2208764 | Draft CR on SRS enhancement in TS 38.214 | ZTE |
| R1-2208789 | Corrections on TCI indication of CORESET not following unified TCI state | OPPO |
| R1-2208790 | Corrections on activated TCI state in Unified TCI framework | OPPO |
| R1-2208791 | Corrections on TCI indication of SRS in Unified TCI framework | OPPO |
| R1-2208871 | Clarification on active BWP for beam application time | |
| R1-2208889 | Draft CR on UL PC with common TCI state pool for CA | LG Electronics |
| R1-2208890 | Draft CR on Type0/0A/2 PDCCH CSS for HST-SFN | LG Electronics |
| R1-2208916 | Clarification of LI reporting for Further Enhanced Type II Port Selection CSI feedback | CATT |
| R1-2208917 | On default power control parameter determination for M-TRP PUSCH transmission | CATT |
| R1-2208918 | On joint DL/UL TCI state update in unified TCI framework | CATT |
| R1-2209133 | Draft CR on monitoring occasion for individual PDCCH candidate overlapping with one of PDCCH repetitions | NEC |
| R1-2209134 | Discussion on monitoring occasion for individual PDCCH candidate overlapping with one of PDCCH repetitions | NEC |
| R1-2209228 | Draft CR on QCL source for CSI-RS | NEC |
| R1-2209306 | Draft editorial CR on beam management for multi-TRP in TS38.213 | CMCC |
| R1-2209307 | Draft editorial CR on beam management for multi-TRP in TS38.214 | CMCC |
| R1-2209539 | Correction on beam activation and update for multiple CCs | |
| R1-2209550 | Clarification of LI bitwidth and mapping order of CSI fields for Further Enhanced Type II Port Selection CSI feedback | CATT |
| R1-2209559 | Maintenance on Further enhancements on MIMO for NR | Apple |
| R1-2209691 | Draft CR on inter-set guard period for SRS enhancement | Samsung |
| R1-2209824 | Correction on conflict resolution for PUSCH TCI-state | Huawei, HiSilicon |
| R1-2209825 | Correction on default power control parameters | Huawei, HiSilicon |
| R1-2209826 | Corrections on default beam of CSI-RS for MTRP beam management in 38.214 | Huawei, HiSilicon |
| R1-2209846 | Correction on codebook mode indication for Rel-17 NCJT CSI measurement | Huawei, HiSilicon |
| R1-2209847 | Correction on codebook mode indication for Rel-17 NCJT CSI measurement | Huawei, HiSilicon |
| R1-2209937 | Draft CR on default beam with unified TCI for cross-carrier scheduling | Qualcomm Incorporated |
| R1-2209938 | Draft CR on SRS power control parameters with unified TCI | Qualcomm Incorporated |
| R1-2209939 | Draft CR on reset accumulation of TPC adjustment state for unified TCI | Qualcomm Incorporated |
| R1-2210056 | Draft CR 38.213 Rel-17 CORESET Configured with CSS and Follow Unified TCI State | Nokia, Nokia Shanghai Bell |
| R1-2210057 | Draft CR 38.214 Rel-17 multi-beam enhancements_beam switch HARQ | Nokia, Nokia Shanghai Bell |
| R1-2210058 | Draft CR 38.214 Rel-17 multi-beam enhancements_CG PUSCH type 1 | Nokia, Nokia Shanghai Bell |
| R1-2210059 | Draft CR on UL SRS Inter-slot GP time location for the first and/or last resource | Nokia, Nokia Shanghai Bell |
| R1-2210076 | Draft CR on SFN dynamic switching | Ericsson,Qualcomm |
| R1-2210077 | Draft CR on default UL beam setup for SFN PDCCH | Ericsson |
| R1-2210079 | Draft CR for TCI state parameter name alignment in TS 38.213 | ASUSTeK |
| R1-2210081 | Draft CR for TCI state parameter name alignment in TS 38.214 | ASUSTeK |
| R1-2210083 | Correction on indicated TCI state | ASUSTeK |
| R1-2210088 | Draft CR to 38.213 on UL TCI state parameter naming | Ericsson |
| R1-2210089 | Draft CR to 38.214 on UL TCI state parameter naming | Ericsson |
| R1-2210090 | Draft CR to 38.213 on unified TCI for PDSCH | Ericsson |
| R1-2210103 | Draft CR to 38.214 on aperiodic CSI reporting on PUSCH | Ericsson |
| R1-2210202 | Correction on DCI based TCI indication for cross carrier scheduling | Huawei, HiSilicon |
| R1-2210215 | Clarifying the ambiguous usage of TCI-State | Huawei, HiSilicon |
| R1-2210216 | UL TCI state parameter name alignment | Huawei, HiSilicon |
| R1-2210389 | Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management (Round 1) | Moderator (CATT) |
| R1-2210401 | Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 0) | Moderator (Intel Corporation) |
| R1-2210402 | Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 1) | Moderator (Intel Corporation) |
| R1-2210418 | Moderator Summary on Rel-17 FeMIMO maintenance for SRS in preparation phase | Moderator (ZTE) |
| R1-2210429 | Moderator Summary on Rel-17 FeMIMO maintenance for SRS in preparation phase | Moderator (ZTE) |
| R1-2210438 | Moderator Summary for Rel.17 NR FeMIMO maintenance: multi-beam | Moderator (ZTE) |
| R1-2210439 | Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2210499 | Moderator Summary for Rel.17 NR FeMIMO maintenance: CSI Enhancement (Round 0) | Moderator (Huawei) |
| R1-2210500 | Moderator Summary for Rel.17 NR FeMIMO maintenance: CSI Enhancement (Round 1) | Moderator (Huawei) |
| R1-2210501 | Correction on LI reporting for Further Enhanced Type II Port Selection CSI feedback | Moderator (Huawei), CATT, Samsung |
| R1-2210502 | Correction on LI reporting for Further Enhanced Type II Port Selection CSI feedback | Moderator (Huawei), CATT, Samsung |
| R1-2210515 | Moderator summary on email discussion on incoming RAN4 LS in R1-2208354 on active TCI state list for UL TCI | Moderator (Nokia) |
| R1-2210516 | Draft CR for TCI state parameter name alignment in TS 38.213 | Moderator (ZTE), ASUSTeK, Ericsson |
| R1-2210517 | Draft CR for TCI state parameter name alignment in TS 38.214 | Moderator (ZTE), ASUSTeK, Lenovo, Ericsson, Huawei, Hisilicon |
| R1-2210518 | Draft CR on reference of MAC CE in TS38.321 for SRS resource on unified TCI framework to TS38.214 | Moderator (ZTE), Lenovo |
| R1-2210519 | On joint DLUL TCI state update in unified TCI framework | Moderator (ZTE), CATT |
| R1-2210520 | Correction on beam activation and update for multiple CCs | Moderator (ZTE), Google |
| R1-2210521 | Clarifying ambiguous usage of TCI-State | Moderator (ZTE), Huawei, HiSilicon |
| R1-2210551 | Draft CR on SRS enhancement in TS 38.214 | Moderator (ZTE), ZTE, CATT, Intel, Samsung |
| R1-2210552 | FL Summary on Rel-17 FeMIMO maintenance for SRS in Round 1 | Moderator (ZTE) |
| R1-2210586 | Summary of [110bis-e-R17-MIMO-03] Email discussion on miscellaneous corrections on DL mTRP for alignment CRs | Moderator (Qualcomm) |
| R1-2210704 | CR on PHR with unified TCI in TS 38.213 | Moderator(ZTE), Lenovo, Samsung |
| R1-2210719 | Reply LS on active TCI state list for UL TCI | RAN1, Nokia |
| R1-2210754 | Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2210755 | Correction on Type 1 configured grant PUSCH transmission associated with two SRS resource sets | Moderator (Nokia), Samsung, Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R1-2208463 | Remaining issues of channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2208464 | Discussion on the type 1 HARQ codebook generation for multiple PDSCH scheduling | Huawei, HiSilicon |
| R1-2208476 | Corrections to multi beam channel access in TS37.213 | Huawei, HiSilicon |
| R1-2208477 | Corrections to channel access field in RAR UL grant in FR2-2 in TS38.213 | Huawei, HiSilicon |
| R1-2208594 | Correction on the short control signaling constraint | vivo |
| R1-2208595 | Correction on the indication of channel access Types | vivo |
| R1-2208596 | Correction on the parameter indicating the number of PRBs for common PUCCH | vivo |
| R1-2208597 | Correction on generation of Type-1 codebook with time domain bundling | vivo |
| R1-2208598 | Correction on RRC parameters for time domain bundling of HARQ-ACK for multi-PDSCH scheduling in TS38.213 | vivo |
| R1-2208680 | Remaining issues for NR 52.6 GHz to 71 GHz | InterDigital, Inc. |
| R1-2208681 | Corrections on a minimum guard period between two SRS resources for antenna switching | InterDigital, Inc. |
| R1-2208704 | Correction on on ChannelAccess-Cpext in RAR UL Grant in TS 38.213 | ZTE, Sanechips |
| R1-2208705 | Clarification on Contention Exempt Short Control Signalling rules for UL in TS 37.213 | ZTE, Sanechips |
| R1-2208706 | Alignment CR on the parameter names in TS 38.213 | ZTE, Sanechips |
| R1-2208707 | Alignment CR on the parameter names in TS 38.214 | ZTE, Sanechips |
| R1-2208708 | Correction on frequency resource for CSI-RS for tracking in TS 38.214 | ZTE, Sanechips |
| R1-2208709 | Correction on UE PUSCH preparation procedure time in TS 38.214 | ZTE, Sanechips |
| R1-2208710 | Draft CR on multi-slot PDCCH monitoring for TS 38.213 | ZTE, Sanechips |
| R1-2208826 | Discussion on remaining issue short control signaling | OPPO |
| R1-2208827 | Draft CR on resolving issue for short control signaling | OPPO |
| R1-2208828 | Draft CR on editorial correction for higher-layer parameter setting | OPPO |
| R1-2208931 | Discussion corrections for BD/CCE budge of scheduling cell(s) for the features extending NR operation to 71 GHz | CATT |
| R1-2208932 | Correction on BD/CCE budge of scheduling cell(s) for the features extending NR operation to 71 GHz | CATT |
| R1-2208933 | Correction on the total serving cell(s) number when r17monitoringcapability of monitoringCapabilityConfig is configured for the features extending NR operation to 71 GHz | CATT |
| R1-2208934 | Discussion on channel access procedures upon detection of a common DCI for frequency range 2-2 | CATT |
| R1-2208935 | Correction on channel access procedures upon detection of a common DCI for frequency range 2-2 | CATT |
| R1-2208936 | Discussion on PDCCH monitoring occasion for DCI format 2_1 for the features extending NR operation to 71 GHz | CATT |
| R1-2208937 | CR for PDCCH monitoring occasion for DCI format 2_1 for the features extending NR operation to 71 GHz | CATT |
| R1-2209005 | Correction on minimum guard period Y between two SRS resources of an SRS resource set for antenna switching | Fujitsu |
| R1-2209006 | Correction on Type-1 HARQ-ACK codebook determination in TS 38.213 | Fujitsu |
| R1-2209007 | Discussion on Type-1 HARQ-ACK codebook | Fujitsu |
| R1-2209031 | Discussion on Applicability of the Short Control Signalling Exemption | Intel Corporation |
| R1-2209032 | [draft] correction for short control signaling LBT exemption applicability in TS 37.213 | Intel Corporation |
| R1-2209177 | Draft CR on Group 2 search space configuration | Ericsson |
| R1-2209178 | Discussion on Group 2 search space configuration | Ericsson |
| R1-2209179 | Draft CR on minimum guard period between SRS resources | Ericsson |
| R1-2209180 | Discussion on minimum guard period between SRS resources | Ericsson |
| R1-2209250 | Correction on the bit length of ChannelAccess-CPext-CAPC field in DCI 0-1 and DCI 1-1 for FR 2-2 | xiaomi |
| R1-2209430 | Remaining issues on channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2209432 | Correction on ChannelAccess-Cpext field in random access response | Nokia, Nokia Shanghai Bell |
| R1-2209436 | Draft CR for indicating GSCN ranges where CD-SSB does not exist using NCD-SSB in FR2-2 | LG Electronics |
| R1-2209437 | Discussion on how to indicate GSCN ranges where CD-SSB does not exist using NCD-SSB in FR2-2 | LG Electronics |
| R1-2209438 | Draft CR for SSSG switching with multiple cells in FR2-2 | LG Electronics |
| R1-2209439 | Discussion on SSSG switching with multiple cells in FR2-2 | LG Electronics |
| R1-2209440 | Draft CR for RRC parameter to disable DMRS FD-OCC in FR2-2 | LG Electronics |
| R1-2209441 | Draft CR for type-1 HARQ-ACK codebook when time domain bundling is configured | LG Electronics |
| R1-2209442 | Discussion on type-1 HARQ-ACK codebook when time domain bundling is configured | LG Electronics |
| R1-2209443 | Draft CR on RRC parameters for HARQ-ACK time domain bundling | LG Electronics |
| R1-2209444 | Remaining issues of channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2209445 | Draft CR for multi-beam channel access procedure in FR2-2 | LG Electronics |
| R1-2209446 | Discussion on multi-beam channel access procedure in FR2-2 | LG Electronics |
| R1-2209447 | Draft CR on channel access indication for RAR grant in FR2-2 | LG Electronics |
| R1-2209692 | Draft CR for ChannelAccess-Cpext in RAR UL grant in FR2-2 | Samsung |
| R1-2209693 | Draft CR for multi-beam channel access procedure in FR2-2 | Samsung |
| R1-2209694 | Discussion on multi-PDSCH/PUSCH scheduling by a single DCI | Samsung |
| R1-2209695 | Draft CR to support up to 32 HARQ process numbers | Samsung |
| R1-2209696 | Draft CR for ZP CSI-RS rate-matching | Samsung |
| R1-2209818 | Corrections on Type 1 HARQ codebook generation in TS38.213 | Huawei, HiSilicon |
| R1-2209819 | Corrections to ED threshold for use with Type 2 channel access procedure in FR2-2 in TS37.213 | Huawei, HiSilicon |
| R1-2209821 | Corrections on SRS switching gap for 480/960KHz SCS for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2209845 | Corrections to per-beam ED threshold for multi-beam COT in FR2-2 in TS37.213 | Huawei, HiSilicon |
| R1-2209868 | Draft CR on spatial domain filter for sensing in FR2-2 | NTT DOCOMO, INC. |
| R1-2209869 | Draft CR on SRS for DL CSI acquisition in FR2-2 | NTT DOCOMO, INC. |
| R1-2209870 | Draft CR on DL PDSCH validity for multi-PDSCH scheduling via single DCI mTRP in FR2-2 | NTT DOCOMO, INC. |
| R1-2209871 | Discussion on remaining issues for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2209940 | Draft CR on unified short control signaling exemption and channel access type upgrade | Qualcomm Incorporated |
| R1-2209941 | Draft CR on ChannelAccess-Cpext field in UL RAR grant | Qualcomm Incorporated |
| R1-2209942 | Draft CR on UL transmission with LBT per sensing beam | Qualcomm Incorporated |
| R1-2209943 | Draft CR on EDT determination rule for COT with SDM or TDM transmission with per beam LBT | Qualcomm Incorporated |
| R1-2209944 | Discussion paper on Maintenance for NR from 52.6GHz to 71 GHz | Qualcomm Incorporated |
| R1-2210053 | Correction on UE resuming a UE initiated COT | Nokia, Nokia Shanghai Bell |
| R1-2210055 | Correction on Short Control Signaling | Nokia, Nokia Shanghai Bell |
| R1-2210094 | Correction on CSI-RS validation | ASUSTeK |
| R1-2210135 | Remaining issue on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2210136 | Draft CR on channel access after failure of Type 2 channel access for FR2-2 | WILUS Inc. |
| R1-2210137 | Draft CR on channel access procedure upon detection of a common DCI for FR2-2 | WILUS Inc. |
| R1-2210168 | Draft CR on channel access type indication in non-fallback DCI | NTT DOCOMO, INC. |
| R1-2210220 | Corrections on TDRA for multiple PUSCH scheduling in TS38.214 | Huawei, HiSilicon |
| R1-2210221 | Corrections on TDRA for multiple PUSCH scheduling in TS38.212 | Huawei, HiSilicon |
| R1-2210270 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2210313 | Discussion Summary #1 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2210328 | FL Summary for AI 8.2 – Enhancements for PUCCH Formats 0/1/4 | Moderator (Ericsson) |
| R1-2210347 | Summary of issues on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2210363 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2210391 | FL Summary on Maintenance of Channel Access Mechanisms for NR in 52.6 to 71GHz band | Moderator (Qualcomm) |
| R1-2210392 | Summary of preparation phase email discussion for maintenance of NR in 52.6 to 71GHz band | Moderator (Qualcomm) |
| R1-2210393 | Summary#1 on email discussion on maintenance of channel access for NR in 52.6 to 71GHz band | Moderator (Qualcomm) |
| R1-2210394 | Summary#2 on email discussion on maintenance of channel access for NR in 52.6 to 71GHz band | Moderator (Qualcomm) |
| R1-2210395 | FL summary #1 of PDSCH/PUSCH enhancement (RS and timeline) | Moderator (vivo) |
| R1-2210409 | FL Summary for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2210457 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2210458 | FL summary #1 for email discussion [110bis-e-R17-FR2-2-04] on PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2210459 | FL summary #2 for email discussion [110bis-e-R17-FR2-2-04] on PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2210460 | DRAFT LS to RAN2 on RRC parameter impact for multi-PDSCH scheduling | Moderator (LG Electronics) |
| R1-2210462 | FL Summary#2 for AI 8.2 – Enhancements for PUCCH Formats 0/1/4 | Moderator (Ericsson) |
| R1-2210471 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2210531 | Correction for ChannelAccess-Cpext in RAR UL grant in FR2-2 | Qualcomm (Moderator), Samsung, LG Electronics, DoCoMo, Huawei/HiSilicon, ZTE/Sanechips |
| R1-2210532 | Correction for ChannelAccess-Cpext in RAR UL grant in FR2-2 | Moderator (Qualcomm), Samsung, LG Electronics, NTT DOCOMO, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210533 | Correction on channel access type indication in non-fallback DCI | Moderator (Qualcomm), NTT DOCOMO, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210534 | Correction on channel access type indication in non-fallback DCI | Moderator (Qualcomm), NTT DOCOMO, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210535 | Correction on spatial domain filter for sensing for SRS transmission in FR2-2 | Moderator (Qualcomm), NTT DOCOMO, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210536 | Correction on spatial domain filter for sensing for SRS transmission in FR2-2 | Moderator (Qualcomm), NTT DOCOMO, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210537 | Correction on spatial domain filter for sensing for PUCCH transmission in FR2-2 | Moderator (Qualcomm), NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210538 | Correction on spatial domain filter for sensing for PUCCH transmission in FR2-2 | Moderator (Qualcomm), NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, Sanechips |
| R1-2210539 | Correction for multi-slot PDCCH monitoring in FR2-2 | Moderator (Lenovo), ZTE, Sanechips, Ericsson |
| R1-2210540 | Correction for multi-slot PDCCH monitoring in FR2-2 | Moderator (Lenovo), ZTE, Sanechips, Ericsson |
| R1-2210541 | Correction for BD/CCE budget of scheduling cell(s) in FR2-2 | Moderator (Lenovo), CATT |
| R1-2210542 | Correction for BD/CCE budget of scheduling cell(s) in FR2-2 | Moderator (Lenovo), CATT |
| R1-2210543 | Correction for SSSG switching with multiple cells in FR2-2 | Moderator (Lenovo), LG Electronics |
| R1-2210568 | FL summary #1 on TCI assumption for RSSI measurement for FR2-2 | Moderator (Apple) |
| R1-2210569 | {Draft] Reply LS on TCI assumption for RSSI measurement for FR2-2 | Apple |
| R1-2210583 | Correction on frequency resource for CSI-RS for tracking in TS 38.214 | Moderator (vivo), ZTE, Sanechips |
| R1-2210584 | Correction on UE PUSCH preparation procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | Moderator (vivo), ZTE, Sanechips |
| R1-2210590 | Reply LS on TCI assumption for RSSI measurement for FR2-2 | RAN1, Apple |
| R1-2210591 | LS to RAN2 on RRC parameter impact for multi-PDSCH scheduling | RAN1, LG Electronics |
| R1-2210594 | Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2210603 | Correction to support up to 32 HARQ process numbers for FR2-2 | Moderator (LG Electronics), Samsung, ZTE |
| R1-2210604 | Correction to support up to 32 HARQ process numbers for FR2-2 | Moderator (LG Electronics), Samsung, ZTE |
| R1-2210605 | Correction on ZP CSI-RS rate-matching for multi-PDSCH scheduling | Moderator (LG Electronics), Samsung, ZTE |
| R1-2210606 | Correction on ZP CSI-RS rate-matching for multi-PDSCH scheduling | Moderator (LG Electronics), Samsung, ZTE |
| R1-2210607 | Correction on TDRA for multiple PUSCH scheduling in TS 38.214 | Moderator (LG Electronics), Huawei, HiSilicon, ZTE |
| R1-2210608 | Correction on TDRA for multiple PUSCH scheduling in TS 38.214 | Moderator (LG Electronics), Huawei, HiSilicon, ZTE |
| R1-2210609 | Correction on TDRA for multiple PUSCH scheduling in TS 38.212 | Moderator (LG Electronics), Huawei, HiSilicon, ZTE |
| R1-2210610 | Correction on TDRA for multiple PUSCH scheduling in TS 38.212 | Moderator (LG Electronics), Huawei, HiSilicon, ZTE |
| R1-2210642 | Correction on BD/CCE decoding with release-specific number of serving cell(s) for NR operation in FR2-2 | Moderator (Lenovo), CATT, Huawei, Ericsson |
| R1-2210643 | Correction on BD/CCE decoding with release-specific number of serving cell(s) for NR operation in FR2-2 | Moderator (Lenovo), CATT, Huawei, Ericsson |
| R1-2210663 | Correction on a minimum guard period between two SRS resources for antenna switching | Moderator (InterDigital, Inc.), Fujitsu, Ericsson, Huawei, HiSilicon, NTT DOCOMO, INC., Samsung, ZTE |
| R1-2210679 | Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) | Ad-Hoc Chair (Huawei) |
| R1-2210705 | Correction on a minimum guard period between two SRS resources for antenna switching | Moderator (InterDigital, Inc.), Fujitsu, Ericsson, Huawei, HiSilicon, NTT DOCOMO, INC., Samsung, ZTE |
| R1-2210766 | Correction on DL PDSCH validity for multi-PDSCH scheduling via single DCI mTRP in FR2-2 | Moderator (LG Electronics), NTT DOCOMO |
| R1-2210767 | Correction on DL PDSCH validity for multi-PDSCH scheduling via single DCI mTRP in FR2-2 | Moderator (LG Electronics), NTT DOCOMO, Fujitsu |
| TDoc | Title | Source |
|---|---|---|
| R1-2208465 | Discussion on PUCCH repetition with semi-static PUCCH cell switching | Huawei, HiSilicon |
| R1-2208473 | Correction for HP SPS HARQ-ACK colliding with LP HARQ-ACK | Huawei, HiSilicon |
| R1-2208599 | Correction on RRC parameters for enhanced Type-3 codebook in TS38.212 | vivo |
| R1-2208600 | Correction on RRC parameters for enhanced Type-3 codebook in TS38.213 | vivo |
| R1-2208864 | Draft CR on e-type 3 HARQ codebook | OPPO |
| R1-2208865 | Draft CR on HARQ-ACK retransmission | OPPO |
| R1-2208866 | Draft CR on intra-UE multiplexing | OPPO |
| R1-2208938 | Discussion on simultaneous configuration of semi-static PUCCH cell switch and PUCCH repetitions | CATT |
| R1-2209033 | Remaining issue for Intra-UE Uplink Channel Multiplexing and Prioritization | Intel Corporation |
| R1-2209034 | Correction on CSI on LP PUSCH with CG-UCI | Intel Corporation |
| R1-2209448 | Remaining issues on HARQ-ACK feedback enhancements | LG Electronics |
| R1-2209466 | Discussion on remaining issue of PUCCH cell switching | ZTE |
| R1-2209467 | Draft CR for multiplexing for SPS HARQ-ACK | ZTE |
| R1-2209560 | Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC | Apple |
| R1-2209697 | Draft CR for PUCCH power control for multiplexing HARQ-ACK of different priorities in a PUCCH | Samsung |
| R1-2209698 | Draft CR for overlapping of a HP PUCCH with SPS PDSCH HARQ-ACK and a LP PUCCH with HARQ-ACK | Samsung |
| R1-2209699 | Draft CR for SPS HARQ-ACK deferral | Samsung |
| R1-2209700 | Discussion on the timeline of determining SPS HARQ-ACK deferral | Samsung |
| R1-2209945 | Correction for joint operation of semi-static PUCCH cell switch and PUCCH repetitions | Qualcomm Incorporated |
| R1-2209946 | Discussion on timeline for PUCCH cell switch with Scell activation, deactivation, and dormancy | Qualcomm Incorporated |
| R1-2210027 | Correction on UCI multiplexing with different priority indexes | ITRI |
| R1-2210028 | Correction on coding scheme for HARQ-ACK with small block length | ITRI |
| R1-2210142 | Correction on semi-static PUCCH cell switching and PUCCH repetitions | Ericsson |
| R1-2210145 | [Draft CR] Correction on PUCCH cell switching | Nokia, Nokia Shanghai Bell |
| R1-2210146 | On semi-static PUCCH cell switching and PUCCH repetition operation | Nokia, Nokia Shanghai Bell |
| R1-2210147 | [Draft CR] Correction on semi-static PUCCH cell switching and PUCCH repetitions | Nokia, Nokia Shanghai Bell |
| R1-2210148 | Accompanying discussions on draft CRs to 38.213 on Rel-17 URLLC / IIoT Intra-UE Multiplexing/Prioritization | Nokia, Nokia Shanghai Bell |
| R1-2210149 | [Draft CR] Handling of PUCCH with high-priority HARQ-ACK and HP SR overlapping with a PUCCH with low-priority HARQ-ACK | Nokia, Nokia Shanghai Bell |
| R1-2210150 | [Draft CR] Handling of high-priority PUCCH with SPS PDSCH HARQ-ACK only overlapping with a low-priority PUCCH with HARQ-ACK | Nokia, Nokia Shanghai Bell |
| R1-2210464 | Summary#1 on intra-UE multiplexing/prioritization B | Moderator (OPPO) |
| R1-2210465 | Summary#1 for email discussion [110bis-e-R17-IIoT-URLLC-02] | Moderator (OPPO) |
| R1-2210466 | Draft CR on multiplexing for SPS HARQ-ACK | Moderator (OPPO), Samsung, LGE, Huawei, HiSilicon, OPPO, ZTE, Nokia, Nokia Shanghai Bell |
| R1-2210467 | Draft CR on CSI on LP PUSCH with CG-UCI | Moderator (OPPO), Intel Corp, Qualcomm, Ericsson, Samsung |
| R1-2210530 | Correction on enhanced Type 3 HARQ-ACK codebook and HARQ-ACK re-transmission triggering | Moderator (Nokia), OPPO |
| R1-2210626 | Correction on enhanced Type 3 HARQ-ACK codebook and HARQ-ACK re-transmission triggering | Moderator (Nokia), OPPO |
| R1-2210632 | CR on multiplexing for SPS HARQ-ACK | Moderator (OPPO), Samsung, LGE, Huawei, HiSilicon, OPPO, ZTE, Nokia, Nokia Shanghai Bell |
| R1-2210639 | Draft CR on power control for PUCCH | Moderator (OPPO), Apple, Samsung, Ericsson |
| R1-2210640 | Draft CR on priority of CG-UCI | Moderator (OPPO), ITRI, Huawei, HiSilicon, LG Electronics, Ericsson |
| R1-2210676 | CR on power control for PUCCH | Moderator (OPPO), Apple, Samsung, Ericsson |
| R1-2210677 | CR on priority of CG-UCI | Moderator (OPPO), ITRI, Huawei, HiSilicon, LG Electronics, Ericsson |
| R1-2210720 | Moderator summary: Maintenance of HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2210773 | CR on CSI on LP PUSCH with CG-UCI | Moderator (OPPO), Intel Corp, Qualcomm, Ericsson, Samsung |
| R1-2210774 | Correction of PUCCH repetition for semi-static PUCCH cell switching | Moderator (Nokia), Nokia Shanghai Bell, ZTE, Ericsson, New H3C |
| TDoc | Title | Source |
|---|---|---|
| R1-2208829 | Discussion on remaining issue for NTN-NR | OPPO |
| R1-2208830 | Draft CR on interpretation SFN indicating epoch time | OPPO |
| R1-2208886 | Draft CR on the indication of downlink disabled HARQ feedback for NR NTN | vivo |
| R1-2208993 | Correction on determination of the number of HARQ-ACK information bits for NTN | Langbo |
| R1-2208994 | Correction on Type-2 HARQ-ACK codebook in PUSCH for NTN | Langbo |
| R1-2209654 | On the validity of assistance information for R17 NR NTN | Ericsson |
| R1-2209823 | Correction on timing relationship parameter for NR NTN | Huawei, HiSilicon |
| R1-2210019 | Remaining issues on solutions for NR to support NTN | Lenovo |
| R1-2210045 | Additional aspects of Rel-17 maintenance for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2210046 | Draft CR for 38.211 to ensure correct interworking between open and closed loop TA | Nokia, Nokia Shanghai Bell |
| R1-2210047 | Draft CR for 38.213 to capture correct validity timer expiry behavior for UL synchronization | Nokia, Nokia Shanghai Bell |
| R1-2210048 | Draft CR for 38.213 to clarify calculation and application of timing advance values for common TA and UE specific TA | Nokia, Nokia Shanghai Bell |
| R1-2210436 | Summary of [110bis-e-R17-NR-NTN-01] Email discussion to determine maintenance issues to be handled in RAN1#110bis-e | Moderator (Thales) |
| R1-2210580 | Summary#1 of [110bis-e-R17-NR-NTN-02] Email discussion for maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN for issues 1-6, 1-1 and 1-4. | Moderator (Thales) |
| R1-2210581 | Summary#2 of [110bis-e-R17-NR-NTN-02] Email discussion for maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN for issues 1-6, 1-1 and 1-4. | Moderator (Thales) |
| R1-2210587 | Summary#1 of maintenance on HARQ for Rel-17 NR-NTN | Moderator (ZTE) |
| R1-2210588 | CR on the Type-2 HARQ-ACK codebook | Moderator (ZTE) |
| R1-2210589 | CR on the Type-2 HARQ-ACK codebook | Moderator (ZTE), Ericsson, Nokia, Thales |
| R1-2210680 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208472 | Maintenance of Rel-17 NR positioning | Huawei, HiSilicon |
| R1-2208601 | Correction on missing of DL PRS-RSRPP | vivo |
| R1-2208602 | Correction on description alignment of ‘DL signals and channels‘ | vivo |
| R1-2208603 | Correction on description of LoS/NLoS indicator | vivo |
| R1-2208604 | Correction on SCS for NR DL PRS | vivo |
| R1-2208731 | Maintenance of NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
| R1-2208732 | Correction on PRS RSTD and PRS RSRPP reporting | Nokia, Nokia Shanghai Bell |
| R1-2208733 | Correction on SRS for positioning switching time | Nokia, Nokia Shanghai Bell |
| R1-2208734 | Correction on DL PRS subcarrier spacings for FR2-2 | Nokia, Nokia Shanghai Bell |
| R1-2208939 | Correction on UE Tx TEG association information reporting | CATT |
| R1-2208940 | Discussion on UE Tx TEG association information reporting | CATT |
| R1-2209209 | Draft CR on collision in PPW for inter-band case | ZTE |
| R1-2209210 | Draft CR on priority issue in PPW | ZTE |
| R1-2209211 | Draft CR on UE TEG framework | ZTE |
| R1-2209458 | Alignment CR on positioning for 38.214 | ZTE |
| R1-2209701 | Discussion on SSB priority on PRS | Samsung |
| R1-2209702 | Draft CR for SSB priority on PRS | Samsung |
| R1-2209703 | Discussion on SRS collision timeline check in inactive state | Samsung |
| R1-2209704 | Draft CR for SRS collision timeline check in inactive state | Samsung |
| R1-2209705 | Discussion on PRS collision handling for UL signals in PPW | Samsung |
| R1-2209706 | Draft CR for PRS collision handling for UL signals in PPW | Samsung |
| R1-2209837 | Correction to the Rx beam reporting condition for DL-AoD | Huawei, HiSilicon |
| R1-2209838 | Correction to the collision timeline for PRS and UL - 38.214 | Huawei, HiSilicon |
| R1-2209839 | Correction to the collision timeline for PRS and UL - 38.213 | Huawei, HiSilicon |
| R1-2209840 | Correction to the PRS processing window | Huawei, HiSilicon |
| R1-2210101 | Draft CR to 38.214 on definition of UE Tx TEG | Ericsson |
| R1-2210211 | Adding DL PRS-RSRPP to the applicable measurements | Huawei, HiSilicon |
| R1-2210212 | Correction to the applied positioning method for RSRP and RSRPP reporting | Huawei, HiSilicon |
| R1-2210213 | Correction to numerology and CP for positioning in RRC_INACTIVE state | Huawei, HiSilicon |
| R1-2210266 | Summary for preparation phase on maintenance of Rel-17 WI on NR positioning enhancements | Moderator (CATT) |
| R1-2210435 | FL Summary for maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2210461 | Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2210477 | Feature Lead Summary #1 for maintenance on accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2210478 | Feature Lead Summary #2 for maintenance on accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2210527 | Summary of discussion on incoming RAN2 LS in R1-2208325 on the support of positioning in FR2-2 | Moderator (Samsung) |
| R1-2210528 | Reply LS on support of positioning in FR2-2 | RAN1, Samsung |
| R1-2210557 | Summary #1 of [110bis-e-R17-ePos-06] positioning latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2210558 | Summary #2 of [110bis-e-R17-ePos-06] positioning latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2210559 | [draft] Correction on SRS for positioning switching time | Moderator (Huawei), Nokia, Nokia Shanghai Bell |
| R1-2210560 | Correction on SRS for positioning switching time | Moderator (Huawei), Nokia, Nokia Shanghai Bell |
| R1-2210595 | Correction on DL PRS subcarrier spacings for FR2-2 | Moderator (Samsung), Nokia, Nokia Shanghai Bell, vivo |
| R1-2210627 | Correction adding DL PRS-RSRPP to the applicable measurements | Moderator (Ericsson), vivo, Huawei, HiSilicon |
| R1-2210628 | Correction to the Rx beam reporting condition for DL-AoD | Moderator (Ericsson), Huawei, HiSilicon |
| R1-2210634 | Correction adding DL PRS-RSRPP to the applicable measurements | Moderator (Ericsson), vivo, Huawei, HiSilicon |
| R1-2210635 | Correction to the Rx beam reporting condition for DL-AoD | Moderator (Ericsson), Huawei, HiSilicon |
| R1-2210681 | Session notes for 8.5 (Maintenance on NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2210736 | [Draft] CR on UE TEG framework | Moderator (CATT), ZTE |
| R1-2210737 | CR on UE TEG framework | Moderator (CATT), ZTE |
| R1-2210759 | Draft CR on collision in Type 1B and Type 2 PPW for FR2 inter-band case | Moderator (Huawei), ZTE |
| R1-2210760 | CR on collision in Type 1B and Type 2 PPW for FR2 inter-band case | Moderator (Huawei), ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2208360 | Corrections and clarifications of RedCap UE procedures | Ericsson |
| R1-2208537 | Corrections on Support of Reduced Capability NR Devices | Spreadtrum Communications |
| R1-2208605 | Correction on invalid symbol determination for PUSCH repetition type B for HD-FDD | vivo, Sharp, Intel, Nokia, Nokia Shanghai Bell |
| R1-2208941 | Correction on QCL relationship between NCD-SSB and CD-SSB | CATT |
| R1-2209164 | Alignment between RAN1 and RAN2 specifications | NEC |
| R1-2209186 | Discussion on RedCap remaining issues | ZTE, Sanechips |
| R1-2209187 | Correction on NCD-SSB related spec for RedCap in TS38213 | ZTE, Sanechips |
| R1-2209188 | Correction on NCD-SSB related spec for RedCap in TS38214 | ZTE, Sanechips |
| R1-2209189 | Correction on TDRA misalignment of PUSCH for RedCap | ZTE, Sanechips |
| R1-2209222 | Draft CR on NCD-SSB in an active BWP | Lenovo |
| R1-2209429 | Editorial corrections for RedCap in TS 38.213 | Nokia, Nokia Shanghai Bell |
| R1-2209431 | Corrections on UE assumptions when configured with NCD-SSB | Nokia, Nokia Shanghai Bell |
| R1-2209778 | Discussion on available slot determination for PUSCH repetition type A and TBoMS for HD-UE | Sharp |
| R1-2209779 | Corrections on available slot determination for PUSCH repetition type A and TBoMS for HD-UE | Sharp, vivo, Nokia, Nokia Shanghai Bell, Intel |
| R1-2209850 | Correction on NCD-SSB for RedCap UE | Huawei, HiSilicon |
| R1-2209947 | Remaining issues on procedures of RedCap UE | Qualcomm Incorporated |
| R1-2210245 | FL summary #1 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2210246 | FL summary #2 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2210247 | FL summary #3 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2210629 | Corrections and clarifications of RedCap UE procedures | Moderator (Ericsson), Ericsson, Samsung, vivo, Spreadtrum, CATT, Nokia, Nokia Shanghai Bell, Intel, NEC |
| R1-2210630 | Correction on invalid symbol determination for PUSCH repetition type B for HD-FDD | Moderator (Ericsson), vivo, Sharp, Intel, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2210631 | Corrections on available slot determination for PUSCH repetition type A and TBoMS for HD-UE | Moderator (Ericsson), Sharp, vivo, Nokia, Nokia Shanghai Bell, Intel, Ericsson, Samsung |
| R1-2210636 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2210682 | Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208478 | Correction on TRS occasions for IDLE mode UE | Huawei, HiSilicon |
| R1-2208479 | Correction on power saving for IDLE mode UE | Huawei, HiSilicon |
| R1-2208606 | Correction on search space set group switching and PDCCH skipping | vivo |
| R1-2208607 | Correction on PDCCH monitoring adaptation and BWP switching | vivo |
| R1-2208838 | Remaining issues for DCI-based power saving adaptation | OPPO |
| R1-2208839 | Draft CR for or DCI-based power saving adaptation | OPPO |
| R1-2209190 | Discussion on remaining issues of PDCCH monitoring adaptation | ZTE, Sanechips |
| R1-2209191 | Correction on PDCCH monitoring adaptation | ZTE, Sanechips |
| R1-2209251 | Remaining issues of PDCCH monitoring adaptation for power saving | xiaomi |
| R1-2209252 | UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI | xiaomi |
| R1-2209373 | Open issues on Idle/Inactive mode power saving | Nokia, Nokia Shanghai Bell |
| R1-2209374 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2209375 | Clarification of virtual resource block mapping in respect of TRS-ResourceSet IE | Nokia, Nokia Shanghai Bell |
| R1-2209376 | Alignment of PDCCH skipping behaviour with SR | Nokia, Nokia Shanghai Bell |
| R1-2209377 | Completion of PDCCH monitoring adaptation behaviour and BWP switching | Nokia, Nokia Shanghai Bell |
| R1-2209815 | Discussion on UE behavior when PDCCH skipping received after a SR transmission | Huawei, HiSilicon |
| R1-2209816 | Correction on UE behavior when PDCCH skipping received after a SR transmission | Huawei, HiSilicon |
| R1-2209817 | Correction on PDCCH monitoring adaptation and BWP switching | Huawei, HiSilicon |
| R1-2209853 | Discussion on corrections for PDCCH monitoring adaptation | Ericsson |
| R1-2209854 | Correction for 38.213 on PDCCH skipping based monitoring adaptation | Ericsson |
| R1-2209855 | Correction for 38.213 on mixed Rel-16 and 17 SSSGS combinations | Ericsson |
| R1-2209856 | Correction for 38.213 on PDCCH monitoring adaptation field in a DCI indicating BWP change | Ericsson |
| R1-2209857 | Corrections for 38.214 on TRS occasions | Ericsson |
| R1-2210244 | Summary#1 for maintenance on UE power saving enhancements | Moderator (MediaTek Inc.) |
| R1-2210508 | Summary#2 for maintenance on UE power saving enhancements | Moderator (MediaTek Inc.) |
| R1-2210658 | Corrections on UE power saving enhancements for NR in TS 38.213 | Moderator (MediaTek), Ericsson, Nokia, Nokia Shanghai Bell, vivo, ZTE, Sanechips |
| R1-2210659 | Corrections on UE power saving enhancements for NR in TS 38.213 | Moderator (MediaTek), Ericsson, Nokia, Nokia Shanghai Bell, vivo, ZTE, Sanechips |
| R1-2210683 | Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2210738 | Summary#3 for maintenance on UE power saving enhancements | Moderator (MediaTek Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208608 | UE behavior of restarting DMRS bundling | vivo |
| R1-2208766 | Maintenance on Rel-17 NR coverage enhancements | China Telecom |
| R1-2208840 | Discussion on remaining issue of coverage enhancement | OPPO |
| R1-2208841 | Draft CR for coverage enhancement | OPPO |
| R1-2208942 | Correction on MCS determination of RAR grant | CATT |
| R1-2208943 | Discussion on UE behavior of restarting DMRS bundling | CATT |
| R1-2209035 | Discussion on remaining issues for DMRS bundling | Intel Corporation |
| R1-2209132 | Discussion on joint channel estimation for PUSCH and PUCCH | Panasonic |
| R1-2209226 | Remaining issues on joint channel estimation for Rel-17 NR coverage enhancements | Lenovo |
| R1-2209227 | Remaining issues on PUSCH repetition type A enhancement | Lenovo |
| R1-2209308 | Maintenance on NR coverage enhancement | CMCC |
| R1-2209468 | Correction on cancellation of PUSCH repetitions and TBoMS | ZTE |
| R1-2209532 | Discussion on RAN4 Reply LS for DMRS bundling | MediaTek Inc. |
| R1-2209561 | Discussion on RAN4 LS on DMRS bundling | Apple |
| R1-2209669 | Discussion on DMRS Bundling Restart | Ericsson |
| R1-2209707 | Maintenance on NR coverage enhancement | Samsung |
| R1-2209872 | Discussion on remaining issues for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2209948 | Discussion on remaining issues in NR Coverage Enhancement | Qualcomm Incorporated |
| R1-2210160 | Remaining issues on enhancements for PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2210161 | Change request on out of order PUSCH scheduling in case of counting on available slots | Nokia, Nokia Shanghai Bell |
| R1-2210162 | Remaining issues on joint channel estimation for PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2210163 | Change request on SRS resource sets mapping for supporting PUSCH repetition type A with joint channel estimation | Nokia, Nokia Shanghai Bell |
| R1-2210164 | Change request on spatial settings or power control parameters sets mapping for supporting PUCCH repetition with joint channel estimation | Nokia, Nokia Shanghai Bell |
| R1-2210181 | Discussion on Power Control with DMRS Bundling | Ericsson |
| R1-2210182 | Correction for Power Control with DMRS Bundling | Ericsson |
| R1-2210214 | Correction on events for determining time domain window for bundling DM-RS | Huawei, HiSilicon |
| R1-2210332 | [110bis-e-R17-CovEnh-01] Summary of email discussion to determine maintenance issues | Moderator (China Telecom) |
| R1-2210420 | FL summary of discussion on joint channel estimation for Rel-17 NR coverage enhancements | Moderator (China Telecom) |
| R1-2210426 | Moderator’s summary #1 for discussions on RAN4 reply LS about DMRS bundling | Moderator (MediaTek Inc.) |
| R1-2210456 | Moderator’s summary #2 for discussions on RAN4 reply LS about DMRS bundling | Moderator (MediaTek Inc.) |
| R1-2210544 | [Draft] Reply LS to RAN4 for further information on DMRS bundling | MediaTek Inc. |
| R1-2210545 | Reply LS to RAN4 for further information on DMRS bundling | RAN1, MediaTek Inc. |
| R1-2210684 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210072 | DRAFT CR Clarification on the no acquisition of the repetition number via DCI for 16-QAM transmissions in NB-IoT | Ericsson |
| R1-2210073 | On the no repetition number acquisition via DCI for 16-QAM in NB-IoT | Ericsson |
| R1-2210685 | Session notes for 8.9 (Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2210778 | Moderator Summary [110bis-e-R17-NB-IoT-eMTC-01 | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208471 | Remaining issues on resource multiplexing for IAB | Huawei, HiSilicon |
| R1-2208786 | Correction on the formula of Case-7 UL Tx timing for eIAB in TS 38.213 | ZTE, Sanechips |
| R1-2208787 | Correction on the position related to the description that the RB set is equivalent to hard for eIAB in TS 38.213 | ZTE, Sanechips |
| R1-2208788 | Corrections on misalignment for MAC CE or RRC parameters for eIAB in TS 38.213 | ZTE, Sanechips |
| R1-2209084 | Correction on RB set size for Rel-17 IAB FDM multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2209118 | Resource multiplexing in enhanced IAB systems | Lenovo |
| R1-2209834 | Correction on coexistance between Rel-16 and Rel-17 H/S/NA configuration | Huawei, HiSilicon |
| R1-2209835 | Correction on TDD configuration for IAB-MT | Huawei, HiSilicon |
| R1-2209949 | Draft CR on FD and TD DU resource configuration coexistence | Qualcomm Incorporated |
| R1-2210170 | Clarification on Rel-16 and Rel-17 H/S/NA Configuration | Nokia, Nokia Shanghai Bell |
| R1-2210225 | Draft CR on DL Tx power control | Ericsson |
| R1-2210226 | Discussion on DL Tx power control | Ericsson |
| R1-2210227 | Draft CR on guard symbols MAC CEs | Ericsson |
| R1-2210228 | Draft CR on timing case indication | Ericsson |
| R1-2210229 | Draft CR on Hard/Soft/Not Available resource definition | Ericsson |
| R1-2210230 | Maintenance on enhanced IAB | Ericsson |
| R1-2210706 | Correction on the formula of Case-7 UL Tx timing for eIAB in TS 38.213 | Moderator (Qualcomm), ZTE, Sanechips |
| R1-2210707 | CR on guard symbols MAC CEs | Moderator (Qualcomm), Ericsson |
| R1-2210756 | Correction on timing case indication | Moderator (Qualcomm), Ericsson, ZTE, Sanechips |
| R1-2210757 | Correction on on coexistence of Rel-17 and Rel-16 HSNA configuration | Moderator (Qualcomm) |
| R1-2210796 | Summary #1 of [110bis-e-R17-eIAB-01] | Moderator (Qualcomm Incorporated) |
| R1-2210797 | Summary #1 of [110bis-e-R17-eIAB-02] | Moderator (Qualcomm Incorporated) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208385 | Discussion on correction for inter-UE coordination Scheme 2 determination of UE-B | FUTUREWEI |
| R1-2208386 | Discussion on resolving ambiguous text in 38.214 | FUTUREWEI |
| R1-2208609 | Clarification on missing field descriptions of SCI 2-C | vivo |
| R1-2208610 | Corrections for partial sensing resource selection | vivo |
| R1-2208611 | Clarification for inter-UE coordination scheme-2 | vivo |
| R1-2208612 | Clarification on IUC related transmission based on latency bound | vivo |
| R1-2208613 | Corrections for missing functions of SCI 2-c | vivo |
| R1-2208614 | Discussion on PDCCH repetition for sidelink | vivo |
| R1-2208615 | Clarification on PDCCH repetition for sidelink-38.213 | vivo |
| R1-2208616 | Clarification on PDCCH repetition for sidelink-38.214 | vivo |
| R1-2208716 | Field naming alignment for SCI format 2-C in TS38.214 | ZTE, Sanechips |
| R1-2208717 | Clarification on Condition 2-A-1 for scheme 2 | ZTE, Sanechips |
| R1-2208718 | Clarification on Condition 2-A-2 for scheme 2 | ZTE, Sanechips |
| R1-2208719 | Corrections on misalignment for RRC parameters in TS 38.214 | ZTE, Sanechips |
| R1-2208720 | Corrections on misalignment for RRC parameters in TS 38.213 | ZTE, Sanechips |
| R1-2208721 | Corrections on misalignment for RRC parameters in TS 38.212 | ZTE, Sanechips |
| R1-2208816 | Draft CR on Q formula in step 6c for periodic-based partial sensing | OPPO |
| R1-2208817 | Draft CR on CPS sensing window | OPPO |
| R1-2208818 | Draft CR on the description of candidate slots for partial sensing | OPPO |
| R1-2208819 | Draft CR on starting slot and pre-condition in re-evaluation and pre-emption checking for partial sensing | OPPO |
| R1-2208919 | Correction on the operations of partial sensing | CATT, GOHIGH |
| R1-2208920 | Correction on resource exclusion behavior with non-preferred resource set | CATT, GOHIGH |
| R1-2208921 | Discussion on resource exclusion behavior with non-preferred resource set | CATT, GOHIGH |
| R1-2208922 | Discussion on remaining issues for R17 eSL power saving RA maintenance | CATT, GOHIGH |
| R1-2209135 | Draft CR on RRC parameter name and value misalignment in TS 38.213 | NEC |
| R1-2209136 | Draft CR on RRC parameter name and value misalignment in TS 38.214 | NEC |
| R1-2209309 | Corrections on the selection of Y or Y’ candidate slots for partial sensing | CMCC |
| R1-2209562 | Correction on Q formula for the second most recent periodic sensing occasion | Apple |
| R1-2209563 | Correction on CPS monitoring length during sidelink DRX inactive time | Apple |
| R1-2209564 | Correction on determining UE-B among UEs scheduling conflicting TBs | Apple |
| R1-2209565 | Correction on priority value of PSFCH transmission with conflict information for condition 2-A-2 | Apple |
| R1-2209676 | Clarification on pre-emption and re-evaluation for periodic transmission in partial sensing | Sharp |
| R1-2209677 | Clarification on monitoring slots for pre-emption check due to half-duplex constraint in partial sensing | Sharp |
| R1-2209678 | Correction on candidate slots selection for partial sensing | Sharp |
| R1-2209680 | Clarification on Preserve for periodic based partial sensing | Sharp |
| R1-2209681 | Clarification on candidate slots for aperiodic transmission in partial sensing | Sharp |
| R1-2209682 | Correction on handling of conflict information receiver flag | Sharp |
| R1-2209683 | Remaining issues on NR sidelink enhancement | Sharp |
| R1-2209798 | Draft CR on Inter-UE coordination in TS 38.212 | ASUSTeK |
| R1-2209799 | Draft CR on Inter-UE coordination in TS 38.213 | ASUSTeK |
| R1-2209801 | Draft CR on Inter-UE coordination in TS 38.214 | ASUSTeK |
| R1-2209827 | Correction on Q formula in step 6 of sensing and resource exclusion procedure in TS 38.214 | Huawei, HiSilicon |
| R1-2209828 | Correction on description of random resource selection in TS 38.214 | Huawei, HiSilicon |
| R1-2209830 | Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | Huawei, HiSilicon |
| R1-2209873 | Draft CR on condition to be UE-A for SL IUC scheme 2 | NTT DOCOMO, INC. |
| R1-2209874 | Draft CR on half-duplex consideration for SL re-evaluation/pre-emption check | NTT DOCOMO, INC. |
| R1-2209875 | Draft CR on insufficient candidate resources for SL re-evaluation/pre-emption check | NTT DOCOMO, INC. |
| R1-2209876 | Draft CR on slot n+T3 excluded from SL re-evaluation/pre-emption check | NTT DOCOMO, INC. |
| R1-2209877 | Draft CR on Y/Y’ candidate slots for SL partial sensing | NTT DOCOMO, INC. |
| R1-2209878 | Editorial corrections for SL IUC (38.212) | NTT DOCOMO, INC. |
| R1-2209879 | Editorial corrections for SL IUC (38.213) | NTT DOCOMO, INC. |
| R1-2209880 | Editorial corrections for SL IUC (38.214) | NTT DOCOMO, INC. |
| R1-2209881 | Discussion on RAN2-related topics for SL maintenance | NTT DOCOMO, INC. |
| R1-2209950 | Draft CR on Non-preferred Resources | Qualcomm Incorporated |
| R1-2209951 | Draft CR on Resource Pool Index in DCI 3_0 for Discovery | Qualcomm Incorporated |
| R1-2209952 | Discussion on Corrections to NR Sidelink | Qualcomm Incorporated |
| R1-2209953 | Draft CR on Power Control Parameters | Qualcomm Incorporated |
| R1-2210039 | Correction on SL timing | Nokia, Nokia Shanghai Bell |
| R1-2210060 | Draft CR on the Notes in section 8.1.4C of 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2210124 | [Draft] Clarification on valid PSFCH occassions for resource conflict information | Ericsson |
| R1-2210125 | [Draft] Consideration of associated processing times for contiguous partial sensing | Ericsson |
| R1-2210126 | [Draft] Correction to allowed resource selection mechanisms in a resource pool in mode 2 | Ericsson |
| R1-2210127 | [Draft] Correction to contiguous partial sensing window | Ericsson |
| R1-2210128 | [Draft] Correction to priority definition for Tx and Rx of PSFCH with conflict information | Ericsson |
| R1-2210129 | [Draft] Modification on Resource Pool index for DCI Format 3_0 | Ericsson |
| R1-2210130 | [Draft] Modifications on SL open loop power control formulae | Ericsson |
| R1-2210154 | Draft CR on corrections for the description of candidate slots in TS38.214 | Lenovo |
| R1-2210184 | Corrections for SL Inter-UE coordination | Nokia, Nokia Shanghai Bell |
| R1-2210185 | Corrections for SL Inter-UE coordination | Nokia, Nokia Shanghai Bell |
| R1-2210203 | Correction on UE-A is the destination UE of a TB transmitted by UE-B in TS 38.214 | Huawei, HiSilicon |
| R1-2210204 | Correction on RRC parameter names and values used for SCI format 1-A and 2-C in TS 38.212 | Huawei, HiSilicon |
| R1-2210285 | FL summary #1 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2210286 | FL summary #2 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2210287 | FL summary #3 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2210288 | FL summary for AI 8.11: R17 eSL power saving RA maintenance (EOM) | Moderator (OPPO) |
| R1-2210333 | Moderator summary for AI 8.11: Maintenance on NR sidelink enhancement | Moderator (LG Electronics) |
| R1-2210334 | Feature lead summary #1 for AI 8.11: Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2210335 | Feature lead summary #2 for AI 8.11: Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2210336 | Feature lead summary #3 for AI 8.11: Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2210481 | Moderator summary for reply LS to R1-2205728 | Moderator (Apple) |
| R1-2210482 | Draft reply LS to RAN2 on IUC with non-preferred resource set | Apple |
| R1-2210495 | Correction on the description for the minimum number of Y and Y’ candidate slots in sidelink partial sensing | Moderator (OPPO) |
| R1-2210496 | Correction on the selection of Y and Y’ candidate slots in sidelink partial sensing | Moderator (OPPO) |
| R1-2210497 | Corrections on CPS operation in sidelink partial sensing | Moderator (OPPO) |
| R1-2210555 | Correction on the description for the minimum number of Y and Y’ candidate slots in sidelink partial sensing | Moderator (OPPO), Samsung, Lenovo, Ericsson, CATT, GOHIGH, ZTE, Sanechips, Huawei, HiSilicon, NTT DOCOMO, vivo |
| R1-2210556 | Correction on the selection of Y and Y’ candidate slots in sidelink partial sensing | Moderator (OPPO), Samsung, Lenovo, Ericsson, CATT, GOHIGH, ZTE, Sanechips, Huawei, HiSilicon, NTT DOCOMO, vivo |
| R1-2210582 | Reply LS to RAN2 on IUC with non-preferred resource set | RAN1, Apple |
| R1-2210621 | Feature lead summary #4 for AI 8.11: Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2210622 | Feature lead summary #5 for AI 8.11: Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2210623 | Correction on sidelink timing | Moderator (LG Electronics) |
| R1-2210624 | Correction on conditions for UE to be UE-B for Condition 2-A-2 of Scheme 2 | Moderator (LG Electronics) |
| R1-2210625 | Correction on the determination of the priority value of PSFCH transmission with conflict information due to Condition 2-A-2 of Scheme 2 | Moderator (LG Electronics) |
| R1-2210686 | Session notes for 8.11 (Maintenance on NR Sidelink enhancement) | Ad-Hoc Chair (Huawei) |
| R1-2210710 | Corrections on CPS operation in sidelink partial sensing | Moderator (OPPO), vivo, Samsung, Lenovo, Intel, Huawei, HiSilicon, ZTE, Sanechips, CATT, GOHIGH, CMCC |
| R1-2210731 | Correction on sidelink timing | Moderator (LG Electronics), Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R1-2210732 | Correction on conditions for UE to be UE-B for Condition 2-A-2 of Scheme 2 | Moderator (LG Electronics), NTT DOCOMO, Ericsson, Samsung, ZTE, Sanechips |
| R1-2210733 | Correction on the determination of the priority value of PSFCH transmission with conflict information due to Condition 2-A-2 of Scheme 2 | Moderator (LG Electronics) |
| R1-2210734 | Draft LS on PDCCH repetition for sidelink | Moderator (LG Electronics) |
| R1-2210735 | LS on PDCCH repetition for sidelink | RAN1, LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2208466 | Correction on processing timeline for NACK-only mode2 to TS38.214 | Huawei, HiSilicon, CBN |
| R1-2208467 | Correction on codebook type for NACK-only HARQ-ACK feedback to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2208468 | Correction on PRI for NACK-only HARQ-ACK feedback to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2208469 | Correction on UE behaviors of PDCCH monitoring for configured RM patterns to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2208470 | Correction on SS0 availability for scheduling MBS to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2208617 | Draft CR on HARQ-ACK feedback for PDSCH scheduled by DCI format 4-1 | vivo |
| R1-2208618 | Draft CR on PUCCH determination for UE configured with NACK-only feedback mode | vivo |
| R1-2208619 | Draft CR on type 2 codebook determination with DG PDSCHs and SPS PDSCHs | vivo |
| R1-2208620 | Discussion on SPS PDSCH overlapping handling in FDM case | vivo |
| R1-2208701 | Remaining Issues for RRC_CONNECTED UEs supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2208887 | Draft CR on HARQ-ACK multiplexing of unicast SPS PDSCHs and multicast DG PDSCHs | vivo |
| R1-2208923 | Discussion on MBS supporting HARQ-ACK codebook retransmission | CATT |
| R1-2208924 | Discussion on MBS supporting deferring HARQ-ACK for SPS PDSCH | CATT |
| R1-2208925 | Draft CR on MBS supporting HARQ-ACK codebook retransmission | CATT |
| R1-2208926 | Draft CR on MBS supporting deferring HARQ-ACK for SPS PDSCH | CATT |
| R1-2208927 | Draft CRs for NR Multicast and Broadcast Service | CATT |
| R1-2208928 | Corrections on multicast DCI format to enable/disable HARQ-ACK | CATT |
| R1-2208929 | Discussion on multicast DCI format to enable/disable HARQ-ACK | CATT |
| R1-2208995 | Correction on Type-2 HARQ-ACK codebook for MBS | Langbo |
| R1-2208996 | Correction on Type-3 HARQ-ACK codebook for MBS | Langbo |
| R1-2209137 | Remaining Issues on NR MBS | NEC |
| R1-2209310 | Remaining issues on HARQ-ACK feedback for multicast | CMCC |
| R1-2209311 | Discussion on specs alignment of PDSCH simultaneous reception for MBS | CMCC |
| R1-2209312 | Draft CR on multicast HARQ-ACK codebook type configuration in DCI formats | CMCC |
| R1-2209313 | Draft CR on multicast rate-matching pattern configuration | CMCC |
| R1-2209314 | Draft CR on SPS and dynamic scheduling PDSCH(s) collision for MBS | CMCC |
| R1-2209315 | Draft CR on RRC parameters correction in TS 38.211 | CMCC |
| R1-2209316 | Draft CR on RRC parameters correction in TS 38.212 | CMCC |
| R1-2209317 | Draft CR on RRC parameters correction in TS 38.213 | CMCC |
| R1-2209318 | Draft CR on RRC parameters correction in TS 38.214 | CMCC |
| R1-2209449 | Maintenance on NR Multicast and Broadcast Services | LG Electronics |
| R1-2209470 | Maintenance of broadcast and multicast for MBS | ZTE |
| R1-2209471 | Draft CR on CFR configuration for multicast | ZTE |
| R1-2209472 | Draft CR on terms of G-RNTI used for MTCH | ZTE |
| R1-2209473 | Draft CR on restrictions of simultaneous reception | ZTE |
| R1-2209474 | Draft CR on SPS collision handling | ZTE |
| R1-2209475 | Draft CR on 1 bit NACK-only feedback | ZTE |
| R1-2209476 | Draft CR on determining NACK-only PUCCH in NACK-only mode1 | ZTE |
| R1-2209524 | Corrections on the MBS reception type combinations in TS 38.202 | MediaTek Inc. |
| R1-2209525 | Corrections on the MBS in TS 38.213 | MediaTek Inc. |
| R1-2209526 | Corrections on the MBS in TS 38.214 | MediaTek Inc. |
| R1-2209527 | Remaining issues on NR MBS | MediaTek Inc. |
| R1-2209566 | Remaining issues on NR Multicast and Broadcast Services | Apple |
| R1-2209708 | Maintenance on multicast-broadcast services | Samsung |
| R1-2209822 | Remaining issues for Rel-17 MBS | Huawei, HiSilicon, CBN |
| R1-2209832 | Correction on processing timeline for NACK-only mode2 to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2209833 | Correction on the max data rate for multiplexing MBS and unicast to TS38.214 | Huawei, HiSilicon, CBN |
| R1-2209882 | Draft CR on DAI field in DCI format 4_2 | NTT DOCOMO, INC. |
| R1-2209883 | Draft CR on HARQ-ACK feedback for SPS GC-PDSCH | NTT DOCOMO, INC. |
| R1-2209884 | Draft CR on NACK-only based feedback for multicast | NTT DOCOMO, INC. |
| R1-2209885 | Draft CR on multiplexing NACK-only based feedback with SR | NTT DOCOMO, INC. |
| R1-2209954 | Draft CR on DCI-indicated enabling/disabling multicast feedback for Type-1 CB | Qualcomm Incorporated |
| R1-2209955 | Draft CR on Type-2 CB for NACK-only multicast feedback | Qualcomm Incorporated |
| R1-2209956 | Draft CR on max data rate per CC in case of FDMed unicast and MBS PDSCHs | Qualcomm Incorporated |
| R1-2209957 | Scaling factor for FDMed unicast and MBS PDSCHs | Qualcomm Incorporated |
| R1-2209958 | Draft CR on upper bound of TBS LBRM in case of FDMed unicast and MBS PDSCHs | Qualcomm Incorporated |
| R1-2209959 | Draft CR on PDSCH processing time required to select PUCCH for NACK-only mode2 based multicast feedback | Qualcomm Incorporated |
| R1-2209960 | Draft CR on multicast PDSCH with a HARQ process with disabled HARQ-ACK feedback | Qualcomm Incorporated |
| R1-2209961 | Draft CR on PDCCH monitoring when overlapping with rate matching patterns | Qualcomm Incorporated |
| R1-2210075 | Correction on MBS SPS | ASUSTeK |
| R1-2210095 | Correction on configurations of G-RNTI and G-CS-RNTI | ASUSTeK |
| R1-2210096 | Correction on configuration of PDSCH aggregation factor for MBS | ASUSTeK |
| R1-2210155 | Correction on HARQ-ACK codebook types in UL DCI formats for scheduling MBS | Lenovo |
| R1-2210156 | Draft CR on HARQ-ACK feedback for PDSCH scheduled by DCI format 4_1 | Lenovo |
| R1-2210157 | Draft CR on DAI update for multicast DCI formats | Lenovo |
| R1-2210158 | Draft CR on simultaneous configuration of Type-1 HARQ-ACK codebook and dci-enabler for multicast service | Lenovo |
| R1-2210159 | Remaining issues on HARQ-ACK feedback for NR MBS | Lenovo |
| R1-2210173 | Maintenance on NR Multicast and Broadcast Services | Ericsson |
| R1-2210207 | Correction on retransmission schemes for MBS HARQ-ACK feedback to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2210208 | Correction on the channel combinations for MBS UE handling to TS38.213 | Huawei, HiSilicon, CBN |
| R1-2210209 | Correction on the channel combinations for MBS UE handling to TS38.214 | Huawei, HiSilicon, CBN |
| R1-2210210 | Correction on the channel combinations for MBS UE handling to TS38.202 | Huawei, HiSilicon, CBN |
| R1-2210371 | FLS on the issues for NR MBS maintenance | Moderator (Huawei) |
| R1-2210372 | FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
| R1-2210373 | FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
| R1-2210374 | FLS#3 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
| R1-2210399 | Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS | Moderator (CMCC) |
| R1-2210400 | Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS | Moderator (CMCC) |
| R1-2210446 | Draft CR on the MBS reception type combinations to TS 38.202 | Moderator (CMCC), MediaTek, Huawei, HiSilicon, CBN |
| R1-2210447 | Draft CR on the MBS reception type combinations to TS 38.213 | Moderator(CMCC), Huawei, HiSilicon, CBN, ZTE |
| R1-2210448 | Draft CR on the MBS reception type combinations to TS 38.214 | Moderator(CMCC), Huawei, HiSilicon, CBN |
| R1-2210449 | Draft CR on the max data rate for FDMed MBS and unicast to TS38.214 | Moderator (CMCC), Huawei, HiSilicon, CBN, Qualcomm Incorporated |
| R1-2210450 | Draft CR on FDRA determination of multicast DCI formats to TS 38.212 | Moderator (CMCC), Nokia, Nokia Shanghai Bell |
| R1-2210451 | Draft CR on CFR configuration for multicast to TS 38.213 | Moderator (CMCC), ZTE, CATT |
| R1-2210452 | Draft CR on SS0 availability for scheduling MBS to TS 38.213 | Moderator (CMCC), Huawei, HiSilicon, CBN |
| R1-2210503 | Draft CR on number of HARQ-ACK codebooks configurable for multicast | Moderator (Huawei), CMCC |
| R1-2210504 | Draft CR on deleting redundant descriptions for HARQ-ACK CB types in UL DCI formats | Moderator (Huawei), Lenovo |
| R1-2210505 | Draft CR on RRC parameters alignment for HARQ-ACK CB for multicast | Moderator (Huawei), CMCC |
| R1-2210506 | Draft CR on multiplexing NACK-only mode1 with others | Moderator (Huawei), ZTE |
| R1-2210509 | Draft CR on SS0 availability for scheduling MBS to TS 38.213 | Moderator (CMCC), Huawei, HiSilicon, CBN |
| R1-2210510 | Draft CR on definition of G-CS-RNTI for SPS group-common PDSCH retransmission to TS 38.213 | Moderator (CMCC), CATT |
| R1-2210511 | Draft CR on PDCCH monitoring when overlapping with the rate matching pattern to TS 38.213 | Moderator (CMCC), Qualcomm Incorporated, Huawei, HiSilicon, CBN, MediaTek |
| R1-2210570 | Draft CR on RRC parameters alignment for HARQ-ACK CB for multicast | Moderator (Huawei), CMCC |
| R1-2210571 | Draft CR on codebook type for NACK-only HARQ-ACK feedback | Moderator (Huawei) |
| R1-2210572 | Draft CR on HARQ-ACK feedback for PDSCH scheduled by DCI format 4_1 | Moderator (Huawei), vivo, CATT, Lenovo |
| R1-2210573 | Draft CR on PUCCH resource determination of multicast HARQ-ACK | Moderator (Huawei), Samsung |
| R1-2210574 | Draft CR on PUCCH resource determination of SPS multicast HARQ-ACK | Moderator (Huawei) |
| R1-2210575 | Draft CR on dci-enabler for Type1 HARQ-ACK CB for multicast | Moderator (Huawei), Qualcomm, Lenovo |
| R1-2210576 | Draft CR on DAI counting for ‘dci-enabler’ in DCI indicating value 0 | Moderator (Huawei), Langbo, Lenovo |
| R1-2210577 | Draft CR on PUCCH resource determination for multiplexing dynamic multicast HARQ-ACK and SPS unicast HARQ-ACK | Moderator (Huawei), vivo |
| R1-2210578 | DRAFT LS on the RRC parameter for multicast HARQ-ACK feedback | Huawei |
| R1-2210638 | Draft CR on handling SR and NACK-only collision | Moderator (Huawei) |
| R1-2210645 | Draft CR on SS0 availability for scheduling MBS to TS 38.213 | Moderator (CMCC), Huawei, HiSilicon, CBN |
| R1-2210646 | Moderator’s summary#3 on scheduling related issues for Rel-17 NR MBS | Moderator (CMCC) |
| R1-2210647 | CR on PDCCH monitoring when overlapping with the rate matching pattern to TS 38.213 | Moderator (CMCC), Qualcomm Incorporated, Huawei, HiSilicon, CBN, MediaTek |
| R1-2210648 | CR on the MBS reception type combinations to TS 38.202 | Moderator (CMCC), MediaTek, Huawei, HiSilicon, CBN, ZTE |
| R1-2210649 | CR on the max data rate for FDMed MBS and unicast to TS38.214 | Moderator (CMCC), Huawei, HiSilicon, CBN, Qualcomm Incorporated |
| R1-2210667 | Draft CR on definition of G-CS-RNTI for SPS group-common PDSCH retransmission to TS 38.213 | Moderator (CMCC), CATT |
| R1-2210687 | Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| R1-2210698 | CR on number of HARQ-ACK codebooks configurable for multicast | Moderator (Huawei), CMCC |
| R1-2210699 | CR on multiplexing NACK-only mode1 with others | Moderator (Huawei), ZTE |
| R1-2210700 | CR on codebook type for NACK-only HARQ-ACK feedback | Moderator (Huawei) |
| R1-2210701 | CR on HARQ-ACK feedback for PDSCH scheduled by DCI format 4_1 | Moderator (Huawei), vivo, CATT, Lenovo |
| R1-2210702 | CR on DAI counting for ‘dci-enabler’ in DCI indicating value 0 | Moderator (Huawei), Langbo, Lenovo |
| R1-2210703 | LS on the RRC parameter for multicast HARQ-ACK feedback | RAN1, Huawei |
| R1-2210728 | CR on PUCCH resource determination of SPS multicast HARQ-ACK | Moderator (Huawei) |
| R1-2210729 | CR on PUCCH resource determination for multiplexing dynamic multicast HARQ-ACK and SPS unicast HARQ-ACK | Moderator (Huawei), vivo |
| R1-2210730 | CR on handling SR and NACK-only collision | Moderator (Huawei) |
| R1-2210750 | Draft CR on multiplexing HARQ-ACK for DG and SPS multicast and unicast | Moderator (Huawei), vivo |
| R1-2210751 | Draft CR on PRI for NACK-only HARQ-ACK feedback to TS38.213 | Moderator (Huawei) |
| R1-2210768 | CR on the MBS reception type combinations to TS 38.214 | Moderator (CMCC), Huawei, HiSilicon, CBN |
| R1-2210769 | CR on SS0 availability for scheduling MBS to TS 38.213 | Moderator (CMCC), Huawei, HiSilicon, CBN, ZTE |
| R1-2210775 | CR on dci-enabler for Type1 HARQ-ACK CB for multicast | Moderator (Huawei), Qualcomm, Lenovo, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2208621 | Corrections on Scell scheduling Pcell | vivo |
| R1-2209036 | Correction on different SCSs between P(S)Cell and sSCell | Intel Corporation |
| R1-2209037 | Discussion on different SCSs between P(S)Cell and sSCell | Intel Corporation |
| R1-2209450 | Discussion on simultaneous PDCCH monitoring between USS set on sSCell and CSS set on PCell | LG Electronics |
| R1-2209469 | Draft CR for Rel-17 DSS | ZTE |
| R1-2209851 | Correction for DCI size alignment for Rel-17 DSS | Huawei, HiSilicon |
| R1-2209962 | Discussion on clarification for cross-carrier scheduling from SCell to P(S)Cell | Qualcomm Incorporated |
| R1-2210191 | Disabling EN-DC power split when SCG is deactivated | Nokia, Nokia Shanghai Bell |
| R1-2210440 | Summary#1 of Email discussion [110bis-e-R17-DSS-01] | Moderator (Ericsson) |
| R1-2210441 | Summary#2 of Email discussion [110bis-e-R17-DSS-01] | Moderator (Ericsson) |
| R1-2210688 | Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2210718 | CR on DCI size alignment for Cross-carrier scheduling from SCell to Pcell | Moderator (Ericsson), Huawei, HiSilicon, Samsung |
| R1-2210770 | CR on DCI size alignment for Cross-carrier scheduling from SCell to Pcell | Moderator (Ericsson), Huawei, HiSilicon, Samsung |
| R1-2210780 | Summary#3 of Email discussion [110bis-e-R17-DSS-01] | Moderator (Ericsson) |
| R1-2210781 | Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208689 | Corrections on timing relationship for IoT-NTN | ZTE |
| R1-2208831 | Draft CR on UE pre-compensation in segment | OPPO |
| R1-2209242 | Draft CR on correction of IoT NTN with dropping in pre-compensation per segment in 36.213 | Nokia, Nokia Shanghai Bell |
| R1-2209243 | Draft CR on correction of IoT NTN with segment configuration in 36.213 | Nokia, Nokia Shanghai Bell |
| R1-2209244 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Nokia, Nokia Shanghai Bell |
| R1-2209650 | On SIB accumulation and Timing relationship enhancements in IoT NTN | Ericsson Limited |
| R1-2210020 | Maintenance for IoT NTN | Lenovo |
| R1-2210070 | DRAFT CR Missing Koffset in FDD HARQ-ACK reporting procedure | Ericsson |
| R1-2210183 | Draft CR on correction of IoT NTN with segment gap in 36.211 | Nokia, Nokia Shanghai Bell |
| R1-2210201 | Corrections on NPDCCH monitoring restriction for IoT NTN | Huawei, HiSilicon |
| R1-2210219 | Corrections on timing relationship parameter for IoT NTN | Huawei, HiSilicon |
| R1-2210258 | FL summary#1 on Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek Inc.) |
| R1-2210259 | FL summary#2 on Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek Inc.) |
| R1-2210299 | FL summary 1 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2210300 | FL summary 2 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2210309 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Qualcomm |
| R1-2210434 | Summary of [110bis-e-R17-IoT-NTN-01] Email discussion to determine maintenance issues to be handled in RAN1#110bis-e | Moderator (MediaTek Inc.) |
| R1-2210561 | [draft] CR on UE pre-compensation in segment | Moderator (MediaTek) |
| R1-2210562 | CR on UE pre-compensation in segment | Moderator (MediaTek) |
| R1-2210689 | Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210488 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #110bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2210489 | LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#110bis-e | RAN1, AT&T, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2208461 | Remaining issues for UE features set 1 topics | Huawei, HiSilicon |
| R1-2208530 | Discussion on UE features for topics 1 | ZTE |
| R1-2208538 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2208622 | Remaining issues on UE features for MBS, Coeverage enhancement and URLLC | vivo |
| R1-2208767 | Remaining issues on UE features for Rel-17 NR coverage enhancements | China Telecom |
| R1-2208868 | Discussion on UE features (Topic-1) | OPPO |
| R1-2209038 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2209319 | Maintenance on Rel.17 UE features for NR coverage enhancement | CMCC |
| R1-2209528 | Views on UE feature Topic 1 | MediaTek Inc. |
| R1-2209670 | Rel-17 UE features topics set #1 | Ericsson |
| R1-2209709 | UE features for Coverage Enhacement | Samsung |
| R1-2209886 | Discussion on remaining issues regarding Rel-17 RAN1 UE features topics 1 | NTT DOCOMO, INC. |
| R1-2209963 | Discussion on Rel-17 UE features topic 1 | Qualcomm Incorporated |
| R1-2210098 | Remaining issues for UE features topics 1 | Nokia, Nokia Shanghai Bell |
| R1-2210275 | Summary#1 on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2210276 | Summary#1 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2210277 | Summary#1 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2210278 | Summary#1 on UE features for SL enh and RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2210281 | Session Notes for R17 UE Features 1 | Moderator (NTT DOCOMO, INC.) |
| R1-2210421 | Summary#2 on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2210422 | Summary#2 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2210423 | Summary#2 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2210492 | Reply LS to RAN2 on Per-FS L1 feature for NR sidelink discovery BC-list | RAN1, OPPO |
| R1-2210664 | Summary#3 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2210665 | Summary#3 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2210721 | Summary#4 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2210722 | Summary#4 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208462 | Remaining issues for UE features set 2 topics | Huawei, HiSilicon |
| R1-2209241 | Discussion on some remaining issues of Rel-17 UE features | ZTE, Sanechips |
| R1-2209567 | View on Rel-17 UE features | Apple |
| R1-2209792 | Summary of UE features topics 2 | Moderator (AT&T) |
| R1-2209887 | Discussion on remaining issues regarding Rel-17 RAN1 UE features topics 2 | NTT DOCOMO, INC. |
| R1-2209964 | Discussion on Rel-17 UE features topic 2 | Qualcomm Incorporated |
| R1-2210087 | UE features topics 2 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2209965 | Other Rel-17 UE features | Qualcomm Incorporated |
| R1-2210100 | Remaining issues for Rel-17 UE features | Nokia, Nokia Shanghai Bell |
| R1-2210279 | Summary#1 on UE features for TEI17 | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208623 | Remaining issues for NR small data transmissions in RRC INACTIVE state | vivo |
| R1-2208624 | Corrections of redundancy version of repeated CG PUSCH for SDT | vivo |
| R1-2208625 | Corrections on resource pool index for sl-TxPoolScheduling | vivo |
| R1-2208711 | Correction on repetitions for CG-SDT | ZTE, Sanechips |
| R1-2208712 | Correction on SSB subset for CG-SDT | ZTE, Sanechips |
| R1-2208713 | Correction on deltapreamble of feature combination | ZTE, Sanechips |
| R1-2208930 | Correction on resource pool index in DCI Format 3_0 | CATT, GOHIGH |
| R1-2209192 | Discussion on NR ra-SearchSpace issues | ZTE, Sanechips |
| R1-2209193 | Correction on ra-SearchSpace for DCI format 0_0 | ZTE, Sanechips |
| R1-2209255 | Discussion on physical layer aspects of small data transmission | xiaomi |
| R1-2209710 | Discussion on the repetition aspect for SDT in active state | Samsung |
| R1-2209711 | Draft CR for the repetition aspect for SDT in active state | Samsung |
| R1-2209831 | Remaining issues on paging monitoring and measurement during SDT procedure | Huawei, HiSilicon |
| R1-2209966 | Remaining Issues of Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2210442 | FL summary of email discussion on remaining issues of Rel-17 UL Tx switching | Moderator (China Telecom) |
| R1-2210485 | Summary of preparation phase email discussion for Rel-17 SDT | Moderator (ZTE) |
| R1-2210486 | Summary on remaining issues of SDT | Moderator (ZTE) |
| R1-2210596 | Correction on deltapreamble of feature combination | Moderator (ZTE), Samsung |
| R1-2210761 | Summary of discussion on NR ra-SearchSpace issues | Moderator (ZTE) |
| R1-2210762 | Correction on ra-SearchSpace for DCI format 0_0 | Moderator (ZTE), Sanechips, Samsung |
| R1-2210763 | Correction on ra-SearchSpace for DCI format 0_0 | Moderator (ZTE), Sanechips, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2208373 | Unified TCI framework extension for multi-TRP | FUTUREWEI |
| R1-2208439 | Discussion on unified TCI framework extension for multi-TRP | Huawei, HiSilicon |
| R1-2208493 | On Unified TCI Extension for MTRP | InterDigital, Inc. |
| R1-2208502 | Enhancements on unified TCI framework extension for multi-TRP | ZTE |
| R1-2208539 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
| R1-2208626 | Discussion on unified TCI framework extension for multi-TRP | vivo |
| R1-2208676 | Unified TCI framework extension for multi-TRP | Ericsson |
| R1-2208702 | Discussion on unified TCI framework extension for multi-TRP operation | TCL Communication Ltd. |
| R1-2208740 | Discussion of unified TCI framework for multi-TRP | Lenovo |
| R1-2208792 | Unified TCI framework extension for multi-TRP | OPPO |
| R1-2208891 | Unified TCI framework extension for multi-TRP/panel | LG Electronics |
| R1-2208945 | On unified TCI framework extension for multi-TRP operation | CATT |
| R1-2209008 | Discussion on unified TCI extension for MTRP | Fujitsu |
| R1-2209039 | Unified TCI Framework for Multi-TRP | Intel Corporation |
| R1-2209138 | Discussion on unified TCI framework extension for multi-TRP | NEC |
| R1-2209165 | Discussion on unified TCI framework extension for multi-TRP | Transsion Holdings |
| R1-2209256 | Unified TCI framework extension for multi-TRP | xiaomi |
| R1-2209320 | Discussion on unified TCI framework extension for multi-TRP | CMCC |
| R1-2209379 | Unified TCI framework extension for multi-TRP | Sharp |
| R1-2209414 | Discussion on unified TCI framework extension for multi-TRP | FGI |
| R1-2209492 | Unified TCI framework extension for multi-TRP | MediaTek Inc. |
| R1-2209540 | Discussion on unified TCI framework extension for multi-TRP | |
| R1-2209547 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209568 | Views on unified TCI framework extension for multi-TRP | Apple |
| R1-2209712 | Views on unified TCI extension focusing on m-TRP | Samsung |
| R1-2209888 | Discussion on unified TCI framework extension for multi-TRP | NTT DOCOMO, INC. |
| R1-2209967 | Extension of unified TCI framework for mTRP | Qualcomm Incorporated |
| R1-2210018 | Unified TCI framework extension for multi-TRP | PANASONIC |
| R1-2210029 | Discussion on unified TCI framework extension for multi-TRP | ITRI |
| R1-2210061 | Unified TCI framework extension for multi-TRP | Nokia, Nokia Shanghai Bell |
| R1-2210104 | Discussion on Unified TCI framework extension for multi-TRP | CEWiT |
| R1-2210243 | Moderator summary on extension of unified TCI framework (Round 0) | Moderator (MediaTek Inc.) |
| R1-2210380 | Moderator summary on extension of unified TCI framework (Round 1) | Moderator (MediaTek Inc.) |
| R1-2210597 | Moderator summary on extension of unified TCI framework (Round 2) | Moderator (MediaTek Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208374 | Enhancements to support two TAs for multi-DCI | FUTUREWEI |
| R1-2208440 | Study on TA enhancement for UL M-TRP transmission | Huawei, HiSilicon |
| R1-2208460 | Discussion on two TAs for multi-DCI based on multi-TRP operation | TCL Communication Ltd. |
| R1-2208494 | Multiple TA for MTRP Operation | InterDigital, Inc. |
| R1-2208503 | TA enhancement for multi-DCI | ZTE |
| R1-2208540 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
| R1-2208627 | Discussion on two TAs for multi-DCI-based multi-TRP operation | vivo |
| R1-2208677 | Two TAs for multi-DCI | Ericsson |
| R1-2208741 | Discussion of two TAs for multi-DCI UL transmission | Lenovo |
| R1-2208793 | Two TAs for multi-DCI | OPPO |
| R1-2208892 | Two TAs for multi-TRP/panel | LG Electronics |
| R1-2208946 | On Two TAs for UL multi-DCI multi-TRP operation | CATT |
| R1-2209040 | On two TAs for multi-DCI | Intel Corporation |
| R1-2209139 | Discussion on two TAs for multi-DCI | NEC |
| R1-2209166 | Discussion on two TAs for multi-DCI based multi-TRP operation | Transsion Holdings |
| R1-2209257 | Discussion on two TAs for multi-TRP operation | xiaomi |
| R1-2209321 | Discussion on two TAs for multi-DCI | CMCC |
| R1-2209380 | Two TAs for multi-DCI | Sharp |
| R1-2209493 | UL Tx Timing Management for MTRP Operation | MediaTek Inc. |
| R1-2209541 | Discussion on two TAs for multi-DCI | |
| R1-2209569 | Two TAs for multi-DCI Uplink Transmissions | Apple |
| R1-2209713 | Views on two TAs for m-DCI | Samsung |
| R1-2209889 | Discussion on two TAs for multi-DCI | NTT DOCOMO, INC. |
| R1-2209968 | Supporting two TAs for multi-DCI based mTRP | Qualcomm Incorporated |
| R1-2210062 | Two TAs for UL multi-DCI multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2210304 | Moderator Summary #1 on Two TAs for multi-DCI | Moderator (Ericsson) |
| R1-2210468 | Moderator Summary #2 on Two TAs for multi-DCI | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208441 | CSI enhancement for coherent JT and mobility | Huawei, HiSilicon |
| R1-2208495 | Enhanced CSI for CJT and High Doppler Operations | InterDigital, Inc. |
| R1-2208504 | CSI enhancement for high/medium UE velocities and CJT | ZTE |
| R1-2208541 | Discussion on CSI enhancement for high/medium UE velocities and coherent JT | Spreadtrum Communications |
| R1-2208628 | Discussion on CSI enhancement for high-medium UE velocities and coherent JT | vivo |
| R1-2208742 | Discussion of CSI enhancement for high speed UE and coherent JT | Lenovo |
| R1-2208794 | CSI enhancement for high/medium UE velocities and coherent JT | OPPO |
| R1-2208872 | On CSI Enhancement | |
| R1-2208893 | Potential CSI enhancement for high/medium UE velocities and coherent JT | LG Electronics |
| R1-2208947 | Discussion on CSI enhancements | CATT |
| R1-2209041 | On CSI enhancements | Intel Corporation |
| R1-2209090 | Further considerations on CSI enhancement for high/medium UE velocities and CJT | Sony |
| R1-2209140 | Discussion on CSI enhancement | NEC |
| R1-2209247 | Discussion on CSI enhancement | Mavenir |
| R1-2209258 | Discussion on CSI enhancement for high/medium UE velocities and CJT | xiaomi |
| R1-2209322 | Discussion on CSI enhancement for high/medium UE velocities and CJT | CMCC |
| R1-2209381 | CSI enhancement | Sharp |
| R1-2209494 | CSI enhancement | MediaTek Inc. |
| R1-2209545 | CSI enhancements for medium UE velocities and coherent JT | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209570 | Views on Rel-18 MIMO CSI enhancement | Apple |
| R1-2209714 | Moderator summary on Rel-18 CSI enhancements | Moderator (Samsung) |
| R1-2209715 | Summary of OFFLINE discussion on Rel-18 MIMO CSI | Moderator (Samsung) |
| R1-2209716 | Views on CSI enhancements | Samsung |
| R1-2209793 | Views on CSI Enhancements for CJT | AT&T |
| R1-2209852 | On CSI enhancements for Rel-18 NR MIMO evolution | Ericsson |
| R1-2209890 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
| R1-2209969 | CSI enhancements for high/medium UE velocities and Coherent-JT | Qualcomm Incorporated |
| R1-2210063 | CSI enhancement for high/medium UE velocities and CJT | Nokia, Nokia Shanghai Bell |
| R1-2210105 | Discussion on CSI Enhancements for high/medium UE velocities and coherent JT | CEWiT |
| R1-2210241 | Views on CSI enhancements | Samsung |
| R1-2210370 | Moderator summary#2 on Rel-18 CSI enhancements: Round 1 | Moderator (Samsung) |
| R1-2210507 | Moderator summary#3 on Rel-18 CSI enhancements: Round 2 | Moderator (Samsung) |
| R1-2210523 | Summary of TDCP Alternatives for Comparison | Moderator (Samsung) |
| R1-2210566 | Moderator summary#4 on Rel-18 CSI enhancements: Round 3 | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208375 | On increasing the number of orthogonal DM-RS ports for MU-MIMO | FUTUREWEI |
| R1-2208442 | Enhancements on DMRS in Rel-18 | Huawei, HiSilicon |
| R1-2208496 | Discussion on DMRS Enhancements | InterDigital, Inc. |
| R1-2208505 | DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO | ZTE |
| R1-2208529 | Discussions on increased number of orthogonal DMRS ports | New H3C Technologies Co., Ltd. |
| R1-2208542 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
| R1-2208629 | Discussion on DMRS enhancements | vivo |
| R1-2208743 | Discussion of increased number of orthogonal DMRS ports | Lenovo |
| R1-2208795 | DMRS enhancement for Rel-18 MIMO | OPPO |
| R1-2208873 | On DMRS Enhancement | |
| R1-2208894 | Increased number of orthogonal DMRS ports | LG Electronics |
| R1-2208948 | Discussion on DMRS enhancements | CATT |
| R1-2209042 | DMRS Enhancements for Rel-18 NR | Intel Corporation |
| R1-2209141 | Discussion on increased number of orthogonal DMRS ports | NEC |
| R1-2209259 | Discussion on DMRS enhancement | xiaomi |
| R1-2209323 | Discussion on increased number of orthogonal DMRS ports | CMCC |
| R1-2209382 | Increased number of orthogonal DMRS ports | Sharp |
| R1-2209495 | Increased number of orthogonal DMRS ports | MediaTek Inc. |
| R1-2209544 | Increased number of orthogonal DMRS ports | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209571 | Views on supporting increased number of orthogonal DMRS ports | Apple |
| R1-2209717 | Views on DMRS enhancements | Samsung |
| R1-2209891 | Discussion on DMRS enhancements | NTT DOCOMO, INC. |
| R1-2209970 | Design for increased number of orthogonal DMRS ports | Qualcomm Incorporated |
| R1-2210064 | Rel-18 UL and DL DMRS Enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210078 | On DMRS enhancement in Rel-18 | Ericsson |
| R1-2210263 | FL summary on DMRS#1 | Moderator (NTT DOCOMO) |
| R1-2210264 | FL summary on DMRS#2 | Moderator (NTT DOCOMO) |
| R1-2210407 | FL summary on DMRS#3 | Moderator (NTT DOCOMO) |
| R1-2210408 | FL summary on DMRS#4 | Moderator (NTT DOCOMO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208376 | SRS enhancements for TDD CJT and 8TX operation | FUTUREWEI |
| R1-2208443 | SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 | Huawei, HiSilicon |
| R1-2208497 | Discussion on SRS Enhancements | InterDigital, Inc. |
| R1-2208506 | SRS enhancement targeting TDD CJT and 8 TX operation | ZTE |
| R1-2208543 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
| R1-2208630 | Discussion on SRS enhancement | vivo |
| R1-2208744 | Discussion of SRS enhancement | Lenovo |
| R1-2208796 | SRS enhancement targeting TDD CJT and 8 TX operation | OPPO |
| R1-2208874 | On SRS Enhancement | |
| R1-2208895 | SRS enhancement targeting TDD CJT and 8 TX operation | LG Electronics |
| R1-2208949 | Discussion on SRS enhancement | CATT |
| R1-2209043 | Discussion on SRS enhancement in Rel-18 | Intel Corporation |
| R1-2209091 | Considerations on SRS enhancement targeting TDD CJT and 8 TX operation | Sony |
| R1-2209142 | Discussion on SRS enhancement | NEC |
| R1-2209260 | Discussion on SRS enhancements | xiaomi |
| R1-2209324 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | CMCC |
| R1-2209383 | SRS enhancement targeting TDD CJT and 8 TX operation | Sharp |
| R1-2209434 | Views on enhanced SRS configuration for 8TX and TDD CJT | KDDI Corporation |
| R1-2209572 | Views on Rel-18 MIMO SRS enhancement | Apple |
| R1-2209623 | On SRS enhancements targeting TDD CJT and 8 TX operation | Ericsson |
| R1-2209718 | Views on SRS enhancements | Samsung |
| R1-2209892 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2209971 | SRS enhancement for TDD CJT and 8 Tx operation | Qualcomm Incorporated |
| R1-2210065 | SRS enhancement for TDD CJT and 8Tx operation | Nokia, Nokia Shanghai Bell |
| R1-2210106 | Discussion on SRS Enhancements for 8Tx Operation | CEWiT |
| R1-2210382 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2210383 | FL Summary #2 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2210384 | FL Summary #3 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2210711 | FL Summary #4 on SRS enhancements | Moderator (FUTUREWEI) |
| TDoc | Title | Source |
|---|---|---|
| R1-2209092 | Considerations on UL precoding indication for multi-panel transmission | Sony |
| TDoc | Title | Source |
|---|---|---|
| R1-2208444 | Discussion on UL precoding indication for multi-panel transmission | Huawei, HiSilicon |
| R1-2208498 | Further Discussion for Uplink Multi-panel Transmission | InterDigital, Inc. |
| R1-2208507 | Enhancements on UL precoding indication for multi-panel transmission | ZTE |
| R1-2208544 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
| R1-2208631 | Discussion on UL precoding indication for multi-panel transmission | vivo |
| R1-2208678 | UL precoding indication for multi-panel transmission | Ericsson |
| R1-2208745 | UL precoding indication for multi-panel transmission | Lenovo |
| R1-2208797 | Transmission scheme and UL precoding indication for multi-panel transmission | OPPO |
| R1-2208875 | On Simultaneous Multi-Panel Transmission | |
| R1-2208896 | UL precoding indication for multi-panel transmission | LG Electronics |
| R1-2208950 | UL precoding indication for multi-panel transmission | CATT |
| R1-2209009 | Discussion on UL precoding indication for multi-panel transmission | Fujitsu |
| R1-2209044 | UL precoding indication for multi-panel transmission | Intel Corporation |
| R1-2209143 | Discussion on UL precoding indication for multi-panel transmission | NEC |
| R1-2209261 | Enhancements on multi-panel uplink transmission | xiaomi |
| R1-2209325 | Discussion on UL precoding indication for multi-panel transmission | CMCC |
| R1-2209384 | Views on UL multi-panel transmission | Sharp |
| R1-2209496 | Simultaneous transmission across multiple UE panels | MediaTek Inc. |
| R1-2209549 | On UL precoding indication for simultaneous multi-panel transmission | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209573 | Views on UL precoding indication for multi-panel simultaneous transmissions | Apple |
| R1-2209719 | Views on UL precoding indication for STxMP | Samsung |
| R1-2209893 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
| R1-2209972 | Simultaneous multi-panel transmission | Qualcomm Incorporated |
| R1-2210026 | UL precoding for multi-panel transmission | PANASONIC |
| R1-2210066 | Precoder Indication for Multi-Panel UL Transmission | Nokia, Nokia Shanghai Bell |
| R1-2210305 | Summary #1 on Rel-18 STxMP | Moderator (OPPO) |
| R1-2210306 | Summary #2 on Rel-18 STxMP | Moderator (OPPO) |
| R1-2210307 | Summary #3 on Rel-18 STxMP | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208445 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
| R1-2208499 | Enhanced SRI/TPMI for 8TX UE | InterDigital, Inc. |
| R1-2208508 | SRI/TPMI enhancement for enabling 8 TX UL transmission | ZTE |
| R1-2208545 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
| R1-2208632 | Discussion on enabling 8 TX UL transmission | vivo |
| R1-2208746 | SRI/TPMI enhancement for enabling 8TX UL transmission | Lenovo |
| R1-2208798 | SRI TPMI enhancement for 8 TX UL transmission | OPPO |
| R1-2208876 | On SRI/TPMI Indication for 8Tx Transmission | |
| R1-2208897 | SRI/TPMI enhancement for enabling 8 TX UL transmission | LG Electronics |
| R1-2208951 | Codebook and SRI/TPMI enhancement for UL 8 TX | CATT |
| R1-2209045 | Discussion on enhancement for 8Tx UL transmission | Intel Corporation |
| R1-2209093 | Discussion on enhancement for 8Tx UL transmission | Sony |
| R1-2209144 | Discussion on SRI/TPMI enhancement | NEC |
| R1-2209262 | Enhancements on 8Tx uplink transmission | xiaomi |
| R1-2209326 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | CMCC |
| R1-2209385 | Views on 8 TX UL transmission | Sharp |
| R1-2209497 | SRI/TPMI enhancement for enabling 8 Tx UL transmission | MediaTek Inc. |
| R1-2209574 | Views on SRI/TPMI enhancement for enabling 8 TX UL transmission | Apple |
| R1-2209671 | SRI/TPMI Enhancement for Enabling 8 TX UL Transmission | Ericsson |
| R1-2209720 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
| R1-2209894 | Discussion on 8 TX UL transmission | NTT DOCOMO, INC. |
| R1-2209973 | Enhancements for 8 Tx UL transmissions | Qualcomm Incorporated |
| R1-2210067 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
| R1-2210376 | FL Summary on SRI/TPMI Enhancements; First Round | Moderator (InterDigital) |
| R1-2210377 | FL Summary on SRI/TPMI Enhancements; Second Round | Moderator (InterDigital) |
| R1-2210378 | FL Summary on SRI/TPMI Enhancements; Third Round | Moderator (InterDigital) |
| R1-2210379 | Recommended Direction on SRI/TPMI Enhancements for RAN1#111 | Moderator (InterDigital) |
| TDoc | Title | Source |
|---|---|---|
| R1-2209974 | Technical report for Rel-18 SI on AI and ML for NR air interface | Qualcomm Incorporated |
| R1-2210690 | Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208365 | Continued discussion on common AI/ML characteristics and operations | FUTUREWEI |
| R1-2208428 | Discussion on general aspects of AI/ML framework | Huawei, HiSilicon |
| R1-2208520 | Discussion on general aspects of common AI PHY framework | ZTE |
| R1-2208546 | Discussion on general aspects of AIML framework | Spreadtrum Communications |
| R1-2208633 | Discussions on AI/ML framework | vivo |
| R1-2208739 | Discussion on general aspects of AI/ML framework | SEU |
| R1-2208768 | Discussion on general aspects of AI/ML for NR air interface | China Telecom |
| R1-2208849 | On general aspects of AI/ML framework | OPPO |
| R1-2208877 | On General Aspects of AI/ML Framework | |
| R1-2208898 | General aspects on AI/ML framework | LG Electronics |
| R1-2208908 | Discussion on general aspects of AI/ML framework | Ericsson |
| R1-2208966 | General aspects of AI/ML framework for NR air interface | CATT |
| R1-2209010 | Discussion on general aspects of AI/ML framework | Fujitsu |
| R1-2209046 | Discussion on general aspects of AI/ML framework | Intel Corporation |
| R1-2209088 | General aspects of AI/ML framework | AT&T |
| R1-2209094 | Considerations on common AI/ML framework | Sony |
| R1-2209119 | General aspects of AI/ML framework | Lenovo |
| R1-2209145 | Discussion on general aspects of AI ML framework | NEC |
| R1-2209229 | Considerations on general aspects on AI-ML framework | CAICT |
| R1-2209276 | Views on the general aspects of AL/ML framework | xiaomi |
| R1-2209327 | Discussion on general aspects of AI/ML framework | CMCC |
| R1-2209366 | Further discussion on the general aspects of ML for Air-interface | Nokia, Nokia Shanghai Bell |
| R1-2209389 | Discussions on Common Aspects of AI/ML Framework | TCL Communication |
| R1-2209399 | Discussion on general aspects of AI/ML framework for NR air interface | ETRI |
| R1-2209505 | General aspects of AI/ML framework | MediaTek Inc. |
| R1-2209575 | General aspect of AI/ML framework | Apple |
| R1-2209624 | General aspects of AI and ML framework for NR air interface | NVIDIA |
| R1-2209639 | Discussion on general aspects of AI ML framework | InterDigital, Inc. |
| R1-2209721 | General aspects of AI ML framework and evaluation methodology | Samsung |
| R1-2209764 | Discussion on AI/ML framework | Rakuten Mobile, Inc |
| R1-2209813 | Discussion on general aspects of AI/ML framework | Panasonic |
| R1-2209865 | Discussion on general aspects of AI/ML framework | KDDI Corporation |
| R1-2209895 | Discussion on general aspects of AI/ML framework | NTT DOCOMO, INC. |
| R1-2209975 | General aspects of AI/ML framework | Qualcomm Incorporated |
| R1-2210375 | Summary#1 of General Aspects of AI/ML Framework | Moderator (Qualcomm Incorporated) |
| R1-2210396 | Summary#1 of General Aspects of AI/ML Framework | Moderator (Qualcomm Incorporated) |
| R1-2210472 | Summary#2 of General Aspects of AI/ML Framework | Moderator (Qualcomm Incorporated) |
| R1-2210661 | Summary#3 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| R1-2210708 | Summary#4 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208366 | Continued discussion on evaluation of AI/ML for CSI feedback enhancement | FUTUREWEI |
| R1-2208429 | Evaluation on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2208521 | Evaluation on AI for CSI feedback enhancement | ZTE |
| R1-2208547 | Discussion on evaluation on AIML for CSI feedback enhancement | Spreadtrum Communications, BUPT |
| R1-2208634 | Evaluation on AI/ML for CSI feedback enhancement | vivo |
| R1-2208729 | Evaluations on AI-CSI | Ericsson |
| R1-2208769 | Evaluation on AI/ML for CSI feedback enhancement | China Telecom |
| R1-2208850 | Evaluation methodology and preliminary results on AI/ML for CSI feedback enhancement | OPPO |
| R1-2208878 | On Evaluation of AI/ML based CSI | |
| R1-2208899 | Evaluation on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2208967 | Evaluation on AI/ML for CSI feedback enhancement | CATT |
| R1-2209011 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu |
| R1-2209047 | Evaluation for CSI feedback enhancements | Intel Corporation |
| R1-2209120 | Evaluation on AI/ML for CSI feedback | Lenovo |
| R1-2209131 | Discussion on evaluation methodology and KPI on AI/ML for CSI feedback enhancement | Panasonic |
| R1-2209230 | Some discussions on evaluation on AI-ML for CSI feedback | CAICT |
| R1-2209277 | Discussion on evaluation on AI/ML for CSI feedback enhancement | xiaomi |
| R1-2209328 | Discussion on evaluation on AI/ML for CSI feedback enhancement | CMCC |
| R1-2209367 | Evaluation of ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2209386 | GRU for Historical CSI Prediction | Sharp |
| R1-2209400 | Evaluation on AI/ML for CSI feedback enhancement | ETRI |
| R1-2209506 | Evaluation on AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2209548 | Evaluation of AI/ML based methods for CSI feedback enhancement | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209576 | Evaluation on AI/ML for CSI feedback | Apple |
| R1-2209625 | Evaluation of AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2209640 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2209652 | Evaluation on AI/ML for CSI Feedback Enhancement | Mavenir |
| R1-2209722 | Evaluation on AI ML for CSI feedback enhancement | Samsung |
| R1-2209794 | Discussion on AI/ML for CSI feedback enhancement | AT&T |
| R1-2209896 | Discussion on evaluation on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2209976 | Evaluation on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2210272 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2210365 | Summary#1 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210366 | Summary#2 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210367 | Summary#3 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210368 | Summary#4 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210369 | Summary#5 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210752 | Summary#6 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| R1-2210753 | Summary#7 of [110bis-e-R18-AI/ML-02] | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208367 | Continued discussion on other aspects of AI/ML for CSI feedback enhancement | FUTUREWEI |
| R1-2208430 | Discussion on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2208522 | Discussion on other aspects for AI CSI feedback enhancement | ZTE |
| R1-2208548 | Discussion on other aspects on AIML for CSI feedback | Spreadtrum Communications |
| R1-2208635 | Other aspects on AI/ML for CSI feedback enhancement | vivo |
| R1-2208728 | Discussions on AI-CSI | Ericsson |
| R1-2208770 | Discussion on AI/ML for CSI feedback enhancement | China Telecom |
| R1-2208851 | On sub use cases and other aspects of AI/ML for CSI feedback enhancement | OPPO |
| R1-2208879 | On Enhancement of AI/ML based CSI | |
| R1-2208900 | Other aspects on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2208968 | Discussion on AI/ML for CSI feedback enhancement | CATT |
| R1-2209012 | Views on specification impact for CSI compression with two-sided model | Fujitsu |
| R1-2209048 | Use-cases and specification for CSI feedback | Intel Corporation |
| R1-2209095 | Considerations on CSI measurement enhancements via AI/ML | Sony |
| R1-2209121 | Further aspects of AI/ML for CSI feedback | Lenovo |
| R1-2209161 | Discussion on AI/ML for CSI feedback enhancement | Panasonic |
| R1-2209231 | Discussions on AI-ML for CSI feedback | CAICT |
| R1-2209278 | Discussion on specification impact for AI/ML based CSI feedback | xiaomi |
| R1-2209329 | Discussion on other aspects on AI/ML for CSI feedback enhancement | CMCC |
| R1-2209368 | Other aspects on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2209390 | Discussions on Sub-Use Cases in AI/ML for CSI Feedback Enhancement | TCL Communication |
| R1-2209401 | Discussion on other aspects on AI/ML for CSI feedback enhancement | ETRI |
| R1-2209424 | Discussion on AI/ML for CSI feedback enhancement | NEC |
| R1-2209507 | Other aspects on AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2209577 | Other aspects on AI/ML for CSI | Apple |
| R1-2209626 | AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2209641 | Discussion on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2209723 | Representative sub use cases for CSI feedback enhancement | Samsung |
| R1-2209795 | Discussion on AI/ML for CSI feedback enhancement | AT&T |
| R1-2209897 | Discussion on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2209977 | Other aspects on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2210319 | Summary #1 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2210320 | Summary #2 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2210321 | Summary #3 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2210611 | Summary #4 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208368 | Continued discussion on evaluation of AI/ML for beam management | FUTUREWEI |
| R1-2208431 | Evaluation on AI/ML for beam management | Huawei, HiSilicon |
| R1-2208523 | Evaluation on AI for beam management | ZTE |
| R1-2208549 | Evaluation on AI for beam management | Spreadtrum Communications |
| R1-2208636 | Evaluation on AI/ML for beam management | vivo |
| R1-2208682 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
| R1-2208771 | Evaluation on AI/ML for beam management | China Telecom |
| R1-2208852 | Evaluation methodology and preliminary results on AI/ML for beam management | OPPO |
| R1-2208880 | On Evaluation of AI/ML based Beam Management | |
| R1-2208901 | Evaluation on AI/ML for beam management | LG Electronics |
| R1-2208906 | Evaluation on AI/ML for beam management | Ericsson |
| R1-2208969 | Evaluation on AI/ML for beam management | CATT |
| R1-2209013 | Evaluation on AI/ML for beam management | Fujitsu |
| R1-2209049 | Evaluations for AI/ML beam management | Intel Corporation |
| R1-2209122 | Evaluation on AI/ML for beam management | Lenovo |
| R1-2209232 | Some discussions on evaluation on AI-ML for Beam management | CAICT |
| R1-2209279 | Evaluation on AI/ML for beam management | xiaomi |
| R1-2209330 | Discussion on evaluation on AI/ML for beam management | CMCC |
| R1-2209369 | Evaluation of ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2209508 | Evaluation on AI/ML for beam management | MediaTek Inc. |
| R1-2209578 | Evaluation on AI/ML for beam management | Apple |
| R1-2209613 | Evaluation of AI/ML based beam management | Rakuten Symphony |
| R1-2209627 | Evaluation of AI and ML for beam management | NVIDIA |
| R1-2209724 | Evaluation on AI ML for Beam management | Samsung |
| R1-2209898 | Discussion on evaluation on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2209978 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
| R1-2210107 | Evaluation on AI/ML for beam management | CEWiT |
| R1-2210240 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
| R1-2210327 | On Evaluation of AI/ML based Beam Management | |
| R1-2210359 | Feature lead summary #0 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2210360 | Feature lead summary #1 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2210361 | Feature lead summary #2 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2210362 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208369 | Continued discussion on other aspects of AI/ML for beam management | FUTUREWEI |
| R1-2208432 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
| R1-2208524 | Discussion on other aspects for AI beam management | ZTE |
| R1-2208550 | Discussion on other aspects on AIML for beam management | Spreadtrum Communications |
| R1-2208637 | Other aspects on AI/ML for beam management | vivo |
| R1-2208683 | Discussion for other aspects on AI/ML for beam management | InterDigital, Inc. |
| R1-2208853 | Other aspects of AI/ML for beam management | OPPO |
| R1-2208881 | On Enhancement of AI/ML based Beam Management | |
| R1-2208902 | Other aspects on AI/ML for beam management | LG Electronics |
| R1-2208907 | Discussion on AI/ML for beam management | Ericsson |
| R1-2208970 | Discussion on AI/ML for beam management | CATT |
| R1-2209014 | Sub use cases and specification impact on AI/ML for beam management | Fujitsu |
| R1-2209050 | Use-cases and Specification Impact for AI/ML beam management | Intel Corporation |
| R1-2209096 | Consideration on AI/ML for beam management | Sony |
| R1-2209123 | Further aspects of AI/ML for beam management | Lenovo |
| R1-2209146 | Discussion on AI/ML for beam management | NEC |
| R1-2209233 | Discussions on AI-ML for Beam management | CAICT |
| R1-2209280 | Discussion on other aspects on AI/ML for beam management | xiaomi |
| R1-2209331 | Discussion on other aspects on AI/ML for beam management | CMCC |
| R1-2209370 | Other aspects on ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2209391 | Discussions on Sub-Use Cases in AI/ML for Beam Management | TCL Communication |
| R1-2209402 | Discussion on other aspects on AI/ML for beam management | ETRI |
| R1-2209509 | Other aspects on AI/ML for beam management | MediaTek Inc. |
| R1-2209579 | Other aspects on AI/ML for beam management | Apple |
| R1-2209614 | Discussion on AI/ML for beam management | Rakuten Symphony |
| R1-2209628 | AI and ML for beam management | NVIDIA |
| R1-2209725 | Representative sub use cases for beam management | Samsung |
| R1-2209899 | Discussion on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2209979 | Other aspects on AI/ML for beam management | Qualcomm Incorporated |
| R1-2210085 | Discussion on sub use cases of AI/ML beam management | Panasonic |
| R1-2210086 | Discussion on other aspects on AI/ML for beam management | KT Corp. |
| R1-2210353 | Summary#1 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2210354 | Summary#2 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2210355 | Summary#3 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2210356 | Summary#4 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2210357 | Summary#5 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2210764 | Summary#6 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208399 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Ericsson |
| R1-2208433 | Evaluation on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2208525 | Evaluation on AI for positioning enhancement | ZTE |
| R1-2208638 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
| R1-2208772 | Evaluation on AI/ML for positioning accuracy enhancement | China Telecom |
| R1-2208854 | Evaluation methodology and preliminary results on AI/ML for positioning accuracy enhancement | OPPO |
| R1-2208882 | On Evaluation of AI/ML based Positioning | |
| R1-2208903 | Evaluation on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2208971 | Evaluation on AI/ML for positioning enhancement | CATT |
| R1-2209015 | Discussions on evaluation of AI positioning accuracy enhancement | Fujitsu |
| R1-2209124 | Discussion on AI/ML Positioning Evaluations | Lenovo |
| R1-2209234 | Some discussions on evaluation on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2209281 | Evaluation on AI/ML for positioning accuracy enhancement | xiaomi |
| R1-2209332 | Discussion on evaluation on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2209371 | Evaluation of ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2209484 | Evaluation on AI/ML for positioning accuracy enhancement | InterDigital, Inc. |
| R1-2209510 | Evaluation on AI/ML for positioning accuracy enhancement | MediaTek Inc. |
| R1-2209537 | Evaluation on AI/ML for positioning accuracy enhancement | Faunhofer IIS, Fraunhofer HHI |
| R1-2209580 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
| R1-2209615 | Evaluation of AI/ML based positioning accuracy enhancement | Rakuten Symphony |
| R1-2209629 | Evaluation of AI and ML for positioning enhancement | NVIDIA |
| R1-2209726 | Evaluation on AI ML for Positioning | Samsung |
| R1-2209980 | Evaluation on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2210385 | Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210386 | Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210387 | Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210388 | Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210650 | Summary #5 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210651 | Summary #6 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2210652 | Final Summary of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208400 | Other Aspects of AI/ML Based Positioning Enhancement | Ericsson |
| R1-2208434 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2208526 | Discussion on other aspects for AI positioning enhancement | ZTE |
| R1-2208551 | Discussion on other aspects on AIML for positioning accuracy enhancement | Spreadtrum Communications |
| R1-2208639 | Other aspects on AI/ML for positioning accuracy enhancement | vivo |
| R1-2208855 | On sub use cases and other aspects of AI/ML for positioning accuracy enhancement | OPPO |
| R1-2208883 | On Enhancement of AI/ML based Positioning | |
| R1-2208904 | Other aspects on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2208972 | Discussion on AI/ML for positioning enhancement | CATT |
| R1-2209016 | Discussions on sub use cases and specification impacts for AIML positioning | Fujitsu |
| R1-2209097 | Discussion on AI/ML for positioning accuracy enhancement | Sony |
| R1-2209125 | AI/ML Positioning use cases and Associated Impacts | Lenovo |
| R1-2209147 | Other aspects on AI/ML for positioning | NEC |
| R1-2209235 | Discussions on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2209282 | Views on the other aspects of AI/ML-based positioning accuracy enhancement | xiaomi |
| R1-2209333 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2209372 | Other aspects on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2209485 | Designs and potential specification impacts of AIML for positioning | InterDigital, Inc. |
| R1-2209538 | On potential specification impact of AI/ML for positioning | Faunhofer IIS, Fraunhofer HHI |
| R1-2209581 | Other aspects on AI/ML for positioning accuracy enhancement | Apple |
| R1-2209616 | Discussion on AI/ML for positioning accuracy enhancement | Rakuten Symphony |
| R1-2209630 | AI and ML for positioning enhancement | NVIDIA |
| R1-2209727 | Representative sub use cases for Positioning | Samsung |
| R1-2209900 | Discussion on AI/ML for positioning accuracy enhancement | NTT DOCOMO, INC. |
| R1-2209981 | Other aspects on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2210308 | FL summary #1 of [110bis-e-R18-AI/ML-07] | Moderator (vivo) |
| R1-2210427 | FL summary #2 of [110bis-e-R18-AI/ML-07] | Moderator (vivo) |
| R1-2210565 | FL summary #3 of [110bis-e-R18-AI/ML-07] | Moderator (vivo) |
| R1-2210669 | FL summary #4 of [110bis-e-R18-AI/ML-07] | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208408 | Discussion on evaluation and methodologies on evolution of NR duplex operation | Huawei, HiSilicon |
| R1-2208483 | Discussion of evaluation on NR duplex evolution | ZTE |
| R1-2208528 | Discussion for Evaluation on NR duplex evolution | New H3C Technologies Co., Ltd. |
| R1-2208531 | Discussion on evaluation on NR duplex operation | KT Corp. |
| R1-2208640 | Evaluation on NR duplex evolution | vivo |
| R1-2208856 | Discussion on evaluation on NR duplex evolution | OPPO |
| R1-2208973 | Discussion on evaluation on NR duplex evolution | CATT |
| R1-2209003 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications, BUPT |
| R1-2209027 | On evaluation methodology for NR-duplex | InterDigital, Inc. |
| R1-2209051 | Evaluations for NR duplex evolution | Intel Corporation |
| R1-2209098 | Preliminary System Level Simulation Results for SBFD | Sony |
| R1-2209174 | Evaluation of NR duplex evolution | Ericsson |
| R1-2209283 | Discussion on evaluation on NR duplex evolution | xiaomi |
| R1-2209334 | Summary#1 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2209335 | Discussion on evaluation on NR duplex evolution | CMCC |
| R1-2209423 | Evaluation of UE-UE CLI for NR SBFD operation | NEC |
| R1-2209582 | Initial evaluation on NR duplex evolution | Apple |
| R1-2209728 | Discussion on evaluation for NR duplex evolution | Samsung |
| R1-2209769 | Deployment scenarios and evaluation methodology for NR duplex evolution | MediaTek Inc. |
| R1-2209808 | Study on Evaluation for NR duplex evolution | LG Electronics |
| R1-2209901 | Discussion on evaluation on NR duplex evolution | NTT DOCOMO, INC. |
| R1-2209982 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | Qualcomm Incorporated |
| R1-2210041 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210194 | Considerations and Recommendations for Evaluation of NR Duplex evolution | Charter Communications, Inc |
| R1-2210415 | Summary#2 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210416 | Summary#3 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210417 | Summary#4 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210599 | Summary#5 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210600 | Summary#6 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210601 | Draft LS on interference modelling for duplex evolution | Moderator (CMCC) |
| R1-2210602 | LS on interference modelling for duplex evolution | RAN1, CMCC |
| R1-2210758 | Summary#7 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2210779 | Final summary on evaluation on NR duplex evolution | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208403 | Discussion on subband non-overlapping full duplex | TCL Communication Ltd. |
| R1-2208409 | Discussion on potential enhancement on subband non-overlapping full duplex | Huawei, HiSilicon |
| R1-2208484 | Discussion of subband non-overlapping full duplex | ZTE |
| R1-2208527 | Discussion for subband non-overlapping full duplex | New H3C Technologies Co., Ltd. |
| R1-2208552 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
| R1-2208641 | Discussion on subband non-overlapping full duplex | vivo |
| R1-2208857 | Discussion on subband non-overlapping full duplex | OPPO |
| R1-2208974 | Discussion on subband non-overlapping full duplex | CATT |
| R1-2209021 | Discussion on subband non-overlapping full duplex | Fujitsu |
| R1-2209028 | Discussion on subband non-overlapping full duplex | InterDigital, Inc. |
| R1-2209052 | Potential solutions for SBFD in NR systems | Intel Corporation |
| R1-2209099 | Considerations on Subband Full Duplex TDD Operations | Sony |
| R1-2209126 | Subband non-overlapping full duplex | Lenovo |
| R1-2209175 | Subband non-overlapping full duplex | Ericsson |
| R1-2209240 | Discussion on subband non-overlapping full duplex | Panasonic |
| R1-2209284 | Discussion on subband non-overlapping full duplex | xiaomi |
| R1-2209336 | Discussion on subband non-overlapping full duplex | CMCC |
| R1-2209403 | Discussion on subband non-overlapping full duplex enhancements | ETRI |
| R1-2209421 | Discussion on subband non-overlapping full duplex | NEC |
| R1-2209583 | Views on subband non-overlapping full duplex | Apple |
| R1-2209729 | SBFD feasibility and design considerations for NR duplex evolution | Samsung |
| R1-2209770 | Discussion on subband non-overlapping full duplex for NR | MediaTek Inc. |
| R1-2209809 | Study on Subband non-overlapping full duplex | LG Electronics |
| R1-2209902 | Discussion on subband non-overlapping full duplex | NTT DOCOMO, INC. |
| R1-2209930 | Discussion on subband non-overlapping full duplex | Sharp |
| R1-2209983 | Feasibility and techniques for Subband non-overlapping full duplex | Qualcomm Incorporated |
| R1-2210030 | Discussion on sub-band non-overlapping full duplex | ITRI |
| R1-2210042 | On subband non-overlapping full duplex for NR | Nokia, Nokia Shanghai Bell |
| R1-2210093 | Details of subband non-overlapping full duplex | ASUSTeK |
| R1-2210108 | Discussion on subband non-overlapping full duplex | CEWiT |
| R1-2210138 | Discussion on subband non-overlapping full duplex | WILUS Inc. |
| R1-2210143 | Inter-UE CLI Test Results for NR Duplex Evolution | KDDI Corporation |
| R1-2210314 | Summary #1 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2210315 | Summary #2 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2210316 | Summary #3 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2210317 | Summary #4 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2210670 | Draft LS on maximum number of UL subbands for duplex evolution | Moderator (CATT) |
| R1-2210671 | LS on maximum number of UL subbands for duplex evolution | RAN1, CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2208404 | Potential Enhancement on dynamic/flexible TDD | TCL Communication Ltd. |
| R1-2208410 | Discussion on potential enhancements on dynamic/flexible TDD | Huawei, HiSilicon |
| R1-2208485 | Discussion of enhancements on dynamic/flexible TDD | ZTE |
| R1-2208553 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
| R1-2208642 | Potential enhancements on dynamic/flexible TDD | vivo |
| R1-2208726 | Study on potential enhancement on dynamic/flexible TDD | New H3C Technologies Co., Ltd. |
| R1-2208858 | Discussion on potential enhancements on dynamic/flexible TDD | OPPO |
| R1-2208975 | Discussion on potential enhancements on dynamic/flexible TDD | CATT |
| R1-2209029 | Potential enhancements on dynamic and flexible TDD | InterDigital, Inc. |
| R1-2209053 | Potential enhancements on dynamic/flexible TDD | Intel Corporation |
| R1-2209100 | Considerations on Flexible/Dynamic TDD | Sony |
| R1-2209176 | Potential enhancements of dynamic TDD | Ericsson |
| R1-2209220 | Potential enhancements on dynamic/flexible TDD | Lenovo |
| R1-2209285 | Discussion on potential enhancements on dynamic TDD | xiaomi |
| R1-2209337 | Discussion on potential enhancements on flexible/dynamic TDD | CMCC |
| R1-2209420 | Views on enhancements of dynamic/flexible TDD | NEC |
| R1-2209584 | Views on potential enhancements on dynamic/flexible TDD | Apple |
| R1-2209730 | Dynamic and flexible TDD for NR duplex evolution | Samsung |
| R1-2209771 | Discussion on potential enhancements on dynamic/flexible TDD | MediaTek Inc. |
| R1-2209810 | Study on Potential enhancements on dynamic/flexible TDD | LG Electronics |
| R1-2209903 | Discussion on potential enhancements on dynamic/flexible TDD | NTT DOCOMO, INC. |
| R1-2209984 | On potential enhancements on dynamic/flexible TDD | Qualcomm Incorporated |
| R1-2210043 | Dynamic TDD enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210109 | Discussion on enhancements on dynamic/flexible TDD | CEWiT |
| R1-2210403 | Summary #1 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2210404 | Summary #2 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2210405 | Summary #3 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2210406 | Summary #4 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210691 | Session notes for 9.4 (NR sidelink evolution) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208356 | On Channel Access Mechanism for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2208370 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | FUTUREWEI |
| R1-2208448 | Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2208554 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2208643 | Channel access mechanism for sidelink on unlicensed spectrum | vivo |
| R1-2208722 | Discussion on channel access mechanism for SL-U | ZTE, Sanechips |
| R1-2208822 | On channel access mechanism and resource allocation for SL-U | OPPO |
| R1-2208976 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2209017 | Discussion on channel access mechanism for SL-U | Fujitsu |
| R1-2209054 | Channel Access Mechanisms for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2209081 | Discussion on channel access mechanisms | Johns Hopkins University APL |
| R1-2209101 | Discussion on channel access mechanism for SL-unlicensed | Sony |
| R1-2209148 | Channel Access of Sidelink on Unlicensed Spetrum | NEC |
| R1-2209167 | Discussion of channel access mechanism for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2209236 | Considerations on channel access mechanism of SL-U | CAICT |
| R1-2209286 | Discussion on channel access mechanism for sidelink-unlicensed | xiaomi |
| R1-2209301 | Channel access mechanism for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2209338 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CMCC |
| R1-2209404 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | ETRI |
| R1-2209417 | NR Sidelink Unlicensed Channel Access Mechanisms | Fraunhofer HHI, Fraunhofer IIS |
| R1-2209478 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | LG Electronics |
| R1-2209529 | Discussion on channel access mechanism | MediaTek Inc. |
| R1-2209551 | SL-U Simulation assumption parameters | CableLabs |
| R1-2209585 | Channel access mechanism for sidelink on FR1 unlicensed band | Apple |
| R1-2209646 | Further Details of Channel Access Mechanism | National Spectrum Consortium |
| R1-2209659 | SL Channel access in unlicensed spectrum | InterDigital, Inc. |
| R1-2209731 | On channel access mehanism for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2209767 | On Channel Access Mechanism for SL-U | ITL |
| R1-2209775 | Discussion on Channel access mechanism for NR sidelink evolution | Sharp |
| R1-2209780 | Sidelink channel access on unlicensed spectrum | Panasonic |
| R1-2209904 | Discussion on channel access mechanism in SL-U | NTT DOCOMO, INC. |
| R1-2209985 | Channel Access Mechanism for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2210074 | Discussion on sidelink on unlicensed spectrum | ASUSTeK |
| R1-2210082 | Discussions on channel access mechanism for sidelink on unlicensed spectrum | ROBERT BOSCH GmbH |
| R1-2210132 | Channel access mechanism for SL-U | Ericsson |
| R1-2210139 | Discussion on channel access mechanism for SL on unlicensed spectrum | WILUS Inc. |
| R1-2210271 | SL-U Simulation assumption parameters | CableLabs, Broadcom, Hewlett-Packard Enterprise, Cisco |
| R1-2210289 | FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2210290 | FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2210291 | FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2210292 | FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2210293 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) | Moderator (OPPO) |
| R1-2210709 | FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208357 | On Physical Channel Design Framework for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2208371 | Discussion on physical channel design for sidelink on unlicensed spectrum | FUTUREWEI |
| R1-2208449 | Physical channel design for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2208492 | Discussion on physical channel design of Sidelink on unlicensed spectrum | Quectel |
| R1-2208555 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2208644 | Physical channel design framework for sidelink on unlicensed spectrum | vivo |
| R1-2208723 | Discussion on physical layer structures and procedures for SL-U | ZTE, Sanechips |
| R1-2208823 | On PHY channel designs and procedures for SL-U | OPPO |
| R1-2208977 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2209055 | Physical Channel Design for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2209083 | Discussion on physical channel design framework | Johns Hopkins University APL |
| R1-2209102 | Discussion on physical channel design framework for SL-unlicensed | Sony |
| R1-2209149 | Discussion on physical channel design framework | NEC |
| R1-2209168 | Discussion of physical channel design for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2209202 | Discussion on Physical channel design framework for sidelink on unlicensed spectrum | Hyundai Motor Company |
| R1-2209287 | Discussion on physical channel design for sidelink-unlicensed | xiaomi |
| R1-2209302 | Physical layer design framework for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2209339 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CMCC |
| R1-2209405 | Discussion on physical channel design framework for SL-U | ETRI |
| R1-2209418 | NR Sidelink Unlicensed Physical Channel Design | Fraunhofer HHI, Fraunhofer IIS |
| R1-2209479 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
| R1-2209530 | Discussion on physical channel design framework | MediaTek Inc. |
| R1-2209586 | Discussion on Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum | Apple |
| R1-2209647 | Physical Channel Design Considerations | National Spectrum Consortium |
| R1-2209660 | SL U physical layer design framework | InterDigital, Inc. |
| R1-2209732 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2209773 | On Physical Channel Design framework for SL-U | ITL |
| R1-2209776 | Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum | Sharp |
| R1-2209781 | Physical channel design for sidelink on unlicensed spectrum | Panasonic |
| R1-2209905 | Discussion on channel design framework in SL-U | NTT DOCOMO, INC. |
| R1-2209986 | Physical Channel Design for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2210044 | Physical channel design for sidelink on unlicensed spectrum | EURECOM |
| R1-2210133 | PHY channel design framework for SL-U | Ericsson |
| R1-2210140 | Discussion on PHY channel design framework for SL on unlicensed spectrum | WILUS Inc. |
| R1-2210252 | FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2210253 | FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2210254 | FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2210255 | FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2210256 | FL summary#5 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208358 | On Co-channel Coexistence for LTE Sidelink and NR Sidelink | Nokia, Nokia Shanghai Bell |
| R1-2208450 | Co-channel coexistence for LTE sidelink and NR sidelink | Huawei, HiSilicon |
| R1-2208556 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Spreadtrum Communications |
| R1-2208645 | Co-channel coexistence for LTE sidelink and NR sidelink | vivo |
| R1-2208724 | Study on co-channel coexistence for LTE sidelink and NR sidelink | ZTE, Sanechips |
| R1-2208765 | Discussion on Sidelink Co-channel Coexistence | Panasonic |
| R1-2208824 | Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL | OPPO |
| R1-2208978 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CATT, GOHIGH |
| R1-2209056 | Considerations for LTE Sidelink and NR Sidelink Co-channel Coexistence | Intel Corporation |
| R1-2209103 | Discussion on co-channel coexistence for LTE sidelink | Sony |
| R1-2209150 | Co-existence between LTE and NR sidelink | NEC |
| R1-2209169 | Discussion of co-channel coexistence for LTE sidelink and NR sidelink | Transsion Holdings |
| R1-2209237 | Considerations on co-channel coexistence for LTE SL and NR SL | CAICT |
| R1-2209288 | Discussion on co-channel coexistence for LTE and NR sidelink | xiaomi |
| R1-2209303 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Lenovo |
| R1-2209340 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CMCC |
| R1-2209406 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | ETRI |
| R1-2209419 | Discussion on Co-Channel Coexistence for LTE and NR Sidelink | Fraunhofer HHI, Fraunhofer IIS |
| R1-2209480 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics |
| R1-2209520 | Co-channel coexistence for NR sidelink and LTE sidelink | MediaTek Inc. |
| R1-2209587 | Discussion on Co-channel Coexistence for LTE Sidelink and NR Sidelink | Apple |
| R1-2209611 | On sidelink co-channel coexistence issues | Mitsubishi Electric RCE |
| R1-2209632 | Discussion on dynamic co-channel coexistence for LTE sidelink and NR sidelink | TOYOTA Info Technology Center |
| R1-2209637 | Co-channel coexistence for LTE sidelink and NR sidelink | InterDigital, Inc. |
| R1-2209733 | On co-channel coexistence for LTE sidelink and NR sidelink | Samsung |
| R1-2209777 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Sharp |
| R1-2209906 | Discussion on co-channel coexistence of LTE-SL and NR-SL | NTT DOCOMO, INC. |
| R1-2209987 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
| R1-2210080 | Views on LTE and NR sidelink co-channel coexistence | ROBERT BOSCH GmbH |
| R1-2210131 | Co-channel coexistence between LTE sidelink and NR sidelink | Ericsson |
| R1-2210141 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | WILUS Inc. |
| R1-2210187 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Continental Automotive GmbH |
| R1-2210188 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Continental Automotive GmbH |
| R1-2210189 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Continental Automotive GmbH |
| R1-2210294 | FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2210295 | FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2210296 | FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2210297 | FL Summary #4 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2210298 | FL Summary EoM of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2210397 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2208359 | On Evaluation Methodology for Sidelink in FR2 | Nokia, Nokia Shanghai Bell |
| R1-2208451 | Evaluation methodology for sidelink operation on FR2 licensed spectrum | Huawei, HiSilicon |
| R1-2208557 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Spreadtrum Communications |
| R1-2208646 | Enhanced sidelink operation on FR2 licensed spectrum | vivo |
| R1-2208725 | Discussion on the evaluation methodology for SL on FR2 | ZTE, Sanechips |
| R1-2208825 | On updating evaluation methodology for SL operation in FR2 | OPPO |
| R1-2208979 | Discussion on the evaluation methodology for enhanced sidelink operation on FR2 licensed spectrum | CATT, GOHIGH |
| R1-2209057 | Evaluation Methodologies for SL Operating in FR-2 licensed band | Intel Corporation |
| R1-2209082 | Discussion on evaluation methodology for commercial deployment scenario | Johns Hopkins University APL |
| R1-2209289 | Discussion on updating the evaluation methodology for commercial deployment scenario | xiaomi |
| R1-2209304 | Discussion on evaluation methodology for sidelink on FR2 | Lenovo |
| R1-2209407 | Discussion on evaluation methodology for enhanced SL operation on FR2 | ETRI |
| R1-2209481 | Discussion on evaluation methodology for sidelink on FR2 licensed spectrum | LG Electronics |
| R1-2209531 | Discussion on evaluation methodology for SL FR2 licensed spectrum | MediaTek Inc. |
| R1-2209588 | Evaluation Methodology for Sidelink Operation on FR2 Licensed Spectrum | Apple |
| R1-2209638 | On enhanced SL FR2 operation | InterDigital, Inc. |
| R1-2209734 | Evaluation Methodology for Enhanced SL Operation in FR2 | Samsung |
| R1-2209988 | Enhanced sidelink operation on FR2 licensed spectrum | Qualcomm Incorporated |
| R1-2210110 | Discussion on evaluation methodology for beam enhancement on sidelink FR2 operation | CEWiT |
| R1-2210134 | Evaluation methodology for sidelink in FR2 | Ericsson |
| R1-2210262 | FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
| R1-2210331 | FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
| R1-2210425 | FL summary #3 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210037 | Work Plan for Study Item on Expanded and Improved NR Positioning | Intel Corporation, CATT, Ericsson |
| R1-2210233 | Draft TR 38.859 v020: Study on expanded and improved NR positioning | Intel, CATT, Ericsson |
| R1-2210672 | Draft TR 38.859 v020: Study on expanded and improved NR positioning | Intel, CATT, Ericsson |
| R1-2210692 | Session notes for 9.5 (Study on expanded and improved NR positioning) | Ad-Hoc Chair (Huawei) |
| R1-2210715 | Draft TR 38.859 v020: Study on expanded and improved NR positioning | Intel, CATT, Ericsson |
| R1-2210717 | Comments to Draft TR 38.859 v020: Study on expanded and improved NR positioning | Intel, CATT, Ericsson |
| R1-2210795 | Post-meeting Comments to Draft TR 38.859 v020: Study on expanded and improved NR positioning | Rapporteur (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210443 | Moderator summary on discussion on incoming SA2 LS in R1-2208338 on terminology alignment | Moderator (Xiaomi) |
| R1-2210550 | [Draft] Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | Xiaomi |
| R1-2210567 | Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | RAN1, xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R1-2208363 | Evaluation of SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2208452 | SL positioning evaluations | Huawei, HiSilicon |
| R1-2208647 | Evaluation of sidelink positioning performance | vivo |
| R1-2208820 | Evaluation methodology and results of SL positioning | OPPO |
| R1-2208980 | Evaluation methodology and performance evaluation for SL positioning | CATT, GOHIGH |
| R1-2209104 | Discussion on evaluation of SL positioning | Sony |
| R1-2209212 | Discussion on evaluation of SL positioning | ZTE, CMCC |
| R1-2209290 | Discussion on evaluation of sidelink positioning | xiaomi |
| R1-2209392 | SL Positioning Evaluation and Performance | Lenovo |
| R1-2209459 | Summary #1 for SL positioning evaluation | Moderator (ZTE) |
| R1-2209460 | Summary #2 for SL positioning evaluation | Moderator (ZTE) |
| R1-2209482 | Discussion on evaluation of SL positioning | LG Electronics |
| R1-2209486 | Evaluation results for SL positioning | InterDigital, Inc. |
| R1-2209735 | Discussion on Evaluation for SL Positioning | Samsung |
| R1-2209782 | SL positioning scenarios | Sharp |
| R1-2209989 | Sidelink Positioning Evaluation Assumptions and Results | Qualcomm Incorporated |
| R1-2210038 | Evaluation of SL positioning | Intel Corporation |
| R1-2210111 | Evaluation results and observations on V2X and IIoT use case for sidelink positioning | CEWiT |
| R1-2210174 | Evaluation of NR SL positioning and ranging | Ericsson |
| R1-2210284 | Evaluation of NR SL positioning and ranging | Ericsson |
| R1-2210579 | Summary #3 for SL positioning evaluation | Moderator (ZTE ) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208364 | Potential solutions for SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2208372 | Potential solutions for sidelink positioning | FUTUREWEI |
| R1-2208453 | Discussion on SL positioning solutions | Huawei, HiSilicon |
| R1-2208558 | Discussion on potential solutions for SL positioning | Spreadtrum Communications |
| R1-2208648 | Discussion on potential solutions for sidelink positioning | vivo |
| R1-2208773 | Discussion on potential solutions for sidelink positioning | China Telecom |
| R1-2208821 | Discussion on potential solutions for SL positioning | OPPO |
| R1-2208981 | Discussion on potential solutions for SL positioning | CATT, GOHIGH |
| R1-2209058 | Potential solutions for SL positioning | Intel Corporation |
| R1-2209105 | Consideration on potential solutions for SL positioning | Sony |
| R1-2209151 | Discussion on potential solutions for SL positioning | NEC |
| R1-2209213 | Discussion on potential solutions for SL positioning | ZTE |
| R1-2209291 | Discussion on sidelink positioning solutions | xiaomi |
| R1-2209341 | Discussion on potential solutions for SL positioning | CMCC |
| R1-2209393 | Potential SL Positioning Solutions | Lenovo |
| R1-2209483 | Discussion on potential solutions for SL positioning | LG Electronics |
| R1-2209487 | Potential solutions for SL positioning | InterDigital, Inc. |
| R1-2209533 | Potential solutions for SL positioning | Faunhofer IIS, Fraunhofer HHI |
| R1-2209589 | Discussions on Potential solutions for SL positioning | Apple |
| R1-2209675 | Discussion on potential solutions for SL positioning | DENSO CORPORATION |
| R1-2209736 | Discussion on Potential Solutions for SL Positioning | Samsung |
| R1-2209783 | Views on potential solutions for SL positioning | Sharp |
| R1-2209797 | Discussion on sidelink positioning | ASUSTeK |
| R1-2209907 | Discussion on potential solutions for SL positioning | NTT DOCOMO, INC. |
| R1-2209990 | Potential Solutions for Sidelink Positioning | Qualcomm Incorporated |
| R1-2210097 | The potential solutions for sidelink positioning | MediaTek Inc. |
| R1-2210102 | Considerable solutions on sidelink positioning in NR | ITL |
| R1-2210112 | Discussion on enhancements for sidelink based positioning | CEWiT |
| R1-2210175 | On potential solutions for SL positioning | Ericsson |
| R1-2210341 | Moderator Summary #1 on potential solutions for SL positioning | Moderator (Qualcomm Incorporated) |
| R1-2210381 | Moderator Summary #2 on potential solutions for SL positioning | Moderator (Qualcomm Incorporated) |
| R1-2210522 | Moderator Summary #3 on potential solutions for SL positioning | Moderator (Qualcomm Incorporated) |
| R1-2210598 | Moderator Summary #4 on potential solutions for SL positioning | Moderator (Qualcomm Incorporated) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208454 | Error source for NR RAT-dependent positioning | Huawei, HiSilicon |
| R1-2208480 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208511 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208512 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208513 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208514 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208515 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208516 | Discussion on integrity of RAT dependent positioning | BUPT |
| R1-2208649 | Discussion on solutions for integrity of RAT-dependent positioning | vivo |
| R1-2208735 | Views on solutions for integrity of RAT-dependent positioning techniques | Nokia, Nokia Shanghai Bell |
| R1-2208800 | Discussions on Integrity for NR Positioning | OPPO |
| R1-2208982 | Discussion on solutions for integrity of RAT dependent positioning techniques | CATT |
| R1-2209002 | Discussion on error sources for RAT dependent positioning | Spreadtrum Communications |
| R1-2209106 | Discussion on Error Sources for Integrity of NR Positioning | Sony |
| R1-2209214 | Discussion on integrity of RAT dependent positioning | ZTE |
| R1-2209292 | Error source for NR RAT-dependent positioning integrity | xiaomi |
| R1-2209342 | Discussion on integrity for RAT-dependent positioning | CMCC |
| R1-2209394 | Integrity aspects for RAT-dependent positioning | Lenovo |
| R1-2209488 | Discussion on integrity for RAT dependent positioning techniques | InterDigital, Inc. |
| R1-2209737 | Discussion on Integrity of RAT Dependent Positioning | Samsung |
| R1-2209784 | Views on solutions for integrity of RAT dependent positioning techniques | Sharp |
| R1-2209908 | Discussion on solutions for integrity of RAT dependent positioning techniques | NTT DOCOMO, INC. |
| R1-2209991 | Integrity for RAT dependent positioning | Qualcomm Incorporated |
| R1-2210176 | Error Sources characterization for integrity of RAT dependent positioning techniques | Ericsson |
| R1-2210274 | FL summary #1 on integrity of RAT dependent positioning techniques | Moderator (InterDigital, Inc.) |
| R1-2210428 | FL summary #2 on integrity of RAT dependent positioning techniques | Moderator (InterDigital, Inc.) |
| R1-2210633 | FL summary #3 on integrity of RAT dependent positioning techniques | Moderator (InterDigital, Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208455 | Discussion on NR carrier phase positioning | Huawei, HiSilicon |
| R1-2208650 | Discussion on carrier phase measurement enhancements | vivo |
| R1-2208736 | Views on improved accuracy based on NR carrier phase measurement | Nokia, Nokia Shanghai Bell |
| R1-2208774 | Discussion on improved accuracy based on NR carrier phase measurement | China Telecom |
| R1-2208801 | Discussions on Carrier Phase Measurement for NR Positioning | OPPO |
| R1-2208983 | Discussion on improved accuracy based on NR carrier phase measurement | CATT |
| R1-2209059 | Carrier phase positioning in NR systems | Intel Corporation |
| R1-2209152 | Discussion on NR carrier phase positioning | NEC |
| R1-2209215 | Discussion on carrier phase measurement based positioning | ZTE |
| R1-2209293 | Improved accuracy based on NR carrier phase measurement | xiaomi |
| R1-2209343 | Discussion on carrier phase positioning | CMCC |
| R1-2209395 | On NR carrier phase measurements | Lenovo |
| R1-2209489 | Discussion on positioning based on NR carrier phase measurement | InterDigital, Inc. |
| R1-2209534 | NR carrier phase measurements for positioning | Faunhofer IIS, Fraunhofer HHI |
| R1-2209543 | Discussion on double difference method and gNB synchronization | Locaila |
| R1-2209546 | Views on NR carrier phase measurement for positioning accuracy enhancement | IIT Kanpur, CEWiT |
| R1-2209738 | Discussion on NR Carrier Phase Measurement | Samsung |
| R1-2209785 | Views on improved accuracy based on NR carrier phase measurement | Sharp |
| R1-2209805 | Discussion on OFDM based carrier phase measurement in NR | LG Electronics |
| R1-2209909 | Discussion on improved accuracy based on NR carrier phase measurement | NTT DOCOMO, INC. |
| R1-2209992 | Phase Measurements in NR Positioning | Qualcomm Incorporated |
| R1-2210099 | On NR carrier phase measurement | MediaTek Inc. |
| R1-2210177 | Improved accuracy based on NR carrier phase measurement | Ericsson |
| R1-2210267 | FL Summary #1 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| R1-2210268 | FL Summary #2 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| R1-2210269 | FL Summary #3 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| R1-2210765 | FL Summary #4 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208456 | Evaluation and solutions for LPHAP | Huawei, HiSilicon |
| R1-2208517 | Discussion on Low Power High Accuracy Positioning | Quectel |
| R1-2208559 | Discussion on evaluation on LPHAP | Spreadtrum Communications |
| R1-2208651 | Discussion on Low Power High Accuracy Positioning | vivo |
| R1-2208737 | Views on LPHAP | Nokia, Nokia Shanghai Bell |
| R1-2208802 | Discussion on Low Power High Accuracy Positioning | OPPO |
| R1-2208984 | Discussion on Low Power High Accuracy Positioning | CATT |
| R1-2209060 | On Low Power High Accuracy Positioning | Intel Corporation |
| R1-2209107 | Discussion on Low Power High Accuracy Positioning | Sony |
| R1-2209216 | Discussion on low power high accuracy positioning | ZTE |
| R1-2209294 | Discussion on Low Power High Accuracy Positioning | xiaomi |
| R1-2209344 | Discussion on low power high accuracy positioning | CMCC |
| R1-2209345 | Summary for low power high accuracy positioning | Moderator (CMCC) |
| R1-2209396 | LPHAP considerations | Lenovo |
| R1-2209490 | Discussions on Low Power High Accuracy Positioning (LPHAP) techniques | InterDigital, Inc. |
| R1-2209739 | Discussion on LPHAP | Samsung |
| R1-2209786 | Views on low power high accuracy positioning | Sharp |
| R1-2209806 | Discussion on LPHAP in idle/inactive state | LG Electronics |
| R1-2209910 | Discussion on Low Power High Accuracy Positioning | NTT DOCOMO, INC. |
| R1-2209993 | Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning | Qualcomm Incorporated |
| R1-2210178 | Evaluations for Low Power High Accuracy Positioning | Ericsson |
| R1-2210242 | Discussion on Low Power High Accuracy Positioning | CATT |
| R1-2210398 | Discussion on low power high accuracy positioning | ZTE |
| R1-2210616 | FL summary #2 for low power high accuracy positioning | Moderator (CMCC) |
| R1-2210617 | FL summary #3 for low power high accuracy positioning | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208457 | Discussion on RedCap positioning | Huawei, HiSilicon |
| R1-2208652 | Discussion on positioning for RedCap UEs | vivo |
| R1-2208738 | Views on Positioning for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2208803 | Discussion on Positioning for RedCap Ues | OPPO |
| R1-2208985 | Discussion on positioning for RedCap UEs | CATT |
| R1-2209061 | Enhancements for positioning for RedCap UEs | Intel Corporation |
| R1-2209108 | Considerations on positioning for RedCap UEs | Sony |
| R1-2209153 | Discussion on positioning support for RedCap UEs | NEC |
| R1-2209217 | Discussion on Positioning for RedCap UE | ZTE |
| R1-2209346 | Discussion on RedCap positioning | CMCC |
| R1-2209397 | Positioning for RedCap devices | Lenovo |
| R1-2209491 | Discussions on positioning for RedCap UEs | InterDigital, Inc. |
| R1-2209590 | Discussions on Positioning for RedCap Ues | Apple |
| R1-2209740 | Discussion on Positioning for RedCap UEs | Samsung |
| R1-2209787 | Views on positioning for RedCap UEs | Sharp |
| R1-2209807 | Discussion on positioning support for RedCap Ues | LG Electronics |
| R1-2209911 | Discussion on positioning for RedCap UEs | NTT DOCOMO, INC. |
| R1-2209994 | Positioning for Reduced Capability UEs | Qualcomm Incorporated |
| R1-2210179 | Positioning for RedCap Ues | Ericsson |
| R1-2210474 | Feature Lead Summary #1 for Positioning for RedCap UEs | Moderator (Ericsson) |
| R1-2210475 | Feature Lead Summary #2 for Positioning for RedCap UEs | Moderator (Ericsson) |
| R1-2210476 | Feature Lead Summary #3 for Positioning for RedCap UEs | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208361 | WI work plan for Rel-18 RedCap | Rapporteur (Ericsson) |
| R1-2210637 | RAN1 agreements for Rel-18 NR RedCap | Rapporteur (Ericsson) |
| R1-2210693 | Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208362 | Further RedCap UE complexity reduction | Ericsson |
| R1-2208387 | Discussion on details for R18 RedCap complexity techniques | FUTUREWEI |
| R1-2208416 | Discussion on potential solutions to further reduce UE complexity | Huawei, HiSilicon |
| R1-2208560 | Discussion on enhanced support of RedCap devices | Spreadtrum Communications |
| R1-2208653 | Discussion on UE further complexity reduction | vivo, Guangdong Genius |
| R1-2208775 | Discussion on UE complexity reduction | China Telecom |
| R1-2208842 | Technologies for further reduced UE complexity | OPPO |
| R1-2208986 | Discussion on further complexity reduction for eRedCap UE | CATT |
| R1-2209004 | RedCap UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
| R1-2209062 | Discussion on complexity reduction for eRedCap UE | Intel Corporation |
| R1-2209109 | UE complexity reduction for eRedCap | Sony |
| R1-2209163 | Discussion on Rel-18 RedCap UE | NEC |
| R1-2209170 | Discussion on UE complexity reduction | Transsion Holdings |
| R1-2209194 | Discussion on further UE complexity reduction | ZTE, Sanechips |
| R1-2209221 | UE complexity reduction | Lenovo |
| R1-2209295 | Discussion on further complexity reduction for eRedCap UEs | xiaomi |
| R1-2209347 | Discussion on further UE complexity reduction | CMCC |
| R1-2209451 | Discussion on further UE complexity reduction for eRedCap | LG Electronics |
| R1-2209519 | On further UE complexity reduction for RedCap | MediaTek Inc. |
| R1-2209591 | Discussion on further RedCap UE complexity reduction | Apple |
| R1-2209663 | Considerations for further UE complexity reduction | Sierra Wireless. S.A. |
| R1-2209684 | Discussion on UE complexity reduction | Sharp |
| R1-2209741 | Further UE complexity reduction for eRedCap | Samsung |
| R1-2209791 | UE complexity reduction for eRedCap | Panasonic |
| R1-2209866 | Discussion on UE complexity reduction | DENSO CORPORATION |
| R1-2209912 | Discussion on further UE complexity reduction for eRedCap | NTT DOCOMO, INC. |
| R1-2209995 | UE complexity reduction for eRedCap | Qualcomm Incorporated |
| R1-2210196 | On further complexity reduction of NR UE | Nordic Semiconductor ASA |
| R1-2210248 | FL summary #1 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
| R1-2210249 | FL summary #2 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
| R1-2210250 | FL summary #3 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
| R1-2210251 | FL summary #4 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
| R1-2210283 | Further RedCap UE complexity reduction | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2209679 | TR 38.864 v0.2.0 for study on network energy savings for NR | Huawei |
| R1-2210593 | Comment collection for draftTR 38.864 | Moderator (Huawei) |
| R1-2210792 | TR 38.864 v0.3.0 for study on network energy savings for NR | Huawei |
| R1-2210793 | Post-meeting comment collection for draftTR 38.864 v0.3.0 | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208381 | BS Sleep States | FUTUREWEI |
| R1-2208424 | Discussion on performance evaluation for network energy saving | Huawei, HiSilicon |
| R1-2208518 | NW energy savings performance evaluation | Nokia, Nokia Shanghai Bell |
| R1-2208561 | Discussion on performance evaluation of network energy savings | Spreadtrum Communications |
| R1-2208654 | Discussion on NW energy savings performance evaluation | vivo |
| R1-2208776 | Discussion on network energy saving performance evaluation methods | China Telecom |
| R1-2208832 | Discussion on NW energy savings performance evaluation | OPPO |
| R1-2208987 | Evaluation Methodology and Power Model for Network Energy Saving | CATT |
| R1-2209022 | Discussion on NW energy savings performance evaluation | Fujitsu |
| R1-2209063 | Discussion on Network energy saving performance evaluations | Intel Corporation |
| R1-2209195 | Discussion on NW energy saving performance evaluation | ZTE, Sanechips |
| R1-2209348 | Discussion on network energy saving performance evaluation | CMCC |
| R1-2209452 | Discussion on performance evaluation for network energy savings | LG Electronics |
| R1-2209500 | Network Energy Savings Performance Evaluation | MediaTek Inc. |
| R1-2209617 | Discussion on network energy savings performance | Rakuten Symphony |
| R1-2209653 | Performance evaluation for network energy saving | InterDigital, Inc. |
| R1-2209742 | NW energy savings performance evaluation | Samsung |
| R1-2209858 | Network energy consumption modeling and evaluation | Ericsson |
| R1-2209913 | Discussion on NW energy savings performance evaluation | NTT DOCOMO, INC. |
| R1-2209996 | NW energy savings performance evaluation | Qualcomm Incorporated |
| R1-2210021 | Performance evaluation for network energy saving | Lenovo |
| R1-2210239 | Network Energy Savings Performance Evaluation | MediaTek Inc. |
| R1-2210257 | Network Energy Savings Performance Evaluation | MediaTek Inc. |
| R1-2210301 | FL summary#1 for R18 NW_ES | Moderator (Huawei) |
| R1-2210302 | FL summary#2 for R18 NW_ES | Moderator (Huawei) |
| R1-2210303 | FL summary#3 for R18 NW_ES | Moderator (Huawei) |
| R1-2210592 | FL summary#4 for R18 NW_ES | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208382 | Potential enhancements for network energy saving | FUTUREWEI |
| R1-2208425 | Discussion on network energy saving techniques | Huawei, HiSilicon |
| R1-2208519 | Network energy saving techniques | Nokia, Nokia Shanghai Bell |
| R1-2208562 | Discussion on network energy saving techniques | Spreadtrum Communications |
| R1-2208655 | Discussion on NW energy saving technique | vivo |
| R1-2208777 | Discussion on potential network energy saving techniques | China Telecom |
| R1-2208833 | Discussion on network energy saving techniques | OPPO |
| R1-2208988 | Network Energy Saving techniques in time, frequency, and spatial domain | CATT |
| R1-2209023 | Discussion on network energy saving techniques | Fujitsu |
| R1-2209064 | Discussion on Network Energy Saving Techniques | Intel Corporation |
| R1-2209127 | Network energy saving techniques | Lenovo |
| R1-2209196 | Discussion on NW energy saving techniques | ZTE, Sanechips |
| R1-2209296 | Discussions on techniques for network energy saving | xiaomi |
| R1-2209349 | Discussion on network energy saving techniques | CMCC |
| R1-2209425 | Discussion on network energy saving techniques | NEC |
| R1-2209453 | Discussion on physical layer techniques for network energy savings | LG Electronics |
| R1-2209501 | On network energy savings techniques | MediaTek Inc. |
| R1-2209592 | Discussion on network energy saving techniques | Apple |
| R1-2209612 | On Network Energy Saving Techniques | Fraunhofer IIS, Fraunhofer HHI |
| R1-2209618 | Discussion on network energy saving techniques | Rakuten Symphony |
| R1-2209633 | Discussion on potential network energy saving techniques | Panasonic |
| R1-2209655 | Potential techniques for network energy saving | InterDigital, Inc. |
| R1-2209743 | Network energy saving techniques | Samsung |
| R1-2209859 | Network energy savings techniques | Ericsson |
| R1-2209914 | Discussion on NW energy saving techniques | NTT DOCOMO, INC. |
| R1-2209997 | Network energy saving techniques | Qualcomm Incorporated |
| R1-2210031 | Discussion on potential L1 network energy saving techniques for NR | ITRI |
| R1-2210113 | Discussion on Network energy saving techniques | CEWiT |
| R1-2210348 | Discussion Summary #1 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2210349 | Discussion Summary #2 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2210619 | Discussion Summary #3 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2210620 | Discussion Summary #4 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2210744 | Discussion Summary #5 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208690 | Work plan for NR network-controlled repeaters | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2208422 | Side control information and behaviors for network-controlled repeaters | Huawei, HiSilicon |
| R1-2208563 | Discussion on side control information and NCR behavior | Spreadtrum Communications |
| R1-2208656 | Discussion on side control information and NCR behavior | vivo |
| R1-2208684 | Discussions on side control information for NR network-controlled repeaters | InterDigital, Inc. |
| R1-2208691 | Discussion on side control information for NCR | ZTE |
| R1-2208778 | Discussion on side control information and NCR behavior | China Telecom |
| R1-2208989 | Discussion on side control information and NCR behavior | CATT |
| R1-2209018 | Discussion on side control information and NCR behavior | Fujitsu |
| R1-2209065 | Discussion on Side control information and NCR behaviour | Intel Corporation |
| R1-2209086 | Discussion on side control information and NCR behavior | Nokia, Nokia Shanghai Bell |
| R1-2209089 | Signalling support for NR network-controlled repeaters | AT&T, FirstNet |
| R1-2209110 | Considerations on side control information and NCR behaviour | Sony |
| R1-2209154 | Discussion on side control information to enable NR network-controlled repeaters | NEC |
| R1-2209238 | Discussion on side control information and NCR behavior | CAICT |
| R1-2209297 | Discussion on side control information and NCR behavior | xiaomi |
| R1-2209350 | Discussion on side control information and NCR behavior | CMCC |
| R1-2209378 | Discussion on side control information and NCR behavior | Panasonic |
| R1-2209408 | Discussion on side control information for network-controlled repeater | ETRI |
| R1-2209511 | Side control information and NCR behavior | MediaTek Inc. |
| R1-2209593 | On side control information and NCR behavior | Apple |
| R1-2209664 | Side control information and configuration for NCR behavior | Sharp |
| R1-2209744 | Discussion on side control information and NCR behavior | Samsung |
| R1-2209763 | Discussion on UL-DL timing alignment in NCR-Fwd | Rakuten Mobile, Inc |
| R1-2209811 | Discussion on side control information and NCR behavior | LG Electronics |
| R1-2209915 | Discussion on Side control information and NCR behavior | NTT DOCOMO, INC. |
| R1-2209998 | On side control information and NCR behavior | Qualcomm Incorporated |
| R1-2210022 | Discussion on side control information and NCR behaviour | Lenovo |
| R1-2210068 | Discussion on side control information and NCR behavior | KDDI Corporation |
| R1-2210114 | Discussion on signaling side control information and NCR behavior | CEWiT, IITK |
| R1-2210231 | Side-control information and behavior in NCR | Ericsson |
| R1-2210343 | Summary#2 of discussion on side control information | Moderator (ZTE) |
| R1-2210364 | Summary#1 of discussion on side control information | Moderator (ZTE) |
| R1-2210483 | Summary#3 of discussion on side control information | Moderator (ZTE) |
| R1-2210484 | Summary#4 of discussion on side control information | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208423 | Configuration for side control information signalling of network-controlled repeaters | Huawei, HiSilicon |
| R1-2208657 | Discussion on other aspects of NCR | vivo |
| R1-2208685 | L1/L2 signaling for side control information of network-controlled repeaters | InterDigital, Inc. |
| R1-2208692 | Discussion on other aspects for NCR | ZTE |
| R1-2208990 | Discussion on control plane signalling and procedures for NR network-controlled repeaters | CATT |
| R1-2209019 | Discussion on control plane signaling and procedures relavant to RAN1 | Fujitsu |
| R1-2209066 | Discussions on L1/L2 signaling and configuration for side control information | Intel Corporation |
| R1-2209087 | Discussion on\tother aspects including control plane signalling and procedures relevant to RAN1 | Nokia, Nokia Shanghai Bell |
| R1-2209155 | Discussion on other aspects for network-controlled repeaters | NEC |
| R1-2209298 | Discussion on other aspects of NCR | xiaomi |
| R1-2209351 | Discussion on other aspects including control plane signalling and procedures relevant to RAN1 | CMCC |
| R1-2209409 | Discussion on NCR signaling and procedures | ETRI |
| R1-2209594 | On control plane signaling and procedures for NCR | Apple |
| R1-2209745 | On signaling and procedures for network-controlled repeaters | Samsung |
| R1-2209812 | Discussion on other aspects for NCR | LG Electronics |
| R1-2209916 | Other aspects including control plane signalling and procedures relevant to RAN1 | NTT DOCOMO, INC. |
| R1-2209999 | On other NCR aspects | Qualcomm Incorporated |
| R1-2210036 | Discussion on signalling of side control information for network-controlled repeaters | Lenovo |
| R1-2210232 | Signaling, procedures and other aspects in NCR | Ericsson |
| R1-2210282 | Summary#1 on other aspects | Moderator (Fujitsu) |
| R1-2210463 | Summary#2 on other aspects | Moderator (Fujitsu) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208426 | Discussion on multi-cell scheduling with a single DCI | Huawei, HiSilicon |
| R1-2208486 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | ZTE |
| R1-2208564 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Spreadtrum Communications |
| R1-2208658 | Discussion on multi-cell scheduling | vivo |
| R1-2208779 | Discussion on multi-cell scheduling with a single DCI | China Telecom |
| R1-2208860 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | OPPO |
| R1-2208991 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CATT |
| R1-2208997 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | Langbo |
| R1-2209020 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | Fujitsu |
| R1-2209067 | Discussions on multi-cell scheduling with a single DCI | Intel Corporation |
| R1-2209239 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | CAICT |
| R1-2209299 | Discussion on the design of multi-cell scheduling with a single DCI | xiaomi |
| R1-2209305 | On multi-cell scheduling via a single DCI | Lenovo |
| R1-2209352 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CMCC |
| R1-2209416 | Discussion on Multicarrier scheduling with a single DCI | FGI |
| R1-2209426 | Discussion on Multi-cell PXSCH scheduling with a single DCI | NEC |
| R1-2209454 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | LG Electronics |
| R1-2209516 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | MediaTek Inc. |
| R1-2209595 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Apple |
| R1-2209746 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Samsung |
| R1-2209860 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Ericsson |
| R1-2209917 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | NTT DOCOMO, INC. |
| R1-2210000 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Qualcomm Incorporated |
| R1-2210032 | Discussion on multi-cell scheduling with a single DCI | ITRI |
| R1-2210034 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Google Inc. |
| R1-2210151 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Nokia, Nokia Shanghai Bell |
| R1-2210350 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2210351 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2210352 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2210662 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208427 | Discussion on multi-carrier UL Tx switching | Huawei, HiSilicon |
| R1-2208487 | Discussion on Multi-carrier UL Tx switching scheme | ZTE |
| R1-2208565 | Discussion on multi-carrier UL Tx switching scheme | Spreadtrum Communications |
| R1-2208659 | Discussion on UL TX switching | vivo |
| R1-2208780 | Discussion on UL Tx switching across up to 3 or 4 bands | China Telecom |
| R1-2208861 | Discussion on multi-carrier UL Tx switching scheme | OPPO |
| R1-2208992 | Discussion on multi-carrier UL Tx switching scheme | CATT |
| R1-2209068 | Discussions on multi-carrier UL Tx switching scheme | Intel Corporation |
| R1-2209111 | Considerations on Multi-carrier UL Tx switching scheme | Sony |
| R1-2209300 | Discussion on multi-carrier UL Tx switching scheme | xiaomi |
| R1-2209353 | Discussion on multi-carrier UL Tx switching scheme | CMCC |
| R1-2209455 | Discussion on Multi-carrier UL Tx switching scheme | LG Electronics |
| R1-2209596 | On multi-carrier UL Tx switching | Apple |
| R1-2209747 | On multi-carrier UL Tx switching | Samsung |
| R1-2209772 | On multi-carrier UL Tx switching scheme | MediaTek Inc. |
| R1-2209861 | Multi-carrier UL Tx switching | Ericsson |
| R1-2209918 | Discussion on Multi-carrier UL Tx switching scheme | NTT DOCOMO, INC. |
| R1-2210001 | Discussion on Rel-18 UL Tx switching | Qualcomm Incorporated |
| R1-2210035 | Discussion on multi-carrier UL Tx switching scheme | Google Inc. |
| R1-2210192 | On Multi-Carrier UL Tx Switching | Nokia, Nokia Shanghai Bell |
| R1-2210280 | Summary#1 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2210455 | Summary#2 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2210548 | Summary#3 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2210723 | Summary#4 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2210724 | LS on UE capability and gNB configuration for UL Tx switching across 3 or 4 bands in Rel-18 | RAN1, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2208401 | Discussion on power saving enhancements for XR | Ericsson |
| R1-2208420 | Discussion on XR-specific power saving techniques | Huawei, HiSilicon |
| R1-2208566 | Discussion on XR specific power saving techniques | Spreadtrum Communications |
| R1-2208660 | Discussion on XR specific power saving enhancements | vivo |
| R1-2208781 | Discussion on XR specific power saving enhancement for NR | China Telecom |
| R1-2208862 | Discussion on XR specific power saving techniques | OPPO |
| R1-2208952 | UE Power saving techniques for XR | CATT |
| R1-2208999 | XR specific power saving techniques | TCL Communication Ltd. |
| R1-2209069 | Discussion on XR specific power saving techniques | Intel Corporation |
| R1-2209112 | Considerations on XR specific power saving techniques | Sony |
| R1-2209128 | XR-specific power saving techniques | Lenovo |
| R1-2209197 | Evaluation on XR specific power saving techniques | ZTE, Sanechips |
| R1-2209263 | Discussions on techniques for XR Power Saving | xiaomi |
| R1-2209354 | Discussion on XR-specific power saving techniques | CMCC |
| R1-2209387 | Discussion on XR specific power saving techniques | Panasonic |
| R1-2209410 | Discussion on power saving techniques for XR | ETRI |
| R1-2209427 | Discussion on XR specific power saving techniques | NEC |
| R1-2209456 | Discussion on XR-specific power saving techniques | LG Electronics |
| R1-2209517 | On XR specific power saving techniques | MediaTek Inc. |
| R1-2209535 | XR-specific power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2209597 | XR specific power saving techniques | Apple |
| R1-2209619 | Power saving techniques for XR | Rakuten Symphony |
| R1-2209636 | On XR-specific power saving techniques | Google Inc. |
| R1-2209657 | Discussion on XR specific power saving techniques | InterDigital, Inc. |
| R1-2209748 | Considerations on Power Savings for XR | Samsung |
| R1-2209919 | Discussion on XR specific power saving techniques | NTT DOCOMO, INC. |
| R1-2210002 | Power saving techniques for XR | Qualcomm Incorporated |
| R1-2210084 | Further Discussion on XR power saving | III |
| R1-2210152 | XR-specific power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210273 | Discussion on XR specific power saving enhancements | vivo |
| R1-2210337 | Moderator Summary#1 on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2210338 | Moderator Summary#2 on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2210339 | Moderator Summary#3 on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2210340 | Final Moderator Summary on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208377 | XR Capacity Evaluation and Enhancements | FUTUREWEI |
| R1-2208402 | Discussion on capacity enhancements for XR | Ericsson |
| R1-2208421 | Discussion on XR-specific capacity enhancements techniques | Huawei, HiSilicon |
| R1-2208661 | Discussion on XR specific capacity enhancements | vivo |
| R1-2208782 | Discussion on XR specific capacity enhancement for NR | China Telecom |
| R1-2208863 | Discussion on XR specific capacity enhancements techniques | OPPO |
| R1-2208953 | NR enhancement for XR capacity improvement | CATT |
| R1-2209000 | XR-specific capacity enhancements techniques | TCL Communication Ltd. |
| R1-2209070 | Discussion on XR specific capacity enhancement techniques | Intel Corporation |
| R1-2209113 | Considerations on XR-specific capacity enhancements | Sony |
| R1-2209129 | XR-specific Capacity Enhancement Techniques | Lenovo |
| R1-2209156 | Discussion on XR-specific capacity enhancements | NEC |
| R1-2209198 | XR specific capacity enhancements | ZTE, Sanechips |
| R1-2209355 | Discussion on XR-specific capacity enhancements techniques | CMCC |
| R1-2209388 | Discussion on XR capacity enhancement techniques | Panasonic |
| R1-2209457 | Discussion on XR-specific capacity enhancement techniques | LG Electronics |
| R1-2209518 | On XR specific capacity improvement enhancements | MediaTek Inc. |
| R1-2209536 | XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
| R1-2209598 | XR-specific capacity enhancements techniques | Apple |
| R1-2209620 | Discussion on XR-specific capacity improvements | Rakuten Symphony |
| R1-2209642 | On XR-specific capacity enhancements techniques | Google Inc. |
| R1-2209658 | Discussion on XR-specific capacity enhancements techniques | InterDigital, Inc. |
| R1-2209749 | Considerations on Capacity Improvements for XR | Samsung |
| R1-2209920 | Discussion on XR specific capacity improvement enhancements | NTT DOCOMO, INC. |
| R1-2210003 | Capacity enhancement techniques for XR | Qualcomm Incorporated |
| R1-2210153 | XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210410 | Moderator Summary#1 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2210411 | Moderator Summary#2 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2210412 | Moderator Summary#3 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2210413 | Moderator Summary#4 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210186 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
| R1-2210694 | Session notes for 9.11 (NTN (Non-Terrestrial Networks) enhancements) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208388 | Discussion on NR NTN coverage enhancement | THALES |
| R1-2208395 | Coverage enhancement for NR NTN | MediaTek Inc. |
| R1-2208435 | Discussion on coverage enhancement for NR NTN | Huawei, HiSilicon |
| R1-2208567 | Discussion on coverage enhancements for NTN | Spreadtrum Communications |
| R1-2208662 | Discussions on coverage enhancement for NR NTN | vivo |
| R1-2208693 | Discussion on coverage enhancement for NTN | ZTE |
| R1-2208834 | Discussion on coverage enhancement for NR NTN | OPPO |
| R1-2208954 | Discussion on UL coverage enhancement for NR NTN | CATT |
| R1-2209071 | On coverage enhancement for NR NTN | Intel Corporation |
| R1-2209114 | On coverage enhancement for NR NTN | Sony |
| R1-2209264 | Discussion on coverage enhancement for NR-NTN | xiaomi |
| R1-2209356 | Discussion on coverage enhancement for NR NTN | CMCC |
| R1-2209411 | Discussion on coverage enhancement for NR NTN | ETRI |
| R1-2209422 | Discussion on coverage enhancements aspects for NR NTN | NEC |
| R1-2209599 | On Coverage Enhancement for NR NTN | Apple |
| R1-2209656 | On coverage enhancements for NR NTN | Ericsson |
| R1-2209750 | On coverage enhancement for NR NTN | Samsung |
| R1-2209768 | Discussion on coverage enhancement for NR NTN | Baicells |
| R1-2209796 | Discussion on coverage enhancement for NR-NTN | Panasonic |
| R1-2209802 | Discussion on coverage enhancement for NR NTN | LG Electronics |
| R1-2209921 | Discussion on coverage enhancement for NR NTN | NTT DOCOMO, INC. |
| R1-2210004 | Coverage enhancements for NR NTN | Qualcomm Incorporated |
| R1-2210023 | Discussion on coverage enhancement for NR NTN | Lenovo |
| R1-2210049 | Considerations on coverage enhancements for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2210344 | Summary #1 on 9.11.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2210345 | Summary #2 on 9.11.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2210346 | Summary #3 on 9.11.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208389 | Discussion on network verified UE location in NR NTN | THALES |
| R1-2208390 | FL Summary #1: Network verified UE location for NR NTN | THALES |
| R1-2208391 | FL Summary #2: Network verified UE location for NR NTN | THALES |
| R1-2208392 | FL Summary #3: Network verified UE location for NR NTN | THALES |
| R1-2208393 | FL Summary #4: Network verified UE location for NR NTN | THALES |
| R1-2208394 | FL Summary #5: Network verified UE location for NR NTN | THALES |
| R1-2208396 | Network verified UE location for NR NTN | MediaTek Inc. |
| R1-2208436 | Discussion on network-verified UE location for NR NTN | Huawei, HiSilicon |
| R1-2208663 | Discussions on network verified UE location for NR NTN | vivo |
| R1-2208694 | Discussion on network verified UE location for NR NTN | ZTE |
| R1-2208835 | Discussion on network verified UE location for NR NTN | OPPO |
| R1-2208955 | Evaluations on network verified UE location for NR NTN | CATT |
| R1-2209072 | On network verified UE location for NR NTN | Intel Corporation |
| R1-2209115 | Network verified UE location for NR NTN | Sony |
| R1-2209265 | Discussion on the network verified location | xiaomi |
| R1-2209398 | NTN NW verified UE location | Lenovo |
| R1-2209600 | Discussion on Network Verified UE Location | Apple |
| R1-2209643 | UE location determination during initial access in NTN | InterDigital, Inc. |
| R1-2209649 | On network verified UE location in NR NTN | Ericsson Limited |
| R1-2209751 | Network verified UE location for NR NTN | Samsung |
| R1-2209922 | Discussion on Network verified UE location for NR NTN | NTT DOCOMO, INC. |
| R1-2210005 | Network verified UE location for NR NTN | Qualcomm Incorporated |
| R1-2210050 | Further discussion on Network Verified UE Positioning | Nokia, Nokia Shanghai Bell |
| R1-2210069 | Discussion on network verified UE location for NTN | PANASONIC |
| R1-2210195 | Discussion on network verified UE location for NR NTN | LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2208397 | Disabling of HARQ for IoT NTN | MediaTek Inc. |
| R1-2208437 | Discussion on disabling of HARQ feedback for IoT NTN | Huawei, HiSilicon |
| R1-2208568 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
| R1-2208695 | Discussion on disabling of HARQ feedback for IoT-NTN | ZTE |
| R1-2208836 | Discussion on disabling of HARQ feedback for IoT NTN | OPPO |
| R1-2208956 | Discussion on disabling of HARQ feedback for IoT NTN | CATT |
| R1-2209157 | Disabling of HARQ feedback for IoT NTN | NEC |
| R1-2209218 | Disabling of HARQ feedback for IoT NTN | Nordic Semiconductor ASA |
| R1-2209245 | Disabling of HARQ feedback for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2209266 | Discussion on the HARQ operation for IoT NTN | xiaomi |
| R1-2209357 | Discussion on disabling of HARQ feedback for IoT NTN | CMCC |
| R1-2209601 | Discussion on HARQ Feedback Disabling for IoT NTN | Apple |
| R1-2209644 | Disabling of HARQ feedback in IoT-NTN | InterDigital, Inc. |
| R1-2209651 | On disabling HARQ feedback for IOT-NTN | Mavenir |
| R1-2209752 | Disabling of HARQ feedback for IoT NTN | Samsung |
| R1-2209931 | Discussions on disabling of HARQ feedback for IoT NTN | Sharp |
| R1-2210006 | Disabling HARQ Feedback for IoT-NTN | Qualcomm Incorporated |
| R1-2210024 | Disabling of HARQ feedback for IoT NTN | Lenovo |
| R1-2210071 | On disabling HARQ feedback for IoT NTN | Ericsson |
| R1-2210329 | FLS#1 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| R1-2210330 | FLS#2 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208398 | Improved GNSS operations for IoT NTN | MediaTek Inc. |
| R1-2208438 | Discussion on improved GNSS operations for IoT NTN | Huawei, HiSilicon |
| R1-2208569 | Discussion on improved GNSS operations for IoT NTN | Spreadtrum Communications |
| R1-2208696 | Discussion on improved GNSS operation for IoT-NTN | ZTE |
| R1-2208837 | Discussion on improved GNSS operations for IoT NTN | OPPO |
| R1-2208957 | Improved GNSS operations for IoT NTN | CATT |
| R1-2209219 | Improved GNSS operations for IoT NTN | Nordic Semiconductor ASA |
| R1-2209246 | Enhancements for long connections in NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2209267 | Discussion on the improved GNSS operation for IoT NTN | xiaomi |
| R1-2209358 | Discussion on improved GNSS operations for IoT NTN | CMCC |
| R1-2209602 | On Improved GNSS Operations for IoT NTN | Apple |
| R1-2209645 | GNSS acquisition and reporting in IoT NTN | InterDigital, Inc. |
| R1-2209648 | On improved GNSS operation in IoT NTN | Ericsson Limited |
| R1-2209753 | Improved GNSS operations for IoT NTN | Samsung |
| R1-2210007 | Improved GNSS Operations for IoT-NTN | Qualcomm Incorporated |
| R1-2210025 | Improved GNSS operations for IoT NTN | Lenovo |
| R1-2210260 | Feature lead summary#1 of AI 9.11.4 on improved GNSS operations | Moderator (MediaTek Inc.) |
| R1-2210261 | Feature lead summary#2 of AI 9.11.4 on improved GNSS operations | Moderator (MediaTek Inc.) |
| R1-2210564 | Feature lead summary#3 of AI 9.11.4 on improved GNSS operations | Moderator (MediaTek Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2210265 | RAN1 Work Plan for Rel-18 Further NR Mobility Enhancements WI | MediaTek Inc., Apple |
| R1-2210695 | Session notes for 9.12 (Further NR mobility enhancements) | Ad-Hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208406 | L1 enhancements for inter-cell beam management | Huawei, HiSilicon |
| R1-2208500 | Discussion on L1 enhancements for L1/L2-based inter-cell mobility | Nokia, Nokia Shanghai Bell |
| R1-2208509 | L1 enhancements for inter-cell beam management | ZTE |
| R1-2208570 | Discussion on L1 enhancements for inter-cell beam management | Spreadtrum Communications |
| R1-2208664 | Discussion on L1 enhancements for L1/L2 mobility | vivo |
| R1-2208679 | L1 enhancements to inter-cell beam management | Ericsson |
| R1-2208747 | L1 enhancements for inter-cell beam management | Lenovo |
| R1-2208805 | Discussions on Inter-cell beam management enhancement | OPPO |
| R1-2208884 | On Intercell beam management enhancement for NR mobility enhancement | |
| R1-2208905 | Enhancements on inter-cell beam management for mobility | LG Electronics |
| R1-2208958 | On L1 enhancements for inter-cell beam management | CATT |
| R1-2209024 | Views on L1 enhancements for inter-cell beam management | Fujitsu |
| R1-2209073 | L1 Enhancements for Inter-cell Beam Management | Intel Corporation |
| R1-2209203 | L1 enhancements for inter-cell beam management | InterDigital, Inc. |
| R1-2209268 | Discussion on L1 enhancements and Dynamic switch mechanism | xiaomi |
| R1-2209359 | Discussion on L1 enhancements for inter-cell beam management | CMCC |
| R1-2209428 | Discussion on L1 enhancements for inter-cell beam management | NEC |
| R1-2209498 | L1 enhancements for inter-cell beam management | MediaTek Inc. |
| R1-2209603 | On L1 enhancements for inter-cell mobility | Apple |
| R1-2209754 | On L1 enhancements for inter-cell beam management | Samsung |
| R1-2209923 | Discussion on L1 enhancements for inter-cell mobility | NTT DOCOMO, INC. |
| R1-2210008 | L1 Enhancements for Inter-Cell Beam Management | Qualcomm Incorporated |
| R1-2210414 | FL summary 1 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu) |
| R1-2210612 | FL summary 2 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu) |
| R1-2210675 | FL summary 3 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu) |
| R1-2210725 | FL final summary on L1 enhancements for inter-cell beam management | Moderator (Fujitsu) |
| R1-2210726 | DRAFT LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | Fujitsu, CATT |
| R1-2210727 | LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | RAN1, Fujitsu, CATT |
| R1-2210791 | DRAFT LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | Fujitsu, CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2208383 | Latency Reduction and Target TA Determination for L1/L2 Mobility | FUTUREWEI |
| R1-2208407 | Timing advance management to reduce latency | Huawei, HiSilicon |
| R1-2208501 | Discussion on timing advance management for L1/L2-based inter-cell mobility | Nokia, Nokia Shanghai Bell |
| R1-2208510 | Enhancements on TA management to reduce latency | ZTE |
| R1-2208571 | Discussion on timing advance management to reduce latency | Spreadtrum Communications |
| R1-2208665 | Discussion on TA management for L1/L2 moblity | vivo |
| R1-2208748 | Timing advancement management for L1L2 mobility | Lenovo |
| R1-2208806 | Discussions on Timing Advance Management | OPPO |
| R1-2208885 | On TA management for NR mobility enhancement | |
| R1-2208959 | On timing advance management to reduce latency | CATT |
| R1-2209074 | On Timing Advance Management | Intel Corporation |
| R1-2209204 | Timing advance management to reduce latency | InterDigital, Inc. |
| R1-2209269 | Discussion on Timing advance management | xiaomi |
| R1-2209360 | Discussion on timing advance management to reduce latency | CMCC |
| R1-2209499 | UL Timing management to reduce handover latency | MediaTek Inc. |
| R1-2209542 | Timing advance management to reduce latency | Ericsson |
| R1-2209604 | Timing advance management to reduce mobility latency | Apple |
| R1-2209755 | Non-serving cell TA management for NR mobility enhancement | Samsung |
| R1-2209924 | Timing advance enhancement for inter-cell mobility | NTT DOCOMO, INC. |
| R1-2210009 | TA management to reduce latency for L1/L2 based mobility | Qualcomm Incorporated |
| R1-2210200 | Timing advance alignment with low latency | Rakuten Symphony |
| R1-2210390 | Moderator summary on timing advance management: Round 1 | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208666 | TR 38.869 skeleton for study on low-power wake up signal and receiver for NR | vivo |
| R1-2208667 | Work plan for low-power wake up signal and receiver for NR | vivo |
| R1-2210430 | TR 38.869 skeleton for study on low-power wake up signal and receiver for NR | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2208378 | Evaluation of Low Power WUS and initial performance results | FUTUREWEI |
| R1-2208417 | Evaluation methodology for LP-WUS | Huawei, HiSilicon |
| R1-2208572 | Discussion on evaluation on low power WUS | Spreadtrum Communications |
| R1-2208668 | Evaluation methodologies for R18 LP-WUS/WUR | vivo |
| R1-2208686 | Discussion on evaluation on LP-WUS | InterDigital, Inc. |
| R1-2208698 | Low power WUS Evaluation Methodology | Nokia, Nokia Shanghai Bell |
| R1-2208843 | Evaluation discussion on lower power wake-up signal | OPPO |
| R1-2208960 | Deployment scenarios and evaluation methodologies for low-power WUS | CATT |
| R1-2209075 | Discussion on evaluations on LP WUS | Intel Corporation |
| R1-2209199 | Evaluation on LP-WUS | ZTE, Sanechips |
| R1-2209270 | Evaluation on low power WUS | xiaomi |
| R1-2209361 | Discussion on evaluation methodology and applicable scenarios for low power WUR | CMCC |
| R1-2209502 | Evaluation on low power WUS | MediaTek Inc. |
| R1-2209605 | On performance evaluation for low power wake-up signal | Apple |
| R1-2209621 | Discussion on low power WUS evaluation | Rakuten Symphony |
| R1-2209665 | Discussion on the evaluation methodology for low power WUS | Lenovo |
| R1-2209685 | Discussion on evaluation for low power WUS | Sharp |
| R1-2209756 | Evaluation on LP-WUS/WUR | Samsung |
| R1-2209766 | Initial view on evaluation of low-power WUS | Rakuten Mobile, Inc |
| R1-2209862 | Evaluation framework for low power WUS | Ericsson |
| R1-2210010 | Evaluation methodology for LP-WUS | Qualcomm Incorporated |
| R1-2210051 | Discussion on Evaluation on Low power WUS | EURECOM |
| R1-2210169 | Discussion on evaluation methodology for low power WUS | NTT DOCOMO, INC. |
| R1-2210197 | On LP-WUS evaluation | Nordic Semiconductor ASA |
| R1-2210222 | Evaluation for low power WUS | Sony |
| R1-2210437 | FL summary#1 of evaluation on low power WUS | Moderator (vivo) |
| R1-2210512 | FL summary#2 of evaluation on low power WUS | Moderator (vivo) |
| R1-2210668 | FL summary#3 of evaluation on low power WUS | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208379 | Low Power WUS Receiver Architectures Considerations and Modeling | FUTUREWEI |
| R1-2208418 | On architectures of LP-WUS receiver | Huawei, HiSilicon |
| R1-2208481 | Low Power WUS receiver architecture | TCL Communication Ltd. |
| R1-2208573 | Discussion on low power WUS receiver architectures | Spreadtrum Communications |
| R1-2208669 | Discussion on low power wake-up receiver architecture | vivo |
| R1-2208687 | Discussion on LP-WUS receiver architectures | InterDigital, Inc. |
| R1-2208699 | Low Power WUS receiver architectures | Nokia, Nokia Shanghai Bell |
| R1-2208844 | Discussion on low power WUS receiver | OPPO |
| R1-2208961 | Design consideration of Low-Power WUS receiver | CATT |
| R1-2209076 | Discussion on LP-WUS receiver architecture | Intel Corporation |
| R1-2209200 | LP-WUS receiver architectures | ZTE, Sanechips |
| R1-2209503 | Low power WUS receiver architectures | MediaTek Inc. |
| R1-2209606 | On low power wake-up receiver architectures | Apple |
| R1-2209622 | Receiver architectures for low power WUS | Rakuten Symphony |
| R1-2209634 | Discussion on Low power WUS receiver architectures | Panasonic |
| R1-2209666 | Discussion on the receiver architecture for low power WUS | Lenovo |
| R1-2209757 | Receiver architecture for LP-WUS | Samsung |
| R1-2209863 | Low power WUS receiver architectures | Ericsson |
| R1-2210011 | Receiver architecture for LP-WUS | Qualcomm Incorporated |
| R1-2210052 | Discussion on Low power WUS receiver architectures | EURECOM |
| R1-2210198 | On LP-WUS architecture | Nordic Semiconductor ASA |
| R1-2210223 | On LP-WUS receiver architectures | Sony |
| R1-2210479 | Summary #1 on [110bis-e-R18-LP_WUS-02] LP WUR architecture | Moderator (Apple) |
| R1-2210480 | Summary #2 on [110bis-e-R18-LP_WUS-02] LP WUR architecture | Moderator (Apple) |
| R1-2210666 | Summary #3 on [110bis-e-R18-LP_WUS-02] LP WUR architecture | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208380 | Low Power WUS Design | FUTUREWEI |
| R1-2208419 | Signal design and procedure for LP-WUS | Huawei, HiSilicon |
| R1-2208482 | L1 signal design and procedure for low power WUS | TCL Communication Ltd. |
| R1-2208574 | Discussion on L1 signal design and procedure for low power WUS | Spreadtrum Communications |
| R1-2208670 | Discussion on physical signal and procedure for low power WUS | vivo |
| R1-2208688 | Discussion on L1 signal design and procedure for LP-WUS | InterDigital, Inc. |
| R1-2208700 | L1 signal design and procedure for low power WUS | Nokia, Nokia Shanghai Bell |
| R1-2208845 | L1 signal design consideration on lower power wake-up signal | OPPO |
| R1-2208962 | Physical layer signals and procedures for Low-Power WUS | CATT |
| R1-2209077 | Discussions on L1 signal design and procedure for low power WUS | Intel Corporation |
| R1-2209158 | Discussion on L1 signal design and procedure for LP-WUS | NEC |
| R1-2209201 | LP-WUS design and related procedure | ZTE, Sanechips |
| R1-2209271 | Discussions on L1 signal design and procedure for low power WUS | xiaomi |
| R1-2209362 | Discussion on L1 signal design for low power WUS | CMCC |
| R1-2209504 | L1 signal design and procedure for low power WUS | MediaTek Inc. |
| R1-2209607 | On the L1 signal design and procedures for low power wake-up signal | Apple |
| R1-2209635 | Discussion on low power wake up signal design | Panasonic |
| R1-2209667 | Discussion on the L1 signal design and procedure for low power WUS | Lenovo |
| R1-2209686 | L1 signal design and procedure for low power WUS | Sharp |
| R1-2209758 | Signal design and procedure for LP-WUS | Samsung |
| R1-2209864 | L1 signal design and procedure for low power WUS | Ericsson |
| R1-2210012 | L1 signal design and procedures for LP-WUR | Qualcomm Incorporated |
| R1-2210054 | Discussion on L1 signal design and procedure for low power WUS | EURECOM |
| R1-2210171 | Discussion on L1 signal design and procedure for low power WUS | NTT DOCOMO, INC. |
| R1-2210199 | On LP-WUS signal design | Nordic Semiconductor ASA |
| R1-2210224 | LP-WUS L1 signal design and procedures | Sony |
| R1-2210238 | Signal design and procedure for LP-WUS | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2208783 | Work plan for Rel-18 WI on Further NR coverage enhancements | China Telecom |
| R1-2210547 | Work plan for Rel-18 WI on Further NR coverage enhancements | China Telecom |
| R1-2210696 | Session notes for 9.14 (Further NR coverage enhancements) | Ad-Hoc Chair (CMCC) |
| R1-2210782 | Session notes for 9.14 (Further NR coverage enhancements) | Ad-Hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208411 | Discussion on PRACH coverage enhancements | Huawei, HiSilicon |
| R1-2208488 | Discussion on PRACH coverage enhancements | ZTE |
| R1-2208575 | Discussion on PRACH coverage enhancements | Spreadtrum Communications |
| R1-2208671 | Discussions on PRACH coverage enhancements | vivo |
| R1-2208784 | Discussion on PRACH coverage enhancement | China Telecom |
| R1-2208846 | PRACH coverage enhancements | OPPO |
| R1-2208963 | PRACH coverage enhancements | CATT |
| R1-2209001 | PRACH coverage enhancements | TCL Communication Ltd. |
| R1-2209025 | Discussion on PRACH Coverage Enhancement | Fujitsu |
| R1-2209078 | Discussions on PRACH coverage enhancement | Intel Corporation |
| R1-2209116 | PRACH Coverage Enhancement using Multi PRACH Transmissions | Sony |
| R1-2209130 | Discussion on PRACH coverage enhancements | Panasonic |
| R1-2209159 | Discussion on PRACH coverage enhancement | NEC |
| R1-2209223 | PRACH coverage enhancements | Lenovo |
| R1-2209249 | Discussion on solutions for NR PRACH coverage enhancement | Mavenir |
| R1-2209272 | Discussion on PRACH coverage enhancements | xiaomi |
| R1-2209363 | Discussion on PRACH coverage enhancements | CMCC |
| R1-2209412 | PRACH coverage enhancements | ETRI |
| R1-2209415 | Discussion on triggering multiple PRACH transmissions | FGI |
| R1-2209521 | Enhancements for PRACH coverage | MediaTek Inc. |
| R1-2209608 | Discussion on PRACH coverage enhancement | Apple |
| R1-2209661 | Discussion on PRACH repetition | InterDigital, Inc. |
| R1-2209672 | Discussion on PRACH coverage enhancement | Ericsson |
| R1-2209759 | PRACH coverage enhancements | Samsung |
| R1-2209788 | Views on multiple PRACH transmission for coverage enhancement | Sharp |
| R1-2209803 | Discussion on PRACH repeated transmission for NR coverage enhancement | LG Electronics |
| R1-2209925 | Discussion on PRACH coverage enhancements | NTT DOCOMO, INC. |
| R1-2210013 | PRACH Coverage Enhancements | Qualcomm Incorporated |
| R1-2210165 | PRACH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210318 | FL Summary#1 of PRACH coverage enhancements | Moderator (China Telecom) |
| R1-2210553 | FL Summary#2 of PRACH coverage enhancements | Moderator (China Telecom) |
| R1-2210554 | FL Summary#3 of PRACH coverage enhancements | Moderator (China Telecom) |
| R1-2210660 | FL Summary#4 of PRACH coverage enhancements | Moderator (China Telecom) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208412 | Discussion on coverage enhancement in power domain | Huawei, HiSilicon |
| R1-2208489 | Discussion on power domain enhancements | ZTE |
| R1-2208576 | Discussion on power domain enhancements | Spreadtrum Communications |
| R1-2208672 | Discussions on power domain enhancements | vivo |
| R1-2208847 | The study of power domain enhancements | OPPO |
| R1-2208964 | Discussion on power domain enhancements | CATT |
| R1-2209026 | Discussion on power domain enhancements for CA/DC | Fujitsu |
| R1-2209079 | Discussions on power domain enhancement | Intel Corporation |
| R1-2209224 | Power domain enhancements | Lenovo |
| R1-2209364 | Discussion on power domain enhancements | CMCC |
| R1-2209522 | Discussion on power-domain enhancements | MediaTek Inc. |
| R1-2209609 | Discussion on power domain coverage enhancement | Apple |
| R1-2209662 | Uplink power enhancements | InterDigital, Inc. |
| R1-2209673 | Power Domain Enhancement Evaluation Methodology and Schemes | Ericsson |
| R1-2209760 | Power domain enhancements | Samsung |
| R1-2209789 | Power domain enhancements for Rel-18 CovEnh | Sharp |
| R1-2209926 | Discussion on power domain enhancements | NTT DOCOMO, INC. |
| R1-2210014 | Power-domain enhancements | Qualcomm Incorporated |
| R1-2210166 | RAN1 impacts for power domain enhancements | Nokia, Nokia Shanghai Bell |
| R1-2210322 | FL summary of power domain enhancements (AI 9.14.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2210323 | FL summary #2 of power domain enhancements (AI 9.14.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2210324 | FL summary #3 of power domain enhancements (AI 9.14.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2210325 | FL summary #4 of power domain enhancements (AI 9.14.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2210326 | Final FL summary of power domain enhancements (AI 9.14.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2210563 | [Draft] LS on work split principles adopted in RAN1 for power domain enhancements | Moderator (Nokia) |
| R1-2210673 | [Draft] LS on enhancements to realize increasing UE power high limit for CA and DC | Moderator (Nokia) |
| R1-2210674 | LS on work split principles adopted in RAN1 for power domain enhancements | RAN1, Nokia |
| R1-2210739 | LS on enhancements to realize increasing UE power high limit for CA and DC | RAN1, Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2208413 | Discussion on dynamic waveform switching for coverage enhancement | Huawei, HiSilicon |
| R1-2208490 | Discussion on dynamic waveform switching | ZTE |
| R1-2208577 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Spreadtrum Communications |
| R1-2208673 | Discussions on dynamic switching between DFT-S-OFDM and CP-OFDM | vivo |
| R1-2208785 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | China Telecom |
| R1-2208848 | Supporting of dynamic switching between DFT-S-OFDM and CP-OFDM | OPPO |
| R1-2208965 | Dynamic switching between DFT-S-OFDM and CP-OFDM | CATT |
| R1-2209080 | Dynamic switching between DFT-S-OFDM and CP-OFDM waveform | Intel Corporation |
| R1-2209117 | Considerations on dynamic waveform switching for NR UL | Sony |
| R1-2209160 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NEC |
| R1-2209162 | Discussion on dynamic waveform switching | Panasonic |
| R1-2209205 | Dynamic switching between DFT-S-OFDM and CP-OFDM | InterDigital, Inc. |
| R1-2209225 | Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM | Lenovo |
| R1-2209248 | Discussion on solutions for NR dynamic switching between DFT-S-OFDM and CP-OFDM | Mavenir |
| R1-2209273 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | xiaomi |
| R1-2209365 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | CMCC |
| R1-2209413 | Dynamic switching between DFT-S-OFDM and CP-OFDM | ETRI |
| R1-2209433 | Discussion on Dynamic switching between DFT-s-OFDM and CP-OFDM | Fujitsu Limited |
| R1-2209523 | Discussion on dynamic switching between waveforms | MediaTek Inc. |
| R1-2209610 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Apple |
| R1-2209674 | Discussion on Dynamic UL Waveform Switching | Ericsson |
| R1-2209761 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Samsung |
| R1-2209790 | Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh | Sharp |
| R1-2209804 | Discussion on dynamic waveform switching for NR coverage enhancement | LG Electronics |
| R1-2209927 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NTT DOCOMO, INC. |
| R1-2210015 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Qualcomm Incorporated |
| R1-2210115 | Discussion on Dynamic switching between DFT-S-OFDM and CP-OFDM | CEWiT |
| R1-2210167 | Dynamic switching between DFT-s-OFDM and CP-OFDM | Nokia, Nokia Shanghai Bell |
| R1-2210431 | Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
| R1-2210432 | Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
| R1-2210433 | Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
| R1-2210749 | Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2209085 | Work plan for Rel-18 Uncrewed Aerial Vehicles | Rapporteur (Nokia) |
| R1-2210697 | Session notes for 9.15 (NR support for Uncrewed Aerial Vehicles) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208405 | UE capability and RRC signaling for UAV beamforming | Huawei, HiSilicon |
| R1-2208674 | Discussion on UE capability and RRC signaling for UAV beamforming | vivo |
| R1-2208697 | Discussion on UE capability for UAV beamforming | ZTE |
| R1-2208749 | Discussion on UE capability and RRC signaling for UAV beamforming | Lenovo |
| R1-2209274 | Discussion on UE capability and RRC signaling for UAV beamforming | xiaomi |
| R1-2209631 | UE capability and RRC signaling for UAV beamforming | Nokia, Nokia Shanghai Bell |
| R1-2209762 | Discussion on the benefits of UE beamforming capability reporting | Samsung |
| R1-2209928 | Discussion on UE capability and RRC signaling for UAV beamforming | NTT DOCOMO, INC. |
| R1-2210016 | Discussion of UE capability and RRC signaling for UAV beamforming | Qualcomm Incorporated |
| R1-2210092 | On UAV beamforming capabilities | Ericsson |
| R1-2210310 | Summary#1 of discussion on UAV capability and RRC signaling for UAV | Moderator (Nokia) |
| R1-2210311 | Summary#2 of discussion on UAV capability and RRC signaling for UAV | Moderator (Nokia) |
| R1-2210312 | Summary#3 of discussion on UAV capability and RRC signaling for UAV | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208491 | Discussion on remaining issues for Rel-18 DSS | ZTE |
| R1-2208578 | Maintenance for Rel-18 DSS | Spreadtrum Communications |
| R1-2208675 | Remaining issues on Rel-18 NR Dynamic spectrum sharing | vivo |
| R1-2208859 | Discussion on remaining issues in Rel-18 eDSS | OPPO |
| R1-2209275 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | xiaomi |
| R1-2209814 | Remaining issues on NR PDCCH reception in symbols with LTE CRS REs | Huawei, HiSilicon |
| R1-2209929 | Remaining issues on NR PDCCH reception in symbols with LTE CRS REs | NTT DOCOMO, INC. |
| R1-2210017 | Maintenance for Rel-18 DSS | Qualcomm Incorporated |
| R1-2210193 | [eDSS] RRC configuration and UE capability for PDCCH on CRS | Nokia, Nokia Shanghai Bell |
| R1-2210358 | Moderator summary for Rel. 18 NR DSS | Moderator (Intel Corporation) |
| R1-2210748 | Session notes for 9.17 (Others) | Ad-hoc Chair (CMCC) |