| 9 | |
| 10 | |
| 11 | |
| 12 | === 4.3) WiScape Measurement Framework === |
| 13 | 4:20pm [[BR]] |
| 14 | Suman Banerjee (Univ Wisc) |
| 15 | |
| 16 | * Overview of current functions [[BR]] |
| 17 | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf slides] [[BR]] |
| 18 | * A data measurement framework with APIs, that the clients and the measurement server expose [[BR]] |
| 19 | * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server [[BR]] |
| 20 | * Measurement include latency, loss, throughput, TCP or UDP [[BR]] |
| 21 | * Provides feedback to network selection [[BR]] |
| 22 | * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php link to WiScape] [[BR]] |
| 23 | |
| 24 | What are next steps? [[BR]] |
| 25 | * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution [[BR]] |
| 26 | |
| 27 | === 4.4) Mobility/handover/multi-homing services === |
| 28 | 4:25pm [[BR]] |
| 29 | Parmesh Ramanathan (Wisconsin) [[BR]] |
| 30 | |
| 31 | * Projects requiring handover include: Clemson, Wayne State, Wisconsin and UCLA. [[BR]] |
| 32 | * Projects that can contribute handover technology include: Rutgers WINLAB and Wisconsin. [[BR]] |
| 33 | * Also, commercial handover technology available from Airspan. (Gregg Tome (Airspan)) [[BR]] |
| 34 | |
| 35 | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx slides] [[BR]] |
| 36 | |
| 37 | * Layer 2 handoff |
| 38 | * Minimal: Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS [[BR]] |
| 39 | * Better: Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2 [[BR]] |
| 40 | * Need: suggested configurations, estimates of required software and level of effort [[BR]] |
| 41 | |
| 42 | * Layer 3 handoff |
| 43 | * Minimal: Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection |
| 44 | [[BR]] |
| 45 | * 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]] |
| 46 | * Need: suggested configurations, estimates of required software and level of effort [[BR]] |
| 47 | |
| 48 | * Suggested steps: [[BR]] |
| 49 | 1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]] |
| 50 | 2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]] |
| 51 | 3) Support new Layer 3 solutions like Mobility First? [[BR]] |
| 52 | 4) Demonstrate heterogeneous network handovers [[BR]] |
| 53 | |
| 54 | What are next steps? [[BR]] |
| 55 | * Better define proposed configurations 1) and 2) (due 11/15/12) [[BR]] |
| 56 | * Review with other interested projects [[BR]] |
| 57 | * Understand proposed Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc, and how they could be used in the implementation [[BR]] |
| 58 | * Understand how Yellow Nodes could be used in the implementation [[BR]] |
| 59 | * Understand how Android handsets could be used in the implementation [[BR]] |
| 60 | * Consider potential uses of WiScape Measurement Framework [[BR]] |
| 61 | * With other projects, define a workplan (due 12/15/12) [[BR]] |
| 62 | |
| 63 | |
| 64 | === 4.5) Mobility/handover/multi-homing plans === |
| 65 | 4:30pm [[BR]] |
| 66 | All [[BR]] |
| 67 | |
| 68 | * What is the best roadmap to useful mobility/handover/multi-homing services based on planned and available platforms and software? [[BR]] |