1、BSI Standards PublicationFramework for energy market communicationsPart 503: Market data exchanges guidelines for the IEC 62325-351 profilePD IEC/TS 62325-503:2014National forewordThis Published Document is the UK implementation of IEC/TS 62325-503:2014.The UK participation in its preparation was en
2、trusted to TechnicalCommittee PEL/57, Power systems management and associated information exchange.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions ofa contract. Users are respon
3、sible for its correct application. The British Standards Institution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 81901 8ICS 33.200Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards P
4、olicy and Strategy Committee on 28 February 2014.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD IEC/TS 62325-503:2014IEC TS 62325-503 Edition 1.0 2014-01 TECHNICAL SPECIFICATION Framework for energy market communications Part 503: Market data exchanges guideline
5、s for the IEC 62325-351 profile INTERNATIONAL ELECTROTECHNICAL COMMISSION XD ICS 33.200 PRICE CODE ISBN 978-2-8322-1368-1 Registered trademark of the International Electrotechnical Commission Warning! Make sure that you obtained this publication from an authorized distributor. colourinsidePD IEC/TS
6、62325-503:2014 2 TS 62325-503 IEC:2014(E) CONTENTS FOREWORD . 7 INTRODUCTION . 9 1 Scope 10 2 Normative references 10 3 Terms and definitions 11 4 High level concepts . 12 4.1 What is MADES intended for? 12 4.2 General overview . 13 4.3 Message delivery and transparency . 14 4.3.1 Message delivery 1
7、4 4.3.2 Transparency 14 4.4 Security and reliability 15 4.5 Main components . 16 4.6 Distributed architecture 17 4.7 Components exposed interfaces . 18 4.8 Security features 18 4.8.1 Overview 18 4.8.2 Transport-layer security 19 4.8.3 Message-level security . 20 4.8.4 Non repudiation 21 5 Components
8、 functions 22 5.1 Routing messages . 22 5.2 Component and message unique identification (ID) 23 5.3 Business-type of a business-message . 23 5.4 Delivery-status of a business-message 23 5.5 Communication between components 25 5.5.1 Principle . 25 5.5.2 Establishing a secured communication channel be
9、tween two components 25 5.5.3 Token authentication of the client component . 26 5.5.4 Request authorisation . 26 5.5.5 Request/Reply validation 26 5.6 Storing messages in components . 27 5.7 Lifecycle of a message state within a component . 27 5.8 Transferring a message between two components (Hands
10、hake) 29 5.9 Accepting a message . 30 5.10 Event management 31 5.10.1 Acknowledgements . 31 5.10.2 Notifying events 32 5.10.3 Lifecycle of an acknowledgement . 34 5.10.4 Processing a transferred acknowledgement 34 5.11 Message expiration 35 5.11.1 Principle . 35 5.11.2 Setting the expiration time of
11、 a message: . 35 5.11.3 Looking for the expired messages: . 35 5.12 Checking the connectivity between two endpoints (Tracing-messages) 35 5.13 Ordering the messages (Priority) 36 PD IEC/TS 62325-503:2014TS 62325-503 IEC:2014(E) 3 5.14 Endpoint 36 5.14.1 Endpoint functions 36 5.14.2 Compression 37 5.
12、14.3 Signing . 38 5.14.4 Encryption 39 5.15 Node 41 5.15.1 Node functions . 41 5.15.2 Synchronizing directory with other nodes 41 5.15.3 Updating the synchronization nodes list . 42 5.16 Certificates and directory management 43 5.16.1 Definitions and principles 43 5.16.2 Certificates: Format and uni
13、que ID . 44 5.16.3 Used certificates and issuers (CAs) 44 5.16.4 Directory services . 46 5.16.5 Caching directory data 46 5.16.6 Trusting the certificates of others components 47 5.16.7 Renewing the expired certificates . 47 5.16.8 Revoking a certificate . 48 6 Managing the version of the MADES spec
14、ification . 49 6.1 Issues and principles . 49 6.1.1 General 49 6.1.2 Rolling out a new version (Mversion and N-compliance) . 49 6.1.3 Service compatibility . 49 6.1.4 Message compatibility 50 6.1.5 Interface with BAs. 50 6.2 Using the correct version for services and messages . 51 6.2.1 Node synchro
15、nization and authentication 51 6.2.2 Directory services and Network acceptance 52 6.2.3 Messaging services 53 6.2.4 Which version to use to send a message? 53 7 Interfaces and services 55 7.1 Overview 55 7.1.1 General 55 7.1.2 Error Codes 55 7.1.3 Types for Time 55 7.2 Endpoint interface 56 7.2.1 Ov
16、erview 56 7.2.2 Services . 56 7.2.3 File System Shared Folders (FSSF) 60 7.3 Node interface . 62 7.3.1 Overview 62 7.3.2 Authentication service 63 7.3.3 Messaging Services 64 7.3.4 Directory services . 67 7.3.5 Node Synchronization interface 70 7.4 Format of the node-list file . 71 7.5 Typed Element
17、s used by the interfaces 72 7.6 Description of the services . 79 7.6.1 About WSDL and SOAP 79 PD IEC/TS 62325-503:2014 4 TS 62325-503 IEC:2014(E) 7.6.2 Endpoint interface. 79 7.6.3 Node interface 86 7.6.4 XML signature example 100 Figure 1 MADES overall view . 12 Figure 2 MADES scope 13 Figure 3 MAD
18、ES key features 13 Figure 4 MADES message delivery overview . 14 Figure 5 MADES security and reliability . 15 Figure 6 MADES components 16 Figure 7 MADES network distributed architecture 17 Figure 8 MADES interfaces and services . 18 Figure 9 MADES transport security overview . 19 Figure 10 MADES se
19、cure communication initiation 19 Figure 11 Message signature . 20 Figure 12 Message encryption and decryption . 20 Figure 13 Non repudiation 21 Figure 14 Delivery route of a business-message 22 Figure 15 Reported events during the delivery of a business-message 24 Figure 16 Lifecycle of the local st
20、ate of a business-message within a component 28 Figure 17 Transfer handshake when uploading of a message 29 Figure 18 Transfer handshake when downloading of a message 30 Figure 19 Acknowledgements along the route of the business-message 32 Figure 20 Encryption process . 40 Figure 21 A node synchroni
21、zes with two other nodes . 42 Figure 22 Certificates and certificate authorities (CAs) for a MADES network 45 Figure 23 Managing the specification version node synchronization and authentication . 51 Figure 24 Managing the specification version Directory services . 52 Figure 25 Managing the specific
22、ation version Messaging services 53 Figure 26 Managing the specification version Which version to use to send a message? . 54 Figure 27 Node interface Overview . 63 Figure 28 Node interface Authentication service . 63 Figure 29 Node interface Messaging services UploadMessages service. 65 Figure 30 N
23、ode interface Messaging services DownloadMessages service 66 Figure 31 Node interface Messaging services ConfirmDownload service 67 Figure 32 Node interface Directory services GetCertificate service 68 Figure 33 Node interface Directory services GetComponent service. 70 Figure 34 WSDL 1.1 definition
24、s 79 Table 1 Message delivery status 25 Table 2 Business message status 28 Table 3 Accepting a message Validation checks . 31 PD IEC/TS 62325-503:2014TS 62325-503 IEC:2014(E) 5 Table 4 Characteristics of notified events . 33 Table 5 Event characteristics description . 34 Table 6 Acknowledgement stat
25、e description . 34 Table 7 Compression metadata attributes . 38 Table 8 Signing metadata attributes 39 Table 9 Encryption metadata attributes . 40 Table 10 Consequences of a certificate revocation 48 Table 11 Service compatibility Possible changes 50 Table 12 Which version to use to send a message?
26、. 54 Table 13 Managing the specification version Rejection conditions . 54 Table 14 Interfaces and services Generic error . 55 Table 15 Interfaces and services String value for errorCode . 55 Table 16 SendMessage Service request elements 56 Table 17 SendMessage Service response elements 57 Table 18
27、SendMessage Additional error elements . 57 Table 19 ReceiveMessage Service request elements 57 Table 20 ReceiveMessage Service response elements . 57 Table 21 ReceiveMessage Additional error elements 58 Table 22 CheckMessageStatus Service request elements . 58 Table 23 CheckMessageStatus Service res
28、ponse elements 58 Table 24 CheckMessageStatus Additional error elements . 58 Table 25 ConnectivityTest Service request elements 59 Table 26 ConnectivityTest Service response elements 59 Table 27 ConnectivityTest Additional error elements . 59 Table 28 ConfirmReceiveMessage Service request elements 5
29、9 Table 29 ConfirmReceiveMessage Service response elements . 59 Table 30 ConfirmReceiveMessage Additional error elements 60 Table 31 FSSF Description and filename format 61 Table 32 FSSF Filename description . 61 Table 33 Authentication Service request elements 64 Table 34 Authentication Service res
30、ponse elements . 64 Table 35 UploadMessages Service request elements 65 Table 36 UploadMessages Service response elements . 65 Table 37 DownloadMessages Service request elements . 66 Table 38 DownloadMessages Service response elements . 66 Table 39 ConfirmDownload Service request elements . 67 Table
31、 40 ConfirmDownload Service response elements 67 Table 41 SetComponentMversion Service request elements . 68 Table 42 SetComponentMversion Service response elements . 68 Table 43 GetCertificate Service request elements . 69 Table 44 GetCertificate Service response elements 69 Table 45 GetCertificate
32、 Additional conditions 69 Table 46 GetComponent Service request elements . 70 PD IEC/TS 62325-503:2014 6 TS 62325-503 IEC:2014(E) Table 47 GetComponent Service response elements 70 Table 48 GetNodeMversion Service request elements 70 Table 49 GetNodeMversion Service response elements 71 Table 50 Get
33、AllDirectoryData Service request elements . 71 Table 51 GetAllDirectoryData Service response elements . 71 Table 52 Node attributes ordered list . 71 Table 53 AuthenticationToken 72 Table 54 Certificate 72 Table 55 CertificateType string enumeration . 72 Table 56 ComponentCertificate 72 Table 57 Com
34、ponentDescription 73 Table 58 ComponentInformation 73 Table 59 ComponentType string enumeration . 73 Table 60 Endpoint 73 Table 61 InternalMessage 74 Table 62 InternalMessageType string enumeration . 75 Table 63 MessageMetadata . 75 Table 64 MessageProcessor 75 Table 65 Map . 75 Table 66 MapEntry .
35、76 Table 67 ValueType (enumeration) 76 Table 68 MessageState (string enumeration) . 76 Table 69 MessageStatus 76 Table 70 MessageTraceItem 77 Table 71 MessageTraceState (string enumeration) 77 Table 72 NotConfirmedMessageResponse . 77 Table 73 NotUploadedMessageResponse 78 Table 74 ReceivedMessage .
36、 78 Table 75 RoutingInformation 78 Table 76 SentMessage 78 PD IEC/TS 62325-503:2014TS 62325-503 IEC:2014(E) 7 INTERNATIONAL ELECTROTECHNICAL COMMISSION _ FRAMEWORK FOR ENERGY MARKET COMMUNICATIONS Part 503: Market data exchanges guidelines for the IEC 62325-351 profile FOREWORD 1) The International
37、Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fie
38、lds. To this end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IE
39、C National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardizat
40、ion (ISO) in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has represent
41、ation from all interested IEC National Committees. 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC can
42、not be held responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publicatio
43、ns. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment services and, in some areas, ac
44、cess to IEC marks of conformity. IEC is not responsible for any services carried out by independent certification bodies. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including in
45、dividual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upo
46、n, this IEC Publication or any other IEC Publications. 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements
47、of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights. The main task of IEC technical committees is to prepare International Standards. In exceptional circumstances, a technical committee may propose the publicati
48、on of a technical specification when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts, or the subject is still under technical development or where, for any other reason, there is the future but no immediate possibility of an agreement on an International Standard. Technical specifications are subject to review within three years of publication to decide whether they can be transformed into International Standards.
