Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.799
Word version: 14.0.0
1…
4…
6…
6.3
6.4
6.5…
6.10…
7…
6
Solutions
6.1
Solutions for Key Issue 1: Support of network slicing
6.2
Solutions for Key Issue 2: QoS framework
...
6
Solutions
p. 51
6.1
Solutions for Key Issue 1: Support of network slicing
p. 51
6.1.1
Solution 1.1: Network Slicing without Slicing the radio
p. 51
6.1.1.1
Architecture description
p. 51
6.1.1.2
Function description
p. 53
6.1.1.3
Solution evaluation
p. 58
6.1.2
Solution 1.2: Network slice selection
p. 58
6.1.2.1
Architecture description
p. 60
6.1.2.1.1
Network Slice and Network Function selection
p. 60
6.1.2.2
Function description
p. 63
6.1.2.2.1
Functions.
p. 63
6.1.2.2.2
Reference points
p. 63
6.1.2.2.3
High level operation description
p. 63
6.1.2.2.4
Definitions used in the solution
p. 65
6.1.2.2.5
Example procedures
p. 66
6.1.2.3
Solution evaluation
p. 73
6.1.3
Solution 1.3: Support of multiple connections to multiple Network Slices
p. 73
6.1.3.1
Architecture description
p. 73
6.1.3.2
Function description
p. 77
6.1.3.3
Solution evaluation
p. 79
6.1.4
Void
6.1.5
Solution 1.5: Selection of a network slice instance
p. 79
6.1.5.1
Terminology and modelling
p. 79
6.1.5.2
Architecture description
p. 80
6.1.5.3
Function description
p. 81
6.1.5.4
Solution evaluation
p. 83
6.1.6
Solution 1.6: Slice Instance ID based Network Slice Selection
p. 83
6.1.6.1
Architecture description
p. 84
6.1.6.2
Function description
p. 84
6.1.6.2.1
Definitions and functions
p. 84
6.1.6.2.2
Common Network Functions
p. 85
6.1.6.2.3
The Attach procedure
p. 85
6.1.6.2.4
Slice Instance ID update due to subscription change
p. 87
6.1.6.3
Solution evaluation
p. 87
6.1.7
Solution 1.7: Network Slice Selection based on Usage Class
p. 87
6.1.7.1
Architecture description
p. 87
6.1.7.2
Solution evaluation
p. 89
6.1.8
Solution 1.8: Network slice instance reselection
p. 89
6.1.8.1
Definition and categorization of slice reselection
p. 89
6.1.8.2
Scenarios for slice reselection
p. 90
6.1.8.3
Function description
p. 91
6.1.8.3.1
Intra C-CPF Network Slice Change
p. 91
6.1.8.3.2
Inter C-CPF Network Slice Change
p. 92
6.1.8.4
Solution evaluation
p. 92
6.1.9
Solution 1.9: Multiple Independent Slices per UE
p. 92
6.1.9.1
Architecture description
p. 92
6.1.9.2
Signalling Procedures
p. 94
6.1.9.2.1
Attach Procedures
p. 94
6.1.9.2.2
Routing Area Update Procedure
p. 97
6.1.9.2.3
Detach Procedure
p. 98
6.1.9.3
Solution evaluation
p. 98
6.1.10
Solution 1.10: Roaming architecture for Network Slicing based on solution#2
p. 98
6.1.10.1
-
p. 99
6.1.10.1.1
Basic Non-roaming architecture
p. 99
6.1.10.1.2
Home-routed roaming architecture
p. 99
6.1.10.1.3
Local breakout roaming architecture supporting Home PLMN Application Function
p. 100
6.1.10.1.4
Local breakout roaming architecture supporting Home PLMN Application Function
p. 101
6.1.10.2
Solution evaluation
p. 101
6.1.11
Solution 1.11: Network Slice Instance Selection and Association
p. 101
6.1.11.1
Architecture description
p. 101
6.1.11.2
Function description
p. 102
6.1.11.2.1
Network slice instance selection and association procedure
p. 102
6.1.11.3
Solution evaluation
p. 104
6.2
Solutions for Key Issue 2: QoS framework
p. 105
6.2.1
Solution 2.1: Per PDU Flow QoS Model
p. 105
6.2.1.1
Architecture description
p. 105
6.2.1.1.1
Relation between PDU Flow and Service Data Flow
p. 107
6.2.1.1.2
Application requirements input
p. 108
6.2.1.1.3
Network Authorized QoS parameters
p. 109
6.2.1.2
Function description
p. 110
6.2.1.2.1
QoS Authorization at PDU session establishment
p. 110
6.2.1.2.2
QoS Authorization based on application requirements
p. 111
6.2.1.3
Solution evaluation
p. 112
6.2.1.3.1
Solution comparison to the existing framework
p. 112
6.2.2
Solution 2.2: Flow based QoS framework
p. 113
6.2.2.1
Architecture description
p. 113
6.2.2.2
Function description
p. 116
6.2.2.3
Solution evaluation
p. 119
6.2.3
Solution 2.3: Content Aware QoS Framework
p. 119
6.2.3.1
Overview
p. 119
6.2.3.2
Architecture description
p. 120
6.2.3.3
QoS related information exchanged between network functions
p. 122
6.2.3.4
Function description
p. 125
6.2.3.5
Solution evaluation
p. 126
6.2.4
Solution 2.4: QoS model for QoS Authorization and Request
p. 126
6.2.4.1
Architecture description
p. 126
6.2.4.1.1
Functional Architecture
p. 126
6.2.4.2
Function description
p. 126
6.2.4.2.1
QoS Pre-Authorization at PDU Session Establishment
p. 126
6.2.4.2.2
QoS Establishment
p. 126
6.2.5
Solution 2.5: QoS model for flexible traffic differentiation
p. 128
6.2.5.1
Architecture description
p. 128
6.2.5.1.1
Functional Architecture
p. 128
6.2.5.1.2
Applications Requirements Input
p. 128
6.2.5.1.3
Packet Markings for Traffic Differentiation
p. 128
6.2.5.2
Function description
p. 130
6.2.5.2.1
Dynamic QoS Modification
p. 130
6.2.6
Solution 2.6: QoS ID solution
p. 130
6.2.6.1
Architecture description
p. 130
6.2.6.2
Function description
p. 131
6.2.6.3
Solution evaluation
p. 132
6.2.7
Solution 2.7: QoS framework for resource management for Mission Critical Group Communications
p. 132
6.2.7.1
Architecture Description
p. 132
6.2.7.2
Functional Description
p. 133
6.2.7.3
Solution evaluation
p. 134
6.2.8
Solution 2.8: Application-based uplink traffic identification
p. 134
6.2.8.1
Solution Description
p. 134
6.2.8.2
Function description
p. 135
6.2.8.3
Solution evaluation
p. 135
6.2.9
Solution 2.9: NextGen Bearer based QoS control model
p. 135
6.2.9.1
Architecture description
p. 135
6.2.9.1.1
NextGen Bearer level QoS parameters
p. 136
6.2.9.2
Function description
p. 138
6.2.9.2.1
NextGen Non-GBR Bearer established at PDU session establishment
p. 138
6.2.9.2.2
NextGen GBR Bearer establishment based on the application server request
p. 139
6.2.9.3
Solution evaluation
p. 139