ДСТУ IEC TS 62325-503:2016 Инфраструктура коммуникаций на энергетическом рынке. Часть 503. Руководство по обмену данными рынка для профиля согласно с ІЕС 62325-351 (IEC TS 62325-503:2014, ІDТ)

Данный документ доступнен в тарифе «ВСЕ ВКЛЮЧЕНО»

У Вас есть вопросы по документу? Мы рады на них ответить!Перечень бесплатных документовОбнаружили ошибку в документе или на сайте? Пожалуйста, напишите нам об этом!Оставить заявку на документ

НАЦІОНАЛЬНИЙ СТАНДАРТ УКРАЇНИ

IEC TS 62325-503:2014

FRAMEWORK FOR ENERGY MARKET COMMUNICATIONS
Part 503: Market data exchanges guidelines for the IEC 62325-351 profile

ДСТУ IEC TS 62325-503:2016
(IEC TS 62325-503:2014, ІDТ)

ІНФРАСТРУКТУРА КОМУНІКАЦІЙ НА ЕНЕРГЕТИЧНОМУ РИНКУ
Частина 503. Настанови щодо обміну даними ринку для профілю згідно з ІЕС 62325-351

 

Київ
   
(ДП «УкрНДНЦ»)
2016

ПЕРЕДМОВА

1 ВНЕСЕНО: ТОВ «Укренергоналадка», Технічний комітет стандартизації «Керування енергетичними системами та пов’язані з ним процеси інформаційної взаємодії» (ТК 162)

2 НАДАНО ЧИННОСТІ: наказ    
(ДП «УкрНДНЦ») від 24 червня 2016 р. № 187 з 2016–09–01

3 Національний стандарт відповідає IEC TS 62325-503:2014 «Framework for energy market communications — Part 503: Market data exchanges guidelines for the IEC 62325-351 profile» (Інфраструктура комунікацій на енергетичному ринку. Частина 503. Настанови щодо обміну даними ринку для профілю згідно з ІЕС 62325-351)

Ступінь відповідності — ідентичний (IDT)

4 УВЕДЕНО ВПЕРШЕ

НАЦІОНАЛЬНИЙ ВСТУП

Цей національний стандарт, прийнятий методом передруку, — ідентичний щодо IEC TS 62325-503:2014 «Framework for energy market communications — Part 503: Market data exchanges guidelines for the IEC 62325-351 profile» (Інфраструктура комунікацій на енергетичному ринку. Частина 503. Настанови щодо обміну даними ринку для профілю згідно з ІЕС 62325-351).

Технічний комітет стандартизації, відповідальний за цей стандарт в Україні, — ТК 162 «Керування енергетичними системами та пов’язані з ним процеси інформаційної взаємодії».

У цьому національному стандарті зазначено вимоги, які відповідають законодавству України.

Структурні елементи цього стандарту: «Титульний аркуш», «Передмова», «Національний вступ» та «Бібліографічні дані» — оформлено згідно з вимогами національної стандартизації.

CONTENTS

FOREWORD

INTRODUCTION

1 Scope

2 Normative references

3 Terms and definitions

4 High level concepts

4.1What is MADES intended for?

4.2 General overview  

4.3 Message delivery and transparency

4.3.1 Message delivery  

4.3.2 Transparency

4.4 Security and reliability  

4.5 Main components  

4.6 Distributed architecture   

4.7 Components’ exposed interfaces

4.8 Security features

4.8.1 Overview

4.8.2 Transport-layer security

4.8.3 Message-level security

4.8.4 Non repudiation

5 Components’ functions

5.1 Routing messages

5.2 Component and message unique identification (ID)

5.3 Business-type of a business-message

5.4 Delivery-status of a business-message

5.5 Communication between components

5.5.1 Principle

5.5.2 Establishing a secured communication channel between two components

5.5.3 Token authentication of the client component

5.5.4 Request authorisation

5.5.5 Request/Reply validation

5.6 Storing messages in components

5.7 Lifecycle of a message state within a component

5.8 Transferring a message between two components (Handshake)

5.9 Accepting a message

5.10 Event management

5.10.1 Acknowledgements

5.10.2 Notifying events

5.10.3 Lifecycle of an acknowledgement

5.10.4 Processing a transferred acknowledgement

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)

5.13 Ordering the messages (Priority)

5.14 Endpoint

5.14.1 Endpoint functions

5.14.2 Compression

5.14.3 Signing

5.14.4 Encryption

5.15 Node

5.15.1 Node functions

5.15.2 Synchronizing directory with other nodes

5.15.3 Updating the synchronization nodes list

5.16 Certificates and directory management

5.16.1 Definitions and principles

5.16.2 Certificates: Format and unique ID

5.16.3 Used certificates and issuers (CAs)

5.16.4 Directory services

5.16.5 Caching directory data

5.16.6 Trusting the certificates of others components

5.16.7 Renewing the expired certificates

5.16.8 Revoking a certificate

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

6.1.4 Message compatibility

6.1.5 Interface with BAs

6.2 Using the correct version for services and messages

6.2.1 Node synchronization and authentication

6.2.2 Directory services and Network acceptance

6.2.3 Messaging services

6.2.4 Which version to use to send a message?

7 Interfaces and services

7.1 Overview

7.1.1 General

7.1.2 Error Codes

7.1.3 Types for Time

7.2 Endpoint interface

7.2.1 Overview

7.2.2 Services

7.2.3 File System Shared Folders (FSSF)

7.3 Node interface

7.3.1 Overview

7.3.2 Authentication service

7.3.3 Messaging Services

7.3.4 Directory services

7.3.5 Node Synchronization interface

7.4 Format of the node-list file

7.5 Typed Elements used by the interfaces

7.6 Description of the services

7.6.1 About WSDL and SOAP

7.6.2 Endpoint interface

7.6.3 Node interface

7.6.4 XML signature example

Figure 1 – MADES overall view

Figure 2 – MADES scope

Figure 3 – MADES key features

Figure 4 – MADES message delivery overview

Figure 5 – MADES security and reliability

Figure 6 – MADES components

Figure 7 – MADES network distributed architecture

Figure 8 – MADES interfaces and services

Figure 9 – MADES transport security overview

Figure 10 – MADES secure communication initiation

Figure 11 – Message signature

Figure 12 – Message encryption and decryption

Figure 13 – Non repudiation

Figure 14 – Delivery route of a business-message

Figure 15 – Reported events during the delivery of a business-message

Figure 16 – Lifecycle of the local state of a business-message within a component

Figure 17 – Transfer handshake when uploading of a message

Figure 18 – Transfer handshake when downloading of a message

Figure 19 – Acknowledgements along the route of the business-message

Figure 20 – Encryption process

Figure 21 – A node synchronizes with two other nodes

Figure 22 – Certificates and certificate authorities (CAs) for a MADES network

Figure 23 – Managing the specification version – node synchronization and authentication

Figure 24 – Managing the specification version – Directory services

Figure 25 – Managing the specification version – Messaging services

Figure 26 – Managing the specification version – Which version to use to send a message?

Figure 27 – Node interface – Overview

Figure 28 – Node interface – Authentication service

Figure 29 – Node interface – Messaging services – UploadMessages service

Figure 30 – Node interface – Messaging services – DownloadMessages service

Figure 31 – Node interface – Messaging services – ConfirmDownload service

Figure 32 – Node interface – Directory services – GetCertificate service

Figure 33 – Node interface – Directory services – GetComponent service

Figure 34 – WSDL 1.1 definitions

Table 1 – Message delivery status

Table 2 – Business message status

Table 3 – Accepting a message – Validation checks

Table 4 – Characteristics of notified events

Table 5 – Event characteristics description

Table 6 – Acknowledgement state description

Table 7 – Compression – metadata attributes

Table 8 – Signing – metadata attributes

Table 9 – Encryption – metadata attributes

Table 10 – Consequences of a certificate revocation

Table 11 – Service compatibility – Possible changes

Table 12 – Which version to use to send a message?

Table 13 – Managing the specification version – Rejection conditions

Table 14 – Interfaces and services – Generic error

Table 15 – Interfaces and services – String value for errorCode

Table 16 – SendMessage – Service request elements

Table 17 – SendMessage – Service response elements

Table 18 – SendMessage – Additional error elements

Table 19 – ReceiveMessage – Service request elements

Table 20 – ReceiveMessage – Service response elements

Table 21 – ReceiveMessage – Additional error elements

Table 22 – CheckMessageStatus – Service request elements

Table 23 – CheckMessageStatus – Service response elements

Table 24 – CheckMessageStatus – Additional error elements

Table 25 – ConnectivityTest – Service request elements

Table 26 – ConnectivityTest – Service response elements

Table 27 – ConnectivityTest – Additional error elements

Table 28 – ConfirmReceiveMessage – Service request elements

Table 29 – ConfirmReceiveMessage – Service response elements

Table 30 – ConfirmReceiveMessage – Additional error elements

Table 31 – FSSF – Description and filename format

Table 32 – FSSF – Filename description

Table 33 – Authentication – Service request elements

Table 34 – Authentication – Service response elements

Table 35 – UploadMessages – Service request elements

Table 36 – UploadMessages – Service response elements

Table 37 – DownloadMessages – Service request elements

Table 38 – DownloadMessages – Service response elements

Table 39 – ConfirmDownload – Service request elements

Table 40 – ConfirmDownload – Service response elements

Table 41 – SetComponentMversion – Service request elements

Table 42 – SetComponentMversion – Service response elements

Table 43 – GetCertificate – Service request elements

Table 44 – GetCertificate – Service response elements

Table 45 – GetCertificate – Additional conditions

Table 46 – GetComponent – Service request elements

Table 47 – GetComponent – Service response elements

Table 48 – GetNodeMversion – Service request elements

Table 49 – GetNodeMversion – Service response elements

Table 50 – GetAllDirectoryData – Service request elements

Table 51 – GetAllDirectoryData – Service response elements

Table 52 – Node attributes ordered list

Table 53 – AuthenticationToken

Table 54 – Certificate

Table 55 – CertificateType – string enumeration

Table 56 – ComponentCertificate

Table 57 – ComponentDescription

Table 58 – ComponentInformation

Table 59 – ComponentType – string enumeration

Table 60 – Endpoint

Table 61 – InternalMessage

Table 62 – InternalMessageType – string enumeration

Table 63 – MessageMetadata

Table 64 – MessageProcessor

Table 65 – Map

Table 66 – MapEntry

Table 67 – ValueType (enumeration)

Table 68 – MessageState (string enumeration)

Table 69 – MessageStatus

Table 70 – MessageTraceItem

Table 71 – MessageTraceState (string enumeration)

Table 72 – NotConfirmedMessageResponse

Table 73 – NotUploadedMessageResponse

Table 74 – ReceivedMessage

Table 75 – RoutingInformation

Table 76 – SentMessage

Полная версия документа доступна в тарифе «ВСЕ ВКЛЮЧЕНО».

Войти в Личный кабинет Подробнее о тарифах

БУДСТАНДАРТ Online