A method, apparatus, and device for processing fault data

Abstract

Embodiments of the present application disclose a method, apparatus, and device for processing fault data. By obtaining the running fault information of the whole vehicle, grouping the running fault information according to the fault type to obtain at least one group of running fault codes; performing bitwise operations on the running fault codes to obtain fault configuration codes. Through the fault configuration codes calculated after grouping the running fault information, the management of a large amount of running fault information can be realized, and the quantity of the running fault information is reduced. Then, a target fault configuration code is selected from the fault configuration codes, and the fault data corresponding to the target fault configuration code is calculated. By using the obtained fault data, the corresponding fault problem can be determined, realizing the determination of the fault problem based on the fault data, thereby improving the efficiency of determining the fault problem and accelerating the speed of software development.

Description

Technical Field

[0001] This application relates to the field of data processing, and particularly to a method, apparatus, and device for processing fault data. Background Art

[0002] Software is installed in a vehicle, and users can obtain the vehicle status and control the vehicle through the software. In the initial stage of software development and testing, developers need to obtain the test results of the actual vehicle and adjust the main body of the software according to the test results of the actual vehicle, so that the software can better meet the usage requirements.

[0003] Currently, the storage method of vehicle fault signals is relatively complex, and a relatively large number of fault codes are required to accurately reflect a fault problem, resulting in complex processing of fault codes. Moreover, it is difficult for developers to directly determine the fault problem from the fault codes, which is not convenient for using the fault codes to correct the software, resulting in low software development efficiency. Summary of the Invention

[0004] In view of this, embodiments of this application provide a method, apparatus, and device for processing fault data, which can generate relatively simple fault data and directly obtain the fault types through the fault data, improving the software development efficiency.

[0005] To solve the above problems, the technical solutions provided by the embodiments of this application are as follows:

[0006] In a first aspect, this application provides a method for processing fault data, the method including:

[0007] Obtain the running fault information of the entire vehicle;

[0008] Group the running fault information according to the fault type to obtain at least one group of running fault codes;

[0009] Perform bitwise operations on the running fault codes to obtain fault configuration codes;

[0010] Select a target fault configuration code from the fault configuration codes, and calculate the fault data corresponding to the target fault configuration code.

[0011] In a possible implementation manner, the obtaining the running fault information of the entire vehicle includes:

[0012] Obtain the first fault information and the second fault information of the entire vehicle, where the first fault information is of boolean type;

[0013] Compare the second fault information with a target threshold value, and convert the second fault information into third fault information of boolean type according to the comparison result; the target threshold value is the threshold value corresponding to the second fault information;

[0014] Obtain the operation fault information based on the first fault information and the third fault information.

[0015] In a possible implementation, calculating the fault data corresponding to the target fault configuration code includes:

[0016] Convert the target fault configuration code into a target base form;

[0017] Obtain the standard configuration code in the target base form corresponding to the target fault configuration code;

[0018] Perform an AND calculation on the target fault configuration code and the standard configuration code to obtain the fault data.

[0019] In a possible implementation, the method further includes:

[0020] Obtain target fault data; the target fault data is the fault data generated by the above fault data processing method;

[0021] Parse the target fault data to obtain the to-be-processed fault configuration code corresponding to the fault data;

[0022] Determine the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

[0023] In a possible implementation, parsing the target fault data to obtain the to-be-processed fault configuration code corresponding to the fault data includes:

[0024] Use the BASE function to parse the target fault data to obtain the to-be-processed fault configuration code corresponding to the target fault data.

[0025] In a possible implementation, before determining the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code, the method further includes:

[0026] Use the PEPT function to perform padding on the to-be-processed fault configuration code.

[0027] In a possible implementation, determining the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code includes:

[0028] Use the MID function to perform bit-by-bit extraction operation on the to-be-processed fault configuration code to obtain fault bits in the first order; the number of the fault bits is the same as the number of bits of the to-be-processed fault configuration code;

[0029] Use the INDEX function to perform reverse order operation on the fault bits in the first order to obtain fault bits in the second order, and the second order is opposite to the first order;

[0030] Determine the vehicle fault according to the value of the fault bit in the second order and the fault type corresponding to the fault bit in the second order.

[0031] In a second aspect, the present application provides a device for processing fault data, the device includes:

[0032] A first acquisition unit, configured to acquire the running fault information of the vehicle;

[0033] A grouping unit, configured to group the running fault information according to the fault type to obtain at least one group of running fault codes;

[0034] A first calculation unit, configured to perform bitwise operations on the running fault codes to obtain fault configuration codes;

[0035] A second calculation unit, configured to select a target fault configuration code from the fault configuration codes and calculate the fault data corresponding to the target fault configuration code.

[0036] In a possible implementation manner, the first acquisition unit is specifically configured to acquire the first fault information and the second fault information of the vehicle, wherein the first fault information is of a Boolean type;

[0037] Compare the second fault information with a target threshold value, and convert the second fault information into third fault information of a Boolean type according to the comparison result; the target threshold value is the threshold value corresponding to the second fault information;

[0038] Obtain the running fault information according to the first fault information and the third fault information.

[0039] In a possible implementation manner, the second calculation unit is specifically configured to convert the target fault configuration code into a target base form;

[0040] Obtain a standard configuration code in the target base form corresponding to the target fault configuration code;

[0041] Perform an AND calculation on the target fault configuration code and the standard configuration code to obtain the fault data.

[0042] In a possible implementation manner, the device further includes:

[0043] A second acquisition unit, configured to acquire target fault data; the target fault data is the fault data generated by the above-mentioned fault data processing method;

[0044] An analysis unit, configured to analyze the target fault data to obtain a to-be-processed fault configuration code corresponding to the fault data;

[0045] A determination unit, configured to determine a vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

[0046] In a possible implementation manner, the parsing unit is specifically configured to parse the target fault data by using the BASE function to obtain the to-be-processed fault configuration code corresponding to the target fault data.

[0047] In a possible implementation manner, the parsing unit is further configured to perform padding on the to-be-processed fault configuration code by using the PEPT function.

[0048] In a possible implementation manner, the determination unit is specifically configured to perform bit-by-bit extraction operation on the to-be-processed fault configuration code by using the MID function to obtain fault bits in a first order; the number of the fault bits is the same as the number of bits of the to-be-processed fault configuration code;

[0049] Perform reverse order operation on the fault bits in the first order by using the INDEX function to obtain fault bits in a second order, where the second order is opposite to the first order;

[0050] Determine the vehicle fault according to the values of the fault bits in the second order and the fault types corresponding to the fault bits in the second order.

[0051] In a third aspect, the present application provides a processing device for fault data, including: a processor, a memory, and a system bus;

[0052] The processor and the memory are connected through the system bus;

[0053] The memory is used to store one or more programs, and the one or more programs include instructions, and when the instructions are executed by the processor, the processor executes the fault data processing method described in any one of the above, or executes the fault data processing method described in any one of the above.

[0054] In a fourth aspect, the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions run on a terminal device, the terminal device executes the fault data processing method described in any one of the above.

[0055] Thus, the embodiments of the present application have the following beneficial effects:

[0056] The method, device, and equipment for processing fault data provided by the embodiments of the present application obtain the running fault information of the whole vehicle, group the running fault information according to the fault type to obtain at least one group of running fault codes, perform bitwise operations on the running fault codes to obtain fault configuration codes. The fault configuration codes calculated after grouping the running fault information can manage a large number of running fault information, reducing the quantity of the running fault information. Then, select target fault configuration codes from the fault configuration codes and calculate the fault data corresponding to the target fault configuration codes. Using the obtained fault data can determine the corresponding fault problems, realizing the determination of fault problems based on the fault data, thereby improving the efficiency of determining fault problems and accelerating the speed of software development. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 It is a flowchart of a method for processing fault data provided by the embodiments of the present application;

[0058] Figure 2 It is a flowchart of another method for processing fault data provided by the embodiments of the present application;

[0059] Figure 3 It is a schematic structural diagram of a device for processing fault data provided by the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0060] To facilitate the understanding and interpretation of the technical solutions provided by the embodiments of the present application, the background technology of the present application will be described first.

[0061] After the inventors' research on the traditional vehicle software development process, they found that, on the one hand, the existing fault storage adopts the methods of fault codes and data snapshots. A relatively complete fault problem may be jointly determined by a large number of signals, and a large amount of data is not convenient for developers to quickly determine the fault problem. On the other hand, after obtaining the fault data, it is also necessary to implement the analysis of the fault data based on the data backfilling of the model, which will lead to a low analysis efficiency of the fault data and is not convenient for developers to quickly determine the fault problem corresponding to the fault data.

[0062] Based on this, the embodiments of the present application provide a method for processing fault data. First, obtain the running fault information of the whole vehicle; group the running fault information according to the fault type to obtain at least one group of running fault codes; secondly, perform bitwise operations on the running fault codes to obtain fault configuration codes; finally, select target fault configuration codes from the fault configuration codes and calculate the fault data corresponding to the target fault configuration codes.

[0063] To facilitate the understanding of the technical solutions provided by the embodiments of the present application, the following describes a method for processing fault data provided by the embodiments of the present application with reference to the accompanying drawings.

[0064] See Figure 1 As shown, this figure is a flowchart of a method for processing fault data provided by an embodiment of the present application. The method includes steps S101 - S104.

[0065] S101: Obtain the running fault information of the whole vehicle.

[0066] The embodiment of the present application does not limit the source of the running fault information. In a possible implementation, the running fault information may be the fault information detected by the underlying software equipped in the whole vehicle. The running fault information may also be the fault information detected by the application layer.

[0067] It should be noted that the types of running fault information from different sources are different. To facilitate the processing of the running fault information and reduce the data transmission volume corresponding to the running fault information, the running fault information can be converted into a boolean type. The embodiment of the present application provides a specific implementation for obtaining the running fault information of the whole vehicle. Please refer to the following text.

[0068] S102: Group the running fault information according to the fault type to obtain at least one group of running fault codes.

[0069] Group the obtained running fault information according to the pre - set fault type. In a possible implementation, the running fault information can be sorted through a pre - set running fault comparison table. After sorting, the running fault information can represent the corresponding fault type. Group and divide the sorted running fault information, and generate running fault codes corresponding to each group of running fault information. The number of digits of the running fault code can be determined according to the coding length of the software. For example, the number of digits of the running fault code can be 8, 16, 32, etc.

[0070] By grouping the running fault information according to the fault type to obtain the corresponding running fault codes, the running fault information can be preliminarily sorted.

[0071] S103: Perform bitwise operations on the running fault codes to obtain fault configuration codes.

[0072] Perform bitwise operations on the obtained grouped running fault codes to obtain fault configuration codes corresponding to the running fault codes.

[0073] In a possible implementation, the bitwise operation can be a radix conversion. Through the radix conversion, the fault configuration code with more characters can be converted into a corresponding single fault configuration code.

[0074] The number of characters corresponding to the fault configuration code is relatively small, so that the number of bytes occupied by the data representing the fault can be reduced. By using a fault configuration code with a relatively small number of characters to represent a running fault code with a relatively large number of characters, efficient management of the running fault code can be achieved.

[0075] The obtained fault configuration code can be used for storage. By storing the fault configuration code with a relatively small number of characters, the storage capacity required to store the running fault information can be reduced.

[0076] S104: Select a target fault configuration code from the fault configuration codes, and calculate the fault data corresponding to the target fault configuration code.

[0077] The fault configuration code contains information about the faults of the whole vehicle. A target fault configuration code with a fault problem can be selected from the obtained fault configuration codes. It can be understood that a single target fault configuration code corresponds to a multi-bit running fault code, which may include multiple fault information. In order to clarify the fault information in the target fault configuration code and screen the fault information, the fault data corresponding to the target fault configuration code is further calculated. The fault data is used to represent the fault information obtained by screening in the target fault configuration code.

[0078] Based on the relevant content of the above S101 - S104, it can be known that in the embodiment of the present application, by first grouping and performing bit operations on the running fault information of the whole vehicle, the number of characters of the stored fault configuration code is reduced, thereby reducing the storage space required for storage. And, efficient management of the running fault information is achieved, which is convenient for fault analysis by means of the fault configuration code. The fault data calculated using the target fault configuration code can reflect the faults contained in the target fault configuration code. The specific fault type can be reversely parsed through the fault data to determine the fault problem, thereby improving the efficiency of determining the fault problem and accelerating the speed of software development.

[0079] When the running fault information is the running fault information output by the application layer, the running fault information is usually represented by physical quantities, uses a relatively large number of characters, and occupies a relatively large storage space, which is inconvenient for fault analysis of the running fault information.

[0080] Based on the above problems, in a possible implementation manner, the obtaining of the running fault information of the whole vehicle includes the following three steps:

[0081] A1: Obtain the first fault information and the second fault information of the whole vehicle, where the first fault information is of the Boolean type.

[0082] The fault information of the whole vehicle can be obtained through different software logic layers. The fault information output by the software bottom layer is usually represented in Boolean type. For example, whether a fault occurs is represented by 0 or 1. The fault information output by the application layer of the software is usually represented by physical quantities. For example, the brake pedal opening is 85%. The fault information represented by physical quantities needs to be further compared with the target critical value to determine whether a fault occurs.

[0083] Obtain the first fault information and the second fault information of the whole vehicle. Among them, the first fault information is the fault information represented in Boolean type. The fault information represented by Boolean type is relatively clear on the one hand, and on the other hand, the number of characters it occupies is less, and there is no need for further conversion.

[0084] The second fault information can be fault information other than Boolean type, and the second fault information can be further converted into fault information of Boolean type.

[0085] A2: Compare the second fault information with the target critical value, and convert the second fault information into a third fault information of Boolean type according to the comparison result; the target critical value is the critical value corresponding to the second fault information.

[0086] The second fault information has a corresponding target critical value. For example, when the obtained second fault information is that the brake pedal opening is 85%, the critical value 80% corresponding to the brake pedal opening can be obtained. When the brake pedal opening is greater than or equal to 80%, it is considered that there is a fault in the brake pedal opening; when the brake pedal opening is less than 80%, it is considered that there is no fault in the brake pedal opening.

[0087] Compare the second fault information with the target critical value to obtain the corresponding comparison result. Then, according to the comparison result, determine whether the second fault information corresponds to a fault problem, and convert the second fault information into a third fault information of Boolean type. Taking the above-mentioned brake pedal opening of 85% as an example, comparing 85% with 80%, it can be determined that a fault occurs when the brake pedal opening is 85%, and it is converted into a brake pedal opening flag = 1 to obtain the third fault information.

[0088] A3: Obtain the running fault information according to the first fault information and the third fault information.

[0089] Combine the first fault information and the third fault information to form the running fault information.

[0090] In the embodiment of the present application, by converting the second fault information that does not belong to the Boolean type, the obtained running fault information is all of the Boolean type, which can save storage space on the one hand; on the other hand, it is convenient to perform fault analysis on the running fault information.

[0091] During the software development process, it is necessary to select corresponding fault information according to the software's corresponding requirements, analyze the fault information, and modify the software. However, the current method is to modify the software main body to obtain the corresponding fault information, resulting in a relatively high modification cost.

[0092] Based on the above problems, in a possible implementation, a standard configuration code for fault signals can be established in advance according to the needs of software design. The target fault configuration code can be compared with the standard configuration code to calculate the fault data.

[0093] Calculating the fault data corresponding to the target fault configuration code specifically includes:

[0094] Convert the target fault configuration code into a target base form;

[0095] Obtain the standard configuration code in the target base form corresponding to the target fault configuration code;

[0096] Perform an AND calculation on the target fault configuration code and the standard configuration code to obtain the fault data.

[0097] It should be noted that the standard configuration code is set in advance and is used to screen the fault types to be analyzed. The standard configuration code can be a numerical value with a certain base form. For example, in a possible implementation, binary 0 and 1 can be used to represent fault problems that do not need to be concerned about and fault problems that need to be concerned about respectively. The operation fault codes with different numbers of bits corresponding to the target fault configuration code can represent the fault problems of corresponding fault types, and the standard configuration code can be determined according to the number of bits of the operation fault code corresponding to the target fault configuration code. For example, when the operation fault code corresponding to the target fault configuration code is 8 bits, the set standard configuration code can be an 8-bit binary numerical value.

[0098] When the number of bits of the operation fault code corresponding to the target fault configuration code is relatively large, the corresponding standard configuration code can be a relatively simple numerical value obtained through base conversion. Before comparing and calculating the target fault configuration code with the standard configuration code, the target fault configuration code and the standard configuration code need to be converted into the corresponding target base form first.

[0099] In a possible implementation, the target base form can be binary, and both the standard configuration code and the target fault configuration code can be converted into binary.

[0100] Perform an AND calculation on the target fault configuration code in the target base form and the standard configuration code in the target base form. In this way, the extraction of the fault information that needs to be screened in advance can be realized, and the shielding of the fault information that does not need to be screened can be achieved.

[0101] Taking a specific target fault configuration code and a standard configuration code as examples, where the target base is binary. The standard configuration code after being converted to binary is 01000011, indicating that the fault information of the 2nd, 7th, and 8th bits needs to be extracted. If the target fault configuration code converted to binary is 01000111, after performing an AND operation on the standard configuration code and the target fault configuration code, 01000011 is obtained. In this way, the extraction of the fault information at specific positions in the target fault configuration code and the masking of the fault information at other positions can be achieved.

[0102] Furthermore, for the convenience of transmission, the data obtained from the AND calculation can be subjected to a base conversion to obtain the final fault data. The embodiments of the present application do not limit the specific base conversion method, which can be determined according to the number of bits of the data obtained from the AND calculation. Taking the 01000011 obtained from the above AND calculation as an example, a binary-to-decimal conversion can be performed to obtain the final fault data 67.

[0103] In the embodiments of the present application, by performing an AND calculation on the target fault configuration code and the standard configuration code, the corresponding selection and masking of the fault information represented in the target fault configuration code can be achieved by setting the standard configuration code. When the requirements of the software change and different fault information needs to be obtained, the corresponding fault information can be obtained by modifying the standard configuration code, which is convenient for corresponding adjustment of the obtained fault information and improves the efficiency of software development.

[0104] It can be understood that the fault data can only reflect whether there is fault information that needs to be extracted. When the fault data obtained through the AND operation is greater than or equal to 1, it indicates that there is fault information that needs to be screened in the target fault configuration code. When the fault data obtained through the AND operation is 0, it indicates that there is no fault information that needs to be screened in the target fault configuration code. However, when the fault data is a value greater than or equal to 1, developers cannot directly obtain the specific fault information from the fault data.

[0105] Corresponding to the generated fault data, the embodiments of the present application also provide a processing method for parsing the fault data. Refer to Figure 2 As shown, this figure is a flowchart of another processing method for fault data provided by the embodiments of the present application. In addition to the above steps, this method includes steps S201 - S203.

[0106] S201: Obtain the target fault data; the target fault data is the fault data generated by any of the above fault data processing methods.

[0107] Obtain the target fault data that needs to be parsed through the above fault data processing method.

[0108] S202: Analyze the target fault data to obtain the to-be-processed fault configuration code corresponding to the fault data.

[0109] Given that the target fault data is data after base conversion, first analyze the obtained target fault data to obtain the to-be-processed fault configuration code corresponding to the target fault data.

[0110] In a possible implementation manner, the target fault data may be decimal data and needs to be converted to binary data for fault analysis.

[0111] Specifically, the analyzing the target fault data to obtain the to-be-processed fault configuration code corresponding to the fault data includes:

[0112] Use the BASE function to analyze the target fault data to obtain the to-be-processed fault configuration code corresponding to the target fault data.

[0113] In a possible implementation manner, the BASE function in Excel can be used to perform base conversion from decimal to binary on the target fault data to obtain the binary to-be-processed fault configuration code.

[0114] Taking the above-mentioned fault data 67 as an example, when the target fault data is 67, analyze the decimal 67 through the BASE function to obtain the to-be-processed fault configuration code 1000011.

[0115] Furthermore, since the BASE function can only display the result after the highest bit is 1 during the analysis process and omits the 0s before 1, the to-be-processed fault configuration code obtained by the analysis is not accurate enough. Before determining the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code, the method further includes:

[0116] Use the PEPT function to fill in the positions of the to-be-processed fault configuration code.

[0117] Fill in the positions of the to-be-processed fault configuration code obtained by the analysis of the BASE function through the PEPT function to make the obtained to-be-processed fault configuration code complete. Taking the above-mentioned to-be-processed fault configuration code 1000011 as an example, through the PEPT function, the completed to-be-processed fault configuration code 01000011 is obtained.

[0118] S203: Determine the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

[0119] The obtained to-be-processed fault configuration code corresponds to the fault type. Use the to-be-processed fault configuration code and the corresponding fault type to determine the vehicle fault.

[0120] Based on the relevant content of S201 - S203 above, it can be known that in the embodiments of the present application, by parsing the target fault data, the corresponding fault configuration code to be processed is obtained, and the vehicle fault of the corresponding fault type can be determined by using the fault configuration code to be processed. In this way, the vehicle fault can be directly obtained by parsing the fault data, which is convenient for adjusting the software and improves the software development efficiency.

[0121] In a possible implementation manner, the embodiments of the present application provide a specific implementation manner for determining the vehicle fault according to the fault type corresponding to the fault configuration code to be processed, which specifically includes the following three steps:

[0122] B1: Use the MID function to perform a bit - by - bit extraction operation on the fault configuration code to be processed to obtain fault bits in the first order; the number of the fault bits is the same as the number of bits of the fault configuration code to be processed.

[0123] The fault configuration code to be processed is multi - bit data with specific values. Before using the fault configuration code to be processed to correspond to the fault type, it is necessary to extract the fault configuration code bit by bit to obtain the fault bits corresponding to each fault type.

[0124] Specifically, the MID function can be used to perform a bit - by - bit extraction operation on the fault configuration code to be processed to obtain fault bits in the first order. Taking the above - mentioned fault configuration code to be processed 01000011 as an example, the fault bits in the first order obtained through the bit - by - bit extraction operation by the MID function are 0, 1, 0, 0, 0, 0, 1, 1 respectively.

[0125] B2: Use the INDEX function to perform a reverse - order operation on the fault bits in the first order to obtain fault bits in the second order, and the second order is opposite to the first order.

[0126] The fault bits in the first order obtained by the MID function are determined in the order from the high - order bit to the low - order bit of the fault configuration code to be processed, which is opposite to the calculation order from the low - order bit to the high - order bit of the fault configuration code to be processed. It is necessary to further adjust the order of the fault bits.

[0127] Use the INDEX function to perform a reverse - order operation on the fault bits in the first order to obtain fault bits in the opposite order, that is, the fault bits in the second order. Taking the above - mentioned fault bits in the first order as an example, the corresponding fault bits in the second order are: 1, 1, 0, 0, 0, 0, 1, 0.

[0128] B3: Determine the vehicle fault according to the values of the fault bits in the second order and the fault types corresponding to the fault bits in the second order.

[0129] The second-order fault bits correspond to the fault types. By using the specific values of the second-order fault bits, it is possible to determine whether the corresponding fault type has occurred, thereby determining the vehicle-wide fault.

[0130] Based on the above, it can be seen that in the embodiments of the present application, by bitwise extracting the fault configuration code to be processed and adjusting the order of the fault bits, the matching between the fault configuration code to be processed and the fault type can be achieved, which can more accurately represent the vehicle-wide fault, facilitating developers to improve the software based on the obtained vehicle-wide fault and improving the efficiency of software development.

[0131] Based on the fault data processing method provided in the above method embodiments, the embodiments of the present application also provide a fault data processing device, which will be described below with reference to the accompanying drawings.

[0132] See Figure 3 , which is a schematic structural diagram of a fault data processing device provided in an embodiment of the present application. As Figure 3 shown, the fault data processing device includes:

[0133] A first acquisition unit 301, configured to acquire the running fault information of the vehicle;

[0134] A grouping unit 302, configured to group the running fault information according to the fault type to obtain at least one group of running fault codes;

[0135] A first calculation unit 303, configured to perform bitwise operations on the running fault codes to obtain a fault configuration code;

[0136] A second calculation unit 304, configured to select a target fault configuration code from the fault configuration code and calculate the fault data corresponding to the target fault configuration code.

[0137] In a possible implementation manner, the first acquisition unit 301 is specifically configured to acquire the first fault information and the second fault information of the vehicle, where the first fault information is of a Boolean type;

[0138] Compare the second fault information with a target threshold value, and convert the second fault information into third fault information of a Boolean type according to the comparison result; the target threshold value is the threshold value corresponding to the second fault information;

[0139] Obtain the running fault information according to the first fault information and the third fault information.

[0140] In a possible implementation manner, the second calculation unit 304 is specifically configured to convert the target fault configuration code into a target base form;

[0141] Obtain the standard configuration code in the target base form corresponding to the target fault configuration code;

[0142] Perform an AND calculation on the target fault configuration code and the standard configuration code to obtain fault data.

[0143] In a possible implementation manner, the device further includes:

[0144] A second acquisition unit, configured to acquire target fault data; the target fault data is the fault data generated by the above-mentioned fault data processing method;

[0145] An analysis unit, configured to analyze the target fault data to obtain the to-be-processed fault configuration code corresponding to the fault data;

[0146] A determination unit, configured to determine a vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

[0147] In a possible implementation manner, the analysis unit is specifically configured to use the BASE function to analyze the target fault data to obtain the to-be-processed fault configuration code corresponding to the target fault data.

[0148] In a possible implementation manner, the analysis unit is further configured to use the PEPT function to fill in the positions of the to-be-processed fault configuration code.

[0149] In a possible implementation manner, the determination unit is specifically configured to use the MID function to perform a bit-by-bit extraction operation on the to-be-processed fault configuration code to obtain fault bits in a first order; the number of the fault bits is the same as the number of bits of the to-be-processed fault configuration code;

[0150] Use the INDEX function to perform a reverse order operation on the fault bits in the first order to obtain fault bits in a second order, and the second order is opposite to the first order;

[0151] Determine a vehicle fault according to the values of the fault bits in the second order and the fault types corresponding to the fault bits in the second order.

[0152] Based on the fault data processing method provided in the above method embodiments, the present application provides a fault data processing device, including: a processor, a memory, and a system bus;

[0153] The processor and the memory are connected through the system bus;

[0154] The memory is used to store one or more programs, and the one or more programs include instructions, and when the instructions are executed by the processor, the processor executes the fault data processing method described in any one of the above, or executes the fault data processing method described in any one of the above.

[0155] Based on the method for processing fault data provided in the above method embodiments, the present application provides a computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a terminal device, the terminal device is caused to execute the method for processing fault data described in any one of the above.

[0156] It should be noted that the various embodiments in this specification are described in a progressive manner. The key point of each embodiment is the difference from other embodiments. The same or similar parts among the various embodiments can be referred to each other. For the systems or devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description in the method part.

[0157] It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist at the same time. Among them, A and B can be singular or plural. The character " / " generally means that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or its similar expression means any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (one) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a, b, and c", where a, b, and c can be single or multiple.

[0158] It should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the element.

[0159] The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be implemented directly in hardware, in a software module executed by a processor, or in a combination thereof. The software module may be disposed in a random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0160] The foregoing description of the disclosed embodiments enables those skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing fault data, characterized in that, The method includes: Obtaining the operation fault information of the whole vehicle; Grouping the operation fault information according to the fault type to obtain at least one group of operation fault codes; Performing a number system conversion on the operation fault codes to obtain fault configuration codes, where the fault configuration codes include the information of the faults of the whole vehicle, and the number of characters of the fault configuration codes is less than the number of characters of the operation fault codes; Selecting a target fault configuration code from the fault configuration codes, and converting the target fault configuration code into a target number system form; obtaining a standard configuration code in the target number system form corresponding to the target fault configuration code; performing an AND calculation on the target fault configuration code and the standard configuration code to obtain fault data, where the target fault configuration code includes a fault problem, the standard configuration code is pre-set and used to screen the fault types to be analyzed, the fault data is used to reflect the fault information included in the target fault configuration code, and the fault data is used to reversely analyze to obtain the specific fault type; Parsing the fault data to obtain a to-be-processed fault configuration code corresponding to the fault data; Determining the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

2. The method according to claim 1, characterized in that, The obtaining of the operation fault information of the whole vehicle includes: Obtaining the first fault information and the second fault information of the whole vehicle, where the first fault information is of a Boolean type; Comparing the second fault information with a target critical value, and converting the second fault information into a third fault information of a Boolean type according to the comparison result; the target critical value is the critical value corresponding to the second fault information; Obtaining the operation fault information according to the first fault information and the third fault information.

3. The method according to claim 1, characterized in that, The parsing of the target fault data to obtain a to-be-processed fault configuration code corresponding to the fault data includes: Parsing the target fault data by using the BASE function to obtain a to-be-processed fault configuration code corresponding to the target fault data.

4. The method according to claim 3, characterized in that, Before determining the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code, the method further includes: Padding the to-be-processed fault configuration code by using the PEPT function.

5. The method according to claim 2, characterized in that, The determining of the vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code includes: Performing a bit-by-bit extraction operation on the to-be-processed fault configuration code by using the MID function to obtain fault bits in a first order; the number of the fault bits is the same as the number of bits of the to-be-processed fault configuration code; Performing a reverse order operation on the fault bits in the first order by using the INDEX function to obtain fault bits in a second order, where the second order is opposite to the first order; Determining the vehicle fault according to the values of the fault bits in the second order and the fault types corresponding to the fault bits in the second order.

6. A device for processing fault data, characterized in that, The device includes: A first obtaining unit, configured to obtain the operation fault information of the whole vehicle; A grouping unit, configured to group the operation fault information according to the fault type to obtain at least one group of operation fault codes; A first calculation unit, configured to perform a number system conversion on the operation fault codes to obtain fault configuration codes, where the fault configuration codes include the information of the faults of the whole vehicle, and the number of characters of the fault configuration codes is less than the number of characters of the operation fault codes; A second calculation unit, configured to select a target fault configuration code from the fault configuration codes, convert the target fault configuration code into a target base form; obtain a standard configuration code in the target base form corresponding to the target fault configuration code; perform an AND calculation on the target fault configuration code and the standard configuration code to obtain fault data, where the target fault configuration code includes a fault problem, the standard configuration code is preset and used to screen the fault types to be analyzed, the fault data is used to reflect the fault information included in the target fault configuration code, and the fault data is used to reversely analyze to obtain specific fault types; A parsing unit, configured to parse the fault data to obtain a to-be-processed fault configuration code corresponding to the fault data; A determination unit, configured to determine a vehicle fault according to the fault type corresponding to the to-be-processed fault configuration code.

7. A device for processing fault data, characterized in that, Comprising: A processor, a memory, and a system bus; The processor and the memory are connected through the system bus; The memory is used to store one or more programs, the one or more programs include instructions, and when the instructions are executed by the processor, the processor executes the fault data processing method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, Instructions are stored in the computer-readable storage medium, and when the instructions run on a terminal device, the terminal device executes the fault data processing method according to any one of claims 1-5.

Images