wiki:WiMAXSiteDeployments

Version 65 (modified by agosain@bbn.com, 7 years ago) (diff)

--

Status of GENI WiMAX Site Deployments

References

Initial Deployment Plan

Extended Deployment Summary

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








Status Summary

===== ============ ======= ========= ================== ======= ======================= =========== ================ ================ ================ ============ ===================== ========== ============== =========== =============== ===== ============
Index Campus       PI/team GENI Proj Site Capabilities                                                                                                              Mobile stations       Experiments                                           Notes Last updated
----- ------------ ------- --------- ------------------------------------------------------------------------------------------------------------------------------ --------------------- ----------------------------------------------------- ----- ------------
#                                    WiMAX base station WiFi AP Control and data server Wimax RF AM Backbone connect Mobility service Central monitor  Remote login                        Local      Classroom      Remote      Multi-site   
===== ============ ======= ========= ================== ======= ======================= =========== ================ ================ ================ ============ ===================== ========== ============== =========== =============== ===== ============


0 Rutgers WINLAB Ivan Seskar
www.orbit-lab.org
2 NEC 2 Airspan yes yellow node 2.5.3 yes no yes yes laptops
handsets
vehicular
whatyes/no what/no what/no
1 NECLabs NA
2 Raytheon BBN Tech Manu Gosain 1 NEC 1 Airspan no yellow node 2.5.3 yes no yes no laptops
handsets
whatyes/no what/no what/no
3 Stanford NA
4 NYU Poly Thanassis Korakis
http://omfserver-witest.poly.edu/
1 NEC 1 Airspan yes yellow node 2.5.3 yes no yes yes laptops
handsets
whatyes/no what/no what/no
5 UMass Brian Lynn 1 NEC no HP ver no no no no laptops
vehicular
whatyes/no what/no what/no
6 Columbia who url wiki NEC Airspan yes/no HP yellow node ver yes/no no yes/no yes/no laptops handsets vehicularwhatyes/no what/no what/no
7 UColorado who url wiki NEC Airspan yes/no HP yellow node ver yes/no no yes/no yes/no laptops handsets vehicularwhatyes/no what/no what/no
8 UWisconsin Suman Banerjee 1 NEC 1 Airspan yes yellow node 2.5.3 yes no yes yes laptops
handsets
vehicular
whatyes/no what/no what/no
9 UCLA Giovanni Pau 1 NEC 1 Airspan no yellow node 2.5.3 yes no yes yes laptops
handsets
vehicular
whatyes/no what/no what/no
10 Clemson Kuang Ching Wang 3 Airspan no yellow node ver yes no no no laptops whatyes/no what/no what/no
11 Wayne State Hongwei Zhang 2 Airspan no yellow node ver no no no no laptops whatyes/no what/no what/no
12 UMichigan Morley Mao 1 Airspan no yellow node ver no no no no laptops whatyes/no what/no what/no
13 Temple who url wiki NEC Airspan yes/no HP yellow node ver yes/no no yes/no yes/no laptops handsets vehicularwhatyes/no what/no what/no
14 Drexel who url wiki NEC Airspan yes/no HP yellow node ver yes/no no yes/no yes/no laptops handsets vehicularwhatyes/no what/no what/no


Status of Each Site

Updates by Each Site

Each site will:

Update status as of GEC16, in section below
Summarize current status, in table above

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

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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)

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

6) Columbia University Site Update

Henning Schulzrinne, Jan Janak (Columbia)

GEC15 status: BR]]

  • No report

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

7) Univ of Colorado at Boulder Site Update

Dirk Grunwald (Colorado)

GEC15 status: BR]]

  • No report

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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)

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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)

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

10) Clemson University Site Deployment Plan

K-C Wang, Fan Yang (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)

GEC16 status:

  • Remain 1 up, 2 down
  • have been working continuously with Airspan to identify issue:
    • BS {#2} confirmed needing RMA for the second time - still waiting for clarification on return shipping handling/charge
    • BS {#3} debugged before without result, GPS unit taken to replace corroded one on BS {#1}, waiting for new GPS units to arrive and continue debugging with Airspan

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)

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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)

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

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:

  • No report

Dec 2012 status:

  • TBD

GEC16 status:

  • TDB

Attachments (1)

Download all attachments as: .zip