Version 18 (modified by, 11 years ago) (diff)


WiMAX Developers Meeting at GEC-16


Tuesday, March 19, 3:30pm - 5pm
Room: TBD
Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies)




First, this session will review Spiral 5 goals for GENI WiMAX campus deployments and experiments.

Next, it will review the status of GENI WiMAX campus deployments and extensions, plus plans for local experiments.

Finally, review several WiMAX deployment tasks and issues.


This is a tentative agenda, which may change.

NOTE: We have many topics to cover in a short time. PLEASE bring only the designated number of slides, and provide a link to additional information. THANKS!

1) Introductions


2) Spiral 5 Goals

Harry Mussman (GPO)

a) Where necessary, complete deployments planned for Spiral 4:

Get experimental frequency from the FCC, that does not interfere with Clearwire services
Install Airspan base station(s), with local NetSpan management system
Optional when multiple cells: backhaul control and data traffic to central equipment site
Add OMF/OML structures, including LoginService
Connect via switch to I2 backbone, via OF switches if there
WiFi access point for dual-homing operating on custom PC node
Vehicular mobile station operating on custom PC node
Fixed “mobile station” for remote experimenters operating on custom PC node

b) Plan local research experiments for Spiral 5

Focus on goals, configurations, steps
Identify necessary extended site capabilities needed in Spiral 5

c) Complete deployments of necessary extended site capabilities needed in Spiral 5, from this list of options: (technology supplier or coordinator shown)

Additional base station (Rutgers WINLAB)
Custom PC nodes ("yellow nodes") (Rutgers WINLAB)
Login Service plus OMF/OML services operating on custom PC node (Rutgers WINLAB)
Connection to I2 (coordinated by BBN)
GIMI I&M services (UMass Amherst/NYU Poly)
Multiple base-station management service operating on custom PC node (Rutgers WINLAB)
Data-path gateway service operating on custom PC node (Rutgers WINLAB)
Mobility/handover/multi-homing service (coordinated by Wisconsin/Clemson)
WiFi access point for dual-homing operating on custom PC node (Rutgers WINLAB)
Vehicular mobile station operating on custom PC node (Rutgers WINLAB)
Fixed “mobile station” for remote experimenters operating on custom PC node (Rutgers WINLAB)
Unlocked Android WiMAX/WiFi handsets. (Wisconsin)

d) Support unified GENI operations:

Forward site monitoring information to the central monitoring server (Rutgers WINLAB)
Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services
When necessary, do an “emergency stop” of your transmissions.

e) Complete and support experiments:

Local research experiments
Experiments by remote experimenters, including those at tutorials
Classroom instruction experiments by students (NYU Poly)
Multi-site experiments, e.g., MobilityFirst (Rutgers WINLAB)

f) Concern: how can we get all of this done?

Common platforms and services
Clear plans, good schedules
Close cooperation!!

3) Engineering and Studies

3.1) Co-exist with Clearwire

Manu Gosain (GPO) and Ivan Seskar (WINLAB)

  • Current approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:
    • Operate under an experimental license from the FCC; otherwise require contract between site and Clearwire, with $ and conditions
    • Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation
    • Maintain accurate DB of site information and contacts at Rutgers, and share with Clearwire
    • Responsive local contact, at each site
    • Centralized monitoring server at Rutgers WINLAB
    • Ability to quickly turn off site transmitter, if interference suspected
    • Possible extension: remote emergency stop, with access to GMOC

What are next steps?

  • Review information on site information and site dashboard pages, and finalize
  • Establish process to add site information, then maintain and track
  • Establish email list for operations issues
  • Provide operations interface to GMOC and Clearwire
  • Complete agreement with Clearwire
  • Encourage all GENI sites to obtain experimental licenses
  • Include WiMAX into GENI emergency stop process
  • Consider adding a WiMAX "emergency stop" button, for use by the GMOC

3.2) Access to Sprint Broadband Services via MVNO Arrangements

Jim Martin (Clemson Univ)

  • Discussions with Sprint and their partner, Arterra
  • Considering approach as discussed in earlier WiNTeB workshop
  • Possible configuration

3.3) Options for Introducing LTE Equipment

Suman Banerjee

GEC14 discussion:

Moderator: Harry Mussman (GPO)
Ray Raychaudhuri (WINLAB)
Ivan Seskar (WINLAB)
Patrick Gossman (Wayne State) The Case for LTE
Gregg Tome (Airspan)

GEC15 discussion group formed:

Moderator: Suman Banerjee (Wisconsin)
Ray Raychaudhuri (WINLAB)
Ivan Seskar (WINLAB)
Patrick Gossman (Wayne State)
Bryan Lyles (NSF)
Jacobus (Kobus) Van der Merwe (Utah) (new)
Tod Sizer (Bell Labs/Alcatel-Lucent) (new)
Walt Magnusen (Texas A&M) (new)
Harry Mussman (GPO)

What are our goals?

How do we match available: base station equipment, on-air frequencies and mobile stations?

LTE frequency bands (from Ivan)

Gregg Tome: Airspan has equipment that operates at 2.6GHz (but this is outside of EBS band)

Tod Sizer: Have used commercial small cells operating at low power, borrowed commercial spectrum, and commercial devices, in a lab setting.

Ivan and Tod: There is available open-source back-end software (Fraunhoffer?)

Walt: Has equipment to test for LTE in public safety, from General Dynamics/IPWireless

What are next steps?

  • Tod to talk with Ray and Ivan
  • Suman to organize calls/meetings

4) Tasks


4.1) Repair and Install Airspan Profile-C Base Stations

Manu Gosain (GPO) and Ivan Seskar (WINLAB)

  • Airspan base stations successfully installed:
  • Airspan base stations with defects, and their current status:
    • Michigan: returned for repairs; received back; installed? status?
    • Clemson #1: ?
    • Clemson #2: ?
  • Next steps:

4.2) Build and Add Custom PC "Yellow Nodes" to WiMAX sites

Ivan Seskar (WINLAB)

  • These are "yellow nodes", introduced in ORBIT testbed
  • Can be used as:
    • General fixed servers
    • Support Multiple Base-Station Mgmt Srvc [[B
    • Support Data-Path GW Srvc
    • Support OMF/OML and Login services
    • Provide WiFi access points
    • Act as fixed "mobile stations"
    • Act as vehicular mobile station (option: 12v power supply)
  • Currently used by: Rutgers WINLAB; NYU Poly; BBN
  • How can these be provided to sites?
    • One design to serve all needs
    • Approximate cost: $800 - $1500
  • What are next steps?
    • Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites
    • Order parts (due 11/15/12)
    • Assemble and deliver to sites (due 1/15/13)
    • Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr?
  • Planned allocation:
    • High-speed nodes (fixed applications only):
  • Low-speed nodes: (fixed or mobile applications):

4.3) Write and Introduce New Services: Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc

Ivan Seskar (Rutgers WINLAB) and Davide Pesavento (UCLA)

  • Multiple Base-Station Mgmt Srvc:
  • 1) Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+; additional updates coming
    • Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring
    • Due: ?
  • 2) New WiMAX RF AggMgr for Airspan base station
    • Provides configuration, to replace Netspan; now running
    • Provides node authorization, and measurements per client
    • First version due: 12/15/12
    • Could BBN, NYU Poly begin testing early version, to replace Netspan?
    • Could early version be shipped to sites on yellow node, with OMF/OML?
  • 3) Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API
    • Should be useful for handover/multi-homing functions: shared white list of MS, allowed to connect to one BS or another
    • What other features are needed?
    • First version due: 3/15/13
  • Data-path GW Srvc:
    • Bridges each base station to global datapath
    • Includes CLICK router (two types)
    • Includes OpenV switch (open-source OF)
    • Should be useful for handover/multi-homing functions
    • First version due: 3/15/13
    • Could there be an earlier version, that provides basic functions, and be manually configured?
    • Could BBN, NYU Poly begin testing early version?
    • Could early version be shipped to sites on yellow node?

What are next steps?

  • Finalize features for WiMAX RF AggMgr releases (due 11/15/12)
  • Establish delivery schedule for WiMAX RF AggMgr releases
  • Could there be an earlier version fo WiMAX RF AggMgr, that provides just basic functions, and be manually configured? released by 11/15/12?
  • Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases
  • Finalize features for Data-path GW Srvc releases (due 11/15/12)
  • Establish delivery schedule for Data-path GW Srvc releases
  • Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases

4.4) Support Central Monitoring by Rutgers WINLAB

4:25pm Manu Gosain (GPO), Ivan Seskar (WINLAB)

4.5) Write and Introduce Mobility/Handover/Multi-homing Services

Parmesh Ramanathan (Wisconsin)

  • Projects requiring handover include: Clemson, Wayne State, Wisconsin and UCLA.
  • Projects that can contribute handover technology include: Rutgers WINLAB and Wisconsin.
  • Also, commercial handover technology available from Airspan. (Gregg Tome (Airspan))
  • Layer 2 handoff
    • Minimal: Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS
    • Better: Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2
    • Need: suggested configurations, estimates of required software and level of effort
  • Layer 3 handoff
    • Minimal: Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection
    • Better: Use open source mobile IP s/w (Transparent Mobile IP link, and OpenFlow s/w in mobile node to de-encapsulate IP packets
    • Need: suggested configurations, estimates of required software and level of effort
  • Suggested steps:
    1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet
    2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme
    3) Support new Layer 3 solutions like Mobility First?
    4) Demonstrate heterogeneous network handovers

What are next steps?

  • Better define proposed configurations 1) and 2) (due 11/15/12)
  • Review with other interested projects
  • Understand proposed Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc, and how they could be used in the implementation
  • Understand how Yellow Nodes could be used in the implementation
  • Understand how Android handsets could be used in the implementation
  • Consider potential uses of WiScape Measurement Framework
  • With other projects, define a workplan (due 12/15/12)

4.6) Consider WiScape Measurement Framework

Suman Banerjee (Univ Wisc)

  • Overview of current functions
    • slides
    • A data measurement framework with APIs, that the clients and the measurement server expose
    • Clients (e.g., on an Android device) measure network performance, and then report measurements to the server
    • Measurement include latency, loss, throughput, TCP or UDP
    • Provides feedback to network selection
    • link to WiScape

What are next steps?

  • Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution

4.7) Add WiFi AP to Support Multi-Homing

Manu Gosain (GPO), Ivan Seskar (WINLAB)

4.8) Acquire and Add Android Handsets

Derek Meyer (Univ Wisconsin)

  • Summary of discussions with Sprint about unlocked HTC Evo handset
    • 3-way NDA was signed
    • Sprint has subcontractor who handles such purchases: contact is ?
    • Many handsets in warehouse, such as HTC Evo 4G; approx $300 per handset
    • Must be unlocked by subcontractor, so can register with GENI network; need to provide config to subcontractor (done by Ivan)
    • Must be sure can download Android apps

What are next steps?

  • Working with other projects, establish how many handsets are needed at which sites
  • Consider how to provide handsets to projects no longer supported by the GPO
  • Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices (due 12/1/12)
  • Get and check samples?
  • Verify operation, and loading of apps
  • Deliver handsets to other projects (due 1/15/13)
  • Support use by other projects
  • Maintain relationship with WSA Distributing

4.9) Add Vehicular Mobile Stations Based on Yellow Node


4.10) Integrate and Introduce GIMI tools

Fraida Fund (NYU Poly)

4.11) Add OMF/OML to WiMAX sites, and Make WiMAX Sites Accessible to Experimenters

Fraida Fund (NYU Poly), Manu Gosain (GPO), Derek Meyer (Wisconsin),

  • Equip a WiMAX site with full OMF/OML capabilities, installing on VMs
  • Include Login Service for Remote Users
  • NYU Poly configuration:
  • 1) physical host acting as base station controller, runs the asn-gw and wimaxrf AM.
    • (1) and (2) run Ubuntu, (3) runs Windows.
    • It has Ethernet connections to the NEC IDU, NYU-Poly network (and Internet), and very soon GENI backbone (campus IS just informed me that they will be testing that tomorrow).
    • We have firewall rules set up so this host only accepts traffic from host (2) on the wimaxrf AM port. This allows us to make sure that only users with a current reservation can configure the BS.
  • 2) physical host running OMF 5.3 AM, EC, and some other services that are useful for the testbed.
    • (1) and (2) run Ubuntu, (3) runs Windows.
    • It has Ethernet connections to NYU-Poly network (internet) and OMF control network.
    • This is the host that testbed users log on to. We have firewall rules set up on this host so that only users with a current reservation can configure the BS or communicate with the testbed nodes.
  • 3) physical host that serves our group website and the reservation system for the testbed. It's connected to the NYU-Poly network (and Internet)
    • (1) and (2) run Ubuntu, (3) runs Windows.
  • Our testbed nodes are scattered throughout several CS labs and research areas (not part of our group).
    • They are connected to the pre-existing Ethernet jacks in the walls and floors of those rooms, which all go back to a CS server room, where we patch them through to our own (non-openflow) switch for the control network.
    • We do have an openflow switch that we plan to deploy somewhere at some point.
  • BBN experience (need summary)
  • All services are running on the same physical machine.
    • HP server that came with the base station.
    • The base OS is Debian and virtual machines using for the services (Virtualbox)
  • Physical machine network connections:
    • Eth0 ( University network (internet)
    • Eth1 ( Network to IDU of base station
    • Eth2 ( Control network for omf
    • Eth3: Connected to openflow (physically, but not enabled until we can get a vlan tag to GENI backbone)
  • Base operating system: Debian
  • Virtualbox guests:
    • 1. Ubuntu 9.04 -> aggmgr 5.2 -> wimaxrf service
    • Eth0 ( bridged interface to university network
    • Eth1( bridged interface to base station network
  • 2. Ubuntu 10.04 -> aggmgr 5.3 -> cmcStub, Frisbee, inventory, pxe, result, saveimage
  • Also expctl, resctl, and xmpp on same machine
  • Eth0 ( bridged interface to university network
  • Eth1 ( bridged interface to control network
  • Coming: plan to federate with ProtoGENI cluster
    • Reference: TridentCom 2012 : "Federating wired and wireless test facilities through Emulab and OMF: the iLab.t use case", Stefan Bouckaert (IBBT - Ghent University)
    • BBN is exploring how to utilize this to better integrate WiMAX sites into GENI, and be able to utilize the GENI AM API to assgin resources.

4.12) Connect WiMAX Sites to Persistent I2 Backbone Network, with IP Routing, to Support Multi-site Experiments

Manu Gosain (GPO), Fraida Fund (NYU Poly), Ivan Seskar (WINLAB)

  • Connect a WiMAX site to the GENI I2 backbone network
    • Update WiMAX RF Agg Mgr to map MS groups into VLAN tags
    • Add switch
    • Connect switch to I2 backbone
    • VLAN connections from each site to "L2 router" at WINLAB


  • When can other WiMAX sites can be added?
    • UCLA; has physical connection; needs to configure; when?
    • Wisconsin; when?
    • Clemson; when?
    • UMass Amherst; has physical connection; needs to configure; when?
  • How is core network configured to support multi-site experiments?
  • How is new Data-path GW Srvc use at site to interface with core network?

What are next steps? (Manu Gosain)

  • Establish planned configuration (due 11/15/12)
  • Establish plan with schedule to connect all sites (due 11/15/12)
  • Track connection of sites, and assist them as needed

5) Status of GENI WiMAX site deployments

Manu Gosain (GPO) and members of site teams

Go to Status of GENI WiMAX site deployments

6) GENI WiMAX Experiments, Demos and Tutorials

6.1) Lab Experiments to Teach Wireless Basics

Thanasis Korakis (NYU Poly)

Funded project (1/13 - 12/13) to define lab experiments for students to teach wireless basics
To be executed on GENI wireless sites, using both WiMAX and WiFi
Overview and status slides

What are next steps?

  • Early versions of lab experiments to be provided by GEC16

6.2) Multiple Site Experiment: Mobility First

Kiran Nagaraja (WINLAB)

GEC14 presentation:


Overview of current Mobility First multiple-site experiment.

What additions are needed?
1) Add WiFi AP to each site.
2) L2 path from MS to core

Experiment done without human intervention, by using x2 MAC addresses, and emulating packet loss to fake mobility.
Consider these as possible sites by GEC13: WINLAB; BBN; NYU Poly; UCLA; Colorado.

6.3) WiMAX Tutorials at GEC16

5:00pm Fraida Fund (NYU Poly)

7) Adjourn


WiMAX BoF Dinner

Please join us for a WiMAX BoF dinner on Wednesday evening. Please indicate on this poll, if you will be attending.


R1) Airspan Profile-C Base Station, with Associated Hardware and Software

Ivan Seskar (WINLAB) and Harry Mussman (GPO)

a) Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites
NEC is not able to provide a WiMAX base station for new GENI WiMAX sites
WINLAB and the GPO have decided to purchase base stations from Airspan, a commercial company pursuing target customers such as universities and small carriers.
For example, the Univ of Colorado at Boulder IT Dept has installed an Airspan system with 4 sectors, that covers the campus. They have been pleased with Airspan.
WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items.

Airspan brochure
MacroMAXe Product Specification
Airspan Deployment Plan for Univ Colorado at Boulder

b) Rutgers will provide a kit including:
Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting

Choice of frequency:
(2510 Lo: 2496MHz to 2570MHz)
(2510 Mid: 2560MHz to 2630MHz)
(2510 Hi: 2620MHz to 2690MHz)
(3650: 3650MHz to 3700MHz)]

NOTE: WINLAB needs to know frequency choices during November (or early December), so that they can place an order with Airspan for delivery late 2011 or early 2012!

Sector antenna, with x4 RF jumper cables
2x4 MIMO, supported by base station and antenna
GPS antenna, with surge suppressor and cable
DC power cable, from base station unit (outside) to testbed (inside)
Network management software license, 1 per base station

c) Campus will need to provide:
Pole for mounting
DC power supply (-48v, approx 300W)
Ethernet cable, from base station unit (outside) to testbed (inside); consider copper (may be a problem with lightning surge) or fiber (requires MM fiber cable, and fiber interface on switch)
Windows server to host network management software
Linux server to host OMF software
Ethernet switches, and other network equipment, for access (configuration to be provided)

d) Additional kits can be purchased from Airspan

Price is approximately $15,000.

e) It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5.

Thus, campus site might be able to add additional sectors, at no cost.
Planning for next year will be done later this year.
Consider including additional sectors within your technical plan right away.

f) Note: Airspan indicates that they expect to introduce a new base station unit within the next year.

Somewhat reduced performance/range.
Approximately half the cost

g) Airspan indicates that their sector antenna provides:

A 90degree pattern, which is consistent with proper coverage over a 120degree sector.
Four internal elements, to support 2x4 MIMO.
Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.

h) Airspan shows that their profile-C base station unit can be configured to operate without an ASN GW and without a RADIUS (authentication) server.

In this mode, a list of allowed base stations must be configured into the base station, and groups of these base stations are mapped to a VLAN on the ethernet port.
This appears to be consistent with the current NEC base station unit operated with the ASN GW/WiMAX RF AggMgr code that has been provided by Rutgers/WINLAB
MacroMAXe Configuration Guide

i) Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.

In this case, the base station unit operates with IP at the interface.

j) Airspan installation instructions link

R2) Netspan Network Management System for Airspan Base Station

Manu Gosain (GPO)

  • Suggest: add Netspan system at each site with Airspan base station
  • Requires: Windows server
  • Use: setup of Netspan base station to provide basic functions


installation instructions

  • Coming: replace with new WiMAX RF AggMgr

Attachments (5)