KR20230030281A - Apparatus and method for converting of common information model based on ontology - Google Patents

Abstract

Disclosed are an ontology-based common information model (CIM) converting apparatus and a method. The ontology-based common information model converting apparatus, according to one embodiment of the present invention, comprises: a key management unit which issues respective hashcode for each row of a table to be converted within a database of an external system or legacy system, and based on each hashcode, issues master resource id (mRID) of each row to manage information of each row of the table to be converted; a triple conversion processing unit which receives sequentially information of all rows of the table to be converted to generate a first hashcode for each row information, searches an mRID pairing with the generated first hashcode, and converts respective row information of the table to be converted into a triple; and a common model conversion processing unit which, according to a predefined conversion rule, converts a triple set of the table to be converted, of which each row information is converted into a triple, into a common information model-based triple. The purpose of the present invention is to provide the ontology-based common information model (CIM) converting apparatus and a method, which can make a conversion at a triple level, expression of logical information, not a conversion at a source code level, for schema conversion of legacy data or database model into a common information model.

Description

Ontology-based standard information model conversion device and method {APPARATUS AND METHOD FOR CONVERTING OF COMMON INFORMATION MODEL BASED ON ONTOLOGY}

The present invention relates to an ontology-based standard information model conversion apparatus and method, and more particularly, when converting a schema from a legacy type data or database model to a standard information model, rather than conversion processing at the source code level, logical information It relates to an ontology-based standard information model conversion apparatus and method capable of performing conversion processing in a triple stage, which is an expression of.

Recently, interest in urban energy management has been increasing worldwide, and smart city technology development is spreading mainly in Europe, Japan, and North America.

In order to create energy businesses and services in the city based on data classified and collected by various energy components in the smart city, the smart city platform must be scalable and an information model to support it is needed.

In order to expand various services, a unified information model must be provided. Accordingly, the conversion rules of original data for each service are defined, processed according to the rules, and stored as a standard information model.

The data information used in smart city is determined by the developer or manufacturer of the system, so it is composed of different information models or databases. In order to provide this to users in a unified format, schema conversion is required.

If the schema conversion work is implemented at the source code level, additional source code work is required when the system developer or system is changed. In addition, when a failure occurs in the process of providing data to a user, it is difficult to respond to which schema the problem occurred.

Therefore, when converting a schema from legacy data or database model to a standard information model, technology that enables conversion processing at the triple level, which is a logical expression of information, rather than conversion processing at the source code level development is required.

The background art of the present invention is disclosed in Registered Patent Publication No. 10-1666623 (2016.10.14. Notice).

The present invention has been devised to improve the above problems, and an object according to one aspect of the present invention is a logical, rather than conversion process at the source code level, when converting a schema from a legacy type data or database model to a standard information model. It is to provide an ontology-based standard information model conversion apparatus and method capable of performing conversion processing at the triple stage, which is the expression of information.

The problem to be solved by the present invention is not limited to the above-mentioned problem (s), and another problem (s) not mentioned will be clearly understood by those skilled in the art from the following description.

An ontology-based standard information model conversion apparatus according to an aspect of the present invention issues a hash code for each row of a conversion target table in a database of an external system or a legacy system, respectively, and issues each hash code. A key management unit that manages each row information of the table to be converted by issuing a master resource id (mRID) of each row based on a code, sequentially receiving all row information of the table to be converted and first hash for each row information A triple conversion processing unit that generates a code, searches for an mRID paired with the generated first hash code, and converts each row information of the conversion target table into a triple, and each row information is converted into a triple and a standard model conversion processing unit that converts the set of triples of the converted conversion target table into triples based on the Common Information Model (CIM) according to predefined conversion rules.

In the present invention, the key management unit may issue a hash code for each row based on an index value included in information on each row of the table to be converted.

The present invention further includes a first storage unit, and the key management unit includes a table name (Source TableName) for each row of the conversion target table, a hash code (HashCode) of the corresponding row, and an mRID paired with the hash code of the corresponding row. By matching and generating a key relationship table and storing the key relationship table in the first storage unit, information on each row of the conversion target table can be managed.

In the present invention, the triple conversion processing unit searches the first storage unit with the first hash code to search the mRID of a corresponding row, uses the searched mRID as a Subject, and sets a column name of the corresponding row as Preidcate. and create a triple with the value of each column as an object.

In the present invention, in the conversion rule, the conversion target table name, the predicate name of the conversion target table, the class name and attribute name of the standard information model corresponding to the conversion target table name and predicate name may be defined.

In the present invention, the standard model conversion processing unit sequentially receives triples in the triple set of the conversion target table, searches whether a conversion rule exists for the input triples, and if there is a conversion rule, determines whether or not a conversion rule exists. Accordingly, the predicate name of the input triple can be changed to an attribute name.

In the present invention, the standard model conversion processing unit may generate a class name corresponding to the mRID of the input triple only once initially, when a conversion rule for the input triple exists.

In the ontology-based standard information model conversion method according to another aspect of the present invention, the key management unit issues hash codes for each row of a conversion target table in a database of an external system or a legacy system, respectively. and issuing mRID (master resource id) of each row based on each hash code to manage information on each row of the conversion target table, wherein the triple conversion processing unit sequentially inputs all row information of the conversion target table receiving and generating a first hash code for each row information, searching for an mRID paired with the generated first hash code, and converting each row information of the table to be converted into a triple, standard model conversion and converting, by a processing unit, a set of triples in a conversion target table in which each row information is converted into triples into a Common Information Model (CIM)-based triple according to a predefined conversion rule.

In the step of managing each row information of the conversion target table, the key management unit may issue a hash code for each row based on an index value included in each row information of the conversion target table.

In the step of managing information on each row of the conversion target table, the key management unit includes a table name (Source TableName), a hash code of the corresponding row, and a hash of the corresponding row for each row of the conversion target table. By matching mRIDs paired with codes to create a key relationship table and storing the key relationship table in the first storage unit, information on each row of the conversion target table can be managed.

In the present invention, in the step of converting each row information of the conversion target table into a triple, the triple conversion processor searches the first storage unit with the first hash code to search for the mRID of the corresponding row, and the search You can create a triple with the specified mRID as the subject, the column name of the corresponding row as the preidcate, and the value of each column as the object.

In the present invention, in the conversion rule, the conversion target table name, the predicate name of the conversion target table, the class name and attribute name of the standard information model corresponding to the conversion target table name and predicate name may be defined.

In the step of converting the standard information model (CIM: Common Information Model)-based triples, the standard model conversion processing unit sequentially receives triples in the triple set of the table to be converted, and converts the input triples into triples. It searches whether a conversion rule exists in the target, and if there is a conversion rule, the predicate name of the input triple can be changed to an attribute name according to the conversion rule.

In the present invention, in the step of converting to a triple based on the standard information model (CIM: Common Information Model), the standard model conversion processing unit, if there is a conversion rule for the input triple, converts the mRID of the input triple The corresponding class name can be created only once initially.

An ontology-based standard information model conversion apparatus and method according to an embodiment of the present invention changes a row of a table of a general database into a set of triples, and attributes the predicate names of the changed triples according to conversion rules. By changing the name, when converting a schema from a legacy type data or database model to a standard information model, it is possible to perform conversion processing at the triple stage, which is a logical expression of information, rather than conversion processing at the source code level. Through this, it is possible to easily perform linkage work without separately developing real-time conversion processing of various information models and database models of smart city-related developers and manufacturers to standard information models.

The ontology-based standard information model conversion apparatus and method according to an embodiment of the present invention can provide services without additional work as long as the conversion rules are defined even if the developer or manufacturer changes or the system changes, and when distributing CIM profiles in the future, OPC-UA standard-based model linkage and service provision are possible.

On the other hand, the effects of the present invention are not limited to the effects mentioned above, and various effects may be included within a range apparent to those skilled in the art from the contents to be described below.

1 and 2 are diagrams for explaining an ontology-based standard information model conversion apparatus according to an embodiment of the present invention.
3 is an exemplary diagram for explaining a table of a legacy DB according to an embodiment of the present invention.
4 and 5 are views for explaining the operation of the key management unit shown in FIG. 1 .
FIG. 6 is a diagram for explaining the operation of the triple conversion processing unit shown in FIG. 1 .
FIG. 7 is a diagram for explaining the operation of the standard model conversion processing unit shown in FIG. 1;
8 is a flowchart illustrating a method for converting an ontology-based standard information model according to an embodiment of the present invention.

Hereinafter, an ontology-based standard information model conversion apparatus and method according to an embodiment of the present invention will be described with reference to the accompanying drawings. In this process, the thickness of lines or the size of components shown in the drawings may be exaggerated for clarity and convenience of explanation. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, definitions of these terms will have to be made based on the content throughout this specification.

Implementations described herein may be embodied in, for example, a method or process, an apparatus, a software program, a data stream, or a signal. Even if discussed only in the context of a single form of implementation (eg, discussed only as a method), the implementation of features discussed may also be implemented in other forms (eg, an apparatus or program). The device may be implemented in suitable hardware, software and firmware. The method may be implemented in an apparatus such as a processor, which is generally referred to as a processing device including, for example, a computer, microprocessor, integrated circuit, programmable logic device, or the like. Processors also include communication devices such as computers, cell phones, personal digital assistants ("PDAs") and other devices that facilitate communication of information between end-users.

1 and 2 are diagrams for explaining an ontology-based standard information model conversion device according to an embodiment of the present invention, and FIG. 3 is an exemplary diagram for explaining a table of a legacy DB according to an embodiment of the present invention. 4 and 5 are diagrams for explaining the operation of the key management unit shown in FIG. 1, FIG. 6 is a diagram for explaining the operation of the triple conversion processing unit shown in FIG. 1, and FIG. 7 is the standard model conversion shown in FIG. It is a diagram for explaining the operation of the processing unit.

1 and 2, the ontology-based standard information model conversion apparatus according to an embodiment of the present invention includes a key management unit 110, a first storage unit 120, a triple conversion processing unit 130, and a standard model conversion processing unit. (140) and a second storage unit (150).

The key management unit 110 issues a hash code for each row of the conversion target table in the database 10 of an external system or legacy system, respectively, and determines the value of each row based on each hash code. A master resource id (mRID) may be issued.

The database 10 of the legacy system may be composed of a plurality of tables, and each table may be composed of a set of row information composed of indexes, column names, and column values. In this case, the index may have one or more values. For example, as shown in FIG. 3, the index may include three indices of "Index A PK", "Index B FK", and "Index C FK".

As such, since the table is composed of a set of index information and a set of general information, the key management unit 110 may apply a method of managing a combination of index values in a hash code in a way to distinguish rows.

That is, the key management unit 110 issues a hash code for each row based on the index value of each row of the table to be converted, and issues a master resource id (mRID) capable of distinguishing a subject based on the issued hash code. can At this time, the key management unit 110 may issue a hash code based on a combination of index values.

On the other hand, Triple is divided into Subject, Predicate, and Object, Subject is a specific ID for distinguishing objects, and mRID can be used in the present invention, Predicate means the name of a property, and Object means a value. can do.

Accordingly, when the conversion target table as shown in FIG. 3 is input, the key management unit 110 may issue a specific ID (ie, mRID) by pre-processing the value of the index set in order to distinguish uniqueness of one row. At this time, the key management unit 110 may use a HashCode issuing technique.

Specifically, the key management unit 110 may check an index column in one row and issue a hash code using each value of the index columns.

For example, if there are three index columns of "Index A PK", "Index B FK", and "Index C FK" as in Row 1 shown in FIGS. 4 and 5, the key management unit 110 Recognizes each value (11, 21, 31) of the three Index columns as a string, calculates the hash code of each individual value, and multiplies it with a specific real number and decimal value to unit Int type values can be extracted.

When issuance of the hash code is completed, the key management unit 110 may issue an mRID capable of distinguishing a subject based on the issued hash code. At this time, the key management unit 110 may issue the mRID using a universally unique identifier (UUID) method. The issued hash code and mRID can be paired with each other.

For example, as shown in FIG. 5 , the key management unit 110 may issue “mRID-1” paired with hash code “13315151”.

The key management unit 110 may issue hash codes for all indexes for all rows of the table to be converted, and issue mRID paired with the issued hash codes.

In addition, the key management unit 110 matches the table name (Source TableName), hash code (HashCode), and mRID of the conversion target table to manage each row information to form a key relationship table 122, and creates a key relationship table 122 ) may be stored in the first storage unit 120 . For example, the key management unit 110 has the table name (Source TableName) of row 1 (row1): "TableX", hash code (HashCode): " 13315151" and mRID:"mRID-1*?**?* may be matched and stored in the first storage unit 120.

Since the key management unit 110 issues hash codes and mRIDs for all rows of the table to be converted, the first storage unit 120 may store hash codes and mRIDs for all rows. For example, in the case of "TableY" composed of four rows, TableY, the table name of row 1 (row1), hash code 1, and mRID-1 are matched and stored in the first storage unit 120, and row 2 (row2) The table name of TableY, hash code 2 and mRID-2 are matched and stored, and TableY, the table name of row 3 (row3), hash code 3 and mRID-3 are matched and stored, and table name of row 4 (row 4) is TableY , hash code 4 and mRID-4 may be matched and stored.

The triple conversion processing unit 130 may convert each row information of the conversion target table into a triple using the mRID issued by the key management unit 110 . At this time, the triple conversion processing unit 130 may convert the issued mRID into Subject, Preidcate the column name of the corresponding row, and convert the value of each column into Object. In this way, the issued mRID becomes a Subject, and one row information can be converted into a set of Subject (mRID)-Preidcate (Column name)-Object (Column value).

The triple conversion processing unit 130 sequentially receives all row information of the conversion target table, generates a hash code for each input row information, and searches the first storage unit 120 with the generated hash code to determine the value of the corresponding row. You can search for mRID, and create a triple with the searched mRID as the subject and the column name and value of the corresponding row as the preidcate and object. At this time, the triple conversion processing unit 130 may generate a hash code using the same key as the public key and encryption key used in generating the hash code in the key management unit 110 .

As such, the triple conversion processing unit 130 may convert one row into a triple by using the mRID paired with the issued hash code.

The triple conversion processor 130 will be described with reference to FIG. 6 . Referring to FIG. 6, when row 1 information of "Table X" is input, the triple conversion processing unit 130 performs a hash code "XXX" based on the index values 11, 21, and 31 of row 1 (row1). -1" can be produced. Then, the triple conversion processing unit 130 queries the first storage unit 120 with "XXX-1" of "Table X", and obtains "mRID-1", which is an mRID paired with hash code "XXX-1". can be extracted. Then, the triple conversion processing unit 130 sets the extracted "mRID-1" as the subject, preidcates the column name of the corresponding row, and converts the value of each column into an object, so that "Table X" such as A You can create a set of triples of ". For example, the triple conversion processing unit 130 converts row 1 of Table X into "mRID-1 - Index A - 11, mRID-1 - Index B - 21, mRID-1 - Index C - 31, mRID-1 - Column A - DATA A, mRID-1 - Column B - DATA B, mRID-1 - Column C - DATA C" can be converted into a triple. In the same way as above, the triple conversion processing unit 130 can convert all row information such as row 2 and row 3 of Table X into triples.

The standard model conversion processing unit 140 may convert a set of triples of a conversion target table in which each row information is converted into triples into a common information model (CIM)-based triple according to a predefined conversion rule. Here, the conversion rule is the conversion target table name, conversion target table attribute (predicate) name, conversion target table name and attribute name and class name and attribute (attribute) of the standard information model corresponding to the conversion target table name and attribute name as shown in B of FIG. name can be defined. These conversion rules can be stored in the second storage unit 150, and the conversion rules are results written in a separate program in advance, stored in a database or file format/Excel format, and then predicated when the actual final conversion is performed. It can be a material for changing .

The standard model conversion processing unit 140 performs conversion processing using the conversion rules stored in the second storage unit 150 in order to convert the triple set of the conversion target table generated by the triple conversion processing unit 130 into a standard information model form. can do.

The table information and standard information model of the legacy database (10) are all forms of information storage to express the characteristics of a thing, and the standard information model, which is composed of class names and attributes and complies with UML, is also triple. (Triple) expression is possible. In other words, legacy table or standard information model differs only in column name or attribute name Predicate, which is the meaning of value, and the value, which is the result of information, is the same. Therefore, conversion processing can be performed with conversion rules for which class and attribute names are expressed in the standard information model for column names in the legacy table.

The standard model conversion processing unit 140 sequentially receives the triples in the triple set of the conversion target table, searches the input triples to see if there is a conversion rule in the second storage unit 150, and if there is a conversion rule According to the conversion rule, the predicate name of the input triple can be changed to the attribute name. Since the triple is expressed as RDF-based information, prior to changing the name of the predicate by the conversion rule, the standard model conversion processing unit 140 determines what class the issued mRID corresponds to in the standard information model by "rdf:type" It must be specified using Predicate. Accordingly, when there is a conversion rule for the input triple, the standard model conversion processing unit 140 may generate a class name corresponding to the mRID of the input triple. At this time, the standard model conversion processing unit 140 may create a class for the corresponding table only once in the initial stage.

The standard model conversion processing unit 140 will be described with reference to FIG. 7 . Referring to FIG. 7 , the standard model conversion processing unit 140 receives input triples one by one from the triple set of the conversion target table such as A, and searches whether the conversion rule of the received triples exists in the second storage unit 150. can

For example, if the first triple ("mRID-1"-Column1-11) is input from the Triple set of TableX, the standard model conversion processing unit 140 may search whether there is a conversion rule for Column1 of TableX. As a search result, since there is no conversion rule for “Column1” of “TableX”, the standard model conversion processing unit 140 may search whether there is a conversion rule for the next triple, the second triple (“mRID-1”-Column2-21). . As such, the standard model conversion processing unit 140 may search whether or not a conversion rule exists in the second storage unit 150 for each triple of the Triple set of TableX. As a result of the search, since the conversion rule of the fourth triple ("mRID-1"-Column4-DataA) exists in the conversion target rule, the standard model conversion processing unit 140 converts "ClassX", which is the class name corresponding to "mRID-1". and "AttributeA", which is the standard information model attribute name corresponding to "Column4", can be acquired and "Column4" can be changed to "AttributeA". At this time, the standard model change processing unit can specify which class "mRID-1" corresponds to in the standard information model using "rdf:type" Predicate. Then, as shown in C, a triple of ("mRID-1"-"rdf:type"-"ClassX") can be generated, and then ("mRID-1"-"AttributeA"-"DataA") Triples can be created. Then, the standard model conversion processing unit 140 may search whether the conversion rule of the fifth triple (“mRID-1”-Column5-DataB) exists in the conversion target rule. As a result of the search, since the conversion rule of the fifth triple ("mRID-1"-Column5-DataB) exists in the conversion target rule, the standard model conversion processing unit 140 determines "AttributeB", which is the standard information model attribute name corresponding to "Column5". , you can change "Column5" to "AttributeB". That is, a triple of ("mRID-1"-"AttributeB"-"DataB") may be generated.

In this way, the standard model conversion processing unit 140 searches for all triples included in the triple set of TableX such as A to see if there is a conversion rule in the conversion target rule, and can change the triple set to a standard information model based triple set such as C.

The ontology-based standard information model conversion device constructed as above can change one row of the table of the general database 10 into a triple set, and change the predicate name of the changed triple into an attribute name according to the conversion rule.

On the other hand, a set of triples converted into standard information model type triples can be easily converted into RDF/XML under the condition that rdf is used as a basic grammar.

Since the smart city standard information model based on IEC61970 CIM-XML uses RDF / XML grammar, using the conversion processing method according to the present invention, without using direct coding, consistent key issuance and predicate in the triple area It is possible to apply a simplified conversion method through name change.

8 is a flowchart illustrating a method for converting an ontology-based standard information model according to an embodiment of the present invention.

Referring to FIG. 8, the ontology-based standard information model conversion device (hereinafter referred to as "device") hash code for each row of the conversion target table in the database 10 of the external system or legacy system ( HashCode) is issued (S810), and mRID (master resource id) of each row is issued based on each hash code to manage row information of the table to be converted (S820). At this time, the device may issue a hash code based on a combination of index values of each row of the table to be converted. After that, the device can issue an mRID that can distinguish the subject based on the issued hash code. After that, the device matches the table name (Source TableName) of the conversion target table, the issued hash code (HashCode), and the mRID paired with the hash code for management of each row information of the conversion target table to match the first storage unit ( 120) can be stored.

When step S820 is performed, the device converts each row information of the conversion target table into triples using the issued mRID (S830). That is, the device sequentially receives all row information of the conversion target table, generates a hash code for each input row information, and searches the first storage unit 120 with the generated hash code to find the mRID of the corresponding row. and a triple can be created with the searched mRID as the Subject and the column name and value of the corresponding row as the Preidcate and Object.

When step S830 is performed, the device converts the set of triples of the conversion target table, in which each row information is converted into triples, into triples based on Common Information Model (CIM) according to a predefined conversion rule (S840). That is, the device sequentially receives triples in the triple set of the table to be converted, searches the inputted triples to see if there is a conversion rule in the second storage unit 150, and if there is a conversion rule, according to the conversion rule. You can change the Predicate name of the input triple to an attribute name. At this time, the device may generate a class name corresponding to the mRID of the input triple, and may generate a class for the corresponding table only once in the initial stage. If the conversion rule does not exist, the device may determine whether the conversion rule exists for the next triple and convert it into a standard information model based triple according to the conversion rule.

As described above, the ontology-based standard information model conversion apparatus and method according to an embodiment of the present invention changes one row of a table of the general database 10 into a triple set, and the changed triples By changing the predicate name to an attribute name according to the conversion rule, when converting a schema from a legacy type data or database model to a standard information model, it is not a conversion process at the source code level, but a triple stage, which is a logical expression of information. Conversion processing can be performed. Through this, it is possible to easily perform linkage work without separately developing real-time conversion processing of various information models and database models of smart city-related developers and manufacturers to standard information models.

The ontology-based standard information model conversion apparatus and method according to an embodiment of the present invention can provide services without additional work as long as the conversion rules are defined even if the developer or manufacturer changes or the system changes, and when distributing CIM profiles in the future, OPC-UA standard-based model linkage and service provision are possible.

The present invention has been described with reference to the embodiments shown in the drawings, but this is only exemplary, and those skilled in the art can make various modifications and equivalent other embodiments. will understand

Therefore, the true technical protection scope of the present invention should be determined by the claims below.

110: key management unit
120: first storage unit
130: triple conversion processing unit
140: standard model conversion processing unit
150: second storage unit

Claims (14)

Issues a hash code for each row of the table to be converted in the database of an external system or legacy system, and issues mRID (master resource id) for each row based on each hash code. a key management unit managing information on each row of the conversion target table;
All row information of the table to be converted is sequentially input, a first hash code is generated for each row information, mRID paired with the generated first hash code is searched, and information on each row of the table to be converted is obtained. a triple conversion processing unit that converts into a triple; and
Standard model conversion processing unit for converting the triple set of the conversion target table, in which each row information is converted into triples, into triples based on the Common Information Model (CIM) according to a predefined conversion rule.
Ontology-based standard information model conversion device comprising a.
According to claim 1,
The key management unit,
An ontology-based standard information model conversion device, characterized in that for issuing a hash code for each row based on an index value included in each row information of the table to be converted.
According to claim 1,
Further comprising a first storage unit,
The key management unit creates a key relationship table by matching a table name (Source TableName), a hash code (HashCode) of a corresponding row, and an mRID paired with a hash code of a corresponding row for each row of the table to be converted, and An ontology-based standard information model conversion device, characterized in that by storing a key relationship table in the first storage unit, managing each row information of the conversion target table.
According to claim 3,
The triple conversion processing unit,
The first storage unit is searched with the first hash code to search the mRID of the corresponding row, the searched mRID is used as the Subject, the column name of the corresponding row is set as Preidcate, and the value of each column is set as Object Ontology-based standard information model conversion device, characterized in that for generating a triple (Triple) to do.
According to claim 1,
The conversion rule is an ontology-based standard information model conversion device, characterized in that the conversion target table name, the predicate name of the conversion target table, the class name and attribute name of the standard information model corresponding to the conversion target table name and predicate name are defined.
According to claim 5,
The standard model conversion processing unit,
The triples in the triple set of the table to be converted are sequentially received, and whether a conversion rule exists for the inputted triple is searched. Ontology-based standard information model conversion device, characterized in that the change to the name.
According to claim 6,
The standard model conversion processing unit,
If there is a conversion rule for the input triple, the ontology-based standard information model conversion device characterized in that the class name corresponding to the mRID of the input triple is initially generated only once.
The key management unit issues a hash code (HashCode) for each row (Row) of the conversion target table in the database of an external system or legacy system, and mRID (master resource id) of each row based on each hash code ) issuing and managing each row information of the conversion target table;
A triple conversion processing unit sequentially receives all row information of the conversion target table, generates a first hash code for each row information, searches for an mRID paired with the generated first hash code, and searches the conversion target table. converting each row of information into a triple; and
Converting, by a standard model conversion processing unit, a set of triples in a conversion target table in which each row information is converted into triples into triples based on a Common Information Model (CIM) according to a predefined conversion rule.
Ontology-based standard information model conversion method including.
According to claim 8,
In the step of managing each row information of the conversion target table,
The key management unit issues a hash code of each row based on an index value included in each row information of the conversion target table.
According to claim 8,
In the step of managing each row information of the conversion target table,
The key management unit creates a key relationship table by matching a table name (Source TableName), a hash code (HashCode) of a corresponding row, and an mRID paired with a hash code of a corresponding row for each row of the table to be converted, and An ontology-based standard information model conversion method characterized by managing each row information of the conversion target table by storing a key relationship table in the first storage unit.
According to claim 8,
In the step of converting each row information of the conversion target table into a triple,
The triple conversion processing unit queries the first storage unit with the first hash code to search the mRID of the corresponding row, uses the searched mRID as a subject, sets a column name of the corresponding row as a Preidcate, and sets each column as a subject. An ontology-based standard information model conversion method characterized by generating a triple with a value of Object.
According to claim 8,
The conversion rule is an ontology-based standard information model conversion method, characterized in that the conversion target table name, the predicate name of the conversion target table, the class name and attribute name of the standard information model corresponding to the conversion target table name and predicate name.
According to claim 12,
In the step of converting to a triple based on the standard information model (CIM: Common Information Model),
The standard model conversion processing unit sequentially receives triples in the triple set of the conversion target table, searches whether a conversion rule exists for the inputted triples, and if there is a conversion rule, the conversion rule is input according to the conversion rule. An ontology-based standard information model conversion method characterized by changing the predicate name of the triple to the attribute name.
According to claim 13,
In the step of converting to a triple based on the standard information model (CIM: Common Information Model),
The standard model conversion processing unit, if a conversion rule for the input triple exists, the ontology-based standard information model conversion method, characterized in that for generating a class name corresponding to the mRID of the input triple only once initially.

Images