MobilityFirst Architecture and Protocol Evaluation on GENI. November 3, 2011 WINLAB

Transcription

1 MobilityFirst Architecture and Protocol Evaluation on GENI November 3,

2 MobilityFirst Project: Collaborating Institutions (LEAD) D. Raychaudhuri, M. Gruteser, W. Trappe, R, Martin, Y. Zhang, I. Seskar, K. Nagaraja, S. Nelson 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

3 Vision: 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

4 Architecture: MobilityFirst Network Overview MF Arch designed to meet emerging mobile/wireless service requirements at scale Key MF protocol features: Separation of naming & addressing Public-key globally unique identifier (GUID) and flat network address (NA) Storage-aware (GDTN) routing Multicast, multipath, anycast services Flexible inter-domain boundaries and aggregation level Early binding/late binding options Hop-by-hop (segmented) transport Support for content & context Strong security and privacy model Separate mgmt & computing layers Data block Base Station Name <-> PKI address mapping AP MobilityFirst Router with Integrated Computing & Storage Hop-by-Hop Transport GDTN Routing Wireless Router Computing Blade Buffer Storage Forwarding Engine Core Network (flat label routing) Data Plane Control & Management Plane Router Global Name Resolution Service Several new protocol components, very distinct from today s TCP/IP.

5 Architecture Concepts: 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) Network Content Naming Service Global Name Resolution Service Net2.local_ID Context Naming Service Taxis in NB

6 Architecture Concepts: Global Name Resolution Service for Dynamic Name <-> Address Binding Fast Global Name Resolution a central feature of architecture GUID <-> network address (NA) mappings Distributed service, possibly hosted directly on routers Fast updates ~ ms to support dynamic mobility Service can scale to ~10B names via P2P/DHT techniques, Moore s law Mobile node trajectory Network NA2 Registration update Host GUID NA2 Data Plane AP Network NA1 Host GUID NA1 Initial registration Global Name- Address Resolution Service Decentralixed name services Hosted by subset of ~100,000+ Gatway routers in network Host Name, Context_ID or Content_ID Network Address

7 Cumulative Distribution Function (CDF) Protocol Design: Direct Hash 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) 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

8 Protocol 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 from switching (good path) to store-andforward (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

9 Example: GUID/Address Routing Scenarios Dual Homing, Partial Disconnection The combination of GUID and network address helps to support new mobility related services including multi-homing, anycast, DTN, context, location Dual-homing scenario below allows for multiple NA:PA s per name GUID NA1:PA22; NA7:PA13 Router bifurcates PDU to NA1 & NA7 (no GUID resolution needed) GUID Net 1 NetAddr= NA1.PA22 Data Plane Net 7 Alice s laptop GUID = xxx Dual-homed mobile device GUID/SID NA1:PA22; NA7:PA13 GUID NetAddr= NA7.PA13 GUID & SID Send data file to Alice s laptop Current network addresses provided by GNRS; NA1:PA22 ; NA7:PA13

10 Protocol Design: MF Stack Core elements of MF protocol stack GUID services layer, supported by control protocols for bootstrap & updates GUID to network address mapping (GNRS) for dynamic mapping of GUID Generalized storage-aware routing (GSTAR) with supporting control protocols Reliable hop-by-hop block transfer between routers Management plane protocol with its own routing scheme Multiple TP options and plug-in programmable services at GUID layer APP-1 APP-2 APP-n Name Certification Service A E2E Transport Protocol A E2E Transport Protocol B.. E2E Transport Protocol B Mgmt Apps Management Plane Protocols (incl. routing) Routing Apps Routing Control Protocols GUID Services Control Protocols GUID Service Layer GUID-to-Net Address Mapping Storage-Aware Routing (GSTAR) Computing Layer Service Plug-ins Hop-by-hop Block Transfer Protocol Link Layer A (e.g fiber) Link Layer B (e.g LTE) Link Layer C (e.g WiFi) Link Layer D (e.g Ethernet

11 Prototyping and Evaluation: Execution Summary Phase 1 Phase 2 Phase 3 Context Addressi ng Stack Content Addressi ng Stack Host/Device Addressing Stack Encoding/Certifying Layer Global Name Resolution Service (GNRS) Storage Aware Routing Locator-X Routing (e.g., GUID-based) Context-Aware / Late-bind Routing Prototype Standalone Modules Evaluation Simulation and Emulation Integrated MF Protocol Stack and Services Smaller Scale Testbed Deployable s/w pkg., box Distributed Testbed E.g. Live on GENI 11

12 Wired and wireless i/f MobilityFirst Prototype: Click-based Router Linux-based implementation with Click modular router as forwarding engine Two-level abstraction: fast path as Click elements, slow path as userlevel processes (control and support services) User-level Processes Routing Name Resolution Content Cache Mgmt. Click Forwarding Engine Rx Q Classifier Host Rx Q Block Aggregator To/From Host Forwarding Table Next-hop Look up Host Tx Q To Next-hop Lookup Block Segmentor Rsrc Control Tx Q Wired and wireless i/f Forwarding Elements Hold buffer x86 hardware and runtime 12

13 MobilityFirst Prototype: Android/Linux Client Implementation Device: HTC Evo, Android 2.3 Unbranded and *rooted* Development: SDK, NDK, flash a modified kernel (if required) WiFi, WiMAX interfaces Modules in Android s MF stack MF-socket API - user level library Transport layer Storage aware routing SHIM layer support for multi-homing 1-Hop reliable data transfer MF-socket API open, send, send_to, recv, recv_from User policies for resource use and intentional data receipt 13

14 MobilityFirst Prototype: Network Architecture Edge networks NA-1, NA-2 connected to global core network Each of NA-1, NA-2 are contained MF routing domains Each WiMAX BSS and WiFi AP is associated with a MF Router Node a is multi-homed within a network Node c is multi-homed across 2 networks NA-1 WiFi AP WiMAX BSS MF Router Android Client w/ WiMAX + WiFi a b c NA-2 d e Linux PC/laptop w/ WiMAX + WiFi Vehicular node w/ WiMAX Sensor node MF Sensor GW Ad hoc networks: Nodes can form ad hoc networks which are named and can attach to existing networks to be globally reachable themselves 14

15 GENI Deployment: Phase 3 on Multiple Sites Legend Internet 2 National Lambda Rail OpenFlow Backbones OpenFlow WiMAX ShadowNet MobilityFirst Router Mobile Hosts Static Hosts Deployment Goals Large scale, multi-site Mobility centric Realistic, live Mapping onto GENI Infrastructure (ProtoGENI nodes, OpenFlow switches, GENI Racks, DieselNET buses, WiMAX/outdoor ORBIT nodes) 15

16 GENI Deployment: WiMAX and WiFi Edges at Rutgers and BBN BBN Cambridge ProtoGENI Backbone WiFi AP WiMAX BSS MF Router + Name Resolution Server Android Client w/ WiMAX + WiFi Linux PC/laptop w/ WiMAX + WiFi Vehicular node w/ WiMAX Sensor node MF Sensor GW N. Brunswick 16

17 GEC-12 Experiment: Overview Network: Edge networks connected to Protogeni backbone WiFi and WiMAX at edges. Mobile hosts and access network. Deployed MF components: MF prototype router with Storage Aware Routing and Name Resolution Service MF Clients including Linux PC/laptops/Android Phone (and vehicular nodes) Applications: Edge to edge content delivery Demonstration Focus: Multi-homing - convergence of WiFi and WiMAX Network-level adaptation to mobility (varying link quality) and disconnection 17

18 Experiment Setup : Proposed MF Network Graph R3 R5 WiFi AP R1 NA-1 GUID=1 NA-3 GUID=3 NA-5 GUID=5 R7 NA-6 GUID=6 WiFi AP GUID=101 WiMAX BTS GUID=2 NA-2 R2 GUID=4 NA-4 R4 GUID=7 NA-7 R6 WiMAX BTS GUID=201 Rutgers Wireless Edge ProtoGENI Backbone BBN Wireless Edge ProtoGENI host running MF Router 18

19 GENI Deployment: Physical Topology Washington NLR Seattle Wisconsin BBN Indiana NLR SUNW NLR Denver NLR Chicago Rutgers I2 New York Clemson I2 Washington Stanford I2 Los Angeles Georgia Tech. I2 Atlanta I2 Houston I2 OF Switch VLAN 3715 NLR OF Switch VLAN 3716 Edge OF Switch

20 GENI Deployment: Mapping to Logical Topology Washington NLR Seattle Wisconsin BBN Indiana WiFi AP NLR SUNW NLR Denver GUID=1 GUID=3 GUID=5 Clemson Bridge NLR Chicago Clemson GUID=6 Rutgers WiFi AP I2 New York I2 Washington Stanford I2 Los Angeles GUID=2 GUID=4 GUID=7 Georgia Tech. I2 Atlanta WiMAX BTS I2 Houston WiMAX BTS I2 OF Switch VLAN 3715 NLR OF Switch VLAN 3716 Edge OF Switch

21 Application: Content Delivery to Mobile Hosts NA Content Subscriber WiFi AP GUID & SID R7 GUID=1 GUID=2 GUID=3 GUID=5 Bridge GUID=4 GUID=7 GUID=6 WiFi AP #9 GUID=201 GUID=101 Content Publisher WiMAX BTS BBN Wireless Edge WiMAX BTS Rutgers Wireless Edge NLR path using VLANs 3716, 3799 (Clemson) I2 path using VLANs 3715, 3745(BBN), 3798 (Clemson) ProtoGENI host running MF Router 21

22 Visualization MF Network element e.g. Router NRS Click Monitor and filter Runtime/OS Data collection framework with API, monitors, filters and data warehouse E.g., Orbit Measurement Library (OML) Network State Repository Web Server HTTP, XML, JSON What s on? 1. Network statistics 2. Packet and flow tracing 3. Routing events 4. Application events Browser: AJAX/JS/Flash Network map credits: ProtoGENI s Flack tool. 22