To present the already motivated idea of a highly reconfigurable and reliable communication service in a conceptual process three separate aspects are investigated. First, an overview of the involved components and information are shown which are used in the context of the project i-Automate. Second, specific information for the used communication service is given. Finally, the specific information is used to present the concept for a highly reconfigurable data distribution service.
The project i-Automate is focused on the LV/MV grid and therefore Intelligent Electronic Devices (IEDs) are used to measure grid information. The IEDs are able to run different applications and functionalities like voltage control or state estimation. To configure the functionalities in a standardized way the IEC 61850 Substation Configuration description Language (SCL) file is used. For example, the IED Capability Description (ICD) file describes all capabilities of an IED. Based on this a specific Instantiated IED Description (IID) file can be processed to describe the functions and objects of a specific IED. For some of the specified functions it is necessary to have not only their own provided measurements but also information from other parts of the grid, which is provided by other IEDs. Therefore, the IEDs needs an application that provides a communication service and under the consideration of reliability and resilience, this service must be highly reconfigurable. In the context of i-Automate a middleware called OpenDDS is used. For a better comprehension, the next paragraph explains the capabilities of OpenDDS in a more detail.
OpenDDS is an open source C++ implementation of the Object Management Group (OMG) Data Distribution Service (DDS). DDS itself is a middleware standard and provides a publish-subscribe pattern to enable scalability, real-time, high-performance and interoperable data exchange. In the following, Fig. 1 introduces the data-centric publish-subscribe (DCPS) concept of OpenDDS.
-
Domain: Is a fundamental partitioning unit and each of the other entities belongs to a domain and can only interact with other entities of the domain.
-
Topic: Describes the interaction between the publishing and subscribing application, so that samples for different instances of topics are published and the subscribers requests on this instances of topics to get the data.
-
DataWriter: The data writer’s type-specific interface is used to publish samples of the topic and is responsible for serializing the data.
-
Publisher: Disseminate the data to all relevant subscribers in the domain.
-
Subscriber: It receives the data from publisher and passes it to the relevant data readers connected.
-
DataReader: takes the data from the Subscriber, to deserialize it into the appropriate type of topic. Afterwards the data reader forward the information to the application.
For the data transmission, OpenDDS provide a specific extensible transport framework (ETF) as shown in Fig. 2. This framework gives the opportunity of different pluggable transport and discovery options. For this reason, TCP, UDP, multicast, shared-memory and RTPS_UDP are available for the transport and two types of discovery are distinguished. First, the centralized discovery with DCPSInfoRepo, which use a centralized repository style, that runs as a separate process allowing publishers and subscribers to discover one another centrally. On the other side, the RTPS discovery that use the peer-to-peer style and utilizes the RTPS protocol to advertise availability and location information.
Together with the information about the middleware that should be used as the data distribution service the conceptual proceeding can be described as follows. Consequently, based on the topologically separation of different IEDs it is possible to build cluster of IEDs there have a similar topological location (as presented in Fig. 3).
For each of the cluster one main responsible IED can aggregate or preprocess information depending on the functionality that is provided. In large scale application a subset of responsible IEDs of all clusters can build again a cluster and provide a hierarchical structure until one main responsible IED is able to aggregate all information. Each of the cluster map to one domain of the DCPS provided by OpenDDS and all IEDs inside of this domain can reach each other by multicast.
The data that have to be exchanged are modelled as a topic inside of each domain and each IED contains publisher and subscriber implementation together with their topic information of their interest. Now each IED inside of a cluster is able to publish or subscribe there samples. A concrete example can be seen by Fig. 4 where three IEDs are connected in the same domain and each of them provides a publisher and subscriber. In this example, the master IED wants to aggregate the information from topic 1 and topic 2 for that the device must only know the topics. The slaves 1 and 2 publish on three topics also only need to know about the topics and not about other IEDs. To illustrate why this concept of flexible and reconfigurable data sharing increase the reliability and resilience of the system, the following scenarios can be investigated:
-
Based on Fig. 4 the master provide a function that needs the information of topic 1 and topic 2. In the case of disconnection of the master, one of the slaves can take over the task. Therefore, slave one reconfigure his communication links by subscribing on the information of topic 1. To realize this reconfiguration the slave one needs only the knowledge about the functionality that runs normally on the master and the necessary topics. To subscribe on the topic 1 OpenDDS use IP multi-cast to share meta-data about the provided topics.
-
For the case that two IEDs are available in the same substations and both are able to provide the same data, OpenDDS provides a technique called hot-swap that can be used to switch the publisher for a topic in real time to avoid that parts of the grid information are unavailable.
To configure the OpenDDS on each IED an extension of the SCL file is been used. This extension provides an additional file with the information about the topics that each of the IEDs have to publish or subscribe. This file is used on a separated server where OpenDDS are preconfigured. With regard to the underlying architecture of the IEDs these configured configuration of OpenDDS will be cross compiled and transferred to the devices. Finally all publisher provides there topics and the data samples that should be exchanged and all subscriber subscribe on the topics of their interest.
