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 |
|---|---|---|---|---|---|---|---|---|---|
| R2-1912084 | Remaining issues on supporting only 2-step RACH configuration on a UL BWP | discussion | OPPO |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |||
| R2-1912085 | msgB MAC PDU format in 2-step RACH | discussion | OPPO |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |||
| R2-1912086 | Remaining stage-2 open issues | discussion | OPPO |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
| R2-1912186 | Differentiation Between 2-step and 4-step RACH | discussion | vivo |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |||
| R2-1912224 | Load balancing between RACH Types | discussion | CATT | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1912431 | 2 Step RA_RACH prioritisation | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1912432 | 2 Step RACH_RNTI for Receiving Network Response | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1912468 | MsgB Retransmission Scheme | discussion | Apple | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1912679 | RNTI design and HARQ aspects for 2-step RA | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1912692 | Loading Control in the RACH Type Selection |
discussion revision of R2-1909238 revised to R2-1915450 |
PANASONIC R&D Center Germany |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |||
| R2-1912794 | Further consideration on the SucessRAR design and Fallback RAR | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1912795 | Preamble grouping selection or PUSCH TBS size selection for 2-step RACH | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1912947 | HARQ feedback for MsgB | discussion | CMCC | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | ||
| R2-1912954 | Further discussion on RA type selection | discussion | CMCC |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |||
| R2-1913008 | Discussion on the MsgA transmission | discussion | Huawei, HiSilicon | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | ||
| R2-1913009 | Discussion on MsgB reception | discussion | Huawei, HiSilicon | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | ||
| R2-1913144 | Discussion on HARQ and RNTI design for msgB | discussion |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | ||||
| R2-1913168 | Considerations on MsgB reception |
discussion revised to R2-1915001 |
Fujitsu | NR_2step_RACH | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913217 | RNTI design for MsgB reception | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913218 | Draft LS on MsgB RNTI design |
LS out LS To: TSG RAN WG1 |
Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913357 | HARQ support for MsgB of 2-Step RACH | discussion | Sony | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913366 | Differentiating between MSG2 and MSGB | discussion | ZTE Corporation, Sanechips | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | ||
| R2-1913367 | Remaining Stage 2 issues for 2-step RACH | discussion | ZTE Corporation, Sanechips | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | ||
| R2-1913401 | Discussion on HARQ feedback for msgB and RNTI design for msgB | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913402 | Prioritized 2-step RACH | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1913870 | RNTI design for msgB |
discussion revision of R2-1909826 |
LG Electronics Inc. | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
| R2-1913914 | Clarification on criteria selection for 2-step RACH and 4-step RACH | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |
| R2-1914051 | [DRAFT] LS to RAN1 on 2-step RACH |
LS out LS To: RAN1 revised to R2-1914067 |
ZTE | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
revised | [WTS] [JSN] | |
| R2-1914052 | Summary of discussion on rebudiling and fallback | discussion | Nokia |
R2-107 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
| R2-1914067 | [DRAFT] LS on differentiating between MSG2 and MSGB |
LS out LS To: RAN1 revision of R2-1914051 revised to R2-1914191 |
ZTE | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
revised | [WTS] [JSN] | |
| R2-1914191 | LS on differentiating between MSG2 and MSGB |
LS out LS To: RAN1 revision of R2-1914067 |
RAN2 | NR_2step_RACH-Core | Rel-16 |
R2-107 AI: 6.13.2 |
approved | [WTS] [JSN] |
31 documents (0.35164308547974 seconds)