Distributed mobility management for Future Internetfor ...sites.ieee.org/northjersey/files/2011/09/20130626_COMSOC_Chan.pdf · Distributed mobility management for Future Internetfor

Distributed mobility management for Future Internetfor Future Internet

H. Anthony ChanHuawei [email protected]

What I have is only borrowed from God so that I may serve others. H Anthony Chan

distributed and dynamic mobility management Wireless broadband networkPage 1 June 25, 2013

Internet

♦ Core network: converge (cellular and Internet – no more IPv4 blocks available)

♦ Access networks: diverse

♦ Devices: multiple interfaces, multiple functions, mobile

♦ Traffic from Wireless device grows 3 times faster than (exceeding soon) that of wireline devices

♦ Internet: lack native support for mobility, multi-homing, etc


Wireless broadband networkPage 2 June 25, 2013

distributed and dynamic mobility management

etc.

Core network: Convergence

Multi-service networkSingle-service networks

e e e e e e e e

Service NetworkS

ContentContent

serv

ice

serv

ice

serv

ice

serv

ice

serv

ice

serv

ice

serv

ice

serv

ice

Vetw

ork

SDN

N

S SS

ContentContent

NAX etw

ork

ueto

oth)

CAT

V

Dat

a/IP

Ne

PSTN

/IS

PLM

N

Connectivity/Connectivity/Backbone NetworkBackbone NetworkMGWMGW MGWMGW

WLA

WiM

A

Sens

or n

e

WPA

N (B

lu

Access NetworksMGWMGWMGWMGW

W




Access, Transport & Switching Networks

Internet


3GPP

♦ Access networks: diverse 802.11

802.16 3GPP;3GPP2

Ethernet

OtherNets?Ethernet







etc.

Wireless access network: Cellular

1 Gbps(4G) LTE-Advanced >1Gbps; IEEE802.16m OFDMA

LTE 326/86 Mbps

100 MbpsHSPA+ 84/23Mbps CDMA

Extend through handoff

10 Mbps

1 Mbps(3G) UMTS:WCDMA; CDMA2000 1x 2Mbps

(3.5G) EV-DO Rev A 3.1/1.8Mbps

(3.5G) HSPA 14.4/5.76Mbps, EV-DO Rev B

handoff1 Mbps

100 kbps

EDGE 384 kbps

(2G) GSM 9.6 kbps(2.5G) GPRS 14.4 kbps

10 kbpsTDMA




1 m 10 m 100 m 1 km 10 km 100 km

Wireless access network: 802 wireless family

802.20 MAN>1 Mbps per

useruser

802.11a/b/g/n WLAN <11, 54, 300 Mbps

802.16 10-66GHz

802.16 2-11GHz WiMax

802.15 Bluetooth

< 70 Mbps

1 m 10 m 100 m 1 km 10 km 100 km

700kbps

MAN 3–8kmLANPAN




WAN 30–50km

Internet


3GPP

♦ Access networks: diverse 802.11

802.16 3GPP;3GPP2

Ethernet

OtherNets?Ethernet







etc.

Internet: ID-Locator split problem

ID-Locator Split networkProcess

IP networkProcess

Socket

Uses ID Transport

ID (of host)

Socket = IP addr + Port #

Transport (Port #)

Network (IP address of interface)

♦ IP address (of interface) changes h ti h T t

♦ ID (of host): Used for session, rarely h

Uses Locator Network (IP address)

when routing changes. Transport session does not survive under IP changes.

changes. ♦ Locator (IP address): Used for

network routing. ♦ Mapping system (control plane): maps♦ Mapping system (control plane): maps

ID with a set of locators (IP addr)




What is the ID/Locator Split Protocol?

Client based / Client-network changes♦ Architectural change to the TCP/IP stack

A new layer between IP and transport

Network based: No change to client stack♦ Locator = globally routable IP addr in

backbone/Internet only♦ Session between Host IDs not affected

by locator changesMajor protocols/proposals:♦ HIP (Ericsson/HIIT)

♦ ID = edge network IP addr; session not affected by locator changes in Internet.

Major protocols:♦ LISP (Cisco);♦ HIP (Ericsson/HIIT)

♦ I3 (UC Berkeley)♦ Clean slate design (Stanford)♦ Internet 3.0 (WashU)

♦ LISP (Cisco); ♦ APT (UCLA)

Backbone/Transit Network

U L( )

ProcessProcess

Transport

ProcessProcess

T t

Before After Uses Locator

Edge network

Ingress router (IR)

Edge network

Egress router (ER)

TransportTransport Uses ID Uses ID

IP layerLocator (IP layer)

Host Identity



distributed and dynamic mobility managementyLink layerLink layer

Source node (S)

Locator (IP layer) Destination node (D)

ID-Locator Split families

♦ Protocol stack (e.g. HIP)Application ApplicationTransport TransportTransport Transport

ID IDIP IP IP IPL2 L2 L2 L2

♦ Core edge separation: tunneling (e g LISP) or

L1 L1 L1 L1Source Router Router Destination

♦ Core-edge separation: tunneling (e.g. LISP) or translation

Application ApplicationTransport TransportTransport TransportIP(PIS,PID) IP(PIS,PID) IP(PAIR,PAER) IP(PAIR,PAER) IP(PIS,PID) IP(PIS,PID)

L2 L2 L2 L2 L2 L2L1 L1 L1 L1 L1 L1




Source Ingress router (IR) Egress router (ER) DestinationEDEG ROUTING CORE ROUTING EDGE ROUTING

Mobile IP

CDNserver

CDNserver

CDNserver

Home network Visited network

MN CNMN

mobile node

Process

correspondent node

SocketTransport

Session Identifier IP address before move




Session Identifier IP address before moveLocator (CoA) Current IP address

Proxy Mobile IP

Application ApplicationTransport TransportIP(HoA) IP(HoA) IP(HoA) IP(HoA) IP(HoA) IP(HoA)

IP(CoA) IP(CoA)MN MAG LMA CNEDEG ROUTING CORE ROUTING INTERNET

MAG: Mobile access gateway




LMA: Local mobility anchor

Host-based versus Network-based mobility management

Host-based mobility management (HoA: P1::mn, CoA: P3::mn)HoA HoA HoA HoA

CoA CoACoA CoACN MR MN (P1::mn)

Mobility client

Network-based mobility management (HoA: P1::mn, CoA: P3::ar)HoA HoA HoA HoA HoA HoA

CoA CoACoA CoACN MR AR (P3::ar) MN

Mobility client




Distributed mobility anchors

♦ Distributed versus centralized mobility anchors♦ Splitting control and data planes: Architecture♦ Splitting control and data planes: Architecture♦ Unified formulation of Internet mobility♦ DMM Route optimization mechanism example♦ DMM Route optimization mechanism example









Centralized mobility anchors

♦ Current mobile networks are hierarchical, and existing mobility solutions are deployed with g y p ycentralized mobility anchoring

♦ E.g. HA in MIPv6/DSMIPv6, LMA in PMIPv6, GGSN in 3GPP

GPRS/UMTS SAE PMIPMIP

GGSN

SGSN SGSN

P-GW

S GW S GW

LMA

MAG MAG

HA

FA FA

• Network: hierarchical versus flattened

SGSN SGSN S-GW S-GW MAG MAGFA FA




• Mobility management: centralized versus distributed

Proxy mobile IP (PMIP) with triangle routing problem

♦ Packets between MN and CN need to tunnel between MAG and LMA, even when MN is far from home network but is close to CN

Home networkwith LMA

Visited networkwith MAG

CDNserver

CDNserver

CDNserver

LMA: Local mobility anchor = Home agent (HA) + PMIP function= Home agent (HA) + PMIP function

MN: mobile nodeCN: correspondent node

MN CN




Problem statement PS1: Non-optimal routes

♦ (1) Routing via a centralized anchor often results in a longer route.g

MA MA MA MA

MN CN




MN CN

PS1: Non-optimal routes (continued)

♦ The problem is manifested, for example, when accessing a local server or servers of a Content gDelivery Network (CDN).

P-GW

SGW SGW SGW CDNserver

CDNserver

CDNserver




MN

PS2: Divergence from other evolutionary trends in network architectures

♦ Centralized mobility management can become non-optimal with a flat network architecture.p

♦ In contrast, distributed mobility management can support both hierarchical network and more flattened network.

GMSC GGSN P-GWGSM GPRS/UMTS:WCDMA EPC:LTE next?

MSC

RNC

SGSN

RNC

S-GW P-GW/S-GW

?RNC

BS

RNC

BS BS BS




MN MN MN MN

PS3: Low scalability of centralized tunnel management and mobility context maintenance ♦ Setting up tunnels through a central anchor and

maintaining mobility context for each MN therein g yrequires more resources in a centralized design, thus reducing scalability. Distributing the tunnel

i t f ti d th bilit t tmaintenance function and the mobility context maintenance function among different network entities can increase scalabilityentities can increase scalability.

MA

MN5 MN0




MN2MN5

MN8MN0

MN12 MN14

PS4: Single point of failure and attack

♦ Centralized anchoring may be more vulnerable to single points of failures and attacks than a g pdistributed system. The impact of a successful attack on a system with centralized mobility

t b f t llmanagement can be far greater as well.

MA MA MA MA




MN CN

PS5: Wasting resources to provide mobility support to nodes that do not need such support♦ IP mobility support is not always required, and not

every parameter of mobility context is always used. For example some applications do not need a stableFor example, some applications do not need a stable IP address during a handover to maintain IP session continuity. Sometimes, the entire application session runs while the terminal does not change the point of attachment.

MN2

MN1

MN4

MN5

MN7

MN6

MN9

MN0

MN12

MN11

MN14

MN15




♦ MN3 MN8 MN13

PS6 (related): Mobility signaling overhead with peer-to-peer communication

♦ Wasting resources when mobility signaling (e.g., maintenance of the tunnel, keep alive, etc.) is not p )turned off for peer-to-peer communication.

Home networkwith LMA

Visited networkwith MAG




MN CN

PS6 (related): Mobility signaling overhead with peer-to-peer communication (continued)

♦ Peer-to-peer communications have particular traffic patterns that often do not benefit from mobility p ysupport from the network. Thus, the associated mobility support signaling (e.g., maintenance of the t l k li t ) t t ktunnel, keep alives, etc.) wastes network resources for no application gain. In such a case, it is better to enable mobility support selectivelyenable mobility support selectively.




PS7 (related): Complicated deployment with too many MIP variants and extensions

♦ Deployment is complicated with many variants and extensions of MIP. When introducing new functions gwhich may add to the complicity, existing solutions are more vulnerable to break.

♦ Variants: MIP, PMIP, HMIP, FMIP, DSMIP, …, etc.









Distributed mobility anchors-Architecture

♦ LMA functions: mobility routing + location management + HoA allocation. g

LM LM LM LM

MR MR MR MR

LM LM LM LM

MN CNMN MN CNMN

LM: Location management (control plane)




LM: Location management (control plane)MR: Mobility routing (data plane)

Distributed mobility anchors-Architecture

MR: Mobility routing function (data plane)

Location Management function (control plane)

N t k b d MR i LM i t d b♦ Network-based: MR in every network, at GW which may move down

♦ LM is supported by distributed database

which may move down to AR in flat net

♦ Host-based: MR at LM3LM2LM1♦ Host based: MR at host

LM

LM3LM2LM1

MR MR MR1 MR2 MR3




MN MN31MN MN32 MN11






Unified formulation of Internet mobility standards

3 Basic Internet Functions3 Basic Mobility Management Functions

♦ 1 The Internet allocates 1 S i id tifi♦ 1. The Internet allocates IPv6 network prefixes or IPv4 addresses to a host.

♦ 2 The Internet manages

♦ 1. Session identifier allocation

♦ 2 Location♦ 2. The Internet manages information needed for routing by maintaining a database (DNS) and

♦ 2. Location management (LM)

♦ 3 Mobility routing (MR)( )exchanging routing information between routers.

♦ 3. Mobility routing (MR)

♦ 3. Router forwards packets using appropriate information in the routing table




table

Session continuity

♦ Session may continue when EID (inner IP address) does not change.g

Process

Socket = IP addr + Port #Socket = IP addr + Port #

Uses EID Transport (Port #) Host stack

N t k (i IP dd )Network (inner IP address)

Uses RLOC Network (outer IP address) Map-and-Encap




Host-based versus Network-based mobility management

Host-based mobility management (HoA: P1::mn, CoA: P3::mn)HoA HoA HoA HoA

CoA CoACoA CoACN MR MN (P1::mn)

Mobility client

Network-based mobility management (HoA: P1::mn, CoA: P3::ar)HoA HoA HoA HoA HoA HoA

CoA CoACoA CoACN MR AR (P3::ar) MN

Mobility client




Mobility Management Framework

♦ Architecture: Configure the logical functions

Logical Functions:1. HoA allocation2. LM: Location management (control plane) g

♦ Protocol: Messages3. MR: Mobility routing (data plane)

♦ Construct one step at a time: MIPv6, PMIPv6, , ,HMIPv6, Distributing mobility anchors, d i bili DMMdynamic mobility, DMM




Existing protocol: MIPv6

Net1 Net2Net3(P11::mn11,P3::mn11)

Logical Functions:HoA allocation; LM: Location management (control plane); MR: Mobility routing (data plane); LU: location update

LM1AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

MR1

MN11+MCMN11 CN21Move13P11::mn11 (HoA11)

P11::mn11(HoA11)P31::mn11(IP31)

MN11+MCMN11 P2::cn21 (IP21)

Move13




Existing protocol: PMIPv6

Net1 Net2Net3(P12::mn12


LM1 (P12::mn12,P3::ar32)AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

MR1

AR32+MC

CN21

P32::ar32(proxy IP32)

Move13 MN12MN12

P2::cn21 (IP21)




Move13P12::mn12(HoA12)

MN12MN12P12::mn12(HoA12)

MIPv6/PMIPv6

Net1 Net2(P11::mn11,P3::mn11)(P12::mn12Net3


LM1 (P12::mn12,P3::ar32)AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

MR1

AR32+MC

MN11+MCMN11 CN21Move13

P32::ar32(proxy IP32)(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)






Hierarchical

Net1 Net2Net3(P11::mn11,P3::mr3)(P12::mn12


LM1 (P12::mn12,P3::mr3)AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR1 MR3

GW3+MR3+MC


P32::ar32(proxy IP32)AR32+MC

(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)






Deploying in all networks

Net1 Net2Net3(P11::mn11,P3::mr3)(P12::mn12 LM2


LM1 (P12::mn12,P3::mr3) LM2LM3AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR1 MR2MR3

GW3+MR3+MC



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)






Selective mobility managementwithout ongoing application requiring session continuity

LM2

Net1 Net2Net3

LM1 LM2LM3AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

GW3 MR3 MCP3::mr3 MR2

GW3+MR3+MCMR1 MR3



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P31::mn11(IP31)


Move13

(b)





MN12MN12

P321::mm12(current address: CoA)

Selective mobility managementwith ongoing application requiring session continuity

(P11::mn11,P3::mr3)(P12::mn12 LM2

Net1 Net2Net3


AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR2

GW3+MR3+MCMR1 MR3



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)





MN12MN12P12::mn12(home address: HoA12)

Selective mobility management

(P11::mn11,P3::mr3)(P12::mn12 LM2

Net1 Net2Net3


AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR2

GW3+MR3+MCMR1 MR3



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)





MN12MN12P12::mn12(home address: HoA12)P321::mm12(current address: CoA)

Mobility Management Framework:HoA of application (in network where appl started)

(P11::mn11,P3::mr3)(P12::mn12 LM2

Net1 Net2Net3


AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR1 MR2MR3

GW3+MR3+MC



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)





MN12MN12P12::mn12(HoA12)P321::mm12(IP32)

DMM




AllocateP2::/64

AllocateP3::/64

GW3 MR3 MC

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)MR1 MR2MR3

GW3+MR3+MC



(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)


Move13

(b)











DMM Example



LM1 (P12::mn12,P3::mr3) LM2LM3

GW3 MR3 MC

AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)

GW3+MR3+MCMR1 MR21st packet after 1st packetMR3

Cache:P12::mn12P3 GW3AR32+MC



P3::GW3

(a)

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)

MN11+MCMN11 P21::cn21 (IP21)

Move13

(b)






DMM Example



LM1 (P12::mn12,P3::mr3) LM2LM3

GW3 MR3 MC

AllocateP1::/64

AllocateP2::/64

AllocateP3::/64

(P12::mn12,P32::ar32)P3::mr3

(P11::mn11,P31::mn11)

GW3+MR3+MCMR1 1st packet after 1st packetMR3 Cache:(P12::mn12P3::mr3)

MR2

AR32+MC

MN11+MCMN11 Move13


P3::mr3)AR21

(a)

CN21

P11::mn11 (HoA11)

Move13 MN12MN12

P11::mn11(HoA11)P31::mn11(IP31)

MN11+MCMN11 Move13

CN22(b)




P21::cn21 (IP21)

CN21Move13P12::mn12(HoA12)


CN22

Thank youy

H. Anthony ChanHuawei [email protected]

What I have is only borrowed from God so that I may serve others.


distributed and dynamic mobility management Wireless broadband networkPage 48 June 25, 2013

Documents

Distributed mobility management for Future Internetfor ...sites.ieee.org/northjersey/files/2011/09/20130626_COMSOC_Chan.pdf · Distributed mobility management for Future Internetfor