JPWO2022254589A5 - - Google Patents

Description

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

Conventionally, there are systems that link multiple blockchain networks. For example, the system is realized by a control device that uses a collaboration blockchain network to coordinate multiple collaboration destination blockchain networks. Here, in order to take measures against the occurrence of a system failure, the control device may be made redundant, and a standby control device and an active control device may be provided.

Prior art techniques include, for example, recovering target transactions having the same sequence number as a target sequence number at a network node. Also, for example, there are techniques in which one of the nodes functions as a primary node and another node functions as a backup node. Furthermore, for example, there is a technique for executing a transaction request on a backup node.

Special Publication No. 2020-516105 Special Publication No. 2020-518887 US Patent Application Publication No. 2019/0278666

However, the conventional technology has a problem in that it is difficult for the standby control device to determine the state of the active control device. For example, when a standby control device periodically communicates with an active control device and monitors the active control device, the processing load placed on each control device tends to increase. Specifically, the standby control device determines whether or not the elapsed time from the time the active control device started processing will time out, and if it times out, there is an error in the active control device. However, if the time required for processing in the active control device is relatively long, it may be mistakenly assumed that there is an abnormality in the active control device even if there is no abnormality in the active control device. The active control device and the standby control device may conflict with each other in processing.

In one aspect, the present invention aims to reduce the processing load on a control device.

According to one embodiment, a blockchain network including nodes corresponding to each of a plurality of control devices records the performance of a process assigned to each of the control devices by the control device. A control method, control program, and information that acquires a block managed by the blockchain network and determines the state of at least one of the plurality of control devices based on the execution record included in the acquired block. A processing device and system are proposed.

According to one aspect, it is possible to reduce the processing load on the control device. For example, when determining the status of an active control device, it is possible to eliminate the need for communication between the active control device and the standby control device, thereby reducing the processing burden on each control device. It becomes possible. Further, according to one aspect, it becomes easier to accurately determine the state of an active control device, and it becomes possible to accurately detect an opportunity for a standby control device corresponding to the active control device to operate. . For example, even if the time required for processing assigned to the standby control device is relatively long, it is possible to accurately determine whether there is an abnormality regarding the standby control device.

FIG. 1 is an explanatory diagram showing an example of a control method according to an embodiment. FIG. 2 is an explanatory diagram showing an example of the BC cooperation system 200. FIG. 3 is a block diagram showing an example of the hardware configuration of the information processing device 100. FIG. 4 is an explanatory diagram showing an example of the stored contents of the BU determination information management table 400. FIG. 5 is a block diagram showing an example of the hardware configuration of the cooperation node 201. FIG. 6 is an explanatory diagram showing an example of the stored contents of the person-in-charge information management table 600. FIG. 7 is a block diagram showing an example of the functional configuration of the BC cooperation system 200. FIG. 8 is an explanatory diagram (Part 1) showing the flow of operation of the BC cooperation system 200. FIG. 9 is an explanatory diagram (part 2) showing the flow of the operation of the BC cooperation system 200. FIG. 10 is an explanatory diagram (part 1) showing an example of the operation of the BC cooperation system 200. FIG. 11 is an explanatory diagram (part 2) showing an example of the operation of the BC cooperation system 200. FIG. 12 is an explanatory diagram (part 3) showing an example of the operation of the BC cooperation system 200. FIG. 13 is an explanatory diagram (part 4) showing an example of the operation of the BC cooperation system 200. FIG. 14 is an explanatory diagram (part 5) showing an example of the operation of the BC cooperation system 200. FIG. 15 is an explanatory diagram (part 6) showing an example of the operation of the BC cooperation system 200. FIG. 16 is an explanatory diagram (part 7) showing an example of the operation of the BC cooperation system 200. FIG. 17 is an explanatory diagram (Part 8) showing an example of the operation of the BC cooperation system 200. FIG. 18 is a flowchart showing an example of the overall processing procedure. FIG. 19 is a flowchart illustrating an example of a cooperation processing procedure. FIG. 20 is a flowchart (Part 1) showing an example of the BU processing procedure. FIG. 21 is a flowchart (Part 2) showing an example of the BU processing procedure. FIG. 22 is a flowchart (part 3) showing an example of the BU processing procedure.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a control method, a control program, an information processing device, and a system according to the present invention will be described in detail below with reference to the drawings.

(An example of a control method according to an embodiment)
FIG. 1 is an explanatory diagram showing an example of a control method according to an embodiment. The information processing device 100 is a computer that can serve as a standby control device corresponding to an active control device.

The operating system control device is a computer for coordinating multiple cooperative blockchain networks. For example, the operating system control device allows a plurality of linked blockchain networks to cooperate and execute a series of transactions. The standby control device is a control device that can replace the active control device. In the following explanation, blockchain may be referred to as "BC".

The BC network implements a BC management system that manages BC. A BC network is formed by multiple nodes. For example, BCs are managed by each node included in the BC network storing and monitoring the same BC.

BC is a list that becomes a distributed ledger that manages transaction information by connecting blocks in which transaction information is registered. Transaction information is called, for example, a transaction (Tx). In the following description, a transaction may be referred to as "Tx". BC realizes, for example, a distributed ledger technology that makes it difficult to tamper with transaction information registered in blocks.

BACKGROUND ART Conventionally, there is a BC cooperation system that allows a plurality of cooperation destination BC networks to cooperate with each other using only one control device. Due to the occurrence of a failure in the BC coordination system, the control device may be unable to complete a series of processes. The failure is, for example, a server down, a node down, or a memory crash.

For this reason, it is conceivable to make the control devices redundant and prepare an active control device and a standby control device corresponding to the active control device to take measures against the occurrence of failures in the BC cooperation system. For example, a standby control device periodically polls the active control device to monitor the active control device, and if it detects that the active control device is down, it can control the active control device. It is conceivable that the device may attempt to continue the series of processing on behalf of the device.

However, there is a problem in that it is difficult for the standby control device to determine the state of the active control device. For example, if a standby control device periodically polls an active control device and monitors the active control device, the processing load placed on each control device tends to increase. The processing load includes, for example, a communication load.

In contrast, the standby control device determines whether or not the elapsed time from the time the active control device started processing times out, and if it times out, it determines that there is an abnormality in the active control device. There are ways to make this determination. With this method, if the time required for processing in the active control device is relatively long, it may be mistakenly determined that there is an abnormality in the active control device, even if there is no abnormality in the active control device. There's a problem. Processing may conflict between the active control device and the standby control device.

Therefore, in the present embodiment, it is made easier to accurately determine that there is an abnormality regarding the active control device, and the processing burden on the respective control devices of the active control device and the standby control device is reduced. A control method that can achieve this will be explained. An abnormality related to the control device is, for example, an abnormality in the control device itself or an abnormality in a communication path of the control device.

In FIG. 1, the information processing device 100 can be a standby control device. There are a plurality of active control devices 101. In the example of FIG. 1, there are three control devices 101. There is a BC network 110 including nodes 111 corresponding to each control device 101. The BC network 110 may further include a node 111 corresponding to the information processing device 100.

The BC network 110 manages blocks 121 in which the execution results of the processes assigned to each control device 101 by the control device 101 are recorded. The processing is, for example, a transaction. The BC network 110 manages, for example, BCs 120 in which blocks 121 are connected. BCs 120 are managed in the BC network 110 by each node 111 storing the same BC 120.

It is assumed that the control device 101 receives requests for processes 1 to 3, and is assigned processes 1 to 3. The control device 101-1 that received the request for process 1 has not completed process 1. When the control device 101-2 that has received the request for process 2 completes process 2, it notifies the node 111 corresponding to the control device 101-2 that process 2 has been completed. When the control device 101-3 that has received the request for process 3 completes process 3, it notifies the node 111 corresponding to the control device 101-3 that process 3 has been completed.

Each node 111 forms a consensus based on the received notification and adds the block 121 to the BC 120. Each node 111 has added to the BC 120, for example, a block 121 in which an execution record indicating that process 2 has been completed and a block 121 in which an execution record indicating that process 3 has been completed are recorded. shall be.

The information processing device 100 acquires the block 121 from the BC network 110. The information processing device 100 determines the state of at least one of the plurality of control devices 101 based on the execution results included in the acquired block 121. For example, if the process assigned to the control device 101 is not completed, the information processing device 100 determines the state of the control device 101 based on whether another process of the same type as the process has been completed. do.

Another process of the same type as a certain process is another process that satisfies a predetermined condition regarding the certain process. Another process of the same type as a certain process may be, for example, another process that uses the same cooperation destination BC network as the certain process. Another process of the same type as a certain process may be, for example, another process from the same request source as the certain process. Another process of the same type as a certain process may be, for example, another process that requires the same amount of time as the certain process.

Specifically, when the information processing device 100 detects that processing 2 assigned to the control device 101-2 has not been completed, but processing 3 of the same type as processing 2 has been completed, the information processing device 100 It is determined that there is an abnormality related to -2. Specifically, even if process 2 assigned to control device 101-2 is not completed, if process 3 of the same type as process 2 is also not completed, information processing device 100 performs processing related to control device 101-2. This can be done without determining that there is an abnormality.

When the information processing device 100 determines that there is an abnormality regarding the control device, it executes processing assigned to the control device on behalf of the control device. In the following description, the fact that the information processing device 100 executes a process assigned to the control device instead of the control device may be expressed as "BU (BackUp)." For example, when the information processing device 100 determines that there is an abnormality regarding the control device 101-2, it executes the process 2 on behalf of the control device 101-2.

Thereby, the information processing device 100 can easily determine the state of the control device 101 accurately, and can accurately detect an opportunity to operate as a standby control device corresponding to the control device 101. The information processing device 100 determines that there is no abnormality regarding the control device 101, even if the time required for the process assigned to the control device 101 is relatively long, if the time required for the same type of process is also relatively long. can do. In addition, since the information processing device 100 does not need to communicate with each control device 101 etc., it is possible to reduce the processing load placed on each control device 101, and the processing load placed on the information processing device 100 can be reduced. It is possible to aim for

Although the case where the information processing device 100 is not an active control device has been described here, the present invention is not limited to this. For example, the information processing device 100 may have a function as an active control device and may also operate as an active control device.

Here, if the process assigned to the control device 101 has not been completed and one other process of the same type as the process has been completed, the information processing device 100 determines that there is an abnormality regarding the control device 101. Although the case has been described above, the case is not limited to this.

Although a case has been described here in which the node 111 corresponding to the information processing apparatus 100 exists, the present invention is not limited to this. For example, the node 111 corresponding to the active control device 101 may also correspond to the information processing device 100.

Here, a case has been described in which, when the information processing apparatus 100 determines that there is an abnormality regarding the control device, it executes the process assigned to the control device instead of the control device, but the present invention is not limited to this. For example, the information processing device 100 may output the determined result.

Specifically, the information processing device 100 may transmit the determined result to a standby control device corresponding to an active control device that has been determined to have an abnormality. In this case, the standby control device executes the process assigned to the active control device in place of the active control device based on the determined result. Moreover, specifically, the information processing apparatus 100 may output the determined result so that the user can refer to it. In this case, the user uses the standby control device to execute the process assigned to the active control device instead of the active control device based on the determined result.

(Example of BC cooperation system 200)
Next, an example of a BC cooperation system 200 to which the information processing device 100 shown in FIG. 1 is applied will be described using FIG. 2.

FIG. 2 is an explanatory diagram showing an example of the BC cooperation system 200. In FIG. 2, the BC cooperation system 200 includes a plurality of information processing devices 100, a cooperation BC network 220, and one or more cooperation destination BC networks 230. The cooperation BC network 220 includes one or more cooperation nodes 201. The cooperation destination BC network 230 includes one or more cooperation destination nodes 202.

In the BC cooperation system 200, the information processing devices 100 are connected via a wired or wireless network 210. The network 210 is, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or the like.

Further, the information processing device 100 and the cooperation BC network 220 are connected via a wired or wireless network 210. Further, the information processing device 100 and the cooperation destination BC network 230 are connected via a wired or wireless network 210.

The information processing device 100 is a computer that can operate as an active control device and a standby control device. The information processing device 100 receives a request to start a series of transactions, and transfers the request to the cooperation node 201. The information processing device 100 executes the transaction assigned by the cooperation node 201. For example, the information processing device 100 executes the assigned transaction using the cooperation destination BC network 230 and causes the cooperation destination BC network 230 to record transaction information regarding the executed transaction. When the information processing device 100 executes a transaction, the execution record of the transaction by the information processing device 100 is recorded in a block forming a cooperation BC managed by the cooperation BC network 220.

The information processing device 100 acquires blocks included in the cooperation BC managed by the cooperation BC network 220. The information processing device 100 determines the state of the other information processing device 100 corresponding to the information processing device 100 based on the execution results recorded in the acquired block. For example, the information processing apparatus 100 refers to a BU determination information management table 400, which will be described later in FIG. Determine whether or not there is.

When the information processing device 100 determines that there is an abnormality regarding another control device corresponding to the information processing device 100, the information processing device 100 executes the transaction assigned to the other information processing device 100 instead of the other information processing device 100. The information processing device 100 is, for example, a server, a PC (Personal Computer), or the like.

The cooperation node 201 is a computer that forms the cooperation BC network 220 and manages the cooperation BC. The cooperation node 201 receives a request to start a series of transactions from the information processing device 100. When the cooperation node 201 receives the request, it allocates the transaction to each information processing device 100 and causes each information processing device 100 to execute the transaction. The collaboration node 201 manages the assignment results using a person-in-charge information management table 600, which will be described later in FIG.

The collaboration node 201 records the execution results in the collaboration BC under the control of the information processing device 100. The cooperation node 201 is equipped with logic called a smart contract that generates transaction information, for example. The collaboration node 201 generates transaction information corresponding to the execution results using, for example, a smart contract, and records it in the collaboration BC. The cooperation node 201 is, for example, a server or a PC.

The cooperation destination node 202 is a computer that forms the cooperation destination BC network 230 and manages the cooperation destination BC. The cooperation destination node 202 records transaction information in the cooperation destination BC under the control of the information processing device 100. The cooperation destination node 202 is equipped with logic called a smart contract that generates transaction information, for example. The cooperation destination node 202 generates transaction information using, for example, a smart contract, and records it in the cooperation destination BC. The cooperation destination node 202 is, for example, a server or a PC.

(Example of hardware configuration of information processing device 100)
Next, an example of the hardware configuration of the information processing device 100 will be described using FIG. 3.

FIG. 3 is a block diagram showing an example of the hardware configuration of the information processing device 100. In FIG. 3, the information processing device 100 includes a CPU (Central Processing Unit) 301, a memory 302, a network I/F (Interface) 303, a recording medium I/F 304, and a recording medium 305. Further, each component is connected to each other by a bus 300.

Here, the CPU 301 is in charge of overall control of the information processing apparatus 100. The memory 302 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash ROM, and the like. Specifically, for example, a flash ROM or ROM stores various programs, and a RAM is used as a work area for the CPU 301. The program stored in the memory 302 is loaded into the CPU 301 and causes the CPU 301 to execute the coded processing.

Network I/F 303 is connected to network 210 through a communication line, and connected to other computers via network 210. The network I/F 303 serves as an internal interface with the network 210, and controls data input/output from other computers. The network I/F 303 is, for example, a modem or a LAN adapter.

The recording medium I/F 304 controls reading/writing of data to/from the recording medium 305 under the control of the CPU 301 . The recording medium I/F 304 is, for example, a disk drive, an SSD (Solid State Drive), a USB (Universal Serial Bus) port, or the like. The recording medium 305 is a nonvolatile memory that stores data written under the control of the recording medium I/F 304. The recording medium 305 is, for example, a disk, a semiconductor memory, a USB memory, or the like. The recording medium 305 may be removable from the information processing apparatus 100.

In addition to the components described above, the information processing device 100 may include, for example, a keyboard, a mouse, a display, a printer, a scanner, a microphone, a speaker, and the like. Further, the information processing apparatus 100 may include a plurality of recording medium I/Fs 304 and recording media 305. Further, the information processing apparatus 100 does not need to have the recording medium I/F 304 or the recording medium 305.

(Stored contents of BU determination information management table 400)
Next, an example of the stored contents of the BU determination information management table 400 will be explained using FIG. 4. The BU determination information management table 400 is realized, for example, by a storage area such as the memory 302 or the recording medium 305 of the information processing apparatus 100 shown in FIG. 3.

FIG. 4 is an explanatory diagram showing an example of the stored contents of the BU determination information management table 400. As shown in FIG. 4, the BU determination information management table 400 has fields of cooperation execution ID_processing ID, process content, BU condition, and a list of transactions that match the condition. In the BU determination information management table 400, BU determination information is stored as a record 400-a by setting information in each field for each transaction. a is any integer.

In the field of cooperation execution ID_processing ID, information that enables identification of any transaction in the series of transactions is set. For example, the cooperation execution ID_processing ID field contains the cooperation execution ID, which is identification information that identifies the entire series of transactions, and the processing ID, which is identification information that identifies any one of the transactions in the series of transactions. Concatenated information is set.

The processing content of any of the above transactions is set in the processing content field. The processing content includes a processing ID, a cooperation partner BCID that is identification information for identifying the cooperation destination BC network 230 regarding any of the above transactions, and any one of processing execution parameters regarding any of the above transactions. The processing content is, for example, remittance from one account to another account. The processing execution parameters include, for example, "from" indicating the remittance source, "to" indicating the remittance destination, and "amount" indicating the remittance amount.

In the BU condition field, a BU condition that triggers one of the above transactions to be executed by another control device in place of the control device to which one of the above transactions is assigned is set. The BU condition indicates, for example, that a predetermined number or more of other transactions that are determined to be of the same type as any of the above transactions are completed. The BU conditions include, for example, a condition indicating a condition for determining that transactions are of the same type, and a number indicating a predetermined number to be compared with the number of other transactions determined to be of the same type. In the field of the transaction list that meets the condition, a transaction list is set in which processing execution parameters for each of the other transactions that satisfy the condition and are determined to be the same type as any of the above transactions are registered.

(Example of hardware configuration of collaboration node 201)
Next, an example of the hardware configuration of the cooperation node 201 will be described using FIG. 5.

FIG. 5 is a block diagram showing an example of the hardware configuration of the cooperation node 201. In FIG. 5, the cooperation node 201 includes a CPU (Central Processing Unit) 501, a memory 502, a network I/F (Interface) 503, a recording medium I/F 504, and a recording medium 505. Further, each component is connected to each other by a bus 500.

Here, the CPU 501 is in charge of overall control of the cooperation node 201. The memory 502 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and a flash ROM. Specifically, for example, a flash ROM or ROM stores various programs, and a RAM is used as a work area for the CPU 501. The program stored in the memory 502 is loaded into the CPU 501 and causes the CPU 501 to execute the coded processing.

Network I/F 503 is connected to network 210 through a communication line, and connected to other computers via network 210. The network I/F 503 serves as an internal interface with the network 210, and controls data input/output from other computers. The network I/F 503 is, for example, a modem or a LAN adapter.

The recording medium I/F 504 controls reading/writing of data to/from the recording medium 505 under the control of the CPU 501 . The recording medium I/F 504 is, for example, a disk drive, an SSD (Solid State Drive), a USB (Universal Serial Bus) port, or the like. The recording medium 505 is a nonvolatile memory that stores data written under the control of the recording medium I/F 504. The recording medium 505 is, for example, a disk, a semiconductor memory, a USB memory, or the like. The recording medium 505 may be removable from the cooperation node 201.

In addition to the components described above, the collaboration node 201 may include, for example, a keyboard, a mouse, a display, a printer, a scanner, a microphone, a speaker, and the like. Moreover, the cooperation node 201 may have a plurality of recording medium I/Fs 504 and recording media 505. Moreover, the cooperation node 201 does not need to have the recording medium I/F 504 or the recording medium 505.

(Contents stored in the person-in-charge information management table 600)
Next, an example of the contents stored in the person-in-charge information management table 600 will be explained using FIG. 6. The person-in-charge information management table 600 is realized, for example, by a storage area such as the memory 502 or the recording medium 505 of the cooperation node 201 shown in FIG.

FIG. 6 is an explanatory diagram showing an example of the stored contents of the person-in-charge information management table 600. As shown in FIG. 6, the person in charge information management table 600 has fields for cooperation destination BCID, processing order, and person in charge of processing. In the person-in-charge information management table 600, the person-in-charge information is stored as a record 600-b by setting information in each field for each series of transactions. b is an arbitrary integer.

The cooperation destination BCID, which is identification information for identifying the cooperation destination BC used in a series of transactions, is set in the cooperation destination BCID field. In the processing order and processing person fields, identification information for identifying the information processing devices 100 in charge of each transaction in the series of transactions is arranged in the order in which they are in charge of each transaction in the series of transactions, and the processing order It is set as information indicating. Identification information for identifying the information processing apparatus 100 that is in charge of the currently executing transaction among the series of transactions is set in the processing order and processing in charge field as information indicating the processing in charge.

(Example of hardware configuration of cooperation destination node 202)
The hardware configuration example of the collaboration destination node 202 is specifically the same as the hardware configuration example of the collaboration node 201 shown in FIG. 5, so the description thereof will be omitted.

(Functional configuration example of BC collaboration system 200)
Next, an example of the functional configuration of the BC cooperation system 200 will be described using FIG. 7.

FIG. 7 is a block diagram showing an example of the functional configuration of the BC cooperation system 200. In the BC cooperation system 200, the information processing device 100 includes a first storage section 700, a first acquisition section 701, a determination section 702, a transaction section 703, and a first output section 704.

The first storage unit 700 is realized, for example, by a storage area such as the memory 302 or the recording medium 305 shown in FIG. 3. Although a case will be described below in which the first storage unit 700 is included in the information processing device 100, the present invention is not limited to this. For example, there may be a case where the first storage unit 700 is included in a device different from the information processing device 100, and the storage contents of the first storage unit 700 can be referenced from the information processing device 100.

The first acquisition unit 701 to first output unit 704 function as an example of a control unit. Specifically, the first acquisition unit 701 to the first output unit 704, for example, cause the CPU 301 to execute a program stored in a storage area such as the memory 302 or the recording medium 305 shown in FIG. The network I/F 303 realizes this function. The processing results of each functional unit are stored in a storage area such as the memory 302 or the recording medium 305 shown in FIG. 3, for example.

The first storage unit 700 stores various information that is referenced or updated in the processing of each functional unit. The first storage unit 700 stores blocks, for example. In the block, an execution record of a process assigned to at least one of the plurality of active control devices by the control device is recorded. The processing is, for example, a transaction. Specifically, the process relates to any one of the plurality of cooperation destination BC networks 230.

The control device is realized by, for example, the information processing device 100. In other words, the information processing device 100 operates as an active control device or a standby control device. The control device may operate as an active system or a standby system. The control device may be implemented, for example, by a computer other than the information processing device 100. For example, the block is acquired by the first acquisition unit 701 and stored in the first storage unit 700. The block may further have a processing request recorded therein. The processing request may be included in the execution record.

The first acquisition unit 701 acquires various information used in processing of each functional unit. The first acquisition unit 701 stores the acquired various information in the first storage unit 700 or outputs it to each functional unit. Further, the first acquisition unit 701 may output various information stored in the first storage unit 700 to each functional unit. The first acquisition unit 701 acquires various information based on, for example, a user's operation input. The first acquisition unit 701 may receive various information from a device different from the information processing device 100, for example.

The first acquisition unit 701 acquires a block from the cooperation BC network 220. The cooperative BC network 220 includes nodes corresponding to each of the plurality of control devices. The cooperation BC network 220 manages blocks in which the execution results of the processes assigned to each control device by the control device are recorded. The cooperation BC network 220 manages, for example, a cooperation BC formed by connecting blocks in which execution records of processes assigned to each control device are recorded by the control devices. Each node acquires the execution results of the processing by the control device corresponding to the node and records them in a block. In the cooperative BC network 220, the nodes share the same block, thereby sharing the execution results of the processes performed by the respective control devices.

The first acquisition unit 701 acquires, for example, a BU request. The BU request indicates that the information processing device 100 has been set as a standby control device corresponding to any active control device. The BU request includes, for example, information that makes it possible to specify the active control device that corresponds to the information processing device 100 that is the standby control device. Specifically, the first acquisition unit 701 acquires the BU request by receiving it from the collaboration node 201.

The first acquisition unit 701 acquires a processing request, for example. The processing request indicates processing related to one of the cooperation destination BC networks 230 assigned to the information processing device 100. Specifically, the first acquisition unit 701 acquires a processing request by receiving it from the collaboration node 201. More specifically, the first acquisition unit 701 acquires the processing request by extracting the processing request included in the block acquired from the collaboration node 201.

The first acquisition unit 701 may receive a start trigger that starts processing of any functional unit. The start trigger is, for example, a predetermined operation input by the user. The start trigger may be, for example, receiving predetermined information from another computer. The start trigger may be, for example, that any functional unit outputs predetermined information.

The first acquisition unit 701 receives, for example, the acquisition of a BU request as a start trigger for starting the process of the determination unit 702. The first acquisition unit 701 receives the acquisition of the processing request as a start trigger for starting the processing of the transaction unit 703.

The determining unit 702 determines the state of at least one of the control devices based on the execution results included in the acquired block. One of the control devices is set as an active control device corresponding to the information processing device 100, for example. The determining unit 702 identifies one of the control devices, for example, based on information that is included in the acquired BU request and allows one of the control devices corresponding to the information processing device 100 to be specified. The determining unit 702 then determines the state of any of the identified control devices based on the execution results included in the acquired block.

Specifically, the determining unit 702 determines whether a process assigned to another control device satisfies conditions for determining that the process is the same type of process as the process assigned to one of the control devices, based on the execution results included in the acquired block. Determine the number of processes performed. Specifically, when the identified number is a predetermined number or more, the determination unit 702 determines that the state of one of the control devices is abnormal. An abnormal state of the control device means that there is an abnormality related to the control device, and indicates that there is an abnormality in the control device itself or a communication path of the control device. On the other hand, specifically, when the specified number is less than a predetermined number, the determination unit 702 determines that the state of one of the control devices is normal.

The condition indicates, for example, that a process having the same parameters as the process is determined to be the same type of process. For example, if the processing content is remittance, the parameters include the remittance amount, remittance destination, or remittance source. The condition indicates that a process that targets the same cooperation destination BC network 230 as the process is determined to be the same type of process. Thereby, the determination unit 702 can accurately determine whether or not there is an abnormality regarding the control device.

Transaction unit 703 executes processing. For example, the transaction unit 703 executes processing related to the cooperation destination BC network 230 that is allocated to the information processing device 100 based on a processing request. Then, the transaction unit 703 records, for example, the execution results of the process in a block managed by the cooperation BC network 220. Thereby, the trading unit 703 can enable a plurality of active control devices to share the process execution results via the cooperative BC network 220.

For example, when the trading unit 703 determines that the state of any of the control devices corresponding to the information processing device 100 is abnormal, the transaction unit 703 causes the information processing device 100 to execute a process assigned to any of the control devices. Then, the transaction unit 703 records the execution results of the process in a block managed by the cooperation BC network 220, for example. Thereby, the trading unit 703 can enable a plurality of active control devices to share the process execution results via the cooperative BC network 220. Furthermore, the transaction unit 703 can execute processing in place of the abnormal control device, and can continue to enable the BC cooperation system 200 to operate normally.

The first output unit 704 outputs the processing results of each functional unit. The output format is, for example, displaying on a display, printing out to a printer, transmitting to an external device via network I/F 303, or storing in a storage area such as memory 302 or recording medium 305. Thereby, the first output unit 704 can notify the user of the processing results of each functional unit, thereby improving the usability of the information processing apparatus 100. The first output unit 704 outputs, for example, the execution result of the process.

In the BC cooperation system 200, the cooperation node 201 includes a second storage section 710, a second acquisition section 711, an allocation section 712, a request section 713, and a second output section 714.

The second storage unit 710 is realized, for example, by a storage area such as the memory 502 or the recording medium 505 shown in FIG. 5. Although a case will be described below in which the second storage unit 710 is included in the collaboration node 201, the present invention is not limited to this. For example, there may be a case in which the second storage unit 710 is included in a device different from the collaboration node 201, and the storage contents of the second storage unit 710 can be referenced from the collaboration node 201.

The second acquisition unit 711 to second output unit 714 function as an example of a control unit. Specifically, the second acquisition unit 711 to the second output unit 714, for example, cause the CPU 501 to execute a program stored in a storage area such as the memory 502 or the recording medium 505 shown in FIG. The network I/F 503 realizes this function. The processing results of each functional unit are stored in a storage area such as the memory 502 or the recording medium 505 shown in FIG. 5, for example.

The second storage unit 710 stores various information that is referenced or updated in the processing of each functional unit. The second storage unit 710 stores a first order in which processes are assigned to a plurality of control devices. The first order is set in advance by, for example, an administrator. The first order may be acquired by the second acquisition unit 711 and stored in the second storage unit 710, for example.

The second storage unit 710 stores a second order for setting standby control devices. The second order is set in advance by, for example, an administrator. The second order may be acquired by the second acquisition unit 711 and stored in the second storage unit 710, for example. The second storage unit 710 stores blocks. The second storage unit 710 stores, for example, a cooperation BC in which blocks are connected.

The second acquisition unit 711 acquires various information used in processing of each functional unit. The second acquisition unit 711 stores the acquired various information in the second storage unit 710 or outputs it to each functional unit. Further, the second acquisition unit 711 may output various information stored in the second storage unit 710 to each functional unit. The second acquisition unit 711 acquires various information based on, for example, a user's operation input. The second acquisition unit 711 may receive various information from a device different from the cooperation node 201, for example.

The second acquisition unit 711 acquires the first order. The first order is, for example, round robin. The second acquisition unit 711 receives input in the first order, for example, based on an operational input from the administrator.

The second acquisition unit 711 acquires the second order. The second order is, for example, round robin. The second acquisition unit 711 receives input in the second order based on, for example, an operational input by the administrator.

The second acquisition unit 711 acquires a cooperation request requesting execution of a series of processes. The second acquisition unit 711 acquires, for example, a cooperation request requesting execution of a series of processes by receiving from another computer serving as a client.

The second acquisition unit 711 acquires the execution results of processing by the control device. The second acquisition unit 711 acquires, for example, the execution results of processes by the control device by receiving them from the control device. The second acquisition unit 711 records the received execution results in a block included in the collaboration BC.

The second acquisition unit 711 may receive a start trigger to start processing of any functional unit. The start trigger is, for example, a predetermined operation input by the user. The start trigger may be, for example, receiving predetermined information from another computer. The start trigger may be, for example, that any functional unit outputs predetermined information. The second acquisition unit 711 receives, for example, the acquisition of a cooperation request as a start trigger for starting processing between the allocation unit 712 and the request unit 713.

When the assignment unit 712 receives the collaboration request, it assigns each process of the series of processes to the plurality of control devices according to the first order. For example, the allocation unit 712 sequentially allocates each process in the series of processes to a plurality of control devices one by one. Thereby, the allocation unit 712 can distribute the load among the plurality of control devices.

When the allocation unit 712 receives the cooperation request, it sets a standby control device for each process in the series of processes among the plurality of control devices, according to the second order. For example, the allocation unit 712 sequentially sets a plurality of control devices one by one as a standby control device for each process. Thereby, the allocation unit 712 can distribute the load among the plurality of control devices.

The requesting unit 713 sends a processing request requesting the control device to execute the assigned process to the control device. The request unit 713 sequentially transmits processing requests requesting execution of a process included in a series of processes to the control device to which the process is assigned, one by one. The requesting unit 713 controls, for example, via the second outputting unit 714, to record the execution results including a processing request requesting execution of a process included in a series of processes in a block. Thereby, the requesting unit 713 can appropriately execute a series of processes. For example, the requesting unit 713 can record the execution results and assign the next person in charge in the same transaction in the collaboration node 201.

The second output unit 714 outputs the processing results of each functional unit. The output format is, for example, displaying on a display, printing out to a printer, transmitting to an external device via network I/F 503, or storing in a storage area such as memory 502 or recording medium 505. Thereby, the second output unit 714 can notify the user of the processing results of each functional unit, thereby improving the usability of the collaboration node 201.

The second output unit 714 outputs blocks, for example. Specifically, the second output unit 714 transmits the block to the information processing device 100 in response to an inquiry from the information processing device 100. Thereby, the second output unit 714 can enable the information processing apparatus 100 to use the execution results recorded in the block.

(Flow of operation of BC cooperation system 200)
Next, the flow of operation of the BC cooperation system 200 will be explained using FIGS. 8 and 9.

8 and 9 are explanatory diagrams showing the flow of operations of the BC cooperation system 200. In FIG. 8, each information processing device 100 has a cooperation engine that realizes functions as an active system and a standby system control device. In the example of FIG. 8, a cooperation engine 1, a cooperation engine 2, a cooperation engine 3, and a cooperation engine 4 exist in different information processing apparatuses 100, respectively. Each cooperation engine has a long-term buffer 801 and a BU determination information management table 400.

The cooperation nodes 201 correspond to different cooperation engines. The collaboration node 201 manages a collaboration BC that is a combination of blocks in which execution results indicating the completion of processing execution and the next execution request are recorded. Each collaboration node 201 sets a person in charge of processing Process 1 according to the collaboration rule, and sends an execution request for Process 1 to the collaboration engine corresponding to its own node via a block. The cooperation rule is a rule for sequentially executing a series of processes, indicating the order of a series of processes, and indicating a process ID, a cooperation destination BCID, a BU condition, etc. for each process. Processing 1 is executed, for example, by a cooperation engine set to be in charge of processing. For example, suppose that the execution result of the completion of execution of process 1 is recorded in the block.

When the execution of process 1 is completed, each collaboration node 201 sets the collaboration engine 2 to be in charge of processing 2, sets the collaboration engine 1 to be in charge of BU of process 2, and the collaboration engine 1 Set the BU conditions that trigger BU for process 2. Each collaboration node 201 transmits a request to execute process 2 to the collaboration engine corresponding to its own node via a block.

It is assumed that each cooperation node 201 sets a person in charge of processing Process 3 and sends an execution request for Process 3 to the cooperation engine corresponding to its own node via a block. Assume that the process 3 is executed by the cooperation engine 3, for example. Further, it is assumed that each cooperation node 201 sets a person in charge of processing Process 4, and sends an execution request for Process 4 to the cooperation engine corresponding to its own node via a block. For example, it is assumed that the process 4 is executed by the cooperation engine 4. After that, assume that, for example, an execution record of completion of execution of process 3 and an execution record of completion of execution of process 4 are recorded in the block.

Since the cooperative engine 1 is in charge of the BU, the cooperative engine 1 determines whether there is an abnormality regarding the cooperative engine 2 based on the set BU conditions. For example, the cooperation engine 1 acquires blocks included in the cooperation BC from the cooperation node 201 corresponding to its own device, and stores the execution results of the completion of execution of other processes determined to be of the same type as process 2 in a long-term buffer. 801. The conditions for determining the same type are included in the BU conditions, for example. For example, another process having the same parameters as process 2 is determined to be of the same type as process 2. For example, another process related to the same cooperation destination BC network 230 as process 2 is determined to be the same type as process 2. For example, when a block whose execution record is recorded is added to the collaboration BC, the collaboration node 201 notifies the collaboration engine corresponding to its own node of the added block.

For example, the cooperation engine 1 calculates the number of completed execution results of other processes that are determined to be of the same type as the process 2, based on the execution results accumulated in the long-term buffer 801. Specifically, since there are processes 3 and 4 that are determined to be the same type as process 2, the cooperation engine 1 calculates the number 2 of other processes that are determined to be the same type as process 2. The cooperation engine 1 determines whether the calculated number 2 is greater than or equal to a predetermined number. The predetermined number is included in the BU condition, for example. The predetermined number is, for example, two.

Here, if another process that is determined to be the same type as Process 2 and is not related to Cooperation Engine 2 has already completed execution, but Process 2 has not yet completed execution, there is a probability that there is an abnormality related to Cooperation Engine 2. is considered to be relatively high. For example, it is considered that there is a relatively high probability that the cooperation destination BC network 230 related to process 2, other cooperation engines that have completed execution of other processes, etc. are normal. In addition, in this case, since multiple other processes determined to be of the same type as process 2 have completed execution, the time required for process 2 is relatively long, and the probability that cooperative engine 2 is normal is relatively low. it is conceivable that.

Therefore, if the calculated number is greater than or equal to the predetermined number, the cooperation engine 1 determines that there is an abnormality regarding the cooperation engine 2. On the other hand, if the calculated number is less than the predetermined number, the cooperation engine 1 determines that there is no abnormality regarding the cooperation engine 2. Thereby, each cooperation engine does not need to communicate with other cooperation engines, and it is possible to reduce the amount of processing. Since the cooperative engine utilizes the number of execution results accumulated in the long-term buffer 801, it is possible to easily determine with accuracy whether or not there is an abnormality regarding other cooperative engines. Next, moving on to the explanation of FIG. 9, a specific example of the BU condition will be explained.

In FIG. 9, the BU condition is a condition for determining that the processing of the cooperation engine has not been completed and that there is an abnormality regarding the cooperation engine. For example, assume that the parameters of process 1 include chainID="chain0", from="alice", to="bob", and amount="100". For example, assume that the parameters of process 2 include chainID="chain0", from="alice", to="taro", and amount="1".

The BU condition regarding process 2 indicates, for example, that another process having the same chain ID="chain0" and from="alice" as process 2 is determined to be the same type of process as process 2. The BU condition regarding process 2 is that if the execution record of completion of execution of another process of the same type as process 2 is number: 2 or more, it is determined that process 2 of the cooperative engine 2 has not completed execution, and the BU condition regarding the cooperative engine 2 is Indicates that it is determined that there is an abnormality. The collaboration engine 1 determines whether or not the BU condition regarding process 2 is satisfied based on the block acquired from the collaboration node 201 via the short-term buffer 901.

(Example of operation of BC cooperation system 200)
Next, an example of the operation of the BC cooperation system 200 will be described using FIGS. 10 to 17.

10 to 17 are explanatory diagrams showing operation examples of the BC cooperation system 200. As shown in FIG. 10, in the operation example, for each process, a cooperation engine in charge of the process and a cooperation engine in charge of the BU regarding the process are set.

Each cooperation node 201 sets, for each process, a cooperation engine in charge of the process and a cooperation engine in charge of the BU regarding the process, based on a preset cooperation rule and allocation order, for example. For example, each collaboration node 201 sends a processing execution request to the collaboration engine corresponding to its own node, including information that enables identification of the collaboration engine set as the processing person and the BU person, and the BU condition. , send via block. This allows each cooperation engine to specify whether its own device is in charge of processing or in charge of BU. Each cooperation engine can specify that execution of a process has been started by one of the cooperation engines.

Further, when the process is completed, the cooperation engine notifies the cooperation node 201 corresponding to its own device of the execution result indicating that the process has been completed. Each collaboration node 201 adds a block in which the execution results notified to any collaboration node 201 are recorded to the collaboration BC and shares the block. Each cooperation node 201 transmits the added block to the cooperation engine corresponding to its own node. This allows each linked engine to refer to the execution results indicating that processing has been completed by any linked engine.

If the cooperative engine is in charge of BU, the cooperative engine determines whether or not to BU the process targeted for BU on behalf of another cooperative engine in charge of the process, based on the BU conditions and the execution results recorded in the block. judge. The BU target process is a process that the own device is assigned to be in charge of BU, and a process that is assigned to another cooperation engine that is in charge of the process. Thereby, each cooperation engine does not need to communicate with other cooperation engines in order to monitor other cooperation engines, and it is possible to reduce the amount of processing. A cooperative engine can easily determine with accuracy whether or not there is an abnormality regarding other cooperative engines. In the operation example, the cooperation BC is, for example, of a consortium type. The collaboration node 201 has functions as a peer and an orderer. Next, the description will move on to FIG. 11.

In FIG. 11, the collaboration engine includes a BU determination information management table 400, a collaboration execution module 1111, a long-term buffer 1112, a Tx/block communication unit (cooperation destination BC) 1120, and a Tx/block communication unit (cooperation BC). 1130.

The Tx/block communication unit (collaboration destination BC) 1120 includes a cooperation destination BCTx execution module 1121 , a cooperation destination BC monitoring module 1122 , a Tx pool 1123 , and a block cache 1124 . The Tx/block communication unit (BC for cooperation) 1130 includes a BCTx execution module for cooperation 1131 and a short-term buffer 1132.

The cooperation node 201 includes a block creation/distribution unit 1140 and a Tx/block communication unit (Peer) 1150. The Tx/block communication unit (Peer) 1150 includes a responsible information management table 600, a Tx execution/reference unit 1151, a storage area 1152, and a cooperation BC 1153. The BC management system realizes various functions by each functional unit. For example, the BC management system implements a shared function between cooperative engines, a cooperative processing execution function, a BU start function, a BU target process accumulation function, a BU execution function, and an allocation function.

The shared function between cooperative engines is a function that makes the cooperative engines redundant. The inter-cooperation engine sharing function is a function that allows a plurality of co-operation engines to share a process execution request for each co-operation engine. The inter-cooperation engine sharing function is, for example, a function that allows a plurality of co-operation engines to share a process execution request to each co-operation engine via Tx monitored by the co-operation node 201.

In the cooperation engine, the cooperation processing execution function is a function that causes the cooperation engine to execute a process based on a process execution request notified to the cooperation engine from the cooperation node 201 corresponding to the cooperation engine. be. In the cooperative engine, the cooperative processing execution function executes the cooperative processing execution function, for example, based on the cooperative engine ID that makes it possible to specify the processing person or BU person in charge described in the execution request. This is a function that executes.

In the cooperation engine, the BU start function causes the cooperation engine to execute the BU target process based on a process execution request notified to the cooperation engine from the cooperation node 201 corresponding to the cooperation engine. This is a function to start detecting a trigger. In the linked engine, the BU start function executes the process for the BU if the linked engine is in charge of the BU, based on the linked engine ID that enables identification of the processing person or the BU person described in the execution request. This is a function that starts detecting an opportunity to do so. Specifically, in the cooperation engine, the BU start function causes the cooperation engine to start monitoring the execution completion Tx of the BU target process and the execution completion Tx of other processes that are determined to be of the same type as the BU target process. This is a function that starts detecting an opportunity to execute a BU target process.

In the cooperation engine, if the cooperation engine is in charge of BU, the BU target process accumulation function associates the BU target process with the execution completion Tx of another process that is determined to be the same type as the BU target process. This is a function to accumulate in the long-term buffer 1112. In the cooperation engine, the BU execution function is a function that executes the process for the BU if the cooperation engine is in charge of the BU and the BU condition is satisfied. The BU execution function is a function that, when a BU target process is executed, registers the execution result in the cooperation BC as an execution completion Tx.

The allocation function is realized by a smart contract that the collaboration node 201 has. In the coordination node 201, the assignment function is a function of setting processing responsibility and BU responsibility to each cooperation engine according to a preset assignment order such as round robin. In each cooperation node 201, the allocation function specifically sets the processing responsibility and the BU responsibility to the same cooperation engine according to the same allocation order.

In each collaboration node 201, the assignment function transmits a process execution request including a collaboration engine ID that enables identification of the set processing person and BU person to the collaboration engine corresponding to the collaboration node 201. Specific operations of each functional unit will be described later with reference to FIGS. 12, 14, and 15. Next, the explanation will move on to FIG. 12.

In FIG. 12, (12-1) the collaboration engine receives a collaboration execution request from the client application 1100. A collaboration execution request is a request to execute a series of processes.

(12-2) Upon receiving the collaboration execution request, the collaboration execution module 1111 generates a collaboration execution ID, assigns it to the collaboration execution request, and transmits it to the collaboration BCTx execution module 1131. The collaboration BCTx execution module 1131 communicates with the collaboration node 201 and causes the collaboration node 201 to execute collaboration start Tx. The collaboration node 201 adds the block recording the collaboration start Tx to the collaboration BC.

The block creation/distribution unit 1140, for example, generates a block recording the collaboration start Tx and transmits it to the Tx/block communication unit 1150 of each collaboration node 201. The Tx/block communication unit 1150 receives, for example, a block recording the collaboration start Tx, and adds it to the collaboration BC.

(12-3) The Tx execution/reference unit 1151 executes each of a series of processes according to the cooperation rules stored in the storage area 1152 in response to the addition of the block recording the cooperation start Tx to the cooperation BC. Specify the processing of The Tx execution/reference unit 1151 assigns a processing person and a BU person in charge of each of the specified series of processes to the cooperation engine according to the cooperation rules stored in the storage area 1152. The Tx/block communication unit (Peer) 1150 sends a request for execution of the process, including a cooperation engine ID that enables identification of the cooperation engine in charge of processing and BU for each process in a series of processes, to the Tx/block through the BC 1153. It is transmitted to the communication department (BC for cooperation) 1130.

The Tx/block communication unit (BC for cooperation) 1130 accumulates each process execution request received from the BC 1153 in the short-term buffer 1132 . The Tx/block communication unit (BC for collaboration) 1130 transmits a request for execution of the first process in a series of processes to the collaboration execution module 1111. Thereby, the collaboration execution module 1111 can specify the start of execution of processing in each collaboration engine.

(12-4) The cooperation execution module 1111 determines whether or not the cooperation engine ID of its own device is the cooperation engine ID of the person in charge of processing or the person in charge of BU included in the process execution request. If the cooperation engine ID of its own device is the cooperation engine ID in charge of processing, the cooperation execution module 1111 performs various operations described later in FIG. 14 to execute the cooperation processing. If the cooperation engine ID of its own device is the cooperation engine ID in charge of BU, the cooperation execution module 1111 performs various operations described later in FIG. 15 to execute the BU process.

(12-5) The Tx/block communication unit (BC for cooperation) 1130 sequentially transmits a request for execution of subsequent processes in the series of processes to the cooperation execution module 1111. The Tx/block communication unit (BC for cooperation) 1130, for example, refers to the short-term buffer 1132, selects the subsequent process for which the previous process has been completed, and requests execution of the selected process to the cooperation execution module 1111. Send to. Thereafter, the cooperation engine repeats the various operations (12-4) and (12-5) until the last process in the series of processes is completed. Next, moving on to the explanation of FIG. 13, an example of the operation (12-3) will be explained.

In FIG. 13, each cooperation node 201 has a smart contract. The smart contract implements the Tx execution/reference unit 1151. One of the collaboration nodes 201 is requested to execute collaboration according to the collaboration rules stored in the storage area 1152 in response to the addition of the block recording the collaboration start Tx to the collaboration BC by the smart contract. Identify each process in a series of processes. For example, the collaboration node 201 corresponding to the collaboration engine that executed the process executes the smart contract.

The coordination node 201 uses a smart contract to assign processing and BU responsibility for each of the series of processes to the coordination engine according to the coordination rules stored in the storage area 1152. If there are multiple collaboration execution requests, the coordination node 201 uses a smart contract to sequentially assign processing and BU responsibility to the coordination engine for each process in a process group that includes a series of processes corresponding to each collaboration execution request. You can. The collaboration node 201 stores, for each collaboration destination BCID, a collaboration engine ID column indicating the processing order and the collaboration engine ID currently in charge of processing in the responsible information management table 600.

The collaboration node 201 uses the smart contract to send to each collaboration engine a request to execute the process, including a collaboration engine ID that allows identification of the collaboration engine in charge of processing and BU for each process in a series of processes. . The collaboration node 201 uses a smart contract to enable each collaboration engine to obtain a process execution request, etc. via the collaboration start Tx and execution completion Tx included in the block of the collaboration BC. Thereby, each cooperation node can enable the cooperation engines to mutually BU the processes assigned to the cooperation engines.

Next, moving on to the explanation of FIG. 14, an example will be described in which, in (12-4), the cooperation execution module 1111 determines that the cooperation engine ID of the own device is the cooperation engine ID in charge of processing. . In FIG. 14, the collaboration execution module 1111 determines that the collaboration engine ID of its own device is the collaboration engine ID in charge of the process included in the process execution request.

(14-1) The cooperation execution module 1111 specifies the processing content based on the processing request. The collaboration execution module 1111 generates a Tx for the collaboration destination BC based on the specified processing content, and stores the TxID corresponding to the generated Tx in the memory. The cooperation execution module 1111 transmits the generated Tx to the Tx/block communication unit (cooperation destination BC) 1120. The Tx/block communication unit (cooperation destination BC) 1120 transmits a processing request to the cooperation destination node 202, causes the cooperation destination node 202 to execute the received Tx, and adds the block in which the Tx is recorded to the cooperation destination BC.

(14-2) The cooperation destination node 202 notifies the Tx/block communication unit (cooperation destination BC) 1120 of the block added to the cooperation destination BC. The cooperation destination BC monitoring module 1122 receives the block and transmits it to the cooperation execution module 1111. The collaboration execution module 1111 receives blocks included in the collaboration destination BC. The cooperation execution module 1111 acquires the processing content from the received block using the TxID stored in the memory as a key. The collaboration execution module 1111 executes the execution completion Tx in the collaboration node 201 based on the acquired processing content, and causes the block in which the execution completion Tx is recorded to be added to the collaboration BC. Each collaboration node 201 transmits the block in which the execution completion Tx, which has been added to the collaboration BC, is recorded, to the respective collaboration engine. Thereby, the cooperation engine can execute the process if its own device is in charge of the process. Moreover, each cooperation engine can share the execution completion Tx of a process, and it is possible to determine an opportunity to BU any one of the processes.

Next, moving on to the explanation of FIG. 15, an example will be described in which, in (12-4), the cooperation execution module 1111 determines that the cooperation engine ID of the own device is the cooperation engine ID in charge of the BU. . In FIG. 15, the collaboration execution module 1111 determines that the collaboration engine ID of its own device is the collaboration engine ID in charge of the BU.

(15-1) The cooperation execution module 1111 associates the BU conditions included in the process request with the requested BU process and stores it in the long-term buffer 1112.

(15-2) The collaboration execution module 1111 executes the BU target process at the collaboration target BC based on the parameters of the BU target process through the collaboration target BC monitoring module 1122 in the Tx/block communication unit (cooperation target BC) 1120. The processing execution Tx is monitored. The cooperation destination BC monitoring module 1122 stores the block notified from the cooperation destination node 202 in the block cache 1124. If the block in which the processing execution Tx of the BU target process in the collaboration target BC is recorded is stored in the block cache 1124, the collaboration destination BC monitoring module 1122 transfers the processing execution Tx of the BU target process to the Tx pool 1123. accumulate.

(15-3) The cooperation execution module 1111 sends the execution completion Tx of the BU target process in the cooperation BC from the short-term buffer 1132 in the Tx/block communication unit (cooperation BC) 1130 to the process ID Search using the key.

If the cooperation execution module 1111 finds the execution completion Tx of the BU target process, it means that the BU target process has been successfully executed by another collaboration engine, and the BU target process is not executed by its own device. I judge that it is okay. Therefore, the cooperation execution module 1111 deletes the BU conditions stored for the BU target process and the process execution Tx of the BU target process accumulated in the Tx pool 1123. If the cooperative execution module 1111 does not find the process execution Tx of the BU target process, it moves to operations (15-4) and (15-5).

(15-4) The cooperation execution module 1111 is notified of the execution completion Tx recorded in the block included in the cooperation BC through the short-term buffer 1132. The cooperation execution module 1111 determines whether the notified execution completion Tx satisfies the BU condition stored in the long-term buffer 1112. The cooperation execution module 1111 associates the execution completion Tx that satisfies the BU condition with the BU target process, and stores it in the BU determination information management table 400 as the execution completion Tx regarding another process of the same type as the BU target process. do.

The cooperation execution module 1111 determines whether the execution completion Tx related to other processes of the same type as the BU target process, which are stored in the BU determination information management table 400 in association with the BU target process, has exceeded a predetermined number. Determine. When the number exceeds a predetermined value, the cooperation execution module 1111 determines that the BU target process is to be BU, and executes the BU target process based on the BU conditions stored for the BU target process and the BU target process accumulated in the Tx pool 1123. Delete Tx etc.

(15-5) The cooperation execution module 1111 searches the Tx pool 1123 of the cooperation destination BC monitoring module 1122 for the process execution Tx of the BU target process. When the process execution Tx of the BU target process is found, the collaboration execution module 1111 executes the execution completion Tx of the BU target process in the collaboration BC via the collaboration BCTx execution module 1131. The cooperation execution module 1111 deletes the process execution Tx of the BU target process in the Tx pool 1123.

If the process execution Tx of the BU target process is not found, the collaboration execution module 1111 executes the process execution Tx of the BU target process in the collaboration destination BC via the collaboration destination BCTx execution module 1121. The collaboration execution module 1111 executes the execution completion Tx of the BU target process in the collaboration BC via the collaboration BCTx execution module 1131. The cooperation execution module 1111 deletes the BU conditions stored for the BU target process and the process execution Tx of the BU target process accumulated in the Tx pool 1123 .

Further, if the notified execution completion Tx is the execution completion Tx of the BU target process, the cooperation execution module 1111 uses the BU conditions stored for the BU target process and the BU target process accumulated in the Tx pool 1123. The execution completion Tx etc. may be deleted.

As a result, the linked engine can accurately identify the completion of execution of the BU target process, accurately determine that there is an abnormality related to other linked engines, and accurately BU the BU target process. be able to. For example, the collaboration engine accurately identifies the completion of execution of the BU target process by monitoring the process execution Tx of the BU target process in the collaboration destination BC and the execution completion Tx of the BU target process in the collaboration BC. can do.

Next, moving on to the description of FIG. 16, a specific example will be described in which the cooperation execution module 1111 BUs the process 2 that is the BU target in the cooperation engine 1 set to be in charge of the BU of the process 2.

In FIG. 16, (16-1) the cooperation execution module 1111 monitors the process execution Tx of the process 2 targeted for BU in the cooperation destination BC through the cooperation destination BC monitoring module 1122. Thereby, the cooperative engine 1 can specify whether or not the process 2 for the BU target has been completed in the cooperation destination BC, and can determine whether there is an abnormality regarding the cooperative engine 2. It can be determined whether or not to perform BU on Process 2.

(16-2) The cooperation execution module 1111 monitors the execution completion Tx in the cooperation BC through the short-term buffer 1132. At this time, the collaboration execution module 1111 may monitor the completion Tx of the process 2 targeted for BU in the collaboration BC. As a result, after the execution of the BU target process 2 in the collaboration destination BC is completed, the collaboration engine 1 can execute the BU target process 2 in the collaboration BC without any abnormality in communication between the collaboration destination BC and the collaboration engine 2. It is possible to determine whether the completion Tx was executed normally. Therefore, the cooperation engine 1 can determine whether or not there is an abnormality regarding the cooperation engine 2, and can determine whether or not to BU the process 2 targeted for BU.

(16-3) The cooperation execution module 1111 identifies the execution completion Tx that satisfies the BU condition among the discovered execution completion Tx. The cooperative execution module 1111 associates the specified execution completion Tx with the BU target process 2 and stores it in the BU determination information management table 400 as an execution completion Tx related to another process of the same type as the BU target process 2.

The cooperation execution module 1111 determines whether the execution completion Tx for other processes of the same type as the BU target process 2, which are stored in the BU determination information management table 400 in association with the BU target process 2, has exceeded a predetermined number. Determine whether or not. When the number is equal to or greater than a predetermined number, the cooperation execution module 1111 determines that the BU condition is satisfied, and determines that the process 2 to be BU is to be BU. The cooperation execution module 1111 deletes the BU conditions stored for the BU target process 2 and the process execution Tx of the BU target process 2 accumulated in the Tx pool 1123 . Thereby, the cooperative engine 1 can accurately determine that there is an abnormality regarding the cooperative engine 2, while taking into account the situation where the time required for the process 2 to be BU is relatively long.

(16-4) The cooperation execution module 1111 searches the Tx pool 1123 for the process execution Tx of process 2 that is the BU target. The cooperation execution module 1111 BUs the process 2 that is the BU target when the process execution Tx of the process 2 that is the BU target is found. If the process execution Tx of the BU target process 2 is not found, the collaboration execution module 1111 executes the process execution Tx of the BU target process 2 on the collaboration BC. Next, moving on to the description of FIG. 17, a specific example in which the cooperation execution module 1111 determines whether or not the BU condition is satisfied will be described.

In FIG. 17, the BU conditions include, for example, a condition indicating a condition for determining that BU target process 2 and other processes are of the same type, and a predetermined condition for comparing the BU target process 2 with the number of other processes determined to be of the same type. number indicating the number of . The number is, for example, 2. The condition includes, for example, chainID="chain0" and from="alice".

For example, it is assumed that the cooperation execution module 1111 discovers the execution completion Tx of process 1. It is assumed that the execution completion Tx of process 1 includes, for example, chainID="chain0", from="alice", to="bob", and amount="100" as parameters of process 1. The cooperation execution module 1111 determines that the execution completion Tx of process 1 satisfies the BU condition. The cooperation execution module 1111 sets the execution completion Tx of the process 1 in the field of the transaction list that matches the condition of the BU determination information management table 400 in association with the process 2 of the BU target.

The cooperation execution module 1111 stores, in the field of the transaction list that matches the condition of the BU determination information management table 400, the execution completion Tx regarding other processes of the same type as the BU target process 2, which is stored in association with the BU target process 2. Calculate the number of. The cooperation execution module 1111 determines that the BU condition is satisfied when the calculated number is equal to or greater than number:2. If the calculated number is not equal to or greater than number:2, the collaboration execution module 1111 determines that the BU condition is not satisfied.

As described above, the BC cooperation system 200 can eliminate the need for redundant cooperation engines to communicate with each other, and can appropriately determine whether or not there is an abnormality regarding the cooperation engines, taking into account fluctuations in processing time. It can be done.

(Overall processing procedure)
Next, an example of the overall processing procedure executed by the information processing apparatus 100 will be described using FIG. 18. The overall processing is realized by, for example, the CPU 301 shown in FIG. 3, storage areas such as the memory 302 and the recording medium 305, and the network I/F 303.

FIG. 18 is a flowchart showing an example of the overall processing procedure. In FIG. 18, the information processing apparatus 100 receives a cooperation execution request from the client application 1100 (step S1801).

Next, the information processing apparatus 100 generates a collaboration execution ID using the collaboration execution module 1111, and transmits a request including the generated collaboration execution ID to the collaboration BCTx execution module 1131 (step S1802). Then, the information processing apparatus 100 uses the cooperation BCTx execution module 1131 to execute the cooperation start Tx in the cooperation BC (step S1803). After that, the information processing apparatus 100 obtains a processing request indicating the processing person and the BU person from the cooperation node 201 based on the cooperation start Tx, and transmits it to the cooperation execution module 1111 (step S1804).

Next, if the information processing device 100 is in charge of processing or in charge of BU, the information processing device 100 uses the cooperation execution module 1111 to execute the cooperation processing described later in FIG. 19 or the BU processing described later in FIGS. 20 to 22 (step S1805). Next, the information processing apparatus 100 waits for a processing request indicating the processing person and the BU person in charge from the cooperation node 201 based on the cooperation start Tx (step S1806).

Then, the information processing apparatus 100 determines whether there is a processing request indicating the processing person and the BU person (step S1807). Here, if there is a processing request (step S1807: Yes), the information processing apparatus 100 returns to the process of step S1805. On the other hand, if there is no processing request (step S1807: No), the information processing apparatus 100 ends the overall processing.

(Cooperation processing procedure)
Next, an example of a cooperation processing procedure executed by the information processing apparatus 100 will be described using FIG. 19. The cooperative processing is realized by, for example, the CPU 301 shown in FIG. 3, a storage area such as the memory 302 or the recording medium 305, and the network I/F 303.

FIG. 19 is a flowchart illustrating an example of a cooperation processing procedure. In FIG. 19, the information processing apparatus 100 uses the cooperation execution module 1111 to generate and execute Tx for the cooperation destination BC (step S1901).

Next, the information processing apparatus 100 uses the cooperation execution module 1111 to acquire the executed Tx from the cooperation destination BC (step S1902). Then, the information processing apparatus 100 uses the collaboration execution module 1111 to generate an execution completion Tx for the collaboration BC, and executes it in the collaboration BC (step S1903). The information processing device 100 ends the cooperation process.

(BU processing procedure)
Next, an example of a BU processing procedure executed by the information processing apparatus 100 will be described using FIGS. 20 to 22. The BU process is realized by, for example, the CPU 301 shown in FIG. 3, a storage area such as the memory 302 and the recording medium 305, and the network I/F 303.

20 to 22 are flowcharts showing an example of a BU processing procedure. In FIG. 20, the information processing apparatus 100 stores the BU condition in the long-term buffer 1112 using the cooperation execution module 1111 (step S2001). Next, the information processing apparatus 100 uses the cooperation execution module 1111 to acquire the Tx to be BU from the block cache 1124 of the cooperation destination BC monitoring module 1122 (step S2002).

The information processing apparatus 100 then uses the cooperation execution module 1111 to determine whether or not a BU target Tx has been discovered (step S2003). Here, if it is found (step S2003: Yes), the information processing apparatus 100 moves to the process of step S2005. On the other hand, if it is not found (step S2003: No), the information processing apparatus 100 moves to the process of step S2004.

In step S2004, the information processing apparatus 100 causes the cooperation execution module 1111 to accumulate the notified Tx for BU in the Tx pool 1123 when the Tx for BU is notified from the cooperation destination BC monitoring module 1122 ( Step S2004). The information processing apparatus 100 then proceeds to the process of step S2006.

In step S2005, the information processing apparatus 100 causes the cooperation execution module 1111 to accumulate the discovered Tx for BU in the Tx pool 1123 (step S2005). The information processing apparatus 100 then proceeds to the process of step S2006.

In step S2006, the information processing apparatus 100 uses the cooperation execution module 1111 to search the short-term buffer 1132 for the execution completion Tx of the BU target (step S2006). The information processing apparatus 100 then proceeds to the process of step S2101 in FIG. 21.

In FIG. 21, the information processing apparatus 100 determines whether an execution completion Tx for the BU target has been discovered by the cooperation execution module 1111 (step S2101). Here, if it is found (step S2101: Yes), the information processing apparatus 100 moves to the process of step S2102. On the other hand, if it is not found (step S2101: No), the information processing apparatus 100 moves to the process of step S2103.

In step S2102, the information processing apparatus 100 uses the cooperation execution module 1111 to delete the BU condition, and if there is a BU target Tx in the Tx pool 1123, delete it (step S2102). The information processing device 100 then ends the BU process.

In step S2103, the information processing apparatus 100 receives a notification of execution completion Tx by the cooperation execution module 1111 via the short-term buffer 1132 (step S2103). Next, the information processing apparatus 100 determines whether the cooperation execution module 1111 has been notified of the execution completion Tx of the BU target (step S2104).

Here, if notified (step S2104: Yes), the information processing apparatus 100 moves to the process of step S2105. On the other hand, if the information processing apparatus 100 is not notified (step S2104: No), the information processing apparatus 100 moves to the process of step S2201 in FIG. 22.

In step S2105, the information processing apparatus 100 uses the cooperation execution module 1111 to delete the BU condition, delete the execution completion Tx accumulated in the long-term buffer 1112, and delete any Tx targeted for BU in the Tx pool 1123 ( Step S2105).

In FIG. 22, the information processing apparatus 100 uses the cooperation execution module 1111 to determine whether the execution completion Tx matches the BU condition in the long-term buffer 1112 (step S2201). Here, if they match (step S2201: Yes), the information processing apparatus 100 moves to the process of step S2202. On the other hand, if they do not match (step S2201: No), the information processing apparatus 100 moves to the process of step S2203.

In step S2202, the information processing apparatus 100 causes the cooperation execution module 1111 to accumulate the execution completion Tx in the long-term buffer 1112 (step S2202). The information processing apparatus 100 then proceeds to the process of step S2203.

In step S2203, the information processing apparatus 100 uses the cooperation execution module 1111 to count the execution completion Tx accumulated in the long-term buffer 1112 (step S2203). Next, the information processing apparatus 100 uses the cooperation execution module 1111 to determine whether the counted number of execution completion Tx is equal to or greater than a certain number (step S2204).

Here, if the number is equal to or greater than a certain value (step S2204: Yes), the information processing apparatus 100 moves to the process of step S2205. On the other hand, if the number is less than the certain number (step S2204: No), the information processing apparatus 100 ends the BU process.

In step S2205, the information processing apparatus 100 uses the cooperation execution module 1111 to delete the BU condition, delete the execution completed Tx accumulated in the long-term buffer 1112, and search the Tx pool 1123 for Tx to be BU (step S2205 ).

Next, in the information processing apparatus 100, the cooperation execution module 1111 determines whether a BU target Tx has been discovered (step S2206). Here, if it is found (step S2206: Yes), the information processing apparatus 100 moves to the process of step S2207. On the other hand, if it is not found (step S2206: No), the information processing apparatus 100 moves to the process of step S2208.

In step S2207, the information processing apparatus 100 uses the cooperation execution module 1111 to execute the execution completion Tx for the BU target on the cooperation BC (step S2207). The information processing device 100 then ends the BU process.

In step S2208, the information processing apparatus 100 uses the cooperation execution module 1111 to execute the cooperation processing shown in FIG. 19 (step S2208). The information processing device 100 then ends the BU process.

As described above, according to the information processing apparatus 100, it is possible to acquire a block managed by the BC network in which the execution results of the processes assigned to each control device by the control device are recorded. According to the information processing device 100, the state of at least one of the plurality of control devices can be determined based on the execution results included in the acquired block. Thereby, the information processing device 100 can appropriately determine whether to BU the process assigned to any of the control devices.

According to the information processing device 100, it is possible to determine the state of any one of the control devices corresponding to the own device, which is a standby control device. Thereby, the information processing device 100 can appropriately determine whether to BU the process assigned to any of the control devices corresponding to the information processing device 100.

According to the information processing device 100, any one of the control devices can be specified based on information that makes it possible to specify any of the control devices corresponding to the own device, which is a standby control device. According to the information processing apparatus 100, the state of any of the identified control devices can be determined based on the execution results included in the acquired block. Thereby, the information processing device 100 can appropriately identify any control device corresponding to the information processing device 100.

According to the information processing device 100, it is possible to operate as a control device included in a plurality of control devices. Thereby, the information processing device 100 can operate as an active system and a standby system.

According to the information processing device 100, a process assigned to another control device satisfies the conditions for determining that the process is the same type of process as the process assigned to one of the control devices, based on the execution results included in the acquired block. The number of can be calculated. According to the information processing device 100, if the calculated number is greater than or equal to a predetermined number, the state of one of the control devices can be determined to be abnormal. Thereby, the information processing device 100 can improve the accuracy of determining the state of any of the control devices.

According to the information processing device 100, a process having the same parameters as a process assigned to any one of the control devices can be determined to be the same type of process as the process assigned to any one of the control devices. Thereby, the information processing device 100 can improve the accuracy of determining the state of one of the control devices as abnormal.

According to the information processing device 100, a process that is to be linked with the same BC network as a process assigned to any one of the control devices is determined to be the same type of process as the process assigned to any one of the control devices. I can do it. Thereby, the information processing device 100 can improve the accuracy of determining the state of one of the control devices as abnormal.

According to the information processing device 100, when it is determined that the state of any one of the control devices is abnormal, the information processing device 100 executes the process assigned to any of the control devices, and the BC network records the execution results of the process. It can be recorded in managed blocks. Thereby, the information processing apparatus 100 can perform BU processing.

The information processing apparatus 100 can be applied to a situation where there are a plurality of control apparatuses that are assigned respective processes of a series of processes according to a first preset order. Thereby, the information processing device 100 can be applied to a situation where a plurality of control devices whose loads are distributed exist.

The information processing device 100 can be applied to a situation where standby control devices for each process in a series of processes are set according to a preset second order. Thereby, the information processing device 100 can be applied to a situation where a plurality of control devices whose loads are distributed exist.

Note that the control method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a PC or a workstation. The control program described in this embodiment is recorded on a computer-readable recording medium, and executed by being read from the recording medium by the computer. The recording medium includes a hard disk, a flexible disk, a CD (Compact Disc)-ROM, an MO (Magneto Optical disc), a DVD (Digital Versatile Disc), and the like. Furthermore, the control program described in this embodiment may be distributed via a network such as the Internet.

Regarding the embodiments described above, the following additional notes are further disclosed.

(Additional Note 1) The blockchain network includes nodes corresponding to each of a plurality of control devices, and records execution results of processes assigned to each of the control devices by the control device. Get the block managed by
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A control method characterized in that processing is executed by a computer.

(Additional Note 2) Each of the control devices is an operating system control device,
The computer is a standby control device corresponding to any one of the plurality of control devices,
The determining process is as follows:
The control method according to appendix 1, characterized in that the state of any of the control devices corresponding to the computer, which is a standby control device, is determined.

(Additional note 3) The above-mentioned determining process is
Identifying any of the control devices based on information that makes it possible to identify any of the control devices corresponding to the computer that is a standby control device;
The control method according to appendix 2, characterized in that the state of any of the identified control devices is determined based on the execution results included in the acquired block.

(Supplementary Note 4) The control method according to any one of Supplementary Notes 1 to 3, wherein the computer is a control device included in the plurality of control devices.

(Supplementary Note 5) The respective control devices according to any one of Supplementary Notes 1 to 4 are assigned processing for one of the plurality of blockchain networks to be cooperated with. Control method.

(Additional note 6) The process for determining the
Based on the execution results included in the obtained block, a predetermined number of processes assigned to other control devices that satisfy the conditions for determining that the processes are the same type as the processes assigned to any of the control devices is determined. 6. The control method according to any one of appendices 1 to 5, characterized in that, if the number of control devices is greater than or equal to the number of control devices, the state of one of the control devices is determined to be abnormal.

(Supplementary note 7) The control method according to supplementary note 6, wherein the condition indicates that a process having the same parameters as the process is determined to be the same type of process as the process.

(Supplementary note 8) The condition as described in supplementary note 6 or 7, wherein the condition indicates that a process that is to be linked with the same blockchain network as the process is determined to be the same type of process as the process. Control method.

(Additional note 9) If the state of any of the control devices is determined to be abnormal, the computer executes the process assigned to any of the control devices, and the blockchain network records the execution results of the process. Record in managed block,
9. The control method according to any one of appendices 1 to 8, characterized in that the processing is executed by the computer.

(Additional Note 10) The node is
When a request for a series of processes is received, each process in the series of processes is assigned to the plurality of control apparatuses according to a preset first order of allocating processes to the plurality of control apparatuses. The control method according to any one of Supplementary Notes 1 to 9 characterized by:

(Additional Note 11) The node is
When a request for a series of processes is received according to a preset second order of setting standby control devices, control of a standby system regarding each process of the series of processes among the plurality of control devices is performed. 11. The control method according to any one of appendices 1 to 10, comprising setting the device.

(Additional Note 12) The blockchain network includes nodes corresponding to each of a plurality of control devices, and records the execution results of processes assigned to each of the control devices by the control device. Get the block managed by
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A control program that causes a computer to perform processing.

(Additional Note 13) The blockchain network includes nodes corresponding to each of a plurality of control devices, and records the execution results of processes assigned to each of the control devices by the control device. Get the block managed by
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
An information processing device comprising a control section.

(Additional Note 14) A system including a blockchain network including nodes corresponding to each of a plurality of control devices, and a standby control device,
The blockchain network is
managing blocks in which records of execution results of processes assigned to each of the control devices by the control devices are recorded;
The standby control device is
obtaining the block from the blockchain network;
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A system characterized by:

100 Information processing device 101 Control device 110 BC network 111 Node 120 BC
121 Block 200 BC linkage system 201 Linkage node 202 Linkage destination node 210 Network 220 Linkage BC network 230 Linkage destination BC network 300,500 Bus 301,501 CPU
302,502 Memory 303,503 Network I/F
304,504 Recording medium I/F
305,505 Recording medium 400 BU judgment information management table 600 Information management table in charge 700 First storage section 701 First acquisition section 702 Judgment section 703 Transaction section 704 First output section 710 Second storage section 711 Second acquisition section 712 Allocation section 713 Request unit 714 Second output unit 801, 1112 Long-term buffer 1100 Client application 1111 Cooperation execution module 1120 Tx/block communication unit (cooperation destination BC)
1121 Cooperation destination BCTx execution module 1122 Cooperation destination BC monitoring module 1123 Tx pool 1124 Block cache 1130 Tx/block communication unit (BC for cooperation)
1131 BCTx execution module for cooperation 1132 Short-term buffer 1140 Block creation/distribution unit 1150 Tx/block communication unit (Peer)
1151 Tx execution/reference unit 1152 Storage area 1153 BC for cooperation

Claims (10)

A block managed by a blockchain network including nodes corresponding to each of a plurality of control devices, in which a track record of execution by the control device of a process assigned to each of the control devices is recorded. get
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A control method characterized in that processing is executed by a computer. Each of the control devices is an active control device,
The computer is a standby control device corresponding to any one of the plurality of control devices,
The determining process is as follows:
2. The control method according to claim 1, further comprising determining the state of one of the control devices corresponding to the computer, which is a standby control device. The determining process is as follows:
Identifying any of the control devices based on information that makes it possible to identify any of the control devices corresponding to the computer that is a standby control device;
3. The control method according to claim 2, further comprising determining the state of any of the identified control devices based on the execution results included in the acquired block. 4. The control method according to claim 1, wherein the computer is a control device included in the plurality of control devices. 5. The control method according to claim 1, wherein each of the control devices is assigned processing for one of a plurality of blockchain networks to be cooperated. The determining process is as follows:
Based on the execution results included in the obtained block, a predetermined number of processes assigned to other control devices that satisfy the conditions for determining that the processes are the same type as the processes assigned to any of the control devices is determined. 6. The control method according to claim 1, further comprising determining that the state of one of the control devices is abnormal if the number of control devices is greater than or equal to the number of control devices. If the state of any of the control devices is determined to be abnormal, the computer executes the process assigned to any of the control devices, and the execution results of the process are stored in a block managed by the blockchain network. Record,
7. The control method according to claim 1, wherein the processing is executed by the computer. A block managed by a blockchain network including nodes corresponding to each of a plurality of control devices, in which a track record of execution by the control device of a process assigned to each of the control devices is recorded. get
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A control program that causes a computer to perform processing. A block managed by a blockchain network including nodes corresponding to each of a plurality of control devices, in which a track record of execution by the control device of a process assigned to each of the control devices is recorded. get
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
An information processing device comprising a control section. A system including a blockchain network including nodes corresponding to each of a plurality of control devices, and a standby control device,
The blockchain network is
managing blocks in which records of execution results of processes assigned to each of the control devices by the control devices are recorded;
The standby control device is
obtaining the block from the blockchain network;
determining the state of at least one of the plurality of control devices based on the execution record included in the acquired block;
A system characterized by: