MobilityFirst Future Internet Architecture. Samuel Nelson

Size: px

Start display at page:

Download "MobilityFirst Future Internet Architecture. Samuel Nelson"

Maude Higgins
5 years ago
Views:

1 MobilityFirst Future Internet Architecture Samuel Nelson

2 MobilityFirst Project: Collaborating Institutions (LEA) A. Venkataramani, J. Kurose,. Towsley M. Reiter S. Bannerjee W. Lehr Z. Morley Mao X. Yang, R. RoyChowdhury G. Chen B. Ramamurthy Project Funded by the US National Science Foundation (NSF) + Also industrial R& collaborations with AT&T Labs, Bell Labs, NTT ocomo,, Toyota ITC, NEC, Ericsson and others 2

MobilityFirst Vision Mobility is viewed as the key driver for the

Cisco white paper predicts >1exabyte per month (surpassing wired PC

3 MobilityFirst Vision Mobility is viewed 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 Internet-connected PC s in 2010 Mobile data growing exponentially Cisco white paper predicts >1exabyte per month (surpassing wired PC traffic) by 2012 Sensor deployment starting Wireless Edge Network INTERNET INTERNET Wireless Edge Network ~2010 ~2020 3

MobilityFirst esign Goals esign a future internet

4 MobilityFirst esign Goals esign a future internet architecture that supports: Host and network mobility iverse communication devices/entities/paradigms Strong security and privacy Large data units, as opposed to flows (e.g., no state) Core 4G Connectivity Wired Wireless Mesh / Cellular Mobile Ad-Hoc TN

5 Architecture Concept: Name and Address Separation Separation of names (I) from network addresses (NA) Globally unique name (GUI) for network attached objects User name, device I, content, context, AS name, and so on Multiple domain-specific naming services

Architecture Concept: Global Name Resolution GNRS responsible for storing, updating (on request), and responding to queries for GUI to NA mappings Target

6 Architecture Concept: Global Name Resolution GNRS responsible for storing, updating (on request), and responding to queries for GUI to NA mappings Target goal: ~50-100ms delays for ~10-100B names ynamic, in-network queries to the GNRS decrease emphasis on end-toend setup and increase emphasis on in-network decisions

Architecture Concept: In-network Storage Utilization Take advantage of cheap storage in the network (storage-aware routing) ~100MB, data in transit

blocks reliably transferred at link layer End-to-end transport does not throttle rate Generalized Storage-Aware Routing Actively monitor link qualities

7 Architecture Concept: In-network Storage Utilization Take advantage of cheap storage in the network (storage-aware routing) ~100MB, data in transit ~10GB, in-network storage ~1TB, content caching Increase routing options Store and/or replicate as feasible routing options Hop-by-hop transport Large blocks reliably transferred at link layer End-to-end transport does not throttle rate Generalized Storage-Aware Routing Actively monitor link qualities of network Router decides whether to store or forward based on 1. Short and long term link qualities 2. Available storage along path 3. Connectivity to destination

8 MobilityFirst Routing Example Utilize both network services (e.g., GNRS) and low-level routing AS3 is a bifurcation point AS3 AS2 AS3 Paths diverge; decide or replicate AS3 AS4 Option to store AS1 AS5 estination Send(M, GUI ) AS4 ; AS5 Update S Source WiFi; 4G GNRS Multi-homing Example

9 MobilityFirst Routing Example Utilize both network services (e.g., GNRS) and low-level routing AS3 is a bifurcation point AS3 AS2 AS3 AS3 Paths diverge; must replicate AS4 Store until available AS1 AS5 estination Send(M, GUI, TN) AS4 ; AS5 S Source often; often GNRS isconnection Example

10 MobilityFirst Content Retrieval Example AS3 C AS6 L Laptop Get(M) Anycast to 3 & 6 AS2 C? AS3, AS6 GNRS AS4 AS5 Business relationship C Provide hooks making it easy for content providers to disseminate content C -> AS3; AS6 P Content Provider

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

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

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

12 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 12

13 Wireless Edge Evaluation: Phases 1, 2 on ORBIT Multi-radio indoor and outdoor nodes with WiMAX, WiFi interfaces 13

Prototyping and Evaluation: Phase 3 on GENI Legend Internet 2 National Lambda Rail OpenFlow Backbones OpenFlow WiMAX ShadowNet MobilityFirst Router Mobile Hosts Static Hosts eployment

14 Prototyping and Evaluation: Phase 3 on GENI Legend Internet 2 National Lambda Rail OpenFlow Backbones OpenFlow WiMAX ShadowNet MobilityFirst Router Mobile Hosts Static Hosts eployment Target Large scale, multi-site Mobility centric Realistic, live Mapping onto GENI Infrastructure (ProtoGENI nodes, OpenFlow switches, GENI Racks, ieselnet buses, WiMAX/outdoor ORBIT nodes) 14

MobilityFirst Prototype: Software Router

15 MobilityFirst Prototype: Software Router Linux-based software router with two-level emulation MF App Services Portable user-level implementation OpenFlow Controller MF Name Resolution MF Routing & Mgmt. User-Level Control Plane Quagga XORP OpenFlow switch host Forwarding Engine 15 Linux routing Click Commodity Hardware NetFPGA

Wired and wireless i/f MobilityFirst Prototype: Click-based Router Linux-based implementation with Click modular router as forwarding engine

16 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 user-level 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 16 x86 hardware and runtime

networking, content delivery and contextaware messaging WiMAX

17 Prototype Framework Client Stack Linux and Android mobile implementation for clients Applications: mobile social networking, content delivery and contextaware messaging WiMAX + WiFi Android Client Also Linux PC/laptop Clients with WiMAX and WiFi 17

18 MobilityFirst Prototype: Android Client evice: HTC Evo, Android 2.3 Unbranded and rooted evelopment: SK, NK, 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 18

19 MobilityFirst Prototype: Status Click-based Router v0.1 implemented Routes MF packets over Ethernet or MAC frames Hop by hop reliable data transfer (Hop) Storage-aware link-state routing with TN extensions (GSTAR) Under evaluation in wired and WiFi networks in ORBIT testbed Integration of R3, an adaptive message replication protocol from UMass, into Click framework under consideration istributed Name Resolution Server Modular C++ version that can support any defined distribution and resolution strategy under development Java version that uses a fixed participation set under development Initial versions are under evaluation in ORBIT/PlanetLab 19

20 MobilityFirst Prototype: Status Contd. Client Stack for Android API paralleling Berkeley sockets defined Accommodates user intent in stack composition, data reception, and resource-to-performance tradeoffs Protocol stack designed using libpcap for low-level packet handling Routing and hop data transfer modules being ported from Click impl. Sample transport layer implementations under development Client Stack for Linux PC/laptop Code from Android/Click will be ported 20

22 Why Not MobileIP? 1. Flexibility and expressiveness MobileIP supports interfaces and works directly on IP addresses GNRS supports entities and works on GUIs Natural support for multi-homing, context, content, etc. 2. Part of the core architecture MobileIP sits high End-points (or home agents) are aware of changes GNRS sits low End-points speaks GUIs, and the network itself directs traffic appropriately, allowing for concepts like access control.

MobilityFirst Prototyping and Evaluation. October 6, 2011 WINLAB

MobilityFirst Prototyping and Evaluation October 6, 2011 1 Prototyping and Evaluation: Execution Summary Phase 1 Phase 2 Phase 3 Context Addressi ng Stack Content Addressi ng Stack Host/Device Addressing