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-2104186 | Way Forward On single DCI scheduling two cells | discussion | Nokia, Nokia Shanghai Bell | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104233 | Discussion on multi-carrier scheduling using single PDCCH | discussion | Huawei, HiSilicon | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104341 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | discussion | ZTE | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104392 | Discussion on joint scheduling | discussion | vivo | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104446 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | Spreadtrum Communications | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104496 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | CATT | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104807 | Discussion on multi-cell PDSCH scheduling via a single DCI | other | OPPO | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104868 | On multi-cell PDSCH scheduling via a single DCI | discussion | Lenovo, Motorola Mobility | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104932 | On 2-cell scheduling via single DCI | discussion | Intel Corporation | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2104988 | On 2-cell scheduling via single DCI | discussion | Intel Corporation | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
withdrawn | [WTS] [JSN] | |
| R1-2105045 | On 2-cell scheduling via single DCI | discussion | Intel Corporation | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
withdrawn | [WTS] [JSN] | |
| R1-2105132 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | discussion | Apple | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105340 | On a single DCI format scheduling on multiple cells | discussion | Samsung | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105402 | On the support of single DCI scheduling two cells | discussion | InterDigital, Inc. | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105412 | Multi-cell PDSCH scheduling via a single DCI | discussion | NEC | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105442 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | LG Electronics | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105724 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | discussion | NTT DOCOMO, INC. | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2105797 | Study on single DCI scheduling PDSCH on multiple cells | discussion | Ericsson | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2106069 | Feature lead summary#1 on multi-cell scheduling via a single DCI | discussion | Moderator (Lenovo) | NR_DSS-Core | Rel-17 |
R1-105-e AI: 8.13.2 |
noted | [WTS] [JSN] | |
| R1-2106134 | Feature lead summary#2 on multi-cell scheduling via a single DCI | discussion | Moderator (Lenovo) | Rel-17 |
R1-105-e AI: 8.13.2 |
noted | [WTS] [JSN] |
20 documents (0.29682207107544 seconds)