BS IEC 62746-10-1:2018:2019 Edition
$215.11
Systems interface between customer energy management system and the power management system – Open automated demand response
Published By | Publication Date | Number of Pages |
BSI | 2019 | 212 |
IEC 62746-10-1(E) specifies a minimal data model and services for demand response (DR), pricing, and distributed energy resource (DER) communications. This document can be leveraged to manage customer energy resources, including load, generation, and storage, via signals provided by grid and/or market operators. These resources can be identified and managed as individual resources with specific capabilities, or as virtual resources with an aggregated set of capabilities. It specifies how to implement a two-way signaling system to facilitate information exchange between electricity service providers, aggregators, and end users. The DR signalling system is described in terms of servers (virtual top nodes or VTNs), which publish information to automated clients (virtual end nodes, or VENs), which in turn subscribe to the information. The services make no assumption of specific DR electric load control strategies that can be used within a DR resource or of any market-specific contractual or business agreements between electricity service providers and their customers.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
5 | CONTENTS |
8 | FOREWORD |
10 | INTRODUCTION |
12 | 1 Scope 2 Normative references |
13 | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions |
14 | 3.2 Abbreviated terms |
15 | 4 Overview 4.1 General |
16 | 4.2 Node and device types Tables Table 1 – IEC 62746-10-1 services support |
17 | 4.3 IEC 62746-10-1 services Figures Figure 1 – Possible relationships of VTN and VEN |
18 | 4.4 Assumptions 5 IEC 62746-10-1 features 5.1 General 5.2 Supported services 5.3 Report Only VENs 5.4 Transport mechanism 5.5 Security 6 Services and data model extensions 6.1 Event service 6.1.1 Event interactions |
19 | Figure 2 – EiEvent PUSH pattern |
20 | Figure 3 – EiEvent PULL pattern |
22 | 6.1.2 oadrEvent mechanism Figure 4 – Time intervals of an event |
24 | Table 2 – Signals |
26 | 6.2 Report service 6.2.1 General |
27 | Figure 5 – Report type |
28 | 6.2.2 Core reporting operations |
29 | Figure 6 – Interaction diagram: Register reporting capabilities |
30 | Figure 7 – Interaction diagram: Request reports |
32 | Figure 8 – Interaction diagram: Send reports |
33 | 6.3 Registration service 6.3.1 Service operations Figure 9 – Interaction diagram: Cancel reports Table 3 – EiRegisterParty payloads |
34 | Figure 10 – Interaction diagram: Query registration Figure 11 – Interaction diagram: Create registration |
35 | Figure 12 – Interaction diagram: Request reregistration Figure 13 – Interaction diagram: Cancel registration |
36 | 6.3.2 Registration information Table 4 – VEN information in oadrCreatePartyRegistration payload |
37 | 6.4 Opt service 6.4.1 Service operations Table 5 – VTN information oadrCreatedPartyRegistration payload Table 6 – EiOpt payloads |
38 | 6.4.2 Detail requirements Figure 14 – Interaction diagram: Create opt Figure 15 – Interaction diagram: Cancel opt |
39 | 6.5 Poll service |
40 | Figure 16 – Interaction diagram: oadrPoll (nothing in queue) |
41 | Figure 17 – Interaction diagram: oadrPoll (oadrDistributeEvent reply) Figure 18 – Interaction diagram: oadrPoll (oadrCreateReport reply) |
42 | 6.6 Application error codes Figure 19 – Interaction diagram: oadrPoll (request reregistration reply) |
43 | 7 Transport protocol 7.1 General 7.2 Simple HTTP 7.2.1 General 7.2.2 PUSH and PULL implementation |
44 | 7.2.3 Service endpoint URIs 7.2.4 HTTP methods 7.2.5 Failure conditions 7.2.6 HTTP response codes |
45 | 7.2.7 Message timeouts 7.2.8 Message retry/quiesce behaviour 7.2.9 PULL timing |
46 | 7.2.10 HTTP headers |
47 | 7.3 Transport-specific security 7.3.1 General 7.3.2 TLS client certificate 7.4 XMPP 7.4.1 General 7.4.2 Exchange model implementation 7.4.3 Service endpoints |
48 | 7.4.4 Service execution 7.4.5 Implementation of XMPP features |
51 | 7.4.6 Security considerations |
52 | 8 Cyber security 8.1 General 8.2 Architecture and certificate types |
53 | 8.3 Certificate authorities 8.4 Certificate revocation 8.5 TLS and cipher suites 8.6 System registration process 8.6.1 General 8.6.2 Certificate fingerprints |
54 | 8.7 Implementing XML signatures for message payloads 8.7.1 XML signature 8.7.2 Components of XML signatures |
55 | 8.7.3 Creating XML signatures Figure 20 – XML signature example |
56 | 8.7.4 Verifying XML signatures 9 Conformance 9.1 Conformance statement 9.2 Conformance rules 9.2.1 EiEvent |
57 | Table 7 – Conformance rules |
64 | 9.2.2 EiEvent – Additional 2.0b conformance rules Table 8 – Additional conformance rules |
66 | 9.2.3 EiOpt Table 9 – EiOpt conformance rules |
68 | 9.2.4 EiReport Table 10 – EiReport conformance rules |
74 | 9.2.5 EiRegisterParty Table 11 – EiRegisterParty conformance rules |
76 | 9.2.6 General conformance rules Table 12 – General conformance rules |
79 | 9.3 Cardinality Table 13 – Cardinalities |
80 | Annex A (normative)Detailed report description |
81 | Annex B (normative)Profile extensions B.1 Overview B.2 Report extension B.3 Event extension B.4 Other extensions |
82 | Annex C (normative)oadrPoll scenarios C.1 Overview C.2 Scenarios |
84 | Annex D (normative)Definition of VEN, VTN, resource, and party |
85 | Annex E (normative)IEC 62746-10-1 Schema |
209 | Bibliography |