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-2003317 | Remaining issues on PDCCH enhancements for NR URLLC | discussion | ZTE | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2003387 | PDCCH enhancements for URLLC | discussion | vivo | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2003439 | Remaining Issue of PDCCH Enhancements for NR URLLC | discussion | Ericsson |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003525 | Corrections on PDCCH enhancement for URLLC | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2003577 | Maintenance of Rel-16 URLLC PDCCH enhancements | discussion | Nokia, Nokia Shanghai Bell |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003620 | Remaining issues on PDCCH enhancements | discussion | CATT |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003684 | Remaining issues on PDCCH enhancements | discussion | MediaTek Inc. |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003702 | Remaining issue for TCI field |
discussion revision of R1-2002484 revised to R1-2006865 |
ASUSTeK | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2003722 | DCI Size Alignment | other | Futurewei |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003737 | Remaining details on PDCCH enhancements for eURLLC | discussion | Intel Corporation | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2003865 | Remaining issues for PDCCH enhancements | discussion | Samsung |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003942 | Remaining Issues on PDCCH Enhancements for URLLC | discussion | Quectel |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2003944 | Remaining issues on PDCCH enhancements for NR URLLC | discussion | Panasonic Corporation | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2003979 | Remaining issues of PDCCH enhancements for URLLC | discussion | Spreadtrum Communications | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2004029 | Remaining issues of PDCCH enhancements for NR URLLC | discussion | LG Electronics | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2004114 | PDCCH enhancements for URLLC | discussion | OPPO |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |||
| R1-2004221 | Remaining Issues on PDCCH Enhancements for eURLLC | discussion | Apple | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2004331 | Remaining issues on PDCCH enhancements for NR URLLC | discussion | Sharp | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2004389 | Remaining issues for PDCCH enhancements for Rel.16 URLLC | discussion | NTT DOCOMO, INC | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | ||
| R1-2004457 | Remaining issues on PDCCH Enhancements for URLLC | discussion | Qualcomm Incorporated | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2004522 | Remaining issues on PDCCH enhancement for NR URLLC | discussion | WILUS Inc. | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2004675 | Feature lead summary#1 on PDCCH enhancements | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2004721 | Feature lead summary#2 on PDCCH enhancements | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2004763 | Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revised to R1-2004927 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2004874 | Discussion on PDCCH Enhancements for eURLLC | discussion | Apple Inc. | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
not treated | [WTS] [JSN] | |
| R1-2004927 | Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revision of R1-2004763 revised to R1-2004928 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2004928 | Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revision of R1-2004927 revised to R1-2004929 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2004929 | Summary #4 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design |
discussion revision of R1-2004928 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2005053 | Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
discussion revised to R1-2005054 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2005054 | Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2005053 revised to R1-2005055 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2005055 | Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] on remaining issues on enhanced PDCCH monitoring capability |
discussion revision of R1-2005054 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2005056 | Text proposal for TS 38.213 Section 10.1 as outcome of issue D-1 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005057 | Text proposal for TS 38.213 Section 10.1 as outcome of issue D-2 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005058 | Text proposal for TS 38.213 Section 10 as outcome of issue C-6 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-03] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005059 | Email discussion/approval [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] on remaining issues on DCI format design and proposed conclusion #1 | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2005060 | Text proposal for TS 38.212 as outcome of issue A-3 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005061 | Text proposal for TS 38.212 Section 7.3.1.0 as outcome of issue A-1 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005062 | Text proposal for TS 38.212 Section 7.3.1.2.3 as outcome of issue A-5 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005063 | Text proposal for TS 38.213 Section 9.1.3.1 as outcome of issue A-13 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005064 | Text proposal for TS 38.213 Section 12 as outcome of issue A-12 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
withdrawn | [WTS] [JSN] | |
| R1-2005065 | Text proposals for TS 38.214 Section 5.1.6.2 & Section 5.1.6.3 as outcome of issue A-5 in [101-e-NR-L1enh-URLLC-PDCCH enhancements-01] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005066 | Summary #1 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
discussion revised to R1-2005067 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2005067 | Summary #2 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
discussion revision of R1-2005066 revised to R1-2005115 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
revised | [WTS] [JSN] | |
| R1-2005068 | Text proposal for TS 38.213 Section 10.1 as outcome of issue C-3 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005069 | Text proposal for TS 38.213 Section 10.1 as outcome of issue C-4 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005115 | Summary #3 of email discussion [101-e-NR-L1enh-URLLC-PDCCH enhancements-02] on remaining issues on scaling PDCCH monitoring capability |
discussion revision of R1-2005067 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
noted | [WTS] [JSN] | |
| R1-2005116 | Text proposal for TS 38.213 Section 10 & Section 10.1 as outcome of issue C-1 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] | |
| R1-2005117 | Text proposal for TS 38.213 Section 10.1 as outcome of issue C-2 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-ah-38103 AI: 7.2.5.1 |
endorsed | [WTS] [JSN] |
48 documents (0.36045789718628 seconds)