ORBIT 10 Years Later Ivan Seskar, Associate Director WINLAB - PowerPoint PPT Presentation

ORBIT 10 Years Later Ivan Seskar, Associate Director WINLAB Rutgers, The State University of New Jersey Contact: seskar (at) winlab (dot) rutgers (dot) edu WINLAB

Orbit Project Rationale • Wireless testbeds motivated by: – cost & time needed to develop experimental prototypes – need for reproducible protocol evaluations – large‐scale system studies (...emergent behavior) – growing importance of cross‐layer protocol studies – creation of communities for wireless network research • ORBIT: open‐access multi‐user facility for experimental wireless networking research primarily in unlicensed bands – ~24/7 service facility with remote access – open interfaces for flexible layer 2,3 & cross‐layer protocols – extensive measurements at PHY, MAC and Net layers – support for wide range of radio system scenarios WINLAB

ORBIT: Open Access Research Testbed for Next‐Generation Wireless Networks • Proposal: Build radio grid emulator (phase I) and field trial network (phase II) • Emulator used for detailed protocol evaluations in reproducible complex radio environments • Field trial network for further real‐world evaluation & application trials WINLAB

Original Orbit co‐PI’s • WINLAB, Rutgers • Princeton University University – Hisashi Kobayashi – Dipankar Raychaudhuri – Ivan Seskar • IBM Research – Max Ott – Arup Acharya – Wade Trappe – Manish Parashar • Lucent Bell Labs – Yanyong Zhang – Sanjoy Paul • Columbia University • Thomson – Henning Schulzrinne – Kumar Ramaswamy WINLAB

ORBIT WINLAB

Orbit Hardware VPN Gateway to Gigabit backbone Front-end Wide-Area Testbed Servers 80 ft ( 20 nodes ) Data 70 ft m ( 20 nodes ) switch Application Servers (User applications/ Delay nodes/ Mobility Controllers / Mobile Nodes) Control switch IS 1 IS 2 IS Q SA 1 SA 2 SA P RF/Spectrum Measurements Interference Sources Back-end servers Internet VPN Gateway WINLAB / Firewall

ORBIT Radio Node Version 0: COTS: Intel/Atheros Intel/Atheros •Proof of concept miniPCI miniPCI •Prototyping platform 802.11 802.11 1 Ghz Version 2: Custom a/b/g a/b/g 512 MB CPU design: RAM VIA •Functional requirements PCI Gigabit C3 1Ghz •Manageability Ethernet 20 GB (control) •Power consumption DISK Gigabit •Cost Ethernet Other attached (data) 22.1Mhz Serial devices: 110 Console VAC Power CPU 10 BaseT •Bluetooth Rabbit Semi Ethernet Supply pwr/reset RCM3700 (CM) volt/temp •ZigBee +5v standby •GNU Radio RJ11 NodeIdBox WINLAB

ORBIT Radio Node Photo Album ORBIT Radio Node with integrated Chassis Manager Non-Grid Node Chassis Manager WINLAB

Wireless Devices 802.11 n/AC 802.11 a/b/g ZigBee Motes Bluetooth WINLAB

OMF ‐ Experimenter View Testbed(s) Experiment Description Node 1 Apps A Apps A Apps A Experimental Network(s) OML Client Experiment Aggregate Resource Controller Controller Managers (Node Agent) (Node Handler) (Grid Services) …. DB Console Server(s) Node K Apps A Apps A Apps A Control & Management OML Client Network Resource Controller (Node Agent) WINLAB

OML – Measurement Collection Experiment Node Experiment Node Experiment Node Application Application Application Application Measurements OML Server OML Server WINLAB 11

ORBIT Grid WINLAB

Sandboxes: SB4 & SB9 WINLAB

Cognitive Radio Platforms RICE WARP Platform U. Of Colorado USRP WINLAB WINC2R System USRP2 RST SDR System WINLAB

Cognitive Experiments at Scale (2008)  ORBIT radio grid testbed currently supports ~22/USRP and USRP2 (GNU) radios, 100 low-cost spectrum sensors, WARP and WinC2R platforms  Plan to reach ~64 cognitive radio nodes (Q2 2009) Suburban ORBIT Radio Grid 20 meters 500 meters Urban Office Current ORBIT sandbox with GNU radio 400-node Radio Grid Facility at WINLAB Tech Center 300 meters 30 meters Programmable Radio Mapping Concept for ORBIT Emulator ORBIT radio node URSP CR board WINLAB

ORBIT Radio Node (Version 4) I7 ‐ 4770 3.4 GHz Xeon E5 ‐ 2600v3 • • Q87T Express with 18 cores chipset 64 GB DDR4 • 16 GB DDR3 2 x 10G Ethernet • • ports • 2 x Gigabit 2 x Gigabit • Ethernet ports Ethernet ports PCI ‐ Express 2.0 • PCI ‐ Express 3.0 • X16 X16 2 x Mini ‐ • 8 x USB 3.0 • PCIexpress socket OOB Mgmgt. • 8 x USB 3.0 • OOB Mgmgt. • WINLAB

New SDR Devices: USRP B210 / USRP X310  Xilinx Kintex‐7 FPGA  Xilinx Spartan‐6 FPGA (XC7K410T)  Dual channel AD9361  2 x 10 Gigabit Ethernet RFIC transceiver (70 MHz – 6 GHz with 56  1 x SBX RF Daughterboard MHz baseband) (400‐4400 MHz Rx/Tx with  USB 3.0 connectivity 120 MHz baseband)  1 x CBX RF Daughterboard (1200‐6000 MHz Rx/Tx with 120 MHz baseband) WINLAB

SDN (2010) WINLAB

ORBIT: Field Trial Plan (Phase II) 3G Coverage Area 802.11 Access Points / Radio Routers 3G Base Station RU BUS Route (Lines A & H) WINLAB

ORBIT Outdoor Infrastructure RF Module ( sector) Omni‐directional Base antenna Module Outdoor Unit (ODU) (elev. < 6ft above roof!) Experimental readings at one location Rt. 1 Campus Coverage of the CINR = 29 RSSI = -51 WiMAX base station WINLAB

WiMax BS Platforms NEC Airspan Profile A Profile C Access m ode SOFDMA/ TDD Frequency 2 5 3 5 ~ 2 6 0 5 MHz DL:UL ratio 3 5 :1 2 , 2 6 :2 1 , 2 9 :1 8 Channel BW 1 0 MHz , 8 .7 5 MHz PHY FFT size 1 0 2 4 , 5 1 2 Fram e duration 5 m s TX output 3 5 dBm / 4 0 dBm ( m ax) Pow er # of sectors 3 Head PHS com pression ARQ HARQ/ CC, ARQ MAC MBS support Single BS, m ultiple BS- MBS Resource Pow er control, m ode m anagem ent control ( idle, sleep etc.) I P protocols I Pv4 , I Pv6 Bridging/ Routi Transparent L2 sw itch, Netw orking ng Bridging Packet handling 8 0 2 .1 Q VLAN, PHS* * ) WINLAB

Mobile Platforms Intel 5150/5350 mini‐PCI express card for ORBIT Node laptops with Linux driver HTC EVO 4G Android based portable platform

Scale: Integrated ORBIT – PlanetLab Experiments Streaming Video Performance

GENI & FIA WINLAB

Revolutionary GENI Idea: Slices and Deep Programmability Install the software I want throughout my network slice (into firewalls, routers, clouds, …) And keep my slice isolated from your slice, so we don’t interfere with each other We can run many different “future internets” in parallel WINLAB Courtesy: Chip Eliot, GENI GPO

Enabling “at scale” experiments • How can we afford / build GENI at sufficient scale? Clearly infeasible to build research testbed “as big as the Internet” – Therefore we are “GENI‐enabling” testbeds, commercial equipment, campuses, regional and – backbone networks Students are early adopters / participants in at ‐ scale experiments – – Key strategy for building an at‐scale suite of infrastructure HP ProCurve 5400 Switch NEC WiMAX Base Station GENI-enabled campuses, GENI-enabled “At scale” GENI prototype students as early adopters WINLAB equipment Courtesy: Chip Eliot, GENI GPO Campus photo by Vonbloompasha

GENI’s Footprint WINLAB

“Opening” of WiMAX & LTE WiMAX Exposed all controllable parameters through • API Removed all default IP routing, simplified ASN • controller* • All switching purely based on MAC addresses Implemented the datapath virtualization and • eth2 VNTS shaping mechanism in click/openvswitch for slice isolation LTE eth0.vl 1 Exposed all controllable • parameters through the same eth0.vl 2 X2,S1-U,S1-MME,... REST based API • Implemented the datapath with openvswitch Current development: ePC • replacement with open source (i.e. eth0.vl n simplification/elimination of LTE control protocols) WINLAB

GENI Wireless Deployment • 26 WiMAX and LTE BS on 14 campuses • SDN (Click and OVS based) datapath/backbone • 10 mini ‐ ORBIT deployments some with SDRs Kettering U Michigan Wayne State UMass U Wisconsin Madison Rutgers U Colorado Boulder Stanford NYU Utah Drexel Columbia Temple UCLA Clemson WINLAB

LTE eNodeB Platforms Amarisoft OAI Ip.access Airspan (USRP) (USRP) Rel 10 Rel 8.9 Rel 12 Rel 8.6 (upgreadable) FDD FDD/TDD FDD/TDD TDD/(FDD) 10MHz 20 MHz 10 MHz 20 MHz 10 dBm 10 dBm 2 x 37 dBm 2 x 10 dBm (2 x 10 dBm) (4 x 30 dBm) (2 x 40 dBm) 13 Mbps BW limited 20 Mbps 300 Mbps 4 (max idle 64) BW limited 5 (25) > 100 (256) WINLAB

4G (WiMax/LTE): Larger Picture WINLAB

FIA: MobilityFirst Architecture Summary

MobilityFirst Architecture Evaluation Characteristics and Requirements • Mobile nature generates particular requirements for experimentation scenarios. • Named oriented architecture requires coexistence of multiple routing paradigms at ones. Direct MobilityFirst Mobility as the Hybrid name addressability In‐network Characteristics norm based routing of all network services principals Flexible service High levels of Strict Support for support and mobility performance coexisting deployment Expected requirements multiple Scenarios for name routing Reliance on Device resolution algorithms software heterogeneity service WINLAB