Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".
Download results in JSON format
| tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
|---|---|---|---|---|---|---|---|---|---|
| R1-2500065 | On Rel-19 Multi-carrier enhancements | discussion | Nokia | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500092 | Discussion on Rel-19 Multi-carrier enhancements | discussion | Huawei, HiSilicon | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500139 | Discussion on multi-cell scheduling with a single DCI | discussion | Lenovo | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500147 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE Corporation, Sanechips | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500187 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum, UNISOC | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500212 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500271 | Discussion on multi-carrier enhancements for NR phase 3 | discussion | China Telecom | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500306 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500371 | Discussion on enhancement of multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | vivo | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500461 | Discussion of multi-cell scheduling with a single DCI | discussion | OPPO | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500808 | On multi-cell PUSCH/PDSCH scheduling with single DCI | discussion | Apple | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500818 | Discussion on multi-carrier enhancements for NR Phase 3 | discussion | Panasonic | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500871 | Enhancements for multi-cell PUSCH/PDSCH scheduling | discussion | Samsung | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500923 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ETRI | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500960 | Discussion on single DCI based multi-cell scheduling for Rel-19 | discussion | LG Electronics | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2500985 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | TCL | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501033 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501178 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501220 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501345 | Multi-cell PxSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501374 | Feature lead summary#1 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2501375 | Feature lead summary#2 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2501376 | Feature lead summary#3 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2501377 | Feature lead summary#4 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120 AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2501827 | Discussion on enhancement of multi-cell PUSCH/PDSCH | discussion | vivo | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501885 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum, UNISOC | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501892 | Discussion on multi-cell scheduling with a single DCI | discussion | Lenovo | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501910 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE Corporation, Sanechips | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501960 | Multi-cell PxSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2501977 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502034 | Discussion on multi-carrier enhancements for NR phase 3 | discussion | China Telecom | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502215 | Discussion on Rel-19 Multi-carrier enhancements | discussion | Huawei, HiSilicon | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502282 | Discussion of multi-cell scheduling with a single DCI | discussion | OPPO | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502388 | Enhancements for multi-cell PUSCH/PDSCH scheduling | discussion | Samsung | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502484 | Discussion on single DCI based multi-cell scheduling for Rel-19 | discussion | LG Electronics | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502493 | Discussion on multi-carrier enhancements for NR Phase 3 | discussion | Panasonic | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502495 | Remaining details on Rel-19 Multi-carrier enhancements | discussion | Nokia | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502574 | Discussion on Multi-cell PUSCHPDSCH scheduling with a single DCI | discussion | TCL | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502720 | Multi-carrier enhancements for NR phase 3 |
discussion revised to R1-2502998 |
MediaTek Inc. | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
revised | [WTS] [JSN] | |
| R1-2502783 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502859 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2502998 | Multi-carrier enhancements for NR phase 3 |
discussion revision of R1-2502720 |
MediaTek Inc. | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
not treated | [WTS] [JSN] | |
| R1-2503037 | Feature lead summary#1 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2503038 | Feature lead summary#2 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
noted | [WTS] [JSN] | |
| R1-2503039 | Feature lead summary#3 on multi-cell scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh2-Core | Rel-19 |
R1-120-bis AI: 9.12.1 |
noted | [WTS] [JSN] |
45 documents (0.36201596260071 seconds)