{"id":250196,"date":"2024-10-19T16:30:07","date_gmt":"2024-10-19T16:30:07","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iec-62746-10-12018\/"},"modified":"2024-10-25T11:43:20","modified_gmt":"2024-10-25T11:43:20","slug":"bs-iec-62746-10-12018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iec-62746-10-12018\/","title":{"rendered":"BS IEC 62746-10-1:2018"},"content":{"rendered":"
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4 Overview 4.1 General <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.2 Node and device types Tables Table 1 \u2013 IEC\u00a062746-10-1 services support <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.3 IEC\u00a062746-10-1 services Figures Figure 1 \u2013 Possible relationships of VTN and VEN <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.4 Assumptions 5 IEC\u00a062746-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 <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Figure 2 \u2013 EiEvent PUSH pattern <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 3 \u2013 EiEvent PULL pattern <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.1.2 oadrEvent mechanism Figure 4 \u2013 Time intervals of an event <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Table 2 \u2013 Signals <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 6.2 Report service 6.2.1 General <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Figure 5 \u2013 Report type <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 6.2.2 Core reporting operations <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Figure 6 \u2013 Interaction diagram: Register reporting capabilities <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure 7 \u2013 Interaction diagram: Request reports <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Figure 8 \u2013 Interaction diagram: Send reports <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.3 Registration service 6.3.1 Service operations Figure 9 \u2013 Interaction diagram: Cancel reports Table 3 \u2013 EiRegisterParty payloads <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure\u00a010 \u2013 Interaction diagram: Query registration Figure 11 \u2013 Interaction diagram: Create registration <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure 12 \u2013 Interaction diagram: Request reregistration Figure 13 \u2013 Interaction diagram: Cancel registration <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 6.3.2 Registration information Table 4 \u2013 VEN information in oadrCreatePartyRegistration payload <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 6.4 Opt service 6.4.1 Service operations Table 5 \u2013 VTN information oadrCreatedPartyRegistration payload Table 6 \u2013 EiOpt payloads <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 6.4.2 Detail requirements Figure 14 \u2013 Interaction diagram: Create opt Figure 15 \u2013 Interaction diagram: Cancel opt <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 6.5 Poll service <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 16 \u2013 Interaction diagram: oadrPoll (nothing in queue) <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure 17 \u2013 Interaction diagram: oadrPoll (oadrDistributeEvent reply) Figure 18 \u2013 Interaction diagram: oadrPoll (oadrCreateReport reply) <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.6 Application error codes Figure 19 \u2013 Interaction diagram: oadrPoll (request reregistration reply) <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 7 Transport protocol 7.1 General 7.2 Simple HTTP 7.2.1 General 7.2.2 PUSH and PULL implementation <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 7.2.3 Service endpoint URIs 7.2.4 HTTP methods 7.2.5 Failure conditions 7.2.6 HTTP response codes <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 7.2.7 Message timeouts 7.2.8 Message retry\/quiesce behaviour 7.2.9 PULL timing <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 7.2.10 HTTP headers <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 7.4.4 Service execution 7.4.5 Implementation of XMPP features <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 7.4.6 Security considerations <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 8 Cyber security 8.1 General 8.2 Architecture and certificate types <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 8.7 Implementing XML signatures for message payloads 8.7.1 XML signature 8.7.2 Components of XML signatures <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 8.7.3 Creating XML signatures Figure 20 \u2013 XML signature example <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 8.7.4 Verifying XML signatures 9 Conformance 9.1 Conformance statement 9.2 Conformance rules 9.2.1 EiEvent <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Table 7 \u2013 Conformance rules <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.2.2 EiEvent \u2013 Additional 2.0b conformance rules Table 8 \u2013 Additional conformance rules <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 9.2.3 EiOpt Table 9 \u2013 EiOpt conformance rules <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 9.2.4 EiReport Table 10 \u2013 EiReport conformance rules <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 9.2.5 EiRegisterParty Table 11 \u2013 EiRegisterParty conformance rules <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 9.2.6 General conformance rules Table 12 \u2013 General conformance rules <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 9.3 Cardinality Table 13 \u2013 Cardinalities <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Annex\u00a0A (normative)Detailed report description <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Annex\u00a0B (normative)Profile extensions B.1 Overview B.2 Report extension B.3 Event extension B.4 Other extensions <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Annex\u00a0C (normative)oadrPoll scenarios C.1 Overview C.2 Scenarios <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Annex\u00a0D (normative)Definition of VEN, VTN, resource, and party <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Annex\u00a0E (normative)IEC\u00a062746-10-1 Schema <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems interface between customer energy management system and the power management system – Open automated demand response<\/b><\/p>\n |