| 2 | Approval of Agenda | |
|---|---|---|
| R1-2203010 | Draft Agenda of RAN1#109-e meeting | RAN1 Chair |
| R1-2203012 | RAN1#109-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2203013 | Additional Guidelines for RAN1#109-e-Meeting Management | RAN1 Chair |
| R1-2203217 | Draft Agenda of RAN1#109-e meeting | RAN1 Chair |
| 3 | Highlights from RAN plenary | |
| R1-2204042 | Highlights from RAN#95-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2203011 | Report of RAN1#108-e meeting | ETSI MCC |
| R1-2205193 | Report of RAN1#108-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2203014 | Response LS on determination of location estimates in local co-ordinates | SA2, Ericsson |
| R1-2203015 | LS on RAN feedback for low latency | SA2, Huawei |
| R1-2203016 | LS on QoS support with PDU Set granularity | SA2, Intel |
| R1-2203017 | Reply LS on beam correspondence with SDT in RRC_INACTIVE | RAN4, Huawei |
| R1-2203018 | LS on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR | RAN4, Apple |
| R1-2203019 | Reply LS on NTN UL time and frequency synchronization requirements | RAN4, Xiaomi |
| R1-2203020 | Reply LS on combination of open and closed loop TA control in NTN | RAN4, Qualcomm |
| R1-2203021 | ReplyLS on L1-RSRP measurement behaviour when SSBs associated with different PCIs overlap | RAN4, vivo |
| R1-2203022 | LS on lower Rx beam sweeping factor for latency improvement | RAN4, Intel |
| R1-2203023 | LS reply on condition of PRS measurement outside MG | RAN4, vivo |
| R1-2203024 | LS on the UE/TRP TEG framework | RAN4, CATT |
| R1-2203025 | Reply LS on propagation delay compensation | RAN4, Huawei |
| R1-2203026 | On applicable number of PFL for the gapless PRS measurement | RAN4, Ericsson |
| R1-2203027 | LS to RAN1 on sensing beam characteristics | RAN4, Ericsson |
| R1-2203028 | Reply LS on latency improvement for PRS measurement with MG | RAN4, Huawei |
| R1-2203029 | Reply LS on Length of Maximum duration for TDD | RAN4, China Telecom |
| R1-2203030 | Reply LS on power control for NR-DC | RAN4, OPPO, vivo |
| R1-2203031 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2203032 | LS on Rel-17 RAN4 UE feature list for NR | RAN4, CMCC |
| R1-2203033 | LS on collision handling of concurrent MGs | RAN4, MediaTek inc. |
| R1-2203034 | LS on R17 MG enhancement - NCSG | RAN4, Apple |
| R1-2203035 | Reply LS on UE capabilities for RedCap from RRM perspective | RAN4, Ericsson |
| R1-2203036 | Reply LS to RAN2 on RLM/BFD relaxation for ePowSav | RAN4, vivo |
| R1-2203037 | LS to RAN2 on UL gap in FR2 RF enhancement | RAN4, Apple |
| R1-2203038 | Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN4, Huawei |
| R1-2203039 | LS on FR2 RedCap UE | RAN4, Ericsson |
| R1-2203040 | Questions concerning the implementation of RAN1 agreements in NRPPa | RAN3, Ericsson |
| R1-2203041 | Reply LS on paging subgrouping and PEI | RAN3, ZTE |
| R1-2203042 | LS to RAN1 on the inter-UE coordination mechanism | RAN2, vivo |
| R1-2203043 | LS on BWP operation without bandwidth restriction | RAN2, Qualcomm |
| R1-2203044 | LS on HARQ process for MCCH and Broadcast MTCH(s) | RAN2, Samsung |
| R1-2203045 | Reply LS on PDCCH Blind Detection in CA | RAN2, HiSilicon |
| R1-2203046 | LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN2, Ericsson |
| R1-2203047 | Reply LS on Signalling of PC2 V2X intra-band concurrent operation | RAN2, Xiaomi |
| R1-2203048 | Reply LS on Pemax for NR-V2X | RAN2, Huawei, CATT |
| R1-2203049 | Reply LS on interruption for PUCCH Scell activation in invalid TA case | RAN2, CATT |
| R1-2203050 | LS on coordination of R17 gap features | RAN2, MediaTek |
| R1-2203051 | LS on TCI state indication | RAN2, MediaTek |
| R1-2203052 | LS on presentation of EUWENA and involvement in 3GPP on Non Public Network | EUWENA (European Users Wireless Enterprise Network Association |
| R1-2203077 | Draft reply LS on PDCCH Blind Detection in CA | Huawei, HiSilicon |
| R1-2203098 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Huawei, HiSilicon |
| R1-2203101 | Remaining issues on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R1-2203120 | On introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2203183 | [Draft] Reply LS on PDCCH Blind Detection in CA | ZTE |
| R1-2203218 | UE capabilities for MBS | SA2, Qualcomm |
| R1-2203219 | LS on UE Power Saving for XR and Media Services | SA2, Nokia |
| R1-2203245 | [Draft] Reply LS on HARQ process for MCCH and Broadcast MTCH(s) | ZTE |
| R1-2203246 | [Draft] Reply UE capabilities for MBS | ZTE |
| R1-2203299 | Discussion on LS on HARQ process for MCCH and Broadcast MTCH(s) | Spreadtrum Communications |
| R1-2203356 | About LS on Inter-UE coordination from RAN2 | ZTE, Sanechips |
| R1-2203393 | Discussion of SA2 LS on RAN feedback for Low Latency | Ericsson |
| R1-2203394 | Discussion of RAN2 LS on PDCCH Blind Detection in CA | Ericsson |
| R1-2203395 | Discussion of SA2 LS on UE Power Saving for XR and Media Services | Ericsson |
| R1-2203406 | Discussion on lower Rx beam sweeping factor for latency improvement | CATT |
| R1-2203407 | Draft reply LS on lower Rx beam sweeping factor for latency improvement | CATT |
| R1-2203408 | Discussion on the UE/TRP TEG framework | CATT |
| R1-2203409 | Draft reply LS on the UE/TRP TEG framework | CATT |
| R1-2203410 | Discussion on applicable number of PFL for the gapless PRS measurement | CATT |
| R1-2203411 | Draft reply LS on applicable number of PFL for the gapless PRS measurement | CATT |
| R1-2203412 | Discussion on questions concerning the implementation of RAN1 agreements in NRPPa | CATT |
| R1-2203413 | Draft reply LS on questions concerning the implementation of RAN1 agreements in NRPPa | CATT |
| R1-2203414 | Draft reply LS on the inter-UE coordination mechanism | CATT, GOHIGH |
| R1-2203487 | Discussion on UE Power Saving for XR and Media Services | vivo |
| R1-2203488 | Draft Reply LS on PDCCH Blind Detection in CA | vivo |
| R1-2203489 | Draft Reply LS on lower Rx beam sweeping factor for latency improvement | vivo |
| R1-2203490 | Draft Reply LS on applicable number of PFL for the gapless PRS measurement | vivo |
| R1-2203491 | Draft Reply LS on questions concerning the implementation of RAN1 agreements in NRPPa | vivo |
| R1-2203492 | Draft reply LS on HARQ process for MCCH and Broadcast MTCH(s) | vivo |
| R1-2203493 | Draft reply LS on the inter-UE coordination mechanism | vivo |
| R1-2203494 | Draft Reply LS on BWP operation without bandwidth restriction | vivo |
| R1-2203495 | Draft Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | vivo |
| R1-2203496 | Discussion on power control for NR-DC in FR2 | vivo |
| R1-2203497 | Draft Reply LS on MBS UE capabilities | vivo |
| R1-2203590 | Discussion on NCD-SSB offset | ZTE, Sanechips |
| R1-2203591 | Discussion on UE power saving for XR and media services | ZTE, Sanechips |
| R1-2203592 | Draft reply LS on UE power saving for XR and media services | ZTE, Sanechips |
| R1-2203615 | Draft reply LS on questions of RAN1 agreements in NRPPa | ZTE |
| R1-2203616 | Draft reply LS on lower Rx beam sweeping factor | ZTE |
| R1-2203617 | Draft reply LS on applicable number of PFL for the gapless PRS measurement | ZTE |
| R1-2203709 | Discussion on LS to RAN1 on the inter-UE coordination mechanism | LG Electronics |
| R1-2203766 | Draft reply to LS on HARQ process for MCCH and Broadcast MTCH(s) | xiaomi |
| R1-2203768 | [Draft] Reply LS on the inter-UE coordination mechanism | xiaomi |
| R1-2203846 | Draft reply LS on BWP operation without bandwidth restriction | Samsung |
| R1-2203847 | Draft reply on applicable number of PFL for the gapless PRS measurement | Samsung |
| R1-2203848 | Draft Reply LS to RAN1 on the inter-UE coordination mechanism | Samsung |
| R1-2203849 | Discussion on RAN2 LS on PDCCH Blind Detection in CA | Samsung |
| R1-2203963 | Discussion on “Questions concerning the implementation of RAN1 agreements in NRPPa” | OPPO |
| R1-2203964 | Discussion on LS on lower Rx beam sweeping factor for latency improvement | OPPO |
| R1-2203969 | Discussion on the LS from RAN2 on the inter-UE coordination mechanism | OPPO |
| R1-2203970 | Draft reply on LS from RAN2 on the inter-UE coordination mechanism | OPPO |
| R1-2203976 | Discussion on the LS from RAN2 on HARQ process for MCCH and Broadcast MTCH(s) | OPPO |
| R1-2203977 | Draft reply on LS from RAN2 on HARQ process for MCCH and Broadcast MTCH(s) | OPPO |
| R1-2204035 | Discussion of BWP operation without bandwidth restriction | Ericsson |
| R1-2204116 | Discussion on LS from RAN4 on directional LBT | Ericsson |
| R1-2204126 | Discussion on LS on UE Power Saving for XR and Media Services | InterDigital, Inc. |
| R1-2204195 | Draft reply LS on inter-UE coordination mechanism | Apple |
| R1-2204270 | Discussion on RAN2 LS on HARQ process for MCCH and Broadcast MTCH(s) | CMCC |
| R1-2204271 | Discussion on RAN2 LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | CMCC |
| R1-2204272 | Discussion on RAN2 LS on BWP operation without bandwidth restriction | CMCC |
| R1-2204273 | Discussion on SA2 LS on UE capabilities for MBS | CMCC |
| R1-2204331 | [Draft] Reply LS on BWP operation without bandwidth restriction | ZTE |
| R1-2204333 | Discussion on BWP operation without bandwidth restriction | NTT DOCOMO, INC. |
| R1-2204434 | Discussion on LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | NEC |
| R1-2204445 | Discussion on LS on HARQ process for MCCH and Broadcast MTCH(s) | Spreadtrum Communications |
| R1-2204658 | Discussion on RAN4 LS on combination of open and closed loop TA control | Ericsson |
| R1-2204716 | Discussion on RAN2 LS on HARQ process for MCCH and Broadcast MTCH | MediaTek Inc. |
| R1-2204732 | [Draft] LS on PEMAX for NR-V2X | Ericsson |
| R1-2204733 | Discussion on LS on PEMAX for NR-V2X | Ericsson |
| R1-2204734 | [Draft] Reply LS to the RAN2 LS on the inter-UE coordination mechanism | Ericsson |
| R1-2204735 | Discussion on the LS from RAN2 on the inter-UE coordination mechanism | Ericsson |
| R1-2204821 | On the PL-RS configuration of PUCCH SCell to be activated | Nokia, Nokia Shanghai Bell |
| R1-2204880 | On configuration of p-MaxEUTRA and p-NR-FR1 | Nokia, Nokia Shanghai Bell |
| R1-2204894 | Discussion on PDCCH Blind Detection in CA | Huawei, HiSilicon |
| R1-2204899 | Discussion on LS from RAN2 on the inter-UE coordination mechanism | Huawei, HiSilicon |
| R1-2204920 | Discussion on BWP operation without bandwidth restriction | Huawei, HiSilicon |
| R1-2204921 | Discussion on LS from RAN4 on FR2 RedCap UE | Huawei, HiSilicon |
| R1-2204923 | Discussion on lower Rx beam sweeping factor | Huawei, HiSilicon |
| R1-2204924 | Discussion on UE/TRP TEG framework | Huawei, HiSilicon |
| R1-2204925 | Discussion on applicable number of PFLs for the gap-less PRS measurement | Huawei, HiSilicon |
| R1-2204926 | Discussion on LS from SA2 on UE Power Saving for XR and Media Services | Huawei, HiSilicon |
| R1-2204927 | Discussion on HARQ process for MCCH and broadcast MTCH(s) | Huawei, HiSilicon |
| R1-2204928 | Discussion on UE capabilities for receiving MBS broadcast | Huawei, HiSilicon |
| R1-2204929 | Draft reply LS on Questions concerning the implementation of RAN1 agreements in NRPPa | Huawei, HiSilicon |
| R1-2204956 | Views on UE capabilities for MBS | Ericsson |
| R1-2204965 | Discussion on Reply LS from RAN4 on power control for NR-DC | Ericsson |
| R1-2204966 | Discussion and Draft Reply to LS on Length of Maximum Duration | Ericsson |
| R1-2204967 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Qualcomm Incorporated |
| R1-2204968 | Draft Reply LS to RAN2 on the inter-UE coordination mechanism | Qualcomm Incorporated |
| R1-2204969 | Draft reply LS on UE Power Saving for XR and Media Services | Qualcomm Incorporated |
| R1-2204970 | Discussion on SA2 LS on UE capabilities of NR MBS broadcast reception | Qualcomm Incorporated |
| R1-2204971 | Discussion on RAN2 LS on BWP operation without bandwidth restriction | Qualcomm Incorporated |
| R1-2205090 | Reply LS on updated Rel-17 RAN1 UE features list for NR | RAN2, Intel |
| R1-2205091 | LS on further questions on feMIMO RRC parameters | RAN2, Ericsson |
| R1-2205092 | [Draft] Reply LS on further questions on feMIMO RRC parameters | vivo |
| R1-2205093 | [Draft] Reply LS on updated Rel-17 RAN1 UE features list for NR | vivo |
| R1-2205114 | On RAN2 LS regarding Rel-17 RAN1 UE features list for NR | Nokia, Nokia Shanghai Bell |
| R1-2205116 | LS on Rel-18 WI related to vehicular distributed antenna systems | 5GAA WG4, LG Electronics |
| R1-2205148 | Incoming LS handling for RAN1#109-e | RAN1 Chair |
| R1-2205243 | LS on TCI state signalling for SRS resource | RAN2, OPPO |
| R1-2205250 | LS on eIAB MAC CEs | RAN2, Samsung |
| R1-2205455 | Summary of [109-e-AI5-LSs-01]: Email discussion for incoming LS on BWP operation without bandwidth restriction | Moderator (Qualcomm Inc.) |
| R1-2205459 | [109-e-AI5-LSs-02] Email discussion for incoming LS on UE capabilities for MBS (R1-2203218) | Moderator (Qualcomm Incorporated) |
| R1-2205460 | DRAFT Reply LS on UE capabilities of MBS | Moderator (Qualcomm Incorporated) |
| R1-2205461 | Reply LS on UE capabilities of MBS | RAN1, Qualcomm Incorporated |
| R1-2205462 | [Draft] Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Moderator (Huawei) |
| R1-2205463 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | RAN1, Huawei |
| R1-2205464 | Draft reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | Moderator (Huawei) |
| R1-2205465 | Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 | RAN1, Huawei |
| R1-2205469 | Summary of email discussion [109-e-AI5-LSs-04] on UE capability of cross PUCCH-group CSI reporting | Moderator (Huawei) |
| R1-2205493 | LS on expected AoA and AoD parameters | RAN2, Huawei |
| R1-2205545 | Reply LS on operation with and without SSB for RedCap UE | RAN2, ZTE |
| R1-2205546 | Summary of email discussion [109-e-AI5-LSs-03] on reply LS to R1-2200873 and R1-2203038 | Moderator (Huawei) |
| 7.1 | Maintenance on NR Releases 15 | |
| R1-2203104 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | Huawei, HiSilicon |
| R1-2203112 | Discussion on PL-RS configuration of SCells | Huawei, HiSilicon |
| R1-2203113 | Corrections on PL-RS configuration | Huawei, HiSilicon |
| R1-2203130 | Discussion on the collision of more than two overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2203182 | Discussion on HARQ-ACK multiplexing on PUSCH | ZTE |
| R1-2203271 | Draft CR on sequence hopping of PUSCH DMRS with mapping type B | ZTE |
| R1-2203415 | Discussion on HARQ-ACK multiplexing in PUSCH without PUCCH | CATT |
| R1-2203416 | Clarification of C-DAI ordering | CATT |
| R1-2203417 | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | CATT |
| R1-2203498 | Timeline requirement for re-transmission of MSG1 and MSGA | vivo |
| R1-2203499 | Maintenance on SRS carrier switching | vivo |
| R1-2203500 | Draft Rel-15 CR on TCI state or the QCL assumption for multi-slot PDSCH | vivo |
| R1-2203501 | Draft Rel-16 mirror CR on TCI state or the QCL assumption for multi-slot PDSCH | vivo |
| R1-2203502 | Draft Rel-17 mirror CR on TCI state or the QCL assumption for multi-slot PDSCH | vivo |
| R1-2203618 | Discussion on SRS carrier switching | ZTE |
| R1-2203850 | Clarification on SRS carrier switching | Samsung |
| R1-2204052 | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | CATT |
| R1-2204117 | Correction for Frequency Hopping with Msg3 | Ericsson |
| R1-2204196 | On Remaining issues for PUSCH UCI Multiplexing without HARQ-ACK PUCCH | Apple |
| R1-2204554 | HARQ-ACK multiplexing on PUSCH without PUCCH | Ericsson, Nokia, Nokia Shanghai Bell |
| R1-2204555 | Correction for parallel transmission of SRS and PUSCH/PUCCH | Ericsson |
| R1-2204681 | Maintenance of Rel-15 RSRQ definition | MediaTek Inc. |
| R1-2204760 | Discussion on HARQ-ACK multiplexing on PUSCH | Intel Corporation |
| R1-2204761 | Discussion on SRS carrier switching | Intel Corporation |
| R1-2204762 | Discussion on gap symbol collision handling for antenna switching | Intel Corporation |
| R1-2204907 | Correction on the collision of more than two overlapped PUCCHs with repetition | Huawei, HiSilicon |
| R1-2204932 | Discussion on SRS carrier switching | Huawei, HiSilicon |
| R1-2204972 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2204973 | On parallel transmission of SRS and other channels | Qualcomm Incorporated |
| R1-2204974 | Issue on PUCCH overlapping with PUCCH with repetitions | Qualcomm Incorporated |
| R1-2205149 | Rel-15 NR maintenance handling for RAN1#109-e | RAN1 Chair |
| R1-2205262 | Summary of email discussion [109-e-NR-CRs-08]: Correction for parallel transmission of SRS and PUSCH/PUCCH | Moderator (Ericsson) |
| R1-2205272 | [109-e-NR-CRs-11] Email discussion summary for maintenance of Rel-15 RSRQ definition | Moderator (MediaTek Inc.) |
| R1-2205294 | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | Moderator (CATT), Ericsson |
| R1-2205295 | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | Moderator (CATT), Ericsson |
| R1-2205297 | Summary for [109-e-NR-CRs-05] Discussion on timeline requirement for MSG1 and MSGA retransmission | Moderator (vivo) |
| R1-2205301 | Summary of [109-e-NR-CRs-07] Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | Moderator (CATT) |
| R1-2205331 | Summary of [109-e-NR-CRs-09] Discussion on gap symbol collision handling for antenna switching | Moderator (Intel) |
| R1-2205342 | Summary of [109-e-NR-CRs-03] Collision of more than two overlapped PUCCHs with repetition | Moderator (Samsung) |
| R1-2205352 | Summary of [109-e-NR-CRs-13] TCI state or the QCL assumption for multi-slot PDSCH | Moderator (vivo) |
| R1-2205359 | Summary of [109-e-NR-CRs-04] Clarification of C-DAI ordering | Moderator (CATT) |
| R1-2205387 | Timeline requirement for retransmitting MSG1 | Moderator (vivo) |
| R1-2205388 | Timeline requirement for retransmit MSG1/MSGA | Moderator (vivo) |
| R1-2205389 | Timeline requirement for retransmit MSG1/MSGA | Moderator (vivo) |
| R1-2205414 | Feature lead summary#1 on [109-e-NR-CRs-06] Maintenance on SRS carrier switching | Moderator (vivo) |
| R1-2205585 | Correction for parallel transmission of SRS and PUSCH/PUCCH | Moderator (Ericsson), Apple, Nokia, Nokia Shanghai Bell, LG Electronics, NTT DOCOMO INC., Fujitsu |
| R1-2205586 | Correction for parallel transmission of SRS and PUSCH/PUCCH | Moderator (Ericsson), Apple, Nokia, Nokia Shanghai Bell, LG Electronics, NTT DOCOMO INC., Fujitsu |
| R1-2205599 | [Draft CR] Corrections on SRS carrier switching | Moderator (vivo), CATT, Samsung, Apple, Qualcomm, ZTE |
| R1-2205605 | Corrections on SRS carrier switching | Moderator (vivo), CATT, Samsung, Apple, Qualcomm, ZTE |
| R1-2205616 | Feature lead summary#2 on [109-e-NR-CRs-06] Maintenance on SRS carrier switching | Moderator (vivo) |
| R1-2205624 | [109-e-NR-CRs-12] On parallel transmission of SRS and other channels | Moderator (Qualcomm) |
| R1-2205625 | Simultaneous transmission of SRS and other channels for intra-band non-contiguous carrier aggregation | Moderator (Qualcomm), Ericsson, NTT DOCOMO, INC. |
| R1-2205627 | Summary for [109-e-NR-CRs-01] HARQ-ACK multiplexing on PUSCH without PUCCH | Moderator (Apple) |
| R1-2205628 | Correction for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | Moderator (Apple), Ericsson, CATT |
| R1-2205629 | Correction for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | Moderator (Apple), Ericsson, CATT |
| R1-2205634 | LS on New UE Feature for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | RAN1, Apple |
| R1-2205637 | Summary of email discussion [109-e-NR-CRs-02] PL-RS configuration of Scells | Moderator (Huawei) |
| 7.2 | Maintenance on NR Releases 16 | |
| R1-2205645 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2205646 | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | Samsung |
| R1-2205684 | Rel-16 editorial corrections for TS 37.213 | Ericsson |
| R1-2205685 | Rel-16 editorial corrections for TS 37.213 (mirrored to Rel-17) | Ericsson |
| R1-2205686 | Rel-16 editorial corrections for TS 38.212 | Huawei |
| R1-2205687 | Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) | Huawei |
| R1-2205688 | Rel-16 editorial corrections for TS 38.214 | Nokia |
| R1-2205689 | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | Nokia |
| R1-2205690 | Clarification of PUSCH DM-RS generation | Ericsson |
| R1-2205691 | Clarification of PUSCH DM-RS generation | Ericsson |
| 7.2.1 | Maintenance on Two step RACH for NR | |
| R1-2204118 | Correction for Frequency Hopping for 2-Step RACH | Ericsson |
| R1-2204700 | On delta value of SRS power control | MediaTek Inc. |
| R1-2204870 | Correction for Frequency Hopping for 2-Step RACH | Ericsson |
| R1-2205108 | Summary of preparation phase email discussion for Rel-16 2-step RACH | Moderator (ZTE) |
| R1-2205273 | [109-e-R16-2Step-RACH-01] Email discussion summary for the draft CR in R1-2204700 | Moderator (MediaTek Inc.) |
| R1-2205274 | Correction on Rel-16 SRS power control with 2-step RACH | Moderator (MediaTek Inc.) |
| R1-2205275 | Correction on Rel-16 SRS power control with 2-step RACH | Moderator (MediaTek Inc.) |
| R1-2205303 | [109-e-R16-2Step-RACH-01] Email discussion/approval the draft CR in R1-2204700 | Moderator (MediaTek) |
| R1-2205557 | Session notes for 7.2.1 (Maintenance of Two step RACH for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.2 | Maintenance on NR-based Access to Unlicensed Spectrum | |
| R1-2203084 | Corrections on semi-static channel occupancy in TS 37.213 | Huawei, HiSilicon |
| R1-2203296 | Correction on RRC parameter for semi-static channel access procedure in TS 38.213 | ZTE, Sanechips |
| R1-2203297 | Correction on RRC parameter for semi-static channel access procedure in TS 37.213 | ZTE, Sanechips |
| R1-2203298 | Correction on RRC parameter for semi-static channel access procedure in TS 38.212 | ZTE, Sanechips |
| R1-2204639 | Correction on assumption of SSB transmission | ASUSTeK |
| R1-2205123 | Summary of preparation phase email discussion for Rel.16 NR-U maintenance | Moderator (Qualcomm) |
| R1-2205245 | FL summary on editorial changes to specs' editors on RRC parameter name alignment for semi-static channel access procedure | Moderator (Qualcomm) |
| R1-2205558 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Huawei) |
| 7.2.4 | Maintenance on 5G V2X with NR sidelink | |
| R1-2203357 | Correction on UE procedure for reporting HARQ-ACK on uplink in TS 38.213 | ZTE, Sanechips |
| R1-2203358 | Correction to the parameter name on SL synchronization in TS 38.213 | ZTE, Sanechips |
| R1-2203503 | Clarification on reporting SL HARQ-ACK on uplink | vivo |
| R1-2203504 | Correction on SL HARQ-ACK reporting | vivo |
| R1-2203609 | Correction on DCI format 3_1 in TS 38.212 | ZTE, Sanechips |
| R1-2203671 | Draft CR on reporting sidelink HARQ-ACK on uplink for SL CG Type 2 PSSCH transmission | NEC |
| R1-2203672 | Draft CR on Type-1 HARQ-ACK codebook for reporting sidelink HARQ-ACK on uplink | NEC |
| R1-2204172 | Clarification on Configuration Index field in DCI format 3_0 | Sharp |
| R1-2204901 | Correction for slots determination in a resource pool | Huawei, HiSilicon |
| R1-2205197 | Moderator summary #1 of [109-e-R16-V2X-03] Alignment CR on TS 38.212 | Moderator (ZTE) |
| R1-2205198 | Moderator summary #2 of [109-e-R16-V2X-03] Alignment CR on TS 38.212 | Moderator (ZTE) |
| R1-2205242 | Summary of [109-e-R16-V2X-05] Alignment CR on TS 38.214 | Moderator (Huawei) |
| R1-2205248 | Summary of email discussion on [109-e-R16-V2X-04] Alignment CR on TS 38.213 | Moderator (NEC) |
| R1-2205298 | Summary of email discussion on [109-e-R16-V2X-01] Clarification on reporting SL HARQ-ACK on uplink for SL CG Type 2 | Moderator (NEC) |
| R1-2205299 | CR on reporting sidelink HARQ-ACK on uplink for SL CG Type 2 PSSCH transmission | Moderator (NEC) |
| R1-2205300 | CR on reporting sidelink HARQ-ACK on uplink for SL CG Type 2 PSSCH transmission | Moderator (NEC) |
| R1-2205365 | Summary of [109-e-R16-V2X-02] Clarification on N_CG value in SL HARQ-ACK reporting | Moderator (vivo) |
| R1-2205395 | Correction on SL HARQ-ACK reporting | Moderator (vivo), ZTE, Sanechips, Ericsson, Huawei, HiSilicon, OPPO, Nokia, Nokia Shanghai Bell |
| R1-2205396 | Correction on SL HARQ-ACK reporting | Moderator (vivo), ZTE, Sanechips, Ericsson, Huawei, HiSilicon, OPPO, Nokia, Nokia Shanghai Bell |
| R1-2205397 | Summary of [109-e-R16-V2X-02] Clarification on N_CG value in SL HARQ-ACK reporting | Moderator (vivo) |
| 7.2.5 | Maintenance on Physical Layer Enhancements for NR URLLC | |
| R1-2203075 | Remaining issues on UCI multiplexing and prioritization | Huawei, HiSilicon |
| R1-2203076 | Remaining issues on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | Huawei, HiSilicon |
| R1-2203111 | Remaining issues on SRS | Huawei, HiSilicon |
| R1-2203184 | Correction on PDCCH reception with last symbol aligning with the first symbol of UL CI for Rel-16 | ZTE |
| R1-2203185 | Discussion on non-overlapping PUCCHs with repetition | ZTE |
| R1-2203186 | The remaining issues on intra-UE multiplexing | ZTE |
| R1-2203277 | Clarification on HARQ-ACK feedback with PUCCH repetition | Nokia, Nokia Shanghai Bell |
| R1-2203278 | [Draft CR] Correction on UE procedure for intra-UE prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2203279 | [Draft CR] Intra-UE prioritization/multiplexing considering PUCCH repetition | Nokia, Nokia Shanghai Bell |
| R1-2203300 | Discussion on UE procedures for UCI multiplexing and prioritization | Spreadtrum Communications |
| R1-2203396 | Resolving Collision of HARQ-ACK with Repetition | Ericsson |
| R1-2203418 | PUCCH collision handling in case of PUCCH repetition | CATT |
| R1-2203419 | Discussion on intra-UE multiplexing/prioritization for eURLLC | CATT |
| R1-2203851 | Remaining issues on intra-UE multiplexing/prioritization | Samsung |
| R1-2204000 | Discussion on scheduling and HARQ enhancement | OPPO |
| R1-2204001 | Clarification on collision handling for overlapping PUCCHs with repetitions | OPPO |
| R1-2204197 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple, Ericsson, OPPO, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2204438 | Correction on RRC parameter name of dl-DataToUL-ACK-ForDCI-Format1-2 in TS 38.213 | ITRI |
| R1-2204446 | Discussion on UE procedures for UCI multiplexing and prioritization | Spreadtrum Communications |
| R1-2204895 | Remaining issues on UL prioritization cases related to SP-CSI | Huawei, HiSilicon |
| R1-2204905 | Correction on SRS resource set with 'antennaSwitching' | Huawei, HiSilicon |
| R1-2204975 | Discussion on Rel-16 Span-based PDCCH monitoring | Qualcomm Incorporated |
| R1-2205132 | Summary of preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2205319 | Draft reply LS on PDCCH Blind Detection in CA | Huawei |
| R1-2205320 | Reply LS on PDCCH Blind Detection in CA | RAN1, Huawei |
| R1-2205321 | Summary of [109-e-R16-URLLC-08] on incoming LS (in R1-2203045) from RAN2 on PDCCH blind detection in CA | Moderator (Huawei) |
| R1-2205343 | Summary of [109-e-R16-URLLC-06] Issue#9 & Issue#11: Editorial corrections for recommendations to editors | Moderator (Samsung) |
| R1-2205348 | Correction on PDCCH reception with last symbol aligning with the first symbol of UL CI for Rel-16 | Moderator (ZTE) |
| R1-2205349 | Correction on PDCCH reception with last symbol aligning with the first symbol of UL CI for Rel-17 | Moderator (ZTE) |
| R1-2205350 | Summary of [109-e-R16-URLLC-05] Issue#7: Correction on PDCCH reception with last symbol aligning with the first symbol of UL CI for Rel-16 | Moderator (ZTE) |
| R1-2205370 | Summary of [109-e-R16-URLLC-02] Issue#4: Remaining issues on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | Moderator (Nokia) |
| R1-2205385 | Summary #1 of email discussion [109-e-R16-URLLC-01] on UCI multiplexing and prioritization in Rel-16 | Moderator (Apple) |
| R1-2205436 | Summary of [109-e-R16-URLLC-03] Issue#3: Discussion on SRS configurations with usage of 'beamManagement' in srs-ResourceSetToAddModListDCI-0-2 | Moderator (Huawei) |
| R1-2205437 | Correction on SRS resource set with 'antennaSwitching' and ‘beamManagement’ | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2205438 | Correction on SRS resource set with 'antennaSwitching' and ‘beamManagement’ | Moderator (Huawei), HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2205439 | Summary of [109-e-R16-URLLC-04] Issue#6: Correction on SRS resource set with ‘antennaSwitching’ | Moderator (Huawei) |
| R1-2205440 | Summary of [109-e-R16-URLLC-07] Issue#8: Remaining issues on UL prioritization cases related to SP-CSI | Moderator (Huawei) |
| R1-2205606 | Final Summary of email discussion [109-e-R16-URLLC-01] on UCI multiplexing and prioritization in Rel-16 | Moderator (Apple) |
| 7.2.6 | Maintenance on Enhancements on MIMO for NR | |
| R1-2203272 | Draft CR on type II HARQ-ACK codebook for Multi-TRP transmission | ZTE |
| R1-2203420 | Clarification of TPMI indication for UL full power transmission | CATT |
| R1-2203852 | Moderator summary for Rel-16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2204161 | Draft CR on type II HARQ-ACK codebook with multiple PDSCHs scheduled by one TRP in a slot | ZTE |
| R1-2204931 | Discussion on triggering offset of aperiodic CMR and IMR set for L1-SINR | Huawei, HiSilicon |
| R1-2205154 | Summary of [109-e-R16-MIMO-01] | Moderator (Huawei) |
| R1-2205322 | Clarification of TPMI indication for UL full power transmission | Moderator(CATT), Huawei, HiSilicon, Ericsson |
| R1-2205323 | Clarification of TPMI indication for UL full power transmission | Moderator(CATT), Huawei, HiSilicon, Ericsson |
| R1-2205324 | Summary of [109-e-R16-MIMO-02] UL.1 (Editorial on UL FP PMI) | Moderator(CATT) |
| 7.2.8 | Maintenance on NR positioning support | |
| R1-2204922 | PRS reception without TDD configuration | Huawei, HiSilicon |
| R1-2204941 | Maintenance for NR positioning support | Ericsson |
| R1-2205128 | Summary of preparation phase for AI 7.2.8 Maintenance on NR positioning support | Moderator (Ericsson) |
| R1-2205254 | Summary #1 of [109-e-R16-Pos-01] on PRS reception without TDD configuration | Moderator (Huawei) |
| R1-2205559 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Huawei) |
| 7.2.10 | Maintenance on Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2203187 | Discussion on power control for NR-DC for FR2 | ZTE |
| R1-2204198 | On remaining issues for NR-NR DC Power Control | Apple |
| R1-2204334 | Discussion on power control for NR-DC in FR2 | NTT DOCOMO, INC. |
| R1-2205127 | [109-e-Prep-AI7.2.10 MR-DC/CA] Prep phase summary | Moderator (Nokia) |
| R1-2205447 | [109-e-R16-MRDC-CA-01] Email discussion on NR DC in FR2 | Moderator (Nokia) |
| R1-2205448 | Reply LS on power control for NR-DC | RAN1, Nokia |
| R1-2205560 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Huawei) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2203630 | UE capability on maximum number of layers for MTRP | ZTE |
| R1-2205115 | Summary on Rel-16 NR UE features related discussion | Moderator (NTT DOCOMO, INC) |
| R1-2205142 | Summary on [109-e-R16-UE-features-MIMO-01] | Moderator (NTT DOCOMO, INC.) |
| 8.1 | Maintenance on Further enhancements on MIMO for NR | |
| R1-2203853 | On RAN2 open issues for Rel-17 NR FeMIMO | Samsung |
| R1-2203854 | Moderator summary for offline discussion on reply to RAN2 LS R2-2204361 | Moderator (Samsung) |
| R1-2205167 | DRAFT LS response on feMIMO RRC parameters | Samsung |
| R1-2205168 | LS response on feMIMO RRC parameters | RAN1, Samsung |
| R1-2205246 | DRAFT LS response on TCI state signaling for SRS resource | Moderator (OPPO) |
| R1-2205247 | LS response on TCI state signaling for SRS resource | RAN1, OPPO |
| R1-2205590 | DRAFT LS on RAN1#109-e agreements with RAN2 impact | Samsung |
| R1-2205591 | LS on RAN1#109-e agreements with RAN2 impact | RAN1, Samsung |
| R1-2205668 | Corrections to MIMO enhancements | Ericsson |
| R1-2205671 | Corrections on further enhancements on MIMO for NR | Samsung |
| R1-2205678 | Correction on further enhancements on MIMO for NR | Nokia |
| R1-2205682 | Corrections on Further enhancements on MIMO for NR in TS 38.212 | Huawei |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2203064 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2203105 | Remaining issues on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2203257 | Remaining issues on multi-beam enhancements | ZTE |
| R1-2203258 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 1: multi-beam | Moderator(ZTE) |
| R1-2203301 | Remaining issues on multi-beam enhancements | Spreadtrum Communications |
| R1-2203421 | Maintenance issues on Rel-17 multi-beam operation | CATT |
| R1-2203505 | Maintenance on multi-beam enhancement | vivo |
| R1-2203673 | Discussion on remaining issues on multi-beam operation | NEC |
| R1-2203764 | Maintenance of Enhancements on Multi-beam Operation | Langbo |
| R1-2203771 | Remaining issues on multi-beam operation enhancement | xiaomi |
| R1-2203855 | Maintenance on Rel-17 multi-beam | Samsung |
| R1-2203948 | Remaining Issues of Enhancements on Multi-Beam Operation | OPPO |
| R1-2204031 | Maintenance of multi-beam enhancements | Ericsson |
| R1-2204137 | Text proposal on multi-beam operation | LG Electronics |
| R1-2204169 | Remaining issues on muiti-beam operation | Lenovo |
| R1-2204192 | Maintenance issue of unified TCI power control | ASUSTeK |
| R1-2204199 | Remaining Issues on Beam Management Enhancement | Apple |
| R1-2204274 | Remaining issues of enhancements on multi-beam operation | CMCC |
| R1-2204335 | Remaining issues on multi-beam operation | NTT DOCOMO, INC. |
| R1-2204447 | Remaining issues on multi-beam enhancements | Spreadtrum Communications |
| R1-2204535 | Maintenance of enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2204680 | Maintenance of enhancements on multi-beam operation | Google Inc. |
| R1-2204682 | Maintenance of Rel-17 multi-beam operation | MediaTek Inc. |
| R1-2204763 | Enhancements on Multi-Beam Operations | Intel Corporation |
| R1-2204976 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2205130 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 1: multi-beam | Moderator(ZTE) |
| R1-2205315 | Moderator Summary #0 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2205316 | Endorsed TPs for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2205422 | Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2205630 | Further Endorsed TPs for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2205631 | Moderator Summary #2 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
| R1-2205640 | LS to RAN4 on SSB measurement for L1-RSRP on inter-cell beam management | RAN1, ZTE |
| 8.1.2 | Enhancements for Multi-TRP Deployment | |
| R1-2203106 | Remaining issues on enhancements for Multi-TRP deployment | Huawei, HiSilicon |
| R1-2203259 | Remaining issues on multi-TRP deployment | ZTE |
| R1-2203302 | Remaining issues on multi-TRP deployment | Spreadtrum Communications |
| R1-2203422 | Maintenance issues on Rel-17 M-TRP enhancements | CATT |
| R1-2203506 | Maintenance on enhancements for multi-TRP Deployment | vivo |
| R1-2203644 | Remaining issues for Multi-TRP Deployment | Ericsson |
| R1-2203674 | Discussion on remaining issues for multi-TRP deployment | NEC |
| R1-2203765 | Maintenance of Enhancements for Multi-TRP Deployment | Langbo |
| R1-2203772 | Remaining issues on HST-SFN deployment enhancement | xiaomi |
| R1-2203856 | Maintenance on Rel-17 multi-TRP and HST-SFN | Samsung |
| R1-2203949 | Maintenance on enhancements for mTRP deployment | OPPO |
| R1-2204138 | Text proposal on multi-TRP deployment | LG Electronics |
| R1-2204170 | Remaining issues on multi-TRP deployment | Lenovo |
| R1-2204193 | Remaining issues for mTRP PUSCH | ASUSTeK |
| R1-2204200 | Remaining Issues on Multi-TRP Enhancement | Apple |
| R1-2204336 | Remaining issues on enhancements for Multi-TRP Deployment | NTT DOCOMO, INC. |
| R1-2204448 | Remaining issues on multi-TRP deployment | Spreadtrum Communications |
| R1-2204536 | Maintenance of enhancements for Multi-TRP Deployment | Nokia, Nokia Shanghai Bell |
| R1-2204683 | Maintenance of Rel-17 beam management for multi-TRP | MediaTek Inc. |
| R1-2204764 | MIMO Enhancements for Multi-TRP Deployment | Intel Corporation |
| R1-2204977 | Remaining Details for Multi-TRP Operation | Qualcomm Incorporated |
| R1-2205126 | Description of issues for Rel.17 NR FeMIMO maintenance: Item 2a DL/UL | Moderator (Nokia) |
| R1-2205145 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 2d: HST | Moderator (Intel Corporation) |
| R1-2205276 | Endorsed TPs in Rel.17 NR FeMIMO maintenance: Item 2a DL/UL | Moderator (Nokia) |
| R1-2205286 | Endorsed TPs in Rel.17 NR FeMIMO maintenance on HST | Moderator (Intel Corporation) |
| R1-2205287 | Moderator Summary of Round-1 for Rel. 17 NR FeMIMO Maintenance on HST | Moderator (Intel Corporation) |
| R1-2205296 | Moderator summary #1 on enhancements of beam management for multi-TRP | Moderator (CATT) |
| R1-2205376 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 2b: inter-cell mTRP | Moderator (vivo) |
| R1-2205377 | Feature lead Summary#1 [109-e-R17-MIMO-04] Maintenance on multi-TRP inter-cell | Moderator (vivo) |
| R1-2205458 | Endorsed TPs in Rel.17 NR FeMIMO maintenance: Item 2a DL/UL | Moderator (Nokia) |
| R1-2205479 | Endorsed TPs in Rel.17 NR FeMIMO maintenance: Item 2c mTRP BM | Moderator (CATT) |
| R1-2205490 | Endorsed TPs in Rel.17 NR FeMIMO maintenance: Item 2c mTRP BM (batch 2) | Moderator (CATT) |
| R1-2205536 | Endorsed TP for Rel.17 NR FeMIMO maintenance on HST-SFN | Moderator (Intel Corporation) |
| R1-2205537 | Moderator Summary of Round-3 for Rel. 17 NR FeMIMO Maintenance on HST | Moderator (Intel Corporation) |
| R1-2205596 | Endorsed TPs in Rel.17 NR FeMIMO maintenance: Item 2b: inter-cell mTRP | Moderator (vivo) |
| R1-2205597 | Feature lead Summary#2 [109-e-R17-MIMO-04] Maintenance on multi-TRP inter-cell | Moderator (vivo) |
| 8.1.3 | Other | |
| R1-2203260 | Remaining issues on SRS and CSI enhancements | ZTE |
| R1-2203261 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 3: SRS | Moderator(ZTE) |
| R1-2203303 | Remaining issues on SRS in Rel-17 | Spreadtrum Communications |
| R1-2203423 | Maintenance issues on SRS | CATT |
| R1-2203507 | Miscellaneous correction on Rel-17 MIMO | vivo |
| R1-2203675 | Discussion on remaining issues on SRS enhancement | NEC |
| R1-2203773 | Remaining issues on M-TRP beam management, SRS and CSI enhancement | xiaomi |
| R1-2203857 | Maintenance on Rel-17 SRS and CSI | Samsung |
| R1-2203950 | Other maintenance issues on further MIMO enhancements | OPPO |
| R1-2204030 | Remaining issues on CSI enhancements for Multi-TRP | Ericsson |
| R1-2204139 | Text proposal on SRS enhancement | LG Electronics |
| R1-2204171 | Remaining issues on SRS enhancements | Lenovo |
| R1-2204337 | Remaining issues on SRS enhancements | NTT DOCOMO, INC. |
| R1-2204449 | Remaining issues on SRS in Rel-17 | Spreadtrum Communications |
| R1-2204537 | Maintenance of miscellaneous Rel-17 MIMO issues | Nokia, Nokia Shanghai Bell |
| R1-2204765 | Remaining details on SRS enhancement | Intel Corporation |
| R1-2204904 | Remaining issues on SRS enhancement in Rel-17 | Huawei, HiSilicon |
| R1-2204978 | Remaining issues for SRS enhancement | Qualcomm Incorporated |
| R1-2205195 | Moderator Summary #1 for Maintenance on Rel-17 SRS | Moderator (ZTE) |
| R1-2205196 | TP of Rel-17 CSI Enhancement for TS 38.214 | Moderator (Huawei, HiSilicon) |
| R1-2205261 | Endorsed TPs for Maintenance on Rel-17 SRS | Moderator (ZTE) |
| R1-2205403 | Moderator Summary #2 for Maintenance on Rel-17 SRS | Moderator (ZTE) |
| R1-2205472 | Moderator Summary #3 for Maintenance on Rel-17 SRS | Moderator (ZTE) |
| R1-2205538 | Further Endorsed TP for Maintenance on Rel-17 SRS | Moderator (ZTE) |
| 8.2 | Maintenance on Supporting NR from 52.6GHz to 71 GHz | |
| R1-2205124 | Summary of preparation phase email discussion for Rel.17 FR2-2 maintenance | Moderator (Qualcomm) |
| R1-2205379 | Draft LS to RAN2 on RRC parameter update for NR up to 71GHz | Moderator (Qualcomm) |
| R1-2205380 | LS to RAN2 on RRC parameter update for NR up to 71GHz | RAN1, Qualcomm |
| R1-2205561 | Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) | Ad-Hoc Chair (Huawei) |
| R1-2205647 | Corrections on extending NR operation to 71 GHz | Samsung |
| R1-2205652 | Corrections of the features extending NR operation to 71 GHz | Ericsson |
| R1-2205656 | Corrections on NR extensions of current NR operation to 71GHz | Nokia |
| R1-2205681 | Correction on extension of current NR operation to 71 GHz in 38.212 | Huawei |
| 8.2.1 | Initial access aspects | |
| R1-2203079 | Remaining issue of initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon, SIA |
| R1-2203290 | Remaining issues on initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203369 | Remaining issues for initial access operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2203430 | Remaining issues on Initial access aspects for up to 71GHz operation | CATT |
| R1-2203508 | Maintenance on initial access for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2203858 | Maintenance on initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2203986 | Discussion on remaining issue for initial access aspects | OPPO |
| R1-2204110 | Initial Access Aspects | Ericsson |
| R1-2204201 | Remaining issues for initial access aspects | Apple |
| R1-2204338 | Remaining issues on initial access aspects for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2204599 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2204611 | Remaining issues of initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2204766 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2205138 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2205139 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2205532 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2203080 | Remaining issues of PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon, SIA |
| R1-2203291 | Remaining issues on PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203370 | Remaining issues for PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2203431 | Remaining issues on PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2203509 | Maintenance on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2203859 | Maintenance on PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2203987 | Discussion on remaining issue for PDCCH monitoring enhancement | OPPO |
| R1-2204075 | Remaining issues on PDCCH monitoring | Panasonic |
| R1-2204111 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2204202 | On remaining issues for PDCCH Monitoring | Apple |
| R1-2204339 | Remaining issues on PDCCH monitoring enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2204514 | PDCCH monitoring enhancements | Sharp |
| R1-2204566 | Remaining Issues on PDCCH Monitoring Enhancements in FR2-2 | TCL Communication |
| R1-2204578 | Remaining issues of PDCCH monitoring enhancements for above 52.6GHz | Transsion Holdings |
| R1-2204600 | Remaining issues on PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204612 | Remaining issues of PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2204706 | Remaining discussion on PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2204767 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2204825 | Remaining issues on PDCCH for NR from 52.6 GHz to 71GHz | Lenovo |
| R1-2204979 | PDCCH monitoring enhancements for NR in 52p6 to 71GHz band | Qualcomm Incorporated |
| R1-2205279 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2205280 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2205466 | Correction to BD/CCE budget allocation over multiple serving cells for multi-DCI multi-TRP for FR2-2 | Ericsson |
| R1-2205518 | Correction to BD/CCE budget allocation over multiple serving cells for multi-DCI multi-TRP for FR2-2 | Ericsson |
| R1-2205523 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | PDSCH/PUSCH enhancements | |
| R1-2203081 | Remaining issues of PDSCH/PUSCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon, SIA |
| R1-2203292 | Remaining issues on data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203371 | Remaining issues for PDSCH/PUSCH enhancements to supporting 52.6-71 GHz band in NR | InterDigital, Inc. |
| R1-2203401 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic |
| R1-2203432 | Remaining issues on PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2203510 | Maintenance on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2203678 | Remaining issues of PDSCH/PUSCH enhancements for 52.6 to 71GHz | NEC |
| R1-2203708 | Remaining issues of multi-PDSCH/PUSCH scheduling via a single DCI | Fujitsu Limited |
| R1-2203784 | Remaining issues on PDSCH and PUSCH enhancements for NR 52.6-71GHz | xiaomi |
| R1-2203860 | Maintenance on PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2203988 | Discussion on remaining issue for PDSCH/PUSCH enhancements | OPPO |
| R1-2204112 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2204190 | Discussion on multi-PXSCH scheduling | ASUSTeK |
| R1-2204203 | On remaining issues for PDSCH PUSCH Enhancements | Apple |
| R1-2204340 | Remaining issues on PDSCH/PUSCH enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2204601 | Remaining issues on PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204613 | Remaining issues of PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2204707 | Remaining discussion on multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2204768 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2204980 | PDSCH and PUSCH enhancements | Qualcomm Incorporated |
| R1-2205136 | Discussion summary #1 of [109-e-R17-FR2-2-03] | Moderator (vivo) |
| R1-2205191 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2205475 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2205549 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.4 | Channel access mechanism | |
| R1-2203056 | Remaining Details in Channel access for Beyond 52.6 GHz | FUTUREWEI |
| R1-2203082 | Remaining issues of channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon, SIA |
| R1-2203293 | Remaining issues on channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203372 | Remaining issues for channel access mechanisms | InterDigital, Inc. |
| R1-2203433 | Remaining issues on channel access mechanism for up to 71GHz operation | CATT |
| R1-2203511 | Maintenance on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2203679 | Remaining issues on channel access mechanism supporting NR from 52.6 to 71 GHz | NEC |
| R1-2203785 | Remaining issues on channel access mechanism for NR on 52.6-71 GHz | xiaomi |
| R1-2203861 | Maintenance on channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2203989 | Discussion on remaining issue for channel access mechanism | OPPO |
| R1-2204113 | Channel Access Mechanisms | Ericsson |
| R1-2204204 | Remaining details on channel access mechanisms for unlicensed access above | Apple |
| R1-2204341 | Remaining issues on Channel access mechanism for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2204546 | Remaining issue on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2204567 | Remaining Issues on Channel Access for NR in 60GHz Unlicensed Band | TCL Communication |
| R1-2204579 | Remaining issues of channel access mechanism for above 52.6GHz | Transsion Holdings |
| R1-2204602 | Remaining issues on channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2204614 | Remaining issues of channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2204636 | Remaining issue on channel access scheme for above 52.6GHz | ASUSTeK |
| R1-2204769 | Discussion on Channel Access Mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2204826 | Remaining issues on channel access for NR from 52.6 GHz to 71GHz | Lenovo |
| R1-2204981 | Channel access enhancements | Qualcomm Incorporated |
| R1-2205125 | FL summary#1 of email discussion for channel access for Rel.17 FR2-2 | Moderator (Qualcomm) |
| R1-2205378 | FL summary#1 of email discussion for channel access for Rel.17 FR2-2 | Moderator (Qualcomm) |
| R1-2205581 | Draft LS to RAN4 on TCI assumption for RSSI measurement in FR2-2 | Qualcomm |
| R1-2205582 | LS on TCI assumption for RSSI measurement in FR2-2 | RAN1, Qualcomm |
| 8.2.5 | Other | |
| R1-2203294 | Remaining issues on beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203373 | Remaining issues for beam management for new SCSs | InterDigital, Inc. |
| R1-2203512 | Maintenance on beam management | vivo |
| R1-2204114 | Remaining issues for beam management | Ericsson |
| R1-2204342 | Remaining issues on beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2204603 | Supported values for SSSG switching delay for 480 kHz and 960 kHz SCS | Nokia, Nokia Shanghai Bell |
| R1-2204615 | Remaining issues of beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2204896 | Remaining issues of PUCCH enhancement and beam management enhancement for 52-71GHz spectrum | Huawei, HiSilicon, SIA |
| R1-2205244 | Discussion Summary #1 of Beam Management for New SCSs | Moderator (InterDigital) |
| R1-2205291 | FL Summary for [109-e-R17-FR2-2-06] Email discussion on whether there is ambiguity on the determination of number of RBs for PUCCH Format 4 | Moderator (Ericsson) |
| 8.3 | Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2205648 | Corrections on IIoT/URLLC enhancements in NR | Samsung |
| R1-2205653 | Correction to semi-static channel access procedures for PUSCH scheduled via RAR | Ericsson |
| R1-2205657 | Corrections on enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Nokia |
| R1-2205660 | Corrections on enhanced IIoT and URLLC in 38.212 | Huawei |
| 8.3.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2203072 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2203188 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2203212 | Remaining issues for HARQ-ACK feedback enhancements | New H3C Technologies Co., Ltd. |
| R1-2203273 | Maintenance of Rel-17 HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2203304 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2203397 | Remaining Issues of HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2203434 | Maintenance on UE feedback enhancements for HARQ-ACK | CATT |
| R1-2203513 | Remaining issues on HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2203680 | Remaining issues of HARQ-ACK feedback enhancements for IIoT/URLLC | NEC |
| R1-2203862 | Maintenance on HARQ-ACK feedback enhancements | Samsung |
| R1-2204002 | Remaining issues on HARQ-ACK enhancements | OPPO |
| R1-2204191 | Remaining issues for HARQ-ACK codebook regarding PUCCH-sSCell | ASUSTeK |
| R1-2204205 | Remaining issues in HARQ-ACK feedback enhancements | Apple |
| R1-2204343 | Remaining issues on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2204450 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2204616 | Remaining issues on HARQ-ACK feedback enhancements | LG Electronics |
| R1-2204725 | Remaining issues for UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2204982 | Remaining issues on HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2205143 | Preparatory phase FL summary for HARQ-ACK feedback enhancements for URLLC/IIoT operation [109-e-Prep-AI8.3 R17 URLLC/IIoT] | Moderator (Nokia) |
| R1-2205144 | Moderator summary #1 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205304 | Moderator summary #2 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205305 | Moderator summary #3 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205445 | Moderator summary #4 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205446 | Moderator summary #5 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205504 | Moderator summary #6 on [109-e-R17-IIoT-URLLC-01] UE feedback enhancements for HARQ-ACK | Moderator (Nokia) |
| R1-2205505 | Updated RRC parameter sheet for Rel-17 URLLC / IIoT | Moderator (Nokia) |
| R1-2205506 | [Draft] LS on Rel-17 URLLC/IIoT RRC parameter updates | Moderator (Nokia) |
| R1-2205507 | LS on Rel-17 URLLC/IIoT RRC parameter updates | RAN1, Nokia |
| 8.3.2 | Intra-UE Multiplexing/Prioritization | |
| R1-2203073 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2203189 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2203213 | Remaining issue on intra-UE multiplexing and prioritization | New H3C Technologies Co., Ltd. |
| R1-2203274 | Maintenance of Rel-17 URLLC / IIoT Intra-UE Multiplexing/Prioritization | Nokia, Nokia Shanghai Bell |
| R1-2203305 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2203398 | Remaining Issues of Intra-UE Multiplexing/Prioritization for IIoT/URLLC | Ericsson |
| R1-2203435 | Maintenance on intra-UE multiplexing and prioritization | CATT |
| R1-2203514 | Remaining issues on intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2203863 | Maintenance on Intra-UE Multiplexing/Prioritization | Samsung |
| R1-2204003 | Remaining issues on intra-UE multiplexing/prioritization | OPPO |
| R1-2204091 | Remaining issues of Intra-UE Multiplexing/Prioritization | InterDigital, Inc. |
| R1-2204206 | Remaining issues in intra-UE multiplexing/prioritization | Apple |
| R1-2204344 | Remaining issues on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2204439 | Remaining details on intra-UE multiplexing and prioritization | ITRI |
| R1-2204451 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2204547 | Remaining issues on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2204617 | Remaining issues on Intra-UE multiplexing enhancements | LG Electronics |
| R1-2204647 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2204770 | Remaining issue for Intra-UE Uplink Channel Multiplexing and Prioritization | Intel Corporation |
| R1-2204983 | Remaining issues on Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2205146 | Preparation phase FL summary for Rel-17 URLLC/IIoT intra-UE MUX A | Moderator (CATT) |
| R1-2205147 | Summary #1 of email thread [109-e-R17-IIoT-URLLC-02] | Moderator (CATT) |
| R1-2205189 | Preparation phase summary of maintenance on Rel-17 Intra-UE Multiplexing/Prioritization - B | Moderator (OPPO) |
| R1-2205190 | Summary#1 of email thread [109-e-R17-IIoT-URLLC-03] | Moderator (OPPO) |
| R1-2205306 | Summary#2 of email thread [109-e-R17-IIoT-URLLC-03] | Moderator (OPPO) |
| R1-2205360 | Summary #2 of email thread [109-e-R17-IIoT-URLLC-02] | Moderator (CATT) |
| R1-2205580 | CR on Interlace determination to support R17 intra-UE multiplexing in unlicensed band | Moderator (OPPO), Apple |
| 8.3.3 | Other | |
| R1-2203190 | The remaining issue on propagation delay compensation enhancements | ZTE |
| R1-2203275 | Maintenance of Rel-17 URLLC/IIoT Propagation Delay Compensation | Nokia, Nokia Shanghai Bell |
| R1-2203399 | Remaining Issues for Propagation Delay Compensation Enhancements | Ericsson |
| R1-2204004 | Remaining issues of URLLC PDC | OPPO |
| R1-2204618 | Remaining issues on Unlicensed band URLLC operation | LG Electronics |
| R1-2204893 | Other remaining issues for URLLC and IIoT | Huawei, HiSilicon |
| R1-2205103 | Preparatory phase FL summary for URLLC/IIoT operation on unlicensed band- [109-e-Prep-AI8.3 R17 URLLC/IIoT] | Moderator (Ericsson) |
| R1-2205104 | FL Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2205105 | FL Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2205133 | Feature lead summary on PDC for preparation phase | Moderator (Huawei) |
| R1-2205134 | Summary#1 of email discussion on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2205135 | Summary#2 of email discussion on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2205263 | Summary#1: [109-e-R17-IIoT-URLLC-04] Maintenance of URLLC/IIoT operation on unlicensed band | Moderator (Ericsson) |
| R1-2205264 | Summary#2: [109-e-R17-IIoT-URLLC-04] Maintenance of URLLC/IIoT operation on unlicensed band | Moderator (Ericsson) |
| 8.4 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2203088 | Maintenance on solutions for NR to support NTN | Huawei, HiSilicon |
| R1-2203231 | Remaining issues on NR-NTN | ZTE |
| R1-2203289 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | PANASONIC R&D Center Germany |
| R1-2203306 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | Spreadtrum Communications |
| R1-2203385 | Maintenance on Solutions for NR to support NTN | MediaTek Inc. |
| R1-2203721 | Discussion on ambiguity of common TA calculation | Sony |
| R1-2203756 | Maintenance on NR NTN | CATT |
| R1-2203770 | Discussion on maintenance issues in NR-NTN | xiaomi |
| R1-2203843 | Maintenance aspects af Rel-17 NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2203935 | Discussion on the remaining issues in R17 NR NTN | NEC |
| R1-2203990 | Discussion on remaining issue for NTN-NR | OPPO |
| R1-2204207 | On remaining issues of NR NTN | Apple |
| R1-2204345 | Remaining issues on NR NTN | NTT DOCOMO, INC. |
| R1-2204452 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | Spreadtrum Communications |
| R1-2204519 | Remaining issues on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2204556 | Maintenance on Release-17 NR NTN | THALES |
| R1-2204660 | On NR NTN maintenance issues | Ericsson |
| R1-2204933 | Enhancements on UL time and frequency synchronization | Mavenir |
| R1-2204984 | Maintenance on NR NTN | Qualcomm Incorporated |
| R1-2205120 | Moderator Summary for preparation phase on maintenance of Rel-17 WI on Solutions for NR to support non-terrestrial networks (NTN) | Moderator (Thales) |
| R1-2205232 | Summary#1 of Email discussion for maintenance on scheduling and HARQ for NR NTN | Moderator (ZTE) |
| R1-2205337 | FL Summary #1: Maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2205338 | FL Summary #2: Maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2205339 | Summary#2 of Email discussion for maintenance on scheduling and HARQ for NR NTN | Moderator (ZTE) |
| R1-2205384 | Summary#3 of Email discussion for maintenance on scheduling and HARQ for NR NTN | Moderator (ZTE) |
| R1-2205489 | FL Summary #3: Maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2205562 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
| R1-2205669 | Corrections to timing advance for NTN | Ericsson |
| R1-2205673 | Corrections on non-terrestrial network operation in NR | Samsung |
| 8.5 | Maintenance on NR Positioning Enhancements | |
| R1-2205097 | Moderator Summary for preparation phase on maintenance of Rel-17 WI on NR positioning enhancements | Moderator (CATT) |
| R1-2205404 | FL Summary of updates to RRC parameters for Rel-17 positioning enhancements | Moderator (CATT) |
| R1-2205405 | [Draft] LS on updates of RRC parameters for Rel-17 positioning enhancements | CATT |
| R1-2205406 | LS on updates of RRC parameters for Rel-17 positioning enhancements | RAN1, CATT |
| R1-2205525 | Moderator Summary for [109-e-R17-ePos-01] on LS in R1-2203040 | Moderator (Ericsson) |
| R1-2205539 | Updated RRC parameters for Rel-17 positioning enhancements | Moderator (CATT) |
| R1-2205563 | Session notes for 8.5 (Maintenance on NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2205600 | [DRAFT] LS reply on questions concerning the implementation of RAN1 agreements in NRPPa | Moderator (Ericsson) |
| R1-2205601 | [DRAFT] LS on DL PRS RSRPP | Moderator (Ericsson) |
| R1-2205602 | LS reply on questions concerning the implementation of RAN1 agreements in NRPPa | RAN1, Ericsson |
| R1-2205603 | LS on DL PRS RSRPP | RAN1, Ericsson |
| R1-2205617 | Summary #1 for discussion on reply LS related to expected AOA/AOD | Moderator (Nokia) |
| R1-2205618 | [DRAFT] Reply LS on expected AoA and AoD parameters | Nokia |
| R1-2205619 | Reply LS on expected AoA and AoD parameters | RAN1, Nokia |
| R1-2205679 | Correction on NR Positioning Enhancements | Nokia |
| 8.5.1 | Accuracy improvements | |
| R1-2203099 | Maintenance of Rel-17 positioning accuracy improvements | Huawei, HiSilicon |
| R1-2203175 | Maintenance of NR Positioning Accuracy | Nokia, Nokia Shanghai Bell |
| R1-2203436 | Maintenance on enhancements of accuracy improvements for NR positioning | CATT |
| R1-2203515 | Maintenance on accuracy improvements for NR positioning enhancements | vivo |
| R1-2203619 | Remaining issues on accuracy improvement for Rel-17 positioning | ZTE |
| R1-2203864 | Maintenance on accuracy improvement related enhancement | Samsung |
| R1-2203960 | Maintenance of Rel-17 Positioning Accuracy Enhancement | OPPO |
| R1-2204127 | Remaining issues for accuracy enhancements for NR positioning | InterDigital, Inc. |
| R1-2204275 | Remaining issues on accuracy improvements | CMCC |
| R1-2204346 | Remaining issue on accuracy improvements | NTT DOCOMO, INC. |
| R1-2204942 | Maintenance of accuracy improvements for NR positioning enhancements | Ericsson |
| R1-2204985 | Maintenance on Accuracy Improvements | Qualcomm Incorporated |
| R1-2205095 | Maintenance of NR Positioning Accuracy | Nokia, Nokia Shanghai Bell |
| R1-2205161 | FL Summary for mitigating UE/gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2205162 | FL Summary #2 for mitigating UE/gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2205163 | FL Summary #3 for mitigating UE/gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2205201 | Feature Lead Summary #1 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2205381 | [Draft] Reply LS on the UE/TRP TEG framework | CATT |
| R1-2205382 | Reply LS on the UE/TRP TEG framework | RAN1, CATT |
| R1-2205524 | Moderator Summary for [109-e-R17-ePos-03] maintenance on accuracy improvements for UL-AoA and DL-AoD positioning solutions | Moderator (Ericsson) |
| 8.5.2 | Other | |
| R1-2203176 | Maintenance of Other NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2203437 | Maintenance on latency reduction for NR positioning | CATT |
| R1-2203516 | Discussion on other maintenance issues on NR positioning enhancements | vivo |
| R1-2203620 | Remaining issues other than accuracy improvement for Rel-17 Positioning | ZTE |
| R1-2203786 | Remaining issues on PRS collision detection | xiaomi |
| R1-2203865 | Maintenance on latency and efficiency improvement related enhancement | Samsung |
| R1-2203961 | Maintenance of Rel-17 Positioning enhancement other than accuracy enhancement | OPPO |
| R1-2204128 | Remaining issues for NR positioning | InterDigital, Inc. |
| R1-2204276 | Remaining issues on latency improvements | CMCC |
| R1-2204522 | Discussion on maintenance for NR positioning other enhancements | LG Electronics |
| R1-2204903 | Maintenance of Rel-17 positioning latency and efficiency improvements | Huawei, HiSilicon |
| R1-2204943 | Remaining issues for NR positioning enhancements | Ericsson |
| R1-2204986 | Maintenance on Other Issues in NR Positioning Enhancements | Qualcomm Incorporated |
| R1-2205255 | Summary #1 of [109-e-R17-ePos-05] on latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2205256 | Summary #2 of [109-e-R17-ePos-05] on latency improvements and RRC_INACTIVE | Moderator (Huawei) |
| R1-2205449 | Draft reply LS on lower Rx beam sweeping factor for latency improvement | Moderator (Huawei) |
| R1-2205450 | Reply LS on lower Rx beam sweeping factor for latency improvement | RAN1, Huawei |
| R1-2205451 | Draft reply LS on applicable number of PFL for the gapless PRS measurement | Moderator (Huawei) |
| R1-2205452 | Reply LS on applicable number of PFL for the gapless PRS measurement | RAN1, Huawei |
| 8.6 | Maintenance on Support of Reduced Capability NR Devices | |
| R1-2205107 | FL summary for preparatory phase for Rel-17 RedCap maintenance | Moderator (Ericsson) |
| R1-2205427 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2205564 | Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2205674 | Corrections on the introduction of UEs with reduced capabilities in NR | Samsung |
| 8.6.1 | UE complexity reduction | |
| R1-2203053 | Remaining aspects of Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2203109 | Remaining issues on UE complexity reduction | Huawei, HiSilicon |
| R1-2203114 | Maintenance issues for UE complexity reduction for RedCap | Ericsson |
| R1-2203307 | Remaining issues on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2203438 | Remaining issues on RedCap UE complexity reduction in Rel-17 | CATT |
| R1-2203517 | Remaining issues on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2203593 | Discussion on UE complexity reduction for Rel-17 Redcap UE | ZTE, Sanechips |
| R1-2203762 | SIB reception for RedCap UE | Panasonic |
| R1-2203787 | Discussion on the remaining issues of complexity reduction | xiaomi |
| R1-2203866 | Remaining issues on UE complexity reduction | Samsung |
| R1-2204036 | Remaining Issues in UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
| R1-2204208 | Reduced maximum UE bandwidth for Redcap | Apple |
| R1-2204277 | Remaining issues on UE complexity reduction | CMCC |
| R1-2204347 | Maintenance on complexity reduction for RedCap | NTT DOCOMO, INC. |
| R1-2204435 | Remaining details on BWP operation for RedCap | NEC |
| R1-2204453 | Remaining issues on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2204619 | Remaining aspects of UE complexity reduction for RedCap | LG Electronics |
| R1-2204663 | Remaining issues on UE complexity reduction for RedCap NR devices | Sharp |
| R1-2204711 | On RedCap UE complexity reduction | MediaTek Inc. |
| R1-2204744 | On remaining aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2204771 | Remaining details on UE complexity reduction for Rel-17 RedCap | Intel Corporation |
| R1-2204987 | Remaining Issues on UE Complexity Reduction | Qualcomm Incorporated |
| R1-2205428 | FL summary for maintenance on UE bandwidth reduction for RedCap | Moderator (Ericsson) |
| R1-2205429 | FL summary for incoming LS (R1-2203046) on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Moderator (Ericsson) |
| R1-2205430 | Draft reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2205534 | Draft reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | Ericsson |
| R1-2205535 | Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times | RAN1, Ericsson |
| 8.6.2 | Other | |
| R1-2203115 | Draft summary of WI on support of reduced capability (RedCap) NR devices | Ericsson |
| R1-2203308 | Remaining issues on other aspects | Spreadtrum Communications |
| R1-2203518 | Remaining issues on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2203594 | Remaining aspects for Rel-17 RedCap UE | ZTE, Sanechips |
| R1-2203788 | Discussion on the other aspects for R17 RedCap | xiaomi |
| R1-2203992 | Other remaining issues for Reduced Capability NR Devices | OPPO |
| R1-2204037 | Other Remaining Issues in RedCap Support | Nokia, Nokia Shanghai Bell |
| R1-2204209 | On other UE complexity reduction aspects of RedCap | Apple |
| R1-2204454 | Remaining issues on other aspects | Spreadtrum Communications |
| R1-2204772 | Remaining details on support of HD-FDD for Rel-17 RedCap | Intel Corporation |
| R1-2204906 | Remaining issues on RAN2 related issues | Huawei, HiSilicon |
| R1-2205364 | FL summary #1 for maintenance on HD-FDD for RedCap | Moderator (Qualcomm Inc.) |
| R1-2205442 | FL summary #2 for maintenance on HD-FDD for RedCap | Moderator (Qualcomm Inc.) |
| 8.7 | Maintenance on UE Power Saving Enhancements | |
| R1-2205565 | Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2205638 | Collection of RAN1 agreements for UE power saving enhancements for NR (post RAN1 #109-e) | Rapporteur (MediaTek) |
| R1-2205651 | Corrections on UE power savings enhancements in NR | Samsung |
| R1-2205662 | Corrections on UE power saving enhancements in 38.212 | Huawei |
| R1-2205667 | Corrections on NR UE Power Saving Enhancements | Ericsson |
| 8.7.1 | Enhancements for idle/inactive-mode UE power saving | |
| R1-2203085 | Remaining issues on UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2203310 | Remaining issues on enhancements for idle/inactive-mode UE power saving | Spreadtrum Communications |
| R1-2203478 | Remaining issues of Paging enhancement and TRS/CSI-RS | CATT |
| R1-2203519 | Remaining issues on idle/inactive-mode UE power saving | vivo |
| R1-2203595 | Remaining issues of idle/inactive-mode UE power saving | ZTE, Sanechips |
| R1-2203789 | Remaining issues on power saving enhancement for idle/inactive UEs | xiaomi |
| R1-2203867 | Maintenance on enhancements for idle/inactive-mode UE power saving | Samsung |
| R1-2204071 | Remaining issues on Enhancements for idle/inactive-mode UE power saving | Panasonic |
| R1-2204175 | Remaining issues on idle/inactive-mode UE power saving | Sharp |
| R1-2204187 | Remaining issues on idle/inactive-mode UE power saving | Sharp |
| R1-2204210 | Remaining issues on idle/inactive-mode UE power saving | Apple |
| R1-2204456 | Remaining issues on enhancements for idle/inactive-mode UE power saving | Spreadtrum Communications |
| R1-2204604 | Open issues on Idle/Inactive mode power saving | Nokia, Nokia Shanghai Bell |
| R1-2204620 | Remaining issue on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2204704 | Maintenance on idle/inactive-mode UE power saving | MediaTek Inc. |
| R1-2204745 | On remaining issues of TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2204773 | Discussion on remaining aspects of UE Power saving in idle/inactive mode | Intel Corporation |
| R1-2204959 | Maintenance for Rel-17 UE PS : Idle/Inactive mode | Ericsson |
| R1-2204988 | Maintenance issues on idle and inactive mode UE power saving | Qualcomm Incorporated |
| R1-2205392 | Preparation phase summary of maintenance on idle/inactive UE power saving enhancements | Moderator (MediaTek) |
| R1-2205394 | Summary#1 of maintenance on idle/inactive UE power saving enhancements | Moderator (MediaTek) |
| R1-2205477 | Summary#2 of maintenance on idle/inactive UE power saving enhancements | Moderator (MediaTek) |
| R1-2205548 | Summary#3 of maintenance on idle/inactive UE power saving enhancements | Moderator (MediaTek) |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2203086 | Remaining issues on the extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2203311 | Remaining issues on enhancements for power saving adaptation during active time | Spreadtrum Communications |
| R1-2203479 | Remaining issues of PDCCH monitoring adaptation | CATT |
| R1-2203520 | Remaining issues on DCI-based power saving adaptation in connected mode | vivo |
| R1-2203596 | Remaining issues of PDCCH monitoring adaptation | ZTE, Sanechips |
| R1-2203790 | Remaining issues on PDCCH monitoring adaptation for power saving | xiaomi |
| R1-2203868 | Maintenance on DCI-based power saving techniques | Samsung |
| R1-2203993 | Remaining issues for DCI-based power saving adaptation | OPPO |
| R1-2204072 | Remaining issues for extensions to Rel-16 DCI-based power saving adaptation during DRX Active Time | Panasonic |
| R1-2204211 | Remaining details on enhanced DCI-based power saving adaptation | Apple |
| R1-2204348 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2204457 | Remaining issues on enhancements for power saving adaptation during active time | Spreadtrum Communications |
| R1-2204605 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2204621 | Remaining issues on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2204705 | Maintenance on DCI-based PDCCH Monitoring Adaptation | MediaTek Inc. |
| R1-2204746 | On remaining issues of PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2204774 | Discussion on remaining issues of DCI-based PDCCH monitoring adaptation in active time | Intel Corporation |
| R1-2204828 | Remaining issues on DCI-based power saving adaptation | InterDigital, Inc. |
| R1-2204960 | Maintenance for Rel-17 UE PS : PDCCH monitoring adaptation | Ericsson |
| R1-2204989 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2205006 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2205277 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2205278 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2205393 | Preparation phase summary of maintenance on PDCCH monitoring adaptation | Moderator (MediaTek) |
| 8.7.3 | Other | |
| R1-2203597 | Discussion on power saving for RRC connected UEs | ZTE, Sanechips |
| R1-2204897 | Discussion on UE assumption of TRS availability | Huawei, HiSilicon |
| R1-2204961 | Related aspects of Rel-17 UE PS maintenance | Ericsson |
| 8.8 | Maintenance on NR coverage enhancement | |
| R1-2203651 | Summary of preparation phase for Rel-17 NR coverage enhancements | Moderator (China Telecom) |
| R1-2205566 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2205655 | Corrections on NR coverage enhancements | Nokia |
| 8.8.1 | PUSCH enhancements | |
| R1-2203095 | Discussion on PUSCH enhancements | Huawei, HiSilicon |
| R1-2203191 | Discussion on remaining issues for PUSCH enhancements | ZTE |
| R1-2203439 | Remaining issues on PUSCH enhancements in Rel-17 | CATT |
| R1-2203521 | Remaining issues on PUSCH enhancements | vivo |
| R1-2203610 | Remaining issues on PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2203791 | Maintenance on PUSCH enhancements | xiaomi |
| R1-2203837 | Remaining issues on TB processing over multi-slot PUSCH | Langbo |
| R1-2203869 | PUSCH enhancements | Samsung |
| R1-2203994 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2204089 | Remaining issues on PUSCH enhancements | InterDigital, Inc. |
| R1-2204212 | Remaining issues on PUSCH repetition type A enhancement | Apple |
| R1-2204278 | Discussion on the remaining issues of CE PUSCH enhancement | CMCC |
| R1-2204349 | Remaining issues on PUSCH enhancements for coverage enhancement | NTT DOCOMO, INC. |
| R1-2204527 | Remaining details on PUSCH enhancements | LG Electronics |
| R1-2204548 | Remaining issues on enhancements for PUSCH repetition Type A | WILUS Inc. |
| R1-2204657 | Discussion on remaining issues on PUSCH repetition Type A enhancements | Panasonic |
| R1-2204664 | PUSCH enhancements for Rel-17 CovEnh | Sharp |
| R1-2204726 | Discussion on PUSCH enhancements | MediaTek Inc. |
| R1-2204728 | Discussion on Joint channel estimation over multi-slot | MediaTek Inc. |
| R1-2204775 | Remaining issues on PUSCH enhancements | Intel Corporation |
| R1-2204871 | Maintenance for PUSCH Repetition and TBoMS | Ericsson |
| R1-2204990 | PUSCH Enhancements | Qualcomm Incorporated |
| R1-2205366 | FL summary #2 of TB processing over multi-slot PUSCH | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2205367 | Final FL summary of TB processing over multi-slot PUSCH | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2205417 | FL summary #3 of TB processing over multi-slot PUSCH | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2205421 | Summary on [109-e-R17_CovEnh-01] for maintenance on PUSCH enhancement (Enhancements on PUSCH repetition type A) | Moderator (Sharp) |
| 8.8.2 | Joint channel estimation for PUSCH and PUCCH | |
| R1-2203096 | Discussion on joint channel estimation for PUSCH and PUCCH | Huawei, HiSilicon |
| R1-2203192 | Discussion on remaining issues for joint channel estimation | ZTE |
| R1-2203309 | Discussion on joint channel estimation for PUSCH&PUCCH | Spreadtrum Communications |
| R1-2203402 | Discussion on joint channel estimation for PUSCH and PUCCH | Panasonic |
| R1-2203440 | Remaining issues on joint channel estimation in Rel-17 | CATT |
| R1-2203522 | Remaining issues on joint channel estimation | vivo |
| R1-2203611 | Remaining issues on joint channel estimation for PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2203652 | Remaining issues on joint channel estimation for PUSCH and PUCCH | China Telecom |
| R1-2203870 | Joint channel estimation for PUSCH and PUCCH | Samsung |
| R1-2204090 | Joint channel estimation for PUSCH and PUCCH | InterDigital, Inc. |
| R1-2204213 | Remaining issues on cross-slot channel estimation for PUSCH | Apple |
| R1-2204279 | Discussion on the remaining issues of joint channel estimation for PUSCH and PUCCH | CMCC |
| R1-2204350 | Remaining issues on joint channel estimation for PUSCH and PUCCH for coverage enhancement | NTT DOCOMO, INC. |
| R1-2204455 | Discussion on joint channel estimation for PUSCH&PUCCH | Spreadtrum Communications |
| R1-2204513 | Joint channel estimation for PUSCH and PUCCH | Sharp |
| R1-2204549 | Remaining issues on Joint channel estimation for PUCCH and PUSCH | WILUS Inc. |
| R1-2204776 | Remaining issues on joint channel estimation for PUSCH and PUCCH | Intel Corporation |
| R1-2204872 | Maintenance of Joint Channel Estimation for PUSCH and PUCCH | Ericsson |
| R1-2204991 | Joint channel estimation for PUSCH and PUCCH | Qualcomm Incorporated |
| R1-2205185 | FL summary #1 of maintenance on PUCCH enhancements | Moderator (Qualcomm) |
| R1-2205351 | FL Summary of joint channel estimation for PUSCH and PUCCH | Moderator (China Telecom) |
| R1-2205441 | FL summary #2 of maintenance on PUCCH enhancements | Moderator (Qualcomm) |
| R1-2205444 | FL Summary#2 of joint channel estimation for PUSCH and PUCCH | Moderator (China Telecom) |
| R1-2205483 | [109-e-R17_CovEnh-04] Summary of email discussion on joint channel estimation for PUSCH and PUCCH | Moderator (China Telecom) |
| R1-2205626 | Agreed TP for maintenance on joint channel estimation for PUSCH and PUCCH | Moderator (Qualcomm) |
| 8.8.3 | Other | |
| R1-2203193 | Discussion on remaining issues for coverage enhancements for PUCCH | ZTE |
| R1-2203612 | Draft LS on description of RRC parameters for nominal time domain window length for PUSCH and PUCCH DMRS bundling | Nokia, Nokia Shanghai Bell |
| R1-2203792 | Other considerations for TB processing over multi-slot PUSCH | xiaomi |
| R1-2204873 | Rel-17 Multi-Slot Frequency Hopping and Further Enhancements | Ericsson |
| R1-2204902 | Further consideration on PUSCH coverage enhancment | Huawei, HiSilicon |
| R1-2204957 | Remaining issues for PUCCH coverage enhancements | InterDigital, Inc. |
| R1-2205121 | Rel-17 Multi-Slot Frequency Hopping and Further Enhancements | Ericsson |
| 8.9 | Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2203223 | On use of DwPTS for 16QAM NPDSCH in NB-IoT | Huawei, HiSilicon |
| R1-2203631 | Clarifications for DL power allocation for 16-QAM | ZTE, Sanechips |
| R1-2204082 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2204878 | Support of 16-QAM in NB-IoT TDD | Nokia, Nokia Shanghai Bell |
| R1-2205152 | Preparation phase discussion on 109-e-Prep-AI8.9 NB-IoT-eMTC | Moderator (Huawei) |
| R1-2205153 | Feature lead summary on 109-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2205375 | Text proposals on NB-IoT 16QAM | Moderator (Huawei) |
| R1-2205567 | Session notes for 8.9 (Maintenance on Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2205664 | Correction to additional enhancements for NB-IoT and eMTC | Ericsson |
| R1-2205666 | Corrections to Additional Enhancements for NB-IoT and LTE-MTC | Motorola Mobility |
| 8.10 | Maintenance on Enhancements to Integrated Access and Backhaul | |
| R1-2203078 | Remaining issues on R17 IAB enhancements | Huawei, HiSilicon |
| R1-2203353 | Maintenance on Enhancements to Integrated Access and Backhaul | Nokia, Nokia Shanghai Bell |
| R1-2203359 | Maintenance on enhancements to IAB | ZTE, Sanechips |
| R1-2203523 | Maintenance on Enhancements to Integrated Access and Backhaul | vivo |
| R1-2203763 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2203871 | Maintenance on Enhancements to NR IAB | Samsung |
| R1-2204351 | Maintenance on Enhancements to Integrated Access and Backhaul | NTT DOCOMO, INC. |
| R1-2204413 | Resource multiplexing in enhanced IAB systems | Lenovo |
| R1-2204528 | Remaining details on enhancements to IAB | LG Electronics |
| R1-2204640 | Maintenance on enhanced IAB | Ericsson |
| R1-2204648 | Discussions on eIAB maintenance | ETRI |
| R1-2204777 | Remaining details on Frequency-domain Resource Multiplexing for IAB | Intel Corporation |
| R1-2204992 | Remaining issues on eIAB | Qualcomm Incorporated |
| R1-2205216 | Email Discussion Summary #1 for [109-e-R17-eIAB-02] | Moderator (AT&T) |
| R1-2205249 | Summary of [109-e-Prep-AI8.10-eIAB] | Moderator (Qualcomm) |
| R1-2205251 | Email Discussion Summary #2 for [109-e-R17-eIAB-02] | Moderator (AT&T) |
| R1-2205282 | Summary of [109-e-Prep-AI8.10-eIAB] | Moderator (Qualcomm) |
| R1-2205283 | Summary #1 of [109-e-R17-eIAB-01] | Moderator (Qualcomm) |
| R1-2205284 | Summary #1 of [109-e-R17-eIAB-03] | Moderator (Qualcomm) |
| R1-2205292 | [Draft] Reply LS on eIAB MAC CEs | Moderator (Qualcomm) |
| R1-2205293 | Reply LS on eIAB MAC CEs | RAN1, Qualcomm |
| R1-2205302 | Discussion on reply LS on eIAB MAC Ces | Moderator (Qualcomm) |
| R1-2205514 | TP for TS38.213 on soft resource availability for eIAB | Moderator (AT&T) |
| R1-2205515 | TP for TS38.214 on CSI feedback for eIAB | Moderator (AT&T) |
| R1-2205516 | [Draft] LS on upper layers parameters for Rel-17 eIAB | Moderator (AT&T) |
| R1-2205517 | LS on upper layers parameters for Rel-17 eIAB | RAN1, AT&T |
| R1-2205552 | Endorsed TPs to TS 38.213 for Rel-17 eIAB | Moderator (Qualcomm) |
| R1-2205644 | LS on upper layers parameters for Rel-17 eIAB | RAN1, AT&T |
| R1-2205670 | Corrections on eIAB | Samsung |
| R1-2205677 | Corrections on eIAB | Nokia |
| 8.11 | Maintenance on NR Sidelink enhancement | |
| R1-2204900 | Addition on Rel-17 inter-UE coordination function for TS38.300 | Huawei, HiSilicon |
| R1-2205117 | Moderator Summary for preparation phase on maintenance on NR sidelink enhancement | Moderator (LG Electronics) |
| R1-2205290 | Moderator Summary #1 of email discussion [109-e-R17-Sidelink-01] | Moderator (vivo) |
| R1-2205332 | Moderator Summary #2 of email discussion [109-e-R17-Sidelink-01] | Moderator (vivo) |
| R1-2205333 | Draft reply LS on the inter-UE coordination mechanism | Moderator (vivo) |
| R1-2205400 | Reply LS on the inter-UE coordination mechanism | RAN1, vivo |
| R1-2205568 | Session notes for 8.11 (Maintenance on NR Sidelink enhancement) | Ad-Hoc Chair (Huawei) |
| R1-2205650 | Corrections on sidelink enhancements in NR | Samsung |
| R1-2205659 | Corrections on NR Sidelink enhancements | Nokia |
| 8.11.1 | Resource allocation for power saving | |
| R1-2203059 | Remaining aspects of Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2203092 | Remaining issues on sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2203125 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2203312 | Remaining issues on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2203360 | Maintenance on resource allocation for power saving | ZTE, Sanechips |
| R1-2203424 | Maintenance on resource allocation for power saving | CATT, GOHIGH |
| R1-2203524 | Remaining issues on resource allocation for power saving | vivo |
| R1-2203701 | Remaining issues on sidelink resource allocation for power saving | Lenovo |
| R1-2203710 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2203774 | Discussion on remaining issues on resource allocation for power saving | xiaomi |
| R1-2203872 | Maintenance on Resource Allocation for Power Saving | Samsung |
| R1-2203971 | Remaining essential issues on power saving RA | OPPO |
| R1-2204046 | Remaining issues on resource allocation for power saving | InterDigital, Inc. |
| R1-2204173 | Remaining issues on resource allocation for power saving | Sharp |
| R1-2204214 | On sidelink resource allocation for power saving | Apple |
| R1-2204280 | Remaining issues on resource allocation for power saving | CMCC |
| R1-2204352 | Maintenance of sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2204458 | Remaining issues on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2204719 | On resource allocation for sidelink power saving | MediaTek Inc. |
| R1-2204736 | Remaining open issues on resource allocation procedures for power saving | Ericsson |
| R1-2205061 | FL summary #1 for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2205062 | FL summary #2 for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2205063 | FL summary #3 for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2205064 | FL summary for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving (EOM) | Moderator (OPPO) |
| R1-2205408 | FL summary #4 for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving | Moderator (OPPO) |
| R1-2205409 | FL summary #5 for AI 8.11.1 – Maintenance on NR sidelink resource allocation for power saving | Moderator (OPPO) |
| 8.11.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2203060 | Remaining aspects for inter-UE coordination | FUTUREWEI |
| R1-2203093 | Remaining issues on Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2203126 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2203313 | Remaining issues on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2203361 | Maintenance on inter-UE coordination | ZTE, Sanechips |
| R1-2203425 | Maintenance on inter-UE coordination for mode 2 enhancements | CATT, GOHIGH |
| R1-2203525 | Remaining issues on inter-UE coordination | vivo |
| R1-2203641 | Remaining issues on Rel.17 inter-UE coordination | Mitsubishi Electric RCE |
| R1-2203676 | Maintenance on inter-UE coordination for mode 2 enhancements | NEC |
| R1-2203702 | Remaining issues on inter-UE coordination for Mode 2 enhancements | Lenovo |
| R1-2203711 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2203716 | Feature lead summary #1 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2203717 | Feature lead summary #2 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2203748 | Inter-UE coordination for Mode 2 enhancements | Panasonic |
| R1-2203775 | Remaining details on inter-UE coordination | xiaomi |
| R1-2203873 | Maintenance on Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2203972 | Remaining essential issues on inter-UE coordination | OPPO |
| R1-2204047 | On remaining open issues for Mode 2 Inter-UE Coordination | InterDigital, Inc. |
| R1-2204174 | Remaining issues on Inter-UE coordination for Mode 2 enhancements | Sharp |
| R1-2204215 | On inter-UE coordination | Apple |
| R1-2204281 | Remaining issues on inter-UE coordination for Mode 2 enhancements | CMCC |
| R1-2204353 | Maintenance of sidelink resource allocation for reliability and latency | NTT DOCOMO, INC. |
| R1-2204459 | Remaining issues on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2204649 | Remaining issues on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2204727 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2204737 | Remaining open issues on mode 2 enhancements for inter-UE coordination and related text proposals | Ericsson |
| R1-2204993 | Remaining Issues in Mode 2 Inter-UE Coordination | Qualcomm Incorporated |
| R1-2205096 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2205317 | Feature lead summary #3 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2205318 | Feature lead summary #4 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2205494 | Feature lead summary #5 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2205547 | Feature lead summary #6 for AI 8.11.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.3 | Other | |
| R1-2203362 | Additional consideration on inter-UE coordination | ZTE, Sanechips |
| R1-2203426 | Discussion on the status of Rel-17 Sidelink enhancements | CATT, GOHIGH |
| R1-2204048 | Additional discussions on conflict indication timeline | InterDigital, Inc. |
| R1-2204738 | Remaining critical issues for random resource selection and the relationship between power saving and inter-UE coordination mechanism | Ericsson |
| R1-2204898 | Other text proposals for specifications | Huawei, HiSilicon |
| 8.12 | Maintenance on NR Multicast and Broadcast Services | |
| R1-2204892 | Text proposal to TS 38.300 on NR MBS | Huawei, HiSilicon, CBN |
| R1-2205129 | Moderator summary for preparation phase on maintenance of Rel-17 WI on NR MBS | Moderator (CMCC) |
| R1-2205158 | FL summary#1 for discussion on NR MBS TP for TS38.300 | Moderator (Huawei) |
| R1-2205213 | Feature lead summary #1 on discussion of RAN2 LS on HARQ process for MCCH and Broadcast MTCH(s) | Moderator (BBC) |
| R1-2205214 | DRAFT Reply LS on HARQ process for MCCH and Broadcast MTCH(s) | BBC |
| R1-2205215 | Reply LS on HARQ process for MCCH and Broadcast MTCH(s) | RAN1, BBC |
| R1-2205334 | Feature lead summary #2 on discussion of RAN2 LS on HARQ process for MCCH and Broadcast MTCH(s) | Moderator (BBC) |
| R1-2205335 | [Draft] LS on NR MBS TP for TS 38.300 | Huawei |
| R1-2205336 | LS on NR MBS TP for TS 38.300 | RAN1, Huawei |
| R1-2205418 | DRAFT Reply LS on HARQ process for MCCH and Broadcast MTCH(s) | BBC |
| R1-2205426 | Feature lead summary #3 on discussion of RAN2 LS on HARQ process for MCCH and Broadcast MTCH(s) | Moderator (BBC) |
| R1-2205569 | Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| R1-2205649 | Corrections on the introduction of multicast-broadcast services in NR | Samsung |
| R1-2205654 | Corrections to NR support of multicast and broadcast services | Qualcomm |
| R1-2205658 | Corrections on NR Multicast and Broadcast Services | Nokia |
| R1-2205661 | Corrections on NR Multicast and Broadcast Services in 38.212 | Huawei |
| 8.12.1 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2203070 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2203194 | Maintenance of reliability improvement for MBS | ZTE |
| R1-2203227 | Open issues on reliability for NR MBS | TD Tech Ltd |
| R1-2203287 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2203314 | Discussion on the remaining issues on mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2203427 | Remaining issues on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2203526 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2203613 | Remaining issues on mechanisms to improve reliability for MBS | ETRI |
| R1-2203677 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2203699 | Remaining issues on reliability improvement for RRC-CONNECTED UEs | Lenovo |
| R1-2203838 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED UEs | Langbo |
| R1-2203874 | Maintenance on mechanisms to improve reliability | Samsung |
| R1-2203974 | Discussion on remaining issues of mechanism to improve reliability for RRC_CONNECTED UEs | OPPO |
| R1-2204216 | Remaining issues on MBS reliability improvement for RRC_connected UEs | Apple |
| R1-2204282 | Maintenance on mechanisms to improve reliability for RRC_CONNECTED UEs | CMCC |
| R1-2204354 | Remaining issues on HARQ-ACK feedback procedure for multicast | NTT DOCOMO, INC. |
| R1-2204460 | Discussion on the remaining issues on mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2204502 | Remaining reliability issues of MBS for RRC_CONNECTED UEs | Google Inc. |
| R1-2204622 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2204717 | Remaining issues on improve multicast reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2204945 | Remaining issues for improvement of reliability of NR MBS | Ericsson |
| R1-2204994 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2205155 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2205156 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2205157 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2205550 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.2 | Other | |
| R1-2203195 | Maintenance of other issues for broadcast and multicast | ZTE |
| R1-2203228 | Discussion on typical configuration for broadcast mode | TD Tech Ltd |
| R1-2203288 | Remaining Issues for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2203315 | Discussion on the remaining issues for MBS | Spreadtrum Communications |
| R1-2203527 | Maintenance on NR Multicast and Broadcast Services | vivo |
| R1-2203700 | Remaining issues on group scheduling mechanism for RRC_CONNECTED UEs | Lenovo |
| R1-2203776 | Other remaining issues for multicast and broadcast | xiaomi |
| R1-2203875 | Maintenance on group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2204189 | Discussion on MBS SPS activation validation | ASUSTeK |
| R1-2204283 | Maintenance on group scheduling mechanisms for NR multicast and broadcast services | CMCC |
| R1-2204355 | Remaining issues on group scheduling mechanisms for MBS | NTT DOCOMO, INC. |
| R1-2204461 | Discussion on the remaining issues for MBS | Spreadtrum Communications |
| R1-2204623 | Other remaining issues for MBS | LG Electronics |
| R1-2204891 | Remaining issues for multicast and broadcast scheduling | Huawei, HiSilicon, CBN |
| R1-2204946 | Remaining issues for group scheduling of NR MBS | Ericsson |
| R1-2204995 | Other remaining issues for Rel-17 MBS | Qualcomm Incorporated |
| R1-2205169 | Summary#1 on mechanisms to support broadcast/multicast for RRC_CONNECTED/RRC_IDLE/RRC_INACTIVE Ues | Moderator (CMCC) |
| R1-2205170 | Summary#2 on mechanisms to support broadcast/multicast for RRC_CONNECTED/RRC_IDLE/RRC_INACTIVE UEs | Moderator (CMCC) |
| R1-2205171 | Summary#3 on mechanisms to support broadcast/multicast for RRC_CONNECTED/RRC_IDLE/RRC_INACTIVE UEs | Moderator (CMCC) |
| R1-2205309 | LS on TCI indication in multicast DCI | RAN1, CMCC |
| R1-2205368 | Draft LS on TCI indication in multicast DCI | Moderator (CMCC) |
| R1-2205369 | LS on TCI indication in multicast DCI | RAN1, CMCC |
| 8.13 | Maintenance on NR Dynamic spectrum sharing (DSS) | |
| R1-2203102 | Discussion on NR Dynamic spectrum sharing | Huawei, HiSilicon |
| R1-2203196 | Maintenance of DSS and MR-DC | ZTE |
| R1-2203528 | Maintenance on Scell scheduling Pcell | vivo |
| R1-2203876 | Remaining details of NR dynamic spectrum sharing | Samsung |
| R1-2204005 | Remaining issues of cross-carrier scheduling from sSCell to Pcell | OPPO |
| R1-2204624 | Remaining issues on Cross-carrier scheduling from Scell to Pcell | LG Electronics |
| R1-2204694 | On Cross-Carrier Scheduling from sSCell to P(S)Cell | MediaTek Inc. |
| R1-2204778 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2204822 | NR-DC uplink power sharing when SCG cells are deactivated | Nokia, Nokia Shanghai Bell |
| R1-2204962 | Maintenance for Rel-17 DSS | Ericsson |
| R1-2204996 | Maintenance on NR Dynamic spectrum sharing | Qualcomm Incorporated |
| R1-2205179 | [109-e-Prep-AI8.13 fMR-DC/CA Enh] Prep phase summary of further MR-DC/CA Enhancement | Moderator (Huawei) |
| R1-2205192 | Summary of [109-e-Prep-AI8.13 DSS] | Moderator (Ericsson) |
| R1-2205570 | Session notes for 8.13 (Maintenance on NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2205583 | Summary of Email discussion [109-e-R17_DSS-01] | Moderator (Ericsson) |
| R1-2205584 | Agreed TPs from Email discussion [109-e-R17_DSS-01] | Moderator (Ericsson) |
| R1-2205614 | Agreed TPs from Email discussion [109-e-R17_DSS-02] | Moderator (Huawei) |
| R1-2205615 | Summary of email discussion [109-e-R17_DSS-02] on Further Multi-RAT Dual-Connectivity enhancements | Moderator (Huawei) |
| R1-2205672 | Corrections on dynamic spectrum sharing enhancements in NR | Samsung |
| R1-2205676 | Corrections on further Multi-RAT Dual-Connectivity enhancements | Nokia |
| R1-2205683 | Corrections on further Multi-RAT Dual-Connectivity enhancements | Samsung |
| 8.14 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2203089 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Huawei, HiSilicon |
| R1-2203232 | Remaining issues on IoT-NTN | ZTE |
| R1-2203316 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Spreadtrum Communications |
| R1-2203386 | Maintenance on NB-IoT/eMTC to support NTN | MediaTek Inc. |
| R1-2203388 | Summary #1 of AI 8.14 Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek Inc.) |
| R1-2203632 | On IoT NTN maintenance issues | Ericsson Limited |
| R1-2203722 | Maintenance of IoT-NTN | Sony |
| R1-2203769 | Remaining issues on IoT NTN | xiaomi |
| R1-2203839 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Nokia, Nokia Shanghai Bell |
| R1-2203991 | Discussion on remaining issues for NB-IOT/eMTC NTN | OPPO |
| R1-2204217 | On remaining issues of IoT NTN | Apple |
| R1-2204462 | Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network | Spreadtrum Communications |
| R1-2204934 | Timing Relationship Enhancements | Mavenir |
| R1-2204997 | Maintenance on IoT-NTN | Qualcomm Incorporated |
| R1-2205110 | Moderator Summary for preparation phase on maintenance of Rel-17 WI on NB-IoT/eMTC support for Non-Terrestrial Network | Moderator (MediaTek) |
| R1-2205199 | FL summary 1 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2205200 | FL summary 2 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2205484 | Maintenance on NB-IoT/eMTC to support NTN: time and frequency synchronization | Moderator (MediaTek) |
| R1-2205485 | List of RAN1 agreements for Rel-17 IoT NTN (Post RAN1#109-e) | Moderator (MediaTek) |
| R1-2205503 | FL summary 3 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2205571 | Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Huawei) |
| R1-2205578 | DRAFT LS on UL Segmented Transmission for UL synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2205579 | [Draft] LS on UL Segmented Transmission for UL synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2205620 | FL summary 4 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN | Moderator (Sony) |
| R1-2205635 | [Draft] LS on UL Segmented Transmission for UL synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2205642 | LS on UL Segmented Transmission for UL synchronization for IoT NTN | RAN1, MediaTek |
| R1-2205663 | Correction to NB-IoT and LTE-MTC over NTN | Ericsson |
| R1-2205665 | Corrections to NB-IoT/eMTC support for Non-Terrestrial Networks | Motorola Mobility |
| 8.16 | Rel-17 UE features | |
| R1-2205172 | Summary of email discussion on incoming LS in R1-2205090 | Moderator (AT&T) |
| R1-2205325 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #109-e Week1 | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205326 | LS on updated Rel-17 RAN1 UE features list for LTE | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2205327 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #109-e Week1 | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205328 | LS on updated Rel-17 RAN1 UE features list for NR | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2205341 | Reply LS on updated Rel-17 RAN1 UE features list for NR | RAN1, vivo |
| R1-2205607 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #109-e Week2 | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205608 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #109-e Week2 including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205609 | LS on updated Rel-17 RAN1 UE features list for NR | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2205610 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #109-e Week2 | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205611 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #109-e Week2 including remaining RAN1 issues | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2205612 | LS on updated Rel-17 RAN1 UE features list for LTE | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2205613 | Session Notes for 8.16 (Rel-17 UE Features) | Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.16.1 | UE features for further enhancements on NR-MIMO | |
| R1-2203107 | Rel-17 UE features for further NR MIMO enhancements | Huawei, HiSilicon |
| R1-2203262 | UE features for feMIMO | ZTE |
| R1-2203529 | Discussion on UE features for further enhancements on NR-MIMO | vivo |
| R1-2203777 | Discussion on FeMIMO UE features | xiaomi |
| R1-2203877 | Views on UE features for Rel-17 NR FeMIMO | Samsung |
| R1-2203951 | UE features for further enhancements on NR-MIMO | OPPO |
| R1-2204032 | Discussion on UE features for FeMIMO | Ericsson |
| R1-2204140 | Discussion on Rel-17 UE feature for NR FeMIMO | LG Electronics |
| R1-2204218 | Views on Rel-17 FeMIMO UE features | Apple |
| R1-2204356 | Discussion on Rel-17 FeMIMO UE features | NTT DOCOMO, INC. |
| R1-2204586 | On UE features for further enhancements on NR-MIMO | Nokia, Nokia Shanghai Bell |
| R1-2204690 | UE Features for further enhancements on NR MIMO | MediaTek Inc. |
| R1-2204779 | UE features for NR feMIMO | Intel Corporation |
| R1-2204849 | Summary of UE features for further enhancements on NR-MIMO | Moderator (AT&T) |
| R1-2204998 | Discussion on FeMIMO UE features | Qualcomm Incorporated |
| R1-2205098 | Proposal on UE Feature for Rel-17 Unified TCI | Samsung, Ericsson, Nokia, NSB, ZTE, Intel, MediaTek, Verizon, AT&T, KDDI, NTT DOCOMO, LG Uplus, KT Corporation, SKT |
| R1-2205383 | Proposal on UE Feature for Rel-17 Unified TCI | Samsung, Ericsson, Nokia, NSB, ZTE, Intel, MediaTek, Verizon, AT&T, KDDI, NTT DOCOMO, LG Uplus, KT Corporation, SKT |
| R1-2205508 | Session Notes for Agenda Item 8.16.1 | Ad-Hoc Chair (AT&T) |
| 8.16.2 | UE features for supporting NR from 52.6 GHz to 71 GHz | |
| R1-2203083 | Rel-17 UE features for extension to 71 GHz | Huawei, HiSilicon, SIA |
| R1-2203295 | Rel-17 UE features for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2203530 | Remaining issues on UE features for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2203878 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2204115 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2204136 | Discussion on UE features for FR2-2 | OPPO |
| R1-2204219 | Views on Rel-17 Beyond 52.6 GHz UE features | Apple |
| R1-2204357 | Views on UE features for supporting NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2204587 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2204625 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2204708 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | MediaTek Inc. |
| R1-2204780 | Discussion on UE capabilities for extending NR up to 71 GHz | Intel Corporation |
| R1-2204850 | Summary of UE features for supporting NR from 52.6 GHz to 71 GHz | Moderator (AT&T) |
| R1-2204999 | UE features for NR from 52p6 Ghz to 71 Ghz | Qualcomm Incorporated |
| R1-2205111 | Views on UE features for supporting NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2205512 | Session Notes for Agenda Item 8.16.2 | Ad-Hoc Chair (AT&T) |
| 8.16.3 | UE features for enhanced IIoT and and URLLC | |
| R1-2203074 | Rel-17 UE features for enhanced IIoT/URLLC | Huawei, HiSilicon |
| R1-2203197 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2203220 | UE features for IIoT and URLLC | New H3C Technologies Co., Ltd. |
| R1-2203317 | UE features for enhanced IIoT and and URLLC | Spreadtrum Communications |
| R1-2203400 | Rel-17 UE Features for IIoT/URLLC | Ericsson |
| R1-2203531 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2204006 | Discussion on UE features for IIoT and URLLC | OPPO |
| R1-2204220 | Views on Rel-17 IIoT/URLLC UE features | Apple |
| R1-2204358 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2204403 | Summary on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2204463 | UE features for enhanced IIoT and and URLLC | Spreadtrum Communications |
| R1-2204588 | On UE features for enhanced IIoT and and URLLC | Nokia, Nokia Shanghai Bell |
| R1-2205000 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| 8.16.4 | UE features for NR NTN | |
| R1-2203090 | Rel-17 UE features for NR NTN | Huawei, HiSilicon |
| R1-2203233 | Discussion on UE feature for NR-NTN | ZTE |
| R1-2203532 | Remaining issues on UE features for NR NTN | vivo |
| R1-2203782 | Discussion on UE features for NR-NTN | xiaomi |
| R1-2203879 | UE features for NR NTN | Samsung |
| R1-2204008 | Discussion on UE features for NTN-NR | OPPO |
| R1-2204221 | Views on Rel-17 NR NTN UE features | Apple |
| R1-2204359 | Discussion on Rel.17 UE features for NR NTN | NTT DOCOMO, INC. |
| R1-2204520 | Discussion on Rel-17 UE feature for NR NTN | LG Electronics |
| R1-2204589 | On UE features for NR NTN | Nokia, Nokia Shanghai Bell |
| R1-2204661 | On UE features for NR NTN | Ericsson |
| R1-2204851 | Summary of UE features for NR NTN | Moderator (AT&T) |
| R1-2205001 | UE features for NR NTN | Qualcomm Incorporated |
| R1-2205511 | Session Notes for Agenda Item 8.16.4 | Ad-Hoc Chair (AT&T) |
| 8.16.5 | UE features for NR positioning enhancements | |
| R1-2203100 | Rel-17 UE features for NR positioning | Huawei, HiSilicon |
| R1-2203429 | Remaining issues on Rel-17 UE features for NR Positioning enhancements | CATT |
| R1-2203533 | Discussion on UE features for NR positioning enhancements | vivo |
| R1-2203621 | Discussion on UE features for Rel-17 positioning | ZTE |
| R1-2203653 | Remaining issues on UE features for Rel-17 NR positioning enhancements | China Telecom |
| R1-2203880 | Discussion on UE features for NR positioning enhancements | Samsung |
| R1-2203962 | UE features for NR positioning enhancements | OPPO |
| R1-2204360 | Discussion on Rel-17 UE features for NR positioning enhancements | NTT DOCOMO, INC. |
| R1-2204590 | On UE features for NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204852 | Summary of UE features for NR positioning enhancements | Moderator (AT&T) |
| R1-2204944 | Views on NR positioning enhancements UE features | Ericsson |
| R1-2205002 | UE features for NR positioning enhancements | Qualcomm Incorporated |
| R1-2205510 | Session Notes for Agenda Item 8.16.5 | Ad-Hoc Chair (AT&T) |
| 8.16.6 | UE features for REDCAP | |
| R1-2203110 | Rel-17 UE features for RedCap | Huawei, HiSilicon |
| R1-2203116 | UE features for RedCap | Ericsson |
| R1-2203534 | Remaining issues on UE feature for NR REDCAP | vivo, Guangdong Genius |
| R1-2203598 | Discussion on RedCap UE features | ZTE, Sanechips |
| R1-2203881 | Discussion on UE features for RedCap | Samsung |
| R1-2203999 | Rel-17 RedCap UE features | OPPO |
| R1-2204284 | Discussion on UE features for RedCap | CMCC |
| R1-2204361 | Discussion on UE features for RedCap | NTT DOCOMO, INC. |
| R1-2204404 | Summary on UE features for REDCAP | Moderator (NTT DOCOMO, INC.) |
| R1-2204436 | Discussion on UE feature for RedCap | NEC |
| R1-2204591 | On UE features for REDCAP | Nokia, Nokia Shanghai Bell |
| R1-2204712 | UE features for RedCap | MediaTek Inc. |
| R1-2204781 | On Rel-17 UE features for RedCap | Intel Corporation |
| R1-2205003 | UE features for RedCap | Qualcomm Incorporated |
| 8.16.7 | UE features for UE power saving enhancements | |
| R1-2203087 | Rel-17 UE features for UE power saving enhancements | Huawei, HiSilicon |
| R1-2203480 | Discussion on UE feature of UE Power saving enhancements for NR | CATT |
| R1-2203535 | Discussion on UE features for UE power saving enhancements | vivo |
| R1-2203599 | Remaining issues of UE feature for UE power saving enhancements | ZTE, Sanechips |
| R1-2203882 | UE features for UE power saving enhancements | Samsung |
| R1-2203997 | Rel-17 UE Power Saving features | OPPO |
| R1-2204222 | Views on UE features for Rel-17 UE power saving | Apple |
| R1-2204362 | Discussion on Rel-17 UE features for UE power saving | NTT DOCOMO, INC. |
| R1-2204405 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2204592 | On UE features for UE power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204695 | On UE features for UE power saving enhancements | MediaTek Inc. |
| R1-2204782 | Discussion on UE features for UE power saving | Intel Corporation |
| R1-2204963 | UE features for UE PS | Ericsson |
| R1-2205004 | UE features for UE power saving enhancements | Qualcomm Incorporated |
| 8.16.8 | UE features for NR coverage enhancement | |
| R1-2203097 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2203198 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2203318 | UE features for NR coverage enhancement | Spreadtrum Communications |
| R1-2203536 | Remaining issues on UE features for NR coverage enhancement | vivo |
| R1-2203654 | Remaining issues on UE features for Rel-17 NR coverage enhancements | China Telecom |
| R1-2203783 | Discussion on UE features for NR coverage enhancement | xiaomi |
| R1-2203883 | UE features for NR coverage enhancement | Samsung |
| R1-2203998 | Rel-17 Coverage Enhancement UE features | OPPO |
| R1-2204223 | Views on Rel-17 Coverage Enhancement UE Features | Apple |
| R1-2204285 | Discussion on Rel.17 UE features for NR coverage enhancement | CMCC |
| R1-2204363 | Discussion on Rel-17 UE features for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2204406 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2204464 | UE features for NR coverage enhancement | Spreadtrum Communications |
| R1-2204593 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204665 | UE feature for Rel-17 coverage enhancement | Sharp |
| R1-2204729 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| R1-2204783 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2204874 | UE Features for NR Coverage Enhancement | Ericsson |
| R1-2205005 | UE Features for Coverage Enhancements | Qualcomm Incorporated |
| 8.16.9 | UE features for NB-IoT and LTE-MTC enhancements | |
| R1-2204083 | On UE features for NB-IoT and LTE-MTC enhancements | Ericsson |
| R1-2204407 | Summary on UE features for NB-IoT and LTE-MTC enhancements | Moderator (NTT DOCOMO, INC.) |
| 8.16.10 | UE features for IAB enhancements | |
| R1-2203363 | Discussion on NR Rel-17 IAB MT features | ZTE, Sanechips |
| R1-2204641 | UE features for enhanced IAB | Ericsson |
| R1-2204853 | Summary of UE features for IAB enhancements | Moderator (AT&T) |
| 8.16.11 | UE features for NR sidelink enhancement | |
| R1-2203094 | Remaining issues on UE feature for sidelink | Huawei, HiSilicon |
| R1-2203364 | On UE features for NR sidelink enhancement | ZTE, Sanechips |
| R1-2203428 | Remaining issues on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2203537 | Remaining issues on UE features for NR sidelink enhancement | vivo |
| R1-2203712 | Discussion on UE features for NR sidelink enhancement | LG Electronics |
| R1-2203778 | Discussion on UE features for NR sidelink enhancement | xiaomi |
| R1-2203973 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2204224 | Views on Rel-17 NR sidelink UE features | Apple |
| R1-2204364 | Discussion on Rel.17 UE features for NR SL enhancement | NTT DOCOMO, INC. |
| R1-2204408 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2204594 | On UE features for NR sidelink enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204739 | UE features for NR sidelink enhancements | Ericsson |
| R1-2205007 | UE Features for Sidelink Enhancements | Qualcomm Incorporated |
| 8.16.12 | UE features for NR MBS | |
| R1-2203071 | Rel-17 UE features for NR MBS | Huawei, HiSilicon |
| R1-2203199 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2203319 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2203538 | UE features for NR MBS | vivo |
| R1-2203779 | Discussion on UE features for NR MBS | xiaomi |
| R1-2203975 | Discussion on UE features for NR MBS | OPPO |
| R1-2204225 | Views on Rel-17 MBS UE Features | Apple |
| R1-2204286 | Discussion on UE features for NR MBS | CMCC |
| R1-2204365 | Discussion on Rel.17 UE features for NR MBS | NTT DOCOMO, INC. |
| R1-2204409 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2204465 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2204595 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2204718 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2204947 | Views on NR MBS UE features | Ericsson |
| R1-2205008 | UE features for MBS | Qualcomm Incorporated |
| R1-2205122 | Discussion on UE features for NR MBS | xiaomi |
| 8.16.13 | UE features for DSS | |
| R1-2203103 | Rel-17 UE features for DSS and MR-DC | Huawei, HiSilicon |
| R1-2203200 | Discussion on Rel-17 UE features for DSS | ZTE |
| R1-2203539 | Maintenance on UE features for DSS | vivo |
| R1-2203780 | Discussion on UE features for NR DSS | xiaomi |
| R1-2203884 | UE features for DSS | Samsung |
| R1-2204007 | Discussion on UE features for DSS | OPPO |
| R1-2204226 | Views on Rel-17 DSS UE features | Apple |
| R1-2204596 | On UE features for DSS and LTE NR DC enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204696 | On UE features for DSS | MediaTek Inc. |
| R1-2204854 | Summary of UE features for DSS | Moderator (AT&T) |
| R1-2204964 | UE features for DSS | Ericsson |
| R1-2205009 | UE features for DSS and LTE_NR_DC_enh2 | Qualcomm Incorporated |
| R1-2205150 | Views on Rel-17 DSS UE features | Apple |
| R1-2205509 | Session Notes for Agenda Item 8.16.13 | Ad-Hoc Chair (AT&T) |
| 8.16.14 | UE features for IoT over NTN | |
| R1-2203091 | Rel-17 UE features for IoT over NTN | Huawei, HiSilicon |
| R1-2203234 | Discussion on UE feature for IoT-NTN | ZTE |
| R1-2203387 | UE features for IoT over NTN | MediaTek Inc. |
| R1-2203781 | Discussion on UE features for IoT-NTN | xiaomi |
| R1-2204009 | Discussion on UE features for NTN-IoT | OPPO |
| R1-2204081 | On UE features for IoT over NTN | Ericsson |
| R1-2204227 | Views on Rel-17 IoT over NTN UE features | Apple |
| R1-2204597 | On UE features for IoT over NTN | Nokia, Nokia Shanghai Bell |
| R1-2204855 | Summary of UE features for IoT over NTN | Moderator (AT&T) |
| R1-2205010 | UE features for IoT over NTN | Qualcomm Incorporated |
| R1-2205513 | Session Notes for Agenda Item 8.16.14 | Ad-Hoc Chair (AT&T) |
| 8.16.15 | UE features for LTE based 5G terrestrial broadcast | |
| R1-2203201 | Discussion on Rel-17 UE features for LTE based 5G terrestrial broadcast | ZTE |
| R1-2204410 | Summary on UE features for LTE based 5G terrestrial broadcast | Moderator (NTT DOCOMO, INC.) |
| 8.16.16 | UE features for DL 1024QAM for NR FR1 | |
| R1-2204713 | UE features DL 1024QAM for NR FR1 | MediaTek Inc. |
| R1-2204856 | Summary of UE features for DL 1024QAM for NR FR1 | Moderator (AT&T) |
| R1-2205011 | UE features for DL 1024 QAM for NR FR1 | Qualcomm Incorporated |
| 8.16.17 | Other | |
| R1-2203171 | Rel-17 UE features for UL Tx switching | Huawei, HiSilicon |
| R1-2203202 | Discussion on other Rel-17 UE features | ZTE |
| R1-2204366 | Discussion on other UE feature related discussions | NTT DOCOMO, INC. |
| R1-2204411 | Summary on other UE feature related discussions | Moderator (NTT DOCOMO, INC.) |
| R1-2204598 | On Remaining Rel-17 UE features | Nokia, Nokia Shanghai Bell |
| R1-2204703 | On UE capability of maximum number of layers for multi-TRP | MediaTek Inc. |
| R1-2205012 | UE features for Rel-17 UL Tx switching | Qualcomm Incorporated |
| 8.17 | Other | |
| R1-2203108 | Discussion on the remaining issues of UL Tx switching | Huawei, HiSilicon |
| R1-2203244 | Discussion on remaining physical layer issues of small data transmission | ZTE Corporation |
| R1-2203540 | Remaining issues for NR small data transmissions in RRC INACTIVE state and Tx switching enhancements | vivo |
| R1-2203637 | Maintenance issues for NR small data transmissions in inactive state | Ericsson |
| R1-2203655 | Summary of preparation phase for Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2203767 | Discussion on physical layer aspects of small data transmission | xiaomi |
| R1-2203885 | Maintenance on small data transmission | Samsung |
| R1-2203952 | Maintenance of Rel-17 UL Tx Switching | OPPO |
| R1-2204228 | Dropping Timeline Considerations for SRS Carrier Switching | Apple |
| R1-2204518 | Remaining issues on RAN1 aspects for small data transmission | Spreadtrum Communications |
| R1-2204701 | On 3CC UL CA transmission power allocation | MediaTek Inc. |
| R1-2204702 | Clarification on PUSCH with UCI Only and DMRS Multiplexing | MediaTek Inc. |
| R1-2204784 | Remaining issues on physical layer aspects of small data transmission | Intel Corporation |
| R1-2205013 | Remaining issues of Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2205109 | Summary of preparation phase email discussion for Rel-17 SDT | Moderator (ZTE) |
| R1-2205345 | Summary on remaining physical layer issues of small data transmission | Moderator (ZTE) |
| R1-2205346 | [Draft] LS on CG period values for small data transmission | ZTE |
| R1-2205347 | LS on CG period values for small data transmission | RAN1, ZTE |
| R1-2205482 | [109-e-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching maintenance | Moderator (China Telecom) |
| R1-2205675 | Corrections on small data transmission in RRC_INACTIVE state for NR | Samsung |
| R1-2205680 | Corrections on UL Tx Switching enhancements | Nokia |
| 9.1 | NR MIMO evolution for downlink and uplink | |
| R1-2203886 | Work plan for Rel-18 Evolved MIMO | Samsung |
| 9.1.1.1 | Unified TCI framework extension for multi-TRP | |
| R1-2203061 | Unified TCI framework extension for multi-TRP | FUTUREWEI |
| R1-2203149 | Discussion on unified TCI framework extension for multi-TRP | Huawei, HiSilicon |
| R1-2203174 | Discussion on Unified TCI framework extension for multi-TRP | CEWiT |
| R1-2203263 | Enhancements on unified TCI framework extension for multi-TRP | ZTE |
| R1-2203320 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
| R1-2203378 | On Extension of Unified TCI Framework | InterDigital, Inc. |
| R1-2203441 | On unified TCI framework extension for multi-TRP operation | CATT |
| R1-2203541 | Views on unified TCI framework extension for multi-TRP | vivo |
| R1-2203681 | Discussion on unified TCI framework extension for multi-TRP | NEC |
| R1-2203723 | Consideration on Unified TCI framework for multi-TRP | Sony |
| R1-2203793 | Unified TCI framework extension for multi-TRP | xiaomi |
| R1-2203887 | Views on unified TCI extension focusing on m-TRP | Samsung |
| R1-2203953 | Unified TCI framework extension for multi-TRP | OPPO |
| R1-2204033 | Unified TCI framework extension for multiple TCI states | Ericsson |
| R1-2204141 | Unified TCI framework extension for multi-TRP/panel | LG Electronics |
| R1-2204162 | Discussion of unified TCI framework for multi-TRP | Lenovo |
| R1-2204229 | Views on unified TCI framework extension for multi-TRP | Apple |
| R1-2204287 | Discussion on unified TCI framework extension for multi-TRP | CMCC |
| R1-2204367 | Discussion on unified TCI framework extension for multi-TRP | NTT DOCOMO, INC. |
| R1-2204440 | Discussion on unified TCI framework extension for multi-TRP | ITRI |
| R1-2204466 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
| R1-2204506 | Unified TCI framework extension for multi-TRP | Sharp |
| R1-2204538 | Unified TCI framework extension for multi-TRP | Nokia, Nokia Shanghai Bell |
| R1-2204584 | Enhancement on unified TCI framework for multi-TRP | Transsion Holdings |
| R1-2204678 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204684 | Unified TCI framework extension for multi-TRP | MediaTek Inc. |
| R1-2204785 | On Unified TCI framework for mTRP | Intel Corporation |
| R1-2204857 | Unified TCI framework extension for multi-TRP | AT&T |
| R1-2205014 | Extension of unified TCI framework for mTRP | Qualcomm Incorporated |
| R1-2205071 | Discussion on unified TCI framework extension for multi-TRP | FGI |
| R1-2205074 | Considerations on unified TCI for mTRP | Fujitsu Limited |
| R1-2205225 | Moderator summary on extension of unified TCI framework for MTRP (Round 1) | Moderator (MediaTek Inc.) |
| R1-2205314 | Moderator summary on extension of unified TCI framework for MTRP (Round 2) | Moderator (MediaTek Inc.) |
| R1-2205639 | LS on UE power limitation for STxMP in FR2 | RAN1, MediaTek |
| 9.1.1.2 | Two TAs for multi-DCI | |
| R1-2203062 | Enhancements to support two TAs for multi-DCI | FUTUREWEI |
| R1-2203150 | Discussion on TA enhancement for UL M-TRP transmission | Huawei, HiSilicon |
| R1-2203264 | TA enhancement for multi-DCI | ZTE |
| R1-2203321 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
| R1-2203379 | Discussion on Multiple TA for multi-TRP | InterDigital, Inc. |
| R1-2203442 | On Two TAs for UL multi-DCI for multi-TRP operation | CATT |
| R1-2203542 | Views on two TAs for multi-DCI-based multi-TRP operation | vivo |
| R1-2203682 | Discussion on two TAs for multi-DCI | NEC |
| R1-2203724 | Considerations on two TAs for multi-DCI | Sony |
| R1-2203794 | Discussion on two TAs for multi-TRP operation | xiaomi |
| R1-2203888 | Views on two TAs for m-DCI | Samsung |
| R1-2203954 | Two TAs for multi-DCI | OPPO |
| R1-2204034 | Two TAs for multi-DCI | Ericsson |
| R1-2204142 | Two TAs for multi-TRP/panel | LG Electronics |
| R1-2204163 | Discussion of two TAs for multi-DCI UL transmission | Lenovo |
| R1-2204230 | On two Timing Advances for multi-DCI Uplink transmissions | Apple |
| R1-2204288 | Discussion on two TAs for multi-DCI | CMCC |
| R1-2204368 | Discussion on two TAs for multi-DCI | NTT DOCOMO, INC. |
| R1-2204467 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
| R1-2204507 | Two TAs for multi-DCI | Sharp |
| R1-2204539 | Two TAs for UL multi-DCI multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2204786 | On two TAs for multi-DCI | Intel Corporation |
| R1-2205015 | Supporting two TAs for multi-DCI based mTRP | Qualcomm Incorporated |
| R1-2205209 | Moderator Summary #1 on Two TA enhancements for multi-DCI based multi-TRP operation | Moderator (Ericsson) |
| R1-2205592 | [Draft] LS on maximum uplink timing difference for Multi-DCI Multi-TRP with two TAs | Ericsson |
| R1-2205593 | LS on maximum uplink timing difference for Multi-DCI Multi-TRP with two TAs | RAN1, Ericsson |
| 9.1.2 | CSI enhancement | |
| R1-2203151 | CSI enhancement for coherent JT and mobility | Huawei, HiSilicon |
| R1-2203229 | On CSI enhancements for Rel-18 NR MIMO evolution | Ericsson |
| R1-2203265 | CSI enhancement for high/medium UE velocities and CJT | ZTE |
| R1-2203322 | Discussion on CSI enhancement for coherent JT | Spreadtrum Communications |
| R1-2203380 | Aspects of CSI Enhancements | InterDigital, Inc. |
| R1-2203443 | On Rel-18 CSI enhancements | CATT |
| R1-2203543 | Views on CSI enhancement for high-medium UE velocities and coherent JT | vivo |
| R1-2203683 | Discussion on CSI enhancement | NEC |
| R1-2203725 | Considerations on CSI enhancement for high/medium UE velocities and coherent JT (CJT) | Sony |
| R1-2203795 | Discussion on CSI enhancement | xiaomi |
| R1-2203889 | Moderator summary on Rel-18 CSI enhancements | Moderator (Samsung) |
| R1-2203890 | Views on CSI enhancements | Samsung |
| R1-2203955 | CSI enhancement for high/medium UE velocities and coherent JT | OPPO |
| R1-2204099 | CSI enhancement for high/medium UE velocities and CJT | FUTUREWEI |
| R1-2204143 | Potential CSI enhancement for high/medium UE velocities and coherent JT | LG Electronics |
| R1-2204164 | Discussion of CSI enhancement for high speed UE and coherent JT | Lenovo |
| R1-2204231 | Views on Rel-18 MIMO CSI enhancement | Apple |
| R1-2204289 | Discussion on CSI enhancement for high/medium UE velocities and CJT | CMCC |
| R1-2204369 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
| R1-2204468 | Discussion on CSI enhancement for coherent JT | Spreadtrum Communications |
| R1-2204508 | CSI enhancement | Sharp |
| R1-2204540 | CSI enhancement for high/medium UE velocities and CJT | Nokia, Nokia Shanghai Bell |
| R1-2204679 | CSI enhancements for medium UE velocities and coherent JT | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204691 | CSI enhancement for high/medium UE velocities and coherent JT | MediaTek Inc. |
| R1-2204748 | Discussion on CSI Enhancements for high/medium UE velocities and coherent JT | CEWiT |
| R1-2204787 | On CSI enhancements | Intel Corporation |
| R1-2204858 | CSI enhancement | AT&T |
| R1-2205016 | CSI enhancements for high-medium UE velocities and Coherent-JT | Qualcomm Incorporated |
| R1-2205288 | Moderator Summary#2 on Rel-18 CSI enhancements: ROUND 2 | Moderator (Samsung) |
| R1-2205289 | EVM for Rel-18 MIMO CSI enhancements | Moderator (Samsung) |
| R1-2205362 | Moderator Summary#3 on Rel-18 CSI enhancements: ROUND 3 | Moderator (Samsung) |
| R1-2205423 | Moderator Summary#4 on Rel-18 CSI enhancements: ROUND 4 | Moderator (Samsung) |
| R1-2205470 | Moderator Summary#5 on Rel-18 CSI enhancements: ROUND 5 | Moderator (Samsung) |
| 9.1.3.1 | Increased number of orthogonal DMRS ports | |
| R1-2203063 | Increased number of orthogonal DMRS ports | FUTUREWEI |
| R1-2203152 | Enhancements on DMRS in Rel-18 | Huawei, HiSilicon |
| R1-2203266 | DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO | ZTE |
| R1-2203323 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
| R1-2203381 | High Capacity DMRS | InterDigital, Inc. |
| R1-2203403 | Discussions on increased number of orthogonal DMRS ports | New H3C Technologies Co., Ltd. |
| R1-2203444 | On increased number of orthogonal DMRS ports | CATT |
| R1-2203544 | Views on DMRS enhancements | vivo |
| R1-2203643 | Increased number of orthogonal DMRS ports | Ericsson |
| R1-2203684 | Discussion on increased number of orthogonal DMRS ports | NEC |
| R1-2203796 | Discussion on DMRS enhancement | xiaomi |
| R1-2203891 | Views on DMRS enhancements | Samsung |
| R1-2203956 | DMRS enhancement for Rel-18 MIMO | OPPO |
| R1-2204144 | Increased number of orthogonal DMRS ports | LG Electronics |
| R1-2204165 | Discussion of increased number of orthogonal DMRS ports | Lenovo |
| R1-2204232 | Views on supporting increased number of orthogonal DMRS ports | Apple |
| R1-2204290 | Discussion on increased number of orthogonal DMRS ports | CMCC |
| R1-2204370 | Discussion on increased number of orthogonal DMRS ports | NTT DOCOMO, INC. |
| R1-2204469 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
| R1-2204509 | Increased number of orthogonal DMRS ports | Sharp |
| R1-2204541 | Rel-18 UL and DL DMRS Enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204677 | Increased number of orthogonal DMRS ports | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204693 | Increased number of orthogonal DMRS ports | MediaTek Inc. |
| R1-2204788 | Discussion on DMRS enhancement | Intel Corporation |
| R1-2205017 | Design for increased number of orthogonal DMRS ports | Qualcomm Incorporated |
| R1-2205112 | Increased number of orthogonal DMRS ports | Ericsson |
| R1-2205159 | Discussion on DMRS enhancement | xiaomi |
| R1-2205208 | FL summary on DMRS | Moderator (NTT DOCOMO) |
| R1-2205260 | FL summary on DMRS #2 | Moderator (NTT DOCOMO) |
| R1-2205424 | FL summary on DMRS #3 | Moderator (NTT DOCOMO) |
| 9.1.3.2 | SRS enhancement targeting TDD CJT and 8 TX operation | |
| R1-2203066 | SRS enhancements for TDD CJT and 8TX operation | FUTUREWEI |
| R1-2203153 | SRS enhancement for TDD CJT and 8 TX operation in Rel-18 | Huawei, HiSilicon |
| R1-2203230 | On SRS enhancements targeting TDD CJT and 8 TX operation | Ericsson |
| R1-2203267 | SRS enhancement targeting TDD CJT and 8 TX operation | ZTE |
| R1-2203324 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
| R1-2203382 | Enhanced SRS Operation | InterDigital, Inc. |
| R1-2203445 | On SRS enhancement | CATT |
| R1-2203545 | Views on SRS enhancement | vivo |
| R1-2203685 | Discussion on SRS enhancement | NEC |
| R1-2203707 | Views on SRS enhancement targeting 8 TX operation | KDDI Corporation |
| R1-2203797 | Discussion on SRS enhancements | xiaomi |
| R1-2203892 | Views on SRS enhancements | Samsung |
| R1-2203957 | SRS enhancement targeting TDD CJT and 8 TX operation | OPPO |
| R1-2204145 | SRS enhancement targeting TDD CJT and 8 TX operation | LG Electronics |
| R1-2204166 | Discussion of SRS enhancement | Lenovo |
| R1-2204233 | Views on Rel-18 MIMO SRS enhancement | Apple |
| R1-2204291 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | CMCC |
| R1-2204371 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2204470 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
| R1-2204510 | SRS enhancement targeting TDD CJT and 8 TX operation | Sharp |
| R1-2204542 | SRS enhancement for TDD CJT and 8Tx operation | Nokia, Nokia Shanghai Bell |
| R1-2204749 | Discussion on SRS Enhancements for 8Tx Operation | CEWiT |
| R1-2204789 | Discussion on SRS enhancement in Rel-18 | Intel Corporation |
| R1-2205018 | SRS enhancement for TDD CJT and 8 Tx operation | Qualcomm Incorporated |
| R1-2205330 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2205390 | FL Summary #2 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2205391 | FL Summary #3 on SRS enhancements | Moderator (FUTUREWEI) |
| R1-2205425 | FL Summary #4 on SRS enhancements | Moderator (FUTUREWEI) |
| 9.1.4.1 | UL precoding indication for multi-panel transmission | |
| R1-2203154 | Discussion on UL precoding indication for multi-panel transmission | Huawei, HiSilicon |
| R1-2203268 | Enhancements on UL precoding indication for multi-panel transmission | ZTE |
| R1-2203325 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
| R1-2203383 | Precoding for Uplink Multi-panel | InterDigital, Inc. |
| R1-2203446 | On UL precoding indication for multi-panel transmission | CATT |
| R1-2203546 | Views on UL precoding indication for multi-panel transmission | vivo |
| R1-2203686 | Discussion on UL precoding indication for multi-panel transmission | NEC |
| R1-2203726 | Considerations on UL precoding indication for multi-panel transmission | Sony |
| R1-2203798 | Enhancements on multi-panel uplink transmission | xiaomi |
| R1-2203893 | Views on UL precoding indication for STxMP | Samsung |
| R1-2203958 | Transmission scheme and UL precoding indicaton for multi-panel transmission | OPPO |
| R1-2204146 | UL precoding indication for multi-panel transmission | LG Electronics |
| R1-2204167 | UL precoding indication for multi-panel transmission | Lenovo |
| R1-2204234 | Views on UL precoding indication for multi-panel simultanous PUSCH transmissions | Apple |
| R1-2204292 | Discussion on UL precoding indication for multi-panel transmission | CMCC |
| R1-2204372 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
| R1-2204471 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
| R1-2204511 | Views on UL multi-panel transmission | Sharp |
| R1-2204543 | UL precoding indication for multi-panel transmission | Nokia, Nokia Shanghai Bell |
| R1-2204685 | UL precoding indication for multi-panel transmission | MediaTek Inc. |
| R1-2204790 | UL precoding indication for multi-panel transmission | Intel Corporation |
| R1-2204875 | UL precoding indication for multi-panel transmission | Ericsson |
| R1-2205019 | Simultaneous multi-panel transmission | Qualcomm Incorporated |
| R1-2205407 | Summary on UL precoding indication for multi-panel transmission | Moderator (OPPO) |
| R1-2205528 | Summary #2 on UL precoding indication for multi-panel transmission | Moderator (OPPO) |
| R1-2205529 | Summary of [109-e-R18-MIMO-06] Email discussion | Moderator (OPPO) |
| R1-2205598 | Moderator Summary of [109-e-R18-MIMO-06] discussion | Moderator (OPPO) |
| 9.1.4.2 | SRI/TPMI enhancement for enabling 8 TX UL transmission | |
| R1-2203155 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
| R1-2203269 | SRI/TPMI enhancement for enabling 8 TX UL transmission | ZTE |
| R1-2203326 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
| R1-2203384 | On SRI/TPMI Enhancement | InterDigital, Inc. |
| R1-2203447 | On SRI/TPMI enhancement for UL 8 TX | CATT |
| R1-2203547 | Views on enabling 8 TX UL transmission | vivo |
| R1-2203687 | Discussion on SRI/TPMI enhancement | NEC |
| R1-2203727 | Considerations on TPMI enhancement for UL transmission | Sony |
| R1-2203799 | Enhancements on 8Tx uplink transmission | xiaomi |
| R1-2203894 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
| R1-2203959 | SRI TPMI enhancement for 8 TX UL transmission | OPPO |
| R1-2204147 | SRI/TPMI enhancement for enabling 8 TX UL transmission | LG Electronics |
| R1-2204168 | SRI/TPMI enhancement for enabling 8TX UL transmission | Lenovo |
| R1-2204235 | Views on SRI/TPMI enhancement for enabling 8 TX UL transmission | Apple |
| R1-2204293 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | CMCC |
| R1-2204373 | Discussion on 8 TX UL transmission | NTT DOCOMO, INC. |
| R1-2204472 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
| R1-2204512 | Views on 8 TX UL transmission | Sharp |
| R1-2204544 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
| R1-2204692 | SRI/TPMI enhancment for enabling 8 TX UL Tranmission | MediaTek Inc. |
| R1-2204791 | Discussion on enhancement for 8Tx UL transmission | Intel Corporation |
| R1-2204876 | SRI/TPMI enhancement for enabling 8 TX UL transmission | Ericsson |
| R1-2205020 | Enhancements for 8 Tx UL transmissions | Qualcomm Incorporated |
| R1-2205220 | FL Summary on SRI/TPMI Enhancements; First Round | Moderator (InterDigital) |
| R1-2205221 | FL Summary on SRI/TPMI Enhancements; Second Round | Moderator (InterDigital) |
| R1-2205497 | FL Summary on SRI/TPMI Enhancements; Third Round | Moderator (InterDigital) |
| R1-2205587 | Recommended Direction on SRI/TPMI Enhancements for RAN1#110 | Moderator (InterDigital) |
| 9.1.5 | Other | |
| R1-2203270 | Evaluation assumptions for CSI, simultaneous multi-panel UL transmission and 8-Tx UL operation | ZTE |
| R1-2203548 | Discussion on CSI prediction at UE | vivo |
| R1-2203895 | Initial SLS results on Type-II CSI enhancements for CJT | Samsung |
| R1-2204236 | Views on MIMO further enhancement | Apple |
| R1-2204877 | Further elaboration on UL evaluations | Ericsson |
| R1-2204913 | Discussion on field test results of CSI enhancement for coherent JT | Huawei, HiSilicon |
| 9.2 | Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface | |
| R1-2205021 | Work plan for Rel-18 SI on AI and ML for NR air interface | Qualcomm Incorporated |
| R1-2205022 | TR skeleton for Rel-18 SI on AI and ML for NR air interface | Qualcomm Incorporated |
| R1-2205476 | TR 38.843 skeleton for Rel-18 SI on AI and ML for NR air interface | Qualcomm Incorporated |
| R1-2205478 | [109-e-R18-AI/ML-01] Email discussion and approval of TR skeleton for Rel-18 SI on AI/ML for NR air interface | Moderator (Qualcomm Incorporated) |
| R1-2205572 | Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) | Ad-hoc Chair (CMCC) |
| R1-2205695 | Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) | Ad-hoc Chair (CMCC) |
| 9.2.1 | General aspects of AI/ML framework | |
| R1-2203067 | Discussion on common AI/ML characteristics and operations | FUTUREWEI |
| R1-2203139 | Discussion on general aspects of AI/ML framework | Huawei, HiSilicon |
| R1-2203247 | Discussion on common AI/ML framework | ZTE |
| R1-2203280 | General aspects of AI PHY framework | Ericsson |
| R1-2203404 | Discussions on AI-ML framework | New H3C Technologies Co., Ltd. |
| R1-2203450 | Discussion on AI/ML framework for air interface | CATT |
| R1-2203549 | General discussions on AI/ML framework | vivo |
| R1-2203656 | Discussion on general aspects of AI/ML for NR air interface | China Telecom |
| R1-2203690 | Discussion on general aspects of AI ML framework | NEC |
| R1-2203728 | Consideration on common AI/ML framework | Sony |
| R1-2203807 | Initial views on the general aspects of AI/ML framework | xiaomi |
| R1-2203896 | General aspects of AI ML framework and evaluation methodogy | Samsung |
| R1-2204014 | On general aspects of AI/ML framework | OPPO |
| R1-2204062 | Evaluating general aspects of AI-ML framework | Charter Communications, Inc |
| R1-2204077 | General aspects of AI/ML framework | Panasonic |
| R1-2204120 | Considerations on AI/ML framework | SHARP Corporation |
| R1-2204148 | General aspects on AI/ML framework | LG Electronics |
| R1-2204179 | Views on general aspects on AI-ML framework | CAICT |
| R1-2204237 | Discussion on general aspect of AI/ML framework | Apple |
| R1-2204294 | Discussion on general aspects of AI/ML framework | CMCC |
| R1-2204374 | Discussion on general aspects of AI/ML framework | NTT DOCOMO, INC. |
| R1-2204416 | General aspects of AI/ML framework | Lenovo |
| R1-2204498 | Discussion on general aspects of AIML framework | Spreadtrum Communications |
| R1-2204570 | ML terminology, descriptions, and collaboration framework | Nokia, Nokia Shanghai Bell |
| R1-2204650 | Discussion on AI/ML framework for NR air interface | ETRI |
| R1-2204792 | Discussion of AI/ML framework | Intel Corporation |
| R1-2204839 | On general aspects of AI and ML framework for NR air interface | NVIDIA |
| R1-2204859 | General aspects of AI/ML framework for NR air interface | AT&T |
| R1-2204936 | General aspects of AI/ML framework | Mavenir |
| R1-2205023 | General aspects of AIML framework | Qualcomm Incorporated |
| R1-2205065 | AI/ML Model Life cycle management | Rakuten Mobile |
| R1-2205075 | Discussions on general aspects of AI/ML framework | Fujitsu Limited |
| R1-2205099 | Overview to support artificial intelligence over air interface | MediaTek Inc. |
| R1-2205285 | Summary#1 of [109-e-R18-AI/ML-02] | Moderator (Qualcomm) |
| R1-2205401 | Summary#2 of [109-e-R18-AI/ML-02] | Moderator (Qualcomm) |
| R1-2205474 | Summary#3 of [109-e-R18-AI/ML-02] | Moderator (Qualcomm) |
| R1-2205522 | Summary#4 of [109-e-R18-AI/ML-02] | Moderator (Qualcomm) |
| 9.2.2.1 | Evaluation on AI/ML for CSI feedback enhancement | |
| R1-2203068 | Discussion on evaluation of AI/ML for CSI feedback enhancement use case | FUTUREWEI |
| R1-2203140 | Evaluation on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2203248 | Evaluation assumptions on AI/ML for CSI feedback | ZTE |
| R1-2203281 | Evaluations on AI-CSI | Ericsson |
| R1-2203451 | Discussion on evaluation on AI/ML for CSI feedback | CATT |
| R1-2203550 | Evaluation on AI/ML for CSI feedback enhancement | vivo |
| R1-2203650 | Evaluation on AI-based CSI feedback | SEU |
| R1-2203808 | Discussion on evaluation on AI/ML for CSI feedback enhancement | xiaomi |
| R1-2203897 | Evaluation on AI ML for CSI feedback enhancement | Samsung |
| R1-2204015 | Evaluation methodology and preliminary results on AI/ML for CSI feedback enhancement | OPPO |
| R1-2204041 | Considerations on AI-enabled CSI overhead reduction | CENC |
| R1-2204050 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2204055 | Evaluation of CSI compression with AI/ML | Beijing Jiaotong University |
| R1-2204063 | Performance evaluation of ML techniques for CSI feedback enhancement | Charter Communications, Inc |
| R1-2204149 | Evaluation on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2204180 | Some discussions on evaluation on AI-ML for CSI feedback | CAICT |
| R1-2204238 | Initial evaluation on AI/ML for CSI feedback | Apple |
| R1-2204295 | Discussion on evaluation on AI/ML for CSI feedback enhancement | CMCC |
| R1-2204375 | Discussion on evaluation on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2204417 | Evaluation on AI/ML for CSI feedback | Lenovo |
| R1-2204499 | Discussion on evaluation on AI/ML for CSI feedback enhancement | Spreadtrum Communications, BUPT |
| R1-2204571 | Evaluation on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204606 | Discussion on the AI/ML methods for CSI feedback enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204793 | Evaluation for CSI feedback enhancements | Intel Corporation |
| R1-2204840 | On evaluation assumptions of AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2204860 | Evaluation of AI/ML for CSI feedback enhancements | AT&T |
| R1-2205024 | Evaluation on AIML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2205076 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu Limited |
| R1-2205100 | Evaluation on AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2205222 | Summary#1 of [109-e-R18-AI/ML-03] | Moderator (Huawei) |
| R1-2205223 | Summary#2 of [109-e-R18-AI/ML-03] | Moderator (Huawei) |
| R1-2205224 | Summary#3 of [109-e-R18-AI/ML-03] | Moderator (Huawei) |
| R1-2205491 | Summary#4 of [109-e-R18-AI/ML-03] | Moderator (Huawei) |
| R1-2205492 | Summary#5 of [109-e-R18-AI/ML-03] | Moderator (Huawei) |
| 9.2.2.2 | Other aspects on AI/ML for CSI feedback enhancement | |
| R1-2203069 | Discussion on sub use cases of AI/ML for CSI feedback enhancement use case | FUTUREWEI |
| R1-2203141 | Discussion on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
| R1-2203249 | Discussion on potential enhancements for AI/ML based CSI feedback | ZTE |
| R1-2203282 | Discussions on AI-CSI | Ericsson |
| R1-2203452 | Discussion on other aspects on AI/ML for CSI feedback | CATT |
| R1-2203551 | Other aspects on AI/ML for CSI feedback enhancement | vivo |
| R1-2203614 | Discussion on AI/ML for CSI feedback enhancement | GDCNI |
| R1-2203729 | Considerations on CSI measurement enhancements via AI/ML | Sony |
| R1-2203809 | Discussion on AI for CSI feedback enhancement | xiaomi |
| R1-2203898 | Representative sub use cases for CSI feedback enhancement | Samsung |
| R1-2203939 | Discussion on AI/ML for CSI feedback enhancement | NEC |
| R1-2204016 | On sub use cases and other aspects of AI/ML for CSI feedback enhancement | OPPO |
| R1-2204051 | Discussion on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
| R1-2204057 | CSI compression with AI/ML | Beijing Jiaotong University |
| R1-2204150 | Other aspects on AI/ML for CSI feedback enhancement | LG Electronics |
| R1-2204181 | Discussions on AI-ML for CSI feedback | CAICT |
| R1-2204239 | Discussion on other aspects on AI/ML for CSI feedback | Apple |
| R1-2204296 | Discussion on other aspects on AI/ML for CSI feedback enhancement | CMCC |
| R1-2204376 | Discussion on other aspects on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
| R1-2204418 | Further aspects of AI/ML for CSI feedback | Lenovo |
| R1-2204500 | Discussion on other aspects on AI/ML for CSI feedback | Spreadtrum Communications |
| R1-2204568 | Discussions on Sub-Use Cases in AI/ML for CSI Feedback Enhancement | TCL Communication |
| R1-2204572 | Other aspects on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204659 | Discussion on AI/ML for CSI feedback enhancement | Panasonic |
| R1-2204794 | Use-cases and specification for CSI feedback | Intel Corporation |
| R1-2204841 | On other aspects of AI and ML for CSI feedback enhancement | NVIDIA |
| R1-2204861 | CSI feedback enhancements for AI/ML based MU-MIMO scheduling and parameter configuration | AT&T |
| R1-2204937 | AI/ML for CSI feedback enhancement | Mavenir |
| R1-2205025 | Other aspects on AIML for CSI feedback enhancement | Qualcomm Incorporated |
| R1-2205077 | Views on sub-use case selection and STD impacts on AI/ML for CSI feedback enhancement | Fujitsu Limited |
| R1-2205101 | On the challenges of collecting field data for training and testing of AI/ML for CSI feedback enhancement | MediaTek Inc. |
| R1-2205467 | Email discussion on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| R1-2205556 | Summary#2 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
| 9.2.3.1 | Evaluation on AI/ML for beam management | |
| R1-2203142 | Evaluation on AI/ML for beam management | Huawei, HiSilicon |
| R1-2203250 | Evaluation assumptions on AI/ML for beam management | ZTE |
| R1-2203255 | Model and data-driven beam predictions in high-speed railway scenarios | PML |
| R1-2203283 | Evaluations on AI-BM | Ericsson |
| R1-2203374 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
| R1-2203453 | Discussion on evaluation on AI/ML for beam management | CATT |
| R1-2203552 | Evaluation on AI/ML for beam management | vivo |
| R1-2203810 | Evaluation on AI/ML for beam management | xiaomi |
| R1-2203899 | Evaluation on AI ML for Beam management | Samsung |
| R1-2204017 | Evaluation methodology and preliminary results on AI/ML for beam management | OPPO |
| R1-2204059 | Evaluation methodology of beam management with AI/ML | Beijing Jiaotong University |
| R1-2204102 | Discussion on evaluation of AI/ML for beam management use case | FUTUREWEI |
| R1-2204151 | Evaluation on AI/ML for beam management | LG Electronics |
| R1-2204182 | Some discussions on evaluation on AI-ML for Beam management | CAICT |
| R1-2204240 | Evaluation on AI based Beam Management | Apple |
| R1-2204297 | Discussion on evaluation on AI/ML for beam management | CMCC |
| R1-2204377 | Discussion on evaluation on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2204419 | Evaluation on AI/ML for beam management | Lenovo |
| R1-2204573 | Evaluation on ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2204795 | Evaluation for beam management | Intel Corporation |
| R1-2204842 | On evaluation assumptions of AI and ML for beam management | NVIDIA |
| R1-2204862 | Evaluation methodology aspects on AI/ML for beam management | AT&T |
| R1-2205026 | Evaluation on AIML for beam management | Qualcomm Incorporated |
| R1-2205078 | Evaluation on AI/ML for beam management | Fujitsu Limited |
| R1-2205102 | AI-assisted Target Cell Prediction for Inter-cell Beam Management | MediaTek Inc. |
| R1-2205269 | Feature lead summary #1 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2205270 | Feature lead summary #2 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2205271 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
| R1-2205641 | Feature lead summary #4 evaluation of AI/ML for beam management | Moderator (Samsung) |
| 9.2.3.2 | Other aspects on AI/ML for beam management | |
| R1-2203143 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
| R1-2203251 | Discussion on potential enhancements for AI/ML based beam management | ZTE |
| R1-2203284 | Discussions on AI-BM | Ericsson |
| R1-2203375 | Discussion for other aspects on AI/ML for beam management | InterDigital, Inc. |
| R1-2203454 | Discussion on other aspects on AI/ML for beam management | CATT |
| R1-2203553 | Other aspects on AI/ML for beam management | vivo |
| R1-2203691 | Discussion on other aspects on AI/ML for beam management | NEC |
| R1-2203730 | Consideration on AI/ML for beam management | Sony |
| R1-2203811 | Other aspects on AI/ML for beam management | xiaomi |
| R1-2203900 | Representative sub use cases for beam management | Samsung |
| R1-2204018 | Other aspects of AI/ML for beam management | OPPO |
| R1-2204060 | Beam management with AI/ML | Beijing Jiaotong University |
| R1-2204078 | Discussion on sub use cases of beam management | Panasonic |
| R1-2204103 | Discussion on sub use cases of AI/ML for beam management use case | FUTUREWEI |
| R1-2204152 | Other aspects on AI/ML for beam management | LG Electronics |
| R1-2204183 | Discussions on AI-ML for Beam management | CAICT |
| R1-2204241 | Enhancement on AI based Beam Management | Apple |
| R1-2204298 | Discussion on other aspects on AI/ML for beam management | CMCC |
| R1-2204378 | Discussion on other aspects on AI/ML for beam management | NTT DOCOMO, INC. |
| R1-2204420 | Further aspects of AI/ML for beam management | Lenovo |
| R1-2204501 | Discussion on other aspects on AI/ML for beam management | Spreadtrum Communications |
| R1-2204569 | Discussions on Sub-Use Cases in AI/ML for Beam Management | TCL Communication |
| R1-2204574 | Other aspects on ML for beam management | Nokia, Nokia Shanghai Bell |
| R1-2204796 | Use-cases and specification for beam management | Intel Corporation |
| R1-2204843 | On other aspects of AI and ML for beam management | NVIDIA |
| R1-2204863 | System performance aspects on AI/ML for beam management | AT&T |
| R1-2204938 | AI/ML for beam management | Mavenir |
| R1-2205027 | Other aspects on AIML for beam management | Qualcomm Incorporated |
| R1-2205079 | Sub-use cases and spec impact on AI/ML for beam management | Fujitsu Limited |
| R1-2205094 | Discussion on Codebook Enhancement with AI/ML | Charter Communications, Inc |
| R1-2205252 | Summary#1 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2205253 | Summary#2 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2205453 | Summary#3 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| R1-2205454 | Summary#4 for other aspects on AI/ML for beam management | Moderator (OPPO) |
| 9.2.4.1 | Evaluation on AI/ML for positioning accuracy enhancement | |
| R1-2203144 | Evaluation on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2203252 | Evaluation assumptions on AI/ML for positioning | ZTE |
| R1-2203285 | Evaluations on AI-Pos | Ericsson |
| R1-2203455 | Discussion on evaluation on AI/ML for positioning | CATT |
| R1-2203554 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
| R1-2203812 | Initial views on the evaluation on AI/ML for positioning accuracy enhancement | xiaomi |
| R1-2203901 | Evaluation on AI ML for Positioning | Samsung |
| R1-2204019 | Evaluation methodology and preliminary results on AI/ML for positioning accuracy enhancement | OPPO |
| R1-2204104 | Discussion on evaluation of AI/ML for positioning accuracy enhancements use case | FUTUREWEI |
| R1-2204153 | Evaluation on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2204159 | Evaluation assumptions and results for AI/ML based positioning | InterDigital, Inc. |
| R1-2204184 | Some discussions on evaluation on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2204242 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
| R1-2204299 | Discussion on evaluation on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2204421 | Discussion on AI/ML Positioning Evaluations | Lenovo |
| R1-2204575 | Evaluation on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204797 | Evaluation for positioning accuracy enhancements | Intel Corporation |
| R1-2204837 | Evaluation on AI/ML for positioning accuracy enhancement | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204844 | On evaluation assumptions of AI and ML for positioning enhancement | NVIDIA |
| R1-2205028 | Evaluation on AIML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2205066 | Initial view on AI/ML application to positioning use cases | Rakuten Mobile |
| R1-2205080 | Discussion on Evaluation related issues for AI/ML for positioning accuracy enhancement | Fujitsu Limited |
| R1-2205217 | Summary #1 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205218 | Summary #2 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205219 | Summary #3 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205480 | Summary #4 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205481 | Summary #5 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205632 | Summary #6 of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| R1-2205633 | Final Summary of [109-e-R18-AI/ML-07] Email discussion on evaluation of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
| 9.2.4.2 | Other aspects on AI/ML for positioning accuracy enhancement | |
| R1-2203145 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
| R1-2203253 | Discussion on potential enhancements for AI/ML based positioning | ZTE |
| R1-2203286 | Discussions on AI-Pos | Ericsson |
| R1-2203456 | Discussion on other aspects on AI/ML for positioning | CATT |
| R1-2203555 | Other aspects on AI/ML for positioning accuracy enhancement | vivo |
| R1-2203692 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | NEC |
| R1-2203731 | Considerations on AI/ML for positioning accuracy enhancement | Sony |
| R1-2203813 | Initial views on the other aspects of AI/ML-based positioning accuracy enhancement | xiaomi |
| R1-2203902 | Representative sub use cases for Positioning | Samsung |
| R1-2204020 | On sub use cases and other aspects of AI/ML for positioning accuracy enhancement | OPPO |
| R1-2204105 | Discussion on sub use cases of AI/ML for positioning accuracy enhancements use case | FUTUREWEI |
| R1-2204154 | Other aspects on AI/ML for positioning accuracy enhancement | LG Electronics |
| R1-2204160 | Potential specification impacts for AI/ML based positioning | InterDigital, Inc. |
| R1-2204185 | Discussions on AI-ML for positioning accuracy enhancement | CAICT |
| R1-2204243 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | Apple |
| R1-2204300 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | CMCC |
| R1-2204422 | AI/ML Positioning use cases and Associated Impacts | Lenovo |
| R1-2204576 | Other aspects on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
| R1-2204798 | Use-cases and specification for positioning | Intel Corporation |
| R1-2204838 | On potential specification impact of AI/ML for positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204845 | On other aspects of AI and ML for positioning enhancement | NVIDIA |
| R1-2205029 | Other aspects on AIML for positioning accuracy enhancement | Qualcomm Incorporated |
| R1-2205081 | Sub-use cases and spec impacts for AI/ML for positioning accuracy enhancement | Fujitsu Limited |
| R1-2205229 | Discussion summary #1 of [109-e-R18-AI/ML-08] | Moderator (vivo) |
| R1-2205498 | Discussion summary #2 of [109-e-R18-AI/ML-08] | Moderator (vivo) |
| 9.2.5 | Other | |
| R1-2203254 | Discussion on other use cases for AI/ML | ZTE |
| R1-2203405 | Discussions on AI-ML challenges and limitations | New H3C Technologies Co., Ltd. |
| R1-2203457 | Views on UE capability of AI/ML for air interface | CATT |
| R1-2203556 | Discussions on AI/ML for DMRS | vivo |
| R1-2203670 | Draft skeleton of TR 38.843 | Ericsson |
| R1-2204577 | On ML capability exchange, interoperability, and testability aspects | Nokia, Nokia Shanghai Bell |
| R1-2204846 | GPU hosted 5G virtual RAN baseband processing and AI applications | NVIDIA |
| R1-2204911 | Discussion on other potential use cases of AI/ML for NR air interface | Huawei, HiSilicon |
| R1-2205067 | Consideration on UE processing capability for AI/ML utilization | Rakuten Mobile |
| 9.3 | Study on evolution of NR duplex operation | |
| R1-2204301 | TR 38.858 skeleton for study on evolution of NR duplex operation | Rapporteur (CMCC) |
| R1-2204302 | Work plan on Rel-18 evolution of NR duplex operation SI | CMCC,Samsung |
| R1-2205187 | TR 38.858 skeleton for study on evolution of NR duplex operation | Rapporteur (CMCC) |
| R1-2205188 | Summary on email discussion of TR skeleton for Rel-18 SI on evolution of NR duplex operation | Moderator (CMCC) |
| R1-2205310 | Summary#2 on email discussion of TR skeleton for Rel-18 SI on evolution of NR duplex operation | Moderator(CMCC) |
| R1-2205399 | TR 38.858 skeleton for study on evolution of NR duplex operation | Rapporteur (CMCC) |
| R1-2205692 | TR 38.858 v0.0.2 for study on evolution of NR duplex operation | Rapporteur (CMCC) |
| 9.3.1 | Evaluation on NR duplex evolution | |
| R1-2203156 | Overview of evaluation on NR duplex evolution | Huawei, HiSilicon |
| R1-2203203 | Discussion of evaluation on NR duplex evolution | ZTE |
| R1-2203214 | Discussion for Evaluation on NR duplex evolution | New H3C Technologies Co., Ltd. |
| R1-2203327 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications,BUPT |
| R1-2203458 | Discussion on deployment scenario and evaluation methodology for duplex operation | CATT |
| R1-2203557 | Evaluation on NR duplex evolution | vivo |
| R1-2203814 | Discussion on evaluation on NR duplex evolution | xiaomi |
| R1-2203903 | Deployment scenario and evaluation methodology for duplex evolution | Samsung |
| R1-2204021 | Discussion on evaluation on NR duplex evolution | OPPO |
| R1-2204053 | Evaluation on NR duplex evolution | SHARP Corporation |
| R1-2204068 | Evaluation assumption and methodology for study on NR-duplex | InterDigital, Inc. |
| R1-2204106 | Evaluation of NR duplex evolution | Ericsson |
| R1-2204122 | Discussion on deployment scenario of NR duplex evolution | KT Corp. |
| R1-2204135 | Discussion on evaluation on NR duplex evolution | Panasonic |
| R1-2204244 | Initial evaluation on NR duplex evolution | Apple |
| R1-2204303 | Discussion on evaluation on NR duplex evolution | CMCC |
| R1-2204379 | Discussion on evaluation on NR duplex evolution | NTT DOCOMO, INC. |
| R1-2204430 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204473 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications,BUPT |
| R1-2204529 | Study on Evaluation for NR duplex evolution | LG Electronics |
| R1-2204721 | Deployment scenarios and evaluation methodology for NR duplex evolution | MediaTek Inc. |
| R1-2204750 | Discussion on evaluation on NR duplex evolution | CEWiT |
| R1-2204799 | On evaluations for NR duplex evolution | Intel Corporation |
| R1-2205030 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | Qualcomm Incorporated |
| R1-2205311 | Summary#1 on email discussion on evaluation of NR duplex evolution | Moderator(CMCC) |
| R1-2205312 | Summary#2 on email discussion on evaluation of NR duplex evolution | Moderator(CMCC) |
| R1-2205313 | Summary#3 on email discussion on evaluation of NR duplex evolution | Moderator(CMCC) |
| R1-2205540 | Summary#4 on email discussion on evaluation of NR duplex evolution | Moderator(CMCC) |
| R1-2205541 | Summary#5 on email discussion on evaluation of NR duplex evolution | Moderator(CMCC) |
| R1-2205542 | Draft LS on interference modelling for duplex evolution | Moderator(CMCC) |
| R1-2205543 | LS on interference modelling for duplex evolution | RAN1, CMCC |
| 9.3.2 | Subband non-overlapping full duplex | |
| R1-2203157 | Discussion on subband non-overlapping full duplex | Huawei, HiSilicon |
| R1-2203204 | Discussion of subband non-overlapping full duplex | ZTE |
| R1-2203215 | Discussion for subband non-overlapping full duplex | New H3C Technologies Co., Ltd. |
| R1-2203328 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
| R1-2203459 | Discussion on subband non-overlapping full duplex | CATT |
| R1-2203558 | Discussion on subband non-overlapping full duplex | vivo |
| R1-2203732 | Adjacent Channel Interference in non-overlapping subband Full Duplex TDD operations | Sony |
| R1-2203815 | Discussion on subband non-overlapping full duplex | xiaomi |
| R1-2203904 | Subband non-overlapping full duplex for duplex evalution | Samsung |
| R1-2203945 | Discussion on subband non-overlapping full duplex | NEC |
| R1-2204022 | Discussion on subband non-overlapping full duplex | OPPO |
| R1-2204054 | Subband non-overlapping full duplex | SHARP Corporation |
| R1-2204069 | Discussion on subband non-overlapping full duplex | InterDigital, Inc. |
| R1-2204107 | Subband non-overlapping full duplex | Ericsson |
| R1-2204156 | Discussion on subband non-overlapping full duplex | Panasonic |
| R1-2204245 | Views on subband non-overlapping full duplex | Apple |
| R1-2204304 | Discussion on subband non-overlapping full duplex | CMCC |
| R1-2204380 | Discussion on subband non-overlapping full duplex | NTT DOCOMO, INC. |
| R1-2204412 | Discussion on sub band non-overlapping full duplex | CENC |
| R1-2204423 | Subband non-overlapping full duplex | Lenovo |
| R1-2204431 | On subband non-overlapping full duplex for NR | Nokia, Nokia Shanghai Bell |
| R1-2204441 | Discussion on sub-band non-overlapping full duplex | ITRI |
| R1-2204474 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
| R1-2204530 | Study on Subband non-overlapping full duplex | LG Electronics |
| R1-2204550 | Discussion on sub-band non overlapping full duplex | WILUS Inc. |
| R1-2204637 | Introduction of subband non-overlapping full duplex | ASUSTeK |
| R1-2204651 | Discussions on subband non-overlapping full duplex enhancements | ETRI |
| R1-2204722 | Discussion on subband non-overlapping full duplex for NR | MediaTek Inc. |
| R1-2204751 | Discussion on subband non-overlapping full duplex | CEWiT |
| R1-2204800 | Discussions on subband non-overlapping full duplex | Intel Corporation |
| R1-2204866 | Considerations for subband non-overlapping full duplex | Charter Communications |
| R1-2205031 | Feasibility and techniques for Subband non-overlapping full duplex | Qualcomm Incorporated |
| R1-2205361 | Summary #1 of [109-e-R18-Duplex-03] Email discussion on subband non-overlapping full duplex | Moderator (CATT) |
| R1-2205520 | Summary #2 of [109-e-R18-Duplex-03] Email discussion on subband non-overlapping full duplex | Moderator (CATT) |
| 9.3.3 | Potential enhancements on dynamic/flexible TDD | |
| R1-2203158 | Potential enhancements on dynamic/flexible TDD | Huawei, HiSilicon |
| R1-2203205 | Discussion of enhancements on dynamic/flexible TDD | ZTE |
| R1-2203216 | Discussion for potential enhancements on dynamic/flexible TDD | New H3C Technologies Co., Ltd. |
| R1-2203221 | Potential enhancement on dynamic/flexible TDD | TCL Communication Ltd. |
| R1-2203329 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
| R1-2203460 | Discussion on potential enhancements on dynamic/flexible TDD | CATT |
| R1-2203559 | Potential enhancements on dynamic/flexible TDD | vivo |
| R1-2203733 | Enhancements to dynamic/flexible TDD for Full Duplex operation | Sony |
| R1-2203816 | Discussion on potential enhancements on dynamic TDD | xiaomi |
| R1-2203905 | Dynamic and flexible TDD for duplex evalution | Samsung |
| R1-2203944 | Views on enhancements of dynamic/flexible TDD | NEC |
| R1-2204023 | Discussion on potential enhancements on dynamic/flexible TDD | OPPO |
| R1-2204056 | Potential enhancements on dynamic/flexible TDD | SHARP Corporation |
| R1-2204070 | Discussion on enhancements of dynamic TDD operations | InterDigital, Inc. |
| R1-2204076 | Potential enhancements on dynamic/flexible TDD for subband full duplex | Panasonic |
| R1-2204108 | Flexible/dynamic TDD | Ericsson |
| R1-2204246 | Views on potential enhancements on dynamic/flexible TDD | Apple |
| R1-2204305 | Discussion on potential enhancements on flexible/dynamic TDD | CMCC |
| R1-2204381 | Discussion on potential enhancements on dynamic/flexible TDD | NTT DOCOMO, INC. |
| R1-2204432 | Dynamic TDD enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204442 | Discussion on potential enhancements on dynamic/flexible TDD | ITRI |
| R1-2204475 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
| R1-2204503 | Potential enhancements on dynamic/flexible TDD | Lenovo |
| R1-2204531 | Study on Potential enhancements on dynamic/flexible TDD | LG Electronics |
| R1-2204551 | Discussion on potential enhancements on dynamic/flexible TDD | WILUS Inc. |
| R1-2204638 | Enhancement on dynamic TDD | ASUSTeK |
| R1-2204723 | Discussion on potential enhancements on dynamic/flexible TDD | MediaTek Inc. |
| R1-2204752 | Discussion on enhancements on dynamic/flexible TDD | CEWiT |
| R1-2204801 | On potential enhancements to dynamic/flexible TDD in NR systems | Intel Corporation |
| R1-2205032 | On potential enhancements on dynamic-flexible TDD | Qualcomm Incorporated |
| R1-2205371 | Summary #1 of [109-e-R18-Duplex-04] Email discussion on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2205372 | Summary #2 of [109-e-R18-Duplex-04] Email discussion on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2205373 | Summary #3 of [109-e-R18-Duplex-04] Email discussion on dynamic/flexible TDD | Moderator (LG Electronics) |
| R1-2205374 | Summary #4 of [109-e-R18-Duplex-04] Email discussion on dynamic/flexible TDD | Moderator (LG Electronics) |
| 9.3.4 | Other | |
| R1-2203206 | Discussion of preliminary simulation results for NR duplex evolution | ZTE |
| R1-2203222 | Backhaul Signaling Reduction for Inter gNB Information exchange | TCL Communication Ltd. |
| R1-2203330 | Further considerations on duplex operation | Spreadtrum Communications |
| R1-2203560 | Other issues on NR duplex evolution | vivo |
| R1-2203633 | Discussion on Rel-18 duplex evolution | CATT |
| R1-2203817 | Other issues on NR duplex evolution | xiaomi |
| R1-2204109 | Inputs needed from RAN4 to facilitate RAN1 study | Ericsson |
| R1-2204433 | RF considerations of dynamic TDD and SBFD | Nokia, Nokia Shanghai Bell |
| R1-2204476 | Further considerations on duplex operation | Spreadtrum Communications |
| R1-2204914 | Discussion on the work plan for the evolution of duplex operation | Huawei, HiSilicon |
| 9.4 | NR sidelink evolution | |
| R1-2203981 | Work plan for NR sidelink evolution | OPPO, LG Electronics |
| R1-2205573 | Session notes for 9.4 (NR sidelink evolution) | Ad-Hoc Chair (Huawei) |
| 9.4.1 | Support of sidelink on unlicensed spectrum | |
| R1-2204093 | Discussion on V2X use cases, scenarios, and requirements for SL-U | TOYOTA Info Technology Center |
| R1-2205113 | Contention-Based Sidelink Burst Transmissions | Johns Hopkins University APL |
| R1-2205118 | General considerations on SL-U | Continental Automotive GmbH |
| 9.4.1.1 | Channel access mechanism | |
| R1-2203122 | On Channel Access Mechanism and Evaluation Methodology for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2203146 | Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2203331 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2203365 | Discussion on channel access mechanism for SL-U | ZTE, Sanechips |
| R1-2203461 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2203561 | Channel access mechanism for sidelink on unlicensed spectrum | vivo |
| R1-2203645 | SL Channel access in unlicensed spectrum | InterDigital, Inc. |
| R1-2203657 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | China Telecom |
| R1-2203693 | Channel Access of Sidelink on Unlicensed Spetrum | NEC |
| R1-2203703 | Channel access mechanism for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2203713 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | LG Electronics |
| R1-2203734 | Discussion on channel access mechanism for SL-unlicensed | Sony |
| R1-2203749 | Sidelink channel access on unlicensed spectrum | Panasonic |
| R1-2203818 | Channel access mechanism for sidelink-unlicensed | xiaomi |
| R1-2203906 | On channel access mechanism for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2203982 | Access mechanisms of NR sidelink in unlicensed channel | OPPO |
| R1-2204084 | SL-U General Access Considerations | CableLabs, Charter Communications |
| R1-2204097 | Discussion of channel access mechanism for sidelink transmission in unlicensed spectrum | FUTUREWEI |
| R1-2204194 | Discussion on sidelink on unlicensed spectrum | ASUSTeK |
| R1-2204247 | On channel access mechanism for sidelink on FR1 unlicensed spectrum | Apple |
| R1-2204306 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CMCC |
| R1-2204382 | Discussions on channel access mechanism in SL-U | NTT DOCOMO, INC. |
| R1-2204427 | Discussions on Channel access mechanism for NR sidelink evolution | Sharp |
| R1-2204477 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2204552 | Discussion on channel access mechanism for SL on unlicensed spectrum | WILUS Inc. |
| R1-2204580 | Discussion of channel access mechanism for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2204607 | NR Sidelink Unlicensed Channel Access Mechanisms | Fraunhofer HHI, Fraunhofer IIS |
| R1-2204730 | Discussion on Channel access mechanism | MediaTek Inc. |
| R1-2204741 | Channel access mechanism for SL-U | Ericsson |
| R1-2204802 | On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2204868 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | ROBERT BOSCH GmbH |
| R1-2205033 | Channel Access Mechanism for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2205082 | Considerations on unlicensed channel access for SL-U | Fujitsu Limited |
| R1-2205180 | FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2205181 | FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2205182 | FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2205183 | FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
| R1-2205184 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) | Moderator (OPPO) |
| 9.4.1.2 | Physical channel design framework | |
| R1-2203123 | On Physical Channel Design Framework for SL-U | Nokia, Nokia Shanghai Bell |
| R1-2203147 | Physical channel design for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| R1-2203332 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2203366 | Discussion on physical layer structures and procedures for SL-U | ZTE, Sanechips |
| R1-2203462 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CATT, GOHIGH |
| R1-2203562 | Physical channel design framework for sidelink on unlicensed spectrum | vivo |
| R1-2203646 | SL U physical layer design framework | InterDigital, Inc. |
| R1-2203694 | Discussion on physical channel design framework | NEC |
| R1-2203704 | Physical layer design framework for sidelink on FR1 unlicensed spectrum | Lenovo |
| R1-2203714 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
| R1-2203735 | Discussion on physical channel design framework for SL-unlicensed | Sony |
| R1-2203750 | Physical channel design for sidelink on unlicensed spectrum | Panasonic |
| R1-2203819 | Physical channel design for sidelink-unlicensed | xiaomi |
| R1-2203907 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Samsung |
| R1-2203983 | Physical channel designs of NR sidelink in unlicensed channel | OPPO |
| R1-2204085 | Discussion on resources on sidelink operation in unlicensed spectrum | CableLabs |
| R1-2204098 | Discussion of physical channel designs for sidelink transmission in unlicensed spectrum | FUTUREWEI |
| R1-2204121 | Discussion on Physical channel design framework for sidelink on unlicensed spectrum | Hyundai Motors |
| R1-2204248 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Apple |
| R1-2204307 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CMCC |
| R1-2204383 | Discussions on channel design framework in SL-U | NTT DOCOMO, INC. |
| R1-2204428 | Discussions on physical channel design framework for NR sidelink evolution on unlicensed spectrum | Sharp |
| R1-2204478 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
| R1-2204553 | Discussion on PHY channel design framework for SL on unlicensed spectrum | WILUS Inc. |
| R1-2204581 | Discussion of physical channel design for sidelink in unlicensed spectrum | Transsion Holdings |
| R1-2204608 | NR Sidelink Unlicensed Physical Channel Design | Fraunhofer HHI, Fraunhofer IIS |
| R1-2204731 | Discussion on Physical channel design framework | MediaTek Inc. |
| R1-2204742 | PHY channel design framework for SL-U | Ericsson |
| R1-2204803 | On the Enhancements to the Physical Channel Design for SL Operating in Unlicensed Spectrum | Intel Corporation |
| R1-2205034 | Physical Channel Design for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
| R1-2205238 | FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2205239 | FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2205240 | FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| R1-2205241 | FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
| 9.4.2 | Co-channel coexistence for LTE sidelink and NR sidelink | |
| R1-2203124 | On Co-channel Coexistence for LTE Sidelink and NR Sidelink | Nokia, Nokia Shanghai Bell |
| R1-2203148 | Co-channel coexistence for LTE sidelink and NR sidelink | Huawei, HiSilicon |
| R1-2203333 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Spreadtrum Communications |
| R1-2203367 | Study on co-channel coexistence for LTE sidelink and NR sidelink | ZTE, Sanechips |
| R1-2203463 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CATT, GOHIGH |
| R1-2203563 | Co-channel coexistence for LTE sidelink and NR sidelink | vivo |
| R1-2203642 | On sidelink co-channel coexistence issues | Mitsubishi Electric RCE |
| R1-2203658 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | China Telecom |
| R1-2203668 | Discussion on Sidelink Co-channel Coexistence | Panasonic |
| R1-2203695 | Co-existence between LTE and NR sidelink | NEC |
| R1-2203705 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Lenovo |
| R1-2203715 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics |
| R1-2203736 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Sony |
| R1-2203820 | Discussion on co-channel coexistence for LTE and NR sidelink | xiaomi |
| R1-2203908 | On co-channel coexistence for LTE sidelink and NR sidelink | Samsung |
| R1-2203984 | Discussion on co-channel coexistence for LTE and NR V2X | OPPO |
| R1-2204049 | Co-channel coexistence for LTE sidelink and NR sidelink | InterDigital, Inc. |
| R1-2204249 | On co-channel coexistence for LTE sidelink and NR sidelink | Apple |
| R1-2204308 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CMCC |
| R1-2204384 | Discussions on co-channel coexistence of LTE-SL and NR-SL | NTT DOCOMO, INC. |
| R1-2204429 | Discussions on co-channel coexistence for LTE sidelink and NR sidelink | Sharp |
| R1-2204479 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Spreadtrum Communications |
| R1-2204585 | Considerations on co-channel coexistence for LTE SL and NR SL | CAICT |
| R1-2204609 | Discussion on Co-Channel Coexistence for LTE and NR Sidelink | Fraunhofer HHI, Fraunhofer IIS |
| R1-2204652 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | ETRI |
| R1-2204720 | On co-channel coexistence between LTE sidelink and NR sidelink | MediaTek Inc. |
| R1-2204740 | Co-channel coexistence between LTE sidelink and NR sidelink | Ericsson |
| R1-2204867 | On co-channel coexistence between LTE and NR sidelink | ROBERT BOSCH GmbH |
| R1-2205035 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
| R1-2205119 | General considerations on Coexistence between LTE- and NR-sidelink | Continental Automotive GmbH |
| R1-2205204 | FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2205205 | FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2205206 | FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2205207 | FL Summary #4 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| R1-2205588 | FL Summary EoM of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (Fraunhofer HHI) |
| 9.4.5 | Other | |
| R1-2203368 | Analysis on channel access efficiency of SL-U | ZTE, Sanechips |
| R1-2203464 | Discussion on the scopes of Rel-18 Sidelink evolution | CATT, GOHIGH |
| R1-2203647 | SL U QoS management | InterDigital, Inc. |
| R1-2203667 | Discussion on sidelink operation on unlicensed spectrum | vivo |
| R1-2203985 | Coexistence evaluation of SL-U and Wi-Fi | OPPO |
| R1-2204250 | On other topics of NR sidelink evolutions | Apple |
| R1-2204743 | Other aspects related to SL-U | Ericsson |
| R1-2204912 | Further consideration on evaluation methodology for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
| 9.5 | Study on expanded and improved NR positioning | |
| R1-2204804 | Draft skeleton of TR38.859 | Rapporteur (Intel Corporation) |
| R1-2204805 | Work Plan for Study Item on Expanded and Improved NR Positioning | Intel Corporation, CATT, Ericsson |
| R1-2205226 | Work Plan for Study Item on Expanded and Improved NR Positioning | Intel Corporation, CATT, Ericsson |
| R1-2205353 | Draft skeleton of TR38.859 | Rapporteur (Intel Corporation) |
| R1-2205358 | FL summary on TR 38.859 skeleton for Rel-18 SI on expanded and improved NR positioning | Moderator (Intel Corporation) |
| R1-2205398 | Draft skeleton of TR38.859 | Rapporteur (Intel Corporation) |
| R1-2205574 | Session notes for 9.5 (Study on expanded and improved NR positioning) | Ad-Hoc Chair (Huawei) |
| 9.5.1.1 | SL positioning scenarios and requirements | |
| R1-2203057 | Considerations on scenarios and target requirements for sidelink positioning | FUTUREWEI |
| R1-2203127 | SL positioning scenarios and requirements | Nokia, Nokia Shanghai Bell |
| R1-2203162 | Discussion on scenarios and requirements for sidelink positioning | Huawei, HiSilicon |
| R1-2203334 | Consideration on SL positioning scenarios and requirements | Spreadtrum Communications |
| R1-2203465 | Discussion on SL positioning scenarios and requirements | CATT, GOHIGH |
| R1-2203564 | Discussion on SL positioning scenarios and requirements | vivo |
| R1-2203622 | Discussion on scenarios and requirements for SL positioning | ZTE |
| R1-2203718 | Discussion on SL positioning scenarios and requirements | LG Electronics |
| R1-2203737 | Considerations on SL positioning scenarios and requirements | Sony |
| R1-2203751 | Scenarios and requirements for sidelink positioning | MediaTek Inc. |
| R1-2203821 | Discussion on sidelink positioning scenarios and requirement | xiaomi |
| R1-2203909 | On SL Positioning Scenarios and Requirements | Samsung |
| R1-2203941 | SL positioning scenarios and requirements | NEC |
| R1-2203978 | Discussion on SL positioning scenarios and requirements | OPPO |
| R1-2204094 | Discussion on V2X use cases, scenarios, and requirements for sidelink positioning | TOYOTA Info Technology Center |
| R1-2204130 | Potential scenarios and requirements for SL positioning | InterDigital, Inc. |
| R1-2204251 | Discussion on SL positioning scenarios and requirements | Apple |
| R1-2204309 | Discussion on SL positioning scenarios and requirements | CMCC |
| R1-2204480 | Consideration on SL positioning scenarios and requirements | Spreadtrum Communications |
| R1-2204557 | Potential SL Positioning Scenarios and Requirements | Lenovo |
| R1-2204666 | Views on SL positioning scenarios and requirements | Sharp |
| R1-2204753 | Discussion on sidelink based positioning requirements & scenarios | CEWiT |
| R1-2204806 | On SL positioning scenarios and requirements | Intel Corporation |
| R1-2204833 | SL positioning scenarios and requirements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204948 | SL positioning scenarios and requirements | Ericsson |
| R1-2205036 | Sidelink Positioning Scenarios and Requirements | Qualcomm Incorporated |
| R1-2205177 | FL summary #1 on SL positioning scenarios and requirements | Moderator (Intel) |
| R1-2205194 | Potential SL Positioning Scenarios and Requirements | Lenovo |
| R1-2205527 | FL summary #2 on SL positioning scenarios and requirements | Moderator (Intel) |
| R1-2205595 | FL summary #3 on SL positioning scenarios and requirements | Moderator (Intel) |
| 9.5.1.2 | Evaluation of SL positioning | |
| R1-2203128 | Evaluation of SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2203163 | Evaluation of SL positioning | Huawei, HiSilicon |
| R1-2203466 | Evaluation methodology and performance evaluation for SL positioning | CATT, GOHIGH |
| R1-2203565 | Evaluation of sideilnk positioning performance | vivo |
| R1-2203623 | Discussion on evaluation for SL positioning | ZTE |
| R1-2203719 | Discussion on evaluation of SL positioning | LG Electronics |
| R1-2203822 | Discussion on sidelink positioning evaluation methodology | xiaomi |
| R1-2203910 | Discussion on Evaluation for SL Positioning | Samsung |
| R1-2203942 | Evaluation of SL positioning | NEC |
| R1-2203979 | Discussion on evaluation methodology of SL positioning | OPPO |
| R1-2204061 | Consideration on sidelink positioning design | CENC |
| R1-2204131 | Evaluation methodology for SL positioning | InterDigital, Inc. |
| R1-2204252 | On Evaluation of SL positioning | Apple |
| R1-2204558 | SL Positioning Evaluation Methodology | Lenovo |
| R1-2204754 | Discussion on evaluation methods and results of sidelink based positioning | CEWiT |
| R1-2204834 | SL positioning evaluation methodology | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204939 | Views on Evaluation Methodology for NR Sidelink Positioning | Intel Corporation |
| R1-2204949 | Evaluation of SL positioning | Ericsson |
| R1-2205037 | Sidelink Positioning Evaluation Assumptions and Results | Qualcomm Incorporated |
| R1-2205186 | Discussion on Evaluation for SL Positioning | Samsung |
| R1-2205227 | Summary #1 of [109-e-R18-Pos-03] Email discussion on evaluation of SL positioning | Moderator (ZTE) |
| R1-2205228 | Summary #2 of [109-e-R18-Pos-03] Email discussion on evaluation of SL positioning | Moderator (ZTE) |
| 9.5.1.3 | Potential solutions for SL positioning | |
| R1-2203058 | Considerations on potential solutions for SL positioning | FUTUREWEI |
| R1-2203129 | Potential solutions for SL positioning | Nokia, Nokia Shanghai Bell |
| R1-2203164 | Discussion on solutions to support SL positioning | Huawei, HiSilicon |
| R1-2203335 | Consideration on potential solutions for SL positioning | Spreadtrum Communications |
| R1-2203467 | Discussion on potential solutions for SL positioning | CATT, GOHIGH |
| R1-2203566 | Discussion on potential solutions for sidelink positioning | vivo |
| R1-2203624 | Discussion on potential solutions for SL positioning | ZTE |
| R1-2203659 | Discussion on potential solutions for sidelink positioning | China Telecom |
| R1-2203720 | Discussion on potential solutions for SL positioning | LG Electronics |
| R1-2203738 | Considerations on potential solutions for SL positioning | Sony |
| R1-2203752 | The potential solutions for sidelink positioning | MediaTek Inc. |
| R1-2203823 | Discussion on sidelink positioning solutions | xiaomi |
| R1-2203911 | Discussion on Potential Solutions for SL Positioning | Samsung |
| R1-2203943 | Discussion on Potential Solutions for SL Positioning | NEC |
| R1-2203980 | Discussion on potential solutions for SL positioning | OPPO |
| R1-2204092 | carrier phase measurement method for sidelink positioning | Locaila |
| R1-2204132 | Potential solutions for SL positioning | InterDigital, Inc. |
| R1-2204253 | Discussions on Potential solutions for SL positioning | Apple |
| R1-2204310 | Discussion on potential solutions for SL positioning | CMCC |
| R1-2204385 | Discussions on potential solutions for SL positioning | NTT DOCOMO, INC. |
| R1-2204481 | Consideration on potential solutions for SL positioning | Spreadtrum Communications |
| R1-2204559 | On Potential SL Positioning Solutions | Lenovo |
| R1-2204667 | Views on potential solutions for SL positioning | Sharp |
| R1-2204755 | Discussion on potential solutions for sidelink based positioning | CEWiT |
| R1-2204835 | Potential solutions for SL positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204869 | Views on potential solutions for SL positioning | ROBERT BOSCH GmbH |
| R1-2204940 | Views on potential solutions for SL positioning | Intel Corporation |
| R1-2204950 | Potential solutions for SL positioning | Ericsson |
| R1-2205038 | Potential Solutions for Sidelink Positioning | Qualcomm Incorporated |
| R1-2205151 | Potential solutions for SL positioning | Ericsson |
| R1-2205202 | Moderator Summary #1 for [109-e-R18-Pos-04] Email discussion on potential solutions for SL positioning | Moderator (Qualcomm) |
| R1-2205457 | Moderator Summary #2 for [109-e-R18-Pos-04] Email discussion on potential solutions for SL positioning | Moderator (Qualcomm) |
| 9.5.2.1 | Solutions for integrity of RAT dependent positioning techniques | |
| R1-2203165 | Error source for NR RAT-dependent positioning | Huawei, HiSilicon |
| R1-2203177 | Initial Views on solutions for integrity of RAT-dependent positioning techniques | Nokia, Nokia Shanghai Bell |
| R1-2203336 | Consideration on solutions for integrity of RAT dependent positioning techniques | Spreadtrum Communications |
| R1-2203468 | Discussion on solutions for integrity of RAT dependent positioning techniques | CATT |
| R1-2203567 | Discussion on solutions for integrity of RAT dependent positioning | vivo |
| R1-2203625 | Discussion on integrity of RAT dependent positioning | ZTE |
| R1-2203739 | Considerations on solution for integrity of RAT dependent positioning techniques | Sony |
| R1-2203912 | Discussion on Integrity of RAT Dependent Positioning | Samsung |
| R1-2203965 | Discussions on Integrity for NR Positioning | OPPO |
| R1-2204133 | Integrity for RAT dependent positioning techniques | InterDigital, Inc. |
| R1-2204311 | Discussion on solutions for integrity of RAT-dependent positioning techniques | CMCC |
| R1-2204386 | Discussion on solutions for integrity of RAT dependent positioning techniques | NTT DOCOMO, INC. |
| R1-2204482 | Consideration on solutions for integrity of RAT dependent positioning techniques | Spreadtrum Communications |
| R1-2204523 | Discussion on integrity of RAT dependent positioning techniques | LG Electronics |
| R1-2204560 | Integrity for RAT-dependent positioning | Lenovo |
| R1-2204668 | Views on solutions for integrity of RAT dependent positioning techniques | Sharp |
| R1-2204951 | Solutions for integrity of RAT dependent positioning techniques | Ericsson |
| R1-2205039 | Integrity for RAT dependent positioning | Qualcomm Incorporated |
| R1-2205344 | Feature Lead summary #1 on Email discussion [109-e-R18-Pos-05] on integrity of RAT dependent positioning techniques | Moderator (InterDigital) |
| 9.5.2.2 | Improved accuracy based on NR carrier phase measurement | |
| R1-2203166 | Discussion on NR carrier phase positioning | Huawei, HiSilicon |
| R1-2203178 | Initial Views on improved accuracy based on NR carrier phase measurement | Nokia, Nokia Shanghai Bell |
| R1-2203337 | Consideration on improved accuracy based on NR carrier phase measurement | Spreadtrum Communications |
| R1-2203469 | Discussion on improved accuracy based on NR carrier phase measurement | CATT |
| R1-2203568 | Discussion on carrier phase measurement enhancements | vivo |
| R1-2203626 | Discussion on Carrier Phase Measurement Based Positioning | ZTE |
| R1-2203634 | Use cases and applications on Carrier Phase Based Positioning for NR | Locaila |
| R1-2203635 | Continuous PRS for improved carrier phase measurement Document for: Discussion & Decision | Dankook University |
| R1-2203660 | Discussion on improved accuracy based on NR carrier phase measurement | China Telecom |
| R1-2203753 | On carrier phase measurement | MediaTek Inc. |
| R1-2203824 | Improved accuracy based on NR carrier phase measurement | xiaomi |
| R1-2203913 | Discussion on NR Carrier Phase Measurement | Samsung |
| R1-2203966 | Discussions on Carrier Phase Measurement for NR Positioning | OPPO |
| R1-2204134 | Potential solutions for carrier phase based positioning | InterDigital, Inc. |
| R1-2204312 | Discussion on carrier phase positioning | CMCC |
| R1-2204387 | Discussion on improved accuracy based on NR carrier phase measurement | NTT DOCOMO, INC. |
| R1-2204483 | Consideration on improved accuracy based on NR carrier phase measurement | Spreadtrum Communications |
| R1-2204524 | Discussion on OFDM based carrier phase measurement in NR | LG Electronics |
| R1-2204561 | On NR carrier phase measurements | Lenovo |
| R1-2204669 | Views on improved accuracy based on NR carrier phase measurement | Sharp |
| R1-2204807 | Design Aspects of Carrier Phase Measurements for NR Positioning Enhancements | Intel Corporation |
| R1-2204836 | NR carrier phase measurements for positioning | Fraunhofer IIS, Fraunhofer HHI |
| R1-2204952 | Improved accuracy based on NR carrier phase measurement | Ericsson |
| R1-2205040 | Phase Measurements in NR Positioning | Qualcomm Incorporated |
| R1-2205164 | FL Summary for improved accuracy based on NR carrier phase measurement | Moderator (CATT) |
| R1-2205165 | FL Summary #2 for improved accuracy based on NR carrier phase measurement | Moderator (CATT) |
| R1-2205166 | FL Summary #3 for improved accuracy based on NR carrier phase measurement | Moderator (CATT) |
| 9.5.2.3 | LPHAP (Low Power High Accuracy Positioning) | |
| R1-2203167 | Requirements and evaluation methodology for LPHAP | Huawei, HiSilicon |
| R1-2203179 | Initial Views on LPHAP | Nokia, Nokia Shanghai Bell |
| R1-2203470 | Discussion on Low Power High Accuracy Positioning | CATT |
| R1-2203569 | Discussion on Low Power High Accuracy Positioning | vivo |
| R1-2203627 | Discussion on low power high accuracy positioning(LPHAP) | ZTE |
| R1-2203825 | LPHAP (Low Power High Accuracy Positioning) | xiaomi |
| R1-2203914 | Discussion on LPHAP | Samsung |
| R1-2203967 | Discussion on Low Power High Accuracy Positioning | OPPO |
| R1-2204155 | Discussions on Low Power High Accuracy Positioning (LPHAP) techniques | InterDigital, Inc. |
| R1-2204313 | Discussion on low power high accuracy positioning | CMCC |
| R1-2204426 | Discussion on Low Power High Accuracy Positioning | Quectel |
| R1-2204525 | Discussion on LPHAP in idle/inactive state | LG Electronics |
| R1-2204562 | LPHAP considerations | Lenovo |
| R1-2204670 | Views on low power high accuracy positioning | Sharp |
| R1-2204953 | On the requirements, evaluations and potential enhancements for Low Power High Accuracy Positioning) | Ericsson |
| R1-2205041 | Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning | Qualcomm Incorporated |
| R1-2205354 | FL summary #2 for AI 9.5.2.3 – low power high accuracy positioning | Moderator (CMCC) |
| R1-2205355 | FL summary #3 for AI 9.5.2.3 – low power high accuracy positioning | Moderator (CMCC) |
| R1-2205594 | FL summary for AI 9.5.2.3 – low power high accuracy positioning (EOM) | Moderator (CMCC) |
| 9.5.3 | Positioning for RedCap UEs | |
| R1-2203168 | Discussion on RedCap positioning | Huawei, HiSilicon |
| R1-2203180 | Initial Views on Positioning for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2203471 | Discussion on positioning for RedCap UEs | CATT |
| R1-2203570 | Discussion on positioning for RedCap Ues | vivo |
| R1-2203628 | Discussion on Positioning for RedCap UE | ZTE |
| R1-2203696 | Discussion on positioning support for RedCap UEs | NEC |
| R1-2203740 | Discussion on positioning for RedCap UEs | Sony |
| R1-2203754 | The potential solutions for RedCap UEs for positioning | MediaTek Inc. |
| R1-2203826 | Initial views on the positioning for RedCap UEs | xiaomi |
| R1-2203915 | Discussion on Positioning for RedCap Ues | Samsung |
| R1-2203968 | Discussion on Positioning for RedCap Ues | OPPO |
| R1-2204157 | Evaluation assumptions and potential solutions for positioning for RedCap UEs | InterDigital, Inc. |
| R1-2204254 | Discussions on Positioning for RedCap UEs | Apple |
| R1-2204314 | Discussion on RedCap positioning | CMCC |
| R1-2204388 | Discussion on positioning for RedCap UEs | NTT DOCOMO, INC. |
| R1-2204425 | Discussion on Positioning for RedCap UEs | Quectel |
| R1-2204526 | Discussion on positioning support for RedCap Ues | LG Electronics |
| R1-2204563 | Positioning for RedCap devices | Lenovo |
| R1-2204671 | Views on positioning for RedCap UEs | Sharp |
| R1-2204808 | On enhancements for NR positioning support of RedCap UEs | Intel Corporation |
| R1-2204954 | Positioning for RedCap Ues | Ericsson |
| R1-2205042 | Positioning for Reduced Capabilities UEs | Qualcomm Incorporated |
| R1-2205526 | Feature Lead Summary#1 for [109-e-R18-Pos-08] Positioning for RedCap Ues | Moderator (Ericsson) |
| R1-2205636 | Feature Lead Summary#2 for [109-e-R18-Pos-08] Positioning for RedCap Ues | Moderator (Ericsson) |
| 9.5.4 | Other | |
| R1-2203181 | Initial Views on Other topics for Positioning | Nokia, Nokia Shanghai Bell |
| R1-2203472 | Discussion on solutions of carrier phase positioning in multipath scenarios | CATT |
| R1-2203571 | Discussion on PRS measurement in IDLE state | vivo |
| R1-2203629 | Discussion on Positioning with Multiple Frequency Layers (Carriers) | ZTE |
| R1-2203916 | Discussion on expended and improved NR positioning | Samsung |
| R1-2204158 | Efficient usage of available bandwidths for positioning | InterDigital, Inc. |
| R1-2204916 | Considerations on the support of PRS/SRS bandwidth aggregation | Huawei, HiSilicon, China Unicom |
| R1-2204955 | Considerations for PRS/SRS bandwidth aggregation | Ericsson |
| 9.6 | Study on further NR RedCap (reduced capability) UE complexity reduction | |
| R1-2203121 | Draft skeleton for TR 38.865 (Study on further NR RedCap UE complexity reduction) | Rapporteur (Ericsson) |
| R1-2204058 | Work plan for Study on further NR RedCap UE complexity reduction | Rapporteur (Ericsson) |
| R1-2205431 | FL summary for TR skeleton for Rel-18 SI on further NR RedCap UE complexity reduction | Moderator (Ericsson) |
| R1-2205432 | Draft skeleton for TR 38.865 (Study on further NR RedCap UE complexity reduction) | Rapporteur (Ericsson) |
| R1-2205575 | Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) | Ad-hoc Chair (CMCC) |
| R1-2205621 | TR 38.865 v0.0.0 (Study on further NR RedCap UE complexity reduction) | Rapporteur (Ericsson) |
| R1-2205693 | TR 38.865 v0.0.1 (Study on further NR RedCap UE complexity reduction) | Rapporteur (Ericsson) |
| R1-2205696 | FL summary for evaluation templates for Rel-18 RedCap SI | Moderator (Ericsson) |
| 9.6.1 | Potential solutions to further reduce UE complexity | |
| R1-2203054 | Discussion of complexity reduction techniques for RedCap UEs in Rel-18 | FUTUREWEI |
| R1-2203117 | Potential solutions to further reduce UE complexity | Ericsson |
| R1-2203169 | Discussion on potential solutions to further reduce UE complexity | Huawei, HiSilicon |
| R1-2203338 | Discussion on potential solutions to further reduce UE complexity | Spreadtrum Communications |
| R1-2203473 | Discussion on solutions to further reduce UE complexity in Rel-18 | CATT |
| R1-2203572 | Techniques to further reduce the complexity of RedCap devices | vivo, Guangdong Genius |
| R1-2203600 | Discussion on further RedCap UE complexity reduction | ZTE, Sanechips |
| R1-2203661 | Discussion on potential solutions to further reduce UE complexity | China Telecom |
| R1-2203761 | Further reduce UE complexity for eRedCap | Panasonic |
| R1-2203827 | Discussion on the potential complexity reduction solutions for further UE complexity reduction | xiaomi |
| R1-2203917 | Further UE complexity reduction for eRedCap | Samsung |
| R1-2203995 | Solution study on further reduced UE complexity | OPPO |
| R1-2204038 | Further UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
| R1-2204176 | Discussions on potential solutions to further reduce UE complexity | Sharp |
| R1-2204188 | Discussions on potential solutions to further reduce UE complexity | Sharp |
| R1-2204255 | On further RedCap UE complexity reduction features | Apple |
| R1-2204315 | Discussion on further reduced UE complexity | CMCC |
| R1-2204389 | Discussion on potential solutions for further UE complexity reduction | NTT DOCOMO, INC. |
| R1-2204437 | Discussion on potential solutions to further reduce UE complexity | NEC |
| R1-2204484 | Discussion on potential solutions to further reduce UE complexity | Spreadtrum Communications |
| R1-2204504 | Potential solutions to further reduce UE complexity | Lenovo |
| R1-2204582 | Discussion on potential solutions to further reduce UE complexity | Transsion Holdings |
| R1-2204626 | Discussion on potential solutions for further UE complexity reduction | LG Electronics |
| R1-2204714 | On potential solutions to further reduce UE complexity | MediaTek Inc. |
| R1-2204747 | On further complexity reduction of NR UE | Nordic Semiconductor ASA |
| R1-2204809 | On solutions to further reduce UE complexity | Intel Corporation |
| R1-2204829 | Potential techniques for further RedCap UE complexity reduction | InterDigital, Inc. |
| R1-2204879 | Considerations for further UE complexity reduction | Sierra Wireless. S.A. |
| R1-2205043 | Further complexity reduction for eRedCap device | Qualcomm Incorporated |
| R1-2205281 | FL summary #1 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2205433 | FL summary #2 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2205434 | FL summary #3 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| R1-2205435 | FL summary #4 on potential solutions to further reduce RedCap UE complexity | Moderator (Ericsson) |
| 9.6.2 | Simulation needs and assumptions | |
| R1-2203055 | Simulations for the Rel-18 RedCap SI | FUTUREWEI |
| R1-2203118 | Simulation needs and assumptions for further RedCap UE complexity reduction | Ericsson |
| R1-2203170 | Discussion on simulation needs and assumptions | Huawei, HiSilicon |
| R1-2203339 | Discussion on evaluation needs and assumptions for eRedCap | Spreadtrum Communications |
| R1-2203474 | Views on evaluation needs based on different assumptions | CATT |
| R1-2203573 | Discussion on potential simulation for eRedCap | vivo, Guangdong Genius |
| R1-2203601 | Evaluation requirements for Rel-18 RedCap UE | ZTE, Sanechips |
| R1-2203828 | Simulation needs and assumptions on further NR Redcap UE complexity reduction | xiaomi |
| R1-2203918 | Evaluations for eRedCap | Samsung |
| R1-2203996 | Simulation and evaluation for RedCap enhancement | OPPO |
| R1-2204039 | Evaluation assumptions for further complexity reduction | Nokia, Nokia Shanghai Bell |
| R1-2204316 | Discussion on simulation needs and assumptions | CMCC |
| R1-2204390 | Discussion on simulations and assumptions for further UE complexity reduction | NTT DOCOMO, INC. |
| R1-2204485 | Discussion on evaluation needs and assumptions for eRedCap | Spreadtrum Communications |
| R1-2204505 | Evaluation needs and assumptions for further NR RedCap | Lenovo |
| R1-2204583 | Discussion on simulation needs and assumptions | Transsion Holdings |
| R1-2204627 | Discussion on simulation needs for further UE complexity reduction | LG Electronics |
| R1-2204715 | On simulation needs and assumptions for RedCap UEs | MediaTek Inc. |
| R1-2204810 | On simulations for further reduced UE complexity | Intel Corporation |
| R1-2204830 | Simulation needs for further RedCap UE complexity reduction | InterDigital, Inc. |
| R1-2205044 | Evaluation for eRedCap SI | Qualcomm Incorporated |
| R1-2205257 | FL summary #1 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO) |
| R1-2205416 | FL summary #2 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO, INC.) |
| R1-2205521 | FL summary #3 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO, INC.) |
| R1-2205544 | FL summary #4 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO, INC.) |
| R1-2205604 | FL summary #5 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO, INC.) |
| R1-2205643 | FL summary #6 on simulation needs and assumptions for further reduce UE complexity | Moderator (NTT DOCOMO, INC.) |
| 9.6.3 | Other | |
| R1-2203119 | Initial evaluation results for further RedCap UE complexity reduction | Ericsson |
| R1-2203340 | Other considerations for eRedCap | Spreadtrum Communications |
| R1-2203475 | Views on coexistence between Rel-17 and Rel-18 RedCap UE | CATT |
| R1-2203574 | Feature extension for Rel-18 Devices | vivo, Guangdong Genius |
| R1-2203602 | Other aspects for Rel-18 eRedCap UE | ZTE, Sanechips |
| R1-2203829 | Other aspects on further NR Redcap UE complexity reduction | xiaomi |
| R1-2204040 | On other aspects for RedCap evolution | Nokia, Nokia Shanghai Bell |
| R1-2204095 | Early thoughts on Rel-18 RedCap UE features | FUTUREWEI |
| R1-2204317 | Discussion on other aspects for RedCap UE | CMCC |
| R1-2204486 | Other considerations for eRedCap | Spreadtrum Communications |
| R1-2204917 | Overall considerations for Rel-18 RedCap | Huawei, HiSilicon |
| 9.7 | Study on network energy savings for NR | |
| R1-2203947 | TR 38.864 skeleton for study on network energy savings for NR | Rapporteur (Huawei) |
| R1-2204919 | Work plan for NR network energy savings | Huawei |
| R1-2205307 | TR 38.864 skeleton for study on network energy savings for NR | Rapporteur (Huawei) |
| R1-2205694 | TR 38.864 v0.0.2 for study on network energy savings for NR | Rapporteur (Huawei) |
| 9.7.1 | NW energy savings performance evaluation | |
| R1-2203172 | Discussion on performance evaluation for network energy saving | Huawei, HiSilicon |
| R1-2203224 | NW energy savings performance evaluation | Nokia, Nokia Shanghai Bell |
| R1-2203341 | Discussion on performance evaluation of network energy savings | Spreadtrum Communications |
| R1-2203481 | Evaluation Methodology and Power Model for Network Energy Saving | CATT |
| R1-2203575 | Discussions on NW energy savings performance evaluation | vivo |
| R1-2203603 | Discussion on NW energy saving performance evaluation | ZTE, Sanechips |
| R1-2203662 | Discussion on network energy saving performance evaluation methods | China Telecom |
| R1-2203830 | Discussions on performance evaluation of network energy saving | xiaomi |
| R1-2203919 | NW energy savings performance evaluation | Samsung |
| R1-2204073 | On network energy savings evaluation methodology and power model | Panasonic |
| R1-2204100 | Base station energy consumption model, evaluation methodology, and KPIs for network energy saving | FUTUREWEI |
| R1-2204256 | On NW energy savings performance evaluation | Apple |
| R1-2204318 | Discussion on network energy saving performance evaluation | CMCC |
| R1-2204391 | Discussion on NW energy savings performance evaluation | NTT DOCOMO, INC. |
| R1-2204487 | Discussion on performance evaluation of network energy savings | Spreadtrum Communications |
| R1-2204628 | Discussion on performance evaluation for network energy savings | LG Electronics |
| R1-2204686 | NW energy savings performance evaluation | MediaTek Inc. |
| R1-2204811 | Discussion on Network Energy Saving Evaluations | Intel Corporation |
| R1-2204831 | Performance evaluation for network energy saving | InterDigital, Inc. |
| R1-2204881 | Modeling and evaluation methodology for network energy saving | Ericsson |
| R1-2205045 | NW energy savings performance evaluation | Qualcomm Incorporated |
| R1-2205083 | Initial views on NW energy savings performance evaluation | Fujitsu Limited |
| R1-2205178 | Discussion on NW energy saving performance evaluation | ZTE, Sanechips |
| R1-2205308 | FL summary#1 for performance evaluation for NR NW energy savings | Moderator (Huawei) |
| R1-2205402 | FL summary#2 for performance evaluation for NR NW energy savings | Moderator (Huawei) |
| R1-2205468 | FL summary#3 for performance evaluation for NR NW energy savings | Moderator (Huawei) |
| R1-2205551 | FL summary#4 for performance evaluation for NR NW energy savings | Moderator (Huawei) |
| 9.7.2 | Network energy saving techniques | |
| R1-2203173 | Discussion on network energy saving techniques | Huawei, HiSilicon |
| R1-2203225 | Network energy saving techniques | Nokia, Nokia Shanghai Bell |
| R1-2203342 | Discussion on network energy saving techniques | Spreadtrum Communications |
| R1-2203482 | Network Energy Saving techniques in time, frequency, and spatial domain | CATT |
| R1-2203576 | Discussions on network energy saving techniques | vivo |
| R1-2203604 | Discussion on NW energy saving techniques | ZTE, Sanechips |
| R1-2203636 | On Network Energy Saving Techniques | Fraunhofer IIS, Fraunhofer HHI |
| R1-2203663 | Discussion on network energy saving techniques | China Telecom |
| R1-2203831 | Discussions on techniques for network energy saving | xiaomi |
| R1-2203920 | Network energy saving techniques | Samsung |
| R1-2203936 | Discussion on network energy saving techniques | NEC |
| R1-2204010 | Study on network energy saving techniques | OPPO |
| R1-2204043 | Discussion on network energy saving techniques | CENC |
| R1-2204044 | Discussion on network energy saving techniques | CENC |
| R1-2204045 | Discussion on network energy saving techniques | CENC |
| R1-2204074 | Discussion on potential network energy saving techniques | Panasonic |
| R1-2204101 | Potential enhancements for network energy saving | FUTUREWEI |
| R1-2204257 | Discussion on Network energy saving techniques | Apple |
| R1-2204319 | Discussion on network energy saving techniques | CMCC |
| R1-2204392 | Discussion on NW energy saving techniques | NTT DOCOMO, INC. |
| R1-2204424 | Network energy saving techniques | Lenovo |
| R1-2204443 | Study on potential L1 network energy saving techniques for NR | ITRI |
| R1-2204488 | Discussion on network energy saving techniques | Spreadtrum Communications |
| R1-2204629 | Discussion on physical layer techniques for network energy savings | LG Electronics |
| R1-2204687 | Network energy saving techniques | MediaTek Inc. |
| R1-2204756 | Discussion on Network energy saving techniques | CEWiT |
| R1-2204812 | Discussion on Network Energy Saving Techniques | Intel Corporation |
| R1-2204832 | Potential techniques for network energy saving | InterDigital, Inc. |
| R1-2204882 | Network energy saving techniques | Ericsson |
| R1-2205046 | Network energy saving techniques | Qualcomm Incorporated |
| R1-2205070 | Potential Techniques of Network Energy Savings | Rakuten Mobile |
| R1-2205084 | Initial views on network energy saving techniques | Fujitsu Limited |
| R1-2205140 | Discussion Summary for energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2205141 | Summary #1 for email discussion on energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2205533 | Summary #2 for email discussion on energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| R1-2205554 | Summary #3 for email discussion on energy saving techniques of NW energy saving SI | Moderator (Intel Corporation) |
| 9.7.3 | Other | |
| R1-2203226 | Others | Nokia, Nokia Shanghai Bell |
| R1-2203483 | Evaluation results of network energy saving | CATT |
| R1-2203577 | Initial evaluation results for network energy saving scheme | vivo |
| R1-2203605 | Consideration about NW energy saving | ZTE, Sanechips |
| R1-2204320 | Discussion on network energy saving scheme in deployment | CMCC |
| R1-2204883 | Other aspects related to network energy saving | Ericsson |
| R1-2204918 | Discussion on information assistance for network energy saving | Huawei, HiSilicon |
| R1-2205160 | Evaluation results of network energy saving | CATT |
| R1-2205175 | Initial evaluation results for network energy saving scheme | vivo |
| 9.8 | Study on NR network-controlled repeaters | |
| R1-2203235 | TR skeleton for NR network-controlled repeaters | ZTE |
| R1-2203236 | Work plan for NR network-controlled repeaters | ZTE |
| R1-2205231 | TR 38.867 skeleton for Study on NR network-controlled repeaters | Rapporteur (ZTE) |
| R1-2205496 | TR 38.867 v0.1.0 for Study on NR network-controlled repeaters | Rapporteur (ZTE) |
| 9.8.1 | Side control information to enable NR network-controlled repeaters | |
| R1-2203133 | Discussion on side control information to enable NR network-controlled repeaters | Huawei, HiSilicon |
| R1-2203237 | Discussion on side control information to enable NR network-controlled repeaters | ZTE |
| R1-2203343 | Discussion on side control information to enable NR network-controlled repeaters | Spreadtrum Communications |
| R1-2203354 | Discussion on side control information to enable NR network-controlled repeaters | Nokia, Nokia Shanghai Bell |
| R1-2203376 | Discussions on side control information to enable NR network-controlled repeaters | InterDigital, Inc. |
| R1-2203476 | Discussion on side control information for NR network-controlled repeaters | CATT |
| R1-2203578 | Discussion on side control information to enable NR network-controlled repeaters | vivo |
| R1-2203697 | Discussion on side control information for network-controlled repeaters | NEC |
| R1-2203741 | Considerations on side control information to enable NR network-controlled repeaters | Sony |
| R1-2203832 | Discussion on side control information to enable NR network-controlled repeaters | xiaomi |
| R1-2203921 | Side control information to enable NR network-controlled repeaters | Samsung |
| R1-2204064 | Discussion on side control information for network controllable repeater | Lenovo |
| R1-2204066 | Side Control Information for Network-Controlled Repeaters | Charter Communications, Inc |
| R1-2204086 | Side Control Information for supporting initial access | CableLabs |
| R1-2204119 | Side control information for network-controlled repeaters | SHARP Corporation |
| R1-2204258 | Potential side control information for NW-controlled repeater | Apple |
| R1-2204321 | Discussion on Side control information to enable NR network-controlled repeaters | CMCC |
| R1-2204393 | Discussion on side control information to enable NR network-controlled repeaters | NTT DOCOMO, INC. |
| R1-2204489 | Discussion on side control information to enable NR network-controlled repeaters | Spreadtrum Communications |
| R1-2204532 | Discussion on side control information for NCR | LG Electronics |
| R1-2204565 | Discussion on side control signals for network-controlled repeaters | Panasonic |
| R1-2204610 | Discussion on side control information to enable NR network-controlled repeaters | CAICT |
| R1-2204642 | Control information for enabling NW-controlled repeaters | Ericsson |
| R1-2204653 | Discussions on side control information for network-controlled repeater | ETRI |
| R1-2204688 | Side control information for network-controlled repeaters | MediaTek Inc. |
| R1-2204757 | Discussion on Side control information to enable NR network-controlled repeaters | CEWiT, IITK |
| R1-2204813 | Discussion on Side control information to enable NR network-controlled repeater | Intel Corporation |
| R1-2204847 | Discussion on side control information to enable NR network-controlled repeaters | KDDI Corporation |
| R1-2204864 | Side control information to enable NR network-controlled repeaters | AT&T |
| R1-2205047 | On side control information for network controlled repeaters (NCR) | Qualcomm Incorporated |
| R1-2205068 | Initial view on Network-controlled repeater | Rakuten Mobile |
| R1-2205085 | Side control information for NR network-controlled repeaters | Fujitsu Limited |
| R1-2205233 | Summary#1 of Email discussion on side control information | Moderator (ZTE) |
| R1-2205340 | Summary#2 of Email discussion on side control information | Moderator (ZTE) |
| R1-2205495 | Summary#3 of Email discussion on side control information | Moderator (ZTE) |
| 9.8.2 | L1/L2 signaling for side control information | |
| R1-2203134 | Discussion on L1/L2 signaling for side control information | Huawei, HiSilicon |
| R1-2203238 | Discussion on L1/L2 signaling for side control information | ZTE |
| R1-2203355 | Discussion on L1/L2 signaling for side control information of network-controlled repeaters | Nokia, Nokia Shanghai Bell |
| R1-2203377 | Discussion on L1/L2 signaling for side control information | InterDigital, Inc. |
| R1-2203477 | Discussion on signalling of side control informaion for NR network-controlled repeaters | CATT |
| R1-2203579 | Discussion on signaling for side control information | vivo |
| R1-2203698 | Discussion on signaling for side control information | NEC |
| R1-2203742 | Considerations on L1/L2 signaling for side control information | Sony |
| R1-2203833 | Discussion on L1/L2 signalling for side control information | xiaomi |
| R1-2203922 | L1/L2 signaling for side control information | Samsung |
| R1-2204065 | Discussion on L1/L2 signaling for side control information of network-controlled repeaters | Lenovo |
| R1-2204259 | Discussion on L1/L2 signaling for side control information | Apple |
| R1-2204322 | Discussion on L1/L2 signaling for side control information | CMCC |
| R1-2204394 | Discussion on L1/L2 signaling for side control information | NTT DOCOMO, INC. |
| R1-2204533 | Discussion on L1/L2 signaling for side control information | LG Electronics |
| R1-2204643 | Signaling of control information for NW-controlled repeaters | Ericsson |
| R1-2204654 | Discussions on L1/L2 signaling for side control information | ETRI |
| R1-2204689 | L1/L2 control signaling for enabling network controlled repeaters | MediaTek Inc. |
| R1-2204758 | Discussion on L1/L2 signaling for side control information for NCR | CEWiT, IITK |
| R1-2204814 | Disucssion on L1/L2 signaling for side control information | Intel Corporation |
| R1-2204848 | Discussion on L1/L2 signaling for side control information | KDDI Corporation |
| R1-2205048 | On L1-L2 signaling for side control information for NCR | Qualcomm Incorporated |
| R1-2205069 | Initial view on signaling for Network-controlled repeater | Rakuten Mobile |
| R1-2205086 | NR network-controlled repeaters receive signaling of side control information | Fujitsu Limited |
| R1-2205237 | Summary#1 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| R1-2205386 | Summary#2 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| R1-2205456 | Summary#2 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| R1-2205519 | Summary#3 on L1/L2 signaling for side control information | Moderator (Fujitsu) |
| 9.8.3 | Other | |
| R1-2203239 | Discussion on other issues for NR network-controlled repeater | ZTE |
| R1-2203580 | Discussion on in-band repeater | vivo |
| R1-2204067 | Deployment Scenarios for Network-Controlled Repeaters | Charter Communications, Inc |
| R1-2204534 | Discussion on operation scenarios for NCR | LG Electronics |
| R1-2204644 | Terminology for NW-controlled repeaters | Ericsson |
| R1-2204930 | Other considerations for NR network-controlled repeaters | Huawei, HiSilicon |
| R1-2205087 | Other issues on network-controlled repeaters | Fujitsu Limited |
| 9.9 | Enhancement of NR Dynamic Spectrum Sharing (DSS) | |
| R1-2204884 | Work plan for Rel18 WI on Enhancement of NR Dynamic spectrum sharing (DSS) | Ericsson |
| R1-2205576 | Session notes for 9.9 (Enhancement of NR Dynamic Spectrum Sharing (DSS)) | Ad-hoc Chair (CMCC) |
| 9.9.1 | NR PDCCH reception in symbols with LTE CRS REs | |
| R1-2203137 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Huawei, HiSilicon |
| R1-2203210 | Discussion on NR PDCCH reception for DSS | ZTE |
| R1-2203344 | Discussion on NR PDCCH reception in symbols with LTE CRS Res | Spreadtrum Communications |
| R1-2203581 | Discussion on PDCCH reception on CRS symbol | vivo |
| R1-2203648 | Evaluation of NR PDCCH overlapping with LTE CRS | InterDigital, Inc. |
| R1-2203834 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | xiaomi |
| R1-2203923 | Considerations on PDCCH receptions in symbols with LTE CRS | Samsung |
| R1-2204024 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | OPPO |
| R1-2204260 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | Apple |
| R1-2204323 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | CMCC |
| R1-2204395 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | NTT DOCOMO, INC. |
| R1-2204490 | Discussion on NR PDCCH reception in symbols with LTE CRS Res | Spreadtrum Communications |
| R1-2204630 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | LG Electronics |
| R1-2204709 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | MediaTek Inc. |
| R1-2204815 | Discussion on NR PDCCH reception in DSS | Intel Corporation |
| R1-2204823 | NR PDCCH overlapping with LTE CRS | Nokia, Nokia Shanghai Bell |
| R1-2204885 | NR PDCCH reception in symbols with LTE CRS REs | Ericsson |
| R1-2205049 | NR PDCCH reception in symbols with LTE CRS REs | Qualcomm Incorporated |
| R1-2205173 | Summary#1 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS Res | Moderator (Intel Corporation) |
| R1-2205174 | Summary#2 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2205356 | Summary#3 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2205357 | Summary#4 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| R1-2205697 | Summary#5 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | Moderator (Intel Corporation) |
| 9.9.2 | UE support for two overlapping CRS rate matching patterns | |
| R1-2203138 | Discussion on UE support for two overlapping CRS rate matching patterns | Huawei, HiSilicon |
| R1-2203211 | Discussion on support of two overlapping CRS patterns for DSS | ZTE |
| R1-2203345 | Discussion on UE support for two overlapping CRS rate matching patterns | Spreadtrum Communications |
| R1-2203582 | Discussion on two overlapping CRS rate matching patterns | vivo |
| R1-2203649 | Supporting two overlapping CRS rate matching patterns | InterDigital, Inc. |
| R1-2203835 | Discussion on UE support for two overlapping CRS rate matching patterns | xiaomi |
| R1-2203924 | Two overlapping CRS rate matching patterns | Samsung |
| R1-2204025 | Discussion on UE support for two overlapping CRS rate matching patterns | OPPO |
| R1-2204261 | Discussion on UE supporting for two overlapping CRS rate matching patterns | Apple |
| R1-2204396 | Discussion on LTE CRS rate matching pattern | NTT DOCOMO, INC. |
| R1-2204491 | Discussion on UE support for two overlapping CRS rate matching patterns | Spreadtrum Communications |
| R1-2204710 | Discussion on supporting two overlapping CRS rate matching pattern | MediaTek Inc. |
| R1-2204824 | Support for 2 overlapping CRS patterns | Nokia, Nokia Shanghai Bell |
| R1-2204886 | UE support for overlapping CRS rate matching patterns | Ericsson |
| R1-2205050 | UE support for two overlapping CRS rate-matching patterns | Qualcomm Incorporated |
| R1-2205258 | Feature lead summary #1 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2205259 | Feature lead summary #2 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2205499 | Feature lead summary #3 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| R1-2205500 | Feature lead summary #4 on UE support for two overlapping CRS rate matching patterns | Moderator (ZTE) |
| 9.9.3 | Other | |
| R1-2203836 | Other issues on enhancement of NR Dynamic Spectrum Sharing | xiaomi |
| R1-2204332 | Discussion on PDCCH reception with two overlapping CRS patterns for DSS | ZTE |
| R1-2204887 | Other aspects related to DSS enhancements | Ericsson |
| R1-2204910 | Discussion on additional evaluation results for NR PDCCH in collision with LTE CRS | Huawei, HiSilicon |
| 9.10 | Multi-carrier enhancements for NR | |
| R1-2204397 | Work plan for Multi-carrier enhancements | NTT DOCOMO, INC. |
| 9.10.1 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | |
| R1-2203135 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single scheduling DCI | Huawei, HiSilicon |
| R1-2203207 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | ZTE |
| R1-2203276 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Nokia, Nokia Shanghai Bell |
| R1-2203346 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Spreadtrum Communications |
| R1-2203448 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CATT |
| R1-2203583 | Discussion on multi-cell scheduling | vivo |
| R1-2203664 | Discussion on multi-cell scheduling with a single DCI | China Telecom |
| R1-2203688 | Discussion on Multi-cell PXSCH scheduling with a single DCI | NEC |
| R1-2203706 | Discussion on multi-cell scheduling via a single DCI | Lenovo |
| R1-2203800 | Discussion on the design of multi-cell scheduling with a single DCI | xiaomi |
| R1-2203842 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | Langbo |
| R1-2203925 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Samsung |
| R1-2204026 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | OPPO |
| R1-2204087 | Multi-cell scheduling with a single DCI | InterDigital, Inc. |
| R1-2204186 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CAICT |
| R1-2204262 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | Apple |
| R1-2204324 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | CMCC |
| R1-2204398 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | NTT DOCOMO, INC. |
| R1-2204492 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | Spreadtrum Communications |
| R1-2204631 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | LG Electronics |
| R1-2204697 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | MediaTek Inc. |
| R1-2204816 | Discussions on multi-cell scheduling with a single DCI | Intel Corporation |
| R1-2204865 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Charter Communications |
| R1-2204888 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | Ericsson |
| R1-2205051 | Multi-cell PUSCH and PDSCH scheduling with a single DCI | Qualcomm Incorporated |
| R1-2205073 | Discussion on Multicarrier scheduling with a single DCI | FGI |
| R1-2205088 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | Fujitsu Limited |
| R1-2205234 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2205235 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2205236 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2205486 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2205487 | Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| R1-2205488 | Feature lead summary#6 on multi-cell PUSCH/PDSCH scheduling with a single DCI | Moderator (Lenovo) |
| 9.10.2 | Multi-carrier UL Tx switching scheme | |
| R1-2203136 | Discussion on multi-carrier UL Tx switching | Huawei, HiSilicon |
| R1-2203208 | Discussion on Multi-carrier UL Tx switching scheme | ZTE |
| R1-2203347 | Discussion on multi-carrier UL Tx switching scheme | Spreadtrum Communications |
| R1-2203449 | Discussion on multi-carrier UL Tx switching scheme | CATT |
| R1-2203584 | Discussion on UL TX switching | vivo |
| R1-2203665 | Discussion on UL Tx switching across up to 3 or 4 bands | China Telecom |
| R1-2203743 | Considerations on Multi-carrier UL Tx switching scheme | Sony |
| R1-2203801 | Discussion on multi-carrier UL Tx switching scheme | xiaomi |
| R1-2203926 | Multi-carrier UL Tx switching scheme | Samsung |
| R1-2204027 | Discussion on multi-carrier UL Tx switching scheme | OPPO |
| R1-2204088 | Multi-carrier UL Tx switching scheme | InterDigital, Inc. |
| R1-2204263 | On the support of multi-carrier UL Tx switching scheme | Apple |
| R1-2204325 | Discussion on multi-carrier UL Tx switching scheme | CMCC |
| R1-2204399 | Discussion on multi-carrier UL Tx switching scheme | NTT DOCOMO, INC. |
| R1-2204493 | Discussion on multi-carrier UL Tx switching scheme | Spreadtrum Communications |
| R1-2204632 | Discussion on Multi-carrier UL Tx switching scheme | LG Electronics |
| R1-2204724 | On multi-carrier UL Tx switching scheme | MediaTek Inc. |
| R1-2204817 | Discussions on multi-carrier UL Tx switching scheme | Intel Corporation |
| R1-2204889 | Multi-carrier UL Tx switching | Ericsson |
| R1-2205052 | Discussion on Rel-18 UL Tx switching | Qualcomm Incorporated |
| R1-2205089 | Initial views on multi-carrier UL Tx switching scheme | Fujitsu Limited |
| R1-2205106 | On Multi-Carrier UL Tx Switching | Nokia, Nokia Shanghai Bell |
| R1-2205131 | Discussion on Multi-carrier UL Tx switching scheme | ZTE |
| R1-2205137 | Discussion on multi-carrier UL Tx switching scheme | CATT |
| R1-2205230 | Summary of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2205363 | Summary#2 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2205471 | Summary#3 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| R1-2205501 | [Draft] LS on UL Tx switching across 3 or 4 bands in Rel-18 | Moderator (NTT DOCOMO) |
| R1-2205502 | LS on UL Tx switching across 3 or 4 bands in Rel-18 | RAN1, NTT DOCOMO |
| R1-2205589 | Summary#4 of discussion on multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
| 9.10.3 | Other | |
| R1-2203209 | Simulation evaluation on Rel-18 Multi-carrier enhancement | ZTE |
| R1-2204890 | Other aspects related to multi-carrier enhancements | Ericsson |
| R1-2204909 | Simulation evaluations of single user experience data rate for multi-carrier UL Tx switching | Huawei, HiSilicon |
| 9.11 | Study on XR enhancements for NR | |
| R1-2204673 | TR 38.835 Skeleton for Study on XR enhancements for NR | Rapporteur (Nokia) |
| R1-2205053 | Work plan for Rel-18 SI on XR enhancements for NR | Qualcomm Incorporated |
| R1-2205329 | TR 38.835 Skeleton for Study on XR enhancements for NR | Rapporteur (Nokia) |
| R1-2205419 | [Draft] LS on draft TR 38.835 skeleton | Nokia |
| R1-2205420 | LS on draft TR 38.835 skeleton | RAN1, Nokia |
| R1-2205443 | LS on draft TR 38.835 skeleton | RAN1, Nokia |
| 9.11.1 | XR specific power saving techniques | |
| R1-2203131 | Discussion on XR-specific power saving techniques | Huawei, HiSilicon |
| R1-2203348 | Discussion on XR specific power saving techniques | Spreadtrum Communications |
| R1-2203484 | UE Power saving techniques for XR | CATT |
| R1-2203585 | Discussion on XR specific power saving enhancements | vivo |
| R1-2203606 | Discussion on XR specific power saving techniques | ZTE, Sanechips |
| R1-2203638 | Discussion on power saving enhancements for XR | Ericsson |
| R1-2203666 | Discussion on XR enhancement for NR | China Telecom |
| R1-2203744 | Considerations on power saving techniques for XR | Sony |
| R1-2203802 | Discussion on XR specific power saving | xiaomi |
| R1-2203927 | Considerations on XR-specific Power Savings | Samsung |
| R1-2203940 | Discussion on XR specific power saving techniques | NEC |
| R1-2204028 | Discussion on XR specific power saving techniques | OPPO |
| R1-2204123 | Discussion on XR specific power saving enhancements | InterDigital, Inc. |
| R1-2204177 | XR specific power saving techniques | TCL Communication Ltd. |
| R1-2204264 | Views on XR specific power saving techniques | Apple |
| R1-2204326 | Discussion on XR-specific power saving techniques | CMCC |
| R1-2204400 | Discussion on XR specific power saving techniques | NTT DOCOMO, INC. |
| R1-2204414 | XR-specific power saving techniques | Lenovo |
| R1-2204444 | Discussion on XR specific power saving techniques | ITRI |
| R1-2204494 | Discussion on XR specific power saving techniques | Spreadtrum Communications |
| R1-2204633 | Discussion on XR-specific power saving techniques | LG Electronics |
| R1-2204655 | Discussion on power saving techniques for XR | ETRI |
| R1-2204674 | Discussion on XR-specific power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204698 | On XR specific power saving techniques | MediaTek Inc. |
| R1-2204818 | Discussion on power saving enhancements for XR applications | Intel Corporation |
| R1-2205054 | Power saving techniques for XR | Qualcomm Incorporated |
| R1-2205055 | Moderator Summary#1 on XR specific power saving techniques | Qualcomm Incorporated |
| R1-2205176 | Power saving techniques for XR | Qualcomm Incorporated |
| R1-2205410 | Moderator Summary#2 on XR specific power saving techniques | Moderator (Qualcomm) |
| R1-2205411 | Moderator Summary#3 on XR specific power saving techniques | Moderator (Qualcomm) |
| R1-2205412 | Final Moderator Summary on XR specific power saving techniques | Moderator (Qualcomm) |
| R1-2205413 | Draft Reply LS on UE Power Saving for XR and Media Services | Moderator (Qualcomm) |
| R1-2205530 | Draft Reply LS on UE Power Saving for XR and Media Services | Moderator (Qualcomm) |
| R1-2205531 | Reply LS on UE Power Saving for XR and Media Services | RAN1, Qualcomm |
| 9.11.2 | XR-specific capacity enhancements techniques | |
| R1-2203065 | XR Capacity Evaluation and Enhancements | FUTUREWEI |
| R1-2203132 | Discussion on XR-specific capacity enhancements techniques | Huawei, HiSilicon |
| R1-2203256 | Discussion on potential SPS enhancements for XR | CEWiT |
| R1-2203349 | XR capacity consideration | Spreadtrum Communications |
| R1-2203485 | NR enhancement for XR capacity improvement | CATT |
| R1-2203586 | Discussion on XR specific capacity enhancements | vivo |
| R1-2203607 | Discussion on XR specific capacity enhancements techniques | ZTE, Sanechips |
| R1-2203639 | Discussion on capacity enhancements for XR | Ericsson |
| R1-2203689 | Discussion on XR-specific capacity enhancements | NEC |
| R1-2203745 | Considerations on capacity enhancements techniques for XR | Sony |
| R1-2203803 | Discussion on XR specific capacity enhancements | xiaomi |
| R1-2203928 | Considerations on XR Capacity Improvements | Samsung |
| R1-2203934 | Discussion on XR specific capacity improvement techniques | Panasonic |
| R1-2204029 | Discussion on XR specific capacity enhancements techniques | OPPO |
| R1-2204124 | Discussion on XR specific capacity enhancements | InterDigital, Inc. |
| R1-2204129 | Discussion on XR specific capacity enhancements techniques | III |
| R1-2204178 | XR-specific capacity enhancements techniques | TCL Communication Ltd. |
| R1-2204265 | Views on XR specific capacity enhancements techniques | Apple |
| R1-2204327 | Discussion on XR-specific capacity enhancements techniques | CMCC |
| R1-2204401 | Discussion on XR specific capacity improvement enhancements | NTT DOCOMO, INC. |
| R1-2204415 | XR-specific capacity enhancement techniques | Lenovo |
| R1-2204495 | XR capacity consideration | Spreadtrum Communications |
| R1-2204634 | Discussion on XR-specific capacity enhancement techniques | LG Electronics |
| R1-2204656 | Discussion on capacity enhancements techniques for XR | ETRI |
| R1-2204675 | Discussion on XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204699 | On XR specific capacity improvement enhancements | MediaTek Inc. |
| R1-2204759 | Discussion on potential SPS enhancements for XR | CEWiT |
| R1-2204819 | Discussion on capacity enhancements for XR applications | Intel Corporation |
| R1-2205056 | Capacity enhancement techniques for XR | Qualcomm Incorporated |
| R1-2205072 | Discussion on XR-specific capacity enhancements techniques | FGI |
| R1-2205265 | FL Summary#1 – Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2205266 | FL Summary#2 – Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2205267 | FL Summary#3 – Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| R1-2205268 | FL Summary#4 – Study on XR Specific Capacity Improvements | Moderator (Ericsson) |
| 9.11.3 | Other | |
| R1-2203486 | XR awareness scheduling and QoS control | CATT |
| R1-2203587 | Discussion on other aspects for XR specific RAN enhancements | vivo |
| R1-2203608 | Consideration about XR services | ZTE, Sanechips |
| R1-2203640 | Discussion on XR-Awareness | Ericsson |
| R1-2204125 | Discussion on XR-Awareness | InterDigital, Inc. |
| R1-2204266 | Considerations on enhancements for XR | Apple |
| R1-2204635 | Other aspects of XR enhancements for NR | LG Electronics |
| R1-2204676 | Performance results of XR-related enhancements | Nokia, Nokia Shanghai Bell |
| R1-2204820 | Views on XR specific RAN enhancement in QoS | III |
| R1-2204908 | Discussion on XR-specific capacity and power issues based on SA2 outcome | Huawei, HiSilicon |
| R1-2205057 | Other enhancements for XR | Qualcomm Incorporated |
| 9.12 | NTN (Non-Terrestrial Networks) enhancements | |
| R1-2204564 | Work plan for NR NTN enhancements | THALES |
| R1-2205577 | Session notes for 9.12 (NTN (Non-Terrestrial Networks) enhancements) | Ad-Hoc Chair (Huawei) |
| 9.12.1 | Coverage enhancement for NR NTN | |
| R1-2203159 | Discussion on coverage enhancement for NR NTN | Huawei, HiSilicon |
| R1-2203240 | Discussion on coverage enhancement for NTN | ZTE |
| R1-2203350 | Consideration on coverage enhancement for NR NTN | Spreadtrum Communications |
| R1-2203389 | Coverage enhancement for NR NTN | MediaTek Inc. |
| R1-2203588 | Discussions on coverage enhancement for NR NTN | vivo |
| R1-2203669 | Discussion on NTN coverage enhancement | Panasonic |
| R1-2203746 | Considerations on improving NR NTN Coverage | Sony |
| R1-2203757 | Discussion on coverage enhancement for NR NTN | CATT |
| R1-2203804 | Discussion on coverage enhancement for NR-NTN | xiaomi |
| R1-2203844 | Solutions for coverage enhancements in NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2203929 | On coverage enhancement for NR NTN | Samsung |
| R1-2203946 | Discussion on coverage enhancements aspects for NR NTN | NEC |
| R1-2204011 | Discussion on coverage enhancement for NR NTN | OPPO |
| R1-2204079 | Consideration on coverage enhancement for NR NTN | Lockheed Martin |
| R1-2204267 | On coverage enhancement for NR NTN | Apple |
| R1-2204328 | Discussion on coverage enhancement for NR NTN | CMCC |
| R1-2204402 | Discussions on coverage enhancement for NR NTN | NTT DOCOMO, INC. |
| R1-2204496 | Consideration on coverage enhancement for NR NTN | Spreadtrum Communications |
| R1-2204515 | Discussion on coverage enhancement for NR NTN | Lenovo |
| R1-2204521 | Discussion on coverage enhancement for NR NTN | LG Electronics |
| R1-2204545 | Discussion on NR NTN coverage enhancement | THALES |
| R1-2204645 | Discussions on Coverage enhancement for NR NTN | Sharp |
| R1-2204662 | On coverage enhancement for NR NTN | Ericsson |
| R1-2204958 | Discussion on Coverage Enhancement for NTN | Fraunhofer IIS - Fraunhofer HHI |
| R1-2205058 | Coverage enhancements for NR NTN | Qualcomm Incorporated |
| R1-2205210 | Summary #1 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO) |
| R1-2205211 | Summary #2 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO) |
| R1-2205212 | Summary #3 on 9.12.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO) |
| R1-2205622 | [Draft] LS on UE antenna gain for NR NTN coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2205623 | LS on UE antenna gain for NR NTN coverage enhancement | RAN1, NTT DOCOMO, INC. |
| 9.12.2 | Disabling of HARQ feedback for IoT NTN | |
| R1-2203160 | Discussion on disabling of HARQ feedback for IoT NTN | Huawei, HiSilicon |
| R1-2203241 | Discussion on disabling of HARQ feedback for IoT-NTN | ZTE |
| R1-2203351 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
| R1-2203390 | Disabling of HARQ for IoT NTN | MediaTek Inc. |
| R1-2203392 | Disabling of HARQ for IoT NTN | Lockheed Martin |
| R1-2203747 | On disabling HARQ feedback for IoT-NTN | Sony |
| R1-2203755 | Disabling of HARQ feedback for IoT NTN | Nordic Semiconductor ASA |
| R1-2203758 | HARQ feedback disabling for IoT NTN | CATT |
| R1-2203805 | Discussion on HARQ operation for IoT NTN | xiaomi |
| R1-2203840 | Disabling of HARQ feedback for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2203930 | Disabling of HARQ feedback for IoT NTN | Samsung |
| R1-2203937 | Disabling of HARQ feedback for IoT NTN | NEC |
| R1-2204012 | Discussion on disabling of HARQ feedback for IoT NTN | OPPO |
| R1-2204080 | On disabling HARQ feedback for IoT NTN | Ericsson |
| R1-2204268 | On disabling of HARQ feedback for IoT NTN | Apple |
| R1-2204329 | Discussion on disabling of HARQ feedback for IoT NTN | CMCC |
| R1-2204497 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
| R1-2204516 | Disabling of HARQ feedback for IoT NTN | Lenovo |
| R1-2204646 | Discussions on Disabling of HARQ feedback for IoT NTN | Sharp |
| R1-2204935 | On disabling HARQ feedback for IOT-NTN | Mavenir |
| R1-2205059 | Disabling HARQ Feedback for IoT-NTN | Qualcomm Incorporated |
| R1-2205415 | Feature lead summary #1 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| R1-2205473 | Feature lead summary #2 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| R1-2205555 | Feature lead summary #3 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
| 9.12.3 | Improved GNSS operations for IoT NTN | |
| R1-2203161 | Discussion on improved GNSS operations for IoT NTN | Huawei, HiSilicon |
| R1-2203242 | Discussion on improved GNSS operation for IoT-NTN | ZTE |
| R1-2203352 | Discussion on improved GNSS operations for IoT NTN | Spreadtrum Communications |
| R1-2203391 | Improved GNSS operations for IoT NTN | MediaTek Inc. |
| R1-2203759 | GNSS operation issues for IoT NTN | CATT |
| R1-2203806 | Discussion on improved GNSS operation for IoT NTN | xiaomi |
| R1-2203841 | Enhancements for long connections in NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2203931 | Improved GNSS operations for IoT NTN | Samsung |
| R1-2203933 | Improved GNSS operations for IoT NTN | Nordic Semiconductor ASA |
| R1-2204013 | Discussion on improved GNSS operations for IoT NTN | OPPO |
| R1-2204269 | On improved GNSS operations for IoT NTN | Apple |
| R1-2204330 | Discussion on improved GNSS operations for IoT NTN | CMCC |
| R1-2204517 | Improved GNSS operations for IoT NTN | Lenovo |
| R1-2204827 | On improved GNSS operation for IoT NTN | Ericsson Telecomunicazioni SpA |
| R1-2205060 | Improved GNSS Operations for IoT-NTN | Qualcomm Incorporated |
| R1-2205203 | Feature lead summary#1 of AI 9.12.3 on improved GNSS operations | Moderator (MediaTek) |
| R1-2205553 | Feature lead summary#2 of AI 9.12.3 on improved GNSS operations | Moderator (MediaTek) |
| 9.12.4 | Other | |
| R1-2203243 | Discussion on other issues for Rel-18 NTN | ZTE |
| R1-2203589 | Other issues for NR NTN enhancements | vivo |
| R1-2203760 | Others issues for NR NTN | CATT |
| R1-2203845 | Other aspects related to NTN operation for Rel-18 | Nokia, Nokia Shanghai Bell |
| R1-2203932 | On TA control enhancement for NTN | Samsung |
| R1-2203938 | Discussions on NR and IoT NTN | NEC |
| R1-2204672 | On other aspects of NTN enhancements | Ericsson |
| R1-2204915 | Further simulation results on coverage enhancement | Huawei, HiSilicon |
| 9.18 | Other | |
| R1-2204096 | Discussion | FUTUREWEI |