Vehicle fault reason determination method and device and computer storage medium

Abstract

The invention discloses a vehicle fault cause determination method and device and a computer storage medium. The method comprises the steps that in response to a received fault generation instruction, target fault information is determined according to the fault generation instruction, and the target fault information comprises a fault phenomenon and a preset fault reason corresponding to the fault phenomenon; matching a target fault mechanism from a preset fault knowledge base according to the fault phenomenon; and determining the target fault reason of the vehicle according to the target fault mechanism and the preset fault reason corresponding to the fault phenomenon. Therefore, the efficiency of determining the fault reason can be improved.

Description

Technical Field

[0001] This application relates to the technical field of fault diagnosis, and in particular to a method and device for determining the cause of a vehicle fault and a computer storage medium. Background Art

[0002] Electric vehicles use power batteries as the energy and power source, which is crucial for the development of electric vehicles. Due to the complex composition of power batteries, it is difficult to detect the specific cause of a fault if a fault occurs in the power battery.

[0003] Currently, manual troubleshooting is used to check each power battery one by one to determine the cause of the fault, but the efficiency of this method for determining the cause of the fault is low. Summary of the Invention

[0004] To solve the above problems, this application provides a method and device for determining the cause of a vehicle fault and a computer storage medium, which can improve the efficiency of determining the cause of the fault.

[0005] To solve the above problems, this application provides a method for determining the cause of a vehicle fault. The method for determining the cause of a vehicle fault includes: in response to receiving a fault occurrence instruction, determining target fault information according to the fault occurrence instruction, where the target fault information includes a fault phenomenon and a preset fault cause corresponding to the fault phenomenon; matching a target fault mechanism from a preset fault knowledge base according to the fault phenomenon; and determining the target fault cause of the vehicle according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon.

[0006] In some embodiments, the fault phenomenon includes a general fault information and a fault warning information. The step of matching a target fault mechanism from a preset fault knowledge base according to the fault phenomenon includes: matching a target general fault information from the preset fault knowledge base according to the general fault information; matching a target fault type from the preset fault types corresponding to the target general fault information in the preset fault knowledge base according to the fault warning information; and determining the fault mechanism corresponding to the target fault type as the target fault mechanism.

[0007] In some embodiments, the fault phenomenon includes a general fault information. The step of matching a target fault mechanism from a preset fault knowledge base according to the fault phenomenon includes: matching a target general fault information from the preset fault knowledge base according to the general fault information; and determining the preset fault mechanism corresponding to the target general fault in the preset fault knowledge base as the target fault mechanism.

[0008] In some embodiments, the step of determining the target fault cause of the vehicle according to the preset fault causes corresponding to the target fault mechanism and the fault phenomenon includes: obtaining the preset fault cause corresponding to the target fault mechanism; determining the same fault cause between the preset fault cause corresponding to the fault phenomenon and the preset fault cause corresponding to the target fault mechanism as the target fault cause of the vehicle.

[0009] In some embodiments, the step of determining the target fault cause of the vehicle according to the preset fault causes corresponding to the target fault mechanism and the fault phenomenon includes: obtaining the preset fault cause corresponding to the target fault mechanism; in response to there being at least two same fault causes between the preset fault cause corresponding to the fault phenomenon and the preset fault cause corresponding to the target fault mechanism, determining the target fault cause of the vehicle according to the historical fault times of each same fault cause.

[0010] In some embodiments, the step of determining the target fault cause of the vehicle according to the historical fault times of each same fault cause includes: performing a sorting process on the historical fault times of each same fault cause to obtain a fault cause sequence; determining the fault cause at a preset sequence position in the fault cause sequence as the target fault cause.

[0011] In some embodiments, the step of obtaining the preset fault cause corresponding to the target fault mechanism includes: performing a matching process between the target fault mechanism and the preset fault causes in a preset fault information database to obtain a matching result; determining the fault cause in the matching result that represents the fault cause in the preset fault information database matching the target fault mechanism as the preset fault cause corresponding to the target fault mechanism.

[0012] In some embodiments, the step of determining the target fault information according to the fault occurrence instruction includes: analyzing and processing the vehicle data in the fault occurrence instruction to obtain an analysis result; determining the target fault information from the preset fault information database according to the analysis result.

[0013] To solve the above problems, the present application provides an electronic device, including: a processor and a memory, where a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the above method.

[0014] To solve the above problems, the present application provides a computer-readable storage medium, on which program instructions are stored, and when the program instructions are executed by a processor, the above method is implemented.

[0015] In the technical solution provided by the embodiment of the present application, in response to receiving a fault occurrence instruction, target fault information is determined according to the fault occurrence instruction, and the target fault information includes a fault phenomenon and a preset fault cause corresponding to the fault phenomenon; a target fault mechanism is matched from a preset fault knowledge base according to the fault phenomenon; and a target fault cause of the vehicle is determined according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon. Thus, a target fault mechanism can be matched from a preset fault knowledge base according to the fault phenomenon, and then the target fault cause can be determined according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon, realizing automatic detection of the target fault cause. Moreover, on the basis of improving the determination efficiency of the target fault cause, the determination accuracy of the target fault cause can also be improved.

[0016] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the embodiments. Obviously, the following described drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0018] Figure 1 is a flowchart of a method for determining a vehicle fault cause shown in an exemplary embodiment of the present application;

[0019] Figure 2 is a schematic diagram of a preset fault information library shown in an exemplary embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a preset fault knowledge base shown in an exemplary embodiment of the present application;

[0021] Figure 4 is a flowchart of an exemplary embodiment of the step of obtaining a preset fault cause corresponding to a target fault mechanism in the present application;

[0022] Figure 5 is Figure 4 a schematic diagram of the matching relationship between the preset fault mechanism and the preset fault cause in the preset fault information library shown;

[0023] Figure 6 is a schematic diagram of the structure of an electronic device according to an embodiment of the present application;

[0024] Figure 7 is a schematic diagram of the structure of a computer storage medium according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0025] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be specifically noted that the following embodiments are only used to illustrate the present application, but do not limit the scope of the present application. Similarly, the following embodiments are only partial embodiments of the present application rather than all embodiments. All other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present application.

[0026] Referring to "embodiments" herein means that specific features, structures, or characteristics described in conjunction with the embodiments can be included in at least one embodiment of the present application. The phrase appearing at various positions in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0027] The present application proposes a method for determining the cause of a vehicle failure, which can be applied to a vehicle. When a vehicle fails, the efficiency of determining the cause of the failure can be improved through the method for determining the cause of the vehicle failure of the present application. Specifically, please refer to Figure 1 , Figure 1 which is a flowchart showing the method for determining the cause of a vehicle failure shown in an exemplary embodiment of the present application.

[0028] Among them, the execution subject of the method for determining the cause of a vehicle failure can be a terminal device, a server, or other processing devices. Among them, the terminal device can be a user equipment (UE), a computer, a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, etc. The execution subject of the method for determining the cause of a vehicle failure can also be a vehicle control system. In some possible implementation manners, the vehicle failure method can be implemented by a processor calling computer-readable instructions stored in a memory.

[0029] The method for determining the cause of a vehicle failure in the embodiments of the present application will be described below with the vehicle control system as the execution subject. Specifically, the method for determining the cause of a vehicle failure in this embodiment includes the following steps:

[0030] Step S110: In response to receiving a fault occurrence instruction, determine target fault information according to the fault occurrence instruction. The target fault information includes a fault phenomenon and a preset fault cause corresponding to the fault phenomenon.

[0031] The fault occurrence instruction can be a trigger instruction received by the vehicle control system for fault cause detection when the vehicle fails.

[0032] As an example, the target fault information may include a fault symptom and a preset fault cause corresponding to the fault symptom. The fault symptom may be a vehicle symptom when a vehicle fault occurs. For example, the battery power system cannot work properly, the power supply of the battery power system is discontinuous, etc. The preset fault cause corresponding to the fault symptom may be preset manually or determined by the vehicle control system according to historical fault causes. For example, the preset fault cause may be insufficient battery power, the battery service life reaches the replacement condition, or the battery is damaged, etc. As another example, the target fault information may further include at least one of vehicle information, battery pack information, and a fault repair strategy.

[0033] The vehicle control system receives a fault occurrence instruction and analyzes the fault occurrence instruction to determine the target fault information. As an example, the vehicle control system analyzes and processes the vehicle data in the fault occurrence instruction to obtain an analysis result. The analysis result includes a fault analysis report. The fault analysis report is subjected to feature extraction processing to obtain feature vectors, and the target fault information is determined according to the similarity between each feature vector and a preset feature vector. As another example, the vehicle control system analyzes and processes the vehicle data in the fault occurrence instruction to obtain an analysis result. The analysis result includes current vehicle information, current battery pack information, and current fault symptoms. The target fault information is determined from a preset fault information database according to the analysis result. Specifically, the vehicle control system determines vehicle information, battery pack information, fault symptoms, fault causes, and a fault recovery strategy with a corresponding relationship from the preset fault information database according to the current vehicle information, current battery pack information, and current fault symptoms.

[0034] It should be noted that the preset fault information database can be understood as a fault case database. Refer to Figure 2 , Figure 2 FIG. is a schematic diagram of a preset fault information database shown in an exemplary embodiment of the present application. The preset fault information database includes at least two fault cases. In each fault case, there is a corresponding vehicle information, battery pack information, fault symptom, fault cause, and fault recovery strategy. For the construction of the fault case database, the vehicle control system uses the historical faults as fault cases, obtains the fault information of the historical faults, and constructs the fault information of the historical faults into a fault case database. The fault information of the historical faults includes vehicle information, battery pack information, fault symptoms, fault causes, and fault recovery strategy of the vehicle where the historical fault occurred, etc.

[0035] Step S120: Match the target fault mechanism from the preset fault knowledge base according to the fault symptom.

[0036] As an example, the preset fault knowledge base includes preset fault phenomena and corresponding preset fault causes. As another example, the preset fault knowledge base may include preset general fault information and preset fault mechanisms, where each piece of preset general fault information corresponds to at least one preset fault mechanism. As yet another example, the preset fault knowledge base may further include preset general fault information, preset fault types, and preset fault mechanisms, where each piece of preset general fault information corresponds to at least one preset fault type, and each preset fault type corresponds to at least one preset fault mechanism.

[0037] The target fault mechanism refers to at least one fault mechanism in the preset fault knowledge base. A fault mechanism refers to the relevant principles involved when a vehicle has a fault, and the fault mechanism helps to identify and solve vehicle faults.

[0038] As an example, if the preset fault knowledge base includes preset fault phenomena and corresponding preset fault causes, the vehicle control system can perform a matching process between the fault phenomenon and the preset fault phenomena in the preset fault knowledge base to determine the target fault phenomenon; and determine the preset fault mechanism corresponding to the target fault phenomenon in the preset fault knowledge base as the target fault mechanism.

[0039] As another example, refer to Figure 3 , Figure 3 is a schematic diagram of the preset fault knowledge base shown in an exemplary embodiment of the present application. If the preset fault knowledge base includes preset general fault information and preset fault mechanisms, and the fault phenomenon includes general fault information, the vehicle control system can perform a matching process between the general fault information in the fault phenomenon and the preset general fault information in the preset fault knowledge base to determine the target general fault information. The general fault information may be the name of the monitored parameter of the battery power system. Exemplarily, the general fault information may be abnormal battery power system voltage. Another exemplarily, the general fault information may be abnormal battery power system temperature. Further, the vehicle control system classifies the fault phenomenon into multiple different pieces of preset general fault information, and each piece of preset general fault information corresponds to a preset fault cause set by humans or determined by the vehicle control system according to historical fault causes. The vehicle control system matches according to the general fault information and the preset general fault information in the preset fault knowledge base, determines the same general fault information obtained by the matching of the two as the target general fault information, and determines the preset fault mechanism corresponding to the target general fault information as the target fault mechanism.

[0040] As another example, if the preset fault knowledge base can include preset general fault information, preset fault types, and preset fault mechanisms, the vehicle control system can first match the general fault information in the fault phenomenon with the preset general fault information in the preset fault knowledge base to determine the target general fault information. The fault phenomenon may also include fault warning information, which can be understood as a further classification of the general fault information in the fault phenomenon. Exemplarily, if the target general fault information is a battery power system voltage fault, the fault warning information can be that the battery power system voltage exceeds the threshold, the battery power system voltage is lower than the threshold, or it can be that the battery power system voltage difference exceeds or is lower than the threshold. As another example, if the general fault information is an abnormal temperature of the battery power system, the fault warning information can be that the battery power system temperature exceeds the threshold or the battery power system temperature is lower than the threshold. After the vehicle control system determines the target general fault information, it can also match the fault warning information with the preset fault types corresponding to the target general fault information in the preset fault knowledge base to match the target fault type corresponding to the fault warning information. Each preset fault type corresponds to at least one preset fault mechanism. After matching the target fault type, the preset fault mechanism corresponding to the target fault type can be determined as the target fault mechanism.

[0041] Step S130: Determine the target fault cause of the vehicle according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon.

[0042] The vehicle control system combines the preset fault information base and the preset fault knowledge base to determine the target fault cause. Specifically, according to the matching between the target fault mechanism matched from the preset fault knowledge base and the preset fault cause corresponding to the fault phenomenon in the preset fault information base, the preset fault cause corresponding to the fault phenomenon and the fault cause corresponding to the fault mechanism are determined as the target fault cause.

[0043] As an example, the vehicle control system can first obtain the preset fault cause corresponding to the target fault mechanism, and determine the target fault cause of the vehicle according to the preset fault cause corresponding to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon. Specifically, after the vehicle control system obtains the preset fault cause corresponding to the target fault mechanism, the same preset fault causes between the preset fault cause corresponding to the fault phenomenon and the preset fault cause corresponding to the target fault mechanism are determined as the target fault cause.

[0044] As another example, the vehicle control system may first obtain the preset fault causes corresponding to the target fault mechanism, and determine the target fault cause according to at least two identical fault causes existing between the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon. Specifically, after the vehicle controller obtains the preset fault causes corresponding to the target fault mechanism, it matches the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon. If there are at least two identical fault causes between the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon, the historical fault times of the identical fault causes obtained by matching in the preset fault information library are first sorted. That is to say, the vehicle control system counts the number of vehicle faults that occur due to the same preset fault cause in the preset fault information library. Since the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon are matched, at least two identical fault causes between the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon can be sorted to obtain a fault cause sequence. Exemplarily, the number of times of the same fault cause can be sorted in descending order, and at least the first few positions in the fault cause sequence can be used as the preset positions, so as to determine the fault cause at the preset position as the target fault cause.

[0045] As another example, the vehicle control system may first obtain the preset fault causes corresponding to the target fault mechanism, and determine the target fault cause of the vehicle according to the fault probabilities of at least two identical fault causes existing between the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon. The preset fault knowledge base includes preset fault general information, preset fault types, and preset fault mechanisms. The vehicle control system may use the preset fault general information as the top event, the preset fault types as the intermediate events, and the preset fault mechanisms as the bottom events. It also makes statistics based on the fault phenomena of the historical fault cases occurring in the preset fault information database and the number of preset fault causes corresponding to the fault phenomena. The number of fault phenomena may include the number of pieces of fault general information and the number of pieces of fault warning information, and the accumulated number of pieces of fault general information, fault warning information, and preset fault causes corresponding to the fault phenomena obtained from the statistics may be respectively corresponded to the accumulated number of pieces of preset fault general information, preset fault types, and preset fault mechanisms in the preset fault knowledge base. After the vehicle control system obtains the preset fault causes corresponding to the target fault mechanism, if there are at least two identical fault causes between the preset fault causes corresponding to the target fault mechanism and the preset fault causes corresponding to the fault phenomenon, it first calculates the percentage of the accumulated number of pieces of the target fault mechanism corresponding to the identical fault cause to the accumulated number of pieces of the target fault type corresponding to the target fault mechanism or the accumulated number of pieces of the target fault general information corresponding to the target fault mechanism to obtain the fault probabilities of each identical fault cause. Furthermore, the vehicle control system may determine the target fault cause according to the fault probabilities of each identical fault cause, and may use the fault cause with a higher fault probability as the target fault cause.

[0046] It can be seen that the vehicle fault cause determination method according to the embodiment of the present application responds to receiving a fault occurrence instruction, determines target fault information according to the fault occurrence instruction, where the target fault information includes a fault phenomenon and the preset fault cause corresponding to the fault phenomenon; matches the target fault mechanism from the preset fault knowledge base according to the fault phenomenon; and determines the target fault cause of the vehicle according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon. Thus, it is possible to match the target fault mechanism from the preset fault knowledge base according to the fault phenomenon, and then determine the target fault cause according to the target fault mechanism and the preset fault cause corresponding to the fault phenomenon, realizing the automatic detection of the target fault cause. Moreover, on the basis of improving the efficiency of determining the target fault cause, the accuracy of determining the target fault cause can also be improved.

[0047] On the basis of the above embodiments, the embodiments of the present application further elaborate on how to improve the accuracy of obtaining the preset fault causes corresponding to the fault mechanism. Refer to Figure 4 and Figure 5 , Figure 4 is a schematic flowchart of an exemplary embodiment of the step of obtaining the preset fault causes corresponding to the target fault mechanism in the present application.Figure 5 Yes Figure 4 It is a schematic diagram of the matching relationship between the preset fault mechanism and the preset fault causes in the preset fault information library. Specifically, the steps of obtaining the preset fault causes corresponding to the target fault mechanism may further include the following steps:

[0048] Step S210: Perform a matching process on the target fault mechanism and the preset fault causes in the preset fault information library to obtain a matching result.

[0049] The matching result refers to the result obtained by the vehicle control system matching the target fault mechanism with the preset fault causes in the preset fault information library. The matching result may include exact match, high similarity match, and low similarity match, etc.

[0050] As an example, the vehicle control system can standardize the description format of the preset fault mechanism. Specifically, the vehicle control system can describe the preset fault mechanism as "component + location + preset fault cause", and also standardize the description format of the preset fault causes corresponding to the fault phenomena in the same way, so as to match the description format of the target fault mechanism with the description format of the preset fault causes corresponding to the fault phenomena in the preset fault information library. There can be three matching results: exact match, high similarity match, and low similarity match. Specifically, the text similarity of the description format of the preset fault mechanism and the description format of the preset fault causes corresponding to the fault phenomena can be calculated respectively. The two description texts with a similarity of 1 are determined as an exact match, the two description texts with a similarity in the range of 0.7 - 0.99 are determined as a high similarity match, and the two description texts with a similarity lower than 0.7 are determined as a low similarity match. Of course, the similarity ranges corresponding to the three matching results are not limited to the above examples, and the similarity corresponding to the three matching results can be adjusted according to the actual situation. The matching results are not limited to the above examples either. For example, there can be four matching results: exact match, high similarity match, partial match, and low similarity match. When performing the matching, the description text of the preset fault cause in the description format can be preferentially matched, and the weight of the description text of the preset fault cause can be appropriately increased. Then, when the matching result is an exact match or a high similarity match, it indicates that the preset fault cause corresponding to the fault phenomenon in the preset fault information library has a preset fault cause that matches the target fault mechanism, which is more conducive to matching the same fault cause.

[0051] As another example, the vehicle control system standardizes the description formats of the preset fault causes corresponding to the fault mechanisms and fault phenomena in the same way, specifically as "component + location + preset fault cause". When the description format of the target fault mechanism is matched with the description format of the preset fault cause corresponding to the fault phenomenon in the preset fault information database, the target fault type and the target fault general information corresponding to the target fault mechanism can also be matched with the fault general information and fault warning information in the preset fault information database, which can reduce the risk that when a target fault mechanism corresponds to at least two fault types, the preset fault cause in the preset fault information database that is not the target fault type is matched to the target fault mechanism. Furthermore, the accuracy of matching the fault mechanism with the preset fault cause in the preset fault information database can be improved.

[0052] Step S220: Determine the fault cause in the preset fault information database that matches the target fault mechanism in the matching result as the preset fault cause corresponding to the target fault mechanism.

[0053] After the vehicle control system matches the target fault mechanism with the preset fault cause in the preset fault information database and obtains the matching result. The vehicle control system determines the preset fault cause in the preset fault information database that matches the target fault mechanism as the preset fault cause corresponding to the target fault mechanism.

[0054] It can be seen that the vehicle fault cause determination method in the embodiment of the present application matches the target fault mechanism with the preset fault cause in the preset fault information database to obtain the matching result; determines the fault cause in the matching result that represents the preset fault cause in the preset fault information database that matches the target fault mechanism as the preset fault cause corresponding to the target fault mechanism. It can accurately match the target fault mechanism with the preset fault cause in the preset fault information database, reduce the same fault causes between the preset fault cause corresponding to the fault mechanism and the preset fault cause corresponding to the fault phenomenon, and improve the accuracy of determining the target fault cause.

[0055] The above method is applied to an electronic device. For details, please refer to Figure 6 , Figure 6 is a schematic structural diagram of an embodiment of the electronic device of the present application. The electronic device 80 in this embodiment includes a processor 81 and a memory 82. Among them, a computer program is stored in the memory 82, and the processor 81 is used to execute the computer program to implement the above vehicle fault cause determination method.

[0056] Among them, the processor 81 can be an integrated circuit chip with the ability to process signals. The processor 81 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0057] For the vehicle fault cause determination method of the above embodiment, it can be presented in the form of a computer program. The present application proposes a computer storage medium carrying the computer program. Please refer to Figure 7 , Figure 7 is a schematic structural diagram of an embodiment of the computer storage medium of the present application. The computer storage medium 90 of this embodiment includes a computer program 91, which can be executed to implement the above vehicle displayable range prediction method.

[0058] The computer storage medium 90 of this embodiment can be a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc, etc., which can store program instructions, or it can also be a server storing the program instructions. The server can send the stored program instructions to other devices for running, or it can also run the stored program instructions by itself.

[0059] If the technical solution of the present application involves personal information, before the product applying the technical solution of the present application processes personal information, it has clearly informed the personal information processing rules and obtained the personal's autonomous consent. If the technical solution of the present application involves sensitive personal information, before the product applying the technical solution of the present application processes sensitive personal information, it has obtained the personal's separate consent and at the same time meets the requirement of "express consent". For example, at a personal information collection device such as a camera, a clear and prominent sign is set to inform that the personal information collection range has been entered and personal information will be collected. If the personal voluntarily enters the collection range, it is regarded as consenting to the collection of their personal information; or on the personal information processing device, when the personal information processing rules are informed by obvious signs / information, personal authorization is obtained through pop-up information or asking the personal to upload their personal information by themselves, etc.; among them, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

[0060] In addition, when the above functions are implemented in the form of software functions and sold or used as independent products, they can be stored in a storage medium readable by a mobile terminal. That is, the present application also provides a storage device storing program data, and the program data can be executed to implement the methods of the above embodiments. The storage device can be, for example, a USB flash drive, an optical disc, a server, etc. That is to say, the present application can be embodied in the form of a software product, which includes several instructions for causing an intelligent terminal to execute all or part of the steps of the methods described in the various embodiments.

[0061] In the description of the present application, the descriptions referring to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples. In addition, without conflict, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0062] Furthermore, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0063] Any process or method description in the flowchart or described in other ways herein can be understood as representing a module, segment, or part of code including one or more executable instructions for implementing a specific logical function or process. The scope of the preferred embodiments of the present application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in the reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present application belong.

[0064] The logic and / or steps represented in the flowchart or otherwise described herein can be considered, for example, a definitional sequence list of executable instructions for implementing a logical function, which can be embodied in any computer-readable medium for use by an instruction execution system, apparatus, or device (which can be a personal computer, server, network device, or other system that can fetch and execute instructions from the instruction execution system, apparatus, or device), or used in conjunction with these instruction execution systems, apparatuses, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or otherwise processing as appropriate, and then stored in a computer memory.

[0065] The above are only the embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A method for determining the cause of a vehicle fault, characterized in that, The method for determining the cause of vehicle failure includes: In response to receiving a failure occurrence instruction, determining target failure information according to the failure occurrence instruction, where the target failure information includes a failure phenomenon and a preset failure cause corresponding to the failure phenomenon; Matching a target failure mechanism from a preset failure knowledge base according to the failure phenomenon; Determining the target failure cause of the vehicle according to the target failure mechanism and the preset failure cause corresponding to the failure phenomenon.

2. The vehicle fault cause determination method according to claim 1, wherein The failure phenomenon includes failure general information and failure warning information. The step of matching a target failure mechanism from a preset failure knowledge base according to the failure phenomenon includes: Matching target failure general information from the preset failure knowledge base according to the failure general information; Matching a target failure type from the preset failure types corresponding to the target failure general information in the preset failure knowledge base according to the failure warning information; Determining the failure mechanism corresponding to the target failure type as the target failure mechanism.

3. The vehicle fault cause determination method according to claim 1, characterized in that The failure phenomenon includes failure general information. The step of matching a target failure mechanism from a preset failure knowledge base according to the failure phenomenon includes: Matching target failure general information from the preset failure knowledge base according to the failure general information; Determining the preset failure mechanism corresponding to the target failure general in the preset failure knowledge base as the target failure mechanism.

4. The method for determining the cause of a vehicle fault according to claim 1, wherein The step of determining the target failure cause of the vehicle according to the target failure mechanism and the preset failure cause corresponding to the failure phenomenon includes: Obtaining the preset failure cause corresponding to the target failure mechanism; Determining the same failure cause between the preset failure cause corresponding to the failure phenomenon and the preset failure cause corresponding to the target failure mechanism as the target failure cause of the vehicle.

5. The method for determining the cause of a vehicle fault according to claim 1, wherein, The step of determining the target failure cause of the vehicle according to the target failure mechanism and the preset failure cause corresponding to the failure phenomenon includes: Obtaining the preset failure cause corresponding to the target failure mechanism; In response to there being at least two same failure causes between the preset failure cause corresponding to the failure phenomenon and the preset failure cause corresponding to the target failure mechanism, determining the target failure cause of the vehicle according to the historical failure times of each same failure cause.

6. The method for determining the cause of a vehicle fault according to claim 5, wherein The step of determining the target failure cause of the vehicle according to the historical failure times of each same failure cause includes: Performing a sorting process on the historical failure times of each same failure cause to obtain a failure cause sequence; Determining the failure cause at a preset order position in the failure cause sequence as the target failure cause.

7. The method for determining the cause of a vehicle fault according to claim 5, characterized in that, The step of obtaining the preset failure cause corresponding to the target failure mechanism includes: Performing a matching process on the target failure mechanism and the preset failure causes in a preset failure information library to obtain a matching result; Determining the failure cause representing the matching between the preset failure information library and the target failure mechanism in the matching result as the preset failure cause corresponding to the target failure mechanism.

8. The method for determining the cause of a vehicle fault according to claim 1, characterized in that, The step of determining target failure information according to the failure occurrence instruction includes: Analyzing and processing the vehicle data in the failure occurrence instruction to obtain an analysis result; Determine the target fault information from a preset fault information database according to the analysis result.

9. An electronic device, characterized in that, Including: A processor and a memory, wherein a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method according to any one of claims 1 to 8.

10. A computer-readable storage medium having program instructions stored thereon, characterized in that, When the program instructions are executed by the processor, the method according to any one of claims 1 to 8 is implemented.

Images