{"id":255656,"date":"2024-10-19T16:54:05","date_gmt":"2024-10-19T16:54:05","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-62325-5032018\/"},"modified":"2024-10-25T12:22:03","modified_gmt":"2024-10-25T12:22:03","slug":"bs-en-iec-62325-5032018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-62325-5032018\/","title":{"rendered":"BS EN IEC 62325-503:2018"},"content":{"rendered":"

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.<\/p>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
2<\/td>\nundefined <\/td>\n<\/tr>\n
5<\/td>\nAnnex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n
7<\/td>\nEnglish
CONTENTS <\/td>\n<\/tr>\n
12<\/td>\nFOREWORD <\/td>\n<\/tr>\n
14<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
15<\/td>\n1 Scope
2 Normative references <\/td>\n<\/tr>\n
16<\/td>\n3 Terms and definitions <\/td>\n<\/tr>\n
17<\/td>\n4 High level concepts
4.1 What is the purpose of MADES?
Figures
Figure 1 \u2013 MADES overall view <\/td>\n<\/tr>\n
18<\/td>\n4.2 Overview
Figure 2 \u2013 MADES scope in a layered architecture <\/td>\n<\/tr>\n
19<\/td>\n4.3 Transparent and reliable message delivery
Figure 3 \u2013 MADES message delivery <\/td>\n<\/tr>\n
20<\/td>\n4.4 Components of a MADES system
4.4.1 Endpoint, broker and component-directory
Figure 4 \u2013 MADES components, interactions and protocols <\/td>\n<\/tr>\n
21<\/td>\n4.4.2 Delivery routes and acknowledgements
Figure 5 \u2013 Possible routes for delivering a message <\/td>\n<\/tr>\n
22<\/td>\n4.4.3 Sharing configuration data of the system
Figure 6 \u2013 Communication protocols for delivering a message <\/td>\n<\/tr>\n
23<\/td>\nFigure 7 \u2013 Data flows between a component-directory and its registered components <\/td>\n<\/tr>\n
24<\/td>\n4.4.4 Interfaces exposed by the components
Figure 8 \u2013 Data flows with several component-directories
Figure 9 \u2013 Component-directory services and protocols <\/td>\n<\/tr>\n
25<\/td>\nFigure 10 \u2013 MADES Interfaces, services and protocols <\/td>\n<\/tr>\n
26<\/td>\n4.4.5 Architecture examples of MADES systems
Figure 11 \u2013 Minimal MADES system (without broker)
Figure 12 \u2013 Minimal MADES system (with broker) <\/td>\n<\/tr>\n
27<\/td>\nFigure 13 \u2013 MADES system with a party in a central role <\/td>\n<\/tr>\n
28<\/td>\nFigure 14 \u2013 MADES system with several brokers <\/td>\n<\/tr>\n
29<\/td>\n4.5 Security and message integrity
4.5.1 Security goals and security solution
Figure 15 \u2013 Using a single endpoint for several business processes <\/td>\n<\/tr>\n
30<\/td>\n4.5.2 Transport-layer security
Figure 16 \u2013 MADES transport security
Figure 17 \u2013 Security: protected endpoint <\/td>\n<\/tr>\n
31<\/td>\n4.5.3 Message-level security: signing and encryption
Figure 18 \u2013 Security: exposed endpoint
Figure 19 \u2013 Message signing and signature verification <\/td>\n<\/tr>\n
32<\/td>\n4.5.4 Non-repudiation
Figure 20 \u2013 Message encryption and decryption <\/td>\n<\/tr>\n
33<\/td>\nFigure 21 \u2013 Non-repudiation <\/td>\n<\/tr>\n
34<\/td>\n5 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 <\/td>\n<\/tr>\n
36<\/td>\n5.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 <\/td>\n<\/tr>\n
37<\/td>\n5.6.2 Delivery events and acknowledgements
Figure 22 \u2013 Message-status along the delivery <\/td>\n<\/tr>\n
38<\/td>\nFigure 23 \u2013 Tracking events while delivering a message <\/td>\n<\/tr>\n
39<\/td>\n5.7 Message expiration
Tables
Table 1 \u2013 Characteristics of the tracking events <\/td>\n<\/tr>\n
40<\/td>\n5.8 Reliable transfer of a message
5.8.1 Rationale <\/td>\n<\/tr>\n
41<\/td>\n5.8.2 Transfer between sender application and sender endpoint
Figure 24 \u2013 Reliable transfer
Figure 25 \u2013Transfer between sender application and sender endpoint <\/td>\n<\/tr>\n
42<\/td>\n5.8.3 Transfer between components using the AMQP protocol
5.8.4 Transfer between recipient endpoint and recipient application
Figure 26 \u2013 Transfer between recipient endpoint and recipient application <\/td>\n<\/tr>\n
43<\/td>\n5.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 \u2013 Final state of a message in an endpoint <\/td>\n<\/tr>\n
44<\/td>\n6 Transferring messages using the AMQP protocol
6.1 Main principles of the AMQP specification
6.1.1 Introduction <\/td>\n<\/tr>\n
45<\/td>\n6.1.2 Connection Open
6.1.3 Session begin
Figure 27 \u2013 The nine AMQP frames <\/td>\n<\/tr>\n
46<\/td>\n6.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 <\/td>\n<\/tr>\n
47<\/td>\n6.2 AMQP high-level implementation: the client\/broker model
Figure 28 \u2013 Structure of an AMQP message <\/td>\n<\/tr>\n
48<\/td>\n6.3 AMQP implementation in MADES components
Table 3 \u2013 Services of the client \/ broker model <\/td>\n<\/tr>\n
49<\/td>\nFigure 29 \u2013 AMQP in MADES components <\/td>\n<\/tr>\n
50<\/td>\n6.4 Management of AMQP connections and attachments by an endpoint
Table 4 \u2013 Rules for setting up connection\/attachment and for message transfer <\/td>\n<\/tr>\n
51<\/td>\n6.5 Internal message format
6.5.1 Definitions, design and security checks
6.5.2 AMQP format for transferring internal messages
Table 5 \u2013 Internal message \u2013 AMQP format: header section
Table 6 \u2013 Internal message \u2013 AMQP format: properties section <\/td>\n<\/tr>\n
52<\/td>\n6.5.3 Encryption
Table 7 \u2013 Internal message \u2013 AMQP format: application-properties section
Table 8 \u2013 Internal message \u2013 AMQP format: application-data section <\/td>\n<\/tr>\n
53<\/td>\n6.5.4 Signing
Table 9 \u2013 Encryption \u2013 Processing metadata attributes for the “AES-256” cipher <\/td>\n<\/tr>\n
54<\/td>\n6.5.5 Internal message metadata
Table 10 \u2013 Signing \u2013 Processing metadata attributes for the “SHA-512” Algorithm <\/td>\n<\/tr>\n
55<\/td>\nTable 11 \u2013 MessageMetadata (type) <\/td>\n<\/tr>\n
56<\/td>\nTable 12 \u2013 InternalMessageType (type: string enumeration)
Table 13 \u2013 ProcessingMetadata (type)
Table 14 \u2013 MessageProcessor (type)
Table 15 \u2013 Map (type)
Table 16 \u2013 MapEntry (type) <\/td>\n<\/tr>\n
57<\/td>\nTable 17 \u2013 ValueType (type: string enumeration) <\/td>\n<\/tr>\n
58<\/td>\n6.5.6 XML signature example <\/td>\n<\/tr>\n
59<\/td>\n7 Managing configuration data of the system
7.1 Rationale
7.2 Directory content and information ownership <\/td>\n<\/tr>\n
60<\/td>\nTable 18 \u2013 Component-directory \u2013 content of an entry
Table 19 \u2013 Certificate (type) <\/td>\n<\/tr>\n
61<\/td>\n7.3 On the consistency of configuration data
7.3.1 Component consistency
Table 20 \u2013 MadesImplementation (type)
Table 21 \u2013 MessagePath (type)
Table 22 \u2013 BrokerRestriction (type) <\/td>\n<\/tr>\n
62<\/td>\n7.3.2 System consistency
7.3.3 Distributed update implementation
7.3.4 Eventual consistency
7.4 Connection to a component-directory <\/td>\n<\/tr>\n
63<\/td>\n7.5 REST API implementation and available resources
Table 23 \u2013 HTTP operations
Table 24 \u2013 HTTP return codes <\/td>\n<\/tr>\n
64<\/td>\n7.6 Registration process
Table 25 \u2013 Component-directory API <\/td>\n<\/tr>\n
65<\/td>\n7.7 Synchronisation process
7.7.1 Validity period of replicated data: time-to-live
7.7.2 Limitation of the synchronisation flow <\/td>\n<\/tr>\n
66<\/td>\n7.7.3 Configuration of the synchronisation process
7.8 XML schemas of the APIs requests and responses
7.8.1 Shared types <\/td>\n<\/tr>\n
68<\/td>\n7.8.2 registrations resource <\/td>\n<\/tr>\n
70<\/td>\n7.8.3 endpoints, brokers and components resources <\/td>\n<\/tr>\n
71<\/td>\n8 Managing the certificates
8.1 Definitions and principles <\/td>\n<\/tr>\n
72<\/td>\n8.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 \u2013 Certificates and certification authorities (CAs) of a MADES system <\/td>\n<\/tr>\n
73<\/td>\n8.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 <\/td>\n<\/tr>\n
74<\/td>\n8.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 <\/td>\n<\/tr>\n
75<\/td>\n9.3 Changing the signature or the encryption algorithms
10 Administrating and operating the components <\/td>\n<\/tr>\n
76<\/td>\n11 Interfaces for the applications
11.1 Endpoint webservice interface for applications
11.1.1 Overview <\/td>\n<\/tr>\n
77<\/td>\n11.1.2 SendMessage service
Table 26 \u2013 Endpoint interface \u2013 Generic error
Table 27 \u2013 Endpoint interface \u2013 Value for errorCode
Table 28 \u2013 SendMessage \u2013 Request elements <\/td>\n<\/tr>\n
78<\/td>\n11.1.3 ReceiveMessage service
Table 29 \u2013 SentMessage (type)
Table 30 \u2013 SendMessage \u2013 Response elements
Table 31 \u2013 SendMessage \u2013 Additional error elements <\/td>\n<\/tr>\n
79<\/td>\nTable 32 \u2013 ReceiveMessage \u2013 Request elements
Table 33 \u2013 ReceiveMessage \u2013 Response elements
Table 34 \u2013 ReceivedMessage (type)
Table 35 \u2013 ReceiveMessage \u2013 Additional error elements <\/td>\n<\/tr>\n
80<\/td>\n11.1.4 ConfirmReceiveMessage service
11.1.5 CheckMessageStatus service
Table 36 \u2013 ConfirmReceiveMessage \u2013 Request elements
Table 37 \u2013 ConfirmReceiveMessage \u2013 Response elements
Table 38 \u2013 ConfirmReceiveMessage \u2013 Additional error elements
Table 39 \u2013 CheckMessageStatus \u2013 Request elements <\/td>\n<\/tr>\n
81<\/td>\nTable 40 \u2013 CheckMessageStatus \u2013 Response elements
Table 41 \u2013 MessageStatus (type)
Table 42 \u2013 MessageTraceItem (type)
Table 43 \u2013 MessageState or MessageTraceState (Type: string enumeration) <\/td>\n<\/tr>\n
82<\/td>\n11.1.6 ConnectivityTest service
11.1.7 WSDL for the endpoint webservice interface
Table 44 \u2013 CheckMessageStatus \u2013 Additional error elements
Table 45 \u2013 ConnectivityTest \u2013 Request elements
Table 46 \u2013 ConnectivityTest \u2013 Response elements
Table 47 \u2013 ConnectivityTest \u2013 Additional error elements <\/td>\n<\/tr>\n
83<\/td>\nFigure 31 \u2013 WSDL 1.1 definitions <\/td>\n<\/tr>\n
89<\/td>\n11.2 File System Shared Folders (FSSF)
11.2.1 Overview
11.2.2 Folders and file naming convention <\/td>\n<\/tr>\n
90<\/td>\nTable 48 \u2013 FSSF \u2013 Folders and filename format
Table 49 \u2013 FSSF \u2013 Tokens used to generate the filenames <\/td>\n<\/tr>\n
91<\/td>\n11.2.3 Concurrent access to files
11.2.4 Configuring FSSF <\/td>\n<\/tr>\n
92<\/td>\nBibliography <\/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\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2018<\/td>\n94<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":255662,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-255656","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/255656","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/255662"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=255656"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=255656"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=255656"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}