KR102575836B1 - Protection coordination in distribution system using dds communication over an ethernet network - Google Patents

Abstract

A power distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention includes a transformer for converting a voltage of power transmitted from a power transmission line that is wired along a telephone pole and transmits power to suit use; a distribution device for supplying the power that is transformed and transmitted to the transformer to consumers; A terminal device for distribution automation that is connected to the distribution equipment to control distribution automation of the distribution equipment, detects and publishes failure information according to the occurrence of a failure; and a DDS in which a plurality of the distribution automation terminal devices are connected to receive the failure information published by any one distribution automation terminal device and provide other distribution automation terminal devices to subscribe to the corresponding failure information. It is a structure that performs peer-to-peer communication between communication devices without a central server, including a domain, and has high reliability because there is no effect on the entire communication due to communication failure of a specific node, and can overcome the disadvantages of the conventional Server-Client middleware. There is an effect.

Description

Distribution protection coordination system using DDS communication in Ethernet environment {PROTECTION COORDINATION IN DISTRIBUTION SYSTEM USING DDS COMMUNICATION OVER AN ETHERNET NETWORK}

The present invention relates to a distribution protection coordination system in an Ethernet environment using DDS communication, which is a new communication method of distribution line protection coordination performed by existing 1:1 serial communication.

CLS (Closed Loop System) protection cooperation refers to fault detection and fault direction information exchange between neighboring terminals for distribution automation in the event of a fault in a distribution line, using high-speed 1:1 communication to classify fault sections and automatically isolate them. is a mechanism for

Currently, CLS protection cooperation exchanges fault information through serial 1:1 communication as shown in FIG. As it is being developed, serial 1:1 communication is expected to be replaced in the future.

Therefore, as the Ethernet environment changes, it is necessary to selectively apply a communication method, protocol, and middleware to replace the existing serial communication for protection cooperation.

The commonly used Client-Server method of communication has a single point of failure (SPOF) in which the entire system becomes unable to communicate in case of a server failure, so reliability is lowered, and performance is lowered because it communicates through the server. It is a concern, and it is a structure that is not very suitable for protection cooperation in 1:1 communication.

The Point to Point (P2P) communication method, which has a communication structure relatively similar to the current serial communication, seems to be a communication method suitable for protection cooperation for 1:1 communication between terminal devices, but communication is reset when a new terminal device is added or deleted during operation. is required, and there is a cumbersome problem of restarting the system after resetting.

In the future, when the communication area is expanded, that is, when it is necessary to change to 1:N, M:N communication rather than the current 1:1 structure, and when location information such as IP address is changed due to network work, communication is also performed. There are cumbersome problems that need to be reset and the system must be restarted.

It is necessary to apply middleware with an international standard and a publish-subscriber communication structure to prevent vendor dependency, interoperate with external systems, and achieve flexible system expansion and efficient maintenance.

Republic of Korea Patent Registration No. 10-1090425 (2011. 11. 30)

In order to solve the above problems, the present invention applies DDS (Data Distribution Service) communication to the protection cooperation of the Ethernet environment-based distribution automation system (in particular, the protection cooperation of the closed loop system <CLS: Closed Loop System>), By enabling real-time exchange of fault information between devices, it is possible to more quickly and accurately determine and block fault sections when faults occur, and also enable flexible system expansion to enable efficient operation of the distribution automation system. Ethernet environment The purpose is to provide a distribution protection coordination system using DDS communication.

A power distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention for achieving the above object is a transformer for transforming the voltage of power transmitted from a power transmission line that is wired along a telephone pole and transmits power suitable for use; a distribution device for supplying the power that is transformed and transmitted to the transformer to consumers; A terminal device for distribution automation that is connected to the distribution equipment to control distribution automation of the distribution equipment, detects and publishes failure information according to the occurrence of a failure; and a DDS in which a plurality of the distribution automation terminal devices are connected to receive the failure information published by any one distribution automation terminal device and provide other distribution automation terminal devices to subscribe to the corresponding failure information. It is characterized in that it includes; domain.

Preferably, in the distribution protection coordination system using DDS communication in the Ethernet environment according to the present invention for achieving the above object, when the distribution automation terminal device is added, the added distribution automation terminal device has an ID assigned to it. Publish topic data including the IDs of the distribution automation terminals located on the left and right sides, and the connection information is changed when the left distribution automation terminals receive data from the added distribution automation terminals of the new ID. recognized, and changing the RIGHT_ID of the topic data to the ID of the added terminal device for distribution automation.

More preferably, in the distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention for achieving the above object, when the distribution automation terminal device is deleted, the deleted distribution automation terminal device cannot communicate with itself. It is determined that it is in the status or removed, and the left and right distribution automation terminal devices change the IDs of the mutual terminal devices to RIGHT_ID and LEFT_ID, respectively, using the topic information received from the deleted distribution automation terminal device.

Distribution protection coordination system using DDS communication in Ethernet environment according to the present invention

As a structure for peer-to-peer communication between communication devices without a central server, there is no effect on overall communication due to a communication failure of a specific node, so reliability is high, and there is an effect that can overcome the disadvantages of the conventional Server-Client middleware.

In the Ethernet environment according to the present invention, the distribution protection coordination system using DDS communication provides most of the communication setting tasks such as communication node search, negotiation, connection setting, and time synchronization, which had to be implemented directly in the past, in middleware, thereby reducing the development load of application developers. has a reducing effect.

In addition, the distribution protection coordination system using DDS communication in the Ethernet environment according to the present invention can filter communication data at the middleware level using the Contents Filtered Topic function, thereby reducing bandwidth waste and application development load.

In the Ethernet environment according to the present invention, the distribution protection coordination system using DDS communication has a built-in auto-discovery mechanism that dynamically searches for and connects communication nodes, so additional settings can be made when adding/deleting communication nodes (distribution terminal devices) Continuous communication is possible without code modification, so reliability is high and system expansion is very flexible.

1 is a diagram showing a failure information exchange system through 1:1 serial communication between adjacent terminal devices in the related art.
2 is a diagram illustrating a power distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
3 is a detailed block diagram of a terminal device for distribution automation included in a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
4 is a topic structure of a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
5 is an application example of Contents Filtered Topic of a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
6 is a diagram illustrating an example of adding a new distribution automation terminal device to a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
7 is a diagram illustrating a process of adding a new distribution automation terminal device to a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
8 is a diagram illustrating an example of deleting a terminal device for distribution automation in a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.
9 is a diagram illustrating a process of deleting a terminal device for distribution automation in a distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention.

The terms or words used in this specification and claims should not be construed as being limited to ordinary or dictionary meanings, and the inventors may appropriately define the concept of terms in order to explain their invention in the best way. Based on the principle that there is, it should be interpreted as meaning and concept consistent with the technical spirit of the present invention.

Therefore, since the embodiments described in this specification and the configurations shown in the drawings are only one of the most preferred embodiments of the present invention and do not represent all of the technical ideas of the present invention, they can be substituted at the time of this application It should be understood that there may be many equivalents and variations.

Hereinafter, a power distribution protection coordination system using DDS communication in an Ethernet environment according to the present invention will be described in detail with reference to the accompanying drawings.

As shown in FIG. 2 , it includes a plurality of transformers 100 , a distribution equipment 200 , a distribution automation terminal device 300 , and a DDS domain 400 .

The transformer 100 converts a voltage of power transmitted from a power transmission line that is wired along a telephone pole and transmits power to suit use.

The distributor 200 supplies the power that is transformed and transmitted to the transformer 100 to consumers.

The distribution automation terminal device 300 is connected to the distribution equipment 200 to control the distribution automation of the distribution equipment 200, and detects and publishes failure information according to the occurrence of a failure.

The DDS domain 400 is a virtual network space that receives the failure information published by any one terminal device for distribution automation 300 through a DDS topic, and any other terminal device for distribution automation 300 corresponds thereto. It provides failure information to be subscribed to.

That is, among the plurality of distribution automation terminal devices 300, any one of the distribution automation terminal devices 300 finds a terminal adjacent to itself through DDS rather than a 1:1 direct connection, and communication with the terminal is performed. It is done.

Another distribution machine 200 is connected between the distribution machines 200 so that a new distribution automation terminal device 300 is added or an arbitrary distribution machine 200 is removed between the distribution machines 200 to automate distribution Even if the terminal device 300 for distribution automation is deleted, the DDS included in the terminal device 300 for distribution automation dynamically resets the connection so that continuous communication is possible.

More specifically, as shown in FIG. 3 , the power distribution automation terminal device 300 has a DDS engine installed to implement a DDS application for protection coordination communication.

In particular, the distribution automation terminal device 300 includes a domain participant 310 and a DDS engine 320, and the domain participant 310 includes a publisher 330 and a subscription. It includes a subscriber (subscriber) 340. The publisher 330 includes a data writer (350) that transmits failure information to neighboring terminal devices, and the subscriber 340 includes a data writer (350) that transmits failure information to neighboring terminal devices. It includes a data reader (Data Reader: 360) for receiving failure information from.

In addition, the Domain Participant (310) includes the Contents Filtered Topic (Contents Filtered Topic) 370, and the corresponding Contents Filtered Topic (370) is filtered previously set in the data reader (360). Only data that satisfies the conditions is transmitted from the corresponding data writer 350 .

Meanwhile, the domain party 310 uses a filtering condition expression such as "RIGHT_ID==%0 OR LEFT_ID==%0" and a locally stored identification value such as "ID" as a filtering condition. It can be created as a parameter to be assigned.

The DDS engine 320 is a communication interface capable of exchanging fault information with other terminal devices for distribution automation 300 that are not close by accessing the DDS domain to which the terminal device for distribution automation 300 is connected.

Meanwhile, the topic (communication data) structure by the content-filtered topic 370 is as shown in FIG.

As shown in FIG. 4, the protection coordination communication information necessary for protection coordination includes unique identification ID information assigned to each distribution automation terminal device 300, and a terminal installed in the opposite direction (for example, to the left) from itself. It includes LEFT_ID information, which is the ID of the device, and RIGHT_ID information, which is the ID of the terminal device installed in the forward direction (eg, right direction) from itself.

In addition, information necessary for protection coordination (for example, fault direction, fault condition, etc.) should be defined as a field, but in the present invention, as an invention for a protection coordination communication method, only fields and contents necessary for communication are specifically presented, and the rest do not describe

The DDS engine 320 allows data to be published to all communication nodes having the same topic. However, in the protection coordination system, filtering is necessary because only the data issued by both adjacent terminal devices must be received and processed.

The function of the Contents Filtered Topic (330) defined in the DDS engine 320 is a function in which the data writer 350 transmits only data that meets the filtering conditions set in advance by the receiver, The data reader 360 can selectively receive only necessary data (or data within an effective range) among topic data.

Since the content filtered topic 330 provides the above-described filtering function, the developer's amount of development is reduced and the program is simplified.

The publisher 330 that transmits or publishes failure information, the subscriber 340 that receives or subscribes to information, and only data that meets the filtering conditions set in advance by the subscriber 340, which is the receiver side, the publisher ( 330) includes a Contents Filtered Topic (330) transmitted.

An example of applying the Contents Filtered Topic 330 will be described with reference to FIG. 5 .

As shown in FIG. 5, each of the distribution automation terminal devices 300 has 100, 200, and 300 as unique ID values. As shown in FIG. 3 , the power distribution automation terminal device 300 includes a data writer 350 that transmits data and a data reader 360 that receives data.

The data reader 360 sets a content-filtered topic, based on the distribution automation terminal device 300 No. 100 in the conditional expression "RIGHT_ID==%0 OR LEFT_ID==%0", parameter values to be entered in the conditional expression. is "RIGHT_ID==100 OR LEFT_ID==100".

That is, the distribution automation terminal device 300 number 100 may display topic data to be published as {ID=100, LEFT_ID=-1, RIGHT_ID=200, ...} when transmitting protection coordination data.

Before communication takes place, the Data Writer 350, which knows the filtering conditions of the matched Data Readers 360 in advance, while performing Discovery, a process of searching for a counterpart to communicate with, filters Data is transmitted only to the data reader (Data Reader: 360) of the terminal device 300 for distribution automation number 200 that meets the conditions.

That is, only the 200 distribution automation terminal devices 300 adjacent to the 100 distribution automation terminal devices 300 receive the failure information data of the 100 distribution automation terminal devices 300 .

The distribution equipment 200 connected to the distribution line uses the Contents Filtered Topic (330) function of the DDS engine 320 included in the distribution automation terminal device 300 to detect other distribution equipment adjacent to both sides. and exchange data for protection cooperation.

Meanwhile, as shown in FIG. 6 , when a new distribution equipment 200 is installed between existing distribution equipment 200, a new distribution automation terminal device 300 receives ID 400 and receives ID 200 correspondingly. It is added between terminal devices for distribution automation with and 300.

As the distribution automation terminal device 300 having an ID of 400 is added between numbers 200 and 300, the terminal device receives topic data {ID=400, LEFT_ID=200, RIGHT_ID=300, ...} is published.

While the terminal device 300 for distribution automation No. 200 communicates with the terminal devices No. 100 and 300, when data reception is confirmed from the terminal device with a new ID, it recognizes that the connection information has changed, and sets RIGHT_ID from the existing 300 to 400 ( 300 -> 400).

Similarly, the LEFT_ID of the distribution automation terminal device 300 number 300 is also changed from 200 to 400 (200->), and connection information of the terminal device is newly established.

As described above, the connection process of the distribution automation terminal device 300 according to the addition of the new distribution equipment 200 is as shown in FIG. 7 .

First, the distribution automation terminal device 300 sets its own identification information ID, RIGHT_ID for the right terminal, and LEFT_ID for the left terminal locally based on the terminal device circuit configuration information of the distribution device 200 is performed (S1).

As shown in FIG. 4 , the power distribution automation terminal device 300 performs a step of generating and setting entities corresponding to attributes for the distribution devices 200 (S2).

The power distribution automation terminal device 300 performs a step of transmitting and receiving protection coordination data using the data writer 350 and data reader 360 (S3).

Thereafter, the power distribution automation terminal device 300 performs a step of confirming whether the left and right IDs of the received data are the same as the information set in the entity created in the step S2 (S4).

If the ID information received in the step S4 is identical to and matches the set ID information, the transmitted data is received and a protection coordination algorithm is executed based on the received data (S5).

If the IDs received in step S4 are not the same, the distribution automation terminal device 300 determines that the left and right distribution devices 200 of the distribution device 200 are added or deleted and the left and right terminal devices are also changed, After performing the step of changing the received left/right data ID to a new left/right ID, the step S5 of performing the protection coordination algorithm is performed.

Next, a connection resetting process when the distribution equipment 200 is deleted on the line and the distribution automation terminal device 300 is deleted correspondingly will be described with reference to FIG. 8 .

In the Ethernet environment according to the present invention, the distribution protection coordination system using DDS communication provides 22 types of QoS (Quality of Service) policies that guarantee various communication quality with simple settings when implementing applications, and various publish-subscribe through QoS combinations. Communication environment can be configured.

Representative QoS provided are Reliability (setting the reliability level of communication <setting whether or not to retransmit lost data>, Durability (setting the level of continuity of communication <setting whether or not the communication node inserted in the middle will receive the previous exchanged history data) Whether or not>), Liveliness (Mechanism for notifying whether DataWriter is alive or not. DataWriter should propagate existence or non-existence to the domain every set lease_duration. If there is no signal during lease_duaration, DataWriter is regarded as failure/termination and notified to application through listener <on_liveliness_changed> ), History (sets the size of the history data queue to be stored in memory), and Lifespan (deletes from memory when the duration set as a policy to prevent storage and transmission of old data elapses).

Among them, the distribution automation terminal device 300 uses a Liveliness Quality of Service (QoS) function provided by the DDS engine 320 to determine changed communication information.

For example, as shown in FIG. 8 , when the distribution automation terminal device 300 having ID No. 200 is removed, the distribution automation terminal devices 300 numbered 100 and 400 adjacent to both ends are removed from the terminal device No. 200 for a set period of time. A Liveliness policy violation event occurs when Liveliness information is not received.

Then, the distribution automation terminal device 300 of No. 100 or 400 determines that the terminal device No. 200 is in a communication disabled state or has been removed from the site, and receives the topic information {ID=200}, LEFR_ID=100, RIGHT_ID of number 100 distribution automation terminal device 300 is changed to 400 and LEFT_ID of number 400 distribution automation terminal device is changed to 100 by using RIGHT_ID = 400, ...}.

As described above, when the power distribution device 200 is deleted on the line, the protection coordination data transmission/reception process between the data transmission side and the reception side is as shown in FIG. 9 .

In the above, the technical idea of the present invention has been described together with the accompanying drawings, but this is an illustrative example of a preferred embodiment of the present invention, but does not limit the present invention. In addition, it is obvious that various modifications and imitations can be made by anyone having ordinary knowledge in the technical field to which the present invention belongs without departing from the scope of the technical idea of the present invention.

100: transformer
200: Distributor
300: terminal device for distribution automation
310: Domain Participant
320: DDS engine
330: Publisher
340: Subscriber
350: Data Writer
360: Data Reader
400: DDS domain

Claims (7)

In a distribution protection coordination system using DDS communication in an Ethernet environment so that real-time fault information can be exchanged between terminal devices for distribution automation by applying DDS communication to protection coordination of a closed loop system,
a transformer that usably transforms a voltage of electric power transmitted from a power transmission line that is wired along a telephone pole and transmits electric power;
a power distribution device that supplies the power that is transformed and transmitted to the transformer to consumers;
A plurality of distribution automation terminal devices that are connected to the distribution equipment to control distribution automation of the distribution equipment, and to detect, publish, and subscribe to failure information according to a failure occurrence; and
A DDS domain in which a plurality of distribution automation terminal devices are connected to receive the failure information published by any one distribution automation terminal device and provide other distribution automation terminal devices to subscribe to the corresponding failure information including;
The plurality of terminal devices for distribution automation, which are participants in the DDS domain, include domain parties publishing and subscribing to failure information of the connected distribution equipment; and
A DDS engine that connects to the DDS domain to provide failure information published and receives fixed information published by other distribution automation terminal devices;
Even if another distribution equipment is connected between the distribution equipment and a new distribution automation terminal device is added, or a distribution automation terminal equipment is deleted as an arbitrary distribution equipment is removed between the distribution equipment, discovery that searches for the other party to communicate with (DISCOVERY ) The DDS engine included in the distribution automation terminal device performing the process dynamically resets the connection to enable continuous communication,
When the distribution automation terminal device is added, the added distribution automation terminal device includes the ID assigned to it and the ID of the distribution automation terminal device located on the left and right sides. Topic data ID = □, LEFT_ID = □, RIGHT_ID=□ is published, and when data reception is confirmed from the added distribution automation terminal device with a new ID, the left distribution automation terminal device recognizes that the connection information has been changed, and sets RIGHT_ID among the topic data to the added distribution automation terminal device. change to the ID of the terminal device for
When the distribution automation terminal device is deleted, the deleted distribution automation terminal device determines that it is unable to communicate or has been removed, and the left and right distribution automation terminal devices receive topics from the deleted distribution automation terminal device. Using the information, the ID of the mutual terminal device is changed to RIGHT_ID and LEFT_ID, respectively,
The domain party is
A publisher composed of a data writer that publishes failure information and transmits it to other adjacent terminal devices for distribution automation;
a subscriber composed of a data reader receiving failure information issued by other distribution automation terminal devices adjacent thereto; and
A power distribution protection coordination system using DDS communication in an Ethernet environment, characterized in that it includes; a content filtered topic that transmits only data that meets filtering conditions previously set in the data reader from the corresponding data writer.
delete delete delete delete According to claim 1,
When the right distribution automation terminal device of the added distribution automation terminal device recognizes that the connection information has been changed when receiving data from the added distribution automation terminal device with a new ID, it recognizes that the LEFT_ID among the topic data has been added. A power distribution protection coordination system using DDS communication in an Ethernet environment, characterized in that it is changed to an ID of a terminal device for distribution automation. delete