Information distribution processing control method, computer system, and computer

Abstract

To identify a cause of a failure of an information distribution process and provide information useful for an operator to determine whether to continue or abort the information distribution process.SOLUTION: A computer system is connected to a plurality of edge devices, monitors, after the start of an information distribution process for the plurality of edge devices, the state of each of the plurality of edge devices, executes a process for identifying an edge device for which the information distribution process has failed and identifying the cause of the failure on the basis of the result of monitoring of the state of each of the plurality of edge devices, and presents details of an operation related to abortion of the information distribution process on the basis of the result of the process.SELECTED DRAWING: Figure 6A

Description

[Technical field]

[0001] The present invention relates to a method, system, and apparatus for controlling the distribution of information to edge devices. [Background technology]

[0002] In recent years, with the advancement of digitalization of edge devices such as factory equipment, railroad cars, and automobiles, information such as software, information content, applications, and functions are distributed / deployed to edge devices via a network. In the following description, the distribution / deployment of information to edge devices via a network is referred to as information distribution.

[0003] As a technique for dealing with failures in information distribution, the technique described in Patent Document 1 is known. Patent Document 1 discloses a firmware update system in which "firmware update processing is executed at different times for multiple groups that divide multiple IoT devices. If the firmware update processing fails for any group, the execution of the firmware update processing for the remaining groups whose firmware has not been updated is restricted." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-154634 A Summary of the Invention [Problem to be solved by the invention]

[0005] By performing a series of processes for information distribution, i.e., a distribution sequence, on multiple edge devices at once, it becomes possible to distribute information to a large number of edge devices while reducing the number of steps required by the worker. For example, the worker can perform a distribution sequence start operation for multiple edge devices at once. Also, for example, when the worker's approval is required for installing software on an edge device, the worker can perform the approval operation for multiple edge devices at once.

[0006] However, in the above method, if there is no notification from the edge device that the preparation for software installation is complete, approval cannot be performed and the distribution sequence fails. The distribution sequence also fails if there is no notification from the edge device that the software installation is complete. There are various causes for the failure of the distribution sequence. For example, there are a limited communication bandwidth, communication disconnection, failure to execute commands due to an increased load on the edge device, and failure to install due to a software malfunction.

[0007] Information regarding the cause of failure of the distribution sequence is useful to the worker, who can determine whether to continue or stop the distribution sequence depending on the cause of the failure. Patent Document 1 does not specify the cause of the failure.

[0008] An object of the present invention is to provide a method and system for identifying the cause of failure of a distribution sequence and providing an operator with information useful for determining whether to continue or stop the distribution sequence. [Means for solving the problem]

[0009] A representative example of the invention disclosed in the present application is as follows: That is, a method for controlling information distribution processing for a plurality of edge devices, executed by a computer system connected to the edge devices, the computer system including a computer having a processor, a storage device connected to the processor, and a network interface connected to the processor, the method for controlling information distribution processing includes a first step in which the processor monitors the status of each of the edge devices after starting the information distribution processing for the edge devices, a second step in which the processor executes a first process for identifying the edge device for which the information distribution processing has failed and the cause of the failure based on a result of monitoring the status of each of the edge devices, and a third step in which the processor presents an operation content for stopping the information distribution processing based on a result of the first process. The failure cause includes a first failure cause which is a cause specific to the edge device, and a second failure cause which is a cause common to the plurality of edge devices. Effect of the Invention

[0010] According to the present invention, it is possible to identify the cause of failure of a distribution sequence and provide the worker with information useful for determining whether to continue or stop the distribution sequence. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a system configuration according to a first embodiment. [Diagram 2] FIG. 2 illustrates an example of the configuration of a distribution control device according to a first embodiment. [Diagram 3] FIG. 2 illustrates an example of the configuration of an edge device according to the first embodiment. [Figure 4] FIG. 13 is a diagram illustrating an example of a data structure of metric correct value management information according to the first embodiment. [Diagram 5] FIG. 4 illustrates an example of a data structure of edge device management information according to the first embodiment. [Figure 6A] FIG. 2 is a sequence diagram illustrating a process flow in the system according to the first embodiment. [Figure 6B]FIG. 2 is a sequence diagram illustrating a process flow in the system according to the first embodiment. [Figure 7] 11 is a flowchart illustrating an example of a stop determination process executed by the distribution control device according to the first embodiment. [Figure 8] 11 is a flowchart illustrating an example of a stop determination process executed by the distribution control device according to the first embodiment. [Figure 9] 11 is a flowchart illustrating an example of a stop determination process executed by the distribution control device according to the first embodiment. [Figure 10A] FIG. 4 is a diagram illustrating an example of a screen displayed on a worker terminal according to the first embodiment. [Figure 10B] FIG. 4 is a diagram illustrating an example of a screen displayed on a worker terminal according to the first embodiment. [Figure 11] 11 is a flowchart illustrating an example of a metric confirmation process executed by the distribution control device according to the first embodiment. [Figure 12] FIG. 11 is a sequence diagram illustrating a process flow in the system according to the second embodiment. [Figure 13] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a second embodiment. [Figure 14] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a second embodiment. [Figure 15] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a second embodiment. [Figure 16] FIG. 11 is a diagram illustrating an example of a screen displayed on a worker terminal according to the second embodiment. [Figure 17] FIG. 11 is a sequence diagram illustrating a process flow in the system according to the third embodiment. [Figure 18A] 13 is a flowchart illustrating an example of a metric confirmation process executed by a distribution control device according to a third embodiment. [Figure 18B] 13 is a flowchart illustrating an example of a metric confirmation process executed by a distribution control device according to a third embodiment. [Figure 19] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a third embodiment. [Figure 20] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a third embodiment. [Figure 21A] FIG. 13 is a sequence diagram illustrating a process flow in the system according to the fourth embodiment. [Figure 21B] FIG. 13 is a sequence diagram illustrating a process flow in the system according to the fourth embodiment. [Figure 22] 13 is a flowchart illustrating an example of a stop determination process executed by a distribution control device according to a fourth embodiment. [Figure 23A] FIG. 11 is a sequence diagram illustrating a process flow in a system according to a modified example. [Figure 23B] FIG. 11 is a sequence diagram illustrating a process flow in a system according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, the present invention should not be interpreted as being limited to the description of the embodiment shown below. It will be easily understood by those skilled in the art that the specific configuration can be changed without departing from the concept or purpose of the present invention.

[0013] In the configurations of the invention described below, the same or similar configurations or functions are given the same reference numerals, and duplicated explanations are omitted.

[0014] In this specification, the terms "first," "second," "third," and the like are used to distinguish components and do not necessarily limit the number or order.

[0015] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings, etc. may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not limited to the position, size, shape, range, etc. disclosed in the drawings, etc. EXAMPLES

[0016] FIG. 1 is a diagram illustrating an example of a system configuration according to a first embodiment.

[0017] The system is composed of a distribution control device 101, an edge device 102, a distribution server 103, and an operator terminal 104. The distribution control device 101, the edge device 102, the distribution server 103, and the operator terminal 104 are connected via a network 105. The network 105 is a WAN (Wide Area Network) and a LAN (Local Area Network), and the connection method may be either wired or wireless.

[0018] The edge device 102 is a device that receives information distribution, such as factory equipment, railway cars, and automobiles. The distribution control device 101 is a computer that controls information distribution. The distribution server 103 is a computer that manages software and information contents to be distributed to the edge device 102 in information distribution. The worker terminal 104 is a terminal operated by a worker who distributes information. The worker operates the distribution control device 101 using the worker terminal 104.

[0019] The functions of the delivery server 103 and the delivery control device 101 may be realized using a computer system consisting of multiple computers. Also, the functions of the delivery server 103 and the delivery control device 101 may be integrated into one of the computers.

[0020] FIG. 2 is a diagram illustrating an example of the configuration of the distribution control device 101 according to the first embodiment.

[0021] The distribution control device 101 has a processor 201, a network interface 202, a main storage device 203, and a secondary storage device 204. The hardware elements are connected to each other via an internal bus.

[0022] The functions of the distribution control device 101 are realized by the processor 201 executing a program stored in the main memory device 203. In the following explanation, when a process is explained with the distribution control device 101 as the subject, it indicates that the processor 201 is executing the program.

[0023] The network interface 202 communicates with external devices over a network.

[0024] The main storage device 203 is a storage device such as a memory, and stores the programs executed by the processor 201 and information used by the programs. The main storage device 203 is also used as a work area.

[0025] The secondary storage device 204 is a storage device such as a hard disk drive (HDD) or a solid state drive (SSD), and stores data permanently. The programs and information stored in the main storage device 203 may be stored in the secondary storage device 204. In this case, the processor 201 reads the programs and information from the secondary storage device 204 and loads them into the main storage device 203.

[0026] The main storage device 203 stores an abort determination program 211, a metric confirmation program 212, metric correct value management information 221, and edge device management information 222. The data structures of the metric correct value management information 221 and the edge device management information 222, and the processes realized by the programs will be described later.

[0027] The hardware configurations of the distribution server 103 and the worker terminal 104 are the same as those of the distribution control device 101, and therefore a description thereof will be omitted.

[0028] FIG. 3 is a diagram illustrating an example of the configuration of the edge device 102 according to the first embodiment.

[0029] The edge device 102 includes a processor 301, a network interface 302, a main memory device 303, and a secondary memory device 304. The hardware elements are connected to each other via an internal bus. The edge device 102 may include hardware elements (not shown), such as a drive device.

[0030] The processor 301 , the network interface 302 , the primary storage device 303 , and the secondary storage device 304 are the same hardware as the processor 201 , the network interface 202 , the primary storage device 203 , and the secondary storage device 204 .

[0031] The functions of the edge device 102 are realized by the processor 301 executing a program stored in the main memory device 303. In the following explanation, when a process is explained with the edge device 102 as the subject, it indicates that the processor 301 is executing the program.

[0032] The main memory 303 stores a command execution program 311 and a metric transmission program 312 .

[0033] FIG. 4 is a diagram illustrating an example of a data structure of the metric correct value management information 221 according to the first embodiment.

[0034] The metric correct value management information 221 is information in a table format, and stores entries including a metric type 401 and a correct value 402. One entry corresponds to one metric type. Note that the fields included in the entry are not limited to those described above.

[0035] The metric type 401 is a field for storing the type of metric indicating the progress of information distribution. The metric correct value management information 221 shown in Fig. 4 stores entries of two metric types: the acquisition rate of the information content and the version of the information content.

[0036] The correct answer value 402 is a field for storing the correct answer value of the metric corresponding to the metric type. 100% is stored in the correct answer value 402 of the entry corresponding to the acquisition rate of the information content, and 2.0 is stored in the correct answer value 402 of the entry corresponding to the version of the information content.

[0037] FIG. 5 is a diagram illustrating an example of a data structure of the edge device management information 222 according to the first embodiment.

[0038] The edge device management information 222 is information in a table format, and stores entries including an edge device ID 501, a delivery sequence execution result 502, a failure indicator 503, and a group ID 504. One entry corresponds to one edge device 102. Note that the fields included in the entry are not limited to those described above.

[0039] The edge device ID 501 is a field for storing identification information of the edge device 102 .

[0040] Delivery sequence execution result 502 is a field that stores the execution result of the delivery sequence for edge device 102. Delivery sequence execution result 502 stores either "Success" indicating that the delivery sequence was successful, or "Failure" indicating that the delivery sequence was unsuccessful.

[0041] The failure index 503 is a field for storing information about the index used in the judgment. For example, in the case of an index related to communication, the failure index 503 stores "connection state," and in the case of an index related to load, the failure index 503 stores "load."

[0042] The group ID 504 is a field for storing identification information of a group, which is an execution unit of a delivery sequence. When a worker sets a group in advance, the group ID 504 stores the identification information of the group.

[0043] Instead of the group identification information, the firmware version, the type of edge device, etc. may be stored. In this case, a group is formed whose elements are edge devices 102 with the same firmware or type.

[0044] 6A and 6B are sequence diagrams illustrating a process flow in the system according to the first embodiment.

[0045] The worker transmits a delivery sequence registration request to the delivery control device 101 using the worker terminal 104 (step S601). For example, by transmitting the delivery sequence registration request, the worker sets the phase group constituting the delivery sequence, the phase requiring the worker's approval, the metrics transmitted by the edge device 102, the commands executed by the edge device 102 in each phase, the correct answer values ​​of the metrics, and the software to be installed, information contents, and necessary materials such as application containers.

[0046] The worker uses the worker terminal 104 to transmit a distribution sequence start instruction to the distribution control device 101 (step S602).

[0047] When the delivery control device 101 receives a delivery sequence start instruction, it starts the delivery sequence. The processes from step S603 to step S624 are the delivery sequence. First, the delivery control device 101 distributes a file to the edge device 102, and also transmits a status update request (step S603). The delivery control device 101 also starts a stop determination process (step S604). The edge device 102 is notified, via the file, of the phases that make up the delivery sequence, the metrics to be sent, the commands that the edge device 102 will execute in each phase, the necessary materials, and the like.

[0048] In response to the file distribution and status update request, the edge device 102 transmits a status update response to the distribution control device 101 (step S605).

[0049] In this embodiment, it is assumed that the distribution control device 101 was able to receive a status update response from edge device (A) 102, but was unable to receive a status update response from edge device (B) 102. Possible causes for the inability to receive a status update response include a missing file / status update request, a missing status update response, etc.

[0050] In the abort determination process, the delivery control device 101 determines whether the delivery sequence has been successful or not based on the reception state of the status update response, and also identifies the cause of failure. Here, the abort determination process will be described in detail. FIGS. 7, 8, and 9 are flowcharts illustrating an example of the abort determination process executed by the delivery control device 101 of the first embodiment. The abort determination process is performed by the processor 201 that executes the abort determination program 211.

[0051] First, the abort determination process shown in Fig. 7 will be described. The abort determination process shown in Fig. 7 is executed for each edge device 102. In the abort determination process shown in Fig. 7, the success or failure of the delivery sequence is determined based on the presence or absence of a status update response from the edge device 102, and the cause of failure is identified based on the evaluation indexes (connection status index and load index) acquired from the edge device 102.

[0052] The distribution control device 101 determines whether or not a status update response has been received from the edge device 102 within a predetermined period of time (step S701).

[0053] If a status update response is received from the edge device 102 within the predetermined period (YES in step S701), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0054] If a status update response is not received from the edge device 102 within a predetermined period of time (NO in step S701), the delivery control device 101 determines that the delivery sequence has failed and identifies the cause of the failure. First, the delivery control device 101 determines whether the connection status of the edge device 102 is good (step S702). Specifically, the following process is executed.

[0055] (S702-1) The distribution control device 101 calculates an index for evaluating the connection state of the edge device 102 (connection state index).

[0056] For example, when the edge device 102 periodically transmits a Keep Alive message to the distribution control device 101, the distribution control device 101 calculates whether or not the message has been received as a connection status index. For example, when the edge device 102 measures an index indicating communication quality, the edge device 102 calculates the latest index or an average value of the index as the connection status index.

[0057] (S702-2) The distribution control device 101 determines the connection state of the edge device 102 based on the connection state indicator.

[0058] For example, if the latest Keep Alive message has been received, the distribution control device 101 determines that the connection state of the edge device 102 is good. For example, if the latest communication quality index is greater than a threshold, the distribution control device 101 determines that the connection state of the edge device 102 is good.

[0059] This concludes the description of the process in step S702.

[0060] If the connection status of the edge device 102 is not good (NO in step S702), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S703). After that, the delivery control device 101 ends the cancellation determination process.

[0061] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0062] If the connection state of the edge device 102 is good (YES in step S702), the distribution control device 101 determines whether the load of the edge device 102 is high (step S704).

[0063] Specifically, the delivery control device 101 calculates an index (load index) for evaluating the load of the edge device 102, and judges whether the load of the edge device 102 is high or not based on the load index. For example, the delivery control device 101 periodically acquires the usage rate of the processor 301 from the edge device 102, and calculates the latest usage rate or the average value of the usage rates as the load index. If the usage rate of the processor 301 is greater than a threshold value, the delivery control device 101 judges that the load of the edge device 102 is high.

[0064] If the load on the edge device 102 is not high (step S704: NO), the delivery control device 101 registers data associating the cause "other" with the identification information of the edge device 102 in the cancellation target list (step S705). After that, the delivery control device 101 ends the cancellation determination process.

[0065] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0066] If the load of the edge device 102 is high (YES in step S704), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S706). After that, the delivery control device 101 ends the cancellation determination process.

[0067] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0068] If the connection state of edge device 102 where the delivery sequence has failed is poor or the load is high, the delivery sequence failure is recorded in the abort target list as having occurred due to a factor specific to edge device 102. Also, if the connection state is good and the load is low, the delivery sequence failure is registered in the abort target list as having occurred due to a factor other than a factor specific to edge device 102.

[0069] After the abort determination process is completed for all edge devices 102, the distribution control device 101 determines a recommended operation to be presented to the operator based on the abort target list. For example, the following recommended operations are considered.

[0070] (1) When there is an edge device 102 whose distribution sequence has failed due to a factor specific to the edge device 102, the distribution control device 101 proposes to the worker to stop the distribution sequence of the edge device 102. In this case, the distribution sequences of the other edge devices 102 continue.

[0071] (2) When there is an edge device 102 in which the delivery sequence has failed due to a factor other than a factor specific to the edge device 102, there is a possibility that the delivery sequence failure will also occur in other edge devices 102. In this case, the delivery control device 101 suggests to the worker to stop the delivery sequence of the group or the entire group.

[0072] (3) When the distribution sequence has failed due to a mixture of factors including edge devices 102, the distribution control device 101 determines the recommended operation based on the ratio of edge devices 102 belonging to each factor. For example, when the ratio of edge devices 102 belonging to the factor "other" is high, the distribution control device 101 suggests to the operator to cancel the group or the entire distribution sequence.

[0073] In this way, by proposing recommended operations along with the failure causes of the distribution sequence, it is possible to realize efficient control of the distribution sequence, thereby reducing the number of steps and the work time required by workers to control the distribution sequence.

[0074] Next, the abort determination process shown in Fig. 8 will be described. The abort determination process shown in Fig. 8 is executed for each edge device 102. In the abort determination process shown in Fig. 8, the success or failure of the delivery sequence is determined based on the presence or absence of a status update response from the edge device 102, and the cause of failure is identified based on evaluation indexes acquired from multiple edge devices 102.

[0075] The distribution control device 101 calculates a representative value of the load index by using a load index such as a usage rate of the processor 301 acquired from each edge device 102 (step S801).

[0076] A representative value of a load index may be the mean, median, or x-percentile (eg, x is 90) of the load index.

[0077] The distribution control device 101 uses the connection status index of each edge device 102 to calculate a representative value of the connection status index (step S802).

[0078] For example, the distribution control device 101 calculates a representative value of a connection status index using a connection status index such as the number of times Keep Alive messages transmitted from each edge device 102 are received within a certain period of time or communication quality. The representative value of the connection status index is the average value, median value, or x-percentile value (x-percentile) (for example, x is 90) of the connection status index.

[0079] The distribution control device 101 determines whether or not a status update response has been received from the edge device 102 within a predetermined period (step S803). The process of step S803 is the same as the process of step S701.

[0080] If a status update response is received from the edge device 102 within the predetermined period (YES in step S803), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0081] If a status update response is not received from the edge device 102 within a predetermined period of time (NO at step S803), the distribution control device 101 determines whether the connection status of the edge device 102 is good (step S804). Specifically, the following process is executed.

[0082] (S804-1) The distribution control device 101 calculates a connection status indicator of the edge device 102.

[0083] For example, when the edge device 102 periodically transmits a Keep Alive message to the distribution control device 101, the distribution control device 101 calculates, as the connection status index, the number of times the message is received within a certain period of time, etc. For example, when the edge device 102 measures an index indicating communication quality, the edge device 102 calculates, as the connection status index, the latest index or the average value of the index, etc.

[0084] (S804-2) The distribution control device 101 determines the connection state of the edge device 102 based on the result of comparing the connection state indicator with the representative value of the connection state indicator.

[0085] For example, if the number of times Keep Alive messages are received within a certain period of time is equal to or greater than the representative value of the connection status index, the distribution control device 101 determines that the connection status of the edge device 102 is good. For example, if the connection status index is equal to or greater than the representative value of the connection status index, the distribution control device 101 determines that the connection status of the edge device 102 is good.

[0086] If the connection status of the edge device 102 is not good (NO in step S804), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S805). After that, the delivery control device 101 ends the cancellation determination process.

[0087] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0088] If the connection state of the edge device 102 is good (YES in step S804), the distribution control device 101 determines whether the load of the edge device 102 is high (step S806).

[0089] Specifically, the distribution control device 101 calculates a load index of the edge device 102, and determines whether the load of the edge device 102 is high or not based on a comparison result between the load index and a representative value of the load index.

[0090] For example, the delivery control device 101 periodically acquires the usage rate of the processor 301 from the edge device 102 and calculates the latest usage rate or the average usage rate, etc., as a load index. If the usage rate of the processor 301 is equal to or greater than the representative value of the load index, the delivery control device 101 determines that the load of the edge device 102 is high.

[0091] If the load on the edge device 102 is not high (step S806: NO), the delivery control device 101 registers data associating the cause "other" with the identification information of the edge device 102 in the cancellation target list (step S807). After that, the delivery control device 101 ends the cancellation determination process.

[0092] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0093] If the load of the edge device 102 is high (YES in step S806), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S808). After that, the delivery control device 101 ends the cancellation determination process.

[0094] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0095] After the abort determination process is completed for all edge devices 102, the distribution control device 101 determines a recommended operation to be presented to the operator based on the abort target list. The method of determining the recommended operation is the same as the method described with reference to FIG.

[0096] The edge device 102 can be relatively evaluated by determining the connection state and load of the edge device 102 based on the comparison result between the evaluation index of the edge device 102 and the representative value of the evaluation index. For example, an edge device 102 with an extremely poor connection state or an extremely high load compared to other edge devices 102 is recorded as a device-specific factor.

[0097] Next, a description will be given of the abort determination process shown in Fig. 9. The abort determination process shown in Fig. 9 is executed once for all edge devices 102. In the abort determination process shown in Fig. 9, a cause of failure is identified based on a comparison result between a representative value of the evaluation index acquired from each edge device 102 and a threshold value.

[0098] The distribution control device 101 calculates a representative value of the load index (step S901), and also calculates a representative value of the connection state index (step S902). The processes in steps S901 and S902 are the same as the processes in steps S801 and S802.

[0099] The distribution control device 101 determines whether there is an edge device 102 from which it has not received a status update response within a predetermined period of time (step S903). That is, it is determined whether there is an edge device 102 from which the distribution sequence has failed.

[0100] If there is no edge device 102 from which a status update response has not been received within the predetermined period (NO in step S903), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entries corresponding to each edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0101] If there is an edge device 102 from which a status update response has not been received within a predetermined period of time (YES in step S903), the distribution control device 101 determines whether or not the representative value of the connection status index is equal to or greater than a threshold value (step S904).

[0102] If the representative value of the connection status index is smaller than the threshold value (step S904: NO), the distribution control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the cancellation target list for each edge device 102 in which the distribution sequence has failed (step S905). After that, the distribution control device 101 proceeds to step S909.

[0103] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0104] If the representative value of the connection status index is equal to or greater than the threshold value (YES in step S904), the distribution control device 101 determines whether the representative value of the load index is equal to or greater than the threshold value (step S906).

[0105] If the representative value of the load index is equal to or greater than the threshold value (YES in step S906), the delivery control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the abort target list for each edge device 102 in which the delivery sequence has failed (step S907). After that, the delivery control device 101 proceeds to step S909.

[0106] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0107] If the representative value of the load index is smaller than the threshold value (step S906: NO), the distribution control device 101 registers data in which the cause "other" is associated with the identification information of the edge device 102 in the cancellation target list for each edge device 102 in which the distribution sequence has failed (step S908). After that, the distribution control device 101 proceeds to step S909.

[0108] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0109] In step S909, the delivery control device 101 determines a recommended operation to be presented to the worker based on the cancellation target list (step S909). After that, the delivery control device 101 ends the cancellation determination process. For example, the following recommended operations are considered.

[0110] (1) When there is an edge device 102 whose cause is "common", the distribution control device 101 proposes to the operator to stop the group or the entire distribution sequence.

[0111] (2) If there is an edge device 102 whose cause is "other", the distribution control device 101 proposes to the worker to stop the distribution sequence of that edge device 102. In this case, the distribution sequences of the other edge devices 102 continue.

[0112] (3) When the distribution sequence has failed due to a mixture of factors including edge devices 102, the distribution control device 101 determines the recommended operation based on the ratio of edge devices 102 belonging to each factor. For example, when the ratio of edge devices 102 belonging to the factor "other" is high, the distribution control device 101 suggests to the operator to cancel the group or the entire distribution sequence.

[0113] Based on the result of comparing the representative value of the evaluation index with the threshold value, the connection state and load of the edge device 102 are determined, thereby making it possible to evaluate the entire system. Furthermore, the abort determination process shown in Fig. 9 can reduce the amount of calculation compared to the process performed on an edge device 102 basis as shown in Figs. 7 and 8.

[0114] This concludes the description of the stop determination process. Returning to the description of FIG. 6A.

[0115] The distribution control device 101 transmits a result of the stop determination process to the operator terminal 104 (step S606). The result includes the edge device management information 222, a recommended operation, and a list of operations to be stopped.

[0116] The worker terminal 104 presents a screen based on the result of the stop determination process and accepts the worker's stop operation. Here, the screen presented to the worker will be described. Fig. 10A and Fig. 10B are diagrams showing an example of a screen displayed on the worker terminal 104 of the first embodiment.

[0117] The screen 1000 includes display fields 1001 , 1002 , 1003 and a selection field 1004 .

[0118] A display field 1001 is a field for displaying the execution results of the distribution sequence of each edge device 102. In the display field 1001, a table 1010 generated based on the edge device management information 222 is displayed.

[0119] The display field 1002 is a field for displaying the identified failure causes. The type and number of the identified failure causes are displayed in the display field 1002. The worker terminal 104 performs display in the display field 1002 based on the abort target list.

[0120] The display field 1003 is a field in which the recommended operation determined by the distribution control device 101 is displayed.

[0121] A selection field 1004 is a field for selecting an operation for the failed distribution sequence. Buttons for selecting an operation are displayed in the selection field 1004. The worker refers to the display fields 1001, 1002, and 1003, and instructs the distribution sequence to be stopped by pressing any of the buttons displayed in the selection field 1004.

[0122] 10A displays buttons for executing an operation to cancel the distribution sequence of the failed edge device 102, an operation to cancel the distribution sequences of all edge devices 102, and waiting. Waiting is an operation for executing the cancel determination process again after waiting for a certain period of time. Selection field 1004 in FIG. 10B further displays a button for executing an operation to cancel the distribution sequence of edge devices 102 belonging to a group that includes the failed edge device 102.

[0123] This concludes the explanation of the screen. Let us return to the explanation of FIG. 6A.

[0124] The worker performs a cancel operation using the worker terminal 104 (step S607). Specifically, the worker presses any of the buttons displayed in the selection field 1004. The worker terminal 104 transmits a cancel request corresponding to the cancel operation to the distribution control device 101 (step S608). The cancel request includes information about the pressed button.

[0125] The distribution control device 101 identifies the edge device 102 to be stopped in accordance with the stop request, and transmits a stop instruction to the identified edge device 102 (step S609).

[0126] When the termination of the distribution sequence of the failed edge device 102 is selected, the distribution control device 101 transmits an abort instruction only to the failed edge device 102. If aborting the distribution sequence of all edge devices 102 is selected, the distribution control device 101 transmits an abort instruction to all edge devices 102. If aborting the distribution sequence of edge devices 102 belonging to a group including the failed edge device 102 is selected, the distribution control device 101 refers to the edge device management information 222, identifies the group including the failed edge device 102, and transmits an abort instruction to the edge devices 102 belonging to that group. If waiting is selected, the distribution control device 101 executes the abort determination process again after a certain period of time has elapsed without transmitting an abort instruction.

[0127] By canceling the distribution sequence on a group basis, for example, if the distribution sequence is a firmware update, it is possible to avoid a situation in which the firmware versions of the edge devices 102 in the group are different.

[0128] It should be noted that if there is no edge device 102 in the cancellation target list, that is, if there is no edge device 102 in which the distribution sequence has failed, the processes from step S606 to step S609 are not executed.

[0129] Here, it is assumed that a request has been made to stop the distribution sequence of edge device (B) 102, which has failed in the distribution sequence. In this case, distribution control device 101 transmits a stop instruction to edge device (B) 102.

[0130] The edge device 102 continuing the distribution sequence executes the command in a predetermined phase (step S610), and transmits a command completion notification to the distribution control device 101 (step S611).

[0131] Specifically, the edge device 102 performs the steps of S603 In step S102, the distribution control device 102 executes a command contained in a file distributed from the distribution control device 101. The command to be executed is, for example, a command for realizing software decompression, acquisition of information content, and the like.

[0132] When the distribution control device 101 receives the command completion notification, it transmits an authentication request to the operator terminal 104 (step S612).

[0133] The worker performs an authentication operation using the worker terminal 104 (step S613), and the worker terminal 104 transmits an authentication response to the distribution control device 101 (step S614).

[0134] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S615).

[0135] The edge device 102 transmits a status update response to the distribution control device 101 (step S616), and also executes the command (step S617).

[0136] Specifically, the edge device 102 performs the steps of S603 In step 104, the distribution control device 102 executes a command contained in a file distributed from the distribution control device 101. The command to be executed is, for example, a command for implementing software installation and preparation for distribution of information content.

[0137] The edge device 102 transmits the metric to the distribution control device 101 (step S618).

[0138] For example, the edge device 102 transmits, as metrics, the presence or absence of an execution result file generated with the installation of software, the version of the installed software, the acquisition rate of information content, the version of the information content, and the like.

[0139] When the distribution control device 101 receives the metric, it executes a metric confirmation process (step S619).

[0140] Here, the metric confirmation process will be described. Fig. 11 is a flowchart illustrating an example of the metric confirmation process executed by the delivery control device 101 of the first embodiment. The metric confirmation process is performed by the processor 201 that executes the metric confirmation program 212. In addition, the metric confirmation process is executed when a metric is received from the edge device 102.

[0141] The distribution control device 101 refers to the metric correct value management information 221, acquires a correct value from an entry corresponding to the type of the received metric, and judges whether the received metric matches the correct value (step S1101).

[0142] If the received metric does not match the correct value (NO at step S1101), the distribution control device 101 transitions to a metric reception waiting state (step S1104), and ends the metric confirmation process.

[0143] If the received metric matches the correct value (YES in step S1101), the distribution control device 101 judges whether or not confirmation has been completed for the metrics of all edge devices 102 (step S1102). In other words, it is judged whether or not confirmation has been made that the metrics of all edge devices 102 match the correct value.

[0144] If the confirmation of the metrics of all edge devices 102 has not been completed (NO at step S1102), the distribution control device 101 transitions to a metric reception waiting state (step S1104) and ends the metric confirmation process.

[0145] When the confirmation of the metrics of all edge devices 102 is completed (YES in step S1102), the distribution control device 101 transmits an authentication request to the operator terminal 104 (steps S1103, S620), and ends the metric confirmation process.

[0146] This concludes the description of the metric confirmation process. Return to FIG. 6B.

[0147] The worker performs an authentication operation using the worker terminal 104 (step S621), and the worker terminal 104 transmits an authentication response to the distribution control device 101 (step S622).

[0148] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S623).

[0149] The edge device 102 transmits a status update response to the distribution control device 101 (step S624).

[0150] According to the first embodiment, the distribution control device 101 identifies the cause of failure for the edge device 102 that does not respond to a status update after file distribution, and proposes an operation to stop the distribution sequence according to the identified cause of failure. This allows efficient control of the stop of the distribution sequence, thereby reducing the man-hours and work time required for controlling the distribution sequence. EXAMPLES

[0151] In the second embodiment, the execution phase of the abort determination process is different from that in the first embodiment. The second embodiment will be described below, focusing on the differences from the first embodiment.

[0152] The system configuration of the second embodiment is the same as that of the first embodiment. The hardware configuration and the software configuration of the distribution control device 101 and the edge device 102 of the second embodiment are the same as those of the first embodiment. The data structures of the metric correct value management information 221 and the edge device management information 222 of the second embodiment are the same as those of the first embodiment.

[0153] FIG. 12 is a sequence diagram illustrating a process flow in the system according to the second embodiment.

[0154] The worker transmits a distribution sequence registration request to the distribution control device 101 using the worker terminal 104 (step S1201). Step S1201 is the same process as step S601.

[0155] The worker uses the worker terminal 104 to transmit a distribution sequence start instruction to the distribution control device 101 (step S1202). Step S1202 is the same as the process of step S602.

[0156] When the distribution control device 101 receives the distribution sequence start instruction, it distributes a file to the edge device 102, and also transmits a status update request (step S1203). The process of step S1203 is the same as the process of step S603.

[0157] In response to the file distribution and status update request, the edge device 102 transmits a status update response to the distribution control device 101 (step S1204). The process of step S1204 is the same as the process of step S604.

[0158] After receiving the status update response, the distribution control device 101 starts the stop determination process (step S1205).

[0159] The edge device 102 executes the command in a predetermined phase (step S1206), and transmits a command completion notification to the distribution control device 101 (step S1207). The processes in steps S1206 and S1207 are the same as the processes in steps S610 and S611.

[0160] In this embodiment, it is assumed that the distribution control device 101 was able to receive a command completion notification from the edge device (A) 102, but was unable to receive a command completion notification from the edge device (B) 102. Possible causes of the command completion notification not being received include failure to execute the command, a long command execution time, a missing command completion notification, etc.

[0161] Here, the details of the stop determination process will be described. Fig. 13, Fig. 14, and Fig. 15 are flowcharts illustrating an example of the stop determination process executed by the distribution control device 101 of the second embodiment. The stop determination process is executed by the processor 201 that executes the stop determination program 211.

[0162] First, the abort determination process shown in Fig. 13 will be described. The abort determination process shown in Fig. 13 is executed for each edge device 102. In the abort determination process shown in Fig. 13, the success or failure of the delivery sequence is determined based on the presence or absence of a command completion notification from the edge device 102, and the cause of failure is identified based on the evaluation index acquired from the edge device 102.

[0163] The distribution control device 101 determines whether or not a command completion notification has been received from the edge device 102 within a predetermined period of time (step S1301).

[0164] If a command completion notification is received from the edge device 102 within the predetermined period (YES in step S1301), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0165] A command from the edge device 102 within a predetermined period Completion notification If the distribution control device 101 has not received the notification (NO in step S1301), the distribution control device 101 determines that the distribution sequence has failed, and identifies the cause of the failure. First, the distribution control device 101 determines whether the connection status of the edge device 102 is good (step S1302). The process in step S1302 is the same as the process in step S702.

[0166] If the connection status of the edge device 102 is not good (NO in step S1302), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S1303). After that, the delivery control device 101 ends the cancellation determination process.

[0167] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0168] If the connection state of the edge device 102 is good (YES in step S1302), the distribution control device 101 judges whether the load of the edge device 102 is high (step S1304). The process of step S1304 is the same as the process of step S704.

[0169] If the load on the edge device 102 is not high (NO in step S1304), the delivery control device 101 registers data associating the cause "other" with the identification information of the edge device 102 in the cancellation target list (step S1305). After that, the delivery control device 101 ends the cancellation determination process.

[0170] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0171] If the load on the edge device 102 is high (YES in step S1304), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S1306). After that, the delivery control device 101 ends the cancellation determination process.

[0172] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0173] If the connection state of edge device 102 where the delivery sequence has failed is poor or the load is high, the delivery sequence failure is recorded in the abort target list as having occurred due to a factor specific to edge device 102. Also, if the connection state is good and the load is low, the delivery sequence failure is registered in the abort target list as having occurred due to a factor other than a factor specific to edge device 102.

[0174] After the abort determination process is completed for all edge devices 102, the distribution control device 101 determines a recommended operation to be presented to the operator based on the abort target list. Of the recommended operations, the method of determining an operation related to aborting a distribution sequence is the same as in the first embodiment. In the second embodiment, the content of an authentication operation is also determined. For example, an operation to authenticate only edge devices 102 that continue the distribution sequence, an operation to authenticate all or a group of edge devices 102, etc. are determined.

[0175] Next, the abort determination process shown in Fig. 14 will be described. The abort determination process shown in Fig. 14 is executed for each edge device 102. In the abort determination process shown in Fig. 14, the success or failure of the delivery sequence is determined based on the presence or absence of a command completion notification from the edge device 102, and the cause of failure is identified based on evaluation indexes acquired from the multiple edge devices 102.

[0176] The distribution control device 101 calculates a representative value of the load index (step S1401). The process of step S1401 is the same as the process of step S801.

[0177] The distribution control device 101 calculates a representative value of the connection state index (step S1402). The process of step S1402 is the same as the process of step S802.

[0178] The distribution control device 101 determines whether or not a command completion notification has been received from the edge device 102 within a predetermined period of time (step S1403). The process of step S1403 is the same as the process of step S1301.

[0179] If a command completion notification is received from the edge device 102 within the predetermined period (YES in step S1403), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0180] If the command completion notification is not received from the edge device 102 within the predetermined period (NO at step S1403), the distribution control device 101 judges whether the connection status of the edge device 102 is good (step S1404). The process at step S1404 is the same as the process at step S804.

[0181] If the connection status of the edge device 102 is not good (step S1404: NO), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S1405). After that, the delivery control device 101 ends the cancellation determination process.

[0182] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0183] If the connection state of the edge device 102 is good (YES in step S1404), the distribution control device 101 judges whether the load of the edge device 102 is high (step S1406). The process of step S1406 is the same as the process of step S806.

[0184] If the load on the edge device 102 is not high (step S1406: NO), the delivery control device 101 registers data associating the cause "other" with the identification information of the edge device 102 in the cancellation target list (step S1407). After that, the delivery control device 101 ends the cancellation determination process.

[0185] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0186] If the load on the edge device 102 is high (YES in step S1406), the delivery control device 101 registers data associating the cause "device specific" with the identification information of the edge device 102 in the cancellation target list (step S1408). After that, the delivery control device 101 ends the cancellation determination process.

[0187] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0188] After the abort determination process is completed for all edge devices 102, the distribution control device 101 determines a recommended operation to be presented to the operator based on the abort target list. The method of determining the recommended operation is the same as the method described with reference to FIG.

[0189] The edge device 102 can be relatively evaluated by determining the connection state and load of the edge device 102 based on the comparison result between the evaluation index of the edge device 102 and the representative value of the evaluation index. For example, an edge device 102 with an extremely poor connection state or an extremely high load compared to other edge devices 102 is recorded as a device-specific factor.

[0190] Next, a description will be given of the abort determination process shown in Fig. 15. The abort determination process shown in Fig. 15 is executed once for all edge devices 102. In the abort determination process shown in Fig. 15, the cause of failure is identified based on the result of comparison between a representative value of the evaluation index acquired from each edge device 102 and a threshold value.

[0191] The distribution control device 101 calculates a representative value of the load index (step S1501), and also calculates a representative value of the connection state index (step S1502). The processes in steps S1501 and S1502 are the same as the processes in steps S801 and S802.

[0192] The distribution control device 101 determines whether there is an edge device 102 from which a command completion notification has not been received within a predetermined period of time (step S1503).

[0193] If there is no edge device 102 that has not received a command completion notification within the predetermined period (NO in step S1503), the delivery control device 101 ends the abort determination process. At this time, the delivery control device 101 updates the entries corresponding to each edge device 102 in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "success".

[0194] If there is an edge device 102 from which the command completion notification has not been received within the predetermined period (YES at step S1503), the distribution control device 101 determines whether the representative value of the connection status indicator is equal to or greater than a threshold value (step S1504).

[0195] If the representative value of the connection status index is smaller than the threshold value (NO in step S1504), the distribution control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the cancellation target list for each edge device 102 in which the distribution sequence has failed (step S1505). After that, the distribution control device 101 proceeds to step S1509.

[0196] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0197] If the representative value of the connection status index is equal to or greater than the threshold value (YES at step S1504), the distribution control device 101 determines whether the representative value of the load index is equal to or greater than the threshold value (step S1506).

[0198] If the representative value of the load index is equal to or greater than the threshold value (YES in step S1506), the distribution control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the cancellation target list for each edge device 102 in which the distribution sequence has failed (step S1507). After that, the distribution control device 101 proceeds to step S1509.

[0199] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0200] If the representative value of the load index is smaller than the threshold value (NO in step S1506), the distribution control device 101 registers data in which the cause "other" is associated with the identification information of the edge device 102 in the cancellation target list for each edge device 102 in which the distribution sequence has failed (step S1508). After that, the distribution control device 101 proceeds to step S1509.

[0201] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0202] In step S1509, the delivery control device 101 determines a recommended operation to be presented to the operator based on the cancellation target list (step S1509). After that, the delivery control device 101 ends the cancellation determination process.

[0203] Of the recommended operations, the method of determining an operation related to stopping a delivery sequence is the same as in Example 1. In Example 2, an authentication operation is also determined. For example, an operation for authenticating only edge devices 102 that continue the delivery sequence, an operation for authenticating all or a group of edge devices 102, etc. are determined.

[0204] Based on the result of comparing the representative value of the evaluation index with the threshold value, the connection state and load of the edge device 102 are determined, thereby making it possible to evaluate the entire system. Furthermore, the abort determination process shown in Fig. 15 can reduce the amount of calculation compared to the process performed on an edge device 102 basis as shown in Figs. 13 and 14.

[0205] This concludes the description of the stop determination process. Returning to the description of FIG.

[0206] The distribution control device 101 transmits the result of the stop determination process and an authentication request to the operator terminal 104 (step S1208). The result includes the edge device management information 222, recommended operations, a list of operations to be stopped, and the like.

[0207] The worker terminal 104 presents a screen based on the result of the cancellation determination process and accepts the worker's authentication operation and cancellation operation. Here, the screen presented to the worker will be described. Fig. 16 is a diagram showing an example of a screen displayed on the worker terminal 104 in the second embodiment.

[0208] The screen 1600 includes display fields 1601, 1602, 1603 and a selection field 1604. The display fields 1601, 1602, 1603 and the selection field 1604 are the same as the display fields 1001, 1002, 1003 and the selection field 1004.

[0209] However, in the display field 1602 of the second embodiment, not only the operations for the failed delivery sequence but also the operations related to the authentication of the delivery sequence are displayed. Also, in the selection field 1604, a button is displayed which instructs an operation that combines the operations for the failed delivery sequence and the operations related to the authentication of the delivery sequence. For example, if the delivery sequence of some edge devices 102 has failed, "Cancel the delivery sequence of the failed edge device and authenticate the delivery sequence of the other edge devices" is displayed, and if there is no failed edge device 102, "Authenticate the delivery sequence of all edge devices" is displayed.

[0210] This concludes the explanation of the screen. Let us return to the explanation of FIG.

[0211] The worker uses the worker terminal 104 to perform authentication and cancellation operations (step S1209). Specifically, the worker presses one of the buttons displayed in the selection field 1604. The worker terminal 104 transmits an authentication response and a cancellation request to the distribution control device 101 (step S1210). Here, it is assumed that the worker has selected "Cancel the distribution sequence of the failed edge device and authenticate the distribution sequences of the other edge devices."

[0212] The distribution control device 101 transmits a stop instruction to the edge device 102 to be stopped (step S1211). Also, the distribution control device 101 transmits a status update request to the edge device 102 to be continued (step S1212). In the sequence diagram shown in Fig. 12, a stop instruction is transmitted to edge device (B) 102, and a status update request is transmitted to edge device (A) 102.

[0213] The edge device 102 transmits a status update response to the delivery control device 101 (step S1213), and also executes the command (step S1214). The edge device 102 transmits metrics to the delivery control device 101 (step S1215). The processes of steps S1213, S1214, and S1215 are the same as the processes of steps S616, S617, and S618.

[0214] When the distribution control device 101 receives the metric, it executes a metric confirmation process (step S1216), and transmits an authentication request to the operator terminal 104 (step S1217). The metric confirmation process of the second embodiment is the same as that of the first embodiment.

[0215] The worker performs an authentication operation using the worker terminal 104 (step S1218), and the worker terminal 104 transmits an authentication response to the distribution control device 101 (step S1219). The processes in steps S1218 and S1219 are the same as the processes in steps S621 and S622.

[0216] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S1220). The process of step S1220 is the same as the process of step S623.

[0217] The edge device 102 transmits a status update response to the distribution control device 101 (step S1221). The process of step S1221 is the same as the process of step S624.

[0218] If there is no failed edge device 102, only an authentication request is transmitted in step S1208, only an authentication operation is performed in step S1209, and only an authentication response is transmitted in step S1210. Also, no abort instruction is transmitted.

[0219] According to the second embodiment, the distribution control device 101 identifies the cause of failure for the edge device 102 that does not receive the command completion notification, and proposes the stop operation of the distribution sequence and the authentication operation according to the identified cause of failure. This allows efficient control of the stop of the distribution sequence, thereby reducing the man-hours and work time required for controlling the distribution sequence. EXAMPLES

[0220] In the embodiment 3, the execution phase of the abort determination process is different from that in the embodiment 1. Hereinafter, the embodiment 3 will be described, focusing on the difference from the embodiment 1.

[0221] The system configuration of the third embodiment is the same as that of the first embodiment. The hardware configuration and the software configuration of the distribution control device 101 and the edge device 102 of the third embodiment are the same as those of the first embodiment. The data structures of the metric correct value management information 221 and the edge device management information 222 of the third embodiment are the same as those of the first embodiment.

[0222] FIG. 17 is a sequence diagram illustrating a process flow in the system according to the third embodiment.

[0223] The worker transmits a distribution sequence registration request to the distribution control device 101 using the worker terminal 104 (step S1701). Step S1701 is the same process as step S601.

[0224] The worker uses the worker terminal 104 to transmit a distribution sequence start instruction to the distribution control device 101 (step S1702). Step S1702 is the same as the process of step S602.

[0225] When the distribution control device 101 receives the distribution sequence start instruction, it distributes a file to the edge device 102, and also transmits a status update request (step S1703). The process of step S1703 is the same as the process of step S603.

[0226] In response to the file distribution and status update request, the edge device 102 transmits a status update response to the distribution control device 101 (step S1704). S605 This is the same as the processing of

[0227] The edge device 102 executes the command in a predetermined phase (step S1705), and transmits a command completion notification to the distribution control device 101 (step S1706). The processes in steps S1705 and S1706 are the same as the processes in steps S610 and S611.

[0228] When the distribution control device 101 receives the command completion notification, it transmits an authentication request to the operator terminal 104 (step S1707). The process of step S1707 is the same as the process of step S612.

[0229] The worker performs an authentication operation using the worker terminal 104 (step S1708), and transmits an authentication response to the distribution control device 101 (step S1709). The processes in steps S1708 and S1709 are the same as the processes in steps S613 and S614.

[0230] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S1710). The process of step S1710 is the same as the process of step S615.

[0231] The edge device 102 transmits a status update response to the distribution control device 101 (step S1711), and also executes the command (step S1712). The edge device 102 transmits metrics to the distribution control device 101 (step S1713). The processes of steps S1711, S1712, and S1713 are the same as the processes of steps S616, S617, and S618.

[0232] When the delivery control device 101 receives the metric, it executes a metric confirmation process (step S1714). In the third embodiment, the cause of failure is identified in the metric confirmation process.

[0233] Here, the metric confirmation process will be described. Fig. 18A and Fig. 18B are flowcharts for explaining an example of the metric confirmation process executed by the delivery control device 101 of the third embodiment. The metric confirmation process is performed by the processor 201 that executes the metric confirmation program 212. In addition, the metric confirmation process is executed when a metric is received from the edge device 102.

[0234] The distribution control device 101 refers to the metric correct value management information 221, acquires a correct value from an entry corresponding to the type of the received metric, and judges whether the received metric matches the correct value (step S1801).

[0235] If the received metric does not match the correct value (NO in step S1801), the distribution control device 101 proceeds to step S1804.

[0236] If the received metric matches the correct value (YES at step S1801), the distribution control device 101 determines whether or not checking has been completed for the metrics of all edge devices 102 (step S1802).

[0237] If the check has not been completed for the metrics of all edge devices 102 (NO in step S1802), the distribution control device 101 proceeds to step S1804.

[0238] When the confirmation of the metrics of all edge devices 102 is completed (YES in step S1802), the distribution control device 101 transmits the determination result and an authentication request to the operator terminal 104 (steps S1803, S1715), and ends the metric confirmation process.

[0239] In step S1804, the distribution control device 101 determines whether a certain period of time has elapsed (step S1804).

[0240] If the certain time has not elapsed (NO at step S1804), the distribution control device 101 transitions to a state of waiting for metric reception (step S1805), and ends the metric confirmation process.

[0241] If the certain time has elapsed (step S1804: YES), the delivery control device 101 executes a stop determination process (step S1806), and then proceeds to step S1803. That is, the delivery control device 101 identifies the edge device 102 whose metric did not match the correct value within the certain time period as an edge device 102 whose delivery sequence has failed, and specifies the cause of the failure.

[0242] Here, the abort determination process executed in the metric confirmation process will be described. The delivery control device 101 executes different abort determination processes depending on the type of metric. Fig. 19 and Fig. 20 are flowcharts for explaining an example of the abort determination process executed by the delivery control device 101 of the third embodiment. The abort determination process is executed by the processor 201 executing the abort determination program 211.

[0243] First, the abort determination process shown in Fig. 19 will be described. The abort determination process shown in Fig. 19 is executed once for an edge device 102 whose metric value does not match the correct value at the start of the abort determination process. In the abort determination process shown in Fig. 19, the cause of failure is identified based on the load index acquired from the edge device 102.

[0244] The distribution control device 101 calculates a representative value of the load index (step S1901). The process of step S1901 is the same as the process of step S801.

[0245] The distribution control device 101 judges whether or not the representative value of the load index is equal to or greater than a threshold value (step S1902).

[0246] If the representative value of the load index is equal to or greater than the threshold value (YES in step S1902), the delivery control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the suspension target list for the number of edge devices 102 whose metrics do not match the correct value (step S1903). After that, the delivery control device 101 proceeds to step S1905.

[0247] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0248] If the representative value of the load index is equal to or smaller than the threshold value (NO in step S1902), the delivery control device 101 registers data in which the cause "other" is associated with the identification information of the edge device 102 in the suspension target list for the number of edge devices 102 whose metrics do not match the correct value (step S1904). After that, the delivery control device 101 proceeds to step S1905.

[0249] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0250] In step S1905, the delivery control device 101 determines a recommended operation to be presented to the operator based on the cancellation target list (step S1905). After that, the delivery control device 101 ends the cancellation determination process.

[0251] Of the recommended operations, the method of determining an operation related to stopping a delivery sequence is the same as in Example 1. In Example 3, an authentication operation is also determined. For example, an operation for authenticating only edge devices 102 that continue the delivery sequence, an operation for authenticating all or a group of edge devices 102, etc. are determined.

[0252] Next, the abort determination process shown in Fig. 20 will be described. The abort determination process shown in Fig. 20 is executed once for an edge device 102 whose metric value does not match the correct value at the start of the abort determination process. In the abort determination process shown in Fig. 20, the cause of failure is identified based on the result of comparing the representative values ​​of the load index and connection status index acquired from each edge device 102 with threshold values.

[0253] The distribution control device 101 calculates a representative value of the load index (step S2001), and also calculates a representative value of the connection state index (step S2002). The processes in steps S2001 and S2002 are the same as the processes in steps S801 and S802.

[0254] The distribution control device 101 judges whether or not the representative value of the connection state index is equal to or greater than a threshold value (step S2003).

[0255] If the representative value of the connection status index is smaller than the threshold value (step S2003: NO), the delivery control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the suspension target list for the number of edge devices 102 whose metrics do not match the correct value (step S2004). After that, the delivery control device 101 proceeds to step S2008.

[0256] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “connection state”.

[0257] If the representative value of the connection status index is equal to or greater than the threshold value (YES in step S2003), the distribution control device 101 determines whether the representative value of the load index is equal to or greater than the threshold value (step S2005).

[0258] If the representative value of the load index is equal to or greater than the threshold value (YES in step S2005), the delivery control device 101 registers data associating the cause "common" with the identification information of the edge device 102 in the suspension target list for the number of edge devices 102 whose metrics do not match the correct value (step S2006). After that, the delivery control device 101 proceeds to step S2008.

[0259] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “failure” and sets the failure indicator 503 to “load”.

[0260] If the representative value of the load index is smaller than the threshold value (NO in step S2005), the delivery control device 101 registers data in which the cause "other" is associated with the identification information of the edge device 102 in the suspension target list for the number of edge devices 102 whose metrics do not match the correct value (step S2007). After that, the delivery control device 101 proceeds to step S2008.

[0261] At this time, the distribution control device 101 updates the entry corresponding to the edge device 102 registered in the cancellation target list in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to “Failed” and sets the failure indicator 503 to “Other”.

[0262] In step S2008, the distribution control device 101 determines a recommended operation to be presented to the operator based on the cancellation target list (step S2008). After that, the distribution control device 101 ends the cancellation determination process.

[0263] Of the recommended operations, the method of determining an operation related to stopping a delivery sequence is the same as in Example 1. In Example 3, an authentication operation is also determined. For example, an operation for authenticating only edge devices 102 that continue the delivery sequence, an operation for authenticating all or a group of edge devices 102, etc. are determined.

[0264] The distribution control device 101 selects the abort determination process to be executed according to the type of metric. For example, if the metric is the presence or absence of an execution result file accompanying software installation, or if the metric is the version of information content, the cause of the metric discrepancy may be a problem with the command or a high load on the edge device 102, and so the abort determination process shown in Fig. 19 is executed. If the metric is the acquisition rate of information content, the cause of the metric discrepancy may be a poor network connection or a high load on the edge device 102, and so the abort determination process shown in Fig. 20 is executed.

[0265] This concludes the explanation of the metric confirmation process. Return to FIG.

[0266] The operator uses the operator terminal 104 to perform authentication and cancellation operations (step S1716), and transmits an authentication response and cancellation request to the distribution control device 101 (step S1717). Here, it is assumed that the operator has selected "cancellation of the distribution sequence of the failed edge device and authentication of the distribution sequences of other edge devices."

[0267] The distribution control device 101 transmits a stop instruction to the edge device 102 to be stopped (step S1718). Also, the distribution control device 101 transmits a status update request to the edge device 102 to be continued (step S1719). In the sequence diagram shown in Fig. 17, a stop instruction is transmitted to edge device (B) 102, and a status update request is transmitted to edge device (A) 102.

[0268] The edge device 102 transmits a status update response to the distribution control device 101 (step S1720).

[0269] If the abort determination process is not executed, only the authentication request is sent in step S1715, and only the authentication operation is performed in step S1716. S1717 In this case, only an authentication response is sent, and no abort instruction is sent.

[0270] According to the third embodiment, the delivery control device 101 identifies the cause of failure for the edge device 102 whose metric does not match the correct value, and proposes a delivery sequence stop operation and an authentication operation according to the identified cause of failure. This allows efficient control of the delivery sequence stop, thereby reducing the man-hours and work time required for controlling the delivery sequence. EXAMPLES

[0271] In the fourth embodiment, the abort determination process is executed before the start of the distribution sequence. Hereinafter, the fourth embodiment will be described, focusing on the difference from the first embodiment.

[0272] The system configuration of the fourth embodiment is the same as that of the first embodiment. The hardware configuration and the software configuration of the distribution control device 101 and the edge device 102 of the fourth embodiment are the same as those of the first embodiment. The data structures of the metric correct value management information 221 and the edge device management information 222 of the fourth embodiment are the same as those of the first embodiment.

[0273] 21A and 21B are sequence diagrams illustrating the flow of processing in the system according to the fourth embodiment.

[0274] The worker transmits a distribution sequence registration request to the distribution control device 101 using the worker terminal 104 (step S2101). Step S2101 is the same process as step S601.

[0275] The worker uses the worker terminal 104 to transmit a distribution sequence start instruction to the distribution control device 101 (step S2102). Step S2102 is the same as the process of step S602.

[0276] When the distribution control device 101 receives the distribution sequence start instruction, it measures (step S2103) the bandwidth of each edge device 102. For example, the distribution control device 101 measures the bandwidth using a ping transmission function or the like.

[0277] The distribution control device 101 executes a stop determination process based on the result of the bandwidth measurement (step S2104).

[0278] Here, the details of the stop determination process will be described. Fig. 22 is a flowchart illustrating an example of the stop determination process executed by the distribution control device 101 of the fourth embodiment. The stop determination process is performed by the processor 201 that executes the stop determination program 211. The stop determination process shown in Fig. 22 is executed once for all edge devices 102.

[0279] The distribution control device 101 determines whether the size of the file to be transmitted to the edge device 102 is equal to or larger than a threshold (step S2201).

[0280] Here, the file transmitted to edge device 102 is a file transmitted from distribution control device 101 at the start of the distribution sequence. In the case of a distribution sequence in which software and information content are acquired from distribution server 103, the size of the software and information content may also be taken into consideration.

[0281] If the file size is smaller than the threshold value (NO in step S2201), the distribution control device 101 ends the abort determination process.

[0282] If the file size is equal to or larger than the threshold (YES in step S2201), the distribution control device 101 starts loop processing of the edge devices 102 (step S2202). The distribution control device 101 selects one edge device 102 from among the edge devices 102 that are targets for executing the distribution sequence.

[0283] The distribution control device 101 determines whether the bandwidth of the selected edge device 102 is equal to or greater than a threshold (step S2203).

[0284] If the bandwidth of the selected edge device 102 is equal to or greater than the threshold (YES in step S2203), the distribution control device 101 proceeds to step S2205.

[0285] If the bandwidth of the selected edge device 102 is smaller than the threshold (NO at step S2203), the distribution control device 101 registers the edge device 102 in the suspension target list (step S2204), and then proceeds to step S2205.

[0286] In step S2205, the distribution control device 101 determines whether or not the process has been completed for all edge devices 102 that are targets of execution of the distribution sequence (step S2205).

[0287] If the process has not been completed for all edge devices 102 that are targets of the distribution sequence (NO in step S2205), the distribution control device 101 returns to step S2202 and executes the same process.

[0288] When processing has been completed for all edge devices 102 that are targets of execution of the distribution sequence (YES in step S2205), the distribution control device 101 determines whether the ratio of edge devices 102 that are targets of execution of the distribution sequence to the number of edge devices 102 that are targets of cancellation is greater than or equal to a threshold value (step S2206).

[0289] If the ratio is equal to or greater than the threshold (step S2206: YES), the delivery control device 101 determines a recommended operation according to the cause "common" (step S2207). After that, the delivery control device 101 ends the cancellation determination process. For example, the delivery control device 101 determines to cancel the execution of the delivery sequence for all edge devices 102 that are targets of the delivery sequence.

[0290] If the ratio is smaller than the threshold (step S2206: NO), the delivery control device 101 determines a recommended operation according to the cause "device specific" (step S2208). After that, the delivery control device 101 ends the abort determination process. For example, the delivery control device 101 determines to abort the execution of the delivery sequence for the edge device 102 registered in the abort target list.

[0291] This concludes the description of the abort determination process. Returning to the description of FIG.

[0292] The distribution control device 101 transmits a result of the stop determination process to the operator terminal 104 (step S2105). The result includes a recommended operation and a list of operations to be stopped.

[0293] The worker performs a stop operation using the worker terminal 104 (step S2106). The process of step S2106 is the same as the process of step S607.

[0294] The worker terminal 104 transmits a stop request according to the worker's operation to the distribution control device 101 (step S2107). The stop request includes information about the operated button.

[0295] The distribution control device 101 identifies the edge device 102 to be stopped in accordance with the stop request, distributes the file to the edge devices 102 other than the identified edge device 102, and also transmits a status update request (step S2108).

[0296] When the execution of the distribution sequence of a particular edge device 102 is stopped, the distribution control device 101 distributes the file to edge devices 102 other than the specific edge device 102, and also transmits a status update request. At this time, the distribution control device 101 updates the entry corresponding to the specific edge device 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to "failure" and the failure indicator 503 to "connection state".

[0297] If it is selected to stop execution of the distribution sequence of all edge devices 102, the distribution control device 101 does not transmit anything to all edge devices 102. At this time, the distribution control device 101 updates the entries corresponding to all edge devices 102 in the edge device management information 222. Specifically, the distribution control device 101 sets the distribution sequence execution result 502 to "failure" and the failure indicator 503 to "connection state".

[0298] It is also possible to instruct edge devices 102 belonging to a group including a specific edge device 102 to stop executing the delivery sequence. In this case, the delivery control device 101 refers to edge device management information 222 to identify the group including the specific edge device 102, distributes a file to edge devices 102 other than the edge devices 102 belonging to the group, and requests a status update. At this time, the delivery control device 101 updates the entries corresponding to the edge devices 102 belonging to the group in the edge device management information 222. Specifically, the delivery control device 101 sets the delivery sequence execution result 502 to "failure" and the failure indicator 503 to "connection status".

[0299] If standby is selected, the distribution control device 101 distributes the file to all edge devices 102 and requests a status update.

[0300] If the edge device 102 is not included in the suspension target list, the processes from step S2105 to step S2107 are not executed.

[0301] Here, it is assumed that a request has been made to stop execution of the distribution sequence of edge device (B) 102. Therefore, distribution control device 101 distributes the file only to edge device (A) 102, and transmits a status update request.

[0302] In response to the file distribution and status update request, the edge device 102 transmits a status update response to the distribution control device 101 (step S2109).

[0303] The edge device 102 executes the command in a predetermined phase (step S2110), and transmits a command completion notification to the distribution control device 101 (step S2111).

[0304] When the distribution control device 101 receives the command completion notification, it transmits an authentication request to the operator terminal 104 (step S2112).

[0305] The worker performs an authentication operation using the worker terminal 104 (step S2113), and transmits an authentication response to the distribution control device 101 (step S2114).

[0306] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S2115).

[0307] The edge device 102 transmits a status update response to the distribution control device 101 (step S2116), and also executes the command (step S2117). The edge device 102 transmits metrics to the distribution control device 101 (step S2118).

[0308] When the distribution control device 101 receives the metric, it executes a metric confirmation process (step S2119) and transmits an authentication request to the operator terminal 104 (step S2120).

[0309] The worker performs an authentication operation using the worker terminal 104 (step S2121), and transmits an authentication response to the distribution control device 101 (step S2122).

[0310] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S2123).

[0311] The edge device 102 transmits a status update response to the distribution control device 101 (step S2124).

[0312] The process from step S2110 to step S2124 is the same as the process from step S610 to step S624.

[0313] According to the fourth embodiment, before the start of a distribution sequence, the distribution control device 101 identifies an edge device 102 with limited bandwidth as an edge device 102 that may cause the distribution sequence to fail. This allows the distribution sequence to be efficiently controlled, thereby reducing the number of steps and the work time required by an operator to control the distribution sequence.

[0314] (Modification) Each of the embodiments from Example 1 to Example 4 can be combined. Here, an embodiment in which Example 2 and Example 4 are combined will be described.

[0315] 23A and 23B are sequence diagrams illustrating the flow of processing in the system of the modified example.

[0316] The worker transmits a distribution sequence registration request to the distribution control device 101 using the worker terminal 104 (step S2301). Step S2301 is the same process as step S601.

[0317] The worker uses the worker terminal 104 to transmit a distribution sequence start instruction to the distribution control device 101 (step S2302). Step S2302 is the same as the process of step S602.

[0318] When the distribution control device 101 receives the distribution sequence start instruction, it measures the bandwidth of each edge device 102 (step S2303). The process of step S2303 is the same as the process of step S2103.

[0319] The distribution control device 101 executes a stop determination process based on the result of the bandwidth measurement (step S2304). The process of step S2304 is the same as the process of step S2104.

[0320] The distribution control device 101 transmits a result of the stop determination process to the operator terminal 104 (step S2305). The process of step S2305 is the same as the process of step S2105.

[0321] The worker performs a cancel operation using the worker terminal 104 (step S2306). The process of step S2306 is the same as the process of step S607.

[0322] The worker terminal 104 transmits a stop request in response to the worker's operation to the distribution control device 101 (step S2307). The process of step S2307 is the same as the process of step S2107.

[0323] The distribution control device 101 identifies the edge device 102 to be stopped in accordance with the stop request, distributes the file to the edge devices 102 other than the identified edge device 102, and also transmits a status update request (step S2308). The process of step S2308 is the same as the process of step S2108.

[0324] If the edge device 102 is not on the stop target list, the processes from step S2305 to step S2307 are not executed. Here, it is assumed that the edge device 102 is not on the stop target list. Therefore, a file is distributed to each of the edge device (A) 102 and the edge device (B) 102, and a status update request is transmitted.

[0325] In response to the file distribution and status update request, the edge device 102 transmits a status update response to the distribution control device 101 (step S2309). S605 This is the same as the processing of

[0326] After receiving the status update response, the distribution control device 101 starts the stop determination process (step S2310).

[0327] The edge device 102 continuing the distribution sequence executes the command in a predetermined phase (step S2311), and transmits a command completion notification to the distribution control device 101 (step S2312). The processes of steps S2311 and S2312 are the same as the processes of steps S610 and S611.

[0328] The distribution control device 101 executes the abort determination process based on the reception status of the command completion notification. The abort determination process is the same as the process described in the second embodiment, so the description will be omitted.

[0329] The distribution control device 101 transmits the result of the stop determination process and an authentication request to the operator terminal 104 (step S2313). The process of step S2313 is the same as the process of step S1208.

[0330] The worker uses the worker terminal 104 to perform authentication and cancellation operations (step S2314), and transmits an authentication response and cancellation request to the distribution control device 101 (step S2315). The processes in steps S2314 and S2315 are the same as those in steps S1209 and S1210.

[0331] The delivery control device 101 transmits a stop instruction to the edge device 102 to be stopped (step S2316). Also, the delivery control device 101 transmits a status update request to the edge device 102 to be continued (step S2317). The processes of steps S2316 and S2317 are the same as the processes of steps S1211 and S1212.

[0332] The edge device 102 transmits a status update response to the delivery control device 101 (step S2318), and also executes the command (step S2319). The edge device 102 transmits metrics to the delivery control device 101 (step S2320). The processes of steps S2318, S2319, and S2320 are the same as the processes of steps S616, S617, and S618.

[0333] When the distribution control device 101 receives the metric, it executes a metric confirmation process (step S2321), and transmits an authentication request to the operator terminal 104 (step S2322). The metric confirmation process is the same as that in the first embodiment.

[0334] The worker performs an authentication operation using the worker terminal 104 (step S2323), and transmits an authentication response to the distribution control device 101 (step S2324). The processes in steps S2323 and S2324 are the same as those in steps S621 and S622.

[0335] After receiving the authentication response, the distribution control device 101 transmits a status update request to the edge device 102 (step S2325). The process of step S2325 is the same as the process of step S623.

[0336] The edge device 102 transmits a status update response to the distribution control device 101 (step S2326). The process of step S2326 is the same as the process of step S624.

[0337] In the example shown in FIGS. 23A and 23B, the distribution control device 101 transmits a stop instruction to the edge device (B) 102 because a command completion notification was not received from the edge device (B) 102.

[0338] The present invention is not limited to the above-mentioned embodiment, but includes various modified examples. For example, the above-mentioned embodiment describes the configuration in detail to easily explain the present invention, and the present invention is not necessarily limited to the configuration including all the described configurations. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0339] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that realizes the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, etc.

[0340] Furthermore, the program code for realizing the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, Java (registered trademark), etc.

[0341] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed over a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read out and execute the program code stored in the storage means or storage medium.

[0342] In the above-mentioned embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all the control lines and information lines are shown in the product. All the components may be connected to each other. [Explanation of symbols]

[0343] 101 Distribution control device 102 Edge Devices 103 Distribution Server 104 Worker terminal 105 Network 201, 301 processors 202, 302 Network Interface 203, 303 Main storage 204, 304 Secondary storage device 211 Cancellation Judgment Program 212 Metric Verification Program 221 Metric Correct Value Management Information 222 Edge device management information 311 Command Execution Program 312 Metrics Sending Program 1000, 1600 screen

Claims

1. 1. A method for controlling information distribution processing for a plurality of edge devices, executed by a computer system connected to the edge devices, comprising: The computer system includes a computer having a processor, a storage device connected to the processor, and a network interface connected to the processor; The method for controlling information distribution processing includes: a first step of the processor monitoring a state of each of the plurality of edge devices after starting the information distribution process for the plurality of edge devices; a second step of executing a first process by the processor to identify an edge device in which the information distribution process has failed and a cause of the failure based on a result of monitoring the state of each of the plurality of edge devices; a third step of the processor presenting an operation content related to stopping the information distribution process based on a result of the first process; 11. A method for controlling information distribution processing, comprising: the failure cause including a first failure cause that is a cause specific to the edge device; and a second failure cause that is a cause common to the plurality of edge devices.

2. A method for controlling the information distribution process according to claim 1, comprising: The second step includes: acquiring, from the plurality of edge devices, at least one of an index indicating a communication quality of the edge device and an index indicating a load of the edge device as an evaluation index; and a step of the processor using the evaluation index to identify a cause of failure of the edge device in which the information distribution process has failed.

3. A method for controlling information distribution processing according to claim 2, comprising: the first step includes a step of monitoring by the processor whether or not there is a response from each of the plurality of edge devices; The method for controlling information distribution processing, wherein the second step includes a step in which the processor identifies the edge device that does not respond as the edge device in which the information distribution processing has failed.

4. A method for controlling information distribution processing according to claim 2, comprising: managing a correct answer value of a metric indicating a progress state of the information distribution process from the plurality of edge devices; The first step includes a step of the processor acquiring the metrics from the plurality of edge devices, The second step is characterized in that it includes a step in which the processor identifies the edge device whose acquired metric did not match a correct value within a period of time as the edge device in which the information distribution process has failed.

5. A method for controlling information distribution processing according to claim 2, comprising: The third step includes: a step of, when the edge device in which the information distribution process has failed due to the first failure cause is present, presenting a recommendation to stop the information distribution process of the edge device; and when there is an edge device where the information distribution process has failed due to the second failure cause, the processor presents a recommendation to stop the information distribution process of the multiple edge devices.

6. A method for controlling information distribution processing according to claim 5, comprising: the information distribution process is executed on a group basis composed of the plurality of edge devices, The third step is a method for controlling information distribution processing, characterized in that, when there is an edge device where the information distribution processing has failed due to the first failure cause, the processor presents a recommendation to at least one of canceling the information distribution processing of the edge device and canceling the information distribution processing of the multiple edge devices belonging to the group including the edge device.

7. A method for controlling information distribution processing according to claim 1, comprising: The processor measures bandwidths of the edge devices before starting the information distribution process; executing, by the processor, a second process of identifying the edge device in which there is a possibility that the information distribution process will fail, based on a result of comparing the bandwidth with a threshold; and a step of the processor presenting an operation for stopping the information distribution process based on a result of the second process.

8. A computer system that connects to a plurality of edge devices and that performs information distribution processing, a computer having a processor, a storage device connected to the processor, and a network interface connected to the processor; The processor, After the information distribution process for the plurality of edge devices is started, a state of each of the plurality of edge devices is monitored; execute a first process of identifying an edge device in which the information distribution process has failed and a cause of the failure based on a result of monitoring the state of each of the plurality of edge devices; presenting an operation content related to the cancellation of the information distribution process based on a result of the first process; A computer system, wherein the failure causes include a first failure cause that is a cause specific to the edge device, and a second failure cause that is a cause common to the plurality of edge devices.

9. The computer system of claim 8, The processor, acquiring at least one of an index indicating a communication quality of the edge devices and an index indicating a load of the edge devices as an evaluation index from the plurality of edge devices; A computer system comprising: a processor that uses the evaluation index to identify a cause of failure of the edge device in which the information distribution process has failed.

10. The computer system of claim 8, The processor, monitoring the presence or absence of a response from each of the plurality of edge devices; The edge device that does not respond is identified as the edge device in which the information distribution process has failed.

11. The computer system of claim 8, managing a correct answer value of a metric indicating a progress state of the information distribution process from the plurality of edge devices; The processor, Obtaining the metrics from the plurality of edge devices; the edge device for which the acquired metric does not match a correct answer value within a period of time is identified as the edge device for which the information distribution process has failed.

12. The computer system of claim 8, The processor, when there is an edge device in which the information distribution process has failed due to the first failure cause, presenting a recommendation to stop the information distribution process of the edge device; a computer system comprising: when an edge device in which the information distribution process has failed due to the second failure cause is present, a presentation is made recommending that the information distribution process of the plurality of edge devices be stopped; 13. The computer system of claim 8, The processor, measuring bandwidths of the edge devices before starting the information distribution process; execute a second process of identifying the edge device in which there is a possibility that the information distribution process will fail based on a result of comparing the bandwidth with a threshold; a computer system which presents an operation for stopping the information distribution process based on a result of the second process.

14. A computer that performs information distribution processing and is connected to a plurality of edge devices, a processor, a storage device connected to the processor, and a network interface connected to the processor; The processor, After the information distribution process for the plurality of edge devices is started, a state of each of the plurality of edge devices is monitored; Executing a process of identifying an edge device where the information distribution process has failed and a cause of the failure based on a result of monitoring the state of each of the plurality of edge devices; presenting an operation for stopping the information distribution process based on a result of the process; The failure cause includes a first failure cause that is a cause specific to the edge device, and a second failure cause that is a cause common to the plurality of edge devices.

Images