Software fault processing method and system for vehicle

Abstract

The invention provides a software fault processing method for a vehicle, and the method comprises the steps: receiving fault report information of a vehicle software fault, and the fault report information comprises information for fault diagnosis and a fault source; determining operation data related to the software fault from classified and stored operation data according to the fault reporting information; obtaining the determined operation data; the determined operation data and the fault reporting information are sent to the fault processing end; wherein the operation data are uploaded to a storage end according to settings when the vehicle accesses a network, and are classified and stored in the storage end in a preset mode; wherein the preset mode is related to partial information in the information for fault diagnosis and the fault source. A software fault handling system for a vehicle is also provided.

Description

Technical Field

[0001] The present application relates to vehicle technology, and more specifically, to vehicle software fault handling technology. Background Art

[0002] With the continuous development of intelligent network technology, vehicles include more and more controllers. When these controllers have software failures, the conventional practice is to contact the maintenance station. At the maintenance station, maintenance personnel read the fault information from the vehicle through diagnostic instruments, and then troubleshoot and handle the fault.

[0003] There are currently some software fault solutions that combine remote diagnosis with Over the Air (OTA) technology, but these solutions require the driver to manually report the fault and upload fault diagnosis data after the fault occurs. In fact, when a fault occurs, the driver may not be able to immediately realize the occurrence of the fault, resulting in the failure to report the vehicle's fault information in a timely manner, which poses a safety hazard to the vehicle. Furthermore, manually uploading data is inconvenient. Summary of the invention

[0004] The present application provides a software fault handling technology for a vehicle to solve at least one of the above problems.

[0005] According to one aspect of the present application, a software fault handling method for a vehicle is provided, the method comprising: receiving fault reporting information of a vehicle software fault, the fault reporting information comprising information for fault diagnosis and a fault source; determining, based on the fault reporting information, operating data related to the software fault from classified and stored operating data; acquiring the determined operating data; sending the determined operating data and the fault reporting information to the fault handling end; wherein the operating data is uploaded to a storage end according to settings when the vehicle is connected to a network, and is classified and stored in the storage end in a preset manner; wherein the preset manner is related to part of the information for fault diagnosis and to the fault source.

[0006] Optionally, the software fault handling method for a vehicle also includes: the fault handling end generates update software for at least the software module where the fault source is located based on the received fault reporting information and operating data; and sends the update software via OTA so that the vehicle can update the corresponding part.

[0007] Optionally, in the software fault handling method for a vehicle, the classification and storage in the storage end in a preset manner includes: classifying the operating data level by level; and storing the classified operating data level by level in the storage end.

[0008] Optionally, in the software fault handling method for a vehicle, classifying the operating data step by step includes: performing a first-level classification of the operating data according to the controller; performing a second-level classification of the operating data that has passed the first-level classification according to the software; and performing a third-level classification of the operating data that has passed the first-level classification and the second-level classification according to a predefined signal, thereby completing the step-by-step classification.

[0009] Optionally, in the software fault handling method for a vehicle, storing the operating data after being classified level by level into the storage end includes: storing the operating data after being classified level by level in different memories of the storage end according to software storage classification.

[0010] According to another aspect of the present application, a software fault handling system for a vehicle is also provided, the system comprising: a storage end for storing operating data, the operating data being operating data uploaded according to settings when the vehicle accesses the network and classified and stored in a preset manner; a diagnostic service end, which is connected to each vehicle for communication, for receiving fault reporting information of vehicle software faults, determining operating data related to the software fault in the classified and stored operating data according to the fault reporting information, and sending the determined operating data and the fault reporting information. The preset manner is related to part of the information used for fault diagnosis and to the fault source.

[0011] Optionally, the software fault handling system for a vehicle further includes: a fault handling end. The fault handling end is used to receive the operation data and the fault reporting information sent by the diagnostic service end; analyze the operation data and the fault reporting information to generate update software for at least the software module where the fault source is located; and send the update software via OTA.

[0012] Optionally, in the software fault handling system for a vehicle, the diagnostic service end includes one or more servers, and the server includes: a communication module, which is used to communicate with the vehicle to at least receive the operating data of the vehicle; a memory, which stores instructions; and a processor, which is used to execute the instructions to classify the operating data level by level, and store the classified operating data in the storage end.

[0013] Optionally, in the software fault handling system for a vehicle, when the processor executes the instruction: the operating data is classified at the first level according to the controller; the operating data that has passed the first level classification is classified at the second level according to the software; the operating data that has passed the first level classification and the second level classification is classified at the third level according to a predefined signal, thereby completing the step-by-step classification.

[0014] Optionally, the storage end of the software fault handling system for a vehicle includes multiple memories for storing the classified operating data respectively according to software storage categories. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The present application will be more fully understood by referring to the following detailed description of specific embodiments in conjunction with the accompanying drawings, wherein:

[0016] Figure 1 is a flow chart of a software fault handling method for a vehicle according to some examples of the present application;

[0017] Figure 2 A specific example of operating data classification is shown;

[0018] Figure 3 is a structural schematic diagram of a software fault handling system for a vehicle according to some examples of the present application;

[0019] Figure 4 A schematic diagram of the structure of a server at the diagnostic service end according to an example of the present application is illustrated. DETAILED DESCRIPTION

[0020] In order to help those skilled in the art to accurately understand the subject matter for which protection is sought in the present application, the specific implementation of the present application will be described in detail below in conjunction with the accompanying drawings.

[0021] Figure 1 It is a flowchart of a software fault handling method for a vehicle according to some examples of the present application. Software in the present application includes software set in the vehicle, which is usually executed by or interacts with at least one of the controllers of the various systems of the vehicle. However, the present application does not exclude software that is not set or not all set in the vehicle but is set in other electronic devices / other vehicles but can interact with the present vehicle. For example, software for the interaction between a vehicle and an electronic device such as a smart terminal, even if the software of the smart terminal fails, according to the present application, it may also be processed by the vehicle due to the execution of the embodiments according to the present application. By way of example and not limitation, software faults in the present application may include software faults themselves and hardware faults associated with the software. Here, hardware faults associated with software refer to hardware faults that cause the software to fail to work properly, or abnormalities that can be reflected by the software.

[0022] In step S100, fault reporting information of vehicle software fault is received, wherein the fault reporting information includes information for fault diagnosis and fault source. The information for fault diagnosis is, for example, a diagnostic fault code DTC. Generally speaking, a DTC code can indicate a fault area, a fault code type, a fault system, a fault description, a fault category, and a fault subtype. Fault areas include, for example, power systems, chassis systems, and body systems. Fault code types include, for example, communication faults, functional faults, power supply faults, and hardware faults. The fault system indicates the specific system where the fault is located, such as an ignition system, a braking system, and a vehicle speed control system. The fault description is used to indicate the specific problem that has occurred. The fault category is used to indicate fault information, including general fault information, general electrical faults, general signal faults, frequency modulation or pulse width modulation faults, system internal faults, and algorithm faults. Fault subtypes, each fault category has a different definition. In this application, the fault source is software used to indicate that a fault has occurred, which can be a predefined identifier for a fault source. It should be noted that the fault code type, the specific system where the fault is located, the fault information, etc. given here are all examples, not limitations. In actual applications, fault classification, vehicle system classification, fault information classification, etc. may be different due to various reasons such as vehicle type.

[0023] In step S102, according to the fault reporting information, operating data related to the software fault is determined from the classified and stored operating data.

[0024] According to the present application, the operating data is data uploaded to the storage end according to the settings when the vehicle is connected to the network. For example, the vehicle connects to the cloud through its network communication interface, and uploads the vehicle's operating data to the cloud for storage in the cloud's memory. In the example of the present application, the operating data mainly includes data that helps to diagnose and eliminate vehicle faults, and may include information such as mileage, voltage, vehicle speed, gear, temperature, and time. As an example, the operating data described herein can be used as diagnostic data for diagnosing faults. According to the example of the present application, the operating data can be uploaded according to the settings when the vehicle is connected to the network. For example, the setting can be that the data can be uploaded as long as the vehicle is connected to the network, or the setting is to upload data in a certain period of time after the vehicle is connected to the network, etc. In some examples, the content of the uploaded operating data can also be set as needed.

[0025] According to the example of the present application, the operation data is classified and stored in the cloud storage according to a preset method. The purpose of classifying and storing the operation data according to the preset method is to store the operation data according to a certain logic, so that the required operation data can be easily and quickly obtained when needed. The preset method is related to part of the information used for fault diagnosis and the source of the fault. Therefore, after receiving the fault reporting information, the operation data related to the software fault can be quickly determined based on the part of the information used for fault diagnosis related to the preset method and the source of the fault.

[0026] In step S104, the determined operation data is obtained. The determined operation data related to the software fault involved in the fault reporting information is obtained from the stored operation data.

[0027] In step S106, the determined operation data and fault reporting information are sent to a fault processing end so as to process the software fault.

[0028] When the vehicle is connected to the network, the operating data is automatically uploaded to the storage terminal located in the cloud. After the vehicle sends the fault report information, the operating data related to the fault can be obtained from the operating data as the diagnostic data for diagnosing the fault. Compared with the prior art, the diagnostic data of the vehicle must be manually obtained from the vehicle at the maintenance station through the diagnostic instrument. According to the embodiment of the present application, the diagnostic data can be automatically obtained in a timely and comprehensive manner without the need to manually transmit it using the diagnostic instrument.

[0029] According to some examples of the present application, the software fault handling method for a vehicle also includes step S108 and step S110.

[0030] In step S108, the fault processing end generates update software for at least the software module where the fault source is located based on the received fault reporting information and operating data. In step S110, the update software is sent via OTA so that the vehicle can update the corresponding part, where the corresponding part refers to the part of the software module where the fault source is located where the fault occurs. In some cases, the corresponding part may only be the module where the fault occurs, and in some cases, it may also include the part of the software module where the fault source is located that is associated with the module where the fault occurs. The "update" of software mentioned in this application also includes the "upgrade" of software.

[0031] According to the present application, the vehicle will automatically report fault information when a software fault occurs in the vehicle, unlike the prior art, where the user has to discover the fault of the vehicle and then report the fault to a professional service organization or person such as a repair station. In contrast, the method according to the embodiment of the present application is safer for the vehicle. Furthermore, the fault handling end can analyze the specific software module where the fault is located from the preset classified operating data, so that only that part can be repaired, which is more efficient.

[0032] According to some examples of the present application, the preset method includes classifying the operation data step by step. As an example, the preset method includes classifying the operation data in the first level according to the controller; classifying the classified data in the second level according to the software; and classifying the data in the second level according to the predefined signal. After the classification is completed, the operation data is stored in the corresponding position of the storage end according to the classification.

[0033] The following example illustrates the process of classifying operation data according to the preset method. Figure 2 As shown, the vehicle controller includes, for example, ECU1, ECU2, and ECU3. The software includes software SW1, software SW2, and software SW3. Each software can be further divided into different modules. In this example, the software can be further divided into different modules according to the functions of the software, that is, each module implements a function of the software in which it is located. Software SW1 includes modules SW1MO1 and SW1MO2, software SW2 includes modules SW2MO1 and SW2MO2, and software SW3 includes module SW3MO1. For each module, it can be further divided into different signals.

[0034] Figure 2 The ECU, software, division of software modules, and division of signals listed in the specification are only examples and not limitations. Software SW1 is, for example, CAN communication software, which is used by every ECU; software SW2 is software run by ECU2; and software SW3 is software run by ECU3. The received operating data 200 from the vehicle is first divided into three categories according to the ECU, namely, operating data 200-1 related to ECU1, operating data 200-2 related to ECU2, and operating data 200-3 related to ECU3. Further, the operating data 200-1 related to ECU1 is divided according to the software, such as the operating data 200-1SW1 of the software SW1 and the data of other software of ECU1 not listed here. The operating data 200-2 related to ECU2 is further divided according to the software involved, such as the operating data 200-2SW1 of the software SW1, and the operating data 200-2SW2 of the software SW2. The operation data 200-3 related to ECU3 is further classified according to the software involved, including, for example, the operation data 200-3SW1 related to software SW1, and the operation data 200-3SW3 related to software SW3. Furthermore, the data of each software is further divided into signals through modules. For example, software SW1 as CAN communication software includes a sending module and a receiving module, and each module can further include a handshake signal, a confirmation signal, etc. In this way, the operation data is further refined into signals. Figure 2In the example, for data that has been classified at the second level, that is, classified by software, classification by signal is directly illustrated. For example, the operation data 200-1SW1 is further divided into data 200-1SW1A representing signal A and data 200-1SW1 B representing signal B; the operation data 200-2SW1 is further divided into data 200-2SW1A representing signal A and data 200-2SW1 B representing signal B; the operation data 200-3SW1 is further divided into data 200-3SW1A representing signal A and data 200-3SW1 B representing signal B. The operation data 200-2SW2 is further divided into data 200-2SW2C representing signal C and data 200-2SW2D representing signal D. The operation data 200-3SW3 is further divided into data 200-3SW3E representing signal E and data 200-3SW2F representing signal F.

[0035] Thus, the operation data is classified and stored in the storage end according to the preset method. When the fault reporting information and the fault source are received, all the stored operation data of the software under the ECU can be quickly found according to the software identifier represented by the fault source and the ECU category in the DTC.

[0036] Furthermore, according to the present application, the operating data can also be stored in different memories of the storage end according to the set software storage classification when it is stored. The software storage classification is, for example, to divide the software on the vehicle into basic software, application software, and real-time environment-related software. The basic software, application software, and real-time environment-related software can be stored in different storage areas of the storage end respectively so that they are relatively independent of each other. Generally speaking, the basic software is, for example, the responsibility of the supplier, and the application software is, for example, the responsibility of the vehicle manufacturer. Accordingly, as an example, the operating data related to the basic software can be stored in the supplier's cloud, and the operating data related to the application software can be stored in the vehicle manufacturer's cloud. This arrangement can further ensure the security of data storage, the convenience and flexibility of data transfer, and is conducive to systematization.

[0037] Figure 3 1 is a schematic diagram of a software fault handling system for a vehicle according to some examples of the present application. The system includes a storage end 30 and a diagnostic service end 32. In the diagram, the storage end 30 may include multiple memories, such as a memory 300, a memory 302, and a memory 304. The diagnostic service end 32 may include one or more diagnostic servers, such as the following: Figure 4The server 320 shown in FIG. By way of example and not limitation, both the storage end 30 and the diagnostic service end 32 may adopt cloud technology. The storage end 30 is used to store operating data. The operating data is data uploaded by the vehicle 40 according to the settings when it accesses the network, and the uploaded operating data is classified and stored in the storage end 30 in a preset manner. The diagnostic service end 32 is connected to each vehicle for communication, and is used to receive fault reporting information of vehicle software faults, determine the operating data related to the software fault in the classified stored operating data according to the fault reporting information, and send the determined operating data and fault reporting information, wherein the fault reporting information includes information for fault diagnosis and the source of the fault. In many embodiments, the fault reporting information is actively reported by the vehicle in which the fault occurs. In some possible cases, the diagnostic service end may also obtain fault information from the vehicle when it fails by actively obtaining it. In this example, the preset method is related to part of the information used for fault diagnosis and to the source of the fault, so that after receiving the fault reporting information, the diagnostic server 32 can quickly determine the data related to the software fault in the operating data stored in the storage end 30 based on the fault reporting information and part of the information related to the preset method and the source of the fault.

[0038] According to some examples of the present application, the diagnostic service end 32 receives the operation data uploaded by the vehicle when it accesses the network, and classifies the received operation data according to a preset method, and then the storage end 30 stores the classified operation data. As an alternative, a communication interface and a control module may be provided at the storage end 30, and the communication interface is connected to the vehicle and receives the operation data from the vehicle, and the control module classifies and stores the received operation data according to a preset method. Figure 2 A specific example is described, which is applicable to the software fault handling system according to the example of this application. For the sake of brevity, the description will not be repeated.

[0039] According to some examples of this application, Figure 3 The system shown may also include a fault processing terminal 50. The fault processing terminal 50 receives the fault reporting information and the determined operation data related to the software fault sent by the diagnostic service terminal 32. It generates update software for at least the software module where the fault source is located, and sends the update software out through OTA so that the vehicle 40 receives and updates the corresponding part.

[0040] Figure 4 The schematic diagram of the structure of a server of the diagnostic service end according to the example of the present application is illustrated. The server 320 of the server end 32 is a representative of the servers in the server end 32, which includes the basic structure of each server. In actual configuration, the specific structure of each server located in the cloud may be slightly different, but may include the basic structure as illustrated in the server 320.

[0041] The server 320 includes a communication module 3200, a processor 3202, and a memory 3204. The communication module 3200 receives communication data from the vehicle, including the vehicle's operating data, the vehicle's fault reporting information, etc. The memory 3204 at least stores instructions executed by the processor 3202. The processor 3202 is used to execute the instructions stored in the memory 3204, which enable the processor 3202 to classify the operating data according to a preset method after receiving the operating data, and store the classified operating data in the storage end 30 (see Figure 3 ).

[0042] According to some examples of the present application, the storage end 30 includes different storage servers, and the classified operation data is further stored in the corresponding storage server according to the software storage classification. According to some specific examples, the software storage classification divides the software into basic software, application software and real-time environment related software, and the storage end 30 includes three corresponding servers, namely, server 300 for storing operation data related to basic software, server 302 for storing operation data related to application software, and server 304 for storing operation data of real-time environment related software.

[0043] Although combined with Figure 3 , Figure 4 In the description, the operating data is classified by the diagnostic server in a preset manner, but other methods are also feasible. For example, as an alternative, a controller can be set at the storage end 30, which classifies and stores the operating data received by the diagnostic server in a preset manner. Or, for example, a controller independent of the storage end 30 and the diagnostic server 32 can be set, which classifies the operating data received by the diagnostic server in a preset manner and controls the storage end 30 to store accordingly. In some cases, the storage end 30 can also directly receive the operating data of the vehicle through a communication interface set thereon.

[0044] The software fault processing method for a vehicle according to the present application may be executed in a software fault processing system for a vehicle according to an example of the present application.

[0045] Please also refer to Figures 1 to 3 When the vehicle 40 is connected to the network, it uploads its operating data according to the settings (for example, automatically and in real time). The operating data includes, for example, Figure 2 The diagnostic server 32 receives the operating data from the vehicle 40 and performs the following operations according to the Figure 2 As an example, the classified operating data can be stored in different memories of the server 30 according to the software storage classification.

[0046] When the software of the vehicle 40 fails, the fault reporting information is uploaded to the diagnostic server 32 (step S100). In this example, the software SW1 fails. As an example, the reported fault information will include information for fault diagnosis and the source of the fault. The source of the fault is the identifier of the software SW1, which can be predefined, such as SW1; the information for fault diagnosis indicates the system controller involved in the fault, such as ECU1. The diagnostic server 32 determines (step S102) the operating data related to the software fault from the operating data stored in the storage end 30 according to the fault source in the fault reporting information and part of the information for fault diagnosis. Specifically, the software involved can be quickly determined according to the identifier of the software SW1 of the fault source, and further, the system controller involved can be determined according to the fault diagnosis information, thereby determining that the operating data related to the software SW1 of ECU1 is needed, for example, including the operating data 200-1SW1, and the data 200-1SW1 has been refined into data 200-1SW1A representing signal A and data 200-1SW1 B representing signal B. Therefore, the diagnostic service end 32 obtains (step S104 ) the operation data related to the software SW1 of the ECU1 in the recent period from the storage end 30 , and sends it together with the fault reporting information (step S106 ) to the fault processing end 50 .

[0047] After receiving the fault reporting information and the operation data, the fault processing end 50 analyzes them. Specifically, after receiving the detailed data of the operation data 200-1SW1, that is, the data 200-1SW1A representing the signal A and the data 200-1SW1 B representing the signal B, the fault processing end 50 analyzes whether the two signals are normal or abnormal, and when it is found that, for example, the data 200-1SW1A representing the signal A is abnormal, only the module of SW1 corresponding to the signal A can be repaired, such as updating or upgrading the part of the software module.

[0048] It can be seen that since the operation data is stored in a preset fractional format, on the one hand, it has been stored in a detailed manner according to the controller, software, etc., making it easy to find the operation data related to it according to the fault reporting information, that is, the diagnostic data for the fault. On the other hand, because the data is refined into signals, as long as the signal is judged to be normal or not, it is possible to know where the fault occurs specifically, so as to solve the problem in a targeted manner.

[0049] In various examples of the present application, a vehicle may include one or more vehicles, such as Figure 3 There may be multiple vehicles 40 shown in the figure. In this case, the uploaded operation data will have an identification indicating the vehicle to which it belongs when it is stored, for example, the identification of the vehicle is realized by a tag. Therefore, the classified operation data also includes the identification indicating the vehicle, and the reported fault reporting information also has the vehicle identification.

[0050] In the example of the present application, the classified and stored operation data can be set to be deleted periodically, for example, once a month.

[0051] In the example of this application, when the diagnostic service sends operating data to the fault processing end, the operating data sent may be the operating data of the corresponding vehicle in the last few hours, days, weeks or months, which can be set according to actual needs. However, it should be understood that in the case of periodic deletion of classified stored operating data, the data sent is the operating data in the undeleted data.

[0052] The present application has described various examples, and it should be understood that the features of the various examples can be combined with each other to form new implementation methods without contradicting each other.

[0053] Although specific embodiments of the present application have been shown and described in detail to illustrate the principles of the present application, it should be understood that the present application can be implemented in other ways without departing from such principles.

Claims

1. A software fault handling method for a vehicle, characterized in that: The method comprises: Receiving fault reporting information of a vehicle software fault, wherein the fault reporting information includes information for fault diagnosis and a fault source; Determining, according to the fault reporting information, operating data related to the software fault from the classified and stored operating data; obtaining the determined operating data; Sending the determined operation data and the fault reporting information to the fault processing end; Wherein, the operation data is uploaded to the storage end according to the settings when the vehicle is connected to the network, and is classified and stored in the storage end in a preset manner; The preset method is related to part of the information used for fault diagnosis and to the fault source.

2. The method according to claim 1, characterized in that The method further comprises: The fault processing terminal generates update software for at least the software module where the fault source is located according to the received fault reporting information and operation data; and The updated software is sent via OTA so that the vehicle can update the corresponding parts.

3. The method according to claim 1 or 2, characterized in that: The storing in the storage end in a preset manner includes: Classifying the operation data level by level; The operation data classified level by level is stored in the storage end.

4. The method according to claim 3, characterized in that Classifying the operation data step by step includes: Performing a first-level classification of the operating data according to the controller; Performing a second-level classification on the operating data that has undergone the first-level classification according to software; The operation data that has undergone the first-level classification and the second-level classification is subjected to the third-level classification according to a predefined signal, thereby completing the step-by-step classification.

5. The method according to claim 3, characterized in that: The step of storing the classified operation data into the storage end includes: The operation data classified level by level are stored in different memories of the storage end according to software storage classification.

6. A software fault handling system for a vehicle, characterized in that: The system comprises: A storage terminal, used to store operation data, wherein the operation data is operation data uploaded according to settings when the vehicle is connected to the network and classified and stored in a preset manner; The diagnostic server is connected to each vehicle for: Receive fault reporting information of vehicle software faults; Determining, according to the fault reporting information, the operating data related to the software fault from the classified and stored operating data; and Sending the determined operating data and the fault reporting information; The preset method is related to part of the information used for fault diagnosis and to the fault source.

7. The system according to claim 6, characterized in that The system further comprises: The fault handling end is used to: Receiving the operation data and the fault reporting information sent by the diagnosis server; Analyzing the operation data and the fault reporting information to generate update software at least for the software module where the fault source is located; and The update software is sent via OTA.

8. The system according to claim 6 or 7, characterized in that: The diagnostic service end includes one or more servers, and the servers include: a communication module, configured to be communicatively connected with the vehicle to at least receive the operating data of the vehicle; Memory, which stores instructions; The processor is used to execute the instructions to classify the operation data level by level, and store the classified operation data in the storage end.

9. The system according to claim 8, characterized in that When the processor executes the instruction: Performing a first-level classification of the operating data according to the controller; Performing a second-level classification on the operating data that has undergone the first-level classification according to software; The operation data that has undergone the first-level classification and the second-level classification is subjected to the third-level classification according to a predefined signal, thereby completing the step-by-step classification.

10. The system according to claim 8, characterized in that The storage end includes a plurality of memories for storing the classified operation data respectively according to software storage classification.

Images