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-161812 | NB-PRACH design | other | Huawei, HiSilicon, Neul |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161813 | Remaining NB-IoT random access physical layer aspects | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161834 | NB-IoT - NPRACH sequences | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161835 | NB-IoT - NPRACH configurations | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161836 | NB-IoT - Remaining issues for random access procedure | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161853 | Remaining issues on NB-PRACH design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161854 | Remaining issues on random access procedure for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161872 | Remaining issues on single tone PRACH for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161903 | Remaining details of NB-PRACH and random access | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161905 | Discussion on NPRACH baseband signal generation |
discussion revised to R1-162983 |
NEC Corporation |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161918 | PRACH for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161944 | Random Access Channel Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161975 | Remaining issues on RACH procedure for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-162027 | WF on PRACH | discussion | Nokia Networks, ALU, ASB |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162033 | WF on NB-PRACH sequence | discussion | Huawei, HiSilicon, Neul, Intel, Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162037 | WF on timing relationships for random access | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162050 | WF on NB-PRACH sequence | discussion | ZTE |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162052 | Timing advance for NB-IoT | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162055 | UL grant in RAR | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] |
19 documents (0.36916899681091 seconds)