Vehicle fault maintenance guidance method and device, and storage medium

Abstract

This application discloses a vehicle fault repair guidance method, apparatus, and storage medium. The method includes: acquiring vehicle information and diagnostic information of a target vehicle; determining the target fault location and the target fault information corresponding to the target fault code based on a preset fault resolution rule base; determining the fault cause and repair plan based on the target fault information; determining the target fault handling difficulty level based on the fault cause, repair plan, target fault occurrence time, and vehicle information; when the target fault handling difficulty level is less than a preset fault handling difficulty level, obtaining m first images by acquiring first images of repair tools in a target repair toolkit; determining repair tool information based on the m first images; generating a target repair guidance plan based on the repair plan and repair tool information; and visually displaying the target repair guidance plan. Using the embodiments of this application can improve the efficiency of handling vehicle faults after they occur.

Description

Technical Field

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

[0002] With the development of automotive intelligence, cars are no longer just simple means of transportation. Car owners are starting to pay attention to more aspects of their vehicles, such as remote fault diagnosis and maintenance, for a better experience. Remote automotive fault diagnosis refers to the process of obtaining fault information about the car upon startup, determining a solution through a data processing center, and remotely eliminating the fault or allowing the owner to be informed of potential problems in advance for timely prevention. Currently, when a vehicle malfunctions, the usual methods are to transport the vehicle to a repair shop and wait for mechanics to inspect and repair it, or to contact a mechanic to come to the location of the fault. These methods require car owners to spend a significant amount of time and energy waiting for the problem to be resolved.

[0003] In practical applications, some vehicle malfunctions can be resolved by the user themselves. For example, when a vehicle malfunctions, the onboard device can diagnose the problem and provide operational guidance, or a remote repair procedure can be provided, allowing the owner to resolve the issue remotely. However, these repair procedures are often described from the perspective of professional repair personnel, containing fault codes and numerous technical terms, making them complex and difficult for car owners to understand, thus significantly increasing the difficulty of repairs. Therefore, the issue of providing visualized repair guidance when vehicle malfunctions occur, and thus enabling more efficient vehicle troubleshooting, urgently needs to be addressed. Summary of the Invention

[0004] This application provides a vehicle fault repair guidance method, device, and storage medium, which can provide a visualized repair guidance scheme according to the difficulty of fault repair of the target vehicle, thereby improving the efficiency of handling faults after a vehicle malfunctions.

[0005] In a first aspect, embodiments of this application provide a vehicle fault repair guidance method, applied to an in-vehicle device, the in-vehicle device including a camera module, a diagnostic device, and a display device, the method comprising:

[0006] Obtain vehicle information for the target vehicle;

[0007] The diagnostic equipment is used to obtain diagnostic information of the target vehicle, including the target fault location, the time of the target fault occurrence, and the target fault code.

[0008] The target fault location and the target fault code are determined according to a preset fault resolution rule base; the preset fault resolution rule base stores the preset correspondence between fault locations, fault codes and fault information.

[0009] Determine the cause of the fault and the repair plan based on the target fault information;

[0010] Based on the cause of the fault, the repair plan, the time of occurrence of the target fault, and the vehicle information, the target fault handling difficulty level of the target vehicle is determined, and the target fault handling difficulty level is used to indicate the severity of the vehicle fault;

[0011] When the target fault handling difficulty level is less than the preset fault handling difficulty level, the camera module acquires the first image of the repair tools in the target repair tool kit, resulting in m first images; m is an integer greater than 1.

[0012] The repair tool information of the target vehicle is determined based on the m first images;

[0013] Based on the repair plan and the repair tool information, a target repair guidance plan is generated;

[0014] The target repair guidance plan is visualized using the display device.

[0015] Secondly, embodiments of this application provide a vehicle fault repair guidance device, applied to in-vehicle equipment. The device includes: an acquisition module, a determination module, a generation module, and a display module, wherein:

[0016] The acquisition module is used to acquire vehicle information of the target vehicle; acquire diagnostic information of the target vehicle, the diagnostic information including target fault location, target fault occurrence time, and target fault code;

[0017] The determining module is used to determine the target fault location and the target fault code corresponding to the target fault information according to a preset fault resolution rule base; the preset fault resolution rule base stores a preset correspondence between fault locations, fault codes and fault information; determine the fault cause and repair plan according to the target fault information; and determine the target fault handling difficulty level of the target vehicle based on the fault cause, the repair plan, the time of occurrence of the target fault and the vehicle information, wherein the target fault handling difficulty level is used to indicate the severity of the vehicle fault.

[0018] The acquisition module is further configured to, when the target fault handling difficulty level is less than the preset fault handling difficulty level, acquire first images of the repair tools in the target repair tool kit through the camera module, and obtain m first images; m is an integer greater than 1.

[0019] The determining module is further configured to determine the repair tool information of the target vehicle based on the m first images;

[0020] The generation module is used to generate a target repair guidance plan based on the repair plan and the repair tool information;

[0021] The display module is used to visually display the target maintenance guidance plan.

[0022] Thirdly, this application provides an in-vehicle device, including: a processor and a memory, the memory being used to store one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps in the first aspect of this application.

[0023] Fourthly, this application provides a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the first aspect of this application.

[0024] Fifthly, this application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the first aspect of this application. The computer program product may be a software installation package.

[0025] As can be seen, the vehicle fault repair guidance method described in this application embodiment obtains vehicle information of the target vehicle; obtains diagnostic information of the target vehicle, the diagnostic information including target fault location, target fault occurrence time, and target fault code; then, determines the target fault information corresponding to the target fault location and the target fault code according to a preset fault resolution rule base; the preset fault resolution rule base stores a preset correspondence between fault location, fault code, and fault information; determines the fault cause and repair plan based on the target fault information; and determines the fault information based on the fault cause, the repair plan, the target fault occurrence time, and the vehicle information. The system identifies a target fault handling difficulty level for the target vehicle, which represents the severity of the fault. Then, when the target fault handling difficulty level is less than a preset fault handling difficulty level, the camera module captures first images of the repair tools in the target repair toolkit, resulting in m first images (m being an integer greater than 1). The repair tool information for the target vehicle is determined based on these m first images. Finally, a target repair guidance plan is generated based on the repair plan and the repair tool information. This target repair guidance plan is then visualized, saving users time in troubleshooting and enabling more efficient vehicle fault handling. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0027] Figure 1 This is a page display diagram of a vehicle fault repair guide provided in an embodiment of this application;

[0028] Figure 2 This is a flowchart of a vehicle fault repair guidance method provided in an embodiment of this application;

[0029] Figure 3 This is a block diagram of the functional modules of a vehicle fault repair guidance device provided in an embodiment of this application;

[0030] Figure 4 This is a schematic diagram of the structure of a vehicle-mounted device provided in an embodiment of this application. Detailed Implementation

[0031] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0032] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0033] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document indicates that the preceding and following related objects are in an "or" relationship. In the embodiments of this application, "multiple" refers to two or more.

[0034] In the embodiments of this application, "at least one item" or its similar expression refers to any combination of these items, including any combination of a single item or a plurality of items. "One or more" means one or more, while "multiple" means two or more. For example, "at least one item" of a, b, or c can represent the following seven cases: a, b, c; a and b; a and c; b and c; a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0035] In this application, the term "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices. This application does not impose any limitations on this.

[0036] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0037] The following will explain some of the names involved in the embodiments of this application:

[0038] Maintenance Guidelines: Maintenance guidelines are a series of instructions on how to diagnose and resolve specific equipment or system problems. They typically include explanations of common faults, diagnostic methods, and corresponding maintenance procedures and recommendations. These guidelines aim to help technicians or users quickly locate problems and take appropriate corrective action to ensure the proper functioning of the equipment or system. Maintenance guidelines include fault symptoms, possible causes of the fault, troubleshooting procedures, and maintenance recommendations. Sometimes, they also include preventative maintenance suggestions to reduce the likelihood of future faults.

[0039] Maintenance terminology: Professional terminology refers to the standardized industry-specific names for certain things in a particular field. These terms are used to facilitate professional communication and simplify names. Professional terminology is relative to everyday language and generally refers to a brief description of the proprietary names of a particular industry, usually familiar to professionals in that field. In maintenance terminology, it refers to the simplification of specific terms, tools, and models in the maintenance field, as well as abbreviations of maintenance procedures. For example, oil leakage refers to the phenomenon of oil running, leaking, dripping, or seeping from equipment; its indicator is the leakage rate, and leak prevention measures should be taken upon discovery of a leak.

[0040] Vehicle breakdowns often occur while driving. Traditional solutions typically involve contacting a mechanic to travel to the location of the breakdown or having the vehicle towed to a repair shop and waiting for repairs. This process is time-consuming and energy-intensive for users. However, sometimes vehicle malfunctions are less severe, and some repairs can be performed by the user. For example, when a vehicle breaks down, diagnostic equipment can diagnose the problem and provide operational instructions. Users can then follow these instructions to troubleshoot. However, these instructions are often written from a professional mechanic's perspective, containing fault codes and technical jargon, making them complex and difficult for users to understand, significantly hindering remote repairs. Therefore, providing visualized repair guidance when a vehicle breaks down to facilitate more efficient troubleshooting is a pressing issue.

[0041] To address the aforementioned issues, this application provides a vehicle fault repair guidance method, apparatus, and storage medium, applied to in-vehicle equipment. The method involves: acquiring vehicle information of a target vehicle; acquiring diagnostic information of the target vehicle through a diagnostic device, the diagnostic information including the target fault location, the target fault occurrence time, and the target fault code; determining target fault information corresponding to the target fault location and the target fault code based on a preset fault resolution rule base; pre-storing a preset correspondence between fault locations, fault codes, and fault information in the preset fault resolution rule base; determining the fault cause and repair plan based on the target fault information; and determining the fault cause and repair plan based on the fault cause and the target fault code. The repair plan, the time of occurrence of the target fault, and the vehicle information determine the target fault handling difficulty level of the target vehicle, which indicates the severity of the vehicle fault. When the target fault handling difficulty level is less than a preset fault handling difficulty level, the camera module captures first images of the repair tools in the target repair tool kit, obtaining m first images; m is an integer greater than 1. The repair tool information of the target vehicle is determined based on the m first images. Based on the repair plan and the repair tool information, a target repair guidance plan is generated. The target repair guidance plan is visualized through the display device. It can provide visualized repair guidance when a vehicle fault occurs, helping to handle vehicle faults more efficiently.

[0042] Please see Figure 1 , Figure 1 This is a page display diagram of a vehicle fault repair guide provided in an embodiment of this application. As can be seen, in this page display diagram 100, the user can understand the cause of the fault based on the fault phenomenon. When the user is dealing with the fault, the interface will provide a fault-solving guide and prompt the user to complete the fault resolution.

[0043] In one possible implementation, when the malfunction indicator lamp on the vehicle's dashboard illuminates, the system interface first automatically displays a prompt message to ensure the user is immediately aware of the fault. Subsequently, a prominent "Start Fault Check" virtual button will appear on the interface, which the user can click to initiate the fault check process. Once the user clicks this button, the interface will guide the user through the first step of the fault handling process, clearly instructing them on how to perform this initial step. After the user successfully follows the first step, the status bar at the bottom of the interface will update in real time, displaying the completion progress of the current repair plan, allowing the user to intuitively understand the progress of the fault handling. The user will then follow the second, third, and fourth steps displayed on the interface sequentially; the specific number and content of these steps will vary depending on the complexity of the fault type. This process will continue until the status bar shows 100% completion of the repair plan, indicating that the fault has been successfully resolved.

[0044] As can be seen, throughout the entire repair guidance process, the system interface displays information using a combination of concise text and illustrations, ensuring that users can quickly and accurately understand and implement troubleshooting solutions. Furthermore, the system provides voice prompts to further facilitate user understanding and operation, ensuring comprehensive and effective support when facing complex repair tasks. This design not only enhances the user experience but also significantly improves the efficiency and success rate of vehicle fault handling.

[0045] Please see Figure 2 , Figure 2 This is a flowchart illustrating a vehicle fault repair guidance method provided in an embodiment of this application, applied to an in-vehicle device, which includes a camera module, diagnostic equipment, and a display device; as shown below. Figure 2 As shown, the method includes, but is not limited to, the following steps:

[0046] S210. Obtain vehicle information of the target vehicle.

[0047] The vehicle information includes the target vehicle's brand, model, year, vehicle identification number (VIN), and mileage. This vehicle information can be automatically obtained through the diagnostic interface of the onboard equipment or collected through user input. The vehicle brand, model, and year help determine the vehicle's technical specifications and fault characteristics, the VIN can be used to identify the vehicle's original engine model, and the mileage helps assess the vehicle's usage condition, potential fault risks, and repair difficulty.

[0048] S220. Obtain diagnostic information of the target vehicle through the diagnostic equipment. The diagnostic information includes the target fault location, the target fault occurrence time, and the target fault code.

[0049] The diagnostic information is generated by establishing a communication connection between the diagnostic equipment and the electronic control unit of the target vehicle. The diagnostic equipment automatically scans various systems of the target vehicle through its built-in diagnostic program, identifies and records the faults that occur, and transmits the faults to the diagnostic equipment. The diagnostic information includes the location of the target fault, the time of occurrence of the target fault, and the target fault code.

[0050] The target fault location refers to the specific location of a fault in a particular component or system within the target vehicle. This information is typically detected and recorded by the vehicle's self-diagnostic system using sensors, and may include the engine, transmission, braking system, and electrical system. Accurate fault location identification guides repair personnel or users to quickly pinpoint the problem. Furthermore, the target fault location can be combined with historical vehicle data to determine if the fault is recurring, thereby optimizing the repair plan. The target fault occurrence time refers to the time when the fault was first identified. This time information can be used to trace the cause of the fault, assess its duration, and analyze its impact on vehicle operation. By comparing it with the vehicle's driving records and other diagnostic information, it is possible to determine the operational status prior to the fault. The status includes user operating habits, road conditions, and vehicle load. Furthermore, recording the time of fault occurrence can be used to calculate the duration of the fault, helping to determine its urgency. The target fault code is a specific code generated by the on-board diagnostic equipment and system to represent the type of fault detected during the vehicle's self-diagnosis process. Fault codes typically include a combination of letters and numbers for easy identification and classification. The main function of fault codes is to simplify the fault identification process, enabling technicians to quickly understand the vehicle's problem. Through fault codes, detailed information related to the fault can be obtained, such as the fault description, possible causes, and recommended repair steps. Fault codes can not only be used to detect single faults but also help diagnose the correlation between multiple faults. For example, the appearance of multiple fault codes may indicate a complex problem within the vehicle system.

[0051] S230. Determine the target fault location and the target fault information corresponding to the target fault code according to the preset fault resolution rule base; the preset fault resolution rule base stores the preset correspondence between fault location, fault code and fault information.

[0052] The diagnostic equipment interacts with a pre-set fault resolution rule base, inputting the acquired target fault location and target fault code into the base for querying and matching to obtain the target fault cause and fault information corresponding to the target fault code. The pre-set fault resolution rule base contains a large amount of fault data, including fault location, corresponding fault code, and related fault descriptions and handling suggestions. The structure of the rule base is typically in key-value pair format, where each fault code corresponds to one or more fault information entries. For example, if the diagnostic equipment detects fault code "P0301," the system will find the corresponding fault information, such as "central brake light fault," and further analyze the associated fault location and repair suggestions. In this way, users can quickly obtain detailed fault causes, improving the efficiency and accuracy of fault diagnosis. Furthermore, the construction of the pre-set fault resolution rule base relies on a large amount of historical data and expert experience to ensure its accuracy and practicality. The rule base is regularly updated and maintained; no specific restrictions are placed on the specific rules for handling the fault.

[0053] In one possible embodiment, the target fault information includes the fault occurrence time period; the step of determining the target fault location and the target fault code corresponding to the target fault information according to a preset fault resolution rule base; and determining the fault cause and repair plan based on the target fault information, includes:

[0054] 31. Obtain the fault records corresponding to the target fault code, resulting in e fault records; e is an integer greater than 1;

[0055] 32. Obtain the fault time of each fault record in the e fault records to obtain e fault times, and obtain the fault time closest to the current time among the e fault times to obtain the first fault time;

[0056] 33. Determine the fault occurrence time period based on the first fault time and the target fault occurrence time;

[0057] 34. Determine the first cause of the fault corresponding to the target fault code;

[0058] 35. Analyze the fault occurrence time period and the target fault location to obtain the cause of the fault;

[0059] 36. Determine the cause of the first fault and the corresponding repair plan.

[0060] The diagnostic equipment directly extracts data from the vehicle's fault storage module. This data records faults that occurred on the target vehicle at different times. The on-board diagnostic equipment system sorts these fault times and selects the most recent fault time among those with the same fault; this time is called the first fault time. By determining the first fault time, technicians can understand the most recent occurrence time of the fault, which is crucial for assessing its urgency. The system determines the fault occurrence time cycle based on the first fault time and the target fault occurrence time. A short fault occurrence time cycle indicates that the fault may be periodic, while a longer cycle suggests it may be an intermittent fault.

[0061] Next, the system will determine the primary cause of the fault based on the target fault code. This step is accomplished by searching for the corresponding information of the target fault code in the fault resolution rule base. Each fault code is usually associated with multiple possible causes. The system will select the most probable cause for further analysis based on historical records and correlation analysis. The diagnostic equipment's system performs in-depth analysis based on the fault occurrence time period and the target fault location to confirm the specific fault cause. If the fault code indicates a problem related to engine performance and the fault occurrence time period is relatively short, combined with the fact that the target fault location is in the engine area, technicians may deduce fault information related to the fuel system or ignition system. This analysis helps narrow down the scope of inspection and improves the efficiency of fault diagnosis.

[0062] Finally, the system will determine the appropriate repair plan based on the primary cause of the fault and the underlying cause. Each fault cause may correspond to multiple different repair plans, ranging from simple repair steps to complex repair instructions, ensuring that users have choices. When selecting a repair plan, users can make the most appropriate decision based on the severity and complexity of the fault and their own repair capabilities. For example, for minor faults, users can choose some simple and easy-to-follow self-repair plans.

[0063] As can be seen, the diagnostic equipment can effectively obtain the fault records of the target vehicle by directly extracting and matching the data of the vehicle fault storage module. Then, the system searches for and analyzes possible fault causes based on the target fault code, and confirms the specific fault cause by combining the fault occurrence time period and the target fault location. Finally, the system formulates multiple repair plans for the user to choose from. The user can make a reasonable decision based on the severity and complexity of the fault. This process improves the efficiency of fault handling and reduces the user's time and energy costs.

[0064] S240. Determine the cause of the fault and the repair plan based on the target fault information.

[0065] The fault information includes the time of occurrence, fault codes, and related vehicle data. Diagnostic equipment can compare data with a pre-set fault database and previous fault cases to identify commonalities and patterns in similar faults. By combining the time of occurrence and the vehicle's operating status, the system assesses the severity of the fault and its impact on vehicle performance. Furthermore, considering differences in vehicle brand and model, the system can provide more accurate repair suggestions. After determining the cause of the fault, the system generates corresponding repair plans based on different fault types. These plans may include specific repair steps, required tools and parts, and the best repair method for different faults. The development of repair plans can leverage machine learning, deep learning, big data analysis, and expert repair advice, among other methods, and is optimized based on historical repair data to ensure the effectiveness and feasibility of the recommendations.

[0066] S250. Based on the cause of the fault, the repair plan, the time of occurrence of the target fault, and the vehicle information, determine the target fault handling difficulty level of the target vehicle. The target fault handling difficulty level is used to indicate the severity of the vehicle fault.

[0067] The system assesses the causes of malfunctions to determine their complexity. For example, if the cause involves the interconnection of multiple components or systems, the difficulty level will be correspondingly higher. The complexity of the repair plan is also considered; for instance, some malfunctions may require specific tools or specialized technician skills, increasing the difficulty of handling them. The system records the occurrence time of the target malfunction to analyze its duration and response time. If a malfunction has persisted for a long time without being addressed, its severity and difficulty of handling will be considered higher. Furthermore, vehicle information (such as brand, model, and mileage) will be considered, as certain brands or models may have specific malfunction modes and varying levels of difficulty, thus influencing the overall judgment. By comprehensively analyzing this information, the system will calculate and evaluate to arrive at a clear target malfunction handling difficulty level. This classification system not only helps technicians understand the severity of the current fault but also provides crucial information for subsequent repair planning and resource allocation. For example, it can be divided into five different levels, each corresponding to whether the user can resolve the issue independently: Level 1: Simple. This type of fault is very easy to repair; the owner doesn't need specialized knowledge or tools to fix it, such as restarting the device or fixing loose connections. Level 2: The owner can repair it themselves using the device's built-in repair manual or by searching for the fault. Level 3: Requires basic professional knowledge. This type of fault involves some technical operations; the owner needs certain technical knowledge or experience, or to refer to detailed repair instructions and have some hands-on ability to resolve it. Level 4: Requires professional technicians. This type of fault requires the intervention of professional repair technicians; the user cannot repair it themselves, and the operation is complex. Level 5: This type of fault is very complex and requires the vehicle to be transported to a repair shop for inspection and repair. During the process, technicians can develop corresponding strategies based on the difficulty level of the target fault. For example, if the repair difficulty level is high, the user may be advised to contact a repair shop for a solution; conversely, if the difficulty level is low, the fault can be resolved quickly to avoid unnecessary delays.

[0068] In one possible embodiment, the vehicle information includes brand, model, and target vehicle runtime. Determining the target fault handling difficulty level of the target vehicle based on the fault cause, the repair plan, the target fault occurrence time, and the vehicle information includes:

[0069] 51. Get the current time;

[0070] 52. Determine the duration of the fault of the target vehicle based on the time of occurrence of the target fault and the current time, wherein the duration of the fault is the length of time from the time of occurrence of the target fault to the current time;

[0071] 53. The urgency of the fault handling is determined by evaluating the duration of the target fault and the running time of the target vehicle.

[0072] 54. Evaluate the fault handling complexity based on the brand, model, cause of failure, and repair plan;

[0073] 55. The target fault handling difficulty coefficient is obtained by weighting the fault handling urgency and the fault handling complexity.

[0074] 56. Determine the target fault handling difficulty level based on the preset fault handling level threshold and the target fault handling difficulty coefficient.

[0075] The current time, obtained through the system clock, is compared with the time the target fault occurred for subsequent analysis. At this point, the system can clearly identify the duration of the fault—that is, the time elapsed since the fault occurred on the target vehicle—and thus calculate the urgency of the fault handling. The longer the fault duration, the greater the potential impact on vehicle safety and functionality. Therefore, the system will determine the priority of fault handling based on set conditions. For example, if the fault duration exceeds a certain threshold, it may be marked as a high-priority fault, prompting the user to handle it immediately.

[0076] Next, the system assesses the complexity of fault handling based on information such as the vehicle's brand, model, cause of the fault, and repair plan. Different brands and models of vehicles differ in design and construction, so the complexity of fault handling will also vary. At this point, the system will obtain information from the database, compare the fault type with the vehicle information, and analyze the complexity index of fault handling. The higher the complexity, the more professional skills and tools are required for repair, the longer the processing time will be, and the greater the difficulty of handling the fault.

[0077] Then, a weighted calculation is performed based on the urgency and complexity of the fault handling to obtain the target fault handling difficulty coefficient. Here, different weights are assigned to each factor; the higher the weight, the greater the difficulty of handling the fault. The two factors are then combined according to a certain weight to form a comprehensive index. This index can provide users with a clear understanding of the overall difficulty of handling the fault.

[0078] Finally, the system determines the target fault handling difficulty level based on the preset fault handling level range and the target fault handling difficulty coefficient. These ranges are usually derived from historical data and expert experience, and may be divided into 1-5 levels. If the target fault handling difficulty coefficient is below the preset range, the system will rate it as Level 1, indicating that the fault has a small impact on the vehicle and the repair work is relatively simple; if the coefficient is between Level 2 and Level 3, it will be rated as Level 3, which means that some technical intervention is required; if it is between Level 3 and Level 4, it will be rated as Level 4, which means that the fault is serious and needs to be dealt with first; if it is between Level 4 and Level 5, it will be rated as Level 5, which means that the fault is extremely serious and the user needs to contact a repair technician.

[0079] As can be seen, by comparing the current time with the time the fault occurred, the system can clearly identify the ongoing impact of the fault, thereby assessing its potential threat to vehicle safety and performance. Furthermore, different brands and models of vehicles may have significant differences in structure and function, leading to varying degrees of difficulty in fault handling. By combining fault information with the specific vehicle model, the weighted calculation of the target fault handling difficulty coefficient, through reasonably set weights, ensures a balance between urgency and complexity in the decision-making process, resulting in a more comprehensive final difficulty level assessment. The preset threshold provides the system with a clear judgment standard, ensuring a rapid and appropriate response to different fault situations. This not only efficiently and accurately assesses the difficulty level of target fault handling but also provides important references for subsequent repair plans. This systematic analysis process helps improve the efficiency and safety of vehicle repair, ensuring a rapid and effective response to vehicle faults in emergencies, and maximizing the safety of vehicle owners and passengers.

[0080] In one possible embodiment, the target fault handling difficulty coefficient is obtained by weighted calculation based on the fault handling urgency and the fault handling complexity, including:

[0081] 551. Based on the preset first weight factor, second weight factor, first weight calculation formula, fault handling urgency, and fault handling complexity, a weight calculation is performed to obtain the fault handling difficulty coefficient. The first weight calculation formula is: P = a × T + b × E + c, where T is the fault handling urgency, E is the fault handling complexity, a is the first weight factor, b is the second weight factor, and c is the first error factor.

[0082] 552. Obtain the model year of the target vehicle, and determine the usage duration of the target vehicle based on the model year of the target vehicle;

[0083] 553. Determine the third weighting factor based on the usage duration;

[0084] 554. The target fault handling difficulty coefficient is obtained by calculating based on the fault handling difficulty coefficient, the third weight factor, and the second weight calculation formula. The second weight calculation formula is: D = d × P + j, where D is the target fault handling difficulty coefficient, d is the third weight factor, and j is the second error factor.

[0085] The urgency of fault handling refers to assessing the imminent impact of a fault on vehicle operational safety based on its cause, type, and severity. This assessment can be completed through analysis of fault characteristics, combined with historical fault data and industry standards. Specifically, the urgency of fault handling can include multiple dimensions, such as the degree of threat the fault poses to vehicle safety, its impact on vehicle functionality, and the potential risks to user safety. Fault handling complexity involves the expertise and technical level required for fault diagnosis and repair. This complexity can be assessed based on the specific nature of the fault, the required tools and equipment, and the complexity of the related repair solutions. For example, some faults may be resolved with simple tools and lower technical skills, while others may involve complex system diagnosis and multi-step repair processes. When calculating the target fault handling difficulty coefficient, the weights of the urgency and complexity of fault handling need to be considered. The weighting factors can be set based on past repair experience, industry standards, or data analysis to ensure the accuracy and reliability of the assessment. For example, high-risk faults may be assigned higher weighting factors to reflect their importance in fault handling. Using the methods described above, the system can not only dynamically assess the difficulty of handling vehicle malfunctions, but also provide practical suggestions to repair personnel, helping them develop effective repair strategies. This comprehensive assessment approach will greatly improve the efficiency of malfunction handling, reduce vehicle repair time, and mitigate safety hazards caused by malfunctions.

[0086] As can be seen, in this embodiment, by comprehensively analyzing multiple factors such as the urgency and complexity of fault handling and the duration of vehicle use, the assessment of the difficulty coefficient of the target fault handling can fully reflect the current fault status of the vehicle. This methodology helps to ensure the scientific and effective nature of maintenance decisions, ultimately providing users with safer and more reliable services.

[0087] S260. When the target fault handling difficulty level is less than the preset fault handling difficulty level, the camera module acquires the first image of the repair tool in the target repair tool kit to obtain m first images; m is an integer greater than 1.

[0088] The system uses m initial images to represent the diversity and quantity of repair tools, ensuring users have a comprehensive understanding of the required tools. Through high-resolution image acquisition by the camera module, the system records the appearance, shape, and size of the repair tools in detail for subsequent tool identification and classification. These images are transmitted to the processing unit in real time for preliminary analysis to identify and confirm the type and purpose of each tool. Image acquisition can be performed automatically when the user initiates the repair procedure. The system judges the complexity and difficulty of the current fault handling, ensuring image acquisition only occurs when the handling difficulty is low. This process improves work efficiency and avoids unnecessary complex tool preparation by the user. Simultaneously, the system records the acquisition time and environmental conditions of each image for subsequent data analysis and tool usage tracking. In the subsequent processing of these initial images, the system can perform image enhancement and feature extraction for more accurate tool identification and comparison. Based on these images, the system can generate information about the target repair tool, including its name, purpose, and association with the current repair plan.

[0089] S270. Determine the repair tool information of the target vehicle based on the m first images.

[0090] The repair tool information includes detailed data such as the tool's name, model, specifications, and purpose. The system identifies the tools by processing and analyzing m initial images. This process involves image recognition technology combined with a pre-trained deep learning model to ensure high accuracy and fast response. The repair tool information can be extracted from a pre-set tool database that stores relevant information for various repair tools, ensuring the system can accurately match the identified tools. Furthermore, the acquisition of repair tool information can be based on multiple criteria, including image features, color, shape, and size, ensuring comprehensive coverage of potential repair needs.

[0091] In one possible embodiment, determining the repair tool information of the target vehicle based on the m first images includes:

[0092] 71. Obtain a target first image, wherein the target first image is any one of the m first images;

[0093] 72. The target first image is identified using image recognition technology to obtain the target repair tool feature data;

[0094] 73. Determine the first tool data corresponding to the first image of the target based on the target repair tool feature data;

[0095] 74. Obtain the target standard image set corresponding to the first tool data from the preset standard image library. The preset standard image library stores k standard image sets, and each standard image set corresponds to p standard images of a tool, where k is an integer greater than 1 and p is an integer greater than or equal to k.

[0096] 75. Determine the repair tool information of the target vehicle based on the target standard image set.

[0097] The system analyzes the target first image using image recognition technology to extract feature data of the repair tools, thereby identifying the specific tool. The identified tool data is then matched against a set of standard images in a pre-set standard image library to ensure accuracy. This process not only improves the efficiency of tool identification but also ensures the smooth progress of repair work.

[0098] S280. Generate a target repair guidance plan based on the repair plan and the repair tool information.

[0099] The target repair guidance plan includes detailed repair steps, required tool information, and operational precautions. It first combines the repair plan with tool information, using logical analysis and prioritization to create a clear operational process. The guidance plan is presented in a graphic format, including specific information on the tools required for each step and their usage. Based on the complexity of the fault and the difficulty of the repair, it provides corresponding safety warnings and optimization suggestions to ensure the smooth progress of the repair process. The target repair guidance plan not only improves repair efficiency but also helps users reduce errors and risks in actual operation, ensuring repair quality. Furthermore, the guidance plan will be provided in the form of electronic documents or a visual interface for easy access and execution by users at any time.

[0100] The system retrieves the types and quantities of repair tools from the repair tool information to generate a candidate repair tool list. These candidate repair tools are then compared with the target repair tools to determine whether they meet the tool requirements of the repair plan. If the types and quantities of the candidate repair tools meet the requirements of the tools listed in the repair plan, the system determines that the user can handle the fault on their own and generates a corresponding target repair guidance plan. If the candidate tools are insufficient to meet the repair needs, the system prompts the user that additional tools are needed or suggests seeking help from professional repair personnel.

[0101] In one possible embodiment, the repair tool information includes the type and quantity of repair tools. The step of generating a target repair guidance plan based on the repair plan and the repair tool information includes:

[0102] 81. Determine the required repair tool information in the repair plan to obtain first repair tool information, wherein the first repair tool information includes the type and quantity of the first repair tool;

[0103] 82. Compare the types and quantities of the repair tools with the types and quantities of the first repair tools to determine whether the repair tools for the target vehicle meet the tool requirements of the repair plan.

[0104] 83. When the repair tools of the target vehicle meet the tool requirements of the repair plan, acquire voice information for user repair interaction;

[0105] 84. Recognize the voice information to obtain the text information corresponding to the voice information;

[0106] 85. Extract the text information using a preset relation extraction model to obtain keywords related to the relationship between faults and maintenance corresponding to the text information;

[0107] 86. Based on a preset set of maintenance terminology, search for keywords related to the relationship between the fault and maintenance to obtain the first colloquial fault resolution data;

[0108] 87. Extract the operation instructions containing maintenance terminology from the maintenance plan to obtain n operation instructions; n is an integer greater than or equal to 1;

[0109] 88. Based on the aforementioned maintenance terminology set, the n operation instructions are converted into colloquial language to generate second colloquial fault-solving data;

[0110] 89. Determine the target maintenance guidance scheme based on the first and second conversational fault resolution data.

[0111] In generating the target repair guidance plan, the system analyzes the user's technical capabilities based on their operating habits to ensure that the generated plan meets professional requirements while being easy for users to understand and implement. First, the system assesses the user's hands-on ability by reviewing their historical repair records, skill level evaluation, and current environmental conditions. Then, it customizes different repair guidance plans for different user groups (such as novice and experienced users). For example, for users with lower technical skills, the system provides more detailed step-by-step instructions with clear illustrations and voice prompts to facilitate gradual follow-up. For experienced users, the system may provide simpler guidance, emphasizing key steps and precautions, reducing redundant information, and improving efficiency. Furthermore, the system intelligently responds promptly to user feedback. When users encounter difficulties or problems while performing repair tasks, the system can adjust the guidance content in real time, providing additional assistance or alternative solutions, or offering online help within the steps of the guidance plan.

[0112] In one possible embodiment, the n operation instructions are converted into colloquial language based on the maintenance terminology set to generate second colloquial fault-solving data, including:

[0113] 881. Based on the maintenance terminology set, determine the complex technical expression terms in the n operation instructions to obtain n complex technical expression terms;

[0114] 882. The n complex technical terms are converted using spoken language association matching technology to obtain q target spoken language expression data; q is an integer greater than or equal to n;

[0115] 883. Process the q target colloquial expression data to obtain the second colloquial fault resolution data.

[0116] This process involves using a maintenance terminology set to deeply analyze complex technical terms in operating instructions, identifying and extracting them. Complex terms include: abbreviations of proper nouns, shortened versions of operating procedures, and colloquial names for tools—the specifics are not limited here. The key is accurately identifying highly technical and specialized terms, which often hinder user understanding and affect performance in actual operation. Therefore, the system not only needs to extract the terms simply but also assess their difficulty in user comprehension. This ensures that in the subsequent colloquialization stage, these complex terms can be effectively simplified, providing users with a clear foundation during the identification and extraction process and avoiding misunderstandings or confusion caused by the complexity of technical terminology.

[0117] S290. The target maintenance guidance plan is visualized and displayed through the display device.

[0118] During the visualization process, the system constructs corresponding vehicle fault models based on different vehicle models and fault types. These fault models integrate various data, including historical fault records, repair cases, and vehicle design features, aiming to provide users with accurate fault location and operational guidance. On the display device, users will be able to intuitively see the specific location of the fault and the specific operating methods for dealing with it.

[0119] The visual displays will also include detailed repair steps for specific faults, including specific operating instructions and safety precautions for each step. For example, if a fault involves the engine system, the system will provide a detailed process for engine disassembly, component inspection, replacement, and reassembly, with corresponding safety warnings displayed next to each step to ensure users follow best practices. Furthermore, voice prompts and interactive features will enhance user engagement. During repairs, users can interact with the system using simple voice commands to query details of specific steps or obtain additional operating tips. This human-computer interaction design allows users to more flexibly address different repair challenges and improve work efficiency.

[0120] During the demonstration, users can also view historical maintenance records and frequently asked questions (FAQs) related to the fault. This information will further help technicians make judgments and decisions more quickly when faced with similar faults. Through data analysis, the most common fault types and corresponding maintenance strategies can be identified, thereby providing users with experience-based advice.

[0121] As can be seen, the vehicle fault repair guidance method described in this application embodiment includes: obtaining vehicle information of the target vehicle; obtaining diagnostic information of the target vehicle through the diagnostic device, the diagnostic information including target fault location, target fault occurrence time, and target fault code; determining target fault information corresponding to the target fault location and the target fault code according to a preset fault resolution rule base; the preset fault resolution rule base stores a preset correspondence between fault location, fault code, and fault information; determining the fault cause and repair plan according to the target fault information; determining the target fault handling difficulty level of the target vehicle based on the fault cause, the repair plan, the target fault occurrence time, and the vehicle information, the target fault handling difficulty level being used to represent the severity of the vehicle fault; when the target fault handling difficulty level is less than the preset fault handling difficulty level, acquiring first images of repair tools in the target repair tool kit through the camera module to obtain m first images; m is an integer greater than 1; determining the repair tool information of the target vehicle based on the m first images; generating a target repair guidance plan based on the repair plan and the repair tool information; and visually displaying the target repair guidance plan through the display device, thereby improving the efficiency of user fault handling.

[0122] Please see Figure 3 , Figure 3 This is a functional module block diagram of a vehicle fault repair guidance device provided in an embodiment of this application. The vehicle fault repair guidance device 300 includes: an acquisition module 310, a determination module 320, a generation module 330, and a display module 340.

[0123] The acquisition module 310 is used to acquire vehicle information of the target vehicle; acquire diagnostic information of the target vehicle, the diagnostic information including target fault location, target fault occurrence time, and target fault code;

[0124] The determining module 320 is used to determine the target fault location and the target fault code corresponding to the target fault information according to a preset fault resolution rule base; the preset fault resolution rule base stores a preset correspondence between fault locations, fault codes and fault information; determine the fault cause and repair plan according to the target fault information; and determine the target fault handling difficulty level of the target vehicle based on the fault cause, the repair plan, the time of occurrence of the target fault and the vehicle information, wherein the target fault handling difficulty level is used to indicate the severity of the vehicle fault;

[0125] The acquisition module 310 is further configured to, when the target fault handling difficulty level is less than the preset fault handling difficulty level, acquire first images of the repair tools in the target repair tool kit through the camera module, and obtain m first images; m is an integer greater than 1.

[0126] The determining module 320 is further configured to determine the repair tool information of the target vehicle based on the m first images;

[0127] The generation module 330 is used to generate a target repair guidance plan based on the repair plan and the repair tool information;

[0128] The display module 340 is used to visualize the target maintenance guidance scheme.

[0129] In one possible embodiment, the determining module 320, in determining the target fault information including the fault occurrence time period, the target fault information corresponding to the target fault location and the target fault code based on a preset fault resolution rule base, and the fault cause and repair plan based on the target fault information, is specifically used for:

[0130] Obtain the fault records corresponding to the target fault code, resulting in e fault records; e is an integer greater than 1.

[0131] Obtain the fault time of each fault record in the e fault records to get e fault times, and obtain the fault time closest to the current time among the e fault times to get the first fault time;

[0132] The fault occurrence time period is determined based on the first fault time and the target fault occurrence time;

[0133] Determine the first cause of the fault corresponding to the target fault code;

[0134] The cause of the fault is determined by analyzing the fault occurrence time period and the target fault location.

[0135] Determine the cause of the first fault and the corresponding repair plan.

[0136] In one possible embodiment, the determining module 320, regarding the vehicle information including brand, model, and target vehicle runtime, and the determination of the target fault handling difficulty level of the target vehicle based on the fault cause, the repair plan, the target fault occurrence time, and the vehicle information, is further specifically used for:

[0137] Get the current time;

[0138] The duration of the fault of the target vehicle is determined based on the time of occurrence of the target fault and the current time, wherein the duration of the fault is the length of time from the time of occurrence of the target fault to the current time.

[0139] The urgency of the fault handling is determined by evaluating the duration of the target fault and the running time of the target vehicle.

[0140] The complexity of fault handling is determined by evaluating the brand, model, cause of fault, and repair plan.

[0141] The target fault handling difficulty coefficient is obtained by weighting the fault handling urgency and the fault handling complexity.

[0142] The target fault handling difficulty level is determined based on a preset fault handling level threshold and the target fault handling difficulty coefficient.

[0143] In one possible embodiment, the determining module 320, in obtaining the target fault handling difficulty coefficient by weighted calculation based on the fault handling urgency and the fault handling complexity, is further configured to:

[0144] The fault handling difficulty coefficient is obtained by calculating the weight based on the preset first weight factor, second weight factor, first weight calculation formula, fault handling urgency, and fault handling complexity. The first weight calculation formula is: P = a × T + b × E + c, where T is the fault handling urgency, E is the fault handling complexity, a is the first weight factor, b is the second weight factor, and c is the first error factor.

[0145] Obtain the model year of the target vehicle, and determine the usage duration of the target vehicle based on the model year;

[0146] The third weighting factor is determined based on the usage duration;

[0147] The target fault handling difficulty coefficient is obtained by calculating based on the fault handling difficulty coefficient, the third weight factor, and the second weight calculation formula. The second weight calculation formula is: D=d×P+j, where D is the target fault handling difficulty coefficient, d is the third weight factor, and j is the second error factor.

[0148] In one possible embodiment, the acquisition module 310, in determining the repair tool information of the target vehicle based on the m first images, is specifically used for:

[0149] Acquire a target first image, wherein the target first image is any one of the m first images;

[0150] The target first image is identified using image recognition technology to obtain the target repair tool feature data;

[0151] Determine the first tool data corresponding to the first image of the target based on the feature data of the target repair tool;

[0152] Obtain the target standard image set corresponding to the first tool data from the preset standard image library. The preset standard image library stores k standard image sets, and each standard image set corresponds to p standard images of a tool, where k is an integer greater than 1 and p is an integer greater than or equal to k.

[0153] The repair tool information of the target vehicle is determined based on the target standard image set.

[0154] In one possible embodiment, the generation module 330, in generating the target repair guidance plan based on the repair plan and the repair tool information, is specifically used for:

[0155] The required repair tool information in the repair plan is determined to obtain the first repair tool information, which includes the type and quantity of the first repair tool.

[0156] The types and quantities of the repair tools are compared with the types and quantities of the first repair tools to determine whether the repair tools of the target vehicle meet the tool requirements of the repair plan.

[0157] When the repair tools for the target vehicle meet the tool requirements of the repair plan, acquire voice information for user repair interaction;

[0158] The voice information is recognized to obtain the corresponding text information.

[0159] The text information is extracted using a preset relationship extraction model to obtain keywords related to the relationship between faults and maintenance.

[0160] Based on a preset set of maintenance terminology, keywords related to the relationship between the fault and maintenance are queried to obtain the first colloquial fault resolution data.

[0161] Extract the operation instructions containing maintenance terminology from the maintenance plan to obtain n operation instructions; n is an integer greater than or equal to 1.

[0162] Based on the maintenance terminology set, the n operation instructions are converted into colloquial language to generate second colloquial fault resolution data;

[0163] The target maintenance guidance scheme is determined based on the first and second conversational fault resolution data.

[0164] In one possible embodiment, the generation module 330, in converting the n operation instructions into colloquial language based on the maintenance terminology set to generate second colloquial fault-solving data, is further configured to:

[0165] Based on the aforementioned maintenance terminology set, the complex technical terms in the n operation instructions are determined, resulting in n complex technical terms.

[0166] The n complex technical terms are converted using spoken language association matching technology to obtain q target spoken language expression data; q is an integer greater than or equal to n;

[0167] The q target colloquial expression data are processed to obtain the second colloquial fault resolution data.

[0168] It is worth noting that the specific functional implementation of the vehicle fault repair guidance device 300 is described above. Figure 2 The description of the vehicle fault repair guidance method illustrates that, for example, the acquisition module 310 is used to implement the relevant content of S210 and S260, and the display module 340 is used to implement the relevant content of S290. Each unit or module in the vehicle fault repair guidance device 300 can be individually or entirely merged into one or more other units or modules, or some of the units or modules can be further divided into multiple functionally smaller units or modules. This achieves the same operation without affecting the technical effects of the embodiments of this application. The aforementioned units or modules are based on logical function division. In practical applications, the function of one unit (or module) is implemented by multiple units (or modules), or the function of multiple units (or modules) is implemented by one unit (or module).

[0169] As can be seen, the vehicle fault repair guidance device described in this application first acquires the vehicle information and diagnostic information of the target vehicle. The diagnostic information includes the target fault location, the target fault occurrence time, and the target fault code. Based on a preset fault resolution rule base, the target fault information corresponding to the target fault location and target fault code is determined. The preset fault resolution rule base stores a pre-defined correspondence between fault locations, fault codes, and fault information. Based on the target fault information, the fault cause and repair plan are determined. Next, based on the fault cause, repair plan, target fault occurrence time, and vehicle information, the target fault handling difficulty level of the target vehicle is determined. The target fault handling difficulty level indicates the severity of the vehicle fault. When the target fault handling difficulty level is less than the preset fault handling difficulty level, first images of the repair tools in the target repair toolkit are acquired, resulting in m first images, where m is an integer greater than 1. The repair tool information of the target vehicle is determined based on the m first images. Then, based on the repair plan and the repair tool information, a target repair guidance plan is generated. Finally, the target repair guidance plan is visualized. In this way, the vehicle fault repair guidance device can guide users to solve relatively easy faults themselves, thereby improving the efficiency of vehicle fault resolution and saving users' time and effort.

[0170] Please see Figure 4 , Figure 4 This is a structural schematic diagram of a vehicle-mounted device provided in an embodiment of this application, such as... Figure 4 As shown, the vehicle-mounted device 400 may include a processor 410, a memory 420, a communication interface 430, and one or more programs 421. The processor 410, memory 420, and communication interface 430 can be interconnected via a bus and perform communication with each other.

[0171] The processor 410 is mainly used for:

[0172] Obtain vehicle information for the target vehicle;

[0173] The diagnostic equipment is used to obtain diagnostic information of the target vehicle, including the target fault location, the time of the target fault occurrence, and the target fault code.

[0174] The target fault location and the target fault code are determined according to a preset fault resolution rule base; the preset fault resolution rule base stores the preset correspondence between fault locations, fault codes and fault information.

[0175] Determine the cause of the fault and the repair plan based on the target fault information;

[0176] Based on the cause of the fault, the repair plan, the time of occurrence of the target fault, and the vehicle information, the target fault handling difficulty level of the target vehicle is determined, and the target fault handling difficulty level is used to indicate the severity of the vehicle fault;

[0177] When the target fault handling difficulty level is less than the preset fault handling difficulty level, the camera module acquires the first image of the repair tools in the target repair tool kit, resulting in m first images; m is an integer greater than 1.

[0178] The repair tool information of the target vehicle is determined based on the m first images;

[0179] Based on the repair plan and the repair tool information, a target repair guidance plan is generated;

[0180] The target repair guidance plan is visualized using the display device.

[0181] The one or more programs 421 are stored in the memory 420 and configured to be executed by the processor 410. The one or more programs include instructions for performing any step in the above method embodiments.

[0182] Among them, the vehicle-mounted device 400 may include smartphones (such as Android phones, iOS phones, Windows Phones, etc.), tablet computers, PDAs, dashcams, vehicle-mounted electronic devices, servers, laptops, mobile internet electronic devices (MIDs) or wearable electronic devices (such as smartwatches, Bluetooth headsets), etc. The above are just examples and not an exhaustive list, including but not limited to the above-mentioned electronic devices.

[0183] The processor can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, cells, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication unit can be a communication interface, a transceiver, a transceiver circuit, etc., and the storage unit can be a memory.

[0184] The memory can be volatile or non-volatile, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0185] This application also provides a computer-readable storage medium storing a computer program for electronic data interchange, the computer program causing a computer to perform some or all of the steps of any of the methods described in the above method embodiments, the computer including an in-vehicle device.

[0186] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments. The computer program product may be a software installation package, and the computer may include an in-vehicle device.

[0187] It should be noted that, for the sake of simplicity, the above embodiments are all described as a series of actions. Those skilled in the art should understand that this application is not limited to the described order of actions, as some steps in the embodiments of this application can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions, steps, modules, or units involved are not necessarily essential to the embodiments of this application.

[0188] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0189] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0190] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, portable hard disk, read-only optical disk (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a terminal device or management device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or management device.

[0191] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0192] The modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on a processor integrated within the chip module. The remaining modules / units (if any) can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal equipment, each of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules / units can be implemented using a software program that runs on a processor integrated within the terminal equipment, while the remaining modules / units (if any) can be implemented using hardware methods such as circuits.

[0193] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A method of vehicle trouble repair guidance, characterized by, The method is applied to a vehicle-mounted device, and the vehicle-mounted device comprises a camera module, a diagnostic device and a display device. Vehicle information of a target vehicle is acquired. Diagnostic information of the target vehicle is acquired by the diagnostic device, and the diagnostic information comprises a target fault position, a target fault occurrence time and a target fault code. Target fault information corresponding to the target fault position and the target fault code is determined according to a preset fault resolution rule base, and the preset fault resolution rule base pre-stores a preset corresponding relationship between a fault position, a fault code and fault information. A fault cause and a repair scheme are determined according to the target fault information. A target fault handling difficulty level of the target vehicle is determined based on the fault cause, the repair scheme, the target fault occurrence time and the vehicle information, and the target fault handling difficulty level is used to represent the severity of the vehicle fault. When the target fault handling difficulty level is less than a preset fault handling difficulty level, a first image of a repair tool in a target repair tool kit is acquired by the camera module to obtain m first images, and m is an integer greater than 1. Repair tool information of the target vehicle is determined according to the m first images. A target repair guidance scheme is generated according to the repair scheme and the repair tool information. The target repair guidance scheme is visually displayed by the display device. The repair tool information comprises the type and quantity of the repair tool, and the target repair guidance scheme is generated according to the repair scheme and the repair tool information, which comprises: Required repair tool information in the repair scheme is determined to obtain first repair tool information, and the first repair tool information comprises the type and quantity of the first repair tool. The type and quantity of the repair tool are compared with the type and quantity of the first repair tool to determine whether the repair tool of the target vehicle meets the tool requirement of the repair scheme. When the repair tool of the target vehicle meets the tool requirement of the repair scheme, voice information of user repair interaction is acquired. The voice information is recognized to obtain text information corresponding to the voice information. The text information is extracted by a preset relation extraction model to obtain keywords between the fault and the repair relation corresponding to the text information. The keywords between the fault and the repair relation are queried based on a preset repair professional term set to obtain first colloquial fault resolution data. Operation instructions containing repair professional terms in the repair scheme are extracted to obtain n operation instructions, and n is an integer greater than or equal to 1. The n operation instructions are converted into colloquial language according to the repair professional term set to generate second colloquial fault resolution data. The target repair guidance scheme is determined according to the first colloquial fault resolution data and the second colloquial fault resolution data.

2. The method of claim 1, wherein, The target fault information comprises a fault occurrence time period, and the target fault information corresponding to the target fault position and the target fault code is determined according to the preset fault resolution rule base. According to the target fault information, a fault cause and a maintenance scheme are determined, comprising: Obtaining the fault records corresponding to the target fault code, obtaining e fault records; e is an integer greater than 1; Obtaining the fault time of each fault record in the e fault records, obtaining e fault times, obtaining the first fault time of the e fault times closest to the current time; According to the first fault time and the target fault occurrence time, the fault occurrence time period is determined; Determine the first fault cause corresponding to the target fault code; According to the fault occurrence time period and the target fault position, the fault cause is obtained; Determine the first fault cause, the maintenance scheme corresponding to the fault cause.

3. The method of claim 1, wherein, The vehicle information includes brand, model, target vehicle running time, and the target vehicle target fault processing difficulty level is determined based on the fault cause, the maintenance scheme, the target fault occurrence time and the vehicle information, comprising: Obtaining the current time; According to the target fault occurrence time and the current time, the fault duration of the target vehicle is determined, and the fault duration is the time length of the target vehicle from the target fault occurrence time to the current time; According to the target fault duration, the target vehicle running time is evaluated, and the fault processing urgency is obtained; According to the brand, the model, the fault cause and the maintenance scheme, the fault processing complexity is evaluated; Based on the fault processing urgency and the fault processing complexity, the target fault processing difficulty coefficient is calculated by weighting; According to the preset fault processing level threshold and the target fault processing difficulty coefficient, the target fault processing difficulty level is determined.

4. The method of claim 3, wherein, Based on the fault processing urgency and the fault processing complexity, the target fault processing difficulty coefficient is calculated by weighting, comprising: The weight calculation is performed based on the preset first weight factor, second weight factor, first weight calculation formula, fault processing urgency and fault processing complexity to obtain a fault processing difficulty coefficient, and the first weight calculation formula is: wherein, the fault processing urgency is denoted as, the fault processing complexity is denoted as, the first weight factor is denoted as, b the second weight factor is denoted as, c and the first error factor is denoted as. Obtaining the year of the target vehicle, and determining the use time of the target vehicle according to the year of the target vehicle; According to the use time, a third weight factor is determined; The target fault handling difficulty coefficient is calculated based on the fault handling difficulty coefficient, the third weight factor, and a second weight calculation formula, where the second weight calculation formula is: wherein D is the target fault handling difficulty coefficient, d is the third weight factor, j is a second error factor.

5. The method of claim 1, wherein, According to the m first images, the maintenance tool information of the target vehicle is determined, comprising: Obtaining a target first image, the target first image is any first image in the m first images; The target first image is identified by image recognition technology, and target maintenance tool feature data is obtained; According to the target maintenance tool feature data, the first tool data corresponding to the target first image is determined; From the preset standard image library, a target standard image set corresponding to the first tool data is obtained, the preset standard image library stores k standard image sets, each standard image set corresponds to p standard images of a tool, k is an integer greater than 1, p is an integer greater than or equal to k; Based on the target standard image set, the maintenance tool information of the target vehicle is determined.

6. The method of claim 1, wherein, According to the maintenance professional term set, the n operation instructions are converted into colloquial language, and the second colloquial fault solving data is generated, comprising: determine complex technical expression terms in the n operation instructions based on the repair professional term set, to obtain n complex technical expression terms; convert the n complex technical expression terms through a spoken language association matching technology, to obtain q target colloquial expression data; q is an integer greater than or equal to n; process the q target colloquial expression data, to obtain the second colloquial fault resolution data.

7. A vehicle trouble repair guidance device characterized by comprising: The device is applied to a vehicle-mounted equipment, and the device comprises an acquisition module, a determination module, a generation module, and a display module, wherein: The acquisition module is configured to acquire vehicle information of a target vehicle; and acquire diagnosis information of the target vehicle, the diagnosis information comprising a target fault position, a target fault occurrence time, and a target fault code. The determination module is configured to determine target fault information corresponding to the target fault position and the target fault code according to a preset fault resolution rule library; the preset fault resolution rule library pre-stores a preset correspondence relationship between fault positions, fault codes, and fault information; determine a fault cause and a repair scheme according to the target fault information; and determine a target fault handling difficulty level of the target vehicle based on the fault cause, the repair scheme, the target fault occurrence time, and the vehicle information, the target fault handling difficulty level being used to represent a severity of a vehicle fault. The acquisition module is further configured to, when the target fault handling difficulty level is less than a preset fault handling difficulty level, acquire first images of repair tools in a target repair tool kit through a camera module, to obtain m first images; m is an integer greater than 1. The determination module is further configured to determine repair tool information of the target vehicle according to the m first images. The generation module is configured to generate a target repair guidance scheme according to the repair scheme and the repair tool information. The display module is configured to visually display the target repair guidance scheme. The repair tool information comprises types of repair tools and quantities of repair tools, and the generation module generates the target repair guidance scheme according to the repair scheme and the repair tool information, which comprises: determining required repair tool information in the repair scheme, to obtain first repair tool information, the first repair tool information comprising types of first repair tools and quantities of the first repair tools; comparing the types of repair tools, the quantities of repair tools, the types of first repair tools, and the quantities of first repair tools, to determine whether repair tools of the target vehicle meet tool requirements of the repair scheme; when the repair tools of the target vehicle meet the tool requirements of the repair scheme, acquiring voice information of user repair interaction; recognizing the voice information, to obtain text information corresponding to the voice information; extracting the text information through a preset relation extraction model, to obtain keywords between faults and repair relations corresponding to the text information; querying the keywords between the faults and the repair relations based on a preset repair professional term set, to obtain first colloquial fault resolution data; and extracting operation instructions containing maintenance professional terms in the maintenance solution, to obtain n operation instructions; n is an integer greater than or equal to 1; performing oralization conversion on the n operation instructions according to the maintenance professional term set, to generate second oralized fault resolution data; determining the target maintenance guidance solution according to the first oralized fault resolution data and the second oralized fault resolution data.

8. An in-vehicle device characterized by comprising: The vehicle-mounted device comprises a processor, a memory, the memory is used to store one or more programs and is configured to be executed by the processor, and the program comprises instructions for executing steps in the method of any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, the computer program comprises program instructions, and the program instructions make the processor execute the method of any one of claims 1-6 when executed by the processor.

Images