Content for TR 23.799 Word version: 14.0.0
6.5 Solutions for Key Issue 5: Enabling (re)selection of efficient user plane paths
6.6 Solutions for Key Issue 6: Support for session and service continuity
6.7 Solutions for Key Issue 7: Network function granularity and interactions between them
6.8 Solutions for Key Issue 8: Next Generation core and access - functional division and interface
...
...
6.5 Solutions for Key Issue 5: Enabling (re)selection of efficient user plane paths p. 279
6.5.1 Solution 5.1: UP Functions selection p. 279
6.5.1.1 Architecture description p. 279
6.5.1.2 Function description p. 279
6.5.1.3 Solution evaluation p. 280
6.5.2 Solution 5.2: Solution to support Session continuity to enable (re)selection of efficient user plane paths p. 280
6.5.2.1 Architecture description p. 280
6.5.2.2 Function description p. 281
6.5.2.2.1 General p. 281
6.5.2.2.2 Mobility aspects p. 282
6.5.2.3 Solution evaluation p. 284
6.5.3 Solution 5.3: Re-selection of user-plane path based on UE traffic pattern p. 284
6.5.3.1 Architecture Description p. 284
6.5.3.2 Function description p. 285
6.5.3.3 Solution Evaluation p. 286
6.5.4 Solution 5.4: Multiple Tunnel based traffic offload p. 286
6.5.4.1 Architecture Description p. 286
6.5.4.2 Function description p. 287
6.5.4.3 Solution Evaluation p. 289
6.5.5 Solution 5.5: Application-aware UP Path (Re)selection p. 289
6.6 Solutions for Key Issue 6: Support for session and service continuity p. 294
6.6.1 Solution 6.1: Session and service continuity framework p. 294
6.6.1.1 Architecture description p. 294
6.6.1.1.1 Overview p. 294
6.6.1.1.2 Assumptions p. 294
6.6.1.1.3 Session and service continuity modes p. 294
6.6.1.1.4 Solution principles p. 295
6.6.1.1.5 How the UE determines the required SSC mode p. 297
6.6.1.2 Function description p. 298
6.6.1.2.1 PDU session establishment/release triggered by handover procedure p. 298
6.6.1.2.2 Service continuity call flows p. 299
6.6.1.2.3 CN-provided trigger followed by UE-requested PDU Session (SSC mode 3) p. 299
6.6.1.2.4 CN-prepared PDU Session modification followed by notification to UE (SSC mode 3) p. 300
6.6.1.2.5 CN-provided trigger followed by UE-requested PDU Session establishment (SSC mode 2) p. 301
6.6.1.2.6 CN-prepared PDU Session modification followed by notification to UE (SSC mode 2) p. 301
6.6.1.3 Solution evaluation p. 302
6.6.2 Solution 6.2: Mobility on Demand using Mobility and Session classes p. 302
6.6.3 Solution 6.3: Multi-homing over multiple PDU sessions with network-provided routing rules p. 303
6.7 Solutions for Key Issue 7: Network function granularity and interactions between them p. 304
6.7.1 Solution 7.1: Interconnection and Routing Function (IRF) based network function interconnection model p. 304
6.7.1.1 General (Assumptions and applicability) p. 304
6.7.1.2 Architectural description p. 305
6.7.1.2.1 Reference model p. 305
6.7.1.2.2 High level principles p. 306
6.7.1.3 Functional description p. 306
6.7.1.3.1 General p. 306
6.7.1.3.2 Functions of Interconnection & Routing Function (IRF) p. 306
6.7.1.3.3 Sample binding repository of IRF p. 307
6.7.1.4 Sample call flows p. 308
6.7.1.4.1 General p. 308
6.7.1.4.2 Basic routing of message between two NFs p. 308
6.7.1.4.3 Support for subscribe-notify type of mechanism p. 309
6.7.1.4.4 NF binding management at IRF p. 309
6.7.1.5 Solution evaluation p. 309
6.7.2 Solution 7.2: The interconnection of NFs and discovery of NFs via NF Repository Function p. 309
6.7.2.1 Architecture description p. 309
6.7.2.2 Function description p. 310
6.7.2.2.1 General model of Network Function p. 310
6.7.2.2.3 General model for the interconnection of CP NFs p. 310
6.7.2.2.4 NF Discovery p. 311
6.7.2.2.5 NF Monitor p. 313
6.7.2.3 Solution evaluation p. 314
6.7.3 Solution 7.3: Interconnection Function Solution p. 314
6.7.3.1 Architecture description p. 314
6.7.3.2 Function description p. 315
6.7.3.3 Solution evaluation p. 317
6.7.4 Solution 7.4: A Framework of Modular Network Functions p. 317
6.7.4.1 Reference Model p. 317
6.7.4.2 Functional Description p. 317
6.7.4.3 Composition of Network Function p. 317
6.7.5 Solution 7.5: Control Plane Interconnection model with a Data Layer p. 318
6.7.5.1 Architecture description p. 318
6.7.5.1.1 Reference model p. 318
6.7.5.2 Architecture principles p. 320
6.7.5.3 Function description p. 320
6.7.5.4 Information exchange across different types of Network functions for capability exposure p. 321
6.7.5.5 Information exchange across same types of Network functions p. 322
6.7.5.5.1 Registration procedure p. 323
6.7.5.5.2 Handover Procedure p. 324
6.7.5.5.3 Service Request Procedure p. 325
6.7.5.5.4 MMF Failover p. 326
6.7.5.5.5 Context Clean-up scenario p. 327
6.7.5.5.6 Data Layer and Network slicing p. 327
6.7.5.6 Stateless Network Function p. 328
6.7.5.7 Solution evaluation p. 328
6.8 Solutions for Key Issue 8: Next Generation core and access - functional division and interface p. 328
6.8.1 Solution 8.1: Solution for Common Core support p. 328
6.8.1.1 Architecture description p. 328
6.8.1.2 Function description p. 330
6.8.1.3 Solution evaluation p. 330
6.8.2 Solution 8.2: Architecture for decoupling and independent evolution of CN and AN p. 330
6.8.2.1 Architecture description p. 330
6.8.2.2 Function description p. 333
6.8.2.2.1 General p. 333
6.8.2.2.2 EAP-over-EAPoL transport between UE and WLAN access point p. 334
6.8.2.2.3 IKEv2 transport between UE and N3ASF p. 336
6.8.2.2.4 PANA transport between UE and N3ASF p. 337
6.8.2.3 Solution evaluation p. 337
6.8.3 Solution 8.3: Alternative A for the interface between UE and Next Generation Core p. 338
6.8.3.1 Architecture description p. 338
6.8.3.2 Function description p. 338
6.8.3.3 Solution evaluation p. 339
6.8.4 Solution 8.4: Alternative B for the interface between UE and Next Generation Core p. 339
6.8.4.1 Architecture description p. 339
6.8.4.2 Function description p. 340
6.8.4.3 Solution evaluation p. 340
6.8.5 Solution 8.5: Alternative C for the interface between UE and Next Generation Core p. 341
6.8.5.1 Architecture description p. 341
6.8.5.2 Function description p. 341
6.8.5.3 Solution evaluation p. 341
6.8.6 Solution 8.6: Architecture for support of untrusted Non-3GPP Access p. 342
6.8.6.1 Architecture description p. 342
6.8.6.2 Function description p. 343
6.8.6.2.1 Initial attach procedure for Untrusted N3GPP Access p. 345
6.8.6.2.2 PDU session establishment via untrusted N3GPP access p. 348
6.8.6.3 Solution evaluation p. 349
6.8.7 Solution 8.7: Support standalone non-3GPP access via NG2/NG3 p. 350
6.8.7.1 Architecture description p. 350
6.8.7.2 Function description p. 351
6.8.7.2.1 Overview p. 351
6.8.7.2.2 Protocol architecture for Trusted non-3GPP access p. 352
6.8.7.2.3 Protocol architecture for Untrusted non-3GPP access p. 354
6.8.7.2.4 Attach via Trusted Non-3GPP Access p. 355
6.8.7.2.5 PDU session setup via Trusted Non-3GPP Access p. 358
6.8.7.2.6 Attach via Untrusted Non-3GPP Access p. 359
6.8.7.2.7 PDU session setup via Untrusted Non-3GPP Access p. 361
6.8.7.3 Solution evaluation p. 361
6.8.8 Solution 8.8: Architecture for support of untrusted Non 3GPP access p. 361
6.8.8.0 Overview p. 361
6.8.8.1 Architecture description p. 362
6.8.8.2 Function description p. 363
6.8.8.2.1 Initial attach procedure for Untrusted N3GPP Access p. 366
6.8.8.2.2 PDU session establishment via untrusted N3GPP access p. 369
6.8.8.3 Solution evaluation p. 370
6.8.9 Solution 8.9: Transfer NAS in IKEv2 for untrusted non-3GPP access p. 370
6.8.9.0 Overview p. 370
6.8.9.1 Architecture description p. 370
6.8.9.2 Function description p. 370
6.8.9.3 Solution evaluation p. 372
6.9 Void
