KR101813066B1 - Scada gateway and method of conversion protocol for dnp 3.0 and iec 61850 - Google Patents

Abstract

The present invention relates to a scada gateway device to accommodate IEDs of IEC 61850 protocol in a scada system according to DNP 3.0 protocols and a protocol converting method thereof. The gateway device to accommodate IEDs of IEC 61850 protocol in the scada system according to DNP 3.0 protocol comprises: a DNP 3.0 master module which plays a master role by being connected with a DNP 3.0 RTU and DNP 3.0 serial method; a DNP 3.0 slave module which plays a slave role by being connected with a DNP 3.0 scada server in a DNP 3.0 ethernet method; an IEC 61850 client module which plays a client role about IEC 61850 IED (30); a protocol conversion unit which performs a protocol conversion at an application layer between the IEC 61850 client and the DNP 3.0 slave; a DNP 3.0 master module which connects the protocol-converted DNP 3.0 slave module (108) with the DNP 3.0 slave module of a server side; and a communication port to connect a setting terminal with a gateway. The gateway device according to the present invention has an advantage of being used by connecting an IED device of a new IEC 61850 protocol with an installed DNP scada system at low cost by converting MMS of IEC 61850 IED into DNP 3.0 protocol by using a service mapping table and a data mapping table.

Description

(SCADA GATEWAY AND METHOD OF CONVERSION PROTOCOL FOR DNP 3.0 AND IEC 61850) [0002] The present invention relates to a Scada gateway apparatus for accommodating DNP 3.0 and IEC 61850,

The present invention relates to a Scada gateway device, and more particularly, to a Scada gateway device for accepting IEDs of the IEC 61850 protocol in a Scada system according to the DNP 3.0 protocol and a protocol conversion method thereof.

Supervisory Control And Data Acquisition (SCADA) system collects and displays the state information data of the remote device as RTU (remoteterminal unit) using analog or digital signals on the communication path, stores and displays them, It is a system that monitors and controls a remote device.

In the Scada system, most of the control operations are performed automatically by the RTU and the PLC. The control commands that the operator can control are usually limited to basic operation changes or management level operations. Data acquisition is initiated by an RTU or PLC (Programmable Logic Controller), which involves reading the instrument readings required by the Scada system and reporting the status of each instrument. The data thus obtained is converted into a human-understandable form so that operators using the Human Machine Interface (HMI) at the control center can make appropriate judgments for system management. The RTU or PLC is thus modified or adjusted by the operator's decision. Scada systems usually have a distributed database and are often referred to as tag databases because they have data called tags or points. A point is a single input or output that is monitored / controlled by the system.

On the other hand, the Scada gateway is an intermediary device for connecting the dispersed RTU of the field to the host computer, and functions to convert the fieldbus protocol of the field to the Ethernet protocol of the server side. Industrial field buses in the field are connected to various industrial control and automation devices such as sensors, loop controllers, valves, PLCs, motors, etc. IEC 61850, MOD buses, Profibus, CAN buses and CC-Link are widely known have.

Currently, the most widely used communication protocols for domestic substations are DNB 3.0 and Modbus, but recently IEC 61850 communication protocol has been rapidly used as an international standard. IEC 61850 is a protocol for substation automation system. It is an international standard developed to enable devices such as power equipment, IED (Intelligent Electronic Device) and application software developed by various manufacturers to communicate smoothly. Because of the emergence of IEC 61850, a protocol for substation automation, which is emerging as an international standard, the existing IED and the new IED use different protocols, so a gateway is needed for the interface between the Modbus and DNP 3.0 protocols and the new IEC 61850 protocol do.

"Data Exchange Method of Gateway for Substation Automation" published in the Korean Intellectual Property Office registered B1 (Registration No. 10-1123701) is a method of transferring data and events directly to necessary interface objects in real time, 61850, Modbus, OPC, and DNP3.0 protocols.

The "multi-function gateway system for providing power information ", which is disclosed in Registration No. 10-1082522 of the registered patent publication (B1), is an IEC 61850 module communicating with the IEC 61850 communication protocol and collecting IED data by communicating with a plurality of IEDs, a DNP 3.0 DNP 3.0 module communicating with the communication protocol, a data mapping module mapping the data acquired using the DNP 3.0 protocol and the data acquired through the IEC 61850 protocol, and an information processing module, The mapping is performed after converting the information protocol by the data conversion module that converts / inverses the protocol between the DNP 3.0 protocol and the IEC 61850 protocol.

KR 10-2017-0029855 A KR 10-1191547 B1 KR 10-0976306 B1

Currently, the most widely used protocol in the Scada system is the DNP3.0 protocol. Recently, as the IEC 61850 communication protocol has become widely used as an international standard, its usage is rapidly increasing. Therefore, in order to accommodate DNP 3.0 and IEC 61850 A variety of Scada gateways have been proposed. However, the conventional Scada gateway is mainly proposed to accommodate the existing DNP 3.0 in the IEC 61850 Scada system, or there is a problem that errors are likely to occur during the protocol conversion process.

It is an object of the present invention to provide a Scada gateway device capable of accommodating IEDs of the IEC 61850 protocol at a low cost and a protocol thereof Thereby providing a conversion method.

In order to achieve the above object, the present invention provides a gateway device for accepting an IED of the IEC 61850 protocol in a Scada system according to the DNP 3.0 protocol, the DNP 3.0 RTU and the DNP 3.0 serial method, DNP 3.0 master module to do; DNP 3.0 slave module connected to DNP 3.0 Scada server and DNP 3.0 Ethernet, acting as a slave; An IEC 61850 client module acting as a client for the IEC 61850 IED 30; A protocol converter for performing protocol conversion between an IEC 61850 client and a DNP 3.0 slave at an application layer; A DNP 3.0 master module for connecting the protocol converted DNP 3.0 slave module 108 to the server side DNP 3.0 slave module; And a communication port for connecting the setting terminal to the gateway.

The protocol conversion unit includes a mapping table processing unit 122 for generating a service mapping table 122, a data mapping table, an SCL file, the service mapping table and the data mapping table from the SCL file and the configuration information, A service mapping unit for converting an IEC 61850 service to a DNP 3.0 service or converting a DNP 3.0 service to an IEC 61850 service, and converting the IEC 61850 data to DNP 3.0 data or the DNP 3.0 data to IEC 61850 And a data mapping unit for converting the data into data.

According to another aspect of the present invention, there is provided a method for converting an IEC 61850 protocol service to a DNP 3.0 service or a service mapping table for converting a DNP 3.0 service to an IEC 61850 protocol service, A second step of generating a data mapping table for converting IEC 61850 protocol data to DNP 3.0 data or converting DNP 3.0 data to IEC 61850 protocol data; A third step of determining whether the received message is the RTU of the DNP 3.0 or the IED of the IEC 61850 according to the destination if the received message is a message received from the Scada server, and then converting the protocol to the corresponding RTU or IED; A fourth step of converting the DNP3.0 serial into a DNP3.0 Ethernet and transmitting the converted DNP3.0 Ethernet to the Scada server if the received message is a message received from the DNP3.0 RTU; And a source, and maps the service according to the service mapping table if the message is received from the IEC 61850 IED, maps the data according to the data mapping table, converts the IEC 61850 protocol to the DNP3.0 Ethernet protocol, And a fifth step of transmitting the data to the server.

In the third step, if the received message is a message received from the Scada server, it is determined whether the RTU is the DNP 3.0 RTD or the IEC 61850 IED according to the destination, and if the RTU is the DNP 3.0 Ethernet, the protocol is converted into the DNP 3.0 serial If the IED is the IED, the service is mapped according to the service mapping table, the data is mapped according to the data mapping table, the DNP 3.0 Ethernet protocol is converted to the IEC 61850 protocol, and the IED is transmitted to the corresponding IED.

The gateway device according to the present invention converts the MMS of the IEC 61850 IED into the DNP 3.0 protocol using the service mapping table and the data mapping table and connects the IED device of the new IEC 61850 protocol to the already installed DNP Scada system at low cost There is an advantage that it can be used.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a schematic view showing the overall configuration of a scada system to which a gateway according to the present invention is applied;
FIG. 2 is a detailed block diagram of the Scada gateway apparatus shown in FIG. 1,
3 is a schematic protocol stack example of a Scada gateway device according to the present invention,
4 is a flowchart illustrating an operation of the Scada gateway according to the present invention,
FIG. 5 is a diagram illustrating a DNP 3.0 protocol stack applied to the present invention, FIG.
6 is a diagram showing a DNP3.0 protocol data format applied to the present invention;
Figure 7 is an example of an IEC 61850 protocol stack as applied to the present invention,
8 shows an example of the data structure of the IEC 61850 protocol applied to the present invention,
9 is an SCL example of the IEC 61850 protocol applied to the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features, and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings. The following examples are merely illustrative of the present invention and are not intended to limit the scope of the present invention.

FIG. 1 is a schematic diagram showing the overall configuration of a Scada system to which a gateway according to the present invention is applied, and FIG. 2 is a detailed block diagram of the Scada gateway apparatus shown in FIG.

As shown in FIG. 1, the Scada system to which the gateway according to the present invention is applied includes a Scada server 10 for providing an application service according to the DNP3.0 protocol, and a Scada server 10 for receiving a DNP3.0 protocol and an IEC 61850 protocol A gateway 100, a remote terminal unit (RTU) 20 according to the DNP 3.0 protocol, and an intelligent terminal device (IED) 30 according to IEC 61850. The gateway 100 and the RTU 20 are connected by a serial communication method such as RS232 or RS485 and the gateway 100 and the IED 30 ) Are connected by Ethernet.

Referring to FIG. 1, the Scada system according to the DNP 3.0 protocol is a remote control system consisting of an MTU (Master Terminal Unit) of a central control center and an RTU (Remote Terminal Unit) installed in a substation or an electric switchboard. ) Performs the MTU function of the DNP 3.0 protocol.

In the embodiment of the present invention, the RTU 20 is connected to a physical device in accordance with the DNP 3.0 protocol, receives measurement data, various status data, sensor data, and the like from the corresponding equipment and delivers the data to the server. It controls the actuators and relays of the equipment. For example, a remote terminal unit (RTU) is a facility that is installed in a wired / unmanned substation to directly monitor, control, and measure electric power facilities. After receiving commands from the upper SCADA system, Control facility, and transmit status monitoring and measurement information acquired from the power facilities to the upper SCADA system. The main functions of RTU are remote monitoring, telemetry, remote control, facility management, communication execution, system diagnosis and time synchronization. The RTU is a central processing unit that includes a main processing unit (MPD) that processes various data and manages communications with the host control system and the field processing unit, a field processing unit (FPD) Intelligent Analog Processing Device (IAPD) that acquires various meter values such as voltage and current of power equipment, GPS receiver (GPS Time Sync.) That synchronizes the time of all RTU devices with standard time from GPS. , A terminal block device (T / B: T / B) that is electrically connected to the field facility, and a power supply device that supplies DC power to each device.

Thus, according to the present invention, the DNP 3.0 protocol communicating between the RTU 20 and the scada server 10 through the gateway processes the remote surveillance control service according to the protocol stack as shown in FIG. FIG. 5 is a diagram illustrating a DNP 3.0 protocol stack applied to the present invention, and FIG. 6 is a diagram illustrating a DNP 3.0 protocol data format applied to the present invention.

The DNP 3.0 protocol was designed based on the physical layer, the data link layer, and the application layer in the OSI 7-layer model. In the beginning, a method of supporting TCP / IP after being designed in a serial manner has been added, Show the protocol stack. Referring to FIG. 5, the DNP 3.0 protocol is divided into a DNP serial and a DNP Ethernet. The DNP serial is defined in a serial manner, such as RS-232 or RS-422/485, Link layer and application layer. The DNP LAN method is composed of the TCP / IP layer and the application layer as the physical LAN as the Ethernet LAN method. In addition, by extending the Advanced RTU functions and frame size, a virtual transport layer can be used to transmit messages larger than 16 bytes up to 255 bytes. Since DNP serial was originally developed and DNP LAN was later developed, TCP Or the DNP data link layer above the UDP layer.

In the DNP 3.0 application layer, an application service data unit (ASDU) is generated by receiving user data. As shown in FIG. 6, one user data can be divided into a plurality of ASDUs. Referring to FIG. 6, each ASDU generates APDU (Application Protocol Data Unit) by combining APCI (Application Protocol Control Information) corresponding to a header. When receiving APDU, And assemble the ASDU to generate complete data. The object header is a data unit identifier (DUI) for identifying a data object to be followed, and the data includes information objects (IOs) of a prescribed type in the object header.

The request header is composed of AC (application control) and FC (function control). In response header, AC and FC are added with IIN (Internal Indication). The AC includes the FIR that refers to the first segmented ASDU or the last ASDU, the FIN, the CON requesting confirmation, and the sequence number. There are FC = 0x00 (CONFIRM), FC = 0x01 (READ), FC = 0x02 (WRITE), and the codes used in the master's request and the slave's response are the purpose of the message. Is used for the purpose.

For example, the FC = 0x00 (CONFIRM) message is used as an acknowledgment for a single partitioned message and for receipt of the requested message. The FC = 0x01 (READ) message is used to obtain the information of the data object from the RTU. Requests and responses are defined for various cases. The FC = 0x02 (WRITE) message is used when the master station sends the object to the RTU. The FC = 0x03 (SELECT) message is used to select the control device, which selects a particular device and puts it into a standby state and reports the result. The received RTU starts the timer, but it must be activated before receiving the FC = 0x04 (OPERATE) message before the timeout. FC = 0x04 (OPERATE) is used to activate one or more control devices. In the case of FC = 0x05 (DIRECT OPERATE), the control device is used to activate the SELECT message without having to receive it in advance. FC = 0x06 (Direct OPERATE No Ack) is a direct control message that does not require the RTU to respond. FC = 0x07, 0x08 (IMMEDIATEFREEZE) The message is used to copy the value of a specific object to the buffer and is distinguished by the need for a response.

The DUI of an object header is composed of an object group, an object variation, a qualifier, and a range, where the object group means a general data class. The object change is set to 0 when sending the request, and it will be represented according to the specific type in the response. For example, in a request, a change to an analog input is delivered with a 0 set, and in response, a 16-bit analog input changes the value of a specific format. A finite value identifies the meaning of the range value that follows, and the range has the start and end values of the index.

The object class is classified into a fixed data object and an event data object. The fixed data object reflects the current value of the external station and is assigned class 0. Event data objects can be assigned to classes 1, 2, and 3 as objects created by data changes or other factors. The external station device profile is made up of classes, and information and settings for assigning data are described.

Application layer message exchange is provided in two ways: a request from the master, a response from the external station, and a method of sending the change detected by the external station. The request / response transaction between the master and the slave must be fully processed before another request is sent to the slave, and the master may receive the on message voluntarily after receiving the response after receiving the request.

Referring again to FIG. 1, an intelligent electronic device (IED) 30 is a microprocessor-based field controller for protecting and controlling power devices such as circuit breakers and transformers. In a digital-based substation system, the IEC 61850 standard Lt; / RTI > The IEC 61850 protocol stack adopted in the IED 30 in the embodiment of the present invention is as shown in FIG. FIG. 7 is an example of an IEC 61850 protocol stack applied to the present invention, FIG. 8 is an example of an IEC 61850 protocol data structure applied to the present invention, and FIG. 9 is an SCL example of an IEC 61850 protocol applied to the present invention.

7, the IEC 61850 protocol can provide various applications such as Sampled Measured Values (SMV), Generic Object Oriented Substation Event (GOOSE), and Manufacturing Message Specification (MMS). However, in the gateway device according to the present invention, It supports MMS over TCP / IP protocol except GOOSE and SMV, which can be implemented at low cost. The IMS 61850 MMS communication service is easy to process at high speed real time data, and the protocol can be used in OSI 7 layer and TCP compatible communication profile, and it is suitable for centralized and distributed architecture in system aspect. The MMS architecture provides a one-to-one mapping structure such as the server / client communication service, sampling communication service, high-speed event communication service and time synchronization service of the abstracted communication service interface (ACSI) defined in IEC 61850-7-2 standard.

In addition, the function and control level of the IED generally required is not fixed, and may change depending on the situation. Therefore, free allocation of functions to the IED is required, and interoperability should be provided as functions are distributed. IEC 61850 supports distribution, station, bay and process level allocations to support this. The application of IEC 61850 conforms to the Abstract Communication Service Interface (ACSI), which must be able to translate to the application layer protocol and be reflected in the communication profile. ACSI is mapped to Specific Communication Service Mapping (SCSM).

Referring to FIG. 8, one physical IED is defined as a plurality of LNs (Logical Nodes), and each LN is defined by data and data attributes. That is, all functions are separated into LNs existing in one or more physical devices, each of which is known as 'LN0', which contains nameplate information or a result of self-supervision of itself LN is essential. These LNs are connected to LCs (Logical Connections) to exchange data exclusively. LNs are assigned to functions (F) and physical devices (PD), which are connected to physical connections (PCs). Each LN (Logical Node) must be able to interpret the syntax and semantics of the data sent and received. To do so, the application models the data in three steps. Level 1 In ACSI, the model and service used to access the domain of the SAS, which is the object model, are applied to reflect the needs of the application. At this time, the service not only reads or writes the object value of the application but also controls the equipment. Level 2 Common Data Classes (CDC) define the structure of objects with one or more attributes, the data types of which are defined in IEC 61850-7-1. Level 3 "Compatible logical node classes and data classes" defines a compatible object model, based on CDC, defined by functional classes and data classes. The data classes of IEC 61850 represent meaningful information and can be written as SetDataValue or as GetDataValue.

The LNs defined in the current standard are defined in the IEC 61850-7-4 and IEC 61850-7-3 annex standards in the form of logical nodes and common data classes (CDC), respectively. In IEC 61850-7-4, 1st edition, 92 logical nodes are defined, and each logical node is classified from (A) to (Z) by type. The new functions and extended data models with the addition of new domains are reflected in the second edition and contain the logical nodes defined in IEC 61850-7-4, 2nd edition (2010). In the second edition, 153 logical nodes were defined by adding logical nodes in functional blocks, mechanical sensors, monitoring sensors, and instrumental transformers compared to the first edition.

The static structure of the communication system also describes where the data is potentially coming from (the transmitting LN) and where it goes (the receiving LN), which should be engineered or negotiated at the system planning stage. It is also necessary to refer to the static structure in order to dynamically open and close the communication channel even during execution. Therefore, SCL is defined in IEC 61850-6 for this official description. Referring to FIG. 8, SCL defines system variables necessary for defining one IED based on XML, including binding information of the IED and functions of the sub-station itself.

Most LNs provide information related to common LN information and state information, set values, measurements, and controls, and represent functions with data and data attributes. Such an LN can provide up to 30 data, and data can include more than 20 attributes.

Referring again to FIG. 1, a Scada gateway device 100 for receiving DNP 3.0 and IEC 61850 according to the present invention includes a DNP 3.0 master module 102 acting as a master for the DNP 3.0 RTU 20, A DNP 3.0 slave module 104 acting as a slave to the 3.0 scada server 10, an IEC 61850 client module 110 acting as a client to the IEC 61850 IED 30, an IEC 61850 client 110, A protocol conversion unit 120 for performing protocol conversion between the DNP 3.0 slaves 108 and a DNP 3.0 master module 108 for connecting the protocol converted DNP 3.0 slave module 108 to the DNP 3.0 slave module 104 on the server side, A protocol table 130 for storing protocol information for each device and a communication port 140 for connecting the setting terminal 40 to the gateway 100.

2, the protocol conversion unit 120 extracts a service mapping table 122 from the service mapping table 122, the data mapping table 123, the SCL file 124, the SCL file 124, and the configuration information, A mapping table processing unit 121 for generating a data mapping table 122 and a service mapping table 121 for converting an IEC 61850 service to a DNP 3.0 service or a DNP 3.0 service to an IEC 61850 service with reference to a service mapping table 125 A mapping unit 125 and a data mapping unit 126 for converting IEC 61850 data into DNP 3.0 data or DNP 3.0 data into IEC 61850 data with reference to a data mapping table 123.

3, the DNP 3.0 RTU 20 converts the DNP serial into a DNP Ethernet protocol and connects the DNP serial to the SCADA server 10, and supports the IEC 61850 support The IED 30 connects to the Scada server 10 via IEC 61850 - DNP 3.0 protocol conversion. 3 is a schematic protocol stack example of a Scada gateway apparatus according to the present invention, wherein (a) schematically shows a protocol conversion process between an IEC 61850 IED 30 and a Scada server 10, and (b) ) Schematically illustrates the protocol conversion process between the DNP 3.0 RTU 20 and the Scada server 10.

3, the MMS message of the IED 30 is transmitted to the Ethernet of the gateway 100 via the TCP / IP and Ethernet protocols and then transmitted to the MMS through the TCP / IP of the gateway 100 And converted into the DNP 3.0 application message by the protocol conversion unit 120, and then transmitted to the Ethernet of the scada server 10 through the TCP / IP and Ethernet. This message is finally delivered to the DNP3.0 application via TCP / IP. Conversely, the DNP 3.0 application message of the Scada server 10 is delivered to the MMS of the IED 30 in the reverse process.

Referring to FIG. 3B, the DNP 3.0 RTU 20 transmits a DNP 3.0 application message to the serial communication unit of the gateway device 100 through a data link and a serial communication line, 3.0 application, and is transmitted to the Ethernet of the Scada server 10 via TCP / IP, Ethernet, and then to the DNP 3.0 application via TCP / IP. Thus, the gateway device 100 converts the DNP serial protocol of the RTU 20 into the DNP Ethernet protocol, and connects to the scada server 10.

4 is a flowchart of the operation of the Scada gateway according to the present invention.

First, the IEC 61850 standard provides a greater variety of message types and protocol stacks compared to DNP 3.0, with more stringent time limits. The DNP 3.0 'request-response' message exchange and the self-reporting Unsolicited Response message at the station can be mapped to a Type 3 message of IEC 61850. There is no DNP 3.0 communication function corresponding to the Sampled Values (SV) method or the GOOSE (Generic Object Oriented Substation Event) method provided by IEC 61850.

Referring to FIG. 4, a gateway configuration is set in a gateway setting step (S101), an SCL file to define a function of the IED is created in the SCL editing step (S102), and the created SCL file is stored in the gateway (S101, S102). In the gateway configuration step S101, a protocol table 130 for defining a protocol of each device may be set for faster processing. The SCL 124 is the same as the example shown in FIG.

And then creates a service mapping table 122 (S103). IEC 61850-8-1 presents the relationship between services and profiles required for client-server communication. Scada gateway 100 of the present invention needs to convert IEC 61850 service to DNP 3.0 service as shown in Table 1 below have.

IEC 61850 service DNP 3.0 Services Remarks GetDataValues Read data SetDataValues Write GetDataValues Read substitute SetDataValues Write Report Unsolicited
Response
report GetBRCBValues Read SetBRCBValues Enable (/ Disable)
Unsolicited
Response GetURCBValues Read SetURCBValues Enable (/ Disable)
Unsolicited
Response Select Select
Control SelectWithValue Select Operate (Direct) Operate

IEC 61850 services not listed in Table 1 above are difficult to convert to DNP 3.0 services. For example, DataSet related services and group setting control services, log related services, and GOOSE and Generic Substation Status Event (GSSE) related services, which allow multiple objects to be set as a single set to retrieve or change values, 0 service can not be converted. In DNP 3.0, there is an Unsolicited message that reports the event itself on the slave, which can be converted to IEC61850 Report service.

Next, a data mapping table 123 for conversion between an object of IEC 61850 and an object (index) of DNP 3.0 is generated (S104). The object of IEC 61850 can deduce the function in the object name itself, independently of the implementation, but in DNP 3.0 this is not possible and therefore the data mapping table 126, which stores the index of the DNP 3.0 object corresponding to the object of IEC 61850, . That is, the information model in IEC 61850 standard should be converted into the DNP information model used in SCADA HOST. The data attributes (stVal, istMag, mag, q, t) corresponding to the lowest information of IEC 61850 are converted into DNP data Should be.

After the mapping table is completed, when the gateway device receives the data, it determines the source and, if the message is received from the scada server 10, the gateway device determines whether the RTU 20 of the DNP 3.0 or the IED 30 of the IEC 61850, If the RTU 20 is an RTE 20, it converts the protocol of the DNP 3.0 Ethernet to the DNP 3.0 serial and transmits the protocol to the RTU 20. If the RTE 20 is the IED 30, the service mapping unit maps the service according to the service mapping table 122, Maps the data according to the mapping table 123, converts the DNP 3.0 Ethernet protocol to the IEC 61850 protocol, and transmits the DNP 3.0 Ethernet protocol to the IED 30 according to the IEC 61850 protocol.

If the message received from the IEC 61850 IED 30 is a message received from the DNP 3.0 RTU 20, the DNP 3.0 serial is converted to DNP 3.0 Ethernet and transmitted to the Scada server 10. If the message is received from the IEC 61850 IED 30, 122, maps the data according to the data mapping table 123, converts the IEC 61850 protocol into the DNP3.0 Ethernet protocol, and transmits the converted data to the scada server 10.

The scada gateway apparatus 100 according to the present invention converts the MMS of the IEC 61850 IED 30 to the DNP 3.0 protocol using the service mapping table 122 and the data mapping table 123 and transmits the already installed DNP The IED device of the new IEC 61850 protocol can be connected to the Scada system at low cost.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

10: Scada server 20: RTU
30: IED 40: Setting terminal
100: Gateway device 102: DNP3.0 master
104: DNP3.0 slave 106: DNP3.0 master
108: DNP 3.0 slave 110: IEC 61850 client
120: protocol conversion unit 121: mapping table processing unit
122: service mapping table 123: data mapping table
124: SCL file 125: service mapping unit
126: Data mapping unit 130: Protocol table

Claims (4)

A gateway device for accommodating an IED of IEC 61850 protocol in a Scada system according to the DNP 3.0 protocol,
A DNP 3.0 master module 102 acting as a master in connection with the DNP 3.0 RTU 20 in a DNP 3.0 serial manner;
A DNP 3.0 slave module 104 serving as a slave in connection with the DNP 3.0 Scada server 10 and the DNP 3.0 Ethernet method;
An IEC 61850 client module 110 acting as a client to the IEC 61850 IED 30;
A protocol conversion unit 120 for performing protocol conversion between an IEC 61850 client 110 and a DNP 3.0 slave 108 at an application layer;
A DNP 3.0 master module 106 for connecting a protocol converted DNP 3.0 slave module 108 to a DNP 3.0 slave module 104 on the server side; And
A Scada gateway device for accommodating DNP 3.0 and IEC 61850, comprising a communication port (140) for connecting a set terminal (40) to a gateway (100). The method of claim 1, wherein the protocol conversion unit (120)
A service mapping table 122, a data mapping table 123, an SCL file 124, a mapping table processing unit 121 for generating the service mapping table and the data mapping table from the SCL file and the configuration information, A service mapping unit 125 for converting an IEC 61850 service to a DNP 3.0 service or a DNP 3.0 service to an IEC 61850 service by referring to the service mapping table, and a service mapping unit 125 for referring to the data mapping table and converting IEC 61850 data to DNP 3.0 data And a data mapping unit 126 for converting DNP 3.0 data to IEC 61850 data. A first step of generating a service mapping table for converting an IEC 61850 protocol service to a DNP 3.0 service or converting a DNP 3.0 service to an IEC 61850 protocol service;
A second step of generating a data mapping table for converting IEC 61850 protocol data to DNP 3.0 data or converting DNP 3.0 data to IEC 61850 protocol data;
A third step of determining whether the received message is the RTU of the DNP 3.0 or the IED of the IEC 61850 according to the destination if the received message is a message received from the Scada server, and then converting the protocol to the corresponding RTU or IED;
A fourth step of converting the DNP3.0 serial into a DNP3.0 Ethernet and transmitting the converted DNP3.0 Ethernet to the Scada server if the received message is a message received from the DNP3.0 RTU; And
If the message is a message received from the IEC 61850 IED, the service is mapped according to the service mapping table, the data is mapped according to the data mapping table to convert the IEC 61850 protocol into the DNP3.0 Ethernet protocol, To a DNP 3.0 and a IEC 61850, including the fifth step of transmitting the protocol to the SCADA gateway. 4. The method of claim 3, wherein the third step comprises:
If the message is received from the Scada server, it is determined whether it is the RTU of DNP 3.0 or IED of IEC 61850 according to the destination. If the message is the RTU, the DNP 3.0 Ethernet is converted into the DNP 3.0 serial and transmitted to the corresponding RTU , IED maps the service according to the service mapping table, maps the data according to the data mapping table, converts the DNP 3.0 Ethernet protocol into the IEC 61850 protocol, and transmits the DNP 3.0 Ethernet protocol to the corresponding IED. A protocol conversion method of a Scada gateway for accepting.

Images