Changes between Initial Version and Version 1 of Dec2012WiMAXstatus


Ignore:
Timestamp:
12/10/12 15:35:27 (11 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Dec2012WiMAXstatus

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