13 May2008 doc IEEE 082 15 08 0317

13 -May-2008 doc. : IEEE 082. 15 -08 -0317 -00 -004 e Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Some MAC Requirements for Neighborhood Area Networks] Date Submitted: [13 May, 2008] Source: [Benjamin A. Rolfe] Company [Blind Creek Associates] [George Flammer] Company [Silver Spring Networks] Address [] Voice: [+1. 408. 395. 7207] E-Mail: [ben@blindcreek. com, gflammer@silverspringnet. com] Re: [] Abstract: Discussion of some critical MAC requirements derived from NAN characteristics and relates them to 802. 15. 4 MAC Purpose: Contribution to technical requirements definition and discussion for task group 15. 4 e Notice: This document has been prepared to assist the IEEE P 802. 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 P 802. 15. Submission: MAC Requirements for NAN Slide 1 Rolfe

13 -May-2008 doc. : IEEE 082. 15 -08 -0317 -00 -004 e MAC Requirements Considerations Neighborhood Area Networks and Utility Networks Benjamin A. Rolfe ben@blindcreek. com Submission: MAC Requirements for NAN Slide 2 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Outline • • What is NAN? NAN Application Example Critical MAC Characteristics NAN related to 4 e MAC efforts Submission: MAC Requirements for NAN 3 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e What does NAN Mean to Me? • Connect transparently out the door, down the street… – Connecting devices IN the home, and then… – Connecting devices ON the home – Long reach with short range (multi-hop) • Know your Neighbor – Ad-hoc associations and forwarding • Large scale networks – Dynamic scalability – Rugged individualism • Not dependent upon infrastructure – – • Forms it’s own connections and paths Adaptive Heterogeneous May include infrastructure bridging points Private – Multiple private networks simultaneously – Cooperation between private networks Submission: MAC Requirements for NAN 4 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e What does NAN Mean to Me? • Connect transparently out the door, down the street… – Devices ON the home – Devices IN the home – Long reach with short range (multi-hop) • Large scale networks – Dynamic scalability – Rugged individualism • Not dependent upon infrastructure – – Forms it’s own connections and paths Adaptive Heterogeneous May include infrastructure bridging points • Private – Multiple private networks simultaneously – Cooperation between private networks Submission: MAC Requirements for NAN 5 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e What does NAN Mean to Me? Looks a lot like a MESH Submission: MAC Requirements for NAN 6 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e NAN Architecture Submission: MAC Requirements for NAN 7 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Example: Utility Network • Utility Networks – Integrated Monitoring and Control • Wide area distributed • Low data rate / Low duty cycle • Ubiquitous Submission: MAC Requirements for NAN 8 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Utility Networks Architecture Reference: 15 -08 -0199 -00 -wng 0 Submission: MAC Requirements for NAN 9 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Utility Networks Overview Utility Automation – Need for Standard-based approach • Cost, availability, risk, efficiency • Interoperability between vendors needed – Low technical risk tolerance • Keep It Simple and Super Reliable (KISSR) – Distributed and Diverse • Diverse physical environments • Dispersed geographically – Distributed Process Control • • Moderate data rates High reliability and secure Simple Provisioning, long service life Constrained costs Reference: 15 -08 -0199 -00 -wng 0 Submission: MAC Requirements for NAN 10 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Key Needs • Low Data Rates – Low rate of data collection < 1 MByte/day/device nominal – Predictable Latency (Hop to hop must be controlled) – Different kinds of event/response requirements • Highly reliable and secure – Robust links, positive error detection, route diversity – Perceived security, privacy assuranc. – Multiple “privacy domains” • • Scalability Simple, Consistent and Cost Effective Provisioning Ubiquitous, connected “always on” Constrained costs – Very large number of nodes – Total cost of ownership – Long service life (in-place upgradeable) Submission: MAC Requirements for NAN 11 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Key MAC Characteristics • • • Data Characteristics MESH and Network Management Low Overhead Performance Characteristics Flexibility Cost Considerations Submission: MAC Requirements for NAN 12 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Data Characteristics • Upper Layers use IP – Effective handling of IP critical – Fragmentation in the MAC? • Critical data delivery – Strong error detection (longer CRC) – Link assessment tools – Adaptive techniques? • Privacy • Classes of Service – Prioritization (user and channel access) Submission: MAC Requirements for NAN 13 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e MESH • MESH support – Very large potential network size – High spectral reuse efficiency – Multi-hops with large spans – Redundant paths w/ mesh parallelism – ‘Pre-healing’ vs. ‘self-healing’ – Self-balancing – Prioritization of traffic – Dynamic response to environment Submission: MAC Requirements for NAN 14 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Performance Characteristics • Deterministic performance – Latency controlled hop to hop • Hop span: 15 -20 hops not unusual • Scalability – Peer-to-Peer, Self-forming and maintaining • Minimal complexity – Flexible – Path redundancy/diversity • Robustness – Environment and Co-existence – Link quality – Error detection and recovery limitations • Multi-level Security Submission: MAC Requirements for NAN 15 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e Flexibility • PHY Support Extensibility – 15. 4 PHY diversity • DSSS @ 900 MHz and 2. 4 – Multiple modulations – Multiple spreading mechanisms • UWB and CSS (15. 4 a) • Regional PHYs (15. 4 c, 15. 4 d) – Why stop there… – New NAN PHY? Submission: MAC Requirements for NAN 16 Rolfe

13 -May-2008 doc. : IEEE 802. 15 -08 -0317 -00 -004 e MAC Efforts • Qo. S – Latency – Classes of service (prioritization) • Channel utilization (hopping/agility) • Distributed network management – Distributed (Peer-to-Peer, ad-hoc) Pico-Net – “belonging” to multiple logical PNs • Robustness – Stronger link quality assessment and reporting – Stronger Error detection (CRC) – Other options? • Privacy – Key distribution in-band? – Device level authentication – Flexible support • MAC layer Fragmentation/de-Fragmentation? • Network (and device) Management Submission: MAC Requirements for NAN 17 Rolfe