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-2210856 | Discussion on multi-cell scheduling with a single DCI | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2210924 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211022 | Discussion on multi-cell scheduling | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211045 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211063 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Google Inc. | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211082 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Fujitsu | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211213 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211244 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211376 | Discussion on the remaining issues for the multi-cell scheduling with a single DCI | discussion | xiaomi | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211414 | Discussions on multi-cell scheduling with a single DCI | discussion | Intel Corporation | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211488 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211534 | Discussion on multi-cell scheduling with a single DCI | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211585 | On multi-cell scheduling via a single DCI | discussion | Lenovo | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211695 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211824 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211878 | Discussion on Multicarrier scheduling with a single DCI | discussion | FGI | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211919 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CAICT | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2211998 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212060 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212132 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212156 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212190 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Langbo | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212252 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212303 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212336 | Discussion on multi-cell scheduling with a single DCI | discussion | ITRI | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212362 | Discussion on Multi-cell PXSCH scheduling with a single DCI | discussion | NEC | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
R1-2212392 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
noted | [WTS] [JSN] | |
R1-2212393 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
noted | [WTS] [JSN] | |
R1-2212394 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
noted | [WTS] [JSN] | |
R1-2212923 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revised to R1-2212924 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
revised | [WTS] [JSN] | |
R1-2212924 | Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revision of R1-2212923 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-111 AI: 9.9.1 |
noted | [WTS] [JSN] |
31 documents (0.31678104400635 seconds)