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-2310887 | Maintenance of multi-cell PDSCCH/PUSCH scheduling with a single DCI | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311024 | Maintenance of Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311046 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Fujitsu | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311110 | Remaining issues on Rel-18 Multi-cell scheduling | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311177 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311275 | Remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311323 | Maintenance on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311387 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | xiaomi | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311496 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311520 | On Rel-18 MC-DCI scheduling | discussion | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311552 | Remaining issues on multi-cell scheduling with a single DCI | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311587 | Remaining issues on Rel-18 multi-carrier enhancements | discussion | Lenovo | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311634 | Maintenance on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311698 | On remaining issues for Rel-18 multi-cell scheduling | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311735 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Langbo | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311758 | Remaining issues on multi-cell PUSCH/PDSCH scheduling | discussion | ETRI | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311860 | Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311899 | Remaining issues on Multi-cell scheduling with single DCI | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2311990 | On maintenance for multi-cell scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2312049 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2312102 | Maintenance for single DCI scheduling multiple cells | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2312115 | Remaining detail on multi-cell scheduling PUSCH/PDSCH with a single DCI | discussion | ITRI | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
not treated | [WTS] [JSN] | |
| R1-2312360 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
noted | [WTS] [JSN] | |
| R1-2312361 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revised to R1-2312362 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
revised | [WTS] [JSN] | |
| R1-2312362 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revision of R1-2312361 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
noted | [WTS] [JSN] | |
| R1-2312513 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
noted | [WTS] [JSN] | |
| R1-2312514 | Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-115 AI: 8.12.1 |
noted | [WTS] [JSN] |
27 documents (0.31147599220276 seconds)