wiki:GEC15Agenda/WiMAXUpdate

Version 2 (modified by hmussman@bbn.com, 12 years ago) (diff)

--

  1. WiMAX Campus and Experiments Update at GEC-15
    1. Schedule
    2. Description
    3. Summary
    4. Agenda
    5. 1) Introductions
    6. 2) GENI WiMAX Deployment Tasks and Issues
      1. 2.1) Co-exist with Clearwire
      2. 2.2) Netspan Network Management System for Airspan Base Station
      3. 2.3) Updated/new WiMAX RF AggMgr
      4. 2.4) Add mobility/handover functions
      5. 2.5) Add "yellow nodes" to WiMAX Sites, as WiFi access points and …
      6. 2.6) Add OMF/OML to WiMAX sites
      7. 2.7) Connect WiMAX sites to I2 backbone network, to support …
      8. 2.8) Roaming Mobile Station using Android Handset
    7. 3) GENI WiMAX site deployment status and local experiment plans
      1. 3.1) BBN Site Extension Plan
      2. 3.2) WINLAB/Rutgers University Site Extension Plan
      3. 3.3) UCLA Site Extension Plans
      4. 4.4) Clemson University Site Deployment Plan
      5. 4.5) University of Wisconsin Site Extension Plan
      6. 4.6) University of Michigan Site Deployment Plan
      7. 4.7) Wayne State University Site Deployment Plan
      8. 4.8) Temple University Site Deployment Plan
      9. 4.9) Drexel University Site Deployment Plan
      10. 4.10) UMass Amherst Site Update
      11. 4.11) NYU Poly Site Update
      12. 4.12) Univ of Colorado at Boulder Site Update
      13. 4.13) Columbia University Site Update
    8. 5) Adjourn
    9. References
      1. R1 GENI WiMAX Strategy
        1. R1.1) Options for Introducing LTE Equipment
      2. R2) WiMAX Licenses
        1. R2.1) Co-exist with Clearwire
      3. R3) Airspan Profile-C Base Station, with Associated Hardware and Software
        1. R3.1) Airspan Installation Instructions
      4. R4) WiMAX Site Configuration
        1. R4.1) Updated WiMAX RF AggMgr for NEC Base Station
        2. R4.2) WiMAX RF AggMgr for Airspan Base Station
        3. R4.3) Adding OMF/OML Configuration
        4. R4.4) GIMI I&M Tool Set to Cover WiMAX Sites
        5. R4.5) Adding Login Service for Remote Users
        6. R4.6) Federating with ProtoGENI Cluster
        7. R4.7) Adding "Yellow Node" with WiFi Access Point, for Dual-homed …
        8. R4.8) Adding Mobility/Handover Functions
      5. R5) Connecting WiMAX Site to Backbone Network
      6. R6) Mobile Station Platforms
        1. R6.1) Fixed Mobile Station using "Yellow Node"
        2. R6.2) Roaming Mobile Station using Linux Netbook
        3. R6.3) Linux driver for Teltonika modem
        4. R6.4) Roaming Mobile Station using Android Handset
      7. R7) Types of Experiments
      8. R8) Spectrum Survey Experiment
      9. R9) Throughput Experiment Using iperf
      10. R10) Throughput Experiment Using Bit Torrent
      11. R11) Raw IP and UDP Traffic Generators
      12. R12) Using OMF and OML in Your Experiment
      13. R13) Remote Experiments
      14. R14) Multiple Site Experiment: Mobility First

WiMAX Campus and Experiments Update at GEC-15

Schedule

Wednesday, October 24, 3pm - 5pm
Room: TBD
Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies)

Description

This session will first review several WiMAX deployment tasks and issues.

Next, it will consider how to find and support GENI WiMAX experimenters.

Finally, it will review the status of WiMAX site deployments and extensions, plus plans for local experiments.

Summary

  • Deployment issues
    • Discussions with Clearwire about spectrum use
    • Introduce Airspan base stations, with Netspan ntwk mgmt system
    • Add “yellow nodes”, OMF/OML, connect to I2 backbone
    • Discussions with Sprint about unlocked handsets, MVNO data service
  • Experimenter support
    • Rutgers and NYU Poly have been supporting remote experimenters; soon: BBN
    • Recent tutorials at GEC13, TridentCom 2012, GEC14 and now GEC15
    • Starting at GEC14: small groups work on challenging experiments
  • Sol 3 site extensions with Airspan base stations:
    • Goal: on-the-air by end of Spiral 4
    • Drexel: base station ordered
    • UCLA, Wisconsin, Michigan, Wayne State, Temple: base stations arrived, installations pending
    • Clemson: one base station installed, some issues; two installations pending

slides

Agenda

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

3:00pm

2) GENI WiMAX Deployment Tasks and Issues

3:05pm

2.1) Co-exist with Clearwire

3:10pm
Harry Mussman (GPO) and Ray Raychaudhuri (WINLAB)

  • Review of current licensing and leasing arrangements
  • Proposed leases by Clearwire, some limited to 1 year, up to $4k to renew, with "indemnification"
    • Kevin Wanuga of Drexel reports: When Drexel general counsel was negotiating with Clearwire, Clearwire was willing to drop indemnification clause, and some other difficult language, before agreement was finalized and signed; Drexel also has an experimental license.
  • Status of discussions with Clearwire
    • Harry reports: waiting to organize another call with Paul McCarthy at Clearwire.
  • Status of discussions with the FCC
    • Harry reports: GENI operates using experimental license as FCC intended; waiting for contact to review GENI documents.
  • Possible approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:
    • Operate under an experimental license from the FCC
    • Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation
    • Responsive local contact, at each site
    • Centralized management DB at Rutgers WINLAB
    • Ability to quickly turn off site transmitter, if interference suspected

2.2) Netspan Network Management System for Airspan Base Station

Moderator: 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

2.3) Updated/new WiMAX RF AggMgr

3:20pm
Ivan Seskar (Rutgers WINLAB)

  • Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+; additional updates coming
  • Need to feed management data to centralized DB at WINLAB, for GENI-wide monitoring
    • Possible access to Clearwire, others.
  • Coming: New WiMAX RF AggMgr for Airspan base station
    • Plan first version by GEC15

2.4) Add mobility/handover functions

3:25pm
Parmesh Ramanathan (Wisconsin)

  • Projects requiring handover include: Clemson, Wayne State and Wisconsin.
  • Projects that can contribute handover technology include: Rutgers WINLAB and Wisconsin.
  • Also, commercial handover technology available from Airspan. (Gregg Tome (Airspan))
  • Parmesh reports: student has started on process to find a good solution, will report at GEC15

2.5) Add "yellow nodes" to WiMAX Sites, as WiFi access points and fixed "mobile stations"

3:35pm
Ivan Seskar (WINLAB)

  • These are "yellow nodes", introduced in ORBIT testbed
    • Can be used as: fixed nodes; WiFi access points; fixed "mobile stations"
    • Currently used by: Rutgers WINLAB; NYU Poly; BBN
  • How can these be provided to sites?
    • Approximate cost: $800 - $1500
    • Rutgers WINLAB has parts list, has been assembling
    • Need to poll sites for interest; then work up a plan.

2.6) Add OMF/OML to WiMAX sites

3:40pm
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.

2.7) Connect WiMAX sites to I2 backbone network, to support multi-site experiments

3:45pm
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?

2.8) Roaming Mobile Station using Android Handset

3:50pm
Harry Mussman (GPO)

  • Summary of discussions with Sprint about unlocked HTC Evo handset
    • Must be unlocked by Sprint, so can register with GENI network [BR]]
    • Perhaps: 500 handsets, purchased by Rutgers WINLAB, approx $500 per handset, and distributed to sites
    • Harry reports: waiting for 3-way NDA to be signed, so that we can resume discussions with Sprint
    • Need to poll sites for interest
  • Also possible: Sprint MVNO arrangement for pay-as-you-go data service
    • Harry reports: waiting for 3-way NDA to be signed, so that we can resume discussions with Sprint
    • Need to poll sites for interest
  • Comments from Matt Sanders (Georgia Tech), who attended the WiMAX meeting
    • Along with other jobs, he reports to the CTO, and is campus wireless services manager.
    • He has extensive experience negotiating with carriers (and I believe Sprint).
    • We talked for some time, and he agreed to advise us as we continue our discussions with Sprint.
  • His comments:
    • 1) Sprint has multiple approaches to dealing with “enterprise customers”. One approach we might consider, for 3G/4G service: “Access Point Node” (APN), where designated mobile stations (typically associated with an enterprise) are assigned certain IP addresses, so that their traffic can be routed directly to the enterprise. (This is likely to be in a different business unit that the MVNO approach)
    • 2) Matt has a contact at HTC. He feels that they might well be willing to make a batch of Evos for us. We would have to talk with them to understand the minimum quantity.

3) GENI WiMAX site deployment status and local experiment plans

3:55pm

deployment overview slides

3.1) BBN Site Extension Plan

3:55pm
Manu Gosain (GPO)

  • Status
    • Changing frequency, per request from Clearwrie
    • Bringup Airspan: installed; working
    • Add OMF/OML: in process: Install on VMs
  • Connect to I2 backbone network: working; used for tutoriala
  • Local experiments
    • Spectrum sensing
    • Throughput and range

slide

3.2) WINLAB/Rutgers University Site Extension Plan

4:00pm
Ivan Seskar (WINLAB)

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

3.3) UCLA Site Extension Plans

4:05pm
Mario Gerla, Giovanni Pau (UCLA)

  • 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
  • Airspan Installation
    • About 4 additional Weeks
    • 2 Weeks to Power
    • 2 Weeks for Installation
    • Delays may come if Facility des not bring Power.
  • Connection to Mesoscale Infrastructure
    • 3-4 weeks depending on the Facility management
    • Preliminary setup of the VLAN (backbone side) could start in about 1.5 weeks.

  • Experiments
    • Planning multiple-path network-coded tcp experiments with MIT
    • Once Connected to ION we will be able to run Nation Wide experiments.

4.4) Clemson University Site Deployment Plan

4:10pm
K-C Wang, Reece Johnson (Clemson) Clemson slides

  • 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)
  • Project Status
  • General Installation:
    • Server currently being installed with Windows Server 2008 R2
    • Awaiting CCIT to complete installation process
    • Additional machine ready to handle OMF/OML
    • Two VLANs created for client and management traffic
    • Tunnel established to Rutgers to enable temporary use of Netspan software
  • Clemson campus location:
    • Base station installed
    • Both VLANs run to base station
    • Initial configuration performed using Rutgers’ Netspan installation
    • Largely mirrored from Rutgers’ installation
    • 10 MHz channel centered at 2507.5 MHz
    • One transmitter is reporting low output power due to RF fault
    • Unable to detect a signal from the base station in line-of-sight
    • Obtaining spectrum analyzer to verify signal output
  • Project Status
    • Greenville location:
    • Mounting equipment, electrical, and fiber installation estimated by July 10th
    • One base station untested, one experiencing startup failure
  • Startup failure:
    • One base station does not properly boot up
    • Upon applying power, a single UDP packet is transmitted to 192.168.0.1:6666
    • This packet reveals a console session to an embedded Linux installation on the base station
    • No web interface is available for basic configuration
    • In communication with Airspan regarding repair
    • Hoping that another working base station can be used to reimage

Other observations

  • After configuration, base station needed to be reset after losing Netspan connection due to power failure

4.5) University of Wisconsin Site Extension Plan

4:20pm
Suman Banerjee, Derek Meyer (Wisconsin)

  • 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)
  • Airspan status
    • Purchased and received the Mean Well 450W power supply
    • Received missing mounting brackets for ODU
    • Tower analysis should have been completed by Friday
    • Unanswered questions: length of burial cat5e; distance to junction box
    • Recommendation: include surge protector in long cat5e cable!

4.6) University of Michigan Site Deployment Plan

4:25pm
Morley Mao (Michigan)

  • 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
  • Status slides from GEC13
    • Recent report: now mounting and painting antenna

4.7) Wayne State University Site Deployment Plan

4:30pm
Hongwei Zhang, Yu Chu (Wayne State)

  • 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

  • WiMAX network equipment

* Being in touch with facilities and campus IT on deployment logistics
* Received three WiMAX base stations and accessories on 06/25/2012
* Now working with facilities and campus IT on concrete action items
* Equipment purchase: mounting masts, networking, electricity; servers, laptops (+ USB dongles through UWM)
* Contracting roof-mount and installation

  • By end of Year 1

* Complete installation and measurement study of the WiMAX network
* Time to get OMF running?
* Connect the WiMAX network to GENI backbone via VLAN
* One source of uncertainty: re-roofing work on the deployment site until mid/late August
* Exploring mechanisms for deploying WiMAX network in parallel
* (No need to worry about re-roofing in the coming 20-30 years )

  • Year 2

* Incorporating OpenXC vehicular sensing and infotainment platform
* Enabling handoff between different base stations/sectors

4.8) Temple University Site Deployment Plan

4:40pm
Shan Lin, Jie Wu (Temple)

  • 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

4.9) Drexel University Site Deployment Plan

4:45pm
Kevin Wanuga, Jeff Wildman, Kapil Dandekar (Drexel)

  • 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

4.10) UMass Amherst Site Update

4:50pm
Mike Zink, Cong Wang (UMass Amherst)

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

4.11) NYU Poly Site Update

4:55pm
Thanasis Korakis, Fraida Fund (NYU-Poly)

  • Operational OMF/OML installation
    • Created OML-ized applications that may be useful to other sites (VLC, BitTorrent client, HTTP server and client)
    • More under development, e.g. OMF driver for Teltonika WiMAX devices
  • Connected to I2 backbone network
    • New wimaxrf
    • Multi-site capability demonstrated at demo night, tutorial
  • Extra capabilities and tools
    • Environmental sensors (temperature, humidity, light)

4.12) Univ of Colorado at Boulder Site Update

Dirk Grunwald (Colorado)

  • Status on 5/23:
    • On-the-air again, after replacing server;

  • Planned experiments
    • Being used for thesis research measruements

4.13) Columbia University Site Update

Henning Schulzrinne, Jan Janak (Columbia)

  • Status
    • On-the-air

  • Planned experiments
    • Exploring WiMAX service profiles

[ max 2 slides]

5) Adjourn

5:00pm

References

R1 GENI WiMAX Strategy

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?

R1.1) Options for Introducing LTE Equipment

Moderator: Harry Mussman (GPO)

Ray Raychaudhuri (WINLAB)

Ivan Seskar (WINLAB)

Patrick Gossman (Wayne State) The Case for LTE

Gregg Tome (Airspan)

R2) WiMAX Licenses

R2.1) Co-exist with Clearwire

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.

R3.1) Airspan Installation Instructions

link

R4) WiMAX Site Configuration

R4.1) Updated WiMAX RF AggMgr for NEC Base Station

R4.2) WiMAX RF AggMgr for Airspan Base Station

R4.3) Adding OMF/OML Configuration

R4.4) GIMI I&M Tool Set to Cover WiMAX Sites

R4.5) Adding Login Service for Remote Users

R4.6) Federating with ProtoGENI Cluster

R4.7) Adding "Yellow Node" with WiFi Access Point, for Dual-homed Experiments

R4.8) Adding Mobility/Handover Functions

Moderator: Parmesh Ramanathan (Wisconsin)

Projects requiring handover include: Clemson, Wayne State and Wisconsin.
Projects that can contribute handover technology include: Rutgers WINLAB and Wisconsin.
Also, commercial handover technology available from Airspan. (Gregg Tome (Airspan))
Process to find a good solution?

[ slides]

R5) Connecting WiMAX Site to Backbone Network

R6) Mobile Station Platforms

R6.1) Fixed Mobile Station using "Yellow Node"

R6.2) Roaming Mobile Station using Linux Netbook

R6.3) Linux driver for Teltonika modem

R6.4) Roaming Mobile Station using Android Handset

R7) Types of Experiments

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

R8) Spectrum Survey Experiment

R9) Throughput Experiment Using iperf

Manu Gosain (GPO) and Harry Mussman (GPO)

Overview of basic throughput experiment, using bidirectional iperf, both TCP and UDP

Basic throughput experiment using OMF/OML

The basic throughput experiments we have done utilize iperf, both TCP and UDP.

In iperf, the data is generated in the client, and flows to the server.
We put the client in the Mobile Station, and the server in the Base Station.
We used -d dualtest (bidirectional mode), where test is initiated at the client, data begins to flow to the server, and then a second data flow starts at the server; at the end of the test, results are available at the client.
Because of this, all tests can be initiated at the Mobile Station, and then results are available there.

iperf results in the TCP mode depend upon buffer sizes; overall delay; and lost packets.

Because of wireless propagation conditions, lost packets are common, and slight changes can significantly affect the measured throughput.
Thus, TCP results are highly variable; we took multiple measurements at each point, and identified the best and worst results.
It would certainly be good to have a better way to evaluate available channel bandwidth.
On the other hand, most apps use TCP and the variable results are typical of how these apps would see the channel.

iperf results in the UDP mode, counts % packets received, for a given (fixed) transmit rate.

If the rate is set below the available bandwidth, typically 100% of the packets are received.
If the rate is set above the available bandwidth, typically % of the packets are received typically equals available bandwidth divided by offered bandwidth, but there is no way to understand how many packets are actually lost.
An extended test that ramped up the offered bandwidth in multiple tests, could actually verify the available bandwidth; this could then be repeated to see real variations in available bandwidth.

References:

iperf tutorial slides
iperf tutorial web site

R10) Throughput Experiment Using Bit Torrent

Fraida Fund (NYU Poly)

slides

Overview of throughput experiment, using bit torrent.
Advantages

Reference
More information & source code
Use the NYU-Poly WiMAX testbed

R11) Raw IP and UDP Traffic Generators

Surat (Au) Teerapittayanon (MIT)

Overview of new raw IP and UDP traffic generators, to accurately gauge available channel bandwidth.
slides

R12) Using OMF and OML in Your Experiment

Christoph Dwertmann (NICTA)

slides

Basic throughput experiment using OMF/OML

OML'ified apps we know of include:

gpslogger
Iperf
omf_nmetrics
omf_trace
otg and otr
wlanconfig_oml
Yantt (Yet another network testing tool)
SNMP wrapper

Repository for OML'ified apps

List of available modules with OMF and OML for use in your experiment
Approach for adding OMF and OML interfaces to additional modules

R13) Remote Experiments

R14) Multiple Site Experiment: Mobility First

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.

Attachments (7)