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.3
Solutions for Key Issue 3: Mobility framework
...
6.3
Solutions for Key Issue 3: Mobility framework
p. 140
6.3.1
Solution 3.1: High-level functions of the mobility framework
p. 140
6.3.1.1
Architecture description
p. 140
6.3.1.2
Function description
p. 141
6.3.1.3
Solution evaluation
p. 141
6.3.2
Solution 3.2: Mobility state framework
p. 142
6.3.2.1
Architecture description
p. 142
6.3.2.2
Function description
p. 143
6.3.2.3
Solution evaluation
p. 143
6.3.3
Solution 3.3: Solution for mobility framework with RAN level tracking
p. 143
6.3.3.1
Architecture description
p. 143
6.3.3.2
Function description
p. 144
6.3.3.3
Solution evaluation
p. 144
6.3.4
Void
6.3.5
Solution 3.5: Stateless Context Management for Data Network Sessions
p. 145
6.3.5.1
Architecture description
p. 145
6.3.5.1.2
Support for Infrequent Small User Data Service
p. 147
6.3.5.1.3
Support of CIoT User Plane Optimizations
p. 147
6.3.5.2
Function description
p. 147
6.3.5.2.1
Context Cookie Creation
p. 147
6.3.5.2.3
Mobile Originated Small Data Service Transfer with Context Cookie-based context verification
p. 149
6.3.5.2.4
Mobile Originated Small Data Transfer with Cookie-based context re-establishment
p. 150
6.3.5.2.4a
Connection Suspension and Cookie Generation for User Plane CIoT Optimisation
p. 151
6.3.5.2.5
Connection Resume for User Plane CIoT Optimisation
p. 151
6.3.5.2.6
Support of Scheduled Mobile Terminated Communications
p. 152
6.3.5.2.7
Support of Unscheduled Mobile Terminated Communications
p. 152
6.3.5.3
Solution evaluation
p. 153
6.3.6
Solution 3.6: Mobility states for UE with power consumption optimization
p. 153
6.3.6.1
Architecture description
p. 153
6.3.6.2
Function description
p. 153
6.3.6.3
Solution evaluation
p. 154
6.3.7
Solution 3.7: NextGen State Model
p. 154
6.3.7.1
General
p. 154
6.3.7.2
Architecture description
p. 154
6.3.7.2.1
NextGen Mobility Management (NMM)
p. 154
6.3.7.2.2
Void
6.3.7.2.3
NextGen Radio Resource Control (RRC)
p. 155
6.3.7.2.4
Overview of NMM, and RRC state models
p. 156
6.3.7.3
Functional description
p. 156
6.3.7.4
Solution evaluation
p. 157
6.3.8
Solution 3.8: Simplified mobility states for stationary UE and MO data transmission only UE
p. 157
6.3.8.1
Architecture description
p. 157
6.3.8.2
Function description
p. 157
6.3.8.2.1
Mobility states and corresponding transitions of stationary UE
p. 157
6.3.8.2.2
Mobility states and corresponding transitions of MO data transmission only UE
p. 158
6.3.8.3
Solution evaluation
p. 158
6.3.9
Solution 3.9: Mobility levels using Mobility and Session classes
p. 158
6.3.9.1
Architecture description
p. 159
6.3.9.2
Function description
p. 159
6.3.9.2.1
Mobility classes
p. 159
6.3.9.2.2
Session classes
p. 160
6.3.9.2.3
Assigning, controlling and enforcing Mobility and Session classes
p. 160
6.3.9.2.4
Mobility aspects and how to handle roaming
p. 161
6.3.9.3
Solution evaluation
p. 162
6.3.10
Solution 3.10: RAN Specific paging for UE in CN connected mode.
p. 162
6.3.10.1
Architecture description
p. 162
6.3.10.2
Function description
p. 163
6.3.10.2.1
Downlink NG1 Signalling Triggered RAN Specific Paging.
p. 163
6.3.10.2.2
Downlink NG3 data Triggered RAN Specific Paging
p. 163
6.3.10.2.3
Core Network Assisted RAN Specific Paging Retry
p. 164
6.3.10.3
Solution evaluation
p. 166
6.3.11
Solution 3.11: Solution for dynamic mobility management
p. 166
6.3.11.1
Mobility categories
p. 166
6.3.11.2
Functional description
p. 166
6.3.11.2.1
Dynamic mobility management in IDLE mode
p. 166
6.3.11.2.2
Differences from existing solutions
p. 167
6.3.11.3
Solution Evaluation
p. 167
6.3.12
Solution 3.12: Solution for UE reachability in power saving state
p. 167
6.3.12.1
Architecture description
p. 167
6.3.12.2
Function description
p. 168
6.3.12.3
Solution evaluation
p. 169
6.3.13
Solution 3.13: Solution for mobility framework with split Location Tracking Function
p. 169
6.3.13.1
Architecture description
p. 169
6.3.13.2
Function description
p. 169
6.3.14
Solution 3.14: Solution for determining UE mobility level
p. 170
6.3.14.1
General description
p. 171
6.3.14.2
Function description
p. 171
6.3.14.3
Solution evaluation
p. 172
6.3.15
Solution 3.15: Solution to support different levels of mobility
p. 172
6.3.15.1
Mobility Levels Definition
p. 172
6.3.15.2
Function description
p. 175
6.3.15.3
Solution evaluation
p. 176
6.3.16
Solution 3.16: Limited & Unlimited UE mobility level
p. 176
6.3.16.1
Architecture description
p. 177
6.3.16.2
Function description
p. 177
6.3.16.3
Solution evaluation
p. 179
6.3.17
Solution 3.17: Support for Idle Mode Mobility capabilities
p. 179
6.3.17.1
Architecture Description
p. 179
6.3.17.2
Function description
p. 181
6.3.17.3
Solution Evaluation
p. 181
6.3.18
Solution 3.18: Mobility procedure
p. 181
6.3.18.1
Architecture description
p. 181
6.3.18.2
Function description
p. 181
6.3.18.2.1
Registration procedure
p. 182
6.3.18.2.2
UE Status Update procedure
p. 183
6.3.18.3
Solution evaluation
p. 183
6.3.19
Solution 3.19: Solution to activate RRC inactive state
p. 184
6.3.19.1
Architecture description
p. 184
6.3.19.2
Function description
p. 184
6.3.19.2.1
Service Activation Procedure
p. 184
6.3.19.3
Solution evaluation
p. 185
6.3.20
Solution 3.20: Solution for UE reachability for devices with only MO-communication
p. 185
6.3.20.1
Architecture description
p. 185
6.3.20.2
Function description
p. 185
6.3.20.3
Solution evaluation
p. 186
6.3.21
Solution 3.21: Solution for explicit signalling to limit idle mode procedures
p. 186
6.3.21.1
General description
p. 187
6.3.21.2
Functional description
p. 187
6.3.21.2.1
Limited Reachability
p. 187
6.3.21.2.2
Limited mobility tracking
p. 187
6.3.21.2.3
Signalling Flows
p. 187
6.3.21.3
Solution Evaluation
p. 188
6.3.22
Solution 3.22: Applying customized NextGen mobility states
p. 188
6.3.22.1
Architecture description
p. 188
6.3.22.2
Function description
p. 188
6.3.22.2.1
Procedure of enabling customized mobility states
p. 189
6.3.22.3
Solution evaluation
p. 190
6.3.23
Solution 3.23: Two layers Tracking Area handling
p. 190
6.3.23.1
Architecture description
p. 190
6.3.23.2
Function description
p. 191
6.3.23.3
Solution evaluation
p. 191
6.3.24
Solution 3.24: Mobility pattern based mobility management
p. 191
6.3.24.1
General description
p. 191
6.3.24.2
Function description
p. 192
6.3.24.3
Solution evaluation
p. 193
6.3.25
UE reachability management in Inactive mode
p. 193
6.3.25.1
Architecture description
p. 193
6.3.25.2
Function description
p. 194
6.3.25.2.1
Common Functional Elements for all approaches
p. 194
6.3.25.2.2
Functional elements necessary if the RAN paging area is configured on NAS level (Tracking Area approach)
p. 198
6.3.26
Solution 3.26: Intra-RAT HO procedure
p. 199
6.3.26.1
Architecture Description
p. 199
6.3.26.2
Function description
p. 201
6.3.26.2.2
Inter-NextGen HO procedure
p. 202
6.3.27
Solution 3.27: Multiple level Tracking Areas handling
p. 203
6.3.27.1
Architecture description
p. 203
6.3.27.2
Function description
p. 204
6.3.27.2.1
Multiple level Tracking Area Allocation
p. 204
6.3.27.2.2
Multiple level Tracking Area Update in the UE
p. 205
6.3.27.2.3
Reachability Management for UE in IDLE state
p. 205
6.3.27.3
Solution evaluation
p. 205