| TDoc | Title | Source |
|---|---|---|
| R1-2104150 | Draft Agenda of RAN1#105-e meeting | RAN1 Chair |
| R1-2104152 | RAN1#105-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2104153 | Additional Guidelines for RAN1#105-e-Meeting Management | RAN1 Chair |
| TDoc | Title | Source |
|---|---|---|
| R1-2104151 | Report of RAN1#104bis-e meeting | ETSI MCC |
| TDoc | Title | Source |
|---|---|---|
| R1-2104154 | LS on Media-Related Services and Requirements | SA4, Qualcomm |
| R1-2104155 | LS on PDB for new 5QI | SA2, Ericsson |
| R1-2104156 | LS on Time Synchronization assistance parameters | SA2, Nokia |
| R1-2104157 | Reply LS on TCI state indication at Direct SCell activation | RAN2, MediaTek |
| R1-2104158 | Reply LS on timing of neighbor cell RSS-based measurements | RAN2, Qualcomm |
| R1-2104159 | Reply LS related to RSS based RSRQ for LTE-MTC | RAN2, Huawei |
| R1-2104160 | Reply LS to RAN1 on SL HARQ-ACK reporting to the gNB | RAN2, Huawei |
| R1-2104161 | LS on RI bit width for Cat5 UE in EN-DC mode | RAN2, Nokia |
| R1-2104162 | LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities | RAN2, ZTE |
| R1-2104163 | LS to RAN1 on random value generation for RMTC-SubframeOffset | RAN2, Apple |
| R1-2104164 | LS on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | RAN2, Ericsson |
| R1-2104165 | LS on broadcast session delivery and MCCH design | RAN2, Huawei |
| R1-2104166 | Reply LS on Introduction of DL 1024QAM for NR | RAN2, Ericsson |
| R1-2104167 | Response LS on Scheduling Location in Advance to reduce Latency | RAN2, Qualcomm |
| R1-2104168 | Reply LS on PUCCH and PUSCH repetition | RAN4, Qualcomm |
| R1-2104169 | Second reply LS on Beam switching gaps for Multi-TRP UL transmission | RAN4, Nokia |
| R1-2104170 | Reply LS on temporary RS for efficient SCell activation in NR CA | RAN4, Huawei |
| R1-2104171 | Reply LS on UE transmit timing error | RAN4, Huawei |
| R1-2104172 | LS reply on NTN UL time and frequency synchronization requirements | RAN4, CATT |
| R1-2104173 | Reply LS on maximum/minimum channel bandwidths and channelization for NR operation in 52.6 to 71 GHz | RAN4, Intel |
| R1-2104174 | Reply LS on Introduction of Cell Grouping UE capability for NR-DC | RAN4, Qualcomm |
| R1-2104175 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2104226 | On RI bit width for Cat5 UE in EN-DC mode | Nokia, Nokia Shanghai Bell |
| R1-2104229 | Reply LS on UE Sub-grouping for Paging Enhancement | RAN2, MediaTek |
| R1-2104230 | LS on TA pre-compensation | RAN2, OPPO |
| R1-2104231 | Reply LS to RAN4 on the capability of transparent TxD | RAN2, vivo |
| R1-2104298 | [Draft] Reply LS on SL DRX design | Nokia, Nokia Shanghai Bell |
| R1-2104319 | Discussion on the Intra-band and Inter-band (NG)EN-DC NE-DC Capabilities | ZTE |
| R1-2104320 | [DRAFT] Reply LS on the Intra-band and Inter-band (NG)EN-DC NE-DC Capabilities | ZTE |
| R1-2104465 | Discussion on LS from RAN2 on SL DRX design | CATT, GOHIGH |
| R1-2104466 | Discussion on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities | CATT |
| R1-2104467 | Discussion on RAN2 Reply LS on UE Sub-grouping for Paging Enhancement | CATT |
| R1-2104559 | LS on R16 V2X for PUCCH reporting and for minimum time gap | RAN2, OPPO |
| R1-2104576 | [DRAFT] Reply LS on broadcast session delivery and MCCH design | ZTE |
| R1-2104578 | Draft reply LS on RI bit width for Cat5 UE in EN-DC | ZTE |
| R1-2104579 | Draft reply LS on fallback applicability for FeatureSetDownLinkPerCC capability fields | ZTE |
| R1-2104597 | Discussion on RAN2 LS on broadcast session delivery and MCCH design | CMCC |
| R1-2104640 | Draft reply LS on Cat-5 with EN-DC | Qualcomm Incorporated |
| R1-2104641 | Draft reply to RAN2 on minimum time gap | Qualcomm Incorporated |
| R1-2104642 | Draft LS reply to RAN2 on UE Sub-grouping for Paging Enhancement | Qualcomm Incorporated |
| R1-2104643 | Draft reply LS to SA2 on Scheduling Location in Advance | Qualcomm Incorporated |
| R1-2104709 | Discussion on RAN2 reply LS on RSS based RSRQ | ZTE |
| R1-2104719 | Discussion on RAN2 LS on DRX impact | Nokia, Nokia Shanghai Bell |
| R1-2104726 | Discussion on SA2 LS on new 5QI for NTN | Ericsson |
| R1-2104749 | Draft reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | OPPO |
| R1-2104753 | Discussion on PUCCH reporting and for minimum time gap | OPPO |
| R1-2104754 | Draft reply LS on R16 V2X for PUCCH reporting and for minimum time gap | OPPO |
| R1-2104757 | Discussion on SL-DRX working assumption from RAN2 | OPPO |
| R1-2104758 | Draft reply LS to RAN2 on SL DRX design | OPPO |
| R1-2104774 | Discussion on LS on PDB for new 5Q | OPPO |
| R1-2104775 | Discussion on LS on TA pre-compensation | OPPO |
| R1-2104818 | Discussion on RSS-based measurements | Qualcomm Incorporated |
| R1-2104838 | Draft reply LS on RMTC-subframeoffset | ZTE |
| R1-2104839 | Discussion on the random value generation for RMTC-subframeoffset | ZTE, Sanechips |
| R1-2104843 | Discussion on the LS from RAN2 on PUCCH reporting and for minimum time gap | CATT, GOHIGH |
| R1-2104883 | Draft reply LS on R16 V2X for PUCCH reporting and for minimum time gap | Intel Corporation |
| R1-2104996 | Draft reply LS on R16 V2X for PUCCH reporting and for minimum time gap | Intel Corporation |
| R1-2105198 | Discussion on LS on TA pre-compensation | ZTE |
| R1-2105199 | Discussion on LS on PDB for new 5QI | ZTE |
| R1-2105279 | Discussion on the random value generation for RMTC-SubframeOffset | Samsung |
| R1-2105280 | Draft reply LS on RI bit width for Cat5 UE in EN-DC mode | Samsung |
| R1-2105281 | Draft reply LS on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | Samsung |
| R1-2105282 | Draft reply LS on R16 V2X for PUCCH reporting and for minimum time gap | Samsung |
| R1-2105385 | [Draft] Reply LS on UE Sub-grouping for Paging Enhancement | MediaTek Inc. |
| R1-2105414 | Discussion on RAN2 LS on random value generation for RMTC-SubframeOffset | LG Electronics |
| R1-2105445 | Draft reply LS on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | vivo |
| R1-2105446 | Draft reply LS on RI bit width for Cat5 UE in EN-DC mode | vivo |
| R1-2105447 | Discussion on RAN4 Reply LS on PUCCH and PUSCH repetition | vivo |
| R1-2105448 | Draft Reply LS on SL DRX design | vivo |
| R1-2105449 | Draft Reply LS on R16 V2X for PUCCH reporting and for minimum time gap | vivo |
| R1-2105450 | Draft Reply LS on random value generation for RMTC-SubframeOffset | vivo |
| R1-2105451 | Draft reply LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities | vivo |
| R1-2105481 | Draft reply LS on TA pre-compensation | LG Electronics |
| R1-2105607 | [Draft]Reply LS to SA4 on Status Update on XR Traffic | ZTE |
| R1-2105608 | [draft]Reply LS on sidelink DRX | ZTE, Sanechips |
| R1-2105609 | Further consideration of SL DRX | ZTE, Sanechips |
| R1-2105610 | About the LS on Status Update on XR Traffic Model | ZTE, Sanechips |
| R1-2105649 | Discussion on LS about paging sub-grouping | ZTE, Sanechips |
| R1-2105811 | Discussion regarding LS reply on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | Ericsson |
| R1-2105833 | Discussion of SA4 input on XR traffic | Ericsson |
| R1-2105898 | [Draft] LS on PUCCH reporting and minimum time gap for V2X | Ericsson |
| R1-2105899 | Discussion on RAN2 LS on PUCCH reporting and for minimum time gap for V2X | Ericsson |
| R1-2105922 | Discussion on HARQ feedback reporting and minimum time gap | Huawei, HiSilicon |
| R1-2105923 | Discussion on RAN2 LS on DRX impact | Huawei, HiSilicon |
| R1-2105924 | Discussion on LS on Status Update on XR Traffic | Huawei, HiSilicon |
| R1-2105927 | Discussion on LS on broadcast session delivery and MCCH design | Huawei, HiSilicon, CBN |
| R1-2105930 | Discusion on PDB for new 5QI | Huawei, HiSilicon |
| R1-2105931 | Discussion on TA pre-compensation | Huawei, HiSilicon |
| R1-2105932 | Discussion on EN-DC/NE-DC UE capabilities | Huawei, HiSilicon |
| R1-2105933 | Discussion on random value generation for rmtc-SubframeOffset | Huawei, HiSilicon |
| R1-2105934 | Discussion on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | Huawei, HiSilicon |
| R1-2105935 | Discussion on RI bit width for Cat5 UE in EN-DC mode | Huawei, HiSilicon |
| R1-2105937 | Discussion on scheduling location in advance to reduce latency | Huawei, HiSilicon |
| R1-2105941 | Discussion on RSS based RSRQ for LTE-MTC | Huawei, HiSilicon |
| R1-2105948 | [Draft] LS response on New Standardized 5QIs for 5G-AIS | Qualcomm Incorporated |
| R1-2105984 | RAN1#105-e preparation phase on LSs | RAN1 Chair |
| R1-2106107 | [105-e-AI5-LS-01] Discussion summary on reply LS to R1-2104161 | Moderator (Nokia) |
| R1-2106108 | Reply LS on RI bit width for Cat5 UE in EN-DC mode | RAN1, Nokia |
| R1-2106180 | Summary of Email Discussion [105-e-AI5-LS-02] | Moderator (ZTE) |
| R1-2106286 | Reply LS on R16 V2X for PUCCH reporting and for minimum time gap | RAN1, OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2104245 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| R1-2104318 | Discussion on Rel-17 UL Tx Switching | ZTE |
| R1-2104468 | Discussion on R17 enhancements for UL TX switching | CATT |
| R1-2104598 | Discussion on Rel-17 UL Tx Switching | CMCC |
| R1-2104644 | Discussion on Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2104652 | Discussion on Rel-17 UL Tx switching | Qualcomm Incorporated |
| R1-2104737 | Dsicussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2104845 | Discussion on Rel-17 uplink Tx switching | China Telecom |
| R1-2105452 | Discussion on Rel-17 Tx switching enhancements | vivo |
| R1-2106150 | [105-e-NR-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104227 | On physical layer aspects of small data transmission | Nokia, Nokia Shanghai Bell |
| R1-2104282 | Physical layer aspects of CG-SDT | Huawei, HiSilicon |
| R1-2104408 | Discussion on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2104469 | Remaining issues on small data transmission | CATT |
| R1-2104798 | Discussion on NR small data transmissions in INACTIVE state | OPPO |
| R1-2104840 | Discussion on the remaining physical layer issues of small data transmission | ZTE, Sanechips |
| R1-2104884 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2104940 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2104997 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2105073 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2105283 | Discussion on physical layer aspects for NR small data transmissions in INACTIVE state | Samsung |
| R1-2105415 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2105453 | Discussion on RAN1 impacts for small data transmisison | vivo |
| R1-2105471 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2105508 | Discussion on RAN1 aspects for NR small data transmissions in INACTIVE state | L.M. Ericsson Limited |
| R1-2106129 | Summary of the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2106130 | Draft LS on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2106309 | LS on Beam correspondence with Small Data Transmission in Inactive State | RAN1, Nokia |
| R1-2106335 | LS on the physical layer aspects of small data transmission | RAN1, ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2104575 | Correction for MBSFN reference signal mapping to resource elements for 1.25 kHz | ZTE |
| R1-2105265 | Correction on DCI format N0 when scrambled by SPS C-RNTI | ZTE |
| R1-2105266 | Correction on UL index for LTE-M | ZTE |
| R1-2105398 | Clarification on NPUSCH postponement for NB-IoT | ZTE, Sanechips, Lenovo, Motorola Mobility |
| R1-2105940 | Discussion on NPUSCH postponement when overlapping with NPRACH | Huawei, HiSilicon |
| R1-2105953 | Correction on DCI format N0 when scrambled by SPS C-RNTI | ZTE |
| R1-2105954 | Correction on UL index for LTE-M | ZTE |
| R1-2106179 | Summary of Email Discussion [105-e-LTE-6.1CRs-01] | Moderator (ZTE) |
| R1-2106220 | Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) | Ad-Hoc Chair (Ericsson) |
| R1-2106297 | Correction of erroneous references | FUTUREWEI, ZTE |
| R1-2106299 | Summary of [105-e-LTE-6.1CRs-03] Email discussion/approval on R1-2105398 and R1-2105940 | Moderator (ZTE) |
| R1-2106342 | Feature lead summary on [105-e-LTE-6.1CRs-02] | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2106221 | Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2105267 | Clarification on UE procedure for uplink MTB scheduling in TDD | ZTE |
| R1-2105268 | Discussion on UE procedure for uplink MTB scheduling in TDD | ZTE |
| R1-2105998 | FL summary on clarification of UE procedure for UL multi-TB scheduling in TDD for Rel-16 LTE-MTC | Moderator (Ericsson) |
| R1-2106214 | Feature lead summary on 105-e-LTE-eMTC5-01 | Moderator (Huawei) |
| R1-2106215 | Reply LS on RSS based RSRQ for LTE-MTC | RAN1, Huawei |
| R1-2106306 | Clarification on UE procedure for uplink MTB scheduling in TDD | Moderator (Ericsson), ZTE, Sanechips, Ericsson, Huawei, HiSilicon, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R1-2105269 | Correction on DMRS cyclic shift for PUR in NB-IoT | ZTE |
| R1-2106196 | Correction on DMRS cyclic shift for PUR in NB-IoT | Moderator (Huawei), Huawei, HiSilicon, Ericsson, ZTE, Sanechips |
| R1-2106203 | Feature lead summary #1 on [105-e-LTE-NB_IoTenh3-01] | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104574 | Correction for 0.37kHz SCS | ZTE |
| R1-2106222 | Session notes for 6.2.4 (Maintenance of LTE-based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Ericsson) |
| R1-2106355 | Correction for 0.37kHz SCS | Moderator (Qualcomm), ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2104299 | Remaining issues with PUSCH skipping (without LCH and PHY prioritization) (Rel-16) | Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2104300 | Draft CR on PUSCH skipping with repetition (Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2104316 | Discussion on UL skipping for PUSCH | ZTE |
| R1-2104317 | Correction on multi-slot PUSCH transmission | ZTE |
| R1-2104409 | Discussion on UL skipping for PUSCH in Rel-16 | Spreadtrum Communications |
| R1-2104470 | Discussion on overlapping between positive SR and PUSCH without UL-SCH | CATT |
| R1-2104471 | Discussion on remaining issue of PUSCH skipping | CATT |
| R1-2104472 | Draft CR on overlapping between PUSCH transmission and SRS transmission | CATT |
| R1-2104580 | Discussion on SRS carrier switching | ZTE |
| R1-2104581 | Draft CR on SRS carrier switching | ZTE |
| R1-2104645 | Draft CR on Type-1 HARQ-ACK for PDSCH repetition with different DL and UL SCSs | Qualcomm Incorporated |
| R1-2104646 | Discussion on PUSCH skipping | Qualcomm Incorporated |
| R1-2104647 | Discussion on SRS carrier switch | Qualcomm Incorporated |
| R1-2104809 | Discussion on PUSCH skipping with UCI overlapping | OPPO |
| R1-2104810 | Draft CR on PUCCH repetition | OPPO |
| R1-2104885 | PDSCH processing time per Capability 2 and DCI format 1_0 | Intel Corporation |
| R1-2104886 | On UL skipping and PUSCH repetitions | Intel Corporation |
| R1-2104941 | PDSCH processing time per Capability 2 and DCI format 1_0 | Intel Corporation |
| R1-2104942 | On UL skipping and PUSCH repetitions | Intel Corporation |
| R1-2104998 | PDSCH processing time per Capability 2 and DCI format 1_0 | Intel Corporation |
| R1-2104999 | On UL skipping and PUSCH repetitions | Intel Corporation |
| R1-2105074 | Timeline Considerations for SRS Carrier Switching and Dropping Procedure in Rel-16 | Apple |
| R1-2105075 | Correction for HARQ-ACK timing in Rel-16 | Apple, Ericsson |
| R1-2105076 | Discussions on PUSCH skipping in Rel-16 | Apple |
| R1-2105077 | Correction on UL cancellation due to DCI format 2_0 | Apple |
| R1-2105078 | Correction on UL cancellation due to DCI format 2_0 | Apple |
| R1-2105079 | Discussions on PUSCH UCI Multiplexing without HARQ-ACK PUCCH in Rel-15 | Apple |
| R1-2105278 | DRX interaction with CPU occupancy | Nokia |
| R1-2105284 | Correction on power control for TS 38.213 | Samsung |
| R1-2105349 | Discussion on DRX interaction with CPU occupancy | Nokia |
| R1-2105389 | Clarification on PHR Report for SRS Carrier | MediaTek Inc. |
| R1-2105390 | Clarification on HARQ-ACK Information Feedback without Receiving DL assignment/PDSCH | MediaTek Inc. |
| R1-2105391 | Clarification on PUSCH with UCI Only and DMRS Multiplexing | MediaTek Inc. |
| R1-2105454 | Discussion on CSI-RS multiplexing with PDSCH scheduled by PDCCH with CRC scrambled by P-RNTI and SI-RNTI | vivo |
| R1-2105455 | Draft 38.214 CR on reference correction for PDSCH EPRE to CSIRS EPRE assumption | vivo |
| R1-2105456 | Draft 38.212 CR on spreading factor for PUCCH format 4 | vivo |
| R1-2105457 | Discussion on CSI-RS Resource counting for UE feature 2-33 | vivo |
| R1-2105458 | Discussion on PUSCH skipping with overlapping UCI on PUCCH in Rel-16 | vivo |
| R1-2105459 | Correction on 38.213 for UL skipping with PUSCH repetitions in Rel-16 | vivo |
| R1-2105520 | Discussion on UL skipping | Huawei, HiSilicon |
| R1-2105539 | Correction on enabling configuration of time restriction over L1-RSRP and CSI measurement | Huawei, HiSilicon |
| R1-2105587 | Discussion on PUSCH with ULSkipping and repetition | Ericsson |
| R1-2105625 | Correction on channel properties assumption of UL transmission | Sharp |
| R1-2105730 | Discussion on UL skipping for PUSCH repetition | NTT DOCOMO INC. |
| R1-2105741 | Clarification on back-to-back PUSCHs scheduling restriction in Rel-15 | MediaTek Inc. |
| R1-2105803 | Discussion on PDCCH monitoring in overlapping CORESETs | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2105835 | UE feature for 2-port CSI-RS | Ericsson |
| R1-2105919 | Correction on PDCCH blind detection capability for CA in TS38.213 | Huawei, HiSilicon |
| R1-2105926 | Correction on the MR-DC Uplink Power Control in 38.213 | Huawei, HiSilicon |
| R1-2105936 | Correction on prioritization rules of SRS carrier switching | Huawei, HiSilicon |
| R1-2105938 | Correction of initial DL BWP configuration | Huawei, HiSilicon |
| R1-2105964 | PDSCH processing time per Capability 2 and DCI format 1_0 | Intel Corporation |
| R1-2105972 | RAN1#105-e preparation phase initial summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2105980 | RAN1#105-e preparation phase final summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2106026 | Summary of discussion on PDSCH processing time per Capability 2 and DCI format 1_0 | Moderator (Intel) |
| R1-2106100 | Summary of [105-e-NR-7.1CRs-12] Issue#26 SRS carrier switching | Moderator (ZTE) |
| R1-2106132 | Summary on editorial spec changes of [105-e-NR-7.1CRs-14] | Moderator (Samsung) |
| R1-2106178 | Summary for [105-e-NR-7.1CRs-04] Issue#9: Clarification on PHR Report for SRS Carrier | Moderator (MediaTek) |
| R1-2106209 | Summary on [105-e-NR-7.1CRs-15] | Moderator (Samsung) |
| R1-2106223 | Session notes for 7.1 (Maintenance of Release 15 NR) | Ad-hoc Chair (Samsung) |
| R1-2106260 | Correction on enabling configuration of time restriction over L1-RSRP and CSI measurement | Huawei, HiSilicon |
| R1-2106261 | Correction on enabling configuration of time restriction over L1-RSRP and CSI measurement | Huawei, HiSilicon |
| R1-2106262 | Summary of [105-e-NR-7.1CRs-05] | Moderator (Huawei) |
| R1-2106266 | Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek) |
| R1-2106267 | Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek) |
| R1-2106268 | Summary of [105-e-NR-7.1CRs-07] Clarification on back-to-back PUSCHs scheduling restriction | Moderator (MediaTek) |
| R1-2106280 | Correction on channel properties assumption of UL transmission | Sharp |
| R1-2106281 | Correction on channel properties assumption of UL transmission | Sharp |
| R1-2106295 | Summary of [105-e-NR-7.1CRs-08]: Correction on PDCCH blind detection capability for CA in TS38.213 | Moderator (Huawei, HiSilicon) |
| R1-2106296 | Summary of email discussion [105-e-NR-7.1CRs-06]: Correction on channel properties assumption of UL transmission | Moderator (Sharp) |
| R1-2106298 | Summary of [105-e-NR-7.1CRs-10] Draft 38.212 CR on spreading factor for PUCCH format 4 | Moderator (vivo) |
| R1-2106300 | Summary of email discussion [105-e-NR-7.1CRs-09] on the correction for UL cancellation due to DCI format 2_0 | Moderator (Apple Inc.) |
| R1-2106301 | Summary of email discussion [105-e-NR-7.1CRs-13] on the correction for HARQ-ACK timing in Rel-16 | Moderator (Apple Inc.) |
| R1-2106302 | Correction on UL cancellation due to DCI format 2_0 | Moderator (Apple Inc.), Qualcomm |
| R1-2106303 | Correction on UL cancellation due to DCI format 2_0 | Moderator (Apple Inc.), Qualcomm, CATT |
| R1-2106317 | Summary for [105-e-NR-7.1CRs-02] Discussions on PUSCH UCI Multiplexing without HARQ-ACK PUCCH | Moderator (Apple) |
| R1-2106349 | Rel-15 editorial corrections for TS 38.213 | Samsung |
| R1-2106350 | Rel-15 editorial corrections for TS 38.213 (mirrored to Rel-16) | Samsung |
| R1-2106352 | Rel-15 editorial corrections for TS 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2106353 | Rel-15 editorial corrections for TS 38.214 (mirrored to Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2106369 | Summary of discussion on remaining issues on UL skipping for PUSCH (Rel16) | Moderator (vivo) |
| R1-2106370 | LS on UL skipping for PUSCH in Rel-16 | RAN1, vivo |
| TDoc | Title | Source |
|---|---|---|
| R1-2105395 | Editorial corrections for 38.214 | Nokia |
| R1-2106347 | Alignment of notation | Ericsson |
| R1-2106348 | Alignment CR for TS 38.212 | Huawei |
| R1-2106351 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2106354 | Rel-16 editorial corrections for TS 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2106373 | Alignment CR for TS 38.212 | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2104474 | Correction on higher layer parameter for MsgA PUSCH DMRS | CATT |
| R1-2105507 | Discussion on corrections for 2-step RACH | L.M. Ericsson Limited |
| R1-2105745 | FL summary on the maintenance of 2-step RACH | Moderator (ZTE) |
| R1-2106127 | Summary of email discussion for [105-e-NR-2step-RACH-01] | Moderator (ZTE) |
| R1-2106128 | Draft LS on the description of RRC parameter p0-AlphaSets | Moderator (ZTE) |
| R1-2106168 | LS on the description of RRC parameter p0-AlphaSets | RAN1, ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2104271 | Maintenance on channel access and HARQ procedures for NR Unlicensed | Huawei, HiSilicon |
| R1-2104272 | Maintenance on DL signals and channels for NR Unlicensed | Huawei, HiSilicon |
| R1-2104458 | Corrections related to HARQ | Ericsson |
| R1-2104459 | Discussion on LS from RAN2 on random value generation for RMTC-SubframeOffset | Ericsson |
| R1-2104476 | Discussion on enhanced dynamic HARQ-ACK codebook for secondary PUCCH group | CATT |
| R1-2104648 | Invalid SSB in FBE | Qualcomm Incorporated |
| R1-2104763 | Discussion on the remaining issues with shared spectrum operation determination | OPPO |
| R1-2104764 | Discussion on the remaining issues of HARQ enhancements | OPPO |
| R1-2104831 | Discussion on the UE behavior of CSI-RS report during SCell activation | ZTE, Sanechips |
| R1-2104832 | Maintenance of channel access for NR-U | ZTE, Sanechips |
| R1-2105071 | Correction on joint search space set group switching across multiple cells | DENSO CORPORATION |
| R1-2105080 | Clarification on NR-U RRM measurement operation | Apple |
| R1-2105271 | Discussion on RAN2 LS on random value generation for RMTC-SubframeOffset | Nokia, Nokia Shanghai Bell |
| R1-2105416 | Discussion on RAN4 LS on measuring CSI-RS during SCell activation | LG Electronics |
| R1-2105460 | TP on frequency hopping for NR-U configured grant | vivo |
| R1-2105461 | Maintenance on HARQ operation for NR-U | vivo |
| R1-2105753 | Correction of higher layer parameter name for NR-U | ITRI |
| R1-2105805 | Initial UL BWP size restriction for NR-U | Sharp, LG Electronics |
| R1-2105942 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2105960 | Feature lead summary for Maintenance of UL Signals and Channels | Moderator (Ericsson) |
| R1-2105985 | Preparation phase email discussion summary for Rel.16 NR-U maintenance | Moderator (Qualcomm) |
| R1-2106111 | FL Summary for discussion [105-e-NR-NRU-01] on measurement during SCell activation | Moderator (Lenovo) |
| R1-2106118 | FL Summary for [105-e-NR-NRU-02] Email discussion/approval | Moderator (Ericsson) |
| R1-2106123 | Feature Lead summary#1 for NRU RRM Operation | Moderator (Apple) |
| R1-2106124 | Feature Lead summary#2 for NRU RRM Operation | Moderator (Apple) |
| R1-2106204 | Feature lead summary on NR-U HARQ maintenance | Moderator (Huawei) |
| R1-2106205 | LS on correction to Rel-16 HARQ description in TS38.300 | RAN1, Huawei |
| R1-2106206 | Correction on HARQ-ACK codebook RRC parameter | Moderator (Huawei), vivo, Lenovo, Motorola Mobility |
| R1-2106207 | Correction on HARQ-ACK codebook RRC parameter | Moderator (Huawei) |
| R1-2106224 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| R1-2106252 | Initial UL BWP size restriction for NR-U | Moderator (Ericsson), Sharp, LG Electronics |
| R1-2106264 | Reply LS on random value generation for RMTC-SubframeOffset | RAN1, Apple |
| R1-2106314 | FL summary for channel access procedures for NR-U | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104194 | TP to address infinite loop due to excessive resource exclusion for Rel. 16 V2X | FUTUREWEI |
| R1-2104235 | Remaining issues for sidelink physical layer procedure | Huawei, HiSilicon |
| R1-2104477 | Discussion and TP on Mode1 resource allocation | CATT, GOHIGH |
| R1-2104478 | Correction on SL HARQ-ACK report piggybacked on PUSCH | CATT, GOHIGH |
| R1-2104649 | Remaining Issues in physical layer procedure | Qualcomm Incorporated |
| R1-2104750 | Remaining open issues and corrections for mode 1 RA | OPPO |
| R1-2104751 | Discusssion on TPs for skipping step 5 in mode 2 RA | OPPO |
| R1-2104752 | Remaining open issues and corrections for physical layer procedure | OPPO |
| R1-2104887 | Correction to sidelink resource identification procedure to prevent infinite loop issue – implementation of the agreement from [104b-e-NR-5G_V2X-03] | Intel Corporation |
| R1-2104890 | Correction to PSFCH reception procedure for NACK-only case to mitigate half-duplex issue | Intel Corporation |
| R1-2104943 | Correction to sidelink resource identification procedure to prevent infinite loop issue – implementation of the agreement from [104b-e-NR-5G_V2X-03] | Intel Corporation |
| R1-2105000 | Correction to sidelink resource identification procedure to prevent infinite loop issue – implementation of the agreement from [104b-e-NR-5G_V2X-03] | Intel Corporation |
| R1-2105056 | Maintenance for mode-1 resource allocation for NR sidelink | Fujitsu |
| R1-2105057 | Maintenance for physical layer procedures for NR sidelink | Fujitsu |
| R1-2105081 | On Remaining Issue of Mode 2 Resource Allocation | Apple |
| R1-2105082 | Maintenance of Sidelink Physical Layer Procedure | Apple |
| R1-2105201 | Discussion on essential corrections in physical layer procedure | LG Electronics |
| R1-2105202 | Discussion on essential corrections in resource allocation procedure | LG Electronics |
| R1-2105210 | Corrections for transmitting sidelink reference signals in TS 38.214 | ETRI |
| R1-2105232 | Corrections for transmitting sidelink reference signals in TS 38.214 | ETRI |
| R1-2105251 | Remaining issues on physical layer structure | NEC |
| R1-2105252 | Remaining issues on resource allocation mode 2 | NEC |
| R1-2105462 | Maintenance on NR sidelink mode-1 resource allocation mechanism | vivo |
| R1-2105463 | Maintenance on NR sidelink mode-2 resource allocation mechanism | vivo |
| R1-2105464 | Maintenance on NR sidelink synchronization and procedure | vivo |
| R1-2105611 | Remaining issues on mode 1 | ZTE, Sanechips |
| R1-2105612 | Remaining issues on mode 2 | ZTE, Sanechips |
| R1-2105613 | Miscellaneous corrections of TS38.212_214 | ZTE, Sanechips |
| R1-2105626 | Remaining issues on physical layer structure for NR sidelink | Sharp |
| R1-2105627 | Remaining issues on resource allocation for NR sidelink | Sharp |
| R1-2105628 | Remaining issues on synchronization mechanism and QoS management for NR sidelink | Sharp |
| R1-2105680 | Maintenance for resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2105681 | Maintenance for sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2105740 | Remaining issues on resource allocation mode-1 and sidelink procedure | ASUSTeK |
| R1-2105841 | Remaining issues on sidelink mode 2 | ASUSTeK |
| R1-2105895 | Corrections to SL procedures | Ericsson |
| R1-2105896 | Corrections to Mode 1 | Ericsson |
| R1-2105897 | Condition to stop the infinite loop for Mode 2 RA | Ericsson |
| R1-2105920 | Correction on resource exclusion for other TBs | Huawei, HiSilicon |
| R1-2105921 | Correction on PSSCH-DMRS time-domain OCC | Huawei, HiSilicon |
| R1-2105943 | Maintenance for Resource allocation for sidelink - Mode 1 | Nokia, Nokia Shanghai Bell |
| R1-2105944 | Maintenance for Resource allocation for sidelink - Mode 2 | Nokia, Nokia Shanghai Bell |
| R1-2105962 | Summary#1 for Rel-16 5G_V2X_NRSL QoS management and congestion control for sidelink | Moderator (Nokia) |
| R1-2105965 | Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2105966 | Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2106015 | Feature lead summary for physical layer procedure aspects in AI 7.2.4 | Moderator (LG Electronics) |
| R1-2106016 | Feature lead summary for email discussion/approval [105-e-NR-5G_V2X-06] | Moderator (LG Electronics) |
| R1-2106017 | Corrections for the multiplexing SL HARQ-ACK information on a PUSCH | Moderator (LG Electronics) |
| R1-2106034 | Moderator summary for email discussion/approval [105-e-NR-5G_V2X-07] | Moderator (OPPO) |
| R1-2106035 | Moderator summary#2 for email discussion/approval [105-e-NR-5G_V2X-07] | Moderator (OPPO) |
| R1-2106036 | Moderator summary#3 for email discussion/approval [105-e-NR-5G_V2X-07] | Moderator (OPPO) |
| R1-2106037 | Moderator summary(eom) for email discussion/approval [105-e-NR-5G_V2X-07] | Moderator (OPPO) |
| R1-2106085 | Feature lead summary on Mode-2 resource allocation issues in Rel.16 5G V2X | Moderator (Intel Corporation) |
| R1-2106088 | Feature lead summary#1 for Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2106089 | Discussion on [105-e-NR-5G_V2X-01] for Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2106181 | [draft] Correction of SL HARQ-ACK reporting when SL feedback is not used | Moderator (Ericsson), Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, NTT DOCOMO |
| R1-2106182 | [draft] Correction of SL HARQ-ACK reporting on UL for SL CG type 2 | Moderator (Ericsson), ASUSTeK, Nokia, Nokia Shanghai Bell, NTT DOCOMO |
| R1-2106192 | LS on RRC parameter for PSFCH RB set | RAN1, LG Electronics |
| R1-2106246 | Correction to sidelink resource identification procedure avoiding infinite loop issue | Moderator (Intel Corporation), Ericsson, FUTUREWEI, Nokia, Nokia Shanghai Bell, OPPO, NTT DOCOMO, Huawei, HiSilicon, CATT, GOHIGH |
| R1-2106253 | Outcome of discussion [105-e-NR-5G_V2X-05] | Moderator (Intel Corporation) |
| R1-2106257 | Correction of SL HARQ-ACK reporting when SL feedback is not used | Moderator (Ericsson), Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, NTT DOCOMO |
| R1-2106258 | Correction of SL HARQ-ACK reporting on UL for SL CG type 2 | Moderator (Ericsson), ASUSTeK, Nokia, Nokia Shanghai Bell, NTT DOCOMO |
| R1-2106272 | Corrections for transmitting sidelink reference signals in TS 38.214 | Moderator (Samsung), Ericsson, vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2106273 | Corrections for transmitting sidelink reference signals in TS 38.214 | Moderator (Samsung), Ericsson, vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2106274 | Correction on OFDM signal generation and PSSCH DM-RS time-domain OCC in TS 38.211 | Moderator (Samsung), Ericsson, vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2106275 | Correction on OFDM signal generation and PSSCH DM-RS time-domain OCC in TS 38.211 | Moderator (Samsung), Ericsson, vivo, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2104214 | Intra-UE Multiplexing and Prioritization for Rel-16 URLLC | Ericsson |
| R1-2104215 | Maintenance of PDCCH and SPS for Rel-16 NR URLLC | Ericsson |
| R1-2104216 | Maintenance of Scheduling and HARQ for Rel-16 NR URLLC | Ericsson |
| R1-2104311 | Rel-16 URLLC/IIoT maintenance of UCI enhancements | Nokia, Nokia Shanghai Bell |
| R1-2104312 | Rel-16 URLLC/IIoT maintenance of PDCCH, Scheduling/HARQ and SPS enhancements | Nokia, Nokia Shanghai Bell |
| R1-2104313 | Rel-16 URLLC/IIoT PUSCH skipping (with LCH and/or PHY prioritization configured) | Nokia, Nokia Shanghai Bell |
| R1-2104321 | Remaining issues on SPS enhancement in Rel-16 URLLC | ZTE |
| R1-2104322 | Remaining issues on intra-UE multiplexing in Rel-16 URLLC | ZTE |
| R1-2104323 | Discussion on PDSCH processing timeline for DCI format 1_2 | ZTE |
| R1-2104410 | Maintenance on PDCCH enhancements for Rel-16 NR URLLC | Spreadtrum Communications |
| R1-2104479 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2104480 | Remaining issues on PUCCH transmission | CATT |
| R1-2104481 | Remaining issues on HARQ codebook | CATT |
| R1-2104650 | Remaining issues on eCG enhancements for URLLC | Qualcomm Incorporated |
| R1-2104799 | Maintenance on PDCCH for UE PDSCH processing time for DCI format 1_2 | OPPO |
| R1-2104800 | Remaining issues on scheduling and HARQ | OPPO |
| R1-2104801 | Maintenance on SPS enhancements | OPPO |
| R1-2105083 | UCI multiplexing and PUSCH skipping design in URLLC | Apple |
| R1-2105084 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple |
| R1-2105285 | Discussion on PUSCH skipping for URLLC | Samsung |
| R1-2105286 | Maintanence on PDCCH as PDSCH SLIV reference | Samsung |
| R1-2105417 | PHR issues related to URLLC/IIOT WI | LG Electronics |
| R1-2105418 | Remaining issues of other aspects for URLLC/IIOT | LG Electronics |
| R1-2105465 | Maintenance on PDCCH enhancement | vivo |
| R1-2105466 | Maintenance on UCI enhancement | vivo |
| R1-2105467 | Maintenance on eCG enhancement and intra-UE prioritization | vivo |
| R1-2105531 | Remaining issues on UCI enhancements and SPS | Huawei, HiSilicon |
| R1-2105532 | On LCH prioritization and UL skipping | Huawei, HiSilicon |
| R1-2105682 | Corrections on scheduling/HARQ for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2105851 | Release of UL grant type 2 PUSCH or SPS PDSCH configurations | ASUSTeK |
| R1-2105867 | Maintenance of PDCCH enhancements for Rel-16 URLLC | WILUS Inc. |
| R1-2105928 | Remaining issues on PDCCH enhancements | Huawei, HiSilicon |
| R1-2106004 | Summary of preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2106005 | Summary of PDCCH enhancements | Moderator (Huawei) |
| R1-2106018 | Summary of HARQ and Scheduling | Moderator (Qualcomm) |
| R1-2106024 | Summary of the Remaining Issues on intra-UE prioritization/multiplexing | Moderator (vivo) |
| R1-2106025 | Summary of [105-e-NR-L1enh-URLLC-04] on the Remaining Issues on intra-UE prioritization/multiplexing | Moderator (vivo) |
| R1-2106049 | Summary#1 on UCI enhancements for R16 URLLC | Moderator (OPPO) |
| R1-2106050 | Summary#1 of email thread [105-e-NR-L1enh-URLLC-02] | Moderator (OPPO) |
| R1-2106052 | Feature lead summary on other aspects for URLLC/IIoT | Moderator (LG Electronics) |
| R1-2106053 | Summary #1 of [105-e-NR-L1enh-URLLC-05] | Moderator (LG Electronics) |
| R1-2106119 | UCI multiplexing and PUSCH skipping design in URLLC | Apple |
| R1-2106225 | Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) | Ad-hoc Chair (Samsung) |
| R1-2106357 | Summary #2 of [105-e-NR-L1enh-URLLC-05] | Moderator (LG Electronics) |
| R1-2106358 | Final Summary of [105-e-NR-L1enh-URLLC-05] | Moderator (LG Electronics) |
| R1-2106359 | Summary of [105-e-NR-L1enh-URLLC-03] Email discussion/approval on remaining issues on Scheduling & HARQ enhancements | Moderator (Qualcomm) |
| R1-2106360 | Handling collision between PUCCH/PUSCH and semi-static DL symbols and SSBs | Moderator (Qualcomm), Samsung, Nokia, DOCOMO |
| R1-2106361 | Summary #1 of email discussion [105-e-NR-L1enh-URLLC-01] on remaining issues on PDCCH enhancements | Moderator (Huawei) |
| R1-2106362 | Correction on Type-1 HARQ-ACK codebook | Moderator (Huawei), HiSilicon, Ericsson |
| R1-2106363 | Correction on value of 1-bit counter DAI | Moderator (Huawei), WILUS, Ericsson |
| R1-2106364 | Correction on SRS resource set configuration in TS 38.212 | Moderator (Huawei), Vivo, Ericsson |
| R1-2106365 | Correction on SRS resource set configuration in TS 38.214 | Moderator (Huawei), Vivo, Ericsson |
| R1-2106374 | CR on correction for sub-slot based PUCCH | Moderator (OPPO) |
| R1-2106375 | CR on clarification for reference point of sub-slot based PUCCH resource | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104407 | Maintenance on multi-TRP transmission | Lenovo, Motorola Mobility |
| R1-2104482 | Correction on power control for PUSCH | CATT |
| R1-2104582 | Maintenance of multi-beam operation | ZTE |
| R1-2104583 | Maintenance of Multi-TRP enhancements | ZTE |
| R1-2104651 | Remaining Issues on Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2104728 | Text proposals for overlapping between PUSCH/HARQ and CSI | OPPO |
| R1-2104729 | Text proposals for TCI state activation | OPPO |
| R1-2105085 | Remaining issues on Rel-16 Multi-TRP enhancement | Apple |
| R1-2105287 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2105288 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2105289 | On Rel-16 multi-beam maintenance | Samsung |
| R1-2105351 | Discussion on DRX interaction with CPU occupancy | Nokia |
| R1-2105352 | DRX interaction with CPU occupancy | Nokia |
| R1-2105468 | Maintenance on number of SRS resource set(s) for DCI format 0_1 and DCI format 0_2 | vivo |
| R1-2105469 | Maintenance on beam related issues | vivo |
| R1-2105537 | Correction on enabling configuration of time restriction over L1-SINR measurement | Huawei, HiSilicon |
| R1-2105538 | Corrections on RRC names and interpretation for Multi-TRP | Huawei, HiSilicon |
| R1-2105809 | Draft CR on DL SPS based PDSCH repetitions | Ericsson |
| R1-2105810 | Maintenance for single-DCI based multi-TRP in Rel-16 | Ericsson |
| R1-2105842 | Interoperation between cross-carrier scheduling and multiple TRPs | ASUSTeK |
| R1-2105950 | Draft CR on DL SPS based PDSCH repetitions | Ericsson |
| R1-2105957 | On Rel-16 multi-beam maintenance | Samsung |
| R1-2105987 | Summary of [105-e-NR-eMIMO-01] | Moderator (LG Electronics) |
| R1-2106137 | Correction on simultaneous multi-CC spatial relation update for SRS | Moderator(LG Electronics), ZTE |
| R1-2106138 | Correction on simultaneous multi-CC TCI indication for CORESET | Moderator(LG Electronics), Vivo |
| R1-2106139 | Text proposal of [105-e-NR-eMIMO-02] Email Discussion | Moderator (Apple Inc.), Huawei, HiSilicon |
| R1-2106140 | Outcome of [105-e-NR-eMIMO-02] Email Discussion | Moderator (Apple) |
| R1-2106141 | Correction on enabling configuration of time restriction over L1-SINR measurement | Moderator (Apple Inc.), Huawei, HiSilicon |
| R1-2106208 | Corrections on RRC names and interpretation for Multi-TRP | Moderator (OPPO), Huawei, HiSilicon |
| R1-2106226 | Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| R1-2106239 | Text Proposal of [105-e-NR-eMIMO-03] | Moderator (OPPO), Huawei, HiSilicon |
| R1-2106322 | Summary of [105-e-NR-eMIMO-03] Email Discussion | Moderator (OPPO) |
| R1-2106323 | Summary of [105-e-NR-eMIMO-04] Email Discussion | Moderator (OPPO) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104254 | Remaining issues for Rel-16 UE power saving | Huawei, HiSilicon |
| R1-2105086 | Maintenace of UE power saving for NR | Apple |
| R1-2105788 | Maintenance for Rel-16 UE power savings | Ericsson |
| R1-2106210 | Summary of email discussion of Rel-16 UE power saving | Moderator (CATT) |
| R1-2106211 | Correction of UE power saving | Moderator (CATT), Ericsson, Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2104276 | Correction to PRS processing priority | Huawei, HiSilicon |
| R1-2104483 | Discussion and TP on remaining issues in NR positioning | CATT |
| R1-2104584 | Clarification on UE Rx-Tx time difference measurements | ZTE |
| R1-2104738 | Corrections on DL PRS resource configruation | OPPO |
| R1-2105470 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2105518 | Draft CR on measurement gap description for positioning | Nokia, Nokia Shanghai Bell |
| R1-2105907 | Maintenance on Rel-16 NR positioning | Ericsson |
| R1-2106019 | Summary of the preparation phase for Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2106020 | Summary of the e-mail discussion [105-e-NR-Pos-01] on Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2106227 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| R1-2106292 | Output #1 for email discussion [105-e-NR-Pos-02] | Moderator (Ericsson) |
| R1-2106293 | CR on DL PRS periodicity and muting repetition factor | Moderator (Ericsson), OPPO |
| R1-2106294 | CR on measurement gap request inside of the active DL BWP for DL PRS measurements | Moderator (Ericsson), Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2106318 | Draft CR on SCS values for DL PRS | Moderator (Intel Corporation), CATT |
| R1-2106319 | Draft CR on correction to DL PRS processing priority order | Moderator (Intel Corporation), Huawei, HiSilicon |
| R1-2106320 | CR on SCS values for DL PRS | Moderator (Intel Corporation), CATT |
| R1-2106321 | CR on correction to DL PRS processing priority order | Moderator (Intel Corporation), Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2105834 | Correction to DAPS HO | Ericsson |
| R1-2106084 | Email discussion summary for Rel-16 NR Mobility Enhancement | Moderator (Intel Corporation) |
| R1-2106240 | Session notes for 7.2.9 (Maintenance of NR Mobility Enhancements) | Ad-hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104324 | Remaing issues for Rel-16 single uplink Tx | ZTE |
| R1-2104475 | Correction for power control of NR-DC | CATT |
| R1-2105375 | Remaining issues on Rel-16 carrier aggregation | MediaTek Inc. |
| R1-2105789 | Maintenance for Rel-16 MR-DCCA | Ericsson |
| R1-2105863 | Removal of FR2-FR2 dual connectivity from Rel-16 | Nokia, Nokia Shanghai Bell |
| R1-2105864 | Moderator summary of MR DC-CA pre-meeting preparation phase | Moderator (Nokia) |
| R1-2105918 | Corrections on CCS with different subcarrier spacings for PDCCH and PDSCH in TS 38.214 | Huawei, HiSilicon |
| R1-2106228 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2106307 | 38.214 CR on unaligned frame boundary CA with A-CSI-RS transmission and CSI reference resource definition | Moderator (Nokia), MediaTek |
| R1-2106308 | [105-e-NR-MRDC-CA-01] Moderator summary | Moderator (Nokia) |
| R1-2106343 | Alignment of EN-DC/NE-DC parameter names | FUTUREWEI |
| R1-2106344 | Alignment of EN-DC/NE-DC parameter names | FUTUREWEI |
| R1-2106376 | Alignment CR on RRC parameter names for EN-DC/NE-DC Coexistence | Lenovo, Motorola Mobility |
| R1-2106377 | Alignment CR on RRC parameter names for EN-DC/NE-DC Coexistence (mirrored to Rel-16) | Lenovo, Motorola Mobility |
| R1-2106378 | Alignment CR on RRC parameter name for single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA | Lenovo, Motorola Mobility |
| TDoc | Title | Source |
|---|---|---|
| R1-2105790 | Remaining details of Rel-16 NR UE features | Ericsson |
| R1-2105814 | Remaining issues on NR Rel-16 UE features | Nokia, Nokia Shanghai Bell |
| R1-2105956 | Summary on Rel-16 NR UE feature related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2106133 | Reply LS on fallback applicability for FeatureSetDownLinkPerCC capability fields | RAN1, ZTE |
| R1-2106157 | Summary on [105-e-NR-UEFeature-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2106158 | Summary on [105-e-NR-UEFeature-MRDCCA-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2106160 | Updated RAN1 UE features list for Rel-16 NR after RAN1#105-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2106161 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | RAN1, AT&T, NTT DOCOMO |
| R1-2106164 | Summary of email discussion/approval [105-e-NR-UEFeatures-eMIMO-01] | Moderator (AT&T) |
| R1-2106345 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | RAN1, AT&T, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2104325 | Remaining Issues of Rel-16 UL Tx Switching | ZTE |
| R1-2104653 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2104730 | Enhancement on uplink power control for M-TRP | OPPO |
| R1-2104731 | Text Proposals for Tx Switching between Two Uplink Carriers | OPPO |
| R1-2104858 | Summary of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2105524 | Discussion on half duplex operation for TDD CA | Huawei, HiSilicon |
| R1-2105925 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2105959 | Summary on Rel-16 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2106151 | [105-e-NR-R16-TxSwitching-01] Summary of email discussion on maintenance of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2106159 | Summary on [105-e-NR-TEI16-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2106346 | Correction on half-duplex operation in CA with unpaired spectrum | Moderator (NTT DOCOMO), Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R1-2106229 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104205 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2104266 | Enhancements on multi-beam operation | Huawei, HiSilicon |
| R1-2104292 | Remaining Issues on Rel-17 Multi-beam Operation | InterDigital, Inc. |
| R1-2104343 | Further discussion on multi beam enhancement | vivo |
| R1-2104404 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2104411 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2104484 | Enhancements on multi-beam operation | CATT |
| R1-2104585 | Enhancements on Multi-beam Operation | ZTE |
| R1-2104599 | Enhancements on multi-beam operation | CMCC |
| R1-2104654 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2104732 | Enhancements on Multi-beam Operation | OPPO |
| R1-2104888 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2104944 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2105001 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2105058 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2105087 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2105151 | Further enhancement on multi-beam operation | Sony |
| R1-2105231 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105246 | Discussion on multi-beam operation | NEC |
| R1-2105273 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2105290 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2105291 | Multi-Beam Enhancements | Samsung |
| R1-2105296 | Moderator summary for offline discussion on multi-beam enhancement: CA QCL and unified TCI for 'other signals/channels' | Moderator (Samsung) |
| R1-2105353 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2105540 | Enhancements on multi-beam operation | Xiaomi |
| R1-2105588 | Enhancements on Multi-beam Operation | Convida Wireless |
| R1-2105665 | Enhancements on Multi-Beam Operations | AT&T |
| R1-2105683 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2105779 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2105816 | Discussion on enhancements for Multi-beam Operation | Asia Pacific Telecom, FGI |
| R1-2105828 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2106086 | Moderator summary for multi-beam enhancement: ROUND 1 | Moderator (Samsung) |
| R1-2106131 | Moderator summary for multi-beam enhancement: ROUND 2 | Moderator (Samsung) |
| R1-2106167 | Moderator summary for multi-beam enhancement: ROUND 3 | Moderator (Samsung) |
| R1-2106285 | Moderator summary for multi-beam enhancement: ROUND 4 | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104201 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2104267 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2104293 | Multi-TRP Enhancements for PUCCH and PUSCH | InterDigital, Inc. |
| R1-2104344 | Further discussion on Multi-TRP for PUCCH and PUSCH enhancements | vivo |
| R1-2104405 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2104412 | Discussion on enhancements on Multi-TRP for PUCCH and PUSCH | Spreadtrum Communications |
| R1-2104485 | Enhancements on PUCCH and PUSCH | CATT |
| R1-2104586 | Multi-TRP enhancements for PUCCH and PUSCH | ZTE |
| R1-2104600 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2104655 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2104733 | Enhancements on Multi-TRP based enhancement for PUCCH and PUSCH | OPPO |
| R1-2104841 | Enhancements on Multi-TRP for uplink channels | CAICT |
| R1-2104889 | Multi-TRP enhancements for PUCCH and PUSCH | Intel Corporation |
| R1-2104945 | Multi-TRP enhancements for PUCCH and PUSCH | Intel Corporation |
| R1-2104946 | Multi-TRP enhancements for PUCCH and PUSCH | Intel Corporation |
| R1-2105002 | Multi-TRP enhancements for PUCCH and PUSCH | Intel Corporation |
| R1-2105003 | Multi-TRP enhancements for PUCCH and PUSCH | Intel Corporation |
| R1-2105059 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2105088 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2105152 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2105247 | Discussion on multi-TRP for PUCCH and PUSCH | NEC |
| R1-2105274 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2105292 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2105350 | On multi-TRP enhancements for PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105354 | Enhancements on Multi-TRP for PUCCH and PUSCH | MediaTek Inc. |
| R1-2105541 | Enhancements on Multi-TRP for PUSCH and PUCCH | Xiaomi |
| R1-2105589 | Enhancements on Multi-TRP for PUCCH and PUSCH | Convida Wireless |
| R1-2105629 | Enhancements on Multi-TRP for PUSCH | Sharp |
| R1-2105684 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2105731 | Discussion on mTRP PUSCH | ASUSTeK |
| R1-2105780 | Enhancements on Multi-TRP for PUCCH and PUSCH | LG Electronics |
| R1-2105808 | On PUCCH and PUSCH enhancements for multi-TRP | Ericsson |
| R1-2105817 | Discussion on enhancements for Multi-TRP for uplink channels | Asia Pacific Telecom, FGI |
| R1-2105837 | Enhancements on Multi-TRP for PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2105949 | Discussion on enhancements on Multi-TRP for PUCCH and PUSCH | Spreadtrum Communications |
| R1-2106073 | Summary#1 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2106074 | Summary#2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2106075 | Summary#3 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104202 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2104268 | Discussion on Multi-panel reception for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2104294 | Further Discussion on M-TRP Beam Management | InterDigital, Inc. |
| R1-2104345 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2104406 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2104413 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2104486 | Beam management enhancements for multi-TRP | CATT |
| R1-2104587 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2104601 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2104656 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2104734 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2104891 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2104947 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2105004 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2105060 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2105089 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2105153 | Enhancements on beam management for multi-TRP | Sony |
| R1-2105211 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2105233 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2105248 | Discussion on beam management for multi-TRP | NEC |
| R1-2105275 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2105293 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2105367 | Enhancement on beam management for MTRP | MediaTek Inc. |
| R1-2105542 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2105590 | On Multi-TRP BFR | Convida Wireless |
| R1-2105666 | Beam Management Enhancements for Multi-TRP | AT&T |
| R1-2105672 | Discussion on beam management for multi-TRP | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2105685 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2105754 | Discussion on beam management for multi-TRP | ITRI |
| R1-2105781 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2105806 | On beam management enhancements for simultaneous multi-TRP transmission with multi-panel reception | Ericsson |
| R1-2105818 | Discussion of enhancements on beam management for Multi-TRP | Asia Pacific Telecom, FGI |
| R1-2105836 | Enhancements on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2106058 | Moderator summary #1 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2106153 | Moderator summary#2 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2106170 | Moderator summary#3 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2106287 | Moderator summary#4 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104203 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2104269 | Enhancements on high speed train for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2104295 | Further Discussion on HST-SFN | InterDigital, Inc. |
| R1-2104346 | Further discussion and evaluation on HST-SFN schemes | vivo |
| R1-2104414 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2104487 | Discussion on HST-SFN transmission schemes | CATT |
| R1-2104588 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2104602 | Enhancements on HST-SFN deployment | CMCC |
| R1-2104657 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2104735 | Enhancements on HST-SFN deployment | OPPO |
| R1-2104892 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2104948 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2105005 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2105090 | Views on Rel-17 HST enhancement | Apple |
| R1-2105154 | Enhancement on HST-SFN deployment | Sony |
| R1-2105249 | Discussion on HST-SFN deployment | NEC |
| R1-2105276 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2105294 | Enhancements on HST-SFN | Samsung |
| R1-2105543 | Enhancements on HST-SFN operation for multi-TRP PDCCH transmission | Xiaomi |
| R1-2105586 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2105591 | On Enhancements for HST-SFN deployment | Convida Wireless |
| R1-2105686 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2105761 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2105782 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2106090 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2106121 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2106242 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104204 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2104270 | Discussion on CSI Enhancements for Rel-17 | Huawei, HiSilicon |
| R1-2104296 | Views on CSI Enhancements for NCJT MTRP | InterDigital, Inc. |
| R1-2104347 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2104415 | Discussion on CSI enhancement for multi-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2104488 | CSI enhancements for Rel-17 | CATT |
| R1-2104589 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2104603 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2104658 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2104736 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2104893 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2104949 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2105006 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2105091 | Views on Rel-17 CSI enhancement | Apple |
| R1-2105155 | More considerations on CSI enhancements | Sony |
| R1-2105250 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2105264 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105277 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2105295 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2105368 | CSI enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2105687 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2105762 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2105783 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2105807 | CSI enhancements for MTRP and FR1 FDD reciprocity | Ericsson |
| R1-2106070 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei) |
| R1-2106071 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei) |
| R1-2106072 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei) |
| R1-2106077 | On PMI sharing for CSI enhancements under multi-TRP framework | Lenovo, Motorola Mobility, Ericsson, Intel Corporation, vivo |
| R1-2106194 | Summary of CSI enhancements for MTRP and FDD (Round 3 and NWM) | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2106230 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104210 | Initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2104273 | Initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2104348 | Discussions on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2104416 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2104452 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2104460 | Initial Access Aspects | Ericsson |
| R1-2104507 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2104659 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2104765 | Discusson on initial access aspects | OPPO |
| R1-2104833 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2104894 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2104950 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2105007 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2105061 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2105092 | Discussion on Initial access signals and channels | Apple |
| R1-2105156 | Considerations on initial access aspects for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2105260 | Discussion on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2105297 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2105370 | Discussion on initial access of 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2105419 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2105495 | Initial access aspects for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2105555 | On initial access aspects for NR from 52.6GHz to 71 GHz | Xiaomi |
| R1-2105581 | Discussions on initial access aspects | InterDigital, Inc. |
| R1-2105592 | NR Initial Access from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2105630 | Initial access aspects | Sharp |
| R1-2105660 | On the importance of inter-operator PCI confusion resolution and ANR support in 52.6 GHz and beyond | AT&T |
| R1-2105688 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2105786 | Further details of initial access for NR above 52.6 GHz | Charter Communications |
| R1-2105868 | Discussion on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2105977 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2105978 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2105988 | On the importance of inter-operator PCI confusion resolution and ANR support in 52.6 GHz and beyond | AT&T, NTT DOCOMO, INC., T-Mobile USA |
| R1-2106082 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2106311 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104211 | Enhancements of PUCCH formats for Beyond 52.6GHz | FUTUREWEI |
| R1-2104349 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2104417 | Discussion on enhancements for PUCCH format 0/1/4 for above 52.6GHz | Spreadtrum Communications |
| R1-2104453 | Enhanced PUCCH formats 0/1/4 | Nokia, Nokia Shanghai Bell |
| R1-2104461 | PUCCH enhancements | Ericsson |
| R1-2104508 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2104660 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2104766 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2104834 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2104895 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2104951 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2105008 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2105093 | Discussion on Enhancements for PUCCH formats 0/1/4 | Apple |
| R1-2105157 | Further considerations on enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2105298 | Enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2105369 | On Enhancements for PUCCH formats 0/1 | MediaTek Inc. |
| R1-2105420 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2105496 | Enhancements to PUCCH formats 0/1/4 for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2105582 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2105689 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2105869 | Discussion on PUCCH enhancement for PUCCH format 0/1/4 | WILUS Inc. |
| R1-2105929 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2105961 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2106065 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2106068 | FL Summary for [105-e-NR-52-71GHz-02] Email discussion/approval | Moderator (Ericsson) |
| R1-2106288 | FL Summary#2 for [105-e-NR-52-71GHz-02] Email discussion/approval | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104212 | Enhancements to support PDSCH/PUSCH for Beyond 52.6GHz | FUTUREWEI |
| R1-2104274 | PDSCH/PUSCH enhancements for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2104350 | Discussions on multi-PDSCH/PUSCH scheduling for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2104418 | Discussion on PDSCH and PUSCH enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2104454 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2104462 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2104509 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2104661 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2104767 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2104835 | Discussion on the PDSCH/PUSCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2104896 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2104952 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2105009 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2105062 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2105094 | Discussion on multi-PxSCH and HARQ Codebook Enhancements | Apple |
| R1-2105158 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2105259 | Discussion on PDSCH enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2105299 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2105372 | HARQ codebook design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2105396 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2105421 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2105422 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2105497 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2105556 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2105583 | Enhancing PDSCH/PUSCH Scheduling for 52.6 GHz to 71 GHz Band | InterDigital, Inc. |
| R1-2105596 | PDSCH Considerations for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2105690 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2105784 | PDSCH-PUSCH Enhancement for NR beyond 52.6 GHz | Charter Communications |
| R1-2105870 | Discussion on multi-PDSCH/PUSCH scheduling for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2106105 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104213 | Channel access for shared spectrum Beyond 52.6 GHz | FUTUREWEI |
| R1-2104275 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2104351 | Discussions on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2104419 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2104455 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2104463 | Channel Access Mechanisms | Ericsson |
| R1-2104510 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2104662 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2104720 | Discussions on channel access mechanism enhancements for 52.6G-71 GHz | CAICT |
| R1-2104768 | Discussion on channel access mechanism | OPPO |
| R1-2104836 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2104897 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2104953 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2105010 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2105063 | Considerations on channel access mechanism for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2105095 | Channel access mechanism | Apple |
| R1-2105145 | Channel access for multi-beam operation | Panasonic |
| R1-2105159 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2105261 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2105300 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2105371 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2105423 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2105498 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2105557 | Discussion on channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2105584 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2105597 | On Channel Access Mechanism for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2105661 | On receiver assisted channel access and directional LBT | AT&T |
| R1-2105691 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2105755 | Discussion on multi-beam operation | ITRI |
| R1-2105785 | Channel access mechanisms for above 52.6 GHz | Charter Communications |
| R1-2105871 | Discussion on channel access mechanism for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2105986 | Contribution summary of channel access mechanism for 52.6GHz-71GHz band, ver01 | Moderator (Qualcomm Incorporated) |
| R1-2106165 | Contribution summary of channel access mechanism for 52.6GHz-71GHz band, ver02 | Moderator (Qualcomm Incorporated) |
| R1-2106193 | Contribution summary of channel access mechanism for 52.6GHz-71GHz band, ver03 | Moderator (Qualcomm Incorporated) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104352 | Discussions on frequency range definition and sync raster for 52.6-71GHz | vivo |
| R1-2104456 | Extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2104464 | Introduction of the 52.6 to 71 GHz frequency range | Ericsson |
| R1-2104511 | Views on Frequency Range for 52.6 to 71 GHz | CATT |
| R1-2104769 | Discussion on other aspects | OPPO |
| R1-2104837 | Discussion on the frequency range definition for above 52.6GHz | ZTE, Sanechips |
| R1-2104898 | Discussion on frequency range determination for NR extension up to 71GHz | Intel Corporation |
| R1-2104954 | Discussion on frequency range determination for NR extension up to 71GHz | Intel Corporation |
| R1-2105011 | Discussion on frequency range determination for NR extension up to 71GHz | Intel Corporation |
| R1-2105096 | On How to Introduce the 52.6-71GHz Frequency Range | Apple |
| R1-2105301 | Discussion on defining frequency range for NR from 52.6 to 71 GHz | Samsung |
| R1-2105373 | Frequency range naming discussion for 52.6-71 GHz | MediaTek Inc. |
| R1-2105424 | Discussion on frequency range definition to support NR above 52.6 GHz | LG Electronics |
| R1-2105533 | Discussion on the frequency range for bands in 52.6-71 GHz | Huawei, HiSilicon |
| R1-2105585 | Efficient beam management for NR in 52.6 – 71 GHz | InterDigital, Inc. |
| R1-2105692 | Views on how to introduce 52.6 - 71 GHz frequency range in NR | NTT DOCOMO, INC. |
| R1-2105787 | Discussion on how to introduce the 52.6-71GHz frequency range | Charter Communications |
| R1-2106109 | Draft LS on how to introduce the 52.6-71GHz frequency range | Moderator (Lenovo) |
| R1-2106110 | FL Summary for discussion [105-e-NR-52-71GHz-05] on analysis or recommendation to RAN#92e (June) on how to introduce the 52.6-71GHz frequency range | Moderator (Lenovo) |
| R1-2106276 | Draft LS on how to introduce the 52.6-71GHz frequency range | Moderator (Lenovo) |
| R1-2106277 | LS on how to introduce the 52.6-71GHz frequency range | RAN1, Lenovo |
| R1-2106278 | FL Summary#2 for discussion [105-e-NR-52-71GHz-05] on analysis or recommendation to RAN#92e (June) on how to introduce the 52.6-71GHz frequency range | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104217 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2104262 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2104309 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2104314 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2104326 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2104353 | HARQ-ACK enahncements for Rel-17 URLLC | vivo |
| R1-2104420 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2104512 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2104604 | Discussion on UE feeback enhancements for HARQ-ACK | CMCC |
| R1-2104663 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2104802 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2104854 | Discussion on two aspects of UE HARQ-ACK feedback enhancements | China Telecom |
| R1-2104899 | On dynamic carrier switching and dropped HARQ feedback retransmission | Intel Corporation |
| R1-2104955 | On dynamic carrier switching and dropped HARQ feedback retransmission | Intel Corporation |
| R1-2105012 | On dynamic carrier switching and dropped HARQ feedback retransmission | Intel Corporation |
| R1-2105097 | Views on eIIoT/URLLC HARQ feedback enhancements | Apple |
| R1-2105160 | Retransmission of dropped HARQ-ACK for URLLC | Sony |
| R1-2105188 | Discussion on UE feedback enhancements for HARQ-ACK | PANASONIC R&D Center Germany |
| R1-2105212 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2105234 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2105258 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2105302 | HARQ-ACK Reporting Enhancements for URLLC | Samsung |
| R1-2105355 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2105399 | HARQ feedback enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2105425 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2105631 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2105693 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2105732 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2105750 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2105766 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2105819 | Discussion on UE feedback enhancements for HARQ-ACK | Asia Pacific Telecom, FGI |
| R1-2105872 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | WILUS Inc. |
| R1-2106097 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2106099 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2106248 | Moderator summary #4 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2106249 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104199 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2104218 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2104263 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2104327 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2104354 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2104421 | Discussion on CSI feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2104513 | CSI feedback enhancements | CATT |
| R1-2104605 | Discussion on CSI feeback enhancements for URLLC | CMCC |
| R1-2104664 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2104803 | CSI feedback enhancements for URLLC | OPPO |
| R1-2104900 | Selection of enhanced CSI feedback schemes | Intel Corporation |
| R1-2104956 | Selection of enhanced CSI feedback schemes | Intel Corporation |
| R1-2105013 | Selection of enhanced CSI feedback schemes | Intel Corporation |
| R1-2105098 | Views on eIIoT/URLLC CSI feedback enhancements | Apple |
| R1-2105161 | Considerations on CSI feedback enhancements | Sony |
| R1-2105186 | Discussion on CSI Feedback Enhancements | Quectel, Langbo |
| R1-2105303 | Improving MCS Selection for URLLC | Samsung |
| R1-2105426 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2105472 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2105580 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2105694 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2105733 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2105767 | CSI feedback enhancements for URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2105958 | Selection of enhanced CSI feedback schemes | Intel Corporation |
| R1-2105975 | Feature lead summary#1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2105976 | Feature lead summary#2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2106003 | CSI feedback enhancements for URLLC/IIoT use cases (revised) | Nokia, Nokia Shanghai Bell |
| R1-2106176 | Feature lead summary#3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2106177 | Feature lead summary#4 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104200 | UE initiated COT for semi-static channel access | FUTUREWEI |
| R1-2104219 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2104265 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2104328 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2104355 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2104422 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2104514 | Enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2104665 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2104804 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2104901 | On the Harmonization of UL CG between NR-U and URLLC and COT-initiator Determination | Intel Corporation |
| R1-2104957 | On the Harmonization of UL CG between NR-U and URLLC and COT-initiator Determination | Intel Corporation |
| R1-2105014 | On the Harmonization of UL CG between NR-U and URLLC and COT-initiator Determination | Intel Corporation |
| R1-2105099 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2105142 | Further UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2105143 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2105162 | Considerations on unlicensed URLLC | Sony |
| R1-2105213 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2105235 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2105304 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2105356 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2105400 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2105409 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2105427 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2105632 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2105695 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2105734 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2105768 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2105873 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2106044 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2106045 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2106046 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2106047 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2106048 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104220 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2104264 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2104310 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2104329 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2104356 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2104423 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2104515 | Intra-UE multiplexing and prioritization | CATT |
| R1-2104606 | Discussion on intra-UE multiplexing/prioritization | CMCC |
| R1-2104666 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2104805 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2104855 | Discussion on intra-UE multiplexing and prioritization | China Telecom |
| R1-2104902 | Details of intra-UE multiplexing and prioritization | Intel Corporation |
| R1-2104958 | Details of intra-UE multiplexing and prioritization | Intel Corporation |
| R1-2105015 | Details of intra-UE multiplexing and prioritization | Intel Corporation |
| R1-2105100 | Design of Rel-17 intra-UE multiplexing/prioritization | Apple |
| R1-2105144 | Discussion on Intra-UE multiplexing and prioritization of different priority | Panasonic Corporation |
| R1-2105163 | Considerations on intra-UE UL multiplexing | Sony |
| R1-2105187 | Discussion on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2105206 | Intra-UE Multiplexing and Prioritization | TCL Communication Ltd. |
| R1-2105221 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2105236 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2105262 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2105305 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2105357 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2105428 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2105473 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2105558 | Intra-UE multiplexing prioritization for URLLC IIoT | Xiaomi |
| R1-2105633 | Intra-UE UCI multiplexing with different priorities and channel prioritization | Sharp |
| R1-2105696 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2105735 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2105756 | Discussion on intra-UE multiplexing | ITRI |
| R1-2105769 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2105874 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2106051 | Summary#1 of email thread [105-e-NR-R17-IIoT_URLLC-04] | Moderator (OPPO) |
| R1-2106063 | Summary#2 of email thread [105-e-NR-R17-IIoT_URLLC-04] | Moderator (OPPO) |
| R1-2106120 | Design of Rel-17 intra-UE multiplexing/prioritization | Apple |
| TDoc | Title | Source |
|---|---|---|
| R1-2106115 | Discussion on how to reply to SA2 LS on new 5QI for NTN | Moderator (Ericsson) |
| R1-2106174 | DRAFT Reply LS on PDB for new 5QI | Moderator (Ericsson) |
| R1-2106231 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| R1-2106331 | Reply LS on PDB for new 5QI | RAN1, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104255 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2104306 | Discussion on timing relationship enhancement in NTN | THALES |
| R1-2104424 | Consideration on timing relationship enhancements for NTN | Spreadtrum Communications |
| R1-2104516 | Timing relationship enhancement for NTN | CATT |
| R1-2104564 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2104607 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2104667 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2104708 | Timing relationship enhancements for NTN | Zhejiang Lab |
| R1-2104721 | Timing relationship enhancements to support NTN | CAICT |
| R1-2104727 | On timing relationship enhancements for NTN | Ericsson |
| R1-2104770 | Discussion on timing relationship enhancement | OPPO |
| R1-2104827 | Further discussion of time relation aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2104857 | Timing Relationship Enhancements in NR-NTN | China Telecom |
| R1-2104903 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2104959 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2105016 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2105101 | Timing Relationship Enhancements for NR NTN | Apple |
| R1-2105164 | Calculation and application of timing relationship offsets | Sony |
| R1-2105189 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2105207 | Discussion on Timing Relationship Enhancements for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105208 | Timing relationship enhancements for NTN | ITL |
| R1-2105306 | Timing relationship enhancements for NTN | Samsung |
| R1-2105410 | Discussion on timing relationship enhancements for NTN | NEC |
| R1-2105477 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2105559 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2105619 | Timing relationship for NTN | Panasonic Corporation |
| R1-2105623 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2105667 | Timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2105697 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2105820 | Timing relationship enhancements in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2105969 | Discussion on timing relationship enhancement | OPPO |
| R1-2105974 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2106059 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2106114 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2106254 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2106325 | Feature lead summary#5 on timing relationship enhancements | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104256 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2104301 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2104302 | Feature lead summary #1 on enhancements on UL timing and frequency synchronization for NR NTN | THALES |
| R1-2104303 | Feature lead summary #2 on enhancements on UL timing and frequency synchronization for NR NTN | THALES |
| R1-2104304 | Feature lead summary #3 on enhancements on UL timing and frequency synchronization for NR NTN | THALES |
| R1-2104305 | Feature lead summary #4 on enhancements on UL timing and frequency synchronization for NR NTN | THALES |
| R1-2104315 | Enhancements on UL time and frequency synchronization | PANASONIC R&D Center Germany |
| R1-2104425 | Consideration on enhancements on UL time and frequency synchronization for NTN | Spreadtrum Communications |
| R1-2104517 | UL time and frequency synchronization for NTN | CATT |
| R1-2104565 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2104608 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2104668 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2104722 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2104771 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2104811 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2104828 | Discussion on time and frequency synchronization for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2104904 | On UL synchronization for NTN | Intel Corporation |
| R1-2104960 | On UL synchronization for NTN | Intel Corporation |
| R1-2105017 | On UL synchronization for NTN | Intel Corporation |
| R1-2105102 | Uplink Time and Frequency Synchronization for NR NT | Apple |
| R1-2105165 | Considerations on UL time synchronisation | Sony |
| R1-2105190 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2105214 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2105272 | Discussion on UL Time Synchronization for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105307 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2105478 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2105560 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2105634 | Enhancements on frequency synchronization for NTN | Sharp |
| R1-2105668 | UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2105698 | Discussion on UL time and frequency synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2105812 | On satellite pass predictions under NTN discontinuous coverage | Sateliot, Gatehouse, ESA, Kepler |
| R1-2105821 | UL time and frequency synchronization in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2105947 | UL time synchronization acquisition for NTN | Mitsubishi Electric RCE |
| R1-2105952 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2106112 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2106142 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2106186 | Summary of Email discussion/approval for R1-2104230 | Moderator (OPPO) |
| R1-2106290 | Feature lead summary #5 on enhancements on UL timing and frequency synchronization for NR NTN | THALES |
| R1-2106305 | LS on broadcast of NTN GW or gNB position | RAN1, THALES |
| R1-2106332 | LS on broadcast of NTN GW or gNB position | RAN1, THALES |
| R1-2106340 | DRAFT Reply LS on TA pre-compensation | Moderator (OPPO) |
| R1-2106341 | Reply LS on TA pre-compensation | RAN1, OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2104257 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2104357 | Discussion on HARQ enhancements for NR-NTN | vivo |
| R1-2104402 | Discussion on HARQ for NTN | Magister Solutions Ltd |
| R1-2104426 | Consideration on enhancements on HARQ for NTN | Spreadtrum Communications |
| R1-2104518 | HARQ operation enhancement for NTN | CATT |
| R1-2104566 | Enhancements on HARQ for NR NTN | MediaTek Inc. |
| R1-2104609 | Enhancements on HARQ for NTN | CMCC |
| R1-2104669 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2104723 | Enhancements on HARQ to support NTN | CAICT |
| R1-2104772 | Discussion on HARQ enhancements | OPPO |
| R1-2104812 | On HARQ enhancements for NTN | Ericsson |
| R1-2104829 | Further discussion related to HARQ operation for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105054 | HARQ enhancements for NTN networks | CEWiT |
| R1-2105103 | On HARQ Enhancements for NR NTN | Apple |
| R1-2105166 | Enhancement on HARQ for NTN | Sony |
| R1-2105191 | Discussion on HARQ for NR-NTN | ZTE |
| R1-2105215 | Enhancements on HARQ for NTN | Lenovo, Motorola Mobility |
| R1-2105222 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2105237 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2105308 | Enhancements on HARQ for NTN | Samsung |
| R1-2105358 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2105411 | Discussion on HARQ enhancements for NR NTN | NEC |
| R1-2105479 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2105561 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2105620 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2105669 | HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2105757 | Enhancements on HARQ for NTN | ITRI |
| R1-2105822 | Enhancements on HARQ in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2106013 | Summary#1 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2106066 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2106171 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2106269 | Summary#4 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104307 | Beam management and BWP operation in NTN | THALES |
| R1-2104358 | Discussion on other aspects for NR-NTN | vivo |
| R1-2104427 | Consideration on beam management and other aspects for NTN | Spreadtrum Communications |
| R1-2104519 | Beam management and other aspects for NTN | CATT |
| R1-2104610 | Other Aspects for NTN | CMCC |
| R1-2104670 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2104773 | Discusson on beam management | OPPO |
| R1-2104776 | FL Summary of 8.4.4 Other Aspects of NR-NTN | Moderator (OPPO) |
| R1-2104813 | On other enhancements for NTN | Ericsson |
| R1-2104830 | Discussion of other aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105104 | Discussions on Other Aspects of NR NTN | Apple |
| R1-2105148 | Beam management and polarization signaling for NTN | Panasonic |
| R1-2105167 | Discussion on beam management and polarization for NTN | Sony |
| R1-2105192 | Discussion on additional enhancement for NR-NTN | ZTE |
| R1-2105209 | Discussion on Beam Management for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105216 | Discussion on other aspects for NTN | Lenovo, Motorola Mobility |
| R1-2105223 | Discussion on beam management for NTN | ETRI |
| R1-2105238 | Discussion on beam management for NTN | ETRI |
| R1-2105309 | Remaining issues for NTN Samsung | Samsung |
| R1-2105359 | Discussion on beam management for NTN | ETRI |
| R1-2105480 | Discussions on other aspects of NTN | LG Electronics |
| R1-2105529 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2105562 | Discussion on other design aspects for NTN | Xiaomi |
| R1-2105671 | On beam management for NTN | InterDigital, Inc. |
| R1-2106175 | FL Summary#2 of 8.4.4 Other Aspects of NR-NTN | OPPO |
| R1-2106263 | FL Summary#3 of 8.4.4 Other Aspects of NR-NTN | OPPO |
| R1-2106336 | FL Summary#4 of 8.4.4 Other Aspects of NR-NTN | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R1-2106162 | Email discussion/approval for the reply LS to R1-2102306 | Moderator (Qualcomm) |
| R1-2106232 | Session notes for 8.5 (NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2106270 | Draft reply LS to SA2 on Scheduling Location in Advance | Qualcomm Incorporated |
| R1-2106312 | Reply LS to SA2 on Scheduling Location in Advance | RAN1, Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R1-2104277 | Enhancement to mitigate gNB and UE Rx/Tx timing error | Huawei, HiSilicon |
| R1-2104359 | Discussion on potential enhancements for RX/TX timing delay mitigating | vivo |
| R1-2104520 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | CATT |
| R1-2104590 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2104611 | Discussion on mitigation of gNB/UE Rx/Tx timing errors | CMCC |
| R1-2104671 | Enhancements on Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2104739 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2104871 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2104905 | Mitigation of UE/gNB TX/RX Timing Errors | Intel Corporation |
| R1-2104961 | Mitigation of UE/gNB TX/RX Timing Errors | Intel Corporation |
| R1-2105018 | Mitigation of UE/gNB TX/RX Timing Errors | Intel Corporation |
| R1-2105105 | Positioning accuracy enhancements under timing errors | Apple |
| R1-2105168 | Discussion on mitigating UE Rx/Tx and gNB Rx/Tx timing delays | Sony |
| R1-2105310 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2105482 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2105512 | Views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2105699 | Discussion on mitigating UE and gNB Rx/Tx timing delays | NTT DOCOMO, INC. |
| R1-2105759 | Mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2105856 | On methods for Rx/Tx timing delays mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105859 | Enhancements for mitigation of Tx/Rx Delays | Lenovo, Motorola Mobility |
| R1-2105908 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2105967 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2106091 | FL Summary#2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2106156 | FL Summary#3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2106259 | FL Summary#4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2106265 | [Draft] LS on positioning reference unit (PRU) for enhancing the positioning performance | CATT |
| R1-2106326 | LS on positioning reference unit (PRU) for enhancing the positioning performance | RAN1, CATT |
| R1-2106339 | FL Summary#5 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104278 | Enhancement for UL AoA positioning | Huawei, HiSilicon |
| R1-2104360 | Discussion on potential enhancements for UL-AoA method | vivo |
| R1-2104521 | Discussion on accuracy improvements for UL-AoA positioning solutions | CATT |
| R1-2104591 | Accuracy improvement for UL-AoA positioning solutions | ZTE |
| R1-2104612 | Discussion on UL-AoA enhancements | CMCC |
| R1-2104672 | Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2104740 | Enhancements for UL AoA Positioning | OPPO |
| R1-2104872 | Discussion on enhancements for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2104906 | NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2104962 | NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2105019 | NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2105106 | Positioning Accuracy enhancements for UL-AoA | Apple |
| R1-2105169 | Discussion on accuracy improvements for UL-AoA positioning method | Sony |
| R1-2105311 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2105483 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2105513 | Views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2105658 | Discussion on UL AoA positioning enhancements | PML |
| R1-2105700 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2105857 | UL-AoA positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105909 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2106021 | Feature lead summary#0 for e-mail discussion [105-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2106022 | Feature lead summary#1 for e-mail discussion [105-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2106023 | Feature lead summary#2 for e-mail discussion [105-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2106201 | Draft LS on support of UL-AOA/ZOA assistance information signalling for NR positioning | Intel Corporation |
| R1-2106202 | LS on support of UL-AOA/ZOA assistance information signalling for NR positioning | RAN1, Intel Corporation |
| R1-2106334 | Feature lead summary#3 for e-mail discussion [105-e-NR-ePos-02] | Moderator (Intel Corporation) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104228 | Accuracy improvements for DL-AoD positioning solutions | BUPT |
| R1-2104279 | Enhancement for DL AoD positioning | Huawei, HiSilicon |
| R1-2104361 | Discussion on potential enhancements for DL-AoD method | vivo |
| R1-2104522 | Discussion on accuracy improvements for DL-AoD positioning solutions | CATT |
| R1-2104592 | Accuracy improvements for DL-AoD positioning solutions | ZTE |
| R1-2104613 | Discussion on DL-AoD enhancements | CMCC |
| R1-2104673 | Potential Enhancements on DL-AoD positioning | Qualcomm Incorporated |
| R1-2104741 | Enhancements for DL-AoD positioning | OPPO |
| R1-2104842 | Discussion on enhancements for DL-AoD positioning | CAICT |
| R1-2104844 | Carrier Phase Based Downlink Angle of Departure Measurement | DanKook University |
| R1-2104873 | Discussion on enhancements for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2104907 | NR Positioning DL-AoD Enhancements | Intel Corporation |
| R1-2104963 | NR Positioning DL-AoD Enhancements | Intel Corporation |
| R1-2105020 | NR Positioning DL-AoD Enhancements | Intel Corporation |
| R1-2105107 | Positioning Accuracy enhancements for DL-AoD | Apple |
| R1-2105170 | Discussion on accuracy improvements for DL-AoD positioning method | Sony |
| R1-2105312 | Discussion on accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2105484 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2105514 | Views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2105563 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2105701 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2105858 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105860 | DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2105910 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2106079 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2106144 | FL summary#2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2106255 | FL summary#3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104280 | Positioning latency enhancements | Huawei, HiSilicon |
| R1-2104362 | Discussion on latency enhancement for NR positioning | vivo |
| R1-2104523 | Discussion on latency improvements for both DL and DL+UL positioning methods | CATT |
| R1-2104593 | Discussion on latency reduction for NR positioning | ZTE |
| R1-2104614 | Discussion on latency improvement for positioning | CMCC |
| R1-2104674 | Enhancements for Latency Improvements for Positioning | Qualcomm Incorporated |
| R1-2104742 | Enhancements on Latency Reduction in NR Positioning | OPPO |
| R1-2104874 | Discussion on latency improvements for DL and DL+UL positioning methods | InterDigital, Inc. |
| R1-2104908 | NR Positioning Latency Reduction | Intel Corporation |
| R1-2104964 | NR Positioning Latency Reduction | Intel Corporation |
| R1-2105021 | NR Positioning Latency Reduction | Intel Corporation |
| R1-2105108 | Views on Rel-17 positioning latency reduction | Apple |
| R1-2105171 | Considerations on Latency Improvements for DL and DL+UL positioning methods | Sony |
| R1-2105313 | Discussion on latency improvements for both DL and DL+UL positioning methods | Samsung |
| R1-2105485 | Discussion on latency improvements for NR positioning | LG Electronics |
| R1-2105515 | Views on PHY Latency Reductions | Nokia, Nokia Shanghai Bell |
| R1-2105564 | Latency improvements for both DL and DL+UL positioning method | Xiaomi |
| R1-2105760 | Aspects for physical latency improvement | MediaTek Inc. |
| R1-2105861 | Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
| R1-2105911 | Latency improvements for both DL and DL+UL positioning methods | Ericsson |
| R1-2105989 | FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2105990 | FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2105991 | FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2106183 | FL summary #4 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2106184 | [DRAFT] LS on PRS processing samples | Moderator (Huawei) |
| R1-2106185 | LS on PRS processing samples | RAN1, Huawei |
| R1-2106315 | [DRAFT] LS on granularity of response time | Huawei |
| R1-2106316 | LS on granularity of response time | RAN1, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R1-2104198 | NLOS Mitigation Enhancements | FUTUREWEI |
| R1-2104281 | Enhancements to support multi-path and NLOS mitigation | Huawei, HiSilicon |
| R1-2104363 | Discussion on potential enhancements for multipath/NLOS mitigation | vivo |
| R1-2104524 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | CATT |
| R1-2104594 | Enhancements on NLOS mitigation for NR positioning | ZTE |
| R1-2104675 | Multipath Reporting in NR Positioning | Qualcomm Incorporated |
| R1-2104743 | Discussion on multipath/NLOS mitigation for NR positioning | OPPO |
| R1-2104856 | Potential enhancements of information reporting from UE for multipath/NLOS mitigation | China Telecom |
| R1-2104875 | Discussion on multipath/NLOS mitigation for positioning | InterDigital, Inc. |
| R1-2104909 | Mitigation of NLOS Problem for NR Positioning | Intel Corporation |
| R1-2104965 | Mitigation of NLOS Problem for NR Positioning | Intel Corporation |
| R1-2105022 | Mitigation of NLOS Problem for NR Positioning | Intel Corporation |
| R1-2105109 | Views on potential enhancements for NLOS mitigation in Rel-17 positioning | Apple |
| R1-2105172 | Discussion on enhanced reporting from UE and gNB for Multipath/NLOS mitigation | Sony |
| R1-2105314 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Samsung |
| R1-2105486 | Discussion on multipath/NLOS mitigation for positioning | LG Electronics |
| R1-2105516 | Views on LoS/NLoS Identification and Mitigation | Nokia, Nokia Shanghai Bell |
| R1-2105565 | Potential enhancements for multipath/NLOS mitigation | Xiaomi |
| R1-2105702 | Discussion on multipath/NLOS mitigation for NR positioning | NTT DOCOMO, INC. |
| R1-2105862 | Accuracy enhancements based on NLOS/Multipath Information Reporting | Lenovo, Motorola Mobility |
| R1-2105865 | Potential positioning enhancements for multipath/NLOS mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2105912 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2106043 | Feature Lead Summary #1 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2106087 | Feature Lead Summary #2 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2106163 | Feature Lead Summary #3 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104364 | Discussion on inactive state positioning and on-demand PRS | vivo |
| R1-2104525 | Discussion on on-demand transmission and reception of DL PRS and positioning solutions for UEs in RRC_ INACTIVE state | CATT |
| R1-2104595 | Discussion on items led by RAN2 for NR positioning | ZTE |
| R1-2104615 | Discussion on NW/UE efficiency enhancements | CMCC |
| R1-2104676 | Enhancements Related to On Demand PRS And Positioning in RRC Inactive State | Qualcomm Incorporated |
| R1-2104744 | Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS | OPPO |
| R1-2104876 | Discussion on on-demand PRS and INACTIVE mode positioning | InterDigital, Inc. |
| R1-2104880 | Carrier/Subcarrier Phase Based Enhancement for 5G NR Positioning | DanKook University |
| R1-2104910 | Support of On-demand DL PRS and NR Positioning for UEs in RRC-INACTIVE state | Intel Corporation |
| R1-2104966 | Support of On-demand DL PRS and NR Positioning for UEs in RRC-INACTIVE state | Intel Corporation |
| R1-2105023 | Support of On-demand DL PRS and NR Positioning for UEs in RRC-INACTIVE state | Intel Corporation |
| R1-2105315 | Discussion on positioning in inactive state | Samsung |
| R1-2105487 | Discussion on other enhancements for positioning | LG Electronics |
| R1-2105517 | Additional views on Inactive Mode Positioning and on-demand PRS | Nokia, Nokia Shanghai Bell |
| R1-2105534 | Discussion on UL and DL+UL positioning in INACTIVE state | Huawei, HiSilicon |
| R1-2105566 | On-demand PRS and positioning for in-active state UE | Xiaomi |
| R1-2105892 | Potential physical layer impact to the RAN2-led topics | MediaTek Inc. |
| R1-2105913 | On-demand transmission and reception of DL PRS for DL and DL+UL positioning | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104178 | Revised WI work plan for RedCap | Rapporteur (Ericsson) |
| R1-2106213 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104179 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2104188 | Discussion on Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2104283 | Reduced maximum UE bandwidth | Huawei, HiSilicon |
| R1-2104365 | Discussion on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2104428 | Discussion on reduced maximum UE bandwidth for RedCap | Spreadtrum Communications |
| R1-2104526 | Discussion on reduced maximum UE bandwidth | CATT |
| R1-2104543 | Aspects related to reduced maximum UE bandwidth | Nokia, Nokia Shanghai Bell |
| R1-2104553 | Discussion on reduced maximum UE bandwidth for RedCap | China Telecommunications |
| R1-2104616 | Discussion on reduced maximum UE bandwidth | CMCC |
| R1-2104677 | BW Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2104710 | Bandwidth reduction for reduced capability NR devices | ZTE, Sanechips |
| R1-2104782 | Discussion on reduced UE bandwidth | OPPO |
| R1-2104851 | Discussion on reduced maximum UE bandwidth for RedCap | China Telecom |
| R1-2104881 | Discussion on reduced maximum UE bandwidth | TCL Communication Ltd. |
| R1-2104911 | On reduced max UE bandwidth for RedCap | Intel Corporation |
| R1-2104967 | On reduced max UE bandwidth for RedCap | Intel Corporation |
| R1-2105024 | On reduced max UE bandwidth for RedCap | Intel Corporation |
| R1-2105072 | Reduced maximum UE band width for RedCap Ues | DENSO CORPORATION |
| R1-2105110 | On reduced maximum UE bandwidth for Redcap | Apple |
| R1-2105217 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2105316 | Bandwidth Reduction for RedCap UEs | Samsung |
| R1-2105429 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2105567 | Discussion on the reduced maximum UE bandwidth for RedCap | Xiaomi |
| R1-2105593 | Discussion on aspects related to reduced maximum UE bandwidth | NEC |
| R1-2105635 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2105679 | Aspects related to reduced maximum UE bandwidth | Panasonic Corporation |
| R1-2105703 | Discussion on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2105736 | On reduced maximum bandwidth for RedCap UEs | MediaTek Inc. |
| R1-2105746 | Reduced maximum bandwidth for RedCap UEs | InterDigital, Inc. |
| R1-2105751 | Discussion on reduced maximum UE bandwidth | China Unicom |
| R1-2105800 | Discussion on aspects related to reduced maximum UE bandwidth | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2105882 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2105983 | Bandwidth Reduction for RedCap UEs | Samsung |
| R1-2105999 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2106000 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2106001 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2106002 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2106092 | Draft LS on RF switching time for RedCap UE | Ericsson |
| R1-2106187 | Draft LS on RF switching time for RedCap UE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104180 | Reduced number of Rx branches for RedCap | Ericsson |
| R1-2104189 | Discussion on RX Branch Reduction for RedCap UEs | FUTUREWEI |
| R1-2104284 | Reduced number of Rx branches for RedCap | Huawei, HiSilicon |
| R1-2104366 | Discussion on reduced number of Rx branches | vivo, Guangdong Genius |
| R1-2104527 | Discussion on reduced number of Rx branches | CATT |
| R1-2104544 | Aspects related to reduced number of Rx branches | Nokia, Nokia Shanghai Bell |
| R1-2104617 | Discussion on reduced number of Rx branches | CMCC |
| R1-2104678 | RX Branch Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2104711 | Discussion on reduced number of UE Rx branches | ZTE, Sanechips |
| R1-2104783 | Discussion on reduced number of UE Rx branches | OPPO |
| R1-2104912 | On reduced number of Rx branches for RedCap | Intel Corporation |
| R1-2104968 | On reduced number of Rx branches for RedCap | Intel Corporation |
| R1-2105025 | On reduced number of Rx branches for RedCap | Intel Corporation |
| R1-2105111 | On reduced number of Rx branches for Redcap | Apple |
| R1-2105112 | FL summary#1 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2105218 | Reduced number or Rx branches for RedCap | Lenovo, Motorola Mobility |
| R1-2105317 | Discussion on reduced number of RX branches for RedCap UEs | Samsung |
| R1-2105430 | Aspects related to the reduced number of Rx branches of RedCap | LG Electronics |
| R1-2105568 | Aspects on reduced number of Rx branches | Xiaomi |
| R1-2105594 | Discussion on aspects related to reduced number of Rx branches | NEC |
| R1-2105636 | Discussion on reduced minimum number of Rx branches | Sharp |
| R1-2105704 | Discussion on reduced minimum number of Rx branches for RedCap | NTT DOCOMO, INC. |
| R1-2105728 | Aspects related to reduced number of Rx branches | Panasonic Corporation |
| R1-2105737 | On reduced number of Rx branches for RedCap UEs | MediaTek Inc. |
| R1-2105747 | Reduced number of Rx branches for RedCap UEs | InterDigital, Inc. |
| R1-2105752 | Discussion on reduced number of Rx branches | China Unicom |
| R1-2105883 | On aspects related to reduced number of Rx branches | Nordic Semiconductor ASA |
| R1-2106081 | FL summary#2 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2106125 | FL summary #3 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2106333 | FL summary #4 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104181 | Duplex operation for RedCap | Ericsson |
| R1-2104285 | Duplex operation for RedCap | Huawei, HiSilicon |
| R1-2104367 | Discussion on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2104429 | Discussion on duplex operation for RedCap | Spreadtrum Communications |
| R1-2104528 | Discussion on HD-FDD operation | CATT |
| R1-2104545 | Aspects related to duplex operation | Nokia, Nokia Shanghai Bell |
| R1-2104618 | Discussion on collision handling of HD-FDD operation | CMCC |
| R1-2104679 | Type-A HD-FDD for RedCap UE | Qualcomm Incorporated |
| R1-2104712 | HD-FDD for reduced capability NR devices | ZTE, Sanechips |
| R1-2104784 | On half-duplex operation | OPPO |
| R1-2104852 | Discussion on duplex operation for RedCap | China Telecom |
| R1-2104913 | On support of HD-FDD for RedCap | Intel Corporation |
| R1-2104969 | On support of HD-FDD for RedCap | Intel Corporation |
| R1-2105026 | On support of HD-FDD for RedCap | Intel Corporation |
| R1-2105053 | Discussion on aspects related to duplex operation | Potevio Company Limited |
| R1-2105113 | Duplex operation for RedCap | Apple |
| R1-2105219 | Half duplex operation for RedCap | Lenovo, Motorola Mobility |
| R1-2105318 | HD-FDD Operation for RedCap UEs | Samsung |
| R1-2105431 | Aspects related to the duplex operation of RedCap | LG Electronics |
| R1-2105569 | Discussion on Half-duplex FDD operation of Redcap UE | Xiaomi |
| R1-2105637 | Discussion on the duplex operation of redcap UEs | Sharp |
| R1-2105705 | Discussion on duplex operation for RedCap | NTT DOCOMO, INC. |
| R1-2105729 | Aspects related to duplex operation | Panasonic Corporation |
| R1-2105738 | On half duplex operation for RedCap UEs | MediaTek Inc. |
| R1-2105748 | Duplex operation for RedCap UEs | InterDigital, Inc. |
| R1-2105801 | Discussion on aspects related to duplex operation | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2105823 | Discussion on aspects related to duplex operation | Asia Pacific Telecom, FGI |
| R1-2105875 | Discussion on duplex operation for RedCap UE | WILUS Inc. |
| R1-2105884 | On aspects related to duplex operation | Nordic Semiconductor ASA |
| R1-2105900 | Half-duplex FDD redcap operation | Sony |
| R1-2106006 | FL summary #1 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2106145 | FL summary#2 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2106244 | FL summary#3 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104182 | MIMO and modulation support for RedCap | Ericsson |
| R1-2104190 | Discussion on Modulation order and parameters | FUTUREWEI |
| R1-2104286 | Reduced maximum MIMO layers and reduced maximum modulation order for RedCap | Huawei, HiSilicon |
| R1-2104368 | Other feature reductions for RedCap NR devices | vivo, Guangdong Genius |
| R1-2104430 | Discussion on relaxed maximum modulation order for RedCap | Spreadtrum Communications |
| R1-2104529 | Discussion on other aspects related to complexity reduction | CATT |
| R1-2104554 | Other UE Complexity Reduction Aspects | Nokia, Nokia Shanghai Bell |
| R1-2104619 | Discussion on other aspects of reduced UE complexity | CMCC |
| R1-2104680 | Other Aspects of UE Complexity Reduction | Qualcomm Incorporated |
| R1-2104713 | Discussion on modulation order and MIMO layers for RedCap | ZTE, Sanechips |
| R1-2104914 | On other complexity reduction features for RedCap | Intel Corporation |
| R1-2104970 | On other complexity reduction features for RedCap | Intel Corporation |
| R1-2105027 | On other complexity reduction features for RedCap | Intel Corporation |
| R1-2105114 | On relaxed maximum modulation order | Apple |
| R1-2105319 | Other aspects for complexity reduction for RedCap UEs | Samsung |
| R1-2105570 | Discussion on relaxed maximum modulation order and relaxed MIMO layer | Xiaomi |
| R1-2105595 | MIMO aspects for RedCap | NEC |
| R1-2105706 | Discussion on other aspects of UE complexity reduction for RedCap | NTT DOCOMO, INC. |
| R1-2106027 | FL summary #1 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2106166 | FL summary #2 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2106282 | FL summary #3 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104183 | RAN1 aspects for RAN2-led features for RedCap | Ericsson |
| R1-2104191 | Discussion on the Identification of RedCap UEs | FUTUREWEI |
| R1-2104287 | RAN1 aspects of RedCap UE type and identification | Huawei, HiSilicon |
| R1-2104369 | Higher layer support for RedCap | vivo, Guangdong Genius |
| R1-2104431 | Discussion on early indication for RedCap UE | Spreadtrum Communications |
| R1-2104530 | Discussion on higher layer support of RedCap | CATT |
| R1-2104546 | Higher layer support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2104562 | Design consideration for Higher layer support of RedCap | Sierra Wireless, S.A. |
| R1-2104620 | Discussion on higher layer support of RedCap UE | CMCC |
| R1-2104681 | Cross Layer Design Considerations for RedCap Device | Qualcomm Incorporated |
| R1-2104714 | Higher layer support of Reduced Capability NR devices | ZTE, Sanechips |
| R1-2104785 | Mechanism in higher&PHY layer for Reduced Capability NR Devices | OPPO |
| R1-2104853 | Discussion on RAN1 aspects for RAN2-led features for RedCap | China Telecom |
| R1-2104915 | On RedCap UE types: Definition, access control, and identification | Intel Corporation |
| R1-2104971 | On RedCap UE types: Definition, access control, and identification | Intel Corporation |
| R1-2105028 | On RedCap UE types: Definition, access control, and identification | Intel Corporation |
| R1-2105115 | On Higher Layer Support of Redcap Devices | Apple |
| R1-2105173 | UE identification of redcap devices | Sony |
| R1-2105220 | UE identification and access control for RedCap | Lenovo, Motorola Mobility |
| R1-2105320 | RAN1 aspects for RAN2-led features for RedCap | Samsung |
| R1-2105432 | RAN1 aspects for RAN2-led features for RedCap | LG Electronics |
| R1-2105571 | Discussion on the early indication and access control | Xiaomi |
| R1-2105638 | RAN1 aspects for RAN2-led features for RedCap | Sharp |
| R1-2105707 | Discussion on RAN1 aspects for RAN2-led features for RedCap | NTT DOCOMO, INC. |
| R1-2105749 | Identification and restriction of RedCap UEs | InterDigital, Inc. |
| R1-2105876 | Discussion on higher layer support of Redcap UE | WILUS Inc. |
| R1-2105885 | On RedCap UE early identification | Nordic Semiconductor ASA |
| R1-2105981 | FL summary #1 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO) |
| R1-2106094 | FL summary #2 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO) |
| R1-2106146 | FL summary#3 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO) |
| R1-2106195 | FL summary#4 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO) |
| R1-2106216 | [Draft] LS on RAN1 agreements on RAN2-led features for RedCap | NTT DOCOMO |
| R1-2106328 | FL summary#5 on RAN1 aspects for RAN2-led features for RedCap | Moderator (NTT DOCOMO) |
| R1-2106329 | LS on RAN1 agreements on RAN2-led features for RedCap | RAN1, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| R1-2104184 | Ensuring coexistence between RedCap and non-RedCap UEs | Ericsson, Deutsche Telekom, NTT DOCOMO, Softbank, Telecom Italia, Telstra, Verizon Wireless, Vodafone |
| R1-2104370 | Discussion on reduced capability signaling | vivo, Guangdong Genius |
| R1-2104531 | Views on remaining issues of RedCap | CATT |
| R1-2104547 | Coverage recovery aspects for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R1-2104621 | Discussion on potential modification of existing DCI formats | CMCC |
| R1-2104715 | NR UE features for RedCap | ZTE, Sanechips |
| R1-2104786 | Other considerations for reduced UE capability | OPPO |
| R1-2105433 | Discussion on other aspects of RedCap | LG Electronics |
| R1-2105535 | On RedCap UL transmission | Huawei, HiSilicon |
| R1-2105572 | Discussion on the transmission of system information for RedCap | Xiaomi |
| R1-2105802 | Discussion on other aspects for reduced capability UE | ASUSTEK COMPUTER (SHANGHAI) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104221 | Discussion on power saving enhancements for paging | ZTE, Sanechips |
| R1-2104251 | Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2104371 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2104432 | Discussion on potential paging enhancements for UE Power Saving | Spreadtrum Communications |
| R1-2104532 | Paging enhancement for UE power saving | CATT |
| R1-2104622 | Discussion on paging early indication design | CMCC |
| R1-2104682 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2104787 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2104916 | On Paging Enhancements for UE Power Saving | Intel Corporation |
| R1-2104972 | On Paging Enhancements for UE Power Saving | Intel Corporation |
| R1-2105029 | On Paging Enhancements for UE Power Saving | Intel Corporation |
| R1-2105116 | Paging early indication for idle/inactive-mode UE | Apple |
| R1-2105174 | Considerations on potential paging enhancements | Sony |
| R1-2105321 | Discussion on paging enhancements | Samsung |
| R1-2105386 | On Paging Enhancements for Idle/Inactive Mode UE Power Saving | MediaTek Inc. |
| R1-2105434 | Discussion on potential paging enhancements | LG Electronics |
| R1-2105474 | On paging enhancement | Panasonic |
| R1-2105504 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2105573 | Paging enhancements for power saving | Xiaomi |
| R1-2105708 | Discussion on paging enhancements | NTT DOCOMO, INC. |
| R1-2105742 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2105770 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2105791 | Design of Paging Enhancements | Ericsson |
| R1-2105886 | On paging early indication | Nordic Semiconductor ASA |
| R1-2106011 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2106076 | Summary of paging enhancements | Moderator (MediaTek) |
| R1-2106143 | Summary#2 of paging enhancements | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104222 | TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2104252 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2104308 | TRS/CSI-RS occasions for idle/inactive UE | TCL Communication Ltd. |
| R1-2104372 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2104433 | Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2104533 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2104623 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2104683 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2104788 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2104917 | Discussion on TRS/CSI-RS Design in idle/inactive mode | Intel Corporation |
| R1-2104973 | Discussion on TRS/CSI-RS Design in idle/inactive mode | Intel Corporation |
| R1-2105030 | Discussion on TRS/CSI-RS Design in idle/inactive mode | Intel Corporation |
| R1-2105117 | Indication of TRS configurations for idle/inactive-mode UE power saving | Apple |
| R1-2105175 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Sony |
| R1-2105322 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2105323 | Summary#1 for TRS/CSI-RS occasion(s) for idle/inactive Ues | Moderator (Samsung) |
| R1-2105387 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2105435 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2105475 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2105506 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2105574 | On TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2105639 | Discussion on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2105709 | Discussion on TRS CSI-RS occasion for idleinactive UEs | NTT DOCOMO, INC. |
| R1-2105743 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2105771 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2105792 | Provisioning of TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2105887 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2106117 | Summary#2 for TRS/CSI-RS occasion(s) for idle/inactive Ues | Moderator (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104223 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE, Sanechips |
| R1-2104373 | Discussion on paging grouping | vivo |
| R1-2104534 | Details of PEI configuration | CATT |
| R1-2104789 | Paging and TRS indication in idle/inactive modes | OPPO |
| R1-2105527 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2105793 | Modeling of Network Power Consumption | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104224 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2104253 | Extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2104374 | Discussion on DCI-based power saving adaptation in connected mode | vivo |
| R1-2104434 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2104535 | PDCCH monitoring adaptation | CATT |
| R1-2104624 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2104684 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2104790 | DCI-based power saving adaptation solutions | OPPO |
| R1-2104918 | Discussion on DCI-based UE Power Saving Schemes during active time | Intel Corporation |
| R1-2104974 | Discussion on DCI-based UE Power Saving Schemes during active time | Intel Corporation |
| R1-2105031 | Discussion on DCI-based UE Power Saving Schemes during active time | Intel Corporation |
| R1-2105118 | Enhanced DCI-based power saving adaptation | Apple |
| R1-2105263 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2105324 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2105388 | On enhancements to DCI-based UE power saving during DRX active time | MediaTek Inc. |
| R1-2105436 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2105476 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2105505 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2105710 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2105744 | PDCCH monitoring reduction in Active Time | InterDigital, Inc. |
| R1-2105758 | Discussion on DCI-based power saving adaptation | ITRI |
| R1-2105772 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2105794 | Design of active time power savings mechanisms | Ericsson |
| R1-2105824 | Discussion on extension(s) to Rel-16 DCI-based power saving adaptation | Asia Pacific Telecom, FGI |
| R1-2105850 | A common framework for SSSG switching and PDCCH skipping | ASUSTeK |
| R1-2105888 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2106040 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2106041 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2106243 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104225 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE, Sanechips |
| R1-2104375 | Discussion on RLM/BFD relax | vivo |
| R1-2104435 | Discussion on other power saving techniques | Spreadtrum Communications |
| R1-2104536 | Link level performance for UE power saving | CATT |
| R1-2104791 | Discussion on RLM relaxation | OPPO |
| R1-2105528 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2105795 | Evaluation results for UE power saving schemes | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104240 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2104290 | Discussion on enhancements on PUSCH repetition Type A for low latency requirement | NICT |
| R1-2104291 | Discussion on enhancements on PUSCH repetition Type A for low latency requirement | NICT, TOYOTA MOTOR CORPORATION |
| R1-2104330 | Discussion on enhanced PUSCH repetition type A | ZTE |
| R1-2104376 | Discussion on enhancement for PUSCH repetition type A | vivo |
| R1-2104537 | Discussion on enhancements on PUSCH repetition type A | CATT |
| R1-2104625 | Discussion on enhancements on PUSCH repetition type A | CMCC |
| R1-2104685 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2104792 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2104846 | Enhancements on PUSCH repetition type A | China Telecom |
| R1-2104859 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2104919 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2104975 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2105032 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2105119 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2105146 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2105255 | Discussion on PUSCH repetition type A | NEC |
| R1-2105325 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2105488 | Discussions on PUSCH repetition type A enhancements | LG Electronics |
| R1-2105511 | Design considerations for PUSCH repetition Type A Enhancements | Sierra Wireless, S.A. |
| R1-2105575 | Enhancements on PUSCH repetition type A | Xiaomi |
| R1-2105640 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2105652 | PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2105711 | Enhancement on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2105773 | Enhancements on PUSCH repetition type A | Lenovo, Motorola Mobility |
| R1-2105877 | Discussion on enhancements on PUSCH repetition type A | WILUS Inc. |
| R1-2105901 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2105992 | FL Summary on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2106155 | FL Summary#2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2106199 | FL Summary#3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2106279 | FL Summary#4 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104242 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2104297 | On TB processing over multiple slots for PUSCH | Indian Institute of Tech (H) |
| R1-2104331 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2104377 | Discussion on PUSCH TB processing over multiple slots | vivo |
| R1-2104436 | Discussion on TB processing over multi-slot PUSCH | Spreadtrum Communications |
| R1-2104538 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2104626 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2104686 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2104793 | Issues for TB over multi-slot PUSCH | OPPO |
| R1-2104847 | Discussion on TB processing over multi-slot PUSCH | China Telecom |
| R1-2104860 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2104920 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2104976 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2105033 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2105064 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2105120 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2105147 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2105256 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2105326 | TB processing over multi-slot PUSCH | Samsung |
| R1-2105384 | Discussion on TB processing over multi-slot PUSCH | MediaTek Inc. |
| R1-2105489 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2105510 | Design Considerations for TB processing over multi-slot PUSCH | Sierra Wireless, S.A. |
| R1-2105576 | Discussion on TB processing over multi-slot PUSCH | Xiaomi |
| R1-2105641 | TB processing over multi-slot PUSCH | Sharp |
| R1-2105653 | TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2105712 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2105774 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2105878 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2105902 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2105968 | Discussion on TB processing over multi-slot PUSCH | MediaTek Inc. |
| R1-2105996 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2106250 | FL summary#2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2106251 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104241 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2104332 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2104378 | Discussion on Joint channel estimation for PUSCH | vivo |
| R1-2104437 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2104539 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2104627 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2104687 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2104794 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2104848 | Discussion on joint channel estimation for PUSCH | China Telecom |
| R1-2104861 | Joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2104882 | Discussion on joint channel estimation for PUSCH | TCL Communication Ltd. |
| R1-2104921 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2104977 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2105034 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2105121 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2105176 | Joint channel estimation for PUSCH | Sony |
| R1-2105327 | Joint channel estimation for PUSCH | Samsung |
| R1-2105394 | Discussion on joint channel estimation for PUSCH | MediaTek Inc. |
| R1-2105397 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2105490 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2105509 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless, S.A. |
| R1-2105577 | Joint channel estimation for PUSCH | Xiaomi |
| R1-2105642 | Joint channel estimation for multi-slot PUSCH | Sharp |
| R1-2105654 | Joint Channel Estimation for PUSCH | Ericsson |
| R1-2105713 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2105775 | Enhancements for joint channel estimation for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2105879 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2105903 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2105979 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2106152 | [105-e-NR-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2106212 | LS on joint channel estimation for PUSCH and PUCCH | RAN1, China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R1-2104243 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2104333 | Discussion on coverage enhancements for PUCCH | ZTE |
| R1-2104379 | Discussion on PUCCH enhancements | vivo |
| R1-2104438 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2104540 | Discussion on PUCCH enhancement | CATT |
| R1-2104628 | Discussion on PUCCH enhancements | CMCC |
| R1-2104688 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2104795 | PUCCH enhancements for coverage | OPPO |
| R1-2104849 | Discussion on PUCCH enhancements | China Telecom |
| R1-2104862 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2104922 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2104978 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2105035 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2105122 | PUCCH coverage enhancement | Apple |
| R1-2105149 | Discussion on PUCCH enhancement for NR coverage enhancement | Panasonic Corporation |
| R1-2105224 | PUCCH enhancements | ETRI |
| R1-2105239 | PUCCH enhancements | ETRI |
| R1-2105257 | Discussion on PUCCH enhancements | NEC |
| R1-2105328 | PUCCH enhancements | Samsung |
| R1-2105360 | PUCCH enhancements | ETRI |
| R1-2105491 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2105578 | PUCCH coverage enhancement | Xiaomi |
| R1-2105643 | PUCCH coverage enhancement | Sharp |
| R1-2105655 | PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2105714 | PUCCH enhancements | NTT DOCOMO, INC. |
| R1-2105776 | Enhancements for PUCCH repetition | Lenovo, Motorola Mobility |
| R1-2105904 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2106014 | FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2106154 | FL summary#2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104244 | Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2104334 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2104380 | Discussion on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2104439 | Discussion on type A PUSCH repetitions for Msg3 | Spreadtrum Communications |
| R1-2104541 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2104629 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2104689 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2104796 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2104850 | Discussion on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2104863 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2104923 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2104979 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2105036 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2105123 | Discussion on Msg3 Coverage Enhancement | Apple |
| R1-2105150 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2105225 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2105240 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2105329 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2105361 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2105492 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2105579 | Discussion on Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2105644 | Type A repetition for msg3 PUSCH | Sharp |
| R1-2105656 | Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2105715 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2105777 | Type A PUSCH repetitions for Msg3 | Lenovo, Motorola Mobility |
| R1-2105880 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2105905 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2106007 | Feature lead summary#1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2106008 | Feature lead summary#2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2106247 | Final feature lead summary on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104335 | Performance impacts of residual frequency error for joint channel estimation of PUSCH and PUCCH transmissions | ZTE |
| R1-2104381 | Enhanced Contention resolution mechanism for CBRA procedure with MSG3 PUSCH repetition | vivo |
| R1-2104542 | Views on reusing PUSCH enhancements for Msg3 | CATT |
| R1-2104797 | Other considerations for coverage enhancement | OPPO |
| R1-2104864 | Deterministic PUSCH repetition for coverage enhancements | InterDigital, Inc. |
| R1-2105330 | Discussion on PRACH enhancements for msg3 beam improvement | Samsung |
| R1-2105523 | Other issues for coverage enhancement | Huawei, HiSilicon |
| R1-2105657 | Other Coverage Enhancements for PUSCH | Ericsson |
| R1-2105906 | Implications of DMRS bundling for PUSCH and PUCCH | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R1-2106233 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104288 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2104548 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2104716 | Discussion on UL and DL 16QAM for NB-IoT | ZTE |
| R1-2104819 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2105374 | Support 16QAM in NB-IOT Release 17 | MediaTek Inc. |
| R1-2105622 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2105889 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2106042 | Feature lead summary #1 on 105-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2106104 | Feature lead summary #2 on 105-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2106219 | Feature lead summary #3 on 105-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104289 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2104549 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2104717 | Remaining issues on 14-HARQ processes in DL for eMTC | ZTE |
| R1-2104821 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2105890 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2106028 | Feature Lead Summary [105-e-LTE-Rel17_NB_IoT_eMTC-02]: checkpoint#1 | Moderator (Ericsson) |
| R1-2106029 | Feature Lead Summary [105-e-LTE-Rel17_NB_IoT_eMTC-02]: checkpoint#2 | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104718 | Remaining issues on DL TBS of 1736 bits for CE mode A | ZTE |
| R1-2105891 | On the L2 Buffer Size for NB-IoT and LTE-M UEs | Ericsson |
| R1-2105939 | Discussion on DL PAPR for 16-QAM of NB-IoT | Huawei, HiSilicon |
| R1-2106256 | Feature Lead Summary [105-e-LTE-Rel17_NB_IoT_eMTC-03] | Moderator (Sony) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104690 | Workplan for Rel-17 IAB | Qualcomm Incorporated |
| R1-2106234 | Session notes for 8.10 (Enhancements to Integrated Access and Backhaul) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104246 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2104382 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2104691 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2104877 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2104924 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2104980 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2105037 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2105055 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2105124 | Enhanced resource multiplexing within and across IAB nodes | Apple |
| R1-2105226 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2105241 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2105331 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2105362 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2105493 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2105617 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2105662 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2105716 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2105763 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2105852 | Resource multiplexing and DC in enhanced IAB | Ericsson |
| R1-2106054 | Feature lead summary#1 of 8.10.1 | Moderator (AT&T) |
| R1-2106055 | Feature lead summary#2 of 8.10.1 | Moderator (AT&T) |
| R1-2106056 | Feature lead summary#3 of 8.10.1 | Moderator (AT&T) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104247 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2104383 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2104692 | Enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2104878 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2104925 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2104981 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2105038 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2105065 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Fujitsu |
| R1-2105068 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2105125 | Other enhancements for simultaneous operation of an IAB node's links | Apple |
| R1-2105227 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2105242 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2105332 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2105363 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2105494 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2105618 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Nokia, Nokia Shanghai Bell |
| R1-2105663 | Enhancements for IAB interference management | AT&T |
| R1-2105717 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2105764 | Timing, interference, and power control in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2105839 | Timing, interference management and power control in enhanced IAB | Ericsson |
| R1-2106009 | Feature lead summary#1 on enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm Inc.) |
| R1-2106083 | Feature lead summary#2 on enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm Inc.) |
| R1-2106173 | Feature lead summary#3 on enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm Inc.) |
| R1-2106241 | Feature lead summary#4 on enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm Inc.) |
| R1-2106313 | Final feature lead summary on enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm Inc.) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104384 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2104879 | Consideration on reference carrier for semi-static IAB-DU resource configuration | ZTE, Sanechips |
| R1-2105525 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2105840 | Discussion on the payload size for DCI format 2_5 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2105203 | Consolidation of agreements on sidelink evaluation methodology update for power saving | LG Electronics |
| R1-2106135 | Moderator Summary #1 of email discussion or approval to reply LS in R1-2100021 | Moderator (ZTE) |
| R1-2106366 | Moderator Summary #2 of email discussion or approval to reply LS in R1-2100021 | Moderator (ZTE) |
| R1-2106367 | Moderator Summary #3 of email discussion or approval to reply LS in R1-2100021 | Moderator (ZTE) |
| R1-2106368 | Moderator Summary #4 of email discussion or approval to reply LS in R1-2100021 | Moderator (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R1-2105333 | On Resource Allocation Enhacements | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R1-2104176 | Sidelink resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2104192 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2104236 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2104385 | Resource allocation for sidelink power saving | vivo |
| R1-2104440 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2104489 | Discussion on resource allocation for power saving | CATT, GOHIGH |
| R1-2104560 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2104630 | Discussion on resource allocation for power saving | CMCC |
| R1-2104693 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2104706 | Discussion on resource allocation for power saving | Zhejiang Lab |
| R1-2104724 | Considerations on partial sensing in NR V2X | CAICT |
| R1-2104755 | Power saving mechanisms in NR sidelink | OPPO |
| R1-2104869 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2104926 | Sidelink Power Saving Schemes | Intel Corporation |
| R1-2104982 | Sidelink Power Saving Schemes | Intel Corporation |
| R1-2105039 | Sidelink Power Saving Schemes | Intel Corporation |
| R1-2105066 | Considerations on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2105070 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2105126 | On Sidelink Resource Allocation for Power Saving | Apple |
| R1-2105177 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2105204 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2105228 | Discussion on resource allocation for power saving | ETRI |
| R1-2105243 | Discussion on resource allocation for power saving | ETRI |
| R1-2105253 | Discussion on resource allocation for power saving | NEC |
| R1-2105334 | On Resource Allocation for Power Saving | Samsung |
| R1-2105364 | Discussion on resource allocation for power saving | ETRI |
| R1-2105380 | Discussion on sidelink power saving | MediaTek Inc. |
| R1-2105544 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2105598 | NR SL Resource Allocation for Power Saving | Convida Wireless |
| R1-2105614 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2105615 | Discussion on resource allocation for power saving | Hyundai Motors |
| R1-2105645 | Discussion on resource allocation for power saving | Sharp |
| R1-2105651 | Resource allocation for power saving with partial sensing in NR sidelink enhancement | ITL |
| R1-2105674 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2105718 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2105845 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2105866 | Further discussion on power saving for sidelink | ROBERT BOSCH GmbH |
| R1-2105893 | Resource allocation procedures for power saving | Ericsson |
| R1-2106030 | FL summary for AI 8.11.1.1 – resource allocation for power saving (1st check point) | Moderator (OPPO) |
| R1-2106031 | FL summary for AI 8.11.1.1 – resource allocation for power saving (2nd check point) | Moderator (OPPO) |
| R1-2106032 | FL summary for AI 8.11.1.1 – resource allocation for power saving (final check point) | Moderator (OPPO) |
| R1-2106033 | FL summary for AI 8.11.1.1 – resource allocation for power saving (final EOM) | Moderator (OPPO) |
| R1-2106067 | Resource allocation for sidelink power saving | vivo |
| R1-2106098 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2106122 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R1-2104177 | Inter-UE coordination in mode 2 sidelink resource allocation | Nokia, Nokia Shanghai Bell |
| R1-2104193 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2104237 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2104386 | Discussion on mode-2 enhancements | vivo |
| R1-2104441 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2104457 | Inter-UE Coordination for Mode 2 Enhancements | Kyocera Corporation |
| R1-2104490 | Discussion on inter-UE coordination in mode 2 enhancement | CATT, GOHIGH |
| R1-2104561 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2104631 | Discussion on reliability and latency enhancements for mode-2 resource allocation | CMCC |
| R1-2104694 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2104707 | Inter-UE coordination schemes in mode 2 | Zhejiang Lab |
| R1-2104725 | Considerations on mode 2 enhancements | CAICT |
| R1-2104756 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2104870 | Discussion on inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2104927 | Inter-UE Coordination Schemes for Sidelink Communication | Intel Corporation |
| R1-2104983 | Inter-UE Coordination Schemes for Sidelink Communication | Intel Corporation |
| R1-2105040 | Inter-UE Coordination Schemes for Sidelink Communication | Intel Corporation |
| R1-2105067 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2105127 | On Inter-UE Coordination | Apple |
| R1-2105178 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2105200 | Discussion on the inter-UE coordination | ZTE |
| R1-2105205 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2105229 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2105244 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2105254 | Discussion on mode 2 enhancements | NEC |
| R1-2105270 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2105335 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2105365 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2105393 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2105545 | Discussion on inter-UE coordination | Xiaomi |
| R1-2105599 | NR SL Inter-UE Coordination for Mode 2 Enhancements | Convida Wireless |
| R1-2105616 | Discussion on inter-UE coordination for Mode 2 enhancements | Hyundai Motors |
| R1-2105646 | Discussion on inter-UE coordination for Mode 2 enhancements | Sharp |
| R1-2105650 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2105659 | Inter-UE coordination for mode 2 enhancements | ITL |
| R1-2105675 | On inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2105719 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2105848 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2105881 | Discussion on inter-UE coordination for sidelink mode-2 | ROBERT BOSCH GmbH |
| R1-2105894 | Feasibility and benefits of mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2105971 | void | ETSI MCC |
| R1-2105982 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2106062 | Feature lead summary for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2106188 | Feature lead summary#2 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2106200 | Discussion on mode-2 enhancements | vivo |
| R1-2106284 | Feature lead summary#3 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2106338 | Feature lead summary#4 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| TDoc | Title | Source |
|---|---|---|
| R1-2106235 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104195 | Group Scheduling Aspects for Connected UEs | FUTUREWEI |
| R1-2104248 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2104336 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2104387 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2104442 | Discussion on MBS group scheduling for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2104491 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2104550 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2104632 | Discussion on group scheduling mechanisms | CMCC |
| R1-2104695 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2104759 | Group scheduling for NR Multicast and Broadcast Services | OPPO |
| R1-2104865 | On group scheduling mechanism for NR MBS | Lenovo, Motorola Mobility |
| R1-2104928 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2104984 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2105041 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2105069 | Discussion on Group Scheduling and Simultaneous MBS and Unicast Reception | TCL Communication Ltd. |
| R1-2105128 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Apple |
| R1-2105179 | Considerations on MBS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2105336 | Support of group scheduling for RRC_CONNECTED Ues | Samsung |
| R1-2105381 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2105437 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2105600 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Convida Wireless |
| R1-2105647 | Discussion on common frequency resource for multicast of RRC_CONNECTED UEs | ETRI |
| R1-2105670 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Google Inc. |
| R1-2105720 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2105838 | Discussion on group scheduling for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2105844 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2105914 | Mechanisms to support MBS group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2105973 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106039 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106093 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106126 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106169 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106197 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2106304 | Summary#7 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104196 | Further Discussions on Reliability for RRC_CONNECTED UEs | FUTUREWEI |
| R1-2104249 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2104337 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2104388 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2104443 | Mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2104492 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT, CBN |
| R1-2104551 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2104633 | Discussion on reliability improvement | CMCC |
| R1-2104696 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2104760 | UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2104866 | On reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2104929 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2104985 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2105042 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2105129 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2105337 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2105382 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2105438 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2105601 | Discussion on reliability enhancement for RRC_CONNECTED UEs | Convida Wireless |
| R1-2105648 | Discussion on HARQ-ACK feedback for multicast of RRC_CONNECTED UEs | ETRI |
| R1-2105721 | Discussion on HARQ-ACK feedback for multicast for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2105843 | Discussion on reliability for RRC_CONNECTED UEs | CHENGDU TD TECH LTD. |
| R1-2105915 | Mechanisms to improve reliability for RRC_CONNECTED Ues | Ericsson |
| R1-2106012 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2106064 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2106113 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2106198 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2106324 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2106330 | FL summary#6 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104197 | MBS Support for RRC IDLE/INACTIVE UEs | FUTUREWEI |
| R1-2104250 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2104338 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2104389 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | vivo |
| R1-2104444 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | Spreadtrum Communications |
| R1-2104493 | Discussion on basic functions for MBS for RRC_IDLEINACTIVE UEs | CATT, CBN |
| R1-2104552 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2104634 | Discussion on NR MBS in RRC_IDLE/ RRC_INACTIVE states | CMCC |
| R1-2104697 | Views on group scheduling for Broadcast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2104761 | Discussion on support for IDLE and INACTIVE state Ues | OPPO |
| R1-2104867 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2104930 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2104986 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2105043 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2105130 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Apple |
| R1-2105180 | Considerations on MBS functions for RRC_IDLE/RRC_INACTIVE UEs | Sony |
| R1-2105338 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2105383 | Discussion on broadcast or multicast for RRC_IDLE or INACTIVE UEs | MediaTek Inc. |
| R1-2105439 | Basic function for broadcast/multicast | LG Electronics |
| R1-2105602 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R1-2105673 | Discussion on MBS for RRC_IDLE/INACTIVE UE | Google Inc. |
| R1-2105722 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | NTT DOCOMO, INC. |
| R1-2105849 | Basic functions for MBS for RRC_IDLE/RRC_INACTIVE UEs | CHENGDU TD TECH LTD. |
| R1-2105916 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2105993 | Feature Lead summary #1 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2105994 | Feature Lead summary #2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2105995 | Feature Lead summary #3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2106217 | Feature Lead summary #4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2106218 | Feature Lead summary #5 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104339 | Consideration on performance enhancement for RRC_IDLE/INACTIVE UEs | ZTE |
| R1-2104390 | Other issues for Rel-17 MBS | vivo |
| R1-2104494 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2104762 | PUCCH resource allocation for NACK-only based HARQ-ACK feedback in MBMS | OPPO |
| R1-2105440 | Other aspects for MBS | LG Electronics |
| R1-2105526 | Impact from MCCH and MTCH on broadcast reception | Huawei, HiSilicon |
| R1-2105853 | MBS related network planning for two delivery modes | CHENGDU TD TECH LTD. |
| R1-2105854 | MBS related network planning for two delivery modes | CHENGDU TD TECH LTD. |
| R1-2105855 | MBS related network planning for two delivery modes | CHENGDU TD TECH LTD. |
| R1-2105917 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2106236 | Session notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104185 | On cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2104232 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2104340 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2104391 | Discussion on Scell scheduling Pcell | vivo |
| R1-2104445 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2104495 | Discussion on cross-carrier scheduling from Scell to Pcell | CATT |
| R1-2104635 | Discussion on cross-carrier scheduling from SCell to Pcell | CMCC |
| R1-2104698 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2104806 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2104931 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2104987 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2105044 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2105131 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2105230 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2105245 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2105339 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2105366 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2105378 | On Cross-Carrier Scheduling from SCell to PCell/PSCell | MediaTek Inc. |
| R1-2105401 | Search space monitoring in sSCell and PCell | InterDigital, Inc. |
| R1-2105441 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2105546 | Discussion on Cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2105723 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2105765 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2105796 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2105847 | Discussion on cross-carrier scheduling from sSCell to PCell/PSCell | ASUSTeK |
| R1-2105970 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2106078 | Summary of Email discussion [105-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2106136 | Summary#2 of Email discussion [105-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2106245 | Summary#3 of Email discussion [105-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2106291 | Summary#4 of Email discussion [105-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2106356 | Summary#5 of Email discussion [105-e-NR-DSS-01] | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104186 | Way Forward On single DCI scheduling two cells | Nokia, Nokia Shanghai Bell |
| R1-2104233 | Discussion on multi-carrier scheduling using single PDCCH | Huawei, HiSilicon |
| R1-2104341 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | ZTE |
| R1-2104392 | Discussion on joint scheduling | vivo |
| R1-2104446 | Discussion on multi-cell PDSCH scheduling via a single DCI | Spreadtrum Communications |
| R1-2104496 | Discussion on multi-cell PDSCH scheduling via a single DCI | CATT |
| R1-2104807 | Discussion on multi-cell PDSCH scheduling via a single DCI | OPPO |
| R1-2104868 | On multi-cell PDSCH scheduling via a single DCI | Lenovo, Motorola Mobility |
| R1-2104932 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2104988 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2105045 | On 2-cell scheduling via single DCI | Intel Corporation |
| R1-2105132 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | Apple |
| R1-2105340 | On a single DCI format scheduling on multiple cells | Samsung |
| R1-2105402 | On the support of single DCI scheduling two cells | InterDigital, Inc. |
| R1-2105412 | Multi-cell PDSCH scheduling via a single DCI | NEC |
| R1-2105442 | Discussion on multi-cell PDSCH scheduling via a single DCI | LG Electronics |
| R1-2105724 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | NTT DOCOMO, INC. |
| R1-2105797 | Study on single DCI scheduling PDSCH on multiple cells | Ericsson |
| R1-2106069 | Feature lead summary#1 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| R1-2106134 | Feature lead summary#2 on multi-cell scheduling via a single DCI | Moderator (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104187 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2104206 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2104234 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2104342 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2104393 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2104447 | Discussion on efficient activation/de-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2104497 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | CATT |
| R1-2104699 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2104808 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2104933 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2104989 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2105046 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2105133 | On efficient SCell Activation/Deactivation | Apple |
| R1-2105341 | Remaining Issues on Scell Activation/Deactivation | Samsung |
| R1-2105379 | Discussion on temporary RS | MediaTek Inc. |
| R1-2105403 | Efficient SCell Activation | InterDigital, Inc. |
| R1-2105413 | Discussion on efficient activation mechanism for SCells | NEC |
| R1-2105725 | Discussion on efficient activation deactivation mechanism for Scells | NTT DOCOMO, INC. |
| R1-2105798 | Reduced Latency SCell Activation | Ericsson |
| R1-2105846 | Efficient activation/deactivation of SCell | ASUSTeK |
| R1-2106147 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2106148 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2106327 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104394 | Discussion on other aspects on DSS | vivo |
| R1-2104498 | Simulation results for multi-cell PDSCH scheduling via a single DCI | CATT |
| R1-2104577 | Further analysis and simulation for Multi-cell scheduling for both downlink and uplink | ZTE |
| R1-2105519 | Remaining issues on the efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2105799 | CRS Rate-matching enhancement for DSS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R1-2104700 | Updated Work Plan for Rel-17 SI on XR Evaluations for NR | Qualcomm Incorporated |
| R1-2106238 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104207 | XR traffic model | FUTUREWEI |
| R1-2104238 | Traffic model for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2104395 | Remaining issues on traffic models of XR | vivo |
| R1-2104502 | XR traffic model | CATT |
| R1-2104555 | On Traffic Model for XR study | Nokia, Nokia Shanghai Bell |
| R1-2104701 | Remaining Issues on XR Traffic Models | Qualcomm Incorporated |
| R1-2104745 | Discussion on the XR traffic models for evaluation | OPPO |
| R1-2104934 | Traffic Model for XR | Intel Corporation |
| R1-2104990 | Traffic Model for XR | Intel Corporation |
| R1-2105047 | Traffic Model for XR | Intel Corporation |
| R1-2105134 | Considerartions on XR traffic model | Apple |
| R1-2105181 | Considerations on XR traffic model | Sony |
| R1-2105342 | Traffic Models for XR | Samsung |
| R1-2105376 | Traffic Model for XR and CG | MediaTek Inc. |
| R1-2105443 | Discussion on traffic models for XR evaluation | LG Electronics |
| R1-2105499 | Discussion on UL traffic models | InterDigital, Inc. |
| R1-2105547 | Discussion on remaining issues of traffic Model for XR services | Xiaomi |
| R1-2105603 | Remaining Issues of XR Traffic Model | ZTE, Sanechips |
| R1-2105726 | Discussion on traffic model for XR | NTT DOCOMO, INC. |
| R1-2105829 | Traffic model for XR | Ericsson |
| R1-2106149 | LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | RAN1, Qualcomm |
| R1-2106380 | [104b-e-NR-XR-01] Email discussion/approval on traffic model | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104208 | XR evaluation methodology | FUTUREWEI |
| R1-2104239 | Evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2104396 | Discussion on evaluation methodologies for XR | vivo |
| R1-2104499 | Evaluation methodology and performance index for XR | CATT |
| R1-2104556 | Development of the Evaluation Methodology for XR Study | Nokia, Nokia Shanghai Bell |
| R1-2104702 | Remaining Issues on Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2104746 | Discussion on the XR evaluation methodology | OPPO |
| R1-2104935 | Evaluation Methodology for XR | Intel Corporation |
| R1-2104991 | Evaluation Methodology for XR | Intel Corporation |
| R1-2105048 | Evaluation Methodology for XR | Intel Corporation |
| R1-2105135 | Remaining issues in XR evaluation methodology | Apple |
| R1-2105343 | Evaluation methodology and KPIs for XR | Samsung |
| R1-2105377 | On Evaluation Methodology for XR and CG | MediaTek Inc. |
| R1-2105444 | Discussion on evaluation methodologies for XR | LG Electronics |
| R1-2105500 | Discussion on additional issues on XR Evaluations Methodology and KPI | InterDigital, Inc. |
| R1-2105548 | Discussion on remaining issues of evaluation methodology for XR services | Xiaomi |
| R1-2105604 | Further Discussion on XR Evaluation Methodology | ZTE, Sanechips |
| R1-2105727 | Discussion on evaluation methodology for XR | NTT DOCOMO, INC. |
| R1-2105830 | Evaluation methodology for XR | Ericsson |
| R1-2105997 | Summary#1 of evaluation methodology for XR | Moderator (vivo) |
| R1-2106096 | Summary#2 of evaluation methodology for XR | Moderator (vivo) |
| R1-2106172 | Summary#3 of evaluation methodology for XR | Moderator (vivo) |
| R1-2106283 | Summary#4 of evaluation methodology for XR | Moderator (vivo) |
| R1-2106371 | Summary of [105-e-NR-XR-02] Email discussion/approval on evaluation methodology | Moderator (vivo) |
| R1-2106372 | Updated template for XR evaluation results | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104209 | XR initial evaluations | FUTUREWEI |
| R1-2104397 | Initial performance evaluation results on XR | vivo |
| R1-2104500 | Evaluation results of XR performance | CATT |
| R1-2104557 | Performance results in indoor hotspot and dense urban deployments of CG and VR applications | Nokia, Nokia Shanghai Bell |
| R1-2104703 | Initial Evaluation Results for XR Capacity and UE Power Consumption | Qualcomm Incorporated |
| R1-2104747 | Evaluation results for XR evaluation | OPPO |
| R1-2104936 | Initial results for XR | Intel Corporation |
| R1-2104992 | Initial results for XR | Intel Corporation |
| R1-2105049 | Initial results for XR | Intel Corporation |
| R1-2105136 | Performance evaluation on XR | Apple |
| R1-2105392 | Initial Performance and Evaluation Results for XR and CG | MediaTek Inc. |
| R1-2105501 | Initial Performance Evaluation Results on XR | InterDigital, Inc. |
| R1-2105521 | Initial evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2105605 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2105664 | XR Initial Performance Results | AT&T |
| R1-2105831 | Initial XR performance evaluation results | Ericsson |
| R1-2105963 | Initial results for XR | Intel Corporation |
| R1-2106010 | Initial Performance Evaluation Results on XR | InterDigital, Inc. |
| R1-2106057 | XR Initial Performance Results | AT&T |
| R1-2106116 | Evaluation Results for XR Capacity and UE Power Consumption | Moderator (Qualcomm) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104398 | Challenges and potential enhancements of XR | vivo |
| R1-2104501 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2104558 | Enhancements for better XR support over NR | Nokia, Nokia Shanghai Bell |
| R1-2104704 | Potential Enhancements for XR | Qualcomm Incorporated |
| R1-2104748 | Discussion on the support of XR/CG service in sidelink-unlicensed | OPPO |
| R1-2105137 | Considerations on potential enhancements for XR | Apple |
| R1-2105344 | Potential enhancements for better XR support in NR | Samsung |
| R1-2105502 | Discussion on potential enhancements for XR | InterDigital, Inc. |
| R1-2105522 | Challenges and potential enhancements for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2105549 | Discussion on potential enhancement for supporting XR | Xiaomi |
| R1-2105606 | Further Discussion on Capacity and Power Working Areas for XR | ZTE, Sanechips |
| R1-2105832 | Discussion on enhancements for XR | Ericsson |
| R1-2106038 | Summary of AI 8.14.4 on potential enhancements for XR | Moderator (vivo) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104573 | Link budget result calibration Spreadsheet for IoT NTN | MediaTek Inc. |
| R1-2105815 | Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) (Release 17) | Rapporteur (MediaTek) |
| R1-2106106 | Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) (Release 17) | Rapporteur (MediaTek) |
| R1-2106237 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| R1-2106379 | Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) (Release 17) | Rapporteur (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104258 | Application scenarios of IoT in NTN | Huawei, HiSilicon |
| R1-2104403 | Discussion on eMTC enabling High Value NTN IoT use-cases | Omnispace |
| R1-2104503 | Applicable scenarios to NB-IoT/eMTC | CATT |
| R1-2104567 | Scenarios applicable to IoT NTN | MediaTek Inc. |
| R1-2104571 | Summary #1 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2104636 | Discussion on scenarios applicable to NB-IoT/eMTC | CMCC |
| R1-2104777 | Discussion on scenarios applicable to NB-IoT/eMTC | OPPO |
| R1-2104814 | On scenarios and evaluations for NB-IoT and eMTC based NTN | Ericsson |
| R1-2104822 | Scenarios applicable to NB-IoT/eMTC | Qualcomm Incorporated |
| R1-2105138 | On Link Budget Analysis of IoT NTN | Apple |
| R1-2105182 | IoT-NTN Link Budgets | Sony |
| R1-2105193 | Discussion on the remaining issues of scenarios and assumption for IoT-NTN | ZTE |
| R1-2105345 | Remaining issues on scenarios applicable to NB-IoT/eMTC | Samsung |
| R1-2105404 | Link budget evaluations and deployment for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105550 | Discussion on the link budget of NBIoT and eMTC over NTN | Xiaomi |
| R1-2105945 | Discussion on eMTC enabling High Value NTN IoT use-cases | Omnispace |
| R1-2105946 | Discussion on eMTC enabling High Value NTN IoT use-cases | Omnispace |
| R1-2106190 | Summary #2 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104259 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2104399 | Discussion on enhancements to time and frequency synchronization on NB-IoT_eMTC for NTN | vivo |
| R1-2104448 | Consideration on enhancements to time and frequency synchronization for IoT NTN | Spreadtrum Communications |
| R1-2104504 | Time and frequency synchronization for NB-IoT/eMTC | CATT |
| R1-2104568 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2104572 | Summary #1 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2104637 | Enhancements to time and frequency synchronization for IoT NTN | CMCC |
| R1-2104778 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2104815 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2104823 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2104937 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2104993 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2105050 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2105139 | Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2105183 | Enhancements to time and frequency synchronisation for IoT-NTN | Sony |
| R1-2105194 | Discussion on the synchronization for IoT-NTN | ZTE |
| R1-2105346 | On enhancements to time and frequency synchronization | Samsung |
| R1-2105405 | Enhancement to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105551 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2105624 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2105676 | Time/Frequency Synchronization for IoT NTN | InterDigital, Inc. |
| R1-2105825 | Time and Frequency Synchronization to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2106095 | Summary #2 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2106191 | Summary #3 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2106289 | Summary #4 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104260 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2104449 | Consideration on timing relationship enhancements for IoT NTN | Spreadtrum Communications |
| R1-2104505 | Timing relationship enhancement for NB-IoT/eMTC | CATT |
| R1-2104569 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2104638 | Timing relationship enhancements for IoT NTN | CMCC |
| R1-2104779 | Discussion on timing relationship enhancements | OPPO |
| R1-2104816 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2104824 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2104938 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2104994 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2105051 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2105140 | Timing Relationship Enhancement in IoT NTN | Apple |
| R1-2105184 | Timing relationship enhancements for IoT-NTN | Sony |
| R1-2105195 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2105347 | Timing relationship enhancements | Samsung |
| R1-2105406 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105503 | RAR Window Offset | Fraunhofer IIS / Fraunhofer HHI |
| R1-2105552 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2105677 | Timing relationship enhancement for IoT NTN | InterDigital, Inc. |
| R1-2105826 | Timing relationship enhancements to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2106080 | FL summary #1 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2106189 | FL summary #2 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2106310 | FL summary #3 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104261 | Discussion on HARQ enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2104400 | Discussion on HARQ enhancements on NB-IoT_eMTC for NTN | vivo |
| R1-2104450 | Consideration on enhancements on HARQ for IoT NTN | Spreadtrum Communications |
| R1-2104506 | HARQ operation enhancement for NB-IoT/eMTC | CATT |
| R1-2104570 | Enhancements on HARQ for IoT NTN | MediaTek Inc. |
| R1-2104639 | Enhancements on HARQ for IoT NTN | CMCC |
| R1-2104780 | Discussion on HARQ enhancements | OPPO |
| R1-2104817 | On HARQ enhancements for IoT NTN | Ericsson |
| R1-2104825 | Enhancements on HARQ | Qualcomm Incorporated |
| R1-2105141 | HARQ Enhancement in IoT NTN | Apple |
| R1-2105185 | HARQ enhancements for IoT-NTN | Sony |
| R1-2105196 | Discussion on HARQ for IoT-NTN | ZTE |
| R1-2105348 | On enhancements on HARQ | Samsung |
| R1-2105407 | HARQ for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2105553 | Discussion on the HARQ enhancement for IoT NTN | Xiaomi |
| R1-2105621 | HARQ enhancement for IoT NTN | Lenovo, Motorola Mobility |
| R1-2105678 | HARQ enhancement for IoT NTN | InterDigital, Inc. |
| R1-2105827 | Enhancements on HARQ to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2106060 | Summary#1 of enhancements on HARQ | Moderator(Samsung) |
| R1-2106061 | Summary#2 of enhancements on HARQ | Moderator(Samsung) |
| R1-2106271 | Summary#3 of enhancements on HARQ | Moderator(Samsung) |
| R1-2106337 | Summary#4 of enhancements on HARQ | Moderator(Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R1-2104451 | Consideration on other design aspects for IoT NTN | Spreadtrum Communications |
| R1-2104781 | Discussion on other aspects | OPPO |
| R1-2104820 | On evaluation assumptions for NB-IoT and eMTC based NTN | Ericsson |
| R1-2104826 | Other aspects for NTN IOT | Qualcomm Incorporated |
| R1-2105197 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2105408 | Applicability of NB-IoT/eMTC features for NTN | Nokia, Nokia Shanghai Bell |
| R1-2105530 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| R1-2105554 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R1-2104401 | Support of 2Tx codebook configuration to 4Tx capable UE in UL | vivo, ZTE, CMCC |
| R1-2104473 | Discussion on SSB resources for RLM | CATT |
| R1-2104596 | TEI-17 proposal on NR codeword mapping | ZTE |
| R1-2104705 | Rel-17 TEI | Qualcomm Incorporated |
| R1-2104939 | On Rel-17 TEI enhancement | Intel Corporation |
| R1-2104995 | On Rel-17 TEI enhancement | Intel Corporation |
| R1-2105052 | On Rel-17 TEI enhancement | Intel Corporation |
| R1-2105536 | Enhancements on the scheduling of PUSCH over multiple slots | Huawei, HiSilicon, China Unicom |
| R1-2105739 | Views on TEI-17 proposal targeting the false PMI reporting issue | MediaTek Inc. |
| R1-2105778 | Rel-17 TEI proposal for mitigating half-duplex issue in NR V2X groupcast NACK-only case regime | Intel Corporation, Qualcomm Inc. |
| R1-2105804 | 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-2105813 | TEI-17 proposal targeting the false PMI reporting issue | Ericsson, NTT DOCOMO, Softbank, Verizon, T-Mobile USA |
| R1-2105951 | Support of 2Tx codebook configuration to 4Tx capable UE in UL | vivo, ZTE, CMCC, Samsung |
| R1-2105955 | Summary on Rel-17 NR TEI related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2106101 | Draft Text Proposals for 38.211 on TEI-17 CW mapping | ZTE |
| R1-2106102 | Draft Text Proposals for 38.212 on TEI-17 CW mapping | ZTE |
| R1-2106103 | Draft Text Proposals for 38.214 on TEI-17 CW mapping | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R1-2104563 | Guidance for elections during TSG RAN WG1#105-e | RAN1 Chair, ETSI MCC |