Terminal device, management system, processing method and program

By using a blockchain to link data across devices and detecting tampering, the system addresses data integrity issues in IoT systems, enhancing reliability and reducing operational risks while minimizing management costs.

JP7582313B2Active Publication Date: 2024-11-13NEC CORP
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2022544995
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-08-27
Publication Date
2024-11-13
Estimated Expiration
2040-08-27

AI Technical Summary

Technical Problem

Existing management systems struggle with ensuring data integrity and reliability in IoT systems by preventing tampering with operation logs and setting values, particularly in scenarios where data is collected from multiple scattered devices, leading to increased management costs and operational risks.

Method used

A terminal device connected to a network maintains a blockchain that links data generated by each device, adding new data or hash values when a new device joins, and includes mechanisms to detect tampering by comparing data across devices, disconnecting from the server if tampering is detected, and invalidating the data.

Benefits of technology

Enhances data reliability by preventing tampering and reducing management costs through centralized data management, ensuring secure operation and reducing operational risks in IoT systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582313000001
    Figure 0007582313000001
  • Figure 0007582313000002
    Figure 0007582313000002
  • Figure 0007582313000003
    Figure 0007582313000003
Patent Text Reader

Abstract

Provided are a terminal device, a data management device, a management system, a processing method, a data management method, a management method, and a non-transitory computer-readable medium having program stored thereon, with which it is possible to improve reliability. A terminal device (10A) is connected to a network (NW) in conjunction with other terminal devices (10B) to (10D), and, in conjunction with the other terminal devices (10B) to (10D), holds a blockchain (BC) in which data generated by each terminal device (10A) to (10D), or hash values of said data, are linked as a block, wherein, if a new terminal device (10E) is to be added to the network (NW), the terminal device (10A) adds new data generated by the new terminal device (10E), or a hash value of the new data, to the blockchain (BC) in conjunction with the other terminal devices (10B) to (10D).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a terminal device, a data management device, a management system, a processing method, a data management method, a management method, and a non-transitory computer-readable medium having a program stored thereon. [Background technology]

[0002] Patent documents 1 and 2 describe electronic data exchange that uses evidence registered in a blockchain to ensure the reliability of data. Proof The system is described in the document. It is also a widely known technology to realize storage that makes data difficult to tamper with by storing the data in a distributed manner among multiple third parties. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6340107 [Patent Document 2] Patent No. 6480528 Summary of the Invention [Problem to be solved by the invention]

[0004] The management systems in Patent Documents 1 and 2 can guarantee the authenticity of devices by managing traceability information at the time of manufacture using a blockchain, but do not take into consideration the prevention of tampering with logs or settings during operation. Even if there is an error in the settings, it is difficult to notice abnormal behavior if the whitelist, etc. is tampered with as if the settings were correct. In addition, if the operation log is tampered with, it is difficult to take corrective action even if information is sent to an unauthorized connection destination.

[0005] In addition, the systems in Patent Documents 1 and 2 can realize storage that is difficult to tamper with by distributing data across multiple third parties, but they require data to be transmitted via specific access points, making them unsuitable for collecting data from devices scattered in multiple locations, such as in Internet of Things (IoT) systems.

[0006] Furthermore, in the systems of Patent Documents 1 and 2, if operation logs and setting value data of edge devices are stored for each tenant and each customer, management costs will increase and there will be a risk of operation suspension in the event of a disaster or large-scale failure.In addition, there will be a risk of data loss if the service provider is unable to continue its business.

[0007] When an IoT system is provided as a service, various actors are involved in the operational process, which increases the risk that someone may intentionally tamper with data.

[0008] The object of the present disclosure has been made to solve such problems, and is to provide a terminal device, a data management device, a management system, a processing method, a data management method, a management method, and a non-transitory computer-readable medium on which a program is stored, which can improve reliability. [Means for solving the problem]

[0009] A terminal device according to the present disclosure is connected to a network together with other terminal devices, and holds a blockchain together with the other terminal devices in which data generated by each terminal device or hash values ​​of the data are linked into blocks, and when a new terminal device is added to the network, new data generated by the new terminal device or the hash value of the new data is added to the blockchain together with the other terminal devices. Effect of the Invention

[0010] According to the present disclosure, it is possible to provide a terminal device, a data management device, a management system, a processing method, a data management method, a management method, and a non-transitory computer-readable medium on which a program is stored, which can improve reliability. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram illustrating a plurality of terminal devices and a network in a management system according to an embodiment. [Diagram 2] FIG. 1 is a diagram illustrating a blockchain in a management system according to an embodiment. [Diagram 3] FIG. 2 is a configuration diagram illustrating a terminal device in a management system according to an embodiment. [Figure 4] 1 is a flowchart illustrating a management method for adding a new terminal device in a management system according to an embodiment. [Diagram 5] 1 is a block diagram illustrating a state in which a new terminal device is added in a management system according to an embodiment. FIG. [Figure 6] 11 is a flowchart illustrating a processing method of a terminal device when a new terminal device is added in the management system according to the embodiment. FIG. [Figure 7] A flowchart illustrating a method for having each terminal device hold a blockchain in a management system according to an embodiment. [Figure 8] 1 is a flowchart illustrating a management method for detecting tampering in a management system according to an embodiment. [Figure 9] 11 is a flowchart illustrating a processing method of a terminal device that detects tampering in a management system according to an embodiment. [Figure 10] 1 is a block diagram illustrating a plurality of terminal devices, a data management device, and a network in a management system according to a first embodiment. [Figure 11] 2 is a block diagram illustrating a terminal device in the management system according to the first embodiment. FIG. [Figure 12]4 is a block diagram illustrating a terminal device to be newly added in the management system according to the first embodiment. FIG. [Figure 13] 2 is a block diagram illustrating a data management device in the management system according to the first embodiment. FIG. [Figure 14] 4 is a sequence diagram illustrating a management method for adding a new terminal device in the management system according to the first embodiment. FIG. [Figure 15] 4 is a block diagram illustrating a state in which a new terminal device is added in the management system according to the first embodiment. FIG. [Figure 16] 1 is a block diagram illustrating a data management device to which digitally signed data generated by a new terminal device has been added in the management system according to the first embodiment. FIG. [Figure 17] 4 is a flow chart illustrating a processing method for a new terminal device to be added in the management system according to the first embodiment. FIG. [Figure 18] 4 is a flow chart illustrating a processing method of a terminal device on the network side in the management system according to the first embodiment. [Figure 19] 4 is a flow chart illustrating a data management method of the data management device in the management system according to the first embodiment. [Figure 20] 2 is a block diagram illustrating a terminal device and a network that detects tampering in the management system according to the first embodiment. FIG. [Figure 21] 4 is a sequence diagram illustrating a management method for detecting tampering in the management system according to the first embodiment. FIG. [Figure 22] 11 is a flowchart illustrating a processing method of a terminal device that detects tampering in a management system according to an embodiment. [Figure 23] 4 is a flowchart illustrating a method for detecting tampering in the management system according to the first embodiment. FIG. [Figure 24] 1 is a block diagram illustrating a terminal device that restores data, other terminal devices, a data management device, a server device, and a network in a management system according to a first embodiment. [Diagram 25] 2 is a block diagram illustrating a data management device in the management system according to the first embodiment. FIG. [Figure 26] 4 is a sequence diagram illustrating a management method for restoring data in the management system according to the first embodiment. FIG. [Figure 27] 11 is a flowchart illustrating a processing method of a terminal device that restores data in a management system according to an embodiment. [Figure 28] 4 is a flowchart illustrating a data restoration processing method in the management system according to the first embodiment. FIG. [Figure 29] 4 is a flowchart illustrating a data management method of a data management device that restores data in the management system according to the first embodiment. [Diagram 30] FIG. 11 is a block diagram illustrating a plurality of terminal devices, a data management device, and a network in a management system according to a second embodiment. [Diagram 31] FIG. 11 is a block diagram illustrating a terminal device in a management system according to a second embodiment. [Diagram 32] FIG. 11 is a block diagram illustrating a data management device in a management system according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] For clarity of explanation, the following description and drawings are omitted and simplified as appropriate. In addition, in each drawing, the same elements are given the same reference numerals, and duplicate explanations are omitted as necessary.

[0013] <Overview of the embodiment> An overview of a management system according to an embodiment will be described. FIG. 1 is a block diagram illustrating a plurality of terminal devices and a network in a management system according to an embodiment. As shown in FIG. 1, the management system 1 includes a plurality of terminal devices 10A to 10D and a network NW to which the plurality of terminal devices 10A to 10D are connected. For example, the terminal device 10A is connected to the network NW together with a plurality of other terminal devices 10B to 10D. Each of the terminal devices 10A to 10D is connected to the network NW in a communicable state by a wireless or wired communication line. Each of the terminal devices 10A to 10D may be connected in a constantly communicable state, or may be connected when transmitting and receiving information.

[0014] Each of the terminal devices 10A to 10D may be connected to the network NW in a peer-to-peer manner. Each of the terminal devices 10A to 10D holds a blockchain BC in which data or hash values ​​of data generated by each of the terminal devices 10A to 10D are linked as blocks. The blockchain BC held by each of the terminal devices 10A to 10D is, for example, the same. When a new terminal device 10E is added to the network NW, each of the terminal devices 10A to 10D adds new data DE generated by the new terminal device 10E or a hash value HE of the new data DE to the blockchain BC.

[0015] Among the multiple terminal devices 10A to 10D, one terminal device, for example, the terminal device 10A, is focused on. Then, the terminal device 10A holds the blockchain BC together with the other terminal devices 10B to 10D. When a new terminal device 10E is added to the network NW, the terminal device 10A adds new data DE generated by the new terminal device 10E or a hash value HE of the new data DE to the blockchain BC together with the other terminal devices 10B to 10D. Below, after explaining <blockchain>, we will explain <overview of terminal devices>. After that, we will explain <overview of operation> of the management system 1 and the terminal devices 10A to 10D.

[0016] <Blockchain> Fig. 2 is a diagram illustrating a blockchain BC in the management system 1 according to the embodiment. As shown in Fig. 2, the blockchain BC is formed by linking data or hash values ​​HA to HD of data generated by each of the terminal devices 10A to 10D as blocks BRA to BRD. The data includes log data such as operation logs acquired by each of the terminal devices 10A to 10D and setting data related to setting values ​​such as whitelists. Thus, each of the terminal devices 10A to 10D manages the log data and hash values ​​HA to HD of the setting data on the public blockchain BC.

[0017] In addition, in FIG. 2, each block BRA-BRD constituting the block chain BC is shown to include hash values ​​HA-HD, but each block BRA-BRD may include data, not limited to hash values ​​HA-HD. Therefore, the object managed by the block chain BC may be data itself, not limited to hash values ​​HA-HD. Also, in FIG. 2, only four blocks BRA-BRD are shown, but it may be three or less, or five or more.

[0018] For example, each of the terminal devices 10A to 10D is an edge device. In that case, the blockchain BC is formed with the edge devices connected to the service as nodes. The blockchain BC holds the cache value of the data of each node. Specifically, for example, the blockchain BC links a block BRA, a block BRB, a block BRC, and a block BRD in this order. The block BRA includes a hash value HA of the data generated by the terminal device 10A. The block BRB includes a hash value HB of the data generated by the terminal device 10B. The block BRC includes a hash value HC of the data generated by the terminal device 10C. The block BRD includes a hash value HD of the data generated by the terminal device 10D. In this case, the block BRB includes the hash value HA as a cache value. The block BRC includes the hash value HB as a cache value. The block BRD includes the hash value HC as a cache value.

[0019] The blockchain BC may already be constructed. A hash value of the data of the edge device may be stored on the constructed blockchain BC, or the data of the edge device itself may be stored on the constructed blockchain BC.

[0020] <Terminal device overview> Next, the terminal device 10 will be described. Any one of the terminal devices 10A to 10E is called the terminal device 10. In addition, one or more of the terminal devices 10A to 10E may be collectively called the terminal device 10. When any one of the terminal devices 10A to 10E is specified, the terminal device 10 is indicated by adding the reference number of any one of the terminal devices 10A to 10E. The terminal device 10 may be configured as hardware including a microcomputer including a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), an interface unit (I / F), and the like. The CPU performs processes such as calculation processing, duplication processing, verification processing, and control processing. The ROM stores programs such as processing programs and control programs executed by the CPU. The RAM stores various data such as data and hash values. The interface unit (I / F) inputs and outputs signals and data to and from the outside. The CPU, ROM, RAM, and interface unit are connected to each other via a data bus or the like.

[0021] Fig. 3 is a configuration diagram illustrating the terminal device 10 in the management system 1 according to the embodiment. As shown in Fig. 3, the terminal device 10 includes a generating and holding unit 11, a calculation unit 12, a duplication unit 13, a transmission / reception unit 14, a holding unit 15, an additional verification unit 16, and a control unit 17. The generating and holding unit 11, the calculation unit 12, the duplication unit 13, the transmission / reception unit 14, the holding unit 15, the additional verification unit 16, and the control unit 17 each have functions as a data generating and holding means, a hash value calculation means, a data and hash value duplication means, a data and hash value transmission / reception means, a blockchain holding means, a hash value additional verification means, and a control means for the terminal device 10.

[0022] The generating and holding unit 11 generates data and holds the generated data as held data. For example, the generating and holding unit 11 generates and holds log data such as an operation log. The generating and holding unit 11 also holds setting data related to setting values ​​such as a whitelist.

[0023] The calculation unit 12 calculates a hash value of the generated data. The duplication unit 13 duplicates at least one of the data and the hash value.

[0024] The transmission / reception unit 14 transmits at least one of the copied data and the hash value to the network NW as transmission data and transmission hash value. The transmission / reception unit 14 also receives at least one of the data and the hash value from another terminal device 10 as reception data and reception hash value.

[0025] The holding unit 15 holds a block chain BC in which data or hash values ​​HA to HD of data generated by the terminal devices 10A to 10D are linked as blocks.

[0026] The additional verification unit 16 adds the received data or the received hash value to the blockchain BC. When a new terminal device 10 is added to the network NW, the additional verification unit 16 adds new data DE generated by the new terminal device 10 or a hash value HE of the new data DE to the blockchain BC.

[0027] Furthermore, the additional verification unit 16 detects tampering with the held data by comparing the held data or the hash value of the held data held by the generating and holding unit 11 with the transmission data or the transmission hash value included in the blockchain BC held by another terminal device 10. Specifically, for example, the additional verification unit 16 of the terminal device 10A detects tampering with the held data of the terminal device 10A by comparing the held data or the hash value of the held data held in the generating and holding unit 11 of the terminal device 10A with the transmission data or the transmission hash value in the blockchain BC held in the terminal device 10B. Here, the transmission data and the transmission hash value are those transmitted by the terminal device 10A to the terminal device 10B.

[0028] When the additional verification unit 16 detects tampering, the control unit 17 disconnects the connection to the server device that provides the service on the network NW. When the control unit 17 detects tampering, the control unit 17 invalidates the held data.

[0029] <Overview of operation> Next, an overview of the addition of a terminal device and the detection of tampering will be described as operations of the management system 1 of this embodiment. Details of each operation will be described in embodiment 1. First, an overview of the addition of a terminal device will be described.

[0030] <Overview of adding terminal devices> First, an overview of adding a terminal device will be described with respect to a management method of the management system 1. Fig. 4 is a flow chart illustrating an example of a management method for adding a new terminal device 10 in the management system 1 according to the embodiment.

[0031] 4, each of the terminal devices 10A to 10D is caused to hold a block chain BC. Specifically, for example, a block chain BC in which data or hash values ​​HA to HD of data generated by each of the terminal devices 10A to 10D in a network NW to which the multiple terminal devices 10A to 10D are connected are linked as blocks is held in each of the terminal devices 10A to 10D.

[0032] Next, as shown in step S12, when a new terminal device 10E is added to the network NW, new data DE or a hash value HE of the new data DE generated by the new terminal device 10E is added to the blockchain BC.

[0033] FIG. 5 is a block diagram illustrating a state in which a new terminal device 10E is added to the management system 1 according to the embodiment. In the figure, the peer-to-peer network NW is indicated by an ellipse. As shown in FIG. 5, the new terminal device 10E is added to the network NW to which multiple terminal devices 10A to 10D are connected. New data DE or a hash value HE of the new data DE is added to the blockchain BC held by each of the terminal devices 10A to 10D. The new terminal device 10E comes to hold the blockchain BC held by each of the terminal devices 10A to 10D.

[0034] Next, a processing method of the terminal device 10A in an overview of adding a terminal device will be described. Fig. 6 is a flow chart illustrating a processing method of the terminal device 10A when adding a new terminal device 10E in the management system 1 according to the embodiment. Of the terminal devices 10A to 10D, the description focuses on the terminal device 10A. The same applies to the terminal devices 10B to 10D.

[0035] As shown in step S21 of Fig. 6, the blockchain BC is held together with the other terminal devices 10B to 10D. Specifically, the blockchain BC in the network NW to which the terminal devices 10B to 10D are connected is held in a specific terminal device 10A together with the other terminal devices 10B to 10D.

[0036] Next, as shown in step S22, when a new terminal device 10E is added to the network NW, new data DE generated by the new terminal device 10E or a hash value HE of the new data DE is added to the blockchain BC of a specific terminal device 10A together with the other terminal devices 10B to 10D.

[0037] Step S11 in Fig. 4 and step S21 in Fig. 6 may be performed as shown in Fig. 7 below. Fig. 7 is a flow chart illustrating a method for causing each of the terminal devices 10A to 10D to hold a blockchain BC in the management system 1 according to the embodiment.

[0038] As shown in FIG. 7, when the blockchain BC is stored in each of the terminal devices 10A to 10D, as shown in step S31, each of the terminal devices 10A to 10D is caused to generate data and store the generated data as retained data.

[0039] Next, as shown in step S32, the calculation unit 12 is caused to calculate a hash value of the generated data, and then, as shown in step S33, the duplication unit 13 is caused to duplicate at least one of the data and the hash value.

[0040] Next, as shown in step S34, the transmitter / receiver 14 is caused to transmit at least one of the copied data and the hash value to the network NW as transmission data and transmission hash value, and as shown in step S35, the transmitter / receiver 14 is caused to receive at least one of the data and the hash value from the other terminal devices 10B to 10D as reception data and reception hash value.

[0041] Next, as shown in step S36, the additional verification unit 16 is caused to add the received data or the received hash value to the block chain BC. In this manner, the block chain BC is held in the holding unit 15 of each of the terminal devices 10A to 10D.

[0042] <Overview of tamper detection> Next, an overview of tamper detection will be described as an operation of the management system 1. First, a management method of the management system 1 in the overview of tamper detection will be described. Fig. 8 is a flow chart illustrating a management method for detecting tampering in the management system 1 according to the embodiment.

[0043] As shown in step S41 in Fig. 8, the block chain BC is held in each of the terminal devices 10A to 10D. Step S41 is similar to step S11 in Fig. 4.

[0044] Next, as shown in step S42, for example, the terminal device 10A is made to detect tampering of the retained data. Specifically, the additional verification unit 16 of the terminal device 10A is made to detect tampering of the retained data by comparing the retained data or the hash value of the retained data retained by the terminal device 10A with the transmission data or the transmission hash value included in the blockchain BC retained by the other terminal devices 10B to 10D. The transmission data and the transmission hash value are those transmitted by the terminal device 10A to the other terminal devices 10B to 10D.

[0045] In order to generalize each of the terminal devices 10A to 10D, for example, if the terminal device 10A is the first terminal device and the terminal device 10B is the second terminal device, the multiple terminal devices 10A to 10D include at least the first terminal device and the second terminal device. In this case, the first terminal device detects tampering with the retained data by comparing the retained data or the hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain BC retained by the second terminal device.

[0046] Next, as shown in step S43, the terminal device 10A is caused to disconnect from the server device. Specifically, when the additional verification unit 16 of the terminal device 10A detects tampering, the control unit 17 of the terminal device 10A causes the terminal device 10A to disconnect from the server device that provides services on the network NW. The server device provides, for example, an operation management service, a security service, and the like.

[0047] Next, as shown in step S44, terminal device 10A is caused to invalidate the retained data. Specifically, when additional verification unit 16 of terminal device 10A detects tampering, control unit 17 of terminal device 10A invalidates the retained data retained in generating and retaining unit 11. For example, control unit 17 of terminal device 10A marks the tampered retained data with a flag or the like so that the data will not be used in subsequent processes.

[0048] Next, a processing method of the terminal device 10A in detecting tampering will be described below. Fig. 9 is a flow chart illustrating a processing method of the terminal device that detects tampering in the management system 1 according to the embodiment.

[0049] 9, the terminal device 10A is caused to hold the blockchain BC together with the other terminal devices 10B to 10D. Step S51 is similar to step S21 in FIG.

[0050] Next, as shown in step S52, the terminal device 10A is caused to detect tampering with the retained data. Specifically, the additional verification unit 16 of the terminal device 10A is caused to detect tampering with the retained data by comparing the retained data or the hash value of the retained data retained by the terminal device 10A with the transmission data or the transmission hash value included in the blockchain BC retained by the other terminal devices 10B to 10D.

[0051] Next, as shown in step S53, the terminal device 10A is caused to disconnect from the server device. Specifically, when the additional verification unit 16 of the terminal device 10A detects tampering, the control unit 17 of the terminal device 10A is caused to disconnect from the server device that provides the service on the network NW.

[0052] Next, as shown in step S54, the terminal device 10A is caused to invalidate the held data. Specifically, when the additional verification unit 16 of the terminal device 10A detects tampering, the control unit 17 of the terminal device 10A invalidates the held data held in the generating and holding unit 11.

[0053] Next, the effects of the present embodiment will be described. Since each terminal device 10A to 10D in the management system 1 holds the blockchain BC, the reliability of the management system 1 can be improved. Further, when a new terminal device 10E is added, each of the terminal devices 10A to 10D causes the blockchain BC to add new data DE or the hash value HE of the new data DE. Thereby, the reliability of the new data DE can be improved. Furthermore, since it is detected whether there is any falsification in the held data at predetermined intervals, the reliability of the held data can be improved.

[0054] <Embodiment 1> Next, the management system according to Embodiment 1 will be described. The management system of the present embodiment further includes a data management device. FIG. 10 is a block diagram illustrating a plurality of terminal devices, a data management device, and a network in the management system according to Embodiment 1. As shown in FIG. 10, the management system 100 includes a plurality of terminal devices 110A to 110D, a data management device 120, and a network NW.

[0055] In the management system 100, a plurality of terminal devices 110A to 110D and a data management device 120 are connected to the network NW. For example, the plurality of terminal devices 110A to 110D and the data management device 120 are connected to the network NW in a peer-to-peer manner. Therefore, each of the terminal devices 110A to 110D is connected to the data management device 120. In the figure, the peer-to-peer network NW is shown as an ellipse. A new terminal device 110E is added to the network NW.

[0056] Hereinafter, after describing the configurations of the <terminal device> and the <data management device>, the details of <I. Addition of a terminal device>, <II. Detection of falsification>, and <III. Restoration of data> will be described as the operations of the management system 100.

[0057] <Terminal device> Fig. 11 is a block diagram illustrating a terminal device 110 in the management system 100 according to the embodiment 1. Fig. 12 is a block diagram illustrating a terminal device 110E that is newly added in the management system 100 according to the embodiment 1.

[0058] As shown in FIG. 11, the terminal device 110 has a generating and holding unit 111, a calculating unit 112, a replicating unit 113, a transmitting and receiving unit 114, a holding unit 115, an additional verification unit 116, and a control unit 117, similar to the terminal device 10. The functions of each component in the terminal device 110 are similar to those of the terminal device 10. As in the case of the terminal device 10, any one of the terminal devices 110A to 110E may be referred to as the terminal device 110. In addition, one or more of the terminal devices 110A to 110E may be collectively referred to as the terminal device 110. When specifying any one of the terminal devices 110A to 110E, the terminal device 110 may be indicated by adding a reference symbol of any one of the terminal devices 110A to 110E. The terminal device 110 may have a hardware configuration similar to that of the terminal device 10.

[0059] Terminal device 110 further includes digital signature section 118 and decryption section 119. Digital signature section 118 and decryption section 119 function as a means for generating digitally signed data and a means for decrypting the digital signature.

[0060] Digital signature unit 118 generates digitally signed data by adding a digital signature formed using a private key unique to each terminal device 110 to the data generated by generating and holding unit 111. Here, the digital signature is, for example, a hash value of the data generated by generating and holding unit 111 encrypted using a private key unique to each terminal device 110.

[0061] The decryption unit 119 decrypts the digital signature using the public key. Here, the digital signature decrypted using the public key is, for example, a hash value of the data. The transmission / reception unit 114 transmits the digitally signed data generated by the digital signature unit 118 to the data management device 120, and receives the digitally signed data from the data management device 120.

[0062] 12, the new terminal device 110E does not hold a blockchain BC in the holding unit 115. Other configurations of the new terminal device 110E are similar to those of the terminal device 110.

[0063] <Data management device> The data management device 120 is connected to a network NW together with a plurality of terminal devices 110. As a result, the data management device 120 is connected to each terminal device 110 that holds the blockchain BC. The data management device 120 is, for example, a server that manages the operation of the management system 100. The data management device 120 may be configured, for example, as hardware including a microcomputer consisting of a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), an interface unit (I / F), and the like. The CPU performs processes such as calculation processing, duplication processing, verification processing, and control processing. The ROM stores programs such as processing programs and control programs executed by the CPU. The RAM stores various data such as data and hash values. The interface unit (I / F) inputs and outputs signals and data from the outside. The CPU, ROM, RAM, and interface unit are connected to each other via a data bus or the like.

[0064] FIG. 13 is a block diagram illustrating a data management device 120 in the management system 100 according to Embodiment 1. As shown in FIG. 13, the data management device 120 has a holding unit 121. The holding unit 121 functions as a means for holding data with an electronic signature. The data management device 120 holds data with electronic signatures SA to SD added thereto, where the electronic signatures SA to SD are formed using private keys unique to each of the terminal devices 110A to 110D, for the data DA to DD generated by each of the terminal devices 110A to 110D. Specifically, the holding unit 121 of the data management device 120 manages the data DA to DD such as log data and setting data generated by the generation and holding units 111 of each of the terminal devices 110A to 110D in a state where the electronic signatures SA to SD are added. The electronic signatures SA to SD are added to the data DA to DD by private keys unique to each of the terminal devices 110A to 110D.

[0065] When a new terminal device 110E is added to the network NW and new data DE generated by the new terminal device 110E or a hash value HE of the new data DE is added to the blockchain BC held by each of the terminal devices 110A to 110D, the data management device 120 adds the data with an electronic signature DE generated by the new terminal device 110E.

[0066] <I. Addition of Terminal Device> Next, as an operation of the management system 100 including the data management device 120, <I. Addition of Terminal Device> will be described. Since the blockchain BC is formed with edge devices connected to the service as nodes, the addition of the terminal device 110E is also an addition of a node. First, <I-1. Management Method of Management System> in the addition of the terminal device will be described. Then, <I-2. Processing Method of New Terminal Device>, <I-3. Processing Method of Terminal Device>, and <I-4. Data Management Method of Data Management Device> will be described.

[0067] <I-1. Management Method of Management System> First, a management method of the management system 100 in adding the terminal device 110E will be described. FIG. 14 is a sequence diagram illustrating a management method for adding a new terminal device 110E in the management system 100 according to Embodiment 1. As shown in step S101 of FIG. 14, the new terminal device 110E added to the management system 100 calculates a hash value HE from the data DE. Specifically, the calculation unit 112 of the terminal device 110E calculates the hash value HE from the data DE generated and held by the generation and holding unit 111.

[0068] Next, as shown in step S102, the terminal device 110E duplicates the hash value HE. Specifically, the duplication unit 113 of the terminal device 110E duplicates the hash value HE calculated by the calculation unit 112. When the blocks of the blockchain BC are composed of data, the duplication unit 113 of the terminal device 110E may duplicate the data DE. In the following descriptions of <I. Addition of Terminal Device>, <II. Detection of Tampering>, and <III. Data Restoration>, the hash values HA to HE may be replaced with the data DA to DE as appropriate.

[0069] Next, as shown in step S103, the terminal device 110E transmits the hash value HE to the terminal device 110A. Specifically, the transmission / reception unit 114 of the terminal device 110E transmits the hash value HE to the transmission / reception unit 114 of the terminal device 110A.

[0070] Next, as shown in step S104, the terminal device 110A that has received the hash value HE duplicates the hash value HE. Specifically, the duplication unit 113 of the terminal device 110A duplicates the hash value HE received by the transmission / reception unit 114.

[0071] Next, as shown in step S105, the terminal device 110A transmits the hash value HE to each of the terminal devices 110B to 110D. Specifically, the transmission / reception unit 114 of the terminal device 110A transmits the duplicated hash value HE to the transmission / reception unit 114 of each of the terminal devices 110B to 110D.

[0072] Next, as shown in step S106, each of the terminal devices 110A to 110D verifies the hash value HE. Specifically, the additional verification unit 116 of each of the terminal devices 110A to 110D verifies whether the hash value HE has a format as a hash value.

[0073] Next, as shown in step S107, each of the terminal devices 110A to 110D adds the hash value HE to the block chain BC. Specifically, the addition verification unit 116 of each of the terminal devices 110A to 110D adds the new hash value HE to the block chain BC held in the holding unit 115.

[0074] Next, as shown in step S108, the new terminal device 110E is connected to the network NW. Then, the holding unit 115 of the new terminal device 110E holds the blockchain BC.

[0075] Next, as shown in step S109, the terminal device 110E adds a digital signature to the data DE using a private key. 111 The digital signature unit 118 adds a digital signature formed by a private key unique to the terminal device 110E to the data DE generated by the terminal device 110E. In this way, the digital signature unit 118 generates the digitally signed data DE.

[0076] Next, as shown in step S110, copying section 113 of terminal device 110E copies the digitally signed data DE generated by digital signature section 118.

[0077] Next, as shown in step S111, the transmitting / receiving unit 114 of the terminal device 110E transmits the digitally signed data DE to the data management device 120. The data management device 120 receives the digitally signed data DE and stores it in the storage unit 121.

[0078] FIG. 15 is a block diagram illustrating a state in which a new terminal device 110E is added to the management system 100 according to Embodiment 1. As shown in FIG. 15, the management system 100 adds the new terminal device 110E to the network NW. As a result, the added terminal device 110E holds the blockchain BC, like the other terminal devices 110A to 110D.

[0079] FIG. 16 is a block diagram illustrating the data management device 120 to which the data DE with an electronic signature generated by the new terminal device 110E is added in the management system 100 according to Embodiment 1. As shown in FIG. 16, the data management device 120 holds the data DE with an electronic signature received from the new terminal device 110E in the holding unit 121. The data DE with an electronic signature has an electronic signature SE formed using a private key unique to the new terminal device 110E added thereto.

[0080] <I-2. Processing method for a new terminal device> Next, a processing method for a new terminal device in adding a terminal device will be described. FIG. 17 is a flowchart illustrating a processing method for the new terminal device 110E to be added in the management system 100 according to Embodiment 1. As shown in step S121 of FIG. 17, the calculation unit 112 of the new terminal device 110E added to the management system 100 calculates a hash value HE from the data DE generated by the generation holding unit 111.

[0081] Next, as shown in step S122, the replication unit of the terminal device 110E 113 replicates the hash value HE calculated by the calculation unit 112.

[0082] Next, as shown in step S123, the transmission / reception unit 114 of the terminal device 110E transmits the replicated hash value HE to, for example, the transmission / reception unit 114 of the terminal device 110A.

[0083] Next, as shown in step S124, the terminal device 110E is connected to the network NW and holds the blockchain BC. Specifically, the additional verification units 116 of the terminal devices 110A to 110D verify the hash value HE transmitted from the transmission / reception unit 114 of the terminal device 110E. For example, the additional verification units 116 of the terminal devices 110A to 110D verify whether the hash value HE has the format of a hash value. Thereafter, the additional verification units 116 of the terminal devices 110A to 110D add the new hash value HE to the blockchain BC held in the holding unit 115. Along with this, the new terminal device 110E is connected to the network NW. Also, the holding unit 115 of the new terminal device 110E holds the blockchain BC.

[0084] Next, as shown in step S125, the electronic signature unit 118 of the terminal device 110E adds an electronic signature SE formed using a secret key unique to the terminal device 110E to the data DE. Thereby, the electronic signature unit 118 generates data DE with an electronic signature.

[0085] Next, as shown in step S126, the replication unit 113 of the terminal device 110E replicates the data DE with an electronic signature.

[0086] Next, as shown in step S127, the transmission / reception unit 114 of the terminal device 110E transmits the data DE with an electronic signature to the data management device 120.

[0087] <I-3. Processing Method of Terminal Device> Next, in the case of adding a terminal device, the processing method of the terminal devices 110A to 110D on the network NW side that accept the new terminal device 110E will be described. FIG. 18 is a flowchart diagram illustrating the processing method of the terminal devices 110A to 110D on the network NW side in the management system 100 according to Embodiment 1.

[0088] As shown in step S131 of FIG. 18, for example, the transceiver unit 114 of the terminal device 110A receives the hash value HE from the new terminal device 110E. Next, as shown in step S132, the replication unit 113 of the terminal device 110A that has received the hash value HE replicates the hash value HE received by the transceiver unit 114.

[0089] Next, as shown in step S133, the transceiver unit 114 of the terminal device 110A transmits the replicated hash value HE to the transceiver units 114 of the other terminal devices 110B - 110D.

[0090] Next, as shown in step S134, the additional verification unit 116 of each of the terminal devices 110A - 110D verifies whether the hash value HE has the format of a hash value.

[0091] Next, as shown in step S135, the additional verification unit 116 of each of the terminal devices 110A - 110D adds the new hash value HE to the blockchain BC held in the holding unit 115.

[0092] In this way, when the new terminal device 110E is added to the network NW, the terminal device 110A verifies the new hash value HE of the data DE generated by the new terminal device 110E together with the other terminal devices 110B - 110D, and then adds it to the blockchain BC.

[0093] <I - 4. Data Management Method of Data Management Device> Next, the data management method of the data management device 120 when adding a new terminal device 10E will be described. FIG. 19 is a flowchart illustrating the data management method of the data management device 120 in the management system 100 according to Embodiment 1.

[0094] As shown in step S141 of FIG. 19, the data management device 120 receives the electronically signed data DE transmitted from the terminal device 110E. Then, as shown in step S142 and FIG. 16, the data management device 120 holds the electronically signed data DE received from the terminal device 110E in the holding unit 121.

[0095] <II. Detection of Tampering> Next, as an operation of the management system 100, the detection of tampering will be described. For example, it is assumed that the held data DA to DD held in the generation holding units 111 of the terminal devices 110A to 110D are tampered with by a tamperer such as a hacker. Therefore, for example, it is detected whether there is tampering at regular intervals or at the timing of referring to the held data. First, <II-1. Management Method of the Management System> in the detection of tampering will be described. Then, <II-2. Processing Method of the Terminal Device> in the detection of tampering will be described.

[0096] <II-1. Management Method of the Management System> FIG. 20 is a block diagram illustrating the terminal devices 110A to 110D and the network NW that perform tampering detection in the management system 100 according to Embodiment 1. As shown in FIG. 20, the management system 100 includes a plurality of terminal devices 110A to 110D, a network NW, and a server device 130 connected to the network NW. The server device 130 provides services. The services are, for example, operation management services, security monitoring services, etc. Each of the terminal devices 110A to 110D holds a blockchain BC.

[0097] FIG. 21 is a sequence diagram illustrating a management method for performing tampering detection in the management system 100 according to Embodiment 1. As shown in step S201 of FIG. 21, among the terminal devices 110A to 110D, for example, the terminal device 110A that performs tampering detection causes the calculation unit 112 to calculate a hash value HA from the held data DA.

[0098] Next, as shown in step S202, the control unit 117 of the terminal device 110A transmits to the terminal device 110B the block Request the hash value HA in the chain BC. block From the perspective of the terminal device 110A, the hash value HA in the chain BC is the transmitted hash value HA transmitted by the terminal device 110A. In response to this, as shown in step S203, the transmitting / receiving unit 114 of the terminal device 110B transmits the requested hash value HA to the terminal device 110A. Then, the transmitting / receiving unit 114 of the terminal device 110A receives the hash value HA transmitted from the terminal device 110B.

[0099] Next, as shown in step S204, the additional verification unit 116 of the terminal device 110A compares the hash value HA calculated from the data DA held by the terminal device 110A with the hash value HA received from the terminal device 110B. As described above, the hash value HA received from the terminal device 110B is the transmission hash value HA included in the blockchain BC held by the terminal device 110B.

[0100] 20, the additional verification unit 116 of the terminal device 110A may compare the hash value HA calculated from the retained data DA with the hash value HA of the blockchain BC retained in the terminal device 110A. Also, the additional verification unit 116 of the terminal device 110A may compare the hash value HA calculated from the retained data DA with the hash value HA included as a cache value in the block of the hash value HB in the blockchain BC retained in the terminal device 110A.

[0101] Next, as shown in step S205 of FIG. 21, the additional verification unit 116 of the terminal device 110A compares the calculated hash value HA with the received hash value HA, and if the two are different, detects tampering with the retained data DA retained in the generation and retention unit 111.

[0102] Next, as shown in step S206, the control unit 117 of the terminal device 110A disconnects the connection with the server device 130 and disconnects the terminal device 110A from the network NW.

[0103] Next, as shown in step S207, the control unit 117 of the terminal device 110A invalidates the tampered holding data DA. For example, the control unit 117 of the terminal device 110A marks the tampered holding data DA with a mark such as a flag so that it is not used in subsequent processing.

[0104] <II-2. Processing Method of Terminal Device> Next, a processing method of the terminal device in detecting tampering will be described. FIG. 22 is a flowchart illustrating a processing method of a terminal device that detects tampering in the management system 100 according to the embodiment.

[0105] As shown in step S211 of FIG. 22, for example, the terminal device 110A is caused to hold the blockchain BC together with other terminal devices 110B to 110D. Step S211 is the same as step S51 of FIG. 9.

[0106] Next, as shown in step S212, the terminal device 110A is caused to detect tampering of the holding data DA. Specifically, by comparing the holding data DA held by the terminal device 110A or the hash value HA of the holding data DA with the transmission data DA or the transmission hash value HA included in the blockchain BC held by the other terminal devices 110B to 110D, the additional verification unit 116 is caused to detect tampering of the holding data DA.

[0107] Next, when the additional verification unit 116 of the terminal device 110A detects tampering, as shown in step S213, the control unit 117 of the terminal device 110A disconnects the connection with the server device 130 that provides services on the network NW.

[0108] Next, as shown in step S214, when the control unit 117 of the terminal device 110A detects forgery, it invalidates the held data DA held in the generation holding unit 111.

[0109] Step S212 is performed by the method shown in FIG. 23 below. FIG. 23 is a flowchart diagram exemplifying a method of detecting forgery in the management system 100 according to Embodiment 1. As shown in step S221 of FIG. 23, the calculation unit 112 of the terminal device 110A calculates a hash value HA from the held data DA held by the generation holding unit 111.

[0110] Next, as shown in step S222, the control unit 117 of the terminal device 110A requests the terminal device 110B for the hash value HA included in the blockchain BC held by the terminal device 110B.

[0111] Next, as shown in step S223, the transceiver unit 114 of the terminal device 110A receives the requested hash value HA from the terminal device 110B.

[0112] Next, as shown in step S224, the additional verification unit 116 of the terminal device 110A compares the hash value HA calculated from the held data DA with the hash value HA received from the terminal device 110B.

[0113] Next, as shown in step S225, the additional verification unit 116 of the terminal device 110A determines forgery. Specifically, when the additional verification unit 116 of the terminal device 110A compares the calculated hash value HA with the received hash value HA and the two are different, it detects forgery of the held data DA held in the generation holding unit 111. In this way, the terminal device 110A detects forgery of the held data DA.

[0114] <III. Data Restoration> Next, as the operation of the management system 100 according to Embodiment 1, data restoration will be described. First, <III-1. Management method of the management system> in data restoration will be described. Thereafter, <III-2. Processing method of the terminal device> and <III-3. Data management method of the data management device> in data restoration will be described.

[0115] <III-1. Management method of the management system> FIG. 24 is a block diagram illustrating a terminal device 110A that performs data restoration, other terminal devices 110B to 110D, a data management device 120, a server device 130, and a network NW in the management system 100 according to Embodiment 1. As shown in FIG. 24, the management system 100 includes a terminal device 110A, a plurality of terminal devices 110B to 110D, a network NW, a data management device 120, and a server device 130. The terminal device 110A is disconnected from the server device 130 that provides services on the network NW. Note that, in the drawings, the configurations of the terminal devices 110A to 110D and the data management device 120 are appropriately shown in a simplified manner.

[0116] FIG. 25 is a block diagram illustrating the data management device 120 in the management system 100 according to Embodiment 1. As shown in FIG. 25, the data management device 120 includes, in addition to a holding unit 121, a replication unit 122, a transmission / reception unit 123, and a control unit 124. The replication unit 122, the transmission / reception unit 123, and the control unit 124 each have a function as a replication means for replicating electronically signed data, a transmission / reception means for transmitting and receiving electronically signed data, and a control means for controlling the data management device 120 (holding unit 121, replication unit 122, and transmission / reception unit 123).

[0117] FIG. 26 is a sequence diagram illustrating a management method for performing data restoration in the management system 100 according to Embodiment 1. As shown in step S301 of FIG. 26 and FIG. 24, the control unit 117 of the terminal device 110A requests the control unit 124 of the data management device 120 for the electronically signed data DA held by the data management device 120.

[0118] Next, as shown in step S302, the copying unit 122 of the data management device 120 copies the digitally signed data DA held in the data management device 120.

[0119] Next, as shown in step S303, the transmitting / receiving unit 123 of the data management device 120 transmits the copied data DA with the electronic signature to the transmitting / receiving unit 114 of the terminal device 110A. In this manner, when the terminal device 110A that has been disconnected from the network NW reconnects to the network NW, the data management device 120 transmits the data DA with the electronic signature that it holds to the terminal device 110A that is to connect.

[0120] Next, as shown in step S304, the decryption unit 119 of the terminal device 110A receives the digitally signed data DA from the data management device 120. Then, the decryption unit 119 decrypts the digital signature SA of the received digitally signed data DA. The decrypted digital signature SA is, for example, a hash value HA of the data DA.

[0121] Next, as shown in step S305, the calculation unit 112 of the terminal device 110A calculates a hash value HA of the digitally signed data DA received from the data management device 120.

[0122] Next, as shown in step S306, the additional verification unit 116 of the terminal device 110A verifies that the received electronically signed data DA belongs to the terminal device 110A by comparing the hash value HA obtained by decrypting the electronic signature SA with the calculated hash value HA of the electronically signed data DA. The additional verification unit 116 of the terminal device 110A also compares the hash value HA included in the blockchain BC held by the terminal device 110B with the calculated hash value HA to verify a match. In this way, the terminal device 110A of this embodiment can guarantee the authenticity of the electronically signed data DA received from the data management device 120 by a two-stage system of the hash value HA obtained from the electronic signature SA and the hash value HA included in the blockchain BC of the terminal device 110B.

[0123] Next, as shown in step S307, the control unit 117 of the terminal device 110A connects the terminal device 110A to the server device 130.

[0124] In this way, in the management system 100, when a plurality of terminal devices 110A to 110D include at least a first terminal device and a second terminal device, the decoding unit 119 of the first terminal device receives the data with an electronic signature from the data management device 120 and decodes the electronic signature of the received data with an electronic signature. The calculation unit 112 of the first terminal device calculates the hash value of the received data with an electronic signature. The additional verification unit 116 of the first terminal device verifies the match between the received data with an electronic signature or the calculated hash value and the transmission data or transmission hash value transmitted by the first terminal device included in the blockchain BC held by the second terminal device. The control unit of the first terminal device 117 connects to the network NW when the additional verification unit 116 verifies the match.

[0125] <III-2. Processing Method of Terminal Device> Next, a processing method of the terminal device in data restoration will be described. FIG. 27 is a flowchart illustrating a processing method of the terminal device 110A that performs data restoration in the management system 100 according to the embodiment.

[0126] As shown in FIG. 27, steps S311 to S314 are the same as steps S211 to S214 in FIG. 22. After invalidating the held data, the terminal device 110A performs data restoration as shown in step S315.

[0127] The data restoration in step S315 of FIG. 27 is, for example, as shown in FIG. 28. FIG. 28 is a flowchart illustrating a processing method of data restoration in the management system 100 according to Embodiment 1. As shown in step S321 of FIG. 28, for example, the control unit 117 of the terminal device 110A requests the control unit 124 of the data management device 120 for backup data of the data DA with an electronic signature held in the holding unit 121.

[0128] Next, as shown in step S322, the transceiver 114 of the terminal device 110A receives the signed data DA transmitted from the transceiver 123 of the data management device 120.

[0129] Next, as shown in step S323, the decoder 119 of the terminal device 110A receives the signed data DA from the data management device 120 and decrypts the digital signature SA of the received signed data DA. By decrypting the digital signature SA, the hash value HA of the data DA is obtained.

[0130] Next, as shown in step S324, the calculation unit 112 of the terminal device 110A calculates the hash value HA of the signed data DA received from the data management device 120.

[0131] Next, as shown in step S325, the additional verification unit 116 of the terminal device 110A verifies that the signed data DA is generated by the terminal device 110A by comparing the hash value HA obtained by decrypting the digital signature SA with the calculated hash value HA. Further, the additional verification unit 116 of the terminal device 110A compares the transmitted hash value HA included in the blockchain BC held by the terminal device 110B with the calculated hash value HA and verifies the match.

[0132] Next, as shown in step S326, when the additional verification unit 116 verifies the match, the control unit 117 of the terminal device 110A connects to the network NW and connects the terminal device 110A to the server device 130. In this way, the terminal device 110A restores the data DA.

[0133] <III-3. Data Management Method of Data Management Device> Next, a data management method of the data management device in data restoration will be described. FIG. 29 is a flowchart illustrating a data management method of the data management device 120 that performs data restoration in the management system 100 according to Embodiment 1.

[0134] As shown in step S331 of FIG. 29, the control unit 124 of the data management device 120 receives a request for backup data of the data DA from the terminal device 110A that has been disconnected from the network NW.

[0135] Next, as shown in step S332, the copying unit 122 of the data management device 120 copies the digitally signed data DA held in the holding unit 121.

[0136] Next, as shown in step S333, the transmission / reception unit 123 of the data management device 120 transmits the copied data DA with the digital signature to the terminal device 110A. In this manner, the data management device 120 transmits the data DA with the digital signature to the terminal device 110A. This allows the terminal device 110A to restore the data.

[0137] Next, the effects of the management system 100 of this embodiment will be described. Since the management system 100 of this embodiment has each of the terminal devices 110A to 110D hold a blockchain BC, it is possible to improve the reliability of the management system 100 and the held data through the addition of a new terminal device 110E, the detection of tampering, and the restoration of data.

[0138] The management system 100 also includes a data management device 120 that holds the digitally signed data DE of each of the terminal devices 110A to 110D. Therefore, when a terminal device 110 that has been disconnected from the management system 100 is reconnected, the data can be restored.

[0139] Furthermore, when a new terminal device 110E is added to the management system 100, new data DE can be added to the data management device 120.

[0140] When tampering is detected, each of the terminal devices 110A to 110D is disconnected from the server device 130. Furthermore, the data held in the disconnected terminal device 110 is invalidated. This makes it possible to improve the reliability of the management system 100 and the held data.

[0141] In addition, since the management system 100 uses a public blockchain BC, it is possible for actors to access it and to prevent arbitrary tampering.

[0142] For example, the management system 100 can provide a security service platform that comprehensively operates and manages securely manufactured edge devices. This allows the management system 100 to configure a system that includes edge IoT devices and servers. Therefore, by realizing the entire lifecycle management from the production of equipment to logistics, installation, operation, maintenance, and disposal, the security and authenticity of the product and the data handled therein can be guaranteed.

[0143] In addition, the management system 100 can detect tampering by registering and managing hash values ​​of setting values ​​such as operation logs and whitelists on the blockchain BC. In addition, the management system 100 can automatically control the disconnection of a terminal device 110 such as an edge device from the management system 100 and the reconnection of the disconnected terminal device 110 to the management system 100.

[0144] In this way, the management system 100 can suppress tampering with logs and setting values ​​during operation, and even if a whitelist or the like is tampered with due to a mistake in settings, etc., the management system 100 can detect the tampering. Furthermore, if tampering is detected, the connection of the terminal device 110 can be cut off, and appropriate measures can be taken.

[0145] Furthermore, the management system 100 of this embodiment may not hold operation logs, setting value data, and the like of the terminal device 110 for each tenant or each customer. This can reduce management costs and the risk of operation suspension in the event of a disaster or large-scale failure. It can also reduce the risk of data loss in the event that a service provider is unable to continue its business. Other configurations and effects are included in the description of the above-mentioned embodiment.

[0146] <Embodiment 2> Next, a management system according to embodiment 2 will be described. The management system 100 according to embodiment 1 is of a P2P network type. In contrast, the management system according to this embodiment is of a client-server type.

[0147] Fig. 30 is a block diagram illustrating a plurality of terminal devices, a data management device, and a network in a management system according to embodiment 2. As shown in Fig. 30, the management system 200 includes a plurality of terminal devices 210A-210D, a data management device 220, and a network NW. The plurality of terminal devices 210A-210D are connected to the network NW. The data management device 220 is also connected to the network NW. The plurality of terminal devices 210A-210D are connected to the data management device 220 via the network NW.

[0148] In this embodiment, the management system 200 is of a client-server type, and a plurality of terminal devices 210A to 210D are connected to a data management device 220. The management system 200 may further include a server device connected to the network NW.

[0149] In the management system 200 of this embodiment, the data management device 220 holds a block chain BC in which data or hash values ​​of data generated by each of the terminal devices 210A to 210D are linked as blocks. In addition, when a new terminal device 210E is added to the network NW, the data management device 220 adds new data or the hash value of the new data generated by the new terminal device 210E to the block chain BC.

[0150] According to the management system 100 described above and the management system 200 of this embodiment, the management system includes a plurality of devices and a network NW to which the plurality of devices are connected. At least one of the plurality of devices holds a blockchain BC in which data or hash values ​​of data generated by two or more of the plurality of devices are linked as a block. In the management system 100, each of the terminal devices 110A to 110D holds a blockchain BC. In the management system 200, the data management device 220 holds a blockchain BC. The configurations of the <terminal device> and the <data management device> are described below.

[0151] <Terminal device> First, the configuration of the terminal devices 210A to 210D will be described. Fig. 31 is a block diagram illustrating the terminal device 210 in the management system 200 according to the second embodiment.

[0152] As shown in FIG. 31, the terminal device 210 may have a generating and storing unit 211, a calculating unit 212, a replicating unit 213, a transmitting and receiving unit 214, a storing unit 215, an additional verifying unit 216, a control unit 217, an electronic signature unit 218, and a decrypting unit 219, similar to the terminal device 110, or may not have some components. The functions of each component in the terminal device 210 are similar to those of the terminal device 110. Note that, similar to the case of the terminal device 110, any one of the terminal devices 210A to 210E, or one or more of the terminal devices 210A to 210E, are collectively referred to as the terminal device 210. When specifying any one of the terminal devices 210A to 210E, the terminal device 210 is indicated by adding a reference symbol of any one of the terminal devices 210A to 210E. The terminal device 210 may have a hardware configuration similar to that of the terminal device 110.

[0153] In this embodiment, the terminal devices 210A to 210D may or may not hold the block chain BC. Also, the terminal devices 210A to 210D may or may not calculate the hash values ​​HA to HE. Furthermore, the terminal devices 210A to 210D may or may not detect tampering.

[0154] <Data management device> Next, a description will be given of the configuration of the data management device 220. Fig. 32 is a block diagram illustrating the data management device 220 in the management system 200 according to the second embodiment.

[0155] 32, data management device 220 has a holding unit 221, a copying unit 222, a transmission / reception unit 223, and a control unit 224. Similar to data management device 120, holding unit 221, copying unit 222, transmission / reception unit 223, and control unit 224 have functions as holding means for holding data with a digital signature, copying means for copying data with a digital signature, transmitting / receiving means for transmitting / receiving data with a digital signature, and control means for controlling data management device 220 (holding unit 221, copying unit 222, and transmission / reception unit 223).

[0156] The data management device 220 further includes a calculation unit 225 and an additional verification unit 226. The calculation unit 225 and the additional verification unit 226 function as a hash value calculation means and a hash value additional verification means. With this configuration, the transmission / reception unit 223 of the data management device 220 receives, from each of the terminal devices 210A to 210D, the data DA to DD generated by each of the terminal devices 210A to 210D. Then, the data management device 220 calculates hash values ​​HA to HD from the received data DA to DD. The data management device 220 adds the calculated hash values ​​HA to HD to the blockchain BC that it holds. In this way, the data management device 220 holds the blockchain BC.

[0157] The data management device 220 may have the same hardware configuration as the data management device 120. The data management device 220 may receive the data DA-DE generated by each of the terminal devices 210A-210D from each of the terminal devices 210A-210D and calculate the hash values ​​HA-HD. The data management device 220 may also receive the hash values ​​HA-HD calculated by each of the terminal devices 210A-210D.

[0158] The data management device 220 may hold the blockchain BC together with the multiple terminal devices 210A to 210D, or only the data management device 220 may hold the blockchain BC.

[0159] The data management device 220 may detect tampering of the retained data DA to DD retained by each of the terminal devices 210A to 210D. In that case, the hash values ​​HA to HD of the retained data DA to DD retained by each of the terminal devices 210A to 210D are compared with the hash values ​​HA to HD included in the block chain retained by the data management device 220.

[0160] When the data management device 220 detects tampering, it disconnects the connection with the terminal device 210A that detected the tampering. It then invalidates the data held by the terminal device 210A. Thereafter, it transmits the digitally signed data to the disconnected terminal device 210A to restore the data and reconnect the terminal device 210A.

[0161] Next, the effects of this embodiment will be described. The management system 200 of this embodiment is a client-server type, and a plurality of terminal devices 210A to 210D are connected to a data management device 220. The data management device 220 holds a blockchain BC. Therefore, the operation of the management system 200 can be managed in a centralized manner. This allows the addition of a new terminal device 210E, the detection of tampering, and the restoration of data to be performed in a centralized manner.

[0162] In addition, the management system 200 of this embodiment transmits and receives data via the data management device 220. Therefore, it can be adapted to an IoT system that collects data from terminal devices 210 scattered at multiple locations. Other configurations and effects are included in the description of the above-mentioned embodiments and embodiment 1.

[0163] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above-mentioned embodiments. Various modifications that can be understood by a person skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. For example, a combination of the configurations of the outline of the embodiment, the first and second embodiments is also included in the scope of the present invention. In addition, a program that causes a computer to execute the processing method, data management method, and management method of the outline of the embodiment, the first and second embodiments is also included in the scope of the present invention.

[0164] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes.

[0165] (Appendix 1) Connected to a network together with other terminal devices, A blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks is stored together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain together with the other terminal devices. Terminal device. (Appendix 2) A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network. 2. A terminal device as described in claim 1. (Appendix 3) The additional verification means detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device. 3. A terminal device as described in appended claim 2. (Appendix 4) The method further includes a control unit for disconnecting a connection to a server device that provides a service on a network when the additional verification unit detects the tampering. 4. A terminal device as described in appended claim 3. (Appendix 5) the control means invalidates the retained data when the falsification is detected. 5. A terminal device as described in claim 4. (Appendix 6) a digitally signed data generating means for generating digitally signed data by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by the generating and holding means; a decryption means for decrypting the electronic signature; Further equipped with The decryption means receives the digitally signed data from a data management device that stores the digitally signed data generated by each of the terminal devices, and decrypts the digital signature of the received digitally signed data; The calculation means calculates a hash value of the received digitally signed data, The additional verification means verifies whether the received digitally signed data or the calculated hash value of the digitally signed data matches the transmission data or the transmission hash value included in the block chain held by the other terminal device; the control means, when the additional verification means verifies the match, connects to the server device; 6. A terminal device according to claim 4 or 5. (Appendix 7) a data management device that stores digitally signed data, the digital signature being generated by using a private key unique to each of the terminal devices and attached to the data generated by each of the terminal devices; A terminal device according to any one of appendix 1 to 6. (Appendix 8) By being connected to a network together with a plurality of terminal devices, each terminal device is connected to a block chain in which data generated by each terminal device or hash values ​​of the data are linked as blocks, storing digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices; When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain held by each of the terminal devices, and the digitally signed data generated by the new terminal device is added. Data management device. (Appendix 9) When the terminal device that has been disconnected from the network reconnects to the network, the terminal device transmits the stored data with the electronic signature to the terminal device that is to reconnect. 9. The data management device of claim 8. (Appendix 10) a storage means for storing the digitally signed data; a copying means for copying the digitally signed data; a transmitting / receiving means for transmitting and receiving the data with the digital signature; a control means for controlling the storage means, the copying means, and the transmitting / receiving means; Equipped with 10. The data management device of claim 8 or 9. (Appendix 11) A plurality of devices; a network to which the plurality of devices are connected; Equipped with At least one of the plurality of devices holds a blockchain in which data generated by two or more of the plurality of devices or hash values ​​of the data are linked as blocks; When a new device is added to the network, the one device adds new data generated by the new device or a hash value of the new data to the blockchain. Management system. (Appendix 12) the plurality of devices includes a plurality of terminal devices, Each terminal device holds a blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks, When a new terminal device is added to the network, each of the terminal devices adds new data generated by the new terminal device or a hash value of the new data to the blockchain. 12. The management system according to claim 11. (Appendix 13) Each of the terminal devices A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from another terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network. 13. The management system according to claim 12. (Appendix 14) the plurality of terminal devices includes at least a first terminal device and a second terminal device, The first terminal device detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain retained by the second terminal device. 14. The management system according to claim 13. (Appendix 15) A server device for providing a service is further provided, Each of the terminal devices has a control means for disconnecting the connection with the server device, When the first terminal device detects the tampering, the control means of the first terminal device disconnects the connection with the server device. 15. The management system according to claim 14. (Appendix 16) the control means of the first terminal device invalidates the retained data when the falsification is detected. 16. The management system according to claim 15. (Appendix 17) Each of the terminal devices a digitally signed data generating means for generating digitally signed data by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by the generating and holding means; a decryption means for decrypting the electronic signature; Further equipped with The decryption means of the first terminal device receives the digitally signed data from a data management device that stores the digitally signed data generated by each of the terminal devices, and decrypts the digital signature of the received digitally signed data; the calculation means of the first terminal device calculates a hash value of the received digitally signed data; The additional verification means of the first terminal device verifies whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain held by the second terminal device; the control means of the first terminal device connects the first terminal device to the server device when the additional verification means verifies the match; 17. The management system of claim 15 or 16. (Appendix 18) connected to a network together with the plurality of terminal devices, The method further includes a data management device for storing digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices. 18. The management system according to any one of appendixes 12 to 17. (Appendix 19) When the new terminal device is added to the network, the data management device is added with the electronic signature data to which the electronic signature formed by using a private key unique to the new terminal device is added. 19. The management system according to claim 18. (Appendix 20) when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the stored digitally signed data to the terminal device that is to reconnect. 20. The management system of claim 18 or 19. (Appendix 21) The data management device includes: a storage means for storing the digitally signed data; a copying means for copying the digitally signed data; a transmitting / receiving means for transmitting and receiving the data with the digital signature; a control means for controlling the storage means, the copying means, and the transmitting / receiving means; Equipped with The management system according to any one of appendixes 18 to 20. (Appendix 22) the plurality of devices include a plurality of terminal devices and a data management device to which the plurality of terminal devices are connected; The data management device holds a block chain in which data generated by each terminal device or hash values ​​of the data are linked as blocks, When a new terminal device is added to the network, the data management device adds new data generated by the new terminal device or a hash value of the new data to the blockchain. 12. The management system according to claim 11. (Appendix 23) A blockchain in which data generated by each terminal device in a network connected together with other terminal devices or hash values ​​of the data are linked as blocks is stored in a predetermined terminal device together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain of the specified terminal device together with the other terminal devices. Processing methods. (Appendix 24) When the blockchain is stored in the specified terminal device together with the other terminal devices, the specified terminal device is generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; 23. The method of claim 23. (Appendix 25) The predetermined terminal device detecting tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device; 2. The processing method described in Appendix 24. (Appendix 26) When the falsification is detected, the connection between the predetermined terminal device and a server device that provides a service over a network is cut off. 25. The processing method described in Appendix 25. (Appendix 27) when the falsification is detected, causing the predetermined terminal device to invalidate the retained data; 27. The processing method according to claim 26. (Appendix 28) causing the predetermined terminal device to generate data with a digital signature by adding a digital signature formed by using a private key unique to each of the terminal devices to the data previously generated; After disconnecting the predetermined terminal device from the server device, receiving the electronically signed data from a data management device that holds the electronically signed data generated by each of the terminal devices, and decrypting the electronic signature of the received electronically signed data; Calculating a hash value of the received digitally signed data; Verifying whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value in the blockchain held by the other terminal device; When the match is verified, the predetermined terminal device is connected to the server device. 28. The processing method according to claim 26 or 27. (Appendix 29) connecting the predetermined terminal device to a data management device that stores digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices; The processing method according to any one of appendix 23 to 28. (Appendix 30) A data management device is connected to each of a plurality of terminal devices connected to a network, the terminal devices holding a block chain in which data generated by each of the terminal devices or hash values ​​of the data are linked as blocks; a data management device that stores electronically signed data, the data being generated by each of the terminal devices and having an electronic signature formed by using a private key unique to each of the terminal devices added thereto; When a new terminal device is added to the network, and new data generated by the new terminal device or a hash value of the new data is added to the blockchain held by each of the terminal devices, the data with the electronic signature generated by the new terminal device is added to the data management device. Data management methods. (Appendix 31) when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the data with the electronic signature held by the data management device to the connected terminal device; 31. A data management method as described in Appendix 30. (Appendix 32) When the data management device transmits the digitally signed data held by the data management device, the data management device storing the digitally signed data; Reproducing the digitally signed data; transmitting and receiving the data with the electronic signature; 32. The data management method according to claim 31. (Appendix 33) A blockchain is created by linking data generated by two or more devices or hash values ​​of the data as blocks among a plurality of devices connected to a network, and the blockchain is stored in at least one device among the plurality of devices; When a new device is added to the network, new data generated by the new device or a hash value of the new data is added to the blockchain; Management method. (Appendix 34) the plurality of devices includes a plurality of terminal devices, A blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks in a network to which each terminal device is connected is stored in each terminal device, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain; The management method described in Appendix 33. (Appendix 35) When the blockchain is stored in each of the terminal devices, generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from another terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; The management method described in Appendix 34. (Appendix 36) The plurality of terminal devices include at least a first terminal device and a second terminal device, The first terminal device detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain retained by the second terminal device. The management method described in Appendix 35. (Appendix 37) when the tampering is detected, causing the first terminal device to disconnect from a server device that provides a service on a network; The method of administration described in Appendix 36. (Appendix 38) when the falsification is detected, causing the first terminal device to invalidate the retained data; The management method described in Appendix 37. (Appendix 39) causing each of the terminal devices to generate data with a digital signature by adding a digital signature formed by using a private key unique to each of the terminal devices to the data previously generated; After disconnecting the first terminal device from the server device, receiving the electronically signed data from a data management device that holds the electronically signed data generated by each of the terminal devices, and decrypting the electronic signature of the received electronically signed data; Calculating a hash value of the received digitally signed data; Verifying whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value in the blockchain held by the second terminal device; If the match is verified, a connection is made to the server device. 39. The method of administration described in Appendix 37 or 38. (Appendix 40) a data management device that stores digitally signed data, the digital signature being generated by using a private key unique to each of the terminal devices, and the data management device is connected to the data management device; The management method according to any one of appendix 34 to 39. (Appendix 41) when the new terminal device is added to the network, the data management device is caused to add the digitally signed data to which a digital signature formed using a private key unique to the new terminal device has been added. The management method described in Appendix 40. (Appendix 42) when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the data with the electronic signature held by the data management device to the connected terminal device; 42. The method of claim 40 or 41. (Appendix 43) When the data management device transmits the digitally signed data held by the data management device, the data management device storing the digitally signed data; Reproducing the digitally signed data; transmitting and receiving the data with the electronic signature; The method of administration described in Appendix 42. (Appendix 44) the plurality of devices include a plurality of terminal devices and a data management device to which the plurality of terminal devices are connected; A blockchain is stored in the data management device, in which data generated by each terminal device in a network to which the terminal devices are connected or hash values ​​of the data are linked as blocks; When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain; The management method described in Appendix 33. (Appendix 45) A blockchain in which data generated by each terminal device in a network connected together with other terminal devices or hash values ​​of the data are linked as blocks is stored in a predetermined terminal device together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain of the specified terminal device together with the other terminal devices. A non-transitory computer-readable medium on which a program for causing a computer to execute a process is stored. (Appendix 46) When the blockchain is stored in the specified terminal device together with the other terminal devices, the specified terminal device is generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; A non-transitory computer-readable medium having stored thereon a program according to claim 45 that causes a computer to execute the program. (Appendix 47) The predetermined terminal device By comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device, tampering with the retained data is detected. A non-transitory computer-readable medium having stored thereon a program according to claim 46 that causes a computer to execute the program. (Appendix 48) When the falsification is detected, the connection between the predetermined terminal device and a server device that provides a service over a network is cut off. A non-transitory computer-readable medium having stored thereon a program according to claim 47 that causes a computer to execute the program. (Appendix 49) when the falsification is detected, causing the predetermined terminal device to invalidate the retained data; A non-transitory computer-readable medium having stored thereon a program according to claim 48 that causes a computer to execute the program. (Appendix 50) causing the predetermined terminal device to generate data with a digital signature by adding a digital signature formed by using a private key unique to each of the terminal devices to the data previously generated; After disconnecting the predetermined terminal device from the server device, receiving the electronically signed data from a data management device that holds the electronically signed data generated by each of the terminal devices, and decrypting the electronic signature of the received electronically signed data; Calculating a hash value of the received digitally signed data; Verifying whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value in the blockchain held by the other terminal device; When the match is verified, the predetermined terminal device is connected to the server device. A non-transitory computer-readable medium having stored thereon a program according to claim 48 or 49 that causes a computer to execute the program. (Appendix 51) connecting the predetermined terminal device to a data management device that stores digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices; A non-transitory computer-readable medium storing a program according to any one of appendices 45 to 50 that causes a computer to execute the program. (Appendix 52) A data management device is connected to each of a plurality of terminal devices connected to a network, the terminal devices holding a block chain in which data generated by each of the terminal devices or hash values ​​of the data are linked as blocks; a data management device that stores electronically signed data, the data being generated by each of the terminal devices and having an electronic signature formed by using a private key unique to each of the terminal devices added thereto; When a new terminal device is added to the network, and new data generated by the new terminal device or a hash value of the new data is added to the blockchain held by each of the terminal devices, the data with the electronic signature generated by the new terminal device is added to the data management device. A non-transitory computer-readable medium on which a program for causing a computer to execute a process is stored. (Appendix 53) when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the data with the electronic signature held by the data management device to the connected terminal device; A non-transitory computer-readable medium having stored thereon a program according to claim 52 that causes a computer to execute the program. (Appendix 54) When the data management device transmits the digitally signed data held by the data management device, the data management device storing the digitally signed data; Reproducing the digitally signed data; transmitting and receiving the data with the electronic signature; A non-transitory computer-readable medium having stored thereon a program according to claim 53 that causes a computer to execute the program. (Appendix 55) A blockchain is created by linking data generated by two or more devices or hash values ​​of the data as blocks among a plurality of devices connected to a network, and the blockchain is stored in at least one device among the plurality of devices; When a new device is added to the network, new data generated by the new device or a hash value of the new data is added to the blockchain; A non-transitory computer-readable medium on which a program for causing a computer to execute a process is stored. (Appendix 56) the plurality of devices includes a plurality of terminal devices, A blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks in a network to which each terminal device is connected is stored in each terminal device, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain; A non-transitory computer-readable medium having stored thereon a program according to claim 55 that causes a computer to execute the program. (Appendix 57) When the blockchain is stored in each of the terminal devices, generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from another terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; A non-transitory computer-readable medium having stored thereon a program according to claim 56 that causes a computer to execute the program. (Appendix 58) The plurality of terminal devices include at least a first terminal device and a second terminal device, The first terminal device detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain retained by the second terminal device. A non-transitory computer-readable medium having stored thereon a program according to claim 57 that causes a computer to execute the program. (Appendix 59) when the tampering is detected, causing the first terminal device to disconnect from a server device that provides a service on a network; A non-transitory computer-readable medium having stored thereon a program according to claim 58 that causes a computer to execute the program. (Appendix 60) when the falsification is detected, causing the first terminal device to invalidate the retained data; A non-transitory computer-readable medium having stored thereon a program according to claim 59 that causes a computer to execute the program. (Appendix 61) causing each of the terminal devices to generate data with a digital signature by adding a digital signature formed by using a private key unique to each of the terminal devices to the data previously generated; After disconnecting the first terminal device from the server device, receiving the electronically signed data from a data management device that holds the electronically signed data generated by each of the terminal devices, and decrypting the electronic signature of the received electronically signed data; Calculating a hash value of the received digitally signed data; Verifying whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value in the blockchain held by the second terminal device; If the match is verified, a connection is made to the server device. A non-transitory computer-readable medium having stored thereon a program according to claim 59 or 60 that causes a computer to execute the program. (Appendix 62) a data management device that stores digitally signed data, the digital signature being generated by using a private key unique to each of the terminal devices, and the data management device is connected to the data management device; A non-transitory computer-readable medium storing a program according to any one of appendices 58 to 61 that causes a computer to execute the program. (Appendix 63) when the new terminal device is added to the network, the data management device is caused to add the digitally signed data to which a digital signature formed using a private key unique to the new terminal device has been added. A non-transitory computer-readable medium having stored thereon a program according to claim 62 that causes a computer to execute the program. (Appendix 64) when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the data with the electronic signature held by the data management device to the connected terminal device; A non-transitory computer-readable medium having stored thereon a program according to claim 62 or 63 that causes a computer to execute the program. (Appendix 65) When the data management device transmits the digitally signed data held by the data management device, the data management device storing the digitally signed data; Reproducing the digitally signed data; transmitting and receiving the data with the electronic signature; A non-transitory computer-readable medium having stored thereon a program according to claim 64 that causes a computer to execute the program. (Appendix 66) the plurality of devices include a plurality of terminal devices and a data management device to which the plurality of terminal devices are connected; A blockchain is stored in the data management device, in which data generated by each terminal device in a network to which the terminal devices are connected or hash values ​​of the data are linked as blocks; When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain; A non-transitory computer-readable medium having stored thereon a program according to claim 65 that causes a computer to execute the program. [Explanation of symbols]

[0166] 1, 100, 200 Management System 10, 10A, 10B, 10C, 10D, 10E Terminal Equipment 11, 111, 211 Generation and holding section 12, 112, 212 calculation section 13, 113, 213 Reproduction Department 14, 114, 214 Transmitter / Receiver 15, 115,215 Holding part 16, 116, 216 Additional Verification Department 17, 117, 217 Control section 110, 110A, 110B, 110C, 110D, 110E terminal equipment 118, 218 Electronic Signature Department 119, 219 Decoding section 120, 220 Data management device 121, 221 Holding part 122, 222 Reproduction Department 123, 223 Transmitter / Receiver 124, 224 Control unit 130 Server device 210, 210A, 210B, 210C, 210D, 210E terminal equipment 225 Calculation Department 226 Additional Verification Department BC Blockchain BRA, BRB, BRC, BRD blocks DA, DB, DC, DD, DE data HA, HB, HC, HD, HE hash values NW Network SA, SB, SC, SD, SE Electronic signature

Claims

1. Connected to a network together with other terminal devices, A blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks is stored together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain together with the other terminal devices; A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network; The additional verification means detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device, The method further includes a control unit for disconnecting a connection to a server device that provides a service on a network when the additional verification unit detects the tampering. Terminal device.

2. the control means invalidates the retained data when the falsification is detected. The terminal device according to claim 1 .

3. a digitally signed data generating means for generating digitally signed data by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by the generating and holding means; a decryption means for decrypting the electronic signature; Further equipped with The decryption means receives the digitally signed data from a data management device that stores the digitally signed data generated by each of the terminal devices, and decrypts the digital signature of the received digitally signed data; The calculation means calculates a hash value of the received digitally signed data, The additional verification means verifies whether the received digitally signed data or the calculated hash value of the digitally signed data matches the transmission data or the transmission hash value included in the block chain held by the other terminal device; the control means, when the additional verification means verifies the match, connects to the server device; 3. The terminal device according to claim 1 or 2.

4. a data management device that stores digitally signed data, the digital signature being generated by using a private key unique to each of the terminal devices and attached to the data generated by each of the terminal devices; The terminal device according to any one of claims 1 to 3.

5. A device connected to a network together with other terminal devices, A blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks is stored together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain together with the other terminal devices; a data management device that stores digitally signed data, the digital signature being generated by using a private key unique to each of the terminal devices and attached to the data generated by each of the terminal devices; A terminal device, A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network; The additional verification means detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device, The method further includes a control unit for disconnecting a connection to a server device that provides a service on a network when the additional verification unit detects the tampering. Terminal device.

6. the control means invalidates the retained data when the falsification is detected. The terminal device according to claim 5.

7. a digitally signed data generating means for generating digitally signed data by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by the generating and holding means; a decryption means for decrypting the electronic signature; Further equipped with The decryption means receives the digitally signed data from a data management device that stores the digitally signed data generated by each of the terminal devices, and decrypts the digital signature of the received digitally signed data; The calculation means calculates a hash value of the received digitally signed data, The additional verification means verifies whether the received digitally signed data or the calculated hash value of the digitally signed data matches the transmission data or the transmission hash value included in the block chain held by the other terminal device; the control means, when the additional verification means verifies the match, connects to the server device; 7. The terminal device according to claim 5 or 6.

8. A plurality of devices; a network to which the plurality of devices are connected; Equipped with At least one of the plurality of devices holds a blockchain in which data generated by two or more of the plurality of devices or hash values ​​of the data are linked as blocks; When a new device is added to the network, the one device adds new data generated by the new device or a hash value of the new data to the blockchain; the plurality of devices includes a plurality of terminal devices, Each terminal device holds a blockchain in which data generated by each terminal device or hash values ​​of the data are linked as blocks, When a new terminal device is added to the network, each of the terminal devices adds new data generated by the new terminal device or a hash value of the new data to the blockchain; Each of the terminal devices A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from another terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network; the plurality of terminal devices include at least a first terminal device and a second terminal device, The first terminal device detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain retained by the second terminal device; A server device for providing a service is further provided, Each of the terminal devices has a control means for disconnecting the connection with the server device, When the first terminal device detects the tampering, the control means of the first terminal device disconnects the connection with the server device. Management system.

9. the control means of the first terminal device invalidates the retained data when the falsification is detected. The management system according to claim 8.

10. Each of the terminal devices a digitally signed data generating means for generating digitally signed data by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by the generating and holding means; a decryption means for decrypting the electronic signature; Further equipped with The decryption means of the first terminal device receives the digitally signed data from a data management device that stores the digitally signed data generated by each of the terminal devices, and decrypts the digital signature of the received digitally signed data; the calculation means of the first terminal device calculates a hash value of the received digitally signed data; The additional verification means of the first terminal device verifies whether the received digitally signed data or the calculated hash value matches the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain held by the second terminal device; the control means of the first terminal device connects the first terminal device to the server device when the additional verification means verifies the match; The management system according to claim 8 or 9.

11. connected to a network together with the plurality of terminal devices, The method further includes a data management device for storing digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices. The management system according to any one of claims 8 to 10.

12. When the new terminal device is added to the network, the data management device is added with the electronic signature data to which the electronic signature formed by using a private key unique to the new terminal device is added. The management system according to claim 11.

13. when the terminal device that has been disconnected from the network reconnects to the network, the data management device transmits the stored digitally signed data to the terminal device that is to reconnect. The management system according to claim 11 or 12.

14. The data management device includes: a storage means for storing the digitally signed data; a copying means for copying the digitally signed data; a transmitting / receiving means for transmitting and receiving the data with the digital signature; a control means for controlling the storage means, the copying means, and the transmitting / receiving means; Equipped with The management system according to any one of claims 11 to 13.

15. the plurality of devices include a plurality of terminal devices and a data management device to which the plurality of terminal devices are connected; The data management device holds a block chain in which data generated by each terminal device or hash values ​​of the data are linked as blocks, When a new terminal device is added to the network, the data management device adds new data generated by the new terminal device or a hash value of the new data to the blockchain. The management system according to claim 8.

16. A plurality of terminal devices; a network to which the plurality of terminal devices are connected; Equipped with At least one of the plurality of terminal devices holds a blockchain in which data generated by two or more of the plurality of terminal devices or hash values ​​of the data are linked as blocks, When a new terminal device is added to the network, the one terminal device adds new data generated by the new terminal device or a hash value of the new data to the blockchain; connected to a network together with the plurality of terminal devices, The method further includes a data management device for storing digitally signed data obtained by adding a digital signature formed by using a private key unique to each of the terminal devices to the data generated by each of the terminal devices.

1. A management system comprising: Each of the terminal devices A generating and holding means for generating the data and holding the generated data as held data; A calculation means for calculating the generated hash value of the data; a replicating means for replicating at least one of the data and the hash value; a transmitting / receiving means for transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from another terminal device as reception data and a reception hash value; A storage means for storing the blockchain; An additional verification means for adding the received data or the received hash value to the block chain; Equipped with The addition verification means adds the new data or a hash value of the new data to the block chain when the new terminal device is added to the network; the plurality of terminal devices include at least a first terminal device and a second terminal device, The first terminal device detects tampering with the retained data by comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value transmitted by the first terminal device and included in the blockchain retained by the second terminal device; A server device for providing a service is further provided, Each of the terminal devices has a control means for disconnecting the connection with the server device, When the first terminal device detects the tampering, the control means of the first terminal device disconnects the connection with the server device. Management system.

17. the control means of the first terminal device invalidates the retained data when the falsification is detected. The management system of claim 16.

18. A blockchain in which data generated by each terminal device in a network connected together with other terminal devices or hash values ​​of the data are linked as blocks is stored in a predetermined terminal device together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain of the specified terminal device together with the other terminal devices; When the blockchain is stored in the specified terminal device together with the other terminal devices, the specified terminal device is generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; The predetermined terminal device By comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device, tampering with the retained data is detected; When the falsification is detected, the connection between the predetermined terminal device and a server device that provides a service over a network is cut off. Processing methods.

19. A blockchain in which data generated by each terminal device in a network connected together with other terminal devices or hash values ​​of the data are linked as blocks is stored in a predetermined terminal device together with the other terminal devices, When a new terminal device is added to the network, new data generated by the new terminal device or a hash value of the new data is added to the blockchain of the specified terminal device together with the other terminal devices; When the blockchain is stored in the specified terminal device together with the other terminal devices, the specified terminal device is generating the data and storing the generated data as retained data; Calculating the hash value of the generated data; Replicating at least one of the data and the hash value; transmitting at least one of the copied data and the hash value to the network as transmission data and a transmission hash value, and receiving at least one of the data and the hash value from the other terminal device as reception data and a reception hash value; Adding the received data or the received hash value to the blockchain; The predetermined terminal device By comparing the retained data or a hash value of the retained data with the transmission data or the transmission hash value included in the blockchain retained by the other terminal device, tampering with the retained data is detected; When the falsification is detected, the connection between the predetermined terminal device and a server device that provides a service over a network is cut off. A program that causes a computer to do something.

Citation Information

Patent Citations

  • A data synchronization method and device between block chains

    CN109189853A

  • Reinforcing member for connecting optical fiber

    JP1988040107A

  • Laminated material of superior fragrance retention

    JP1989080528A

  • System for approving document on internet in www base

    JP2001188739A

  • Data management method and data management system

    JP2019204216A