| 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 === |
| | 93 | * Sprint is operating both LTE and Wimax till end of 2015 |
| | 94 | * Sprint acknowledges the master agreement signed formerly with Clearwire |
| | 95 | * Sprint RF planning team is doing site surveys based on the wimax table at |
| | 96 | http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3.5GENIWiMAXSitesandContacts |
| | 97 | |
| | 98 | PLEASE UPDATE THIS PAGE |
| | 99 | |
| | 100 | |
| | 101 | === 3.2) SciWiNet === |
| 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 |
