Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 23.861  Word version:  13.0.0

Top   Top   None   None   Next
1…   4…


1  Scopep. 9

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.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel 10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel 13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel 13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel 13 consider the following aspects:
  • The support of a PDN Connection active over multiple accesses simultaneously.
  • The association of one or multiple IP flows belonging to a PDN connection to an access system.
  • The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
  • The triggers for IP flow mobility in the UE and the network.
  • UE-initiated and network-initiated NBIFOM.
  • The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used.

2  Referencesp. 9

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 23.402: "Architecture enhancements for non-3GPP accesses".
TS 23.327: "Mobility between 3GPP-WLAN interworking and 3GPP systems".
draft-ietf-monami6-multiplecoa-11.txt,  "Multiple Care-of Addresses Registration", work in progress.
draft-ietf-mext-flow-binding-01.txt,  "Flow Bindings in Mobile IPv6 and Nemo Basic Support", work in progress.
draft-ietf-mext-nemo-v4traversal-07.txt,  "Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)", work in progress.
TS 23.203: "Policy and Charging Control Architecture".
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
draft-ietf-netext-pmipv6-flowmob-04.txt,  " Proxy Mobile IPv6 Extensions to Support Flow Mobility" , work in progress.
RFC 5996,  "Internet Key Exchange Protocol Version 2 (IKEv2)".
TS 33.402: "3GPP System Architecture Evolution: Security aspects of non-3GPP accesses".
TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3".
TS 23.261: " IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2".
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
RFC 7077:  "Update Notifications for Proxy Mobile IPv6".
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1 AP)".
TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".

3  Definitions and abbreviationsp. 10

3.1  Definitionsp. 10

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Routing filter:
A set of packet flow IP header parameter values/ranges used to identify IP flows for routing purposes.
routing address:
A routable IP address. In DSMIPv6 this is either the CoA (visited link case) or the HoA (in home link case).
routing access type:
Type of access network (e.g. 3GPP or WLAN) that the P-GW routes the UE's IP flow.
routing rule:
The association of routing filter with a routing address or routing access type.
IFOM based on network mobility protocols (GTP or PMIP).
UE-initiated NBIFOM:
IFOM based on network mobility protocols (GTP and PMIP) where the UE initiates the IP flow mobility.
Network-initiated NBIFOM:
IFOM based on network mobility protocols (GTP and PMIP) where the network initiates the IP flow mobility.
Multi-access PDN connection:
A PDN connection whose traffic can be routed over either a 3GPP access or a WLAN access or both. Each IP flow is routed at any single time only over one access.

3.2  Abbreviationsp. 11

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Network-based IP flow mobility
Multi-connection mode
Single-connection mode
Transparent Single-connection mode

Up   Top   ToC