JP2007028037A - Apparatus for coping with fault detection and diagnosis, system for coping with fault detection and diagnosis, and method for coping with fault detection and diagnosis - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an apparatus for coping with fault detection and diagnosis provided with a function of detecting an unknown fault having not been caused in its own apparatus and a system so as to externally acquire a diagnostic countermeasure, and to provide a system for coping with fault detection and diagnosis, and a method for coping with fault detection and diagnosis. <P>SOLUTION: The apparatus for coping with fault detection and diagnosis in the system for coping with fault detection and diagnosis and adopting the method for coping with fault detection and diagnosis includes: a fault detection processing section that detects the occurrence of a fault; a diagnosis processing section that acquires diagnostic countermeasure information for countermeasuring a cause to the detected fault on the basis of self-diagnosis countermeasure information stored in a storage section or coping with the fault via a network and diagnoses the fault on the basis of the self-diagnosis countermeasure information or the diagnosis countermeasure information; and a fault countermeasure processing section that executes processing for countermeasuring the fault and processing of managing the countermeasuring processing on the basis of the result of the diagnosis. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a failure detection diagnosis coping apparatus, a failure detection diagnosis coping system, and a failure detection diagnosis coping method for detecting a system failure and diagnosing the failure and coping with the failure. By quickly reflecting failure detection and diagnosis countermeasures on similar system components that have a common function connected to the network, it is possible to respond to the failure without having a special server for failure detection and diagnosis on the network. The present invention relates to a failure detection diagnosis handling apparatus, a failure detection diagnosis handling system, and a failure detection diagnosis handling method.

  The conventional failure detection / diagnostic system does not have a function for detecting an unknown failure in its own system. Therefore, when an unknown failure occurs in the system, even if the unknown failure occurs outside the system, Even if there is a solution of the above, it was not possible to cope.

  As an example, FIG. 1 shows a schematic configuration of a “vehicle maintenance management device” disclosed in Patent Document 1. The vehicle maintenance management device shown in FIG. 1 is a vehicle-mounted diagnosis notification device that performs failure diagnosis of each part of the vehicle and wirelessly transmits the diagnosis results, and receives and accumulates the diagnosis results at the base and manages them as a maintenance file. It has a stationary file management device. And in the vehicle maintenance management apparatus which manages vehicle maintenance with the stored file, the wireless transmission part which transmits the data of a maintenance file is provided in a file management apparatus. In addition, a radio receiving unit that receives the data and a monitor unit that displays the diagnosis result are provided in the diagnosis reporting device. In other words, the vehicle maintenance management device has a form in which the base side that constitutes the device collectively manages failure diagnosis and countermeasure information in the event of a vehicle failure.

  In addition, the following proposals have been made in relation to the above technique.

  In the “vehicle maintenance management device” disclosed in Japanese Patent No. 2885158, a diagnosis notification device provided on the vehicle side that performs failure diagnosis of each part of the vehicle and wirelessly transmits the diagnosis result, and receives the diagnosis result And a file management device provided on the base side for managing as a maintenance file, and in a vehicle maintenance management device for managing vehicle maintenance using the accumulated file, a diagnosis notification device provided on the vehicle side File management provided on the base side, having a memory for storing the diagnosis results made on the side and a monitor unit for displaying the diagnosis results stored in the memory when communication with the base side is not performed While providing a wireless transmission unit for transmitting maintenance file data to the device, receiving data from this wireless transmission unit, Vehicle maintenance management system has been proposed for displaying together with diagnosis performed on the vehicle side at Nita unit.

JP 09-164923 A Japanese Patent No. 2885158

  In “conventional failure diagnosis countermeasure devices and systems” such as conventional vehicle maintenance management devices, the failure is detected from the value of the sensor by detecting the failure with the sensor provided by itself and referring to the history information of the failure that has already occurred. The cause of the problem is diagnosed, and further countermeasures are taken for the failure. For this reason, it is not possible to take measures such as detection, diagnosis and coping with an unknown failure, not an already occurring failure.

  In order to solve such a problem, in the “vehicle maintenance management device” disclosed in Patent Document 1, the vehicle maintenance management device and a vehicle maintenance management device having a common function with the vehicle maintenance management device And a common access server that these devices can access in common are configured through a network. As a result, from the self-contained type in which only the vehicle maintenance management device itself completes the response to the failure, the information on the failure detection diagnosis handling held by the plurality of vehicle maintenance management devices having the same function as the vehicle maintenance management device is obtained. , Acquired through a common access server, and realized to detect, diagnose and deal with unknown failures.

  However, in a system with a common access server, information on failure detection and diagnosis that was solved by the vehicle maintenance management device having a common function with the vehicle maintenance management device connected to the network is registered in the common access server. Or, when a vehicle maintenance management device having a common function with the vehicle maintenance management device is released from the network, information management such as deleting information related to the release device from the common access server is required.

  In the following, means for solving the problem will be described using reference numerals with parentheses used in [Best Mode for Carrying Out the Invention]. These symbols are added in order to clarify the correspondence between the description of [Claims] and the description of the best mode for carrying out the invention. ] Should not be used for interpretation of the technical scope of the invention described in the above.

  The failure detection diagnosis coping system (80) of the present invention includes a plurality of failure detection diagnosis coping devices (1A, 1B, 1C) connected to the network (1000). Is detected by a failure detection processing unit (500, 60) for detecting the occurrence of a fault, a storage unit (40) for storing self-diagnosis handling information for a failure that has occurred in itself, and a failure detection processing unit. The plurality of failure detection diagnoses having the handling information corresponding to the failure, the self-diagnosis handling information (610, 60) stored in the storage unit, or the diagnosis handling information corresponding to the failure via the network A diagnosis processing unit (600, 60) acquired from any of the coping devices and a process (720) corresponding to the failure are executed based on the result of the diagnosis by the diagnosis processing unit. A fault handling processing unit which performs management of the execution by said processing (710) and (700,60).

  The failure detection diagnosis coping apparatus, the failure detection diagnosis coping system, and the failure detection diagnosis coping method of the present invention have a function capable of detecting an unknown fault that has never occurred in its own system, Can be acquired from outside of itself.

  Further, in the failure detection diagnosis countermeasure apparatus, the failure detection diagnosis countermeasure system, and the failure detection diagnosis countermeasure method of the present invention, management of resolved failure detection diagnosis countermeasure information becomes unnecessary.

  Further, the failure detection diagnosis handling apparatus, the failure detection diagnosis handling system, and the failure detection diagnosis handling method of the present invention do not require a common access server, so that continuous management is unnecessary.

  With reference to the attached drawings, the best mode for carrying out the failure detection diagnosis handling apparatus, the failure detection diagnosis handling system and the failure detection diagnosis handling method of the present invention will be described below.

(Embodiment 1) Failure detection diagnosis coping apparatus FIG. 2A shows a schematic configuration of a failure detection diagnosis coping apparatus according to Embodiment 1 of the present invention. FIG. 2B shows a functional configuration of the failure detection / diagnosis handling apparatus according to the first embodiment.

  The failure detection diagnosis coping apparatus A (1A) according to the present embodiment includes an input unit 20 for inputting instructions, a CPU 60, a storage unit 40, a communication unit 30 for connecting to the network 1000, and an input unit. And an output unit 70 for outputting a result of a process performed based on the instruction input to 20. The input unit 20, the storage unit 40, the output unit 70, the CPU 60, and the communication unit 30 are connected by a bus line 50.

  In addition, as shown in FIG. 2B, this embodiment includes (1) failure detection processing units 500 and 60 that are functions for detecting the occurrence of a failure, and (3) the cause of the detected failure. Based on the self-diagnosis handling information 610 stored in the storage unit 40 or via the network 1000, diagnostic handling information corresponding to the failure is acquired, and the failure diagnosis is performed based on the self-diagnosis handling information 610 or the diagnosis handling information. A diagnosis processing unit 600 that is a function for performing the processing, and (3) a failure handling processing unit 700 that is a function for performing the processing 720 that deals with the failure based on the diagnosis result and the processing 710 that manages the processing to be dealt with. And as a functional configuration.

  In the present embodiment, in order to realize the function shown in FIG. 2B, an application 900 and an OS (operating system) 300 that execute the function, which is software 100, are stored in the storage unit 40 in advance. The OS (operating system) 300 includes a task management 310 and a network management 400. The task management 310 has a task queue 311 that is data indicating the execution order of tasks of the application 900. The network management 400 includes a network layer 410 and a transport layer 420. The network layer 410 has a routing table 411.

  The application 900 includes an application task 1 (910) to an application task n (930), a failure detection processing unit 500, a diagnosis processing unit 600, and a countermeasure processing unit 700. Application task 1 (910) to application task n (930) include task state information 1 (912) to task state information n (932) indicating the operation state of each application task, and details of the operation of the application task. A constant table 1 (914) to a constant table n (934) for adjustment are provided. The constant table 1 (914) to the constant table n (934) are particularly stored in a rewritable nonvolatile memory or the like.

  The failure detection processing unit 500 includes a software error occurrence frequency transition investigation process 520, a task state transition elapsed time investigation process 530, a task / queue abnormal array detection process 540, and a detection information management process 510 for managing them. ing. The failure detection processing unit 500 actually corresponds to the failure detection processing unit 500 of the application 900 when the failure detection diagnosis coping apparatus A (1A) is activated and the CPU 60 reads the application 900 stored in the storage unit 40. By executing the processing, the function is realized.

  The diagnosis processing unit 600 includes a diagnosis client process 620, a diagnosis server process 630, and self-diagnosis handling information 610. The diagnosis processing unit 600 is actually a process corresponding to the diagnosis processing unit 600 of the application 900 when the failure detection diagnosis coping apparatus A (1A) is activated and the CPU 60 reads the application 900 stored in the storage unit 40. This function is realized by executing.

  The failure handling processing unit 700 includes an application task m 720 as a handling application task, and a handling management process 710. The application task m720 includes task state information m722 indicating the operation state of each application task, and a constant table m724 for finely adjusting the operation of the application task. In the failure handling processing unit 700, the failure detection diagnosis handling apparatus A (1A) is actually activated, and the application 900 stored in the storage unit 40 is read by the CPU 60, and the diagnosis processing unit 600 of the failure handling processing unit 700 is read. The function is realized by executing the processing corresponding to.

(Operation principle of Embodiment 1)
The operation principle of the failure detection / diagnosis handling apparatus A (1A) according to Embodiment 1 of the present invention will be described with reference to FIG. 2B. When the failure detection diagnosis coping apparatus A (1A) according to the present embodiment is activated, the CPU 60 reads and executes the application 900 stored in the storage unit 40. FIG. 3 shows the relationship of functions among the failure detection processing unit 500, the diagnosis processing unit 600, and the countermeasure processing unit 700 in the present embodiment.

  The failure detection processing unit 500 detects a failure occurring in the apparatus according to the present embodiment using three methods.

  The first method is based on the software error occurrence frequency transition investigation process 520. FIG. 4 shows an example of the error occurrence frequency transition table of a certain system. In task state information 1 (912) to task state information n (932), it is possible to know what processing the application software is performing. The task status information 1 (912) to task status information n (932) includes error processing. If the time transition of the error number and the number of error occurrences shown in FIG. It can be seen that some sort of failure has occurred even though it cannot be identified. Deterioration of parts is a cause of increasing errors over time. As a countermeasure for component deterioration, there is a method of changing the value of a constant table owned by an application task. The constant table is prepared for fine-tuning a problem caused by component variations at the time of product shipment. In the present invention, a constant table used for correcting the variation of the parts is used to deal with the deterioration of the parts. In the functional configuration illustrated in FIG. 2, the handling management process 710 corresponds to the process by changing the constant table 1 (914) to the constant table m (724). If the parts function is not possible, a method of changing to alternative means compatible software including alternative information sources can be considered, but if this is not possible, parts are replaced. As an example of changing to the alternative means compatible software, a method of obtaining acceleration using a speedometer when an acceleration sensor used in an air bag system breaks down is used as an alternative means. That is, the application task may be changed from acceleration using an acceleration sensor to acceleration using a speedometer. Specifically, in FIG. 2, the processing of the acceleration sensor is assumed to be application task 1 (910), and the coping application task is assumed to be application task m (720) for obtaining acceleration from a speedometer. Here, the coping application task is an application task created for coping with a failure in the coping process information acquired from the diagnosis client process. In addition, the handling management process includes a process for loading and deleting the handling application task, a process for adjusting start and stop of the application task, and a process for adjusting the constant table of the application task. is there.

  The handling management process 710 of the fault handling processing unit 700 receives the application task m 720 from the diagnostic client process 620, stops the application task 1 (910), and executes the application task m (720) instead. If the application task 1 (910) and the application task m720 are stored in a common storage unit, it is not known from other application tasks that use the acceleration information that the application task has been switched.

  The second method is task state transition elapsed time investigation processing 530. The task state transition elapsed time investigating process 530 is a process of detecting a system failure based on an abnormality in task state information indicating an operation state of an application / task. The task state information is information in which the number of times error processing has been passed on the software is recorded over time, or the execution time and transition destination information of each application software. FIG. 5 shows an expected value list and an actual value table used in the task state transition elapsed time investigation process. On the software 100 provided in the present embodiment, an expected value list is incorporated, and by checking the state transition and processing time of each application task, the list is updated based on the lower limit and upper limit of the state transition and processing time. An abnormality of the failure detection diagnosis coping apparatus A (1A) according to the embodiment is detected. Although this method cannot identify the cause, it can be seen that some kind of failure has occurred. As a rough cause, deterioration and inability of parts and soft bugs are considered. As a countermeasure corresponding to this, the constant table is changed for the deterioration of the component. In addition, if the component is not available, the process of changing to alternative software is performed as described above. In the case of a software bug, the software of the corresponding application task may be changed by the same method as the change of the application task in the first method.

  The third method is task queue abnormal array detection processing 540. The task queue abnormal array detection process 540 is a process for determining an abnormal array of execution tasks from a task queue indicating the execution order of tasks managed by the operating system and detecting a system failure. FIG. 6 shows an example of an abnormal task queue in an electrical device. In this example, there are more application tasks for urgently stopping the electrical device than there are application tasks for stopping. According to this method, only a situation that is unlikely to occur normally is found, and although the cause cannot be specified, it is understood that some kind of failure has occurred. As the cause, as in the second method, deterioration of parts, inability to function, and soft bugs can be considered.

  The above-described three failure detection methods are managed by the detection information management process 510, and are taken over by the diagnosis processing unit 600 when a diagnosis countermeasure that cannot be solved by the apparatus itself occurs.

  The processing of the diagnosis processing unit 600 in this embodiment is connected to the failure detection diagnosis coping apparatus A (1A) according to the present embodiment via the network, and has the same function as the failure detection diagnosis coping apparatus A (1A). This is performed in cooperation with a diagnostic process executed in the external device. The diagnosis processing unit 600 according to the present embodiment includes a function for performing a diagnosis client process 620 and a diagnosis server process 630, and self-diagnosis handling information 610 for failures that have been dealt with so far.

  The diagnosis client process 620 will be described with reference to FIG. In the diagnosis client processing 620, when it is determined that a failure that has not been solved in the device has occurred, the detected information of the detected failure is sent to the adjacent external device, and a request for failure diagnosis is requested. When the diagnostic countermeasure information is acquired from the external device having the corresponding diagnostic countermeasure information, the countermeasure information is transferred from the acquired diagnostic countermeasure information to the countermeasure processing of its own device. When the process by the countermeasure process is executed, the countermeasure result is acquired from the countermeasure process, and the process result is transmitted to the external device that is the source of the diagnosis countermeasure information. The diagnostic countermeasure information adopted by the own device is added or changed to the diagnostic countermeasure information storage location for storing the diagnostic countermeasure information owned by the own device. Also, an external device connected to the network from the presence / absence of a response based on diagnostic server processing from an external device connected to the network, and information of the transport layer 420 and network layer 410 of the network management 400 provided in the device itself The connection state is detected, and the failure notification, the limitation of the processing contents for the handling processing, and the change notification of the alternative means for the handling processing are performed to the external device in which the fault has occurred. When the diagnosis client process 620 is actually started (step S100), first, the device unresolved failure occurrence determination (step S105) is performed. This is to determine the result of failure occurrence in the detection information management processing 510, and is repeated until an unresolved failure occurs. Next, when an unresolved failure occurs, external device failure diagnosis countermeasure inquiry processing (step S110) is performed. In this process, the failure detection diagnosis coping apparatus A (1A) according to the present embodiment has a function capable of executing the same processing, and the failure detection diagnosis coping apparatus A according to the present embodiment via the network is performed. (1A) transmits unresolved failure detection information to the external device connected to the external device, and inquires whether a similar failure has occurred in the external device in the past. When the external device failure diagnosis countermeasure inquiry processing (step S110) is completed, the diagnostic client processing 620 executes the external device failure diagnosis countermeasure information standby acquisition processing (step S120) waiting for a response from the external device. The diagnostic server processing 630 in the failure detection diagnosis coping apparatus according to the present embodiment and the external device connected to the fault detection diagnosis coping apparatus A (1A) according to the present embodiment via the network requests itself. It is determined whether or not the information for handling the diagnosis of the failed failure is held. If not, the next external apparatus is inquired based on the routing table 411 of the network layer 410. In the diagnosis server process, when a diagnosis request is received from the diagnosis client process of the external device and the diagnosis countermeasure information corresponding to the diagnosis countermeasure information storage location of its own is received, the diagnosis client process of the requesting external device When the diagnostic countermeasure information is transmitted and the corresponding diagnostic countermeasure information is not included, an inquiry is made for the diagnostic server processing of the next adjacent external device. Further, when the confirmation result of the diagnostic countermeasure information transmitted to the request source is received, the diagnostic countermeasure information is recorded, deleted, and changed in the diagnostic countermeasure information storage location.

  FIG. 7 shows an example in which a plurality of external devices to be inquired are distributed and processed at the same time, and an example in which the external device N (1N) has failure diagnosis countermeasure information is shown. The diagnosis client process 620 first inquires of the external device K (1K) whether there is failure diagnosis countermeasure information (step S110). The external device K (1K) determines whether or not the failure diagnosis countermeasure information is held in the requested failure diagnosis countermeasure information possession determination (step S210). As a result, when it is determined that the external device K (1K) does not have the failure diagnosis countermeasure information, an inquiry is made to the external device N (1N). Similarly, in the external device N (1N), it is determined whether or not the failure diagnosis countermeasure information is possessed in the requested failure diagnosis countermeasure information possession determination (step S310). If the external device N (1N) holds the failure diagnosis countermeasure information, a failure diagnosis countermeasure information request system return process (step S320) for returning the failure diagnosis countermeasure information to the requesting device is executed. The failure diagnosis response information transmitted from the external device N (1N) is acquired by the standby external device failure diagnosis response information standby acquisition process (step S120) of the present embodiment, and the information is external The device failure diagnosis response information response processing transfer processing (step S130) is sent to the response processing response setting, execution and effect result determination processing (step S110) in the failure response processing unit 700. The processing results processed in the handling processing handling setting, execution, and effect result determination processing (step S110) in the failure handling processing unit 700 are returned to the handling effect result standby acquisition processing (step S140) of the client processing 620. The countermeasure effect result standby acquisition process (step S140) that receives the effect result from the countermeasure setting, execution, and effect result determination process (step S110) transmits the effect result to the next countermeasure effect result determination (step S150), and If it is determined in the countermeasure effect result determination (step S150) that there is an effect, the diagnosis countermeasure information storage process (step for storing the diagnostic countermeasure information acquired from the external device in the storage unit 40 in which the self-diagnosis countermeasure information 610 is stored) S160) is executed, information providing external device effect transmission processing (step S180) is performed to transmit that the external device that provided the information has an effect, and the provision information of the external device N (1N) is reflected next time. A result with a countermeasure effect is sent to the process (step S330). On the other hand, if there is no effect, an information providing external device effect absence transmission process (step S170) for transmitting that the external device that provided the information has no effect is executed, and information provided by the external device N (1N) is executed. A result of no countermeasure effect is sent to the next reflection process (step S330). The provision information next reflection process (step S330) of the external device N (1N) retains the determination condition processed in the requested failure diagnosis countermeasure information possession determination (step S310) as it is, for example, when there is a countermeasure effect. Keep it. On the other hand, if there is no countermeasure effect, it is deleted from the determination conditions processed in the requested failure diagnosis countermeasure information possession determination (step S310). When there is a difference in device type between devices connected to the network 1000 and exchanging information, the countermeasure effect is added as additional information to the determination condition processed in the requested failure diagnosis countermeasure information possession determination (step S310). Append the result.

  As described above, the failure detection diagnosis coping apparatus A (1A) according to the present embodiment has a function capable of detecting an unknown failure that has never occurred in its own device, and diagnoses it. The countermeasure can be acquired from an external device having the same function via the network. Moreover, management of failure detection diagnosis countermeasure information that occurs each time a failure is dealt with becomes unnecessary. Further, since no common access server or the like is required, it is not necessary to install and manage the common access server continuously.

(Embodiment 2) Failure detection diagnosis coping system FIG. 2A shows a schematic configuration of a failure detection diagnosis coping system according to Embodiment 2 of the present invention. FIG. 2B shows a functional configuration of the failure detection / diagnosis handling apparatus provided in the present embodiment.

  The failure detection diagnosis coping system 80 according to the present embodiment includes a failure detection diagnosis coping apparatus A (1A), a failure detection diagnosis coping apparatus B (1B) having the same function as the failure detection diagnosis coping apparatus A (1A), and a fault detection. The diagnostic coping apparatus C (1C) is configured by being connected to the network 1000 by wire or wirelessly.

  The general configuration of the failure detection / diagnosis handling system according to the present embodiment, the operation principle thereof, and the operational effects brought about by the configuration and the operation principle have been described in the first embodiment, and thus detailed description thereof is omitted here. To do.

  However, in the description of the first embodiment, focusing on the failure detection / diagnosis handling device A (1A), other devices connected to the network 1000 are described as external devices. However, the failure described in FIG. The detection diagnosis coping apparatus B (1B) and the failure detection diagnosis coping apparatus C (1C) each have a configuration and operating principle that are comparable to the failure detection diagnosis coping apparatus A (1A).

(Embodiment 3) Automobile failure detection diagnosis coping system FIG. 8 shows a schematic configuration of an automobile failure detection diagnosis coping system according to Embodiment 3 of the present invention.

  The vehicle failure detection diagnosis coping system 80A according to the present embodiment includes an ECU (Electric) equipped with the failure detection diagnosis coping apparatus A (1A) described in the first embodiment in a vehicle and connected via an in-vehicle LAN. Control Unit; engine control device, car audio, car navigation system, etc.).

  The automobile failure detection / diagnosis handling system 80A according to the present embodiment includes an automobile 1 (850A), an automobile 2 (850B), and an automobile 3 (850C) connected to the same network 1000 by a wireless LAN.

  The automobile 1 (850A) includes an ECU 1A (851A), an ECU 2A (852A), an ECU 3A (853A), an ECU 5A (855A), and an ECU 9A (859A) connected to the in-vehicle LAN (A) 860A. Specifically, each ECU is an electronic device having a microcomputer such as an engine control device, a car audio, a car navigation system, or the like, which is an electronic control device provided in an automobile. Similarly for the automobile 2 (850B) and the automobile 3 (850C), the ECU 1B (851B), the ECU 2B (852B), and the ECU 3B (853B) are connected by the in-vehicle LAN (B) 860B and the in-vehicle LAN (C) 860C, respectively. ), ECU 5B (855B), ECU 9B (859B), and ECU 1C (851C), ECU 2C (852C), ECU 3C (853C), ECU 5C (855C), ECU 9C (859C). In the present embodiment, each automobile is connected to the network 1000 via a wireless LAN via the ECU 9A (859A), the ECU 9B (859B), and the ECU 9C (859C), thereby forming a system according to the present embodiment. The In the present embodiment, the number of automobiles is three, and the number of ECUs provided in each automobile is six. However, this number is appropriately changed as necessary. Further, the ECU 9A (859A), the ECU 9B (859B), and the ECU 9C (859C) are connected to the network, respectively, but this connecting device is appropriately changed to another ECU.

  In FIG. 8, the ECU 1A of the automobile 1 (850A) is shown in comparison with the failure detection / diagnosis handling apparatus A (1A) of the first embodiment, but other ECUs have the same configuration and operation principle. .

  The operation principle of the automobile failure detection / diagnosis handling system 80A according to the present embodiment is the same as that of the second embodiment, and detailed description thereof is omitted here. However, in the present embodiment, as shown in FIG. 8, a plurality of ECUs are connected via the in-vehicle LAN. For this reason, the diagnosis processing unit 600 detects the connection state of each ECU connected adjacent to the in-vehicle LAN based on the transport layer 420 of the network management 400 and the routing table 411 included in the network layer 410. To do. If there is a problem in the connection state of another ECU, it is determined that there is a failure. If the in-vehicle LAN can be bypassed to the adjacent ECU, a failure notification is given, and the processing content is restricted for the handling processing of the ECU. Notification or change of alternative means of the process.

  The present embodiment provides the same effects as those of the first and second embodiments. In particular, in the present embodiment, the safety and reliability related to the operation and operation of the automobile, as well as repair, are remarkably improved. I can do it.

(Embodiment 4) Electrical equipment failure detection diagnosis handling system FIG. 9 shows a schematic configuration of an electrical equipment failure detection diagnosis handling system according to Embodiment 4 of the present invention.

  The electrical device failure detection / diagnosis handling system 80B according to the present embodiment is obtained by applying the failure detection / diagnosis handling device A (1A) described in the first embodiment to each electrical device connected to the network 1000.

  Here, the electrical equipment includes, for example, AV (audio-visual equipment), refrigerators, air conditioners, household appliances, office appliances, and electrical appliances used as industrial control devices used in factories. It is a broad concept that includes. Therefore, in FIG. 9, specifically, household appliances such as AV equipment, refrigerators and air conditioners, industrial control devices, etc. are used as specific applied products. is there.

  The electrical device failure detection diagnosis coping system 80B according to the present embodiment includes an electrical device 1 (800A), an electrical device 2 (800B), and an electrical device 3 (800C) connected to the same network 1000 by a wireless or wired LAN. ). In the present embodiment, the number of electrical devices connected to the network 1000 is three, but this number is appropriately changed as necessary.

  In FIG. 9, the electric device 1 (800A) is shown in comparison with the failure detection / diagnosis handling apparatus A (1A) of the first embodiment, but other electric devices have the same configuration and operation principle. .

  The operating principle of the electrical equipment failure detection / diagnosis handling system 80B according to the present embodiment is the same as that of the second embodiment, and detailed description thereof is omitted here. The configuration shown in this embodiment is an example in which each electric device does not have a LAN in the device. However, the LAN is installed in the electric device, and each operation unit in the device is connected via the LAN. It is also possible to adopt the same configuration and operation principle as in the third embodiment. Each electric device is equipped with a microcomputer, and the apparatus shown in Embodiment 1 is realized by the configuration of each microcomputer. Diagnosis for a failure that cannot be solved by the electric device 1 (800A) is inquired of the electric device 2 (800B) or the electric device 3 (800C) via the network 1000.

  The present embodiment provides the same effects as at least one of the first to third embodiments. In the present embodiment, the operation of the electric equipment and the reliability at the time of failure are remarkably improved. Can be improved.

(Embodiment 5) Intermediary Server Attached Electrical Equipment Fault Detection Diagnosis Handling System FIG. 10 shows a schematic configuration of an intermediary server attached electrical equipment fault detection diagnosis handling system according to Embodiment 5 of the present invention. The electrical equipment failure detection diagnosis coping system 80C attached to the mediation server according to the present embodiment is further connected to the electrical equipment failure detection diagnosis coping system 80B according to the fourth embodiment via the network 1000, and is connected to the network. The intermediary server 880 having the system network address of each of the electrical devices and the diagnosis coping information at the time of failure is provided. The mediation server 880 is a normal computer server, and performs a mediation server diagnostic server process as its server function. The diagnostic server process for the mediation server is a process that introduces another electrical device that has the diagnosis handling information and is connected to the network 1000 with respect to the electrical device that is requested to deal with the failure. is there.

  As in the fourth embodiment, the electrical device in this embodiment is also an AV (audio / visual) device, a household appliance such as a refrigerator or an air conditioner, and an appliance for a business use, or an industrial appliance used in a factory. It is a broad concept that includes electrical equipment used as a control device.

  In the present embodiment, the diagnosis processing unit 600 of each of a plurality of electrical devices connected to the network 1000 determines whether a failure can be diagnosed based on the self-diagnosis handling information 610 when a failure is detected. . If it is determined that the failure cannot be diagnosed by itself, the failure detection information is transmitted to the mediation server 880 via the communication unit 30. Based on the reception of the detection information, the mediation server 880 refers to the failure diagnosis handling information holding device network address information having the system network address of each of the plurality of electrical devices connected to the network 1000 and the diagnosis handling information at the time of failure. Then, the system network address of the electrical device having the diagnostic information corresponding to the failure is searched. If there is no system network address of an electrical device having diagnostic information corresponding to the failure, failure detection information is further transmitted to the electrical device connected adjacent to the requesting electrical device on the network 1000 Request.

  Further, the mediation server 880 receives the result of the handling process for the failure from the requesting electrical device, and changes the fault diagnosis handling information holding device network address information based on the result. Further, when the mediation server 880 determines that the result is effective in dealing with the failure based on the result of the handling process, the mediation server 880 obtains the device network address information of the electrical device having the diagnostic information corresponding to the failure. If it is determined that the result is ineffective in dealing with the failure, the device network address of the electrical device having diagnostic information corresponding to the failure is deleted. If it is determined that the device is related to a type of electrical device that is not included in the current failure diagnosis response information holding device network address information, the failure diagnosis response information holding device network address information A device network address and diagnostic countermeasure information at the time of failure are newly added.

(Operational principle of Embodiment 5)
The operation flow according to the present embodiment will be described with reference to FIG. 11 separately for the failure handling processing unit 700, the diagnostic client processing 620, the mediation server diagnostic server processing 810, and the external server diagnostic server processing.

  The basic part of the operation flow according to the present embodiment is the same as that of the first embodiment. However, in the operation flow of the present embodiment, the external device failure diagnosis coping information inquiry processing (step S110) in the operation flow (FIG. 7) of the first embodiment is replaced with the external device failure diagnosis coping information intermediary server inquiry processing (step S110). S115) is performed. That is, when making an inquiry to the outside, first of all, an inquiry about failure handling information is made to the mediation server 880. In the intermediary server diagnostic server processing 810 in the intermediary server 880, the inquiry fault diagnosis coping information for searching the network address of the electrical device that holds the diagnostic coping information of the fault to be inquired from the fault diagnosis coping information holding device network address information. The holding device network address search process (step S400) is executed, and a search is performed as to whether or not the corresponding electrical device is registered in the information. If there is no corresponding electric device, an inquiry is made for diagnosis server processing of an electric device connected adjacently on the network 1000. In the operation flow shown in FIG. 11, an electric device having corresponding diagnosis countermeasure information is set as an apparatus N (1N).

  Further, in the operation flow of the present embodiment, in place of the information providing external device effect-free transmission process (step S170) in the operation flow of the first embodiment, not only the electrical device that provides information but also the mediation server 880 Also, the intermediary server information providing external device effect-free transmission process (step S175) for transmitting the processing effect is performed. Similarly, in place of the information providing external device effect transmission processing (step S180), the mediation server information providing external device effect transmission processing (step S185) is performed. For example, if there is a countermeasure effect by the next reflection processing for the mediation server providing information (step S420), the fault diagnosis countermeasure information holding device network address information is held as it is. On the other hand, if the countermeasure is not effective, the corresponding information is excluded from the fault diagnosis countermeasure information holding device network address information. Also, if there is a difference in type between connected electrical devices, the device network address of the requesting electrical device and the diagnostic response information at the time of failure are stored in the failure diagnosis response information holding device network address information. Newly added.

  In the present embodiment, the following functions and effects are provided in addition to the functions and effects described in the fourth embodiment. That is, first, inquiry processing information regarding the failure is made to the mediation server 880. Then, when it is determined that the intermediary server 880 does not have the corresponding information, the information is inquired to the electrical equipment connected adjacent to the network. Accordingly, it is possible to reduce the time for searching for the handling information for dealing with the failure, rather than making an inquiry to the electrical equipment connected adjacent to the network from the beginning.

It is a figure which shows schematic structure of the conventional vehicle maintenance management apparatus. It is a figure which shows schematic structure of the failure detection diagnosis countermeasure apparatus concerning Embodiment 1, and the failure detection diagnosis countermeasure system of Embodiment 2. FIG. 2 is a diagram illustrating a functional configuration of a failure detection diagnosis coping apparatus according to Embodiment 1. FIG. FIG. 6 is a diagram showing a list of detection diagnosis handling processes in the first embodiment. FIG. 10 is a diagram illustrating a transition in the number of error occurrences in the process of the failure detection processing unit according to the first embodiment. FIG. 10 is a diagram illustrating a flow of task state transition elapsed time investigation processing in the failure detection processing unit of the first embodiment. FIG. 10 is a diagram showing a flow of task queue abnormal array detection processing in the failure detection processing units of the first, fourth, and fifth embodiments. FIG. 3 is a diagram showing an operation flow of the first embodiment. It is a figure which shows schematic structure of the vehicle failure detection diagnosis countermeasure system concerning Embodiment 3. FIG. It is a figure which shows schematic structure of the electric equipment failure detection diagnosis countermeasure system concerning Embodiment 4. FIG. It is a figure which shows schematic structure of the mediation server attached electric equipment fault detection diagnosis countermeasure system concerning Embodiment 5. FIG. FIG. 10 is a diagram showing an operation flow of the fifth embodiment.

Explanation of symbols

1A ... Failure detection diagnosis coping apparatus A
1B: Failure detection diagnosis coping apparatus B
1C: Failure detection diagnosis coping device C
20 ... Input unit 30 ... Communication unit 40 ... Storage unit 50 ... Bus line 60 ... CPU
DESCRIPTION OF SYMBOLS 70 ... Output part 80 ... Failure detection diagnosis coping system 80A ... Automobile failure detection diagnosis coping system 80B ... Electric equipment fault detection coping system 80C ... Intermediary server attached electric equipment fault detection coping system 100 ... Software 300 ... OS (operating system)
310 ... Task management 311 ... Task queue 400 ... Network management 410 ... Network layer 411 ... Routing table 420 ... Transport layer 500 ... Failure detection processing unit 510 ... Detection information management processing 520 ... Software error occurrence frequency transition investigation processing 530 ... Task state transition elapsed time investigation processing 540 ... task queue abnormal array detection processing 600 ... diagnosis processing unit 610 ... self-diagnosis handling information 620 ... diagnosis client processing 630 ... diagnosis server processing 700 ... failure handling processing unit 710 ... handling management processing 720 ... Application task m
722 ... Task state information m
724 ... Constant table m
800A ... Electric equipment 1
800B ... Electric equipment 2
800C ... Electric equipment 3
850A ... Car 1
850B ... Car 2
850C ... Car 3
851A, B, C ... ECU (Electrical Control Unit) 1A, 1B, 1C
852A, B, C ... ECU (Electrical Control Unit) 2A, 2B, 2C
853A, B, C ... ECU (Electrical Control Unit) 3A, 3B, 3C
854A, B, C ... ECU (Electrical Control Unit) 4A, 4B, 4C
855A, B, C ... ECU (Electrical Control Unit) 5A, 5B, 5C
859A, B, C ... ECU (Electrical Control Unit) 9A, 9B, 9C
860A ... In-vehicle LAN (A)
860B ... In-car LAN (B)
860C ... In-vehicle LAN (C)
880 ... Mediation server 900 ... Application 910 ... Application task 1
912 ... Task state information 1
914 ... Constant table 1
920 ... Application task 2
922 ... Task state information 2
924 ... Constant table 2
930 ... Application task n
932. Task state information n
934 ... Constant table n
1000 ... Network

Claims (19)

Provided with a plurality of failure detection diagnosis coping devices connected to the network,
Each of the plurality of failure detection diagnosis coping devices,
A failure detection processing unit for detecting that a failure has occurred;
A storage unit for storing self-diagnosis coping information for failures that have occurred to itself,
The plurality of handling information corresponding to the failure detected by the failure detection processing unit, self-diagnosis handling information stored in the storage unit, or diagnostic handling information corresponding to the failure via the network A diagnostic processing unit to be acquired from any of the failure detection diagnosis coping devices;
A failure detection / diagnosis handling system including a failure handling processing unit that executes processing corresponding to the failure based on the handling information acquired by the diagnosis processing unit and manages the executed processing. In the failure detection diagnosis coping system according to claim 1,
Each of the plurality of failure detection diagnosis coping devices is a failure detection diagnosis coping system that is an ECU (Electrical Control Unit) mounted on an automobile connected to the network via an in-vehicle LAN. In the failure detection diagnosis coping system according to claim 1,
Each of the plurality of failure detection diagnosis coping devices is a failure detection diagnosis coping system that is a microcomputer mounted on an electric device connected to the network by a wired or wireless LAN. In the failure detection diagnosis coping system according to at least one of claims 1 to 3,
Furthermore, a failure detection diagnosis countermeasure information holding device network having device network addresses of each of the plurality of failure detection diagnosis countermeasure devices connected to the network and diagnosis countermeasure information at the time of failure of each of the plurality of failure detection diagnosis countermeasure devices It has a mediation server with address information,
The diagnosis processing unit of each of the plurality of failure detection diagnosis coping devices connected to the network determines whether the failure can be diagnosed based on the self diagnosis coping information when a failure is detected, If it is determined that the diagnosis cannot be made, the failure detection information is transmitted to the mediation server, and the mediation server refers to the failure detection diagnosis handling information holding device network address information based on the reception of the detection information and determines the failure. The device network address of the failure detection diagnosis coping device having the corresponding diagnosis information is searched, and when there is no device network address of the failure detection diagnosis coping device having the diagnosis information corresponding to the failure, the request source on the network Sending the fault detection information to the fault detection diagnosis coping apparatus connected adjacent to the fault detection diagnosis coping apparatus to request the fault diagnosis,
Further, the mediation server receives a result of the coping process for the fault from the fault detection diagnostic coping apparatus of the request source, and fault detection diagnostic that changes the fault detection diagnostic coping information holding apparatus network address information based on the result Coping system. In the failure detection diagnosis coping system according to claim 4,
If the mediation server determines that the result is effective in dealing with the failure based on the result, the failure detection corresponding to the failure detection diagnosis coping apparatus having diagnostic information corresponding to the failure Diagnosis handling information holding device Network address information is retained as it is, and if it is determined that the result is ineffective in dealing with the failure, it corresponds to a failure detection diagnosis handling device having diagnosis information corresponding to the failure Delete the device network address of the failure detection diagnosis coping information holding device network address information,
Further, when it is determined that the result is related to a type of device not included in the failure detection / diagnosis handling information holding device network address information, the failure detection / diagnosis handling information holding device network address information includes the A failure detection diagnosis coping system for newly adding a device network address of a requesting fault detection diagnosis coping device and the diagnosis coping information at the time of the failure. A failure detection processing unit for detecting that a failure has occurred;
A storage unit for storing self-diagnosis coping information for failures that have occurred to itself,
Failure detection diagnosis countermeasures including countermeasure information corresponding to the failure detected by the failure detection processing unit, self-diagnosis countermeasure information stored in the storage unit, or diagnosis countermeasure information corresponding to the failure via a network A diagnostic processing unit obtained from the device;
A failure detection diagnosis coping apparatus, comprising: a coping process processing unit that executes a process corresponding to the fault based on the coping information acquired by the diagnostic processing unit and manages the executed process. In the failure detection diagnosis coping apparatus according to claim 6,
The failure detection processing unit is a failure detection diagnosis coping apparatus that detects that the failure has occurred by detecting an abnormality in task state information indicating an operation state of an application / task. In the failure detection diagnosis coping apparatus according to claim 7,
The task status information includes information in which the number of error processes that occur when the program stored in the storage unit is executed is recorded over time, or failure detection diagnosis that includes information on the execution time and transition destination of each program Coping device. In the failure detection diagnosis coping apparatus according to at least one of claims 6 to 8,
The failure detection processing unit detects the failure by determining an abnormal array of execution tasks from information of a task queue indicating an execution order of tasks managed by the operating system stored in the storage unit. Diagnostic response device. In the failure detection diagnosis coping apparatus according to at least one of claims 6 to 9,
The diagnosis processing unit determines whether or not the failure can be diagnosed based on the self-diagnosis handling information, and when determining that the diagnosis cannot be performed, the failure detection diagnosis connected to the network includes the failure detection information. The diagnosis transmitted from the external device having the diagnosis coping information corresponding to the failure detection information based on the request is transmitted to an external device having the same function as the coping device to request the failure diagnosis of the failure Obtaining the handling information, sending the handling information from the acquired diagnostic handling information to the failure handling processing unit,
Further, the result of the handling process based on the handling information is received from the fault handling processing unit, and the result of the handling process is transmitted to the external device having diagnostic handling information corresponding to the detection information of the fault, and the self-diagnosis The acquired diagnostic countermeasure information is stored in the countermeasure information, or the self-diagnostic countermeasure information is changed based on the diagnostic countermeasure information, and whether there is a failure diagnosis request from the external device connected to the network, and the storage The connection state of the external device connected to the network is detected from the information of the transport layer and the network layer for connecting to the network of the operating system included in the unit, and the external device connected to the network and having a failure Notification of failure, notification of restrictions on the handling process, and handling Failure detection diagnostic cope device to change the alternative to sense. In the failure detection diagnosis coping apparatus according to claim 10,
The diagnosis processing unit receives a failure diagnosis request from the external device, and based on the reception of the failure diagnosis, a diagnosis response corresponding to the failure diagnosis request from the storage unit storing the self-diagnosis response information Information is searched, and when there is corresponding diagnostic countermeasure information, the corresponding diagnostic countermeasure information is transmitted to the requesting external device, and when there is no corresponding diagnostic countermeasure information, it is included in the network layer Based on the routing table, the failure diagnosis request is transmitted to the external device connected to the network, the confirmation result of the diagnosis countermeasure information is sent to the requesting external device, and the diagnosis countermeasure is further transmitted. A failure detection diagnosis coping apparatus that retains, deletes, or changes the self-diagnosis coping information stored in the storage unit based on an information confirmation result. In the failure detection diagnosis coping apparatus according to at least one of claims 6 to 11,
The management of the processing to be handled performed by the failure handling processing unit is a processing for loading and deleting an application task when performing the handling processing, and a processing for adjusting start and stop of the application task, A failure detection diagnosis coping apparatus comprising: processing for adjusting a constant table of the application task. A failure detection processing step for detecting that a failure has occurred;
A diagnostic processing step for acquiring the handling information corresponding to the detected failure from the self-diagnosis handling information stored in its own storage unit or the diagnosis handling information corresponding to the failure via a network;
A failure detection diagnosis coping method, comprising: a coping process step that executes a process corresponding to the fault based on the coping information acquired in the diagnostic processing step and manages the executed process. In the failure detection diagnosis coping method according to claim 13,
The diagnosis processing step determines whether or not the failure can be diagnosed based on the self-diagnosis handling information. If it is determined that the failure cannot be diagnosed, the failure detection diagnosis connected to the network is used as the failure detection information. Sending a coping method to an external device capable of implementing the fault, requesting the fault diagnosis of the fault, and based on the request, the diagnostic coping sent from the external device having diagnostic coping information corresponding to the fault detection information Information is acquired, and the countermeasure information is transmitted from the acquired diagnostic countermeasure information to the fault handling processing unit that performs the fault handling processing step.
Further, the result of the handling process based on the handling information is received from the fault handling processing unit, and the result of the handling process is transmitted to the external device having diagnostic handling information corresponding to the detection information of the fault, and the self-diagnosis The acquired diagnostic countermeasure information is stored in the countermeasure information, or the self-diagnostic countermeasure information is changed based on the diagnostic countermeasure information, and whether there is a failure diagnosis request from the external device connected to the network, and the storage The connection state of the external device connected to the network is detected from the information of the transport layer and the network layer for connecting to the network included in the operating system provided in the unit, and the external device that is connected to the network and has a fault Notification of failure to the device, notification of restrictions on the handling process, and the handling Failure detection diagnosis deal with how to make the change of alternatives to management. In the failure detection diagnosis coping method according to claim 14,
The diagnosis processing step receives a fault diagnosis request from the external device connected to the network, and stores the self-diagnosis handling information from the storage unit storing the self-diagnosis handling information based on the reception of the fault diagnosis. When the diagnostic countermeasure information corresponding to the request is searched and there is corresponding diagnostic countermeasure information, the corresponding diagnostic countermeasure information is transmitted to the requesting external device, and when there is no corresponding diagnostic countermeasure information, Based on a routing table included in the network layer, the failure diagnosis request is transmitted to the external device connected to the network, and the confirmation result of the diagnosis countermeasure information is transmitted to the requesting external device. In addition, a failure detection that retains, deletes, or changes the self-diagnosis handling information stored in the storage unit based on a check result of the diagnosis handling information. Diagnostic Solution. The failure detection diagnosis coping method according to at least one of claims 13 to 15,
The management of the handling performed by the fault handling processing step includes processing for loading and deleting an application task when performing processing corresponding to the fault, processing for adjusting start and stop of the application task, and A failure detection diagnosis coping method comprising: processing for adjusting a constant table of the application task. The failure detection diagnosis coping method according to at least one of claims 14 to 16,
Whether the diagnosis processing step of each of a plurality of external devices capable of executing the failure detection diagnosis coping method connected to the network can diagnose the failure based on the self-diagnosis coping information when a failure is detected If it is determined whether or not diagnosis is possible, the failure detection information includes the failure detection information, the device network address of each of the plurality of external devices, and diagnosis countermeasure information at the time of failure of each of the plurality of external devices. Diagnosis corresponding to the failure from among the plurality of external devices by holding the diagnosis handling information holding device network address information and referring to the failure detection diagnosis handling information holding device network address information based on reception of the detection information The device network address of the external device having the information is searched, and the device number of the external device having the diagnostic information corresponding to the failure is searched. If no network address, and sends to the intermediary step of requesting the failure diagnosis by sending detection information of the failure to the external device connected adjacent to the requester of the external device over the network,
The mediation step, when receiving a result of the handling process for the failure, a failure detection diagnosis handling method for changing the failure detection diagnosis handling information holding device network address information based on the result. In the failure detection diagnosis coping method according to claim 17,
When the mediation step determines that the result was effective in dealing with the failure based on the result, the failure detection diagnostic treatment corresponding to the external device having diagnostic information corresponding to the failure If the information holding device network address information is retained as it is and the result is determined to be ineffective in dealing with the failure, the failure detection corresponding to the external device having diagnostic information corresponding to the failure Delete the device network address in the diagnostic network information holding device network address information,
Further, when it is determined that the result relates to a device type not included in the failure detection / diagnosis handling information holding device network address information, the failure detection / diagnosis handling information holding device network address information A failure detection diagnosis coping method for newly adding a device network address of the requesting external device and the diagnosis coping information at the time of the failure.   A computer-readable failure diagnosis countermeasure program for executing the failure diagnosis countermeasure method according to any one of claims 13 to 18.

Images