1. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [L2 routing demands for FAN ] Date Submitted: [ 16 May, 2012] Source1: [Noriyuki Sato, Kiyoshi Fukui] Company [OKI] Address [2-5-7 Hommachi chuo-ku, Osaka, Japan] Voice:[+81-6-6260-0700], FAX: [+81-6-6260-0770], E-Mail:[sato652@oki.com, fukui535@oki.com] Source1: [Thomas Herbst] Company [Silver Spring Networks] Address [555 Broadway Redwood. City, CA 94063] Voice:[+1-650-868-4483], E-Mail:[therbst@silverspringnet.com] Re: [This is the original document.] Abstract:[This documents describes demands of L2 routing for the field area networks.] Purpose:[To identify the companies’ interest.] Notice:This document has been prepared to assist the IEEE P802.15. 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. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 2 L2 routing demands for the Field Area networks WNG Session Presentation 16 th May 2012 Atlanta GA Noriyuki Sato / Kiyoshi Fukui OKI Electric Industry Co., Ltd. Thomas Herbst Silver Spring Networks

3. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 3 Introduction Group Management and L2-routing issue was presented as interwork with WG21 at Jacksonville Meeting in January 2012. The WG21 decided to extend their scope to address group management. L2-routing issue was remained There was a question raised at Jacksonville meeting: “Does IEEE802.15.5 suffice the requirement of L2-routing for the field area?” In this presentation, we revisit the requirement for L2-routing for the field area and clarify the gap between the requirements and IEEE802.15.5

4. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 4 Why do we need a standard for L2-routing? Demands for L2-routing –IEEE802.15.4g extends PHY of IEEE802.15.4 to be used in field area. AMI infrastructure etc. –IP-based and non-IP-based networks are considerable for its upper layer. –IETF 6lowpan WG addressed how to adapt IEEE 802.15.4 to IPv6 Offers two adaptation models on routing –Route over, and –Mesh under –IETF Roll WG defined routing protocol for ‘Route over’ model –However, IETF has not addressed routing protocol for ‘Mesh under’ model This is mostly because IETF does not define link layers What standard body is appropriate? –Many forum or consortium address the specification for FAN protocol. But FAN is often used in public purpose. Open and Public standard body is preferable. Some market in certain country requires that. –Extension of IEEE802.15.4 should be addressed within IEEE802.15

5. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 5 Requirements for the purpose Network Requirements for FAN –Handling thousands of nodes within a network. –Consideration for scalability of network expands –Redundancy routing –Self healing of routing Avoid and quickly resolve loops Re-routing when network disaster occurs –Self organizing (forming /reforming network within minutes) –Accommodate battery powered devices –Bandwidth efficient

6. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 6 What is insufficient with the IEEE802.15.5? Scalability of network –In IEEE802.15.5, it uses tree routing. We have to define network plan before it deploys. Ex. How many child nodes a parent has. Self healing of routing –Since the routing depends on its addressing, it requires assigning of address on the whole network again if the routing topology has been changed. Consistency of amendments –IEEE802.15.5 defines its own low energy functionality but we have similar functionality in IEEE802.15.4e

7. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 7 Scalability Address allocation mechanism of IEEE802.15.5 Step 1 : Making a tree structure by joining from top level to lower Step 2 : Reporting number of children (including reservation) to parent from lowest level nodes to higher. After gathering all of number of children, root node start assign address spaces to nodes from top level to lower. Issue –Network topology plan should been made before network formation. –Functionality of address space reservation for future use and adjustment of assignments would help for extending network. However it is difficult when drastic change has been made. In that case, the network should have re-start from address assignment. 1 5 1 1 2 8 1 5 1 1 2 8 Inform number of childrenAssign address spaces by root 1 5 1 1 2 8 New joiner Join No more address to allocate! Assign address spaces by root ×

8. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 8 Self healing of routing Outline of routing algorithm of IEEE802.15.5 –Exchange the information with neighbors (address spaces, tree level etc.) –Choose next hop from the information Issue –Since routing algorithm is based on address assignment, network should start over from address assignment when drastic change on routing topology has been made. In the public field area network, drastic and long term topology change will be considered. A B C D E F G H I J K L M N O × ⇒ [1:8] [2:6] [3][4:5] [5] [6] [9:14] [10:14] [7:8] [8] [11:13] [13] [14] [12] [0:14] A B C D E F G H I J K L M N O [1:8] [2:6] [3][4:5] [5] [6] [9:14] [10:14] [7:8],[11:13] [8] [11:13] [13] [14] [12] [0:14] Cannot merge address spaces! ×

9. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 9 (Ref.) IEEE802.15.5 routing algorithm

10. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 10 What to be documented Extend IEEE802.15.5 or make another specification? Recommended Practice or Amendment of IEEE802.15.4? What to be included in the document? –Routing protocol which works well in the FAN –Consideration to use IEEE802.15.4e/g or other amendments

11. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 11 Example solutions This is OKI’s proprietary L2-routing protocol as an example. –Enhancement of link layer retransmission –Reducing flooding of control frames –Self healing by switching root node Example of self healing functionality

12. doc.: IEEE 802.15-12-268-01-wng Submission May 2012 N. Sato, K. Fukui & T. HerbstSlide 12 Question How many companies have interest on this activity? If it is enough, do we establish an interest group or a study group within IEEE802.15 to discuss it?