Vehicle fault maintenance method and device, server and storage medium

Abstract

The invention relates to a vehicle fault maintenance method and device, a server and a storage medium. The method comprises the following steps: sending a request instruction for reading a fault code to a plurality of electronic control units of a vehicle; and in response to the received fault code returned by the target electronic control unit and target identification information corresponding to the target electronic control unit, sending the fault code and the target identification information to a preset server of the vehicle so as to receive target maintenance guidance information corresponding to the fault code returned by the preset server. According to the method, the accuracy and convenience of the obtained maintenance data can be improved, so that the vehicle maintenance efficiency is improved.

Description

Technical Field

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

[0002] In vehicle diagnostic communication, vehicle fault codes are standardized codes generated by the on-board diagnostic system to quickly identify vehicle anomalies. However, due to differences in vehicle models, configurations, and operating environments, the same fault may require different repair methods on different vehicles. Existing diagnostic systems often fail to adequately consider these factors, resulting in inaccurate repair guidance information that cannot meet actual repair needs. Summary of the Invention

[0003] This application provides a vehicle fault repair method, apparatus, server, and storage medium to solve the above-mentioned problems.

[0004] To achieve the above objectives, according to a first aspect of this application, a vehicle fault repair method is provided, the method comprising:

[0005] Sends a request command to read fault codes to multiple electronic control units of the vehicle;

[0006] In response to receiving a fault code and target identification information corresponding to the target electronic control unit, the fault code and target identification information are sent to a preset server of the vehicle to receive target repair guidance information corresponding to the fault code returned by the preset server.

[0007] In some embodiments, sending the fault code and the target identification information to a preset server of the vehicle to receive target repair guidance information corresponding to the fault code returned by the preset server includes:

[0008] The target identification information and the fault code are sent to the preset server, so that the preset server can obtain associated maintenance guidance information related to the target identification information and the fault code based on the target identification information, the fault code, and a preset mapping relationship, and send it to the diagnostic terminal.

[0009] The preset mapping relationship is used to indicate the associated maintenance guidance information corresponding to each combination of multiple preset identification information and preset fault codes;

[0010] Based on the associated repair guidance information sent by the preset server, the target repair guidance information is determined.

[0011] In some embodiments, the associated repair guidance information includes associated address information, which is used to indicate the storage address of the repair guidance information. The preset mapping relationship includes multiple types, and each preset mapping relationship is used to associate associated address information of different format types. The multiple format types include at least one of file format and web page format.

[0012] In some embodiments, the target repair guidance information is one of several formats of repair guidance information.

[0013] When the associated address information is associated file address information, the format type of the target maintenance guidance information is a file format, or

[0014] When the associated address information is associated webpage address information, the format type of the target maintenance guidance information is webpage format.

[0015] In some embodiments, determining the target repair guidance information based on the associated repair guidance information sent by the preset server includes:

[0016] When the associated maintenance guidance information includes a target file, the target maintenance guidance information is determined based on the target file, wherein the target file is the corresponding file queried by the preset server based on the associated file address information;

[0017] When the associated repair guidance information includes associated webpage address information, the corresponding webpage content is queried based on the associated webpage address information to determine the target repair guidance information.

[0018] In some embodiments, the method further includes:

[0019] Generate a vehicle fault map, which is used to characterize the fault propagation path between various components of the vehicle;

[0020] Based on the target identification information and the fault code, multiple sets of candidate maintenance guidance information are generated, and each set of candidate maintenance guidance information includes at least one of maintenance sequence and maintenance method;

[0021] Based on the vehicle fault map and the candidate maintenance guidance information, the implementation effect of each group of candidate maintenance guidance information is predicted by a prediction model.

[0022] Based on the implementation effect and preset optimization goals of each group of candidate maintenance guidance information, target maintenance guidance information is recommended.

[0023] According to a second aspect of this application, embodiments of this application also provide a file server deployed in a vehicle, the file server being used for:

[0024] Receive fault codes and target identification information from the diagnostic terminal, and obtain associated file address information associated with the target identification information and the fault codes based on the fault codes, the target identification information, and a preset mapping relationship;

[0025] Based on the associated file address information, the corresponding file is queried to obtain the associated maintenance guidance information and sent to the diagnostic terminal.

[0026] According to a third aspect of this application, embodiments of this application also provide a website server deployed in a vehicle, the website server being used for:

[0027] Receive fault codes and target identification information from the diagnostic terminal, and obtain associated web page address information related to the target identification information and the fault codes based on the fault codes, the target identification information, and a preset mapping relationship;

[0028] The associated webpage address information is sent to the diagnostic terminal as associated repair guidance information.

[0029] According to a fourth aspect of this application, embodiments of this application also provide a vehicle fault repair device, the device comprising:

[0030] The request module is used to send request commands to read fault codes to multiple electronic control units of the vehicle;

[0031] The determination module is configured to, in response to receiving a fault code returned by a target electronic control unit and target identification information corresponding to the target electronic control unit, send the fault code and the target identification information to a preset server of the vehicle, so as to receive target repair guidance information corresponding to the fault code returned by the preset server.

[0032] According to a fifth aspect of this application, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods provided in embodiments of this application.

[0033] Some embodiments of this specification include at least the following beneficial effects: by querying the vehicle's maintenance guidance information stored in the preset server inside the vehicle through target identification information and fault information, the maintenance guidance information can be obtained more accurately and conveniently, thereby improving the efficiency of vehicle maintenance.

[0034] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] To gain a more complete understanding of this application and its beneficial effects, the following description will be provided in conjunction with the accompanying drawings, wherein the same reference numerals in the following description denote the same parts.

[0037] Figure 1 These are application scenario diagrams illustrating vehicle fault repair methods according to some embodiments of this specification;

[0038] Figure 2 This is an exemplary flowchart of a vehicle fault repair method according to some embodiments of this specification;

[0039] Figure 3 This is an exemplary flowchart illustrating the determination of target maintenance guidance information according to some embodiments of this specification;

[0040] Figure 4 This is a structural schematic diagram of a vehicle fault repair device according to some embodiments of this specification;

[0041] Figure 5 This is a schematic diagram of the structure of an electronic device according to some embodiments of this specification. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the protection scope of this application.

[0043] To facilitate understanding of the implementation schemes provided in this application, the relevant application background of the vehicle fault repair method provided in this application will be explained first.

[0044] Currently, when sensors, actuators, or electronic control units (ECUs) detect parameters deviating from standard ranges, they automatically record corresponding fault codes (e.g., P0171 indicates a lean fuel system). These fault codes can accurately pinpoint the faulty component (such as the powertrain, chassis, or emissions system), helping users diagnose efficiently, reducing manual troubleshooting time. Fault code classification (temporary / permanent) can distinguish between intermittent and persistent faults. Some codes, when triggered, will also activate the malfunction indicator lamp (MIL), reminding users to perform timely repairs. Currently, after a vehicle malfunctions, diagnostic equipment communicates with the vehicle's ECU to read fault codes and fault descriptions, such as an open circuit or short circuit in a vehicle wiring harness. However, the current methods for obtaining repair guidance information through fault codes and descriptions are relatively limited, relying on networks or human experience, resulting in lower accuracy of the obtained repair guidance information.

[0045] Therefore, some embodiments of this specification provide a vehicle fault repair method. The vehicle can have an internal file server or web server installed to store all fault numbers and corresponding repair guidance information for each fault number. If the repair guidance information is in a file format such as PDF, a file server can be used. If the repair guidance information is in a web page format, a web server can be used. The diagnostic device requests repair guidance information from the corresponding server using the ECU ID and fault code number: if it's a file server, it returns a guidance file to the diagnostic device, which can then open the file to view the repair guidance information; if it's a web server, it returns a corresponding URL, which the diagnostic device can directly access through a browser to view the content. The repair guidance information retrieved based on the fault number, stored internally by each vehicle, is more accurate. Access to the vehicle's internal server is possible without an internet connection, making it more convenient and improving the efficiency of vehicle repair and fault diagnosis.

[0046] Figure 1 These are application scenario diagrams of vehicle fault repair methods shown in some embodiments of this specification.

[0047] The vehicle fault repair method of this application embodiment can be applied to various vehicle repair scenarios. For example, remote monitoring and diagnosis of vehicles, such as manufacturers using diagnostic equipment to periodically send request commands to the electronic control unit to obtain vehicle fault information for preventative maintenance; or rapid fault diagnosis and repair, where repair personnel can obtain detailed fault information and repair instructions through a preset server when a vehicle malfunctions, quickly locate the problem and perform repairs.

[0048] The implementing entity of the technical solution in this application embodiment can be an electronic device, or a vehicle fault repair module or diagnostic device in the aforementioned electronic device, such as... Figure 1 As shown, the diagnostic device can communicate with each electronic control unit in the vehicle and a preset server configured in the vehicle. Exemplarily, the aforementioned vehicle fault repair module can be implemented through software and / or hardware. This electronic device can be deployed on a mobile device or connected to a mobile device via wired or wireless means; of course, the electronic device can also be the mobile device itself. The mobile device can have any appearance, such as a smart vehicle.

[0049] In some embodiments, the electronic device may be an in-vehicle terminal integrated into the vehicle, such as an Electronic Control Unit (ECU), Vehicle Control Unit (VCU), Microcontroller (MCU), vehicle controller, etc., or a device that interacts with the vehicle for data exchange. This application does not limit the specific type of electronic device.

[0050] When the electronic device is connected to a mobile device, the electronic device can be a terminal device, such as a smartphone, tablet, laptop, desktop computer, etc., but is not limited to this.

[0051] In some embodiments, the application scenario may also include, for example, networks, storage devices, etc. Networks may include any suitable wired or wireless networks that facilitate the exchange of information and / or data. Storage devices are used to store data, instructions, and / or any other information.

[0052] The following explanation uses a mobile device, specifically an intelligent vehicle (hereinafter referred to as a vehicle), as an example. It is important to note that the application scenarios for the component inspection method are provided for illustrative purposes only and are not intended to limit the scope of this specification. Those skilled in the art can make various changes and modifications based on the description in this specification. For example, application scenarios may also include databases, information sources, etc. Furthermore, application scenarios may be implemented on other devices to achieve similar or different functions. However, these changes and modifications will not depart from the scope of this specification.

[0053] Figure 2 This is an exemplary flowchart of a vehicle fault repair method according to some embodiments of this specification. In some embodiments, process 200 may be executed based on a diagnostic terminal. Figure 2 As shown, process 200 includes the following steps.

[0054] Step 210: Send a request command to read fault codes to multiple electronic control units of the vehicle.

[0055] A diagnostic terminal is a device or apparatus used to communicate with electronic control units (ECUs) to send request commands and receive diagnostic information. A diagnostic terminal can be a handheld device, a laptop, a tablet, or a dedicated diagnostic tool. For example, an OBD-II (On-Board Diagnostics II) scanning tool used in auto repair shops.

[0056] The diagnostic terminal can send request commands and receive vehicle fault information by connecting to the vehicle's OBD-II interface.

[0057] An electronic control unit (ECU) refers to a device or apparatus within a vehicle that can receive request commands and return diagnostic information. For example, an ECU can be one or more ECUs, or it can be a vehicle gateway or domain controller. Exemplary ECUs may include, but are not limited to, any one or a combination of: an engine control module (ECM), a transmission control module (TCM), a brake control module (BCM), a gateway controller (Gateway ECU), and an autonomous driving domain controller (ADC).

[0058] A request command is an instruction issued by the diagnostic terminal to obtain specific diagnostic information from the electronic control unit. This diagnostic information may include current fault codes, vehicle operating status, sensor data, etc. For example, a request command may include reading current fault codes, reading freeze frame data, or reading status information (such as vehicle speed and coolant temperature).

[0059] In some embodiments, the diagnostic terminal can interact with a designated electronic control unit via the vehicle's communication bus (e.g., CAN (Controller Area Network) bus), Ethernet communication protocol (e.g., DoIP), or OBD-II interface to proactively (e.g., in real time, at intervals, or triggered under certain conditions) obtain diagnostic information from the electronic control unit.

[0060] Step 220: In response to receiving the fault code and target identification information corresponding to the target electronic control unit returned by the target electronic control unit, the fault code and target identification information are sent to the vehicle's preset server to receive the target repair guidance information corresponding to the fault code returned by the preset server.

[0061] Diagnostic information is a data packet that the electronic control unit returns to the diagnostic terminal after receiving a request command. For example, diagnostic information may include diagnostic results, error codes, or status information.

[0062] In some embodiments, diagnostic information depends on the service type of the request command, and the data structure of the diagnostic information returned by different ECUs may be different.

[0063] The target electronic control unit refers to one or more specific electronic control units in a vehicle that have detected an anomaly and recorded a fault code (DTC).

[0064] In some embodiments, the diagnostic device can query all available electronic control units in the vehicle through a preset protocol (e.g., network management protocol (ISO 14229)) to obtain a list of electronic control units; and send a request command to each electronic control unit in the list to read fault codes. If a fault code exists in a certain electronic control unit, the electronic control unit is selected as the target electronic control unit, and the fault code and the target identification information corresponding to the target electronic control unit are returned; if no fault code exists, an empty or specific status code is returned.

[0065] A Diagnostic Trouble Code (DTC) is a standardized code that is recorded and stored when a target electronic control unit detects an abnormality in its control system or corresponding component, and is used to indicate the specific type of fault.

[0066] Target identification information is identification information that indicates the identity of a target electronic control unit. Identification information can be data that uniquely identifies a vehicle or ECU. For example, identification information may include VIN (Vehicle Identification Number), software version number, vehicle model number, vehicle network address (such as CAN ID), etc.

[0067] In some embodiments, the target electronic control unit may return fault information and target identification information corresponding to the target electronic control unit.

[0068] Fault information refers to the Diagnostic Trouble Code (DTC) and its related descriptive information of the target electronic control unit. This descriptive information includes, but is not limited to: freeze frame data, fault count, and fault severity level. Freeze frame data records the status information (such as vehicle speed and temperature) at the time of the fault, and the fault count records the number of times the fault occurred.

[0069] In some embodiments, the target identification information of the target electronic control unit is the identifier of the target electronic control unit (e.g., ECU ID), and the fault information is the fault code number. It is understood that in other alternative embodiments, the information fed back by the target electronic control unit may consist of more data, such as VIN codes, etc., and this is not limited here.

[0070] A pre-installed server refers to a server pre-deployed inside the vehicle to provide corresponding repair suggestions or handling information based on vehicle identification and fault information. For example, a pre-installed server could be a diagnostic coordination server on the vehicle gateway or a maintenance policy engine in the domain controller.

[0071] Targeted repair guidance information provides detailed repair instructions for specific vehicle faults, including repair sequence, repair methods, and a list of required parts. For example, for an engine misfire fault (P0300), targeted repair guidance information may include checking the spark plugs, ignition coils, and fuel injection system in sequence.

[0072] In some embodiments, users can access this target repair guidance information through a diagnostic terminal or a repair terminal. For example, repair technicians can obtain detailed repair guidance information from a pre-set server by entering the vehicle's VIN code and fault codes.

[0073] In some embodiments, the diagnostic terminal can communicate with a preset server via an in-vehicle communication network (e.g., CAN, LIN, Ethernet) to send fault codes and target identification information to the vehicle's preset server, and receive target repair guidance information corresponding to the fault codes returned by the preset server.

[0074] In some embodiments of this specification, the returned target identification information (such as VIN code, ECU ID, etc.) and fault codes can accurately identify the electronic control unit and fault codes, which helps to identify the specific type and location of the fault in the vehicle and avoids repair errors caused by misjudging the fault type or location. For example, different vehicle models or faults may require different repair methods, and accurate identification information can ensure that repair personnel use the correct repair methods. Diagnostic equipment can also directly access the vehicle's preset server without a network, which is more convenient and improves the efficiency of vehicle repair and fault diagnosis.

[0075] In some embodiments, fault codes and target identification information are sent to a preset server of the vehicle to receive target repair guidance information corresponding to the fault codes returned by the preset server, including:

[0076] The target identification information and fault code are sent to a preset server, which then uses the target identification information, fault code, and preset mapping relationship to obtain associated maintenance guidance information related to the target identification information and fault code, and sends it to the diagnostic terminal.

[0077] Among them, the preset mapping relationship is used to indicate the associated maintenance guidance information corresponding to each combination of multiple preset identification information and preset fault codes;

[0078] Based on the associated repair guidance information sent by the preset server, the target repair guidance information is determined.

[0079] The preset mapping relationship is a mapping table stored in the preset server, used to establish the correspondence between the identification information and fault code number of the electronic control unit and the maintenance guidance information. For example, the preset mapping relationship can be a database table containing the following: vehicle identification information (such as VIN code (Vehicle Identification Number)), ECU identification information (ECUID), fault information (fault code number P0300), and its corresponding associated maintenance guidance information, such as specific chapters in the maintenance manual, troubleshooting steps, lists of required tools and parts, maintenance methods, etc.

[0080] In some embodiments, preset mapping relationships are typically predefined by the vehicle manufacturer or maintenance guidance information provider and stored in a preset server. Preset mapping relationships can be updated periodically or periodically. For example, updates can be sent directly to the vehicle's preset server via a wireless network using OTA technology, or the vehicle's preset server can periodically synchronize the latest mapping relationships from a cloud server.

[0081] Associated maintenance guidance information is maintenance guidance information that is associated with specific identification information and specific fault information.

[0082] In some embodiments, the preset mapping relationship may be a preset database, and the method further includes:

[0083] Based on identification and fault information, the associated maintenance guidance information is determined through a preset database to obtain feedback information.

[0084] In some embodiments, a retrieval vector can be constructed based on target identification information and fault information; a retrieval is performed in a preset database based on the retrieval vector to determine the target vector that meets the matching conditions; and the target maintenance guidance information is obtained based on the associated maintenance guidance information corresponding to the target vector.

[0085] The preset database is used to store, index, and query vectors. It can store multiple reference vectors and their corresponding associated maintenance guidance information. Each reference vector is constructed from preset identification information and preset fault information.

[0086] The preset identification information and preset fault information that constitute the reference vector can be data from the same device.

[0087] In some embodiments, a preset database can be constructed based on historical data. For example, based on historical data, each repaired historical identification information and historical fault information can be determined as a reference vector, and the historical maintenance guidance information of the historical identification information and historical fault information can be used as the associated maintenance guidance information corresponding to the reference vector. Furthermore, a preset database can be constructed based on multiple reference vectors and their corresponding associated maintenance guidance information.

[0088] Matching conditions refer to the criteria used to determine the target vector. Matching conditions may include a vector distance to the retrieved vector that is less than a threshold. There are various methods for calculating vector distance, such as Euclidean distance and cosine distance. The first distance can be a system preset value, a system default value, etc.

[0089] In some embodiments of this specification, a preset database allows for fast retrieval and matching, which can reduce unnecessary calculations and improve processing efficiency.

[0090] In some embodiments, the target repair guidance information can be directly obtained based on the feedback information sent by the preset server, or the target repair guidance information can be obtained by dynamically adjusting the feedback information based on the feedback information sent by the preset server and the parts inventory status. For example, if the required parts are not in stock, a prompt message suggesting an appointment or recommending an alternative model will be issued.

[0091] In some embodiments of this specification, each vehicle stores its own maintenance guidance materials. This means that maintenance technicians can directly access maintenance guidance information that is perfectly matched to that vehicle. The guidance materials stored inside the vehicle are specific to that particular model and configuration, thus providing more accurate maintenance guidance and reducing maintenance errors caused by information mismatches. For example, vehicles of different years and configurations may require different maintenance procedures and parts, and the vehicle's internal server can provide the most precise guidance.

[0092] In some embodiments, the associated maintenance guidance information includes associated address information, which is used to indicate the storage address of the maintenance guidance information. The preset mapping relationship includes multiple types, and each preset mapping relationship is used to associate associated address information of different format types. The multiple format types include at least one of file format and web page format.

[0093] The associated address information is the storage address that points to the actual storage location of the repair guidance information. The storage address is the specific location on the pre-defined server where the associated repair guidance information is stored. For example, the storage address can be a file path, a database record index, a URL (Uniform Resource Locator) link, etc., used to quickly locate and access the required repair guidance information.

[0094] The file path refers to the specific location of the maintenance guidance information file stored in the server's file system. The database record index refers to the unique identifier of the maintenance guidance information record in the database. A URL link refers to the address used to access a specific resource over a network.

[0095] File paths can be predefined by the server administrator and stored in a database or configuration file.

[0096] Multiple format types refer to the format used by the content pointed to by the associated address information. Among these, file-based repair guidance information can include, but is not limited to, spreadsheets, PDF files, Word documents, presentations, technical manuals, and multimedia files (such as video and audio files). Web-based repair guidance information can include, but is not limited to, HTML pages, online manuals, and technical support forums.

[0097] In some embodiments, the preset mapping relationship includes multiple types, such as a first preset mapping relationship and a second preset mapping relationship. The first preset mapping relationship can be used to indicate the associated file address information corresponding to each combination of multiple first preset identification information and first preset fault information. The first preset mapping relationship can be used to indicate the associated web page address information corresponding to each combination of multiple second preset identification information and second preset fault information.

[0098] In some embodiments, a preset server may have one or more preset mapping relationships to support maintenance guidance information in different formats. Alternatively, one preset server may correspond to one preset mapping relationship, and multiple preset servers corresponding to different preset mapping relationships may be configured in the vehicle. Or, the IDs and fault codes of multiple electronic control units may be divided into multiple groups by a preset method, with each group corresponding to a preset mapping relationship.

[0099] For example, one preset server corresponds to one preset mapping relationship. As functionality expands and data volume increases, each preset server is only responsible for one preset mapping relationship, such as:

[0100] The default server A is used to handle the mapping relationships related to PDF files;

[0101] The default server B is used to handle the mapping relationships related to web page links.

[0102] Each server corresponds to a different preset mapping relationship, and they do not interfere with each other. If a preset server fails or needs to update its content, it will not affect the normal operation of other parts.

[0103] For example, multiple different server addresses can be configured within the vehicle. This means the vehicle can choose to access different servers depending on the current task, such as:

[0104] When maintenance technicians perform professional diagnoses, they can use a text server to obtain PDF repair manuals.

[0105] When car owners view the meaning of fault codes through a mobile app, they can use a web-based server to display text and image explanations.

[0106] When a software-related fault is detected, an OTA upgrade server can be used to obtain a firmware update.

[0107] When a fault involving parts replacement is detected, the spare parts query server can be used to obtain the part number and price.

[0108] The above methods can increase scalability and customizability, allowing for flexible switching of maintenance guidance information sources based on different user roles and usage scenarios.

[0109] For example, the IDs and fault codes of multiple electronic control units can be divided into multiple groups by a preset method, with each group corresponding to a preset mapping relationship. Since there can be multiple ECUs in a vehicle, and each ECU has different functions, structures, and common fault modes, they can be divided in the following ways:

[0110] Group power-related ECUs such as the engine control unit (PCM) and transmission control unit (TCM) together and configure mapping relationships for mechanical faults;

[0111] The body control module (BCM), air conditioning control unit, and other comfort-related ECUs are grouped into another group, and mapping relationships for electrical and sensor issues are configured.

[0112] Each ECU group corresponds to a preset mapping relationship, and each preset mapping relationship can point to a different server to improve the accuracy of fault location and match more professional maintenance guidance solutions.

[0113] For example, different vehicles can be configured with different preset servers, which can be determined according to the actual situation. For example, vehicle A can be configured with a configuration file server, while vehicle B can be configured with a website server.

[0114] In some embodiments, the target repair guidance information is one of several formats of repair guidance information.

[0115] When the associated address information is associated file address information, the format type of the target maintenance guidance information is file format, or

[0116] When the associated address information is an associated webpage address, the target repair guidance information is in webpage format.

[0117] In some embodiments, the associated address information for a file format can be a file path and file name, etc. The associated address information for a webpage format can be a URL link and webpage name, etc.

[0118] In some embodiments, the target repair guidance information is determined based on the associated repair guidance information sent by a preset server, including:

[0119] When the associated maintenance guidance information includes a target file, the target maintenance guidance information is determined based on the target file. The target file is the corresponding file that the pre-defined server finds based on the associated file address information.

[0120] When the associated repair guidance information includes associated webpage address information, the corresponding webpage content is queried based on the associated webpage address information to determine the target repair guidance information.

[0121] The target file refers to the specific file determined by the preset server based on the associated file address information, and it may contain detailed maintenance guidance information. The file path of the target file is generated by the preset server based on the target identifier information and fault information, combined with the preset mapping relationship.

[0122] In some embodiments, the diagnostic terminal can parse the target file or associated web page address information in the feedback information, access the corresponding file or web page content, and extract the target repair guidance information.

[0123] In some embodiments, during the maintenance process, key parameters of various components on the vehicle (such as engine temperature, oil pressure, etc.) can be monitored in real time, and maintenance guidance information for adjustment can be automatically recommended to maintenance personnel, or the maintenance personnel can be reminded whether the maintenance guidance information needs to be adjusted.

[0124] In some embodiments of this specification, maintenance technicians can quickly access the required maintenance guidance information via associated address information without manually searching or waiting for a server response. For example, technicians can directly access maintenance manuals (PDF format) or online video tutorials (web page format) stored on an in-vehicle server or a preset server through the electronic control unit.

[0125] Figure 3 This is an exemplary flowchart of a vehicle fault repair method according to some embodiments of this specification. In some embodiments, process 300 may be executed based on a diagnostic terminal. Figure 3 As shown, process 300 includes the following steps.

[0126] In some embodiments, the method further includes:

[0127] Step 310: Generate a vehicle fault map, which is used to characterize the fault propagation path between various components of the vehicle.

[0128] Step 320: Based on the target identification information and fault code, generate multiple sets of candidate maintenance guidance information. Each set of candidate maintenance guidance information includes at least one of maintenance sequence and maintenance method.

[0129] Step 330: Based on the vehicle fault map and candidate maintenance guidance information, predict the implementation effect of each set of candidate maintenance guidance information using a prediction model.

[0130] Step 340: Based on the implementation effect and preset optimization goals of each group of candidate maintenance guidance information, recommend target maintenance guidance information.

[0131] In some embodiments, a vehicle fault map can be constructed based on data from the vehicle to be repaired. The vehicle fault map can be graph-structured data reflecting the propagation path of vehicle faults. Graph-structured data includes nodes and edges, which represent the fault propagation relationships between various vehicle components. For example, nodes can represent various vehicle components, such as the engine, transmission, and braking system. Edges can represent the relationships between components along a fault propagation path, such as causal relationships or dependency relationships.

[0132] In some embodiments, nodes may correspond to various components of the vehicle. Node attributes can reflect the relevant characteristics of the corresponding component. For example, node attributes may include: historical maintenance records, component characteristics, component environmental characteristics, and estimated risk values. Historical maintenance records can be obtained by querying historical data. Component characteristics refer to the inherent technical parameters and functional characteristics of the component itself, such as: component type (e.g., sensor, actuator, controller), model and version, operating voltage, current range, etc. The estimated risk value refers to the risk of the vehicle's component failing within a certain period of time.

[0133] Nodes that meet the connection conditions can be connected by edges. In some embodiments, the connection conditions may include a causal relationship between two nodes that share the same fault, or that the distance between the components corresponding to the two nodes is less than a distance threshold. Edge attributes may include a component correlation coefficient, which can be determined based on the following formula:

[0134] Component correlation coefficient = the number of times the two components simultaneously failed in historical data / the sum of the total number of failures of each component.

[0135] Candidate repair guidance information is used to determine which repair guidance information will be selected as the target. In some embodiments, candidate repair guidance information is generated based on target identification information and fault information, according to preset rules or an expert system. The preset rules may be formulated by vehicle manufacturers or repair experts based on experience and historical data.

[0136] In some embodiments, the effectiveness of implementing candidate maintenance guidance information can be determined by a first prediction model based on vehicle fault maps.

[0137] Implementation effectiveness refers to the expected results of each set of candidate maintenance guidance information in practical application. For example, implementation effectiveness may include indicators such as repair success rate, maintenance time, maintenance cost, and post-maintenance risks.

[0138] In some embodiments, the first prediction model may be a graph neural network (GNN) model. In some embodiments, the input to the first prediction model may be a vehicle fault map and candidate repair guidance information, and the post-repair risk of the faulty component is output based on the nodes of the vehicle fault map as the implementation effect of the candidate repair guidance information.

[0139] In some embodiments, the first prediction model can be obtained through training. For example, the first training sample can be historical vehicle fault maps and historical repair guidance information from historical data, and the first label can be the risk situation determined by a preset table based on the failure of the component corresponding to the second training sample after repair. If the component fails within a certain period after repair, the risk situation assessed according to the preset table based on the failure situation can be used as the first label. The preset table can be preset by technicians based on historical experience. For example, the preset table can be in the following form: ([a1, b1], [a2, b2], ...), where a1, a2, ... represent historical fault situations, and b1, b2, ... represent the risk situations corresponding to the historical fault situations, wherein the risk situations corresponding to the historical fault situations involved in the vehicle fault map are used as the first label.

[0140] Preset optimization goals refer to the objectives that need to be optimized when selecting target repair guidance information, such as minimizing repair costs, maximizing repair success rate, minimizing repair time, and minimizing post-repair risks.

[0141] In some embodiments, the candidate maintenance guidance information with the lowest post-repair risk can be used as the target maintenance guidance information.

[0142] In some embodiments of this specification, based on the vehicle data to be repaired and candidate repair guidance information, a vehicle fault map is constructed, and the vehicle fault map is processed using a first prediction model to obtain the post-repair risk, thereby making the prediction of post-repair risk more consistent with reality.

[0143] In some embodiments, the estimated risk value can be determined by a second prediction model based on component characteristics, component environmental characteristics, and candidate maintenance parameters.

[0144] In some embodiments, the second prediction model can be a machine learning model, such as a neural network model. The input to the second prediction model can be component features and component environmental features, wherein maintenance parameters can be added to the input for repaired components; the output can be an estimated risk value.

[0145] In some embodiments, the second prediction model can be obtained through training. For example, the second training sample can be the component characteristics and environmental characteristics of a sample component in the first historical time period from historical data. If the sample component has been repaired, repair parameters of the sample component can be added to the input. The second label can be the risk value corresponding to the second training sample. The risk value of the second training sample can be measured based on risk-related factors such as whether the sample component has failed in the second historical time period, the type of failure, and the degree of danger of the failure. The second historical time period is later than the first historical time period.

[0146] For example, the actual risk value as the second label can be determined by the following formula:

[0147] Estimated risk value = k1 Fault type + k2 Pre-maintenance risk.

[0148] Where k1 and k2 are preset weighting coefficients. For details regarding pre-repair risks, please refer to the relevant content above.

[0149] In some embodiments of this specification, the estimated risk value is determined by a second prediction model based on component characteristics, component environmental characteristics, and maintenance parameters, which can improve the accuracy of the prediction of the estimated risk value.

[0150] In some embodiments of this specification, by taking into account various aspects of component data, the obtained post-repair risks are more comprehensive and accurate, which helps to better guide current maintenance work and effectively repair component failures.

[0151] One or more embodiments of this specification also provide a vehicle repair method, the method comprising:

[0152] Repair guidance information is an important guide for repair technicians to analyze and troubleshoot vehicle malfunctions. It can include each step of the troubleshooting process, relevant circuit diagrams, and other materials. Common vehicle repair guidance information is generally available in two formats: file format (e.g., PDF) and web page format.

[0153] A server can be set up inside the vehicle before it leaves the factory. If the maintenance instructions are in file format, a file server is set up; if the instructions are in web page format, a web server is set up. The web server can be set up on the domain controller, vehicle controller, or gateway inside the vehicle.

[0154] The server deploys a pre-defined mapping relationship between ECU IDs, fault code numbers, and repair guidance information. For example, the file server deploys a pre-defined mapping relationship between ECU IDs, fault code numbers, and specific file paths. For instance, the P1001 fault code of the engine ECU corresponds to the file ZD0082.PDF. The web server deploys a pre-defined mapping relationship between ECU IDs, fault code numbers, and web pages. For instance, the P1001 fault code of the engine ECU corresponds to the web page / / 192.168.1.100 / Engine / P1001.PHP, where 192.168.1.100 represents the web server address, Engine represents the engine ECU, and P1001.PHP is the web page containing the information.

[0155] When a vehicle malfunctions, the diagnostic equipment sends a request command to each ECU (Engine Control Unit) to read fault codes, such as 0x190208. Upon receiving this request, the specific ECU determines if a fault exists. If no fault exists, it replies with an empty string; if a fault exists, it replies with the fault code number and the ECU ID to the diagnostic equipment. The diagnostic equipment can then look up the fault description corresponding to the fault code in its fault code database, for example, P1001 - The injection valve (cylinder 1) has a short circuit to ground.

[0156] If a repair technician needs to access repair instructions for this fault, the diagnostic equipment can record the ECU ID and fault code number for further investigation. For example, the engine ECU ID is 0x7e0, and the fault code number is P1001.

[0157] If the server deployed on the vehicle is a file server, the diagnostic equipment sends the ECU ID and fault code number to the file server. The file server then uses the configured preset mapping relationship to find the corresponding file path and name of the maintenance guidance information, and then sends the file at that path to the diagnostic equipment. After receiving the file, the diagnostic equipment saves it to its local disk, and the user can open the file to view the specific content of the maintenance guidance information.

[0158] If the server deployed on the vehicle is a web server, the diagnostic equipment sends the ECU ID and fault code number to the web server. The web server can then find the corresponding webpage URL based on a preset mapping and send the URL to the diagnostic equipment. The user can open a browser (such as IE or Google Chrome) through the diagnostic equipment, pass the URL to the browser, and open the webpage content on that URL to view the specific repair guidance information.

[0159] If changes or additions to the maintenance guidance information are detected, the file server or web server can connect to the vehicle manufacturer's backend server through the vehicle's TBOX system to update the preset mapping relationship.

[0160] It should be noted that the above description of the process is for illustrative purposes only and does not limit the scope of this specification. Those skilled in the art can make various modifications and changes to the process under the guidance of this specification. However, these modifications and changes remain within the scope of this specification.

[0161] One or more embodiments of this specification also provide a file server deployed in a vehicle, the file server being used for:

[0162] Receive fault codes and target identification information from the diagnostic terminal, and obtain the associated file address information associated with the target identification information and fault codes based on the fault codes, target identification information and preset mapping relationships;

[0163] Based on the associated file address information, the corresponding file is queried to obtain the associated maintenance guidance information and sent to the diagnostic terminal.

[0164] One or more embodiments of this specification also provide a web server deployed in a vehicle, the web server being used for:

[0165] Receive fault codes and target identification information from the diagnostic terminal, and obtain associated web page address information related to the target identification information and fault codes based on the fault codes, target identification information and preset mapping relationships;

[0166] The associated webpage address information is sent to the diagnostic terminal as associated repair guidance information.

[0167] Figure 4 This is a structural schematic diagram of a vehicle fault repair device according to some embodiments of this specification.

[0168] like Figure 4 As shown in the diagram, one or more embodiments of this specification also provide a structural schematic of a vehicle fault repair device. This vehicle fault repair device may include:

[0169] The request module 401 is used to send a request command to read fault codes to multiple electronic control units of the vehicle;

[0170] The determination module 402 is used to send the fault code and target identification information corresponding to the target electronic control unit to the vehicle's preset server in response to receiving the fault code returned by the target electronic control unit and the target identification information corresponding to the target electronic control unit, so as to receive the target maintenance guidance information corresponding to the fault code returned by the preset server.

[0171] The request module 401 and the determination module 402 can be used to execute the embodiments corresponding to the above-mentioned vehicle fault repair method. For the specific implementation methods of these modules and more details, please refer to the corresponding method section, which will not be elaborated here.

[0172] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0173] Figure 5 This is a schematic diagram of the structure of an electronic device according to some embodiments of this specification.

[0174] This application embodiment also provides an electronic device 500, which may include components such as a processor 501 with one or more processing cores, a memory 502 with one or more computer-readable storage media, a power supply 503, and an input unit 504. Those skilled in the art will understand that... Figure 5 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0175] The processor 501 is the vehicle's fault repair center. It connects various parts of the electronic device via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory 502, and by calling data stored in the memory 502, thereby providing overall monitoring of the electronic device. It is understood that the processor 501 communicates with the controller via signal transmission. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may also not be integrated into the processor 501.

[0176] The memory 502 can be used to store software programs and modules. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.

[0177] In some embodiments of this application, the vehicle fault repair device can be implemented as a computer program, which can be implemented in, for example... Figure 5 The device operates on the electronic device shown. The memory of the electronic device can store various program modules that constitute the vehicle fault repair apparatus. The computer program composed of the various program modules causes the processor to execute the steps in the vehicle fault repair methods of the various embodiments of this application described in this specification.

[0178] The electronic device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The network interface is used to communicate with external electronic devices via a network connection. When the computer program is executed by the processor, it implements a vehicle fault repair method.

[0179] The electronic device also includes a power supply 503 that supplies power to various components. Preferably, the power supply 503 can be logically connected to the processor 501 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 503 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0180] The electronic device may also include an input unit 504, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0181] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 501 in the electronic device loads the executable files corresponding to the processes of one or more application programs into the memory 502 according to computer instructions, and the processor 501 runs the application programs stored in the memory 502 to realize various functions, such as the vehicle fault repair methods of the various embodiments of this application described in this specification.

[0182] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0183] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.

[0184] It should be noted that, Figure 5 This is merely one implementation of the electronic device 500 provided in this application embodiment. In actual applications, the electronic device 500 may include more or fewer components, which is not limited here.

[0185] It should be understood that the various solutions in the embodiments of this application can be used in a reasonable combination, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0186] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0187] Based on the above embodiments and the same concept, this application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method provided in the above embodiments.

[0188] Based on the above embodiments and the same concept, this application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to execute the method provided in the above embodiments.

[0189] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0190] The embodiments, implementation methods, and related technical features of this application can be combined and substituted for each other without conflict.

[0191] The above are merely preferred embodiments of this application and are not intended to limit this application in any way. Although the descriptions of each embodiment in this application have different focuses, and the parts not described in detail in a certain embodiment can be referred to the relevant embodiments of other embodiments, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of this application without departing from the content of the technical solution of this application shall still fall within the scope of the technical solution of this application.

Claims

1. A method for repairing vehicle malfunctions, characterized in that, Applied to a diagnostic terminal, the method includes: Sends a request command to read fault codes to multiple electronic control units of the vehicle; In response to receiving a fault code and target identification information corresponding to the target electronic control unit, the fault code and target identification information are sent to a preset server of the vehicle to receive target repair guidance information corresponding to the fault code returned by the preset server.

2. The method according to claim 1, characterized in that, The step of sending the fault code and the target identification information to the vehicle's preset server, and receiving the target repair guidance information corresponding to the fault code returned by the preset server, includes: The target identification information and the fault code are sent to the preset server, so that the preset server can obtain associated maintenance guidance information related to the target identification information and the fault code based on the target identification information, the fault code, and a preset mapping relationship, and send it to the diagnostic terminal. The preset mapping relationship is used to indicate the associated maintenance guidance information corresponding to each combination of multiple preset identification information and preset fault codes; Based on the associated repair guidance information sent by the preset server, the target repair guidance information is determined.

3. The method according to claim 2, characterized in that, The associated repair guidance information includes associated address information, which is used to indicate the storage address of the repair guidance information. The preset mapping relationship includes multiple types, and each preset mapping relationship is used to associate associated address information of different format types. The multiple format types include at least one of file format and web page format.

4. The method according to claim 3, characterized in that, The target repair guidance information is one of several formats. When the associated address information is associated file address information, the format type of the target maintenance guidance information is a file format, or When the associated address information is associated webpage address information, the format type of the target maintenance guidance information is webpage format.

5. The method according to claim 3, characterized in that, The determination of the target repair guidance information based on the associated repair guidance information sent by the preset server includes: When the associated maintenance guidance information includes a target file, the target maintenance guidance information is determined based on the target file, wherein the target file is the corresponding file queried by the preset server based on the associated file address information; When the associated repair guidance information includes associated webpage address information, the corresponding webpage content is queried based on the associated webpage address information to determine the target repair guidance information.

6. The method according to claim 1, characterized in that, The method further includes: Generate a vehicle fault map, which is used to characterize the fault propagation path between various components of the vehicle; Based on the target identification information and the fault code, multiple sets of candidate maintenance guidance information are generated, and each set of candidate maintenance guidance information includes at least one of maintenance sequence and maintenance method; Based on the vehicle fault map and the candidate maintenance guidance information, the implementation effect of each group of candidate maintenance guidance information is predicted by a prediction model. Based on the implementation effect and preset optimization goals of each group of candidate maintenance guidance information, target maintenance guidance information is recommended.

7. A file server deployed in a vehicle, characterized in that, The file server is used for: Receive fault codes and target identification information from the diagnostic terminal, and obtain associated file address information associated with the target identification information and the fault codes based on the fault codes, the target identification information, and a preset mapping relationship; Based on the associated file address information, the corresponding file is queried to obtain the associated maintenance guidance information and sent to the diagnostic terminal.

8. A website server deployed in a vehicle, characterized in that, The website server is used for: Receive fault codes and target identification information from the diagnostic terminal, and obtain associated web page address information related to the target identification information and the fault codes based on the fault codes, the target identification information, and a preset mapping relationship; The associated webpage address information is sent to the diagnostic terminal as associated repair guidance information.

9. A vehicle fault repair device, characterized in that, The device includes: The request module is used to send request commands to read fault codes to multiple electronic control units of the vehicle; The determination module is used to respond to receiving a fault code returned by a target electronic control unit and target identification information corresponding to the target electronic control unit, and send the fault code and the target identification information to a preset server of the vehicle, so as to receive target repair guidance information corresponding to the fault code returned by the preset server.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images