3GPP TS V ( )

Transcription

1 TS V ( ) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP flow mobility and seamless Wirless Local Area Network (WLAN) offload; Stage 2 (Release 10) The present document has been developed within the 3rd Generation Partnership Project ( TM ) and may be further elaborated for the purposes of. The present document has not been subject to any approval process by the Organizational Partners and shall not be implemented. This Specification is provided for future development work within only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the TM system should be obtained via the Organizational Partners' Publications Offices.

2 2 TS V ( ) Keywords EPS, IP flow mobility, Dual-Stack Mobile IPv6 (DSMIPv6), WLAN, Non- accesses. Postal address support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: Fax: Internet Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 2010, Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members is a Trade Mark of ETSI registered for the benefit of its Members and of the Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association

3 3 TS V ( ) Contents Foreword Scope References Definitions and abbreviations Definitions Abbreviations Architecture model and concepts General concepts Architecture reference model Non-roaming architecture Roaming architecture High level functions S2c and H1 extensions for IP flow mobility General DSMIPv6 enhancements Policy provisioning for Inter-system mobility and WLAN offload Policy Control and Charging support Local Operating Environment Information IP Flow Mobility procedures and flows General PDN connection establishment over first access General PDN connection establishment over access PDN connection establishment over WLAN Addition of an access to a PDN connection General Addition of WLAN access Addition of access IP flow mobility within a PDN connection General IP flow mobility within a PDN connection with network-initiated dynamic PCC IP flow mobility within a PDN connection with UE-initiated resource request Removal of an access from a PDN connection Addition of one access for multiple PDN connections to the same APN Detach and PDN disconnection procedures Annex A (informative): Change history... 20

4 4 TS V ( ) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

5 5 TS V ( ) 1 Scope This document specifies the Stage 2 system description for IP flow mobility between a and a WLAN. The technical solution is based on the working principles of DSMIPv6 [2] and it is applicable to both the Evolved Packet System and the I-WLAN mobility architecture. The specification covers the system description of seamless WLAN offload and IP flow mobility between and WLAN as well as the respective interactions with the PCC and ANDSF frameworks. The system description for non seamless WLAN offload is covered in TS [3]. This document specifies also the detailed extensions to S2c [3] and H1 [4] reference points for IP flow mobility. The extensions to the PCC and to the ANDSF framework are specified respectively in TS [5] and in TS [3]. 2 References 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 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. [1] TR : "Vocabulary for Specifications". [2] IETF RFC 5555 (June 2009): "Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)". [3] TS : "Architecture enhancements for non- accesses". [4] TS : "Mobility between -Wireless Local Area Network (WLAN) interworking and systems". [5] TS : "Policy and Charging Control architecture". [6] IETF RFC 4877 (April 2007): "Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture". [7] IETF RFC 5648 (October 2009): "Multiple Care-of Addresses Registration". [8] IETF Internet-Draft, draft-ietf-mext-flow-binding-04.txt, "Flow Bindings in Mobile IPv6 and Nemo Basic Support", work in progress. [9] TS : " System to Wireless Local Area Network (WLAN) Interworking; System Description". [10] TS : "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". [11] TS : "General Packet Radio Service (GPRS); Service description; Stage 2". [12] IETF Internet-Draft, draft-ietf-mext-binary-ts-02.txt, "Traffic Selectors for Flow Bindings", work in progress. Editor's note: The above Internet-Draft cannot be formally referenced until it is published as an RFC.

6 6 TS V ( ) 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR [1] and the following apply. The following terms used in this Technical Specification are defined in RFC 3775 [2]: Home Address, Care-of Address, binding cache, binding cache entry. The following terms used in this Technical Specification are defined in TS [3]: Home network prefix. Home Agent: The Home Agent functionality consists in the DSMIPv6 anchor point functionality described in RFC 5555 [2] and in RFC 4877 [6] and the extensions defined in RFC 5648 [7] and IETF I-D draft-ietf-mext-flowbinding [8]. As per TS [3], the HA functionality is located in the PDN Gateway. As per TS [4] the HA functionality can be either a standalone entity or co-located with the GGSN or with the PDG. Local Operating Environment Information: This is a set of implementation specific parameters which describe the local environment in which the UE is operating. routing address: A routable IP address. In DSMIPv6 this is either the CoA (visited link case) or the HoA (in home link case). routing filter: A set of packet flow IP header parameter values/ranges used to identify one or more IP flows for routing purposes. routing rule: The association of a routing filter with a routing address. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR [1] and the following apply. BID CoA DSMIPv6 EPC epdg EPS FID GW HA HoA UE Binding Identifier Care-of Address Dual-Stack Mobile IPv6 Evolved Packet Core Evolved Packet Data Gateway Evolved Packet System Flow Identifier Gateway Home Agent Home Address User Equipment 4 Architecture model and concepts 4.1 General concepts This document specifies a mechanism for a UE to simultaneously connect to access and WLAN and exchange different IP flows belonging to the same PDN connection through different accesses. The mechanism also enables seamless IP flow mobility, with IP flows belonging to the same or different applications being moved seamlessly between a access and WLAN. The solution allows the operator to indicate how the IP flows are routed through the available access systems and to selectively offload some traffic (e.g. best effort traffic) to WLAN while using UTRAN or E-UTRAN for other traffic (e.g. traffic with specific QoS requirements). This is usually referred to as WLAN offload.

7 7 TS V ( ) The technical solution is based on DSMIPv6 [2] and is applicable to both the Evolved Packet System and the I-WLAN mobility architecture. Since the solution is based on DSMIPv6, IP address preservation and session continuity is provided when moving IP flows from one access to the other. 4.2 Architecture reference model Non-roaming architecture The baseline architecture reference model for IP flow mobility when EPS is deployed in the non roaming case is specified in TS [3]. The baseline architecture reference model for IP flow mobility when I-WLAN mobility is deployed in the non roaming case is specified in TS [4]. The baseline Non-roaming architecture for I-WLAN is specified in TS [9]. The baseline Non-roaming architecture for ANDSF is specified in TS [3] Roaming architecture The baseline architecture reference model for IP flow mobility when EPS is deployed in the roaming case is specified in TS [3]. The baseline architecture reference model for IP flow mobility when I-WLAN mobility is deployed in the roaming case is specified in TS [4]. The baseline roaming architecture for I-WLAN is specified in TS [9]. The baseline roaming architecture for ANDSF is specified in TS [3]. 4.3 High level functions S2c and H1 extensions for IP flow mobility General The granularity of access system connectivity and inter system mobility based on TS and is per PDN connection basis. This implies that when a handover occurs all the IP flows belonging to the same PDN connection are moved from the source access system to the target access system. With IP flow mobility it is possible to have a finer granularity in access system connectivity and inter system mobility: the handover procedures can be applied to a single or multiple IP flows belonging to the same PDN connection. This implies that some IP flows of one PDN connection can be routed via one access system while simultaneously some IP flows of the same PDN connection can be routed via another access system. To achieve IP flow mobility the inter-system mobility signalling is enhanced in order to carry routing filters. The extensions to DSMIPv6 mobility signalling needed to carry routing filters when the UE is connected to multiple accesses simultaneously are specified in RFC 5648 [7] and IETF draft-ietf-mext-flow-binding [8] and are applicable to both S2c and H DSMIPv6 enhancements When a UE configures different IPv6 global addresses on multiple accesses, it can register these addresses with the HA as CoAs using multiple bindings as specified in IETF RFC 5648 [7]. To register multiple bindings, the UE generates a Binding ID (BID) for each CoA and stores the BID in the binding update list. The UE then registers its CoAs by sending a Binding Update (BU) with a Binding Identifier mobility option. The BID is included in the Binding Identifier mobility option. When the UE is on the home link in one of the access, the CoA field is set to the HoA in the respective BID.

8 8 TS V ( ) When the HA receives the BU with a Binding Identifier mobility option, it copies the BID from the mobility option to the corresponding field in the Binding Cache entry. If there is an existing Binding Cache entry for the UE, and if the BID in the BU does not match the one with the existing entry, the HA creates a new Binding Cache entry for the new CoA and BID. Based on this extension, a typical Binding Cache in HA according to this specification in case the UE is not on the home link is shown in Table NOTE: A BID is only unique for a given HoA, i.e. different mobile nodes can use the same BID value. Table : Binding Cache in HA supporting multiple CoAs registration Home Address Care-of Address Binding ID Priority HoA1 CoA1 BID1 x HoA1 CoA2 BID2 y In order to route IP flows through a specific access, the UE needs to request to store routing filters for that access at the HA: the UE includes the Flow Identification (FID) mobility option in the BU message as defined in IETF draft-ietfmext-flow-binding [8]. The FID option defines a routing rule which contains a routing filter and a routing address. The routing address (either CoA or HoA) is indicated by the BID. The routing filter is included in the DSMIPv6 signalling as described in draft-ietf-mext-binary-ts [12]. The routing filters are unidirectional and can be different for uplink and downlink traffic. It is assumed that between UE and the Home Agent function there is always a default routing address via which packets not matching any specific routing filter are routed. The UE provides a relative priority with each BID, where the BID with the highest priority is the default route. The UE may update the priority of a BID during IP flow mobility procedures. To install/remove/move an IP flow, the UE shall create a new IP flow binding or remove/update the IP flow binding at the HA by using DSMIPv6 signalling as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8]. An example of a typical Binding Cache in HA with routing filters is shown in Table Note that a FID is only unique for a given HoA, i.e. different PDN connections can use the same FID value. Each flow binding entry contains a relative priority. Table : Binding Cache in HA supporting flow bindings Home Routing Binding ID BID Priority Flow ID FID Priority Routing Filter Address Address HoA1 CoA1 BID1 x FID1 a Description of IP flows FID2 b Description of IP flows HoA1 CoA2 BID2 y FID3 NOTE: This clause shows only a conceptual representation of the binding cache. The actual format is implementation specific Policy provisioning for Inter-system mobility and WLAN offload As specified in TS [3], the UE may be provisioned with two sets of information: - Inter System Mobility policies. - Access Network Discovery Information. Inter-system mobility policies and access network discovery information are provided to the UE by the operator, either through the ANDSF or by means of static pre-configuration of the UE. In order to allow the operator to indicate to the UE through which access technology IP flows are expected to be routed, IP flow class specific inter system mobility policies are introduced in TS [3]. Such policies can be defined per APN, per IP flow class under any APN or per IP flow class under a specific APN.

9 9 TS V ( ) For IP flows that are routed over WLAN, the IP flow class specific inter system mobility policies also specify whether the traffic should be routed through the HA or directly via the WLAN access, bypassing the HA. The normative procedures for ANDSF and UE can be found in TS [3]. Editor's note: The normative procedures for policy provisioning for inter-system mobility and WLAN offload are expected to be included in TS as the work progresses Policy Control and Charging support When IP flow mobility is used and PCC is deployed, the PCC architecture is enhanced to handle multiple simultaneous access connections for a single IP-CAN session. These enhancements require the PDN GW to keep the PCRF up to date about the current routing address for each IP flow. The detailed description of the normative procedures for PCC enhancements can be found in TS [5] Local Operating Environment Information In addition to operator policy and user preferences, the UE may take into account the Local Operating Environment Information when deciding which access to use for an IP flow. The actual Local Operating Environment Information is implementation dependent and may comprise of such items as, radio environment information, quality of IP connection, application specific requirements, power considerations, etc. 5 IP Flow Mobility procedures and flows 5.1 General This section describes the IP flow mobility procedures for different scenarios. The call flows are described in a common way for I-WLAN and EPS and the procedures which are applicable to EPS only are marked as optional and identified as not applicable to an I-WLAN mobility deployment. Furthermore the call flows do not differentiate between trusted or untrusted accesses as the IP flow mobility procedures are common as soon as the UE configures a Care-of Address. 5.2 PDN connection establishment over first access General This clause specifies the additional UE procedures when establishing a PDN connection through a or through a WLAN access when the UE supports IP flow mobility. In these flows it is assumed that the UE has not established the PDN connection through any access yet. NOTE: In the rest of the document the PDN connection establishment procedure is meant to be PDP context activation procedure in case of I-WLAN mobility architecture PDN connection establishment over access The UE performs the initial PDN connection establishment to a access as shown in Figure This procedure applies independently whether the UE attaches to EPS or GPRS.

10 10 TS V ( ) Roaming Scenario UE GERAN/ UTRAN/ EUTRAN HA/ PDN GW Proxy vpcrf HSS/ hpcrf 1. PDN connection establishment as defined in TS or TS HA discovery, DSMIPv6 bootstrapping and Home Link Detection 3. Binding Update 4. Binding Acknowledgement Figure PDN connection procedure over access 1. The initial PDN establishment procedure is performed by the UE according to TS [10] or TS [11], depending if the PDN connection establishment is to EPS or GPRS. During this step an IPv4 address and/or an IPv6 address/prefix is assigned to the UE. 2. The UE performs HA discovery, DSMIPv6 bootstrapping and the home link detection procedure as described in TS [3] or TS [4]. 3. If the UE detects it is not on the home link, the UE sends a DSMIPv6 Binding Update (HoA, CoA, Lifetime, BID) message to the HA as specified in RFC 5555 [2] and RFC 5648 [7]. The inclusion of the BID option at this stage is an indication that the UE supports IP Flow Mobility extensions. The UE may also include some FID options as described in draft-ietf-mext-flow-binding [8]. Editor s Note: A procedure for the UE to check the IP Flow Mobility capability of the PDN GW is needed. This can be done either via PCO or creating a home binding sending a BU after the Home Link Detection procedure via IKEv2 is done or using the IKEv2 signaling. The actual procedure(s) is FFS. NOTE 1: The receipt of policies on IP flow mobility from the ANDSF of a given PLMN can be considered by the UE as an implicit indication that the Home Agents of that PLMN support IP flow mobility. If the UE detects that the Home Agent does not support IP flow mobility, the UE shall disable IP flow mobility until the UE disconnects from that PDN connection. NOTE 2: This step cannot happen in case IP flow mobility is used in EPS as is always the home link in EPS. 4. The HA validates the BU, installs the IP flow mobility routing rules, establishes the DSMIPv6 bindings and sends a BA to the UE per RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8] PDN connection establishment over WLAN The UE performs the initial PDN connection establishment over a WLAN access as shown in Figure

11 11 TS V ( ) UE Trusted non- IP Access/PDG/ epdg HA/ PDN GW Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. WLAN link establishment and IP address assignment 2. GW control session and QoS rules provision procedure 4. Binding Update 3. HA discovery, DSMIPv6 bootstrapping and Home Link Detection 6. Binding Acknowledgement 5. IP-CAN session establishment procedure Figure PDN connection procedure over non- access 1. The UE connects to the WLAN and configures an IPv4 address and/or an IPv6 address/prefix. Depending on the specific scenario considered the UE attaches either to a trusted WLAN, an epdg via an untrusted WLAN or to a PDG via a I-WLAN access as specified in TS [3] or TS [4]. If the UE connects to PDG or epdg, an IPv4 address and/or an IPv6 address/prefix is assigned to the UE. 2. If the UE connects to a Trusted non- access and dynamic PCC is deployed, a GW control session may be established as specified in TS [5]. 3. The UE performs HA discovery, DSMIPv6 bootstrapping and the home link detection procedure as described in TS [3] or TS [4]. 4. If the UE detects it is not on the home link, the UE sends a DSMIPv6 Binding Update (HoA, CoA, Lifetime, BID) message to the HA as specified in RFC 5555 [2] and RFC 5648 [7]. The inclusion of the BID option at this stage is an indication that the UE supports IP Flow Mobility extensions. The BID option contains the Binding ID of the WLAN access. The UE may also include some FID options as described in draft-ietf-mext-flowbinding [8]. 5. If the HA function is located in the PDN GW and dynamic PCC is deployed, the PDN GW performs an IP-CAN session establishment procedure with the PCRF as specified in TS [5]. 6) The HA validates the BU, installs the IP flow mobility routing rules, establishes the DSMIPv6 bindings and sends a BA to the UE per RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8]. In this step the UE detects if the HA supports IP flow mobility. If the HA does not support IP flow mobility, it does not acknowledge the BID option and the FID option as described in RFC 5648 [7] and draft-ietf-mext-flowbinding [8]. If the UE detects that the Home Agent does not support IP flow mobility, the UE shall disable IP flow mobility until the UE disconnects from that PDN connection 5.3 Addition of an access to a PDN connection General This clause specifies the additional procedures for adding an access to an existing PDN connection over a access or a WLAN access when the UE supports IP flow mobility. In these flows it is assumed that the UE has performed a PDN Connection establishment procedure through one access as specified in clause 5.2. Subsequently the UE attaches to a second access and starts using both accesses for the same PDN connection. As a result the UE is simultaneously

12 12 TS V ( ) connected via both accesses and a set of traffic flows are routed through one access while the remaining traffic flows are routed through the other access Addition of WLAN access After successfully attachment to access, the UE has established a PDN connection over access as specified in clause Subsequently the UE performs the WLAN attachment, and requests to establish a PDN connection using the same APN, and attempts to use both accesses for the same PDN connection simultaneously. The WLAN access may be considered as the UE's foreign link from DSMIPv6 perspective. Non-roaming, home routed roaming and Local Breakout cases are supported by this procedure. The proxy and vpcrf are only used in the case of home routed roaming and Local Breakout. In non-roaming scenarios, the proxy and vpcrf are not involved. The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed in EPC. These steps are never present when the solution is applied to I-WLAN mobility architecture according to TS [4]. UE Trusted - non- IP Access/PDG/ epdg GERAN/ UTRAN/ EUTRAN PDN GW/ HA Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. WLAN link establishment and IP address assignment 2. HA discovery, DSMIPv6 bootstrapping and Home Link Detection 3. Binding Update 4. IP-CAN session modification request 6. Binding Acknowledgement 5. IP-CAN session modification response 7. GW control session and QoS rules provision procedure 8. EPS resource release Figure : Addition of WLAN access to the PDN connection The signalling flow above shows the particular case where the UE is first connected to a access and then it requests addition of a WLAN access. 1. The UE discovers a WLAN and connects to it and configures an IPv4 address and/or an IPv6 address/prefix according to TS [3] or TS [4], depending whether the WLAN access is used in the context of EPC or I-WLAN mobility architecture. 2. The UE performs HA discovery, DSMIPv6 bootstrapping and DSMIPv6 home link detection procedure according to TS [3] unless already performed in the access. 3. The UE sends a DSMIPv6 Binding Update (HoA, CoA, Lifetime, BID, FID, flow description) message to the HA over the WLAN access. The UE may include the requested routing rules via the FID option with both the routing filters and the BID (which includes the routing address) as specified in IETF RFC 5555 [2], IETF RFC 5648 [7] and draft-ietf-mext-flow-binding [8]. The UE can include more than one routing rule by including multiple FID options in the Binding Update. The DSMIPv6 Binding Update also contains an indication which indicates that the home link ( access) is still connected and also the BID options which identify that one binding is associated with the home address ( access) and the other with the Care-of-Address from the

13 13 TS V ( ) WLAN access. The UE also indicates in the Binding Update which is the default binding where the HA should route packets not matching any FID as specified in [8]. 4. In case the HA function is located in the PDN GW and dynamic PCC is deployed, the PDN GW sends an IP- CAN session modification request to the PCRF. In this request, the PDN GW provides the updated routing rules to the PCRF. The PCRF stores the mapping between each SDF and its routing address. 5. If the HA function is located in the PDN GW, based on the successful establishment of resources at the BBERF, the PCRF sends an acknowledgement to the PDN GW, including updated PCC rules if appropriate. 6. The HA creates a DSMIPv6 binding, installs the IP flow routing rules and sends a Binding Acknowledgment (Lifetime, HoA, CoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flowbinding [8], to indicate which routing rules requested by the UE are accepted. The PDN GW may send message 6 before receiving the reply from PCRF in message Based on the IP-CAN session modification request, the PCRF ensures that the relevant QoS rules for the SDFs are installed in the target BBERF. This is done by a GW control session and QoS rules provision procedure as specified in TS [5]. 8. In case the HA function is located in the PDN GW, appropriate resource release procedures are executed for the resources associated with the flows that were moved away from the source access. This procedure may be triggered by the PCRF via a GW control session and QoS rules provision procedure if PMIPv6 is used on S5 and it may be triggered by the DN GW in case GTP is used on S Addition of access After successfully attachment to WLAN access, the UE has established a PDN connection over WLAN as specified in clause As the UE detected the WLAN access is not the home link from DSMIPv6 perspective, DSMIPv6 signalling was triggered over the WLAN access. Subsequently, as described in this clause, the UE performs the initial attachment procedure or PDN Connection establishment procedure over a access and establishes a PDN connection using the same APN, as described in TS [11], TS [10] or TS [3]. As the UE has indicated IP flow mobility during the initial attachment over WLAN, the access attachment completion shall not trigger the DSMIPv6 binding deregistration. UE Trusted - non- IP Access/PDG/ epdg GERAN/ UTRAN/ EUTRAN PDN GW/ HA Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. PDN connection establishment as defined in TS or TS Binding Update 3. IP-CAN session modification request 4. IP-CAN session modification response 5. Binding Acknowledgement 6. GW control session and QoS rules provision procedure 7. EPS bearer setup or modification Figure : Addition of access to the PDN connection

14 14 TS V ( ) The signalling flow above shows the particular case where the UE is first connected to a WLAN access and then it requests addition of a access. 1. The UE discovers a access and performs the Attach or PDN Connection establishment procedure according to TS [10] or TS [11]. Specifically, the UE sets the Request Type to Handover to facilitate the MME selects the same PDN GW/HA as the UE connects in WLAN Access. Since the UE has indicated IP flow mobility support during the initial attachment over WLAN, the HA shall not deregister the DSMIPv6 binding by sending a Binding Revocation Indication towards the WLAN access. 2. The UE sends a DSMIPv6 Binding Update (HoA, CoA, Lifetime, BID, FID, flow description) message to the HA over the access. The UE may include the requested routing rules via the FID option with both the routing filters and the BID (which includes the routing address) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8]. If the access is the home link, the UE sets 'the 'H' flag in the respective BID option, as specified in [8]. The UE can include more than one routing rule by including multiple FID options in the Binding Update. The UE also indicates in the Binding Update which is the default binding where the HA should route packets not matching any FID as specified in draft-ietf-mext-flow-binding [8]. 3. In case the HA function is located in the PDN GW and dynamic PCC is deployed, the PDN GW sends an IP- CAN session modification request to the PCRF. In this request, the PDN GW provides the updated routing rules to the PCRF. The PCRF stores the mapping between each SDF and its routing address. 4. If the HA function is located in the PDN GW, based on the successful establishment of resources at the BBERF, the PCRF sends an acknowledgement to the PDN GW, including updated PCC rules if appropriate. 5. The HA sends a Binding Acknowledgment (Lifetime, HoA, CoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8], to indicate which routing rules requested by the UE are accepted. The PDN GW/HA may send message 6 before receiving the reply from PCRF in message Based on the IP-CAN session modification request (if step 3 was performed), the PCRF ensures that the relevant QoS rules for the SDFs are installed in the target BBERF. This is done by a GW control session and QoS rules provision procedure as specified in TS [5]. 7. In case the HA function is located in the PDN GW, appropriate bearer setup or modification procedures are executed for the resources associated with the flows that were moved onto the access. This procedure may be triggered by the PCRF via a GW control session and QoS rules provision procedure if PMIPv6 is used on S5 and it may be triggered by the PDN GW in case GTP is used on S IP flow mobility within a PDN connection General This clause specifies the IP flow mobility procedures within a PDN connection. In these procedures the UE is assumed to simultaneously connect via a access and a WLAN access. The UE is using both the accesses for the same PDN connection. Subsequently, the UE adds/modifies/deletes/moves between accesses IP flows using DSMIPv6 messages. Non-roaming, home routed roaming and Local Breakout cases are supported by this procedure. The proxy and vpcrf shown in Figure are only used in the case of home routed roaming and Local Breakout. In non-roaming scenarios, the proxy and vpcrf are not involved. The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed in EPC. These steps are not present when the solution is applied to I-WLAN mobility architecture according to TS [4]. There are two scenarios, depending on UE initiates the QoS establishment in the target access or the network performs the QoS establishment when the IP flow is moved.

15 15 TS V ( ) IP flow mobility within a PDN connection with network-initiated dynamic PCC In this scenario the UE moves one or more IP flow(s) from one access to the other access and network-intiated dynamic PCC is used is used to set up or remove appropriate resources. UE Trusted - non- IP Access/PDG/ epdg GERAN/ UTRAN/ EUTRAN HA / PDN GW Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. UE is connected simultaneously to and non accesses and multiple bindings and multiple IP flows are registered at the HA 2. Binding Update 3. IP-CAN session modification request 5. Binding Acknowledgement 4. IP-CAN session modification response 6. GW control session and QoS rules provision procedure 7. EPS resource release Figure : IP Flow Mobility and network initiated dynamic PCC 1. The UE is simultaneously connected to a access and a WLAN access based on the procedures specified in clauses 5.2 and 5.3. Based on current routing rules some traffic is routed through the access and some other traffic through the WLAN access. 2. The UE sends a Binding Update (HoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietfmext-flow-binding [8] to the HA to install a new routing rule or to modify the routing address of an existing routing rule to route the respective traffic (identified by the included FID) through one particular access (identified by the included BID) or to remove an existing routing rule. In case of new routing rule with a new FID option, the UE includes the routing filter description. NOTE: The UE can send the Binding Update either from the or from the WLAN access irrespective of which access the IP flow is moved to. 3. In case the HA function is implemented in EPC, the PDN GW sends an IP-CAN session modification request to the PCRF. In this request the PDN GW provides the updated routing rules to the PCRF. The PCRF stores the updated mapping between routing addresses and SDFs. 4. If the HA function is implemented in EPC, based on the successful establishment of resources in the WLAN access, the PCRF sends an acknowledgement to the PDN GW, including updated PCC rules if appropriate. 5. The HA sends a Binding Acknowledgment (Lifetime, HoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8], to indicate which routing rules requested by the UE are accepted. The PDN GW/HA may send message 5 before receiving the reply from PCRF in message If the HA function is implemented in EPC, based on the IP-CAN session modification request, the PCRF ensures that the relevant QoS rules are installed in the target access or the relevant QoS rules are uninstalled from the source access. For non- access, this is done by a GW control session and QoS rules provision procedure as specified in TS [5].

16 16 TS V ( ) 7. If the HA function is implemented in EPC, appropriate EPS resource release procedures are executed for those resources that were moved away from the source access or appropriate EPS resource allocation procedures are executed fro those resources that were moved in to the access, as specified in TS This procedure may be triggered by the PCRF via a GW control session and QoS rules provision procedure if PMIPv6 is used on S5 and it may be triggered by the PDN GW in case GTP is used on S5. If the HA function is implemented in I-WLAN mobility, the UE may initiate GPRS resource release procedures for those resources that were moved away from the source access, as specified in TS [11] IP flow mobility within a PDN connection with UE-initiated resource request In this scenario the UE requests for resources in the target access with UE-initiated procedures and when the resources are provided, the UE moves one or more IP flow(s) to the target access. UE Trusted - non- IP Access/PDG/ epdg GERAN/ UTRAN/ EUTRAN HA / PDN GW Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. UE is connected simultaneously to and non accesses and multiple bindings and multiple IP flows are registered at the HA 2. UE requested bearer resource modification as specified in TS , section or in TS , section Binding Update 6. Binding Acknowledgement 4. IP-CAN session modification request 5. IP-CAN session modification request 7. GW control session and QoS rules provision procedure Figure : IP Flow Mobility and UE initiated resource request 1. The UE is simultaneously connected to a access and a WLAN access based on the procedures specified in clauses 5.2 and 5.3. Based on current routing rules some traffic is routed through the access and some other traffic through the WLAN access. 2. Before moving an IP flow currently routed over WLAN to the access, the UE requests appropriate resources in the access. This is done as specified in clause of TS [10] or in clause or A of TS [11]. In this procedure the UE includes the packet filters related to the requested resources. In this step if the HA function is implemented in EPC, the PDN GW may interact with the PCRF to trigger the appropriate PCC decision. The PCRF can authorize the resource establishment but since there is no change in the routing rules provided by the PDN GW. NOTE 1: After this step and until step 5 is performed, resources are allocated in two accesses for the same SDF. 3. The UE sends a Binding Update (HoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietfmext-flow-binding [8] to the HA to install a new routing rule or to modify the routing address of an existing routing rule to route the respective traffic (identified by the included FID) through one particular access (identified by the included BID) or to remove an existing routing rule. In case of new routing rule with a new FID option, the UE includes the routing filter description. NOTE 2: The UE can send the Binding Update either from the or from the WLAN access irrespective of which access the IP flow is moved to.

17 17 TS V ( ) NOTE 3: The routing filters included in the BU can be different from the packet filters included in step 2 by the UE. QoS will be provided only based on the packet filters installed in step 2 but the UE can include different, e.g. more generic, routing filters in this operation. 4. In case the HA function is implemented in EPC, the PDN GW sends an IP-CAN session modification request to the PCRF. In this request the PDN GW provides the updated routing rules to the PCRF. The PCRF stores the updated mapping between routing addresses and SDFs. 5. If the If the HA function is implemented in EPC, based on the successful establishment of resources in the WLAN access, the PCRF sends an acknowledgement to the PDN GW, including updated PCC rules if appropriate. 6. The HA sends a Binding Acknowledgment (Lifetime, HoA, BID, FID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8], to indicate which routing rules requested by the UE are accepted. The PDN GW may send message 6 before receiving the reply from PCRF in message If the HA function is implemented in EPC, based on the IP-CAN session modification request, the PCRF ensures that the resources associated with the routing filters moved to the access are released. This is done by a GW control session and QoS rules provision procedure as specified in TS [5]. 5.5 Removal of an access from a PDN connection In this scenario, the UE is attached to a access and a WLAN access and is using both the accesses for the same PDN connection. Subsequently, the UE moves all IP flows associated with one access to another access and disconnects from the one access (e.g. due to loss of coverage or by an explicit detach). The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed in EPC. These steps are never present when the solution is applied to I-WLAN mobility architecture according to TS [4]. UE Trusted - non- IP Access/PDG/ epdg GERAN/ UTRAN/ EUTRAN PDN GW/ HA Roaming Scenario Proxy vpcrf HSS/ hpcrf 1. UE is connected simultaneously to and non accesses and multiple bindings and multiple IP flows are registered at the HA 2. Binding Update 4. Binding Acknowledgement 3. IP-CAN session modification procedure 5. GW control session and QoS rules provision procedure 6. resource release Figure 5.5-1: Removal of one access from the PDN connection 1. The UE is simultaneously connected to a access and a WLAN access based on the procedures specified in clauses 5.2 and 5.3. Based on current routing rules some IP flows are routed through the access and some other IP flows through the WLAN access.

18 18 TS V ( ) 2. The UE decides to move all IP flows to one access and to disconnect from the other access (e.g. due to loss of coverage, based on internal trigger, based on updated policies from ANDSF). a. If UE disconnects one access (either a home link or a foreign link) and maintains the other access which is the foreign link, the UE sends a Binding Update (Lifetime, HoA, BID) to the HA with lifetime set to 0 to remove the BID of the access it disconnects from. Or, alternatively, the UE sends a Binding Update (HoA, BID) over the maintained foreign link to the HA with lifetime set to non-zero, the BID of the maintained foreign link, and "O" flag set. b. If the UE disconnects the WLAN access which is a foreign link and maintains only the access which is the home link, the UE sends a Binding Update with lifetime 0 without any BID. This de-registration Binding Update can be sent from any available access. 3. In case the HA function is located in the PDN GW, the PDN GW initiates the IP-CAN session modification procedure with the PCRF. In this procedure, the PDN GW removes the routing address related to the removed BID associated with the IP-CAN session. 4. The HA sends a Binding Acknowledgment (Lifetime, HoA, BID) as specified in RFC 5555 [2], RFC 5648 [7] and draft-ietf-mext-flow-binding [8]. NOTE 1: As specified in draft-ietf-mext-flow-binding [8] the routing rules which point to a routing address which is not registered become inactive and don't influence the routing of the packets, i.e. there is no need for the UE to change the routing rules as all packets will be anyway routed to the only existing binding. 5. If the HA function is located in the PDN GW, as part of the IP-CAN session modification procedure initiated in step 3, the PCRF ensures that the relevant QoS rules for the SDFs are installed in the target BBERF. This is done by a GW control session and QoS rules provision procedure as specified in TS [5]. 6. If in step 2 the UE has removed the BID associated with the access and maintained the BID for the WLAN access, the PDN GW shall initiate the PDN GW Initiated PDN Disconnection procedure in access as defined in TS [3], clause or the PDN GW Initiated Bearer Deactivation procedure as defined in TS [10], clause The PDN GW shall set the release cause to 'RAT changed from to Non- ' to avoid the MME remove the PDN GW ID from the HSS. In case of I-WLAN mobility architecture and the UE has removed the BID associated with the access, the UE may initiate PDP Context Deactivation as described in TS [11]. If the BID associated with the WLAN access is removed, according to TS [3] the security associations between the UE and the HA should not be immediately deleted. As the security associations were created dynamically using IKEv2 they will be automatically deleted when they expire. Similarly, for I-WLAN mobility architecture, the H2 session between the HA and the Server should not be immediately deleted. The H2 session will be deleted by the HA immediately after security associations are deleted. In case of I-WLAN mobility architecture, the UE may initiate release of the IKEv2 security association with the PDG according to TS NOTE 2: In case a detach from access needs to be triggered, e.g. based on O&M, a PDN GW initiated PDN disconnection procedure is used instead of a MME/SGSN-initiated detach/pdn disconnection procedure. 5.6 Addition of one access for multiple PDN connections to the same APN When a UE having multiple PDN connections to the same APN via one access attaches to a second access, the UE needs to decide which of the multiple PDN connections the UE has would use both accesses simultaneously. When the UE having multiple PDN connections to the same APN via a access attaches to a WLAN, the UE shall perform DSMIPv6 procedures only for the PDN connections for which it will use IP flow mobility. When the UE having multiple PDN connections to the same APN via the WLAN attaches to the access, the UE should only establish the PDN connections for which it will use IP flow mobility. However, due to the restriction that the UE cannot indicate which PDN connection is to establish, the UE shall repeat UE PDN Connectivity Request until the desired PDN connections have been established and shall perform DSMIPv6 procedures for the desired PDN connections.

19 19 TS V ( ) 5.7 Detach and PDN disconnection procedures When the UE is attached to the same PDN through two accesses and a detach or PDN disconnection procedure is required, the following considerations apply: - In case of UE initiated PDN disconnection the UE-initiated PDN disconnection procedure described in clause of TS [3] shall be performed (in case of untrusted access the procedure described in clause of TS [3] shall be performed). When this procedure is completed, UE-initiated Detach procedure described in clause of TS [10] shall be performed. - In case of HSS initiated detach, the HSS-initiated Detach procedure described in of TS [3] shall be performed (in case of untrusted access the procedure described in clause of TS [3] shall be performed). When this procedure is completed, the HSS-initiated Detach procedure described in clause of TS [10] shall be performed. - In case of PDN-GW initiated PDN disconnection procedure, the procedure in clause of TS [3] shall be performed (in case of untrusted access the procedure described in clause of TS [3] shall be performed). When this procedure is completed, the PDN GW Initiated Bearer Deactivation procedure as defined in TS [10], clause , shall be performed. When the UE is attached to I-WLAN architecture through and WLAN accesses and a detach or PDN disconnection procedure is required, similar considerations as above apply with reference to the procedures described in TS [4] and TS [11].

20 20 TS V ( ) Annex A (informative): Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New SP-48 SP MCC Update to version for presentation to TSG SA for approval SP MCC Update to version after approval at TSG SA (Release 10)