1 / 6

Switching Mesh with Service ID: An Issue and Possible Solutions

This document discusses the issue of switching mesh by using service ID and proposes options to solve the problem. The functionality of choosing appropriate mesh tree, self healing, management of mesh growth, and switching to another mesh tree in case of mesh root failure are addressed.

mildredgallagher
Download Presentation

Switching Mesh with Service ID: An Issue and Possible Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [An issue on switching mesh by using service ID] Date Submitted: [17 September, 2015] 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] Re: [This is the original document.] Abstract: [The issue to place the functionality to choose appropriate mesh tree – NHL or L2R layer ?] Purpose: [To initiate discussions] 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. N. Sato and K. Fukui (OKI)

  2. An issue on switching mesh by using service ID TG10 presentation 16th September 2015 Noriyuki Sato / Kiyoshi Fukui OKI Electric Industry Co., Ltd. N. Sato and K. Fukui (OKI)

  3. Specification of D1 • Service ID is to present what service is provided in that mesh tree so that application can choose which mesh tree the device join to. • Self healing among mesh trees with same service ID. If there are same service ID which some mesh trees provide, • (I) a joining Node selects better PQM from different mesh • (II) A node which is already part of the mesh can Reconnect to another mesh tree which provides better PQM • (III)If the two mesh trees grow and a new node between two mesh trees can select which mesh tree it should join to by Max Depth and PQM. • (IV) If a mesh root dies, nodes of its children can switch to another mesh tree which provides same service ID. N. Sato and K. Fukui (OKI)

  4. Functionality mesh tree selection – self healing, management mesh growth Change mesh tree Join Mesh root A Service I Mesh root B Service II Mesh root A Service I Mesh root B Service II PQM will be 3 PQM is 3 PQM will be 5 PQM will be 2 A device can switch the mesh tree if the coordinator provides lower PQM than current parent. (I) A joining device can choose better PQM among the tree by indicating service ID. At boundary, a node can select Within max depth Within max depth Mesh root B Service II (III) Letting a device choose one of mesh tree which provides same service, tree stops to grow intermediate point between mesh roots (IV) If one of mesh roots dies, a device automatically reconnect to another tree which provides same service. N. Sato and K. Fukui (OKI)

  5. Issue on D2 • (I) Joining Node selects better PQM from different mesh • L2R-D IE doesn’t provide PQM. So, the device cannot choose a mesh tree which provides better PQM. There is no way to make NHL know information in TC IE (e.g. PQM) • (II) Reconnecting to another mesh tree which provides better PQM • There is no way to let NHL know that there is a neighbor which provides better PQM. • (III) Automatically growth of mesh tree on same service • Same as (II). There is no way to let NHL know max depth which a tree provides so that NHL can select mesh tree which allows it to join. • (IV) Switching to another mesh tree when the mesh root dies • L2RLME-DISCONNECT-MESH.indication in D2 can handles – no issue on this functionality N. Sato and K. Fukui (OKI)

  6. Options to solve • Options • Let the higher layer to have functionality to switch or select mesh tree join in • Indication primitive which announces better PQM found is required • or indication every time the node receives TC IE. • L2R Scan sequence at join sequence should be separated. • Let the L2R layer to have that functionality (Going back to D1 basis) • Join primitive needs service ID to let L2R which service L2R subscribe • Let node choose mesh tree by indicating either mesh root address or service ID • Give up to incorporate switching functionality among mesh trees which provide same service according to the link change (PQM change) N. Sato and K. Fukui (OKI)

More Related