Management device, management system, management method, and program

Abstract

A management device that enables improvement of the accuracy of estimating suspect packages. [Solution] A management device comprising a fault information acquisition unit that acquires suspect package information and fault types 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, an acquisition count update unit that counts the number of times each fault information is acquired, a weighting coefficient identification unit that identifies a weighting 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 and the suspect package information, and a transmission unit that transmits the weighting coefficient and fault information to the other 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 used by each managed device to infer a suspect package.

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 technique for notifying a maintenance manager of the package in which a fault has occurred when a fault occurs in an information processing device having multiple packages. When a fault occurs in which the package in which the fault has occurred cannot be identified, a suspect package is estimated based on the history of past fault occurrences, as described in Patent Document 1. A suspect package is a package that is estimated (suspected) to have caused a fault. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-137806 A Summary of the Invention [Problem to be solved by the invention]

[0004] In general, the fault occurrence history is a history of faults that occurred in a single information processing device that is the monitoring target. Therefore, even if a fault occurs in another information processing device having the same package, the fault occurrence history cannot be used to infer the suspect package. In order to improve the accuracy of inferring the suspect package, it is desirable to be able to use fault information in the 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 and a fault type, which are information about a suspect package, 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 a fault, an acquisition count update unit that counts the number of times each fault information is acquired, a weighting coefficient identification unit that identifies a weighting 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 information of managed devices that have the package and the suspect package information, and a transmission unit that transmits the weighting coefficient and the fault information to the other identified managed devices, wherein the 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 suspect probability that is preset according to a combination of each fault type and each package, and 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 and a fault type, which are information about the suspect package, 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, counts the number of times each piece of fault information is acquired, determines a weighting coefficient according to the number of times it is acquired, 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 transmits the weighting coefficient and the 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 a 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 embodiment of the present disclosure causes a computer to execute the following processes: acquire suspect package information and a fault type, which are information about a suspect package, as fault information from a managed device that has detected a fault in its own device and inferred a suspect package, which is a package that is presumed to have caused the fault; count the number of times each piece of fault information has been acquired; identify a weighting coefficient according to the number of times it has been 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 transmit the weighting coefficient and the 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 a weighting coefficient is a weight that is multiplied by a suspect probability that is preset according to a combination of each fault type and each package, and is used by each managed device when inferring a suspect package. Effect 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 description 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. [Diagram 2] FIG. 2 is a block diagram showing an example of a configuration of a management device according to the present disclosure. [Diagram 3] 13 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. [Diagram 5] 1 is an example of a package management ledger according to the present disclosure. [Figure 6] 1 is a block diagram showing an example of a configuration of a managed device according to the present disclosure. [Figure 7] FIG. 2 is a diagram showing an example of a first suspicion probability table according to the present disclosure. [Figure 8]FIG. 13 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 an 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 an operation of a managed device according to the present disclosure. [Figure 12] FIG. 2 is a block diagram showing 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 PREFERRED EMBODIMENTS

[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 explain 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 fault is detected in any of a plurality of managed devices that are managed, the management system according to this embodiment transmits a weighting factor according to the number of times the fault has been acquired to all managed devices having a suspect package in which the fault is suspected. The managed devices that receive the weighting factor update a suspicion probability table for estimating a suspect package by multiplying the weighting factor by the suspicion probability used when estimating a suspect package.

[0014] (overview) 1 is a conceptual diagram for explaining an overview of a management system according to the present disclosure. The 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. n is a natural number of 2 or more. 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 device 70. When a fault occurs in any of the managed devices 70-1 to 70-n, the management device 10 receives a fault type and suspect package information from the managed device. The fault type is a classification of faults according to the behavior and cause of the detected fault. The suspect package information is information on a suspect package that is generated when a fault is detected in the managed device 70-n. When the management device 10 receives the fault type and the suspect package information, it counts the number of times each fault information is acquired. The management device 10 specifies a weighting factor according to the counted number of times of acquisition. Furthermore, the management device 10 specifies a managed device 70 having a suspect package from among the managed devices 70-1 to 70-n. The management device 10 transmits the calculated weighting factor, the suspect package information, and the fault type to all of the specified managed devices 70.

[0017] [Managed device] The managed device 70 is an information processing device communicatively connected to the management device 10. 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 capable of communicating with the management device 10, the managed device 70 may be a stationary terminal device, a notebook terminal device, a tablet, a portable terminal device, or the like.

[0018] The managed device 70 has a plurality of packages. When a fault occurs in the managed device 70, the managed device 70 detects the occurrence of the fault and detects the type of fault. Furthermore, the managed device 70 identifies a suspect package using a suspicion probability table. The suspicion probability table is a table that indicates, for each of a plurality of packages held by the managed device 70, a suspicion probability that is the probability that a fault has occurred in that package when a fault of a certain fault type occurs. The managed device 70 transmits the identified fault type and suspect package information that is information related to the identified suspect 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 terminal] The administrator terminal 80 is a terminal device operated by a maintenance manager of the managed device 70. The administrator terminal 80 has an output unit (not shown). For example, the output unit is realized 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 transmitted from the managed device 70 via the output unit. The administrator terminal 80 has 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 with reference to 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 acquiring unit 11 acquires fault information transmitted from the managed device 70. The fault information includes a fault type and suspected package information.

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

[0025] The suspect package information is information relating to a suspect package, which is a package in which a fault is presumed to have occurred. The suspect package information is generated by the managed device 70 when a fault in the managed device 70 is detected. The suspect package information includes at least package identification information of the suspect package. The package identification information is information for uniquely identifying the suspect package. The package identification information is, for example, a UUID (Universally Unique Identifier) ​​or the like. The 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 also updates the acquisition count table for suspect packages using the counting results. 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 fault information. FIG. 3 is a diagram showing an example of the acquisition count table in the present disclosure. In the example of FIG. 3, "Fault A" and "Fault B" are fault types, "PKG-A" is package identification information, "REV-1" to "REV-4" are revision numbers, "manufacturing time a" to "manufacturing time d" are manufacturing times, and the numbers in the table indicate the number of acquisitions. In the example of FIG. 3, the acquisition count table is stored in table format for each package identification information. The acquisition count table 741-1 is an acquisition count table that records the number of times that a fault of PKG-A has been acquired. For example, in the example of FIG. 3, the number of acquisitions 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 time is "manufacturing time a" is 10.

[0028] A specific example of the acquisition count update unit 12 updating the number of times a fault is 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 a suspect package is PKG-A, the production date is production 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 specification unit 13 uses the weighting factor table to specify a weighting factor according to the number of times the fault has been acquired, updated by the number of times the fault has been acquired update unit 12. The weighting factor is a weight by which the suspected probability of the package is multiplied. The suspected probability of the package will be described later.

[0030] A specific example of the weighting coefficient specification unit 13 specifying the 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 acquired. The weighting coefficient is set to a smaller value the fewer the number of times a fault has been acquired, and a larger value the more the number of times a fault has been acquired.

[0031] For example, suppose that the fault information acquisition unit 11 acquires fault information in which the package identification information of a suspect package is PKG-A, the production date is production date a, and the revision number is REV-A from the managed device 70. 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 suspicious package information and the package management register to specify the managed device having the suspicious 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. Information stored in the package management ledger is updated at regular 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 identifies the managed devices 70 having the suspect package by using the fault information acquired by the fault information acquisition unit 11. For example, it is assumed that the fault information acquisition unit 11 acquires fault information of 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 having the suspect package are "managed device 70-1" and "managed device 70-6".

[0035] The transmitting unit 15 transmits the identified weighting factor and the acquired fault information to the managed device 70 having the suspect package. For example, it is assumed that the fault information acquiring 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 time is manufacturing time a, and the revision number is REV-A. It is also assumed that the acquisition count updating unit 12 updates the number of times that the package has been acquired as a fault to "11". It is also assumed that the weighting factor identifying unit 13 identifies the weighting factor as "1.5". It is also assumed that the destination identifying unit 14 identifies the managed devices having the suspect package as "managed device 70-1" and "managed device 70-6". In this case, the transmitting unit 15 transmits the weighting factor "1.5" identified by the weighting factor identifying unit 13 and the fault information acquired by the fault information acquiring unit 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 with reference to 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 a plurality of 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 simply be referred to as packages 79.

[0038] The fault detection unit 71 detects that a fault has occurred in any of the multiple packages 79 that the managed device 70 has. The fault detection unit 71 also identifies the fault type of the detected fault. The fault detection unit 71 detects the fault and the fault type by 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 fault type by a known method, for example, by 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 suspected probability table. The suspected probability table is a table that indicates, for each of multiple packages in the managed device 70, the suspected probability, which is the probability that a fault of a certain fault type is estimated to have occurred in that package.

[0040] The suspicion probability table includes 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 with reference to Figs. 7 and 8.

[0041] FIG. 7 is a diagram showing an example of a first suspicion probability table in the present disclosure. The first suspicion probability table is a table in which the initial value of the suspicion probability is stored. The value stored in the first suspicion probability is predetermined. The first suspicion probability table is referred to when the suspicion probability is updated by the suspicion probability table update unit 76. FIG. 8 is a diagram showing an example of a second suspicion probability table in the present disclosure. The second suspicion probability table is a table in which the value of the first suspicion probability table is multiplied by the weighting factor received from the management device 10. The second suspicion probability table is referred to when the suspect package estimation unit 72 estimates a suspect package. The value stored in the second suspicion probability table is updated every time a weighting factor is received from the management device 10. On the other hand, the value stored in the first suspicion probability table does not change from the predetermined value.

[0042] The suspected package estimation unit 72 estimates a suspected package using the second suspected probability table. The suspected package estimation unit 72 estimates the package with the highest suspected probability for the fault type identified by the fault detection unit 71 as the suspected package. For example, assume that the fault detection unit 71 identifies the fault type as "fault A." In this case, the suspected package estimation unit 72 refers to the second suspected probability table 182 and estimates "PKG-A," which is the package with the highest suspected 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 the weighting factor 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 matching 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, first, the suspicion probability calculation unit 75 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] When the total value of the suspicion probability for each fault type does not become the specified value by multiplying the weight coefficient, the suspicion probability calculation unit 75 may perform calibration so that the total value becomes the specified value. For example, when the suspicion probability is a percentage, the suspicion probability may be multiplied by a predetermined coefficient so that the total value of the suspicion probability for each fault type becomes 100%. For example, in the second suspicion probability table shown in FIG. 8, the total value 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 value to 100% by multiplying each suspicion probability by 1.25. After the 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 value of the suspicion probability stored in the second suspicion probability table for the corresponding package.

[0049] The output unit 77 transmits a control signal for notifying 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 a fault has occurred and text information of the fault information on a display screen of the administrator terminal 80. Alternatively, the output unit 77 transmits to the administrator terminal 80 a control signal for outputting audio information of the identification information of the managed device 70 in which a fault has occurred and the fault information on a speaker of the administrator terminal 80. The output unit 77 may output a control signal for displaying (notifying) information indicating the occurrence of a fault and the fault information on a display screen (not shown) or a speaker (not shown) of 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. In addition, 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 information necessary for the 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 the 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 weighting 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 weighting 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 weighting 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 process] 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 failure detection unit 71 detects that a failure has occurred in any of the multiple packages 79 (step S71). Furthermore, the failure detection unit 71 identifies the type of the failure that has occurred (step S72).

[0055] Next, the suspected package estimation unit 72 estimates, using the second suspected probability table, the package having the highest suspected probability value for the fault type identified in step S12 as the suspected package (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 on 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 of 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 acquiring 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 acquisitions for each fault information acquired in step S11.

[0061] Next, the weighting factor specification 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 transmitting unit 15 transmits the weighting coefficients identified in step S13 and the fault information acquired in step S11 to all the managed devices 70 identified in step S14 (step S15). The weighting coefficient transmission process ends with the process of step S15.

[0064] [Suspicion 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 the failure 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 matching 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 manager 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 identification unit, a transmission destination identification unit, and a transmission unit. The fault information acquisition unit acquires, as fault information, suspect package information, which is information about a suspect package, and a fault type, from a managed device that has detected a fault in its own device and estimated a suspect package, which is a package estimated to have caused a fault. A package is a shipping unit of software or hardware to be mounted on a managed device. The acquisition count update unit counts the number of acquisitions for each fault information. The weighting factor identification unit identifies a weighting factor according to the number of acquisitions. The transmission destination identification unit identifies other managed devices that have a suspect package using a package management ledger that stores a list of managed devices that have a package and the suspect package information. The transmission unit transmits the weighting factor and the fault information to the identified other managed devices. The weighting factor is a weight that is multiplied by a suspect probability that is set in advance according to a combination of each fault type and each package, which is used when the managed device estimates a suspect package. The suspect probability indicates the probability that a package is a suspect package when a fault of a certain fault type is detected.

[0070] The management device in this embodiment has the above-mentioned configuration, and thus can improve the accuracy of estimating a suspect package. In general, the estimation of a suspect package is performed using a failure occurrence history that occurs in 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 occurrence history cannot be used to estimate a suspect package. When a failure occurs in any of the managed devices, the management device in this embodiment identifies the managed device having the suspect package and transmits a weighting coefficient according to the updated number of times the failure has been acquired to all managed devices having the suspect package. In other words, the managed device can acquire a weighting coefficient that takes into account the failure occurrence history of devices other than the managed device in which the failure occurred. In other words, the management device in this embodiment can improve the accuracy of estimating a suspect package.

[0071] The managed device of this embodiment includes a weighting factor acquisition unit, a suspected probability calculation unit, a fault detection unit, a suspected package estimation unit, and a fault information transmission unit. The weighting factor acquisition unit acquires fault information and weighting factors transmitted from the management device. The suspected probability calculation unit calculates the suspected probability by multiplying the suspected probability matching the acquired fault information by the acquired weighting factor. The fault detection unit detects that a fault has occurred in the managed device and detects a 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 a plurality of packages.

[0072] The managed device in the present embodiment has the above-mentioned configuration, and thus can improve the accuracy of estimating a suspect package. In general, the suspect package is estimated using a failure history that occurred in 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 in the present disclosure has a configuration that uses this weight coefficient to update the suspect probability used to estimate the suspect package. Furthermore, the managed device in the present disclosure has a configuration that uses the updated suspect probability to estimate the suspect package. In other words, the managed device calculates the suspect probability for estimating the suspect package by taking into account the failure history of other managed devices. Therefore, the managed device in the present embodiment can improve the accuracy of estimating the suspect package.

[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 according to the number of acquisitions are stored. 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 multiplied by the suspected probability used by the managed device when estimating the suspected package. The weighting coefficient is smaller the fewer the number of acquisitions, and is larger the more the number of acquisitions, so that the managed device can set a high suspected probability for packages with a high number of acquired faults and a low suspected probability for packages with a low number of acquired faults. This can improve the estimation accuracy of the suspected package.

[0074] In one aspect of this embodiment, the destination specification unit specifies managed devices having a suspicious package using a package management ledger that stores a list of managed devices having a package. The information stored in the package management ledger is updated at regular time intervals via an input unit of the administrator terminal. The management device of one aspect of this embodiment can specify all managed devices having a suspicious package using the destination specification unit. 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 estimate the suspicious package. In other words, the management device of one aspect of this embodiment can improve the accuracy of estimating the suspicious package.

[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. When the suspect package information includes the manufacturing date, the acquisition count update unit counts the number of times a fault has been acquired for each manufacturing date of the package. Similarly, when the suspect package information includes the revision number, the acquisition count update unit counts the number of times a fault has been acquired for each revision number of the package. The number of times a fault has been acquired for a package may differ 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 acquired for each of these pieces of information, thereby further improving the accuracy of estimating suspect packages.

[0076] (Modification) The acquisition count table 741 may store a fault detection ratio instead of the fault acquisition count. In the case where the acquisition count table 741 is configured to store a fault detection ratio, the weighting factor table 742 also stores a fault detection ratio instead of the fault acquisition count. The fault detection ratio is the ratio of the fault acquisition count to the number of shipments of the package. In this case, the acquisition count update unit 12 calculates the detection ratio, which is the ratio of the fault acquisition count to the number of shipments of the suspect package. The weighting factor specification unit 13 specifies the weighting factor using the weighting factor table 742 in which a weighting factor determined in advance according to the detection ratio is stored. For example, by outputting the acquisition count table 741 including the fault detection ratio to the administrator terminal 80, the administrator can intuitively grasp the package in which many faults occur. This makes it easier to perform a process such as revising a package in which many faults occur, thereby improving the convenience of the system.

[0077] Second embodiment In this embodiment, a management device 20 will be described, which is 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 the management device according to the present embodiment will be described with reference to the drawings. Fig. 12 is a block diagram showing an example of the configuration of the management device in 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 destination determination unit 24, and a transmission unit 25.

[0079] The fault information acquisition unit 21 acquires, as fault information, suspect package information, which is information about a suspect package, and a fault type from a managed device 70 that has detected a fault in its own device and estimated a suspect package, which is a package that is estimated to have caused a fault. A package is a shipping unit of software or hardware that is installed in each managed device 70. The acquisition count update unit 22 counts the number of acquisitions for each fault information. The weighting factor identification unit 23 identifies a weighting factor according to the number of acquisitions. The transmission destination identification unit 24 identifies other managed devices that have a suspect package using a package management ledger that stores a list of managed devices that have a package and the suspect package information. The transmission unit 25 transmits the weighting factor and the fault information to the identified other managed devices. The weighting factor is a weight that is multiplied by a suspect probability that is set in advance according to a combination of each fault type and each package, which 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, as fault information, suspect package information, which is information about a suspect package, and a fault type from the managed device 70 that has detected a fault in its own device and estimated a suspect package, which is a package that is presumed 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 is 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 having the suspicious package using the package management ledger that stores a list of managed devices having the package and the suspicious package information (step S24).

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

[0086] When a fault is detected in any of the managed devices, the management device of this embodiment transmits a weighting coefficient according to the number of times each fault information is acquired to the managed device having the suspect package. The weighting coefficient is a weight that is multiplied by a suspect probability that is set in advance according to each combination of each fault type and each package, and is used when the managed device infers a suspect package. In other words, the management device of this embodiment can improve the accuracy of inferring a suspect package.

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

[0088] Fig. 14 is a diagram showing an example of a hardware configuration in which an information generating device according to the present disclosure is realized by a computer device 90 including a processor. The information generating 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 a 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 is, for example, an optical disk, a flexible disk, a magneto-optical disk, an external hard disk, or a semiconductor memory. A part of the storage device is a storage medium that is a non-volatile storage device, and the program is recorded therein. The program 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, a keyboard, etc., and is used for input operations. Similarly, the output device connected to the input / output interface 94 is realized by, for example, a display, etc., 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-mentioned embodiments. Various modifications that can be understood by a person 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 appropriately combined with other embodiments.

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

[0094] (Appendix 1) a fault information acquiring means for acquiring, as fault information, suspected package information, which is information related to 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 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 is acquired; a weighting factor determining means for determining a weighting factor according to the number of times of acquisition; a destination specifying means for specifying other managed devices having the suspect package by using a package management ledger storing a list of managed devices having the package and the suspect package information; a transmitting means for transmitting the weighting coefficient and the fault information to the identified other managed devices; 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 by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when each managed device estimates the suspected package. (Appendix 2) The management device according to claim 1, wherein the weighting factor specification means specifies the weighting factor using a weighting factor table in which predetermined weighting factors are stored according to the number of acquisitions. (Appendix 3) The management device according to claim 2, wherein the weighting coefficient stored in the weighting coefficient table is smaller as the number of times the information is acquired is smaller, and is larger as the number of times the information is acquired 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, 2. The management device according to claim 1, wherein the suspicion probability indicates the probability that each of the plurality of packages is a suspect package when a failure of the failure type is detected. (Appendix 7) The acquisition count update means calculates a detection rate that is a rate of the acquisition count to the number of shipments of the suspect package, The management device according to claim 1, wherein the weighting factor specification means specifies the weighting factor using a weighting factor table in which predetermined weighting factors corresponding 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 by 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, suspect package information, which is information about the 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 the managed device; Counting the number of times each piece of fault information is acquired; A weighting factor is determined according to the number of times of acquisition. 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; Transmitting the weighting coefficient and the fault information to the identified other managed devices; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when each managed device estimates the suspected package. (Appendix 10) On the computer, A process of acquiring suspect package information, which is information related to the suspect package, and a type of failure from a managed device that has detected a failure and estimated a suspect package, which is a package that is estimated to have caused the failure, as failure information; 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 by using a package management ledger that stores a list of managed devices having the package and the suspect package information; a process of 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 by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when the managed device estimates the suspected package.

[0095] In addition, in the above appendices, some or all of the configurations described in appendices 2 to 7 that are subordinate to appendices 1 may also be subordinate to appendices 9 and 10 in the same subordinate relationship as appendices 2 to 7. Furthermore, not limited to appendices 1, 9, and 10, but within the scope of each of the above-mentioned embodiments, some or all of the configurations described as appendices may be subordinate to various hardware, software, various recording means for recording software, or systems. [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 Identification 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 Processor 92 Memory 93 Storage device 94 Input / Output Interface 95 Communication Interface

Claims

1. a fault information acquiring means for acquiring, as fault information, suspected package information, which is information related to 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 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 is acquired; a weighting factor determining means for determining a weighting factor according to the number of times of acquisition; a destination specifying means for specifying other managed devices having the suspect package by using a package management ledger storing a list of managed devices having the package and the suspect package information; a transmitting means for transmitting the weighting coefficient and the fault information to the identified other managed devices; 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 by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when each managed device estimates the suspected package.

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

3. The management device according to claim 2 , wherein the weighting coefficients stored in the weighting coefficient table are smaller as the number of times the information is acquired is smaller, and are larger as the number of times the information is acquired is larger.

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 that is a rate of the acquisition count to the number of shipments of the suspect package, 2 . The management device according to claim 1 , wherein the weighting factor specifying means specifies the weighting factor by using a weighting factor table in which predetermined weighting factors corresponding to the detection ratios 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 by 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 estimated suspected package to the management device; A managed device having A management system comprising:

9. The computer Obtaining, as fault information, suspect package information, which is information about the 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 the managed device; Counting the number of times each piece of fault information is acquired; A weighting factor is determined according to the number of times of acquisition. 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; Transmitting the weighting coefficient and the fault information to the identified other managed devices; The package is a shipping unit of software or hardware to be installed in each managed device, The weighting coefficient is a weight by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when each managed device estimates the suspected package.

10. On the computer, A process of acquiring suspected package information, which is information related to the suspected fault package, and a fault type as fault information from a managed device that has detected a fault in its own device and estimated a suspected package, which is a package that is estimated to have caused the fault; A process of counting the number of times each piece of fault information is acquired; A process of determining a weighting factor according to the number of times of acquisition; a process of identifying other managed devices having the suspect package by using a package management ledger that stores a list of managed devices having the package and the suspect package information; a process of 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 by which a suspected probability set in advance according to a combination of each fault type and each package is multiplied when each managed device estimates the suspected package.

Images