| TDoc | Title | Source |
|---|---|---|
| R1-2205700 | Draft Agenda of RAN1#110 meeting | RAN1 Chair |
| R1-2205703 | RAN1#110 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2205704 | RAN1#110 Meeting Management | RAN1 Chair |
| R1-2207719 | RAN1#110 Meeting Management | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2205702 | Highlights from RAN#96 | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2205701 | Report of RAN1#109-e meeting | ETSI MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2205705 | LS on RB set configuration for IAB | RAN3, Huawei |
| R1-2205706 | LS reply on UE capability for 16QAM for NB-IoT | RAN4, Ericsson |
| R1-2205707 | Further reply LS on condition for PRS measurement outside the MG | RAN4, Huawei |
| R1-2205708 | LS on Tx TEG framework | RAN4, CATT |
| R1-2205709 | LS on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE | RAN4, Huawei |
| R1-2205710 | LS on range of power control parameters for eIAB | RAN4, Samsung |
| R1-2205711 | Reply LS on the dropping rule of DL signals/channels for capability 1B and 2 | RAN4, CATT |
| R1-2205712 | LS on timing advance (TADV) report mapping for NR UL E-CID positioning | RAN4, Ericsson |
| R1-2205713 | LS on clarification of RACH prioritisation rules between LTE and NR-U | RAN4, Ericsson |
| R1-2205714 | LS on CCA configurations of neighbour cells | RAN4, Nokia |
| R1-2205715 | Reply LS to RAN1/RAN2 on DMRS bundling | RAN4, MediaTek |
| R1-2205716 | LS on GP positioning between two UL SRS resource sets | RAN4, Nokia |
| R1-2205717 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2205718 | Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN4, Qualcomm |
| R1-2205719 | LS on Incorrect PMI Reporting | RAN4, Apple |
| R1-2205720 | LS on R17 MG enhancement - NCSG | RAN4, Apple |
| R1-2205721 | LS on measurement capability for RedCap | RAN4, CMCC |
| R1-2205722 | Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN4, Ericsson |
| R1-2205723 | LS reply on coordination of R17 gap features | RAN4, MediaTek |
| R1-2205724 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2205725 | LS to RAN2 on UL gap in FR2 RF enhancement | RAN4, Apple |
| R1-2205726 | Reply LS on UE capabilities for MBS | RAN, Qualcomm |
| R1-2205727 | LS on RRC parameters for IUC Scheme 1 and default CBR configuration | RAN2, Huawei |
| R1-2205728 | LS on IUC with non-preferred resource set | RAN2, Apple |
| R1-2205729 | LS on the CQI periodic reporting for Dormant SCell state | RAN2, Samsung |
| R1-2205730 | Reply LS on system information | RAN2, Huawei |
| R1-2205731 | LS on eMIMO features defined in different granularity with prerequisite | RAN2, HiSilicon |
| R1-2205732 | LS on rate matching patterns and CORESET configuration for MBS | RAN2, Huawei |
| R1-2205733 | MBS SPS configuration on Scell | RAN2, OPPO |
| R1-2205734 | Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN2, Ericsson |
| R1-2205735 | LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | RAN2, vivo |
| R1-2205736 | Reply LS on the L1 related agreements for SDT | RAN2, ZTE |
| R1-2205737 | Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN2, Huawei |
| R1-2205761 | On the offset between CD-SSB and NCD-SSB | Huawei, HiSilicon |
| R1-2205802 | Discussion on RAN2 LS on L1 related agreements for SDT | Huawei, HiSilicon |
| R1-2205803 | On RB set configuration for IAB | Huawei, HiSilicon |
| R1-2205804 | Draft reply LS on RB set configuration for IAB | Huawei, HiSilicon |
| R1-2205805 | Draft reply LS on eMIMO features defined in different granularity with prerequisite | Huawei, HiSilicon |
| R1-2205807 | Correction to timing advance [NRTADV] | Huawei, HiSilicon |
| R1-2205845 | Discussion on LS on RRC parameters for IUC Scheme 1 and default CBR configuration | LG Electronics |
| R1-2205846 | Discussion on LS on IUC with non-preferred resource set | LG Electronics |
| R1-2205847 | Discussion on LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | LG Electronics |
| R1-2205925 | Draft reply LS on eMIMO features defined in different granularity with prerequisite | ZTE |
| R1-2205944 | [DRAFT] Reply LS on the CQI periodic reporting for Dormant SCell state | ZTE |
| R1-2205945 | [DRAFT] MBS SPS configuration on Scell | ZTE |
| R1-2205946 | [DRAFT] Reply LS to RAN4 on DMRS bundling | ZTE |
| R1-2205969 | [Draft] Reply LS on BWP operation without bandwidth restriction | ZTE |
| R1-2205971 | Discussion on RAN4 LS on DMRS bundling | Spreadtrum Communications |
| R1-2205972 | Discussion on LS on MBS SPS configuration on Scell | Spreadtrum Communications |
| R1-2206076 | Draft reply LS on clarification of RACH prioritisation rules between LTE and NR-U | ZTE, Sanechips |
| R1-2206077 | Draft reply LS on CCA configurations of neighbour cells | ZTE, Sanechips |
| R1-2206078 | Discussion on CCA configurations of neighbour cells | ZTE, Sanechips |
| R1-2206079 | Discussion on physical layer issues of small data transmission | ZTE, Sanechips |
| R1-2206091 | About LS on RRC parameters for IUC Scheme 1 and default CBR configuration | ZTE, Sanechips |
| R1-2206092 | About LS on IUC with non-preferred resource set | ZTE, Sanechips |
| R1-2206093 | Draft reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | ZTE, Sanechips |
| R1-2206186 | Draft reply LS on eMIMO features defined in different granularity with prerequisite | |
| R1-2206207 | About reply LS on RB set configuration for IAB | ZTE, Sanechips |
| R1-2206216 | Draft reply LS on eMIMO features defined in different granularity with prerequisite | Lenovo |
| R1-2206277 | Discussion on the LS on RRC parameters for IUC Scheme 1 and default CBR configuration | OPPO |
| R1-2206278 | Draft reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | OPPO |
| R1-2206279 | Discussion on the LS on IUC with non-preferred resource set | OPPO |
| R1-2206280 | Draft reply LS on IUC with non-preferred resource set | OPPO |
| R1-2206281 | Discussion on the LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | OPPO |
| R1-2206282 | Draft reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | OPPO |
| R1-2206331 | Discussion on LS on clarification of RACH prioritisation rules between LTE and NR-U | OPPO |
| R1-2206338 | On the incoming RAN2 LS R1-2205728 on IUC and non-preferred resources | FUTUREWEI |
| R1-2206342 | Draft Reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | CATT, GOHIGH |
| R1-2206343 | Draft Reply LS on IUC with non-preferred resource set | CATT, GOHIGH |
| R1-2206344 | Draft Reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | CATT, GOHIGH |
| R1-2206345 | Discussion on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE | CATT |
| R1-2206346 | Draft Reply LS on MBS SPS configuration on SCell | CATT |
| R1-2206347 | Draft reply LS on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE | CATT |
| R1-2206348 | Discussion on timing advance (TADV) report mapping for NR UL E-CID positioning | CATT |
| R1-2206415 | Discussion on LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | NEC |
| R1-2206427 | On FG 6-1a BWP without restriction | Nokia, Nokia Shanghai Bell |
| R1-2206441 | Discussion on reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB | Nokia, Nokia Shanghai Bell |
| R1-2206482 | On the Reply LS on the L1 related agreements for SDT | Ericsson |
| R1-2206483 | On the Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2206526 | Discussion on LS for CCA configurations of neighbour cells | Intel Corporation |
| R1-2206527 | [draft] reply LS on CCA configurations of neighbour cells | Intel Corporation |
| R1-2206528 | Discussion on reply LS for DMRS bundling | Intel Corporation |
| R1-2206529 | Discussion on reply LS for SDT common search space | Intel Corporation |
| R1-2206530 | On FG 6-1a and NCD-SSB for Non-RedCap UEs | Intel Corporation |
| R1-2206608 | [Draft]Reply LS on IUC with non-preferred resource set | Xiaomi |
| R1-2206609 | [Draft]Reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | Xiaomi |
| R1-2206610 | Discussion on LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Xiaomi |
| R1-2206704 | Draft reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | vivo |
| R1-2206705 | Discussion on BWP without restriction | vivo |
| R1-2206706 | Draft reply LS on eMIMO features defined in different granularity with prerequisite | vivo |
| R1-2206707 | Draft reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | vivo |
| R1-2206708 | Draft reply LS on IUC with non-preferred resource set | vivo |
| R1-2206709 | Draft reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | vivo |
| R1-2206710 | Draft Reply LS on MBS SPS configuration on Scell | vivo |
| R1-2206711 | Draft reply LS on CCA configurations of neighbour cells | vivo |
| R1-2206712 | Draft reply LS on clarification of RACH prioritisation rules between LTE and NR-U | vivo |
| R1-2206713 | Draft LS reply on the L1 related agreements for SDT | vivo |
| R1-2206714 | Draft LS reply on DMRS bundling | vivo |
| R1-2206775 | Draft Reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | Samsung |
| R1-2206776 | Draft Reply LS on IUC with non-preferred resource set | Samsung |
| R1-2206777 | Draft Reply LS on the CQI periodic reporting for Dormant SCell state | Samsung |
| R1-2206778 | Draft Reply LS on eMIMO features defined in different granularity with prerequisite | Samsung |
| R1-2206779 | Draft Reply LS on RB set configuration for IAB | Samsung |
| R1-2206780 | Draft Reply LS to RAN4 on DMRS bundling | Samsung |
| R1-2206886 | Discussion on RAN2 LS on MBS SPS configuration on Scell | CMCC |
| R1-2206887 | Discussion on RAN4 LS on DMRS bundling | CMCC |
| R1-2206998 | Discussion on RAN2 LS on BWP operation without bandwidth restriction | MediaTek Inc. |
| R1-2206999 | Draft Reply LS on BWP operation without bandwidth restriction | MediaTek Inc. |
| R1-2207019 | Discussion on RAN4 LS on CCA configurations of neighbour cells | Nokia, Nokia Shanghai Bell |
| R1-2207022 | Discussion on RAN4 LS for CCA configurations of neighbour cells | LG Electronics |
| R1-2207044 | Discussion on LS reply for time offset between CD-SSB and NCD-SSB | ZTE, Sanechips |
| R1-2207157 | [Draft] Reply to LS on Multicarrier Operation and Tx Power with DMRS Bundling | Ericsson |
| R1-2207164 | Discussion on dormant SCell CQI | Qualcomm Incorporated |
| R1-2207165 | Discussion on RAN2 LS on BWP operation without bandwidth restriction | Qualcomm Incorporated, Vodafone |
| R1-2207166 | Reply to RAN2 LS on RRC parameters for IUC Scheme 1 and default CBR configuration | Qualcomm Incorporated |
| R1-2207167 | Reply to RAN2 LS on IUC with non-preferred resource set | Qualcomm Incorporated |
| R1-2207168 | Reply to RAN2 LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Qualcomm Incorporated |
| R1-2207169 | Discussion of Reply to RAN4 LS on DMRS bundling | Qualcomm Incorporated |
| R1-2207302 | Discussion on RAN2 LS on RRC Parameters for IUC Scheme 1 and Default CBR Configuration | Apple |
| R1-2207303 | Draft Reply LS to RAN2 on RRC Parameters for IUC Scheme 1 and Default CBR Configuration | Apple |
| R1-2207304 | Discussion on RAN2 LS on IUC with Non-preferred Resource Set | Apple |
| R1-2207305 | Draft Reply LS to RNA2 on IUC with Non-preferred Resource Set | Apple |
| R1-2207306 | Discussion on RAN4 LS on DMRS bundling | Apple |
| R1-2207374 | On Rel-17 RB set configuration for IAB | Nokia, Nokia Shanghai Bell |
| R1-2207375 | Discussion on RAN4 LS on CCA configurations of neighbour cells | NTT DOCOMO, INC. |
| R1-2207430 | Discussion on LS on BWP operation without bandwidth restriction | NEC |
| R1-2207474 | Discussion on LS from RAN4 on clarification of RACH prioritisation rules between LTE and NR-U | Ericsson |
| R1-2207514 | Discussion on multicast SPS configuration on PCell/SCell | Huawei, HiSilicon, CBN |
| R1-2207515 | On supporting FG 6-1a for non-RedCap UEs | Huawei, HiSilicon |
| R1-2207516 | Discussion on LS on RRC parameters for IUC Scheme 1 and default CBR configuration | Huawei, HiSilicon |
| R1-2207517 | Discussion on LS on IUC with non-preferred resource set | Huawei, HiSilicon |
| R1-2207518 | Discussion on LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Huawei, HiSilicon |
| R1-2207520 | Discussion on the LS on the CCA configurations of neighbour cell | Huawei, HiSilicon |
| R1-2207529 | Discussion on rate matching patterns and CORESET configuration for MBS | Huawei, HiSilicon |
| R1-2207530 | DRAFT reply LS on rate matching patterns and CORESET configuration for MBS | Huawei, HiSilicon |
| R1-2207552 | Discussion on RAN4 Reply LS for DMRS bundling | MediaTek Beijing Inc. |
| R1-2207557 | [Draft] Reply LS on IUC with non-preferred resource set | Ericsson |
| R1-2207558 | Discussion on LS on IUC with non-preferred resource set | Ericsson |
| R1-2207559 | [Draft] Reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Ericsson |
| R1-2207560 | Discussion on LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Ericsson |
| R1-2207561 | [Draft] Reply LS on RRC parameters for IUC Scheme 1 and default CBR configuration | Ericsson |
| R1-2207562 | Discussion on LS on RRC parameters for IUC scheme 1 and default CBR configuration | Ericsson |
| R1-2207580 | Discussion on LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Xiaomi |
| R1-2207585 | Multicarrier Operation and Tx Power with DMRS Bundling | Ericsson |
| R1-2207614 | Draft Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2207649 | Draft Reply LS to RAN1/RAN2 on DMRS bundling | Huawei, HiSilicon |
| R1-2207650 | Discussion on DMRS bundling | Huawei, HiSilicon |
| R1-2207651 | Discussion on the RAN4 LS on the RACH prioritisation rules between LTE and NR-U | Huawei, HiSilicon |
| R1-2207652 | Discussion on CSI periodic reporting for Dormant SCell state | Huawei, HiSilicon |
| R1-2207671 | Discussion on RAN3 LS on RB set configuration for IAB | Ericsson |
| R1-2207672 | Draft reply LS on RB set configuration for IAB | Ericsson |
| R1-2207673 | Discussion on RAN4 LS on range of power control parameters for eIAB | Ericsson |
| R1-2207812 | LS on DL-PRS measurements with reduced samples capability | RAN2, ZTE |
| R1-2207813 | LS on missing RRC parameter in IUC Scheme 2 | RAN2, Apple |
| R1-2207814 | Reply LS to RAN1 on priority for IUC | RAN2, vivo |
| R1-2207815 | LS on Rx beam sweeping factor for RRM measurements | RAN4, LG Electronics |
| R1-2207816 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2207911 | LS on further questions on feMIMO RRC parameters | RAN2, Ericsson |
| R1-2207999 | LS on skeleton of TR 38.864 for NR network energy savings | RAN3, Huawei |
| R1-2208000 | Reply LS on UL Tx switching across 3 or 4 bands | RAN4, China Telecom |
| R1-2208056 | Summary of offline discussion on BWP operation without bandwidth restriction | Moderator (Qualcomm) |
| R1-2208168 | LS on BWP operation without restriction | RAN1, Qualcomm |
| R1-2208172 | Progress on NCR identification and authorization | RAN3, ZTE |
| R1-2208204 | LS on further questions on feMIMO RRC parameters | RAN2, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2207493 | Correction on determination of TBS for NPDSCH | ASUSTeK |
| R1-2207574 | Misssing DCI formats when mapping ACKNACK resource offset field | Ericsson |
| R1-2207575 | DRAFT CR Misssing DCI formats when mapping ACKNACK resource offset field | Ericsson |
| R1-2207849 | Summary on companies’ views on R1-2207493 | Moderator (ASUSTeK) |
| R1-2207912 | Moderator Summary [110-LTE-Maintenance] on Missing DCI Formats | Moderator (Ericsson) |
| R1-2208028 | Correction on determination of TBS for NPDSCH | ASUSTeK |
| R1-2208087 | Missing DCI formats when mapping ACKNACK resource offset field | Ericsson |
| R1-2208119 | Moderator Summary [110-LTE-Maintenance] of Reply LS on the CSI periodic reporting for Dormant SCell state | Moderator (Samsung) |
| R1-2208162 | Session notes for 6 (Releases 8 – 16 E-UTRA Maintenance) | Ad-hoc Chair (CMCC) |
| R1-2208177 | Correction on determination of TBS for NPDSCH | ASUSTeK |
| R1-2208253 | Draft CR on the CSI periodic reporting for dormant SCell state in Rel15 | Moderator (Samsung) |
| R1-2208254 | Draft CR on the CSI periodic reporting for dormant SCell state in Rel16 | Moderator (Samsung) |
| R1-2208255 | CR on the CSI periodic reporting for dormant SCell state in Rel15 | Moderator (Samsung) |
| R1-2208256 | CR on the CSI periodic reporting for dormant SCell state in Rel16 | Moderator (Samsung) |
| R1-2208257 | Draft reply LS on the CSI periodic reporting for Dormant SCell state | Moderator (Samsung) |
| R1-2208258 | Reply LS on the CSI periodic reporting for Dormant SCell state | RAN1, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2205765 | Discussion on SRS carrier switching | Huawei, HiSilicon |
| R1-2205785 | Discussion on the collision of overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2205786 | Correction on the collision of overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2205811 | Add Space Division Multiplexing PRB Usage for MIMO cell | CMDI ZTE |
| R1-2205941 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | ZTE |
| R1-2205942 | Draft 38.214 CR on TBS determination | ZTE |
| R1-2205943 | Draft 38.214 CR on TBS determination | ZTE |
| R1-2206305 | Clarification on collision handling for overlapping PUCCHs with repetitions | OPPO |
| R1-2206339 | Draft CR on HARQ-ACK multiplexing on PUSCH without PUCCH | ZTE |
| R1-2206340 | Discussion on HARQ-ACK multiplexing on PUSCH when last DL DCI is missing | ZTE |
| R1-2206341 | Draft CR on HARQ-ACK multiplexing on PUSCH when last DL DCI is missing | ZTE |
| R1-2206349 | Clarification on precoding determination for Type 1 CG PUSCH | CATT |
| R1-2206350 | Collision handling of more than two overlapping PUCCHs with repetition | CATT |
| R1-2206428 | n_RNTI for CG-PUSCH initial Tx scrambling | Nokia, Nokia Shanghai Bell |
| R1-2206429 | PUSCH power control, configuration of the set of p0 in P0-PUSCH-AlphaSet | Nokia, Nokia Shanghai Bell |
| R1-2206531 | Discussion on SRS carrier switching | Intel Corporation |
| R1-2206781 | Discussion on more than two overlapping PUCCHs with repetitions | Samsung |
| R1-2206782 | Draft CR for Intra-UE multiplexing/prioritization of the same priority | Samsung |
| R1-2207004 | On PUSCH power initialization during BWP switch | MediaTek Inc. |
| R1-2207170 | Issue on PUCCH overlapping with PUCCH with repetitions | Qualcomm Incorporated |
| R1-2207171 | Remaining issues for SRS carrier switching | Qualcomm Incorporated |
| R1-2207262 | Clarification on RNTI selection for PUSCH and PDSCH | Qualcomm Incorporated |
| R1-2207523 | Correction on interrupted transmission indication | Huawei, HiSilicon |
| R1-2207531 | Discussion on multiple CSI reports associated with the same PUCCH resource ID | Huawei, HiSilicon |
| R1-2207781 | Summary of clarification on RNTI selection | Moderator (Qualcomm) |
| R1-2207913 | Summary of Collision handling for overlapping PUCCHs with repetitions | Moderator (Samsung) |
| R1-2207950 | Summary of R1-2206428 discussions (n_RNTI) | Moderator (Nokia) |
| R1-2207951 | Summary of R1-2206429 discussions (alpha set) | Moderator (Nokia) |
| R1-2207959 | Feature lead summary on SRS carrier switching | Moderator (Huawei) |
| R1-2207960 | Draft CR on SRS carrier switching | Moderator (Huawei) |
| R1-2207961 | Summary on multiple CSI reports associated with the same PUCCH resource ID | Moderator (Huawei) |
| R1-2207962 | Summary of discussion on draft CR on precoding determination for Type 1 CG | Moderator (CATT) |
| R1-2207971 | Summary of the draft CR on TBS determination | Moderator (ZTE) |
| R1-2207972 | Summary of HARQ-ACK multiplexing on PUSCH without PUCCH | Moderator (ZTE) |
| R1-2207985 | Summary of comments on R1-2207004 “On PUSCH power initialization during BWP switch” | Moderator (MediaTek Inc.) |
| R1-2208085 | [Draft CR] Correction for Intra-UE multiplexing/prioritization of the same priority | Moderator (Samsung), Huawei, HiSilicon, CATT |
| R1-2208086 | [Draft CR] Correction for Intra-UE multiplexing/prioritization of the same priority | Moderator (Samsung), Huawei, HiSilicon, CATT |
| R1-2208151 | Session notes for 7.1 (Maintenance on NR Releases 15) | Ad-Hoc Chair (CMCC) |
| R1-2208219 | Summary of comments on R1-2207523 Correction on interrupted transmission indication | Moderator (Huawei) |
| R1-2208227 | Correction for Intra-UE multiplexing/prioritization of the same priority | Moderator (Samsung), Huawei, HiSilicon, CATT |
| R1-2208228 | Correction for Intra-UE multiplexing/prioritization of the same priority | Moderator (Samsung), Huawei, HiSilicon, CATT |
| R1-2208249 | CR on SRS carrier switching | Moderator (Huawei), Qualcomm |
| R1-2208279 | Summary #2 of clarification on RNTI selection | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208305 | Rel-16 editorial corrections for TS 37.213 (mirrored to Rel-17) | Ericsson |
| R1-2208306 | Rel-16 editorial corrections for TS 37.213 | Ericsson |
| R1-2208307 | Rel-16 editorial corrections for TS 38.214 | Nokia |
| R1-2208308 | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R1-2206089 | Correction on parallel transmission of MsgA and other channels in TS 38.214 | ZTE, Sanechips |
| R1-2207818 | Summary of draft CR on parallel MsgA and other channels | Moderator (ZTE) |
| R1-2208037 | Correction on parallel transmission of MsgA and other channels in TS 38.214 | Moderator (ZTE) |
| R1-2208103 | Correction on parallel transmission of MsgA and other channels in TS 38.214 | Moderator (ZTE) |
| R1-2208109 | Correction on parallel transmission of MsgA and other channels in TS 38.214 | Moderator (ZTE) |
| R1-2208130 | Session notes for 7.2.1 (Maintenance of Two step RACH for NR) | Ad-Hoc Chair (CMCC) |
| R1-2208187 | Correction on parallel transmission of MsgA and other channels in TS 38.214 | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205947 | Discussion on HARQ-ACK multiplexing on PUSCH | ZTE |
| R1-2205948 | Discussion on Type-3 HARQ codebook in case of PUCCH repetition | ZTE |
| R1-2206935 | Miscellaneous corrections to TS 37.213 | Sharp |
| R1-2207376 | Draft CR on CAPC for DL | NTT DOCOMO, INC. |
| R1-2207594 | Correction on DL channel access procedure for NR-U | WILUS Inc. |
| R1-2207721 | FL summary on CRs submitted for Rel-16 NR-U | Moderator (Qualcomm) |
| R1-2207763 | Summary#1 on draft CRs on CAPC for DL | Moderator (NTT DOCOMO, INC.) |
| R1-2207919 | Summary of comments on R1-2206935 miscellaneous corrections to TS 37.213 | Moderator (Sharp) |
| R1-2207934 | [DRAFT] Reply LS on clarification of RACH prioritisation rules between LTE and NR-U | Ericsson |
| R1-2207935 | Reply LS on clarification of RACH prioritisation rules between LTE and NR-U | RAN1, Ericsson |
| R1-2208003 | Summary#2 on draft CRs on CAPC for DL | Moderator (NTT DOCOMO, INC.) |
| R1-2208057 | Summary of HARQ-ACK multiplexing on PUSCH | Moderator (ZTE) |
| R1-2208058 | Summary of Type-3 HARQ codebook in case of PUCCH repetition | Moderator (ZTE) |
| R1-2208131 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Huawei) |
| R1-2208169 | Summary#3 on draft CRs on CAPC for DL | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206094 | Corrections of the parameter for configuring PSSCH DMRS time pattern in TS 38.214 | ZTE, Sanechips |
| R1-2206095 | Miscellaneous corrections to TS 38.214 | ZTE, Sanechips |
| R1-2206715 | Correction on P0 of SL power control | vivo |
| R1-2206716 | Correction on UE capability and SAI counting for DCI format 3_0 reception | vivo |
| R1-2207641 | Correction on description for SL CG type 2 PSSCH transmission | Huawei, HiSilicon |
| R1-2207914 | Miscellaneous corrections to TS 38.214 | ZTE, Sanechips |
| R1-2207915 | Views on corrections to TS 38.214 under AI 7.2.4 | ZTE, Sanechips |
| R1-2207929 | Summary of SL power control P0 issue in R1-2206715 | Moderator (vivo) |
| R1-2207930 | Summary of UE capability and SAI counting for DCI format 3_0 issue in R1-2206716 | Moderator (vivo) |
| R1-2207995 | Summary of issue on description for SL CG type 2 PSSCH | Moderator (Huawei) |
| R1-2208001 | Correction on DCI format 3_0 reception | Moderator (vivo) |
| R1-2208002 | Correction on DCI format 3_0 reception | Moderator (vivo) |
| R1-2208064 | Summary of issue on description for SL CG type 2 PSSCH transmission in R1-2207641 | Moderator (Huawei) |
| R1-2208065 | Summary of SL power control P0 issue in R1-2206715 | Moderator (vivo) |
| R1-2208113 | Summary#3 of SL power control P0 issue in R1-2206715 | Moderator (vivo) |
| R1-2208120 | Draft LS on SL P0 parameters | vivo |
| R1-2208121 | LS on SL P0 parameters | RAN1, vivo |
| R1-2208128 | Correction on DCI format 3_0 reception | Moderator(vivo), Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO, ZTE, Sanechips |
| R1-2208129 | Correction on DCI format 3_0 reception | Moderator(vivo), Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, OPPO, ZTE, Sanechips |
| R1-2208152 | Session notes for 7.2.4 (Maintenance on 5G V2X with NR sidelink) | Ad-Hoc Chair (Huawei) |
| R1-2208235 | Summary#2 of issue on description for SL CG type 2 PSSCH transmission in R1-2207641 | Moderator (Huawei) |
| R1-2208283 | Summary#4 of SL power control P0 issue in R1-2206715 | Moderator (vivo) |
| R1-2208284 | Summary#2 of UE capability and SAI counting for DCI format 3_0 issue in R1-2206716 | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205759 | Remaining issues on UCI multiplexing and prioritization | Huawei, HiSilicon |
| R1-2205781 | Remaining issues on UL prioritization cases related to SP-CSI | Huawei, HiSilicon |
| R1-2205782 | Correction on UL prioritization cases related to CG PUSCHs | Huawei, HiSilicon |
| R1-2205783 | Correction on Priority rules for CSI reports in TS 38.214 | Huawei, HiSilicon |
| R1-2205970 | Discussion on UCI multiplexing and prioritization | ZTE |
| R1-2206143 | [Draft CR] Correction on intra-UE prioritization for configured grant PUSCHs | Nokia, Nokia Shanghai Bell |
| R1-2206144 | [Draft CR] Clarification on intra-UE prioritization for PUSCH with SP-CSI | Nokia, Nokia Shanghai Bell |
| R1-2206145 | Discussion on Rel-16 UE procedure for intra-UE prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2206146 | [Draft CR] Intra-UE prioritization clarification for PUCCH / PUSCH scheduled by a DCI | Nokia, Nokia Shanghai Bell |
| R1-2206306 | Discussion on scheduling and HARQ enhancement | OPPO |
| R1-2206532 | PUCCH collision handling for more than two overlapped PUCCHs with repetition | Intel Corporation |
| R1-2207172 | Maintenance for R16 eURLLC | Qualcomm Incorporated |
| R1-2207270 | Corrections on presence of redundancy version field and HARQ process number field of DCI formats 0_2/1_2 for validation of activation and release DCI format | Sharp |
| R1-2207271 | Corrections on presence of redundancy version field and HARQ process number field of DCI format 0_2 for semi-persistent CSI activation or deactivation PDCCH validation | Sharp |
| R1-2207307 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple |
| R1-2207533 | Correction on UL prioritization cases related to SP-CSI | Huawei, HiSilicon |
| R1-2207782 | Summary of additional patterns for span-based PDCCH | Moderator (Qualcomm) |
| R1-2207783 | Summary of corrections for PUSCH TDRA | Moderator (Qualcomm) |
| R1-2207827 | Summary 1 Intra-UE prioritization related to SP-CSI | Moderator (Huawei) |
| R1-2207828 | Summary 1 Correction on Priority rules for CSI reports in TS 38.214 | Moderator (Huawei) |
| R1-2207829 | Summary 1 Correction on UL prior cases related to CG PUSCHs | Moderator (Huawei) |
| R1-2207851 | Summary of views on R1-2207270 and R1-2207271: Corrections on presence of the RV field and the HPN field of DCI formats 0_2/1_2 for PDCCH validation | Moderator (Sharp) |
| R1-2207954 | Summary 2 Intra-UE prioritization related to SP-CSI | Moderator (Huawei) |
| R1-2207977 | Summary#2 of corrections for PUSCH TDRA | Moderator (Qualcomm) |
| R1-2207996 | Correction for PUSCH TDRA Tables | Qualcomm |
| R1-2207997 | Correction for PUSCH TDRA Tables | Qualcomm |
| R1-2208050 | Correction on UL prioritization cases related to CG PUSCHs | Moderator (Huawei) |
| R1-2208076 | Correction for PUSCH TDRA Tables | Qualcomm |
| R1-2208173 | [Draft] Correction on UL prioritization cases related to CG PUSCHs | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2208174 | Correction on UL prioritization cases related to CG PUSCHs | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2208259 | Corrections on presence of redundancy version field and HARQ process number field of DCI formats 0_2/1_2 for validation of activation and release DCI format | Sharp |
| R1-2208260 | Corrections on presence of redundancy version field and HARQ process number field of DCI formats 0_2/1_2 for validation of activation and release DCI format | Sharp |
| R1-2208261 | Corrections on presence of redundancy version field and HARQ process number field of DCI format 0_2 for semi-persistent CSI activation or deactivation PDCCH validation | Sharp |
| R1-2208262 | Corrections on presence of redundancy version field and HARQ process number field of DCI format 0_2 for semi-persistent CSI activation or deactivation PDCCH validation | Sharp |
| R1-2208280 | Summary #2 of additional patterns for span-based PDCCH | Moderator (Qualcomm) |
| R1-2208281 | Summary #3 of corrections for PUSCH TDRA | Moderator (Qualcomm) |
| R1-2208285 | Summary of discussions on UCI multiplexing and prioritization in Rel-16 URLLC | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206372 | Clarification of LI reporting for Enhanced Type II CSI feedback | CATT |
| R1-2207502 | Correction on PL RS determination for PUSCH scheduled by DCI format 0_0 | ASUSTeK |
| R1-2207830 | Summary for R1-2206372 on LI reporting for Rel.16 Enhanced Type II CSI feedback | Moderator (CATT) |
| R1-2207847 | Summary on companies’ views on R1-2207502 | Moderator (ASUSTeK) |
| R1-2208073 | Clarification of LI reporting for Enhanced Type II CSI feedback | Moderator (CATT) |
| R1-2208195 | Correction on PL RS determination for PUSCH scheduled by DCI format 0_0 | Moderator (ASUSTeK), LG Electronics |
| R1-2208263 | Clarification of LI reporting for Enhanced Type II CSI feedback | CATT |
| R1-2208264 | Clarification of LI reporting for Enhanced Type II CSI feedback | CATT |
| R1-2208265 | Correction on PL RS determination for PUSCH scheduled by DCI format 0_0 | Moderator (ASUSTeK), LG Electronics |
| R1-2208266 | Correction on PL RS determination for PUSCH scheduled by DCI format 0_0 | Moderator (ASUSTeK), LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R1-2205772 | Correction on positioning measurements | Huawei, HiSilicon |
| R1-2207615 | Maintenance for NR positioning support | Ericsson |
| R1-2207739 | Correction to align DL PRS frequency layer terminology | Ericsson |
| R1-2207824 | Summary #1 of R1-2205772 Correction on positioning measurements | Moderator (Huawei) |
| R1-2207895 | Summary#1 on discussion on draft CR in R1-2207615 | Moderator (Ericsson) |
| R1-2208132 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206371 | Discussion of SCell dormancy without DRX | CATT |
| R1-2207005 | On Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | MediaTek Inc. |
| R1-2207931 | Summary of offline discussion on SCell dormancy without DRX (R1-2206371) | Moderator (CATT) |
| R1-2207986 | Summary of comments on R1-2207005 “On Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy” | Moderator (MediaTek Inc.) |
| R1-2207998 | Summary#2 of comments on R1-2207005 “On Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy” | Moderator (MediaTek Inc.) |
| R1-2208133 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2208163 | Issue summary on R1-2207005 “On Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy” | Moderator (MediaTek Inc.) |
| R1-2208164 | Draft CR on Rel-16 Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | Moderator (MediaTek Inc.) |
| R1-2208165 | Draft CR on Rel-16 Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | Moderator (MediaTek Inc.) |
| R1-2208166 | CR on Rel-16 Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | Moderator (MediaTek Inc.) |
| R1-2208167 | CR on Rel-16 Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | Moderator (MediaTek Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207173 | Discussion on Rel-16 span-based PDCCH monitoring capability | Qualcomm Incorporated |
| R1-2207784 | Summary of additional capabilities for span-based PDCCH | Moderator (Qualcomm) |
| R1-2208153 | Session notes for 7.2.11 (NR Rel-16 UE Features) | Ad-Hoc Chair (CMCC) |
| R1-2208250 | Reply LS on eMIMO features defined in different granularity with prerequisite | RAN1, Huawei |
| R1-2208282 | Summary #2 of additional capabilities for span-based PDCCH | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208289 | Corrections on the introduction of multicast-broadcast services in NR | Samsung |
| R1-2208290 | Corrections on NR coverage enhancements | Nokia |
| R1-2208291 | Corrections on NR Dynamic Spectrum Sharing enhancements | Nokia |
| R1-2208292 | Correction on further enhancements on MIMO for NR | Nokia |
| R1-2208293 | Corrections on enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Nokia |
| R1-2208294 | Corrections on NR Multicast and Broadcast Services | Nokia |
| R1-2208295 | Correction on NR Positioning Enhancements | Nokia |
| R1-2208296 | Corrections on UL Tx Switching enhancements | Nokia |
| R1-2208297 | Corrections on NR Sidelink enhancements | Nokia |
| R1-2208298 | Rel-17 editorial corrections for TS 38.214 | Nokia |
| R1-2208299 | Corrections on NR Multicast and Broadcast Services in 38.212 | Huawei |
| R1-2208300 | Correction on NR sidelink enhancement | Huawei |
| R1-2208301 | Corrections to NR support of multicast and broadcast services | Ericsson |
| R1-2208302 | Rel-17 editorial corrections for TS 38.213 | Samsung |
| R1-2208303 | Rel-17 editorial corrections for TS 38.212 | Huawei |
| R1-2208304 | RRC parameter corrections for TS 37.213 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2205762 | Correction on conflict resolution for PUSCH TCI-state | Huawei, HiSilicon |
| R1-2205763 | Correction on linking of search spaces | Huawei, HiSilicon |
| R1-2205764 | Correction on Rel-17 aperiodic SRS configuration for 1T4R | Huawei, HiSilicon |
| R1-2205926 | Draft CR on beam and power control update for PUCCH in mTRP-BFR in TS 38.213 | ZTE |
| R1-2205927 | Draft CR on SRS enhancement in TS 38.213 | ZTE |
| R1-2205928 | Draft CR on PDCCH repetition in TS38.213 | ZTE |
| R1-2205929 | Draft CR on closed loop power control resetting after BFR in TS38.213 | ZTE |
| R1-2205930 | Discussion on issues of cross CC power control for unified TCI | ZTE |
| R1-2205931 | Draft CR on applying default QCL assumption when indicated TCI state is associated with non-serving-cell PCI in TS38.214 | ZTE |
| R1-2205932 | Draft editorial CR on unified TCI in TS38.214 | ZTE |
| R1-2205933 | Draft CR on CPU occupied for MTRP CSI in TS38.214 | ZTE |
| R1-2205934 | Draft CR on CSS for Multi-TRP HST-SFN | ZTE |
| R1-2205935 | Draft CR on symbols overlapping between UL signal and non-serving cell SSB in 38.213 | ZTE |
| R1-2206100 | Correction on TCI state for RLF | Langbo |
| R1-2206136 | Draft CR on SRS enhancement in TS 38.214 | ZTE |
| R1-2206187 | Draft CR on default beam for unified TCI framework | |
| R1-2206188 | Draft CR on Target bandwidth part for indicated unified TCI state | |
| R1-2206217 | Draft CR on SR configured for TRP-specific BFRQ to TS38.213 | Lenovo |
| R1-2206218 | Draft CR on SRI-PUSCH-PowerControl for M-TRP PUSCH power control to TS38.213 | Lenovo |
| R1-2206219 | Draft editorial CR on UCI multiplexing in TS38.212 | Lenovo |
| R1-2206220 | Draft CR on PHR with unified TCI in TS 38.213 | Lenovo |
| R1-2206221 | Draft CR on inter-cell multi-TRP operation in TS38.214 | Lenovo |
| R1-2206222 | Draft CR on monitoring Type0/0A/1/2 PDCCH CSS with HST deployment in TS38.213 | Lenovo |
| R1-2206254 | Corrections on TCI indication of CORESET not following unified TCI state | OPPO |
| R1-2206255 | Corrections on activated TCI state in Unified TCI framework | OPPO |
| R1-2206256 | Corrections on TCI indication of SRS in Unified TCI framework | OPPO |
| R1-2206257 | Draft CR for CSI-RS port restriction for mTRP CSI | OPPO |
| R1-2206258 | Draft CR for CSI-RS power for inter-cell mTRP | OPPO |
| R1-2206259 | Draft CR for power control for PUSCH repetition | OPPO |
| R1-2206260 | Correction on the description of the SRS resource set indication for PUSCH repetition | OPPO |
| R1-2206261 | Correction for the SRS with available slot(s) | OPPO |
| R1-2206351 | Clarification of LI reporting for Enhanced Type II CSI feedback and Further Enhanced Type II Port Selection CSI feedback | CATT |
| R1-2206352 | Clarification on L1-RSRP reporting for enhanced group based beam reporting | CATT |
| R1-2206353 | Correction on BFD-RS set determination for mTRP BFR | CATT |
| R1-2206354 | Correction on TPMI determination for M-TRP PUSCH transmission | CATT |
| R1-2206355 | Clarification on indication of number of layers for Type 1 CG PUSCH | CATT |
| R1-2206356 | Correction on SRI/TPMI determination for Type 1 CG PUSCH | CATT |
| R1-2206357 | Correction on codebook subset determination for M-TRP PUSCH transmission | CATT |
| R1-2206358 | Editorial corrections on beam reporting in uplink panel selection | CATT |
| R1-2206359 | Correction on UL PC parameter for unified TCI framework | CATT |
| R1-2206452 | Draft CR on search space set linking for PDCCH repetition | NEC |
| R1-2206453 | Draft CR on DCI based TCI state indication | NEC |
| R1-2206454 | Discussion on DCI based TCI state indication | NEC |
| R1-2206455 | Draft CR on TPC application time window in case of interlaced PDCCH repetition | NEC |
| R1-2206456 | Discussion on TPC application time window in case of interlaced PDCCH repetition | NEC |
| R1-2206457 | Draft CR on DAI value for individual PDCCH candidate overlapping with one of PDCCH repetitions | NEC |
| R1-2206458 | Discussion on DAI value for individual PDCCH candidate overlapping with one of PDCCH repetitions | NEC |
| R1-2206481 | Draft CR on available slot offset for aperiodic SRS in 38.214 | ZTE |
| R1-2206717 | Draft CR on SFN-based CORESET#0 issue for HST-SFN | vivo |
| R1-2206718 | Draft CR on information field alignment for BWP switching for MTRP PUSCH repetition | vivo |
| R1-2206719 | Draft CR on PTRS power boosting for MTRP PUSCH repetition | vivo |
| R1-2206720 | Draft CR on power control for configured grant based PUSCH for unified TCI framework | vivo |
| R1-2206721 | Draft CR on the activated unified TCI states for determining the indicated TCI state | vivo |
| R1-2206722 | Draft CR on the application of the indicated unified TCI state for the DL/UL channel over multiple slots | vivo |
| R1-2206723 | Draft CR on BAT for CA case | vivo |
| R1-2206724 | Draft CR on SSSG behavior for PDCCH repetition | vivo |
| R1-2206725 | Clarification on ambiguity of AL8 and AL16 | vivo |
| R1-2206726 | Draft CR on the QCL assumption of PDSCH and aperiodic CSI-RS for unified TCI framework | vivo |
| R1-2206727 | Draft CR on the application of the configuration of group-based beam reporting | vivo |
| R1-2206728 | Correction on SRS following unified TCI state | vivo |
| R1-2206729 | Correction on RRC parameters for SRS and power control with unified TCI states | vivo |
| R1-2206784 | Draft CR on Unified TCI state of CORESET 0 | Samsung |
| R1-2206785 | Draft CR on HARQ-ACK feedback for beam indication | Samsung |
| R1-2206786 | Draft CR on PHR enhancement for mTRP PUSCH repetition | Samsung |
| R1-2206787 | Draft CR on default QCL assumption in HST-SFN | Samsung |
| R1-2206788 | Draft CR on inter-set guard period for SRS enhancement | Samsung |
| R1-2206863 | Draft CR on UL PC with common TCI state pool for CA | LG Electronics |
| R1-2206864 | Draft CR on beam failure recovery for M-TRP | LG Electronics |
| R1-2206865 | Draft CR on SRS antenna switching | LG Electronics |
| R1-2207113 | TCI state parameter naming alignment | Ericsson |
| R1-2207114 | TCI state parameter naming alignment | Ericsson |
| R1-2207115 | Clarification of the reference CC functionality | Ericsson |
| R1-2207116 | Discussion on the reference CC functionality | Ericsson |
| R1-2207132 | Draft CR correcting RRC parameter related to unified TCI and inter cell | Ericsson |
| R1-2207133 | Draft CR on QCL assumption for SFN PDSCH | Ericsson |
| R1-2207134 | Draft CR aligning parameter name related to multi-TRP inter cell | Ericsson |
| R1-2207174 | Draft CR on default beam with unified TCI for cross-carrier scheduling | Qualcomm Incorporated |
| R1-2207175 | Draft CR on SRS power control parameters with unified TCI | Qualcomm Incorporated |
| R1-2207176 | Draft CR on L1-RSRP reporting for enhanced group based beam report | Qualcomm Incorporated |
| R1-2207177 | Draft CR on inter-cell mTRP when SSBs of additional PCI overlap with UL | Qualcomm Incorporated |
| R1-2207178 | Draft CR on inter-cell mTRP with PUSCH repetition TypeB | Qualcomm Incorporated |
| R1-2207308 | Maintenance of further enhancements on MIMIO | Apple |
| R1-2207377 | Draft CR on default QCL for unified TCI state for PDSCH and A-CSI-RS | NTT DOCOMO, INC. |
| R1-2207378 | Draft CR on DCI triggering aperiodic SRS only | NTT DOCOMO, INC. |
| R1-2207379 | Draft CR on inter-set guard period for antenna switching SRS | NTT DOCOMO, INC. |
| R1-2207488 | Correction on unified TCI state | ASUSTeK |
| R1-2207489 | Correction on spatial filter used for Msg 3 retransmission | ASUSTeK |
| R1-2207498 | Correction on BFD-RS indication MAC CE | ASUSTeK |
| R1-2207500 | Correction on higher layer parameter of SRS resource set | ASUSTeK |
| R1-2207510 | Draft CR on default PUSCH power control parameters for mTRP PUSCH | Ericsson |
| R1-2207526 | Discussion on the definition of inter-set guard period | Huawei, HiSilicon |
| R1-2207527 | Correction on definition of inter-set guard period | Huawei, HiSilicon |
| R1-2207528 | Correction on slot offsets of CSI-RS resource pairs for MTRP | Huawei, HiSilicon |
| R1-2207532 | Correction on UE behavior in the interval between SRS resource sets | Huawei, HiSilicon |
| R1-2207534 | Maintenance of enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2207535 | Draft CR 38.213 Rel-17 CORESET Configured with CSS and Follow Unified TCI State | Nokia, Nokia Shanghai Bell |
| R1-2207536 | Draft CR 38.214 Rel-17 multi-beam enhancements_beam switch HARQ | Nokia, Nokia Shanghai Bell |
| R1-2207537 | Draft CR 38.214 Rel-17 multi-beam enhancements_CG PUSCH type 1 | Nokia, Nokia Shanghai Bell |
| R1-2207538 | Draft CR 38.214 Rel-17 multi-beam enhancements_default operation correspondence index | Nokia, Nokia Shanghai Bell |
| R1-2207539 | Draft CR 38.213 BFD-RS Selection in SFN Operation Mode | Nokia, Nokia Shanghai Bell |
| R1-2207540 | Draft CR 38.213 New Beam Identification Resource Pair for SFN Operation Mode | Nokia, Nokia Shanghai Bell |
| R1-2207541 | Draft CR 38.213 PDCCH Monitoring After m-TRP BFR | Nokia, Nokia Shanghai Bell |
| R1-2207542 | Draft CR on UL SRS Inter-slot GP time location | Nokia, Nokia Shanghai Bell |
| R1-2207543 | Draft CR on UL SRS Inter-slot GP time location for the first and/or last resource | Nokia, Nokia Shanghai Bell |
| R1-2207568 | Draft CR 38.214 Rel-17 MTRP-CSI_number of CPUs | Nokia |
| R1-2207593 | Motivation for Draft CR on default PUSCH power control parameters for mTRP PUSCH | Ericsson |
| R1-2207612 | Draft CR on channel measurement with two Resource Groups | Ericsson |
| R1-2207613 | Motivation for Draft CR on channel measurement with two Resource Groups | Ericsson |
| R1-2207639 | Correction on default power control parameters | Huawei, HiSilicon |
| R1-2207640 | Correction on BFD-RS | Huawei, HiSilicon |
| R1-2207656 | Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH | Huawei, HiSilicon |
| R1-2207745 | Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 0) | Moderator (Intel Corporation) |
| R1-2207773 | Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management | Moderator (CATT) |
| R1-2207834 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 1: multi-beam | Moderator (ZTE) |
| R1-2207850 | Moderator Summary on Rel-17 FeMIMO maintenance for SRS | Moderator (ZTE) |
| R1-2207859 | Summary of maintenance issues for multi-TRP PDCCH repetition | Moderator (Qualcomm) |
| R1-2207861 | Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP PUCCH/PUSCH enhancement | Moderator (Nokia) |
| R1-2207877 | Moderator Summary for Rel.17 NR FeMIMO maintenance: CSI Enhancement (Round 0) | Moderator (Huawei, HiSilicon) |
| R1-2207878 | Moderator Summary for Rel.17 NR FeMIMO maintenance: CSI Enhancement (Round 1) | Moderator (Huawei, HiSilicon) |
| R1-2207890 | Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 0) Final | Moderator (Intel Corporation) |
| R1-2207891 | Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 1) | Moderator (Intel Corporation) |
| R1-2207896 | [Draft] CR on default QCL for unified TCI state for PDSCH and A-CSI-RS | Moderater (ZTE), ZTE, NTT DOCOMO, Google, Qualcomm, [vivo] |
| R1-2207897 | [Draft] editorial CR on unified TCI in TS38.214 | Moderator (ZTE), ZTE |
| R1-2207898 | [Draft] Correction on RRC parameters for SRS and power control with unified TCI states | Moderator(ZTE), vivo, CATT |
| R1-2207899 | [Draft] Correction on SRS following unified TCI state | Moderator (ZTE), vivo |
| R1-2207900 | TCI state parameter name alignment | Moderator (ZTE), Ericsson, ASUSTeK |
| R1-2207901 | TCI state parameter naming | Moderator (ZTE), Ericsson, ASUSTeK |
| R1-2207902 | [Draft] CR correcting RRC parameter related to unified TCI and inter cell | Moderator (ZTE), Ericsson |
| R1-2207903 | Editorial corrections on beam reporting in uplink panel selection | Moderator (ZTE), CATT |
| R1-2207907 | Correction on Rel-17 aperiodic SRS configuration for 1T4R | Moderater (ZTE), Huawei, HiSilicon |
| R1-2207908 | Draft CR on SRS enhancement in TS 38.214 | Moderater (ZTE), ZTE |
| R1-2207909 | Correction for the SRS with available slot(s) | Moderater (ZTE), OPPO |
| R1-2207916 | FL summary on CR on intercell-mtrp | Moderator (vivo) |
| R1-2207945 | CR on PDCCH repetition with SSSG switching | Moderator (Qualcomm), vivo |
| R1-2207947 | FL summary#2 on CR on intercell-mtrp | Moderator (vivo) |
| R1-2207955 | Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2207963 | Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 1 | Moderator (ZTE) |
| R1-2208052 | Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2208059 | FL summary#3 on CR on intercell-mtrp | Moderator (vivo) |
| R1-2208060 | CR on inter-cell multi-TRP operation | Moderator (vivo), Lenovo, OPPO |
| R1-2208061 | CR on inter-cell mTRP with PUSCH repetition TypeB | Moderator (vivo) |
| R1-2208062 | CR on inter-cell mTRP when SSBs of additional PCI overlap with UL | Moderator (vivo) |
| R1-2208067 | CR on default PUSCH power control parameters for mTRP PUSCH | Moderator (Nokia), Ericsson |
| R1-2208068 | CR for power control of mTRP PUSCH repetition | Moderator (Nokia), OPPO |
| R1-2208069 | CR on the description of the SRS resource set indication for PUSCH repetition | Moderator (Nokia), OPPO |
| R1-2208081 | CR for CSI-RS power for inter-cell mTRP | Moderator (vivo), OPPO |
| R1-2208082 | CR on inter-cell multi-TRP operation | Moderator (vivo), Lenovo, OPPO |
| R1-2208083 | CR on inter-cell mTRP with PUSCH repetition TypeB | Moderator (vivo), Qualcomm |
| R1-2208084 | CR on inter-cell mTRP when SSBs of additional PCI overlap with UL | Moderator (vivo), Qualcomm, ZTE |
| R1-2208092 | Draft CR on default QCL assumption in HST-SFN | Moderator (Intel Corporation), Samsung, NTT DOCOMO, Qualcomm |
| R1-2208093 | Draft reply LS on LS on further questions on feMIMO RRC parameters | Ericsson |
| R1-2208098 | CR on default QCL for unified TCI state for PDSCH and A-CSI-RS | Moderater (ZTE), ZTE, NTT DOCOMO, Google, Qualcomm, vivo |
| R1-2208099 | CR on unified TCI in TS38.214 | Moderator (ZTE), ZTE |
| R1-2208100 | CR on BAT for CA case | Moderator (ZTE), vivo |
| R1-2208156 | Moderator Summary for Rel.17 NR FeMIMO maintenance: mTRP beam management (Round 1) | Moderator (CATT) |
| R1-2208180 | Moderator Summary for Rel.17 NR FeMIMO maintenance: CSI Enhancement (Round 2) | Moderator (Huawei, HiSilicon) |
| R1-2208181 | Correction on the number of CPUs for Multi-TRP CSI | Moderator (Huawei), Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2208182 | Correction on CSI-RS port restriction for mTRP CSI | Moderator (Huawei), OPPO |
| R1-2208183 | Correction on slot offsets of CSI-RS resource pairs for MTRP | Moderator (Huawei), HiSilicon |
| R1-2208184 | Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH | Moderator (Huawei), HiSilicon |
| R1-2208203 | LS on TCI state indication of CORESET#0 associated with SS#0 | RAN1, Intel Corporation, vivo |
| R1-2208224 | Reply LS on LS on further questions on feMIMO RRC parameters | RAN1, Ericsson |
| R1-2208232 | Summary for OFFLINE FeMIMO Reply to RAN2 LS RRC | Moderator (ZTE) |
| R1-2208236 | CR on the application of the configuration of group-based beam reporting | Moderator (CATT), vivo |
| R1-2208240 | Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 2 | Moderator (ZTE) |
| R1-2208242 | CR on default QCL assumption in HST-SFN | Moderator (Intel Corporation), Samsung, NTT DOCOMO, Qualcomm |
| R1-2208252 | Correction on Rel-17 aperiodic SRS configuration for 1T4R | Moderater (ZTE), Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2205743 | Remaining details for Beyond 52.6 channel access | FUTUREWEI |
| R1-2205768 | Remaining issue of initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2205769 | Corrections on HARQ codebook generation for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2205770 | Discussion on timeline of CSI request for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2206080 | Discussion on remaining issues of channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2206081 | Draft CR on multi-slot PDCCH monitoring for TS 38.213 | ZTE, Sanechips |
| R1-2206082 | Clarification on Contention Exempt Short Control Signalling rules for UL in TS 37.213 | ZTE, Sanechips |
| R1-2206083 | Correction on the subcarrier offset k_SSB in TS 38.211 | ZTE, Sanechips |
| R1-2206084 | Correction on the tables for determining PDCCH monitoring occasions in TS 38.213 | ZTE, Sanechips |
| R1-2206085 | Correction on a reference SCS configuration for co-DurationList in TS 38.213 | ZTE, Sanechips |
| R1-2206086 | Correction on UE PDSCH processing procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | ZTE, Sanechips |
| R1-2206087 | Correction on CD-SSB frequency indication using NCD-SSB in TS 38.213 | ZTE, Sanechips |
| R1-2206088 | Discussion on CD-SSB frequency indication using NCD-SSB | ZTE, Sanechips |
| R1-2206160 | Correction on Type-1 HARQ-ACK codebook determination in TS 38.213 | Fujitsu |
| R1-2206180 | Remaining issues for NR 52.6 GHz to 71 GHz | InterDigital, Inc. |
| R1-2206293 | Discussion on remaining issue short control signaling | OPPO |
| R1-2206294 | Draft CR on resolving issue for short control signaling | OPPO |
| R1-2206362 | Correction on channel access procedures upon detection of a common DCI for frequency range 2-2 | CATT |
| R1-2206363 | Corrections for PDCCH monitoring occasion for DCI format 2_1 for the features extending NR operation to 71 GHz | CATT |
| R1-2206364 | Corrections on Random Access Response Grant Content field for frequency range 2-2 | CATT |
| R1-2206365 | Corrections on the value of slot configuration period for the features extending NR operation to 71 GHz | CATT |
| R1-2206533 | Discussion on remaining issues on TCI states for the scheduled PDSCHs by a DCI | Intel Corporation |
| R1-2206534 | [draft CR] Correction on the activated TCI states for the scheduled PDSCHs by a DCI | Intel Corporation |
| R1-2206535 | Discussion on Type-2 HARQ-ACK CB generation when both of spatial bundling and time bundling are configured | Intel Corporation |
| R1-2206536 | [draft CR] Correction on Type-2 HARQ-ACK CB generation when both of spatial bundling and time bundling are configured | Intel Corporation |
| R1-2206537 | Discussion on Channel Access Indication within Fall-back and RAR UL Grant DCIs | Intel Corporation |
| R1-2206538 | [draft CR] correction on support of channel access indication within the fall-back DCIs | Intel Corporation |
| R1-2206539 | [draft CR] correction on support of channel access indication within the UL RAR grant | Intel Corporation |
| R1-2206540 | Discussion on Applicability of the Short Control Signalling Exemption | Intel Corporation |
| R1-2206541 | [draft CR] Correction on short control signaling LBT exemption applicability | Intel Corporation |
| R1-2206542 | Discussion on Pout and EDT Threshould for Independent per-beam LBT Operation | Intel Corporation |
| R1-2206543 | [draft CR] Correction on EDT threshold calculation for per-beam LBT operation | Intel Corporation |
| R1-2206615 | Correction on the bit length of ChannelAccess-CPext-CAPC field in DCI 0-1 and DCI 1-1 for FR 2-2 | Xiaomi |
| R1-2206730 | Correction on indication of cell defined SSB from non-cell defined SSB | vivo |
| R1-2206731 | Remaining issues on CD-SSB frequency indication in initial access | vivo |
| R1-2206732 | Correction on multi-slot PDCCH monitoring in CA scenario with mixed capability types | vivo |
| R1-2206733 | Correction on short control signaling constrain | vivo |
| R1-2206734 | Correction on the indication of channel access Types | vivo |
| R1-2206735 | Remaining issues on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2206736 | Correction on division of TBGs for Type-2 codebook | vivo |
| R1-2206737 | Correction on time domain bundling with spatial bundling for Type-2 codebook | vivo |
| R1-2206738 | Remaining issues on Type-2 codebook for multi-PDSCH scheduling | vivo |
| R1-2206789 | Discussion for cell-defining SSB indication using non-cell-defining SSB in FR2-2 | Samsung |
| R1-2206790 | Draft CR for cell-defining SSB indication using non-cell-defining SSB in FR2-2 | Samsung |
| R1-2206791 | Draft CR for multi-slot PDCCH monitoring in FR2-2 | Samsung |
| R1-2206792 | Draft CR for multi-beam channel access procedure in FR2-2 | Samsung |
| R1-2206793 | Draft CR for HARQ-ACK timing parameters for FR2-2 | Samsung |
| R1-2206794 | Draft CR for aperiodic CSI triggering offset for FR2-2 | Samsung |
| R1-2206976 | Remaining issues on channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2206977 | Correction on ChannelAccess-Cpext field in fallback DCIs 0_0 and 1_0 | Nokia, Nokia Shanghai Bell |
| R1-2206978 | Correction on ChannelAccess-Cpext field in random access response | Nokia, Nokia Shanghai Bell |
| R1-2207018 | Corrections on Short Control Signaling | Nokia, Nokia Shanghai Bell |
| R1-2207021 | On UE capability parameters for CA with per-slot group monitoring | Nokia, Nokia Shanghai Bell |
| R1-2207023 | Discussion on default value of duration-r17 in FR2-2 | LG Electronics |
| R1-2207024 | Draft CR for SSSG switching with multiple cells in FR2-2 | LG Electronics |
| R1-2207025 | Discussion on SSSG switching with multiple cells in FR2-2 | LG Electronics |
| R1-2207026 | Draft CR for aperiodic CSI triggering offset in FR2-2 | LG Electronics |
| R1-2207027 | Draft CR for type-1 HARQ-ACK codebook for multi-PDSCH scheduling | LG Electronics |
| R1-2207028 | Remaining issues of channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2207029 | Draft CR for independent per-beam sensing and LBT procedure for UE in FR2-2 | LG Electronics |
| R1-2207030 | Draft CR on channel access indication for RAR grant in FR2-2 | LG Electronics |
| R1-2207031 | Draft CR for channel access indication within fallback-DCI in FR2-2 | LG Electronics |
| R1-2207082 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2207098 | Correction on UE resuming a UE initiated COT | Nokia, Nokia Shanghai Bell |
| R1-2207179 | Draft CR on ChannelAccess-Cpext in Fallback DCI | Qualcomm Incorporated |
| R1-2207180 | Draft CR on ChannelAccess-Cpext in RAR UL Grant | Qualcomm Incorporated |
| R1-2207181 | Draft CR on sensing exempted transmission of first message of RACH | Qualcomm Incorporated |
| R1-2207182 | Draft CR on BW parameter in EDT determination and ED Value cap | Qualcomm Incorporated |
| R1-2207183 | Draft CR on UL transmission with LBT per sensing beam | Qualcomm Incorporated |
| R1-2207184 | Draft CR on EDT determination rule for COT with SDM or TDM transmission with per beam LBT | Qualcomm Incorporated |
| R1-2207185 | Draft CR on rule for resuming a transmission after a gap within MCOT | Qualcomm Incorporated |
| R1-2207186 | Draft CR on rule for channel access type upgrade | Qualcomm Incorporated |
| R1-2207187 | Discussion paper on Maintenance for NR from 52.6GHz to 71 GHz | Qualcomm Incorporated |
| R1-2207269 | Draft CR for spatial HARQ-ACK bundling for type-2 codebook with multi-PDSCH scheduling | Nokia, Nokia Shanghai Bell |
| R1-2207309 | Maintenance on Supporting NR from 52.6GHz to 71GHz | Apple |
| R1-2207380 | Draft CR on channel access type indication by fallback DCI in FR2-2 | NTT DOCOMO, INC. |
| R1-2207381 | Draft CR on spatial domain filter for sensing in FR2-2 | NTT DOCOMO, INC. |
| R1-2207382 | Discussion on remaining issues for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2207464 | Draft CR on UE capability name alignment | Ericsson |
| R1-2207465 | Discussion on UE capability name alignment | Ericsson |
| R1-2207466 | Draft CR on Group 2 search space configuration | Ericsson |
| R1-2207467 | Discussion on Group 2 search space configuration | Ericsson |
| R1-2207468 | Draft CR on LBT-type indication in RAR UL grant | Ericsson |
| R1-2207469 | Discussion on LBT-type indication in RAR UL grant | Ericsson |
| R1-2207470 | Draft CR on LBT-type indication in Fallback DCIs | Ericsson |
| R1-2207471 | Discussion on LBT-type indication in Fallback DCIs | Ericsson |
| R1-2207472 | Discussion on L3-RSSI measurements and LS to RAN4 | Ericsson |
| R1-2207473 | Discussion on configuration to enable LBT for all transmissions | Ericsson |
| R1-2207495 | Correction on CSI-RS validation | ASUSTeK |
| R1-2207519 | Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2207524 | Corrections on the timeline of CSI request in TS38.214 | Huawei, HiSilicon |
| R1-2207595 | Remaining issue on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2207608 | On spatial HARQ-ACK bundling for type-2 codebook with multi-PDSCH scheduling | Nokia, Nokia Shanghai Bell |
| R1-2207642 | Remaining issues of channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2207663 | Corrections to ED threshold for use with Type 2 channel access procedure in FR2-2 in TS37.213 | Huawei, HiSilicon |
| R1-2207664 | Corrections to the conditions for channel sensing in FR2-2 in TS37.213 | Huawei, HiSilicon |
| R1-2207696 | Summary of issues on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2207717 | On spatial HARQ-ACK bundling for type-2 codebook with multi-PDSCH scheduling | Nokia, Nokia Shanghai Bell |
| R1-2207722 | FL summary#1 on CRs submitted to Rel-17 60GHz band channel access aspect | Moderator (Qualcomm) |
| R1-2207723 | FL summary#2 on CRs submitted to Rel-17 60GHz band channel access aspect | Moderator (Qualcomm) |
| R1-2207724 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2207753 | FL summary #1 of PDSCH/PUSCH enhancement (RS and timeline) | Moderator (vivo) |
| R1-2207794 | Discussion Summary #1 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2207948 | FL Summary for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2207964 | DRAFT LS to RAN2 on reportSlotOffsetList parameter for NR up to 71GHz | Moderator (vivo) |
| R1-2207965 | Draft CR Corrections on timeline of CSI request for 480kHz and 960kHz SCS in TS38.214 | Moderator (vivo), Huawei, HiSilicon |
| R1-2207966 | Draft CR Correction on UE PDSCH processing procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | Moderator (vivo), ZTE, Sanechips |
| R1-2207967 | Draft CR Corrections on the value of slot configuration period in TS 38.213 for the features extending NR operation to 71 GHz | Moderator (vivo), CATT, Nokia |
| R1-2207968 | Draft CR Correction for aperiodic CSI triggering offset for FR2-2 in TS 38.214 | Moderator (vivo), LG Electronics, Samsung |
| R1-2208006 | FL summary#3 on CRs submitted to Rel-17 60GHz band channel access aspect | Moderator (Qualcomm) |
| R1-2208007 | Corrections on timeline of CSI request for 480kHz and 960kHz SCS in TS38.214 | Moderator (vivo), Huawei, HiSilicon |
| R1-2208008 | Correction on UE PDSCH processing procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | Moderator (vivo), ZTE, Sanechips |
| R1-2208009 | Corrections on the value of slot configuration period in TS 38.213 for the features extending NR operation to 71 GHz | Moderator (vivo), CATT, Nokia |
| R1-2208010 | Correction for aperiodic CSI triggering offset for FR2-2 in TS 38.214 | Moderator (vivo), LG Electronics, Samsung |
| R1-2208026 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2208033 | Correction on the tables for determining Type0 PDCCH monitoring occasions | Moderator (Intel Corporation), ZTE, Sanechips |
| R1-2208034 | Correction on the subcarrier offset, kssb | Moderator (Intel Corporation), ZTE, Sanechips |
| R1-2208039 | [DRAFT] LS to RAN2 on RRC parameter impact for NR up to 71GHz | Moderator (vivo) |
| R1-2208040 | LS to RAN2 on RRC parameter impact for NR up to 71GHz | RAN1, vivo |
| R1-2208051 | Summary#2 of issues on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2208055 | Correction on multi-slot PDCCH monitoring in NR-DC and CA scenarios with mixed capability types | Moderator (Lenovo), vivo, Ericsson |
| R1-2208088 | Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon, Ericsson, Lenovo |
| R1-2208089 | Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon, Ericsson, Lenovo |
| R1-2208112 | Correction on a reference SCS configuration for co-DurationList in TS 38.213 | Moderator (Qualcomm), ZTE, Sanechips |
| R1-2208134 | Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) | Ad-Hoc Chair (Huawei) |
| R1-2208154 | Correction on Type-2 HARQ CB generation when both of spatial bundling and time bundling are configured | Moderator (LG Electronics), vivo, Fujitsu, ZTE, Huawei, InterDigital, Intel |
| R1-2208155 | Correction on Type-2 HARQ CB generation when time bundling is configured but spatial bundling is not configured | Moderator (LG Electronics), vivo, Fujitsu, ZTE, InterDigital, Intel |
| R1-2208179 | Correction on CD-SSB frequency indication using NCD-SSB in TS 38.213 | Moderator (Intel Corporation) |
| R1-2208198 | FL summary#4 on CRs submitted to Rel-17 60GHz band channel access aspect | Moderator (Qualcomm) |
| R1-2208213 | Draft CR on ChannelAccess-Cpext in Fallback DCI | Moderator (Qualcomm) |
| R1-2208214 | Draft CR on ChannelAccess-Cpext in RAR UL Grant | Moderator (Qualcomm) |
| R1-2208215 | Corrections to the conditions for channel sensing in FR2-2 in TS37.213 | Moderator (Qualcomm), Huawei, HiSilicon |
| R1-2208230 | Draft LS on condition to apply channel access procedure | OPPO |
| R1-2208231 | LS on condition to apply channel access procedure | RAN1, OPPO |
| R1-2208241 | Correction on CD-SSB frequency indication using NCD-SSB in TS 38.213 | Moderator (Intel Corporation), Samsung, ZTE, Sanechips |
| R1-2208244 | CR on ChannelAccess-Cpext in Fallback DCI | Moderator (Qualcomm) |
| R1-2208272 | Corrections to the conditions for channel sensing in FR2-2 in TS37.213 | Moderator (Qualcomm), Huawei, HiSilicon |
| R1-2208309 | Corrections to the conditions for channel sensing in FR2-2 in TS37.213 | Moderator (Qualcomm), Huawei, HiSilicon, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2205790 | Discussion on the timing for semi-static PUCCH pattern | Huawei, HiSilicon |
| R1-2205791 | Correction on PUCCH repetition with semi-static PUCCH cell switching | Huawei, HiSilicon |
| R1-2205792 | Remaining issue for HP SPS HARQ-ACK colliding with LP HARQ-ACK | Huawei, HiSilicon |
| R1-2205793 | Remaining issue for HP PUCCH with HARQ-ACK and SR colliding LP HARQ-ACK | Huawei, HiSilicon |
| R1-2205949 | Draft CR for semi-static PUCCH cell switch and PUCCH repetitions | ZTE |
| R1-2205950 | Discussion on multiplexing PUCCH carrying HP SR and HP HARQ with PUCCH carrying LP HARQ-ACK | ZTE |
| R1-2206147 | [Draft CR] RRC parameter corrections for Rel-17 enhanced IIoT and URLLC for NR in 38.212 | Nokia, Nokia Shanghai Bell |
| R1-2206148 | [Draft CR] RRC parameter corrections for Rel-17 enhanced IIoT and URLLC for NR in 38.213 | Nokia, Nokia Shanghai Bell |
| R1-2206149 | [Draft CR] RRC parameter corrections for Rel-17 enhanced IIoT and URLLC for NR in 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2206150 | [Draft CR] Corrections to DCI field size definitions for DCI formats 1_1 and 1_2 for the secondary PUCCH group for Rel-17 URLLC / IIoT HARQ-ACK feedback enhancements | Nokia, Nokia Shanghai Bell |
| R1-2206151 | [Draft CR] Correction to Rel-17 URLLC / IIoT HARQ-ACK codebook retransmission triggering indication | Nokia, Nokia Shanghai Bell |
| R1-2206152 | [Draft CR] Correction on semi-static PUCCH cell switching and PUCCH repetitions PDCCH | Nokia, Nokia Shanghai Bell |
| R1-2206153 | Discussion document for 38.213 Draft CR: Correction on semi-static PUCCH cell switching and SCell activation / dormancy to active | Nokia, Nokia Shanghai Bell |
| R1-2206154 | [Draft CR] Correction on semi-static PUCCH cell switching and SCell activation / dormancy to active | Nokia, Nokia Shanghai Bell |
| R1-2206228 | [Draft CR] RRC parameter corrections for Rel-17 enhanced IIoT and URLLC for NR in 37.213 | Nokia, Nokia Shanghai Bell |
| R1-2206229 | Accompanying discussions on draft CRs to 38.213 on Rel-17 URLLC / IIoT Intra-UE Multiplexing/Prioritization | Nokia, Nokia Shanghai Bell |
| R1-2206230 | [Draft CR] Collision resolution involving LP PUCCH with HARQ-ACK and CSI/SR | Nokia, Nokia Shanghai Bell |
| R1-2206231 | [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-2206232 | [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-2206366 | HP PUCCH format 0/1 with SR and HARQ-ACK overlapping with LP HARQ-ACK | CATT |
| R1-2206425 | Draft CR on UE procedure for overlapping CG PUSCH and DG PUSCH | ZTE |
| R1-2206474 | Clarification on semi-static PUCCH cell switching for PUCCH repetitions | NEC |
| R1-2206544 | Correction on HP DG PUSCH and LP CG PUSCH collision resolution | Intel Corporation |
| R1-2206545 | Remaining issue for Intra-UE Uplink Channel Multiplexing and Prioritization | Intel Corporation |
| R1-2206739 | Correction on PUCCH repetition for semi-static PUCCH cell switching | vivo |
| R1-2206740 | Draft CR on HP PUCCH with HARQ-ACK and SR colliding with LP HARQ-ACK | vivo |
| R1-2206741 | Draft CR on multiplexing for HP SPS HARQ-ACK | vivo |
| R1-2206795 | Maintenance on HARQ-ACK feedback enhancements | Samsung |
| R1-2206796 | Maintenance on Intra-UE Multiplexing/Prioritization | Samsung |
| R1-2206939 | Draft CR on time point to apply PUCCH cell switching pattern | CATT |
| R1-2206941 | Draft CR for simultaneous configuration of semi-static PUCCH cell switching and PUCCH repetition | CATT |
| R1-2206942 | Draft CR on SPS HARQ-ACK deferral | CATT |
| R1-2206948 | Remaining issues on Enhanced IIoT and URLLC | ETRI |
| R1-2206949 | Draft CR on Enhanced IIoT and URLLC | ETRI |
| R1-2207032 | Remaining issues on HARQ-ACK feedback enhancements | LG Electronics |
| R1-2207033 | Remaining issues on Intra-UE multiplexing enhancements | LG Electronics |
| R1-2207188 | Correction for joint operation of semi-static PUCCH cell switch and PUCCH repetitions | Qualcomm Incorporated |
| R1-2207189 | Correction for HARQ-ACK codebook generation for PUCCH cell switching and UL BWP switching | Qualcomm Incorporated |
| R1-2207190 | Discussion on timeline for PUCCH cell switch with Scell activation, deactivation, and dormancy | Qualcomm Incorporated |
| R1-2207191 | Discussion on remaining issues on intra-UE multiplexing and prioritization | Qualcomm Incorporated |
| R1-2207192 | Correction for intra-UE multiplexing and prioritization | Qualcomm Incorporated |
| R1-2207310 | Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC | Apple |
| R1-2207490 | Remaining Issues of Intra-UE Multiplexing/Prioritization for IIoT/URLLC | Ericsson |
| R1-2207491 | Collision of HP PUCCH PF0/1 with {HARQ-ACK, SR} and LP HARQ-ACK | Ericsson |
| R1-2207492 | Corrections on DG-CG PUSCH prioritization | Ericsson |
| R1-2207501 | Correction on HARQ-ACK retransmission indicator | ASUSTeK |
| R1-2207596 | Remaining issues on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2207627 | Correction on semi-static PUCCH cell switching and PUCCH repetitions | Ericsson |
| R1-2207657 | Correction for HP SPS HARQ-ACK colliding with LP HARQ-ACK | Huawei, HiSilicon |
| R1-2207658 | Correction for HP PUCCH with HARQ-ACK and SR colliding LP HARQ-ACK | Huawei, HiSilicon |
| R1-2207659 | Correction on enhanced Type 3 HARQ-ACK codebook in 38.212 | Huawei, HiSilicon |
| R1-2207660 | Correction on HARQ-ACK enhancement related RRC parameters in 38.213 | Huawei, HiSilicon |
| R1-2207661 | Correction on PUCCH carrier switching related RRC parameters in 38.213 | Huawei, HiSilicon |
| R1-2207662 | Discussion on the missed RRC parameters from higher layer parameter list | Huawei, HiSilicon |
| R1-2207777 | Moderator summary #1 on Maintenance of HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2207778 | Moderator summary #2 on Maintenance of HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2207779 | Moderator summary #1 on RRC parameter corrections for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2207804 | FL summary of Rel-17 URLLC/IIoT intra-UE MUX A | Moderator (CATT) |
| R1-2207852 | Summary#1 on intra-UE multiplexing/prioritization B | Moderator (OPPO) |
| R1-2208004 | Summary#2 on intra-UE multiplexing/prioritization B | Moderator (OPPO) |
| R1-2208029 | Correction for HARQ-ACK codebook generation for PUCCH cell switching and UL BWP switching | Moderator (Nokia), Qualcomm |
| R1-2208094 | Draft CR on UE procedure for overlapping CG PUSCH and DG PUSCH | Moderator (OPPO), ZTE, Ericsson |
| R1-2208101 | Correction for HARQ-ACK codebook generation for PUCCH cell switching and UL BWP switching | Moderator (Nokia), Qualcomm |
| R1-2208102 | Moderator summary #3 on Maintenance of HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2208225 | CR on UE procedure for overlapping CG PUSCH and DG PUSCH | Moderator (OPPO), ZTE, Ericsson |
| R1-2208226 | CR on HP DG PUSCH and LP CG PUSCH collision resolution | Moderator (OPPO), Intel Corp |
| TDoc | Title | Source |
|---|---|---|
| R1-2205809 | Correction on HARQ-ACK transmission in NTN | Huawei, HiSilicon |
| R1-2205828 | Maintenance on Release-17 NR NTN | THALES |
| R1-2205833 | Discussion on Common TA Drift Variation | Lockheed Martin |
| R1-2205973 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | Spreadtrum Communications |
| R1-2206013 | Remaining issues on NR-NTN | ZTE |
| R1-2206014 | Corrections on NR-NTN synchronization | ZTE |
| R1-2206157 | Maintenance on Solutions for NR to support NTN | MediaTek Inc. |
| R1-2206178 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | PANASONIC |
| R1-2206233 | Correction on HARQ process number for NTN | ASUSTeK |
| R1-2206295 | Discussion on remaining issue for NTN-NR | OPPO |
| R1-2206296 | Draft CR on time relationship for MAC-CE activation | OPPO |
| R1-2206854 | Draft CR on interpretation SFN indicating epoch time | OPPO |
| R1-2206855 | Draft CR on editorial correction on Koffset MAC CE command | OPPO |
| R1-2207137 | Further aspects of Rel-17 maintenance of NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2207138 | Draft CR for 38.211 to ensure correct interworking between open and closed loop TA | Nokia, Nokia Shanghai Bell |
| R1-2207139 | Draft CR for 38.213 to capture correct validity timer expiry behavior for UL synchronization | Nokia, Nokia Shanghai Bell |
| R1-2207193 | Maintenance for R17 NR NTN | Qualcomm Incorporated |
| R1-2207311 | Maintenance on NR NTN | Apple |
| R1-2207357 | Remaining issues on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2207496 | Correction on HARQ feedback enabling for NTN | ASUSTeK |
| R1-2207497 | Correction on HARQ feedback enabling for the first SPS PDSCH | ASUSTeK |
| R1-2207512 | Correction on UE-specific TA for NTN | Huawei, HiSilicon |
| R1-2207554 | On NR NTN maintenance issues | Ericsson |
| R1-2207632 | FL Summary #1: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | THALES |
| R1-2207633 | FL Summary #2: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | THALES |
| R1-2207634 | FL Summary #3: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | THALES |
| R1-2207635 | FL Summary #4: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | THALES |
| R1-2207666 | Discussion on interpretation of SFN indicating Epoch time | Huawei, HiSilicon |
| R1-2207687 | Summary#1 of maintenance on scheduling and HARQ for NR NTN | Moderator (ZTE) |
| R1-2208042 | CR on the clarification of PUCCH resource determination in 38.213 | Moderator (ZTE), Huawei, HiSilicon, Xiaomi, OPPO, Ericsson |
| R1-2208043 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.213 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208044 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.214 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208045 | CR on DCI size for Rel-17 NTN HARQ in 38.212 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208124 | CR on the clarification of PUCCH resource determination in 38.213 | Moderator (ZTE), Huawei, HiSilicon, Xiaomi, OPPO, Ericsson |
| R1-2208125 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.213 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208126 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.214 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208127 | CR on DCI size for Rel-17 NTN HARQ in 38.212 | Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson |
| R1-2208135 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205773 | Maintenance of Rel-17 positioning | Huawei, HiSilicon |
| R1-2205774 | Correction to the condition of Rx beam index reporting | Huawei, HiSilicon |
| R1-2205775 | Correction of SRS and BWP restriction | Huawei, HiSilicon |
| R1-2205906 | Draft CR on DL-AOD positioning measurement for 38.214 | ZTE |
| R1-2205907 | Alignment CR on positioning for 38.214 | ZTE |
| R1-2205908 | Draft CR on RSTD measurement for 38.214 | ZTE |
| R1-2205909 | Draft CR on PRS processing sample for 38.214 | ZTE |
| R1-2205910 | Draft CR on PPW timeline issue for 38.214 | ZTE |
| R1-2205911 | Draft CR on remaining issues of PPW for 38.214 | ZTE |
| R1-2205912 | Discussion on some remaining issues for NR positioning | ZTE |
| R1-2205913 | Draft CR on RRC_INACTIVE positioning issue for 38.214 | ZTE |
| R1-2206270 | Corrections on M-sample measurement | OPPO |
| R1-2206271 | Correction for TEG-based DL positioning methods | OPPO |
| R1-2206272 | Correction for TEG-based UL positioning methods | OPPO |
| R1-2206367 | Correction on the definition of timing advance (TADV) | CATT |
| R1-2206368 | Correction on PRS reception procedure | CATT |
| R1-2206486 | Maintenance of NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
| R1-2206487 | Correction on PRS measurement outside MG | Nokia, Nokia Shanghai Bell |
| R1-2206488 | Correction on PRS collision timeline | Nokia, Nokia Shanghai Bell |
| R1-2206489 | Correction on PRS RSTD and PRS RSRPP reporting | Nokia, Nokia Shanghai Bell |
| R1-2206662 | Draft CR on UE TX TEG description for 38.214 | ZTE |
| R1-2206742 | Correction on accuracy improvements for NR positioning | vivo |
| R1-2206743 | Correction on latency and efficiency improvements for NR positioning | vivo |
| R1-2206744 | Discussion on accuracy improvements for NR positioning | vivo |
| R1-2206745 | Discussion on latency and efficiency improvements for NR positioning | vivo |
| R1-2206797 | Maintenance on NR Positioning Enhancements | Samsung |
| R1-2206798 | Draft CR on NR Positioning Enhancements | Samsung |
| R1-2207194 | Draft CR on NR R17 Positioning PPW Action Timelines | Qualcomm Incorporated |
| R1-2207195 | Maintenance for NR R17 Positioning | Qualcomm Incorporated |
| R1-2207609 | Draft CR on DL PRS measurement within DL PRS processing window | Ericsson |
| R1-2207610 | Motivation for Draft CR on DL PRS measurement within DL PRS processing window | Ericsson |
| R1-2207611 | Draft CR for higher layer parameter alignment | Ericsson |
| R1-2207643 | Correction of Rx diversity option for DL-PRS RSRPP reporting | Huawei, HiSilicon |
| R1-2207644 | Correction to PPW | Huawei, HiSilicon |
| R1-2207645 | Correction of BWP for SRS | Huawei, HiSilicon |
| R1-2207689 | FL Summary for mitigating UE/gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2207746 | Feature Lead Summary #1 for Maintenance of NR positioning Enhancements (AOD topics) | Moderator (Ericsson) |
| R1-2207747 | Feature Lead Summary #2 for Maintenance of NR positioning Enhancements (AOD topics) | Moderator (Ericsson) |
| R1-2207748 | Feature Lead Summary #3 for Maintenance of NR positioning Enhancements (AOD topics) | Moderator (Ericsson) |
| R1-2207825 | Summary #1 of positioning latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2207826 | Summary #2 of positioning latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2207892 | Summary of discussion on LS on timing advance (TADV) report mapping for NR UL E-CID positioning | Moderator (Ericsson) |
| R1-2207893 | [Draft] LS reply on timing advance (TADV) report mapping for NR UL E-CID positioning | Ericsson |
| R1-2207894 | LS reply on timing advance (TADV) report mapping for NR UL E-CID positioning | RAN1, Ericsson |
| R1-2207906 | Summary on LS for reduced PRS samples capability | Moderator (ZTE) |
| R1-2207940 | Reply LS on DL-PRS measurements with reduced samples capability | RAN1, ZTE |
| R1-2207943 | Correction on PRS reception procedure | Moderator (CATT), ZTE, vivo |
| R1-2207944 | Correction on UE sounding procedure for positioning purposes | Moderator(CATT), ZTE, vivo |
| R1-2207973 | FL Summary #2 for mitigating UE/gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2207988 | CR on DL-AOD positioning measurement for 38.214 | Moderator (Ericsson), ZTE |
| R1-2207989 | CR on PRS RSRPP reporting for 38.214 | Moderator (Ericsson), vivo |
| R1-2207990 | CR on PRS RSRPP for 38.215 | Moderator (Ericsson), Huawei, HiSilicon |
| R1-2208017 | CR on priority states within the PRS processing window | Moderator (Huawei), Ericsson, HiSilicon |
| R1-2208018 | CR on PRS processing sample for 38.214 | Moderator (Huawei), ZTE |
| R1-2208019 | Corrections on M-sample measurement | Moderator (Huawei), OPPO |
| R1-2208020 | CR on the positioning frequency layer within a PPW and UE capability for the PPW | Moderator (Huawei), ZTE |
| R1-2208021 | CR on PRS reception and SRS transmission outside initial BWP | Moderator (Huawei), vivo, ZTE, HiSilicon |
| R1-2208022 | Correction of BWP for SRS | Moderator (Huawei), HiSilicon |
| R1-2208136 | Session notes for 8.5 (Maintenance on NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2208170 | Correction on PRS reception procedure | Moderator (CATT), ZTE, vivo |
| R1-2208171 | Correction on UE sounding procedure for positioning purposes | Moderator (CATT), ZTE, vivo |
| R1-2208217 | Summary #2 of positioning latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2208218 | Draft CR on completing the PPW processing timeline | Moderator (Huawei), Qualcomm, ZTE, Nokia |
| R1-2208239 | CR on completing the PPW processing timeline | Moderator (Huawei), Qualcomm, ZTE, Nokia |
| R1-2208243 | Correction on PRS reception procedure | Moderator (Ericsson), CATT |
| TDoc | Title | Source |
|---|---|---|
| R1-2205738 | Corrections and clarifications of RedCap UE procedures | Ericsson |
| R1-2205788 | Correction on separate initial DL/UL BWP for RedCap UEs | Huawei, HiSilicon |
| R1-2205789 | Corrections related to NCD-SSB for RedCap UEs | Huawei, HiSilicon |
| R1-2205974 | Remaining issues on support of Reduced Capability NR Devices | Spreadtrum Communications |
| R1-2206298 | Other remaining issues for Reduced Capability NR Devices | OPPO |
| R1-2206369 | Correction on Type2-PDCCH CSS configuration in separate initial DL BWP | CATT |
| R1-2206416 | Remaining details on BWP operation for RedCap | NEC |
| R1-2206442 | Maintenance Issues on Complexity Reduction for RedCap | Nokia, Nokia Shanghai Bell |
| R1-2206546 | Draft CR on corrections to BWP operations for RedCap UEs | Intel Corporation |
| R1-2206547 | Remaining details on BWP operations for RedCap UEs | Intel Corporation |
| R1-2206548 | Draft CR on correction to handling of Types A and B PUSCH repetitions for HD-FDD RedCap UEs | Intel Corporation |
| R1-2206549 | Draft CR on corrections for handling of NCD-SSB for RedCap UEs | Intel Corporation |
| R1-2206550 | Draft CR on corrections for PDSCH reception in BWP configured with NCD-SSB for RedCap UEs | Intel Corporation |
| R1-2206551 | Discussion on NCD-SSB handling for RedCap UEs | Intel Corporation |
| R1-2206616 | Corrections on Half-duplex FDD operation in paired spectrum in TS 38.213 | Xiaomi |
| R1-2206746 | Corrections for RedCap UE behavior on BWP operation | vivo |
| R1-2206747 | Correction on PDSCH resource mapping around NCD-SSB for RedCap UE | vivo |
| R1-2206748 | Correction on PDCCH monitoring for RedCap UE | vivo |
| R1-2206749 | Corrections on DCI format 0_0 size determination for RedCap UE | vivo |
| R1-2206750 | Correction on available slot determination for PUSCH repetition type A for HD-FDD | vivo |
| R1-2206751 | Correction on invalid symbol determination for PUSCH repetition type B for HD-FDD | vivo |
| R1-2206888 | Correction on SSB transmission for initial DL BWP | CMCC |
| R1-2207000 | Correction for PUCCH resource set indication for RedCap | MediaTek Inc. |
| R1-2207045 | Discussion on RedCap remaining issues | ZTE, Sanechips |
| R1-2207046 | Correction on NCD-SSB related spec for RedCap in TS38.213 | ZTE, Sanechips |
| R1-2207047 | Correction on NCD-SSB related spec for RedCap in TS38.214 | ZTE, Sanechips |
| R1-2207048 | Correction on SSB and CORESET#0 presence for RedCap | ZTE, Sanechips |
| R1-2207196 | Maintenance on NR R17 RedCap UE | Qualcomm Incorporated |
| R1-2207272 | Corrections on available slot counting for PUSCH repetition type A for HD-UE | Sharp |
| R1-2207273 | Corrections on inclusion of NCD-SSB and switching gap for determining invalid symbols for PUSCH repetition type B for HD-UE | Sharp |
| R1-2207274 | Corrections on collision handling between NCD-SSB and UL transmission in TS38.213 for RedCap UE in unpaired spectrum | Sharp |
| R1-2207275 | Corrections on inclusion of NCD-SSB in TS38.214 for RedCap UE | Sharp |
| R1-2207276 | Correction on RRC parameter alignment for additional PRB offset in TS38.213 for RedCap UE | Sharp |
| R1-2207383 | Draft CR on timeline requirement for retransmitting MSG1/MSGA for RedCap | NTT DOCOMO, INC. |
| R1-2207384 | Discussion on timeline requirement for retransmitting MSG1/MSGA for RedCap | NTT DOCOMO, INC. |
| R1-2207494 | On PUCCH resource set indication for RedCap | MediaTek Beijing Inc. |
| R1-2207669 | Correction on separate initial UL BWP for RedCap UEs | Huawei, HiSilicon |
| R1-2207727 | FL summary #1 for Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2207728 | FL summary #2 for Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2207729 | FL summary #3 for Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2207979 | Draft Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2207980 | Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN1, Ericsson |
| R1-2208137 | Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2208207 | Draft LS on common PUCCH resource configuration for RedCap | Ericsson |
| R1-2208208 | LS on common PUCCH resource configuration for RedCap | RAN1, Ericsson |
| R1-2208247 | Corrections and clarifications of RedCap UE procedures | Moderator (Ericsson) |
| R1-2208274 | RAN1 agreements for Rel-17 NR RedCap | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2205794 | Correction on TRS not affecting UE behavior in CONNECTED mode | Huawei, HiSilicon |
| R1-2205795 | Retransmission handling during PDCCH skipping duration | Huawei, HiSilicon |
| R1-2205796 | Correction on retransmission handling during PDCCH skipping duration | Huawei, HiSilicon |
| R1-2205797 | Correction on PDCCH monitoring adaptation and BWP switching | Huawei, HiSilicon |
| R1-2205798 | Correction on PDCCH skipping with C-DRX operation | Huawei, HiSilicon |
| R1-2205799 | Correction on PDCCH monitoring adaptation for RACH procedure | Huawei, HiSilicon |
| R1-2205975 | Remaining issues on UE power saving enhancements | Spreadtrum Communications |
| R1-2206299 | Remaining issues for DCI-based power saving adaptation | OPPO |
| R1-2206300 | Draft CR for DCI-based power saving adaptation | OPPO |
| R1-2206374 | Remaining issues of PDCCH monitoring adaptation | CATT |
| R1-2206552 | Remaining issues of DCI-based PDCCH monitoring \n adaptation in active time | Intel Corporation |
| R1-2206617 | Remaining issues of PDCCH monitoring adaptation for power saving | Xiaomi |
| R1-2206618 | UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI | Xiaomi |
| R1-2206752 | Correction on PDCCH skipping for RACH procedure | vivo |
| R1-2206753 | Correction on Skipping duration within active time | vivo |
| R1-2206754 | Correction on PDCCH monitoring adaptation and BWP switching | vivo |
| R1-2207006 | Maintenance on UE Power Saving Enhancements | MediaTek Inc. |
| R1-2207049 | Discussion on remaining issues of UE power saving | ZTE, Sanechips |
| R1-2207050 | Correction on RRC parameters in TS38.212 | ZTE, Sanechips |
| R1-2207051 | Correction on RRC parameters in TS38.213 | ZTE, Sanechips |
| R1-2207052 | Correction on RRC parameters in TS38.214 | ZTE, Sanechips |
| R1-2207053 | Correction on PDCCH monitoring adaptation and BWP switching procedures | ZTE, Sanechips |
| R1-2207054 | Correction on PDCCH monitoring adaptation for RACH procedure | ZTE, Sanechips |
| R1-2207055 | Correction on search space set group switching and skipping of PDCCH monitoring | ZTE, Sanechips |
| R1-2207078 | Draft CR for DCI-based power saving adaptation | Dongguan OPPO Precision Elec. |
| R1-2207083 | Open issues on Idle/Inactive mode power saving | Nokia, Nokia Shanghai Bell |
| R1-2207084 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2207197 | Maintenance on UE Power Saving Enhancements | Qualcomm Incorporated |
| R1-2207198 | Draft CR on UE power saving enhancement | Qualcomm Incorporated |
| R1-2207199 | Draft CR on UE power saving enhancement | Qualcomm Incorporated |
| R1-2207200 | Draft CR on UE power saving enhancement | Qualcomm Incorporated |
| R1-2207312 | Maintenance on UE power saving enhancements | Apple |
| R1-2207371 | Correction on TRS for idle or inactive state UEs | ZTE, Sanechips |
| R1-2207431 | Discussion on corrections for PDCCH monitoring adaptation | Ericsson |
| R1-2207432 | Correction for PDCCH skipping during RAR window | Ericsson |
| R1-2207433 | Draft CR for PDCCH skipping interaction with HARQ retransmission and duration overlap with active time | Ericsson |
| R1-2207434 | Corrections for SSSG switching | Ericsson |
| R1-2207435 | Corrections for TRS occasions | Ericsson |
| R1-2207638 | Other remaining issues on UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2207646 | Correction on power saving for IDLE mode UE | Huawei, HiSilicon |
| R1-2207653 | Correction on parameter names for UE power saving | Huawei, HiSilicon |
| R1-2207654 | Correction on TRS occasions for IDLE mode UE | Huawei, HiSilicon |
| R1-2207758 | Summary#1 for maintenance on UE power saving enhancements | Moderator (MediaTek Inc.) |
| R1-2207970 | Summary#2 for maintenance on UE power saving enhancements | Moderator (MediaTek Inc.) |
| R1-2208138 | Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2208199 | Corrections on UE power saving enhancements for NR in TS 38.211 | Moderator (MediaTek) , Huawei, HiSilicon, ZTE, Sanechips |
| R1-2208200 | Corrections on UE power saving enhancements for NR in TS 38.212 | Moderator (MediaTek) , Huawei, HiSilicon, ZTE, Sanechips |
| R1-2208201 | Corrections on UE power saving enhancements for NR in TS 38.213 | Moderator (MediaTek) , Huawei, HiSilicon, vivo |
| R1-2208202 | Corrections on UE power saving enhancements for NR in TS 38.214 | Moderator (MediaTek) , Huawei, HiSilicon, ZTE, Sanechips |
| R1-2208209 | Draft LS on PDCCH skipping | MediaTek |
| R1-2208210 | LS on PDCCH skipping | RAN1, MediaTek |
| R1-2208276 | Corrections on UE power saving enhancements for NR in TS 38.211 | Moderator (MediaTek) , Huawei, HiSilicon, ZTE, Sanechips |
| R1-2208277 | Corrections on UE power saving enhancements for NR in TS 38.212 | Moderator (MediaTek) , Huawei, HiSilicon, ZTE, Sanechips |
| R1-2208278 | Corrections on UE power saving enhancements for NR in TS 38.213 | Moderator (MediaTek) , Huawei, HiSilicon, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2205776 | Discussion on A-CSI multiplexing on TBoMS PUSCH | Huawei, HiSilicon |
| R1-2205777 | Discussion on frequency hopping pattern enhancements for joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2205779 | Correction on A-CSI multiplexing on TBoMS PUSCH | Huawei, HiSilicon |
| R1-2205780 | Correction on frequency hopping pattern enhancements for joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2205806 | Correction on determining time domain window for bundling DMRS | Huawei, HiSilicon |
| R1-2205953 | Correction on available slot counting for inter-cell multi-TRPs | ZTE |
| R1-2205954 | Discussion on UE behavior of restarting DMRS bundling | ZTE |
| R1-2205955 | Correction on UE behavior of restarting DMRS bundling | ZTE |
| R1-2205976 | Clarification of A-CSI multiplexing on TBoMS | Spreadtrum Communications |
| R1-2206301 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2206302 | Draft CR for PUSCH repetition type A | OPPO |
| R1-2206370 | Correction on inter-slot frequency hopping with inter-slot bundling | CATT |
| R1-2206553 | Discussion on PUSCH repetition type A with available slots counting for inter-cell multi-TRPs | Intel Corporation |
| R1-2206554 | Correction on PUSCH repetition type A with available slots counting for inter-cell multi-TRPs | Intel Corporation |
| R1-2206555 | Correction on TBoMS for HD-FDD RedCap UEs | Intel Corporation |
| R1-2206556 | Correction on A-CSI reports on TBoMS | Intel Corporation |
| R1-2206557 | Discussion on action of TPC command and restarting DMRS bundling | Intel Corporation |
| R1-2206558 | Correction on action of TPC command for DMRS bundling | Intel Corporation |
| R1-2206559 | Discussion on enhanced inter-slot frequency hopping for PUSCH repetitions | Intel Corporation |
| R1-2206560 | Correction on enhanced inter-slot frequency hopping for PUSCH repetitions | Intel Corporation |
| R1-2206619 | Maintenance on NR coverage enhancement | Xiaomi |
| R1-2206683 | Remaining issues on Rel-17 NR coverage enhancements | China Telecom |
| R1-2206684 | Correction on inter-slot frequency hopping for DMRS bundling | China Telecom |
| R1-2206755 | Corrections of Msg3 repetition | vivo |
| R1-2206756 | Corrections of Msg3 repetition | vivo |
| R1-2206757 | A-CSI multiplexing on TBoMS | vivo |
| R1-2206758 | Available slot determination for inter-cell mTRP | vivo |
| R1-2206759 | Frequency hop determination for PUSCH with DMRS bundling | vivo |
| R1-2206760 | UE behavior of restarting DMRS bundling | vivo |
| R1-2206799 | PUSCH enhancements | Samsung |
| R1-2206800 | Draft CR on available slot counting for inter-cell multi-TRPs | Samsung |
| R1-2206801 | Joint channel estimation for PUSCH and PUCCH | Samsung |
| R1-2206802 | Draft CR on transmit power for DMRS bundling | Samsung |
| R1-2206852 | Draft CR for NR coverage enhancement about UE behavior for DMRS bundling | MediaTek Beijing Inc. |
| R1-2206862 | Discussion on joint channel estimation for PUSCH and PUCCH | Panasonic |
| R1-2206889 | Maintenance on NR coverage enhancement | CMCC |
| R1-2206943 | Discussion on inter-slot frequency hopping for DMRS bundling for PUSCH transmissions | ZTE |
| R1-2206944 | Correction on inter-slot frequency hopping for DMRS bundling for PUSCH transmissions | ZTE |
| R1-2206945 | Discussion on A-CSI for TBoMS | ZTE |
| R1-2207099 | Remaining issues on enhancements for PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2207100 | Change request on out of order PUSCH scheduling in case of counting on available slots | Nokia, Nokia Shanghai Bell |
| R1-2207101 | Change request on available slots counting in inter-cell multi-TRPs | Nokia, Nokia Shanghai Bell |
| R1-2207102 | Remaining issues on joint channel estimation for PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2207103 | Change request on UE behavior for power control adjustment state for PUCCH in the case of DMRS bundling | Nokia, Nokia Shanghai Bell |
| R1-2207104 | Change request on UE behavior for power control adjustment state for PUSCH in the case of DMRS bundling | Nokia, Nokia Shanghai Bell |
| R1-2207105 | Change request on removal of square brackets for starting RB determination for inter-slot frequency hopping when DMRS bundling is enabled | Nokia, Nokia Shanghai Bell |
| R1-2207106 | Change request on SRS resource sets mapping for supporting PUSCH repetition type A with joint channel estimation | Nokia, Nokia Shanghai Bell |
| R1-2207107 | Change request on spatial settings or power control parameters sets mapping for supporting PUCCH repetition with joint channel estimation | Nokia, Nokia Shanghai Bell |
| R1-2207108 | Remaining issues on transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2207109 | Change request on A-CSI multiplexing on TBoMS | Nokia, Nokia Shanghai Bell |
| R1-2207142 | Correction on available slot counting for a PUSCH scheduled by RAR UL grant or by DCI format with CRC scrambled by TC-RNTI for HD-FDD RedCap UE | Sharp |
| R1-2207155 | Discussion on available slot counting for inter-cell mTRP | InterDigital, Inc. |
| R1-2207156 | Available slot counting for inter-cell mTRP | InterDigital, Inc. |
| R1-2207158 | Correction for Available Slot Determination for Inter-Cell Multi-TRP Operation | Ericsson |
| R1-2207159 | Correction for Power Control with DMRS Bundling | Ericsson |
| R1-2207160 | Correction for A-CSI Multiplexing on TBoMS | Ericsson |
| R1-2207161 | Correction on Frequency Hopping Offset and Interval Determination for DMRS Bundling | Ericsson |
| R1-2207201 | Discussion on remaining issues on NR coverage enhancement | Qualcomm Incorporated |
| R1-2207202 | Correction on Inter-slot Frequency Hopping for PUSCH with DMRS Bundling | Qualcomm Incorporated |
| R1-2207203 | Correction on A-CSI multiplexing with TBOMS | Qualcomm Incorporated |
| R1-2207277 | Available slot counting for Inter-cell multi-TRPs in Rel-17 CovEnh | Sharp |
| R1-2207278 | Corrections on use of SSBs for inter-cell multiple TRPs for the available slot determination | Sharp |
| R1-2207385 | Discussion on remaining issues for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2207448 | Maintenance for coverage enhancement in terms of joint channel estimation for PUSCH | Sharp |
| R1-2207449 | Inter-slot frequency hopping with DMRS bundling for PUSCH | Sharp |
| R1-2207485 | Draft 38.213 CR on Msg3 repetition | ZTE |
| R1-2207486 | Draft 38.214 CR on Msg3 repetition | ZTE |
| R1-2207586 | Discussion on Available Slot Determination for Inter-Cell Multi-TRP | Ericsson |
| R1-2207587 | Discussion on Power Control with DMRS Bundling | Ericsson |
| R1-2207588 | Discussion on DMRS Bundling Restart | Ericsson |
| R1-2207589 | Discussion on A-CSI Multiplexing on TBoMS | Ericsson |
| R1-2207597 | Remaining issues on enhancements for PUSCH repetition Type A | WILUS Inc. |
| R1-2207755 | Summary of preparation phase for Rel-17 NR coverage enhancements – Remaining issues for TBoMS | Moderator (Nokia) |
| R1-2207756 | Summary of remaining issues for TBoMS for Rel-17 NR coverage enhancements | Moderator (Nokia) |
| R1-2207757 | Summary #2 of remaining issues for TBoMS for Rel-17 NR coverage enhancements | Moderator (Nokia) |
| R1-2207765 | FL summary of discussion on joint channel estimation for Rel-17 NR coverage enhancements | Moderator (China Telecom) |
| R1-2207845 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2207885 | FL summary #1 for Rel-17 CovEnh maintenance: Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2207886 | FL summary #1 of maintenance on PUCCH enhancements | Moderator (Qualcomm) |
| R1-2207889 | [Draft] CR for coverage enhancements in NR | ETRI |
| R1-2207917 | Moderator summary on RAN4 LS Reply about DMRS bundling for R17 NR Coverage Enhancement | Moderator (MediaTek Inc.) |
| R1-2207918 | Change request on A-CSI multiplexing on TBoMS | Nokia (Moderator), Intel, vivo |
| R1-2208111 | FL summary #2 of maintenance on PUCCH enhancements | Moderator (Qualcomm) |
| R1-2208139 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2208188 | FL summary #2 for Rel-17 CovEnh maintenance: Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2208211 | Draft Reply LS to RAN4 on DMRS bundling | MediaTek |
| R1-2208212 | Reply LS to RAN4 on DMRS bundling | RAN1, MediaTek |
| R1-2208313 | Change request on A-CSI multiplexing on TBoMS | Moderator (Nokia), Intel, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2207056 | Clarification on TBS range of QPSK for NUPSCH | ZTE, Sanechips |
| R1-2207572 | Clarification on the mapping to physical resources for 16-QAM in NB-IoT | Ericsson |
| R1-2207573 | DRAFT CR Clarification on the mapping to physical resources for 16-QAM in NB-IoT | Ericsson |
| R1-2207957 | Feature lead summary on 110-R17-NB_IoT_MTC | Moderator (Huawei) |
| R1-2207958 | Clarification on TBS range of QPSK for NUPSCH | Moderator (Huawei) |
| R1-2208140 | Session notes for 8.9 (Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2208251 | Clarification on TBS range of QPSK for NUPSCH | Moderator (Huawei), HiSilicon, ZTE, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2205808 | Correction on TDD configuration for IAB-MT | Huawei, HiSilicon |
| R1-2206202 | Corrections on misalignment for MAC CE or RRC parameters for eIAB in TS 38.213 | ZTE, Sanechips |
| R1-2206203 | Correction on the formula of Case-7 UL Tx timing for eIAB in TS 38.213 | ZTE, Sanechips |
| R1-2206204 | 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-2206205 | Correction on coexistence between Rel-16 and Rel-17 H/S/NA configuration | ZTE, Sanechips |
| R1-2206206 | Discussion on coexistence between Rel-16 and Rel-17 H/S/NA configuration | ZTE, Sanechips |
| R1-2206508 | Resource multiplexing in enhanced IAB systems | Lenovo |
| R1-2206561 | Remaining Issues on Frequency-domain Resource Multiplexing for IAB | Intel Corporation |
| R1-2206761 | Maintenance on Enhancements to Integrated Access and Backhaul | vivo |
| R1-2206762 | Corrections on resource availability indication | vivo |
| R1-2206803 | Maintenance on Enhancements to NR IAB | Samsung |
| R1-2206950 | Discussions on eIAB CSI | ETRI |
| R1-2206951 | Draft CR on eIAB CSI | ETRI |
| R1-2207204 | Draft CR on eIAB | Qualcomm Incorporated |
| R1-2207205 | Remaining issues on eIAB | Qualcomm Incorporated |
| R1-2207373 | On Handling for Rel-16 and Rel-17 Resource Configuration Conflicts | Nokia, Nokia Shanghai Bell |
| R1-2207521 | Remaining issues on resource multiplexing for IAB | Huawei, HiSilicon |
| R1-2207522 | Correction on CQI derivation accounting for provided DL Tx power adjustment for IAB-MT | Huawei, HiSilicon |
| R1-2207665 | Correction on HSNA resource configuration for IAB | Huawei, HiSilicon |
| R1-2207674 | Draft CR on DL Tx power control | Ericsson |
| R1-2207675 | Discussion on DL Tx power control | Ericsson |
| R1-2207676 | Draft CR on guard symbols MAC CEs | Ericsson |
| R1-2207677 | Draft CR on timing case indication | Ericsson |
| R1-2207678 | Draft CR on Hard/Soft/Not Available resource definition | Ericsson |
| R1-2207679 | Maintenance on enhanced IAB | Ericsson |
| R1-2207946 | Summary 1 of [110-R17-IAB] | Moderator (Qualcomm) |
| R1-2207956 | Summary 1 of discussion on IAB rely LS for R1-2205705 | Moderator (Huawei) |
| R1-2208053 | Correction on CQI derivation accounting for provided DL Tx power adjustment for IAB-MT | Moderator (Qualcomm), Huawei, HiSilicon |
| R1-2208054 | CR on eIAB CSI | Moderator (Qualcomm), ETRI |
| R1-2208220 | Draft reply LS on RB set configuration for IAB | Huawei |
| R1-2208221 | Reply LS on RB set configuration for IAB | RAN1, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2205742 | Correction for inter-UE coordination Scheme 2 determination of UE-B | FUTUREWEI |
| R1-2205766 | Remaining issues on maintenance of Rel-17 sidelink enhancements | Huawei, HiSilicon |
| R1-2205848 | Discussion on maintenance on NR sidelink enhancement | LG Electronics |
| R1-2205977 | Remaining issues on NR Sidelink enhancement | Spreadtrum Communications |
| R1-2206096 | Maintenance on NR SL enhancement | ZTE, Sanechips |
| R1-2206283 | Remaining essential issues in R17 NR sidelink enhancement | OPPO |
| R1-2206360 | Maintenance on NR sidelink enhancement | CATT, GOHIGH |
| R1-2206447 | Remaining issues on resource allocation for sidelink enhancement | Lenovo |
| R1-2206468 | Editorial correction for inter-UE coordination | NEC |
| R1-2206562 | Discussion on LS Related to RRC Parameters for IUC Scheme 1 and Default CBR Configuration | Intel Corporation |
| R1-2206563 | Discussion on LS on IUC with Non-Preferred Resource Set | Intel Corporation |
| R1-2206763 | Maintenance on NR Sidelink enhancement | vivo |
| R1-2206804 | Maintenance on NR sidelink enhancement | Samsung |
| R1-2206890 | Maintenance on NR Sidelink enhancement | CMCC |
| R1-2206936 | Remaining issues on NR sidelink enhancement | Sharp |
| R1-2207146 | Remaining issues on R17 SL Enhancement | InterDigital, Inc. |
| R1-2207206 | Remaining issues in Sidelink | Qualcomm Incorporated |
| R1-2207313 | On Maintenance of NR Sidelink Enhancement | Apple |
| R1-2207386 | Maintenance of sidelink enhancement | NTT DOCOMO, INC. |
| R1-2207483 | Maintenance on Inter-UE coordination | ASUSTeK |
| R1-2207563 | Critical corrections and remaining issues on NR SL enhancement | Ericsson |
| R1-2207766 | Feature lead summary #1 for AI 8.11 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2207767 | Feature lead summary #2 for AI 8.11 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2207768 | Feature lead summary #3 for AI 8.11 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2207785 | FL summary #1 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2207786 | FL summary #2 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2207787 | FL summary #3 for AI 8.11: R17 eSL power saving RA maintenance | Moderator (OPPO) |
| R1-2207788 | FL summary for AI 8.11: R17 eSL power saving RA maintenance (EOM) | Moderator (OPPO) |
| R1-2207952 | Moderator Summary of discussion for LS reply to R1-2205735 | Moderator (vivo) |
| R1-2207953 | Draft reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Moderator (vivo) |
| R1-2208024 | Moderator summary for reply LS to R1-2205727 | Moderator (Huawei) |
| R1-2208025 | Draft reply LS to RAN2 on RRC parameters for IUC Scheme 1 and default CBR configuration | Huawei, HiSilicon |
| R1-2208078 | Moderator Summary of Email Discussion on Reply LS to R1-2207813 | Moderator (Apple) |
| R1-2208079 | [Draft] Reply LS to RAN2 on Missing RRC Parameter in IUC Scheme 2 | Moderator (Apple) |
| R1-2208080 | Moderator Summary of Email Discussion on Reply LS in R1-2205728 | Moderator (Apple) |
| R1-2208090 | Reply LS to RAN2 on RRC parameters for IUC Scheme 1 and default CBR configuration | RAN1, Huawei |
| R1-2208091 | Moderator summary#2 for reply LS to R1-2205727 | Moderator (Huawei) |
| R1-2208097 | Reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig | Moderator (vivo) |
| R1-2208123 | Reply LS to RAN2 on Missing RRC Parameter in IUC Scheme 2 | RAN1, Apple |
| R1-2208141 | Session notes for 8.11 (Maintenance on NR Sidelink enhancement) | Ad-Hoc Chair (Huawei) |
| R1-2208159 | Moderator Summary for Reply LS to R1-2207813 | Moderator (Apple) |
| R1-2208222 | [Draft] Reply LS to RAN2 on IUC with Non-preferred Resource Set | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2205757 | Remaining issues for Rel-17 NR MBS | Huawei, HiSilicon, CBN |
| R1-2205951 | Maintenance of broadcast and multicast for MBS | ZTE |
| R1-2205978 | Discussion on the remaining issues for MBS | Spreadtrum Communications |
| R1-2206102 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED UEs | Langbo |
| R1-2206285 | Discussion on remaining issues on NR MBS | OPPO |
| R1-2206361 | Maintenance on NR Multicast and Broadcast Services | CATT |
| R1-2206445 | Remaining Issues for RRC_CONNECTED UEs supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2206446 | Remaining issues on reliability improvement and group scheduling for MBS | Lenovo |
| R1-2206476 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2206611 | Text proposals for NR Multicast and Broadcast Service | Xiaomi |
| R1-2206764 | Maintenance on NR Multicast and Broadcast Services | vivo |
| R1-2206805 | Maintenance on multicast-broadcast services | Samsung |
| R1-2206891 | Maintenance on NR multicast and broadcast services | CMCC |
| R1-2206946 | Remaining issues on NR Multicast and Broadcast Services | ETRI |
| R1-2207013 | Remaining issues on NR MBS | MediaTek Inc. |
| R1-2207034 | Maintenance on NR Multicast and Broadcast Services | LG Electronics |
| R1-2207207 | Maintenance on Rel-17 NR multicast | Qualcomm Incorporated |
| R1-2207314 | Remaining issues on NR Multicast and Broadcast Services | Apple |
| R1-2207387 | Maintenance on NR multicast and broadcast services | NTT DOCOMO, INC. |
| R1-2207503 | Correction on MBS SPS | ASUSTeK |
| R1-2207616 | Maintenance on NR Multicast and Broadcast Services | Ericsson |
| R1-2207711 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2207712 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2207713 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2207714 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2207817 | Moderator’s summary on Rel-17 NR MBS maintenance: mechanisms to support broadcast/multicast | Moderator (CMCC) |
| R1-2207857 | FL summary#1 on configurations for MBS regarding rate matching patterns and CORESET | Moderator (Huawei) |
| R1-2207858 | FL summary#2 on configurations for MBS regarding rate matching patterns and CORESET | Moderator (Huawei) |
| R1-2207975 | FL summary#3 on configurations for MBS regarding rate matching patterns and CORESET | Moderator (Huawei) |
| R1-2207991 | Moderator’s summary#2 on Rel-17 NR MBS maintenance: mechanisms to support broadcast/multicast | Moderator (CMCC) |
| R1-2207992 | Moderator’s summary#3 on Rel-17 NR MBS maintenance: mechanisms to support broadcast/multicast | Moderator (CMCC) |
| R1-2208071 | DRAFT reply LS on rate matching patterns and CORESET configuration for MBS | Huawei |
| R1-2208072 | Reply LS on rate matching patterns and CORESET configuration for MBS | RAN1, Huawei |
| R1-2208142 | Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205760 | Discussion on minimum scheduling offset restriction | Huawei, HiSilicon |
| R1-2205952 | Maintenance of Rel-17 DSS | ZTE |
| R1-2206430 | Disabling EN-DC power split when SCG is deactivated | Nokia, Nokia Shanghai Bell |
| R1-2206431 | Section naming correction on the CSI-RS for Tracking for Fast SCell activation | Nokia, Nokia Shanghai Bell |
| R1-2206564 | Correction on different SCS between P(S)Cell and sSCell | Intel Corporation |
| R1-2206565 | Discussion on different SCS between P(S)Cell and sSCell | Intel Corporation |
| R1-2206765 | Corrections for efficient SCell activation | vivo |
| R1-2206806 | Discussion on DCI size alignment for Rel-17 DSS | Samsung |
| R1-2206807 | Draft CR for DCI size alignment for Rel-17 DSS | Samsung |
| R1-2207208 | Draft CR on Aperiodic CSI-RS for tracking for fast SCell activation | Qualcomm Incorporated |
| R1-2207436 | Corrections for fast SCell activation | Ericsson |
| R1-2207667 | Correction on dormancy indication on SCell | Huawei, HiSilicon |
| R1-2207668 | Correction on dormancy indication on SCell | Huawei, HiSilicon |
| R1-2207835 | Summary#1 of Rel17 Maintenance on NR Dynamic spectrum sharing (DSS) | Moderator (Ericsson) |
| R1-2207927 | Summary#1 of further MR-DC/CA Enhancement | Moderator (Huawei) |
| R1-2208143 | Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2208190 | CR on Aperiodic CSI-RS for tracking for fast SCell activation | Moderator (Huawei), Qualcomm, Ericsson |
| R1-2208205 | Draft CR on DCI size alignment for Cross-carrier scheduling from SCell to Pcell | Moderator (Ericsson), Samsung |
| R1-2208246 | CR on DCI size alignment for Cross-carrier scheduling from SCell to Pcell | Moderator (Ericsson), Samsung |
| R1-2208248 | Summary#2 of Rel17 Maintenance on NR Dynamic spectrum sharing (DSS) | Moderator (Ericsson) |
| R1-2208286 | Summary#2 of further MR-DC/CA Enhancement | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206015 | Remaining issues on IoT-NTN | ZTE |
| R1-2206016 | Corrections on IoT-NTN synchronization | ZTE |
| R1-2206158 | Maintenance on NB-IoT/eMTC to support NTN | MediaTek Inc. |
| R1-2206159 | Summary #1 of AI 8.14 Maintenance on NB-IoT/eMTC to support NTN: time and frequency\nsynchronization | Moderator (MediaTek Inc.) |
| R1-2206179 | Corrections to NB-IoT/eMTC support for Non-Terrestrial Networks | Mediatek India Technology Pvt. |
| R1-2206297 | Draft CR on UE pre-compensation in segment | OPPO |
| R1-2207209 | Maintenance on IoT-NTN | Qualcomm Incorporated |
| R1-2207288 | Draft CR on correction of IoT NTN with dropping in pre-compensation per segment in 36.211 | Nokia, Nokia Shanghai Bell |
| R1-2207289 | Draft CR on correction of IoT NTN with dropping in pre-compensation per segment in 36.213 | Nokia, Nokia Shanghai Bell |
| R1-2207290 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Nokia, Nokia Shanghai Bell |
| R1-2207315 | Maintenance on IoT NTN | Apple |
| R1-2207513 | Corrections on NPDCCH monitoring restriction for IoT NTN | Huawei, HiSilicon |
| R1-2207569 | DRAFT CR on timing relationship enhancements for IoT NTN | Ericsson |
| R1-2207602 | Maintenance of IoT-NTN | Sony |
| R1-2207683 | On SIB accumulation and Timing relationship enhancements in IoT NTN | Ericsson |
| R1-2207759 | FL summary 1 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2207760 | FL summary 2 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2208074 | Summary #2 of AI 8.14 Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek Inc.) |
| R1-2208144 | Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Huawei) |
| R1-2208175 | Summary #3 of AI 8.14 Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek Inc.) |
| R1-2208176 | CR on UE pre-compensation in segment | Moderator (MediaTek) |
| R1-2208223 | CR on FDD HARQ-ACK reporting procedure | Moderator (MediaTek) |
| R1-2208237 | CR on FDD HARQ-ACK reporting procedure | Moderator (MediaTek) |
| R1-2208238 | CR on UE pre-compensation in segment | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207921 | Session Notes of AI 8.16.5 (NR_FeMIMO, NR_ext_to_71GHz, NR_NTN_solutions, IoT over NTN, NR_IAB_enh, NR_DSS, LTE_NR_DC_enh2, NR_pos_enh, and NR_DL1024QAM_FR1) | Ad-Hoc Chair (AT&T) |
| R1-2207923 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #110 Thursday | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2207924 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #110 Thursday | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2207925 | LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#110 Thursday | RAN1, AT&T, NTT DOCOMO |
| R1-2207926 | LS on updated Rel-17 RAN1 UE features lists for LTE after RAN1#110 Thursday | RAN1, AT&T, NTT DOCOMO |
| R1-2208118 | Session Notes for R17 UE Features 1 | Moderator (NTT DOCOMO, INC.) |
| R1-2208196 | DRAFT LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#110 Thursday | NTT DOCOMO, AT&T |
| R1-2208197 | DRAFT LS on updated Rel-17 RAN1 UE features lists for LTE after RAN1#110 Thursday | NTT DOCOMO, AT&T |
| TDoc | Title | Source |
|---|---|---|
| R1-2205784 | Rel-17 UE features for enhanced IIoT/URLLC | Huawei, HiSilicon |
| R1-2205956 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2206307 | Discussion on UE features for IIoT and URLLC | OPPO |
| R1-2206766 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2207210 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| R1-2207388 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2207581 | On UE features for enhanced IIoT and URLLC | Nokia, Nokia Shanghai Bell |
| R1-2207701 | Summary on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2207936 | Summary#2 on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2208114 | Summary#3 on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205778 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2205957 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2206566 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2206612 | Discussion on UE features for NR coverage enhancement | Xiaomi |
| R1-2206685 | Remaining issues on UE features for Rel-17 NR coverage enhancements | China Telecom |
| R1-2206767 | Remaining issues on UE features for NR coverage enhancement | vivo |
| R1-2206808 | UE features for NR coverage enhancement | Samsung |
| R1-2206892 | Maintenance on Rel.17 UE features for NR coverage enhancement | CMCC |
| R1-2207017 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| R1-2207162 | UE Features for NR Coverage Enhancement | Ericsson |
| R1-2207211 | UE features for NR coverage enhancement | Qualcomm Incorporated |
| R1-2207316 | On Rel-17 NR coverage enhancement UE Features | Apple |
| R1-2207389 | Discussion on remaining issues in RAN1 UE features for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2207582 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2207702 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2207937 | Summary#2 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2208115 | Summary#3 on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205767 | Remaining issues on UE feature for sidelink | Huawei, HiSilicon |
| R1-2205849 | Discussion on UE features for NR sidelink enhancement | LG Electronics |
| R1-2206156 | On UE features for NR sidelink enhancement | ZTE,Sanechips |
| R1-2206284 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2206335 | On the pre-requisites for Rel-17 SL feature groups | FUTUREWEI |
| R1-2206373 | Remaining issues on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2206768 | Remaining issues on UE features for NR sidelink enhancement | vivo |
| R1-2207212 | UE features for NR sidelink enhancements | Qualcomm Incorporated |
| R1-2207317 | On Rel-17 NR Sidelink UE Features | Apple |
| R1-2207390 | Discussion on Rel.17 UE features for NR sidelink enhancement | NTT DOCOMO, INC. |
| R1-2207564 | UE features for NR sidelink enhancements | Ericsson |
| R1-2207703 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2207938 | Summary#2 on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205758 | Rel-17 UE features for NR MBS | Huawei, HiSilicon |
| R1-2205958 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2205979 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2206286 | Discussion on UE features for NR MBS | OPPO |
| R1-2206613 | Discussion on UE features for NR MBS | Xiaomi |
| R1-2206769 | UE features for NR MBS | vivo |
| R1-2207014 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2207213 | UE features for Rel-17 NR MBS | Qualcomm Incorporated |
| R1-2207318 | On Rel-17 NR MBS UE Features | Apple |
| R1-2207391 | Discussion on Rel.17 UE features for NR MBS | NTT DOCOMO, INC. |
| R1-2207583 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2207617 | Views on NR MBS UE features | Ericsson |
| R1-2207704 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2207939 | Summary#2 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2208116 | Summary#3 on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205787 | On UE features for other Rel-17 work items | Huawei, HiSilicon |
| R1-2205914 | Discussion on some remaining issues of Rel-17 UE features | ZTE |
| R1-2206567 | Discussion on remaining issues for Rel-17 UE capability | Intel Corporation |
| R1-2206770 | Other remaining issues for Rel-17 UE features (RedCap, B52.6GHz) | vivo |
| R1-2206809 | Views on UE features for Rel-17 NR FeMIMO | Samsung |
| R1-2206856 | Discussion on UE features for NTN-IoT | OPPO |
| R1-2206893 | Discussion on UE features for RedCap | CMCC |
| R1-2207001 | Remaining issues on R17 UE features | MediaTek Inc. |
| R1-2207035 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2207214 | Other Rel-17 UE features | Qualcomm Incorporated |
| R1-2207319 | View on Rel-17 UE features | Apple |
| R1-2207392 | Discussion on remaining issues in RAN1 UE features list for Rel-17 NR | NTT DOCOMO, INC. |
| R1-2207576 | UE features on Rel-17 Work Items under Agenda Item "Others" | Ericsson |
| R1-2207584 | On UE features for miscellaneous topics | Nokia, Nokia Shanghai Bell |
| R1-2207705 | Summary on UE features for NR RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2207706 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2207707 | Summary on UE features for NB-IoT and LTE-MTC enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2207708 | Summary on UE features for TEI17 | Moderator (NTT DOCOMO, INC.) |
| R1-2207920 | Summary of UE features for NR_FeMIMO, NR_ext_to_71GHz, NR_NTN_solutions, IoT over NTN, NR_IAB_enh, NR_DSS, LTE_NR_DC_enh2, NR_pos_enh, and NR_DL1024QAM_FR1 | Moderator (AT&T) |
| R1-2208117 | Summary#2 on UE features for NR redcap | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205771 | Discussion on remaining issues for supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2205800 | Remaining issues on PUCCH feedback during SDT procedure | Huawei, HiSilicon |
| R1-2205801 | Correction on uplink suspension for CA-based SRS carrier switching | Huawei, HiSilicon |
| R1-2205980 | Remaining issues on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2206090 | Correction on small data transmission in TS 38.213 | ZTE, Sanechips |
| R1-2206109 | Collison of PUCCH and PUSCH for SDT | Sony |
| R1-2206262 | Correction on UL Tx switching | OPPO |
| R1-2206568 | Correction on CG-SDT search space | Intel Corporation |
| R1-2206569 | Correction on CG-PUSCH repetitions for CG-SDT operation | Intel Corporation |
| R1-2206614 | Discussion on physical layer aspects of small data transmission | Xiaomi |
| R1-2206771 | Remaining issues for NR small data transmissions in RRC INACTIVE state | vivo |
| R1-2206772 | Corrections of random-access based small data transmission | vivo |
| R1-2206773 | Corrections of reduncancy version for SDT | vivo |
| R1-2206774 | Corrections of search space for SDT | vivo |
| R1-2206853 | Correction on CG-SDT parameters | InterDigital, Inc. |
| R1-2207525 | Correction on MsgA PUSCH occasion validation for 2-step RACH | Huawei, HiSilicon |
| R1-2207637 | Remaining issues on paging monitoring and measurement during SDT procedure | Huawei, HiSilicon |
| R1-2207647 | Correction on uplink suspension for CA-based SRS carrier switching | Huawei, HiSilicon |
| R1-2207648 | Correction on back-to-back switching with SRS switching | Huawei, HiSilicon |
| R1-2207655 | Correction on PRACH configurations for SDT | Huawei, HiSilicon |
| R1-2207764 | FL summary of discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2207819 | Summary on remaining physical layer issues of small data transmission | Moderator (ZTE) |
| R1-2208035 | [Draft] Reply LS on common search space for small data transmission | Moderator (ZTE) |
| R1-2208036 | Summary#2 on remaining physical layer issues of small data transmission | Moderator (ZTE) |
| R1-2208038 | Corrections of redundancy version for SDT | Moderator (ZTE), vivo |
| R1-2208070 | Correction on uplink suspension for CA-based SRS carrier switching | Moderator (China Telecom), Huawei, HiSilicon, ZTE |
| R1-2208107 | Reply LS on common search space for small data transmission | RAN1, ZTE |
| R1-2208108 | Summary#3 on remaining physical layer issues of small data transmission | Moderator (ZTE) |
| R1-2208229 | FL summary#2 of discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2208233 | [Draft] Corrections of random-access based small data transmission | Moderator (ZTE) |
| R1-2208234 | Corrections of random-access based small data transmission | Moderator (ZTE), vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2206963 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
| TDoc | Title | Source |
|---|---|---|
| R1-2205747 | Unified TCI framework extension for multi-TRP | FUTUREWEI |
| R1-2205816 | Discussion on Unified TCI Extension for MTRP | InterDigital, Inc. |
| R1-2205825 | Discussion on unified TCI framework extension for multi-TRP operation | TCL Communication Ltd. |
| R1-2205879 | Discussion on unified TCI framework extension for multi-TRP | Huawei, HiSilicon |
| R1-2205918 | Enhancements on unified TCI framework extension for multi-TRP | ZTE |
| R1-2205981 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
| R1-2206024 | Discussion on unified TCI framework extension for multi-TRP | vivo |
| R1-2206110 | Considerations on unified TCI framework for multi-TRP | Sony |
| R1-2206161 | Discussion on unified TCI extension for mTRP | Fujitsu |
| R1-2206209 | Discussion of unified TCI framework for multi-TRP | Lenovo |
| R1-2206246 | Unified TCI framework extension for multi-TRP | Ericsson |
| R1-2206263 | Unified TCI framework extension for multi-TRP | OPPO |
| R1-2206375 | Discussion on unified TCI framework extension for multi-TRP operation | CATT |
| R1-2206463 | Discussion on unified TCI framework extension for multi-TRP | NEC |
| R1-2206484 | Discussion on unified TCI framework extension for multi-TRP | |
| R1-2206570 | Unified TCI framework for mTRP | Intel Corporation |
| R1-2206620 | Unified TCI framework extension for multi-TRP | Xiaomi |
| R1-2206667 | Enhancement on unified TCI framework for multi-TRP | Transsion Holdings |
| R1-2206810 | Views on unified TCI extension focusing on m-TRP | Samsung |
| R1-2206866 | Unified TCI framework extension for multi-TRP/panel | LG Electronics |
| R1-2206894 | Discussion on unified TCI framework extension for multi-TRP | CMCC |
| R1-2206975 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
| R1-2206995 | Unified TCI framework extension for multi-TRP | MediaTek Inc. |
| R1-2207065 | Discussion on Unified TCI framework extension for multi-TRP | CEWiT |
| R1-2207096 | Discussion on unified TCI framework extension for multi-TRP | FGI |
| R1-2207215 | Extension of unified TCI framework for mTRP | Qualcomm Incorporated |
| R1-2207265 | Unified TCI framework extension for multi-TRP | Panasonic |
| R1-2207320 | Unified TCI framework extension for multi-TRP | Apple |
| R1-2207393 | Discussion on unified TCI framework extension for multi-TRP | NTT DOCOMO, INC. |
| R1-2207444 | Discussion on unified TCI framework extension for multi-TRP | ITRI |
| R1-2207450 | Unified TCI framework extension for multi-TRP | Sharp |
| R1-2207544 | Unified TCI framework extension for multi-TRP | Nokia, Nokia Shanghai Bell |
| R1-2207735 | Moderator summary on extension of unified TCI framework (Round 0) | Moderator (MediaTek Inc.) |
| R1-2207928 | Moderator summary on extension of unified TCI framework (Round 1) | Moderator (MediaTek Inc.) |
| R1-2208075 | Moderator summary on extension of unified TCI framework (Round 2) | Moderator (MediaTek Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205748 | Enhancements to support two TAs for multi-DCI | FUTUREWEI |
| R1-2205817 | On Utilization of Multiple TA | InterDigital, Inc. |
| R1-2205823 | Discussion on two TAs for multi-DCI based on multi-TRP operation | TCL Communication Ltd. |
| R1-2205880 | Study on TA enhancement for UL M-TRP transmssion | Huawei, HiSilicon |
| R1-2205919 | TA enhancement for multi-DCI | ZTE |
| R1-2205982 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
| R1-2206025 | Discussion on two TAs for multi-DCI-based multi-TRP operation | vivo |
| R1-2206210 | Discussion of two TAs for multi-DCI UL transmission | Lenovo |
| R1-2206247 | Two TAs for multi-DCI | Ericsson |
| R1-2206264 | Two TAs for multi-DCI | OPPO |
| R1-2206376 | Discussion on two TAs for UL multi-DCI for multi-TRP operation | CATT |
| R1-2206464 | Discussion on two TAs for multi-DCI | NEC |
| R1-2206485 | Discussion on two TAs for multi-DCI | |
| R1-2206571 | On two TAs for multi-DCI | Intel Corporation |
| R1-2206621 | Discussion on two TAs for multi-TRP operation | Xiaomi |
| R1-2206668 | Discussion on TA enhancement for multi-DCI based multi-TRP operation | Transsion Holdings |
| R1-2206811 | Views on two TAs for m-DCI | Samsung |
| R1-2206867 | Two TAs for multi-TRP/panel | LG Electronics |
| R1-2206895 | Discussion on two TAs for multi-DCI | CMCC |
| R1-2206996 | UL Tx Timing Management for MTRP Operation | MediaTek Inc. |
| R1-2207216 | Supporting two TAs for multi-DCI based mTRP | Qualcomm Incorporated |
| R1-2207321 | Views on two TAs for multi-DCI Uplink Transmissions | Apple |
| R1-2207394 | Discussion on two TAs for multi-DCI | NTT DOCOMO, INC. |
| R1-2207451 | Two TAs for multi-DCI | Sharp |
| R1-2207545 | Two TAs for UL multi-DCI multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2207800 | Moderator Summary on Two TAs for multi-DCI | Moderator (Ericsson) |
| R1-2208016 | Moderator Summary #2 on Two TAs for multi-DCI | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205818 | CSI Enhancements for CJT and High Doppler Operations | InterDigital, Inc. |
| R1-2205881 | CSI enhancement for coherent JT and mobility | Huawei, HiSilicon |
| R1-2205920 | CSI enhancement for high/medium UE velocities and CJT | ZTE |
| R1-2205983 | Discussion on CSI enhancement for high/medium UE velocities and coherent JT | Spreadtrum Communications |
| R1-2206026 | Discussion on CSI enhancement for high-medium UE velocities and coherent JT | vivo |
| R1-2206101 | Discussion on CSI enhancement | Mavenir |
| R1-2206189 | On CSI Enhancement | |
| R1-2206211 | Discussion of CSI enhancement for high speed UE and coherent JT | Lenovo |
| R1-2206265 | CSI enhancement for high/medium UE velocities and coherent JT | OPPO |
| R1-2206377 | On Rel-18 CSI enhancements for high/medium UE velocities and coherent JT | CATT |
| R1-2206459 | Discussion on CSI enhancement | NEC |
| R1-2206572 | On CSI enhancements | Intel Corporation |
| R1-2206622 | Discussion on CSI enhancements | Xiaomi |
| R1-2206783 | Moderator Summary of Tuesday Offline Session on Rel-18 CSI enhancements | Moderator (Samsung) |
| R1-2206812 | Moderator summary on Rel-18 CSI enhancements | Moderator (Samsung) |
| R1-2206813 | Summary of OFFLINE discussion on Rel-18 MIMO CSI | Moderator (Samsung) |
| R1-2206814 | Views on CSI enhancements | Samsung |
| R1-2206868 | Potential CSI enhancement for high/medium UE velocities and coherent JT | LG Electronics |
| R1-2206896 | Discussion on CSI enhancement for high/medium UE velocities and CJT | CMCC |
| R1-2206974 | CSI enhancements for medium UE velocities and coherent JT | Fraunhofer IIS, Fraunhofer HHI |
| R1-2206992 | CSI enhancement | MediaTek Inc. |
| R1-2207066 | Discussion on CSI Enhancements for high/medium UE velocities and coherent JT | CEWiT |
| R1-2207217 | CSI enhancements for high/medium UE velocities and Coherent-JT | Qualcomm Incorporated |
| R1-2207322 | Views on Rel-18 MIMO CSI enhancement | Apple |
| R1-2207369 | CSI Enhancements for CJT | AT&T |
| R1-2207395 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
| R1-2207452 | CSI enhancement | Sharp |
| R1-2207505 | On CSI enhancements for Rel-18 NR MIMO evolution | Ericsson |
| R1-2207546 | CSI enhancement for high/medium UE velocities and CJT | Nokia, Nokia Shanghai Bell |
| R1-2207603 | Additional considerations on CSI enhancement for high/medium UE velocities and coherent JT (CJT) | Sony |
| R1-2207876 | Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 | Moderator (Samsung) |
| R1-2207978 | Moderator Summary#3 on Rel-18 CSI enhancements: Round 2 | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205749 | On increasing the number of orthogonal DM-RS ports for MU-MIMO | FUTUREWEI |
| R1-2205819 | Enhanced Capacity DMRS | InterDigital, Inc. |
| R1-2205882 | Enhancements on DMRS in Rel-18 | Huawei, HiSilicon |
| R1-2205921 | DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO | ZTE |
| R1-2205984 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
| R1-2206027 | Discussion on DMRS enhancements | vivo |
| R1-2206106 | Discussions on increased number of orthogonal DMRS ports | New H3C Technologies Co., Ltd. |
| R1-2206190 | On DMRS Enhancement | |
| R1-2206212 | Discussion of increased number of orthogonal DMRS ports | Lenovo |
| R1-2206266 | DMRS enhancement for Rel-18 MIMO | OPPO |
| R1-2206378 | On DMRS enhancements | CATT |
| R1-2206460 | Discussion on increased number of orthogonal DMRS ports | NEC |
| R1-2206573 | Discussion on DMRS enhancement | Intel Corporation |
| R1-2206623 | Discussion on DMRS enhancement | Xiaomi |
| R1-2206815 | Views on DMRS enhancements | Samsung |
| R1-2206869 | Increased number of orthogonal DMRS ports | LG Electronics |
| R1-2206897 | Discussion on increased number of orthogonal DMRS ports | CMCC |
| R1-2206966 | Increased number of orthogonal DMRS ports | Fraunhofer IIS, Fraunhofer HHI |
| R1-2206993 | Increased number of orthogonal DMRS ports | MediaTek Inc. |
| R1-2207135 | On DMRS enhancement in Rel-18 | Ericsson |
| R1-2207218 | Design for increased number of orthogonal DMRS ports | Qualcomm Incorporated |
| R1-2207323 | Views on supporting increased number of orthogonal DMRS ports | Apple |
| R1-2207396 | Discussion on DMRS enhancements | NTT DOCOMO, INC. |
| R1-2207453 | Increased number of orthogonal DMRS ports | Sharp |
| R1-2207547 | Rel-18 UL and DL DMRS Enhancements | Nokia, Nokia Shanghai Bell |
| R1-2207715 | FL summary on DMRS#1 | Moderator (NTT DOCOMO) |
| R1-2207716 | FL summary on DMRS#2 | Moderator (NTT DOCOMO) |
| R1-2208005 | FL summary#3 on DMRS | Moderator (NTT DOCOMO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205750 | SRS enhancements for TDD CJT and 8TX operation | FUTUREWEI |
| R1-2205820 | On SRS Enhancements for CJT and 8TX UEs | InterDigital, Inc. |
| R1-2205883 | SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 | Huawei, HiSilicon, LG Uplus |
| R1-2205922 | SRS enhancement targeting TDD CJT and 8 TX operation | ZTE |
| R1-2205985 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
| R1-2206028 | Discussion on SRS enhancement | vivo |
| R1-2206191 | On SRS Enhancement | |
| R1-2206213 | Discussion of SRS enhancement | Lenovo |
| R1-2206267 | SRS enhancement targeting TDD CJT and 8 TX operation | OPPO |
| R1-2206379 | On SRS enhancement for R18 | CATT |
| R1-2206419 | Views on SRS configuration targeting TDD CJT and 8 TX operation | KDDI Corporation |
| R1-2206461 | Discussion on SRS enhancement | NEC |
| R1-2206574 | Discussion on SRS enhancement in Rel-18 | Intel Corporation |
| R1-2206624 | Discussion on SRS enhancements | Xiaomi |
| R1-2206816 | Views on SRS enhancements | Samsung |
| R1-2206870 | SRS enhancement targeting TDD CJT and 8 TX operation | LG Electronics |
| R1-2206898 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | CMCC |
| R1-2207067 | Discussion on SRS Enhancements for 8Tx Operation | CEWiT |
| R1-2207219 | SRS enhancement for TDD CJT and 8 Tx operation | Qualcomm Incorporated |
| R1-2207324 | Views on Rel-18 MIMO SRS enhancement | Apple |
| R1-2207397 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2207454 | SRS enhancement targeting TDD CJT and 8 TX operation | Sharp |
| R1-2207499 | On SRS enhancements targeting TDD CJT and 8 TX operation | Ericsson |
| R1-2207548 | SRS enhancement for TDD CJT and 8Tx operation | Nokia, Nokia Shanghai Bell |
| R1-2207604 | Considerations on precoded SRS | Sony |
| R1-2207855 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2207856 | FL Summary #2 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2208014 | FL Summary #3 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2208015 | FL Summary #4 on SRS enhancements | Moderator (FUTUREWEI) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205821 | Discussion on Uplink Multi-panel Transmission | InterDigital, Inc. |
| R1-2205884 | Discussion on UL precoding indication for multi-panel transmission | Huawei, HiSilicon |
| R1-2205923 | Enhancements on UL precoding indication for multi-panel transmission | ZTE |
| R1-2205986 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
| R1-2206029 | Discussion on UL precoding indication for multi-panel transmission | vivo |
| R1-2206111 | Considerations on UL for multi-panel transmission | Sony |
| R1-2206162 | Discussion on UL precoding indication for multi-panel transmission | Fujitsu |
| R1-2206192 | On Simultaneous Multi-Panel Transmission | |
| R1-2206214 | UL precoding indication for multi-panel transmission | Lenovo |
| R1-2206268 | Transmission scheme and UL precoding indicaton for multi-panel transmission | OPPO |
| R1-2206380 | Discussion on UL precoding indication for multi-panel transmission | CATT |
| R1-2206465 | Discussion on UL precoding indication for multi-panel transmission | NEC |
| R1-2206575 | UL precoding indication for multi-panel transmission (STxMP) | Intel Corporation |
| R1-2206625 | Enhancements on multi-panel uplink transmission | Xiaomi |
| R1-2206817 | Views on UL precoding indication for STxMP | Samsung |
| R1-2206871 | UL precoding indication for multi-panel transmission | LG Electronics |
| R1-2206899 | Discussion on UL precoding indication for multi-panel transmission | CMCC |
| R1-2206997 | Simultaneous transmission across multiple UE panels | MediaTek Inc. |
| R1-2207112 | UL precoding indication for multi-panel transmission | Ericsson |
| R1-2207145 | On UL precoding indication for simultaneous multi-panel transmission | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207220 | Simultaneous multi-panel transmission | Qualcomm Incorporated |
| R1-2207325 | Views on UL precoding indication for multi-panel simultaneous PUSCH transmissions | Apple |
| R1-2207398 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
| R1-2207455 | Views on UL multi-panel transmission | Sharp |
| R1-2207549 | Precoder Indication for Multi-Panel UL Transmission | Nokia, Nokia Shanghai Bell |
| R1-2207693 | UL precoding indication for multi-panel transmission | LG Electronics |
| R1-2207698 | Summary #1 on Rel-18 STxMP | Moderator (OPPO) |
| R1-2207699 | Summary #2 on Rel-18 STxMP | Moderator (OPPO) |
| R1-2207700 | Summary #3 on Rel-18 STxMP | Moderator (OPPO) |
| R1-2207761 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
| TDoc | Title | Source |
|---|---|---|
| R1-2205822 | SRI/TPMI Enhancement for 8TX UE | InterDigital, Inc. |
| R1-2205885 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
| R1-2205924 | SRI/TPMI enhancement for enabling 8 TX UL transmission | ZTE |
| R1-2205987 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
| R1-2206030 | Discussion on enabling 8 TX UL transmission | vivo |
| R1-2206112 | Discussion on enhancement for 8Tx UL transmission | Sony |
| R1-2206193 | On SRI/TPMI Indication for 8Tx Transmission | |
| R1-2206215 | SRI/TPMI enhancement for enabling 8TX UL transmission | Lenovo |
| R1-2206269 | SRI TPMI enhancement for 8 TX UL transmission | OPPO |
| R1-2206381 | On codebook and SRI/TPMI enhancement for UL 8 TX | CATT |
| R1-2206462 | Discussion on SRI/TPMI enhancement | NEC |
| R1-2206576 | Discussion on enhancement for 8Tx UL transmission | Intel Corporation |
| R1-2206626 | Enhancements on 8Tx uplink transmission | Xiaomi |
| R1-2206818 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
| R1-2206872 | SRI/TPMI enhancement for enabling 8 TX UL transmission | LG Electronics |
| R1-2206900 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | CMCC |
| R1-2206994 | SRI/TPMI enhancement for enabling 8 TT UL transmission | MediaTek Inc. |
| R1-2207163 | SRI/TPMI Enhancement for Enabling 8 TX UL Transmission | Ericsson |
| R1-2207221 | Enhancements for 8 Tx UL transmissions | Qualcomm Incorporated |
| R1-2207326 | Views on SRI/TPMI enhancement for enabling 8 TX UL transmission | Apple |
| R1-2207399 | Discussion on 8 TX UL transmission | NTT DOCOMO, INC. |
| R1-2207456 | Views on 8 TX UL transmission | Sharp |
| R1-2207550 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
| R1-2207725 | FL Summary on SRI/TPMI Enhancements; First Round | Moderator (InterDigital) |
| R1-2207726 | FL Summary on SRI/TPMI Enhancements; Second Round | Moderator (InterDigital) |
| R1-2208012 | FL Summary on SRI/TPMI Enhancements; Third Round | Moderator (InterDigital) |
| R1-2208013 | Recommended Direction on SRI/TPMI Enhancements for RAN1#110b-e | Moderator (InterDigital) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207222 | Technical report for Rel-18 SI on AI and ML for NR air interface | Qualcomm Incorporated |
| R1-2208145 | 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-2205752 | Continued discussion on common AI/ML characteristics and operations | FUTUREWEI |
| R1-2205830 | General aspects of dataset construction | Keysight Technologies UK Ltd |
| R1-2205889 | Discussion on general aspects of AI/ML framework | Huawei, HiSilicon |
| R1-2205966 | Discussions on Common Aspects of AI/ML Framework | TCL Communication |
| R1-2206031 | Discussions on AI/ML framework | vivo |
| R1-2206067 | Discussion on general aspects of common AI PHY framework | ZTE |
| R1-2206113 | Considerations on common AI/ML framework | Sony |
| R1-2206163 | Discussion on general aspects of AI/ML framework | Fujitsu |
| R1-2206194 | On General Aspects of AI/ML Framework | |
| R1-2206314 | On general aspects of AI/ML framework | OPPO |
| R1-2206390 | AI/ML framework for air interface | CATT |
| R1-2206466 | Discussion on general aspects of AI ML framework | NEC |
| R1-2206507 | General aspects of AI and ML framework for NR air interface | NVIDIA |
| R1-2206509 | General aspects of AI/ML framework | Lenovo |
| R1-2206577 | General aspects of AI/ML framework | Intel Corporation |
| R1-2206603 | Discussion on general aspects of AIML framework | Spreadtrum Communications |
| R1-2206634 | Views on the general aspects of AL/ML framework | Xiaomi |
| R1-2206674 | Considerations on general aspects on AI-ML framework | CAICT |
| R1-2206686 | Discussion on general aspects of AI/ML for NR air interface | China Telecom |
| R1-2206819 | General aspects of AI ML framework and evaluation methodogy | Samsung |
| R1-2206873 | General aspects on AI/ML framework | LG Electronics |
| R1-2206885 | Discussion on general aspects of AI/ML framework | Ericsson |
| R1-2206901 | Discussion on general aspects of AI/ML framework | CMCC |
| R1-2206952 | Discussion on general aspects of AI/ML framework for NR air interface | ETRI |
| R1-2206967 | Further discussion on the general aspects of ML for Air-interface | Nokia, Nokia Shanghai Bell |
| R1-2206987 | General aspects of AI/ML framework | MediaTek Inc. |
| R1-2207117 | Discussion on AI/ML Model Life Cycle Management | Rakuten Mobile Inc. |
| R1-2207223 | General aspects of AI/ML framework | Qualcomm Incorporated |
| R1-2207293 | Discussion on general aspects of AI/ML framework | Panasonic |
| R1-2207327 | General aspect of AI/ML framework | Apple |
| R1-2207400 | Discussion on general aspects of AI/ML framework | NTT DOCOMO, INC. |
| R1-2207457 | Observation of Channel Matrix | Sharp |
| R1-2207459 | Discussion on general aspects of AI/ML framework | KDDI Corporation |
| R1-2207879 | Summary#1 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| R1-2207932 | Summary#2 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| R1-2208063 | Summary#3 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| R1-2208178 | Summary#4 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205824 | Evaluation on AI/ML for CSI feedback enhancement in spatial-frequency-time domain | SEU |
| R1-2205890 | Evaluation on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2206032 | Evaluation on AI/ML for CSI feedback enhancement | vivo |
| R1-2206068 | Evaluation on AI for CSI feedback enhancement | ZTE |
| R1-2206164 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu |
| R1-2206195 | On Evaluation of AI/ML based CSI | |
| R1-2206315 | Evaluation methodology and preliminary results on AI/ML for CSI feedback enhancement | OPPO |
| R1-2206334 | Evaluation on AI/ML-based CSI feedback enhancement | BJTU |
| R1-2206336 | Continued discussion on evaluation of AI/ML for CSI feedback enhancement | FUTUREWEI |
| R1-2206391 | Evaluation on AI/ML for CSI feedback | CATT |
| R1-2206510 | Evaluation on AI/ML for CSI feedback | Lenovo |
| R1-2206520 | Evaluation of AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2206578 | Evaluation for CSI feedback enhancements | Intel Corporation |
| R1-2206604 | Discussion on evaluation on AIML for CSI feedback enhancement | Spreadtrum Communications, BUPT |
| R1-2206635 | Discussion on evaluation on AI/ML for CSI feedback enhancement | Xiaomi |
| R1-2206675 | Some discussions on evaluation on AI-ML for CSI feedback | CAICT |
| R1-2206820 | Evaluation on AI ML for CSI feedback enhancement | Samsung |
| R1-2206874 | Evaluation on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2206883 | Evaluations of AI-CSI | Ericsson |
| R1-2206902 | Discussion on evaluation on AI/ML for CSI feedback enhancement | CMCC |
| R1-2206953 | Evaluation on AI/ML for CSI feedback enhancement | ETRI |
| R1-2206968 | Evaluation of ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2206988 | Evaluation on AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2207063 | On evaluation of AI/ML based methods for CSI feedback enhancement | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207081 | Views on Evaluation of AI/ML for CSI Feedback Enhancement | Mavenir |
| R1-2207152 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2207224 | Evaluation on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2207328 | Evaluation on AI/ML for CSI feedback | Apple |
| R1-2207401 | Discussion on evaluation on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2207475 | Evaluation on AI/ML for CSI feedback enhancement in spatial-frequency-time domain | SEU |
| R1-2207720 | Evaluations of AI-CSI | Ericsson |
| R1-2207836 | Summary#1 for CSI evaluation of [110-R18-AI/ML] | Moderator (Huawei) |
| R1-2207837 | Summary#2 for CSI evaluation of [110-R18-AI/ML] | Moderator (Huawei) |
| R1-2207838 | Summary#3 for CSI evaluation of [110-R18-AI/ML] | Moderator (Huawei) |
| R1-2207839 | Summary#4 for CSI evaluation of [110-R18-AI/ML] | Moderator (Huawei) |
| R1-2207840 | Summary#5 for CSI evaluation of [110-R18-AI/ML] | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205891 | Discussion on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2205967 | Discussions on Sub-Use Cases in AI/ML for CSI Feedback Enhancement | TCL Communication |
| R1-2206033 | Other aspects on AI/ML for CSI feedback enhancement | vivo |
| R1-2206069 | Discussion on other aspects for AI CSI feedback enhancement | ZTE |
| R1-2206114 | Considerations on CSI measurement enhancements via AI/ML | Sony |
| R1-2206165 | Discussion on other aspects of AI/ML for CSI feedback enhancement | Fujitsu |
| R1-2206185 | Discussion on AI/ML for CSI feedback enhancement | Panasonic |
| R1-2206196 | On Enhancement of AI/ML based CSI | |
| R1-2206241 | Discussion on AI/ML for CSI feedback enhancement | NEC |
| R1-2206316 | On sub use cases and other aspects of AI/ML for CSI feedback enhancement | OPPO |
| R1-2206337 | Continued discussion on other aspects of AI/ML for CSI feedback enhancement | FUTUREWEI |
| R1-2206392 | Other aspects on AI/ML for CSI feedback | CATT |
| R1-2206511 | Further aspects of AI/ML for CSI feedback | Lenovo |
| R1-2206521 | AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2206579 | Use-cases and specification for CSI feedback | Intel Corporation |
| R1-2206605 | Discussion on other aspects on AIML for CSI feedback | Spreadtrum Communications |
| R1-2206636 | Discussion on potential specification impact for CSI feedback based on AI/ML | Xiaomi |
| R1-2206676 | Discussions on AI-ML for CSI feedback | CAICT |
| R1-2206687 | Discussion on AI/ML for CSI feedback enhancement | China Telecom |
| R1-2206821 | Representative sub use cases for CSI feedback enhancement | Samsung |
| R1-2206875 | Other aspects on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2206884 | Discussion on AI-CSI | Ericsson |
| R1-2206903 | Discussion on other aspects on AI/ML for CSI feedback enhancement | CMCC |
| R1-2206954 | Discussion on other aspects on AI/ML for CSI feedback enhancement | ETRI |
| R1-2206969 | Other aspects on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2206989 | Other aspects on AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2207153 | Discussion on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2207225 | Other aspects on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2207329 | Other aspects on AI/ML for CSI | Apple |
| R1-2207370 | Sub-use cases for AI/ML feedback enhancements | AT&T |
| R1-2207402 | Discussion on other aspects on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2207780 | Summary #1 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2207853 | Summary #2 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2207854 | Summary #3 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2208077 | Summary #4 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205753 | Continued discussion on evaluation of AI/ML for beam management | FUTUREWEI |
| R1-2205892 | Evaluation on AI/ML for beam management | Huawei, HiSilicon |
| R1-2206034 | Evaluation on AI/ML for beam management | vivo |
| R1-2206070 | Evaluation on AI for beam management | ZTE |
| R1-2206166 | Evaluation on AI/ML for beam management | Fujitsu |
| R1-2206181 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
| R1-2206197 | On Evaluation of AI/ML based Beam Management | |
| R1-2206250 | Evaluation of AI/ML based beam management | Rakuten Symphony |
| R1-2206317 | Evaluation methodology and preliminary results on AI/ML for beam management | OPPO |
| R1-2206393 | Evaluation on AI/ML for beam management | CATT |
| R1-2206512 | Evaluation on AI/ML for beam management | Lenovo |
| R1-2206522 | Evaluation of AI and ML for beam management | NVIDIA |
| R1-2206580 | Evaluation for beam management | Intel Corporation |
| R1-2206637 | Evaluation on AI/ML for beam management | Xiaomi |
| R1-2206677 | Some discussions on evaluation on AI-ML for Beam management | CAICT |
| R1-2206688 | Evaluation on AI/ML for beam management | China Telecom |
| R1-2206822 | Evaluation on AI ML for Beam management | Samsung |
| R1-2206876 | Evaluation on AI/ML for beam management | LG Electronics |
| R1-2206904 | Discussion on evaluation on AI/ML for beam management | CMCC |
| R1-2206938 | Evaluation on AI/ML for beam management | Ericsson |
| R1-2206970 | Evaluation of ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2206990 | Evaluation on AI/ML for beam management | MediaTek Inc. |
| R1-2207068 | Evaluation on AI/ML for beam management | CEWiT |
| R1-2207226 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
| R1-2207330 | Evaluation on AI/ML for beam management | Apple |
| R1-2207403 | Discussion on evaluation on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2207774 | Feature lead summary #1 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2207775 | Feature lead summary #2 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2207776 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2208104 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2208105 | Feature lead summary #4 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2208106 | Feature lead summary #5 evaluation of AI/ML for beam management | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205754 | Continued discussion on other aspects of AI/ML for beam management | FUTUREWEI |
| R1-2205893 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
| R1-2205968 | Discussions on Sub-Use Cases in AI/ML for Beam Management | TCL Communication |
| R1-2206035 | Other aspects on AI/ML for beam management | vivo |
| R1-2206071 | Discussion on other aspects for AI beam management | ZTE |
| R1-2206115 | Considerations on AI/ML for beam management | Sony |
| R1-2206167 | Sub use cases and specification impact on AI/ML for beam management | Fujitsu |
| R1-2206182 | Discussion for other aspects on AI/ML for beam management | InterDigital, Inc. |
| R1-2206198 | On Enhancement of AI/ML based Beam Management | |
| R1-2206251 | Other aspects on AI/ML for beam management | Rakuten Symphony |
| R1-2206318 | Other aspects of AI/ML for beam management | OPPO |
| R1-2206332 | Beam management with AI/ML in high-speed railway scenarios | BJTU |
| R1-2206394 | Other aspects on AI/ML for beam management | CATT |
| R1-2206472 | Discussion on AI/ML for beam management | NEC |
| R1-2206513 | Further aspects of AI/ML for beam management | Lenovo |
| R1-2206523 | AI and ML for beam management | NVIDIA |
| R1-2206581 | Use-cases and specification for beam management | Intel Corporation |
| R1-2206606 | Discussion on other aspects on AIML for beam management | Spreadtrum Communications |
| R1-2206638 | Discussion on other aspects on AI/ML for beam management | Xiaomi |
| R1-2206678 | Discussions on AI-ML for Beam management | CAICT |
| R1-2206823 | Representative sub use cases for beam management | Samsung |
| R1-2206877 | Other aspects on AI/ML for beam management | LG Electronics |
| R1-2206905 | Discussion on other aspects on AI/ML for beam management | CMCC |
| R1-2206940 | Discussion on AI/ML for beam management | Ericsson |
| R1-2206971 | Other aspects on ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2206991 | Other aspects on AI/ML for beam management | MediaTek Inc. |
| R1-2207227 | Other aspects on AI/ML for beam management | Qualcomm Incorporated |
| R1-2207331 | Other aspects on AI/ML for beam management | Apple |
| R1-2207404 | Discussion on other aspects on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2207506 | Discussion on sub use cases of AI/ML beam management | Panasonic |
| R1-2207551 | Discussion on Performance Related Aspects of Codebook Enhancement with AI/ML | Charter Communications, Inc |
| R1-2207590 | Discussion on other aspects on AI/ML for beam management | KT Corp. |
| R1-2207871 | Summary#1 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2207872 | Summary#2 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2207873 | Summary#3 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2207874 | Summary#4 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205894 | Evaluation on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2205915 | Evaluation on AI/ML for positioning accuracy enhancement | PML |
| R1-2206036 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
| R1-2206072 | Evaluation on AI for positioning enhancement | ZTE |
| R1-2206168 | Preliminary evaluation results and discussions of AI positioning accuracy enhancement | Fujitsu |
| R1-2206199 | On Evaluation of AI/ML based Positioning | |
| R1-2206224 | Evaluation method on AI/ML for positioning accuracy enhancement | PML |
| R1-2206248 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Ericsson |
| R1-2206252 | Evaluation on AI/ML for positioning accuracy enhancement | Rakuten Symphony |
| R1-2206319 | Evaluation methodology and preliminary results on AI/ML for positioning accuracy enhancement | OPPO |
| R1-2206395 | Evaluation on AI/ML for positioning | CATT |
| R1-2206514 | Discussion on AI/ML Positioning Evaluations | Lenovo |
| R1-2206524 | Evaluation of AI and ML for positioning enhancement | NVIDIA |
| R1-2206639 | Evaluation on AI/ML for positioning accuracy enhancement | Xiaomi |
| R1-2206679 | Some discussions on evaluation on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2206689 | Evaluation on AI/ML for positioning accuracy enhancement | China Telecom |
| R1-2206824 | Evaluation on AI ML for Positioning | Samsung |
| R1-2206878 | Evaluation on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2206906 | Discussion on evaluation on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2206972 | Evaluation of ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2207094 | Evaluation on AI/ML for positioning accuracy enhancement | InterDigital, Inc. |
| R1-2207123 | Evaluation on AI/ML for positioning accuracy enhancement | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207228 | Evaluation on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2207332 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
| R1-2207862 | Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2207863 | Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2207864 | Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2208160 | Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2208161 | Summary #5 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205895 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2206037 | Other aspects on AI/ML for positioning accuracy enhancement | vivo |
| R1-2206073 | Discussion on other aspects for AI positioning enhancement | ZTE |
| R1-2206116 | Considerations on AI/ML for positioning accuracy enhancement | Sony |
| R1-2206169 | Discussions on sub use cases and spec impacts for AIML for positioning accuracy enhancement | Fujitsu |
| R1-2206200 | On Enhancement of AI/ML based Positioning | |
| R1-2206249 | Other Aspects of AI/ML Based Positioning Enhancement | Ericsson |
| R1-2206253 | Other aspects on AI/ML based positioning | Rakuten Symphony |
| R1-2206320 | On sub use cases and other aspects of AI/ML for positioning accuracy enhancement | OPPO |
| R1-2206396 | Other aspects on AI/ML for positioning | CATT |
| R1-2206477 | Discussion on AI/ML for positioning accuracy enhancement | NEC |
| R1-2206515 | AI/ML Positioning use cases and Associated Impacts | Lenovo |
| R1-2206525 | AI and ML for positioning enhancement | NVIDIA |
| R1-2206607 | Discussion on other aspects on AIML for positioning accuracy enhancement | Spreadtrum Communications |
| R1-2206640 | Views on the other aspects of AI/ML-based positioning accuracy enhancement | Xiaomi |
| R1-2206680 | Discussions on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2206825 | Representative sub use cases for Positioning | Samsung |
| R1-2206879 | Other aspects on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2206907 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2206973 | Other aspects on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2207093 | Designs and potential specification impacts of AIML for positioning | InterDigital, Inc. |
| R1-2207122 | On potential specification impact of AI/ML for positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207229 | Other aspects on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2207333 | Other aspects on AI/ML for positioning accuracy enhancement | Apple |
| R1-2207754 | FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
| R1-2207880 | FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
| R1-2208049 | FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206908 | Updated work plan on Rel-18 evolution of NR duplex operation SI | CMCC, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2205810 | On deployment scenarios and evaluation methodology of NR full duplex | Dell Technologies |
| R1-2205814 | Evaluation methodolgy for NR duplex evolution | Kumu Networks |
| R1-2205842 | Proposing New Energy Consumption Metric for SBFD | VODAFONE Group Plc |
| R1-2205896 | Evolution of NR duplex operation | Huawei, HiSilicon |
| R1-2205936 | Discussion on evaluation methodology for NR-duplex | InterDigital, Inc. |
| R1-2205959 | Discussion of evaluation on NR duplex evolution | ZTE |
| R1-2205988 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications, BUPT |
| R1-2206038 | Evaluation on NR duplex evolution | vivo |
| R1-2206107 | Discussion for Evaluation on NR duplex evolution | New H3C Technologies Co., Ltd. |
| R1-2206237 | Evaluation of UE-UE CLI for NR SBFD operation | NEC |
| R1-2206321 | Discussion on evaluation on NR duplex evolution | OPPO |
| R1-2206397 | Discussion on evaluation on NR duplex evolution | CATT |
| R1-2206420 | Deployment scenario and evaluation methodology for NR duplex evolution | Samsung |
| R1-2206504 | Discussion on evaluation on NR duplex evolution | Sharp |
| R1-2206582 | Evaluation of NR duplex evolution | Intel Corporation |
| R1-2206641 | Discussion on evaluation on NR duplex evolution | Xiaomi |
| R1-2206857 | Discussion on guard band evaluation of NR duplex evolution | KT Corp. |
| R1-2206909 | Summary#1 of email discussion on evaluation of NR duplex evolution | Moderator (CMCC) |
| R1-2206910 | Discussion on evaluation on NR duplex evolution | CMCC |
| R1-2206983 | Deployment scenarios and evaluation methodology for NR duplex evolution | MediaTek Inc. |
| R1-2207230 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | Qualcomm Incorporated |
| R1-2207266 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2207334 | Initial evaluation on NR duplex evolution | Apple |
| R1-2207363 | Study on Evaluation for NR duplex evolution | LG Electronics |
| R1-2207405 | Discussion on evaluation on NR duplex evolution | NTT DOCOMO, INC. |
| R1-2207461 | Evaluation of NR duplex evolution | Ericsson |
| R1-2207571 | Proposing New Energy Consumption Metric for SBFD | Vodafone, China Telecom, Telecom Italia |
| R1-2207607 | Additional considerations for NR Duplex evolution | Charter Communications, Inc |
| R1-2207887 | Summary#2 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2207888 | Summary#3 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2208030 | Summary#4 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2208031 | Summary#5 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2208270 | Summary#6 on evaluation on NR duplex evolution | Moderator (CMCC) |
| R1-2208271 | Final summary on evaluation on NR duplex evolution | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205812 | Discussion on NR sub-band full duplex | Dell Technologies |
| R1-2205815 | RF cancellation techniques for subband non-overlapping full duplex | Kumu Networks |
| R1-2205834 | Discussion on Subband non-overlapping Full Duplex | TCL Communication Ltd. |
| R1-2205897 | Study on subband non-overlapping full duplex | Huawei, HiSilicon |
| R1-2205937 | Discussion on SBFD operations for NR-duplex | InterDigital, Inc. |
| R1-2205960 | Discussion of subband non-overlapping full duplex | ZTE |
| R1-2205989 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
| R1-2206039 | Discussion on subband non-overlapping full duplex | vivo |
| R1-2206108 | Discussion for subband non-overlapping full duplex | New H3C Technologies Co., Ltd. |
| R1-2206117 | Considerations on Subband Full Duplex TDD Operations | Sony |
| R1-2206170 | Views on Subband non-overlapping full duplex | Fujitsu |
| R1-2206235 | Discussion on subband non-overlapping full duplex | NEC |
| R1-2206322 | Discussion on subband non-overlapping full duplex | OPPO |
| R1-2206398 | Discussion on subband non-overlapping full duplex | CATT |
| R1-2206421 | SBFD feasibility and design considerations for NR duplex evolution | Samsung |
| R1-2206505 | Discussion on subband non-overlapping full duplex | Sharp |
| R1-2206516 | Subband non-overlapping full duplex | Lenovo |
| R1-2206583 | Potential solutions for SBFD in NR systems | Intel Corporation |
| R1-2206642 | Discussion on subband non-overlapping full duplex | Xiaomi |
| R1-2206690 | Discussion on subband non-overlapping full duplex | China Telecom |
| R1-2206911 | Discussion on subband non-overlapping full duplex | CMCC |
| R1-2206955 | Discussion on subband non-overlapping full duplex enhancements | ETRI |
| R1-2206984 | Discussion on subband non-overlapping full duplex for NR | MediaTek Inc. |
| R1-2207069 | Discussion on subband non-overlapping full duplex | CEWiT |
| R1-2207118 | Discussion on framework for interference mitigation | Rakuten Mobile Inc. |
| R1-2207231 | Feasibility and techniques for Subband non-overlapping full duplex | Qualcomm Incorporated |
| R1-2207261 | Discussion on subband non-overlapping full duplex | Panasonic |
| R1-2207267 | On subband non-overlapping full duplex for NR | Nokia, Nokia Shanghai Bell |
| R1-2207335 | Views on subband non-overlapping full duplex | Apple |
| R1-2207364 | Study on Subband non-overlapping full duplex | LG Electronics |
| R1-2207368 | Discussion on subband non-overlapping full duplex | KDDI Corporation |
| R1-2207406 | Discussion on subband non-overlapping full duplex | NTT DOCOMO, INC. |
| R1-2207445 | Discussion on sub-band non-overlapping full duplex | ITRI |
| R1-2207462 | Subband non-overlapping full duplex | Ericsson |
| R1-2207487 | Introduction of subband non-overlapping full duplex | ASUSTeK |
| R1-2207592 | Discussion on subband non-overlapping full duplex | KT Corp. |
| R1-2207598 | Discussion on subband non-overlapping full duplex | WILUS Inc. |
| R1-2207805 | Summary #1 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2207806 | Summary #2 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2207807 | Summary #3 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2207976 | Summary #4 of subband non-overlapping full duplex | Moderator (CATT) |
| R1-2208122 | Summary #5 of subband non-overlapping full duplex | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205835 | Potential enhancement on dynamic/flexible TDD | TCL Communication Ltd. |
| R1-2205898 | Study on potential enhancements on dynamic/flexible TDD | Huawei, HiSilicon |
| R1-2205938 | On potential enhancements of dynamic and flexible TDD | InterDigital, Inc. |
| R1-2205961 | Discussion of enhancements on dynamic/flexible TDD | ZTE |
| R1-2205990 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
| R1-2206040 | Potential enhancements on dynamic/flexible TDD | vivo |
| R1-2206118 | Considerations on Flexible/Dynamic TDD | Sony |
| R1-2206234 | Views on enhancements of dynamic/flexible TDD | NEC |
| R1-2206323 | Discussion on potential enhancements on dynamic/flexible TDD | OPPO |
| R1-2206399 | Discussion on potential enhancements on dynamic/flexible TDD | CATT |
| R1-2206422 | Dynamic and flexible TDD for NR duplex evolution | Samsung |
| R1-2206506 | Discussion on potential enhancement to dynamic TDD | Sharp |
| R1-2206584 | Potential enhancements to dynamic/flexible TDD | Intel Corporation |
| R1-2206643 | Discussion on potential enhancements on dynamic TDD | Xiaomi |
| R1-2206880 | Discussion for potential enhancement on dynamic/flexible TDD | New H3C Technologies Co., Ltd. |
| R1-2206912 | Discussion on potential enhancements on flexible/dynamic TDD | CMCC |
| R1-2206985 | Discussion on potential enhancements on dynamic/flexible TDD | MediaTek Inc. |
| R1-2207070 | Discussion on enhancements on dynamic/flexible TDD | CEWiT |
| R1-2207232 | On potential enhancements on dynamic/flexible TDD | Qualcomm Incorporated |
| R1-2207268 | Dynamic TDD enhancements | Nokia, Nokia Shanghai Bell |
| R1-2207336 | Views on potential enhancements on dynamic/flexible TDD | Apple |
| R1-2207365 | Study on Potential enhancements on dynamic/flexible TDD | LG Electronics |
| R1-2207407 | Discussion on potential enhancements on dynamic/flexible TDD | NTT DOCOMO, INC. |
| R1-2207463 | Flexible/dynamic TDD | Ericsson |
| R1-2207476 | Potential enhancements on dynamic/flexible TDD | Lenovo |
| R1-2207881 | Summary #1 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2207882 | Summary #2 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2207883 | Summary #3 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2207884 | Summary #4 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208146 | Session notes for 9.4 (NR sidelink evolution) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205744 | Channel access mechanism for sidelink operation in unlicensed spectrum | FUTUREWEI |
| R1-2205839 | On Channel Access Mechanism and Evaluation Methodology for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2205850 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | LG Electronics |
| R1-2205886 | Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2205991 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2206041 | Channel access mechanism for sidelink on unlicensed spectrum | vivo |
| R1-2206097 | Discussion on channel access mechanism for SL-U | ZTE,Sanechips |
| R1-2206119 | Discussion on channel access mechanism for SL-unlicensed | Sony |
| R1-2206171 | Discussion on channel access mechanism for SL-U | Fujitsu |
| R1-2206290 | Access mechanisms and resource allocation for NR sidelink in unlicensed channel | OPPO |
| R1-2206400 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2206438 | NR Sidelink Unlicensed Channel Access Mechanisms | Fraunhofer HHI, Fraunhofer IIS |
| R1-2206448 | Channel access mechanism for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2206469 | Channel Access of Sidelink on Unlicensed Spetrum | NEC |
| R1-2206585 | Channel Access Mechanisms for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2206644 | Discussion on channel access mechanism for sidelink-unlicensed | Xiaomi |
| R1-2206669 | Discussion of channel access mechanism for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2206691 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | China Telecom |
| R1-2206826 | On channel access mechanism for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2206860 | On Channel Access Mechanism for SL-U | ITL |
| R1-2206913 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CMCC |
| R1-2207015 | Discussion on channel access mechanism | MediaTek Inc. |
| R1-2207110 | Discussion of Channel Access Mechanisms | Johns Hopkins University APL |
| R1-2207128 | SL Channel access in unlicensed spectrum | InterDigital, Inc. |
| R1-2207136 | On Evaluation Methodology for SL-U | CableLabs |
| R1-2207233 | Channel Access Mechanism for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2207279 | Discussion on Channel access mechanism for NR sidelink evolution | Sharp |
| R1-2207298 | Sidelink channel access on unlicensed spectrum | Panasonic |
| R1-2207337 | Channel access mechanism for sidelink on FR1 unlicensed band | Apple |
| R1-2207408 | Discussion on channel access mechanism in SL-U | NTT DOCOMO, INC. |
| R1-2207504 | Discussion on sidelink on unlicensed spectrum | ASUSTeK |
| R1-2207511 | Discussions on channel access mechanism for sidelink on unlicensed spectrum | ROBERT BOSCH GmbH |
| R1-2207566 | Channel access mechanism for SL-U | Ericsson |
| R1-2207599 | Discussion on channel access mechanism for SL on unlicensed spectrum | WILUS Inc. |
| R1-2207709 | Discussion on channel access mechanism for SL-U | ZTE,Sanechips |
| R1-2207743 | On Evaluation Methodology for SL-U | CableLabs, Broadcom, Charter Communications |
| R1-2207789 | FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2207790 | FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2207791 | FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2207792 | FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2207793 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205745 | Physical channel design for sidelink operation in unlicensed spectrum | FUTUREWEI |
| R1-2205840 | On Physical Channel Design Framework for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2205851 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
| R1-2205887 | Physical channel design for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2205992 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2206042 | Physical channel design framework for sidelink on unlicensed spectrum | vivo |
| R1-2206098 | Discussion on physical layer structures and procedures for SL-U | ZTE,Sanechips |
| R1-2206120 | Discussion on physical channel design framework for SL-unlicensed | Sony |
| R1-2206291 | Physical channel designs of NR sidelink in unlicensed channel | OPPO |
| R1-2206401 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2206439 | NR Sidelink Unlicensed Physical Channel Design | Fraunhofer HHI, Fraunhofer IIS |
| R1-2206449 | Physical layer design framework for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2206470 | Discussion on physical channel design framework | NEC |
| R1-2206586 | Physical Channel Design for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2206645 | Discussion on physical channel design for sidelink-unlicensed | Xiaomi |
| R1-2206661 | Discussion on Physical channel design framework for sidelink on unlicensed spectrum | Hyundai Motor Company |
| R1-2206670 | Discussion of physical channel design for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2206827 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2206861 | On Physical Channel Design framework for SL-U | ITL |
| R1-2206914 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CMCC |
| R1-2207016 | Discussion on physical channel design framework | MediaTek Inc. |
| R1-2207064 | Physical channel design for sidelink on unlicensed spectrum | EURECOM |
| R1-2207111 | Discussion on Design of Short Synchronization Signals | Johns Hopkins University APL |
| R1-2207129 | SL U physical layer design framework | InterDigital, Inc. |
| R1-2207234 | Physical Channel Design for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2207280 | Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum | Sharp |
| R1-2207299 | Physical channel design for sidelink on unlicensed spectrum | Panasonic |
| R1-2207338 | Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum | Apple |
| R1-2207409 | Discussion on channel design framework in SL-U | NTT DOCOMO, INC. |
| R1-2207567 | PHY channel design framework for SL-U | Ericsson |
| R1-2207600 | Discussion on PHY channel design framework for SL on unlicensed spectrum | WILUS Inc. |
| R1-2207795 | FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2207796 | FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2207797 | FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2207798 | FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2207799 | FL summary#5 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2208023 | FL summary#6 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205841 | On Co-channel Coexistence for LTE Sidelink and NR Sidelink | Nokia, Nokia Shanghai Bell |
| R1-2205852 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics |
| R1-2205888 | Co-channel coexistence for LTE sidelink and NR sidelink | Huawei, HiSilicon |
| R1-2205993 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Spreadtrum Communications |
| R1-2206043 | Co-channel coexistence for LTE sidelink and NR sidelink | vivo |
| R1-2206065 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | TOYOTA Info Technology Center |
| R1-2206099 | Study on co-channel coexistence for LTE sidelink and NR sidelink | ZTE,Sanechips |
| R1-2206121 | Discussion on co-channel coexistence for LTE sidelink | Sony |
| R1-2206292 | Discussion on co-channel coexistence for LTE and NR V2X | OPPO |
| R1-2206402 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CATT, GOHIGH |
| R1-2206440 | Discussion on Co-Channel Coexistence for LTE and NR Sidelink | Fraunhofer HHI, Fraunhofer IIS |
| R1-2206450 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Lenovo |
| R1-2206471 | Co-existence between LTE and NR sidelink | NEC |
| R1-2206587 | Considerations for LTE Sidelink and NR Sidelink Co-channel Coexistence | Intel Corporation |
| R1-2206646 | Discussion on co-channel coexistence for LTE and NR sidelink | Xiaomi |
| R1-2206660 | Discussion on Sidelink Co-channel Coexistence | Panasonic |
| R1-2206671 | Discussion of co-channel coexistence for LTE sidelink and NR sidelink | Transsion Holdings |
| R1-2206681 | Considerations on co-channel coexistence for LTE SL and NR SL | CAICT |
| R1-2206692 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | China Telecom |
| R1-2206828 | On co-channel coexistence for LTE sidelink and NR sidelink | Samsung |
| R1-2206915 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CMCC |
| R1-2206956 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | ETRI |
| R1-2207010 | Co-channel coexistence for NR sidelink and LTE sidelink | MediaTek Inc. |
| R1-2207147 | Co-channel coexistence for LTE sidelink and NR sidelink | InterDigital, Inc. |
| R1-2207154 | On sidelink co-channel coexistence issues | Mitsubishi Electric RCE |
| R1-2207235 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
| R1-2207281 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Sharp |
| R1-2207339 | Co-channel Coexistence for LTE Sidelink and NR Sidelink | Apple |
| R1-2207410 | Discussion on co-channel coexistence of LTE-SL and NR-SL | NTT DOCOMO, INC. |
| R1-2207509 | Discussions on LTE and NR sidelink co-channel coexistence | ROBERT BOSCH GmbH |
| R1-2207565 | Co-channel coexistence between LTE sidelink and NR sidelink | Ericsson |
| R1-2207601 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | WILUS Inc. |
| R1-2207625 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Continental Automotive GmbH |
| R1-2207636 | FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2207670 | FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2208095 | FL Summary#3 for AI 9.4.2 - Co-Channel Coexistence for LTE and NR Sidelink | Moderator (Fraunhofer HHI) |
| R1-2208096 | FL Summary EoM of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207458 | Draft TR 38.859 v001: Study on expanded and improved NR positioning | Intel Corporation, CATT, Ericsson |
| R1-2208147 | Session notes for 9.5 (Study on expanded and improved NR positioning) | Ad-Hoc Chair (Huawei) |
| R1-2208157 | Draft TR 38.859 v010: Study on expanded and improved NR positioning | Intel Corporation, CATT, Ericsson |
| R1-2208267 | Draft TR 38.859 v010: Study on expanded and improved NR positioning | Intel Corporation, CATT, Ericsson |
| R1-2208275 | TR 38.859 v010: Study on expanded and improved NR positioning | Rapporteurs (Intel Corporation, CATT, Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205836 | SL positioning scenarios and requirements | Nokia, Nokia Shanghai Bell |
| R1-2205853 | Discussion on SL positioning scenarios and requirements | LG Electronics |
| R1-2205866 | Remaining issues of scenarios and requirements for sidelink positioning | Huawei, HiSilicon |
| R1-2205899 | Discussion on scenarios and requirements for SL positioning | ZTE |
| R1-2206044 | Discussion on SL positioning scenarios and requirements | vivo |
| R1-2206066 | Discussion on requirements for sidelink positioning | TOYOTA Info Technology Center |
| R1-2206122 | Considerations on SL positioning scenarios | Sony |
| R1-2206238 | SL positioning scenarios and requirements | NEC |
| R1-2206287 | Discussion on SL positioning scenarios and requirements | OPPO |
| R1-2206403 | Discussion on SL positioning scenarios and requirements | CATT, GOHIGH |
| R1-2206496 | Potential SL Positioning Scenarios and Requirements | Lenovo |
| R1-2206588 | On scenarios and requirements for SL positioning | Intel Corporation |
| R1-2206647 | Discussion on sidelink positioning scenarios and requirement | Xiaomi |
| R1-2206829 | On SL Positioning Scenarios and Requirements | Samsung |
| R1-2206916 | Remaining issues on SL positioning scenarios and requirements | CMCC |
| R1-2207071 | Further discussion on sidelink based positioning requirements & scenarios | CEWiT |
| R1-2207085 | Discussions on SL positioning scenario and requirements | InterDigital, Inc. |
| R1-2207236 | Sidelink Positioning Scenarios and Requirements | Qualcomm Incorporated |
| R1-2207282 | Views on SL positioning scenarios and requirements | Sharp |
| R1-2207340 | Discussion on Sidelink positioning scenarios and requirements | Apple |
| R1-2207507 | Views on SL positioning scenarios and requirements | ROBERT BOSCH GmbH |
| R1-2207577 | Discussion on sidelink positioning scenarios and requirement | Xiaomi |
| R1-2207618 | Scenarios and requirements for sidelink positioning | Ericsson |
| R1-2207626 | Considerations on sidelink positioning in NR | ITL |
| R1-2207738 | FL summary #1 on SL positioning scenarios and requirements | Moderator (Intel) |
| R1-2208158 | FL summary #2 on SL positioning scenarios and requirements | Moderator (Intel) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205837 | Evaluation of SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2205854 | Discussion on evaluation of SL positioning | LG Electronics |
| R1-2205867 | Evaluation assumptions and results for SL positioning | Huawei, HiSilicon |
| R1-2205900 | Discussion on evaluation of SL positioning | ZTE |
| R1-2206045 | Evaluation of sidelink positioning performance | vivo |
| R1-2206123 | Initial Performance Evaluation of SL Positioning | Sony |
| R1-2206239 | Evaluation of SL positioning | NEC |
| R1-2206288 | Remaining details on evaluation methodology of SL positioning | OPPO |
| R1-2206404 | Evaluation methodology and performance evaluation for SL positioning | CATT, GOHIGH |
| R1-2206497 | SL Positioning Evaluation Methodology and Performance | Lenovo |
| R1-2206648 | Discussion on evaluation of sidelink positioning | Xiaomi |
| R1-2206830 | Discussion on Evaluation for SL Positioning | Samsung |
| R1-2207072 | Discussion on evaluation methods and results of sidelink based positioning | CEWiT |
| R1-2207086 | Evaluation results for SL positioning | InterDigital, Inc. |
| R1-2207124 | Evaluation methodology for SL positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207237 | Sidelink Positioning Evaluation Assumptions and Results | Qualcomm Incorporated |
| R1-2207508 | Views on Evaluation of SL positioning for VRU Protection | ROBERT BOSCH GmbH |
| R1-2207578 | Discussion on evaluation of sidelink positioning | Xiaomi |
| R1-2207605 | FL summary#1 for SL positioning evaluation | ZTE |
| R1-2207606 | FL summary#2 for SL positioning evaluation | ZTE |
| R1-2207619 | Simulation assumptions and evaluations for NR SL positioning | Ericsson |
| R1-2207686 | SL Positioning Evaluation Methodology and Performance | Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R1-2205746 | Potential sidelink positioning solutions | FUTUREWEI |
| R1-2205838 | Potential solutions for SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2205855 | Discussion on potential solutions for SL positioning | LG Electronics |
| R1-2205868 | Discussion on solutions to support SL positioning | Huawei, HiSilicon |
| R1-2205901 | Discussion on potential solutions for SL positioning | ZTE |
| R1-2205994 | Discussion on potential solutions for SL positioning | Spreadtrum Communications |
| R1-2206046 | Discussion on potential solutions for sidelink positioning | vivo |
| R1-2206124 | Discussion on potential solutions for SL positioning | Sony |
| R1-2206240 | Discussion on Potential Solutions for SL Positioning | NEC |
| R1-2206289 | Discussion on potential solutions for SL positioning | OPPO |
| R1-2206405 | Discussion on potential solutions for SL positioning | CATT, GOHIGH |
| R1-2206498 | On Potential SL Positioning Solutions | Lenovo |
| R1-2206589 | Potential solutions for SL positioning | Intel Corporation |
| R1-2206649 | Discussion on sidelink positioning solutions | Xiaomi |
| R1-2206693 | Discussion on potential solutions for sidelink positioning | China Telecom |
| R1-2206831 | Discussion on Potential Solutions for SL Positioning | Samsung |
| R1-2206917 | Discussion on potential solutions for SL positioning | CMCC |
| R1-2207073 | Discussion on enhancement for sidelink positioning support | CEWiT |
| R1-2207087 | Potential solutions for SL positioning | InterDigital, Inc. |
| R1-2207125 | Potential solutions for SL positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207238 | Potential Solutions for Sidelink Positioning | Qualcomm Incorporated |
| R1-2207283 | Views on potential solutions for SL positioning | Sharp |
| R1-2207341 | Discussions on Potential solutions for SL positioning | Apple |
| R1-2207411 | Discussion on potential solutions for SL positioning | NTT DOCOMO, INC. |
| R1-2207443 | Discussion on handling Anchor UE | DENSO AUTOMOTIVE |
| R1-2207479 | The potential solutions for sidelink positioning | MediaTek Inc. |
| R1-2207484 | Discussion on sidelink positioning | ASUSTeK |
| R1-2207579 | Discussion on sidelink positioning solutions | Xiaomi |
| R1-2207620 | On potential solutions for SL positioning | Ericsson |
| R1-2207846 | Moderator Summary #1 on potential solutions for SL positioning | Moderator (Qualcomm) |
| R1-2207875 | Moderator Summary #2 on potential solutions for SL positioning | Moderator (Qualcomm) |
| R1-2207974 | Moderator Summary #3 on potential solutions for SL positioning | Moderator (Qualcomm) |
| R1-2208186 | Moderator Summary #4 on potential solutions for SL positioning | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205869 | Error source for NR RAT-dependent positioning | Huawei, HiSilicon |
| R1-2205902 | Discussion on integrity of RAT dependent positioning | ZTE |
| R1-2205995 | Discussion on error sources for RAT-dependent positioning | Spreadtrum Communications |
| R1-2206047 | Discussion on solutions for integrity of RAT dependent positioning | vivo |
| R1-2206125 | Considerations on Integrity for RAT dependent positioning | Sony |
| R1-2206273 | Discussions on Integrity for NR Positioning | OPPO |
| R1-2206406 | Discussion on solutions for integrity of RAT dependent positioning techniques | CATT |
| R1-2206490 | Views on solutions for integrity of RAT-dependent positioning techniques | Nokia, Nokia Shanghai Bell |
| R1-2206499 | Integrity aspects for RAT-dependent positioning | Lenovo |
| R1-2206650 | Error source for NR RAT-dependent positioning integrity | Xiaomi |
| R1-2206832 | Discussion on Integrity of RAT Dependent Positioning | Samsung |
| R1-2206918 | Discussion on integrity for RAT-dependent positioning | CMCC |
| R1-2207088 | Discussion on integrity for RAT dependent positioning techniques | InterDigital, Inc. |
| R1-2207239 | Integrity for RAT dependent positioning | Qualcomm Incorporated |
| R1-2207284 | Views on solutions for integrity of RAT dependent positioning techniques | Sharp |
| R1-2207412 | Discussion on solutions for integrity of RAT dependent positioning techniques | NTT DOCOMO, INC. |
| R1-2207621 | Error Sources characterization for integrity of RAT dependent positioning techniques | Ericsson |
| R1-2207744 | FL summary #1 on integrity of RAT dependent positioning techniques | Moderator (InterDigital) |
| R1-2207922 | FL summary #2 on integrity of RAT dependent positioning techniques | Moderator (InterDigital) |
| R1-2208189 | FL summary #3 on integrity of RAT dependent positioning techniques | Moderator (InterDigital) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205870 | Evaluation and solutions for NR carrier phase positioning | Huawei, HiSilicon |
| R1-2205903 | Discussion on carrier phase measurement based positioning | ZTE |
| R1-2206048 | Discussion on carrier phase measurement enhancements | vivo |
| R1-2206227 | Solutions for Integer Ambiguity, TRP synchronization and Vertical Positioning | Locaila |
| R1-2206274 | Discussions on Carrier Phase Measurement for NR Positioning | OPPO |
| R1-2206407 | Discussion on improved accuracy based on NR carrier phase measurement | CATT |
| R1-2206491 | Views on improved accuracy based on NR carrier phase measurement | Nokia, Nokia Shanghai Bell |
| R1-2206500 | On NR carrier phase measurements | Lenovo |
| R1-2206590 | Improved positioning accuracy with NR carrier phase measurements | Intel Corporation |
| R1-2206651 | Improved accuracy based on NR carrier phase measurement | Xiaomi |
| R1-2206694 | Discussion on improved accuracy based on NR carrier phase measurement | China Telecom |
| R1-2206833 | Discussion on NR Carrier Phase Measurement | Samsung |
| R1-2206919 | Discussion on carrier phase positioning | CMCC |
| R1-2207090 | Discussion on positioning based on NR carrier phase measurement | InterDigital, Inc. |
| R1-2207126 | NR carrier phase measurements for positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2207240 | Phase Measurements in NR Positioning | Qualcomm Incorporated |
| R1-2207285 | Views on improved accuracy based on NR carrier phase measurement | Sharp |
| R1-2207360 | Discussion on OFDM based carrier phase measurement in NR | LG Electronics |
| R1-2207413 | Discussion on improved accuracy based on NR carrier phase measurement | NTT DOCOMO, INC. |
| R1-2207480 | On carrier phase measurement | MediaTek Inc. |
| R1-2207622 | Improved accuracy based on NR carrier phase measurement | Ericsson |
| R1-2207690 | FL Summary for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| R1-2207691 | FL Summary #2 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| R1-2207710 | Discussion on OFDM based carrier phase measurement in NR | LG Electronics |
| R1-2207742 | Discussion on NR Carrier Phase Measurement | Samsung |
| R1-2208206 | FL Summary #3 for improved accuracy based on NR carrier phase measurements | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205871 | Evaluation and solutions for LPHAP | Huawei, HiSilicon |
| R1-2205904 | Discussion on low power high accuracy positioning | ZTE |
| R1-2205996 | Discussion on evaluation on LPHAP | Spreadtrum Communications |
| R1-2206049 | Discussion on Low Power High Accuracy Positioning | vivo |
| R1-2206275 | Disucssion on Low Power High Accuracy Positioning | OPPO |
| R1-2206408 | Discussion on Low Power High Accuracy Positioning | CATT |
| R1-2206492 | Views on LPHAP | Nokia, Nokia Shanghai Bell |
| R1-2206501 | LPHAP considerations | Lenovo |
| R1-2206591 | Discussion on power saving evaluation and techniques for LPHAP | Intel Corporation |
| R1-2206652 | Discussion on Low Power High Accuracy Positioning | Xiaomi |
| R1-2206834 | Discussion on LPHAP | Samsung |
| R1-2206920 | Discussion on low power high accuracy positioning | CMCC |
| R1-2206921 | Summary for low power high accuracy positioning | Moderator (CMCC) |
| R1-2207091 | Discussions on Low Power High Accuracy Positioning (LPHAP) techniques | InterDigital, Inc. |
| R1-2207241 | Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning | Qualcomm Incorporated |
| R1-2207286 | Views on low power high accuracy positioning | Sharp |
| R1-2207361 | Discussion on LPHAP in idle/inactive state | LG Electronics |
| R1-2207414 | Discussion on Low Power High Accuracy Positioning | NTT DOCOMO, INC. |
| R1-2207623 | Evaluations for Low Power High Accuracy Positioning | Ericsson |
| R1-2207993 | FL summary #2 for low power high accuracy positioning | Moderator (CMCC) |
| R1-2207994 | FL summary #3 for low power high accuracy positioning | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205872 | Discussion on RedCap positioning | Huawei, HiSilicon |
| R1-2205905 | Discussion on Positioning for RedCap UE | ZTE |
| R1-2206050 | Discussion on positioning for RedCap UEs | vivo |
| R1-2206126 | Discussion on positioning for RedCap UEs | Sony |
| R1-2206276 | Discussion on Positioning for RedCap Ues | OPPO |
| R1-2206426 | Discussion on positioning for RedCap UEs | CATT |
| R1-2206473 | Discussion on positioning support for RedCap UEs | NEC |
| R1-2206493 | Views on Positioning for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2206502 | Positioning for RedCap devices | Lenovo |
| R1-2206592 | Positioning for RedCap UEs | Intel Corporation |
| R1-2206835 | Discussion on Positioning for RedCap UEs | Samsung |
| R1-2206922 | Discussion on RedCap positioning | CMCC |
| R1-2207092 | Discussions on positioning for RedCap UEs | InterDigital, Inc. |
| R1-2207242 | Positioning for Reduced Capabilities UEs | Qualcomm Incorporated |
| R1-2207287 | Views on positioning for RedCap Ues | Sharp |
| R1-2207342 | Discussions on Positioning for RedCap Ues | Apple |
| R1-2207362 | Discussion on positioning support for RedCap Ues | LG Electronics |
| R1-2207415 | Discussion on positioning for RedCap UEs | NTT DOCOMO, INC. |
| R1-2207482 | The potential solutions for RedCap UEs for positioning | MediaTek Inc. |
| R1-2207624 | Considerations for RedCap Positioning | Ericsson |
| R1-2207749 | Feature Lead Summary #1 for Positioning for RedCap UEs | Moderator (Ericsson) |
| R1-2207750 | Feature Lead Summary #2 for Positioning for RedCap UEs | Moderator (Ericsson) |
| R1-2207751 | Feature Lead Summary #3 for Positioning for RedCap UEs | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207730 | FL summary for collection of evaluation results for Rel-18 RedCap SI | Moderator (Ericsson, MediaTek) |
| R1-2207981 | FL summary #2 for collection of evaluation results for Rel-18 RedCap SI | Moderators (Ericsson, MediaTek) |
| R1-2208032 | TR 38.865 V0.1.0 Study on further NR RedCap UE complexity reduction | Rapporteur (Ericsson) |
| R1-2208148 | Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) | Ad-hoc Chair (CMCC) |
| R1-2208316 | TR 38.865 V0.1.0 Study on further NR RedCap UE complexity reduction | Rapporteur (Ericsson) |
| R1-2208317 | Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205739 | Potential solutions for further RedCap UE complexity reduction | Ericsson |
| R1-2205741 | Analysis of complexity reduction techniques for RedCap UEs in Rel-18 | FUTUREWEI |
| R1-2205873 | Discussion on potential solutions to further reduce UE complexity | Huawei, HiSilicon |
| R1-2205997 | Discussion on potential solutions to further reduce UE complexity | Spreadtrum Communications |
| R1-2206051 | Techniques to further reduce RedCap UE complexity | vivo, Guangdong Genius |
| R1-2206127 | Complexity reduction for RedCap UEs | Sony |
| R1-2206201 | Discussion on further RedCap UE complexity reduction | DENSO CORPORATION |
| R1-2206303 | Solution study on further reduced UE complexity | OPPO |
| R1-2206333 | Potential solutions to further reduce UE complexity for eRedCap | Panasonic |
| R1-2206409 | Discussion on solutions to further reduce UE complexity in Rel-18 | CATT |
| R1-2206417 | Discussion on potential solutions to further reduce UE complexity | NEC |
| R1-2206443 | Further RedCap UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
| R1-2206494 | On further complexity reduction of NR UE | Nordic Semiconductor ASA |
| R1-2206593 | On solutions to further reduce UE complexity | Intel Corporation |
| R1-2206653 | Potential solutions to further reduce UE complexity | Xiaomi |
| R1-2206672 | Discussion on potential solutions to further reduce UE complexity | Transsion Holdings |
| R1-2206695 | Discussion on potential solutions to further reduce UE complexity | China Telecom |
| R1-2206836 | Further UE complexity reduction for eRedCap | Samsung |
| R1-2206923 | Discussion on further reduced UE complexity | CMCC |
| R1-2206937 | Discussion on solutions to further reduce UE complexity | Sharp |
| R1-2207002 | Potential solutions to further reduce UE complexity | MediaTek Inc. |
| R1-2207036 | Discussion on potential solutions for further UE complexity reduction | LG Electronics |
| R1-2207057 | Discussion on eRedCap UE complexity reduction | ZTE, Sanechips |
| R1-2207149 | On complexity reduction for RedCap UE | InterDigital, Inc. |
| R1-2207243 | Further complexity reduction for eRedCap device | Qualcomm Incorporated |
| R1-2207260 | Considerations for further UE complexity reduction | Sierra Wireless. S.A. |
| R1-2207416 | Discussion on potential solutions for further UE complexity reduction for eRedCap | NTT DOCOMO, INC. |
| R1-2207477 | Potential solutions to further reduce UE complexity | Lenovo |
| R1-2207684 | Discussion on potential solutions for further UE complexity reduction for eRedCap | NTT DOCOMO, INC. |
| R1-2207731 | FL summary #1 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2207732 | FL summary #2 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2207733 | FL summary #3 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2207734 | FL summary #4 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2207982 | FL summary #5 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2207983 | FL summary #6 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2208273 | FL summary #7 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2208287 | FL summary #8 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205740 | Evaluation of coverage impact for further RedCap UE complexity reduction | Ericsson |
| R1-2205874 | Discussion on coverage evaluation | Huawei, HiSilicon |
| R1-2205998 | Evaluation of coverage impact for eRedCap | Spreadtrum Communications |
| R1-2206052 | Coverage evaluation for eRedCap | vivo, Guangdong Genius |
| R1-2206104 | Discussion on NR RedCap UE coverage | Mavenir |
| R1-2206304 | Evaluation of coverage for RedCap enhancement | OPPO |
| R1-2206410 | Evaluation of coverage of Rel-18 eRedCap UEs | CATT |
| R1-2206437 | Evaluation of coverage impact for eRedCap | Panasonic |
| R1-2206444 | Evaluation of coverage impact | Nokia, Nokia Shanghai Bell |
| R1-2206594 | Evaluations on coverage impact for eRedCap UE | Intel Corporation |
| R1-2206654 | Evaluation of coverage impact of further UE bandwidth reduction | Xiaomi |
| R1-2206673 | Discussion on simulation needs and assumptions | Transsion Holdings |
| R1-2206837 | Coverage evaluations for eRedCap | Samsung |
| R1-2206924 | Discussion on evaluation of coverage impact | CMCC |
| R1-2207003 | Evaluation of coverage impact for Rel-18 RedCap | MediaTek Inc. |
| R1-2207058 | Coverage evaluation for eRedCap UE | ZTE, Sanechips |
| R1-2207148 | Evaluation on coverage impact for RedCap UE | InterDigital, Inc. |
| R1-2207244 | Coverage analysis for eRedCap | Qualcomm Incorporated |
| R1-2207417 | Discussion on evaluations of coverage impact for eRedCap | NTT DOCOMO, INC. |
| R1-2207478 | Evaluation of coverage impact | Lenovo |
| R1-2207692 | Discussion on evaluations of coverage impact for eRedCap | NTT DOCOMO, INC. |
| R1-2207740 | Evaluations on coverage impact for eRedCap UE | Intel Corporation |
| R1-2207741 | Evaluation of coverage impact for further RedCap UE complexity reduction | Ericsson |
| R1-2207866 | FL summary #1 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2207867 | FL summary #2 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2207868 | FL summary #3 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2207869 | FL summary #4 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2207904 | Example tables for R18 eRedCap coverage impact evaluation | Moderator (MediaTek) |
| R1-2207905 | FL summary #5 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2207969 | Evaluation of coverage of Rel-18 eRedCap UEs | CATT |
| R1-2208245 | FL summary #6 on evaluation of coverage impact | Moderator (MediaTek) |
| R1-2208288 | FL summary #7 on evaluation of coverage impact | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2207020 | TR 38.864 v0.1.0 for study on network energy savings for NR | Rapporteur (Huawei) |
| R1-2208311 | TR 38.864 comments collection for Post-110-R18-NW_ES1 | Moderator (Huawei) |
| R1-2208315 | TR 38.864 v0.1.0 for study on network energy savings for NR | Rapporteur (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205755 | BS Energy Consumption Model and Sleep States | FUTUREWEI |
| R1-2205860 | Discussion on performance evaluation for network energy saving | Huawei, HiSilicon |
| R1-2205999 | Discussion on performance evaluation of network energy savings | Spreadtrum Communications |
| R1-2206053 | Discussions on NW energy savings performance evaluationns on | vivo |
| R1-2206074 | NW energy savings performance evaluation | Nokia, Nokia Shanghai Bell |
| R1-2206141 | On network energy savings evaluation methodology and power model | Panasonic |
| R1-2206172 | Discussion on NW energy savings performance evaluation | Fujitsu |
| R1-2206308 | Discussion on NW energy savings performance evaluation | OPPO |
| R1-2206411 | Evaluation Methodology and Power Model for Network Energy Saving | CATT |
| R1-2206595 | Discussion on Network energy saving performance evaluations | Intel Corporation |
| R1-2206665 | Performance evaluation for network energy saving | InterDigital, Inc. |
| R1-2206696 | Discussion on BS energy saving model and evaluation | China Telecom |
| R1-2206838 | NW Energy Savings Performance Evaluation | Samsung |
| R1-2206925 | Discussion on network energy saving performance evaluation | CMCC |
| R1-2206979 | NW energy savings performance evaluation | MediaTek Inc. |
| R1-2207037 | Discussion on performance evaluation for network energy savings | LG Electronics |
| R1-2207059 | Discussion on NW energy saving performance evaluation | ZTE, Sanechips |
| R1-2207079 | Evaluation and power model for network energy savings | Rakuten Symphony |
| R1-2207245 | NW energy savings performance evaluation | Qualcomm Incorporated |
| R1-2207343 | On NW energy savings performance evaluation | Apple |
| R1-2207418 | Discussion on NW energy savings performance evaluation | NTT DOCOMO, INC. |
| R1-2207437 | Network energy consumption modeling and evaluation | Ericsson |
| R1-2207685 | Discussion on NW energy savings performance evaluation | OPPO |
| R1-2207694 | Discussion on Network energy saving performance evaluations | Intel Corporation |
| R1-2207910 | FL summary#1 for EVM for NR NW energy savings | Moderator (Huawei) |
| R1-2207987 | FL summary#2 for EVM for NR NW energy savings | Moderator (Huawei) |
| R1-2208216 | FL summary#3 for EVM for NR NW energy savings | Moderator (Huawei) |
| R1-2208312 | FL summary for Post-110-R18- NW_ES2 | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205756 | Enhancements for network energy saving | FUTUREWEI |
| R1-2205861 | Discussion on network energy saving techniques | Huawei, HiSilicon |
| R1-2206000 | Discussion on network energy saving techniques | Spreadtrum Communications |
| R1-2206054 | Discussions on network energy saving techniques | vivo |
| R1-2206075 | Network energy saving techniques | Nokia, Nokia Shanghai Bell |
| R1-2206142 | Discussion on potential network energy saving techniques | Panasonic |
| R1-2206173 | Discussion on Network energy saving techniques | Fujitsu |
| R1-2206242 | Discussion on network energy saving techniques | NEC |
| R1-2206309 | Discussion on network energy saving techniques | OPPO |
| R1-2206412 | Network Energy Saving techniques in time, frequency, and spatial domain | CATT |
| R1-2206517 | Network energy saving techniques | Lenovo |
| R1-2206596 | Discussion on Network energy saving techniques | Intel Corporation |
| R1-2206655 | Discussions on techniques for network energy saving | Xiaomi |
| R1-2206666 | Potential techniques for network energy saving | InterDigital, Inc. |
| R1-2206697 | Discussion on potential techniques for network energy saving | China Telecom |
| R1-2206839 | Network energy saving techniques | Samsung |
| R1-2206926 | Discussion on network energy saving techniques | CMCC |
| R1-2206947 | On Network Energy Saving Techniques | Fraunhofer IIS, Fraunhofer HHI |
| R1-2206980 | Network energy saving techniques | MediaTek Inc. |
| R1-2207038 | Discussion on physical layer techniques for network energy savings | LG Electronics |
| R1-2207060 | Discussion on NW energy saving techniques | ZTE, Sanechips |
| R1-2207074 | Discussion on Network energy saving techniques | CEWiT |
| R1-2207119 | Discussion on network energy saving techniques | Rakuten Mobile Inc. |
| R1-2207246 | Network energy saving techniques | Qualcomm Incorporated |
| R1-2207344 | Discussion on Network energy saving techniques | Apple |
| R1-2207419 | Discussion on NW energy saving techniques | NTT DOCOMO, INC. |
| R1-2207438 | Network energy savings techniques | Ericsson |
| R1-2207446 | Discussion on potential L1 network energy saving techniques for NR | ITRI |
| R1-2207481 | Discussion on network energy saving techniques | KT Corp. |
| R1-2207697 | Discussion Summary for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2207841 | Discussion Summary#1 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2208027 | Discussion Summary#2 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2208185 | Discussion Summary#2 for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2206017 | Updated TR38.867 for Study on NR NCR | ZTE |
| R1-2207941 | Updated TR38.867 for Study on NR NCR | ZTE |
| R1-2208191 | TR 38.867 v0.2.0 for Study on NR network-controlled repeaters | Rapporteur (ZTE) |
| R1-2208310 | TR 38.867 v0.2.0 for Study on NR network-controlled repeaters | Rapporteur (ZTE) |
| R1-2208314 | TR 38.867 v0.2.0 for Study on NR network-controlled repeaters | Rapporteur (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205813 | Power Control and Side Control Information for NCRs | Pivotal Commware, AT&T |
| R1-2205875 | On the side control information and performance evaluation for NCR | Huawei, HiSilicon |
| R1-2205939 | Discussion on side control information to enable NR network-controlled repeaters | Nokia, Nokia Shanghai Bell |
| R1-2206001 | Discussion on side control information to enable NR network-controlled repeaters | Spreadtrum Communications |
| R1-2206018 | Discussion on side control information for NCR | ZTE |
| R1-2206055 | Discussion on side control information to enable NR network-controlled repeaters | vivo |
| R1-2206128 | Additional considerations on side control information to enable NR network-controlled repeaters | Sony |
| R1-2206174 | Discussion on side control information for NR network-controlled repeaters | Fujitsu |
| R1-2206183 | Discussions on side control information for NR network-controlled repeaters | InterDigital, Inc. |
| R1-2206208 | Side control information for network-controlled repeaters | NICT and Toyota InfoTechnology Center |
| R1-2206330 | Discussion on side control information for NCR | OPPO |
| R1-2206413 | Side control information to enable NR network-controlled repeaters | CATT |
| R1-2206435 | Discussion on side control information for network-controlled repeaters | Panasonic |
| R1-2206478 | Discussion on side control information to enable NR network-controlled repeaters | NEC |
| R1-2206597 | Discussion on Side control information to enable NR network-controlled repeater | Intel Corporation |
| R1-2206656 | Discussion on side control information to enable NR network-controlled repeaters | Xiaomi |
| R1-2206698 | Discussion on side control information for network-controlled repeaters | China Telecom |
| R1-2206840 | Side control information to enable NR network-controlled repeaters | Samsung |
| R1-2206927 | Discussion on side control information to enable NR network-controlled repeaters | CMCC |
| R1-2206957 | Discussion on side control information for network-controlled repeater | ETRI |
| R1-2206981 | Side control information for network-controlled repeaters | MediaTek Inc. |
| R1-2207075 | Discussion on Side control information to enable NR network-controlled repeaters | CEWiT, IITK |
| R1-2207120 | Discussion on side control information for NCR | Rakuten Mobile Inc. |
| R1-2207127 | Discussion on side control information to enable NCR operations | Sharp |
| R1-2207247 | On side control information for network controlled repeaters (NCR) | Qualcomm Incorporated |
| R1-2207297 | Discussion on side control information for network-controlled repeater | Lenovo |
| R1-2207300 | Discussion on side control information to enable NR network-controlled repeaters | CAICT |
| R1-2207345 | Discussion on side control information for NR network-controlled repeaters | Apple |
| R1-2207366 | Discussion on side control information for NCR | LG Electronics |
| R1-2207420 | Discussion on side control information to enable NR network-controlled repeaters | NTT DOCOMO, INC. |
| R1-2207460 | Discussion on side control information to enable NR network-controlled repeaters | KDDI Corporation |
| R1-2207680 | Control information for enabling NCR | Ericsson |
| R1-2207688 | Summary#1 of discussion on side control information | Moderator (ZTE) |
| R1-2207933 | Summary#2 of discussion on side control information | Moderator (ZTE) |
| R1-2208041 | Summary#3 of discussion on side control information | Moderator (ZTE) |
| R1-2208192 | Summary#4 of discussion on side control information | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205876 | On L1/L2 signaling for side control information | Huawei, HiSilicon |
| R1-2205940 | Discussion on L1/L2 signaling for side control information of network-controlled repeaters | Nokia, Nokia Shanghai Bell |
| R1-2206002 | Discussion on L1/L2 signaling for side control information | Spreadtrum Communications |
| R1-2206019 | Discussion on L1/L2 signaling for side control information | ZTE |
| R1-2206056 | Discussion on signaling for side control information | vivo |
| R1-2206129 | Additional considerations on L1/L2 signaling for side control information | Sony |
| R1-2206175 | Discussion on L1/L2 signaling for side control information | Fujitsu |
| R1-2206184 | L1/L2 signaling for side control information of network-controlled repeaters | InterDigital, Inc. |
| R1-2206414 | Discussion on signaling for side control information for NR network-controlled repeaters | CATT |
| R1-2206479 | Discussion on L1/L2 signaling for side control information | NEC |
| R1-2206598 | Discussions on L1/L2 signaling for side control information | Intel Corporation |
| R1-2206657 | Discussion on L1/L2 signalling for side control information | Xiaomi |
| R1-2206699 | Discussion on L1/L2 signaling for side control information | China Telecom |
| R1-2206841 | L1/L2 signaling for side control information | Samsung |
| R1-2206858 | Discussion on ON-OFF information for NCR | KT Corp. |
| R1-2206928 | Discussion on L1/L2 signaling for side control information | CMCC |
| R1-2206958 | Discussion on L1/L2 signaling for side control information | ETRI |
| R1-2206982 | L1/L2 control signaling for enabling network controlled repeaters | MediaTek Inc. |
| R1-2207076 | Discussion on L1/L2 signaling for side control information for NCR | CEWiT, IITK |
| R1-2207089 | Discussion on L1/L2 signaling for side control information of network-controlled repeaters | Lenovo |
| R1-2207121 | Discussion on signaling for side control information | Rakuten Mobile Inc. |
| R1-2207248 | On L1/L2 signaling for side control information for NCR | Qualcomm Incorporated |
| R1-2207346 | Discussion on L1/L2 signaling for side control information | Apple |
| R1-2207367 | Discussion on L1/L2 signaling for side control information | LG Electronics |
| R1-2207421 | Discussion on L1/L2 signaling for side control information | NTT DOCOMO, INC. |
| R1-2207681 | Signaling of control information for NCR | Ericsson |
| R1-2207848 | Summary#1 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| R1-2207984 | Summary#2 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| R1-2208110 | Summary#3 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| TDoc | Title | Source |
|---|---|---|
| R1-2208149 | Session notes for 9.9 (Enhancement of NR Dynamic Spectrum Sharing (DSS)) | Ad-hoc Chair (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205864 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Huawei, HiSilicon |
| R1-2205964 | Discussion on NR PDCCH reception for DSS | ZTE |
| R1-2206003 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Spreadtrum Communications |
| R1-2206057 | Discussion on PDCCH reception on CRS symbol | vivo |
| R1-2206324 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | OPPO |
| R1-2206432 | NR PDCCH overlapping with LTE CRS | Nokia, Nokia Shanghai Bell |
| R1-2206658 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Xiaomi |
| R1-2206842 | On PDCCH receptions in symbols with LTE CRS | Samsung |
| R1-2207011 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | MediaTek Inc. |
| R1-2207039 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | LG Electronics |
| R1-2207130 | Evaluation of NR PDCCH overlapping with LTE CRS | InterDigital, Inc. |
| R1-2207249 | NR PDCCH reception in symbols with LTE CRS REs | Qualcomm Incorporated |
| R1-2207347 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Apple |
| R1-2207422 | Discussion on NR PDCCH reception in symbols with LTE CRS Res | NTT DOCOMO, INC. |
| R1-2207439 | NR PDCCH reception in symbols with LTE CRS REs | Ericsson |
| R1-2207591 | Considerations on NR PDCCH for DSS | KT Corp. |
| R1-2207801 | Summary#1 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2207802 | Summary#2 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2207803 | Summary#3 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2207865 | Joint Proposal on enabling LTE CRS puncturing of NR PDCCH for Rel18 DSS Enhancements WI | Ericsson, Nokia, Nokia Shanghai Bell, NTT DOCOMO, Softbank |
| TDoc | Title | Source |
|---|---|---|
| R1-2205865 | Discussion on UE support for two overlapping CRS rate matching patterns | Huawei, HiSilicon |
| R1-2205965 | Discussion on support of two overlapping CRS patterns for DSS | ZTE, China Telecom |
| R1-2206004 | Discussion on UE support for two overlapping CRS rate matching patterns | Spreadtrum Communications |
| R1-2206058 | Discussion on two overlapping CRS rate matching patterns | vivo |
| R1-2206325 | Discussion on UE support for two overlapping CRS rate matching patterns | OPPO |
| R1-2206433 | Support for 2 overlapping CRS patterns | Nokia, Nokia Shanghai Bell |
| R1-2206659 | Discussion on UE support for two overlapping CRS rate matching patterns | Xiaomi |
| R1-2206843 | Two overlapping CRS rate matching patterns | Samsung |
| R1-2207012 | Discussion on supporting two overlapping CRS rate matching pattern | MediaTek Inc. |
| R1-2207131 | Supporting two overlapping CRS rate matching patterns | InterDigital, Inc. |
| R1-2207250 | UE support for two overlapping CRS rate matching patterns | Qualcomm Incorporated |
| R1-2207348 | Disucssion on UE supporting for two overlapping CRS rate matching patterns | Apple |
| R1-2207423 | Discussion on LTE CRS rate matching pattern | NTT DOCOMO, INC. |
| R1-2207440 | UE support for overlapping CRS rate matching patterns | Ericsson |
| R1-2207842 | Feature lead summary #1 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2207843 | Feature lead summary #2 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2207844 | Feature lead summary #3 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2208193 | [Draft] LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS | ZTE |
| R1-2208194 | LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS | RAN1, ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2205862 | Discussion on multi-cell scheduling with a single DCI | Huawei, HiSilicon |
| R1-2205962 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | ZTE |
| R1-2206005 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Spreadtrum Communications |
| R1-2206059 | Discussion on multi-cell scheduling | vivo |
| R1-2206103 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | Langbo |
| R1-2206155 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Nokia, Nokia Shanghai Bell |
| R1-2206176 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | Fujitsu |
| R1-2206243 | Discussion on Multi-cell PXSCH scheduling with a single DCI | NEC |
| R1-2206326 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | OPPO |
| R1-2206382 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CATT |
| R1-2206451 | Discussion on multi-cell scheduling via a single DCI | Lenovo |
| R1-2206467 | Discussion on Multi-cell PXSCH scheduling with a single DCI | NEC |
| R1-2206599 | Discussions on multi-cell scheduling with a single DCI | Intel Corporation |
| R1-2206627 | Discussion on the design of multi-cell scheduling with a single DCI | Xiaomi |
| R1-2206663 | Multi-cell scheduling with a single DCI | InterDigital, Inc. |
| R1-2206682 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | CAICT |
| R1-2206700 | Discussion on multi-cell scheduling with a single DCI | China Telecom |
| R1-2206844 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Samsung |
| R1-2206929 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CMCC |
| R1-2207007 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | MediaTek Inc. |
| R1-2207040 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | LG Electronics |
| R1-2207097 | Discussion on Multicarrier scheduling with a single DCI | FGI |
| R1-2207143 | Discussions on multi-cell scheduling with a single DCI | Sharp |
| R1-2207251 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Qualcomm Incorporated |
| R1-2207349 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Apple |
| R1-2207424 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | NTT DOCOMO, INC. |
| R1-2207441 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Ericsson |
| R1-2207447 | Discussion on multi-cell scheduling with a single DCI | ITRI |
| R1-2207553 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Google Inc. |
| R1-2207695 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Spreadtrum Communications |
| R1-2207769 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2207770 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2207771 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2208046 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2208047 | Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2208048 | Feature lead summary#6 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205863 | Discussion on multi-carrier UL Tx switching | Huawei, HiSilicon |
| R1-2205963 | Discussion on Multi-carrier UL Tx switching scheme | ZTE |
| R1-2206006 | Discussion on multi-carrier UL Tx switching scheme | Spreadtrum Communications |
| R1-2206060 | Discussion on UL TX switching | vivo |
| R1-2206130 | Considerations on Multi-carrier UL Tx switching scheme | Sony |
| R1-2206177 | Views on multi-carrier UL Tx switching scheme | Fujitsu |
| R1-2206327 | Discussion on multi-carrier UL Tx switching scheme | OPPO |
| R1-2206383 | Discussion on multi-carrier UL Tx switching scheme | CATT |
| R1-2206434 | On Multi-Carrier UL Tx Switching | Nokia, Nokia Shanghai Bell |
| R1-2206600 | Discussions on multi-carrier UL Tx switching scheme | Intel Corporation |
| R1-2206628 | Discussion on multi-carrier UL Tx switching scheme | Xiaomi |
| R1-2206664 | Multi-carrier UL Tx switching scheme | InterDigital, Inc. |
| R1-2206701 | Discussion on UL Tx switching across up to 3 or 4 bands | China Telecom |
| R1-2206845 | On multi-carrier UL Tx switching | Samsung |
| R1-2206930 | Discussion on multi-carrier UL Tx switching scheme | CMCC |
| R1-2206986 | On multi-carrier UL Tx switching scheme | MediaTek Inc. |
| R1-2207041 | Discussion on Multi-carrier UL Tx switching scheme | LG Electronics |
| R1-2207252 | Discussion on Rel-18 UL Tx switching | Qualcomm Incorporated |
| R1-2207350 | On multi-carrier UL Tx switching | Apple |
| R1-2207425 | Discussion on multi-carrier UL Tx switching scheme | NTT DOCOMO, INC. |
| R1-2207442 | Multi-carrier UL Tx switching | Ericsson |
| R1-2207555 | Discussion on multi-carrier UL Tx switching scheme | Google Inc. |
| R1-2207752 | Summary on discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2207870 | Summary#2 on discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2207942 | Summary#3 on discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205843 | XR specific power saving techniques | TCL Communication Ltd. |
| R1-2205877 | Discussion on XR-specific power saving techniques | Huawei, HiSilicon |
| R1-2205916 | Discussion on power saving enhancements for XR | Ericsson |
| R1-2206007 | Discussion on XR specific power saving techniques | Spreadtrum Communications |
| R1-2206061 | Discussion on XR specific power saving enhancements | vivo |
| R1-2206105 | Discussion on XR power saving techniques | III |
| R1-2206131 | Considerations on power saving techniques for XR | Sony |
| R1-2206225 | XR-specific power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2206244 | Discussion on XR specific power saving techniques | NEC |
| R1-2206328 | Discussion on XR specific power saving techniques | OPPO |
| R1-2206384 | UE Power saving techniques for XR | CATT |
| R1-2206436 | Discussion on XR specific power saving techniques | Panasonic |
| R1-2206495 | Power saving techniques for XR | Rakuten Symphony |
| R1-2206518 | XR-specific power saving techniques | Lenovo |
| R1-2206601 | Discussion on XR specific power saving techniques | Intel Corporation |
| R1-2206629 | Discussions on techniques for XR Power Saving | Xiaomi |
| R1-2206702 | Discussion on XR specific power saving enhancement for NR | China Telecom |
| R1-2206846 | Considerations on XR-specific Power Savings | Samsung |
| R1-2206931 | Discussion on XR-specific power saving techniques | CMCC |
| R1-2206959 | Discussion on power saving techniques for XR | ETRI |
| R1-2206965 | On XR-specific power saving techniques | Google Inc. |
| R1-2207008 | On XR specific power saving techniques | MediaTek Inc. |
| R1-2207042 | Discussion on XR-specific power saving techniques | LG Electronics |
| R1-2207061 | Evaluation on XR specific power saving techniques | ZTE, Sanechips |
| R1-2207253 | Power saving techniques for XR | Qualcomm Incorporated |
| R1-2207263 | Discussion on XR specific power saving techniques | InterDigital, Inc. |
| R1-2207351 | XR specific power saving techniques | Apple |
| R1-2207426 | Discussion on XR specific power saving techniques | NTT DOCOMO, INC. |
| R1-2207831 | Moderator Summary#1 on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2207832 | Moderator Summary#2 on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2207833 | Final Moderator Summary on XR specific power saving techniques | Moderator (Qualcomm Incorporated) |
| R1-2207860 | Discussion on XR specific power saving enhancements | vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2205751 | XR Capacity Evaluation and Enhancements | FUTUREWEI |
| R1-2205844 | XR-specific capacity enhancements techniques | TCL Communication Ltd. |
| R1-2205878 | Discussion on XR-specific capacity enhancements techniques | Huawei, HiSilicon |
| R1-2205917 | Discussion on capacity enhancements for XR | Ericsson |
| R1-2206008 | Discussion on XR specific capacity enhancements techniques | Spreadtrum Communications |
| R1-2206062 | Discussion on XR specific capacity enhancements | vivo |
| R1-2206132 | Discussion on XR-specific capacity enhancements | Sony |
| R1-2206226 | XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
| R1-2206245 | Discussion on XR-specific capacity enhancements | NEC |
| R1-2206329 | Discussion on XR specific capacity enhancements techniques | OPPO |
| R1-2206385 | NR enhancement for XR capacity improvement | CATT |
| R1-2206475 | Discussion on XR-specific capacity enhancements | NEC |
| R1-2206519 | XR-specific capacity enhancement techniques | Lenovo |
| R1-2206602 | Discussion on XR specific capacity enhancement techniques | Intel Corporation |
| R1-2206703 | Discussion on XR specific capacity enhancement for NR | China Telecom |
| R1-2206847 | Considerations on XR Capacity Improvements | Samsung |
| R1-2206932 | Discussion on XR-specific capacity enhancements techniques | CMCC |
| R1-2206960 | Discussion on SPS and CG enhancements for XR capacity improvement | ETRI |
| R1-2206964 | On XR-specific capacity enhancements techniques | Google Inc. |
| R1-2207009 | On XR specific capacity improvement enhancements | MediaTek Inc. |
| R1-2207043 | Discussion on XR-specific capacity enhancement techniques | LG Electronics |
| R1-2207062 | XR specific capacity enhancements | ZTE, Sanechips |
| R1-2207077 | Discussion on XR specific capacity enhancements | CEWiT |
| R1-2207095 | Discussion on XR-specific capacity enhancements techniques | FGI |
| R1-2207254 | Capacity enhancement techniques for XR | Qualcomm Incorporated |
| R1-2207264 | Discussion on XR-specific capacity enhancements techniques | InterDigital, Inc. |
| R1-2207301 | Discussion on XR-specific capacity improvements | Rakuten Symphony |
| R1-2207352 | XR-specific capacity enhancements techniques | Apple |
| R1-2207427 | Discussion on XR specific capacity improvement enhancements | NTT DOCOMO, INC. |
| R1-2207718 | Discussion on XR specific capacity enhancements | vivo |
| R1-2207820 | Moderator Summary#1 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2207821 | Moderator Summary#2 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2207822 | Moderator Summary#3 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2207823 | Moderator Summary#4 - Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205829 | Work plan for NR NTN enhancements in Rel-18 | THALES |
| R1-2206223 | Discussion on UL time and frequency synchronization enhancement for NTN | BUPT |
| R1-2206418 | Discussion on UL time and frequency synchronization enhancement for NTN | BUPT |
| R1-2208150 | Session notes for 9.12 (NTN (Non-Terrestrial Networks) enhancements) | Ad-Hoc Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205826 | Discussion on NR NTN coverage enhancement | THALES |
| R1-2205832 | Coverage Enhancement for NTN | Lockheed Martin |
| R1-2205856 | Discussion on coverage enhancement for NR NTN | Huawei, HiSilicon |
| R1-2206009 | Discussion on coverage enhancements for NTN | Spreadtrum Communications |
| R1-2206012 | Coverage enhancement for NR NTN | NTPU |
| R1-2206020 | Discussion on coverage enhancement for NTN | ZTE |
| R1-2206063 | Discussions on coverage enhancement for NR NTN | vivo |
| R1-2206133 | Considerations on improving NR NTN Coverage | Sony |
| R1-2206137 | Coverage enhancement for NR NTN | MediaTek Inc. |
| R1-2206236 | Discussion on coverage enhancements aspects for NR NTN | NEC |
| R1-2206310 | Discussion on coverage enhancement for NR NTN | OPPO |
| R1-2206386 | Discussion on coverage enhancement for NR NTN | CATT |
| R1-2206423 | Evaluation results for NTN coverage enhancement | Panasonic |
| R1-2206630 | Discussion on coverage enhancement for NR-NTN | Xiaomi |
| R1-2206848 | On coverage enhancement for NR NTN | Samsung |
| R1-2206859 | On NTN coverage enhancement | ITL |
| R1-2206961 | Coverage enhancement for NR NTN | ETRI |
| R1-2207140 | Evaluation of coverage enhancements for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2207255 | Coverage enhancements for NR NTN | Qualcomm Incorporated |
| R1-2207294 | Discussion on coverage enhancement for NR NTN | Lenovo |
| R1-2207353 | Performance Evaluation on Coverage Enhancement for NR NTN | Apple |
| R1-2207358 | Discussion on coverage enhancement for NR NTN | LG Electronics |
| R1-2207372 | Discussion on coverage enhancement for NR NTN | Baicells |
| R1-2207428 | Discussion on coverage enhancement for NR NTN | NTT DOCOMO, INC. |
| R1-2207556 | On coverage enhancements for NR NTN | Ericsson |
| R1-2207762 | On coverage enhancements for NR NTN | Ericsson |
| R1-2207808 | Summary #1 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2207809 | Summary #2 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2207810 | Summary #3 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2207811 | Summary #4 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2208268 | Summary #5 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| R1-2208269 | Summary #6 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205827 | Discussion on network verified UE location in NR NTN | THALES |
| R1-2205859 | Discussion on network-verified UE location for NR NTN | Huawei, HiSilicon |
| R1-2206021 | Discussion on network verified UE location for NR NTN | ZTE |
| R1-2206064 | Discussions on Network verified UE location for NR NTN | vivo |
| R1-2206134 | Network verified UE location for NR NTN | Sony |
| R1-2206138 | Network verified UE location for NR NTN | MediaTek Inc. |
| R1-2206311 | Discussion on network verified UE location for NR NTN | OPPO |
| R1-2206387 | Considerations on network verified UE location for NR NTN | CATT |
| R1-2206424 | Discussion on network verified UE location for NTN | Panasonic |
| R1-2206503 | On NTN NW verified UE location | Lenovo |
| R1-2206631 | Discussion on the network verified location for NTN | Xiaomi |
| R1-2206849 | Network verified UE location for NR NTN | Samsung |
| R1-2206962 | Discussion on network verified UE location for NTN | ETRI |
| R1-2207141 | Network verified UE positioning for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2207256 | Network verified UE location for NR NTN | Qualcomm Incorporated |
| R1-2207354 | On Network Verified UE Location | Apple |
| R1-2207359 | Discussion on network verified UE location for NR NTN | LG Electronics |
| R1-2207429 | Discussion on Network verified UE location for NR NTN | NTT DOCOMO, INC. |
| R1-2207628 | FL Summary #1: Network verified UE location for NR NTN | Moderator (THALES) |
| R1-2207629 | FL Summary #2: Network verified UE location for NR NTN | Moderator (THALES) |
| R1-2207630 | FL Summary #3: Network verified UE location for NR NTN | Moderator (THALES) |
| R1-2207631 | FL Summary #4: Network verified UE location for NR NTN | Moderator (THALES) |
| R1-2207682 | On network verified UE location in NR NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2205831 | Remaining Issues for HARQ | Lockheed Martin |
| R1-2205857 | Discussion on disabling of HARQ feedback for IoT NTN | Huawei, HiSilicon |
| R1-2206010 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
| R1-2206022 | Discussion on disabling of HARQ feedback for IoT-NTN | ZTE |
| R1-2206135 | On disabling HARQ feedback for IoT-NTN | Sony |
| R1-2206139 | Disabling of HARQ for IoT NTN | MediaTek Inc. |
| R1-2206312 | Discussion on disabling of HARQ feedback for IoT NTN | OPPO |
| R1-2206388 | Discussion on disabling of HARQ feedback for IoT NTN | CATT |
| R1-2206480 | Disabling of HARQ feedback for IoT NTN | NEC |
| R1-2206632 | Discussion on HARQ operation for IoT NTN | Xiaomi |
| R1-2206850 | Disabling of HARQ feedback for IoT NTN | Samsung |
| R1-2206881 | Disabling of HARQ feedback for IoT NTN | Nordic Semiconductor ASA |
| R1-2206933 | Discussion on disabling of HARQ feedback for IoT NTN | CMCC |
| R1-2207080 | On disabling HARQ feedback for IOT-NTN | Mavenir |
| R1-2207144 | Discussions on disabling of HARQ feedback for IoT NTN | Sharp |
| R1-2207150 | Disabling HARQ feedback in IoT-NTN | InterDigital, Inc. |
| R1-2207257 | Disabling HARQ Feedback for IoT-NTN | Qualcomm Incorporated |
| R1-2207291 | Disabling of HARQ feedback for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2207295 | Disabling of HARQ feedback for IoT NTN | Lenovo |
| R1-2207355 | HARQ Feedback Disabling for IoT NTN | Apple |
| R1-2207570 | On disabling HARQ feedback for IoT NTN | Ericsson |
| R1-2207772 | FLS#1 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| R1-2207949 | FLS#2 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| R1-2208011 | FLS#3 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2205858 | Discussion on improved GNSS operations for IoT NTN | Huawei, HiSilicon |
| R1-2206011 | Discussion on improved GNSS operations for IoT NTN | Spreadtrum Communications |
| R1-2206023 | Discussion on improved GNSS operation for IoT-NTN | ZTE |
| R1-2206140 | Improved GNSS operations for IoT NTN | MediaTek Inc. |
| R1-2206313 | Discussion on improved GNSS operations for IoT NTN | OPPO |
| R1-2206389 | Improved GNSS operations for IoT NTN | CATT |
| R1-2206633 | Discussion on improved GNSS operation for IoT NTN | Xiaomi |
| R1-2206851 | Improved GNSS operations for IoT NTN | Samsung |
| R1-2206882 | Improved GNSS operations for IoT NTN | Nordic Semiconductor ASA |
| R1-2206934 | Discussion on improved GNSS operations for IoT NTN | CMCC |
| R1-2207151 | On improved GNSS operation for IoT-NTN | InterDigital, Inc. |
| R1-2207258 | Improved GNSS Operations for IoT-NTN | Qualcomm Incorporated |
| R1-2207259 | On improved GNSS operation in IoT NTN | Ericsson Limited |
| R1-2207292 | Enhancements for long connections in NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2207296 | Improved GNSS operations for IoT NTN | Lenovo |
| R1-2207356 | On Improved GNSS Operations for IoT NTN | Apple |
| R1-2207736 | Feature lead summary#1 of AI 9.12.4 on improved GNSS operations | Moderator (MediaTek) |
| R1-2207737 | Feature lead summary#2 of AI 9.12.4 on improved GNSS operations | Moderator (MediaTek) |
| R1-2208066 | Feature lead summary#3 of AI 9.12.4 on improved GNSS operations | Moderator (MediaTek) |