Distributed mobility management

Transcription

1 Distributed mobility management for Future Internet H. Anthony Chan Huawei Technologies 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. Page 1 June 25, 2013 Page 2 June 25, 2013 Core network: Convergence Internet Single-service networks PL PSTN/IS SDN Data/IP Ne etwork CATV WiMA AX WLA N WPAN (Blu uetooth) Sensor ne etwork Access, & Switching Networks Content Multi-service network MGW S Service Network S S S Connectivity/ Backbone Network MGW MGW Access Networks Content MGW Core network: converge (cellular and Internet no more IPv4 blocks available) Ethernet Access networks: diverse Ethernet GPP; 3GPP2 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. Other Nets? Page 3 June 25, 2013 Page 4 June 25, 2013

2 Wireless access network: Cellular Wireless access network: 802 wireless family 1 Gbps 100 Mbps 10 Mbps 1 Mbps (4G) LTE-Advanced >1Gbps; IEEE802.16m LTE 326/86 Mbps HSPA+ 84/23Mbps (3.5G) HSPA 14.4/5.76Mbps, EV-DO Rev B (3.5G) EV-DO Rev A 3.1/1.8Mbps (3G) UMTS:WCDMA; CDMA2000 1x 2Mbps EDGE 384 kbps OFDMA CDMA Extend through handoff a/b/g/n WLAN <11, 54, 300 Mbps Bluetooth 700kbps MAN >1 Mbps per user GHz < 70 Mbps GHz WiMax 100 kbps 1 m 10 m 100 m 1 km 10 km 100 km 10 kbps (2.5G) GPRS 14.4 kbps (2G) GSM 9.6 kbps TDMA PAN LAN MAN 3 8km 1 m 10 m 100 m 1 km 10 km 100 km Page 5 June 25, 2013 WAN 30 50km Page 6 June 25, 2013 Internet Internet: ID-Locator split problem Core network: converge (cellular and Internet no more IPv4 blocks available) IP network Process ID-Locator Split network Process Ethernet Access networks: diverse Ethernet GPP; 3GPP2 Other Nets? Socket = IP addr + Port # (Port #) Network (IP address of interface) Uses ID Socket ID (of host) 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. IP address (of interface) changes when routing changes. session does not survive under IP changes. Uses Locator Network (IP address) ID (of host): Used for session, rarely changes. Locator (IP address): Used for network routing. Mapping system (control plane): maps ID with a set of locators (IP addr) Page 7 June 25, 2013 Page 8 June 25, 2013

3 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 Session between Host IDs not affected by locator changes Major protocols/proposals: HIP (Ericsson/HIIT) I3 (UC Berkeley) Clean slate design (Stanford) Internet 3.0 (WashU) Before After Process IP layer Link layer Process Host Identity Locator (IP layer) Link layer Network based: No change to client stack Locator = globally routable IP addr in backbone/internet only ID = edge network IP addr; session not affected by locator changes in Internet. Major protocols: LISP (Cisco); APT (UCLA) Backbone/ Transit Network Uses Locator Ingress Egress router (IR) router (ER) Edge network Uses ID Source node (S) Edge network Uses ID Destination node (D) Page 9 June 25, 2013 Protocol stack (e.g. HIP) Application ID-Locator Split families Application ID ID IP IP IP IP L2 L2 L2 L2 L1 L1 L1 L1 Source Router Router Destination Core-edge edge separation: tunneling (e.g. LISP) or translation Application Application IP(PI S,PI D ) IP(PI S,PI D ) IP(PA IR,PA ER ) IP(PA IR,PA ER ) IP(PI S,PI D ) IP(PI S,PI D ) L2 L2 L2 L2 L2 L2 L1 L1 L1 L1 L1 L1 Source Ingress router (IR) Egress router (ER) Destination EDEG ROUTING CORE ROUTING EDGE ROUTING Page 10 June 25, 2013 Mobile IP Proxy Mobile IP Home network Session Identifier Locator () CDN CDN Visited network mobile node CN CDN correspondent node Process Socket IP address before move Current IP address Page 11 June 25, 2013 Application Application IP(HoA) IP(HoA) IP(HoA) IP(HoA) IP(HoA) IP(HoA) IP() IP() MAG LMA CN EDEG ROUTING CORE ROUTING INTERNET MAG: Mobile access gateway LMA: Local mobility anchor Page 12 June 25, 2013

4 Host-based versus Network-based mobility management Host-based mobility management (HoA: P1::mn, : P3::mn) HoA HoA HoA HoA CN MR (P1::mn) Mobility client Distributed mobility anchors Distributed versus centralized mobility anchors Splitting control and data planes: Architecture Unified formulation of Internet mobility DMM Route optimization mechanism example Network-based mobility management (HoA: P1::mn, : P3::ar) HoA HoA HoA HoA HoA HoA CN MR AR (P3::ar) Mobility client Page 13 June 25, 2013 Page 14 June 25, 2013 Distributed mobility anchors Distributed versus centralized mobility anchors Splitting control and data planes: Architecture Unified formulation of Internet mobility DMM Route optimization mechanism example Centralized mobility anchors Current mobile networks are hierarchical, and existing mobility solutions are deployed with centralized mobility anchoring E.g. HA in MIPv6/DSMIPv6, LMA in PMIPv6, GGSN in 3GPP GPRS/UMTS SAE MIP PMIP GGSN P-GW HA LMA SGSN SGSN S-GW S-GW FA FA MAG MAG Network: hierarchical versus flattened Mobility management: centralized versus distributed Page 15 June 25, 2013 Page 16 June 25, 2013

5 Proxy mobile IP (PMIP) with triangle routing problem Packets between and CN need to tunnel between MAG and LMA, even when is far from home network but is close to CN Problem statement PS1: Non-optimal routes (1) Routing via a centralized anchor often results in a longer route. Home network with LMA CDN CDN Visited network with MAG CDN LMA: Local mobility anchor MA MA MA MA = Home agent (HA) + PMIP function : mobile node CN CN: correspondent node CN Page 17 June 25, 2013 Page 18 June 25, 2013 PS1: Non-optimal routes (continued) The problem is manifested, for example, when accessing a local or s of a Content Delivery Network (CDN). PS2: Divergence from other evolutionary trends in network architectures Centralized mobility management can become nonoptimal with a flat network architecture. In contrast, distributed mobility management can support both hierarchical network and more flattened network. GSM GPRS/UMTS:WCDMA EPC:LTE next? GMSC GGSN P-GW MSC SGSN S-GW P-GW/S-GW P-GW RNC RNC? SGW CDN SGW CDN SGW CDN Page 19 June 25, 2013 BS BS BS BS Page 20 June 25, 2013

6 PS3: Low scalability of centralized tunnel management and mobility context maintenance Setting up tunnels through a central anchor and maintaining mobility context for each therein requires more resources in a centralized design, thus reducing scalability. Distributing the tunnel maintenance function and the mobility context t maintenance function among different network entities can increase scalability. MA PS4: Single point of failure and attack Centralized anchoring may be more vulnerable to single points of failures and attacks than a distributed system. The impact of a successful attack on a system with centralized mobility management can be far greater as well. MA MA MA MA CN Page 21 June 25, 2013 Page 22 June 25, 2013 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 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. 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 turned off for peer-to-peer communication Home network with LMA Visited network with MAG CN Page 23 June 25, 2013 Page 24 June 25, 2013

7 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 support from the network. Thus, the associated mobility support signaling (e.g., maintenance of the tunnel, keep alives, etc.) wastes network resources for no application gain. In such a case, it is better to enable 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 which may add to the complicity, existing solutions are more vulnerable to break. Variants: MIP, PMIP, HMIP, FMIP, DSMIP,, etc. Page 25 June 25, 2013 Page 26 June 25, 2013 Distributed mobility anchors Distributed versus centralized mobility anchors Splitting control and data planes: Architecture Unified formulation of Internet mobility DMM Route optimization mechanism example Distributed mobility anchors-architecture LMA functions: mobility routing + location management + HoA allocation. LM LM LM LM MR MR MR MR CN LM: Location management (control plane) MR: Mobility routing (data plane) Page 27 June 25, 2013 Page 28 June 25, 2013

8 Distributed mobility anchors-architecture MR: Mobility routing function (data plane) Network-based: MR in every network, at GW which may move down to AR in flat net Host-based: MR at host Location Management function (control plane) LM is supported by distributed database N t k b d MR i LM i t d b LM LM1 Distributed mobility anchors Distributed versus centralized mobility anchors Splitting control and data planes: Architecture Unified formulation of Internet mobility DMM Route optimization mechanism example MR MR Page 29 June 25, 2013 Page 30 June 25, 2013 Unified formulation of Internet mobility standards 3 Basic Mobility 3 Basic Internet Functions Management Functions 1. The Internet allocates 1. Session identifier IPv6 network prefixes or IPv4 addresses to a host. allocation 2. The Internet manages 2. Location information needed for routing by maintaining a management (LM) database (DNS) and exchanging routing 3. Mobility routing (MR) information between routers. 3. Router forwards packets using appropriate information in the routing table Session continuity Session may continue when EID (inner IP address) does not change. Process Socket = IP addr + Port # Uses EID (Port #) Host stack Network (inner IP address) Uses RLOC Network (outer IP address) Map-and-Encap Page 31 June 25, 2013 Page 32 June 25, 2013

9 Host-based versus Network-based mobility management Host-based mobility management (HoA: P1::mn, : P3::mn) HoA HoA HoA HoA CN MR (P1::mn) Mobility client Network-based mobility management (HoA: P1::mn, : P3::ar) HoA HoA HoA HoA HoA HoA CN MR AR (P3::ar) Mobility client Mobility Management Framework 1. HoA allocation 2. LM: Location management (control plane) g 3. MR: Mobility routing (data plane) Architecture: Configure the logical functions Protocol: Messages Construct one step at a time: MIPv6, PMIPv6, HMIPv6, Distributing mobility anchors, dynamic mobility, DMM Page 33 June 25, 2013 Page 34 June 25, 2013 P3::mn11) Existing protocol: MIPv6 LM1 P3::ar32) Existing protocol: PMIPv6 + Page 35 June 25, 2013 Page 36 June 25, 2013

10 P3::mn11) P3::ar32) MIPv6/PMIPv6 + Hierarchical ) + Page 37 June 25, 2013 Page 38 June 25, 2013 Deploying in all networks ) + Page 39 June 25, 2013 Selective mobility management without ongoing application requiring session continuity LM1 + P321::mm12(current address: ) Page 40 June 25, 2013

11 Selective mobility management with ongoing application requiring session continuity Selective mobility management ) + P12::mn12(home address: HoA12) Page 41 June 25, ) P12::mn12(home address: HoA12) P321::mm12(current address: ) Page 42 June 25, 2013 Mobility Management Framework: HoA of application (in network where appl started) + ) P321::mm12(IP32) Page 43 June 25, 2013 DMM + ) P321::mm12(IP32) Page 44 June 25, 2013

12 Distributed mobility anchors Distributed versus centralized mobility anchors Splitting control and data planes: Architecture Unified formulation of Internet mobility DMM Route optimization mechanism example Page 45 June 25, 2013 DMM Example 1st packet after 1st packet ) + P321::mm12(IP32) Cache: P12::mn12 P3::GW3 P21::cn21 Page 46 June 25, 2013 DMM Example 1st packet after 1st packet Cache: ) (P12::mn12 AR21 + CN22 P321::mm12(IP32) P21::cn21 Page 47 June 25, 2013 Thank you H. Anthony Chan Huawei Technologies h.a.chan@ieee.org that I may serve others. Page 48 June 25, 2013