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-1914373 | Differentiation Between Msg2 and MsgB by MsgB-RNTI | discussion | vivo |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
R2-1914375 | Contention Resolution of 2-step RACH Triggered by Uplink Data Arrival Without Valid TA | discussion | vivo |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |||
R2-1914376 | Remaining Issues on MsgA Transmission and Fallback | discussion | vivo |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
R2-1914377 | Resource Selection for 2-step RACH |
discussion revision of R2-1912189 revised to R2-2000142 |
vivo |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |||
R2-1914378 | Discussion on the BFR-initiated 2-step RACH | discussion | vivo |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |||
R2-1914388 | Remaining open issues for 2-step RACH | discussion | OPPO | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914389 | Draft TP for msgB MAC PDU format | draftCR | OPPO | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914391 | Contention resolution for 2-step RACH in C-RNTI MAC CE case | discussion | OPPO | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1914396 | [Draft] LS on preamble group for 2-step RACH |
LS out LS To: RAN1 |
OPPO | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914421 | On the remaining open issues of 2-step RACH | discussion | CATT | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1914423 | Consideration on msgB-RNTI | discussion | CATT | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914424 | RA Type Selection between Legacy CFRA and 2-step CBRA |
discussion revision of R2-1912225 |
CATT | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914430 | Report of Email discussion 107bis#76- MSG B Format Design | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1914431 | MAC TP_MSGB Format Design | draftCR | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
endorsed | [WTS] [JSN] | |
R2-1914432 | Legacy CFRA and Selection between 2 step and 4 step RA | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1914433 | 2 Step RACH_RNTI for Receiving Network Response | discussion | Samsung Electronics Co., Ltd | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1914617 | Discussion on 2-step RACH for BFR | discussion | Asia Pacific Telecom co. Ltd | NR_2step_RACH-Core |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1914796 | Remaining open issues for 2-step CBRA | discussion | ZTE Corporation, Sanechips |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
R2-1914797 | Consideration on the MsgB RA-RNTI calculation | discussion | ZTE Corporation, Sanechips |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |||
R2-1914798 | Running MAC CR for 2-step RACH | draftCR | ZTE Corporation (email rapporteur) | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
endorsed | [WTS] [JSN] | |
R2-1914799 | Summary of running MAC CR review issue list | report | ZTE Corporation (email rapporteur) |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |||
R2-1914842 | Other User Plane Stage-3 issues on 2-Step RACH | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1914843 | Remaining issues on PUSCH resource unit selection for 2-step RACH | discussion | Intel Corporation | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915001 | Considerations on MsgB reception |
discussion revision of R2-1913168 |
Fujitsu | NR_2step_RACH | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915005 | RA Prioritization for MPS for 2-step RACH |
discussion revised to R2-1916269 |
Perspecta Labs, ECD, AT&T, T-Mobile, Sprint, Ericsson, Qualcomm | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
revised | [WTS] [JSN] | |
R2-1915069 | RA variables for 2-step RACH fallback procedure | discussion | ITRI | NR_2step_RACH-Core |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1915215 | Discussion on the new RA-RNTI for MsgB | discussion | CMCC | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1915225 | TA handling in 2-step RACH |
discussion revision of R2-1912478 |
Samsung | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915239 | Applying un-used RNTIs for MsgB of 2-Step RACH | discussion | Sony | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1915240 | Differentiating MsgB with and without RRC messages |
discussion revised to R2-2000831 |
Sony | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
not treated | [WTS] [JSN] | |
R2-1915255 | Consideration on the variables for 2-step RACH | discussion | ZTE Corporation, Sanechips |
R2-108 AI: 6.13.2 |
withdrawn | [WTS] [JSN] | |||
R2-1915326 | RNTI design for MsgB reception | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1915327 | 2-step RACH only BWP | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915328 | HARQ ACK resources for successRAR | discussion | Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915329 | Draft LS on HARQ ACK resources for successRAR |
LS out LS To: TSG RAN WG1 |
Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915602 | RA type switch and fallback in 2-step RA | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1915603 | New msgB format for 2-step RA | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1915607 | msgB RNTI design for 2-step RA | discussion | Ericsson | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1915928 | RAN1 Impact on MsgB Design | discussion | Apple | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916006 | Remaining issues on user plane aspects | discussion | LG Electronics | NR_2step_RACH-Core |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1916013 | Remaining issues on PDU format for MsgB | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916014 | MsgA resource configuration and selection | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916015 | Remaining issues on MsgB reception | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916016 | Discussion on MsgB-RNTI design | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916018 | Further Discussions on Fallback Procedure for 2-step RACH | discussion | Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916024 | RNTI for msgB | discussion | LG Electronics | NR_2step_RACH-Core |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1916027 | Draft LS to RAN1 on RNTI for msgB |
LS out LS To: RAN1 |
LG Electronics | NR_2step_RACH-Core |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||
R2-1916060 | RNTI design for msgB | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] | |
R2-1916062 | Contention resolution for msgA with C-RNTI | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916064 | msgB MAC PDU format | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916065 | Remaining issue on 2-step RACH fall back procedure | discussion | Qualcomm Incorporated | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916083 | Discussion on MSGB-RNTI design | discussion |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||||
R2-1916084 | Discussion on msgB HARQ process | discussion |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | ||||
R2-1916163 | Discussion on indication for presence of RRC messages | discussion | LG Electronics Polska | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
available | [WTS] [JSN] | |
R2-1916269 | RA Prioritization for MPS for 2-step RACH |
discussion revision of R2-1915005 |
Perspecta Labs, CISA ECD, AT&T, T-Mobile, Sprint, Verizon, Ericsson, Qualcomm | NR_2step_RACH-Core | Rel-16 |
R2-108 AI: 6.13.2 |
noted | [WTS] [JSN] |
55 documents (0.35158801078796 seconds)