Menu path query method and device, electronic equipment and storage medium

Abstract

The invention is suitable for the technical field of vehicle diagnosis, and provides a menu path query method and device, electronic equipment and a storage medium, and the menu path query method comprises the steps: obtaining a target diagnosis function name input by a user, and generating a menu path query request; sending a menu path query request to a server, wherein the menu path query request comprises a target diagnosis function name and version information of diagnosis software; target menu path information, returned by the server, of the target diagnosis function is received, the target menu path information is generated after the server conducts menu path retrieval on the basis of the name of the target diagnosis function and version information of the diagnosis software, and the target menu path information comprises multiple pieces of menu node information; the menu nodes are arranged according to the sequence from the top-level menu node to the menu node where the target diagnosis function is located. According to the scheme, the fluency and accuracy of diagnosis operation can be improved through an efficient menu path query method.

Description

Technical Field

[0001] The present application belongs to the field of vehicle diagnosis technology, and in particular relates to a menu path query method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of automotive electronics, vehicle diagnostic equipment has become an indispensable tool for repair shop technicians in the process of fault detection and repair. Most current mainstream diagnostic equipment uses a hierarchical menu structure. Technicians need to gradually enter the relevant diagnostic function path based on information such as vehicle model, system module, and fault type to perform operations such as code reading, code clearing, matching, and programming.

[0003] In actual use, experienced technicians can quickly locate the target function. However, novices or users unfamiliar with the specific vehicle system often take a long time to find the function path, and may even mistakenly enter other menus and then return, affecting operational efficiency. In addition, in some complex fault diagnosis scenarios, technicians may need to frequently switch between multiple functional modules. The repeated path-finding operation under the traditional menu structure increases the user burden and affects the overall diagnostic experience. Summary of the Invention

[0004] In view of this, embodiments of the present application provide a menu path query method, device, electronic device, and storage medium, which can improve the fluency and accuracy of diagnostic operations through an efficient menu path query method.

[0005] A first aspect of an embodiment of the present application provides a menu path query method, which is applied to a diagnostic terminal configured with diagnostic software, and the method includes:

[0006] Obtain the target diagnostic function name input by the user and generate a menu path query request;

[0007] Sending the menu path query request to the server, wherein the menu path query request includes the target diagnostic function name and the version information of the diagnostic software;

[0008] Receive the target menu path information of the target diagnostic function returned by the server, the target menu path information is generated by the server after performing a menu path retrieval based on the target diagnostic function name and the version information of the diagnostic software, the target menu path information includes multiple menu node information, and the multiple menu nodes are arranged in order from the top-level menu node to the menu node where the target diagnostic function is located.

[0009] In a possible implementation, the diagnostic software includes a menu query page, and the method further includes:

[0010] Displaying the received target menu path information on the menu query page and locating the target position of the target diagnostic function in the menu structure; or,

[0011] According to the target menu path information, a diagnostic function module corresponding to the target diagnostic function is automatically called to perform a diagnostic operation on the vehicle to be diagnosed, and the automatic calling is automatically triggered based on user settings or diagnostic process configuration.

[0012] In another possible implementation, the method further includes:

[0013] When packaging the diagnostic software, receiving and storing a menu data table corresponding to a current version of the diagnostic software, the menu data table including a plurality of diagnostic function names, menu identification information, and menu hierarchical structure information;

[0014] When the diagnostic software is uploaded and published to the server, the menu data table is imported into the server so that the server can classify and store the diagnostic software according to its version information and perform menu path retrieval according to the corresponding menu data table.

[0015] A second aspect of an embodiment of the present application provides a menu path query method, which is applied to a server, and the method includes:

[0016] In response to a menu path query request from a diagnostic terminal, extracting a target diagnostic function name to be queried and version information of diagnostic software in the diagnostic terminal;

[0017] Performing a menu path search based on the target diagnostic function name to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function, wherein the target menu path information includes information of a plurality of menu nodes, and the plurality of menu nodes are arranged in order from a top-level menu node to a menu node where the target diagnostic function is located;

[0018] The target menu path information is returned to the diagnosis terminal.

[0019] In one possible implementation, the method further includes:

[0020] Receive the menu data table uploaded by the diagnostic terminal, and classify and store the menu data table according to the version information of the diagnostic software. The menu data table includes multiple diagnostic function names, menu identification information and menu hierarchical structure information. The menu data table uniquely corresponds to the version information of the diagnostic software.

[0021] In a possible implementation, performing menu path retrieval based on the target diagnostic function name to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function includes:

[0022] determining a target menu data table according to the version information of the diagnostic software, wherein the target menu data table corresponds to the version information of the diagnostic software;

[0023] Searching the target menu data table according to the target diagnostic function name to be queried;

[0024] If the target diagnostic function name is not matched in the target menu data table, the query result returned is data matching null;

[0025] If a menu node corresponding to the target diagnostic function name is matched in the target menu data table, the representation information of the upper-level menu node is searched according to the identification information of the menu node until the top-level menu node is traced back to generate the target menu path information of the target diagnostic function.

[0026] A third aspect of an embodiment of the present application provides a menu path query device, which is applied to a diagnostic terminal configured with diagnostic software, and includes:

[0027] The request acquisition module is used to obtain the target diagnostic function name input by the user and generate a menu path query request;

[0028] a request sending module, configured to send the menu path query request to a server, wherein the menu path query request includes a target diagnostic function name and version information of the diagnostic software;

[0029] A path receiving module is used to receive the target menu path information of the target diagnostic function returned by the server, the target menu path information is generated by the server after performing a menu path retrieval based on the target diagnostic function name and the version information of the diagnostic software, the target menu path information includes multiple menu node information, and the multiple menu nodes are arranged in order from the top-level menu node to the menu node where the target diagnostic function is located.

[0030] In a possible implementation, the menu path query device further includes:

[0031] A display module is configured to display the received target menu path information on the menu query page and locate the target position of the target diagnostic function in the menu structure; or

[0032] A function calling module is used to automatically call a diagnostic function module corresponding to the target diagnostic function according to the target menu path information to perform a diagnostic operation on the vehicle to be diagnosed, and the automatic calling is automatically triggered based on user settings or diagnostic process configuration.

[0033] In another possible implementation, the menu path query device further includes:

[0034] a data table storage module for receiving and storing a menu data table corresponding to a current version of the diagnostic software when the diagnostic software is packaged, the menu data table including a plurality of diagnostic function names, menu identification information, and menu hierarchical structure information;

[0035] The data table import module is used to import the menu data table into the server when the diagnostic software is uploaded and published to the server, so that the server can classify and store the diagnostic software according to its version information and perform menu path retrieval according to the corresponding menu data table.

[0036] A fourth aspect of the embodiments of the present application provides a menu path query device, which is applied to a server, and includes:

[0037] a request response module, configured to extract the target diagnostic function name to be queried and the version information of the diagnostic software in the diagnostic terminal in response to a menu path query request from the diagnostic terminal;

[0038] a path generation module, configured to perform menu path retrieval based on the name of the target diagnostic function to be queried and the version information of the diagnostic software, and generate target menu path information of the target diagnostic function, wherein the target menu path information includes information of a plurality of menu nodes, and the plurality of menu nodes are arranged in order from a top-level menu node to a menu node where the target diagnostic function is located;

[0039] The path returning module is used to return the target menu path information to the diagnosis terminal.

[0040] In a possible implementation, the menu path query device further includes:

[0041] A data table receiving module is used to receive the menu data table uploaded by the diagnostic terminal, and classify and store the menu data table according to the version information of the diagnostic software. The menu data table includes multiple diagnostic function names, menu identification information and menu hierarchical structure information. The menu data table uniquely corresponds to the version information of the diagnostic software.

[0042] In a possible implementation, the path generation module includes:

[0043] a data table determining unit, configured to determine a target menu data table according to the version information of the diagnostic software, wherein the target menu data table corresponds to the version information of the diagnostic software;

[0044] A retrieval unit, configured to retrieve the target menu data table according to the target diagnostic function name to be queried;

[0045] A first judgment unit is configured to return a query result indicating that the target diagnostic function name is empty if no match is found in the target menu data table;

[0046] The second judgment unit is used to search for the representation information of the upper-level menu node according to the identification information of the menu node if a menu node corresponding to the target diagnostic function name is matched in the target menu data table, until the top-level menu node is traced back to generate the target menu path information of the target diagnostic function.

[0047] A fifth aspect of an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the menu path query method described in the first or second aspect above when executing the computer program.

[0048] The seventh aspect of an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the menu path query method described in the first aspect above, or when the computer program is executed by a processor, it implements the menu path query method described in the second aspect above.

[0049] An eighth aspect of an embodiment of the present application provides a computer program product, which, when running on an electronic device, enables the electronic device to execute the menu path query method described in the first aspect above, or when running on a server, enables the server to execute the menu path query method described in the first aspect above.

[0050] Compared with the prior art, the present embodiment has the following advantages: the present embodiment obtains the target diagnostic function name input by the user, generates a menu path query request, and sends the menu path query request to the server. After receiving the query request, the server performs a menu path search based on the target diagnostic function name and the version information of the diagnostic software, generates target menu path information from the top-level menu node to the target function menu node, and returns it to the diagnostic terminal. By receiving the target menu path information, the diagnostic terminal can avoid the user's repeated search in multiple levels of complex menus, thereby improving the fluency and accuracy of diagnostic operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order 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 descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0052] Figure 1 This is a structural diagram of a menu path query system provided in Example 1 of the present application;

[0053] Figure 2 This is a flowchart of a menu path query method provided in Example 2 of the present application;

[0054] Figure 3 This is an example diagram of the menu data table;

[0055] Figure 4 This is a flowchart of a menu path query method provided in Example 3 of the present application;

[0056] Figure 5 This is a structural diagram of a menu path query device provided in Example 4 of the present application;

[0057] Figure 6 This is a structural diagram of a menu path query device provided in Example 5 of the present application;

[0058] Figure 7 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may 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 obscuring the description of the present application with unnecessary detail.

[0060] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0061] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0062] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0063] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0064] It should be understood that the size of the serial numbers of each step in this embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of this application.

[0065] With the rapid development of automotive electronics, vehicle diagnostic equipment has become an indispensable tool for repair shop technicians in the process of fault detection and repair. Most current mainstream diagnostic equipment uses a hierarchical menu structure. Technicians need to gradually enter the relevant diagnostic function path based on information such as vehicle model, system module, and fault type to perform operations such as code reading, code clearing, matching, and programming.

[0066] In actual use, experienced technicians can quickly locate the target function. However, novices or users unfamiliar with the specific vehicle system often take a long time to find the function path, and may even mistakenly enter other menus and then return, affecting operational efficiency. In addition, in some complex fault diagnosis scenarios, technicians may need to frequently switch between multiple functional modules. The repeated path-finding operation under the traditional menu structure increases the user burden and affects the overall diagnostic experience.

[0067] Based on this, the embodiments of the present application propose a menu path query method, device, electronic device and storage medium. When querying the target menu path of the target diagnostic function, the target diagnostic function name input by the user is first obtained to generate a menu path query request. Secondly, the menu path query request is sent to the server. After receiving the query request, the server performs a menu path search based on the target diagnostic function name and the version information of the diagnostic software, generates target menu path information from the top-level menu node to the target function menu node, and returns it to the diagnostic terminal. Finally, the diagnostic terminal can receive the target menu path information, avoiding the user's repeated searches in multi-level complex menus, and improving the fluency and accuracy of diagnostic operations.

[0068] See Figure 1 , Figure 1 This is a structural diagram of a menu path query system provided in Example 1 of the present application.

[0069] The menu path query system includes: a server and M diagnostic terminals, where M is an integer greater than zero. The server is connected to the M diagnostic terminals via the Internet of Things to achieve data and / or signaling interaction.

[0070] The diagnostic terminal may refer to a device that can run diagnostic programs, communicate with the vehicle, obtain vehicle information, and write data. Specifically, it may include dedicated diagnostic instruments, computers or tablet devices equipped with VCI (vehicle communication interface), personal digital assistants (PDA), mobile Internet devices (MID), car computers, and other electronic devices, which are not limited in the embodiments of the present invention.

[0071] The menu path query system can be used to implement the menu path query method provided in the embodiments of the present application. For example, the diagnostic terminal obtains the target diagnostic function name input by the user, constructs a menu path query request, and attaches the version information of the current diagnostic software, and sends the request to the server. After receiving the menu path query request from the diagnostic terminal, the server first parses the request content, extracts the target diagnostic function name and the version information of the diagnostic software, and then performs a path search based on the extracted function name and version information in the menu path database preset in the server.

[0072] During the search process, the server locates the menu node for the target diagnostic function, starting from the top-level menu and following the menu hierarchy, based on the menu structure corresponding to different versions of the diagnostic software. The server then generates target menu path information, which includes information about multiple menu nodes from the top-level menu node to the target diagnostic function menu node. After generating the target menu path information, the server returns it to the diagnostic terminal.

[0073] After receiving the target menu path information returned by the server, the diagnostic terminal can display this path information on the user interface, helping users quickly understand and locate the menu location of the target diagnostic function in the diagnostic software. Based on the menu path information returned by the system, users can more efficiently navigate to the corresponding diagnostic function interface, thereby improving the convenience and accuracy of diagnostic operations.

[0074] based on Figure 1 The system structure shown in Figure 2 , Figure 2 This is a flowchart of a menu path query method provided in Example 2 of the present application. This method is applied to a diagnostic terminal equipped with diagnostic software, such as Figure 2 As shown, the menu path query method may include the following steps:

[0075] Step 201: Obtain the target diagnostic function name input by the user and generate a menu path query request.

[0076] In the embodiment of the present application, the diagnostic terminal refers to a hardware device that is installed with diagnostic software and is used to perform vehicle fault diagnosis and repair operations. Specifically, it can be implemented using a mobile terminal or dedicated diagnostic equipment with communication capabilities, serving as an interactive entrance for users to initiate query requests and receive path information.

[0077] The target diagnostic function name refers to the identifier of the function module to be queried, entered by the user in the diagnostic software interface. This can be implemented using a text input box to specify the specific diagnostic function the user wants to locate. For example, entering "tachometer diagnostics" on the menu query page of the diagnostic software generates a menu path query request for "tachometer diagnostics."

[0078] The menu path query request refers to a data packet sent by the diagnostic terminal to the server, which is used to trigger the path retrieval process on the server side.

[0079] In an embodiment of the present application, a menu path query request is generated based on a target diagnostic function name input by a user.

[0080] Step 202: Send the menu path query request to the server.

[0081] Among them, the menu path query request includes the target diagnostic function name and the version information of the diagnostic software. Specifically, the version information of the diagnostic software refers to the version identifier corresponding to the diagnostic software running by the current diagnostic terminal, which can be implemented in a digital number or date coding format. For example, the version identifier is V50.20, which is used to match the corresponding version of the menu data table on the server side.

[0082] In the embodiment of the present application, the menu path query request can be implemented by encapsulating the HTTP protocol or a custom communication protocol.

[0083] Step 203: Receive target menu path information of the target diagnostic function returned by the server.

[0084] In the embodiment of the present application, the target menu path information is generated by the server after performing a menu path search based on the target diagnostic function name and the version information of the diagnostic software.

[0085] Among them, menu path retrieval refers to the operation of the server querying the corresponding path in the pre-stored data structure according to the name of the target diagnostic function and the version information of the diagnostic software. It can be implemented by relational database query or tree structure traversal algorithm to quickly determine the position of the target diagnostic function in the multi-layer menu.

[0086] Among them, the target menu path information refers to the hierarchical path description data returned by the server, which contains the complete path from the top-level menu to the target function node. It can be implemented using a JSON array or XML node sequence to intuitively display the navigation order of the function entrance on the diagnostic terminal.

[0087] Among them, menu node information refers to the data description of each hierarchical unit that constitutes the menu path, including the node name, identifier, and upper and lower level association relationships. It can be implemented in key-value pairs or structure formats to restore the logical relationship of the menu structure.

[0088] In an embodiment of the present application, the server-side path retrieval is triggered by the user inputting the function name and version information, and the structured menu path data is directly returned, avoiding the operation of manually searching the menu level by level, significantly reducing the operation complexity and improving the diagnosis efficiency.

[0089] The following example describes the specific implementation process of the above solution:

[0090] The diagnostic terminal is equipped with diagnostic software, which includes a menu query page. On this page, the user enters the name of the desired diagnostic function, such as "wheel speed sensor calibration." The system receives this input and automatically extracts the current diagnostic software version, such as "V50.20." Based on these two pieces of information, the system generates a menu path query request.

[0091] This request is sent over the network to the remote server. Upon receiving the request, the server first locates the corresponding menu data table based on the version information "V50.20." Within this table, the system searches for the "Wheel Speed ​​Sensor Calibration" function and finds its menu node. The system then searches upwards through the parent menu nodes until it reaches the top-level menu.

[0092] Assuming that the search results show that the function is located in a four-level menu structure, the server generates the following target menu path information:

[0093] "Vehicle Systems > Chassis > Braking System > ABS > Wheel Speed ​​Sensor Calibration"

[0094] This path information is returned to the diagnostic terminal. The terminal displays the complete path on the menu query page, allowing users to quickly locate the desired diagnostic function. Alternatively, the system automatically calls the "Wheel Speed ​​Sensor Calibration" function module based on pre-set configurations, directly entering the operation interface.

[0095] It should be understood that the target diagnostic function name may be replaced by an identifier, for example, the ID of the target diagnostic function, that is, the user may enter the ID corresponding to “wheel speed sensor calibration” (0x0000019).

[0096] In a possible implementation, the menu path query method further includes:

[0097] Display the received target menu path information on the menu query page and locate the target position of the target diagnostic function in the menu structure; or

[0098] According to the target menu path information, the diagnostic function module corresponding to the target diagnostic function is automatically called to perform diagnostic operations on the vehicle to be diagnosed. The automatic call is automatically triggered based on user settings or diagnostic process configuration.

[0099] Specifically, the menu query page can display the target menu path information in a tree structure, expanding step by step from the top-level menu node to the menu node where the target diagnostic function is located. For example, for the target menu path of "Engine - Fault Code - Read Fault Code", the complete menu tree can be displayed on the left side of the page, with each node along the path highlighted.

[0100] Furthermore, based on the target menu path information, the system automatically calls the diagnostic function module corresponding to the target diagnostic function to perform diagnostic operations on the vehicle being diagnosed. This automatic call is triggered based on user settings or diagnostic process configuration. For example, the user can enable the "Quick Diagnosis" function in the diagnostic software settings. Upon receiving the target menu path information, the system automatically calls the corresponding diagnostic function module, eliminating the need for the user to manually click to access it.

[0101] In a possible implementation, the menu path query method further includes:

[0102] When packaging the diagnostic software, receiving and storing a menu data table corresponding to the current version of the diagnostic software, the menu data table including a plurality of diagnostic function names, menu identification information, and menu hierarchical structure information;

[0103] When the diagnostic software is uploaded and published to the server, the menu data table is imported into the server so that the server can classify and store the diagnostic software according to its version information and perform menu path retrieval according to the corresponding menu data table.

[0104] The operation of receiving and storing the menu data table corresponding to the current version is completed during the software packaging phase. For example, the compiled menu configuration data is converted into a structured table format through an automated script and archived locally with the version number as the file name. The process of importing the menu data table to the server is implemented during the software release phase. Specifically, the locally stored menu data table can be uploaded to the server database through an interface call. The database creates an independent storage partition based on the version information. For example, the menu data table with version number V50.20 is stored in a data table named after the version number. The menu hierarchical relationship is recorded in the menu data table through a tree structure. For example, the parent-child node association field is used to describe the parent-child relationship of each menu node.

[0105] Specifically, an example diagram of the menu data table can be found in Figure 3 .

[0106] Specifically, during the diagnostic software packaging process, the integrated development environment automatically extracts the menu hierarchy structure of the current version of the software configuration, and generates a menu data table according to a preset format for the diagnostic function name, unique identifier, and parent node identifier corresponding to each menu node. The data table is bound to the software installation package through the version number to ensure the consistency of version information during subsequent uploads. When the software is released to the server, the upload module transfers the menu data table and the version number to the server storage module. The server creates an independent data storage unit based on the version number, such as creating a data table for each version in a relational database. In the subsequent menu path query process, the server accurately matches the corresponding data table based on the version number provided by the diagnostic terminal, retrieves the node identifier corresponding to the target diagnostic function name in the table, and traverses up along the parent-child node relationship chain to the root node to generate a complete menu path. This solution avoids the problem of different versions of menu structures interfering with each other through a versioned data isolation mechanism, while improving path retrieval efficiency by using pre-stored structured data tables.

[0107] See also Figure 4 , Figure 4This is a flowchart of a menu path query method provided in Example 3 of this application. The method is applied to a server, such as Figure 4 As shown, the menu path query method may include the following steps:

[0108] Step 401, in response to a menu path query request from a diagnostic terminal, extract the target diagnostic function name to be queried and the version information of the diagnostic software in the diagnostic terminal;

[0109] In an embodiment of the present application, the operation of extracting version information is implemented by parsing the version identification field in the request message, and the version identification field corresponds to the version number generated when the diagnostic software is packaged.

[0110] Step 402: performing menu path retrieval based on the target diagnostic function name to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function;

[0111] In this embodiment of the present application, when searching for a menu path, a pre-stored menu data table containing a mapping relationship between diagnostic function names and menu node hierarchies is matched based on version information. When generating target menu path information, a recursive algorithm is used to traverse upward from the target node to the top-level node, forming an ordered node sequence.

[0112] For example, if the target diagnostic function is located in the third-level menu, the path chain records the first-level menu name, the second-level menu name and the target function name in sequence, and finally generates the target menu path information.

[0113] In a possible implementation, the menu path query method further includes:

[0114] Receive the menu data table uploaded by the diagnostic terminal, and classify and store the menu data table according to the version information of the diagnostic software. The menu data table includes multiple diagnostic function names, menu identification information, and menu hierarchical structure information. The menu data table uniquely corresponds to the version information of the diagnostic software.

[0115] In a possible implementation, menu path retrieval is performed based on the name of the target diagnostic function to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function, including:

[0116] Determine the target menu data table according to the version information of the diagnostic software, wherein the target menu data table corresponds to the version information of the diagnostic software;

[0117] Search the target menu data table according to the target diagnostic function name to be queried;

[0118] If the target diagnostic function name is not matched in the target menu data table, the query result returned is data matching empty;

[0119] If a menu node corresponding to the target diagnostic function name is matched in the target menu data table, the representation information of its upper-level menu node is searched according to the identification information of the menu node until the top-level menu node is traced back to generate the target menu path information of the target diagnostic function.

[0120] Specifically, when searching the target menu data table, a keyword matching algorithm is used to compare the target diagnostic function name with the diagnostic function name fields stored in the data table one by one. The keyword matching algorithm supports fuzzy query or precise query mode. When the target diagnostic function name is not matched, a query result message containing a null value identifier is generated and returned to the diagnostic terminal to avoid occupying system resources due to invalid queries. After matching the target diagnostic function name, the parent node pointer of the menu node identification information is recursively called to traverse the menu hierarchy level by level until the parent node pointer is empty and it is determined that the top-level menu node has been reached. During the traversal process, the identification information of each node is stored in the path information queue in order.

[0121] For example, the target menu data table is determined based on the version information of the diagnostic software. The target menu data table corresponds to the version information of the diagnostic software. For example, for diagnostic software with version number V50.20, the corresponding menu data table BMW_memudata_50.20.xlsx is selected.

[0122] According to the target diagnostic function name to be queried, the target menu data table is searched. Specifically, an SQL statement can be used to search for records matching the target diagnostic function name in the menu data table.

[0123] If the target diagnostic function name is not matched in the target menu data table, the query result returned is "Data Match NULL". In this case, a "No relevant function found" prompt message can be displayed to the user.

[0124] If a menu node corresponding to the target diagnostic function name is found in the target menu data table, the target menu path information for the target diagnostic function is generated by searching the menu node's parent menu node based on its identification information, tracing back to the top-level menu node. Furthermore, a recursive algorithm can be used to trace back the menu path, thereby forming a complete path from the top-level menu to the target function.

[0125] Through the above technical solution, this application can quickly locate the location of the target diagnostic function in the menu structure, reducing the user's search time in multi-level menus. At the same time, version matching ensures the accuracy of menu paths across different versions of diagnostic software, improving the efficiency and accuracy of diagnostic operations. In addition, this solution can also adapt to version updates of the diagnostic software, ensuring the continued availability of the menu path query function.

[0126] Step 403: Return the target menu path information to the diagnosis terminal.

[0127] In an embodiment of the present application, the target menu path information can be packaged into a data packet, encapsulated via the HTTP protocol or a custom communication protocol, and transmitted to the diagnostic terminal. The diagnostic terminal can parse it based on the agreed protocol and obtain the target menu path information.

[0128] See also Figure 5 , shows a structural diagram of a menu path query device provided in Example 4 of the present application. For the sake of convenience, only the parts related to the example of the present application are shown.

[0129] The menu path query device 500 may specifically include the following modules:

[0130] The request acquisition module 501 is used to obtain the target diagnostic function name input by the user and generate a menu path query request;

[0131] The request sending module 502 is used to send a menu path query request to the server, where the menu path query request includes the target diagnostic function name and the version information of the diagnostic software;

[0132] The path receiving module 503 is used to receive the target menu path information of the target diagnostic function returned by the server. The target menu path information is generated by the server after performing a menu path retrieval based on the target diagnostic function name and the version information of the diagnostic software. The target menu path information includes multiple menu node information, and the multiple menu nodes are arranged in order from the top-level menu node to the menu node where the target diagnostic function is located.

[0133] In the embodiment of the present application, the menu path query device 500 further includes:

[0134] A display module is used to display the received target menu path information on the menu query page and locate the target position of the target diagnostic function in the menu structure; or

[0135] The function calling module is used to automatically call the diagnostic function module corresponding to the target diagnostic function according to the target menu path information to perform diagnostic operations on the vehicle to be diagnosed. The automatic call is automatically triggered based on user settings or diagnostic process configuration.

[0136] In the embodiment of the present application, the menu path query device 500 further includes:

[0137] A data table storage module is used to receive and store a menu data table corresponding to the current version of the diagnostic software when the diagnostic software is packaged, the menu data table including a plurality of diagnostic function names, menu identification information and menu hierarchical structure information;

[0138] The data table import module is used to import the menu data table into the server when the diagnostic software is uploaded and published to the server, so that the server can classify and store the diagnostic software according to its version information and perform menu path retrieval based on the corresponding menu data table.

[0139] The menu path query device 500 provided in the embodiment of the present application can be applied to the menu path query method provided in the aforementioned embodiment 1. For details, please refer to the description of the menu path query method provided in the aforementioned embodiment 1, which will not be repeated here.

[0140] See also Figure 6 , shows a structural diagram of a menu path query device provided in Example 5 of the present application. For the sake of convenience, only the parts related to the embodiment of the present application are shown.

[0141] The menu path query device 600 may specifically include the following modules:

[0142] The request response module 601 is used to respond to the menu path query request from the diagnostic terminal and extract the target diagnostic function name to be queried and the version information of the diagnostic software in the diagnostic terminal;

[0143] Path generation module 602, configured to perform menu path retrieval based on the target diagnostic function name to be queried and the version information of the diagnostic software, and generate target menu path information of the target diagnostic function, wherein the target menu path information includes information of multiple menu nodes, and the multiple menu nodes are arranged in order from the top menu node to the menu node where the target diagnostic function is located;

[0144] The path returning module 603 is used to return the target menu path information to the diagnosis terminal.

[0145] In the embodiment of the present application, the menu path query device 600 further includes:

[0146] The data table receiving module is used to receive the menu data table uploaded by the diagnostic terminal and classify and store the menu data table according to the version information of the diagnostic software. The menu data table includes multiple diagnostic function names, menu identification information and menu hierarchical structure information. The menu data table uniquely corresponds to the version information of the diagnostic software.

[0147] In the embodiment of the present application, the path generation module 602 includes:

[0148] a data table determining unit, for determining a target menu data table according to the version information of the diagnostic software, wherein the target menu data table corresponds to the version information of the diagnostic software;

[0149] A retrieval unit, configured to retrieve a target menu data table according to a target diagnostic function name to be queried;

[0150] The first judgment unit is configured to return a query result indicating that the target diagnostic function name is empty if no match is found in the target menu data table;

[0151] The second judgment unit is used to search for the representation information of the upper-level menu node according to the identification information of the menu node if a menu node corresponding to the target diagnostic function name is matched in the target menu data table, until the top-level menu node is traced back to generate the target menu path information of the target diagnostic function.

[0152] The menu path query device 600 provided in the embodiment of the present application can be applied to the menu path query method provided in the aforementioned embodiment 2. For details, please refer to the description of the menu path query method provided in the aforementioned embodiment 2, which will not be repeated here.

[0153] Figure 7 Schematic diagram of the structure of the electronic device provided in the embodiment of the present application. Figure 7 As shown, the electronic device 700 of this embodiment includes: at least one processor 710 ( Figure 7 Only one is shown in the figure) a processor, a memory 720, and a computer program 721 stored in the memory 720 and executable on the at least one processor 710, wherein the processor 710 implements the steps in the first embodiment of the above-mentioned menu path query method when executing the computer program 721, or implements the steps in the second embodiment of the above-mentioned menu path query method when executing the computer program 721.

[0154] The electronic device 700 may be a computing device such as a desktop computer, a notebook, or a palmtop computer. The electronic device may include, but is not limited to, a processor 710 and a memory 720. It will be understood by those skilled in the art that Figure 7 This is merely an example of the electronic device 700 and does not constitute a limitation on the electronic device 700 . The electronic device 700 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0155] The processor 710 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

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

[0157] In a specific implementation, the processor 710, memory 720, and computer program 721 described in the embodiments of the present application can execute the present application. Figure 2 and Figure 3 The embodiment of the provided menu path query method will not be described in detail here.

[0158] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, 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. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0159] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0160] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0161] In the embodiments provided in the present application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0163] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0164] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0165] The present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed through a computer program product. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments when executing.

[0166] The above embodiments are intended only to illustrate the technical solutions of the present application and are not intended to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they may still modify the technical solutions described in the above embodiments or replace some of the technical features therein with equivalents; and such modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application and should be included within the scope of protection of the present application.

Claims

1. A menu path query method, characterized in that: Applied to a diagnostic terminal equipped with diagnostic software, the method includes: Obtain the target diagnostic function name input by the user and generate a menu path query request; Sending the menu path query request to the server, wherein the menu path query request includes the target diagnostic function name and the version information of the diagnostic software; Receive the target menu path information of the target diagnostic function returned by the server, the target menu path information is generated by the server after performing a menu path retrieval based on the target diagnostic function name and the version information of the diagnostic software, the target menu path information includes multiple menu node information, and the multiple menu nodes are arranged in order from the top-level menu node to the menu node where the target diagnostic function is located.

2. The menu path query method according to claim 1, wherein: The diagnostic software includes a menu query page, and the method further includes: Displaying the received target menu path information on the menu query page and locating the target position of the target diagnostic function in the menu structure; or, According to the target menu path information, a diagnostic function module corresponding to the target diagnostic function is automatically called to perform a diagnostic operation on the vehicle to be diagnosed, and the automatic calling is automatically triggered based on user settings or diagnostic process configuration.

3. The menu path query method according to claim 1, wherein: The method further comprises: When packaging the diagnostic software, receiving and storing a menu data table corresponding to a current version of the diagnostic software, the menu data table including a plurality of diagnostic function names, menu identification information, and menu hierarchical structure information; When the diagnostic software is uploaded and published to the server, the menu data table is imported into the server so that the server can classify and store the diagnostic software according to its version information and perform menu path retrieval according to the corresponding menu data table.

4. A menu path query method, characterized in that: Applied to a server, the method includes: In response to a menu path query request from a diagnostic terminal, extracting a target diagnostic function name to be queried and version information of diagnostic software in the diagnostic terminal; Performing a menu path search based on the target diagnostic function name to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function, wherein the target menu path information includes information of a plurality of menu nodes, and the plurality of menu nodes are arranged in order from a top-level menu node to a menu node where the target diagnostic function is located; The target menu path information is returned to the diagnosis terminal.

5. The menu path query method according to claim 4, wherein: The method further comprises: Receive the menu data table uploaded by the diagnostic terminal, and classify and store the menu data table according to the version information of the diagnostic software. The menu data table includes multiple diagnostic function names, menu identification information and menu hierarchical structure information. The menu data table uniquely corresponds to the version information of the diagnostic software.

6. The menu path query method according to claim 5, wherein: The step of performing menu path retrieval based on the target diagnostic function name to be queried and the version information of the diagnostic software to generate target menu path information of the target diagnostic function includes: determining a target menu data table according to the version information of the diagnostic software, wherein the target menu data table corresponds to the version information of the diagnostic software; Searching the target menu data table according to the target diagnostic function name to be queried; If the target diagnostic function name is not matched in the target menu data table, the query result returned is data matching null; If a menu node corresponding to the target diagnostic function name is matched in the target menu data table, the representation information of the upper-level menu node is searched according to the identification information of the menu node until the top-level menu node is traced back to generate the target menu path information of the target diagnostic function.

7. A menu path query device, characterized in that: Applicable to a diagnostic terminal equipped with diagnostic software, the device comprises: The request acquisition module is used to obtain the target diagnostic function name input by the user and generate a menu path query request; a request sending module, configured to send the menu path query request to a server, wherein the menu path query request includes a target diagnostic function name and version information of the diagnostic software; A path receiving module is used to receive the target menu path information of the target diagnostic function returned by the server, the target menu path information is generated by the server after performing a menu path retrieval based on the target diagnostic function name and the version information of the diagnostic software, the target menu path information includes multiple menu node information, and the multiple menu nodes are arranged in order from the top-level menu node to the menu node where the target diagnostic function is located.

8. A menu path query device, characterized in that: Applied to a server, the device includes: a request response module, configured to extract the target diagnostic function name to be queried and the version information of the diagnostic software in the diagnostic terminal in response to a menu path query request from the diagnostic terminal; a path generation module, configured to perform menu path retrieval based on the name of the target diagnostic function to be queried and the version information of the diagnostic software, and generate target menu path information of the target diagnostic function, wherein the target menu path information includes information of a plurality of menu nodes, and the plurality of menu nodes are arranged in order from a top-level menu node to a menu node where the target diagnostic function is located; The path returning module is used to return the target menu path information to the diagnosis terminal.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 or claims 4 to 6 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 or claims 4 to 6 are implemented.

Images