SMART ENERGY PROFILE 2.0 UPDATE – PAPS 3 & 9 Robby Simpson, PhD Smart Energy WG Chair GE Digital...

SMART ENERGY PROFILE 2.0 UPDATE – PAPS 3 & 9Robby Simpson, PhDSmart Energy WG ChairGE Digital [email protected] 1, 2010

mailto:[email protected]

2

• What is SEP 2.0?• Status Update• Pricing Function Set Details• DRLC Function Set Details• DER Function Set Details

OUTLINE

SGIP Grid-Interop 2010, Chicago, Ill

SEP 2.0?


4

• Application-Layer Profile – a collection of standards where options and configurations are specified with the intention of leading to interoperability and embedded device constraints

• Focus on communications related to efficiency, usage, price communication, and messaging• Range of backhaul (AMI, Internet, etc.) bandwidths and cost kept in mind during

development• MAC/PHY (Link Layer) independent – intended to run over generic Internet Protocol stack• Developing with several organizations including:

– ZigBee Alliance– HomePlug Powerline Alliance– Wi-Fi Alliance– EPRI– SunSpec Alliance– SAE– IETF– UCAIug

• 35+ million meters currently under contract, from a variety of major North American and international meter manufacturers

• Robust testing and certification program with logoing

WHAT IS THE SMART ENERGY PROFILE?


5

EXAMPLE SYSTEM ARCHITECTURE


6

SEP 2.0 STACK OVERVIEW AND RESPONSIBILITIES


802.15.4-2006

PANA

EAP-TLSEAP-PSK

IPv6RPL

TCP UDP

HTTP

TLS

mDNS

DNS-SD

EXI

CIM SEP 2.0 App Spec

App Support Spec

ZigBee IP

6LoWPAN

802.11, 1901, etc.

7

• Pricing Communication• Demand Response and Load Control• Metering / Energy Usage Information• Messaging• Pre-Payment• Plug-In Electric Vehicles• Distributed Energy Resources• Billing• Firmware Download• Time

FUNCTION SETS


8

• Application layer security built around TLS• May also have link layer security• Think ‘https’• Certificates

– Have agreed on a specific ECC cipher suite as the mandatory cipher suite for interoperability

– Have agreed on a specific RSA cipher suite as an optional cipher suite for interoperability

SECURITY


9

• HTTP – the web protocol we all know and love• Used to interact with ‘resources’ in a ‘RESTful’ manner

– 4 verbs: GET, PUT, POST, DELETE

• Driven by desire to have a long-lived protocol and a familiar protocol for consumer interactions

APPLICATION TRANSPORT


10

• mDNS – Multicast DNS• Familiar to many via Apple Bonjour• Enable DNS names without the need for a centralized DNS

server• Used in conjunction with DNS-SD to provide device and

service discovery

NAME RESOLUTION


11

• DNS-SD, used in conjunction with mDNS• Service Discovery

– Types and Sub-Types

• Essentially just DNS TXT records• “Give me all smartenergy devices”• “Give me all smartenergy DER devices”• Returns various information such as path

DEVICE AND SERVICE DISCOVERY


12

• EXI – Efficient XML Interchange• Tokenized XML• W3C standard• Message format of the HTTP resources

APPLICATION PAYLOAD FORMAT


13

• CIM, the Common Information Model• The “what”

– Metering, Pricing, etc.

• IEC standard (61968/61970)• UML -> Schema -> Resources

SEMANTIC MODEL


STATUS


15

• SEP 2.0 TRD comment resolution nearing completion and reballot

• SEP 2.0 Application Specification (App Spec):– Ballot received ~2000 comments– Resolution divided into sections led by champions– Significant progress made on resolving comments (most, if not all,

contentious items thought to be resolved)– Several face-to-face meetings (typically once per month)– The positive: we have a draft of a cutting edge application standard that

will serve as the foundation of the HAN for time to come and has been widely acclaimed

– The negative: has not been easy – requirements are a moving target with many external factors and contentious items, often caught in middle (CIM vs. 61850, for example)

• Several test/interop events have occurred

CURRENT STATUS


16

• US NIST and SGIP• NAESB• IEC• OpenSG• EU (ESMIG, OFGEM, etc.)• AU (WSAA, etc.)• SAE

EXTERNAL INFLUENCES


17

• Working with many SDOs• Developing new standards:

– IETF ROLL/RPL– IETF CoRE/CoAp– IETF 6LoWPAN (ND, etc.)

• Refining existing standards:– IETF PANA– IETF TLS– IEC 61968 (CIM)– IEEE 802.15.4– IETF mDNS– IETF IPv6 CPE BCP

EXTERNAL OUTREACH


18

• Within ZigBee, specification are not considered to be complete until there are Certified Products

• Targeting next public release (with comment resolution) end of January / early February

• Targeting final release in Q2 of 2011

• ZigBee Process:– Market Requirements Document (MRD)– Technical Requirements Document (TRD)– 0.7 version of Specification (Interop-Ready)– 0.9 version of Specification (Certification-Ready)– Final version of Specification (Certified Products)

PROJECT TIMELINE


PRICING FUNCTION SET DETAILS


20SGIP Grid-Interop 2010, Chicago, Ill

DRLC FUNCTION SET DETAILS


23

# RequestGET /dr HTTP/1.1Host: ::1

# ResponseHTTP/1.1 200 OKContent-Type: application/exi

<?xml version=“1.0” encoding=“UTF-8” ?><List results=“10” total=“10” xmlns=“http://www.zigbee.org/se”>

<DemandResponseProgram><link rel=“self” href=“/dr/0” /><ID>0</ID><name>RateSaver</name><List type=“EndDeviceControl” total=“1”

href=“/dr/0/edc” /></DemandResponseProgram>

</List>

LIST OF DEMAND RESPONSE PROGRAMS


24

# RequestGET /dr/0 HTTP/1.1Host: ::1


<?xml version=“1.0” encoding=“UTF-8” ?><DemandResponseProgram xmlns=“http://www.zigbee.org/se”>

<ID>0</ID><name>RateSaver</name><List type=“EndDeviceControl” total=“1”

href=“/dr/0/edc” /></DemandResponseProgram>

DEMAND RESPONSE PROGRAM


26

# RequestGET /dr/0/edc HTTP/1.1Host: ::1


<?xml version=“1.0” encoding=“UTF-8” ?><List total=“1” results=“1” xmlns=“http://www.zigbee.org/se”>

<EndDeviceControl><link rel=“self” href=“/dr/0/edc/0” /><deviceCategory>0xFFFFFFFF</deviceCategory><drProgramMandatory>true</drProgramMandatory><scheduledInterval>

<randomizeStart>5</randomizeStart><randomizeEnd>5</randomizeEnd><start>XXX</start><duration>60</duration>

</scheduledInterval><TargetReduction>

<type>0x00</type><value>10</value>

</TargetReduction><SetPoint>

<type>0</type><value>22</value>

</SetPoint><Offset>


</Offset><Status>

<dateTime>XXX</dateTime><reason>Peak Shaving</reason><type>0</type>

</Status><DutyCycle>80</DutyCycle>

</EndDeviceControl></List>

LIST OF END DEVICE CONTROLS


27

# RequestGET /dr/0/edc/0 HTTP/1.1Host: ::1


<?xml version=“1.0” encoding=“UTF-8” ?><EndDeviceControl>

<deviceCategory>0xFFFFFFFF</deviceCategory><drProgramMandatory>true</drProgramMandatory><scheduledInterval>

<randomizeStart>5</randomizeStart><randomizeEnd>5</randomizeEnd><start>XXX</start><duration>60</duration>

</scheduledInterval><TargetReduction>

<type>0x00</type><value>10</value>

</TargetReduction><SetPoint>


</SetPoint><Offset>


</Offset><Status>

<dateTime>XXX</dateTime><reason>Peak Shaving</reason><type>0</type>

</Status><DutyCycle>80</DutyCycle>

</EndDeviceControl>

END DEVICE CONTROL


DER FUNCTION SET DETAILS


29

• Working closely with EPRI, SunSpec, and IEC to use an appropriately harmonized semantic model based on CIM extensions from 61850

STAY TUNED…


30

Thanks!

For more information, please visit:http://www.ZigBee.org/SmartEnergy

CONCLUSION


http://www.zigbee.org/SmartEnergy

SMART ENERGY PROFILE 2.0 UPDATE – PAPS 3 & 9 Robby Simpson, PhD Smart Energy WG Chair GE Digital...

Documents

Transcript of SMART ENERGY PROFILE 2.0 UPDATE – PAPS 3 & 9 Robby Simpson, PhD Smart Energy WG Chair GE Digital...