Management device, management system, management method, and program

Abstract

To provide a management device that can improve accuracy of estimating a suspect package.SOLUTION: A management device includes: a failure information acquisition unit that acquires, as failure information, suspected package information and a failure type from a managed device that has detected a failure in an own device and estimated a suspected package, which is a package that is estimated to have caused the failure; an acquisition count update unit that counts the number of times each piece of failure information has been acquired; a weighting coefficient specification unit that specifies a weighting coefficient according to the number of acquisitions; a destination specification unit that specifies another managed device having a suspected package using a package management ledger and the suspected package information; and a transmitter that transmits a weighting factor and the failure information to the other managed device. A package is a shipping unit of software or hardware installed in each managed device. The weighting coefficient is a weight that is multiplied by a preset suspect probability according to a combination of each failure type and each package used by each managed device to estimate the suspect package.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present disclosure relates to a management device, a management system, a management method, and a program. [Background technology]

[0002] There is a technology that notifies a maintenance manager of the package in which a failure has occurred when a failure occurs in an information processing device that has multiple packages. When a failure occurs in which the package in which the failure has occurred cannot be identified, a suspect package is estimated based on a history of past failures, as described in Patent Document 1. A suspect package is a package that is estimated (suspected) to have caused a failure. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-137806 Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, the fault occurrence history is a history of faults that occurred in a single information processing device that is the target of monitoring. Therefore, even if a fault occurs in another information processing device that has the same package, the fault occurrence history cannot be used to estimate the suspect package. In order to improve the accuracy of estimating the suspect package, it is desirable to be able to use fault information from other information processing devices as well.

[0005] An object of the present disclosure is to provide a management device, a management system, a management method, and a program that enable improvement in the accuracy of estimating suspect packages. [Means for solving the problem]

[0006] A management device of one embodiment of the present disclosure includes a fault information acquisition unit that acquires suspect package information, which is information about a suspect package, and a fault type as fault information from a managed device that has detected a fault and inferred a suspect package, which is a package that is presumed to have caused the fault, in the managed device itself; an acquisition count update unit that counts the number of times each piece of fault information is acquired; a weight coefficient identification unit that identifies a weight coefficient according to the number of acquisitions; a destination identification unit that identifies other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspect package information; and a transmission unit that transmits the weight coefficient and fault information to the identified other managed devices, wherein the package is a shipping unit of software or hardware installed in each managed device, and the weight coefficient is a weight that is multiplied by a predetermined suspicion probability according to the combination of each fault type and each package, which is used by each managed device when inferring a suspect package.

[0007] In one aspect of the management method of the present disclosure, a computer acquires suspect package information, which is information about the suspect package, and a fault type as fault information from a managed device that has detected a fault and inferred a suspect package, which is a package that is suspected to have caused the fault, counts the number of times each piece of fault information is acquired, determines a weighting coefficient according to the number of acquisitions, identifies other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package, and the suspect package information, and sends the weighting coefficient and fault information to the other identified managed devices, where a package is a shipping unit of software or hardware installed in each managed device, and the weighting coefficient is a weight that is multiplied by a predetermined suspicion probability according to the combination of each fault type and each package, which is used by each managed device when inferring a suspect package.

[0008] A program of one aspect of the present disclosure causes a computer to perform the following processes: acquire suspect package information, which is information about the suspect package, and a fault type as fault information from a managed device that has detected a fault and inferred a suspect package, which is a package that is suspected to have caused the fault, in its own device; count the number of times each piece of fault information is acquired; determine a weighting coefficient according to the number of times it is acquired; identify other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspect package information; and send the weighting coefficient and fault information to the other identified managed devices; wherein a package is a shipping unit of software or hardware installed in each managed device, and the weighting coefficient is a weight that is multiplied by a predetermined suspicion probability according to the combination of each fault type and each package, which is used by each managed device when inferring a suspect package. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to provide a management device, a management system, a management method, and a program that enable improvement in the accuracy of estimating suspect packages. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a conceptual diagram for explaining an overview of a management system according to the present disclosure. [Figure 2] FIG. 2 is a block diagram illustrating an example of a configuration of a management device according to the present disclosure. [Figure 3] 10 is an example of a fault acquisition count table according to the present disclosure. [Figure 4] 1 is an example of a weighting coefficient table according to the present disclosure. [Figure 5] 1 is an example of a package management ledger according to the present disclosure. [Figure 6] 1 is a block diagram illustrating an example of a configuration of a managed device according to the present disclosure. [Figure 7] FIG. 10 is a diagram showing an example of a first suspicion probability table according to the present disclosure. [Figure 8]FIG. 10 is a diagram showing an example of a second suspicion probability table according to the present disclosure. [Figure 9] 10 is a flowchart illustrating an example of the operation of a managed device according to the present disclosure. [Figure 10] 10 is a flowchart illustrating an example of an operation of a management device according to the present disclosure. [Figure 11] 10 is a flowchart illustrating an example of the operation of a managed device according to the present disclosure. [Figure 12] FIG. 2 is a block diagram illustrating an example of a configuration of a management device according to the present disclosure. [Figure 13] 10 is a flowchart illustrating an example of an operation of a management device according to the present disclosure. [Figure 14] FIG. 2 is a block diagram showing an example of a hardware configuration for executing control and processing according to each embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The embodiments described below are limited in a manner that is technically preferable for implementing the present disclosure, but the scope of the invention is not limited to the following. In all drawings used to describe the following embodiments, the same reference numerals are used for similar parts unless otherwise specified. In the following embodiments, repeated explanations of similar configurations and operations may be omitted.

[0012] In this disclosure, a package refers to a shipping unit of software or hardware to be installed in an information processing device.

[0013] (First embodiment) First, a management system according to a first embodiment will be described with reference to the drawings. When a failure is detected in one of multiple managed devices that are subject to management, the management device according to this embodiment transmits a weighting factor corresponding to the number of times the failure has been detected to all managed devices that have a suspect package that is presumed to have caused the failure. Upon receiving the weighting factor, the managed device updates a suspicion probability table for presuming a suspect package by multiplying the weighting factor by the suspicion probability used when presuming a suspect package.

[0014] (overview) 1 is a conceptual diagram for explaining an overview of a management system according to the present disclosure. An overview of a management system 1 will be explained using FIG.

[0015] The management system 1 includes managed devices 70-1 to 70-n and a management device 10. The management device 10 is communicably connected to each of the managed devices 70-1 to 70-n. The managed devices 70-1 to 70-n are communicably connected to administrator terminals 80-1 to 80-n, where n is a natural number of 2 or greater. In the following description, when it is not necessary to distinguish between the managed devices 70-1 to 70-n, they will be referred to as managed devices 70. Similarly, when it is not necessary to distinguish between the administrator terminals 80-1 to 80-n, they will be referred to as administrator terminals 80.

[0016] [Management device] The management device 10 is an information processing device communicatively connected to the managed devices 70. When a failure occurs in any of the managed devices 70-1 to 70-n, the management device 10 receives a failure type and suspected package information from the managed device. The failure type is a classification of failures according to the behavior and cause of the detected failure. The suspected package information is information about a suspected package that is generated when a failure is detected in the managed device 70-n. Upon receiving the failure type and suspected package information, the management device 10 counts the number of times each piece of failure information is acquired. The management device 10 determines a weighting factor based on the counted number of acquisitions. Furthermore, the management device 10 identifies the managed devices 70 that have the suspected package from among the managed devices 70-1 to 70-n. The management device 10 transmits the calculated weighting factor, suspected package information, and failure type to all of the identified managed devices 70.

[0017] [Managed device] The managed device 70 is an information processing device connected to the management device 10 so as to be able to communicate with it. For example, the managed device 70 is an information processing device such as a server, or a storage device such as a storage. As long as it is able to communicate with the management device 10, the managed device 70 may be a desktop terminal device, a notebook terminal device, a tablet, a portable terminal device, or the like.

[0018] The managed device 70 has multiple packages. When a failure occurs in the managed device 70, the managed device 70 detects the failure and detects the type of failure. Furthermore, the managed device 70 identifies a suspected package using a suspicion probability table. The suspicion probability table is a table that shows, for each of the multiple packages held by the managed device 70, the suspicion probability, which is the probability that a failure of a certain failure type is estimated to have occurred in that package. The managed device 70 transmits the identified failure type and suspected package information, which is information related to the identified suspected package, to the management device 10.

[0019] Furthermore, when the managed device 70 receives the weighting coefficient, suspected package information, and fault type from the management device 10, it updates the suspicion probability in the suspicion probability table using the received information.

[0020] [Administrator's terminal] The administrator terminal 80 is a terminal device operated by a maintenance manager of the managed device 70. The administrator terminal 80 includes an output unit (not shown). For example, the output unit is implemented by an input / output interface connected to a display device such as a display or an acoustic transducer such as a speaker. The administrator terminal 80 notifies the maintenance manager of information related to suspect packages sent from the managed device 70 via the output unit. The administrator terminal 80 also includes an input unit (not shown). For example, the maintenance manager updates information stored in a weighting coefficient table and a package management ledger via the input unit. The weighting coefficient table and the package management ledger will be described later.

[0021] (composition) Next, a management device and a managed device included in the management system according to the present disclosure will be described. The management device and the managed device will be described individually below.

[0022] [Management device] Fig. 2 is a block diagram showing an example of the configuration of a management device according to the present disclosure. The configuration of the management device 10 will be described using Fig. 2. As shown in Fig. 2, the management device 10 includes a fault information acquisition unit 11, an acquisition count update unit 12, a weighting coefficient determination unit 13, a transmission destination determination unit 14, a transmission unit 15, and a storage unit 16.

[0023] The fault information acquisition unit 11 acquires fault information sent from the managed device 70. The fault information includes the fault type and suspected package information.

[0024] As mentioned above, the fault type is a classification of the fault according to the behavior and cause of the detected fault. For example, the fault type may be "timing control failure" or "user interface failure."

[0025] Suspect package information is information about a suspect package, which is a package in which a failure is presumed to have occurred. Suspect package information is generated by the managed device 70 when a failure in the managed device 70 is detected. Suspect package information includes at least package identification information of the suspect package. Package identification information is information for uniquely identifying a suspect package. Package identification information is, for example, a UUID (Universally Unique Identifier). Suspect package information may include the manufacturing date of the suspect package, the revision date of the suspect package, and the revision number of the suspect package. The revision number of the suspect package is, for example, the version number or revision number of the suspect package.

[0026] The acquisition count update unit 12 counts the number of acquisitions for each piece of acquired fault information. The acquisition count update unit 12 also uses the counting results to update the acquisition count table for suspected packages. The acquisition count update unit 12 increments by 1 the count of the number of acquisitions for a package that matches the fault information acquired by the fault information acquisition unit 11.

[0027] The acquisition count table is a table for storing the number of acquisitions for each piece of fault information. FIG. 3 is a diagram showing an example of an acquisition count table in the present disclosure. In the example of FIG. 3, "Fault A" and "Fault B" indicate fault types, "PKG-A" indicates package identification information, "REV-1" to "REV-4" indicate revision numbers, "manufacturing date a" to "manufacturing date d" indicate manufacturing dates, and the numbers in the table indicate acquisition counts. In the example of FIG. 3, the acquisition count table is stored in table format for each piece of package identification information. Acquisition count table 741-1 is an acquisition count table that records the number of acquisitions for a fault in PKG-A. For example, in the example of FIG. 3, the acquisition count for a package whose fault type is "Fault A," whose package identification information is "PKG-A," whose revision number is "REV-1," and whose manufacturing date is "manufacturing date a" is 10.

[0028] A specific example of the acquisition count update unit 12 updating the number of times a fault has been acquired will be described with reference to Fig. 3. Assume that the fault information acquisition unit 11 acquires fault information from the managed device 70, in which the package identification information of the suspect package is PKG-A, the manufacturing date is manufacturing date a, and the revision number is REV-A. In this case, the acquisition count update unit 12 increases the count in the upper left column of the acquisition count table 741-1 from "10" to "11."

[0029] The weighting factor determination unit 13 uses the weighting factor table to determine a weighting factor according to the number of times the fault has been acquired and updated by the acquisition count update unit 12. The weighting factor is a weight by which the package suspicion probability is multiplied. The package suspicion probability will be described later.

[0030] A specific example of how the weighting coefficient specification unit 13 specifies a weighting coefficient will be described with reference to Fig. 4. Fig. 4 is an example of a weighting coefficient table according to the present disclosure. Weighting coefficient table 742 stores weighting coefficients determined in advance according to the number of times a fault has been detected. The weighting coefficient is set to a smaller value the fewer the number of times a fault has been detected, and a larger value the more the number of times a fault has been detected.

[0031] For example, suppose that the fault information acquisition unit 11 acquires fault information from the managed device 70, in which the package identification information of the suspect package is PKG-A, the production date is production date a, and the revision number is REV-A. Then, suppose that the acquisition count update unit 12 counts the number of times the fault information has been acquired as "11." In this case, the weighting coefficient determination unit 13 refers to the weighting coefficient table 742 and determines the weighting coefficient to be "1.5."

[0032] The destination specification unit 14 uses the suspect package information and the package management ledger to specify the managed device having the suspect package.

[0033] Next, a specific example in which the destination specification unit 14 specifies a managed device having a suspicious package will be described with reference to FIG. 5. FIG. 5 is an example of a package management ledger according to the present disclosure. The package management ledger is a list of managed devices 70 having packages. The information stored in the package management ledger is updated at regular time intervals, for example, via an input unit (not shown) of the administrator terminal 80. In the example of FIG. 5, a package management ledger is prepared for each package identification information. Package management ledger 743-1 is a package management ledger for a package whose package identification information is "PKG-A".

[0034] The destination specification unit 14 specifies the managed devices 70 that have the suspicious package using the fault information obtained by the fault information obtaining unit 11. For example, suppose that the fault information obtaining unit 11 obtains fault information for a package whose package identification information is "PKG-A," whose revision number is "REV-1," and whose manufacturing date is "manufacturing date a." In this case, the destination specification unit 14 refers to the package management ledger 743-1 shown in FIG. 5 and specifies that the managed devices 70 that have the suspicious package are "managed device 70-1" and "managed device 70-6."

[0035] The transmitter 15 transmits the identified weighting factor and the acquired fault information to the managed device 70 having the suspect package. For example, suppose that the fault information acquirer 11 acquires fault information from the managed device 70, where the package identification information of the suspect package is PKG-A, the manufacturing date is manufacturing date a, and the revision number is REV-A. Also, suppose that the acquisition count updater 12 updates the number of times a fault has been acquired for the package to "11." Also, suppose that the weighting factor identifier 13 identifies the weighting factor as "1.5." Also, suppose that the destination identifier 14 identifies the managed devices having the suspect package as "managed device 70-1" and "managed device 70-6." In this case, the transmitter 15 transmits the weighting factor "1.5" identified by the weighting factor identifier 13 and the fault information acquired by the fault information acquirer 11 to "managed device 70-1" and "managed device 70-6."

[0036] The storage unit 16 stores various information necessary for the processing of the management device 10. Specifically, the storage unit 16 stores an acquisition count table, a weighting coefficient table, and a package management ledger. The storage unit 16 may store information other than the above-mentioned information, such as information temporarily required for the processing of the management device 10.

[0037] [Managed device] Fig. 6 is a block diagram showing an example of the configuration of a managed device according to the present disclosure. The configuration of a managed device 70 will be described using Fig. 6. The managed device 70 includes a fault detection unit 71, a suspected package estimation unit 72, a fault information transmission unit 73, a weighting coefficient acquisition unit 74, a suspected probability calculation unit 75, a suspected probability table update unit 76, an output unit 77, a storage unit 78, and a package 79. The managed device 70 has multiple packages 79 (PKG-A 79-1, PKG-B 79-2, ...). In the following description, when it is not necessary to distinguish between the individual packages, they will be simply referred to as packages 79.

[0038] The fault detection unit 71 detects that a fault has occurred in one of the multiple packages 79 that the managed device 70 has. The fault detection unit 71 also identifies the type of fault that has been detected. The fault detection unit 71 detects the fault and the type of fault using a known method. For example, the fault detection unit 71 may detect that a fault has occurred when a value acquired by a sensor (not shown) provided in the managed device 70 is an abnormal value. The fault detection unit 71 also identifies the type of fault using a known method, for example, using a log of the value acquired by the sensor.

[0039] The suspected package estimation unit 72 estimates the package with the highest suspected probability for the identified fault type as the suspected package using a suspicion probability table. The suspicion probability table is a table that indicates, for each of multiple packages in the managed device 70, the probability that a fault of a certain fault type will occur in that package.

[0040] The suspicion probability table is divided into a first suspicion probability table and a second suspicion probability table. The first suspicion probability table and the second suspicion probability table will be explained using Figures 7 and 8.

[0041] FIG. 7 is a diagram illustrating an example of a first suspicion probability table in the present disclosure. The first suspicion probability table is a table in which initial values ​​of suspicion probabilities are stored. The values ​​stored in the first suspicion probabilities are predetermined. The first suspicion probability table is referenced when the suspicion probability table update unit 76 updates the suspicion probabilities. FIG. 8 is a diagram illustrating an example of a second suspicion probability table in the present disclosure. The second suspicion probability table is a table in which values ​​obtained by multiplying the values ​​in the first suspicion probability table by weighting factors received from the management device 10 are stored. The second suspicion probability table is referenced when the suspect package estimation unit 72 estimates a suspect package. The values ​​stored in the second suspicion probability table are updated each time a weighting factor is received from the management device 10. On the other hand, the values ​​stored in the first suspicion probability table do not fluctuate from the predetermined values.

[0042] The suspected package estimation unit 72 estimates a suspected package using the second suspicion probability table. The suspected package estimation unit 72 estimates the package with the highest suspect probability for the fault type identified by the fault detection unit 71 as the suspected package. For example, suppose that the fault detection unit 71 identifies the fault type as "Fault A." In this case, the suspected package estimation unit 72 references the second suspicion probability table 182 and estimates "PKG-A," which is the package with the highest suspect probability for "Fault A," as the suspected package.

[0043] The fault information transmitting unit 73 transmits the fault information to the management device 10. The fault information includes the fault type identified by the fault detecting unit 71 and suspected package information relating to the suspected package estimated by the suspected package estimating unit 72.

[0044] The weighting factor acquisition unit 74 acquires the fault information and weighting factors transmitted from the management device 10 .

[0045] The suspicion probability calculation unit 75 calculates the suspicion probability to be stored in the second suspicion probability table using the fault information and weighting coefficients acquired by the weighting coefficient acquisition unit 74. The suspicion probability calculation unit 75 sets the value of the suspicion probability of the package that matches the fault information, stored in the first suspicion probability table, as an initial value, and calculates the suspicion probability by multiplying the initial value by the acquired weighting coefficient.

[0046] 7 and 8, a specific example in which the suspicion probability calculation unit 75 calculates the suspicion probability will be described. In this specific example, it is assumed that the weighting coefficient acquisition unit 74 receives from the management device 10 that the weighting coefficient of PKG-A in failure C is "0.8". In this case, the suspicion probability calculation unit 75 first refers to the first suspicion probability table 181 shown in FIG. 7 and obtains the suspicion probability of PKG-A in failure C of "40%" as the initial value of the suspicion probability. Next, the suspicion probability calculation unit 75 multiplies the initial value of the suspicion probability, "40%," by the weighting coefficient "0.8" acquired by the weighting coefficient acquisition unit 74 to calculate the suspicion probability as "32".

[0047] If the total of the suspicion probabilities for each fault type does not equal a specified value after multiplication by the weighting coefficient, the suspicion probability calculation unit 75 may perform calibration so that the total equals the specified value. For example, if the suspicion probability is a percentage, the suspicion probability may be multiplied by a predetermined coefficient so that the total of the suspicion probabilities for each fault type equals 100%. For example, in the second suspicion probability table shown in FIG. 8, the total of the suspicion probabilities of "PKG-A," "PKG-B," "PKG-C," and "PKG-D" for fault B is 80%. In this case, the suspicion probability calculation unit 75 may calibrate the total to 100% by multiplying each suspicion probability by 1.25. After calibration, the suspicion probability of "PKG-A" is 50%, the suspicion probability of "PKG-B" is 37.5%, the suspicion probability of "PKG-C" is 6.25%, and the suspicion probability of "PKG-D" is 6.25%.

[0048] The suspicion probability table update unit 76 updates the values ​​of the second suspicion probability table using the suspicion probability calculated by the suspicion probability calculation unit 75. Each time a suspicion probability is calculated by the suspicion probability calculation unit 75, the suspicion probability table update unit 76 updates the suspicion probability value stored in the second suspicion probability table for the corresponding package.

[0049] The output unit 77 transmits a control signal to the administrator terminal 80 to notify the administrator terminal 80 of the fault information. The fault information is notified by text information or audio information. For example, the output unit 77 transmits to the administrator terminal 80 a control signal for outputting identification information of the managed device 70 in which the fault has occurred and text information about the fault information on a display screen provided in the administrator terminal 80. Alternatively, the output unit 77 transmits to the administrator terminal 80 a control signal for outputting audio information about the identification information of the managed device 70 in which the fault has occurred and the fault information on a speaker provided in the administrator terminal 80. The output unit 77 may output a control signal for displaying (notifying) information indicating that a fault has occurred and the fault information on a display screen (not shown) or a speaker (not shown) provided in the managed device 70.

[0050] The output unit 77 may transmit information indicating that the suspicion probability table has been updated to the administrator terminal 80. Furthermore, the output unit 77 may output a control signal to a display screen (not shown) or a speaker (not shown) provided in the managed device 70 to display (notify) information indicating that the suspicion probability table has been updated.

[0051] The storage unit 78 stores various types of information necessary for processing of the managed device 70. Specifically, the storage unit 78 stores a first suspicion probability table and a second suspicion probability table. The storage unit 78 may store information other than the above-mentioned information, such as information temporarily required for processing of the managed device 70.

[0052] (operation) Next, the operation of the management system 1 according to this embodiment will be described with reference to Figs. 9 to 11. The operation of the management system 1 is broadly divided into a suspect package notification process, a weight coefficient transmission process, and a suspicion probability table update process. The suspect package notification process and the suspicion probability table update process are operations of the managed device 70. The weight coefficient calculation process is an operation of the management device 10. Fig. 9 is a diagram showing an example of the operation of the suspect package notification process according to the present disclosure. Fig. 10 is a diagram showing an example of the operation of the weight coefficient transmission process according to the present disclosure. Fig. 11 is a diagram showing an example of the operation of the suspicion probability table update process according to the present disclosure.

[0053] [Suspicious package notification processing] First, the operation of the suspected package notification process performed by the managed device 70 will be described with reference to FIG.

[0054] First, the fault detection unit 71 detects that a fault has occurred in any of the plurality of packages 79 (step S71). Furthermore, the fault detection unit 71 identifies the fault type of the fault that has occurred (step S72).

[0055] Next, the suspected package estimation unit 72 uses the second suspicion probability table to estimate, as the suspected package, the package with the highest suspected probability value for the fault type identified in step S12 (step S73).

[0056] Next, the fault information transmitting unit 73 transmits the fault information to the management device 10 (step S74). The fault information includes the fault type identified in step S72 and suspected package information, which is information about the suspected package estimated in step S73.

[0057] Next, the output unit 77 transmits a control signal for notifying the administrator terminal 80 of the fault information (step S75). For example, the control signal for notifying the fault information is a control signal for outputting identification information of the managed device 70 in which the fault has occurred and text information about the fault information. The suspected package notification process ends with the processing of step S75.

[0058] [Weighting coefficient transmission process] Next, the operation of the weighting coefficient transmission process by the management device 10 will be described with reference to Fig. 10. The weighting coefficient transmission process starts when fault information is received from the managed device 70.

[0059] First, the fault information acquisition unit 11 acquires fault information transmitted from the managed device 70 (step S11).

[0060] Next, the acquisition count update unit 12 updates the acquisition count table of the suspected package using the fault information acquired in step S11 (step S12). The acquisition count update unit 12 updates the acquisition count table by counting the number of times each piece of fault information acquired in step S11 has been acquired.

[0061] Next, the weighting factor specifying unit 13 refers to the weighting factor table and specifies a weighting factor according to the number of times the fault has been acquired, which has been updated in step S12 (step S13).

[0062] Next, the destination specification unit 14 refers to the package management ledger to specify the managed device having the suspicious package (step S14).

[0063] Next, the transmitter 15 transmits the weighting coefficients identified in step S13 and the fault information acquired in step S11 to all managed devices 70 identified in step S14 (step S15). The weighting coefficient transmission process ends with the process of step S15.

[0064] [Suspect probability table update process] Next, the operation of the suspicion probability table update process by the managed device 70 will be described with reference to Fig. 11. The suspicion probability table update process starts when fault information and weighting coefficients are received from the management device 10.

[0065] First, the weighting factor acquisition unit 74 acquires the fault information and the weighting factor transmitted from the management device 10 (step S76).

[0066] Next, the suspicion probability calculation unit 75 calculates the suspicion probability to be stored in the second suspicion probability table using the fault information and weighting coefficient acquired in step S76 (step S77). The suspicion probability calculation unit 75 sets the value of the suspicion probability of the package that matches the fault information, stored in the first suspicion probability table, as an initial value, and calculates the suspicion probability by multiplying the initial value by the weighting coefficient acquired in step S76. The suspicion probability calculation unit 75 may perform calibration so that the total value of the suspicion probability for each fault type becomes a specified value (e.g., 100%).

[0067] Next, the suspicion probability table update unit 76 updates the values ​​of the second suspicion probability table using the suspicion probabilities calculated by the suspicion probability calculation unit 75 (step S78).

[0068] Next, the output unit 77 transmits information indicating that the suspicion probability table has been updated to the administrator terminal 80 (step S79). The suspicion probability table update process ends with the process of step S79.

[0069] As described above, the management device of this embodiment includes a fault information acquisition unit, an acquisition count update unit, a weighting factor determination unit, a transmission destination determination unit, and a transmission unit. The fault information acquisition unit acquires, as fault information, suspected package information, which is information about a suspect package, and a fault type, from a managed device that has detected a fault and estimated a suspect package, which is a package that is estimated to have caused the fault, in its own device. A package is a shipping unit of software or hardware installed in a managed device. The acquisition count update unit counts the number of times each piece of fault information has been acquired. The weighting factor determination unit determines a weighting factor according to the number of acquisitions. The transmission destination determination unit identifies other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspected package information. The transmission unit transmits the weighting factor and fault information to the identified other managed devices. The weighting factor is a weight that is used by the managed device to estimate a suspect package and is multiplied by a suspicion probability that is preset according to the combination of each fault type and each package. The suspected probability indicates the probability that a package is a suspected package when a fault of a fault type is detected.

[0070] The management device of this embodiment, having the above-described configuration, can improve the accuracy of suspect package identification. Typically, suspect package identification is performed using the failure history of a single information processing device being monitored. Therefore, even if a failure occurs in another information processing device equipped with the same type of package, the failure history cannot be used to identify the suspect package. When a failure occurs in one of the managed devices, the management device of this embodiment identifies the managed device that has the suspect package and transmits a weighting factor corresponding to the updated number of failures to all managed devices that have the suspect package. In other words, the managed device can acquire a weighting factor that takes into account the failure history of devices other than the failed managed device. In other words, the management device of this embodiment can improve the accuracy of suspect package identification.

[0071] The managed device of this embodiment includes a weighting coefficient acquisition unit, a suspected probability calculation unit, a fault detection unit, a suspected package estimation unit, and a fault information transmission unit. The weighting coefficient acquisition unit acquires fault information and weighting coefficients transmitted from the management device. The suspected probability calculation unit calculates the suspected probability by multiplying the suspected probability that matches the acquired fault information by the acquired weighting coefficient. The fault detection unit detects that a fault has occurred in the managed device and detects the fault type. The suspected package estimation unit estimates a suspected package using the detected fault type and the calculated suspected probability. The fault information transmission unit transmits the fault type and suspected package information of the estimated suspected package to the management device. The managed device has multiple packages.

[0072] The managed device according to the present embodiment has the above-described configuration, thereby improving the accuracy of suspect package estimation. Generally, suspect packages are estimated using a failure history that occurred within a single information processing device to be monitored. Therefore, even if a failure occurs in another information processing device equipped with the same type of package, the failure history cannot be used to estimate the suspect package. The weight acquired by the weight coefficient acquisition unit is a weight coefficient that takes into account the failure history of devices other than the managed device in which the failure occurred. The managed device according to the present disclosure is configured to use this weight coefficient to update the suspicion probability used to estimate the suspect package. Furthermore, the managed device according to the present disclosure is configured to estimate the suspect package using the updated suspicion probability. In other words, the managed device calculates the suspicion probability for estimating the suspect package by taking into account the failure history of other managed devices. Therefore, the managed device according to the present embodiment can improve the accuracy of suspect package estimation.

[0073] In one aspect of this embodiment, the weighting coefficient identification unit identifies the weighting coefficient using a weighting coefficient table in which predetermined weighting coefficients are stored according to the number of acquisitions. The weighting coefficient stored in the weighting coefficient table is smaller the fewer the number of acquisitions, and is larger the more the number of acquisitions. As described above, the weighting coefficient is a weight by which the managed device multiplies the suspicion probability used when inferring the suspected package. By using a weighting coefficient that is smaller the fewer the number of acquisitions and larger the more the number of acquisitions, the managed device can set a higher suspicion probability for packages with a higher number of failure acquisitions and a lower suspicion probability for packages with a lower number of failure acquisitions. This can improve the accuracy of inferring suspected packages.

[0074] In one aspect of this embodiment, the destination specification unit specifies managed devices that have a suspicious package using a package management ledger that stores a list of managed devices that have a package. The information stored in the package management ledger is updated at regular intervals via an input unit on the administrator terminal. The management device of one aspect of this embodiment can use the destination specification unit to specify all managed devices that have a suspicious package. As a result, even if a failure occurs in another information processing device that has the same type of package, the management device of this embodiment can use the failure occurrence history to identify the suspicious package. In other words, the management device of one aspect of this embodiment can improve the accuracy of identifying suspicious packages.

[0075] In one aspect of this embodiment, the suspect package information includes package identification information of the suspect package. The suspect package information further includes at least one of the manufacturing date of the suspect package, the revision date of the suspect package, or the revision number of the suspect package. If the suspect package information includes the manufacturing date, the acquisition count update unit counts the number of times a fault has been detected for each manufacturing date of the package. Similarly, if the suspect package information includes the revision number, the acquisition count update unit counts the number of times a fault has been detected for each revision number of the package. The number of times a fault has been detected for a package may vary depending on its manufacturing date or revision number. The management device of one aspect of this embodiment counts the number of times a fault has been detected for each of these pieces of information, thereby further improving the accuracy of estimating suspect packages.

[0076] (Variation) The acquisition count table 741 may store the fault detection rate instead of the number of times a fault is detected. When the acquisition count table 741 is configured to store the fault detection rate, the weighting coefficient table 742 also stores the fault detection rate instead of the number of times a fault is detected. The fault detection rate is the ratio of the number of times a fault is detected to the number of shipped packages. In this case, the acquisition count update unit 12 calculates the detection rate, which is the ratio of the number of times a fault is detected to the number of shipped suspect packages. The weighting coefficient identification unit 13 identifies a weighting coefficient using the weighting coefficient table 742, which stores a weighting coefficient determined in advance according to the detection rate. For example, by outputting the acquisition count table 741 including the fault detection rate to the administrator terminal 80, the administrator can intuitively identify packages in which a large number of faults occur. This makes it easier to perform processes such as revising packages in which a large number of faults occur, thereby improving the convenience of the system.

[0077] (Second embodiment) In this embodiment, a management device 20 will be described, which has a simplified configuration of the management device according to the first embodiment. In the following description, the same parts as those in the first embodiment will not be described as appropriate.

[0078] (composition) Next, the configuration of a management device according to this embodiment will be described with reference to the drawings. Fig. 12 is a block diagram showing an example of the configuration of a management device according to the present disclosure. The management device 20 includes a fault information acquisition unit 21, an acquisition count update unit 22, a weighting coefficient determination unit 23, a transmission destination determination unit 24, and a transmission unit 25.

[0079] The fault information acquisition unit 21 acquires, as fault information, suspected package information, which is information about a suspect package, and a fault type from a managed device 70 that has detected a fault and estimated a suspect package, which is a package that is estimated to have caused the fault, in its own device. A package is a shipping unit of software or hardware installed in each managed device 70. The acquisition count update unit 22 counts the number of times each piece of fault information has been acquired. The weighting coefficient identification unit 23 identifies a weighting coefficient according to the number of acquisitions. The transmission destination identification unit 24 identifies other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspected package information. The transmission unit 25 transmits the weighting coefficient and fault information to the identified other managed devices. The weighting coefficient is a weight that is multiplied by a suspicion probability that is preset according to the combination of each fault type and each package, and is used by each managed device 70 when estimating a suspect package.

[0080] (operation) Next, an example of the operation of the management device according to this embodiment will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of the operation of the management device according to the present disclosure.

[0081] First, the fault information acquisition unit 21 acquires suspected package information, which is information about the suspected package, and the fault type as fault information from the managed device 70 that has detected a fault in its own device and estimated a suspected package, which is a package that is suspected to have caused the fault (step S21).

[0082] Next, the acquisition count update unit 22 counts the number of times each piece of fault information has been acquired (step S22).

[0083] Next, the weighting factor specifying unit 23 specifies a weighting factor according to the number of times of acquisition (step S23).

[0084] Next, the destination specification unit 24 specifies other managed devices that have the suspicious package using the package management ledger that stores a list of managed devices that have the package and the suspicious package information (step S24).

[0085] Next, the transmitter 25 transmits the weighting coefficient and the fault information to the other identified managed devices (step S25).

[0086] When a failure is detected in one of the managed devices, the management device of this embodiment transmits a weighting factor corresponding to the number of times each piece of failure information is acquired to the managed device that has the suspect package. The weighting factor is a weight that is used by the managed device to estimate the suspect package and is multiplied by a predetermined suspicion probability corresponding to the combination of each failure type and each package. In other words, the management device of this embodiment can improve the accuracy of estimating the suspect package.

[0087] (Hardware configuration) The functions of each of the components according to each of the embodiments of the present disclosure described above can be realized not only as hardware but also as a computer device or firmware under program control.

[0088] 14 is a diagram showing an example of a hardware configuration in which an information generation device according to the present disclosure is realized by a computer device 90 including a processor. The information generation device of each embodiment is realized by the computer device 90. As shown in FIG. 14, the computer device 90 includes a processor 91, a memory 92, a storage device 93 such as a hard disk for storing programs, an input / output interface 94 for connecting input devices and output devices, and a communication interface 95 for connecting to a network.

[0089] The processor 91 loads a program (instructions) stored in a storage device 93 or the like into the memory 92. For example, the program is a software program for executing the control and processing in the present disclosure. The processor 91 executes the program loaded into the memory 92. The processor 91 executes the program to execute the control and processing in the present disclosure.

[0090] The storage device 93 may be, for example, an optical disk, a flexible disk, a magneto-optical disk, an external hard disk, or a semiconductor memory. Some storage media in the storage device are non-volatile storage devices, and the programs are recorded therein. The programs may also be downloaded from an external computer (not shown) connected to a communication network.

[0091] The input device connected to the input / output interface 94 is realized by, for example, a mouse or a keyboard, and is used for input operations. Similarly, the output device connected to the input / output interface 94 is realized by, for example, a display, and is used for displaying and checking output results.

[0092] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0093] Some or all of the above embodiments can also be described as follows:

[0094] (Appendix 1) a fault information acquisition means for acquiring, as fault information, suspected package information, which is information about the suspected package, and a fault type, from a managed device that has detected a fault and estimated a suspected package, which is a package that is estimated to have caused the fault, in its own device; an acquisition count update means for counting the number of times each piece of fault information has been acquired; a weighting coefficient specifying means for specifying a weighting coefficient according to the number of times of acquisition; a destination specifying means for specifying other managed devices having the suspicious package using a package management ledger storing a list of managed devices having the package and the suspicious package information; a transmitting means for transmitting the weighting coefficient and the fault information to the identified other managed device; Equipped with The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by each of the managed devices when estimating the suspect package, and is multiplied by a suspect probability set in advance according to a combination of each failure type and each package. (Appendix 2) The management device according to claim 1, wherein the weighting factor specifying means specifies the weighting factor using a weighting factor table in which predetermined weighting factors are stored according to the number of times of acquisition. (Appendix 3) The management device according to Supplementary Note 2, wherein the weighting coefficients stored in the weighting coefficient table are smaller as the number of times of acquisition is smaller, and are larger as the number of times of acquisition is larger. (Appendix 4) 2. The management device according to claim 1, wherein the suspect package information includes package identification information of the suspect package. (Appendix 5) 5. The management device according to claim 4, wherein the suspect package information further includes at least one of a manufacturing date of the suspect package, a revision date of the suspect package, or a revision number of the suspect package. (Appendix 6) the managed device has a plurality of the packages, The management device according to claim 1, wherein the suspicion probability indicates the probability that each of the plurality of packages is the suspect package when a failure of the failure type is detected. (Appendix 7) The acquisition count update means calculates a detection rate, which is a rate of the acquisition count to the number of shipments of the suspect package, and The management device according to claim 1, wherein the weighting factor specifying means specifies the weighting factor using a weighting factor table in which weighting factors determined in advance according to the detection ratio are stored. (Appendix 8) A management device according to any one of Supplementary Notes 1 to 7, and a plurality of said packages; a weighting factor acquisition means for acquiring the weighting factor and the fault information transmitted from the management device; a suspicion probability calculation means for calculating the suspicion probability by multiplying the suspicion probability that matches the acquired fault information by the acquired weighting coefficient; a fault detection unit that detects that a fault has occurred in the package and detects the type of the fault; a suspect package estimation means for estimating the suspect package using the detected fault type and the calculated suspect probability; a fault information transmitting means for transmitting the fault type and the suspected package information of the suspected package to the management device; A managed device having A management system comprising: (Appendix 9) The computer Obtaining, as fault information, suspected package information, which is information about the suspected package, and a fault type, from a managed device that has detected a fault and estimated a suspected package, which is a package that is estimated to have caused the fault, in its own device; Counting the number of times each piece of fault information is acquired; determining a weighting coefficient according to the number of times of acquisition; identifying other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspect package information; transmitting the weighting coefficient and the fault information to the identified other managed device; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by each of the managed devices when estimating the suspect package, and is multiplied by a suspect probability set in advance according to a combination of each failure type and each package. (Appendix 10) On the computer, A process of acquiring suspected package information, which is information about the suspected package, and a type of failure as failure information from a managed device that has detected a failure and estimated a suspected package, which is a package that is estimated to have caused the failure, in its own device; a process of counting the number of times each piece of fault information is acquired; A process of determining a weighting coefficient according to the number of times of acquisition; a process of identifying other managed devices having the suspect package using a package management ledger that stores a list of managed devices having the package and the suspect package information; causing the identified other managed device to execute a process of transmitting the weighting coefficient and the fault information; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by the managed device when estimating the suspected package, and is multiplied by a suspected probability set in advance according to a combination of each fault type and each package.

[0095] In addition, in the above appendices, some or all of the configurations described in appendices 2 to 7 that are dependent on appendices 1 may also be dependent on appendices 9 and 10 in the same dependent relationship as appendices 2 to 7. Furthermore, not limited to appendices 1, 9, and 10, some or all of the configurations described as appendices may be made dependent on various hardware, software, various recording means for recording software, or systems, within the scope of each of the above-mentioned embodiments. [Explanation of symbols]

[0096] 10, 20 Management device 11, 21 Fault information acquisition section 12, 22 Acquisition count update section 13, 23 Weighting coefficient determination unit 14, 24 Destination specification part 15, 25 Transmitter 16 Memory section 70 Managed device 71 Fault detection unit 72 Suspect Package Estimation Department 73 Fault information transmission unit 74 Weighting coefficient acquisition unit 75 Suspect Probability Calculation Unit 76 Suspect Probability Table Update Section 77 Output section 78 Memory section 79 packages 80 Administrator terminal 90 Computer Equipment 91 processors 92 memory 93 Storage device 94 Input / Output Interface 95 Communication Interface

Claims

1. a fault information acquisition means for acquiring, as fault information, suspected package information, which is information about the suspected package, and a fault type, from a managed device that has detected a fault and estimated a suspected package, which is a package that is estimated to have caused the fault, in its own device; an acquisition count update means for counting the number of times each piece of fault information has been acquired; a weighting coefficient specifying means for specifying a weighting coefficient according to the number of times of acquisition; a destination specifying means for specifying other managed devices having the suspicious package using a package management ledger storing a list of managed devices having the package and the suspicious package information; a transmitting means for transmitting the weighting coefficient and the fault information to the identified other managed device; Equipped with The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by each of the managed devices when estimating the suspect package, and is multiplied by a suspect probability set in advance according to a combination of each failure type and each package.

2. The management device according to claim 1 , wherein the weighting factor specifying means specifies the weighting factor using a weighting factor table in which predetermined weighting factors are stored according to the number of times of acquisition.

3. The management device according to claim 2 , wherein the weighting coefficients stored in the weighting coefficient table have smaller values ​​as the number of times of acquisition decreases and larger values ​​as the number of times of acquisition increases.

4. The management device according to claim 1 , wherein the suspect package information includes package identification information of the suspect package.

5. 5. The management device according to claim 4, wherein the suspect package information further includes at least one of a manufacturing date of the suspect package, a revision date of the suspect package, and a revision number of the suspect package.

6. the managed device has a plurality of the packages, The management device according to claim 1 , wherein the suspicion probability indicates a probability that each of the plurality of packages is the suspect package when a failure of the failure type is detected.

7. The acquisition count update means calculates a detection rate, which is a rate of the acquisition count to the number of shipments of the suspect package, and 2. The management device according to claim 1, wherein the weighting factor specifying means specifies the weighting factor using a weighting factor table in which weighting factors determined in advance according to the detection rate are stored.

8. A management device according to any one of claims 1 to 7, and a plurality of said packages; a weighting factor acquisition means for acquiring the weighting factor and the fault information transmitted from the management device; a suspicion probability calculation means for calculating the suspicion probability by multiplying the suspicion probability that matches the acquired fault information by the acquired weighting coefficient; a fault detection unit that detects that a fault has occurred in the package and detects the type of the fault; a suspect package estimation means for estimating the suspect package using the detected fault type and the calculated suspect probability; a fault information transmitting means for transmitting fault information including the fault type and the suspected package information of the suspected package to the management device; A managed device having A management system comprising:

9. The computer Obtaining, as fault information, suspected package information, which is information about the suspected package, and a fault type, from a managed device that has detected a fault and estimated a suspected package, which is a package that is estimated to have caused the fault, in its own device; Counting the number of times each piece of fault information is acquired; determining a weighting coefficient according to the number of times of acquisition; identifying other managed devices that have the suspect package using a package management ledger that stores a list of managed devices that have the package and the suspect package information; transmitting the weighting coefficient and the fault information to the identified other managed device; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by each of the managed devices when estimating the suspect package, and is multiplied by a suspect probability set in advance according to a combination of each failure type and each package.

10. On the computer, A process of acquiring suspected package information, which is information about the suspected fault package, and a fault type as fault information from a managed device that has detected a fault and estimated a suspected package, which is a package that is estimated to have caused the fault, in its own device; a process of counting the number of times each piece of fault information is acquired; A process of determining a weighting coefficient according to the number of times of acquisition; a process of identifying other managed devices having the suspect package using a package management ledger that stores a list of managed devices having the package and the suspect package information; causing the identified other managed device to execute a process of transmitting the weighting coefficient and the fault information; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight used by each managed device when estimating the suspected package, and is multiplied by a suspected probability set in advance according to a combination of each fault type and each package.

Images