| 25 | |
| 26 | == 1) Introductions == |
| 27 | |
| 28 | == 2) Spiral 6 Goals == |
| 29 | |
| 30 | a) Where necessary, complete deployments planned for Spiral 4: [[BR]] |
| 31 | Get experimental frequency from the FCC, that does not interfere with Clearwire services [[BR]] |
| 32 | Install Airspan base station(s), with local NetSpan management system [[BR]] |
| 33 | Optional when multiple cells: backhaul control and data traffic to central equipment site [[BR]] |
| 34 | Add OMF/OML structures, including LoginService [[BR]] |
| 35 | Connect via switch to I2 backbone, via OF switches if there [[BR]] |
| 36 | WiFi access point for dual-homing operating on custom PC node [[BR]] |
| 37 | Vehicular mobile station operating on custom PC node [[BR]] |
| 38 | Fixed “mobile station” for remote experimenters operating on custom PC node [[BR]] |
| 39 | |
| 40 | b) Plan local research experiments for Spiral 5 [[BR]] |
| 41 | Focus on goals, configurations, steps [[BR]] |
| 42 | Identify necessary extended site capabilities needed in Spiral 5 [[BR]] |
| 43 | |
| 44 | c) Complete deployments of necessary extended site capabilities needed in Spiral 5, from this list of options: (technology supplier or coordinator shown) [[BR]] |
| 45 | Additional base station (Rutgers WINLAB) [[BR]] |
| 46 | Custom PC nodes ("yellow nodes") (Rutgers WINLAB) [[BR]] |
| 47 | Login Service plus OMF/OML services operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 48 | Connection to I2 (coordinated by BBN) [[BR]] |
| 49 | GIMI I&M services (UMass Amherst/NYU Poly) [[BR]] |
| 50 | Multiple base-station management service operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 51 | Data-path gateway service operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 52 | Mobility/handover/multi-homing service (coordinated by Wisconsin/Clemson) [[BR]] |
| 53 | WiFi access point for dual-homing operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 54 | Vehicular mobile station operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 55 | Fixed “mobile station” for remote experimenters operating on custom PC node (Rutgers WINLAB) [[BR]] |
| 56 | Unlocked Android WiMAX/WiFi handsets. (Wisconsin) [[BR]] |
| 57 | |
| 58 | d) Support unified GENI operations: [[BR]] |
| 59 | Forward site monitoring information to the central monitoring server (Rutgers WINLAB) [[BR]] |
| 60 | Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]] |
| 61 | When necessary, do an “emergency stop” of your transmissions. [[BR]] |
| 62 | |
| 63 | e) Complete and support experiments: [[BR]] |
| 64 | Local research experiments [[BR]] |
| 65 | Experiments by remote experimenters, including those at tutorials [[BR]] |
| 66 | Classroom instruction experiments by students (NYU Poly) [[BR]] |
| 67 | Multi-site experiments, e.g., MobilityFirst (Rutgers WINLAB) [[BR]] |
| 68 | |
| 69 | f) Concern: how can we get all of this done? [[BR]] |
| 70 | Common platforms and services [[BR]] |
| 71 | Clear plans, good schedules [[BR]] |
| 72 | Close cooperation!! [[BR]] |
| 73 | |
| 74 | == 3) Engineering and Studies == |
| 75 | |
| 76 | |
| 77 | |
| 78 | === 3.1) Cooperate with Sprint === |
| 79 | |
| 80 | Ivan Seskar (WINLAB) and Manu Gosain (GPO)[[BR]] |
| 81 | |
| 82 | |
| 83 | * Sprint is operating both LTE and Wimax till end of 2015 |
| 84 | * Sprint acknowledges the master agreement signed formerly with Clearwire |
| 85 | * Sprint RF planning team is doing site surveys based on the wimax table at |
| 86 | http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.5GENIWiMAXSitesandContacts |
| 87 | |
| 88 | PLEASE UPDATE THIS PAGE |
| 89 | |
| 90 | |
| 91 | === 3.2) !SciWiNet === |
| 92 | |
| 93 | Jim Martin (Clemson Univ) [[BR]] |
| 94 | |
| 95 | |
| 96 | Discussions with Sprint and their partner, Arterra: [[BR]] |
| 97 | * Considering approach as discussed in earlier WiNTeB workshop |
| 98 | * Possible configuration, and cost, have been received. |
| 99 | * 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 |
| 100 | * How much of a research market would there be for this service? |
| 101 | * Another advantage: provides a path to utilize (commercial) LTE |
| 102 | * Enabling Android handsets acquired from kajeet technologies on Sciwinet |
| 103 | * Sciwinet tools that capture and report back handset connectivity data to central clemson data |
| 104 | [http://sciwinet.org/map Coverage SciWiNet] |
| 105 | |
| 106 | |
| 107 | |
| 108 | == 4) Tasks == |
| 109 | |
| 110 | === 4.1) Build and Add Custom PC "Yellow Nodes" to WiMAX sites === |
| 111 | |
| 112 | Ivan Seskar (WINLAB) [[BR]] |
| 113 | |
| 114 | |
| 115 | * These are "yellow nodes", introduced in ORBIT testbed [[BR]] |
| 116 | |
| 117 | * Can be used as: [[BR]] |
| 118 | * General fixed servers [[BR]] |
| 119 | * Support Multiple Base-Station Mgmt Srvc [[BR]] |
| 120 | * Support Data-Path GW Srvc [[BR]] |
| 121 | * Support OMF/OML and Login services [[BR]] |
| 122 | * Provide WiFi access points [[BR]] |
| 123 | * Act as fixed "mobile stations" [[BR]] |
| 124 | * Act as vehicular mobile station (option: 12v power supply) [[BR]] |
| 125 | |
| 126 | * Currently used by: Rutgers WINLAB; NYU Poly; BBN [[BR]] |
| 127 | |
| 128 | * What are next steps? [[BR]] |
| 129 | * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites [[BR]] |
| 130 | * Order parts (due 11/15/12) [[BR]] |
| 131 | * Assemble and deliver to sites (due 1/15/13) [[BR]] |
| 132 | * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr? [[BR]] |
| 133 | |
| 134 | Revised design: [[BR]] |
| 135 | * High-speed nodes (fixed applications only) |
| 136 | * Low-speed nodes: (fixed or mobile applications) |
| 137 | |
| 138 | Current schedule: [[BR]] |
| 139 | * All 32 nodes have been shipped |
| 140 | * testing complete at all sites |
| 141 | |
| 142 | Planned allocations: [[BR]] |
| 143 | * 8 high-speed: 1 to each site |
| 144 | * 24 low speed: 3 to each site |
| 145 | |
| 146 | Sites: |
| 147 | * Need to provide Ethernet switches |
| 148 | * Ubuntu Host to run Wimax-rf software |
| 149 | |
| 150 | |
| 151 | === 4.2) Write and Introduce New Services: Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc === |
| 152 | |
| 153 | Ivan Seskar (Rutgers WINLAB) and Davide Pesavento (UCLA) [[BR]] |
| 154 | |
| 155 | |
| 156 | * Multiple Base-Station Mgmt Srvc: [[BR]] |
| 157 | |
| 158 | * 1) Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+; additional updates coming [[BR]] |
| 159 | * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring [[BR]] |
| 160 | * Due: ? [[BR]] |
| 161 | |
| 162 | * 2) New WiMAX RF AggMgr for Airspan base station [[BR]] |
| 163 | * Provides configuration, to replace Netspan; now running [[BR]] |
| 164 | * Provides node authorization, and measurements per client [[BR]] |
| 165 | * Could BBN, NYU Poly begin testing early version, to replace Netspan? [[BR]] |
| 166 | * Could early version be shipped to sites on yellow node, with OMF/OML? [[BR]] |
| 167 | |
| 168 | * 3) Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API [[BR]] |
| 169 | * Should be useful for handover/multi-homing functions: shared white list of MS, allowed to connect to one BS or another [[BR]] |
| 170 | * What other features are needed? [[BR]] |
| 171 | * First version due: 3/15/13 [[BR]] |
| 172 | |
| 173 | * Data-path GW Srvc: [[BR]] |
| 174 | * Bridges each base station to global datapath [[BR]] |
| 175 | * Includes CLICK router (two types) [[BR]] |
| 176 | * Includes OpenV switch (open-source OF) [[BR]] |
| 177 | * Should be useful for handover/multi-homing functions [[BR]] |
| 178 | * First version due: 3/15/13 [[BR]] |
| 179 | * Could there be an earlier version, that provides basic functions, and be manually configured? |
| 180 | * Could BBN, NYU Poly begin testing early version? [[BR]] |
| 181 | * Could early version be shipped to sites on yellow node? [[BR]] |
| 182 | |
| 183 | What are next steps? [[BR]] |
| 184 | * Finalize features for WiMAX RF AggMgr releases (due 11/15/12) [[BR]] |
| 185 | * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]] |
| 186 | * 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]] |
| 187 | * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]] |
| 188 | * Finalize features for Data-path GW Srvc releases (due 11/15/12) [[BR]] |
| 189 | * Establish delivery schedule for Data-path GW Srvc releases [[BR]] |
| 190 | * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]] |
| 191 | |
| 192 | |
| 193 | Current design and schedule: [[BR]] |
| 194 | * See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/gec16-wimaxrf%20%5BRead-Only%5D.pdf slides] |
| 195 | * Airspan config completed, need to be tested; Manu will assist |
| 196 | * NEC config in progress |
| 197 | * Client registration in progress; needs to be done by end of April |
| 198 | * Ivan has updated for OMF 5.4 |
| 199 | |
| 200 | Recommendations for sites: [[BR]] |
| 201 | |
| 202 | |
| 203 | |
| 204 | === 4.3) Support GENI Monitoring architecture by Rutgers WINLAB === |
| 205 | |
| 206 | David Wiggins (GPO), Stephane Blais (GPO), Ivan Seskar (WINLAB) [[BR]] |
| 207 | |
| 208 | |
| 209 | Current status: [[BR]] |
| 210 | * [http://oml.orbit-lab.org:4040/tab/home_tab GENI WiMAX Site Monitoring Dashboard] |
| 211 | |
| 212 | Next steps: [[BR]] |
| 213 | * Final installation of Wimax-rf service will collect OML stats from the Base station |
| 214 | * Work with GPO monitoring team to submit data via new aggregator schema. |
| 215 | * Understand and develop local data collectors and submit data to Rutgers |
| 216 | |
| 217 | |
| 218 | |
| 219 | === 4.4) Create Template for WiMAX sites GENI Aggregate and Operator Pages === |
| 220 | |
| 221 | Manu Gosain (GPO) [[BR]] |
| 222 | |
| 223 | |
| 224 | * Sample Wimax aggregate template is defined here [http://groups.geni.net/geni/wiki/WimaxTemplateAggregate WiMAX template] |
| 225 | * Create aggregate pages for each WiMAX site |
| 226 | * Create operator facing pages for each WiMAX site http://groups.geni.net/geni/wiki/GENIRacksHome/Operators |
| 227 | |
| 228 | |
| 229 | === 4.5) Acquire and Add Android Handsets === |
| 230 | |
| 231 | Ivan Seskar (Rutgers University) [[BR]] |
| 232 | |
| 233 | |
| 234 | |
| 235 | * 15 handsets have been ordered and received via the Sprint MVNO arrangement |
| 236 | * Samsung galaxy S2 that runs android 4.1.2 Jelly bean |
| 237 | * Verify operation, and loading of apps by Rutgers [[BR]] |
| 238 | * 60 handsets procured by Rutgers |
| 239 | * Delivery of handsets and WiMAX gateways to project teams completed 6/18 [[BR]] |
| 240 | * Support use by other projects [[BR]] |
| 241 | * Maintain relationship with SciWiNet to use data plans that are in place with WSA for experiments [[BR]] |
| 242 | |
| 243 | |
| 244 | |
| 245 | === 4.6) Integration with GENI portal and making WiMAX Sites Accessible to Experimenters === |
| 246 | |
| 247 | Manu Gosain (GPO) [[BR]] |
| 248 | |
| 249 | |
| 250 | * Portal integration [[BR]] |
| 251 | * Include Login Service for Remote Users [[BR]] |
| 252 | * Orbit login enabled for all users on GENI Portal |
| 253 | * Portal accounts used by Wimax handoff tutorial at GEC 20 |
| 254 | * Instructions posted at [http://wimax.orbit-lab.org/wiki/WiMAX/27#LogintoOrbitWimaxResourcesviaGENIPortal Orbit-GENI login] |
| 255 | |
| 256 | |
| 257 | === 4.7) Connect WiMAX Sites to Persistent I2 Backbone Network using AL2S and Integration of GENI racks and Wimax Base station controllers === |
| 258 | |
| 259 | Manu Gosain (GPO) and Ivan Seskar (WINLAB) [[BR]] |
| 260 | |
| 261 | |
| 262 | * Connect a WiMAX site to the GENI I2 backbone network [[BR]] |
| 263 | * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]] |
| 264 | * Add switch [[BR]] |
| 265 | * Connect switch to I2 backbone [[BR]] |
| 266 | * VLAN connections from each site to "L2 router" at WINLAB [[BR]] |
| 267 | |
| 268 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide] [[BR]] |
| 269 | |
| 270 | * When can other WiMAX sites can be added? [[BR]] |
| 271 | * UCLA; has physical connection; needs to configure; when? [[BR]] |
| 272 | * Wisconsin; done [[BR]] |
| 273 | * Clemson; done via OpenGENI rack [[BR]] |
| 274 | * UMass Amherst; has physical connection; needs to configure; when? [[BR]] |
| 275 | |
| 276 | * How is core network configured to support multi-site experiments? [[BR]] |
| 277 | |
| 278 | * How is new Data-path GW Srvc use at site to interface with core network? [[BR]] |
| 279 | |
| 280 | What are next steps? (Manu Gosain) [[BR]] |
| 281 | * Use I2 AL2S service to create a single multi-point VLAN that encompasses all Wimax sites |
| 282 | * Connect the Wimax multi-site VLAN at each campus upstream to respective GENI rack |
| 283 | * GENI rack dataplane connectivity will be the cross-connect piece between AL2S and the wimax base station controller |
| 284 | |
| 285 | Current status: |
| 286 | * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.7GENIWiMAXSiteBackboneConnections Current Operational Site Backbone Connections] [[BR]] |
| 287 | |
| 288 | |
| 289 | |
| 290 | == 5) Status of GENI WiMAX site deployments == |
| 291 | |
| 292 | Manu Gosain (GPO) and members of site teams [[BR]] |
| 293 | |
| 294 | |
| 295 | [http://groups.geni.net/geni/wiki/WiMAXSiteDeployments Current status of GENI WiMAX site deployments] [[BR]] |
| 296 | |
| 297 | === Univ Wisconsin at Madison === |
| 298 | |
| 299 | Suman Bannerjee and Derek Meyer: [[BR]] |
| 300 | See [http://groups.geni.net/geni/attachment/wiki/GEC20Agenda/WiMAXDevs/Wisconsin-Wimax-Update.pdf slides] [[BR]] |
| 301 | GENI in the classroom [[BR]] |
| 302 | GENI WiMAX clients on GENI Backbone [[BR]] |
| 303 | Greenpacket WiMAX Modems [[BR]] |
| 304 | |
| 305 | === Wayne State === |
| 306 | |
| 307 | Hongwei Zhang: [[BR]] |
| 308 | See [http://groups.geni.net/geni/attachment/wiki/GEC16Agenda/WiMAX-Developers/version%203_GEC16%20Status_WayneSateU.ppt slides] [[BR]] |
| 309 | x2 Airspan operating [[BR]] |
| 310 | More at [http://groups.geni.net/geni/wiki/GEC16Agenda/WiMAX-Developers#WiMAXPrototypinginMetroDetroit GEC16 demo] [[BR]] |
| 311 | |
| 312 | |
| 313 | === Clemson === |
| 314 | |
| 315 | KC Wang: [[BR]] |
| 316 | x1 Airspan on-the-air [[BR]] |
| 317 | x2 Airspan need repair [[BR]] |
| 318 | |
| 319 | === Temple === |
| 320 | |
| 321 | Tigran N: [[BR]] |
| 322 | x3 Airspan on-the-air [[BR]] |
| 323 | Netspan instance over L2TP to rutgers [[BR]] |
| 324 | |
| 325 | |
| 326 | == 6) GENI WiMAX Experiments, Demos and Tutorials == |
| 327 | |
| 328 | === 6.1) Lab Experiments to Teach Wireless Basics === |
| 329 | |
| 330 | Thanasis Korakis and Fraida Fund(NYU Poly) [[BR]] |
| 331 | |
| 332 | |
| 333 | Current status? [[BR]] |
| 334 | |
| 335 | |
| 336 | == 7) Adjourn == |
| 337 | |
| 338 | |
| 339 | |
| 340 | == References == |
| 341 | |
| 342 | |
| 343 | |
| 344 | === R1) Airspan Profile-C Base Station, with Associated Hardware and Software === |
| 345 | Ivan Seskar (WINLAB) and Manu Gosain (GPO) [[BR]] |
| 346 | |
| 347 | |
| 348 | a) Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]] |
| 349 | NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]] |
| 350 | 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]] |
| 351 | 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]] |
| 352 | WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]] |
| 353 | |
| 354 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf Airspan brochure][[BR]] |
| 355 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf MacroMAXe Product Specification] [[BR]] |
| 356 | [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]] |
| 357 | |
| 358 | b) Rutgers will provide a kit including: [[BR]] |
| 359 | Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]] |
| 360 | Choice of frequency: [[BR]] |
| 361 | (2510 Lo: 2496MHz to 2570MHz) [[BR]] |
| 362 | (2510 Mid: 2560MHz to 2630MHz) [[BR]] |
| 363 | (2510 Hi: 2620MHz to 2690MHz) [[BR]] |
| 364 | (3650: 3650MHz to 3700MHz)] [[BR]] |
| 365 | |
| 366 | 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! |
| 367 | |
| 368 | Sector antenna, with x4 RF jumper cables [[BR]] |
| 369 | 2x4 MIMO, supported by base station and antenna [[BR]] |
| 370 | GPS antenna, with surge suppressor and cable [[BR]] |
| 371 | DC power cable, from base station unit (outside) to testbed (inside) [[BR]] |
| 372 | Network management software license, 1 per base station [[BR]] |
| 373 | |
| 374 | |
| 375 | c) Campus will need to provide: [[BR]] |
| 376 | Pole for mounting [[BR]] |
| 377 | DC power supply (-48v, approx 300W) [[BR]] |
| 378 | 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]] |
| 379 | Windows server to host network management software [[BR]] |
| 380 | Linux server to host OMF software [[BR]] |
| 381 | Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]] |
| 382 | |
| 383 | d) Additional kits can be purchased from Airspan [[BR]] |
| 384 | Price is approximately $15,000. [[BR]] |
| 385 | |
| 386 | e) It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]] |
| 387 | Thus, campus site might be able to add additional sectors, at no cost. [[BR]] |
| 388 | Planning for next year will be done later this year. [[BR]] |
| 389 | Consider including additional sectors within your technical plan right away. [[BR]] |
| 390 | |
| 391 | f) Note: Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]] |
| 392 | Somewhat reduced performance/range. [[BR]] |
| 393 | Approximately half the cost [[BR]] |
| 394 | |
| 395 | g) Airspan indicates that their sector antenna provides:[[BR]] |
| 396 | A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]] |
| 397 | Four internal elements, to support 2x4 MIMO.[[BR]] |
| 398 | Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]] |
| 399 | |
| 400 | 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]] |
| 401 | 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]] |
| 402 | 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]] |
| 403 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf MacroMAXe Configuration Guide][[BR]] |
| 404 | |
| 405 | i) Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]] |
| 406 | In this case, the base station unit operates with IP at the interface. [[BR]] |
| 407 | |
| 408 | |
| 409 | j) Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b link] [[BR]] |
| 410 | |
| 411 | |
| 412 | |
| 413 | === R2) Netspan Network Management System for Airspan Base Station === |
| 414 | Manu Gosain (GPO) [[BR]] |
| 415 | |
| 416 | * Suggest: add Netspan system at each site with Airspan base station [[BR]] |
| 417 | * Requires: Windows server [[BR]] |
| 418 | * Use: setup of Netspan base station to provide basic functions [[BR]] |
| 419 | |
| 420 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides] [[BR]] |
| 421 | |
| 422 | [http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions installation instructions] [[BR]] |
| 423 | |
| 424 | |