1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-11-0042-00-0000 Title: Heterogeneous mesh networking issues Date Submitted: March 16, 2011 Presented at IEEE 802.21 session #43 in Singapore Authors or Source(s): Yoshihiro Ohba (Toshiba) and Noriyuki Sato (Oki Electric Industry Co., Ltd.) Abstract: This document describes heterogeneous mesh networking use cases and issues 121-10-0042-00-0000

2. 2 IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 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 802.21. 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 Development http://standards.ieee.org/board/pat/faq.pdf> Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf

3. Need for Heterogeneous Mesh A mesh network may be an inter-connection of sub-mesh networks of different link-layer technologies Access mesh networks and backhaul mesh networks should use different frequencies to avoid radio interference Access mesh networks in the same location may use different link-layer technologies to increase capacity Why interconnecting the heterogeneous mesh networks into a single mesh? To provide a unified and simplified way of mesh network management with providing self-{forming,healing} features across different link-layer technologies 21-10-0042-00-00003

4. Example Use Case 21-10-0042-00-00004 802.11 Access mesh 802.16 Backhaul mesh 802.15.4 Access mesh SMH Wired backhaul Heterogeneous mesh MMH MMH may use only one interface simultaneously MMR MMR: Multi-interface Mesh Router SMH: Single-Interface Mesh Host MMH: Multi-interface Mesh Host MMR

5. Example scenario for self healing 802.16 Backhaul mesh 802.15. 4 Access mesh MMR 802.15. 4 Access mesh 802.16 Backhaul mesh 802. 15.4 Acc ess mes h MMR 802.15.4 Access mesh Assumption: Two 802.15.4 mesh can be connected each other. In other words, nodes can be formed as one network. To gain reliability and bandwidth capacity, two access mesh networks are formed under two MMRs in this case. A network problem occurs and some nodes lose their connectivity to backhaul. Changing routing topology makes the networks to assure nodes’ connectivity. 521-10-0042-00-0000

6. Considerable Network architecture I IEEE802.21 IEEE802.15.4 SMH 802.15.4 Access mesh IEEE802.15.4 IEEE802.21 IEEE802.16 802.16 Backhaul mesh 802.15.4 Mesh routing MMR IEEE802.11 IEEE802.21 IEEE802.16 MMR 802.11 Access mesh IEEE802.21 IEEE802.11 SMH Media-independent Mesh Routing with SMHs and MMRs participation Only SMHs and MMRs talk 802.21 (Other nodes in each access mesh and backhaul mesh does not support 802.21 ) 802.11 Mesh routing 802.16 Mesh routing 621-10-0042-00-0000

7. 802.21- capable 802.11 Access mesh 802.21- capable 802.15.4 Access mesh Considerable Network architecture II IEEE802.21 IEEE802.15.4 SMH IEEE802.15.4 IEEE802.21 IEEE802.16 802.21- capable 802.16 Backhaul mesh MMR IEEE802.11 IEEE802.21 IEEE802.16 MMR IEEE802.21 IEEE802.11 SMH All nodes within each access mesh and backhaul mesh talk 802.21. (All nodes including routers works as 802.21 nodes.) Fully Media-independent Mesh Routing (with all nodes participation) 721-10-0042-00-0000

8. Heterogeneous Mesh Networking Issues There has been no standard way to provide self- {forming,healing} for heterogeneous mesh network, including configuration of operational parameters for PHY/MAC and higher layer protocols There has been no unified security mechanism that works across different mesh-capable access technology There has been no discussion to support inter-technology handovers for mesh networks Routing Issue What is an appropriate network architecture for media independent routing? L2 which doesn’t have its own mesh routing What could be event to change routing topologies? Self healing when disaster occurs Bandwidth efficiency Energy consumption etc. 21-10-0042-00-00008

9. What needs to be studied first? Existing device/network configuration and discovery protocols Existing mesh security protocols and mechanisms Applicability of MIH for inter-technology handover for heterogeneous mesh networks Existing mesh routing protocols 21-10-0042-00-00009