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-2003365 | Remaining issues on channel structure for 2-step RACH | discussion | vivo | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2003455 | Remaining issues of the channel structure for 2-step RACH | discussion | ZTE, Sanechips |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2003457 | FL summary on the maintenance of the 2-step RACH channel strucutre | discussion | Moderator (ZTE) |
R1-ah-38103 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |||
| R1-2003503 | Corrections on channel structure of 2-step RACH | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2003600 | Remaining issues on 2-step RACH channel structure | discussion | CATT |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2003724 | Remaining details of channel structure for 2-step RACH | discussion | Intel Corporation | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2003855 | Channel Structure for Two-Step RACH | discussion | Samsung |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2003978 | Remaining issues on channel structure for 2-step RACH | discussion | Spreadtrum Communications | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2004099 | Discussion on Channel Structure for Two-step RACH | discussion | OPPO |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2004130 | Remaining details of Channel Structure for 2-step RACH | discussion | LG Electronics | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2004213 | Remaining issues on channel structure for 2-step RACH | discussion | Apple | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2004347 | Channel Structure Related Corrections For 2-Step RACH | discussion | Ericsson |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2004381 | Maintenance for Channel Structure for Two-Step RACH | discussion | NTT DOCOMO, INC. | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2004440 | Remaining issues and clarification on channel structure for Two-Step RACH | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2004588 | Discussion on remaining issues related to channel structure for Two-step RACH | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2004833 | Summary of email discussion [101-e-NR-2step-RACH-01] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2004834 | Summary of email discussion [101-e-NR-2step-RACH-02] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2004835 | Summary of email discussion [101-e-NR-2step-RACH-03] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-38103 AI: 7.2.1.1 |
noted | [WTS] [JSN] |
18 documents (0.35804986953735 seconds)