CN117520024A

CN117520024A - Method and device for processing fault data and vehicle

Info

Publication number: CN117520024A
Application number: CN202210909861.6A
Authority: CN
Inventors: 陈二伟; 李旭升; 刘山山; 刘卓
Original assignee: Great Wall Motor Co Ltd
Current assignee: Great Wall Motor Co Ltd
Priority date: 2022-07-29
Filing date: 2022-07-29
Publication date: 2024-02-06

Abstract

The embodiment of the application provides a method and device for processing fault data and a vehicle. Specifically, the failure phenomenon data may be acquired first. Then, a plurality of fault cause events that may cause the fault event may be determined according to the fault event data and the first correspondence. After the candidate fault cause event set is determined, historical fault cause data may be obtained, and a target fault cause event may be determined from the candidate fault cause event set based on the historical fault cause data. The historical fault reason data are used for indicating the fault reason of the target vehicle in the historical preset time. In this way, the correspondence between the fault event and the fault cause event is determined in combination with the structure inside the target vehicle, and the fault cause event of the target vehicle occurring in the near future can be determined, so that the fault cause event having the highest probability of causing the fault event of the target vehicle can be determined.

Description

Method and device for processing fault data and vehicle

Technical Field

The present disclosure relates to the field of automotive technologies, and in particular, to a method and an apparatus for processing fault data, and a vehicle.

Background

With the progress of vehicle intellectualization, the functions that vehicles can realize are increasing. Accordingly, the number of components on the vehicle is increasing. If these components are operating properly, the vehicle can perform the corresponding functions. If the component fails and cannot normally operate, the vehicle may not realize functions related to the failed component, and may even affect normal running of the vehicle. Therefore, whether each component on the vehicle has faults or not needs to be timely judged, so that timely repair is carried out.

For this reason, most of the current vehicles are deployed with a detection mechanism for detecting the failure condition of the components. For example, to determine whether a vehicle engine is operating properly, a sensor may be deployed on the vehicle engine for monitoring the operating state of the engine. In order to determine whether the vehicle can communicate with the outside, signal transmission between an on-board computer and an on-board remote communicator (T-BOX) is possible. If the two signals cannot be normally transmitted, the communication function between the vehicle and the outside is influenced.

However, most of the conventional detection mechanisms detect by sensors. Often only a fault is detected. On this basis, a technician or expert is required to determine the cause of the fault by performing test analysis on the vehicle. Therefore, the traditional fault detection method has the problems of low fault detection efficiency and poor detection effect.

Disclosure of Invention

In view of this, the embodiments of the present application provide a method, an apparatus, and a vehicle for processing fault data, which aim to determine a cause that has a highest probability of causing a fault in a target vehicle.

In a first aspect, an embodiment of the present application provides a method for processing fault data, the method including:

acquiring fault phenomenon data, wherein the fault phenomenon data are used for indicating fault phenomenon events of a target vehicle;

determining a candidate fault cause event set according to the fault phenomenon data and a first corresponding relation, wherein the first corresponding relation is used for describing causal relation between a fault phenomenon event and a fault cause event, the candidate fault cause event set comprises at least one candidate fault cause event, and the fault cause event has the capacity of causing the fault phenomenon event to occur;

acquiring historical fault reason data, wherein the historical fault data are used for indicating fault reason events of the target vehicle in a historical preset time period;

and determining a target fault cause event according to the historical fault cause data and the candidate fault cause event set, wherein the probability of occurrence of the fault event caused by the target fault cause event is higher than that of occurrence of the fault event caused by a non-target fault cause event in the candidate fault cause event set.

In some possible implementations, the method further includes:

determining an early warning fault event set according to the target fault cause event and the first corresponding relation, wherein the early warning fault event set comprises at least one early warning fault event, and the fault cause event has the capability of triggering the early warning fault event;

and pre-warning each pre-warning fault event in the pre-warning fault event set.

In some possible implementations, the pre-warning each pre-warning fault event in the set of pre-warning fault event events includes:

generating alarm information according to the early warning fault phenomenon event;

and displaying the alarm information on the target vehicle.

In some possible implementations, the method further includes:

establishing a connection between the target vehicle and a maintenance diagnostic system;

and sending the fault phenomenon data and the information of the target fault cause event to the maintenance diagnosis system so that the maintenance diagnosis system can generate a diagnosis report according to the fault phenomenon data and the information of the target fault cause event.

In some possible implementations, the method further includes:

uploading the information of the fault event and the information of the target fault cause event through the Internet, wherein the information of the fault event data and the information of the fault cause event are used for updating the first corresponding relation.

In a second aspect, an embodiment of the present application provides an apparatus for processing fault data, where the apparatus includes:

the system comprises an acquisition unit, a control unit and a control unit, wherein the acquisition unit is used for acquiring fault phenomenon data, and the fault phenomenon data are used for indicating fault phenomenon events of a target vehicle;

the processing unit is used for determining a candidate fault cause event set according to the fault phenomenon data and a first corresponding relation, wherein the first corresponding relation is used for describing causal relation between fault event and fault cause event, the candidate fault cause event set comprises at least one candidate fault cause event, and the fault cause event has the capacity of causing the fault event to occur;

the acquisition unit is further used for acquiring historical fault reason data, wherein the historical fault data are used for indicating fault reason events of the target vehicle in a historical preset time period;

the processing unit is further configured to determine a target fault cause event according to the historical fault cause data and the candidate fault cause event set, where the probability that the target fault cause event causes the fault event is higher than the probability that a non-target fault cause event in the candidate fault cause event set causes the fault event.

In some possible implementations, the processing unit is configured to determine an early warning failure event set according to the target failure cause event and the first correspondence, where the early warning failure event set includes at least one early warning failure event, and the failure cause event has a capability of triggering the occurrence of the early warning failure event; and pre-warning each pre-warning fault event in the pre-warning fault event set.

In some possible implementations, the processing unit is specifically configured to generate alarm information according to the early warning fault event; and displaying the alarm information on the target vehicle.

In some possible implementations, the apparatus further includes a transmitting unit;

the processing unit is specifically used for establishing connection between the target vehicle and a maintenance diagnosis system;

the sending unit is used for sending the fault phenomenon data and the information of the target fault cause event to the maintenance diagnosis system so that the maintenance diagnosis system can generate a diagnosis report according to the fault phenomenon data and the information of the target fault cause event.

In some possible implementations, the sending unit is further configured to upload, through the internet, the information of the failure event and the information of the target failure cause event, where the information of the failure event data and the information of the failure cause event are used to update the first correspondence.

In a third aspect, embodiments of the present application provide an apparatus, the apparatus comprising a memory for storing instructions or code, and a processor for executing the instructions or code to cause the apparatus to perform the method of processing fault data according to any one of the preceding first aspects.

In a fourth aspect, embodiments of the present application provide a computer storage medium having code stored therein, which when executed, implements a method of processing fault data as in any of the preceding first aspects.

In a fifth aspect, embodiments of the present application provide a vehicle including a processor configured to implement the method for processing fault data according to any one of the first aspect.

The embodiment of the application provides a method and device for processing fault data and a vehicle, wherein the method can be used for determining a fault cause event which causes a fault event to occur on a target vehicle. Specifically, failure event data may be first obtained, where the failure event data is used to identify a failure event that occurs with the target vehicle. Then, a plurality of fault cause events that may cause the fault event may be determined according to the fault event data and the first correspondence. The set of multiple fault cause events is referred to as a candidate fault cause event set. After the candidate fault cause event set is determined, historical fault cause data may be obtained, and a target fault cause event may be determined from the candidate fault cause event set based on the historical fault cause data. The historical fault reason data are used for indicating the fault reason of the target vehicle in the historical preset time. The target fault cause event determined by the method is a fault cause event which occurs recently and can cause the target vehicle to generate a fault event. In this way, the correspondence between the fault event and the fault cause event is determined in combination with the structure inside the target vehicle, and the fault cause event of the target vehicle occurring in the near future can be determined, so that the fault cause event having the highest probability of causing the fault event of the target vehicle can be determined. Thus, the automatic diagnosis of the fault event of the target vehicle is realized, and the probability that the obtained fault cause event is the actual fault of the target vehicle is high.

Drawings

In order to more clearly illustrate the present embodiments or the technical solutions in the prior art, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method for processing fault data according to an embodiment of the present application;

FIG. 2 is a schematic structural diagram of an apparatus for processing fault data according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of a vehicle according to an embodiment of the present application.

Detailed Description

To monitor the operation of a vehicle, it is currently possible to deploy sensors on the vehicle and detection programs on the vehicle controller. Therefore, after a fault event occurs to the vehicle, the monitoring mechanism can timely discover the fault of the vehicle, so that a driver is reminded of paying attention, and reference advice can be provided for technicians when the vehicle is overhauled.

For example. At present, a monitoring mechanism can be deployed on a vehicle-mounted computer and used for detecting the communication condition of the vehicle-mounted computer and a vehicle-mounted T-box. For example, the vehicle-mounted computer can periodically send a heartbeat message to the vehicle-mounted T-box, and judge whether the communication between the vehicle-mounted approximate calculation and the vehicle-mounted T-box is normal or not according to the condition that the vehicle-mounted T-box receives the heartbeat message.

However, with respect to a part of the devices or systems on the vehicle, such as the wireless communication apparatus of the vehicle, the structure thereof may be complicated, only the occurrence of the failure may be found by the sensor or the detection program, and the specific cause of the occurrence of the failure may not be determined. That is, the conventional monitoring method can only monitor the appearance of the fault, and cannot determine why the fault occurs. In this way, when the vehicle is troubleshooted, only a technician can manually check the vehicle's travel log to analyze the cause of the vehicle failure. Clearly, the above process has the disadvantages of low efficiency and long time consumption.

The description is given along with the above examples. Abnormalities in the communication of the onboard computer with the onboard T-box may be caused for a number of reasons. For example, a problem with the ethernet module on the vehicle may cause the vehicle computer to fail to interact with the vehicle T-box, e.g., an open ethernet signal, a short ethernet signal, or an ethernet signal may cause the vehicle computer to fail to interact with the vehicle T-box. In addition, if the extensible service-oriented middleware protocol (SOMEIP) process based on the Internet protocol (Internet Protocol, IP) is closed in the in-vehicle computer, the in-vehicle computer cannot communicate with the in-vehicle T-box. Therefore, for the traditional monitoring method, only the table item of abnormal communication between the vehicle-mounted computer and the vehicle-mounted T-box can be determined, and the reason for abnormal communication between the vehicle-mounted computer and the vehicle-mounted T-box cannot be determined.

In order to quickly diagnose a cause of a fault of a vehicle, the embodiment of the application provides a method and a device for processing fault data and the vehicle. Wherein the method of processing fault data may be performed by a controller on a target vehicle. For example, an on-board computer, or a device with data processing capability for fault diagnosis in a vehicle. From the point of view of the controller. The method for processing fault data provided by the embodiment of the application is described. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Referring to fig. 1, fig. 1 is a flowchart of a method for processing fault data according to an embodiment of the present application, including:

s101: and obtaining fault phenomenon data.

To diagnose a fault occurring on the target vehicle, the controller may acquire fault phenomenon data. The fault event data is used to indicate a fault event occurring in the target vehicle, and may include, for example, information about a fault event that has occurred in the target vehicle. In the embodiment of the application, the fault event occurring on the target vehicle may include a fault event and a fault cause event. The fault cause event is a cause capable of causing the fault event to occur.

Alternatively, the failure event may be detected by a sensor or detection mechanism already deployed on the target vehicle; fault cause events may be difficult to detect by sensors or detection mechanisms already deployed on the target vehicle. Therefore, by the method for processing fault data provided by the embodiment of the application, the fault cause event causing the fault event can be determined based on the related information of the fault event which can be detected.

S102: and determining a candidate fault cause event set according to the fault phenomenon data and the first corresponding relation.

After the fault phenomenon data is obtained, the processor can determine a candidate fault cause event set corresponding to the fault phenomenon event according to the first corresponding relation. Wherein the set of candidate fault causes may include information of one or more candidate fault cause events. Candidate fault cause events have the ability to trigger a fault event. The first correspondence is used to describe a causal relationship between the failure event and the failure cause event.

That is, the first correspondence indicates which fault event events may be caused by the fault cause event. Thus, according to the first correspondence, it is possible to deduce which fault event cause events may be caused by the fault event included in the fault event data. These fault cause events may be referred to as candidate fault cause events. The set of candidate fault cause events is referred to as a fault cause event set.

In some possible implementations, the first correspondence may be based on expert experience. Specifically, a technician may analyze the structure and connection relationships of various components in the target vehicle in advance to determine which fault events may cause other fault events to occur. Next, a fault event having the ability to cause other fault events to occur may be taken as a fault cause event, and a causal relationship between the fault cause event and other fault events that it can trigger may be established. It will be appreciated that a fault cause event may also trigger a fault cause event. Accordingly, the first correspondence may also include a causal relationship between fault cause events. In some possible implementations, the first correspondence is a causal relationship between fault events, wherein the fault event and the fault cause event are not distinguished.

In some other possible implementations, the first correspondence may be learned based on sample data. Specifically, a training sample dataset may be acquired first. The training sample data set comprises information of a plurality of fault event types and information of fault cause events corresponding to each fault event type. Then, the artificial intelligence model may be trained based on the training sample data set such that the artificial intelligence model learns a correspondence between the failure event and the failure cause event. Thus, the artificial intelligence model obtained through training is the first corresponding relation. Thus, the accuracy of the first corresponding relation can be improved through the artificial intelligence model.

S103: historical fault cause data is obtained.

In the above step, the controller may determine one or more candidate fault cause events that can cause the occurrence of the fault event according to the related information of the fault event and the first correspondence. Then, the controller can screen out the fault reason event with the largest probability of actually causing the fault phenomenon event from one or more candidate fault reason events, and the fault diagnosis of the target vehicle is completed. Alternatively, if there are a plurality of fault cause events that lead to the same probability of occurrence of a fault event, the controller may determine each fault cause event as the target fault cause event. Alternatively, the controller may determine a fault cause event having a time closest to the current event among the plurality of fault cause events as the target fault cause event.

Specifically, the controller may first obtain historical failure cause data. The historical fault cause data is used for indicating fault cause events of the target vehicle in a historical preset time period. The historical preset time period may be twenty-four hours before the current time, one week before the current time, or one month before the current time, for example. Alternatively, the history preset period may be set according to actual conditions.

That is, the historical failure cause data is information about failure cause events that have occurred in a past period of events of the target vehicle. Thus, based on the historical fault cause data, it can be determined what components on the vehicle have failed in a relatively recent past event. Therefore, the target fault cause event can be conveniently determined according to the history rule of the fault cause event.

S104: and determining a target fault cause event according to the historical fault cause data and the candidate fault cause event set.

After the candidate fault cause event set is determined and the historical fault cause data is obtained, the controller may determine a target fault event from a plurality of candidate fault cause events in the candidate fault cause event set according to the historical fault cause data. The probability that the target fault cause event causes the fault event is higher than the probability that the non-target fault cause event in the candidate fault cause event set causes the fault event. That is, the target failure cause event is the failure cause event most likely to cause the failure event to occur. Alternatively, the controller may determine, as the target fault cause event, a candidate fault cause event that has occurred in the candidate fault cause event set and has a time of occurrence closest to the current time. Alternatively, the controller may determine, as the target fault cause event, a candidate fault cause event that has occurred in the candidate fault cause event set and has the largest occurrence number.

After the target fault cause event is determined, auxiliary fault screening may be performed using the target fault cause event. Specifically, if the communication system of the target vehicle is not faulty, the controller may establish a connection between the target vehicle and the maintenance diagnostic system, and transmit fault data and information of a fault cause event to the maintenance diagnostic system based on the connection so that the maintenance diagnostic system generates a diagnostic report according to the fault phenomenon data and the information of the target fault cause event.

In some possible implementations, the controller may store fault event data and information related to the target fault cause event. When the target vehicle is driven to a service area, such as a 4S store or a service factory corresponding to the vehicle, the controller of the target vehicle may automatically establish connection with the computer device of the service area and upload information of the failure event and information of the failure cause event of the target through the internet. The establishment of the online between the controller of the target vehicle and the computer equipment of the maintenance area may specifically include: the controller of the target vehicle establishes an online connection with the computer devices of the service area via bluetooth, wireless network or other protocol. Therefore, the primary screening of the fault event can be realized, and the maintenance and inspection personnel can maintain the target vehicle conveniently.

That is, if a fault event occurs in the vehicle during the driving of the vehicle by the driver, the controller may determine the target fault cause event corresponding to the fault event by using the technical solution provided in the embodiment of the present application. The target fault cause event is a fault cause event which is determined after the primary analysis of the controller and causes the maximum occurrence probability of the fault event. As a result of a malfunction of the vehicle, the driver can drive the vehicle to a maintenance area, such as a 4S store or the like. After the target vehicle enters the maintenance area, the target vehicle may establish a connection with the computer device of the maintenance area, and send information of the target failure cause event obtained by the controller to the computer device of the maintenance area through the connection. Therefore, as the target fault cause event is the fault cause event with the largest occurrence probability, technicians in the maintenance area can screen the target fault cause event preferentially, so that the maintenance efficiency of the target vehicle is improved.

The embodiment of the application provides a method for processing fault data, which can be used for determining fault reason events which cause fault phenomenon events to occur on a target vehicle. Specifically, failure event data may be first obtained, where the failure event data is used to identify a failure event that occurs with the target vehicle. Then, a plurality of fault cause events that may cause the fault event may be determined according to the fault event data and the first correspondence. The set of multiple fault cause events is referred to as a candidate fault cause event set. After the candidate fault cause event set is determined, historical fault cause data may be obtained, and a target fault cause event may be determined from the candidate fault cause event set based on the historical fault cause data. The historical fault reason data are used for indicating the fault reason of the target vehicle in the historical preset time. The target fault cause event determined by the method is a fault cause event which occurs recently and can cause the target vehicle to generate a fault event. In this way, the correspondence between the fault event and the fault cause event is determined in combination with the structure inside the target vehicle, and the fault cause event of the target vehicle occurring in the near future can be determined, so that the fault cause event having the highest probability of causing the fault event of the target vehicle can be determined. Thus, the automatic diagnosis of the fault event of the target vehicle is realized, and the probability that the obtained fault cause event is the actual fault of the target vehicle is high.

In some possible implementations, the controller may also perform early warning based on the first correspondence and the fault cause event.

Specifically, after determining the target failure cause event, the controller may determine the early warning failure event set according to the target failure cause event and the first correspondence. The early warning fault event set comprises at least one early warning fault event. The early warning fault event is a fault event that may be triggered by a target fault cause event. Then, the controller can pre-warn each pre-warn fault event in the pre-warn fault event set. Therefore, after the controller determines the target fault cause event according to the fault event, the controller can determine other fault event events which can be triggered by the target fault cause event, so that early warning is timely carried out, and the influence on the normal operation of the target vehicle is avoided

Optionally, the controller may pre-warn the pre-warn fault event by generating the warning information. Specifically, the controller may generate warning information according to the early warning failure event, and then display the warning information on the target vehicle, thereby completing warning of the early warning failure event.

The foregoing provides some specific implementations of a method for processing fault data according to the embodiments of the present application, and based on this, the present application further provides a corresponding apparatus for processing fault data. The apparatus for processing fault data provided in the embodiments of the present application will be described from the viewpoint of functional modularization.

Referring to a schematic structural diagram of an apparatus for processing fault data shown in fig. 2, the apparatus 200 for processing fault data includes an acquisition unit 210 and a processing unit 220.

The acquiring unit 210 is configured to acquire fault event data, where the fault event data is used to indicate a fault event that occurs in the target vehicle.

The processing unit 220 is configured to determine a candidate failure cause event set according to the failure event data and a first correspondence, where the first correspondence is used to describe a causal relationship between a failure event and a failure cause event, and the candidate failure cause event set includes at least one candidate failure cause event, and the failure cause event has a capability of causing the failure event to occur.

The obtaining unit 210 is further configured to obtain historical fault cause data, where the historical fault data is used to indicate a fault cause event that occurs in the target vehicle within a historical preset time period.

The processing unit 220 is further configured to determine a target fault cause event according to the historical fault cause data and the candidate fault cause event set, where the probability that the target fault cause event causes the fault event is higher than the probability that a non-target fault cause event in the candidate fault cause event set causes the fault event.

The embodiment of the application provides a device for processing fault data. Specifically, failure event data may be first obtained, where the failure event data is used to identify a failure event that occurs with the target vehicle. Then, a plurality of fault cause events that may cause the fault event may be determined according to the fault event data and the first correspondence. The set of multiple fault cause events is referred to as a candidate fault cause event set. After the candidate fault cause event set is determined, historical fault cause data may be obtained, and a target fault cause event may be determined from the candidate fault cause event set based on the historical fault cause data. The historical fault reason data are used for indicating the fault reason of the target vehicle in the historical preset time. The target fault cause event determined by the method is a fault cause event which occurs recently and can cause the target vehicle to generate a fault event. In this way, the correspondence between the fault event and the fault cause event is determined in combination with the structure inside the target vehicle, and the fault cause event of the target vehicle occurring in the near future can be determined, so that the fault cause event having the highest probability of causing the fault event of the target vehicle can be determined. Thus, the automatic diagnosis of the fault event of the target vehicle is realized, and the probability that the obtained fault cause event is the actual fault of the target vehicle is high.

Optionally, in some possible implementations, the processing unit 220 is configured to determine an early warning failure event set according to the target failure cause event and the first correspondence, where the early warning failure event set includes at least one early warning failure event, and the failure cause event has a capability of triggering the occurrence of the early warning failure event; and pre-warning each pre-warning fault event in the pre-warning fault event set.

Optionally, in some possible implementations, the processing unit 220 is specifically configured to generate alarm information according to the early warning failure event; and displaying the alarm information on the target vehicle.

Optionally, in some possible implementations, the apparatus 200 further includes a transmitting unit;

the processing unit 220 is specifically configured to establish a connection between the target vehicle and a maintenance diagnostic system.

Optionally, in some possible implementations, the sending unit is further configured to upload, through the internet, information of the failure event and information of the target failure cause event, where the information of the failure event and the information of the failure event are used to update the first correspondence.

The embodiment of the application also provides corresponding equipment, a computer storage medium and a vehicle, which are used for realizing any one of the method for processing the fault data.

The device comprises a memory for storing instructions or code and a processor for executing the instructions or code to cause the device to perform the method for processing fault data according to any of the embodiments of the present application.

The computer storage medium has code stored therein, and when the code is executed, a device executing the code implements the method for processing fault data according to any embodiment of the present application.

Referring to fig. 3, fig. 3 is a schematic diagram of a possible structure of a vehicle according to an embodiment of the present application. In the embodiment shown in fig. 3, the vehicle 300 includes a memory 310 and a controller 320. The memory 310 is configured to store instructions or code, and the controller 320 is configured to execute the instructions or code stored in the memory 310 to implement a method for processing fault data according to any of the embodiments of the present application.

The "first" and "second" in the names of "first", "second" (where present) and the like in the embodiments of the present application are used for name identification only, and do not represent the first and second in sequence.

From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, or the like, including several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the methods described in the embodiments or some parts of the embodiments of the present application.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application.

Claims

1. A method of processing fault data, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method of claim 2, wherein said pre-warning each pre-warning fault event in said set of pre-warning fault event events comprises:

and displaying the alarm information on the target vehicle.

4. A method according to any one of claims 1-3, wherein the method further comprises:

5. The method according to claim 1, wherein the method further comprises:

6. An apparatus for processing fault data, the apparatus comprising:

7. The apparatus of claim 6, wherein the device comprises a plurality of sensors,

the processing unit is used for determining an early warning fault event set according to the target fault cause event and the first corresponding relation, wherein the early warning fault event set comprises at least one early warning fault event, and the fault cause event has the capability of triggering the early warning fault event; and pre-warning each pre-warning fault event in the pre-warning fault event set.

8. The apparatus of claim 7, wherein the device comprises a plurality of sensors,

the processing unit is specifically used for generating alarm information according to the early warning fault phenomenon event; and displaying the alarm information on the target vehicle.

9. The apparatus according to any one of claims 6-8, further comprising a transmitting unit;

10. A vehicle comprising a memory for storing instructions or code and a processor for executing instructions or code stored in the memory to implement the method of processing fault data according to any one of claims 1 to 5.