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-2200043 | [Post116-e][242][Slicing] Slice-based cell re-selection algorithm | discussion | Ericsson |
R2-116-bis-e AI: 8.8.2 |
noted | [WTS] [JSN] | |||
R2-2200044 | Running 38.304 CR for RAN slicing | draftCR | Ericsson | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
noted | [WTS] [JSN] | |
R2-2200179 | Remaining issues on slice specific cell reselection | discussion | Qualcomm Incorporated | NR_SL_relay-Core |
R2-116-bis-e AI: 8.8.2 |
not treated | [WTS] [JSN] | ||
R2-2200406 | Optimizations for signalling Slice Information | discussion | Lenovo, Motorola Mobility | NR_slice-Core |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2200407 | RAN Slicing CR to 38.304 | CR | Lenovo, Motorola Mobility | 38.304 16.7.0 CR#225 catB | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] |
R2-2200408 | Triggers for initiating RAN slicing based cell reselections | discussion | Lenovo, Motorola Mobility | NR_slice-Core |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2200409 | Principles of Slice based reselection | discussion | Lenovo, Motorola Mobility | NR_slice-Core |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2200416 | Discussion on Slice based Cell Reselection | discussion | CATT | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200417 | Analysis on issues of slice groups at TA boundaries | discussion | CATT | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200510 | Further considerations of slice based cell reselection | discussion | Intel Corporation | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200636 | Consideration on slice based cell reselection | discussion | Spreadtrum Communications | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2200845 | Discussion on open issues for slice based cell reselection | discussion | CMCC | FS_NR_slice | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200929 | Consideration on slice-specific cell reselection | discussion | OPPO | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200947 | Considerations on slice groups | discussion | Nokia, Nokia Shanghai Bell | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200948 | Text Proposals for the draft 38.304 PCR | discussion | Nokia, Nokia Shanghai Bell | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2200949 | Cell reselection delay for option B and option C | discussion | Samsung R&D Institute India |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2200974 | Discussion on slice based cell reselection under network control | discussion | Huawei, HiSilicon | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201005 | Leftover issues in slice based cell reselection | discussion | ZTE corporation, Sanechips | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201110 | Text proposal for slice based cell reselection under NW control |
discussion revised to R2-2201686 |
Apple | NR_slice-Core |
R2-116-bis-e AI: 8.8.2 |
revised | [WTS] [JSN] | ||
R2-2201169 | On slice-based cell re-selection TP for 38.304 | discussion | Ericsson | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201190 | Slice-Info provision | discussion | NEC Telecom MODUS Ltd. |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2201192 | Slice-based cell re-selection TP for solution 4C | discussion | NEC Telecom MODUS Ltd. |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2201200 | Slice information provided by RRCRelease |
discussion revision of R2-2110912 revised to R2-2203452 |
Sharp | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2201208 | Discussion on signalling slice information | discussion | LG Electronics UK | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2201209 | Discussion on slice based cell reselection | discussion | LG Electronics UK | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2201389 | A couple of FFS for Cell Reselection |
discussion revision of R2-2110274 |
Kyocera |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2201406 | Discussion on Slice Aware UL BSR | discussion | RadiSys, Reliance JIO | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201410 | Resolving the common issues in slice based cell reselection | discussion | Beijing Xiaomi Software Tech | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | ||
R2-2201418 | TP for system information and slice based reselection priority handling | discussion | ZTE corporation, Sanechips | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201422 | On selection of Solution 4 Option A, B and C | discussion | Samsung R&D Institute UK |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2201443 | Remaining Issues on Slice Information | discussion | Samsung R&D Institute UK |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |||
R2-2201686 | Text proposal for slice based cell reselection under NW control |
discussion revision of R2-2201110 |
Apple, BT Plc | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
available | [WTS] [JSN] | |
R2-2201708 | Report for [AT116bis-e][240][Slicing] Remaining details for slice groups (CMCC) | discussion | CMCC | NR_slice-Core | Rel-17 |
R2-116-bis-e AI: 8.8.2 |
noted | [WTS] [JSN] |
33 documents (0.33364415168762 seconds)