CN114043994B

CN114043994B - Vehicle fault processing method, device, equipment and storage medium

Info

Publication number: CN114043994B
Application number: CN202111363068.2A
Authority: CN
Inventors: 马红敏
Original assignee: Guoqi Intelligent Control Beijing Technology Co Ltd
Current assignee: Guoqi Intelligent Control Beijing Technology Co Ltd
Priority date: 2021-11-17
Filing date: 2021-11-17
Publication date: 2024-06-04
Anticipated expiration: 2041-11-17
Also published as: CN114043994A

Abstract

The invention provides a vehicle fault processing method, device, equipment and storage medium, which are applied to distributed nodes in an SOA heterogeneous platform and comprise fault monitoring nodes, fault reporting nodes, fault information processing nodes and fault storage nodes which sequentially transmit data, and particularly, the fault monitoring nodes are used for acquiring operation data corresponding to a plurality of operation nodes in a vehicle, and extracting vehicle fault information from the operation data; analyzing the vehicle fault information through the fault reporting node to obtain fault reports corresponding to a plurality of operation nodes; determining a fault level of the vehicle according to the fault report through the fault information processing node; the fault storage node stores the fault grade and the fault report of the vehicle to a nonvolatile storage area based on the fault type information, and the nonvolatile storage area is used for accessing diagnostic communication of cloud equipment based on the fault type information. Therefore, the invention can be applied to fault processing of a high-performance domain, improves flexibility and reduces resource waste.

Description

Vehicle fault processing method, device, equipment and storage medium

Technical Field

The present invention relates to the field of automatic driving technologies, and in particular, to a vehicle fault handling method, device, apparatus, and storage medium.

Background

With the development of autopilot technology, automobile System functions are more and more complex, safety level is higher and higher, more and more automobiles are deployed with advanced driving assistance systems (ADVANCED DRIVING ASSISTANT SYSTEM, ADAS), automobile engineers (SoCiety of Automotive Engineers, SAE) have clear definition on autopilot level, L2 level (semiautomatic driving) and following distributed control modes of multiple electronic control units (Electronic Control Unit, ECU) based on micro control units (Microcontroller Unit, MCU) are adopted for intelligent driving control part, and more L3 (autopilot) must adopt centralized control strategy of domain controller automobile domain control units (Domain Control Unit, DCU) based on high performance System on a Chip (SoC), wherein DCU integrates multiple high performance chips including central processor (Central Processing Unit, CPU) and graphic processor (Graphics Processing Unit, GPU).

In the prior art, when a fault diagnosis system in the real time domain processes a vehicle fault, the vehicle fault is usually checked periodically by using an inherent program based on a multi-ECU distributed control mode of an MCU.

However, if the real-time domain fault diagnosis system is used for processing the vehicle fault in the high-performance domain, resources are wasted, the effect is not ideal, and the flexibility is low.

Disclosure of Invention

The invention provides a vehicle fault processing method, device, equipment and storage medium, which are applied to distributed nodes in an SOA heterogeneous platform and are used for solving the problems that a fault processing method aiming at a high-performance domain in the prior art is immature, resources are wasted, the effect is not ideal and the flexibility is low.

In a first aspect, the present invention provides a vehicle fault handling method, applied to a distributed node in an SOA heterogeneous platform, where the distributed node includes a fault monitoring node, a fault reporting node, a fault information processing node, and a fault storage node that sequentially transmit data, and the method includes:

acquiring operation data corresponding to a plurality of operation nodes in a vehicle through the fault monitoring node, and extracting vehicle fault information from the operation data;

Analyzing the vehicle fault information through the fault report node to obtain fault reports corresponding to a plurality of operation nodes; the fault report comprises fault degree information, fault type information and diagnosis fault codes; the fault type information comprises system on chip (SoC) end information and Microcontroller (MCU) end information;

Determining, by the fault information processing node, a fault level of the vehicle according to the fault degree information, the fault type information, and the diagnostic fault code;

and storing the fault grade of the vehicle, the fault degree information and the diagnosis fault code to a nonvolatile storage area in a file system based on the fault type information through the fault storage node, wherein the nonvolatile storage area is used for accessing diagnosis communication by cloud equipment based on the fault type information.

Optionally, the plurality of operation nodes are registered nodes in advance; the method further comprises the steps of:

Creating an instance for subscribing the plurality of nodes through the fault monitoring node, and initiating a subscription request to a plurality of operation nodes in the vehicle by calling an interface corresponding to the instance; the subscription request is used for acquiring operation data of the plurality of operation nodes;

Correspondingly, the operation data corresponding to a plurality of operation nodes in the vehicle are obtained through the fault monitoring node, and the method comprises the following steps:

And receiving the operation data sent by the plurality of operation nodes according to the subscription request by the fault monitoring node based on a synchronous mode or an asynchronous mode.

Optionally, the analyzing the vehicle fault information to obtain fault reports corresponding to the plurality of operation nodes includes:

Extracting characteristic information in the vehicle fault information, and comparing the characteristic information with a parameter threshold value in a preset fault library to obtain a comparison result;

and obtaining fault reports corresponding to the plurality of operation nodes according to the comparison result.

Optionally, determining the fault level of the vehicle according to the fault degree information, the fault type information and the diagnostic fault code includes:

Determining an associated influence degree based on the fault degree information and the diagnosis fault codes corresponding to each operation node; the association influence degree is a degree level for affecting the normal operation of other operation nodes; and determining the fault level of the vehicle according to the association influence degree and the fault type information.

Optionally, the method further comprises:

Dividing a nonvolatile storage area in a file system into two storage areas based on the fault type information through the fault storage node, wherein the two storage areas are a first storage area and a second storage area respectively, the first storage area is used for storing information from an SoC end, and the second storage area is used for storing information from an MCU end;

accordingly, storing the failure level of the vehicle, the failure degree information, and the diagnostic failure code to a nonvolatile storage area in a file system based on the failure type information, including:

and respectively storing the fault grade of the vehicle, the fault degree information and the diagnosis fault code into corresponding storage areas according to the corresponding fault type information.

Optionally, the method further comprises:

acquiring an electronic ignition switch state of a vehicle;

If the electronic ignition switch state is a starting state, the unprocessed historical fault information in the nonvolatile storage area is read; the historical fault information comprises the fault grade, the fault degree information and the fault type information of the vehicle which are stored when the electronic ignition switch state of the vehicle is in the off state last time;

And executing corresponding actions according to the fault grades in the historical fault information.

Optionally, executing the corresponding action according to the fault level in the historical fault information includes:

judging whether the fault grade in the historical fault information reaches a preset grade or not;

And if at least one fault level reaches a preset level, sending an engine locking instruction to an engine electronic controller unit of the vehicle.

Optionally, the method further comprises:

Calling https encryption protocol to encrypt each item of data in the nonvolatile storage area in a first layer;

setting a preset encryption key to encrypt the data of the second layer of data, and generating encrypted data and a corresponding encrypted data ID (identity);

And sending the encrypted data and the corresponding encrypted data ID to cloud equipment, wherein the cloud equipment is used for decrypting the encrypted data based on the encrypted data ID and reading the encrypted data.

Optionally, the fault level includes at least a first level and a second level; the method further comprises the steps of:

If the fault grade of the vehicle is the first grade, a first instruction is sent to control the vehicle to carry out parking treatment;

and if the fault grade of the vehicle is the second grade, sending a second instruction to control the vehicle to travel to a vehicle maintenance point according to a preset travel path or a re-planned travel path.

In a second aspect, the present invention provides a vehicle failure processing apparatus, the apparatus comprising:

The fault monitoring node is used for acquiring operation data corresponding to a plurality of operation nodes in the vehicle and extracting vehicle fault information from the operation data;

The fault report node is used for analyzing the vehicle fault information to obtain fault reports corresponding to the plurality of operation nodes; the fault report comprises fault degree information, fault type information and diagnosis fault codes; the fault type information comprises system on chip (SoC) end information and Microcontroller (MCU) end information;

the fault information processing node is used for determining the fault grade of the vehicle according to the fault degree information, the fault type information and the diagnosis fault code;

the fault storage node is used for storing the fault grade of the vehicle, the fault degree information and the diagnosis fault code to a nonvolatile storage area in a file system based on the fault type information, and the nonvolatile storage area is used for accessing diagnosis communication by cloud equipment based on the fault type information.

In a third aspect, the present invention provides a vehicle failure processing apparatus comprising: at least one processor and memory;

The memory stores computer-executable instructions;

The at least one processor executing computer-executable instructions stored in the memory causes the at least one processor to perform the vehicle fault handling method of any one of the first aspects.

In a fourth aspect, the present invention provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement the vehicle fault handling method of any one of the first aspects.

In a fifth aspect, the present invention provides a computer program product comprising a computer program which, when executed by a processor, implements the vehicle fault handling method according to any of the first aspects.

The vehicle fault processing method, the device, the equipment and the storage medium are applied to distributed nodes in an SOA heterogeneous platform, and comprise fault monitoring nodes, fault reporting nodes, fault information processing nodes and fault storage nodes which sequentially transmit data, and particularly, operation data corresponding to a plurality of operation nodes in a vehicle can be obtained through the fault monitoring nodes, and vehicle fault information is extracted from the operation data; further, the vehicle fault information is sent to a fault report node, and correspondingly, the received vehicle fault information is analyzed through the fault report node to obtain fault degree information, fault type information and diagnosis fault codes corresponding to a plurality of operation nodes; the fault type information comprises system on chip (SoC) end information and Microcontroller (MCU) end information; further, the information is sent to a fault information processing node, and correspondingly, the fault grade of the vehicle is determined through the fault information processing node according to the received fault degree information, fault type information and diagnosis fault codes; further, the fault storage node stores the fault grade, the fault degree information and the diagnosis fault code of the vehicle to a nonvolatile storage area in the file system based on the fault type information, and the nonvolatile storage area is used for the cloud end equipment to access diagnosis communication based on the fault type information, wherein the vehicle fault information can come from the SoC end and the MCU end.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

Fig. 1 is a schematic diagram of an application scenario of a vehicle fault handling method according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of an autopilot vehicle according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of a vehicle fault handling method according to an embodiment of the present invention;

Fig. 4 is a schematic architecture diagram of a distributed node in an SOA heterogeneous platform according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a vehicle fault handling method according to an embodiment of the present invention;

FIG. 6 is a flowchart illustrating another vehicle fault handling method according to an embodiment of the present invention;

fig. 7 is a schematic flow chart of fault self-checking when a vehicle is started according to an embodiment of the present invention;

FIG. 8 is a schematic flow chart of fault self-checking when another vehicle is started according to the embodiment of the present invention;

FIG. 9 is a flow chart of a method for storing failure information according to an embodiment of the present invention;

Fig. 10 is a schematic structural diagram of a vehicle fault handling apparatus according to an embodiment of the present invention;

fig. 11 is a schematic hardware structure of a vehicle fault handling apparatus according to an embodiment of the present invention.

Specific embodiments of the present invention have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention.

First, the terms involved in the present invention will be explained:

A System-on-a-chip (SoC) refers to an integrated circuit with a dedicated target that contains the complete System and has the entire contents of embedded software. The wireless SoC can be composed of a system-on-chip control logic module, a microprocessor/microcontroller CPU core module, a digital signal processor DSP module, an embedded memory module, an interface module for communicating with the outside, an Analog front-end module containing an Analog-to-Digital Converter (ADC)/digital-to-Analog converter (Digital to Analog Converte, DAC), a power supply and power consumption management module, and a radio frequency front-end module, a user-defined logic and micro-electronic mechanical module, a basic software module or loadable user software and the like.

A microcontroller (Microcontroller Unit, MCU), which may also be referred to as a micro-control unit, refers to an integrated circuit device for controlling other parts of an electronic system, which may be composed of a CPU, a non-volatile memory (ROM), a volatile memory (RAM), peripheral devices and supporting circuitry.

The following explains the application scenario of the embodiment of the present invention:

Fig. 1 is a schematic diagram of an application scenario of a vehicle fault processing method provided in an embodiment of the present invention, as shown in fig. 1, a vehicle fault detection system is disposed in a vehicle 102, and in a running process of the vehicle 102, running data of the vehicle 102 may be periodically obtained to determine whether a fault exists in a running state of the vehicle 102, and fault information encountered by the vehicle 102 may be stored in a nonvolatile storage area in a file system, so that a 4S shop worker may query fault information from the nonvolatile storage area or query fault information from the nonvolatile storage area by using a terminal device.

It can be appreciated that the present invention can be applied to an application scenario where an autonomous vehicle needs to handle a vehicle fault during driving, because the autonomous vehicle is controlled by a computing platform under the condition of unmanned active control, the autonomous vehicle needs various sensors to replace a driver to sense a change in driving environment, and in particular, the various sensors may be devices that can collect external environments, such as millimeter wave radar, laser radar, images, etc., and may sense a change in driving environment using global positioning system (Global Positioning System, GPS) technology, navigation technology, high-precision map technology, artificial intelligence technology, monitoring device technology, vehicle-to-vehicle communication technology, vehicle-to-infrastructure technology, and drive-by-wire technology.

For a better understanding of the embodiments of the present invention, the structure of an autonomous vehicle suitable for use in the vehicle fault handling method provided by the present invention will be briefly described with reference to fig. 2. Fig. 2 is a schematic structural diagram of an autopilot vehicle according to an embodiment of the present invention.

As shown in fig. 2, the autonomous vehicle 200 may include: domain controller (Domain Controller, DC) 201, navigation System 202, vehicle display 203, autopilot module 204, combination meter (Instrument Cluster, IC) 205, whole vehicle control unit (Vehicle Control Unit, VCU) 206, micro control unit (Motor Control Unit, MCU) 207, power distribution unit (Power Distribution Unit, PDU) 208, battery management System (Battery MANAGEMENT SYSTEM, BMS) 209, body control module (Body Control Module, BCM) 210, wherein DC201 is built by System on a Chip (SoC).

It should be appreciated that the various components described above may be connected via a controller area network (Controller Area Network, CAN) bus, a local internet (Local Interconnect Network, LIN) bus, a flex-array bus, a media oriented system transport (Media Oriented Systems Transport, MOST) bus, or the like. Buses of the types described above may be used to transfer information between various components. It will also be appreciated that the form or format of the signals transmitted on the different buses connecting the different parts may be different and the gateway may convert the signals in the different forms or formats before delivering them to the receiver of the signals. The gateway is named here only one kind, but may be replaced by other processors that are able to mutually translate the signals of the above parts.

The navigation system may include, for example, but is not limited to, a global satellite positioning system (Global Positioning System, GPS), a Beidou satellite navigation system (BeiDou Navigation SATELLITE SYSTEM, BDS), real-time dynamic positioning (Real-TIME KINEMATIC, RTK), and Ultra Wideband (UWB) positioning systems. In the embodiment of the invention, the navigation system can be used for positioning the position of the automatic driving vehicle, acquiring the running speed of the vehicle, the remaining distance of the automatic driving road section and other information.

It is to be understood that the illustrated construction of the embodiment of the present invention does not constitute any limitation on the autonomous vehicle 200. In other embodiments, autonomous vehicle 200 may include more or fewer components than shown, or certain components may be combined, certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

During the automatic driving, various portions of the vehicle 102 may fail, and in order to avoid an accident, the generated vehicle failure needs to be handled.

In the prior art, when a fault diagnosis system in the real time domain processes a vehicle fault, the vehicle fault is checked periodically by utilizing an inherent program in a multi-ECU distributed control mode based on an MCU, and the fault generated by the vehicle is further processed.

Based on the above problems, the invention provides a vehicle fault processing method based on a high-performance domain, which defines each node in a fault processing flow as the Service of an SOA (Service-oriented architecture) under the SOA architecture of the high-performance domain, namely, a distributed node under a heterogeneous platform, wherein the distributed node comprises a fault monitoring node, a fault reporting node, a fault information processing node and a fault storage node which sequentially transmit data, and processes the vehicle fault through the nodes.

The technical scheme of the invention is described in detail below by specific examples. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.

Fig. 3 is a flow chart of a vehicle fault handling method according to an embodiment of the present invention, where the method of the present embodiment may be executed by a vehicle fault handling system. As shown in fig. 3, the method of the present embodiment may include:

Step 301, operation data corresponding to a plurality of operation nodes in the vehicle are obtained through the fault monitoring node, and vehicle fault information is extracted from the operation data.

In the step, the fault monitoring node can acquire operation data corresponding to a plurality of operation nodes in the vehicle through a publish-subscribe mechanism.

Wherein the operational data may include, but is not limited to: vehicle state data, software operational data, and hardware operational data, the vehicle state data may include: tire pressure, electricity usage, motor state, variable box running state, vehicle running speed and the like; the software operation data can comprise state detection data of service modules such as a perception module, a cognition module, a positioning module, a decision control module, a vehicle software control module, a map module and the like; the hardware operational data may include: the system comprises an industrial personal computer, a camera, a radar, a laser radar, an ultrasonic radar, a millimeter wave radar, a global positioning system, an inertial measurement device, an image acquisition module, an inertial sensor, a wheel speed meter, a global navigation satellite system and other equipment state detection data.

It may be understood that the plurality of operation nodes may refer to various sensors and operation components of the vehicle during the running process, which is not particularly limited in the embodiment of the present invention, but the plurality of operation nodes are registered in advance in the fault monitoring node, so that the fault monitoring node may monitor operation data of the plurality of operation nodes, and may also manually add the operation node to the fault monitoring node to monitor the added operation node.

In this embodiment, the vehicle fault information may include an operation state parameter, fault description information, and the like, where the operation state parameter includes an operation parameter when each operation node generates a fault, for example, a running speed of 100km/h, a fuel consumption of 1/km, a running distance of 1m, and the like; the failure description information includes information describing a failure, for example, failure of the turn signal lamp, failure of the camera to acquire an image, and the like.

For example, the fault monitoring node may obtain operation data corresponding to the speed sensor in the vehicle, further extract operation state parameters, fault description information, and the like from the operation data, for example, a running speed of 100km/h, and a speed running too fast.

Step S302, analyzing the vehicle fault information through the fault report node to obtain fault reports corresponding to a plurality of operation nodes; the fault report comprises fault degree information, fault type information and diagnosis fault codes; the fault type information comprises SoC end information of a system on a chip and MCU end information of a microcontroller.

In this embodiment, the failure degree information indicates the severity of a failure of a certain operation node in the vehicle. The fault type information comprises SoC end information and MCU end information, wherein the SoC end information refers to that vehicle fault information of each motion node comes from the SoC end, the MCU end information refers to that vehicle fault information of each motion node comes from the MCU end, and the SoC end information and the MCU end information can be distinguished by adding an identification mode, for example, the vehicle fault information of each motion node from the SoC end is provided with an identification ID number of '1', and the vehicle fault information of each motion node from the MCU end is provided with an identification ID number of '2'.

The fault code may represent what kind of fault the vehicle is in particular, which may be represented in particular according to an internationally common code; for example, when the generated fault code is P019, this indicates that the fuel pressure sensor is faulty and the fuel consumption is too high; when the generated fault code is P021, it indicates that the fault that the engine of the vehicle is overheated at this time, it is understood that the form of the fault code in the embodiment of the present invention is not particularly limited, and the fault code may be the above-mentioned international code or an artificially specified code, for example, when the generated fault code is 010, it indicates that the fuel pressure sensor is faulty at this time.

In this step, the vehicle fault information sent by a certain node may be analyzed by the fault reporting node, for example, a certain operation parameter in the vehicle fault information is oil consumption 1L/km, the operation parameter has a mark "2", further, a certain operation parameter is compared with a normal parameter threshold, the normal parameter threshold is 0.072L/km, the oil consumption is found to be too high and greater than 10 times of the normal parameter threshold, the running of the automobile may be affected, the level is 1, meanwhile, a fault code P019 may be obtained, and the mark "2" indicates that the operation parameter is the vehicle fault information of a certain motion node from the MCU side, and then it may be known that the fault report of the node is: the fault degree information is of level 1, the fault type information is MCU side information, and the fault code is P019.

It should be understood that the specific method for determining the severity level of the fault level information according to the embodiments of the present invention is not limited, and the above is merely an example.

And step S303, determining the fault grade of the vehicle according to the fault degree information, the fault type information and the diagnosis fault code through the fault information processing node.

In the step, the influence degree on the running of the vehicle can be judged through the fault degree information, the fault type information and the diagnosis fault code, so that the fault grade of the vehicle is determined, and if one running node has serious fault and a plurality of running nodes are influenced to be unable to normally run after the running node breaks down, the fault grade is higher.

Alternatively, if a failure of one of the operating nodes is slight, for example, due to a shelter of a building or in an underground parking garage, the communication signal is weak, and after a period of time, the communication signal may be automatically recovered, the effect on the running function of the vehicle is not great, and the failure level is low.

It will be appreciated that the fault type information and the diagnostic fault code play an auxiliary role in judging the fault level of the vehicle, for example, the fault type information is that the SoC end and the diagnostic fault code are P019, but the fault level information is 5 levels, which indicates that the fault level is low, and the fault type information is that the SoC end and the diagnostic fault code are P019, but the fault level information is 1 level, which also affects the normal operation of other operation nodes, which indicates that the fault level is high.

And step S304, storing the fault grade of the vehicle, the fault degree information and the diagnosis fault code to a nonvolatile storage area in a file system based on the fault type information through the fault storage node, wherein the nonvolatile storage area is used for accessing diagnosis communication by cloud equipment based on the fault type information.

In the embodiment of the invention, the nonvolatile storage area in the file system is divided into two storage areas in advance and is respectively used for storing the information of the SoC end and the information of the MCU end, namely the fault information from the SoC end and the fault information from the MCU end are respectively and correspondingly stored in different areas, so that the data classification is more orderly and is convenient for the cloud equipment to read.

In this step, the fault storage node may store the fault level, the fault degree information, and the diagnosis fault code of the vehicle in its corresponding storage areas, respectively, based on the fault type information, so as to facilitate data management. For example, the fault level of the vehicle corresponding to the operation node 1 is high level, the fault degree information is 1 level, the diagnosis fault code is P019, the fault level of the vehicle corresponding to the operation node 2 is medium level, the fault degree information is 5 level, the diagnosis fault code is P018, the fault degree information and the diagnosis fault code of the vehicle corresponding to the operation node 1 are stored in the storage area 1 when the operation node 2 transmits the data, the fault level, the fault degree information and the diagnosis fault code of the vehicle corresponding to the operation node 1 are stored in the storage area 2, the storage data type corresponding to the storage area 1 is SoC end information, and the storage data type corresponding to the storage area 2 is MCU end information.

It can be understood that when the cloud device accesses the data in the nonvolatile storage area in the file system, the cloud device can access the data based on the classification of the fault type information, so that the access rate is improved.

Therefore, the invention can monitor the vehicle information from the SoC end or the MCU end, acquire a certain amount of vehicle information data to perform unified fault analysis, save resources, further determine the fault level, improve the processing flexibility, further store the vehicle fault information into the nonvolatile storage areas respectively through the classification of the fault types, support the access of cloud diagnosis communication, ensure that the data has regularity and avoid the data loss.

It should be noted that, the distributed nodes in the SOA heterogeneous platform may be software or hardware, or may be a combination of software and hardware, etc., which is not limited in particular by the embodiment of the present invention. Specifically, fig. 4 is a schematic architecture diagram of a distributed node in an SOA heterogeneous platform according to an embodiment of the present invention, as shown in fig. 4, the distributed node in the SOA heterogeneous platform may include a fault monitoring node, a fault reporting node, a fault information processing node and a fault storage node that sequentially transmit data, where the fault monitoring node may receive operation data corresponding to the operation node and process the operation data, and send the processed data to the fault reporting node, and the corresponding fault reporting node receives and parses the processed data, and sends the parsed data to the fault information processing node, and the corresponding fault information processing node receives and processes the parsed data again and sends the reprocessed data to the fault storage node to store.

For example, fig. 5 is a schematic diagram of a vehicle fault handling method provided by the embodiment of the present invention, as shown in fig. 5, in order to implement handling of a fault generated by a vehicle, data of each operation node may be monitored first, and a specific monitoring manner may be to receive data of each operation node based on a fault monitoring node publish-subscribe mechanism; after the monitored data is collected, data analysis can be performed, wherein the data analysis refers to analysis of the collected data by a fault report node to obtain required parameter data; after the data analysis is completed, data analysis can be performed, wherein the data analysis refers to that the fault information processing node analyzes the acquired parameter data and judges the occurrence level of the fault, namely the corresponding influence level of the fault of the vehicle; finally, data storage is performed according to the result of data analysis, wherein the data storage can be classified storage of the analyzed data by a fault storage node and is used for supporting access of diagnostic communication. The purpose of processing the vehicle faults can be achieved based on the principle.

In this embodiment, creating an instance for subscribing to a plurality of nodes may refer to generating related objects from data generated by subscribing to the plurality of nodes, i.e., constructing a method for subscribing to data generated by the plurality of nodes.

The synchronization mode refers to that after a certain operation node is called to send operation data according to a subscription request, the call needs to wait for a return result to be executed continuously. The asynchronous mode may refer to that after a certain running node is called for running data sent according to a subscription request, subsequent operations can be continuously executed without waiting for a call return result, but local buffer refreshing is needed.

In the step, the fault monitoring node can firstly create an instance for subscribing to a certain node, for example, create a proxy instance, after the instance is created, subscribe through a proxy interface Event, and further initiate subscription requests to a plurality of running nodes in the vehicle; the subscription request is used for acquiring the operation data of a certain operation node; because the mode of receiving data by the fault monitoring node is divided into a synchronous mode and an asynchronous mode, if the mode is the asynchronous mode, a callback function is firstly transmitted through an Event: SETRECEIVEHANDLER (SWS_CM_00181) interface, then an Event:: update (SWS_CM_00172) interface is called to refresh a buffer zone, and finally an Event:: GETCACHEDSAMPLES (SWS_CM_00173) interface is operated to acquire operation data sent by a certain operation node according to a subscription request.

Therefore, the processing efficiency can be improved by asynchronous inquiry and synchronous inquiry of the operation data sent by a plurality of operation nodes according to the subscription request according to actual conditions.

Optionally, fig. 6 is a schematic flow chart of another vehicle fault handling method according to the embodiment of the present invention, as shown in fig. 6, where, based on the vehicle fault handling method according to the embodiment shown in fig. 3, step S302 is further refined, and then the vehicle fault handling method according to the embodiment includes the following steps:

And step S601, acquiring operation data corresponding to a plurality of operation nodes in the vehicle through the fault monitoring node, and extracting vehicle fault information from the operation data.

And step S602, extracting characteristic information in the vehicle fault information through the fault reporting node, and comparing the characteristic information with a parameter threshold value in a preset fault library to obtain a comparison result.

In this embodiment, the feature information may include fault node ID information, fault type information, data corresponding to an operation parameter, a type number, and the like. The type number refers to a type number corresponding to a certain operation parameter from different operation nodes, for example, a certain operation parameter is oil consumption 1L/km, the operation parameter is from an oil consumption type in a fuel pressure sensor, the corresponding type number is P1, it should be noted that each operation node can be corresponding to multiple types, the embodiment of the invention is not limited in particular, for example, the fuel pressure sensor can be corresponding to an oil consumption type, an oil quantity type, an oil temperature type, etc., and the invention is not limited in particular to the type number corresponding to each type, and can be set manually.

When different running nodes of the vehicle have different faults, parameter thresholds corresponding to running state parameters of the different running nodes and mapping tables of type numbers are collected in advance in the fault library, the mapping tables are used for storing corresponding relations between the type numbers of the different running nodes of the vehicle and the running nodes in the fault, and each type number also corresponds to the parameter thresholds and the fault codes in a normal range.

In this step, the fault report node may extract feature information in the vehicle fault information corresponding to a certain operation node, for example, a certain operation parameter in the vehicle fault information of a certain operation node is oil consumption 1L/km, where the operation parameter has an identifier "2", the fault report node may extract that the fault node ID is operation node 1, the data corresponding to the operation parameter is 1L/km, the fault type information is MCU side information, the type number is P1, further, based on the type number P1, the corresponding parameter threshold value is found and compared with 0.072L/km, it is found that 1L/km is far greater than 0.072L/km, and is greater than 10 times of the normal parameter threshold value, its oil consumption is too high, and it is possible that the oil pressure sensor fails, further, it is determined that the level is 1, and the corresponding fault code is found and is P019.

It should be noted that, in the present invention, a multiple relationship of the phase difference is also set for comparing the operation parameter with the parameter threshold, the greater the multiple difference is, the higher the degree of influence is, but the degree level corresponding to the specific numerical value of the multiple relationship is not specifically limited, for example, the degree level corresponding to the 10-time relationship may be 1 level, or the degree level corresponding to the 10-time relationship may be 2 level.

Step 603, obtaining fault reports corresponding to a plurality of operation nodes according to the comparison result through the fault reporting node; the fault report comprises fault degree information, fault type information and diagnosis fault codes; the fault type information comprises SoC end information of a system on a chip and MCU end information of a microcontroller.

In this step, the fault report node obtains a fault report corresponding to the running node 1 based on the comparison result of the running node 1, for example, the comparison result is: the node with faults is an operation node 1, the comparison with a parameter threshold value in a preset fault library finds that 1L/km is far more than 0.072L/km and is more than 10 times of a normal parameter threshold value, the fuel consumption is too high, the fault of a fuel pressure sensor is likely to occur, the level of the fuel pressure sensor is further determined to be 1, a fault code corresponding to the fuel pressure sensor is found to be P019, the fault type information is MCU side information, and the corresponding fault report is that: the fault degree information is of level 1, the fault type information is MCU side information, and the fault code is P019.

Step S604, determining the fault grade of the vehicle according to the fault degree information, the fault type information and the diagnosis fault code through the fault information processing node.

Step S605, storing, by the fault storage node, the fault level of the vehicle, the fault degree information and the diagnostic fault code to a nonvolatile storage area in a file system based on the fault type information, where the nonvolatile storage area is used for accessing diagnostic communication by a cloud device based on the fault type information.

Therefore, the embodiment of the invention can specifically find the fault report corresponding to each operation node, improve the accuracy of identifying the fault information, further respectively store the vehicle fault information to the nonvolatile storage areas through the classification of the fault types, support the access of cloud diagnosis communication, and ensure that key data in the vehicle can be stably stored and not easy to lose.

In this embodiment, the degree of influence of association may refer to the degree of influence on other operation nodes after a certain operation node of the vehicle fails, where the operation node of the vehicle has an association relationship with some operation nodes thereof. The influence degree of a certain operation node on other operation nodes in the vehicle is judged according to the fault degree information and the diagnosis fault code of the certain operation node, and if the certain operation node has serious fault and a plurality of operation nodes are associated, the fault level is higher.

In this step, the fault reporting node may determine the relevant influence degree based on the fault degree information and the diagnostic fault code corresponding to each operation node, for example, the operation node 1 is a communication module, the operation parameter is a 4G signal and is in a 3-grid state, the operation parameter is sent with a flag "1", the fault is that the communication signal is weak, the influence degree is slight, the diagnostic fault code is 002, further, the fault reporting node may determine that the influence degree of the operation node 1 on other operation nodes is not great based on the above information, and the vehicle may continue to travel, and may determine that the fault grade of the vehicle is lower, i.e., is a third grade (i.e., lower grade) based on the fault type information for the SoC end information.

Therefore, the fault grade of the vehicle can be determined according to the fault degree information, the fault type information, the diagnosis fault code and other data information, so that the fault grade determining mode is more accurate, and the judgment errors are reduced.

Optionally, the method further comprises:

For example, the nonvolatile storage in the file system can be divided into two storage areas in advance, namely a first storage area for storing information from the SoC end and a second storage area for storing information from the MCU end, and further, after the fault storage node receives the fault level, the fault degree information and the diagnosis fault codes of the vehicles corresponding to the plurality of running nodes, the information can be stored in the corresponding first storage area and the second storage area respectively based on the fault type information, so that data management is facilitated. For example, the fault level of the vehicle corresponding to the running node 1 is a first level, the fault degree information is a level 1, the diagnostic fault code is P019, and the fault type information is an SoC end; the fault grade of the vehicle corresponding to the operation node 2 is a medium grade, the fault degree information is a grade 5, the diagnosis fault code is P018, and the fault type information is an SoC end; the fault grade of the vehicle corresponding to the operation node 3 is low, the fault degree information is 10, the diagnosis fault code is P010, and the fault type information is MCU end; the data corresponding to the operation node 1 and the operation node 2 are stored in the first storage area, and the data corresponding to the operation node 3 is stored in the second storage area.

Therefore, the data from the SoC end and the MCU end can be processed and then stored respectively, so that the data can be conveniently read and written, and the stored data can be accessed more quickly.

Optionally, the vehicle may process the generated fault during running, but before the vehicle starts, the fault self-checking may be performed first, and fig. 7 is a schematic flow chart of performing the fault self-checking when the vehicle starts, as shown in fig. 7, where the method steps are performed, including:

step S701, acquiring an electronic ignition switch state of the vehicle.

In this step, the operating system in the vehicle may establish a communication connection with the electronic ignition system of the vehicle according to the diagnostic protocol corresponding to the vehicle, and further, may acquire the electronic ignition switch state of the vehicle.

For example, if the ignition state of the current vehicle changes from OFF to ON, it indicates that the vehicle is being started, and further, it is possible to acquire that the electronic ignition switch state of the vehicle is an ON state.

Step S702, if the state of the electronic ignition switch is a starting state, the unprocessed historical fault information in the nonvolatile storage area is read; the historical fault information comprises the fault grade, the fault degree information and the fault type information of the vehicle which are stored last time when the electronic ignition switch state of the vehicle is in the off state.

In this step, the operating system in the vehicle may read the fault level, the fault degree information, and the fault type information stored last time the vehicle stopped traveling, and determine whether the information in the nonvolatile memory area is processed.

It can be understood that after the staff in the 4S store processes the fault in the nonvolatile storage area, the fault information in the nonvolatile storage area can be deleted by the terminal device, that is, which historical fault information in the nonvolatile storage area is solved, and correspondingly, the historical fault information is not found in the nonvolatile storage area.

In a possible implementation manner, the cloud device can also read the historical fault information in the nonvolatile storage area, a worker reserving the 4S store in advance repairs the vehicle fault, and after the historical fault information is solved, the cloud device deletes the fault information in the nonvolatile storage area.

And step 703, executing corresponding actions according to the fault levels in the historical fault information.

In this step, the operating system of the vehicle may read the failure level corresponding to the unprocessed information in the historical failure information, determine what operation should be executed next according to the level of the failure level, if the failure level is higher, prohibit the vehicle from running, and if the failure level is lower, generate a prompt message, send the prompt message to the terminal device of the user, remind the user that a certain running node has a failure, and ask for timely maintenance and processing.

It can be understood that the invention can preliminarily judge the faults existing in the vehicle without checking the faults by maintenance personnel, thereby improving the processing efficiency of the faults.

The method has the advantages that the requirement of the vehicle on the power-on time is met, so that the requirement on the implementation efficiency in the self-checking process is high, at the moment, when an operating system starts an application program, the fault information processing nodes are preferentially started to process each operation node, the vehicle can be started to perform the service function of the computing platform after the detection is passed, and the safe operation of the intelligent driving computing platform is ensured.

Therefore, the invention can also preferentially start the self-checking function to carry out self-checking on the vehicle when the vehicle is started, thereby improving the safety performance and ensuring the stable operation of the vehicle.

Optionally, fig. 8 is a schematic flow chart of fault self-checking at the time of starting another vehicle provided in the embodiment of the present invention, as shown in fig. 8, where, based on the fault self-checking method at the time of starting the vehicle provided in the embodiment of fig. 7, step S703 is further refined, and then the fault self-checking method at the time of starting the vehicle provided in the embodiment includes the following steps:

step S801, an electronic ignition switch state of the vehicle is acquired.

Step S802, if the state of the electronic ignition switch is a starting state, the unprocessed historical fault information in the nonvolatile storage area is read; the historical fault information comprises the fault grade, the fault degree information and the fault type information of the vehicle which are stored last time when the electronic ignition switch state of the vehicle is in the off state.

Step 803, judging whether the fault level in the historical fault information reaches a preset level.

In this step, the preset level may refer to a level at which the vehicle is prohibited from running after the system is set to reach the level, that is, the failure is serious. The operating system of the vehicle may determine whether the failure level in the history failure information read from the nonvolatile memory area reaches a preset level.

Step S804, if at least one of the fault levels reaches a preset level, sending an engine locking command to an engine electronic controller unit of the vehicle.

In this step, since the operating system may establish a communication connection with the engine system of the vehicle according to the diagnostic protocol, after the communication connection is established, if the operating system of the vehicle determines that at least one of the failure levels in the historical failure information reaches the preset level, an engine locking instruction is sent to the engine system, for example, the instruction is 0000001, the engine system locks the engine after receiving the instruction, and returns the instruction to 0000002 to indicate that the locking is successful, and the vehicle owner cannot drive.

If the operating system of the vehicle judges that none of the fault levels in the historical fault information reaches the preset level, the fault level can be formed into prompt information which is sent to the terminal equipment of the user to prompt the user that a certain operation node has a fault, and the user is required to overhaul and process in time. The embodiment of the invention does not limit the specific form of the prompt message, and can be used for sending a message prompt box, wherein the prompt box is provided with buttons such as ' operation node 1 has a fault, please overhaul and process the message prompt in time ', and the buttons are used for reminding a vehicle owner to process the fault in time, and also provided with ' later processing, closing the bullet box ', reminding again at intervals of 2 hours ' and the like for a user to select.

In another possible implementation manner, if the operating system of the vehicle determines that none of the fault levels in the historical fault information reaches the preset level, it may determine whether the vehicle is locked, and if the vehicle is in a locked state, an unlock instruction is first sent to an engine system of the vehicle to unlock. Specifically, if the engine is locked due to the vehicle fault, an unlocking instruction is sent to an engine system of the vehicle to unlock.

Therefore, by acquiring the electronic ignition switch state of the vehicle, whether the fault level in the historical fault information reaches the preset level can be further judged, if the fault level reaches the preset level, an engine locking instruction can be sent to carry out driving limitation, the fault information of the vehicle owner is prompted in advance, and traffic accidents are avoided.

Optionally, when the fault information is stored in the mechanism of the non-volatile memory of the computing platform, the stored data may also be encrypted, and fig. 9 is a flowchart of a method for storing fault information, as shown in fig. 9, where the method steps are performed, including:

and step S901, calling an https encryption protocol to encrypt each item of data in the nonvolatile storage area in a first layer of data.

In this embodiment, https encryption protocol may refer to secure hypertext transfer protocol, which is a secure communication channel developed based on http for exchanging information between a computing platform and a cloud. The method uses a Secure Socket Layer (SSL) for information exchange, which is an HTTP protocol encrypted by TLS/SSL, namely a module for processing encrypted information is added on HTTP.

In this step, if the vehicle needs to store some sensitive data or data to be encrypted, the encrypted data is sent to the fault storage node through the fault information processing node, and specifically, the fault information processing node may call https encryption protocol to encrypt some sensitive data or data to be encrypted with first layer data.

It can be understood that it is possible to artificially set which data in the various data in the nonvolatile storage area are some sensitive data or data to be encrypted, or encrypt all data in the nonvolatile storage area, which is not particularly limited in the embodiment of the present invention.

Step S902, a preset encryption key is set to encrypt the second layer data of each item of data, so as to generate encrypted data and a corresponding encrypted data ID.

In this embodiment, the encryption key may refer to an encryption string that performs encryption and decryption operations on plaintext using the same or symmetric key, and for example, the encryption key may be a 9-bit cipher.

In this step, the fault information processing node may further set a preset encryption key to encrypt certain sensitive data or data to be encrypted with second layer data, for example, set a 9-bit initial password, encrypt the data with second layer data, and further, may generate a corresponding encrypted data ID.

Step 903, sending the encrypted data and the encrypted data ID corresponding to the encrypted data to a cloud device, where the cloud device decrypts the encrypted data based on the encrypted data ID and reads the encrypted data.

In this step, the failure information processing node sends the generated encrypted data ID and the encrypted data to the failure storage node for storage, and accordingly, the failure storage node may store the encrypted data and the encrypted data ID in a nonvolatile storage area in the file system, and further, the failure storage node sends the encrypted data and the encrypted data ID corresponding thereto to the cloud device, where the cloud device decrypts the encrypted data based on the encrypted data ID and reads the encrypted data.

When the fault information processing node encrypts the data, the fault information processing node divides the encrypted data into two types based on the fault type information in advance, and then the fault storage node stores the encrypted data in the corresponding storage areas respectively.

It can be understood that the cloud device can query the encrypted data from the nonvolatile storage area according to the encrypted data ID, and obtain the corresponding encrypted data when the encrypted data ID is queried, and further, the cloud device can decrypt the second layer of data on the encrypted data by using the preset encryption key, and then invoke the https encryption protocol to decrypt the first layer of data, so as to obtain the decrypted data.

Therefore, for some sensitive data and data needing encryption, the encryption service can be called to encrypt two layers of data, so that the security and the reliability are improved.

In this embodiment, the first level may refer to a level corresponding to a vehicle fault with a higher severity, and the second level may refer to a level corresponding to a vehicle fault with a lower severity. The setting of the failure level is used to evaluate the severity of the vehicle failure. For example, a first level fault may cause a safety accident, or a first level fault may cause a driving function failure of the vehicle; the second-level fault does not cause a safety accident, nor does it cause a failure of the driving function of the vehicle. If the oil in the oil tank leaks, serious safety accidents can be caused, and the oil tank is classified as a first-level fault; the driving system fails, so that the vehicle cannot run, the driving function of the vehicle is invalid, and the vehicle is classified as a first-level failure; the network signal is poor, the safety accident can not be caused, the driving function failure of the vehicle can not be caused, and the vehicle is classified as a second-level fault.

In the step, when the first-level fault of the vehicle is determined, a first instruction can be sent to the engine system to control the vehicle to carry out parking processing, and a 4S shop worker can be reminded of carrying out the processing by a short message or a telephone mode. When the second-level fault of the vehicle is determined, a second instruction can be sent to control the vehicle to travel to a vehicle maintenance point according to a preset travel path or a re-planned travel path, and further safety accidents can be avoided.

It can be understood that when the vehicle is controlled to park, the vehicle can find a safe parking place, run at a reduced speed until parking, and light a warning lamp to remind pedestrians and other vehicles; when the vehicle is controlled to travel to a vehicle maintenance point according to a preset travel path or a re-planned travel path, the vehicle enters a low-speed travel mode and returns to the vehicle maintenance point according to the preset travel path, so that pedestrians, other vehicles and the like have sufficient time to avoid during the travel, and the occurrence probability of safety accidents is further reduced.

It should be noted that, in practice, the evaluation criteria of the fault level may be various, the result of classifying the fault level according to the evaluation criteria of the fault level may be various, and the fault level may further include levels of other levels, such as a third level, a fourth level, etc., and the classification of the levels is not specifically limited according to the manner of the present invention, which is just an example.

Therefore, the fault level of the vehicle can be determined to respectively execute different operations, the probability of occurrence of safety accidents is reduced, and the occurrence of traffic accidents is avoided.

In the foregoing embodiment, the vehicle fault handling method provided in the embodiment of the present invention is described, and in order to implement each function in the method provided in the embodiment of the present invention, the electronic device as the execution body may include a hardware structure and/or a software module, and each function may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

Fig. 10 is a schematic structural diagram of a vehicle fault handling apparatus according to an embodiment of the present invention, and as shown in fig. 10, the vehicle fault handling apparatus 100 includes:

The fault monitoring node 1001 is configured to obtain operation data corresponding to a plurality of operation nodes in a vehicle, and extract vehicle fault information from the operation data;

The fault report node 1002 is configured to parse the vehicle fault information to obtain fault reports corresponding to a plurality of operation nodes; the fault report comprises fault degree information, fault type information and diagnosis fault codes; the fault type information comprises system on chip (SoC) end information and Microcontroller (MCU) end information;

a fault information processing node 1003 for determining a fault class of the vehicle according to the fault degree information, the fault type information, and the diagnostic fault code;

the fault storage node 1004 is configured to store, based on the fault type information, a fault level of the vehicle, the fault degree information, and the diagnostic fault code to a nonvolatile storage area in a file system, where the nonvolatile storage area is used for accessing diagnostic communication by a cloud device based on the fault type information.

Optionally, the plurality of operation nodes are registered nodes in advance; the fault monitoring node 1001 is further configured to create an instance for subscribing to the plurality of nodes, and initiate a subscription request to a plurality of running nodes in the vehicle by calling an interface corresponding to the instance; the subscription request is used for acquiring operation data of the plurality of operation nodes;

accordingly, the fault monitoring node 1001 is specifically configured to:

Optionally, the fault reporting node 1002 is specifically configured to:

Optionally, the fault information processing node 1003 is specifically configured to:

Optionally, the failure storage node 1004 is further configured to divide a nonvolatile storage area in the file system into two storage areas based on the failure type information, which are a first storage area and a second storage area, where the first storage area is used to store information from the SoC end, and the second storage area is used to store information from the MCU end;

Accordingly, the failure storage node 1004 is specifically configured to:

Optionally, the device further comprises an acquisition node, a reading node and an execution node;

Specifically, the acquiring node is configured to acquire an electronic ignition switch state of the vehicle;

The reading node is used for reading unprocessed historical fault information in the nonvolatile storage area when the electronic ignition switch state is a starting state; the historical fault information comprises the fault grade, the fault degree information and the fault type information of the vehicle which are stored when the electronic ignition switch state of the vehicle is in the off state last time;

and the execution node is used for executing corresponding actions according to the fault level in the historical fault information.

Optionally, the executing node is specifically configured to:

Optionally, the apparatus further comprises an encryption node, the encryption node being configured to:

Optionally, the fault level includes at least a first level and a second level; the apparatus further comprises a transmitting node, configured to:

when the fault grade of the vehicle is determined to be the first grade, a first instruction is sent to control the vehicle to carry out parking treatment;

And when the fault grade of the vehicle is determined to be the second grade, sending a second instruction to control the vehicle to travel to a vehicle maintenance point according to a preset travel path or a re-planned travel path.

The vehicle fault processing device provided by the embodiment of the present invention can implement the vehicle fault processing method of the embodiments shown in fig. 3 to 9, and its implementation principle and technical effects are similar, and are not repeated here.

Fig. 11 is a schematic hardware structure of a vehicle fault handling apparatus according to an embodiment of the present invention. As shown in fig. 11, the vehicle fault handling apparatus 110 provided by the present embodiment includes: at least one processor 1101 and a memory 1102. The processor 1101 and the memory 1102 are connected by a bus 1103.

In a specific implementation, the at least one processor 1101 executes computer-executable instructions stored in the memory 1102, so that the at least one processor 1101 performs the vehicle fault handling method in the above method embodiment.

The specific implementation process of the processor 1101 may be referred to the above method embodiment, and its implementation principle and technical effects are similar, which is not described herein.

In the embodiment shown in fig. 11, it should be understood that the Processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), other general purpose processors, digital signal Processor (english: DIGITAL SIGNAL Processor, abbreviated as DSP), application-specific integrated Circuit (english: application SPECIFIC INTEGRATED Circuit, abbreviated as ASIC), and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise high speed RAM memory or may further comprise non-volatile storage NVM, such as at least one disk memory.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (PERIPHERAL COMPONENT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present invention are not limited to only one bus or to one type of bus.

The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the vehicle fault processing method of the method embodiment is realized.

The computer readable storage medium described above may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an Application SPECIFIC INTEGRATED Circuits (ASIC). The processor and the readable storage medium may reside as discrete components in a device.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.

Claims

1. The vehicle fault processing method is characterized by being applied to distributed nodes in an SOA heterogeneous platform, wherein the distributed nodes comprise fault monitoring nodes, fault reporting nodes, fault information processing nodes and fault storage nodes which sequentially transmit data, and the method comprises the following steps:

2. The method of claim 1, wherein the plurality of operational nodes are pre-registered nodes; the method further comprises the steps of:

Creating an instance for subscribing the plurality of operation nodes through the fault monitoring node, and initiating a subscription request to the plurality of operation nodes in the vehicle by calling an interface corresponding to the instance; the subscription request is used for acquiring operation data of the plurality of operation nodes;

3. The method of claim 1, wherein resolving the vehicle fault information to obtain fault reports corresponding to a plurality of operating nodes, comprises:

4. The method of claim 1, wherein determining a fault level of a vehicle based on the fault level information, the fault type information, and the diagnostic fault code comprises:

5. The method as recited in claim 1, further comprising:

6. The method as recited in claim 1, further comprising:

acquiring an electronic ignition switch state of a vehicle;

7. The method of claim 6, wherein performing the corresponding action based on the level of failure in the historical failure information comprises:

8. The method as recited in claim 1, further comprising:

9. The method of any one of claims 1-8, wherein the failure levels include at least a first level and a second level; the method further comprises the steps of:

10. A vehicle fault handling apparatus for use with an SOA heterogeneous platform, the apparatus comprising:

11. A vehicle failure processing apparatus characterized by comprising: at least one processor and memory;

The memory stores computer-executable instructions;

The at least one processor executing computer-executable instructions stored in the memory causes the at least one processor to perform the vehicle fault handling method of any one of claims 1 to 9.

12. A computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the vehicle fault handling method of any one of claims 1 to 9.

13. A computer program product comprising program code which, when run on a computer, performs the vehicle fault handling method according to any one of claims 1 to 9.