| 2 | Approval of Agenda | |
|---|---|---|
| R1-2106400 | Draft Agenda of RAN1#106-e meeting | RAN1 Chair |
| R1-2106403 | RAN1#106-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2106404 | Additional Guidelines for RAN1#106-e-Meeting Management | RAN1 Chair |
| R1-2108195 | Draft Agenda of RAN1#106-e meeting | RAN1 Chair |
| 3 | Highlights from RAN plenary | |
| R1-2106401 | Highlights from RAN#92-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2106402 | Report of RAN1#105-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2106405 | Reply LS to RAN1 on physical layer aspects of small data transmission | RAN2, vivo |
| R1-2106406 | LS on resource reselection trigger sl-reselectAfter | RAN2, Apple |
| R1-2106407 | LS response on two PUCCH capability | RAN2, OPPO |
| R1-2106408 | Reply LS on G-RNTI and G-CS-RNTI for MBS | RAN2, CMCC |
| R1-2106409 | Reply LS on overlapped data and SR with equal L1 priority | RAN2, Samsung |
| R1-2106410 | LS on update for MCCH design | RAN2, Huawei |
| R1-2106411 | LS to RAN1 on UL positioning in RRC_INACTIVE | RAN2, Intel |
| R1-2106412 | LS to RAN1 on parameters for on-demand PRS | RAN2, Intel |
| R1-2106413 | LS on time gap information in SCI | RAN2, OPPO |
| R1-2106414 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN2, Samsung |
| R1-2106415 | Reply LS on PDB for new 5QI | RAN2, Ericsson |
| R1-2106416 | Reply LS on Time Synchronization assistance parameters | RAN2, Nokia |
| R1-2106417 | LS on On-demand PRS | RAN2, Ericsson |
| R1-2106418 | Reply LS to RAN1 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN3, Samsung |
| R1-2106419 | LS on IAB resource multiplexing | RAN3, Huawei |
| R1-2106420 | LS on Inter-donor migration | RAN3, Samsung |
| R1-2106421 | Response LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN3, ZTE |
| R1-2106422 | Reply LS on Rel-17 uplink Tx switching | RAN4, China Telecom |
| R1-2106423 | Reply LS on PUCCH and PUSCH repetition | RAN4, Qualcomm |
| R1-2106424 | LS on maximum UE EIRP and conducted power | RAN4, Intel |
| R1-2106425 | LS on 60 GHz Time-related issues | RAN4, Apple |
| R1-2106426 | Reply LS on L1/L2 centric inter-cell mobility | RAN4, Samsung |
| R1-2106427 | Reply LS on temporary RS for efficient SCell activation in NR CA | RAN4, Huawei |
| R1-2106428 | Response LS on NTN UL frequency synchronization requirements | RAN4, CATT |
| R1-2106429 | Reply LS on timing assumption for inter-cell DL measurement | RAN4, Samsung |
| R1-2106430 | LS on synchronous operation between Uu and SL in TDD band n79 | RAN4, CATT |
| R1-2106431 | LS on UL MIMO coherence for Tx switching between two carriers | RAN4, China Telecom |
| R1-2106432 | LS on RAN4 recommendation for the 52.6 - 71 GHz frequency range designation | RAN4, Huawei |
| R1-2106433 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2106434 | Reply LS on the intra-band and inter-band (NG)EN-DC or NE-DC Capabilities | RAN4, ZTE Corporation |
| R1-2106435 | LS on determination of location estimates in local co-ordinates | SA2, Ericsson |
| R1-2106436 | Response LS on Scheduling Location in Advance to reduce Latency | SA2, CATT |
| R1-2106437 | LS on 5 GHz channel access mechanism | ETSI TC BRAN |
| R1-2106727 | Discussion on the Intra-band and Inter-band (NG)EN-DC NE-DC Capabilities | ZTE |
| R1-2106728 | [DRAFT] Reply LS on the Intra-band and Inter-band (NG)EN-DC NE-DC Capabilities | ZTE |
| R1-2106777 | Draft Reply LS to RAN2 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | ZTE |
| R1-2106778 | Draft Reply LS to RAN3 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | ZTE |
| R1-2106779 | Draft Reply LS to RAN4 LS on L1/L2-Centric Inter-Cell Mobility | ZTE |
| R1-2106780 | Draft Reply LS to RAN2 on parameters for on-demand PRS | ZTE |
| R1-2106786 | Discussion on RAN4 LS on UL MIMO coherence for Tx switching between two carriers | ZTE |
| R1-2106787 | [DRAFT] Reply LS on PUCCH and PUSCH repetition | ZTE |
| R1-2106849 | Draft reply LS on resource reselection trigger sl-reselectAfter | Samsung |
| R1-2106850 | Draft reply LS on time gap information in SCI | Samsung |
| R1-2106851 | Draft reply LS on synchronous operation between Uu and SL in TDD band n79 | Samsung |
| R1-2106852 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN2 | Samsung |
| R1-2106853 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | Samsung |
| R1-2106854 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN4 | Samsung |
| R1-2106922 | Discussion on LS from RAN2 on SL DRX design | CATT, GOHIGH |
| R1-2106923 | Discussion on LS from RAN2 on time gap information in SCI | CATT, GOHIGH |
| R1-2106924 | Draft Reply LS on on physical layer aspects of small data transmission | CATT |
| R1-2106995 | Draft Reply LS on resource reselection trigger sl-reselectAfter | CATT, GOHIGH |
| R1-2107070 | [DRAFT] Reply LS to RAN2 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Lenovo, Motorola Mobility |
| R1-2107071 | [DRAFT] Reply LS to RAN2 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Lenovo, Motorola Mobility |
| R1-2107072 | [DRAFT] Reply LS to RAN4 LS on L1/L2-Centric Inter-Cell Mobility | Lenovo, Motorola Mobility |
| R1-2107177 | Draft Reply LS to RAN2 on UL positioning in RRC_INACTIVE | ZTE |
| R1-2107219 | Discussion on LS to RAN1 on parameters for on-demand PRS | OPPO |
| R1-2107222 | Draft reply LS on resource reselection trigger sl-reselectAfter | OPPO |
| R1-2107226 | Discussion on time gap information in SCI | OPPO |
| R1-2107227 | Draft reply LS on time gap information in SCI | OPPO |
| R1-2107228 | Draft reply LS on synchronous operation between Uu and SL in TDD band | OPPO |
| R1-2107283 | Discussion on LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | OPPO |
| R1-2107284 | Discussion on Reply LS to RAN1 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | OPPO |
| R1-2107285 | Discussion on Reply LS on L1/L2 centric inter-cell mobility | OPPO |
| R1-2107304 | Draft Reply to RAN2 LS on time gap information in SCI | Qualcomm Incorporated |
| R1-2107305 | Draft Reply to RAN2 LS on resource reselection trigger sl-reselectAfter | Qualcomm Incorporated |
| R1-2107306 | Draft Reply to RAN4 LS on synchronous operation between Uu and SL in TDD band | Qualcomm Incorporated |
| R1-2107307 | Discussion of RAN4 LS on UL MIMO coherence for Tx switching between two carriers | Qualcomm Incorporated |
| R1-2107387 | Discussion on RAN2 LS on update for MCCH design | CMCC |
| R1-2107513 | Discussion on RAN2 LS on broadcast session delivery about MCCH design | MediaTek Inc. |
| R1-2107530 | Discussion on LS on resource reselection trigger sl-reselectAfter | LG Electronics |
| R1-2107531 | Discussion on LS on synchronous operation between Uu and SL in TDD band n79 | LG Electronics |
| R1-2107532 | Discussion on LS on time gap information in SCI | LG Electronics |
| R1-2107547 | Draft Reply LS on PUCCH and PUSCH repetition | LG Electronics |
| R1-2107565 | Discussion on RAN2 LS on resource reselection trigger sl-reselectAfter | Intel Corporation |
| R1-2107632 | Discussion of SA4 input on XR traffic | Ericsson |
| R1-2107696 | Draft Reply LS on TCI update for Inter-cell Mobility [RAN2] | Apple |
| R1-2107697 | Draft Reply LS on TCI update for Inter-cell Mobility [RAN3] | Apple |
| R1-2107698 | Draft Reply LS on TCI update for Inter-cell Mobility [RAN4] | Apple |
| R1-2107699 | Draft Reply LS on Resource Reselection Trigger sl-reselectAfter | Apple |
| R1-2107700 | Draft Reply LS on Time Gap Information in SCI | Apple |
| R1-2107701 | Draft Reply LS on Synchronous Operation between Uu and SL in TDD Band | Apple |
| R1-2107702 | Discussion on RAN2 LS on Resource Reselection | Apple |
| R1-2107703 | Discussion on RAN2 LS on Time Gap Information | Apple |
| R1-2107704 | Discussion on RAN4 LS on Sidelink Timing | Apple |
| R1-2107705 | Discussion on RAN2 LS on Sidelink DRX | Apple |
| R1-2107706 | Discussion on RAN2 LS on TA Pre-compensation | Apple |
| R1-2107813 | Draft Reply LS to RAN2 on LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | LG Electronics |
| R1-2107827 | About reply LS on inter-donor migration in IAB | ZTE, Sanechips |
| R1-2107891 | [Draft] Reply LS on time gap information in SCI | Xiaomi |
| R1-2107892 | [Draft] Reply LS on synchronous operation between Uu and SL in TDD band | Xiaomi |
| R1-2107954 | Draft Reply LS on R16 V2X for PUCCH reporting and for minimum time gap | vivo |
| R1-2107955 | Draft reply LS on resource reselection trigger sl-reselectAfter | vivo |
| R1-2107956 | Draft reply LS on synchronous operation between Uu and SL in TDD band | vivo |
| R1-2107957 | Draft reply LS on time gap information in SCI | vivo |
| R1-2107958 | Draft Reply LS on SL DRX design | vivo |
| R1-2107959 | Discussion on RAN4 Reply LS on PUCCH and PUSCH repetition | vivo |
| R1-2107960 | Discussion on LS on UL MIMO coherence for Tx switching between two carriers | vivo |
| R1-2107961 | Draft reply LS on UL MIMO coherence for Tx switching between two carriers | vivo |
| R1-2107962 | Draft CR on UL MIMO coherence for Tx switching between two carriers | vivo |
| R1-2107963 | Draft Reply LS on RAN2 LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | vivo |
| R1-2107964 | Draft Reply LS on RAN3 Reply LS to RAN1 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | vivo |
| R1-2107965 | Draft Reply LS on RAN4 Reply to RAN1 LS on L1/L2-Centric Inter-Cell Mobility | vivo |
| R1-2107966 | Draft reply LS on determination of location estimates in local co-ordinates | vivo |
| R1-2107967 | Draft reply LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities | vivo |
| R1-2107968 | Draft reply LS on IAB resource multiplexing | vivo |
| R1-2107969 | Draft reply LS on Inter-donor migration | vivo |
| R1-2108059 | Discussion on synchronous operation between Uu and SL in TDD band | OPPO |
| R1-2108062 | On DU resource configuration in case of inter-donor migration | Huawei, HiSilicon |
| R1-2108063 | Views on RAN2 reply LS for L1/L2 mobility | Huawei, HiSilicon |
| R1-2108064 | Views on RAN3 reply LS for L1/L2 mobility | Huawei, HiSilicon |
| R1-2108065 | Views on RAN4 reply LS for L1/L2 mobility | Huawei, HiSilicon |
| R1-2108066 | Draft reply LS on MCCH change notification | Huawei, HiSilicon |
| R1-2108067 | Discussion on MCCH change notification | Huawei, HiSilicon |
| R1-2108068 | Discussion on determination of location estimates in local co-ordinates | Huawei, HiSilicon |
| R1-2108069 | On inter-donor resource multiplexing for IAB | Huawei, HiSilicon |
| R1-2108075 | Discussion on RAN4 LS on synchronous operation between Uu and SL in TDD band n79 | ZTE, Sanechips |
| R1-2108076 | Discussion on RAN2 LS on time gap information in SCI | ZTE, Sanechips |
| R1-2108077 | Discussion on RAN2 LS on resource reselection trigger sl-reselectAfter | ZTE, Sanechips |
| R1-2108078 | Further consideration of SL DRX | ZTE, Sanechips |
| R1-2108079 | [draft]Reply LS on sidelink DRX | ZTE, Sanechips |
| R1-2108110 | Discussion on IAB resource multiplexing | Ericsson |
| R1-2108111 | Discussion on inter-donor migration in eIAB | Ericsson |
| R1-2108125 | Discussion on RAN4 LS on synchronous operation between Uu and SL | Nokia, Nokia Shanghai Bell |
| R1-2108126 | [Draft] Reply LS on PUCCH reporting and minimum time gap for V2X | Ericsson |
| R1-2108127 | [Draft] Reply LS on resource reselection trigger sl-reselectAfter | Ericsson |
| R1-2108128 | [Draft] Reply LS on SL DRX design | Ericsson |
| R1-2108129 | [Draft] Reply LS on synchronous operation between Uu and SL in TDD band | Ericsson |
| R1-2108130 | [Draft] Reply LS on time gap information in SCI | Ericsson |
| R1-2108131 | Discussion on RAN2 LS on PUCCH reporting and for minimum time gap for V2X | Ericsson |
| R1-2108132 | Discussion on RAN2 LS on resource reselection trigger sl-reselectAfter | Ericsson |
| R1-2108133 | Discussion on RAN2 LS on SL DRX design | Ericsson |
| R1-2108134 | Discussion on RAN4 LS on synchronous operation between Uu and SL in TDD band | Ericsson |
| R1-2108135 | Discussion on RAN2 LS on time gap information in SCI | Ericsson |
| R1-2108177 | Discussion Reply on PUCCH and PUSCH Repetition | Ericsson |
| R1-2108178 | [Draft] Reply LS on SL DRX design | Nokia, Nokia Shanghai Bell |
| R1-2108179 | Discussion on RAN2 LS on DRX impact | Nokia, Nokia Shanghai Bell |
| R1-2108180 | Discussion of RAN2 LS on resource reselection trigger sl-reselectAfter | Nokia, Nokia Shanghai Bell |
| R1-2108181 | Discussion of RAN2 LS on time gap information in SCI | Nokia, Nokia Shanghai Bell |
| R1-2108182 | Discussion on LS on Status Update on XR Traffic | Huawei, HiSilicon |
| R1-2108183 | Discussion on RAN2 LS on resource reselection trigger sl-reselectAfter | Huawei, HiSilicon |
| R1-2108185 | Discussion on RAN2 LS on time gap information in SCI | Huawei, HiSilicon |
| R1-2108186 | Discussion on RAN2 LS on DRX impact | Huawei, HiSilicon |
| R1-2108187 | Discussion on RAN4 LS on synchronous operation between Uu and SL in TDD band | Huawei, HiSilicon |
| R1-2108191 | Discussion on UL positioning in RRC_INACTIVE | Huawei, HiSilicon |
| R1-2108192 | Discussion on parameters for on-demand PRS | Huawei, HiSilicon |
| R1-2108193 | Draft reply LS on PUCCH and PUSCH repetition | Huawei, HiSilicon |
| R1-2108197 | Discussion on LS on resource reselection trigger sl-reselectAfter | LG Electronics, Hyundai Motors |
| R1-2108257 | RAN1#106-e preparation phase on LSs | RAN1 Chair |
| R1-2108330 | Discussion on RAN2 LS on resource reselection trigger sl-reselectAfter | ZTE, Sanechips |
| R1-2108378 | Reply LS on the Intra-band and Inter-band (NG)EN-DC NE-DC Capabilities | RAN1, ZTE |
| R1-2108391 | Summary of Email Discussion [106-e-NR-AI5-LSs-01] | Moderator (ZTE) |
| R1-2108484 | LS to RAN1 on UL skipping with LCH-based prioritization | RAN2, vivo |
| R1-2108543 | Reply LS on granularity of response time | RAN2, Huawei |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2106500 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| R1-2106729 | Discussion on Rel-17 UL Tx Switching | ZTE |
| R1-2106925 | Discussion on R17 enhancements for UL TX switching | CATT |
| R1-2107122 | Discussion on Rel-17 uplink Tx switching | China Telecom |
| R1-2107211 | Discussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2107308 | Discussion on R17 UL Tx switching | Qualcomm Incorporated |
| R1-2107388 | Discussion on Rel-17 UL Tx Switching | CMCC |
| R1-2107970 | Discussion on Rel-17 Tx switching enhancements | vivo |
| R1-2108643 | [106-e-NR-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| 5.2 | RAN1 Aspects for NR small data transmissions in INACTIVE state | |
| R1-2106458 | Physical layer aspects of CG-SDT | Huawei, HiSilicon |
| R1-2106683 | Discussion on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2106765 | Physical layer aspects for NR small data transmissions in INACTIVE state | Ericsson |
| R1-2106788 | Physical layer aspects of small data transmission | Sony |
| R1-2106855 | Discussion on physical layer aspects for NR small data transmissions in INACTIVE state | Samsung |
| R1-2106926 | Discussion on remaining issues on small data transmission | CATT |
| R1-2107007 | Discussion on the remaining physical layer issues of small data transmission | ZTE, Sanechips |
| R1-2107075 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2107139 | Discussion on RAN1 Aspects for NR small data transmissions | NEC |
| R1-2107309 | Draft Reply to RAN2 LS on Physical Layer Aspects of SDT | Qualcomm Incorporated |
| R1-2107433 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2107566 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2107707 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2107971 | Discussion on RAN1 impacts for small data transmission | vivo |
| R1-2107972 | Draft reply LS on physical layer aspects of small data transmission | vivo |
| R1-2108089 | On physical layer aspects of small data transmission | Nokia, Nokia Shanghai Bell |
| R1-2108531 | Draft Reply LS on physical layer aspects of small data transmission | Moderator (vivo) |
| R1-2108532 | Summary of Email discussion on [106-e-NR-R17-SDT-02] Reply LS to R1-2106405 | Moderator (vivo) |
| R1-2108533 | Reply LS on on physical layer aspects of small data transmission | RAN1, vivo |
| R1-2108561 | Summary on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2108562 | Draft LS on the TA validation and mapping details for CG-SDT | Moderator (ZTE) |
| R1-2108649 | LS on the TA validation and mapping details for CG-SDT | RAN1, ZTE |
| 6 | E-UTRA Maintenance | |
| R1-2106561 | Discussion on NPUSCH postponement when overlapping with NPRACH | Huawei, HiSilicon |
| R1-2106839 | Draft Rel-14 CR on Clarification on NPUSCH postponement for NB-IoT | ZTE, Sanechips |
| R1-2106840 | Draft Rel-15 CR on Clarification on NPUSCH postponement for NB-IoT | ZTE, Sanechips |
| R1-2107686 | NPUSCH postponement for NB-IoT | Huawei, HiSilicon |
| R1-2107688 | Correction on cyclic shift for eMTC PUR | Huawei, HiSilicon |
| R1-2108119 | Clarification on NPUSCH postponement when the NPRACH resource is implicitly indicated | Ericsson |
| R1-2108120 | Deployment Mode Indicator for anchor and non-anchor carriers | Ericsson |
| R1-2108194 | Discussion on distinguishing between PUR and SPS PUSCH for eMTC | Huawei, HiSilicon |
| R1-2108246 | RAN1#106-e preparation phase initial summary on Rel 8-16 CRs | Ad-hoc chair (CMCC) |
| R1-2108247 | RAN1#106-e preparation phase final summary on Rel 8-16 CRs | Ad-hoc chair (CMCC) |
| R1-2108535 | Correction on PUSCH cyclic shift for eMTC PUR | Moderator (Huawei), HiSilicon |
| R1-2108536 | Correction on PUSCH cyclic shift for eMTC PUR | Moderator (Huawei), Huawei, HiSilicon, Ericsson, ZTE, Sanechips, Lenovo, Motorola Mobility |
| R1-2108537 | Summary of [106-e-LTE-6CRs-01] | Moderator (ZTE) |
| R1-2108538 | Summary of [106-e-LTE-6CRs-02] | Moderator (Huawei) |
| R1-2108539 | Summary of [106-e-LTE-6CRs-03] | Moderator (Ericsson) |
| R1-2108540 | Summary of [106-e-LTE-6CRs-04] | Moderator (Huawei) |
| R1-2108581 | Clarification on NPUSCH postponement for NB-IoT in Rel-15 | Moderator (ZTE), Sanechips, Ericsson, Lenovo, Motorola Mobility, Huawei |
| R1-2108582 | Clarification on NPUSCH postponement for NB-IoT | Moderator (ZTE), Sanechips, Ericsson, Lenovo, Motorola Mobility, Huawei |
| R1-2108597 | Session notes for 6 (Maintenance of E-UTRA Releases 8-16) | Ad-Hoc Chair (CMCC) |
| R1-2108651 | Clarification on the deployment mode indicator for NB-IoT | Moderator (Ericsson), Ericsson |
| R1-2108652 | Clarification on the deployment mode indicator for NB-IoT | Moderator (Ericsson), Ericsson |
| R1-2108658 | Correction on PUSCH cyclic shift for eMTC PUR | Moderator (Huawei), Huawei, HiSilicon, Ericsson, ZTE, Sanechips, Lenovo, Motorola Mobility |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2106474 | Clarification on back-to-back PUSCHs scheduling restriction | Huawei, HiSilicon |
| R1-2106516 | Correction on prioritization rules of SRS carrier switching | Huawei, HiSilicon |
| R1-2106517 | Correction on data and control multiplexing | Huawei, HiSilicon |
| R1-2106533 | Discussion on SRS carrier switching | ZTE |
| R1-2106534 | Draft CR on SRS carrier switching | ZTE |
| R1-2106535 | Draft CR on the number of layers to determine TBS | ZTE |
| R1-2106536 | Discussion on accumulated closed loop power control for BWP switching | ZTE |
| R1-2106537 | Draft CR on accumulated closed loop power control for BWP switching | ZTE |
| R1-2106684 | PDSCH processing time per Capability 2 and DCI format 1_0 | Spreadtrum Communications |
| R1-2106726 | Discussion on Configuration of First Active BWP | ZTE |
| R1-2106773 | Correction of physical-layer model of BCH transmission | Ericsson |
| R1-2106774 | Correction of physical-layer model of BCH transmission | Ericsson |
| R1-2106856 | Discussion on counting PDCCH candidates in overbooking procedure | Samsung |
| R1-2106857 | Correction on counting PDCCH candidates in overbooking procedure | Samsung |
| R1-2106927 | Discussion on overlapping between positive SR and PUSCH without UL-SCH | CATT |
| R1-2106928 | Discussion on cancellation of semi-static transmission due to dynamic transmission | CATT |
| R1-2107008 | On the PDCCH monitoring behavior during SCell activation | ZTE, Sanechips |
| R1-2107159 | TP for editor’s CR on Precoding information and number of layers, and Antenna port(s) configuration table | NEC |
| R1-2107299 | TP for editor’s CR | NEC |
| R1-2107310 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | Qualcomm Incorporated |
| R1-2107311 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2107312 | Draft CR on Rel-16 Type-1 HARQ-ACK codebook construction | Qualcomm Incorporated |
| R1-2107313 | Clarification on back-to-back PUSCHs scheduling restriction | Qualcomm Incorporated |
| R1-2107314 | Clarification on coefficient reporting order in Type II CSI | Qualcomm Incorporated |
| R1-2107389 | Draft CR on PDCCH DMRS scrambling sequence | CMCC, ZTE |
| R1-2107503 | Draft 38.213 CR on PUSCH/PUCCH power control adjustment state during UL BWP change | MediaTek Inc. |
| R1-2107504 | On two DCIs in the same slot for BWP switch | MediaTek Inc. |
| R1-2107505 | On PUSCH scheduling restriction | MediaTek Inc. |
| R1-2107506 | Clarification on Multiplexing HARQ-ACK Information in PUSCH without PUCCH | MediaTek Inc. |
| R1-2107507 | Clarification on PUSCH with UCI only and DMRS multiplexing | MediaTek Inc. |
| R1-2107525 | Correction to cell-specific PUCCH resource configuration with pucch-ResourceCommon | Nokia, Nokia Shanghai Bell |
| R1-2107567 | Discussion on SRS carrier switching | Intel Corporation |
| R1-2107568 | On UE processing capability #2 and PDSCH scheduled by DCI 1_0 | Intel Corporation |
| R1-2107626 | draftCR on PUCCH maxCodeRate in TS 38.213 (Rel-15) | Ericsson |
| R1-2107627 | draftCR on PUCCH maxCodeRate in TS 38.213 (Rel-16) | Ericsson |
| R1-2107672 | Discussion on the UCI multiplexing without PUCCH | Huawei, HiSilicon |
| R1-2107677 | Processing time for PDSCH scheduled by DCI format 1_0 | Huawei, HiSilicon |
| R1-2107683 | Correction to PDSCH rate matching for SPS | Huawei, HiSilicon |
| R1-2107708 | Draft CR on PT-RS threshold report (CatF) | Apple |
| R1-2107709 | Draft CR on PT-RS threshold report (CatA) | Apple |
| R1-2107710 | Timeline Considerations for SRS Carrier Switching and Dropping Procedure in Rel-16 | Apple |
| R1-2107711 | Discussions on PUSCH UCI Multiplexing without HARQ-ACK PUCCH in Rel-15 and Rel-16 | Apple |
| R1-2107835 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH overlapping | NTT DOCOMO, INC. |
| R1-2107836 | Discussion on PUSCH without UL-SCH and with FDM indication | NTT DOCOMO, INC. |
| R1-2107973 | Discussion on CSI-RS multiplexing with PDSCH scheduled by PDCCH with CRC scrambled by P-RNTI and SI-RNTI | vivo |
| R1-2107974 | Draft CR on PUCCH power control for Rel-15 | vivo |
| R1-2107975 | Discussion on SRS carrier switching | vivo |
| R1-2107995 | Capability 2 and fallback DCI format 1-0 PDSCH handling | Ericsson |
| R1-2108320 | Summary of [106-e-NR-7.1CRs-02] Issue#2: Correction on prioritization rules of SRS carrier switching | Moderator (Huawei) |
| R1-2108335 | Correction to PDSCH rate matching for SPS | Huawei, HiSilicon |
| R1-2108365 | Summary of [106-e-NR-7.1CRs-10] Correction on counting PDCCH candidates in overbooking procedure | Moderator (Samsung) |
| R1-2108388 | Summary on [106-e-NR-7.1CRs-12] | Moderator (Samsung) |
| R1-2108403 | Summary of [106-e-NR-7.1CRs-05] | Moderator (CATT) |
| R1-2108412 | Summary on [106-e-NR-7.1CRs-11] | Moderator (NEC) |
| R1-2108413 | Summary of [106-e-NR-7.1CRs-06] on the PDCCH monitoring behavior during SCell activation | Moderator (ZTE) |
| R1-2108414 | Email Discussion Summary of [106-e-NR-7.1CRs-03] | Moderator (ZTE) |
| R1-2108489 | CR to 38.214 clarification on coefficients packing order for Type II CSI | Moderator (Qualcomm Incorporated) |
| R1-2108490 | CR to 38.214 clarification on coefficients packing order for Type II CSI | Moderator (Qualcomm Incorporated) |
| R1-2108491 | Summary of [106-e-NR-7.1CRs-08] | Moderator (Qualcomm Incorporated) |
| R1-2108565 | Summary of [106-e-NR-7.1CRs-01] Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek Inc.) |
| R1-2108566 | Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek), Apple, CATT |
| R1-2108567 | Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek), Apple, CATT |
| R1-2108573 | Summary of discussion on PDSCH processing time per Capability 2 and DCI format 1_0 | Moderator (Intel) |
| R1-2108591 | Rel-15 editorial corrections for TS 38.212 | Huawei |
| R1-2108592 | Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) | Huawei |
| R1-2108647 | Summary for [106-e-NR-7.1CRs-07] Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | Moderator(Apple) |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2108593 | Alignment of notation | Ericsson |
| R1-2108594 | Alignment CR for TS 38.212 | Huawei |
| R1-2108595 | Editorial corrections for TS 38.213 | Samsung |
| R1-2108596 | Rel-16 editorial corrections for TS 38.214 | Nokia, Nokia Shanghai Bell |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2107009 | Editorial correction on the DMRS port of MsgA PUSCH | ZTE, Sanechips |
| R1-2107261 | Draft CR on spatial domain transmission filter for PUCCH | OPPO |
| R1-2108214 | FL summary on the maintenance of 2-step RACH | Moderator (ZTE) |
| R1-2108342 | Summary of the e-mail discussion [106-e-NR_2step_RACH-Core-01] on spatial filter for PUCCH before RRC connection in 2-step RACH | Moderator (OPPO) |
| R1-2108598 | Session notes for 7.2.1 (Maintenance of Two step RACH for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2106441 | Changes of channel access procedure in TS 37.213 | Huawei, HiSilicon |
| R1-2106507 | Discussion on the impact of MIIT consultation to channel access procedure | Huawei, HiSilicon |
| R1-2106508 | Correction on RRC parameter name of HARQ-ACK codebook in TS37.213 | Huawei, HiSilicon |
| R1-2106509 | Correction on DFI flag in DCI format 0-1 in TS38.212 | Huawei, HiSilicon |
| R1-2106510 | Changes of channel access procedure according to MIIT regulation in TS 38.212 | Huawei, HiSilicon |
| R1-2106518 | Corrections on CG-UCI multiplexing in TS38.212 | Huawei, HiSilicon |
| R1-2107010 | Editorial correction on the channel access for type-2 random access | ZTE, Sanechips |
| R1-2107012 | Alignment CR on the parameter name of discovery burst window length | ZTE, Sanechips |
| R1-2107049 | Correction related to wideband operation | Ericsson |
| R1-2107232 | Draft CR on e-type 2 HARQ codebook | OPPO |
| R1-2107233 | Draft CR on HARQ-ACK for PUSCH | OPPO |
| R1-2107234 | Draft CR on PUCCH resource determination | OPPO |
| R1-2107235 | Draft CR on PDSCH-to-HARQ feedback timing indicator field values | OPPO |
| R1-2107236 | Draft CR on LBT bandwidth | OPPO |
| R1-2107484 | Correction related to search space set group switching | MediaTek Inc. |
| R1-2107695 | Correction on frequency hopping for multi-PUSCH scheduling with single DCI | Ericsson Inc. |
| R1-2107712 | Correction on Wideband Operation for NRU | Apple |
| R1-2107976 | Discussion on frequency hopping for multi-PUSCH scheduling | vivo |
| R1-2108049 | Correction on channel access type and CP extension indictaion | ASUSTeK |
| R1-2108051 | Correction on ChannelAccess-CPext field in RAR | ASUSTeK |
| R1-2108205 | Feature lead summary for NR-U wideband operations | Moderator (LG Electronics) |
| R1-2108216 | FL summary for NR-U configured grant | Moderator (vivo) |
| R1-2108218 | Feature lead summary for Maintenance of UL Signals and Channels | Moderator (Ericsson) |
| R1-2108219 | Feature lead summary#1 for HARQ enhancements | Moderator (Huawei) |
| R1-2108222 | Rel.16 NR-U maintenance preparation phase email discussions summary | Moderator (Qualcomm Incorporated) |
| R1-2108226 | FL summary for channel access procedures for NR-U | Moderator (Nokia) |
| R1-2108232 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2108379 | Email discussion summary for editorial CRs for Rel.16 NR-U | Moderator(Qualcomm) |
| R1-2108434 | FL Summary for [106-e-NR-NRU-01] Email discussion/approval on CORESET configuration for wideband operation | Moderator (Ericsson) |
| R1-2108435 | [DRAFT] LS to RAN2 on default value for rb-Offset | Moderator (Ericsson) |
| R1-2108436 | LS to RAN2 on default value for rb-Offset | RAN1, Ericsson |
| R1-2108600 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| R1-2108663 | Summary of Email discussion on [106-e-NR-NRU-02] | Moderator (vivo) |
| 7.2.4 | Maintenance for 5G V2X with NR sidelink | |
| R1-2106475 | Correction on PSFCH resource determination | Huawei, HiSilicon |
| R1-2106476 | Correction on Mode 2 resource reservation period | Huawei, HiSilicon |
| R1-2106506 | Correction on PT-RS and PSSCH RE mapping | Huawei, HiSilicon |
| R1-2106858 | Discussion on interpretation of frequency resource indication value for NR sidelink | Samsung |
| R1-2106859 | Draft CR on interpretation of frequency resource indication value for NR sidelink | Samsung |
| R1-2106860 | Draft CR on editorial changes for RRC parameters in TS 38.213 | Samsung |
| R1-2107027 | Maintenance for mode-1 resource allocation for NR sidelink | Fujitsu |
| R1-2107028 | Maintenance for physical layer procedures for NR sidelink | Fujitsu |
| R1-2107220 | Correct typos for TS 38.211 | OPPO |
| R1-2107221 | Correct a parameter name for PSSCH power control in TS 38.213 | OPPO |
| R1-2107315 | Draft CR on Reserved-bit Values | Qualcomm Incorporated |
| R1-2107316 | Draft CR on Overlapping Grants in Mode 1 | Qualcomm Incorporated |
| R1-2107317 | Draft CR on NR SL Transmission Prioritization with LTE SL Reception | Qualcomm Incorporated |
| R1-2107783 | Correction on TDD indication in PSBCH payload for supplementary uplink band | Sharp |
| R1-2107784 | Correction on frequency resources for PSFCH transmissions | Sharp |
| R1-2107785 | Correction on sidelink congestion control in resource allocation mode 2 | Sharp |
| R1-2107786 | Correction on identification of candidate resources in mode 2 sensing procedure | Sharp |
| R1-2107837 | Correction of SL HARQ-ACK reporting on UL for skipped DG | NTT DOCOMO, INC. |
| R1-2107977 | Correction on HARQ reporting for multiple pools with PSFCH | vivo |
| R1-2107978 | Clarification on HARQ reporting on PUCCH for an ‘incomplete’ PSFCH period | vivo |
| R1-2107979 | Clarification on PUCCH Power control when the number of SL HARQ-ACK bits larger than 11 | vivo |
| R1-2107980 | Clarification on UE behaviour in out of coverage case | vivo |
| R1-2107981 | Clarification on UE behaviour in case of HARQ RTT restriction violation | vivo |
| R1-2108080 | Corrections on sidelink reference signal scaling factors in TS38.211 | ZTE, Sanechips |
| R1-2108081 | Corrections on sidelink reference signal scaling factors in TS38.214 | ZTE, Sanechips |
| R1-2108082 | Editorial correction on the field description of DCI Format 3_0 | ZTE, Sanechips |
| R1-2108083 | Correction on logical slot index in sensing procedure in TS38.214 | ZTE, Sanechips |
| R1-2108084 | Correction on the first symbol and the number of symbols for SL transmissions | ZTE, Sanechips |
| R1-2108094 | Remaining issues on sidelink mode 2 | ASUSTeK |
| R1-2108112 | Discussion on Type-1 HARQ codebook regarding multiple resource pools | ASUSTeK |
| R1-2108113 | Miscellaneous correction for Rel-16 sidelink V2X | ASUSTeK |
| R1-2108139 | [Draft] Correction on prioritizations for LTE and NR sidelink transmission and reception | Ericsson |
| R1-2108140 | [Draft] Correction on synchronization procedure for sidelink transmission | Ericsson |
| R1-2108141 | [Draft] Correction on procedure for transmitting the physical sidelink shared channel | Ericsson |
| R1-2108190 | Correction on DCI format 3_0 references | Huawei, HiSilicon |
| R1-2108198 | Correction on frequency resources for PSSCH transmissions | Sharp |
| R1-2108276 | Summary for email discussion [106-e-NR-5G_V2X-01]. | Moderator (OPPO) |
| R1-2108344 | Summary of [106-e-NR-5G_V2X-10] on editorial changes for recommendation to the editors | Moderator (Sharp) |
| R1-2108352 | Correction of SL HARQ-ACK reporting on UL for skipped DG | Moderator (NTT DOCOMO, INC.) |
| R1-2108353 | Summary of [106-e-NR-5G_V2X-03] | Moderator (NTT DOCOMO, INC.) |
| R1-2108364 | Correction on procedure for transmitting the physical sidelink shared channel | Ericsson |
| R1-2108366 | [Draft] Clarification on SL power control and SL type-1 HARQ-ACK codebook in out of coverage case | Moderator (vivo), Huawei, HiSilicon, Ericsson, OPPO |
| R1-2108375 | Clarification on SL power control and SL type-1 HARQ-ACK codebook in out of coverage case | Moderator (vivo), Huawei, HiSilicon, Ericsson, OPPO |
| R1-2108376 | Correction on procedure for transmitting the physical sidelink shared channel | Ericsson |
| R1-2108392 | Summary of [106-e-NR-5G_V2X-09] | Moderator (Huawei) |
| R1-2108393 | LS to RAN2 on mode 2 resource reservation period | RAN1, Huawei |
| R1-2108400 | Parameter name correction for PSSCH power control | OPPO |
| R1-2108408 | Correction on synchronization procedure for sidelink transmission | Moderator (Ericsson), vivo, OPPO |
| R1-2108431 | Summary of [106-e-NR-5G_V2X-07] | Moderator (Ericsson) |
| R1-2108432 | Summary of [106-e-NR-5G_V2X-08] | Moderator (Ericsson) |
| R1-2108437 | Summary of [106-e-NR-5G_V2XX-11] Discussion on reply LS in R1-2106406 | Moderator (Apple) |
| R1-2108438 | Reply LS on Resource Reselection Trigger sl-reselectAfter | RAN1, Apple |
| R1-2108443 | CR on Simultaneous NR SL and LTE SL Operation | Moderator (Qualcomm), Apple, Ericsson, Huawei, HiSilicon, NEC, Nokia, Nokia Shanghai Bell, Samsung, vivo |
| R1-2108444 | Summary of [106-e-NR-5G_V2X-02] | Moderator (Qualcomm) |
| R1-2108445 | Clarification on PUCCH Power control | Moderator (vivo) , Huawei, HiSilicon, LG Electronics, Ericsson, NEC, NTT DOCOMO, INC. |
| R1-2108446 | Summary of [106-e-NR-5G_V2X-05] | Moderator (vivo) |
| R1-2108455 | Correction of SL HARQ-ACK reporting on UL for skipped DG | Moderator (NTT DOCOMO, INC.), Ericsson, Fujitsu, Huawei, HiSilicon, LG Electronics, Lenovo, Motorola Mobility |
| R1-2108496 | Correction on HARQ reporting for multiple pools with PSFCH | Moderator (vivo), Ericsson |
| R1-2108505 | Summary of [106-e-NR-5G_V2X-04] | Moderator (vivo) |
| R1-2108506 | Summary of [106-e-NR-5G_V2X-06] | Moderator (vivo) |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC | |
| R1-2106487 | Remaining issues on UL prioritization and UL skipping | Huawei, HiSilicon |
| R1-2106488 | CSI-PUCCH-ResourceList where SPS HARQ-ACK multiplexed | Huawei, HiSilicon |
| R1-2106489 | Correction on overlapping between SPS HARQ-ACK with HP and SPS HARQ-ACK with LP | Huawei, HiSilicon |
| R1-2106511 | Correction for PUSCH repetition Type B in 38.213 | Huawei, HiSilicon |
| R1-2106512 | Correction for PUSCH repetition Type B in 38.214 | Huawei, HiSilicon |
| R1-2106513 | Correction on UL cancellation time | Huawei, HiSilicon |
| R1-2106672 | UE PDSCH processing time for DCI format 1_2 | Ericsson |
| R1-2106673 | UE Procedures for UCI Multiplexing and Prioritization | Ericsson |
| R1-2106674 | Sub-slot Based HARQ-ACK Feedback for MAC CE Activation/deactivation | Ericsson |
| R1-2106675 | Intra-UE Multiplexing/Prioritization and UL Skipping | Ericsson |
| R1-2106676 | SPS Release and SPS PDSCH Receptions with Slot Aggregation | Ericsson |
| R1-2106677 | Multi-CSI-PUCCH-ResourceList with Multiplexed SPS HARQ-ACK | Ericsson |
| R1-2106730 | Draft CR on Type-2 HARQ-ACK codebook size calculation | ZTE |
| R1-2106731 | Remaining issues on intra-UE multiplexing in Rel-16 URLLC | ZTE |
| R1-2106732 | Discussion on PDSCH processing timeline for DCI format 1_2 | ZTE |
| R1-2106825 | [Draft CR] Correction on UE procedure for intra-UE prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2106826 | Draft CR] Clarification on Inter-sub-slot multiplexing of low-priority UCIs | Nokia, Nokia Shanghai Bell |
| R1-2106827 | [Draft CR] Handling of HARQ-ACK feedback for SPS release | Nokia, Nokia Shanghai Bell |
| R1-2106861 | Discussion on PUSCH skipping for URLLC | Samsung |
| R1-2106862 | Draft CR on SPS release with aggregation factor | Samsung |
| R1-2106930 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2106931 | Correction on MAC CE effective time for spatial setting for a PUCCH transmission | CATT |
| R1-2106932 | Correction on invalid symbol determination for PUSCH repetition Type B | CATT |
| R1-2107063 | Timing for slot-based and sub-slot-based HARQ-ACK Feedback | Ericsson Inc. |
| R1-2107263 | Draft CR on PUCCH spatial setting when subslotLength-ForPUCCH is provided | OPPO |
| R1-2107264 | Draft CR on collison handling for overlapping SPS PDSCHs with SPS release | OPPO |
| R1-2107265 | Draft CR on PDCCH monitoring capability | OPPO |
| R1-2107266 | Remaining issues on HARQ-ACK timing for sub-slot based HARQ-ACK feedback | OPPO |
| R1-2107267 | Draft CR on Type-1 HARQ-ACK codebook generation for SPS release and SPS PDSCH | OPPO |
| R1-2107268 | Discussion on Type-1 HARQ-ACK codebook generation for SPS release and SPS PDSCH | OPPO |
| R1-2107269 | Remaining issues on intra-UE prioritization or multiplexing | OPPO |
| R1-2107270 | Draft CR on scheduling and HARQ | OPPO |
| R1-2107271 | Discussion on scheduling and HARQ | OPPO |
| R1-2107318 | Remaining issues on PDCCH enhancements for URLLC | Qualcomm Incorporated |
| R1-2107319 | Remaining issues on eCG enhancements for URLLC | Qualcomm Incorporated |
| R1-2107434 | PHR issues related to URLLC/IIOT WI | LG Electronics |
| R1-2107555 | UCI enhancements maintenance: Conflict between the first PUCCH repetition and semi-static configuration in Rel-15/16 | Nokia, Nokia Shanghai Bell |
| R1-2107556 | Rel-16 URLLC/IIoT PUSCH skipping (with LCH and/or PHY prioritization configured) | Nokia, Nokia Shanghai Bell |
| R1-2107557 | Discussion on Nokia draft CRs on Rel-16 URLLC/IIoT Scheduling/HARQ and SPS enhancements | Nokia, Nokia Shanghai Bell |
| R1-2107680 | Remaining issues on Scheduling and HARQ | Huawei, HiSilicon |
| R1-2107681 | Correction for HARQ-ACK timing in Rel-16 | Huawei, HiSilicon |
| R1-2107713 | Discussions on HARQ-ACK timing for sub-slot-based HARQ-ACK feedback in Rel-16 | Apple |
| R1-2107714 | UCI multiplexing and PUSCH skipping design for eURLLC | Apple |
| R1-2107715 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple |
| R1-2107787 | Correction on RNTI in Table 6.1.2.1.1-1 for determining PUSCH time domain resource allocation for DCI format 0_0 | Sharp |
| R1-2107982 | Clarification on UE procedure for prioritization | vivo |
| R1-2107983 | Maintenance on SPS enhancements | vivo |
| R1-2107984 | Maintenance on intra-UE prioritization and multiplexing | vivo |
| R1-2107985 | Draft CR on PUCCH spatial relation update | vivo |
| R1-2107986 | Draft 38.214 CR on non-Codebook based UL transmission with DCI format 0_2 | vivo |
| R1-2108025 | Correction on SPS overlap with dynamic PDSCH in TS 38.214 | Lenovo, Motorola Mobility |
| R1-2108199 | Correction for PUSCH repetition Type B in 38.213 | Huawei, HiSilicon |
| R1-2108201 | Summary of preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2108374 | Correction on invalid symbol determination for PUSCH repetition Type B | CATT |
| R1-2108385 | Summary of email discussion [106-e-NR-L1enh-URLLC-13] on editorial spec changes for recommendation to the editor | Moderator (Huawei) |
| R1-2108395 | Summary for email discussion [106-e-NR-L1enh-URLLC-10] | Moderator (LG Electronics) |
| R1-2108396 | Summary for email discussion [106-e-NR-L1enh-URLLC-11] | Moderator (LG Electronics) |
| R1-2108404 | Summary of [106-e-NR-L1enh-URLLC-09] | Moderator (CATT) |
| R1-2108441 | Correction on overlapping between SPS HARQ-ACK with HP and SPS HARQ-ACK with LP | Moderator (Huawei), HiSilicon, Ericsson |
| R1-2108442 | Summary of [106-e-NR-L1enh-URLLC-07] | Moderator (Huawei) |
| R1-2108451 | Summary of [106-e-NR-L1enh-URLLC-08] Correction for PUSCH repetition Type B in 38.213 (38.214) | Moderator (Huawei) |
| R1-2108452 | Summary of email discussion [106-e-NR-L1enh-URLLC-02] Sub-slot Based HARQ-ACK Feedback for MAC CE Activation/deactivation | Moderator (Ericsson) |
| R1-2108453 | Corrections on Sub-slot Based HARQ-ACK Feedback for MAC CE Activation/deactivation | Moderator (Ericsson), CATT, vivo, Ericsson, Apple |
| R1-2108461 | Summary of [106-e-NR-L1enh-URLLC-05] Issue#9: Remaining issues on UL prioritization and UL skipping | Moderator (vivo) |
| R1-2108469 | Summary of [106-e-NR-L1enh-URLLC-01] Issue#3: Correction on SRS resource configuration | Moderator (Qualcomm) |
| R1-2108470 | Correction on SRS resource set configuration for DCI format 0_2 in TS 38.212 | Moderator (Qualcomm), Ericsson |
| R1-2108499 | Summary of email thread [106-e-NR-L1enh-URLLC-12] | Moderator (OPPO) |
| R1-2108534 | CR for SPS Release and SPS PDSCH Receptions with Slot Aggregation | Moderator (LG Electronics), Ericsson, vivo, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2108560 | Summary of [106-e-NR-L1enh-URLLC-04] | Moderator (Nokia) |
| R1-2108655 | Summary of [106-e-NR-L1enh-URLLC-06] Issue #10: UE Procedures for UCI Multiplexing and Prioritization | Moderator (Qualcomm) |
| R1-2108656 | Summary of [106-e-NR-L1enh-URLLC-14] Discussion on Two PUCCH Capability | Moderator (Qualcomm) |
| R1-2108657 | Reply LS on Two PUCCH Capability | RAN1, Qualcomm |
| R1-2108659 | Correction on overlapping between SPS HARQ-ACK with HP and SPS HARQ-ACK with LP | Moderator (Huawei), HiSilicon, Ericsson |
| R1-2108666 | Summary of email discussion [106-e-NR-L1enh-URLLC-03] on sub-slot-based HARQ-ACK timing in Rel-16 | Moderator (Apple) |
| R1-2108667 | Correction on HARQ-ACK timing | Moderator (Apple Inc.), Ericsson, CATT |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2106470 | Correction on QCL acquisition in TS 38.214 | Huawei, HiSilicon |
| R1-2106471 | Correction on DM-RS position in TS 38.211 | Huawei, HiSilicon |
| R1-2106538 | Clarification on default spatial setting of PUCCH with multiple slots | ZTE |
| R1-2106539 | Draft CR on number of received PDSCHs for multi-TRP transmission | ZTE |
| R1-2106863 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2106933 | Correction on MU-CSI enhancement | CATT |
| R1-2106934 | Correction on QCL-type set for aperiodic CSI-RS | CATT |
| R1-2107011 | Correction on the RRC parameter of ackNackFeedbackMode | ZTE, Sanechips |
| R1-2107202 | Draft CR for M-DCI based M-TRP transmission | OPPO |
| R1-2107320 | Draft CR on sum data rate for tdmSchemeA and fdmSchemeB | Qualcomm Incorporated |
| R1-2107716 | Draft CR on Action Time for Pathloss Reference Signal Update | Apple |
| R1-2107717 | Draft CR on SCell candidate beam detection | Apple |
| R1-2107987 | Discussion on spatial relation update across CCs for SRS | vivo |
| R1-2107988 | Draft CR on spatial relation update across CCs for SRS | vivo |
| R1-2107989 | Discussion on default QCL assumption of AP CSI-RS in MTRP operation when the triggering PDCCH and the CSI-RS have different numerologies | vivo |
| R1-2107990 | Draft CR on default QCL assumption of AP CSI-RS in MTRP operation when the triggering PDCCH and the CSI-RS have different numerologies | vivo |
| R1-2108345 | Summary of email discussions [106-e-NR-eMIMO-07] MT.4 (PDSCH repetition counting) | Moderator (Qualcomm) |
| R1-2108346 | CR on sum data rate for tdmSchemeA and fdmSchemeB | Moderator (Qualcomm) |
| R1-2108401 | CR on number of received PDSCHs for multi-TRP transmission | Moderator (ZTE) |
| R1-2108405 | Summary of [106-e-NR-eMIMO-06] Email Discussion | Moderator (OPPO) |
| R1-2108406 | Summary of [106-e-NR-eMIMO-05] MT.1 (candidate PDSCH for mDCI) | Moderator (ZTE) |
| R1-2108415 | Email Discussion Summary of [106-e-NR-eMIMO-02] | Moderator (ZTE) |
| R1-2108460 | Summary on editorial spec changes of [106-e-NR-eMIMO-01] | Moderator (CATT) |
| R1-2108464 | Summary of Email discussion [106-e-NR-eMIMO-03] | Moderator (Apple) |
| R1-2108465 | Outcome of Email discussion [106-e-NR-eMIMO-03] | Moderator (Apple) |
| R1-2108485 | Summary of [106-e-NR-eMIMO-04] | Moderator (vivo) |
| R1-2108486 | Summary of [106-e-NR-eMIMO-08] | Moderator (vivo) |
| 7.2.7 | Maintenance of UE Power Saving for NR | |
| R1-2106514 | Discussion on corrections of Scell dormancy for power saving | Huawei, HiSilicon |
| R1-2106515 | Corrections of Scell dormancy for power saving | Huawei, HiSilicon |
| R1-2108188 | Correction on cross-slot scheduling based power saving | Huawei, HiSilicon |
| R1-2108423 | Correction on cross-slot scheduling based power saving | Huawei, HiSilicon |
| R1-2108473 | Moderator summary of [106-e-NR_UE_Pow_Sav-01] | Moderator (Huawei, HiSilicon) |
| R1-2108599 | Session notes for 7.2.7 (Maintenance of UE Power Saving for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2106448 | Draft CR on terminology correction to cell for positioning | Huawei, HiSilicon |
| R1-2106503 | Discussion on clauses for positioning procedures in TS 38.214 | Huawei, HiSilicon |
| R1-2106504 | Draft CR on PRS antenna ports | Huawei, HiSilicon |
| R1-2106540 | Interpretation of expected RSTD and expected RSTD uncertainty | ZTE |
| R1-2106994 | Draft CR on PRS reception procedure in NR positioning | CATTI |
| R1-2107682 | Correction on clauses for positioning procedures in TS 38.214 | Huawei, HiSilicon |
| R1-2107991 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2108163 | Maintenance on Rel-16 NR positioning | Ericsson |
| R1-2108189 | Aligning PRS duration calculation with RAN4 | Huawei, HiSilicon |
| R1-2108283 | Summary of [106-e-NR-Pos-05] | Moderator (vivo) |
| R1-2108288 | Summary of the preparation phase for Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2108394 | Summary on email discussion [106-e-NR-Pos-04] for optional content in nr-DL-PRS-ReferenceInfo | Moderator (CATT) |
| R1-2108419 | Summary of email discussion for [106-e-NR-Pos-03] | Moderator (ZTE Corporation) |
| R1-2108420 | Summary of [106-e-NR-Pos-01] Replacement of cell terminology | Moderator (Huawei) |
| R1-2108421 | Summary of [106-e-NR-Pos-02] DL PRS antenna ports and editorial corrections for SRS | Moderator (Huawei) |
| R1-2108422 | Draft CR on terminology correction to cell for positioning | Moderator (Huawei), HiSilicon, vivo, ZTE |
| R1-2108456 | CR on terminology correction to cell for positioning | Moderator (Huawei), HiSilicon, vivo, ZTE |
| R1-2108467 | Draft CR on alignment with RAN4 on DL PRS processing | Moderator (vivo), vivo, Huawei, HiSilicon |
| R1-2108468 | CR on alignment with RAN4 on DL PRS processing | Moderator (vivo), vivo, Huawei, HiSilicon |
| R1-2108601 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2106505 | Corrections on HARQ-ACK for case 2 dormancy indication in 38.213 | Huawei, HiSilicon |
| R1-2106733 | Correction on cross-carrier scheduling and cross-carrier CSI-RS triggering | ZTE |
| R1-2107262 | Draft CR on PDSCH-to-HARQ feedback timing indicator field values | OPPO |
| R1-2107996 | Draft CR for correction of SCell Dormancy | Ericsson |
| R1-2108147 | Removal of power sharing for FR2-FR2 dual connectivity from Rel-16 | Nokia, Nokia Shanghai Bell |
| R1-2108313 | Moderator summary of MR DC-CA pre-meeting preparation phase | Moderator (Nokia) |
| R1-2108418 | Corrections on SCell dormancy indication | Huawei, OPPO, Ericsson, Intel |
| R1-2108447 | Correction on cross-carrier scheduling and cross-carrier CSI-RS triggering | Moderator (ZTE) |
| R1-2108448 | Summary of Email Discussion [106-e-NR-MRDC-CA-02] | Moderator (ZTE) |
| R1-2108474 | Moderator summary of [106-e-NR-MRDC-CA-03] | Moderator (HiSilicon) |
| R1-2108502 | Summary of [106-e-NR-MRDC-CA-01] on SCell dormancy | Moderator (Huawei) |
| R1-2108510 | Corrections on SCell dormancy indication | Huawei, OPPO, Ericsson, Intel |
| R1-2108602 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2106502 | Discussion on positioning UE features | Huawei, HiSilicon |
| R1-2107321 | Remaining issues on Rel-16 UE features | Qualcomm Incorporated |
| R1-2107997 | Update to NR-DC Power sharing UE capabilities | Ericsson |
| R1-2108196 | On Rel-16 UE Features | Nokia, Nokia Shanghai Bell |
| R1-2108203 | Summary on Rel-16 NR UE features related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2108424 | Summary on [106-e-NR-UEFeature-Positioning-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2108425 | Summary on [106-e-NR-UEFeature-MRDCCA-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2108426 | Updated RAN1 UE features list for Rel-16 NR after RAN1#106-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2108427 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#106-e | RAN1, AT&T, NTT DOCOMO |
| 7.2.12 | Other | |
| R1-2106501 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2106929 | Draft CR on Rel-16 CSI-RS resources for mobility | CATT |
| R1-2107136 | Summary of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2107322 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2108204 | Summary on Rel-16 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2108417 | [106-e-NR-Maintenance-Others-02] Summary of email discussion on remaining issues on Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2108472 | [106-e-NR-Maintenance-Others-01] | Moderator (vivo) |
| 8 | Release 17 | |
| R1-2108678 | Preliminary RAN1 UE features list for Rel-17 LTE | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2108679 | Preliminary RAN1 UE features list for Rel-17 NR | Moderators (AT&T, NTT DOCOMO, INC.) |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2108676 | Moderator summary of RRC parameters for Rel-17 NR_FeMIMO | Moderator (Samsung) |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2106463 | Enhancements on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2106541 | Enhancements on Multi-beam Operation | ZTE |
| R1-2106571 | Further discussion on multi beam enhancement | vivo |
| R1-2106640 | Remaining Details on Enhancements for Multi-beam Operation | InterDigital, Inc. |
| R1-2106666 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2106685 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2106789 | Further enhancement on multi-beam operation | Sony |
| R1-2106864 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2106865 | Multi-Beam Enhancements | Samsung |
| R1-2106935 | Discussions on enhancements on multi-beam operation | CATT |
| R1-2107029 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2107085 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2107143 | Discussion on multi-beam operation | NEC |
| R1-2107203 | Enhancements on Multi-beam Operation | OPPO |
| R1-2107297 | Discussion of enhancements on multi-beam operation | FGI, Asia Pacific Telecom |
| R1-2107323 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2107390 | Enhancements on multi-beam operation | CMCC |
| R1-2107464 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2107485 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2107570 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2107628 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2107689 | Enhancements on Multi-beam operations | AT&T |
| R1-2107718 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2107814 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2107838 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2107893 | Enhancements on multi-beam operation | Xiaomi |
| R1-2108019 | Enhancements on Multi-beam Operation | Convida Wireless |
| R1-2108052 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2108208 | Summary of offline discussion on unified TCI and inter-cell beam management | Moderator (Samsung) |
| R1-2108231 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2108309 | Moderator summary for LS replies to RAN2/3/4 on inter-cell beam management | Moderator (Samsung) |
| R1-2108325 | Moderator summary#2 for multi-beam enhancement: ROUND 1 | Moderator (Samsung) |
| R1-2108361 | Moderator summary#3 for multi-beam enhancement: ROUND 2 | Moderator (Samsung) |
| R1-2108399 | Moderator summary#4 for multi-beam enhancement: ROUND 3 | Moderator (Samsung) |
| R1-2108520 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN2 | Moderator (Samsung) |
| R1-2108521 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | Moderator (Samsung) |
| R1-2108522 | [Draft] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN4 | Moderator (Samsung) |
| R1-2108526 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN2 | RAN1, Samsung |
| R1-2108527 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | RAN1, Samsung |
| R1-2108528 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN4 | RAN1, Samsung |
| R1-2108557 | Moderator summary#5 for multi-beam enhancement: ROUND 4 | Moderator (Samsung) |
| R1-2108648 | Moderator summary#6 for multi-beam enhancement: ROUND 5 | Moderator (Samsung) |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2106464 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2106542 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2106572 | Further discussion on Multi-TRP for PDCCH, PUCCH and PUSCH enhancements | vivo |
| R1-2106641 | Discussion on Enhancements for PDCCH, PUCCH, and PUSCH | InterDigital, Inc. |
| R1-2106667 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2106686 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2106790 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2106866 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2106936 | Enhancements on multi-TRP/panel transmission for PDCCH, PUCCH and PUSCH | CATT |
| R1-2107030 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2107079 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2107144 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2107204 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2107293 | Discussion on enhancements on multi-TRP for uplink channels | FGI, Asia Pacific Telecom |
| R1-2107324 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2107391 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2107465 | On multi-TRP enhancements for PDCCH and PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2107486 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | MediaTek Inc. |
| R1-2107571 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2107719 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2107815 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2107839 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2107894 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | Xiaomi |
| R1-2108020 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Convida Wireless |
| R1-2108053 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2108072 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2108074 | On PDCCH, PUCCH and PUSCH enhancements for multi-TRP | Ericsson |
| R1-2108106 | Discussion on mTRP PXXCH | ASUSTeK |
| R1-2108254 | Summary #1 of email discussions [106-e-NR-feMIMO-03] for mTRP PDCCH enhancements | Moderator (Qualcomm Inc.) |
| R1-2108255 | Summary #2 of email discussions [106-e-NR-feMIMO-03] for mTRP PDCCH enhancements | Moderator (Qualcomm Inc.) |
| R1-2108256 | Summary #3 of email discussions [106-e-NR-feMIMO-03] for mTRP PDCCH enhancements | Moderator (Qualcomm Inc.) |
| R1-2108298 | Summary #1 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2108299 | Summary #2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2108300 | Summary #3 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2106465 | Enhancements on inter-cell multi-TRP operation in Rel-17 | Huawei, HiSilicon |
| R1-2106543 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2106573 | Further discussion on inter-cell MTRP operation | vivo |
| R1-2106642 | On M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2106668 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2106687 | Discussion on enhancements on Multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2106867 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2106937 | Enhancements on inter-cell operation for multi-TRP/panel | CATT |
| R1-2107026 | On Multi-TRP inter-cell operation | Ericsson |
| R1-2107080 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2107205 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2107325 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2107392 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2107572 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2107720 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2107816 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2107840 | Discussion on inter-cell multi-TRP operations | NTT DOCOMO, INC. |
| R1-2107895 | QCL/TCI-related enhancements on Inter-cell Multi-TRP | Xiaomi |
| R1-2108029 | Discussion on Multi-TRP inter-cell operation | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2108054 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2108337 | Feature lead summary#1 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2108457 | Feature lead summary#2 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2108571 | Feature lead summary#3 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2108633 | LS on Rel-17 inter-cell multi TRP | RAN1, vivo |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2106466 | Enhancements on beam management for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2106544 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2106574 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2106643 | Further Details on Beam Management Enhancements for Multi-TRP | InterDigital, Inc. |
| R1-2106669 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2106688 | Discussion on enhancements on beam management for Multi-TRP | Spreadtrum Communications |
| R1-2106791 | Enhancements on beam management for multi-TRP | Sony |
| R1-2106868 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2106938 | Enhancements on beam reporting and beam failure recovery for multi-TRP | CATT |
| R1-2107031 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2107081 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2107145 | Discussion on beam management for multi-TRP | NEC |
| R1-2107206 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2107298 | Discussion of enhancements on beam management for multi-TRP | FGI, Asia Pacific Telecom |
| R1-2107326 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2107393 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2107470 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2107487 | Enhancement on beam management for multi-TRP | MediaTek Inc. |
| R1-2107573 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2107690 | Beam Management Enhancements for multi-TRP | AT&T |
| R1-2107721 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2107817 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2107841 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2107896 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2108009 | Discussion on beam management for multi-TRP | ITRI |
| R1-2108021 | On Multi-TRP BFR | Convida Wireless |
| R1-2108030 | Discussion on beam management for multi-TRP | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2108044 | Enhancements on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2108045 | On beam management enhancements for multi-TRP | Ericsson |
| R1-2108055 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2108321 | Moderator summary #1 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2108322 | Moderator summary #2 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2108323 | Moderator summary #3 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2106467 | Enhancements on HST multi-TRP deployment in Rel-17 | Huawei, HiSilicon |
| R1-2106545 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2106575 | Further discussion and evaluation on HST-SFN schemes | vivo |
| R1-2106644 | M-TRP Operation for HST-SFN Deployment | InterDigital, Inc. |
| R1-2106689 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2106792 | Enhancement on HST-SFN deployment | Sony |
| R1-2106869 | Enhancements on HST-SFN | Samsung |
| R1-2106939 | Enhancements on HST-SFN deployment for Rel-17 | CATT |
| R1-2107082 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2107146 | Discussion on HST-SFN deployment | NEC |
| R1-2107178 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2107207 | Enhancements on HST-SFN deployment | OPPO |
| R1-2107327 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2107394 | Enhancements on HST-SFN deployment | CMCC |
| R1-2107488 | Enhancements on HST-SFN deployment | MediaTek Inc. |
| R1-2107574 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2107625 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2107722 | Views on Rel-17 HST enhancement | Apple |
| R1-2107818 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2107842 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2107897 | Enhancements on HST-SFN operation for multi-TRP PDCCH transmission | Xiaomi |
| R1-2108022 | On Enhancements for HST-SFN deployment | Convida Wireless |
| R1-2108056 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2108326 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2108407 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2108548 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2106468 | Enhancements on SRS in Rel-17 | Huawei, HiSilicon |
| R1-2106546 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2106576 | Further discussion on SRS enhancement | vivo |
| R1-2106645 | Remaining Issues on SRS Enhancements | InterDigital, Inc. |
| R1-2106670 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2106690 | Considerations on SRS enhancements | Spreadtrum Communications |
| R1-2106793 | Considerations on SRS flexibility, coverage and capacity | Sony |
| R1-2106870 | Enhancements on SRS | Samsung |
| R1-2106940 | Discussion on SRS enhancements for Rel-17 | CATT |
| R1-2107083 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2107147 | Discussion on SRS enhancement | NEC |
| R1-2107208 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2107328 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2107395 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2107467 | Enhancements on SRS for coverage and capacity | Fraunhofer IIS, Fraunhofer HHI |
| R1-2107489 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2107558 | SRS Performance and Potential Enhancements | Ericsson |
| R1-2107575 | Discussion on SRS enhancements | Intel Corporation |
| R1-2107723 | Views on Rel-17 SRS enhancement | Apple |
| R1-2107788 | Enhancements on SRS | Sharp |
| R1-2107819 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2107843 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2107898 | Discussion on SRS enhancements | Xiaomi |
| R1-2108057 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2108217 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2108373 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2108512 | FL summary #3 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2106469 | Discussion on CSI Enhancements for Rel-17 | Huawei, HiSilicon |
| R1-2106547 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2106577 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2106646 | Further Discussion on CSI Enhancements for NCJT MTRP | InterDigital, Inc. |
| R1-2106691 | Discussion on CSI enhancements for M-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2106794 | More considerations on CSI enhancements | Sony |
| R1-2106871 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2106941 | Discussion on CSI enhancements for Rel-17 | CATT |
| R1-2107084 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2107148 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2107179 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2107209 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2107329 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2107396 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2107466 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2107490 | CSI Enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2107576 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2107724 | Views on Rel-17 CSI enhancement | Apple |
| R1-2107820 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2107844 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2108058 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2108071 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | Ericsson |
| R1-2108355 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei) |
| R1-2108356 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei) |
| R1-2108357 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei) |
| R1-2108358 | Summary of CSI enhancements for MTRP and FDD (Round 3) | Moderator (Huawei) |
| 8.1.5 | Other | |
| R1-2106548 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2106578 | Discussion on impact of cross-talk on UL performance | vivo |
| R1-2106647 | Performance of Multi-Panel Multi-TRP MIMO | InterDigital, Inc. |
| R1-2106671 | HARQ feedback of SPS PDSCH reception in multi-DCI based multiple TRPs | Lenovo, Motorola Mobility |
| R1-2106872 | Additional enhancements for multi-beam | Samsung |
| R1-2107210 | Discussion on further enhancements for multi-beam operation | OPPO |
| R1-2107670 | Further considerations and simulations for Rel-17 PS codebook design | Huawei, HiSilicon |
| R1-2107725 | On Further MIMO Enhancement | Apple |
| R1-2107821 | Analysis on TRP- and/or UE panel-specific UL timing synchronization | LG Electronics |
| R1-2108087 | Rel.18 MIMO work item proposals | Ericsson |
| 8.2 | Supporting NR from 52.6GHz to 71 GHz | |
| R1-2108603 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Ericsson) |
| R1-2108677 | [Post-106-e-Rel17-RRC-02] Summary of email discussion on RRC parameters for supporting NR from 52.6GHz to 71 GHz | Moderator (Qualcomm) |
| 8.2.1 | Initial access aspects | |
| R1-2106442 | Initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2106579 | Discussions on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106692 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2106766 | Discussions on initial access signals and channels for operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2106795 | Considerations on initial access aspects for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2106831 | Initial access aspects for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106873 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106956 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2107000 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107032 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2107050 | Initial Access Aspects | Ericsson |
| R1-2107097 | Initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2107104 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2107112 | Further discussion of initial access for NR above 52.6 GHz | Charter Communications |
| R1-2107149 | Discussion on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2107176 | Initial access aspects for NR from 52.6GHz to 71 GHz | Panasonic Corporation |
| R1-2107237 | Discusson on initial access aspects | OPPO |
| R1-2107330 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2107435 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2107471 | Discussion on initial access aspects for NR from 52.6 to 71GHz | ETRI |
| R1-2107517 | Discussion on initial access of 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2107577 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2107726 | Initial access signals and channels | Apple |
| R1-2107789 | Initial access aspects | Sharp |
| R1-2107845 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2107912 | On initial access aspects for NR from 52.6GHz to 71 GHz | Xiaomi |
| R1-2108008 | NR SSB design consideration from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2108148 | Discussion on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2108206 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108207 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108363 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108480 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108551 | Summary #4 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108588 | Summary #5 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2108589 | Summary #6 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2106443 | Enhancement on PDCCH monitoring | Huawei, HiSilicon |
| R1-2106580 | Discussions on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106767 | Discussions on PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2106796 | PDCCH enhancement for 52.6 to 71 GHz | Sony |
| R1-2106832 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106874 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106957 | PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2107001 | Discussion on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107051 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2107098 | PDCCH and HARQ support for multi-PDSCH/PUSCH scheduling | FUTUREWEI |
| R1-2107105 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2107113 | PDCCH monitoring enhancements | Charter Communications |
| R1-2107153 | Discussion on PDCCH monitoring enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2107238 | Discussion on PDCCH monitoring enhancement | OPPO |
| R1-2107331 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2107432 | PDCCH monitoring for NR operation from 52.6 to 71 GHz | Panasonic |
| R1-2107436 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2107510 | PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2107578 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2107727 | PDCCH Enhancements for above 52.6 GHz | Apple |
| R1-2107790 | PDCCH monitoring enhancements | Sharp |
| R1-2107846 | PDCCH monitoring enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2107913 | Discussion on PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2108015 | PDCCH Monitoring for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2108233 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2108389 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2108390 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2108559 | Feature lead summary #4 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2106444 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2106581 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106693 | Discussion on enhancements for PUCCH formats 0/1/4 for above 52.6GHz | Spreadtrum Communications |
| R1-2106768 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2106797 | More considerations on PUCCH enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2106833 | Enhancements to PUCCH formats 0/1/4 for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106875 | Enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106958 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2107002 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107052 | PUCCH enhancements | Ericsson |
| R1-2107099 | Resource mapping and sequences for PUCCH formats 0/1/4 for 52.6GHz to 71GHz | FUTUREWEI |
| R1-2107106 | Enhanced PUCCH formats 0/1/4 | Nokia, Nokia Shanghai Bell |
| R1-2107239 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2107332 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2107437 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2107509 | On Enhancements for PUCCH formats 0/1/4 | MediaTek Inc. |
| R1-2107579 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2107728 | Discussion on Enhancements for PUCCH formats 0/1/4 above 52.6 GHz | Apple |
| R1-2107774 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2107847 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2108149 | Discussion on PUCCH enhancement for PUCCH format 0/1/4 | WILUS Inc. |
| R1-2108433 | FL Summary #2 for [106-e-NR-52-71GHz-03] Email discussion/approval on enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2108523 | FL Summary #3 for [106-e-NR-52-71GHz-03] Email discussion/approval on enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2108624 | FL Summary #4 for [106-e-NR-52-71GHz-03] Email discussion/approval on enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| 8.2.4 | Beam management for new SCSs | |
| R1-2106445 | Discussion on the beam management procedures for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2106582 | Discussions on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106694 | Discussion on beam management for above 52.6GHz | Spreadtrum Communications |
| R1-2106769 | Discussions on beam management for new SCSs | InterDigital, Inc. |
| R1-2106798 | Beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2106834 | Beam-management enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106876 | Beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106959 | Beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2107003 | Discussion on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107053 | Beam Management for New SCSs | Ericsson |
| R1-2107101 | Views on Beam management for beyond B52.6 GHz | FUTUREWEI |
| R1-2107107 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2107155 | Beam management enhancement for NR from 52.6GHz to 71GHz | NEC |
| R1-2107240 | Discussion on beam management for new SCSs | OPPO |
| R1-2107333 | Beam managment for new SCS | Qualcomm Incorporated |
| R1-2107438 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2107511 | Beam management discussion for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2107580 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2107729 | Beam Management for New SCSs | Apple |
| R1-2107848 | Beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2107914 | Discussion on beam management for new SCSs | Xiaomi |
| R1-2108016 | On Beam Management for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2108260 | Discussion Summary #1 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2108261 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2108541 | Discussion Summary #3 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2108542 | Discussion Summary #4 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2108654 | Discussion Summary #5 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2106446 | PDSCH/PUSCH enhancements for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2106569 | PT-RS enhancements for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2106583 | Discussions on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106695 | Discussion on PDSCH and PUSCH enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2106770 | PDSCH/PUSCH enhancements for supporting NR from 52.6GHz to 71 GHz | InterDigital, Inc. |
| R1-2106799 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2106835 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106877 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106960 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2107004 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107033 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2107039 | Enhancements of PDSCH/PUSCH Scheduling for 52.6 GHz to 71 GHz Band | CEWiT |
| R1-2107054 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2107100 | Enhancements of PDSCH/PUSCH and scheduling for 52.6GHz to 71GHz | FUTUREWEI |
| R1-2107108 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2107154 | Discussion on PDSCH enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2107241 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2107334 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2107439 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2107440 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2107512 | Multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2107581 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2107730 | Discussion on PDSCH and PUSCH Enhancements for NR above 52.6 GHz | Apple |
| R1-2107829 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2107849 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2107915 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2108010 | Discussion on multiple PDSCHs scheduled by a DCI | ITRI |
| R1-2108017 | NR PDSCH design consideration from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2108150 | Discussion on multi-PDSCH/PUSCH scheduling for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2108212 | Summary of PDSCH/PUSCH enhancements (Bandwidth/Timeline/Reference signals) | Moderator (vivo) |
| R1-2108284 | Discussion summary #1 of [106-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2108329 | Discussion summary #2 of [106-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2108333 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2108334 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2108370 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2108487 | Discussion summary #3 of [106-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2108550 | Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2108590 | Summary #5 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2108636 | Summary #6 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2106447 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2106584 | Discussions on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2106696 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2106771 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2106800 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2106836 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2106878 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2106961 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2107005 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2107034 | Considerations on receiver assistance in channel access | Fujitsu |
| R1-2107055 | Channel Access Mechanisms | Ericsson |
| R1-2107102 | Channel access for shared spectrum Beyond 52.6 GHz | FUTUREWEI |
| R1-2107109 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2107111 | Channel access mechanisms for NR above 52 GHz | Charter Communications |
| R1-2107150 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2107166 | Discussions on channel access mechanism enhancements for 52.6-71 GHz | CAICT |
| R1-2107242 | Discussion on channel access mechanism | OPPO |
| R1-2107335 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2107386 | Channel access for multi-beam operation | Panasonic |
| R1-2107441 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2107518 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2107582 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2107691 | Views on Rel. 17 channel access enhancements | AT&T |
| R1-2107731 | Channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2107850 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2107916 | Discussion on channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2108011 | Discussion on multi-beam operation | ITRI |
| R1-2108018 | Discussion On Channel Access for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2108099 | Discussion on EDT enhancement in channel access for NR unlicensed operation from 52.6 to 71GHz | GDCNI |
| R1-2108151 | Discussion on channel access mechanism for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2108223 | FL summary for channel access for beyond 52.6GHz band | Moderator (Qualcomm Incorporated) |
| R1-2108367 | FL summary#2 for channel access for beyond 52.6GHz band | Moderator (Qualcomm Incorporated) |
| R1-2108554 | FL summary#3 for channel access for beyond 52.6GHz band | Moderator (Qualcomm Incorporated) |
| 8.2.7 | Other | |
| R1-2106585 | Discussions on sync raster for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2106772 | Efficient beam management for NR in 52.6 – 71 GHz | InterDigital, Inc. |
| R1-2107006 | Evaluation results for above 52.6GHz | ZTE, Sanechips |
| R1-2107056 | NR channelization for the 57 – 71 GHz band | Ericsson |
| R1-2107110 | Simulation results | Nokia, Nokia Shanghai Bell |
| R1-2107442 | Link level evaluation results and complexity analysis for NR FR2-2 PTRS design | LG Electronics |
| R1-2107663 | LLS results for enhancement reference signals | Huawei, HiSilicon |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2108680 | Summary of [Post-106-e-Rel17-RRC-03] Enhanced IIoT and URLLC | Moderator (Nokia) |
| 8.3.1.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2106490 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2106586 | HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2106636 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2106639 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2106678 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2106697 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2106734 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2106801 | Considerations on HARQ-ACK enhancements for URLLC | Sony |
| R1-2106879 | On HARQ-ACK reporting enhancements | Samsung |
| R1-2106962 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2107025 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic |
| R1-2107133 | Discussion on UE feedback enhancements for HARQ-ACK | China Telecom |
| R1-2107156 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2107180 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2107272 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2107296 | Discussion on UE feedback enhancements for HARQ-ACK | FGI, Asia Pacific Telecom |
| R1-2107336 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2107397 | Discussion on UE feeback enhancements for HARQ-ACK | CMCC |
| R1-2107443 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2107472 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2107491 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2107583 | Design aspects for the agreed HARQ feedback enhancements | Intel Corporation |
| R1-2107639 | HARQ enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2107732 | HARQ Feedback Enhancements for URLLC | Apple |
| R1-2107791 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2107833 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2107851 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2107917 | UE feedback enhancements for HARQ-ACK | Xiaomi |
| R1-2108152 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | WILUS Inc. |
| R1-2108162 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2108440 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2108546 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2108547 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.1.2 | CSI feedback enhancements | |
| R1-2106491 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2106587 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2106679 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2106698 | Discussion on CSI feedback enhancements | Spreadtrum Communications |
| R1-2106735 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2106802 | Considerations on CSI enhancements for URLLC | Sony |
| R1-2106837 | Discussion on CSI Feedback Enhancements | Quectel, Langbo |
| R1-2106880 | UE Feedback Enhancements for URLLC | Samsung |
| R1-2106963 | CSI feedback enhancements | CATT |
| R1-2107019 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2107074 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2107078 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2107185 | CSI feedback enhancements for URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2107273 | CSI feedback enhancements for URLLC | OPPO |
| R1-2107337 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2107398 | Discussion on CSI feeback enhancements for URLLC | CMCC |
| R1-2107444 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2107492 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2107584 | On enhanced SB CQI reporting granularity and delta-MCS reporting | Intel Corporation |
| R1-2107733 | CSI feedback enhancements for URLLC | Apple |
| R1-2107852 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2108012 | Views for Increasing Granularity of Subband CQI | ITRI |
| R1-2108235 | Feature lead summary #1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2108236 | Feature lead summary #2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2108237 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2108449 | Feature lead summary #3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital) |
| R1-2108450 | Feature lead summary #4 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2106493 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2106588 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2106680 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2106699 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2106736 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2106764 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2106803 | Considerations on Unlicensed URLLC | Sony |
| R1-2106881 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2106964 | Discussion on remaining issues on enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2107013 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2107103 | UE initiated COT for semi-static channel access | FUTUREWEI |
| R1-2107114 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2107186 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2107274 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2107294 | Enhancements for unlicensed band URLLC/IIoT | FGI, Asia Pacific Telecom |
| R1-2107338 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2107445 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2107473 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2107493 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2107585 | On the Details for Enabling URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2107640 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2107734 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2107792 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2107853 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2108153 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2108301 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2108302 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2108303 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2108304 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2108305 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2108306 | Summary#6 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2106492 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2106589 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2106637 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106681 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2106700 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2106737 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2106804 | Considerations on UL Intra-UE Multiplexing | Sony |
| R1-2106838 | Discussion on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2106882 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2106965 | Intra-UE multiplexing and prioritization | CATT |
| R1-2107073 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2107115 | Discussion on Intra-UE multiplexing of different priority | Panasonic Corporation |
| R1-2107132 | Discussion on intra-UE multiplexing and prioritization | China Telecom |
| R1-2107157 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2107181 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2107200 | Discussion on Intra-UE Multiplexing and Prioritization | Potevio Company Limited |
| R1-2107275 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2107295 | Discussion on Intra-UE multiplexing/prioritization | FGI, Asia Pacific Telecom |
| R1-2107339 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2107446 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2107474 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2107494 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2107586 | Further details of intra-UE uplink channel multiplexing and prioritization | Intel Corporation |
| R1-2107735 | Design considerations on Rel-17 intra-UE multiplexing/prioritization | Apple |
| R1-2107793 | Enhancements of intra-UE UCI multiplexing on PUCCH and PUSCH | Sharp |
| R1-2107834 | Intra-UE multiplexing/prioritization | TCL Communication Ltd. |
| R1-2107854 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2108013 | Discussion on intra-UE multiplexing | ITRI |
| R1-2108154 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2108274 | Summary#1 of email thread [106-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2108336 | Summary#2 of email thread [106-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2108402 | Summary#3 of email thread [106-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2108556 | Summary#4 of email thread [106-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2108628 | Summary#5 of email thread [106-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2106590 | Discussion on propagation delay compensation enhancements | vivo |
| R1-2106638 | Discussion on enhancements for propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2106682 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2106738 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2106883 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2106966 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2107276 | Enhancement for support of time synchronization | OPPO |
| R1-2107340 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2107447 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2107495 | Discussion on propagation delay compensation for time synchronization | MediaTek Inc. |
| R1-2107587 | Further analysis and design considerations for propagation delay compensation methods | Intel Corporation |
| R1-2107678 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2108200 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2108384 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2108513 | Feature lead summary#3 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2108617 | Feature lead summary#4 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2108618 | Draft LS on TA-based propagation delay compensation | Moderator (Huawei) |
| R1-2108634 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2108635 | LS on TA-based propagation delay compensation | RAN1, Huawei |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2107076 | Updated NR_NTN_solutions work plan | THALES |
| R1-2108604 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| R1-2108675 | RRC parameter changes required for NR-NTN, up to RAN1 #106-e | Moderator (Thales) |
| 8.4.1 | Timing relationship enhancements | |
| R1-2106482 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2106591 | Discussion on timing relationship enhancements for NR-NTN | vivo |
| R1-2106701 | Discussion on timing relationship enhancements for NTN | Spreadtrum Communications |
| R1-2106723 | Timing relationship enhancements for NTN | Zhejiang Lab |
| R1-2106754 | Discussion on timing relationship enhancement for NTN | Baicells |
| R1-2106805 | Calculation and application of timing relationship offsets | Sony |
| R1-2106884 | Timing relationship enhancements for NTN | Samsung |
| R1-2106967 | Further discussion on timing relationship enhancements for NTN | CATT |
| R1-2107014 | Discussion on timing relationship enhancements for NTN | NEC |
| R1-2107064 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2107167 | Timing relationship enhancements to support NTN | CAICT |
| R1-2107194 | Discussion on timing relationship enhancements for NTN | Hyundai Motors |
| R1-2107243 | Discusson on timing relationship enhancement | OPPO |
| R1-2107287 | Timing relationship enhancements in NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107341 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2107399 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2107468 | Timing relationship for NTN | Panasonic Corporation |
| R1-2107538 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2107588 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2107636 | On timing relationship enhancements for NTN | Ericsson |
| R1-2107736 | On Timing Relationship Enhancements for NR NTN | Apple |
| R1-2107775 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2107855 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2107918 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2107944 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2107992 | Timing relationship enhancements for NTN | ITL |
| R1-2108031 | Timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2108070 | Discussion on Timing Relationship Enhancements for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108090 | Time relation aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2108220 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2108331 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2108439 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2108492 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2108555 | Feature lead summary#5 on timing relationship enhancements | Moderator (Ericsson) |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2106483 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2106556 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2106592 | Discussion on UL time and frequency synchronization enhancements for NR-NTN | vivo |
| R1-2106702 | Discussion on enhancements on UL time and frequency synchronization for NTN | Spreadtrum Communications |
| R1-2106755 | Discussion on UL time and frequency synchronization enhancement for NTN | Baicells |
| R1-2106781 | Feature lead summary #1 on enhancements on UL timing and frequency synchronization | THALES |
| R1-2106782 | Feature lead summary #2 on enhancements on UL timing and frequency synchronization | THALES |
| R1-2106783 | Feature lead summary #3 on enhancements on UL timing and frequency synchronization | THALES |
| R1-2106784 | Feature lead summary #4 on enhancements on UL timing and frequency synchronization | THALES |
| R1-2106785 | Feature lead summary #5 on enhancements on UL timing and frequency synchronization | THALES |
| R1-2106806 | Considerations on UL time synchronisation | Sony |
| R1-2106885 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2106968 | Enhancements on UL time and frequency synchronization for NTN | CATT |
| R1-2107020 | Enhancements on UL time and frequency synchronization | PANASONIC R&D Center Germany |
| R1-2107065 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2107244 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2107288 | UL time and frequency synchronization in NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107342 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2107400 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2107539 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2107589 | On UL synchronization for NTN | Intel Corporation |
| R1-2107637 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2107737 | On Uplink Time and Frequency Synchronization for NR NTN | Apple |
| R1-2107776 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2107856 | Discussion on UL time synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2107890 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2107919 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2107945 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2108032 | UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2108073 | Discussion on UL Time Synchronization for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108091 | Time and frequency synchronization for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2108240 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2108409 | DRAFT Reply LS on TA pre-compensation | OPPO |
| R1-2108410 | Reply LS on TA pre-compensation | RAN1, OPPO |
| R1-2108518 | Draft reply LS on TA pre-compensation | Moderator (OPPO) |
| R1-2108586 | FL Summary #6 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108587 | FL Summary #7 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| 8.4.3 | Enhancements on HARQ | |
| R1-2106484 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2106593 | Discussion on HARQ enhancements for NR-NTN | vivo |
| R1-2106703 | Discussion on enhancements on HARQ for NTN | Spreadtrum Communications |
| R1-2106756 | Discussion on HARQ enhancement for NTN | Baicells |
| R1-2106807 | Enhancements on HARQ for NTN | Sony |
| R1-2106886 | Enhancements on HARQ for NTN | Samsung |
| R1-2106969 | HARQ operation enhancement for NTN | CATT |
| R1-2107015 | Discussion on HARQ enhancements for NR NTN | NEC |
| R1-2107066 | Enhancements on HARQ for NR NTN | MediaTek Inc. |
| R1-2107168 | Enhancements on HARQ to support NTN | CAICT |
| R1-2107245 | Discussion on HARQ enhancements | OPPO |
| R1-2107289 | Enhancements on HARQ in NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107343 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2107401 | Enhancements on HARQ for NTN | CMCC |
| R1-2107469 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2107475 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2107540 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2107638 | On HARQ enhancements for NTN | Ericsson |
| R1-2107738 | HARQ Enhancements for NR NTN | Apple |
| R1-2107777 | Discussion on HARQ for NR-NTN | ZTE |
| R1-2107857 | Discussion on HARQ enhancements for NR NTN | NTT DOCOMO, INC. |
| R1-2107920 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2107993 | Discussion on HARQ enhancements for NTN | ITL |
| R1-2108033 | HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2108092 | Remaining HARQ aspects of NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2108343 | Summary#1 of AI 8.4.3 for HARQ in NTN | Moderator(ZTE) |
| R1-2108511 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator(ZTE) |
| 8.4.4 | Other | |
| R1-2106530 | Discussion on channel models for marine and inland river scenes | GDCNI |
| R1-2106557 | Beam management and BWP operation in NTN | THALES |
| R1-2106594 | Discussion on other aspects for NR-NTN | vivo |
| R1-2106704 | Discussion on beam management and other aspects for NTN | Spreadtrum Communications |
| R1-2106757 | Discussion on beam management and other consideration for NTN | Baicells |
| R1-2106808 | Discussion on beam management and polarization for NTN | Sony |
| R1-2106887 | Remaining issues for NTN Samsung | Samsung |
| R1-2106970 | Beam management and other aspects for NTN | CATT |
| R1-2106999 | Discussion on channel models for marine and inland river scenes | GDCNI |
| R1-2107016 | Remaining issues for NR NTN | NEC |
| R1-2107120 | Discussion on channel models for marine and inland river scenes | GDCNI |
| R1-2107246 | Discusson on beam management | OPPO |
| R1-2107290 | Other aspects of NR-NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107344 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2107381 | Problems of Rel-17 NTN WI from HAPS point of view | SoftBank Corp. |
| R1-2107402 | Other Aspects for NTN | CMCC |
| R1-2107463 | Beam management and polarization signaling for NTN | Panasonic |
| R1-2107541 | Discussions on other aspects of NTN | LG Electronics |
| R1-2107644 | On other enhancements for NTN | Ericsson |
| R1-2107675 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2107739 | On Other Aspects of NR NTN | Apple |
| R1-2107778 | Discussion on additional enhancement for NR-NTN | ZTE |
| R1-2107921 | Discussion on other design aspects for NTN | Xiaomi |
| R1-2107946 | Discussion on other aspects for NTN | Lenovo, Motorola Mobility |
| R1-2108034 | On beam management for NTN | InterDigital, Inc. |
| R1-2108093 | Further discussion of other aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2108234 | Summary #1 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2108411 | Summary #2 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2108517 | Summary #3 of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| 8.5 | NR Positioning Enhancements | |
| R1-2108605 | Session notes for 8.5 (NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2108682 | [Post-106-e-Rel17-RRC-05] Summary of email discussion on RRC parameters for NR Positioning Enhancements | Moderator (CATT) |
| 8.5.1 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | |
| R1-2106449 | Enhancement to mitigate gNB and UE Rx/Tx timing error | Huawei, HiSilicon |
| R1-2106549 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2106595 | Discussion on potential enhancements for RX/TX timing delay mitigating | vivo |
| R1-2106809 | On mitigating Rx/Tx timing delays | Sony |
| R1-2106888 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2106971 | Discussion on mitigating UE and gNB Rx/Tx timing errors | CATT |
| R1-2107057 | Views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2107213 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2107345 | Enhancements on Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2107403 | Discussion on mitigation of gNB/UE Rx/Tx timing errors | CMCC |
| R1-2107542 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2107590 | Details of UE/gNB RX/TX Timing Errors Mitigation | Intel Corporation |
| R1-2107643 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2107740 | Positioning accuracy enhancements under timing errors | Apple |
| R1-2107822 | Mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2107858 | Discussion on mitigating UE and gNB Rx/Tx timing delays | NTT DOCOMO, INC. |
| R1-2108101 | On methods for Rx/Tx timing delays mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108142 | Enhancements for mitigation of Tx/Rx Delays | Lenovo, Motorola Mobility |
| R1-2108164 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2108241 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2108242 | FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2108243 | FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2108244 | FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2108245 | FL Summary #5 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| 8.5.2 | Accuracy improvements for UL-AoA positioning solutions | |
| R1-2106450 | Enhancement for UL AoA positioning | Huawei, HiSilicon |
| R1-2106550 | Accuracy improvement for UL-AoA positioning solutions | ZTE |
| R1-2106596 | Discussion on potential enhancements for UL-AoA method | vivo |
| R1-2106810 | Considerations on UL-AoA enhancements | Sony |
| R1-2106889 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2106972 | Discussion on enhancements for UL-AoA positioning method | CATT |
| R1-2107058 | Views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2107214 | Enhancements for UL AoA Positioning | OPPO |
| R1-2107346 | Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2107404 | Discussion on UL-AoA enhancements | CMCC |
| R1-2107543 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2107591 | Remaining Details of NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2107645 | Discussion on enhancements for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2107741 | Positioning Accuracy enhancements for UL-AoA | Apple |
| R1-2107859 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2108102 | UL-AoA positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108165 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2108176 | Discussion on enhancements for UL AoA positioning | CEWiT |
| R1-2108289 | Feature Lead Summary#1 for E-mail Discussion [106-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2108290 | Feature Lead Summary#2 for E-mail Discussion [106-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2108291 | Feature Lead Summary#3 for E-mail Discussion [106-e-NR-ePos-02] | Moderator (Intel Corporation) |
| 8.5.3 | Accuracy improvements for DL-AoD positioning solutions | |
| R1-2106451 | Enhancement for DL AoD positioning | Huawei, HiSilicon |
| R1-2106551 | Accuracy improvement for DL-AoD positioning solutions | ZTE |
| R1-2106597 | Discussion on potential enhancements for DL-AoD method | vivo |
| R1-2106811 | Considerations on DL-AoD enhancements | Sony |
| R1-2106890 | Discussion on accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2106973 | Discussion on enhancements for DL-AoD positioning method | CATT |
| R1-2107059 | Views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2107169 | Discussion on enhancements for DL-AoD positioning | CAICT |
| R1-2107215 | Enhancements for DL-AoD positioning | OPPO |
| R1-2107347 | Potential Enhancements on DL-AoD positioning | Qualcomm Incorporated |
| R1-2107405 | Discussion on DL-AoD enhancements | CMCC |
| R1-2107544 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2107592 | DL-AoD Enhancements for Precise NR Positioning | Intel Corporation |
| R1-2107646 | Discussion on enhancements for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2107742 | Positioning Accuracy enhancements for DL-AoD | Apple |
| R1-2107823 | Accuracy enhancement for DL-AOD technique | MediaTek Inc. |
| R1-2107860 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2107922 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2108103 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108143 | Discussion on DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2108166 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2108174 | Discussion on enhancements for DL-AoD positioning | CEWiT |
| R1-2108311 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2108507 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2108577 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2108623 | FL summary #4 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2108645 | [DRAFT ]LS on beam/antenna information for DL AOD in NR positioning | Moderrator (Ericsson) |
| R1-2108646 | LS on beam/antenna information for DL AOD in NR positioning | RAN1, Ericsson |
| 8.5.4 | Latency improvements for both DL and DL+UL positioning methods | |
| R1-2106452 | Positioning latency enhancements | Huawei, HiSilicon |
| R1-2106552 | Discussion on latency reduction for NR positioning | ZTE |
| R1-2106598 | Discussion on latency enhancement for NR positioning | vivo |
| R1-2106812 | Considerations on latency improvements for positioning | Sony |
| R1-2106891 | Discussion on latency improvements for both DL and DL+UL positioning methods | Samsung |
| R1-2106974 | Discussion on latency reduction for NR positioning | CATT |
| R1-2107060 | Views on PHY Latency Reductions | Nokia, Nokia Shanghai Bell |
| R1-2107134 | Discussion on latency improvements for positioning methods | China Telecom |
| R1-2107216 | Enhancements on Latency Reduction in NR Positioning | OPPO |
| R1-2107348 | Enhancements for Latency Improvements for Positioning | Qualcomm Incorporated |
| R1-2107406 | Discussion on latency improvement for positioning | CMCC |
| R1-2107545 | Discussion on latency improvements for NR positioning | LG Electronics |
| R1-2107593 | Latency Reduction Solutions for NR Positioning | Intel Corporation |
| R1-2107647 | Discussion on latency improvements for DL and DL+UL positioning methods | InterDigital, Inc. |
| R1-2107743 | Views on Rel-17 positioning latency reduction | Apple |
| R1-2107828 | Aspects of physical latency improvement | MediaTek Inc. |
| R1-2107861 | Discussion on latency improvements for both DL and DL+UL positioning methods | NTT DOCOMO, INC. |
| R1-2107923 | Latency improvements for both DL and DL+UL positioning method | Xiaomi |
| R1-2108144 | Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
| R1-2108167 | Latency improvements for both DL and DL+UL positioning methods | Ericsson |
| R1-2108248 | FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2108249 | FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2108250 | FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2108583 | FL summary #4 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2108638 | [DRAFT] LS on PRS measurement outside the measurement gap | Moderator (Huawei) |
| R1-2108639 | LS on PRS measurement outside the measurement gap | RAN1, Huawei |
| 8.5.5 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | |
| R1-2106453 | Enhancements to support multi-path and NLOS mitigation | Huawei, HiSilicon |
| R1-2106553 | Enhancements on NLOS and Multi-path mitigation for NR positioning | ZTE |
| R1-2106599 | Discussion on potential enhancements for multipath/NLOS mitigation | vivo |
| R1-2106813 | Discussion on enhanced reporting for multipath/NLOS mitigation | Sony |
| R1-2106892 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Samsung |
| R1-2106975 | Discussion on information reporting from UE and gNB for multipath/NLOS mitigation | CATT |
| R1-2107061 | Views on LoS/NLoS Identification and Mitigation | Nokia, Nokia Shanghai Bell |
| R1-2107096 | NLOS Mitigation Enhancements | FUTUREWEI |
| R1-2107135 | Discussion on multipath/NLOS identification and mitigation for positioning enhancement | China Telecom |
| R1-2107217 | Discussion on multipath/NLOS mitigation for NR positioning | OPPO |
| R1-2107349 | Multipath Reporting in NR Positioning | Qualcomm Incorporated |
| R1-2107546 | Discussion on multipath/NLOS mitigation for positioning | LG Electronics |
| R1-2107594 | Solutions for Mitigation of NLOS Problem for NR Positioning | Intel Corporation |
| R1-2107648 | Discussion on multipath/NLOS mitigation for positioning | InterDigital, Inc. |
| R1-2107744 | Views on potential enhancements for NLOS mitigation in Rel-17 positioning | Apple |
| R1-2107862 | Discussion on multipath/NLOS mitigation for NR positioning | NTT DOCOMO, INC. |
| R1-2107924 | Potential enhancements for multipath/NLOS mitigation | Xiaomi |
| R1-2108104 | Potential positioning enhancements for multipath/NLOS mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108145 | Accuracy enhancements based on NLOS/Multipath Information Reporting | Lenovo, Motorola Mobility |
| R1-2108168 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2108175 | Discussion on enhancements of multipath/NLOS reporting from UE and gNB | CEWiT |
| R1-2108280 | Feature Lead Summary #1 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2108281 | Feature Lead Summary #2 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2108282 | Feature Lead Summary #3 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2108629 | Feature Lead Summary #4 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| 8.5.6 | Other | |
| R1-2106554 | Discussion on items led by RAN2 for NR positioning | ZTE |
| R1-2106600 | Discussion on inactive state positioning and on-demand PRS | vivo |
| R1-2106814 | Considerations on positioning in RRC Inactive and on-demand PRS | Sony |
| R1-2106893 | Discussion on demand positioning and positioning in inactive state | Samsung |
| R1-2106976 | Discussion on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state | CATT |
| R1-2107062 | Additional views on Inactive Mode Positioning and on-demand PRS | Nokia, Nokia Shanghai Bell |
| R1-2107170 | Discussion on other enhancements for on-demand PRS and INACTIVE mode positioning | CAICT |
| R1-2107218 | Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS | OPPO |
| R1-2107350 | Enhancements Related to On Demand PRS And Positioning in RRC Inactive State | Qualcomm Incorporated |
| R1-2107407 | Discussion on RAN2-led items for positioning | CMCC |
| R1-2107595 | On-demand DL PRS Signalling and NR Positioning for UEs in RRC-INACTIVE state | Intel Corporation |
| R1-2107649 | Discussion on on-demand PRS and INACTIVE mode positioning | InterDigital, Inc. |
| R1-2107664 | Discussion on RAN2 led objectives for NR positioning | Huawei, HiSilicon |
| R1-2107830 | Potential physical layer impact to the RAN2-led topics | MediaTek Inc. |
| R1-2107831 | Discussion on other enhancements for positioning | LG Electronics |
| R1-2107863 | Discussion on positioning for UEs in RRC_INACTIVE state | NTT DOCOMO, INC. |
| R1-2107925 | On-demand PRS and positioning for in-active state UE | Xiaomi |
| R1-2108105 | Considerations on SRS transmission for positioning in RRC_INACTIVE state | Fraunhofer IIS, Fraunhofer HHI |
| R1-2108146 | Discussion on On-Demand PRS and RRC_INACTIVE Positioning | Lenovo, Motorola Mobility |
| R1-2108169 | On-demand transmission and reception of DL PRS for DL and DL+UL positioning | Ericsson |
| R1-2108292 | Feature Lead Summary#1 for E-mail Discussion [106-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2108293 | Feature Lead Summary#2 for E-mail Discussion [106-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2108294 | Feature Lead Summary#3 for E-mail Discussion [106-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2108382 | Draft LS to RAN2 with update on RAN1 discussion for on-demand DL PRS | Moderator (Intel Corporation) |
| R1-2108383 | LS to RAN2 with update on RAN1 discussion for on-demand DL PRS | RAN1, Intel Corporation |
| R1-2108508 | Draft reply LS on determination of location estimates in local co-ordinates | Moderator (Ericsson) |
| R1-2108509 | Reply LS on determination of location estimates in local co-ordinates | RAN1, Ericsson |
| R1-2108563 | Draft LS to RAN2 on SRS for Positioning Transmission by UEs in RRC_INACTIVE State | Moderator (Intel Corporation) |
| R1-2108564 | LS to RAN2 on SRS for Positioning Transmission by UEs in RRC_INACTIVE State | RAN1, Intel Corporation |
| 8.6 | Support of Reduced Capability NR Devices | |
| R1-2107286 | Revised WI work plan for RedCap | Rapporteur (Ericsson) |
| R1-2108271 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2108606 | Session notes for 8.6 (Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2108669 | FL summary on RAN1 RRC parameter list for RedCap | Ericsson |
| R1-2108670 | Initial draft RAN1 RRC parameter list for RedCap | Ericsson |
| 8.6.1 | UE complexity reduction | |
| R1-2108114 | Complexity reduction for RedCap UE | GDCNI |
| 8.6.1.1 | Aspects related to reduced maximum UE bandwidth | |
| R1-2106459 | Reduced maximum UE bandwidth | Huawei, HiSilicon |
| R1-2106563 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2106601 | Discussion on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2106648 | UE Complexity Reduction aspects related to reduced maximum UE bandwidth | Nokia, Nokia Shanghai Bell |
| R1-2106705 | Discussion on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2106841 | Bandwidth reduction for reduced capability NR devices | ZTE, Sanechips |
| R1-2106894 | UE complexity reduction | Samsung |
| R1-2106977 | Discussion on reduced maximum UE bandwidth | CATT |
| R1-2107040 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2107089 | Discussion on Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2107128 | Discussion on reduced maximum UE bandwidth for RedCap | China Telecom |
| R1-2107197 | Discussion on reduced maximum UE bandwidth | TCL Communication Ltd. |
| R1-2107249 | Discussion on reduced UE bandwidth | OPPO |
| R1-2107300 | Discussion on aspects related to reduced maximum UE bandwidth | NEC |
| R1-2107351 | BW Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2107408 | Discussion on reduced maximum UE bandwidth | CMCC |
| R1-2107448 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2107496 | On reduced maximum bandwidth for RedCap UEs | MediaTek Inc. |
| R1-2107596 | On reduced BW support for RedCap | Intel Corporation |
| R1-2107745 | Reduced maximum UE bandwidth for Redcap | Apple |
| R1-2107794 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2107809 | Reduced maximum bandwidth for RedCap UEs | InterDigital, Inc. |
| R1-2107864 | Discussion on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2107926 | Discussion on the remaining issues of reduced maximum UE bandwidth for RedCap | Xiaomi |
| R1-2107947 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2108041 | Aspects related to reduced maximum UE bandwidth | Panasonic Corporation |
| R1-2108060 | Discussion on aspects related to reduced maximum UE bandwidth | ASUSTeK |
| R1-2108267 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108268 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108269 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108270 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108497 | FL summary #5 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108498 | FL summary #6 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2108632 | FL summary #7 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| 8.6.1.2 | Aspects related to reduced number of Rx branches | |
| R1-2106460 | Reduced number of Rx branches for RedCap | Huawei, HiSilicon |
| R1-2106564 | Reduced number of Rx branches for RedCap | Ericsson |
| R1-2106602 | Discussion on reduced number of Rx branches | vivo, Guangdong Genius |
| R1-2106649 | UE Complexity Reduction aspects related to reduced number of Rx branches | Nokia, Nokia Shanghai Bell |
| R1-2106842 | Discussion on reduced number of UE Rx branches | ZTE, Sanechips |
| R1-2106895 | Discussion on reduced number of RX branches for RedCap UEs | Samsung |
| R1-2106978 | Discussion on reduced number of Rx branches | CATT |
| R1-2107041 | On aspects related to reduced number of Rx branches | Nordic Semiconductor ASA |
| R1-2107250 | Discussion on reduced number of UE Rx branches | OPPO |
| R1-2107352 | RX Branch Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2107409 | Discussion on aspects related to reduced number of Rx branches | CMCC |
| R1-2107449 | Aspects related to the reduced number of Rx branches of RedCap | LG Electronics |
| R1-2107746 | On reduced number of Rx branches for Redcap | Apple |
| R1-2107747 | FL summary #1 on reduced number of Rx branches for RedCap | Apple |
| R1-2107795 | Discussion on reduced minimum number of Rx branches | Sharp |
| R1-2107810 | Reduced number of Rx branches for RedCap UEs | InterDigital, Inc. |
| R1-2107865 | Discussion on reduced minimum number of Rx branches for RedCap | NTT DOCOMO, INC. |
| R1-2107927 | Discussion on the remaining issues of reduced Rx for RedCap | Xiaomi |
| R1-2107948 | Remain issues for reduced number or Rx branches for RedCap | Lenovo, Motorola Mobility |
| R1-2108098 | Discussion on reduced number of Rx branches | China Unicom |
| R1-2108319 | FL summary #2 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2108351 | FL summary #3 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2108570 | Reduced number of Rx branches for RedCap | Ericsson |
| 8.6.1.3 | Aspects related to duplex operation | |
| R1-2106461 | Duplex operation for RedCap | Huawei, HiSilicon |
| R1-2106565 | Duplex operation for RedCap | Ericsson |
| R1-2106603 | Discussion on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2106650 | UE Complexity Reduction aspects related to duplex operation | Nokia, Nokia Shanghai Bell |
| R1-2106706 | Discussion on duplex operation for RedCap | Spreadtrum Communications |
| R1-2106843 | HD-FDD for reduced capability NR devices | ZTE, Sanechips |
| R1-2106896 | HD-FDD Operation for RedCap UEs | Samsung |
| R1-2106979 | Discussion on HD-FDD operation | CATT |
| R1-2107042 | On aspects related to duplex operation | Nordic Semiconductor ASA |
| R1-2107129 | Discussion on duplex operation for RedCap | China Telecom |
| R1-2107251 | On half-duplex operation | OPPO |
| R1-2107353 | Type-A HD-FDD for RedCap UE | Qualcomm Incorporated |
| R1-2107410 | Discussion on collision handling of HD-FDD operation | CMCC |
| R1-2107450 | Aspects related to the duplex operation of RedCap | LG Electronics |
| R1-2107497 | On half duplex operation for RedCap UEs | MediaTek Inc. |
| R1-2107597 | On HD-FDD support for RedCap | Intel Corporation |
| R1-2107748 | Duplex Operation for Redcap | Apple |
| R1-2107796 | Discussion on the duplex operation of redcap UEs | Sharp |
| R1-2107811 | Duplex operation for RedCap UEs | InterDigital, Inc. |
| R1-2107866 | Discussion on duplex operation for RedCap | NTT DOCOMO, INC. |
| R1-2107928 | Discussion on Half-duplex FDD operation of Redcap UE | Xiaomi |
| R1-2108042 | Aspects related to duplex operation | Panasonic Corporation |
| R1-2108061 | Discussion on aspects related to duplex operation | ASUSTeK |
| R1-2108155 | Discussion on duplex operation for RedCap UE | WILUS Inc. |
| R1-2108252 | FL summary #1 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2108327 | FL summary #2 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2108328 | FL summary #3 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2108477 | FL summary #4 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2108478 | FL summary #5 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| 8.6.1.4 | Other aspects | |
| R1-2106566 | Other UE complexity reduction aspects for RedCap | Ericsson |
| R1-2106652 | Other UE Complexity Reduction Aspects | Nokia, Nokia Shanghai Bell |
| R1-2106844 | Discussion on DL MIMO layers for RedCap UEs | ZTE, Sanechips |
| R1-2106980 | Discussion on other aspects related to complexity reduction | CATT |
| R1-2107301 | MIMO aspects for RedCap | NEC |
| R1-2107354 | Other Aspects of UE Complexity Reduction | Qualcomm Incorporated |
| R1-2107411 | Discussion on potential modification of existing DCI formats | CMCC |
| R1-2107668 | Reduced maximum MIMO layers and reduced maximum modulation order for RedCap | Huawei, HiSilicon |
| R1-2107929 | Discussion on the UE features for RedCap | Xiaomi |
| R1-2108088 | RedCap UE Further Complexity Reduction Considerations | u-blox AG |
| R1-2108316 | FL summary #1 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2108524 | FL summary #2 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| 8.6.2 | RAN1 aspects for RAN2-led features for RedCap | |
| R1-2106462 | RAN1 aspects of RedCap UE type and identification | Huawei, HiSilicon |
| R1-2106567 | RAN1 aspects for RAN2-led features for RedCap | Ericsson |
| R1-2106604 | Higher layer support for RedCap | vivo, Guangdong Genius |
| R1-2106651 | Higher layer support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2106707 | Discussion on early indication for RedCap | Spreadtrum Communications |
| R1-2106845 | Higher layer support of Reduced Capability NR devices | ZTE, Sanechips |
| R1-2106897 | RAN1 aspects for RAN2-led features for RedCap | Samsung |
| R1-2106981 | Discussion on higher layer support of RedCap | CATT |
| R1-2107043 | On RedCap UE early identification and UE type | Nordic Semiconductor ASA |
| R1-2107077 | Design consideration for Higher layer support of RedCap | Sierra Wireless, S.A. |
| R1-2107090 | Discussion on the Identification of RedCap UEs | FUTUREWEI |
| R1-2107130 | Discussion on RAN1 aspects for RAN2-led features for RedCap | China Telecom |
| R1-2107252 | Mechanism in higher&PHY layer for Reduced Capability NR Devices | OPPO |
| R1-2107302 | RAN1 aspects for RAN2-led features for RedCap | NEC |
| R1-2107355 | Cross Layer Design Considerations for RedCap Device | Qualcomm Incorporated |
| R1-2107412 | Discussion on higher layer support of RedCap UE | CMCC |
| R1-2107451 | RAN1 aspects for RAN2-led features for RedCap | LG Electronics |
| R1-2107598 | On RAN1 aspects for RAN2-led objectives for RedCap | Intel Corporation |
| R1-2107749 | On Higher Layer Support of Redcap Devices | Apple |
| R1-2107797 | RAN1 aspects for RAN2-led features for RedCap | Sharp |
| R1-2107812 | Identification and restriction of RedCap UEs | InterDigital, Inc. |
| R1-2107867 | Discussion on RAN1 aspects for RAN2-led features for RedCap | NTT DOCOMO, INC. |
| R1-2107868 | FL summary #1 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2107930 | Discussion on the remaining issues of the higher layer related topics for RedCap | Xiaomi |
| R1-2107949 | RAN1 aspects for RAN2-led features for RedCap | Lenovo, Motorola Mobility |
| R1-2108043 | RAN1 aspects for RAN2-led features for RedCap | Panasonic Corporation |
| R1-2108156 | Discussion on higher layer support of Redcap UE | WILUS Inc. |
| R1-2108341 | FL summary #2 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108369 | FL summary #3 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108483 | FL summary #4 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108552 | FL summary #5 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108614 | FL summary #6 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108615 | [Draft] LS on RAN1 agreements on RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108630 | FL summary #7 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO, INC.) |
| R1-2108631 | LS on RAN1 agreements on RAN2-led features for RedCap | RAN1, NTT DOCOMO, INC. |
| 8.6.3 | Other | |
| R1-2106568 | Potential RedCap solutions for avoiding or minimizing PUSCH resource fragmentation | Ericsson |
| R1-2106605 | Discussion on L1 reduced capability signaling | vivo, Guangdong Genius |
| R1-2106653 | Discussion on RedCap UE capabilities | Nokia, Nokia Shanghai Bell |
| R1-2106846 | NR UE features for RedCap | ZTE, Sanechips |
| R1-2106982 | Views on remaining issues of RedCap | CATT |
| R1-2107385 | Discussion on scaling factor for RedCap | Spreadtrum Communications, Apple, CEPRI |
| R1-2107413 | Discussion other aspects of RedCap UE | CMCC |
| R1-2107452 | Discussion on other aspects of RedCap | LG Electronics |
| R1-2107669 | On RedCap UL transmission | Huawei, HiSilicon |
| R1-2107931 | Discussion on the transmission of system information for RedCap | Xiaomi |
| R1-2108050 | Considerations on 2-step RACH for RedCap | Lenovo, Motorola Mobility |
| 8.7 | UE Power Saving Enhancements | |
| R1-2108607 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2108683 | [Post-106-e-Rel17-RRC-07] Summary of email discussion on RRC parameters for UE Power Saving Enhancements | Moderator (MediaTek) |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2106479 | Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2106520 | Potential Paging Enhancements | TCL Communication Ltd. |
| R1-2106521 | Discussion on power saving enhancements for paging | ZTE, Sanechips |
| R1-2106606 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2106708 | Discussion on potential paging enhancements for UE power saving | Spreadtrum Communications |
| R1-2106775 | Discussion on paging enhancements | Transsion Holdings |
| R1-2106815 | Paging enhancements for idle/inactive UE power saving | Sony |
| R1-2106898 | Discussion on paging enhancements | Samsung |
| R1-2106983 | Paging enhancement for UE power saving | CATT |
| R1-2106998 | Discussion on paging enhancements with PEI | Transsion Holdings |
| R1-2107044 | On paging early indication | Nordic Semiconductor ASA |
| R1-2107182 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2107253 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2107356 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2107414 | Discussion on paging early indication design | CMCC |
| R1-2107453 | Discussion on potential paging enhancements | LG Electronics |
| R1-2107519 | Design of Paging Early Indication for Idle-Mode UE Power Saving | MediaTek Inc. |
| R1-2107599 | On Paging Enhancements for UE Power Saving | Intel Corporation |
| R1-2107622 | On paging enhancement | Panasonic |
| R1-2107750 | Paging enhancements for idle/inactive-mode UE | Apple |
| R1-2107806 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2107869 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2107932 | Potential paging enhancements for power saving | Xiaomi |
| R1-2107998 | Design of Paging Enhancements | Ericsson |
| R1-2108122 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2108310 | Summary of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2108398 | Summary#2 of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2108475 | Summary#3 of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2108495 | Summary#4 of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2108625 | Summary#5 of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2108660 | Summary#6 of paging enhancements | Moderator (MediaTek Inc.) |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2106480 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2106519 | TRS/CSI-RS occasions for IDLE/inactive mode | TCL Communication Ltd. |
| R1-2106522 | TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2106607 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2106709 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2106816 | Considerations on TRS/CSI-RS occasion(s) for idle/inactive UEs | Sony |
| R1-2106899 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2106900 | Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2106984 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2107045 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2107183 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2107254 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2107357 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2107415 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2107454 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2107520 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2107600 | On TRS/CSI-RS Ocassions for UE Power Saving | Intel Corporation |
| R1-2107623 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2107751 | Indication of TRS configurations for idle/inactive-mode UE power saving | Apple |
| R1-2107798 | Discussion on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2107807 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2107870 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2107933 | On TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2107999 | Provisioning TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2108123 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2108362 | Moderator summary#2 for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2108454 | Moderator summary#2 for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2108514 | Moderator summary#3 for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2108515 | Final summary for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2106523 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE, Sanechips |
| R1-2106608 | Discussion on paging grouping | vivo |
| R1-2106985 | Details of PEI configuration | CATT |
| R1-2107673 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2107934 | Other aspect for idle/inactive-mode UE power saving | Xiaomi |
| R1-2108000 | NW power consumption evaluation of SIB based TRS availability signaling | Ericsson |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2106481 | Extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2106524 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2106610 | Discussion on DCI-based power saving adaptation in connected mode | vivo |
| R1-2106710 | Discussion on power saving techniques for connected-mode UE | Spreadtrum Communications |
| R1-2106901 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2106986 | PDCCH monitoring adaptation | CATT |
| R1-2107017 | Discussion on DCI-based power saving adaptation | NEC |
| R1-2107046 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2107184 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2107255 | DCI-based power saving adaptation solutions | OPPO |
| R1-2107358 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2107416 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2107455 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2107476 | DCI-based power saving adaptation during DRX active time | ETRI |
| R1-2107521 | On enhancements to DCI-based UE power saving during DRX active time | MediaTek Inc. |
| R1-2107533 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2107601 | On PDCCH Monitoring Adaptation during DRX active time | Intel Corporation |
| R1-2107624 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2107752 | Enhanced DCI-based power saving adaptation | Apple |
| R1-2107808 | PDCCH monitoring reduction in Active Time | InterDigital, Inc. |
| R1-2107871 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2108001 | Design of active time power savings mechanisms | Ericsson |
| R1-2108014 | Discussion on DCI-based power saving adaptation | ITRI |
| R1-2108048 | A common framework for SSSG switching and PDCCH skipping | ASUSTeK |
| R1-2108124 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2108224 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2108225 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2108386 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2108387 | FL summary#4 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2108620 | FL summary#5 of DCI-based power saving adaptation | Moderator (vivo) |
| 8.7.3 | Other | |
| R1-2106525 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE, Sanechips |
| R1-2106609 | UE Power Model for Downlink Reception | vivo |
| R1-2106987 | Link level performance for UE power saving | CATT |
| R1-2107674 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2108002 | Evaluation results for UE power saving schemes | Ericsson |
| 8.8 | NR coverage enhancement | |
| R1-2108458 | Reply LS on PUCCH and PUSCH repetition | RAN1, Qualcomm |
| R1-2108608 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2108673 | [Post-106-e-Rel17-RRC-08] Summary of email discussion on RRC parameters for NR coverage enhancements | Moderator (China Telecom) |
| 8.8.1.1 | Enhancements on PUSCH repetition type A | |
| R1-2106495 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2106611 | Discussion on enhancement for PUSCH repetition type A | vivo |
| R1-2106655 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2106739 | Discussion on enhanced PUSCH repetition type A | ZTE |
| R1-2106902 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2106988 | Discussion on enhancements on PUSCH repetition type A | CATT |
| R1-2107116 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2107121 | Discussion on enhancements on PUSCH repetition type A | Rakuten Mobile, Inc |
| R1-2107123 | Enhancements on PUSCH repetition type A | China Telecom |
| R1-2107140 | Discussion on PUSCH repetition type A | NEC |
| R1-2107190 | Enhancements on PUSCH repetition type A | Lenovo, Motorola Mobility |
| R1-2107256 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2107359 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2107417 | Discussion on enhancements on PUSCH repetition type A | CMCC |
| R1-2107548 | Discussions on PUSCH repetition type A enhancements | LG Electronics |
| R1-2107559 | PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2107602 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2107634 | Design considerations for PUSCH repetition Type A Enhancements | Sierra Wireless, S.A. |
| R1-2107650 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2107753 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2107799 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2107872 | Enhancements on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2107935 | Enhancements on PUSCH repetition type A | Xiaomi |
| R1-2108157 | Discussion on enhancements on PUSCH repetition type A | WILUS Inc. |
| R1-2108286 | FL Summary #1 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2108287 | FL Summary #2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2108462 | FL Summary #3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2108463 | FL Summary #4 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2108616 | FL Summary #5 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2108650 | FL Summary #6 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2106496 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2106612 | Discussion on PUSCH TB processing over multiple slots | vivo |
| R1-2106656 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106740 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2106903 | TB processing over multi-slot PUSCH | Samsung |
| R1-2106989 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2107035 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2107117 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2107124 | Discussion on TB processing over multi-slot PUSCH | China Telecom |
| R1-2107141 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2107191 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2107198 | Discussion on TBoMS | TCL Communication Ltd. |
| R1-2107257 | Issues for TB over multi-slot PUSCH | OPPO |
| R1-2107360 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2107418 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2107523 | Discussion on TB processing over multi-slot PUSCH | MediaTek Inc. |
| R1-2107549 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2107560 | TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2107603 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2107635 | Design Considerations for TB Processing over Multi-Slot PUSCH | Sierra Wireless, S.A. |
| R1-2107651 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2107754 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2107800 | Transport block processing over multi-slot PUSCH | Sharp |
| R1-2107873 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2107936 | Discussion on TB processing over multi-slot PUSCH | Xiaomi |
| R1-2108158 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2108253 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2108544 | FL summary #2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2108545 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2106497 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2106613 | Discussion on joint channel estimation for PUSCH | vivo |
| R1-2106657 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106711 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2106741 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2106817 | On joint channel estimation for PUSCH | Sony |
| R1-2106904 | Joint channel estimation for PUSCH | Samsung |
| R1-2106990 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2107125 | Discussion on joint channel estimation for PUSCH | China Telecom |
| R1-2107192 | Enhancements for joint channel estimation for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2107199 | Discussion on Joint channel estimation for PUSCH | TCL Communication Ltd. |
| R1-2107258 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2107361 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2107419 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2107524 | Discussion on Joint channel estimation over multi-slot PUSCH | MediaTek Inc. |
| R1-2107550 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2107561 | Joint Channel Estimation for PUSCH | Ericsson |
| R1-2107604 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2107633 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless, S.A. |
| R1-2107652 | Joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2107755 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2107801 | Joint channel estimation for multiple PUSCH transmission | Sharp |
| R1-2107832 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2107874 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2107937 | Discussion on joint channel estimation for PUSCH | Xiaomi |
| R1-2108159 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2108221 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2108371 | FL Summary#2 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2108416 | FL Summary#3 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2108503 | FL Summary#4 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2108504 | FL Summary#5 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2108644 | [106-e-NR-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.2 | PUCCH enhancements | |
| R1-2106498 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2106614 | Discussion on PUCCH enhancements | vivo |
| R1-2106658 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106712 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2106742 | Discussion on coverage enhancements for PUCCH | ZTE |
| R1-2106905 | PUCCH enhancements | Samsung |
| R1-2106991 | Discussion on PUCCH enhancement | CATT |
| R1-2107118 | Discussion on PUCCH enhancement for NR coverage enhancement | Panasonic Corporation |
| R1-2107126 | Discussion on PUCCH enhancements | China Telecom |
| R1-2107142 | Discussion on PUCCH enhancements | NEC |
| R1-2107193 | Enhancements for PUCCH repetition | Lenovo, Motorola Mobility |
| R1-2107259 | PUCCH enhancements for coverage | OPPO |
| R1-2107362 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2107420 | Discussion on PUCCH enhancements | CMCC |
| R1-2107477 | PUCCH enhancements | ETRI |
| R1-2107551 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2107562 | PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2107605 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2107653 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2107756 | PUCCH coverage enhancement | Apple |
| R1-2107802 | PUCCH coverage enhancement | Sharp |
| R1-2107875 | PUCCH enhancements | NTT DOCOMO, INC. |
| R1-2107938 | Discussion on PUCCH enhancements | Xiaomi |
| R1-2108315 | FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2108347 | FL summary#2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2108482 | FL summary#3 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2108619 | FL summary#4 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2106499 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2106615 | Discussion on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2106659 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2106713 | Discussion on type A PUSCH repetitions for Msg3 | Spreadtrum Communications |
| R1-2106743 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2106906 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2106992 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2107119 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2107127 | Discussion on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2107260 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2107363 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2107421 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2107478 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2107552 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2107563 | Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2107606 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2107654 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2107757 | Discussion on Msg3 Coverage Enhancement | Apple |
| R1-2107803 | Type A PUSCH repetition for msg3 | Sharp |
| R1-2107876 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2107939 | Discussion on Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2108160 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2108258 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2108259 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2108584 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2108585 | Feature lead summary #4 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| 8.8.4 | Other | |
| R1-2106616 | Enhanced contention resolution mechanism for CBRA procedure with MSG3 PUSCH repetition | vivo |
| R1-2106660 | Discussion on the scope of DMRS bundling for PUSCH | Nokia, Nokia Shanghai Bell |
| R1-2106744 | Performance impacts of residual frequency error for joint channel estimation of PUSCH and PUCCH transmissions | ZTE |
| R1-2106993 | Views on reusing PUSCH enhancements for Msg3 | CATT |
| R1-2107564 | Other Coverage Enhancements for PUSCH | Ericsson |
| R1-2107655 | Deterministic PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2107679 | On futher potential coverage enhancements | Huawei, HiSilicon |
| R1-2107940 | Other considerations for coverage enhancement | xiaomi |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2107687 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R1-2108609 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2108684 | [Post-106-e-Rel17-RRC-09] Summary of email discussion on RRC parameters for Enhancements for NB-IoT and LTE-MTC | Moderator (Huawei) |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2106558 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2106654 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2106758 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2106847 | Discussion on UL and DL 16QAM for NB-IoT | ZTE, Sanechips |
| R1-2107508 | Support 16QAM in NB-IOT | MediaTek Inc. |
| R1-2107941 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2108116 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2108275 | Feature lead summary #1 on 106-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2108466 | Feature lead summary #2 on 106-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2108530 | Feature lead summary #3 on 106-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2108642 | Feature lead summary #4 on 106-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2106559 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2106661 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2106759 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2106848 | Remaining issues on 14-HARQ processes in DL for eMTC | ZTE, Sanechips |
| R1-2108117 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2108295 | Feature Lead Summary [106-e-LTE-Rel17_NB_IoT_eMTC-02] - 1st check point | Moderator (Ericsson) |
| R1-2108296 | Feature Lead Summary [106-e-LTE-Rel17_NB_IoT_eMTC-02] - 2nd check point | Moderator (Ericsson) |
| R1-2108297 | Feature Lead Summary [106-e-LTE-Rel17_NB_IoT_eMTC-02] - final check | Moderator (Ericsson) |
| 8.9.3 | Other | |
| R1-2107684 | Discussion on DL PAPR for 16-QAM of NB-IoT | Huawei, HiSilicon |
| R1-2108118 | On Rel-17 RRC parameters and specification impacts for LTE-M and NB-IoT | Ericsson |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2107364 | Workplan for Rel-17 IAB | Qualcomm Incorporated |
| R1-2108685 | [Post-106-e-Rel17-RRC-10] Summary of email discussion on RRC parameters for eIAB | Moderator (Qualcomm) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2106454 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2106617 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2106828 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2106907 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2107188 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2107365 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2107479 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2107553 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2107607 | Enhancements to resource multiplexing between child and parent links of an IAB node | Intel Corporation |
| R1-2107692 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2107758 | Enhanced resource multiplexing within and across IAB nodes | Apple |
| R1-2107824 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2107877 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2108107 | Resource multiplexing and dual connectivity in enhanced IAB | Ericsson |
| R1-2108161 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2108277 | Feature lead summary #1 of 8.10.1 | Moderator (AT&T) |
| R1-2108278 | Feature lead summary #2 of 8.10.1 | Moderator (AT&T) |
| R1-2108279 | Feature lead summary #3 of 8.10.1 | Moderator (AT&T) |
| R1-2108494 | Reply LS on IAB resource multiplexing | RAN1, Ericsson |
| R1-2108525 | Draft reply LS on Inter-donor migration | Moderator (Huawei) |
| R1-2108529 | Reply LS on Inter-donor migration | RAN1, Huawei |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2106455 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2106618 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2106829 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Nokia, Nokia Shanghai Bell |
| R1-2106908 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2107036 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Fujitsu |
| R1-2107189 | Timing, interference, and power control in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2107366 | Enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2107480 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2107554 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2107608 | Other Enhancements for simultaneous operations | Intel Corporation |
| R1-2107693 | Enhancements for IAB interference management | AT&T |
| R1-2107759 | Other enhancements for simultaneous operation of an IAB node's links | Apple |
| R1-2107825 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2107878 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2108040 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2108108 | Timing, interference management and power control in enhanced IAB | Ericsson |
| R1-2108339 | FL summary#1 on other enhancements for simultaneous operation of IAB-node’s child and parent links [106-e-NR-eIAB-04] | Moderator (Qualcomm) |
| R1-2108479 | FL summary#2 on other enhancements for simultaneous operation of IAB-node’s child and parent links [106-e-NR-eIAB-04] | Moderator (Qualcomm) |
| R1-2108568 | FL summary#3 on other enhancements for simultaneous operation of IAB-node’s child and parent links [106-e-NR-eIAB-04] | Moderator (Qualcomm) |
| 8.10.3 | Other | |
| R1-2106619 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2106830 | Discussion on inter-donor IAB migration and topology redundancy | Nokia, Nokia Shanghai Bell |
| R1-2107665 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2107826 | Consideration on reference carrier for semi-static IAB-DU resource configuration | ZTE, Sanechips |
| R1-2108109 | Discussion on overlapping DCI format 2_5 indications in enhanced IAB | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2108681 | [Post-106-e-Rel17-RRC-11] Summary of email discussion on RRC parameters for Sidelink enhancement | Moderator (LG Electronics) |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2106477 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2106531 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2106620 | Resource allocation for sidelink power saving | vivo |
| R1-2106714 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2106724 | Discussion on resource allocation for power saving | Zhejiang Lab |
| R1-2106818 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2106909 | On Resource Allocation for Power Saving | Samsung |
| R1-2106942 | Discussion on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2107021 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2107022 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2107037 | Considerations on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2107091 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2107151 | Discussion on resource allocation for power saving | NEC |
| R1-2107163 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2107171 | Considerations on partial sensing mechanism of NR V2X | CAICT |
| R1-2107195 | Discussion on resource allocation for power saving | Hyundai Motors |
| R1-2107223 | Discussion on power saving in NR sidelink communication | OPPO |
| R1-2107367 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2107422 | Discussion on resource allocation for power saving | CMCC |
| R1-2107481 | Discussion on resource allocation for power saving | ETRI |
| R1-2107498 | Discussion on sidelink power saving | MediaTek Inc. |
| R1-2107528 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2107609 | Sidelink Resource Allocation Schemes for UE Power Saving | Intel Corporation |
| R1-2107760 | Sidelink Resource Allocation for Power Saving | Apple |
| R1-2107804 | Discussion on resource allocation for power saving | Sharp |
| R1-2107879 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2107899 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2108023 | Resource Allocation for Power Saving in NR SL | Convida Wireless |
| R1-2108035 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2108085 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2108096 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2108121 | Resource allocation for power saving in NR sidelink enhancement | ITL |
| R1-2108136 | Resource allocation procedures for power saving | Ericsson |
| R1-2108238 | Discussion on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2108262 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 1st check point) | Moderator (OPPO) |
| R1-2108263 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 2nd check point) | Moderator (OPPO) |
| R1-2108264 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 3rd check point) | Moderator (OPPO) |
| R1-2108265 | FL summary for AI 8.11.1.1 – resource allocation for power saving (EOM) | Moderator (OPPO) |
| R1-2108266 | Moderator summary for [106-e-NR-R17-Sidelink-02] Reply LS to R1-2106413 | Moderator (OPPO) |
| R1-2108580 | Reply LS on SL DRX design | RAN1, ZTE |
| R1-2108621 | Draft reply LS on time gap information in SCI | Moderator (OPPO) |
| R1-2108622 | Reply LS on time gap information in SCI | RAN1, OPPO |
| R1-2108653 | Summary of [106-e-NR-R17-Sidelink-03] email discussion to reply LS in R1-2100021 | Moderator (ZTE) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2106478 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2106532 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106570 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2106621 | Discussion on mode-2 enhancements | vivo |
| R1-2106715 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2106725 | Discussion on inter-UE coordination for mode 2 enhancements | Zhejiang Lab |
| R1-2106819 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2106910 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2106943 | Discussion on inter-UE coordination in sidelink mode 2 | CATT, GOHIGH |
| R1-2107023 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2107038 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2107092 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2107152 | Discussion on mode 2 enhancements | NEC |
| R1-2107164 | Discussion on inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2107172 | Considerations on mode 2 enhancements | CAICT |
| R1-2107196 | Discussion on inter-UE coordination for Mode 2 enhancements | Hyundai Motors |
| R1-2107224 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2107303 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2107368 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2107423 | Discussion on inter-UE coordination for mode 2 enhancement | CMCC |
| R1-2107482 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2107522 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2107529 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2107610 | Design of Inter-UE Coordination Solutions for Sidelink Communication | Intel Corporation |
| R1-2107621 | Inter-UE Coordination for Mode 2 Enhancements | Kyocera |
| R1-2107761 | Discussion on Inter-UE Coordination | Apple |
| R1-2107782 | Discussion on inter-UE coordination | ZTE |
| R1-2107805 | Discussion on inter-UE coordination for mode 2 enhancements | Sharp |
| R1-2107880 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2107900 | Discussion on inter-UE coordination | Xiaomi |
| R1-2107994 | Inter-UE coordination for mode 2 enhancements | ITL |
| R1-2108024 | Inter-UE Coordination for NR SL Mode 2 Enhancements | Convida Wireless |
| R1-2108036 | On inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2108097 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2108115 | Feasibility and benefits for NR Sidelink mode 2 enhancements | CEWiT |
| R1-2108137 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2108210 | Discussion on mode-2 enhancements | vivo |
| R1-2108272 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2108340 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2108569 | Feature lead summary for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2108627 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| 8.11.2 | Other | |
| R1-2106622 | Other aspects on SL enhancements | vivo |
| R1-2106911 | Discussion on Sidelink Enhancement | Samsung |
| R1-2106944 | Discussion on SL DRX configuration | CATT, GOHIGH |
| R1-2107225 | Wake up signal for NR sidelink | OPPO |
| R1-2107762 | Network Assisted Resource Selection | Apple |
| R1-2107901 | Discussion on other design aspects for sidelink enhancement | Xiaomi |
| R1-2108037 | On gNB-designated resources for inter-UE coordination | InterDigital, Inc. |
| R1-2108086 | BWP configuration for power saving | ZTE, Sanechips |
| R1-2108138 | Additional enhancements to resource allocation procedures | Ericsson |
| R1-2108184 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2108572 | Summary for email discussion [106-e-NR-R17-Sidelink-05] | Moderator (CATT) |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2108610 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Ericsson) |
| R1-2108686 | [Post-106-e-Rel17-RRC-12] Summary of email discussion on RRC parameters for NR MBS | Moderator (CMCC, Huawei, BBC) |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2106438 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2106623 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED Ues | vivo |
| R1-2106662 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2106716 | Discussion on MBS group scheduling for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2106745 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2106820 | Considerations on MBS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2106912 | Support of group scheduling for RRC_CONNECTED Ues | Samsung |
| R1-2106945 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2106996 | Common frequency resource configuration for multicast of RRC_CONNECTED Ues | ETRI |
| R1-2107093 | Group Scheduling Aspects for Connected UEs | FUTUREWEI |
| R1-2107137 | Discussion on Group Scheduling Mechanisms for RRC_CONNECTED Ues | NEC |
| R1-2107160 | On group scheduling mechanism for NR MBS | Lenovo, Motorola Mobility |
| R1-2107201 | Discussion on group scheduling mechanisms for RRC_CONNECTED UEs | Potevio Company Limited |
| R1-2107229 | Discussion on group Scheduling mechanism for RRC_CONNECTED UEs | OPPO |
| R1-2107369 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2107382 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Google Inc. |
| R1-2107424 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2107425 | Discussion on group scheduling mechanisms | CMCC |
| R1-2107456 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2107514 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2107611 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2107763 | Discussion on group scheduling mechanism for RRC_CONNECTED Ues | Apple |
| R1-2107881 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2107902 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UE | Xiaomi |
| R1-2107950 | Group scheduling related discussion for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2108026 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Convida Wireless |
| R1-2108046 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2108170 | Mechanisms to support MBS group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2108308 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108359 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108368 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108428 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108459 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108471 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108549 | Summary#7 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2108574 | Summary#8 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2106439 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2106624 | Discussion on mechanisms to improve reliability for RRC_CONNECTED Ues | vivo |
| R1-2106663 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2106717 | Mechanisms to improve MBS reliability for RRC_CONNECTED Ues | Spreadtrum Communications |
| R1-2106746 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2106913 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2106946 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT, CBN |
| R1-2106997 | HARQ-ACK feedback scheme for multicast of RRC_CONNECTED Ues | ETRI |
| R1-2107094 | Further Discussions on Reliability for RRC_CONNECTED UEs | FUTUREWEI |
| R1-2107138 | Discussion on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2107161 | On reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2107230 | UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2107370 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2107383 | Discussion on MBS reliability for RRC_CONNECTED UEs | Google Inc. |
| R1-2107426 | Discussion on reliability improvement | CMCC |
| R1-2107457 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2107515 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2107612 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2107764 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2107882 | Discussion on mechanisms to improve reliability for multicast for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2107951 | Reliability related discussion for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2108027 | Discussion on reliability enhancement for RRC_CONNECTED UEs | Convida Wireless |
| R1-2108171 | Mechanisms to improve reliability for RRC_CONNECTED Ues | Ericsson |
| R1-2108285 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108332 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108372 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108429 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108481 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108553 | FL summary#6 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2108641 | FL summary#7 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2106440 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2106625 | Discussion on basic functions for broadcast multicast for RRC_IDLE RRC_INACTIVE UEs | vivo |
| R1-2106664 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2106718 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | Spreadtrum Communications |
| R1-2106747 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2106821 | Considerations on MBS functions for RRC_IDLE/INACTIVE UEs | Sony |
| R1-2106914 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2106947 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | CATT, CBN |
| R1-2107095 | MBS Support for RRC IDLE/INACTIVE UEs | FUTUREWEI |
| R1-2107162 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2107165 | Search Space and DCI Design for MBS in IDLE and INACTIVE states | TCL Communication Ltd. |
| R1-2107231 | Discussion on basic functions for RRC_IDLE/RRC_INACTIVE UEs | OPPO |
| R1-2107371 | Views on group scheduling for Broadcast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2107384 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Google Inc. |
| R1-2107427 | Discussion on NR MBS in RRC_IDLE/ RRC_INACTIVE states | CMCC |
| R1-2107458 | Basic function for broadcast/multicast | LG Electronics |
| R1-2107516 | Discussion on MBS for RRC_IDLE/INACTIVE UEs | MediaTek Inc. |
| R1-2107613 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2107765 | Discussion on MBS for RRC_IDLE and RRC_INACTIVE UEs | Apple |
| R1-2107883 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | NTT DOCOMO, INC. |
| R1-2107952 | NR MBS related discussion for RRC_IDLE/RRC_INACITVE UEs | CHENGDU TD TECH LTD. |
| R1-2108028 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R1-2108172 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2108227 | Feature Lead summary #1 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2108228 | Feature Lead summary #2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2108229 | Feature Lead summary #3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2108230 | Feature Lead summary #4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2108578 | Feature Lead summary #5 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2108579 | Feature Lead summary #6 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| 8.12.4 | Other | |
| R1-2106626 | Other issues for Rel-17 MBS | vivo |
| R1-2106665 | Other Aspects for Rel-17 MBS | Nokia, Nokia Shanghai Bell |
| R1-2106748 | Consideration on potential further enhancement for MBS | ZTE |
| R1-2106948 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2107379 | Other aspects of NR Multicast | Qualcomm Incorporated |
| R1-2107459 | Other aspects for MBS | LG Electronics |
| R1-2107662 | Impact from MCCH and MTCH on broadcast reception | Huawei, HiSilicon |
| R1-2107953 | Other aspects for NR MBS | CHENGDU TD TECH LTD. |
| R1-2108173 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2108003 | Work plan for Rel17 WI on NR Dynamic spectrum sharing (DSS) | Ericsson |
| R1-2108611 | Session notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2108687 | [Post-106-e-Rel17-RRC-13] Summary of email discussion on RRC parameters for DSS | Moderator (Ericsson) |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2106472 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2106627 | Discussion on Scell scheduling Pcell | vivo |
| R1-2106721 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2106749 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2106915 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2107187 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2107277 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2107372 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2107428 | Discussion on cross-carrier scheduling from SCell to Pcell | CMCC |
| R1-2107460 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2107483 | Cross-carrier scheduling from SCell to PCell | ETRI |
| R1-2107499 | On Cross-Carrier Scheduling from sSCell to P(S)Cell | MediaTek Inc. |
| R1-2107526 | On cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2107614 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2107641 | PCell and sSCell scheduling Pcell | InterDigital, Inc. |
| R1-2107766 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2107884 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2107903 | Discussion on Cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2108004 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2108307 | Summary of Email discussion [106-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2108354 | Summary#2 of Email discussion [106-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2108476 | Summary#3 of Email discussion [106-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2108575 | Summary#4 of Email discussion [106-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2108576 | Draft LS on Cross-carrier scheduling from SCell to P(S)Cell | Moderator (Ericsson) |
| R1-2108661 | Summary#5 of Email discussion [106-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2108662 | LS on Cross-carrier scheduling from SCell to P(S)Cell | RAN1, Ericsson |
| 8.13.2 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2106473 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2106628 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2106722 | Discussion on efficient activationde-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2106750 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2106916 | Remaining Issues on Scell Activation/Deactivation | Samsung |
| R1-2107086 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2107278 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2107373 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2107527 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2107615 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2107642 | Fast SCell Activation | InterDigital, Inc. |
| R1-2107767 | On Efficient SCell Activation/Deactivation | Apple |
| R1-2107885 | Discussion on efficient activation deactivation mechanism for SCells | NTT DOCOMO, INC. |
| R1-2107904 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | Xiaomi |
| R1-2108005 | Reduced Latency SCell Activation | Ericsson |
| R1-2108047 | Efficient activation/deactivation of SCell | ASUSTeK |
| R1-2108317 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2108318 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2108380 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2108381 | Summary#4 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2108668 | Summary#5 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2108674 | Summary of email discussion [Post-106-e-Rel17-RRC-14] on efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| 8.13.3 | Other | |
| R1-2106751 | Considerations on potential further enhancements for CA | ZTE |
| R1-2107380 | Other aspects of DSS | Qualcomm Incorporated |
| R1-2107671 | Remaining issues on the efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2108006 | CRS Rate-matching enhancement for DSS | Ericsson |
| 8.14 | Study on XR Evaluations for NR (RAN1) | |
| R1-2108612 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (CMCC) |
| 8.14.1 | Traffic Model | |
| R1-2106456 | Traffic model for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2106526 | Remaining Issues of XR Traffic Model | ZTE, Sanechips |
| R1-2106629 | Remaining issues on traffic models of XR | vivo |
| R1-2106917 | Traffic Models for XR | Samsung |
| R1-2106949 | XR traffic model | CATT |
| R1-2107131 | Discussion on Traffic Model for XR/CG | China Telecom |
| R1-2107279 | Discussion on the XR traffic models for evaluation | OPPO |
| R1-2107374 | Remaining Issues on XR Traffic Models | Qualcomm Incorporated |
| R1-2107461 | Discussion on traffic models for XR evaluation | LG Electronics |
| R1-2107500 | Traffic Model for XR and CG | MediaTek Inc. |
| R1-2107534 | Discussion on UL traffic models for AR | InterDigital, Inc. |
| R1-2107616 | Traffic model for XR | Intel Corporation |
| R1-2107629 | Traffic model for XR | Ericsson |
| R1-2107768 | Remaining issues in XR traffic model | Apple |
| R1-2107886 | Discussion on traffic model for XR | NTT DOCOMO, INC. |
| R1-2107905 | Discussion on remaining issues of traffic Model for XR services | Xiaomi |
| R1-2108213 | Discussion on the XR traffic models for evaluation | OPPO |
| R1-2108500 | FL proposals for remaining issues of XR traffic model | Moderator (Qualcomm) |
| 8.14.2 | Evaluation Methodology | |
| R1-2106457 | Evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2106527 | Remaining Issues of XR Evaluation Methodology | ZTE, Sanechips |
| R1-2106630 | Remaining issues on evaluation methodologies for XR | vivo |
| R1-2106918 | Evaluation methodology and KPIs for XR | Samsung |
| R1-2106950 | Evaluation methodology and performance index for XR | CATT |
| R1-2107087 | XR evaluation methodology | FUTUREWEI |
| R1-2107280 | Discussion on the XR evaluation methodology | OPPO |
| R1-2107375 | Remaining Issues on Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2107462 | Discussion on evaluation methodologies for XR | LG Electronics |
| R1-2107501 | On Evaluation Methodology for XR and CG | MediaTek Inc. |
| R1-2107535 | Remaining Issues on XR Evaluation Methodologies | InterDigital, Inc. |
| R1-2107617 | Evaluation Methodology for XR | Intel Corporation |
| R1-2107630 | Evaluation methodology for XR | Ericsson |
| R1-2107656 | Development of the Evaluation Methodology for XR Study | Nokia, Nokia Shanghai Bell |
| R1-2107769 | Considerations on XR evaluation methodology | Apple |
| R1-2107887 | Discussion on evaluation methodology for XR | NTT DOCOMO, INC. |
| R1-2107906 | Discussion on remaining issues of evaluation methodology for XR services | Xiaomi |
| R1-2108501 | FL proposals for remaining issues of evaluation methodology for XR | Moderator (Qualcomm) |
| 8.14.3 | Initial Performance Evaluation Results | |
| R1-2106528 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2106631 | Performance evaluation results for XR | vivo |
| R1-2106951 | Evaluation results of XR performance | CATT |
| R1-2107088 | XR initial evaluations | FUTUREWEI |
| R1-2107281 | Evaluation results for XR evaluation | OPPO |
| R1-2107376 | Evaluation Results for XR Capacity and Power | Qualcomm Incorporated |
| R1-2107429 | Initial XR Evaluation Results | CMCC |
| R1-2107502 | Initial Performance and Evaluation Results for XR and CG | MediaTek Inc. |
| R1-2107536 | Performance Evaluation Results for XR | InterDigital, Inc. |
| R1-2107618 | Initial results for XR | Intel Corporation |
| R1-2107657 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2107666 | Initial evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2107694 | XR Initial Performance Results | AT&T |
| R1-2107770 | Performance evaluation on XR | Apple |
| R1-2107907 | Initial performance evaluation result for XR | Xiaomi |
| R1-2108007 | XR performance evaluation results | Ericsson |
| R1-2108100 | Initial evaluation results for XR | China Unicom |
| R1-2108202 | Initial Performance and Evaluation Results for XR and CG | MediaTek Inc. |
| R1-2108209 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2108239 | Initial results for XR | Intel Corporation |
| R1-2108251 | Evaluation Results for XR Capacity and Power | Qualcomm |
| R1-2108273 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2108314 | Summary #1 of initial performance evaluation results for XR | Moderator (vivo) |
| R1-2108377 | Evaluation results for XR evaluation | OPPO |
| R1-2108488 | XR performance evaluation results | Ericsson |
| R1-2108664 | Summary of [106-e-NR-XR-03] email discussion on XR evaluation results | Moderator (vivo) |
| R1-2108665 | Summary of XR evaluation results_RAN1-106e | Moderator (vivo) |
| 8.14.4 | Other | |
| R1-2106529 | On Capacity and Power Working Areas for XR | ZTE, Sanechips |
| R1-2106632 | Challenges and potential enhancements for XR | vivo |
| R1-2106822 | Considerations on potential enhancements for XR | Sony |
| R1-2106919 | Potential enhancements for XR | Samsung |
| R1-2106952 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2107158 | Potential enhancements of NR to support XR services | NEC |
| R1-2107282 | Discussion on the support of XR/CG service | OPPO |
| R1-2107377 | Potential Enhancements for XR | Qualcomm Incorporated |
| R1-2107537 | Discussion on potential enhancements for XR | InterDigital, Inc. |
| R1-2107631 | Discussion on enhancements for XR | Ericsson |
| R1-2107658 | Enhancements for better XR support over NR | Nokia, Nokia Shanghai Bell |
| R1-2107667 | Challenges and potential enhancements for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2107771 | Potential enhancements for XR | Apple |
| R1-2107908 | Discussion on potential enhancement for supporting XR | Xiaomi |
| 8.15 | NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2108215 | LTE_NBIOT_eMTC_NTN work plan | Rapporteur (MediaTek) |
| R1-2108613 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| R1-2108671 | Summary of [Post-106-e-Rel17-RRC-15] IoT over NTN | Moderator (MediaTek) |
| R1-2108672 | List of IoT over NTN Rel-17 RRC parameters | Moderator (MediaTek) |
| 8.15.1 | Enhancements to time and frequency synchronization | |
| R1-2106485 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2106633 | Discussion on time and frequency synchronization enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2106719 | Discussion on enhancements to time and frequency synchronization for IOT NTN | Spreadtrum Communications |
| R1-2106760 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2106823 | Enhancement to time synchronisation for IoT-NTN | Sony |
| R1-2106920 | On enhancements to time and frequency synchronization | Samsung |
| R1-2106953 | Time and frequency synchronization enhancement for IoT over NTN | CATT |
| R1-2107018 | Enhancements to time and frequency synchronization | NEC |
| R1-2107047 | On enhancements to time and frequency synchronization | Nordic Semiconductor ASA |
| R1-2107067 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2107069 | Summary #1 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2107173 | Enhancement to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2107247 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2107291 | Enhancements to time and frequency synchronization to NB-IoT NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107430 | Enhancements on time and frequency synchronization for IoT NTN | CMCC |
| R1-2107619 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2107659 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2107772 | On Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2107779 | Discussion on synchronization for IoT-NTN | ZTE |
| R1-2107909 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2107942 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2108038 | On Time/Frequency Synchronization for IoT NTN | InterDigital, Inc. |
| R1-2108095 | Application scenarios of IoT in NTN | GDCNI |
| R1-2108338 | Summary #2 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2108348 | Summary #3 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2108430 | Summary #4 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2108516 | Summary #5 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2108558 | Summary #6 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2108640 | Summary #7 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| 8.15.2 | Timing relationship enhancements | |
| R1-2106486 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2106634 | Discussion on timing relationship enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2106720 | Discussion on timing relationship enhancements for IOT NTN | Spreadtrum Communications |
| R1-2106761 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2106824 | Timing relationship enhancements for IoT-NTN | Sony |
| R1-2106921 | Timing relationship enhancements | Samsung |
| R1-2106954 | Timing relationship enhancement for IoT over NTN | CATT |
| R1-2107048 | On timing relationship enhancements | Nordic Semiconductor ASA |
| R1-2107068 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2107174 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2107248 | Discussion on timing relationship enhancements | OPPO |
| R1-2107292 | Timing relationship enhancements to NB-IoT NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2107431 | Discussion on timing relationship enhancements for IoT NTN | CMCC |
| R1-2107620 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2107660 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2107773 | On Timing Relationship Enhancements in IoT NTN | Apple |
| R1-2107780 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2107910 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2107943 | Timing Relationship for IoT NTN | Lenovo, Motorola Mobility |
| R1-2108039 | On Timing relationship enhancement for IoT NTN | InterDigital, Inc. |
| R1-2108312 | FL summary 1 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2108350 | FL summary 2 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2108397 | FL summary 3 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2108493 | FL summary 4 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2108519 | FL summary 5 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2108637 | FL summary 6 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| 8.15.3 | Other | |
| R1-2106776 | On LEO satellite flyover timing and discontinuous coverage | Eutelsat S.A. |
| R1-2107175 | Discussion on other aspects for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2107661 | Mobile IoT in the 5G future – NB-IoT and eMTC for NTN | Ericsson |
| R1-2107676 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| R1-2107781 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2107911 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| 8.16 | New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast | |
| R1-2106555 | TEI-17 proposal on NR codeword mapping | ZTE |
| R1-2106762 | Work Plan for New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast | Qualcomm Incorporated, EBU |
| R1-2108626 | Session notes for 8.16 (New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Ericsson) |
| R1-2108688 | [Post-106-e-Rel17-RRC-16] Summary of email discussion on RRC parameters for LTE based 5G Terrestrial Broadcast | Moderator (Qualcomm) |
| 8.16.1 | PMCH allocation of 6/7/8 MHz and corresponding MBSFN reference signals | |
| R1-2106560 | On PMCH allocation of 6/7/8 MHz and corresponding reference signals | Huawei, HiSilicon |
| R1-2106752 | Discussion on PMCH allocation and corresponding MBSFN reference signals | ZTE |
| R1-2106763 | PMCH allocation of 6/7/8MHz | Qualcomm Incorporated |
| R1-2108211 | Feature lead summary on New bands and bandwidth allocation for LTE based 5G terrestrial broadcast | Moderator (Qualcomm Incorporated) |
| R1-2108324 | Feature lead summary#2 on New bands and bandwidth allocation for LTE based 5G terrestrial broadcast | Moderator (Qualcomm Incorporated) |
| R1-2108360 | Feature lead summary#3 on New bands and bandwidth allocation for LTE based 5G terrestrial broadcast | Moderator (Qualcomm Incorporated) |
| 8.16.2 | Other | |
| R1-2106753 | Considerations on bandwidth changing in MBSFN subframe for 15KHz subcarrier spacing | ZTE |
| R1-2107685 | Numerologies supported for MBMS-dedicated cell | Huawei, HiSilicon |
| 8.17 | Other | |
| R1-2106494 | Enhancements on the scheduling of PUSCH over multiple slots | Huawei, HiSilicon, China Unicom |
| R1-2106562 | TEI-17 proposal on NR codeword mapping | ZTE |
| R1-2106635 | Rel-17 TEI proposals | vivo |
| R1-2106955 | Rel-17 TEI proposals on SSB resource for RLM and HARQ-ACK feedback enhancements for TDD-FDD CA | CATT |
| R1-2107024 | TEI-17 proposal targeting the false PMI reporting issue | Ericsson |
| R1-2107212 | Support of default power control parameter per TRP | OPPO, ZTE |
| R1-2107378 | Rel-17 TEI Topics | Qualcomm Incorporated |
| R1-2107569 | Rel-17 TEI proposal for mitigating half-duplex issue in NR V2X groupcast NACK-only case regime | Intel Corporation, Qualcomm Inc., NTT DOCOMO, Ericsson |
| R1-2107888 | NR positioning support for TA-based positioning in E-CID (TEI) | NTT DOCOMO INC., Ericsson, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT |
| R1-2107889 | Summary on Rel-17 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2108349 | Rel-17 TEI proposal for mitigating half-duplex issue in NR V2X groupcast NACK-only case regime | Intel Corporation, Qualcomm Inc., NTT DOCOMO, Ericsson, Bosch |