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-2001524 | Corrections on channel structure of 2-step RACH | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2001647 | Remaining issues on channel structure for 2-step RACH | discussion | vivo |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2001710 | Remaining issues of the channel structure for 2-step RACH | discussion | ZTE, Sanechips |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2001712 | FL summary on the maintenance of the 2-step RACH channel structure |
discussion revised to R1-2002728 |
Moderator (ZTE) |
R1-ah-34813 AI: 7.2.1.1 |
revised | [WTS] [JSN] | |||
| R1-2001766 | Discussion on Channel Structure for Two-step RACH | discussion | OPPO |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2001949 | Remaining details of Channel Structure for 2-step RACH | discussion | LG Electronics | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2001958 | Discussion on Two-step RACH LS received from RAN2 | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core |
R1-ah-34813 AI: 7.2.1.1 |
withdrawn | [WTS] [JSN] | ||
| R1-2001976 | Discussion on Two-step RACH related LS received from RAN2 | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2001983 | Remaining details of channel structure for 2-step RACH | discussion | Intel Corporation | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2002064 | Remaining issues on 2-step RACH channel structure | discussion | CATT |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2002112 | Channel Structure for Two-Step RACH | discussion | Samsung |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2002259 | Remaining issue on preamble and PRU mapping for 2-step CFRA | discussion | Spreadtrum Communications | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2002319 | Remaining issues on channel structure for 2-step RACH | discussion | Apple | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2002369 | Channel Structure Related Corrections For 2-Step RACH | discussion | Ericsson |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |||
| R1-2002431 | Maintenance for Channel Structure for Two-Step RACH | discussion | NTT DOCOMO, INC. | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | ||
| R1-2002526 | Remaining issues and clarification on channel structure for Two-Step RACH | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
not treated | [WTS] [JSN] | |
| R1-2002728 | FL summary#2 on the maintenance of the 2-step RACH channel structure |
discussion revision of R1-2001712 |
Moderator (ZTE) |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |||
| R1-2002816 | Summary of email discussion [100b-e-NR-2step-RACH-01] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2002817 | Summary of email discussion [100b-e-NR-2step-RACH-02] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2002818 | Summary of email discussion [100b-e-NR-2step-RACH-03] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2002819 | Summary of email discussion [100b-e-NR-2step-RACH-04] | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2003019 | Text Proposal of PRACH validation rule | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2003020 | Text Proposal of PUSCH validation rule | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
endorsed | [WTS] [JSN] | |
| R1-2003021 | Text Proposal of alignment of terminology for RAR | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2003022 | Text Proposal of UE behavior if MsgA PRACH transmission is canceled | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
endorsed | [WTS] [JSN] | |
| R1-2003023 | Text Proposal of clarification on the guard period between hops | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] | |
| R1-2003024 | Text Proposal of the terminology for frequency hops | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
endorsed | [WTS] [JSN] | |
| R1-2003025 | Text Proposal of clarification on the DMRS sequences | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
endorsed | [WTS] [JSN] | |
| R1-2003026 | Text Proposal of clarification on the slot offset | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
endorsed | [WTS] [JSN] | |
| R1-2003027 | Text Proposals of editorial changes for 2-step RACH | discussion | Moderator (ZTE) | NR_2step_RACH-Core | Rel-16 |
R1-ah-34813 AI: 7.2.1.1 |
noted | [WTS] [JSN] |
30 documents (0.36400318145752 seconds)