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-2100129 | Discussion on candidate solutions of slice-based RACH | discussion | Qualcomm Incorporated | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100363 | Consideration of slice based RACH | discussion | Intel Corporation | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100424 | Considerations on the solutions of slice based RACH configuration | discussion | Beijing Xiaomi Software Tech | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | ||
R2-2100599 | RACH prioritisation for slices | discussion | Nokia, Nokia Shanghai Bell | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100662 | Consideration on slice based RACH configuration | discussion | Spreadtrum Communications | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100705 | Remaining issues on RACH configuration | discussion | vivo | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100878 | Discussion on slice based RACH and cell barring | discussion | Apple | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100895 | Consideration on slice-specific RACH | discussion | OPPO | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2100929 | Consideration on slice-specific separate RACH resources pool | discussion | Samsung Electronics | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2101062 | Considerations on solutions for slice-specific RACH configuration | discussion | Lenovo, Motorola Mobility | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2101195 | Consideration on the slice specific RACH configuration | discussion | ZTE corporation, Sanechips | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2101405 | RSRP Thresholds for RACH separation and prioritisation for numerous slice configurations | discussion | NEC Telecom MODUS Ltd. |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |||
R2-2101701 | Slice based RACH configuration | discussion | Huawei, HiSilicon | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2101805 | Solutions analysis and draft TP for slice-based RACH configuration | discussion | CMCC | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
available | [WTS] [JSN] | |
R2-2101975 | Summary of [AT113-e][252][Slicing] Conclusions on slice-based RACH configuration (CMCC) | discussion | CMCC | FS_NR_slice | Rel-17 |
R2-113-e AI: 8.8.3 |
noted | [WTS] [JSN] |
15 documents (0.31354594230652 seconds)