Fault code evaluation method and device, computer equipment and storage medium

Abstract

The invention relates to a fault code evaluation method and device, computer equipment and a storage medium. Obtaining an after-sales data set, a preset fault code set and a preset failure mode set corresponding to a target component in the target vehicle; determining each actual fault type according to each actual fault phenomenon in the after-sales data set and the corresponding actual fault code; determining at least one target fault type matched with each actual fault type in each candidate fault type; determining at least one target fault code matched with each actual fault code in each candidate fault code; and according to the target fault type and the target fault code, determining whether a redundant or missing fault code exists in a preset fault code set. According to the scheme, whether redundant or missing fault codes exist in the preset fault code set or not is evaluated according to the after-sales data set, the preset fault code set and the preset failure mode set, a more reliable basis is provided for fault positioning and fault reason troubleshooting, and then the efficiency of fault positioning and fault reason troubleshooting is improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicles, and particularly to a method and device for evaluating fault codes, a computer device, and a storage medium. Background Art

[0002] With the development of the automotive industry towards electrification, intelligence, and networking, the functions of vehicles are becoming more diverse, and the faults that occur in vehicles are becoming more complex. In order to enable after-sales maintenance personnel to quickly locate faults and troubleshoot the causes of faults when a vehicle fails, corresponding diagnostic trouble codes (DTCs) are usually defined for each controller in the vehicle during the development stage.

[0003] However, the design of DTCs mainly depends on suppliers, and it is difficult for after-sales maintenance personnel to evaluate the reliability of DTCs set by suppliers, which is not conducive to quickly locating faults and troubleshooting the causes of faults. Therefore, how to evaluate the reliability of DTCs set by suppliers has become a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide a method and device for evaluating fault codes, a computer device, and a storage medium, which can evaluate the reliability of DTCs set by suppliers, so as to improve the efficiency of locating faults and troubleshooting the causes of faults.

[0005] In a first aspect, the present application provides a method for evaluating fault codes, the method comprising:

[0006] Obtain an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0007] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0008] Determine at least one target fault type in each candidate fault type that matches each actual fault type;

[0009] Determine at least one target fault code in each candidate fault code that matches each actual fault code;

[0010] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0011] In one embodiment, determining at least one target fault type that matches each actual fault type among the candidate fault types includes:

[0012] For each actual fault type, if there is text in the text corresponding to the candidate fault types whose similarity to the text of the actual fault type is greater than the similarity threshold, then the candidate fault type corresponding to the text with a similarity greater than the similarity threshold is used as the target fault type that matches the actual fault type.

[0013] In one embodiment, determining at least one target fault code that matches each actual fault code among the candidate fault codes includes:

[0014] For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, then the candidate fault code is used as the target fault code that matches the actual fault code.

[0015] In one embodiment, determining whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code includes:

[0016] For each target fault type, if there is no target fault code in at least one target fault code that matches the target fault type, it is determined that there is a missing fault code in the preset fault code set.

[0017] In one embodiment, determining whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code includes:

[0018] For each target fault code, if there is no target fault type in at least one target fault type that matches the target fault code, it is determined that there is a redundant fault code in the preset fault code set.

[0019] In one embodiment, determining each actual fault type according to each actual fault phenomenon and the corresponding actual fault code includes:

[0020] For each actual fault phenomenon and the corresponding actual fault code, a target combination including the actual fault phenomenon and the corresponding actual fault code is screened out from the candidate fault combination set, and the fault type included in the target combination is used as the actual fault type that matches the actual fault phenomenon and the corresponding actual fault code.

[0021] In a second aspect, the present application further provides a fault diagnosis and evaluation device, and the device includes:

[0022] An acquisition module, configured to acquire an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the corresponding actual fault code; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0023] A first determination module, configured to determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0024] A second determination module, configured to determine at least one target fault type that matches each actual fault type among each candidate fault type;

[0025] A third determination module, configured to determine at least one target fault code that matches each actual fault code among each candidate fault code;

[0026] A fourth determination module, configured to determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0027] In a third aspect, the present application further provides a computer device, the computer device includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0028] Acquire an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the corresponding actual fault code; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0029] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0030] Determine at least one target fault type that matches each actual fault type among each candidate fault type;

[0031] Determine at least one target fault code that matches each actual fault code among each candidate fault code;

[0032] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0033] In a fourth aspect, the present application further provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0034] Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target component in the target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the corresponding actual fault code; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0035] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0036] Determine at least one target fault type in each candidate fault type that matches each actual fault type;

[0037] Determine at least one target fault code in each candidate fault code that matches each actual fault code;

[0038] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0039] In a fifth aspect, the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the following steps are implemented:

[0040] Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target component in the target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the corresponding actual fault code; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0041] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0042] Determine at least one target fault type in each candidate fault type that matches each actual fault type;

[0043] Determine at least one target fault code in each candidate fault code that matches each actual fault code;

[0044] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0045] The above-mentioned fault code evaluation method, device, computer device and storage medium obtain an after-sales data set, a preset fault code set and a preset failure mode set corresponding to a target component in a target vehicle; and determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code in the after-sales data set; furthermore, determine at least one target fault type in each candidate fault type that matches each actual fault type; and determine at least one target fault code in each candidate fault code that matches each actual fault code; and determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code. In the above solution, by obtaining the after-sales data set, the preset fault code set and the preset failure mode set corresponding to the target component in the target vehicle, and then evaluating whether there are redundant or missing fault codes in the preset fault code set according to the after-sales data set, the preset fault code set and the preset failure mode set, a more reliable basis is provided for fault location and troubleshooting of the cause of the fault, thereby improving the efficiency of fault location and troubleshooting of the cause of the fault. Brief Description of the Drawings

[0046] Figure 1 It is a schematic flowchart of the fault code evaluation method in an embodiment;

[0047] Figure 2 It is a schematic flowchart of the process of evaluating the preset fault code set of a storage battery in an embodiment;

[0048] Figure 3 It is a structural block diagram of the fault code evaluation device in an embodiment;

[0049] Figure 4 It is an internal structure diagram of a computer device in an embodiment. Detailed Embodiment

[0050] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] The fault code evaluation method provided in the embodiment of the present application can be applied to an application scenario for fault analysis of a vehicle. The method provided in the embodiment of the present application can be executed by a server or by a terminal with a certain computing power. Among them, the server can be implemented by an independent server or a server cluster composed of multiple servers. The terminal can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc.

[0052] In one embodiment, asFigure 1 As shown, a fault code evaluation method is provided. Taking the application of this method to a server as an example, it includes the following steps:

[0053] S101, obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target component in the target vehicle.

[0054] Exemplarily, the target vehicle can be a specific model of vehicle, and the target component can be any component in the target vehicle. The after-sales data set corresponding to the target component in the target vehicle can be a list containing fault information, repair records, and other data feedback by customers after the target vehicle is sold. The preset fault code set can be a fault diagnosis design list for each controller corresponding to the target vehicle, which details all DTCs designed in each controller of the target vehicle and their corresponding fault descriptions. This is an important reference for evaluating whether the preset fault code set is reasonable. The preset failure mode set can be a Design Failure Mode and Effects Analysis (DFMEA) document. The DFMEA document is a systematic analysis of possible failure modes and their impacts in a product or system. It provides a basis for identifying potential design problems. In the embodiments of the present application, the DFMEA document includes all candidate fault types that may occur in component Pj, that is, potential failure modes.

[0055] Among them, the after-sales data set includes at least each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type. The preset fault code set specifically includes candidate fault code Pj_Tm, that is, the candidate fault code designed for target component Pj in the controller of the target vehicle; and fault description Pj_Mz, the detailed fault description corresponding to candidate fault code Pj_Tm. The preset failure mode set specifically includes candidate fault type (potential failure mode) Pj_My, that is, all potential failure modes that may occur in target component Pj.

[0056] S102, determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code.

[0057] Exemplarily, according to the correspondence between each actual fault phenomenon and the corresponding actual fault code and the actual fault type, each actual fault type that matches each actual fault phenomenon and the corresponding actual fault code can be determined.

[0058] It can be understood that according to the after-sales data set, the abnormal functions Fi existing in the target vehicle can be determined, that is, the specific abnormal functions or problems occurring in the target vehicle; the actual fault phenomena Fi_Sn, that is, the specific manifestations or symptoms of the abnormal functions; the target components Pj, that is, the specific components causing the faults; the actual fault types Pj_Mx, that is, the failure types or causes of the target components; the actual fault codes Pj_Tr, that is, the fault codes recorded during after-sales maintenance, which are used to quickly locate problems.

[0059] S103. Determine at least one target fault type that matches each actual fault type among the candidate fault types.

[0060] Exemplarily, at least one target fault type that matches each actual fault type among the candidate fault types can be determined according to the fault descriptions corresponding to the fault types.

[0061] S104. Determine at least one target fault code that matches each actual fault code among the candidate fault codes.

[0062] Exemplarily, at least one target fault code that matches each actual fault code among the candidate fault codes can be determined by comparing the candidate fault codes with the actual fault codes.

[0063] S105. Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault types and the target fault codes.

[0064] Exemplarily, whether there are redundant or missing fault codes in the preset fault code set can be determined according to the matching results between the target fault diagnosis types and the target fault codes.

[0065] For the above fault code evaluation method, obtain the after-sales data set, the preset fault code set and the preset failure mode set corresponding to the target components in the target vehicle; and determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code in the after-sales data set; further determine at least one target fault type that matches each actual fault type among the candidate fault types; and determine at least one target fault code that matches each actual fault code among the candidate fault codes; and determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault types and the target fault codes. For the above solution, by obtaining the after-sales data set, the preset fault code set and the preset failure mode set corresponding to the target components in the target vehicle, and then evaluating whether there are redundant or missing fault codes in the preset fault code set according to the after-sales data set, the preset fault code set and the preset failure mode set, it provides a more reliable basis for locating faults and troubleshooting the causes of faults, and further improves the efficiency of locating faults and troubleshooting the causes of faults.

[0066] In some alternative implementation manners, determining at least one target fault type that matches each actual fault type among candidate fault types can be achieved through the following manner:

[0067] For each actual fault type, if there is text in the text corresponding to each candidate fault type whose similarity to the text of the actual fault type is greater than the similarity threshold, then the candidate fault type corresponding to the text with a similarity greater than the similarity threshold is used as the target fault type that matches the actual fault type.

[0068] Exemplarily, the similarity threshold can be set according to the actual situation. For example, it can be set to 80%. If there is text in the text corresponding to each candidate fault type whose similarity to the text of any actual fault type is greater than 80%, then the candidate fault type corresponding to the text with a similarity greater than 80% is used as the target fault type that matches the actual fault type.

[0069] In the embodiments of the present application, an implementable manner for determining the target fault type is provided, which is convenient for further determining whether there are redundant or missing fault codes in the preset fault code set.

[0070] In some alternative implementation manners, determining at least one target fault code that matches each actual fault code among candidate fault codes can be specifically achieved through the following manner:

[0071] For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, then the candidate fault code is used as the target fault code that matches the actual fault code. For example, for each actual fault code, it can be determined whether there is a candidate fault code in the candidate fault codes that is the same as the actual fault code. If so, the candidate fault code that is the same as the actual fault code is used as the target fault code that matches the actual fault code.

[0072] In the embodiments of the present application, an implementable manner for determining the target fault code is provided, which is convenient for further determining whether there are redundant or missing fault codes in the preset fault code set.

[0073] In some alternative implementation manners, determining whether there are missing fault codes in the preset fault code set according to the target fault type and the target fault code can be specifically achieved through the following manner:

[0074] For each target fault type, if there is no target fault code that matches the target fault type among at least one target fault code, it is determined that there are missing fault codes in the preset fault code set.

[0075] It can be understood that the target fault type is the fault type among the candidate fault types that matches each actual fault type, that is, the target fault type is the fault type that has appeared in the after-sales dataset of the target vehicle; and the target fault code is the fault code among the candidate fault codes that matches each actual fault code, that is, the target fault code is the fault code that has appeared in the after-sales dataset of the target vehicle.

[0076] If there is no target fault code that matches the target fault type, it can be determined that there is a missing fault code in the preset fault code set, that is, a fault code that matches the target fault type is missing.

[0077] In the embodiments of the present application, a method is provided to screen whether there is a fault code that matches each target fault type among the target fault codes, and then determine whether there is a missing fault code in the preset fault code set, thereby providing a basis for updating the preset fault code set, and further providing a more reliable basis for fault location and troubleshooting of fault causes, and further improving the efficiency of fault location and troubleshooting of fault causes.

[0078] In some alternative implementation manners, according to the target fault type and the target fault code, it is determined whether there is a redundant fault code in the preset fault code set, which can be specifically implemented by the following method:

[0079] For each target fault code, if there is no target fault type that matches the target fault code in at least one target fault type, it is determined that there is a redundant fault code in the preset fault code set.

[0080] Similarly, the target fault type is the fault type among the candidate fault types that matches each actual fault type, that is, the target fault type is the fault type that has appeared in the after-sales dataset of the target vehicle; and the target fault code is the fault code among the candidate fault codes that matches each actual fault code, that is, the target fault code is the fault code that has appeared in the after-sales dataset of the target vehicle.

[0081] If there is no target fault type that matches the target fault code, it can be determined that there is a redundant fault code in the preset fault code set, that is, the target fault code that does not match any of the target fault types is redundant.

[0082] In the embodiments of the present application, a method is provided to screen whether there is a fault type that matches each target fault code among the target fault types, and then determine whether there is a redundant fault code in the preset fault code set, thereby providing a basis for updating the preset fault code set, and further providing a more reliable basis for fault location and troubleshooting of fault causes, and further improving the efficiency of fault location and troubleshooting of fault causes.

[0083] In some alternative implementations, according to each actual fault phenomenon and the corresponding actual fault code, each actual fault type is determined, which can be specifically implemented through the following methods:

[0084] Exemplarily, a candidate fault combination set can be established in advance. Each candidate combination in the candidate combination set includes a fault phenomenon, a fault code, and a fault type. Based on this, when determining the actual fault type that matches each actual fault phenomenon and the corresponding actual fault code, for each actual fault phenomenon and the actual fault code corresponding to this actual fault phenomenon, a target combination including the actual fault phenomenon and the actual fault code corresponding to this actual fault phenomenon is screened out from the candidate fault combination set, and the fault type included in the target combination is used as the actual fault type that matches the actual fault phenomenon and the corresponding actual fault code.

[0085] In the embodiments of the present application, an implementable method for determining the actual fault type that matches the actual fault phenomenon and the corresponding actual fault code is provided, which is convenient for further determining the target fault type.

[0086] In some alternative implementations, taking the target component as the battery as an example, the embodiments of the present application introduce in detail how to evaluate whether there are redundant or missing fault codes in the preset fault code set corresponding to the battery.

[0087] See Figure 2 , Figure 2 A schematic flow chart of a process for evaluating the preset fault code set of a battery is provided, which specifically includes the following steps:

[0088] S201, Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the battery in the target vehicle.

[0089] S202, For each actual fault phenomenon and the corresponding actual fault code, screen out a target combination including the actual fault phenomenon and the corresponding actual fault code from the candidate fault combination set, and use the fault type included in the target combination as the actual fault type that matches the actual fault phenomenon and the corresponding actual fault code.

[0090] S203, For each actual fault type, if there is a text in the texts corresponding to the candidate fault types whose similarity to the text of the actual fault type is greater than the similarity threshold, then use the candidate fault type corresponding to the text with a similarity greater than the similarity threshold as the target fault type that matches the actual fault type.

[0091] S204, For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, then use the candidate fault code as the target fault code that matches the actual fault code.

[0092] Exemplarily, referring to Table 1, Table 1 provides a relationship matrix. This relationship matrix can be based on the component battery Pj, and establish the relationship matrix between Pj_My (candidate failure type) in the preset failure mode set of the battery, Fi_Sn (actual failure phenomenon), and Pj_Tm (candidate fault code).

[0093] The position where the candidate failure type Pj_My and the actual failure phenomenon Fi_Sn intersect in the relationship matrix represents the failure correlation, denoted as MSyn; the position where the candidate failure type Pj_My and the candidate fault code Pj_Tm intersect in the relationship matrix also represents the failure correlation, denoted as MTym.

[0094] Table 1:

[0095]

[0096] Assume that the actual failure phenomenon Fi_Sn includes F1_S1, F1_S2, and F1_S3; the candidate fault codes Pj_Tm are P1_T1, P1_T2, and P1_T3; and the candidate failure types Pj_My are P1_M1, P1_M2, P1_M3, P1_M4, and P1_M5.

[0097] First, use the text similarity algorithm to judge the content similarity between the actual failure type Pj_Mx and each candidate failure type Pj_My. If the similarity is greater than or equal to 80%, then it is considered that Pj_Mx = Pj_My, and let MSyn = 1; otherwise, it is considered that Pj_Mx ≠ Pj_My, and let MSyn = 0. It should be noted that the candidate failure type corresponding to MSyn = 1 is used as the target failure type.

[0098] Furthermore, perform a fault code comparison. If the actual fault code Pj_Tr = the candidate fault code Pj_Tm, then let MTym = 1; otherwise, let MTym = 0. It should be noted that the candidate fault code corresponding to MTym = 1 is used as the target fault code.

[0099] S205. For each target failure type, if there is no target fault code in at least one target fault code that matches the target failure type, it is determined that there is a missing fault code in the preset fault code set.

[0100] S206. For each target fault code, if there is no target failure type in at least one target failure type that matches the target fault code, it is determined that there is a redundant fault code in the preset fault code set.

[0101] It should be noted that if there is a newly added after-sales data set, the actual failure phenomenon Fi_Sn in Table 1 can be updated based on the newly added after-sales data set, and the values of MSyn and MTym can be updated.

[0102] Further, first, an assessment can be made on whether the fault codes in the preset fault code set are redundant. The specific assessment method is as follows:

[0103] Let the total failure correlation of the m-th fault code of the battery Pj be Kj, and let , where a is the number of the a-th candidate fault type, and i is the maximum value of the candidate fault type numbers; if Kj = 0, it means that there are redundant fault codes in the preset fault code set of the component Pj, and it is necessary to focus on evaluating whether this fault code needs to be retained.

[0104] Furthermore, an assessment can be made on whether the fault codes in the preset fault code set are missing. The specific assessment method is as follows:

[0105] For the b-th target fault type, let the number of candidate fault codes corresponding to the b-th target fault type of the battery Pj be Mj, , where m is the number of the m-th candidate fault code, and z is the maximum value of the candidate fault code numbers. If Mj = 0, it means that there is no corresponding fault code designed for the b-th target fault type of the battery Pj, and it is necessary to focus on evaluating whether it is necessary to add the corresponding fault code.

[0106] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are displayed in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of the steps or stages in other steps or other steps.

[0107] Based on the same inventive concept, the embodiments of the present application also provide a fault code evaluation device for implementing the above-mentioned fault code evaluation method. The implementation solutions provided by this device to solve problems are similar to the implementation solutions described in the above method. Therefore, the specific limitations in one or more embodiments of the following fault code evaluation device can refer to the limitations on the fault code evaluation method in the above text, and will not be repeated here.

[0108] In one embodiment, as Figure 3 shown, a fault code evaluation device is provided, including:

[0109] An acquisition module 10 is configured to acquire an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0110] A first determination module 20 is configured to determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0111] A second determination module 30 is configured to determine at least one target fault type that matches each actual fault type among each candidate fault type;

[0112] A third determination module 40 is configured to determine at least one target fault code that matches each actual fault code among each candidate fault code;

[0113] A fourth determination module 50 is configured to determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0114] The above-mentioned fault code evaluation device acquires an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; and determines each actual fault type according to each actual fault phenomenon and the corresponding actual fault code in the after-sales data set; further determines at least one target fault type that matches each actual fault type among each candidate fault type; and determines at least one target fault code that matches each actual fault code among each candidate fault code; and determines whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code. The above solution evaluates whether there are redundant or missing fault codes in the preset fault code set by acquiring the after-sales data set, the preset fault code set, and the preset failure mode set corresponding to the target component in the target vehicle, and then provides a more reliable basis for fault location and troubleshooting of the cause of the fault, thereby improving the efficiency of fault location and troubleshooting of the cause of the fault.

[0115] In one embodiment, the second determination module 30 is specifically configured to:

[0116] For each actual fault type, if there is a text in the texts corresponding to each candidate fault type whose similarity to the text of the actual fault type is greater than the similarity threshold, then the candidate fault type corresponding to the text with a similarity greater than the similarity threshold is used as the target fault type that matches the actual fault type.

[0117] In one embodiment, the third determination module 40 is specifically configured to:

[0118] For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, the candidate fault code is used as the target fault code that matches the actual fault code.

[0119] In one embodiment, the fourth determination module 50 is specifically configured to:

[0120] For each target fault type, if there is no target fault code in at least one target fault code that matches the target fault type, it is determined that there is a missing fault code in the preset fault code set.

[0121] In one embodiment, the fourth determination module 50 is specifically configured to:

[0122] For each target fault code, if there is no target fault type in at least one target fault type that matches the target fault code, it is determined that there is a redundant fault code in the preset fault code set.

[0123] In one embodiment, the first determination module 20 is specifically configured to:

[0124] For each actual fault phenomenon and the corresponding actual fault code, in the candidate fault combination set, a target combination that includes the actual fault phenomenon and the corresponding actual fault code is screened out, and the fault type included in the target combination is used as the actual fault type that matches the actual fault phenomenon and the corresponding actual fault code.

[0125] Each module in the above fault diagnosis and evaluation device can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each of the above modules.

[0126] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 4 shown. The computer device includes a processor, a memory, and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store after-sales data sets, preset fault code sets, and preset failure mode sets. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements a fault code evaluation method.

[0127] Those skilled in the art can understand,Figure 4 The structure shown is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0128] In one embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, the following steps are implemented:

[0129] Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target component in the target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0130] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0131] Determine at least one target fault type in each candidate fault type that matches each actual fault type;

[0132] Determine at least one target fault code in each candidate fault code that matches each actual fault code;

[0133] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0134] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0135] For each actual fault type, if there is a text in the texts corresponding to each candidate fault type whose similarity to the text of the actual fault type is greater than the similarity threshold, then use the candidate fault type corresponding to the text with a similarity greater than the similarity threshold as the target fault type that matches the actual fault type.

[0136] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0137] For each actual fault code, if there is a candidate fault code in each candidate fault code that is the same as the actual fault code, then use the candidate fault code as the target fault code that matches the actual fault code.

[0138] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0139] For each target fault type, if there is no target fault code matching the target fault type in at least one target fault code, it is determined that there is a missing fault code in the preset fault code set.

[0140] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0141] For each target fault code, if there is no target fault type matching the target fault code in at least one target fault type, it is determined that there is a redundant fault code in the preset fault code set.

[0142] In one embodiment, when the processor executes the computer program, the following steps are further implemented:

[0143] For each actual fault phenomenon and the corresponding actual fault code, screen out the target combinations containing the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon from the candidate fault combination set, and use the fault types included in the target combinations as the actual fault types matching the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon.

[0144] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0145] Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target components in the target vehicle; wherein, the after-sales data set includes at least each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0146] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0147] Determine at least one target fault type matching each actual fault type among each candidate fault type;

[0148] Determine at least one target fault code matching each actual fault code among each candidate fault code;

[0149] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0150] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented:

[0151] For each actual fault type, if there is text in the texts corresponding to the candidate fault types whose similarity to the text of the actual fault type is greater than the similarity threshold, then the candidate fault type corresponding to the text with a similarity greater than the similarity threshold is used as the target fault type that matches the actual fault type.

[0152] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0153] For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, then the candidate fault code is used as the target fault code that matches the actual fault code.

[0154] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0155] For each target fault type, if there is no target fault code in at least one target fault code that matches the target fault type, then it is determined that there is a missing fault code in the preset fault code set.

[0156] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0157] For each target fault code, if there is no target fault type in at least one target fault type that matches the target fault code, then it is determined that there is a redundant fault code in the preset fault code set.

[0158] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0159] For each actual fault phenomenon and the corresponding actual fault code, filter out the target combinations in the candidate fault combination set that include the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon, and use the fault types included in the target combinations as the actual fault types that match the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon.

[0160] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0161] Obtain the after-sales data set, preset fault code set, and preset failure mode set corresponding to the target component in the target vehicle; wherein, the after-sales data set at least includes each actual fault phenomenon and the actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; the preset failure mode set includes each candidate fault type;

[0162] Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code;

[0163] Determine at least one target fault type that matches each actual fault type among the candidate fault types;

[0164] Determine at least one target fault code that matches each actual fault code among the candidate fault codes;

[0165] Determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

[0166] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0167] For each actual fault type, if there is text in the texts corresponding to the candidate fault types whose similarity to the text of the actual fault type is greater than the similarity threshold, then use the candidate fault type corresponding to the text with a similarity greater than the similarity threshold as the target fault type that matches the actual fault type.

[0168] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0169] For each actual fault code, if there is a candidate fault code in the candidate fault codes that is the same as the actual fault code, then use the candidate fault code as the target fault code that matches the actual fault code.

[0170] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0171] For each target fault type, if there is no target fault code in at least one target fault code that matches the target fault type, then determine that there is a missing fault code in the preset fault code set.

[0172] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0173] For each target fault code, if there is no target fault type in at least one target fault type that matches the target fault code, then determine that there is a redundant fault code in the preset fault code set.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0175] For each actual fault phenomenon and the corresponding actual fault code, screen out the target combination that includes the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon from the candidate fault combination set, and use the fault type included in the target combination as the actual fault type that matches the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon.

[0176] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0177] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memory can include Read-Only Memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0178] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered to be within the scope described in this specification.

[0179] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A fault code evaluation method, characterized in that: The method comprises: Acquire an after-sales data set, a preset fault code set, and a preset failure mode set corresponding to a target component in a target vehicle; wherein the after-sales data set at least includes each actual fault phenomenon and an actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; and the preset failure mode set includes each candidate fault type; Determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code; Determine at least one target fault type among each candidate fault type that matches each actual fault type; Determining at least one target fault code among the candidate fault codes that matches each actual fault code; According to the target fault type and the target fault code, it is determined whether the preset fault code set has redundant or missing fault codes.

2. The method according to claim 1, characterized in that The determining of at least one target fault type among the candidate fault types that matches the actual fault types includes: For each actual fault type, if there is text in the text corresponding to each candidate fault type whose similarity with the text of the actual fault type is greater than a similarity threshold, the candidate fault type corresponding to the text with similarity greater than the similarity threshold is used as the target fault type that matches the actual fault type.

3. The method according to claim 1, characterized in that The determining of at least one target fault code among the candidate fault codes that matches the actual fault codes includes: For each actual fault code, if there is a candidate fault code that is the same as the actual fault code among the candidate fault codes, the candidate fault code is used as the target fault code that matches the actual fault code.

4. The method according to claim 1, characterized in that: The determining, according to the target fault type and the target fault code, whether the preset fault code set has redundant or missing fault codes includes: For each target fault type, if there is no target fault code matching the target fault type in at least one target fault code, it is determined that there is a missing fault code in the preset fault code set.

5. The method according to claim 1, characterized in that The determining, according to the target fault type and the target fault code, whether the preset fault code set has redundant or missing fault codes includes: For each target fault code, if there is no target fault type matching the target fault code in at least one target fault type, it is determined that there is a redundant fault code in the preset fault code set.

6. The method according to claim 1, characterized in that Determining each actual fault type according to each actual fault phenomenon and the corresponding actual fault code includes: For each actual fault phenomenon and the corresponding actual fault code, a target combination including the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon is screened out from the candidate fault combination set, and the fault type contained in the target combination is used as the actual fault type that matches the actual fault phenomenon and the actual fault code corresponding to the actual fault phenomenon.

7. A fault diagnosis and evaluation device, characterized in that: The device comprises: An acquisition module is used to acquire an after-sales data set, a preset fault code set and a preset failure mode set corresponding to a target component in a target vehicle; wherein the after-sales data set at least includes each actual fault phenomenon and an actual fault code corresponding to each actual fault phenomenon; the preset fault code set includes each candidate fault code; and the preset failure mode set includes each candidate fault type; A first determination module, used to determine each actual fault type according to each actual fault phenomenon and the corresponding actual fault code; A second determination module is used to determine at least one target fault type that matches each actual fault type among each candidate fault type; A third determination module is used to determine at least one target fault code among the candidate fault codes that matches each actual fault code; The fourth determination module is used to determine whether there are redundant or missing fault codes in the preset fault code set according to the target fault type and the target fault code.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images