IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Media Independent Mesh Networks Date Submitted: March, 2009 Presented at IEEE session #31 in Vancouver Authors or Source(s): Albert Vidal (i2CAT) Albert Banchs(Universidad Carlos III de Madrid) Antonio de la Oliva (Universidad Carlos III de Madrid) Bernd Gloss (Alcatel-Lucent) Burak Simsek (Fraunhofer Institute) Frank Zdarsky (NEC) Telemaco Melia (Alcatel-Lucent) Xavier Perez Costa(NEC) Abstract: An introduction to media independent mesh networks with IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards DevelopmentSection 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards DevelopmentSection 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6 Overview Motivation and Objective Scenarios Extensions Extended Semantics Extended Functionalities Related work CARMEN Proposal Motivation Mesh networks are being deployed and there are already many commercial products Cisco(Cisco Aironet 1520 Series), InfiNet (InfiMesh), Winncom (SyncMesh), BelAir, NEC, Motorola (MotoMesh), Others Products are designed for homogenous media, but the flexibility of mesh makes it attractive to combine heterogeneous technologies Hence heterogeneous access is required by network operators , , , DVB, 3GPP Current mesh solutions do not provide support for carrier grade services Need support at data link layer for mesh optimization Objective Realize heterogeneous backhaul mesh networks for operator deployments with support for mobile unicast and broadcast carrier grade services Overview Motivation and Objective Scenarios Extensions Extended Semantics Extended Functionalities Related work CARMEN Proposal Permanent and/or temporal deployment of radio access in public places, mass events or last mile application Deployment in public places or low-fiber areas Municipal applications (e.g. administrations, police, fireworkers,...) Scenarios City coverage On-demand infrastructure with local and worldwide access Deployment in different phases Coverage Capacity Scenarios Disaster recovery WLAN IEEE WiMAX IEEE GHz Satellite-based gateway to InternetWired or wireless terrestrial gateway to Internet Scenarios Rural Areas/ Undeveloped Countries On demand infrastructure, cheap and fast deployment for rural areas and under-developed nations Overview Motivation and Objective Scenarios Extensions Extended Semantics Extended Functionalities Related work CARMEN Proposal Approach Mesh needs many enhancements Inter-router communication instead of terminals Mesh management is certainly different than handovers IEEE as a basis for media independent behaviour Use existing IEEE primitives Extend semantics so as to support heterogenous wireless mesh nodes Extend existing functionalities of IEEE to enable building, managing and performance optimization of media independent mesh networks Link Layer management Monitoring Self Configuration Higher Layers Some ideas in extended functionality Link Layer Management Mechanisms to reach a virtual homogeneous mesh. Heterogeneous mesh with the behavior of a unique technology at link level. Media independent link creation Media independent link behavior management Media independent link metrics (interference..) Media independent QoS metrics and reporting per technology, allow the maintenance of QoS requirements in a technology independent way New primitives required to configure different radio interfaces in a common way, allowing to configure channels, transmission characteristics and so on. Examples of new primitives: AI_Radio_Get/Set_Radios, AI_Radio_Get/Set_Parameters AI_Link_Allocate/Modify/Release_Resources Extended Functionality, Examples Handover with Wireless Backhaul Low performance Wireless Link Current solution assumes bottleneck is in PoAs Wireless Mesh shall consider changes in the backbone wireless medium while performing handovers Mesh_Link_Allocate/Modify/Release_Re sources prior to handover Some ideas in extended functionality Monitoring Online monitoring of the state of the network Get parameters, configurations of heterogeneous links in the mesh Define and monitor performance metrics in an abstract way Active and passive monitoring of neighbors Mechanism able to detect neighbors for supported technologies Detection of outages in the network Node_Down primitive Remote communication of specific events to central monitoring point Example of new primitives: AI_Radio_Get_Statistics, Extended Functionality, Examples Heterogenous Network and Neighbourhood Discovery Some examples to messages/primitives Gateway_Registration Request Used for forwarding gateway info Implies existence of a mesh network Includes available technologies to connect Connection type (uni-bi directional) Mesh_Node_Mesh_Discover Request Used specifically by new mesh nodes Indicates available interfaces Lists already discovered neighbours Also used for panic mode Neighbourhood_Scan Request Passive and active monitoring results to support topology discovery and minimize interference Some ideas in extended functionality Self Configuration Network setup and configuration (node discovery and topology formation) Online adaptation and optimization for self configuration and repair Built on top of the new primitives of Monitoring and Link Layer Management Instruct AI to configure the nodes and their radio interfaces Decide threshold values for AI and Monitoring, handle notifications Requires new mechanisms to transport the information when the network is not configured Example of new primitives: Mesh_Node_Registration / Gateway_Registration Request Mesh_Node_Reconfiguration Radio_Set_Parameters Radio_Configuration_Suspend Extended Functionality, Examples Topology Formation Some examples to messages/primitives Mesh_Node_Registration Request Configurable radio paramters are given Get_Radio Request Get_Radio Properties Request Get_Radio_Paramters Request Mesh_Reconfiguration Request Examples to Extended Semantics IEEE protocol is designed for communication between terminal and access network Need to include communication among mesh nodes at the backhaul side Examples: MIH_Link_Up, Link_Down: L2 Connection is established and link is available for use. Applied to links between PoA and MN. New semantic: Also applies to links between nodes in the mesh. MIH_*_Candidate_Query: Use to query resources on the target networks in order to choose the best one. New semantic: Depending on the mesh model, it may require to query resources along the path to the destination. AI_Capabilities_Discover: Used to discover the events and commands available and link address list (optional) at a node New semantic: Discover all interface types and radio capabilities of a node. Some ideas in extended functionality Improvements at upper layers The new functionalities allow higher layers to extend their traditional capabilities Routing Prior to L3 routing, optimize topology for best performing routes Fast recovery in case of failure thanks to link layer triggers Abstract QoS based routing Media independent performance monitoring Media independent resource reservations Cooperation with Self Configuration for self healing/optimization Create on-demand new routes through radio configurations Mobility QoS aware abstract handover, may require to check resource availability across the network Use of the mesh as a smart backbone behind PoAs (e.g. 3G BSS) Overall optimization of the network resources based on smart attachment of the users Other benefits: Fast deployment Lower OPEX Use of whatever technology at hand to cover holes in the network Others Some ideas in extended functionality Improvements at upper layers Overview Motivation and Objective Scenarios Extensions Extended Semantics Extended Functionalities Related work CARMEN Proposal CARMEN Network operators Equipment manufacturers Academia / research institutes Carmen Objectives Objective 1 Support for multiple technologies by designing an interface to provide an abstraction of radio based MAC layers for mesh Objective 2 Create a cost-effective mesh network that supports carrier grade services Objective 3 Support for mobile unicast and broadcast services in a mesh environment CARMEN Architecture Mobility Self Configuration Routing Capacity Handling Monitoring (MeMs, MoMa) Overview Motivation and Objective Scenarios Extensions Extended Semantics Extended Functionalities Related work CARMEN Proposal Proposal We have identified an issue Upcoming scenarios will require a standard No current standards addressing this issue There is industry interest 5C are covered: Broad market potential, Compatibility, Distinct identity, Technical feasibility and Economical feasibility Proposal Study group IEEE 802 tutorial Mesh specific amendment of IEEE Mesh specific standard based on IEEE