1

Flow Mobility Support

QUALCOMM Inc. George Cherian, Jun Wang, Masa Shirotagcherian/jwang/mshirota@qualcomm.com

Notice ©2009. All rights reserved.

The contributors grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner’s standards publication. The contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.

This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.

2

Why Do We Need Flow Mobility?

• Simultaneous connectivity through multiple heterogeneous accesses

– E.g., Dual radio access terminal connected to a 3GPP2 and a non 3GPP2 access (WLAN) simultaneously

• Different IP flows on different access systems simultaneously– Allows different QoS treatment (e.g., VoIP over HRPD and ftp over WLAN)– Allows loading balance based on access network loading

• Optimized path for TCP type protocols

• Dynamic IP flow mobility between accesses– Based on the availability of certain access, certain flows can be moved from one access to

another access without interrupting the service.

• Transparent to the deployed access systems– Deployed HRPD/1x systems are not impacted by these extensions

• IETF is developing DSMIPv6 extensions to handle parallel connectivity and flow movement

– draft-ietf-mext-flow-binding-00

3

Why simultaneous connectivity through multiple heterogeneous accesses?

• Multi-radio Access Terminals start to become more common– E.g. cdma2000 + WiFi in the home environment

• Allows usage of the “best” access technology based on the application type/QoS requirements connecting to the same core network

– E.g. when user is an area of both cdma2000 and WiFi coverage• The QoS sensitive real time applications could be routed via cdma2000 access

– to optimize the end user experience for these apps

• The best effort high data-rate internet applications could be routed via WiFi– to reduce the load on cellular system– for a better overall user experience

– IP flows can be dynamically switched between cdma2000 and non-cdma2000 accesses

• Depending on the availability of the Non cdma2000 access systems (e.g. WiFi)– some IP flows moved to WiFi when user enters home– WiFi routed IP flows moved to cdma2000 when user loses WiFi coverage

4

cdma2000WLAN

AT

AAA

Both IP flows are routed through cdma2000 access

Example Scenario(Step 0: AT in cdma2000 Access)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIP

PDSN

Mobile IP tunnel

5

cdma2000WLAN

AT

AAA

Example Scenario(Step 1: AT detects “WiFi”)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIP

PDSN

The UE moves to an area where also coverage from trusted non 3GPP2 access (e.g. WiFi) is available

Mobile IP tunnel

6

cdma2000WLAN

AT

AAA

Example Scenario(Step 2: IP Flow A is moved to WiFi)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIP

PDSN

IP Flow A is moved to go through WLAN to reduce the load in cdma2000 and to increase the end user bandwidth for browsing

Mobile IP tunnelMobile IP tunnel

7

PDSN cdma2000WLAN

AT

AAA

Example Scenario (Step 3: New IP Flow C is established via WiFi)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIPA new application is launched and a new IP flow C is created and routed via WLAN

IP flow C, e.g. Ftp

Mobile IP tunnelMobile IP tunnel

8

PDSN cdma2000WLAN

AT

AAA

Example Scenario (Step 4: AT moves out from WiFi coverage)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIPAT moves to an area where WiFi can not anymore be used to transport IP flow A and C.

IP flow C, e.g. Ftp

Mobile IP tunnelMobile IP tunnel

9

PDSN cdma2000WLAN

AT

AAA

Example Scenario (Step 5: All IP flows are moved to cdma2000)

HA

IP flow A, e.g. Http

IP flow B, e.g. VoIPIP flow C, e.g. Ftp

Mobile IP tunnel

10

Multiple registrations at DSMIPv6 level

• “DSMIPv6 MCoAs registration” refers to the capability of the AT to register multiple CoAs at the Home Agent– The different CoAs are obtained over different access networks – The different CoAs are then used simultaneously– See related IETF work in draft-ietf-monami6-multiplecoa-13,

draft-ietf-mext-flow-binding-02

• DSMIPv6 MCoAs registration is independent of:– application level signaling: works for both IMS applications and

non-IMS applications– access level mobility: works for any access providing IP

connectivity (section 3 of draft-ietf-monami6-multiplecoa-13)

Flow mobility Triggers• Static Policy based on pre-provision

– Provisioning of rules can be done on the AT.• RAT preference based on traffic-type.

– For example, BE traffic is preferred on WLAN, if available, QoS based traffic is preferred on HRPD etc.

• Over-The-Air provisioning of the policy– OTA based provisioning

– ANDSF based provisioning

• Dynamic policy based on access network loading– AT detects the relative strength of radio-level signal-strength and the

expected throughput• If the actual throughput at a certain radio signal is lesser than the expected

throughput at that signal strength by a certain threshold, then that is an indication to the AT that access network is loaded.

11

12

Conclusions

• Flow mobility provides simultaneous connectivity through multiple heterogeneous accesses

• Flow Mobility is built on DSMIPv6

• Recommendation:

– Add flow mobility support in X.P0011-E

• Minimal standards impact