wiki:Dec2012WiMAXstatus

Version 6 (modified by hmussman@bbn.com, 7 years ago) (diff)

--

  1. WiMAX D&P Status and Campus Deployments Status during December 2012
    1. Schedule of Calls
    2. Agenda
    3. 1) Spiral 5 Goals
    4. 2) Forward-looking Studies
      1. 2.1) Options for Introducing LTE Equipment
      2. 2.2) Access to Sprint Broadband Services via MVNO Arrangements
      3. 2.3) Integration of WiMAX wireless sites with ProtoGENI aggregates
    5. 3) GENI WiMAX Deployment Tasks and Issues
      1. 3.1) Co-exist with Clearwire
      2. 3.2) Add "yellow nodes" to WiMAX Sites
      3. 3.3) Mobile Station using Android Handset
      4. 3.4) New: Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc
      5. 3.5) New: GIMI I&M Services
      6. 3.6) New: Mobility/handover/multi-homing services
    6. 4) GENI WiMAX site deployment status and local experiment plans
      1. 4.1) WINLAB/Rutgers University Site Extension Plan
      2. 4.2) BBN Site Extension Plan
      3. 4.4) NYU Poly Site Update
      4. 4.5) UMass Amherst Site Update
      5. 4.6) Columbia University Site Update
      6. 4.7) Univ of Colorado at Boulder Site Update
      7. 4.8) University of Wisconsin Site Extension Plan
      8. 4.9) UCLA Site Extension Plans
      9. 4.10) Clemson University Site Deployment Plan
      10. 4.11) Wayne State University Site Deployment Plan
      11. 4.12) University of Michigan Site Deployment Plan
      12. 4.13) Temple University Site Deployment Plan
      13. 4.14) Drexel University Site Deployment Plan
    7. 5) GENI WiMAX Experiments, Demos and Tutorials
      1. 5.1) Lab Experiments to Teach Wireless Basics
      2. 5.2) Multiple Site Experiment: Mobility First
    8. References
      1. R1 GENI WiMAX Spiral 4 Goals
      2. R2) Overview of GENI WiMAX Sites and Experiments
      3. R3) Airspan Profile-C Base Station, with Associated Hardware and Software
      4. R4) Netspan Network Management System for Airspan Base Station
      5. R5) Add OMF/OML to WiMAX sites
      6. R6) Connect WiMAX sites to I2 backbone network, to support multi-site …

WiMAX D&P Status and Campus Deployments Status during December 2012

Schedule of Calls

Agenda

These calls will review:

Spiral 5 goals for GENI WiMAX campus deployments and experiments.
Status of GENI WiMAX D&P tasks.
Status of GENI WiMAX campus deployments and extensions, plus plans for local experiments.

1) 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!!

2) Forward-looking Studies

2.1) Options for Introducing LTE Equipment

GEC14 discussion:

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

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

2.2) Access to Sprint Broadband Services via MVNO Arrangements

2.3) Integration of WiMAX wireless sites with ProtoGENI aggregates

3) GENI WiMAX Deployment Tasks and Issues

4:00pm

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
    • Maintain email list for operations issues
    • 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
  • 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) Add "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
    • 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
  • Fixed node
    • I7 processor
    • AC power supply, approx 400W
    • Approximate cost: $800 - $1500
  • Mobile node
    • I5 processor
    • DC power supply, approx 200W
    • Can also be used as fixed node with AC power
    • 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?

3.3) Mobile Station using Android Handset

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

3.4) New: 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

3.5) New: GIMI I&M Services

Mike Zink, Cong Wang (UMass Amherst)
Thanasis Korakis, Fraid Fund (NYU Poly)

  • Integrate available (rel beta2) GIMI I&M tools with WiMAX sites
  • Train campus sites on use of GIMI I&M tools
  • Demonstrate GIMI I&M tools for WiMAX experiments at GEC16

3.6) New: Mobility/handover/multi-homing services

Parmesh Ramanathan (Wisconsin) and KC Wang (Clemson)

  • 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) GENI WiMAX site deployment status and local experiment plans

Each site will indicate:

Support for unified GENI operations:
Status of deployments planned for Spiral 4 and Spiral 5:
Plan for local research experiments in Spiral 5:
Support for experiments:

4.1) WINLAB/Rutgers University Site Extension Plan

Ivan Seskar (WINLAB)

GEC14 status:

  • Status
    • Bringing Airspan on Busch campus
    • Continuing remote access to BSs
    • Connected to I2 backbone network
  • Local and remote experiments

GEC15 status:

  • WINLAB site:
    1) NEC base station, with fixed mobile station
    2) Sandbox: NEC base station, connected via programmable RF attenuator to fixed mobile station
  • Busch campus site:
    3) Airspan base station, for use by students on campus

a) Status of deployments planned for Spiral 4:

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

b) Plan for local research experiments in Spiral 5:

What is new?

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

Additional base station (Rutgers WINLAB)
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)
Unlocked Android WiMAX/WiFi handsets. (Wisconsin)

d) Support for 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) Support for 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)

4.2) BBN Site Extension Plan

Manu Gosain (GPO)

GEC14 status:

slide

GEC15 status:
a) Status of deployments planned for Spiral 4:

Get experimental frequency from the FCC, that does not interfere with Clearwire services (yes, new frequency)
Install Airspan base station(s), with local NetSpan management system (yes)
Add OMF/OML structures, including LoginService (yes)
Connect via switch to I2 backbone, via OF switches if there (yes)
WiFi access point for dual-homing operating on custom PC node (partial)
Fixed “mobile station” for remote experimenters operating on custom PC node (yes)

b) Plan for local research experiments in Spiral 5:

Repeat throughput and range, comparing NEC and Airspan

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

Custom PC nodes ("yellow nodes") (Rutgers WINLAB)
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)
Unlocked Android WiMAX/WiFi handsets. (Wisconsin)

d) Support for 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) Support for 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)

4.4) NYU Poly Site Update

Thanasis Korakis, Fraida Fund (NYU-Poly)

GEC14 status:

  • Operational OMF/OML installation
  • Connected to I2 backbone network
  • Testbed open to experimenters since GEC12

GEC15 status:

  • Airspan base station isntallation still pending.
  • Working closely with UMass Amherst on use of GIMI tools with WiMAX
  • Supporting experimenters, including students and tutorials

a) Status of deployments planned for Spiral 4:

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

b) Plan for local research experiments in Spiral 5:

Many experiments formulated for students, and tutorials, including:

StreamLoad
NetCheck
AFFIX

Working on set of lab experiments to teach wireless principals

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

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)
Vehicular mobile station operating on custom PC node (Rutgers WINLAB)
Unlocked Android WiMAX/WiFi handsets. (Wisconsin)

d) Support for 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) Support for 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)

What are next steps?

  • Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)

4.5) UMass Amherst Site Update

Mike Zink, Cong Wang (UMass Amherst)

GEC14 status:

  • Add OMF/OML: have installed
  • Connect to I2 backbone network: plan to do soon
  • Planned experiments: use to integrate GIMI tools

GEC15 status: BR]]

No report

4.6) Columbia University Site Update

Henning Schulzrinne, Jan Janak (Columbia)

GEC15 status: BR]]

  • No report

4.7) Univ of Colorado at Boulder Site Update

Dirk Grunwald (Colorado)

GEC15 status: BR]]

  • No report

4.8) University of Wisconsin Site Extension Plan

Suman Banerjee, Derek Meyer (Wisconsin)

GEC14 status:

  • Extension plan
    • Add Airspan to building/tower near Capitol.
    • Connect via Madison unified fiber project
    • Outside contributions for power and poles.
    • x1 (2510 Mid: 2560MHz to 2630MHz)

GEC15 status:

  • Airspan status
    • Planned installation blocked by site issues
    • Instead, will move quickly to install on CS building (where Cisco base station was installed)

a) Status of deployments planned for Spiral 4:

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

b) Plan for local research experiments in Spiral 5:

Focus on mobility experiments from bus
Planning multi-site video experiment with NYU Poly
Begin classroom use in Spring 2013

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

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) (or use local service?)
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 for 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) Support for 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)

What are next steps?

  • Establish a plan for all of your Spiral 5 tasks, and document (due 12/1/12)
  • Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)
  • Complete connection to I2 backbone, and demonstrate a service with another site(s) (due 1/15/12)

4.9) UCLA Site Extension Plans

Giovanni Pau, Mario Gerla (UCLA)

GEC14 status:

  • Extension plan
    • Add x1 Airspan BS near UCLA dormitories; possibly other BSs.
    • x1 (2510 Mid: 2560MHz to 2630MHz)
  • License
    • Renewed Experimental License
    • Coordination with Clearwire Started

GEC15 status:

  • Airspan Installation
    • Location selected: top of Spraul Hall; pole installed
    • On hold for poweer, network connections
    • Temporary: in use in lab for WiMAX RF AggMgr software testing
  • Connection to Mesoscale Infrastructure
    • Completed

a) Status of deployments planned for Spiral 4:

Get experimental frequency from the FCC, that does not interfere with Clearwire services (yes)
Install Airspan base station(s), with local NetSpan management system (pending, partial)
Optional when multiple cells: backhaul control and data traffic to central equipment site (pending)
Add OMF/OML structures, including LoginService (yes)
Connect via switch to I2 backbone, via OF switches if there (yes)
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 (yes)

b) Plan for local research experiments in Spiral 5:

Coverage and performance, with Teltonica and NEC, also Airspan
Mobile experiments with permanent vehicular nodes
NDN experiments over WiMAX

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

Custom PC nodes ("yellow nodes") (Rutgers WINLAB)
Login Service plus OMF/OML services operating on custom PC node (Rutgers WINLAB)
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 for 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) Support for 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)

What are next steps?

  • Establish a plan for all of your Spiral 5 tasks, and document (due 12/1/12)
  • Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)
  • Complete connection to I2 backbone, and demonstrate a service with another site(s) (due 1/15/12)

4.10) Clemson University Site Deployment Plan

K-C Wang, Reece Johnson (Clemson)

GEC13 plans:
Clemson slides

GEC14 status:

  • Extension plan
    • Add x1 Airspan BS near campus
    • Add x2 Airspan BS near Greenville; connect via DOT fibers.
    • Want handover near I85/I385 intersection.
    • x3 (2510 Lo: 2496 to 2570 MHz)

GEC15 status:

  • Clemson campus location:
    • Installed, on-the-air: signal strength measurements completed
  • Greenville locations:
    • Installed, with power and fiber connections
    • Both report "RF failure"; Netspan and/or base station issue

a) Status of deployments planned for Spiral 4:

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

b) Plan for local research experiments in Spiral 5:

Working with Wisconsin handover project
Focus on "uniform solution for handover in heterogeneous networks, e.g., WiFi off-loading

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

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 for 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) Support for 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)

What are next steps?

  • Establish a plan for all of your Spiral 5 tasks, and document (due 12/1/12)
  • Complete installation of Airspan base stations, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)
  • Complete connection to I2 backbone, and demonstrate a service with another site(s) (due 1/15/12)

4.11) Wayne State University Site Deployment Plan

Hongwei Zhang, Yu Chu (Wayne State)

GEC14 status:

  • Extension plan
    • Plan: one site with three sectors, and 3 Airspan base stations.
    • One frequency (10MHz) from Clearwire
    • x3 (2510 Mid: 2560MHz to 2630MHz)
  • Spectrum loan from Clearwire: done

* 10MHz band: 2591MHz – 2601MHz (belongs to 2510 Mid band of 2560MHz~2630MHz)
* Current loan valid until March 1, 2013; to be renewed annually afterwards
GEC15 status:

  • Airspan base stations:

* 2 installed on 17th floor, and on the air; CINR measured

a) Status of deployments planned for Spiral 4:

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

b) Plan for local research experiments in Spiral 5:

Enable handoff between different base stations/sectors
Develop measurement services
Measurement campaign: spatiotemporal behavior in static & mobile scenarios: smart grid and smart transportation

ns-3 integration
GENI-fy OpenXC vehicular sensing and infotainment platform
Refine OpenXC, virtualization, etc
Integrate with OMF, measurement tools
Integrate with v2V & V2I platforms (i.e., SDR) as well as vehicle sensing and control apps

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

Additional base station (pending) (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)
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 for 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) Support for 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)

What are next steps?

  • Establish a plan for all of your Spiral 5 tasks, and document (due 12/1/12)
  • Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)
  • Complete connection to I2 backbone, and demonstrate a service with another site(s) (due 1/15/12)

4.12) University of Michigan Site Deployment Plan

Morley Mao (Michigan)

GEC13 plans:

GEC14 status:

  • Extension plan
    • Add one Airspan on top of building
    • Will signals penetrate into buildings?
    • One frequency from Clearwire
    • x1 (2510 Lo: 2496 to 2570 MHz)
    • Location and backhaul
    • Mobility and handover

GEC15 status:

  • Base station installed, local Netspan ready, but waiting for power
  • I2 connection pending

a) Status of deployments planned for Spiral 4:

Get experimental frequency from the FCC, that does not interfere with Clearwire services (yes)
Install Airspan base station(s), with local NetSpan management system (pending)
Add OMF/OML structures, including LoginService (no)
Connect via switch to I2 backbone, via OF switches if there (pending)
WiFi access point for dual-homing operating on custom PC node (no)
Fixed “mobile station” for remote experimenters operating on custom PC node (no)

b) Plan for local research experiments in Spiral 5:

Content delivery service

c) Plan to complete deployments of extended site capabilities needed in Spiral 5:

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)
Fixed “mobile station” for remote experimenters operating on custom PC node (Rutgers WINLAB)
Unlocked Android WiMAX/WiFi handsets. (Wisconsin)

d) Support for 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) Support for 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)

What are next steps?

  • Establish a plan for all of your Spiral 5 tasks, and document (due 12/1/12)
  • Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput (due 12/15/12)
  • Complete connection to I2 backbone, and demonstrate a service with another site(s) (due 1/15/12)

4.13) Temple University Site Deployment Plan

Shan Lin, Jie Wu (Temple)

GEC14 status:

  • Extension plan
    • x1 (or x2?) Airspan base stations (2510 Mid: 2560MHz to 2630MHz)
    • Two frequencies from Clearwire, shared with Drexel
    • Location and backhaul
    • Mobility and handover
  • License application approved by Clear
    • License is valid until Jan 31, 2013
    • Frequencies: 2585-2595 & 2603-2613 MHz
    • Clearwire holds the right to terminate operation with 30 days prior notice
  • Wimax base station purchased and arrived
    • One Air4G-MacroMAXe 2510M Air4G-W24-2510MT
    • Installation contract placed
    • Latitude & Longitude: (39.98038, -75.15703)
    • Height: 12th floor (131 ft)
  • Experiments (with the existing TU-WiMax)
    • Observe highly irregular ranges (longest range>2.29mile)
    • High bandwidth (>700kbps) only very close to the base station (<0.5mile)
    • Significant shadowing among buildings

GEC15 status: BR]]

  • No report

4.14) Drexel University Site Deployment Plan

Kevin Wanuga, Jeff Wildman, Kapil Dandekar (Drexel)

GEC13 plans:

GEC14 status:

  • Extension plan
    • x1 (or x2?) Airspan base stations (2510 Mid: 2560MHz to 2630MHz)
    • Two frequencies from Clearwire, shared with Temple
    • Location and backhaul
    • Mobility and handover
  • Kevin Wanuga reports:
    • Planning for top of 18-story building; 3m radiation safety clearance
    • More urban than Temple
    • Airspan order placed; not yet received
    • Kiva networks to install base station
    • Contract engineer mast; recommendation from Giovanni: check masts at GNE supply
    • Questions about power cable; recommendation from Harry: call us, and we can explain parameters

GEC15 status: BR]]

  • No report

5) GENI WiMAX Experiments, Demos and Tutorials

link

5.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

5.2) Multiple Site Experiment: Mobility First

GEC14 presentation:
Kiran Nagaraja (WINLAB)

slides

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.

References

R1 GENI WiMAX Spiral 4 Goals

Harry Mussman (GPO)

a) Goals for GENI WiMAX site deployments:

Satisfy needs of local research experiments
Support multi-site experiments, e.g., MobilityFirst
Support remote experimenters

Support multi-site applications?

Are we missing something? support for instruction?

b) Sol 2 base station deployments:

Update to include OMF/OML structures, including LoginService
Add GENI AM API

Complete, and update to new software that support multiple VLANs, etc.
Connect via switch to I2 backbone, via OF switches if there

Consider how to setup multi-site slice, and include other GENI resources
Consider federated operation
Consider adding WiFi AP to support dual-homed experiments, e.g., MobilityFirst

c) Sol 3 base station deployments:

Consider 3.6GHz operation?
Study commercial campus deployments, to understand coverage and applications: U Colorado, Boulder; Northern Mich U; UMass Dartmouth
Order Airspan base stations and related items, for delivery 1/2012
Complete installation within Spiral 4! (within 1 year)

Decide on how to provide ASN-GW for handover
Consider open-source ASN-GW? or ASN-GW from Airspan?
How could we use Wisconsin mobility engine?

Airspan Deployment Plan for Univ Colorado at Boulder

d) Mobile stations:

Reference MS is Linux netbook, with Intel WIMAX modem card, internal or external
Reference vehicular MS?
Reference handset MS? Need to be able to unlock Sprint-supported device?

e) Experiment support:

Move to OMF/OML, for better support and for easier sharing
Consider alternate techniques for throughput measurements
Consider how to setup multi-site slice, and include other GENI resources

GIMI project committed to supporting WiMAX sites

How can we make it easy for experimenters?

f) Other topics:

Interworking with carriers (Clemson)
Use of carrier resources, i.e., WiNTeB
How could we add LTE? any match of equipment, frequencies and mobile stations?

g) CONCERN:

Do not have resources to do all of the above! how do we decide?
What is the best way to support campus projects?
What is the best way to support experimenters?

R2) Overview of GENI WiMAX Sites and Experiments

Harry Mussman (GPO)

Paper including sections on basic and extended WiMAX sites, and on WiMAX research and service experiments: pdf

R3) 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

R4) 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

slides

installation instructions

  • Coming: replace with new WiMAX RF AggMgr

R5) Add OMF/OML to WiMAX sites

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 (128.105.22.xxx): University network (internet)
    • Eth1 (10.3.8.126): Network to IDU of base station
    • Eth2 (10.0.0.1): 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 (128.105.22.xxx): bridged interface to university network
    • Eth1(10.3.8.254): 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 (128.105.22.xxx): bridged interface to university network
  • Eth1 (10.0.0.200): 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.

R6) Connect WiMAX sites to I2 backbone network, 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

slide

  • 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

Attachments (1)

Download all attachments as: .zip