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 |
---|---|---|---|---|---|---|---|---|---|
R3-204807 | Service Continuity when a slice becomes unavailable | discussion | Qualcomm Incorporated | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-204808 | LS on Service Continuity when a slice becomes unavailable |
LS out LS To: SA2 |
Qualcomm Incorporated | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-204839 | Use Cases for Network Slice Service Continuity | discussion | Nokia, Nokia Shanghai Bell |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |||
R3-204840 | RAN Re-mapping Solution: key principles | discussion | Nokia, Nokia Shanghai Bell |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |||
R3-204883 | On RAN slice awareness and service continuity | discussion | NEC | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-204884 | On intra-RAT handover service continuity | discussion | NEC | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-204902 | Discussion on slice re-mapping and fallback upon handover | discussion | China Telecommunication | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | ||
R3-205030 | Discussion on slice Re-mapping at mobility | discussion | Ericsson | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205061 | Description of Slice Remapping | pCR | Ericsson | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] |
R3-205083 | Use cases for network slice service continuity | discussion | Huawei | FS_NR_slice | Rel-16 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205084 | Potential solutions to network slice service continuity | discussion | Huawei | FS_NR_slice | Rel-16 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205184 | Initial Consideration On RAN slicing | discussion | ZTE, Lenovo, Motorola Mobility | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205185 | TP for 38.832 | other | ZTE | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205353 | Discussion on use cases for slice service continuity and slice remapping solutions | discussion | LG Electronics |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |||
R3-205354 | (TP for 38.832) Use cases for slice service continuity and slice remapping solutions | pCR | LG Electronics | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] |
R3-205361 | Discussion on NG based handover slice re-mapping | discussion | CATT | FS_NR_slice |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | ||
R3-205362 | Discussion on Xn based handover slice re-mapping | discussion | CATT | FS_NR_slice |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | ||
R3-205404 | Discussion on slice re-mapping | discussion | Samsung | FS_NR_QoE | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205440 | Service continuity for slicing | discussion | CMCC | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205441 | TP to service continuity for slicing | discussion | CMCC | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
available | [WTS] [JSN] | |
R3-205483 | CB: # RANSlicing2-Slice_Remapping_Scenarios - Summary of email discussion |
discussion revised to R3-205728 |
ZTE - moderator |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] | |||
R3-205484 | CB: # RANSlicing3-Slice_Remapping_Solutions - Summary of email discussion |
discussion revised to R3-205730 |
Nokia - moderator |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] | |||
R3-205626 | (TP for 38.832) Re-mapping Policy in target NG-RAN node | pCR | Nokia | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
agreed | [WTS] [JSN] |
R3-205646 | (TP for 38.832) Potential solutions to network slice service continuity |
pCR revised to R3-205729 |
Huawei | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] |
R3-205689 | TP for TR38.382 on service continuity for slicing |
pCR revised to R3-205727 |
CMCC | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] |
R3-205727 | TP for TR38.382 on service continuity for slicing |
pCR revision of R3-205689 revised to R3-205783 |
CMCC | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] |
R3-205728 | CB: # RANSlicing2-Slice_Remapping_Scenarios - Summary of email discussion |
discussion revision of R3-205483 |
ZTE - moderator |
R3-109-e AI: 17.2 |
noted | [WTS] [JSN] | |||
R3-205729 | (TP for 38.832) Potential solutions to network slice service continuity |
pCR revision of R3-205646 |
Huawei | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
agreed | [WTS] [JSN] |
R3-205730 | CB: # RANSlicing3-Slice_Remapping_Solutions - Summary of email discussion |
discussion revision of R3-205484 |
Nokia - moderator |
R3-109-e AI: 17.2 |
noted | [WTS] [JSN] | |||
R3-205758 | LS on Enhancement of RAN Slicing |
LS out LS To: SA2 revised to R3-205802 |
Qualcomm | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
revised | [WTS] [JSN] | |
R3-205783 | TP for TR38.382 on service continuity for slicing |
pCR revision of R3-205727 |
CMCC | 38.832 0.0.0 | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
agreed | [WTS] [JSN] |
R3-205802 | LS on Enhancement of RAN Slicing |
LS out LS To: SA2 revision of R3-205758 |
Qualcomm | FS_NR_slice | Rel-17 |
R3-109-e AI: 17.2 |
agreed | [WTS] [JSN] |
32 documents (0.29601001739502 seconds)