TDoc | Title | Source |
---|---|---|
R1-2403820 | Draft Agenda of RAN1#117 meeting | RAN1 Chair |
R1-2403822 | RAN1#117 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2403821 | Report of RAN1#116bis meeting | ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2403823 | Reply LS on improved GNSS operations in Rel-18 IoT NTN | RAN2, Huawei |
R1-2403824 | LS to RAN1 on bandwidth aggregation | RAN2, ZTE |
R1-2403825 | LS to RAN1 on SLPP agreements | RAN2, Intel |
R1-2403826 | LS on PRACH mask index handling for MSG1 repetition | RAN2, China Telecom |
R1-2403827 | LS on Sidelink Feature Co-configuration | RAN2, OPPO |
R1-2403828 | LS on type 3 PH value for the serving cell configured with mTRP | RAN2, ZTE |
R1-2403829 | LS on parameters used for CG RACH-less Handover | RAN2, InterDigital |
R1-2403830 | LS on SL positioning measurements | RAN4, Huawei |
R1-2403831 | LS on UE capability for NW verified location | RAN4, Huawei |
R1-2403832 | Reply LS on BWP operation without bandwidth restriction | RAN4, vivo, Vodafone |
R1-2403833 | LS on UE Capability for Asymmetric BW for less than 5 MHz | RAN4, Rakuten Mobile |
R1-2403834 | LS on 3T6R and 4T6R antenna switching SRS | RAN4, Huawei |
R1-2403835 | LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | SA2, vivo |
R1-2403836 | Reply LS on OAM requirements for UE location verification | SA5, CATT |
R1-2403837 | LS on reference point for SSB-TimeOffset | RAN2, Apple |
R1-2403838 | Reply LS on n-TimingAdvanceOffset for PDCCH order RACH | RAN4, Apple |
R1-2403839 | LS on RAN4 UE feature list for Rel-18 (version 4) | RAN4, CMCC |
R1-2403899 | Discussion of SA2 LS on Data Collection for Direct AI/ML Based Positioning | Ericsson |
R1-2403986 | Draft LS reply on SRS bandwidth aggregation | Intel Corporation |
R1-2403987 | Draft LS reply on SL positioning measurements | Intel Corporation |
R1-2403988 | Draft LS reply on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | Intel Corporation |
R1-2403990 | Discussion on RAN4 LS on 3T6R and 4T6R SRS antenna switching | Ericsson |
R1-2404010 | Discussion on LS on bandwidth aggregation | Spreadtrum Communications |
R1-2404011 | Discussion on LS on PRACH mask index handling for MSG1 repetition | Spreadtrum Communications |
R1-2404012 | Discussion on LS on type 3 PH value for the serving cell configured with mTRP | Spreadtrum Communications |
R1-2404050 | Draft Reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Nokia |
R1-2404051 | Draft Reply LS to RAN2 on bandwidth aggregation | Nokia |
R1-2404060 | Draft Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | Samsung |
R1-2404061 | Discussion on LS on data collection for direct AI/ML based positioning | Samsung |
R1-2404062 | Draft Reply LS on parameters used for CG RACH-less Handover | Samsung |
R1-2404063 | Draft reply LS on type 3 PH value for the serving cell configured with mTRP | Samsung |
R1-2404064 | Draft reply LS on 3T6R and 4T6R antenna switching SRS | Samsung |
R1-2404139 | Draft LS reply on Sidelink Feature co-configuration | vivo |
R1-2404140 | Draft reply LS on bandwidth aggregation | vivo |
R1-2404141 | Draft reply LS on SL positioning measurements | vivo |
R1-2404142 | Discussion on LS on 3T6R and 4T6R antenna switching SRS | vivo |
R1-2404143 | Discussion on LS on parameters used for CG RACH-less Handover | vivo |
R1-2404144 | Discussion on LS on type 3 PH value for the serving cell configured with mTRP | vivo |
R1-2404145 | Draft reply LS on LTM L1 intra and inter-frequency measurements | vivo |
R1-2404146 | Draft reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | vivo |
R1-2404198 | LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | RAN2, Nokia |
R1-2404199 | LS on LTM L1 intra and inter-frequency measurements | RAN2, Intel |
R1-2404200 | Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 | RAN2, Qualcomm |
R1-2404206 | On RAN4 LS on the system parameters for FR2-NTN | THALES |
R1-2404207 | Discussion on parameters used for CG RACH-less Handover | ZTE |
R1-2404208 | Draft reply LS on parameters used for CG RACH-less Handover | ZTE |
R1-2404209 | Discussion on the reference point for SSB-TimeOffset | ZTE |
R1-2404243 | Discussion on type 3 PH value for the serving cell configured with mTRP | ZTE |
R1-2404244 | Draft reply LS on type 3 PH value for the serving cell configured with mTRP | ZTE |
R1-2404245 | Discussion on 3T6R and 4T6R antenna switching SRS | ZTE |
R1-2404246 | Draft reply LS on 3T6R and 4T6R antenna switching SRS | ZTE |
R1-2404247 | Discussion on LTM L1 intra and inter-frequency measurements | ZTE |
R1-2404248 | Draft reply LS on LTM L1 intra and inter-frequency measurements | ZTE |
R1-2404265 | Draft reply LS on LTM L1 intra and inter-frequency measurements | Samsung |
R1-2404266 | Discussion on RAN2 LS on Reference Point for SSB-TimeOffset | Apple |
R1-2404267 | Draft Reply LS to RAN2 on Reference Point for SSB-TimeOffset | Apple |
R1-2404268 | Draft Reply LS type 3 PH value for the serving cell configured with mTRP | Apple |
R1-2404341 | Reply LS on Type 3 PH Value for the Serving Cell Configured with mTRP | Lenovo |
R1-2404342 | Reply LS on LTM L1 intra and inter-frequency measurements | Lenovo |
R1-2404349 | Draft reply LS on LTM L1 intra and inter-frequency measurements | Spreadtrum Communications |
R1-2404350 | Draft reply LS on Type3 PH value for the serving cell configured with mTRP | MediaTek Inc. |
R1-2404352 | Discussion on reply LS to SA2 on direct AI/ML based positioning | CATT |
R1-2404353 | Draft reply LS on direct AI/ML based positioning | CATT |
R1-2404354 | Discussion on reply RAN2 LS on type 3 PH value for the serving cell configured with mTRP | CATT |
R1-2404355 | Draft reply LS on type 3 PH value for the serving cell configured with mTRP | CATT |
R1-2404356 | Discussion on bandwidth aggregation | CATT |
R1-2404357 | Draft reply LS on bandwidth aggregation | CATT |
R1-2404358 | Discussion on SL positioning measurements | CATT, CICTCI |
R1-2404359 | Draft reply LS on SL positioning measurements | CATT, CICTCI |
R1-2404360 | Draft reply LS on Sidelink feature co-configuration | CATT, CICTCI |
R1-2404361 | Discussion on asymmetric BW for less than 5 MHz | CATT |
R1-2404443 | Discussion on reference point for SSB-TimeOffset | CMCC |
R1-2404483 | Discussion on UE Capability for Asymmetric BW for less than 5 MHz | Nokia |
R1-2404535 | Discussion of LS On UE Capability for Asymmetric BW for less than 5 MHz | Ericsson |
R1-2404545 | Draft reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | LG Electronics |
R1-2404638 | About RAN2 LS on sidelink feature co-configuration | ZTE, Sanechips |
R1-2404649 | Discussion on LS reply on DL-AoD measurements in NR-PRU-DL-Info | InterDigital, Inc. |
R1-2404660 | Discussion on SA2 LS on data collection for direct AIML positioning | NEC |
R1-2404677 | Draft reply to LS on LTM L1 intra and inter-frequency measurements | NEC |
R1-2404679 | Draft Reply LS on type 3 PH value for the serving cell configured with mTRP | |
R1-2404699 | Draft reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | ZTE |
R1-2404700 | Discussion on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | ZTE |
R1-2404727 | Discussion on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | CATT |
R1-2404728 | Draft reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | CATT |
R1-2404753 | Discussion of LS on LTM L1 intra and inter-frequency measurements | Ericsson |
R1-2404754 | Discussion of LS on questions and recommendations to Rel-18 RAN1 UE features list | Ericsson |
R1-2404755 | Discussion of LS on type 3 PH value for the serving cell configured with mTRP | Ericsson |
R1-2404788 | Discussion on reply LS on reference point for SSB-TimeOffset | CATT |
R1-2404811 | Discussion on LS on UE capability for asymmetric BW for less than 5 MHz | ZTE |
R1-2404825 | Discussion on LS on 3T6R and 4T6R antenna switching SRS | OPPO |
R1-2404826 | Discussion on LS on type 3 PH value for the serving cell configured with mTRP | OPPO |
R1-2404827 | Discussion on RAN2 LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | OPPO |
R1-2404828 | Discussion on RAN2 LS on bandwidth aggregation | OPPO |
R1-2404829 | Discussion on RAN2 LS on LTM L1 intra and inter-frequency measurements | OPPO |
R1-2404830 | Draft reply LS on LTM L1 intra and inter-frequency measurements | OPPO |
R1-2404842 | Discussion on Sidelink Feature Co-configuration | OPPO |
R1-2404843 | Draft reply LS on Sidelink Feature Co-configuration | OPPO |
R1-2404848 | Discussion on LS from RAN4 on SL positioning measurements | OPPO |
R1-2404849 | Draft reply LS to RAN4 on SL positioning measurements | OPPO |
R1-2404851 | Discussion on LS from RAN2 on SSB time offset | OPPO |
R1-2404909 | Draft LS reply on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | Nokia |
R1-2404930 | Discussion on LS on LTM L1 intra and inter-frequency measurements | Nokia |
R1-2404933 | Draft Reply LS on parameters used for CG RACH-less Handover | InterDigital, Inc. |
R1-2404948 | Reply LS on UE Capability for Asymmetric BW for less than 5 MHz | Huawei |
R1-2404949 | Discussions on LS on Sidelink Feature Co-configuration | Huawei, HiSilicon |
R1-2404950 | Discussion on RAN2 LS to RAN1 on bandwidth aggregation | Huawei, HiSilicon |
R1-2404951 | Discussion on RAN4 LS on SL positioning measurements | Huawei, HiSilicon |
R1-2404952 | Discussion on the LS on UE capability for NW verified location | Huawei, HiSilicon |
R1-2404953 | Discussion on LS reply to SA2 on data collection for direct positioning | Huawei, HiSilicon |
R1-2404956 | Discussion of RAN2 LS on reference point for SSB-TimeOffset | Ericsson |
R1-2404969 | Draft LS reply on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Intel Corporation |
R1-2404978 | Draft reply LS on zenith angle value range on SLPP agreements | ZTE |
R1-2404979 | Discussion on zenith angle value range on SLPP agreements | ZTE |
R1-2404980 | Draft reply LS on SL positioning measurements | ZTE |
R1-2404981 | Discussion on SL positioning measurements | ZTE |
R1-2404983 | Discussion on SRS BW aggregation | ZTE |
R1-2404984 | Draft reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | ZTE |
R1-2404985 | Discussion on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | ZTE |
R1-2405007 | Draft reply LS on LTM L1 intra and inter-frequency measurements | CATT |
R1-2405018 | Draft LS reply on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning | NTT DOCOMO, INC. |
R1-2405019 | Discussion on UE Capability for Asymmetric BW for less than 5 MHz | NTT DOCOMO, INC. |
R1-2405063 | Discussion of RAN4 LS on 3T6R and 4T6R antenna switching SRS | Nokia |
R1-2405129 | Draft Reply to LS on UE Capability for Asymmetric BW for less than 5 MHz | Qualcomm Incorporated |
R1-2405130 | Discussion for RAN4 LS on UE Capability for Asymmetric BW for less than 5 MHz | Qualcomm Incorporated |
R1-2405131 | Discussion of RAN4 LS on 3T6R and 4T6R antenna switching SRS | Qualcomm Incorporated |
R1-2405132 | Draft Reply to LS on reference point for SSB-TimeOffset | Qualcomm Incorporated |
R1-2405133 | Draft Reply to LS to RAN1 on bandwidth aggregation | Qualcomm Incorporated |
R1-2405134 | Draft Reply to LS on SL positioning measurements | Qualcomm Incorporated |
R1-2405135 | Draft Reply to LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Qualcomm Incorporated |
R1-2405136 | Further discussion on RAN1 issues trigged by LS on Parallel Tx Capability | Qualcomm Incorporated |
R1-2405186 | Discussion on RAN2 LS regarding type 3 PHR | ASUSTeK |
R1-2405279 | Discussion on PRACH mask index handling for MSG1 repetition | Nokia |
R1-2405285 | Discussion on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Ericsson |
R1-2405286 | Discussion on LS to RAN1 on bandwidth aggregation | Ericsson |
R1-2405287 | Discussion on LS on SL positioning measurements | Ericsson |
R1-2405302 | Discussion on RAN4 LS on 3T6R and 4T6R SRS antenna switching | Ericsson |
R1-2405322 | Discussion on the reply of LS on reference point for SSB-TimeOffset | Huawei, HiSilicon |
R1-2405323 | Discussion on the RAN2 LS on the LTM UE capability | Huawei, HiSilicon |
R1-2405326 | Discussion on the reply of LS on parameters used for CG RACH-less Handover | Huawei, HiSilicon |
R1-2405329 | Discussion on RAN2 LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Huawei, HiSilicon |
R1-2405330 | Discussion on type 3 PH value for the serving cell configured with mTRP | Huawei, HiSilicon |
R1-2405331 | Discussion on 3T6R and 4T6R antenna switching SRS | Huawei, HiSilicon |
R1-2405343 | Discussion of RAN2 LS on reference point for SSB-TimeOffset | Ericsson |
R1-2405400 | Summary of offline discussion on reply RAN2 LS on type 3 PH value for the serving cell configured with mTRP | Moderator (MediaTek Inc.) |
R1-2405647 | Summary of discussion on 3T6R and 4T6R antenna switching SRS | Moderator (Huawei) |
R1-2405684 | FL summary #1 of further discussion on RAN1 issues trigged by LS on Parallel Tx Capability | Moderator (Qualcomm) |
R1-2405733 | FL summary #2 of further discussion on RAN1 issues trigged by LS on Parallel Tx Capability | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2404065 | Discussion on intra-UE multiplexing and prioritization | Samsung |
R1-2404066 | Correction on UCI multiplexing in a PUSCH transmission | Samsung |
R1-2404067 | Discussion on multiplexing HARQ-ACK in a PUSCH transmission | Samsung |
R1-2404068 | Correction on multiplexing HARQ-ACK in a PUSCH transmission | Samsung |
R1-2404069 | Draft CR on HARQ-ACK skipping for BWP switching | Samsung |
R1-2404070 | Discussion on HARQ-ACK skipping for BWP switching | Samsung |
R1-2404071 | Correction on initial BWP configuration for RedCap UEs | Samsung |
R1-2404072 | Discussion on initial BWP configuration for RedCap UEs | Samsung |
R1-2404073 | Draft CR on PUSCH repetition with available slot counting | Samsung |
R1-2404074 | Discussion on mDCI based mTRP out-of-order operation | Samsung |
R1-2404075 | Draft CR on mDCI based mTRP out-of-order operation | Samsung |
R1-2404076 | Draft CR on mDCI based mTRP out-of-order operation (mirror on Rel-17) | Samsung |
R1-2404077 | Draft CR on mDCI based mTRP out-of-order operation (mirror on Rel-18) | Samsung |
R1-2404078 | Discussion on PTRS-DMRS association field for Rel-17 UL multi-TRP PUSCH repetition | Samsung |
R1-2404079 | Draft CR on PTRS-DMRS association field for Rel-17 UL multi-TRP PUSCH repetition (Rel-17 spec) | Samsung |
R1-2404080 | Draft CR on PTRS-DMRS association field for Rel-17 UL multi-TRP PUSCH repetition (Rel-18 spec) | Samsung |
R1-2404210 | Correction on SSB to CG-SDT PUSCH mapping | ZTE |
R1-2404226 | Discussion on HARQ-ACK generation for BWP switching | ZTE |
R1-2404227 | Discussion on the multiplexing prioritization for a PUSCH without a TB | ZTE |
R1-2404228 | Draft CR on the configuration of UL HARQ processes | ZTE |
R1-2404229 | Discussion on UCI multiplexing in Msg3 PUSCH | ZTE |
R1-2404238 | Correction on timing of Msg3 retransmission in NTN | ZTE |
R1-2404249 | Discussion on joint TCI configuration for SRS not sharing indicated TCI | ZTE |
R1-2404250 | Draft CR on joint TCI configuration for SRS not sharing indicated TCI | ZTE |
R1-2404251 | Draft CR on joint TCI configuration for SRS not sharing indicated TCI (mirror on Rel-18) | ZTE |
R1-2404269 | Views on multiplexing UCI on MSG3 PUSCH | Apple |
R1-2404362 | Draft CR on UL TX spatial filter determination for SRS transmission in unified TCI framework | CATT |
R1-2404363 | Correction on default beam for UL transmission in unified TCI framework | CATT |
R1-2404364 | Correction on power control for UL transmission in unified TCI framework | CATT |
R1-2404365 | Correction on PHR for the serving cell configured with mTRP | CATT |
R1-2404479 | On not multiplexing UCI on MSG3 PUSCH | Nokia, CATT, Ericsson |
R1-2404480 | Clarification on not multiplexing UCI on MSG3 PUSCH | Nokia, CATT, Ericsson |
R1-2404911 | Correction to Sidelink resource allocation mode 2 | TOYOTA InfoTechnology Center |
R1-2404912 | Correction to Sidelink resource allocation mode 2 | TOYOTA InfoTechnology Center |
R1-2404913 | Correction to Sidelink resource allocation mode 2 | TOYOTA InfoTechnology Center |
R1-2404945 | Discussion on overlapping issues related to Msg3 | Huawei, HiSilicon |
R1-2404947 | Clarification on the maximum number of CORESET and search space set in TS38.213 | Huawei, HiSilicon |
R1-2404954 | Draft CR for overlapping between msg3 PUSCH and PUCCH | Samsung |
R1-2404961 | Correction on uplink resource allocation type 0 for configured grant | Sharp |
R1-2405013 | Draft CR on MCS table for broadcast PDSCH | CMCC |
R1-2405118 | SRS Tx occasion and power scaling | Ericsson, Nokia |
R1-2405189 | Discussion on Rel-17 RedCap remaining issues | ZTE, Sanechips |
R1-2405190 | Draft Rel-17 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405191 | Draft shadow Rel-18 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405260 | Discussion of missing support for NTN in Rel-17 RAN1 specifications | Nokia |
R1-2405270 | Draft CR for 38.214 on unified TCI state | Ericsson, Samsung, MediaTek Inc. |
R1-2405291 | Correction on Multi-Resource SRS Port Power Scaling | Ericsson, Nokia |
R1-2405316 | Discussion on DCI ordering issues | Huawei, HiSilicon |
R1-2405317 | Corrections on DCI ordering issues | Huawei, HiSilicon |
R1-2405318 | Discussion on TPC accumulation for SRS | Huawei, HiSilicon |
R1-2405319 | Draft CR on TPC accumulation for SRS | Huawei, HiSilicon |
R1-2405337 | Ambiguity in the RAR window start timine determination | Nokia |
R1-2405338 | Clarification to RA response window start time | Nokia |
R1-2405352 | Clarification on the maximum number of CORESET and search space set in TS38.213 | Huawei, HiSilicon |
R1-2405399 | Summary of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2405420 | [117-Pre-R18-NR] Summary#1 of UCI on Msg3 PUSCH | Nokia (Moderator) |
R1-2405466 | Draft CR for 38.214 on unified TCI state | Ericsson, Samsung, MediaTek Inc., Nokia |
R1-2405467 | Moderator Summary #1 on joint TCI configuration for SRS not sharing indicated TCI | Moderator (ZTE) |
R1-2405479 | Summary on mDCI based mTRP out-of-order operation | Moderator (Samsung) |
R1-2405480 | Summary on PTRS-DMRS association field for Rel-17 UL multi-TRP PUSCH repetition | Moderator (Samsung) |
R1-2405513 | Draft CR for 38.214 on unified TCI state | Ericsson, Samsung, MediaTek Inc., Nokia |
R1-2405514 | CR on joint TCI configuration for SRS not sharing indicated TCI | ZTE, Samsung |
R1-2405515 | CR on joint TCI configuration for SRS not sharing indicated TCI | ZTE, Samsung |
R1-2405518 | Moderator summary of unified TCI state correction | Moderator (Ericsson) |
R1-2405521 | [117-Pre-R18-NR] Summary#2 of UCI on Msg3 PUSCH | Nokia (Moderator) |
R1-2405524 | Summary#1 of discussion on RedCap initial DL BWP and NCD-SSB | Moderator (ZTE) |
R1-2405532 | Summary #1 of discussion on DCI ordering issues | Moderator (Huawei) |
R1-2405533 | Summary #2 of discussion on DCI ordering issues | Moderator (Huawei) |
R1-2405534 | Summary of discussion on clarification on the maximum number of CORESETs and search space sets | Moderator (Huawei) |
R1-2405540 | Draft CR for 38.211 for capturing NR over NTN operation | Moderator (Nokia) |
R1-2405541 | Draft CR for 38.213 for capturing NR over NTN operation | Moderator (Nokia) |
R1-2405542 | Draft CR for 38.214 for capturing NR over NTN operation | Moderator (Nokia) |
R1-2405543 | Discussion on updating references to capture Rel-17 NR over NTN | Moderator (Nokia) |
R1-2405551 | Summary of discussion on Draft CR on UL TX spatial filter determination for SRS transmission in unified TCI framework | Moderator (CATT) |
R1-2405552 | Summary of discussion on Correction on default beam for UL transmission in unified TCI framework | Moderator (CATT) |
R1-2405553 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
R1-2405559 | Summary of discussion on intra-UE multiplexing and prioritization | Moderator (Samsung) |
R1-2405560 | Summary of discussion on multiple DAI values for a UL DCI format | Moderator (Samsung) |
R1-2405573 | CR for 38.214 on unified TCI state | Ericsson, Samsung, MediaTek Inc., Nokia |
R1-2405574 | CR for 38.214 on unified TCI state | Ericsson, Samsung, MediaTek Inc., Nokia |
R1-2405575 | Summary#1 on SSB to CG-SDT PUSCH mapping | Moderator (ZTE) |
R1-2405579 | Summary on PTRS-DMRS association field for Rel-17 UL multi-TRP PUSCH repetition (Round 2) | Moderator (Samsung) |
R1-2405590 | Final summary of discussion on clarification on the maximum number of CORESETs and search space sets | Moderator (Huawei) |
R1-2405591 | Correction to Sidelink resource allocation mode 2 | Toyota ITC |
R1-2405596 | Summary#2 of discussion on multiple DAI values for a UL DCI format | Moderator (Samsung) |
R1-2405603 | Summary of discussion on Type-2 HARQ-ACK codebook and DL BWP change | Moderator (Samsung) |
R1-2405604 | Summary#2 of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2405605 | Discussion on updating references to capture Rel-17 NR over NTN, second round | Moderator (Nokia) |
R1-2405614 | Correction on mDCI based mTRP out-of-order operation | Samsung, Nokia |
R1-2405615 | Correction on mDCI based mTRP out-of-order operation | Samsung, Nokia |
R1-2405616 | Correction on mDCI based mTRP out-of-order operation | Samsung, Nokia |
R1-2405620 | Clarification on not multiplexing UCI on MSG3 PUSCH | Nokia, CATT, Ericsson, Samsung |
R1-2405639 | Summary#2 of discussion on RedCap initial DL BWP and NCD-SSB | Moderator (ZTE) |
R1-2405640 | Summary#2 on SSB to CG-SDT PUSCH mapping | Moderator (ZTE) |
R1-2405642 | Draft CR for 38.211 for capturing NR over NTN operation | Moderator (Nokia) |
R1-2405643 | Draft CR for 38.213 for capturing NR over NTN operation | Moderator (Nokia) |
R1-2405644 | Clarification on not multiplexing UCI on MSG3 PUSCH | Nokia, CATT, Ericsson, Huawei, HiSilicon, Samsung, ZTE |
R1-2405649 | Correction on Type-2 HARQ-ACK codebook and DL BWP change | Moderator (Samsung), ZTE, vivo |
R1-2405650 | CR on UL TX spatial filter determination | Moderator (CATT), ZTE, Samsung, New H3C |
R1-2405651 | CR on UL TX spatial filter determination | Moderator (CATT), ZTE, Samsung, New H3C |
R1-2405652 | Correction on SSB to CG-SDT PUSCH mapping | Moderator (ZTE) |
R1-2405653 | Summary on Msg3 retransmission timing | Moderator (ZTE) |
R1-2405654 | Correction on timing of Msg3 retransmission in NTN | Moderator (ZTE) |
R1-2405660 | Correction on mDCI based mTRP out-of-order operation | Samsung, Nokia |
R1-2405661 | Correction on mDCI based mTRP out-of-order operation (mirror on Rel-17) | Samsung, Nokia |
R1-2405662 | Correction on mDCI based mTRP out-of-order operation (mirror on Rel-18) | Samsung, Nokia |
R1-2405686 | Session notes for 7 Pre-Rel-18 NR Maintenance (ad-hoc session) | Ad-Hoc Chair (Huawei) |
R1-2405700 | Correction on multiplexing HARQ-ACK in a PUSCH transmission | Moderator (Samsung), Ericsson, Nokia, Huawei, HiSilicon, ZTE |
R1-2405709 | Correction on SSB to CG-SDT PUSCH mapping | Moderator(ZTE), Samsung, Ericsson, vivo, Xiaomi, New H3C |
R1-2405710 | Correction on SSB to CG-SDT PUSCH mapping | Moderator(ZTE), Samsung, Ericsson, vivo, Xiaomi, New H3C |
R1-2405711 | Rel-17 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405712 | Rel-18 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405717 | Draft Rel-17 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405718 | Draft shadow Rel-18 RedCap Correction on initial DL BWP | ZTE, Sanechips |
R1-2405720 | Correction on PTRS-DMRS association field in DCI format 0_1 and DCI format 0_2 | Huawei |
R1-2405726 | Final summary of discussion on DCI ordering issues | Moderator (Huawei) |
R1-2405737 | Final summary of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2405744 | Correction on PTRS-DMRS association field in DCI format 0_1 and DCI format 0_2 | Huawei, Samsung |
R1-2405752 | Rel-16 editorial corrections for TS 38.212 | Huawei |
R1-2405753 | Rel-17 editorial corrections for TS 38.212 | Huawei |
R1-2405756 | Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) | Huawei |
R1-2405757 | Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-18) | Huawei |
R1-2405758 | Rel-17 editorial corrections for TS 38.212 (mirrored to Rel-18) | Huawei |
R1-2405762 | Rel-17 editorial corrections for TS 38.213 | Samsung |
R1-2405764 | Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) | Samsung |
R1-2405766 | Rel-17 editorial corrections for TS 38.214 | Nokia |
R1-2405767 | Rel-17 editorial corrections for TS 38.214 – mirror to Rel-18 | Nokia |
R1-2405769 | Corrections to NTN operation | Ericsson |
R1-2405770 | Corrections to NTN operation | Ericsson |
R1-2405771 | Rel-17 editorial corrections for TS 38.214 | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2405747 | Alignment corrections for TS38.215 | Intel Corporation |
R1-2405748 | Maintenance of NR Sidelink operation on shared spectrum | Ericsson |
R1-2405749 | Corrections to positioning enhancements | Ericsson |
R1-2405750 | Corrections to sidelink enhancements | Ericsson |
R1-2405751 | Corrections on Rel-18 Multi-carrier enhancements in 38.212 | Huawei |
R1-2405754 | Rel-18 editorial corrections for TS 38.212 | Huawei |
R1-2405755 | Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 | Huawei |
R1-2405759 | Maintenance of multi-carrier enhancements for NR | Samsung |
R1-2405760 | Maintenance of MIMO Evolution for Downlink and Uplink | Samsung |
R1-2405761 | Maintenance of expanded and improved NR positioning | Samsung |
R1-2405763 | Rel-18 editorial corrections for TS 38.213 | Samsung |
R1-2405765 | Rel-18 editorial corrections for TS 38.214 | Nokia |
R1-2405768 | Corrections on the support for Expanded and Improved NR Positioning | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2403854 | FL Summary on Maintenance of 8TX (NR_MIMO_evo_DL_UL); 1st Round | Moderator (InterDigital, Inc.) |
R1-2403855 | FL Summary on Maintenance of 8TX (NR_MIMO_evo_DL_UL); 2nd Round | Moderator (InterDigital, Inc.) |
R1-2403922 | Corrections on Rel-18 MBS to TS 38.212 | Huawei, HiSilicon |
R1-2403923 | Corrections on Rel-18 MBS to TS 38.213 | Huawei, HiSilicon |
R1-2403924 | Corrections on Rel-18 MBS to TS 38.214 | Huawei, HiSilicon |
R1-2403927 | Discussion on the pathloss RS in LTM TCI state | Huawei, HiSilicon |
R1-2403928 | Discussion on the CFRA triggered by cell switch command | Huawei, HiSilicon |
R1-2403937 | Discussion on FR2-NTN PRACH Table for NTN above 10GHz | Huawei, HiSilicon |
R1-2403958 | Maintenance of Rel-18 Multicarrier Enhancements | Huawei, HiSilicon |
R1-2403959 | Remaining issues of Rel-18 positioning | Huawei, HiSilicon |
R1-2403970 | Correction on collision handling of positioning SRS with frequency hopping in TDD systems | Intel Corporation |
R1-2403971 | Corrections on positioning SRS with frequency hopping | Intel Corporation |
R1-2403982 | Corrections on power headroom report for dynamic waveform switching | Intel Corporation |
R1-2404013 | Corrections for Unified TCI update by DCI format 1_3 | Spreadtrum Communications |
R1-2404014 | Maintenance of NTN above 10GHz | Spreadtrum Communications |
R1-2404052 | Maintenance on Expanded and Improved NR Positioning | Nokia |
R1-2404081 | Remaining issues on network energy saving | Samsung |
R1-2404082 | Correction on power assumption for type 1 spatial domain adaptation | Samsung |
R1-2404083 | Correction on CSI-RS EPRE for type 1 spatial domain adaptation | Samsung |
R1-2404084 | Correction on Cell DRX operation for SRS | Samsung |
R1-2404085 | Remaining Issues for NR Sidelink Evolution | Samsung |
R1-2404086 | Draft CR for Correcting S-SSB Transmission in Non-Anchor RB Set | Samsung |
R1-2404087 | Correction of TB disabling for multi-cell scheduling | Samsung |
R1-2404088 | Correction of indicated unified TCI states for non-scheduled cells in multi-cell scheduling | Samsung |
R1-2404089 | Draft CR on HARQ-ACK skipping for DL/UL BWP switching in multi-cell scheduling | Samsung |
R1-2404090 | Summary for Rel-18 MIMO CSI maintenance | Moderator (Samsung) |
R1-2404091 | Draft CR on applying apply-IndicatedTCIState to PDCCH repetition | Samsung |
R1-2404092 | Discussions on cell-specific BFR under eUTCI | Samsung |
R1-2404093 | Draft CR on determining a BFD RS set with two indicated TCI states | Samsung |
R1-2404094 | Draft CR on cell-specific beam resetting for MDCI MTRP under eUTCI | Samsung |
R1-2404095 | Discussion on mDCI based STx2P out-of-order operation | Samsung |
R1-2404096 | Draft CR on mDCI based STx2P out-of-order operation | Samsung |
R1-2404097 | Discussion on twoPHRmode for single-DCI based STx2P | Samsung |
R1-2404098 | Discussion on TDM or non-TDM 8-port SRS | Samsung |
R1-2404099 | Draft CR on TDM or non-TDM 8-port SRS | Samsung |
R1-2404100 | Discussion on relevant UE capability on supported codebook for TDM or non-TDM 8-port SRS | Samsung |
R1-2404147 | Draft CR on HARQ-ACK codebook for DL BWP switching | vivo |
R1-2404148 | Clarification on COT sharing flag in 38.212 | vivo |
R1-2404149 | Clarification on DMRS symbol in 38.211 | vivo |
R1-2404150 | Clarification on CPE determination for PSCCH/PSSCH transmission on a resumed COT in 38.214 | vivo |
R1-2404151 | Clarification on guardRB handling in 38.214 | vivo |
R1-2404152 | Clarification on CSI request in 38.214 | vivo |
R1-2404153 | Draft CR on PRS for carrier phase positioning | vivo |
R1-2404154 | Draft CR on SRS bandwidth aggregation for positioning measurements | vivo |
R1-2404155 | Draft CR on SRS frequency hopping for positioning | vivo |
R1-2404156 | Draft CR on Sidelink congestion control in dedicated SL PRS resource pool | vivo |
R1-2404157 | Draft CR on RRC parameter correction for enhanced DMRS | vivo |
R1-2404158 | Discussion on M-DCI based PUSCH+PUSCH STxMP | vivo |
R1-2404159 | Draft CR on M-DCI based PUSCH+PUSCH STxMP | vivo |
R1-2404160 | Maintenance on Further NR Coverage Enhancements | vivo |
R1-2404161 | Draft CR on P_CMAX report for assumed PUSCH | vivo |
R1-2404162 | Draft CR on timing assumption between source and target cells for R18 LTM cell switch | vivo |
R1-2404211 | Further discussion on LS on the system parameters for NTN above 10 GHz | ZTE |
R1-2404218 | Draft CR for 38.211 on Introduction of FR2-NTN | THALES |
R1-2404230 | Discussion on the maximal HARQ process numbers for TN in FR1 and FR2-1 | ZTE, CMCC, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Verizon |
R1-2404231 | Correction on multiplexing HARQ-ACK in a PUSCH with repetitions | ZTE |
R1-2404232 | Draft CR on search space of DCI format 0_3 and DCI format 1_3 | ZTE |
R1-2404233 | Discussion on HARQ-ACK generation in case of DL BWP switching | ZTE |
R1-2404234 | Draft CR on HARQ-ACK generation in case of DL BWP switching | ZTE |
R1-2404235 | Draft CR on Precoding information and number of layers in DCI format 0_3 | ZTE |
R1-2404236 | Draft CR on PRACH mask index handling for MSG1 repetition | ZTE |
R1-2404237 | Discussion on PRACH mask index handling for MSG1 repetition | ZTE |
R1-2404252 | Draft CR on beam collision between PDSCH with offset less than a threshold and PDCCH in S-DCI based MTRP | ZTE |
R1-2404253 | Draft CR on beam collision between PDSCH with offset less than a threshold and PDCCH in M-DCI based MTRP | ZTE |
R1-2404254 | Draft CR on implicit BFD-RS determination for S-DCI based MTRP | ZTE |
R1-2404255 | Discussion on CFRA triggered by LTM Cell Switch Command MAC CE | ZTE |
R1-2404256 | Draft CR on CFRA triggered by LTM Cell Switch Command MAC CE applied for NTN | ZTE |
R1-2404257 | Draft CR on timeline for PRACH transmission triggered by LTM Cell Switch Command MAC CE | ZTE |
R1-2404258 | Discussion on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE | ZTE |
R1-2404259 | Draft CR on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE | ZTE |
R1-2404260 | Discussion on applying TCI state indicated in LTM Cell Switch Command MAC CE to a list of CCs | ZTE |
R1-2404322 | Draft CR for correction on CSI processing criteria for new NES capability signaling in TS38.214 | Apple (UK) Limited |
R1-2404343 | Draft CR on 38213 on RACH procedure triggered by LTM cell switch command MAC CE | Lenovo |
R1-2404351 | Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension | Moderator (MediaTek Inc.) |
R1-2404366 | Correction on the definition of sidelink PRS channel busy ratio | CATT, CICTCI |
R1-2404367 | Maintenance on NR Network-Controlled Repeaters | CATT |
R1-2404368 | Correction on RRC parameters for NR Rel-18 MIMO in TS 38.214 | CATT |
R1-2404369 | Correction on RRC parameters for NR Rel-18 MIMO in TS 38.213 | CATT |
R1-2404370 | Draft CR on configuration of TCI states for SRS | CATT |
R1-2404371 | Correction on the CPE starting position for SL transmissions within a COT | CATT, CICTCI |
R1-2404372 | Correction on the UE procedure for transmitting PSCCH in dedicated SL PRS resource pool | CATT, CICTCI |
R1-2404373 | Discussion on the higher layer parameters in a dedicated SL PRS resource pool | CATT, CICTCI |
R1-2404374 | Correction on the determination of intra-cell guard band for SL-U | CATT, CICTCI |
R1-2404375 | Correction on the frequency resource of a resource pool for SL-U | CATT, CICTCI |
R1-2404376 | Maintenance on Multi-Carrier Enhancements for NR | CATT |
R1-2404377 | Draft CR on maxNrofCodeWordsScheduledByDCI for second Type-2 HARQ-ACK codebook | CATT |
R1-2404378 | Draft CR on HARQ-ACK information skipping due to BWP change for second Type-2 HARQ-ACK codebook | CATT |
R1-2404379 | Draft CR on information field determination for DCI 0_3/1_3 in case of BWP change | CATT |
R1-2404380 | Correction on RRC parameters for NR mobility enhancements in TS 38.213 | CATT |
R1-2404381 | Draft CR on PRACH mask index handling for MSG1 repetition | CATT |
R1-2404419 | Remaining issues on PRACH coverage enhancement | China Telecom |
R1-2404420 | Draft CR on PRACH mask index for PRACH transmission with preamble repetitions | China Telecom |
R1-2404481 | Correction of bitwidth determination of beta_offset indicator field of DCI format 0_1 | Nokia |
R1-2404482 | Correction of UCI-onPUSCH for PUSCH scheduled by DCI format 0_1 and 0_3 | Nokia |
R1-2404581 | Correction on TA offset information for UE-based TA acquisition | Fujitsu |
R1-2404598 | Draft CR on MBS PDSCH CBW definition for Rel-18 RedCap | Xiaomi |
R1-2404599 | Draft CR on CAPC condition for COT resuming for SL-U | Xiaomi |
R1-2404600 | Draft CR on default beam for AP CSI-RS in M-DCI based MTRP scenario with Rel-18 unified TCI state framework | Xiaomi |
R1-2404639 | Correction on PSSCH transmission decode behaviour in TS 38.214 | ZTE, Sanechips |
R1-2404640 | Correction on PSFCH resource mapping for contiguous RB resource pool in TS 38.213 | ZTE, Sanechips |
R1-2404641 | Correction on CAPC for SL in TS 37.213 | ZTE, Sanechips |
R1-2404642 | Correction on IUC in co-existence case in TS 38.214 | ZTE, Sanechips |
R1-2404643 | Correction on SL BWP configuration in TS 38.213 | ZTE, Sanechips |
R1-2404644 | Correction on parameter names for section 16.1 in TS 38.213 | ZTE, Sanechips |
R1-2404645 | Correction on parameter names for section 8.1.2.1 in TS 38.214 | ZTE, Sanechips |
R1-2404646 | Alignment for RAN2 agreement in TS38.214 | ZTE, Sanechips |
R1-2404647 | Correction on the highest sub-channel of PSSCH in TS 38.214 | ZTE, Sanechips |
R1-2404663 | Draft CR on applicable RB set(s) for COT sharing in TS 37.213 or TS 38.214 | NEC |
R1-2404673 | Draft CR on indicated TCI state in TS38.214 | NEC |
R1-2404680 | Discussion on UCI multiplexing for STxMP | |
R1-2404681 | Draft CR on UCI multiplexing for STxMP | |
R1-2404708 | Discussion on precoding determination of STxMP SDM/SFN scheme in TS38.211 | ZTE |
R1-2404709 | Draft CR on precoding determination of STxMP SDM/SFN scheme in TS38.211 | ZTE |
R1-2404710 | Discussion on SRS transmission for NCB PUSCH in STxMP SDM/SFN scheme in TS 38.214 | ZTE |
R1-2404711 | Draft CR on SRS transmission for NCB PUSCH in STxMP SDM/SFN scheme in TS 38.214 | ZTE |
R1-2404716 | Discussion on PRACH association indicator field in PDCCH order in TS 38.212 | ZTE |
R1-2404717 | Draft CR on PRACH association indicator field in PDCCH order in TS 38.212 | ZTE |
R1-2404718 | Draft CR on priority for Legacy CSI report and LTM CSI report in TS 38.213 | ZTE |
R1-2404719 | Draft CR on clarifying the unit of BWPswitchDelay | ZTE |
R1-2404720 | Discussion on BWPswitchDelay | ZTE |
R1-2404729 | Correction on Further NR Mobility Enhancements | Langbo |
R1-2404730 | Correction on PDCCH Search Space for Rel-18 Multi-Carrier Enhancements | Langbo |
R1-2404731 | Correction on Minimum Scheduling Offset for Rel-18 Multi-Carrier Enhancements | Langbo |
R1-2404741 | Maintenance on IoT NTN enhancements | Nokia, Nokia Shanghai Bell |
R1-2404747 | Draft CR for 38.213 on deactivation of candidate TCI states | Ericsson |
R1-2404748 | Draft CR for 38.213 on RACH procedure triggred by LTM cell switch | Ericsson |
R1-2404749 | Draft CR for 38.213 on signaling of TCI state in LTM cell switch command | Ericsson |
R1-2404750 | Draft CR for 38.213 on TCI state applied for CORESETs other than CORESET 0 | Ericsson |
R1-2404751 | Draft CR for 38.214 on spCellInclusion | Ericsson |
R1-2404752 | Draft CR for 38.214 on simultaneous UL transmission | Ericsson |
R1-2404765 | Discussion for clarifications for time offset in preamble transmission | ETRI |
R1-2404790 | FL summary 1 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2404791 | FL summary 2 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2404812 | Draft CR on PDSCH reception for MBS | ZTE, CBN |
R1-2404823 | Draft CR for Rel-18 two-TA enhancement | OPPO |
R1-2404831 | Draft CR for correction on contention window adjustment | OPPO |
R1-2404832 | Draft CR for correction on CPE starting position for PSCCH/PSSCH | OPPO, Samsung |
R1-2404833 | Draft CR for correction on CPE starting position for PSFCH | OPPO |
R1-2404834 | Draft CR for editorial corrections of TS 38.214 | OPPO |
R1-2404835 | Draft CR on RRC alignments for Rel-18 SL operation (TS 37.213) | OPPO |
R1-2404836 | Draft CR on RRC alignments for Rel-18 SL operation (TS 38.211) | OPPO |
R1-2404837 | Draft CR on RRC alignments for Rel-18 SL operation (TS 38.212) | OPPO |
R1-2404838 | Draft CR on RRC alignments for Rel-18 SL operation (TS 38.213) | OPPO |
R1-2404839 | Draft CR on RRC alignments for Rel-18 SL operation (TS 38.214) | OPPO |
R1-2404840 | Draft CR on RRC alignments for Rel-18 SL operation (TS 38.215) | OPPO |
R1-2404844 | Draft CR for correction on candidate multi-slot resource in partial sensing | OPPO |
R1-2404845 | Draft CR for correction on PSFCH power control | OPPO, ZTE, Sanechips |
R1-2404846 | Draft CR for correction on PSSCH rate matching | OPPO |
R1-2404847 | Draft CR for correction on PSSCH decoding behaviour | OPPO |
R1-2404850 | Discussion on remaining issue for FR2 NTN | OPPO |
R1-2404855 | Draft CR on Type-2 field blocks in DCI 1_3/0_3 | OPPO |
R1-2404856 | Draft CR on number of MCS/NDI/RV blocks for TB-2 in DCI 1_3 | OPPO |
R1-2404886 | Discussion on EPRE of CSI-RS and PDSCH for NES | LG Electronics |
R1-2404917 | Maintenance on NR MIMO Evolution for Downlink and Uplink | Nokia |
R1-2404922 | Draft CR on multicast transmissions for Rel-18 RedCap in INACTIVE mode | Nokia |
R1-2404927 | Draft CR for CFRA procedure triggered by LTM cell switch command | Nokia |
R1-2404928 | Draft CR for TCI state applied for CORESETs other than CORESET 0 in LTM | Nokia |
R1-2404929 | Draft CR for 38.214 on QCL assumption after LTM cell switch command | Nokia |
R1-2404936 | Discussion of PRACH configurations for FR2-NTN in paired spectrum | Ericsson |
R1-2404944 | Correction on PSFCH power control | Huawei, HiSilicon |
R1-2404946 | Correction on HARQ-ACK multiplexing on a PUSCH repetition | Huawei, HiSilicon |
R1-2404974 | Draft CR on SL-U TBS determination | Panasonic |
R1-2404975 | Maintenance of NR Sidelink unlicensed spectrum | Panasonic |
R1-2404977 | Draft CR on Rel-18 Type II Doppler codebook based CSI enhancement | Beijing Xiaomi Electronics |
R1-2404982 | Draft reply LS on SRS BW aggregation | ZTE |
R1-2404986 | Correction on PRS bandwidth aggregation for 38.214 | ZTE |
R1-2404987 | Correction on SRS bandwidth aggregation in RRC_INACTIVE for 38.214 | ZTE |
R1-2404988 | Draft CR for dropping rule on SRS bandwidth aggregation | ZTE |
R1-2404989 | Draft CR on PRS processing for bandwidth aggregation | ZTE |
R1-2404990 | Correction on SRS configuration and UE behavior in validity area for LPHAP for 38.214 | ZTE |
R1-2404991 | Correction on UE behavior in validity area for LPHAP for 38.213 | ZTE |
R1-2404992 | Draft CR for carrier phase positioning | ZTE |
R1-2404993 | Draft CR for collision handling of positioning SRS with Tx hopping in TDD system | ZTE |
R1-2404994 | Discussion on collision handling of positioning SRS with Tx hopping in TDD system | ZTE |
R1-2404995 | Draft CR for RedCap UE frequency hopping | ZTE |
R1-2404996 | Draft CR for UE behavior on monitoring DCI format 3_2 | ZTE |
R1-2404997 | Discussion on UE behavior on monitoring DCI format 3_2 | ZTE |
R1-2404998 | Correction on SL positioning for 38.214 | ZTE |
R1-2404999 | Correction on SL positioning for 38.212 | ZTE |
R1-2405000 | Correction on SL positioning for 38.211 | ZTE |
R1-2405001 | Missed RRC parameters for sidelink positioning | ZTE |
R1-2405008 | Discussion on remaining issues of Rel-18 Coverage Enhancements | Ericsson |
R1-2405014 | Draft CR on MCS table for multicast PDSCH in RRC_INACTIVE mode | CMCC |
R1-2405020 | Maintenance on Multi-Carrier Enhancements for NR | NTT DOCOMO, INC. |
R1-2405021 | Draft CR on beam application timing for mDCI mTRP for Rel-18 TCI framework | NTT DOCOMO, INC. |
R1-2405022 | Remaining issues on power control for M-TRP operation in NR MIMO Evolution for Downlink and Uplink | NTT DOCOMO, INC. |
R1-2405023 | Remaining issues on 8TX UL transmission in NR MIMO Evolution for Downlink and Uplink | NTT DOCOMO, INC. |
R1-2405024 | Discussion on FR2-NTN | NTT DOCOMO, INC. |
R1-2405025 | Draft CR on CAPC value for PSFCH+S-SSB for SL-U | NTT DOCOMO, INC. |
R1-2405026 | Maintenance of resource selection in MAC layer for SL-U | NTT DOCOMO, INC. |
R1-2405027 | Draft CR on sensing with two starting symbols | NTT DOCOMO, INC. |
R1-2405064 | Remaining issue on NW energy saving techniques in spatial domain | Fujitsu |
R1-2405065 | Correction on UE assumptions for CQI/PMI/RI calculation for type 1 spatial domain adaptation | Fujitsu |
R1-2405066 | Discussion on RAN4 LS on FR2-NTN aspects | Sharp |
R1-2405067 | Correction on determination of PSFCH resources for a PSSCH | Sharp |
R1-2405099 | Discussion on power offset for spatial domain adaptation for Rel-18 NES | Ericsson |
R1-2405100 | Draft CR for 38.211 on TRS occasions for idle/inactive UEs | Ericsson |
R1-2405101 | Draft CR for 38.212 on TRS occasions for idle/inactive UEs | Ericsson |
R1-2405102 | Draft CR for 38.213 on TRS occasions for idle/inactive UEs | Ericsson |
R1-2405103 | Draft CR for 38.214 on TRS occasions for idle/inactive UEs | Ericsson |
R1-2405137 | Maintenance of Rel-18 UL Tx switching | Qualcomm Incorporated |
R1-2405138 | Draft CR for indication of remaining channel occupancy duration | Qualcomm Incorporated |
R1-2405139 | Maintenance on NR MIMO Evolution for Downlink and Uplink | Qualcomm Incorporated |
R1-2405140 | Draft CR on the application time of cell DRX for NR NTN | Qualcomm Incorporated |
R1-2405192 | Discussion on R18 (e)RedCap UE remaining issues | ZTE, Sanechips |
R1-2405193 | Draft CR for eRedCap UE supporting enhanced positioning | ZTE, Sanechips |
R1-2405194 | Draft CR for eRedCap UE supporting MBS in inactive state | ZTE, Sanechips |
R1-2405195 | Draft CR for Rel-18 RedCap UE supporting MBS in inactive state | ZTE, Sanechips |
R1-2405196 | Draft CR for semi-persistent CSI report for Rel-18 NES | ZTE, Sanechips |
R1-2405197 | Draft CR for CSI report configuration for Rel-18 NES | ZTE, Sanechips |
R1-2405198 | Correction of UTO-UCI bit generation in Rel-18 XR | ZTE, Sanechips |
R1-2405203 | Parameter name alignment on 8Tx PUSCH | ASUSTeK |
R1-2405204 | Parameter name alignment on 8Tx PUSCH | ASUSTeK |
R1-2405220 | Discussion on HARQ-ACK skipping for Rel-18 multi-cell scheduling | Lenovo |
R1-2405221 | Draft CR on HARQ-ACK skipping for Rel-18 multi-cell scheduling | Lenovo |
R1-2405225 | Draft CR for 38.214 on CSI report priority | Ericsson, Huawei, HiSilicon |
R1-2405228 | Draft CR on T_offset for UL Tx switching | ZTE, Apple, CATT, Ericsson, LG Electronics, Nokia, Qualcomm Incorporated, vivo, OPPO |
R1-2405229 | Align RRC parameters used in TDCP definition | Ericsson |
R1-2405230 | Align RRC parameters for DMRS | Ericsson |
R1-2405231 | Align UE capability parameters for DMRS | Ericsson |
R1-2405232 | Clarification on DMRS antenna port table | Ericsson |
R1-2405233 | Align RRC parameter for multiuser scheduling | Ericsson |
R1-2405256 | Correction on multiplexing HARQ-ACK in a PUSCH with repetitions | Samsung, Ericsson |
R1-2405261 | Discussion of missing support for NTN in Rel-18 RAN1 specifications | Nokia |
R1-2405262 | On FR2-NTN inclusion to specifications | Nokia |
R1-2405266 | Feature lead summary 1 on FR2-NTN discussions | Moderator (Nokia) |
R1-2405267 | Feature lead summary 2 on FR2-NTN discussions | Moderator (Nokia) |
R1-2405268 | Draft CR for 38.212 on the condition for the PRACH association indicator field | Ericsson |
R1-2405278 | Remaining issues on further NR coverage enhancements | Nokia |
R1-2405288 | Draft CR for correction to SRS for positioning with tx hopping in 38.211 | Ericsson |
R1-2405289 | Draft CR for correction to SRS for positioning with tx hopping in 38.214 | Ericsson |
R1-2405292 | Corrections for When UL 8 Tx Layer Limits Exceed 4 Layers | Ericsson |
R1-2405293 | Corrections on UL 8 Tx Configured Grant Layer Limits and 8 Tx Layer Configuration | Ericsson |
R1-2405294 | Correction on 8 Tx UL MIMO Codebook Configuration Constraints | Ericsson |
R1-2405295 | Correction on PT-RS Coherence Conditions for 8 Tx | Ericsson |
R1-2405305 | Corrections to the Pathloss RS in LTM TCI state in TS38.213 | Huawei, HiSilicon |
R1-2405306 | Corrections to the timeline of CFRA triggered by cell switch command in TS38.213 | Huawei, HiSilicon |
R1-2405307 | Corrections to the beam of CFRA triggered by cell switch command in TS38.213 | Huawei, HiSilicon |
R1-2405308 | Correction on SCell dormancy indication case 2 in case of BWP switching | Huawei, HiSilicon |
R1-2405309 | Correction on type 2 HARQ-ACK codebook skipping in case of BWP switching | Huawei, HiSilicon |
R1-2405310 | Correction on PDCCH overbooking in TS 38.213 | Huawei, HiSilicon |
R1-2405311 | Corrections on Rel-18 UL Tx switching with two configured bands | Huawei, HiSilicon |
R1-2405312 | Corrections on Rel-18 UL Tx switching period determination | Huawei, HiSilicon |
R1-2405313 | Correction to 38.202 on support of combination of SL CA and SL positioning | Huawei, HiSilicon |
R1-2405314 | Correction to 38.213 on support of DCI formats for SL positioning | Huawei, HiSilicon |
R1-2405315 | Correction to 38.211 on the transmission counter | Huawei, HiSilicon |
R1-2405320 | Correction to the impact from DL reception on the affected bands | Huawei, HiSilicon |
R1-2405321 | Correction to the provision of RTD in SL positioning | Huawei, HiSilicon |
R1-2405324 | Corrections to the UL/SUL indication for CFRA in TS38.213 | Huawei, HiSilicon |
R1-2405325 | Corrections to the default beam determination after cell switch in TS38.214 | Huawei, HiSilicon, Ericsson |
R1-2405327 | Correction to the RRC parameters for CG RACH-less handover | Huawei, HiSilicon |
R1-2405328 | Correction to the UL power control of PUSCH for CG RACH-less handover | Huawei, HiSilicon |
R1-2405332 | Corrections to the first UL transmission after LTM cell switch in TS38.213 | Huawei, HiSilicon |
R1-2405333 | Correction on PRACH association indicator in PDCCH order in 38.212 | Huawei, HiSilicon, Google, Ericsson |
R1-2405334 | Correction on PUSCH retransmission for CG RACH-less handover | Huawei, HiSilicon |
R1-2405335 | Correction on PRACH mask index for MSG1 repetition | Nokia |
R1-2405344 | FL summary on Rel-18 MIMO DMRS | Moderator (NTT DOCOMO) |
R1-2405345 | Summary on Rel-18 STxMP | Moderator (OPPO) |
R1-2405351 | FL Summary for maintenance on NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2405353 | FL summary #1 for AI 8.1: SL-U channel access and RA | Moderator (OPPO) |
R1-2405354 | FL summary #2 for AI 8.1: SL-U channel access and RA | Moderator (OPPO) |
R1-2405355 | FL summary #3 for AI 8.1: SL-U channel access and RA | Moderator (OPPO) |
R1-2405356 | FL summary for AI 8.1: SL-U channel access and RA (EOM) | Moderator (OPPO) |
R1-2405357 | Summary of issues for Rel-18 NES enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2405358 | Summary #1 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2405359 | Summary #2 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2405366 | FL Summary #1 for AI 8.1: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2405367 | FL Summary #2 for AI 8.1: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2405368 | FL Summary #1 for AI 8.1: Sidelink CA operation | Moderator (LG Electronics) |
R1-2405369 | FL Summary #2 for AI 8.1: Sidelink CA operation | Moderator (LG Electronics) |
R1-2405378 | FL summary on MCS table for multicast PDSCH in RRC_INACTIVE mode | Moderator (CMCC) |
R1-2405383 | FLS#1 for maintenance of SD-PD adaptation R18 NES | Moderator (Huawei) |
R1-2405384 | FLS#2 for maintenance of SD-PD adaptation R18 NES | Moderator (Huawei) |
R1-2405390 | FL summary#1 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2405391 | FL summary#2 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2405392 | FL summary#3 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2405393 | Correction on PSFCH Power Control to avoid exceeding Pcmax | Moderator (Huawei), Huawei, Hisilicon |
R1-2405394 | Correction on PSFCH Power Control for common interlace | Moderator (Huawei), OPPO, ZTE, Sanechips |
R1-2405395 | FL Summary #1: Maintenance on Rel-18 NR NTN | Moderator (Thales) |
R1-2405396 | FL Summary #2: Maintenance on Rel-18 NR NTN | Moderator (Thales) |
R1-2405397 | FL Summary #3: Maintenance on Rel-18 NR NTN | Moderator (Thales) |
R1-2405398 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
R1-2405401 | FL summary #1 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2405402 | Draft LS on higher layer parameters for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2405403 | LS on higher layer parameters for Rel-18 Positioning | RAN1, Intel Corporation |
R1-2405404 | Editorial corrections to TS 38.211 for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2405405 | Editorial corrections to TS 38.212 for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2405406 | Editorial corrections to TS 38.214 for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2405407 | FL Summary #1 of maintenance on further NR coverage enhancements | Moderator (China Telecom) |
R1-2405408 | Summary of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2405426 | Moderator Summary #1 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2405442 | Moderator Summary #0 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2405446 | Summary #1 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2405447 | Summary #2 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2405448 | Summary #3 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2405449 | Editorial corrections to TS 38.213 for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2405450 | Moderator summary of reply RAN2 LS on type 3 PH value for the serving cell configured with mTRP | Moderator (MediaTek Inc.) |
R1-2405451 | Feature lead summary#1 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2405452 | Feature lead summary#2 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2405453 | Feature lead summary#3 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2405454 | Summary #1 for BW aggregation positioning | Moderator (ZTE) |
R1-2405455 | Summary #2 for BW aggregation positioning | Moderator (ZTE) |
R1-2405456 | Reply LS on SRS BW aggregation | RAN1, ZTE |
R1-2405457 | Summary for reply LS on SRS BW aggregation | Moderator (ZTE) |
R1-2405458 | Summary of Rel-18 maintenance for UE power savings | Moderator (Ericsson) |
R1-2405461 | FL summary #1 for Rel-18 NR eRedCap maintenance | Moderator (Ericsson) |
R1-2405462 | FL summary #2 for Rel-18 NR eRedCap maintenance | Moderator (Ericsson) |
R1-2405463 | RAN1 agreements for Rel-18 NR eRedCap | Rapporteur (Ericsson) |
R1-2405472 | Summary #1 of discussion on HARQ-ACK multiplexing on a PUSCH repetition | Moderator (Huawei) |
R1-2405473 | Summary#2 on Rel-18 STxMP | Moderator (OPPO) |
R1-2405474 | Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension (Round 1) | Moderator (MediaTek Inc.) |
R1-2405475 | FL summary of PDSCH reception for MBS | Moderator (ZTE) |
R1-2405476 | Draft CR Corrections for Referencing UE Capabilities for 8TX UE | Moderator (InterDigital), Ericsson, Samsung |
R1-2405477 | Draft CR Corrections for Configured Grant Operation for 8TX UE | Moderator (InterDigital), Ericsson, ASUSTek, Samsung |
R1-2405478 | Draft CR Corrections for Transmission with more than 4 Layers for 8TX UE | Moderator (InterDigital), NTT DOCOMO, Ericsson, ASUSTek, Samsung |
R1-2405481 | Feature Lead summary #1 for Maintenance of Positioning for RedCap Ues | Moderator (Ericsson) |
R1-2405482 | Correction for hop counting in SRS for positioning with tx hopping | Moderator (Ericsson) |
R1-2405483 | Correction on CSI processing criteria for new NES capability signaling | Moderator (Huawei), Apple, Samsung |
R1-2405500 | Correction to 38.202 on support of combination of SL CA and SL positioning | Moderator (Qualcomm), Huawei, HiSilicon |
R1-2405509 | FLS#1 on reply LS on SL positioning measurement | Huawei |
R1-2405510 | DRAFT reply LS on SL positioning measurement | Huawei |
R1-2405511 | Reply LS on SL positioning measurement | RAN1, Huawei |
R1-2405520 | Corrections for 8-port SRS (TDM or non-TDM, without mixture) | Moderator (Futurewei), Samsung, ZTE, Ericsson |
R1-2405522 | Corrections on PRACH association indicator in PDCCH order in 38.212 | Moderator (Ericsson), Huawei, HiSilicon, Google, Ericsson, ZTE, Samsung, New H3C, vivo |
R1-2405523 | Summary #2 of discussion on HARQ-ACK multiplexing on a PUSCH repetition | Moderator (Huawei) |
R1-2405525 | RAN1 agreements for R18 NR SL-U PHY channel design until RAN1#116bis | Moderator (Huawei) |
R1-2405526 | RAN1 agreements for R18 NR SL-U PHY channel design until RAN1#117 | Moderator (Huawei) |
R1-2405527 | Draft CR on correction on supporting SL partial sensing for interlaced RB allocation and MCSt | Moderator (OPPO), Samsung, CATT, CICTCI |
R1-2405528 | Correction on SL partial sensing for interlaced RB allocation and MCSt | Moderator (OPPO), Samsung, CATT, CICTCI |
R1-2405529 | Draft Reply LS on Sidelink Feature Co-configuration | OPPO |
R1-2405530 | Reply LS on Sidelink Feature Co-configuration | RAN1, OPPO |
R1-2405531 | Correction on HARQ-ACK multiplexing on a PUSCH repetition [HARQ-ACK MUX on PUSCH] | Moderator (Huawei) |
R1-2405535 | Correction on guardband PRB handling | Moderator (Huawei), vivo, Samsung, OPPO |
R1-2405536 | Correction on the determination of intra-cell guard band for SL-U | Moderator (Huawei), CATT, CICTCI, Samsung |
R1-2405537 | Correction on the frequency resource of a resource pool for SL-U | Moderator (Huawei), CATT, CICTCI, NEC, OPPO |
R1-2405538 | Correction on the highest sub-channel of PSSCH | Moderator (Huawei), ZTE, Sanechips, Samsung, OPPO |
R1-2405539 | Corrections on determination of PSFCH resources for a PSSCH | Moderator (Huawei), Sharp, NEC, Samsung, OPPO |
R1-2405544 | Correction to 38.202 on support of combination of SL CA and SL positioning | Moderator (Qualcomm), Huawei, HiSilicon |
R1-2405547 | Correction on PSFCH Power Control to avoid exceeding Pcmax | Moderator (Huawei), Huawei, Hisilicon |
R1-2405548 | Correction on PSFCH Power Control for common interlace | Moderator (Huawei), OPPO, ZTE, Sanechips |
R1-2405554 | Draft CR on correction on CPE starting position determination and transmission for PSSCH/PSCCH | Moderator (OPPO), Samsung, CATT, CICTCI |
R1-2405555 | Correction on CPE starting position determination and transmission for PSSCH/PSCCH | Moderator (OPPO), Samsung, CATT, CICTCI |
R1-2405556 | Correction on beam application timing for mDCI mTRP for Rel-18 unified TCI framework | Moderator (MediaTek. Inc), NTT DOCOMO. Inc, Ericsson, Samsung, ASUSTeK |
R1-2405557 | Alignments on RRC parameters for NR Rel-18 MIMO in TS 38.214 | Moderator (MediaTek. Inc), CATT, Ericsson, Samsung |
R1-2405558 | Correction on configuration of TCI states for SRS | Moderator (MediaTek. Inc), CATT, Samsung |
R1-2405561 | Summary of discussion on RAN2 LS on RRC parameters used for CG RACH-less Handover | Moderator (Samsung) |
R1-2405562 | Draft reply LS on parameters used for CG RACH-less Handover | Moderator (Samsung) |
R1-2405563 | Reply LS on parameters used for CG RACH-less Handover | RAN1, Samsung |
R1-2405572 | Feature lead summary on IoT-NTN discussions | Moderator (Nokia) |
R1-2405576 | Correction of physical channels and signals during cell DTX/DRX operation | Moderator (Intel Corporation), Huawei, HiSilicon, Qualcomm, Ericsson, Samsung, Fujitsu |
R1-2405580 | Correction on Rel-18 Type II Doppler codebook based CSI enhancement | Moderator (Samsung), Xiaomi, New H3C, Google, Ericsson |
R1-2405581 | Correction on the application time of cell DRX for NR NTN | Moderator (Thales) |
R1-2405582 | Moderator Summary for Reply LS to R1-2403837 (LS on Reference Point for SSB-TimeOffset) | Moderator (Apple) |
R1-2405583 | Draft Reply LS on Reference Point for SSB-TimeOffset | Moderator (Apple) |
R1-2405584 | Moderator Summary on LS reply on DL-AoD Assistance Information | Moderator (Nokia) |
R1-2405585 | Draft Reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | Moderator (Nokia) |
R1-2405586 | Reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE | RAN1, Nokia |
R1-2405587 | Draft CR for 38.211 on Introduction of FR2-NTN | THALES |
R1-2405594 | Draft CR on Correction on PT-RS Coherence Conditions for 8 Tx | Moderator (NTT DOCOMO), Ericsson, Samsung |
R1-2405597 | Moderator Summary #1 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2405598 | Draft LS on the configuration of the SRS for positioning with Tx hopping | Ericsson |
R1-2405599 | LS on the configuration of the SRS for positioning with Tx hopping | RAN1, Ericsson |
R1-2405601 | Correction for hop counting in SRS for positioning with tx hopping | Moderator (Ericsson), Huawei/HiSilicon, Ericsson |
R1-2405606 | CR for dropping rule on SRS bandwidth aggregation | Moderator (ZTE) |
R1-2405607 | Multicast MBS PDSCH bandwidth for eRedCap UE in RRC inactive state | Moderator (Ericsson), Huawei, HiSilicon, Ericsson |
R1-2405608 | Correction on T_offset for UL Tx switching | Moderator (NTT DOCOMO, INC.), ZTE |
R1-2405609 | Summary#2 of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2405617 | Multicast MBS PDSCH bandwidth for eRedCap UE in RRC inactive state | Moderator (Ericsson), Huawei, HiSilicon, Ericsson |
R1-2405618 | Correction on PT-RS Coherence Conditions for 8 Tx | Moderator (NTT DOCOMO), Ericsson, Samsung |
R1-2405619 | Reply to RAN2 LS on type 3 PH value for the serving cell configured with mTRP | RAN1, MediaTek Inc. |
R1-2405621 | Correction on Rel-18 Type II Doppler codebook based CSI enhancement | Moderator (Samsung), Xiaomi, New H3C, Google, Ericsson |
R1-2405622 | Moderator Summary#2 for Reply LS to R1-2403837 (LS on Reference Point for SSB-TimeOffset) | Moderator (Apple) |
R1-2405623 | Draft CR for 38.211 on Introduction of FDD FR2-NTN | Ericsson, Eutelsat, NTT DOCOMO |
R1-2405624 | Corrections for Referencing UE Capabilities for 8TX UE | Moderator (InterDigital), Ericsson, Samsung |
R1-2405625 | Corrections for Configured Grant Operation for 8TX UE | Moderator (InterDigital), Ericsson, ASUSTek, Samsung |
R1-2405626 | Corrections for Transmission with more than 4 Layers for 8TX UE | Moderator (InterDigital), NTT DOCOMO, Ericsson, ASUSTek, Samsung |
R1-2405627 | Correction on beam application timing for mDCI mTRP for Rel-18 unified TCI framework | Moderator (MediaTek. Inc), NTT DOCOMO. Inc, Ericsson, Samsung, ASUSTeK |
R1-2405628 | Alignments on RRC parameters for NR Rel-18 MIMO in TS 38.214 | Moderator (MediaTek. Inc), CATT, Ericsson, Samsung |
R1-2405629 | Correction on configuration of TCI states for SRS | Moderator (MediaTek. Inc), CATT, Samsung |
R1-2405633 | Draft CR for 38.211 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT |
R1-2405634 | Draft CR for 38.212 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT |
R1-2405635 | Draft CR for 38.213 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT |
R1-2405636 | Draft CR for 38.214 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT |
R1-2405637 | Summary#2 of Rel-18 maintenance for UE power savings | Moderator (Ericsson) |
R1-2405663 | Draft CR on correction on contention window adjustment procedures for PSCCH/PSSCH transmission | Moderator (OPPO) |
R1-2405664 | Correction on contention window adjustment procedures for PSCCH/PSSCH transmission | Moderator (OPPO), Samsung, CATT, CICTCI |
R1-2405668 | FL summary 3 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2405669 | Final FL summary of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2405670 | [draft] Reply LS on parameters used for CG RACH-less Handover from LTM perspective | Moderator (Fujitsu) |
R1-2405671 | Reply LS on parameters used for CG RACH-less Handover from LTM perspective | RAN1, Fujitsu |
R1-2405672 | Corrections to the Pathloss RS in LTM TCI state | Moderator (Fujitsu), Huawei, HiSilicon, Ericsson, Google, Langbo, Lenovo, New H3C, Nokia, Samsung, ZTE |
R1-2405673 | Correction on CFRA procedure triggered by LTM cell switch command | Moderator (Fujitsu), Nokia, Ericsson, Google, Huawei, HiSilicon, Langbo, Lenovo, New H3C, Samsung, ZTE |
R1-2405674 | Correction on the unit of BWPswitchDelay | Moderator(Fujitsu), Langbo, ZTE, Ericsson, Google, Huawei, HiSilicon, Lenovo, New H3C, Samsung, Nokia |
R1-2405675 | Correction on spCellInclusion for LTM | Moderator (Fujitsu), Ericsson, Google, Huawei, HiSilicon, Langbo, Lenovo, New H3C, Nokia, Samsung, ZTE |
R1-2405676 | Corrections to the default beam determination after LTM cell switch | Moderator(Fujitsu), Huawei, HiSilicon, Ericsson, Google, Langbo, Lenovo, New H3C, Nokia, Samsung, ZTE |
R1-2405687 | Session notes for 8.1 (Maintenance on Rel-18 work items - Positioning Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2405688 | Session notes for 8.1 (Maintenance on Rel-18 work items - Mobility Enhancement) | Ad-Hoc Chair (CMCC) |
R1-2405689 | Session notes for 8.1 (Maintenance on Rel-18 work items - Coverage Enhancement) | Ad-Hoc Chair (CMCC) |
R1-2405690 | Session notes for 8.1 (Maintenance on Rel-18 work items - IoT NTN/NR NTN Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2405691 | Session notes for 8.1 (Maintenance on Rel-18 work items - RedCap Enhancement) | Ad-Hoc Chair (CMCC) |
R1-2405692 | Session notes for 8.1 (Maintenance on Rel-18 work items - Sidelink Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2405693 | Session notes for 8.1 (Maintenance on Rel-18 work items - MBS Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2405694 | Session notes for 8.1 (Maintenance on Rel-18 work items - UE power saving) | Ad-Hoc Chair (CMCC) |
R1-2405701 | CR for 38.211 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT, Huawei, HiSilicon |
R1-2405702 | CR for 38.212 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT, Huawei, HiSilicon |
R1-2405703 | CR for 38.213 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT, Huawei, HiSilicon |
R1-2405704 | CR for 38.214 on TRS occasions for idle/inactive UEs | Ericsson, Nokia, Mediatek, CATT, Huawei, HiSilicon |
R1-2405705 | Correction on CSI processing criteria for new NES capability signaling | Moderator (Huawei), Apple, Samsung, Ericsson |
R1-2405706 | Correction on PUSCH retransmission for CG RACH-less handover | Moderator (Thales), Huawei, HiSilicon, Samsung, CATT, Ericsson |
R1-2405707 | Correction to the provision of RTD in SL positioning | Moderator (vivo), Huawei, HiSilicon |
R1-2405713 | Correction on priority for LTM CSI report | Moderator (Fujitsu), ZTE, Ericsson, Google, Huawei, HiSilicon, Langbo, Lenovo, New H3C, Nokia, Samsung |
R1-2405714 | Corrections to the beam of CFRA triggered by cell switch command in TS38.213 | Moderator (Fujitsu), Huawei, HiSilicon, Ericsson, Google, Langbo, Lenovo, New H3C, Nokia, Samsung, ZTE |
R1-2405715 | Correction on TCI state applied for CORESETs other than CORESET 0 in LTM | Moderator (Fujitsu), Nokia, Ericsson, Google, Huawei, HiSilicon, Langbo, Lenovo, New H3C, Samsung, ZTE |
R1-2405716 | Correction on QCL assumption after LTM cell switch command | Moderator (Fujitsu), Nokia, Ericsson, Google, Huawei, HiSilicon, Langbo, Lenovo, New H3C, Samsung, ZTE |
R1-2405719 | Reply LS on Reference Point for SSB-TimeOffset | RAN1, Apple |
R1-2405722 | Corrections for 8-port SRS (TDM or non-TDM, without mixture) | Moderator (Futurewei), Samsung, ZTE, Ericsson |
R1-2405724 | Final summary of discussion on HARQ-ACK multiplexing on a PUSCH repetition | Moderator (Huawei) |
R1-2405725 | Correction on HARQ-ACK multiplexing on a PUSCH repetition [HARQ-ACK MUX on PUSCH] | Moderator (Huawei), HiSilicon, Samsung, Ericsson, ZTE |
R1-2405727 | Clarification on SL CSI request in TS 38.214 | Moderator (LG Electronics), vivo, OPPO |
R1-2405728 | Correction on SL BWP configuration in TS 38.213 | Moderator (LG Electronics), vivo, OPPO |
R1-2405731 | Feature lead summary#4 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2405734 | Correction on indicated unified TCI states for multi-cell scheduling | Moderator (Lenovo) , Samsung, Nokia, Spreadtrum, NTT DOCOMO, INC., Cybercore |
R1-2405738 | CR for TS 38.211 for introduction of FR2-NTN | Moderator (Nokia), NTT DOCOMO , INC., Samsung, Ericsson |
R1-2405739 | CR for TS 38.213 for introduction of FR2-NTN | Moderator (Nokia), NTT DOCOMO , INC., Samsung, Ericsson |
R1-2405740 | CR for TS 38.214 for introduction of FR2-NTN | Moderator (Nokia), NTT DOCOMO , INC., Samsung, Ericsson |
R1-2405746 | Correction on PT-RS Coherence Conditions for 8 Tx | Moderator (NTT DOCOMO), Ericsson, Samsung |
TDoc | Title | Source |
---|---|---|
R1-2405564 | Updated RAN1 UE features list for Rel-18 NR after RAN1 #117 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2405565 | Draft LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#117 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2405566 | LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#117 | RAN1, AT&T, NTT DOCOMO, INC. |
R1-2405567 | Updated RAN1 UE features list for Rel-18 LTE after RAN1 #117 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2405568 | Draft LS on updated Rel-18 RAN1 UE features lists for LTE after RAN1#117 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2405569 | LS on updated Rel-18 RAN1 UE features lists for LTE after RAN1#117 | RAN1, AT&T, NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R1-2403918 | UE features for other Rel-18 work items (Topics A) | Huawei, HiSilicon |
R1-2404006 | Discussion on UE feature topics A | ZTE |
R1-2404101 | UE features for other Rel-18 work items (Topics A) | Samsung |
R1-2404163 | Discussion on Rel-18 UE features topics A (Sidelink, MBS) | vivo |
R1-2404270 | Discussion on UE Feature Topics A | Apple |
R1-2404382 | Remaining issues on UE features for NR sidelink evolution and MBS | CATT, CICTCI, CBN |
R1-2404484 | UE Features for Other Topics A (SLenh, MCenh, MBS, Sub-5MHz) | Nokia |
R1-2404523 | Rel-18 UE features topics set A | Ericsson |
R1-2404841 | UE features list for Rel-18 NR sidelink evolution WI | OPPO, Huawei, HiSilicon, LG Electronics |
R1-2404857 | Discussion on UE features for multi-carrier enhancement | OPPO |
R1-2405028 | Discussion on UE features for other Rel-18 work items (Topics A) | NTT DOCOMO, INC. |
R1-2405141 | UE features for other Rel-18 work items (Topics A) | Qualcomm Incorporated |
R1-2405252 | 3MHz asymmetric bandwidth UE capability discussion | Rakuten Mobile, Inc |
R1-2405409 | Summary of discussion on UE features for NR sidelink evolution | Moderator (NTT DOCOMO, INC.) |
R1-2405410 | Summary of discussion on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2405411 | Summary of discussion on UE features for dedicated spectrum less than 5MHz | Moderator (NTT DOCOMO, INC.) |
R1-2405412 | Summary of discussion on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
R1-2405413 | Summary of discussion on UE features for MBS | Moderator (NTT DOCOMO, INC.) |
R1-2405570 | Session Notes of AI 8.2.1 | Ad-Hoc Chair (NTT DOCOMO, INC.) |
R1-2405610 | Summary#2 of discussion on UE features for NR sidelink evolution | Moderator (NTT DOCOMO, INC.) |
R1-2405611 | Summary#2 of discussion on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2405612 | Summary#2 of discussion on UE features for dedicated spectrum less than 5MHz | Moderator (NTT DOCOMO, INC.) |
R1-2405613 | Summary#2 of discussion on UE features for MBS | Moderator (NTT DOCOMO, INC.) |
R1-2405677 | Summary#3 of discussion on UE features for NR sidelink evolution | Moderator (NTT DOCOMO, INC.) |
R1-2405742 | Summary#3 of discussion on UE features for dedicated spectrum less than 5MHz | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2403919 | UE features for other Rel-18 work items (Topics B) | Huawei, HiSilicon |
R1-2403972 | UE features for Rel-18 Work Items (Topics B) | Intel Corporation |
R1-2404102 | UE features for other Rel-18 work items (Topics B) | Samsung |
R1-2404164 | Discussion on Rel-18 UE features topics B (Positioning) | vivo |
R1-2404271 | Discussion on UE Feature Topics B | Apple |
R1-2404383 | Remaining issues on UE features for expanded and improved NR positioning | CATT |
R1-2404485 | UE Features for Other Topics B (MIMO, Pos, NES, MobEnh, IoT-NTN, NR-NTN) | Nokia |
R1-2404824 | UE features for other Rel-18 work items (Topics B) | OPPO |
R1-2404887 | Discussion on UE features for NES | LG Electronics |
R1-2404910 | Discussion on BWP Without Restriction maintenance | Vodafone |
R1-2405004 | UE features for other Rel-18 work items (Topics B) | ZTE |
R1-2405029 | Discussion on UE features for other Rel-18 work items (Topics B) | NTT DOCOMO, INC. |
R1-2405104 | Rel-18 UE features topics set B | Ericsson |
R1-2405142 | UE features for other Rel-18 work items (Topics B) | Qualcomm Incorporated |
R1-2405571 | Session Notes of AI 8.2.2 | Ad-Hoc Chair (AT&T) |
R1-2405602 | Summary of UE features for other Rel-18 work items (Topics B) | Moderator (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2405222 | Specification support for beam management | KDDI Corporation |
R1-2405695 | Session notes for 9.1 (AI/ML for NR Air Interface) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2403866 | Discussion on specification support for beam management | FUTUREWEI |
R1-2403914 | AIML for beam management | Ericsson |
R1-2403929 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
R1-2403973 | Specification support for AI/ML for beam management | Intel Corporation |
R1-2403998 | Discussions on AIML for beam management | New H3C Technologies Co., Ltd. |
R1-2403999 | Discussion on AI/ML beam management | TCL |
R1-2404015 | Discussion on AIML for beam management | Spreadtrum Communications |
R1-2404137 | Discussion for supporting AI/ML based beam management | Samsung |
R1-2404165 | Specification support for beam management | vivo |
R1-2404272 | Discussion on AI/ML-based beam management | Apple |
R1-2404311 | Discussion on AI/ML for beam management | InterDigital, Inc. |
R1-2404384 | Discussion on AI/ML for beam management | CATT |
R1-2404421 | Discussion on specification support for AI/ML beam management | China Telecom |
R1-2404444 | Discussion on specification support for beam management | CMCC |
R1-2404490 | Discussions on AI/ML for beam management | Sony |
R1-2404525 | AI/ML specification support for beam management | Lenovo |
R1-2404536 | Specification support for AI-enabled beam management | NVIDIA |
R1-2404546 | Discussions on AI/ML for beam management | LG Electronics |
R1-2404567 | Discussion on specification support for beam management | Panasonic |
R1-2404582 | Discussion on specification support on AI/ML for beam management | Fujitsu |
R1-2404601 | Specification support for beam management | Xiaomi |
R1-2404655 | Discussion on specification support for beam management | NEC |
R1-2404682 | AI/ML based Beam Management | |
R1-2404701 | Discussion on specification support for AI/ML beam management | ZTE |
R1-2404721 | Discussions on AI/ML for beam management | CAICT |
R1-2404737 | Discussion on AI/ML based beam management | Hyundai Motor Company |
R1-2404766 | Discussion on specification support for beam management | ETRI |
R1-2404802 | Prediction of untransmitted beams in a UE-side AI-ML model | Rakuten Mobile, Inc |
R1-2404877 | On specification for AI/ML-based beam management | OPPO |
R1-2404903 | Specification support for beam management | Fraunhofer HHI, Fraunhofer IIS |
R1-2404904 | AI/ML for Beam Management | Nokia |
R1-2405030 | Discussion on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2405068 | Discussions on specification support for beam management | Sharp |
R1-2405087 | Discussion on specification support for AI/ML-based beam management | MediaTek Inc. |
R1-2405096 | Discussion on AI/ML based beam management | KT Corp. |
R1-2405121 | Discussions on specification support for beam management | Ruijie Networks Co. Ltd |
R1-2405143 | Specification support for AI-ML-based beam management | Qualcomm Incorporated |
R1-2405223 | Specification support for AI/ML beam management | ITL |
R1-2405234 | Discussion on Specification Support for Beam Management | CEWiT |
R1-2405284 | Discussions on Specification Support of AI/ML for Beam Management | Indian Institute of Tech (M), IIT Kanpur |
R1-2405336 | Specification support for beam management | KDDI Corporation |
R1-2405427 | FL summary #0 for AI/ML in beam management | Moderator (Samsung) |
R1-2405428 | FL summary #1 for AI/ML in beam management | Moderator (Samsung) |
R1-2405429 | FL summary #2 for AI/ML in beam management | Moderator (Samsung) |
R1-2405430 | FL summary #3 for AI/ML in beam management | Moderator (Samsung) |
R1-2405679 | FL summary #4 for AI/ML in beam management | Moderator (Samsung) |
R1-2405680 | FL summary #5 for AI/ML in beam management | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2403898 | AI/ML for Positioning Accuracy Enhancement | Ericsson |
R1-2403930 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2403974 | Specification support for AI/ML for positioning accuracy enhancement | Intel Corporation |
R1-2404002 | Discussion on specification support for positioning accuracy enhancement | TCL |
R1-2404138 | Discussion for supporting AI/ML based positioning accuracy enhancement | Samsung |
R1-2404166 | Specification support for positioning accuracy enhancement | vivo |
R1-2404273 | Discussion on Specification Support for AI/ML-based positioning | Apple |
R1-2404316 | AI/ML positioning accuracy enhancement | Fraunhofer IIS, Fraunhofer HHI |
R1-2404347 | Discussion on specification support for positioning accuracy enhancement | Lekha Wireless Solutions |
R1-2404385 | Discussion on AI/ML for positioning accuracy enhancement | CATT, CICTCI |
R1-2404445 | Discussion on specification support for positioning accuracy enhancement | CMCC |
R1-2404478 | Specification support for positioning accuracy enhancement | Quectel |
R1-2404491 | Discussion on Specification Support for AI/ML Positioning | Sony |
R1-2404526 | Specification impacts for Enhanced Positioning | Lenovo |
R1-2404537 | Specification support for AI-enabled positioning | NVIDIA |
R1-2404583 | Discussion on specification support for AI/ML positioning accuracy enhancement | Fujitsu |
R1-2404602 | Discussion on AI/ML-based positioning accuracy enhancement | Xiaomi |
R1-2404650 | Discussion on support for AIML positioning | InterDigital, Inc. |
R1-2404659 | Discussion on specification support for AI/ML based positioning accuracy enhancement | NEC |
R1-2404683 | AI/ML based Positioning | |
R1-2404763 | Design for AI/ML based positioning | MediaTek Korea Inc. |
R1-2404767 | Discussion on specification support for positioning accuracy enhancement | ETRI |
R1-2404878 | On specification for AI/ML-based positioning accuracy enhancements | OPPO |
R1-2404905 | AI/ML for Positioning Accuracy Enhancement | Nokia |
R1-2405031 | Discussion on AI/ML for positioning accuracy enhancement | NTT DOCOMO, INC. |
R1-2405069 | Discussion on specification support for AI/ML based positioning accuracy enhancements | Sharp |
R1-2405120 | Discussion on specification support for AI/ML positioning accuracy enhancement | ZTE, Pengcheng laboratory |
R1-2405144 | Specification support for AI-ML-based positioning accuracy enhancement | Qualcomm Incorporated |
R1-2405235 | Discussion on specification support for AI/ML Positioning Accuracy enhancement | CEWiT |
R1-2405277 | Discussions on positioning accuracy enhancement for AI/ML | ITL |
R1-2405283 | Discussion on Specification Support of AI/ML for Positioning Accuracy Enhancement | Indian Institute of Tech (M), IIT Kanpur |
R1-2405350 | Discussion on specification support for positioning accuracy enhancement | Lekha Wireless Solutions |
R1-2405385 | Summary #1 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2405386 | Summary #2 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2405387 | Summary #3 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2405388 | Summary #4 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2405389 | Summary #5 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2405577 | [Draft] Reply LS on data collection to enable ML model training and inference in 5GC for direct AI/ML based positioning | Ericsson |
R1-2405578 | Reply LS on data collection to enable ML model training and inference in 5GC for direct AI/ML based positioning | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2403909 | AI/ML for CSI prediction | Ericsson |
R1-2403931 | Discussion on AI/ML for CSI prediction | Huawei, HiSilicon |
R1-2403961 | Discussion on study for AI/ML CSI prediction | Tejas Networks Limited |
R1-2403975 | AI/ML for CSI prediction | Intel Corporation |
R1-2404016 | Discussion on AIML for CSI prediction | Spreadtrum Communications, BUPT |
R1-2404053 | Discussion on AI/ML-based CSI prediction | InterDigital, Inc. |
R1-2404103 | Discussion for further study on AI/ML-based CSI prediction | Samsung |
R1-2404167 | Discussion on CSI prediction | vivo |
R1-2404274 | Discussion on AI based CSI prediction | Apple |
R1-2404386 | Study on AI/ML for CSI prediction | CATT |
R1-2404422 | Discussion on AI/ML-based CSI prediction | China Telecom |
R1-2404446 | Discussion on AI/ML for CSI prediction | CMCC |
R1-2404492 | Discussion on CSI prediction inference in AI/ML | Sony |
R1-2404527 | On AI/ML for CSI prediction | Lenovo |
R1-2404538 | Additional study on AI-enabled CSI prediction | NVIDIA |
R1-2404547 | Study on CSI prediction | LG Electronics |
R1-2404569 | Discussion on AI/ML for CSI prediction | SK Telecom |
R1-2404584 | Discussion on CSI prediction with AI/ML | Fujitsu |
R1-2404603 | Discussion on AI/ML model based CSI prediction | Xiaomi |
R1-2404653 | Discussion on CSI prediction | NEC |
R1-2404684 | AI/ML based CSI Prediction | |
R1-2404702 | Discussion on study for AI/ML CSI prediction | ZTE |
R1-2404744 | Discussion on AI/ML for CSI prediction | Panasonic |
R1-2404810 | Varying CSI feedback granularity based on channel conditions | Rakuten Mobile, Inc |
R1-2404879 | Additional study on AI/ML-based CSI prediction | OPPO |
R1-2404906 | AI/ML for CSI Prediction | Nokia |
R1-2405015 | Discussion on AI/ML for CSI prediction | AT&T |
R1-2405032 | Discussion on AI/ML for CSI prediction | NTT DOCOMO, INC. |
R1-2405088 | Additional Study on AI/ML for CSI Prediction | MediaTek Inc. |
R1-2405125 | AI/ML for CSI prediction | Mavenir |
R1-2405145 | Additional study on CSI prediction | Qualcomm Incorporated |
R1-2405236 | Discussion on AI/ML for CSI Prediction | CEWiT |
R1-2405290 | Discussion on study of AIML for CSI prediction | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405489 | Summary #1 of CSI prediction | Moderator (LG Electronics) |
R1-2405490 | Summary #2 of CSI prediction | Moderator (LG Electronics) |
R1-2405491 | Summary #3 of CSI prediction | Moderator (LG Electronics) |
R1-2405492 | Summary #4 of CSI prediction | Moderator (LG Electronics) |
R1-2405683 | Summary #5 of CSI prediction | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2403867 | Discussion on additional study on AI/ML for NR air interface for CSI compression | FUTUREWEI |
R1-2403897 | AI/ML for CSI Compression | Tejas Networks Limited |
R1-2403910 | AI/ML for CSI compression | Ericsson |
R1-2403932 | Discussion on AI/ML for CSI compression | Huawei, HiSilicon |
R1-2403976 | AI/ML for CSI compression | Intel Corporation |
R1-2404000 | Discussion on AI/ML CSI compression | TCL |
R1-2404017 | Discussion on AIML for CSI compression | Spreadtrum Communications, BUPT |
R1-2404054 | Discussion on AI/ML-based CSI compression | InterDigital, Inc. |
R1-2404104 | Discussion for further study on AI/ML-based CSI compression | Samsung |
R1-2404168 | Discussion on CSI compression | vivo |
R1-2404275 | Discussion on AI based CSI compression | Apple |
R1-2404387 | Study on AI/ML for CSI compression | CATT |
R1-2404423 | Discussion on AI/ML-based CSI compression | China Telecom |
R1-2404447 | Discussion on AI/ML for CSI compression | CMCC |
R1-2404493 | Discussion on CSI compression | Sony |
R1-2404528 | On AI/ML for CSI compression | Lenovo |
R1-2404539 | Additional study on AI-enabled CSI compression | NVIDIA |
R1-2404548 | Study on CSI compression | LG Electronics |
R1-2404571 | Discussion on AI/ML for CSI compression | SK Telecom |
R1-2404585 | Discussion on CSI compression with AI/ML | Fujitsu |
R1-2404604 | Discussion on AI/ML model based CSI compression | Xiaomi |
R1-2404654 | Discussion on CSI compression | NEC |
R1-2404685 | AI/ML based CSI Compression | |
R1-2404703 | Discussion on study for AI/ML CSI compression | ZTE |
R1-2404722 | Discussions on AI/ML for CSI feedback | CAICT |
R1-2404745 | Discussion on AI/ML for CSI compression | Panasonic |
R1-2404768 | Discussion on AI/ML for CSI compression | ETRI |
R1-2404880 | Additional study on AI/ML-based CSI compression | OPPO |
R1-2404907 | AI/ML for CSI Compression | Nokia |
R1-2405016 | Discussion on AI/ML for CSI compression | AT&T |
R1-2405033 | Discussion on AI/ML for CSI compression | NTT DOCOMO, INC. |
R1-2405089 | Additional Study on AI/ML for CSI Compression | MediaTek Inc. |
R1-2405116 | Discussion on additional study of AI/ML for CSI Compression | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405146 | Additional study on CSI compression | Qualcomm Incorporated |
R1-2405210 | Discussion on the AI/ML for CSI Compression | Fraunhofer IIS |
R1-2405237 | Discussion on AI/ML for CSI Compression | CEWiT |
R1-2405414 | Summary#1 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2405415 | Summary#2 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2405416 | Summary#3 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2405417 | Summary#4 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2405418 | Summary#5 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2405419 | Final summary of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2403868 | Discussion on other aspects of AI/ML model and data on AI/ML for NR air-interface | FUTUREWEI |
R1-2403915 | Discussion on other aspects of AI/ML | Ericsson |
R1-2403933 | Discussion on other aspects of the additional study for AI/ML | Huawei, HiSilicon |
R1-2403977 | Other study aspects of AI/ML for air interface | Intel Corporation |
R1-2404018 | Discussion on other aspects of AI/ML model and data | Spreadtrum Communications |
R1-2404055 | Discussion on other aspects of AI/ML model and data | InterDigital, Inc. |
R1-2404105 | Discussion for further study on other aspects of AI/ML model and data | Samsung |
R1-2404169 | Other aspects of AI/ML model and data | vivo |
R1-2404276 | Discussion on other aspects of AI/ML model and data | Apple |
R1-2404388 | Study on AI/ML for other aspects of model and data | CATT, CICTCI |
R1-2404448 | Discussion on other aspects of AI/ML model and data | CMCC |
R1-2404529 | On aspects of AI/ML model and data framework | Lenovo |
R1-2404540 | Additional study on other aspects of AI model and data | NVIDIA |
R1-2404549 | Discussion on other aspects of AI/ML model and data | LG Electronics |
R1-2404586 | Discussion on other aspects of AI/ML model and data | Fujitsu |
R1-2404605 | Further study on AI/ML model and data | Xiaomi |
R1-2404656 | Discussion on other aspects of AI/ML model and data | NEC |
R1-2404686 | AI/ML Model and Data | |
R1-2404704 | Discussion on study for other aspects of AI/ML model and data | ZTE |
R1-2404756 | Discussion on other aspects for AI/ML for air interface | Panasonic |
R1-2404764 | View on AI/ML model and data | MediaTek Korea Inc. |
R1-2404769 | Discussion on other aspects of AI/ML model and data | ETRI |
R1-2404881 | Additional study on other aspects of AI/ML model and data | OPPO |
R1-2404908 | Other Aspects of AI/ML Model and Data | Nokia |
R1-2405017 | Other Aspects of AI/ML framework | AT&T |
R1-2405034 | Discussion on other aspects of AI/ML model and data | NTT DOCOMO, INC. |
R1-2405147 | Other aspects of AI/ML model and data | Qualcomm Incorporated |
R1-2405212 | Discussion on other aspects of AI/ML model and data | Continental Automotive |
R1-2405304 | Discussion on other aspects of AI/ML model and data | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405501 | Summary #1 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2405502 | Summary #2 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2405503 | Summary #3 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2405504 | Summary #4 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2405505 | Summary #5 for other aspects of AI/ML model and data | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2403846 | Discussion on Rel-19 UE/Event-Driven Beam Management | InterDigital, Inc. |
R1-2403872 | Enhancements for UE-initiated/event-driven beam management | FUTUREWEI |
R1-2403877 | Discussion on Rel-19 Enhancement for UE-initiated/event-driven beam management | New H3C Technologies Co., Ltd. |
R1-2403900 | Enhancements for UE-initiated/event-driven beam management | MediaTek Inc. |
R1-2403944 | On UE initiated/event-driven beam management | Huawei, HiSilicon |
R1-2403985 | Enhancements for event driven beam management | Intel Corporation |
R1-2404019 | Discussion on UE-initiated/event-driven beam management | Spreadtrum Communications |
R1-2404106 | Views on Rel-19 UE-initiated/event-driven beam management | Samsung |
R1-2404170 | Discussion on UE-initiated/event-driven beam management | vivo |
R1-2404239 | Discussion on enhancements for UE-initiated/event-driven beam management | ZTE |
R1-2404277 | Enhancements for UE-initiated beam management | Apple |
R1-2404336 | Enhancements for UE-initiated/event-driven beam management | Lenovo |
R1-2404394 | Views on UE-initiated/event-driven beam management | CATT |
R1-2404449 | Discussion on enhancements for UE-initiated/event-driven beam management | CMCC |
R1-2404475 | Enhancements for UE-initiated/Event-Driven Beam Management | Panasonic |
R1-2404494 | Discussion on UE initiated beam management | Sony |
R1-2404550 | UE-initiated beam management | LG Electronics |
R1-2404574 | Discussion on UE-initiated/event-driven beam management | HONOR |
R1-2404587 | Discussion on enhancements for UE-initiated/event-driven beam management | Fujitsu |
R1-2404611 | Enhancements for UE-initiated/event-driven beam management | Xiaomi |
R1-2404657 | Discussion on enhancements for UE-initiated or event-driven beam management | NEC |
R1-2404712 | Offline summary for Rel-19 MIMO UEIBM (9.2.1) pre-RAN1#117 | Moderator (ZTE) |
R1-2404713 | Moderator Summary #1 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2404714 | Moderator Summary #2 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2404715 | Moderator Summary #3 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2404739 | Discussion on enhancements for UE-initiated/event-driven beam management | Hyundai Motor Company |
R1-2404746 | Enhancements for UE-initiated beam management | Ericsson |
R1-2404770 | Enhancements for UE-initiated/event-driven beam management | ETRI |
R1-2404813 | Enhancements for UE-initiated/event-driven beam management | Transsion Holdings |
R1-2404882 | Discussions on UE-initiated/event-driven beam management | OPPO |
R1-2404918 | Enhancements to facilitate UE-initiated/event-driven beam management | Nokia |
R1-2404970 | Enhancements for UE-initiated/event-driven beam management | Sharp |
R1-2405035 | Discussion on enhancements for UE-initiated/event-driven beam management | NTT DOCOMO, INC. |
R1-2405111 | Discussion on UE-initiated/event-driven beam management | ITRI |
R1-2405122 | Discussions on enhancements for UE-initiated/event-driven beam management | Ruijie Networks Co. Ltd |
R1-2405148 | UE-initiated/event-driven beam management | Qualcomm Incorporated |
R1-2405187 | Discussion on UE initiated beam management | ASUSTeK |
R1-2405205 | Enhancements for UE-initiated/event-driven beam management | NICT |
R1-2405238 | Enhancements for UE-initiated/event-driven beam management | CEWiT |
R1-2405258 | Discussions on enhancements for UE-initiated/event-driven beam management | KDDI Corporation |
R1-2405271 | Discussion on enhancements for UE-initiated or event-driven beam management | |
R1-2405638 | Moderator Summary #4 on UE-initiated/event-driven beam management | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R1-2403847 | Discussion on Rel-19 Enhancements of CSI | InterDigital, Inc. |
R1-2403876 | Discussion on Rel-19 CSI enhancements | New H3C Technologies Co., Ltd. |
R1-2403884 | CSI enhancement for NR MIMO Phase 5 | Tejas Networks Limited |
R1-2403901 | CSI enhancements to support up to 128 CSI-RS ports | MediaTek Inc. |
R1-2403945 | On 128 CSI-RS ports and UE reporting enhancement | Huawei, HiSilicon |
R1-2403981 | CSI enhancements for MIMO | Intel Corporation |
R1-2404004 | Discussion on Rel-19 CSI enhancements | TCL |
R1-2404020 | Discussion on CSI enhancements | Spreadtrum Communications |
R1-2404107 | Moderator summary for OFFLINE discussion on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2404108 | Moderator summary on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2404109 | Views on Rel-19 CSI enhancements | Samsung |
R1-2404171 | Discussion on Rel-19 CSI enhancements | vivo |
R1-2404240 | Discussion on CSI enhancements | ZTE |
R1-2404278 | Views on R19 MIMO CSI enhancement | Apple |
R1-2404337 | Discussion on CSI enhancements | Lenovo |
R1-2404395 | Views on MIMO CSI enhancements in Rel-19 | CATT |
R1-2404450 | Discussion on CSI enhancements | CMCC |
R1-2404495 | Additional views on CSI enhancements | Sony |
R1-2404551 | Discussions on CSI enhancements | LG Electronics |
R1-2404575 | Discussion on CSI enhancements | HONOR |
R1-2404588 | Discussion on Rel-19 CSI enhancements | Fujitsu |
R1-2404612 | Discussion on CSI enhancement | Xiaomi |
R1-2404668 | Discussion on CSI enhancements | NEC |
R1-2404687 | CSI Enhancement for NR MIMO | |
R1-2404883 | CSI enhancements for Rel-19 MIMO | OPPO |
R1-2404919 | CSI enhancement for NR MIMO Phase 5 | Nokia |
R1-2404923 | CSI enhancements for Rel.19 MIMO | Fraunhofer IIS, Fraunhofer HHI |
R1-2404971 | CSI enhancements | Sharp |
R1-2405005 | CSI enhancements for large antenna arrays and CJT | Ericsson |
R1-2405036 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
R1-2405149 | CSI enhancements for >32 ports and UE-assisted CJT | Qualcomm Incorporated |
R1-2405206 | CSI enhancements | NICT |
R1-2405239 | CSI Enhancements | CEWiT |
R1-2405255 | Discussion on CSI enhancements for NR MIMO Phase 5 | KDDI Corporation |
R1-2405340 | CSI enhancements to support up to 128 CSI-RS ports | MediaTek Inc. |
R1-2405365 | Views on Rel-19 CSI enhancements | Samsung |
R1-2405382 | Views on Rel-19 CSI enhancements | Samsung |
R1-2405445 | On 128 CSI-RS ports and UE reporting enhancement | Huawei, HiSilicon |
R1-2405484 | Moderator Summary#2 on Rel-19 CSI enhancements: Round 2 | Moderator (Samsung) |
R1-2405485 | Moderator Summary#3 on Rel-19 CSI enhancements: Round 3 | Moderator (Samsung) |
R1-2405486 | Moderator Summary#4 on Rel-19 CSI enhancements: Round 4 | Moderator (Samsung) |
R1-2405487 | Moderator summary of Tuesday morning offline on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2405488 | Moderator summary of Tuesday afternoon offline on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2405678 | Moderator summary of Thursday offline on Rel-19 CSI enhancements | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2403848 | Discussion on Rel-19 CB-based UL for 3TX UE | InterDigital, Inc. |
R1-2403850 | Summary of Offline Discussions on 3TX CB-based Uplink | Moderator (InterDigital, Inc.) |
R1-2403851 | FL Summary Support for 3TX CB-based Uplink; First Round | Moderator (InterDigital, Inc.) |
R1-2403852 | FL Summary Support for 3TX CB-based Uplink; Second Round | Moderator (InterDigital, Inc.) |
R1-2403853 | Recommended Direction on 3TX CB-based Uplink in RAN1#118 | Moderator (InterDigital, Inc.) |
R1-2403902 | Support for 3-antenna-port codebook-based transmissions | MediaTek Inc. |
R1-2403946 | On codebook for 3-antenna-port UL transmission | Huawei, HiSilicon |
R1-2403983 | Support for 3Tx UL MIMO | Intel Corporation |
R1-2404021 | Discussion on 3-antenna-port codebook-based transmissions | Spreadtrum Communications |
R1-2404046 | Discussion on Rel-19 CB-based UL transmission for 3TX UE | TCL |
R1-2404110 | Views on Rel-19 3-antenna-port codebook-based transmissions | Samsung |
R1-2404172 | Discussion on 3-antenna-port codebook-based uplink transmissions | vivo |
R1-2404241 | Discussion on 3-antenna-port codebook-based transmissions | ZTE |
R1-2404279 | Views on R19 3Tx codebook based transmission | Apple |
R1-2404338 | Support for 3-antenna-port codebook-based transmissions | Lenovo |
R1-2404396 | Views on support for 3-antenna-port codebook-based transmissions | CATT |
R1-2404451 | Discussion on support for 3-antenna-port codebook-based transmissions | CMCC |
R1-2404552 | Discussions on 3-antenna-port codebook-based transmissions | LG Electronics |
R1-2404589 | Discussion on uplink enhancement for UE with 3Tx | Fujitsu |
R1-2404613 | Discussion on the support of 3-antenna-port CB based transmissions | Xiaomi |
R1-2404669 | Discussion on 3-antenna-port codebook-based transmissions | NEC |
R1-2404688 | Uplink 3 Port Codebook based Transmission | |
R1-2404814 | Discussion on 3-antenna-port codebook-based transmissions | Transsion Holdings |
R1-2404884 | Discussion on 3-antenna-port codebook-based transmissions | OPPO |
R1-2404920 | On the support for 3-antenna-port codebook-based transmissions | Nokia |
R1-2404972 | Support for 3-antenna-port codebook-based transmission | Sharp |
R1-2405037 | Discussion on support for 3-antenna-port codebook-based transmissions | NTT DOCOMO, INC. |
R1-2405119 | Support for 3 Tx UL transmissions | Ericsson |
R1-2405150 | 3 Tx UL MIMO transmissions | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R1-2403849 | Discussion on Rel-19 Asymmetric mTRP Operation | InterDigital, Inc. |
R1-2403903 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | MediaTek Inc. |
R1-2403947 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | Huawei, HiSilicon |
R1-2403984 | Enhancements for asymmetric DL/UL scenarios | Intel Corporation |
R1-2404022 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | Spreadtrum Communications |
R1-2404111 | Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios | Samsung |
R1-2404173 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | vivo |
R1-2404242 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | ZTE, China Telecom |
R1-2404280 | Enhancements for asymmetric DL sTRP/UL mTRP | Apple |
R1-2404339 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Lenovo |
R1-2404397 | Views on asymmetric DL sTRP/UL mTRP scenarios | CATT |
R1-2404424 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | China Telecom, ZTE |
R1-2404452 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | CMCC |
R1-2404476 | Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios | Panasonic |
R1-2404496 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Sony |
R1-2404532 | Enhancement for asymmetric DL sTRP UL mTRP scenarios | Ericsson |
R1-2404553 | Discussions on asymmetric DL sTRP/UL mTRP scenarios | LG Electronics |
R1-2404568 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | TCL |
R1-2404590 | Discussion on UL-only mTRP operation | Fujitsu |
R1-2404614 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | Xiaomi |
R1-2404658 | Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios | NEC |
R1-2404771 | Discussion on asymmetric DL sTRP and UL mTRP operation | ETRI |
R1-2404815 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | Transsion Holdings |
R1-2404885 | Enhancements on asymmetric DL sTRP/UL mTRP scenarios | OPPO |
R1-2404921 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Nokia |
R1-2404973 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Sharp |
R1-2405038 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | NTT DOCOMO, INC. |
R1-2405151 | Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios | Qualcomm Incorporated |
R1-2405188 | Discussion on asymmetric DL sTRP and UL mTRP | ASUSTeK |
R1-2405272 | Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios | |
R1-2405346 | Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
R1-2405347 | Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
R1-2405348 | Summary #3 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2403874 | Discussion for SBFD TX/RX/ measurement procedures | New H3C Technologies Co., Ltd. |
R1-2403892 | Discussion for SBFD TX/RX/ measurement procedures | Tejas Networks Limited |
R1-2403904 | Discussion on SBFD TX/RX/measurement procedures | LG Electronics |
R1-2403911 | SBFD Tx/Rx/measurement procedures | Ericsson |
R1-2403934 | On subband full duplex design | Huawei, HiSilicon |
R1-2404007 | Discussion on transmission, reception and measurement procedures for SBFD operation | ZTE |
R1-2404023 | Discussion on SBFD TX/RX/measurement procedures | Spreadtrum Communications |
R1-2404047 | Discussion on SBFD TX RX and measurement procedures | InterDigital, Inc. |
R1-2404057 | Discussion on SBFD TX/RX/measurement procedures | TCL |
R1-2404112 | SBFD operation and procedures | Samsung |
R1-2404174 | Discussion on Rel-19 SBFD operation | vivo |
R1-2404281 | Views on SBFD TX/RX/measurement procedures | Apple |
R1-2404317 | SBFD procedures in RRC_CONNECTED mode | Sharp |
R1-2404348 | Discussion on SBFD TX/RX/measurement procedures | Google Inc. |
R1-2404398 | Discussion on SBFD TX/RX/measurement procedures | CATT |
R1-2404425 | Discussion on SBFD TX/RX/measurement procedures | China Telecom |
R1-2404453 | Discussion on SBFD TX/RX/measurement procedures | CMCC |
R1-2404497 | SBFD Operations | Sony |
R1-2404516 | Discussion on SBFD TX/RX/measurement procedures | MediaTek Inc. |
R1-2404591 | Discussion on Tx/Rx/Measurement procedures for SBFD operation | Fujitsu |
R1-2404595 | Discussion on SBFD TX/RX/measurement procedures | Panasonic |
R1-2404615 | Discussion on reception and transmission procedure for SBFD operation | Xiaomi |
R1-2404732 | Discussion on SBFD TX/RX/measurement procedures | Langbo |
R1-2404772 | Discussion on SBFD TX/RX/measurement procedures | ETRI |
R1-2404792 | Discussion on subband non-overlapping full duplex Tx-Rx and measurement operations | NEC |
R1-2404816 | Discussion on SBFD operation | Transsion Holdings |
R1-2404865 | Discussion on SBFD Tx/Rx/measurement procedures | OPPO |
R1-2404955 | Views on SBFD TX/RX Measurement Procedures | Lenovo |
R1-2405039 | Discussion on SBFD TX/RX/measurement procedures | NTT DOCOMO, INC. |
R1-2405060 | On SBFD TX/RX/measurement procedures | Nokia, Nokia Shanghai Bell |
R1-2405112 | Discussion on SBFD TX/RX/measurement procedures | ITRI |
R1-2405123 | Discussions on SBFD TX/RX/measurement procedures | Ruijie Networks Co. Ltd |
R1-2405152 | SBFD Transmission, Reception and Measurement Procedures | Qualcomm Incorporated |
R1-2405199 | Tx Rx procedure for SBFD | ASUSTeK |
R1-2405240 | Discussion on SBFD TX/RX/ measurement procedures | CEWiT |
R1-2405259 | Discussion on SBFD Tx/Rx/measurement procedures | KT Corp. |
R1-2405280 | Discussion on SBFD TX/RX/measurement procedures | WILUS Inc. |
R1-2405422 | Summary #1 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
R1-2405423 | Summary #2 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
R1-2405424 | Summary #3 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
R1-2405425 | Summary #4 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2403873 | Discussion for SBFD random access operation | New H3C Technologies Co., Ltd. |
R1-2403893 | Discussion on SBFD Random Access Operation | Tejas Networks Limited |
R1-2403905 | Discussion on SBFD random access operation | LG Electronics |
R1-2403912 | SBFD random access operation | Ericsson |
R1-2403935 | On subband full duplex random access operation | Huawei, HiSilicon |
R1-2404008 | Discussion on SBFD random access operation | ZTE |
R1-2404024 | Discussion on SBFD random access operation | Spreadtrum Communications, BUPT |
R1-2404048 | Discussion on SBFD random access operation | InterDigital, Inc. |
R1-2404056 | Discussion on SBFD random access operation | Korea Testing Laboratory |
R1-2404058 | Discussion on SBFD random access operation | TCL |
R1-2404113 | Random access on SBFD resources | Samsung |
R1-2404175 | Discussion on random access for Rel-19 SBFD | vivo |
R1-2404282 | Views on SBFD random access operation | Apple |
R1-2404318 | Random access in SBFD symbols | Sharp |
R1-2404399 | Discussion on SBFD random access operation | CATT |
R1-2404426 | Discussion on SBFD random access operation | China Telecom |
R1-2404454 | Discussion on SBFD random access operation | CMCC |
R1-2404498 | SBFD PRACH Operations | Sony |
R1-2404517 | Discussion on SBFD Random Access Operation | MediaTek Inc. |
R1-2404597 | Discussion on SBFD random access operation | Panasonic |
R1-2404616 | Discussion on SBFD random access operation | Xiaomi |
R1-2404661 | Discussion on random access for SBFD | NEC |
R1-2404678 | Discussion on SBFD for random access operation | SK Telecom |
R1-2404696 | SBFD random access operation | Lenovo |
R1-2404733 | Discussion on SBFD random access operation | Langbo |
R1-2404740 | Discussion on SBFD random access operation | Hyundai Motor Company |
R1-2404773 | SBFD random access operation | ETRI |
R1-2404804 | Discussion on SBFD random access operation | Fujitsu |
R1-2404817 | Discussion on SBFD random access operation | Transsion Holdings |
R1-2404866 | Discussion on SBFD random access operation | OPPO |
R1-2404934 | On SBFD random access operation | Google Inc. |
R1-2405040 | Discussion on SBFD random access operation | NTT DOCOMO, INC. |
R1-2405061 | SBFD random access operation | Nokia, Nokia Shanghai Bell |
R1-2405097 | Discussion on SBFD Random Access operation | KT Corp. |
R1-2405113 | Discussion on SBFD random access operation for SBFD aware UEs in RRC CONNECTED state | ITRI |
R1-2405153 | SBFD Random Access Operation | Qualcomm Incorporated |
R1-2405200 | Random access procedure for SBFD | ASUSTeK |
R1-2405281 | Discussion on SBFD random access operation | WILUS Inc. |
R1-2405349 | Random access on SBFD resources | Samsung |
R1-2405375 | Summary#1 on SBFD random access operation | Moderator (CMCC) |
R1-2405376 | Summary#2 on SBFD random access operation | Moderator (CMCC) |
R1-2405377 | Summary#3 on SBFD random access operation | Moderator (CMCC) |
R1-2405656 | Summary#4 on SBFD random access operation | Moderator (CMCC) |
R1-2405657 | Summary#5 on SBFD random access operation | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2403875 | Discussion on CLI handling | New H3C Technologies Co., Ltd. |
R1-2403894 | Discussion on gNB-gNB CLI handling | Tejas Networks Limited |
R1-2403906 | Discussion on CLI handling | LG Electronics |
R1-2403913 | SBFD CLI handling | Ericsson |
R1-2403936 | On cross-link interference handling for subband full duplex | Huawei, HiSilicon |
R1-2404009 | Discussion on CLI handling for Rel-19 duplex operation | ZTE |
R1-2404025 | Discussion on CLI handling | Spreadtrum Communications |
R1-2404049 | Discussion on CLI handling for SBFD operation | InterDigital, Inc. |
R1-2404114 | Cross-link interference handling for SBFD | Samsung |
R1-2404176 | Discussion on CLI handling for Rel-19 NR duplex | vivo |
R1-2404222 | Aspects for further discussion on CLI | Deutsche Telekom |
R1-2404283 | Views on CLI handling | Apple |
R1-2404400 | Discussion on CLI handling for NR duplex evolution | CATT |
R1-2404455 | Discussion on CLI handling | CMCC |
R1-2404499 | CLI Handling for SBFD | Sony |
R1-2404518 | Discussion on CLI Handling in SBFD system | MediaTek Inc. |
R1-2404530 | Cross-link interference management for duplexing evolution | Lenovo |
R1-2404617 | Discussion on CLI handling for SBFD operation | Xiaomi |
R1-2404662 | CLI handling for NR duplex operations | NEC |
R1-2404726 | Discussion on CLI handling | Panasonic |
R1-2404774 | Discussion on CLI handling for SBFD operation | ETRI |
R1-2404818 | Discussion on SBFD CLI handling | Transsion Holdings |
R1-2404867 | CLI handling in NR duplex operation | OPPO |
R1-2404935 | On the gNB-to-gNB CLI and the UE-to-UE CLI handling | Google Inc. |
R1-2405041 | Discussion on CLI handling | NTT DOCOMO, INC. |
R1-2405062 | Cross-link interference handling for duplex evolution | Nokia, Nokia Shanghai Bell |
R1-2405154 | Enhancements for CLI handling | Qualcomm Incorporated |
R1-2405241 | Discussion on CLI handling | CEWiT |
R1-2405282 | Discussion on CLI handling for evolution of NR duplex operation | WILUS Inc. |
R1-2405468 | Summary #1 of CLI handling | Moderator (Huawei) |
R1-2405469 | Summary #2 of CLI handling | Moderator (Huawei) |
R1-2405470 | Summary #3 of CLI handling | Moderator (Huawei) |
R1-2405641 | Summary #4 of CLI handling | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2405696 | Session notes for 9.4 (Study on solutions for Ambient IoT in NR) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2403840 | Evaluation assumptions and results for Ambient IoT | Ericsson |
R1-2403858 | Discussion on evaluation assumptions and results for Ambient IoT devices | FUTUREWEI |
R1-2403885 | Evaluation assumption and preliminary results for Ambient IoT | Tejas Networks Limited |
R1-2403886 | Evaluation assumptions and results for Ambient IoT | Nokia |
R1-2403952 | Evaluation methodology and assumptions for Ambient IoT | Huawei, HiSilicon |
R1-2404026 | Discussion on evaluation assumptions and results for Ambient IoT | Spreadtrum Communications |
R1-2404115 | Considerations for evaluation assumptions and results | Samsung |
R1-2404177 | Evaluation methodologies assumptions and results for Ambient IoT | vivo |
R1-2404284 | On evaluation assumptions and link budget analysis for AIoT | Apple |
R1-2404401 | The evaluation methodology and preliminary results of Ambient IoT | CATT |
R1-2404427 | Discussion on evaluation assumptions and results for Ambient IoT | China Telecom |
R1-2404456 | Discussion on evaluation methodology and assumptions | CMCC |
R1-2404500 | Initial evaluation results for Ambient IoT | Sony |
R1-2404554 | Discussion on Ambient IoT evaluations | ZTE, Sanechips |
R1-2404618 | Evaluation methodology and assumptions for Ambient IoT | Xiaomi |
R1-2404793 | Discussion on ambient IoT evaluation framework | NEC |
R1-2404868 | Discussion on evaluation assumptions and results for A-IoT | OPPO |
R1-2404888 | Discussion on Ambient IoT evaluation | LG Electronics |
R1-2404939 | Discussion on the evaluation assumptions for Ambient IoT devices | Lenovo |
R1-2404957 | Evaluation assumptions for Ambient IoT | InterDigital, Inc. |
R1-2405042 | Study on evaluation assumptions for Ambient IoT | NTT DOCOMO, INC. |
R1-2405076 | Evaluation assumptions and results | MediaTek Inc. |
R1-2405155 | Evaluation Assumptions and Results | Qualcomm Incorporated |
R1-2405214 | Evaluation assumptions for Ambient IoT | Comba |
R1-2405296 | Evaluation assumption and preliminary results for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405364 | Considerations for evaluation assumptions and results | Samsung |
R1-2405435 | FL summary #1 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2405436 | FL summary #2 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2405437 | FL summary #3 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2405745 | Final FL summary for Ambient IoT evaluation | Moderator (CMCC) |
R1-2405772 | Email discussion on Ambient IoT evaluation assumptions | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2403841 | Ambient IoT device architectures | Ericsson |
R1-2403859 | Discussion on Rel-19 Ambient IoT device architecture | FUTUREWEI |
R1-2403880 | Discussion on ambient IoT device architectures | TCL |
R1-2403887 | Ambient IoT device architectures | Nokia |
R1-2403953 | Ultra low power device architectures for Ambient IoT | Huawei, HiSilicon |
R1-2404027 | Discussion on Ambient IoT device architectures | Spreadtrum Communications |
R1-2404116 | Considerations for Ambient-IoT device architectures | Samsung |
R1-2404178 | Discussion on Ambient IoT Device architectures | vivo |
R1-2404285 | On device architecture for AIoT | Apple |
R1-2404321 | Discussion on Ambient-IoT Device Architecture | Everactive |
R1-2404402 | Study of the Ambient IoT devices architecture | CATT |
R1-2404428 | Discussion on Ambient IoT device architectures | China Telecom |
R1-2404457 | Discussion on Ambient IoT device architectures | CMCC |
R1-2404501 | Ambient IoT device architectures | Sony |
R1-2404555 | Discussion on Ambient IoT device architectures | ZTE, Sanechips |
R1-2404619 | Discussion on ambient IoT device architectures | Xiaomi |
R1-2404794 | Device architecture requirements for ambient IoT | NEC |
R1-2404869 | Discussion on device architecture for A-IoT device | OPPO |
R1-2404889 | Discussion on Ambient IoT device architectures | LG Electronics |
R1-2404940 | Discussion on the Ambient IoT device architectures | Lenovo |
R1-2404958 | Device architectures for Ambient IoT | InterDigital, Inc. |
R1-2405043 | Study on device architectures for Ambient IoT | NTT DOCOMO, INC. |
R1-2405077 | Ambient IoT device architectures | MediaTek Inc. |
R1-2405156 | Ambient IoT Device Architecture | Qualcomm Incorporated |
R1-2405215 | Ambient IoT Device Architecture | Comba |
R1-2405297 | Views on Architecture of Ambient IoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405431 | FL Summary #1 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2405432 | FL Summary #2 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2405433 | FL Summary #3 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2405434 | FL Summary #4 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2403842 | General aspects of physical layer design for Ambient IoT | Ericsson |
R1-2403860 | Discussion on physical layer design for Rel-19 Ambient IoT devices | FUTUREWEI |
R1-2403881 | Discussion on general aspects of physical layer design for Ambient IoT | TCL |
R1-2403888 | General aspects of physical layer design for Ambient IoT | Nokia |
R1-2403954 | On general aspects of physical layer design for Ambient IoT | Huawei, HiSilicon |
R1-2404005 | Discussion on Physical Layer Design for Ambient-IoT | EURECOM |
R1-2404028 | Discussion on general aspects of physical layer design for Ambient IoT | Spreadtrum Communications |
R1-2404117 | Considerations on general aspects of Ambient IoT | Samsung |
R1-2404179 | Discussion on General Aspects of Physical Layer Design | vivo |
R1-2404286 | On general physical layer design aspects for AIoT | Apple |
R1-2404345 | On General Physical Layer Design Considerations for Ambient IoT (internet of things) Applications | Lekha Wireless Solutions |
R1-2404403 | Discussion on general aspects of physical layer design | CATT |
R1-2404429 | Discussion on general aspects of physical layer design for Ambient IoT | China Telecom |
R1-2404458 | Discussion on general aspects of A-IoT physical layer design | CMCC |
R1-2404502 | General aspects of physical layer design for Ambient IoT | Sony |
R1-2404556 | Discussion on general aspects of physical layer design for Ambient IoT | ZTE, Sanechips |
R1-2404592 | Consideration on general aspects of physical layer | Fujitsu |
R1-2404620 | Discussion on physical layer design of Ambient IoT | Xiaomi |
R1-2404674 | Discussion on general aspects of ambient IoT physical layer design | NEC |
R1-2404743 | General aspects of physical layer design for Ambient IoT | Panasonic |
R1-2404775 | Discussion on general aspects of physical layer design | ETRI |
R1-2404870 | Discussion on general aspects of physical layer design of A-IoT communication | OPPO |
R1-2404890 | General aspects of Ambient IoT physical layer design | LG Electronics |
R1-2404941 | Discussion on the physical layer design aspects for Ambient IoT devices | Lenovo |
R1-2404959 | Discussion on general aspects of physical layer design for Ambient IoT | InterDigital, Inc. |
R1-2404962 | Discussion on general aspects of physical layer design | Sharp |
R1-2405044 | Study on general aspects of physical layer design for Ambient IoT | NTT DOCOMO, INC. |
R1-2405078 | General aspects of physical layer design | MediaTek Inc. |
R1-2405124 | Discussions on general aspects of physical layer design for Ambient IoT | Ruijie Networks Co. Ltd |
R1-2405157 | General aspects of physical layer design | Qualcomm Incorporated |
R1-2405216 | Discussion on physical layer design for Ambient IoT | Comba |
R1-2405224 | General aspects of physical layer design for Ambient IoT | ITL |
R1-2405242 | Discussion on General aspects of physical layer design | CEWiT |
R1-2405269 | Ambient IoT – General aspects of physical layer design, performance for uplink modulation | Wiliot Ltd. |
R1-2405298 | Discussion on General aspects of physical layer design for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405439 | Feature Lead Summary #1 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
R1-2405440 | Feature Lead Summary #2 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
R1-2405441 | Feature Lead Summary #3 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2403843 | Frame structure and timing aspects for Ambient IoT | Ericsson |
R1-2403861 | Frame Structure and Timing Aspects for Ambient IoT | FUTUREWEI |
R1-2403889 | Frame structure and timing aspects for Ambient IoT | Nokia |
R1-2403955 | On frame structure and timing aspects of Ambient IoT | Huawei, HiSilicon |
R1-2403966 | Discussions on frame structure and timing aspects for A-IoT | Intel Corporation |
R1-2404029 | Discussion on frame structure and timing aspects for Ambient IoT | Spreadtrum Communications |
R1-2404118 | Considerations for frame structure and timing aspects | Samsung |
R1-2404180 | Discussion on Frame structure, random access, scheduling and timing aspects | vivo |
R1-2404219 | Discussion on frame structure and physical layer procedures for Ambient IoT | Lenovo |
R1-2404287 | Frame structure and timing aspects for Ambient IoT | Apple |
R1-2404329 | Discussion on frame structure and timing aspects for Ambient IoT | TCL |
R1-2404404 | Study of Frame structure and timing aspects for Ambient IoT | CATT |
R1-2404430 | Discussion on frame structure and timing aspects for Ambient IoT | China Telecom |
R1-2404459 | Discussion on frame structure and timing aspects for A-IoT | CMCC |
R1-2404503 | Frame structure and timing aspects for Ambient IoT | Sony |
R1-2404519 | Frame structure and timing aspects of Ambient IoT | InterDigital, Inc. |
R1-2404557 | Discussion on frame structure and physical layer procedure for Ambient IoT | ZTE, Sanechips |
R1-2404593 | Discussion on frame structure and timing aspects | Fujitsu |
R1-2404596 | Discussion on A-IoT Frame Structure and Timing Aspects | Panasonic |
R1-2404621 | Discussion on frame structure and timing aspects for Ambient IoT | Xiaomi |
R1-2404675 | Discussion on frame structure and timing for ambient IoT | NEC |
R1-2404734 | Discussion on frame structure and timing aspects for Ambient IoT | BUPT |
R1-2404776 | Discussion on frame structure and timing aspects | ETRI |
R1-2404798 | Some Considerations on Frame Structure and Timing Aspects for A-IoT | Continental Automotive |
R1-2404803 | Discussion on Frame Structure and Timing Aspects for Ambient IoT | IIT, Kharagpur |
R1-2404871 | Discussion on frame structure and timing aspects of A-IoT communication | OPPO |
R1-2404891 | Frame structure and timing aspects for Ambient IoT | LG Electronics |
R1-2404963 | Discussion on frame structure and timing aspects | Sharp |
R1-2405045 | Study on frame structure and timing aspects for Ambient IoT | NTT DOCOMO, INC. |
R1-2405079 | Frame structure and timing aspects | MediaTek Inc. |
R1-2405158 | Frame structure and timing aspects | Qualcomm Incorporated |
R1-2405181 | Discussion on Frame structure and timing aspects for A-IoT | Unicompay |
R1-2405183 | Discussion on Frame structure and timing aspects for A-IoT | China Unicom |
R1-2405208 | Discussion on frame structure and timing aspect | ASUSTeK |
R1-2405217 | Discussion on frame structure and timing aspects for Ambient IoT | Comba |
R1-2405243 | Discussion on Frame structure and timing aspects | CEWiT |
R1-2405273 | Discussion on frame structure and timing aspects | |
R1-2405299 | Frame structure and timing aspects for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405379 | FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2405380 | FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2405381 | FL summary #3 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2403844 | Downlink and uplink channel/signal aspects for Ambient IoT | Ericsson |
R1-2403862 | D2R and R2D Channel/Signal Aspects for Ambient IoT | FUTUREWEI |
R1-2403882 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | TCL |
R1-2403890 | R2D and D2R channel/signal aspects for Ambient IoT | Nokia |
R1-2403956 | Physical channels and signals for Ambient IoT | Huawei, HiSilicon |
R1-2403967 | Discussions on physical channel and signals for A-IoT | Intel Corporation |
R1-2404030 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | Spreadtrum Communications |
R1-2404119 | Considerations for downlink and uplink channel/signal aspect | Samsung |
R1-2404181 | Discussion on Downlink and uplink channel/signal aspects | vivo |
R1-2404220 | Discussion on channel/signal aspects for Ambient IoT | Lenovo |
R1-2404288 | On physical channels/signals and proximity determination for AIoT | Apple |
R1-2404290 | FL summary#1 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2404291 | FL summary#2 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2404292 | FL summary#3 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2404405 | DL and UL Physical Channels/signals design in support of Ambient IoT devices | CATT |
R1-2404431 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | China Telecom |
R1-2404460 | Discussion on downlink and uplink channel/signal aspects | CMCC |
R1-2404504 | Downlink and uplink physical channel for Ambient IoT | Sony |
R1-2404520 | Downlink and uplink channels aspects of Ambient IoT | InterDigital, Inc. |
R1-2404558 | Discussion on channel and signal for Ambient IoT | ZTE, Sanechips |
R1-2404576 | Discussion on downlink and uplink channel/signal aspects for A-IoT | HONOR |
R1-2404594 | Discussion on downlink and uplink channel/signal aspects | Fujitsu |
R1-2404622 | Discussion on downlink and uplink channel_signal aspects for Ambient IoT | Xiaomi |
R1-2404676 | Discussion on downlink and uplink channel for ambient IoT | NEC |
R1-2404777 | Downlink and uplink channel/signal aspects for A-IoT | ETRI |
R1-2404799 | Considerations on Downlink and Uplink Channels/Signals for A-IoT | Continental Automotive |
R1-2404872 | Discussion on downlink and uplink channel/signal aspects for A-IoT | OPPO |
R1-2404892 | Downlink and uplink channel/signal aspects for Ambient IoT | LG Electronics |
R1-2404901 | Discussion on downlink and uplink channels and signals for A-IoT | Panasonic |
R1-2404937 | Considerations for downlink and uplink channel/signal aspects | Semtech Neuchatel SA |
R1-2404964 | Discussion on downlink and uplink channel/signal aspects | Sharp |
R1-2405046 | Study on downlink and uplink channel/signal aspects for Ambient IoT | NTT DOCOMO, INC. |
R1-2405080 | Downlink and uplink channel/signal aspects | MediaTek Inc. |
R1-2405159 | Downlink and uplink channel/signal aspects | Qualcomm Incorporated |
R1-2405184 | Discussion on downlink and uplink channel aspects for A-IoT | China Unicom |
R1-2405218 | Discussion on downlink and uplink channel and signal for Ambient IoT | Comba |
R1-2405244 | Discussion on Downlink and Uplink channel/signal aspects | CEWiT |
R1-2405274 | Discussion on downlink and uplink transmission aspects | |
R1-2405300 | Discussion on Downlink and uplink channel signal aspects for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
TDoc | Title | Source |
---|---|---|
R1-2403845 | Waveform characteristics of carrier wave provided externally to the Ambient IoT device | Ericsson |
R1-2403863 | Discussion on External Carrier Waveform Characteristics for Rel-19 Ambient IoT devices | FUTUREWEI |
R1-2403883 | Discussion on waveform characteristics of external carrier-wave for Ambient IoT | TCL |
R1-2403891 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | Nokia |
R1-2403957 | On external carrier wave for backscattering based Ambient IoT device | Huawei, HiSilicon |
R1-2403968 | Discussions on waveform characteristics of carrier-wave for A-IoT | Intel Corporation |
R1-2404031 | Discussion on waveform characteristics of external carrier-wave for Ambient IoT | Spreadtrum Communications |
R1-2404120 | Considerations for Waveform characteristics of carrier-wave | Samsung |
R1-2404182 | Discussion on CW waveform and interference handling at AIoT UL receiver | vivo |
R1-2404221 | Discussion on external carrier wave for Ambient IoT | Lenovo |
R1-2404289 | On carrier waveform and interference handling for AIoT | Apple |
R1-2404406 | Discussion on the waveform characteristics of carrier-wave for the Ambient IoT device | CATT |
R1-2404432 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | China Telecom |
R1-2404461 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | CMCC |
R1-2404505 | External carrier wave for Ambient IoT | Sony |
R1-2404559 | Discussion on carrier wave for Ambient IoT | ZTE, Sanechips |
R1-2404623 | Discussion on waveform characteristics of carrier-wave | Xiaomi |
R1-2404778 | Waveform characteristics of carrier-wave provided externally to the A-IoT device | ETRI |
R1-2404873 | Discussion on Waveform characteristics of carrier-wave provided externally to the A-IoT device | OPPO |
R1-2404893 | Considerations on carrier-wave transmission for Ambient IoT | LG Electronics |
R1-2404902 | Discussion on waveform characteristics of carrier-wave for Ambient IoT device | Panasonic |
R1-2404938 | Considerations for carrier-wave aspects | Semtech Neuchatel SA |
R1-2404960 | Discussion on carrier-wave for Ambient IoT | InterDigital, Inc. |
R1-2404965 | Discussion on waveform characteristics of externally provided carrier-wave | Sharp |
R1-2405006 | Analyses on interference between AIoT and NR | Fujitsu |
R1-2405047 | Study on waveform characteristics of carrier-wave for Ambient IoT | NTT DOCOMO, INC. |
R1-2405081 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | MediaTek Inc. |
R1-2405160 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | Qualcomm Incorporated |
R1-2405185 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | China Unicom |
R1-2405219 | Discussion on waveform characteristics of carrier-wave for Ambient IoT | Comba |
R1-2405245 | Discussion on Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | CEWiT |
R1-2405275 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | |
R1-2405301 | Discussion on Carrier wave related aspects for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2405438 | FL summary#1 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2405549 | FL summary#2 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2405729 | Final FL summary on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
TDoc | Title | Source |
---|---|---|
R1-2403869 | Discussion of on-demand SSB Scell operation | FUTUREWEI |
R1-2403896 | On-demand SSB SCell operation | Tejas Networks Limited |
R1-2403960 | On-demand SSB SCell operation for eNES | Huawei, HiSilicon |
R1-2403978 | Design of on-demand SSB SCell operation | Intel Corporation |
R1-2404032 | Discussion on on-demand SSB SCell operation | Spreadtrum Communications |
R1-2404121 | On-demand SSB SCell operation | Samsung |
R1-2404183 | Discussions on on-demand SSB Scell operation | vivo |
R1-2404223 | On-demand SSB SCell Operation | Nokia, Nokia Shanghai Bell |
R1-2404293 | On-demand SSB SCell Operation | Apple |
R1-2404332 | Discussion on on-demand SSB SCell operation | InterDigital, Inc. |
R1-2404407 | Discussion on on-demand SSB SCell operation | CATT |
R1-2404433 | Discussion on on-demand SSB operation for SCell | China Telecom |
R1-2404462 | Discussion on on-demand SSB SCell operation | CMCC |
R1-2404506 | On-demand SSB SCell operation | Sony |
R1-2404560 | Discussion on on-demand SSB for NES | ZTE, Sanechips |
R1-2404577 | Discussion on on-demand SSB SCell operation | HONOR |
R1-2404624 | Discussion on on-demand SSB SCell operation | Xiaomi |
R1-2404648 | On-demand SSB Scell operation | Quectel |
R1-2404689 | On-demand SSB SCell Operation | |
R1-2404697 | On-demand SSB SCell operation | Lenovo |
R1-2404757 | Discussion on on-demand SSB SCell operation | Panasonic |
R1-2404779 | Discussion on On-demand SSB SCell operation | ETRI |
R1-2404795 | Discussion on on-demand SSB for SCell operation | NEC |
R1-2404807 | Discussion on on-demand SSB SCell operation | Fujitsu |
R1-2404819 | Discussion on On-Demand SSB SCell operation | Transsion Holdings |
R1-2404858 | Discussion on the enhancement to support on demand SSB SCell operation | OPPO |
R1-2404894 | On-demand SSB SCell operation | LG Electronics |
R1-2405048 | Discussion on on-demand SSB SCell operation | NTT DOCOMO, INC. |
R1-2405070 | Discussion on on-demand SSB SCell operation | Sharp |
R1-2405084 | On-demand SSB SCell operation | MediaTek Inc. |
R1-2405105 | On-demand SSB SCell operation | Ericsson |
R1-2405114 | Discussion on On-demand SSB SCell operation | ITRI |
R1-2405126 | Discussion of On-demand SSB SCell operation | Mavenir |
R1-2405127 | Discussion on on-demand SSB SCell operation | CAICT |
R1-2405161 | On-demand SSB operation for Scell | Qualcomm Incorporated |
R1-2405201 | On-demand SSB for SCell | ASUSTeK |
R1-2405211 | On-demand SSB SCell operation for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2405246 | Discussion on on-demand SSB Scell operation | CEWiT |
R1-2405495 | Summary #4 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2405496 | Summary #2 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2405497 | Summary #3 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2405498 | Summary #1 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2405723 | Summary #5 of on-demand SSB for NES | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2403870 | Discussion of on-demand SIB1 for idle/inactive mode UEs | FUTUREWEI |
R1-2403942 | Discussion on on-demand SIB1 for eNES | Huawei, HiSilicon |
R1-2403979 | Study on on-demand SIB1 for Idle/inactive mode Ues | Intel Corporation |
R1-2404033 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Spreadtrum Communications |
R1-2404122 | On-demand SIB1 for idle/inactive mode UEs | Samsung |
R1-2404184 | Discussions on on-demand SIB1 for idle/inactive mode UEs | vivo |
R1-2404224 | On-demand SIB1 for Idle/Inactive mode UEs | Nokia, Nokia Shanghai Bell |
R1-2404294 | On on-demand SIB1 for IDLE/INACTIVE mode UE | Apple |
R1-2404333 | Discussion on on-demand SIB1 for idle/inactive mode UEs | InterDigital, Inc. |
R1-2404408 | Discussion on on-demand SIB1 | CATT |
R1-2404434 | Discussion on on-demand SIB1 for idle/inactive mode UEs | China Telecom |
R1-2404463 | Discussion on on-demand SIB1 for UEs in idle/inactive mode | CMCC |
R1-2404507 | On-demand SIB1 for idle/inactive mode UEs | Sony |
R1-2404561 | Discussion on on-demand SIB1 for UEs | ZTE, Sanechips |
R1-2404625 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Xiaomi |
R1-2404690 | On-demand SIB1 for Idle/Inactive Mode UE | |
R1-2404698 | On-demand SIB1 for idle/inactive mode UEs | Lenovo |
R1-2404758 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Panasonic |
R1-2404780 | On-demand SIB1 for idle/inactive mode UEs for NES | ETRI |
R1-2404796 | Discussion on on-demand SIB1 for UEs in idle/inactive mode | NEC |
R1-2404800 | Discussion on on-demand SIB1 for idle/inactive mode UEs | DENSO CORPORATION |
R1-2404808 | Discussion on on-demand SIB1 transmission for idle/inactive mode UEs | Fujitsu |
R1-2404820 | Discussion on on-demand SIB1 transmission for idle/inactive mode UEs | Transsion Holdings |
R1-2404859 | Discussion on the enhancement to support on demand SIB1 for idle/inactive mode UE | OPPO |
R1-2404895 | On-demand SIB1 for idle/inactive mode UEs | LG Electronics |
R1-2405049 | Discussion on on-demand SIB1 for idle/inactive mode UEs | NTT DOCOMO, INC. |
R1-2405071 | Discussion on on-demand SIB1 transmission for idle UEs | Sharp |
R1-2405085 | On-demand SIB1 for idle or inactive mode UEs | MediaTek Inc. |
R1-2405106 | Study of on-demand SIB1 for UEs in idle/inactive mode for NES | Ericsson |
R1-2405162 | On-demand SIB1 procedure | Qualcomm Incorporated |
R1-2405177 | Discussion on on-demand SIB1 for idle/inactive mode UEs | KT Corp. |
R1-2405182 | On-demand SIB1 for Idle/Inactive mode UEs | III |
R1-2405202 | Triggering of on-demand SIB1 | ASUSTeK |
R1-2405207 | On-demand SIB1 for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2405213 | Views on On-demand SIB1 operation for idle/inactive UEs | Vodafone |
R1-2405247 | Discussion on on-demand SIB1 | CEWiT |
R1-2405341 | On-demand SIB1 for idle or inactive mode UEs | MediaTek Inc. |
R1-2405363 | Discussions on on-demand SIB1 for idle/inactive mode UEs | vivo |
R1-2405370 | FL summary 1 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2405371 | FL summary 2 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2405372 | FL summary 3 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2405373 | FL summary 4 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2405595 | On-demand SIB1 for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2405632 | FL summary 5 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2405658 | FL summary 6 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2403871 | Discussion of the adaptation of common signal/channel transmissions | FUTUREWEI |
R1-2403895 | Adaptation of common signal/channel transmissions | Tejas Networks Limited |
R1-2403943 | On common channel/signal adaptation for eNES | Huawei, HiSilicon |
R1-2403980 | Adaptation of common signal/channel transmissions for Network Energy Saving | Intel Corporation |
R1-2404034 | Discussion on adaptation of common signal/channel transmissions | Spreadtrum Communications |
R1-2404123 | Adaptation of common signal/channel transmissions | Samsung |
R1-2404185 | Discussions on adaptation of common signal/channel transmissions | vivo |
R1-2404225 | Adaptation of common signal/channel transmissions | Nokia, Nokia Shanghai Bell |
R1-2404295 | On adaptation of common signal/channel for NES enhancements | Apple |
R1-2404334 | Discussion on adaptation of common signal/channel transmissions | InterDigital, Inc. |
R1-2404409 | Discussion on adaptation of common signal/channel transmissions | CATT |
R1-2404464 | Discussion on adaptation of common signal/channel transmissions | CMCC |
R1-2404489 | Adaptation of common signals and channels | Lenovo |
R1-2404508 | Adaptation of common signal/channel transmissions | Sony |
R1-2404562 | Discussion on common signal channel for NES | ZTE, Sanechips |
R1-2404578 | Discussion on adaptation of common signal channel transmissions | HONOR |
R1-2404626 | Discussion on adaptation of common signal and channel transmissions | Xiaomi |
R1-2404691 | Adaptation of Common Signals | |
R1-2404759 | Discussion on adaptation of common signal/channel transmission | Panasonic |
R1-2404781 | Adaptation of common signal/channel transmissions for NES | ETRI |
R1-2404797 | Discussion on adaptation of common signal/channel transmissions for Cell DTX/DRX | NEC |
R1-2404809 | Discussion on adaptation of common signal / channel transmissions | Fujitsu |
R1-2404821 | Discussion on adaptive transmission of common signal or common channel | Transsion Holdings |
R1-2404860 | Discussion on adaptation of common signal/channel transmission | OPPO |
R1-2404896 | Adaptation of common signal/channel transmissions | LG Electronics |
R1-2405050 | Discussion on adaptation of common signal/channel transmissions | NTT DOCOMO, INC. |
R1-2405072 | Discussion on adaptation of common signal/channel transmissions | Sharp |
R1-2405086 | Adaptation of common signal/channel transmissions | MediaTek Inc. |
R1-2405107 | Adaptation of common signal/channel transmissions for NES | Ericsson |
R1-2405128 | Adaptation of Common Signal Channel Transmissions | Mavenir |
R1-2405163 | Adaptation of common channel transmissions | Qualcomm Incorporated |
R1-2405179 | Discussion on adaptation of common signal/channel transmissions | KT Corp. |
R1-2405209 | Adaptation of Common Signals and Channels for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2405248 | Discussion on adaptation of common signal and channel transmissions | CEWiT |
R1-2405459 | Summary#1 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2405460 | Summary#2 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2405630 | Summary#3 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2405631 | Summary#4 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2405743 | Final summary of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2405735 | Summary of RAN1 agreements on LP-WUS/WUR for NR | Rapporteur (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2403864 | Discussion on LP-WUS and LP-SS Design | FUTUREWEI |
R1-2403879 | Discussion on LP-WUS and LP-SS Design | EURECOM |
R1-2403948 | Signal Design of LP-WUS and LP-SS | Huawei, HiSilicon |
R1-2404035 | Discussion on LP-WUS and LP-SS design | Spreadtrum Communications |
R1-2404059 | Discussion on LP-WUS and LP-SS Design | TCL |
R1-2404124 | Discussion on LP-WUS and LP-SS design | Samsung |
R1-2404186 | Discussion on LP-WUS and LP-SS design | vivo |
R1-2404296 | LP-WUS and LP-SS design | Apple |
R1-2404312 | Discussion on LP-WUS and LP-SS design framework for Low power WUS | InterDigital, Inc. |
R1-2404320 | Discussion on LP-WUS and LP-SS design | Everactive |
R1-2404410 | Design of LP-WUS and LP-SS | CATT |
R1-2404465 | Discussion on LP-WUS and LP-SS design | CMCC |
R1-2404509 | LP-WUS and LP-SS design | Sony |
R1-2404563 | Discussion on LP-WUS design | ZTE, Sanechips |
R1-2404579 | Discussion on LP-WUS and LP-SS design | HONOR |
R1-2404627 | Discussion on LP-WUS and LP-SS design | Xiaomi |
R1-2404664 | Discussion on LP-WUS and LP-SS design | NEC |
R1-2404705 | LP-WUS and LP-SS design | Nokia |
R1-2404760 | Discussion on the LP-WUS and LP-SS design | Panasonic |
R1-2404852 | Signal design for LP-WUS and LP-SS | OPPO |
R1-2404897 | Discussion on LP-WUS and LP-SS design | LG Electronics |
R1-2404942 | Discussion on LP-WUS and LP-SS design | Lenovo |
R1-2404966 | Discussion on LP-WUS and LP-SS design | Sharp |
R1-2405051 | Discussion on LP-WUS and LP-SS design | NTT DOCOMO, INC. |
R1-2405073 | LP-WUS and LP-SS design | MediaTek Inc. |
R1-2405108 | LP-WUS and LP-SS design | Ericsson |
R1-2405164 | LP-WUS and LP-SS design | Qualcomm Incorporated |
R1-2405254 | On LP-WUS and LP-SS design | Nordic Semiconductor ASA |
R1-2405374 | LP-WUS and LP-SS design | Ericsson |
R1-2405499 | Summary #1 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2405519 | Summary #2 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2405600 | Summary #3 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2405645 | Summary #4 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2405655 | LP-WUS and LP-SS design | Nokia |
R1-2405708 | Summary #5 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2405732 | Final summary of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2403865 | Discussion on LP-WUS Operation in IDLE/INACTIVE Modes | FUTUREWEI |
R1-2403949 | Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode | Huawei, HiSilicon |
R1-2404036 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Spreadtrum Communications |
R1-2404125 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Samsung |
R1-2404136 | Discussion on LP-WUS Operation in IDLE/INACTIVE state | TCL |
R1-2404187 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | vivo |
R1-2404297 | LP-WUS operation in IDLE/INACTIVE modes | Apple |
R1-2404299 | Summary #1 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2404300 | Summary #2 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2404301 | Summary #3 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2404313 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | InterDigital, Inc. |
R1-2404411 | System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes | CATT |
R1-2404466 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | CMCC |
R1-2404510 | LP-WUS operation in IDLE / INACTIVE modes | Sony |
R1-2404564 | Discussion on LP-WUS operation in IDLE/INACTIVE mode | ZTE, Sanechips |
R1-2404628 | Discussion on LP-WUS operation in Idle/Inactive modes | Xiaomi |
R1-2404665 | Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode | NEC |
R1-2404706 | LP-WUS operation in IDLE/Inactive mode | Nokia |
R1-2404761 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Panasonic |
R1-2404782 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | ETRI |
R1-2404805 | Discussion on LP-WUS operation in IDLE/INACTIVE mode | Fujitsu |
R1-2404853 | Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes | OPPO |
R1-2404898 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | LG Electronics |
R1-2404943 | Discussion on LP-WUS operation in Idle/Inactive modes | Lenovo |
R1-2404967 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Sharp |
R1-2405052 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | NTT DOCOMO, INC. |
R1-2405074 | LP-WUS operation in IDLE/INACTIVE modes | MediaTek Inc. |
R1-2405109 | LP-WUS operation in IDLE and INACTIVE modes | Ericsson |
R1-2405165 | LP-WUR operation in idle and inactive modes | Qualcomm Incorporated |
R1-2405180 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | KT Corp. |
R1-2405253 | On LP-WUS operation in IDLE/Inactive | Nordic Semiconductor ASA |
R1-2405681 | Summary #4 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2405682 | Summary #5 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2403950 | Procedures and functionalities of LP-WUS in CONNECTED mode | Huawei, HiSilicon |
R1-2404001 | Discussion on LP-WUS procedures in Connected mode | TCL |
R1-2404037 | Discussion on LP-WUS operation in CONNECTED modes | Spreadtrum Communications |
R1-2404126 | Discussion on LP-WUS operation in CONNECTED modes | Samsung |
R1-2404188 | Discussion on LP-WUS operation in CONNECTED modes | vivo |
R1-2404298 | LP-WUS operation in CONNECTED modes | Apple |
R1-2404314 | Discussion on RRC CONNECTED mode LP-WUS monitoring | InterDigital, Inc. |
R1-2404412 | System design and procedure of LP-WUS operation for UE in CONNECTED Modes | CATT |
R1-2404440 | Discussion on LP-WUS operation in CONNECTED modes | Lenovo |
R1-2404467 | Discussion on LP-WUS operation in CONNECTED mode | CMCC |
R1-2404511 | LP-WUS operation in CONNECTED mode | Sony |
R1-2404565 | Discussion on LP-WUS operation in CONNECTED mode | ZTE, Sanechips |
R1-2404629 | Discussion on LP-WUS operation in Connected mode | Xiaomi |
R1-2404666 | Discussion on LP-WUS operation in RRC CONNECTED mode | NEC |
R1-2404707 | LP-WUS operation in CONNECTED mode | Nokia |
R1-2404762 | Discussion on LP-WUS operation in CONNECTED mode | Panasonic |
R1-2404783 | Discussion on LP-WUS operation in CONNECTED modes | ETRI |
R1-2404854 | Consideration on wake-up procedure in connected mode | OPPO |
R1-2404899 | Discussion on LP-WUS operation in CONNECTED modes | LG Electronics |
R1-2404968 | Discussion on LP-WUS operation in CONNECTED modes | Sharp |
R1-2405053 | Discussion on LP-WUS operation in CONNECTED mode | NTT DOCOMO, INC. |
R1-2405075 | LP-WUS operation in CONNECTED modes | MediaTek Inc. |
R1-2405110 | LP-WUS operation in CONNECTED mode | Ericsson |
R1-2405166 | LP-WUR operation in connected mode | Qualcomm Incorporated |
R1-2405471 | FL summary #1 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2405508 | LP-WUR operation in connected mode | Qualcomm Incorporated |
R1-2405512 | Discussion on LP-WUS operation in CONNECTED modes | vivo |
R1-2405592 | FL summary #2 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2405659 | FL summary #3 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2405721 | FL summary #4 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2404630 | Updated work plan on channel modelling for ISAC | Xiaomi, AT&T |
R1-2404631 | Skeleton CR for TR 38.901 to introduce channel model for ISAC | Xiaomi, AT&T |
R1-2404822 | Ray-Tracing based Channel Models for Automotive ISAC | DENSO CORPORATION |
R1-2405697 | Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2403916 | Discussion on ISAC deployment scenarios and requirements | EURECOM |
R1-2403920 | Deployment scenarios for ISAC channel model | Huawei, HiSilicon |
R1-2403964 | Deployment scenarios for ISAC channel modeling | Intel Corporation |
R1-2403994 | Discussion on ISAC deployment scenarios | Nokia, Nokia Shanghai Bell |
R1-2404038 | Discussion on ISAC deployment scenarios | Spreadtrum Communications |
R1-2404127 | Discussion on ISAC deployment scenarios | Samsung |
R1-2404189 | Views on Rel-19 ISAC deployment scenarios | vivo |
R1-2404302 | Discussion on ISAC deployment scenarios | Apple |
R1-2404327 | Discussion on ISAC deployment scenarios | LG Electronics |
R1-2404413 | Discussion on ISAC deployment scenarios | CATT, CICTCI |
R1-2404435 | Discussion on ISAC deployment scenarios | China Telecom |
R1-2404468 | Discussion on ISAC deployment scenarios | CMCC, China Southern Power Grid |
R1-2404486 | FL Summary #1 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2404487 | FL Summary #2 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2404488 | FL Summary #3 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2404512 | Views on ISAC Deployment Scenarios | Sony |
R1-2404522 | Deployment Scenarios for ISAC Channel Modeling | AT&T, FirstNet |
R1-2404541 | Deployment scenarios for integrated sensing and communication with NR | NVIDIA |
R1-2404572 | Discussion on ISAC deployment scenarios | Tiami Networks |
R1-2404573 | Discussion on ISAC deployment scenarios | Tiami Networks |
R1-2404632 | Deployment scenarios and evaluation assumptions for ISAC channel model | Xiaomi |
R1-2404651 | Discussion on ISAC deployment scenarios | InterDigital, Inc. |
R1-2404723 | Considerations on ISCA deployment scenarios | CAICT |
R1-2404875 | Discussion on ISAC deployment scenarios | OPPO |
R1-2404914 | Discussion on ISAC deployment scenarios | TOYOTA InfoTechnology Center |
R1-2404931 | Discussion on ISAC deployment scenarios | Lenovo |
R1-2405002 | Discussion on ISAC deployment scenarios | ZTE |
R1-2405009 | Discussion on ISAC Deployment Scenarios | Ericsson |
R1-2405054 | Study on deployment scenarios for ISAC channel modelling | NTT DOCOMO, INC. |
R1-2405094 | Discussion on ISAC deployment scenario | MediaTek Inc. |
R1-2405115 | Discussion on deployment scenarios for ISAC channel mode | ITRI |
R1-2405167 | Discussion on ISAC deployment scenarios | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R1-2403917 | Discussion on ISAC channel modeling | EURECOM |
R1-2403921 | Channel modelling for ISAC | Huawei, HiSilicon |
R1-2403965 | Discussion on ISAC channel modeling | Intel Corporation |
R1-2403995 | Discussion on ISAC channel modelling | Nokia, Nokia Shanghai Bell |
R1-2404039 | Discussion on ISAC channel modeling | Spreadtrum Communications |
R1-2404128 | Discussion on ISAC channel modelling | Samsung |
R1-2404190 | Views on Rel-19 ISAC channel modelling | vivo |
R1-2404303 | Discussion on ISAC channel modelling | Apple |
R1-2404328 | Discussion on ISAC channel modelling | LG Electronics |
R1-2404344 | Discussions on ISAC Channel Modelling | Lekha Wireless Solutions |
R1-2404414 | Discussion on ISAC channel modelling | CATT, CICTCI |
R1-2404417 | Discussion on ISAC channel modeling | BUPT, CMCC |
R1-2404436 | Discussion on ISAC channel modelling | China Telecom |
R1-2404469 | Discussion on channel modeling methodology for ISAC | CMCC,BUPT,SEU, PML |
R1-2404477 | Discussion on ISAC Channel Modelling | Panasonic |
R1-2404513 | Views on channel modelling for ISAC | Sony |
R1-2404542 | Channel modeling for integrated sensing and communication with NR | NVIDIA |
R1-2404570 | Discussion on ISAC Channel Modeling | Tiami Networks |
R1-2404633 | Summary #1 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2404634 | Summary #2 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2404635 | Summary #3 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2404636 | Summary #4 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2404637 | Summary #5 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2404652 | Discussion on ISAC channel modeling | InterDigital, Inc. |
R1-2404724 | Considerations on ISAC channel modelling | CAICT |
R1-2404876 | Study on ISAC channel modelling | OPPO |
R1-2404915 | Discussion on ISAC channel modelling | TOYOTA InfoTechnology Center |
R1-2404924 | Discussions on ISAC Channel Modeling | AT&T |
R1-2404926 | Discussion on Channel Modelling for ISAC | Lenovo |
R1-2405003 | Discussion on channel modelling for ISAC | ZTE, BJTU |
R1-2405010 | Discussion on ISAC Channel Modelling | Ericsson |
R1-2405055 | Discussion on ISAC channel modeling | NTT DOCOMO, INC. |
R1-2405095 | Discussion on ISAC channel modelling | MediaTek Inc. |
R1-2405098 | Discussion on ISAC channel model | Xiaomi, BUPT, BJTU |
R1-2405168 | Discussion on ISAC channel modelling | Qualcomm Incorporated |
R1-2405249 | Discussion on ISAC Channel Modelling | CEWiT |
R1-2405276 | Discussions on ISAC Channel Modelling | ITL |
R1-2405303 | TBC | ICS |
TDoc | Title | Source |
---|---|---|
R1-2403969 | Template for Data Source Descriptions | Intel Corporation, ZTE |
R1-2405646 | Data source descriptions for 7 – 24 GHz SI | Moderator (Intel Corporation) |
R1-2405698 | Session notes for 9.8 (Study on channel modelling enhancements for 7-24GHz for NR) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2403856 | Discussion on Channel Model Validation of TR38.901 for FR3 | InterDigital, Inc. |
R1-2403878 | Views on Channel model validation of TR38.901 for 7-24GHz | Sharp, NYU WIRELESS |
R1-2403907 | Discussion on channel model validation of TR38.901 for 7-24GHz | LG Electronics |
R1-2403925 | Considerations on the 7-24GHz channel model validation | Huawei, HiSilicon |
R1-2403962 | Discussion on channel modeling verification for 7-24 GHz | Intel Corporation |
R1-2403991 | Discussion on validation of channel model | Ericsson |
R1-2403996 | Discussion on Channel model validation of TR38.901 for 7-24GHz | Nokia, Anritsu |
R1-2404129 | Discussion on channel model validation of TR38.901 for 7 - 24 GHz | Samsung |
R1-2404191 | Views on channel model validation of TR38.901 for 7-24GHz | vivo |
R1-2404212 | Discussion on the channel model validation | ZTE |
R1-2404304 | Initial Measurement Results for Channel Model Validation | Apple |
R1-2404331 | Discussion on channel model validation of TR38.901 for 7-24GHz | BUPT, Spark NZ Ltd, vivo |
R1-2404415 | On channel model validation of TR38.901 for 7-24GHz | CATT |
R1-2404514 | Discussion on channel model validation of TR38.901 for 7-24GHz | Sony |
R1-2404521 | Discussion on validation of channel model | Vodafone, Ericsson |
R1-2404543 | Channel model validation of TR 38901 for 7-24 GHz | NVIDIA |
R1-2404925 | Discussion on Validation of the Channel Model in 38901 | AT&T |
R1-2405169 | Channel Model Validation of TR38.901 for 7-24 GHz | Qualcomm Incorporated |
R1-2405339 | Views on Channel model validation of TR38.901 for 7-24GHz | Sharp, NYU WIRELESS |
R1-2405360 | Summary of issues for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2405361 | Summary #1 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2405362 | Summary #2 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2405588 | Summary #3 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2405589 | Summary #4 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
TDoc | Title | Source |
---|---|---|
R1-2403857 | Discussion on Channel Model Extension of TR38.901 for FR3 | InterDigital, Inc. |
R1-2403908 | Discussion on channel modelling adaptation/extension for 7-24GHz | LG Electronics |
R1-2403926 | Considerations on the 7-24GHz channel model extension | Huawei, HiSilicon |
R1-2403963 | Discussion on channel model adaptation/extension | Intel Corporation |
R1-2403992 | Discussion on adaptation and extension of channel model | Ericsson |
R1-2403997 | Discussion on Channel model adaptation/extension of TR38.901 for 7-24GHz | Nokia |
R1-2404130 | Discussion on channel model adaptation/extension of TR38.901 for 7 - 24 GHz | Samsung |
R1-2404192 | Views on channel model adaptation/extension of TR38.901 for 7-24GHz | vivo |
R1-2404213 | Discussion on the channel model adaptation and extension | ZTE |
R1-2404305 | Channel Model Adaptation and Extension of TR38.901 for 7-24 GHz | Apple |
R1-2404330 | Discussion on modeling near-field propagation and spatial non-stationarity in TR38.901 for 7-24GHz | BUPT, CMCC, vivo |
R1-2404340 | Discussion of FR3 channel model | Lenovo |
R1-2404416 | On channel model adaptation/extension of TR38.901 for 7-24GHz | CATT |
R1-2404437 | Discussion on channel modeling for single road bridge (SRB) scenario | China Telecom, BJTU |
R1-2404544 | Channel model adaptation of TR 38901 for 7-24 GHz | NVIDIA |
R1-2405082 | Discussion on channel modelling enhancements for 7-24GHz for NR | MediaTek Inc. |
R1-2405170 | Channel Model Adaptation/Extension of TR38.901 for 7-24GHz | Qualcomm Incorporated |
R1-2405250 | Channel model adaptation/extension of TR38.901 for 7-24 GHz | CEWiT |
R1-2405443 | Summary#1 of channel model adaptation and extension | Moderator (ZTE) |
R1-2405444 | Summary#2 of channel model adaptation and extension | Moderator (ZTE) |
R1-2405545 | Summary#3 of channel model adaptation and extension | Moderator (ZTE) |
R1-2405546 | Summary#4 of channel model adaptation and extension | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R1-2403951 | Discussions on scheduling enhancements considering RRM measurements for XR | Huawei, HiSilicon |
R1-2404040 | Discussion on enabling TX/RX for XR during RRM measurements | Spreadtrum Communications |
R1-2404045 | Enhancements to enable TX/RX for XR during RRM measurements | Fraunhofer IIS, Fraunhofer HHI |
R1-2404131 | Discussion on enabling TX/RX for XR during RRM measurements | Samsung |
R1-2404193 | Discussion on enabling data transmissions for XR during RRM measurements | vivo |
R1-2404306 | Enabling TX/RX for XR during RRM measurements | Apple |
R1-2404335 | Discussion on enabling TX/RX for XR during RRM measurements | InterDigital, Inc. |
R1-2404346 | Discussion on Enabling TX/RX for XR During RRM Measurements | Meta |
R1-2404389 | Signaling control of scheduling restriction during measurement gap in support of XR services | CATT |
R1-2404470 | Discussion on enabling TX/RX for XR during RRM measurements | CMCC |
R1-2404515 | Enhancements to Support TX/RX During RRM Measurements | Sony |
R1-2404524 | RRM measurement gap and scheduling restriction enhancements to TX/RX XR traffic | Ericsson |
R1-2404531 | Enabling TX/RX for XR during RRM measurements | Lenovo |
R1-2404566 | Discussion on measurement gap for XR | ZTE, Sanechips |
R1-2404606 | Discussion on enabling TX/RX for XR during RRM measurements | Xiaomi |
R1-2404667 | Discussion on enabling TX/RX for XR during RRM measurements | NEC |
R1-2404735 | Enabling TX/RX for XR during RRM measurements | TCL |
R1-2404738 | Discussion on enabling TX/RX for XR during RRM measurements | Panasonic |
R1-2404874 | Enhancements to enable TX/RX for XR during RRM measurements | OPPO |
R1-2404900 | Discussion on XR during RRM measurements | LG Electronics |
R1-2404932 | On enabling Tx/Rx for XR during RRM measurements | Google Inc. |
R1-2405012 | Discussion on enabling TX/RX for XR during RRM measurements | III |
R1-2405056 | Discussion on Enaling TX/RX for XR during RRM | NTT DOCOMO, INC. |
R1-2405083 | Enabling TX RX for XR during RRM measurements | MediaTek Inc. |
R1-2405171 | Enabling Tx/Rx for XR during RRM measurements | Qualcomm Incorporated |
R1-2405176 | Enabling TX/RX for XR during RRM measurements | Nokia |
R1-2405464 | Moderator summary #1 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2405465 | Moderator summary #2 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2405665 | Moderator summary #3 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2405666 | Moderator summary #4 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2405667 | Draft LS on UE assistance information related to measurement occasions | Nokia |
R1-2405736 | LS on UE assistance information | RAN1, Nokia |
TDoc | Title | Source |
---|---|---|
R1-2404205 | Work plan for Rel-19 NR_NTN_Ph3 | THALES |
R1-2405699 | Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2403938 | Discussion on downlink coverage enhancements for NR NTN | Huawei, HiSilicon |
R1-2403989 | On NR-NTN downlink coverage enhancement | Ericsson |
R1-2403993 | Further considerations on FR2-NTN analysis assumptions | Eutelsat Group |
R1-2404003 | Discussion on downlink coverage enhancements for NR NTN | Fraunhofer IIS, Fraunhofer HHI |
R1-2404041 | Discussion on NR-NTN downlink coverage enhancement | Spreadtrum Communications |
R1-2404132 | Discussion on downlink coverage enhancement for NR-NTN | Samsung |
R1-2404194 | Discussion on NR-NTN downlink coverage enhancement | vivo |
R1-2404201 | Discussion on NR NTN Downlink coverage enhancements | THALES |
R1-2404202 | FL Summary #1: NR-NTN downlink coverage enhancements | THALES |
R1-2404203 | FL Summary #2: NR-NTN downlink coverage enhancements | THALES |
R1-2404204 | FL Summary #3: NR-NTN downlink coverage enhancements | THALES |
R1-2404214 | Discussion on DL coverage enhancement for NR NTN | ZTE |
R1-2404261 | NR-NTN downlink coverage enhancement | InterDigital, Inc. |
R1-2404307 | Discussion on NR-NTN Downlink Coverage Enhancement | Apple |
R1-2404323 | Discussion on NR-NTN downlink coverage enhancement | LG Electronics |
R1-2404390 | Performance evaluation of downlink coverage enhancement for NR NTN | CATT |
R1-2404441 | Discussion on downlink coverage enhancement for NR NTN | Lenovo |
R1-2404471 | Discussion on NR-NTN DL coverage enhancement | CMCC |
R1-2404607 | Discussion on NR-NTN downlink coverage enhancement | Xiaomi |
R1-2404670 | NR-NTN downlink coverage enhancement | NEC |
R1-2404692 | Downlink Coverage Enhancement for NR NTN | |
R1-2404694 | Beam group for NR-NTN downlink coverage enhancement | Sharp |
R1-2404784 | Discussion on NR-NTN downlink coverage enhancement | ETRI |
R1-2404789 | Discussion on downlink coverage enhancement for NR NTN | Baicells |
R1-2404861 | Discussion on NR-NTN downlink coverage enhancement | OPPO |
R1-2404916 | Discussion on NR NTN Downlink Coverage Enhancements | IIT Kharagpur, CEWIT |
R1-2405057 | Discussion on DL coverage enhancement for NR-NTN | NTT DOCOMO, INC. |
R1-2405090 | Discussion on NR-NTN downlink coverage enhancement | MediaTek Inc. |
R1-2405117 | NR-NTN Downlink Coverage Enhancement | Panasonic |
R1-2405172 | Downlink coverage enhancement for NR NTN | Qualcomm Incorporated |
R1-2405226 | Discussion on DL coverage enhancements for NR-NTN | NICT |
R1-2405251 | Downlink Coverage Enhancements for NR NTN | CEWiT |
R1-2405257 | Discussion on downlink coverage enhancement for NR-NTN | CSCN |
R1-2405263 | Downlink coverage enhancements for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2405342 | Discussion on NR NTN Downlink coverage enhancements | THALES, Magister |
R1-2405421 | Discussion on downlink coverage enhancements for NR NTN | Huawei, HiSilicon |
R1-2405730 | FL Summary #4: NR-NTN downlink coverage enhancements | Moderator (THALES) |
TDoc | Title | Source |
---|---|---|
R1-2403939 | Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN | Huawei, HiSilicon |
R1-2404042 | Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Spreadtrum Communications |
R1-2404133 | Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Samsung |
R1-2404195 | Discussion on support of RedCap and eRedCap UEs with NR-NTN | vivo |
R1-2404215 | Discussion on support of RedCap/eRedCap UEs for NR NTN | ZTE |
R1-2404262 | Discussion on half-duplex RedCap issues for NTN FR1 operation | InterDigital, Inc. |
R1-2404308 | Discussion on support of RedCap UEs with NR NTN operation | Apple |
R1-2404324 | Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands | LG Electronics |
R1-2404391 | Discussion on the operation of RedCap and eRedCap UEs In NTN | CATT |
R1-2404438 | Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | China Telecom |
R1-2404472 | Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN | CMCC |
R1-2404533 | On HD-FDD Redcap UEs for NTN | Ericsson |
R1-2404580 | Discussion on support of RedCap/eRedCap UEs in NR NTN | HONOR |
R1-2404608 | Discussion on the support of Redcap UE for NTN operating on FR1 bands | Xiaomi |
R1-2404725 | Discussion on support of RedCap/eRedCap UEs in NTN | CAICT |
R1-2404736 | Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN | TCL |
R1-2404785 | Discussion on HD UEs with NR NTN | ETRI |
R1-2404862 | Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | OPPO |
R1-2405058 | Discussion on support of RedCap and eRedCap UEs in FR1-NTN | NTT DOCOMO, INC. |
R1-2405091 | Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | MediaTek Inc. |
R1-2405173 | Support of Redcap and eRedcap UEs in NR NTN | Qualcomm Incorporated |
R1-2405264 | Considerations on (e)RedCap operation in NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2405516 | Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
R1-2405517 | Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
R1-2405741 | Summary #3 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2403940 | Discussion on uplink capacity/throughput enhancement for FR1-NTN | Huawei, HiSilicon |
R1-2404043 | Discussion on NR-NTN uplink capacity/throughput enhancement | Spreadtrum Communications |
R1-2404134 | Discussion on uplink capacity/throughput enhancement for NR-NTN | Samsung |
R1-2404196 | Discussion on NR-NTN uplink capacity enhancement | vivo |
R1-2404216 | Discussion on UL capacity enhancement for NR NTN | ZTE |
R1-2404263 | NR-NTN uplink capacity/throughput enhancement | InterDigital, Inc. |
R1-2404309 | Discussion on NR-NTN Uplink Capacity Enhancement | Apple |
R1-2404315 | Views on NR-NTN PUSCH capacity enhancement | Mitsubishi Electric RCE |
R1-2404319 | NTN NR uplink capacity enhancement | Sharp |
R1-2404325 | Discussion on NR-NTN uplink capacity/throughput enhancement | LG Electronics |
R1-2404392 | Discussion on UL capacity enhancement for NR NTN | CATT |
R1-2404418 | On uplink capacity/throughput enhancement for NR NTN | Ericsson |
R1-2404439 | Discussion on NR-NTN uplink enhancement | China Telecom |
R1-2404473 | Discussion on the NR-NTN uplink capacity/throughput enhancements | CMCC |
R1-2404609 | Discussion on NR-NTN PUSCH capacity enhancement | Xiaomi |
R1-2404671 | NR-NTN uplink capacity/throughput enhancement | NEC |
R1-2404693 | Uplink Capacity Enhancement for NR NTN | |
R1-2404786 | Discussion on NR-NTN uplink capacity/throughput enhancement | ETRI |
R1-2404801 | Discussion on uplink capacity/throughput enhancement for NR-NTN | Lenovo |
R1-2404806 | Discussion on uplink capacity/throughput enhancement for FR1-NTN | Fujitsu |
R1-2404863 | Discussion on NR-NTN uplink capacity/throughput enhancement | OPPO |
R1-2404976 | Discussion on the NR-NTN uplink capacity/throughput enhancements | TCL |
R1-2405011 | Uplink capacity/throughput enhancement for NR-NTN | Panasonic |
R1-2405059 | Discussion on NR-NTN uplink capacity/throughput enhancement | NTT DOCOMO, INC. |
R1-2405092 | Discussion on NR-NTN uplink capacity and throughput | MediaTek Inc. |
R1-2405174 | NR-NTN uplink capacity / throughput enhancement | Qualcomm Incorporated |
R1-2405227 | Discussion on NR-NTN uplink capacity/throughput enhancement | NICT |
R1-2405265 | Uplink capacity enhancement considerations for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2405506 | Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput | Moderator (MediaTek) |
R1-2405507 | Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput | Moderator (MediaTek) |
R1-2405550 | Discussion on uplink capacity/throughput enhancement for FR1-NTN | Huawei, HiSilicon |
R1-2405593 | Feature lead summary #3 of AI 9.11.3 on NR-NTN uplink capacity and throughput | Moderator (MediaTek) |
R1-2405648 | Feature lead summary #4 of AI 9.11.3 on NR-NTN uplink capacity and throughput | Moderator (MediaTek) |
R1-2405685 | Feature lead summary #5 of AI 9.11.3 on NR-NTN uplink capacity and throughput | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2403941 | Discussion on UL capacity enhancements for IoT NTN | Huawei, HiSilicon |
R1-2404044 | Discussion on IoT-NTN uplink capacity/throughput enhancement | Spreadtrum Communications |
R1-2404135 | Discussion on uplink capacity/throughput enhancement for IoT-NTN | Samsung |
R1-2404197 | Discussion on IoT-NTN uplink capacity enhancement | vivo |
R1-2404217 | Discussion on UL capacity enhancement for IoT NTN | ZTE |
R1-2404264 | IoT-NTN uplink capacity/throughput enhancement | InterDigital, Inc. |
R1-2404310 | Discussion on IoT-NTN Uplink Capacity Enhancement | Apple |
R1-2404326 | Discussion on IoT-NTN uplink capacity/throughput enhancement | LG Electronics |
R1-2404393 | Discussion on UL capacity enhancement for IoT NTN | CATT |
R1-2404442 | Discussion on uplink capacity enhancement for IoT NTN | Lenovo |
R1-2404474 | Discussion on the IoT -NTN uplink capacity/throughput enhancements | CMCC |
R1-2404534 | On uplink capacity enhancements for IoT-NTN | Ericsson |
R1-2404610 | Discussion on IoT-NTN uplink capacity enhancement | Xiaomi |
R1-2404672 | IoT-NTN uplink capacity/throughput enhancement | NEC |
R1-2404695 | IoT NTN OCC multiplexing methods for NPUSCH and NPRACH | Sharp |
R1-2404742 | IoT-NTN uplink capacity enhancement | Nokia, Nokia Shanghai Bell |
R1-2404787 | Discussion on uplink capacity/throughput enhancement for IoT NTN | ETRI |
R1-2404864 | Discussion on IoT-NTN uplink capacity/throughput enhancement | OPPO |
R1-2405093 | Discussion on IoT-NTN uplink capacity and throughput | MediaTek Inc. |
R1-2405175 | IOT-NTN uplink capacity/throughput enhancement | Qualcomm Incorporated |
R1-2405178 | Discussion on the IoT-NTN uplink capacity/throughput enhancements | TCL |
R1-2405493 | FL Summary #1 for IoT-NTN | Moderator (Sony) |
R1-2405494 | FL Summary #2 for IoT-NTN | Moderator (Sony) |