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-2005410 | Discussion on joint scheduling |
discussion revised to R1-2006987 |
vivo | Rel-17 |
R1-102-e AI: 8.13.2 |
revised | [WTS] [JSN] | ||
| R1-2005441 | Discussion on Multi-cell PDSCH Scheduling via a Single DCI | discussion | ZTE | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2005628 | On Multi-cell PDSCH scheduling via a single DCI | discussion | MediaTek Inc. |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2005697 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | CATT |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2005901 | On 2-cell scheduling via single DCI | discussion | Intel Corporation | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2005909 | On support of Single DCI scheduling two cells | other | Nokia, Nokia Shanghai Bell |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2006064 | Multi-cell PDSCH scheduling via a single DCI | discussion | OPPO |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2006177 | On the use of one DCI format for scheduling on two cells | discussion | Samsung |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2006282 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | Spreadtrum Communications | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2006319 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | LG Electronics | NR_DSS-Core | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2006413 | Discussion on the PDCCH of P(S)Cell/SCell scheduling PDSCH on mulitple cells using a single DCI | discussion | Huawei, HiSilicon | NR_DSS-Core | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2006474 | A single DCI scheduling multi-cell | discussion | InterDigital, Inc. |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2006510 | Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI | discussion | Apple | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2006583 | Discussion on multi-cell PDSCH scheduling via a single DCI | discussion | ASUSTeK | NR_DSS-Core | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |
| R1-2006672 | Discussion on single DCI scheduling PDSCH on multiple cells | discussion | Ericsson |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | |||
| R1-2006750 | Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS | discussion | NTT DOCOMO, INC. | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2006834 | Views on multi-cell PDSCH scheduling via a single DCI | discussion | Qualcomm Incorporated | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] | ||
| R1-2006987 | Discussion on joint scheduling |
discussion revision of R1-2005410 |
vivo | Rel-17 |
R1-102-e AI: 8.13.2 |
not treated | [WTS] [JSN] |
18 documents (0.3187301158905 seconds)