Use case scenarios for Distributed Mobility Management

Hidetoshi Yokota, KDDI LabPierrick Seite, France Telecom-OrangeElena Demaria, Telecom ItaliaZhen Cao, China MobileDapeng Liu, China MobileH. Anthony Chan, Huawei TechnologiesCharlie Perkins, TellabsTelemaco Meria, Alcatel-Lucent Bell LabsHui Deng, China MobileWassim Haddad, Ericsson

IETF79 MEXT WG 1

Background and motivation Mobile data is literally growing exponentially

Smartphones generate much more traffic than plain old mobile phones

Mobile operators are starting to offload mobile traffic to WiFi networks and deploy local Content Delivery Network

Standardization for mobile data offload is underway in other SDOs 3GPP LIPA/SIPTO

This issue is not only for one SDO, but for the whole Internet

Renovate the conventional mobile network More distributed and scalable model

IETF79 MEXT WG 2

Where to distribute…?

IETF79 MEXT WG

APAP

HA/LMAHA/LMA

AR/FA/MAGAR/FA/MAG

3

MHMH

Core-level

AR-level

Access-level

MobileCore

Network

AccessNetwork

Host-level

Core-level distribution Keep existing

hierarchy Traffic and

mobility bindings are distributed over HA/LMAs

Handover, signaling and/or routing may be needed between HAs/LMAs

IETF79 MEXT WG 4

APAP

HA/LMAHA/LMA

AR/FA/MAGAR/FA/MAG

MHMH

Core-level

AR-level

HA/LMAHA/LMA HA/LMAHA/LMA

AR/FA/MAGAR/FA/MAG AR/FA/MAGAR/FA/MAG

APAP APAP

MHMH

InternetInternet

AR-level distribution Role of HA/LMA

is regressed Traffic and

mobility bindings are distributed over ARs

Signaling and routing needed between ARs

IETF79 MEXT WG 5

APAP

AR/FA/MAGAR/FA/MAG

MHMH

AR-level

HA/LMAHA/LMA

AR/FA/MAGAR/FA/MAG AR/FA/MAGAR/FA/MAG

APAP APAP

MHMH

InternetInternet

Access-level distribution Role of mobile

core is regressed Part of AR

functionality is combined with AP Access Node (AN)

=AP+AR Distribute traffic

and mobility bindings over ANs

Signaling and routing needed between ANs

IETF79 MEXT WG 6

FA/MAGFA/MAG

MHMH

Access-level

HA/LMAHA/LMA

MHMH

InternetInternet

ANAN ANAN ANAN

Access NWAccess NW

Mobile CoreMobile Core

Host-level distribution Peer-to-peer

communication between MHs

More independent of the mobile network

Signaling and routing needed between MHs

IETF79 MEXT WG 7

MHMHHost-level

MHMH

InternetInternet

How to distribute…?

Possible approaches for Distributed Mobility Management Partially distributed approach Fully distributed approach

IETF79 MEXT WG 8

Partially distributed approach (I)

Control and data plane separation Control plane: Centralized Data plane: Distributed

IETF79 MEXT WG

MAMA MAMAMAMA

MAMAMAMA

ControlControlFunctionFunction

9

MA: Mobility Anchor

RegistrationRegistration

Route SetupRoute Setup

MH1MH1MH2MH2

Partially distributed approach (II)

Dynamic mobility management Mobility is provided on demand

IETF79 MEXT WG 10

AR1AR1

MH1MH1

CH1CH1 CH2CH2

AR2AR2

MH1MH1

IP1 IP2IP1

MHMHMHMHMHnMHn

MHMHMHMHCHnCHn

MH1

mobility binding

MH1

mobility binding

Fully distributed approach Both control and data planes are

distributed

IETF79 MEXT WG 11

MAMA MAMAMAMA

MAMAMAMA

MA: Mobility Anchor (including control function)

MH1MH1MH2MH2

Dynamic mobility management also applies

Selection of the appropriate mobility anchor is an issue

Mobility anchor selection in fully distributed approach Ex.1: broadcast/multicast approach

No routing is needed Good for regional area, probably not for

global

IETF79 MEXT WG

MAMA MAMAMAMA

MAMAMAMA

12

MH1MH1MH2MH2

Mobility anchor selection in fully distributed approach (cont’d)

Ex.2: Search & delivery Efficient look-up mechanisms exist, but

still takes time to discover the corresponding MAscalability issue could remain

IETF79 MEXT WG

MAMA MAMA MAMAMAMA

MAMA

13

MH1MH1MH2MH2

Analysis and proposal

More flat architecture is preferred for effective distribution

Flexible and manageable routing is needed for selective traffic offloadAR/Access-level distribution

Scalability must be consideredPartially distributed approach is likely to be more practical so far

IETF79 MEXT WG 14