Auxiliary diagnosis method and device for automobile related faults

By combining the technology of the benchmark database and data middle platform in car maintenance, we generate the combination of related phenomena and the ranking of fault causes, the problem that maintenance technicians find it difficult to detect related phenomena is solved, the accuracy and efficiency of fault diagnosis is improved, and the maintenance quality is improved.

CN116560343BActive Publication Date: 2024-12-03WUHAN PINZHI AUTOMOBILE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310604122.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-05-26
Publication Date
2024-12-03
Estimated Expiration
2043-05-26

AI Technical Summary

Technical Problem

During the car maintenance process, it is difficult for maintenance technicians to discover causal or concomitant relationships with known fault phenomena, resulting in low maintenance quality, and the existing technology relies on experience or consulting guidance, which is time-consuming and prone to diagnostic errors.

Method used

Based on the benchmark database and data middle platform, combining theoretical and practical data, benchmark diagnostic data is generated, and online auxiliary diagnostic system is provided, the user obtains fault information, and the data middle platform generates related phenomenon combinations and possible fault causes sorting, and guides maintenance The technician conducted a check.

Benefits of technology

It improves the accuracy and efficiency of fault diagnosis by maintenance technicians, ensures synchronous inspection of potential fault phenomena, and improves the quality of maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116560343B_ABST
    Figure CN116560343B_ABST
Patent Text Reader

Abstract

The present invention discloses an auxiliary diagnosis method and device for automobile-related faults, the method is applied to an auxiliary diagnosis system for automobile-related faults, the system includes a user terminal and a data middle station in communication connection, the auxiliary diagnosis method for automobile-related faults includes: the user terminal obtains fault information; the user terminal sends the fault information to the data middle station; the data middle station generates a combination of related phenomena corresponding to known fault phenomena according to the fault information; the data middle station recommends the corresponding possible fault cause ranking and the diagnosis and maintenance instructions of the corresponding fault cause according to each known fault phenomenon; the data middle station sends the combination of related phenomena, the possible fault cause ranking and the diagnosis and maintenance instructions of the corresponding fault cause to the user terminal. The auxiliary diagnosis method for automobile-related faults of the present invention can achieve the purpose of assisting maintenance technicians to complete fault diagnosis and maintenance, and improves work efficiency and accuracy.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of automobile fault diagnosis, and in particular to an auxiliary diagnosis method and device for automobile related faults. Background Art

[0002] With the continuous development and application of automotive electronics and sensor technology, especially the rapid development of new energy vehicles, while improving the overall performance of the vehicle, it also makes the automotive mechanical and electrical structure more complex, and also makes it more difficult for maintenance technicians to quickly identify fault phenomena, accurately locate the cause of the fault, and the fault location.

[0003] In the actual maintenance process, for most car failures, maintenance technicians can easily understand the fault information through human perception or diagnostic instruments, and then diagnose and repair according to the fault information. However, sometimes there may be some other related phenomena that have a causal or associated relationship with the known phenomenon that are difficult to be discovered, resulting in low maintenance quality.

[0004] The information disclosed in this background technology section is only intended to enhance the understanding of the overall background of the invention and should not be regarded as an acknowledgment or any form of suggestion that the information constitutes the prior art already known to a person skilled in the art. Summary of the invention

[0005] The purpose of the present invention is to provide an auxiliary diagnosis method and device for automobile related faults, which can guide maintenance technicians online to check the related phenomena that have causal or associated relationships with known fault phenomena and the possible causes of each fault phenomenon in turn, thereby achieving the purpose of assisting maintenance technicians to complete fault diagnosis and maintenance, and improving work efficiency and accuracy.

[0006] To achieve the above-mentioned objectives, in a first aspect, the present invention provides an auxiliary diagnosis method and device for automobile-related faults, the method being applied to an auxiliary diagnosis system for automobile-related faults, the system comprising a user terminal and a data middle station in communication connection, the auxiliary diagnosis method for automobile-related faults comprising: step S100, the user terminal obtains fault information; step S200, the user terminal sends the fault information to the data middle station; step S300, the data middle station generates a combination of related phenomena corresponding to known fault phenomena based on the fault information; step S400, the data middle station recommends a corresponding possible fault cause ranking and a corresponding diagnosis and repair description of the fault cause based on each known fault phenomenon; step S500, the data middle station sends the combination of related phenomena, the possible fault cause ranking and the corresponding diagnosis and repair description of the fault cause to the user terminal.

[0007] In one embodiment of the present invention, step S100 includes: the user terminal obtains VIN information and fault phenomenon information input by the user.

[0008] In one embodiment of the present invention, the fault phenomenon information includes: DTC-related fault phenomena and non-DTC-related fault phenomena.

[0009] In one embodiment of the present invention, step S300 includes: the data center extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomenon based on the fault information, and generates and outputs a corresponding associated phenomenon combination.

[0010] In one embodiment of the present invention, step S400 includes: the data center counts the occurrence frequency of the fault causes of each known fault phenomenon in the preset database, sorts them, and generates a possible fault cause sorting and diagnostic maintenance instructions.

[0011] In the second aspect, the present invention provides an auxiliary diagnosis device for automobile-related faults, the device is applied to an auxiliary diagnosis system for automobile-related faults, the system includes a user end and a data middle station in communication connection, and the auxiliary diagnosis device for automobile-related faults includes: an acquisition module, a first sending module, a generation module, a recommendation module and a second sending module. The acquisition module is used for the user end to acquire fault information; the first sending module is used for the user end to send the fault information to the data middle station; the generation module is used for the data middle station to generate a combination of related phenomena corresponding to a known fault phenomenon based on the fault information; the recommendation module is used for the data middle station to recommend the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance instructions based on each known fault phenomenon; the second sending module is used for the data middle station to send the combination of related phenomena, the possible fault cause ranking and the corresponding fault cause diagnosis and maintenance instructions to the user end.

[0012] In one embodiment of the present invention, the user end acquires the fault information including: the user end acquires the VIN information and the fault phenomenon information input by the user through an acquisition module.

[0013] In one embodiment of the present invention, the fault phenomenon information includes: DTC-type fault phenomenon and non-DTC-type fault phenomenon.

[0014] In one embodiment of the present invention, the data middle platform generates a combination of associated phenomena corresponding to a known fault phenomenon based on the fault information, including: the data middle platform extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomenon based on the fault information, and generates and outputs a corresponding combination of associated phenomena.

[0015] In one embodiment of the present invention, the data center recommends a corresponding possible fault cause ranking and a corresponding diagnostic and repair description of the fault cause based on each known fault phenomenon, including: the data center counts the occurrence frequency of the fault cause of each known fault phenomenon in a preset database, and sorts them to generate a possible fault cause ranking and a diagnostic and repair description.

[0016] Compared with the prior art, the auxiliary diagnosis method and device for automobile related faults according to the present invention can guide maintenance technicians online to check the related phenomena that have causal or associated relationships with known fault phenomena and the possible causes of each fault phenomenon in turn, thereby achieving the purpose of assisting maintenance technicians to complete fault diagnosis and maintenance, and improving work efficiency and accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a flow chart of an auxiliary diagnosis method for automobile related faults in Embodiment 1 of the present invention;

[0018] Figure 2 It is a structural schematic diagram of an auxiliary diagnosis device for automobile related faults in embodiment 1 of the present invention. DETAILED DESCRIPTION

[0019] The embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the embodiments of the present invention, rather than to limit the embodiments of the present invention. It is also necessary to explain that, for ease of description, only parts related to the embodiments of the present invention are shown in the accompanying drawings, rather than all structures.

[0020] To facilitate understanding, the main implementation concepts of the embodiments of the present invention are first briefly described.

[0021] With the electrification, new energy, and intelligent networking of automobiles, automobile failures are no longer simple mechanical problems. There are more electrical failures, system communications, and network bus failures. Automobile failures have become more complicated, involving comprehensive problems in multiple fields, which has brought unprecedented challenges to maintenance technicians. The number of intelligent and networked cars in society is constantly increasing, but it takes a long time to train a qualified auto repair expert, so that the supply and demand relationship is seriously unbalanced. In particular, verifying and solving faults based on experience or consulting relevant personnel for technical guidance is time-consuming and prone to diagnostic errors. In addition, it is impossible to simultaneously check potential fault phenomena, and the maintenance quality is low.

[0022] In the actual maintenance process, for most car failures, maintenance technicians can easily understand the fault information through human perception or diagnostic instruments, and then diagnose and repair according to the fault information. However, sometimes there may be some other related phenomena that have a causal or associated relationship with the known phenomenon that are difficult to be discovered, resulting in low maintenance quality.

[0023] The inventor discovered the technical defects as described in the previous background technology, and then hoped to find a way to avoid maintenance technicians from missing the investigation of related phenomena during the actual maintenance process through a reasoning model that combines theory with actual data on the basis of a benchmark database and a data middle platform, and to systematically guide maintenance technicians to investigate the possible causes of fault phenomena.

[0024] In order to solve the technical problems existing in the prior art that it is time-consuming and prone to diagnostic errors to verify and solve faults based on experience or consult relevant personnel for technical guidance, and that potential fault phenomena cannot be checked simultaneously, resulting in low maintenance quality, the inventor of the present invention has obtained an auxiliary diagnosis method and device for automobile-related faults through creative labor.

[0025] The auxiliary diagnosis method and device for automobile related faults of the present invention are based on a benchmark database and a data middle platform. Through a reasoning model that combines theory with actual data, it can guide maintenance technicians online to check the related phenomena that have causal or associated relationships with known fault phenomena and the possible causes of each fault phenomenon in turn, thereby achieving the purpose of assisting maintenance technicians to complete fault diagnosis and maintenance, and improving work efficiency and accuracy.

[0026] Specifically, the above-mentioned benchmark database is constructed by a method for extracting information from automobile fault diagnosis big data, which specifically includes:

[0027] Based on the historical diagnosis database, the historical fault diagnosis data in the historical diagnosis database is classified and cleaned to generate data to be sampled. As a carrier of repair and maintenance information that has occurred during the actual driving of the vehicle, the historical diagnosis database contains a large number of different fault phenomena and the corresponding fault cause information; by classifying and cleaning the historical fault diagnosis data in the historical diagnosis database, the data to be sampled is generated for subsequent sampling and extraction. The automobile fault diagnosis big data information extraction method is based on the historical fault diagnosis data in the historical diagnosis database. The historical fault diagnosis data includes a large number of different fault phenomena and the corresponding fault cause information of a large number of different vehicles. By classifying and cleaning the information in the historical diagnosis database in a targeted manner, it is convenient for subsequent sampling and use, which greatly avoids the waste of manpower due to processing invalid data.

[0028] Through the data processing tool, the sampled data is sampled and information is extracted to generate benchmark diagnostic data. Two operation permissions are preset in the data processing tool: the phenomenon processing end (phenomenon processing module) and the cause processing end (cause processing module). The fault phenomenon and fault cause information in the sampled data are extracted and reviewed (through the sampling module) to generate benchmark diagnostic data. Through the data processing tool, the sampled data is sampled and information is extracted to generate benchmark diagnostic data. The benchmark diagnostic data is the data after the effective information in the historical diagnostic data is extracted, which makes the technical logic of the generated benchmark diagnostic data clearer, and is convenient for maintenance personnel to directly learn from experience, thereby achieving the purpose of improving their skill level.

[0029] The benchmark diagnostic data is submitted and stored in the benchmark database. The benchmark database stores the final benchmark diagnostic data, which is convenient for maintenance personnel to retrieve, view and learn at any time, so as to achieve the purpose of improving their skills.

[0030] The data processing tool includes a sampling module, a phenomenon processing module, and a cause processing module. The data processing tool can be a virtual software or a physical organization, with multiple functions (modules) built in. By setting parameters, specific functions can be realized. The data processing tool can expand different functions according to different user needs, which is convenient for users to use, thereby effectively improving the efficiency of data extraction, classification, cleaning and generation of benchmark diagnostic data.

[0031] Based on the historical diagnostic database, the historical fault diagnosis data in the historical diagnostic database is classified and cleaned, and the data to be sampled is generated, including: extracting the information of the historical fault diagnosis data stored in the historical diagnostic database through a first preset strategy to generate diagnostic data; classifying and cleaning the diagnostic data through a second preset strategy to generate the data to be sampled. The first preset strategy can specifically be the maintenance type, brand, vehicle model, fault phenomenon description, fault cause part number and fault cause name, etc.; through the first preset strategy, effective information can be extracted from the historical fault diagnosis data, thereby generating diagnostic data. Through the first preset strategy, the required information can be targetedly screened and extracted to generate diagnostic data, and it is beneficial to reduce the amount of data calculation of the fault diagnosis big data information extraction device in subsequent data processing. The second preset strategy is specifically to classify the data in the historical diagnostic database, clear the useless data in the historical diagnostic database that has extremely low reference value for analyzing fault diagnosis, and then retain the data to be sampled in the historical diagnostic database that is beneficial to analyzing fault diagnosis information. For example, the diagnostic data in the historical diagnostic database is classified into "invalid data" for the maintenance type of "normal maintenance" and "quality rectification" and the data containing "passive upgrade", "commercial vehicle inspection", "body corrosion" and other words in the "fault phenomenon description". Through the two preset strategies, the data to be sampled that is conducive to the subsequent extraction of effective fault diagnosis information can be accurately screened, which greatly reduces the workload of processing complex data.

[0032] The data to be sampled is sampled and information is extracted by a data processing tool to generate the reference diagnostic data, including: presetting a DTC diagnostic data identification rule in the sampling module; presetting a sample sampling rule in the sampling module, sampling the data to be sampled, and generating sample sampling data; extracting the fault diagnosis information in the DTC and non-DTC data in the sample sampling data, and generating the reference diagnostic data. The data processing tool is presetting a DTC diagnostic data keyword identification rule, and when the preset keyword appears in the "fault phenomenon description" of the fault diagnosis big data, the data processing tool automatically identifies the diagnostic data containing the DTC fault phenomenon, so as to facilitate the subsequent extraction of information in the diagnostic data, and extract the DTC diagnostic data separately; the identification rule is specifically: presetting words, letters, and numbers such as "current, read, fault code, report code, instrument display, computer check, OBD, FC, SPN, FMI, DTC" in the data processing tool, matching the preset keywords with the diagnostic big data, and identifying the DTC diagnostic data containing the keywords; and performing rolling maintenance on the keywords preset in the data processing tool for identifying the DTC diagnostic data. Preset DTC diagnostic data keyword recognition rules in the data processing tool can quickly obtain and identify DTC diagnostic data, which is convenient for subsequent extraction of DTC fault information. Set sampling rules and sample DTC and non-DTC fault diagnostic data in the data processing tool, and ensure that the sample covers all the diagnostic data of the fault cause parts that have appeared as much as possible; the data processing tool samples and extracts information from the sampled data by setting sampling rules, and covers all the diagnostic data of the fault cause parts that have appeared during the sampling process, which is conducive to cutting the workload of data processing step by step and summarizing and improving the information extraction rules for different types of diagnostic data in the future.

[0033] Submitting the reference diagnostic data to the reference database includes: the data processing tool submits the reference diagnostic data to the reference database. The final reference diagnostic data is stored in the reference database, which is convenient for maintenance personnel to retrieve and view at any time, thereby improving the work efficiency of maintenance personnel and effectively ensuring the accuracy of maintenance diagnosis.

[0034] Extracting fault diagnosis information from the DTC and non-DTC data in the sampled data and generating the reference diagnostic data includes: the phenomenon processing module extracting phenomenon keywords from the data of the marked meaning DTC class, comparing the phenomenon keywords extracted from the entry with the DTC code general meaning library, determining the DTC code corresponding to the DTC phenomenon keyword and the general meaning of the corresponding code, and using the corresponding DTC code as the first phenomenon general word corresponding to the DTC phenomenon keyword. The phenomenon processing module extracts phenomenon keywords from the data of the non-marked meaning DTC class, creates corresponding second phenomenon general words according to the extracted phenomenon keywords, and determines the technical logic between the phenomenon keywords and the second phenomenon general words. The cause processing module extracts fault cause keywords from the data of the non-marked meaning DTC class, creates corresponding cause general words according to the extracted fault cause keywords, and determines the technical logic between the second phenomenon general words, the fault cause keywords and the cause general words. The reference diagnostic data is generated based on the first phenomenon general words, the second phenomenon general words and the cause general words. The extraction of DTC diagnostic data information is to match the extracted keywords with the DTC codes in the DTC code general meaning library; if there is only one DTC that matches the keyword, the corresponding DTC code and the general meaning of the corresponding code are called; if there are multiple DTCs in the DTC code general meaning library that match the DTC phenomenon keywords in the diagnostic data, the VIN corresponding to the vehicle in the diagnostic data is used to retrieve the loading list of the vehicle model corresponding to the VIN, and the key parts number associated with the product subsystem to which each DTC belongs (i.e., the different functional systems or parts assemblies divided in the vehicle) is matched one by one with the part number in the loading list of the target vehicle model, and the DTC phenomenon keyword corresponding to the DTC code and the corresponding code general meaning are determined by the matching results. Since there is a corresponding standard fault cause description in the meaning of the DTC fault code, there is no need to repeatedly create the corresponding fault cause keyword and cause general word. Among them, the DTC code general meaning library contains: DTC code, product subsystem, fault code general meaning, key parts number and other elements.The information extraction of non-DTC diagnostic data includes the extraction of fault phenomenon information. The phenomenon processing module extracts the phenomenon keywords in the fault diagnosis data, creates corresponding common phenomena based on the extracted phenomenon keywords, reviews the technical logic between the phenomenon keywords and the phenomenon common words, completes the extraction of fault phenomenon information, and submits it to the benchmark database; for example: the phenomenon description in the fault diagnosis data is: the right side window lifter cannot be raised or lowered; the extractable phenomenon keywords are: right side glass, cannot be raised or lowered; the corresponding phenomenon common words can be created as: the right door glass cannot be raised or lowered; among them, in order to show that there are causal or associated relationships between different fault phenomena, when extracting keywords for multiple fault phenomena contained in the same diagnostic data, all the keywords of the fault phenomena with causal or associated relationships need to be extracted and shared, and the fault phenomena without causal or associated relationships have fault keywords extracted separately, and cross-brand common phenomenon common words are created according to different fault phenomenon keywords. The extraction of non-DTC diagnostic data information also includes the extraction of fault cause information. The cause processing module extracts the corresponding fault cause keywords in the diagnostic data, and creates corresponding cause general words based on the extracted fault cause keywords. It performs technical and logical judgment on the phenomenon general words, fault cause keywords, and cause general words to complete the extraction and submission of fault cause information. When the cause base word is created, it is created in the form of fault cause component + failure mode. For example, the fault diagnosis data is described as: the right side window lifter cannot be raised or lowered. After inspection, it is found that the glass lifter motor is not working. The extractable cause keywords are: right side glass, glass lifter motor, not working; the corresponding cause general words can be created as: right door glass lifter motor is damaged; the fault cause component is: right door glass lifter motor, and the failure mode is: damaged; when a single phenomenon involves multiple fault causes, it is necessary to extract the corresponding fault cause keywords for different fault causes, and create corresponding fault cause general words according to different fault cause keywords. Since different brands and models may have different names for the same parts, or different keyword descriptions for the same fault phenomenon, when creating common words, the common words corresponding to different fault phenomena and fault cause keywords can be the same; the common words corresponding to the same fault phenomenon and fault cause keywords must be the same. The benchmark diagnostic data generated here refers to the standard data stored in the benchmark database after the common words and logical relationships extracted above are determined. The extracted information is submitted to the benchmark database. For the fault phenomena and fault cause information that need further review and confirmation, the phenomenon processing end and the cause processing end can color-code them and label them as "pending", and organize experts to conduct technical reviews; the diagnostic data after the review and confirmation is stored in the benchmark database and the benchmark diagnostic data after information extraction is used as historical maintenance data.

[0035] The above content elaborates on the origin of the benchmark database, and the present invention is based on the benchmark database to generate the inference of automobile fault diagnosis related phenomena.

[0036] Embodiment 1

[0037] Figure 1 FIG. 1 is a flow chart of an auxiliary diagnosis method for automobile related faults in Embodiment 1 of the present invention. Figure 1 As shown, an auxiliary diagnosis method for automobile-related faults provided in Embodiment 1 is applied to an auxiliary diagnosis system for automobile-related faults, the system comprising a user terminal and a data middle station connected in communication, and the auxiliary diagnosis method for automobile-related faults comprises:

[0038] Step S100, the user terminal obtains fault information;

[0039] Step S200, the user terminal sends the fault information to the data center;

[0040] Step S300: The data center generates a combination of associated phenomena corresponding to known fault phenomena according to the fault information;

[0041] Step S400, the data center recommends the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance instructions according to each known fault phenomenon;

[0042] In step S500, the data center sends the combination of related phenomena, the ranking of possible fault causes, and the diagnostic and repair instructions corresponding to the fault causes to the user end.

[0043] Specifically, fault phenomenon information input: the user-side software identifies the VIN information input by the maintenance technician, and guides the maintenance technician to enter the fault phenomenon information in the DTC search box and the symptom search box according to the actual type of fault phenomenon that occurred in the target vehicle model; DTC type fault phenomenon information input: the maintenance technician enters the obtained DTC code of the faulty vehicle in the DTC search box, and the user-side software recommends and displays a list of all connected vehicle DTCs containing the code based on the input DTC code; the maintenance technician connects to the diagnostic instrument and verifies whether the DTC type fault phenomenon exists according to the sub-product system; non-DTC type fault phenomenon input: the maintenance technician enters the phenomenon word for the non-DTC type fault phenomenon in the symptom search box, and the user-side software matches the input with the phenomenon keyword in the data in real time, and recommends phenomenon keyword groups incrementally, and the maintenance technician checks the recommended phenomenon keywords.

[0044] For example: The technician first enters the phenomenon word A

[0045] First-level recommendation: A, B

[0046] A.C ...

[0048] If phenomenon B also exists, then check phenomenon B.

[0049] Secondary recommendation: A, B, C

[0050] A, B, D ...

[0052] Among them, the phenomenon keyword group is matched by the data center based on the phenomenon word input by the software on the user side and the phenomenon keyword extracted from the historical fault diagnosis big data (benchmark database), and all phenomenon keyword groups containing the phenomenon word are recommended based on the input.

[0053] Based on the above analysis, it can be seen that in this embodiment, the software on the user side receives the VIN information input by the maintenance technician, and guides the maintenance technician to gradually input the fault information. The data middle platform recommends a combination of related phenomena corresponding to the known phenomena for the input fault information based on the fault information received by the software on the user side, and recommends the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance methods according to each fault phenomenon. The maintenance technician is guided online to check the related phenomena that have a causal or associated relationship with the known fault phenomenon and the possible fault causes of each fault phenomenon in turn, thereby achieving the purpose of assisting the maintenance technician to complete fault diagnosis and maintenance, and improving work efficiency and accuracy.

[0054] In this embodiment, step S100 includes: the user terminal obtains VIN information and fault phenomenon information input by the user.

[0055] In this embodiment, the fault phenomenon information includes: DTC-related fault phenomena and non-DTC-related fault phenomena.

[0056] In this embodiment, step S300 includes: the data center extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomenon based on the fault information, and generates and outputs a corresponding associated phenomenon combination.

[0057] In this embodiment, step S400 includes: the data center counts the occurrence frequency of the fault cause of each known fault phenomenon in the preset database, sorts them, and generates a possible fault cause sorting and diagnostic maintenance instructions.

[0058] Specifically, the recommendation and selection of related phenomena: the software on the user side determines the fault phenomenon (DTC category + non-DTC category) corresponding to the target vehicle based on the checked confirmed phenomenon keywords; outputs the corresponding related phenomena for the phenomena with the same fault cause association frequency as the known fault phenomena in the historical fault diagnosis big data; the data center infers the combination of phenomena with the same fault cause association frequency as the known fault phenomena based on the fault phenomena input by the software on the user side, and outputs the combination of related phenomena with the most known fault phenomena; for the phenomena with no association frequency, the known phenomena are output as independent phenomena; for all related phenomena with association frequency with the known fault phenomena, the data center counts the occurrence frequency of each related phenomenon in the historical fault diagnosis big data in turn, and calculates the correlation between the related phenomenon and the known phenomenon. The software on the user side first sorts the related phenomena in the data center in descending order according to the association frequency, and then sorts them in descending order according to the correlation degree of each related phenomenon, and generates a recommended related phenomenon sorting table for known phenomena. The maintenance technician checks the related phenomena that have been determined in the related phenomenon sorting table to avoid missing the diagnosis of other phenomena associated with the known fault phenomena; among them, for the DTC-type phenomena recommended in the related phenomenon sorting table, the maintenance technician can connect the diagnostic instrument to verify whether the DTC fault code exists and clear it.

[0059] Specifically, possible causes are checked: the user-side software recommends the above-mentioned related phenomena, and the related phenomena and independent phenomena that are checked in the vehicle are sorted and displayed in order from left to right according to the severity of the phenomena; based on the combination of fault phenomena displayed by the user-side software, the data center recommends the fault causes, fault cause parts, failure modes and other information that may cause each fault phenomenon, and counts the occurrence frequency of the fault cause part name and fault cause part number in each fault cause. The user-side software sorts the possible cause parts in descending order according to the number of phenomena involved in the cause parts in the phenomenon combination; when the maintenance technician inquires about the possible cause parts of the known phenomena and their fault causes, the user-side software gives priority to displaying the fault cause parts, and then expands the fault cause parts to display the failure mode sorting they contain.

[0060] Specifically, possible cause investigation and fault diagnosis: the maintenance technician recommends possible cause parts and possible cause rankings based on the phenomenon to be queried, and by checking the possible cause parts and their failure modes, the user-side software displays the diagnosis and repair methods of each fault cause; the maintenance technician diagnoses and investigates each possible cause in turn and checks the fault phenomena that have been eliminated until all faults are investigated and eliminated, assisting the maintenance technician in completing the diagnosis and repair of all possible fault phenomena of the target vehicle.

[0061] Based on the above analysis, it can be seen that in this embodiment, the software on the user side receives the VIN information input by the maintenance technician, and guides the maintenance technician to gradually input the fault information. The data middle platform recommends a combination of related phenomena corresponding to the known phenomena for the input fault information based on the fault information received by the software on the user side, and recommends the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance methods according to each fault phenomenon. The maintenance technician is guided online to check the related phenomena that have a causal or associated relationship with the known fault phenomenon and the possible fault causes of each fault phenomenon in turn, thereby achieving the purpose of assisting the maintenance technician to complete fault diagnosis and maintenance, and improving work efficiency and accuracy.

[0062] Embodiment 2

[0063] Figure 2 Schematic diagram of the structure of an auxiliary diagnosis device for automobile related faults in the first embodiment of the present invention. Figure 2 As shown, an auxiliary diagnosis device for automobile-related faults provided in the first embodiment is applied to an auxiliary diagnosis system for automobile-related faults, the system includes a user terminal and a data middle station connected in communication, and the auxiliary diagnosis device for automobile-related faults includes: an acquisition module 601, a first sending module 602, a generation module 603, a recommendation module 604, and a second sending module 605. The acquisition module 601 is used for the user terminal to acquire fault information; the first sending module 602 is used for the user terminal to send the fault information to the data middle station; the generation module 603 is used for the data middle station to generate a combination of related phenomena corresponding to a known fault phenomenon according to the fault information; the recommendation module 604 is used for the data middle station to recommend the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance instructions according to each known fault phenomenon; the second sending module 605 is used for the data middle station to send the combination of related phenomena, the possible fault cause ranking, and the corresponding fault cause diagnosis and maintenance instructions to the user terminal.

[0064] In this embodiment, the user terminal acquires the fault information including: the user terminal acquires the VIN information and the fault phenomenon information input by the user through the acquisition module 601 .

[0065] In this embodiment, the fault phenomenon information includes: DTC-related fault phenomena and non-DTC-related fault phenomena.

[0066] In this embodiment, the data middle platform generates a combination of associated phenomena corresponding to the known fault phenomenon based on the fault information, including: the data middle platform extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomenon based on the fault information, and generates and outputs a corresponding combination of associated phenomena.

[0067] In this embodiment, the data center recommends the corresponding possible fault cause ranking and the corresponding diagnostic and repair instructions based on each known fault phenomenon, including: the data center counts the occurrence frequency of the fault cause of each known fault phenomenon in the preset database, and sorts them to generate the possible fault cause ranking and diagnostic and repair instructions.

[0068] For all the associated phenomena that have an associated frequency with the known fault phenomenon, the data center station sequentially counts the occurrence frequency of each associated phenomenon in the historical fault diagnosis big data, calculates the correlation between the associated phenomenon and the known phenomenon, and generates the correlation ranking of each associated phenomenon. The specific method is to use an inference generation method for automobile fault diagnosis associated phenomena, which specifically includes:

[0069] The data center counts the occurrence frequency of the fault causes of each fault phenomenon in the preset database;

[0070] The data center derives the correlation between different fault phenomena with the same fault cause and generates a correlation ranking for each related phenomenon.

[0071] Specifically, the above-mentioned preset database is the benchmark database mentioned above, and the data middle platform is a data processing center that processes the benchmark data in the benchmark database, mainly to conduct frequency statistics on the causes of various fault phenomena in the benchmark data.

[0072] Based on the above analysis, the data center can lay the foundation for the subsequent reasoning of the correlation logic between various fault phenomena by statistically analyzing the occurrence frequency of the fault causes of various fault phenomena in the benchmark database.

[0073] Specifically, the data center derives the correlation between different fault phenomena with the same fault cause based on the benchmark data extracted from the benchmark database, and generates a correlation ranking for each related phenomenon.

[0074] Based on the above analysis, it can be seen that through the reasoning model that combines theory with actual data, the correlation logic between various fault phenomena is systematically sorted out, which helps maintenance technicians to simultaneously check potential fault phenomena in the actual fault diagnosis process, improve maintenance quality, and improve work efficiency and accuracy.

[0075] Among them, the frequency of occurrence of the fault causes of each fault phenomenon in the preset database of the data center statistics includes:

[0076] The data center extracts keywords from the preset database that are used to describe fault phenomena and fault causes.

[0077] According to the extracted keywords of the fault phenomenon and the extracted keywords of the fault cause, corresponding common phenomenon words and common cause words that are common across brands are created respectively.

[0078] The data center platform performs frequency statistics on the occurrence of each group of fault phenomena and fault causes in the preset database within the same product subsystem based on each group of common phenomenon words and common cause words created.

[0079] Specifically, keywords used to describe fault phenomena and fault cause information in historical fault diagnosis big data (benchmark data) are extracted. Since different brands and models have different names for the same parts and different keyword descriptions for the same fault phenomenon, corresponding cross-brand common phenomenon common words and cause common words are created based on the extracted keywords, and the association logic between keywords and common words is established, and technical logic judgments are made between fault phenomena and fault causes. Based on each group of cause common words and phenomenon common words created, the data center performs frequency statistics on the number of occurrences of each group of phenomena + causes in the benchmark data within the same product subsystem. For example: Fault phenomenon A has 1, 2, 3, 4... and other fault causes. When counting the frequency, the data center performs statistics in the benchmark database according to the fault cause name and part number of the fault cause part in the fault cause according to the phenomenon + cause (A-1, A-2...).

[0080] Based on the above analysis, the data center can lay the foundation for the subsequent reasoning of the correlation logic between various fault phenomena by statistically analyzing the occurrence frequency of the fault causes of various fault phenomena in the benchmark database.

[0081] Among them, the data center derives the correlation between different fault phenomena with the same fault cause, and generates the correlation ranking of each related phenomenon, including:

[0082] The data center generates the first associated phenomenon based on the preset database reasoning;

[0083] The data center generates the second related phenomenon based on the preset fault diagnosis and troubleshooting process;

[0084] The data center performs association logic judgment based on the first association phenomenon and the second association phenomenon, and generates a correlation ranking of each association phenomenon.

[0085] Specifically, the data middle platform infers related phenomena based on the benchmark database. According to the fault phenomena and fault cause information extracted from the big data of various fault diagnosis that actually occurred in history, the correlation between different fault phenomena with the same fault cause is inferred to generate the first related phenomenon.

[0086] Based on the above analysis, the data center conducts quantitative statistics on other fault phenomena in the benchmark database that have the same cause as the current fault phenomenon according to the automobile sub-functional product system (i.e., different functional systems or parts assemblies divided in the vehicle), establishes a phenomenon correlation algorithm model, counts the number of common fault causes between other fault phenomena and the current fault phenomenon, and calculates the correlation between other fault phenomena and the current fault phenomenon based on the phenomenon correlation algorithm model.

[0087] Specifically, the data center generates the second related phenomenon based on the fault diagnosis and troubleshooting process reasoning. According to the control modules on the vehicle (such as the engine electronic control module, ABS electronic control module, etc.), the DTC-type fault phenomena of the phenomenon troubleshooting process in the historical fault diagnosis manual are extracted, and the extracted DTC-type fault phenomena are matched with the DTC code general meaning library to determine the general meaning of the DTC code corresponding to the DTC-type phenomenon code and the fault cause, which are stored in the benchmark database.

[0088] Based on the above analysis, the data center performs quantitative statistics (i.e., frequency) on the general meaning and fault causes of each group of DTC codes contained in the historically developed vehicle models, and calculates the correlation of DTC-type fault phenomena with the same cause and the same general meaning with reference to the correlation algorithm model in the above step S201, generates the correlation of DTC-type fault phenomena in the same control module, and completes the correlation phenomenon reasoning of DTC-type fault phenomena in the fault phenomenon troubleshooting process.

[0089] Specifically, the data center performs association logic judgment based on the first association phenomenon and the second association phenomenon, performs association logic judgment on the association phenomena that are inferred to have causal or associated relationships in the above two methods, and generates a correlation ranking of each association phenomenon. When confirming the recommended association phenomenon, for phenomena that have been technically judged and confirmed to have association logic, there is no need to perform the association calculation in the above two steps (the data center generates the first association phenomenon based on the preset database inference and the data center generates the second association phenomenon based on the preset fault diagnosis and troubleshooting process inference); for unconfirmed inference phenomena, the data center sets an association threshold screening condition (the association is greater than or equal to 80%, and this threshold can be adjusted according to the actual calculation results), so as to recommend association phenomena on the user-side software for association phenomena that meet the association threshold condition. The data center collects the recommended association phenomenon results checked by the maintenance technician in the user-side software, and technically judges that the association logic between the recommended association phenomenon and the known phenomenon is reasonable, thereby completing the confirmation of the association logic between each association phenomenon (generating a correlation ranking for each association phenomenon).

[0090] Among them, the data center generates the first association phenomenon based on the preset database inference, including:

[0091] The data center platform counts the number of different fault phenomena with the same fault cause based on the information of fault phenomena and fault causes extracted from the preset database;

[0092] Specifically, the data center counts the number of other fault phenomena in the benchmark database that have the same cause as the current fault phenomenon according to the automobile sub-functional product system (i.e., the different functional systems or parts assemblies divided in the vehicle).

[0093] Establish a phenomenon correlation algorithm model to count the common fault causes between other fault phenomena and the current fault phenomenon;

[0094] Specifically, a phenomenon correlation algorithm model is established to count the number of common fault causes between other fault phenomena and the current fault phenomenon. Phenomenon correlation = (number of occurrences of the lower cause-phenomenon group) / (number of occurrences of the higher cause-phenomenon group)*100%.

[0095] According to the phenomenon correlation algorithm model, the correlation between other fault phenomena and the current fault phenomenon is calculated to generate a first correlation phenomenon.

[0096] Specifically, the correlation between other fault phenomena and the current fault phenomenon is calculated according to the phenomenon correlation algorithm model; when the number of common causes between the phenomenon and the associated phenomenon is n, the correlation algorithm model calculates n rounds, and the result of the nth round of calculation is the correlation between the two fault phenomena.

[0097] For example: A and B are fault phenomena; the fault causes of A are a, c, and e; the fault causes of B are a and c; the number of identical causes is 2;

[0098] When A occurs, the probability of B occurring is: 1. The frequency of A~a is 50, the frequency of A~c is 30, and the frequency of A~e is 40;

[0099] 2. The frequency of B~a is 20, and the frequency of B~c is 60;

[0100] 3. 20 / 50 = 40%, 30 / 60 = 50% (first round);

[0101] Then, the correlation between phenomenon A and phenomenon B = 40% / 50% = 80% (round 2).

[0102] Among them, the data center generates the second related phenomena based on the preset fault diagnosis and troubleshooting process, including:

[0103] The data center counts the common meanings and fault causes of each set of DTC codes contained in historically developed vehicle models.

[0104] Specifically, the data center counts the common meanings and fault causes of each set of DTC codes contained in historically developed vehicle models (i.e., frequency).

[0105] The phenomenon correlation algorithm model is used to calculate the correlation of DTC-type fault phenomena with the same cause and the same general meaning to generate the second correlation phenomenon.

[0106] Specifically, for DTC-type fault phenomena with the same cause and the same general meaning, the correlation degree is calculated by referring to the correlation algorithm model in the first part above (the data center generates the first correlation phenomenon based on the preset database inference), and the correlation degree of DTC-type fault phenomena in the same control module is generated to complete the correlation phenomenon reasoning of DTC-type fault phenomena in the fault phenomenon troubleshooting process. For example: when A occurs, the probability of B occurring (A and B represent the general meaning of DTC corresponding to different DTC-type fault phenomena, and a and c are the corresponding fault causes):

[0107] 1. The frequency of A~a is 10, and the frequency of A~c is 8;

[0108] 2. The frequency of B~a is 6, and the frequency of B~c is 7;

[0109] 3. Calculation of correlation: 6 / 10=60%, 7 / 8=87.5% (first round);

[0110] 4. The correlation between A and B is: 60% / 87.5%=68.57% (second round).

[0111] The data center performs association logic judgment based on the first association phenomenon and the second association phenomenon, and generates the association ranking of each association phenomenon, including:

[0112] The correlation degrees of the correlation phenomena in the first correlation phenomenon and the second correlation phenomenon are compared, and the correlation phenomena with high correlation degrees are retained.

[0113] Specifically, for the correlation phenomena that exist in the above two methods (generating the first correlation phenomenon and the second correlation phenomenon), the correlation degree is compared, and the one with the higher correlation degree is retained. For example: in the above two methods, A and B are both inferred as correlation phenomena. In the first method, the correlation degree between A and B is 70%; in the second method, the correlation degree between A and B is 80%. When the correlation logic is confirmed, the data of the inference of the correlation degree between A and B of 80% in the second method is retained as the confirmation basis.

[0114] The correlation phenomena that only exist in the first correlation phenomenon or the second correlation phenomenon are retained.

[0115] Specifically, for the associated phenomena that only exist in one of the above-mentioned methods of reasoning, they are all retained. For example: in the first method above, A and B are inferred as associated phenomena; in the second method above, A and C are inferred as associated phenomena. When determining the associated phenomena, the associated phenomena B and C inferred by the two methods need to be retained and the associated logic determination is performed with A respectively.

[0116] Generate a correlation ranking of each related phenomenon to assist maintenance technicians to sort each related phenomenon in order of correlation. For example, when reasoning about the related phenomenon of phenomenon A, B, C, and D are inferred through the first method mentioned above; through the second method mentioned above, B, D, and E are inferred, and they are sorted in descending order according to the size of their respective correlations. Among them, B and D are inferred in both methods; when sorting, the one with the higher correlation in the two methods is taken as the sorting basis.

[0117] Specifically, when the data center confirms the recommended related phenomena, for phenomena that have been technically determined and confirmed to have related logic, there is no need to perform the correlation calculation in the above two methods; for unconfirmed reasoning phenomena, the data center sets the correlation threshold screening conditions (the correlation is greater than or equal to 80%, and this threshold can be adjusted according to the actual calculation results), so as to recommend related phenomena on the user-side software for related phenomena that meet the correlation threshold conditions. The data center collects the recommended related phenomenon results checked by the maintenance technician in the user-side software, and technically determines that the correlation logic between the recommended related phenomena and the known phenomena is reasonable, thereby completing the confirmation of the correlation logic between each related phenomenon.

[0118] Among them, the reasoning generation method of automobile fault diagnosis related phenomena also includes: the data center outputs related phenomenon recommendations corresponding to the user-side request based on the user-side request.

[0119] Specifically, the user end may be a user PC, and the user sends a request to the data center through the software on the PC.

[0120] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the disclosure of the present invention can be performed in parallel, sequentially or in different orders, as long as the desired results of the technical solution disclosed in the present invention can be achieved, and this document does not limit this.

[0121] In summary, the auxiliary diagnosis method and device for automobile related faults of the present invention receives the VIN information input by the maintenance technician by the user-side software, guides the maintenance technician to gradually input the fault information, and the data middle platform recommends a combination of related phenomena corresponding to the known phenomena for the input fault information based on the fault information received by the user-side software, and recommends the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance methods according to each fault phenomenon, and guides the maintenance technician online to check the related phenomena that have a causal or associated relationship with the known fault phenomenon and the possible fault causes of each fault phenomenon in turn, thereby achieving the purpose of assisting the maintenance technician to complete fault diagnosis and maintenance, and improving work efficiency and accuracy.

[0122] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An auxiliary diagnosis method for automobile related faults, characterized in that: The method is applied to an auxiliary diagnosis system for automobile-related faults, the system comprising a user terminal and a data middle station connected in communication, and the auxiliary diagnosis method for automobile-related faults comprises: Step S100, the user terminal obtains fault information; Step S200, the user terminal sends the fault information to the data center; Step S300, the data center generates a correlation phenomenon combination corresponding to the known fault phenomenon according to the fault information; Step S400, the data center recommends a corresponding possible fault cause ranking and a diagnostic maintenance description of the corresponding fault cause according to each of the known fault phenomena; Step S500, the data center sends the associated phenomenon combination, the possible fault cause ranking and the diagnosis and maintenance instructions corresponding to the fault cause to the user terminal; Wherein, the step S300 includes: The data center extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomena based on the fault information, and generates and outputs a corresponding associated phenomenon combination; Wherein, the step S400 includes: The data center counts the occurrence frequency of the fault causes of each known fault phenomenon in the preset database, sorts them, and generates the possible fault cause sorting and diagnosis and maintenance instructions; The method for constructing the preset database is as follows: Based on the historical diagnosis database, the historical fault diagnosis data in the historical diagnosis database is classified and cleaned to generate data to be sampled; Through data processing tools, the sampled data is sampled and information is extracted to generate benchmark diagnostic data; submitting the baseline diagnostic data for storage in a baseline database; Among them, the data processing tools include sampling module, phenomenon processing module and cause processing module; Wherein, sampling and information extraction are performed on the data to be sampled by the data processing tool to generate the reference diagnostic data, including: presetting a DTC-type diagnostic data identification rule in the sampling module; Presetting a sample sampling rule in the sampling module, performing sample sampling on the data to be sampled, and generating sample sampling data; Fault diagnosis information in the DTC type and non-DTC type data in the sample data is extracted to generate the reference diagnosis data.

2. The auxiliary diagnosis method for automobile related faults according to claim 1, characterized in that: The step S100 includes: The user terminal obtains VIN information and fault phenomenon information input by the user.

3. The auxiliary diagnosis method for automobile related faults as claimed in claim 2, characterized in that: The fault phenomenon information includes: DTC-related fault phenomena and non-DTC-related fault phenomena.

4. An auxiliary diagnosis device for automobile related faults, characterized in that: The device is applied to an auxiliary diagnosis system for automobile-related faults, the system comprising a user terminal and a data middle station connected in communication, and the auxiliary diagnosis device for automobile-related faults comprises: An acquisition module, used for the user end to acquire fault information; A first sending module, used for the user end to send the fault information to the data center; A generation module, used by the data center to generate a combination of associated phenomena corresponding to a known fault phenomenon according to the fault information; A recommendation module, used for the data center to recommend the corresponding possible fault cause ranking and the corresponding diagnosis and maintenance instructions of the fault cause according to each known fault phenomenon; A second sending module is used for the data center to send the combination of related phenomena, the possible fault cause ranking and the diagnosis and maintenance instructions corresponding to the fault cause to the user end; The data center generates, based on the fault information, a combination of associated phenomena corresponding to known fault phenomena, including: The data center extracts phenomena in a preset database that have the same fault cause association frequency as the known fault phenomena based on the fault information, and generates and outputs a corresponding associated phenomenon combination; Among them, the data center recommends the corresponding possible fault cause ranking and the corresponding fault cause diagnosis and maintenance instructions according to each known fault phenomenon, including: The data center counts the occurrence frequency of the fault causes of each known fault phenomenon in the preset database, sorts them, and generates the possible fault cause sorting and diagnosis and maintenance instructions; The method for constructing the preset database is as follows: Based on the historical diagnosis database, the historical fault diagnosis data in the historical diagnosis database is classified and cleaned to generate data to be sampled; Through data processing tools, the sampled data is sampled and information is extracted to generate benchmark diagnostic data; submitting the baseline diagnostic data for storage in a baseline database; Among them, the data processing tools include sampling module, phenomenon processing module and cause processing module; Wherein, sampling and information extraction are performed on the data to be sampled by the data processing tool to generate the reference diagnostic data, including: presetting a DTC-type diagnostic data identification rule in the sampling module; Presetting a sample sampling rule in the sampling module, performing sample sampling on the data to be sampled, and generating sample sampling data; Fault diagnosis information in the DTC type and non-DTC type data in the sample data is extracted to generate the reference diagnosis data.

5. The auxiliary diagnosis device for automobile-related faults as claimed in claim 4, characterized in that: The user end obtaining fault information includes: The user terminal obtains the VIN information and fault phenomenon information input by the user through the acquisition module.

6. The auxiliary diagnosis device for automobile-related faults as claimed in claim 5, characterized in that: The fault phenomenon information includes: DTC-related fault phenomena and non-DTC-related fault phenomena.