Vehicle fault data management method, system, equipment and medium
By extracting and dividing fault feature codes and pushing the fault main code features to the fault detection system, the problems of inefficient and insufficient accuracy of traditional fault code management methods are solved, and efficient and accurate vehicle fault diagnosis is achieved.
Patent Information
- Application Number
- CN202411507168.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-28
- Publication Date
- 2025-03-21
AI Technical Summary
Traditional fault code management methods rely on manual identification and processing, are inefficient and prone to errors. Especially when facing a large amount of fault data, how to quickly and accurately locate the fault type has become an urgent problem to be solved.
By obtaining the fault code set, extracting the fault characteristic code of the fault code, dividing the fault characteristic code group, obtaining the target fault characteristic code group, and pushing the fault main code characteristic set to the fault detection system according to the preset ratio.
It significantly improves the efficiency and accuracy of vehicle fault diagnosis, and provides strong technical support through systematic processing processes, accurate fault positioning, dynamically adjusted detection range and automated data push.
Smart Images
Figure CN119672827A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of vehicle fault data management methods, and in particular to a vehicle fault data management method, system, device and medium. Background Art
[0002] During the long-term use of vehicles, various faults may occur due to the wear, aging, overload, damage and other reasons of parts, as well as improper operation of the driver or unreasonable transportation environment and behavior. These faults will reduce the performance and reliability of the vehicle, increase maintenance costs, and even pose potential risks to passengers, drivers and other traffic participants.
[0003] Fault codes, or fault codes, represent the meaning of a fault or abnormality that occurs during the operation of a vehicle. They are a set of standard code systems created by manufacturers to record and explain fault conditions of a vehicle or its related systems. These codes are usually binary coded and usually consist of two English letters or numbers. The significance of fault codes is that they provide a common language for maintenance personnel, OEMs and maintenance diagnostic equipment, allowing fault information to be communicated between different manufacturers, models and systems.
[0004] In the field of vehicle fault diagnosis, as automotive electronic systems become increasingly complex, the number and types of fault codes have also increased dramatically. Traditional fault code management methods often rely on manual identification and processing, which is not only inefficient but also prone to errors. Especially when faced with a large amount of fault data, how to quickly and accurately locate the fault type has become an urgent problem to be solved. Summary of the invention
[0005] The main purpose of this application is to provide a vehicle fault data management method, system, device and medium, aiming to solve the technical problem of how to quickly and accurately locate the fault type when facing a large amount of fault data, as the traditional fault code management method often relies on manual identification and processing, which is not only inefficient but also prone to errors.
[0006] To achieve the above objectives, in a first aspect, the present application provides a vehicle fault data management method, comprising the following steps:
[0007] Acquire a fault code set, extract fault feature codes of all fault codes in the fault code set, and form a fault feature code set;
[0008] According to the fault type corresponding to the fault feature code, the fault feature code set is divided into a plurality of fault feature code groups, and a target fault feature code group with the largest number of fault feature codes is obtained;
[0009] Obtaining a first ratio according to a ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set;
[0010] If the first ratio is smaller than the preset ratio;
[0011] then, according to the fault type corresponding to the fault feature code group, obtaining at least one secondary fault feature code group associated with the target fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set;
[0012] Obtaining a second ratio according to a ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set;
[0013] When the second ratio is greater than the preset ratio, the fault main code feature set is pushed to a fault detection system.
[0014] Optionally, the step of acquiring a fault code set, extracting fault feature codes of all fault codes in the fault code set, and forming a fault feature code set includes:
[0015] Obtain all fault codes within a preset time period and form a fault code set;
[0016] The fault code set is traversed, and for each fault code, its corresponding fault feature code is parsed according to a predetermined parsing rule, and all the fault feature codes are combined into a fault feature code set.
[0017] Optionally, the step of dividing the fault feature code set into a plurality of fault feature code groups according to the fault types corresponding to the fault feature codes, and obtaining a target fault feature code group having the largest number of fault feature codes includes:
[0018] Traversing the fault feature code set, and dividing the fault feature codes with the same fault type into the same fault feature code group according to the fault types corresponding to the fault feature codes;
[0019] sorting all the fault feature code groups according to the number of fault feature codes in the fault feature code group;
[0020] The fault feature code group with the largest number of marked fault feature codes is the target fault feature code group.
[0021] Optionally, the step of obtaining the first ratio according to the ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set further includes:
[0022] Verifying the relationship between the first ratio and a preset ratio;
[0023] If the first ratio is greater than or equal to the preset ratio, the target feature code group is pushed to the fault detection system.
[0024] Optionally, if the first ratio is greater than or equal to the preset ratio, the step of pushing the target feature code group to the fault detection system further includes:
[0025] According to the target feature code group, extracting vehicle status history data of the same vehicle model, the same fault type, and the same fault level;
[0026] Predict the vehicle state of the target vehicle.
[0027] Optionally, the step of acquiring at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group form a fault main code feature set, comprises:
[0028] Obtaining the fault type and fault location corresponding to the target fault feature code group, and the fault types and fault locations of all remaining fault feature code groups except the target fault feature code group;
[0029] Comparing the fault types and fault locations of all remaining fault feature code groups with the fault types and fault locations corresponding to the target fault feature code group, to obtain the correlation between all remaining fault feature code groups and the target fault feature code group;
[0030] According to the correlation, all remaining fault feature code groups are sorted from high to low according to the correlation to obtain a first sorting result.
[0031] Optionally, the step of obtaining a second ratio according to the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set comprises:
[0032] Adding the target fault feature code group to the fault main code feature set;
[0033] According to the first sorting result, the remaining fault feature code groups are sequentially added to the fault main code feature set until the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set is greater than a preset ratio.
[0034] In a second aspect, the present application provides a vehicle fault data management system, comprising:
[0035] A fault code acquisition module is configured to acquire a fault code set, extract fault feature codes of all fault codes in the fault code set, and form a fault feature code set;
[0036] a fault code processing module, configured to divide the fault feature code set into a plurality of fault feature code groups according to the fault type corresponding to the fault feature code, and obtain a target fault feature code group with the largest number of fault feature codes;
[0037] A first ratio acquisition module, configured to obtain a first ratio according to a ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set;
[0038] A first judgment module is configured to determine if the first ratio is smaller than the preset ratio;
[0039] then, according to the fault type corresponding to the fault feature code group, obtaining at least one secondary fault feature code group associated with the target fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set;
[0040] A second ratio acquisition module, configured to obtain a second ratio according to a ratio of the fault main code feature set to the number of fault feature codes in the fault feature code set;
[0041] The fault main code feature set processing module is configured to push the fault main code feature set to a fault detection system when the second ratio is greater than the preset ratio.
[0042] In a third aspect, the present application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above method.
[0043] In a fourth aspect, the present application provides a computer storage medium, wherein a computer program is stored on the computer-readable storage medium, and a processor executes the computer program to implement the above method.
[0044] Beneficial effects that this application can achieve:
[0045] A vehicle fault data management method, system, device and medium proposed in an embodiment of the present application include the following operating steps: obtaining a fault code set, extracting fault feature codes of all fault codes in the fault code set, and forming a fault feature code set; dividing the fault feature code set into multiple fault feature code groups according to the fault type corresponding to the fault feature code, and obtaining a target fault feature code group with the largest number of fault feature codes; obtaining a first ratio according to the ratio of the number of fault feature codes of the target fault feature code group to the number of fault feature codes in the fault feature code set; if the first ratio is less than the preset ratio; then obtaining at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, and the target fault feature code group and at least one secondary fault feature code group form a fault main code feature set; obtaining a second ratio according to the ratio of the number of fault feature codes of the fault main code feature set to the number of fault feature codes in the fault feature code set; when the second ratio is greater than the preset ratio, pushing the fault main code feature set to a fault detection system. Through systematic processing procedures, precise fault location, dynamically adjusted detection range and automated data push, the efficiency and accuracy of vehicle fault diagnosis have been significantly improved, providing strong technical support for vehicle repair and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Figure 1 This is a flow chart of the vehicle fault data management method of the present application.
[0047] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0049] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.
[0050] In the present invention, unless otherwise clearly specified and limited, the terms "connection", "fixation", etc. should be understood in a broad sense. For example, "fixation" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements, unless otherwise clearly defined. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0051] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the meaning of "and / or" appearing in the full text includes three parallel schemes. Taking "A and / or B" as an example, it includes scheme A, or scheme B, or a scheme that satisfies both A and B. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in the field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.
[0052] Example 1
[0053] Reference Figure 1 The first embodiment of the present application provides a vehicle fault data management method, comprising the following steps:
[0054] S10, acquiring a fault code set, extracting fault feature codes of all the fault codes in the fault code set, and forming a fault feature code set.
[0055] Specifically, a fault code is a coding system used by automotive electronic systems to diagnose and report faults. In the automotive field, a fault code is usually composed of a set of characters (including letters and numbers), and each fault code uniquely corresponds to a specific fault or a class of faults. These fault codes are stored in the car's electronic control unit (ECU). When the system detects a fault, the corresponding fault code will be triggered and recorded.
[0056] The types of car failures generally include the following:
[0057] Engine failure: including ignition system failure, fuel supply system failure, cooling system failure, etc. For example, engine ignition system failure may cause the engine to fail to start or run unstably.
[0058] Transmission system failure: including transmission failure, clutch failure, drive shaft failure, etc. Transmission system failure may cause the car to be unable to drive normally or cause abnormal noise, shaking, etc. during driving.
[0059] Electrical system failure: including battery failure, generator failure, line failure, etc. Electrical system failure may cause the car lights to not light up, the instrument to not display, or the electrical equipment to not work properly.
[0060] Braking system failure: including brake pad wear, insufficient brake fluid, brake failure, etc. Braking system failure may cause the vehicle's braking performance to decline or fail, posing a serious threat to driving safety.
[0061] Chassis and suspension system failure: including tire failure, suspension system damage, steering system failure, etc. Such failures may cause unstable driving, reduced handling or abnormal noise.
[0062] For ease of understanding, let's take a specific fault code as an example: Assume that the fault code read is "P0123", then: The first character: "P" indicates the powertrain system. The second character: "0" indicates that this is a universal code controlled by the ISO / SAE standard. The third, fourth and fifth characters: "123" are the fault signature codes, indicating the specific fault type or condition. In this example, according to the standard, "P0123" usually means "the input voltage of the throttle position sensor circuit A is too high."
[0063] S20. Divide the fault feature code set into a plurality of fault feature code groups according to the fault types corresponding to the fault feature codes, and obtain a target fault feature code group having the largest number of fault feature codes.
[0064] A fault signature group refers to the situation that the same type of fault may occur multiple times in a vehicle within a period of time, and the cause is relatively simple. Therefore, the fault codes in the current time period can be divided into the same fault signature group according to the same type of fault. Multiple fault signature groups represent the most common fault codes of different types of faults in the current time period. By dividing the fault signature set into multiple fault signature groups according to the fault type corresponding to the fault signature code, and identifying the target fault signature group with the largest number of fault signature codes, this method aims to quickly locate the most common or important fault type in the vehicle, and provide strong support for subsequent fault diagnosis and repair.
[0065] S30: Obtain a first ratio according to the ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set.
[0066] S40: If the first ratio is smaller than the preset ratio.
[0067] Optionally, the preset ratio can be set according to actual conditions, for example, the preset ratio can be any ratio between 20% and 40%. The first ratio being less than the preset ratio means that the first ratio is too small, the number of fault feature codes in the target fault feature code group is not much different from the number of other fault feature code groups, and other fault feature code groups may also cause vehicle failures, so it is not suitable to directly push the target fault feature code to the fault detection system.
[0068] S50, acquiring at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set.
[0069] By using the main fault code feature set, the present invention can realize multi-level diagnosis of faults. First, the main fault type is quickly located through the target fault feature code group; then, combined with the secondary fault feature code group, the potential causes or concurrent faults that may lead to the main fault are deeply explored to provide maintenance personnel with a detailed fault diagnosis report. The main fault code feature set not only reveals the direct connection between faults, but also shows the potential correlation between faults through the secondary fault feature code group. This analysis helps to discover the fault propagation path, prevent chain reactions caused by a single fault, and improve the overall stability and security of the system.
[0070] S60: Obtain a second ratio according to the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set.
[0071] By calculating the ratio of the number of fault signatures in the fault main code feature set (including the target fault signature code group and its associated secondary fault signature code group) to the number of fault signatures in the entire fault signature code set, the coverage of the fault main code feature set for the overall fault can be evaluated. The level of the second ratio reflects the completeness and representativeness of the fault main code feature set. If the second ratio is low, it means that the fault main code feature set may not fully cover all relevant fault signatures. At this time, it may be necessary to further expand the acquisition scope of the secondary fault signature code group, or reconsider the selection of the target fault signature code group to optimize the fault diagnosis strategy. The second ratio can also be used as a reference for fault prediction and prevention. If the second ratio of a certain fault main code feature set is continuously high, it may mean that the fault type corresponding to the set is more common in the system or has a higher probability of occurrence, so it is necessary to strengthen the monitoring and prevention of this type of fault.
[0072] S70: When the second ratio is greater than the preset ratio, the fault main code feature set is pushed to a fault detection system.
[0073] A fault detection system is a technical system designed specifically to monitor, identify and report faults in equipment or systems. In the automotive field, fault detection systems are usually integrated into the vehicle's electronic control unit (ECU) or used as a standalone diagnostic tool. By processing and screening fault codes and utilizing the powerful analysis capabilities of the fault detection system, a more in-depth and accurate diagnosis of faults can be performed to locate the cause of the fault more quickly.
[0074] Example 2
[0075] Based on Example 1, this example provides a vehicle fault data management method, including the following steps:
[0076] S10, acquiring a fault code set, extracting fault feature codes of all the fault codes in the fault code set, and forming a fault feature code set.
[0077] The step of obtaining a fault code set, extracting fault feature codes of all fault codes in the fault code set, and forming a fault feature code set includes:
[0078] S11, obtaining all fault codes within a preset time period and forming a fault code set;
[0079] The preset time period can be a user actively sending a request to obtain a fault code, or the fault code can be obtained at a preset frequency, which can be daily, weekly, or monthly.
[0080] S12, traversing the fault code set, parsing each fault code according to a predetermined parsing rule to obtain its corresponding fault feature code, and forming all the fault feature codes into a fault feature code set.
[0081] Predetermined interpretation rules, such as the most common OBD-II (second-generation on-board diagnostic system) fault code, are usually composed of five characters, including an alphabetic prefix and four subsequent characters (numbers or letters, but in most cases numbers). The first character: usually a letter, indicating the system or subsystem. For example, P stands for powertrain, B stands for body, C stands for chassis, and U stands for undefined network communication problems. The second character: usually a number 0 or 1, indicating the body of the code. 0 represents a universal code controlled by ISO / SAE standards, while 1 represents a specific code controlled by the car manufacturer. The third character: a number, indicating the subsystem where the detected fault is located. For example, 0 may represent the entire system, 1 and 2 may be related to the fuel supply system, 3 represents the ignition system, etc. The fourth and fifth characters: numbers, indicating the specific fault type or condition. These numbers provide detailed information about the nature of the fault, such as sensor signals out of range, slow actuator response, etc. The fault signature code usually refers to the part of the code that can uniquely identify a specific fault type or condition. For OBD-II fault codes, the fault signature code mainly consists of the first, third, fourth and fifth characters, because they together provide detailed information about the specific nature of the fault.
[0082] For ease of understanding, a specific example is as follows: Assuming the fault code read is "P0123", then: The first character: "P" indicates the powertrain system. The second character: "0" indicates that this is a universal code controlled by the ISO / SAE standard. The third, fourth and fifth characters: "p, 1, 2, 3" are fault signature codes, indicating the specific fault type or condition. In this example, according to the standard, "P0123" generally means "The input voltage of the throttle position sensor circuit A is too high."
[0083] S20, dividing the fault feature code set into a plurality of fault feature code groups according to the fault types corresponding to the fault feature codes, and obtaining a target fault feature code group having the largest number of fault feature codes;
[0084] The step of dividing the fault feature code set into a plurality of fault feature code groups according to the fault type corresponding to the fault feature code, and obtaining a target fault feature code group with the largest number of fault feature codes comprises:
[0085] S21, traversing the fault feature code set, and dividing the fault feature codes with the same fault type into the same fault feature code group according to the fault types corresponding to the fault feature codes;
[0086] Optionally, initialize an empty dictionary or hash table to store the mapping relationship between the fault type and the corresponding fault feature code group. For each fault feature code, check its corresponding fault type. If the fault type already exists in the dictionary, add the fault feature code to the feature code group corresponding to the fault type. If the fault type does not exist in the dictionary, create a new fault feature code group, add the fault feature code to it, and associate the fault type with the newly created feature code group and store it in the dictionary.
[0087] S22, sorting all fault feature code groups according to the number of fault feature code groups;
[0088] Optionally, create a list to store all fault signature code groups and their corresponding fault signature code quantities. Traverse the dictionary constructed in the previous step and calculate the number of fault signature codes contained in each fault signature code group. Sort the fault signature code groups in the list in descending order according to the number of fault signature codes.
[0089] S23. Mark the fault feature code group with the largest number of fault feature codes as the target fault feature code group.
[0090] Specifically, the sorted list is checked to find the fault feature code group with the largest number of fault feature codes, and the fault feature code group is marked as a target fault feature code group for subsequent focused analysis or processing.
[0091] For steps S21-S23, for ease of understanding, an example is given as follows: Assume that there is a set of the following fault feature codes: feature code A, corresponding to the fault type "memory leak"; feature code B, corresponding to the fault type "disk damage"; feature code C, corresponding to the fault type "memory leak"; feature code D, corresponding to the fault type "network interruption"; feature code E, corresponding to the fault type "memory leak".
[0092] According to step S21, we divide these feature codes into the following fault feature code groups: "memory leakage" group: [A, C, E]; "disk damage" group: [B]; "network interruption" group: [D].
[0093] Next, according to step S22, we sort the groups according to the number of feature codes, and obtain: "memory leak" group (3 feature codes); "disk damage" group (1 feature code); "network interruption" group (1 feature code).
[0094] Finally, according to step S23, we mark the "memory leak" group as the target fault signature group because it contains the largest number of signatures, indicating that "memory leak" may be the most common or serious problem in the current system and requires priority attention and processing.
[0095] S30, obtaining a first ratio according to the ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set;
[0096] The step of obtaining the first ratio according to the ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set further includes:
[0097] S31, verifying the relationship between the first ratio and a preset ratio;
[0098] Specifically, the first ratio is compared with a preset ratio.
[0099] S32: If the first ratio is greater than or equal to the preset ratio, the target feature code group is pushed to a fault detection system.
[0100] Specifically, if the first ratio is greater than or equal to the preset ratio, it means that the target fault feature code group accounts for a large proportion in the fault feature code set, which may represent a common or serious fault type. Therefore, the target feature code group is pushed to the fault detection system for more in-depth analysis and diagnosis.
[0101] The step of pushing the target feature code group to the fault detection system if the first ratio is greater than or equal to the preset ratio further includes:
[0102] S321, extracting vehicle status history data of the same vehicle model, the same fault type, and the same fault level according to the target feature code group;
[0103] S322: Predict the vehicle state of the target vehicle.
[0104] Specifically, the future state of the target vehicle is predicted using the extracted vehicle status history data and the analysis results of the fault detection system. The prediction content may include the probability of fault occurrence, possible fault time, the impact of the fault on vehicle performance, etc., so as to take preventive measures or prepare maintenance resources in time.
[0105] For steps S321-S322, for ease of understanding, an example is given below: Assume that a fault feature code set of a certain vehicle type contains 1000 fault feature codes, of which the target fault feature code group "engine fault" contains 200 fault feature codes. The preset ratio is 15%. Calculate the first ratio: 200 / 1000=20%. Verify the relationship between the first ratio and the preset ratio: 20%>15%, so the first ratio is greater than the preset ratio.
[0106] Push target signature code group to fault detection system: Push the "engine fault" signature code group to the fault detection system for analysis.
[0107] Extract vehicle status history data: extract vehicle status history data of the same vehicle model, the same fault type "engine failure", and the same fault level (such as "serious") from the database.
[0108] Predict the vehicle status of the target vehicle: Use the extracted data and the analysis results of the fault detection system to predict the probability and possible impact of "engine failure" of the target vehicle in the future so that corresponding measures can be taken in time.
[0109] S40, if the first ratio is smaller than the preset ratio;
[0110] S50, acquiring at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set;
[0111] The step of obtaining at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group form a fault main code feature set comprises:
[0112] S51, acquiring the fault type and fault location corresponding to the target fault feature code group, and the fault types and fault locations of all remaining fault feature code groups except the target fault feature code group;
[0113] S52, comparing the fault types and fault locations of all remaining fault feature code groups with the fault types and fault locations corresponding to the target fault feature code group, to obtain the correlation between all remaining fault feature code groups and the target fault feature code group;
[0114] S53 . According to the correlation, sort all remaining fault feature code groups from high to low according to the correlation to obtain a first sorting result.
[0115] Specifically, the purpose of comparing the fault type and fault location is to find out the possible correlation between the remaining fault feature code group and the target fault feature code group, such as whether they belong to the same system, whether they are caused by the same reason, whether they often occur at the same time, etc.
[0116] According to the comparison results, the correlation between the remaining fault signature code groups and the target fault signature code group is evaluated. The correlation can be quantified by setting certain standards or weights, such as the frequency of common occurrence, the similarity of fault causes, the degree of fault impact, etc.
[0117] The remaining fault signature code groups are sorted from high to low according to the correlation to obtain the first sorting result. The purpose of sorting is to give priority to those fault signature code groups that are highly correlated with the target fault signature code group and may have a greater impact on the system.
[0118] For steps S51-S53, for ease of understanding, an example is given below: Assume that the fault type corresponding to the target fault feature code group is "battery aging" and the fault location is "electric vehicle battery pack". The remaining fault feature code groups include multiple groups, one of which corresponds to the fault type "charging system abnormality" and the fault location is "electric vehicle charging interface".
[0119] Obtaining information (S51):
[0120] Target fault signature group: "Battery aging" (electric vehicle battery pack)
[0121] One of the remaining fault feature code groups: "Charging system abnormality" (electric vehicle charging interface)
[0122] Compare the fault type and fault location (S52):
[0123] A comparison found that although "battery aging" and "charging system abnormality" are different types of faults, they are both related to the energy system of electric vehicles, and battery aging may affect the charging effect, so there is a certain correlation.
[0124] Evaluate and sort the associations (S53):
[0125] According to the correlation evaluation criteria (such as the frequency of common occurrence, similarity of fault causes, etc.), the "charging system abnormality" fault feature code group is ranked at a higher position because it has a strong correlation with the target fault feature code group "battery aging". The other remaining fault feature code groups are also evaluated and ranked in a similar way.
[0126] S60, obtaining a second ratio according to the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set;
[0127] The step of obtaining a second ratio according to the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set comprises:
[0128] S61, adding the target fault feature code group to the fault main code feature set;
[0129] S62. According to the first sorting result, the remaining fault feature code groups are sequentially added to the fault main code feature set until the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set is greater than a preset ratio.
[0130] Specifically, according to the first sorting result, the fault feature code groups with the highest sorting are added one by one to the fault main code feature set. After each addition, the ratio of the number of fault feature codes in the fault main code feature set to the fault feature code set is recalculated, and the second ratio is compared with the preset ratio. Until the second ratio is greater than or equal to the preset ratio, the action of adding the fault feature code group to the fault main code feature set is stopped.
[0131] S70: When the second ratio is greater than the preset ratio, the fault main code feature set is pushed to a fault detection system.
[0132] For the convenience of understanding, steps S60-S70 are described below with examples:
[0133] Assume that the fault signature set includes 1000 fault signatures, the target fault signature group includes 50 fault signatures, and the remaining fault signature groups have 20, which have been sorted in the first order according to the relevance. The preset ratio is 15%.
[0134] Add the target fault feature code group (50 fault feature codes) to the fault main code feature set.
[0135] According to the first sorting result, the remaining fault feature code groups are sequentially added to the fault main code feature set, and a new ratio is calculated after each addition.
[0136] Assume that after adding the first five remaining fault feature code groups, the total number of fault feature codes in the fault main code feature set reaches 160.
[0137] The calculated ratio is 140 / 1000=14%, which is less than the preset ratio. However, since we need the ratio to be greater than the preset ratio, we continue to add.
[0138] After adding the sixth remaining fault feature code group, the ratio becomes 160 / 1000=16%, which is greater than the preset ratio.
[0139] When the ratio is greater than the preset ratio (ie, 16%>15%), the current fault main code feature set (including the target fault feature code group and the remaining fault feature code groups that have been added) is pushed to the fault detection system.
[0140] Example 3
[0141] Based on Example 1, this embodiment provides a vehicle fault data management system, including:
[0142] A fault code acquisition module is configured to acquire a fault code set, extract fault feature codes of all fault codes in the fault code set, and form a fault feature code set;
[0143] a fault code processing module, configured to divide the fault feature code set into a plurality of fault feature code groups according to the fault type corresponding to the fault feature code, and obtain a target fault feature code group with the largest number of fault feature codes;
[0144] A first ratio acquisition module, configured to obtain a first ratio according to a ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set;
[0145] A first judgment module is configured to determine if the first ratio is smaller than the preset ratio;
[0146] then, according to the fault type corresponding to the fault feature code group, obtaining at least one secondary fault feature code group associated with the target fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set;
[0147] A second ratio acquisition module, configured to obtain a second ratio according to a ratio of the fault main code feature set to the number of fault feature codes in the fault feature code set;
[0148] The fault main code feature set processing module is configured to push the fault main code feature set to a fault detection system when the second ratio is greater than the preset ratio.
[0149] Example 4
[0150] Based on the same inventive concept as the above-mentioned embodiment, this embodiment provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-mentioned method.
[0151] Example 5
[0152] Based on the same inventive concept as the aforementioned embodiment, this embodiment provides a computer-readable storage medium, on which a computer program is stored, and a processor executes the computer program to implement the aforementioned method.
[0153] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A vehicle fault data management method, characterized in that: The steps are as follows: Acquire a fault code set, extract fault feature codes of all fault codes in the fault code set, and form a fault feature code set; According to the fault type corresponding to the fault feature code, the fault feature code set is divided into a plurality of fault feature code groups, and a target fault feature code group with the largest number of fault feature codes is obtained; Obtaining a first ratio according to a ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set; If the first ratio is smaller than the preset ratio; then, according to the fault type corresponding to the fault feature code group, obtaining at least one secondary fault feature code group associated with the target fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set; Obtaining a second ratio according to a ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set; When the second ratio is greater than the preset ratio, the fault main code feature set is pushed to a fault detection system.
2. The vehicle fault data management method according to claim 1, characterized in that: The step of obtaining a fault code set, extracting fault feature codes of all fault codes in the fault code set, and forming a fault feature code set includes: Obtain all fault codes within a preset time period and form a fault code set; The fault code set is traversed, and for each fault code, its corresponding fault feature code is parsed according to a predetermined parsing rule, and all the fault feature codes are combined into a fault feature code set.
3. The vehicle fault data management method according to claim 1, characterized in that: The step of dividing the fault feature code set into a plurality of fault feature code groups according to the fault type corresponding to the fault feature code, and obtaining a target fault feature code group with the largest number of fault feature codes comprises: Traversing the fault feature code set, and dividing the fault feature codes with the same fault type into the same fault feature code group according to the fault types corresponding to the fault feature codes; sorting all the fault feature code groups according to the number of fault feature codes in the fault feature code group; The fault feature code group with the largest number of marked fault feature codes is the target fault feature code group.
4. The vehicle fault data management method according to claim 1, characterized in that: The step of obtaining the first ratio according to the ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set further includes: Verifying the relationship between the first ratio and a preset ratio; If the first ratio is greater than or equal to the preset ratio, the target feature code group is pushed to the fault detection system.
5. The vehicle fault data management method according to claim 4, characterized in that: The step of pushing the target feature code group to the fault detection system if the first ratio is greater than or equal to the preset ratio further includes: According to the target feature code group, extracting vehicle status history data of the same vehicle model, the same fault type, and the same fault level; Predict the vehicle state of the target vehicle.
6. The vehicle fault data management method according to claim 1, characterized in that: The step of obtaining at least one secondary fault feature code group associated with the target fault feature code group according to the fault type corresponding to the fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group form a fault main code feature set comprises: Obtaining the fault type and fault location corresponding to the target fault feature code group, and the fault types and fault locations of all remaining fault feature code groups except the target fault feature code group; Comparing the fault types and fault locations of all remaining fault feature code groups with the fault types and fault locations corresponding to the target fault feature code group, to obtain the correlation between all remaining fault feature code groups and the target fault feature code group; According to the correlation, all remaining fault feature code groups are sorted from high to low according to the correlation to obtain a first sorting result.
7. The vehicle fault data management method according to claim 6, characterized in that: The step of obtaining a second ratio according to the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set comprises: Adding the target fault feature code group to the fault main code feature set; According to the first sorting result, the remaining fault feature code groups are sequentially added to the fault main code feature set until the ratio of the number of fault feature codes in the fault main code feature set to the number of fault feature codes in the fault feature code set is greater than a preset ratio.
8. A vehicle fault data management system, characterized in that: include: A fault code acquisition module is configured to acquire a fault code set, extract fault feature codes of all fault codes in the fault code set, and form a fault feature code set; a fault code processing module, configured to divide the fault feature code set into a plurality of fault feature code groups according to the fault type corresponding to the fault feature code, and obtain a target fault feature code group with the largest number of fault feature codes; A first ratio acquisition module, configured to obtain a first ratio according to a ratio of the number of fault feature codes in the target fault feature code group to the number of fault feature codes in the fault feature code set; A first judgment module is configured to determine if the first ratio is smaller than the preset ratio; then, according to the fault type corresponding to the fault feature code group, obtaining at least one secondary fault feature code group associated with the target fault feature code group, wherein the target fault feature code group and the at least one secondary fault feature code group constitute a primary fault code feature set; A second ratio acquisition module, configured to obtain a second ratio according to a ratio of the fault main code feature set to the number of fault feature codes in the fault feature code set; The fault main code feature set processing module is configured to push the fault main code feature set to a fault detection system when the second ratio is greater than the preset ratio.
9. A computer device, characterized in that: The computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method according to any one of claims 1 to 7.
10. A computer storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the processor executes the computer program to implement the method according to any one of claims 1 to 7.