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-2007580 Discussion on multi-carrier scheduling using single PDCCH discussion Huawei, HiSilicon NR_DSS-Core Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2007696 Discussion on joint scheduling discussion vivo R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2007840 Discussion on multi-cell PDSCH scheduling via a single DCI discussion CATT R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008063 Discussion on multi-cell PDSCH scheduling via a single DCI discussion LG Electronics NR_DSS-Core Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008111 Discussion on multi-cell PDSCH scheduling via a single DCI discussion Spreadtrum Communications Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008196 On the use of one DCI format for scheduling on two cells discussion Samsung R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008285 Discussion on multi-cell PDSCH scheduling via a single DCI discussion OPPO R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008452 Views on Rel-17 DSS Multi-cell PDSCH scheduling via a single DCI discussion Apple Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008696 Discussion on multi-cell PDSCH scheduling via a single DCI discussion ASUSTeK R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008831 Discussion on Multi-cell PDSCH Scheduling via a Single DCI discussion ZTE Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008835 Multi-cell scheduling and dormancy discussion Charter Communications Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2008929 Discussion on multi-cell PDSCH scheduling via a single DCI discussion Lenovo, Motorola Mobility R1-103-e

AI: 8.13.2

noted [WTS] [JSN]
R1-2008963 Evaluation on On Multi-cell PDSCH Scheduling via Single DCI discussion MediaTek Inc. R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009004 On 2-cell scheduling via single DCI discussion Intel Corporation Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009024 Discussion on multi-cell PDSCH scheduling via a single DCI discussion

revised to R1-2101089

ETRI R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009047 On support of Single DCI scheduling two cells discussion Nokia, Nokia Shanghai Bell NR_DSS Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009086 Discussion on the support of single DCI scheduling multi-cell discussion InterDigital, Inc. R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009196 Discussion on multi-cell PDSCH scheduling via a single DCI for NR DSS discussion NTT DOCOMO, INC. Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009207 Study on single DCI scheduling PDSCH on multiple cells discussion Ericsson R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009278 Views on multi-cell PDSCH scheduling via a single DCI discussion Qualcomm Incorporated Rel-17 R1-103-e

AI: 8.13.2

not treated [WTS] [JSN]
R1-2009559 Feature lead summary#1 on multi-cell scheduling via a single DCI discussion Moderator (Lenovo) NR_DSS-Core Rel-17 R1-103-e

AI: 8.13.2

noted [WTS] [JSN]
R1-2009815 Final Feature lead summary on multi-cell scheduling via a single DCI discussion Moderator (Lenovo) NR_DSS-Core Rel-17 R1-103-e

AI: 8.13.2

noted [WTS] [JSN]

22 documents (0.36805200576782 seconds)