BS EN IEC 62325-503:2018
$215.11
Framework for energy market communications – Market data exchanges guidelines for the IEC 62325-351 profile
| Published By | Publication Date | Number of Pages |
| BSI | 2018 | 94 |
IEC 62325-503:2018 specifies a standard for a communication platform which every Transmission System Operator (TSO) in Europe can use to exchange reliably and securely documents for the energy market. Consequently a European market participant (TSO, regional supervision centre, distribution utility, power exchange, etc.) could benefit from a single, common, harmonised and secure platform for message exchange with other participants; thus, reducing the cost of building different information technology (IT) platforms to interface with all the parties involved. This edition cancels and replaces IEC TS 62325-503 published in 2014. This edition includes the following significant technical changes with respect to the previous edition: a) Use of ISO/IEC 19464:2014, Advanced Message Queuing Protocol (AMQP) v1.0 specification; b) Splitting of the node described in the IEC TS 62325-503:2014 into a broker that implements the messaging function and a directory; c) Increase of operability and resilience of the communication system with the ability for an endpoint to send and receive messages through several brokers; d) Benefits of standardisation, performance and scalability of the AMQP protocol for transferring messages.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
| 7 | English CONTENTS |
| 12 | FOREWORD |
| 14 | INTRODUCTION |
| 15 | 1 Scope 2 Normative references |
| 16 | 3 Terms and definitions |
| 17 | 4 High level concepts 4.1 What is the purpose of MADES? Figures Figure 1 โ MADES overall view |
| 18 | 4.2 Overview Figure 2 โ MADES scope in a layered architecture |
| 19 | 4.3 Transparent and reliable message delivery Figure 3 โ MADES message delivery |
| 20 | 4.4 Components of a MADES system 4.4.1 Endpoint, broker and component-directory Figure 4 โ MADES components, interactions and protocols |
| 21 | 4.4.2 Delivery routes and acknowledgements Figure 5 โ Possible routes for delivering a message |
| 22 | 4.4.3 Sharing configuration data of the system Figure 6 โ Communication protocols for delivering a message |
| 23 | Figure 7 โ Data flows between a component-directory and its registered components |
| 24 | 4.4.4 Interfaces exposed by the components Figure 8 โ Data flows with several component-directories Figure 9 โ Component-directory services and protocols |
| 25 | Figure 10 โ MADES Interfaces, services and protocols |
| 26 | 4.4.5 Architecture examples of MADES systems Figure 11 โ Minimal MADES system (without broker) Figure 12 โ Minimal MADES system (with broker) |
| 27 | Figure 13 โ MADES system with a party in a central role |
| 28 | Figure 14 โ MADES system with several brokers |
| 29 | 4.5 Security and message integrity 4.5.1 Security goals and security solution Figure 15 โ Using a single endpoint for several business processes |
| 30 | 4.5.2 Transport-layer security Figure 16 โ MADES transport security Figure 17 โ Security: protected endpoint |
| 31 | 4.5.3 Message-level security: signing and encryption Figure 18 โ Security: exposed endpoint Figure 19 โ Message signing and signature verification |
| 32 | 4.5.4 Non-repudiation Figure 20 โ Message encryption and decryption |
| 33 | Figure 21 โ Non-repudiation |
| 34 | 5 Delivering the messages 5.1 Unique identification of components and messages 5.2 Message-type of a message 5.3 Message route towards a recipient endpoint: message-paths |
| 36 | 5.4 Restriction on the routes by a broker 5.5 Message acceptance by a sender endpoint 5.6 Tracking the delivery of a message 5.6.1 Message-status of a message |
| 37 | 5.6.2 Delivery events and acknowledgements Figure 22 โ Message-status along the delivery |
| 38 | Figure 23 โ Tracking events while delivering a message |
| 39 | 5.7 Message expiration Tables Table 1 โ Characteristics of the tracking events |
| 40 | 5.8 Reliable transfer of a message 5.8.1 Rationale |
| 41 | 5.8.2 Transfer between sender application and sender endpoint Figure 24 โ Reliable transfer Figure 25 โTransfer between sender application and sender endpoint |
| 42 | 5.8.3 Transfer between components using the AMQP protocol 5.8.4 Transfer between recipient endpoint and recipient application Figure 26 โ Transfer between recipient endpoint and recipient application |
| 43 | 5.9 Storing internal messages in components 5.10 Message priority 5.11 Message delivery order 5.12 Testing a route between two endpoints: tracing-messages Table 2 โ Final state of a message in an endpoint |
| 44 | 6 Transferring messages using the AMQP protocol 6.1 Main principles of the AMQP specification 6.1.1 Introduction |
| 45 | 6.1.2 Connection Open 6.1.3 Session begin Figure 27 โ The nine AMQP frames |
| 46 | 6.1.4 Link attachment 6.1.5 Message transfer 6.1.6 Link recovery and resends 6.1.7 Error management 6.1.8 Message structure |
| 47 | 6.2 AMQP high-level implementation: the client/broker model Figure 28 โ Structure of an AMQP message |
| 48 | 6.3 AMQP implementation in MADES components Table 3 โ Services of the client / broker model |
| 49 | Figure 29 โ AMQP in MADES components |
| 50 | 6.4 Management of AMQP connections and attachments by an endpoint Table 4 โ Rules for setting up connection/attachment and for message transfer |
| 51 | 6.5 Internal message format 6.5.1 Definitions, design and security checks 6.5.2 AMQP format for transferring internal messages Table 5 โ Internal message โ AMQP format: header section Table 6 โ Internal message โ AMQP format: properties section |
| 52 | 6.5.3 Encryption Table 7 โ Internal message โ AMQP format: application-properties section Table 8 โ Internal message โ AMQP format: application-data section |
| 53 | 6.5.4 Signing Table 9 โ Encryption โ Processing metadata attributes for the “AES-256” cipher |
| 54 | 6.5.5 Internal message metadata Table 10 โ Signing โ Processing metadata attributes for the “SHA-512” Algorithm |
| 55 | Table 11 โ MessageMetadata (type) |
| 56 | Table 12 โ InternalMessageType (type: string enumeration) Table 13 โ ProcessingMetadata (type) Table 14 โ MessageProcessor (type) Table 15 โ Map (type) Table 16 โ MapEntry (type) |
| 57 | Table 17 โ ValueType (type: string enumeration) |
| 58 | 6.5.6 XML signature example |
| 59 | 7 Managing configuration data of the system 7.1 Rationale 7.2 Directory content and information ownership |
| 60 | Table 18 โ Component-directory โ content of an entry Table 19 โ Certificate (type) |
| 61 | 7.3 On the consistency of configuration data 7.3.1 Component consistency Table 20 โ MadesImplementation (type) Table 21 โ MessagePath (type) Table 22 โ BrokerRestriction (type) |
| 62 | 7.3.2 System consistency 7.3.3 Distributed update implementation 7.3.4 Eventual consistency 7.4 Connection to a component-directory |
| 63 | 7.5 REST API implementation and available resources Table 23 โ HTTP operations Table 24 โ HTTP return codes |
| 64 | 7.6 Registration process Table 25 โ Component-directory API |
| 65 | 7.7 Synchronisation process 7.7.1 Validity period of replicated data: time-to-live 7.7.2 Limitation of the synchronisation flow |
| 66 | 7.7.3 Configuration of the synchronisation process 7.8 XML schemas of the APIs requests and responses 7.8.1 Shared types |
| 68 | 7.8.2 registrations resource |
| 70 | 7.8.3 endpoints, brokers and components resources |
| 71 | 8 Managing the certificates 8.1 Definitions and principles |
| 72 | 8.2 Certificates: format and unique ID 8.3 Used certificates and issuers certificates authorities 8.3.1 Overview 8.3.2 Transport-layer security (authorise data exchanges) Figure 30 โ Certificates and certification authorities (CAs) of a MADES system |
| 73 | 8.3.3 Message-level security (protect message confidentiality and authenticate message issuer) 8.4 Trusting the certificates of others components 8.4.1 Authentication 8.4.2 Signing and encryption 8.5 Renewing the (nearly) expired certificates |
| 74 | 8.6 Revoking a component 9 Managing the version of the MADES specification 9.1 MADES version of this document 9.2 Issue, version meaning, upgrading recommendations |
| 75 | 9.3 Changing the signature or the encryption algorithms 10 Administrating and operating the components |
| 76 | 11 Interfaces for the applications 11.1 Endpoint webservice interface for applications 11.1.1 Overview |
| 77 | 11.1.2 SendMessage service Table 26 โ Endpoint interface โ Generic error Table 27 โ Endpoint interface โ Value for errorCode Table 28 โ SendMessage โ Request elements |
| 78 | 11.1.3 ReceiveMessage service Table 29 โ SentMessage (type) Table 30 โ SendMessage โ Response elements Table 31 โ SendMessage โ Additional error elements |
| 79 | Table 32 โ ReceiveMessage โ Request elements Table 33 โ ReceiveMessage โ Response elements Table 34 โ ReceivedMessage (type) Table 35 โ ReceiveMessage โ Additional error elements |
| 80 | 11.1.4 ConfirmReceiveMessage service 11.1.5 CheckMessageStatus service Table 36 โ ConfirmReceiveMessage โ Request elements Table 37 โ ConfirmReceiveMessage โ Response elements Table 38 โ ConfirmReceiveMessage โ Additional error elements Table 39 โ CheckMessageStatus โ Request elements |
| 81 | Table 40 โ CheckMessageStatus โ Response elements Table 41 โ MessageStatus (type) Table 42 โ MessageTraceItem (type) Table 43 โ MessageState or MessageTraceState (Type: string enumeration) |
| 82 | 11.1.6 ConnectivityTest service 11.1.7 WSDL for the endpoint webservice interface Table 44 โ CheckMessageStatus โ Additional error elements Table 45 โ ConnectivityTest โ Request elements Table 46 โ ConnectivityTest โ Response elements Table 47 โ ConnectivityTest โ Additional error elements |
| 83 | Figure 31 โ WSDL 1.1 definitions |
| 89 | 11.2 File System Shared Folders (FSSF) 11.2.1 Overview 11.2.2 Folders and file naming convention |
| 90 | Table 48 โ FSSF โ Folders and filename format Table 49 โ FSSF โ Tokens used to generate the filenames |
| 91 | 11.2.3 Concurrent access to files 11.2.4 Configuring FSSF |
| 92 | Bibliography |
