Fault monitoring method, monitoring device, and program

The failure monitoring method using a distributed ledger system verifies IoT device functionality, ensuring only operational devices are utilized, thereby reducing waste and enhancing reliability.

JP7595000B2Active Publication Date: 2024-12-05PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021511282
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-03-29
Filing Date
2020-03-05
Publication Date
2024-12-05
Estimated Expiration
2040-03-05

AI Technical Summary

Technical Problem

Existing blockchain-based services for IoT devices, such as electronic locks, cannot determine if the device is malfunctioning until it is physically accessed, leading to wasted time and energy and unreliable service reliability.

Method used

A failure monitoring method using a distributed ledger that includes a terminal, monitoring device, and authentication servers to communicate and verify the status of IoT devices, preventing their use if malfunctioning.

Benefits of technology

Ensures that only functional IoT devices are used, reducing time and energy waste and enhancing service reliability by preventing the use of malfunctioning equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007595000000001
    Figure 0007595000000001
  • Figure 0007595000000002
    Figure 0007595000000002
  • Figure 0007595000000003
    Figure 0007595000000003
Patent Text Reader

Abstract

Provided is a fault monitoring method which is executed by a monitoring device in a fault monitoring system comprising a terminal used by a user, a device which is to be operated by the user, the monitoring device, and a plurality of authentication servers which each have a distributed ledger, said method involving: acquiring event information which indicates an event generated in accordance with a request including a processing command for allowing the user to operate the device and which is stored by the plurality of authentication servers (S11); acquiring state information indicating whether the device has a fault from the device (S12); generating first transaction data including the acquired state information and transmitting the same to the plurality of authentication servers (S13); and transmitting the processing instruction included in the event information to the device if it is verified from the state information that the device does not have a fault (S14).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a fault monitoring method, a monitoring device, and a program, and in particular to a fault monitoring method, a monitoring device, and a program using a distributed ledger. [Background technology]

[0002] In recent years, various companies have proposed services that use blockchain. One example of a service that uses blockchain is a service that uses blockchain to manage the unlocking and locking of units that make up delivery lockers (see Non-Patent Document 1).

[0003] Another example of a service that uses blockchain is a service that installs electronic locks in hotel rooms and uses blockchain to manage access to the rooms. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] GMO Internet, Inc., "GMO Internet Group, Saison Information Systems, and Parco jointly conduct second demonstration experiment using blockchain and IoT," [online], June 21, 2017, [Retrieved October 25, 2018], Internet<URL:https: / / cloud.z.com / jp / news-ep / IoT2 / > Summary of the Invention [Problem to be solved by the invention]

[0005] However, in these services, if an electronic lock attached to an IoT (Internet of Things) device such as a parcel box or a room is broken, a problem occurs in that although operations such as unlocking the electronic lock can be performed on the blockchain, it is not possible to actually perform the operation. In other words, there is a problem in that it is not known whether the IoT device can actually be used until the user moves to the actual location of the IoT device and performs operations on the blockchain. In such a case, not only is the time and energy spent moving to the actual location of the IoT device wasted, but the reliability of the service using the blockchain cannot be obtained, and the IoT device remains unused. For this reason, there is a demand for a technology that detects whether an electronic lock is broken when an IoT device is actually used, and that makes the IoT device (hereinafter also referred to as equipment) unusable if it is broken.

[0006] The present disclosure has been made in consideration of the above-mentioned circumstances, and provides a fault monitoring method, etc. that can suppress the use of faulty equipment using a distributed ledger. [Means for solving the problem]

[0007] In order to solve the above problem, a fault monitoring method according to one embodiment of the present disclosure is a fault monitoring method executed by the monitoring device in a fault monitoring system including a terminal used by a user, an appliance that is the target of operation by the user, a monitoring device, and a plurality of authentication servers each having a distributed ledger, wherein the terminal, the monitoring device, and the plurality of authentication servers are capable of communicating with each other via a network, the method comprising the steps of: obtaining, from the first authentication server, event information indicating an event generated in response to a request sent by the terminal to a first authentication server among the plurality of authentication servers, the request including a processing instruction for the user to operate the appliance generated by the user via the terminal, the event information being stored in the plurality of authentication servers; obtaining, from the first authentication server, status information indicating whether the appliance is faulty or not, generating first transaction data including the obtained status information, and transmitting the first transaction data to the first authentication server, thereby recording the first transaction data in the distributed ledgers of the plurality of authentication servers; and, if it is confirmed from the status information that the appliance is not faulty, transmitting the processing instruction included in the event information to the appliance.

[0008] These comprehensive or specific aspects may be realized by a system, an integrated circuit, a computer program, or a recording medium such as a computer-readable CD-ROM, or may be realized by any combination of a system, a method, an integrated circuit, a computer program, and a recording medium. Effect of the Invention

[0009] According to the present disclosure, it is possible to realize a fault monitoring method, etc., that can suppress the use of faulty equipment by using a distributed ledger. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of an overall configuration of a fault monitoring system according to an embodiment. [Figure 2A] FIG. 2A is a diagram showing another example of the monitoring device and devices constituting the fault monitoring system shown in FIG. [Figure 2B] FIG. 2B is a diagram showing another example of the monitoring device and devices constituting the fault monitoring system shown in FIG. [Figure 2C] FIG. 2C is a diagram showing another example of the monitoring device and devices constituting the fault monitoring system shown in FIG. [Diagram 3] FIG. 3 is a diagram illustrating an example of a configuration of a terminal according to an embodiment. [Figure 4A] FIG. 4A is a diagram illustrating an example of a processing command and the like included in transaction data generated by a transaction data generating unit according to the embodiment. [Figure 4B] FIG. 4B is a diagram showing an example of a processing command etc. included in the transaction data generated by the transaction data generating unit according to the embodiment. [Figure 4C] FIG. 4C is a diagram illustrating an example of a processing command and the like included in the transaction data generated by the transaction data generating unit according to the embodiment. [Figure 4D] FIG. 4D is a diagram illustrating an example of a processing command and the like included in the transaction data generated by the transaction data generating unit according to the embodiment. [Figure 4E] FIG. 4E is a diagram illustrating an example of a processing command and the like included in the transaction data generated by the transaction data generating unit according to the embodiment. [Figure 4F] FIG. 4F is a diagram showing an example of a processing command etc. included in the transaction data generated by the transaction data generating unit according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating another example of the configuration of the terminal according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a configuration of an authentication server according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a configuration of a monitoring device according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of transaction data generated by a notification unit according to the embodiment. [Figure 9]FIG. 9 is a diagram illustrating an example of transaction data generated by a notification unit according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a configuration of a device according to an embodiment. [Figure 11] FIG. 11 is a flowchart showing a fault monitoring method according to the embodiment. [Figure 12] FIG. 12 is a sequence diagram illustrating an example of a user request transmission operation of the fault monitoring system according to the embodiment. [Figure 13] FIG. 13 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the embodiment. [Figure 14] FIG. 14 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the first embodiment. [Figure 15] FIG. 15 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] (Findings on which this disclosure is based) For example, consider a service in which electronic locks are installed in hotel rooms and access to the rooms is managed by a blockchain (distributed ledger). When such a service is provided, users can reserve a room in advance using the blockchain. Then, when the user arrives at the hotel and holds an IC card or the like over the electronic lock installed in the room, verification of whether the user is allowed to enter or exit is performed by checking whether the user has the right to unlock the electronic lock on the distributed ledger. If the user has the right to unlock the electronic lock, it is unlocked. This prevents unauthorized users from tampering with the authority or stealing and using the electronic key.

[0012] However, as mentioned above, if the electronic lock installed in a room is broken, although operations such as reserving and unlocking the room can be performed on the distributed ledger, there is a problem that the room, i.e. the equipment, cannot actually be used.

[0013] In view of this, the present disclosure proposes a technology for detecting whether a device is faulty when the device is actually used and disabling the device if the device is faulty. In other words, the present disclosure provides a fault monitoring method and the like that can suppress the use of faulty devices by using a distributed ledger.

[0014] A fault monitoring method according to one embodiment of the present disclosure is a fault monitoring method executed by the monitoring device in a fault monitoring system including a terminal used by a user, an appliance that is operated by the user, a monitoring device, and a plurality of authentication servers each having a distributed ledger, wherein the terminal, the monitoring device, and the plurality of authentication servers are capable of communicating with each other via a network, the method comprising the steps of: obtaining, from the first authentication server, event information indicating an event generated in response to a request sent by the terminal to a first authentication server among the plurality of authentication servers, the request including a processing instruction for the user to operate the appliance generated by the user via the terminal, the event information being stored in the plurality of authentication servers; obtaining, from the first authentication server, status information indicating whether the appliance is faulty or not, generating first transaction data including the obtained status information, and transmitting the first transaction data to the first authentication server, thereby recording the first transaction data in the distributed ledgers of the plurality of authentication servers; and, if it is confirmed from the status information that the appliance is not faulty, transmitting the processing instruction included in the event information to the appliance.

[0015] This makes it possible to suppress the use of faulty devices using the distributed ledger. More specifically, the monitoring device monitors whether the device operated by the user is faulty or not, and the status information indicating whether the device is faulty or not is managed in the distributed ledger. This not only makes it impossible to tamper with the status information of the device, but also suppresses the use of faulty devices.

[0016] Furthermore, since devices that can be operated using the blockchain can be known as devices that can actually be used, it is possible to eliminate the situation where you cannot know whether a device can actually be used until you move to the location where the device is located. Therefore, the time and energy spent moving to the location of a broken device that cannot be operated is not wasted, and time and energy can be reduced. In addition, the reliability of services using the blockchain can be obtained.

[0017] Here, for example, the request may further include a request for transfer of authority of the device capable of causing the device to execute the processing command, and the event information may further include information indicating that a request for transfer of authority of the device has been made, and when the status information is acquired, if it is confirmed from the status information that the device is not malfunctioning, second transaction data indicating that the transfer request is approved may be generated and transmitted to the first authentication server, and when it is confirmed from the status information that the device is malfunctioning, third transaction data indicating that the transfer request is rejected may be generated and transmitted to the first authentication server.

[0018] Also, for example, the request may further include a transfer of authority of the device to enable the device to execute the processing command, and the event information may further include information indicating that a transfer of authority of the device has occurred, and if, upon acquiring the status information, it is determined from the status information that the device is malfunctioning, fourth transaction data indicating that the transfer is to be reversed may be generated and transmitted to the first authentication server.

[0019] Also, for example, the method further generates the first transaction data, and records a block including the generated first transaction data in the distributed ledger.

[0020] Also, for example, when recording in the distributed ledger, the first transaction data including the status information is generated only if it is confirmed from the status information that the device is faulty.

[0021] Furthermore, for example, in the first authentication server, fifth transaction data indicating a request including the processing instruction is recorded in the distributed ledger.

[0022] Moreover, a monitoring device according to one embodiment of the present disclosure is a monitoring device in a fault monitoring system, the fault monitoring system comprising: a terminal used by a user, an appliance that is the target of operation by the user; the monitoring device; and a plurality of authentication servers each having a distributed ledger, the terminal, the monitoring device, and the plurality of authentication servers being capable of communicating with each other via a network, and comprising: an event information monitoring unit that acquires, from the first authentication server, event information indicating an event generated in response to a request sent by the terminal to a first authentication server among the plurality of authentication servers, the request including a processing instruction generated by the user via the terminal for operating the appliance, the event information being stored in the plurality of authentication servers; a fault confirmation unit that acquires from the appliance, status information indicating whether the appliance is faulty or not, generates first transaction data including the acquired status information, and transmits the first transaction data to the first authentication server, thereby recording the first transaction data in the distributed ledgers of the plurality of authentication servers; and a processing instruction request unit that transmits the processing instruction included in the event information to the appliance when it is confirmed from the status information that the appliance is not faulty.

[0023] Hereinafter, the embodiments will be described with reference to the drawings. Note that each of the embodiments described below shows a specific example of the present disclosure. The numerical values, shapes, components, steps, and order of steps shown in the following embodiments are merely examples and are not intended to limit the present disclosure. In addition, among the components in the following embodiments, components that are not described in an independent claim showing the highest concept are described as optional components. In addition, each figure is not necessarily a strict illustration. In each figure, substantially the same configuration is given the same reference numeral, and duplicated explanations may be omitted or simplified.

[0024] Furthermore, as long as the scope of the present disclosure does not deviate from the gist of the present disclosure, various modifications that would come to mind by a person skilled in the art and other forms constructed by combining some of the components of each of the embodiments are also included in the scope of the present disclosure.

[0025] (Embodiment) First, the fault monitoring system of the present disclosure will be described.

[0026] [1. Fault monitoring system] The fault monitoring system disclosed herein includes a terminal used by a user, a device operated by the user, a monitoring device, and multiple authentication servers each having a distributed ledger. The fault monitoring system disclosed herein manages, in a distributed ledger (blockchain), status information indicating whether the device operated by the user is faulty, and can suspend use of the device if it is faulty.

[0027] Hereinafter, a fault monitoring system and the like according to an embodiment will be described with reference to the drawings.

[0028] [1.1 Overall configuration of the fault monitoring system] Fig. 1 is a diagram showing an example of the overall configuration of a fault monitoring system according to the first embodiment. The fault monitoring system shown in Fig. 1 includes a terminal 20, for example, three authentication servers 30a, 30b, and 30c, a monitoring device 10, and a device 40. These are connected by a network such as the Internet via wire, wireless communication, or dedicated communication. Note that these communications do not have to be in real time. For example, the terminal 20 may collect a certain amount of transaction data and then transmit it to the multiple authentication servers 30a, 30b, and 30c at the same time.

[0029] In FIG. 1, an example is shown in which one monitoring device 10 monitors one device 40 for failure in the failure monitoring system, but the present invention is not limited to this. FIGS. 2A to 2C are diagrams showing another example of the monitoring devices and devices constituting the failure monitoring system shown in FIG. 1. That is, as shown in FIG. 2A, one monitoring device 10 may monitor one or more devices 40, such as devices 40a, 40b, and 40c. Also, as shown in FIG. 2B, there may be a plurality of devices 40 and a plurality of monitoring devices 10, as long as they are the same number. More specifically, although one monitoring device 10 monitors one device 40 for failure, there may be a plurality of monitoring devices 10, such as monitoring devices 10a, 10b, and 10c, and one or more devices 40, such as devices 40a, 40b, and 40c. Also, as shown in FIG. 2C, there may be a plurality of devices 40 and a plurality of monitoring devices 10, and one device 40 may be monitored by one or more monitoring devices 10.

[0030] 1 shows an example in which the fault monitoring system includes one terminal 20 and three authentication servers 30, but the present invention is not limited to this. The fault monitoring system may include two or more terminals 20, and may include one or more authentication servers 30.

[0031] [1.2 Terminal] Fig. 3 is a diagram showing an example of the configuration of terminal 20 according to the embodiment. As shown in Fig. 3, terminal 20 includes transaction data generating unit 201 and communication unit 202. Terminal 20 is implemented in, for example, a computer or a mobile terminal including a processor (microprocessor), a memory, a communication interface, and the like. Terminal 20 is also configured to include an interface that receives input from a user. The interface may be, for example, a button for opening the door when device 40 is a door to a room, or may be, for example, a button for turning on the light when device 40 is a light.

[0032] [1.2.1 Transaction data generation unit] The transaction data generating unit 201 generates transaction data including the device 40 to be operated selected by a user input and a processing command requested by the user. For example, when a button for opening a door or a button for turning on a light is pressed by the user, the transaction data generating unit 201 generates transaction data including a processing command for opening the door or turning on the light.

[0033] The transaction data generation unit 201 transmits the generated transaction data to the communication unit 202 .

[0034] Here, an example of transaction data generated by transaction data generating unit 201 will be described with reference to FIGS. 4A to 4F.

[0035] 4A to 4F are diagrams showing examples of processing commands and the like included in transaction data generated by transaction data generating unit 201 according to the embodiment.

[0036] 4A and 4B show examples of transaction data including a device to be operated (shown as a target device) selected by a user's input and a processing command requested by the user. More specifically, FIG. 4A shows transaction data indicating that the target device is a light 1 and that the processing command is to turn on, and FIG. 4B shows transaction data indicating that the target device is a front door 1 and that the processing command is to unlock. If the processing command is self-evident and does not need to be described, the transaction data may include only the target device. In addition, when the same processing command is requested for multiple devices, the transaction data shown in FIG. 4A or FIG. 4B may be created for the number of target devices, or multiple target devices may be included in one transaction data, for example, as shown in FIG. 4C. Here, FIG. 4C shows transaction data indicating that the target devices are lights 1, 2, and 3, and that the processing command is to turn on.

[0037] Also, as shown in FIG. 4D, a signature of the creator may be added in addition to FIG. 4A. This makes it possible to confirm whether the creator of the transaction data is the same as the user who wishes to operate the target device. Also, as shown in FIG. 4E, a date and time of issue of the transaction data may be added in addition to FIG. 4A. This makes it possible to prevent the order of execution of multiple processing commands for the target device from changing. Also, as shown in FIG. 4F, a processing date and time at which a processing command is desired to be executed may be specified in addition to FIG. 4A.

[0038] [1.2.2 Communication section] The communication unit 202 communicates with the authentication servers 30a, 30b, and 30c via a network. In this embodiment, the communication unit 202 transmits the transaction data generated by the transaction data generation unit 201 to the authentication servers 30a, 30b, and 30c.

[0039] In this way, the terminal 20 receives an input from the user, creates a request including a processing command for the user to operate the device 40, and transmits the request to at least one authentication server (e.g., the first authentication server) among the multiple authentication servers 30. In this embodiment, the terminal 20 generates transaction data including the created request and transmits it to the authentication servers 30a, 30b, and 30c.

[0040] When there are multiple devices 40 that the user can operate, the user can select the device 40 to be operated from among the multiple devices 40 through input by the user.

[0041] 5 is a diagram showing an example of the configuration of a terminal 20A according to an embodiment. The same elements as those in FIG. 3 are given the same reference numerals, and detailed description thereof will be omitted. The terminal 20A shown in FIG. 5 is configured in a case where there are multiple devices 40 that the user can operate, and further includes a target device selection unit 203 in comparison with the terminal 20 shown in FIG. 3. The target device selection unit 203 selects a device 40 to be operated from among the multiple devices 40 according to a user input. In addition, the target device selection unit 203 selects a processing command for the device 40 selected according to a user input. Then, the target device selection unit 203 transmits the selected device 40 and the processing command to the transaction data generation unit 201.

[0042] [1.3 Authentication Server] The authentication servers 30a, 30b, and 30c shown in Fig. 1 are, for example, cloud servers. Since the authentication servers 30a, 30b, and 30c have the same configuration, the configuration of the authentication server 30, which represents them, will be described below. Note that the authentication server 30 has a distributed ledger (not shown). Also, any of the authentication servers 30a, 30b, and 30c is an example of a first server.

[0043] 6 is a diagram showing an example of a configuration of authentication server 30 according to an embodiment. Authentication server 30 includes transaction data storage unit 301, transaction data verification unit 302, event publishing unit 303, event information storage unit 304, and communication unit 305. Note that transaction data verification unit 302 is not essential. Authentication server 30 can be realized by a processor executing a predetermined program using a memory. Each component will be described below.

[0044] [1.3.1 Transaction data storage section] The transaction data storage unit 301 stores transaction data received from the terminal 20 or the monitoring device 10. The transaction data storage unit 301 may be configured with an area for temporarily storing transaction data and an area that functions as a distributed ledger. In this case, the transaction data storage unit 301 records (stores) the transaction data received from the terminal 20 or the monitoring device 10 as a distributed ledger.

[0045] [1.3.2 Transaction Data Verification Unit] The transaction data verification unit 302 verifies the validity of transaction data sent from the terminal 20 or the monitoring device 10. Specifically, the transaction data verification unit 302 verifies, for example, whether a cryptographic signature generated by a correct method is attached to the transaction data, whether the processing instructions included in the transaction data are meaningful, etc. If the transaction data verification unit 302 verifies that the transaction data is valid, it transmits the transaction data to the event publisher 303, which issues an event.

[0046] [1.3.3 Event Publisher] The event issuing unit 303 issues an event related to the transaction data whose validity has been verified by the transaction data verifying unit 302. Here, the event is generated in response to a request generated by the user via the terminal 20 and including a processing command for the user to operate the device 40. In this embodiment, the event includes information such as the processing command included in the transaction data and the target device. Note that the event may also include the transaction data.

[0047] The event publisher 303 transmits the published event to the event information storage unit 304 .

[0048] [1.3.4 Event information storage section] The event information storage unit 304 stores, as event information, the event issued by the event publishing unit 303. Furthermore, when there is an inquiry or request for event information from the monitoring device 10, the event information storage unit 304 transmits the event information to the monitoring device 10.

[0049] [1.3.5 Communication section] The communication unit 305 communicates with the terminal 20, other authentication servers 30, and monitoring device 10 via the network. In this embodiment, the communication unit 305 stores transaction data transmitted from the terminal 20 or monitoring device 10 in the transaction data storage unit 301. The communication unit 305 also transfers transaction data transmitted from the transaction data verification unit 302 to other authentication servers 30. When there is a request or inquiry for event information from the monitoring device 10, the communication unit 305 receives event information from the event information storage unit 304 and transmits it to the monitoring device 10.

[0050] [1.4 Monitoring device] Next, the monitoring device 10 will be described.

[0051] 7 is a diagram showing an example of a configuration of a monitoring device 10 according to an embodiment. The monitoring device 10 includes an event information monitoring unit 101, a fault confirmation unit 102, a notification unit 103, a processing command request unit 104, and a communication unit 105, and monitors a device 40. The monitoring device 10 is implemented in a computer including, for example, a processor, a memory, a communication interface, and the like.

[0052] [1.4.1 Event information monitoring section] The event information monitoring unit 101 acquires event information by making an inquiry about event information or a request for transmission to any one of the authentication servers 30a, 30b, and 30c. The event information for which the event information monitoring unit 101 makes an inquiry may be event information including all events issued up to now, or may be event information including only events issued since the previous inquiry.

[0053] After acquiring the event information, the event information monitoring unit 101 requests the failure confirmation unit 102 to confirm a failure of a target device of a processing command included in the unexecuted event. At this time, the event information monitoring unit 101 transmits the unexecuted event to the failure confirmation unit 102.

[0054] [1.4.2 Failure confirmation part] The failure confirmation unit 102 acquires from the device 40 status information indicating whether or not the device is broken. In this embodiment, the failure confirmation unit 102 confirms whether or not the event information received from the event information monitoring unit 101 includes a processing command to the device 40 monitored by the monitoring device 10. If the event information includes a processing command to the device 40, the failure confirmation unit 102 confirms whether or not the device 40 is broken. The failure confirmation unit 102 acquires status information from the device 40 to confirm whether or not the device 40 is broken. The failure confirmation unit 102 confirms whether or not the device 40 is broken from the acquired status information. Note that the method of confirming whether or not the device 40 is broken is not limited, and for example, a message may be sent to the device 40 and confirmation may be made based on the presence or absence of a reply, or other methods may be used.

[0055] The failure confirmation unit 102 transmits the acquired status information to the notification unit 103 .

[0056] [1.4.3 Notification section] The notification unit 103 receives status information of the device 40 from the failure confirmation unit 102, generates transaction data including the acquired status information, and transmits the transaction data to at least one authentication server 30. Here, the notification unit 103 may generate transaction data including the status information only when the failure confirmation unit 102 confirms from the status information that the device 40 is broken. In this embodiment, when the failure confirmation unit 102 confirms that the device 40 is broken, the notification unit 103 generates transaction data including the status information and transmits the transaction data to the authentication servers 30a, 30b, and 30c. Note that, even when the failure confirmation unit 102 confirms that the device 40 is not broken, the notification unit 103 may generate transaction data including the status information and transmit the transaction data to the authentication servers 30a, 30b, and 30c.

[0057] Here, an example of the transaction data generated by the notification unit 103 will be described with reference to FIGS.

[0058] 8 and 9 are diagrams showing an example of transaction data generated by the notification unit 103 according to the embodiment. Fig. 8 shows transaction data including status information indicating that the confirmation date and time is 2019 / 12 / 1 17:30, the target device is Light 1, and the failure status is failure. Fig. 9 shows transaction data including status information indicating that the confirmation date and time is 2019 / 12 / 1 17:30, the target device is Light 1, and the failure status is normal.

[0059] [1.4.4 Processing Instruction Request] When the processing command request unit 104 confirms from the status information acquired by the fault confirmation unit 102 that the device 40 is not faulty, it transmits the processing command included in the event information to the device 40. In this embodiment, when the fault confirmation unit 102 confirms from the status information that the device 40 is not faulty, the processing command request unit 104 requests the device 40 to execute the processing command included in the event information received from the fault confirmation unit 102.

[0060] [1.4.5 Communication section] The communication unit 105 communicates with the authentication servers 30a, 30b, and 30c and the device 40 via the network. In this embodiment, the communication unit 105 transmits a message to the authentication servers 30a, 30b, and 30c to inquire about event information or to request transmission of event information, and receives the event information as a reply. The communication unit 105 transmits transaction data generated by the notification unit 103 to the authentication servers 30a, 30b, and 30c. The communication unit 305 transmits a processing command to the device 40 and requests execution of the processing command.

[0061] In this way, the monitoring device 10 acquires status information on whether or not the device 40 is malfunctioning based on the acquired event information. If the device 40 is operating normally, the monitoring device 10 requests the device 40 to execute a processing command included in the event information. If the device 40 is malfunctioning, the monitoring device 10 transmits transaction data including the status information to the authentication servers 30a, 30b, and 30c to register the status information in the distributed ledger. Note that even if the device 40 is operating normally, the monitoring device 10 may transmit transaction data including the status information to the authentication servers 30a, 30b, and 30c to register the status information in the distributed ledger.

[0062] [1.5 Equipment] Next, a description will be given of the device 40. The device 40 may be, for example, an air conditioner, a locker, a delivery box, an e-bike, an e-bicycle, or a coin laundry, or may be an electronic lock attached to any of these.

[0063] 10 is a diagram showing an example of the configuration of device 40 according to the embodiment. Device 40 according to the embodiment includes processing command execution unit 401 and communication unit 402.

[0064] [1.5.1 Processing Instruction Execution Part] The processing command execution unit 401 executes a processing command transmitted from the monitoring device 10 .

[0065] [1.5.2 Communication section] The communication unit 402 communicates with the monitoring device 10 via the network. In this embodiment, the communication unit 402 receives a processing command from the monitoring device 10 and transmits the processing command to the processing command execution unit 401.

[0066] In this manner, the device 40 receives processing instructions from the monitoring device 10 and executes the processing.

[0067] [2. Operation] The fault monitoring method of the monitoring device 10 in the fault monitoring system configured as above will be described with reference to a flowchart.

[0068] FIG. 11 is a flowchart showing a fault monitoring method according to the embodiment.

[0069] 11, the monitoring device 10 acquires event information stored in the multiple authentication servers 30 from a first authentication server (S11). Here, the event information includes an event generated in response to a request transmitted from the terminal 20 to a first server among the multiple authentication servers 30, the request being generated by the user via the terminal 20 and including a processing command for the user to operate the device 40, as described above.

[0070] Next, the monitoring device 10 acquires, from the device 40, status information indicating whether or not the device is malfunctioning (S12).

[0071] Next, the monitoring device 10 generates first transaction data including the state information acquired in step S12, and transmits the first transaction data to the first authentication server (S13). This allows the first transaction data to be recorded in the distributed ledgers of the multiple authentication servers 30.

[0072] Next, if the monitoring device 10 confirms from the status information acquired in step S12 that the device 40 is not malfunctioning, it transmits the processing command included in the event information to the device 40 (S14).

[0073] Next, the operation of the fault monitoring system configured as above will be explained with reference to a sequence diagram. The operation of the fault monitoring system will be explained by dividing it into two phases: a user request transmission operation and a fault monitoring operation.

[0074] [2.1 User request transmission operation] The user request transmission operation of the fault monitoring system will now be described.

[0075] FIG. 12 is a sequence diagram illustrating an example of a user request transmission operation of the fault monitoring system according to the embodiment.

[0076] First, the terminal 20 receives an input from the user and selects a device to be operated (a target device in the figure) and a processing command to that device (S101).

[0077] Next, the terminal 20 generates and transmits transaction data (hereinafter referred to as fifth transaction data) including information on the device selected in step S101 and a processing command (S102). Here, as described above, the fifth transaction data may include information on the target device, the creation date and time of the transaction data, or a signature by the user, in addition to the processing command. In the example shown in FIG. 12, the terminal 20 transmits the generated fifth transaction data to the authentication servers 30a, 30b, and 30c. The terminal 20 may transmit the generated fifth transaction data to only one of the authentication servers 30a, 30b, and 30c. In this case, one of the authentication servers 30a, 30b, and 30c transfers the fifth transaction data to the other authentication servers.

[0078] Next, authentication servers 30a, 30b, and 30c receive the fifth transaction data transmitted in step S101, and temporarily store it in transaction data storage unit 301 (S103).

[0079] Next, the authentication servers 30a, 30b, and 30c execute a consensus algorithm (S104). More specifically, first, the authentication servers 30a, 30b, and 30c read the fifth transaction data stored in the transaction data storage unit 301 and verify the legitimacy of the fifth transaction data. The legitimacy is verified, for example, by checking the consistency, issuance date and time, and name of the processing command included in the fifth transaction data. When the authentication servers 30a, 30b, and 30c verify the legitimacy of the received fifth transaction data, they each generate a block including the fifth transaction data. Then, the authentication servers 30a, 30b, and 30c record the block including the fifth transaction data in an area of ​​the transaction data storage unit 301 that functions as a distributed ledger. In this way, the fifth transaction data indicating a request including a processing command is recorded in the distributed ledger, i.e., the blockchain.

[0080] Next, the authentication servers 30a, 30b, and 30c issue an event related to the fifth transaction data (S105). As described above, the event related to the fifth transaction data is an event generated in response to a request including a processing command for a user to operate a device, and includes, for example, an issue date and time and the fifth transaction data.

[0081] [2.2 Fault monitoring operation] Next, the fault monitoring operation of the fault monitoring system will be described.

[0082] FIG. 13 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the embodiment.

[0083] First, the monitoring device 10 checks whether an event has been issued to one of the authentication servers 30a, 30b, and 30c (authentication server 30c in the figure) (S201). In this embodiment, the monitoring device 10 queries the authentication server 30c about event information.

[0084] Next, the authentication server 30c that has received the inquiry returns the event information stored in the event information storage unit 304 to the monitoring device 10 (S202).

[0085] Next, the monitoring device 10 checks whether the acquired event information includes a processing command to the device 40 monitored by the monitoring device 10 (S203). Note that in step S203, if the acquired event information does not include a processing command to the device 40 (No in S203), the monitoring device 10 returns to step S201.

[0086] In step S203, if the acquired event information includes a processing command to the device 40 (Yes in S203), the monitoring device 10 acquires status information of the device 40 (S204). Here, as a method for acquiring the status information, for example, there is a method for acquiring status information indicating whether or not the device is malfunctioning by sending a message to the device 40 and checking for a malfunction based on the presence or absence of a reply.

[0087] Next, the monitoring device 10 generates transaction data (hereinafter referred to as first transaction data) including the status information acquired in step S204, and transmits it to the authentication servers 30a, 30b, and 30c (S205). Note that the monitoring device 10 may transmit the generated first transaction data to only one of the authentication servers 30a, 30b, and 30c. In this case, one of the authentication servers 30a, 30b, and 30c transfers the first transaction data to the other authentication servers.

[0088] Next, when the authentication servers 30a, 30b, and 30c receive the first transaction data transmitted from the monitoring device 10, they temporarily store the data in the transaction data storage unit 301 and execute a consensus algorithm (S206). More specifically, first, the authentication servers 30a, 30b, and 30c read the first transaction data stored in the transaction data storage unit 301 and verify the validity of the first transaction data. When the authentication servers 30a, 30b, and 30c verify the validity of the received first transaction data, they each generate a block including the first transaction data. Then, the authentication servers 30a, 30b, and 30c record the block including the first transaction data in an area of ​​the transaction data storage unit 301 that functions as a distributed ledger. In this way, the first transaction data including the state information is recorded in the distributed ledger, i.e., the blockchain.

[0089] Furthermore, if the device 40 is not malfunctioning, the monitoring device 10 transmits the processing command contained in the event information to the device 40 (S207).

[0090] Finally, the device 40 executes the received processing command (S208).

[0091] The order of steps S207 and S206 does not matter.

[0092] [3. Effects, etc.] As described above, in the failure monitoring system of the present embodiment, the user causes the terminal 20 to transmit the fifth transaction data including a processing command to the authentication server 30 in order to have the target device perform a process. The authentication server 30 verifies the validity of the fifth transaction data received from the terminal 20, and if the data is valid, issues an event corresponding to the processing command. The monitoring device 10 confirms that the event has been issued, and obtains status information indicating whether or not the device 40 that is the target of the user's processing command is malfunctioning. When the monitoring device 10 confirms that the device 40 is malfunctioning, the monitoring device 10 transmits the first transaction data including the status information to the authentication server 30, thereby registering the status information in the distributed ledger. If the device 40 is not malfunctioning, the monitoring device 10 causes the device 40 to execute the process requested by the user.

[0093] As described above, according to the fault monitoring system of this embodiment, the monitoring device monitors whether the device operated by the user is faulty or not, and the status information indicating whether the device is faulty or not is managed by a distributed ledger, i.e., a blockchain. This not only makes it impossible to tamper with the status information of the device, but also makes it possible to suppress the use of faulty devices. In other words, according to the fault monitoring system of this embodiment, the use of faulty devices can be suppressed by using a distributed ledger.

[0094] Furthermore, since devices that can be operated on the blockchain can be known as devices that can actually be used, it is possible to eliminate the situation where you cannot know whether a device can actually be used until you move to the location where the device is located. Therefore, the time and energy spent moving to the location of a broken device that cannot be operated is not wasted, which reduces time and energy and also ensures the reliability of services that use the blockchain.

[0095] Example 1 When operating a device on the blockchain, the authority of the device is managed by the blockchain. For example, if the device is an electronic lock installed in a hotel room, the authority to lock or unlock the electronic lock is managed by the blockchain, and the entry and exit management of the room is also managed by the blockchain.

[0096] In the first embodiment, a case will be described in which authority of the device is transferred on the blockchain after it is confirmed that the device to be operated is not broken. In this case, the fifth transaction data generated by the terminal 20 includes a request for transferring authority of the device 40 that allows the device 40 to execute the processing command in a request including a processing command for the user to operate the device 40. Therefore, the event information also includes information indicating that a request for transferring authority of the device 40 has been made.

[0097] The failure monitoring operation according to the first embodiment will be described below with reference to FIG.

[0098] FIG. 14 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the first embodiment.

[0099] First, the monitoring device 10 checks whether an event has been issued to one of the authentication servers 30a, 30b, and 30c (authentication server 30c in the figure) (S301). In this embodiment, the monitoring device 10 also queries the authentication server 30c about event information.

[0100] Next, the authentication server 30c that has received the inquiry returns the event information stored in the event information storage unit 304 to the monitoring device 10 (S302). In this embodiment, the event information also includes information indicating that a request for transfer of authority of the device 40 has been made.

[0101] Next, the monitoring device 10 checks whether the acquired event information includes a request for transferring the authority of the device 40 monitored by the monitoring device 10 (S303). Note that in step S303, if the acquired event information does not include a request for transferring the authority of the device 40 (No in S303), the monitoring device 10 returns to step S301.

[0102] In step S303, if the acquired event information includes a request for transferring authority of the device 40 (Yes in S303), the monitoring device 10 acquires status information of the device 40 (S304). Note that the method for acquiring the status information is the same as that described in step S204, and therefore will not be described here.

[0103] Next, the monitoring device 10 generates first transaction data including the status information acquired in step S304, and transmits the first transaction data to the authentication servers 30a, 30b, and 30c (S305).

[0104] Next, when the authentication servers 30a, 30b, and 30c receive the first transaction data transmitted from the monitoring device 10, they temporarily store the data in the transaction data storage unit 301 and execute a consensus algorithm (S306). Details are as explained in step S206, so explanations will be omitted. As a result of executing the consensus algorithm, the first transaction data including the state information is recorded in the distributed ledger, i.e., the blockchain.

[0105] Furthermore, the monitoring device 10 checks from the status information whether or not the device 40 is malfunctioning (S307).

[0106] In step S307, if the monitoring device 10 confirms from the acquired status information that the device 40 is not malfunctioning (No in S307), it generates transaction data (hereinafter referred to as second transaction data) indicating that the request to transfer the authority of the device 40 is approved, and transmits the transaction data to the authentication servers 30a, 30b, and 30c (S308).

[0107] Next, the monitoring device 10 transmits to the device 40 a processing command for the device 40, which is included in the event information (S309).

[0108] Next, the device 40 executes the received processing command (S310).

[0109] On the other hand, in step S307, if the monitoring device 10 determines from the acquired status information that the device 40 is malfunctioning (Yes in S307), it generates transaction data (hereinafter referred to as third transaction data) indicating a denial of the request to transfer the authority of the device 40 and transmits the transaction data to the authentication servers 30a, 30b, 30c (S311).

[0110] Next, when the authentication servers 30a, 30b, and 30c receive the second or third transaction data transmitted from the monitoring device 10, they temporarily store it in the transaction data storage unit 301 and execute the consensus algorithm (S312). In more detail, first, the authentication servers 30a, 30b, and 30c read the second or third transaction data stored in the transaction data storage unit 301 and verify the validity of the second or third transaction data. When the authentication servers 30a, 30b, and 30c verify the validity of the received second or third transaction data, they generate blocks including the second or third transaction data, respectively. Then, the authentication servers 30a, 30b, and 30c record the blocks including the second or third transaction data in an area of ​​the transaction data storage unit 301 that functions as a distributed ledger. In this way, the second or third transaction data is recorded in the distributed ledger, i.e., the blockchain.

[0111] The order of steps S310 and S312 does not matter, and the execution of step S312 is not essential.

[0112] Example 2 In the second embodiment, a case will be described in which authority of the device to be operated is transferred on the blockchain before checking the status information of the device to be operated, and the authority is returned if the device is broken. In this case, the fifth transaction data generated by the terminal 20 includes a transfer of authority of the device 40 that can cause the device 40 to execute the processing command in a request including a processing command for the user to operate the device 40. Therefore, the event information also includes information indicating that the authority of the device 40 has been transferred.

[0113] The failure monitoring operation according to the second embodiment will be described below with reference to FIG.

[0114] FIG. 15 is a sequence diagram illustrating an example of the failure monitoring operation of the failure monitoring system according to the second embodiment.

[0115] First, the monitoring device 10 checks whether an event has been issued to one of the authentication servers 30a, 30b, and 30c (authentication server 30c in the figure) (S401). In this embodiment, the monitoring device 10 also queries the authentication server 30c about event information.

[0116] Next, the authentication server 30c that has received the inquiry returns the event information stored in the event information storage unit 304 to the monitoring device 10 (S402). In this embodiment, the event information also includes information indicating that the authority of the device 40 has been transferred.

[0117] Next, the monitoring device 10 checks whether the acquired event information indicates that the authority of the device 40 monitored by the monitoring device 10 has been transferred (S403). Note that in step S403, if the acquired event information does not indicate that the authority of the device 40 has been transferred (No in S403), the monitoring device 10 returns to step S401.

[0118] In step S403, if the acquired event information indicates that the authority of the device 40 has been transferred (Yes in S403), the monitoring device 10 acquires the status information of the device 40 (S404). Note that the method of acquiring the status information is the same as that described in step S204, and therefore will not be described here.

[0119] Next, the monitoring device 10 generates first transaction data including the status information acquired in step S404, and transmits the first transaction data to the authentication servers 30a, 30b, and 30c (S405).

[0120] Next, when the authentication servers 30a, 30b, and 30c receive the first transaction data transmitted from the monitoring device 10, they temporarily store the data in the transaction data storage unit 301 and execute a consensus algorithm (S406). Details are as explained in step S206, so explanations will be omitted. As a result of executing the consensus algorithm, the first transaction data including the state information is recorded in the distributed ledger, i.e., the blockchain.

[0121] Furthermore, the monitoring device 10 checks from the status information whether or not the device 40 is malfunctioning (S407).

[0122] In step S407, if the monitoring device 10 determines from the acquired status information that the device 40 is not malfunctioning (No in S407), it transmits a processing command for the device 40, which is included in the event information, to the device 40 (S408).

[0123] Next, the device 40 executes the received processing command (S409).

[0124] On the other hand, in step S407, if the monitoring device 10 determines from the acquired status information that the device 40 is malfunctioning (Yes in S407), it generates transaction data (hereinafter referred to as fourth transaction data) indicating that the transfer of authority of the device 40 is to be returned, and transmits the transaction data to the authentication servers 30a, 30b, 30c (S410).

[0125] Next, when the authentication servers 30a, 30b, and 30c receive the fourth transaction data transmitted from the monitoring device 10, they temporarily store it in the transaction data storage unit 301 and execute the consensus algorithm (S411). More specifically, first, the authentication servers 30a, 30b, and 30c read the fourth transaction data stored in the transaction data storage unit 301 and verify the validity of the fourth transaction data. When the authentication servers 30a, 30b, and 30c verify the validity of the received fourth transaction data, they each generate a block including the fourth transaction data. Then, the authentication servers 30a, 30b, and 30c record the block including the fourth transaction data in an area of ​​the transaction data storage unit 301 that functions as a distributed ledger. In this way, the fourth transaction data is recorded in the distributed ledger, i.e., the blockchain.

[0126] The order of steps S409 and S411 does not matter.

[0127] (Other embodiments) Although the fault monitoring system according to the present disclosure has been described above based on the embodiment, the present disclosure is not limited to the above embodiment. As long as it does not deviate from the gist of the present disclosure, various modifications conceived by a person skilled in the art to the embodiment and other forms formed by combining some of the components in the embodiment are also included in the scope of the present disclosure. For example, the following cases are also included in the present disclosure.

[0128] (1) In the case where one monitoring device monitors multiple devices, when the monitoring device acquires device status information, it may acquire status information only for devices that are the target of a newly issued event indicated in the acquired event information. Also, when the monitoring device acquires device status information, it may acquire status information for all devices monitored by the monitoring device, not just for devices that are the target of a newly issued event indicated in the acquired event information.

[0129] (2) In the above embodiment, in the fault monitoring system according to the present disclosure, when a new event is issued by the authentication server 30, the monitoring device acquires status information from the device to check whether the device is faulty or not, and then requests the device to execute a processing command. However, this is not limited to the above. When a new event is issued by the authentication server 30, the monitoring device may request the device to execute a processing command, and acquire status information from the execution result transmitted from the device. For example, assume that the device is a locker, and the locker is equipped with a sensor that detects when the door is opened. In this case, if the monitoring device issues a command to open the locker but is unable to detect that the door is open, the monitoring device may determine that the locker is faulty, and acquire status information indicating that the locker is faulty.

[0130] (3) The above-mentioned devices are specifically computer systems consisting of a microprocessor, ROM, RAM, a hard disk unit, a display unit, a keyboard, a mouse, etc. A computer program is stored in the RAM or hard disk unit. The microprocessor operates according to the computer program, causing each device to achieve its function. Here, a computer program is composed of a combination of multiple instruction codes that indicate commands for a computer to achieve a specified function.

[0131] (4) Some or all of the components constituting the above-mentioned device may be composed of one system LSI (Large Scale Integration). The system LSI is an ultra-multifunctional LSI manufactured by integrating multiple components on one chip, and specifically, is a computer system including a microprocessor, ROM, RAM, etc. A computer program is stored in the RAM. The system LSI achieves its functions by the microprocessor operating in accordance with the computer program.

[0132] (5) Some or all of the components constituting the above-mentioned device may be composed of an IC card or a standalone module that is detachable from each device. The IC card or the module is a computer system composed of a microprocessor, ROM, RAM, etc. The IC card or the module may include the above-mentioned ultra-multifunction LSI. The microprocessor operates according to a computer program, causing the IC card or the module to achieve its functions. The IC card or the module may be tamper-resistant.

[0133] (6) The present disclosure may also be embodied as the methods described above, as a computer program for implementing these methods by a computer, or as a digital signal comprising the computer program.

[0134] (7) The present disclosure may also be the computer program or the digital signal recorded on a computer-readable recording medium, such as a flexible disk, a hard disk, a CD-ROM, an MO, a DVD, a DVD-ROM, a DVD-RAM, a BD (Blu-ray (registered trademark) Disc), a semiconductor memory, etc. Also, the present disclosure may be the digital signal recorded on such a recording medium.

[0135] Furthermore, the present disclosure may involve transmitting the computer program or the digital signal via a telecommunications line, a wireless or wired communication line, a network such as the Internet, data broadcasting, or the like.

[0136] The present disclosure may also provide a computer system having a microprocessor and a memory, the memory storing the above-mentioned computer program, and the microprocessor operating in accordance with the computer program.

[0137] In addition, the program or the digital signal may be implemented by another independent computer system by recording it on the recording medium and transferring it, or by transferring the program or the digital signal via the network, etc. [Industrial Applicability]

[0138] The present disclosure can be applied to a system in which a monitoring device independent of equipment monitors equipment failures and manages the status of whether the equipment is faulty using a blockchain. [Explanation of symbols]

[0139] 10, 10a, 10b, 10c monitoring equipment 20 Terminals 30, 30a, 30b, 30c Authentication Server 40, 40a, 40b, 40c equipment 101 Event Information Monitoring Department 102 Failure confirmation section 103 Notification Department 104 Processing instruction request section 105, 202, 305 Communications Department 201 Transaction Data Generation Unit 301 Transaction Data Storage Unit 302 Transaction Data Verification Department 303 Event Publishing Department 304 Event information storage section 401 Processing command execution unit 402 Communications Department

Claims

1. A fault monitoring method performed by an apparatus, comprising: Obtaining event information from the first authentication server, the event information being indicative of a requested event that includes processing instructions for operating the device; obtaining status information from the device, the status information indicating whether the device is malfunctioning; Generate first transaction data including the acquired state information and transmit the first transaction data to the first authentication server having a distributed ledger; When it is confirmed that the device is not malfunctioning based on the status information acquired from the device, the processing command included in the event information acquired from the first authentication server is transmitted to the device; The request further includes a request for transfer of authority of the device capable of causing the device to execute the processing command; The event information further includes information indicating that a request for transfer of authority of the device has been made, When the state information is acquired, When it is confirmed from the status information that the device is not malfunctioning, second transaction data indicating approval of the transfer request is generated and transmitted to the first authentication server; if it is determined from the status information that the device is out of order, generate third transaction data indicating that the transfer request is rejected, and transmit the third transaction data to the first authentication server; Failure monitoring method.

2. A fault monitoring method performed by an apparatus, comprising: Obtaining event information from the first authentication server, the event information being indicative of a requested event that includes processing instructions for operating the device; obtaining status information from the device, the status information indicating whether the device is malfunctioning; Generate first transaction data including the acquired state information and transmit the first transaction data to the first authentication server having a distributed ledger; When it is confirmed that the device is not malfunctioning based on the status information acquired from the device, the processing command included in the event information acquired from the first authentication server is transmitted to the device; The request further includes a transfer of authority of the device to cause the device to execute the processing command; The event information further includes information indicating that the authority of the device has been transferred, When the state information is acquired, if it is determined from the status information that the device is broken, generate fourth transaction data indicating that the transfer is to be returned, and transmit the fourth transaction data to the first authentication server; Failure monitoring method.

3. moreover, generating the first transaction data and recording a block including the generated first transaction data in the distributed ledger; The fault monitoring method according to any one of claims 1 to 2.

4. When recording in the distributed ledger, generating the first transaction data including the status information only when it is confirmed from the status information that the device is malfunctioning; The fault monitoring method according to any one of claims 1 to 3.

5. Further, in the first authentication server, fifth transaction data indicating a request including the processing instruction is recorded in the distributed ledger. The fault monitoring method according to any one of claims 1 to 4.

6. an event information monitoring unit that acquires, from the first authentication server, event information indicating an event generated in response to a request including a processing command for operating the device; a failure confirmation unit that acquires from the device status information indicating whether the device is malfunctioning, generates first transaction data including the acquired status information, and transmits the first transaction data to the first authentication server having a distributed ledger; a processing command request unit that transmits the processing command included in the event information acquired from the first authentication server to the device when it is confirmed that the device is not malfunctioning based on the status information acquired from the device, The request further includes a request for transfer of authority of the device capable of causing the device to execute the processing command; The event information further includes information indicating that a request for transfer of authority of the device has been made, When the state information is acquired, When it is confirmed from the status information that the device is not malfunctioning, second transaction data indicating approval of the transfer request is generated and transmitted to the first authentication server; if it is determined from the status information that the device is out of order, generate third transaction data indicating that the transfer request is rejected, and transmit the third transaction data to the first authentication server; monitoring equipment.

7. A program for causing a computer to execute the fault monitoring method according to claim 1.

8. an event information monitoring unit that acquires, from the first authentication server, event information indicating an event generated in response to a request including a processing command for operating the device; a failure confirmation unit that acquires from the device status information indicating whether the device is malfunctioning, generates first transaction data including the acquired status information, and transmits the first transaction data to the first authentication server having a distributed ledger; a processing command request unit that transmits the processing command included in the event information acquired from the first authentication server to the device when it is confirmed that the device is not malfunctioning based on the status information acquired from the device, The request further includes a transfer of authority of the device to cause the device to execute the processing command; The event information further includes information indicating that the authority of the device has been transferred, When the state information is acquired, if it is determined from the status information that the device is broken, generate fourth transaction data indicating that the transfer is to be returned, and transmit the fourth transaction data to the first authentication server; monitoring equipment.

9. A program for causing a computer to execute the fault monitoring method according to claim 2.

Citation Information

Patent Citations

  • Heterojunction bipolar transistor

    JP1989017467A

  • Bicycle rental system

    JP2016143185A

  • Delivery method and delivery system

    JP2019040440A

  • Devices, systems, and methods for storing items

    WO2016164577A1