Changes between Version 1 and Version 2 of GEC18Agenda/WiMAXDevelopers


Ignore:
Timestamp:
09/17/13 10:59:40 (8 years ago)
Author:
agosain@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC18Agenda/WiMAXDevelopers

    v1 v2  
    2323
    2424== Agenda / Details ==
     25
     26This is a tentative agenda, which may change.
     27
     28NOTE: 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!
     29
     30== 1)  Introductions ==
     318:30am  [[BR]]
     325min [[BR]]
     33
     34== 2)  Spiral 5 Goals ==
     358:35am  [[BR]]
     360min  [[BR]]
     37
     38a)  Where necessary, complete deployments planned for Spiral 4:  [[BR]]
     39 Get experimental frequency from the FCC, that does not interfere with Clearwire services  [[BR]]
     40 Install Airspan base station(s), with local NetSpan management system  [[BR]]
     41 Optional when multiple cells:  backhaul control and data traffic to central equipment site  [[BR]]
     42 Add OMF/OML structures, including LoginService [[BR]]
     43 Connect via switch to I2 backbone, via OF switches if there [[BR]]
     44 WiFi access point for dual-homing operating on custom PC node  [[BR]]
     45 Vehicular mobile station operating on custom PC node    [[BR]]
     46 Fixed “mobile station” for remote experimenters operating on custom PC node   [[BR]]
     47
     48b)  Plan local research experiments for Spiral 5  [[BR]]
     49 Focus on goals, configurations, steps  [[BR]]
     50 Identify necessary extended site capabilities needed in Spiral 5  [[BR]]
     51
     52c)  Complete deployments of necessary extended site capabilities needed in Spiral 5, from this list of options:  (technology supplier or coordinator shown)  [[BR]]
     53 Additional base station  (Rutgers WINLAB)  [[BR]]
     54 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     55 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     56 Connection to I2  (coordinated by BBN) [[BR]]
     57 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     58 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     59 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     60 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     61 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     62 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     63 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     64 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     65
     66d)  Support unified GENI operations:  [[BR]]
     67 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     68 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     69 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     70
     71e)  Complete and support experiments:  [[BR]]
     72 Local research experiments [[BR]]
     73 Experiments by remote experimenters, including those at tutorials  [[BR]]
     74 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     75 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     76
     77f)  Concern: how can we get all of this done? [[BR]]
     78 Common platforms and services  [[BR]]
     79 Clear plans, good schedules  [[BR]]
     80 Close cooperation!!  [[BR]]
     81 
     82==  3)  Engineering and Studies ==
     83
     84
     85
     86=== 3.1)  Cooperate with Clearwire ===
     878:35am  [[BR]]
     88Ivan Seskar (WINLAB) and Manu Gosain (GPO)[[BR]]
     8910min
     90
     91  * Current approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:  [[BR]]
     92  * Operate under an experimental license from the FCC;  otherwise require contract between site and Clearwire, with $ and conditions   [[BR]]
     93  * Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation  [[BR]]
     94  * Maintain accurate DB of site information and contacts at Rutgers, and share with Clearwire  [[BR]]
     95  * Responsive local contact, at each site  [[BR]]
     96  * Centralized monitoring server at Rutgers WINLAB  [[BR]]
     97  * Ability to quickly turn off site transmitter, if interference suspected  [[BR]]
     98  * Possible extension:  remote emergency stop, with access to GMOC  [[BR]]
     99
     100
     101 * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3GENICampusDeployments  GENI WiMAX Site Operations Resources]  [[BR]]
     102
     103 * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Monitoring Dashboard]  [[BR]]
     104
     105What are next steps?   [[BR]]
     106 *  Review information on site information and site dashboard pages, and finalize [[BR]]
     107 *  Establish process to add site information, then maintain and track   [[BR]]
     108 *  Establish email list for operations issues  [[BR]]
     109 *  Provide operations interface to GMOC and Clearwire   [[BR]]
     110 *  Complete agreement with Clearwire [[BR]]
     111 *  Encourage all GENI sites to obtain experimental licenses [[BR]]
     112 *  Include WiMAX into GENI emergency stop process  [[BR]]
     113 *  Consider adding a WiMAX "emergency stop" button, for use by the GMOC  [[BR]]
     114
     115What is the current status?  [[BR]]
     116 *  Completed agreement between WINLAB and Clearwire, to allow use of frequencies, in return for information and operations support.  [[BR]]
     117 *  Existing sites would pay no fee.  [[BR]]
     118
     119
     120=== 3.2)  Access to Sprint Broadband Services via MVNO Arrangements ===
     1218:45am  [[BR]]
     122Jim Martin (Clemson Univ) [[BR]]
     12310min  [[BR]]
     124
     125Discussions with Sprint and their partner, Arterra:  [[BR]]
     126 *  Considering approach as discussed in earlier WiNTeB workshop
     127 *  Possible configuration, and cost, have been received.
     128 *  Need to complete a proposal, and submit to NSF;  see [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/MVNOIdea-v3.pdf  slides] for overview
     129 *  How much of a research market would there be for this service?
     130 *  Another advantage: provides a path to utilize (commercial) LTE
     131
     132
     133
     134== 4)  Tasks   ==
     135
     136
     137
     138
     139
     140=== 4.1)  Build and Add Custom PC "Yellow Nodes" to WiMAX sites ===
     1419:05am  [[BR]]
     142Ivan Seskar  (WINLAB) [[BR]]
     14310min  [[BR]]
     144
     145 * These are "yellow nodes", introduced in ORBIT testbed [[BR]]
     146
     147 * Can be used as:   [[BR]]
     148  * General fixed servers  [[BR]]
     149  * Support Multiple Base-Station Mgmt Srvc   [[BR]]
     150  * Support Data-Path GW Srvc  [[BR]]
     151  * Support OMF/OML and Login services  [[BR]]
     152  * Provide WiFi access points  [[BR]]
     153  * Act as fixed "mobile stations"  [[BR]]
     154  * Act as vehicular mobile station (option:  12v power supply)  [[BR]]
     155
     156  * Currently used by:  Rutgers WINLAB;  NYU Poly;  BBN  [[BR]]
     157
     158 * How can these be provided to sites?  [[BR]]
     159  * One design to serve all needs  [[BR]]
     160  * Approximate cost:  $800 - $1500  [[BR]]
     161
     162 * What are next steps?   [[BR]]
     163  * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites   [[BR]]
     164  * Order parts (due 11/15/12)  [[BR]]
     165  * Assemble and deliver to sites  (due 1/15/13)  [[BR]]
     166  * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr?  [[BR]]
     167
     168Revised design:  [[BR]]
     169 * High-speed nodes (fixed applications only)
     170 * Low-speed nodes:  (fixed or mobile applications)
     171
     172Current schedule:  [[BR]]
     173 * All 32 nodes have been built
     174 * tentative shipping date for sites is 7/27 
     175
     176Planned allocations:  [[BR]]
     177 * 8 high-speed:  1 to each site
     178 * 24 low speed:  3 to each site
     179
     180Sites:
     181 * Need to provide Ethernet switches
     182 * Ubuntu Host to run Wimax-rf software
     183
     184
     185=== 4.2)  Write and Introduce New Services:  Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc ===
     1869:15am  [[br]]
     187Ivan Seskar  (Rutgers WINLAB) and Davide Pesavento (UCLA)  [[BR]]
     18810min  [[BR]]
     189
     190 * Multiple Base-Station Mgmt Srvc:  [[BR]]
     191
     192 * 1)  Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+;  additional updates coming  [[BR]]
     193  * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring  [[BR]]
     194  * Due:  ?  [[BR]]
     195
     196 *  2)  New WiMAX RF AggMgr for Airspan base station  [[BR]]
     197  * Provides configuration, to replace Netspan;  now running  [[BR]]
     198  * Provides node authorization, and measurements per client  [[BR]]
     199  * Could BBN, NYU Poly begin testing early version, to replace Netspan?    [[BR]]
     200  * Could early version be shipped to sites on yellow node, with OMF/OML?   [[BR]]
     201
     202 *  3)  Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API  [[BR]]
     203  * Should be useful for handover/multi-homing functions:  shared white list of MS, allowed to connect to one BS or another  [[BR]]
     204  * What other features are needed?  [[BR]]
     205  * First version due:  3/15/13  [[BR]]
     206
     207 * Data-path GW Srvc:  [[BR]]
     208  * Bridges each base station to global datapath  [[BR]]
     209  * Includes CLICK router (two types) [[BR]]
     210  * Includes OpenV switch  (open-source OF) [[BR]]
     211  * Should be useful for handover/multi-homing functions [[BR]]
     212  * First version due:  3/15/13  [[BR]]
     213  * Could there be an earlier version, that provides basic functions, and be manually configured? 
     214  * Could BBN, NYU Poly begin testing early version?    [[BR]]
     215  * Could early version be shipped to sites on yellow node?   [[BR]]
     216 
     217What are next steps?   [[BR]]
     218 * Finalize features for WiMAX RF AggMgr releases  (due 11/15/12) [[BR]]
     219 * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]]
     220 * Could there be an earlier version fo WiMAX RF AggMgr, that provides just basic functions, and be manually configured?  released by 11/15/12?  [[BR]]
     221 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     222 * Finalize features for Data-path GW Srvc releases (due 11/15/12)  [[BR]]
     223 * Establish delivery schedule for Data-path GW Srvc releases [[BR]]
     224 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     225
     226
     227Current design and schedule:  [[BR]]
     228 * See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/gec16-wimaxrf%20%5BRead-Only%5D.pdf  slides]
     229 * Airspan config completed, need to be tested;  Manu will assist
     230 * NEC config in progress
     231 * Client registration in progress;  needs to be done by end of April
     232 * Ivan has updated for OMF 5.4
     233
     234Recommendations for sites:  [[BR]]
     235
     236
     237
     238=== 4.3)  Support Central Monitoring by Rutgers WINLAB ===
     2399:25am  [[BR]]
     240Manu Gosain (GPO), Ivan Seskar (WINLAB)  [[BR]]
     2410min  [[BR]]
     242
     243Current status: [[BR]]
     244 * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Monitoring Dashboard] 
     245
     246Next steps:  [[BR]]
     247 * Remaining sites should connect, when have upgraded their WiMAX RF AggMgr.
     248
     249=== 4.4)  Write and Introduce Mobility/Handover/Multi-homing Services  ===
     2509:25am  [[BR]]
     251Parmesh Ramanathan  (Wisconsin)  [[BR]]
     2528min  [[BR]]
     253
     254 * Projects requiring handover include:  Clemson, Wayne State, Wisconsin and UCLA.    [[BR]]
     255 * Projects that can contribute handover technology include:  Rutgers WINLAB and Wisconsin.  [[BR]]
     256 * Also, commercial handover technology available from Airspan.  (Gregg Tome (Airspan))  [[BR]]
     257
     258 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx  slides]  [[BR]]
     259
     260 * Layer 2 handoff
     261  * Minimal:  Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS  [[BR]]
     262  * Better:  Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2  [[BR]]
     263  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     264
     265 * Layer 3 handoff
     266  * Minimal:  Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection
     267  [[BR]]
     268  * Better:  Use open source mobile IP s/w (Transparent Mobile IP [http://sourceforge.net/projects/tmip/ link], and OpenFlow s/w in mobile node to de-encapsulate IP packets  [[BR]]
     269  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     270
     271 * Suggested steps:    [[BR]]
     272  1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]]
     273  2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]]
     274  3) Support new Layer 3 solutions like Mobility First? [[BR]]
     275  4) Demonstrate heterogeneous network handovers [[BR]]
     276
     277What are next steps?   [[BR]]
     278 * Better define proposed configurations 1) and 2) (due 11/15/12)  [[BR]]
     279 * Review with other interested projects  [[BR]]
     280 * Understand proposed Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc, and how they could be used in the implementation  [[BR]]
     281 * Understand how Yellow Nodes could be used in the implementation  [[BR]]
     282 * Understand how Android handsets could be used in the implementation  [[BR]]
     283 * Consider potential uses of WiScape Measurement Framework  [[BR]]
     284 * With other projects, define a workplan  (due 12/15/12)  [[BR]]
     285
     286Current status:  [[BR]]
     287 * Have defined the 2 approaches;  see [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/handover_parmesh.pptx  slides]
     288 * Config 1 has been tested.
     289 * Ready to test Config 2 when Clemson has at least 2 base stations on-the-air
     290
     291=== 4.5)  Acquire and Add Android Handsets ===
     2929:35am  [[BR]]
     293Derek Meyer (Univ Wisconsin)[[BR]]
     2945min  [[BR]]
     295
     296
     297 * Summary of discussions with Sprint about unlocked HTC Evo handset  [[BR]]
     298  * 3-way NDA was signed  [[BR]]
     299  * Sprint has subcontractor who handles such purchases: contact is ? [[BR]]
     300  * Many handsets in warehouse, such as HTC Evo 4G;  approx $300 per handset[[BR]]
     301  * Must be unlocked by subcontractor, so can register with GENI network;  need to provide config to subcontractor (done by Ivan)[[BR]]
     302  * Must be sure can download Android apps[[BR]]
     303
     304What are next steps?   [[BR]]
     305 * Working with other projects, establish how many handsets are needed at which sites   [[BR]]
     306 * Consider how to provide handsets to projects no longer supported by the GPO  [[BR]]
     307 * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices  (due 12/1/12) [[BR]]
     308 * Get and check samples?  [[BR]]
     309 * Verify operation, and loading of apps [[BR]]
     310 * Deliver handsets to other projects  (due 1/15/13)  [[BR]]
     311 * Support use by other projects  [[BR]]
     312 * Maintain relationship with WSA Distributing  [[BR]]
     313
     314
     315Current status:  [[BR]]
     316 * Still working with WSA;  have received a handset, but does not work on GENI network
     317 * Next:  sending rep a table of frequencies
     318 * Next"  send rep an "xml profile", previously used
     319
     320=== 4.6) Integration with GENI portal and making WiMAX Sites Accessible to Experimenters ===
     3219:45am  [[BR]]
     322Manu Gosain (GPO) [[BR]]
     3235min  [[BR]]
     324
     325 * Portal integration [[BR]]
     326 * Include Login Service for Remote Users [[BR]]
     327
     328 
     329=== 4.7)  Connect WiMAX Sites to Persistent I2 Backbone Network, with IP Routing, to Support Multi-site Experiments ===
     3309:45am  [[BR]]
     331Manu Gosain (GPO) and Ivan Seskar (WINLAB)  [[BR]]
     3320min  [[BR]]
     333
     334
     335* Connect a WiMAX site to the GENI I2 backbone network  [[BR]]
     336  * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]]
     337  * Add switch  [[BR]]
     338  * Connect switch to I2 backbone  [[BR]]
     339  * VLAN connections from each site to "L2 router" at WINLAB   [[BR]]
     340
     341[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide]  [[BR]]
     342
     343 * When can other WiMAX sites can be added?  [[BR]]
     344  * UCLA; has physical connection;  needs to configure;  when?  [[BR]]
     345  * Wisconsin;  when?  [[BR]]
     346  * Clemson;  when?  [[BR]]
     347  * UMass Amherst; has physical connection;  needs to configure;  when?  [[BR]]
     348
     349 * How is core network configured to support multi-site experiments?   [[BR]]
     350
     351 * How is new Data-path GW Srvc use at site to interface with core network? [[BR]]
     352
     353What are next steps?  (Manu Gosain)  [[BR]]
     354 * Establish planned configuration  (due 11/15/12) [[BR]]
     355 * Establish plan with schedule to connect all sites  (due 11/15/12) [[BR]]
     356 * Track connection of sites, and assist them as needed  [[BR]]
     357
     358Current status:
     359 *  [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.7GENIWiMAXSiteBackboneConnections  Current Operational Site Backbone Connections]  [[BR]]
     360
     361
     362
     363== 5)  Status of GENI WiMAX site deployments ==
     3649:45am  [[BR]]
     365Manu Gosain (GPO) and members of site teams [[BR]]
     36615min  [[BR]]
     367
     368[http://groups.geni.net/geni/wiki/WiMAXSiteDeployments  Current status of GENI WiMAX site deployments]  [[BR]]
     369
     370=== Univ Wisconsin at Madison ===
     371
     372Suman Bannerjee:  [[BR]]
     373See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides]  [[BR]]
     374Airspan on-the-air, throughput and range evaluated  [[BR]]
     375Used by undergrad course, 80 students  [[BR]]
     376
     377=== Wayne State ===
     378
     379Hongwei Zhang:  [[BR]]
     380See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/version%203_GEC16%20Status_WayneSateU.ppt  slides]  [[BR]]
     381x2 Airspan operating  [[BR]]
     382More at [http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Developers#WiMAXPrototypinginMetroDetroit  GEC16 demo]  [[BR]]
     383
     384=== Michigan ===
     385
     386Mehrdad Moradi:  [[BR]]
     387Base station has been repaired, but still some problems.  [[BR]]
     388
     389=== Drexel ===
     390
     391Ryan Measel:  [[BR]]
     392x2 Airspan arrived  [[BR]]
     393Waiting for site engineering work, before they can be installed  [[BR]]
     394Next:  temporarily install with attenuator  [[BR]]
     395  [[BR]]
     396=== Clemson ===
     397
     398KC Wang:  [[BR]]
     399x1 Airspan on-the-air  [[BR]]
     400x2 Airspan need repair  [[BR]]
     401
     402
     403== 6)  GENI WiMAX Experiments, Demos and Tutorials ==
     404
     405=== 6.1)  Lab Experiments to Teach Wireless Basics ===
     40610:00am  [[BR]]
     407Thanasis Korakis  (NYU Poly)  [[BR]]
     4080min  [[BR]]
     409
     410 Funded project (1/13 - 12/13) to define lab experiments for students to teach wireless basics  [[BR]]
     411 To be executed on GENI wireless sites, using both WiMAX and WiFi  [[BR]]
     412 Overview and status [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/NYUPolyWirelessLab.pptx slides] [[BR]]
     413
     414What are next steps?   [[BR]]
     415 *  Early versions of lab experiments to be provided by GEC16 [[BR]]
     416
     417Current status?  [[BR]]
     418
     419==== NYU Poly ====
     420
     421See [http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Developers#WiMAXatNYU-Poly  demo at GEC16]
     422
     423==== Univ Wisconsin at Madison ====
     424
     425See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides]
     426
     427==== Columbia Univ ====
     428
     429See [http://groups.geni.net/geni/wiki/Experiments#WiMAXintheClassroomDesigningaCellularNetworkingHands-onLab  paper] at Second GENI Research and Educational Experiment Workshop (GREE2013)
     430
     431=== 6.2)  Multiple Site Experiment:  Mobility First ===
     43210:00am [[BR]]
     433Kiran Nagaraja (WINLAB)  [[BR]]
     4340min  [[BR]]
     435
     436GEC14 presentation:  [[BR]]
     437
     438[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MF-GEC12-PlenaryDemo-10-3-2011.pdf  slides] [[BR]]
     439
     440Overview of current Mobility First multiple-site experiment. [[BR]]
     441
     442What additions are needed?  [[BR]]
     4431)  Add WiFi AP to each site.  [[BR]]
     4442)  L2 path from MS to core  [[BR]]
     445
     446Experiment done without human intervention, by using x2 MAC addresses, and emulating packet loss to fake mobility.  [[BR]]
     447Consider these as possible sites by GEC13:  WINLAB;  BBN;  NYU Poly;  UCLA;  Colorado.  [[BR]]
     448
     449Current plans?  [[BR]]
     450
     451=== 6.3)  WiMAX Tutorials at GEC17 ===
     45210:00am
     453Organized by NYU Poly  [[BR]]
     4540min  [[BR]]
     455
     456[http://groups.geni.net/geni/wiki/GEC17Agenda/WimaxTutorial  WiMAX Tutorials at GEC17]  [[BR]]
     457
     458
     459=== 6.4)  Wireless Demos at GEC17 ===
     46010:00am
     4610min
     462
     463<TBD>
     464
     465
     466== 7) Adjourn ==
     46710:00am  [[BR]]
     468
     469
     470== References ==
     471
     472
     473
     474=== R1) Airspan Profile-C Base Station, with Associated Hardware and Software ===
     475Ivan Seskar (WINLAB) and Manu Gosain (GPO) [[BR]]
     476
     477 
     478a)  Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     479NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     480WINLAB and the GPO have decided to purchase base stations from Airspan, a commercial company pursuing target customers such as universities and small carriers. [[BR]]
     481For 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. [[BR]]
     482WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]]
     483
     484[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf  Airspan brochure][[BR]]
     485[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf  MacroMAXe Product Specification]  [[BR]] 
     486[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/UoC%20-%20MacroMAXe%20RF%20Plan%20V1.1.pptx  Airspan Deployment Plan for Univ Colorado at Boulder][[BR]]
     487
     488b)  Rutgers will provide a kit including: [[BR]]
     489Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]]
     490  Choice of frequency:   [[BR]]
     491  (2510 Lo:  2496MHz to 2570MHz)   [[BR]]
     492  (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     493  (2510 Hi:  2620MHz to 2690MHz)  [[BR]]
     494  (3650: 3650MHz to 3700MHz)]  [[BR]]
     495
     496NOTE:  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!
     497
     498Sector antenna, with x4 RF jumper cables [[BR]]
     4992x4 MIMO, supported by base station and antenna [[BR]]
     500GPS antenna, with surge suppressor and cable [[BR]]
     501DC power cable, from base station unit (outside) to testbed (inside) [[BR]]
     502Network management software license, 1 per base station [[BR]]
     503
     504
     505c)  Campus will need to provide: [[BR]]
     506Pole for mounting [[BR]]
     507DC power supply (-48v, approx 300W) [[BR]]
     508Ethernet 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) [[BR]]
     509Windows server to host network management software [[BR]]
     510Linux server to host OMF software [[BR]]
     511Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]]       
     512
     513d)  Additional kits can be purchased from Airspan [[BR]]
     514  Price is approximately $15,000. [[BR]]
     515 
     516e)  It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]]
     517  Thus, campus site might be able to add additional sectors, at no cost. [[BR]]
     518  Planning for next year will be done later this year. [[BR]]
     519  Consider including additional sectors within your technical plan right away.   [[BR]]
     520
     521f)  Note:  Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]]
     522  Somewhat reduced performance/range. [[BR]]
     523  Approximately half the cost [[BR]]
     524
     525g)  Airspan indicates that their sector antenna provides:[[BR]]
     526  A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]]
     527  Four internal elements, to support 2x4 MIMO.[[BR]]
     528  Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]]
     529
     530h)  Airspan shows that their profile-C base station unit can be configured to operate without an ASN GW and without a RADIUS (authentication) server.[[BR]]
     531  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.[[BR]]
     532  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[[BR]]
     533  [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf  MacroMAXe Configuration Guide][[BR]]
     534
     535i)  Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]]
     536  In this case, the base station unit operates with IP at the interface.  [[BR]]
     537
     538
     539j)  Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b  link]  [[BR]]
     540
     541
     542
     543=== R2)  Netspan Network Management System for Airspan Base Station ===
     544Manu Gosain  (GPO)  [[BR]]
     545
     546 * Suggest:  add Netspan system at each site with Airspan base station  [[BR]]
     547 * Requires:  Windows server [[BR]]
     548 * Use: setup of Netspan base station to provide basic functions  [[BR]]
     549
     550[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides]  [[BR]]
     551
     552[http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions   installation instructions]  [[BR]]
     553
     554 * Coming: replace with new WiMAX RF AggMgr  [[BR]]