doc.: IEEE <doc#>

Slides:



Advertisements
Similar presentations
Doc.: IEEE nan IG NAN Submission 09 May 2008 Jay Ramasastry; James Pace /Silver Spring NetworksSlide 1 Project: IEEE P Working.
Advertisements

Doc.: IEEE leci Submission Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Low Energy.
Doc.: IEEE e Submission: NAN Application Description 11 November 2008 RolfeSlide 1 Project: IEEE P Working Group for Wireless.
Doc.: IEEE wng0 12-May-2008 FlammerSubmission: MAC Requirements for Smart Grid Slide 1 Project: IEEE P Working Group for Wireless.
May 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [PHY proposal for existing Sub 1-GHz bands in.
November 2014 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Mobile Wireless Backhaul for Fast Moving.
doc.: IEEE <doc#>
Submission Title: [ Wireless Neighborhood Area Networks – WNAN ]
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
13-May-2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Some MAC Requirements for Neighborhood Area.
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [the Smart Grid] Date Submitted: [20 March.
doc.: IEEE <doc#>
August 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suitability Evaluation of Network Topologies]
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
W-SUN Technical Requirements Discussion
<month year> IEEE P xxxx g July 2009
May, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Information relating to default channel frequency.
Submission Title: [IG-NAN: Nature of the Requirements]
January 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Sub-GHz proposal for ] Date Submitted:
8 July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IG-NAN PAR Considerations for NAN] Date.
doc.: IEEE <doc#>
January 2014 doc.: IEEE /0084r0 January 2016
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
8 July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC Error Reporting Proposal] Date Submitted:
Submission Title: Usage Models for Personal Space Communications
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#>
Submission Title: [Narrow Band PHY Proposal for g]
Date Submitted: [17 November 2009] Source: [Peter Murray]
Submission Title: [Bluetooth SIG Liaison Report Nov08]
doc.: IEEE <doc#>
doc.: IEEE <doc#1>
Project: IEEE P WG for Wireless Personal Area Networks (WPANs)
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [more.
January 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Sub-GHz proposal for ] Date Submitted:
doc.: IEEE <doc#>
November 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Text Proposal for FCC NPRM Response Date.
July 2005 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c rate-range requirements: looking forward]
doc.: IEEE <doc#>
Submission Title: [ Wireless Neighborhood Area Networks – WNAN ]
April, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Information relating to default channel frequency.
13 November 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [NAN Application Description] Date Submitted:
<month year> <doc.: IEEE doc> March 2015
1 December 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4g Timeline Discussion] Date Submitted:
February 19 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4g-SUN Closing Report for Vancouver, March.
16 July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IG-NAN PAR Considerations for NAN] Date.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Intended IG Objectives] Date Submitted:
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
13 May 2009 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Battery Operated Sensing Device Requirements.
<month year> <doc.: IEEE doc> May 2015
<month year>20 Jan 2006
May, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Information relating to default channel frequency.
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> March 2015
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Consideration on MAC enhancement of IEEE ]
November 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Text Proposal for FCC NPRM Response Date.
<month year> doc.: IEEE <030158r0> <March 2003>
doc.: IEEE <doc#>
September 2009doc.: IEEE wng0
doc.: IEEE < nnn-00-0mag>
July 2009 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Flexible DSSS Merging Effort] Date Submitted:
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Summary.
<month year> <doc.: IEEE doc> March 2015
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.
doc.: IEEE <doc#3>
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Fitting Smart Grid Applications and 802 Wireless Ecosystem] Date Submitted: [12 May, 2008] Source: [Jay Ramasastry] Company [Silver Springs Networks] [Benjamin A. Rolfe] Company [Independent Consultant] [George Flammer] Company [Silver Springs Networks] Address [] Voice:[+1.408.395.7207] E-Mail:[ben@blindcreek.com, jramasas@silverspringnet.com, gflammer@silverspringnet.com] Re: [] Abstract: Review of what leads SSN to 802.15.4 Purpose: Contribution to Neighborhood Area Networks Interest Group (IG-NAN) 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. <author>, <company>

doc.: IEEE 802.15-<doc#> 05-May-2008 doc.: IEEE 802. 15-08-0244-00-wng0 <month year> doc.: IEEE 802.15-<doc#> Smart Grid and the 802 Wireless Ecosystem Prepared By: Jay Ramasastry George Flammer Silver Springs Networks Benjamin Rolfe Independent Consultant May 12, 2008 IEEE 802.15 Interest Group: Neighborhood Area Networks Add Jay’s name Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> 05-May-2008 doc.: IEEE 802. 15-08-0244-00-wng0 <month year> doc.: IEEE 802.15-<doc#> Why 802.15 For Neighborhood Area Networks? Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> Outline General Requirements Summary 802 Wireless Ecosystem Reviewed: 3G/4G 802.16 802.11 802.20 802.22 802.15 Prefer: 802.15 Rolfe/Flammer/Ramasastry <author>, <company>

Utility Network – General Requirements <month year> doc.: IEEE 802.15-<doc#> Utility Network – General Requirements Wide Area Process Control Low Data Volume 5-10 transactions per day per device Low data rate, low duty cycle Latency tolerance Needs to be consistent/deterministic Ubiquity Every customer connected Multiple devices per customer Robustness Perform under extreme environments Tolerant of device placement rather than optimally placed for network Consistency of performance Cost Constrained Acquisition – infrastructure cost Deployment Consistency across regions Long term Cost of Ownership Scalable Millions per utility Billions per country Needed Right Now! 10kB per transaction. Talk to “spectrum friendly”. Lots of nodes. Rolfe/Flammer/Ramasastry <author>, <company>

Utility Networks Architecture <month year> doc.: IEEE 802.15-<doc#> Utility Networks Architecture Talk to the MESH characteristics, multi-hop, etc. Reference: 15-08-0199-00-wng0 Rolfe/Flammer/Ramasastry <author>, <company>

Architectural Considerations Mesh Self forming and maintaining Self-healing (pre-healing) Multi-hop with large spans Large number of end nodes Peer to peer Flexible topologies Overlapping SOIs and SOPs Heterogeneous network elements Rolfe/Flammer/Ramasastry

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802 Wireless Ecosystem Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> Standards Review Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 3G/4G Licensed spectrum (cost, flexibility, risk) Coverage Dependence on service providers (and infrastructure) Limited options per region Inconsistent region to region – difficult to provide common solution everywhere Inconsistent over time Legacy requirements (voice, text, etc.) add complexity Optimized for mass consumer network Access not guaranteed Reliability/Robustness can not be controlled Part of the solution for backhaul Consumer network; Utility has no control over other users of the same network; depend on network management of service providers. Performance not predictable. Can’t depend on carrier to meet connection requirements kept consistenly Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.16 / WiMAX Licensed spectrum Architectural Complexity Infrastructure based architecture Designed for high data rate Unlicensed WiMAX ? No WiMAX profile (yet?) Mobile Licensed spectrum only (so far?) Complimentary part of the solution Backhaul Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.11 / WiFi Optimized for high data rate and high duty cycle Complex to Mesh Crowded space Provisioning complexity Perceived security/privacy concerns Perceived as an open network (hotspot) Robustness concerns Metro WiFi Inconsistent coverage => inconsistent solution Complimentary part of the solution Backhaul Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.20 Focus on Mobile Applications Licensed spectrum (above 2Ghz) Same concerns as above Complex multiple radio system Cost and availability Infrastructure intensive Deployment cost and complexity Lack of deployed base/inertia High risk Unclear risk/reward Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.22 Applicability unclear Infrastructure based architecture Point-to-point and point-to-multipoint Lack of deployed base/inertia Cost and availability uncertainty Something to watch Sub GHz, unlicensed ban The cool thing about 802.22 is the availability of unlicensed spectrum below 1GHz with relatively high power (for license exempt) of 4W. Good propagation + power = range. Unclear Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.15 15.1 Simple and Cheap, but… Short range, low rate optimized for low power not ideally “meshable” 15.3c Way more speed than needed Very short range (60GHz) Optimized for totally different application needs The cool thing about 802.22 is the availability of unlicensed spectrum below 1GHz with relatively high power (for license exempt) of 4W. Good propagation + power = range. Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.15 15.4 Unlicensed spectrum (incl. 900 MHz) Low complexity Suitable for Mesh (but can be made better) Compatible data rates Best fit of 802 standards …need appropriate enhancements Application Symbionics Synergy with existing applications Same users implementing in both application spaces The cool thing about 802.22 is the availability of unlicensed spectrum below 1GHz with relatively high power (for license exempt) of 4W. Good propagation + power = range. Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.15 15.1 is too slow… 15.3 is too fast… 15.4 is just right! The cool thing about 802.22 is the availability of unlicensed spectrum below 1GHz with relatively high power (for license exempt) of 4W. Good propagation + power = range. Rolfe/Flammer/Ramasastry <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> 802.15 15.1 is too slow… 15.3 is too fast… 15.4 is just right! (well, closer…) The cool thing about 802.22 is the availability of unlicensed spectrum below 1GHz with relatively high power (for license exempt) of 4W. Good propagation + power = range. Rolfe/Flammer/Ramasastry <author>, <company>

Take Aways 15.4 closest to “home” MAC may be closer than PHY ?? (work on this) Rolfe/Flammer/Ramasastry