Data distribution management system and data distribution management method

Abstract

To provide a distribution management system and a distribution management method that can easily share data even between data systems that are distributed in the event of a large-scale disaster or the like.SOLUTION: In a distribution management system, a data distribution management device 1 includes a recording unit that links content data shared between a first recording medium and a second recording medium with metadata related to attributes of the content data and records the linked data on the first recording medium, and a communication device 11 having two or more communication networks 5 that communicate one or more of the content data or metadata recorded by the stage of the recording unit between the first recording medium and the second recording medium. Thus, by appropriately handling two or more communication lines, data can be easily shared even between data systems that are distributed in the event of a large-scale disaster or the like.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a distributed data management system and a distributed data management method. [Background technology]

[0002] In recent years, the Basic Disaster Prevention Plan has stipulated the use of SIP4D (Shared Information Platform for Disaster Management), a fundamental disaster prevention data distribution network that was constructed for the purpose of aggregating, managing, and organizing various disaster-related data held by multiple organizations, such as disaster response organizations, government-related organizations, and public organizations such as local governments, in a unified disaster response headquarters, and sharing the data across the various organizations. In addition, other conventional technologies for sharing this data are, for example, as disclosed in the following Patent Documents 1 to 4. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2023-72063 A [Patent Document 2] JP 2023-69701 A [Patent Document 3] JP 2004-133529 A [Patent Document 4] International Publication No. 2014 / 155654 Summary of the Invention [Problem to be solved by the invention]

[0004] However, this SIP4D is a cloud-based system, and there is a problem that it cannot be used when the public communication network is cut off due to a large-scale disaster, etc. Furthermore, there is a problem that digital data such as photos, videos, and text data cannot be shared, integrated, and visualized between disaster response organizations in disaster-stricken areas where the public communication network is cut off.

[0005] Furthermore, Patent Document 1 describes a method of placing data between microservices using container technology. The technology described in Patent Document 1 is a technology for moving data used by a microservice based on performance data of the machine on which each microservice is executed when it is executed. However, the technology described in Patent Document 1 is a technology for moving microservices and data to appropriate hardware resources so as to satisfy the service quality based on a given policy, and does not consider situations such as division or isolation that may occur during a disaster. For this reason, the technology described in Patent Document 1 has a problem in that data may not be shared during a disaster.

[0006] Furthermore, Patent Document 2 describes a technology for caching remote files and objects locally before executing an application when an application tries to access remote files and objects in distributed storage. However, the technology described in Patent Document 2 is a system that assumes that storages are always connected via a network, and does not assume an environment that may occur during a disaster, in which the network may be interrupted or it is not known in advance who will be connected and when. For this reason, the technology described in Patent Document 2 has a problem in that data may not be shared during a disaster.

[0007] Also, Patent Document 3 describes a technology for backing up data in a small-scale data processing system without the need for expensive hardware and software, and without requiring users to have specialized knowledge, and for ensuring data preservation. However, the technology described in Patent Document 3 is a centralized data backup method. Therefore, the technology described in Patent Document 3 has a problem in that it cannot be applied to technology for sharing data in a distributed environment.

[0008] Also, Patent Document 4 describes a technology related to an information processing device that provides applications via a network as a distributed cloud. In Patent Document 4, when replacing this information processing device with a new one, the storage of the information processing device that is in use at a remote location is copied to the new information processing device on the network in advance. After this, when disconnecting from the network and transporting the new information processing device, file update management of the information processing device in use is started. As a result, when the new information processing device to be replaced arrives at the remote location, the information processing device described in Patent Document 4 copies only the primary of the files that have been updated to the new information processing device, and the secondary of the new information processing device can be generated autonomously. However, the technology described in Patent Document 4 is a technology for replacing a device of a distributed cloud with a new one, and does not assume data sharing in an environment where multiple distributed information processing devices constantly generate differential data offline. For this reason, the technology described in Patent Document 4 has a problem that data may not be shared in the event of a disaster.

[0009] The present invention has been devised in consideration of the above-mentioned problems, and its object is to provide a data distribution management system and a data distribution management method that enable easy sharing of data between distributed data systems even during a large-scale disaster, etc. [Means for solving the problem]

[0010] The data distribution management system according to the first invention is characterized in that it comprises a recording means for linking content data shared between a first recording medium and a second recording medium with metadata relating to attributes of the content data and recording the linked content data on the first recording medium, and a communication means having two or more communication lines for communicating one or more of the content data or the metadata recorded by the recording means between the first recording medium and the second recording medium.

[0011] The data distribution management system of the second invention is characterized in that, in the first invention, the recording means records the metadata including priority data indicating a priority for sharing the content data, and the communication means communicates one or more of the content data or the metadata based on the priority data included in the metadata recorded by the recording means.

[0012] The data distribution management system of the third invention is characterized in that, in the first invention, the communication means acquires communication data indicating the communication status of each of the communication lines, and selects the communication line for communicating one or more of the content data or the metadata based on each of the acquired communication data.

[0013] The data distribution management system of the fourth invention is characterized in that, in the first invention, the communication means acquires difference data relating to a difference between the data recorded on the first recording medium and the data recorded on the second recording medium, and communicates one or more of the content data or the metadata based on the acquired difference data.

[0014] The data distribution management system of the fifth invention is characterized in that, in the first invention, the recording means records the metadata including priority data indicating a priority for sharing the content data on the second recording medium, and the communication means communicates one or more of the content data or the metadata based on the priority data included in the metadata recorded by the recording means.

[0015] The data distribution management method of the sixth invention is characterized in that it has a computer execute a recording step of linking content data shared between a first recording medium and a second recording medium with metadata related to attributes of the content data and recording the content data on the first recording medium, and a communication step of communicating, between the first recording medium and the second recording medium, using two or more communication lines, either the content data or the metadata recorded by the recording step. Effect of the Invention

[0016] According to the first to sixth inventions, the data distribution management system and data distribution management method have two or more communication lines for communicating one or more of content data or metadata between the first recording medium and the second recording medium. By appropriately handling the two or more communication lines, data can be easily shared between distributed data systems even in the event of a large-scale disaster.

[0017] In particular, according to the second aspect of the present invention, the communication means communicates at least one of the content data and the metadata based on the priority data. This makes it possible to communicate data in order of priority, so that appropriate data can be easily shared among distributed data systems even in the event of a large-scale disaster.

[0018] In particular, according to the third aspect of the present invention, the communication means selects a communication line for communicating at least one of the content data and the metadata based on each communication data, which makes it possible to communicate using a more appropriate communication line even between distributed data systems during a large-scale disaster or the like.

[0019] In particular, according to the fourth aspect of the present invention, the communication means communicates one or more of the content data and the metadata based on the differential data. This makes it possible to appropriately select the data to be communicated, and makes it easier to share data between distributed data systems even in the event of a large-scale disaster.

[0020] In particular, according to the fifth aspect of the present invention, the communication means communicates at least one of the content data and the metadata based on the priority data recorded on the second recording medium. This allows the data distribution management device on the data receiving side to set the priority data, so that appropriate data can be easily shared between distributed data systems even in the event of a large-scale disaster. [Brief description of the drawings]

[0021] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a distributed data management system to which an embodiment of the present invention is applied. [Diagram 2] FIG. 2 is a diagram showing the configuration of a data distribution management device to which the embodiment of the present invention is applied. [Diagram 3] FIG. 3 is a diagram showing a flowchart of a data distribution management system to which the embodiment of the present invention is applied. [Figure 4] FIG. 4 is a diagram showing a state of metadata communication between data distribution management devices to which the embodiment of the present invention is applied. [Diagram 5] FIG. 5 is a diagram showing a state of communication of content data between data distribution management devices to which the embodiment of the present invention is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] A distributed data management system to which an embodiment of the present invention is applied will be described in detail below.

[0023] Fig. 1 shows the overall configuration of a distributed data management system 100 to which an embodiment of the present invention is applied. The distributed data management system 100 performs communication between distributed systems, for example, during a large-scale disaster. In the distributed data management system 100, for example, as shown in Fig. 1, a plurality of distributed data management devices 1, a server 3, and a terminal 6 are connected via a communication network 5. The distributed data management system 100 may also include a distributed data management device 1 provided in a mobile object 2 such as an emergency vehicle or a building 4 such as a hospital.

[0024] The data distribution management device 1 includes two or more communication devices 11, a sensor 12, a processing unit 13, a display unit 14, and a recording unit 15, each of which is connected to an internal bus (not shown). The communication devices 11 communicate with, for example, other data distribution management devices 1, terminals 6, and servers 3. The communication devices 11 communicate using different communication lines included in the communication network 5. In this case, for example, the communication device 11A may use a public communication line, the communication device 11B may use a high-speed communication line for short-distance communication, and the communication device 11C may use a low-speed communication line capable of long-distance communication.

[0025] The sensor 12 is a sensor for acquiring various data. For example, the sensor 12 may be a GPS (Global Positioning System) for acquiring location data related to the location of the data distribution management device 1. The sensor 12 may also be a sensor for acquiring time data related to the time when data is acquired and updated. The sensor 12 may also be a camera for capturing images and videos. The sensor 12 may also be a recorder for recording audio. The sensor 12 outputs the acquired data to the processing unit 13 and the recording unit 15.

[0026] The processing unit 13 processes various data output from the communication device 11 and the sensor 12. The processing unit 13 may be, for example, a CPU (Central Processing Unit) for processing data.

[0027] The display unit 14 is a monitor that displays various data. The display unit 14 may display, for example, communication data indicating a communication state. The display unit 14 may also be, for example, a speaker that outputs sound. The display unit 14 presents, in a simple form, for example, the progress of the synchronization and sharing of content data, whether synchronization of all content data has been completed, whether synchronization processing is still in progress, whether synchronization of high-priority content data has been completed, and the like.

[0028] The recording unit 15 is a recording medium such as a memory for recording various data. For example, the recording unit 15 records the content data shared between the data distribution management devices 1 in association with metadata related to the attributes of the content data. The recording unit 15 may include, for example, a content file for recording the content data, a catalog database for recording various data such as metadata, and the like.

[0029] The communication network 5 is a communication network consisting of various communication lines, including, for example, public communication lines such as satellite lines and mobile phone lines, short-distance but high-speed communication lines such as wireless LAN (local area network) and Ethernet (registered trademark), and low-speed communication lines capable of long-distance communication such as LPWA (Low Power Wide Area).

[0030] The server 3 is a server that records various data shared via the communication network 5. The server 3 may have some or all of the functions of the data distribution management device 1, for example.

[0031] The terminal 6 is, for example, a terminal for using the data distribution management system 100. The terminal 6 may be any smartphone, personal computer, etc. The terminal 6 may have, for example, a part or all of the functions of the data distribution management device 1.

[0032] Next, a description will be given of the operation of the distributed data management system 100 to which the embodiment of the present invention is applied. Fig. 3 is a diagram showing a flowchart of the operation of the distributed data management system 100 to which the embodiment of the present invention is applied.

[0033] First, in step S1, the data distribution management device 1 acquires content data. The content data is data shared between each data distribution management device 1. The content data is data shared between the recording units 15 of the data distribution management device 1A and the data distribution management device 1B as shown in FIG. 4, for example. The content data may be, for example, image and video data captured during a disaster. The content data may be, for example, data relating to a person or place in need of rescue. Furthermore, the content data is not limited to this, and may be any data shared between each data distribution management device 1.

[0034] In step S1, the data distribution management device 1 may acquire content data shared via, for example, the communication network 5. Also, in step S1, the data distribution management device 1 may acquire data acquired by, for example, the sensor 12 as the content data.

[0035] Next, in step S2, the recording unit 15 records the content data acquired in step S1 in association with metadata related to the attributes of the content data. The metadata is data related to the attributes of the content data, and includes, for example, priority data indicating the priority of sharing the content data, real-time data indicating the freshness of the content data, and data such as the capacity, size, and format of the content data. The metadata may also include time data related to the time when the content data was acquired or shared. The metadata may also include history data related to the history of modifying or sharing the content data. The recording unit 15 may record the metadata originally associated with the content data acquired in step S1. The recording unit 15 may record the content data acquired in step S1 in association with metadata input from an external application such as the terminal 6 by a user using the data distribution management system 100 via an API (Application Programming Interface). In step S2, the data distribution management device 1 may also assign to the content data path data to the content entity, time data indicating the time when the content data was acquired or updated, and data such as a unique ID such as a universally unique identifier (UUID) assigned to each piece of content data. In addition, for updates and deletions to existing content data and metadata, data may be newly recorded as an addition of a new record of an operation on the content data, and the update history may be recorded in chronological order.

[0036] In addition, in step S2, the processing unit 13 may acquire metadata from the content data acquired in step S1. In this case, the processing unit 13 may acquire priority data according to the capacity of the content data, for example. In this case, when a plurality of content data are acquired in step S1, the processing unit 13 may acquire priority data so as to increase the priority in proportion to the size of the capacity of each content data. Furthermore, the processing unit 13 may acquire priority data for each content data based on, for example, a correspondence table indicating the relationship between the capacity and priority of the content data acquired in advance. Furthermore, the processing unit 13 may acquire priority data input by a user. Furthermore, this priority data may be data indicating the priority of downloading data assigned to each data distribution management device 1. Furthermore, an expiration date may be set for the priority data.

[0037] The above-mentioned steps S1 and S2 make it possible to link and record content data and metadata in the data distribution management device 1. Next, a description will be given of an operation for sharing the content data and metadata linked and recorded in step S2 with another data distribution management device 1. This sharing operation is performed, for example, when a mobile object 2 carrying a data distribution management device 1 approaches another data distribution management device 1 and becomes capable of communication.

[0038] In step S3, the data distribution management device 1 acquires communication data indicating the communication state of each communication line. The communication data is data indicating the communication state of each communication line of the communication network 5, and may be, for example, data indicating the communication state of each communication device 11 provided in the data distribution management device 1. The communication state indicates, for example, the communication speed, whether communication is possible, whether communication is in progress, etc. The communication data may also be data regarding the clearance of the communication partner. In step S3, the data distribution management device 1, as a plurality of portable on-premise servers, assigns an IP (Internet Protocol) address to a client such as another data distribution management device 1 connected to itself, and sets a DNS (Domain Name System) server to itself at the same time, and returns its own IP address in response to an address resolution request for a cloud URL (Uniform Resource Locator), and operates as if it were a cloud server. This makes it possible to search for files on the cloud, download files, and upload files as if it were connected to a cloud system.

[0039] Next, in step S4, the data distribution management device 1 acquires differential data relating to the difference between the data recorded in two or more data distribution management devices 1. The differential data is, for example, data indicating the difference between the content data or metadata recorded in two data distribution management devices 1 that communicate with each other. The differential data is, for example, data indicating whether or not the content data associated with the same unique ID or the like as the content data recorded in the data distribution management device 1A is recorded in the data distribution management device 1B. The differential data may also be the difference between the metadata recorded in the data distribution management device 1A and the metadata recorded in the data distribution management device 1B. In step S4, for example, the data distribution management device 1 may acquire metadata including a unique ID recorded in the data distribution management device 1 that shares the content data, and acquire the differential data by comparing the acquired metadata with the recorded metadata. In step S4, when the data distribution management devices 1 are in a situation where they can directly communicate with each other via a public communication network (such as a mobile phone or satellite line), a wireless LAN, or the like, they discover each other and automatically exchange differential data. This update of differential data involves the synchronous sharing of the catalog database in the recording unit 15 and the synchronous sharing of content files. Regarding file synchronization, the differential data is updated based on the update history of the files recorded in chronological order, and regarding the deletion operation, a deletion operation record is added so that the application side recognizes that the content data has been deleted without actually erasing it.

[0040] Next, in step S5, the data distribution management device 1 communicates and shares one or more of the content data or the metadata with the other data distribution management device 1. In step S5, for example, the data distribution management device 1 selects a communication line for communicating one or more of the content data or the metadata based on the communication data acquired in step S3. In this case, the data distribution management device 1 may communicate the metadata using the communication line of the communication device 11C if the communication device 11C using a low-speed communication line capable of long-distance communication is capable of communication, for example, as shown in FIG. 4. Also, the data distribution management device 1 may select the communication line with the highest communication speed among the communication devices 11A and 11B using a high-speed communication line for short-distance communication, for example, as shown in FIG. 5, and communicate the content data using the selected communication line. Also, in the case where two data distribution management devices 1 sharing data are connected to each other by multiple communication lines, the data distribution management device 1 may simultaneously use the multiple communication lines as independent lines for synchronizing the content data or the metadata. This allows, for example, metadata with a small data capacity to be shared using a low-speed communication line capable of long-distance communication, and content data with a large data capacity to be shared using a short-distance but high-speed communication line. This also allows users to quickly recognize which data distribution management device 1 holds which content data, and by assigning higher priority to content data in demand, it is possible to increase the probability that the content data will be delivered to the user who demands it, and at the same time, it is possible to encourage users to operate the mobile object 2 to obtain this content data, bringing the data distribution management devices 1 closer to each other, or to change their behavior so that they go to get it. This allows communication to be performed using more appropriate communication lines even between distributed data systems during a large-scale disaster, etc.

[0041] In step S5, the data distribution management device 1 communicates one or more of the content data and the metadata based on the priority data acquired in step S2. In this case, for example, the data distribution management device 1 communicates the content data or the metadata with higher priority. This makes it possible to communicate the data with higher priority, so that appropriate data can be easily shared between distributed data systems even in the event of a large-scale disaster.

[0042] In step S5, the data distribution management device 1 communicates at least one of the content data and the metadata based on the difference data acquired in step S4. In this case, for example, if the content data associated with the same unique ID or the like as the content data recorded in the data distribution management device 1A is not recorded in the data distribution management device 1B, the data distribution management device 1 communicates the content data and shares the data. In addition, if there is a difference between the metadata recorded in the data distribution management device 1A and the metadata recorded in the data distribution management device 1B, the data distribution management device 1 shares the metadata. In this case, for example, the metadata is communicated so that the metadata with the newer time indicated by the time data included in the metadata is shared. Therefore, even if the metadata including the ID of the content data is shared first via a control line or the like and the content data associated with this metadata is not shared, the content data can be shared through the multiple data distribution management devices 1 in the form of a bucket brigade. This makes it possible to appropriately select the data to be communicated, and makes it easier to share data between distributed data systems during a large-scale disaster or the like.

[0043] Also, in step S5, if multiple other data distribution management devices 1 with which it can directly communicate hold the same content data as the content data being synchronously shared via the communication network 5, the data distribution management device 1 may simultaneously distribute and obtain the content data from the multiple other data distribution management devices 1 with which it can directly communicate, and resume or combine the received content data to generate the original content data.

[0044] In addition, in step S5, when transmitting large-volume content data or metadata, if the transmission cannot be completed within a certain period of time due to a decrease in the communication line speed, the data distribution management device 1 may delay synchronization based on a preset policy.

[0045] Furthermore, in step S5, when the data distribution management device 1 executes a download operation of the data to be acquired, a request for data sharing may be distributed or registered via a communication line from the portable data distribution management device 1 mounted on the mobile body 2 to the surrounding data distribution management devices 1. In such a case, when the data distribution management device 1 receives the request, it may display data such as whether or not it has content data with the same ID assigned thereto via the display unit 14. Also, if it does not have the content data, it may be set to increase the priority of synchronization of this content data.

[0046] In addition, in step S5, when sharing data, the data distribution management device 1 may acquire contact history data indicating the history of the other party with whom the data distribution management device 1 of the other party shared data, movement history data indicating the movement history of the mobile body 2 carrying the data distribution management device 1, and prioritize synchronization with the other party who is likely to deliver the data to be shared. In such a case, for example, the current location of the other party with whom the most recent data was shared may be predicted from the contact history data and the movement history data, and the mobile body 2 may be controlled to move to the predicted current location. In addition, for example, the current location of the other party with whom the most recent data was shared may be predicted from the contact history data and the movement history data, and the route to the predicted current location may be presented to the user via the display unit 14.

[0047] In addition, in step S5, the data distribution management device 1 may set priority data based on the shared metadata. In this case, the data distribution management device 1 may use priority data included in the metadata, but is not limited to this, and may set priority data based on the metadata as in step S2. In addition, if the content data linked to the metadata is not shared, priority data may be set to increase the priority. In this case, the priority data may be set by a user who uses the data distribution management device 1 on the data receiving side. This allows the data distribution management device 1 on the content data receiving side to set priority data, for example, making it easier to share high-priority data even in the event of a disaster.

[0048] The above steps complete the operation of the data distribution management system 100 according to the embodiment of the present invention. As a result, in a situation where the public communication network is disrupted over a wide area, such as during a large-scale disaster, the data distribution management device 1 can be brought to the on-site command center of a disaster response organization and used as a data processing device for data collection and analysis, making it easy to share data between distributed data systems. In addition, it is assumed that the public communication network is disrupted during a large-scale disaster, and in this environment, multiple disaster response organizations can maintain data sharing between on-site devices or between remote command centers via ad hoc communication means, and by carrying the data distribution management device 1, data can be shared between distant bases where direct communication is not possible by directly sharing differential data when the data distribution management devices 1 approach each other.

[0049] In addition, by connecting a catalog database system that manages content data and metadata to the data distribution management system 100, in a system in which applications used by users are combined, even if the communication paths between the systems are interrupted, the use of application services can be continued, and the application services can be continued without being aware of the interruption of communication with the cloud or the outside. In addition, in order to continue the service as a single system even in a situation where the system is completely isolated from the cloud, the server itself is operated on-premise, and multiple servers operating on-premise are brought to multiple geographically separated locations where communication is interrupted and each server updates the data, so that these data can be managed in an integrated manner without inconsistencies. In addition, regardless of which of the multiple servers operating on-premise is connected, the same operability and usability can be provided to the user without the user being aware of the connection location or the communication line between the locations, and the entire system can be operated as one system.

[0050] Although the embodiment of the present invention has been described, this embodiment is presented as an example and is not intended to limit the scope of the invention. Such a novel embodiment can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. This embodiment and its modifications are included in the scope and spirit of the invention, and are included in the invention and its equivalents described in the claims. [Explanation of symbols]

[0051] 1. Data distribution management device 2. Mobile 3 Server 4 Buildings 5. Communication Network 6 Terminal 11 Communication Device 12 Sensors 13 Processing section 14 Display section 15 Recording Section 100 Data Distributed Management System

Claims

1. a recording means for linking content data shared between a first recording medium and a second recording medium with metadata relating to attributes of the content data and recording the linked content data on the first recording medium; a communication means having two or more communication lines for communicating one or more of the content data and the metadata recorded by the recording means between the first recording medium and the second recording medium; A data distribution management system characterized by:

2. the recording means records the metadata including priority data indicating a priority of sharing the content data; The communication means communicates at least one of the content data and the metadata based on the priority data included in the metadata recorded by the recording means.

2. The data distribution management system according to claim 1,

3. The communication means acquires communication data indicating a communication state of each of the communication lines, and selects the communication line for communicating at least one of the content data and the metadata based on the acquired communication data.

2. The data distribution management system according to claim 1,

4. the communication means acquires difference data relating to a difference between the data recorded on the first recording medium and the data recorded on the second recording medium, and communicates at least one of the content data and the metadata based on the acquired difference data.

2. The data distribution management system according to claim 1,

5. the recording means records the metadata including priority data indicating a priority of sharing the content data on the second recording medium; The communication means communicates at least one of the content data and the metadata based on the priority data included in the metadata recorded by the recording means.

2. The data distribution management system according to claim 1,

6. a recording step of linking content data shared between a first recording medium and a second recording medium with metadata relating to attributes of the content data and recording the content data on the first recording medium; a communication step of communicating, between the first recording medium and the second recording medium, at least one of the content data and the metadata recorded in the recording step, using two or more communication lines. A data distribution management method comprising:

Images