11

Texas AMIT DiscussionTexas AMIT DiscussionSEP 1.x and SEP 2.0SEP 1.x and SEP 2.0

July 2011

22

AgendaAgenda

• Ember Overview• Demonstration• SE 1.x status and timeline• SE 2.0 status and timeline• Our Perspective on Market View

3

• Global low-power, wireless mesh networking standard for monitoring and control applications

• Technology of choice for Smart Meters and Home Area Networks (HANs)

• Well suited for variety of sensor network applications

• Global Alliance of over 350 companies

Ember – Facts At A Glance

Ember is the leading supplier of ZigBee Semiconductors, Software and Development Tools

Incorporated: 2001 | Revenues: ~ $12M (2009)~ $30M (2010) What is ZigBee?What is ZigBee?

Offices: Boston, MACambridge, UKHong Kong

Employees: 64 total, 45 in R&D

Management: Robert LeFort – President & CEOJim Sheehan – SVP & CFODennis Natale – VP, Sales, AmericasSkip Ashton – SVP, EngineeringBert Lutje Berenbroek – VP, Sales, EMEARNick Horne – Director, IC EngineeringBob Power – Director, Software Engineering

Investors: Polaris Venture Partners, GrandBanks Capital, RRE Ventures, Vulcan Capital, DFJ ePlanet

Ventures, New Atlantic Ventures, WestLB Mellon Asset Management, Stata Venture Partners

4

Where is Ember Found?

• Smart Grid– Smart Meters

– Home Area Networks (HAN)

– Neighborhood Area Networks (NAN)

• Security, Monitoring and Automation– “Quadruple play” for ISPs / MSOs

– Replaces existing services from alarm monitoring pure plays (i.e. ADT)

• Home Automation– Advanced lighting, entertainment, and

climate control systems

– Service-based monitoring, security, and awareness systems

• Building Automation– Climate & lighting control systems

And wide variety of other sensing and control applications…

HomeMonitoringServices

HomeMonitoringServices

Home Automation

Home Automation

Home Area Network (HAN)

Home Area Network (HAN)

UtilityNetworks

UtilityNetworks

HVACControls

HVACControls

LightingControls

LightingControls

Sample Ember Customers

5

Demonstration

6

UbuntuHTTP/CoAPProxy

(1) IP Stack 30 Node Demo

Window 7 PC• HTTP Client (standard Firefox browser)• Wireshark to monitor Ethernet • ISD to monitor 15.4

Ubuntu Running HTTP/CoAP Proxy• Statelessly converts between HTTP/XML and CoAP/EXI• Attached to EM357 IP Modem via USB/Serial

EM357 IP Modem• Bridge between the Proxy and the EM357 network• Is the network root –setting up DAG for RPL routing

EM357 29 Node Network• Network of 29 EM357 nodes running an IP stack• Each node is either a Meter or a DRLC device• Each accepts CoAP GET requests for applicable URIs• Each responds with EXI payload over CoAP

Windows 7Firefox Browser

EM357IP Modem

Ethernet Serial

Ethernet IPv4 HTTP Serial IPv6 CoAP

15.4

15.4 IPv6 / 6LoWPAN CoAP/EXI

EM35729 NodeNetwork

RPL routing

77

Who is ZigBee?Who is ZigBee?

A global alliance of over 400 companies with a specification for interoperable, low-power,

low-cost wireless device communication

A global alliance of over 400 companies with a specification for interoperable, low-power,

low-cost wireless device communication

• Defines the network, security, and application protocol layers

• Provides interoperability and conformance specifications

• Promotes the ZigBee brand globally to build market awareness

• Manages future evolution of ZigBee technology

• Defines the network, security, and application protocol layers

• Provides interoperability and conformance specifications

• Promotes the ZigBee brand globally to build market awareness

• Manages future evolution of ZigBee technology

ZigBee PromotersZigBee Promoters

8

ZigBee and SEP Status

99

Where is ZigBee Today?Where is ZigBee Today?ZigBee Smart Energy is bridging the gap between the power grid today & the Smart Grid of tomorrow

– Using ZigBee Smart Energy today can improve in building energy efficiency, comfort and convenience all at the same time even without a smartgrid or a smart meter

– Households with digital tools controlling temperature and price preferences saved on average 10% on utility bills

40+ million ZigBee electric meters being deployed by over 11 utility companies in the USA

– Major deployments in California, Texas, Michigan & Virginia– An additional 40 million meters (from utility RFPs) in the USA are in

various stages of business case development and rate approval with local regulatory bodies

Large scale rollouts underway– Technology is available today; field trials as well as large scale

deployment are happening now– Australia deployments– British Gas 1m home deployment through 2012

1010

Smart Energy 1.0 and 1.1Smart Energy 1.0 and 1.1

• SE 1.0 – Primary focus on consumption data– Demand Response– Pricing– Establish underlying security and device authentication

• SE 1.1 (spec approved and released)– Over the air software updates– Fast polling– Pricing Updates– Large number of test spec improvements and cleanup from field

events

1111

Smart Energy 1.1 and 1.2Smart Energy 1.1 and 1.2

• SE 1.1 additional features (in testing)– Tunneling (for DLMS)– Prepayment– Trust Center replacement– Multi-ESI behavior

• SE 1.2 (in marketing discussion)– Compatibility with HA networks– British Gas requirements– Security Improvements from CSWG review– Other features under discussion with Members

12

Deployments for SE 1.x

• Meter deployments do not fulfill the promise of Smart Energy

• Need consumer engagement and HAN use• This is viewed differently in different regions

– Texas – retailers decision– California – limited pilots– UK deployment by British Gas is 4 devices per home

(eMeter, Gas, IHD, Gateway)– Australia – retailers decision

13

On Going Demands for SE 1.x

• Other regions continue to deploy SE 1.x – India now looking at SEP for meter data networks– China interest and meetings in June

• New areas of deployment often mean new extensions to the profile– British gas requirements for UK market– Tampering cluster requested in India

• ZigBee Alliance is market driven so new features are evaluated on case by case basis

14

SE 2.0 (IP) Stack Status • Overall

– Major pieces of stack defined– Ongoing work to clarify the specification– SE 2.0 TRD Passed ballot

• Test event now being scheduled for September– More expected to complete stack– then certify platforms and products – Q4 or early 2012 expected

• Nine Companies participating in SE 2.0 Platform test events

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

15

ZigBee IP Stack Testing Status

• Started in Jan 2010• ZigBee Testing in 3 phases

– Feature definition/spec clarification – rough testing between vendors

– Test spec development and refinement – detailed testing and negative cases

– Certification – complete from start to end with no changed among multiple vendors

• Still working to complete initial testing of features

• Events so far:• Jan 2010 – 6lowPAN• March 2010 – 15.4 security• April 2010 – RPL routing, TCP• May 2010 – RPL, HTTP• June 2010 – ND, Bootstrapping• August 2010 – ND, RPL• Oct 2010 – ND, RPL• Nov – ND, RPL, PANA (Dublin)• Dec 2010 – latest ND, RPL,

EAP/PANA/TLS with PSK• Jan 2011 – Multicast, mDNS, RPL failures• Feb 2011 – HTTPS, multiple LBR’s,• March 2011 – ECC testing• May 2011 – Large network, MLE• July 2011 – MLE, sleeping join

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

16

Stack Items Remaining to be Tested

• Multiple border routers (need to complete on and off network testing)• Sleeping end devices

– How parent knows device is sleeping (tested in July event)– Routing and handling sleeping device (RPL handles, need to test)– Proxing messages, service discovery etc (need to specify behavior)

• Key update (need to agree on method)• Failure cases (started for routing, but also needed for other areas)• Replacement/backup of functions• General cleanup for all platforms

• Once all Features are completed:• Complete Specification update• Certification testing runs (likely 3-6 months effort)• Then stack can be provided to customers for integration into products

Ember Corporation ConfidentialCopyright © 2011 — All Rights Reserved

17

SE 2.0 Application Status• Failed April ballot• Agreed on path forward in Wuxi meetings• Currently

– Defined as TCP/HTTP– Discussion of UDP/CoAP usage– Payload compression also being discussed

• Other comment resolution ongoing – security, discovery etc• Resolved major comments and implemented Wuxi accord text• Went back to 30 day ballot on July 15• Some comments will wait for resolution from 0.7 to 0.9 spec and

testing efforts

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

18

App Spec Schedule

• ZigBee Alliance schedule update based on reballot of specification

• Specification approved to 0.7 August 2011• Test events Sept 2011 – June 2012• 0.9 document approved June 2012• Certification events July – Sept 2012• Completed specification Sept 2012

• Then companies can begin integrating and releasing SE 2.0 in products

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

19

SE 2.0 Profile Functionality• Application functionality includes

– DRLC– Messaging– Pricing– Prepayment– Metering– Plug-in electric vehicles– Distributed energy resources– Billing– Registration– Device configuration and capabilities– Network management– Firmware downloads (tftp)– Diagnostics and monitoring

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

20

Application Model

• Application model is based on CIM (UML)• From this we can generate XML representing the data

exchanges needed• XML is compressed using EXI for more efficient

messaging– Known schema being developed to be simple to compress and

decompress for devices

• Ember has been working to define how EXI can be used for efficiency and allow extensibility of protocol (for SE 2.1…)

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

21

Backup or Alternate Application Profile Support

• CORE group formed within IETF for devices not suitable for TCP/HTTP (CORE = Constrained Restful Environments)

• Provide means to use compressed protocol mapped to HTTP but over UDP for lower bandwidth constrained networks

• Work is ongoing within IETF• Would not change application profile –

– Same objects and messages– Transport over UDP to http proxy device

• ZigBee is working on this to evaluate as backup to TCP and HTTP for some devices (battery operated clients)

Ember Corporation – Confidential InformationCopyright © 2011 — All Rights Reserved

22

Market View

• Developments in SE 1.x will continue in parallel with SE 2.0 for some time

• Some markets will wait for SE 2.0 and others will continue deployment and wait for maturity before switching over

• This is a local decision• Ember will continue to support both until market

decides otherwise• Focus is customer benefit and not underlying

technology

23

Comments or Questions?