Changes between Version 4 and Version 5 of GEC17Agenda/WiMAXDevelopers


Ignore:
Timestamp:
06/03/13 15:52:23 (6 years ago)
Author:
agosain@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC17Agenda/WiMAXDevelopers

    v4 v5  
    1616
    1717NOTE: 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!
     18
     19== 1)  Introductions ==
     203:30pm  [[BR]]
     215min [[BR]]
     22
     23== 2)  Spiral 5 Goals ==
     243:35pm  [[BR]]
     25Harry Mussman (GPO) [[BR]]
     260min  [[BR]]
     27
     28a)  Where necessary, complete deployments planned for Spiral 4:  [[BR]]
     29 Get experimental frequency from the FCC, that does not interfere with Clearwire services  [[BR]]
     30 Install Airspan base station(s), with local NetSpan management system  [[BR]]
     31 Optional when multiple cells:  backhaul control and data traffic to central equipment site  [[BR]]
     32 Add OMF/OML structures, including LoginService [[BR]]
     33 Connect via switch to I2 backbone, via OF switches if there [[BR]]
     34 WiFi access point for dual-homing operating on custom PC node  [[BR]]
     35 Vehicular mobile station operating on custom PC node    [[BR]]
     36 Fixed “mobile station” for remote experimenters operating on custom PC node   [[BR]]
     37
     38b)  Plan local research experiments for Spiral 5  [[BR]]
     39 Focus on goals, configurations, steps  [[BR]]
     40 Identify necessary extended site capabilities needed in Spiral 5  [[BR]]
     41
     42c)  Complete deployments of necessary extended site capabilities needed in Spiral 5, from this list of options:  (technology supplier or coordinator shown)  [[BR]]
     43 Additional base station  (Rutgers WINLAB)  [[BR]]
     44 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     45 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     46 Connection to I2  (coordinated by BBN) [[BR]]
     47 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     48 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     49 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     50 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     51 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     52 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     53 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     54 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     55
     56d)  Support unified GENI operations:  [[BR]]
     57 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     58 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     59 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     60
     61e)  Complete and support experiments:  [[BR]]
     62 Local research experiments [[BR]]
     63 Experiments by remote experimenters, including those at tutorials  [[BR]]
     64 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     65 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     66
     67f)  Concern: how can we get all of this done? [[BR]]
     68 Common platforms and services  [[BR]]
     69 Clear plans, good schedules  [[BR]]
     70 Close cooperation!!  [[BR]]
     71 
     72==  3)  Engineering and Studies ==
     73
     74
     75
     76=== 3.1)  Cooperate with Clearwire ===
     773:35pm  [[BR]]
     78Ray Raychaudhuri (WINLAB), Ivan Seskar (WINLAB) and Harry Mussman (GPO)[[BR]]
     7910min
     80
     81 * Current approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:  [[BR]]
     82  * Operate under an experimental license from the FCC;  otherwise require contract between site and Clearwire, with $ and conditions   [[BR]]
     83  * Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation  [[BR]]
     84  * Maintain accurate DB of site information and contacts at Rutgers, and share with Clearwire  [[BR]]
     85  * Responsive local contact, at each site  [[BR]]
     86  * Centralized monitoring server at Rutgers WINLAB  [[BR]]
     87  * Ability to quickly turn off site transmitter, if interference suspected  [[BR]]
     88  * Possible extension:  remote emergency stop, with access to GMOC  [[BR]]
     89
     90
     91 * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3GENICampusDeployments  GENI WiMAX Site Operations Resources]  [[BR]]
     92
     93 * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Monitoring Dashboard]  [[BR]]
     94
     95What are next steps?   [[BR]]
     96 *  Review information on site information and site dashboard pages, and finalize [[BR]]
     97 *  Establish process to add site information, then maintain and track   [[BR]]
     98 *  Establish email list for operations issues  [[BR]]
     99 *  Provide operations interface to GMOC and Clearwire   [[BR]]
     100 *  Complete agreement with Clearwire [[BR]]
     101 *  Encourage all GENI sites to obtain experimental licenses [[BR]]
     102 *  Include WiMAX into GENI emergency stop process  [[BR]]
     103 *  Consider adding a WiMAX "emergency stop" button, for use by the GMOC  [[BR]]
     104
     105What is the current status?  [[BR]]
     106 *  Working on pending agreement between WINLAB and Clearwire, to allow use of frequencies, in return for information and operations support.  [[BR]]
     107 *  Existing sites would pay no fee.  [[BR]]
     108 *  What happens when Sprint completes deal to buy Clearwire?  [[BR]]
     109
     110=== 3.2)  Access to Sprint Broadband Services via MVNO Arrangements ===
     1113:45pm  [[BR]]
     112Jim Martin (Clemson Univ) and Harry Mussman (GPO) [[BR]]
     11310min  [[BR]]
     114
     115Discussions with Sprint and their partner, Arterra:  [[BR]]
     116 *  Considering approach as discussed in earlier WiNTeB workshop
     117 *  Possible configuration, and cost, have been received.
     118 *  Need to complete a proposal, and submit to NSF;  see [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/MVNOIdea-v3.pdf  slides] for overview
     119 *  How much of a research market would there be for this service?
     120 *  Another advantage: provides a path to utilize (commercial) LTE
     121
     122
     123
     124=== 3.3)  Options for Introducing LTE Equipment ===
     1253:55pm  [[BR]]
     126Suman Banerjee  [[BR]]
     1275min [[BR]]
     128
     129GEC14 discussion:  [[BR]]
     130 Moderator:  Harry Mussman  (GPO)  [[BR]]
     131 Ray Raychaudhuri  (WINLAB)  [[BR]]
     132 Ivan Seskar  (WINLAB)  [[BR]]
     133 Patrick Gossman (Wayne State) [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/The%20Case%20for%20LTE.pptx  The Case for LTE]  [[BR]]
     134 Gregg Tome (Airspan)  [[BR]]
     135
     136GEC15 discussion group formed: [[BR]]
     137 Moderator:  Suman Banerjee  (Wisconsin) [[BR]]
     138 Ray Raychaudhuri  (WINLAB)  [[BR]]
     139 Ivan Seskar  (WINLAB)  [[BR]]
     140 Patrick Gossman (Wayne State) [[BR]]
     141 Bryan Lyles (NSF)  [[BR]]
     142 Jacobus (Kobus) Van der Merwe (Utah)  (new)   [[BR]]
     143 Tod Sizer (Bell Labs/Alcatel-Lucent)  (new)   [[BR]]
     144 Walt Magnusen (Texas A&M)  (new)  [[BR]]
     145 Harry Mussman  (GPO)  [[BR]]
     146
     147What are our goals?   [[BR]]
     148
     149How do we match available:  base station equipment, on-air frequencies and mobile stations? [[BR]]
     150
     151[http://niviuk.free.fr/lte_band.php  LTE frequency bands (from Ivan)] [[BR]]
     152
     153Gregg Tome:  Airspan has equipment that operates at 2.6GHz (but this is outside of EBS band) [[BR]]
     154
     155Tod Sizer:  Have used commercial small cells operating at low power, borrowed commercial spectrum, and commercial devices, in a lab setting. [[BR]]
     156
     157Ivan and Tod:  There is available open-source back-end software (Fraunhoffer?) [[BR]]
     158
     159Walt:  Has equipment to test for LTE in public safety, from General Dynamics/IPWireless  [[BR]]
     160
     161What are next steps?   [[BR]]
     162 *  Tod to talk with Ray and Ivan [[BR]]
     163 *  Suman to organize calls/meetings   [[BR]]
     164
     165What is current status?  [[BR]]
     166 *  See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides}
     167 *  Idea:  introduce on-the-air LTE in a remote location (northern Wisconsin), where no interference with anyone else
     168 *  Consider:  platform based on picochip/mindspeed, plus open-source software
     169
     170== 4)  Tasks   ==
     1714:00pm  [[BR]]
     172
     173
     174
     175
     176=== 4.1) Install Airspan Profile-C Base Stations ===
     1774:00pm  [[BR]]
     178Manu Gosain  (GPO) and Ivan Seskar (WINLAB)  [[BR]]
     1796min  [[BR]]
     180
     181
     182Airspan base stations successfully installed:  [[BR]]
     183 *  WINLAB 1
     184 *  BBN 1
     185 *  UCLA 1
     186 *  Wayne State 1, 2
     187 *  Wisconsin 1
     188
     189Airspan base stations with defects, and their current status: [[BR]]
     190 *  Michigan 1:  Sent with RMA after power accident/fault;  Received with power fixed, but RF transmitters reporting Fault; client connection fails; 3/27: actively debugging with Airspan technical support who has remote access to the base station
     191 *  Clemson 1: short outage due to GPS unit corrosion - replaced GPS and back to normal.
     192 *  Clemson 2: failed on first boot; went through circular debug-RMA request-debug-RMA request; 3/18:  Airspan examined remotely, and confirmed problem needing RMA, and offered to advance ship a replacement, while Clemson returns unit. 
     193 *  Clemson 3: high loss when connected to Netspan, waiting for new GPS receiver, then proceed to Airspan debug
     194
     195Technical tickets:  Manu has an account, track all open tickets.
     196Airspan has remote access:  Michigan 1;  Clemson 2 (more?)
     197
     198RMA process:  Typically Manu starts, site continues, and Airspan approves;  then site ships back;  who pays for shipping when there is an Airspan fault?
     199Approximate shipping costs:  $300
     200
     201Next steps:  [[BR]]
     202 *  Review with Airspan ASAP, and define steps and schedule to be on-the-air soon, e.g., by end of April.
     203
     204
     205=== 4.2)  Build and Add Custom PC "Yellow Nodes" to WiMAX sites ===
     2064:05pm  [[BR]]
     207Ivan Seskar  (WINLAB) [[BR]]
     20810min  [[BR]]
     209
     210 * These are "yellow nodes", introduced in ORBIT testbed [[BR]]
     211
     212 * Can be used as:   [[BR]]
     213  * General fixed servers  [[BR]]
     214  * Support Multiple Base-Station Mgmt Srvc   [[BR]]
     215  * Support Data-Path GW Srvc  [[BR]]
     216  * Support OMF/OML and Login services  [[BR]]
     217  * Provide WiFi access points  [[BR]]
     218  * Act as fixed "mobile stations"  [[BR]]
     219  * Act as vehicular mobile station (option:  12v power supply)  [[BR]]
     220
     221  * Currently used by:  Rutgers WINLAB;  NYU Poly;  BBN  [[BR]]
     222
     223 * How can these be provided to sites?  [[BR]]
     224  * One design to serve all needs  [[BR]]
     225  * Approximate cost:  $800 - $1500  [[BR]]
     226
     227 * What are next steps?   [[BR]]
     228  * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites   [[BR]]
     229  * Order parts (due 11/15/12)  [[BR]]
     230  * Assemble and deliver to sites  (due 1/15/13)  [[BR]]
     231  * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr?  [[BR]]
     232
     233Revised design:  [[BR]]
     234 * High-speed nodes (fixed applications only)
     235 * Low-speed nodes:  (fixed or mobile applications)
     236
     237Current schedule:  [[BR]]
     238 * Mother bods due 3/25
     239 * metal cabinets being fabricated
     240 * some units by mid-April
     241 * all units by end of April
     242
     243Planned allocations:  [[BR]]
     244 * 8 high-speed:  1 to each site
     245 * 32 low speed:  3 to each site
     246
     247Sites:
     248 * Need to provide Ethernet switches
     249
     250
     251
     252=== 4.3)  Write and Introduce New Services:  Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc ===
     2534:15pm  [[br]]
     254Ivan Seskar  (Rutgers WINLAB) and Davide Pesavento (UCLA)  [[BR]]
     25510min  [[BR]]
     256
     257 * Multiple Base-Station Mgmt Srvc:  [[BR]]
     258
     259 * 1)  Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+;  additional updates coming  [[BR]]
     260  * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring  [[BR]]
     261  * Due:  ?  [[BR]]
     262
     263 *  2)  New WiMAX RF AggMgr for Airspan base station  [[BR]]
     264  * Provides configuration, to replace Netspan;  now running  [[BR]]
     265  * Provides node authorization, and measurements per client  [[BR]]
     266  * First version due:  12/15/12 [[BR]]
     267  * Could BBN, NYU Poly begin testing early version, to replace Netspan?    [[BR]]
     268  * Could early version be shipped to sites on yellow node, with OMF/OML?   [[BR]]
     269
     270 *  3)  Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API  [[BR]]
     271  * Should be useful for handover/multi-homing functions:  shared white list of MS, allowed to connect to one BS or another  [[BR]]
     272  * What other features are needed?  [[BR]]
     273  * First version due:  3/15/13  [[BR]]
     274
     275 * Data-path GW Srvc:  [[BR]]
     276  * Bridges each base station to global datapath  [[BR]]
     277  * Includes CLICK router (two types) [[BR]]
     278  * Includes OpenV switch  (open-source OF) [[BR]]
     279  * Should be useful for handover/multi-homing functions [[BR]]
     280  * First version due:  3/15/13  [[BR]]
     281  * Could there be an earlier version, that provides basic functions, and be manually configured? 
     282  * Could BBN, NYU Poly begin testing early version?    [[BR]]
     283  * Could early version be shipped to sites on yellow node?   [[BR]]
     284 
     285What are next steps?   [[BR]]
     286 * Finalize features for WiMAX RF AggMgr releases  (due 11/15/12) [[BR]]
     287 * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]]
     288 * 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]]
     289 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     290 * Finalize features for Data-path GW Srvc releases (due 11/15/12)  [[BR]]
     291 * Establish delivery schedule for Data-path GW Srvc releases [[BR]]
     292 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     293
     294
     295Current design and schedule:  [[BR]]
     296 * See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/gec16-wimaxrf%20%5BRead-Only%5D.pdf  slides]
     297 * Airspan config completed, need to be tested;  Manu will assist
     298 * NEC config in progress
     299 * Client registration in progress;  needs to be done by end of April
     300 * Ivan has updated for OMF 5.4
     301
     302Recommendations for sites:  [[BR]]
     303
     304
     305
     306=== 4.4)  Support Central Monitoring by Rutgers WINLAB ===
     3074:25pm  [[BR]]
     308Manu Gosain (GPO), Ivan Seskar (WINLAB)  [[BR]]
     3090min  [[BR]]
     310
     311Current status: [[BR]]
     312 * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Monitoring Dashboard] 
     313
     314Next steps:  [[BR]]
     315 * Remaining sites should connect, when have upgraded their WiMAX RF AggMgr.
     316
     317=== 4.5)  Write and Introduce Mobility/Handover/Multi-homing Services  ===
     3184:25pm  [[BR]]
     319Parmesh Ramanathan  (Wisconsin)  [[BR]]
     3208min  [[BR]]
     321
     322 * Projects requiring handover include:  Clemson, Wayne State, Wisconsin and UCLA.    [[BR]]
     323 * Projects that can contribute handover technology include:  Rutgers WINLAB and Wisconsin.  [[BR]]
     324 * Also, commercial handover technology available from Airspan.  (Gregg Tome (Airspan))  [[BR]]
     325
     326 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx  slides]  [[BR]]
     327
     328 * Layer 2 handoff
     329  * Minimal:  Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS  [[BR]]
     330  * Better:  Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2  [[BR]]
     331  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     332
     333 * Layer 3 handoff
     334  * Minimal:  Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection
     335  [[BR]]
     336  * 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]]
     337  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     338
     339 * Suggested steps:    [[BR]]
     340  1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]]
     341  2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]]
     342  3) Support new Layer 3 solutions like Mobility First? [[BR]]
     343  4) Demonstrate heterogeneous network handovers [[BR]]
     344
     345What are next steps?   [[BR]]
     346 * Better define proposed configurations 1) and 2) (due 11/15/12)  [[BR]]
     347 * Review with other interested projects  [[BR]]
     348 * Understand proposed Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc, and how they could be used in the implementation  [[BR]]
     349 * Understand how Yellow Nodes could be used in the implementation  [[BR]]
     350 * Understand how Android handsets could be used in the implementation  [[BR]]
     351 * Consider potential uses of WiScape Measurement Framework  [[BR]]
     352 * With other projects, define a workplan  (due 12/15/12)  [[BR]]
     353
     354Current status:  [[BR]]
     355 * Have defined the 2 approaches;  see [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/handover_parmesh.pptx  slides]
     356 * Config 1 has been tested.
     357 * Ready to test Config 2 when Clemson has at least 2 base stations on-the-air
     358
     359=== 4.6)  Consider WiScape Measurement Framework ===
     3604:33pm  [[BR]]
     361Suman Banerjee (Univ Wisc)  [[BR]]
     3622min [[BR]]
     363
     364 * Overview of current functions  [[BR]]
     365  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf  slides]  [[BR]]
     366  * A data measurement framework with APIs, that the clients and the measurement server expose  [[BR]]
     367  * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server  [[BR]]
     368  * Measurement include latency, loss, throughput, TCP or UDP  [[BR]]
     369  * Provides feedback to network selection  [[BR]]
     370  * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php  link to WiScape]  [[BR]]
     371
     372What are next steps?   [[BR]]
     373 * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution  [[BR]]
     374
     375Current status:  [[BR]]
     376 * See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides]
     377 * Mobility Services engine working, and has been tested.
     378
     379=== 4.7)  Add WiFi AP to Support Multi-Homing ===
     3804:35pm  [[BR]]
     381Manu Gosain (GPO), Ivan Seskar (WINLAB)  [[BR]]
     3820min  [[BR]]
     383
     384Approach: [[BR]]
     385 * Install yellow node, and use to support WiFi AP
     386
     387Uses:   [[BR]]
     388 * MobilityFirst testing. 
     389
     390=== 4.8)  Acquire and Add Android Handsets ===
     3914:35pm  [[BR]]
     392Derek Meyer (Univ Wisconsin)[[BR]]
     3935min  [[BR]]
     394
     395
     396 * Summary of discussions with Sprint about unlocked HTC Evo handset  [[BR]]
     397  * 3-way NDA was signed  [[BR]]
     398  * Sprint has subcontractor who handles such purchases: contact is ? [[BR]]
     399  * Many handsets in warehouse, such as HTC Evo 4G;  approx $300 per handset[[BR]]
     400  * Must be unlocked by subcontractor, so can register with GENI network;  need to provide config to subcontractor (done by Ivan)[[BR]]
     401  * Must be sure can download Android apps[[BR]]
     402
     403What are next steps?   [[BR]]
     404 * Working with other projects, establish how many handsets are needed at which sites   [[BR]]
     405 * Consider how to provide handsets to projects no longer supported by the GPO  [[BR]]
     406 * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices  (due 12/1/12) [[BR]]
     407 * Get and check samples?  [[BR]]
     408 * Verify operation, and loading of apps [[BR]]
     409 * Deliver handsets to other projects  (due 1/15/13)  [[BR]]
     410 * Support use by other projects  [[BR]]
     411 * Maintain relationship with WSA Distributing  [[BR]]
     412
     413
     414Current status:  [[BR]]
     415 * Still working with WSA;  have received a handset, but does not work on GENI network
     416 * Next:  sending rep a table of frequencies
     417 * Next"  send rep an "xml profile", previously used
     418
     419=== 4.9)  Add Vehicular Mobile Stations Based on Yellow Node ===
     4204:40pm  [[BR]]
     421Giovanni Pau (UCLA) and Ivan Seskar (WINLAB)  [[BR]]
     4220min  [[BR]]
     423
     424Approach: [[BR]]
     425 * Install yellow node, and use to support WiMAX modems
     426
     427Uses:   [[BR]]
     428 * Vehicular mobility tests
     429
     430Next:
     431 * Hongwei Zhang (Wayne State Univ) will take lead
     432
     433
     434=== 4.10)  Integrate and Introduce GIMI tools ===
     4354:40pm  [[BR]]
     436Fraida Fund  (NYU Poly)  [[BR]]
     4375min
     438
     439[http://wimax.orbit-lab.org/wiki/WiMAX/GIMISetup  GIMI Setup]  [[BR]]
     440
     441[http://wimax.orbit-lab.org/wiki/WiMAX/GIMIUse  GIMI Use]  [[BR]]
     442
     443=== 4.11) Add OMF/OML to WiMAX sites, and Make WiMAX Sites Accessible to Experimenters ===
     4444:45pm  [[BR]]
     445Fraida Fund (NYU Poly), Manu Gosain (GPO), Derek Meyer (Wisconsin), [[BR]]
     4460min  [[BR]]
     447
     448 * Equip a WiMAX site with full OMF/OML capabilities, installing on VMs  [[BR]]
     449 * Include Login Service for Remote Users [[BR]]
     450
     451 * NYU Poly configuration:  [[BR]]
     452
     453 * 1) physical host acting as base station controller, runs the asn-gw and wimaxrf AM. [[BR]]
     454  * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
     455  * 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]]
     456  * 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]]
     457
     458 * 2) physical host running OMF 5.3 AM, EC, and some other services that are useful for the testbed. [[BR]]
     459  * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
     460  * It has Ethernet connections to NYU-Poly network (internet) and OMF control network.  [[BR]]
     461  * 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]]
     462
     463 * 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]]
     464  * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]]
     465
     466 * Our testbed nodes are scattered throughout several CS labs and research areas (not part of our group).  [[BR]]
     467  * 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]]
     468  * We do have an openflow switch that we plan to deploy somewhere at some point. [[BR]]
     469
     470
     471
     472
     473 * BBN experience  (need summary)  [[BR]]
     474
     475 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/vmsetup_at_uwmadison.pdf Wisconsin configuration] [[BR]]
     476
     477 * All services are running on the same physical machine. [[BR]]
     478  * HP server that came with the base station.  [[BR]]
     479  * The base OS is Debian and virtual machines using for the services (Virtualbox)  [[BR]]
     480
     481 * Physical machine network connections: [[BR]]
     482  * Eth0 (128.105.22.xxx): University network (internet) [[BR]]
     483  * Eth1 (10.3.8.126): Network to IDU of base station [[BR]]
     484  * Eth2 (10.0.0.1): Control network for omf [[BR]]
     485  * Eth3: Connected to openflow (physically, but not enabled until we can get a vlan tag to GENI backbone) [[BR]]
     486
     487 * Base operating system:  Debian [[BR]]
     488
     489 * Virtualbox guests: [[BR]]
     490  * 1.  Ubuntu 9.04 ->  aggmgr 5.2 ->  wimaxrf service [[BR]]
     491  * Eth0 (128.105.22.xxx):  bridged interface to university network [[BR]]
     492  * Eth1(10.3.8.254):  bridged interface to base station network [[BR]]
     493
     494  * 2.  Ubuntu 10.04 ->  aggmgr 5.3 ->  cmcStub, Frisbee, inventory, pxe, result, saveimage [[BR]]
     495  * Also expctl, resctl, and xmpp on same machine [[BR]]
     496  * Eth0 (128.105.22.xxx): bridged interface to university network [[BR]]
     497  * Eth1 (10.0.0.200): bridged interface to control network [[BR]]
     498
     499
     500
     501 * Coming:  plan to federate with ProtoGENI cluster  [[BR]]
     502  *  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]]
     503  *  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]]
     504
     505Current status:
     506 *  [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.6GENIWiMAXSiteExperimenterLoginInterfaces  Current Operational Site Experimenter Login Interfaces]  [[BR]]
     507
     508=== 4.12)  Connect WiMAX Sites to Persistent I2 Backbone Network, with IP Routing, to Support Multi-site Experiments ===
     5094:45pm  [[BR]]
     510Manu Gosain (GPO), Fraida Fund (NYU Poly), Ivan Seskar (WINLAB)  [[BR]]
     5110min  [[BR]]
     512
     513
     514* Connect a WiMAX site to the GENI I2 backbone network  [[BR]]
     515  * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]]
     516  * Add switch  [[BR]]
     517  * Connect switch to I2 backbone  [[BR]]
     518  * VLAN connections from each site to "L2 router" at WINLAB   [[BR]]
     519
     520[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide]  [[BR]]
     521
     522 * When can other WiMAX sites can be added?  [[BR]]
     523  * UCLA; has physical connection;  needs to configure;  when?  [[BR]]
     524  * Wisconsin;  when?  [[BR]]
     525  * Clemson;  when?  [[BR]]
     526  * UMass Amherst; has physical connection;  needs to configure;  when?  [[BR]]
     527
     528 * How is core network configured to support multi-site experiments?   [[BR]]
     529
     530 * How is new Data-path GW Srvc use at site to interface with core network? [[BR]]
     531
     532What are next steps?  (Manu Gosain)  [[BR]]
     533 * Establish planned configuration  (due 11/15/12) [[BR]]
     534 * Establish plan with schedule to connect all sites  (due 11/15/12) [[BR]]
     535 * Track connection of sites, and assist them as needed  [[BR]]
     536
     537Current status:
     538 *  [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.7GENIWiMAXSiteBackboneConnections  Current Operational Site Backbone Connections]  [[BR]]
     539
     540
     541
     542== 5)  Status of GENI WiMAX site deployments ==
     5434:45pm  [[BR]]
     544Manu Gosain (GPO) and members of site teams [[BR]]
     54515min  [[BR]]
     546
     547[http://groups.geni.net/geni/wiki/WiMAXSiteDeployments  Current status of GENI WiMAX site deployments]  [[BR]]
     548
     549=== Univ Wisconsin at Madison ===
     550
     551Suman Bannerjee:  [[BR]]
     552See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides]  [[BR]]
     553Airspan on-the-air, throughput and range evaluated  [[BR]]
     554Used by undergrad course, 80 students  [[BR]]
     555
     556=== Wayne State ===
     557
     558Hongwei Zhang:  [[BR]]
     559See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/version%203_GEC16%20Status_WayneSateU.ppt  slides]  [[BR]]
     560x2 Airspan operating  [[BR]]
     561More at [http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Developers#WiMAXPrototypinginMetroDetroit  GEC16 demo]  [[BR]]
     562
     563=== Michigan ===
     564
     565Mehrdad Moradi:  [[BR]]
     566Base station has been repaired, but still some problems.  [[BR]]
     567
     568=== Drexel ===
     569
     570Ryan Measel:  [[BR]]
     571x2 Airspan arrived  [[BR]]
     572Waiting for site engineering work, before they can be installed  [[BR]]
     573Next:  temporarily install with attenuator  [[BR]]
     574  [[BR]]
     575=== Clemson ===
     576
     577KC Wang:  [[BR]]
     578x1 Airspan on-the-air  [[BR]]
     579x2 Airspan need repair  [[BR]]
     580
     581
     582== 6)  GENI WiMAX Experiments, Demos and Tutorials ==
     583
     584=== 6.1)  Lab Experiments to Teach Wireless Basics ===
     5855:00pm  [[BR]]
     586Thanasis Korakis  (NYU Poly)  [[BR]]
     5870min  [[BR]]
     588
     589 Funded project (1/13 - 12/13) to define lab experiments for students to teach wireless basics  [[BR]]
     590 To be executed on GENI wireless sites, using both WiMAX and WiFi  [[BR]]
     591 Overview and status [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/NYUPolyWirelessLab.pptx slides] [[BR]]
     592
     593What are next steps?   [[BR]]
     594 *  Early versions of lab experiments to be provided by GEC16 [[BR]]
     595
     596Current status?  [[BR]]
     597
     598==== NYU Poly ====
     599
     600See [http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Developers#WiMAXatNYU-Poly  demo at GEC16]
     601
     602==== Univ Wisconsin at Madison ====
     603
     604See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/banerjee-gec16.pptx  slides]
     605
     606==== Columbia Univ ====
     607
     608See [http://groups.geni.net/geni/wiki/Experiments#WiMAXintheClassroomDesigningaCellularNetworkingHands-onLab  paper] at Second GENI Research and Educational Experiment Workshop (GREE2013)
     609
     610=== 6.2)  Multiple Site Experiment:  Mobility First ===
     6115:00pm [[BR]]
     612Kiran Nagaraja (WINLAB)  [[BR]]
     6130min  [[BR]]
     614
     615GEC14 presentation:  [[BR]]
     616
     617[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MF-GEC12-PlenaryDemo-10-3-2011.pdf  slides] [[BR]]
     618
     619Overview of current Mobility First multiple-site experiment. [[BR]]
     620
     621What additions are needed?  [[BR]]
     6221)  Add WiFi AP to each site.  [[BR]]
     6232)  L2 path from MS to core  [[BR]]
     624
     625Experiment done without human intervention, by using x2 MAC addresses, and emulating packet loss to fake mobility.  [[BR]]
     626Consider these as possible sites by GEC13:  WINLAB;  BBN;  NYU Poly;  UCLA;  Colorado.  [[BR]]
     627
     628Current plans?  [[BR]]
     629
     630=== 6.3)  WiMAX Tutorials at GEC16 ===
     6315:00pm
     632Organized by Fraida Fund  (NYU Poly)  [[BR]]
     6330min  [[BR]]
     634
     635[http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Tutorial  WiMAX Tutorials at GEC16]  [[BR]]
     636
     637
     638=== 6.4)  Wireless Demos at GEC16 ===
     6395:00pm
     6400min
     641
     642
     643===== Vertical Handoff Using OpenFlow =====
     644
     645This demonstration will show how OpenFlow, Open vSwitch, and the Floodlight controller can be used as a vertical handoff solution between different network interfaces. Traffic will be generated from a server application, and with the handoff solution, will be sent using various networking interfaces to a client. The client will receive the traffic from the server. The interfaces used on the server will be alternated to show the handoff process.
     646
     647Participants:
     648  * Ryan Izard, rizard@clemson.edu
     649
     650===== Network Coding on ProtoGENI for Vehicular Networks =====
     651
     652Network coding using ProtoGENI testbed will be demonstrated. By implementing network coding and multipath forwarding capabilities in the core network, this demo is designed for supporting efficient broadband data delivery in infrastructure-based vehicular networks at Clemson.
     653
     654Participants:
     655  * Ke Xu, kxu@clemson.edu
     656
     657===== Supporting !MobilityFirst in OpenFlow Based SDNs =====
     658
     659!MobilityFirst (clean slate FIA project) has some unique features such as a globally unique naming scheme (GUID), storage aware routing etc. In this demo, we use GENI resources to show that such experimental non IP features can be enabled using OpenFlow based SDNs, by writing appropriate control programs that handle them.
     660
     661Participants:
     662  * Aravind Krishnamoorthy, aravind.k90@rutgers.edu
     663
     664===== WiMAX Prototyping in Metro Detroit =====
     665
     666Our initial coverage measurement and the tools we have developed to facilitate the road tests will be presented. We will also show the OpenXC platform and its integration with GENI, which may well benefit Wireless Vehicular Networking by offering you more insights into your car's operation.
     667
     668Participants:
     669  * Yu Chen, yuchen.wayne@gmail.com
     670
     671===== Mobility Services Engine =====
     672
     673A Demonstration of the Mobility Services Engine (MSE). This will be a live demonstration of the MSE using a laptop client. We will highlight some of the measurement capabilities of the system.
     674
     675Participants:
     676  * Derek Meyer, dmeyer@cs.wisc.edu
     677
     678===== !MobilityFirst Network API use in Mobile Applications =====
     679
     680One of the key feature of the proposed !MobilityFirst protocol stack is the service flexibility, with particular emphasis on multicasting and anycasting. In the demo we will show how this network service features could be easily exploited to enhance the capabilities of mobile applications through the use of the network API.
     681
     682Participants:
     683  * Ivan Seskar, seskar@winlab.rutgers.edu
     684
     685===== WiMAX at NYU-Poly =====
     686
     687Demonstration of wireless lab exercises utilizing GENI WiMAX resources.
     688
     689Participants:
     690  * ffund01@students.poly.edu
     691
     692===== WiMAX DDoS Reverse Engineering =====
     693
     694Our WiMAX research involves analyzing the cross-layer affects of the system parameters used for the Bandwidth Contention Process. We are specifically looking at how these parameters affect a subscriber station's (SS) throughput, packet loss rates, and vulnerability to Distributed Denial of Service (DDoS) attacks. Software simulations use the NS-2 simulator and hardware simulations are being conducted on ORBIT. The parameters investigated are request retires, backoff start, backoff end and frame duration.
     695
     696Participants:
     697  * Katherine Cameron, kccamer@clemson.edu
     698
     699== 7) Adjourn ==
     7005:00pm  [[BR]]
     701
     702
     703== WiMAX BoF Dinner ==
     704
     705Please join us for a [http://groups.geni.net/geni/wiki/GEC16Agenda/BoF_WiMAX  WiMAX BoF dinner] on Wednesday evening. Please indicate on this poll, if you will be attending.  [[BR]]
     706
     707
     708
     709== References ==
     710
     711
     712
     713=== R1) Airspan Profile-C Base Station, with Associated Hardware and Software ===
     714Ivan Seskar (WINLAB) and Harry Mussman (GPO) [[BR]]
     715
     716 
     717a)  Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     718NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     719WINLAB and the GPO have decided to purchase base stations from Airspan, a commercial company pursuing target customers such as universities and small carriers. [[BR]]
     720For 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]]
     721WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]]
     722
     723[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf  Airspan brochure][[BR]]
     724[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf  MacroMAXe Product Specification]  [[BR]] 
     725[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]]
     726
     727b)  Rutgers will provide a kit including: [[BR]]
     728Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]]
     729  Choice of frequency:   [[BR]]
     730  (2510 Lo:  2496MHz to 2570MHz)   [[BR]]
     731  (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     732  (2510 Hi:  2620MHz to 2690MHz)  [[BR]]
     733  (3650: 3650MHz to 3700MHz)]  [[BR]]
     734
     735NOTE:  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!
     736
     737Sector antenna, with x4 RF jumper cables [[BR]]
     7382x4 MIMO, supported by base station and antenna [[BR]]
     739GPS antenna, with surge suppressor and cable [[BR]]
     740DC power cable, from base station unit (outside) to testbed (inside) [[BR]]
     741Network management software license, 1 per base station [[BR]]
     742
     743
     744c)  Campus will need to provide: [[BR]]
     745Pole for mounting [[BR]]
     746DC power supply (-48v, approx 300W) [[BR]]
     747Ethernet 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]]
     748Windows server to host network management software [[BR]]
     749Linux server to host OMF software [[BR]]
     750Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]]       
     751
     752d)  Additional kits can be purchased from Airspan [[BR]]
     753  Price is approximately $15,000. [[BR]]
     754 
     755e)  It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]]
     756  Thus, campus site might be able to add additional sectors, at no cost. [[BR]]
     757  Planning for next year will be done later this year. [[BR]]
     758  Consider including additional sectors within your technical plan right away.   [[BR]]
     759
     760f)  Note:  Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]]
     761  Somewhat reduced performance/range. [[BR]]
     762  Approximately half the cost [[BR]]
     763
     764g)  Airspan indicates that their sector antenna provides:[[BR]]
     765  A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]]
     766  Four internal elements, to support 2x4 MIMO.[[BR]]
     767  Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]]
     768
     769h)  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]]
     770  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]]
     771  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]]
     772  [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf  MacroMAXe Configuration Guide][[BR]]
     773
     774i)  Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]]
     775  In this case, the base station unit operates with IP at the interface.  [[BR]]
     776
     777
     778j)  Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b  link]  [[BR]]
     779
     780
     781
     782=== R2)  Netspan Network Management System for Airspan Base Station ===
     783Manu Gosain  (GPO)  [[BR]]
     784
     785 * Suggest:  add Netspan system at each site with Airspan base station  [[BR]]
     786 * Requires:  Windows server [[BR]]
     787 * Use: setup of Netspan base station to provide basic functions  [[BR]]
     788
     789[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides]  [[BR]]
     790
     791[http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions   installation instructions]  [[BR]]
     792
     793 * Coming: replace with new WiMAX RF AggMgr  [[BR]]