Repair proposal method and device of vehicle
Patent Information
- Application Number
- JP2023086572
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-26
- Publication Date
- 2024-12-06
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
【0009】 この発明によれば、故障の予兆を検知したときに故障部品候補を特定しかつその出張修理での対応の可否を考慮した上でユーザが出張修理等の提案を受領するので、ユーザにとって便利であるとともに、作業員の無駄な出張を防止することができる。
Smart Images

Figure 2024169812000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a method and apparatus for proposing an appropriate repair policy, including on-site repair, to a user when a symptom of a failure in a vehicle part is detected. [Background technology]
[0002] When a user (owner of the vehicle) notices some sort of malfunction in the vehicle or detects a sign of an impending breakdown, the user must take the vehicle to a dealer, that is, the sales company of the vehicle, to have it inspected and repaired.
[0003] Patent Document 1 discloses a technology that allows a repair estimate to be made remotely when a vehicle is damaged in an accident by sending an image of the damaged area via a smartphone and receiving an estimated repair cost from a server in response to the image. It also describes that the estimated repair cost includes the travel cost for picking up the vehicle. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2008-308075 A Summary of the Invention [Problem to be solved by the invention]
[0005] For general users, bringing a vehicle to a dealer is a hassle in terms of time and effort. Therefore, even if a user feels that the vehicle is not working properly, the user tends to continue driving the vehicle without having it inspected at the dealer. On the other hand, if a user blindly requests repairs at home, the number of unnecessary visits by repair personnel will increase.
[0006] It should be noted that the on-site repair costs in Patent Document 1 are merely the costs required to transport the damaged vehicle to a repair shop, and do not disclose on-site repair services in which a dealer's worker travels to the user's home or other location to perform repairs. [Means for solving the problem]
[0007] The vehicle repair suggestion method according to the present invention comprises: Detects signs of failure in vehicle parts, Based on these symptoms, one or more potential faulty parts are identified, Determine whether each defective part can be repaired by on-site service, Based on this determination, a repair policy, including on-site repair, is proposed to the user.
[0008] In the present invention, one or more candidate faulty parts are identified, a decision is made as to whether or not the part can be repaired by an on-site visit, and a final repair policy is proposed. Effect of the Invention
[0009] According to this invention, when a sign of a failure is detected, the user is given a proposal for on-site repair after identifying possible faulty parts and considering whether the part can be handled by on-site repair, etc., which is convenient for the user and prevents unnecessary on-site visits by workers. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a configuration explanatory diagram showing a first embodiment of an on-site repair suggestion system according to the present invention; [Diagram 2] FIG. 4 is an explanatory diagram showing data on the results of failure sign detection on the vehicle side in a table format. [Diagram 3] FIG. 4 is an explanatory diagram of a failure sign detection result database on the on-site repair determination device. [Figure 4] FIG. 13 is an explanatory diagram of an on-site repair compatible parts information database. [Diagram 5] 4 is a flowchart showing the flow of processing in the first embodiment. [Figure 6] FIG. 11 is a diagram illustrating the degree of coincidence of failure symptom information. [Figure 7] FIG. 13 is an explanatory diagram showing an example of a list of parts with high matching degrees. [Figure 8] FIG. 13 is a configuration explanatory diagram showing a second embodiment of the on-site repair suggestion system; [Figure 9] 10 is a flowchart showing the flow of processing according to a second embodiment. [Figure 10] FIG. 13 is a configuration explanatory diagram showing a third embodiment of the on-site repair suggestion system; [Figure 11] FIG. 13 is an explanatory diagram of a failure sign detection result database including a history of abnormal signals. [Figure 12] FIG. 4 is an explanatory diagram of a failure sign history database. [Figure 13] 13 is a flowchart showing the flow of processing according to a third embodiment. [Figure 14] FIG. 13 is an explanatory diagram showing an example of a list of parts with high matching degrees. [Figure 15] FIG. 13 is a configuration explanatory diagram showing a fourth embodiment of the on-site repair suggestion system; [Figure 16] FIG. 4 is an explanatory diagram of a signal importance database. [Figure 17] 13 is a flowchart showing the flow of processing according to a fourth embodiment. [Figure 18] FIG. 13 is an explanatory diagram showing an example of a list of ranked parts. [Figure 19] FIG. 13 is a configuration explanatory diagram showing a fifth embodiment of the on-site repair suggestion system; [Figure 20] FIG. 4 is an explanatory diagram of a signal feature database. [Figure 21] 13 is a flowchart showing the flow of processing according to the fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] An embodiment of the present invention will be described in detail below with reference to the drawings. Fig. 1 is a configuration explanatory diagram showing a first embodiment of an on-site repair suggestion system according to the present invention. The on-site repair suggestion system is composed of a vehicle-side device 001 that is installed in each vehicle (e.g., vehicle A), and an on-site repair determination device 002 that is composed of a server or cloud computer installed in a dealer or the like.
[0012] The vehicle-side device 001 is a part of a so-called computer system of the vehicle, and includes a diagnostic device 003, a memory 004, a display unit 005, an ECU (Electronic Control Unit) 006, a communication unit 007, and a failure prediction unit 008. The diagnostic device 003 monitors various signals (also called vehicle data) obtained from each part of the vehicle and detects abnormal signals. The failure prediction unit 008 detects that a part is a sign of failure based on one or more abnormal signals, stores the detected abnormal signals in the memory 004, and transmits the detected abnormal signals to the on-site repair determination device 002 via the communication unit 007. The vehicle is configured as a so-called connected car, and is constantly connected to, for example, the Internet via the communication unit 007. Using this communication function, various information is transmitted and received between the vehicle-side device 001 and the on-site repair determination device 002. The display unit 005 is, for example, a display provided in front of the driver's seat, and displays various information. The display unit 005 may be a mobile terminal (for example, a smartphone) of a user who owns the vehicle.
[0013] When the failure prediction unit 008 detects a sign of failure, the presence of the sign of failure may be displayed on the display unit 005 together with the transmission to the on-site repair determination device 002. Alternatively, the sign of failure may not be displayed alone, but may be displayed together with a proposal for on-site repair, which will be described later.
[0014] In the failure prediction unit 008, when a sign of failure is detected, data of a failure sign detection result 050 is generated in a form as shown in FIG. 2, and this data is transmitted via the communication unit 007. As exemplified in FIG. 2, this data includes the vehicle identification number, the date and time when the sign was detected, and the content of the sign, that is, the content of the abnormal signal (in the illustrated example, three types of abnormal signals a, b, and c are included). Other additional information may be included. That is, when the failure prediction unit 008 detects that there is a sign of failure from some signal or information, it acquires the sign information including a plurality of abnormal signals related to this sign, and generates data as shown in FIG. 2 together with the date and time. Note that the sign may be detected based on the abnormal signals themselves, for example, a, b, and c, included in the sign information, or may be determined to be present when another signal or information indicates a sign of failure, and the abnormal signal at that time may be acquired.
[0015] The on-site repair determination device 002 includes a communication unit 009, a faulty part identification unit 010, a fault sign consistency diagnosis unit 011, a fault sign detection result database 012, an on-site repair feasibility determination unit 013, an on-site repair compatible parts information database 014, and an on-site repair proposal unit 015. Each of these units does not necessarily have to be configured by a single computer, and can be configured by multiple servers or cloud computers.
[0016] The communication unit 009 communicates with the communication unit 007 on the vehicle side via an appropriate communication network, and when a sign of failure is detected on the vehicle side, it receives data of the failure sign detection result 050 shown in Fig. 2 from the vehicle side. When finally proposing an on-site repair, which will be described later, it transmits information to that effect to the vehicle side.
[0017] The failure sign detection result database 012 stores a large amount of diagnostic data that summarizes past symptom information and diagnostic results of other vehicles (which may include past data of the vehicle itself), such as failure sign detection result data 051, a portion of which is illustrated in FIG. 3. As illustrated in FIG. 3, the data 051 of the failure sign detection result database 012 includes information such as the vehicle identification number, the symptom detection content, which indicates what part is abnormal, the date and time when the symptom was detected, the content of the abnormality signal (in other words, the symptom information), the name of the part that was actually repaired and replaced, and the result after the repair and replacement (i.e., whether the defect was resolved). If the result after the repair and replacement is good, it means that the part that was repaired and replaced based on the symptom was appropriate. The data 051 of the failure sign detection result database 012 may include other additional information. For example, information such as the period (time or distance traveled) elapsed from the time when a symptom was detected until the actual repair and replacement, or the period (time or distance traveled) elapsed until the failure occurs if the failure is left unattended, may be added. New data is added to the failure symptom detection result database 012 every time a part is actually repaired or replaced.
[0018] The failure sign coincidence diagnosis unit 011 determines the degree of coincidence between the contents of the sign detected on the vehicle side and the contents of the sign included in the past data 051 in the failure sign detection result database 012. For example, if the contents of the sign obtained by the failure prediction unit 008 are a combination of abnormal signals "a, b, c", a combination pattern including the combination of abnormal signals "a, b, c" is determined to be a combination pattern with a high degree of coincidence in the past data 051 in the failure sign detection result database 012. In the example of FIG. 3, the combinations of abnormal signals "a, b, c" and "a, b, c, f" are determined to be a coincidence pattern with a high degree of coincidence. Note that the combination of "a, b, c" has a higher degree of coincidence than the combination of "a, b, c, f". A combination pattern that does not include "a, b, c" (partially missing) and a combination pattern that includes multiple abnormal signals other than "a, b, c" are determined to be a non-coincidence pattern with a low degree of coincidence. Note that in the present invention, the degree of coincidence required is set to any level.
[0019] As a specific example, the abnormal signals a, b, and c are, for example, the engine speed, the ignition timing, and the air-fuel ratio, respectively, and are determined to be abnormal by processing these constantly monitored signals (detection signals or internal signals) through an abnormality detection process of an appropriate algorithm (for example, statistical abnormality detection for time-series data). The abnormal signal f can be, for example, an air-fuel ratio correction coefficient.
[0020] The faulty part identification unit 010 identifies parts that have a high degree of match with the contents of the symptom based on the degree of match between the contents of the symptom detected on the vehicle side by the fault symptom coincidence diagnosis unit 011 and the contents of the symptom in the past data 051. The parts identified here become candidate faulty parts corresponding to the symptom. These candidate faulty parts may include multiple parts with a high degree of match. Note that it is desirable to exclude from the candidate faulty parts those parts that have been repaired and replaced based on the symptoms in the past data 051 but have not produced good results, even if the degree of match with the contents of the symptom is high.
[0021] The on-site repair availability determination unit 013 refers to the on-site repair compatible parts information database 014 to determine whether on-site repair is possible. As illustrated in FIG. 4, the on-site repair compatible parts information database 014 stores a large amount of parts information data 052 with information on whether on-site repair is possible for each of all parts (which may be only some of the main parts) included in the vehicle. For example, on-site repair is not possible for parts that are difficult to repair without large-scale equipment or special devices in a repair shop. The on-site repair availability determination unit 013 refers to the on-site repair compatible parts information database 014 to determine whether on-site repair is possible for each of the candidate faulty parts identified by the faulty part identification unit 010, and determines that on-site repair is possible when all the candidate faulty parts are possible for on-site repair.
[0022] The on-site repair compatible parts information database 014 can be constructed in advance, for example, based on knowledge about each part (design information, etc.), but it is desirable to update it successively when an on-site repair is actually performed (including cases where an on-site repair is attempted but not completed). In particular, for parts with new specifications, it is desirable to update the on-site repair compatible parts information database 014 and store new information when an on-site repair is actually performed. This makes it possible to efficiently increase the number of part varieties that can be handled by on-site repair. Also, by updating the data based on actual on-site repairs, the probability that the repair can be completed by on-site repair increases.
[0023] As another example, the on-site repair feasibility determination unit 013 may determine that on-site repair is possible even if some of the candidate faulty parts are not available for on-site repair. For example, the probability that each of the multiple candidate faulty parts is a part that needs repair or replacement is calculated, and if the probability that the candidate faulty parts are available for on-site repair is equal to or higher than a predetermined threshold, on-site repair is possible even if the candidate faulty parts are not available for on-site repair. Note that the above probability is calculated based on, for example, the degree of agreement of the contents of the signs described above and the past fault sign detection result data 051.
[0024] Alternatively, multiple faulty part candidates may be arranged in order of priority, and if the top-ranked faulty part candidates are available for on-site repair, then on-site repair may be possible even if lower-ranked faulty part candidates are not available for on-site repair. For example, if the top three faulty part candidates arranged in order of priority are available for on-site repair, on-site repair may be possible even if lower-ranked faulty part candidates are not available for on-site repair.
[0025] If the on-site repair availability determination unit 013 determines that on-site repair is possible, the on-site repair suggestion unit 015 proposes on-site repair to the user of the vehicle. Specifically, information regarding the proposal for on-site repair is sent to the vehicle-side device 001 via the communication units 009 and 007, and the information is displayed (may include audio) on the display unit 005 of the vehicle or a mobile terminal (such as a so-called smartphone) owned by the user. For example, information such as the presence of a sign of a breakdown, the availability of on-site repair at home, etc. is conveyed to the user.
[0026] Fig. 5 is a flowchart showing the process flow of the on-site repair suggestion system of the first embodiment. Note that the flowchart of Fig. 5 shows each step in the order of the overall process flow without distinguishing between the process performed by the vehicle-side device 001 and the process performed by the on-site repair determination device 002.
[0027] In step 101, the diagnosis device 003 and the failure prediction unit 008 of the vehicle-side device 001 predict failure (detection of a sign of failure) based on vehicle data. In step 102, the detected failure prediction information (failure sign detection result 050) is transmitted from the vehicle-side device 001 to the on-site repair determination device 002.
[0028] In step 103, data 051 stored in the failure sign detection result database 012, that is, information on failure signs of other vehicles, is referred to. In step 104, the degree of agreement between the failure sign detection result 050 sent from the vehicle-side device 001 and the information on failure signs of other vehicles obtained from the failure sign detection result database 012 is diagnosed. As described above, a combination pattern of multiple types of abnormal signals is used to diagnose the degree of agreement. For example, as shown in FIG. 6, if the contents of the detected sign are a combination of abnormal signals "a, b, c", the combination of abnormal signals "a, b, c" or "a, b, c, f" is a matching pattern with a high degree of agreement, while a combination pattern in which the signals are different, such as "g, f" or "s, t", or which includes multiple other abnormal signals, such as "a, b, c, f, g, h", is a non-matching pattern with a low degree of agreement.
[0029] Then, in step 105, the parts with a high degree of match are narrowed down to be candidates for the faulty part. There may be multiple candidates here. For example, in the example of Fig. 7, two parts, a plug and an injector, are extracted as candidates for the faulty part with a high degree of match for the combination of abnormal signals "a, b, c".
[0030] Next, in step 106, the data 052 stored in the on-site repair part information database 014 is referenced, and in step 107, one or more parts that are candidate faulty parts (parts that are determined to have a high degree of match in step 105) are compared with the data 052 in the on-site repair part information database 014. For example, in the data 052 illustrated in FIG. 4, plugs and injectors are designated as parts that can be used for on-site repair. In step 108, it is determined whether all of the candidate faulty parts that have a high degree of match are parts that can be used for on-site repair. If all of the candidate faulty parts are parts that can be used for on-site repair, the process proceeds to step 109, where an on-site repair is proposed via the display unit 005 of the vehicle or a mobile terminal or the like held by the user. If the user agrees to this proposal, a dealer's worker will visit the vehicle storage location, such as the user's home, to repair and replace the vehicle.
[0031] If even one of the candidate faulty parts is not a part that can be used for on-site repair, the process proceeds to step 110 and on-site repair is not proposed. If on-site repair is not proposed, a message may be displayed indicating that the part is not suitable for on-site repair, or nothing may be displayed.
[0032] As described above with regard to the on-site repair feasibility determination unit 013, even if some of the candidate faulty parts are not suitable for on-site repair in step 108, it may be determined that on-site repair is possible, for example, depending on the priority, and an on-site repair may be proposed in step 109.
[0033] In this way, in the above embodiment, when a symptom of a part failure is detected, one or more candidate failed parts are identified, and an on-site repair is proposed on the condition that these candidate failed parts are parts that can be repaired on-site. This increases the probability that the repair will be completed by a dealer's worker at the user's home or the like, which is convenient for the user and also allows the on-site worker to avoid unnecessary visits.
[0034] Next, a second embodiment of the present invention will be described with reference to Figures 8 and 9. The following mainly describes the differences from the first embodiment. The second embodiment differs from the first embodiment in that failure prediction is performed not by the vehicle-side device 001 but by an on-site repair determination device 002 managed by a dealer or the like, and in that a diagnosis is made as to whether the vehicle is in a condition in which it can be driven to a repair shop and an appropriate proposal is made.
[0035] As shown in FIG. 8, the on-site repair suggestion system of the second embodiment is composed of a vehicle-side device 001 installed in each vehicle, and an on-site repair determination device 002 consisting of a server or cloud computer installed in a dealer or the like.
[0036] As in the first embodiment, the vehicle-side device 001 includes a diagnostic device 003, a memory 004, a display unit 005, an ECU 006, and a communication unit 007. However, the vehicle-side device 001 does not include a failure prediction unit 008.
[0037] The on-site repair determination device 002 is basically configured to include a communication unit 009, a faulty part identification unit 010, a fault sign coincidence diagnosis unit 011, a fault sign detection result database 012, an on-site repair availability determination unit 013, an on-site repair compatible part information database 014, and an on-site repair proposal unit 015, similar to the first embodiment. In the second embodiment, a fault prediction unit 008 is configured as a part of the on-site repair determination device 002. The fault prediction unit 008 detects that a part is a sign of failure based on one or more abnormal signals sent from the diagnosis device 003 of the vehicle-side device 001 via the communication units 007 and 009. When the fault prediction unit 008 detects a fault sign, it acquires symptom information including multiple abnormal signals. As a result, data of the fault sign detection result 050 as shown in FIG. 2 is generated. This is basically the same data as in the first embodiment, and includes, for example, the vehicle identification number, the date and time when the symptom was detected, and the contents of the abnormal signal (in the illustrated example, three abnormal signals a, b, and c are included), as shown in Fig. 2. Other additional information may also be included.
[0038] The on-site repair determination device 002 of the second embodiment further includes a vehicle state diagnosis unit 027 that diagnoses the state of the vehicle based on the vehicle data (including abnormality signals) sent from the vehicle-side device 001. In this embodiment, the vehicle state diagnosis unit 027 mainly diagnoses whether the vehicle is in a state in which it can be driven to the dealer.
[0039] 9 is a flowchart showing the process flow of the on-site repair suggestion system of the second embodiment. The basic process flow is the same as that of the first embodiment, but first, as shown in step 112, vehicle data is sent from the vehicle-side device 001 to the on-site repair determination device 002. In step 101, the on-site repair determination device 002 performs failure prediction (detection of a sign) based on the vehicle data sent from the vehicle-side device 001.
[0040] In step 103, the data 051 stored in the failure sign detection result database 012, i.e., information on failure signs of other vehicles, is referenced. In step 104, the degree of match between the failure sign detection result 050 output by the failure prediction unit 008 and the information on failure signs of other vehicles obtained from the failure sign detection result database 012 is diagnosed. As described above, a combination pattern of a plurality of abnormal signals is used to diagnose the degree of match.
[0041] Then, in step 105, the components with the highest degree of match are narrowed down to be candidates for the faulty component. Here, there may be multiple candidates.
[0042] Next, in step 106, the data 052 stored in the on-site repair parts information database 014 is referenced, and in step 107, a plurality of parts that are candidate faulty parts (parts with a high degree of match in step 105) are compared with the data 052 in the on-site repair parts information database 014. In step 108, it is determined whether all of the candidate faulty parts with a high degree of match are parts that can be used for on-site repair. If all of the candidate faulty parts are parts that can be used for on-site repair, the system proceeds to step 109, and an on-site repair is proposed via the display unit 005 of the vehicle or a mobile terminal or the like held by the user.
[0043] On the other hand, if even one of the candidate faulty parts is not a part that can be repaired on-site, the process proceeds to step 117, where it is diagnosed whether the vehicle is in a condition that allows it to be driven. If the vehicle is in a condition that allows it to be driven, the process proceeds to step 110, where an on-site repair is not suggested. The process then proceeds to step 111, where it is suggested, via the display unit 005 of the vehicle or the mobile terminal 040 owned by the user, that the user bring the vehicle to the dealer for repair (dealer visit repair).
[0044] If it is determined in step 117 that the vehicle is not in a condition to be driven, the process proceeds to step 118, where a suggestion is made via the display unit 005 of the vehicle or the mobile terminal 040 held by the user that the vehicle be transported to a dealer in a tow truck for repairs. In this case, if the user accepts the suggestion, the dealer will make arrangements for a tow truck, etc.
[0045] In addition, when determining whether or not traveling is possible in step 117, the user may be inquired about his / her convenience and intentions and these may be taken into consideration in addition to the state of the vehicle.
[0046] According to the second embodiment, appropriate measures such as on-site repair, dealer visit repair, and transportation by tow truck are proposed to the user after taking into consideration the vehicle condition, etc. Also, according to the second embodiment, the failure prediction unit 008 is not required on the vehicle side, so that the present invention can be applied to many more vehicles including existing vehicles.
[0047] Next, a third embodiment of the present invention will be described with reference to Figures 10 to 14. The third embodiment differs from the first and second embodiments in that candidate faulty parts are identified in consideration of the history of past signs of faults in the vehicle.
[0048] As shown in FIG. 10, the on-site repair suggestion system of the third embodiment is composed of a vehicle-side device 001 installed in each vehicle, and an on-site repair determination device 002 consisting of a server or cloud computer installed in a dealer or the like.
[0049] The vehicle-side device 001 includes a diagnostic device 003, a memory 004, a display unit 005, an ECU 006, and a communication unit 007, similarly to the second embodiment.
[0050] The on-site repair determination device 002 is basically similar to the second embodiment and includes a failure prediction unit 008, a communication unit 009, a faulty part identification unit 010, a failure sign consistency diagnosis unit 011, a failure sign detection result database 012, an on-site repair feasibility determination unit 013, an on-site repair compatible parts information database 014, and an on-site repair proposal unit 015. In the third embodiment, the device further includes a detection information acquisition unit 016 that acquires information on the failure signs (information on abnormal signals) detected by the failure prediction unit 008, and a failure sign history database 017 that accumulates information on the failure signs of the vehicle.
[0051] FIG. 12 shows an example of the failure sign history stored in the failure sign history database 017, and stores data 061 including the date and time of failure prediction for the vehicle and the abnormal signal detected at that time.
[0052] Similarly, the failure sign detection result database 012 in the third embodiment stores failure sign detection result data 062 including the history of several abnormal signals in the past for each vehicle, as exemplified in FIG.
[0053] FIG. 13 is a flowchart showing the process flow of the on-site repair suggestion system of the third embodiment. The basic process flow is the same as that of the second embodiment. First, in step 112, vehicle data is transmitted from the vehicle-side device 001 to the on-site repair determination device 002. In step 101, the on-site repair determination device 002 performs failure prediction (detection of a sign) based on the vehicle data transmitted from the vehicle-side device 001. Here, data of the failure sign detection result 050 as exemplified in FIG. 2 is generated. In step 113, data of the current failure sign detection result 050 detected in step 101 is added to data 061 of the failure sign history database 017 exemplified in FIG. 12. In other words, the current failure sign detection result 050 is stored. The failure sign history database 017 created in this way is a database related to failure signs of the vehicle itself.
[0054] In step 103, information on the signs of failure of other vehicles is referenced from the signs of failure detection result data 062 including the past history shown in Fig. 11. As described above, the signs of failure detection result data 062 in this embodiment basically corresponds to the data 051 (Fig. 3) in the signs of failure detection result database 012 in the first embodiment, but also includes the history of several abnormal signals in the past for each vehicle.
[0055] In the next step 114, the degree of agreement between the failure sign information in the failure sign detection result data 062 and the failure sign history in the data 061 of the failure sign history database 017 related to the vehicle is diagnosed. In this agreement diagnosis, a combination pattern of abnormal signals including past history is used. For example, if the combination pattern of abnormal signals in the failure sign history data 061 of the vehicle is "a, b, c" for the first time, "a, b" for the second time, and "a, b, c" for the third time (see FIG. 12), the combination pattern of "a, b, c" and the combination pattern of "a, b" are determined as matching patterns among the combination patterns including the abnormal signal history in the failure sign detection result data 062 of the other vehicle. On the other hand, a combination pattern that includes signals other than a, b, and c, such as "a, b, c, f," or a combination pattern that does not include a and b is determined as a non-matching pattern. In the example of FIG. 11, the part surrounded by a thick solid line is a matching pattern.
[0056] Then, in step 105, the parts with a high degree of match are narrowed down to be candidates for the faulty part. There may be multiple candidates here. For example, in the example of list 053 shown in Fig. 14, as a result of considering the past history, plugs are extracted as candidates for the faulty part with a high degree of match.
[0057] Next, in step 106, the data 052 stored in the on-site repair parts information database 014 is referenced, and in step 107, one or more parts that are candidate faulty parts (parts that are determined to have a high degree of match in step 105) are compared with the data 052 in the on-site repair parts information database 014. For example, in the data 052 illustrated in FIG. 4, the candidate plugs are parts that are available for on-site repair. In step 108, it is determined whether all of the candidate faulty parts that have a high degree of match are parts that are available for on-site repair. If all of the candidate faulty parts are parts that are available for on-site repair, the process proceeds to step 109, where on-site repair is proposed. If even one of the candidate faulty parts is not a part that is available for on-site repair, the process proceeds to step 110, where on-site repair is not proposed.
[0058] In this way, in the third embodiment, candidate faulty parts are identified taking into account the history of signs of failure, so that candidate faulty parts can be extracted with higher accuracy, increasing the probability of completing on-site repairs.
[0059] Next, a fourth embodiment of the present invention will be described with reference to Fig. 15 to Fig. 18. The fourth embodiment differs from the first and second embodiments in that the importance of an abnormal signal is determined for each component, and the coincidence of predictive information is determined taking into account this importance.
[0060] As shown in FIG. 15, the on-site repair suggestion system of the fourth embodiment is composed of a vehicle-side device 001 installed in each vehicle, and an on-site repair determination device 002 consisting of a server or cloud computer installed in a dealer or the like.
[0061] The vehicle-side device 001 includes a diagnostic device 003, a memory 004, a display unit 005, an ECU 006, and a communication unit 007, similarly to the second embodiment.
[0062] The on-site repair determination device 002 is basically configured to include a failure prediction unit 008, a communication unit 009, a faulty part identification unit 010, a failure sign coincidence diagnosis unit 011, a failure sign detection result database 012, an on-site repair availability determination unit 013, an on-site repair compatible part information database 014, and an on-site repair proposal unit 015, similar to the second embodiment. In the fourth embodiment, the device further includes a signal importance ranking unit 018 that determines the order of importance of abnormal signals for each part, and a signal importance database 019 that accumulates information on the signal importance. The signal importance database 019 stores data of a signal importance list 063 that summarizes the abnormal signal patterns and the importance of each abnormal signal for each part, as illustrated in FIG. 16, for example. The signal importance can be set in advance based on knowledge about each part (design information, test results, etc.). Alternatively, the priority, i.e., the importance, of the abnormal signal may be obtained from a large amount of failure sign detection result data 051 (see FIG. 3) that is sequentially stored in the failure sign detection result database 012. Even when the failure mechanism of a component is not clear, the importance of the signal can be known from past data.
[0063] Fig. 17 is a flow chart showing the process flow of the on-site repair suggestion system of the fourth embodiment. The basic process flow is the same as that of the second embodiment, and first, in step 112, vehicle data is sent from the vehicle-side device 001 to the on-site repair determination device 002. In step 101, failure prediction (detection of signs) is performed on the on-site repair determination device 002 side based on the vehicle data sent from the vehicle-side device 001. Here, data of failure sign detection result 050 such as that shown in Fig. 2 is generated.
[0064] In step 103, information on signs of failure of other vehicles is referenced from the data 051 (FIG. 3) in the failure sign detection result database 012. In step 104, the degree of agreement between the failure sign detection result 050 of the vehicle itself and the information on signs of failure of other vehicles obtained from the failure sign detection result database 012 is diagnosed. As described above, a combination pattern of a plurality of abnormal signals is used to diagnose the degree of agreement.
[0065] Next, in step 111, information (signal importance list 063) in a signal importance database 019 that summarizes the importance information of abnormal signals is referenced, and in the next step 115, priorities are assigned taking into consideration the importance information of the abnormal signals, and the parts with high degrees of match (candidates for faulty parts) are narrowed down.
[0066] In the example of Fig. 16, in the signal importance list 063, for example, when the content of the precursor detection is a plug, the combination patterns of abnormal signals are "a, b, c" and "a, b", and the importance of the abnormal signals is recorded as "a, b>c". In other words, the importance of signal c is low. On the other hand, when the content of the precursor detection is an injector, the combination patterns of abnormal signals are "a, b, c, f" and "a, b, f", and the importance of the abnormal signals is recorded as "a, f>b>c".
[0067] Therefore, in this example, when the combination of abnormal signals that are detected as a sign of failure is "a, b, c," since signal f, which is a signal with high importance for the injector, is not included, when narrowing down the candidate faulty parts, it is determined that the degree of match with the injector is lower than that with the plug.
[0068] As a result, as shown in the example of list 053 in FIG. 18, faulty part candidates are extracted with a ranking, for example, the plug in first place, the injector in second place, and so on.
[0069] Next, in step 106, the data 052 stored in the on-site repair parts information database 014 is referenced, and in step 107, one or more parts that are candidate faulty parts (parts that are determined to have a high degree of match in step 115) are compared with the data 052 in the on-site repair parts information database 014. For example, in the data 052 illustrated in FIG. 4, the candidate faulty parts, that is, plugs and injectors, are parts that are available for on-site repair. In step 108, it is determined whether all of the faulty part candidates that have a high degree of match are parts that are available for on-site repair. If all of the faulty part candidates are parts that are available for on-site repair, the process proceeds to step 109, where on-site repair is proposed. If even one of the faulty part candidates is not a part that is available for on-site repair, the process proceeds to step 110, where on-site repair is not proposed.
[0070] In this manner, in the fourth embodiment, since the importance of the abnormal signal is taken into consideration to identify a candidate faulty part, it is possible to identify the candidate faulty part with higher accuracy and to easily rank a plurality of candidate faulty parts.
[0071] Next, a fifth embodiment of the present invention will be described with reference to Fig. 19 to Fig. 21. The fifth embodiment differs from the first and second embodiments in that the degree of coincidence of the predictive information is obtained by taking into account information on the feature amount of the abnormal signal of each component.
[0072] As shown in FIG. 19, the on-site repair suggestion system of the fifth embodiment is composed of a vehicle-side device 001 installed in each vehicle, and an on-site repair determination device 002 consisting of a server or cloud computer installed in a dealer or the like.
[0073] The vehicle-side device 001 includes a diagnostic device 003, a memory 004, a display unit 005, an ECU 006, and a communication unit 007, similarly to the second embodiment.
[0074] The on-site repair determination device 002 is basically configured to include a failure prediction unit 008, a communication unit 009, a faulty part identification unit 010, a failure sign coincidence diagnosis unit 011, a failure sign detection result database 012, an on-site repair availability determination unit 013, an on-site repair compatible part information database 014, and an on-site repair proposal unit 015, similar to the second embodiment. The fifth embodiment further includes a signal feature amount diagnosis unit 020 that diagnoses what the feature amount of an abnormal signal is for each part, and a signal feature amount database 021 that accumulates information on the signal feature amount. The signal feature amount database 020 stores data of a signal feature amount list 065 that summarizes the abnormal signals of each part and the feature amounts of the abnormal signals, as illustrated in FIG. 20, for example. The signal feature amount list 065 can be created in advance, for example, based on knowledge about each part (design information, test results, etc.). Alternatively, the abnormal signal and its feature amount may be obtained from a large amount of failure sign detection result data 051 (see FIG. 3) that is sequentially stored in the failure sign detection result database 012.
[0075] Fig. 21 is a flow chart showing the process flow of the on-site repair suggestion system of the fifth embodiment. The basic process flow is the same as that of the second embodiment, and first, in step 112, vehicle data is sent from the vehicle-side device 001 to the on-site repair determination device 002. In step 101, failure prediction (detection of signs) is performed on the on-site repair determination device 002 side based on the vehicle data sent from the vehicle-side device 001. Here, data of failure sign detection result 050 such as that shown in Fig. 2 is generated.
[0076] In step 103, information on signs of failure of other vehicles is referenced from the data 051 (FIG. 3) in the failure sign detection result database 012. In step 104, the degree of agreement between the failure sign detection result 050 of the vehicle itself and the information on signs of failure of other vehicles obtained from the failure sign detection result database 012 is diagnosed. As described above, a combination pattern of a plurality of abnormal signals is used to diagnose the degree of agreement.
[0077] Next, in step 120, information (signal feature list 065) in the signal feature database 020 that summarizes information on the features of abnormal signals is referenced, and in the next step 116, prioritization is performed on the parts that had a relatively high degree of match in step 104.
[0078] In the example of FIG. 20, the signal feature list 065 records, for example, that when the precursor detection content is a plug, the abnormal signals are a, b, and c, and that the feature of signal a is the kurtosis of 10 minutes of data, the feature of signal b is the variance of 10 minutes of data, and the feature of signal c is the difference value of 1 minute of data.
[0079] On the other hand, when the predictive detection content is an injector, the abnormal signals are a, b, c, and f. It is recorded that the feature of signal a is the kurtosis of 10 minutes of data, the feature of signal b is the variance of 10 minutes of data, the feature of signal c is the average value of 1 minute of data, and the feature of signal f is the variance of 10 minutes of data.
[0080] Therefore, for example, the feature amount of the detected abnormal signal c of a failure sign is the difference value of the data for one minute for plugs and the average value of the data for one minute for injectors, which are different from each other, so by focusing on the abnormal signal c, it is possible to determine the degree of match with higher accuracy. In other words, by diagnosing the degree of match using the type of signal that has a high contribution to the classification of anomalies among the signals in which an abnormality has been detected, the accuracy of identifying candidate faulty parts is increased.
[0081] Next, in step 106, the data 052 stored in the on-site repair parts information database 014 is referenced, and in step 107, one or more candidate faulty parts (parts determined to have a high degree of match in step 116) are compared with the data 052 in the on-site repair parts information database 014. In step 108, it is determined whether all of the candidate faulty parts with a high degree of match are parts available for on-site repair. If all of the candidate faulty parts are parts available for on-site repair, the process proceeds to step 109, where on-site repair is proposed. If even one of the candidate faulty parts is not a part available for on-site repair, the process proceeds to step 110, where on-site repair is not proposed. [Explanation of symbols]
[0082] 001...Vehicle side device 002...On-site repair judgment device 003...Diagnostic equipment 005...Display section 007…Communications Department 008…Failure prediction department 009…Communications Department 010…Faulty part identification section 011…Failure prediction consistency diagnosis section 012…Failure sign detection result database 013…On-site repair availability determination department 014…On-site repair parts information database 015…On-site repair proposal department
Claims
1. Detects signs of failure in vehicle parts, Based on the symptoms, one or more candidate faulty parts are identified, Determine whether each defective part can be repaired by on-site service, Based on this determination, a repair plan, including an on-site repair, is proposed to the user. How to propose repairs for your vehicle.
2. moreover, Diagnosing whether the vehicle is in a condition to be driven based on the vehicle data; Propose a repair plan taking into account whether the vehicle can be driven or not.
2. The vehicle repair recommendation method of claim 1.
3. If the defective part can be repaired by on-site repair, we will propose on-site repair.
2. The vehicle repair recommendation method of claim 1.
4. If all of the multiple defective part candidates can be repaired by on-site repair, propose on-site repair.
2. The vehicle repair recommendation method of claim 1.
5. If the multiple possible faulty parts include a part that cannot be repaired on-site and the vehicle is still drivable, we will suggest a visit to the dealer.
3. The vehicle repair recommendation method of claim 2.
6. If the multiple defective part candidates include a part that cannot be repaired by on-site repair and the vehicle cannot be driven, we will suggest transporting it to a dealer.
3. The vehicle repair recommendation method of claim 2.
7. Based on preset on-site repair compatible part information, it is determined whether each of the defective part candidates can be handled by on-site repair.
2. The vehicle repair recommendation method of claim 1.
8. The on-site repair compatible parts information is updated using data on the on-site repair that has actually been performed.
8. The vehicle repair recommendation method of claim 7.
9. determining a probability that each of a plurality of candidate faulty parts is a part that needs to be repaired or replaced; If the probability of the defective part candidate being repairable by on-site repair is equal to or greater than a predetermined threshold, an on-site repair is proposed even if the defective part candidate is not repairable by on-site repair.
5. The vehicle repair recommendation method of claim 4.
10. A plurality of faulty part candidates are arranged in order of priority, and if the faulty part candidates in a predetermined upper range are capable of being handled by on-site repair, an on-site repair is proposed even if the faulty part candidates in the lower range are not capable of being handled by on-site repair.
5. The vehicle repair recommendation method of claim 4.
11. Identifying potential faulty parts by referring to diagnostic data that compiles past symptom information and diagnostic results for other vehicles; 2. The vehicle repair recommendation method of claim 1.
12. The diagnostic data includes past symptom information and corresponding repair / replacement parts that have been repaired or replaced with good results, Extracting parts for repair or replacement that have a high degree of match between the detected predictive information and past predictive information in the diagnostic data as candidate faulty parts; 12. The vehicle repair recommendation method of claim 11.
13. Identifying a candidate faulty part based on the degree of agreement between the types of multiple abnormal signals when the symptom is detected and the types of abnormal signals included in the past symptom information of other vehicles in the diagnostic data.
13. The vehicle repair recommendation method of claim 12.
14. The importance of multiple abnormal signals is determined for each component. Considering the importance of each signal, the degree of agreement between the detected predictive information and past predictive information is calculated.
13. The vehicle repair recommendation method of claim 12.
15. The importance level is set based on accumulated diagnostic data.
15. The vehicle repair recommendation method of claim 14.
16. When the feature amount of the abnormal signal is different for each of the plurality of components, the abnormal signal is determined as an abnormal signal having a high contribution to the abnormality classification; The abnormal signal with the highest contribution is given priority, and the degree of agreement between the detected predictive information and past predictive information is calculated.
13. The vehicle repair recommendation method of claim 12.
17. The feature amount is set based on accumulated diagnostic data.
17. The vehicle repair recommendation method of claim 16.
18. The system detects signs of failure in vehicle parts on the vehicle side, The vehicle acquires the warning information and sends it to a server. This server identifies potential faulty parts and proposes repair plans.
2. A method for providing repair suggestions to a vehicle as recited in claim 1.
19. A failure prediction unit that detects a sign of failure of a vehicle component; a faulty part identification unit that identifies one or more faulty part candidates based on the symptom; an on-site repair feasibility determination unit that determines whether or not each of the candidate faulty parts can be repaired by on-site repair; a repair policy suggestion unit that proposes a repair policy, including on-site repair, to the user based on the determination; A vehicle repair suggestion device comprising:
Citation Information
Patent Citations
Maintenance time informing device
JP2008308075A
