Tech-invite   3GPPspecs   RFCs   SIP   Search in Tech-invite

21222324252627282931323334353637384142434445464849515255IntroTBsRELsRef‑PointsIDs?
Top   in Index   Prev   Next

TR 23.861 (SA2)
Network based IP Flow Mobility

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V13.0.0 (Wzip)  2015/06  153 p.

Rapporteur:  Miss So, Tricci

Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel-13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.

full Table of Contents for  TR 23.861  Word version:   13.0.0

 

Here   Top

 

1  ScopeWord-p. 9
2  References
3  Definitions and abbreviationsWord-p. 10
4  Use cases
5  Service requirementsWord-p. 14
6  Architectural requirements, assumptions, high level issues and design considerationsWord-p. 15
7  Solutions for multi access PDN connectivity and IP flow mobilityWord-p. 18
7.1  IP flow mobility solutions for S2c/H1 (DSMIPv6)
7.2  IP flow mobility solutions for S2a (PMIPv6)
7.2.1  Solution A: Routeing filters in PMIPv6
7.2.2  Solution B: IP flow mobility based on PCC for Network Based Mobility Management ProceduresWord-p. 28
7.2.2.1  Additional Simultaneous PDN Connectivity over Different Access
7.2.2.2  Additional access Procedure to the PDN connection
7.2.2.3  UE initiated IP flow mobilityWord-p. 34
7.2.2.4  UE initiated Removal of one access from the PDN connectionWord-p. 39
7.2.2.5  Network-initiated Dynamic PCCWord-p. 43
7.3  IP flow mobility solutions for S2a (GTP)
7.4  IP flow mobility solutions for S2b (PMIPv6)Word-p. 64
7.5  IP flow mobility solutions for S2b (GTP)
7.5.1  Issues and Design Considerations
7.5.2  Solution A: IP flow mobility routing rules negotiated via 3GPP access specific signallingWord-p. 78
7.5.3  Solution B: IP flow mobility routing rules negotiated in both WLAN and 3GPP accessesWord-p. 82
7.5.4  Solution C - Merged Control Plane signalling solution for GTP-based S2b
7.6  Solutions based on User-Plane signallingWord-p. 102
7.7  IP flow mobility policiesWord-p. 116
7.8  Co-existence of UE-initiated and Network-initiatedWord-p. 127
7.9  Co-existence with ANDSF IFOM rules
8  Evaluation of the Solutions
9  ConclusionsWord-p. 137
A  Handling of multiple PDN connectionsWord-p. 140
B  Usage of IMS Service Continuity in conjunction with Multi Access PDN ConnectivityWord-p. 146
C  Access information mapping SDF onto multiple access typesWord-p. 148
D  Change historyWord-p. 153

Up   Top