Vehicle diagnosis method, vehicle diagnosis equipment, vehicle diagnosis system and storage medium

Abstract

The invention relates to the technical field of vehicles, and discloses a vehicle diagnosis method, vehicle diagnosis equipment, a vehicle diagnosis system and a storage medium, and the method comprises the steps: obtaining a to-be-executed diagnosis function instruction of a to-be-detected vehicle; according to a stored first corresponding relation, all execution paths of a diagnosis function instruction to be executed in the vehicle diagnosis equipment are determined, and the first corresponding relation is the corresponding relation between the diagnosis function instruction and the execution paths; acquiring vehicle configuration information of a to-be-detected vehicle; according to a stored second corresponding relation, a target execution path matched with the vehicle configuration information of the to-be-detected vehicle is determined from all the execution paths, and the second corresponding relation is the corresponding relation between the execution paths and the vehicle configuration information; and executing a diagnosis function corresponding to the target execution path on the to-be-detected vehicle. Through the above mode, the vehicle diagnosis efficiency is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle technology, and specifically to a vehicle diagnostic method, a vehicle diagnostic device, a vehicle diagnostic system, and a storage medium. Background Art

[0002] With the continuous development of automotive electronic technology, Electronic Control Unit (ECU) has been widely used in modern automobiles. At present, when a car breaks down, maintenance technicians often need to use automotive diagnostic equipment to diagnose the ECU in the car. However, before using the automotive diagnostic equipment to diagnose the ECU, it is necessary to first determine the ECU to be tested from all the ECUs listed by the diagnostic equipment, then select the diagnostic function to be executed from the diagnostic functions supported by the ECU to be tested, and finally execute the selected diagnostic function on the vehicle to be tested, resulting in low diagnostic efficiency. Summary of the invention

[0003] In view of the above problems, the embodiments of the present application provide a vehicle diagnostic method, a vehicle diagnostic device, a vehicle diagnostic system and a storage medium, which are used to solve the problem of low efficiency in vehicle diagnosis in the prior art.

[0004] According to one aspect of an embodiment of the present application, a vehicle diagnosis method is provided, the method comprising: a vehicle diagnosis device obtains a diagnostic function instruction to be executed of a vehicle to be detected; the vehicle diagnosis device determines all execution paths of the diagnostic function instruction to be executed in the vehicle diagnosis device according to a stored first correspondence, wherein the first correspondence is a correspondence between a diagnostic function instruction and an execution path; the vehicle diagnosis device obtains vehicle configuration information of the vehicle to be detected; the vehicle diagnosis device determines a target execution path that matches the vehicle configuration information of the vehicle to be detected from all execution paths according to a stored second correspondence, wherein the second correspondence is a correspondence between an execution path and vehicle configuration information; the vehicle diagnosis device executes a diagnostic function corresponding to the target execution path on the vehicle to be detected. .

[0005] In an optional manner, the vehicle diagnostic device performs a diagnostic function corresponding to the target execution path on the vehicle to be detected, including: if the vehicle diagnostic device determines that there are multiple target execution paths, then the diagnostic function corresponding to each target execution path is performed on the vehicle to be detected in sequence.

[0006] In an optional manner, the vehicle diagnostic device performs a diagnostic function corresponding to the target execution path on the vehicle to be detected, including: if the vehicle diagnostic device determines that there are multiple target execution paths, then determines and outputs multiple automotive electronic control units ECU corresponding to the multiple target execution paths respectively according to a stored third correspondence relationship, wherein the third correspondence relationship is a correspondence relationship between an execution path and an ECU; and the vehicle diagnostic device responds to an operation of selecting a target ECU from the multiple ECUs, and performs a diagnostic function corresponding to the target ECU on the vehicle to be detected.

[0007] In an optional manner, before the vehicle diagnostic device obtains the diagnostic function instruction to be executed of the vehicle to be detected, the method further includes: the vehicle diagnostic device obtains a first voice instruction; the vehicle diagnostic device performs voice recognition on the first voice instruction to obtain first text information; the vehicle diagnostic device parses the first text information to obtain the diagnostic function instruction to be executed of the vehicle to be detected; or, before the vehicle diagnostic device obtains the diagnostic function instruction to be executed of the vehicle to be detected, the method further includes: the vehicle diagnostic device obtains the first voice instruction and transmits the first voice instruction to a server, wherein the vehicle diagnostic device is communicatively connected to the server; the server performs voice recognition on the first voice instruction to obtain first text information, parses the first text information to obtain the diagnostic function instruction to be executed of the vehicle to be detected, and transmits the diagnostic function instruction to be executed of the vehicle to be detected to the vehicle diagnostic device.

[0008] In an optional manner, the first text information is parsed to obtain the diagnostic function instructions to be executed of the vehicle to be detected, including: determining the target intention entity corresponding to the first text information; determining the target specification entity in a vector database that matches the target intention entity, wherein the vector database includes a fourth correspondence between the specification entity and the diagnostic function instructions; and determining the diagnostic function instructions to be executed of the vehicle to be detected corresponding to the first text information based on the target specification entity and the fourth correspondence.

[0009] In an optional manner, before determining the target intent entity corresponding to the first text information, the method also includes: determining the target intent type corresponding to the first text information; the vector database is a vector database of a type corresponding to the target intent type among a plurality of pre-configured type vector databases.

[0010] In an optional manner, the standard entity is determined by the following steps: determining the professional names, popular names and at least one of the corresponding vehicle abnormal symptoms of the diagnostic functions of multiple vehicle brands; determining the standard entity in the vector database based on the professional names, the popular names and at least one of the corresponding vehicle abnormal symptoms.

[0011] In an optional manner, the determining the target standard entity in the vector database that matches the target intent entity includes: respectively determining all matching degrees between the target intent entity and all standard entities; and determining the target standard entity based on the all matching degrees.

[0012] In an optional manner, the target standard entity is determined based on all the matching degrees, including: if the maximum matching degree among all the matching degrees is less than a preset threshold, the first voice instruction is determined to be wrong, the step of determining the diagnostic function instruction corresponding to the first text information based on the target standard entity and the fourth correspondence is not performed, and the information that the first voice instruction is wrong is output through the vehicle diagnostic equipment; if the maximum n matching degrees among all the matching degrees are greater than or equal to the preset threshold, the standard entity corresponding to the maximum n matching degrees is determined to be the target standard entity, wherein n is a positive integer.

[0013] In an optional manner, before the vehicle diagnostic device determines the entire execution path of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first correspondence, the method further includes: the vehicle diagnostic device obtains the state of the diagnostic thread of the vehicle diagnostic device at the current moment; if the state indicates that the diagnostic thread does not perform the diagnostic function on the vehicle to be detected at the current moment, the vehicle diagnostic device executes the step of determining the entire execution path of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first correspondence.

[0014] In an optional manner, the method further includes: the vehicle diagnostic device receives a second voice command; the vehicle diagnostic device performs voice recognition on the second voice command to obtain second text information; the vehicle diagnostic device parses the second text information to obtain a diagnostic data query instruction; the vehicle diagnostic device queries the diagnostic data stored in the vehicle diagnostic device or a server connected to the vehicle diagnostic device according to the diagnostic data query instruction, and outputs the queried diagnostic data; or, the method further includes: the vehicle diagnostic device receives the second voice command and transmits the second voice command to a server, wherein the vehicle diagnostic device is connected to the server; the server performs voice recognition on the second voice command to obtain second text information, parses the second text information to obtain a diagnostic data query instruction, and transmits the diagnostic data query instruction to the vehicle diagnostic device; the vehicle diagnostic device queries the diagnostic data stored in the vehicle diagnostic device or the server according to the diagnostic data query instruction, and outputs the queried diagnostic data.

[0015] In an optional manner, the method further includes: the vehicle diagnostic device receives a third voice instruction; the vehicle diagnostic device performs voice recognition on the third voice instruction to obtain third text information; the vehicle diagnostic device parses the third text information to obtain an operation target button instruction; the vehicle diagnostic device operates the target button according to the operation target button instruction; or, the method further includes: the vehicle diagnostic device receives the third voice instruction, and transmits the third voice instruction to a server, wherein the vehicle diagnostic device is communicatively connected to the server; the server performs voice recognition on the third voice instruction to obtain third text information, parses the third text information to obtain an operation target button instruction, and transmits the operation target button instruction to the vehicle diagnostic device; the vehicle diagnostic device operates the target button according to the operation target button instruction.

[0016] According to another aspect of an embodiment of the present application, a vehicle diagnostic device is provided, including a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to implement the vehicle diagnostic method as described above.

[0017] According to another aspect of an embodiment of the present application, a vehicle diagnostic system is provided, the system comprising a server and a vehicle diagnostic device, the vehicle diagnostic device being communicatively connected to the server; the vehicle diagnostic device being used to obtain a first voice instruction; uploading the first voice instruction to the server to obtain a diagnostic function instruction to be executed of a vehicle to be detected returned by the server; determining all execution paths of the diagnostic function instruction to be executed in the vehicle diagnostic device according to a stored first correspondence, wherein the first correspondence is a correspondence between diagnostic function instructions and execution paths; obtaining vehicle configuration information of the vehicle to be detected; determining a target execution path that matches the vehicle configuration information of the vehicle to be detected from all execution paths according to a stored second correspondence, wherein the second correspondence is a correspondence between execution paths and vehicle configuration information; executing a diagnostic function corresponding to the target execution path on the vehicle to be detected; the server being used to perform voice recognition on the first voice instruction to obtain first text information; parsing the first text information to obtain the diagnostic function instruction.

[0018] In an optional manner, the server is used to parse the first text information to obtain the diagnostic function instructions to be executed of the vehicle to be detected, and is specifically used to: determine the target intention entity corresponding to the first text information; determine the target specification entity in the vector database that matches the target intention entity, wherein the vector database includes a fourth correspondence between the specification entity and the diagnostic function instructions; and determine the diagnostic function instructions to be executed of the vehicle to be detected corresponding to the first text information based on the target specification entity and the fourth correspondence.

[0019] In an optional manner, before determining the target intent entity corresponding to the first text information, the server is also used to: determine the target intent type corresponding to the first text information; the vector database is a vector database of a type corresponding to the target intent type among a plurality of pre-configured type vector databases.

[0020] In an optional manner, the vehicle diagnostic device is further used to receive a second voice command and transmit the second voice command to the server; the server is further used to receive the second voice command, perform voice recognition on the second voice command to obtain second text information, parse the second text information to obtain a diagnostic data query instruction, and transmit the diagnostic data query instruction to the vehicle diagnostic device; the vehicle diagnostic device is further used to query the diagnostic data stored in the vehicle diagnostic device or the server according to the diagnostic data query instruction, and output the queried diagnostic data.

[0021] In an optional manner, the vehicle diagnostic device is also used to receive a third voice instruction and transmit the third voice instruction to the server; the server is also used to receive the third voice instruction, perform voice recognition on the third voice instruction to obtain third text information, parse the third text information to obtain an operation target button instruction, and transmit the operation target button instruction to the vehicle diagnostic device; the vehicle diagnostic device is also used to receive the operation target button instruction and operate the target button according to the operation target button instruction.

[0022] According to another aspect of the embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the vehicle diagnosis method as described above is implemented.

[0023] In the embodiment of the present application, since the vehicle diagnostic device stores a first correspondence (i.e., the correspondence between the diagnostic function instruction and the execution path) and a second correspondence (i.e., the correspondence between the execution path and the vehicle configuration information), after receiving the diagnostic function instruction to be executed for the detection vehicle sent by the user, the vehicle diagnostic device can determine all execution paths corresponding to the diagnostic function instruction to be executed according to the first correspondence, and then determine the target execution path that matches the vehicle configuration information of the detection vehicle in all execution paths according to the second correspondence, so as to execute the diagnostic function to be executed on the detection vehicle and complete the diagnosis of the detection vehicle. Since the user does not need to step by step execute the operations corresponding to the existing diagnostic logic, the user only needs to provide the diagnostic function instruction to be executed and the vehicle configuration information to complete the diagnosis of the detection vehicle, which greatly simplifies the process of diagnosing the vehicle, thereby improving the diagnostic efficiency.

[0024] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present application. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:

[0026] Figure 1 A schematic diagram showing the diagnostic logic of a vehicle diagnostic device in the prior art is shown;

[0027] Figure 2 A schematic diagram of a vehicle diagnostic method according to an embodiment of the present application is shown;

[0028] Figure 3A schematic diagram showing the diagnostic logic of a vehicle diagnostic device provided by an embodiment of the present application is shown;

[0029] Figure 4 A schematic diagram showing a flow chart of a vehicle diagnostic method provided by another embodiment of the present application is shown;

[0030] Figure 5 A schematic flow chart of a vehicle diagnostic method provided by another embodiment of the present application is shown;

[0031] Figure 6 A schematic diagram of the structure of a vehicle diagnostic device provided in an embodiment of the present application is shown;

[0032] Figure 7 A schematic diagram of a vehicle diagnostic system provided by an embodiment of the present application is shown;

[0033] Figure 8 A flow chart of a vehicle diagnostic method provided in yet another embodiment of the present application is shown. DETAILED DESCRIPTION

[0034] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein.

[0035] Figure 1 FIG. 1 is a schematic diagram showing the diagnostic logic of a vehicle diagnostic device in the prior art. Figure 1As shown, when the current user uses the vehicle diagnostic device to diagnose the vehicle, the diagnostic device will first display the vehicle brands supported by the vehicle diagnostic device for the user to choose. After the user selects the vehicle brand, for example, selects vehicle brand A, the vehicle diagnostic device then displays all the models under the vehicle brand A for the user to choose, wherein the figure only takes two models under vehicle brand A as an example for introduction. After the user selects the model, for example, selects model 1, the vehicle diagnostic device then displays all the years to which the model belongs for the user to choose. After the user selects the year, for example, selects year 2, the vehicle diagnostic device then displays all the engine types under the year for the user to choose. After the user selects the engine type, for example, selects engine type 5, the vehicle diagnostic device then displays all the ECUs under engine type 5 for the user to choose. After the user selects an ECU, for example, selects ECU3, the vehicle diagnostic device then displays the diagnostic functions that can be supported by the ECU for the user to choose. The user selects the diagnostic function to be executed, and finally executes the diagnostic function selected by the user on the vehicle to be detected. The diagnostic functions may include but are not limited to: reading fault codes, reading data streams, and component testing. The above operation process is rather complicated, resulting in low diagnostic efficiency, and requires the user to have a deep understanding of the vehicle to be tested and each ECU under the vehicle. If the user only knows the name of the diagnostic function but cannot identify the ECU, it is impossible to quickly perform the diagnostic function on the vehicle to be tested.

[0036] Based on this, in order to improve the diagnostic efficiency, the present application proposes a vehicle diagnostic method, which is applied to a vehicle diagnostic device. The method receives the name of the diagnostic function to be executed and the vehicle configuration information of the vehicle to be detected, such as the vehicle brand, model, year and engine type, provided by the user, and then determines all execution paths corresponding to the diagnostic function to be executed, wherein the execution path is the path for locating and executing the diagnostic function, and then determines the target execution path corresponding to the vehicle configuration information of the vehicle to be detected from all the execution paths, and finally executes the diagnostic function corresponding to the target execution path on the vehicle to be detected. Since the user does not need to execute layer by layer, Figure 1 The selection operation corresponding to the diagnostic logic is improved, thereby improving the diagnostic efficiency, and the user can perform the diagnostic function on the vehicle to be tested even if he only knows the diagnostic function and the ECU to be tested is unknown.

[0037] Figure 2A flow chart of a vehicle diagnostic method provided in an embodiment of the present application is shown, and the method is executed by a vehicle diagnostic device, which may be a device including one or more processors, and the processor may be a central processing unit CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement an embodiment of the present invention, which is not limited here. The one or more processors included in the vehicle diagnostic device may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs, which is not limited here. Figure 2 As shown, the method comprises the following steps:

[0038] S110: Obtaining a diagnostic function instruction to be executed of the vehicle to be detected.

[0039] The diagnostic function instruction to be executed may include a coding ID, or may include a name of a diagnostic function to be executed (for example, reading a fault code), as long as the diagnostic program can be determined through the diagnostic function instruction, wherein the diagnostic program is a program for executing a diagnostic function on a vehicle. If the diagnostic function instruction includes a coding ID, a correspondence between the coding ID and the diagnostic program is pre-stored, and the corresponding diagnostic program can be determined according to the correspondence; if the diagnostic function instruction includes a name of a diagnostic function to be executed, the corresponding diagnostic program can be directly determined according to the name of the diagnostic function. The vehicle diagnostic device can receive the diagnostic function instruction to be executed in the form of voice or text, that is, the user can input the diagnostic function instruction to be executed on the vehicle diagnostic device in the form of voice or text as needed, or send the diagnostic function instruction to be executed to the vehicle diagnostic device through other electronic devices.

[0040] S120: Determine all execution paths of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first corresponding relationship.

[0041] Among them, the first correspondence is the correspondence between the diagnostic function instruction and the execution path, and the first correspondence is pre-stored in the vehicle diagnostic device. The execution path is the path for locating and executing the diagnostic function, and different diagnostic functions correspond to different execution paths. It can be understood that the same diagnostic function can usually be executed on different ECUs. For example, for the diagnostic function of reading fault codes, it can be executed on ECUs such as engine ECU, air conditioning ECU, fuel system ECU, etc. Therefore, if the same diagnostic function can be executed on different ECUs, then the same diagnostic function will correspond to multiple different execution paths, and different execution paths correspond to different ECUs.

[0042] Figure 3FIG. 1 is a schematic diagram showing the diagnostic logic of a vehicle diagnostic device provided by an embodiment of the present application. Figure 3 As shown, the vehicle brand to be detected is vehicle brand B. After the vehicle diagnostic equipment obtains the diagnostic function instructions to be executed of the vehicle to be detected, all execution paths corresponding to the diagnostic functions to be executed can be determined. For example, if the diagnostic function to be executed is diagnostic function 1, the corresponding execution path includes execution path 1.

[0043] S130: Obtain vehicle configuration information of the vehicle to be detected.

[0044] The vehicle configuration information includes information such as the vehicle brand, model, year, and engine type. Vehicles with different configuration information may include different ECUs, and the diagnostic functions supported by different ECUs are also different. Figure 3 As shown, for two vehicles with the brand of brand B, the year of the vehicle is year 3, the engine type is type 2, and the ECU is the same (both are ECU3) but the vehicle model is different, then the diagnostic functions that can be executed by the same ECU3 are different. Therefore, in the embodiment of the present application, the vehicle configuration information of the vehicle to be detected is obtained so that which ECU of the vehicle to be detected can be accurately and quickly determined later on to execute the diagnostic function to be executed.

[0045] S140: Determine, from all execution paths, a target execution path that matches the vehicle configuration information of the vehicle to be detected according to the stored second corresponding relationship.

[0046] Among them, the second corresponding relationship is the corresponding relationship between the execution path and the vehicle configuration information, and the second corresponding relationship is pre-stored in the vehicle diagnostic device. Since all the execution paths obtained in S120 may include execution paths corresponding to the configuration information that does not belong to the vehicle to be detected, therefore, in this step, it is necessary to determine the target execution path corresponding to the configuration information of the vehicle to be detected from all the execution paths according to the configuration information of the vehicle to be detected. For example, the vehicle detection equipment can execute the diagnostic function to be executed on ECU1 and ECU2, but the vehicle to be detected only includes ECU1 but not ECU2, then all the execution paths determined by S120 include the execution path corresponding to ECU1 and the execution path corresponding to ECU2, and the target execution path determined according to the second corresponding relationship in this step is the execution path corresponding to ECU1.

[0047] S150: Execute a diagnostic function corresponding to the target execution path on the vehicle to be detected.

[0048] Among them, in this step, by executing the diagnostic function corresponding to the target execution path on the vehicle to be detected, the diagnosis of the vehicle to be detected can be achieved.

[0049] In the embodiment of the present application, since the vehicle diagnostic device stores a first correspondence (i.e., the correspondence between the diagnostic function instruction and the execution path) and a second correspondence (i.e., the correspondence between the execution path and the vehicle configuration information), after receiving the diagnostic function instruction to be executed for the detection vehicle sent by the user, the vehicle diagnostic device can determine all the execution paths corresponding to the diagnostic function instruction to be executed according to the first correspondence, and then determine the target execution path that matches the vehicle configuration information of the detection vehicle among all the execution paths according to the second correspondence, and thus execute the diagnostic function to be executed on the detection vehicle, and complete the diagnosis of the detection vehicle. Since the user does not need to execute step by step, the vehicle diagnostic device can complete the diagnosis of the detection vehicle. Figure 1 For operations corresponding to the diagnostic logic, users only need to provide the diagnostic function instructions to be executed and the vehicle configuration information to complete the diagnosis of the vehicle to be tested, which greatly simplifies the process of vehicle diagnosis and thus improves the diagnostic efficiency.

[0050] In order to further improve the diagnostic efficiency, in the embodiment of the present application, S150 includes: if there are multiple target execution paths, the diagnostic functions corresponding to each target execution path are executed in sequence for the vehicle to be detected. Among them, for the vehicle to be detected, if there are multiple diagnostic functions supported by different ECUs, all of which include the diagnostic function to be executed, then multiple target execution paths can be determined through S140. In some cases, it is necessary to execute diagnostic functions corresponding to multiple target execution paths for the vehicle to be detected. For example, when maintaining the vehicle, it is usually necessary to read the mileage data of the engine and the mileage data of the dashboard to formulate a vehicle maintenance plan. At this time, if the diagnostic function to be executed is to read the mileage data, the mileage of the engine and the mileage of the dashboard are read in this step. If the user is required to switch back and forth on the vehicle diagnostic equipment to search for and execute the diagnostic function of reading mileage data on the engine and dashboard, it will take a long time and the diagnostic efficiency will be low.

[0051] Therefore, in the embodiment of the present application, by sequentially executing the diagnostic functions corresponding to each target execution path on the vehicle to be detected, the diagnosis of the vehicle to be detected is realized, and the user does not need to operate the vehicle diagnostic equipment to switch back and forth between multiple ECUs, thereby further improving the diagnostic efficiency. In addition, in the embodiment of the present application, when the user only knows the name of the diagnostic function to be executed, but does not know which ECU needs to execute the diagnostic function to be executed, the diagnostic function can also be executed on the vehicle to be detected in the above manner.

[0052] In order to reduce the power consumption of the vehicle diagnostic equipment, in the embodiment of the present application, S150 includes the following steps a01 to a02.

[0053] Step a01: If there are multiple target execution paths, multiple ECUs corresponding to the multiple target execution paths are determined and output according to the stored third corresponding relationship, wherein the third corresponding relationship is a corresponding relationship between the execution path and the ECU.

[0054] The third corresponding relationship is pre-stored in the vehicle diagnostic device. The vehicle diagnostic device can display the ECUs corresponding to the multiple target execution paths to the user through a display screen, or output the ECUs corresponding to the multiple target execution paths to the user through voice broadcast.

[0055] Step a02: In response to an operation of selecting a target ECU from a plurality of ECUs, a diagnostic function corresponding to the target ECU is executed on the vehicle to be detected.

[0056] Among them, after the user selects one or more target ECUs from the ECUs corresponding to multiple target execution paths output by the vehicle diagnostic device, the vehicle diagnostic device executes the diagnostic function corresponding to the target ECU on the vehicle to be detected.

[0057] In the embodiment of the present application, the power consumption of the vehicle diagnostic device is reduced by executing the diagnostic function to be executed only on the target ECU selected by the user, and not executing the diagnostic function on other irrelevant ECUs.

[0058] Figure 4 FIG. 2 is a flow chart of a vehicle diagnostic method provided by another embodiment of the present application, wherein the method is executed by a vehicle diagnostic device. Figure 4 As shown, the method comprises the following steps:

[0059] S110: Obtaining a diagnostic function instruction to be executed of the vehicle to be detected.

[0060] The principle and implementation of this step can be referred to Figure 2 The principle and implementation of S110 in the provided embodiment.

[0061] S111: Obtain the status of the diagnosis thread of the vehicle diagnosis device at the current moment.

[0062] In the embodiment of the present application, S150 is executed by the diagnostic thread of the diagnostic process of the vehicle diagnostic device. The diagnostic thread sets its state to the working state when executing the diagnostic function on the vehicle to be detected, and restores its state to the idle state after the diagnostic function is completed.

[0063] S112: Determine whether the state indicates that the current diagnostic thread is executing a diagnostic function on the vehicle to be detected. If so, go to S113; if not, go to S120.

[0064] In this step, by judging the state of the current diagnostic thread, it can be determined whether the current diagnostic thread is performing a diagnostic function on the vehicle to be detected. If the current diagnostic thread state is a working state, it indicates that the current diagnostic thread is performing a diagnostic function on the vehicle to be detected.

[0065] S113: Outputting prompt information, wherein the prompt information is used to prompt that a new diagnostic function cannot be executed at the current moment.

[0066] In the process of executing the diagnostic function on the vehicle, if the current diagnostic function is terminated, it will have an adverse effect on the vehicle. Therefore, if the diagnostic function is currently being executed on the vehicle, a prompt message is output to prompt the user that a new diagnostic function cannot be executed at the current moment.

[0067] S120: Determine all execution paths of the diagnostic function to be executed in the vehicle diagnostic device according to the stored first corresponding relationship.

[0068] S130: Obtain vehicle configuration information of the vehicle to be detected.

[0069] S140: Determine, from all execution paths, a target execution path that matches the vehicle configuration information of the vehicle to be detected according to the stored second corresponding relationship.

[0070] S150: Execute a diagnostic function corresponding to the target execution path on the vehicle to be detected.

[0071] Among them, S120~S150 can refer to Figure 2 An embodiment is provided.

[0072] It is understandable that it usually takes a certain amount of time to perform a diagnostic function on a vehicle. Therefore, in the embodiment of the present application, the vehicle diagnostic device receives a first diagnostic function instruction to be executed at a historical moment, requiring the first diagnostic function to be executed on the vehicle to be detected. If a second diagnostic function instruction to be executed is received at the current moment, requiring the second diagnostic function to be executed on the vehicle to be detected, it is first determined whether the diagnostic function is being executed on the vehicle to be detected at the current moment. If the first diagnostic function is being executed on the vehicle to be detected at the current moment, a prompt message is output to prompt the user that the second diagnostic function cannot be executed on the vehicle to be detected at the current moment, thereby avoiding the situation where the vehicle diagnostic device is suspended from executing the first diagnostic function on the vehicle to be detected during the process of executing the first diagnostic function on the vehicle to be detected, thereby avoiding adverse effects on the vehicle to be detected.

[0073] Figure 5 FIG. 2 is a flow chart of a vehicle diagnostic method provided by another embodiment of the present application, and the method is executed by a vehicle diagnostic device. Figure 5As shown, the method includes the following steps S201-S212, wherein steps S201-S204 are executed by the voice process, and steps S210-S212 are executed by the diagnostic thread of the diagnostic process. It can be understood that the voice process and the diagnostic process belong to two different processes, so the voice process and the diagnostic process can work in parallel.

[0074] S201: Acquire a first voice command.

[0075] The first voice command may be a command transmitted to the vehicle diagnostic device via an external voice input device (eg, a smart phone or computer including a microphone), or may be a command received via a microphone of the vehicle diagnostic device itself.

[0076] S202: Transmitting the first voice instruction to an automatic voice recognition module, so that the automatic voice recognition module performs voice recognition on the first voice instruction to obtain first text information.

[0077] In order to accurately perform voice recognition on the first voice command, in the embodiment of the present application, the vehicle diagnostic device includes an automatic speech recognition (ASR) module, and the ASR module is used to convert the voice information received by the vehicle diagnostic device into text information.

[0078] Since the first voice command received in the embodiment of the present application may include proprietary names in the field, such as reading fault codes, etc., in order to improve the accuracy of the ASR module in recognizing and converting the first voice command into the first text information, the ASR module can be trained using proprietary names related to the field, thereby improving the accuracy of the recognized first text information.

[0079] S203: Receive a first text message sent by the automatic speech recognition module, and transmit the first text message to the intention recognition module, so that the intention recognition module parses the first text message to obtain a first parsed intention.

[0080] Among them, in order to accurately parse the first text information, in an embodiment of the present application, the vehicle diagnostic device includes an intention recognition module, which is used to recognize the intention of the received text information to determine the operation that the user requires the vehicle diagnostic device to perform, thereby obtaining the diagnostic function instructions to be executed for the vehicle to be tested.

[0081] S204: receiving the diagnostic function instruction to be executed of the vehicle to be detected sent by the intention recognition module, and transmitting the diagnostic function instruction to be executed of the vehicle to be detected to the voice interaction thread of the diagnosis process.

[0082] Among them, the diagnostic process includes at least two parallel threads, one is a voice interaction thread, which is used to interact with the voice process, that is, the interaction between the diagnostic process and the voice process is realized through the voice interaction thread; the other is a diagnostic thread, which is used to perform diagnostic functions on the vehicle to be inspected.

[0083] S205: Obtaining the status of the diagnosis thread of the vehicle diagnosis device at the current moment through the voice interaction thread.

[0084] Among them, the user can provide the vehicle configuration information of the vehicle to be tested in the form of voice, and the vehicle configuration information can be received through the voice process in this step; the display screen of the vehicle diagnostic equipment can also display all optional vehicle configuration information to the user for the user to select and confirm, and the vehicle configuration information determined by the user can be obtained through the input process in this step.

[0085] S206: Determine through the voice interaction thread whether the state indicates that the current diagnosis thread is performing a diagnosis function on the vehicle to be detected. If so, go to S207; if not, go to S208.

[0086] Among them, the principles and implementation methods of S204~S206 can be referred to Figure 4 S110 to S112 in the above description will not be described in detail here.

[0087] S207: Outputting rejection information to the voice process through the voice interaction thread, so that the voice process generates and outputs prompt information after receiving the rejection information.

[0088] Among them, after the voice interaction thread determines that the diagnostic thread is currently executing a diagnostic function on the vehicle to be detected, it does not transmit the diagnostic function instructions to be executed of the vehicle to be detected to the diagnostic thread, thereby not terminating the diagnostic function that the diagnostic thread is executing on the vehicle to be detected, and outputs a rejection message to the voice process, so that the voice process generates and outputs a prompt message after receiving the rejection message, thereby prompting the user that the diagnostic device cannot execute the first voice command according to the diagnostic function instructions to be executed of the vehicle to be detected at the current moment.

[0089] S208: Transmitting the diagnostic function instructions to be executed of the vehicle to be detected to the diagnostic thread through the voice interaction thread.

[0090] Among them, after the voice interaction thread determines that the diagnostic thread is not executing the diagnostic function on the vehicle to be detected at the current moment, it transmits the diagnostic function instructions to be executed of the vehicle to be detected to the diagnostic thread, so that the diagnostic thread executes the diagnostic function instructions to be executed of the vehicle to be detected.

[0091] S209: Obtain vehicle configuration information of the vehicle to be detected.

[0092] Among them, the principle and implementation of S209 can be referred to Figure 2 The S130 in the specification will not be described in detail here.

[0093] S210: Determine all execution paths of the diagnostic function to be executed in the vehicle diagnostic device according to the stored first corresponding relationship.

[0094] Among them, the principle and implementation of S210 can be referred to Figure 2 The S120 in the specification will not be described in detail here.

[0095] S211: Determine, from all execution paths, a target execution path that matches the vehicle configuration information of the vehicle to be detected according to the stored second corresponding relationship.

[0096] S212: Execute a diagnostic function corresponding to the target execution path on the vehicle to be detected.

[0097] The principles and implementation methods of S211 to S212 can be found in Figure 2 S140~S150 in the above description will not be described in detail here.

[0098] Since traditional vehicle diagnostic equipment usually uses a touch screen or buttons for operation, users can only select according to the fixed buttons and menus set by the diagnostic equipment through manual operation, and cannot directly input the functions they want or current symptoms, resulting in low convenience and requiring users to operate step by step, resulting in low diagnostic efficiency. Therefore, in the embodiment of the present application, the user can input a first voice command to the vehicle diagnostic equipment to enable the vehicle diagnostic equipment to perform the diagnostic function to be executed on the vehicle to be tested, without the need for the user to operate tediously step by step, thereby bringing convenience to the user and improving diagnostic efficiency.

[0099] Furthermore, in an embodiment of the present application, a first voice command and a diagnostic function instruction to be executed of a vehicle to be detected are received through a voice process, and the diagnostic process receives the diagnostic function instruction to be executed of the vehicle to be detected sent by the voice process through a voice interaction thread, and the diagnostic function is executed on the vehicle to be detected through the diagnostic thread. Since the voice interaction thread and the diagnostic thread in the diagnostic process are two different threads that can work in parallel, during the process of the diagnostic thread executing the diagnostic function on the vehicle to be detected, the interaction between the voice process and the voice interaction thread can be avoided to affect the working diagnostic thread, thereby avoiding the situation where the diagnostic thread terminates the executing diagnostic function during the process of executing the diagnostic function on the vehicle to be detected.

[0100] In some embodiments, the intention recognition module in the vehicle diagnostic device parses the first text information through the following steps b01 to b03 to obtain the diagnostic function instructions to be executed for the vehicle to be detected.

[0101] Step b01: Determine the target intent entity corresponding to the first text information.

[0102] Among them, the intention entity is the entity of the user's intended operation, including button name, operation action, diagnostic function name, and query object in querying diagnostic data.

[0103] Step b02: Determine a target specification entity in a vector database that matches the target intent entity, wherein the vector database includes a fourth correspondence between the specification entity and the diagnostic function instruction.

[0104] Among them, the standard entity is an entity stored in the vehicle diagnostic equipment, and its name is unique. For the same standard entity, different users may express it differently, so in this step, it is necessary to determine the target standard entity that matches the target intent entity to accurately determine the entity that the user intends to operate. In this step, the target standard entity that matches the target intent entity is determined so that the diagnostic function instructions to be executed for the vehicle to be tested can be accurately generated later. The role of the vector database is to use the vector database similarity search capability to match the target intent entity corresponding to the first text information to the standard entity in the vector database.

[0105] In some embodiments, the canonical entity in the vector database is determined by the following steps b21 to b22:

[0106] Step b21: Determine at least one of the professional names, popular names, and corresponding vehicle abnormal symptoms of the diagnostic functions of multiple vehicle brands.

[0107] Among them, you can determine the professional name of the diagnostic function by visiting the official website or technical manual of the vehicle brand. You can determine the popular name of the diagnostic function by consulting information on social media, forums and other websites to understand consumers and technicians' popular names for the diagnostic function. You can determine the abnormal vehicle symptoms corresponding to the diagnostic function through actual repair cases provided by users.

[0108] Step b22: Determine the standard entity in the vector database according to at least one of the professional name, the popular name and the abnormal symptom of the vehicle.

[0109] Among them, professional names, popular names or abnormal vehicle symptoms can be determined as standard entities, or professional names and popular names can be combined to form a standard entity.

[0110] In some embodiments, step b02 includes the following steps b23 to b24:

[0111] Step b23: Determine the overall matching degree between the target intent entity and all standard entities respectively.

[0112] In this step, the matching degree between the target intent entity and each standard entity stored in the vector database is determined respectively. For example, if there are 10 standard entities stored in the vector database, then in this step, 10 matching degrees between the target intent entity and the above 10 standard entities are determined respectively.

[0113] Step b24: Determine the target standard entity based on the total matching degree.

[0114] In this step, the standard entity corresponding to the maximum matching degree can be determined as the target standard entity.

[0115] By determining multiple matching degrees between a target intent entity and multiple standard entities, and then determining the target standard entity based on the matching degrees, the determination method is more accurate and simple, thereby improving the accuracy and efficiency of determining the target standard entity.

[0116] Step b03: Determine the diagnostic function instruction to be executed of the vehicle to be detected corresponding to the first text information according to the target specification entity and the fourth corresponding relationship.

[0117] Among them, in this step, the diagnostic function instruction to be executed of the vehicle to be detected corresponding to the first text information can be determined through the fourth corresponding relationship.

[0118] In some embodiments, if the maximum matching degree among all matching degrees is less than a preset threshold, the first voice instruction is determined to be wrong, step b03 is not performed, and information that the first voice instruction is wrong is output through the vehicle diagnostic device. If the maximum n matching degrees among all matching degrees are greater than or equal to the preset threshold, the standard entity corresponding to the maximum n matching degrees is determined to be the target standard entity, where n is a positive integer.

[0119] The preset threshold can be set as needed, for example, 95%, 90% or 80%, etc., and is not limited here. If the maximum matching degree among multiple matching degrees is less than the preset threshold, it means that the target specification entity that matches the target intent entity cannot be accurately determined, and the first voice instruction cannot be executed.

[0120] For example, a car with a 4-cylinder engine generally has four fuel injectors, namely, fuel injector 1, fuel injector 2, fuel injector 3 and fuel injector 4, and the four standard entities of fuel injector 1, fuel injector 2, fuel injector 3 and fuel injector 4 are stored in the vector database. If the user does not specify which fuel injector it is, the target intention entity is the fuel injector, and the matching degree of the target intention entity with the four standard entities of fuel injector 1, fuel injector 2, fuel injector 3 and fuel injector 4 is the same and greater than the preset threshold, and both are greater than the matching degree of the target intention entity with other standard entities except these four standard entities. In this step, fuel injector 1, fuel injector 2, fuel injector 3 and fuel injector 4 are all determined as target standard entities.

[0121] In the embodiment of the present application, by judging the size relationship between multiple matching degrees and a preset threshold, the target standard entity is determined only when the matching degree is greater than or equal to the preset threshold, thereby improving the accuracy of the determined target standard entity.

[0122] In some embodiments, before executing step b01, the target intent type corresponding to the first text information may also be determined first, and the vector database in step b02 is a vector database of a type corresponding to the target intent type among a plurality of pre-configured type vector databases.

[0123] Among them, the intention type includes the intention to execute the diagnostic function, the intention to query the diagnostic information, and the intention to operate the button. In this step, the target intention type can be determined by the content of the first text message. For example, if the first text message is to read the fault code, the corresponding target intention type is the intention to execute the diagnostic function.

[0124] In an embodiment of the present application, the target intent type and the target specification entity that matches the target intent entity are determined through the first text information, and then the diagnostic function instructions to be executed for the vehicle to be inspected are generated, which can avoid the situation where the user intent cannot be correctly executed due to inaccurate user expression.

[0125] It should be noted that the intent recognition module can be trained by deep learning. Specifically, the corpus of standardized entity names, vehicle function queries, and diagnostic information queries in various scenarios and the corresponding intent types can be collected as positive sample data sets, and the corpus of non-above intents can be used as negative sample data sets, and then the intent recognition module can be trained using the positive sample data sets and the negative sample data sets.

[0126] It is worth noting that the vector database can include data in the diagnostic program as a knowledge reserve for the intention recognition module. Since it includes the graphical interface that interacts with the user in the diagnostic program, and the vector data generated by the vectorization of the operation actions of the graphical interface that interacts with the user, all vectors are associated with control instructions, so that the query of the control instructions of the graphical interface that interacts with the user can be realized. The vector database can also include the function names of all brands, the common names of the function names of each brand, and the diagnostic function vector data generated by the vectorization of vehicle symptoms. All vectors are associated with the corresponding diagnostic function instructions. Vehicle symptoms need to collect the corresponding diagnostic functions to realize the query of diagnostic function instructions through diagnostic function names and vehicle symptoms. The addition of the common names of the function names of each brand can enable users to find the desired functions without knowing the real function name of the current brand. The vector database can also include the function help information, abbreviations and their expansion vectorization of each function in the diagnostic program to generate maintenance knowledge vector data, and the corresponding help information or abbreviation expansion can be queried through the function name and abbreviation.

[0127] exist Figure 5 Based on the embodiments provided, in the embodiments of the present application, the vehicle diagnosis method further includes the following steps which are all performed through the voice process:

[0128] Step c01: Receive a second voice instruction.

[0129] Step c02: Transmit the second voice instruction to the automatic voice recognition module, so that the automatic voice recognition module performs voice recognition on the second voice instruction to obtain second text information.

[0130] Among them, in the embodiment of the present application, the vehicle diagnostic equipment includes an automatic speech recognition module.

[0131] Step c03: receiving the second text information sent by the automatic speech recognition module, and transmitting the second text information to the intention recognition module, so that the intention recognition module parses the second text information to obtain a diagnostic data query instruction, wherein the diagnostic data query instruction includes the intention information of querying the diagnostic data.

[0132] Among them, in the embodiment of the present application, the vehicle diagnostic equipment includes an intention recognition module.

[0133] Steps c01 to c03 are similar to S201 to S203 , and therefore, the principles and implementation methods of steps c01 to c03 may refer to those of S201 to S203 , and will not be described in detail here.

[0134] Herein, querying diagnostic information can be understood as querying the explanation and description of professional terms in this field, or querying the explanation and description of some abbreviations, etc.

[0135] Step c04: receiving a diagnostic data query instruction sent by the intention recognition module, querying diagnostic data stored in the vehicle diagnostic device or in a server connected to the vehicle diagnostic device in communication according to the diagnostic data query instruction, and outputting the queried diagnostic data.

[0136] Among them, in this step, data is pre-stored in the vehicle diagnostic device. Therefore, when the voice process receives an instruction to query diagnostic data, in order to improve the efficiency of outputting diagnostic data, the diagnostic data is preferentially queried and output from the data stored in the vehicle diagnostic device. If the diagnostic data cannot be queried from the data stored in the vehicle diagnostic device, the diagnostic data is queried from the data stored in the server that is communicatively connected to the vehicle diagnostic device. After the vehicle diagnostic device downloads the queried diagnostic data from the server, it outputs the queried diagnostic data.

[0137] Since users may encounter unfamiliar professional terms when using vehicle diagnostic equipment or diagnosing a vehicle, in an embodiment of the present application, the vehicle diagnostic equipment provides users with diagnostic data query and outputs diagnostic data, thereby bringing convenience to users.

[0138] exist Figure 5 Based on the provided embodiment, in the embodiment of the present application, the vehicle diagnosis method further includes the following steps:

[0139] Step d01: receiving a third voice instruction through a voice process.

[0140] Step d02: Transmit the third voice instruction to the automatic speech recognition module, so that the automatic speech recognition module performs speech recognition on the third instruction and obtains third text information.

[0141] Among them, in the embodiment of the present application, the vehicle diagnostic equipment includes an automatic speech recognition module.

[0142] Step d03: Receive the third text information sent by the automatic speech recognition module through the voice process, and transmit the third text information to the intention recognition module, so that the intention recognition module parses the third text information and obtains the operation target button instruction, wherein the operation target button instruction includes the intention information of the operation target button.

[0143] Among them, in the embodiment of the present application, the vehicle diagnostic equipment includes an intention recognition module.

[0144] Step d04: Receive the operation target button instruction sent by the intention recognition module through the voice process, and send the operation target button instruction to the voice interaction thread.

[0145] Among them, step d01 to step d04 are similar to S201 to S204. Therefore, the principles and implementation methods of step d01 to step d04 can refer to S201 to S204 and will not be repeated here.

[0146] Step d05: Receive the target button operation instruction sent by the voice interaction thread through the button operation thread of the diagnosis process, and operate the target button according to the target button operation instruction.

[0147] The operation button can be understood as an element or button on a graphical interface displayed by the vehicle diagnostic device for user interaction, which executes a command corresponding to the button or triggers a function corresponding to the button by clicking or touching a button. It should be noted that in the embodiment of the present application, the button operation thread and the diagnosis thread can be the same thread or two different threads.

[0148] In the embodiment of the present application, the user can operate the target button through voice without the need for the user to manually click or touch the target button, thereby bringing convenience to the user.

[0149] It is worth noting that only when the diagnostic thread starts executing the second diagnostic function before the first diagnostic function of the vehicle to be detected is completed, the first diagnostic function will be forced to end. The operation button will not cause the executing diagnostic function to be forced to end.

[0150] In some embodiments, the diagnostic thread will send the names of the operable buttons in the graphical interface displayed by the current vehicle diagnostic device and capable of interacting with the user to the voice process at the same time as the voice process receives the voice command, so that the voice process will send the received operable button names to the intent recognition module, so that the intent recognition module can match and generate a parsed intent based on the operable button names.

[0151] In some embodiments, when displaying important prompt information, the vehicle diagnostic device will send the text information of the prompt information to the voice process, so that the voice process will voice broadcast the important prompt information to attract the user's attention. The importance of the prompt information can be set as needed.

[0152] Figure 6 A schematic diagram of the structure of a vehicle diagnostic device provided in an embodiment of the present application is shown. The specific embodiment of the present application does not limit the specific implementation of the vehicle diagnostic device.

[0153] like Figure 6 As shown, the vehicle diagnostic device 300 may include a processor 302 and a memory 304 .

[0154] The memory 304 is used to store a computer program 306. The memory 304 may include a high-speed RAM memory, or may also include a non-volatile memory, such as at least one disk memory. The computer program 306 may include computer executable instructions.

[0155] The processor 302 is used to execute the computer program 306 to implement the above-mentioned vehicle diagnosis method embodiment.

[0156] The processor 302 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the vehicle diagnostic device may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.

[0157] Figure 7 FIG. 1 is a schematic diagram of a vehicle diagnostic system provided by an embodiment of the present application. Figure 7 As shown, the vehicle diagnostic system 10 includes a vehicle diagnostic device 400 and a server 500. The vehicle diagnostic device 400 and the server 500 are communicatively connected. Figure 8 FIG. 2 is a flow chart of a vehicle diagnostic method provided by another embodiment of the present application. Figure 8 As shown, the vehicle diagnosis method includes the following steps:

[0158] S410: The vehicle diagnostic device 400 obtains a first voice command.

[0159] S420 : The vehicle diagnostic device 400 transmits the first voice command to the server 500 .

[0160] S430: The server 500 performs voice recognition on the first voice instruction to obtain first text information.

[0161] The server 500 includes an automatic speech recognition module, and the first voice instruction is recognized by the automatic speech recognition module.

[0162] S440: The server 500 parses the first text information to obtain a diagnostic function instruction to be executed for the vehicle to be detected.

[0163] The server 500 includes an intention recognition module, and the first text information is parsed by the intention recognition module.

[0164] S450 : The server 500 transmits the diagnostic function instruction to be executed of the vehicle to be detected to the vehicle diagnostic device 400 .

[0165] S460: The vehicle diagnostic device 400 determines all execution paths of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first correspondence.

[0166] The first corresponding relationship is the corresponding relationship between the diagnostic function instruction and the execution path.

[0167] S470: The vehicle diagnosis device 400 obtains vehicle configuration information of the vehicle to be detected.

[0168] S480: The vehicle diagnosis device 400 determines a target execution path that matches the vehicle configuration information of the vehicle to be detected from all execution paths according to the stored second corresponding relationship.

[0169] The second corresponding relationship is the corresponding relationship between the execution path and the vehicle configuration information.

[0170] S490: The vehicle diagnosis device 400 executes a diagnosis function corresponding to the target execution path on the vehicle to be detected.

[0171] The principles, implementation methods and beneficial effects of the embodiments of the present application can be referred to the aforementioned related method embodiments, which will not be repeated here. It is worth noting that in the embodiments of the present application, by integrating the automatic speech recognition module and the intention recognition module in the server 500 instead of in the vehicle diagnostic device 400, the volume of the vehicle diagnostic device 400 can be effectively reduced.

[0172] exist Figure 8 Based on the provided embodiments, in some embodiments, S440 performed by the server 500 includes the following steps:

[0173] Step e01: The server 500 determines a target intent entity corresponding to the first text information.

[0174] Step e02: The server 500 determines a target specification entity in a vector database that matches the target intent entity, wherein the vector database includes a fourth correspondence between the specification entity and the diagnostic function instruction.

[0175] Step e03: the server 500 determines the diagnostic function instruction to be executed of the vehicle to be detected corresponding to the first text information according to the target specification entity and the fourth corresponding relationship.

[0176] The principles, implementation methods and beneficial effects of the embodiments of the present application can be referred to the aforementioned related method embodiments, which will not be repeated here.

[0177] In some embodiments, before executing step e01, the server 500 first determines the target intent type corresponding to the first text information, wherein the vector database in step e02 is a vector database of a type corresponding to the target intent type among a plurality of pre-configured type vector databases.

[0178] The principles, implementation methods and beneficial effects of the embodiments of the present application can be referred to the aforementioned related method embodiments, which will not be repeated here.

[0179] In some embodiments, the server 500 determines the target specification entity by executing the following steps f01 to f02.

[0180] Step f01: The server 500 determines all matching degrees between the target intent entity and all standard entities respectively.

[0181] Step f02: The server 500 determines the target standard entity according to all matching degrees.

[0182] In some embodiments, step f02 includes: if the maximum degree of match among all the degrees of match is less than a preset threshold, the server 500 determines that the first voice instruction is wrong, does not execute step e03, and outputs information that the first voice instruction is wrong to the vehicle diagnostic device 400. If the maximum n degrees of match among all the degrees of match are greater than or equal to the preset threshold, the server 500 determines that the standard entity corresponding to the maximum n degrees of match is the target standard entity, where n is a positive integer. The vehicle diagnostic device 400 is also used to receive and output information that the first voice instruction is wrong sent by the server 500.

[0183] In some embodiments, the vehicle diagnostic device 400 is further configured to receive a second voice command and transmit the second voice command to the server 500. The server 500 is further configured to receive the second voice command, perform voice recognition on the second voice command to obtain a second text message, parse the second text message to obtain a diagnostic data query instruction, and transmit the diagnostic data query instruction to the vehicle diagnostic device 400. The vehicle diagnostic device 400 is further configured to query diagnostic data stored in the vehicle diagnostic device 400 or the server 500 according to the diagnostic data query instruction, and output the queried diagnostic data.

[0184] In some embodiments, the vehicle diagnostic device 400 is further configured to receive a third voice command and transmit the third voice command to the server 500. The server 500 is further configured to receive the third voice command, perform voice recognition on the third voice command to obtain third text information, parse the third text information to obtain an operation target button command, and transmit the operation target button command to the vehicle diagnostic device 400. The vehicle diagnostic device 400 is further configured to receive an operation target button command and operate the target button according to the operation target button command.

[0185] An embodiment of the present application provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned vehicle diagnostic method embodiment is implemented.

[0186] An embodiment of the present application provides a computer program, which can be executed by a processor to implement the above-mentioned vehicle diagnostic method embodiment.

[0187] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above-mentioned vehicle diagnostic method embodiment is implemented.

[0188] In several embodiments provided in the present application, if any function is implemented in the form of a software function module / unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the technical solution of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, server or other electronic device) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (RandomAccess Memory, RAM), disk or optical disk and other media that can store computer program codes.

[0189] The algorithm or display provided here are not inherently related to any specific computer, virtual system or other equipment. Various general systems can also be used together with the teaching based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the present application embodiment is not directed to any specific programming language yet. It should be understood that various programming languages ​​can be utilized to realize the content of the present application described here, and the above description of specific languages ​​is to disclose the best mode of implementation of the present application.

[0190] It should be noted that the above embodiments illustrate the present application rather than limit the present application, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be constructed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of multiple such elements. The present application may be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In the claims that list several devices, several units or modules in these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

[0191] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A vehicle diagnostic method, characterized in that: The method comprises: The vehicle diagnostic device obtains a diagnostic function instruction to be executed of the vehicle to be detected; The vehicle diagnostic device determines all execution paths of the diagnostic function instructions to be executed in the vehicle diagnostic device according to a stored first correspondence relationship, wherein the first correspondence relationship is a correspondence relationship between the diagnostic function instructions and the execution paths; The vehicle diagnostic device acquires vehicle configuration information of the vehicle to be detected; The vehicle diagnostic device determines, from the entire execution paths, a target execution path that matches the vehicle configuration information of the vehicle to be detected according to a stored second correspondence relationship, wherein the second correspondence relationship is a correspondence relationship between the execution path and the vehicle configuration information; The vehicle diagnosis device performs a diagnosis function corresponding to the target execution path on the vehicle to be detected.

2. The method according to claim 1, characterized in that The vehicle diagnostic device performs a diagnostic function corresponding to the target execution path on the vehicle to be detected, including: If the vehicle diagnostic device determines that there are multiple target execution paths, the diagnostic function corresponding to each target execution path is sequentially executed on the vehicle to be detected.

3. The method according to claim 1, characterized in that The vehicle diagnostic device performs a diagnostic function corresponding to the target execution path on the vehicle to be detected, including: If the vehicle diagnostic device determines that there are multiple target execution paths, the vehicle diagnostic device determines and outputs multiple vehicle electronic control units ECUs corresponding to the multiple target execution paths according to the stored third correspondence relationship, wherein the third correspondence relationship is a correspondence relationship between execution paths and ECUs; The vehicle diagnostic device executes a diagnostic function corresponding to the target ECU on the vehicle to be inspected in response to an operation of selecting the target ECU from among the plurality of ECUs.

4. The method according to claim 1, characterized in that: Before the vehicle diagnostic device obtains the diagnostic function instruction to be executed of the vehicle to be detected, the method further includes: The vehicle diagnostic device acquires a first voice command; The vehicle diagnostic device performs voice recognition on the first voice instruction to obtain first text information; The vehicle diagnostic device parses the first text information to obtain a diagnostic function instruction to be executed for the vehicle to be detected; Alternatively, before the vehicle diagnostic device obtains the diagnostic function instruction to be executed of the vehicle to be detected, the method further includes: The vehicle diagnostic device acquires a first voice command and transmits the first voice command to a server, wherein the vehicle diagnostic device is in communication with the server; The server performs voice recognition on the first voice instruction to obtain first text information, parses the first text information to obtain the diagnostic function instruction to be executed of the vehicle to be detected, and transmits the diagnostic function instruction to be executed of the vehicle to be detected to the vehicle diagnostic device.

5. The method according to claim 4, characterized in that The step of parsing the first text information to obtain a diagnostic function instruction to be executed for the vehicle to be detected includes: Determining a target intent entity corresponding to the first text information; Determining a target specification entity in a vector database that matches the target intent entity, wherein the vector database includes a fourth correspondence between a specification entity and a diagnostic function instruction; According to the target specification entity and the fourth corresponding relationship, a diagnostic function instruction to be executed of the vehicle to be detected corresponding to the first text information is determined.

6. The method according to claim 5, characterized in that Before determining the target intent entity corresponding to the first text information, the method further includes: Determining a target intent type corresponding to the first text information; The vector database is a vector database of a type corresponding to the target intent type among a plurality of pre-configured types of vector databases.

7. The method according to claim 5, characterized in that The regulatory entity is determined by the following steps: Determine at least one of the professional name, the common name and the corresponding vehicle abnormal symptom of the diagnostic function of multiple vehicle brands; A standard entity in the vector database is determined according to at least one of the professional name, the popular name, and the abnormal vehicle symptom.

8. The method according to claim 5, characterized in that The determining a target specification entity in a vector database that matches the target intent entity comprises: Determining all matching degrees between the target intent entity and all normative entities respectively; The target specification entity is determined according to the total matching degree.

9. The method according to claim 8, characterized in that The determining the target specification entity according to the total matching degree includes: If the maximum matching degree among all the matching degrees is less than a preset threshold, it is determined that the first voice instruction is wrong, the step of determining the diagnostic function instruction corresponding to the first text information according to the target specification entity and the fourth corresponding relationship is not performed, and information that the first voice instruction is wrong is output through the vehicle diagnostic device; If the largest n matching degrees among all the matching degrees are greater than or equal to the preset threshold, the standard entity corresponding to the largest n matching degrees is determined as the target standard entity, where n is a positive integer.

10. The method according to claim 1, characterized in that Before the vehicle diagnostic device determines all execution paths of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first correspondence, the method further includes: The vehicle diagnostic device obtains the state of the diagnostic thread of the vehicle diagnostic device at the current moment; If the status indicates that the diagnostic thread does not perform a diagnostic function on the vehicle to be detected at the current moment, the vehicle diagnostic device performs the step of determining all execution paths of the diagnostic function instructions to be executed in the vehicle diagnostic device according to the stored first correspondence.

11. The method according to claim 1, characterized in that: The method further comprises: The vehicle diagnostic device receives a second voice command; The vehicle diagnostic device performs voice recognition on the second voice instruction to obtain second text information; The vehicle diagnostic device parses the second text information to obtain a diagnostic data query instruction; The vehicle diagnostic device queries the diagnostic data stored in the vehicle diagnostic device or in a server connected to the vehicle diagnostic device in communication according to the diagnostic data query instruction, and outputs the queried diagnostic data; Alternatively, the method further comprises: The vehicle diagnostic device receives a second voice command and transmits the second voice command to a server, wherein the vehicle diagnostic device is in communication with the server; The server performs voice recognition on the second voice instruction to obtain second text information, parses the second text information to obtain a diagnostic data query instruction, and transmits the diagnostic data query instruction to the vehicle diagnostic device; The vehicle diagnostic device queries the diagnostic data stored in the vehicle diagnostic device or the server according to the diagnostic data query instruction, and outputs the queried diagnostic data.

12. The method according to claim 1, characterized in that The method further comprises: The vehicle diagnostic device receives a third voice command; The vehicle diagnostic device performs voice recognition on the third voice command to obtain third text information; The vehicle diagnostic device parses the third text information to obtain an operation target button instruction; the vehicle diagnostic device operates the target button according to the operation target button instruction; Alternatively, the method further comprises: The vehicle diagnostic device receives a third voice command and transmits the third voice command to a server, wherein the vehicle diagnostic device is in communication with the server; The server performs voice recognition on the third voice instruction to obtain third text information, parses the third text information to obtain an operation target button instruction, and transmits the operation target button instruction to the vehicle diagnostic device; The vehicle diagnostic device operates the target button according to the operation target button instruction.

13. A vehicle diagnostic device, comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the vehicle diagnosis method according to any one of claims 1 to 12.

14. A vehicle diagnostic system, characterized in that: The system includes a server and a vehicle diagnostic device, wherein the vehicle diagnostic device is communicatively connected to the server; The vehicle diagnostic device is used to obtain a first voice instruction; upload the first voice instruction to the server, and obtain the diagnostic function instruction to be executed of the vehicle to be detected returned by the server; determine all execution paths of the diagnostic function instruction to be executed in the vehicle diagnostic device according to the stored first correspondence, wherein the first correspondence is the correspondence between the diagnostic function instruction and the execution path; obtain the vehicle configuration information of the vehicle to be detected; determine the target execution path that matches the vehicle configuration information of the vehicle to be detected from all the execution paths according to the stored second correspondence, wherein the second correspondence is the correspondence between the execution path and the vehicle configuration information; execute the diagnostic function corresponding to the target execution path on the vehicle to be detected; The server is used to perform voice recognition on the first voice instruction to obtain first text information; and parse the first text information to obtain the diagnostic function instruction.

15. The system according to claim 14, characterized in that The server is used to parse the first text information and obtain the diagnostic function instruction to be executed of the vehicle to be detected, specifically to: Determining a target intent entity corresponding to the first text information; Determining a target specification entity in a vector database that matches the target intent entity, wherein the vector database includes a fourth correspondence between a specification entity and a diagnostic function instruction; According to the target specification entity and the fourth corresponding relationship, a diagnostic function instruction to be executed of the vehicle to be detected corresponding to the first text information is determined.

16. The system according to claim 15, characterized in that Before determining the target intent entity corresponding to the first text information, the server is further configured to: Determining a target intent type corresponding to the first text information; The vector database is a vector database of a type corresponding to the target intent type among a plurality of pre-configured types of vector databases.

17. The system according to claim 14, characterized in that The vehicle diagnostic device is also used to receive a second voice command and transmit the second voice command to the server; The server is further configured to receive the second voice command, perform voice recognition on the second voice command to obtain second text information, parse the second text information to obtain a diagnostic data query instruction, and transmit the diagnostic data query instruction to the vehicle diagnostic device; The vehicle diagnostic device is also used to query the diagnostic data stored in the vehicle diagnostic device or the server according to the diagnostic data query instruction, and output the queried diagnostic data.

18. The system according to claim 14, characterized in that The vehicle diagnostic device is also used to receive a third voice command and transmit the third voice command to the server; The server is further configured to receive the third voice instruction, perform voice recognition on the third voice instruction to obtain third text information, parse the third text information to obtain an operation target button instruction, and transmit the operation target button instruction to the vehicle diagnostic device; The vehicle diagnostic device is further configured to receive the target button operation instruction and operate the target button according to the target button operation instruction.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the vehicle diagnosis method according to any one of claims 1 to 12 is implemented.

Images