WO2015167224A1

WO2015167224A1 - Cmd data converting method for smart grid

Info

Publication number: WO2015167224A1
Application number: PCT/KR2015/004262
Authority: WO
Inventors: 정재기; 최윤종; 김석중; 홍순영
Original assignee: 한빛이디에스(주)
Priority date: 2014-04-29
Filing date: 2015-04-28
Publication date: 2015-11-05
Also published as: KR101572587B1; KR20150124583A

Abstract

The present invention relates to a power equipment condition monitoring and diagnosis (CMD) data converting method for a smart grid, which can provide compatibility between data structures when a data node and a sensor node installed for CMD have different data structures. A CMD data converting method according to a preferred embodiment of the present invention comprises the steps of: receiving, by a data node, a conversion reference information ID and data conversion reference information identified by the conversion reference information ID from a sensor node; registering, by the data node, the data conversion reference information having the conversion reference information ID matched thereto on the data node; receiving, by the data node, monitoring data, a sensor node attribute information ID, and a data conversion reference information ID from the sensor node; acquiring, by the data node, a data class-data attribute by preparing PD-LD-LN information using the sensor node attribute information ID and converting the monitoring data using data conversion reference information identified by the data conversion reference information ID; and transmitting, by the data node, data having an IEC 61850 data structure having a PD-LD-LN-data class-data attribute layer architecture to a monitor node.

Description

How to convert CMD data for smart grid

The present invention relates to a CMD data converting method for a smart grid, and can provide compatibility between data structures and sensor nodes installed for power facility CMD (Condition Mornitoring and Diagnosis) when the data nodes have different data structures. The present invention relates to a CMD data converting method.

In the power industry, standards for communication systems have provided standards for many years to effectively exchange important information such as control commands, status information and measurement data. As the number of information increased, existing standards began to reach their limits and began in 1995 as the Standardization Project (IEC 61850) raised these problems.

As a result, IEC TC 57 (Power systems management and associated information exchange) allows the exchange of data between protective devices (IEC 60870-5-103) and control sensors (IEC 60870-5-101). We developed and enacted specific standards related to.

IEC 61850 provides a framework for a very wide range of data models, where the data model is not limited to previously used information such as measurements.

IEC 61850 is a data structure provided to IEC 61850 clients and presents a hierarchical structure such as PD (Logical Device) -LD (Logical Device) -LN (Logical Node) -Data Class-Data Attribute.

Existing sensor node platform technologies include Korean Patent Publication No. 2011-0120810, Korean Patent Publication No. 2013-0003615, and the like.

Korean Patent Publication No. 2011-0120810 relates to a technology for accommodating a sensor having various interfaces through a universal interface, downloading a sensor device driver through the universal interface, and controlling the sensor using the downloaded sensor device driver.

Korea Patent Publication No. 2013-0003615 provides a plug and plug function between a sensor node and a sensor module, and when the sensor module is connected to the sensor node, the sensor node receives a sensor ID, a sensor device driver, and a sensor application profile from the sensor module. It is about.

As described above, the existing sensor node platform technology approaches the sensor node platform in terms of hardware media compatible with various sensors.

As previously seen, many data nodes installed in substations in a smart grid environment must provide power device status information and measurement information to IEC 61850 clients such as SCADA in a data structure specified in IEC 61850.

However, the lower node of the data node, that is, the sensor node, is not subject to standardization according to IEC 61850. Therefore, the sensor node can be arbitrarily set up by the power equipment diagnostic system builder. In addition, it is common for the installed sensor node to not support the data structure of IEC 61850.

In this situation, the data node must be able to convert data collected from the sensor node to conform to the IEC 61850 format. In smart grids, sensor node platforms need to have a “universal” concept through data compatibility.

However, the existing sensor node platform did not provide data compatibility suitable for smart grid.

Accordingly, the present invention is to provide a CMD data converting method that can provide compatibility between the data node and the sensor node that is installed for the power equipment CMD has a different data structure.

Other objects of the present invention will be readily understood through the following description of the embodiments.

CMD data converting method according to an embodiment of the present invention for achieving the above object is a data node receiving a data conversion reference information identified by the conversion reference information ID and the conversion reference information ID from the sensor node step; Registering, by the data node, the data conversion criteria information on the data node by matching the conversion criteria information ID; The data node receiving monitoring data, sensor node attribute information ID and data conversion reference information ID from the sensor node; The data node provides PD-LD-LN information using the sensor node attribute information ID, and converts the monitoring data using data conversion reference information identified by the data conversion reference information ID. Obtaining an attribute; And transmitting, by the data node, data having the IEC 61850 data structure having the PD-LD-LN-Data Class-Data Attribute hierarchy to the monitor node.

Wherein the data node receives the sensor node attribute information ID; And authenticating the sensor node using the sensor node attribute information ID.

When receiving the monitoring data, the sensor node attribute information ID, and the data conversion reference information ID, a hash value for the data conversion reference information ID may be further received.

As described above, when the data node and the sensor node installed for the power plant condition mornitoring and diagnosis (CMD) have different data structures, the present invention can provide compatibility between the data structures.

1 shows a schematic diagram of a USP system structure to which the present invention is applied.

2 shows an IEC 61850 data structure.

3 is a functional block diagram of a sensor node according to an exemplary embodiment of the present invention.

4 shows a functional block diagram of a data node according to one preferred embodiment of the present invention.

5 is a ladder chart illustrating a CMD data converting method according to an embodiment of the present invention.

6 is a functional block diagram of a sensor node according to another embodiment of the present invention.

7 is a functional block diagram of a data node according to another embodiment of the present invention.

8 is a ladder chart illustrating a CMD data converting method according to another embodiment of the present invention.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing the drawings, similar reference numerals are used for similar elements. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.

The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be.

On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art.

Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

First, the terms used below are defined.

Universal Sensor Platform (USP): An environment or specification that can provide compatibility between sensor nodes with various data structures and IEC 61850 data structures.

Sensor Node (SN): A node that is directly connected to a sensor to acquire data from the sensor, perform data operations, and perform primary analysis. The sensor node can be equipped with a diagnostic engine for Condition Morniting and Diagnois (CMD). The sensor node may only have a measurement function.

Data Node (DN): A node that receives data from sensor nodes and collects data and forwards them to a higher level. The data node may be an IEC 61850 Teminal Node. There is no limit to the number of sensor nodes connected to a data node.

Monitor Node (MN): A node that plays a role of displaying data received from a sensor node or a data node on a screen so that a user can clearly see. A monitor node can mean a remote control device including a SCADA in a smart grid. The monitor node may be any one of the IEC 61850 Client Nodes. Here, the IEC 61850 Client Node may be a node that transmits and receives data or control command signals according to the IEC 61850 standard.

First, the USP system structure to which the present invention is applied will be described with reference to FIG. 1. 1 shows a schematic diagram of a USP system structure to which the present invention is applied.

Referring to FIG. 1, the USP system includes at least one sensor node SN, at least one data node DN, a sensor node SN, or a data node DN. It may include at least one monitor node (MN) that is an upper node. The sensor node SN and the data node DN may each be implemented in multiple layers. Unlike FIG. 1, the USP system may be implemented as one sensor node SN and a monitor node MN in the simplest form.

The USP system may have a tree structure consisting of a monitor node (MN) that is a top node, a data node (DN) that is an intermediate node, and a sensor node (SN) that is a bottom node. In addition, a plurality of data nodes DN may have a mesh or a ring structure. A database storing information used to implement the USP in the USP system may be added. This will be described later.

Hereinafter, the IEC 61850 data structure will be described with reference to FIG. 2. 2 shows an IEC 61850 data structure. For convenience of description below, it is assumed that the data node DN is an IEC 61850 terminal node and the monitor node MN is an IEC 61850 client node.

As is well known, the IEC 61850 data structure has a hierarchical structure such as PD (Physical Device) -LD (Logical Device) -LN (Logical Node) -Data Class-Data Attribute.

Here, the PD may be unique information indicating a physical device (hardware, an operating system, etc.) that accommodates at least one LD as an entity representing a physical part of a device. The LD may be an entity representing one typical substation function. LD may be unique information indicating an IED. The PD and LD may be arbitrarily set by the sensor node manufacturer and may be unique information in the power system. The LN may be an entity that represents a series of typical substation functions. Data Class is defined in IEC61850-7-4 (Basic Communication Structures of Substations and Feeders—Compatible Logic Slow Classes and Data Classes) and can be interpreted as monitoring items in the LN. Figure 2 illustrates the case of LN: Circuit Breaker, Data Class: POS specified in Section 5.12.1 of IEC 61850-7-4. The following example illustrates the case where the Data attribute is a state value. The data attribute may be information such as a state value or a measured value. Various object names of LN, Data Class and Data Attribute are defined in IEC 61850.

First Embodiment

Hereinafter, a sensor node according to an exemplary embodiment of the present invention will be described with reference to FIG. 3. 3 is a functional block diagram of a sensor node according to an exemplary embodiment of the present invention. The sensor node of FIG. 3 may be any one of the sensor nodes of FIG. 1.

Referring to FIG. 3, the sensor node 100 may include a conversion reference information providing unit 110, a data generating unit 120, and a data providing unit 130.

When the sensor node 100 is initially connected to the data node 200 (when the communication protocol between the sensor node 100 and the data node 200 is based on the Zigbee method), the conversion reference information providing unit 110 uses the data node ( When the sensor node 100 joins the PAN (Personal Area Network) generated by the 200), the data conversion criteria information identified by the sensor node attribute information ID, the conversion criteria information ID, and the conversion criteria information ID is simultaneously or The data node 200 may transmit the data. The sensor node attribute information ID may be information for identifying a physical device (PD) and at least one logical device (LD) -logical node (LN). When there are a plurality of LDs or LNs accommodated by the sensor node 100, in order to identify each LN, there may be a plurality of SN attribute information IDs. This is because when a plurality of LDs and LNs are accommodated, there are a plurality of instances of the LDs and LNs. The data conversion reference information may be reference information used to convert a data structure (not an IEC 61850 data structure) used when the sensor node 100 transmits data to the data node 200 to an IEC 61850 data structure. This data conversion criterion information may be a mapping table between a data class and a data attribute between the data structure and the IEC 61850 data structure used when the sensor node 100 transmits data to the data node 200. have. The data conversion reference information may include information for identifying the PD of the sensor node and at least one LD-LN accommodated by the PD. When the sensor node 100 creates a data class and a data attribute in accordance with the IEC 61850 standard and provides the data node to the data node, the provision of the conversion reference information ID may be omitted. In addition, only PD-LD-LN may be added to a data class and a data attribute according to sensor node attribute information during data conversion. The data structure of the sensor node 100 may be changed according to the needs of the designer of the sensor node 100. Therefore, when the data structure of the sensor node 100 is changed after the data node 200 registers the data conversion criterion information, the conversion criterion information providing unit 110 updates the conversion criterion including the changed conversion criterion information ID and the data conversion criterion information. The request message may be sent to the data node 200. In this case, the setting unit 220 (refer to FIG. 4) may update the existing data conversion reference information and the conversion reference information ID by using the conversion reference information ID and the data conversion reference information on the conversion reference update request message. In addition, at least one of LD and LN may be added according to the needs of the designer of the sensor node 100. In this case, the conversion criterion information providing unit 110 may transmit a conversion criterion addition request message including the added conversion criterion information ID and data conversion criterion information to the data node 200. In this case, the setting unit 220 (refer to FIG. 4) may additionally register the conversion criterion ID and data conversion criterion information on the conversion criterion addition request message on the data node 200.

The data generator 120 may generate monitoring data. The monitoring data may be at least one of measurement data, status data, and diagnostic data. Monitoring data may have a hierarchical structure such as Data Class-Data Attribute. However, Data Class-Data Attribute may not be prepared in the manner prescribed by IEC61850. In some cases, monitoring data may be created in a manner that Data Class-Data Attributes are specified in IEC61850. In this case, only the PD-LD-LN part may be added when converting to the IEC61850 data structure as described above.

The data provider 130 may provide the monitoring data generated by the data generator 120 to the data node 200. When the monitoring data is transmitted, the conversion reference information ID and the SN attribute information ID may be transmitted together. If the sensor node accepts only one LN, transmission of the SN attribute information ID may be omitted. Alternatively, when the SN attribute information ID is included in the data conversion reference information, transmission of the SN attribute information ID may be omitted. The conversion criteria information ID and the SN attribute information ID may be provided in the form of a hash value. Or, to increase reliability, both ID and hash values may be provided with the monitoring data. In this case, the hash value may serve as a parity bit.

Hereinafter, a data node according to another embodiment of the present invention will be described with reference to FIG. 4. 4 shows a functional block diagram of a data node according to one preferred embodiment of the present invention. The data node of FIG. 4 may be any one of the data nodes of FIG. 1.

Referring to FIG. 4, the data node 200 may include an authenticator 210, a setup unit 220, a data collector 230, a data converter 240, and a data provider 250.

When the authentication unit 210 receives the sensor node attribute information ID, the authentication unit 210 may transmit a sensor node attribute information request message to the database 400. In this case, the sensor node attribute information request message may include sensor node attribute information ID to be used for retrieving the sensor node attribute information. In this case, the database 400 may search the sensor node attribute information using the sensor node attribute information ID and provide the search result to the data node 200. In this case, the authenticator 210 may authenticate the sensor node using the search result. If any one of the LNs accommodated by the sensor node is not found, the authenticator 210 may treat the sensor node 100 as an unregistered sensor node. That is, if any one of the LNs identified by the sensor node attribute information accommodated by the sensor node is not retrieved from the database 400, the authenticator 210 determines the sensor node 100 as an unregistered sensor. You can treat it as a node and take appropriate action accordingly. For example, the authenticator 210 may transmit the sensor attribute information ID of the unregistered sensor node to the monitoring node 300. If all the LNs accommodated by the sensor node 100 exist in the database 400 and the authentication unit 210 authenticates that the sensor node 100 is the pre-registered sensor node 100, the authentication unit 210 is set. The unit 220 may inform this.

In response to the authenticator 210 determining that the sensor node 100 is a pre-registered sensor node, the setting unit 220 registers the data conversion reference information received from the sensor node 100 by matching the conversion reference information ID. Or can be stored. When there are a plurality of LNs accommodated by the PD, data conversion reference information may be stored for each LN. In this case, the data conversion reference information may include sensor node attribute information. The data conversion reference information may be stored in match with the sensor node attribute information ID.

In this case, the data collector 230 may collect monitoring data from at least one sensor node 100 and provide the collected monitoring data to the data converter 240.

The data converter 240 may convert the collected monitoring data into an IEC 61850 data structure. As seen above, the data structure provided to the IEC 61850 client has a hierarchical structure of PD-LD-LN-Data Class-Data Attribute. When the data conversion unit 240 receives data from a specific LN accommodated by the sensor node, the data conversion unit 240 may extract PD-LD-LN information from data conversion reference information matching the conversion reference information ID stored in the data node 200. have. In addition, the portion corresponding to the Data Class-Data Attribute in the monitoring data may be converted to conform to the IEC 61850 standard by using a mapping table on the data conversion reference information. The data converter 240 may create the extracted PD-LD-LN and the converted Data Class-Data Attribute in the form of PD-LD-LN-Data Class-Data Attribute. When data conversion criterion information is stored in accordance with the SN attribute information, data conversion criteria matching the SN attribute information ID may be used in data conversion.

The data provider 250 may provide the converted monitoring data to the monitoring node 300 when the conversion by the data converter 240 is completed.

Hereinafter, a CMD data converting method according to an exemplary embodiment of the present invention will be described with reference to FIGS. 3 to 5. 5 is a ladder chart illustrating a CMD data converting method according to an embodiment of the present invention. In FIG. 5, a database may be connected to a data node through a wired network, and a sensor node may be connected to a data node through a wireless network.

First, when the conversion reference information providing unit 110 initially connects to the data node 200 (when the communication protocol between the sensor node 100 and the data node 200 is based on the Zigbee method, the data node 200 generates the data node 200. When the sensor node 100 joins a personal area network (PAN), data conversion reference information matching the sensor node attribute information ID, the conversion reference information ID, and the conversion reference information ID is simultaneously or simultaneously transferred to the data node 200. Can be transmitted (S501). The sensor node attribute information ID, the conversion criterion information ID, and the data conversion criterion information are used when a request from the data node 200 occurs or when a preset event occurs (for example, when the sensor node 100 is assigned a PAN ID). ) May be provided to the data node 200. The request for the conversion reference information ID and the data conversion reference information may proceed when authentication of the sensor node using the sensor node attribute information ID described later is completed. The sensor node attribute information ID may be information for identifying a physical device (PD) and at least one logical device (LD) -logical node (LN). When there are a plurality of LDs or LNs accommodated by the sensor node 100, in order to identify each LN, there may be a plurality of sensor node attribute information IDs. This is because when a plurality of LDs and LNs are accommodated, there are a plurality of instances of the LDs and LNs. The conversion reference information ID may be reference information used to convert a data structure (not an IEC 61850 data structure) used when the sensor node 100 transmits data to the data node 200 to an IEC 61850 data structure. This data conversion criterion information may be a mapping table between a data class and a data attribute between the data structure and the IEC 61850 data structure used when the sensor node 100 transmits data to the data node 200. have. The data conversion reference information may include information for identifying the PD of the sensor node and at least one LD-LN accommodated by the PD. The data structure of the sensor node 100 may be changed according to the needs of the designer of the sensor node 100. Therefore, when the data structure of the sensor node 100 is changed after the data node 200 registers the data conversion criterion information, the sensor node 100 sends a conversion criterion update request message including the changed conversion criterion information ID and the data conversion criterion information. The data node 200 may transmit the data. In this case, the data node 200 may update the existing data conversion reference information and the conversion reference information ID by using the conversion reference information ID and the data conversion reference information on the conversion reference update request message. In addition, at least one of LD and LN may be added according to the needs of the designer of the sensor node 100. In this case, the conversion criterion information providing unit 110 may transmit a conversion criterion addition request message including the added conversion criterion information ID and data conversion criterion information identified by the conversion criterion information ID to the data node 200. In this case, the setting unit 220 may additionally register the conversion reference information ID and the data conversion reference information on the conversion reference addition request message to the data node 200.

When receiving the sensor node attribute information ID, the authenticator 2100 may transmit a sensor node attribute information request message to the database 400 (S502). In this case, the sensor node attribute information request message may include sensor node attribute information ID to be used for retrieving the sensor node attribute information.

When the database 400 receives the sensor node attribute information request message, the database 400 may retrieve the sensor node attribute information using the sensor node attribute information ID and provide the search result to the data node 200 (S503).

In this case, the authenticator 210 may authenticate the sensor node using the search result (S504). If any one of the LNs accommodated by the sensor node is not found, the sensor node 100 may be treated as an unregistered sensor node. That is, if any one of the LNs identified by the SN attribute information accommodated by the sensor node 100 is not retrieved from the database 400, the authentication unit 210 treats the sensor node as an unregistered terminal and appropriate action accordingly. Can be taken (S505). For example, the authenticator 210 may transmit the sensor attribute ID of the unregistered sensor node to the monitoring node 300.

If all the LNs accommodated by the sensor node 1000 exist in the database 400 in S504 and the sensor node 100 is recognized as a pre-registered sensor node, the setting unit 220 converts the data node 200. Data conversion reference information identified by the reference information ID and the conversion reference information ID can be registered (S506). When there are a plurality of LNs accommodated by the PD, data conversion reference information may be stored for each LN. In this case, the data conversion reference information may include sensor node attribute information. The data conversion reference information may be stored in match with the sensor node attribute information ID.

The data generator 110 may generate monitoring data and transmit the generated monitoring data to the data node 200 (S507). The monitoring data may be at least one of measurement data, status data, and diagnostic data. Monitoring data may have a hierarchical structure such as Data Class-Data Attribute. However, Data Class-Data Attribute may not be prepared in the manner prescribed by IEC61850. In some cases, monitoring data may be created in a manner that Data Class-Data Attributes are specified in IEC61850. When the monitoring data is transmitted, the conversion reference information ID and the sensor node attribute information ID may be transmitted together. If the sensor node accepts only one LN, the transmission of the sensor node attribute information ID may be omitted. Alternatively, when the sensor node attribute information ID is included in the conversion reference information, transmission of the sensor node attribute information ID may be omitted. The conversion criteria information ID and the sensor node attribute information ID may be provided in the form of a hash value. Or, to increase reliability, both ID and hash values may be provided with the monitoring data.

When the data collection unit 230 collects the monitoring data and provides the collected monitoring data to the data conversion unit 240, the data conversion unit 240 may convert the collected monitoring data into the IEC 61850 data structure (S508). ). As seen above, the data structure provided to the IEC 61850 client has a hierarchical structure of PD-LD-LN-Data Class-Data Attribute. When the data conversion unit 240 receives data from a specific LN accommodated by the sensor node, the data conversion unit 240 may extract PD-LD-LN information from data conversion reference information matching the conversion reference information ID stored in the data node 200. have. In addition, the portion corresponding to the Data Class-Data Attribute in the monitoring data may be converted to conform to the IEC 61850 standard by using a mapping table on the data conversion reference information. The data converter 240 may create the extracted PD-LD-LN and the converted Data Class-Data Attribute in the form of PD-LD-LN-Data Class-Data Attribute. When the data conversion criteria information is stored in accordance with the sensor node attribute information, the data conversion criteria matching the sensor node attribute information ID may be used in data conversion.

In this case, the data provider 250 may provide the converted monitoring data to the monitoring node 300 (S509).

As such, when the sensor node 100 is initially connected, the sensor node 100 provides the data conversion reference information identified by the conversion reference information ID and the conversion reference information ID to the data node 200, and when transmitting the monitoring data, Data corresponding to the PD-LD-LN may be replaced with an SN attribute information ID or a conversion criterion information ID. Therefore, the amount of data provided by the sensor node 100 may be minimized, and thus, power consumption of the sensor node 100 may be minimized.

Second Embodiment

Hereinafter, a sensor node according to another embodiment of the present invention will be described with reference to FIG. 6. 6 is a functional block diagram of a sensor node according to another embodiment of the present invention. The sensor node of FIG. 6 may be any one of the sensor nodes of FIG. 1.

Referring to FIG. 6, the sensor node 1000 may include an ID provider 1100, a data generator 1200, and a data provider 1300.

When the sensor node 1000 is initially connected to the data node 2000 (when the communication protocol between the sensor node 1000 and the data node 2000 is based on the Zigbee method), the ID provider 1100 may use the data node 2000. When the sensor node 1000 joins the created personal area network (PAN), the sensor node attribute information ID and the conversion reference information ID may be transmitted to the data node 2000 at the same time or at this time. The SN attribute information ID may be information for identifying a physical device (PD) and at least one logical device (LD) -logical node (LN). When there are a plurality of LDs or LNs accommodated by the sensor node 1000, in order to identify each LN, there may be a plurality of SN attribute information IDs. This is because when a plurality of LDs and LNs are accommodated, there are a plurality of instances of the LDs and LNs. The conversion reference information ID may be reference information used to convert a data structure (not an IEC 61850 data structure) used when the sensor node 1000 transmits data to the data node 2000 to an IEC 61850 data structure. The conversion reference information may be a mapping table between a data class and a data attribute between a data structure used when the sensor node 1000 transmits data to the data node 2000 and an IEC 61850 data structure. . The conversion reference information may include information for identifying the PD of the sensor node and at least one LD-LN accommodated by the PD. When the sensor node 1000 creates and provides a data class and a data attribute to the data node in accordance with the IEC 61850 standard, the provision of the conversion reference information ID may be omitted. In addition, only PD-LD-LN may be added to a data class and a data attribute according to sensor node attribute information during data conversion. The data structure of the sensor node 1000 may be changed according to the needs of the designer of the sensor node 1000. Therefore, when the data structure of the sensor node 1000 is changed after the data node 2000 registers the data conversion criterion information, the ID provider 1100 may transmit a conversion criterion update request message including the changed conversion criterion information ID to the data node 2000. ) Can be sent. In this case, the setting unit 2200 (refer to FIG. 7) obtains data conversion reference information from the database 4000 by using the conversion reference information ID on the conversion reference update request message, and converts the existing data using the obtained data conversion reference information. The standard information can be updated. In addition, according to the needs of the designer of the sensor node 1000, at least one of LD and LN may be added. In this case, the ID provider 1100 may transmit a data conversion criterion information addition request message including the added conversion criterion information ID to the data node 2000. At this time, the setting unit 2200 (refer to FIG. 7) obtains data conversion reference information from the database 4000 using the conversion reference information ID on the conversion criterion addition request message, and uses the obtained data conversion reference information to convert the data. You can add information.

The data generator 1200 may generate monitoring data. The monitoring data may be at least one of measurement data, status data, and diagnostic data. Monitoring data may have a hierarchical structure such as Data Class-Data Attribute. However, Data Class-Data Attribute may not be prepared in the manner prescribed by IEC61850. In some cases, monitoring data may be created in a manner that Data Class-Data Attributes are specified in IEC61850.

The data provider 1300 may provide the monitoring data generated by the data generator 1200 to the data node 2000. When the monitoring data is transmitted, the conversion reference information ID and the sensor node attribute information ID may be transmitted together. If the sensor node accepts only one LN, the transmission of the sensor node attribute information ID may be omitted. Alternatively, when the sensor node attribute information ID is included in the conversion reference information, transmission of the sensor node attribute information ID may be omitted. The conversion criteria information ID and the sensor node attribute information ID may be provided in the form of a hash value. Or, to increase reliability, both ID and hash values may be provided with the monitoring data.

Hereinafter, a data node according to another embodiment of the present invention will be described with reference to FIG. 7. The data node of FIG. 7 may be any one of the data nodes of FIG. 1. 7 is a functional block diagram of a data node according to another embodiment of the present invention.

Referring to FIG. 7, the data node 2000 may include an authentication unit 2100, a setting unit 2200, a data collection unit 2300, a data converter 2400, and a data provider 2500.

When the authentication unit 2100 receives the sensor node attribute information ID, the authenticator 2100 may transmit a sensor node attribute information request message to the database 4000. In this case, the sensor node attribute information request message may include sensor node attribute information ID to be used for retrieving the sensor node attribute information. In this case, the database 4000 may search for sensor node attribute information using the sensor node attribute information ID and provide the search result to the data node 2000. In this case, the authenticator 2100 may authenticate the sensor node using the search result. If any of the LNs accommodated by the sensor node is not found, the authenticator 2100 may treat the sensor node 1000 as an unregistered sensor node. That is, if any one of the LNs identified by the sensor node attribute information accommodated by the sensor node is not retrieved from the database 4000, the authentication unit 2100 determines that the sensor node 1000 is an unregistered terminal. And take appropriate action accordingly. For example, the authenticator 2100 may transmit a sensor attribute ID of an unregistered sensor node to the data node 3000. If all the LNs accommodated by the sensor node 1000 exist in the database 4000 and the authentication unit 2100 authenticates that the sensor node 1000 is a pre-registered sensor node 1000, the setting unit 2200 does this. You can inform.

In response to the authenticator 2100 determining that the sensor node 1000 is the pre-registered sensor node 1000, the setting unit 2200 may transmit a data conversion criterion information request message to the database 4000. The data conversion criterion information request message may include a conversion criterion information ID used for retrieving data conversion criterion information. In this case, the database 4000 may search for data conversion reference information about the sensor node 1000 registered using the conversion reference information ID and provide the retrieved data conversion reference information to the setting unit 2200. When the setting unit 2200 receives the data conversion reference information, the setting unit 2200 may register the data conversion reference information on the data node 2000. When there are a plurality of LNs accommodated by the PD, data conversion reference information may be stored for each LN. In this case, the data conversion reference information may include sensor node attribute information. The data conversion reference information may be stored in match with the sensor node attribute information ID.

In this case, the data collector 2300 may collect monitoring data from at least one sensor node 1000 and provide the collected monitoring data to the data converter 2400.

The data converter 2400 may convert the collected monitoring data into an IEC 61850 data structure. As seen above, the data structure provided to the IEC 61850 client has a hierarchical structure of PD-LD-LN-Data Class-Data Attribute. When the data conversion unit 2400 receives data from a specific LN accommodated by the sensor node, the data conversion unit 2400 may extract PD-LD-LN information from data conversion reference information matching the conversion reference information ID stored in the data node 2000. have. In addition, the portion corresponding to the Data Class-Data Attribute in the monitoring data may be converted to conform to the IEC 61850 standard by using a mapping table on the data conversion reference information. The data converter 2400 may create the extracted PD-LD-LN and the converted Data Class-Data Attribute in the form of PD-LD-LN-Data Class-Data Attribute. When the data conversion criteria information is stored in accordance with the sensor node attribute information, the data conversion criteria matching the sensor node attribute information ID may be used in data conversion.

The data provider 2500 may provide the converted monitoring data to the monitoring node 3000 when the conversion by the data converter 2400 is completed.

Hereinafter, a method of providing a universal sensor platform according to another exemplary embodiment of the present invention will be described with reference to FIGS. 6 to 8. 8 is a ladder chart illustrating a CMD data converting method according to another embodiment of the present invention. In FIG. 8, a database may be connected to a data node through a wired network, and a sensor node may be connected to a data node through a wireless network.

First, when the ID provider 1100 initially connects to the data node 2000 (when the communication protocol between the sensor node 1000 and the data node 2000 is based on the Zigbee method, the PAN (generated by the data node 2000) is generated. When the sensor node 1000 joins the Personal Area Network), the sensor node attribute information ID and the conversion reference information ID may be transmitted to the data node 2000 at the same time or at this time (S801). The sensor node attribute information ID and the conversion criterion information ID are used when the data node 2000 requests or when a preset event occurs (for example, when the sensor node 1000 is assigned a PAN ID). ) May be provided. The request may proceed when authentication of the sensor node using the sensor node attribute information ID described later is completed. The sensor node attribute information ID may be information for identifying a physical device (PD) and at least one logical device (LD) -logical node (LN). When there are a plurality of LDs or LNs accommodated by the sensor node 1000, a plurality of sensor node attribute information IDs may be used to identify each LN. This is because when a plurality of LDs and LNs are accommodated, there are a plurality of instances of the LDs and LNs. The conversion reference information ID may be reference information used to convert a data structure (not an IEC 61850 data structure) used when the sensor node 1000 transmits data to the data node 2000 to an IEC 61850 data structure. This data conversion criterion information may be a mapping table between a data class and a data attribute between the data structure used when the sensor node 1000 transmits data to the data node 2000 and the IEC 61850 data structure. have. The data conversion reference information may include information for identifying the PD of the sensor node and at least one LD-LN accommodated by the PD. The data structure of the sensor node 1000 may be changed according to the needs of the designer of the sensor node 1000. Therefore, when the data structure of the sensor node 1000 is changed after the data node 2000 registers the data conversion criterion information, the sensor node 1000 transmits a conversion criterion update request message including the changed conversion criterion ID to the data node 2000. Can transmit In this case, the data node 2000 may obtain data conversion criterion information from the database 4000 using the conversion criterion ID on the conversion criterion update request message, and update the existing data conversion criterion using the obtained data conversion criterion. . In addition, according to the needs of the designer of the sensor node 1000, at least one of LD and LN may be added. In this case, the ID provider 1100 may transmit a conversion criteria addition request message including the added conversion criteria ID to the data node 2000. At this time, the setting unit 2200 (refer to FIG. 7) obtains data conversion reference information from the database 4000 using the conversion reference information ID on the conversion criterion addition request message, and uses the obtained data conversion reference information to convert the data. You can add information.

When receiving the sensor node attribute information ID, the authenticator 2100 may transmit a sensor node attribute information request message to the database 4000 (S802). In this case, the sensor node attribute information request message may include an SN attribute information ID to be used for SN attribute information retrieval.

When the database 4000 receives the SN attribute information request message, the database 4000 may retrieve SN attribute information using the SN attribute information ID and provide the search result to the data node 2000 (S803).

In this case, the data node 2000 may authenticate the sensor node using the search result (S804). If any of the LNs accommodated by the sensor node is not found, the sensor node 1000 may be treated as an unregistered sensor node. That is, if any of the LNs identified by the sensor node attribute information received by the sensor node is not retrieved from the database 4000, the data node 2000 treats the sensor node as an unregistered terminal and takes appropriate action accordingly. It may be (S805). For example, the sensor attribute information ID of the unregistered sensor node may be transmitted to the data node 3000.

As a result of the search in S804, when all the LNs accommodated by the sensor node 1000 exist in the database and the sensor node is recognized as the pre-registered sensor node 1000, the setting unit 2200 converts the data into the database 4000. The information request message may be transmitted (S806). The data conversion criterion information request message may include a conversion criterion information ID used for retrieving data conversion criterion information.

The database 4000 may search for data conversion reference information about the sensor node 1000 registered using the conversion reference information ID and provide the retrieved data conversion reference information to the setting unit 2200 (S807).

When the setting unit 2200 receives the data conversion reference information, the setting unit 2200 may register the data conversion reference information on the data node 2000 (S808). When there are a plurality of LNs accommodated by the PD, data conversion reference information may be stored for each LN. In this case, the data conversion reference information may include sensor node attribute information. The data conversion reference information may be stored in match with the sensor node attribute information ID.

The data generator 1000 may generate monitoring data and transmit the generated monitoring data to the data node 2000 (S809). The monitoring data may be at least one of measurement data, status data, and diagnostic data. Monitoring data may have a hierarchical structure such as Data Class-Data Attribute. However, Data Class-Data Attribute may not be prepared in the manner prescribed by IEC61850. In some cases, monitoring data may be created in a manner that Data Class-Data Attributes are specified in IEC61850. When the monitoring data is transmitted, the conversion reference information ID and the sensor node attribute information ID may be transmitted together. If the sensor node accepts only one LN, the transmission of the sensor node attribute information ID may be omitted. Alternatively, when the sensor attribute information ID is included in the data conversion reference information, the transmission of the sensor node attribute information ID may be omitted. The conversion criteria information ID and the sensor node attribute information ID may be provided in the form of a hash value. Or, to increase reliability, both ID and hash values may be provided with the monitoring data.

In this case, when the data collection unit 2300 collects the monitoring data and provides the collected monitoring data to the data conversion unit 2400, the data conversion unit 2400 may convert the collected monitoring data into the IEC 61850 data structure. (S810). As seen above, the data structure provided to the IEC 61850 client has a hierarchical structure of PD-LD-LN-Data Class-Data Attribute. When the data converter 2400 receives data from a specific LN accommodated by the sensor node, the data converter 2400 may extract PD-LD-LN information from data conversion reference information matching the data conversion reference information ID stored in the data node 2000. Can be. In addition, the portion corresponding to the Data Class-Data Attribute in the monitoring data may be converted to conform to the IEC 61850 standard by using a mapping table on the data conversion reference information. The data converter 2400 may create the extracted PD-LD-LN and the converted Data Class-Data Attribute in the form of PD-LD-LN-Data Class-Data Attribute. When the data conversion criteria information is stored in accordance with the sensor node attribute information, the data conversion criteria matching the sensor node attribute information ID may be used in data conversion.

In this case, the data provider 2500 may provide the converted monitoring data to the monitoring node 3000 (S811).

As such, when the sensor node 1000 is initially connected, the sensor node 1000 provides only the conversion reference information ID to the data node 2000, and the data conversion reference information is obtained from the database 4000 through the wired network. The amount of data transmitted by the sensor node 1000 may be minimized at the time of connection, and the transmission speed and data reliability of the data conversion reference information may be further improved.

In addition, when transmitting the monitoring data, the sensor node 1000 may replace data corresponding to the PD-LD-LN with an SN attribute information ID or a conversion reference information ID. Therefore, the amount of data provided by the sensor node 1000 may be minimized, and thus, power consumption of the sensor node 1000 may be minimized.

[Description of the code]

100, 1000: sensor node

110, 1100: Conversion reference information providing unit

120, 1200: data generator

130, 1300: data provider

200, 2000: data nodes

210, 2100: Certification part

220, 2200: setting part

230, 2300: data collector

240, 2400: data conversion unit

250, 2500: data provider

3000: monitoring node

4000: database

Claims

In the CMD data converting method for a smart grid,

Receiving, by a data node, a transformation reference information ID and data transformation reference information identified by the transformation reference information ID from a sensor node;

Registering, by the data node, the data conversion criteria information on the data node by matching the conversion criteria information ID;

The data node receiving monitoring data, sensor node attribute information ID and data conversion reference information ID from the sensor node;

The data node provides PD-LD-LN information using the sensor node attribute information ID, and converts the monitoring data using data conversion reference information identified by the data conversion reference information ID. Obtaining an attribute; And

And transmitting the data having the IEC 61850 data structure having the PD-LD-LN-Data Class-Data Attribute hierarchy to the monitor node.
The method of claim 1,

The data node receiving the sensor node attribute information ID; And

And authenticating the sensor node using the sensor node attribute information ID.
The method of claim 1,

And upon receiving the monitoring data, the sensor node attribute information ID, and the data conversion criterion information ID, a hash value for the data conversion criterion information ID is further received.