JP2014146271A - Data relevant information management device, data communication system, data relevant information management method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable the determination of whether metadata of data can be deleted in a system that stores the metadata of the data and location information of the data and has a data retrieval mechanism.SOLUTION: A data relevant information management device includes a data relevant information storage part for storing data relevant information obtained by associating data identification information with metadata of data shown by the data identification information, a data relevant information management part for managing the data relevant information stored in the data relevant information storage part, and a subordinate data information storage part for storing subordinate data information obtained by associating node identification information showing a node of a communication network with data identification information of data subordinate to the node. The data relevant information management part determines whether the data identification information is included in the subordinate data information about the data identification information included in the data relevant information, and deletes the data identification information and the associated metadata from the data relevant information when determining that the data identification information is not included.

Description

  The present invention relates to a data related information management device, a data communication system, a data related information management method, and a program.

  Systems that link various sensors and actuators with data storage functions (storage), applications, etc., and communications for linkage to realize visualization of power, energy saving control, and improvement of daily life Protocols are becoming popular. When such a system becomes large-scale, the relationship between data and an access destination to the data becomes complicated. In particular, when an application or the like accesses data, the location of necessary data becomes difficult to understand.

Therefore, several techniques for making it possible to acquire necessary data have been proposed.
For example, in the IEEE 1888 protocol, the registry stores data metadata (point table) and data location information. Then, the component (gateway, storage, or application) selects necessary data by the point search referring to the metadata of the data, and grasps the location of the necessary data by the component search referring to the data location information.
By managing the data metadata and the data location information separately as in the IEEE 1888 protocol, for example, the same data such as the data of each time measured by the same sensor can be handled uniformly. In addition, by managing the data metadata and the data location information separately, duplication of data metadata when there are multiple identical data, such as when multiple storages store the same data Can be avoided, and an increase in storage capacity can be suppressed.
In the service status monitoring system of the Web service system described in Patent Document 1, the client obtains the address of the Web service to be used from UDDI and issues a request for the Web service at the address.

JP 2005-196449 A

In a system that stores data metadata and data location information and has a data retrieval mechanism, the storage capacity required for data metadata and data location information increases as the system becomes larger and the data reference relationship becomes more complex To do. For this reason, it is preferable to suppress an increase in storage capacity by deleting unnecessary information.
However, in IEEE 1888, data metadata (point table) is not deleted in principle. Since the metadata of the data is associated with the data rather than the data provider such as each sensor or storage, it is not easy to determine whether or not deletion is possible.
Patent Document 1 does not describe deletion of Web service search information stored in a UDDI registry.

  The present invention has been made in view of such circumstances, and its object is to determine whether or not data metadata can be deleted in a system that stores data metadata and data location information and has a data search mechanism. An object of the present invention is to provide a data-related information management apparatus, a data communication system, a data-related information management method, and a program that can be used.

  The present invention has been made to solve the above-described problem, and a data-related information management device according to an aspect of the present invention provides data in which data identification information is associated with metadata of data indicated by the data identification information. A data related information storage unit for storing related information, a data related information management unit for managing the data related information stored in the data related information storage unit, node identification information indicating a node of the communication network, and subordinates of the node A subordinate data information storage unit that stores subordinate data information associated with data identification information of the data, and the data related information management unit is configured to store the data regarding the data identification information included in the data related information. It is determined whether or not identification information is included in the subordinate data information. Remove metadata attached finely corresponding from the data-related information, characterized in that.

  A data-related information management device according to another aspect of the present invention is the above-described data-related information management device, comprising: a subordinate data information management unit that manages the subordinate data information; and a node of the communication network, A deletion request acquisition unit that acquires a deletion request for data identification information included in the subordinate data information, and the subordinate data information management unit includes data identification information whose deletion request request node is a deletion request target It is determined whether or not the user has the delete request authority. If the delete request authority is determined, the data identification information is deleted from the subordinate data information according to the delete request.

  A data related information management apparatus according to another aspect of the present invention is the data related information management apparatus described above, wherein the data related information storage unit has a right to request deletion of the data identification information and the data identification information. Node identification information indicating a node having the information is stored in association with the data related information.

  A data communication system according to another aspect of the present invention is a data communication system comprising a node of a communication network and a data related information management device, wherein the data related information management device includes data identification information and the data related information A data related information storage unit that stores data related information associated with metadata of data indicated by the data identification information; a data related information management unit that manages the data related information stored in the data related information storage unit; A subordinate data information storage unit for storing subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node, and the data related information management The data identification information included in the data related information, the data identification information is the subordinate data information Including whether determined by deletes the data identification information and metadata are correlated if it is determined that not contained from the data-related information, characterized in that.

  A data related information management method according to another aspect of the present invention includes a data related information storage unit that stores data related information in which data identification information is associated with metadata of data indicated by the data identification information, A data-related information management apparatus comprising: a subordinate data information storage unit that stores subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node; In the information management method, for data identification information included in the data related information, it is determined whether or not the data identification information is included in the subordinate data information. And a data-related information management step for deleting the associated metadata from the data-related information. The features.

  A program according to another aspect of the present invention includes a data related information storage unit that stores data related information in which data identification information and metadata of data indicated by the data identification information are associated, and a node of the communication network A subordinate data information storage unit that stores subordinate data information in which node identification information indicating data and data identification information of data under the node are associated with each other. For the data identification information included in the related information, it is determined whether the data identification information is included in the subordinate data information. If it is determined that the data identification information is not included, the data identification information and the associated metadata are A program for executing a data related information management step to be deleted from the data related information .

  According to the present invention, it is possible to determine whether or not data metadata can be deleted in a system that stores data metadata and data location information and has a data search mechanism.

It is a schematic block diagram which shows the structure of the data communication system in one Embodiment of this invention. It is a schematic block diagram which shows the function structure of the registry apparatus in the embodiment. It is explanatory drawing which shows the example of the component table which a component information storage part memorize | stores in the same embodiment. It is explanatory drawing which shows the example of the point table | surface which a point information storage part memorize | stores in the same embodiment. It is explanatory drawing which shows the example of determination of the presence or absence of the deletion authority which a component information management part performs in the same embodiment. It is a sequence diagram which shows the example of the process which a data communication system performs in the embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. In the following description, a case where the present invention is applied to a data communication system configured based on the IEEE 1888 protocol and the registry function is extended will be described as an example. However, the scope of the present invention is not limited to this. The present invention can be applied to various systems that store data metadata and data location information and have a data retrieval mechanism.

FIG. 1 is a schematic block diagram showing a configuration of a data communication system according to an embodiment of the present invention. In FIG. 1, a data communication system 1 includes a registry device 10, a gateway (GW) device 21, a storage device 22, an application (APP) 23, a sensor device 31, Actuator equipment 32, measurement data 33, and machining data 34 are provided.
In addition, the registry device 10, the gateway device 21, the storage device 22, and the application 23 communicate via the communication network 90. The sensor device 31 and the actuator device 32 are connected to the gateway device 21. In addition, the measurement data 33 and the processing data 34 are data stored in the storage device 22.

  The communication network 90 mediates communication between the registry device 10, the gateway device 21, the storage device 22, and the application 23. Various communication networks can be used as the communication network 90. For example, the communication network 90 may be the Internet, a LAN (Local Area Network), or a network dedicated to the data communication system 1.

The gateway device 21 is a device that provides a gateway function through a connection between the communication network 90 and the sensor device 31, the actuator device 32, or another communication network. The gateway function here is a function for eliminating a difference in communication protocols. Specifically, the gateway device 21 converts the measurement data of the sensor device 31 into data that can be used in the communication network 90. Further, the gateway device 21 converts an operation command for the actuator device 32 into data executable by the actuator device 32. Further, the gateway device 21 performs protocol conversion between the communication protocol of the communication network 90 and the communication protocol of another network.
The gateway device 21 is configured by a server device, for example.

  The storage device 22 provides a storage function. The storage function here is a function for storing (accumulating) various data such as measurement data of the sensor device 31 and data obtained by processing the measurement data (processing data). The storage device 22 is configured using a storage device such as a network storage (NAS) device.

  The application 23 provides an application function. The application function here is a function obtained when the computer executes the application program. In particular, the application 23 provides an application function involving data communication such as visualization (visual display) of measurement data of the sensor device 31.

  The sensor device 31 performs measurement and outputs measurement data. Here, various devices that perform measurement can be used as the sensor device 31. For example, the sensor device 31 may be a digital sensor or an analog sensor such as a temperature sensor or a power sensor, or may be an ON / OFF sensor such as a human sensor.

  The actuator device 32 operates in response to an operation command. Here, various devices to be controlled can be used as the actuator device 32. For example, the actuator device 32 may be a device that performs an ON / OFF operation such as a power switch, or may be a device that is numerically controlled such as a temperature adjustment function in an air conditioning device.

  The measurement data 33 is measurement data of the sensor device 31 stored in the storage device 22. The processed data 34 is processed data (data obtained by processing the measurement data of the sensor device 31) stored in the storage device 22. The measurement data 33 and the processing data 34 correspond to examples of data stored in the storage device 22. However, the data stored in the storage device 22 is not limited to this. For example, the storage device 22 may store data obtained by user input or processed data of the data.

Hereinafter, the gateway function, the storage function, and the application function are collectively referred to as “component” or “component 20”. In the notation of “component”, the gateway function and the gateway device, and the storage function and the storage device are regarded as the same. Accordingly, the gateway device and the storage device are also referred to as components. The component corresponds to a node of the communication network 90.
The number of components included in the data communication system 1 is not limited to six shown in FIG. 1 and may be one or more.

  In the following, the measurement data of the sensor device, the data as a command to the actuator device, and the data stored in the storage device are collectively referred to as “point” or “point 30”. In the notation of “point”, the measurement data of the sensor device and the sensor device, and the command to the actuator device and the actuator device are identified. Therefore, sensor devices and actuator devices are also referred to as points.

In addition, in the notation of “point”, data obtained from the same source is identified. For example, a series of time-series data obtained from one sensor device such as measurement data of the sensor device 31 and past measurement data of the sensor device 31 stored in the storage device 22 is regarded as the same point.
The number of points included in the data communication system 1 is not limited to seven shown in FIG. 1 and may be an arbitrary number.

The registry device 10 provides a registry function. The registry function here is a function that stores information about components and points as components of the data communication system 1 and provides the information to the components. The registry device 10 is configured by a server device, for example.
The registry device 10 corresponds to an example of a data related information management device.

  FIG. 2 is a schematic block diagram illustrating a functional configuration of the registry device 10. In FIG. 1, the registry device 10 includes a communication unit 110, a storage unit 120, and a control unit 130. The storage unit 120 includes a point information storage unit 121 and a component information storage unit 122. The control unit 130 includes a point information management unit 131 and a component information management unit 132.

The storage unit 120 is configured by a storage device included in the registry device 10 and stores various data.
The component information storage unit 122 stores a component table including a subordinate point table in which identification information of a component that is a node of the communication network 90 and identification information of a subordinate point of the component are associated with each other. The component information storage unit 122 corresponds to an example of a subordinate data information storage unit, and the subordinate point table corresponds to an example of subordinate data information.

  Here, the data being under the node means that the node outputs (provides) the data, or the node accepts the data as control command data. Therefore, the point being under the component means that the component outputs the point as data, or the component receives the point as data of a control command.

  FIG. 3 is an explanatory diagram illustrating an example of a component table stored in the component information storage unit 122. The component table shown in the figure has a component table body T11 and a subordinate point table T12. The component table body T11 has a “component name” column, a “URI” column, an “update component” column, and a “link” column. One row of the component table main body T11 corresponds to one component.

The “component name” column stores the component name assigned to each component. The component name corresponds to an example of component identification information (thus, an example of node identification information of a communication network).
The “URI” column stores the URI (Uniform Resource Identifier) of the component. The component URI corresponds to an example of a component address in the communication network 90.

  The “update component” column indicates a component having update authority for the row of the component table (the row of the component table body and the associated subordinate point table). When the component indicated by the component name and the component having the update authority always match, that is, when only the component indicated by the component name has the update authority for the corresponding row, the “update component” field can be omitted.

  The component table is updated by, for example, a component having update authority requesting the component information management unit 132 to update by indicating the update position and the update content. Such an update request is made, for example, when the component calls a REGISTERATION method.

The “link” column is a column indicating a link from the row of the component table body to the subordinate point table. The link only needs to be traced from the row of the component table main body to at most one subordinate point table, and various expression methods can be used. For example, a component name may be assigned to the subordinate point table, and the correspondence between the row of the component table main body and the subordinate point table may be indicated by matching the component name. In this case, it is not necessary to provide a “link” column in the component table main body.
The component table body T11 further stores information related to the component such as component attribute information. When a component is identified by URI, the “component” field need not be provided.

The subordinate point table T12 indicates information regarding points under the component. The subordinate point table T12 has a “KEY” column.
The “KEY” column stores identification information (point names in the example of FIG. 3) of points under the component. In the example of FIG. 3, there are a point a and a point b under the gateway 1. Further, there are a point a and a point c under the storage 1.

If a component does not have subordinate points or if no subordinate points are registered, a subordinate point table corresponding to the component is not provided.
The subordinate point table may further store information regarding subordinate points such as attribute information of subordinate points.
Note that the component information storage unit 122 stores not only the table format such as the component table but also various formats for storing the component information.

The point information storage unit 121 stores a point table in which data identification information on points is associated with metadata of data indicated by the data identification information. Further, the point information storage unit 121 stores the data identification information at the point and the node identification information indicating the node having the authority to request deletion of the data identification information in association with each other in the point table.
The point information storage unit 121 corresponds to an example of a data related information storage unit, and the point table corresponds to an example of data related information.

FIG. 4 is an explanatory diagram illustrating an example of a point table stored in the point information storage unit 121. The point table shown in the figure has a “point name” column, an “update component” column, a “location” column, and a “type” column. One row of the point table corresponds to one point.
The “point name” column stores a point name that is a name assigned to each point. The point name corresponds to an example of data identification information (that is, point identification information) at the point.

The “update component” column stores identification information (component name in the example of FIG. 4) of the component having the authority to delete points in the subordinate point table of the component table.
Here, the subordinate point table has the update authority shown in the corresponding row in the component table body in principle, but in addition, the update component shown in the point table also has the delete authority. . In the case of the example in FIG. 3, the information on the point a in the subordinate point table of the storage 1 is the storage 1 itself that is the update component of the storage 1 and the update component of the point a in the point table of FIG. 4. Gateway 1 has a deletion authority.

The “location” column stores a location associated with the point, such as an installation location of the sensor device or actuator device. In the example of FIG. 4, a place associated with a point is indicated by a room number.
The “type” column indicates the type of data at the point. “Power” in the example of FIG. 4 indicates measurement data from the power sensor, or indicates that target power is set when an operation is commanded to the actuator device. “Temperature” indicates measurement data from a temperature sensor, or indicates that a target temperature is set when an operation is commanded to the actuator device.
Note that the point information storage unit 121 stores not only the table format such as the point table but also various formats as the format for storing the point information.

  The communication unit 110 communicates by connecting to the communication network 90. In particular, the communication unit 110 acquires (receives) a deletion request for a row corresponding to a certain point included in a subordinate point table of the component table from a component that is a node of the communication network 90. The communication unit 110 corresponds to an example of a deletion request acquisition unit.

The control unit 130 controls each unit of the registry device 10 and executes various functions. For example, the control unit 130 is configured by a CPU (Central Processing Unit) included in the registry device 10 reading out a program from the storage unit 120 and executing the program.
The point information management unit 131 manages the point table stored in the point information storage unit 121. The point information management unit 131 corresponds to an example of a data related information management unit. In particular, the point information management unit 131 determines whether or not the identification information of the points included in the point table is included in the subordinate data table of the component table. The identification information and associated metadata are deleted from the point table.

The component information management unit 132 manages the component table. The component information management unit 132 corresponds to an example of a subordinate data information management unit. In particular, the component information management unit 132 determines whether or not the request source component of the deletion request for the row of the subordinate point table received by the communication unit 110 has the deletion request authority for the deletion request target row, and delete request authority If it is determined that the corresponding row is included, the corresponding row is deleted from the point table according to the deletion request.
Specifically, the component information management unit 132 notifies the point information management unit 131 of the point name of the line for which deletion is requested by the deletion request, and acquires the update component (information indicating the corresponding point). . Then, the component information management unit 132 compares the component that is the transmission source of the deletion request with the update component, and determines that there is a deletion authority if the transmission source component is included in or matches the update component. If it is determined that there is a deletion authority, the component information management unit 132 deletes the row of the subordinate data table according to the deletion request.

FIG. 5 is an explanatory diagram illustrating an example of determination of presence / absence of deletion authority performed by the component information management unit 132. This figure shows an example when the component B requests deletion of the row L11 of the subordinate point table.
In this case, referring to the row L12 corresponding to the subordinate point table to be deleted in the component table, the update component is the component A, which is different from the component B as the deletion request source. On the other hand, referring to the row L13 of the component B corresponding to the deletion target row L11 in the point table, the deletion component is the component B, which matches the component B of the deletion request source. Therefore, the component information management unit 132 deletes the row L11 of the subordinate point table.

Next, the operation of the data communication system 1 will be described with reference to FIG.
FIG. 6 is a sequence diagram illustrating an example of processing performed by the data communication system 1. In the figure, first, the component B registers the information of the point x in the point table by the REGISTRATION procedure of the point (sequence S111).
Here, the REGISTRATION procedure for points is a procedure for registering point information in the point table. On the other hand, the deletion of the point information registered in the point table is not a request from the component, but is determined by the registry itself.

  Component B registers its own information in the component table in the component REGISTERATION procedure (sequence S112). Here, the REGISTRATION procedure for a component is a procedure for registering, changing or deleting component information in the component table.

Next, the component A requests the registry to search for point information having a certain attribute in the point LOOKUP procedure (sequence S121). Here, the point LOOKUP procedure is a procedure for searching the point table.
On the other hand, the registry replies with the information of the point having the designated attribute (sequence S122). In the example of FIG. 6, the registry replies with information including point x information.

In addition, the component A requests the registry to search for information on components that satisfy certain conditions in the component LOOKUP procedure (sequence S131). Here, the component LOOKUP procedure is a procedure for searching the component table.
In response to this, the registry replies with information on components that satisfy the specified condition (sequence S132). In the example of FIG. 6, the registry responds with information including component B information.

Component A requests data from component B in the FETCH procedure (sequence S141). Here, the FETCH procedure is a procedure for acquiring data in which a certain component exists in another component.
In response to this, the component B returns the requested data to the component A (sequence S142).
Further, the component A registers the information of the component A itself in the component table in the component REGISTERATION procedure (sequence S151).

In addition, when component B wants to delete point x information from the registry (component table and point table), it first searches the registry for information on the component that manages the point x information in the component LOOKUP procedure. Requesting (sequence S161). Here, the component that manages the point information is a component that registers the point in the subordinate point table of the component table.
On the other hand, the registry replies with information of all components managing the information of point x as a search result (sequence S162). In the example of FIG. 6, the registry responds with information including component B information.

Next, the component B deletes the information of the point x from the subordinate point table of the component table for all the components included in the answer of the sequence S162 in the component REGISTERATION procedure (sequence S163).
Further, the registry detects that the point name of the point x is not included in any of the subordinate point tables of the component table, and deletes the information of the point x from the point table (sequence S164).

Various methods can be used as a method for deleting information from the component table and the point table. For example, the column or line to be deleted may be eliminated, or a blank or blank line may be left while leaving the column or line itself.
Note that the timing at which the registry deletes point information from the point table can be various. For example, as in the example of FIG. 6, when the registry determines whether or not the point appears in another subordinate point table at the timing when the point information is deleted from the subordinate point table, and determines that it does not appear In addition, the point information may be deleted from the point table. Alternatively, the registry may periodically detect a point that does not appear in the subordinate point table in the background job, and delete the information of the point from the point table.

  As described above, the point information storage unit 121 stores a point table (data information), and the component information storage unit 122 stores a component table (node information). And the point information management part 131 determines whether the said identification information is contained in the component table | surface about the identification information of the point contained in a point table. If it is determined that the point information is not included, the point information management unit 131 deletes the point information from the point table.

In this way, the point information management unit 131 refers to the subordinate point table to detect whether or not the point is under the component, thereby determining whether or not the point information (data metadata) in the point table can be deleted. Can be determined.
After the point information management unit 131 confirms that the point does not appear in the subordinate point table, the point information is deleted from the point table, so that the subordinate point table has the point information. The state without point information can be avoided. That is, the registry device 10 uses the storage information wastefully because the information of the component table is not used because the attribute information of the point is not included in the point table even though the component table indicates the location information of the point. Can be avoided.

  Further, when the communication unit 110 receives a request to delete point information in the subordinate point table, the component information management unit 132 determines whether or not the request source component has a deletion request authority. If it is determined that the user has the deletion request authority, the component information management unit 132 deletes the point information from the subordinate point table in accordance with the deletion request.

  In this manner, the component 20 can delete information on points under the control of other components by determining whether or not the component information management unit 132 has the deletion request authority. A component with delete request authority deletes the information of points under the control of other components, thereby avoiding the above-mentioned situation where there is point information in the subordinate point table but no point information in the point table. However, the point information can be deleted from the point table.

Further, the point information storage unit 121 stores the identification information of the points and the identification information of the update component indicating the component having the authority to request deletion of the identification information in association with each other in the point table.
As a result, the point information management unit 131 can confirm whether or not the deletion request source component has deletion authority by a simple process of referring to the point table.

It should be noted that a program for realizing all or part of the functions of the registry device 10 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. You may perform the process of. Here, the “computer system” includes an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like without departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 Data communication system 10 Registry apparatus 21 Gateway apparatus 22 Storage apparatus 23 Application 31 Sensor apparatus 32 Actuator apparatus 33 Measurement data 34 Processing data 90 Communication network 110 Communication part 120 Storage part 121 Point information storage part 122 Component information storage part 130 Control part 131 Point information management unit 132 Component information management unit

Claims (6)

A data related information storage unit for storing data related information in which data identification information and metadata of data indicated by the data identification information are associated;
A data related information management unit for managing the data related information stored in the data related information storage unit;
A subordinate data information storage unit for storing subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node;
Comprising
The data-related information management unit determines whether or not the data identification information is included in the subordinate data information for the data identification information included in the data-related information. A data-related information management apparatus, wherein information and associated metadata are deleted from the data-related information. A subordinate data information management unit for managing the subordinate data information;
A deletion request acquisition unit for acquiring a deletion request for data identification information included in the subordinate data information from a node of the communication network;
Comprising
The subordinate data information management unit determines whether or not the request source node of the deletion request has a deletion request authority for data identification information to be deleted, and determines that the deletion request authority has a deletion request authority. The data related information management apparatus according to claim 1, wherein the data identification information is deleted from the subordinate data information.   The data related information storage unit stores the data identification information and node identification information indicating a node having authority to request deletion of the data identification information in association with the data related information. The data related information management apparatus according to claim 1 or 2. A data communication system comprising a communication network node and a data-related information management device,
The data related information management device
A data related information storage unit for storing data related information in which data identification information and metadata of data indicated by the data identification information are associated;
A data related information management unit for managing the data related information stored in the data related information storage unit;
A subordinate data information storage unit that stores subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node;
Comprising
The data-related information management unit determines whether or not the data identification information is included in the subordinate data information for the data identification information included in the data-related information. A data communication system, wherein information and associated metadata are deleted from the data related information. A data related information storage unit for storing data related information in which data identification information and metadata of data indicated by the data identification information are associated;
A subordinate data information storage unit for storing subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node;
A data-related information management method for a data-related information management apparatus comprising:
For the data identification information included in the data related information, it is determined whether or not the data identification information is included in the subordinate data information. If it is determined that the data identification information is not included, the data identification information and the associated meta data are determined. A data-related information management method comprising a data-related information management step of deleting data from the data-related information. A data related information storage unit for storing data related information in which data identification information and metadata of data indicated by the data identification information are associated;
A subordinate data information storage unit for storing subordinate data information in which node identification information indicating a node of the communication network is associated with data identification information of data under the node;
In a computer as a data related information management device comprising
For the data identification information included in the data related information, it is determined whether or not the data identification information is included in the subordinate data information. If it is determined that the data identification information is not included, the data identification information and the associated meta data are determined. A program for executing a data related information management step of deleting data from the data related information.

Images