Changes between Version 1 and Version 2 of WiMAXGoalsStrategy


Ignore:
Timestamp:
11/02/12 15:09:52 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WiMAXGoalsStrategy

    v1 v2  
    184184
    185185
    186 
    187 
    188 
    189 === 3.1)  BBN Site Extension Plan ===
    190 3:15pm  [[BR]]
    191 Manu Gosain (GPO)  [[BR]]
    192 
    193 GEC14 status:  [[BR]]
    194  [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/BBNStatus%200710wimaxmeeting14gec.ppt slide]  [[BR]]
    195 
    196 GEC15 status:  [[BR]]
    197 a)  Status of deployments planned for Spiral 4:  [[BR]]
    198  Get experimental frequency from the FCC, that does not interfere with Clearwire services   (yes, new frequency) [[BR]]
    199  Install Airspan base station(s), with local NetSpan management system   (yes) [[BR]]
    200  Add OMF/OML structures, including LoginService  (yes)  [[BR]]
    201  Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
    202  WiFi access point for dual-homing operating on custom PC node  (partial)  [[BR]]
    203  Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
    204 
    205 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    206  Repeat throughput and range, comparing NEC and Airspan [[BR]]
    207 
    208 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    209  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    210  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    211  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    212  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    213  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    214  WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    215  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    216 
    217 d)  Support for unified GENI operations:  [[BR]]
    218  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    219  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    220  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    221 
    222 e)  Support for experiments:  [[BR]]
    223  Local research experiments [[BR]]
    224  Experiments by remote experimenters, including those at tutorials  [[BR]]
    225  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    226  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    227 
    228 
    229 
    230 === 3.2)  WINLAB/Rutgers University Site Extension Plan ===
    231 3:20pm  [[BR]]
    232 Ivan Seskar (WINLAB) [[BR]]
    233 
    234 GEC14 status: [[BR]]
    235  * Status  [[BR]]
    236   * Bringing Airspan on Busch campus  [[BR]]
    237   * Continuing remote access to BSs [[BR]]
    238   * Connected to I2 backbone network [[BR]]
    239 
    240  * Local and remote experiments [[BR]]
    241 
    242 GEC15 status:  [[BR]]
    243  * WINLAB site:  [[BR]]
    244   1)  NEC base station, with fixed mobile station [[BR]]
    245   2)  Sandbox:  NEC base station, connected via programmable RF attenuator to fixed mobile station [[BR]]
    246 
    247  * Busch campus site:  [[BR]]
    248   3)  Airspan base station, for use by students on campus [[BR]]
    249 
    250 a)  Status of deployments planned for Spiral 4:  [[BR]]
    251  Install Airspan base station(s), with local NetSpan management system  (yes) [[BR]]
    252  Optional when multiple cells:  backhaul control and data traffic to central equipment site (yes) [[BR]]
    253  Add OMF/OML structures, including LoginService  (yes) [[BR]]
    254  Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
    255  WiFi access point for dual-homing operating on custom PC node   (yes)  [[BR]]
    256  Vehicular mobile station operating on custom PC node  (yes)  [[BR]]
    257  Fixed “mobile station” for remote experimenters operating on custom PC node  (yes)  [[BR]]
    258 
    259 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    260  What is new?  [[BR]]
    261 
    262 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    263  Additional base station  (Rutgers WINLAB)  [[BR]]
    264  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    265  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    266  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    267  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    268  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    269 
    270 d)  Support for unified GENI operations:  [[BR]]
    271  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    272  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    273  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    274 
    275 e)  Support for experiments:  [[BR]]
    276  Local research experiments [[BR]]
    277  Experiments by remote experimenters, including those at tutorials  [[BR]]
    278  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    279  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    280 
    281 
    282 
    283 === 3.3)  UCLA Site Extension Plans ===
    284 3:25pm  [[BR]]
    285 Giovanni Pau, Mario Gerla (UCLA) [[BR]]
    286 
    287 GEC14 status:  [[BR]]
    288  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/ucla%20%20%202012-July-10-GEC.pptx  slides]   [[BR]]
    289 
    290  * Extension plan  [[BR]]
    291   * Add x1 Airspan BS near UCLA dormitories;  possibly other BSs.  [[BR]] 
    292   * x1  (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    293 
    294  * License [[BR]]
    295   * Renewed Experimental License [[BR]]
    296   * Coordination with Clearwire Started [[BR]]
    297 
    298  
    299 GEC15 status:
    300  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/2012-July-10-GEC%20UCLA%20GEC15.pptx  slides]  [[BR]]
    301 
    302  * Airspan Installation [[BR]]
    303   * Location selected:  top of Spraul Hall;  pole installed [[BR]]
    304   * On hold for poweer, network connections  [[BR]]
    305   * Temporary:  in use in lab for WiMAX RF AggMgr software testing  [[BR]]
    306 
    307  * Connection to Mesoscale Infrastructure   [[BR]]
    308   * Completed [[BR]]
    309 
    310 a)  Status of deployments planned for Spiral 4:  [[BR]]
    311  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes) [[BR]]
    312  Install Airspan base station(s), with local NetSpan management system  (pending, partial) [[BR]]
    313  Optional when multiple cells:  backhaul control and data traffic to central equipment site (pending)  [[BR]]
    314  Add OMF/OML structures, including LoginService  (yes) [[BR]]
    315  Connect via switch to I2 backbone, via OF switches if there   (yes) [[BR]]
    316  WiFi access point for dual-homing operating on custom PC node  (?) [[BR]]
    317  Vehicular mobile station operating on custom PC node  (?)  [[BR]]
    318  Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
    319 
    320 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    321  Coverage and performance, with Teltonica and NEC, also Airspan  [[BR]]
    322  Mobile experiments with permanent vehicular nodes  [[BR]]
    323  NDN experiments over WiMAX
    324 
    325 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    326  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    327  Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    328  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    329  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    330  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    331  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    332  WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    333  Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    334  Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    335  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    336 
    337 d)  Support for unified GENI operations:  [[BR]]
    338  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    339  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    340  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    341 
    342 e)  Support for experiments:  [[BR]]
    343  Local research experiments [[BR]]
    344  Experiments by remote experimenters, including those at tutorials  [[BR]]
    345  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    346  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    347 
    348 What are next steps?   [[BR]]
    349  * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
    350  * 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) [[BR]]
    351  * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
    352 
    353 
    354 === 3.4)  Clemson University Site Deployment Plan ===
    355 3:30pm  [[BR]]
    356 K-C Wang, Reece Johnson (Clemson)
    357 
    358 GEC13 plans:  [[BR]]
    359 [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/GEC13-WiMAX-Clemson.pdf Clemson slides][[BR]]
    360 
    361 GEC14 status:  [[BR]]
    362  * Status:  [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-Clemson.ppt slides]  [[BR]] 
    363 
    364  * Extension plan   [[BR]]
    365   * Add x1 Airspan BS near campus [[BR]]
    366   * Add x2 Airspan BS near Greenville;  connect via DOT fibers.  [[BR]]
    367   * Want handover near I85/I385 intersection.  [[BR]]
    368   * x3 (2510 Lo:  2496 to 2570 MHz)  [[BR]]
    369 
    370 GEC15 status:  [[BR]]
    371  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/GEC15-WiMAX-clemson.ppt slides]  [[BR]]
    372 
    373 
    374  * Clemson campus location:
    375   * Installed, on-the-air:  signal strength measurements completed
    376 
    377  * Greenville locations:
    378   * Installed, with power and fiber connections
    379   * Both report "RF failure";  Netspan and/or base station issue
    380 
    381 a)  Status of deployments planned for Spiral 4:  [[BR]]
    382  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
    383  Install Airspan base station(s), with local NetSpan management system  (partial: 3 installed, 1 of 3 on-the-air) [[BR]]
    384  Optional when multiple cells:  backhaul control and data traffic to central equipment site  (yes) [[BR]]
    385  Add OMF/OML structures, including LoginService  (pending) [[BR]]
    386  Connect via switch to I2 backbone, via OF switches if there (?) [[BR]]
    387  WiFi access point for dual-homing operating on custom PC node (use campus network?) [[BR]]
    388  Vehicular mobile station operating on custom PC node  (pending)  [[BR]]
    389  Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
    390 
    391 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    392  Working with Wisconsin handover project  [[BR]]
    393  Focus on "uniform solution for handover in heterogeneous networks, e.g., WiFi off-loading  [[BR]]
    394 
    395 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    396  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    397  Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    398  Connection to I2  (coordinated by BBN) [[BR]]
    399  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    400  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    401  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    402  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    403  WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    404  Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    405  Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    406  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    407 
    408 d)  Support for unified GENI operations:  [[BR]]
    409  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    410  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    411  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    412 
    413 e)  Support for experiments:  [[BR]]
    414  Local research experiments [[BR]]
    415  Experiments by remote experimenters, including those at tutorials  [[BR]]
    416  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    417  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    418 
    419 What are next steps?   [[BR]]
    420  * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
    421  * 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) [[BR]]
    422  * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
    423  
    424 === 3.5)  University of Wisconsin Site Extension Plan ===
    425 3:35pm  [[BR]]
    426 Suman Banerjee, Derek Meyer (Wisconsin)  [[BR]]
    427 
    428 GEC14 status:  [[BR]]
    429  * Status [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/2012_07_09_Geni_Conference.ppt  slides]  [[BR]]
    430 
    431  * Extension plan  [[BR]]
    432   * Add Airspan to building/tower near Capitol.  [[BR]]
    433   * Connect via Madison unified fiber project  [[BR]]
    434   * Outside contributions for power and poles.  [[BR]]
    435   * x1 (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    436 
    437 
    438 GEC15 status:  [[BR]]
    439  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf  slides]  [[BR]]
    440 
    441 
    442  * Airspan status [[BR]]
    443   * Planned installation blocked by site issues [[BR]]
    444   * Instead, will move quickly to install on CS building (where Cisco base station was installed) [[BR]]
    445 
    446 a)  Status of deployments planned for Spiral 4:  [[BR]]
    447  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
    448  Install Airspan base station(s), with local NetSpan management system  (no;  restarting) [[BR]]
    449  Optional when multiple cells:  backhaul control and data traffic to central equipment site  (?) [[BR]]
    450  Add OMF/OML structures, including LoginService  (partial) [[BR]]
    451  Connect via switch to I2 backbone, via OF switches if there (?) [[BR]]
    452  WiFi access point for dual-homing operating on custom PC node  (no)  [[BR]]
    453  Vehicular mobile station operating on custom PC node  (no)  [[BR]]
    454  Fixed “mobile station” for remote experimenters operating on custom PC node  (no) [[BR]]
    455 
    456 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    457  Focus on mobility experiments from bus  [[BR]]
    458  Planning multi-site video experiment with NYU Poly  [[BR]]
    459  Begin classroom use in Spring 2013  [[BR]]
    460 
    461 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    462  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    463  Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    464  Connection to I2  (coordinated by BBN) [[BR]]
    465  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    466  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    467  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    468  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    469  WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB) (or use local service?) [[BR]]
    470  Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    471  Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    472  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    473 
    474 d)  Support for unified GENI operations:  [[BR]]
    475  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    476  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    477  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    478 
    479 e)  Support for experiments:  [[BR]]
    480  Local research experiments [[BR]]
    481  Experiments by remote experimenters, including those at tutorials  [[BR]]
    482  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    483  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    484 
    485 What are next steps?   [[BR]]
    486  * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
    487  * 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) [[BR]]
    488  * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
    489 
    490 === 3.6)  University of Michigan Site Deployment Plan ===
    491 3:40pm [[BR]]
    492 Morley Mao  (Michigan)  [[BR]]
    493 
    494 GEC13 plans:
    495  * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/WIMAXexperimentMichigan.pdf  slides]  [[BR]]
    496 
    497 GEC14 status:  [[BR]]
    498  * Extension plan  [[BR]]
    499   * Add one Airspan on top of building  [[BR]]
    500   * Will signals penetrate into buildings?  [[BR]]
    501   * One frequency from Clearwire  [[BR]]
    502   * x1 (2510 Lo:  2496 to 2570 MHz)  [[BR]]
    503   * Location and backhaul [[BR]]
    504   * Mobility and handover [[BR]]
    505 
    506 GEC15 status:[[BR]]
    507  * Base station installed, local Netspan ready, but waiting for power  [[BR]]
    508  * I2 connection pending  [[BR]]
    509 
    510 a)  Status of deployments planned for Spiral 4:  [[BR]]
    511  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes) [[BR]]
    512  Install Airspan base station(s), with local NetSpan management system  (pending) [[BR]]
    513  Add OMF/OML structures, including LoginService  (no) [[BR]]
    514  Connect via switch to I2 backbone, via OF switches if there   (pending) [[BR]]
    515  WiFi access point for dual-homing operating on custom PC node (no) [[BR]]
    516  Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
    517 
    518 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    519  Content delivery service [[BR]]
    520 
    521 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    522  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    523  Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    524  Connection to I2  (coordinated by BBN) [[BR]]
    525  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    526  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    527  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    528  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    529  WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    530  Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    531  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    532 
    533 d)  Support for unified GENI operations:  [[BR]]
    534  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    535  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    536  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    537 
    538 e)  Support for experiments:  [[BR]]
    539  Local research experiments [[BR]]
    540  Experiments by remote experimenters, including those at tutorials  [[BR]]
    541  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    542  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    543 
    544 What are next steps?   [[BR]]
    545  * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
    546  * 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) [[BR]]
    547  * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
    548 
    549 
    550 === 3.7)  Wayne State University Site Deployment Plan ===
    551 3:45m   [[BR]]
    552 Hongwei Zhang, Yu Chu (Wayne State)  [[BR]]
    553 
    554 GEC14 status:
    555  * Status [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WayneWiMAX-deployment-planAndStatus-GEC14.pdf  slides]  [[BR]]
    556 
    557  * Extension plan  [[BR]]
    558   * Plan: one site with three sectors, and 3 Airspan base stations. [[BR]] 
    559   * One frequency (10MHz) from Clearwire  [[BR]] 
    560   * x3 (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    561 
    562  * Spectrum loan from Clearwire: done [[BR]]
    563   * 10MHz band: 2591MHz – 2601MHz (belongs to 2510 Mid band of 2560MHz~2630MHz) [[BR]] 
    564   * Current loan valid until March 1, 2013; to be renewed annually afterwards [[BR]] 
    565 
    566 GEC15 status:  [[BR]]
    567  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/WayneWiMAX-deployment-planAndStatus-GEC15-final.pdf  slides]  [[BR]]
    568 
    569  * Airspan base stations: [[BR]]
    570   * 2 installed on 17th floor, and on the air;  CINR measured [[BR]]
    571 
    572 
    573 a)  Status of deployments planned for Spiral 4:  [[BR]]
    574  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
    575  Install Airspan base station(s), with local NetSpan management system  (yes, 2 of 3) [[BR]]
    576  Optional when multiple cells:  backhaul control and data traffic to central equipment site (yes, to equipment room) [[BR]]
    577  Add OMF/OML structures, including LoginService (no) [[BR]]
    578  Connect via switch to I2 backbone, via OF switches if there  (pending) [[BR]]
    579  Vehicular mobile station operating on custom PC node  (no)  [[BR]]
    580  Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
    581 
    582 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    583  Enable handoff between different base stations/sectors [[BR]]
    584  Develop measurement services  [[BR]]
    585  Measurement campaign: spatiotemporal behavior in static & mobile scenarios: smart grid and smart transportation [[BR]]
    586  ns-3 integration [[BR]]
    587  GENI-fy OpenXC vehicular sensing and infotainment platform [[BR]]
    588  Refine OpenXC, virtualization, etc [[BR]]
    589  Integrate with OMF, measurement tools [[BR]]
    590  Integrate with v2V & V2I platforms (i.e., SDR) as well as vehicle sensing and control apps [[BR]]
    591 
    592 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    593  Additional base station   (pending) (Rutgers WINLAB)  [[BR]]
    594  Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
    595  Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    596  Connection to I2  (coordinated by BBN) [[BR]]
    597  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    598  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    599  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    600  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    601  Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    602  Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    603  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    604 
    605 d)  Support for unified GENI operations:  [[BR]]
    606  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    607  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    608  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    609 
    610 e)  Support for experiments:  [[BR]]
    611  Local research experiments [[BR]]
    612  Experiments by remote experimenters, including those at tutorials  [[BR]]
    613  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    614  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    615 
    616 What are next steps?   [[BR]]
    617  * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
    618  * 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) [[BR]]
    619  * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
    620 
    621 
    622 === 3.8) NYU Poly Site Update ===
    623 3:50pm   [[BR]]
    624 Thanasis Korakis, Fraida Fund (NYU-Poly)[[BR]]
    625 
    626 GEC14 status:  [[BR]]
    627  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-NYUPoly.pdf  slides] [[BR]]
    628 
    629  * Operational OMF/OML installation[[BR]]
    630  * Connected to I2 backbone network[[BR]]
    631  * Testbed open to experimenters since GEC12[[BR]]
    632 
    633 GEC15 status:  [[BR]]
    634 
    635  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/NYUPolyGEC15.pdf slides] [[BR]]
    636 
    637  * Airspan base station isntallation still pending.
    638  * Working closely with UMass Amherst on use of GIMI tools with WiMAX
    639  * Supporting experimenters, including students and tutorials
    640 
    641 a)  Status of deployments planned for Spiral 4:  [[BR]]
    642  Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
    643  Install Airspan base station(s), with local NetSpan management system  (pending) [[BR]]
    644  Optional when multiple cells:  backhaul control and data traffic to central equipment site  (?) [[BR]]
    645  Add OMF/OML structures, including LoginService  (yes)  [[BR]]
    646  Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
    647  WiFi access point for dual-homing operating on custom PC node  (yes) [[BR]]
    648  Vehicular mobile station operating on custom PC node  (?)  [[BR]]
    649  Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
    650 
    651 b)  Plan for local research experiments in Spiral 5:   [[BR]]
    652  Many experiments formulated for students, and tutorials, including: [[BR]]
    653   StreamLoad [[BR]]
    654   NetCheck [[BR]]
    655   AFFIX [[BR]]
    656  Working on set of lab experiments to teach wireless principals  [[BR]]
    657 
    658 c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
    659  GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
    660  Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    661  Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    662  Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
    663  Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
    664  Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
    665 
    666 d)  Support for unified GENI operations:  [[BR]]
    667  Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
    668  Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
    669  When necessary, do an “emergency stop” of your transmissions.  [[BR]]
    670 
    671 e)  Support for experiments:  [[BR]]
    672  Local research experiments [[BR]]
    673  Experiments by remote experimenters, including those at tutorials  [[BR]]
    674  Classroom instruction experiments by students   (NYU Poly)  [[BR]]
    675  Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
    676 
    677 What are next steps?   [[BR]]
    678  * 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) [[BR]]
    679 
    680 
    681 === 3.9) UMass Amherst Site Update ===
    682 3:55pm   [[BR]]
    683 Mike Zink, Cong Wang (UMass Amherst)  [[BR]]
    684 
    685 GEC14 status:
    686  * Add OMF/OML:  have installed  [[BR]]
    687  * Connect to I2 backbone network:  plan to do soon  [[BR]]
    688 
    689  * Planned experiments:  use to integrate GIMI tools [[BR]]
    690 
    691 GEC15 status:  BR]]
    692  No report  [[BR]]
    693 
    694 === 3.xx)  Temple University Site Deployment Plan ===
    695 Shan Lin, Jie Wu (Temple)  [[BR]]
    696 
    697 GEC14 status:  [[BR]]
    698  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/geni-meeting-temple-july2012.pptx slides]  [[BR]]
    699 
    700  * Extension plan  [[BR]]
    701   * x1 (or x2?) Airspan base stations (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    702   * Two frequencies from Clearwire, shared with Drexel  [[BR]]
    703   * Location and backhaul [[BR]]
    704   * Mobility and handover [[BR]]
    705 
    706  * License application approved by Clear [[BR]] 
    707   * License is valid until Jan 31, 2013 [[BR]] 
    708   * Frequencies: 2585-2595 & 2603-2613 MHz [[BR]] 
    709   * Clearwire holds the right to terminate operation with 30 days prior notice [[BR]] 
    710 
    711  * Wimax base station purchased and arrived [[BR]] 
    712   * One Air4G-MacroMAXe 2510M Air4G-W24-2510MT [[BR]] 
    713   * Installation contract placed  [[BR]] 
    714   * Latitude & Longitude: (39.98038, -75.15703) [[BR]] 
    715   * Height: 12th floor (131 ft)  [[BR]]   
    716 
    717  * Experiments (with the existing TU-WiMax) [[BR]] 
    718   * Observe highly irregular ranges (longest range>2.29mile) [[BR]] 
    719   * High bandwidth (>700kbps) only very close to the base station (<0.5mile) [[BR]] 
    720   * Significant shadowing among buildings [[BR]] 
    721 
    722 
    723 GEC15 status:  BR]]
    724  * No report  [[BR]]
    725  
    726 === 3.xx)  Drexel University Site Deployment Plan ===
    727 Kevin Wanuga, Jeff Wildman, Kapil Dandekar (Drexel)  [[BR]]
    728 
    729 GEC13 plans:  [[BR]]
    730  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC13%20%20drexel%20%20GENI.ppt slides] [[BR]]
    731 
    732 GEC14 status:  [[BR]]
    733  * Extension plan  [[BR]]
    734   * x1 (or x2?) Airspan base stations (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    735   * Two frequencies from Clearwire, shared with Temple  [[BR]]
    736   * Location and backhaul [[BR]]
    737   * Mobility and handover [[BR]]
    738 
    739  * Kevin Wanuga reports: [[BR]]
    740   * Planning for top of 18-story building;  3m radiation safety clearance [[BR]]
    741   * More urban than Temple [[BR]]
    742   * Airspan order placed;  not yet received [[BR]]
    743   * Kiva networks to install base station [[BR]]
    744   * Contract engineer mast;  recommendation from Giovanni:  check masts at GNE supply [[BR]]
    745   * Questions about power cable; recommendation from Harry:  call us, and we can explain parameters [[BR]]
    746 
    747 
    748 GEC15 status:  BR]]
    749  * No report  [[BR]]
    750 
    751 
    752 
    753 === 3.xx) Univ of Colorado at Boulder Site Update ===
    754 Dirk Grunwald (Colorado)  [[BR]]
    755 
    756 
    757 GEC15 status:  BR]]
    758  * No report  [[BR]]
    759 
    760 === 3.xx) Columbia University Site Update ===
    761 Henning Schulzrinne, Jan Janak (Columbia)  [[BR]]
    762 
    763 
    764 GEC15 status:  BR]]
    765  * No report  [[BR]]
    766 
    767 == 4)  GENI WiMAX Deployment Tasks and Issues ==
    768 4:00pm  [[BR]]
    769 
    770 
    771 === 4.1)  Co-exist with Clearwire ===
    772 4:00pm  [[BR]]
    773 Manu Gosain  (GPO) and Ivan Seskar (WINLAB)
    774 
    775  * Current approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:  [[BR]]
    776   * Operate under an experimental license from the FCC;  otherwise require contract between site and Clearwire, with $ and conditions   [[BR]]
    777   * Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation  [[BR]]
    778   * Maintain accurate DB of site information and contacts at Rutgers, and share with Clearwire  [[BR]]
    779   * Responsive local contact, at each site  [[BR]]
    780   * Centralized monitoring server at Rutgers WINLAB  [[BR]]
    781   * Ability to quickly turn off site transmitter, if interference suspected  [[BR]]
    782   * Possible extension:  remote emergency stop, with access to GMOC  [[BR]]
    783 
    784 
    785  * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3GENICampusDeployments  GENI WiMAX Site Information]  [[BR]]
    786  * [http://wimax.orbit-lab.org/wiki/WiMAX/27#a10.GENIWimaxSites  GENI WiMAX Site Licenses]  [[BR]]
    787 
    788 
    789  * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Dashboard]  [[BR]]
    790 
    791 What are next steps?   [[BR]]
    792  *  Review information on site information and site dashboard pages, and finalize [[BR]]
    793  *  Establish process to add site information, then maintain and track   [[BR]]
    794  *  Establish email list for operations issues  [[BR]]
    795  *  Provide operations interface to GMOC and Clearwire   [[BR]]
    796  *  Complete agreement with Clearwire [[BR]]
    797  *  Encourage all GENI sites to obtain experimental licenses [[BR]]
    798  *  Include WiMAX into GENI emergency stop process  [[BR]]
    799  *  Consider adding a WiMAX "emergency stop" button, for use by the GMOC  [[BR]]
    800 
    801 === 4.2)  New services:  Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc ===
    802 4:10pm  [[br]]
    803 Ivan Seskar  (Rutgers WINLAB) and Davide Pesavento (UCLA)  [[BR]]
    804 
    805  * Multiple Base-Station Mgmt Srvc:  [[BR]]
    806 
    807  * 1)  Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+;  additional updates coming  [[BR]]
    808   * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring  [[BR]]
    809   * Due:  ?  [[BR]]
    810 
    811  *  2)  New WiMAX RF AggMgr for Airspan base station  [[BR]]
    812   * Provides configuration, to replace Netspan;  now running  [[BR]]
    813   * Provides node authorization, and measurements per client  [[BR]]
    814   * First version due:  12/15/12 [[BR]]
    815   * Could BBN, NYU Poly begin testing early version, to replace Netspan?    [[BR]]
    816   * Could early version be shipped to sites on yellow node, with OMF/OML?   [[BR]]
    817 
    818  *  3)  Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API  [[BR]]
    819   * Should be useful for handover/multi-homing functions:  shared white list of MS, allowed to connect to one BS or another  [[BR]]
    820   * What other features are needed?  [[BR]]
    821   * First version due:  3/15/13  [[BR]]
    822 
    823  * Data-path GW Srvc:  [[BR]]
    824   * Bridges each base station to global datapath  [[BR]]
    825   * Includes CLICK router (two types) [[BR]]
    826   * Includes OpenV switch  (open-source OF) [[BR]]
    827   * Should be useful for handover/multi-homing functions [[BR]]
    828   * First version due:  3/15/13  [[BR]]
    829   * Could there be an earlier version, that provides basic functions, and be manually configured? 
    830   * Could BBN, NYU Poly begin testing early version?    [[BR]]
    831   * Could early version be shipped to sites on yellow node?   [[BR]]
    832  
    833 What are next steps?   [[BR]]
    834  * Finalize features for WiMAX RF AggMgr releases  (due 11/15/12) [[BR]]
    835  * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]]
    836  * 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]]
    837  * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
    838  * Finalize features for Data-path GW Srvc releases (due 11/15/12)  [[BR]]
    839  * Establish delivery schedule for Data-path GW Srvc releases [[BR]]
    840  * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
    841 
    842 === 4.3)  WiScape Measurement Framework ===
    843 4:20pm  [[BR]]
    844 Suman Banerjee (Univ Wisc)
    845 
    846  * Overview of current functions  [[BR]]
    847   * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf  slides]  [[BR]]
    848   * A data measurement framework with APIs, that the clients and the measurement server expose  [[BR]]
    849   * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server  [[BR]]
    850   * Measurement include latency, loss, throughput, TCP or UDP  [[BR]]
    851   * Provides feedback to network selection  [[BR]]
    852   * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php  link to WiScape]  [[BR]]
    853 
    854 What are next steps?   [[BR]]
    855  * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution  [[BR]]
    856 
    857 === 4.4)  Mobility/handover/multi-homing services  ===
    858 4:25pm  [[BR]]
    859 Parmesh Ramanathan  (Wisconsin)  [[BR]]
    860 
    861  * Projects requiring handover include:  Clemson, Wayne State, Wisconsin and UCLA.    [[BR]]
    862  * Projects that can contribute handover technology include:  Rutgers WINLAB and Wisconsin.  [[BR]]
    863  * Also, commercial handover technology available from Airspan.  (Gregg Tome (Airspan))  [[BR]]
    864 
    865  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx  slides]  [[BR]]
    866 
    867  * Layer 2 handoff
    868   * Minimal:  Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS  [[BR]]
    869   * Better:  Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2  [[BR]]
    870   * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
    871 
    872  * Layer 3 handoff
    873   * Minimal:  Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection
    874   [[BR]]
    875   * 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]]
    876   * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
    877 
    878  * Suggested steps:    [[BR]]
    879   1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]]
    880   2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]]
    881   3) Support new Layer 3 solutions like Mobility First? [[BR]]
    882   4) Demonstrate heterogeneous network handovers [[BR]]
    883 
    884 What are next steps?   [[BR]]
    885  * Better define proposed configurations 1) and 2) (due 11/15/12)  [[BR]]
    886  * Review with other interested projects  [[BR]]
    887  * Understand proposed Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc, and how they could be used in the implementation  [[BR]]
    888  * Understand how Yellow Nodes could be used in the implementation  [[BR]]
    889  * Understand how Android handsets could be used in the implementation  [[BR]]
    890  * Consider potential uses of WiScape Measurement Framework  [[BR]]
    891  * With other projects, define a workplan  (due 12/15/12)  [[BR]]
    892 
    893 
    894 === 4.5)  Mobility/handover/multi-homing plans ===
    895 4:30pm  [[BR]]
    896 All  [[BR]]
    897 
    898  * What is the best roadmap to useful mobility/handover/multi-homing services based on planned and available platforms and software?  [[BR]]
    899 
    900 
    901 === 4.6)  Add "yellow nodes" to WiMAX Sites ===
    902 4:45pm  [[BR]]
    903 Ivan Seskar  (WINLAB) [[BR]]
    904 
    905  * These are "yellow nodes", introduced in ORBIT testbed [[BR]]
    906 
    907  * Can be used as:   [[BR]]
    908   * General fixed servers  [[BR]]
    909   * Support Multiple Base-Station Mgmt Srvc   [[BR]]
    910   * Support Data-Path GW Srvc  [[BR]]
    911   * Support OMF/OML and Login services  [[BR]]
    912   * Provide WiFi access points  [[BR]]
    913   * Act as fixed "mobile stations"  [[BR]]
    914   * Act as vehicular mobile station (option:  12v power supply)  [[BR]]
    915 
    916   * Currently used by:  Rutgers WINLAB;  NYU Poly;  BBN  [[BR]]
    917 
    918  * How can these be provided to sites?  [[BR]]
    919   * One design to serve all needs  [[BR]]
    920   * Approximate cost:  $800 - $1500  [[BR]]
    921 
    922 What are next steps?   [[BR]]
    923   * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites   [[BR]]
    924   * Order parts (due 11/15/12)  [[BR]]
    925   * Assemble and deliver to sites  (due 1/15/13)  [[BR]]
    926   * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr?  [[BR]]
    927 
    928 
    929 === 4.7)  Mobile Station using Android Handset ===
    930 4:55pm  [[BR]]
    931 Derek Meyer (Univ Wisconsin)[[BR]]
    932 
    933  * Summary of discussions with Sprint about unlocked HTC Evo handset  [[BR]]
    934   * 3-way NDA was signed  [[BR]]
    935   * Sprint has subcontractor who handles such purchases: contact is ? [[BR]]
    936   * Many handsets in warehouse, such as HTC Evo 4G;  approx $300 per handset[[BR]]
    937   * Must be unlocked by subcontractor, so can register with GENI network;  need to provide config to subcontractor (done by Ivan)[[BR]]
    938   * Must be sure can download Android apps[[BR]]
    939 
    940 What are next steps?   [[BR]]
    941  * Working with other projects, establish how many handsets are needed at which sites   [[BR]]
    942  * Consider how to provide handsets to projects no longer supported by the GPO  [[BR]]
    943  * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices  (due 12/1/12) [[BR]]
    944  * Get and check samples?  [[BR]]
    945  * Verify operation, and loading of apps [[BR]]
    946  * Deliver handsets to other projects  (due 1/15/13)  [[BR]]
    947  * Support use by other projects  [[BR]]
    948  * Maintain relationship with WSA Distributing  [[BR]]
    949 
    950  
    951 
    952 == 5) Adjourn ==
    953 5:00pm  [[BR]]
    954 
    955 Please join us for a Wimax BoF dinner. Please indicate on this poll, if you will be attending
    956 
    957  http://www.doodle.com/gtz6rdv9b37gg4rc
    958 
    959 == References ==
    960 
    961 
    962 
    963 === R2) Overview of GENI WiMAX Sites and Experiments ===
    964 Harry Mussman (GPO) [[BR]]
    965 
    966 Paper including sections on basic and extended WiMAX sites, and on WiMAX research and service experiments:    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/020112b_ExtendingGENI_TridentCom2012.pdf  pdf]  [[BR]]
    967 
    968 
    969 === R3) Airspan Profile-C Base Station, with Associated Hardware and Software ===
    970 Ivan Seskar (WINLAB) and Harry Mussman (GPO) [[BR]]
    971 
    972  
    973 a)  Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
    974 NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
    975 WINLAB and the GPO have decided to purchase base stations from Airspan, a commercial company pursuing target customers such as universities and small carriers. [[BR]]
    976 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. [[BR]]
    977 WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]]
    978 
    979 [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf  Airspan brochure][[BR]]
    980 [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf  MacroMAXe Product Specification]  [[BR]] 
    981 [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]]
    982 
    983 b)  Rutgers will provide a kit including: [[BR]]
    984 Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]]
    985   Choice of frequency:   [[BR]]
    986   (2510 Lo:  2496MHz to 2570MHz)   [[BR]]
    987   (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
    988   (2510 Hi:  2620MHz to 2690MHz)  [[BR]]
    989   (3650: 3650MHz to 3700MHz)]  [[BR]]
    990 
    991 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!
    992 
    993 Sector antenna, with x4 RF jumper cables [[BR]]
    994 2x4 MIMO, supported by base station and antenna [[BR]]
    995 GPS antenna, with surge suppressor and cable [[BR]]
    996 DC power cable, from base station unit (outside) to testbed (inside) [[BR]]
    997 Network management software license, 1 per base station [[BR]]
    998 
    999 
    1000 c)  Campus will need to provide: [[BR]]
    1001 Pole for mounting [[BR]]
    1002 DC power supply (-48v, approx 300W) [[BR]]
    1003 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) [[BR]]
    1004 Windows server to host network management software [[BR]]
    1005 Linux server to host OMF software [[BR]]
    1006 Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]]       
    1007 
    1008 d)  Additional kits can be purchased from Airspan [[BR]]
    1009   Price is approximately $15,000. [[BR]]
    1010  
    1011 e)  It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]]
    1012   Thus, campus site might be able to add additional sectors, at no cost. [[BR]]
    1013   Planning for next year will be done later this year. [[BR]]
    1014   Consider including additional sectors within your technical plan right away.   [[BR]]
    1015 
    1016 f)  Note:  Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]]
    1017   Somewhat reduced performance/range. [[BR]]
    1018   Approximately half the cost [[BR]]
    1019 
    1020 g)  Airspan indicates that their sector antenna provides:[[BR]]
    1021   A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]]
    1022   Four internal elements, to support 2x4 MIMO.[[BR]]
    1023   Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]]
    1024 
    1025 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.[[BR]]
    1026   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]]
    1027   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]]
    1028   [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf  MacroMAXe Configuration Guide][[BR]]
    1029 
    1030 i)  Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]]
    1031   In this case, the base station unit operates with IP at the interface.  [[BR]]
    1032 
    1033 
    1034 j)  Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b  link]  [[BR]]
    1035 
    1036 
    1037 
    1038 === R4)  Netspan Network Management System for Airspan Base Station ===
    1039 Manu Gosain  (GPO)  [[BR]]
    1040 
    1041  * Suggest:  add Netspan system at each site with Airspan base station  [[BR]]
    1042  * Requires:  Windows server [[BR]]
    1043  * Use: setup of Netspan base station to provide basic functions  [[BR]]
    1044 
    1045 [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides]  [[BR]]
    1046 
    1047 [http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions   installation instructions]  [[BR]]
    1048 
    1049  * Coming: replace with new WiMAX RF AggMgr  [[BR]]
    1050 
    1051 
    1052 
    1053 
    1054 
    1055 === R5) Add OMF/OML to WiMAX sites ===
    1056 Fraida Fund (NYU Poly), Manu Gosain (GPO), Derek Meyer (Wisconsin), [[BR]]
    1057 
    1058  * Equip a WiMAX site with full OMF/OML capabilities, installing on VMs  [[BR]]
    1059  * Include Login Service for Remote Users [[BR]]
    1060 
    1061  * NYU Poly configuration:  [[BR]]
    1062 
    1063  * 1) physical host acting as base station controller, runs the asn-gw and wimaxrf AM. [[BR]]
    1064   * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
    1065   * 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).  [[BR]]
    1066   * 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. [[BR]]
    1067 
    1068  * 2) physical host running OMF 5.3 AM, EC, and some other services that are useful for the testbed. [[BR]]
    1069   * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
    1070   * It has Ethernet connections to NYU-Poly network (internet) and OMF control network.  [[BR]]
    1071   * 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. [[BR]]
    1072 
    1073  * 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)  [[BR]]
    1074   * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]]
    1075 
    1076  * Our testbed nodes are scattered throughout several CS labs and research areas (not part of our group).  [[BR]]
    1077   * 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. [[BR]]
    1078   * We do have an openflow switch that we plan to deploy somewhere at some point. [[BR]]
    1079 
    1080 
    1081 
    1082 
    1083  * BBN experience  (need summary)  [[BR]]
    1084 
    1085  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/vmsetup_at_uwmadison.pdf Wisconsin configuration] [[BR]]
    1086 
    1087  * All services are running on the same physical machine. [[BR]]
    1088   * HP server that came with the base station.  [[BR]]
    1089   * The base OS is Debian and virtual machines using for the services (Virtualbox)  [[BR]]
    1090 
    1091  * Physical machine network connections: [[BR]]
    1092   * Eth0 (128.105.22.xxx): University network (internet) [[BR]]
    1093   * Eth1 (10.3.8.126): Network to IDU of base station [[BR]]
    1094   * Eth2 (10.0.0.1): Control network for omf [[BR]]
    1095   * Eth3: Connected to openflow (physically, but not enabled until we can get a vlan tag to GENI backbone) [[BR]]
    1096 
    1097  * Base operating system:  Debian [[BR]]
    1098 
    1099  * Virtualbox guests: [[BR]]
    1100   * 1.  Ubuntu 9.04 ->  aggmgr 5.2 ->  wimaxrf service [[BR]]
    1101   * Eth0 (128.105.22.xxx):  bridged interface to university network [[BR]]
    1102   * Eth1(10.3.8.254):  bridged interface to base station network [[BR]]
    1103 
    1104   * 2.  Ubuntu 10.04 ->  aggmgr 5.3 ->  cmcStub, Frisbee, inventory, pxe, result, saveimage [[BR]]
    1105   * Also expctl, resctl, and xmpp on same machine [[BR]]
    1106   * Eth0 (128.105.22.xxx): bridged interface to university network [[BR]]
    1107   * Eth1 (10.0.0.200): bridged interface to control network [[BR]]
    1108 
    1109 
    1110 
    1111  * Coming:  plan to federate with ProtoGENI cluster  [[BR]]
    1112   *  Reference: [http://www.tridentcom.org/2012/program  TridentCom 2012]  :  "Federating wired and wireless test facilities through Emulab and OMF: the iLab.t use case", Stefan Bouckaert (IBBT - Ghent University)  [[BR]]
    1113   *  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.  [[BR]]
    1114 
    1115 
    1116 
    1117 
    1118 === R6)  Connect WiMAX sites to I2 backbone network, to support multi-site experiments ===
    1119 Manu Gosain (GPO), Fraida Fund (NYU Poly), Ivan Seskar (WINLAB)  [[BR]]
    1120 
    1121 * Connect a WiMAX site to the GENI I2 backbone network  [[BR]]
    1122   * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]]
    1123   * Add switch  [[BR]]
    1124   * Connect switch to I2 backbone  [[BR]]
    1125   * VLAN connections from each site to "L2 router" at WINLAB   [[BR]]
    1126 
    1127 [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide]  [[BR]]
    1128 
    1129  * When can other WiMAX sites can be added?  [[BR]]
    1130   * UCLA; has physical connection;  needs to configure;  when?  [[BR]]
    1131   * Wisconsin;  when?  [[BR]]
    1132   * Clemson;  when?  [[BR]]
    1133   * UMass Amherst; has physical connection;  needs to configure;  when?  [[BR]]
    1134 
    1135  * How is core network configured to support multi-site experiments?   [[BR]]
    1136 
    1137  * How is new Data-path GW Srvc use at site to interface with core network? [[BR]]
    1138 
    1139 What are next steps?  (Manu Gosain)  [[BR]]
    1140  * Establish planned configuration  (due 11/15/12) [[BR]]
    1141  * Establish plan with schedule to connect all sites  (due 11/15/12) [[BR]]
    1142  * Track connection of sites, and assist them as needed  [[BR]]
    1143 
    1144 === R7) GENI WiMAX Experiments, Demos and Tutorials ===
    1145 
    1146 [http://groups.geni.net/geni/wiki/Experiments  link]  [[BR]]