67 | | === 2.2) New services: Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc === |
| 67 | |
| 68 | |
| 69 | === 2.2) Airspan Profile-C Base Station, with Associated Hardware and Software, including Netspan Network Management System === |
| 70 | Ivan Seskar (WINLAB) and Harry Mussman (GPO) [[BR]] |
| 71 | |
| 72 | |
| 73 | a) Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]] |
| 74 | NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]] |
| 75 | 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]] |
| 76 | 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]] |
| 77 | WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]] |
| 78 | |
| 79 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf Airspan brochure][[BR]] |
| 80 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf MacroMAXe Product Specification] [[BR]] |
| 81 | [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]] |
| 82 | |
| 83 | b) Rutgers will provide a kit including: [[BR]] |
| 84 | Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]] |
| 85 | Choice of frequency: [[BR]] |
| 86 | (2510 Lo: 2496MHz to 2570MHz) [[BR]] |
| 87 | (2510 Mid: 2560MHz to 2630MHz) [[BR]] |
| 88 | (2510 Hi: 2620MHz to 2690MHz) [[BR]] |
| 89 | (3650: 3650MHz to 3700MHz)] [[BR]] |
| 90 | |
| 91 | 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! |
| 92 | |
| 93 | Sector antenna, with x4 RF jumper cables [[BR]] |
| 94 | 2x4 MIMO, supported by base station and antenna [[BR]] |
| 95 | GPS antenna, with surge suppressor and cable [[BR]] |
| 96 | DC power cable, from base station unit (outside) to testbed (inside) [[BR]] |
| 97 | Network management software license, 1 per base station [[BR]] |
| 98 | |
| 99 | |
| 100 | c) Campus will need to provide: [[BR]] |
| 101 | Pole for mounting [[BR]] |
| 102 | DC power supply (-48v, approx 300W) [[BR]] |
| 103 | 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]] |
| 104 | Windows server to host network management software [[BR]] |
| 105 | Linux server to host OMF software [[BR]] |
| 106 | Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]] |
| 107 | |
| 108 | d) Additional kits can be purchased from Airspan [[BR]] |
| 109 | Price is approximately $15,000. [[BR]] |
| 110 | |
| 111 | e) It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]] |
| 112 | Thus, campus site might be able to add additional sectors, at no cost. [[BR]] |
| 113 | Planning for next year will be done later this year. [[BR]] |
| 114 | Consider including additional sectors within your technical plan right away. [[BR]] |
| 115 | |
| 116 | f) Note: Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]] |
| 117 | Somewhat reduced performance/range. [[BR]] |
| 118 | Approximately half the cost [[BR]] |
| 119 | |
| 120 | g) Airspan indicates that their sector antenna provides:[[BR]] |
| 121 | A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]] |
| 122 | Four internal elements, to support 2x4 MIMO.[[BR]] |
| 123 | Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]] |
| 124 | |
| 125 | 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]] |
| 126 | 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]] |
| 127 | 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]] |
| 128 | [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf MacroMAXe Configuration Guide][[BR]] |
| 129 | |
| 130 | i) Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]] |
| 131 | In this case, the base station unit operates with IP at the interface. [[BR]] |
| 132 | |
| 133 | |
| 134 | j) Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b link] [[BR]] |
| 135 | |
| 136 | |
| 137 | |
| 138 | * Suggest: add Netspan system at each site with Airspan base station [[BR]] |
| 139 | * Requires: Windows server [[BR]] |
| 140 | * Use: setup of Netspan base station to provide basic functions [[BR]] |
| 141 | |
| 142 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides] [[BR]] |
| 143 | |
| 144 | [http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions installation instructions] [[BR]] |
| 145 | |
| 146 | * Coming: replace with new WiMAX RF AggMgr [[BR]] |
| 147 | |
| 148 | |
| 149 | |
| 150 | === 2.3) Add "yellow nodes" to WiMAX Sites === |
| 151 | 4:45pm [[BR]] |
| 152 | Ivan Seskar (WINLAB) [[BR]] |
| 153 | |
| 154 | * These are "yellow nodes", introduced in ORBIT testbed [[BR]] |
| 155 | |
| 156 | * Can be used as: [[BR]] |
| 157 | * General fixed servers [[BR]] |
| 158 | * Support Multiple Base-Station Mgmt Srvc [[BR]] |
| 159 | * Support Data-Path GW Srvc [[BR]] |
| 160 | * Support OMF/OML and Login services [[BR]] |
| 161 | * Provide WiFi access points [[BR]] |
| 162 | * Act as fixed "mobile stations" [[BR]] |
| 163 | * Act as vehicular mobile station (option: 12v power supply) [[BR]] |
| 164 | |
| 165 | * Currently used by: Rutgers WINLAB; NYU Poly; BBN [[BR]] |
| 166 | |
| 167 | * How can these be provided to sites? [[BR]] |
| 168 | * One design to serve all needs [[BR]] |
| 169 | * Approximate cost: $800 - $1500 [[BR]] |
| 170 | |
| 171 | What are next steps? [[BR]] |
| 172 | * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites [[BR]] |
| 173 | * Order parts (due 11/15/12) [[BR]] |
| 174 | * Assemble and deliver to sites (due 1/15/13) [[BR]] |
| 175 | * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr? [[BR]] |
| 176 | |
| 177 | |
| 178 | === 2.4) New services: Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc === |
108 | | === 2.3) WiScape Measurement Framework === |
109 | | 4:20pm [[BR]] |
110 | | Suman Banerjee (Univ Wisc) |
111 | | |
112 | | * Overview of current functions [[BR]] |
113 | | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf slides] [[BR]] |
114 | | * A data measurement framework with APIs, that the clients and the measurement server expose [[BR]] |
115 | | * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server [[BR]] |
116 | | * Measurement include latency, loss, throughput, TCP or UDP [[BR]] |
117 | | * Provides feedback to network selection [[BR]] |
118 | | * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php link to WiScape] [[BR]] |
119 | | |
120 | | What are next steps? [[BR]] |
121 | | * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution [[BR]] |
122 | | |
123 | | === 2.4) Mobility/handover/multi-homing services === |
| 219 | |
| 220 | |
| 221 | |
| 222 | === 2.5) Add OMF/OML to WiMAX sites === |
| 223 | Fraida Fund (NYU Poly), Manu Gosain (GPO), Derek Meyer (Wisconsin), [[BR]] |
| 224 | |
| 225 | * Equip a WiMAX site with full OMF/OML capabilities, installing on VMs [[BR]] |
| 226 | * Include Login Service for Remote Users [[BR]] |
| 227 | |
| 228 | * NYU Poly configuration: [[BR]] |
| 229 | |
| 230 | * 1) physical host acting as base station controller, runs the asn-gw and wimaxrf AM. [[BR]] |
| 231 | * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]] |
| 232 | * 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]] |
| 233 | * 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]] |
| 234 | |
| 235 | * 2) physical host running OMF 5.3 AM, EC, and some other services that are useful for the testbed. [[BR]] |
| 236 | * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]] |
| 237 | * It has Ethernet connections to NYU-Poly network (internet) and OMF control network. [[BR]] |
| 238 | * 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]] |
| 239 | |
| 240 | * 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]] |
| 241 | * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]] |
| 242 | |
| 243 | * Our testbed nodes are scattered throughout several CS labs and research areas (not part of our group). [[BR]] |
| 244 | * 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]] |
| 245 | * We do have an openflow switch that we plan to deploy somewhere at some point. [[BR]] |
| 246 | |
| 247 | |
| 248 | |
| 249 | |
| 250 | * BBN experience (need summary) [[BR]] |
| 251 | |
| 252 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/vmsetup_at_uwmadison.pdf Wisconsin configuration] [[BR]] |
| 253 | |
| 254 | * All services are running on the same physical machine. [[BR]] |
| 255 | * HP server that came with the base station. [[BR]] |
| 256 | * The base OS is Debian and virtual machines using for the services (Virtualbox) [[BR]] |
| 257 | |
| 258 | * Physical machine network connections: [[BR]] |
| 259 | * Eth0 (128.105.22.xxx): University network (internet) [[BR]] |
| 260 | * Eth1 (10.3.8.126): Network to IDU of base station [[BR]] |
| 261 | * Eth2 (10.0.0.1): Control network for omf [[BR]] |
| 262 | * Eth3: Connected to openflow (physically, but not enabled until we can get a vlan tag to GENI backbone) [[BR]] |
| 263 | |
| 264 | * Base operating system: Debian [[BR]] |
| 265 | |
| 266 | * Virtualbox guests: [[BR]] |
| 267 | * 1. Ubuntu 9.04 -> aggmgr 5.2 -> wimaxrf service [[BR]] |
| 268 | * Eth0 (128.105.22.xxx): bridged interface to university network [[BR]] |
| 269 | * Eth1(10.3.8.254): bridged interface to base station network [[BR]] |
| 270 | |
| 271 | * 2. Ubuntu 10.04 -> aggmgr 5.3 -> cmcStub, Frisbee, inventory, pxe, result, saveimage [[BR]] |
| 272 | * Also expctl, resctl, and xmpp on same machine [[BR]] |
| 273 | * Eth0 (128.105.22.xxx): bridged interface to university network [[BR]] |
| 274 | * Eth1 (10.0.0.200): bridged interface to control network [[BR]] |
| 275 | |
| 276 | |
| 277 | |
| 278 | * Coming: plan to federate with ProtoGENI cluster [[BR]] |
| 279 | * 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]] |
| 280 | * 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]] |
| 281 | |
| 282 | |
| 283 | |
| 284 | |
| 285 | === 2.6) Connect WiMAX sites to I2 backbone network, to support multi-site experiments === |
| 286 | Manu Gosain (GPO), Fraida Fund (NYU Poly), Ivan Seskar (WINLAB) [[BR]] |
| 287 | |
| 288 | * Connect a WiMAX site to the GENI I2 backbone network [[BR]] |
| 289 | * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]] |
| 290 | * Add switch [[BR]] |
| 291 | * Connect switch to I2 backbone [[BR]] |
| 292 | * VLAN connections from each site to "L2 router" at WINLAB [[BR]] |
| 293 | |
| 294 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide] [[BR]] |
| 295 | |
| 296 | * When can other WiMAX sites can be added? [[BR]] |
| 297 | * UCLA; has physical connection; needs to configure; when? [[BR]] |
| 298 | * Wisconsin; when? [[BR]] |
| 299 | * Clemson; when? [[BR]] |
| 300 | * UMass Amherst; has physical connection; needs to configure; when? [[BR]] |
| 301 | |
| 302 | * How is core network configured to support multi-site experiments? [[BR]] |
| 303 | |
| 304 | * How is new Data-path GW Srvc use at site to interface with core network? [[BR]] |
| 305 | |
| 306 | What are next steps? (Manu Gosain) [[BR]] |
| 307 | * Establish planned configuration (due 11/15/12) [[BR]] |
| 308 | * Establish plan with schedule to connect all sites (due 11/15/12) [[BR]] |
| 309 | * Track connection of sites, and assist them as needed [[BR]] |
| 310 | |
| 311 | |
| 312 | === 2.7) Summary of GENI WiMAX Site Status === |
| 313 | Manu Gosain (GPO) [[BR]] |
| 314 | |
| 315 | |
| 316 | === 2.8) Mobility/handover/multi-homing services === |
160 | | === 2.5) Mobility/handover/multi-homing plans === |
161 | | 4:30pm [[BR]] |
162 | | All [[BR]] |
163 | | |
164 | | * What is the best roadmap to useful mobility/handover/multi-homing services based on planned and available platforms and software? [[BR]] |
165 | | |
166 | | |
167 | | === 2.6) Add "yellow nodes" to WiMAX Sites === |
168 | | 4:45pm [[BR]] |
169 | | Ivan Seskar (WINLAB) [[BR]] |
170 | | |
171 | | * These are "yellow nodes", introduced in ORBIT testbed [[BR]] |
172 | | |
173 | | * Can be used as: [[BR]] |
174 | | * General fixed servers [[BR]] |
175 | | * Support Multiple Base-Station Mgmt Srvc [[BR]] |
176 | | * Support Data-Path GW Srvc [[BR]] |
177 | | * Support OMF/OML and Login services [[BR]] |
178 | | * Provide WiFi access points [[BR]] |
179 | | * Act as fixed "mobile stations" [[BR]] |
180 | | * Act as vehicular mobile station (option: 12v power supply) [[BR]] |
181 | | |
182 | | * Currently used by: Rutgers WINLAB; NYU Poly; BBN [[BR]] |
183 | | |
184 | | * How can these be provided to sites? [[BR]] |
185 | | * One design to serve all needs [[BR]] |
186 | | * Approximate cost: $800 - $1500 [[BR]] |
187 | | |
188 | | What are next steps? [[BR]] |
189 | | * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites [[BR]] |
190 | | * Order parts (due 11/15/12) [[BR]] |
191 | | * Assemble and deliver to sites (due 1/15/13) [[BR]] |
192 | | * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr? [[BR]] |
193 | | |
194 | | |
195 | | === 2.7) Mobile Station using Android Handset === |
196 | | 4:55pm [[BR]] |
197 | | Derek Meyer (Univ Wisconsin)[[BR]] |
198 | | |
199 | | * Summary of discussions with Sprint about unlocked HTC Evo handset [[BR]] |
200 | | * 3-way NDA was signed [[BR]] |
201 | | * Sprint has subcontractor who handles such purchases: contact is ? [[BR]] |
202 | | * Many handsets in warehouse, such as HTC Evo 4G; approx $300 per handset[[BR]] |
203 | | * Must be unlocked by subcontractor, so can register with GENI network; need to provide config to subcontractor (done by Ivan)[[BR]] |
204 | | * Must be sure can download Android apps[[BR]] |
205 | | |
206 | | What are next steps? [[BR]] |
207 | | * Working with other projects, establish how many handsets are needed at which sites [[BR]] |
208 | | * Consider how to provide handsets to projects no longer supported by the GPO [[BR]] |
209 | | * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices (due 12/1/12) [[BR]] |
210 | | * Get and check samples? [[BR]] |
211 | | * Verify operation, and loading of apps [[BR]] |
212 | | * Deliver handsets to other projects (due 1/15/13) [[BR]] |
213 | | * Support use by other projects [[BR]] |
214 | | * Maintain relationship with WSA Distributing [[BR]] |
215 | | |
216 | | |
217 | | === 2.8) Options for Introducing LTE Equipment === |
| 353 | === 2.9) Options for Introducing LTE Equipment === |
255 | | === 2.9) Lab Experiments to Teach Wireless Basics === |
| 391 | === 2.10) Mobile Station using Android Handset === |
| 392 | 4:55pm [[BR]] |
| 393 | Derek Meyer (Univ Wisconsin)[[BR]] |
| 394 | |
| 395 | * Summary of discussions with Sprint about unlocked HTC Evo handset [[BR]] |
| 396 | * 3-way NDA was signed [[BR]] |
| 397 | * Sprint has subcontractor who handles such purchases: contact is ? [[BR]] |
| 398 | * Many handsets in warehouse, such as HTC Evo 4G; approx $300 per handset[[BR]] |
| 399 | * Must be unlocked by subcontractor, so can register with GENI network; need to provide config to subcontractor (done by Ivan)[[BR]] |
| 400 | * Must be sure can download Android apps[[BR]] |
| 401 | |
| 402 | What are next steps? [[BR]] |
| 403 | * Working with other projects, establish how many handsets are needed at which sites [[BR]] |
| 404 | * Consider how to provide handsets to projects no longer supported by the GPO [[BR]] |
| 405 | * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices (due 12/1/12) [[BR]] |
| 406 | * Get and check samples? [[BR]] |
| 407 | * Verify operation, and loading of apps [[BR]] |
| 408 | * Deliver handsets to other projects (due 1/15/13) [[BR]] |
| 409 | * Support use by other projects [[BR]] |
| 410 | * Maintain relationship with WSA Distributing [[BR]] |
| 411 | |
| 412 | === 2.11) Access to Commercial Broadband Services via MVNO Arrangements === |
| 413 | |
| 414 | === 2.12) Tutorials and GIMI Tools === |
| 415 | |
| 416 | |
| 417 | |
| 418 | |
| 419 | |
| 420 | |
| 421 | |
| 422 | |
| 423 | |
| 424 | |
| 425 | |
| 426 | |
| 427 | === 2.13) Lab Experiments to Teach Wireless Basics === |