Content for TR 23.861 Word version: 13.0.0
4 Use cases
5 Service requirements
6 Architectural requirements, assumptions, high level issues and design considerations
7 Solutions for multi access PDN connectivity and IP flow mobility
8 Evaluation of the Solutions
9 Conclusions
A Handling of multiple PDN connections
B Usage of IMS Service Continuity in conjunction with Multi Access PDN Connectivity
C Access information mapping SDF onto multiple access types
$ Change history
4 Use cases p. 11
5 Service requirements p. 14
6 Architectural requirements, assumptions, high level issues and design considerations p. 15
6.1 Architectural requirements p. 15
6.2 Architectural assumptions p. 15
6.3 High level issues and design considerations p. 17
7 Solutions for multi access PDN connectivity and IP flow mobility p. 18
7.1 IP flow mobility solutions for S2c/H1 (DSMIPv6) p. 18
7.1.1 Solution A: Routeing filters in DSMIPv6 p. 18
7.1.1.1 Overview p. 18
7.1.1.2 DSMIPv6 enhancements p. 18
7.1.1.3 PCC Enhancements p. 19
7.1.1.4 Flows p. 19
7.1.1.4.1 General p. 19
7.1.1.4.2 Addition of one access to the PDN connection p. 20
7.1.1.4.3 IP flow mobility p. 21
7.1.1.4.4 Removal of one access from the PDN connection p. 22
7.1.1.4.5 Addition of one access for multiple PDN connections to the same APN p. 24
7.1.1.5 Routeing Filters p. 24
7.2 IP flow mobility solutions for S2a (PMIPv6) p. 24
7.2.1 Solution A: Routeing filters in PMIPv6 p. 24
7.2.1.2 Addition of one access to the PDN connection p. 24
7.2.1.3 IP flow mobility p. 26
7.2.1.4 Detaching from an Access p. 27
7.2.2 Solution B: IP flow mobility based on PCC for Network Based Mobility Management Procedures p. 28
7.2.2.1 Additional Simultaneous PDN Connectivity over Different Access p. 28
7.2.2.2 Additional access Procedure to the PDN connection p. 28
7.2.2.2.1 General p. 28
7.2.2.2.2 PCC Enhancements p. 29
7.2.2.2.3 Additional access to the PDN connection with GTP-based S5 or S8 p. 29
7.2.2.2.4 Additional access to the PDN connection with PMIP-based S5 or S8 p. 31
7.2.2.2.5 Additional access to the PDN connection from Trusted non-3GPP access network with PMIP-based S2a p. 33
7.2.2.3 UE initiated IP flow mobility p. 34
7.2.2.3.1 General p. 34
7.2.2.3.2 IP flow mobility from trusted non-3GPP access with PMIP based S2a to 3GPP access with GTP based S5/S8 p. 35
7.2.2.3.3 IP flow mobility from trusted non-3GPP access with PMIP based S2a to 3GPP access with PMIP based S5/S8 p. 36
7.2.2.3.4 IP flow mobility from 3GPP access with GTP or PMIP based S5/S8 to non-3GPP access with PMIP based S2a p. 37
7.2.2.4 UE initiated Removal of one access from the PDN connection p. 39
7.2.2.4.1 General p. 39
7.2.2.4.2 UE initiated Removal of 3GPP access from the PDN connection (GTP-based) p. 39
7.2.2.4.3 UE initiated Removal of 3GPP access from the PDN connection (PMIP-based) p. 40
7.2.2.4.4 UE initiated Removal of non-3GPP access from the PDN connection (S2a PMIP-based) p. 41
7.2.2.5 Network-initiated Dynamic PCC p. 43
7.3 IP flow mobility solutions for S2a (GTP) p. 44
7.3.1 Issues and Design Considerations p. 44
7.3.2 Solution A: Control Plane signalling solution p. 44
7.3.2.1 Overview p. 45
7.3.2.1.1 General p. 45
7.3.2.1.2 NBIFOM capability discovery/negotiation p. 45
7.3.2.1.3 Routing rules considerations p. 45
7.3.2.1.4 Delivery of routing rules p. 46
7.3.2.1.5 Co-existence of UE-initiated and Network-initiated handling p. 46
7.3.2.1.6 PCC Interactions p. 46
7.3.2.2 System Impacts p. 47
7.3.2.2.1 3GPP RAN p. 47
7.3.2.2.2 UE p. 47
7.3.2.2.3 MME p. 47
7.3.2.2.4 S-GW p. 47
7.3.2.2.5 TWAN p. 47
7.3.2.2.6 P-GW p. 47
7.3.2.2.7 SGSN p. 48
7.3.2.2.8 PCC Enhancements p. 48
7.3.2.3 Flows p. 49
7.3.2.3.1 Initial PDN connection establishment over first access p. 49
7.3.2.3.2 Addition of one access to a PDN connection p. 51
7.3.2.3.3 IP flow mobility within a PDN connection p. 52
7.3.2.3.4 Removal of an access from a PDN connection p. 57
7.3.2.3.5 An access of a PDN connection becomes unusable p. 59
7.3.2.3.6 An access for a PDN connection becomes usable p. 61
7.4 IP flow mobility solutions for S2b (PMIPv6) p. 64
7.4.1 Issues and Design Considerations p. 64
7.4.1.1 Issues p. 64
7.4.2 Solution A: IP flow mobility routing rules negotiated via 3GPP access specific signalling p. 64
7.4.2.1 Overview p. 64
7.4.2.1.1 General p. 64
7.4.2.1.2 Routing Rules p. 64
7.4.2.2 System Impacts p. 65
7.4.2.2.1 RAN p. 65
7.4.2.2.2 UE p. 65
7.4.2.2.3 MME p. 65
7.4.2.2.4 S-GW p. 65
7.4.2.2.5 P-GW p. 65
7.4.2.2.6 PCC Enhancements p. 65
7.4.2.3 Flows p. 66
7.4.3 Solution B: IP flow mobility routing rules negotiated in both WLAN and 3GPP access p. 70
7.4.3.1 Overview p. 70
7.4.3.1.1 General p. 70
7.4.3.1.2 Routing Rules p. 70
7.4.3.2 System Impacts p. 71
7.4.3.3 Flows p. 71
7.5 IP flow mobility solutions for S2b (GTP) p. 77
7.5.1 Issues and Design Considerations p. 77
7.5.2 Solution A: IP flow mobility routing rules negotiated via 3GPP access specific signalling p. 78
7.5.2.1 Overview p. 78
7.5.2.1.1 General p. 78
7.5.2.1.2 Routing Rules p. 78
7.5.2.2 System Impacts p. 78
7.5.2.2.1 RAN p. 78
7.5.2.2.2 UE p. 78
7.5.2.2.3 MME p. 78
7.5.2.2.4 S-GW p. 78
7.5.2.2.5 P-GW p. 78
7.5.2.3 Flows p. 78
7.5.3 Solution B: IP flow mobility routing rules negotiated in both WLAN and 3GPP accesses p. 82
7.5.3.1 Overview p. 82
7.5.3.1.1 General p. 82
7.5.3.1.2 Routing Rules p. 82
7.5.3.2 System Impacts p. 82
7.5.3.3 Flows p. 82
7.5.4 Solution C - Merged Control Plane signalling solution for GTP-based S2b p. 86
7.5.4.1 Overview p. 86
7.5.4.1.1 General p. 86
7.5.4.1.2 Routing Rules p. 87
7.5.4.1.3 NBIFOM Capability Discovery over S2b p. 87
7.5.4.2 System Impacts p. 87
7.5.4.2.1 3GPP RAN p. 87
7.5.4.2.2 UE p. 87
7.5.4.2.3 MME p. 88
7.5.4.2.4 S-GW p. 88
7.5.4.2.5 ePDG p. 88
7.5.4.2.6 PGW p. 88
7.5.4.2.7 PCC Enhancements p. 88
7.5.4.2.8 SGSN p. 88
7.5.4.3 Signalling Flows p. 89
7.5.4.3.1 Initial PDN connection establishment over first access p. 89
7.5.4.3.2 Addition of one access to a PDN connection p. 89
7.5.4.3.3 IP flow mobility p. 91
7.5.4.3.4 Removal of one access p. 97
7.5.4.3.5 Loss of an access from a PDN connection in case of network-initiated IP flow mobility p. 101
7.6 Solutions based on User-Plane signalling p. 102
7.6.1 Solution 1 p. 102
7.6.1.1 Overview - without exchanging routing rules p. 102
7.6.1.1.1 General p. 102
7.6.1.1.2 NBIFOM capability discovery/negotiation p. 104
7.6.1.1.3 Routing rules considerations p. 104
7.6.1.1.4 Delivery of routing rules p. 104
7.6.1.1.5 Co-existence of UE-initiated and Network-initiated handling p. 104
7.6.1.1.6 PCC Interactions p. 104
7.6.1.1.7 Response to "Redirection" Request p. 104
7.6.1.2 System Impacts p. 105
7.6.1.3 Procedures p. 105
7.6.1.3.1 Initial PDN connection establishment over first access p. 105
7.6.1.3.2 Addition of one access to a PDN connection p. 106
7.6.1.3.3 IP Flow Mobility within a PDN connection p. 106
7.6.1.3.4 Removal of an access from a PDN connection p. 107
7.6.1.3.5 Loss of an access from a PDN connection p. 107
7.6.2 Solution 2 - IP Flow Management Protocol p. 107
7.6.2.1 Overview p. 107
7.6.2.1.1 General p. 108
7.6.2.1.2 NBIFOM capability discovery/negotiation p. 108
7.6.2.1.3 Routing rules considerations p. 108
7.6.2.1.4 Delivery of routing rules p. 109
7.6.2.1.5 Co-existence of UE-initiated and Network-initiated handling p. 109
7.6.2.1.7 Co-existence with ANDSF traffic steering p. 109
7.6.2.2 System Impacts p. 109
7.6.2.3 Procedures p. 110
7.7 IP flow mobility policies p. 116
7.7.1 Introduction p. 116
7.7.2 ANDSF enhancements p. 116
7.7.3 PCC based mechanism p. 117
7.7.3.1 Solution A: PCC rules related with the Access Type - Notifications related with the Access Type p. 117
7.7.3.1.1 Definitions p. 117
7.7.3.1.2 Overview p. 117
7.7.3.1.3 Void
7.7.3.1.4 Flows p. 119
7.7.3.1.5 Charging impacts p. 123
7.7.3.2 Solution B: Support of Traffic sharing for a SDF p. 123
7.7.3.2.1 Overview p. 123
7.7.3.3 Solution C: Support of APN-AMBR per Access Type p. 124
7.7.3.3.1 Overview p. 124
7.7.3.4 Solution D: Access Type depending on TWAN-Id p. 124
7.7.3.4.1 Overview p. 124
7.7.3.5 Solution E: PCC rules associating a SDF with multiple allowed Access Types p. 125
7.8 Co-existence of UE-initiated and Network-initiated p. 127
7.8.1 General p. 127
7.8.2 Solution A p. 127
7.8.3 Solution B p. 127
7.8.4 Solution C p. 128
7.8.5 Solution D p. 128
7.8.6 Solution-E: NBIFOM Operation Modes p. 129
7.8.6.1 General p. 129
7.8.6.2 Mode Selection p. 130
7.8.6.2.1 UE-Initiated Mode p. 131
7.8.6.2.2 NW-Initiated Mode p. 132
7.9 Co-existence with ANDSF IFOM rules p. 132
8 Evaluation of the Solutions p. 133
8.1 Evaluation of solutions for client based IFOM p. 133
8.2 Evaluation of solutions for NBIFOM p. 134
9 Conclusions p. 137
9.1 Conclusion of client based IFOM p. 137
9.2 Conclusion of NBIFOM p. 137
9.2.1 Working Assumptions p. 137
9.2.2 NBIFOM Rel-13 Conclusions p. 138
A Handling of multiple PDN connections p. 140
A.1 Multiple PDN connections to different APNs p. 140
A.1.1 Basic principles for simultaneous connectivity over multiple accesses p. 140
A.1.2 Scenarios p. 140
A.1.3 Architectural principles p. 140
A.1.4 Description of the impacts on TS 23.402 p. 141
A.1.5 Description of the impacts on TS 23.401 p. 144
A.1.6 PDN GW Identity Notification to AGW/ePDG p. 145
B Usage of IMS Service Continuity in conjunction with Multi Access PDN Connectivity p. 146
C Access information mapping SDF onto multiple access types p. 148
C.0 Overview p. 148
C.1 Access information mapping SDF onto a single access type p. 148
C.2 Access information mapping SDF onto a multiple access types p. 150
$ Change history p. 153
