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