<month year> doc.: IEEE < > <September 2017>

Slides:



Advertisements
Similar presentations
Doc.: IEEE xxx Submission January 2015 N. Sato and K. Fukui (OKI)Slide 1 Project: IEEE P Working Group for Wireless Personal Area.
Advertisements

Doc.: IEEE l2r Submission September 2012 N. Sato & K. FukuiSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks.
Submission Title: [Add name of submission]
<month year> doc.: IEEE <# > <April 2008>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI protocol stack and flows of operations]
<month year> doc.: IEEE < > <Sept 2016>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Submission Title: Coding example for the ULI
Submission Title: [MC EventsList] Date Submitted: [11Jul00]
doc.: IEEE <doc#>
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG10 (L2R) Closing Report.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for ULI primitives] Date Submitted:
<month year> doc.: IEEE < e>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
<month year> doc.: IEEE < > <September 2017>
<month year> doc.: IEEE < > <January 2018>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Handling of non-ULI frame and Profile.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for ULI primitives] Date Submitted:
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<month year> doc.: IEEE < e>
<month year> <Sept 2018>
<month year> doc.: IEEE < > <September 2017>
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#1>
<month year> doc.: IEEE < e>
Submission Title: Example of P2P route discovery
<month year> doc.: IEEE < e> <Mar 2018>
Submission Title: Coding example for the ULI
<month year> doc.: IEEE <xyz> January 2001
Submission Title: Coding example for the ULI
doc.: IEEE <doc#>
平成31年1月 doc.: IEEE /424r1 July 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c motion.
<month year> doc.: IEEE < > <May 2017>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI “Profile” for Protocol Management] Date.
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Enhancing reliability of data transmission.
<month year> doc.: IEEE < e>
Source: [Pat Kinney] Company [Kinney Consulting LLC]
平成31年2月 doc.: IEEE /424r1 November 2008
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ULI protocol stack and flows of operations]
Submission Title: [Proposal for Short Address Multicast]
平成31年2月 doc.: IEEE /424r1 November 2007
<month year> November, 2004
Submission Title: [IEEE WPAN Mesh Reference Model]
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
<month year> <Nov 2018>
doc.: IEEE <doc#>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
<month year> doc.: IEEE < e>
doc.: IEEE <doc#>
<month year> doc.: IEEE August 2014
平成31年5月 doc.: IEEE /424r1 September 2007
<month year> doc.: IEEE May 2014
<month year> doc.: IEEE < > <March 2019>
Aug Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Explanation and Revision of Previous Time.
doc.: IEEE <doc#>
<month year> doc.: IEEE <030158r0> <March 2003>
平成31年7月 doc.: IEEE /424r1 March 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Call.
doc.: IEEE <doc#>
平成31年7月 doc.: IEEE /424r1 November 2007
Source: [Chunhui Zhu] Company [Samsung]
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Improve the latency between GTS request.
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.
Aug Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Explanation and Revision of Previous Time.
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
<month year> doc.: IEEE s September 2019
12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:
Presentation transcript:

doc.: IEEE 802.15-<15-16-0666-00-0012> <month year> doc.: IEEE 802.15-<15-16-0666-00-0012> <September 2017> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [L2R operation] Date Submitted: [11 September 2017] Source: [Noriyuki Sato, Kiyoshi Fukui] Company [Oki Electric Industry Co., Ltd.] Address [2-6-8, Bingo-machi, Chuo-ku, Osaka, Japan] Voice:[+81-6-6260-0700], E-Mail:[sato652@oki.com] Re: [L2R operation] Abstract: [Explaining L2R operations with ULI management box] Purpose: [To discuss] 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. <Noriyuki Sato><Kiyoshi Fukui>, <OKI>

L2R Operations Configuration Operations Device types Operation mode PAN Coordinator, Mesh root, L2R router, End device Operation mode PAN Coordinator decides PAN type – SSPAN, Regular PAN,TMCTP Mesh root decides operation options Address mode, Non-store/Store/Adhoc-P2P/etc… Joining device to be configured – allowed options Ex. I can join to the mesh operates in either non-storing mode or storing. L2R PIBs Operations Bootstrap procedure Process the procedure as configured – (Management box does?) Security setting Need a detailed procedure of KMP to set key parameters to L2R PIBs Interaction with higher layer (see following pages)

Short address assignment Device L2R Router Mesh root

Short address assignment PANCDC Device L2R Router Mesh root Only PAN Coordinator has short address assignment function. If the mesh root is also PAN coordinator, it has a function to assign a short address. If the mesh root is not PAN coordinator, mesh root play a role of proxy using PAN coordinator direct connection (PANCDC) PANCDC also manages the inter mesh flooding A mesh root forwards flooding data using PANCDC to PAN Coordinator and PAN Coordinator forwards all the mesh roots.

Short address request on a joining device Device requesting a short address L2R Protocols sublayer MMI sublayer IEEE802.15.4 MMI-DATA.request MCPS-DATA.request PDE MMI AA-RQ IE MCPS-DATA.confirm MMI-DATA.confirm L2R MCPS-DATA.indication AA-RP IE MMI-DATA.indication 15.4 AA-RP IE AA-RQ IE L2R invokes MMI-DATA.request to invoke MCPS-DATA.request.

Short address assignment on a mesh root (Option 1 – APL does) PANC DC Mesh root on PAN coordinator Mesh root with PANC DC Alternate AA AA PDE MMI PDE MMI L2R L2R PAN coordinator 15.4 15.4

Short address assignment on a mesh root (Option 1) MMI sublayer L2R Protocols sublayer PDE sublayer AA MGT App. IEEE802.15.4 AA-RQ IE MCPS-DATA.indication MMI-DATA.indication L2RLME-AA-RQ.indication PDE-MGMT.indication PDE-MGMT.request L2RLME-AA-RP.request PANC DC MCPS-DATA.request MMI-DATA.request AA-RP IE MCPS-DATA.confirm MMI-DATA.confirm L2RLME-AA-RP.confirm PDE-MGMT.confirm

Short address assignment on a mesh root (Option 2 – Management box does) PANC DC Mesh root on PAN coordinator Mesh root with PANC DC PANC comm. PDE MMI PDE MMI L2R MGMT L2R MGMT AA Alt. AA PAN coordinator 15.4 15.4

L2R short address assignment (Option 2) MMI sublayer L2R Protocols sublayer Management Protocols sublayer PDE sublayer Management Protocols sublayer IEEE802.15.4 NHL NHL PDE sublayer MCPS-DATA. indication AA-RQ IE MMI-DATA. indication L2RLME-AA-RQ.indication MGMT-MGMET. indication PDE-MGMT. indication PDE-MGMT. request MGMT-MGMET. request PANC DC MGMT-MGMT. confirm PDE-MGMT. confirm PDE-MGMT. response MGMT-MGMT. response L2RLME-AA-RP.request MMI-DATA. request MCPS-DATA. request PANC DC AA-RP IE MCPS-DATA. confirm MMI-DATA. confirm L2RLME-AA-RP.confirm

Short address assignment on a mesh root (Option 3 APL does & MGMT pass the messages) PANC DC Mesh root on PAN coordinator Mesh root with PANC DC Alternate AA AA PDE MMI PDE MMI L2R L2R L2R MGMT L2R MGMT PAN coordinator 15.4 15.4

Short address assignment on a mesh root (Option 3) MMI sublayer L2R Protocols sublayer Management Protocols sublayer PDE sublayer AA MGT App. IEEE802.15.4 AA-RQ IE MCPS-DATA.indication MMI-DATA.indication L2RLME-AA-RQ.indication MGMTMGMT. indication PDE-MGMT.indication PDE-MGMT.request MGMT-MGMT. request PANC DC L2RLME-AA-RP.request MCPS-DATA.request MMI-DATA.request AA-RP IE MCPS-DATA.confirm MMI-DATA.confirm L2RLME-AA-RP.confirm MGMT-MGMT. confirm PDE-MGMT.confirm

Source routing It depends on how to fix inconsistency on source routing error in IEEE802.15.10. NHL manages source routing L2R layer manages source routing

Source routing APL APL APL APL manages source routing. APL needs to manages the mode in which L2R operates and need to invoke L2R-DATA.request with appropriate parameters. L2R mesh root L2R Router DST node Source route APL APL APL

Source routing APL APL APL L2R mesh root L2R Router DST node Source route Management Box manages source routing. It manages mode in which L2R operates and it also manages data transmission.

Source routing APL APL APL L2R mesh root L2R Router DST node Source route If the source routing is managed in L2R. APL just send a data using Data-SAP

Source routing P2P communication on no-Storing mode SRC node L2R mesh root DST node Source route APL APL APL Hop by Hop routing Source routing APL handles source routing – Call L2R primitives directly? Or PDE handles indication and notify to APL? It can be that MGMT handles first and then invokes appropriate primitives

Source routing P2P communication on no-Storing mode SRC node L2R mesh root DST node APL APL APL Source route

Source routing P2P communication on no-Storing mode SRC node L2R mesh root DST node APL APL APL Source route L2R Layer manages source routing. Nothing to do with management box or APL.