KR20180116793A - Method for data interoperability based on CIM and OPC-UA - Google Patents

Abstract

The present invention relates to a CIM and OPC-UA-based data interoperability method. According to an embodiment of the present invention, the data interoperability method comprises the steps of: receiving a CIM data model using a communication standard model in a data designer, and generating a CIM profile on the basis of the received CIM data model; generating, by a schema format converting unit, an OPC-UA data model in accordance with a predetermined conversion rule including a mapping rule mapping a CIM meta model and an OPC-UA meta model on the basis of the CIM profile; structuring the generated OPC-UA data model in a server in a form including a node to store the same; and transceiving data corresponding to the OPC-UA data model using a proxy communicating with the server using a predetermined data communication rule.

Description

CIM and OPC-UA based data interoperability based on CIM and OPC-UA}

The present invention relates to CIM and OPC-UA-based data interoperability methods.

Recently, CIM (Common Information Model) has been applied as a data model related standard in electric power field. CIM is an abstract data model aimed at modeling and expressing various kinds of information generated in the power field in class form.

Specifically, IEC 61970 CIM and IEC 61968 CIM are common data models used in the power sector, and IEC 61970 and IEC 61968 are standards used in transmission and distribution systems, respectively.

OPC-UA (OLE Process for Control-Unified Architecture) is a communication architecture standard standardized in IEC62541. It is a standard that is originally applied to industrial automation. However, in order to ensure interoperability of power domains, IEC 61970 or 61968 CIM data model There is a need to use the OPC-UA standard.

Referring to FIG. 1, there is shown a conventional CIM and OPC-UA-based data conversion method.

Referring to FIG. 1, there is a difficulty in interworking between the conventional data communication system based on the CIM data model and the data communication system based on the OPC-UA data model. Specifically, a system that performs data communication based on a CIM data model uses a CIM data model 10 (for example, IEC 61970 or 61968 standard), and a system that performs data communication based on an OPC-UA data model uses an OPC- (20, for example, NodeSet2.xml).

In the data communication area based on the CIM data model, the data structure is defined as the CIM profile 15. In the data communication area based on the OPC-UA data model, the data structure is defined as the OPC-UA data model 25 in the NodeSet2.xml format So that there was no mutual compatibility.

Since there is no compatibility between the CIM profile 15 and the OPC-UA data model 25, data is transformed and transferred by the hard-coding method for each data structure in order to interoperate. Specifically, some of CIM-based data may be manually selected and converted to OPC-UA-based data format, or some of OPC-UA-based data may be selected and converted to CIM-based data format for offline connection, I used a method of recognizing the type in advance and performing a simple conversion only for the data type identified.

Although the IEC 61970 or 61968 CIM data model is defined as a standard, there is no definition of detailed technology for actual implementation and use, and it was difficult to ensure interoperability in the power domain.

However, there is an attempt to secure interoperability by using the OPC-UA data model having actual implementation technology, but there is no compatibility between the OPC-UA data model and the CIM data model, and there is a time or cost difficulty in interworking .

The IEC 62541 OPC-UA standard defines a communication infrastructure for operating a data model as well as a data model. Since there is a standard stack and a software development kit (SDK), IEC 62541 OPC-UA infrastructure defines CIM data It is intended to provide a mutual compatibility method for operating a model.

The present invention implements interoperability by allowing the OPC UA Client to operate and manage a power system using IEC61970 or IEC 61968 standards by implementing interoperability through matching between IEC 61970 or IEC 61968 CIM models and OPC-UA models The purpose is to provide.

It is an object of the present invention to provide a CIM and OPC-UA-based data interoperability method for real-time processing of information exchange between various systems in a power field even when a new CIM standard is applied or a new facility is added.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned can be understood by the following description and more clearly understood by the embodiments of the present invention. It will also be readily apparent that the objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

In order to achieve the above object, a data interoperability method of the present invention includes receiving a CIM data model using a communication standard model in a data designer, generating a CIM profile based on the received CIM data model, Generating an OPC-UA data model according to a predetermined conversion rule including a mapping rule mapping a CIM meta model and an OPC-UA meta model on the basis of the CIM profile in the OPC-UA data model, Structuring and storing the OPC-UA data model in a form including a node in the server, and transmitting and receiving data corresponding to the OPC-UA data model using a proxy communicating with the server using a predetermined data communication rule .

In addition, the communication standard model may include the IEC 61970 CIM standard or the IEC 61968 CIM standard, and the OPC-UA data model may include using the IEC 62541 OPC-UA standard.

The generating of the OPC-UA data model may include receiving a CIM class from the CIM profile, mapping the CIM class to a UA Object according to the mapping rule, Transforming and creating a CIM profile into the OPC-UA data model, and performing an validation check on the generated OPC-UA data model.

In addition, the CIM profile may include a subset or an extended CIM profile based on the CIM data model in the data designer.

Also, the data designer can convert the generated CIM profile into a logical data structure.

In addition, the OPC-UA data model may be converted to a logical data structure in the data designer, and may include a Nodeset2.xml format.

The generating of the OPC-UA data model may include receiving an OPC-UA model using the IEC 62541 standard in the data designer, and generating the OPC-UA data model based on the received OPC-UA model ≪ / RTI >

The generating of the OPC-UA data model may include receiving XML data from the data designer and generating an XML schema based on the received XML data, And generating the OPC-UA data model according to the predetermined conversion rule based on the OPC-UA data model.

In order to achieve the above object, a data interoperability method of the present invention includes receiving CIM data using a communication standard model, and mapping rules for mapping a CIM meta model and an OPC-UA meta model in a data format conversion unit Converting the received CIM data into first OPC-UA data according to a predetermined conversion rule, converting the first OPC-UA data from a proxy into a predetermined type of second OPC-UA represented by a node, UA data is changed to data and stored in the server when the second OPC-UA data is changed, and the second OPC-UA data is changed to the server through the proxy when the second OPC- Converting the second OPC-UA data into the CIM data by the data format conversion unit, and transmitting the converted CIM data to the data format conversion unit And a system.

In addition, the communication standard model may include the IEC 61970 CIM standard or the IEC 61968 CIM standard, and the first OPC-UA data and the second OPC-UA data may include using the IEC 62541 OPC-UA standard. have.

In addition, the proxy includes a first proxy included in the CIM-based data operation unit and a second proxy included in the OPC-UA-based data operation unit, and the first proxy and the second proxy include predetermined data communication rules To communicate with the server.

The receiving of the CIM data may include receiving OPC-UA data using the IEC 62541 OPC-UA standard, and the second proxy may transmit the received OPC-UA data to a node UA data is transmitted to the server via the first proxy and the second OPC-UA data is transmitted to the server through the second proxy, and the second OPC- -UA data and transmitting the data.

The step of receiving the CIM data may include receiving XML data, and the step of converting into the first OPC-UA data may include converting the received XML data into the first OPC-UA data And converting the OPC-UA data into the CIM data may include converting the second OPC-UA data into the XML data, and transmitting the converted XML data.

According to the data interoperability method of the present invention as described above, by utilizing the IEC 62541 OPC-UA standard as the implementation infrastructure of the CIM data model, by ensuring interoperability based on the IEC 61970 or IEC 61968 CIM data model in the power domain , The power infrastructure can be improved in interoperability, reliability and efficiency, and real-time power information can be exchanged between the supplier and the consumer.

The data interoperability method of the present invention enables the interface between heterogeneous standards through the mapping from the power system using the IEC 61970 or IEC 61968 standard to the OPC-UA standard, and at the same time, .

The data interoperability method of the present invention is used as a middleware for linkage between various systems constituting a DMS (Distribution Management System) or a Microgrid System so that various systems and applications can interoperate without technical, temporal, and cost problems There are advantages to be able to.

The above and other objects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: FIG.

1 is a diagram illustrating a conventional CIM and OPC-UA-based data conversion method.
2 is a diagram illustrating a data interoperability system in accordance with some embodiments of the present invention.
3 illustrates a data interoperability system in accordance with an embodiment of the present invention.
4 is a flowchart illustrating a data interoperability method according to an embodiment of the present invention.
5 is a diagram illustrating a data interoperability system according to another embodiment of the present invention.
6 is a flowchart illustrating a data interoperability method according to another embodiment of the present invention.
FIG. 7 is a view for explaining the conversion rules of FIGS. 4 and 6 according to an embodiment of the present invention.
8 is a flowchart illustrating a method of generating an OPC-UA data model according to an embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention, and the manner of achieving them, will be apparent from and elucidated with reference to the embodiments described hereinafter in conjunction with the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Although the first, second, etc. are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are used only to distinguish one component from another. Therefore, it goes without saying that the first component mentioned below may be the second component within the technical scope of the present invention.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

Hereinafter, a method of data interoperability based on CIM and OPC-UA according to some embodiments of the present invention will be described with reference to FIGS. 2 to 8. FIG.

2 is a diagram illustrating a data interoperability system in accordance with some embodiments of the present invention.

Referring to FIG. 2, a data interoperability system according to some embodiments of the present invention includes a CIM-based system 100, a first data designer 115, a data format conversion unit 133, a first proxy 135, an OPC A UA-based system 200, a second data designer 215, a schema format conversion unit 230, a second proxy 255, and a server 270.

IEC 62541 OPC-UA is a technology that can manage various commercial communication technologies in an integrated manner, and is a communication standard mainly used in industrial automation systems. OPC-UA has a basic data model and can model logical objects using the basic data model.

The OPC-UA can represent all of the OPC-UA data models, including Classic OPC, data models defined by other organizations, and vendor-defined data. The meta model called OPC-UA address space provided by the OPC-UA is defined along with the general data model based on the object type. In addition, OPC-UA can provide a simple data model as well as a complex data model.

The OPC-UA can be modeled on the following principles. For example, i) OPC-UA modeling uses object-based techniques such as layering and inheritance of information. ii) Type information can be accessed by instantiation. iii) There are no restrictions on the data model methodology to provide data for use on various machines. iv) Always performed on the server side. However, the present invention is not limited thereto.

The modeling concept of the OPC-UA is represented by a node. Specifically, each node may include attribute information such as id and name. However, the present invention is not limited thereto.

The OPC-UA basic data model consists of an object, an object type, a variable, a variable type, and a reference. Specifically, a variable type means a basic data type (such as Boolean, int or float). It is also possible to add a new data format if desired by the user. However, the present invention is not limited thereto.

A variable is a name assigned to a variable type. The object type can be configured by including various variables. An object is a meaningful name given to an object type. Reference refers to an object type, a variable type, an object, and a reference method between variables. However, the present invention is not limited thereto.

IEC 61970 and IEC 61968 CIM are common data models used in the power sector, IEC 61970 is the transmission system, and IEC 61968 is the standard used in the distribution system.

IEC 61970 and IEC 61968 CIM are technologies that can be used both inside and outside the power system. In addition, IEC 61970 and IEC 61968 CIMs can model information in the power system as logical objects and define data messages in a standardized data structure.

The CIM-based system 100 includes a system for performing CIM data model-based data communication, and the OPC-UA based system 200 includes a system for performing OPC-UA data model-based data communication.

The OPC-UA based system 200 may communicate with a lower level CIM based power system as an upper control level power system. Alternatively, the OPC-UA based system 200 can communicate with a higher level CIM based power system as a lower control level power system. However, the present invention is not limited thereto.

At this time, the power system is divided into an energy management system (EMS), a power management system (PMS), a power automation system (PAS), a transmission and distribution system, a generation system, Advanced Distribution Management Systems (ADMS), Distribution Management Systems (DMS), Supervisory Control and Data Acquisition (SCADA) for monitoring and control. However, the present invention is not limited thereto.

The communication protocol between the CIM-based system 100 and the OPC-UA based system 200 may include UCA 2.0, Modbus, DNP 3.0, IEC 870-5, HDLC, ICCP, PIS or TCP / IP, But is not limited thereto.

The data designer includes a module that performs data modeling. For example, a data designer can be represented in a program format such as 'Data Designer .exe' through the GUI of the system on which the data designer is installed and can be structured and organized easily by clicking or dragging. have.

Data modeling involves the task of constructing a logical data model (e.g., RDF or XML data) from a given concept (e.g., real-time power usage). However, the present invention is not limited thereto.

The data designer may include a first data designer 115 or a second data designer 215. However, the present invention is not limited thereto.

The first data designer 115 is installed or included in the CIM-based system 100 to receive the CIM data model using the IEC 61970 or IEC 61968 standard and to generate the CIM profile 117 based on the received CIM data model can do.

The second data designer 215 is installed in or included in the OPC-UA-based system 200 and receives the OPC-UA model using the IEC 62541 standard and transmits the OPC-UA data model 217 < / RTI >

The format conversion unit includes a module, a program, or a computer device that automatically converts the data format according to a predetermined conversion rule (235). For example, the format conversion unit may include converting the CIM data format and the OPC-UA data format, or converting the XML data format and the OPC-UA data format. However, the present invention is not limited thereto. For reference, a detailed description of the predetermined conversion rule 235 will be described later.

The format conversion unit may include a data format conversion unit 133 and a schema format conversion unit 230. [ However, the present invention is not limited thereto.

The data format conversion unit 133 may include converting the XML data at the time of data operation and the schema format conversion unit 230 may include converting the XML schema 317 at the time of data modeling. But is not limited thereto.

The proxy may include a module, program, or computer device that communicates with the server 270 using predetermined data communication rules.

 Specifically, the predetermined data communication rules include transforming the data into a data format that is communicable with the server 270 performing OPC-UA data model-based data communication. For example, the proxy may receive OPC-UA data and convert the data to have attribute information such as id and name so as to correspond to a node modeled in the server 270.

The proxy has a merit that it is easy to grasp the cause of a data communication error when data communication error occurs when performing data communication between different systems or computer devices and the server 270 by performing logging. Specifically, the proxy includes logging information (logs) necessary to debug an error that may occur during program development and after completion, or to monitor the state of an active program. However, the present invention is not limited thereto.

Proxies can perform data validation checks to prevent unusual situations (eg, DDOS (Distributed DoS) attacks, hacking or server down) due to erroneous data communications. For example, if anomalous data is to be accessed by the server 270, the proxy may perform data filtering to send only normal data to the server 270.

The proxy may include a first proxy 135 or a second proxy 255.

The first proxy 135 communicates with the CIM-based data operation unit 130 and the server 270 so that the CIM data can be transmitted to the server 270 when the CIM-based data operation for performing the CIM data model- Can be performed.

The second proxy 255 may include an OPC-UA-based data operation unit 250 so that the OPC-UA data may be transmitted to the server 270 in OPC-UA-based data operation for performing OPC-UA data model- And the server 270. [0050]

The server 270 may include a computer or a program that stores and manages data, such as the above-described power system, and provides information to a program or a computer device via a network, but the present invention is not limited thereto.

The server 270 may be modeled to store an OPC-UA data model 217 represented by a Node. Specifically, each node may include attribute information such as id and name. For example, the OPC-UA data model 217 may include a NodeSet2.xml format. However, the present invention is not limited thereto.

3 illustrates a data interoperability system in accordance with an embodiment of the present invention. For the sake of convenience of description, the same elements as those of the above-described embodiment will be described below with the exception of duplicate descriptions.

3, a data interoperability system according to an exemplary embodiment of the present invention includes a CIM-based data modeling unit 110, a first data designer 115, a schema format conversion unit 230, an OPC-UA- A second data designer 215, a server 270, a CIM-based data operation unit 130, a data format conversion unit 133, a first proxy 135, a server 270, an OPC-UA 210, a second data designer 215, Based data operation unit 250, and a second proxy 255. [

The CIM-based data modeling unit 110 includes a module, a program, or a computer device that performs data modeling based on a CIM data model. Specifically, the CIM data model may include IEC 61970 or IEC 61968 CIM data models. However, the present invention is not limited thereto.

The OPC-UA-based data modeling unit 210 includes a module, a program, or a computer device that performs data modeling based on the OPC-UA model. Specifically, the OPC-UA model may include the IEC 62541 model, but the present invention is not limited thereto.

The schema format conversion unit 230 receives the CIM profile 117 from the CIM-based data modeling unit 110 and converts the received CIM profile 117 into the OPC-UA data model 217, 270). In addition, the OPC-UA-based data modeling unit 210 may transmit the structured OPC-UA data model 217 to the server 270.

The server 270 can exchange the OPC-UA data model 217 represented by the node with the CIM-based data operation unit 130 and the OPC-UA-based data operation unit 250.

The CIM-based data operation unit 130 is included in the CIM-based system 100 that performs CIM data model-based data communication, and transmits CIM data (for example, CIM data using the IEC 61970 or IEC 61968 standard) And can communicate with the server 270. [ Specifically, the CIM data received from the external system is converted into a form accessible to the server by the first proxy 135 and transferred to the server. When the specific data of the server is changed, the first proxy 135 transfers the CIM data to the external system .

The OPC-UA-based data operation unit 250 is included in the OPC-UA-based system 200 that performs OPC-UA data model-based data communication and transmits OPC-UA data (for example, OPC-UA data using the IEC 62541 standard, UA data) from an external system and communicate with the server 270. [ Specifically, the OPC-UA data received from the external system is converted into a form accessible to the server by the second proxy 255 and transferred to the server. When the specific data of the server is changed, System. However, the present invention is not limited thereto.

4 is a flowchart illustrating a data interoperability method according to an embodiment of the present invention. For the sake of convenience of description, the same elements as those of the above-described embodiment will be described below with the exception of duplicate descriptions.

Referring to FIG. 4, the data interoperability method according to an embodiment of the present invention can be divided into data modeling in design-time and data operation in run-time. At this time, the structure of the server 270 and the communication method of the server 270 include using the OPC-UA standard. However, the present invention is not limited thereto.

Data modeling at design time can include CIM data model-based data modeling and OPC-UA-based data modeling.

The CIM data model-based data modeling generates the CIM profile 117 through the first data designer 115. Specifically, the first data designer 115 may receive the CIM data model using the IEC 61970 or IEC 61968 standard, and may generate the CIM profile 117 based on the received CIM data model.

The CIM profile 117 may include a subset or an expanded CIM profile 117 based on the CIM data model in the data designer. For example, the subset CIM profile 117 includes a selectively structured CIM profile 117 only for data that the user needs based on the CIM data model. In addition, the extended CIM profile 117 includes a CIM profile 117 that adds data attributes based on the CIM data model. At this time, the first data designer 115 may convert the CIM profile 117 into a logical data structure to be logically organized. However, the present invention is not limited thereto.

Then, the OPC-UA data model 217 is generated through the schema format conversion unit 230. Specifically, the OPC-UA data model 217 using the IEC 62541 OPC-UA standard can be generated according to a predetermined conversion rule 235 based on the CIM profile 117 generated by the schema format conversion unit 230 have. For example, the predetermined conversion rule 235 includes a mapping rule for mapping the CIM meta model and the OPC-UA meta model. However, the present invention is not limited thereto.

Then, the OPC-UA data model 217 is stored in the server 270. Specifically, the generated OPC-UA data model 217 can be structured and stored in the server 270. Specifically, the OPC-UA data model 217 may include the Nodeset2.xml format.

The OPC-UA-based data modeling generates the OPC-UA data model 217 through the second data designer 215. Specifically, the OPC-UA model using the IEC 62541 standard may be received by the second data designer 215, and the OPC-UA data model 217 may be generated based on the received OPC-UA model. At this time, the second data designer 215 may convert the OPC-UA data model 217 into a logical data structure to be logically organized. However, the present invention is not limited thereto.

Then, the OPC-UA data model 217 is stored in the server 270. Specifically, the OPC-UA data model 217 can be structured and stored in the server 270. Specifically, the OPC-UA data model 217 may include the Nodeset2.xml format.

Runtime data operations can include CIM data model-based data operations and OPC-UA-based data operations. However, the present invention is not limited thereto.

The CIM data model-based data operation receives CIM data from the CIM-based system 100. Specifically, the CIM-based data operation unit 130 can receive the CIM data using the IEC 61970 or IEC 61968 standard.

Then, the data format conversion unit 133 converts the data into OPC-UA-based data. Specifically, the CIM data received according to the conversion rule 235 predetermined by the data format conversion unit 133 can be converted into the first OPC-UA data using the IEC 62541 OPC-UA standard. For example, the predetermined conversion rule 235 includes a mapping rule for mapping the CIM meta model and the OPC-UA meta model. However, the present invention is not limited thereto.

Then, OPC-UA data is transmitted to the server 270 through the first proxy 135. Specifically, the first proxy 135 converts the first OPC-UA data converted by the data format conversion unit 133 into a second OPC-UA data of a predetermined type represented by a node, , And may store the second OPC-UA data in the server 270. For example, the predetermined type of OPC-UA data may include OPC-UA data represented by a node of a type accessible to the server 270. Specifically, each node may include attribute information such as id and name. For example, the OPC-UA data may include the NodeSet2.xml format. However, the present invention is not limited thereto.

At this time, the data converted from the data format conversion unit 133, the schema format conversion unit 230, the first proxy 135 and the second proxy 255 and stored in the server, or the data transferred to the server, Lt; RTI ID = 0.0 > XML format. ≪ / RTI > Specifically, the first OPC-UA data may be converted into a second OPC-UA in an XML format modeled to correspond to a schema structure stored in the server in the first proxy 135. For example, the second OPC-UA data may include attribute information such as id and name, and may include modeled XML data of a schema structure represented by a node (Node). At this time, a node includes a logical structure that abstracts the structure of data in order to model data. A node may logically structure data by id, name, value, class, etc., and may receive attribute information or an identifier from the data designer, the format conversion unit, or the proxy, which allows the data to access the logical structure. However, the present invention is not limited thereto.

Then, when the specific data of the server 270 is changed, the data is transmitted to the data format conversion unit 133 via the first proxy 135. Specifically, when the data stored in the server 270 is changed based on the second OPC-UA data, the second OPC-UA data may be transmitted to the data format converter 133 via the proxy.

Then, the data is converted into CIM data through the data format conversion unit 133 and transmitted to the CIM-based system. Specifically, the data format conversion unit 133 may convert the second OPC-UA data into CIM data, and transmitting the converted CIM data.

The OPC-UA-based data operation receives OPC-UA data from the OPC-UA based system 200. Specifically, the OPC-UA data using the IEC 62541 OPC-UA standard can be received by the OPC-UA-based data operation unit 250.

Then, OPC-UA data is transmitted to the server 270 through the second proxy 255. [ Specifically, the OPC-UA data received by the second proxy 255 may be converted into a second OPC-UA data of a predetermined type represented by a node and transmitted to the server 270. At this time, the proxy communicating with the server 270 using the predetermined data communication rule is included in the first proxy 135 and the OPC-UA-based data operation unit 250 included in the CIM-based data operation unit 130 Lt; RTI ID = 0.0 > 255 < / RTI > However, the present invention is not limited thereto.

Then, when the specific data of the server 270 is changed, OPC-UA data is transmitted to the OPC-UA-based system 200 through the second proxy 255. [ Specifically, when data stored in the server 270 is changed based on the second OPC-UA data, the second OPC-UA data may be converted into OPC-UA data through the second proxy 255 and transmitted . For example, the second proxy 255 receives the second OPC-UA data and transmits the OPC-UA data to the server 270 so as to have attribute information such as id and name, Can be converted. At this time, when the data stored in the server 270 is changed, the second OPC-UA data can be converted into OPC-UA data used in the communication of the OPC-UA-based data operation unit 250 and transmitted. However, the present invention is not limited thereto.

5 is a diagram illustrating a data interoperability system according to another embodiment of the present invention. For the sake of convenience of description, the same elements as those of the above-described embodiment will be described below with the exception of duplicate descriptions.

5, the data interoperability system according to another embodiment of the present invention includes an XML data modeling unit 310, a first data designer 315, a schema format conversion unit 230, an OPC-UA- A second data designer 215, a server 270, an XML data operation unit 330, a data format conversion unit 333, a first proxy 335, an OPC-UA-based data operation unit 250, , And a second proxy (255).

The XML data modeling unit 310 and the XML data operation unit 330 may be included in an XML based system that performs XML data communication using XML (Extensible Markup Language) data.

The XML data modeling unit 310 includes a module, a program, or a computer device that performs data modeling based on an XML data model. Specifically, the XML data model may include an XML data model used in XML data communication. In addition, the XML data operation unit 330 may receive XML data and communicate with the server 270. However, the present invention is not limited thereto.

6 is a flowchart illustrating a data interoperability method according to another embodiment of the present invention. For the sake of convenience of description, the same elements as those of the above-described embodiment will be described below with the exception of duplicate descriptions.

Referring to FIG. 6, the data interoperability method according to another embodiment of the present invention can be divided into design-time and run-time data operations.

Data modeling at design time can include XML data model-based data modeling and OPC-UA-based data modeling. For reference, a detailed description of OPC-UA-based data modeling is omitted above.

The XML data model-based data modeling generates the XML schema 317 through the first data designer 315. Specifically, the first data designer 315 receives the XML data, and generates the XML schema 317 based on the received CIM data. At this time, the first data designer 315 can convert the XML schema 317 into a logical data structure so as to be logically organized. However, the present invention is not limited thereto.

Then, the OPC-UA data model 217 is generated through the schema format conversion unit 230. Specifically, an OPC-UA data model 217 using the IEC 62541 OPC-UA standard can be generated according to a predetermined conversion rule 235 based on the XML schema 317 generated by the schema format conversion unit 230 have. For example, the predetermined conversion rule 235 includes a mapping rule for mapping the XML metamodel and the OPC-UA metamodel. However, the present invention is not limited thereto.

Runtime data operations can include CIM data model-based data operations and OPC-UA-based data operations. For reference, a detailed description of OPC-UA-based data operation has been omitted above.

XML data model-based data operations receive XML data from an XML-based system. More specifically, the XML-based data operation unit can receive the XML data.

Then, the data format conversion unit 333 converts the data into OPC-UA-based data. Specifically, the data format converting unit 333 may convert the received first XML data into the first OPC-UA data using the IEC 62541 OPC-UA standard according to a predetermined conversion rule 235. For example, the predetermined conversion rule 235 includes a mapping rule for mapping the XML metamodel and the OPC-UA metamodel. However, the present invention is not limited thereto.

Then, the OPC-UA data is transmitted to the server 270 through the first proxy 335. Specifically, the first proxy 335 converts the first OPC-UA data converted by the data format conversion unit 133 into a second OPC-UA data of a predetermined type represented by a node, ). ≪ / RTI > For example, the predetermined type of OPC-UA data may include OPC-UA data represented by a node of a type accessible to the server 270. Specifically, each node may include attribute information such as id and name. For example, the OPC-UA data may include the NodeSet2.xml format. However, the present invention is not limited thereto.

Then, when the specific data of the server 270 is changed, the data is transmitted to the data format conversion unit 333 through the first proxy 335. Specifically, when the data stored in the server 270 is changed based on the second OPC-UA data, the second OPC-UA data may be transmitted to the data format converter 333 via the proxy.

Subsequently, the data is converted into XML data through the data format conversion unit 333 and transmitted to the XML-based system. Specifically, the data format converting unit 333 may convert the second OPC-UA data to second XML data, and transmitting the converted second XML data to the XML-based system. However, the present invention is not limited thereto.

FIG. 7 is a view for explaining the conversion rules of FIGS. 4 and 6 according to an embodiment of the present invention.

Referring to FIG. 7, the transformation rule 235 according to an embodiment of the present invention may include a mapping rule for mapping the CIM meta model and the OPC-UA meta model. Specifically, the CIM metamodel includes a CIM metamodel for modeling the CIM data model, which is a superordinate concept for the CIM data model, that is, a one-dimensional abstraction and structuring of the CIM data model. In addition, the OPC-UA metamodel is a superordinate concept for the OPC-UA data model 217, that is, an OPC-UA data model 217 for modeling the OPC-UA data model 217 for one-dimensional abstraction and structuring of the OPC- OPC-UA meta-model.

The mapping rule maps the CIM class to the UA Object, maps the CIM class inheritance relationship to the HasSub Type Reference Type, maps the association between the CIM classes to the non-symmetric reference type, maps the Aggregation between the CIM classes to the Reference Type, Map the Attribute of the CIM class to the Property or Variable Type, map the Data Type and Enumeration class to the Data Type, map the Property of the CIM Class to the Variable Type, map the CIM element name to the BrowerName, DisplayName, and Attribute , And mapping the CIM element description to Description. However, the present invention is not limited thereto.

At this time, the mapping rule is automatically mapped to each CIM object, not the automatic mapping at the metamodel level, since the CIM metamodel and the OPC-UA metamodel do not correspond one to one. That is, not all CIM classes are converted into OPC UA objects, but CIM class substation objects can be converted into OPC UA substation objects. However, the present invention is not limited thereto.

At this time, when the CIM standard is revised, the mapping rule can be applied to the revised CIM standard by modifying the mapping rule according to the revision or change. Specifically, the changes are verified by comparing the revised CIM standard with the existing CIM standard. Then, if the change is a new class, add a mapping rule for content related to the class (Attribute, Association, Aggregation, Inheritance, etc.). However, the present invention is not limited thereto.

8 is a flowchart illustrating a method of generating an OPC-UA data model according to an embodiment of the present invention.

Referring to FIG. 8, a method of generating an OPC-UA data model 217 according to an embodiment of the present invention receives a CIM class from a CIM profile 117 (S110). Specifically, the schema format conversion unit 230 may receive the CIM profile 117 from the CIM-based data modeling unit and receive the CIM class from the CIM profile 117.

Then, the CIM class and the OPC-UA mapping are performed (S120). Specifically, the CIM class is mapped to a UA Object according to a mapping rule. For example, the mapping rules may include mapping rules that map the CIM metamodel and the OPC-UA metamodel. However, the present invention is not limited thereto.

Then, the CIM profile 117 is converted into an OPC-UA data model 217 and generated (step S130). Specifically, the OPC-UA data model 217 can be generated by converting the CIM profile 117 corresponding to the CIM class into the OPC-UA data model 217 using the mapped CIM class.

Then, the validation test is performed on the generated OPC-UA data model 217 (S140). Specifically, a data validation check on a structure, a list, a content, and the like can be performed to prevent data errors that may occur at design time or run time. However, the present invention is not limited thereto.

The above-described data interoperability method is not limited to the configuration and method of the embodiments described above, but the embodiments may be modified such that all or some of the embodiments are selectively combined so that various modifications can be made. .

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

110: CIM-based data modeling unit
130: CIM-based data operation unit
210: OPC-UA-based data modeling unit
230: schema format conversion unit
250: Data processing unit based on OPC-UA
270: Server

Claims (14)

Receiving a CIM data model using a communication standard model in a data designer, and creating a CIM profile based on the received CIM data model;
Generating an OPC-UA data model according to a predetermined conversion rule including a mapping rule for mapping a CIM meta model and an OPC-UA meta model based on the CIM profile in a schema format conversion unit; And
And structuring and storing the generated OPC-UA data model in a form including a node in a server
Data interoperability method.
The method according to claim 1,
And transmitting and receiving data corresponding to the OPC-UA data model using a proxy communicating with the server using a predetermined data communication rule
Data interoperability method.
The method according to claim 1,
The communication standard model includes the IEC 61970 CIM standard or the IEC 61968 CIM standard,
The OPC-UA data model includes using the IEC 62541 OPC-UA standard
Data interoperability method.
The method of claim 3,
Wherein the generating the OPC-UA data model comprises:
Receiving a CIM class from the CIM profile;
Mapping the CIM class to a UA Object according to the mapping rule;
Transforming and creating the CIM profile into the OPC-UA data model using the mapped CIM class; And
And performing an validation check on the generated OPC-UA data model
Data interoperability method.
The method according to claim 1,
The CIM profile,
Wherein the data designer includes a subset or an expanded CIM profile based on the CIM data model
Data interoperability method.
The method according to claim 1,
The data designer,
Converting the generated CIM profile into a logical data structure
Data interoperability method.
The method according to claim 1,
The OPC-UA data model includes:
Which is converted from the data designer into a logical data structure, including the Nodeset2.xml format
Data interoperability method.
The method according to claim 1,
Wherein the generating the OPC-UA data model comprises:
Receiving an OPC-UA model using the IEC 62541 standard in the data designer and generating the OPC-UA data model based on the received OPC-UA model;
Data interoperability method.
The method according to claim 1,
Wherein the generating the OPC-UA data model comprises:
Receiving XML data from the data designer and generating an XML schema based on the received XML data; And
And generating the OPC-UA data model according to the predetermined conversion rule based on the generated XML schema in a schema format conversion unit
Data interoperability method.
Receiving CIM data using a communication standard model;
Converting the received CIM data into first OPC-UA data according to a predetermined conversion rule including a mapping rule for mapping the CIM meta model and the OPC-UA meta model in the data format conversion unit;
Converting the first OPC-UA data into a second OPC-UA data of a predetermined type represented by a node and transmitting the second OPC-UA data to the server, and storing the second OPC-UA data in the server;
Transmitting the changed second OPC-UA data to the server through the proxy to the data format conversion unit when the second OPC-UA data is changed;
Converting the second OPC-UA data into CIM data in the data format conversion unit; And
And transmitting the converted CIM data
Data interoperability method.
11. The method of claim 10,
The communication standard model includes the IEC 61970 CIM standard or the IEC 61968 CIM standard,
Wherein the first OPC-UA data and the second OPC-UA data comprise using an IEC 62541 OPC-UA standard
Data interoperability method.
11. The method of claim 10,
The proxy,
A first proxy included in the CIM-based data operation unit and a second proxy included in the OPC-UA-based data operation unit,
Wherein the first proxy and the second proxy communicate with the server using a predetermined data communication rule
Data interoperability method.
13. The method of claim 12,
The step of receiving the CIM data comprises:
Including receiving OPC-UA data using the IEC 62541 OPC-UA standard,
The second proxy converts the received OPC-UA data into the second OPC-UA data of a predetermined type represented by a node and transmits the second OPC-UA data to the server, Lt; / RTI >
And converting the second OPC-UA data to the OPC-UA data through the second proxy and transmitting the OPC-UA data
Data interoperability method.
11. The method of claim 10,
The step of receiving the CIM data comprises:
Comprising receiving XML data,
The step of converting into the first OPC-UA data comprises:
And converting the received XML data into the first OPC-UA data,
The step of converting into CIM data comprises:
And converting the second OPC-UA data to the XML data, and transmitting the converted XML data
Data interoperability method.

Images