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-2109452 | Selection and fallback between RACH partitions | discussion | Qualcomm Incorporated | Rel-17 |
R2-116-e AI: 8.18.2 |
noted | [WTS] [JSN] | ||
| R2-2109532 | RA Procedure Aspects | discussion | Samsung Electronics Co., Ltd | NR_cov_enh-Core, NR_SmallData_INACTIVE-Core, NR_slice-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2109542 | Considerations on the common aspects of RACH procedure | discussion | Beijing Xiaomi Software Tech | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | ||
| R2-2109882 | RACH resource/configuration selection and fallback mechanism | discussion | Intel Corporation | NR_cov_enh-Core, NR_redcap-Core, NR_UE_pow_sav_enh-Core, NR_slice-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2110260 | Discussion on RACH indication and partitioning | discussion | CMCC | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | ||
| R2-2110560 | RNTI collision problem for Rel-17 features | discussion | Ericsson | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | ||
| R2-2110578 | User plane aspects of RACH partitioning | discussion | ZTE Corporation, Sanechips | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | ||
| R2-2110598 | MAC aspects for RACH partitioning | discussion | Huawei, HiSilicon | NR_SmallData_INACTIVE-Core, NR_slice-Core, NR_redcap-Core, NR_cov_enh-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2110665 | Overview of RACH resource selection | discussion | NEC | NR_redcap-Core, NR_cov_enh-Core, NR_SmallData_INACTIVE-Core, NR_slice-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2110813 | Selection of RACH partition | discussion | Nokia, Nokia Shanghai Bell | NR_SmallData_INACTIVE-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2110917 | RACH indication and partitioning | discussion | InterDigital | NR_SmallData_INACTIVE-Core, NR_cov_enh-Core, NR_redcap-Core, NR_slice-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2110927 | Discussion on RACH Partitioning in RA Procedure Aspect |
discussion revision of R2-2107058 revised to R2-2201628 |
vivo | NR_SmallData_INACTIVE-Core, NR_cov_enh-Core, NR_redcap-Core, NR_slice-Core | Rel-17 |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] | |
| R2-2111164 | Discussion on common RA procedure for RACH partitioning features | discussion | LG Electronics Inc. | NR_SmallData_INACTIVE-Core, NR_slice-Core, NR_redcap-Core, NR_cov_enh-Core |
R2-116-e AI: 8.18.2 |
not treated | [WTS] [JSN] |
13 documents (0.33308815956116 seconds)