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-2005347 | PDCCH enhancements for URLLC | discussion | vivo | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2005413 | Remaining issues on PDCCH enhancements for NR URLLC | discussion | ZTE | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2005506 | Remaining Issue of PDCCH Enhancements for NR URLLC | discussion | Ericsson |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2005672 | Remaining issues on PDCCH enhancements | discussion | CATT |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2005790 | Corrections on PDCCH enhancement for URLLC | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2005850 | Remaining corrections for PDCCH enhancements for URLLC | discussion | Intel Corporation | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2006051 | PDCCH enhancements for URLLC | discussion | OPPO |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2006109 | Maintenance on PDCCH enhancements | discussion | Samsung |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2006278 | Remaining issues of PDCCH enhancements for URLLC | discussion | Spreadtrum Communications | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2006487 | Remaining issues on PDCCH enhancements | discussion | Apple | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2006549 | Remaining Issues on PDCCH Enhancements for Rel-16 URLLC | discussion | Quectel |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2006563 | Remaining issues on PDCCH enhancements for NR URLLC | discussion | Sharp | NR_L1enh_URLLC-Core |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2006774 | Remaining issues on PDCCH Enhancements for URLLC | discussion | Qualcomm Incorporated | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2006865 | Remaining issue for TCI field |
discussion revision of R1-2003702 revised to R1-2008634 |
ASUSTeK | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2006882 | Remaining issues on PDCCH for NR URLLC | discussion | WILUS Inc. | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2006968 | Feature lead summary#1 on PDCCH enhancements |
discussion revised to R1-2007004 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007004 | Feature lead summary#2 on PDCCH enhancements |
discussion revision of R1-2006968 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2007066 | Summary #1 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revised to R1-2007118 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007067 | Summary #1 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability |
discussion revised to R1-2007119 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007118 | Summary #2 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revision of R1-2007066 revised to R1-2007255 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007119 | Summary #2 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2007067 revised to R1-2007226 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2007226 | Summary #3 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2007119 revised to R1-2007250 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007250 | Summary #4 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2007226 revised to R1-2007443 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2007251 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-2 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2007252 | Text proposal for TS 38.213 Section 10 as outcome of issue B-5-3 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2007253 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-5-4 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2007254 | Text proposal for TS 38.213 Section 10.1 as outcome of issue B-5-6 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2007255 | Summary #3 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revision of R1-2007118 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2007256 | Text proposal for TS 38.212 Section 7.3.1.0 as outcome of issue A-1 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2007443 | Summary #5 of email discussion [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2007250 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2007444 | Text proposal for TS 38.213 Section 10 as outcome of issue B-1 in [102-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-102-e AI: 7.2.5.1 |
endorsed | [WTS] [JSN] |
31 documents (0.35690903663635 seconds)