WO2020195746A1

WO2020195746A1 - Device management system, device management method, information processing apparatus, and program

Info

Publication number: WO2020195746A1
Application number: PCT/JP2020/010007
Authority: WO
Inventors: 篤古城; 航洋竹之下
Original assignee: 株式会社ウフル
Priority date: 2019-03-22
Filing date: 2020-03-09
Publication date: 2020-10-01
Also published as: GB2572925A; JP6656446B1; GB201910795D0; JP2020154954A

Abstract

Provided are a device management system, a device management method, an information processing apparatus, and a program which make it possible to improve the reliability of a device.　The device management system comprises: a distributed ledger which is, for example, an IOTA tangle; a registering means that registers, in the distributed ledger, at least one of manufacture time information that is information pertaining to a process of manufacturing an IoT device, startup time information that is information pertaining to a process of starting up the IoT device, and update time information that is information pertaining to a process of updating the IoT device; and an information readout means that reads out the information registered in the distributed ledger.

Description

Device management system, device management method, information processing device and program

The present invention relates to a device management system, a device management method, an information processing device and a program.

In recent years, with the spread of IoT (Internet of Things), technologies for connecting IoT devices such as sensors, cameras, and home appliances to networks, controlling these IoT devices, and utilizing data from IoT devices have been developed. It is becoming widely used. In utilizing an IoT device, it is required that the IoT device is reliable. The information that guarantees the reliability of the IoT device includes, for example, manufacturing information such as what kind of component and where the IoT device was manufactured. Information that guarantees such reliability is required not only for IoT devices but also for all other devices.
In the invention described in Patent Document 1, in the semiconductor device management device, information such as manufacturing conditions of the semiconductor device manufacturing process is recorded in a database in association with a fingerprint pattern formed on the semiconductor device. According to this configuration, it is difficult to artificially rewrite the fingerprint pattern formed on the semiconductor device, thereby increasing the reliability of the information of the semiconductor device.

Japanese Unexamined Patent Publication No. 2014-146722

However, in the technique described in Patent Document 1, information on the semiconductor device is confirmed (traced) by a database, and at that time, an electron microscope for observing the fingerprint pattern formed on the semiconductor device is required. It was. For this reason, unless an electron microscope is prepared, it is not possible to know whether or not the fingerprint pattern is forged, and it can be confirmed only in a special environment. Further, in the technique described in Patent Document 1, no consideration is given to the case where the information itself in the database is rewritten.

An object of the present invention is to provide a device management system, a device management method, an information processing device, and a program capable of improving the reliability of a device.

One embodiment of the present invention provides a network to a distributed ledger, a first information processing device connected to an information processing device constituting the distributed ledger via a network, and an information processing device constituting the distributed ledger. A second information processing device connected via a device is provided, and the first information processing device is information related to a communication unit that communicates via a network and a device manufacturing process, and can identify the device. At least one of manufacturing information including the device ID, information related to the device startup process and including the device ID, and information related to the device updating process and including the device ID. It is equipped with a processing unit that records information in a distributed ledger, and the second information processing device acquires the device ID of the device to be managed, and updates the acquired device ID with manufacturing information and startup information. It is a device management system that reads at least one of the information recorded in the distributed ledger among the time information and confirms the reliability of the managed device.
One embodiment of the present invention is to connect a network to a distributed ledger, a first information processing device connected to an information processing device constituting the distributed ledger via a network, and an information processing device constituting the distributed ledger. The first information processing device includes a second information processing device connected via the first information processing device.
It detects whether or not manufacturing time information, which is information related to the manufacturing process of the device, has been generated with the communication unit that communicates via the network, and if it is detected that manufacturing time information has occurred, the manufacturing time information is displayed. The second information processing apparatus is a device management system that includes a processing unit that records in a distributed ledger, and reads manufacturing time information from the distributed ledger to check the reliability of the device.
One embodiment of the present invention includes a communication unit that communicates with an information processing device constituting a distributed ledger via a network, and a device ID that is information related to a device manufacturing process and can identify the device at the time of manufacturing. At least one of information, information related to the device startup process and startup information including the device ID, and information related to the device update process and update time information including the device ID is stored in the distributed ledger. It is equipped with a processing unit for recording, and at least one of the information recorded in the distributed ledger among the manufacturing information, startup information, and update information is used when checking the reliability of the managed device. It is an information processing device that is information read out based on the device ID of the device to be managed.
One embodiment of the present invention detects whether or not manufacturing information, which is information related to the manufacturing process of a device, has been generated, and a communication unit that communicates with an information processing device constituting a distributed ledger via a network. , When it is detected that the manufacturing time information has been generated, it is equipped with a processing unit that records the manufacturing time information in the distributed ledger, and the manufacturing time information recorded in the distributed ledger is the reliability of the device to be managed. It is an information processing device which is information read when confirming.
One embodiment of the present invention is information related to a device manufacturing process and including a device ID that can identify the device, manufacturing information including a device ID, information related to a device activation process, and startup information including the device ID, and A device to be managed that is connected to an information processing device that constitutes a distributed ledger in which at least one of the update information including the device ID, which is information related to the device update process, is recorded via a network. Acquires the device ID, and reads at least one of the information recorded in the block chain among the manufacturing information, startup information, and update information for the acquired device ID to determine the reliability of the managed device. It is an information processing device to confirm.
One embodiment of the present invention is manufacturing including information related to a device manufacturing process and a device ID that can identify the device by the processing unit of the first information processing device connected to the distributed ledger via a network. A distributed ledger that contains at least one of the time information, the information related to the device startup process and the startup information including the device ID, and the information related to the device update process and the update time information including the device ID. The device ID of the device to be managed is acquired by the second information processing device connected to the distributed ledger via the network, and the manufacturing information and startup information of the acquired device ID are acquired. It is a device management method having to read at least one of the information recorded in the distributed ledger among the information at the time of update and to confirm the reliability of the device to be managed.
In one embodiment of the present invention, it is detected whether or not manufacturing time information, which is information related to the manufacturing process of the device, is generated by the processing unit of the first information processing device connected to the block chain via a network. However, when it is detected that the manufacturing time information has been generated, the manufacturing time information is recorded in the distributed ledger, and the distributed ledger is connected to the distributed ledger via a second information processing device via a network. It is a device management method that includes reading manufacturing information from and confirming the reliability of the device.
One embodiment of the present invention is manufacturing information including a device ID which is information related to a device manufacturing process and can identify a device to a computer connected to an information processing device constituting a distributed ledger via a network. , Information related to the device startup process and including the device ID, and at least one of the information related to the device update process and the update information including the device ID are recorded in the block chain. At least one of the manufacturing information, startup information, and update information recorded in the blockchain is managed when checking the reliability of the managed device. It is a program that is information read out based on the device ID of the device.
One embodiment of the present invention detects whether or not manufacturing time information, which is information related to the manufacturing process of a device, is generated in a computer connected to an information processing device constituting a distributed ledger via a network. When it is detected that the manufacturing information has been generated, the manufacturing information is recorded in the blockchain, and the manufacturing information recorded in the blockchain confirms the reliability of the managed device. It is a program that is information read at the time.
One embodiment of the present invention is information related to a device manufacturing process and including a device ID that can identify a device, manufacturing information including a device ID, information related to a device activation process, and startup information including a device ID, and A device to be managed by an information processing device and a computer connected to a network that form a distributed ledger in which at least one piece of update information including a device ID, which is information related to a device update process, is recorded. Device ID is acquired, and at least one of the information recorded in the distributed ledger among the manufacturing information, startup information, and update information for the acquired device ID is read out to determine the reliability of the managed device. It is a program that executes to confirm.

According to the present invention, it is possible to provide a device management system, a device management method, an information processing device, and a program capable of improving the reliability of the device.

It is a block diagram which shows the structure of the device management system which concerns on 1st Embodiment of this invention. It is a block diagram which shows about the IoT device managed by the device management system 1 shown in FIG. It is a block diagram which shows the structure of the terminal apparatus which is an example of the information processing apparatus 2 shown in FIG. It is a block diagram which shows the structure of the device which is an example of the IoT device 5 shown in FIG. It is a figure which shows the structure which applied an example of the distributed ledger technology in the device management system 1 shown in FIG. It is a figure which shows the tangle which is an example of the distributed ledger which records the information about the device to be managed in the device management system 1 shown in FIG. FIG. 3 is a block diagram showing a configuration related to bookkeeping of manufacturing information of a device managed by the device management system 1 shown in FIG. 1. FIG. 5 is a flowchart showing a process related to bookkeeping of manufacturing information of a device managed by the device management system 1 shown in FIG. FIG. 5 is a block diagram showing a configuration related to bookkeeping of start-up information of a device managed by the device management system 1 shown in FIG. It is a flowchart which shows the process which concerns on the recording of the start-up information of the device managed by the device management system 1 shown in FIG. FIG. 5 is a block diagram showing a configuration related to bookkeeping of update information of a device managed by the device management system 1 shown in FIG. 1. It is a flowchart which shows the process which concerns on the recording of the update information of the device managed by the device management system 1 shown in FIG. FIG. 5 is a flowchart showing a process of recording update information of a device managed by the device management system 1 shown in FIG. 1 at predetermined time intervals. FIG. 5 is a block diagram showing a configuration in which the device management system 1 shown in FIG. 1 refers to the device manufacturing time-use block chain 101 and the device change history block chain 102. It is a flowchart which shows the process which refers to the block chain 101 for device manufacturing and the block chain 102 for device change history in the device management system 1 shown in FIG. It is a block diagram which shows the structure of Example 1 to which the device management system by this invention was applied. It is a block diagram which shows the structure of Example 2 which applied the device management system by this invention.

Hereinafter, embodiments of the device management system according to the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing a configuration of a device management system according to the first embodiment of the present invention. The device management system 1 of the present embodiment is configured by connecting a plurality of information processing devices 2 via a network 3. The network 3 is, for example, a P2P (peer-to-peer) type network. The network 3 may be a wired network or a wireless network. The network 3 is, for example, an internet network. The device management system 1 utilizes a distributed ledger technology (Distributed Ledger Technology). Each of the plurality of information processing devices 2 constitutes a node in the distributed ledger technology. In the device management system 1 of the present embodiment, the Tangle of IOTA is used as a distributed ledger, but the present invention is not limited to this, and other distributed ledger may be used. For example, as a distributed ledger, an Ethereum blockchain may be used.

FIG. 2 is a block diagram showing an IoT device managed by the device management system 1 shown in FIG. The device management system 1 manages the IoT device 5. The IoT device 5 is connected to the information processing device 2 by the network 4. The information processing device 2 controls the operation of the IoT device 5. The network 4 may be a wired network or a wireless network. The network 4 is, for example, an internet network. The IoT device 5 may be any sensor that detects a natural phenomenon such as temperature, humidity, pressure, light amount, and volume, and a known fluctuation amount such as a moving speed of an object or a position and its acceleration. Further, the IoT device 5 may be a camera capable of photographing the surroundings. Further, the IoT device 5 may be any product such as a home electric appliance such as an air conditioner, an automobile, or a robot. In the device management system 1 of the present embodiment, the device to be managed is an IoT device, but the present invention is not limited to this, and the device management system according to the present invention manages devices that are not connected by a network. It may be a thing. The IoT device 5 may be a device that constitutes a node in the distributed ledger technology.

FIG. 3 is a block diagram showing a configuration of a terminal device which is an example of the information processing device 2 shown in FIG. The information processing device 2 may be a device generally called a personal computer, a workstation, a mainframe, or a device called a supercomputer. Further, the information processing device 2 may be a device called a smartphone or a tablet. Further, the information processing device 2 may be various devices having a function peculiar to the device such as a sensor function and a camera function in addition to the function of the computer. Here, the configuration of the terminal device 11 as an example of the information processing device 2 will be described. The terminal device 11 includes a processing unit 12 that performs various processes, an input / output unit 13 that performs input / output to and from the operator, a storage unit 14 that stores programs and various data operated by the processing unit 12, a network 3, and a network 3. It is configured to include a communication unit 15 that performs communication via the network 4. The terminal device 11 may be a device managed by the device management system 1 of the present embodiment. All devices that can be connected to the Internet are IoT devices managed by the device management system 1 of the present embodiment.

The processing unit 12 is an arithmetic unit called a CPU or MPU. The processing unit 12 executes the program stored in the storage unit 14. The input / output unit 13 is an input / output device such as a keyboard, a mouse, and a display. The storage unit 14 may be any known storage device such as a RAM, a ROM, a hard disk, a magnetic storage device, and an optical storage device. Each of the plurality of information processing devices 2 may have the same configuration, or each device may have a configuration different from that of the other devices.

FIG. 4 is a block diagram showing a device configuration which is an example of the IoT device 5 shown in FIG. The device 16 includes a processing unit 17 that performs various processes, a device function execution unit 18 that executes a function peculiar to the device, a storage unit 19 that stores programs and various data operated by the processing unit 17, and a network 4. It is configured to include a communication unit 20 that performs communication via the above. The processing unit 17 is an arithmetic unit called a CPU or MPU. The processing unit 17 executes the program stored in the storage unit 19. The storage unit 14 may be any known storage device such as a RAM, a ROM, a hard disk, a magnetic storage device, and an optical storage device. Each of the plurality of information processing devices 2 may have the same configuration, or each device may have a configuration different from that of the other devices.

The device function execution unit 18 is configured to execute a function peculiar to the device. When the device 16 is a sensor, the device function execution unit 18 includes a detection element that detects an object, a control unit that controls the detection element, and the like. When the device 16 is a camera, the device function execution unit 18 includes an image sensor that images the surroundings, an image processing unit that performs image processing on the image captured by the image sensor, and an image sensor and an image processing unit. It has a control unit to control. When the device 16 is an air conditioner, the device function execution unit 18 includes a drive unit that drives each configuration related to the refrigeration cycle, a detection unit that detects temperature and humidity, and a control unit that controls the drive unit and the detection unit. Has. When the device 16 is an automobile, the device function execution unit 18 is a drive unit that drives each configuration related to the running of the automobile, a detection unit that detects a situation related to safety outside the vehicle, a situation related to comfort inside the vehicle, and the like. It also has a control unit that controls a drive unit and a detection unit. When the device 16 is a robot, the device function execution unit 18 includes a drive unit that drives the robot, a detection unit that detects the surrounding conditions of the robot, and a control unit that controls the drive unit and the detection unit. When the device 16 is a robot, the robot may manufacture an IoT device to be managed by the device management system 1 of the present embodiment. By doing so, a more reliable IoT device can be manufactured.

FIG. 5 is a diagram showing a configuration in which an example of the distributed ledger technology is applied in the device management system 1 shown in FIG. The device management system 1 of the present embodiment has, as nodes, a full node having a tangle, which is an example of a distributed ledger, and a light wallet having no tangle. A full node synchronizes its own tangle with the tangles of other full nodes. A light wallet is also called a light node. Here, the light wallet is called a light node. Since the light node does not have a tangle by itself, there is no need to manage the tangle, so the operational burden is small, but when operating with information obtained from the full node, there is a slight delay in processing due to communication time. There is a risk. In a full node, there is a burden of managing the tangle by itself, but by using the tangle of its own, there is no need for communication and it is possible to operate without depending on other devices. In the device management system 1, charges may be charged for the exchange of information between or within each device. Although the amount charged for sending and receiving a small amount of information is small, it is possible to build a system suitable for micropayment by paying the amount charged with IOTA, which is a virtual currency. The information processing device 2, the IoT device 5, the terminal device 11, and the device 16 may be full nodes or light nodes.

FIG. 6 is a diagram showing a tangle which is an example of a distributed ledger for recording information about a device to be managed in the device management system 1 shown in FIG. The tangle uses a DAG (Directed Acyclic Graph). In the device management system 1 shown in FIG. 1, recording information in the distributed ledger means recording a transaction (TX) in the tangle. Proof of work (PoW) is performed when recording a new transaction. By using the IOTA tangle as a blockchain, the speed of posting to the blockchain can be increased.

FIG. 7 is a block diagram showing a configuration related to bookkeeping of manufacturing information of the device managed by the device management system 1 shown in FIG. The device manufacturing blockchain 101 is a blockchain that records manufacturing information, which is information related to the manufacturing process of a device managed by the device management system 1 (hereinafter, referred to as “managed device”). The device manufacturing distributed ledger 101 is a tangle possessed by the full nodes constituting the device management system 1. The terminal device 11 records the manufacturing time information 16a in the device manufacturing time distributed ledger 101. The manufacturing time information 16a is a transaction in the device manufacturing time distribution ledger 101. The manufacturing information 16a is information when manufacturing the managed device. The manufacturing time information 16a is generated each time the parts constituting the managed device are selected and assembled in the manufacturing process of the managed device. For example, in the manufacturing process of a managed device, when the circuit board A, which is a component constituting the managed device, is selected and the electronic component B (CPU, memory, etc.) is mounted on the circuit board A, the managed device is used. On the other hand, the manufacturing information 16a for the circuit board A is generated, and the manufacturing information 16a for the electronic component B is generated.

The manufacturing information 16a can specify a device ID that can identify the managed device, a component ID that can identify the parts constituting the managed device, and a manufacturing line that incorporates the component indicated by the component ID into the managed device. The production line ID and the production time information indicating the time when the component indicated by the component ID is incorporated into the managed device are included. Further, the manufacturing time information 16a is information in which the part ID, the manufacturing line ID, and the manufacturing time information are associated with the device ID. The manufacturing line ID may include a worker person in charge ID or a manufacturing device (robot) ID in order to identify a worker or a manufacturing device.

FIG. 8 is a flowchart showing a process related to bookkeeping of manufacturing information of the device managed by the device management system 1 shown in FIG. FIG. 8 shows a process executed by the terminal device 11. First, the processing unit 12 of the terminal device 11 detects whether or not there is newly generated manufacturing time information 16a (step S801). The manufacturing person may operate the input / output unit 13 of the terminal device 11 to input the manufacturing information 16a to the terminal device 11. Further, when the robot manufactures the managed device, the robot may input the manufacturing time information 16a to the terminal device 11 via the communication unit 15 of the terminal device 11.

If there is newly generated manufacturing time information 16a in step S801, the processing unit 12 records the manufacturing time information 16a in the device manufacturing time distribution ledger 101 (step S802), and ends the process. .. If there is no newly generated manufacturing information 16a in step S801, the processing unit 12 ends the processing as it is. The terminal device 11 recorded in the device manufacturing distributed ledger 101 may be either the information processing device 2, the IoT device 5, or the device 16, or may be the managed device itself. Generally, the device manufacturing process is divided into a plurality of processes such as component mounting, assembly, and inspection. The manufacturing information 16a may be recorded for each process, or may be recorded at least once in the final assembly / inspection process.

FIG. 9 is a block diagram showing a configuration related to bookkeeping of device startup information managed by the device management system 1 shown in FIG. The device change history distributed ledger 102 is a distributed ledger for recording startup information 16b, which is information related to the startup process of the managed device. The device change history distributed ledger 102 is a tangle possessed by the full nodes constituting the device management system 1. The device change history distributed ledger 102 may be the same distributed ledger as the device manufacturing distributed ledger 101. The terminal device 11 records the startup information 16b in the device change history distributed ledger 102. The startup information 16b is a transaction in the device change history distributed ledger 102. The startup information 16b is information when the managed device is activated. The managed device manufactured in the manufacturing process performs the activation process at the time of activation. In this activation process, the managed device is initialized and activated. In the present embodiment, the managed device has a ROM that stores the program, a CPU that executes the program stored in the ROM, and a secure element. The secure element may be a TPM (Trusted Platform Module) having tamper resistance, a SIM (Subscriber Identity Module), a SAM (Security Application Module), or any other known configuration. The secure element does not necessarily have to have tamper resistance as long as it has a function that can store the verification key of the digital signature. For example, it uses a mechanism called TrustZone that exists in the CPU separately from the normal memory. You may. When the activation process of the managed device is executed, the activation information 16b is generated.

The startup information 16b includes a device ID that can identify the managed device, verification time information indicating the time when the startup process of the managed device was performed, and a hash of a file of a program or data used in the startup process of the managed device. Includes values and digital signatures by managed devices. Further, the startup information 16b is information in which the verification time information, the hash value, and the digital signature are associated with the device ID.

FIG. 10 is a flowchart showing a process related to bookkeeping of device startup information managed by the device management system 1 shown in FIG. FIG. 10 shows a process executed by the terminal device 11. First, the processing unit 12 of the terminal device 11 detects whether or not there is newly generated start-up information 16b (step S1001). The managed device may input the startup information 16b into the terminal device 11 via the communication unit 15 of the terminal device 11. The managed device itself may record the startup information 16b in the device change history distributed ledger 102.

If there is newly generated startup information 16b in step S1001, the processing unit 12 records the current startup information 16b in the device change history distributed ledger 102 (step S1002), and ends the process. .. In step S1001, if there is no newly generated start-up information 16b, the processing unit 12 ends the processing as it is. The terminal device 11 recorded in the device change history distributed ledger 102 may be either the information processing device 2, the IoT device 5, or the device 16, or may be the managed device itself.

FIG. 11 is a block diagram showing a configuration related to bookkeeping of update information of the device managed by the device management system 1 shown in FIG. The device change history distributed ledger 102 is a distributed ledger that records the update information 16c, which is information related to the update process of the managed device, in addition to the startup information 16b. The device change history distributed ledger 102 is a tangle possessed by the full nodes constituting the device management system 1. The terminal device 11 records the update information 16c in the device change history distributed ledger 102. The update information 16c is a transaction in the device change history distributed ledger 102. The update information 16c is information when updating the managed device. The managed device activated in the activation process executes an update process for updating the program during operation. For example, a managed device is a program that receives firmware patches, programs that add new functions in functions specific to managed devices, programs that fix bugs, and various data via the Internet, and is managed. Update the program that runs on the device. In the present embodiment, the managed device has a firmware (FW) executed by the managed device, a program executed by the managed device, and a data file (File) used for execution. Firmware is also a type of program. When the update process of the managed device is executed, the update information 16c is generated. The process of updating the managed device may include updating the firmware and the config file of the managed device by, for example, the terminal device 11. In this case, the terminal device 11 records the update information 16c regarding the update in the device change history distributed ledger 102.

The update information 16c includes a device ID that can identify the managed device, verification time information indicating the time when the update process of the managed device was performed, and a hash of a file of a program or data used in the update process of the managed device. Includes values and digital signatures by managed devices. Further, the update information 16c is information in which the verification time information, the hash value, and the digital signature are associated with the device ID.

FIG. 12 is a flowchart showing a process related to bookkeeping of update information of the device managed by the device management system 1 shown in FIG. FIG. 12 shows a process executed by the terminal device 11. First, the processing unit 12 of the terminal device 11 detects whether or not there is newly generated update information 16c (step S1201). The managed device may input the update information 16c to the terminal device 11 via the communication unit 15 of the terminal device 11. The managed device itself may record the update information 16c in the device change history distributed ledger 102.

If there is newly generated update information 16c in step S1201, the processing unit 12 records the current update information 16c in the device change history distributed ledger 102 (step S1202), and ends the process. .. In step S1201, if there is no newly generated update information 16c, the processing unit 12 ends the processing as it is. The terminal device 11 recorded in the device change history distributed ledger 102 may be either the information processing device 2, the IoT device 5, or the device 16, or may be the managed device itself.

It should be noted that the terminal device 11 is not only when there is new update information 16c (when it is updated), but also when it is updated to indicate the current state of the managed device at predetermined time intervals even if it is not updated. The information 16c may be recorded in the device change history distributed ledger 102. The update information 16c indicating the status of the current managed device includes a device ID that can identify the managed device, verification time information indicating the current time, and a file of programs and data currently being executed on the managed device. Includes the hash value of and the digital signature of the managed device. Further, the update information 16c is information in which the verification time information, the hash value, and the digital signature are associated with the device ID.

FIG. 13 is a flowchart showing a process of recording update information of the device managed by the device management system 1 shown in FIG. 1 at predetermined time intervals. FIG. 13 shows a process executed by the terminal device 11. First, the processing unit 12 of the terminal device 11 confirms whether a predetermined time has elapsed from the recording of the previous update information 16c (step S1301). The predetermined time determined in step S1301 may be determined according to the frequency at which the managed device may be tampered with. Further, the predetermined time may be a fixed time or may be changed. The managed device may input the update information 16c to the terminal device 11 via the communication unit 15 of the terminal device 11. The managed device itself may record the update information 16c in the device change history distributed ledger 102.

In step S1301, when the predetermined time has elapsed, the processing unit 12 records the current startup information 16b in the device change history distributed ledger 102 (step S1302), and ends the process. If the predetermined time does not elapse in step S1301, the processing unit 12 ends the processing as it is. The terminal device 11 recorded in the device change history distributed ledger 102 may be either the information processing device 2, the IoT device 5, or the device 16, or may be the managed device itself. According to the process shown in FIG. 13, even though the managed device has been updated, it is possible to respond to tampering that pretends to be in an unupdated state, and the current status of the managed device is correct. It is reflected in the device change history distributed ledger 102.

FIG. 14 is a block diagram showing a configuration in which the device management system 1 shown in FIG. 1 refers to the device manufacturing time distributed ledger 101 and the device change history distributed ledger 102. In the device management system 1, for example, the terminal device 11 has a manufacturing time information 16a recorded in the device manufacturing distributed ledger 101, a startup information 16b recorded in the device change history distributed ledger 102, and a device change history. Refer to the update information 16c recorded in the distributed ledger 102.

FIG. 15 is a flowchart showing a process of referring to the device manufacturing time distributed ledger 101 and the device change history distributed ledger 102 in the device management system 1 shown in FIG. FIG. 15 shows a process executed by the terminal device 11. First, the terminal device 11 determines whether or not a process for confirming the reliability of the managed device has occurred (step S1501). The process of confirming the reliability of a managed device includes, for example, a process of confirming the state of the managed device when there is some suspicious movement in the operation of the managed device. The process of confirming the reliability of a managed device includes, for example, a process of confirming the reliability of the managed device when using data from a certain managed device. The process of confirming the reliability of the managed device includes, for example, a process of confirming the reliability of the managed device when driving and controlling a certain managed device. The process of confirming the reliability of a managed device includes, for example, a process of confirming the status of a managed device when an audit of the managed device becomes necessary.

If the process of confirming the reliability of the managed device has not occurred in step S1501, the terminal device 11 ends the process as it is. When a process for confirming the reliability of the managed device occurs in step S1501, in step S1502, the terminal device 11 assigns a device ID for specifying which device is the managed device for which the reliability is confirmed this time. get. The device ID may be acquired by being input from the input / output unit 13, may be acquired by receiving from the outside via the communication unit 15, or may be read from the storage unit 14. You may get it by. Further, in step S1502, the terminal device 11 reads the manufacturing time information 16a about the acquired device ID from the device manufacturing time distribution type ledger 101, and reads the acquired device ID startup information 16b from the device change history distribution type. Read from the ledger 102, and read the updated information 16c about the acquired device ID from the device change history distributed ledger 102.

Subsequently, the terminal device 11 determines the manufacturing information 16a, the startup information 16b, and the update information 16c read in step S1501 and confirms the current reliability of the managed device (step S1503). In step S1504, the process is terminated after performing control based on the current reliability of the managed device, which is the determination result of step S1503. For example, if the manufacturing information 16a read from the device manufacturing blockchain 101 contains information about parts other than the originally planned parts, it is possible to perform control without using the managed device. it can. Further, for example, when the update information 16c read from the device change history distributed ledger 102 includes information about a non-genuine update, control can be performed without using the managed device. .. Further, for example, if there is no suspicious point in the manufacturing information 16a, the startup information 16b, and the updating information 16c, it is possible to control the managed device to be used as a reliable device. The terminal device 11 that executes the process of FIG. 15 may be either the information processing device 2, the IoT device 5, or the device 16, or may be the managed device itself. As described above, according to the present embodiment, it is possible to provide a traceable environment for the managed device. Further, according to the present embodiment, it is possible to provide a third party with a basis for claiming that the managed device is a legitimate device.

FIG. 16 is a block diagram showing a configuration of Example 1 to which the device management system according to the present invention is applied. The present embodiment is an example in which the device management system according to the present invention is applied to a person tracking system that tracks the footprints of a person. The person tracking system 1600 has

surveillance cameras

1606, 1607 and 1608 that are managed devices. Information at the time of manufacture, start-up, and update of the

surveillance cameras

1606, 1607, and 1608 is recorded in the distributed ledger 1602 at any time. The reliability of

surveillance cameras

1606, 1607 and 1608 is guaranteed by the blockchain 1602. The decentralized ledger 1602 refers to the decentralized ledger 1601 in which the evidence on which the reliable device is sufficient is recorded.

The face image of the person 1605 is recorded in the distributed ledger 1604. The

surveillance cameras

1606, 1607 and 1608 collate the face image recorded in the distributed ledger 1604 with the face image of the person photographed by the person 1605, so that the person 1605 can set the installation position of the

surveillance cameras

1606, 1607 and 1608. Acquire the action history that passed. This action history is recorded in the distributed ledger 1603. When recording the action history, the distributed ledger 1602 is referred to, and the reliability of the shooting results of the

surveillance cameras

1606, 1607 and 1608 is guaranteed. At the store 1609, the distributed ledger 1603 can be referred to to analyze the behavior pattern and purchase tendency of the person 1605, which can be used for product purchase and product development.

FIG. 17 is a block diagram showing a configuration of Example 2 to which the device management system according to the present invention is applied. This embodiment is an example in which the device management system according to the present invention is applied to a dangerous vehicle discrimination system for discriminating a dangerous driving vehicle. The dangerous vehicle discrimination system 1700 has

surveillance cameras

1705 and 1706 which are managed devices.

Surveillance cameras

1705 and 1706 are mounted on the vehicle 1704. The surveillance camera 1705 photographs the front of the vehicle 1704 and captures the driving situation of the preceding vehicle 1707. The surveillance camera 1706 photographs the rear of the vehicle 1704 and captures the driving situation of the following vehicle 1708. Information at the time of manufacture, start-up, and update of the

surveillance cameras

1705 and 1706 is recorded in the distributed ledger 1702 at any time. The reliability of

surveillance cameras

1705 and 1706 is guaranteed by the blockchain 1702. The decentralized ledger 1702 refers to the decentralized ledger 1701 in which the evidence on which the reliable device is sufficient is recorded.

The driving status and vehicle number of the preceding vehicle and the following vehicle taken by the

surveillance cameras

1705 and 1706 are recorded in the distributed ledger 1703. In addition, the

surveillance cameras

1705 and 1706 can acquire the vehicle number of the vehicle that has driven dangerously in the past by referring to the contents recorded in the distributed ledger 1703 in the past. The

surveillance cameras

1705 and 1706 match the vehicle numbers of the preceding vehicle and the following vehicle that are currently being photographed with the vehicle numbers of the vehicles that have been dangerously driven in the past obtained from the distributed ledger 1703, thereby causing the preceding vehicle and the following vehicle to collide with each other. It is possible to notify the smartphone 1710 of the driver driving the vehicle 1704 or the navigation system 1709 mounted on the vehicle 1704 about the risk of the vehicle driving dangerously.

(1) In the present invention, the distributed ledger (distributed ledger 101 for device manufacturing, distributed ledger 102 for device change history), manufacturing information which is information related to the device manufacturing process, and activation of the device. Bookkeeping means (S802, S1002, S1202, S1302) for recording at least one of the start-up information, which is information related to the process, and the update time information, which is information related to the device update process, in the block chain. It is characterized by having an information reading means (S1502) for reading the information recorded in the distributed ledger. This provides a device management system capable of improving the reliability of the device. Further, by recording the information about the device in the distributed ledger, it is possible to prevent the information from being tampered with. In addition, by recording in a public blockchain, it is possible to provide a system in which anyone can refer to information about the device, and anyone can confirm the reliability of the device.

(2) Further, the present invention is characterized in that the distributed ledger is a tangle (see FIG. 6). As a result, it is possible to record in the block chain in real time. Also, unlike other decentralized ledgers that require a fee for bookkeeping, bookkeeping in the decentralized ledger can be done free of charge. In addition, it is possible to provide a scalable system. In addition, it is possible to provide a system having a high affinity with micropayments using the virtual currency IOTA.

(3) Further, in the present invention, the manufacturing information incorporates a device ID capable of identifying the device, a component ID capable of identifying a component constituting the device, and a component indicated by the component ID into the device. It is information that includes a manufacturing line ID that can identify the manufacturing line and manufacturing time information that indicates the time when the component indicated by the component ID is incorporated into the device, and each information is linked to the device ID. It is a feature. As a result, it is possible to provide a system with improved reliability at the time of manufacturing the device.

(4) Further, in the present invention, the startup information includes a device ID that can identify the device, verification time information indicating the time when the device activation process is performed, and a file used for the device activation process. The hash value and the digital signature by the device are included, and each information is associated with the device ID. As a result, it is possible to provide a system with improved reliability at the time of device startup.

(5) Further, in the present invention, the update time information includes a device ID that can identify the device, verification time information indicating the time when the device update process is performed, and a file used for the device update process. The hash value and the digital signature by the device are included, and each information is associated with the device ID. As a result, it is possible to provide a system with improved reliability when updating the device.

(6) Further, the present invention is characterized in that the digital signature is a digital signature obtained by encrypting the hash value of the file with a private key. This also makes it possible to make it more difficult for the information about the device recorded in the block chain to be tampered with.

(7) Further, the present invention is characterized in that the device is an IoT device. As a result, it is possible to increase the reliability of IoT devices that may be attacked by malware or the like by being connected to the Internet. Further, according to the present invention, even if the program that controls the IoT device is rewritten by malware, for example, the rewritten program is recorded in the distributed ledger, so that the current state of the IoT device can be known. , The operator can obtain a judgment material for deciding whether or not to utilize the IoT device.

(8) Further, the present invention is a device management method for managing a device using a computer, which is manufacturing information which is information related to a device manufacturing process and startup information which is information related to the device starting process. A bookkeeping step of recording information and at least one of update information, which is information related to the device update process, in a distributed ledger, and an information reading step of reading information recorded in the distributed ledger. It is characterized by having. This provides a device management method that can improve the reliability of the device. Further, by recording the information about the device in the distributed ledger, it is possible to prevent the information from being tampered with. In addition, by posting in a public blockchain, it is possible to provide a method in which anyone can refer to information about the device, and anyone can confirm the reliability of the device.

(9) Further, in the information processing apparatus, the present invention relates to manufacturing information which is information related to a device manufacturing process, startup information which is information related to the device activation process, and information related to the device updating process. It is characterized by having a recording means for recording at least one of the updated information in the distributed ledger. As a result, the information processing device records the information about the device in the distributed ledger, so that the information about the device is less likely to be falsified, and highly reliable information can be provided.

(10) Further, in the IoT device, the present invention includes manufacturing information which is information related to the manufacturing process of the device, startup information which is information related to the activation process of the device, and information related to the updating process of the device. It is characterized by having a bookkeeping means for recording at least one of the update information in a distributed ledger. As a result, the IoT device records the information about the device in the distributed ledger, so that the information about the device is less likely to be tampered with, and highly reliable information can be provided.

(11) Further, in the program, the present invention includes manufacturing information which is information related to a device manufacturing process, startup information which is information related to the device activation process, and information related to the device updating process. The computer functions as a bookkeeping means for recording at least one of the update information in the block chain. This provides a program that can improve the reliability of the device. Further, by recording the information about the device in the distributed ledger, it is possible to prevent the information from being tampered with. In addition, by recording in a public block chain, it is possible to provide a program in which anyone can refer to information about the device, and anyone can check the reliability of the device.

(12) Further, the present invention is characterized in that the distributed ledger is a tangle in the program. As a result, it is possible to record in the block chain in real time. Also, unlike other decentralized ledgers that require a fee for bookkeeping, bookkeeping in the decentralized ledger can be done free of charge. In addition, it is possible to provide a scalable program. In addition, it is possible to provide a program having a high affinity with micropayments using the virtual currency IOTA.

(13) Further, in the program, the manufacturing information includes a device ID capable of identifying the device, a component ID capable of identifying a component constituting the device, and a component indicated by the component ID. The information includes a manufacturing line ID capable of specifying the manufacturing line incorporated in the device and manufacturing time information indicating the time when the component indicated by the component ID is incorporated in the device, and each information is associated with the device ID. It is characterized by being. As a result, it is possible to provide a program with increased reliability when manufacturing the device.

(14) Further, in the program, the startup information includes a device ID that can identify the device, verification time information indicating the time when the device activation step is performed, and the device activation process. It is characterized in that the information includes the hash value of the file used and the digital signature by the device, and each information is associated with the device ID. As a result, it is possible to provide a program with improved reliability at the time of starting the device.

(15) Further, in the program, the update time information includes a device ID that can identify the device, verification time information indicating the time when the device update process is performed, and the device update process. It is characterized in that the information includes the hash value of the file used and the digital signature by the device, and each information is associated with the device ID. As a result, it is possible to provide a program with improved reliability when updating the device.

(16) Further, the present invention is characterized in that, in a program, the bookkeeping means records the manufacturing time information in the distributed ledger when the device is manufactured by the manufacturing process. As a result, it is possible to provide a program with increased reliability when manufacturing the device.

(17) Further, the present invention is characterized in that, in a program, the bookkeeping means records the startup information in the distributed ledger when the device is activated by the activation step. As a result, it is possible to provide a program with improved reliability at the time of starting the device.

(18) Further, the present invention is characterized in that, in a program, the bookkeeping means records the update time information in the distributed ledger when the device is updated by the update step. As a result, it is possible to provide a program with improved reliability when updating the device.

(19) Further, the present invention is characterized in that, in a program, the bookkeeping means records the update information in the distributed ledger at predetermined time intervals. As a result, the status of the device can be confirmed at predetermined time intervals, and a program with enhanced device reliability can be provided.

Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes can be made within the scope of the gist thereof. These embodiments and modifications thereof are included in the scope and gist of the invention, and at the same time, are included in the scope of the invention described in the claims and the equivalent scope thereof.

This application claims priority based on Japanese Patent Application No. 2019-54461, which is a Japanese patent application filed on March 22, 2019, and incorporates all the contents described in the Japanese patent application.

1 Device management system 2 Information processing device 3 Network 4 Network 5 IoT device 11 Terminal device 12 Processing unit 13 Input / output unit 14 Storage unit 15 Communication unit 16 Device 17 Processing unit 18 Device function execution unit 19 Storage unit 20 Communication unit 101 Device manufacturing Distributed ledger for time 102 Distributed ledger for device change history

16a Manufacturing information

16b Startup information 16c Update information

Claims

Blockchain and
A first information processing device connected to the information processing device constituting the block chain via a network, and
A second information processing device connected to the information processing device constituting the distributed ledger via a network is provided.
The first information processing device is
With the communication unit that communicates via the network
Manufacturing process information related to the device manufacturing process including a device ID that can identify the device, starting information related to the device activation process including the device ID, and updating process of the device. A processing unit that records at least one piece of information at the time of update including the device ID in the distributed ledger is provided.
The second information processing apparatus acquires the device ID of the device to be managed, and the distributed ledger of the manufacturing information, the startup information, and the update information for the acquired device ID. A device management system that reads at least one of the information recorded in the device and confirms the reliability of the managed device.
Blockchain and
A first information processing device connected to the information processing device constituting the block chain via a network, and
A second information processing device connected to the information processing device constituting the distributed ledger via a network is provided.
The first information processing device is
With the communication unit that communicates via the network
A processing unit that detects whether or not manufacturing time information, which is information related to the manufacturing process of the device, has been generated, and if it is detected that the manufacturing time information has been generated, records the manufacturing time information in the block chain. And with
The second information processing device is a device management system that reads the manufacturing time information from the distributed ledger and confirms the reliability of the device.
Information processing devices that make up the block chain and the communication unit that communicates via the network,
Manufacturing process information related to the device manufacturing process including a device ID that can identify the device, starting information related to the device activation process including the device ID, and updating process of the device. A processing unit that records at least one piece of information at the time of update including the device ID in the distributed ledger is provided.
At least one of the information recorded in the distributed ledger among the manufacturing information, the startup information, and the update information is the managed device when confirming the reliability of the managed device. Information processing device, which is information read out based on the device ID of the above.
Information processing devices that make up the block chain and the communication unit that communicates via the network,
A processing unit that detects whether or not manufacturing time information, which is information related to the manufacturing process of the device, has been generated, and if it is detected that the manufacturing time information has been generated, records the manufacturing time information in the block chain. And with
The information processing device, which is information to be read when confirming the reliability of the device to be managed, is the manufacturing information recorded in the distributed ledger.
Information related to the manufacturing process of the device and including the device ID that can identify the device, information related to the booting process of the device and booting information including the device ID, and updating process of the device. It is connected to the information processing device constituting the distributed ledger in which at least one of the update information including the device ID is recorded via a network.
The device ID of the device to be managed is acquired, and at least one of the manufacturing information, the startup information, and the update information of the acquired device ID is recorded in the distributed ledger. An information processing device that reads out and confirms the reliability of the managed device.
The manufacturing information includes a device ID that can identify the device, a component ID that can identify the parts constituting the device, and a manufacturing line that can specify a manufacturing line in which the component indicated by the component ID is incorporated into the device. Information that includes an ID and manufacturing time information indicating the time when the component indicated by the component ID is incorporated into the device, and links the component ID, the manufacturing line ID, and the manufacturing time information to the device ID. is there,
The information processing device according to any one of claims 3 to 5.
The manufacturing information is recorded in the blockchain when the device is manufactured by the manufacturing process.
The information processing device according to any one of claims 3 to 5 and 6.
The start-up information includes verification time information indicating the time when the start-up process of the device is performed, a hash value of a file used in the start-up step of the device, and a digital signature by the device. This is information in which the verification time information indicating the execution time, the hash value of the file used in the activation process, and the digital signature are associated with the device ID.
The information processing device according to claim 3 or 5.
The digital signature included in the startup information is a digital signature obtained by encrypting the hash value of the file used in the startup process with a private key.
The information processing device according to any one of claims 3, 5 and 8.
The start-up information is recorded in the blockchain when the device is started by the start-up process.
The information processing device according to any one of claims 3, 5, 8 and 9.
The update time information includes verification time information indicating the time when the device update process was performed, a hash value of a file used in the device update process, and a digital signature by the device, and the update process is performed. This is information in which the verification time information indicating the time of execution, the hash value of the file used in the update process, and the digital signature are associated with the device ID.
The information processing apparatus according to any one of claims 3, 5, 8 to 10.
The digital signature included in the update information is a digital signature obtained by encrypting the hash value of the file used in the update process with a private key.
The information processing apparatus according to any one of claims 3, 5, 8 to 11.
The update information is recorded in the blockchain when the device is updated by the update process.
The information processing apparatus according to any one of claims 3, 5, 8 to 12.
The update information is recorded in the blockchain at predetermined time intervals.
The information processing apparatus according to any one of claims 3, 5, 8 to 13.
The blockchain is a tangle,
The information processing device according to any one of claims 3 to 14.
The device is an IoT device,
The information processing device according to any one of claims 3 to 15.
By the processing unit of the first information processing device connected to the block chain via a network, information related to the manufacturing process of the device, manufacturing information including a device ID that can identify the device, and activation of the device. At least one of the information related to the process and the start-up information including the device ID and the information related to the update process of the device and the update information including the device ID is recorded in the block chain. To do and
The device ID of the device to be managed is acquired by the second information processing device connected to the block chain via the network, and the manufacturing information and the startup information of the acquired device ID are obtained. To confirm the reliability of the managed device by reading at least one of the updated information and the information recorded in the distributed ledger.
Device management method with.
The processing unit of the first information processing apparatus connected to the block chain via a network detects whether or not manufacturing time information, which is information related to the device manufacturing process, has been generated, and the manufacturing time information is generated. When it is detected that the information has been processed, the manufacturing information is recorded in the distributed ledger.
A device management method comprising reading the manufacturing time information from the distributed ledger by a second information processing device connected to the distributed ledger via a network and confirming the reliability of the device.
To a computer connected to the information processing devices that make up the block chain via a network
Manufacturing process information related to the device manufacturing process including a device ID that can identify the device, starting information related to the device activation process including the device ID, and device updating process. At least one of the update information including the device ID, which is the information related to the above, is recorded in the distributed ledger.
Of the manufacturing information, the startup information, and the update information, at least one of the information recorded in the distributed ledger is the managed device when confirming the reliability of the managed device. Information that is read out based on the device ID of the program.
To a computer connected to the information processing devices that make up the block chain via a network
It is detected whether or not manufacturing time information, which is information related to the manufacturing process of the device, has been generated, and when it is detected that the manufacturing time information has been generated, the manufacturing time information is recorded in the block chain. Let it run
The manufacturing information recorded in the distributed ledger is information read when confirming the reliability of the device to be managed, a program.
Information related to the manufacturing process of the device and including the device ID that can identify the device, information related to the booting process of the device and booting information including the device ID, and updating process of the device. To a computer connected to a network and an information processing device constituting a distributed ledger in which at least one of the update information including the device ID is recorded.
The device ID of the device to be managed is acquired, and at least one of the manufacturing information, the startup information, and the update information of the acquired device ID is recorded in the distributed ledger. A program that reads and confirms the reliability of the managed device.