WINLAB Joint Work: WINLAB, NECLA, NICTA A Brief Tutorial on WiMAX setup using OMF

WINLAB Overview System architecture Control API Use of the VM Grid service to setup an experiment Example scenario

WINLAB Prototype Architecture ASN SubstratevBTS Substrate Cons-wm-02 eth2 Cons-wm-03 eth2 Outdoor Network eth0 eth1 Instrumentation Network Internal Network Base Station (BTS) eth1 eth0 Outside World Outside Bus (Trunk) VM Bus (Trunk) Original Components Of the BTS

WINLAB API Architecture

WINLAB Baseline Experiment Setup Steps Admin Functions User commands: – (1) Create/Destroy Slice – (2) Start/Stop Slice – (3) Add Client RF API – Discussed in detail on the Wiki

WINLAB Baseline Admin. Functions Initialize the grid service: – wget Initializes the VM grid service Checks for running VMs and initializes datapath on the machine List all running slices in XML format: – wget Allows the administrator to have a detailed view of the running VMs Shows VM statistics in XML format

WINLAB Start and Stop Slice Functionality: – Starts/Stops VM instance – Configures VLANs on VM substrate wget = vm1http://wm-asngw-02:5012/wimaxvm/start?vmname wget = vm1http://wm-asngw-02:5012/wimaxvm/stop?vmname

WINLAB Add Mobile Functionality: – Registers a client with the slice – Currently adds default service flow settings for the client – Adds mapping to the datapath controller on ASN- GW Call: – wget = vm1\& clientmac = 84:22: b.9ahttp://wm-asngw-02:5012/wimaxvm/addclient?vmname

WINLAB Mock Experiment Sequence Mobile associates, gets added to default slice, starts UL traffic Slice user starts a new slice, adds the mobile to its slice Datapath switch from (Mobile – VM0)  (Mobile – VM1) Physical BTS ASN-GW Default Slice (VM-0) User Slice (VM-1) Air Interface

WINLAB Thanks.

WINLAB Appendix

WINLAB Project Overview The project leverages a commercial e base station from NEC. We build an open software controller around a standard WiMAX BTS for allowing integration and use as a part of the GENI framework. The setup should support sharing of the BTS and provide layer 2/3 programmability.

WINLAB BTS Virtualization Virtualization – Abstraction Provide the illusion of owning the entire hardware to each slice – Programmability Sufficient degree of freedom to every experimenter – Isolation Control and prevent the impact of one slice on the other Physical BTS Each user sees an independent BTS Isolation Slice – refers to the share of the resources owned by a particular user. User A User B Terminology

WINLAB Challenges In Sharing The BTS BTS framework should be time shared in such a way that every experimenter/slice : – Has the illusion of using the entire BTS Similar or scaled delay/throughput characteristics Similar access interface – Has similar control to the BTS Adding its own set of clients, custom service flows Can run an IP independent protocol stack – Has minimum coupling with experiments from other slices

WINLAB Why have an ``Open” Basestation? Capabilities of an open basestation: – Access to the experimenter community – Measurement and data collection from the framework – Control over some BTS parameters Driven by the NSF GENI* initiative – A large federated testbed infrastructure with wireless edges Allows shift of research: Simulation  Prototyping *

WINLAB Range of experiments Longer range for a control channel – Outdoor mobility: Vehicular, and or walking. – Collection of GPS traces, sensor measurement, … Allows evaluation of end – to – end links – Used in conjunction with a wired experimentation backbone such as PlanetLAB or VINI With enough Basestations: – Evaluate a service with ``real” traffic – Comparing Handoff mechanisms Optimization and evaluation of transport mechanism for performance over cellular wireless Performance evaluation of a wide area network Security

WINLAB Envisioned Architecture Experimenters include the BTS as a part of their experiments Backbone is time shared..so.. How do we share the BTS? GENI terminals (WiMAX phone/PDA running GENI/Linux) Virtual GENI Router (at PoP) GENI Backbone Network GENI Access Network (Ethernet SW & Routers) GENI Compliant WIMAX Base Station Controller WiMAX Base Station (GBSN)

WINLAB Design & Implementation

WINLAB BTS Hardware Roof mounted Antenna Operational with an educational license Inherently IP based Basestation (IDU) Unit RF (ODU) Amplifier

WINLAB Major additions and changes All packet forwarding is now L2 – Eliminated all IP routing from the datapath Provided API within each virtual machine to interact with the BTS – Similar features to that provided on the raw BTS (Add client, remove client, setup service flows …) Mechanism for isolation between slices – VNTS traffic shaping mechanism

WINLAB vBTS Architecture Redirect all traffic from VLANs to individual slices Similar redirection from slices to outbound VLAN interfaces Grid services for creation, destruction, maintenance of slices, adding clients, slice allocation control … Virtual machine instances Dynamically created VLANs ASN Substrate vBTS Substrate Base Station (BTS)

WINLAB ASN Packet Forwarding Removed all default IP routing, simplified ASN controller* All switching purely based on MAC addresses Implemented the VNTS shaping mechanism in click for slice isolation ASN Substrate vBTS Substrate Base Station (BTS) * Work done at NEC

WINLAB BTS The BTS itself is a black box Hence, the slice isolation mechanism and control framework is outside of this box ASN Substrate vBTS Substrate Base Station (BTS) Un-modified WiMAX BTS (Black box) Data And Control Pipes

WINLAB Baseline Measurement

WINLAB Coverage map of the WiMAX BaseStation Measured RSSI

WINLAB Demo Setup at GEC6 Goal: – Show the effectiveness of our shaping mechanism for providing isolation across slices Setup: – 2 Clients (1 per slice) – Stationary client in control room (CINR =31) Mobile Slice Stationary Slice Open WiMAX BTS Mobile Client Stationary Client

WINLAB Path For The Mobile UDP CBR traffic: 1024bytes, 10Mbps/Slice Mobile client moves as shown Measured RSSI along the mobile client’s path

WINLAB DL Throughput Vs Time – no shaping Observed UDP Throughput No isolation among clients without VNTS BTS is throughput fair – But, air-time fairness is voilated

WINLAB With VNTS Performance improves significantly – Good overall throughput performance – Improvement in isolation DL Throughput Vs Time – VNTS Good aggregate throughput Isolation improves

WINLAB Future Steps Tighter integration of the control framework Better algorithms to adaptively shape client traffic Similar control mechanism for UL slice traffic

WINLAB BTS Specification PHY Access modeSOFDMA/TDD Frequency2535 ~ 2605 MHz DL:UL ratio35:12, 26:21, 29:18 Channel BW10 MHz, 8.75 MHz FFT size1024, 512 Frame duration5ms TX output Power35dBm (max) # of sectors3 MAC Head compressionPHS ARQHARQ/CC, ARQ MBS supportSingle BS, multiple BS-MBS Resource management Power control, mode control (idle, sleep etc.) Networking IP protocolsIPv4, IPv6 Bridging/Routing Transparent L2 switch, Bridging Packet handling802.1Q VLAN, PHS**) rtPS real-time polling service ertPS enhanced real-time polling service nrtPS non real-time polling service UGS unsolicited grant service BE best effort Base Station Features Supported Service Classes

WINLAB VNTS Mechanism Baseline algorithm for evaluating the shaping rate at the BTS Modifications which account for retries are not included here – Work in progress

WINLAB Outdoor Measurements 2 3

WINLAB Performance comparison Fairness IndexCoupling Coefficient