745 | | [http://oml.orbit-lab.org:4040/tab/home_tab GENI WiMAX Site Dashboard] [[BR]] |
746 | | |
747 | | [http://wimax.orbit-lab.org/wiki/WiMAX/27#a10.GENIWimaxSites GENI WiMAX Site Licenses] [[BR]] |
| 745 | |
| 746 | * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3GENICampusDeployments GENI WiMAX Site Information] [[BR]] |
| 747 | * [http://wimax.orbit-lab.org/wiki/WiMAX/27#a10.GENIWimaxSites GENI WiMAX Site Licenses] [[BR]] |
| 748 | |
| 749 | |
| 750 | * [http://oml.orbit-lab.org:4040/tab/home_tab GENI WiMAX Site Dashboard] [[BR]] |
| 751 | |
| 752 | What are next steps? [[BR]] |
| 753 | * Review information on site information and site dashboard pages, and finalize [[BR]] |
| 754 | * Establish process to add site information, then maintain and track [[BR]] |
| 755 | * Provide interface to GMOC and Clearwire [[BR]] |
| 756 | * Complete agreement with Clearwire [[BR]] |
| 757 | * Encourage all GENI sites to obtain experimental licenses [[BR]] |
| 758 | * Consider adding an "emergency stop" button, to be used by GMOC [[BR]] |
756 | | * Need to feed management data to centralized DB at WINLAB, for GENI-wide monitoring [[BR]] |
757 | | * Possible access to Clearwire, others. [[BR]] |
758 | | |
759 | | * 2) New WiMAX RF AggMgr for Airspan base station, to replace Netspan [[BR]] |
760 | | * Plan first version by GEC15 [[BR]] |
| 767 | * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring [[BR]] |
| 768 | * Due: ? [[BR]] |
| 769 | |
| 770 | * 2) New WiMAX RF AggMgr for Airspan base station [[BR]] |
| 771 | * Provides configuration, to replace Netspan; now running [[BR]] |
| 772 | * Provides node authorization, and measurements per client [[BR]] |
| 773 | * First version due: 12/15/12 [[BR]] |
| 774 | * Could BBN, NYU Poly begin testing early version, to replace Netspan? [[BR]] |
| 775 | * Could early version be shipped to sites on yellow node, with OMF/OML? [[BR]] |
771 | | |
772 | | |
773 | | === 4.3) Mobility services engine === |
| 788 | * Could there be an earlier version, that provides basic functions, and be manually configured? |
| 789 | * Could BBN, NYU Poly begin testing early version? [[BR]] |
| 790 | * Could early version be shipped to sites on yellow node? [[BR]] |
| 791 | |
| 792 | What are next steps? [[BR]] |
| 793 | * Finalize features for WiMAX RF AggMgr releases (due 11/15/12) [[BR]] |
| 794 | * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]] |
| 795 | * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]] |
| 796 | * Finalize features for Data-path GW Srvc releases (due 11/15/12) [[BR]] |
| 797 | * Establish delivery schedule for Data-path GW Srvc releases [[BR]] |
| 798 | * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]] |
| 799 | |
| 800 | === 4.3) WiScape Measurement Framework === |
777 | | * Overview of current functions and software [[BR]] |
778 | | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf slides] [[BR]] |
779 | | |
780 | | === 4.4) Mobility/handover services === |
| 804 | * Overview of current functions [[BR]] |
| 805 | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf slides] [[BR]] |
| 806 | * A data measurement framework with APIs, that the clients and the measurement server expose [[BR]] |
| 807 | * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server [[BR]] |
| 808 | * Measurement include latency, loss, throughput, TCP or UDP [[BR]] |
| 809 | * Provides feedback to network selection [[BR]] |
| 810 | * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php link to WiScape] [[BR]] |
| 811 | |
| 812 | What are next steps? [[BR]] |
| 813 | * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution [[BR]] |
| 814 | |
| 815 | === 4.4) Mobility/handover/multi-homing services === |
788 | | * Parmesh reports: student has started on process to find a good solution, will report at GEC15 [[BR]] |
789 | | |
790 | | [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx slides] [[BR]] |
| 823 | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx slides] [[BR]] |
| 824 | |
| 825 | * Layer 2 handoff |
| 826 | * Minimal: Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS [[BR]] |
| 827 | * Better: Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2 [[BR]] |
| 828 | * Need: suggested configurations, estimates of required software and level of effort [[BR]] |
| 829 | |
| 830 | * Layer 3 handoff |
| 831 | * Minimal: Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection |
| 832 | [[BR]] |
| 833 | * 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]] |
| 834 | * Need: suggested configurations, estimates of required software and level of effort [[BR]] |
| 835 | |
| 836 | * Suggested steps: |
| 837 | 1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet |
| 838 | 2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme |
| 839 | 3) Support new Layer 3 solutions like Mobility First? |
| 840 | 4) Demonstrate heterogeneous network handovers |
| 841 | |
| 842 | What are next steps? [[BR]] |
| 843 | * Better define proposed configurations 1) and 2) (due 11/15/12) [[BR]] |
| 844 | * Review with other interested projects [[BR]] |
| 845 | * Understand proposed Multiple Base-Station Mgmt Srvc and Data-Path GW Srvc, and how they could be used in the implementation [[BR]] |
| 846 | * Understand how Yellow Nodes could be used in the implementation [[BR]] |
| 847 | * Understand how Android handsets could be used in the implementation [[BR]] |
| 848 | * Consider potential uses of WiScape Measurement Framework [[BR]] |
| 849 | * With other projects, define a workplan (due 12/15/12) [[BR]] |
| 850 | |
819 | | * Need to refine design to balance functionality and cost [[BR]] |
820 | | * Rutgers WINLAB has parts list, will order parts and assemble [[BR]] |
821 | | * Rutgers WINLAB plans to deliver to sites by 1/15/13 [[BR]] |
822 | | * Start now: what nodes are needed at which sites [[BR]] |
| 879 | |
| 880 | What are next steps? [[BR]] |
| 881 | * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites [[BR]] |
| 882 | * Order parts (due 11/15/12) [[BR]] |
| 883 | * Assemble and deliver to sites (due 1/15/13) [[BR]] |
| 884 | * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr? [[BR]] |