MobilityFirst Architecture Summary WINLAB Research Review May 14, 2012

Transcription

1 MobilityFirst Architecture Summary Research Review May 14, 2012 Contact: D. Raychaudhuri, Rutgers University Technology Centre of NJ 671 Route 1, North Brunswick, NJ 08902, USA

2 NSF Future Internet Architecture (FIA) Program FIA program started in Oct 2010, with 4 teams funded: XIA (led by CMU) project aims to develop very flexible architecture which can evolve to meet new requirements NEBULA (led by UPenn) project aims to design fast/managed flows to cloud services at the core of the Internet NDN (led by UCLA/PARC) project aims to re-design Internet to handle named content efficiently MobilityFirst (led by Rutgers) project aims to develop efficient and scalable architecture for emerging mobility services Scope of all these FIA projects includes architecture/design, protocol validation and comprehensive evaluation of usability and performance (using real-world applications in later stages)

3 MobilityFirst Project: Overall Goals MobilityFirst objectives from the NSF FIA project abstract (Aug 2010): This project is aimed at the design and experimental validation of a comprehensive clean-slate future Internet architecture. The major design goals of the architecture are: mobility as the norm with dynamic host and network mobility at scale; robustness with respect to intrinsic properties of the wireless medium; trustworthiness in the form of enhanced security and privacy; usability features such as support for context-aware services, content, evolvability, manageability and economic viability. The project s scope includes architectural design, validation of key protocol components, testbed prototyping, and real-world protocol deployment on the GENI experimental infrastructure.

4 MF Project: Yearly Goals/Outcomes Year 1 - architecture white paper, protocol specs, component-level prototypes (NRS, GDTN routing, Hop TP, PKI security, context services, computing layer, etc.) and early lab demo of the network Year 2 detailed validations of key components, network evaluation results, and a multi-site proof-of-concept network prototype Year 3 - updated protocol design based on evaluation feedback, and medium-scale service deployment using GENI infrastructure. The project will conclude with a comprehensive validation and evaluation of usability and performance using both controlled experiments and application trials with real-world end-users.

5 MF Project: Progress Highlights as of 5/12 (1) Group consensus on MobilityFirst protocol architecture Baseline MF protocol design completed and spec doc 0.9 posted complete ver 1.0 spec release 6/12 Key protocol components going through design, evaluation and redesign process GUID service layer with support for mcast, mhoming, mpath,.. Global name resolution service (GNRS) Storage-aware intra-domain routing (GSTAR) Edge-aware inter-domain routing with hybrid GUID/NA, late binding.. Content and context/m2m services Compute layer for enhanced services Spiral development of proof-of-concept MF prototype MF router framework using Click platform; Android mobile protocol stack GNRS and GSTAR protocols Content and context service implementations ORBIT and GENI experiments; first MF demo at Nov 2011 GEC

6 MF Project: Progress Highlights as of 5/12 (2) Initiated project on MF integration with optical networks/openflow Ongoing research and design work on security/privacy Core security architecture and protocols Privacy considerations and design options DDOS resistance and robustness Economic models and policy analysis Cellular-internet convergence scenarios Industry structure, privacy/censorship issues, network neutrality, etc. Participation in recent FIA meeting (April 19,20) on business models

7 MobilityFirst Project: Collaborating Institutions (LEAD) D. Raychaudhuri, M. Gruteser, W. Trappe, R, Martin, Y. Zhang, I. Seskar, K. Nagaraja A. Venkataramani, J. Kurose, D. Towsley M. Reiter S. Bannerjee W. Lehr Z. Morley Mao B. Ramamurthy X. Yang, R. RoyChowdhury G. Chen Project Funded by the US National Science Foundation (NSF) Under the Future Internet Architecture (FIA) Program, CISE + Also industrial R&D collaborations with AT&T Labs, Bell Labs, NTT DoCoMo,, Toyota ITC, NEC, Ericsson and others

8 Introduction

9 Introduction: Mobility as the key driver for the future Internet Historic shift from PC s to mobile computing and embedded devices ~4 B cell phones vs. ~1B PC s in 2010 Mobile data growing exponentially Cisco white paper predicts 3.6 Exabytes by 2014, significantly exceeding wired Internet traffic Sensor/IoT/V2V just starting, ~5-10B units by 2020 ~1B server/pc s, ~700M smart phones ~2B servers/pc s, ~10B notebooks, PDA s, smart phones, sensors INTERNET Wireles s Edge Networ k INTERNET Wireless Edge Network ~2010 ~2020

10 Introduction: Near-term mobile Internet usage scenario ISP as mobility service provider Mobility services similar to cellular enabled by MF architecture Seamless mobility for all Internet devices/services as a standard feature ISP can offer mobile data services qualitatively similar to cellular Expansion of free WiFi services, aggregated roaming agreements, etc. Mobile User Virtual Network AS-96=AS-9+AS-41 AS-41 Regional Aggregate VN mgmt interface SLA+ interface For roaming agreements AS-9 AS-208 Requires protocol support for aggregating non-contiguous AS s into virtual AS

11 Introduction: Near-term mobile Internet usage scenario cellular convergence ~5B smartphones worldwide (by 2015) will drive convergence of both technical standards and business models Currently involves 2 sets of addresses (cellular number & IP), 2 sets of protocols (3GPP and IP), and protocol gateways (GGSN, PDN GW, etc.) Scalability, performance and security problems when bridging 2 networks Cross-layer interaction between PHY/MAC and TCP/IP impacts performance Lack of a single unified standard inhibits mobile Internet app development across diverse networks and platforms INTERNET Cellular Internet GW Cellular Internet GW MOBILE INTERNET Radio Access C Cellular system B Cellular system A Mobility, Security Varying Access bw Heterogeneous radio Radio Access Net A Radio Access B

12 Introduction: Near-term mobile Internet usage scenario Mobile P2P and Infostations P2P and Infostations (DTN-like) modes for content delivery becoming mainstream Heterogeneous access; network may be disconnected at times Both terminal & network mobility; dynamic trust identity vs. address Requires content caching and opportunistic data delivery MOBILE INTERNET Mobile DTN Router Opportunistic High-Speed Link (MB/s) Ad-Hoc Network Roadway Sensors Disconnection Opportunistic access Message ferry/dtn Content delivery/cache Infostations Router Mobile P2P User Mobile DTN User/Router

13 Introduction: Future mobile Internet usage scenarios vehicular networks 100 s of million cars will be equipped with radios by ~2015 Both V2V (vehicle-to-vehicle) and V2I (vehicle-to-infrastructure) modes Involves capabilities such as location services, georouting, ad hoc networks Important new trust (security and privacy) requirements in this scenario V2I Irrelevant vehicles in radio range for few seconds V2V Passing vehicle, in radio range for seconds Following vehicle, in radio range for minutes Geographic routing/multicast Dynamic network formation, trust Location & context services

14 Introduction: Emerging mobile Internet usage scenarios pervasive/m2m/iot The next generation of Internet applications will involve interfacing human beings with the physical world Wide range of usage scenarios including healthcare, smart grids, etc. Networking requires awareness of location, content and context Challenges content/context services, security and robustness Cloud computing models with in-network processing & storage Ambient interfaces Human in the Loop Cloud Applications To Actuators Global Pervasive Network (Future Internet) Protocol module Data From Sensors Content & Location Aware Routers Healthcare Application Virtualized physical world object Computation & Storage Network Connectivity & Computation Vehicles with Sensors & Wireless Context- and content-services In-network computing options cloud computing models Smart Grids Robotics Application

15 MobilityFirst Architecture Concepts

16 Architecture: Why Are Mobile Networks Different? BW Variation & Disconnection The wireless medium has inherent fluctuations in bit-rate (by as much as 10:1 in 3G/4G access, heterogeneity and disconnection fundamental protocol design challenge Motivates in-network storage and hop-by-hop transport (solutions such as CNF, DTN,..) Mobile devices with varying BW due to SNR variation, Shared media access and heterogeneous technologies BS-1 Bit Rate (Mbps) BS-1 Disconnect AP-2 Wireless Access Net #3 INTERNET Disconnection internal Time Wireless Access Network #2 AP-2

17 Architecture: Why Are Mobile Networks Different? - Multihoming, Multipath Wired Internet devices typically have a single Ethernet interface associated with a static network/as In contrast, mobile devices typically have ~2-3 radios and can see ~5-10 distinct networks/as s at any given location Basic property - multiple paths to a single destination leads to fundamentally different routing, both intra and inter domain! Mobile device with multi-path reachability Single virtual link in wired Internet Wireless Access Net #1 BS-1 Wireless Access Network Wireless Access Net #3 BS-2 INTERNET Access Network (Eithernet) Ethernet NiC INTERNET Wireless Edge Network AP1 BS-3 Multiple Potential Paths Dual Radio NIC s

18 Architecture: Why Are Mobile Networks Different? Multicast Many mobility services (content, context) involve multicast The wireless medium is inherently multicast, making it possible to reach multiple end-user devices with a single transmission Fine-grain packet level multicast desirable at network routers Session level Multicast Overlay (e.g. PIM-SIM) Packet-level Multicast at Routers/AP s/bss Pkt Mcast at Routers Wireless Access Net #11 INTERNET RP Access Network (Eithernet) INTERNET Wireless Access Net #32 Radio Broadcast Medium

19 Architecture: Why Are Mobile Networks Different? Ad Hoc & Network Mobility Wireless devices can form ad hoc networks with or without connectivity to the core Internet These ad hoc networks may also be mobile and may be capable of peering Requires rethinking of interdomain routing, trust model, etc. Ad Hoc Network Formation, Intermittent Connection to Wired Internet & Network Mobility Access Network INTERNET Access Network ) )

20 Architecture: Why Are Mobile Networks Different? Content & Context Content and context aware message delivery often associated with mobile services Anycast content retrieval from nearest storage location (cache) Context based message delivery specific by group, area, time, etc. Service typically involves dynamic binding of content or context to a specific set of network addresses along with multicast delivery Context = geo-coordinates & first_responder Send (context, data) Context Naming Service Context GUID Global Name Resolution service ba x NA1:P7, NA1:P9, NA2,P21,.. Context-based Multicast delivery Mobile Device trajectory

21 MobilityFirst Protocol Design

22 MobilityFirst Design: Architecture Features Named devices, content, and context Human-readable name Strong authentication, privacy Public Key Based Global Identifier (GUID) End-Point mobility with multi-homing Heterogeneous Wireless Access Routers with Integrated Storage & Computing In-network content cache Service API with unicast, multi-homing, mcast, anycast, content query, etc. Storage-aware Intra-domain routing Edge-aware Inter-domain routing Hop-by-hop file transport Connectionless Packet Switched Network with hybrid name/address routing Network Mobility & Disconnected Mode Ad-hoc p2p mode

23 MobilityFirst Design: Technology Solution Name Certification Service (NCS) Flexible name-based network service layer Global Name Resolution Service (GNRS) Name-Based Services (mobility, mcast, content, context, M2M) Optional Compute Layer Plug-Ins (cache, privacy, etc.) Meta-level Network Services Hybrid GUID/NA Global Routing (Edge-aware, mobile, Late binding, etc.) Storage-Aware & DTN Routing (GSTAR) in Edge Networks Hop-by-Hop Transport (w/bypass option) Core Transport Services Pure connectionless packet switching with in-network storage

24 MobilityFirst Design: Name-Address Separation Separation of names (ID) from network addresses (NA) Globally unique name (GUID) for network attached objects User name, device ID, content, context, AS name, and so on Multiple domain-specific naming services Global Name Resolution Service for GUID NA mappings Hybrid GUID/NA approach Both name/address headers in PDU Fast path when NA is available GUID resolution, late binding option Sue s_mobile_2 Network address Net1.local_ID John s _laptop_1 Host Naming Service Server_1234 Sensor Naming Service Sensor@XYZ Media File_ABC Globally Unique Flat Identifier (GUID) Global Name Resolution Service Network Content Naming Service Net2.local_ID Context Naming Service Taxis in NB

25 MobilityFirst Design: Realizing the GNRS Fast GNRS implementation based on DHT between routers GNRS entries (GUID <-> NA) stored at Router Addr = hash(guid) Results in distributed in-network directory with fast access (~100 ms) 1 Cumulative Distribution Function (CDF) K = 5, 95 th Percentile at 91 ms K = 1, 95 th Percentile at 202 ms K = 1 K = 2 K = 3 K = 4 K = ,000 Round Trip Query Latency in milliseconds (log scale) Internet Scale Simulation Results Using DIMES database

26 MobilityFirst Design: Storage-Aware Routing (GSTAR) Storage aware (CNF, generalized DTN) routing exploits in-network storage to deal with varying link quality and disconnection Routing algorithm adapts seamlessly adapts from switching (good path) to store-and-forward (poor link BW/short disconnection) to DTN (longer disconnections) Storage has benefits for wired networks as well.. Temporary Storage at Router Initial Routing Path Low BW cellular link PDU Storage Router Re-routed path For delivery Mobile Device trajectory High BW WiFi link Sample CNF routing result

27 MobilityFirst Design: Segmented Transport Segment-by-segment transport between routers with storage, in contrast to end-to-end TCP used today Unit of transport (PDU) is a content file or max size fragment Hop TP provides improved throughput for time-varying wireless links, and also helps deal with disconnections Also supports content caching, location services, etc. PDU Segmented (Hop-by-Hop TP) Hop #3 BS Hop #1 Hop #2 Hop-by-Hop Transport Storage Router Temporarily Stored PDU Optical Router (no storage) Low BW cellular link Hop #4 GID/Service Hdr Mux Hdr More details of TP layer fragments with addl mux header Data Frag 1 Data Frag 2 Data Frag n Net Address Hdr

28 MobilityFirst Design: Interdomain Routing Requirements include: edge awareness, flexible network boundaries, dynamic AS formation, virtual nets, network mobility, DTN mode, path selection, multipath, multi-homing, etc. Motivates rethinking of today s 2-tier IP/BGP architecture (inter-as, intranet) MobilityFirst interdomain approach uses GNRS service + enhanced global routing protocol (path vector, telescopic flooding) to achieve design goals still evaluating multiple design options. Core Net 17 Access Net 200 Core Net 23 Access Net 500 Path Vector+ Routing Plane Path Vector+ Routing protocol Provides reachability & path info between networks Mobile Net 1 Mobile Net 2 Global GNRS directory GNRS provides Net name <-> addr mapping

29 MobilityFirst Design: Computing Layer Programmable computing layer provides service flexibility and evolution/growth path Routers include a virtual computing layer to support new network services Packets carry service tags and are directed to optional services where applicable Programming API for service creation provided as integral part of architecture Computing load can be reasonable with per-file (PDU) operations (vs. per packet) MF Compute Layer with service plug-ins Plug-in Module MF Compute MF Compute Plug-in Module Enhanced Service Provider Interface

30 MobilityFirst Design: Protocol Stack App 1 App 2 App 3 App 4 Name Certification & Assignment Service NCS Socket API E2E TP1 E2E TP2 E2E TP3 E2E TP4 Optional Compute Layer Plug-In A Global Name Resolution Service GNRS GUID Service Layer Narrow Waist MF Routing Control Protocol GSTAR Routing Hop-by-Hop Block Transfer MF Inter-Domain Switching Option IP Link Layer 1 (802.11) Link Layer 2 (LTE) Link Layer 3 (Ethernet) Link Layer 4 (SONET) Link Layer 5 (etc.) Control Plane Data Plane

31 MobilityFirst Protocol Stack Examples

32 MobilityFirst Examples: How MF Works - (1) At the Device End-Points Service API capabilities: - send (GUID, options, data) Options = anycast, mcast, time,.. - get (content_guid, options) Options = nearest, all,.. GUID lookup from directory Name Certification Services (NCS) Register John Smith22 s devices with NCS GUID assigned MobilityFirst Network (Data Plane) NA99 GNRS update (after link-layer association) Send (GUID = , SID=01, data) NA32 GUID <-> NA lookup GNRS query GNRS GUID = Send (GUID = , SID=01, NA99, NA32, data) Represents network object with 2 devices DATA GUID SID NAs Packet sent out by host

33 MobilityFirst Examples: How MF Works - (2) At Router, AP or BS Example of Functions at Branching Router for a Multicast Packet to be delivered to NA99 and NA32 GUID based forwarding (slow path) Look up GUID-NA table when: - no NAs in pkt header - encapsulated GUID - delivery failure or expired NA entry GUID-Address Mapping virtual DHT table GUID NA NA99,32 To NA11 DATA DATA To NA51 Router Storage Store when: - Poor short-term path quality - Delivery failure, no NA entry - GNRS query failure - Content cache decision - etc. GUID= SID NA99,NA32 Look up NA-next hop table when: - pkt header includes NAs - valid NA to next hop entry NA Routing Table stored physically at router Dest NA NA99 NA62 NA32 Next Hop NA11 NA11 NA51 Network Address Based Forwarding (fast path) DATA

34 MobilityFirst Examples: How MF Works - (3) Multicast Service Multicast service example DATA Router bifurcates PDU to NA99 & NA32 (no GUID resolution needed) GUID DATA NetAddr= NA99 NA99 Data Plane NA32 DATA DATA GUID= SID NA99,NA32 DATA GUID NetAddr= NA32 GUID SID Send data file to John Smith22 s devices, SID= 21 (mcast)

35 MobilityFirst Examples: How MF Works - (4) Dual Homing Scenario Multihoming service example DATA Router bifurcates PDU to NA99 & NA32 (no GUID resolution needed) GUID DATA NetAddr= NA99 NA99 Data Plane NA32 DATA DATA GUID= SID NA99,NA32 DATA GUID NetAddr= NA32 GUID SID Send data file to John Smith22 s laptop, SID= 129 (multihoming all interfaces)

36 MobilityFirst Examples: How MF Works - (5) Handling Disconnection Store-and-forward mobility service example GUID DATA NA99 rebind to NA75 Delivery failure at NA99 due to device mobility Router stores & periodically checks GNRS binding Deliver to new network NA75 when GNRS updates NA99 Data Plane NA75 Disconnection interval Device mobility DATA DATA GUID SID NA99 DATA GUID NA75 GUID SID Send data file to John Smith22 s laptop, SID= 11 (unicast, mobile delivery)

37 MobilityFirst Examples: How MF Works (6) Enhanced CDN Service Enhanced service example content delivery with in-network storage GUID= NA31 NA43 GUID= MF Compute Layer with Content Cache Service plug-in Filter on SID=128 Content cache at mobile Operator s network NA99 GUID= NA99 GNRS query Returns list: NA99,31,22,43 NA22 Content Owner s Server GUID= NA29 GNRS Query Data fetch from NA43 Get (content_guid) Data fetch from NA99 Content file Mobile s GUID Get (content_guid, SID=128 - cache service) Query User mobility GUID= SID=128 (enhanced service)

38 Resources Project website: GENI website: ORBIT website: