Vehicle diagnosis method and device, terminal equipment and computer program product

Abstract

The invention relates to a vehicle diagnosis method and device, terminal equipment and a computer program product, and the method comprises the steps that the following processing is executed through first terminal equipment: a preset interaction interface is displayed, and the interaction interface comprises target maintenance data corresponding to a target part and a target diagnosis link corresponding to the target part; in response to a selection operation on a target diagnosis link, target diagnosis menu configuration corresponding to the target part is obtained, and the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis menu configuration; and displaying a target diagnosis menu based on the target diagnosis menu configuration, and performing diagnosis operation on the to-be-diagnosed vehicle through the target diagnosis menu. Through application of the method and the device, the problem of relatively low vehicle diagnosis efficiency caused by complicated switching operation of the H5 page and the menu in the vehicle diagnosis equipment in the related technology is solved, and the technical effect of improving the vehicle diagnosis efficiency is realized.

Description

Technical Field

[0001] This application belongs to the technical field of data processing, and particularly relates to a vehicle diagnosis method, apparatus, terminal device, and computer program product. Background Art

[0002] With the increasing complexity of vehicle electronic control systems, the demand for vehicle diagnostic devices has also been continuously increasing. Vehicle diagnostic devices support using H5 pages to display vehicle repair assistance, maintenance materials, and maintenance cases, etc. Users can view the above-mentioned vehicle repair data edited by other users on the vehicle diagnostic device, or edit the above-mentioned vehicle repair data (for example, reply to a vehicle repair assistance post) through the vehicle diagnostic device and upload it to the server.

[0003] However, after a user finds the corresponding repair method by viewing the above-mentioned vehicle repair data stored locally or on the server through the vehicle diagnostic device, they often need to exit the current page, then open the corresponding diagnostic software, and start the vehicle diagnostic operation only after debugging the diagnostic menu of the diagnostic software based on the repair method; even more, some of the content in the vehicle repair data is complicated, and the user needs to perform operations of entering and exiting the page and menu debugging multiple times before they can start the vehicle diagnostic operation, which will prolong the diagnostic time of the vehicle diagnostic device and greatly reduce the vehicle diagnostic efficiency.

[0004] Currently, for the problem of low vehicle diagnostic efficiency caused by the complicated switching operation between the H5 page and the menu in the vehicle diagnostic device in the related art, no effective solution has been proposed. Summary of the Invention

[0005] Embodiments of this application provide a vehicle diagnosis method, apparatus, terminal device, and computer program product, so as to at least solve the problem of low vehicle diagnostic efficiency caused by the complicated switching operation between the H5 page and the menu in the vehicle diagnostic device in the related art.

[0006] In a first aspect, embodiments of this application provide a vehicle diagnosis method, including: performing the following processing through a first terminal device: displaying a preset interaction interface, where the interaction interface includes target repair data corresponding to a target component and a target diagnosis link corresponding to the target component; in response to a selection operation on the target diagnosis link, obtaining a target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by a second terminal device to be associated with the target diagnosis menu configuration; displaying a target diagnosis menu based on the target diagnosis menu configuration, and performing a diagnosis operation on a vehicle to be diagnosed through the target diagnosis menu.

[0007] In some embodiments, obtaining a target diagnostic menu configuration corresponding to the target component in response to a selection operation on the target diagnostic link includes: obtaining a target diagnostic software configuration corresponding to the target diagnostic link in response to the selection operation on the target diagnostic link, where the target diagnostic link is configured by the second terminal device to be associated with the target diagnostic software configuration; determining whether the target diagnostic software corresponding to the target diagnostic software configuration is stored locally; and obtaining the target diagnostic menu configuration when the target diagnostic software is stored locally.

[0008] In some embodiments, presenting a target diagnostic menu based on the target diagnostic menu configuration includes: loading the target diagnostic menu configuration, and obtaining the names and paths of target diagnostic functions corresponding to the target diagnostic menu configuration; starting the target diagnostic software, and controlling the target diagnostic software to generate and present the target diagnostic menu based on the names and paths of the target diagnostic functions.

[0009] In some embodiments, after presenting the target diagnostic menu based on the target diagnostic menu configuration and performing a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu, the method further includes: when the presentation of the target diagnostic menu fails, requesting the target diagnostic menu corresponding to the target diagnostic menu configuration from the server, and controlling the target diagnostic software to present the target diagnostic menu.

[0010] In some embodiments, after presenting the target diagnostic menu based on the target diagnostic menu configuration and performing a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu, the method further includes: when the presentation of the target diagnostic menu fails, controlling the target diagnostic software to generate a local diagnostic menu; correcting each diagnostic function in the local diagnostic menu based on the names and paths of the target diagnostic functions to obtain the target diagnostic menu, and controlling the target diagnostic software to present the target diagnostic menu.

[0011] In some embodiments, the method further includes: performing the following processing by the second terminal device: in response to an editing operation on the target maintenance data, requesting an initial diagnostic menu corresponding to the target component from the server, where the initial diagnostic menu includes a plurality of target diagnostic functions, and each target diagnostic function corresponds to a plurality of target options; in response to an editing operation on the target options corresponding to each target diagnostic function in the initial diagnostic menu, generating the target diagnostic link and the target diagnostic menu configuration, and associating the target diagnostic link with the target diagnostic menu configuration.

[0012] In some embodiments, performing a diagnostic operation on a vehicle to be diagnosed through the target diagnostic menu includes: detecting the Bluetooth connection status of the vehicle to be diagnosed; and when the Bluetooth connection status is connected, performing a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu.

[0013] In a second aspect, an embodiment of the present application provides a vehicle diagnostic device, including: a display module, configured to display a preset interaction interface, where the interaction interface includes target maintenance data corresponding to a target component and a target diagnostic link corresponding to the target component; an acquisition module, configured to, in response to a selection operation on the target diagnostic link, acquire a target diagnostic menu configuration corresponding to the target component, where the target diagnostic link is configured by a second terminal device to be associated with the target diagnostic menu configuration; and a diagnostic module, configured to display a target diagnostic menu based on the target diagnostic menu configuration and perform a diagnostic operation on a vehicle to be diagnosed through the target diagnostic menu.

[0014] In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the vehicle diagnostic method according to any one of the above first aspects is implemented.

[0015] In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program. When the computer program is run, the vehicle diagnostic method according to any one of the above first aspects is executed.

[0016] Compared with the related art, in the vehicle diagnostic method, device, terminal device, and computer program product provided by the embodiments of the present application, an interaction interface is displayed through a first terminal device. The interaction interface includes target maintenance data corresponding to a target component and a target diagnostic link corresponding to the target component. A user can click on the target diagnostic link to acquire a target diagnostic menu configuration corresponding to the target component. The association relationship between the target diagnostic link and the target diagnostic menu configuration is configured by a second terminal device. Then, the first terminal device can display a target diagnostic menu based on the target diagnostic menu configuration and perform a diagnostic operation on a vehicle to be diagnosed through the target diagnostic menu. In this way, after consulting the required maintenance data, the user does not need to manually switch to a diagnostic software to perform menu debugging operations, avoiding the cumbersome switching operations between the H5 page and the diagnostic menu, thereby reducing the diagnostic time of the vehicle diagnostic device and improving the efficiency of vehicle diagnosis. Through the present application, the problem of low vehicle diagnosis efficiency caused by the cumbersome switching operations between the H5 page and the menu in the related art vehicle diagnostic device is solved, and the technical effect of improving the efficiency of vehicle diagnosis is achieved.

[0017] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more concise and understandable. Description of the Drawings

[0018] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0019] Figure 1 is an architecture diagram of a communication system according to an embodiment of the present application;

[0020] Figure 2 is a flowchart of a vehicle diagnosis method according to an embodiment of the present application;

[0021] Figure 3 is a structural schematic diagram of a vehicle diagnosis device according to an embodiment of the present application;

[0022] Figure 4 is a structural schematic diagram of a terminal device according to an embodiment of the present application. Detailed Embodiments

[0023] In the following description, specific details such as specific system structures and technologies are presented for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0024] It should be understood that when used in the specification and claims of the present application, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0025] It should also be understood that the term "and / or" used in the specification and claims of the present application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0026] As used in the specification of this application and the appended claims, the term "if" may be construed as "when", "once", "in response to determining", or "in response to detecting" depending on the context. Similarly, the phrases "if determined" or "if [the described condition or event] is detected" may be construed as meaning "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]" depending on the context.

[0027] In addition, in the description of the specification of this application and the appended claims, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be construed as indicating or implying relative importance.

[0028] Reference to "one embodiment" or "some embodiments" or the like described in the specification of this application means that a specific feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of this application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "comprising", "including", "having", and their variants all mean "including but not limited to", unless otherwise specifically emphasized in another way.

[0029] With the increasing complexity of vehicle electronic control systems, the demand for vehicle diagnostic devices is also constantly increasing. Vehicle diagnostic devices support using H5 pages to display vehicle repair assistance, maintenance data, and maintenance cases, etc. Users can view the above-mentioned vehicle repair data edited by other users on the vehicle diagnostic device, or edit the above-mentioned vehicle repair data (for example, reply to a vehicle repair assistance post) through the vehicle diagnostic device and upload it to the server.

[0030] However, after the user finds the corresponding repair method by viewing the above-mentioned vehicle repair data stored locally or on the server through the vehicle diagnostic device, the user often needs to exit the current page, then open the corresponding diagnostic software, and start the vehicle diagnostic operation only after debugging the diagnostic menu of the diagnostic software based on the repair method; even, the content in some vehicle repair data is complex, and the user needs to perform operations of entering and exiting the page and menu debugging multiple times before starting the vehicle diagnostic operation, which will prolong the diagnostic time of the vehicle diagnostic device and greatly reduce the efficiency of vehicle diagnosis.

[0031] Currently, no effective solution has been proposed for the problem of low vehicle diagnostic efficiency caused by the complex switching operation between the H5 page and the menu in the vehicle diagnostic device in the related art.

[0032] In view of this, an embodiment of the present application provides a vehicle diagnosis method. An interaction interface is displayed through a first terminal device. The interaction interface includes target maintenance data corresponding to a target component and a target diagnosis link corresponding to the target component. A user can click on the target diagnosis link to obtain a target diagnosis menu configuration corresponding to the target component. The association relationship between the target diagnosis link and the target diagnosis menu configuration is configured by a second terminal device. Then, the first terminal device can display a target diagnosis menu based on the target diagnosis menu configuration and perform a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu. In this way, after the user consults the required maintenance data, there is no need to manually switch to a diagnosis software for menu debugging operations, avoiding complicated switching operations between the H5 page and the diagnosis menu, thereby reducing the diagnosis time of the vehicle diagnosis device and improving the efficiency of vehicle diagnosis. Through the present application, the problem of low vehicle diagnosis efficiency caused by complicated switching operations between the H5 page and the menu in the related art of vehicle diagnosis devices is solved, and the technical effect of improving the efficiency of vehicle diagnosis is achieved.

[0033] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0034] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as a wireless fidelity (WiFi) system, a vehicle to everything (V2X) communication system, a device-to-device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system, such as a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system, such as a new radio (NR) system, and future communication systems, such as a 6th generation (6G) mobile communication system, etc.

[0035] The vehicle diagnosis method provided by the embodiments of the present application can be used for Figure 1 the communication systems shown. Please refer to Figure 1 , Figure 1FIG. 0 is a schematic structural diagram of a communication system 10 according to an embodiment of the present application. The communication system 10 includes: a first terminal device 100, a second terminal device 110, and a server 120. The first terminal device 100 and the second terminal device 110 can communicate with the server 120 through a wired network or a wireless network, and the first terminal device 100 and the second terminal device 110 can communicate with each other through a wired network or a wireless network.

[0036] The server 120 can be a single server, or it can also be a server cluster composed of multiple servers (or micro servers). The server cluster can also be a distributed cluster. The embodiments of the present application do not limit the specific implementation manner of the server 120.

[0037] The first terminal device 100 and the second terminal device 110 can both be vehicle diagnostic devices, or they can be other terminal devices with vehicle diagnostic functions. For example, the first terminal device 100 and the second terminal device 110 can be mobile phones, tablets, desktop computers, laptops, handheld computers, notebooks, ultra-mobile personal computers (UMPCs), netbooks, wearable devices, personal digital assistants (PDAs), augmented reality (AR) / virtual reality (VR) devices, etc. that have vehicle diagnostic functions and can install application software. The embodiments of the present application do not impose special restrictions on the specific forms of the first terminal device 100 and the second terminal device 110.

[0038] The first terminal device 100 and the second terminal device 110 can be used to perform diagnostic operations on a vehicle to be diagnosed. The first terminal device 100 and the second terminal device 110 can also be built into an in-vehicle module, in-vehicle module group, in-vehicle component, in-vehicle chip, or in-vehicle unit of the vehicle to be diagnosed as one or more components or units. The vehicle to be diagnosed can implement the vehicle diagnostic method provided by the present application through the built-in in-vehicle module, in-vehicle module group, in-vehicle component, in-vehicle chip, or in-vehicle unit.

[0039] Specifically, the first terminal device 100 can display a preset interaction interface, where the interaction interface includes target maintenance data corresponding to the target component and a target diagnosis link corresponding to the target component; in response to a selection operation on the target diagnosis link, obtain a target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by the second terminal device 110 to be associated with the target diagnosis menu configuration; display a target diagnosis menu based on the target diagnosis menu configuration, and perform a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu.

[0040] The second terminal device 110 can, in response to an editing operation on the target maintenance data, request an initial diagnosis menu corresponding to the target component from the server, where the initial diagnosis menu includes multiple target diagnosis functions, and each target diagnosis function corresponds to multiple target options; in response to an editing operation on the target options corresponding to the respective target diagnosis functions in the initial diagnosis menu, generate the target diagnosis link and the target diagnosis menu configuration, and associate the target diagnosis link with the target diagnosis menu configuration.

[0041] It should be noted that the user can not only use the first terminal device 100 to view the target maintenance data related to the target component, but also use the first terminal device 100 to perform an editing operation on the target maintenance data, and use the first terminal device 100 to complete the generation and association of the target diagnosis link and the target diagnosis menu configuration. That is to say, the functions of the first terminal device 100 and the second terminal device 110 are not independent. Either the first terminal device 100 or the second terminal device 110 can simultaneously have the functions of the first terminal device 100 and the second terminal device 110 introduced in the above embodiments.

[0042] In specific implementation, the first terminal device 100, the second terminal device 110, and the server 120 can all adopt Figure 4 the shown composition results or include Figure 4 the shown components. Figure 4 FIG. is a schematic structural diagram of a terminal device according to an embodiment of the present application. When the terminal device 4 has the function of the first terminal device 100 described in the embodiment of the present application, the terminal device 4 can be the first terminal device 100 or a chip or system-on-chip in the first terminal device 100; when the terminal device 4 has the function of the second terminal device 110 described in the embodiment of the present application, the terminal device 4 can be the second terminal device 110 or a chip or system-on-chip in the second terminal device 110; when the terminal device 4 has the function of the server 120 described in the embodiment of the present application, the terminal device 4 can be the server 120 or a chip or system-on-chip in the server 120.

[0043] In some embodiments, the first terminal device 100 or the second terminal device 110 provided by the embodiments of the present application can be implemented in software. For example, it can be loaded in Figure 4 the memory 41 of the terminal device 4 shown in the figure. The first terminal device 100 can be software in the form of programs and plugins, including: a display module 30, an acquisition module 31, and a diagnosis module 32. These modules are logical, so they can be combined arbitrarily or further split according to the functions to be implemented.

[0044] The functions of each module will be described below.

[0045] The vehicle diagnosis method provided by the embodiments of the present application will be described in conjunction with the exemplary application architecture of the communication system 10 provided by the embodiments of the present application.

[0046] Next, in conjunction with Figure 2 a vehicle diagnosis method provided by an embodiment of the present application will be described. Please refer to Figure 2 , Figure 2 which is a flowchart of a vehicle diagnosis method according to an embodiment of the present application. As shown in Figure 2 , the method includes:

[0047] Performing the following processing by the first terminal device:

[0048] Step S201, displaying a preset interaction interface, where the interaction interface includes target maintenance data corresponding to the target component and a target diagnosis link corresponding to the target component.

[0049] In this embodiment, the target maintenance data can be a repair help post, maintenance information, or maintenance case obtained after the first user searches for the target vehicle model, target vehicle brand, or target component.

[0050] As an example, the first user can enter the above-mentioned target vehicle model, target vehicle brand, or target component in the search box of the application software of the first terminal device. The application software can obtain maintenance data associated with the input characters from the local memory or the remote server of the first terminal device. The first user can screen these maintenance data and select the target maintenance data to enter the interaction interface corresponding to the target maintenance data. Among them, the target maintenance data can be the question content and reply content of the repair help post, maintenance information, or maintenance case, etc.

[0051] The interactive interface presented by the first terminal device may include a target diagnosis link, which is used to provide a target diagnosis menu configuration corresponding to the target component. After the first user clicks on the target diagnosis link, the first terminal device can generate and display the corresponding target diagnosis menu according to the target diagnosis menu configuration, eliminating the need for the user to frequently switch between the H5 page and menu debugging, thereby improving the efficiency of vehicle diagnosis.

[0052] Step S202: In response to the selection operation of the target diagnosis link, obtain the target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis menu configuration.

[0053] In this embodiment, the first user can perform operations such as mouse clicking or touch pressing on the target diagnosis link. After the first terminal device detects the above operations, it can respond to the selection operation of the target diagnosis link and request the target diagnosis menu configuration corresponding to the target diagnosis link from the local memory or server of the first terminal device.

[0054] It should be noted that the association relationship between the target diagnosis menu configuration and the target diagnosis link can be configured in the second terminal device. As an example, the second user can use the second terminal device to edit the target repair data related to the target component (for example, write repair cases, repair materials, or answer other users' car repair help posts). During or after the editing process, the second terminal device can request an initial diagnosis menu related to the target component from the server through an Application Programming Interface (API), where the initial diagnosis menu includes multiple target diagnosis functions, and each target diagnosis function corresponds to multiple target options.

[0055] Specifically, the second terminal device can perform the following processing: In response to the editing operation of the target repair data, request the initial diagnosis menu corresponding to the target component from the server, where the initial diagnosis menu includes multiple target diagnosis functions, and each target diagnosis function corresponds to multiple target options; in response to the editing operation of the target options corresponding to each target diagnosis function in the initial diagnosis menu, generate the target diagnosis link and the target diagnosis menu configuration, and associate the target diagnosis link with the target diagnosis menu configuration.

[0056] The second user can perform editing operations (such as selection, value filling, etc.) on one or more target options of one or more target diagnosis functions in the above initial diagnosis menu through the second terminal device. The second terminal device then records the various editing operations performed by the second user on the above initial diagnosis menu, generates the target diagnosis link and the target diagnosis menu configuration, and associates the target diagnosis link with the target diagnosis menu configuration.

[0057] In addition, the first user can not only view the target maintenance data related to the target component through the first terminal device, but also perform editing operations on the maintenance data related to other components through the first terminal device. The functions between the first terminal device and the second terminal device are not independent, but can exist simultaneously.

[0058] In one embodiment, "responding to the selection operation of the target diagnosis link and obtaining the target diagnosis menu configuration corresponding to the target component" in step S202 includes the following steps:

[0059] Step 1, responding to the selection operation of the target diagnosis link, obtaining the target diagnosis software configuration corresponding to the target diagnosis link, wherein the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis software configuration.

[0060] Step 2, determining whether the target diagnosis software corresponding to the target diagnosis software configuration is stored locally.

[0061] Step 3, when the target diagnosis software is stored locally, obtaining the target diagnosis menu configuration.

[0062] In this embodiment, when the second terminal device records the various editing operations performed by the second user on the above initial diagnosis menu to generate the target diagnosis link and the target diagnosis menu configuration, it can also record the target diagnosis software configuration used by the second user, wherein the target diagnosis software configuration records the type and version number of the target diagnosis software used by the second user.

[0063] The first terminal device can determine whether the target diagnosis software corresponding to the target diagnosis software configuration is stored in the local memory based on the above target diagnosis software configuration. If the target diagnosis software is not stored locally in the first terminal device, the first user can be prompted to purchase or download it; if the target diagnosis software is stored locally in the first terminal device but its version number does not match the version number recorded in the target diagnosis software configuration, the first user can be prompted to update or downgrade it.

[0064] In this way, it is possible to prevent the use of incorrect diagnostic software to perform diagnostic operations on the vehicle to be diagnosed, thereby improving the accuracy of vehicle diagnosis.

[0065] Step S203, displaying the target diagnosis menu based on the target diagnosis menu configuration, and performing diagnostic operations on the vehicle to be diagnosed through the target diagnosis menu.

[0066] In this embodiment, "displaying the target diagnosis menu based on the target diagnosis menu configuration" in step S203 includes the following steps:

[0067] Step 1: Load the target diagnostic menu configuration and obtain the name and path of the target diagnostic function corresponding to the target diagnostic menu configuration.

[0068] Step 2: Start the target diagnostic software and, based on the name and path of the target diagnostic function, control the target diagnostic software to generate and display the target diagnostic menu.

[0069] In this embodiment, when the target diagnostic software is locally stored in the first terminal device and the version number of the target diagnostic software matches the target diagnostic software configuration, the target diagnostic software can be controlled to generate and display the target diagnostic menu based on the name and path of the target diagnostic function.

[0070] However, in practical applications, there may be a situation where the target diagnostic software is locally stored in the first terminal device, but the version number of the target diagnostic software does not match the target diagnostic software configuration. In this case, if the target diagnostic software is directly started and controlled to generate and display the target diagnostic menu, the target diagnostic menu may be displayed incorrectly or fail to be displayed.

[0071] Therefore, in one embodiment, after step S203, the method further includes: when the target diagnostic menu fails to be displayed, request the target diagnostic menu corresponding to the target diagnostic menu configuration from the server and control the target diagnostic software to display the target diagnostic menu.

[0072] In this embodiment, the situation where the target diagnostic software is locally stored in the first terminal device, but the version number of the target diagnostic software does not match the target diagnostic software configuration is considered. In this case, the first terminal device can directly request the target diagnostic menu corresponding to the target diagnostic menu configuration from the server and control the target diagnostic software to display the target diagnostic menu.

[0073] However, in practical applications, the usage environment of the first terminal device may be an offline environment. In this case, the first terminal device cannot request the target diagnostic menu from the server, that is, it cannot control the target diagnostic software to display the target diagnostic menu.

[0074] Therefore, in another embodiment, after step S203, the method further includes: when the target diagnostic menu fails to be displayed, control the target diagnostic software to generate a local diagnostic menu; based on the name and path of the target diagnostic function, correct each diagnostic function in the local diagnostic menu to obtain the target diagnostic menu, and control the target diagnostic software to display the target diagnostic menu.

[0075] In this embodiment, the case where the usage environment of the first terminal device is an offline environment is considered. In this case, the target diagnostic software can be controlled to generate a local diagnostic menu, and the option settings of each diagnostic function in the local diagnostic menu may not match those of the target diagnostic menu. Therefore, based on the names and paths of the target diagnostic functions corresponding to the target diagnostic menu configuration, each diagnostic function in the local diagnostic menu can be corrected to obtain the target diagnostic menu, and the target diagnostic software can be controlled to display the target diagnostic menu.

[0076] In this way, considering various usage environments of the first terminal device, the environmental adaptability when using the first terminal device for vehicle diagnosis can be improved. In addition, since the case where the version number of the target diagnostic software locally stored in the first terminal device does not match the target diagnostic software configuration is also considered, the situation where the target diagnostic menu is displayed incorrectly (for example, the options of some diagnostic functions are garbled or the options are missing, etc.) or the display fails can be avoided, which can improve the accuracy when using the first terminal device for vehicle diagnosis and improve the user experience.

[0077] In one embodiment, "performing a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu" in step S203 includes the following steps:

[0078] Step 1, detecting the Bluetooth connection status with the vehicle to be diagnosed.

[0079] Step 2, when the Bluetooth connection status is connected, performing a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu.

[0080] In this embodiment, before the first terminal device performs a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu, the Bluetooth connection status between the first terminal device and the vehicle to be diagnosed can also be verified. In addition, the Bluetooth version number of the first terminal device can also be verified. If the Bluetooth connection status is not connected, the first user can be prompted to use the Bluetooth connection function of the first terminal device to control the first terminal device to establish a Bluetooth connection with the vehicle to be diagnosed; if the Bluetooth version number is relatively low, the first user can be prompted to use the update function of the first terminal device to update the Bluetooth.

[0081] In this way, the connection stability during subsequent diagnostic operations on the vehicle to be diagnosed can be improved, and the situation of frequent Bluetooth connections can be avoided, thereby improving the efficiency of vehicle diagnosis.

[0082] Through the above steps S201 to S203, an interactive interface is displayed through the first terminal device. The interactive interface includes target maintenance data corresponding to the target component and a target diagnosis link corresponding to the target component. The user can click on the target diagnosis link to obtain a target diagnosis menu configuration corresponding to the target component. The association relationship between the target diagnosis link and the target diagnosis menu configuration is configured by the second terminal device. Then, the first terminal device can display the target diagnosis menu based on the target diagnosis menu configuration and perform a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu. In this way, after the user consults the required maintenance data, there is no need to manually switch to the diagnostic software for menu debugging operations, avoiding the cumbersome switching operations between the H5 page and the diagnostic menu, thereby reducing the diagnostic time of the vehicle diagnostic device and improving the efficiency of vehicle diagnosis. Through the present application, the problem of low vehicle diagnosis efficiency caused by the cumbersome switching operations between the H5 page and the menu in the related art of vehicle diagnostic devices is solved, and the technical effect of improving the efficiency of vehicle diagnosis is achieved.

[0083] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The order of execution of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0084] Corresponding to the vehicle diagnosis method described in the above embodiments, Figure 3 The structural schematic diagram of a vehicle diagnosis device according to an embodiment of the present application is shown. For the sake of convenience of description, only the parts related to the embodiments of the present application are shown.

[0085] Please refer to Figure 3 , the vehicle diagnosis device 3 includes: a display module 30 for displaying a preset interactive interface, where the interactive interface includes target maintenance data corresponding to the target component and a target diagnosis link corresponding to the target component; an acquisition module 31 for, in response to a selection operation on the target diagnosis link, acquiring a target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis menu configuration; a diagnosis module 32 for displaying the target diagnosis menu based on the target diagnosis menu configuration and performing a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu.

[0086] In one embodiment, the acquisition module 31 is further configured to, in response to a selection operation on the target diagnosis link, acquire a target diagnosis software configuration corresponding to the target diagnosis link, where the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis software configuration; determine whether a target diagnosis software corresponding to the target diagnosis software configuration is stored locally; and acquire the target diagnosis menu configuration when the target diagnosis software is stored locally.

[0087] In one embodiment, the diagnostic module 32 is further configured to load a target diagnostic menu configuration, obtain the name and path of a target diagnostic function corresponding to the target diagnostic menu configuration; start the target diagnostic software, and based on the name and path of the target diagnostic function, control the target diagnostic software to generate and display the target diagnostic menu.

[0088] In one embodiment, the diagnostic module 32 is further configured to, when the display of the target diagnostic menu fails, request the target diagnostic menu corresponding to the target diagnostic menu configuration from the server, and control the target diagnostic software to display the target diagnostic menu.

[0089] In one embodiment, the diagnostic module 32 is further configured to, when the display of the target diagnostic menu fails, control the target diagnostic software to generate a local diagnostic menu; based on the name and path of the target diagnostic function, correct each diagnostic function in the local diagnostic menu to obtain the target diagnostic menu, and control the target diagnostic software to display the target diagnostic menu.

[0090] In one embodiment, the vehicle diagnostic device 3 further includes a writing module, configured to, in response to an editing operation on target maintenance data, request an initial diagnostic menu corresponding to a target component from the server, where the initial diagnostic menu includes a plurality of target diagnostic functions, and each target diagnostic function corresponds to a plurality of target options; in response to an editing operation on the target options corresponding to each target diagnostic function in the initial diagnostic menu, generate a target diagnostic link and a target diagnostic menu configuration, and associate the target diagnostic link with the target diagnostic menu configuration.

[0091] In one embodiment, the diagnostic module 32 is further configured to detect the Bluetooth connection status of the vehicle to be diagnosed; when the Bluetooth connection status is connected, perform a diagnostic operation on the vehicle to be diagnosed through the target diagnostic menu.

[0092] It should be noted that, for the information interaction, execution process, etc. between the above-mentioned devices / units, since they are based on the same concept as the method embodiments of the present application, their specific functions and the technical effects brought thereby can be specifically referred to in the method embodiment part, and will not be elaborated here.

[0093] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working processes of the units and modules in the above system can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0094] Figure 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As Figure 4 shown, the terminal device 4 includes: at least one processor 40 ( Figure 4 only one is shown in the figure), a processor, a memory 41, and a computer program 42 stored in the memory 41 and executable on at least one processor 40. When the processor 40 executes the computer program 42, the steps in any of the foregoing vehicle diagnosis method embodiments are implemented.

[0095] The terminal device 4 can be a computing device such as a desktop computer, a notebook, a palm computer, and a cloud server. The terminal device 4 may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art can understand that Figure 4 merely examples of the terminal device 4 do not constitute a limitation on the terminal device 4, and may include more or fewer components than shown in the figure, or combine some components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0096] The processor 40 may be a central processing unit (CPU), and the processor 40 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0097] The memory 41 may be an internal storage unit of the terminal device 4 in some embodiments, such as the hard disk or memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4 in other embodiments, such as a plug-in hard disk equipped on the terminal device 4, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. In other embodiments, the memory 41 may also include both the internal storage unit and the external storage device of the terminal device 4. The memory 41 is used to store an operating system, application programs, a BootLoader, data, and other programs, such as the program code of the computer program 42. The memory 41 may also be used to temporarily store data that has been output or will be output.

[0098] An embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned various embodiments of the vehicle diagnosis method can be implemented.

[0099] An embodiment of the present application provides a computer program product, and when the computer program product runs on a mobile terminal, the mobile terminal is enabled to implement the steps in the above-mentioned various embodiments of the vehicle diagnosis method when executed.

[0100] All or part of the processes in the above-mentioned embodiment methods of the present application can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps in the above-mentioned various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, an executable file, or some intermediate form, etc. The computer-readable medium can at least include: any entity or device capable of carrying the computer program code to the terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk, or an optical disc, etc.

[0101] In the above embodiments, the descriptions of the various embodiments have their own emphases. For parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0102] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0103] In the embodiments provided in this application, it should be understood that the disclosed device / network device and method can be implemented in other ways. For example, the device / network device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

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

[0105] The above embodiments are only used to illustrate the technical solutions of this application, rather than to limit it; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included in the protection scope of this application.

Claims

1. A vehicle diagnosis method, characterized in that, including: performing the following processes through a first terminal device: displaying a preset interaction interface, where the interaction interface includes target maintenance data corresponding to a target component and a target diagnosis link corresponding to the target component; in response to a selection operation on the target diagnosis link, obtaining a target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by a second terminal device to be associated with the target diagnosis menu configuration; displaying a target diagnosis menu based on the target diagnosis menu configuration, and performing a diagnosis operation on a vehicle to be diagnosed through the target diagnosis menu.

2. The method according to claim 1, characterized in that, Obtaining a target diagnosis menu configuration corresponding to the target component in response to a selection operation on the target diagnosis link includes: in response to a selection operation on the target diagnosis link, obtaining a target diagnosis software configuration corresponding to the target diagnosis link, where the target diagnosis link is configured by the second terminal device to be associated with the target diagnosis software configuration; determining whether a target diagnosis software corresponding to the target diagnosis software configuration is stored locally; when the target diagnosis software is stored locally, obtaining the target diagnosis menu configuration.

3. The method according to claim 2, wherein Displaying a target diagnosis menu based on the target diagnosis menu configuration includes: loading the target diagnosis menu configuration, and obtaining the name and path of a target diagnosis function corresponding to the target diagnosis menu configuration; starting the target diagnosis software, and controlling the target diagnosis software to generate and display the target diagnosis menu based on the name and path of the target diagnosis function.

4. The method according to claim 3, wherein After displaying a target diagnosis menu based on the target diagnosis menu configuration and performing a diagnosis operation on a vehicle to be diagnosed through the target diagnosis menu, the method further includes: when the display of the target diagnosis menu fails, requesting the target diagnosis menu corresponding to the target diagnosis menu configuration from a server, and controlling the target diagnosis software to display the target diagnosis menu.

5. The method according to claim 4, characterized in that, After displaying a target diagnosis menu based on the target diagnosis menu configuration and performing a diagnosis operation on a vehicle to be diagnosed through the target diagnosis menu, the method further includes: when the display of the target diagnosis menu fails, controlling the target diagnosis software to generate a local diagnosis menu; correcting each diagnosis function in the local diagnosis menu based on the name and path of the target diagnosis function to obtain the target diagnosis menu, and controlling the target diagnosis software to display the target diagnosis menu.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: performing the following processes through the second terminal device: in response to an edit operation on the target maintenance data, requesting an initial diagnosis menu corresponding to the target component from a server, where the initial diagnosis menu includes a plurality of target diagnosis functions, and each target diagnosis function corresponds to a plurality of target options; in response to an edit operation on the target options corresponding to each target diagnosis function in the initial diagnosis menu, generating the target diagnosis link and the target diagnosis menu configuration, and associating the target diagnosis link with the target diagnosis menu configuration.

7. The method according to any one of claims 1 to 5, characterized in that Performing a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu includes: Detecting the Bluetooth connection status of the vehicle to be diagnosed; When the Bluetooth connection status is connected, performing a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu.

8. A vehicle diagnostic device, characterized in that, Including: A display module for displaying a preset interaction interface, where the interaction interface includes target maintenance data corresponding to the target component and a target diagnosis link corresponding to the target component; An acquisition module for, in response to a selection operation on the target diagnosis link, acquiring a target diagnosis menu configuration corresponding to the target component, where the target diagnosis link is configured by a second terminal device to be associated with the target diagnosis menu configuration; A diagnosis module for displaying a target diagnosis menu based on the target diagnosis menu configuration and performing a diagnosis operation on the vehicle to be diagnosed through the target diagnosis menu.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, the vehicle diagnosis method described in any one of claims 1 to 7 is implemented.

10. A computer program product, characterized in that, Including a computer program, when the computer program is run, the vehicle diagnosis method described in any one of claims 1 to 7 is executed.

Images