Upload
ariel-walker
View
217
Download
4
Embed Size (px)
Citation preview
September 2012
N. Sato & K. FukuiSlide 1
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [L2R Functionary Requirement ]Date Submitted: [20 September, 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:[[email protected], [email protected]]
Re: [This is the original document.]
Abstract: [This documents intends for discussion of the L2R functionality.]
Purpose: [For discussion]
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.
September 2012
N. Sato & K. FukuiSlide 2
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
L2 routing functionality requirements
L2R IG Presentation20th September 2012 Palm Springs CA
Noriyuki Sato / Kiyoshi FukuiOKI Electric Industry Co., Ltd.
September 2012
N. Sato & K. FukuiSlide 3
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Summary
• This presentation provides some of tips for following perspectives– To show use cases to share what L2R
protocol will be required– Proposing preliminary ideas regarding
what functionalities will be required
Note: This is really preliminary and does not cover all.
September 2012
N. Sato & K. FukuiSlide 4
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Vending machineVending machine
Smart Smart meteringmetering
M2MM2M
Smart meterSmart meter
ConcentratorConcentrator
Environmental monitoringEnvironmental monitoring
Ad-hoc data collection
What mesh will be required for FAN?• Mainly, data collection from many nodes in FAN and control of many nodes in FAN
from the outer server – Many to one and One to many routing protocol will be suitable• Ad-hoc data collection in the field area may be required in some use cases –
Reactive P2P routing may be required • Covering 1000+ nodes within one PAN and expected to interwork• Low power technology may be required in environmental monitoring or gas metering.
Low power routing
September 2012
N. Sato & K. FukuiSlide 5
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Concentrator 1
Concentrator 2
Concentrator3
Concentrator1
Concentrator2
Concentrator4
Concentrator2 is deactivated
Concentrator2 is reactivated
PAN1
PAN2
PAN3
PAN1
PAN3
An example scenario for managing FAN• Network should be configurable and workable automatically.• Less cost repairing process will be required when the network has problem.• After the problem has gone, network should be reformed (maybe to almost
original ) to reduce the load.
September 2012
N. Sato & K. FukuiSlide 6
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Non IPprotocol
Multiple protocols of upper layer
• Ether allows multiple protocols to work on it. L2R may need to do like it. To distinguish the protocols, it may need to hire a Protocol ID.
IPv6
6LoWPAN
L2R mesh
IEEE802.15.4
TCP UDP
MeshManagement This can be vendor specific or
be defined in the standard. But we should consider so that
multiple protocols works over L2R mesh at least .
Protocol ID?
September 2012
N. Sato & K. FukuiSlide 7
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Other required stuffs
• To make it work in the large network– Enforcement of reliability
• Enhancement of hop-by-hop retransmission to reduce the E2E retransmission– Scattering the Joining timing when the whole network restarts
• Scalability– Nodes density, network size etc.
• Sleeping routers and sleeping end nodes for the environmental monitoring
• Management of flooding, multicasting– Timing, grouping etc.
• Congestion avoidance, flow control• Security• Priority of frames• Others
– Considering scalability of hardware resources to network size
September 2012
N. Sato & K. FukuiSlide 8
doc.: IEEE 802.15-12-0547-00-0l2r
Submission
Thanks !