WO2024017072A1 - 车辆的故障信息处理方法、装置、存储介质和处理器 - Google Patents

车辆的故障信息处理方法、装置、存储介质和处理器 Download PDF

Info

Publication number
WO2024017072A1
WO2024017072A1 PCT/CN2023/106195 CN2023106195W WO2024017072A1 WO 2024017072 A1 WO2024017072 A1 WO 2024017072A1 CN 2023106195 W CN2023106195 W CN 2023106195W WO 2024017072 A1 WO2024017072 A1 WO 2024017072A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
current
level
vehicle
information
Prior art date
Application number
PCT/CN2023/106195
Other languages
English (en)
French (fr)
Inventor
刘兴
于钊
刘元治
韩衍东
吴骄阳
高泽天
Original Assignee
中国第一汽车股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国第一汽车股份有限公司 filed Critical 中国第一汽车股份有限公司
Publication of WO2024017072A1 publication Critical patent/WO2024017072A1/zh

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0262—Confirmation of fault detection, e.g. extra checks to confirm that a failure has indeed occurred
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808—Diagnosing performance data
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24065—Real time diagnostics

Definitions

  • the embodiments of the present application relate to the field of vehicle technology, specifically, to vehicle fault information processing methods, devices, storage media, and processors.
  • the vehicle's control component can record the fault and perform related fault processing. However, it only simply stores the fault and performs simple fault elimination after the fault disappears. It will not be based on the current vehicle status. Make comprehensive considerations to determine how to store and clear faults. This fault storage clearing mechanism may interfere with the subsequent search for the cause of the problem, affect problem analysis, and make it inconvenient to find the real cause of the problem and solve the problem.
  • Embodiments of the present application provide a vehicle fault information processing method, device, storage medium and processor to at least solve the technical problem of unreasonable fault storage when a vehicle fault occurs.
  • a vehicle fault information processing method which includes: obtaining fault information of a current fault of the vehicle within the current driving cycle; determining that the current fault is a coded fault based on the fault information, and obtaining the vehicle's fault information.
  • Current storage space in response to the current storage space being less than the target threshold, obtain the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space, where the fault level is used to indicate the impact of the corresponding fault on the safe driving of the vehicle.
  • the stored information of the current fault is determined, where the stored information is used to indicate whether the fault will be The information is stored in the current storage space.
  • the current fault is a coded fault
  • the current storage space of the vehicle is obtained, including: determining the fault level of the current fault based on the fault information; determining the current fault level based on the fault level of the current fault. Whether the fault is a code storage fault; in response to the current fault being a code storage fault, obtain the current storage space of the vehicle.
  • determining the storage information of the current fault includes: in response to the fault level of the current fault being higher than the fault level of the historical fault, storing the fault information of the current fault to the current fault. storage space; or, in response to the fact that the fault level of the current fault is not higher than the fault level of the historical fault, the fault information of the current fault is reported to the server.
  • the method also includes: determining the fault information of the target historical fault from the fault information of historical faults stored in the current storage space, where the target historical fault is any fault in the historical faults; based on whether the target occurs within the current driving cycle Historical faults, determine the current number of fault clearing driving cycles of the target historical fault, where the current number of fault clearing driving cycles is used to indicate the number of driving cycles required to clear the target historical fault from the current storage space.
  • determining the current fault clearing driving cycle number of the target historical fault includes: in response to the occurrence of the target historical fault in the current driving cycle, clearing the current fault corresponding to the target historical fault and driving.
  • the number of cycles is set to the initial value; in response to the target fault not occurring in the current driving cycle, the number of current fault clearing driving cycles corresponding to the target historical fault is decremented by 1.
  • a vehicle fault information processing device including: a first acquisition component, configured to acquire fault information of a current fault of the vehicle within the current driving cycle; a second acquisition component, configured to Based on the fault information, it is determined that the current fault is a coded fault, and the current storage space of the vehicle is obtained; the third acquisition component is configured to obtain the fault level of the current fault and the fault level of the vehicle stored in the current storage space in response to the current storage space being less than the target threshold.
  • the fault level of the historical fault where the fault level is used to indicate the impact of the fault on the safe driving of the vehicle.
  • the first determination component is set to be based on the current
  • the fault level of the fault and the fault level of the historical fault determine the storage information of the current fault, where the storage information is used to indicate whether to store the fault information to the current storage space.
  • the second acquisition component includes: a second determination component, configured to determine the fault level of the current fault based on the fault information; and a third determination component, configured to determine whether the current fault is a coded fault based on the fault level of the current fault. ;
  • the fourth acquisition component is configured to acquire the current storage space of the vehicle in response to the current fault being a code storage fault.
  • a computer-readable storage medium includes a stored program, wherein when the program is run, the device where the computer-readable storage medium is located is controlled to execute the vehicle fault information processing method according to the embodiment of the present application.
  • a processor is also provided.
  • the processor is set up to run programs, When the program is running, the vehicle fault information processing method according to the embodiment of the present application is executed.
  • a vehicle is also provided, and the vehicle is configured to execute the vehicle fault information processing method of the embodiment of the present application.
  • the fault information of the vehicle failure within the current driving cycle is obtained; when it is determined that the current fault is a coded fault based on the fault information, the current storage space of the vehicle is obtained; in response to the current storage space being less than the target threshold, the current storage space of the vehicle is obtained.
  • the fault level of the current fault and the fault level of the vehicle's historical faults stored in the current storage space; based on the fault level of the current fault and the fault level of the historical fault, the storage information of the current fault is determined.
  • when the current storage space is less than the target threshold it can also be determined based on the fault level of the current fault and the fault level of historical faults whether to store the fault information of the current fault in the storage space.
  • This fault storage mechanism Being able to reasonably store faults based on their fault levels can avoid the situation where serious faults cannot be stored, achieve the technical effect of reasonably storing faults, and facilitate subsequent analysis and location of fault causes, and solve the problem when a vehicle fails. , technical problems caused by unreasonable fault storage.
  • Figure 1 is a flow chart of a vehicle fault information processing method according to an embodiment of the present application
  • FIG. 2 is a flow chart of another vehicle fault information processing method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a vehicle fault information storage process according to an embodiment of the present application.
  • Figure 4 is a schematic flowchart of clearing fault information of a vehicle according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a vehicle fault information processing device according to an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a processor according to an embodiment of the present application.
  • an embodiment of a vehicle fault information processing method is provided. It should be noted that the steps shown in the flow chart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, Also, although a logical order is shown in the flowchart diagrams, in some cases the steps shown or described may be performed in a different order than herein.
  • Figure 1 is a flow chart of a vehicle fault information processing method according to an embodiment of the present application. As shown in Figure 1, the method may include the following steps:
  • Step S101 Obtain the fault information of the current fault of the vehicle in the current driving cycle.
  • the vehicle's control component can start to work, that is, the vehicle's control component can start to detect whether the vehicle malfunctions within the current driving cycle.
  • the control component detects that the vehicle
  • the fault information of the current fault on the vehicle can be obtained.
  • the fault information may include the fault level of the fault, the fault code corresponding to the fault, the number of fault clearing driving cycles of the fault, etc., which are not specifically limited here.
  • the current fault may be one or multiple.
  • the driving cycle can be divided into an IG cycle, a sleep-wake cycle, and a warm-up cycle.
  • the vehicle from ignition (key on) to flameout (key off) can be called an IG cycle; the vehicle's wake-up to sleep is called a sleep wake-up cycle; the vehicle starts from key on until the engine reaches 70 degrees Celsius and When the temperature is higher than 25 degrees Celsius when the key is on, it is called a warm-up cycle.
  • driving cycles can also be divided into more types of cycles, which are not limited here.
  • Step S102 Based on the fault information, it is determined that the current fault is a code storage fault, and the current storage space of the vehicle is obtained.
  • the control component can determine the fault level of the current fault from the fault information, and then determine the fault level based on the current fault.
  • the fault level determines the coding type of the current fault, where the coding type of the fault includes coding faults and non-coding faults. It should be noted that the fault level of this fault is used to indicate the impact of this fault on vehicle safety. The degree of impact on safe driving of the vehicle, among which, the higher the fault level, the more serious the impact of the fault on the safe driving of the vehicle.
  • the fault level can be divided into level one, level two, and level three according to the severity of the impact of the fault on safe driving of the vehicle.
  • the seriousness of the impact of the third-level fault on the safe driving of the vehicle is greater than that of the second-level fault on the safe driving of the vehicle.
  • the impact of the second-level fault on the safe driving of the vehicle is more serious than the impact of the first-level fault on the safe driving of the vehicle.
  • the severity of the impact on driving that is, the higher the fault level, the more serious the impact of the fault on the safe driving of the vehicle.
  • faults with a fault level not greater than one level can be determined as non-coded faults, and faults with a fault level greater than one level can be determined as coded faults.
  • a certain fault when a certain fault is a non-coded fault, it means that the fault information of the fault cannot be stored in the storage space, and the fault information of the fault cannot be read from the storage space through the diagnostic instrument later.
  • the fault information of the fault when a certain fault is a coded fault, the fault information of the fault can be stored in the storage space. Subsequently, the fault information of the fault can be read from the storage space through the diagnostic instrument and the fault can be analyzed.
  • the current fault may be one or multiple. Based on this, when the current fault is one, the control component can determine whether the fault level of the current fault is greater than level one, and then Determine whether the current fault is a code storage fault. Similarly, when there are multiple current faults, the control component can also determine whether the fault level of each current fault in the multiple current faults is greater than one, and then determine whether the multiple current faults are coded faults.
  • the control component can obtain the current storage space of the vehicle, and then determine the cause of the current fault based on the current storage space of the vehicle. Store information.
  • Step S103 In response to the current storage space being less than the target threshold, obtain the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space.
  • the control component when the current storage space is less than the target threshold, it means that the current storage space may be insufficient, and the fault information of the current fault may not be stored in the storage space.
  • the control component The fault level of the current fault and the fault level of the historical faults stored in the current storage space can be obtained, and then based on the fault level of the current fault and the fault level of the historical faults stored in the current storage space, it is determined whether to store the fault information of the current fault. Save to storage space.
  • the target threshold can be set in advance. For example, assuming that the vehicle's storage space can store up to n items of fault information, the target threshold can be set to 1. There is no specific restriction here.
  • control The component can obtain the fault level of the current fault from the fault information of the current fault.
  • the control component can also obtain the fault level of each historical fault from the fault information of historical faults that have been stored in the current storage space. Then, based on the current fault, The fault level and the fault level of the historical faults stored in the current storage space are used to determine the storage information of the current fault.
  • Step S104 Determine the stored information of the current fault based on the fault level of the current fault and the fault level of historical faults.
  • control component after determining the fault level of the current fault and the fault level of historical faults, the control component can determine the stored information of the current fault based on the fault level of the current fault and the fault level of historical faults.
  • control component can compare the fault levels of the multiple current faults with the fault levels of multiple historical faults stored in the current storage space, and then determine the fault of the multiple current faults. Whether the level is higher than the fault level of the multiple historical faults.
  • the control unit may generate the current fault.
  • the storage information is used to instruct the fault information of the current fault to be stored in the current storage space.
  • the control component can replace the fault information of the historical fault with the fault information of the current fault. That is, the control component can store the fault information of the current fault in the current storage space and delete the fault information of the historical fault.
  • the control component can generate fault information of the current fault, and the fault information is used to indicate reporting the fault information of the current fault, where , the control component can report the fault information of the current fault to the server, and the server can handle the current fault according to the fault processing policy, but the control component cannot store the fault information of the current fault in the current storage space.
  • the control component can compare the fault level of each current fault in the multiple current faults with the fault levels of multiple historical faults stored in the current storage space, and then generate storage information for each current fault.
  • the above-mentioned steps S101 to S104 of this application obtain the fault information of the vehicle failure within the current driving cycle.
  • the current storage space of the vehicle is obtained; in response to the current storage space being less than the target threshold, the current storage space of the vehicle is obtained.
  • the fault level of the current fault and the historical faults already stored in the current storage space can also be used.
  • the fault level is used to determine the storage information of the current fault.
  • This fault storage mechanism can reasonably store faults based on the fault level, and can avoid the situation where serious faults occur but cannot be stored. Now, the technical effect of reasonable fault storage is achieved, and the technical problem of unreasonable fault storage when a vehicle fails is solved.
  • step S102 determines that the current fault is a coding fault based on the fault information, and then obtains the current storage space of the vehicle.
  • the coded fault type is divided into coded faults and non-coded faults.
  • the control component first determines whether the current fault is a coded fault. If the current fault is a coded fault, If a fault occurs, the control component can obtain the current storage space of the vehicle, and then determine the storage information of the current fault based on the current storage space of the vehicle.
  • the fault information of each fault may include the fault level of the fault, the fault code corresponding to the fault, and the number of fault clearing driving cycles of the fault.
  • the vehicle fault mapping relationship table is pre-stored in the control component.
  • the vehicle fault mapping relationship table can be as shown in Table 1 below.
  • the vehicle fault mapping relationship table can also have other setting methods, which are not specifically limited here.
  • the control component can obtain the fault level of each current fault from the fault information of each of the multiple current faults, and then based on each of the multiple current faults The fault level of the current fault and the fault mapping relationship table of the vehicle determine whether each of the multiple current faults is a coded fault.
  • the control component obtains from the fault information of the current fault that the fault level of the current fault is level one.
  • the control component The fault level that is consistent with the fault level of the current fault can be searched from the vehicle's fault mapping relationship table according to the fault level of the current fault, and then the code storage type corresponding to the found fault level is used as the code storage type of the current fault. That is, the code storage type of the current fault is a non-code storage fault.
  • the control component can determine the coding type corresponding to each of the multiple current faults.
  • control component can also refer to the above method to determine the code type of the current fault, which will not be described again here.
  • the control component can perform corresponding processing on the current fault based on the coding type of the current fault.
  • the control component can report the fault information of the current fault to the server, and the server can process the current fault based on the fault information of the current fault, but the control component will not process the current fault.
  • the fault information of the fault is stored in the storage space.
  • the control component can obtain the current storage space of the vehicle, and then determine whether the current storage space is sufficient.
  • step S103 in response to the current storage space being less than the target threshold, obtain the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space.
  • the control component when responding that the current storage space is less than the target threshold, the control component may obtain the fault level of the current fault and the fault level of the historical faults stored in the current storage space.
  • the fault level is used to indicate the impact of the current fault on the safe driving of the vehicle. The higher the fault level of the current fault, the higher the impact of the current fault on the safe driving of the vehicle.
  • the control component can obtain the fault level of the current fault and the historical faults of the vehicle stored in the current storage space. the fault level, and then based on the fault level of the current fault and the fault level of historical faults, it is further determined whether the fault information of the current fault should be stored in the current storage space.
  • the fault information of the fault includes the fault level of the fault, the fault code corresponding to the fault, and the number of fault clearing driving cycles of the fault.
  • the control component can obtain the fault information from the current fault. Obtain the fault level of the current fault from the system, and determine the fault level of each historical fault from the fault information of each historical fault stored in the storage space.
  • the current storage space is not less than the target threshold, it means that the current storage space is sufficient, and the fault information of the current fault can be stored in the current storage space.
  • step S104 determines the stored information of the current fault based on the fault level of the current fault and the fault level of historical faults.
  • the control component can determine the storage information of the current fault based on the fault level of the current fault and the fault level of the historical fault, wherein the fault information is used to indicate whether to store the current fault.
  • the fault is stored in the current storage space.
  • control component can determine the cause of the current fault from the fault information of the current fault. fault level, and determine the fault level of each historical fault from the fault information of historical faults stored in the storage space. After that, the control component can determine whether to proceed based on the fault level of the current fault and the fault level of historical faults stored in the storage space. Store the fault information of the current fault in the current storage space.
  • the control component can compare the fault level of the current fault with the fault level of each historical fault, if the fault level of the current fault is higher than the fault level of a certain historical fault , then the control component can generate the storage information of the current fault.
  • the storage information of the current fault is used to instruct the control component to store the fault information of the current fault into the current storage space.
  • the control component can store the fault level in the storage space that is lower than the fault level of the current fault.
  • the fault information of the historical faults of the level is cleared, and then the fault information of the current fault is stored in the current storage space.
  • the control component can compare the fault levels of the multiple historical faults again, and then compare the one with the lowest fault level among the multiple historical faults.
  • the fault information of the fault is cleared from the current storage space, and the fault information of the current fault is stored in the current storage space.
  • the control component can generate storage information of the current fault, and the storage information is used to instruct the control component to report the fault information of the current fault to the server.
  • the server can handle the current fault according to the fault handling strategy.
  • the control component may compare the fault level of each current fault in the multiple current faults with the fault level of each historical fault, if there is a fault in the multiple current faults. If the fault level is higher than the fault level of the historical fault, the control component can clear the fault information of the historical fault that the fault level is lower than the fault level of the current fault stored in the current storage space, and store the fault information of the current fault. to the current storage space. If the fault levels of the multiple current faults are lower than the fault levels of historical faults, the control component can report the fault information of the multiple current faults to the server, and the server can process the multiple current faults according to the fault processing strategy. .
  • the control component can clear the fault information of the two historical faults from the current storage space. Then, the control component can also compare the fault levels of the five current faults, and then compare the five current faults with the higher fault level. The fault information of the two current faults is stored in the current storage space.
  • the fault information of a vehicle failure within the current driving cycle can be obtained.
  • the current fault is determined to be a coded fault based on the fault information
  • the current storage space of the vehicle is obtained; in response to the current storage space being less than the target threshold, the current storage space of the current fault is obtained.
  • the fault level is the same as the fault level of the historical fault of the vehicle stored in the current storage space; based on the fault level of the current fault and the fault level of the historical fault, the storage information of the current fault is determined.
  • the current storage space when the current storage space is less than the target threshold, it can also be determined based on the fault level of the current fault and the fault level of historical faults whether to store the fault information of the current fault.
  • This fault storage mechanism can be based on the fault level of the fault.
  • Reasonable storage of faults at fault levels can avoid the situation where serious faults occur but cannot be stored. It achieves the technical effect of reasonably storing faults and facilitating subsequent analysis and location of fault causes. It also solves the problem of insufficient fault storage when a vehicle fails. Reasonable technical issues.
  • FIG. 2 is a flow chart of a vehicle fault information processing method according to an embodiment of the present application. As shown in Figure 2, the method may include the following steps:
  • Step S201 Determine the fault information of the target historical fault from the fault information of historical faults stored in the current storage space.
  • the control component can determine the fault information of the target historical fault from the historical faults stored in the current storage space, where the target historical fault is any fault in the historical faults. After determining the target historical fault, the control component can obtain the current number of fault clearing driving cycles of the target historical fault. It should be noted that the number of fault clearing driving cycles required for faults of different fault levels is different. Among them, the higher the fault level, the greater the number of fault clearing driving cycles required, to preset the number of fault clearing driving cycles for each fault level. The number of fault clearing drive cycles required for the fault.
  • the number of fault clearing driving cycles required for each fault level can also be set in other ways, which are not specifically limited here.
  • Step S202 Based on whether the target historical fault occurs within the current driving cycle, determine the number of current fault clearing driving cycles for the target historical fault.
  • the control component can determine the number of current fault clearing driving cycles of the target historical fault based on whether the target historical fault occurs within the current driving cycle. Among them, when the target historical fault occurs in the current driving cycle, the current fault clearing driving cycle number corresponding to the target historical fault is set to the initial value; when the target historical fault does not occur in the current driving cycle, the current fault corresponding to the target historical fault is set to the initial value. Clear drive cycle count minus 1.
  • the target historical fault is a secondary fault
  • the current number of fault clearing driving cycles for the target historical fault is 25 times.
  • the initial value of the number of fault clearing driving cycles for a secondary fault is 30.
  • the current fault clearing driving cycle number of the target historical fault will be Set as the initial value, that is, the current fault clearing driving cycle number of the target historical fault is set to 30 times; if the target historical fault does not occur in the current driving cycle, the target historical fault will be The current fault clearing driving cycle number of the target historical fault is reduced by 1, that is, the current fault clearing driving cycle number of the target historical fault is set to 24 times.
  • the number of fault driving cycles of the target historical fault is set to the initial value. If the target historical fault does not occur in the next driving cycle, the number of fault driving cycles of the target historical fault is set to the initial value. The number of fault driving cycles is reduced by 1. According to this method, when the number of fault clearing driving cycles of the target historical fault is reduced to 0, the fault information of the target historical fault will be automatically cleared from the current storage space.
  • the above steps S201 to S202 of this application can determine the fault information of the target historical fault from the fault information of the historical fault stored in the current storage space; based on whether the target historical fault occurs within the current driving cycle, determine the current fault of the target historical fault. Clear the number of drive cycles. Among them, if the target historical fault occurs in the current driving cycle, the current fault clearing driving cycle number corresponding to the target historical fault is set to the initial value; if the target historical fault does not occur in the current driving cycle, the target historical fault corresponding to The number of current fault clearing driving cycles is reduced by 1. That is to say, in the embodiment of the present application, the number of fault clearing driving cycles of historical faults stored in the storage space can be set according to whether the historical fault occurs again in the next driving cycle. This method determines the fault based on the frequency of fault occurrence.
  • the fault clearing mechanism that clears the required number of times is more flexible and can ensure that frequently occurring faults are stored in the storage space for subsequent analysis and processing of the fault.
  • step S202 determines the number of current fault clearing driving cycles of the target historical fault based on whether the target historical fault occurs within the current driving cycle.
  • the control component can also determine the target historical fault from the fault information of the target historical fault.
  • the current number of fault clearing driving cycles It should be noted that after the target historical fault is successfully stored in the current storage space, the number of fault clearing driving cycles for the target historical fault begins to take effect. That is, when the target historical fault does not occur again in the next driving cycle, the target historical fault will The number of fault clearing driving cycles for a fault is automatically decremented by 1.
  • the control component can obtain the current number of fault clearing driving cycles of the target historical fault from the fault information of the target historical fault.
  • the control component can manage the number of fault clearing driving cycles for each historical fault.
  • the fault information of the target historical fault can be determined from the fault information of the historical fault stored in the current storage space; based on whether the target historical fault occurs within the current driving cycle, the number of current fault clearing driving cycles of the target historical fault is determined.
  • the current fault clearing driving cycle number corresponding to the target historical fault is set to the initial value; if the target historical fault does not occur in the current driving cycle, the target historical fault corresponding to The number of current fault clearing driving cycles is reduced by 1. That is to say, in the embodiment of the present application, the number of fault clearing driving cycles of historical faults stored in the storage space can be set according to whether the historical fault occurs again in the next driving cycle.
  • This method determines the fault based on the frequency of fault occurrence.
  • the fault clearing mechanism that clears the required number of times is more flexible and can ensure that frequently occurring faults are stored in the storage space for subsequent analysis and processing of the fault.
  • the vehicle's control component can store the fault information of each fault in the order in which the fault occurs, but it will no longer store it when the storage space is full.
  • the fault information can also be cleared simply after the fault is eliminated.
  • This fault storage clearing mechanism is relatively simple and difficult to apply to complex working conditions.
  • the system consists of a storage component, a vehicle control processor component, an information interaction device, vehicle real-time information
  • the display component is composed of a real-time communication between the vehicle's real-time information and the vehicle control processor component; the fault information of the vehicle's real-time information is analyzed and stored through the vehicle control processor component, and the fault information is displayed on the display component through the information interaction device.
  • Visual display helps analyze and count the types and numbers of fault information that occur in the vehicle; when the vehicle fails, the real-time fault status of the vehicle can be detected; when there is no fault, the historical fault information of the vehicle can be viewed.
  • an alarm prompt is given through the display component.
  • This fault storage and detection method is mainly used to count the frequency of fault occurrences, but it cannot manage faults.
  • an electric vehicle fault diagnosis and processing method includes a vehicle control component, which includes a hardware layer, an underlying platform software layer, and an application software layer.
  • the application software layer detects faults in the electric vehicle system based on the status information of each component; assigns a unique fault code to the fault and transmits the fault code to the underlying platform software layer; the underlying platform software layer further confirms the fault and The confirmed fault is stored in the memory; the application software layer reads the fault information from the memory and performs corresponding action processing according to the action processing parameter settings; the alarm light is operated according to the lighting parameter settings.
  • This method mainly describes the process of fault identification and processing, and mainly optimizes fault confirmation, but does not plan the storage and clearing mechanism of fault codes, and cannot realize the function of fault management.
  • a hybrid vehicle troubleshooting method and its troubleshooting system are proposed.
  • a hybrid vehicle fault handling method includes the following steps: detecting the current fault type of each component of the hybrid vehicle, determining the fault level of each component according to the fault type; mapping to obtain each zero based on the fault level of each component The fault response level of the component; determine the highest fault response level among the obtained fault response levels of each component as the final fault response level; perform corresponding fault processing based on the final fault response level.
  • the fault handling method provided by this method can effectively prevent loopholes in vehicle control when a fault occurs and eliminate safety hazards. However, this method cannot achieve reasonable storage and clearing of fault information.
  • the embodiment of the present application proposes a vehicle fault information processing method.
  • the control component can obtain the fault information of vehicle faults within the current driving cycle; and determine whether the current fault is a stored fault based on the fault information. If the current fault is a stored fault, If the code fails, the current storage space of the vehicle is further obtained; in response to the current storage space being less than the target threshold, the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space are obtained; based on the fault level of the current fault and The fault level of historical faults determines the stored information of current faults.
  • the control component can also manage the number of fault clearing driving cycles of historical faults based on whether there is a recurrence of historical faults in the current driving cycle to solve the technical problem of unreasonable fault storage when a vehicle fails.
  • Figure 3 is a schematic flowchart of a vehicle fault information storage process according to an embodiment of the present application. As shown in Figure 3, the process can include the following steps:
  • Step S301 After the vehicle control component is awakened, the diagnostic work is started.
  • Step S302 detect whether a fault occurs in the current driving cycle. If no fault occurs in the current driving cycle, step S303 is executed; if a fault occurs in the current driving cycle, step S304 is executed.
  • Step S303 End the current diagnosis work.
  • Step S304 Determine whether the current fault is a code storage fault according to the fault level of the current fault. If the current fault is not a code storage fault, execute step S305; if the current fault is a code storage fault, execute step S306.
  • Step S305 The fault information of the current fault is not stored, but only fault processing is performed.
  • Step S306 Determine whether the current storage space is sufficient. If the current storage space is sufficient, perform step S307; if the current storage space is insufficient, perform step S308.
  • Step S307 Store the fault information of the current fault.
  • Step S308 determine whether the fault level of the current fault is higher than the fault level of the historical faults stored in the storage space. If the fault level of the current fault is higher than the fault level of the historical faults stored in the storage space, then execute step S307; if the current fault The fault level is not higher than the fault level of the historical faults stored in the storage space, then step S305 is executed.
  • Step S309 Set the fault response to process the current fault, and then execute step S303.
  • the fault information of a vehicle failure within the current driving cycle can be obtained, and based on the fault information, it is determined that the current fault is a coded fault, and the current storage space of the vehicle is obtained; in response to the current storage space being less than the target threshold, Obtain the fault level of the current fault and the fault level of the vehicle's historical faults stored in the current storage space; determine the storage information of the current fault based on the fault level of the current fault and the fault level of the historical fault. That is to say, in the embodiment of this application, when the current storage space is less than the target threshold, it can also be determined based on the fault level of the current fault and the fault level of historical faults whether to store the fault information of the current fault.
  • This fault storage mechanism Faults can be stored reasonably according to their fault levels, which can avoid the situation where serious faults occur but cannot be stored, and achieve reasonable storage of faults.
  • Figure 4 is a schematic diagram of the vehicle fault information clearing process according to the embodiment of the present application. As shown in Figure 4, the process may include the following steps. :
  • Step S401 After the vehicle control component is awakened, the diagnostic work is started.
  • Step S402 detect whether there is a historical fault in the current driving cycle. If no historical fault occurs in the current driving cycle, execute step S403; if there is a historical fault in the current driving cycle, execute step S404.
  • Step S403 End the current diagnosis work, and perform the next round of fault detection after a certain period of time.
  • Step S404 Read the fault clearing cycle number t of the historical fault X.
  • Step S405 detect whether the historical fault X occurs again in the current driving cycle. If the historical fault X does not occur again in the current driving cycle, execute step S406; if the historical fault X occurs again in the current driving cycle, execute step S407.
  • Step S406 Decrement the current fault clearing driving cycle number t of the historical fault X by 1 to become t-1, and then execute step S403.
  • Step S407 Set the current fault clearing cycle number t of the historical fault X to the initial value T, and then execute step S403.
  • the fault information of historical faults stored in the current storage space Fault information of the target fault; based on whether the target fault occurs within the current driving cycle, determine the number of fault clearing driving cycles for the target fault. Among them, if the target fault occurs in the current driving cycle, the number of fault clearing driving cycles corresponding to the target fault is set to the initial value; if the target fault does not occur in the current driving cycle, the current fault clearing driving cycle corresponding to the target fault is set. Decrease the number of cycles by 1. That is to say, in the embodiment of the present application, the number of fault clearing cycles of historical faults stored in the storage space can be set according to whether the historical fault occurs again in the next driving cycle. This method determines fault clearing based on the frequency of fault occurrence. The required number of fault clearing mechanisms is more flexible and can ensure that frequently occurring faults are known to be stored in the storage space for subsequent analysis and processing of the fault.
  • a vehicle fault information processing device is also provided. It should be noted that the vehicle fault information processing device may be configured to execute the vehicle fault information processing method in Embodiment 1.
  • FIG. 5 is a schematic diagram of a vehicle fault information processing device according to an embodiment of the present application.
  • the fault information processing device 500 of the vehicle may include: a first acquisition component 501 , a second acquisition component 502 , a third acquisition component 503 and a first determination component 504 .
  • the first acquisition component 501 is configured to acquire the fault information of the current fault of the vehicle within the current driving cycle
  • the second acquisition component 502 is configured to determine that the current fault is a coded fault based on the fault information, and then acquire the current storage space of the vehicle;
  • the third acquisition component 503 is configured to acquire the fault level of the current fault and the fault level of historical faults of the vehicle stored in the current storage space in response to the current storage space being less than the target threshold, where the fault level is used to indicate the impact of the fault on safe driving of the vehicle.
  • the degree of impact of the fault the higher the fault level, the more serious the impact of the fault on the safe driving of the vehicle;
  • the first determining component 504 is configured to determine the storage information of the current fault based on the fault level of the current fault and the fault level of historical faults, where the storage information is used to indicate whether to store the fault information into the current storage space.
  • first acquisition component 501 can be run in the terminal as part of the device, and can be executed by the processor in the terminal.
  • the terminals can also be smart phones (such as Android phones, iOS phones, etc.), tablet computers, applause computers, and mobile Internet devices (Mobile Internet Devices, referred to as MID), PAD and other terminal devices
  • the second acquisition component 502 may include: a second determination component configured to determine the fault level of the current fault based on fault information; a third determination component configured to determine whether the current fault is a coded fault based on the fault level of the current fault. Fault; the fourth acquisition component is set to acquire the vehicle in response to the current fault being a coded fault. of current storage space.
  • the above-mentioned second determination component, third determination component and third acquisition component can be run in the terminal as part of the device, and the functions implemented by the above components can be executed by the processor in the terminal.
  • the first determination component 504 includes: a storage component, configured to store the fault information of the current fault in the current storage space in response to the fault level of the current fault being higher than the fault level of the historical fault; and a reporting component, configured to respond to The fault level of the current fault is not higher than the fault level of the historical fault, and the fault information of the current fault is reported to the server.
  • the above-mentioned storage component and reporting component can run in the terminal as part of the device, and the functions implemented by the above-mentioned components can be executed by the processor in the terminal.
  • the device 500 further includes: a fourth determination component, configured to determine the fault information of the target historical fault from the fault information of historical faults stored in the current storage space, and the target historical fault is any fault in the historical faults;
  • the fifth determination component is configured to determine the current fault clearing driving cycle number of the target historical fault based on whether the target historical fault occurs within the current driving cycle, wherein the current fault clearing driving cycle number is used to indicate that the target historical fault is cleared from the current storage space. Number of driving cycles required.
  • the above-mentioned fourth determining component and the fifth determining component can run in the terminal as part of the device, and the functions implemented by the above-mentioned components can be executed by the processor in the terminal.
  • the third determination component includes: a first setting component, configured to respond to the occurrence of a target historical fault within the current driving cycle, and set the number of current fault clearing driving cycles corresponding to the target historical fault to an initial value; a second setting component, Set to respond to the target historical fault not occurring within the current driving cycle, then decrement the number of current fault clearing driving cycles corresponding to the target historical fault by 1.
  • first setting component and the second setting component can be run in the terminal as part of the device, and the functions implemented by the above-mentioned components can be executed by the processor in the terminal.
  • the first acquisition component is configured to acquire the fault information of the current fault of the vehicle within the current driving cycle; the second acquisition component is configured to determine that the current fault is a coded fault based on the fault information, and then acquire the current stored fault of the vehicle. space; the third acquisition component is set to obtain the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space in response to the current storage space being less than the target threshold; the first determination component is set to based on the current fault. The fault level and the fault level of historical faults determine the stored information of the current fault.
  • the current storage space when the current storage space is less than the target threshold, it can also be determined based on the fault level of the current fault and the fault level of historical faults whether to store the fault information of the current fault into the storage space.
  • This kind of fault The storage mechanism can reasonably store faults according to their fault levels, which can avoid the situation where serious faults occur but cannot be stored. It achieves reasonable storage of faults and facilitates subsequent analysis of the causes of faults. The technical effect of analysis and positioning solves the technical problem of unreasonable fault storage when a vehicle fails.
  • Each functional component provided by the embodiment of the present application can be run in the vehicle's fault information processing method or similar AND computing device, or can be stored as part of a computer-readable storage medium.
  • Figure 6 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present application.
  • a program product 60 in a real-time manner according to the present application is provided, on which a computer program is stored, and the computer program is processed
  • the current fault is a code storage fault, and the current storage space of the vehicle is obtained;
  • the fault level is used to indicate the impact of the corresponding fault on the safe driving of the vehicle, and the fault level is The higher the fault level, the more serious the impact of the fault on the safe driving of the vehicle;
  • the storage information of the current fault is determined, where the storage information is used to indicate whether to store the fault information to the current storage space.
  • the computer program also implements the following steps when executed by the processor: determine the fault level of the current fault based on the fault information; determine whether the current fault is a coded fault based on the fault level of the current fault; respond to the current fault as Code storage failure, obtain the current storage space of the vehicle.
  • the computer program also implements the following steps when executed by the processor: in response to the fault level of the current fault being higher than the fault level of the historical fault, storing the fault information of the current fault into the current storage space; or, in response to The fault level of the current fault is not higher than the fault level of the historical fault, and the fault information of the current fault is reported to the server.
  • the computer program is also program code that implements the following steps when executed by the processor: determining the fault information of the target historical fault from the fault information of historical faults stored in the current storage space, and the target historical fault is any of the historical faults. Fault; based on whether the target historical fault occurs within the current driving cycle, determine the current fault clearing driving cycle number of the target historical fault, where the current fault clearing driving cycle number is used to indicate the driving cycles required to clear the target historical fault from the current storage space frequency.
  • the computer program is also program code that implements the following steps when executed by the processor: in response to the occurrence of a target historical fault within the current driving cycle, setting the number of current fault clearing driving cycles corresponding to the target historical fault to an initial value; in response to the current If the target fault does not occur within the driving cycle, the number of current fault clearing driving cycles corresponding to the target historical fault is reduced by 1.
  • the computer-readable storage medium may also be provided with program codes for various preferred or optional method steps provided by the vehicle fault information processing method.
  • a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave carrying the readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above.
  • Non-volatile storage media may send, propagate, or transport programs for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code contained in a computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, radio frequency, etc., or any suitable combination of the above.
  • FIG. 7 is a schematic structural diagram of a processor according to an embodiment of the present application.
  • the processor 70 is configured to run a program, wherein when the program is running, the vehicle fault information processing method described in the embodiment of the present application is executed.
  • the above-mentioned processor 70 can execute the operating program of the vehicle fault information processing method.
  • the processor 70 may be configured to perform the following steps:
  • the current fault is a code storage fault, and the current storage space of the vehicle is obtained;
  • the fault level is used to indicate the impact of the corresponding fault on the safe driving of the vehicle, and the fault level is The higher the fault level, the more serious the impact of the fault on the safe driving of the vehicle;
  • the storage information of the current fault is determined, where the storage information is used to indicate whether to store the fault information to the current storage space.
  • the processor 70 may be further configured to perform the following steps: determine the fault level of the current fault based on the fault information; determine whether the current fault is a coded fault based on the fault level of the current fault; respond to the current fault being a coded fault. Fault to get the current storage space of the vehicle.
  • the processor 70 may be further configured to perform the following steps: in response to the fault level of the current fault being higher than the fault level of the historical fault, storing the fault information of the current fault into the current storage space; or, in response to the current fault The fault level is not higher than the fault level of historical faults, and the fault information of the current fault is reported to the server.
  • the processor 70 may be further configured to perform the following steps: retrieve history stored in the current storage space.
  • the fault information of the target historical fault is determined from the fault information of the fault, and the target historical fault is any fault in the historical faults; based on whether the target historical fault occurs within the current driving cycle, the current fault clearing driving cycle number of the target historical fault is determined, where, The number of current fault clearing driving cycles is used to indicate the number of driving cycles required to clear the target historical fault from the current storage space.
  • the processor 70 may be further configured to perform the following steps: in response to the target historical fault occurring within the current driving cycle, setting the number of current fault clearing driving cycles corresponding to the target historical fault to an initial value; in response to the current driving cycle If the target fault does not occur within the target historical fault, the number of current fault clearing driving cycles corresponding to the target historical fault is reduced by 1.
  • the above-mentioned processor 70 can execute various functional applications and data processing by running software programs and components stored in the memory, that is, implementing the above-mentioned vehicle fault information processing method.
  • the disclosed technical content can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of components can be a logical functional division. In actual implementation, there may be other division methods.
  • multiple components or components can be combined or integrated into Another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, the components or the indirect coupling or communication connection of the components, which may be in electrical or other forms.
  • Components described as separate components may or may not be physically separate.
  • Components shown as components may or may not be physical components, that is, they may be located in one place, or they may be distributed across multiple components. Some or all of the components may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional component in each embodiment of the present application can be integrated into a processing component, or each component can exist physically alone, or two or more components can be integrated into one component.
  • the above integrated components can be implemented in the form of hardware or software functional components.
  • Integrated components may be stored in a computer-readable storage medium if they are implemented in the form of software functional components and sold or used as independent products.
  • the technical solution of the present application is essentially or contributes to the relevant technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, Includes several instructions to cause a computer device (which can be a personal computer, a server or a network device, etc.) to execute the methods of various embodiments of the present application. all or part of the steps.
  • the aforementioned storage media include: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program code. .
  • the solution provided by the embodiment of the present application can be applied to the vehicle fault information processing process to obtain the fault information of the vehicle failure within the current driving cycle; when it is determined that the current fault is a coded fault based on the fault information, the current storage space of the vehicle is obtained ; In response to the current storage space being less than the target threshold, obtain the fault level of the current fault and the fault level of the historical faults of the vehicle stored in the current storage space; determine the storage information of the current fault based on the fault level of the current fault and the fault level of the historical fault. .
  • the fault storage mechanism of the above scheme can reasonably store faults according to the fault level, which can avoid the situation of serious faults that cannot be stored, and achieve the technical effect of rationally storing faults and facilitating subsequent analysis and location of fault causes. , which solves the technical problem of unreasonable fault storage when a vehicle breaks down.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本申请实施例公开了车辆的故障信息处理方法、装置、存储介质和处理器。其中，该方法包括：获取当前驾驶循环内车辆发生当前故障的故障信息；基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。

Description

车辆的故障信息处理方法、装置、存储介质和处理器
本申请要求于2022年07月18日提交中国专利局、优先权号为202210841846.2、发明名称为“车辆的故障信息处理方法、装置、存储介质和处理器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及车辆技术领域，具体而言，涉及车辆的故障信息处理方法、装置、存储介质和处理器。
背景技术
目前，车辆在发生故障时，车辆的控制组件可以记录发生的故障并进行相关故障处理，但是仅仅是简单的将故障进行存储，等故障消失后进行简单的故障消除，并不会根据当前车辆状态进行综合考虑，进而确定如何存储故障、清除故障。这种故障存储清除机制可能会对后续查找问题原因产生干扰，影响问题分析，不便于查找问题真正的原因及解决问题。
针对上述车辆发生故障时，故障存储不合理的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种车辆的故障信息处理方法、装置、存储介质和处理器，以至少解决车辆发生故障时，故障存储不合理的技术问题。
根据本申请实施例的一个方面，提供了一种车辆的故障信息处理方法，包括：获取当前驾驶循环内车辆发生当前故障的故障信息；基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，其中，故障等级用于指示对应的故障对车辆安全驾驶的影响程度，故障的故障等级越高，故障对车辆安全驾驶的影响程度越严重；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，存储信息用于指示是否将故障信息存储至当前存储空间。
可选地，基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间，包括：基于故障信息确定当前故障的故障等级；基于当前故障的故障等级，确定当前 故障是否为存码故障；响应于当前故障为存码故障，获取车辆的当前存储空间。
可选地，基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，包括：响应于当前故障的故障等级高于历史故障的故障等级，将当前故障的故障信息存储至当前存储空间；或者，响应于当前故障的故障等级不高于历史故障的故障等级，向服务器上报当前故障的故障信息。
可选地，该方法还包括：从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息，目标历史故障为历史故障中的任一故障；基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数，其中，当前故障清除驾驶循环次数用于指示目标历史故障从当前存储空间中清除所需的驾驶循环次数。
可选地，基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数，包括：响应于当前驾驶循环内发生目标历史故障，将目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；响应于当前驾驶循环内未发生目标故障，将目标历史故障对应的当前故障清除驾驶循环次数减1。
根据本申请实施例的另一方面，提供了一种车辆的故障信息处理装置，包括：第一获取组件，设置为获取当前驾驶循环内车辆发生当前故障的故障信息；第二获取组件，设置为基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；第三获取组件，设置为响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，其中，故障等级用于指示故障对车辆安全驾驶的影响程度，故障的故障等级越高，则故障对车辆安全驾驶的影响程度越严重；第一确定组件，设置为基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，存储信息用于指示是否将故障信息存储至当前存储空间。
可选地，第二获取组件，包括：第二确定组件，设置为基于故障信息确定当前故障的故障等级；第三确定组件，设置为基于当前故障的故障等级，确定当前故障是否为存码故障；第四获取组件，设置为响应于当前故障为存码故障，获取车辆的当前存储空间。
根据本申请实施例的另一方面，还提供了一种计算机可读存储介质。该计算机可读存储介质包括存储的程序，其中，在程序运行时控制计算机可读存储介质所在设备执行本申请实施例的车辆的故障信息处理方法。
根据本申请实施例的另一方面，还提供了一种处理器。该处理器设置为运行程序， 其中，程序运行时执行本申请实施例的车辆的故障信息处理方法。
根据本申请实施例的另一方面，还提供了一种车辆，该车辆设置为执行本申请实施例的车辆的故障信息处理方法。
在本申请实施例中，获取当前驾驶循环内车辆发生故障的故障信息；基于故障信息确定出当前故障为存码故障时，则获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。在本申请实施例中当当前存储空间小于目标阈值时，还可以根据当前故障的故障等级和历史故障的故障等级，来确定是否要将当前故障的故障信息存储至存储空间，这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出现，实现了对故障进行合理存储，便于后续对故障原因进行分析和定位的技术效果，解决了车辆发生故障时，故障存储不合理的技术问题。
附图说明
此处所说明的附图用来提供对本申请实施例的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请实施例的一种车辆的故障信息处理方法的流程图；
图2是根据本申请实施例的另一种车辆的故障信息处理方法的流程图；
图3是根据本申请实施例的一种车辆的故障信息的存储流程示意图；
图4是根据本申请实施例的一种车辆的故障信息的清除流程示意图；
图5是根据本申请实施例的一种车辆的故障信息处理装置的示意图；
图6是根据本申请实施例的一种计算机可读存储介质的结构示意图；
图7是根据本申请实施例的一种处理器的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于 本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或组件的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或组件，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或组件。
根据本申请实施例，提供了一种车辆的故障信息处理方法的实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图1是根据本申请实施例的一种车辆的故障信息处理方法的流程图，如图1所示，该方法可以包括如下步骤：
步骤S101，获取当前驾驶循环内车辆发生当前故障的故障信息。
在本申请上述步骤S101提供的技术方案中，当车辆点火之后，车辆的控制组件可以开始工作，也即车辆的控制组件可以开始检测在当前驾驶循环内车辆是否发生故障，当控制组件检测到车辆发生故障时，可以获取车辆发生当前故障的故障信息。其中，该故障信息中可以包括该故障的故障等级、该故障所对应的故障码以及该故障的故障清除驾驶循环次数等，此处不做具体限定。其中，该当前故障可能为一个，也可能为多个。
可选地，在本申请实施例中，可以将驾驶循环分为IG循环、休眠唤醒循环和暖机循环。其中，可以将车辆从点火(key on)到熄火(key off)称为一次IG循环；将整车的唤醒到休眠称为一次休眠唤醒循环；将车辆从key on开始，到发动机达到70摄氏度并比key on时温度高于25摄氏度称为一次暖机循环。当然，还可以将驾驶循环分为更多类型的循环，此处不做限定。
步骤S102，基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间。
在本申请上述步骤S102提供的技术方案中，在获取到当前驾驶循环内车辆发生当前故障的故障信息后，控制组件可以从该故障信息中确定该当前故障的故障等级，进而基于该当前故障的故障等级确定该当前故障的存码类型，其中故障的存码类型包括存码故障和非存码故障。需要说明的是，该故障的故障等级用于指示该故障对车辆安 全驾驶的影响程度，其中，故障的故障等级越高，故障对车辆安全驾驶的影响程度越严重。
可选的，根据故障对车辆安全驾驶影响程度的严重性可以将故障的故障等级划分为一级、二级、三级，此处不做具体限定。其中，三级故障对车辆安全驾驶的影响程度的严重性大于二级故障对车辆安全驾驶的影响程度的严重性，二级故障对车辆安全驾驶的影响程度的严重性大于一级故障对车辆安全驾驶的影响程度的严重性，也即故障的故障等级越高，则该故障对车辆安全驾驶的影响程度越严重。
可选地，在本申请实施例中，可以将故障等级不大于一级的故障确定为非存码故障，将故障等级大于一级的故障确定为存码故障。其中，当某一故障为非存码故障时，说明该故障的故障信息无法存储至存储空间，后续无法通过诊断仪从存储空间中读取该故障的故障信息。当某一故障为存码故障时，说明该故障的故障信息可以存储至存储空间，后续可以通过诊断仪从存储空间中读取该故障的故障信息，并对该故障进行分析。
可选地，由上述介绍可知，该当前故障可能为一个，也可能为多个，基于此，当该当前故障为一个时，控制组件可以判定该一个当前故障的故障等级是否大于一级，进而确定该当前故障是否为存码故障。同理，当该当前故障为多个时，控制组件也可以判定该多个当前故障中的每个当前故障的故障等级是否大于一级，进而确定该多个当前故障是否为存码故障。
可选地，由于车辆的存储空间有限，基于此，在确定出该当前故障为存码故障后，控制组件可以获取车辆的当前存储空间，进而基于车辆的当前存储空间，来确定该当前故障的存储信息。
步骤S103，响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级。
本申请上述步骤S103提供的技术方案中，响应于当前存储空间小于目标阈值时，则说明当前存储空间可能不足，当前故障的故障信息可能无法存储至存储空间内，在这种情况下，控制组件可以获取当前故障的故障等级与当前存储空间中存储的历史故障的故障等级，进而基于当前故障的故障等级与当前存储空间中存储的历史故障的故障等级来确定是否要将该当前故障的故障信息存储至存储空间。其中，目标阈值可以预先设置，例如，假设车辆的存储空间最多可存储的故障信息的条目为n条，则可将该目标阈值设置为1，此处不做具体限制。
可选地，不论当前故障为一个还是多个，当当前存储空间小于目标阈值时，控制 组件可以从当前故障的故障信息中获取该当前故障的故障等级，控制组件还可以从当前存储空间中已经存储的历史故障的故障信息中获取每个历史故障的故障等级，之后，基于该当前故障的故障等级和当前存储空间中存储的历史故障的故障等级，确定当前故障的存储信息。
步骤S104，基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。
本申请上述步骤S104提供的技术方案中，控制组件在确定出当前故障的故障等级和历史故障的故障等级后，可以基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。
可选地，当当前故障为多个时，控制组件可以将该多个当前故障的故障等级与当前存储空间中存储的多个历史故障的故障等级进行对比，进而确定该多个当前故障的故障等级是否高于该多个历史故障的故障等级。
可选地，以该多个当前故障中的任意一个当前故障为例，如果该当前故障的故障等级高于该多个历史故障中某个历史故障的故障等级，则控制单元可以生成该当前故障的存储信息，该存储信息用于指示将该当前故障的故障信息存储至当前存储空间内。其中，控制组件可以用该当前故障的故障信息代替该历史故障的故障信息，也即，控制组件可以将该当前故障的故障信息存储至该当前存储空间中，并删除该历史故障的故障信息。如果该当前故障的故障等级不高于该多个历史故障中任意历史故障的故障等级，则控制组件可以生成该当前故障的故障信息，该故障信息用于指示上报该当前故障的故障信息，其中，控制组件可以将该当前故障的故障信息上报至服务器，服务器可以根据故障处理策略，对该当前故障进行处理，但控制组件无法将该当前故障的故障信息存储至当前存储空间。依据相同的方法，控制组件可以将该多个当前故障中的每个当前故障的故障等级与当前存储空间中存储的多个历史故障的故障等级进行比较，进而生成每个当前故障的存储信息。
本申请上述步骤S101至步骤S104，获取当前驾驶循环内车辆发生故障的故障信息，基于故障信息确定当前故障为存码故障时，获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。也就是说，在本申请实施例中，当当前故障为存码故障，且当前存储空间不足以存储该当前故障时，还可以根据该当前故障的故障等级与当前存储空间中已经存储的历史故障的故障等级来确定该当前故障的存储信息，这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出 现，实现了对故障进行合理存储的技术效果，解决了车辆发生故障时，故障存储不合理的技术问题。
下面对该实施例的上述方法进行进一步介绍。
作为一种可选的实施例方式，步骤S102，基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间。
在该实施例中，故障的存码类型分为存码故障和非存码故障，当当前车辆发生故障后，控制组件首先要判定该当前故障是否为存码故障，如果该当前故障为存码故障，则控制组件可以获取车辆的当前存储空间，进而根据车辆的当前存储空间来确定该当前故障的存储信息。
可选地，由前述介绍可知，每种故障的故障信息中可以包括该故障的故障等级、该故障所对应的故障码、以及该故障的故障清除驾驶循环次数。需要说明的是，控制组件中预先存储有车辆故障映射关系表。例如，该车辆故障映射关系表可以如下表1所示，当然，该车辆故障映射关系表也可以有其他设置方式，此处不做具体限定。
表1车辆故障映射关系表
可选地，由前述介绍可知，车辆发生的当前故障可能有一个，也可能有多个。其中，当该车辆的当前故障为多个时，控制组件可以从该多个当前故障中每个当前故障的故障信息中获取每个当前故障的故障等级，进而基于该多个当前故障中每个当前故障的故障等级和车辆的故障映射关系表，确定该多个当前故障中每个当前故障是否为存码故障。
举例而言，以该多个当前故障中的任一当前故障为例，假设控制组件从该当前故障的故障信息中获取到该当前故障的故障等级为一级，在这种情况下，控制组件可以根据该当前故障的故障等级从车辆的故障映射关系表中查找与该当前故障的故障等级一致的故障等级，进而将查找到的故障等级对应的存码类型作为该当前故障的存码类型，也即该当前故障的存码类型为非存码故障。依据相同的方法，控制组件可以确定出多个当前故障中每个当前故障所对应的存码类型。
可选地，如果车辆发生的当前故障为一个时，控制组件也可以参考上述方法确定出该一个当前故障的存码类型，此处不再赘述。
在确定出当前故障的存码类型之后，控制组件可以基于该当前故障的存码类型对该当前故障进行相应的处理。其中，当该当前故障为非存码故障时，控制组件可以向服务器上报该当前故障的故障信息，服务器可以基于该当前故障的故障信息对该当前故障进行处理，但是控制组件不会将该当前故障的故障信息存储至存储空间。当该当前故障为存码故障时，控制组件可以获取该车辆的当前存储空间，进而确定该当前存储空间是否充足。
作为一种可选的实施例方式，步骤S103，响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级。
在该实施例中，当响应于当前存储空间小于目标阈值时，控制组件可以获取当前故障的故障等级与当前存储空间中存储的历史故障的故障等级。其中，该故障等级用于指示该当前故障对车辆安全驾驶的影响程度，该当前故障的故障等级越高，该当前故障对该车辆安全驾驶的影响程度越高。
可选地，继前述举例，当目标阈值为1时，当当前存储空间可以存储的故障信息的条目小于1时，控制组件可以获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，之后，再基于该当前故障的故障等级和历史故障的故障等级，进一步判定是否要将该当前故障的故障信息存储至当前存储空间中。
可选地，由前述介绍可知，故障的故障信息中包括该故障的故障等级、该故障所对应的故障码以及该故障的故障清除驾驶循环次数，基于此，控制组件可以从当前故障的故障信息中获取当前故障的故障等级，并从存储空间中存储的各个历史故障的故障信息中确定各个历史故障的故障等级。
可选地，当当前存储空间不小于目标阈值时，则说明当前存储空间充足，该当前故障的故障信息可以存储至当前存储空间。
作为一种可选的实施例方式，步骤S104，基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。
在该实施例中，当当前存储空间小于目标阈值时，控制组件可以基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，该故障信息用于指示是否要将当前故障存储至当前存储空间。
可选地，如前所述，控制组件可以从当前故障的故障信息中确定该当前故障的故 障等级，并从存储空间中存储的历史故障的故障信息中确定各个历史故障的故障等级，之后，控制组件可以基于当前故障的故障等级与存储空间中存储的历史故障的故障等级，确定是否要将该当前故障的故障信息存储至当前存储空间中。
可选地，如果该当前故障只有一个，则控制组件可以将该一个当前故障的故障等级与每个历史故障的故障等级进行比较，如果该当前故障的故障等级高于某个历史故障的故障等级，则控制组件可以生成该当前故障的存储信息。其中，该当前故障的存储信息用于指示控制组件将该当前故障的故障信息存储至当前存储空间，在这种情况下，控制组件可以将存储空间中存储的故障等级低于该当前故障的故障等级的历史故障的故障信息进行清除，进而将该当前故障的故障信息存储至当前存储空间中。其中，当该当前故障的故障等级高于多个历史故障的故障等级时，控制组件可以将该多个历史故障的故障等级再次进行比较，进而将该多个历史故障中故障等级最低的一个历史故障的故障信息从该当前存储空间中进行清除，并将该当前故障的故障信息存储至当前存储空间中。
具体地，如果该当前故障的故障等级低于每个历史故障的故障等级，则控制组件可以生成该当前故障的存储信息，该存储信息用于指示控制组件将该当前故障的故障信息上报至服务器，服务器可以根据故障处理策略，对该当前故障进行处理。
可选地，如果该当前故障有多个，则控制组件可以将该多个当前故障中每个当前故障的故障等级与每个历史故障的故障等级进行比较，如果该多个当前故障中存在故障等级高于历史故障的故障等级的故障，则控制组件可以将当前存储空间中存储的故障等级低于该当前故障的故障等级的历史故障的故障信息进行清除，并将该当前故障的故障信息存储至当前存储空间中。如果该多个当前故障的故障等级均低于历史故障的故障等级，则控制组件可以将该多个当前故障的故障信息上报至服务器，服务器可以根据故障处理策略，对该多个当前故障进行处理。
举例而言，假设该当前故障有8个，其中该8个当前故障中有5个当前故障的故障等级高于当前存储空间中存储的某2个历史故障的故障等级，在这种情况下，控制组件可以将该2个历史故障的故障信息从当前存储空间中进行清除，然后，控制组件还可以将该5个当前故障的故障等级进行比较，进而将该5个当前故障中故障等级较高的2个当前故障的故障信息存储至该当前存储空间中。
本申请实施例，可以获取当前驾驶循环内车辆发生故障的故障信息，基于故障信息确定当前故障为存码故障时，获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。 在本申请实施例中当当前存储空间小于目标阈值时，还可以根据当前故障的故障等级和历史故障的故障等级，来确定是否要存储当前故障的故障信息，这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出现，实现了对故障进行合理存储，便于后续对故障原因进行分析和定位的技术效果，解决了车辆发生故障时，故障存储不合理的技术问题。
图2是根据本申请实施例的一种车辆的故障信息处理方法的流程图，如图2所示，该方法可以包括如下步骤：
步骤S201，从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息。
本申请上述步骤S201提供的技术方案中，控制组件可以从当前存储空间中存储的历史故障中确定目标历史故障的故障信息，其中，该目标历史故障为历史故障中的任一故障。在确定出目标历史故障后，控制组件可以获取目标历史故障当前的故障清除驾驶循环次数。需要说明的是，不同故障等级的故障所需的故障清除驾驶循环次数不同，其中，可以按照故障等级越高，所需的故障清除驾驶循环次数越多的原则，来预先设置每种故障等级的故障所需的故障清除驾驶循环次数。例如，可以将一级故障所需的故障清除驾驶循环次数设置为20次，将二级故障所需的故障清除驾驶循环次数设置为30次，将三级故障所需的故障清除驾驶循环次数设置为40次。当然，每种故障等级的故障所需的故障清除驾驶循环次数还可以有其他的设置方式，此处不做具体限定。
步骤S202，基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数。
本申请上述步骤S202提供的技术方案中，控制组件可以基于当前驾驶循环内是否发生目标历史故障，来确定目标历史故障的当前故障清除驾驶循环次数。其中，当当前驾驶循环内发生目标历史故障，则将目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；当当前驾驶循环内未发生目标历史故障，则将目标历史故障对应的当前故障清除驾驶循环次数减1。
举例而言，如果该目标历史故障为二级故障，且该目标历史故障的当前故障清除驾驶循环次数为25次。继前述举例，二级故障的故障清除驾驶循环次数的初始值为30次，在这种情况下，如果当前驾驶循环内发生该目标历史故障，则将该目标历史故障的当前故障清除驾驶循环次数设置为初始值，也即将该目标历史故障的当前故障清除驾驶循环次数设置为30次；如果当前驾驶循环内没有发生该目标历史故障，则将该 目标历史故障的当前故障清除驾驶循环次数减1，也即将该目标历史故障的当前故障清除驾驶循环次数设置为24次。后续，如果在下一个驾驶循环内发生该目标历史故障，则将该目标历史故障的故障驾驶循环次数设置为初始值，如果在下一个驾驶循环内没有发生该目标历史故障，则将该目标历史故障的故障驾驶循环次数减1，依据这样的方法，当该目标历史故障的故障清除驾驶循环次数减为0，则该目标历史故障的故障信息将会自动从当前存储空间中清除。
本申请上述步骤S201至步骤S202，可以从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息；基于该当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数。其中，如果当前驾驶循环内发生目标历史故障，则将该目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；如果当前驾驶循环内没发生该目标历史故障，则将该目标历史故障对应的当前故障清除驾驶循环次数减1。也就是说，在本申请实施例中，存储空间中存储的历史故障的故障清除驾驶循环次数可以根据该历史故障是否在下一次驾驶循环中再次发生来设置，这种根据故障发生的频次来确定故障清除所需的次数的故障清除机制更加的灵活，可以保证频繁发生的故障存储在存储空间中，以便后续对该故障进行分析和处理。
下面对该实施例的上述方法进行进一步介绍。
作为一种可选的实施例方式，步骤S202，基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数。
在该实施例中，当控制组件从当前存储空间中存储的历史故障的故障信息中确定出目标历史故障的故障信息后，控制组件还可以从该目标历史故障的故障信息中确定该目标历史故障的当前故障清除驾驶循环次数。需要说明的是，当目标历史故障成功存储至当前存储空间之后，该目标历史故障的故障清除驾驶循环次数开始生效，也即，当下一次驾驶循环内没有再次发生该目标历史故障，则该目标历史故障的故障清除驾驶循环次数自动减1，按照该方法，每当下一个驾驶循环内没有发生该目标历史故障，就将该目标历史故障的故障清除驾驶循环次数自动减1，直至该目标历史故障的故障清除驾驶循环次数减为0时，该目标历史故障的故障信息可以自动从该当前存储空间中清除。如果该目标历史故障的故障信息存储至存储空间中之后，在之后的任一驾驶循环内再次发生该目标历史故障，则该目标历史故障的故障清除驾驶循环次数将会自动恢复为初始值，之后再重新开始计算该目标历史故障的故障清除驾驶循环次数。基于此，控制组件可以从该目标历史故障的故障信息中获取该目标历史故障的当前故障清除驾驶循环次数。
可选地，控制组件在获取到目标历史故障的当前故障清除驾驶循环次数后，如果 该当前驾驶循环内发生该目标历史故障，则可将该目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；如果该当前驾驶循环内没有发生该目标历史故障，则将该目标历史故障对应的当前故障清除驾驶循环次数减1。依据该方法，控制组件可以对每个历史故障的故障清除驾驶循环次数进行管理。
本实施例，可以从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息；基于该当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数。其中，如果当前驾驶循环内发生目标历史故障，则将该目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；如果当前驾驶循环内未发生该目标历史故障，则将该目标历史故障对应的当前故障清除驾驶循环次数减1。也就是说，在本申请实施例中，存储空间中存储的历史故障的故障清除驾驶循环次数可以根据该历史故障是否在下一次驾驶循环中再次发生来设置，这种根据故障发生的频次来确定故障清除所需的次数的故障清除机制更加的灵活，可以保证频繁发生的故障存储在存储空间中，以便后续对该故障进行分析和处理。
下面结合优选的实施方式对本申请实施例的技术方案进行举例说明。
目前，当车辆发生故障时，车辆的控制组件可以按照故障发生的顺序来存储各个故障的故障信息，但是当存储空间满了之后就不再进行存储。对于故障信息的清除也是等故障消除后进行简单的消除。这种故障存储清除机制较为单一，难以适用于复杂的工作状况。
因此，为了克服以上问题，在一种相关技术中，提出了一种新能源汽车故障存储系统及检测方法，该系统由存储组件、整车控制处理器组件、信息交互装置、整车实时信息、显示组件组成，整车实时信息与整车控制处理器组件实时通讯；通过整车控制处理器组件针对整车实时信息的故障信息进行解析并储存，并通过信息交互装置将故障信息在显示组件进行可视化展示，帮助分析、统计整车发生的故障信息的种类和个数；整车故障时，可以检测整车实时故障状态；无故障时，可以查看整车历史故障信息，当某一种类别的故障发生次数达到一定上限时，通过显示组件给予报警提示。这种故障存储与检测方法主要用于统计故障发生的频次，但无法对故障进行管理。
在另一种相关技术中，提出了一种电动汽车故障诊断和处理方法。具体地，电动汽车包括整车控制组件，整车控制组件包括硬件层、底层平台软件层和应用软件层。其中应用软件层基于各部件的状态信息检测电动汽车系统中的故障；为故障分配唯一的故障代码，并将故障代码传送至底层平台软件层；底层平台软件层对故障进行进一步的确认，并将确认后的故障存储在存储器中；应用软件层从存储器中读取故障信息，并且根据动作处理参数设置执行相应的动作处理；根据点灯参数设置操作报警灯向用 户提示故障。该方法主要是描述了故障识别及处理的过程，主要对故障确认进行了优化，但并未对故障码的存储及清除机制进行规划，无法实现对故障进行管理的功能。
在另一种相关技术中，提出了一种混合动力车故障处理方法及其故障处理系统。一种混合动力车故障处理方法，包括如下步骤：检测混合动力车的各零部件当前发生的故障种类，根据故障种类确定各零部件的故障级别；根据各零部件的故障级别，映射获得各零部件的故障响应级别；将获得的各零部件的故障响应级别中最高的故障响应级别确定为最终故障响应级别；根据最终故障响应级别，进行对应的故障处理。该方法提供的故障处理方法，可有效防止整车控制在故障发生时出现漏洞，消除安全隐患，但该方法无法实现对故障信息进行合理的存储和清除。
然而，本申请实施例提出一种车辆的故障信息处理方法，控制组件可以获取当前驾驶循环内车辆发生故障的故障信息；并基于故障信息确定当前故障是否为存码故障，如果该当前故障为存码故障，则进一步获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，则获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。同时，控制组件还可以根据当前驾驶循环内是否有历史故障再次发生，对历史故障的故障清除驾驶循环次数进行管理，以解决车辆发生故障时，故障存储不合理的技术问题。
下面对本申请实施例所提供的车辆故障信息的存储流程做进一步举例介绍。图3是根据本申请实施例的一种车辆的故障信息的存储流程示意图。如图3所示，该流程可以包括以下步骤：
步骤S301，在整车控制组件被唤醒后，开始诊断工作。
步骤S302，检测当前驾驶循环内是否有故障发生，如果当前驾驶循环内没有故障发生，则执行步骤S303；如果当前驾驶循环内发生故障，则执行步骤S304。
步骤S303，结束当前诊断工作。
步骤S304，根据当前故障的故障等级判定该当前故障是否为存码故障，如果当前故障不是存码故障，则执行步骤S305；如果当前故障是存码故障，则执行步骤S306。
步骤S305，不存储当前故障的故障信息，只进行故障处理。
步骤S306，判定当前存储空间是否充足，如果当前存储空间充足，则执行步骤S307；如果当前存储空间不足，则执行步骤S308。
步骤S307，存储当前故障的故障信息。
步骤S308，判定当前故障的故障等级是否高于存储空间已经存储的历史故障的故障等级，如果当前故障的故障等级高于存储空间中存储的历史故障的故障等级，则执行步骤S307；如果当前故障的故障等级不高于存储空间中存储的历史故障的故障等级，则执行步骤S305。
步骤S309，置位故障反应，将当前故障进行处理，之后，执行步骤S303。
在本申请该实施例中，可以获取当前驾驶循环内车辆发生故障的故障信息，并基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。也就是说，在本申请实施例中当当前存储空间小于目标阈值时，还可以根据当前故障的故障等级和历史故障的故障等级，来确定是否要存储当前故障的故障信息，这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出现，实现了对故障进行合理存储。
下面对本申请实施例所提供的车辆故障信息的清除流程做进一步举例介绍，图4是根据本申请实施例的一种车辆的故障信息的清除流程示意图，如图4示，该流程可以包括以下步骤：
步骤S401，在整车控制组件被唤醒后，开始诊断工作。
步骤S402，检测当前驾驶循环内是否有历史故障，如果当前驾驶循环内没有历史故障发生，则执行步骤S403；如果当前驾驶循环内存在历史故障，则执行步骤S404。
步骤S403，结束当前诊断工作，经过一定时间进行下一轮故障检测。
步骤S404，读取历史故障X的故障清除循环周期次数t。
步骤S405，检测当前驾驶循环内历史故障X是否再次发生，如果当前驾驶循环内历史故障X没有再次发生，则执行步骤S406；如果当前驾驶循环内历史故障X再次发生，则执行步骤S407。
步骤S406，将该历史故障X的当前故障清除驾驶循环次数t数值减1，变为t-1，之后，执行步骤S403。
步骤S407，将该历史故障X的当前故障清除循环周期次数t设置为初始值T，之后，执行步骤S403。
在本申请该实施例中，可以从当前存储空间中存储的历史故障的故障信息中确定 目标故障的故障信息；基于该当前驾驶循环内是否发生目标故障，确定目标故障的故障清除驾驶循环次数。其中，如果当前驾驶循环内发生目标故障，则将该目标故障对应的故障清除驾驶循环次数设置为初始值；如果当前驾驶循环内没发生该目标故障，则将该目标故障对应的当前故障清除驾驶循环次数减1。也就是说，在本申请实施例中，存储空间中存储的历史故障的故障清除循环次数可以根据该历史故障是否在下一次驾驶循环中再次发生来设置，这种根据故障发生的频次来确定故障清除所需的次数的故障清除机制更加的灵活，可以保证频繁发生的故障已知存储在存储空间中，以便后续对该故障进行分析和处理。
根据本申请实施例，还提供了一种车辆的故障信息处理装置。需要说明的是，该车辆的故障信息处理装置可以设置为执行实施例1中的车辆的故障信息处理方法。
图5是根据本申请实施例的一种车辆的故障信息处理装置的示意图。如图5所示，该车辆的故障信息处理装置500可以包括：第一获取组件501、第二获取组件502、第三获取组件503和第一确定组件504。
第一获取组件501，设置为获取当前驾驶循环内车辆发生当前故障的故障信息；
第二获取组件502，设置为基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；
第三获取组件503，设置为响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，其中，故障等级用于指示故障对车辆安全驾驶的影响程度，故障的故障等级越高，故障对车辆安全驾驶的影响程度越严重；
第一确定组件504，设置为基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，存储信息用于指示是否将故障信息存储至当前存储空间。
此处需要说明的是，上述第一获取组件501、第二获取组件502、第三获取组件503和第一确定组件504可以作为装置的一部分运行在终端中，可以通过终端中的处理器来执行上述模块实现的功能，终端也可以是智能手机(如Android手机、iOS手机等)、平板电脑、掌声电脑以及移动互联网设备(Mobile Internet Devices，简称为MID)、PAD等终端设备
可选地，第二获取组件502可以包括：第二确定组件，设置为基于故障信息确定当前故障的故障等级；第三确定组件：设置为基于当前故障的故障等级，确定当前故障是否为存码故障；第四获取组件，设置为响应于当前故障为存码故障，则获取车辆 的当前存储空间。
此处需要说明的是，上述第二确定组件、第三确定组件和第三获取组件可以作为装置的一部分运行在终端中，可以通过终端中的处理器来执行上述组件实现的功能。
可选地，第一确定组件504包括：存储组件，设置为响应于当前故障的故障等级高于历史故障的故障等级，将当前故障的故障信息存储至当前存储空间；上报组件，设置为响应于当前故障的故障等级不高于历史故障的故障等级，向服务器上报当前故障的故障信息。
此处需要说明的是，上述存储组件和上报组件可以作为装置的一部分运行在终端中，可以通过终端中的处理器来执行上述组件实现的功能。
可选地，该装置500还包括：第四确定组件，设置为从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息，目标历史故障为历史故障中的任一故障；第五确定组件，设置为基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数，其中，当前故障清除驾驶循环次数用于指示目标历史故障从当前存储空间中清除所需的驾驶循环次数。此处需要说明的是，上述第四确定组件和第五确定组件可以作为装置的一部分运行在终端中，可以通过终端中的处理器来执行上述组件实现的功能。
可选地，第三确定组件包括：第一设置组件，设置为响应于当前驾驶循环内发生目标历史故障，将目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；第二设置组件，设置为响应于当前驾驶循环内未发生目标历史故障，则将目标历史故障对应的当前故障清除驾驶循环次数减1。
此处需要说明的是，上述第一设置组件和第二设置组件可以作为装置的一部分运行在终端中，可以通过终端中的处理器来执行上述组件实现的功能。
在该实施例中，第一获取组件，设置为获取当前驾驶循环内车辆发生当前故障的故障信息；第二获取组件，设置为基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；第三获取组件，设置为响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；第一确定组件，设置为基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。在本申请实施例中，当当前存储空间小于目标阈值时，还可以根据当前故障的故障等级和历史故障的故障等级，来确定是否要将该当前故障的故障信息存储至存储空间，这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出现，实现了对故障进行合理存储，便于后续对故障原因进 行分析和定位的技术效果，解决了车辆发生故障时，故障存储不合理的技术问题。
本申请实施例所提供的各个功能组件可以在车辆的故障信息处理方法或者类似的与运算装置中运行，也可以作为计算机可读存储介质的一部分进行存储。
图6是根据本申请实施例的一种计算机可读存储介质的结构示意图，如图6所示，提供了根据本申请的实时方式的程序产品60，其上存储由计算机程序，计算机程序被处理器执行时实现如下步骤的程序代码：
获取当前驾驶循环内车辆发生当前故障的故障信息；
基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；
响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，其中，故障等级用于指示对应的故障对车辆安全驾驶的影响程度，故障的故障等级越高，故障对车辆安全驾驶的影响程度越严重；
基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，存储信息用于指示是否将故障信息存储至当前存储空间。
可选地，计算机程序还被处理器执行时实现如下步骤的程序代码：基于故障信息确定当前故障的故障等级；基于当前故障的故障等级，确定当前故障是否为存码故障；响应于当前故障为存码故障，获取车辆的当前存储空间。
可选地，计算机程序还被处理器执行时实现如下步骤的程序代码：响应于当前故障的故障等级高于历史故障的故障等级，将当前故障的故障信息存储至当前存储空间；或者，响应于当前故障的故障等级不高于历史故障的故障等级，向服务器上报当前故障的故障信息。
可选地，计算机程序还被处理器执行时实现如下步骤的程序代码：从当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息，目标历史故障为历史故障中的任一故障；基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数，其中，当前故障清除驾驶循环次数用于指示目标历史故障从当前存储空间中清除所需的驾驶循环次数。
可选地，计算机程序还被处理器执行时实现如下步骤的程序代码：响应于当前驾驶循环内发生目标历史故障，将目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；响应于当前驾驶循环内未发生目标故障，将目标历史故障对应的当前故障清除驾驶循环次数减1。
可选地，在本申请实施例中，计算机可读存储介质还可以被设置为车辆的故障信息处理方法提供的各种优选的或可选的方法步骤的程序代码。
可选地，在本申请实施例中的具体示例可以参考上述实施例中所描述的实例，本实施例在此不再赘述。
计算机可读存储介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。非易失性存储介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读存储介质中包含的程序代码可以用任何适当的介质传输，包括但不限于无线、有线、光缆、射频等等，或者上述的任意合适的组合。
根据本申请实施例，还提供了一种处理器。图7是根据本申请实施例的一种处理器的结构示意图。如图7所示，该处理器70设置为运行程序，其中，程序运行时执行本申请实施例所述的车辆的故障信息处理方法。
在本申请实施例中，上述处理器70可以执行车辆的故障信息处理方法的运行程序。
可选地，在本申请实施例中，处理器70可以被设置为执行下述步骤：
获取当前驾驶循环内车辆发生当前故障的故障信息；
基于故障信息确定当前故障为存码故障，则获取车辆的当前存储空间；
响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级，其中，故障等级用于指示对应的故障对车辆安全驾驶的影响程度，故障的故障等级越高，故障对车辆安全驾驶的影响程度越严重；
基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息，其中，存储信息用于指示是否将故障信息存储至当前存储空间。
可选地，处理器70可以还被设置为执行下述步骤：基于故障信息确定当前故障的故障等级；基于当前故障的故障等级，确定当前故障是否为存码故障；响应于当前故障为存码故障，获取车辆的当前存储空间。
可选地，处理器70可以还被设置为执行下述步骤：响应于当前故障的故障等级高于历史故障的故障等级，将当前故障的故障信息存储至当前存储空间；或者，响应于当前故障的故障等级不高于历史故障的故障等级，向服务器上报当前故障的故障信息。
可选地，处理器70可以还被设置为执行下述步骤：从当前存储空间中存储的历史 故障的故障信息中确定目标历史故障的故障信息，目标历史故障为历史故障中的任一故障；基于当前驾驶循环内是否发生目标历史故障，确定目标历史故障的当前故障清除驾驶循环次数，其中，当前故障清除驾驶循环次数用于指示目标历史故障从当前存储空间中清除所需的驾驶循环次数。
可选地，处理器70可以还被设置为执行下述步骤：响应于当前驾驶循环内发生目标历史故障，将目标历史故障对应的当前故障清除驾驶循环次数设置为初始值；响应于当前驾驶循环内未发生目标故障，将目标历史故障对应的当前故障清除驾驶循环次数减1。
上述处理器70可以通过运行存储在存储器内的软件程序以及组件，从而执行各种功能应用以及数据处理，即实现上述的车辆的故障信息处理方法。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如组件的划分，可以为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个组件或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，组件或组件的间接耦合或通信连接，可以是电性或其它的形式。
作为分离部件说明的组件可以是或者也可以不是物理上分开的，作为组件显示的部件可以是或者也可以不是物理组件，即可以位于一个地方，或者也可以分布到多个组件上。可以根据实际的需要选择其中的部分或者全部组件来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能组件可以集成在一个处理组件中，也可以是各个组件单独物理存在，也可以两个或两个以上组件集成在一个组件中。上述集成的组件既可以采用硬件的形式实现，也可以采用软件功能组件的形式实现。
集成的组件如果以软件功能组件的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例方法 的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上仅是本申请的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。
工业实用性
本申请实施例提供的方案可以应用于车辆的故障信息处理过程中，获取当前驾驶循环内车辆发生故障的故障信息；基于故障信息确定出当前故障为存码故障时，则获取车辆的当前存储空间；响应于当前存储空间小于目标阈值，获取当前故障的故障等级与当前存储空间中存储的车辆的历史故障的故障等级；基于当前故障的故障等级和历史故障的故障等级，确定当前故障的存储信息。上述方案这种故障存储机制能够依据故障的故障等级合理存储故障，可以避免有严重故障发生却无法存储的情况出现，实现了对故障进行合理存储，便于后续对故障原因进行分析和定位的技术效果，解决了车辆发生故障时，故障存储不合理的技术问题。

Claims (12)

  1. 一种车辆的故障信息处理方法，包括：
    获取当前驾驶循环内车辆发生当前故障的故障信息；
    基于所述故障信息确定所述当前故障为存码故障，则获取所述车辆的当前存储空间；
    响应于所述当前存储空间小于目标阈值，获取所述当前故障的故障等级与所述当前存储空间中存储的所述车辆的历史故障的故障等级，其中，所述故障等级用于指示对应的故障对所述车辆安全驾驶的影响程度，所述故障的故障等级越高，所述故障对所述车辆安全驾驶的影响程度越严重；
    基于所述当前故障的故障等级和所述历史故障的故障等级，确定所述当前故障的存储信息，其中，所述存储信息用于指示是否将所述故障信息存储至所述当前存储空间。
  2. 根据权利要求1所述的方法，其中，基于所述故障信息确定所述当前故障为存码故障，则获取所述车辆的当前存储空间，包括：
    基于所述故障信息确定所述当前故障的故障等级；
    基于所述当前故障的故障等级，确定所述当前故障是否为所述存码故障；
    响应于所述当前故障为所述存码故障，获取所述车辆的当前存储空间。
  3. 根据权利要求1所述的方法，其中，基于所述当前故障的故障等级和所述历史故障的故障等级，确定所述当前故障的存储信息，包括：
    响应于所述当前故障的故障等级高于所述历史故障的故障等级，将所述当前故障的故障信息存储至所述当前存储空间；或者，
    响应于所述当前故障的故障等级不高于所述历史故障的故障等级，向服务器上报所述当前故障的故障信息。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    从所述当前存储空间中存储的历史故障的故障信息中确定目标历史故障的故障信息，其中，所述目标历史故障为所述历史故障中的任一故障；
    基于所述当前驾驶循环内是否发生所述目标历史故障，确定所述目标历史故障的 当前故障清除驾驶循环次数，其中，所述当前故障清除驾驶循环次数用于指示所述目标历史故障从所述当前存储空间中清除所需的驾驶循环次数。
  5. 根据权利要求4所述方法，其中，基于所述当前驾驶循环内是否发生所述目标历史故障，确定所述目标历史故障的当前故障清除驾驶循环次数，包括：
    响应于所述当前驾驶循环内发生所述目标历史故障，将所述目标历史故障对应的所述当前故障清除驾驶循环次数设置为初始值；
    响应于所述当前驾驶循环内未发生所述目标故障，将所述目标历史故障对应的所述当前故障清除驾驶循环次数减1。
  6. 一种车辆的故障信息处理装置，包括：
    第一获取组件，设置为获取当前驾驶循环内车辆发生当前故障的故障信息；
    第二获取组件，设置为基于所述故障信息确定所述当前故障为存码故障，则获取所述车辆的当前存储空间；
    第三获取组件，设置为响应于所述当前存储空间小于目标阈值，获取所述当前故障的故障等级与所述当前存储空间中存储的所述车辆的历史故障的故障等级，其中，所述故障等级用于指示对应的故障对所述车辆安全驾驶的影响程度，所述故障的故障等级越高，则所述故障对所述车辆安全驾驶的影响程度越严重；
    第一确定组件，设置为基于所述当前故障的故障等级和所述历史故障的故障等级，确定所述当前故障的存储信息，其中，所述存储信息用于指示是否将所述故障信息存储至所述当前存储空间。
  7. 根据权利要求6所述的装置，其中，所述第二获取组件，包括：
    第二确定组件，设置为基于所述故障信息确定所述当前故障的故障等级；
    第三确定组件，设置为基于所述当前故障的故障等级，确定所述当前故障是否为所述存码故障；
    第四获取组件，设置为响应于所述当前故障为所述存码故障，获取所述车辆的当前存储空间。
  8. 一种计算机可读存储介质，其中，所述计算机可读存储介质包括存储的程序，其中，在所述程序运行时控制所述计算机可读存储介质所在设备执行权利要求1至5中任意一项所述的方法。
  9. 一种处理器，其中，所述处理器设置为运行程序，其中，所述程序被所述处理器运行时执行权利要求1至5中任意一项所述的方法。
  10. 一种车辆，其中，所述车辆设置为执行权利要求1至5中任意一项所述的方法。
  11. 根据权利要求1所述的方法，其中，通过诊断仪从所述当前存储空间中读取所述存储信息，其中，所述存储信息为所述当前存储空间中的所述当前故障的所述故障信息。
  12. 根据权利要求1所述的方法，其中，在基于所述故障信息确定所述当前故障为存码故障，则获取所述车辆的当前存储空间之前，所述方法还包括：
    基于所述当前故障的故障等级和所述车辆的故障映射关系表，确定所述当前故障为所述存码故障，其中，所述故障映射关系表用于表征所述故障等级、所述故障的存码类型、所述车辆的驾驶循环类型和所述车辆的故障清楚驾驶循环次数之间的关系。
PCT/CN2023/106195 2022-07-18 2023-07-06 车辆的故障信息处理方法、装置、存储介质和处理器 WO2024017072A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210841846.2 2022-07-18
CN202210841846.2A CN115407746A (zh) 2022-07-18 2022-07-18 车辆的故障信息处理方法、装置、存储介质和处理器

Publications (1)

Publication Number Publication Date
WO2024017072A1 true WO2024017072A1 (zh) 2024-01-25

Family

ID=84157333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/106195 WO2024017072A1 (zh) 2022-07-18 2023-07-06 车辆的故障信息处理方法、装置、存储介质和处理器

Country Status (2)

Country Link
CN (1) CN115407746A (zh)
WO (1) WO2024017072A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115407746A (zh) * 2022-07-18 2022-11-29 中国第一汽车股份有限公司 车辆的故障信息处理方法、装置、存储介质和处理器
CN117572852B (zh) * 2024-01-16 2024-05-24 中国第一汽车股份有限公司 车辆部件故障分析方法、装置、设备、介质和产品

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107544453A (zh) * 2016-06-28 2018-01-05 长城汽车股份有限公司 车辆的控制方法、控制装置及车辆
CN110618673A (zh) * 2019-10-31 2019-12-27 深圳市鹏巨术信息技术有限公司 车辆故障处理的方法及车载设备
CN111694341A (zh) * 2020-06-05 2020-09-22 中国第一汽车股份有限公司 一种故障数据存储方法、装置、车载设备及存储介质
US11112990B1 (en) * 2016-04-27 2021-09-07 Pure Storage, Inc. Managing storage device evacuation
CN114043994A (zh) * 2021-11-17 2022-02-15 国汽智控(北京)科技有限公司 车辆故障处理方法、装置、设备和存储介质
CN114137932A (zh) * 2021-11-11 2022-03-04 上汽通用五菱汽车股份有限公司 车辆诊断方法、整车控制器、车辆和可读存储介质
CN114489500A (zh) * 2022-01-18 2022-05-13 上汽通用五菱汽车股份有限公司 故障数据处理方法、系统、设备及计算机可读存储介质
CN114610570A (zh) * 2022-03-07 2022-06-10 潍柴动力股份有限公司 一种故障存储的方法及装置
CN114706703A (zh) * 2022-03-23 2022-07-05 飞腾信息技术有限公司 多路服务器系统故障诊断装置、系统及方法
CN115407746A (zh) * 2022-07-18 2022-11-29 中国第一汽车股份有限公司 车辆的故障信息处理方法、装置、存储介质和处理器

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100861592B1 (ko) * 2006-12-01 2008-10-07 한국전자통신연구원 가입자 망 관리 시스템에서의 고장관리 방법 및 장치
CN103425122B (zh) * 2013-08-13 2016-01-20 重庆长安汽车股份有限公司 新能源汽车控制器的故障管理方法
CN104964387B (zh) * 2015-06-12 2017-07-25 石家庄国祥运输设备有限公司 一种轨道交通车辆空调设备故障信息的记录和选取方法
CN112699648B (zh) * 2021-01-04 2023-04-21 潍柴动力股份有限公司 数据处理方法及装置

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11112990B1 (en) * 2016-04-27 2021-09-07 Pure Storage, Inc. Managing storage device evacuation
CN107544453A (zh) * 2016-06-28 2018-01-05 长城汽车股份有限公司 车辆的控制方法、控制装置及车辆
CN110618673A (zh) * 2019-10-31 2019-12-27 深圳市鹏巨术信息技术有限公司 车辆故障处理的方法及车载设备
CN111694341A (zh) * 2020-06-05 2020-09-22 中国第一汽车股份有限公司 一种故障数据存储方法、装置、车载设备及存储介质
CN114137932A (zh) * 2021-11-11 2022-03-04 上汽通用五菱汽车股份有限公司 车辆诊断方法、整车控制器、车辆和可读存储介质
CN114043994A (zh) * 2021-11-17 2022-02-15 国汽智控(北京)科技有限公司 车辆故障处理方法、装置、设备和存储介质
CN114489500A (zh) * 2022-01-18 2022-05-13 上汽通用五菱汽车股份有限公司 故障数据处理方法、系统、设备及计算机可读存储介质
CN114610570A (zh) * 2022-03-07 2022-06-10 潍柴动力股份有限公司 一种故障存储的方法及装置
CN114706703A (zh) * 2022-03-23 2022-07-05 飞腾信息技术有限公司 多路服务器系统故障诊断装置、系统及方法
CN115407746A (zh) * 2022-07-18 2022-11-29 中国第一汽车股份有限公司 车辆的故障信息处理方法、装置、存储介质和处理器

Also Published As

Publication number Publication date
CN115407746A (zh) 2022-11-29

Similar Documents

Publication Publication Date Title
WO2024017072A1 (zh) 车辆的故障信息处理方法、装置、存储介质和处理器
CN109325349A (zh) 一种安全管理方法、终端设备及计算机可读存储介质
CN110661650B (zh) 一种日志管理方法、装置及电子设备和存储介质
CN102915289A (zh) 数据传输方法
CN111881460A (zh) 一种漏洞利用检测方法、系统、设备及计算机存储介质
CN108872762A (zh) 电子设备漏电检测方法、装置、电子设备及存储介质
WO2015106416A1 (zh) 一种触摸信号的处理方法及终端设备
CN105677150B (zh) 应用程序的数据清理方法及装置
CN111142900A (zh) 程序更新方法、装置及终端设备
CN108540356A (zh) 处理方法与处理设备
CN111130856A (zh) 一种服务器配置方法、系统、设备及计算机可读存储介质
CN110765085A (zh) 日志信息写入方法、系统、存储介质及移动终端
CN113220352A (zh) 关机控制方法及装置
CN117055533A (zh) 一种车载系统故障处理方法、装置、设备及介质
CN116319268A (zh) 一种网络丢包处理方法、系统及相关组件
WO2023240944A1 (zh) 数据恢复方法、装置、电子设备及存储介质
JP2007304935A (ja) 修理交換部品指示システム、修理交換部品指示装置、修理交換部品指示方法、コンピュータプログラム、及び、記録媒体
CN111367934A (zh) 数据一致性的检验方法、装置、服务器和介质
CN112463446B (zh) 一种PCIe设备恢复方法、系统及电子设备和存储介质
US11138062B2 (en) Terminal device troubleshooting method and terminal device
CN104572418A (zh) 移动终端的诊断方法、装置和系统
CN113778834B (zh) 一种应用软件的系统性能测试方法、装置与计算设备
CN115269243A (zh) 一种检测进程的方法、装置、设备及存储介质
CN114968558A (zh) 内存清理方法以及相关设备
CN111090403B (zh) 一种墨水屏设备的字符输入方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23842137

Country of ref document: EP

Kind code of ref document: A1