=== Extended GENI WiMAX Capabilities === GENI WiMAX capabilities were extended by Sol 3 projects, including the addition of additional sites and the introduction of Airspan base stations. The following summarize the configuration of GENI WiMAX sites at the end of Spiral 4, and the types of WiMAX experiments these sites could support: [[BR]] [http://groups.geni.net/geni/attachment/wiki/WiMAXArchitectureOverview/020112b_ExtendingGENI_TridentCom2012.doc document] [[BR]] [http://groups.geni.net/geni/attachment/wiki/WiMAXArchitectureOverview/032312_WiMAXExtensionOverview.pptx slide] [[BR]] === 4.3) WiScape Measurement Framework === 4:20pm [[BR]] Suman Banerjee (Univ Wisc) * Overview of current functions [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf slides] [[BR]] * A data measurement framework with APIs, that the clients and the measurement server expose [[BR]] * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server [[BR]] * Measurement include latency, loss, throughput, TCP or UDP [[BR]] * Provides feedback to network selection [[BR]] * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php link to WiScape] [[BR]] What are next steps? [[BR]] * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution [[BR]] === 4.4) Mobility/handover/multi-homing services === 4:25pm [[BR]] Parmesh Ramanathan (Wisconsin) [[BR]] * Projects requiring handover include: Clemson, Wayne State, Wisconsin and UCLA. [[BR]] * Projects that can contribute handover technology include: Rutgers WINLAB and Wisconsin. [[BR]] * Also, commercial handover technology available from Airspan. (Gregg Tome (Airspan)) [[BR]] * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx slides] [[BR]] * Layer 2 handoff * Minimal: Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS [[BR]] * Better: Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2 [[BR]] * Need: suggested configurations, estimates of required software and level of effort [[BR]] * Layer 3 handoff * Minimal: Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection [[BR]] * 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]] * Need: suggested configurations, estimates of required software and level of effort [[BR]] * Suggested steps: [[BR]] 1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]] 2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]] 3) Support new Layer 3 solutions like Mobility First? [[BR]] 4) Demonstrate heterogeneous network handovers [[BR]] What are next steps? [[BR]] * Better define proposed configurations 1) and 2) (due 11/15/12) [[BR]] * Review with other interested projects [[BR]] * Understand proposed Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc, and how they could be used in the implementation [[BR]] * Understand how Yellow Nodes could be used in the implementation [[BR]] * Understand how Android handsets could be used in the implementation [[BR]] * Consider potential uses of WiScape Measurement Framework [[BR]] * With other projects, define a workplan (due 12/15/12) [[BR]] === 4.5) Mobility/handover/multi-homing plans === 4:30pm [[BR]] All [[BR]] * What is the best roadmap to useful mobility/handover/multi-homing services based on planned and available platforms and software? [[BR]]