JP2013152557A - Metadata attachment apparatus, metadata attachment method and metadata attachment program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a load of processing for attaching metadata to sensor data.SOLUTION: A data collection section 101 acquires a sensor ID and a sensor value from a sensor information DB 102. The data collection section 101 inquires cache memory 104 whether a cache associated with the acquired sensor ID exists or not. As a result, the data collection section 101 acquires facility configuration information related to the sensor ID from the cache memory 104 and stores the acquired facility configuration information in a pre-analysis information storage DB 106 when the cache exists. The data collection section 101 acquires the facility configuration information related to the sensor ID from a facility configuration information DB 103 when the cache does not exist. Then, the data collection section 101 stores the acquired facility configuration information in the cache memory 104, creates a cache, and stores the facility configuration information related to the sensor ID in the pre-analysis information storage DB 106.

Description

  The present invention relates to a metadata grant apparatus, a metadata grant method, and a metadata grant program.

  2. Description of the Related Art Conventionally, a technique is known in which metadata that is attribute information is added to time-series data (for example, sensor data detected by a sensor) and stored. Here, time-series data such as sensor data is characterized by a small amount of data and a large number of data. In addition, sensor data is characterized in that data in various formats is often searched across and atypical processing is often performed.

  For this reason, when sensor data is stored in an RDB (Relational Data Base) of a schema-full RDBMS (Relational Data Base Management System) that has been widely used in the past, a large number of data must be stored as individual rows. It becomes. When searching in the RDB using a search expression, the number of lines to be matched and the number of matching lines become enormous, and the load for collating each data in the RDBMS and the line arrangement for answering the results are shown. The load to store temporarily was large.

  As described above, when the sensor data is stored in the RDB, the amount of each data is small, so that the number of lines to be collated and the number of matching lines are enormous, which increases the burden. In addition, in order to process a large amount of data, scale-out for load distribution is required. However, when clustering is performed in RDBMS, the table is locked frequently and the availability of data is reduced, so the scale-out reaches its peak. There was a case.

  For these reasons, sensor data is stored in a schemaless DBMS (Data Base Management System), metadata as attribute information is stored in a schema-full DBMS, and tuning by combining a plurality of DBMSs or between different DBMSs. Technology to exchange data efficiently has become important.

  As such a technique, for example, a technique is known in which sensor data that approximate each other is stored together in a chunk data file to reduce the processing load of search processing (for example, Patent Document 1).

JP 2011-170791 A

  However, in the technology of storing the above sensor data in a schemaless DBMS (Data Base Management System) and storing the metadata as attribute information in the schemaful DBMS, there is a processing load for adding metadata to the sensor data. There was a problem of being big. In other words, in order to give metadata to sensor data, it is necessary to acquire sensor data from a schemaless DBMS and to acquire attribute information from a schemaful DBMS. The number of rows and the number of matching rows is enormous. For this reason, as a result of a large load for collating each data in the RDBMS and a large load for temporarily storing a row of rows for answering results, a load of processing for adding metadata to sensor data increases.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and an object thereof is to reduce the processing load for adding metadata to sensor data.

  In order to solve the above-described problems and achieve the object, the metadata providing apparatus disclosed in the present application stores a sensor identifier for uniquely identifying a sensor and a sensor value that the sensor detects every predetermined time in time series. A sensor information storage unit, an equipment configuration information storage unit that stores attribute information about the equipment in which the sensor is installed, and a sensor identifier and a sensor value obtained from the sensor information storage unit, and attribute information corresponding to the sensor identifier A cache determination unit that determines whether or not the attribute information corresponding to the sensor identifier is stored in the cache memory. The attribute information related to the sensor of the identifier is extracted from the facility configuration information storage unit, and the extracted attribute information and the sensor identification Are stored in the cache memory in association with each other, and the extracted attribute information is associated with the sensor value as metadata and stored in the pre-analysis information storage unit, and the sensor identifier is stored in the sensor identifier by the cache determination unit. If it is determined that the corresponding attribute information is stored in the cache memory, the attribute information corresponding to the sensor identifier is acquired from the cache memory, and the attribute information is associated with the sensor value as metadata. And a metadata adding unit for storing in the pre-analysis information storage unit.

  Further, the metadata providing method disclosed in the present application includes a sensor identifier and a sensor value from a sensor information storage unit that stores a sensor identifier that uniquely identifies a sensor and a sensor value that the sensor detects every predetermined time in time series. And determining whether or not attribute information corresponding to the sensor identifier is stored in the cache memory, and attribute information corresponding to the sensor identifier is stored in the cache memory by the cache determination step. If it is determined that the attribute information related to the sensor of the sensor identifier is extracted from the equipment configuration information storage unit that stores the attribute information related to the equipment in which the sensor is installed, the extracted attribute information and the A sensor identifier is associated and stored in the cache memory, and the extracted attribute information is stored in the meta data. A cache storage step of storing data in a pre-analysis information storage unit in association with a sensor value as data, and when the cache determination step determines that attribute information corresponding to the sensor identifier is stored in the cache memory Includes a metadata adding step of acquiring attribute information corresponding to the sensor identifier from the cache memory and storing the attribute information as metadata in association with a sensor value in the pre-analysis information storage unit. And

  The metadata providing program disclosed in the present application acquires a sensor identifier and a sensor value from a sensor information storage unit that stores a sensor identifier that uniquely identifies the sensor and a sensor value that the sensor detects every predetermined time in time series. And determining whether or not attribute information corresponding to the sensor identifier is stored in the cache memory, and attribute information corresponding to the sensor identifier is not stored in the cache memory by the cache determining step. If it is determined, the attribute information related to the sensor of the sensor identifier is extracted from the facility configuration information storage unit that stores the attribute information related to the facility where the sensor is installed, and the extracted attribute information and the sensor identifier Are associated and stored in the cache memory, and the extracted attribute information is stored in the cache memory. Storing in the pre-analysis information storage unit in association with the sensor value as metadata, and when determining that the attribute information corresponding to the sensor identifier is stored in the cache memory by the cache determination step In the computer, the attribute information corresponding to the sensor identifier is acquired from the cache memory, and the attribute information is associated with a sensor value as metadata and stored in the pre-analysis information storage unit. Let

  The metadata providing apparatus, the metadata providing method, and the metadata providing program disclosed in the present application have an effect of reducing the processing load for adding metadata to sensor data.

FIG. 1 is a block diagram illustrating the configuration of the metadata providing apparatus according to the first embodiment. FIG. 2 is a diagram illustrating an example of data stored in the sensor information DB. FIG. 3 is a diagram illustrating an example of data stored in the facility configuration information DB. FIG. 4 is a diagram illustrating an example of data stored in the cache memory. FIG. 5 is a diagram illustrating an example of data stored in the pre-analysis information storage DB. FIG. 6 is a diagram illustrating an example of data stored in the analysis result information storage DB. FIG. 7 is a flowchart illustrating the flow of the metadata providing process performed by the metadata providing apparatus according to the first embodiment. FIG. 8 is a flowchart illustrating the flow of analysis and aggregation processing performed by the metadata providing apparatus according to the first embodiment. FIG. 9 is a flowchart illustrating the flow of the information presentation process performed by the metadata providing apparatus according to the first embodiment. FIG. 10 is a flowchart illustrating the flow of the metadata providing process performed by the metadata providing apparatus according to the first embodiment. FIG. 11 is a diagram illustrating a computer that executes a metadata providing program.

  Exemplary embodiments of a metadata providing apparatus, a metadata providing method, and a metadata providing program according to the present invention will be described below in detail with reference to the accompanying drawings. Note that the present invention is not limited to the embodiments.

  In the following embodiments, the configuration and processing flow of the metadata providing apparatus according to the first embodiment will be described in order, and finally the effects of the first embodiment will be described.

[Configuration of metadata adding device]
Initially, the structure of the metadata provision apparatus 100 is demonstrated using FIG. The metadata providing apparatus 100 includes a data collection unit 101, a sensor information DB (Data Base) 102, an equipment configuration information DB 103, a cache memory 104, a data totaling unit 105, a pre-analysis information storage DB 106, an information presentation unit 107, and an analysis result information storage. A DB 108 and a cache removing unit 109 are included. The processing of each of these units will be described below.

  The data collection unit 101 acquires a sensor ID and a sensor value (hereinafter, a combination of the sensor ID and the sensor value is referred to as sensor data) from the sensor information DB 102 (described in detail later with reference to FIG. 2). Attribute information (hereinafter referred to as “equipment configuration information” as appropriate) about the equipment in which the sensor is installed is acquired from the cache memory 104 (detailed using FIG. 3) or the cache memory 104 (detailed later using FIG. 4). By storing the data in the pre-analysis information storage DB 106 (detailed later using FIG. 5) in association with the sensor value as data, metadata is given to the sensor data. The data collection unit 101 includes a cache determination unit 101a, a cache storage unit 101b, a metadata addition unit 101c, and a data update unit 101d. The processing of each of these units will be described below.

  The cache determination unit 101a acquires the sensor ID and sensor value from the sensor information DB 102, and determines whether or not attribute information corresponding to the sensor ID is stored in the cache memory 104.

  Specifically, the cache determination unit 101a acquires a sensor ID, a sensor value, and a measurement time from the sensor information DB 102 when a predetermined time interval elapses. Then, the cache determination unit 101a inquires whether the cache associated with the sensor ID acquired in the cache memory 104 exists in the cache memory 104, and determines whether or not the cache exists. Note that the determination process is not limited to the case where the predetermined time interval has elapsed, and the determination process may be performed using the detection of the sensor value by the sensor as a trigger.

  When the cache determination unit 101a determines that the attribute information corresponding to the sensor ID is not stored in the cache memory 104, the cache storage unit 101b obtains attribute information related to the sensor with the sensor ID from the facility configuration information DB 103. The extracted attribute information and the sensor ID are associated with each other and stored in the cache memory 104, and the extracted attribute information is associated with the sensor value as metadata and stored in the pre-analysis information storage DB 106.

  Specifically, the cache storage unit 101b throws a query using SQL (Structured Query Language) when the cache determination unit 101a determines that the cache of attribute information corresponding to the sensor ID does not exist in the cache memory 104. As the equipment configuration information related to the sensor ID from the equipment configuration information DB 103, sensors such as the rack ID of the rack in which the sensor is installed, the area ID indicating the area of the server in which the sensor is installed, and the sensor type indicating the type of sensor Get attribute information related to. Then, the cache storage unit 101b stores the acquired facility configuration information in the cache memory 104. Thereafter, the cache storage unit 101b stores the equipment configuration information in the pre-analysis information storage DB 106 as metadata in association with the sensor ID.

  When the cache determination unit 101a determines that the attribute information corresponding to the sensor ID is stored in the cache memory 104, the metadata adding unit 101c acquires the attribute information corresponding to the sensor ID from the cache memory 104. The attribute information is stored in the pre-analysis information storage DB 106 as metadata in association with the sensor value.

  For example, when the cache determination unit 101a determines that the attribute information cache corresponding to the sensor ID exists in the cache memory 104, the metadata adding unit 101c uses the cache memory 104 as the equipment configuration information related to the sensor ID. The rack ID, area ID, sensor type, and the like are acquired, and the acquired equipment configuration information is stored as metadata in the pre-analysis information storage DB 106 in association with the sensor ID, sensor value, and measurement time.

  As described above, the metadata adding unit 101c generates a new cache when the cache of the equipment configuration information that is the metadata does not exist in the cache memory 104, and caches the next time the same query is called. Since the equipment configuration information associated with the sensor ID is acquired from the memory 104, it is possible to reduce the processing load for adding metadata to the sensor data.

  The data update unit 101d acquires the updated attribute information from the facility configuration information DB 103, and stores the updated attribute information in the cache memory 104. For example, when the data stored in the facility configuration information DB 103 is updated, the data update unit 101d updates the data updated from the facility configuration information DB 103 after the cache removal unit 109 described later clears the cache in the cache memory 104. The acquired data is stored in the cache memory 104.

  The sensor information DB 102 stores, in time series, a sensor ID that uniquely identifies the sensor and a sensor value that the sensor detects every predetermined time. Specifically, the sensor information DB 102 is a DBMS (Data Base Management System) such as KVS (Key-Value Store) which is a schemaless DB, and stores the sensor ID and the sensor value in time series. . For example, as illustrated in FIG. 2, the sensor information DB 102 includes a “sensor ID” that uniquely identifies a sensor, a “sensor value” that is a value detected by the sensor, and a “measurement time” that is a time measured by the sensor. Is stored in association with each other. 2, the sensor information DB 102 stores the sensor ID “1”, the sensor value “394”, and the measurement time “12:12:12” in association with each other. This means that the sensor with the sensor ID “1” has detected the sensor value “394” at the measurement time “12:12:12”. Here, the sensor value is, for example, the power consumption of a device such as a server, the power consumption of an air conditioner, temperature, and the like.

  The facility configuration information DB 103 stores attribute information related to the facility where the sensor is installed. Specifically, the facility configuration information DB 103 is a schema-full RDBMS (Relational Data Base Management System) and stores attribute information. For example, as illustrated in FIG. 3, the facility configuration information DB 103 includes a “rack ID” that uniquely identifies the rack that houses the server, an “area ID” that identifies the area where the server is installed, "Server model" indicating the model of the server, "Host name" indicating the host name, "Physical address" indicating the physical address of the server, "Virtual address" indicating the virtual address of the server, and the person managing the server "Administrator" indicating, "Installation location" indicating the location where the server is installed, "Sensor ID" uniquely identifying the sensor installed on the server, and "Sensor type" indicating the type of sensor Are stored in association with each other.

  The cache memory 104 stores facility configuration information that is metadata attached to sensor data. Specifically, as illustrated in FIG. 4, the cache memory 104 stores a sensor ID, a rack ID, an area ID, and a sensor type in association with each other. Here, the cache memory 104 is an on-memory DB to which, for example, Memcached is applied.

  The data totaling unit 105 acquires the sensor value and metadata stored in the pre-analysis information storage DB 106, uses the metadata to total the sensor value according to a predetermined condition, and the totaled result is the analysis result information storage DB 108. To store. Specifically, the data totaling unit 105 acquires metadata related to sensor data from the pre-analysis information storage DB 106. And the data totaling part 105 analyzes the acquired metadata, and totals sensor data according to predetermined conditions. Thereafter, the data totaling unit 105 stores the totaled results in the analysis result information storage DB 108.

  For example, the data totaling unit 105 totals the sensor data for each service provided by the server using the service ID as a key. Then, the data totaling unit 105 stores, in the analysis result information storage DB 108, information in a format in which metadata is added to the sensor data totaled in service units. The data totaling unit 105 totals sensor data for each building in which the server is installed, using the building ID as a key. Then, the data totaling unit 105 stores, in the analysis result information storage DB 108, information in a format in which metadata is added to the sensor data totaled for each building. Similarly, the data totaling unit 105 totals sensor data in units of floors where servers are installed, totals sensor data in units of racks in which servers are stored, and sensor data in units of servers (units of devices). Are stored in the analysis result information storage DB 108 in a format in which metadata is added to the totaled sensor data.

  The pre-analysis information storage DB 106 stores metadata corresponding to the sensor ID. Specifically, as illustrated in FIG. 5, the pre-analysis information storage DB 106 includes a “table name” indicating a table name, a “rowkey” indicating a rowkey specified at the time of search, and a column family name “ “column families” is stored in association with each other. In the example of FIG. 5, the measurement time “time” of the sensor and the sensor ID “sensorid” are stored as rowkeys, the rack ID “info: rackid”, the area ID “info: areaid”, and the sensor value “data” as column families. : Sensor value ”and sensor type“ option: sensor type ”.

  The information presentation unit 107 acquires data from the analysis result information storage DB 108 by specifying an ID (service ID, building ID, area ID, rack ID, or device ID), a data type, and a set of measurement periods as keys. The acquired data is displayed to the user. For example, the information presenting unit 107 designates the area ID “1”, the data type “2” (one day unit), and the measurement period “January 1 to December 31, 2012” as keys from the user. Then, data is acquired from the analysis result information storage DB 108 and the acquired data is displayed to the user.

  The analysis result information storage DB 108 stores a set of sensor values and metadata aggregated for each predetermined condition as an analysis result. Specifically, as shown in FIG. 6, the analysis result information storage DB 108 stores “table name” indicating the name of the table, “rowkey” indicating rowkey specified at the time of search, and “column” which is the column family name. "family" is stored in association with each other.

  For example, the analysis result information storage DB 108 stores the results totaled for each service, each building, each area, each rack, and each device in units of 15 minutes, 1 day, 1 month, and 1 year. Referring to the example of FIG. 6, the analysis result information storage DB 108 stores “service_view”, “building_view”, “area_view”, “rack_view”, and “facility_view” as table names. “Service_view” is an information reference table in service units, and stores “serviceid” that is a service ID, “type” that is the type of measurement time, and “time” that is the measurement time of the sensor as rowkeys. Here, when “type” is “1”, it indicates that the data is in units of 10 minutes, and when “type” is “2”, it indicates that the data is in units of one day, and “type” "3" indicates that the data is in units of one month, and "type" indicates that the data is in units of one year.

  When the attribute information stored in the facility configuration information DB 103 is updated, the cache removal unit 109 removes the attribute information in the cache memory 104 corresponding to the updated attribute information. Specifically, when the data stored in the facility configuration information DB 103 is updated, the cache removal unit 109 searches the cache memory 104 for a cache corresponding to the updated data, and clears the searched cache.

[Processing by metadata adding device]
Next, processing performed by the metadata providing apparatus 100 according to the first embodiment will be described with reference to FIGS. FIG. 7 is a flowchart illustrating the flow of the metadata providing process performed by the metadata providing apparatus according to the first embodiment. FIG. 8 is a flowchart illustrating the flow of analysis and aggregation processing performed by the metadata providing apparatus according to the first embodiment. FIG. 9 is a flowchart illustrating the flow of the information presentation process performed by the metadata providing apparatus according to the first embodiment. FIG. 10 is a flowchart illustrating the flow of the metadata providing process performed by the metadata providing apparatus according to the first embodiment.

  As illustrated in FIG. 7, when a predetermined time interval elapses, the data collection unit 101 acquires a sensor ID and a sensor value from the sensor information DB 102 (step S101). Then, the data collection unit 101 inquires whether there is a cache associated with the acquired sensor ID in the cache memory 104 (step S102). As a result, if the cache exists (Yes at Step S103), the data collection unit 101 acquires the equipment configuration information related to the sensor ID from the cache memory 104 (Step S107), and analyzes the acquired equipment configuration information before analysis. It stores in result information storage DB106 (step S106).

  If there is no cache (No at Step S103), the data collection unit 101 acquires equipment configuration information related to the sensor ID from the equipment configuration information DB 103 (Step S104). Then, the data collection unit 101 stores the acquired equipment configuration information in the cache memory 104, and creates a cache (step S105). Thereafter, the data collection unit 101 stores the equipment configuration information related to the sensor ID in the pre-analysis information storage DB 106 (step S106).

  Next, with reference to FIG. 8, the analysis and aggregation process performed by the metadata providing apparatus 100 according to the first embodiment will be described. As shown in FIG. 8, when a predetermined time interval elapses, the data totaling unit 105 of the metadata providing apparatus 100 acquires metadata related to sensor data from the pre-analysis information storage DB 106 (step S201). Then, the data totaling unit 105 analyzes the acquired data and totals sensor data and metadata according to a predetermined condition (step S202). Thereafter, the totaled results are stored in the analysis result information storage DB 108 (step S203).

  For example, the data totaling unit 105 includes a service unit provided by the server, a building unit in which the server is installed, a floor unit in which the server is installed, a rack unit in which the server is stored, or a server unit (device unit). Then, the sensor data is totaled, and the totaled result is stored in the analysis result information storage DB 108.

  Next, the information presentation process by the metadata providing apparatus 100 according to the first embodiment will be described with reference to FIG. As shown in FIG. 9, the information presenting unit 107 sets a set of ID (service ID, building ID, area ID, rack ID, or device ID), data type, and measurement period as a search key from the user. If accepted, the received key is designated and data is acquired from the analysis result information storage DB 108 (step S301). And the information presentation part 107 displays the data acquired from analysis result information storage DB108 to a user (step S302).

  For example, the information presenting unit 107 designates the area ID “1”, the data type “2” (one day unit), and the measurement period “January 1 to December 31, 2012” as keys from the user. Then, data is acquired from the analysis result information storage DB 108 and the acquired data is displayed to the user.

  Next, with reference to FIG. 10, analysis and aggregation processing by the metadata providing apparatus 100 according to the first embodiment will be described. As shown in FIG. 10, when the data stored in the facility configuration information DB 103 is updated (Yes in step S401), the cache removing unit 109 of the metadata providing apparatus 100 updates the cache memory 104 corresponding to the updated data. The cache is cleared (step S402).

  Then, the data collection unit 101 acquires updated data from the facility configuration information DB 103 (step S403). Thereafter, the data collection unit 101 stores the acquired data in the cache memory 104 (step S404).

[Effect of Example 1]
As described above, the metadata providing apparatus 100 includes a sensor ID that uniquely identifies a sensor, a sensor information DB 102 that stores a sensor value that the sensor detects every predetermined time, and a sensor. And an equipment configuration information DB 103 that stores attribute information related to the installed equipment. Then, the metadata providing apparatus 100 acquires a sensor ID and a sensor value from the sensor information DB 102 and determines whether or not attribute information corresponding to the sensor ID is stored in the cache memory 104. When it is determined that the attribute information corresponding to the sensor ID is not stored in the cache memory 104, the metadata providing apparatus 100 extracts the attribute information related to the sensor with the sensor ID from the facility configuration information DB 103. The extracted attribute information and the sensor ID are stored in the cache memory 104 in association with each other, and the extracted attribute information is stored as metadata in the pre-analysis information storage DB 106 in association with the sensor value. If it is determined that the attribute information corresponding to the sensor ID is stored in the cache memory 104, the metadata providing apparatus 100 acquires the attribute information corresponding to the sensor ID, and uses the attribute information as metadata. And stored in the pre-analysis information storage DB 106 in association with the sensor value. For this reason, if the cache of the equipment configuration information that is metadata does not exist in the cache memory 104, a new cache is generated, and the equipment configuration information associated with the sensor ID is called when the same query is called next time. Since it can be acquired from the cache memory 104, it is possible to reduce the load for collating each data in the equipment configuration information DB 103, which is an RDBMS, and the load for temporarily storing the row of rows for answering results. It is possible to reduce the processing load to be given.

  Further, according to the first embodiment, the sensor value and metadata stored in the pre-analysis information storage DB 106 are acquired, the sensor value is aggregated according to a predetermined condition using the metadata, and the aggregated result is an analysis result. Store in the information storage DB 108. For this reason, sensor data can be analyzed and aggregated using the given metadata.

  According to the first embodiment, when the attribute information stored in the facility configuration information DB 103 is updated, the attribute information in the cache memory 104 corresponding to the updated attribute information is deleted, and the facility configuration information DB 103 is deleted. The updated attribute information is acquired from the cache memory 104 and the updated attribute information is stored in the cache memory 104. For this reason, when the attribute information stored in the equipment configuration information DB 103 is updated, the attribute information stored in the cache memory 104 can also be automatically updated to the latest information.

[System configuration]
In addition, among the processes described in the above embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, specific names, and information including various data and parameters shown in the document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.

[program]
It is also possible to create a program in which the processing executed by the metadata providing apparatus 100 described in the above embodiment is described in a language that can be executed by a computer. For example, it is possible to create a metadata providing program in which processing executed by the metadata providing apparatus 100 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the metadata providing program, the same effect as in the above embodiment can be obtained. Further, the same processing as in the first embodiment is realized by recording the metadata providing program on a computer-readable recording medium, and reading and executing the metadata providing program recorded on the recording medium. May be. Hereinafter, an example of a computer that executes a metadata providing program that realizes the same function as the metadata providing apparatus 100 illustrated in FIG. 1 will be described.

  FIG. 11 is a diagram illustrating a computer 1000 that executes a metadata providing program. As illustrated in FIG. 11, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive. The serial port interface 1050 is connected to a mouse 1051 and a keyboard 1052, for example, as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 11, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the above-described metadata providing program is stored in, for example, the hard disk drive 1031 as a program module in which a command to be executed by the computer 1000 is described.

  The various data described in the above embodiment is stored as program data, for example, in the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1031 to the RAM 1012 as necessary, and executes a cache determination procedure, a cache storage procedure, and a metadata assignment procedure.

  Note that the program module 1093 and the program data 1094 related to the metadata providing program are not limited to being stored in the hard disk drive 1031, but are stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. May be. Alternatively, the program module 1093 and the program data 1094 related to the metadata providing program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and the network interface 1070 is stored. It may be read by the CPU 1020 via

DESCRIPTION OF SYMBOLS 100 Metadata provision apparatus 101 Data collection part 102 Sensor information DB
103 Equipment configuration information DB
104 Cache memory 105 Data totaling unit 106 Pre-analysis information storage DB
107 Information Presentation Unit 108 Analysis Result Information Storage DB
109 Cache Remover 1000 Computer 1010 Memory 1020 CPU
1030 Hard disk drive interface 1040 Disk drive interface 1050 Serial port interface 1060 Video adapter 1070 Network interface 1080 Bus 1031 Hard disk drive 1041 Disk drive 1051 Mouse 1052 Keyboard 1061 Display

Claims (5)

A sensor identifier that uniquely identifies the sensor, a sensor information storage unit that stores in time series a sensor value that the sensor detects every predetermined time;
A facility configuration information storage unit that stores attribute information related to the facility in which the sensor is installed;
A cache determination unit that acquires a sensor identifier and a sensor value from the sensor information storage unit, and determines whether or not attribute information corresponding to the sensor identifier is stored in a cache memory;
If the cache determination unit determines that the attribute information corresponding to the sensor identifier is not stored in the cache memory, the attribute information related to the sensor of the sensor identifier is extracted from the facility configuration information storage unit. A cache storage unit that stores the extracted attribute information in association with the sensor identifier in the cache memory, and stores the extracted attribute information in the pre-analysis information storage unit in association with the sensor value as metadata;
When the cache determination unit determines that attribute information corresponding to the sensor identifier is stored in the cache memory, the attribute information corresponding to the sensor identifier is acquired from the cache memory, and the attribute information is A metadata providing unit that stores the metadata in association with a sensor value in the pre-analysis information storage unit.   Data tabulation that acquires sensor values and metadata stored in the pre-analysis information storage unit, tabulates sensor values according to predetermined conditions using the metadata, and stores the tabulated results in the analysis result information storage unit The metadata providing apparatus according to claim 1, further comprising a section. When the attribute information stored in the facility configuration information storage unit is updated, a cache removal unit that removes the attribute information in the cache memory corresponding to the updated attribute information;
The metadata according to claim 1, further comprising: a data updating unit that acquires updated attribute information from the facility configuration information storage unit and stores the updated attribute information in the cache memory. Granting device. Attribute information corresponding to the sensor identifier obtained by acquiring the sensor identifier and the sensor value from a sensor information storage unit that stores the sensor identifier that uniquely identifies the sensor and the sensor value that the sensor detects every predetermined time in time series Cache determination step for determining whether or not is stored in the cache memory;
If it is determined by the cache determination step that attribute information corresponding to the sensor identifier is not stored in the cache memory, attribute information related to the sensor of the sensor identifier is related to the facility where the sensor is installed. The attribute information is extracted from the equipment configuration information storage unit, the extracted attribute information and the sensor identifier are associated with each other and stored in the cache memory, and the extracted attribute information is associated with the sensor value as metadata. A cache storage step of storing in the pre-analysis information storage unit;
If it is determined in the cache determination step that attribute information corresponding to the sensor identifier is stored in the cache memory, attribute information corresponding to the sensor identifier is acquired from the cache memory, and the attribute information is A metadata providing step of storing in the pre-analysis information storage unit in association with a sensor value as metadata. Attribute information corresponding to the sensor identifier obtained by acquiring the sensor identifier and the sensor value from a sensor information storage unit that stores the sensor identifier that uniquely identifies the sensor and the sensor value that the sensor detects every predetermined time in time series A cache determination step for determining whether or not is stored in the cache memory;
If it is determined in the cache determination step that attribute information corresponding to the sensor identifier is not stored in the cache memory, attribute information related to the sensor of the sensor identifier is related to the facility in which the sensor is installed. The attribute information is extracted from the equipment configuration information storage unit, the extracted attribute information and the sensor identifier are associated with each other and stored in the cache memory, and the extracted attribute information is associated with the sensor value as metadata. A cache storage step for storing in the pre-analysis information storage unit;
If it is determined in the cache determination step that attribute information corresponding to the sensor identifier is stored in the cache memory, attribute information corresponding to the sensor identifier is acquired from the cache memory, and the attribute information is A metadata providing program for causing a computer to execute a metadata providing step of storing in the pre-analysis information storage unit in association with a sensor value as metadata.

Images