JP2014013529A - Fault management system, fault management method and fault management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a fault management system or the like for reducing cost for constructing the fault management system.SOLUTION: A fault management system 10 includes a diagnostic part 20 for reading a register value shown by a register 60 in electronic equipment 50 through a communication network 40, comparing the register value with a determination value representing a condition for issuing an instruction, selecting a specific state value among state values showing states of the electronic equipment 50 in accordance with the compared result, and outputting the specific state value, and a recovery part 30 for issuing a specific instruction to the electronic equipment in accordance with the specific state value.

Description

  The present invention relates to a failure management system in an electronic device.

  An electronic device may have a malfunction (hereinafter also referred to as “failure”). For example, a home gateway can be given as an example of an electronic device. In that case, in order to cope with the problem, the server needs to update the firmware in the electronic device from the outside. On the other hand, as the functions of electronic devices become diversified, the scale of firmware increases and the configuration of firmware becomes complicated. The cost of improving a malfunctioning firmware increases as the size and complexity of the firmware increases. Therefore, in a situation where the functions of the electronic device are diverse, it is difficult to quickly cope with the malfunction.

  In addition, when the electronic device detects that a problem has occurred inside, the electronic apparatus may have a function of notifying information about the problem that has occurred to the outside. In this case, the monitoring system monitors information notified from the electronic device, so that it is possible to collectively monitor failures that have occurred in the electronic device. In that case, each electronic device monitored by the monitoring system has a function for detecting a malfunction occurring in the electronic device.

  The device remote monitoring system disclosed in Patent Document 1 is connected to an electronic device via a communication network (for example, “Internet”). When the device remote monitoring system receives a notification notifying that a failure has occurred in the electronic device (hereinafter, referred to as “failure notification”), the device remote monitoring system reads the firmware version in the electronic device. Next, the device remote monitoring system determines a countermeasure method for the failure based on the version. On the other hand, the electronic device has a function of detecting that a failure has occurred in the electronic device and a function of notifying a failure to the outside.

  When the debug information notification device disclosed in Patent Document 2 detects that a failure has occurred in the electronic device, the debug information notification device outputs debug information related to the failure to the outside.

  When the failure location detection device disclosed in Patent Document 3 detects that a failure has occurred in the electronic device, the failure location detection device inspects the failure location.

JP 2007-257085 A JP 2004-013714 A JP 2010-226309 A

  In the failure management system described above, the electronic device needs to have a function of detecting a failure that has occurred in the electronic device. Therefore, each electronic device has a device that detects a failure (hereinafter, referred to as a “failure detection device”). However, the fact that each electronic device has a failure detection device leads to an increase in construction cost.

  Further, in the situation where the functions of the electronic device are diverse, the cost of improving the firmware in which a problem has occurred is enormous. For this reason, in the device remote monitoring system disclosed in Patent Document 1, it is difficult to quickly cope with a malfunction that has occurred.

  Therefore, a main object of the present invention is to provide a failure management system and the like that can be constructed at low cost.

  In order to achieve the above object, a fault management system according to the present invention is characterized by having the following configuration.

That is, the fault management system according to the present invention is
The register value indicated by the register in the electronic device is read via a communication network, the register value is compared with a determination value indicating a condition for issuing an instruction, and the state of the electronic device is indicated according to the comparison result. A diagnosis unit that selects a specific state value from among the state values and outputs the specific state value;
And a recovery unit that issues a specific command to the electronic device according to the specific state value.

Further, as another aspect of the present invention, the fault management method according to the present invention includes:
The register value indicated by the register in the electronic device is read via a communication network, the register value is compared with a determination value indicating a condition for issuing an instruction, and the state of the electronic device is indicated according to the comparison result. A specific state value is selected from the state values, and a specific command is issued to the electronic device according to the specific state value.

  According to the failure management system and the like according to the present invention, the cost for constructing the failure management system can be reduced.

  Next, the best mode for carrying out the invention will be described in detail with reference to the drawings.

<First Embodiment>
The configuration of the fault management system according to the first embodiment of the present invention will be described in detail with reference to FIG. FIG. 1 is a block diagram showing a configuration of a failure management system according to the first embodiment of the present invention.

  Referring to FIG. 1, the failure management system 10 according to the first embodiment of the present invention includes a diagnosis unit 20 and a recovery unit 30. First, the diagnosis unit 20 reads the value of the register 60 included in the electronic device 50 via the communication network 40. Next, the diagnosis unit 20 compares the read value of the register 60 with a determination value indicating a condition for issuing an instruction, and outputs a state value indicating the state of the electronic device 50 according to the result. Next, the recovery unit 30 issues a command to the electronic device 50 according to the state value output by the diagnosis unit 20.

  For example, the determination value is a certain numerical value or a bit string. For example, in the determination value, 0 is associated with a normal state, 1 is a state where a register needs to be rewritten, and 2 is a state where a restart is necessary. For example, when the value of the register 60 is 2, the diagnosis unit 20 determines that the electronic device 50 needs to be restarted, and outputs a state value indicating the state to the recovery unit 30. In the above description, the determination value is an integer value, but is not limited to an integer value. That is, the determination value may be a bit string or a part of the bit string. When the determination value is a bit string, the diagnosis unit 20 performs a comparison with reference to a predetermined bit string. The determination value is not limited to the example described above.

  The restoration unit 30 issues an instruction to the electronic device 50 by combining one or more instruction candidates. For example, the instruction candidates include an instruction to restart the electronic device 50, an instruction to rewrite the first register, an instruction to rewrite the second register, an instruction to restart after rewriting the register. Each of the state values described above is associated with an instruction candidate. The recovery unit 30 issues a command to the electronic device 50 by combining one command candidate or a plurality of command candidates according to the state value received from the diagnosis unit 20. However, the instruction candidates are not limited to the example described above.

  Next, the flow of processing performed by the failure management system 10 according to the first embodiment of the invention will be described in detail with reference to FIG. FIG. 2 is a flowchart showing the flow of processing in the failure management system 10.

  The diagnosis unit 20 in the failure management system 10 reads the value of the register 60 included in the electronic device 50 via the communication network 40 (step S10). Next, the diagnosis unit 20 compares the read value of the register 60 with the determination value, and outputs a state value indicating the state of the electronic device 50 according to the result (step S20). Next, the restoration unit 30 issues a command to the electronic device 50 according to the state value output by the diagnosis unit 20 (step S30).

  The device remote monitoring system disclosed in Patent Document 1 receives a failure notification issued by the electronic device 50, and copes with a failure according to the received failure notification. There are a plurality of electronic devices 50 monitored by the device remote monitoring system. Since the plurality of electronic devices 50 each have a failure detection device, there are a plurality of failure detection devices as a whole.

  On the other hand, the diagnosis unit 20 according to the first embodiment of the present invention determines the state of the electronic device 50 according to the register 60. Therefore, the electronic device 50 does not need to have a failure detection device. As a result, according to the failure management system according to the first embodiment, the number of failure detection devices can be reduced.

  In the above description, there is one register 60, but it is not necessarily one. Even when there are a plurality of registers 60, the first embodiment of the present invention performs the same processing.

  Furthermore, for example, the failure management system 10 in the first embodiment can be constructed by defining instruction candidates associated with the state value as an instruction to rewrite a register and an instruction to restart. In that case, the failure management system 10 issues a command to rewrite a register and a command to restart in response to a failure in the electronic device 50. In other words, according to the first embodiment, it is possible to deal with a problem without updating the firmware. For this reason, it becomes possible to quickly cope with a problem that has occurred.

  That is, according to the failure management system according to the first embodiment of the present invention, it is possible to reduce the cost of constructing the failure management system and to quickly cope with the trouble that has occurred.

<Second Embodiment>
Next, a second embodiment based on the above-described first embodiment will be described.

  In the following description, the characteristic part according to the present embodiment will be mainly described, and the same components as those in the first embodiment described above will be denoted by the same reference numerals, and redundant description will be omitted. To do.

  The diagnosis unit 20 in the failure management system according to the second embodiment of the present invention will be described with reference to FIGS. FIG. 3 is a block diagram showing a configuration of the diagnosis unit 20 in the failure management system according to the second embodiment of the present invention. FIG. 4 is a flowchart showing a flow of processing in the diagnosis unit 20 in the failure management system according to the second embodiment of the present invention.

  Referring to FIG. 3, the diagnosis unit 20 includes a register reading unit 22, a failure searching unit 24, and a determination information unit 26. The determination information unit 26 stores a determination value representing a condition for issuing a command to the electronic device 50 (illustrated in FIG. 1). The determination value may be a predetermined value or a predetermined bit string. The determination value is not limited to those exemplified above.

  The determination information unit 26 will be described with reference to FIG. FIG. 5 is a diagram illustrating an example of a table associated with the determination information unit 26 according to the second embodiment of the present invention. Referring to FIG. 5, the determination information unit 26 includes a register identifier (IDentifier, hereinafter also referred to as “ID”) for identifying the register 60 (shown in FIG. 1), and a determination value indicating a condition for issuing an instruction. The state value indicating the state of the electronic device 50 (shown in FIG. 1) is stored in association with each other.

  The register reading unit 22 reads the value of the register 60 (illustrated in FIG. 1) of the electronic device 50 (illustrated in FIG. 1) via the communication network 40 (illustrated in FIG. 1) (step S12).

  Next, the failure search unit 24 reads one or more determination values and state values associated with the register ID corresponding to the register read by the register reading unit 22 from the determination information unit 26 (step S14). Next, the failure search unit 24 determines whether the read determination value and the value of the register satisfy a predetermined determination condition (step S16).

  The predetermined determination condition is, for example, whether two values match or whether a predetermined bit string in the values matches. The predetermined determination condition is not limited to the above-described condition.

  Next, if the failure search unit 24 satisfies the predetermined determination condition among the determination values read from the determination information unit 26 (YES in step S16), the failure search unit 24 outputs the read state value ( Step S18). If there is no failure satisfying the predetermined determination condition in determination information unit 26 (NO in step S16), failure search unit 24 outputs a state value indicating that processing is not performed for the failure (step S19). ).

For example, it is assumed that the determination information unit 26 stores values as shown in FIG. In that case,
The failure search unit 24 outputs a status value of 2 if the value of the register whose register ID is 0x002 is 0x001.

  In the above description, there is one register 60 (illustrated in FIG. 1), but it is not necessarily one. Even when there are a plurality of registers 60 (shown in FIG. 1), the second embodiment of the present invention performs the same processing for each register.

  The diagnosis unit 20 determines the state of the electronic device 50 (shown in FIG. 1) according to the value of the register 60 (shown in FIG. 1). Therefore, the effect of the failure management system 10 having the diagnosis unit 20 in the second embodiment of the present invention is not different from the effect in the first embodiment described above.

  That is, according to the failure management system according to the second embodiment of the present invention, the cost for constructing the failure management system can be reduced, and a trouble that has occurred can be quickly dealt with.

<Third Embodiment>
Next, a third embodiment based on the above-described first embodiment will be described.

  In the following description, the characteristic part according to the present embodiment will be mainly described, and the same components as those in the first embodiment described above will be denoted by the same reference numerals, and redundant description will be omitted. To do.

  The recovery unit 30 in the failure management system according to the third embodiment of the present invention will be described with reference to FIGS. FIG. 6 is a block diagram showing the configuration of the recovery unit 30 in the failure management system according to the third embodiment of the present invention. FIG. 7 is a flowchart showing the flow of processing in the recovery unit 30 in the failure management system according to the third embodiment of the present invention.

  Referring to FIG. 6, the recovery unit 30 in the failure management system according to the third exemplary embodiment of the present invention includes an instruction unit 32 and an instruction information unit 34. The instruction information unit 34 stores the state value and an instruction to be performed on the electronic device 50 (illustrated in FIG. 1) in association with each other.

  The instruction information unit 34 will be described with reference to FIG. FIG. 8 is a diagram illustrating an example of a table associated with the instruction information unit 34 according to the third embodiment of the present invention. The instruction information unit 34 stores a state value indicating the state of the electronic device 50 (shown in FIG. 1) and an instruction in association with each other. For example, in FIG. 8, the state value of 2 is associated with an instruction “write a value of 0x0002 to a register whose register ID is 0x001”.

  First, the command unit 32 receives the state value output by the diagnosis unit 20 (illustrated in FIG. 1) (step S22). Next, the command unit 32 reads a command associated with the received state value from the command information unit 34 (step S24). Next, the command unit 32 issues a command to the electronic device 50 (shown in FIG. 1) in accordance with the read command (step S26).

  For example, it is assumed that the command unit 32 receives that the state value is 2. In this case, the instruction unit 32 reads from the instruction information unit 34 an instruction “write a value of 0x0002 to a register whose register ID is 0x001” associated with the state value being 2. Next, the instruction unit 32 issues to the electronic device 50 (illustrated in FIG. 1) the read instruction, that is, an instruction “write a value of 0x0002 to a register whose register ID is 0x001”. .

  In the above description, there is one register 60 (illustrated in FIG. 1), but it is not necessarily one. Even when there are a plurality of registers 60 (shown in FIG. 1), the third embodiment of the present invention performs the same processing.

  The command unit 32 issues a command to the electronic device 50 (shown in FIG. 1) according to the received state value. Therefore, the effect of the failure management system 10 having the command unit 32 in the third embodiment of the present invention is not different from the effect in the first embodiment described above.

  That is, according to the fault management system according to the third embodiment of the present invention, the cost for constructing the fault management system can be reduced, and a trouble that has occurred can be quickly dealt with.

<Fourth Embodiment>
Next, a fourth embodiment based on the above-described second embodiment will be described.

  In the following description, the characteristic part according to the present embodiment will be mainly described, and the same reference numerals will be given to the same configurations as those of the second embodiment described above, thereby omitting redundant description. To do.

  The diagnosis unit 21 in the failure management system according to the fourth embodiment of the present invention will be described with reference to FIGS. 9 and 10. FIG. 9 is a block diagram showing the configuration of the diagnosis unit 21 in the failure management system according to the fourth embodiment of the present invention. FIG. 10 is a flowchart showing the flow of processing in the diagnosis unit 21 in the failure management system according to the fourth embodiment of the present invention.

  Referring to FIG. 9, the diagnosis unit 21 includes a register reading unit 22, a failure searching unit 25, and a determination information unit 27. Referring to FIG. 11, the determination information unit 27 changes the register ID corresponding to the register 60 (illustrated in FIG. 1) read by the register reading unit 22, the restart determination value indicating the restart command condition, and the register. A register change determination value representing a condition to be executed, an instruction value representing an instruction, a register ID for changing the value, and change data representing data to be written are stored in association with each other. FIG. 11 is a diagram illustrating an example of a table associated with the determination information unit 27 according to the fourth embodiment of the present invention.

  The failure search unit 25 receives, from the determination information unit 27, one or more restart determination values associated with the register ID corresponding to the register read by the register reading unit 22, and a register change determination indicating a condition for changing the register The value, the instruction value representing the instruction, the register ID for changing the value, the instruction value representing the instruction, the register ID for changing the value, and the changed data representing the data to be written are read (step S31). Next, the failure search unit 25 determines whether the read restart determination value and the register value satisfy a predetermined determination condition (step S32).

  The predetermined determination condition is, for example, whether two values match or whether a predetermined bit string in the values matches. The predetermined determination condition is not limited to the above-described condition.

  Next, the failure search unit 25 reads the command value read if the restart determination value and the state value read from the determination information unit 27 satisfy the predetermined determination condition (YES in step S32). The register ID for changing the read value is associated with the read change data (step S35).

  If there is no restart determination value that satisfies the predetermined determination condition (NO in step S32), the failure search unit 25 and the register change determination value read from the determination information unit 27 and the register 60 (see FIG. 1). When it is determined whether or not the register value in FIG. 6 satisfies a predetermined determination condition, a comparison is performed (step S33). If there is a register change determination value that satisfies a predetermined determination condition (YES in step S33), the read instruction value and the register ID for changing the read value are associated with the read change data ( Step S36).

  If there is no register change determination value that satisfies the predetermined determination condition (NO in step S33), failure search unit 25 outputs a state value indicating that processing is not performed for the failure (step S33). S37).

For example, it is assumed that the determination information unit 27 stores values as shown in FIG. In that case,
If the value of the register whose register ID is 0x002 is 0x001, the failure search unit 25 matches the read restart determination value. Therefore, the failure search unit 25 outputs data in which the instruction value is 11, the change register ID is 0x003, and the change data is 0x0002 in association with each other.

  In the above description, there is one register 60 (illustrated in FIG. 1), but it is not necessarily one. Even when there are a plurality of registers 60 (shown in FIG. 1), the fourth embodiment of the present invention performs the same processing for each register.

  The diagnosis unit 21 determines the state of the electronic device 50 (shown in FIG. 1) according to the value of the register 60 (shown in FIG. 1). Therefore, the effect of the failure management system 10 having the diagnosis unit 21 in the fourth embodiment of the present invention is not different from the effect in the above-described fourth embodiment.

  That is, according to the fault management system according to the fourth embodiment of the present invention, the cost for constructing the fault management system can be reduced, and a trouble that has occurred can be quickly dealt with.

<Fifth Embodiment>
Next, a fifth embodiment based on the above-described third embodiment will be described.

  In the following description, characteristic parts according to the present embodiment will be mainly described, and the same components as those in the third embodiment described above will be denoted by the same reference numerals, and redundant description will be omitted. To do.

  The recovery unit 31 in the failure management system according to the fifth exemplary embodiment of the present invention will be described with reference to FIGS. FIG. 12 is a block diagram showing the configuration of the recovery unit 31 in the failure management system according to the fifth embodiment of the present invention. FIG. 13 is a flowchart showing the flow of processing in the recovery unit 31 in the failure management system according to the fifth embodiment of the present invention.

  Referring to FIG. 12, the recovery unit 31 in the failure management system according to the fifth exemplary embodiment of the present invention includes an instruction unit 33.

  First, the instruction unit 33 receives an instruction value output from the diagnosis unit 21 (illustrated in FIG. 9), a register ID for changing the value, and change data (step S41). Next, the command unit 33 issues a command to the electronic device 50 (shown in FIG. 1) according to the read command value, the register ID for changing the value, and the changed data (step S42). .

  According to the restoration unit 31 according to the fifth embodiment of the present invention, the instruction information unit is not necessary.

  In the above description, there is one register 60 (illustrated in FIG. 1), but it is not necessarily one. Even when there are a plurality of registers 60 (shown in FIG. 1), the fifth embodiment of the present invention performs the same processing.

  The command unit 33 issues a command to the electronic device 50 (shown in FIG. 1) according to the received state value. Therefore, the effect of the failure management system 10 having the command unit 33 in the fifth embodiment of the present invention is not different from the effect in the above-described fourth embodiment.

  That is, according to the fault management system according to the fifth embodiment of the present invention, it is possible to reduce the cost of constructing the fault management system and to quickly deal with the fault that has occurred.

(Hardware configuration example)
FIG. 14 is a block diagram schematically illustrating a hardware configuration of a calculation processing apparatus that can implement the failure management system according to each embodiment.

  Next, a configuration example of hardware resources that implements the failure management system in each of the above-described embodiments using one calculation processing device (information processing device, computer) will be described. However, the failure management system may be realized using at least two types of calculation processing devices physically or functionally. Further, the failure management system may be realized as a dedicated device.

  FIG. 14 is a diagram schematically illustrating a hardware configuration of a calculation processing apparatus capable of realizing the failure management system according to the first to fifth embodiments. The calculation processing device 100 includes a central processing unit (hereinafter referred to as “CPU”) 110, a memory 120, a disk 130, an output device 140, an input device 150, and a nonvolatile recording medium 160.

  The non-volatile recording medium 160 refers to, for example, a compact disc, a digital versatile disc, a Blu-ray Disc, a universal serial bus memory (USB memory), and the like. Even if it is not supplied, the program is retained and can be carried. The nonvolatile recording medium 160 is not limited to the above-described medium. Further, the program may be carried via a communication network instead of the nonvolatile recording medium 160.

  That is, the CPU 110 copies a software program (computer program: hereinafter simply referred to as “program”) stored in the disk 130 to the memory 120 at the time of execution, and executes arithmetic processing. The CPU 110 reads data necessary for program execution from the memory 120. When display is necessary, the CPU 110 displays the output result on the output device 140. When inputting a program from the outside, the CPU 110 reads the program from the input device 150. The CPU 110 interprets and executes the failure management program (FIGS. 2, 4, 7, 10, and 13) in the memory 120. The CPU 110 sequentially performs the processes described in the above embodiments.

  That is, in such a case, it can be understood that the present invention can also be realized by such a failure management program. Furthermore, it can be understood that the present invention can also be realized by a computer-readable recording medium in which such a failure management program is recorded.

It is a block diagram which shows the structure of the failure management system which concerns on the 1st Embodiment of this invention. It is a flowchart which shows the flow of a process in the failure management system which concerns on the 1st Embodiment of this invention. It is a block diagram which shows the structure of the diagnostic part in the failure management system which concerns on the 2nd Embodiment of this invention. It is a flowchart which shows the flow of a process in the diagnostic part in the failure management system which concerns on the 2nd Embodiment of this invention. It is a figure showing an example of the table with which the determination information part which concerns on the 2nd Embodiment of this invention associates. It is a block diagram which shows the structure of the recovery part in the failure management system which concerns on the 3rd Embodiment of this invention. It is a flowchart which shows the flow of a process in the recovery part in the failure management system which concerns on the 3rd Embodiment of this invention. It is a figure showing an example of the table with which the command information part which concerns on the 3rd Embodiment of this invention associates. It is a block diagram which shows the structure of the diagnostic part in the failure management system which concerns on the 4th Embodiment of this invention. It is a flowchart which shows the flow of a process in the diagnostic part in the failure management system which concerns on the 4th Embodiment of this invention. It is a figure showing an example of the table with which the determination information part which concerns on the 4th Embodiment of this invention associates. It is a block diagram which shows the structure of the recovery part in the failure management system which concerns on the 5th Embodiment of this invention. It is a flowchart which shows the flow of a process in the recovery part in the failure management system which concerns on the 5th Embodiment of this invention. It is a block diagram which shows roughly the hardware constitutions of the calculation processing apparatus which can implement | achieve the failure management system which concerns on each embodiment.

DESCRIPTION OF SYMBOLS 10 Fault management system 20 Diagnosis part 21 Diagnosis part 22 Register reading part 24 Fault search part 25 Fault search part 26 Determination information part 27 Determination information part 30 Recovery part 31 Recovery part 32 Command part 33 Command part 34 Command information part 40 Communication network 50 Electronic device 60 Register 100 Calculation processing device 110 CPU
120 Memory 130 Disk 140 Output device 150 Input device 160 Non-volatile recording medium

Claims (10)

The register value indicated by the register in the electronic device is read via a communication network, the register value is compared with a determination value indicating a condition for issuing an instruction, and the state of the electronic device is indicated according to the comparison result. A diagnosis unit that selects a specific state value from among the state values and outputs the specific state value;
A failure management system comprising: a recovery unit that issues a specific command to the electronic device according to the specific state value. The diagnostic unit
A register identifier for identifying the register, the determination value, and a determination information unit that stores the state value in association with each other;
A register reading unit for reading the register value;
When a specific determination value associated with a register identifier corresponding to the register referred to by the register reading unit and a first state value are read, the register value is compared with the determination value, and a predetermined determination condition is satisfied Is a fault search that uses the first state value as the specific state value and outputs a state value indicating that no processing is performed for the failure as the specific state value when a predetermined determination condition is not satisfied. The failure management system according to claim 1, further comprising: a unit. The recovery unit
An instruction information section for storing the state value and the instruction in association with each other;
The failure management system according to claim 1, further comprising: an instruction unit that reads a first instruction associated with the state value from the instruction information unit and uses the first instruction as the specific instruction. In the determination information section,
The determination value represents a restart determination value representing a condition for instructing restart, and a register change determination value representing a condition for changing a register,
The state value represents an instruction value representing an instruction, a register identifier for changing the value, and change data representing data to be written,
The failure search unit reads a specific restart determination value, a specific register change determination value, a specific register identifier, and specific change data associated with a register identifier corresponding to the register referred to by the register reading unit. ,
Compare the register value and the restart determination value,
If the predetermined judgment condition is met, select a specific command value corresponding to the command to be restarted,
When the predetermined determination condition is not satisfied, the register value is compared with the register change determination value, and when the predetermined determination condition is satisfied, a specific instruction value representing an instruction to write a value to the register is selected,
If the predetermined judgment condition is not satisfied, select a specific command value indicating that processing is not performed for the defect,
The fault management system according to claim 1 or 2, wherein the specific instruction value, the specific change data, and the specific register identifier are output as the specific state value. The fault management system according to claim 1, wherein the command unit issues the specific command in accordance with the specific command value, the specific register identifier, and the specific change data.   The register value indicated by the register in the electronic device is read via a communication network, the register value is compared with a determination value indicating a condition for issuing an instruction, and the state of the electronic device is indicated according to the comparison result. A failure management method for selecting a specific status value from status values and issuing a specific command to the electronic device in accordance with the specific status value. The register value indicated by the register in the electronic device is read via a communication network, the register value is compared with a determination value indicating a condition for issuing an instruction, and the state of the electronic device is indicated according to the comparison result. A diagnostic function for selecting a specific status value from the status values and outputting the specific status value;
A failure management program for causing a computer to implement a recovery function for issuing a specific command to the electronic device according to the specific state value. The diagnostic function is:
A first function for associating a register identifier for identifying the register, the determination value, and the state value;
A register reading function for reading the register value;
When a specific determination value associated with a register identifier corresponding to the register referred to by the register reading function and a first state value are read, the register value is compared with the determination value, and a predetermined determination condition is satisfied Is a fault search that uses the first state value as the specific state value and outputs a state value indicating that no processing is performed for the failure as the specific state value when a predetermined determination condition is not satisfied. The failure management program according to claim 7 provided with a function. The recovery function is
A second function associating the state value with the instruction;
The failure management program according to claim 7 or 8, further comprising: an instruction function that uses the second function to select a first instruction associated with the state value and uses the first instruction as the specific instruction. . In the first function,
The determination value represents a restart determination value representing a condition for instructing restart, and a register change determination value representing a condition for changing a register,
The state value represents an instruction value representing an instruction, a register identifier for changing the value, and change data representing data to be written,
The failure search function reads a specific restart determination value, a specific register change determination value, a specific register identifier, and specific change data associated with a register identifier corresponding to the register referred to by the register reading unit. ,
Compare the register value and the restart determination value,
If the predetermined judgment condition is met, select a specific command value corresponding to the command to be restarted,
When the predetermined determination condition is not satisfied, the register value is compared with the register change determination value, and when the predetermined determination condition is satisfied, a specific instruction value representing an instruction to write a value to the register is selected,
If the predetermined judgment condition is not satisfied, select a specific command value indicating that processing is not performed for the defect,
9. The fault management program according to claim 7, wherein the specific instruction value, the specific change data, and the specific register identifier are output as the specific state value.

Images