WO2021172589A1 - Information processing system and program - Google Patents

Abstract

This invention addresses the problem of handling a large amount of data and preventing leakage of such data, and improving convenience with regard to the same.　This invention comprises: at least one node server 2 on a cloud C, each node server functioning as a node belonging to a network related to a blockchain; and at least one node terminal 1, each of which is connected to the cloud C via a dedicated line LL and functions as a node belonging to the network relating to the blockchain. Upon being instructed to save at least one file F, each of all the nodes constituting the network relating to the blockchain performs a blockchain management function to cause the at least one file F to be managed by the network. Due to this configuration, the foregoing problem is solved.

Description

Information processing system and program

The present invention relates to an information processing system and a program.

In recent years, the development of various technologies utilizing blockchain has been active. For example, information in which an entity (information processing device) that creates and updates a document links the state of each version of the document and registers it in the blockchain to store the state of the document including the change history in a verifiable manner. There was a technique related to a processing system (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2019-12194

However, in the prior art including the technique described in Patent Document 1, the management device (blockchain management device) manages the blockchain. That is, it is the management device that manages the documents, and the amount of documents that can be managed may be determined by the performance of the management device. Furthermore, when a document created and updated is embedded in the blockchain, the document itself could not be kept secret.

It is an object of the present invention to realize the handling of a large amount of data and the prevention of leakage of the data, and to improve the convenience related to them.

In order to achieve the above object, the information processing system of one aspect of the present invention is
One or more first-class information processing devices on the cloud that function as nodes belonging to the blockchain network, respectively.
One or more type 2 information processing devices that are connected to the cloud via a dedicated line and function as nodes belonging to the network related to the blockchain, respectively.
With
When each of the nodes constituting the network related to the blockchain is instructed to save one or more data, a blockchain management function for putting the one or more data in a state managed by the network is provided. Make it work.

The program of one aspect of the present invention is a program corresponding to the above-mentioned information processing system of one aspect of the present invention.

According to the present invention, it is possible to handle a large amount of data and prevent leakage of the data, and to improve the convenience related to them.

It is a schematic diagram explaining an example of the outline of the service to which the information processing system which concerns on one Embodiment of this invention is applied. It is a figure which shows the structural example of the information processing system which concerns on one Embodiment of this invention applied when providing the service shown in FIG. It is a block diagram which shows the hardware configuration of the node server in the information processing system of FIG. It is a functional block diagram which shows an example of the functional configuration of the node server and the node terminal of FIG. It is a schematic diagram which shows an example of the relationship of the blockchain managed by a node server and a node terminal having a functional configuration of FIG. 4, and various data managed by using the blockchain. It is a schematic diagram explaining an example of using this service by locally connecting an operator terminal to a node terminal. FIG. 6 is a functional block diagram showing an example of functional configurations of a user terminal, a node terminal, and a node server in the case of FIG.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a schematic diagram illustrating an example of an outline of a service (hereinafter, referred to as “the service”) to which the information processing system according to the embodiment of the present invention is applied.

This service is a service that enables the management of one or more data using the technology related to the blockchain by applying the information processing system shown in FIG. Hereinafter, in the description of the present embodiment, it is assumed that the file F is managed as an example of one or more data.
This service is provided to a predetermined organization (for example, a company) by a service provider (not shown). However, the operation for using this service is performed by the operator U who belongs to the predetermined organization.

In this service, a network related to blockchain is constructed. This network is composed of a plurality of nodes, and at least one node exists on the cloud C.
In the example of FIG. 1, each of the four node servers 2-1 to 2-4 managed by the service provider functions as one node by being arranged in the cloud C.
Further, in the example of FIG. 1, five node terminals 1-1 to 1-5 are transferred from the service provider to a predetermined group (for example, a company). Each of these five node terminals 1-1 to 1-5 functions as one node by being connected to the cloud C via each of the dedicated lines LL-1 to LL-5.
That is, in the example of FIG. 1, a total of nine node servers 2-1 to 2-4 and node terminals 1-1 to 1-5 function as each of the nine nodes, thereby forming a network related to the blockchain. It is composed.

Hereinafter, when it is not necessary to individually distinguish the node terminals 1-1 to 1-5, these are collectively referred to as "node terminal 1". When the node terminal 1 is called, the dedicated lines LL-1 to LL-5 are collectively referred to as "dedicated line LL". When it is not necessary to distinguish the node servers 2-1 to 2-4 individually, these are collectively referred to as "node server 2".

Here, the leased line LL is a communication line dedicated to a specific user.
For example, communication on a leased line is isolated from a network (for example, the Internet) configured to include an untrusted information processing device or the like. That is, communication between information processing devices connected by a dedicated line LL is unlikely to be eavesdropped or intercepted by a malicious third party or the like. That is, since this service is used via a dedicated line LL, it is provided in a state where there is a low possibility of eavesdropping or interception by a third party or the like. The leased line LL does not have to be physically isolated from the Internet or the like. That is, for example, a virtual dedicated line using VPN (Virtual Private Network) technology can also be adopted as the above-mentioned dedicated line LL.

Here, in order to function as one node belonging to the network related to the blockchain, it is necessary to provide a file system and a blockchain.
Here, the "file system" is a system that stores and manages the entire data of the file F itself.

Further, here, the "blockchain" refers to various information related to one or more data (for example, file F) managed by using this service (data related to soundness verification such as metadata and hash related to file F, etc.). ) Is a series of data in which blocks are connected like a chain.
In general, the word blockchain can mean distributed ledger technology or distributed networks. That is, a blockchain word is an ambiguous word that includes a series of data itself in which data called a block is connected like a chain, and technologies and networks related thereto.
Therefore, hereinafter, the decentralized network that manages the blockchain is referred to as a "network related to the blockchain", and is distinguished from the "blockchain" which is a series of data in which blocks are connected like a chain.

Specifically, for example, in the example of FIG. 1, each of the node servers 2-1 to 2-4 has a blockchain BC-1 to 2-4 and a file system FS-1 to FS-4, respectively. And are provided.
In the following, when the term "node server 2" is used, the blockchains BC-1 to 2-4 are collectively referred to as the "blockchain BC", and the file systems FS-1 to FS-4 are collectively referred to as the "file". It is called "system FS".

Further, as will be described in detail later, the node terminal 1 can execute a part or all of the predetermined processing related to the provision of this service. That is, the blockchain BC and the file system FS described above may be provided in each of the node terminals 1-1 to 1-5, if necessary.

Here, the node terminal 1 and the node server 2 that make up the network related to the blockchain are both "nodes" that make up the network related to the blockchain. Further, both the node terminal 1 and the node server 2 are information processing devices that execute a part or all of a predetermined process related to the provision of this service. Therefore, hereinafter, when it is not necessary to distinguish the node terminal 1 and the node server 2 individually, these are collectively referred to as a "node" as appropriate.

Summarizing the above, the network related to the blockchain in the present embodiment includes "node servers 2-1 to 2-4 on the cloud C, which function as nodes belonging to the network related to the blockchain, respectively" and "to the cloud C. Node terminals 1-1 to 1-5, which are connected via dedicated lines LL-1 to LL-5 and function as nodes belonging to a network related to a blockchain, respectively.

The outline of this service will be described below along with the flow when the operator U manages the file F using this service.

In the example of the present embodiment, when the operator U performs an operation to manage the file F by using this service, the hardware key IDH is required. Further, in the example of the present embodiment, in order for the operator U to operate the node terminal 1-1, an identification card IDC for authentication of the operator U is required. Then, in the example of the present embodiment, only the node terminal 1-1 is allowed to be operated and used by the operator U, and in order for the operation to be possible, the hardware key IDH and the ID card IDC are 1-1. It is assumed that it needs to be read by.
Therefore, as a premise, it is assumed that the operator U has a hardware key IDH and an ID card IDC for using this service. In addition, the information related to the hardware key IDH and the ID card IDC shall be managed in advance by the node used in this service.

First, the operator U executes various operations related to the personal authentication step ST1 shown in FIG.

Specifically, for example, the operator U connects the hardware key IDH to the node terminal 1-1. The node terminal 1 collates the predetermined information that can be acquired from the hardware key IDH with the information about the hardware key IDH managed by the node. When it is verified that the hardware key IDH is correct, the node terminal 1 authenticates the operator U as a user of this service.
Further, for example, the operator U holds the IDC of the operator U himself / herself over a wireless card reader (not shown) connected to the node terminal 1-1. The node terminal 1-1 collates the predetermined information that can be acquired from the ID card with the information about the ID card managed by the node. When it is verified that the ID card is correct, the node terminal 1-1 authenticates the operator U as the person who is the user of this service.

In this way, the node terminal 1-1 can authenticate that the operator U is the user of the service and the operator U himself / herself by both the hardware key IDH and the ID card. That is, a third party who does not have either the hardware key IDH or the ID card managed by the node used in this service cannot use this service. Hereinafter, it is assumed that the operator U is a user of this service and has been authenticated as the person himself / herself.
When the operator U is a user of this service and is authenticated to be the person himself / herself, the node terminal 1 is made to function as a node of the network related to the blockchain. That is, in the node terminal 1-1, the blockchain management function and the like, which will be described later, are made to function. As a result, this service is provided to the operator U.
Here, the "blockchain management function" is a state in which one or more data is managed by each of the nodes constituting the network related to the blockchain when the storage of one or more data is instructed. It is a function to make. The file movement step ST2 and the save process step ST3 in FIG. 1 are examples of the blockchain management function.

When the node terminal 1-1 is made to function as a node of the network related to the blockchain, the node terminal 1-1 connects with any node server 2 among the plurality of node servers 2 on the cloud C and the dedicated line LL. Information is exchanged through. Hereinafter, in the description of FIG. 1, the node terminal 1-1 operated by the operator U will be described as exchanging various information with the node server 2-1.

Next, the operator U executes various operations related to the file movement step ST2 shown in FIG.
That is, the operator U instructs to save one or more data in the file movement step ST2. For example, the operator U instructs to save the file F by performing an operation of storing a predetermined file F to be managed by this service in a dedicated folder D.
Specifically, for example, the operator U operates a predetermined user interface provided by the node terminal 1-1 to store a predetermined file F to be managed by the service in a dedicated folder D. I do.
Here, the dedicated folder D is monitored by the application program that provides this service. As a result, the file F stored in the dedicated folder D is grasped as one or more data managed by this service, and becomes the target data of the storage process described later.

Hereinafter, the outline of the saving process by the node server 2-1 when the operator U gives an instruction to save the file F which is one or more data as described above will be described with reference to FIG. The details of the storage process by the node server 2-1 will be described with reference to FIG.

Next, on the node server 2-1 various functions related to step ST3 of the storage process shown in FIG. 1 are exhibited. As a result, in step ST3 of the storage process, the node server 2-1 puts the file F in a state managed by the network related to the blockchain.

Specifically, as shown in FIG. 1, the encryption and division functional block FB1 acquires the file F. As a result, in the encryption / division step ST3-1, the encryption / division functional block FB1 encrypts and divides the file F1.

Next, as shown in FIG. 1, the blockchain management functional block FB2 "file distributed storage, history storage" of the encrypted and divided file F.
That is, the functional block FB2 of the blockchain management distributes and stores the encrypted file F and the file F divided into a plurality of files F in the file systems FS-1 to FS-4.
Further, various information about the file F is stored in the blockchain BC as a history. Specifically, after a predetermined process related to the blockchain, it is stored as a history in all of the blockchains BC-1 to BC-4 provided in each of the node servers 2-1 to 2-4.
The details of various information related to the file F (data related to the verification of soundness such as metadata and hashes related to the file F) stored as a history in the blockchain BC will be described with reference to FIG.

As described above, in the node server 2-1 as various functions related to the storage process step ST3 shown in FIG. 1, the functions of the encryption and division functional block FB1 and the blockchain management functional block FB2 are exhibited. NS. As a result, the node server 2-1 puts the file F in a state managed by the network related to the blockchain.

As described above, the history of the file F is stored in each of the blockchain BCs provided in each of the plurality of node servers 2. As a result, when the file F is tampered with, each of the nodes can detect that the file F has been tampered with. In other words, the file F whose soundness has been verified by this service is guaranteed that the data of the file F is valid.

Further, as described above, the file F is stored after being encrypted and divided in each of the file systems FS provided in each of the plurality of node servers 2. That is, the file F is encrypted and stored in the file system FS.
Further, the file F is divided and saved in the file system FS. As a result, when decrypting the file F, it is necessary to acquire a fragment of the other file F divided from the other node.
As described above, it is difficult to decrypt the file F except for the operator U who stores the file F. That is, this service can prevent the leakage of the data of the file F.
Furthermore, for a file F having a large file size, it is possible to achieve the effect that handling when saving is easy by dividing the file F.

Summarizing the above, this service is a service that manages data that can handle large amounts of data and prevent leakage of the data.

The outline of this service has been described above with reference to FIG.
Hereinafter, the information processing system applied when the service shown in FIG. 1 of this service is provided will be described with reference to FIGS. 2 to 4.
FIG. 2 is a diagram showing a configuration example of an information processing system according to an embodiment of the present invention applied when the service shown in FIG. 1 is provided.

In the description of FIG. 1, it is assumed that the number of node servers 2 managed by the service provider is four, and the number of node terminals 1 transferred from the service provider to a predetermined organization is five. , Not particularly limited to this.
That is, as shown in FIG. 2, the information processing system of the present embodiment used in this service includes n node terminals 1-1 to 1-n and m units (n is an arbitrary integer value of 1 or more). (M may be an arbitrary integer value of 1 or more independent of n) and may be configured to include the node servers 2-1 to 2-m.

Each of the node terminals 1-1 to 1-n is connected to the cloud C via each of the dedicated lines LL-1 to LL-n.
The node servers 2-1 to 2-m are arranged on the cloud C. In addition, the node servers 2-1 to 2-m can exchange various information related to this service with each other.
Each of the node terminals 1-1 to 1-n can exchange various information related to this service with any of the node servers 2-1 to 2-m on the cloud C. ..

FIG. 3 is a block diagram showing the hardware configuration of the node terminal in the information processing system of FIG.

The node terminal 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a bus 14, an input / output interface 15, an output unit 16, and an input unit 17. A storage unit 18, a communication unit 19, and a drive 20 are provided.

The CPU 11 executes various processes according to the program recorded in the ROM 12 or the program loaded from the storage unit 18 into the RAM 13.
Data and the like necessary for the CPU 11 to execute various processes are also appropriately stored in the RAM 13.

The CPU 11, ROM 12 and RAM 13 are connected to each other via the bus 14. An input / output interface 15 is also connected to the bus 14. An output unit 16, an input unit 17, a storage unit 18, a communication unit 19, and a drive 20 are connected to the input / output interface 15.

The output unit 16 is composed of a display, a speaker, and the like, and outputs various information as images and sounds.
The input unit 17 is composed of a keyboard, a mouse, and the like, and inputs various information.

The storage unit 18 is composed of a hard disk, a DRAM (Dynamic Random Access Memory), or the like, and stores various data.
The communication unit 19 communicates with another device (node server 2 in the example of FIG. 1) via the network N including the Internet.

A removable media 41 made of a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is appropriately mounted on the drive 20. The program read from the removable media 41 by the drive 20 is installed in the storage unit 18 as needed.
Further, the removable media 41 can also store various data stored in the storage unit 18 in the same manner as the storage unit 18.

Although not shown, the node server 2 of the information processing system of FIG. 2 has basically the same configuration as the hardware configuration shown in FIG. That is, the node server 2 includes the CPU 11, ROM 12, RAM 13, bus 14, input / output interface 15, output unit 16, input unit 17, storage unit 18, communication unit 19, and drive 20 of the node terminal 1 shown in FIG. Similar hardware configurations include a CPU 21, a ROM 22, a RAM 23, a bus 24, an input / output interface 25, an output unit 26, an input unit 27, a storage unit 28, a communication unit 29, and a drive 30.

Hereinafter, an example of the functional configuration of the node terminal 1 and the node server 2 when the processes corresponding to steps ST1 to ST3 of FIG. 1 are executed will be described with reference to FIG.

FIG. 4 is a functional block diagram showing an example of the functional configuration of the node terminal and the node server of FIG. For the sake of simplification of the description, in the description of FIG. 4, only one node terminal 1 and one node server 2 are shown.

When the process corresponding to the personal authentication step ST1 of FIG. 1 is executed, the hardware key detection unit 111, the personal authentication unit 112, and the node management unit 113 function in the CPU 11 of the node terminal 1. Further, the node management unit 211 functions in the CPU 21 of the node server 2.

The hardware key detection unit 111 of the node terminal 1 detects the hardware key IDH connected to the node terminal 1. When the operator U connects the hardware key IDH to the node terminal 1, the hardware key detection unit 111 sets the predetermined information that can be acquired from the hardware key IDH and the information about the hardware key IDH managed by the node. Based on this, the hardware key IDH is detected.
That is, the hardware key detection unit 111 determines whether or not the hardware key or other device connected to the node terminal 1 is the hardware key IDH related to this service. Then, when it is determined that the hardware key IDH is related to this service, it is assumed that the hardware key IDH connected to the node terminal 1 is detected.

The personal authentication unit 112 authenticates whether the operator U is the operator U of the service by using the identification card IDC read by the node terminal 1. When the operator U loads his / her own IDC into the node terminal 1, the operator U is read based on the predetermined information that can be obtained from the IDC and the information about the IDC managed by the node. Authenticate as the person who uses the service.

In the node management unit 113, when the hardware key IDH is detected by the hardware key detection unit 111 and the operator U is authenticated by the personal authentication unit 112 as the operator U of the service, the node terminal 1 Is managed as a node of the network related to the blockchain.
Further, in this case, the node management unit 211 of the node server 2 manages the node terminal 1 as a node of the network related to the blockchain. That is, the node management unit 113 of the node terminal 1 and the node management unit 211 of the node server 2 can manage the node terminal 1 as a node of the network related to the blockchain by cooperating with each other.

In this way, when the operator U is authenticated to be the operator U himself who is authorized to operate this service based on the hardware key IDH and the ID card, the node terminal 1 is set to the block chain. It is managed as a node of the network related to.

Here, it is preferable that only a reliable information processing device is provided as a node in a network related to a so-called consortium type or private type blockchain. Therefore, in this service, as another node of the node server 2, the node terminal 1 authenticated based on the hardware key IDH and the identification IDC is managed as a reliable information processing device as a node of the network related to the blockchain. Will be done.
In this way, in this service, only the reliable node terminal 1 is managed in cooperation with the node server 2 so as to be provided in the network related to the blockchain.
The node terminal 1 managed so as to be provided in the network related to the blockchain can exert the blockchain management function described later. That is, it can be said that the hardware key IDH is provided in the information processing system according to the embodiment of the present invention in order to exert the blockchain management function in a predetermined one of the plurality of node terminals 1.

When the processes corresponding to the file management step ST2 and the save process step ST3 of FIG. 1 are executed, the node management unit 113, the file acquisition unit 114, and the file management unit 115 are executed in the CPU 11 of the node terminal 1. Works. Further, a blockchain storage unit 150 and a file storage unit 160 are provided in one area of the storage unit 18 of the node terminal 1.
Further, in the CPU 21 of the node server 2, the node management unit 211 and the file management unit 213 function. Further, a blockchain storage unit 250 and a file storage unit 260 are provided in one area of the storage unit 28 of the node server 2.

As described above, the node terminal 1 can execute a part or all of the predetermined processing related to the provision of this service. Therefore, in the description of FIG. 4, the process of step ST3 of the storage process in the description of FIG. 1 is basically described as being executed by the node terminal 1. Further, as described above, the file management step ST2 and the saving process step ST3 are examples of the blockchain management function.

First, the operator U operates a predetermined user interface provided by the node terminal 1-1 to perform an operation for storing a predetermined file F to be managed by the service in a dedicated folder D.
Here, the dedicated folder D is monitored by the application program that provides this service. As a result, the file acquisition unit 114 acquires the file F stored in the dedicated folder D as one or more data managed by this service.

The file management unit 115 manages the file F by using the blockchain BC and the file system FS.
The file management unit 115 includes a blockchain management unit 121 and a distributed file system management unit 122.

The blockchain management unit 121 extracts various information related to the file F (data related to soundness verification such as metadata and hash related to the file F) and manages the information as a part of the block. Further, the blockchain management unit 121 manages various information related to the file F to other nodes provided in the network related to the blockchain, which are managed by the node management unit 113, as a part of a new block of the blockchain. Let me.
That is, although the details will be described later with reference to FIG. 5, the blockchain management unit 121 of the node terminal 1 cooperates with the blockchain management unit 221 of the node server 2 to provide various information regarding the file F to the blockchain. Manage as part of a block.

In this way, the blockchain management unit 121 can have all the nodes provided in the network related to the blockchain manage various information related to the extracted file F. This makes it difficult for a malicious third party or the like to falsify various information related to the file F.

Further, the distributed file system management unit 122 encrypts and divides and manages the entire data of the file F itself.
At this time, the distributed file system management unit 122 manages the file F managed as a result of the blockchain management function by imposing access restrictions on a person other than the operator U who has instructed to save the file F. That is, for example, the file management unit 115 can provide access control in the storage unit of each node belonging to the network related to the blockchain and divide it for each operator U.
Specifically, for example, the distributed file system management unit 122 encrypts the entire data of the file F itself by using the information contained in the hardware key IDH and the ID card. That is, the distributed file system management unit 122 encrypts the file F so that it can be decrypted only by the operator U who holds the hardware key IDH and the ID card.
Next, the distributed file system management unit 122 of the node terminal 1 divides the encrypted file F. Next, the distributed file system management unit 122 of the node terminal 1 cooperates with the distributed file system management unit 122 of the node server 2 to store the encrypted and divided file F in the file storage units of the plurality of node terminals 1. It is distributed and managed in 160 and the file storage unit 260 of the node server 2.

In this way, the distributed file system management unit 122 divides the encrypted file F and distributes and stores the encrypted file F in a plurality of file systems FS. As a result, when decrypting the file F, it is necessary to acquire a fragment of the other file F divided from the other node.
As described above, it is difficult to decrypt the file F except for the operator U who stores the file F. That is, this service can prevent the leakage of the data of the file F.
Furthermore, for a file F having a large file size, it is possible to achieve the effect that handling when saving is easy by dividing the file F.

The file management unit 115 stores and manages the blockchain BC in the blockchain storage unit 150 by the blockchain management unit 121, and stores the file F in the file storage unit 160 as the file system FS from the distributed file system management unit 122. Can be managed.

Note that, as in the above description, the node server 2 includes a file acquisition unit 212 having basically the same function as the file acquisition unit 114 of the node terminal 1. That is, similarly, when the node server 2 accepts the operation for using this service by the operator U, the node server 2 itself and other nodes can manage the file F.

The information processing system applied when the service shown in FIG. 1 of this service is provided has been described above with reference to FIGS. 2 to 4.
Hereinafter, with reference to FIG. 5, details of various information regarding the storage process by the node server 2-1 and the file F stored as a history in the blockchain BC will be described.

FIG. 5 is a schematic diagram showing an example of the relationship between the blockchain managed by the node server and the node terminal having the functional configuration of FIG. 4 and various data managed by the blockchain.
FIG. 5 shows a series of data in which blocks B1 to B3 are connected like a chain as an example of the blockchain BC. Further, in the block chain BC of FIG. 5, when the blocks B1 and B2 are connected like a chain, the storage of the file F is instructed, and various information related to the file F is managed as a part of the block B3. This is an example.

Further, in FIG. 5, the file recording database FDB1 at the stage of only block B1 of the blockchain BC and the file recording database FDB2 at the stage of a series of data in which blocks B1 and B2 are connected like a chain are illustrated by dotted lines. ing. Further, the file recording database FDB3 at the stage of a series of data in which the blocks B1 to B3 are connected like a chain is shown by a solid line. Hereinafter, when it is not necessary to individually distinguish the file recording databases FDB1 to FDB3, these are collectively referred to as "file recording database FDB".
The file recording database FDB is a database that stores various information about each of the data managed by the network related to the blockchain. Here, the various information regarding the file F managed by the network related to the blockchain includes the following information. That is, for example, the "hash", "registration date and time", and "registrant and viewer" information regarding the file F are examples of various information regarding the file F. Here, the various information about the file F does not include the entire data of the file F itself, but includes the hash of the file F. That is, the file recording database FDB contains a hash of the file F that can be used to verify the integrity of the file F. As a result, when the file F is decrypted and the file F is tampered with, it is possible to detect that the tampering has occurred.
Further, as described above, the file recording databases FDB1 and FDB2 are shown by broken lines, and the file recording database FDB3 is shown by a solid line. This indicates that the file recording database FDB records the latest contents (file recording database FDB3 in FIG. 5).

The block B1 is composed of the first related information HD1, the base data BD1, and the second related information FT1.
Here, the first related information HD1 is an initial value in the first block B1 of the blockchain BC.
Further, the base data BD1 is data that serves as a base for connecting to the next block B2 of the blockchain BC. The base data BD1 stores information corresponding to the file recording database FDB1. That is, for example, the base data BD1 includes "hash", "registration date and time", and "registrant and viewer" information regarding one or more data managed from the beginning by this service. If one or more data managed from the beginning by this service does not exist, a predetermined base data (for example, a random number string) is adopted.
The second related information is the hash value of the block B1. An arrow is drawn from the first related information HD1, the base data BD1, and the file recording database FDB1 toward the second related information. This indicates that the hash value of the second related information FT1 is a hash value that correlates with the data of the first related information HD1, the base data BD1, and the file recording database FDB1.

The block B2 is composed of the first related information HD2, the recorded data BD2, and the second related information FT2.
Here, the first related information HD2 is the second related information FT1 of the previous block B1 in the blockchain BC. In this way, consecutive blocks such as blocks B1 and B2 are generated so that the first related information HD2 of the block B2 and the second related information FT1 of the previous block B1 match. As a result, continuous blocks become a series of data connected like a chain.
Further, the recorded data BD2 is information of "hash", "registration date and time", and "registrant and viewer" regarding the changed data. The recorded data BD2 stores information corresponding to the difference between the file recording database FDB2 and the file recording database FDB1. That is, for example, among one or more data managed by this service at the stage of generating block B2, a "hash" relating to data of a difference from one or more data managed by this service at the stage of generating block B1. , "Registration date and time", and "Registrant and viewer" information is included in the recorded data BD2.
The second related information is the hash value of the block B2. An arrow is drawn from the first related information HD2, the recorded data BD2, and the file recording database FDB2 toward the second related information. This indicates that the hash value of the second related information FT2 is a hash value that correlates with the data of the first related information HD2, the recorded data BD2, and the file recording database FDB2.

Hereinafter, when the block B3 is generated, the file F that was not managed by the service at the stage of generating the block B2 is newly managed by the service at the stage of generating the block B3. explain.
In this case, the node terminal 1 generates the block B3 as the latest block of the blockchain BC. The block B3 is composed of the first related information HD2, the recorded data BD2, and the second related information FT2. Hereinafter, what kind of information is adopted as the recorded data BD2 and the like will be described.
As in the description of FIG. 4, the process of step ST3 of the storage process in the description of FIG. 1 is basically described as being executed by the node terminal 1.

Here, the first related information HD2 is the second related information FT1 of the previous block B1 in the blockchain BC. In this way, consecutive blocks such as blocks B1 and B2 are generated so that the first related information HD2 of the block B2 and the second related information FT1 of the previous block B1 match. As a result, continuous blocks become a series of data connected like a chain.

Next, the blockchain management unit 121 of the node terminal 1 acquires the file recording FR of the file F. The file record FR includes records (information) of "hash", "registration date and time", and "registrant and viewer" regarding file F. The file recording FR is adopted as a part of the recording data BD3 of the block B3.
Further, the file recording FR of the file F is stored in the file recording database FDB3 based on the file recording database FDB2 as the latest information related to the file F.

Next, the blockchain management unit 121 of the node terminal 1 generates a hash value that correlates with the first related information HD2, the base data BD2, and the data of the file recording database FDB2 as the second related information FT3. do.
As a result, the block B3 is generated as the latest block of the blockchain BC.

At this time, the entire data of the file F itself is processed as follows.
The distributed file system management unit 122 of the node terminal 1 converts the file F into the encrypted and divided files FS1 to FS4.
Next, the distributed file system management unit 122 of the node terminal 1 distributes and stores the encrypted and divided files FS1 to FS4 in a plurality of nodes (for example, each of the node servers 2-1 to 2-4). ..
In this way, the encrypted and divided files FS1 to FS4 are distributed and stored in the nodes provided in the network related to the blockchain.

As described above, with reference to FIG. 5, the details of various information regarding the save process by the node server 2-1 and the file F saved as the history in the blockchain BC have been described.

FIG. 6 is a schematic diagram illustrating an example in which the operator terminal is locally connected to the node terminal to use this service.

Here, the local connection means, for example, a connection in a range called Local Area Network (local area network, hereinafter referred to as LAN). A LAN is a network that cannot be freely connected from the Wide Area Network side in areas such as homes and offices.

In addition to operating a predetermined user interface provided by the node terminal 1, the operator U can also operate the operator terminal 3 locally connected to the node terminal 1 to obtain the file F by using the blockchain BC. Can be stored and managed. The details of the flow of this service when the operator U uses the operator terminal 3 will be described later.

In FIG. 1 above, a total of nine node servers 2-1 to 2-4 and node terminals 1-1 to 1-5 function as each of the nine nodes to form a network related to the blockchain. An example was shown. On the other hand, FIG. 6 shows an example in which the operator terminals 3-1 to 3-5 are additionally connected to the node terminals 1-1 to 1-5, respectively.
Specifically, the operator terminals 3-1 to 3-5 are locally connected to the node terminals 1-1 to 1-5 via the routers R1 to R5, respectively. Each of the routers R1 to R5 used for this local connection may be independent of each of the node terminals 1-1 to 1-5, or each of the node terminals 1-1 to 1-5. It may exist as a function. In the example of FIG. 6, among the node terminals 1-1 to 1-5, the routers R1 to R3 each exist independently of the node terminals 1-1 to 1-3, and the routers R4 and R5 Each exists as a function of each of the node terminals 1-4 and 1-5.

Each of the routers R1 to R5 can connect a plurality of networks to each other and control, that is, route the route as needed. Specifically, for example, the routers R1 to R5 each have a cloud C for providing this service for communication for the blockchain BC and the file system FS in each of the operator terminals 3-1 to 3-5. , Route to pass through the dedicated line LL as a connection with the LAN. Further, for example, each of the routers R1 to R5 routes the communication for browsing the Internet at each of the operator terminals 3-1 to 3-5 as a connection between the Internet and the LAN (not shown).

Here, the merits of having each of the routers R4 and R5 as one function of the own machine like the node terminals 1-4 and 1-5 will be described. That is, when the node terminal 1 is provided with the router function as in the node terminals 1-4 and 1-5, the dedicated line LL for connecting the node terminal 1 to the node server 2 is set in advance. As a result, the operator U can use this service simply by connecting the operation terminal 3 to the node terminal 1 for which the setting of the leased line LL has been completed.

Next, the configuration of the operation terminal 3 will be described. The operator terminal 3 is an information processing device such as a personal computer operated by the operator U. The operator terminal 3 has basically the same configuration as the hardware configuration shown in FIG. 3 described above. That is, although not shown, the operator terminal 3 includes the CPU 11, ROM 12, RAM 13, bus 14, input / output interface 15, output unit 16, input unit 17, storage unit 18, and communication unit 19 of the node terminal 1 shown in FIG. The hardware configuration similar to that of the drive 20 is provided with the CPU 31, ROM 32, RAM 33, bus 34, input / output interface 35, output unit 36, input unit 37, storage unit 38, communication unit 39, and drive 40, respectively. ..

Next, the flow of this service when the operator terminal 3 is used will be described. The operator U locally connects the operator terminal 3 to the node terminal 1 and performs the following operations using a predetermined user interface provided by the operator terminal 3. That is, the operator terminal 3 that has received the operation of the operator U encrypts the file F to be saved and managed using the blockchain BC, records the signature for the file F, and transmits the file F to the node terminal 1. I do. As a result, the operator U can save and manage the file F using the blockchain BC as long as the operator terminal 3 is locally connected to the node terminal 1 even from the outside isolated from the node terminal 1. Can be done.
In this way, the worker terminal 3 can bring the file F into a state managed by the network related to the blockchain by cooperating with the node terminal 1 and the node server 2.

The blockchain BC includes a public key for encrypting the file F on the operator terminal 3 (hereinafter referred to as "public key for encryption") and a signature of the operator U on the file F. The public key (hereinafter referred to as "public key for signature") is stored. Further, the private key corresponding to each of the encryption public key and the signature public key is stored in the operator terminal 3, respectively. The operator terminal 3 that has received the operation of the operator U acquires the encryption public key from the blockchain BC. The operator terminal 3 encrypts the file F using the acquired public key for encryption. Next, the operator terminal 3 records its own signature (electronic signature) in the file F using the private signature key. After that, the operator terminal 3 transmits the file F in which the signature is recorded to the node terminal 1. Then, the above-described processing is appropriately executed in each of the node terminal 1 and the node server 2 with reference to FIGS. 1 to 5. As a result, the file F transmitted from the operator terminal 3 is saved and managed using the file blockchain BC.

As described above, in this service, the encryption public key of the operator U to which the viewing authority is given is stored in the blockchain BC. Then, the file F cannot be decrypted unless the private key is paired with the public key for encryption. As a result, stronger viewing restrictions can be applied.
Further, the file F transmitted from the operator terminal 3 to the node terminal 1 is encrypted. Therefore, in the node terminal 1, only the encrypted file F exists unless the node terminal 1 newly creates the file F. As a result, even if the file F stored in the node terminal 1 or the node terminal 1 itself is stolen, the confidentiality of the file F can be ensured.
The encrypted file F is generated as many as the number of public keys for encryption. That is, for example, when the file F is shared between the first operator U and the second operator U, the encryption public keys of the first operator U and the second operator U are used, respectively. Encrypt each. As a result, each of the first operator U and the second operator U can decrypt the file F using the corresponding private key held by each. In this way, when saving and managing the file F, encryption is performed for each of the decryptable operators U. Even if an operator U leaks the private key, the damage caused by it can be minimized.

FIG. 7 is a functional block diagram showing an example of the functional configuration of the node terminal, the node server, and the user terminal of FIG. For the sake of simplification of the explanation, in the explanation of FIG. 7, only one node terminal 1, the node server 2, and the operator terminal 3 are shown. Further, since the functional configuration of the node server 2 shown in FIG. 7 is the same as the functional configuration of each of the node servers 2 shown in FIG. 4 described above, the illustration of the functional block and its description thereof are omitted.

In the CPU 11 of the node terminal 1 shown in FIG. 7, in addition to the hardware key detection unit 111, the personal authentication unit 112, the node management unit 113, the file acquisition unit 114, and the file management unit 115 described above, the update management unit 116 functions. do.

The update management unit 116 manages the updates of the node terminal 1 and the operator terminal 3. Specifically, the update management unit 116 confirms the existence of update information for each of the node terminal 1 and the operator terminal 3 at a predetermined timing (for example, when the node terminal 1 is started), and updates as necessary. Performs processing control. As a result, the node terminal 1 and the operator terminal 3 are automatically updated, so that it becomes easy to add or update various applications using the blockchain BC at any time.

In addition, various variations can be adopted for the functional configuration of the node terminal 1. For example, it may have a functional configuration that does not include the distributed file system management unit 122. In this case, the file management unit 115 transmits the file F acquired by the file acquisition unit 114 to the node server 2 via the communication unit 19. The node server 2 that has received the file F causes the distributed file system management unit 222 of the file management unit 213 to manage the file F. The distributed file system management unit 222 acquires the hash value of the file F and transmits the information including the hash value to the file management unit 115 of the node terminal 1.

In the CPU 31 of the operator terminal 3, the file acquisition unit 311, the key management unit 312, the encryption unit 313, and the transmission control unit 314 function. Further, a private key DB 360 is provided in one area of the storage unit 38 of the operator terminal 3.

The file acquisition unit 311 acquires the file F to be saved in the blockchain BC by the operator U.

The key management unit 312 stores and manages the public key for encryption and the public key for signature in the blockchain BC. Further, the key management unit 312 stores and manages the private keys of the encryption public key and the signature public key in the private key DB 360.
When the file F is encrypted or managed, the key management unit 312 acquires the encryption public key and the signature public key stored in the blockchain BC.

The encryption unit 313 encrypts the file F acquired by the file acquisition unit 311. Specifically, the encryption unit 313 encrypts the file F using the encryption public key acquired by the key management unit 312.
Further, the encryption unit 313 accepts the record of the signature of the encrypted file F. Specifically, the encryption unit 313 accepts a signature record (electronic signature) by the operator U using the private key corresponding to the signature public key acquired by the key management unit 312. The other operator U who shared the file F can confirm that the signature of the file F was made by the operator U by using the signing public key. In this service, since the public key for signature is recorded in the blockchain BC, another operator U can easily verify that the signature is recorded by the operator U.

The transmission control unit 314 executes control to transmit the file F for which the encryption and the signature record have been received by the encryption unit 313 to the node terminal 1. As a result, all the files F transmitted from the operator terminal 3 are encrypted.

Summarizing the above, the storage and management of the file F is performed via the node terminal 1 arranged separately from the operator terminal 3 operated by the operator U. Further, the node terminal 1 can manage updates of the node terminal 1 itself and the operator terminal 3. As a result, the operator 3 can reduce the labor required for setting and the like in using this service.

The embodiment of the information processing system to which the present invention is applied has been described above. However, the embodiment to which the present invention is applied may be, for example, as follows.

In the above-described embodiment, the service is provided to a predetermined organization (for example, a company) by a service provider (not shown). That is, for example, a predetermined organization (for example, a company) has an initial cost (for example, hundreds of thousands to millions of yen) according to the number of operators U, the number of node terminals 1 and node servers 2, etc., and on the cloud C. This service may be provided in consideration of a running fee (for example, several hundred thousand yen) for a predetermined period of the node server 2 of the above.
However, this service is not limited to those provided to a predetermined organization (for example, a company). That is, for example, it may be an individual who has a contract with a service provider.

Further, in the present embodiment, five node terminals 1-1 to 1-5 are transferred from the service provider to a predetermined organization (for example, a company), but the present invention is not particularly limited to this. That is, for example, the node terminal 1 in which the application related to this service is pre-installed may be sold, and the individual who purchased the node terminal 1 may be provided with this service.

Further, in the above-described embodiment, the node terminals 1-1 to 1-5 are connected to the cloud C via the dedicated lines LL-1 to LL-5, respectively, so that they are connected to the cloud C as one node. It was supposed to work. Further, in the above-described embodiment, the node terminal 1 can execute a part or all of the predetermined processing related to the provision of the service.
Specifically, for example, in the description of FIG. 1, the node server 2 has executed step ST3 of the storage process. Further, in the description of FIG. 4, the node terminal 1 has executed step ST3 of the saving process.
However, the node terminal 1 and the node server 2 may perform a process such as acting as a part of a predetermined process related to the provision of this service. Specifically, for example, the node terminal 1 may perform a part of the process in which the blockchain management unit 221 of the node server 2 calculates the hash value of the new block B3. As a result, the amount of calculation of the node server 2 can be reduced by utilizing the computational resources of the node terminal 1.
Further, for example, the data to be stored in the file storage unit 260 of the node server 2 can be distributed and stored in the file storage unit 160 of the node terminal 1. As a result, the information processing system related to this service can manage a large number of files without consuming the storage unit 28 of the node server 2.

Further, in the above-described embodiment, when the operator U who operates the node terminal 1-1 is authenticated, the blockchain management function is exhibited at the node terminal 1-1, but the blockchain at the node terminal 1 The conditions for whether or not the management function is exhibited are not limited to this. That is, for example, even when the operator U who operates the plurality of node terminals 1 is authenticated, the blockchain management function may not be exhibited at the node terminals 1-1. Further, for example, when the operator U who operates the plurality of node terminals 1 is not authenticated and the hardware key IDH is detected, only a part of the blockchain management functions is executed at the node terminal 1. May be done. Summarizing the above, it is not necessary for the blockchain management function to be exhibited in all of the plurality of node terminals 1.

As described with reference to FIG. 6, the worker terminal 3 can bring the file F into a state managed by the network related to the blockchain by cooperating with the node terminal 1 and the node server 2. ..
Here, as described in the above-described embodiment, the "blockchain management function" means that when one or more data is instructed to be saved, the one or more data is stored by each of the nodes constituting the network related to the blockchain. It is a function to make it managed by the network. Further, step ST2 for moving the file and step ST3 for saving processing in FIG. 1 are examples of the blockchain management function.
Therefore, since the worker terminal 3 has a blockchain management function, it can be grasped as an example of a node of the network related to the blockchain.

Further, in the above-described embodiment, in the description of FIG. 1, the node terminal 1-1 operated by the operator U has been described as exchanging various information with the node server 2-1. However, the present invention is particularly limited to this. Not done. That is, for example, the node terminal 1-1 may exchange various information with a plurality of node servers 2 (for example, a part or all of the node servers 2-1 to 2-4).

Further, in the above-described embodiment, in the description of FIG. 2, the node servers 2-1 to 2-m are assumed to be arranged on the cloud C, but the present invention is not particularly limited to this. That is, for example, a part or all of the plurality of node servers 2 is arranged not on the cloud C but on a predetermined network (for example, a local area network or an intranet) including the node terminal 1 and the node server 2. May be good. That is, the node server 2 may be an on-premises server installed in a predetermined organization (for example, a company) to which the operator U belongs, instead of being installed on the cloud C.

As described above, each of the node terminal 1, the node server 2, and the operator terminal 3 can exert (execute) a part or all of a predetermined function (process) related to the provision of this service. In summary, the configurations of the node terminal 1, the node server 2, the operator terminal 3, and the like can be classified as follows.
Hereinafter, the classification of the information processing devices (node terminal 1, node server 2, operator terminal 3, etc.) will be described with reference to FIGS. 4 and 7.

The node terminal 1 in which the blockchain management unit 121 and the distributed file system management unit 122 in FIG. 4 function, and the node server 2 in which the blockchain management unit 221 and the distributed file system management unit 222 function are examples of full nodes. That is, a full node is an information processing device that exhibits at least a function of extracting various information related to file F and managing it as a part of a block, and a function of encrypting and dividing and managing the entire data of file F. ..

Information that has more computational resources (for example, CPU 11) for calculating the hash value and the like and a storage unit (for example, storage unit 18) for storing the encrypted and divided file F as compared with the light node described later. The processing device is adopted as a full node.
Therefore, the service provider (not shown) provides the operator U with the node terminal 1 which is a full node to extract various information about the file F in the entire service and manage the functions and files as a part of the block. It is possible to increase the number of information processing devices that share the function of encrypting and dividing and managing the entire F data itself. That is, it becomes easy for a service provider (not shown) to scale out in this service.

Although not shown, a terminal in the node terminal 1 of FIG. 7 in which the node management unit 113 functions and the blockchain storage unit 150 and the file storage unit 160 do not function is an example of a write node. That is, the write node is a function of extracting various information about the file F via the terminal (for example, the node terminal 1) itself and managing it as a part of a block, or encrypting and dividing the entire data of the file F itself. An information processing device that exerts a management function and does not store a blockchain BC or a file F by the terminal itself.

The write node does not need to have a computational resource (for example, CPU 11) for calculating a hash value or the like, or a storage unit (for example, a storage unit 18) for storing an encrypted and divided file F. Therefore, the operator U can use this service via a light node (information processing device) which is relatively low cost.
Further, since the write node does not store the blockchain BC or the file F, even if the write node is stolen, the recorded data is not directly stolen and the confidentiality of the file F is ensured.

In addition, a distributed file system node may be prepared separately. That is, the distributed file system node has a storage unit (for example, a storage unit 18) for storing the encrypted and divided file F, and can store various data in cooperation with the write node and the full node. can.
Not limited to the above example, an information processing device having various functional blocks or a part of a storage unit may be connected to the network related to this service.

Further, in the above-described embodiment, the hardware key IDH of FIG. 1 is assumed to be able to acquire predetermined information by the node terminal 1, but what kind of hardware the hardware key IDH is is not particularly limited. .. That is, the hardware key is sufficient as long as it is the hardware for exerting the blockchain management function on the node terminal 1. That is, the hardware key IDH is sufficient if it can detect that the operator U holds the hardware key IDH.
Specifically, for example, the hardware key IDH may be a flash memory having a USB (Universal Social Bus) standard connector or a card having an RFID (Radio Frequency Identification) function. That is, the hardware key IDH may be directly connected to the node terminal 1, may be connected by wire, or may be connected wirelessly. Furthermore, the hardware key IDH may be hardware capable of displaying a predetermined identifier (for example, a sequence of one-time passwords or a two-dimensional bar code). In this case, for example, the node terminal 1 can detect the hardware key IDH by reading a predetermined identifier related to the hardware key IDH via the input unit 17 (for example, a keyboard or an imaging device).

Further, in the above-described embodiment, the private key corresponding to each of the encryption public key and the signature public key is stored in the operator terminal 3, respectively.
That is, when the private key corresponding to each of the encryption public key and the signature public key is stored in the operator terminal 3, the encryption public key and the signature public key are stored in the operator terminal 3, respectively. Since the private key corresponding to is stored, a different private key can be adopted for each of the operator terminals 3. As a result, in the storage and management of the file F, it is possible to individually manage the history of each of the operator terminals 3. This is suitable in an environment where there is little need to take out the operator terminal 3, for example, a desktop personal computer for an office.
However, the private keys corresponding to the encryption public key and the signature public key are not stored in the operator terminal 3 respectively, but may be stored in the node terminal 1 respectively. In this case, based on the operation of the operator terminal 3 by the operator U, the file F can be saved and managed by using the blockchain BC as in the above-described embodiment via the node terminal 1. Further, the operator terminal 3 does not store the private key corresponding to each of the encryption public key and the signature public key. Therefore, even if the operator U takes out the operator terminal 3, there is no risk of leaking the private key corresponding to each of the encryption public key and the signature public key. When only one set of private key corresponding to each of the public key for encryption and the public key for signing is stored in the node terminal 1, the history of each of the plurality of operator terminals 3 locally connected to the node terminal 1 Can not be managed individually, but for example, the storage and management of the file F can be managed for each node terminal 1. Therefore, by arranging the node terminals 1 for each group (for example, department) in the office, storage and management may be performed for each group.
A plurality of sets of private keys corresponding to the encryption public key and the signature public key may be stored in the node terminal 1 and may be used as appropriate.

Further, in the description of the above-described embodiment, it has been explained that this service is suitable for managing documents and a large amount of data. However, for example, it is applied to still image, moving image, and audio data in addition to documents. Can be done. Specifically, for example, this service can store and manage moving images, voices, and call histories of Web conferences and the like as a file F using a blockchain BC.
As a result, the contents of the proceedings in the Web conference or the like can be saved and managed without falsification.

Further, for example, the above-mentioned series of processes can be executed by hardware or software.
In other words, the functional configuration of FIG. 4 is merely an example and is not particularly limited.
That is, it suffices if the information processing system is provided with a function capable of executing the above-mentioned series of processes as a whole, and what kind of functional block is used to realize this function is not particularly limited to the example of FIG. Further, the location of the functional block is not particularly limited to FIG. 4, and may be arbitrary. For example, the functional block of the node terminal 1 may be transferred to the node server 2 or the like.
Further, one functional block may be configured by a single piece of hardware, a single piece of software, or a combination thereof.

Further, for example, when a series of processes are executed by software, a program constituting the software is installed on a computer or the like from a network or a recording medium.
The computer may be a computer embedded in dedicated hardware.
Further, the computer may be a computer capable of executing various functions by installing various programs, for example, a general-purpose smartphone or a personal computer in addition to a server.

Further, for example, a recording medium containing such a program is not only composed of a removable medium (not shown) distributed separately from the device main body in order to provide the program to the operator U, but is also preliminarily incorporated in the device main body. It is composed of a recording medium or the like provided to the operator U in this state.

In the present specification, the steps for describing a program recorded on a recording medium are not necessarily processed in chronological order, but also in parallel or individually, even if they are not necessarily processed in chronological order. It also includes the processing to be executed.
Further, in the present specification, the term of the system means an overall device composed of a plurality of devices, a plurality of means, and the like.

In other words, the information processing system to which the present invention is applied can take various embodiments having the following configurations.

That is, the information processing system to which the present invention is applied (for example, the information processing system of FIGS. 1, 2 and 4) is
A cloud (for example, FIG. 1) that functions as a node belonging to a network related to a blockchain (for example, a network including node terminals 1-1 to 1-5 and node servers 2-1 to 2-4 in FIG. 1). And one or more first-class information processing devices (for example, the node server 2 in FIGS. 1, 2 and 4) on the cloud C in FIG.
One or more type 2 information processing that is connected to the cloud via a dedicated line (for example, the dedicated line LL of FIGS. 1, 2 and 4) and functions as a node belonging to the network related to the blockchain. Devices (eg, node terminals 1 in FIGS. 1, 2 and 4) and
Including
When each of the nodes constituting the network related to the blockchain is instructed to save one or more data (for example, an instruction by the operator U by operating a predetermined user interface), the one or more It exerts a blockchain management function that puts data in a state managed by the network.

As a result, the information processing system provided with the first-class information processing device on the cloud and the second information processing device connected to the cloud via a dedicated line as nodes belonging to the network related to the blockchain blocks the information. The chain management function is demonstrated.
That is, for example, not only the conventional first information processing device on the cloud but also the second information processing device connected to the cloud via a dedicated line functions as a node, thereby relating to the information processing of the first information processing device. The load can be reduced. That is, it is possible to handle a large amount of data and prevent leakage of the data, and improve the convenience related to them.

Further, a hardware key (for example, the hardware key IDH in FIG. 1) for exerting the blockchain management function in a predetermined one of the above-mentioned one or more type 2 information processing devices.
Can be further prepared.

As a result, for example, when the second information processing device connected to the cloud via a dedicated line also functions as a node, it is possible to evaluate whether or not the second information processing device is reliable based on the hardware key. can. As a result, the strength of security of the information processing system according to the present invention is improved.

Further, the one or more data managed as a result of the blockchain management function can be restricted from accessing a person other than the person who has instructed to save the one or more data.

As a result, only the person who has instructed to save one or more data can access (for example, browse) one or more data managed as a result of the blockchain management function. As a result, the strength of security of the information processing system according to the present invention is improved.

Further, a third-class information processing device connected to the second-class information processing device is further provided.
The third-class information processing device can encrypt the data and record a predetermined signature on the encrypted data by using a predetermined public key stored in the blockchain. can.

As a result, the data transmitted from the type 3 information processing device to the type 2 information processing device is encrypted. Therefore, in the type 2 information processing device, only the encrypted data exists unless new data is created by the type 2 information processing device. As a result, even if the data stored in the type 2 information processing device or the type 2 information processing device itself is stolen, the confidentiality of the data can be ensured.

In addition, the second-class information processing device is
Confirmation of the presence or absence of update information of the own machine and the third-class information processing device is performed at a predetermined timing, and when the predetermined conditions are satisfied, the update information is acquired and the update process of the own machine and the third-class information processing device is performed. Can be further controlled.

As a result, the type 2 information processing device and the type 3 information processing device are automatically updated, so that it becomes easy to add or update various applications using the blockchain at any time.

1,1-1 to 1-5 ... Node terminal, 11 ... CPU, 111 ... Hardware key detection unit, 112 ... Personal authentication unit, 113 ... Node management unit, 114 ...・ File acquisition unit, 115 ・ ・ ・ File management department, 116 ・ ・ ・ Update management department, 121 ・ ・ ・ Blockchain management department, 122 ・ ・ ・ Distributed file system management department, 18 ・ ・ ・ Storage unit, 150 ・ ・-Blockchain storage unit, 160 ... file storage unit, 19 ... communication unit, 2,2-1 to 2-4 ... node server, 21 ... CPU, 211 ... node management unit, 212 ... File acquisition unit, 213 ... File management unit, 221 ... Blockchain management unit, 222 ... Distributed file system management unit, 28 ... Storage unit, 250 ... Blockchain storage unit 260 ... File storage unit, 29 ... Communication unit, 31 ... CPU, 311 ... File acquisition unit, 312 ... Key management unit, 313 ... Encryption unit, 314 ... Transmission control unit 360 ... Private key 360, LL, LL-1 to LL-5 ... Dedicated line, IDH ... Hardware key, IDC ... Identification card, BC, BC-1 to BC- 4 ... Blockchain, FS, FS-1 to FS-4 ... File system, F ... File, D ... Folder, C ... Cloud

Claims (6)

1. One or more first-class information processing devices on the cloud that function as nodes belonging to the blockchain network, respectively.
   One or more type 2 information processing devices that are connected to the cloud via a dedicated line and function as nodes belonging to the network related to the blockchain, respectively.
   Including
   When each of the nodes constituting the network related to the blockchain is instructed to save one or more data, a blockchain management function for putting the one or more data in a state managed by the network is provided. Demonstrate,
   Information processing system.
2. A hardware key for exerting the blockchain management function in a predetermined one of the one or more type 2 information processing devices.
   The information processing system according to claim 1, further comprising.
3. The one or more data managed as a result of the blockchain management function is subject to access restrictions to persons other than the person who has instructed to save the one or more data.
   The information processing system according to claim 1 or 2.
4. A third-class information processing device connected to the second-class information processing device is further provided.
   The third-class information processing device uses a predetermined public key stored in the blockchain to encrypt the data and record a predetermined signature on the encrypted data.
   The information processing system according to any one of claims 1 to 3.
5. The second-class information processing device is
   Confirmation of the presence or absence of update information of the own machine and the third-class information processing device is performed at a predetermined timing, and when the predetermined conditions are satisfied, the update information is acquired and the update process of the own machine and the third-class information processing device is performed. Further control and control,
   The information processing system according to claim 4.
6. On the computer
   A type 2 information processing device connected via a dedicated line to a cloud in which one or more type 1 information processing devices each function as a node belonging to a node of a network related to a blockchain exists. In a state of functioning as a node belonging to the node of the network related to the blockchain.
   When it is instructed to save one or more data, it includes a process of exerting a blockchain management function that puts the one or more data in a state managed by the network related to the blockchain.
   A program that executes control processing.

Images