Fault information processing method and device and storage medium

Abstract

The invention provides a fault information processing method and device and a storage medium. The method comprises the following steps: acquiring a fault code sent by a vehicle-mounted data terminal; analyzing the fault code to obtain fault message information; determining a vehicle fault according to the fault message information; acquiring regional information of a vehicle fault; determining a target processing terminal of the vehicle fault according to the area information; generating fault diagnosis information according to the vehicle fault; and sending the fault diagnosis information to the target processing terminal so as to trigger fault processing through the target processing terminal. The accuracy of vehicle faults and fault diagnosis information can be improved, fault processing is triggered in time, the vehicle faults are quickly responded, the timeliness and efficiency of fault processing are improved, and the customer satisfaction degree is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a fault information processing method, device and storage medium. Background Technology

[0002] With the gradual increase in the number of new energy commercial vehicles on the road, how to quickly locate and handle vehicle malfunctions has become a major challenge for OEMs.

[0003] Currently, the main approach is to identify faults based on information reported by vehicles and to perform remote fault diagnosis.

[0004] However, existing technology is unable to respond quickly to vehicle malfunctions. Summary of the Invention

[0005] This application provides a fault information processing method, device, and storage medium to solve the problem that the prior art cannot respond quickly to vehicle faults.

[0006] Firstly, this application provides a fault information processing method, including:

[0007] Obtain fault codes sent by the vehicle data terminal;

[0008] The fault code is parsed to obtain the fault message information;

[0009] The vehicle malfunction is determined based on the fault message information.

[0010] Obtain the area information of the vehicle malfunction;

[0011] Based on the area information, the target processing terminal for the vehicle malfunction is determined;

[0012] Based on the vehicle malfunction, generate fault diagnosis information;

[0013] The fault diagnosis information is sent to the target processing terminal so that fault processing is triggered through the target processing terminal.

[0014] In one possible implementation, the fault message information includes fault message time and fault message count; correspondingly, determining the vehicle fault based on the fault message information includes: determining the fault start time and fault end time based on the fault message time; wherein, the same vehicle fault is a summary of one or more fault message messages of the same fault type in the same vehicle; the time difference between the fault message times of the one or more fault message messages is less than a preset time difference threshold; determining the fault occurrence type based on the fault message count; and determining the vehicle fault based on the fault start time, the fault end time, and the fault occurrence type.

[0015] In one possible implementation, parsing the fault code to obtain fault message information includes: obtaining a preset fault code parsing document; wherein the fault code parsing document includes at least one of parsing method, fault code parameters, fault code level, and fault parsing description; and parsing the fault code according to the fault code parsing document to obtain the fault message information.

[0016] In one possible implementation, generating fault diagnosis information based on the vehicle fault includes: acquiring a preset knowledge base; wherein the preset knowledge base includes multiple vehicle faults and corresponding diagnostic information for the vehicle faults; matching the vehicle faults in the preset knowledge base to obtain target diagnostic information; and generating fault diagnosis information based on the target diagnostic information.

[0017] In one possible implementation, after sending the fault diagnosis information to the target processing terminal to trigger fault processing through the target processing terminal, the method further includes: receiving fault processing information sent by the target processing terminal; and updating the preset knowledge base based on the fault processing information.

[0018] In one possible implementation, after sending the fault diagnosis information to the target processing terminal to trigger fault processing through the target processing terminal, the method further includes: generating an original message data acquisition instruction; sending the original message data acquisition instruction to the vehicle-mounted data terminal; receiving a message file sent by the vehicle-mounted data terminal; and updating the preset knowledge base according to the message file.

[0019] In one possible implementation, the message file includes multiple sub-message file fragments, which are sent in parallel by the vehicle-mounted data terminal after processing the original message data into fragments using a file fragmentation transmission strategy.

[0020] In one possible implementation, the raw message data is stored in the vehicle data terminal in a vehicle signal converter file format.

[0021] In one possible implementation, generating the original message data acquisition instruction includes: acquiring the time information of the vehicle malfunction; determining the message data extraction time interval based on the time information; and generating the original message data acquisition instruction based on the message data extraction time interval.

[0022] Secondly, this application provides a fault information processing device, including: a memory and a processor;

[0023] The memory stores computer-executed instructions;

[0024] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0025] Thirdly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0026] The fault information processing method, device, and storage medium provided in this application determine vehicle faults based on fault codes; generate fault diagnosis information based on vehicle faults; determine a target processing terminal based on the area information of the vehicle fault; and send the fault diagnosis information to the target processing terminal to trigger fault processing. This improves the accuracy of vehicle faults and fault diagnosis information, promptly triggers fault processing, enables rapid response to vehicle faults, enhances the timeliness and efficiency of fault handling, and improves customer satisfaction. Attached Figure Description

[0027] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0028] Figure 1 A schematic diagram of a scenario for the fault information processing method provided in the embodiments of this application;

[0029] Figure 2 A flowchart illustrating a fault information processing method provided in one embodiment of this application;

[0030] Figure 3 A flowchart illustrating another fault information processing method provided in an embodiment of this application;

[0031] Figure 4 A schematic diagram of a remote fault diagnosis process provided in an embodiment of this application;

[0032] Figure 5 A schematic diagram of a process for obtaining raw message data is provided for an embodiment of this application;

[0033] Figure 6 A schematic diagram illustrating a preset knowledge base update process provided for an embodiment of this application;

[0034] Figure 7 This is a schematic diagram of the structure of a fault information processing system provided in an embodiment of this application;

[0035] Figure 8 This is a schematic diagram of the structure of the fault information processing device provided in the embodiments of this application;

[0036] Figure 9 This is a schematic diagram of the fault information processing device provided in an embodiment of this application.

[0037] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0038] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0039] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0040] Currently, existing technologies identify faults based on information reported by vehicles and use the UDS (Unified Diagnostic Services) protocol for remote fault diagnosis. However, existing technologies cannot provide a rapid response to vehicle faults.

[0041] The fault information processing method provided in this application determines the target processing terminal by obtaining the area information of the vehicle fault, and triggers fault processing through the target processing terminal, which can improve the timeliness and efficiency of fault processing and enhance customer satisfaction.

[0042] Figure 1 This is a schematic diagram of a scenario for the fault information processing method provided in the embodiments of this application, such as... Figure 1 As shown, the specific application scenarios of this application include: cloud platform 101, vehicle data terminal 102, and target processing terminal 103.

[0043] The cloud platform 101 can be a server. Optionally, it can be a single server or a cluster of multiple servers.

[0044] Specifically, the vehicle-mounted data terminal 102 sends a fault code to the cloud platform 101; the cloud platform 101 generates fault diagnosis information based on the fault code; the cloud platform 101 sends the fault diagnosis information to the target processing terminal 103; and the target processing terminal 103 sends fault processing information to the cloud platform 101.

[0045] Specifically, the cloud platform 101 sends the original message data collection instruction to the vehicle data terminal 102; the vehicle data terminal 102 generates a message file according to the original message data collection instruction and sends the message file to the cloud platform 101.

[0046] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0047] Figure 2 This is a flowchart illustrating a fault information processing method provided in one embodiment of this application. The execution entity of this embodiment can be... Figure 1 The cloud platform 101 shown can also be other computer devices, and this embodiment does not impose any particular limitations on it. Figure 2 As shown, the method includes:

[0048] S201: Obtain the fault code sent by the vehicle data terminal.

[0049] Among them, the fault code can be a custom cyclic message fault code.

[0050] Among them, the fault code can be a DTC (Diagnostic Trouble Code).

[0051] It should be noted that the vehicle data terminal detects DM1 (Diagnostic Message 1). If DM1 is detected, the fault code is reported to the cloud platform. DM1 is reported at an actual frequency of 1 second.

[0052] S202: Parse the fault code to obtain the fault message information.

[0053] Specifically, the fault codes are parsed using preset parsing rules to obtain fault message information.

[0054] S203: Determine the vehicle malfunction based on the fault message information.

[0055] The fault message information includes the fault message time and the number of fault messages.

[0056] Specifically, S203 includes S2031 to S2033:

[0057] S2031: Determine the fault start time and fault end time based on the fault message time; wherein, the fault of the same vehicle is a summary of one or more fault message messages of the same fault type in the same vehicle; the time difference between the fault message times of one or more fault message messages is less than a preset time difference threshold.

[0058] The fault start time is determined by the earliest fault message time among one or more fault message messages in the same vehicle fault, and the fault end time is determined by the latest fault message time among one or more fault message messages in the same vehicle fault.

[0059] The preset time difference threshold can be 5 minutes, which can be set according to the actual situation. This application embodiment does not limit this.

[0060] S2032: Determine the type of fault based on the number of fault messages.

[0061] Specifically, the fault occurrence type corresponding to the number of fault messages is determined according to preset rules.

[0062] The types of faults include false alarms, temporary faults, intermittent faults, hard faults, and serious anomalies.

[0063] S2033: Determine the vehicle fault based on the fault start time, fault end time, and fault type.

[0064] Specifically, the duration is determined based on the fault start time and fault end time; the vehicle fault is determined based on the fault type and duration.

[0065] S204: Obtain information about the area where the vehicle is malfunctioning.

[0066] Specifically, the regional information is obtained based on the latitude and longitude location information in the fault message of the vehicle component to which the fault belongs.

[0067] S205: Determine the target processing terminal for vehicle faults based on regional information.

[0068] Specifically, the target processing terminal is matched from the preset responsible terminal library based on the regional information.

[0069] The target processing terminals include the responsible terminal for the component to which the vehicle malfunction belongs and the service station within the operating area to which the vehicle malfunction belongs.

[0070] S206: Generate fault diagnosis information based on vehicle faults.

[0071] Specifically, S206 includes S2061 to S2063:

[0072] S2061: Obtain a preset knowledge base; wherein, the preset knowledge base includes multiple vehicle faults and corresponding diagnostic information for the vehicle faults.

[0073] S2062: Based on the vehicle fault, perform a match in the preset knowledge base to obtain the target diagnostic information.

[0074] Specifically, the frozen frame data is obtained; based on the vehicle fault and the frozen frame data, a match is made in a preset knowledge base to obtain the target diagnostic information.

[0075] S2063: Generate fault diagnosis information based on the target diagnosis information.

[0076] S207: Send the fault diagnosis information to the target processing terminal so that the fault processing can be triggered through the target processing terminal.

[0077] The fault information processing method provided in this application involves determining a vehicle fault based on a fault code; generating fault diagnosis information based on the vehicle fault; determining a target processing terminal based on the area information of the vehicle fault; and sending the fault diagnosis information to the target processing terminal to trigger fault processing. This method improves the accuracy of vehicle faults and fault diagnosis information, promptly triggers fault processing, provides a rapid response to vehicle faults, enhances the timeliness and efficiency of fault handling, and improves customer satisfaction.

[0078] In one embodiment of this application, based on the above embodiments, step S202 is further provided in another way, as detailed below:

[0079] S2021: Obtain a preset fault code parsing document; wherein, the fault code parsing document includes at least one of the following: parsing method, fault code parameters, fault code level, and fault parsing description.

[0080] The preset fault code parsing document can be a preset DTC parsing document.

[0081] The parsing methods include those for circular messages, which include: data start bit, data length, and number system conversion, including hexadecimal to decimal conversion.

[0082] The fault code parameters can be SPN (Suspect Parameter Number), FMI (Failure Mode Identifier), etc.

[0083] The fault analysis instructions include a variety of fault analysis strategies. Users can customize whether a fault triggers an automatic data collection option and whether it is pushed to the terminals of relevant responsible persons. The fault analysis scheme can be quickly configured by importing files and can be configured for different vehicles.

[0084] S2022: Based on the fault code parsing document, the fault codes are parsed and processed to obtain the fault message information.

[0085] Specifically, the fault code is matched with the corresponding fault parsing strategy in the fault parsing document; the fault code is then parsed according to the fault parsing strategy to obtain the fault message information.

[0086] The fault information processing method provided in this application embodiment parses fault codes using a preset fault parsing document, supports custom configuration of the fault parsing document, and improves the compatibility of access vehicle fault parsing protocols and the fault parsing efficiency when different types of vehicles access the system.

[0087] In one embodiment of this application, based on the above embodiments, after step S207, a process of updating the preset knowledge base is further included, as detailed below:

[0088] S208: Receive fault handling information sent by the target processing terminal.

[0089] The fault handling information includes the cause of the fault and the fault handling measures.

[0090] Among them, the fault handling information is obtained by the person in charge of the target processing terminal filling in the information filling interface according to the preset template.

[0091] It should be noted that during the filling process, if the cause of the fault and the fault handling measures are to be filled in, you can choose to fill in the existing records; if there are no matching records, you can fill in the information manually. After submission, the fault will be closed.

[0092] S209: Update the preset knowledge base based on fault handling information.

[0093] In another embodiment of this application, after step S208, the method further includes statistically analyzing the causes of high-frequency faults within a preset time period based on fault handling information, generating a fault-related report to indicate the optimization and adjustment of relevant components.

[0094] The fault information processing method provided in this application embodiment can improve the accuracy of the content in the preset knowledge base and improve the efficiency of fault processing.

[0095] In one embodiment of this application, based on the above embodiment, after step S207, a process of collecting raw message data is further included, as detailed below:

[0096] S210: Generate raw message data acquisition instructions.

[0097] S211: Send the raw message data acquisition command to the vehicle data terminal.

[0098] In another embodiment of this application, the original message data acquisition instruction may be sent to the vehicle data terminal in response to the confirmation operation of the person in charge on the control interface, or it may be automatically sent to the vehicle data terminal according to the corresponding fault policy.

[0099] The conditions under which the cloud platform automatically sends raw message data collection instructions are: the vehicle fault is identified through parsing, and the automatic issuance of collection instructions has been enabled in the corresponding fault solution for the vehicle.

[0100] The conditions for manually issuing raw message collection instructions through the cloud platform are: pre-setting the collection vehicle and collection time range. During collection, the vehicle must be in a low-voltage or high-voltage state.

[0101] In another embodiment of this application, after the vehicle-mounted data terminal receives the raw message data collection instruction sent by the cloud platform, it further includes the following steps:

[0102] Step 1: The vehicle-mounted data terminal reports the total file size and number of files in the vehicle-mounted data terminal database storage during the time period of receiving the original message data collection instruction to the cloud platform.

[0103] To avoid performance pressure on the vehicle-mounted data terminal when parsing the original compressed message files stored in the database and performing message data time filtering, the file time interval is used as the granularity for differentiation. For example, if the preset message file is divided into independent files with a time length of 1 minute and the collection time interval is 3 minutes and 30 seconds, then a total of 4 independent files containing this 3 minutes and 30 seconds of data will be reported.

[0104] Step 2: The vehicle-mounted data terminal adopts a file fragmentation transmission strategy to transmit the original message data to the cloud platform in the form of stored independent files. If the transmission of a single file fails, only that single file will be retransmitted.

[0105] This application embodiment provides data support for rapid fault analysis and troubleshooting through a file fragmentation transmission strategy. At the same time, it can avoid the problems of wasted traffic and inability to extract data caused by multiple retransmissions due to network fluctuations during the transmission of large files.

[0106] Step 3: The cloud platform determines whether to send a command to enable the concurrent upload mode of the vehicle data terminal based on the network latency of the interaction with the vehicle data terminal and the total file size and data volume reported.

[0107] It should be noted that the concurrency of the vehicle data terminal is determined by the main control chip of the current vehicle data terminal based on the load rate.

[0108] The embodiments of this application can improve file transfer efficiency.

[0109] Step 4: The cloud platform determines whether to end the concurrent upload mode based on the file upload success rate and / or the vehicle data terminal based on the current load rate.

[0110] S212: Receive message files sent by the vehicle-mounted data terminal.

[0111] The message file includes multiple sub-message file fragments, which are sent in parallel by the vehicle-mounted data terminal after processing the original message data into fragments using a file fragmentation transmission strategy.

[0112] The original message data is stored in the vehicle data terminal in the format of a vehicle signal converter file.

[0113] It should be noted that the cloud platform can convert data into ASC (American Standard Code for Information Interchange) file format, allowing for intuitive viewing of the original message data and facilitating analysis and processing.

[0114] The embodiments of this application can save storage space in vehicle-mounted data terminals.

[0115] S213: Update the preset knowledge base according to the message file.

[0116] The fault information processing method provided in this application update the preset knowledge base through message files, which can enrich the content of the preset knowledge base, improve the accuracy of fault diagnosis information, and thus improve the efficiency of fault processing.

[0117] In one embodiment of this application, based on the above embodiments, step S210 is further provided in another way, as detailed below:

[0118] S2101: Obtain the time information of vehicle malfunction.

[0119] S2102: Determine the time range for message data extraction based on the time information.

[0120] The time information includes the fault trigger time.

[0121] Specifically, based on the fault trigger time, the message data extraction time interval is determined within a preset time period.

[0122] It should be noted that the same fault will only trigger one data collection session within the preset data collection time.

[0123] The preset time period can be from one minute before the fault trigger time to three minutes after the fault trigger time, and the preset collection time can be 30 consecutive minutes.

[0124] S2103: Generate raw message data acquisition instructions based on the time interval from which message data is extracted.

[0125] The fault information processing method provided in this application can improve the efficiency of locating the vehicle status at the time of the fault and improve the timeliness and efficiency of fault processing by obtaining the time information of the vehicle fault and determining the time interval for extracting message data.

[0126] Figure 3 This is a flowchart illustrating another fault information processing method provided in an embodiment of this application. Figure 3 As shown, the method includes:

[0127] S301: The on-board data terminal acquires bus DTC message packets.

[0128] Each message packet is defined as a single packet within a preset time period, which can be 10 seconds.

[0129] S302: The vehicle data terminal determines whether a DM1 message exists on the bus.

[0130] S303: If the vehicle data terminal determines that there is a DM1 message on the bus, it sends a DTC message packet and a DM1 message to the cloud platform.

[0131] S304: The cloud platform parses the DTC message group and DM1 message according to the preset parsing rules to obtain the message data.

[0132] S305: The cloud platform determines whether there is a fault in the message data.

[0133] S306: If the cloud platform determines that there is a fault in the message data, it records the fault to obtain fault diagnosis information; if it determines that there is no fault in the message data, it repeats step S305.

[0134] Among them, the time difference between the fault start time and the fault end time of the same fault is less than the preset time difference threshold.

[0135] The preset time difference threshold can be 5 minutes.

[0136] The fault diagnosis information includes the fault start time, fault end time, and fault message time.

[0137] S307: The cloud platform determines the target processing terminal based on the preset fault grouping and the region of the vehicle to which the on-board data terminal belongs.

[0138] S308: The cloud platform sends fault diagnosis information to the target processing terminal.

[0139] The fault information processing method provided in this application can improve the accuracy of vehicle fault and fault diagnosis information, and trigger fault processing in a timely manner, so as to respond quickly to vehicle faults, improve the timeliness and efficiency of fault processing, and enhance customer satisfaction.

[0140] Figure 4 This is a schematic diagram of a remote fault diagnosis process provided in an embodiment of this application. Figure 4 As shown, the method includes:

[0141] S401: The cloud platform sends remote diagnostic commands to any vehicle data terminal.

[0142] Specifically, the cloud platform sends remote diagnostic commands to any vehicle data terminal based on the service sub-functions.

[0143] Among them, the service sub-functions can be pre-set or obtained in real time through a custom interface.

[0144] S402: The on-board data terminal obtains diagnostic information based on remote diagnostic commands.

[0145] S403: The onboard data terminal sends diagnostic information to the cloud platform.

[0146] S404: The cloud platform parses and displays diagnostic information.

[0147] Figure 5 This is a schematic diagram illustrating a process for obtaining raw message data, provided as an embodiment of this application. Figure 5 As shown, the method includes:

[0148] S501: The vehicle-mounted data terminal acquires and saves the original message data.

[0149] S502: In response to a fault, the cloud platform automatically sends a raw message data collection command or, according to preset collection rules, sends a raw message data collection command to the vehicle data terminal within a preset collection interval. The raw message data collection command includes the message data extraction time interval.

[0150] S503: The vehicle-mounted data terminal extracts the original message data within the time interval based on the message data, generates a compressed data file, and sends the compressed data file to the cloud platform.

[0151] S504: The cloud platform converts the compressed data file into ASC format for saving.

[0152] Figure 6 This is a schematic diagram illustrating a preset knowledge base update process provided in an embodiment of this application. For example... Figure 6 As shown, the method includes:

[0153] S601: The target processing terminal matches the fault against a preset knowledge base to obtain a fault handling plan, which is then used by the person in charge and / or the service station executor corresponding to the target processing terminal to handle the fault. The fault handling plan includes a fault diagnosis plan and a fault repair plan.

[0154] S602: The target processing terminal sends the cause of the fault and the fault handling solution to the cloud platform.

[0155] S603: The cloud platform updates the preset knowledge base based on the cause of the fault and the fault handling solution.

[0156] S604: The cloud platform updates the priority ranking of fault causes and fault handling solutions based on the frequency of use of the fault causes and fault handling solutions.

[0157] Figure 7 This is a schematic diagram of the structure of a fault information processing system provided in an embodiment of this application. Figure 7 As shown, the obstacle information processing system provided in this embodiment includes: a cloud platform, a vehicle, an in-vehicle data terminal, and a target processing terminal.

[0158] The vehicle-mounted data terminal includes a data storage module, a data packaging module, an information communication module, and a diagnostic module. The data storage module stores message data from the vehicle bus connected to the vehicle-mounted data terminal; the data packaging module extracts and packages fault information and message bus data from the bus according to a specified format; the information communication module transmits information with the cloud platform; and the diagnostic module converts remote diagnostic commands into UDS protocol procedures for interaction with the vehicle.

[0159] The cloud platform comprises a data storage unit, an information communication and interaction unit, a data parsing unit, and a business application unit. The data storage unit stores information received from the vehicle-mounted data terminal and other system data; the information communication and interaction unit communicates with the vehicle-mounted data terminal; the data parsing unit parses and converts fault information and message files reported by the vehicle-mounted data terminal according to parsing and file conversion rules; and the business application unit supports business functions such as fault statistics, improvement of the preset knowledge base, and diagnostic operations.

[0160] Figure 8 This is a schematic diagram of the fault information processing device provided in an embodiment of this application. Figure 8As shown, the fault information processing device 80 provided in this embodiment includes: an acquisition module 801, a parsing module 802, a determination module 803, a generation module 804, and a sending module 805.

[0161] The acquisition module 801 is used to acquire fault codes sent by the vehicle data terminal;

[0162] The parsing module 802 is used to parse the fault code to obtain fault message information;

[0163] The determination module 803 is used to determine the vehicle fault based on the fault message information;

[0164] The acquisition module 801 is also used to acquire the area information of the vehicle fault;

[0165] The determining module 803 is further configured to determine the target processing terminal for the vehicle fault based on the area information.

[0166] The generation module 804 is used to generate fault diagnosis information based on the vehicle fault.

[0167] The sending module 805 is used to send the fault diagnosis information to the target processing terminal so as to trigger fault processing through the target processing terminal.

[0168] In one possible implementation, the fault message information includes fault message time and fault message count; correspondingly, the determining module 803 is specifically used to: determine the fault start time and fault end time based on the fault message time; wherein, the same vehicle fault is a summary of one or more fault message messages of the same fault type in the same vehicle; the time difference between the fault message times of the one or more fault message messages is less than a preset time difference threshold; determine the fault occurrence type based on the fault message count; and determine the vehicle fault based on the fault start time, the fault end time, and the fault occurrence type.

[0169] In one possible implementation, the parsing module 802 is specifically used to: obtain a preset fault code parsing document; wherein the fault code parsing document includes at least one of parsing method, fault code parameters, fault code level, and fault parsing description; and parse the fault code according to the fault code parsing document to obtain the fault message information.

[0170] In one possible implementation, the generation module 804 is specifically used for: acquiring a preset knowledge base; wherein the preset knowledge base includes multiple vehicle faults and diagnostic information corresponding to the vehicle faults; matching the vehicle faults in the preset knowledge base to obtain target diagnostic information; and generating fault diagnostic information based on the target diagnostic information.

[0171] In one possible implementation, the fault information processing device 80 further includes:

[0172] An update module is used to receive fault handling information sent by the target processing terminal and update the preset knowledge base according to the fault handling information.

[0173] In one possible implementation, the update module is further configured to: generate an original message data acquisition instruction; send the original message data acquisition instruction to the vehicle-mounted data terminal; receive a message file sent by the vehicle-mounted data terminal; and update the preset knowledge base according to the message file.

[0174] In one possible implementation, the message file includes multiple sub-message file fragments, which are sent in parallel by the vehicle-mounted data terminal after processing the original message data into fragments using a file fragmentation transmission strategy.

[0175] In one possible implementation, the raw message data is stored in the vehicle data terminal in a vehicle signal converter file format.

[0176] In one possible implementation, the update module, when "generating the original message data acquisition instruction", obtains the time information of the vehicle malfunction; determines the message data extraction time interval based on the time information; and generates the original message data acquisition instruction based on the message data extraction time interval.

[0177] The fault information processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0178] Figure 9 This is a schematic diagram of the structure of the fault information processing device provided in an embodiment of this application. Figure 9 As shown, the fault information processing device 90 provided in this embodiment includes at least one processor 901 and a memory 902. Optionally, the device 90 further includes a communication component 903. The processor 901, memory 902, and communication component 903 are connected via a bus 904.

[0179] In a specific implementation, at least one processor 901 executes computer execution instructions stored in memory 902, causing at least one processor 901 to perform the above-described method.

[0180] The specific implementation process of processor 901 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0181] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0182] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0183] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0184] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0185] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0186] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0187] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0188] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0189] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0190] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0191] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0192] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0193] Finally, it should be noted that other embodiments of this application will readily conceive of by those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and alterations may be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A fault information processing method, characterized in that, The method includes: Obtain fault codes sent by the vehicle data terminal; The fault code is parsed to obtain the fault message information; The vehicle malfunction is determined based on the fault message information. Obtain the area information of the vehicle malfunction; Based on the area information, the target processing terminal for the vehicle malfunction is determined; Based on the vehicle malfunction, generate fault diagnosis information; The fault diagnosis information is sent to the target processing terminal so that fault processing is triggered through the target processing terminal.

2. The method according to claim 1, characterized in that, The fault message information includes the fault message time and the number of fault messages; Accordingly, determining the vehicle fault based on the fault message information includes: Based on the fault message time, the fault start time and fault end time are determined; wherein, the same vehicle fault is a summary of one or more fault message messages of the same fault type in the same vehicle; the time difference between the fault message times of the one or more fault message messages is less than a preset time difference threshold. The type of fault is determined based on the number of fault messages received. The vehicle fault is determined based on the fault start time, the fault end time, and the fault occurrence type.

3. The method according to claim 1, characterized in that, The process of parsing the fault code to obtain fault message information includes: Obtain a preset fault code parsing document; wherein, the fault code parsing document includes at least one of the following: parsing method, fault code parameters, fault code level, and fault parsing description; Different parsing schemes can be configured for different vehicles. Based on the fault code parsing document, the fault codes are parsed and processed to obtain the fault message information.

4. The method according to any one of claims 1 to 3, characterized in that, The step of generating fault diagnosis information based on the vehicle fault includes: Obtain a preset knowledge base; wherein, the preset knowledge base includes multiple vehicle faults and corresponding diagnostic information for the vehicle faults; Based on the vehicle malfunction, a match is made in the preset knowledge base to obtain target diagnostic information; Based on the target diagnostic information, fault diagnostic information is generated.

5. The method according to claim 4, characterized in that, After sending the fault diagnosis information to the target processing terminal to trigger fault processing through the target processing terminal, the method further includes: Receive fault handling information sent by the target processing terminal; The preset knowledge base is updated based on the fault handling information.

6. The method according to claim 4, characterized in that, After sending the fault diagnosis information to the target processing terminal to trigger fault processing through the target processing terminal, the method further includes: Generate raw message data acquisition instructions; The original message data acquisition command is sent to the vehicle-mounted data terminal; Receive message files sent by the vehicle-mounted data terminal; Update the preset knowledge base according to the message file.

7. The method according to claim 6, characterized in that, The message file includes multiple sub-message file fragments, which are generated by the vehicle-mounted data terminal using a file fragmentation transmission strategy to process the original message data into fragments and send them in parallel.

8. The method according to claim 7, characterized in that, The original message data is stored in the vehicle data terminal in the format of an automotive signal converter file.

9. The method according to claim 6, characterized in that, The command to generate raw message data collection includes: Obtain the time information of the vehicle malfunction; Based on the time information, determine the time interval for message data extraction; Based on the time interval for extracting the message data, a raw message data acquisition instruction is generated.

10. A fault information processing device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the fault information processing method as described in any one of claims 1 to 9.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the fault information processing method as described in any one of claims 1 to 9.

Images