JP2004302675A - Remote failure diagnostic system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce load on a user and communication traffic in a remote failure diagnostic system. <P>SOLUTION: In the remote failure diagnostic system, a failure diagnostic server 101 is connected to a failure diagnostic target vehicle 110 through a network and decides whether failures are caused in the diagnostic target vehicle 110 or not by using vehicle data previously acquired from a failed vehicle 111 before the occurrence of failures. Specifically, the failure diagnostic server 101 specifies a traveling condition for acquiring vehicle data to the diagnostic target vehicle 110. The diagnostic target vehicle 110 acquires the vehicle data matched with the traveling condition and transmits the vehicle data to the failure diagnostic server 101. The failure diagnostic server 101 diagnoses failures on the basis of the vehicle data acquired under the specific traveling condition and the vehicle data of the failed vehicle. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a remote failure diagnosis system that diagnoses a failure by connecting to a vehicle remotely.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, various techniques for performing a failure diagnosis of a vehicle are known (Patent Document 1). Patent Document 1 discloses a failure diagnosis device that diagnoses a vehicle using a select monitor (a failure diagnosis device) disposed at a dealer's service factory or the like. That is, according to the invention described in this publication, first, an electronic control device that stores vehicle data such as data of on-vehicle sensors, switches, and actuators is mounted on a vehicle. A monitor (failure diagnosis device) is provided. The select monitor reads the internal data, which are these various vehicle data, from the on-vehicle electronic control device, and also has a measurement function itself, and reads the self-measured vehicle data and the on-vehicle electronic control device. By displaying the internal data at the same time, it is possible to easily compare and examine the corresponding data. In this way, the failure diagnosis device described in this publication makes it possible to easily determine the validity of the data read from the on-vehicle electronic control device and improve the diagnosis efficiency.
Patent Document 2 discloses a failure detection device in which self-diagnosis information of a vehicle is stored in an ignition key, and a failure location, a failure state, and the like are analyzed in detail from diagnosis information read from the ignition key. I have. Specifically, according to the invention described in this publication, when the ignition key is taken out of the cylinder lock, the transmitter of the vehicle outputs self-diagnosis information, the receiver of the ignition key receives this information, and The self-diagnosis information is stored in the ignition key memory. The diagnostic information is read out from the ignition key storing the self-diagnosis information using a key information reader, and input to a personal computer, and the personal computer detects the failure location / failure state in detail. . According to the invention described in this publication, the ignition key is the only part to be removed from the vehicle and carried, so that the dealer who took this key reads the self-diagnosis information from the key and detects the failure location, failure state, etc. can do. Therefore, there is an effect that it is possible to immediately specify the cost required for the failure repair or the replacement part, the delivery date of the vehicle, and the like.
Japanese Patent Application Laid-Open No. H11-163873 discloses a method in which failure diagnosis information based on an abnormality based on self-diagnosis of a vehicle is wirelessly transmitted from the vehicle to the base station, and then the abnormality of the vehicle corresponding to the failure diagnosis information is eliminated (repaired). There is disclosed a vehicle diagnosis system in which the abnormality resolution information (repaired code) is wirelessly transmitted from the vehicle to the base station. According to the invention described in this publication, when the base station receives the failure diagnosis information of the vehicle and subsequently receives the corresponding repaired code, the base station issues a request to the user for inspection, repair, and maintenance of the vehicle to the user. This can be omitted, and unnecessary processing between the vehicle and the base station can be eliminated.
[0003]
However, in each of the above-described conventional technologies, the vehicle itself has a failure diagnosis function, and the failure diagnosis information obtained by the self-failure diagnosis function is transmitted to some means, for example, a failure diagnosis device (select monitor), an ignition key, and the like. , Through wireless transmission to the base station, to contact the outside, including the dealer.
[0004]
On the other hand, Patent Literature 4 proposes a failure diagnosis system that connects to a failed vehicle via a network and diagnoses the location of the failure. According to this conventional technique, by connecting the failure diagnosis system and the vehicle remotely, it is very convenient to know whether the vehicle has failed and the location of the failure without the customer having to go to the service factory. is there.
[0005]
[Patent Document 1]
JP-A-10-10013
[Patent Document 2]
JP-A-11-51817
[Patent Document 3]
JP-A-11-223578
[Patent Document 4]
JP-A-2002-228552.
[0006]
[Problems to be solved by the invention]
By the way, in order to perform a failure diagnosis, it is necessary to sample vehicle data such as sensor output and control data that change every moment and transmit the vehicle data to the failure diagnosis system.
[0007]
Furthermore, some types of failures may only be reproduced under certain driving conditions. For example, it is often heard that a driver feels an abnormality while driving and enters the vehicle at a dealer or a maintenance shop, but the failure is not reproduced at that time.
[0008]
In view of the above, an object of the present invention is to reduce the burden on the user side regarding data necessary for vehicle failure diagnosis and communication traffic.
[0009]
[Means for Solving the Problems]
In order to achieve the above object, a remote failure diagnosis system according to the present invention has the following configuration.
[0010]
The first invention of the present application is required when a failure diagnosis is performed for a predetermined failure in a remote failure diagnosis system that remotely performs a failure diagnosis on a diagnosis target vehicle and transmits a failure diagnosis result to a customer. Determining means for determining a driving condition; transmitting means for transmitting the determined driving condition to the vehicle to be diagnosed; and receiving to receive vehicle data acquired in accordance with the driving condition from the vehicle to be diagnosed. Means, failure diagnosis means for performing a failure diagnosis on the predetermined failure based on the received vehicle data, and notification means for notifying a customer of the diagnosis target vehicle of a failure diagnosis result by the failure diagnosis means. It is characterized by having.
[0011]
According to a second aspect of the present invention, in a remote failure diagnosis system for remotely executing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer, a predetermined diagnosis is performed based on vehicle data received from the diagnosis target vehicle. First failure diagnosis means for performing failure diagnosis on a failure, determination means for determining whether more detailed failure diagnosis is required based on the result of the failure diagnosis, and determination that more detailed failure diagnosis is required Requesting means for requesting vehicle data under specific driving conditions required for performing the more detailed failure diagnosis; and receiving vehicle data acquired in accordance with the driving conditions from the vehicle to be diagnosed. A receiving unit, a second failure diagnosing unit that executes a more detailed failure diagnosis than the first failure diagnosing unit based on the received vehicle data, and a second failure diagnosing unit. And having a notifying means for notifying the disability diagnosis result to the customer of the diagnosis target vehicle.
[0012]
It should be noted that the predetermined failure may be characterized by high reproducibility under specific driving conditions. In addition, the failure diagnosis system includes a database that stores driving conditions when acquiring vehicle data and vehicle data of the failed vehicle for each of the plurality of failures, wherein the failure diagnosis unit includes the failure diagnosis vehicle. The vehicle data of the failed vehicle may be compared with the vehicle data of the failed vehicle stored in the database to determine whether a failure has occurred.
[0013]
The traveling condition may be defined by a combination of a plurality of behaviors of the vehicle. In addition, the determination unit may determine a type of vehicle data to be acquired in the diagnosis target vehicle, a sampling condition when acquiring the vehicle data, and the like. The transmission means may transmit information specifying a type of vehicle data to be acquired in the vehicle to be diagnosed, together with the traveling condition. In addition, the transmission unit may transmit information specifying a sampling condition when acquiring the vehicle data, together with the traveling condition.
[0014]
According to a third aspect of the present invention, there is provided a vehicle to be diagnosed which is diagnosed by any one of the above-described remote failure diagnosis systems, wherein: a means for receiving the traveling condition from the remote failure diagnosis system; Means for acquiring vehicle data in accordance with: a means for transmitting the acquired vehicle data to the remote fault diagnosis system; a means for receiving a fault diagnosis result from the remote fault diagnosis system; Means for outputting a diagnosis result. It is to be noted that the vehicle data further includes means for determining whether a predetermined time has elapsed from a previous acquisition time, and means for prohibiting the acquisition or transmission of the vehicle data if the predetermined time has not elapsed. You may. Further, a change unit for changing the length of the predetermined time may be further provided. Further, the changing means may change the predetermined time based on a change command from a remote failure diagnosis system. Further, the changing unit may set the predetermined time to a longer interval when the vehicle data acquired last time and the vehicle data acquired this time have not substantially changed. Further, the apparatus may further include a deletion unit that deletes the received traveling condition when a predetermined deletion condition is satisfied.
[0015]
According to a fourth aspect of the present invention, in a remote failure diagnosis system for remotely performing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer, vehicle data of the failed vehicle required for the failure diagnosis is stored. A database, request means for requesting vehicle data under specific driving conditions required for updating to one or more failed vehicles when an update request for the database is issued, and vehicle data received from the failed vehicle Updating means for updating the contents of the database based on the information.
[0016]
The above-mentioned object is also achieved by a remote failure diagnosis method corresponding to a remote failure diagnosis system having each of the above configurations.
[0017]
Further, the above object is also achieved by a program for realizing each means included in the remote failure diagnosis system by a computer, and a computer-readable storage medium storing the program code.
[0018]
【The invention's effect】
According to the present invention, a remote failure diagnosis system, a remote failure diagnosis method, and a vehicle to be diagnosed, which can reduce the burden on the user side and communication traffic concerning data required for vehicle failure diagnosis as compared with the related art, are realized.
[0019]
That is, according to the first, second, eighth, fifteenth, sixteenth, eighteenth and nineteenth aspects of the present invention, the remote failure diagnosis system determines a traveling condition for determining a timing for acquiring vehicle data necessary for the diagnosis by the diagnostic vehicle. , Unnecessary transmission of vehicle data can be suppressed, and the burden on the user side and communication traffic can be reduced.
[0020]
According to the third aspect of the invention, it is possible to diagnose a failure with high reproducibility under a specific traveling condition.
[0021]
According to the invention described in claim 4, by storing the vehicle data according to the corresponding driving conditions for each type of failure in a database, it is possible to compare the data with the data of the actual failed vehicle. Also, an accurate failure diagnosis result may be obtained.
[0022]
According to the fifth aspect of the present invention, by defining the traveling condition by a combination of a plurality of behaviors of the vehicle, a failure diagnosis result with higher accuracy than before can be obtained especially for a failure depending on the behavior of the vehicle. I will get it.
[0023]
According to the sixth aspect of the present invention, it is possible to transmit only vehicle data necessary for failure diagnosis to the remote failure diagnosis system among various vehicle data that can be acquired in the vehicle. Traffic can be reduced.
[0024]
According to the seventh aspect of the present invention, by specifying the sampling conditions when acquiring vehicle data, for example, for those having a small time change, a longer sampling interval can be set, and the size of the vehicle data is reduced. Let's do it.
[0025]
According to the invention described in claim 8, a vehicle suitable for the above-described failure diagnosis system is provided.
[0026]
According to the ninth aspect of the present invention, when the predetermined time has not elapsed since the previous acquisition time of the vehicle data, transmission or acquisition of the vehicle data is prohibited, so that similar vehicle data is transmitted to the failure diagnosis system. Communication and processing waste due to transmission can be reduced.
[0027]
According to the tenth aspect, for example, when a more detailed diagnosis is to be performed, the number of transmissions of the vehicle data can be increased by shortening the predetermined time. On the other hand, by changing the predetermined time longer, it is possible to reduce communication traffic.
[0028]
According to the eleventh aspect, the predetermined time can be changed according to the convenience of the failure diagnosis system. For example, when the load on the failure diagnosis system is heavy, the predetermined time can be set longer to suppress transmission of vehicle data.
[0029]
According to the twelfth aspect of the invention, when it is expected that the diagnosis result does not change even when the vehicle data is transmitted, such as when the change in the vehicle data is poor, the transmission of the vehicle data is suppressed and the communication traffic is reduced. And the load on the failure diagnosis system and the vehicle side can be reduced.
[0030]
According to the thirteenth aspect, when a predetermined deletion condition is satisfied, such as when transmission of vehicle data under specific driving conditions becomes unnecessary, the driving condition is deleted and the vehicle returns to the normal state. Can be.
[0031]
According to the inventions described in claims 14, 17 and 20, when updating the failure diagnosis database, it becomes possible to request only the vehicle data required for the update from the vehicle. The load associated with processing can be reduced.
[0032]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of a remote failure diagnosis system according to the present invention will be described in detail with reference to the drawings. In the following, there may be embodiments that seem at first glance not to be described in the claims, but these are not intentionally excluded. For example, since it is equivalent to the invention described in the claims, it may not be described in the claims.
[0033]
[First Embodiment]
FIG. 1 is a diagram illustrating a configuration example of a system according to the present embodiment. The information center 100 is a group of computers that accumulates various types of information transmitted from the customers' vehicles 110 and 111, the service factory 120, and the like, and provides a failure diagnosis result. The information center 100 is connected to a customer's vehicle 110 and service factory 120 via the Internet 130, a mobile communication line, or the like.
[0034]
The customer's vehicles 110 and 111 acquire data necessary for failure diagnosis and transmit the data to the information center 100.
[0035]
The service factory 120 is a so-called repair shop or the like, and reads out vehicle data from the failed vehicle 111 and transmits information on the location of the failure and the cause of the failure to the information center 100. In the service factory, a client device for the service factory is set. The client device is a kind of computer, and includes a CPU, a memory, a hard disk drive, a communication interface, and the like. In the following description, various processes are executed by the CPU executing a program corresponding to the flowchart.
[0036]
The information center 100 includes a failure diagnosis server 101 that executes a failure diagnosis process, a customer information database 102 that stores information of customers (all customers or contractors of the failure diagnosis service), a failure vehicle 111 and a service factory. A failure information database 103 storing the failure data transmitted from the client device 121, a vehicle information database 104 storing the vehicle data transmitted from the customer's vehicles 110 and 111, and information relating to the location of the service factory and the like are stored. A service factory database 105, a map database 106 storing map data, and a diagnostic program database 107 storing various programs for diagnosing failures are included.
[0037]
The failure diagnosis server 101 is a kind of computer, and includes a CPU, a memory, a hard disk drive, a communication interface, and the like. In the following description, various processes are executed by the CPU executing a program corresponding to the flowchart.
[0038]
The failure diagnosis server 101 determines, for example, a driving condition (eg, a CPU of the failure diagnosis server 101) required to execute a failure diagnosis for a predetermined failure, and determines the determined traveling condition. Transmission means for transmitting to the diagnosis target vehicle 110 (for example, a communication interface of the failure diagnosis server 101) and reception means for receiving vehicle data acquired in accordance with the traveling conditions from the diagnosis target vehicle (for example, failure A communication interface of the diagnosis server 101), a failure diagnosis unit (eg, a CPU of the failure diagnosis server 101) for performing a failure diagnosis for the predetermined failure based on the received vehicle data, and a failure diagnosis by the failure diagnosis unit Notification means for notifying the customer of the diagnosis target vehicle of the result (eg, a communication interface of the failure diagnosis server 101); Fault diagnosis system having is realized.
[0039]
FIG. 2 is a block diagram illustrating a configuration example of the vehicle according to the present embodiment. The remote vehicle client device 200 is a main controller including a CPU, a memory, and the like, acquires control data and sensor outputs from various control units and sensors, accumulates the acquired data in a memory, and stores the accumulated information in a mobile terminal (mobile communication interface). ) 250 or the short-range wireless communication interface 255 to transmit to the information center 100 or receive a failure prediction result from the information center 100. The short-range wireless communication interface 225 can employ a wireless standard for wireless LAN, Bluetooth, and ETC.
[0040]
The body system 210 includes a power window unit 211, a headlight unit 212, an audio unit 213, an air conditioner unit 214, a wiper unit 215, a door lock unit 216, and the like, and transmits control results and data such as current and voltage to a vehicle client device. Output to 200.
[0041]
The control system system 220 includes an ABS (antilock brake system) 221 for controlling the brake not to lock, a DSC (dynamic stability controller) 222 for controlling the behavior of the vehicle, and an EGI for controlling the fuel supply. (Electric Gas Injection) 223, EAT (Electric Automatic Transmission) 224 for controlling the automatic transmission, ICCW (Intelligent Cruise Control & Warning) 225 for assisting driver's driving such as automatic driving, etc. The control result is notified to the client device 220 for use.
[0042]
Various sensors are mounted on the vehicle. For example, a GPS sensor 231 that receives a radio wave from a GPS (Global Positioning System) satellite to calculate the current position of the vehicle, a VICS information receiver 232 that receives traffic congestion information and the like, and a vehicle speed sensor 233 that detects the speed of the vehicle An inter-vehicle distance sensor 234 for measuring a distance from another vehicle such as a preceding vehicle, a yaw rate sensor 235 for detecting a yaw rate of the vehicle, an acceleration sensor for detecting acceleration of the vehicle, a steering angle sensor 237 for detecting a steering angle of the vehicle, A throttle opening sensor 238 for detecting the opening of the throttle, a brake pressure sensor 239 for detecting the pressure applied to the brake, a blinker SW sensor 240 for detecting the operating state of the blinker switch, an outside air temperature sensor 241 for measuring the outside air temperature, and Rain sensor 24 that measures whether or not it is raining and the amount of rain Such as is mounted on the vehicle.
[0043]
The navigation controller 260 is a device that searches map information stored in a hard disk drive or the like based on positioning data from the GPS sensor 231 and displays a map of the current position. The input / output device 270 for the driver serving as a customer includes a display device such as a liquid crystal display and a voice main device, and outputs map data from the navigation controller 260 and outputs a failure diagnosis result from the information center 100. Or
[0044]
A means (eg, mobile communication interface 250, short-range wireless communication interface 255, or the like) for receiving the traveling condition from a remote failure diagnosis system (eg, failure diagnosis server 101) by the vehicle shown in FIG. Means for obtaining vehicle data in accordance with the obtained driving conditions (eg, the vehicle client device 200, the GPS sensor 231 and the like), and means for transmitting the obtained vehicle data to the remote failure diagnosis system (eg, mobile) Communication interface 250, short-range wireless communication interface 255, etc.), means for receiving a failure diagnosis result from the remote failure diagnosis system (eg, mobile communication interface 250, short-range wireless communication interface 255, etc.), and Means for outputting a diagnosis result (eg, input / output device 270, etc.) Diagnosed vehicle including is realized.
[0045]
FIG. 3 is a diagram showing a configuration example of the service factory 120. The service factory client 121 reads out the failure diagnosis information from the tester 301 and the vehicle data before the failure stored in the vehicular client device 200 mounted on the failed vehicle 111, and displays the failure that indicates the failure that has occurred. It is a computer that transmits the information to the information center 100 together with the identification code. The service factory client 121 also includes a communication interface for communicating with the information center 100. When communicating with the vehicle, it can be connected to the vehicle 111 via the short-range wireless communication interface 310, for example. The tester 301 is a device that performs a detailed failure diagnosis by connecting to a connector provided in a failed vehicle.
[0046]
FIG. 4 is a flowchart relating to collection of vehicle data according to the present embodiment. In particular, in the flow chart, vehicle data including normal vehicle data is collected and a vehicle information database is created. In other words, if there is vehicle data of a normal vehicle, it becomes easier to find the characteristics of the vehicle data of the failed vehicle, and it is also useful for creating a failure model to be used at the time of failure diagnosis and determining running conditions for a specific failure. .
[0047]
In step S400, the CPU mounted on the vehicle client device 200 samples outputs from various sensors and units at appropriate timings, and stores them in the memory.
[0048]
In step S402, the CPU mounted on the vehicle client device 200 performs predetermined timing (for example, periodically, at the time of engine start, after a predetermined time has elapsed after engine start, and when an explicit instruction is input by the driver, etc.). ), The vehicle data stored in the memory is read, information for specifying the vehicle or the driver is added, and the information is transmitted to the information center 100 via the mobile communication interface 250 or the short-range wireless communication interface 255.
[0049]
In step S410, the failure diagnosis server 101 of the information center 100 receives the vehicle data transmitted from the vehicle via a mobile communication interface or the like. In step S412, the failure diagnosis server 101 stores the received vehicle data in the vehicle information database 104 in association with the information specifying the corresponding vehicle or driver.
[0050]
By the above procedure, vehicle data on a normal vehicle that has not failed is stored in the vehicle database 104.
[0051]
FIG. 5 is a flowchart relating to collection of failure data used for failure diagnosis. There are generally two methods for collecting failure data. One is a method of reading failure data from a failed vehicle and writing the failure data in the failure information database 103 (steps S500 and S502). The other is a method in which the failure data is read from the failed vehicle 111 by the client device 121 of the service factory into which the failed vehicle 111 is stored, and then written from the client device 121 of the service factory to the failure information database 103 (S510, S512).
[0052]
In step S500, the vehicle client device 200 mounted on the failed vehicle 111 determines whether transmission of the failure data is specified by the customer who has recognized the occurrence of the failure, or when an abnormality is detected in the various control devices (for example, a warning is issued). When the lamp is turned on), the running conditions at the time of the failure, the failure occurrence time, the vehicle number (vehicle number), the failure identification code, and the like are read from the memory to create failure data. The failure occurrence time and the failure identification code may be input by the customer operating the input / output device 270 or a failure code corresponding to a warning lamp or the like. Information useful for specifying a vehicle, such as a vehicle number, may be read from, for example, information stored in a ROM or the like.
[0053]
When the vehicle client device 200 is equipped with a failure diagnosis program, the failure diagnosis program is executed to constantly, periodically, or at a predetermined timing (such as when operating a switch) receive signals from various sensors and units. Obtain the data and monitor the occurrence of the failure, and when the occurrence of the failure is detected, determine the running conditions at the time of the failure, the failure occurrence time, and the failure identification code corresponding to the occurred failure, create the failure data, It can be uploaded to the information center 100.
[0054]
In step S502, the vehicle client device 200 transmits the vehicle data and the failure data stored in the memory to the failure diagnosis server 101 in the information center 100. In step S504, the failure diagnosis server 101 receives the vehicle data and the failure data via the Internet 130. In step S506, failure diagnosis server 101 stores the received vehicle data in vehicle information database 104. In step S508, the failure diagnosis server 101 stores the received failure data in the vehicle information database.
[0055]
As described above, the failure data and the vehicle data serving as the judgment factors for use in the failure diagnosis are stored in each database. The failure data and its vehicle data can be said to be a failure model, but in the data mining method, this failure model is constantly changing as data is added every moment, and it can be compared with other data. It is determined at the stage of. In that sense, the process in which the failure diagnosis server 101 registers the received failure data in the failure information database 103 or the vehicle information database 104 and the process in which desired vehicle data is extracted therefrom corresponds to a failure model creation process. I can say.
[0056]
Incidentally, the failure data and the vehicle data may be collected from the service factory 120. In step S510, the tester 301 is connected to the failed vehicle 111, and a failure diagnosis is performed. In this failure diagnosis, the tester 301 and / or the client device 121 reads the vehicle data stored in the memory of the failed vehicle 111 and performs a detailed investigation, or transmits a specific inspection signal to various units. Then, failure data is created by checking response data from various units.
[0057]
Note that the service factory client 121 may connect to the failed vehicle 111 via the wireless communication interface 310 and read vehicle data stored in the memory. In this case, the service factory client device 121 It is also possible to execute a diagnostic program and make a detailed diagnosis of the failure location to create failure data. In step S512, the client device 121 for the service factory transmits the created failure data and the vehicle data read from the failed vehicle to the failure diagnosis server 101 of the information center 100. After that, the processing after step S504 is executed.
[0058]
As described above, two methods have been exemplified for collecting failure data. However, the latter method has an advantage that a more detailed diagnosis result can be obtained because a specialized diagnostic device that is too expensive to be mounted on a vehicle can be used. .
[0059]
FIG. 6 is a flowchart of the remote failure diagnosis processing according to the present embodiment.
[0060]
In step S600, upon detecting that a failure diagnosis request has been input from the input / output device 270, the vehicle client device 200 transmits a failure diagnosis request to the failure diagnosis server 101 of the information center 100. Note that the failure diagnosis trigger may be triggered not only by the driver, but also periodically or when the vehicle client device 200 satisfies a certain condition, or by the failure diagnosis server 101 periodically or The trigger may be performed when a specific condition is satisfied, or may be triggered when a failure is detected (a warning lamp is turned on) by a failure detection device mounted on the vehicle. When the type of failure to be diagnosed is designated from the input / output device 270, the vehicle client device 200 mounts the designated failure type (such as a failure code) in the failure diagnosis request. .
[0061]
In step S602, the failure diagnosis server 101 receives a failure diagnosis request via a communication interface.
[0062]
In step S604, the failure diagnosis server 101 determines the type of failure to be diagnosed. For example, the determination may be made based on information on the type of failure included in the failure diagnosis request. The number of failure types may be one or more. When the type of failure is not included in the failure diagnosis request, all diagnoseable failures (for example, i = 0th failure code to i = nth failure code) may be determined as targets, Alternatively, the breakdown may be narrowed down to a failure having a high urgency.
[0063]
In step S606, the failure diagnosis server 101 determines a traveling condition corresponding to the failure determined as a diagnosis target. Note that two or more running conditions may be determined.
[0064]
FIG. 7 is a diagram showing the contents of the failure information database and the vehicle information database and the concept of the failure diagnosis. For example, when the failure represented by the failure code E0001 is determined as a diagnosis target, the failure diagnosis server 101 refers to the failure information database 103 and extracts a traveling condition corresponding to the failure code E0001. In this example, the traveling condition is traveling on a curve of 130R at a speed of 50 km / h.
[0065]
In step S608, the vehicle diagnosis server 101 transmits information on the determined driving conditions to the diagnosis target vehicle 110. The vehicle diagnosis server 101 may add an identification number (running condition ID) to the running condition, and register the vehicle number of the vehicle to be diagnosed and the transmitted running condition ID in the database in association with each other. Good. Since it is assumed that it may take a long time for the vehicle to be diagnosed to meet the driving conditions, it is possible to determine which vehicle is the vehicle to be diagnosed and under what driving conditions the failure diagnosis server 101 It is necessary to manage by.
[0066]
In step S610, the vehicular client device 200 receives the information on the driving condition via the mobile communication interface 250 or the like and stores the information in a storage device such as a RAM.
[0067]
In step S612, the vehicle client device 200 determines whether output data from a sensor or a control device related to the traveling condition satisfies the traveling condition stored in the RAM, and waits until the data is satisfied. . For example, if the traveling condition is that the vehicle is traveling on a 130R curve at a speed of 50 km / h, the navigation controller 260 determines whether the vehicle is traveling on a curve that is approximately 130R based on information from the GPS sensor 231. It is determined whether the output of the vehicle speed sensor 233 is approximately 50 km / h. When these conditions are satisfied, the process exits the standby loop and proceeds to the next step.
[0068]
In step S614, the vehicle client device 200 samples vehicle outputs from various sensors and control devices to create vehicle data, and stores the vehicle data in a storage device such as a RAM or a hard disk.
[0069]
In step S616, the vehicle client device 200 reads the vehicle data from the storage device and transmits the vehicle data to the failure diagnosis server 101.
[0070]
In step S618, the failure diagnosis server 101 receives the vehicle data via the communication interface and stores the data in the vehicle information database. In the example of FIG. 7, a number for specifying a vehicle, a yaw rate as an example of vehicle data, running conditions when the vehicle data is acquired, and the like are stored in the vehicle information database 104.
[0071]
In step S620, the vehicle diagnosis server 101 determines whether a failure has occurred in the diagnosis target vehicle 110 based on the vehicle data of the failed vehicle and the vehicle data of the diagnosis target vehicle.
[0072]
In step S622, the vehicle diagnosis server 101 transmits information on the failure diagnosis result to the diagnosis target vehicle 110.
[0073]
In step S624, the vehicle client device 200 receives the information on the failure diagnosis result.
[0074]
In step S626, vehicle client device 200 outputs the received failure diagnosis result from input / output device 270.
[0075]
The remote failure diagnosis is executed according to the above flow. Note that the remote diagnosis processing is terminated by receiving the diagnosis result. At this time, the vehicle client device 200 deletes the running conditions stored in the storage device. This is because, if not deleted, the traveling condition is always valid, and vehicle data is acquired and transmitted when the traveling condition is satisfied.
[0076]
Note that the vehicle client device 200 may execute the deletion of a specific driving condition when a predetermined deletion condition is satisfied, such as when receiving a driving condition deletion command from the failure diagnosis server 101. Further, the vehicle client device 200 may continue to acquire and transmit the vehicle data every time the traveling condition is met until the transmission end command of the vehicle data is received from the failure diagnosis server 101.
[0077]
FIG. 8 is a detailed flowchart of the failure diagnosis processing. In step S800, the failure diagnosis server 101 extracts the vehicle data of the vehicle 110 to be diagnosed from the vehicle information database 104 for the i-th failure (the initial value of i is 0) which is the diagnosis target. To explain with reference to the example of FIG. 7, the corresponding vehicle data is specified and read out from the vehicle number of the diagnosis target vehicle 110 and the traveling conditions.
[0078]
In step S802, the failure diagnosis server 101 extracts the vehicle data of the failed vehicle 111 from the vehicle information database 104 for the i-th failure to be diagnosed (the initial value of i is 0). To explain with reference to the example of FIG. 7, corresponding vehicle data is specified and read out from the vehicle number of the failed vehicle 111 and the traveling conditions.
[0079]
In step S804, the failure diagnosis server 101 compares the read vehicle data of the diagnosis target vehicle 110 with the vehicle data of the failed vehicle 111, and the two are the same to the extent that similar failure is considered to have occurred. Or, determine whether or not they are similar. If they are the same or similar, the process proceeds to step S806; otherwise, the process proceeds to step S708. At the time of failure diagnosis, it may be compared with vehicle data of another normal vehicle. That is, the failure diagnosis server 1010 compares the vehicle data of another normal vehicle with the vehicle data of the diagnosis target vehicle 110, and determines that an abnormality (failure) has occurred if the vehicle data is not statistically within an error range. . Alternatively, the vehicle data of both the failed vehicle and the normal vehicle may be compared to determine which is more similar. As specific data processing, a data mining method such as MBR (Memory Based Reasoning) can be used. If MBR is applied, since a failure model or a normal model is created by directly using a large amount of failure data or vehicle data, there is a merit that prior modeling is not required unlike other methods. Therefore, diagnosis of a new failure that did not exist in the past can be realized only by adding new failure data as needed without changing the system. Further, since the failure diagnosis is performed based on the past failure facts (failure data), the basis of the failure is clear, and the reliability of the failure diagnosis will be higher than in the related art. Furthermore, since inference is performed with a subset of data (for example, vehicle data having the following time width T), it has a strong characteristic against noise.
[0080]
In step S806, the failure diagnosis server 101 adds the i-th failure identification code to the failure list. The failure list is stored in storage means such as a memory or a hard disk drive.
[0081]
In step S808, it is determined whether the failure diagnosis has been completed for all the failure codes. If not completed, the value of i is incremented in step S830, and the process returns to step S800 to perform a failure diagnosis for the next failure identification code.
[0082]
In step S810, the failure diagnosis server 101 reads the failure list stored in the storage unit and determines which failure identification code is registered. If any failure identification code is registered, it means that a failure corresponding to the failure identification code has occurred. If the failure code has not been registered, the process proceeds to step S822. If at least one failure is found, the process proceeds to step S820.
[0083]
In step S820, the failure diagnosis server 101 creates a failure diagnosis result (prediction report) for reporting to the driver. For example, the fault identification codes registered in the fault list may be sorted by urgency to generate a fault diagnosis result. This failure diagnosis result may include, for example, all discovered failures, or only failures that could impede operation or those with a high degree of urgency that are directly related to safety. You may. This is because there is a possibility that some drivers may be overly anxious if a low urgency level is notified, so that only a high urgency level is notified.
[0084]
Further, when the urgency of a failure is high, a failure diagnosis result reflecting the urgency may be created. This will make it easier for the driver to grasp the degree of urgency.
[0085]
In step S822, the failure diagnosis server 101 creates a diagnosis result indicating that there is no failure and stores it in the storage unit. As a result of the diagnosis, for example, "I could not confirm the occurrence of a failure. Please enjoy comfortable driving." Or "I could not confirm the occurrence of a failure at this time. Or "The failure could not be confirmed at this time. However, failures may occur unexpectedly, so be sure to carry out pre-operation inspections and periodic inspections." Message.
[0086]
As described above, in the invention according to the present embodiment, it is only necessary to transmit the vehicle data of the vehicle to be diagnosed when a specific traveling condition is met, so that the load on the vehicle side and the server side can be reduced as compared with the related art, Further, communication traffic can be reduced. Further, there is an advantage that a failure that occurs only under a specific traveling condition can be efficiently detected.
[0087]
[Second embodiment]
A second embodiment based on the remote fault diagnosis system according to the first embodiment will be described. In the following description, the same configuration as that of the first embodiment will not be described repeatedly, and will be described focusing on the characteristic portions of the present embodiment.
[0088]
In the second embodiment, a simple diagnosis is performed based on normal vehicle data, and as a result, when it is determined that detailed diagnosis is necessary, the vehicle data is acquired by specifying driving conditions and the like, and the detailed diagnosis is performed. Is to execute.
[0089]
FIG. 9 is a flowchart related to the failure diagnosis according to the second embodiment. Steps common to those in FIGS. 4 and 6 are denoted by the same reference numerals to simplify the description. In step S400, the diagnosis target vehicle 110 transmits the vehicle data at a predetermined timing, and in step S410, the failure diagnosis server 101 receives the vehicle data. At this time, since the running conditions and the like are not specified for the vehicle data, the data amount may be reduced by increasing the sampling interval.
[0090]
In step S904, failure diagnosis server 101 performs a failure diagnosis based on the received vehicle data. Here, the failure diagnosis is executed according to the flowchart shown in FIG.
[0091]
In step S905, the failure diagnosis server 101 determines whether more detailed diagnosis is necessary based on the failure diagnosis result. For example, although the comparison result does not indicate a value that can be concluded as a failure, if it is close to it, it is determined that detailed diagnosis is necessary. The numerical value here is a value indicating the degree of coincidence between the vehicle data of the failed vehicle and the vehicle data of the vehicle to be diagnosed, and a correlation value or the like obtained by a correlation operation may be employed. As a result of the determination, if detailed diagnosis is necessary, the process proceeds to step S606, and a traveling condition corresponding to the failure targeted for detailed diagnosis is determined. On the other hand, when detailed diagnosis is unnecessary, the process proceeds to step S622.
[0092]
As described above, according to the present embodiment, there is provided a remote failure diagnosis system (e.g., failure diagnosis server 101 or the like) that performs a failure diagnosis on a diagnosis target vehicle 110 remotely and transmits a failure diagnosis result to a customer. A first failure diagnosis unit (eg, CPU of the failure diagnosis server 101, step S904) for performing a failure diagnosis for a predetermined failure based on the vehicle data received from the diagnosis target vehicle 110; A determination unit (eg, CPU of the failure diagnosis server 101, step S905) for determining whether more detailed failure diagnosis is necessary based on the failure diagnosis. Requesting means (eg, CPU of the failure diagnosis server 101, step S608) for requesting vehicle data under specific driving conditions necessary for executing A receiving unit (for example, step S618) for receiving vehicle data acquired according to running conditions from the vehicle to be diagnosed, and more detailed than the first failure diagnostic unit based on the received vehicle data. Second failure diagnosis means for executing failure diagnosis (eg, CPU of failure diagnosis server 101, step S620), and notification for notifying a customer of the vehicle to be diagnosed of a failure diagnosis result by the second failure diagnosis means. A remote fault diagnosis system having means and (eg, CPU of fault diagnosis server 101, step S622) is provided.
[0093]
Further, in the present embodiment, for example, when the vehicle data is transmitted at a regular timing or the like, the failure diagnosis can be performed. Therefore, even when the driver forgets to perform the failure diagnosis, the failure diagnosis is automatically performed. Diagnosis results can be reported.
[0094]
Also, at the time of normal failure diagnosis, simple diagnosis is performed with vehicle data having a small data amount, and when the possibility of failure is confirmed, more detailed vehicle data is obtained by specifying driving conditions and the like to obtain detailed vehicle data. By performing the failure diagnosis, the data size of the vehicle data can be normally suppressed. Further, since the vehicle data for detailed diagnosis is transmitted when the vehicle satisfies the running conditions, the amount of vehicle data transmitted in total can be reduced in a long time. Further, a failure that can be easily reproduced under a specific driving condition can be efficiently found.
[0095]
[Third Embodiment]
In the above-described embodiment, the failure diagnosis is triggered mainly from the diagnostic vehicle side. However, the present invention is not limited to this, and a trigger can be applied from the information center 100 side.
[0096]
FIG. 10 is a flowchart of the failure diagnosis according to the third embodiment. Steps S600 and S602 in FIG. 6 are replaced with step S1002. In step S1002, the failure diagnosis server 101 determines whether it is a predetermined timing to start diagnosis. The predetermined timing may be a regular timing such as once a week, a timing requested by the quality department, or a time when the use of automobiles increases such as the first day of consecutive holidays. . Alternatively, the previous diagnosis time is stored in the storage device, and a request for diagnosis is transmitted from the vehicle even after a certain period of time.
As described above, in the present embodiment, even when there is no diagnosis request from the vehicle or the user side, the failure diagnosis server 101 starts the diagnosis at a necessary time, so that the driver can execute the failure diagnosis. Even if you have forgotten, you can automatically report the failure diagnosis result. Further, since the operation on the user side at the start of the diagnosis is not required, usability will be improved for the user.
[0097]
If no failure is found, the failure diagnosis server 101 may end the process without notifying the driver of the diagnosis result. Thereby, it is possible to suppress transmission of useless information to the driver. Further, in the present embodiment, since the failure diagnosis is performed without the driver being conscious, if the occurrence of a failure is not found, it may be preferable to keep the driver unaware as it is possible to concentrate on driving. unknown.
[0098]
[Fourth embodiment]
In the present embodiment, useless traffic due to transmission of the same or similar vehicle data every time is suppressed, and a failure diagnosis is performed efficiently. FIG. 11 is a flowchart of the failure diagnosis processing according to the present embodiment. In the flowcharts shown in FIGS. 6, 9, and 10, processing unique to the present embodiment is added between steps S610 and S612.
[0099]
In step S1111, the vehicle client device 200 reads the previous diagnosis time stored in the storage device in advance, compares the diagnosis time with the current time, and determines whether a predetermined time has elapsed. . If the predetermined time has elapsed, the process proceeds to step S612, and vehicle data that matches the traveling conditions is acquired. Otherwise, the current vehicle data is not considered to be significantly different from the previous vehicle data, so that the vehicle waits for a predetermined time. The predetermined time may be, for example, a unit of one day or one week, or may be set to a time at which a significant change appears empirically.
[0100]
As described above, in the present embodiment, the failure diagnosis is executed by acquiring the vehicle data after the elapse of a predetermined time from the previous diagnosis time. It is possible to avoid such a situation. That is, since acquisition and transmission of vehicle data are performed when a meaningful diagnosis result is obtained, there is an advantage that unnecessary acquisition and transmission of vehicle data can be omitted.
[0101]
In step S1002, the purpose is achieved by waiting until a predetermined time has elapsed, but another method may be used. For example, the vehicle client device 200 stores the previous vehicle data in a storage device such as a hard disk drive, compares the currently obtained vehicle data with the previous vehicle data, and substantially differs from the previous vehicle data. In this case, the current vehicle data may be transmitted to the failure diagnosis server 101.
[0102]
Instead of the predetermined time, a condition that the vehicle has traveled a predetermined distance from the time of the previous diagnosis may be used. The vehicle client device 200 stores the value of the mileage meter at the time of the previous diagnosis in the storage device, and determines whether or not the vehicle has traveled beyond a predetermined distance such as 100 km or 1000 km from the storage device. Good.
[0103]
Further, the vehicle client device 200 may appropriately correct the predetermined time. For example, the vehicle client device 200 compares the currently acquired vehicle data with the previous vehicle data, and if they are not substantially different, transmits the vehicle data for the time being and sets a predetermined time longer than before. Also set longer. As described above, when there is not much change in the vehicle data, frequent transmission of the vehicle data is useless, and the transmission timing may be gradually lengthened. By setting the sampling period longer than before, instead of changing the transmission period, the size of vehicle data transmitted at one time can be reduced. Note that the failure diagnosis server 101 may make a similar determination and instruct the vehicle client device 200 to change the predetermined time.
[0104]
As described above, according to the present embodiment, the vehicle client device 200 prohibits transmission of vehicle data until a predetermined condition is satisfied, so that useless communication is suppressed.
[0105]
[Fifth Embodiment]
In the present embodiment, an object is to efficiently perform a process of updating the failure information database 103. FIG. 12 is a flowchart related to a process of updating the failure information database 103 according to the present embodiment.
[0106]
In step S1200, failure diagnosis server 101 determines whether an update request has been input. This update request may be input by the administrator of the failure diagnosis server 101 from the operation unit, or may be input to the failure diagnosis server 101 by an update request from a computer in the quality department. Further, what kind of failure may be specified for updating the failure information. At the time of designation, a failure code can be designated.
[0107]
In step S1202, the failure diagnosis server 101 determines whether the failure to be updated has high reproducibility under a specific driving condition. For example, the failure diagnosis server 101 searches the failure information database 103 using the designated failure code as a search key, and determines whether a specific driving condition is registered. If the specific driving condition has been registered, the process proceeds to step S606, and the specific driving condition extracted by the search is determined as the driving condition for acquiring the vehicle data. Otherwise, the process proceeds to step S614, in which the failure diagnosis server 101 causes the vehicle client device 200 of the failed vehicle 111 to acquire and transmit the vehicle data without specially specifying the traveling conditions.
[0108]
In step S1220, failure diagnosis server 101 updates failure information database 103 and vehicle information database 104 based on the vehicle data received from vehicle client device 200 of failed vehicle 111.
[0109]
As described above, according to the present embodiment, in the remote failure diagnosis system (for example, the failure diagnosis server 101) that remotely executes the failure diagnosis on the diagnosis target vehicle 110 and transmits the failure diagnosis result to the customer, the failure diagnosis is performed. (E.g., the failure information database 103 and the vehicle information database 104) storing vehicle data of the failed vehicle required for the vehicle, and when an update request for the database is issued, a specific one of the vehicle data required for the update is specified. Requesting means (eg, step S608) for requesting vehicle data from one or more failed vehicles under running conditions, and updating means (eg, S1220) for updating the contents of the database based on vehicle data received from the failed vehicle. ) Is provided.
[0110]
According to the present embodiment, since various traveling conditions can be designated according to the type of failure, vehicle data can be efficiently updated for failures that cannot be reproduced under specific traveling conditions.
[0111]
[Sixth Embodiment]
In the present embodiment, based on the remote failure diagnosis flowchart of FIG. 9, when performing detailed diagnosis, vehicle data is requested again when vehicle data under specific driving conditions is required. It is a flowchart which performs a detailed diagnosis based on data. The parts already described in the description of FIG. 9 are omitted.
[0112]
FIG. 13 is a flowchart of the remote failure diagnosis according to the sixth embodiment. If it is determined in step S905 that detailed diagnosis is necessary, the process advances to step S1306. In step S1306, the failure diagnosis server 101 can perform the detailed diagnosis based on the currently obtained vehicle data or the vehicle data under a specific driving condition, depending on the type of the failure subjected to the detailed diagnosis. Otherwise, it is determined whether detailed diagnosis cannot be performed. For example, the determination may be made based on whether or not running conditions for executing the detailed diagnosis are registered in the failure information database 103 in association with the failure code.
[0113]
If the result of the determination is that vehicle data under specific running conditions is required, the process proceeds to step S606 and subsequent steps. If unnecessary, the process proceeds to step S620, where a detailed diagnosis is performed using the currently obtained vehicle data.
[0114]
As described above, according to the present embodiment, the simple diagnosis, the detailed diagnosis, and the detailed diagnosis using the vehicle data under specific driving conditions are selectively used according to the type of the failure, so that the vehicle side and the system side can be used. The load can be reduced, and the communication traffic can be reduced.
[0115]
[Other embodiments]
In the above-described embodiment, all vehicle data including the failed vehicle is stored in the vehicle information database 104. However, the vehicle data of the failed vehicle may be stored in the failure information database 103. Considering the number of vehicles spread, the amount of vehicle data may be enormous, so old information must be deleted from the vehicle information database 103 as needed. Therefore, the storage amount of the vehicle information database 103 can be reduced by leaving only the vehicle data of the really necessary failed vehicle in the failure information database 103.
[0116]
The running conditions can be specified based on latitude / longitude information for each time, speed information, acceleration information, night / day, temperature, rain / sun, etc. included in the vehicle data. For example, the failure diagnosis server 110 specifies the position when the vehicle data is acquired from the latitude and longitude information, and further determines whether the position is a highway, a curve of 130R, or a slope of 15 degrees from the map database. Identify the driving conditions such as
[0117]
The failure diagnosis result may be directly transmitted from the failure diagnosis server 110 to the vehicle client device 200, or may be transmitted as an e-mail to the customer. For example, the failure diagnosis server 110 searches the customer database 102 based on the vehicle number of the failure diagnosis target vehicle 110 and extracts the customer's e-mail address. Then, the failure diagnosis server 110 transmits a diagnosis result to the extracted e-mail address.
[0118]
If not only the driver's e-mail address but also a plurality of e-mail addresses such as the e-mail address of the company to which the driver belongs are registered in the customer database, the failure diagnosis server 110 will not only store the driver, Since the diagnosis result can be distributed to the company to which the driver belongs, there is an advantage that the whole company can be used for safety management.
[0119]
In addition to the running conditions described above, the failure diagnosis server 101 specifies the sampling cycle and the sampling time, so that the size of the vehicle data can be adjusted.
[0120]
Further, the failure diagnosis server 101 may transmit a plurality of traveling conditions to the vehicle client device 200 at the same time. The vehicle client device 200 acquires the vehicle data and stores it in the storage device every time there is a plurality of running conditions that match. The acquired storage device may be transmitted for each traveling condition or may be transmitted when all traveling conditions are met.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration example of a system according to an embodiment;
FIG. 2 is a block diagram showing a configuration example of a vehicle according to the embodiment.
FIG. 3 is a diagram illustrating a configuration example of a service factory 120;
FIG. 4 is a flowchart relating to collection of vehicle data according to the embodiment.
FIG. 5 is a flowchart relating to collection of failure data used for failure diagnosis.
FIG. 6 is a flowchart of a remote failure diagnosis process according to the first embodiment.
FIG. 7 is a diagram illustrating the contents of a database and the concept of a failure diagnosis process according to the embodiment;
FIG. 8 is a detailed flowchart of a failure diagnosis process according to the embodiment.
FIG. 9 is a flowchart of a remote failure diagnosis process according to the second embodiment.
FIG. 10 is a flowchart of a remote failure diagnosis process according to the third embodiment.
FIG. 11 is a flowchart of a remote failure diagnosis process according to the fourth embodiment.
FIG. 12 is a flowchart of a database update process according to a fifth embodiment.
FIG. 13 is a flowchart of a remote failure diagnosis process according to the sixth embodiment.
[Explanation of symbols]
100… Information center
101: Failure diagnosis server
110… Failure diagnosis target vehicle
111 ... Failure vehicle
120… Service factory
121… Service factory client

Claims (20)

In a remote failure diagnosis system that remotely executes a failure diagnosis on a vehicle to be diagnosed and transmits a failure diagnosis result to a customer,
Determining means for determining running conditions required when performing a failure diagnosis for a predetermined failure;
Transmission means for transmitting the determined driving conditions to the vehicle to be diagnosed,
Receiving means for receiving vehicle data obtained in accordance with the traveling conditions from the vehicle to be diagnosed,
Failure diagnosis means for performing a failure diagnosis for the predetermined failure based on the received vehicle data,
A remote failure diagnosis system comprising: a notification unit configured to notify a customer of the vehicle to be diagnosed of a failure diagnosis result by the failure diagnosis unit. In a remote failure diagnosis system that remotely executes a failure diagnosis on a vehicle to be diagnosed and transmits a failure diagnosis result to a customer,
First failure diagnosis means for performing failure diagnosis for a predetermined failure based on vehicle data received from the vehicle to be diagnosed;
Determining means for determining whether more detailed failure diagnosis is required based on the result of the failure diagnosis,
Requesting means for requesting vehicle data under specific driving conditions required when executing the more detailed failure diagnosis when it is determined that more detailed failure diagnosis is necessary;
Receiving means for receiving vehicle data obtained in accordance with the traveling conditions from the vehicle to be diagnosed,
A second failure diagnosis unit that performs a more detailed failure diagnosis than the first failure diagnosis unit based on the received vehicle data;
Notification means for notifying a customer of the vehicle to be diagnosed of a result of the failure diagnosis by the second failure diagnosis means. The remote failure diagnosis system according to claim 1, wherein the predetermined failure has high reproducibility under a specific driving condition. For each of the plurality of failures, comprising a database that stores running conditions and vehicle data of the failed vehicle when acquiring vehicle data,
The failure diagnosis unit determines whether a failure has occurred by comparing vehicle data of the vehicle to be diagnosed with vehicle data of a failed vehicle stored in the database. The remote fault diagnosis system according to any one of claims 1 to 3. 5. The remote failure diagnosis system according to claim 1, wherein the travel condition is defined by a combination of a plurality of behaviors of the vehicle. The determining unit further determines a type of vehicle data to be acquired in the diagnosis target vehicle, and the transmitting unit transmits information specifying the determined type of vehicle data together with the traveling condition. The remote fault diagnosis system according to any one of claims 1 to 5, wherein: The method according to claim 1, wherein the determining unit further determines a sampling condition when acquiring the vehicle data, and the transmitting unit transmits information specifying the determined sampling condition together with the traveling condition. 7. The remote failure diagnosis system according to any one of claims 1 to 6. A vehicle to be diagnosed for failure by the remote failure diagnosis system according to any one of claims 1 to 7,
Means for receiving the driving condition from the remote failure diagnosis system;
Means for acquiring vehicle data when the received driving conditions are met,
Means for transmitting the obtained vehicle data to the remote failure diagnosis system,
Means for receiving a failure diagnosis result from the remote failure diagnosis system;
Means for outputting the received failure diagnosis result. Means for determining whether a predetermined time has elapsed since the previous acquisition time for the vehicle data,
Means for prohibiting the acquisition or transmission of the vehicle data if the predetermined time has not elapsed,
The vehicle to be diagnosed according to claim 8, further comprising: The diagnosis target vehicle according to claim 9, further comprising a change unit that changes the length of the predetermined time. The diagnosis target vehicle according to claim 10, wherein the change unit changes the predetermined time based on a change command from a remote failure diagnosis system. 11. The method according to claim 10, wherein the change unit sets the predetermined time to a longer interval when the vehicle data obtained last time and the vehicle data obtained this time have not substantially changed. The vehicle to be diagnosed as described. The diagnosis target vehicle according to any one of claims 8 to 12, further comprising a deletion unit configured to delete the received traveling condition when a predetermined deletion condition is satisfied. In a remote failure diagnosis system that remotely executes a failure diagnosis on a vehicle to be diagnosed and transmits a failure diagnosis result to a customer,
A database for storing vehicle data of a failed vehicle required for failure diagnosis,
Request means for requesting one or more failed vehicles of vehicle data under specific driving conditions among the vehicle data required for updating when the database update request is issued;
Updating means for updating the contents of the database based on vehicle data received from the failed vehicle. In a remote failure diagnosis method for remotely performing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Determining running conditions required when performing a failure diagnosis for a predetermined failure;
Transmitting the determined traveling condition to the vehicle to be diagnosed;
Receiving the vehicle data obtained in accordance with the running conditions from the vehicle to be diagnosed,
Performing a failure diagnosis for the predetermined failure based on the received vehicle data;
Notifying the customer of the vehicle to be diagnosed of the result of the failure diagnosis by the failure diagnosis means. In a remote failure diagnosis method for remotely performing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Performing a failure diagnosis for a predetermined failure based on the vehicle data received from the diagnosis target vehicle;
Determining whether more detailed failure diagnosis is required based on the result of the failure diagnosis;
When it is determined that more detailed failure diagnosis is necessary, requesting vehicle data under specific driving conditions required for performing the more detailed failure diagnosis;
Receiving the vehicle data obtained in accordance with the running conditions from the vehicle to be diagnosed,
Performing a more detailed failure diagnosis than the first failure diagnosis means based on the received vehicle data;
Notifying a customer of the diagnosis target vehicle of a result of the failure diagnosis by the second failure diagnosis means. A remote failure diagnosis method for remotely performing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Receiving a request to update a database that stores vehicle data of a failed vehicle required for failure diagnosis;
Requesting one or more failed vehicles to transmit vehicle data under specific driving conditions among vehicle data required for updating the database;
Updating the contents of the database based on vehicle data received from the failed vehicle. A computer program for causing a computer to execute a remote failure diagnosis for remotely executing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Determining running conditions required when performing a failure diagnosis for a predetermined failure;
Transmitting the determined traveling condition to the vehicle to be diagnosed;
Receiving the vehicle data obtained in accordance with the running conditions from the vehicle to be diagnosed,
Performing a failure diagnosis for the predetermined failure based on the received vehicle data;
Notifying a customer of the vehicle to be diagnosed of the result of the failure diagnosis by the failure diagnosis means. A computer program for causing a computer to execute a remote failure diagnosis for remotely executing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
In a remote failure diagnosis method for remotely performing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Performing a failure diagnosis for a predetermined failure based on the vehicle data received from the diagnosis target vehicle;
Determining whether more detailed failure diagnosis is required based on the result of the failure diagnosis;
When it is determined that more detailed failure diagnosis is necessary, requesting vehicle data under specific driving conditions required for performing the more detailed failure diagnosis;
Receiving the vehicle data obtained in accordance with the running conditions from the vehicle to be diagnosed,
Performing a more detailed failure diagnosis than the first failure diagnosis means based on the received vehicle data;
Notifying the customer of the vehicle to be diagnosed of the result of the failure diagnosis by the second failure diagnosis means. A computer program for causing a computer to execute a remote failure diagnosis for remotely executing a failure diagnosis on a diagnosis target vehicle and transmitting a failure diagnosis result to a customer,
Receiving a request to update a database that stores vehicle data of a failed vehicle required for failure diagnosis;
Requesting one or more failed vehicles to transmit vehicle data under specific driving conditions among vehicle data required for updating the database;
Updating the contents of the database based on vehicle data received from the failed vehicle.

Images