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-1903073 | Discussion on the Trigger Events of 2-step RACH | discussion | vivo |
R2-105 AI: 11.13 |
noted | [WTS] [JSN] | |||
| R2-1903074 | Clarification on the Cntention-based 2-step RACH | discussion | vivo |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903075 | Differentiation between 2-step and 4-step RACH | discussion | vivo |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903076 | Prioritized RA Parameters for 2-step RACH | discussion | vivo |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903077 | Considerations on the 2-step RACH Procedure | discussion | vivo |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903112 | 2 Step RA_MsgA Aspects | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903113 | 2 Step RA_MsgB Aspects | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903114 | Fallback from 2 step to 4 step RACH | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903115 | 2 Step RA_MAC PDU Format for MsgB | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903152 | Consideration on 2-step RACH |
discussion revised to R2-1905753 |
CATT | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903246 | Procedures for 2-step RACH | discussion | ETRI |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903291 | Clarification on contention based 2-step RACH | discussion | OPPO |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903292 | Contents for msgA and msgB | discussion | OPPO |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903293 | Contention resolution for 2-step RACH | discussion | OPPO |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903294 | Fall back mechanisms for 2-steps RACH | discussion | OPPO |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903426 | 2-step RACH General Aspects | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903427 | Fallback for 2-step RACH | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903428 | MsgA and msgB size for 2-step RACH | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903429 | RNTIs and Contention Resolution for 2-step RACH | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903534 | Workplan for 2-step RACH | Work Plan | ZTE Corporation, Sanechips |
R2-105 AI: 11.13 |
noted | [WTS] [JSN] | |||
| R2-1903535 | MsgA payload size for 2-step RACH | discussion | ZTE Corporation, Sanechips |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903536 | LS on msgA payload size for 2-step RACH |
LS out LS To: RAN1 |
ZTE Corporation, Sanechips |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903548 | General consideration on the content of MsgB | discussion | ZTE Corporation, Sanechips |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903549 | Consideration on 2-step RACH procedure | discussion | ZTE Corporation, Sanechips |
R2-105 AI: 11.13 |
noted | [WTS] [JSN] | |||
| R2-1903608 | Msg-A Content of 2-step RACH | discussion | Apple | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903715 | Fall back from 2-step RACH to 4-step RACH | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903716 | msgB design | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903717 | Network control of 2-step RACH | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903729 | Contention-based 2-Step RACH procedure |
discussion revised to R2-1906555, R2-1906572 |
LG Electronics Inc. | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1903731 | Contents in MAC layer of msgA and msgB |
discussion revised to R2-1906574 |
LG Electronics Inc. | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1903732 | RNTI for msgB in 2-step RACH |
discussion revised to R2-1906579 |
LG Electronics Inc. | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1903781 | Commonality of MsgB for RAR | discussion | Fujitsu | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903782 | On procedure selection among 2-step and 4-step RACH |
discussion revised to R2-1906256 |
Fujitsu | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903783 | On recognition of msgB or msg2 |
discussion revised to R2-1906257 |
Fujitsu | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1903794 | Discussion on 2-step RACH procedure | discussion | Spreadtrum Communications |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |||
| R2-1903914 | Discussion on 2-step RACH procedure | discussion | Panasonic Corporation | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1904031 | Applicable triggers for 2-step RACH | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904032 | MsgA for 2-step RACH | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904033 | Draft LS on MsgA content size |
LS out LS To: RAN1 revised to R2-1905303 |
Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
revised | [WTS] [JSN] | |
| R2-1904034 | RNTI design for MsgB reception | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904071 | Fall back to 4 step RACH procedure | discussion | NEC | NR_2step_RACH | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904108 | Discussion on supported triggers and scenarios for 2-step RACH | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904109 | Discussion on MsgA payload content | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904110 | Discussion on the 2-step RACH procedure | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904111 | Discussion on the MsgA resource configuration |
discussion revised to R2-1905202 |
Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
revised | [WTS] [JSN] | |
| R2-1904112 | Discussion on RACH type switching between 2-step, 4-step RACH and CFRA | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904113 | Discussion on MsgB for 2-step RACH | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904210 | Consideration on fall back procedure from 2-step RACH to 4-step RACH |
discussion revised to R2-1907046 |
Sony | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904211 | PUSCH Configurations for MsgA of 2-step RACH |
discussion revised to R2-1907047 |
Sony | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904324 | Discussion on RACH resources and fallback from 2-step to 4-step random access |
discussion revised to R2-1905923 |
CMCC | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1904325 | Discussion of MsgA and MsgB identification | discussion | CMCC | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1904377 | LS on message sizes for 2-step RACH | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904426 | RNTI and HARQ aspects of 2-step RACH |
discussion revised to R2-1907073 |
MediaTek Inc. | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904428 | On the contents of msgA and msgB in 2-step RACH | discussion | MediaTek Inc. | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904429 | SI Request and BFR triggers for 2-step RACH | discussion | MediaTek Inc. | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904438 | Consideration of MsgA contents and size | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904439 | Procedure for 2-Step RACH | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904947 | Random Access Resource selection procedure for 2-step CBRA |
discussion revised to R2-1907925 |
LG Electronics | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1904969 | two-step RACH msgA contents and UE ID for two-step RACH | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904970 | two-step RACH msgB contents and RNTI for msgB | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904971 | two-step RACH fall back to four-step RACH |
discussion revised to R2-1907910 |
Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1904979 | Discussion on payload size of msgA for 2-step RACH | discussion | LG Electronics | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1904983 | [Draft] LS on maximum payload size of msgA for 2-step RACH |
LS out LS To: RAN WG1 |
LG Electronics | NR_2step_RACH-Core |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1905118 | Initial consideration on 2 step RACH | discussion | NTT DOCOMO INC. | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | ||
| R2-1905202 | Discussion on the MsgA resource configuration |
discussion revision of R2-1904111 |
Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
not treated | [WTS] [JSN] | |
| R2-1905303 | Draft LS on MsgA content size |
LS out LS To: RAN1 revision of R2-1904033 revised to R2-1905304 |
Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
revised | [WTS] [JSN] | |
| R2-1905304 | LS on MsgA content size |
LS out LS To: RAN1 LS reply in R1-1906750, R1-1907901, R1-1907935, R1-1907948 revision of R2-1905303 revised to R2-1905472 |
RAN2 | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
approved | [WTS] [JSN] | |
| R2-1905472 | LS on MsgA content size |
LS out LS To: RAN1 revision of R2-1905304 |
RAN2 | NR_2step_RACH-Core | Rel-16 |
R2-105 AI: 11.13 |
withdrawn | [WTS] [JSN] |
68 documents (0.35667395591736 seconds)