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-160014 | NB-PDCCH design for NB-IoT | discussion | Nokia Networks |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160017 | DCI design for NB-IoT | discussion | Nokia Networks |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160024 | NB-PDCCH resource mapping | other | Huawei, HiSilicon |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160029 | NB-PDCCH search space | other | Huawei, HiSilicon |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160032 | DCI for NB-IoT | other | Huawei, HiSilicon |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160044 | NB-PDCCH design for NB-IOT | discussion | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160045 | Multiplexing of downlink channels for NB-IOT | discussion | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160046 | Scheduling of DL and UL data channels for NB-IOT | discussion | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160047 | Summary of NB-PDCCH email discussion | discussion | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160063 | Downlink resource multiplexing for NB-IoT | other | SHARP Corporation |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160071 | Discussion on NB-PDCCH design | discussion | Panasonic Corporation |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160074 | NB-IoT - NB-PDCCH design | discussion | Ericsson |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160075 | NB-IoT - Search space design considerations | discussion | Ericsson |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160103 | NB-PDCCH Design | other | Qualcomm Inc. |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160113 | Discussions on NB-PDCCH design for NB-IoT | discussion | LG Electronics |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160123 | Considerations on control channels of NB-IoT | discussion | ETRI |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160127 | NB-IoT Downlink Control Channel Design | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |
| R1-160136 | NB-PDCCH Design for NB-IoT | discussion | Interdigital Communications |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160139 | NB-PDCCH Design | discussion | Samsung |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160152 | Downlink control channel design for NB-IOT | discussion | MediaTek Inc. |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160162 | Discussion on scheduling timing for NB-IoT | discussion | MediaTek Inc. |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160165 | Initial views on NB-PDCCH for NB-IoT | discussion | NTT DOCOMO, INC. |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160175 | NB-PDCCH Design for NB-IoT | discussion | Sony Corporation |
R1-ah-31964 AI: 2.1.1.2 |
available | [WTS] [JSN] | |||
| R1-160207 | WF on NB-PDCCH for NB-IoT | other | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160208 | WF on DL multiplexing for NB-IoT | other | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160209 | WF on timing of NB-PDCCH and NB-PDSCH/PUSCH for NB-IoT | other | ZTE |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] | |||
| R1-160210 | WF on NB-PDCCH resource mapping | other | LG Electronics, MediaTek, Intel |
R1-ah-31964 AI: 2.1.1.2 |
noted | [WTS] [JSN] |
27 documents (0.36347103118896 seconds)