This technical specification is for European electricity markets.<\/p>\n
This document specifies a standard for a communication platform which every Transmission System Operator (TSO) in Europe may use to reliably and securely exchange documents for the energy market. Consequently a European market participant (trader, distribution utilities, etc.) could benefit from a single, common, harmonized and secure platform for message exchange with the different TSOs; thus reducing the cost of building different IT platforms to interface with all the parties involved. This also represents an important step in facilitating parties entering into markets other than their national ones.<\/p>\n
From now on the acronym \u201cMADES\u201d (MArket Data ExchangeS) will be used to designate these Technical Specifications.<\/p>\n
MADES is a specification for a decentralized common communication platform based on international IT protocol standards:<\/p>\n
From a business application (BA) perspective, MADES specifies software interfaces to exchange electronic documents with other BAs. Such interfaces mainly provide means to send and receive documents using a so-called \u201cMADES network\u201d. Every step of the delivery process is acknowledged, and the sender can request about the delivery status of a document. This is done through acknowledgement, which are messages returned back to the sender. This makes MADES networks usable for exchanging documents in business processes requiring reliable delivery.<\/p>\n<\/li>\n
MADES also specifies all services for the business application (BA); the complexities of recipient localisation, recipient connection status, message routing and security are hidden from the connecting BA. MADES services include directory, authentication, encryption, signing, message tracking, message logging and temporary message storage.<\/p>\n<\/li>\n<\/ul>\n
The purpose of MADES is to create a data exchange standard comprised of standard protocols and utilizing IT best practices to create a mechanism for exchanging data over any TCP\/IP communication network, in order to facilitate business to business information exchanges as described in IEC 62325-351 and the IEC 62325-451 series.<\/p>\n
A MADES network acts as a post-office organization. The transported object is a \u201cmessage\u201d in which the sender document is securely repackaged in an envelope (i.e. a header) containing all the necessary information for tracking, transportation and delivery.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4 High level concepts 4.1 What is MADES intended for? Figures Figure 1 \u2013 MADES overall view <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.2 General overview Figure 2 \u2013 MADES scope Figure 3 \u2013 MADES key features <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4.3 Message delivery and transparency 4.3.1 Message delivery 4.3.2 Transparency Figure 4 \u2013 MADES message delivery overview <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4.4 Security and reliability Figure 5 \u2013 MADES security and reliability <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 4.5 Main components Figure 6 \u2013 MADES components <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 4.6 Distributed architecture Figure 7 \u2013 MADES network distributed architecture <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 4.7 Components\u2019 exposed interfaces 4.8 Security features 4.8.1 Overview Figure 8 \u2013 MADES interfaces and services <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 4.8.2 Transport-layer security Figure 9 \u2013 MADES transport security overview Figure 10 \u2013 MADES secure communication initiation <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 4.8.3 Message-level security Figure 11 \u2013 Message signature Figure 12 \u2013 Message encryption and decryption <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 4.8.4 Non repudiation Figure 13 \u2013 Non repudiation <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5 Components\u2019 functions 5.1 Routing messages Figure 14 \u2013 Delivery route of a business-message <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 5.2 Component and message unique identification (ID) 5.3 Business-type of a business-message 5.4 Delivery-status of a business-message <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | Figure 15 \u2013 Reported events during the delivery of a business-message <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 5.5 Communication between components 5.5.1 Principle 5.5.2 Establishing a secured communication channel between two components Tables Table 1 \u2013 Message delivery status <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.5.3 Token authentication of the client component 5.5.4 Request authorisation 5.5.5 Request\/Reply validation <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 5.6 Storing messages in components 5.7 Lifecycle of a message state within a component <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Figure 16 \u2013 Lifecycle of the local state of a business-message within a component Table 2 \u2013 Business message status <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.8 Transferring a message between two components (Handshake) Figure 17 \u2013 Transfer handshake when uploading of a message <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 5.9 Accepting a message Figure 18 \u2013 Transfer handshake when downloading of a message <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 5.10 Event management 5.10.1 Acknowledgements Table 3 \u2013 Accepting a message \u2013 Validation checks <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 5.10.2 Notifying events Figure 19 \u2013 Acknowledgements along the route of the business-message <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Table 4 \u2013 Characteristics of notified events <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 5.10.3 Lifecycle of an acknowledgement 5.10.4 Processing a transferred acknowledgement Table 5 \u2013 Event characteristics description Table 6 \u2013 Acknowledgement state description <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 5.11 Message expiration 5.11.1 Principle 5.11.2 Setting the expiration time of a message: 5.11.3 Looking for the expired messages: 5.12 Checking the connectivity between two endpoints (Tracing-messages) <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 5.13 Ordering the messages (Priority) 5.14 Endpoint 5.14.1 Endpoint functions <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 5.14.2 Compression <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 5.14.3 Signing Table 7 \u2013 Compression \u2013 metadata attributes <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 5.14.4 Encryption Table 8 \u2013 Signing \u2013 metadata attributes <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | Figure 20 \u2013 Encryption process Table 9 \u2013 Encryption \u2013 metadata attributes <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 5.15 Node 5.15.1 Node functions 5.15.2 Synchronizing directory with other nodes <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 5.15.3 Updating the synchronization nodes\u2019 list Figure 21 \u2013 A node synchronizes with two other nodes <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 5.16 Certificates and directory management 5.16.1 Definitions and principles <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 5.16.2 Certificates: Format and unique ID 5.16.3 Used certificates and issuers (CAs) <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Figure 22 \u2013 Certificates and certificate authorities (CAs) for a MADES network <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 5.16.4 Directory services 5.16.5 Caching directory data <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 5.16.6 Trusting the certificates of others components 5.16.7 Renewing the expired certificates <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 5.16.8 Revoking a certificate Table 10 \u2013 Consequences of a certificate revocation <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 6 Managing the version of the MADES specification 6.1 Issues and principles 6.1.1 General 6.1.2 Rolling out a new version (Mversion and N-compliance) 6.1.3 Service compatibility <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 6.1.4 Message compatibility 6.1.5 Interface with BAs Table 11 \u2013 Service compatibility \u2013 Possible changes <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 6.2 Using the correct version for services and messages 6.2.1 Node synchronization and authentication Figure 23 \u2013 Managing the specification version \u2013 node synchronization and authentication <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 6.2.2 Directory services and Network acceptance Figure 24 \u2013 Managing the specification version \u2013 Directory services <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 6.2.3 Messaging services 6.2.4 Which version to use to send a message? Figure 25 \u2013 Managing the specification version \u2013 Messaging services <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | Figure 26 \u2013 Managing the specification version \u2013 Which version to use to send a message? Table 12 \u2013 Which version to use to send a message? Table 13 \u2013 Managing the specification version \u2013 Rejection conditions <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 7 Interfaces and services 7.1 Overview 7.1.1 General 7.1.2 Error Codes 7.1.3 Types for Time Table 14 \u2013 Interfaces and services \u2013 Generic error Table 15 \u2013 Interfaces and services \u2013 String value for errorCode <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 7.2 Endpoint interface 7.2.1 Overview 7.2.2 Services Table 16 \u2013 SendMessage \u2013 Service request elements <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | Table 17 \u2013 SendMessage \u2013 Service response elements Table 18 \u2013 SendMessage \u2013 Additional error elements Table 19 \u2013 ReceiveMessage \u2013 Service request elements Table 20 \u2013 ReceiveMessage \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | Table 21 \u2013 ReceiveMessage \u2013 Additional error elements Table 22 \u2013 CheckMessageStatus \u2013 Service request elements Table 23 \u2013 CheckMessageStatus \u2013 Service response elements Table 24 \u2013 CheckMessageStatus \u2013 Additional error elements <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | Table 25 \u2013 ConnectivityTest \u2013 Service request elements Table 26 \u2013 ConnectivityTest \u2013 Service response elements Table 27 \u2013 ConnectivityTest \u2013 Additional error elements Table 28 \u2013 ConfirmReceiveMessage \u2013 Service request elements Table 29 \u2013 ConfirmReceiveMessage \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 7.2.3 File System Shared Folders (FSSF) Table 30 \u2013 ConfirmReceiveMessage \u2013 Additional error elements <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | Table 31 \u2013 FSSF \u2013 Description and filename format Table 32 \u2013 FSSF \u2013 Filename description <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | 7.3 Node interface 7.3.1 Overview <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 7.3.2 Authentication service Figure 27 \u2013 Node interface \u2013 Overview Figure 28 \u2013 Node interface \u2013 Authentication service <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 7.3.3 Messaging Services Table 33 \u2013 Authentication \u2013 Service request elements Table 34 \u2013 Authentication \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | Figure 29 \u2013 Node interface \u2013 Messaging services \u2013 UploadMessages service Table 35 \u2013 UploadMessages \u2013 Service request elements Table 36 \u2013 UploadMessages \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | Figure 30 \u2013 Node interface \u2013 Messaging services \u2013 DownloadMessages service Table 37 \u2013 DownloadMessages \u2013 Service request elements Table 38 \u2013 DownloadMessages \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | 7.3.4 Directory services Figure 31 \u2013 Node interface \u2013 Messaging services \u2013 ConfirmDownload service Table 39 \u2013 ConfirmDownload \u2013 Service request elements Table 40 \u2013 ConfirmDownload \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | Figure 32 \u2013 Node interface \u2013 Directory services \u2013 GetCertificate service Table 41 \u2013 SetComponentMversion \u2013 Service request elements Table 42 \u2013 SetComponentMversion \u2013 Service response elements <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | Table 43 \u2013 GetCertificate \u2013 Service request elements Table 44 \u2013 GetCertificate \u2013 Service response elements Table 45 \u2013 GetCertificate \u2013 Additional conditions <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | 7.3.5 Node Synchronization interface Figure 33 \u2013 Node interface \u2013 Directory services \u2013 GetComponent service Table 46 \u2013 GetComponent \u2013 Service request elements Table 47 \u2013 GetComponent \u2013 Service response elements Table 48 \u2013 GetNodeMversion \u2013 Service request elements <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | 7.4 Format of the node-list file Table 49 \u2013 GetNodeMversion \u2013 Service response elements Table 50 \u2013 GetAllDirectoryData \u2013 Service request elements Table 51 \u2013 GetAllDirectoryData \u2013 Service response elements Table 52 \u2013 Node attributes ordered list <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | 7.5 Typed Elements used by the interfaces Table 53 \u2013 AuthenticationToken Table 54 \u2013 Certificate Table 55 \u2013 CertificateType \u2013 string enumeration Table 56 \u2013 ComponentCertificate <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | Table 57 \u2013 ComponentDescription Table 58 \u2013 ComponentInformation Table 59 \u2013 ComponentType \u2013 string enumeration Table 60 \u2013 Endpoint <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | Table 61 \u2013 InternalMessage <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | Table 62 \u2013 InternalMessageType \u2013 string enumeration Table 63 \u2013 MessageMetadata Table 64 \u2013 MessageProcessor Table 65 \u2013 Map <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | Table 66 \u2013 MapEntry Table 67 \u2013 ValueType (enumeration) Table 68 \u2013 MessageState (string enumeration) Table 69 \u2013 MessageStatus <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | Table 70 \u2013 MessageTraceItem Table 71 \u2013 MessageTraceState (string enumeration) Table 72 \u2013 NotConfirmedMessageResponse <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | Table 73 \u2013 NotUploadedMessageResponse Table 74 \u2013 ReceivedMessage Table 75 \u2013 RoutingInformation Table 76 \u2013 SentMessage <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | 7.6 Description of the services 7.6.1 About WSDL and SOAP 7.6.2 Endpoint interface Figure 34 \u2013 WSDL 1.1 definitions <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | 7.6.3 Node interface <\/td>\n<\/tr>\n | ||||||
| 102<\/td>\n | 7.6.4 XML signature example <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Framework for energy market communications – Market data exchanges guidelines for the IEC 62325-351 profile<\/b><\/p>\n |