TDoc | Title | Source |
---|---|---|
R1-2304300 | Draft Agenda of RAN1#113 meeting | RAN1 Chair |
R1-2304302 | RAN1#113 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
R1-2304303 | RAN1#113 Meeting Management | RAN1 Chair |
TDoc | Title | Source |
---|---|---|
R1-2304301 | Report of RAN1#112bis-e meeting | ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2304304 | Reply LS on 3GPP work on Energy Efficiency | CT1, Huawei |
R1-2304305 | LS out on the N6 PDU Set Identification | SA4, Intel |
R1-2304306 | Reply LS to LS to SA2 on Sidelink positioning procedure | SA2, xiaomi |
R1-2304307 | Reply LS on 1-symbol PRS | RAN3, ZTE |
R1-2304308 | Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM | RAN3, Fujitsu, CATT |
R1-2304309 | LS on the system parameters for NTN above 10 GHz | RAN4, CATT |
R1-2304310 | Reply LS on interference modelling for duplex evolution | RAN4, Samsung |
R1-2304311 | LS on RS supported for group-based reporting | RAN4, Ericsson |
R1-2304312 | LS to RAN1 on low-power wake-up receiver architectures | RAN4, vivo |
R1-2304313 | LS on Rel-18 Tx switching across 3/4 bands | RAN4, China Telecom |
R1-2304314 | Reply LS on Rel-16 UL Tx switching period | RAN4, vivo |
R1-2304315 | Reply LS on configured Tx power for STxMP in FR2 | RAN4, Qualcomm Incorporated |
R1-2304316 | LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | RAN4, Ericsson |
R1-2304317 | LS on updated Rel-17 RAN4 feature list for NR | RAN4, CMCC |
R1-2304318 | LS on FR2 unknown SCell activation enhancement | RAN4, Apple |
R1-2304319 | Reply LS on Comparison of SL-RSRP and SDRSRP measurements | RAN4, Nokia |
R1-2304320 | LS on MAC-CE Based Indication for Cross-RRH TCI State Switch | RAN4, Nokia |
R1-2304321 | LS response on SL LBT failure indication and SL consistent LBT failure granularity | RAN2, vivo |
R1-2304322 | LS on RACH-less Handover | RAN2, Samsung |
R1-2304323 | LS on unchanged PCI | RAN2, CATT |
R1-2304324 | LS on HARQ Enhancements | RAN2, OPPO |
R1-2304325 | LS to RAN1 on multicast reception in RRC_INACTIVE | RAN2, Apple |
R1-2304326 | LS on 2TA for multi-DCI multi-TRP | RAN2, Ericsson |
R1-2304327 | LS on RRC configuration of Tx state in Rel-18 UL Tx switching | RAN2, NTT DOCOMO |
R1-2304328 | Reply LS on 1-symbol PRS | RAN2, ZTE |
R1-2304329 | LS on unified TCI-state and fast Scell activation | RAN2, xiaomi, ZTE |
R1-2304330 | Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM | RAN2, Fujitsu, CATT |
R1-2304331 | LS on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs | RAN2, Ericsson |
R1-2304332 | LS on the RAT-dependent positioning integrity | RAN2, OPPO |
R1-2304333 | LS on report of switching periods in Rel-18 UL Tx switching | RAN2, NTT DOCOMO |
R1-2304334 | LS on Cell DTX/DRX activation/deactivation | RAN2, Huawei |
R1-2304335 | Reply LS to SA2 on Low Power High Accuracy Positioning | RAN2, Huawei |
R1-2304402 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | ZTE |
R1-2304403 | Discussion on RAN2 LS on 2TA for multi-DCI multi-TRP | ZTE |
R1-2304404 | Draft reply LS to RAN4 on RS supported for group-based reporting | ZTE |
R1-2304405 | Draft reply LS to RAN2 on unified TCI-state and fast SCell activation | ZTE |
R1-2304444 | Reply LS on NR support for dedicated spectrum less than 5MHz for FR1 | vivo |
R1-2304445 | Draft reply LS on 1-symbol PRS | vivo |
R1-2304446 | Draft reply LS on the RAT-dependent positioning integrity | vivo |
R1-2304447 | Draft reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | vivo |
R1-2304448 | Draft reply LS to SA on Sidelink positioning procedure | vivo |
R1-2304449 | Discussion on RAN2 LS on unchanged PCI | vivo |
R1-2304450 | Discussion on RAN2 LS on RACH-less Handover | vivo |
R1-2304451 | Draft reply LS on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs | vivo |
R1-2304452 | Draft reply LS on Cell DTX/DRX activation/deactivation | vivo |
R1-2304453 | Draft reply LS to RAN4 on low-power wake-up receiver architectures | vivo |
R1-2304454 | Draft LS reply on report of switching periods in Rel-18 UL Tx switching | vivo |
R1-2304455 | Discussion on report of switching periods in Rel-18 UL Tx switching | vivo |
R1-2304456 | Draft LS reply on Rel-18 Tx switching across 3/4 bands | vivo |
R1-2304457 | Discussion on Rel-18 Tx switching across 3/4 bands | vivo |
R1-2304458 | Discussion on RAN2 LS on multicast reception in RRC_INACTIVE | vivo |
R1-2304459 | Draft reply LS to RAN2 on multicast reception in RRC_INACTIVE | vivo |
R1-2304460 | Draft reply LS on RS supported for group-based reporting | vivo |
R1-2304461 | Draft reply LS on unified TCI-state and fast SCell activation | vivo |
R1-2304462 | Draft reply LS on 2TA for multi-DCI multi-TRP | vivo |
R1-2304523 | Discussion on reply LS on paging overlapping with CG-SDT for HD-FDD RedCap UE | ZTE, Sanechips |
R1-2304524 | Discussion on Cell DTX/DRX activation/deactivation | ZTE, Sanechips |
R1-2304525 | Draft reply LS on low-power wake-up receiver architectures | ZTE, Sanechips |
R1-2304540 | Response LS on PRU Procedures | RAN2,Qualcomm |
R1-2304541 | Discussion on LS on 2TA for multi-DCI multi-TRP | Spreadtrum Communications |
R1-2304589 | Discussion on RAN4 LS on dedicated spectrum less than 5 MHz | ZTE |
R1-2304590 | [Draft] Reply LS to RAN4 on dedicated spectrum less than 5MHz | ZTE |
R1-2304591 | [Draft] Reply LS on Rel-18 Tx switching across 3/4 bands | ZTE |
R1-2304592 | [Draft] Reply LS on RRC configuration of Tx state in Rel-18 UL Tx switching | ZTE |
R1-2304593 | [Draft] Reply LS on report of switching periods in Rel-18 UL Tx switching | ZTE |
R1-2304594 | [Draft] Reply LS on multicast reception in RRC_INACTIVE | ZTE |
R1-2304643 | Discussion on the UE SRS IL imbalance issue | Huawei, HiSilicon |
R1-2304673 | Discussion on multicast reception in RRC_INACTIVE | Huawei, HiSilicon |
R1-2304674 | Discussion on RAN4 LS for dedicated spectrum less than 5 MHz for FR1 | Huawei, HiSilicon |
R1-2304689 | Discussion on RAN4 LS on Rel-18 Tx switching across 3/4 bands | CATT |
R1-2304690 | Discussion on RAN2 LS on RRC configuration of Tx state in Rel-18 UL Tx switching | CATT |
R1-2304691 | Discussion on RAN2 LS on report of switching periods in Rel-18 UL Tx switching | CATT |
R1-2304692 | Discussion on Sidelink positioning procedure | CATT |
R1-2304693 | Draft reply LS on Sidelink positioning procedure | CATT |
R1-2304694 | Discussion on 1-symbol PRS | CATT |
R1-2304695 | Draft reply LS on 1-symbol PRS | CATT |
R1-2304696 | Discussion on the RAT-dependent positioning integrity | CATT |
R1-2304697 | Draft reply LS on the RAT-dependent positioning integrity | CATT |
R1-2304698 | Discussion on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | CATT |
R1-2304699 | Draft reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | CATT |
R1-2304700 | Draft reply LS on RS supported for group-based reporting | CATT |
R1-2304701 | Discussion on RAN4 Reply LS on LP-WUR architecture | CATT |
R1-2304702 | Discussion on RAN2 LS on L1 signaling for cell DTX/DRX activation/deactivation | CATT |
R1-2304703 | Draft reply LS on 2TA for multi-DCI multi-TRP | CATT |
R1-2304704 | Draft reply LS on unified TCI-state and fast Scell activation | CATT |
R1-2304756 | Discussion on RAN2 LS reply on unchanged PCI | CATT |
R1-2304757 | Draft reply LS to RAN2 on unchanged PCI | CATT |
R1-2304794 | On LS on Monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs | Ericsson |
R1-2304850 | Draft reply LS to RAN2 on HARQ Enhancements | Lenovo |
R1-2304853 | [Draft] Reply LS on Rel-18 Multi-carrier enhancement | China Telecom |
R1-2304871 | Draft reply LS on unified TCI-state and fast SCell activation | xiaomi |
R1-2304872 | [Draft] Reply to LS on Rel-18 Tx switching | xiaomi |
R1-2304922 | Draft Reply LS on RAT-dependent positioning integrity | ZTE |
R1-2304923 | Discussion on RAT-dependent positioning integrity | ZTE |
R1-2304924 | Draft Reply LS on Sidelink positioning procedure | ZTE |
R1-2304925 | Draft Reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | ZTE |
R1-2304926 | Draft Reply LS to RAN2 on 1-symbol PRS | ZTE |
R1-2304938 | Collision handling between paging occasions and CG-SDT occasions for HD-FDD UEs | Beijing Xiaomi Software Tech |
R1-2304959 | [Draft] Reply LS on 2TA for multi-DCI multi-TRP | Lenovo |
R1-2304960 | [Draft] Reply LS on unified TCI-state and fast SCell activation | Lenovo |
R1-2304961 | Draft reply LS on Rel-18 Tx switching across 3/4 bands | Spreadtrum Communications |
R1-2304962 | Draft reply LS on unified TCI-state and fast Scell activation | Spreadtrum Communications |
R1-2304969 | Draft reply LS on paging and CG-SDT conflicting issue for HD-FDD RedCap UE | ZTE, Sanechips |
R1-2305025 | Draft Reply LS on Sidelink positioning procedure | xiaomi |
R1-2305027 | DRAFT Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 | Nokia, Nokia Shanghai Bell |
R1-2305075 | Discussion on RAN2 LS on unchanged PCI | CMCC |
R1-2305076 | Discussion on LS on multicast reception in RRC_INACTIVE | CMCC |
R1-2305121 | Discussion for LS reply on the RAT-dependent positioning integrity | InterDigital, Inc. |
R1-2305122 | Draft LS reply on the RAT-dependent positioning integrity | InterDigital, Inc. |
R1-2305140 | Discussion on reply LS to RAN4 on UL Tx switching across 3 or 4 bands in Rel-18 | LG Electronics |
R1-2305141 | Discussion on RAN4 LS for LP-WUR architectures | LG Electronics |
R1-2305193 | Discussion on RAN4 LS on Rel-18 Tx switching across 3/4 bands | MediaTek Inc. |
R1-2305215 | Draft reply LS to RAN2 on multicast reception in RRC_INACTIVE | Apple |
R1-2305216 | Discussion on multicast reception in RRC_INACTIVE | Apple |
R1-2305217 | Draft reply LS on report of switching periods in Rel-18 UL Tx switching | Apple |
R1-2305218 | Draft reply LS on Rel-18 Tx switching across 3/4 bands | Apple |
R1-2305219 | Draft reply LS on RS supported for group-based reporting | Apple |
R1-2305220 | Draft reply LS on 2TA for multi-DCI multi-TRP | Apple |
R1-2305221 | Draft reply LS on unified TCI-state and fast Scell activation | Apple |
R1-2305222 | Draft Reply LS on RACH-less Handover | Apple |
R1-2305223 | Discussion on RAN2 LS on RACH-less Handover | Apple |
R1-2305224 | Draft Reply LS on HARQ Enhancements | Apple |
R1-2305225 | Discussion on RAN2 LS on HARQ Enhancements | Apple |
R1-2305304 | Draft reply LS on RS supported for group-based reporting | LG Electronics |
R1-2305305 | Draft reply LS on 2TA for multi-DCI multi-TRP | LG Electronics |
R1-2305310 | Draft reply LS to RAN2 on 2TA for multi-DCI multi-TRP | Qualcomm Incorporated |
R1-2305311 | Discussion on RAN4 LS of Rel-18 UL Tx switching timeline | Qualcomm Incorporated |
R1-2305312 | Discussion on RAN2 LS on switching periods in Rel-18 | Qualcomm Incorporated |
R1-2305313 | Draft reply LS to RAN2 on RACH-less handover | Qualcomm Incorporated |
R1-2305314 | Draft reply LS to RAN2 on multicast reception in RRC_INACTIVE | Qualcomm Incorporated |
R1-2305315 | Draft Reply to RAN4 LS on NR support for dedicated spectrum less than 5 MHz for FR1 | Qualcomm Incorporated |
R1-2305316 | Discussion on NTN IOT HARQ enhancements | Qualcomm Incorporated |
R1-2305317 | Draft Reply to the LS on 1-symbol PRS | Qualcomm Incorporated |
R1-2305399 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | Nokia, Nokia Shanghai Bell |
R1-2305400 | Discussion on questions of HARQ enhancement in IoT NTN from RAN2 LS | Nokia, Nokia Shanghai Bell |
R1-2305410 | Discussion on SRS insertion loss issue | OPPO |
R1-2305411 | Discussion on LS on unified TCI-state and fast SCell activation | OPPO |
R1-2305412 | Discussion on LS on 2TA operation for Rel-18 MIMO | OPPO |
R1-2305417 | Discussion on LS on the RAT-dependent positioning integrity | OPPO |
R1-2305425 | Discussion on the LS from SA2 on Sidelink positioning procedure | OPPO |
R1-2305426 | Draft reply LS to SA2 on Sidelink positioning procedure | OPPO |
R1-2305430 | Discussion on the LS from RAN2 on multicast reception in RRC_INACTIVE | OPPO |
R1-2305431 | Draft reply LS to RAN2 on multicast reception in RRC_INACTIVE | OPPO |
R1-2305434 | Discussion RAN2 LS on Cell DTX/DRX activation/deactivation | OPPO |
R1-2305435 | Draft reply LS on Cell DTX/DRX activation/deactivation | OPPO |
R1-2305440 | Discussion RAN2 LS on unchanged PCI | OPPO |
R1-2305441 | Draft reply LS on unchanged PCI | OPPO |
R1-2305442 | Discussion RAN2 LS on RACH-less Handover | OPPO |
R1-2305443 | Draft reply LS on RACH-less Handover | OPPO |
R1-2305444 | Discussion RAN2 LS on HARQ Enhancements | OPPO |
R1-2305445 | Draft reply LS on HARQ Enhancements | OPPO |
R1-2305456 | Dsicussion on LS reply of WUS bandwidth | OPPO |
R1-2305473 | Discussion on RAN4 LS for Rel-18 Tx switching | OPPO |
R1-2305474 | Discussion on RAN2 LS for using 1-symbol PRS in PDC | OPPO |
R1-2305486 | Draft reply LS on 2TA for multi-DCI multi-TRP | Samsung |
R1-2305487 | Draft reply LS on unified TCI-state and fast Scell activation | Samsung |
R1-2305488 | Draft reply LS on RS supported for group-based reporting | Samsung |
R1-2305489 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | Samsung |
R1-2305490 | Draft reply LS on the RAT-dependent positioning integrity | Samsung |
R1-2305491 | Discussion on the RAT-dependent positioning integrity | Samsung |
R1-2305492 | Draft reply LS on RACH-less Handover | Samsung |
R1-2305493 | Discussion on RAN2 and RAN4 LS on Rel-18 UL Tx switching | Samsung |
R1-2305563 | Discussion on LS on HARQ Enhancements | ZTE |
R1-2305564 | Draft Reply LS on the HARQ enhancement | ZTE |
R1-2305565 | Discussion on LS on the unchanged PCI | ZTE |
R1-2305566 | Discussion on LS on RACH-less | ZTE |
R1-2305571 | Discussion on RAN2 LS on Cell DTX/DRX activation/deactivation | Ericsson |
R1-2305572 | Discussion on RAN4 LS on low-power wake-up receiver architectures | Ericsson |
R1-2305580 | Discussion on LSs from RAN2/4 on Rel-18 UL Tx switching | NTT DOCOMO, INC. |
R1-2305581 | Discussion on reply LS to RAN4 on group-based reporting | NTT DOCOMO, INC. |
R1-2305582 | [draft] Reply LS on 1-symbol PRS | NTT DOCOMO, INC. |
R1-2305646 | Evaluation of SRS antenna switching with insertion loss | MediaTek Inc. |
R1-2305679 | Discussion on multicast reception in RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
R1-2305680 | Draft reply LS to RAN2 on multicast reception in RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
R1-2305746 | Draft reply LS to RAN4 on RS supported for group-based reporting | Nokia, Nokia Shanghai Bell |
R1-2305747 | Draft Reply LS on 2TA for multi-DCI multi-TRP | Nokia, Nokia Shanghai Bell |
R1-2305755 | Discussion on RAN4 LS on RS supported for group-based reporting | Ericsson |
R1-2305756 | Draft reply LS on 2TA for multi-DCI multi-TRP | Ericsson |
R1-2305811 | Discussion on RAN2 LS on multicast reception in RRC INACTIVE | MediaTek Inc. |
R1-2305821 | discussion on LS to RAN1 on multicast reception in RRC_INACTIVE | Ericsson |
R1-2305822 | Draft reply LS on multicast reception in RRC_INACTIVE | Ericsson |
R1-2305823 | Discussion on LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | Ericsson |
R1-2305824 | Draft LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | Ericsson |
R1-2305825 | Discussion on Reply LS on 1-symbol PRS | Ericsson |
R1-2305826 | Draft LS reply on 1-symbol PRS | Ericsson |
R1-2305827 | Discussion on LS on the RAT-dependent positioning integrity | Ericsson |
R1-2305828 | Draft reply LS on the RAT-dependent positioning integrity | Ericsson |
R1-2305838 | Discussion the UE SRS IL imbalance issue | vivo |
R1-2305852 | Discussion on the LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | MediaTek (Chengdu) Inc. |
R1-2305860 | TEI18: On 1-symbol PRS applicability to PDC | Nokia, Nokia Shanghai Bell |
R1-2305861 | Reply LS on Rel-18 Tx switching across 3/4 bands | Nokia, Nokia Shanghai Bell |
R1-2305862 | Reply LS on report of switching periods in Rel-18 UL Tx switching | Nokia, Nokia Shanghai Bell |
R1-2305866 | [Draft] Reply LS on Rel-18 Tx switching across 3/4 bands | Ericsson |
R1-2305875 | Discussion on LS to RAN1 on multicast reception in RRC_INACTIVE | Ericsson |
R1-2305876 | Draft reply LS on multicast reception in RRC_INACTIVE | Ericsson |
R1-2305877 | Discussion on LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | Ericsson |
R1-2305878 | Draft LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | Ericsson |
R1-2305879 | Discussion on Reply LS on 1-symbol PRS | Ericsson |
R1-2305880 | Draft LS reply on 1-symbol PRS | Ericsson |
R1-2305881 | Discussion on LS on the RAT-dependent positioning integrity | Ericsson |
R1-2305882 | Draft reply LS on the RAT-dependent positioning integrity | Ericsson |
R1-2305890 | Discussion on reply LS to LS to SA2 on Sidelink positioning procedure | Ericsson |
R1-2305891 | Draft Reply LS to SA2 on Sidelink positioning procedure | Ericsson |
R1-2305911 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | Ericsson |
R1-2305912 | Draft reply LS on RAN4 LS on the UE SRS IL imbalance issue | Ericsson |
R1-2305915 | [Draft] Reply to RAN2 LS on HARQ Enhancements | Nordic Semiconductor ASA |
R1-2305920 | [Draft] Reply LS on RACH-less handover | Ericsson |
R1-2305921 | Discussion on RAN2 LS on RACH-less handover | Ericsson |
R1-2305923 | Discussion of RAN4 LS on LP-WUR architecture | Huawei, HiSilicon |
R1-2305924 | Discussion on LS on unchanged PCI | Huawei, HiSilicon |
R1-2305925 | Discussion on LS on RACH-less handover | Huawei, HiSilicon |
R1-2305926 | Discussion on RAN2 LS on cell DTX/DRX activation/deactivation | Huawei, HiSilicon |
R1-2305930 | Discussion on RRC configuration of Tx state in Rel-18 UL Tx switching | Huawei, HiSilicon |
R1-2305931 | Discussion on UL Tx switching across 3 or 4 bands in Rel-18 | Huawei, HiSilicon |
R1-2305933 | Discussion on RAT-dependent positioning integrity | Huawei, HiSilicon |
R1-2305934 | Discussion on 1-symbol PRS | Huawei, HiSilicon |
R1-2305935 | Discussion on switching time for RedCap UE positioning | Huawei, HiSilicon |
R1-2305936 | Draft reply LS on cell DTX/DRX activation/deactivation | Huawei, HiSilicon |
R1-2305937 | Draft reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 | Huawei, HiSilicon |
R1-2305938 | Discussion on the LS of HARQ enhancement for IoT NTN | Huawei, HiSilicon |
R1-2305939 | Discussion on SL positioning procedures | Huawei, HiSilicon |
R1-2305940 | Discussion on RS LS on supported for group-based reporting | Huawei, HiSilicon |
R1-2305941 | Discussion on LS on 2TA for multi-DCI multi-TRP | Huawei, HiSilicon |
R1-2305942 | Discussion on LS on unified TCI-state and fast Scell activation | Huawei, HiSilicon |
R1-2305943 | Discussion on Monitoring of paging occasions for CG-SDT with HD-FDD Redcap Ues | Huawei, HiSilicon |
R1-2305944 | Discussion on report of switching periods in Rel-18 UL Tx switching | Huawei, HiSilicon |
R1-2305946 | Draft reply LS on RACH-less handover | Huawei, HiSilicon |
R1-2305947 | Draft reply LS on the UE SRS IL imbalance issue | Huawei, HiSilicon |
R1-2305948 | Draft reply LS on the UE SRS IL imbalance issue | Qualcomm |
R1-2306121 | Summary#1 of discussion on RAN2 LS in R1-2304327 | Moderator (NTT DOCOMO, INC.) |
R1-2306135 | Draft reply LS on RS supported for group-based reporting | Moderator (Ericsson) |
R1-2306139 | Summary on reply LS on unified TCI-state and fast SCell activation | Moderator (ZTE) |
R1-2306174 | LS on C-LBT Failure Recovery | RAN2, InterDigital |
R1-2306175 | [Draft] Reply LS on Rel-18 Multi-carrier enhancement for NR | Moderator (China Telecom) |
R1-2306176 | FL summary of discussion on reply LS for Rel-18 Tx switching | Moderator (China Telecom) |
R1-2306177 | Draft reply LS on multicast reception in RRC_INACTIVE | Moderator (Apple) |
R1-2306178 | FL summary on multicast reception in RRC_INACTIVE | Moderator (Apple) |
R1-2306196 | [Draft] Reply LS on RRC configuration of Tx state in Rel-18 UL Tx switching | Moderator (NTT DOCOMO) |
R1-2306197 | Reply LS to RAN2 on unified TCI-state and fast SCell activation | RAN1, ZTE |
R1-2306198 | Reply LS on PSFCH and S-SSB transmissions over non-contiguous RB sets | RAN4, OPPO, Huawei |
R1-2306200 | FL Summary on SRS IL imbalance issue | Moderator (Huawei) |
R1-2306211 | Reply LS on Rel-18 Multi-carrier enhancement for NR | RAN1, China Telecom |
R1-2306230 | Draft reply LS on RS supported for group-based reporting | Moderator (Ericsson) |
R1-2306243 | Reply LS on multicast reception in RRC_INACTIVE | RAN1, Apple |
R1-2306257 | Reply LS on RS supported for group-based reporting | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2306267 | Summary of Email discussion on LS for Rel-18 higher layer parameters | Moderator (Ericsson) |
R1-2306268 | Collection of higher layers parameter list for Rel-18 | Moderator (Ericsson) |
R1-2306269 | DRAFT LS on Rel-18 higher-layers parameter list | Moderator (Ericsson) |
R1-2306270 | LS on Rel-18 higher-layers parameter list | RAN1, Ericsson |
R1-2306271 | Consolidated higher layers parameter list for Rel-18 | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2305494 | RRC parameters for Rel-18 NR MIMO | Rapporteur (Samsung) |
R1-2306244 | RRC parameters for Rel-18 NR MIMO: post-RAN1#113 updated list | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2304348 | Unified TCI framework extension for multi-TRP | FUTUREWEI |
R1-2304375 | Unified TCI framework extension for multi-TRP | Panasonic |
R1-2304385 | Unified TCI framework extension for multi-TRP | MediaTek Inc. |
R1-2304389 | Moderator summary on extension of unified TCI framework (Round 0) | Moderator (MediaTek Inc.) |
R1-2304390 | Moderator summary on extension of unified TCI framework (Round 1) | Moderator (MediaTek Inc.) |
R1-2304391 | Moderator summary on extension of unified TCI framework (Round 2) | Moderator (MediaTek Inc.) |
R1-2304392 | Enhancements on unified TCI framework extension for multi-TRP | ZTE |
R1-2304421 | Enhanced Unified TCI for mTRP | InterDigital, Inc. |
R1-2304463 | Further discussion on unified TCI framework extension for multi-TRP | vivo |
R1-2304542 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
R1-2304636 | Discussion on unified TCI framework extension for multi-TRP | Huawei, HiSilicon |
R1-2304705 | Discussion on unified TCI framework extension for multi-TRP operation | CATT |
R1-2304760 | Discussion on unified TCI framework extension for multi-TRP | Fujitsu |
R1-2304783 | Unified TCI framework extension for multi-TRP | Ericsson |
R1-2304817 | On Unified TCI Framework for multi-TRP | Intel Corporation |
R1-2304873 | Unified TCI framework extension for multi-TRP | xiaomi |
R1-2304950 | Discussion of unified TCI framework for multi-TRP | Lenovo |
R1-2304963 | Discussion on unified TCI framework extension for multi-TRP | Hyundai Motor Company |
R1-2304988 | Discussion on unified TCI framework extension for multi-TRP | NEC |
R1-2305008 | Discussion on unified TCI framework extension for multi-TRP | |
R1-2305060 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
R1-2305077 | Discussion on unified TCI framework extension for multi-TRP | CMCC |
R1-2305226 | Unified TCI framework extension for multi-TRP | Apple |
R1-2305288 | Unified TCI framework extension for multi-TRP/panel | LG Electronics |
R1-2305318 | Extension of unified TCI framework for mTRP | Qualcomm Incorporated |
R1-2305401 | Unified TCI framework extension for multi-TRP | OPPO |
R1-2305495 | Views on unified TCI extension focusing on m-TRP | Samsung |
R1-2305583 | Discussion on unified TCI framework extension for multi-TRP | NTT DOCOMO, INC. |
R1-2305642 | Unified TCI framework extension for multi-TRP | MediaTek Inc. |
R1-2305704 | Discussion on unified TCI framework extension for multi-TRP | Transsion Holdings |
R1-2305733 | Unified TCI framework extension for multi-TRP | Sharp |
R1-2305748 | Unified TCI framework extension for multi-TRP | Nokia, Nokia Shanghai Bell |
R1-2305771 | Discussion on unified TCI framework extension for multi-TRP | ITRI |
R1-2305776 | Discussion on unified TCI framework extension for multi-TRP | FGI |
R1-2305892 | Discussion on Unified TCI framework extension for multi-TRP | CEWiT |
R1-2306155 | Moderator summary on extension of unified TCI framework (Final) | Moderator (MediaTek Inc.) |
R1-2306231 | Moderator summary on extension of unified TCI framework (Final) | Moderator (MediaTek Inc.) |
TDoc | Title | Source |
---|---|---|
R1-2304349 | Enhancements to support two TAs for multi-DCI | FUTUREWEI |
R1-2304386 | UL Tx Timing Management for MTRP Operation | MediaTek Inc. |
R1-2304393 | TA enhancement for multi-DCI | ZTE |
R1-2304422 | Multiple TA for mTRP Operation | InterDigital, Inc. |
R1-2304464 | Further discussion on two TAs for multi-DCI-based multi-TRP operation | vivo |
R1-2304543 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
R1-2304637 | Study on TA enhancement for UL M-TRP transmssion | Huawei, HiSilicon |
R1-2304706 | Remaining issues on two TAs for UL multi-DCI multi-TRP operation | CATT |
R1-2304784 | Two TAs for multi-DCI | Ericsson |
R1-2304874 | Discussion on two TAs for multi-TRP operation | xiaomi |
R1-2304951 | Discussion of two TAs for multi-DCI UL transmission | Lenovo |
R1-2304989 | Discussion on two TAs for multi-DCI | NEC |
R1-2305009 | Discussion on two TAs for multi-DCI | |
R1-2305078 | Discussion on two TAs for multi-DCI | CMCC |
R1-2305134 | Discussion on two TAs for multi-DCI based on multi-TRP operation | TCL Communication Ltd. |
R1-2305171 | On two TAs for multi-DCI | Intel Corporation |
R1-2305227 | Views on two TAs for multi-DCI Uplink Transmissions | Apple |
R1-2305289 | Two TAs for multi-TRP/panel | LG Electronics |
R1-2305319 | Supporting two TAs for multi-DCI based mTRP | Qualcomm Incorporated |
R1-2305402 | Two TAs for multi-DCI based multi-TRP operation | OPPO |
R1-2305496 | Views on two TAs for m-DCI | Samsung |
R1-2305584 | Discussion on two TAs for multi-DCI | NTT DOCOMO, INC. |
R1-2305643 | UL Tx Timing Management for MTRP Operation | MediaTek Inc. |
R1-2305705 | Discussion on two TAs for multi-DCI based multi-TRP operation | Transsion Holdings |
R1-2305738 | Two TAs for multi-DCI | Sharp |
R1-2305749 | Two TAs for UL multi-DCI multi-TRP operation | Nokia, Nokia Shanghai Bell |
R1-2305777 | Discussion on two TAs for multi-DCI | FGI |
R1-2305786 | Discussion on two TAs for multi-DCI operation | ETRI |
R1-2306053 | Moderator Summary #1 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2306128 | Moderator Summary #2 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2306203 | Moderator Summary #3 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2306229 | Draft reply on LS 2TA for multi-DCI multi-TRP | Moderator (Ericsson) |
R1-2306249 | Reply on LS 2TA for multi-DCI multi-TRP | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2304394 | CSI enhancement for high/medium UE velocities and CJT | ZTE |
R1-2304423 | Remaining Details on CSI for CJT and Medium/High UE Velocities | InterDigital, Inc. |
R1-2304465 | Further discussion on CSI enhancement for high-medium UE velocities and coherent JT | vivo |
R1-2304544 | Discussion on CSI enhancement for high/medium UE velocities and coherent JT | Spreadtrum Communications |
R1-2304638 | CSI enhancement for coherent JT and mobility | Huawei, HiSilicon |
R1-2304707 | Remaining issues on CSI enhancement | CATT |
R1-2304761 | Discussion on Rel-18 MIMO CSI enhancement | Fujitsu |
R1-2304812 | Discussion on CSI enhancements | Intel Corporation |
R1-2304836 | On CSI Enhancement | |
R1-2304875 | Further discussion on CSI enhancement for high/medium UE velocities and CJT | xiaomi |
R1-2304939 | Views on CSI Enhancements for CJT | AT&T |
R1-2304952 | Discussion of CSI enhancement for high speed UE and coherent JT | Lenovo |
R1-2304995 | Discussion on CSI enhancement | NEC |
R1-2305029 | Discussion on CSI enhancement for high/medium UE velocities and coherent JT | Sony |
R1-2305061 | CSI enhancements for medium UE velocities and coherent JT | Fraunhofer IIS, Fraunhofer HHI |
R1-2305079 | Discussion on CSI enhancement for high/medium UE velocities and CJT | CMCC |
R1-2305228 | Views on Rel-18 MIMO CSI enhancement | Apple |
R1-2305290 | Potential CSI enhancement for high/medium UE velocities and coherent JT | LG Electronics |
R1-2305320 | CSI enhancements for medium UE velocities and Coherent-JT | Qualcomm Incorporated |
R1-2305403 | CSI enhancement for high/medium UE velocities and coherent JT | OPPO |
R1-2305497 | Moderator summary on Rel-18 CSI enhancements | Moderator (Samsung) |
R1-2305498 | Summary of OFFLINE discussion on Rel-18 MIMO CSI | Moderator (Samsung) |
R1-2305499 | Views on CSI enhancements | Samsung |
R1-2305585 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
R1-2305669 | CSI Enhancements | MediaTek Inc. |
R1-2305683 | Discussion on CSI enhancement | Mavenir |
R1-2305715 | On CSI enhancements for Rel-18 NR MIMO evolution | Ericsson |
R1-2305750 | CSI enhancement for high/medium UE velocities and CJT | Nokia, Nokia Shanghai Bell |
R1-2305814 | CSI enhancements | Sharp |
R1-2306009 | Views on CSI enhancements | Samsung |
R1-2306080 | Moderator Summary#2 on Rel-18 CSI enhancements: ROUND 1 | Moderator (Samsung) |
R1-2306081 | Moderator Summary on Tuesday OFFLINE for Rel-18 CSI enhancements | Moderator (Samsung) |
R1-2306131 | Moderator Summary#3 on Rel-18 CSI enhancements: ROUND 2 | Moderator (Samsung) |
R1-2306132 | Moderator Summary on Wednesday OFFLINE for Rel-18 CSI enhancements | Moderator (Samsung) |
R1-2306136 | DRAFT LS to RAN4 on TDCP Agreement for Rel-18 MIMO | Moderator (Samsung) |
R1-2306137 | LS to RAN4 on TDCP Agreement for Rel-18 MIMO | RAN1, Samsung |
TDoc | Title | Source |
---|---|---|
R1-2304350 | On increasing the number of orthogonal DM-RS ports for MU-MIMO | FUTUREWEI |
R1-2304377 | Discussions on increased number of orthogonal DMRS ports | New H3C Technologies Co., Ltd. |
R1-2304395 | DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO | ZTE, China Telecom |
R1-2304424 | Further Details on DMRS Enhancements | InterDigital, Inc. |
R1-2304437 | On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO | Ericsson |
R1-2304466 | Further discussion on DMRS enhancements | vivo |
R1-2304545 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
R1-2304639 | Discussion on DMRS enhancements in Rel-18 | Huawei, HiSilicon |
R1-2304708 | Remaining issues of DMRS enhancements in Rel-18 | CATT |
R1-2304818 | DM-RS Enhancements for Rel-18 NR | Intel Corporation |
R1-2304837 | On DMRS Enhancement | |
R1-2304876 | Discussion on DMRS enhancement | xiaomi |
R1-2304953 | Discussion of increased number of orthogonal DMRS ports | Lenovo |
R1-2304996 | Discussion on increased number of orthogonal DMRS ports | NEC |
R1-2305059 | On increased number of orthogonal DMRS ports | Fraunhofer IIS, Fraunhofer HHI |
R1-2305080 | Discussion on increased number of orthogonal DMRS ports | CMCC |
R1-2305229 | Views on supporting increased number of orthogonal DMRS ports | Apple |
R1-2305291 | Increased number of orthogonal DMRS ports | LG Electronics |
R1-2305321 | Design for increased number of orthogonal DMRS ports | Qualcomm Incorporated |
R1-2305404 | DMRS enhancement for Rel-18 MIMO | OPPO |
R1-2305500 | Views on DMRS enhancements | Samsung |
R1-2305586 | Discussion on DMRS enhancements | NTT DOCOMO, INC. |
R1-2305670 | Increased number of orthogonal DMRS ports | MediaTek Inc. |
R1-2305734 | Increased number of orthogonal DMRS ports | Sharp |
R1-2305751 | Rel-18 UL and DL DMRS Enhancements | Nokia, Nokia Shanghai Bell |
R1-2305950 | FL summary#1 on DMRS | Moderator (NTT DOCOMO) |
R1-2305951 | FL summary#2 on DMRS | Moderator (NTT DOCOMO) |
R1-2306130 | FL summary#3 on DMRS | Moderator (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2304351 | SRS enhancements for TDD CJT and 8TX operation | FUTUREWEI |
R1-2304378 | Discussions on SRS enhancement in Rel-18 | New H3C Technologies Co., Ltd. |
R1-2304396 | SRS enhancement targeting TDD CJT and 8 TX operation | ZTE |
R1-2304420 | On SRS enhancements targeting TDD CJT and 8 TX operation | Ericsson |
R1-2304425 | Further Details on SRS for CJT and 8TX UEs | InterDigital, Inc. |
R1-2304467 | Further discussion on SRS enhancements | vivo |
R1-2304546 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
R1-2304640 | Discussion on SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 | Huawei, HiSilicon |
R1-2304709 | On SRS enhancement for CJT and 8Tx operation | CATT |
R1-2304819 | SRS Enhancements for Rel-18 NR | Intel Corporation |
R1-2304838 | On SRS Enhancement | |
R1-2304877 | Discussion on SRS enhancements | xiaomi |
R1-2304954 | Discussion of SRS enhancement | Lenovo |
R1-2304971 | Discussions on SRS enhancement targeting TDD CJT and 8 TX operation | KDDI Corporation |
R1-2304997 | Discussion on SRS enhancement | NEC |
R1-2305081 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | CMCC |
R1-2305230 | Views on Rel-18 MIMO SRS enhancement | Apple |
R1-2305292 | SRS enhancement targeting TDD CJT and 8 TX operation | LG Electronics |
R1-2305322 | SRS enhancement for TDD CJT and 8 Tx operation | Qualcomm Incorporated |
R1-2305405 | SRS enhancement targeting TDD CJT and 8 TX operation | OPPO |
R1-2305501 | Views on SRS enhancements | Samsung |
R1-2305587 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
R1-2305735 | SRS enhancement targeting TDD CJT and 8 TX operation | Sharp |
R1-2305752 | SRS enhancement for TDD CJT and 8Tx operation | Nokia, Nokia Shanghai Bell |
R1-2305787 | Discussion on SRS enhancement targeting TDD CJT | ETRI |
R1-2306064 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
R1-2306065 | FL Summary #2 on SRS enhancements | Moderator (FUTUREWEI) |
R1-2306066 | FL Summary #3 on SRS enhancements | Moderator (FUTUREWEI) |
TDoc | Title | Source |
---|---|---|
R1-2304376 | UL Precoding for Multi-panel Transmission | Panasonic |
R1-2304387 | Simultaneous transmission across multiple UE panels | MediaTek Inc. |
R1-2304397 | Enhancements on UL precoding indication for multi-panel transmission | ZTE |
R1-2304419 | UL precoding indication for multi-panel transmission | Ericsson |
R1-2304426 | Multi-panel Uplink Transmission | InterDigital, Inc. |
R1-2304468 | Further discussion on UL precoding indication for multi-panel transmission | vivo |
R1-2304547 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
R1-2304641 | Discussion on UL precoding indication for multi-panel transmission | Huawei, HiSilicon |
R1-2304710 | Further discussion on UL precoding indication for multi-panel transmission | CATT |
R1-2304762 | Discussion on UL precoding indication for multi-panel transmission | Fujitsu |
R1-2304839 | On Simultaneous Multi-Panel Transmission | |
R1-2304878 | Enhancements on multi-panel uplink transmission | xiaomi |
R1-2304955 | UL precoding indication for multi-panel transmission | Lenovo |
R1-2304964 | Discussion on UL precoding indication for multi-panel transmission | Hyundai Motor Company |
R1-2304990 | Discussion on UL precoding indication for multi-panel transmission | NEC |
R1-2305082 | Discussion on UL precoding indication for multi-panel transmission | CMCC |
R1-2305172 | UL precoding indication for multi-panel transmission | Intel Corporation |
R1-2305231 | Views on UL precoding indication for multi-panel simultaneous PUSCH transmissions | Apple |
R1-2305293 | UL precoding indication for multi-panel transmission | LG Electronics |
R1-2305323 | Simultaneous multi-panel transmission | Qualcomm Incorporated |
R1-2305406 | Discussion on UL precoding indication for multi-panel transmission | OPPO |
R1-2305502 | Views on UL precoding indication for STxMP | Samsung |
R1-2305588 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
R1-2305644 | Simultaneous transmission across multiple UE panels | MediaTek Inc. |
R1-2305739 | Views on UL multi-panel transmission | Sharp |
R1-2305753 | Precoder Indication for Multi-Panel UL Transmission | Nokia, Nokia Shanghai Bell |
R1-2305778 | Discussion on simultaneous transmission on multiple panels | FGI |
R1-2305812 | Discussion on UCI multiplexing regarding STxMP | ASUSTeK |
R1-2305966 | Summary #1 on Rel-18 STxMP | Moderator (OPPO) |
R1-2305967 | Summary #2 on Rel-18 STxMP | Moderator (OPPO) |
R1-2305968 | Summary #3 on Rel-18 STxMP | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2304398 | SRI/TPMI enhancement for enabling 8 TX UL transmission | ZTE |
R1-2304427 | Details on 8TX UE Operations | InterDigital, Inc. |
R1-2304428 | FL Summary SRI/TPMI Enhancements; Preparatory | Moderator (InterDigital, Inc.) |
R1-2304429 | FL Summary SRI/TPMI Enhancements; First Round | Moderator (InterDigital, Inc.) |
R1-2304430 | FL Summary SRI/TPMI Enhancements; Second Round | Moderator (InterDigital, Inc.) |
R1-2304431 | FL Summary SRI/TPMI Enhancements; Third Round | Moderator (InterDigital, Inc.) |
R1-2304432 | Recommended Direction on SRITPMI Enhancements for RAN1#114 | Moderator (InterDigital, Inc.) |
R1-2304469 | Further discussion on enabling 8 TX UL transmission | vivo |
R1-2304548 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
R1-2304642 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
R1-2304711 | SRI/TPMI enhancement for 8Tx UL transmission | CATT |
R1-2304840 | On SRI/TPMI Indication for 8Tx Transmission | |
R1-2304879 | Enhancements on 8Tx uplink transmission | xiaomi |
R1-2304956 | SRI/TPMI enhancement for enabling 8TX UL transmission | Lenovo |
R1-2304998 | Discussion on SRI/TPMI enhancement | NEC |
R1-2305030 | Considerations on SRI/TPMI enhancement for enabling 8 TX UL transmission | Sony |
R1-2305083 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | CMCC |
R1-2305173 | Discussion on enhancement for 8Tx UL transmission | Intel Corporation |
R1-2305232 | Views on SRI/TPMI enhancement for enabling 8 TX UL transmission | Apple |
R1-2305294 | SRI/TPMI enhancement for enabling 8 TX UL transmission | LG Electronics |
R1-2305324 | Enhancements for 8 Tx UL transmissions | Qualcomm Incorporated |
R1-2305407 | SRI TPMI enhancement for 8 TX UL transmission | OPPO |
R1-2305482 | SRI/TPMI Enhancement for Enabling 8 TX UL Transmission | Ericsson |
R1-2305503 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
R1-2305589 | Discussion on 8 TX UL transmission | NTT DOCOMO, INC. |
R1-2305671 | SRI/TPMI enhancement for enabling 8 Tx UL transmission | MediaTek Inc. |
R1-2305740 | Views on 8 TX UL transmission | Sharp |
R1-2305754 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
R1-2305779 | Discussion on SRI/TPMI Enhancements for 8 TX UL Transmission | FGI |
R1-2305893 | SRI/TPMI enhancement for enabling 8 TX UL transmission | CEWiT |
R1-2305906 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | KDDI Corporation |
R1-2306010 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
R1-2306078 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
R1-2306153 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
R1-2306166 | FL Summary SRI/TPMI Enhancements; Fourth Round | Moderator (InterDigital, Inc.) |
TDoc | Title | Source |
---|---|---|
R1-2305325 | Updated TR 38.843 including RAN1 agreements until RAN1#112 | Qualcomm Incorporated |
R1-2305326 | Updated TR 38.843 including RAN1 agreements from RAN1#112bis-e | Qualcomm Incorporated |
R1-2306142 | Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) | Ad-hoc Chair (CMCC) |
R1-2306170 | TR38.843 v0.1.0: Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface | Rapporteur (Qualcomm) |
R1-2306235 | TR38.843 v0.1.0: Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface | Rapporteur (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2304370 | Discussion on common AI/ML characteristics and operations | FUTUREWEI |
R1-2304418 | Discussion on general aspects of AI/ML framework | Continental Automotive Technologies GmbH |
R1-2304438 | Discussion on general aspects of AI/ML framework | Panasonic |
R1-2304470 | Discussions on AI/ML framework | vivo |
R1-2304533 | Discussion on general aspects of common AI PHY framework | ZTE |
R1-2304549 | Discussion on general aspects of AIML framework | Spreadtrum Communications |
R1-2304652 | Discussion on general aspects of AI/ML framework | Huawei, HiSilicon |
R1-2304679 | Discussion on general aspects of AI/ML LCM | NYCU, NTPU |
R1-2304680 | Further discussion on the general aspects of ML for Air-interface | Nokia, Nokia Shanghai Bell |
R1-2304721 | Discussion on AI/ML general framework | CATT |
R1-2304748 | Discussion on general aspects of AIML framework | Ericsson |
R1-2304763 | Discussion on general aspects of AI/ML framework | Fujitsu |
R1-2304778 | Discussion on general aspects of AI/ML framework | InterDigital, Inc. |
R1-2304841 | On General Aspects of AI/ML Framework | |
R1-2304892 | Views on the general aspects of AI/ML framework | xiaomi |
R1-2304947 | General Aspects of AI/ML framework | AT&T |
R1-2304991 | Discussion on general aspects of AI ML framework | NEC |
R1-2305014 | Considerations on general aspects on AI-ML framework | CAICT |
R1-2305028 | Discussion on general aspects of AI/ML framework | KDDI Corporation |
R1-2305031 | Considerations on common AI/ML framework | Sony |
R1-2305084 | Discussion on general aspects of AI/ML framework | CMCC |
R1-2305159 | General aspects of AI and ML framework for NR air interface | NVIDIA |
R1-2305174 | General aspects of AI/ML framework for NR air interface | Intel Corporation |
R1-2305197 | General aspects of AI/ML framework | Fraunhofer IIS, Fraunhofer HHI |
R1-2305201 | Discussion on general aspects of AI/ML framework | Lenovo |
R1-2305233 | Discussion on general aspect of AI/ML framework | Apple |
R1-2305295 | General aspects on AI/ML framework | LG Electronics |
R1-2305327 | General aspects of AI/ML framework | Qualcomm Incorporated |
R1-2305458 | On general aspects of AI/ML framework | OPPO |
R1-2305481 | Discussion on AI/ML Model Life Cycle Management | Rakuten Mobile, Inc |
R1-2305504 | General aspects of AI/ML framework and evaluation methodology | Samsung |
R1-2305590 | Discussion on general aspects of AI/ML framework | NTT DOCOMO, INC. |
R1-2305690 | Considering on system architecture for general AI/ML framework | TCL Communication Ltd. |
R1-2305691 | Discussions on General Aspects of AI/ML Framework | Indian Institute of Tech (M), IIT Kanpur |
R1-2305696 | Discussion on general aspects of AI/ML LCM | MediaTek Inc. |
R1-2305788 | Discussion on general aspects of AI/ML framework for NR air interface | ETRI |
R1-2306048 | Summary#1 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2306049 | Summary#2 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2306050 | Summary#3 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2306051 | Summary#4 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2306052 | Final summary of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2304371 | Discussion and evaluation of AI/ML for CSI feedback enhancement | FUTUREWEI |
R1-2304471 | Evaluation on AI/ML for CSI feedback enhancement | vivo |
R1-2304521 | Evaluations of AI-CSI | Ericsson |
R1-2304534 | Evaluation on AI CSI feedback enhancement | ZTE |
R1-2304550 | Discussion on evaluation on AIML for CSI feedback enhancement | Spreadtrum Communications, BUPT |
R1-2304653 | Evaluation on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
R1-2304681 | Evaluation of ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
R1-2304722 | Evaluation on AI/ML for CSI feedback enhancement | CATT |
R1-2304764 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu |
R1-2304779 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
R1-2304813 | Evaluation on AI/ML for CSI feedback enhancement | Intel Corporation |
R1-2304842 | On Evaluation of AI/ML based CSI | |
R1-2304854 | Evaluation on AI/ML for CSI feedback enhancement | China Telecom |
R1-2304893 | Discussion on evaluation on AI/ML for CSI feedback enhancement | xiaomi |
R1-2304948 | Discussion on AI/ML for CSI feedback enhancement | AT&T |
R1-2305015 | Some discussions on evaluation on AI-ML for CSI feedback | CAICT |
R1-2305085 | Discussion on evaluation on AI/ML for CSI feedback enhancement | CMCC |
R1-2305160 | Evaluation of AI and ML for CSI feedback enhancement | NVIDIA |
R1-2305202 | Evaluation on AI/ML for CSI feedback | Lenovo |
R1-2305234 | Evaluation for AI/ML based CSI feedback enhancement | Apple |
R1-2305296 | Evaluation on AI/ML for CSI feedback enhancement | LG Electronics |
R1-2305328 | Evaluation on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
R1-2305459 | Evaluation methodology and results on AI/ML for CSI feedback enhancement | OPPO |
R1-2305505 | Views on Evaluation of AI/ML for CSI feedback enhancement | Samsung |
R1-2305591 | Discussion on evaluation on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
R1-2305655 | Evaluation on AI/ML for CSI feedback enhancement | MediaTek Inc. |
R1-2305688 | Evaluation on AI/ML for CSI feedback enhancement | Mavenir |
R1-2305730 | Evaluation and preliminary results on AI/ML-based CSI feedback enhancement | BJTU |
R1-2305789 | Evaluation on AI/ML for CSI feedback enhancement | ETRI |
R1-2305894 | Evaluation of AI/ML for CSI feedback Enhancement | CEWiT |
R1-2305975 | Evaluation on AI/ML for CSI feedback enhancement | CATT |
R1-2305981 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu |
R1-2306058 | Summary#1 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
R1-2306059 | Summary#2 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
R1-2306060 | Summary#3 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
R1-2306061 | Summary#4 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
R1-2306062 | Summary#5 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
R1-2306063 | Summary#6 for CSI evaluation of [113-R18-AI/ML] | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2304372 | Discussion on other aspects of AI/ML for CSI feedback enhancement | FUTUREWEI |
R1-2304472 | Other aspects on AI/ML for CSI feedback enhancement | vivo |
R1-2304522 | Discussion on AI-CSI | Ericsson |
R1-2304535 | Discussion on other aspects for AI CSI feedback enhancement | ZTE |
R1-2304551 | Discussion on other aspects on AIML for CSI feedback | Spreadtrum Communications |
R1-2304654 | Discussion on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
R1-2304682 | Other aspects on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
R1-2304723 | Discussion on AI/ML for CSI feedback enhancement | CATT |
R1-2304765 | Views on specification impact for CSI feedback enhancement | Fujitsu |
R1-2304780 | Discussion on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
R1-2304814 | Discussion on AI/ML for CSI feedback | Intel Corporation |
R1-2304843 | On Enhancement of AI/ML based CSI | |
R1-2304855 | Discussion on AI/ML for CSI feedback enhancement | China Telecom |
R1-2304869 | Discussion on AI/ML for CSI feedback enhancement | Panasonic |
R1-2304894 | Further discussion on specification impact for CSI feedback based on AI/ML | xiaomi |
R1-2304949 | Discussion on AI/ML for CSI feedback enhancement | AT&T |
R1-2305016 | Discussions on AI-ML for CSI feedback | CAICT |
R1-2305032 | Considerations on CSI measurement enhancements via AI/ML | Sony |
R1-2305058 | Discussion on AI/ML based methods for CSI feedback enhancement | Fraunhofer IIS, Fraunhofer HHI |
R1-2305070 | Discussion on AI/ML for CSI feedback enhancement | NEC |
R1-2305086 | Discussion on other aspects on AI/ML for CSI feedback enhancement | CMCC |
R1-2305161 | AI and ML for CSI feedback enhancement | NVIDIA |
R1-2305203 | Further aspects of AI/ML for CSI feedback | Lenovo |
R1-2305235 | Discussion on other aspects of AI/ML for CSI enhancement | Apple |
R1-2305297 | Other aspects on AI/ML for CSI feedback enhancement | LG Electronics |
R1-2305329 | Other aspects on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
R1-2305460 | On sub use cases and other aspects of AI/ML for CSI feedback enhancement | OPPO |
R1-2305506 | Discussion on potential specification impact for CSI feedback enhancement | Samsung |
R1-2305592 | Discussion on other aspects on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
R1-2305656 | Other aspects on AI/ML for CSI feedback enhancement | MediaTek Inc. |
R1-2305763 | Discussion on AI/ML for CSI feedback enhancement | ITL |
R1-2305790 | Discussion on other aspects on AI/ML for CSI feedback enhancement | ETRI |
R1-2305873 | Other aspects on AI/ML for CSI feedback enhancement | IIT Kanpur |
R1-2306042 | Summary #1 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2306043 | Summary #2 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2306044 | Summary #3 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2306045 | Summary #4 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2306046 | Summary #5 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2306047 | Final summary on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2304373 | Discussion and evaluation of AI/ML for beam management | FUTUREWEI |
R1-2304439 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
R1-2304473 | Evaluation on AI/ML for beam management | vivo |
R1-2304536 | Evaluation on AI beam management | ZTE |
R1-2304552 | Evaluation on AI/ML for beam management | Spreadtrum Communications |
R1-2304655 | Evaluation on AI/ML for beam management | Huawei, HiSilicon |
R1-2304683 | Evaluation of ML for beam management | Nokia, Nokia Shanghai Bell |
R1-2304724 | Evaluation on AI/ML for beam management | CATT |
R1-2304749 | Evaluation of AIML for beam management | Ericsson |
R1-2304766 | Evaluation on AI/ML for beam management | Fujitsu |
R1-2304820 | Evaluations for AI/ML Beam Management | Intel Corporation |
R1-2304844 | On Evaluation of AI/ML based Beam Management | |
R1-2304856 | Evaluation on AI/ML for beam management | China Telecom |
R1-2304895 | Evaluation on AI/ML for beam management | xiaomi |
R1-2304979 | Evaluation on AI ML for Beam management | RAN1, Comba |
R1-2305017 | Some discussions on evaluation on AI-ML for Beam management | CAICT |
R1-2305087 | Discussion on evaluation on AI/ML for beam management | CMCC |
R1-2305162 | Evaluation of AI and ML for beam management | NVIDIA |
R1-2305204 | Evaluation on AI/ML for beam management | Lenovo |
R1-2305236 | Evaluation for AI/ML based beam management enhancements | Apple |
R1-2305298 | Evaluation on AI/ML for beam management | LG Electronics |
R1-2305330 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
R1-2305461 | Evaluation methodology and results on AI/ML for beam management | OPPO |
R1-2305507 | Evaluation on AI/ML for Beam management | Samsung |
R1-2305593 | Discussion on evaluation on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2305657 | Evaluation on AI/ML for beam management | MediaTek Inc. |
R1-2305731 | Evaluation methodology and results on AI/ML for beam management | BJTU |
R1-2305791 | Evaluation on AI/ML for beam management | ETRI |
R1-2305895 | Evaluation on AI/ML for beam management | CEWiT |
R1-2305982 | Evaluation on AI/ML for Beam management | Samsung |
R1-2306000 | Feature lead summary #0 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2306001 | Feature lead summary #1 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2306002 | Feature lead summary #2 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2306003 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2306199 | Feature lead summary #4 evaluation of AI/ML for beam management | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2304374 | Discussion on other aspects of AI/ML for beam management | FUTUREWEI |
R1-2304379 | Discussion on other aspects of AI/ML beam management | New H3C Technologies Co., Ltd. |
R1-2304440 | Discussion for other aspects on AI/ML for beam management | InterDigital, Inc. |
R1-2304474 | Other aspects on AI/ML for beam management | vivo |
R1-2304537 | Discussion on other aspects for AI beam management | ZTE |
R1-2304553 | Other aspects on AI/ML for beam management | Spreadtrum Communications |
R1-2304656 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
R1-2304684 | Other aspects on ML for beam management | Nokia, Nokia Shanghai Bell |
R1-2304725 | Discussion on AI/ML for beam management | CATT |
R1-2304750 | Discussion on AI/ML for beam management | Ericsson |
R1-2304767 | Discussion for specification impacts on AI/ML for beam management | Fujitsu |
R1-2304821 | Other Aspects on AI/ML for Beam Management | Intel Corporation |
R1-2304845 | On Enhancement of AI/ML based Beam Management | |
R1-2304896 | Potential specification impact on AI/ML for beam management | xiaomi |
R1-2304992 | Discussion on AI/ML for beam management | NEC |
R1-2305018 | Discussions on AI-ML for Beam management | CAICT |
R1-2305033 | Consideration on AI/ML for beam management | Sony |
R1-2305088 | Discussion on other aspects on AI/ML for beam management | CMCC |
R1-2305163 | AI and ML for beam management | NVIDIA |
R1-2305205 | Further aspects of AI/ML for beam management | Lenovo |
R1-2305237 | Discussion on other aspects of AI/ML based beam management enhancements | Apple |
R1-2305299 | Other aspects on AI/ML for beam management | LG Electronics |
R1-2305331 | Other aspects on AI/ML for beam management | Qualcomm Incorporated |
R1-2305462 | Other aspects of AI/ML for beam management | OPPO |
R1-2305508 | Discussion on potential specification impact for beam management | Samsung |
R1-2305594 | Discussion on other aspects on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2305658 | Other aspects on AI/ML for beam management | MediaTek Inc. |
R1-2305757 | Discussion on AI/ML for beam management | Panasonic |
R1-2305792 | Discussion on other aspects on AI/ML for beam management | ETRI |
R1-2306068 | Summary#1 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2306069 | Summary#2 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2306070 | Summary#3 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2306071 | Summary#4 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2306072 | Summary#5 for other aspects on AI/ML for beam management | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2304339 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Ericsson |
R1-2304475 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
R1-2304538 | Evaluation on AI positioning enhancement | ZTE |
R1-2304657 | Evaluation on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2304685 | Evaluation of ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
R1-2304726 | Evaluation on AI/ML for positioning enhancement | CATT |
R1-2304768 | Discussions on evaluation results of AIML positioning accuracy enhancement | Fujitsu |
R1-2304846 | On Evaluation of AI/ML based Positioning | |
R1-2304857 | Evaluation on AI/ML for positioning accuracy enhancement | China Telecom |
R1-2304897 | Evaluation on AI/ML for positioning accuracy enhancement | xiaomi |
R1-2305019 | Some discussions on evaluation on AI-ML for positioning accuracy enhancement | CAICT |
R1-2305089 | Discussion on evaluation on AI/ML for positioning accuracy enhancement | CMCC |
R1-2305123 | Evaluation on AI/ML for positioning accuracy enhancement | InterDigital, Inc. |
R1-2305164 | Evaluation of AI and ML for positioning enhancement | NVIDIA |
R1-2305206 | Discussion on AI/ML Positioning Evaluations | Lenovo |
R1-2305238 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
R1-2305300 | Evaluation on AI/ML for positioning accuracy enhancement | LG Electronics |
R1-2305332 | Evaluation on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
R1-2305463 | Evaluation methodology and results on AI/ML for positioning accuracy enhancement | OPPO |
R1-2305509 | Evaluation on AI/ML for Positioning | Samsung |
R1-2305659 | Evaluation of AIML for Positioning Accuracy Enhancement | MediaTek Inc. |
R1-2305689 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Indian Institute of Tech (M), IIT Kanpur |
R1-2305896 | Evaluation on AI/ML for Positioning Accuracy Enhancement | CEWiT |
R1-2305973 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
R1-2306054 | Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2306055 | Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2306056 | Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2306057 | Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2306112 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
TDoc | Title | Source |
---|---|---|
R1-2304340 | Other Aspects of AI/ML Based Positioning Enhancement | Ericsson |
R1-2304476 | Other aspects on AI/ML for positioning accuracy enhancement | vivo |
R1-2304539 | Discussion on other aspects for AI positioning enhancement | ZTE |
R1-2304554 | Discussion on other aspects on AIML for positioning accuracy enhancement | Spreadtrum Communications |
R1-2304658 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2304686 | Other aspects on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
R1-2304727 | Discussion on AI/ML for positioning enhancement | CATT |
R1-2304746 | Discussion of other aspects on AI/ML for positioning accuracy enhancement | NYCU |
R1-2304769 | Discussions on specification impacts for AIML positioning accuracy enhancement | Fujitsu |
R1-2304847 | On Enhancement of AI/ML based Positioning | |
R1-2304898 | Views on the other aspects of AI/ML-based positioning accuracy enhancement | xiaomi |
R1-2304921 | Other aspects on AI-ML for positioning accuracy enhancement | Baicells |
R1-2305001 | Discussion on AI/ML for positioning accuracy enhancement | NEC |
R1-2305020 | Discussions on AI-ML for positioning accuracy enhancement | CAICT |
R1-2305034 | On other aspects of AI/ML for positioning accuracy enhancement | Sony |
R1-2305090 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | CMCC |
R1-2305124 | Designs and potential specification impacts of AIML for positioning | InterDigital, Inc. |
R1-2305165 | AI and ML for positioning enhancement | NVIDIA |
R1-2305198 | On potential AI/ML solutions for positioning | Fraunhofer IIS, Fraunhofer HHI |
R1-2305207 | AI/ML Positioning use cases and associated Impacts | Lenovo |
R1-2305239 | On Other aspects on AI/ML for positioning accuracy enhancement | Apple |
R1-2305301 | Other aspects on AI/ML for positioning accuracy enhancement | LG Electronics |
R1-2305333 | Other aspects on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
R1-2305464 | On sub use cases and other aspects of AI/ML for positioning accuracy enhancement | OPPO |
R1-2305510 | Discussion on potential specification impact for Positioning | Samsung |
R1-2305595 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | NTT DOCOMO, INC. |
R1-2305660 | Other Aspects on AI ML Based Positioning Enhancement | MediaTek Inc. |
R1-2305992 | FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2305993 | FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2305994 | FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2306180 | FL summary #4 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2306206 | FL summary #5 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2305091 | TR 38.858 v0.4.0 for study on evolution of NR duplex operation | Rapporteur (CMCC) |
R1-2306344 | TR 38.858 v0.4.1 for study on evolution of NR duplex operation | Rapporteur (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2304380 | Discussion for Evaluation on NR duplex evolution | New H3C Technologies Co., Ltd. |
R1-2304477 | Evaluation on NR duplex evolution | vivo |
R1-2304555 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications, BUPT, New H3C |
R1-2304595 | SBFD Prototype and Preliminary Simulation Results | ZTE |
R1-2304646 | Discussion on evaluation and methodologies on evolution of NR duplex operation | Huawei, HiSilicon |
R1-2304728 | Discussion on evaluation on NR duplex evolution | CATT |
R1-2304788 | On evaluations for NR duplex evolution | InterDigital, Inc. |
R1-2304791 | Evaluation on NR duplex evolution | Ericsson |
R1-2304824 | Evaluations for NR Duplex evolution | Intel Corporation |
R1-2304899 | Discussion on evaluation on NR duplex evolution | xiaomi |
R1-2305035 | SBFD System Level Simulation Results | Sony |
R1-2305092 | Evaluation on NR duplex evolution | CMCC |
R1-2305187 | Discussion on evaluation of NR duplex evolution | MediaTek Inc. |
R1-2305194 | Evaluation of NR duplex evolution | Sharp |
R1-2305240 | On evaluations for NR duplex evolution | Apple |
R1-2305334 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | Qualcomm Incorporated |
R1-2305383 | Study on Evaluation for NR duplex evolution | LG Electronics |
R1-2305396 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
R1-2305465 | Discussion on evaluation on NR duplex evolution | OPPO |
R1-2305511 | Discussion on evaluation for NR duplex evolution | Samsung |
R1-2305596 | Discussion on evaluation on NR duplex evolution | NTT DOCOMO, INC. |
R1-2305897 | LLS for evaluation of coverage performance in TDD and SBFD systems | CEWiT, IITM |
R1-2306041 | Discussion on evaluation and methodologies on evolution of NR duplex operation | Huawei, HiSilicon |
R1-2306079 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
R1-2306092 | Evaluations for NR Duplex evolution | Intel Corporation |
R1-2306102 | Summary#1 on evaluation on NR duplex evolution | Moderator (CMCC) |
R1-2306103 | Summary#2 on evaluation on NR duplex evolution | Moderator (CMCC) |
R1-2306104 | Summary#3 on evaluation on NR duplex evolution | Moderator (CMCC) |
R1-2306219 | Final Summary on evaluation on NR duplex evolution | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2304381 | Discussion for subband non-overlapping full duplex | New H3C Technologies Co., Ltd. |
R1-2304478 | Discussion on subband non-overlapping full duplex | vivo |
R1-2304518 | Discussion on subband non-overlapping full duplex | TCL Communication Ltd. |
R1-2304556 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
R1-2304596 | Discussion of subband non-overlapping full duplex | ZTE |
R1-2304647 | Discussion on potential enhancement on subband non-overlapping full duplex | Huawei, HiSilicon |
R1-2304729 | Discussion on subband non-overlapping full duplex | CATT |
R1-2304770 | Discussion on subband non-overlapping full duplex | Fujitsu |
R1-2304789 | On subband non-overlapping full duplex operations | InterDigital, Inc. |
R1-2304792 | Subband non-overlapping full duplex | Ericsson |
R1-2304825 | On SBFD support | Intel Corporation |
R1-2304900 | Discussion on subband non-overlapping full duplex | xiaomi |
R1-2304972 | Discussion on subband non-overlapping full duplex | Panasonic |
R1-2305036 | Considerations on Subband Full Duplex TDD operations | Sony |
R1-2305067 | Discussion on subband non-overlapping full duplex | NEC |
R1-2305093 | Discussion on subband non-overlapping full duplex | CMCC |
R1-2305188 | Discussion on subband non-overlapping full duplex for NR | MediaTek Inc. |
R1-2305195 | Discussion on subband non-overlapping full duplex | Sharp |
R1-2305208 | Subband non-overlapping full duplex | Lenovo |
R1-2305241 | Views on subband non-overlapping full duplex | Apple |
R1-2305335 | Feasibility and techniques for Subband non-overlapping full duplex | Qualcomm Incorporated |
R1-2305384 | Study on Subband non-overlapping full duplex | LG Electronics |
R1-2305397 | On subband non-overlapping full duplex for NR | Nokia, Nokia Shanghai Bell |
R1-2305466 | Discussion on subband non-overlapping full duplex | OPPO |
R1-2305512 | On SBFD for NR duplex evolution | Samsung |
R1-2305549 | Details of subband non-overlapping full duplex | ASUSTeK |
R1-2305597 | Discussion on subband non-overlapping full duplex | NTT DOCOMO, INC. |
R1-2305695 | Discussion on subband non-overlapping full duplex | Indian Institute of Tech (M) |
R1-2305770 | Discussion on subband non-overlapping full duplex | KT Corp. |
R1-2305772 | Discussion on sub-band non-overlapping full duplex | ITRI |
R1-2305793 | Discussion on subband non-overlapping full duplex enhancements | ETRI |
R1-2305815 | Discussion on subband non-overlapping full duplex | WILUS Inc. |
R1-2305898 | Discussion on subband non-overlapping full duplex | CEWiT |
R1-2306073 | Summary #1 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2306074 | Summary #2 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2306075 | Summary #3 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2306076 | Summary #4 of subband non-overlapping full duplex | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2304382 | Discussion on potential enhancement on dynamic/flexible TDD | New H3C Technologies Co., Ltd. |
R1-2304479 | Potential enhancements on dynamic/flexible TDD | vivo |
R1-2304519 | Potential enhancement on dynamic/flexible TDD | TCL Communication Ltd. |
R1-2304557 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
R1-2304597 | Discussion of enhancements on dynamic/flexible TDD | ZTE, China Telecom |
R1-2304648 | Study on potential enhancements on dynamic/flexible TDD | Huawei, HiSilicon |
R1-2304730 | Discussion on potential enhancements on dynamic/flexible TDD | CATT |
R1-2304790 | On potential enhancements for dynamic/flexible TDD | InterDigital, Inc. |
R1-2304793 | Potential enhancements on dynamic/flexible TDD | Ericsson |
R1-2304826 | On dynamic/flexible TDD | Intel Corporation |
R1-2304858 | Field test for dynamic/flexible TDD | China Telecom, ZTE |
R1-2304901 | Discussion on potential enhancements on dynamic/flexible TDD | xiaomi |
R1-2304973 | Potential enhancements on dynamic/flexible TDD | Lenovo |
R1-2305005 | Discussion on potential enhancements on dynamic/flexible TDD | Panasonic |
R1-2305037 | Considerations on Dynamic / Flexible TDD | Sony |
R1-2305066 | Views on enhancements of dynamic/flexible TDD | NEC |
R1-2305094 | Discussion on potential enhancements on flexible/dynamic TDD | CMCC |
R1-2305189 | Discussion on potential enhancements for dynamic/flexible TDD | MediaTek Inc. |
R1-2305242 | Views on potential enhancements on dynamic TDD | Apple |
R1-2305336 | On potential enhancements on dynamic/flexible TDD | Qualcomm Incorporated |
R1-2305385 | Study on Potential enhancements on dynamic/flexible TDD | LG Electronics |
R1-2305398 | Dynamic TDD enhancements | Nokia, Nokia Shanghai Bell |
R1-2305467 | Discussion on potential enhancements on dynamic/flexible TDD | OPPO |
R1-2305513 | Dynamic and flexible TDD for NR duplex evolution | Samsung |
R1-2305598 | Discussion on potential enhancements on dynamic/flexible TDD | NTT DOCOMO, INC. |
R1-2305816 | Discussion on potential enhancements on dynamic/flexible TDD | WILUS Inc. |
R1-2305899 | Discussion on enhancements on dynamic/flexible TDD | CEWiT |
R1-2306093 | Summary #1 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2306094 | Summary #2 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2306095 | Summary #3 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2306096 | Summary #4 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2306278 | Post RAN1#113 Email Discussion of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2305420 | Initial higher layer parameters list for Rel-18 NR sidelink evolution WI | OPPO, Huawei, HiSilicon, LG Electronics |
R1-2305922 | Public Safety Screens Down Sidelink Considerations | AT&T, FirstNet |
R1-2306143 | Session notes for 9.4 (NR sidelink evolution) | Ad-Hoc Chair (Huawei) |
R1-2306263 | RRC parameters for Rel-18 NR sidelink evolution WI: post-RAN1#113 updated list | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2304341 | On Channel Access Mechanism for SL-U | Nokia, Nokia Shanghai Bell |
R1-2304363 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | FUTUREWEI |
R1-2304480 | Channel access mechanism for sidelink on unlicensed spectrum | vivo |
R1-2304558 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
R1-2304616 | SL-U channel access mechanism considerations | CableLabs |
R1-2304661 | Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
R1-2304731 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CATT, GOHIGH |
R1-2304771 | Discussion on channel access mechanism for SL-U | Fujitsu |
R1-2304798 | Sidelink channel access mechanisms for unlicensed spectrum | National Spectrum Consortium |
R1-2304902 | Discussion on channel access mechanism for sidelink-unlicensed | xiaomi |
R1-2304985 | Channel Access of Sidelink on Unlicensed Spectrum | NEC |
R1-2305021 | Considerations on channel access mechanism of SL-U | CAICT |
R1-2305038 | Discussion on channel access mechanism for SL-unlicensed | Sony |
R1-2305062 | Channel access mechanism for sidelink on FR1 unlicensed spectrum | Lenovo |
R1-2305095 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CMCC |
R1-2305152 | Sidelink channel access on unlicensed spectrum | InterDigital, Inc. |
R1-2305170 | Discussion on Channel Access Mechanisms | Johns Hopkins University APL |
R1-2305243 | Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum | Apple |
R1-2305337 | Channel Access Mechanism for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
R1-2305379 | Discussion on channel access mechanism for SL-U | ZTE, Sanechips |
R1-2305421 | Remaining issues on SL-U channel access mechanism and resource allocation | OPPO |
R1-2305514 | On channel access mehanism for sidelink on FR1 unlicensed spectrum | Samsung |
R1-2305599 | Discussion on channel access mechanism in SL-U | NTT DOCOMO, INC. |
R1-2305630 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | LG Electronics |
R1-2305672 | Discussion on channel access mechanism | MediaTek Inc. |
R1-2305692 | Sidelink channel access on unlicensed spectrum | Panasonic |
R1-2305706 | Discussion of channel access mechanism for sidelink in unlicensed spectrum | Transsion Holdings |
R1-2305758 | Channel Access Mechanism for SL-U | ITL |
R1-2305760 | NR Sidelink Unlicensed Channel Access Mechanisms | Fraunhofer HHI, Fraunhofer IIS |
R1-2305794 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | ETRI |
R1-2305817 | Discussion on channel access mechanism for SL-U | WILUS Inc. |
R1-2305843 | Discussion on channel access mechanism for NR sidelink evolution | Sharp |
R1-2305869 | Channel access mechanism for SL-U | Ericsson |
R1-2306025 | FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2306026 | FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2306027 | FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2306028 | FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2306029 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2304342 | On Physical Channel Design Framework for SL-U | Nokia, Nokia Shanghai Bell |
R1-2304364 | Discussion on physical channel design for sidelink on unlicensed spectrum | FUTUREWEI |
R1-2304481 | Physical channel design framework for sidelink on unlicensed spectrum | vivo |
R1-2304559 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
R1-2304662 | Physical channel design for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
R1-2304732 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CATT, GOHIGH |
R1-2304903 | Discussion on physical channel design for sidelink-unlicensed | xiaomi |
R1-2304982 | Discussion on physical channel design framework | NEC |
R1-2305039 | Discussion on physical channel design framework for SL-unlicensed | Sony |
R1-2305063 | Physical layer design framework for sidelink on FR1 unlicensed spectrum | Lenovo |
R1-2305096 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CMCC |
R1-2305153 | SL U physical layer design framework | InterDigital, Inc. |
R1-2305244 | Sidelink Physical Channel Design Framework for Unlicensed Spectrum | Apple |
R1-2305338 | Physical Channel Design for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
R1-2305380 | Discussion on physical layer structures and procedures for SL-U | ZTE, Sanechips |
R1-2305422 | Remaining issues on SL-U PHY channel designs and procedures | OPPO |
R1-2305515 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Samsung |
R1-2305600 | Discussion on channel design framework in SL-U | NTT DOCOMO, INC. |
R1-2305631 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
R1-2305673 | Discussion on physical channel design framework | MediaTek Inc. |
R1-2305694 | Physical channel design for sidelink on unlicensed spectrum | Panasonic |
R1-2305707 | Discussion of physical channel design for sidelink in unlicensed spectrum | Transsion Holdings |
R1-2305759 | Physical Channel Design framework for SL-U | ITL |
R1-2305761 | NR Sidelink Unlicensed Physical Channel Design | Fraunhofer HHI, Fraunhofer IIS |
R1-2305795 | Discussion on physical channel design framework for SL-U | ETRI |
R1-2305818 | Discussion on PHY channel design framework for SL-U | WILUS Inc. |
R1-2305844 | Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum | Sharp |
R1-2305870 | PHY channel design framework for SL-U | Ericsson |
R1-2305986 | FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2305987 | FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2305988 | FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2305989 | FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2305990 | FL summary#5 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2305991 | FL summary#6 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2304343 | On Co-channel Coexistence for LTE Sidelink and NR Sidelink | Nokia, Nokia Shanghai Bell |
R1-2304409 | Dynamic co-channel coexistence for LTE sidelink and NR sidelink | TOYOTA Info Technology Center |
R1-2304482 | Co-channel coexistence for LTE sidelink and NR sidelink | vivo |
R1-2304560 | Discussion on Co-channel coexistence for LTE sidelink and NR sidelink | Spreadtrum Communications |
R1-2304663 | Co-channel coexistence for LTE sidelink and NR sidelink | Huawei, HiSilicon |
R1-2304733 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | CATT, GOHIGH |
R1-2304805 | Remaining issues on NR-LTE sidelink co-channel co-existence | Intel Corporation |
R1-2304904 | Discussion on co-channel coexistence for LTE and NR sidelink | xiaomi |
R1-2304966 | Discussion on Sidelink Co-channel Coexistence | Panasonic |
R1-2304986 | Co-existence between LTE and NR sidelink | NEC |
R1-2305064 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Lenovo |
R1-2305154 | Co-channel coexistence for LTE sidelink and NR sidelink | InterDigital, Inc. |
R1-2305245 | Co-channel Coexistence for LTE Sidelink and NR Sidelink | Apple |
R1-2305339 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
R1-2305381 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | ZTE, Sanechips |
R1-2305423 | Remaining details on dynamic resource sharing | OPPO |
R1-2305516 | Remaining details on co-channel coexistence for LTE sidelink and NR sidelink | Samsung |
R1-2305601 | Discussion on co-channel coexistence of LTE-SL and NR-SL | NTT DOCOMO, INC. |
R1-2305632 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics |
R1-2305637 | FL Summary #1 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2305638 | FL Summary #2 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2305639 | FL Summary #3 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2305762 | Discussion on Co-Channel Coexistence for LTE and NR Sidelink | Fraunhofer HHI, Fraunhofer IIS |
R1-2305796 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | ETRI |
R1-2305819 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | WILUS Inc. |
R1-2305845 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Sharp |
R1-2305871 | Co-channel coexistence between LTE sidelink and NR sidelink | Ericsson |
R1-2305907 | On sidelink co-channel coexistence issues | Mitsubishi Electric RCE |
R1-2305949 | Dynamic co-channel coexistence for LTE sidelink and NR sidelink | TOYOTA Info Technology Center, Continental Automotive |
R1-2305969 | On sidelink co-channel coexistence issues | Mitsubishi Electric RCE |
R1-2306100 | FL Summary #4 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2306101 | FL Summary #5 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2304344 | On Beam Management for Sidelink in FR2 | Nokia, Nokia Shanghai Bell |
R1-2304410 | Discussion on sidelink beam management on FR2 licensed spectrum | TOYOTA Info Technology Center |
R1-2304483 | Enhanced sidelink operation on FR2 licensed spectrum | vivo |
R1-2304561 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Spreadtrum Communications |
R1-2304664 | Enhanced sidelink operation on FR2 licensed spectrum | Huawei, HiSilicon |
R1-2304734 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | CATT |
R1-2304806 | On Sidelink Operation in FR2 Licensed Spectrum | Intel Corporation |
R1-2304905 | Discussion on SL beam management in FR2 licensed spectrum | xiaomi |
R1-2304983 | Discussion on sidelink operation on FR2 licensed spectrum | NEC |
R1-2305040 | Discussion on sidelink beam management on FR2 licensed spectrum | Sony |
R1-2305065 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Lenovo |
R1-2305097 | Discussion on sidelink enhancements on FR2 licensed spectrum | CMCC |
R1-2305155 | On enhanced SL FR2 operation | InterDigital, Inc. |
R1-2305169 | Discussion on Enhanced Sidelink Operation on FR2 Licensed Spectrum | Johns Hopkins University APL |
R1-2305246 | Sidelink Operation on FR2 | Apple |
R1-2305340 | Enhanced sidelink operation on FR2 licensed spectrum | Qualcomm Incorporated |
R1-2305382 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | ZTE, Sanechips |
R1-2305424 | On sidelink beam management in FR2 | OPPO |
R1-2305517 | On enhanced SL Operation in FR2 | Samsung |
R1-2305602 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | NTT DOCOMO, INC. |
R1-2305633 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | LG Electronics |
R1-2305674 | Discussion on SL operation on FR2 | MediaTek Inc. |
R1-2305708 | Discussion of sidelink operation on FR2 | Transsion Holdings |
R1-2305764 | Sidelink Operation in FR2 | Fraunhofer HHI, Fraunhofer IIS |
R1-2305797 | Discussion on enhanced SL operation on FR2 licensed spectrum | ETRI |
R1-2305820 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | WILUS Inc. |
R1-2305846 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Sharp |
R1-2305872 | Study aspects for sidelink in FR2 licensed spectrum | Ericsson |
R1-2305900 | Views on beam enhancement procedures for sidelink FR2 operation | CEWiT |
R1-2306017 | FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
R1-2306018 | FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
R1-2306019 | FL summary #3 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2304827 | Higher layer parameters for Rel-18 Positioning | Intel Corporation |
R1-2306109 | Moderator summary on LS reply on the RAT-dependent positioning integrity (R1-2304332) | Moderator (InterDigital, Inc.) |
R1-2306144 | Session notes for 9.5 (Study on expanded and improved NR positioning) | Ad-Hoc Chair (Huawei) |
R1-2306156 | Draft LS reply on the RAT-dependent positioning integrity | Moderator (InterDigital, Inc.) |
R1-2306157 | LS reply on the RAT-dependent positioning integrity | RAN1, InterDigital, Inc. |
R1-2306237 | FLS on list of RRC parameters on Rel-18 WI on expanded and improved NR positioning | Rapporteur (Intel Corporation) |
R1-2306238 | RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning | Rapporteur (Intel Corporation) |
TDoc | Title | Source |
---|---|---|
R1-2306082 | Moderator summary on discussion of SA2 LS in R1-2304306 on SL positioning procedure | Moderator (xiaomi) |
R1-2306140 | Draft Reply LS on Sidelink positioning procedure | Moderator (xiaomi) |
R1-2306207 | Moderator summary (EOM) on discussion of SA2 LS in R1-2304306 on SL positioning procedure | Moderator (xiaomi) |
R1-2306208 | Reply LS on Sidelink positioning procedure | RAN1, xiaomi |
TDoc | Title | Source |
---|---|---|
R1-2304345 | Design of SL positioning reference signal SL-PRS | Nokia, Nokia Shanghai Bell |
R1-2304365 | Discussion on SL positioning reference signal | FUTUREWEI |
R1-2304411 | Discussion on SL positioning reference signal | TOYOTA Info Technology Center |
R1-2304484 | Discussion on SL positioning reference signal | vivo |
R1-2304562 | Discussion on SL positioning reference signal | Spreadtrum Communications |
R1-2304621 | Remaining issues on SL-PRS and power control | Huawei, HiSilicon |
R1-2304677 | Considerations on some aspects of SL PRS | Continental Automotive |
R1-2304735 | On SL positioning reference signal | CATT, GOHIGH |
R1-2304828 | On SL Positioning Reference Signals | Intel Corporation |
R1-2304859 | Discussion on SL positioning reference signal | China Telecom |
R1-2304906 | Discussion on sidelink positioning reference signal | xiaomi |
R1-2304927 | Discussion on SL positioning reference signal | ZTE |
R1-2304967 | Discussion on Sidelink Positioning Reference Signal | Panasonic |
R1-2305003 | Discussion on SL positioning reference signal | NEC |
R1-2305041 | On SL Positioning Reference Signal | Sony |
R1-2305098 | Discussion on SL positioning reference signal | CMCC |
R1-2305125 | SL-PRS design and power control for SL-PRS | InterDigital, Inc. |
R1-2305168 | Considerations on SL PRS sequence ID selection | Philips International B.V. |
R1-2305199 | Design considerations on SL positioning reference signal | Fraunhofer IIS, Fraunhofer HHI |
R1-2305247 | On SL positioning reference signal | Apple |
R1-2305341 | Reference Signal Design for SL Positioning | Qualcomm Incorporated |
R1-2305427 | Discussion on SL positioning reference signal | OPPO |
R1-2305518 | On SL Positioning Reference Signal | Samsung |
R1-2305634 | Discussion on SL positioning reference signal | LG Electronics |
R1-2305684 | SL positioning reference signal | Sharp |
R1-2305701 | Discussion on sidelink positioning reference signal | ASUSTeK |
R1-2305736 | Discussion on SL PRS Design | Lenovo |
R1-2305829 | SL positioning reference signal design | Ericsson |
R1-2305836 | Reference signal design for sidelink positioning | MediaTek (Chengdu) Inc. |
R1-2305883 | SL positioning reference signal design | Ericsson |
R1-2305901 | Further discussion on sidelink positioning reference signal design aspects | CEWiT |
R1-2305995 | FL summary #1 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2305996 | FL summary #2 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2305997 | FL summary #3 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2306236 | FL summary #4 on SL positioning reference signal | Moderator (Intel Corporation) |
TDoc | Title | Source |
---|---|---|
R1-2304346 | On measurements and reporting for SL positioning | Nokia, Nokia Shanghai Bell |
R1-2304366 | Discussion on measurements and reporting for SL positioning | FUTUREWEI |
R1-2304485 | Discussion on measurements and reporting for SL positioning | vivo |
R1-2304563 | Discussion on measurements and reporting for SL positioning | Spreadtrum Communications |
R1-2304622 | Remaining issues on SL positioning measurement and reporting | Huawei, HiSilicon |
R1-2304736 | On measurements and reporting for SL positioning | CATT, GOHIGH |
R1-2304796 | On measurements for SL positioning congestion control | Continental Automotive |
R1-2304829 | On measurements and reporting for SL positioning | Intel Corporation |
R1-2304907 | Discussion on measurements and reporting for SL positioning | xiaomi |
R1-2304928 | Discussion on SL positioning measurements and reporting | ZTE |
R1-2305042 | Discussion on measurements and reporting for SL positioning | Sony |
R1-2305099 | Discussion on measurements and reporting for SL positioning | CMCC |
R1-2305126 | Measurement and reporting for SL positioning | InterDigital, Inc. |
R1-2305200 | Measurements and reporting for SL positioning | Fraunhofer IIS, Fraunhofer HHI |
R1-2305248 | On Measurements and reporting for SL positioning | Apple |
R1-2305342 | Measurements and Reporting for SL Positioning | Qualcomm Incorporated |
R1-2305428 | Discussion on measurements and reporting for SL positioning | OPPO |
R1-2305476 | Discussion on SL positioning measurements and reporting | BUPT |
R1-2305519 | On Measurements and Reporting for SL Positioning | Samsung |
R1-2305635 | Discussion on measurements and reporting for SL positioning | LG Electronics |
R1-2305685 | Measurements and reporting for SL positioning | Sharp |
R1-2305737 | Discussion on SL Positioning Measurement and Reporting | Lenovo |
R1-2305830 | Measurements and reporting for SL positioning | Ericsson |
R1-2305837 | Measurement and reporting design for sidelink positioning | MediaTek (Chengdu) Inc. |
R1-2305884 | Measurements and reporting for SL positioning | Ericsson |
R1-2305902 | View on measurements and reporting for SL positioning methods | CEWiT |
R1-2306040 | Measurement and reporting for SL positioning | InterDigital, Inc. |
R1-2306097 | Summary #1 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2306098 | Summary #2 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2306099 | Summary #3 on Measurements and reporting for SL positioning | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2304347 | On resource allocation for SL positioning reference signal | Nokia, Nokia Shanghai Bell |
R1-2304367 | Discussion on resource allocation for SL PRS | FUTUREWEI |
R1-2304412 | Discussion on resource allocation for SL positioning reference signal | TOYOTA Info Technology Center |
R1-2304486 | Discussion on resource allocation for SL positioning reference signal | vivo |
R1-2304564 | Discussion on resource allocation for SL positioning reference signal | Spreadtrum Communications |
R1-2304623 | Discussion on SL-PRS resource allocation | Huawei, HiSilicon |
R1-2304676 | Considerations on resource allocation for SL positioning | Continental Automotive |
R1-2304737 | On resource allocation for SL positioning reference signal | CATT, GOHIGH |
R1-2304830 | On resource allocation for SL positioning | Intel Corporation |
R1-2304908 | Discussion on resource allocation for SL positioning reference signal | xiaomi |
R1-2304929 | Discussion on resource allocation for SL positioning reference signal | ZTE |
R1-2304968 | Discussion on Resource Allocation for SL-PRS | Panasonic |
R1-2305004 | Discussion on resource allocation for SL positioning reference signal | NEC |
R1-2305043 | On Resource Allocation for SL Positioning Reference Signal | Sony |
R1-2305100 | Discussion on resource allocation for SL positioning reference signal | CMCC |
R1-2305127 | Resource allocation for SL positioning reference signal | InterDigital, Inc. |
R1-2305213 | Considerations on SL-PRS resource allocation | Fraunhofer IIS, Fraunhofer HHI |
R1-2305249 | On Resource allocation for SL positioning reference signal | Apple |
R1-2305343 | Resource Allocation for SL-PRS | Qualcomm Incorporated |
R1-2305429 | Discussion on resource allocation for SL positioning reference signal | OPPO |
R1-2305520 | On Resource Allocation for SL Positioning Reference Signal | Samsung |
R1-2305636 | Discussion on resource allocation for SL positioning reference signal | LG Electronics |
R1-2305686 | Resource allocation for SL positioning reference signal | Sharp |
R1-2305702 | Discussion on resource allocation for SL PRS | ASUSTeK |
R1-2305741 | Discussion on SL Positioning Resource Allocation | Lenovo |
R1-2305785 | Considerations on resource allocation for SL positioning | ITL |
R1-2305831 | Resource allocation for SL positioning reference signal | Ericsson |
R1-2305839 | Resource allocation for SL-PRS | MediaTek (Chengdu) Inc. |
R1-2305885 | Resource allocation for SL positioning reference signal | Ericsson |
R1-2305903 | Further discussion on SL positioning resource allocation for SL positioning reference signal | CEWiT |
R1-2306067 | Moderator Summary #1 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2306124 | Moderator Summary #2 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2306171 | Moderator Summary #3 on resource allocation for SL PRS | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2304487 | Discussion on carrier phase positioning | vivo |
R1-2304565 | Discussion on NR DL and UL carrier phase positioning | Spreadtrum Communications |
R1-2304624 | Remaining issues for NR carrier phase positioning | Huawei, HiSilicon |
R1-2304738 | On NR DL and UL carrier phase positioning | CATT |
R1-2304831 | On carrier phase positioning | Intel Corporation |
R1-2304909 | NR DL and UL carrier phase positioning | xiaomi |
R1-2304930 | Discussion on carrier phase positioning | ZTE |
R1-2304970 | Discussion on NR DL and UL carrier phase positioning | Locaila |
R1-2305101 | Discussion on DL/UL carrier phase positioning | CMCC |
R1-2305129 | Discussion on positioning based on NR carrier phase measurement | InterDigital, Inc. |
R1-2305177 | Views on NR DL and UL carrier phase positioning | Nokia, Nokia Shanghai Bell |
R1-2305182 | Discussion on NR UL and DL carrier phase positioning | IIT Kanpur, CEWiT |
R1-2305214 | NR carrier phase measurements for positioning | Fraunhofer IIS, Fraunhofer HHI |
R1-2305250 | On NR DL and UL carrier phase positioning | Apple |
R1-2305344 | NR Carrier Phase Positioning | Qualcomm Incorporated |
R1-2305386 | Discussion on carrier phase positioning in NR | LG Electronics |
R1-2305413 | Discussions on NR carrier phase positioning | OPPO |
R1-2305521 | On NR DL and UL Carrier Phase Positioning | Samsung |
R1-2305603 | Discussion on NR DL and UL carrier phase positioning | NTT DOCOMO, INC. |
R1-2305742 | DL & UL Carrier Phase Positioning Discussion | Lenovo |
R1-2305832 | NR DL and UL carrier phase positioning | Ericsson |
R1-2305840 | Solutions for carrier phase positioning | MediaTek (Chengdu) Inc. |
R1-2305886 | NR DL and UL carrier phase positioning | Ericsson |
R1-2305970 | FL Summary #1 for NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2305971 | FL Summary #2 for NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2305972 | FL Summary #3 for NR DL and UL carrier phase positioning | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2304369 | On enhancements for Rel-18 NR LPHAP | FUTUREWEI |
R1-2304488 | Discussion on low power high accuracy positioning | vivo |
R1-2304566 | Discussion on LPHAP (Low Power High Accuracy Positioning) | Spreadtrum Communications |
R1-2304625 | Remaining issues of SRS in multiple cells | Huawei, HiSilicon |
R1-2304739 | On Low Power High Accuracy Positioning | CATT |
R1-2304747 | Discussion on Low Power High Accuracy Positioning | Quectel |
R1-2304832 | On low power high accuracy positioning | Intel Corporation |
R1-2304910 | Discussion on Low Power High Accuracy Positioning | xiaomi |
R1-2304931 | Discussion on low power high accuracy positioning | ZTE |
R1-2305002 | Discussion on Low Power High Accuracy Positioning | NEC |
R1-2305044 | Discussion on LPHAP | Sony |
R1-2305102 | Discussion on low power high accuracy positioning | CMCC |
R1-2305131 | Discussions on Low Power High Accuracy Positioning (LPHAP) techniques | InterDigital, Inc. |
R1-2305178 | Views on LPHAP | Nokia, Nokia Shanghai Bell |
R1-2305251 | On Low Power High Accuracy Positioning | Apple |
R1-2305345 | Discussion on LPHAP Positioning | Qualcomm Incorporated |
R1-2305387 | Discussion on LPHAP in idle/inactive state | LG Electronics |
R1-2305415 | Discussion on low power high accuracy positioning | OPPO |
R1-2305522 | On Low Power High Accuracy Positioning | Samsung |
R1-2305604 | Discussion on Low Power High Accuracy Positioning | NTT DOCOMO, INC. |
R1-2305833 | On Low Power High Accuracy Positioning | Ericsson |
R1-2305887 | On Low Power High Accuracy Positioning | Ericsson |
R1-2306014 | Summary #1 for low power high accuracy positioning | Moderator (CMCC) |
R1-2306015 | Summary #2 for low power high accuracy positioning | Moderator (CMCC) |
R1-2306016 | Summary #3 for low power high accuracy positioning | Moderator (CMCC) |
R1-2306247 | Draft LS on determination of UL timing to transmit SRS for positioning by UEs in RRC_INACTIVE states | CMCC |
R1-2306248 | LS on determination of UL timing to transmit SRS for positioning by UEs in RRC_INACTIVE states | RAN1, CMCC |
TDoc | Title | Source |
---|---|---|
R1-2304489 | Discussion on bandwidth aggregation for positioning measurements | vivo |
R1-2304567 | Discussion on bandwidth aggregation for positioning measurements | Spreadtrum Communications |
R1-2304626 | Remaining issues on PRS/SRS BW aggregation | Huawei, HiSilicon |
R1-2304740 | On bandwidth aggregation for positioning measurements | CATT |
R1-2304833 | On bandwidth aggregation for positioning | Intel Corporation |
R1-2304911 | Bandwidth aggregation for positioning measurement | xiaomi |
R1-2304932 | Discussion on BW aggregation for positioning | ZTE |
R1-2304935 | Summary #1 for BW aggregation positioning | Moderator (ZTE) |
R1-2304936 | Summary #2 for BW aggregation positioning | Moderator (ZTE) |
R1-2304937 | Summary #3 for BW aggregation positioning | Moderator (ZTE) |
R1-2305012 | Discussions on Carrier Aggregation for NR Positioning | BUPT |
R1-2305103 | Discussion on BW aggregation for positioning measurements | CMCC |
R1-2305132 | Bandwidth aggregation for positioning measurements | InterDigital, Inc. |
R1-2305179 | Views on Bandwidth aggregation for positioning measurements | Nokia, Nokia Shanghai Bell |
R1-2305252 | On Bandwidth aggregation for positioning measurements | Apple |
R1-2305346 | Discussion on Bandwidth aggregation for Positioning | Qualcomm Incorporated |
R1-2305388 | Discussion on Bandwidth aggregation for positioning measurements | LG Electronics |
R1-2305414 | Discussion on bandwidth aggregation for positioning measurement | OPPO |
R1-2305523 | On Bandwidth Aggregation for Positioning Measurements | Samsung |
R1-2305605 | Discussion on bandwidth aggregation for positioning measurements | NTT DOCOMO, INC. |
R1-2305743 | PRS/SRS Bandwidth Aggregation Aspects | Lenovo |
R1-2305834 | Bandwidth aggregation for positioning measurements | Ericsson |
R1-2305841 | PRS/SRS aggregation for positioning measurement | MediaTek (Chengdu) Inc. |
R1-2305888 | Bandwidth aggregation for positioning measurements | Ericsson |
R1-2306213 | Draft LS to RAN2 on SRS bandwidth aggregation for positioning | ZTE |
R1-2306214 | LS to RAN2 on SRS bandwidth aggregation for positioning | RAN1, ZTE |
R1-2306215 | Draft LS to RAN4 on SRS and PRS bandwidth aggregation for positioning | ZTE |
R1-2306216 | LS to RAN4 on SRS and PRS bandwidth aggregation for positioning | RAN1, ZTE |
TDoc | Title | Source |
---|---|---|
R1-2304368 | On positioning for RedCap UEs in Rel-18 | FUTUREWEI |
R1-2304490 | Discussion on positioning for RedCap UEs | vivo |
R1-2304568 | Discussion on positioning for RedCap UEs | Spreadtrum Communications |
R1-2304627 | Remaining issues on positioning for RedCap UEs | Huawei, HiSilicon |
R1-2304741 | On positioning for RedCap UEs | CATT |
R1-2304834 | On positioning for RedCap UEs | Intel Corporation |
R1-2304933 | Discussion on Positioning for RedCap UEs | ZTE |
R1-2304987 | Discussion on positioning support for RedCap UEs | NEC |
R1-2305045 | On Positioning for RedCap UEs | Sony |
R1-2305104 | Discussion on RedCap UE positioning | CMCC |
R1-2305133 | Positioning for RedCap UEs | InterDigital, Inc. |
R1-2305180 | Views on Positioning for RedCap UEs | Nokia, Nokia Shanghai Bell |
R1-2305183 | Discussion on NR positioning for RedCap | IIT Kanpur, CEWiT |
R1-2305253 | On Positioning for RedCap UEs | Apple |
R1-2305347 | Positioning for Reduced Capabilities UEs | Qualcomm Incorporated |
R1-2305389 | Discussion on positioning support for RedCap UEs | LG Electronics |
R1-2305416 | Discussion on positioning for RedCap UEs | OPPO |
R1-2305524 | On Positioning for RedCap UEs | Samsung |
R1-2305606 | Discussion on positioning for RedCap UEs | NTT DOCOMO, INC. |
R1-2305744 | RedCap Positioning | Lenovo |
R1-2305835 | Positioning for RedCap UEs | Ericsson |
R1-2305842 | Positioning for RedCap UEs | MediaTek (Chengdu) Inc. |
R1-2305889 | Positioning for RedCap Ues | Ericsson |
R1-2305961 | Positioning for Reduced Capabilities UEs | Qualcomm Incorporated |
R1-2306114 | Feature Lead summary #1 for Positioning for RedCap UEs | Moderator (Ericsson) |
R1-2306115 | Feature Lead summary #2 for Positioning for RedCap UEs | Moderator (Ericsson) |
R1-2306116 | Feature Lead summary #3 for Positioning for RedCap UEs | Moderator (Ericsson) |
R1-2306117 | Feature Lead summary #4 for Positioning for RedCap UEs | Moderator (Ericsson) |
R1-2306118 | Draft reply LS for DL PRS and UL SRS frequency hopping Switching time | Moderator (Ericsson) |
R1-2306119 | LS reply on switching time for DL PRS or UL SRS frequency hopping for RedCap Ues | RAN1, Ericsson |
R1-2306120 | Summary of discussion on LS for DL PRS and UL SRS frequency hopping Switching time | Moderator (Ericsson) |
R1-2306226 | [DRAFT] LS on the use of a single measurement gap for DL PRS with Rx hopping measurement | Ericsson |
R1-2306227 | LS on the use of a single measurement gap for DL PRS with Rx hopping measurement | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2304336 | Initial input on higher layer signalling for Rel-18 eRedCap | Rapporteur (Ericsson) |
R1-2305960 | RAN1 agreements for Rel-18 NR RedCap | Rapporteur (Ericsson) |
R1-2306145 | Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) | Ad-hoc Chair (CMCC) |
R1-2306261 | RAN1 agreements for Rel-18 NR RedCap | Rapporteur (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2304338 | Further RedCap UE complexity reduction | Ericsson |
R1-2304359 | Discussion on R18 RedCap complexity | FUTUREWEI |
R1-2304491 | Discussion on further UE complexity reduction | vivo |
R1-2304526 | Discussion on further UE complexity reduction | ZTE, Sanechips |
R1-2304569 | Discussion on enhanced support of RedCap devices | Spreadtrum Communications |
R1-2304629 | Discussion on potential solutions to further reduce UE complexity | Huawei, HiSilicon |
R1-2304742 | Discussion on further complexity reduction for Rel-18 RedCap UE | CATT |
R1-2304758 | RedCap UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
R1-2304802 | Complexity reduction for eRedCap UE | Intel Corporation |
R1-2304860 | Discussion on further complexity reduction for eRedCap UEs | China Telecom |
R1-2304912 | Discussion on further complexity reduction for eRedCap UEs | xiaomi |
R1-2304974 | UE complexity reduction | Lenovo |
R1-2305024 | Discussion on Rel-18 RedCap UE | NEC |
R1-2305046 | On eRedCap complexity reduction | Sony |
R1-2305105 | Discussion on further reduced UE complexity | CMCC |
R1-2305142 | Discussion on further UE complexity reduction for eRedCap | LG Electronics |
R1-2305158 | Considerations for further UE complexity reduction | Sierra Wireless. S.A. |
R1-2305254 | Further RedCap UE complexity reduction | Apple |
R1-2305287 | UE complexity reduction for eRedCap | Panasonic |
R1-2305308 | Discussion on complexity reduction for eRedCap UE | Sharp |
R1-2305348 | UE complexity reduction for eRedCap | Qualcomm Incorporated |
R1-2305449 | Further consideration on reduced UE complexity | OPPO |
R1-2305525 | Further UE complexity reduction for eRedCap | Samsung |
R1-2305567 | Discussion on UE complexity reduction | DENSO CORPORATION |
R1-2305607 | Discussion on further UE complexity reduction for eRedCap | NTT DOCOMO, INC. |
R1-2305647 | On eRedCap UE complexity reduction | MediaTek Inc. |
R1-2305709 | Discussion on UE complexity reduction | Transsion Holdings |
R1-2305853 | On further complexity reduction of NR UE | Nordic Semiconductor ASA |
R1-2305868 | Considerations for Rel-18 eRedCap UE complexity reduction | Sequans Communications |
R1-2305956 | FL summary #1 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2305957 | FL summary #2 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2305958 | FL summary #3 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2305959 | FL summary #4 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2306262 | Sorted RAN1 agreements for Rel-18 network energy savings post 113 | Rapporteur (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2304357 | Spatial and Power Adaptations for Network Energy Savings | FUTUREWEI |
R1-2304406 | Techniques in spatial and power domains | Nokia, Nokia Shanghai Bell |
R1-2304492 | Discussions on NES techniques in spatial and power domain | vivo |
R1-2304527 | Discussion on NES techniques in spatial and power domains | ZTE, Sanechips |
R1-2304570 | Discussion on NES techniques in spatial and power domains | Spreadtrum Communications |
R1-2304644 | CSI enhancements for network energy saving | Huawei, HiSilicon |
R1-2304743 | Network Energy Saving techniques in spatial and power domain | CATT |
R1-2304772 | Discussion on NW energy saving techniques in spatial and power domains | Fujitsu |
R1-2304810 | Discussion on NWES techniques in spatial and power domain | Intel Corporation |
R1-2304848 | Network Energy Saving in Spatial and Power Domain | |
R1-2304861 | Discussion on the spatial and power techniques for NES | China Telecom |
R1-2304913 | Discussion on techniques in spatial and power domains | xiaomi |
R1-2304946 | Network energy savings techniques in spatial domain | AT&T |
R1-2305071 | Discussion on network energy saving techniques in spatial and power domains | NEC |
R1-2305106 | Discussion on spatial and power domains enhancements for network energy saving | CMCC |
R1-2305143 | Discussion on NES techniques in spatial and power domains | LG Electronics |
R1-2305176 | Discussion on techniques in spatial and power domains | InterDigital, Inc. |
R1-2305209 | Network energy saving techniques in spatial and power domains | Lenovo |
R1-2305255 | Discussion on spatial and power domain enhancements to support network energy saving | Apple |
R1-2305349 | Techniques in spatial and power domains | Qualcomm Incorporated |
R1-2305432 | Discussion on techniques in spatial and power domains | OPPO |
R1-2305526 | Techniques in spatial and power domains | Samsung |
R1-2305551 | Discussion on spatial/power domain adaptation | ASUSTeK |
R1-2305552 | On network energy saving techniques in spatial and power domains | KT Corp. |
R1-2305573 | NW energy saving techniques in spatial and power domains | Ericsson |
R1-2305608 | Discussion on spatial and power domain enhancements for NW energy savings | NTT DOCOMO, INC. |
R1-2305676 | On NW energy saving techniques in spatial and power domains | MediaTek Inc. |
R1-2305710 | Discussion of NES techniques in spatial domain and power domain | Transsion Holdings |
R1-2305765 | Spatial and power domain adaptation for network energy saving | Panasonic |
R1-2305773 | Discussion on techniques in spatial and power domains | ITRI |
R1-2305780 | Discussion on NES for signaling of spatial adaptation | FGI |
R1-2305798 | Discussion on NES techniques in spatial and power domains | ETRI |
R1-2305867 | Spatial Domain Adaptation for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2305904 | Discussion on spatial and power adaptations for network energy savings | CEWiT |
R1-2306011 | Discussion on NES techniques in spatial and power domains | ZTE, Sanechips |
R1-2306030 | FL summary#1 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2306031 | FL summary#2 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2306032 | FL summary#3 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2306033 | FL summary#4 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2306034 | Final FL summary for SD and PD adaptation for R18 NES | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2304358 | Cell DTX/DRX for NES | FUTUREWEI |
R1-2304407 | Enhancements on cell DTX/DRX mechanism | Nokia, Nokia Shanghai Bell |
R1-2304493 | Discussions on enhancements on cell DTX/DRX mechanism | vivo |
R1-2304528 | Discussion on cell DTX/DRX | ZTE, Sanechips |
R1-2304571 | Discussion on enhancements on cell DTXDRX mechanism | Spreadtrum Communications |
R1-2304645 | Cell DTX/DRX mechanism for network energy saving | Huawei, HiSilicon |
R1-2304744 | DTX/DRX for network Energy Saving | CATT |
R1-2304773 | Discussion on cell DTX/DRX mechanism | Fujitsu |
R1-2304811 | Discussion on enhancements on cell DTX/DRX mechanism | Intel Corporation |
R1-2304849 | Network Energy Saving on Cell DTX and DRX | |
R1-2304862 | Discussion on the Cell-DTX/DRX | China Telecom |
R1-2304914 | Discussions on cell DTX-DRX for network energy saving | xiaomi |
R1-2305073 | Cell DTX/DRX Configuration for Network Energy Saving | NEC |
R1-2305107 | Discussion on cell DTX DRX enhancements | CMCC |
R1-2305144 | Discussion on cell DTX/DRX mechanism | LG Electronics |
R1-2305181 | Discussion on enhancements on cell DTX/DRX mechanism | InterDigital, Inc. |
R1-2305210 | Enhancements on cell DTX/DRX mechanism | Lenovo |
R1-2305256 | Discussion on cell DTX/DRX enhancements | Apple |
R1-2305350 | Enhancements on cell DTX and DRX mechanism | Qualcomm Incorporated |
R1-2305433 | Discussion on enhancements on cell DTX/DRX mechanism | OPPO |
R1-2305527 | Enhancements on cell DTX/DRX mechanism | Samsung |
R1-2305553 | Discussion on cell DTX/DRX | ASUSTeK |
R1-2305574 | RAN1 aspects of cell DTX/DRX | Ericsson |
R1-2305609 | Discussion on enhancements on Cell DTX/DRX mechanism | NTT DOCOMO, INC. |
R1-2305677 | On NW energy saving enhancements for cell DTX/DRX mechanism | MediaTek Inc. |
R1-2305711 | Discussion on Enhancement on cell DTX DRX mechanism | Transsion Holdings |
R1-2305766 | Cell DTX/DRX enhancement for network energy saving | Panasonic |
R1-2305774 | Discussion on potential enhancements on cell DTX/DRX mechanism for NR | ITRI |
R1-2305799 | Discussion on cell DTX/DRX mechanism | ETRI |
R1-2305874 | Signaling and Reliability for Cell DTX and DRX | Fraunhofer IIS, Fraunhofer HHI |
R1-2305905 | Discussion on cell DTX/DRX mechanism for network energy saving | CEWiT |
R1-2306006 | Summary of issues for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306007 | Discussion Summary #1 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306110 | Discussion Summary #2 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306111 | Discussion Summary #3 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306169 | Draft reply LS on cell DTX/DRX activation/deactivation | Moderators (Huawei, Intel) |
R1-2306172 | Discussion Summary #4 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306173 | Discussion Summary #5 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2306246 | Reply LS on cell DTX/DRX activation/deactivation | RAN1, Huawei, Intel |
TDoc | Title | Source |
---|---|---|
R1-2304494 | Draft CR on PDCCH monitoring resumption after NACK | vivo, MediaTek, Ericsson, Xiaomi, ZTE, Sanechips, China Telecom, China Unicom, Qualcomm, LGE, Huawei, HiSilicon, Google, Meta, Apple |
R1-2305257 | Discussion on PDCCH monitoring resumption after UL NACK | Apple |
R1-2305864 | Draft CR for Introducing PDCCH monitoring resumption after UL NACK | Nokia, Nokia Shanghai Bell |
R1-2305865 | Work Plan for Rel-18 WI on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL) |
TDoc | Title | Source |
---|---|---|
R1-2304354 | XR-specific capacity enhancements | FUTUREWEI |
R1-2304384 | Discussions on XR-specific capacity enhancements | New H3C Technologies Co., Ltd. |
R1-2304413 | Capacity Enhancements for XR | Ericsson |
R1-2304495 | Discussion on XR specific capacity enhancements | vivo |
R1-2304529 | Discussion on XR specific capacity enhancements | ZTE, Sanechips |
R1-2304572 | Discussion on XR-specific capacity enhancements | Spreadtrum Communications |
R1-2304617 | Discussion on XR capacity enhancement techniques | Panasonic |
R1-2304665 | Discussion on CG enhancements for XR capacity | Huawei, HiSilicon |
R1-2304745 | Design of Multiple CG Occasions and unused CG occasion feedback | CATT |
R1-2304915 | Discussion on XR-specific capacity enhancements | xiaomi |
R1-2304980 | Discussion on XR-specific capacity enhancements | Honor |
R1-2304981 | Discussion on XR-specific capacity enhancements | DENSO CORPORATION |
R1-2304993 | Discussion on XR-specific capacity enhancements | NEC |
R1-2305022 | Discussion on XR specific capacity enhancements | CAICT |
R1-2305047 | On XR-specific capacity enhancements techniques | Sony |
R1-2305074 | On XR-specific capacity enhancements techniques | Google Inc. |
R1-2305108 | Discussion on XR-specific capacity enhancements | CMCC |
R1-2305135 | XR-specific capacity enhancements techniques | TCL Communication Ltd. |
R1-2305145 | Discussion on XR-specific capacity enhancements | LG Electronics |
R1-2305175 | Discussion on XR-specific capacity enhancements | InterDigital, Inc. |
R1-2305196 | Remaining issues on XR-specific capacity enhancements | Sharp |
R1-2305211 | XR-related CG Enhancements | Lenovo |
R1-2305258 | XR-specific capacity enhancements | Apple |
R1-2305351 | Capacity Enhancement Techniques for XR | Qualcomm Incorporated |
R1-2305468 | Discussion on XR specific capacity enhancements | OPPO |
R1-2305528 | Capacity enhancements for XR | Samsung |
R1-2305554 | On XR-specific capacity enhancements | KT Corp. |
R1-2305610 | Discussion on XR-specific capacity enhancements | NTT DOCOMO, INC. |
R1-2305663 | On XR capacity enhancements | MediaTek Inc. |
R1-2305781 | Discussion on XR-specific capacity enhancements | FGI |
R1-2305863 | XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
R1-2306086 | Moderator Summary#1 - XR Specific Enhancements | Moderator (Ericsson) |
R1-2306087 | Moderator Summary#2 - XR Specific Enhancements | Moderator (Ericsson) |
R1-2306088 | Moderator Summary#3 - XR Specific Enhancements | Moderator (Ericsson) |
R1-2306089 | Moderator Summary#4 - XR Specific Enhancements | Moderator (Ericsson) |
R1-2306232 | [Draft] LS on XR capacity enhancements | Moderator (Ericsson) |
R1-2306233 | LS on XR capacity enhancements | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2304615 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
R1-2305851 | Initial input on RRC parameters for Rel-18 IoT NTN enhancements | Rapporteur (MediaTek Inc.) |
R1-2306004 | Initial input on higher layer parameters for Rel-18 NR NTN | Rapporteur (Thales) |
R1-2306005 | RAN1 agreements for Rel-18 WI on NR NTN enhancements | Rapporteur (Thales) |
R1-2306150 | Session notes for 9.9 (NTN (Non-Terrestrial Networks) enhancements) | Ad-Hoc Chair (Huawei) |
R1-2306151 | Draft reply LS on RACH-less Handover | Moderator (Samsung) |
R1-2306152 | Moderator summary on reply LS on RACH-less handover | Moderator (Samsung) |
R1-2306201 | FL summary on RAN2 LS reply on unchanged PCI | Moderator (CATT) |
R1-2306209 | Draft reply LS on unchanged PCI | CATT |
R1-2306210 | Reply LS on unchanged PCI | RAN1, CATT |
R1-2306217 | Reply LS on RACH-less Handover | RAN1, Samsung |
R1-2306250 | RRC parameters for Rel-18 IoT NTN enhancements | Rapporteur (MediaTek Inc.) |
R1-2306253 | Summary of offline discussion on RRC parameters for Rel-18 NR NTN enhancements | Moderator (Thales) |
R1-2306264 | RAN1 agreements for Rel-18 WI on NR NTN enhancements up to RAN1#113 | WI rapporteur (Thales) |
R1-2306272 | RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#113 | Moderator (MediaTek) |
R1-2306273 | RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#113 | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2304408 | Coverage enhancements for NR NTN | Quectel |
R1-2304434 | Coverage enhancements for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2304496 | Discussions on remaining issues of coverage enhancements in NR NTN | vivo |
R1-2304573 | Discussion on coverage enhancements for NTN | Spreadtrum Communications |
R1-2304632 | Discussion on coverage enhancement for NR NTN | Huawei, HiSilicon |
R1-2304678 | Discussion on coverage enhancements for NR NTN | CCU, NTPU |
R1-2304751 | Further discussion on UL coverage enhancement for NR NTN | CATT |
R1-2304815 | On coverage enhancement for NR NTN | Intel Corporation |
R1-2304863 | Discussion on coverage enhancement for NR NTN | China Telecom |
R1-2304916 | Discussion on coverage enhancement for NR-NTN | xiaomi |
R1-2304920 | Discussion on coverage enhancement for NR NTN | Baicells |
R1-2304965 | Discussion on coverage enhancement for NR NTN | Hyundai Motor Company |
R1-2305006 | On coverage enhancements for NR NTN | Ericsson |
R1-2305068 | Coverage enhancement for NR NTN | NEC |
R1-2305109 | Discussion on coverage enhancement for NR NTN | CMCC |
R1-2305212 | Coverage enhancements for NR NTN | Lenovo |
R1-2305259 | Coverage Enhancement for NR NTN | Apple |
R1-2305352 | Coverage enhancements for NR NTN | Qualcomm Incorporated |
R1-2305390 | Discussion on coverage enhancement for NR NTN | LG Electronics |
R1-2305436 | Discussion on coverage enhancement for NR NTN | OPPO |
R1-2305529 | On coverage enhancement for NR NTN | Samsung |
R1-2305556 | Discussion on coverage enhancement for NTN | ZTE |
R1-2305611 | Discussion on coverage enhancement for NR NTN | NTT DOCOMO, INC. |
R1-2305640 | UL coverage enhancements | MediaTek Inc. |
R1-2305699 | Discussion on coverage enhancement for NR-NTN | Panasonic |
R1-2305782 | Discussion on coverage enhancements for NR NTN | FGI |
R1-2305800 | Discussion on coverage enhancement for NR NTN | ETRI |
R1-2305847 | Discussions on Coverage enhancement for NR NTN | Sharp |
R1-2306022 | Summary #1 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
R1-2306023 | Summary #2 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
R1-2306024 | Summary #3 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
R1-2306085 | [Draft] LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK | Moderator (NTT DOCOMO, INC.) |
R1-2306105 | LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK | RAN1, NTT DOCOMO |
R1-2306228 | Summary EOM on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304435 | Aspects related to network verified UE location for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2304497 | Discussions on remaining issues of UE location verification in NR NTN | vivo |
R1-2304610 | Discussion on network verified UE location in NR NTN | THALES |
R1-2304611 | FL Summary #1: Network verified UE location for NR NTN | THALES |
R1-2304612 | FL Summary #2: Network verified UE location for NR NTN | THALES |
R1-2304613 | FL Summary #3: Network verified UE location for NR NTN | THALES |
R1-2304614 | FL Summary #4: Network verified UE location for NR NTN | THALES |
R1-2304633 | Discussion on network-verified UE location for NR NTN | Huawei, HiSilicon |
R1-2304752 | Further discussion on Network verified UE location for NR NTN | CATT |
R1-2304816 | On network verified UE location for NR NTN | Intel Corporation |
R1-2304917 | Discussion on the network verified location for NR-NTN | xiaomi |
R1-2305048 | On network verified UE location for NR NTN | Sony |
R1-2305260 | Network Verified UE Location | Apple |
R1-2305353 | Network verified UE location for NR NTN | Qualcomm Incorporated |
R1-2305391 | Discussion on network verified UE location for NR NTN | LG Electronics |
R1-2305437 | Discussion on network verified UE location for NR NTN | OPPO |
R1-2305530 | Network verified UE location for NR NTN | Samsung |
R1-2305557 | Discussion on network verified UE location for NR NTN | ZTE |
R1-2305612 | Discussion on Network verified UE location for NR NTN | NTT DOCOMO, INC. |
R1-2305641 | Network verified UE location for NR NTN | MediaTek Inc. |
R1-2305678 | Further Discussion on Network Verified UE Location | TCL Communication Ltd. |
R1-2305681 | Discussion on Network-verified UE location for NR NTN | Panasonic |
R1-2305745 | NTN NW verified UE location | Lenovo |
R1-2305801 | Discussion on Network verified UE location for NR NTN | ETRI |
R1-2305848 | Network verified UE location for Rel-18 NR NTN | Sharp |
R1-2305918 | On network verified UE location NR NTN | Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2304574 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
R1-2304634 | Discussion on disabling of HARQ feedback for IoT NTN | Huawei, HiSilicon |
R1-2304687 | Disabling of HARQ feedback for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
R1-2304753 | Discussion on remaining issues of disabling of HARQ feedback for IoT NTN | CATT |
R1-2304781 | Disabling of HARQ feedback for IoT NTN | InterDigital, Inc. |
R1-2304851 | Disabling of HARQ feedback for IoT NTN | Lenovo |
R1-2304918 | Discussion on the HARQ operation for IoT NTN | xiaomi |
R1-2304984 | Disabling of HARQ feedback for IoT NTN | NEC |
R1-2305049 | Discussion on disabling of HARQ feedback for IoT-NTN | Sony |
R1-2305110 | Discussion on disabling of HARQ feedback for IoT NTN | CMCC |
R1-2305184 | On disabling HARQ feedback for IoT NTN | Ericsson |
R1-2305261 | HARQ Feedback Disabling for IoT NTN | Apple |
R1-2305354 | Disabling HARQ Feedback for IoT-NTN | Qualcomm Incorporated |
R1-2305438 | Discussion on disabling of HARQ feedback for IoT NTN | OPPO |
R1-2305531 | Disabling of HARQ feedback for IoT NTN | Samsung |
R1-2305558 | Discussion on disabling of HARQ feedback for IoT-NTN | ZTE |
R1-2305568 | Views on Disabling of HARQ feedback for IoT NTN | Sharp |
R1-2305650 | Disabling of HARQ for IoT NTN | MediaTek Inc. |
R1-2305849 | Views on Disabling of HARQ feedback for IoT NTN | Sharp |
R1-2305909 | Disabling of HARQ feedback for IoT NTN | Nordic Semiconductor ASA |
R1-2306020 | FLS#1 on disabling of HARQ feedback for IoT NTN | Moderator(Lenovo) |
R1-2306021 | FLS#2 on disabling of HARQ feedback for IoT NTN | Moderator(Lenovo) |
R1-2306106 | Summary of discussion on LS on HARQ enhancements | Moderator (OPPO) |
R1-2306134 | Draft reply LS on HARQ Enhancements | Moderator (OPPO) |
R1-2306179 | Summary#2 of discussion on LS on HARQ enhancements | Moderator (OPPO) |
R1-2306182 | Reply LS on HARQ Enhancements | RAN1, OPPO |
R1-2306205 | [Draft] LS on NPDCCH monitoring restriction for NBIoT NTN | Moderator (Lenovo) |
R1-2306245 | LS on NPDCCH monitoring restriction for NBIoT NTN | RAN1, Lenovo |
TDoc | Title | Source |
---|---|---|
R1-2304575 | Discussion on improved GNSS operations for IoT NTN | Spreadtrum Communications |
R1-2304635 | Discussion on improved GNSS operations for IoT NTN | Huawei, HiSilicon |
R1-2304688 | Enhancements for long connections in NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
R1-2304754 | Discussion on remaining issues of improved GNSS operations for IoT NTN | CATT |
R1-2304782 | Improved GNSS operations for IoT NTN | InterDigital, Inc. |
R1-2304852 | Improved GNSS operations for IoT NTN | Lenovo |
R1-2304919 | Discussion on the improved GNSS operation for IoT NTN | xiaomi |
R1-2305069 | On Improved GNSS Operations for IoT NTN | NEC |
R1-2305111 | Discussion on improved GNSS operations for IoT NTN | CMCC |
R1-2305262 | On improved GNSS operations for IoT NTN | Apple |
R1-2305286 | Remaining issues on improved GNSS operations for IoT NTN | Sharp |
R1-2305355 | Improved GNSS Operations for IoT-NTN | Qualcomm Incorporated |
R1-2305439 | Discussion on improved GNSS operations for IoT NTN | OPPO |
R1-2305532 | Improved GNSS operations for IoT NTN | Samsung |
R1-2305559 | Discussion on improved GNSS operation for IoT-NTN | ZTE |
R1-2305651 | Improved GNSS operations for IoT NTN | MediaTek Inc. |
R1-2305910 | Improved GNSS operations for IoT NTN | Nordic Semiconductor ASA |
R1-2305916 | On improved GNSS operation in IoT NTN | Ericsson |
R1-2305998 | Feature lead summary#1 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
R1-2305999 | Feature lead summary#2 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
R1-2306202 | Feature lead summary#3 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2306147 | Session notes for 9.10 (Further NR mobility enhancements) | Ad-Hoc Chair (CMCC) |
R1-2306258 | DRAFT LS on beam application time, contents of cell switch command, TCI state activation and UE based TA measurement for LTM | Fujitsu, MediaTek, CATT |
R1-2306259 | LS on beam application time, contents of cell switch command, TCI state activation and UE based TA measurement for LTM | RAN1, Fujitsu, MediaTek, CATT |
TDoc | Title | Source |
---|---|---|
R1-2304352 | L1 enhancements for inter-cell beam management | FUTUREWEI |
R1-2304399 | L1 enhancements for inter-cell beam management | ZTE |
R1-2304498 | Discussion on L1 enhancements for L1/L2 mobility | vivo |
R1-2304576 | Discussion on L1 enhancements for inter-cell beam management | Spreadtrum Communications |
R1-2304588 | FL plan on L1 enhancements for LTM at RAN1#113 | Moderator (Fujitsu, MediaTek) |
R1-2304659 | L1 enhancements for inter-cell beam management | Huawei, HiSilicon |
R1-2304712 | Further discussion on L1 enhancements for inter-cell beam management | CATT |
R1-2304774 | Views on L1 enhancements for inter-cell beam management | Fujitsu |
R1-2304785 | L1 enhancements to inter-cell beam management | Ericsson |
R1-2304823 | L1 Enhancements for Inter-cell Beam Management | Intel Corporation |
R1-2304880 | Discussion on L1 enhancements for inter-cell beam management | xiaomi |
R1-2304957 | L1 enhancements for inter-cell beam management | Lenovo |
R1-2305007 | L1 enhancements for inter-cell beam management | KDDI Corporation |
R1-2305010 | Discussion on L1 enhancements for inter-cell beam management | |
R1-2305050 | L1 enhancements for inter-cell beam management | Sony |
R1-2305072 | Discussion on L1 enhancements for inter-cell beam management | NEC |
R1-2305112 | Discussion on L1 enhancements for inter-cell beam management | CMCC |
R1-2305128 | FL summary 1 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2305130 | FL summary 2 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2305156 | Layer-1 Enhancements for L1/L2-triggered Mobility | Nokia, Nokia Shanghai Bell |
R1-2305263 | L1 enhancements to inter-cell beam management | Apple |
R1-2305302 | Enhancements on inter-cell beam management for mobility | LG Electronics |
R1-2305356 | L1 Enhancements for Inter-Cell Beam Management | Qualcomm Incorporated |
R1-2305418 | Discussions on Inter-cell beam management enhancement | OPPO |
R1-2305480 | Discussion on multi-TA indication for LTM | ASUSTEK COMPUTER |
R1-2305533 | On L1 enhancements for inter-cell beam management | Samsung |
R1-2305613 | Discussion on L1 enhancements for inter-cell mobility | NTT DOCOMO, INC. |
R1-2305667 | L1 enhancements for inter-cell beam management | MediaTek Inc. |
R1-2305693 | Discussion on L1 enhancements for L1L2-triggered mobility | Panasonic |
R1-2305712 | Discussion on measurement enhancement of L1L2 triggered mobility | Transsion Holdings |
R1-2305783 | Discussion on L1 enhancements for inter-cell beam management | FGI |
R1-2305856 | Discussion on L1 enhancements for inter-cell beam management | InterDigital, Inc. |
R1-2306167 | FL summary 3 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2306168 | FL summary 4 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2306260 | Final FL summary on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2304353 | Discussion on UE based RACH-less TA determination | FUTUREWEI |
R1-2304388 | UL Timing management to reduce handover latency | MediaTek Inc. |
R1-2304400 | Enhancements on TA management to reduce latency | ZTE |
R1-2304499 | Discussion on TA management for L1/L2 mobility | vivo |
R1-2304577 | Discussion on timing advance management to reduce latency | Spreadtrum Communications |
R1-2304660 | Timing advance management to reduce latency | Huawei, HiSilicon |
R1-2304713 | Discussion on time advance management to reduce latency | CATT |
R1-2304786 | Timing advance management for L1/L2 Mobility | Ericsson |
R1-2304822 | On Timing Advance Management | Intel Corporation |
R1-2304881 | Discussion on Timing advance management | xiaomi |
R1-2304958 | Timing advancement management for L1L2 mobility | Lenovo |
R1-2305011 | Discussion on timing advance management to reduce latency | |
R1-2305023 | Discussion on timing advance management to reduce latency | CAICT |
R1-2305113 | Discussion on timing advance management to reduce latency | CMCC |
R1-2305157 | Timing Advance Management for L1/L2-triggered Mobility | Nokia, Nokia Shanghai Bell |
R1-2305264 | Timing advance management for L1/L2 triggered mobility | Apple |
R1-2305303 | Enhancements on TA management for mobility | LG Electronics |
R1-2305357 | TA management to reduce latency for L1/L2 based mobility | Qualcomm Incorporated |
R1-2305419 | Discussions on Timing Advance Management | OPPO |
R1-2305534 | Candidate cell TA acquisition for NR L1/L2 mobility enhancement | Samsung |
R1-2305614 | Timing advance enhancement for inter-cell mobility | NTT DOCOMO, INC. |
R1-2305645 | UL Timing management to reduce handover latency | MediaTek Inc. |
R1-2305713 | Discussion on TA management for L1/L2 mobility | Transsion Holdings |
R1-2305775 | Discussion on TA management for mobility enhancement | ITRI |
R1-2305784 | Discussion on TA management for LTM | FGI |
R1-2305857 | Discussion on timing advance management | InterDigital, Inc. |
R1-2305962 | Candidate cell TA acquisition for NR L1/L2 mobility enhancement | Samsung |
R1-2306035 | Moderator summary on Timing advance management for LTM: Round 1 | Moderator (CATT) |
R1-2306123 | Moderator summary on Timing advance management for LTM: Round 2 | Moderator (CATT) |
R1-2306158 | Moderator summary on Timing advance management for LTM: Round 3 | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2305954 | TR 38.869 v020: Study on low-power wake up signal and receiver for NR | Rapporteur (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2304414 | Low power WUS Evaluation Methodology | Nokia, Nokia Shanghai Bell |
R1-2304441 | Discussion on evaluation on LP-WUS | InterDigital, Inc. |
R1-2304500 | Evaluation methodologies and results for LP-WUS/WUR | vivo |
R1-2304530 | Evaluation on LP-WUS | ZTE, Sanechips |
R1-2304578 | Discussion on evaluation on low power WUS | Spreadtrum Communications |
R1-2304618 | Evaluations for LP-WUS | Huawei, HiSilicon |
R1-2304714 | Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR | CATT |
R1-2304797 | Evaluation of LP-WUS and Performance Results | FUTUREWEI |
R1-2304803 | Evaluations on LP WUS | Intel Corporation |
R1-2304882 | Evaluation on low power WUS | xiaomi |
R1-2305051 | Evaluation of low power WUS | Sony |
R1-2305146 | Discussion on evaluation for LP-WUS | LG Electronics |
R1-2305265 | On performance evaluation for low power wake-up signal | Apple |
R1-2305358 | Evaluation methodology for LP-WUS | Qualcomm Incorporated |
R1-2305450 | Evaluation for lower power wake-up signal | OPPO |
R1-2305535 | Evaluation on LP-WUS/WUR | Samsung |
R1-2305575 | Low power WUS evaluations | Ericsson |
R1-2305652 | Evaluation on low power WUS | MediaTek Inc. |
R1-2305952 | FL summary #1 of evaluation methodologies on LP-WUS/WUR | Moderator (vivo) |
R1-2305953 | Summary of evaluation results #1 | Moderator (vivo) |
R1-2305963 | Discussion on evaluation on low power WUS | Spreadtrum Communications |
R1-2305974 | Low power WUS evaluations | Ericsson |
R1-2305976 | Low power WUS Evaluation Methodology | Nokia, Nokia Shanghai Bell |
R1-2305983 | Evaluation methodologies and results for LP-WUS/WUR | vivo |
R1-2306012 | On performance evaluation for low power wake-up signal | Apple |
R1-2306077 | Evaluation methodology for LP-WUS | Qualcomm Incorporated |
R1-2306129 | Evaluation methodologies and results for LP-WUS/WUR | vivo |
R1-2306195 | FL summary #2 of evaluation methodologies on LP-WUS/WUR | Moderator (vivo) |
R1-2306251 | FL Summary (final) of evaluation results for RAN1#113 on LP-WUS/WUR | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2304355 | Discussion on LP-WUS Receiver Architectures | FUTUREWEI |
R1-2304415 | Low Power WUS receiver architectures | Nokia, Nokia Shanghai Bell |
R1-2304442 | Discussion on LP-WUS receiver architectures | InterDigital, Inc. |
R1-2304501 | Remaining issues on low power wake-up receiver architecture | vivo |
R1-2304531 | LP-WUS receiver architectures | ZTE, Sanechips |
R1-2304579 | Discussion on L1 signal design and procedure for low power WUS | Spreadtrum Communications |
R1-2304619 | Discussion on architecture of LP-WUS receiver | Huawei, HiSilicon |
R1-2304715 | Low-Power WUS receiver Architectures and its performance | CATT |
R1-2305266 | On low power wake-up receiver architectures | Apple |
R1-2305267 | Summary #1 on LP WUR architectures | Apple |
R1-2305268 | Summary #2 on LP WUR architectures | Apple |
R1-2305269 | Summary #3 on LP WUR architectures | Apple |
R1-2305359 | Receiver architecture for LP-WUS | Qualcomm Incorporated |
R1-2305451 | Discussion on low power WUS receiver | OPPO |
R1-2305536 | Receiver architecture for LP-WUS | Samsung |
R1-2305576 | Low power WUS receiver architectures | Ericsson |
R1-2305653 | Low power WUS receiver architectures | MediaTek Inc. |
R1-2305767 | Discussion on low power wake up receiver architectures | Panasonic |
R1-2306125 | [Draft] Reply LS to RAN4 on LP WUR architectures | Moderator (Apple) |
R1-2306126 | Reply LS to RAN4 on LP WUR architectures | RAN1, Apple |
R1-2306204 | Summary #4 on LP WUR architectures | Apple |
TDoc | Title | Source |
---|---|---|
R1-2304356 | LP-WUS Physical Signal Design and Performance | FUTUREWEI |
R1-2304417 | L1 signal design and procedures for low power WUS | Nokia, Nokia Shanghai Bell |
R1-2304443 | Discussion on L1 signal design and procedure for LP-WUS | InterDigital, Inc. |
R1-2304502 | Discussion on physical signal and procedure for low power WUS | vivo |
R1-2304520 | L1 signal design and procedure for low power WUS | TCL Communication Ltd. |
R1-2304532 | LP-WUS design and related procedure | ZTE, Sanechips |
R1-2304620 | Further details on signal design and procedure for LP-WUS | Huawei, HiSilicon |
R1-2304716 | Physical layer signals/procedures and higher layer protocol for Low-Power WUR | CATT |
R1-2304804 | Discussions on L1 signal design and procedure for LP-WUS | Intel Corporation |
R1-2304864 | Discussion on signal design and procedure for LP-WUS | China Telecom |
R1-2304883 | Discussions on L1 signal design and procedure for low power WUS | xiaomi |
R1-2304994 | Discussion on L1 signal design and procedure for LP-WUS | NEC |
R1-2305013 | Discussion on L1 signal design and procedure for low power WUS | EURECOM |
R1-2305052 | On L1 signal design and procedures for low power WUS | Sony |
R1-2305055 | On L1 signal design and procedure for LP-WUS | Vodafone |
R1-2305114 | Discussion on L1 signal design and procedure for LP-WUS | CMCC |
R1-2305147 | Discussion on L1 signal design and procedure for LP-WUS | LG Electronics |
R1-2305270 | On the L1 signal design and procedures for low power wake-up signal | Apple |
R1-2305309 | Discussion on L1 signal design and procedure for low power WUS | Sharp |
R1-2305360 | L1 signal design and procedures for LP-WUR | Qualcomm Incorporated |
R1-2305452 | Design consideration on lower power wake-up signal and procedure | OPPO |
R1-2305537 | Signal design and procedure for LP-WUS | Samsung |
R1-2305577 | L1 signal design and procedure for low power WUS | Ericsson |
R1-2305615 | Discussion on L1 signal design and procedure for low power WUS | NTT DOCOMO, INC. |
R1-2305654 | L1 signal design and procedure for low power WUS | MediaTek Inc. |
R1-2305768 | Discussion on low power wake up signal design | Panasonic |
R1-2305854 | On LP-WUS signal design | Nordic Semiconductor ASA |
R1-2305919 | Discussion on the L1 signal design and procedure for low power WUS | Lenovo |
R1-2305965 | Design consideration on lower power wake-up signal and procedure | OPPO |
R1-2306013 | Discussion on physical signal and procedure for low power WUS | vivo |
R1-2306084 | Discussion on L1 signal design and procedure for LP-WUS | InterDigital, Inc. |
R1-2306108 | Summary#1 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2306133 | Summary#2 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2306181 | Summary#3 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2306234 | Summary#4 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
TDoc | Title | Source |
---|---|---|
R1-2306148 | Session notes for 9.12 (Further NR coverage enhancements) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2304383 | Discussions on PRACH coverage enhancements | New H3C Technologies Co., Ltd. |
R1-2304503 | Discussions on remaining issues of PRACH coverage enhancements | vivo |
R1-2304580 | Discussion on PRACH coverage enhancements | Spreadtrum Communications |
R1-2304598 | Discussion on PRACH coverage enhancements | ZTE |
R1-2304649 | Discussion on PRACH coverage enhancements | Huawei, HiSilicon |
R1-2304717 | PRACH coverage enhancements | CATT |
R1-2304775 | Discussion on PRACH coverage enhancements | Fujitsu |
R1-2304807 | Discussions on PRACH coverage enhancement | Intel Corporation |
R1-2304865 | Discussion on PRACH coverage enhancement | China Telecom |
R1-2304884 | Discussion on PRACH coverage enhancements | xiaomi |
R1-2304975 | PRACH coverage enhancements | Lenovo |
R1-2304999 | Discussion on PRACH coverage enhancement | NEC |
R1-2305053 | PRACH Coverage Enhancement using Multiple PRACH Transmissions | Sony |
R1-2305115 | Discussion on PRACH coverage enhancements | CMCC |
R1-2305136 | PRACH coverage enhancements | Nokia, Nokia Shanghai Bell |
R1-2305139 | PRACH coverage enhancements | TCL Communication Ltd. |
R1-2305151 | Discussion on PRACH coverage enhancements | Quectel |
R1-2305167 | PRACH coverage enhancements | Charter Communications, Inc |
R1-2305190 | PRACH coverage enhancements | Charter Communications, Inc |
R1-2305191 | PRACH coverage enhancements | Charter Communications, Inc |
R1-2305192 | PRACH coverage enhancements | Charter Communications, Inc |
R1-2305271 | Discussion on PRACH coverage enhancement | Apple |
R1-2305306 | Discussion on PRACH coverage enhancements | Panasonic |
R1-2305361 | PRACH Coverage Enhancements | Qualcomm Incorporated |
R1-2305392 | Discussion on PRACH repeated transmission for NR coverage enhancement | LG Electronics |
R1-2305453 | PRACH coverage enhancements | OPPO |
R1-2305483 | Discussion on PRACH coverage enhancement | Ericsson |
R1-2305538 | PRACH coverage enhancements | Samsung |
R1-2305569 | Views on multiple PRACH transmission for coverage enhancement | Sharp |
R1-2305616 | Discussion on PRACH coverage enhancements | NTT DOCOMO, INC. |
R1-2305664 | On PRACH coverage enhancements | MediaTek Inc. |
R1-2305687 | Discussion on PRACH coverage enhancement | Mavenir |
R1-2305802 | PRACH coverage enhancements | ETRI |
R1-2305858 | Discussion on PRACH coverage enhancements | InterDigital, Inc. |
R1-2306008 | Discussion on PRACH coverage enhancement | Ericsson |
R1-2306036 | FL Summary#1 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2306037 | FL Summary#2 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2306038 | FL Summary#3 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2306039 | FL Summary#4 on PRACH coverage enhancements | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R1-2304504 | Discussions on remaining issues of power domain enhancements | vivo |
R1-2304581 | Discussion on power domain enhancements | Spreadtrum Communications |
R1-2304599 | Discussion on power domain enhancements | ZTE |
R1-2304650 | Discussion on coverage enhancement in power domain | Huawei, HiSilicon |
R1-2304718 | Discussion on MPR/PAR reduction enhancements | CATT |
R1-2304776 | Discussion on Power domain enhancements | Fujitsu |
R1-2304808 | Discussions on power domain enhancement | Intel Corporation |
R1-2304866 | Discussion on power domain enhancements | China Telecom |
R1-2304885 | Discussion on power domain enhancements | xiaomi |
R1-2304976 | Power domain enhancements | Lenovo |
R1-2305116 | Discussion on power domain enhancements | CMCC |
R1-2305137 | RAN1 impacts for power domain enhancements | Nokia, Nokia Shanghai Bell |
R1-2305272 | Discussion on power domain coverage enhancement | Apple |
R1-2305307 | Discussion on power domain enhancements | Panasonic |
R1-2305362 | Power-domain enhancements | Qualcomm Incorporated |
R1-2305393 | Discussion on Power Domain Enhancements | LG Electronics |
R1-2305454 | The study of power domain enhancements | OPPO |
R1-2305484 | Power Domain Enhancement Schemes and Performance | Ericsson |
R1-2305539 | Power domain enhancements | Samsung |
R1-2305617 | Discussion on power domain enhancements | NTT DOCOMO, INC. |
R1-2305665 | Discussion on power domain enhancements | MediaTek Inc. |
R1-2305808 | DMRS design for power domain enhancements | Indian Institute of Tech (H) |
R1-2305850 | Power domain enhancements for Rel-18 CovEnh | Sharp |
R1-2305859 | Discussion on power domain enhancements | InterDigital, Inc. |
R1-2305913 | Discussion on power domain enhancements | Google Inc. |
R1-2305977 | FL summary of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2305978 | FL summary #2 of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2305979 | FL summary #3 of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2305980 | Final FL summary of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2306127 | FL summary #4 of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R1-2304505 | Discussions on remaining issues of dynamic waveform switching | vivo |
R1-2304582 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Spreadtrum Communications |
R1-2304600 | Discussion on dynamic waveform switching | ZTE |
R1-2304651 | Discussion on dynamic waveform switching for coverage enhancement | Huawei, HiSilicon |
R1-2304719 | Dynamic switching between DFT-S-OFDM and CP-OFDM | CATT |
R1-2304799 | Dynamic switching between DFT-S-OFDM and CP-OFDM | InterDigital, Inc. |
R1-2304809 | Dynamic switching between DFT-S-OFDM and CP-OFDM waveform | Intel Corporation |
R1-2304867 | Discussion on dynamic waveform switching between DFT-s-OFDM and CP-OFDM | China Telecom |
R1-2304870 | Discussion on dynamic waveform switching | Panasonic |
R1-2304886 | Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM | xiaomi |
R1-2304977 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Lenovo |
R1-2305000 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NEC |
R1-2305054 | Considerations on dynamic waveform switching for various PUSCH types | Sony |
R1-2305117 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | CMCC |
R1-2305138 | Dynamic switching between DFT-s-OFDM and CP-OFDM | Nokia, Nokia Shanghai Bell |
R1-2305273 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Apple |
R1-2305363 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Qualcomm Incorporated |
R1-2305394 | Discussion on dynamic waveform switching for NR coverage enhancement | LG Electronics |
R1-2305455 | Considerations on dynamic switching between DFT-S-OFDM and CP-OFDM | OPPO |
R1-2305477 | Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2305478 | Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2305479 | Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2305485 | Discussion on Dynamic UL Waveform Switching | Ericsson |
R1-2305540 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Samsung |
R1-2305570 | Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh | Sharp |
R1-2305618 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NTT DOCOMO, INC. |
R1-2305666 | Dynamic switching between waveforms | MediaTek Inc. |
R1-2305682 | Discussion on solutions for NR dynamic switching between DFT-S-OFDM and CP-OFDM | Mavenir |
R1-2305714 | Discussion of dynamic switching between DFT-S-OFDM and CP-OFDM | Transsion Holdings |
R1-2305803 | Dynamic switching between DFT-S-OFDM and CP-OFDM | ETRI |
R1-2305914 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Google Inc. |
R1-2306239 | Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2306255 | Summary #5 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
TDoc | Title | Source |
---|---|---|
R1-2306149 | Session notes for 9.13 (NR support for dedicated spectrum less than 5MHz for FR1) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2304360 | Discussion on less than 5 MHz dedicated spectrum | FUTUREWEI |
R1-2304506 | Discussion on NR support for dedicated spectrum less than 5MHz | vivo |
R1-2304583 | Discussion on enhancements to operate NR on dedicated spectrum | Spreadtrum Communications |
R1-2304601 | Discussion on Enhancements to operate NR on dedicated spectrum less than 5 MHz | ZTE |
R1-2304630 | Discussion on dedicated spectrum less than 5 MHz for FR1 | Huawei, HiSilicon |
R1-2304887 | Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz | xiaomi |
R1-2304978 | Enhancements to operate NR on dedicated spectrum less than 5 MHz | Lenovo |
R1-2305026 | NR support for below 5 MHz BW | Nokia, Nokia Shanghai Bell |
R1-2305148 | Discussion on enhancements for dedicated spectrum less than 5 MHz | LG Electronics |
R1-2305185 | NR support of spectrum less than 5MHz for FR1 | Ericsson |
R1-2305274 | NR support of spectrum less than 5MHz for FR1 | Apple |
R1-2305364 | NR support for dedicated spectrum less than 5MHz for FR1 | Qualcomm Incorporated |
R1-2305541 | Enhancements to operate NR on dedicated spectrum less than 5 MHz | Samsung |
R1-2305550 | Discussion on operation of NR on dedicated spectrum less than 5 MHz | Rakuten Mobile, Inc |
R1-2305619 | Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz | NTT DOCOMO, INC. |
R1-2305629 | Open issues of dedicated spectrum less than 5MHz for FR1 | TD Tech, Chengdu TD Tech |
R1-2305648 | On dedicated spectrum less than 5 MHz | MediaTek Inc. |
R1-2305984 | On dedicated spectrum less than 5 MHz | MediaTek Inc. |
R1-2306107 | Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2306154 | Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2306218 | Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2306240 | DRAFT Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 | Moderator (Nokia) |
R1-2306241 | Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 | RAN1, Nokia |
TDoc | Title | Source |
---|---|---|
R1-2306146 | Session notes for 9.14 (Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2304436 | Further discussion on self-evaluation methodology for 3GPP submission of IMT-2020 Satellite Radio Interface Technology | Nokia, Nokia Shanghai Bell |
R1-2304628 | Evaluation methodology of IMT-2020 satellite | Huawei, HiSilicon |
R1-2304755 | Evaluation methodology and performance consideration for IMT2020 Satellite RIT | CATT |
R1-2304759 | Consideration on IMT-2020 Satellite self-evaluation | THALES |
R1-2305365 | Further discussion on self-evaluation assumptions | Qualcomm Incorporated |
R1-2305448 | Discussion on self-evaluation methodology for IMT-2020 satellite radio interface | OPPO |
R1-2305560 | Discussion on the Self-Evaluation for IMT-2020 Satellite | ZTE |
R1-2305700 | Discussion on evaluation assumptions for self-evaluation of IMT-2020 satellite radio interface technology | Panasonic |
R1-2305703 | Peak data rate and peak spectral efficiency evaluation | Ericsson |
R1-2306083 | Feature lead summary #1 on evaluation methodology for IMT-2020 Satellite | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2304433 | On SRS Imbalance | InterDigital |
R1-2304602 | On PUSCH repetition type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI | ZTE, China Telecom, Sanechips |
R1-2304675 | Rel-18 TEI proposal on HARQ multiplexing on PUSCH | Huawei, HiSilicon, Ericsson, China Unicom |
R1-2304888 | Rel-18 TEI on pathloss RS for Type 1 CG PUSCH | xiaomi |
R1-2305366 | Rel-18 RAN1 TEI proposals | Qualcomm Incorporated |
R1-2305408 | TEI on the introduction of a UE capability with up to 6-layer DL MIMO | OPPO |
R1-2305628 | Summary #1 on Rel-18 TEIs | Moderator (NTT DOCOMO, INC.) |
R1-2305917 | Rel-18 TEI proposal on eCP support for NR MBS | CBN, China Telecom, China Unicom, CATT, Huawei, HiSilicon |
R1-2305964 | Rel-18 TEI proposal on eCP support for NR MBS | CBN, China Telecom, China Unicom, CATT, Huawei, HiSilicon, ZTE, Sanechips |
R1-2306138 | Moderator summary for LS on 1-symbol PRS | ZTE |
R1-2306212 | Reply LS on 1-symbol PRS | RAN1, ZTE |
R1-2306242 | Summary #2 on Rel-18 TEIs | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2306220 | Initial RAN1 UE features list for Rel-18 LTE after RAN1#113 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2306221 | Draft LS on Rel-18 RAN1 UE features list for LTE after RAN1#113 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2306222 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#113 | RAN1 (NTT DOCOMO, AT&T) |
R1-2306223 | Updated RAN1 UE features list for Rel-18 NR after RAN1#113 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2306224 | Draft LS on Rel-18 RAN1 UE features list for NR after RAN1#113 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2306225 | LS on Rel-18 RAN1 UE features list for NR after RAN1#113 | RAN1 (NTT DOCOMO, AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304401 | Discussion on UE features for NR MIMO evolution | ZTE |
R1-2304507 | Discussion on Rel-18 MIMO UE features | vivo |
R1-2304940 | Summary of UE features for NR MIMO evolution | Moderator (AT&T) |
R1-2305275 | Views on UE features for Rel-18 NR MIMO evolution | Apple |
R1-2305367 | UE features for NR MIMO evolution | Qualcomm Incorporated |
R1-2305409 | UE features for Rel-18 MIMO evolution | OPPO |
R1-2305542 | UE features for Rel-18 MIMO | Rapporteur (Samsung) |
R1-2305698 | Discussion on UE features for Rel18 MIMO | Ericsson |
R1-2305718 | Initial views on UE features for MIMO evolution | Nokia, Nokia Shanghai Bell |
R1-2305927 | UE features for NR MIMO evolution | Huawei, HiSilicon |
R1-2305955 | UE features for Rel-18 MIMO | Samsung |
R1-2306160 | Session Notes of AI 9.16.1 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304508 | Discussion on Rel-18 positioning UE features | vivo |
R1-2304666 | UE features for expanded and improved NR positioning | Huawei, HiSilicon |
R1-2304720 | Discussion on UE features for expanded and improved NR positioning | CATT |
R1-2304835 | UE features for Rel-18 positioning | Intel Corporation |
R1-2304934 | Discussion on UE feature for Rel-18 NR positioning | ZTE |
R1-2304941 | Summary of UE features for expanded and improved NR positioning | Moderator (AT&T) |
R1-2305276 | Vieww on UE features for expanded and improved NR positioning | Apple |
R1-2305368 | UE features on Expanded and improved NR Positioning | Qualcomm Incorporated |
R1-2305469 | Discussion on UE features for expanded and improved NR positioning | OPPO |
R1-2305719 | Initial views on UE features for expanded and improved NR positioning | Nokia, Nokia Shanghai Bell |
R1-2306161 | Session Notes of AI 9.16.2 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304509 | Discussion on UE feature for NCR | vivo |
R1-2304631 | Discussions on UE features for NR NCR | Huawei, HiSilicon |
R1-2304777 | Discussion on UE features for NR NCR | Fujitsu |
R1-2304800 | UE features for NCR | Intel Corporation |
R1-2304890 | Discussion on UE features for NR NCR | xiaomi |
R1-2304942 | Summary of UE features for NR NCR | Moderator (AT&T) |
R1-2305118 | Discussion on UE feature of NR NCR | CMCC |
R1-2305277 | On UE features for Rel-18 NR network-controlled repeaters | Apple |
R1-2305369 | UE features on NR NCR | Qualcomm Incorporated |
R1-2305395 | Discussion on UE features for NR NCR | LG Electronics |
R1-2305543 | UE features for NR NCR | Samsung |
R1-2305555 | Discussion on the UE feature for NCR | ZTE |
R1-2305620 | Discussion on UE features for NR NCR | NTT DOCOMO, INC. |
R1-2305717 | UE features for NCR | Ericsson |
R1-2305720 | On UE features for Network Controlled Repeaters | Nokia, Nokia Shanghai Bell |
R1-2305804 | Discussion on NCR features | ETRI |
R1-2305813 | Discussion on UE features for NR NCR | Sony |
R1-2306162 | Session Notes of AI 9.16.4 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304510 | Discussions on UE feature of NR NTN enhancements | vivo |
R1-2304667 | UE features for NR NTN enhancements | Huawei, HiSilicon |
R1-2304943 | Summary of UE features for NR NTN enhancements | Moderator (AT&T) |
R1-2305119 | Discussion on UE features for NR NTN enhancements | CMCC |
R1-2305278 | On UE Features for Rel-18 NR NTN Enhancements | Apple |
R1-2305370 | UE features on NR NTN enhancements | Qualcomm Incorporated |
R1-2305446 | Discussion on UE features for NR NTN enhancements | OPPO |
R1-2305561 | Discussion on the UE feature for NR-NTN | ZTE |
R1-2305621 | Discussion on UE features for NR NTN enhancements | NTT DOCOMO, INC. |
R1-2305721 | Initial views on UE features for NR NTN enhancements | Nokia, Nokia Shanghai Bell |
R1-2305806 | On UE features for NR NTN enhancements | Ericsson |
R1-2306163 | Session Notes of AI 9.16.5 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304511 | Discussion on UE features for Rel-18 sidelink | vivo |
R1-2304668 | UE features for NR sidelink evolution | Huawei, HiSilicon |
R1-2305279 | On UE Features for Rel-18 NR Sidelink Evolution | Apple |
R1-2305371 | UE Features for Sidelink Evolution | Qualcomm Incorporated |
R1-2305470 | Initial UE features list for Rel-18 NR sidelink evolution WI | OPPO, Huawei, HiSilicon, LG Electronics |
R1-2305622 | Discussion on UE features for NR SL evolution | NTT DOCOMO, INC. |
R1-2305697 | Discussion on UE features for NR sidelink evolution | ZTE, Sanechips |
R1-2305722 | Initial views on UE features for Sidelink evolution | Nokia, Nokia Shanghai Bell |
R1-2306183 | Session Notes for 9.16.7 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306189 | Summary on UE features for NR sidelink evolution | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304337 | Initial input on UE features for Rel-18 eRedCap | Rapporteur (Ericsson) |
R1-2304361 | Discussion on UE features for R18 RedCap | FUTUREWEI |
R1-2304512 | Discussion on UE features for R18 eRedCap | vivo |
R1-2304795 | On support of legacy features for Rel-18 eRedCap UEs | Ericsson |
R1-2305372 | UE featuers for eRedCap | Qualcomm Incorporated |
R1-2305457 | Rel-18 RedCap UE features | OPPO |
R1-2305544 | UE features for eRedcap | Samsung |
R1-2305623 | Discussion on UE features for eRedCap | NTT DOCOMO, INC. |
R1-2305662 | UE features for eRedCap | MediaTek Inc. |
R1-2305723 | Initial views on UE features for eRedCap | Nokia, Nokia Shanghai Bell |
R1-2305855 | On eRedcap features | Nordic Semiconductor ASA |
R1-2305928 | UE features for eRedCap | Huawei, HiSilicon |
R1-2306184 | Session Notes for 9.16.8 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306190 | Summary on UE features for eRedCap | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304513 | Discussion on UE features for Multi-carrier enhancements | vivo |
R1-2304584 | Discussion on UE features for multi-carrier enhancement | Spreadtrum Communications |
R1-2304603 | Discussion on UE feature for MC enhancements | ZTE |
R1-2304671 | UE features for MC enhancements | Huawei, HiSilicon |
R1-2304891 | Disucssion on UE features for MC enhancements | xiaomi |
R1-2305149 | Discussion on UE features for MC enhancements | LG Electronics |
R1-2305280 | On UE features for Rel-18 multi-carrier enhancements | Apple |
R1-2305373 | UE features for MC enhancements | Qualcomm Incorporated |
R1-2305471 | Discussion on UE features for multi-carrier enhancement | OPPO |
R1-2305545 | UE features for multi-carrier enhancements | Samsung |
R1-2305578 | UE features for MCE | Ericsson |
R1-2305624 | Discussion on UE features for Multi-carrier enhancements | NTT DOCOMO, INC. |
R1-2305661 | On UE feature discussion for Rel-18 MC enhancements | MediaTek Inc. |
R1-2305724 | On UE features for Multi-carrier Enhancements | Nokia, Nokia Shanghai Bell |
R1-2306185 | Session Notes for 9.16.9 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306191 | Summary on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304669 | UE features for IoT NTN enhancements | Huawei, HiSilicon |
R1-2304944 | Summary of UE features for IoT NTN enhancements | Moderator (AT&T) |
R1-2305281 | On UE Features for Rel-18 IoT NTN Enhancements | Apple |
R1-2305374 | UE features for IOT NTN | Qualcomm Incorporated |
R1-2305447 | Discussion on UE features for IoT NTN enhancements | OPPO |
R1-2305562 | Discussion on the UE feature for IoT-NTN | ZTE |
R1-2305725 | Initial views on UE features for IoT NTN enhancements | Nokia, Nokia Shanghai Bell |
R1-2305807 | Initial input on UE features for Rel-18 IoT NTN enhancements | Rapporteur (MediaTek Inc.) |
R1-2305809 | On UE features for IoT NTN enhancements | Ericsson |
R1-2306164 | Session Notes of AI 9.16.11 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304362 | Discussion on UE features for less than 5 MHz dedicated spectrum | FUTUREWEI |
R1-2304514 | Discussion on UE features for dedicated spectrum less than 5MHz | vivo |
R1-2304604 | Discussion on UE feature for dedicated spectrum less than 5MHz | ZTE |
R1-2305186 | Initial view on UE features for LessThan5MHzFR1 | Ericsson |
R1-2305375 | UE features for dedicated spectrum less than 5MHz | Qualcomm Incorporated |
R1-2305546 | UE features for dedicated spectrum less than 5MHz | Samsung |
R1-2305625 | Discussion on UE features for dedicated spectrum less than 5MHz | NTT DOCOMO, INC. |
R1-2305726 | Initial views on UE features for dedicated spectrum less than 5MHz | Nokia, Nokia Shanghai Bell |
R1-2305732 | Initial UE feature list for NR support for dedicated spectrum less than 5MHz | Nokia (WI Rapporteur) |
R1-2305929 | UE features for dedicated spectrum less than 5MHz | Huawei, HiSilicon |
R1-2306186 | Session Notes for 9.16.12 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306192 | Summary on UE features for dedicated spectrum less than 5MHz | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304515 | Discussion on UE features for eDSS | vivo |
R1-2304585 | Discussion on UE features for eDSS | Spreadtrum Communications |
R1-2304605 | Discussion on UE feature for eDSS | ZTE |
R1-2304672 | UE features for eDSS | Huawei, HiSilicon |
R1-2304889 | Discussion on UE features for eDSS | xiaomi |
R1-2305282 | On Rel-18 eDSS UE features | Apple |
R1-2305376 | UE features for eDSS | Qualcomm Incorporated |
R1-2305472 | Discussion on UE features for eDSS enhancement | OPPO |
R1-2305547 | UE features for eDSS | Samsung |
R1-2305579 | UE features for Rel18 DSS Enhancements | Ericsson |
R1-2305626 | Discussion on UE features for eDSS | NTT DOCOMO, INC. |
R1-2305668 | UE feature discussion for Rel-18 eDSS | MediaTek Inc. |
R1-2305727 | On UE features for eDSS | Nokia, Nokia Shanghai Bell |
R1-2306187 | Session Notes for 9.16.13 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306193 | Summary on UE features for eDSS | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304516 | Discussion on UE features for BWP without restriction | vivo |
R1-2304606 | Discussion on UE feature for BWP without restriction | ZTE |
R1-2304609 | On UE features for BWP without restrictions | Dell Technologies |
R1-2304670 | UE features for BWP without restriction | Huawei, HiSilicon |
R1-2304787 | UE features for BWP without restriction | Ericsson |
R1-2304945 | Summary of UE features for BWP without restriction | Moderator (AT&T) |
R1-2305056 | Open issues in UE features for BWP without restrictions | Vodafone |
R1-2305283 | On UE features for Rel-18 BWP without restriction | Apple |
R1-2305377 | UE features for BWP without restriction | Qualcomm Incorporated |
R1-2305649 | UE features for BWP without restriction | MediaTek Inc. |
R1-2305728 | On UE features for BWP without restriction | Nokia, Nokia Shanghai Bell |
R1-2305985 | UE features for BWP without restriction | MediaTek Inc. |
R1-2306165 | Session Notes of AI 9.16.14 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2304416 | UE feature for endorsed TEI-18 on single DCI scheduling multiple PUSCHs | Ericsson, Qualcomm |
R1-2305729 | On UE features for TEI-18 | Nokia, Nokia Shanghai Bell |
R1-2305945 | UE feature for non-contiguous multi-PUSCH scheduling with single DCI 0_1 in FR1 | Huawei, HiSilicon |
R1-2306188 | Session Notes for 9.16.16 | Ad-Hoc Chair (NTT DOCOMO) |
R1-2306194 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2304517 | Discussion on Rel-18 Multi-carrier enhancements, eDSS and NCR | vivo |
R1-2304586 | Discussion on remaining issues in RRC signaling for Rel-18 multi-carrier enhancement and eDSS | Spreadtrum Communications |
R1-2304587 | Introduction of multi-carrier enhancements for NR | Spreadtrum Communications |
R1-2304607 | Draft CRs and higher layer signalling for others | ZTE |
R1-2304608 | On MC-enhancements and BWP without restrictions | Nokia, Nokia Shanghai Bell |
R1-2304801 | On remaining issues for R18 NCR and MCE | Intel Corporation |
R1-2304868 | On CR for the introduction of UL Tx switching across up to 4 bands | China Telecom |
R1-2305057 | Open issues in Higher Layer Parameters for BWP without restrictions | Vodafone, vivo |
R1-2305120 | Discussion on Rel-18 NCR | CMCC |
R1-2305150 | Remaining aspects on Rel-18 NCR and MC enhancements | LG Electronics |
R1-2305166 | Initial higher layer parameters for endorsed TEI-18 on single DCI scheduling multiple PUSCHs | Ericsson, Qualcomm |
R1-2305284 | Views on draft CR for Rel-18 multi-carrier enhancements | Apple |
R1-2305285 | On remaining issues for Rel-18 multi-carrier enhancements | Apple |
R1-2305378 | Views on draft CRs and higher layer signalling for R18 MC enhancements | Qualcomm Incorporated |
R1-2305475 | Discussion on remaining issues in Rel-18 eDSS | OPPO |
R1-2305548 | Discussions on higher layer signalling for multi-carrier enhancements | Samsung |
R1-2305627 | Discussion on higher layer parameters and remaining issues on Rel-18 WIs | NTT DOCOMO, INC. |
R1-2305675 | On maintenance for MC-Enhancement of multi-cell scheduling | MediaTek Inc. |
R1-2305716 | Higher layer signaling for NR Rel-18 | Ericsson |
R1-2305769 | Recommendations for RAN1 RRC Parameter Preparation | Moderator(Ericsson) |
R1-2305805 | Discussion on NCR backhaul beam control | ETRI |
R1-2305810 | On remaining issues for R18 NCR | Comba |
R1-2305908 | Discussion on remaining issues of Rel-18 multi-carrier enhancement | Lenovo |
R1-2305932 | Discussions on draft CRs and higher layer signalling for other Rel-18 items | Huawei, HiSilicon |
R1-2306090 | FL Summary#1 - Higher layer signaling for single DCI scheduling non-consecutive PUSCHs in FR1 | Moderator (Ericsson) |
R1-2306091 | FL Summary#2 - Higher layer signaling for single DCI scheduling non-consecutive PUSCHs in FR1 | Moderator (Ericsson) |
R1-2306113 | Summary of higher layer parameters for R18 DSS Enhancements | Moderator (Ericsson) |
R1-2306122 | Summary#1 of discussion on higher layer signalling for MC-Enh | Moderator (NTT DOCOMO, INC.) |
R1-2306141 | Summary of discussion on RRC parameter for NCR | Moderator (ZTE) |
R1-2306159 | Summary#2 of discussion on RRC parameter for NCR | Moderator (ZTE) |
R1-2306254 | Summary of the BWP_wor higher layer signalling email discussion | Moderator (Vodafone) |
R1-2306256 | Summary on the [113-R18-Others-02] Email discussion on MC-Enh draft CR for TS38.214 | Nokia |
R1-2306266 | Discussion summary on higher layer parameter list for Rel-18 DSS Enhancements WI | WI Rapporteur (Ericsson) |
R1-2306274 | Release 18 TS38.215 Editor CR for MIMO | Intel Corporation |
R1-2306275 | Release 18 TS38.215 Editor CR for Positioning Enhancements | Intel Corporation |
R1-2306276 | Introduction of sidelink channel access procedures for Rel-18 NR sidelink evolution | NTT DOCOMO, INC. |
R1-2306277 | Summary of discussion on draft 38.201 CR for NR sidelink evolution | NTT DOCOMO, INC. |
R1-2306279 | Introduction of IoT (Internet of Things) NTN (non-terrestrial network) enhancements | Motorola Mobility |
R1-2306280 | Introduction of RS for pathloss determination for Type 1 CG PUSCH | Samsung |
R1-2306281 | Summary of email discussions [113-R18-38.213-NR_TEI 1] | Samsung |
R1-2306282 | Introduction of multiplexing in a PUSCH with repetitions HARQ-ACK associated with DL assignments received after an UL grant for the PUSCH | Samsung |
R1-2306283 | Summary of email discussions [113-R18-38.213-NR_DSS_enh] | Samsung |
R1-2306284 | Introduction of dynamic spectrum sharing (DSS) enhancements | Samsung |
R1-2306285 | Summary of email discussions [113-R18-38.213-NR_redcap_enh] | Samsung |
R1-2306286 | Introduction of support for enhanced reduced capability NR devices | Samsung |
R1-2306287 | Summary of email discussions [113-R18-38.213-NR_FR1_lessthan_5MHz_BW] | Samsung |
R1-2306288 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Samsung |
R1-2306289 | Summary of email discussions [113-R18-38.213-NR_MC_enh] | Samsung |
R1-2306290 | Introduction of multi-carrier enhancements for NR | Samsung |
R1-2306291 | Summary of email discussions [113-R18-38.213-NR_MIMO_evo_DL_UL] | Samsung |
R1-2306292 | Introduction of MIMO Evolution for Downlink and Uplink | Samsung |
R1-2306293 | Summary of email discussions [113-R18-38.213-NR_mob_enh2] | Samsung |
R1-2306294 | Introduction of further mobility enhancements | Samsung |
R1-2306295 | Summary of email discussions [113-R18-38.213-NR_NCR] | Samsung |
R1-2306296 | Introduction of Network Controlled Repeaters - NR_NCR-Core | Samsung |
R1-2306297 | Summary of email discussions [113-R18-38.213-NR_NTN_enh] | Samsung |
R1-2306298 | Introduction of NR NTN enhancements | Samsung |
R1-2306299 | Summary of email discussions [113-R18-38.213-NR_pos_enh2] | Samsung |
R1-2306300 | Introduction of expanded and improved NR positioning | Samsung |
R1-2306301 | Introduction of NR sidelink evolution - NR_SL_enh2-Core | Samsung |
R1-2306302 | Editor’s summary on draft CR 37.213 for SL-U | Ericsson |
R1-2306303 | Introduction of NR Sidelink operation on shared spectrum | Ericsson |
R1-2306304 | Editor’s summary on draft CR 38.211 for NR_SL_enh2-Core | Ericsson |
R1-2306305 | Introduction of NR sidelink evolution | Ericsson |
R1-2306306 | Editor’s summary on draft CR 38.211 for NR_pos_enh2-Core | Ericsson |
R1-2306307 | Introduction of expanded and improved NR positioning | Ericsson |
R1-2306308 | Editor’s summary on draft CR 38.211 for NR_MIMO_evo_DL_UL-Core | Ericsson |
R1-2306309 | Introduction of MIMO evolution for downlink and uplink | Ericsson |
R1-2306310 | Editor’s summary on draft CR 38.211 for NR_LessThan_5MHz_FR1-Core | Ericsson |
R1-2306311 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Ericsson |
R1-2306312 | Summary of email discussion [Post-113-38.212-NR_MC_enh] | Huawei |
R1-2306313 | Introduction of Rel-18 Multi-carrier enhancements | Huawei |
R1-2306314 | Summary of email discussion [Post-113-38.212-NR_MIMO_evo_DL_UL] | Huawei |
R1-2306315 | Introduction of Rel-18 MIMO Evolution for Downlink and Uplink | Huawei |
R1-2306316 | Summary of email discussion [Post-113-38.212-NR_Mob_enh2-Core] | Huawei |
R1-2306317 | Introduction of Rel-18 Further NR mobility enhancements | Huawei |
R1-2306318 | Summary of email discussion [Post-113-38.212-NR_NTN_enh-Core] | Huawei |
R1-2306319 | Introduction of Rel-18 NR NTN enhancements | Huawei |
R1-2306320 | Summary of email discussion [Post-113-38.212-NR_pos_enh2-Core] | Huawei |
R1-2306321 | Introduction of NR positioning enhancement in Rel-18 | Huawei |
R1-2306322 | Summary of email discussion [Post-113-38.212-NR_SL_enh2-Core] | Huawei |
R1-2306323 | Introduction of Rel-18 NR sidelink evolution | Huawei |
R1-2306324 | Release 18 TS38.215 Editor CR for MIMO | Intel Corporation |
R1-2306325 | Release 18 TS38.215 Editor CR for Positioning Enhancements | Intel Corporation |
R1-2306326 | Release 18 TS38.202 Editor CR for MIMO | Qualcomm |
R1-2306327 | Summary of email discussion on the introduction of UL Tx switching across up to 4 bands in [Post-113-38.214-MC_Enh] | Nokia |
R1-2306328 | Introduction of UL Tx switching across up to 4 bands | Nokia |
R1-2306329 | Summary of email discussion on NR_MIMO enhancements on CSI | Nokia |
R1-2306330 | Introduction of specification support for MIMO enhancements on CSI | Nokia |
R1-2306331 | Summary of email discussion on NR_MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA | Nokia |
R1-2306332 | Introduction of specification support for MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA | Nokia |
R1-2306333 | Summary on email discussion on NR_Mob_enh2 | Nokia |
R1-2306334 | Introduction of specification support for mobility enhancements | Nokia |
R1-2306335 | Summary on email discussion on NR Enhanced Positioning | Nokia |
R1-2306336 | Introduction of specification support for Expanded and Improved NR Positioning | Nokia |
R1-2306337 | Summary on email discussion on Red Cap enhancements | Nokia |
R1-2306338 | Introduction of enhanced reduced capability NR devices | Nokia |
R1-2306339 | Summary on email discussion on Sidelink enhancements | Nokia |
R1-2306340 | Introduction of specification enhancements for NR sidelink evolution | Nokia |
R1-2306341 | Summary of email discussion on Multi-Cell Scheduling in [113-38.214-MC_Enh] | Nokia |
R1-2306342 | Introduction of multi-cell PDSCH / PUSCH scheduling | Nokia |
R1-2306343 | Summary of email discussions [Post-113-36.213-IoT_NTN_enh-Core] | Motorola Mobility |
TDoc | Title | Source |
---|---|---|
R1-2306252 | Post RAN1#113 event | RAN1 community |
R1-2306265 | 3GPP Excellence Award | RAN1 Chair |