Interface display method and device

Abstract

The application is suitable for the technical field of vehicle diagnosis, and provides an interface display method and device. The method is applied to a first device, the first device comprises a vehicle diagnosis application, the vehicle diagnosis application comprises X application functions, and the method comprises the following steps: in response to a first starting instruction of the vehicle diagnosis application, a first request is sent to a server, the first request is used for requesting interface data and switch data of the vehicle diagnosis application; the interface data indicates that Y controls in X controls corresponding to the X application functions are displayed at the same level, Y is less than or equal to X, and the switch data is used for indicating that a first control in the X controls is not displayed at the level; a first response sent by the server is received, the first response comprises the interface data and the switch data; and a first interface is displayed according to the interface data and the switch data, the first interface comprises a second control, and the second control is any one or more of the Y controls which are different from the first control. The interface display method can improve the user experience of the vehicle diagnosis application.

Description

Technical Field

[0001] This application belongs to the field of vehicle diagnostic technology, and in particular relates to an interface display method and device. Background Technology

[0002] Vehicle diagnostic applications are software applications used for vehicle diagnosis. For example, vehicle diagnostic equipment or mobile devices can install vehicle diagnostic applications. However, these applications are often immature, leading to frequent issues such as the inability to access diagnostic functions, thus impacting user experience. Therefore, improving the user experience of vehicle diagnostic applications has become a pressing technical problem. Summary of the Invention

[0003] This application provides an interface display method and apparatus that can improve the user experience of vehicle diagnostic applications.

[0004] In a first aspect, embodiments of this application provide an interface display method applied to a first device. The first device includes a vehicle diagnostic application, which includes X application functions, where X is an integer greater than or equal to 1. The method includes: responding to a user's first start command for the vehicle diagnostic application, sending a first request to a server, the first request being used to request interface data and switch data of the vehicle diagnostic application; the interface data indicating that Y controls from X controls corresponding to the X application functions are displayed at the same level, where Y ≤ X, and the switch data indicating that the first control from the X controls is not displayed at the level; receiving a first response sent by the server, the first response including the interface data and the switch data; and displaying a first interface based on the interface data and the switch data, wherein the first interface includes a second control, the second control being any one or more of the Y controls that are different from the first control.

[0005] In this embodiment, the first device sends a first request to the server, and the received first response includes not only interface data but also switch data. The interface data indicates that Y controls from the X controls corresponding to X application functions should be displayed at the same level. This can be understood as Y representing the total number of application functions and the total number of controls for all application functions at the same level. The switch data indicates that if the first control from the X controls is not displayed at the level, the first interface displayed by combining the interface data and the switch data includes any one or more second controls from the Y controls that are different from the first control. Thus, the first device can flexibly control whether to display controls corresponding to application functions in the first interface through the switch data, and thereby flexibly control whether to provide the user with each application function in the first interface.

[0006] In one possible implementation of the first aspect, the interface data is an interface configuration file, which is used to configure at least one of the following: the order of Y controls in the same level, the size of each control, and the icon of each control; the switch data is a switch configuration file.

[0007] Compared to releasing a new version of the vehicle diagnostic application to update the entire application, this embodiment allows users to flexibly and efficiently update interface and / or switch data simply by modifying the aforementioned interface configuration file and / or switch configuration file. This significantly improves the flexibility and maintainability of modifying interface and / or switch data.

[0008] In one possible implementation of the first aspect, the interface data includes: menu interface data of at least one level, the first interface including an i-th level menu interface, the method further includes: in response to a user triggering a second control of the first interface, displaying the i+1-th level menu interface when the second control is associated with an i+1-th level menu interface; and launching an application function when the second control is associated with an application function, the application function including a vehicle diagnostic function.

[0009] In this embodiment, based on the hierarchical structure of the vehicle diagnostic application's functions, the interface data is displayed in a hierarchical interface format. Each hierarchical menu interface's controls can trigger access to the next level menu interface or launch application functions. This hierarchical interface offers stronger functional logic, facilitates user operation, and improves the user experience.

[0010] In one possible implementation of the first aspect, the switch data further indicates the target processing flow of the application function, the target processing flow being one of at least one candidate processing flow; when the second control is associated with the application function, starting the application function includes: when the second control is associated with the application function, determining the target processing flow corresponding to the application function based on the switch data; and executing the target processing flow.

[0011] For any application function, the hierarchical design of specifying the target processing flow among the multiple candidate processing flows allows the interface display method of this application embodiment to be flexibly switched in different hardware environments, network environments and other scenarios.

[0012] In one possible implementation of the first aspect, when the second control is associated with an application function, launching the application function includes at least one of the following: when the second control is associated with a functional module of the application function, launching the functional module; when the second control is associated with a local software package of the application function, launching the local software package of the application function; when the second control is associated with a front-end page of the application function, jumping to the front-end page; when the second control is associated with a third-party software package of the application function, launching the third-party software package of the application function.

[0013] In this embodiment, the vehicle diagnostic application utilizes multiple technology stacks to achieve diverse application functions, enabling it to efficiently provide a variety of services. For example, some functions are implemented through complete functional modules. When these modules are used for vehicle diagnostics, they possess highly complex technical logic specific to the vehicle diagnostic field, exhibiting high professionalism and reliability. Some functions are implemented using local software packages to ensure performance and offline availability. Other functions are implemented by calling front-end pages, facilitating rapid iteration and cross-platform compatibility. Finally, some functions are implemented by calling third-party software packages to integrate third-party capabilities.

[0014] In one possible implementation of the first aspect, the first device includes a vehicle diagnostic device, which includes an external storage device, and the external storage device includes a first file directory and a second file directory; after receiving a first response sent by the server, the method further includes: saving target data in the first file directory, the target data including interface data and / or switch data; the first file directory is different from the second file directory, the first file directory has a first attribute and / or a second attribute, the first attribute indicates that the first file directory will not be cleared, the second attribute indicates that the first file directory has a hidden attribute for third-party software packages, and the second file directory is used to save application data of the vehicle diagnostic application.

[0015] In this embodiment, the vehicle diagnostic device stores target data such as interface data and / or switch data in a first file directory that is different from the second file directory. The second file directory stores the application data of the vehicle diagnostic application, which ensures that the target data in the first file directory will not be deleted when the application data of the vehicle diagnostic application is subsequently deleted.

[0016] Furthermore, even if the external storage of the vehicle diagnostic device is formatted, the target data in the first file directory will not be erased if the first file directory has the first attribute. Moreover, since the target data in the first file directory is stored in external storage, and due to the non-volatile nature of external storage after power failure, the target data can be persistently stored locally on the vehicle diagnostic device.

[0017] Furthermore, if the first file target has a second attribute, the first file directory has a hidden attribute for third-party software packages. This prevents third-party software packages in the vehicle diagnostic application device from accessing the first file directory, thus ensuring the security of the target data in the first file directory.

[0018] In one possible implementation of the first aspect, the vehicle diagnostic device includes internal memory. After receiving a first response from a server, the method further includes: saving target data to the internal memory; sending a second request to the server in response to a second start command for vehicle diagnostic applications, the second request requesting the target data, the timing of the first start command preceding the timing of the second start command; receiving a second response from the server, the second response including the target data; and updating the target data in the internal memory and / or a first file directory based on the target data corresponding to the second response.

[0019] In this embodiment, the target data in the external and / or internal memory of the vehicle diagnostic equipment is updated to ensure that the target data in the external and / or internal memory is always up-to-date. The updated target data is used to display the updated first interface. The updated first interface is more accurate, resulting in a better user experience.

[0020] Secondly, embodiments of this application provide an interface display device applied to a first device, the first device including a vehicle diagnostic application, the vehicle diagnostic application including X application functions, where X is an integer greater than or equal to 1, the device including: a transceiver module, used to send a first request to a server in response to a user's first start command for the vehicle diagnostic application, the first request being used to request interface data and switch data of the vehicle diagnostic application; the interface data indicating that Y controls from the X controls corresponding to the X application functions are displayed at the same level, where Y≤X, the switch data being used to indicate that the first control from the X controls is not displayed at the level; the transceiver module is also used to receive a first response sent by the server, the first response including interface data and switch data; a processing module, used to display a first interface according to the interface data and switch data, wherein the first interface includes a second control, the second control being any one of the Y controls that is different from the first control.

[0021] Thirdly, embodiments of this application provide a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in the first aspect. This terminal device can be understood as an electronic device.

[0022] Fourthly, embodiments of this application provide a vehicle diagnostic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in the first aspect. This vehicle diagnostic device can be understood as an electronic device.

[0023] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method as described in the first aspect.

[0024] Sixthly, embodiments of this application provide a computer program product that, when run on a terminal device or a vehicle diagnostic device, causes the terminal device or vehicle diagnostic device to perform the method as described in the first aspect.

[0025] It is understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0027] Figure 1 This is a schematic diagram of the user interface of a vehicle diagnostic application provided in an embodiment of this application; Figure 2 This is a schematic diagram of the user interface of a diagnostic kit provided in one embodiment of this application; Figure 3 This is a schematic diagram of a system architecture to which the interface display method provided in one embodiment of this application can be applied; Figure 4 This is a schematic diagram of an interface display method provided in an embodiment of this application; Figure 5 This is a schematic diagram of the initial interface provided in one embodiment of this application; Figure 6 This is a schematic diagram of a first interface provided in an embodiment of this application; Figure 7 This is a schematic diagram of an interface display method provided in another embodiment of this application; Figure 8 This is a schematic diagram of the interface display device provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of a vehicle diagnostic device provided in one embodiment of this application. Detailed Implementation

[0028] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0029] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0030] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0031] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0032] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0033] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0034] The following will introduce the relevant terminology of the interface display method and apparatus in the embodiments of this application.

[0035] Vehicle diagnostic equipment: A specialized tool or system used to detect, analyze, and evaluate vehicle performance and condition, as well as to locate faults. Vehicle diagnostic equipment is installed on the vehicle to perform diagnostics. It includes a diagnostic panel and a diagnostic box. The diagnostic panel is primarily used for displaying and controlling vehicle diagnostic operations. The diagnostic box is used to communicate with various vehicle systems to obtain vehicle performance parameters to determine the vehicle's condition.

[0036] Vehicle diagnostic applications: Computer programs or applications used for fault diagnosis, performance testing, and system maintenance of vehicles. Vehicle diagnostic applications can be installed on vehicle diagnostic equipment or terminal devices such as mobile phones. The functions here include at least vehicle diagnostic capabilities, which are implemented through vehicle diagnostic software.

[0037] Controls: Interactive elements in the user interface. Users can trigger corresponding application functions or enter menu interfaces by activating controls.

[0038] Figure 1 A schematic diagram illustrating a user interface 11 of a vehicle diagnostic application according to one embodiment is shown. Figure 1 As shown, the user interface 11 includes at least one of the following application functions: intelligent diagnostics, local diagnostics, electric vehicle diagnostics, remote diagnostics, special functions, toolbox, software update, feedback, diagnostic kit, marketplace, academy, information center, user information, and other modules. Figure 1 The corresponding controls for each application function are also shown. For example, the application function of intelligent diagnosis can be triggered by control 11A.

[0039] Among them, intelligent diagnostics is used to quickly and accurately perform comprehensive vehicle diagnostics with the help of intelligent algorithms, including fault detection, system analysis, etc., to efficiently troubleshoot vehicle problems.

[0040] Local diagnostics is used to directly connect to the vehicle and perform diagnostic operations on various vehicle systems locally, obtaining information such as fault codes and data streams.

[0041] Electric vehicle diagnostics is used to diagnose electric vehicles' unique systems, such as high-voltage systems and battery management systems, to ensure fault diagnosis and maintenance.

[0042] Remote diagnostics is used to connect vehicles via a network, allowing technicians to perform vehicle diagnostics remotely, enabling remote fault diagnosis and technical support without on-site operation.

[0043] Special features include functions that address specific needs in vehicle maintenance, such as anti-theft matching and fuel injector coding, to solve specific operations that are not routine diagnostics.

[0044] The toolbox is used to collect various auxiliary repair tools, such as repair data lookup and tool usage instructions, to assist in carrying out repair work.

[0045] Software updates are used to update the device's diagnostic applications, ensuring that the device supports new vehicle models, new fault diagnoses, and maintains advanced functionality.

[0046] Feedback is used by maintenance personnel and other users to submit problems and suggestions encountered when using vehicle diagnostic equipment, helping vehicle diagnostic equipment manufacturers collect information to optimize their products.

[0047] Diagnostic suites are used to associate diagnostic-related components and function sets, making it easy to quickly access diagnostic resources and tools within the suite.

[0048] The online store provides vehicle diagnostic equipment-related accessories, upgrade services, and repair manuals, making it convenient for users to purchase the items they need.

[0049] The academy aims to help users learn about vehicle diagnostics and the operation techniques of vehicle diagnostic equipment, thereby improving their repair and diagnostic skills. The academy includes courses and case studies.

[0050] The information center is used to gather information such as user manuals for vehicle diagnostic equipment, vehicle model diagnostic data, and fault case databases, for users to query and refer to, and to assist in maintenance decisions.

[0051] User information is used to display the logged-in user's account information, permission settings, personalized configurations, etc., making it convenient for users to manage their personal data and access permissions to vehicle diagnostic equipment.

[0052] Other modules are used to store auxiliary functions that are not separately categorized.

[0053] exist Figure 1 Among the various application functions, the example of the control 11I corresponding to the user triggering the diagnostic suite will be used for explanation. Figure 2A schematic diagram of the user interface 21 of the diagnostic kit, as shown below. Figure 2 As shown, the user interface 21 of the diagnostic kit includes at least one of the following application functions: vehicle coverage, controller area network (CAN) bus pin detection, high-speed CAN bus testing, CAN bus oscilloscope function, diagnostic software clearing, connector firmware repair, data stream sampling, data link connector (DLC) voltage check, flash data management, resetting vehicle identification number information, diagnostic history, and vehicle QR code. Figure 2 The controls corresponding to each application function of the diagnostic kit are shown. For example, the application function of the diagnostic kit's vehicle coverage can be triggered by control 21A.

[0054] The vehicle coverage area is used to view information such as the vehicle brands and models supported by the diagnostic kit.

[0055] CAN bus pin detection is used to detect the connection status, signal status, and other information of CAN bus pins.

[0056] High-speed CAN bus testing is used to perform relevant tests on the high-speed CAN bus and troubleshoot bus faults.

[0057] Diagnostic software cleanup is used to clear related data, cache, or software settings in diagnostic software.

[0058] Repair connector firmware is used to repair and update the connector firmware of vehicle diagnostic equipment.

[0059] Data stream sampling is used to collect data streams from various vehicle systems in order to analyze the vehicle's operating status.

[0060] The data link connector voltage check is used to detect whether the voltage of the data link connector is normal.

[0061] Flash data management is used to manage data in the flash memory of vehicle diagnostic equipment, such as storing data, reading data, and deleting data, at least one of these.

[0062] Reset Vehicle Identification Number Information is used to reset or update the data related to the vehicle identification number.

[0063] The diagnostic history is used to view previous diagnostic information for the vehicle.

[0064] The vehicle QR code function is used to scan the vehicle's QR code to obtain vehicle information or diagnostic data, etc.

[0065] by Figure 1The user interface 11 shown is an example of the first-level menu interface. When a user triggers control A in the first-level menu interface, they can enter the second-level menu interface or enter the function corresponding to control A. Figure 2 The user interface 21 shown is the second-level menu interface corresponding to the diagnostic kit. Similarly, the user can access the third-level menu interface or the function corresponding to control B by triggering control B in the second-level menu interface. The interface hierarchy of the vehicle diagnostic application described above is only an example and not a limitation.

[0066] Vehicle diagnostic applications are highly specialized applications. For example, they need to be compatible with the proprietary communication protocols of different vehicle brands and models, and also meet industry compliance requirements. This makes vehicle diagnostic applications quite complex. Furthermore, with the rapid development of vehicle technology, vehicle diagnostic applications need to evolve their diagnostic technologies in parallel, placing higher demands on the timeliness of updates. These factors contribute to at least one issue: the technology of vehicle diagnostic applications is not yet mature enough. This immaturity is specifically manifested in the following ways: When a vehicle diagnostic application malfunctions and users are unable to access it, the application crashes, leading to complaints. Alternatively, some newly developed vehicle diagnostic applications are released only to a small group of users to gather feedback and check for bugs and whether the new features meet user needs. This allows technical staff to fix issues before releasing the application to all users, preventing the majority of users from being affected.

[0067] Based on this, this application proposes an interface display method. (See reference...) Figure 3 This is a schematic diagram of a system architecture (hereinafter also referred to as an interface display system) to which the interface display method of one embodiment of this application can be applied. Figure 3 As shown, the interface display system may include a first device and a server 302. The first device can interact with the server 302 via a communication link.

[0068] like Figure 3 As shown, the first device may include a vehicle diagnostic device 301-1 or a terminal device 301-2. When the first device is a vehicle diagnostic device 301-1, it is installed on the vehicle 303. When the first device is a terminal device 301-2, it can also communicate with the vehicle diagnostic device 301-1 via a wireless network. The first device has a display screen. The first device has a vehicle diagnostic application installed; when the application is started, its interface is displayed on the first device's display screen. (The text then repeats the description of the vehicle diagnostic application interface.) Figure 1Taking the menu interface shown as an example, the first device can respond to the user's trigger operation on a control corresponding to a certain application function in the menu interface, and enter the function corresponding to that control or enter the menu interface of that control.

[0069] Server 302 can provide services to the first device. For example, when the vehicle diagnostic application on the first device is started, the first device sends a request to the server to obtain relevant data from the vehicle diagnostic application. The first device displays the data based on the data sent by the server. As another example, when a control displayed on the first device's interface is triggered, the first device can send a request corresponding to that control to the server. Server 302 can then send data corresponding to the triggered control's request to the first device or perform corresponding data processing based on that request.

[0070] It should be noted that the above system architecture is only an example and does not constitute a limitation on the interface display system.

[0071] The following will combine Figure 3 The system architecture of this application is described in detail, along with the interface display method of the embodiments thereof. This interface display method is applied to a first device. The first device includes a vehicle diagnostic application, which includes X application functions, where X is an integer greater than or equal to 1.

[0072] refer to Figure 4 This is a schematic diagram of an interface display method according to an embodiment of this application. Figure 4 As shown, the interface display method includes steps S401 to S403.

[0073] S401, In response to the user's first start command for the vehicle diagnostic application, the first device sends a first request to the server. The first request is used to request the interface data and switch data of the vehicle diagnostic application.

[0074] Optionally, if the first device includes a hardware button for launching a vehicle diagnostic application, the first device receives a first launch command in response to the user triggering the hardware button. If the first device's interface displays a control for launching a vehicle diagnostic application, the first device receives a first launch command in response to the user triggering the control. If the first device has voice interaction functionality, the first launch command includes a voice command indicated by the user for launching the vehicle diagnostic application.

[0075] For example, the first request may be in JavaScript object notation (JSON) format or Extensible markup language (XML) format, etc.

[0076] The interface data indicates that Y controls from the X controls corresponding to X application functions are displayed at the same level, where Y ≤ X. The vehicle diagnostic application includes N levels, and the total number of application functions corresponding to N levels is X. Taking one level L... i For example, this level L i The number of application functions is Y, and correspondingly, the level L i The number of controls for the application's functionality is Y. i∈[1,N], where N is an integer greater than or equal to 1. Combining the above... Figure 1 and Figure 2 In the example, N can take the value 2 or 3. Figure 1 In the first level shown, the number of Y is 14. Figure 2 In the second level shown, the number of Y is 12.

[0077] The switch data is used to indicate the first control among X controls that is not displayed in the hierarchy. For example, the switch data includes a first field and a second field, where the first field indicates the control identifier and the second field indicates whether the control is displayed in the hierarchy. Alternatively, the switch data includes a third field, which indicates either the identifier of a control that is not displayed in the hierarchy or the identifier of a control that is displayed in the hierarchy.

[0078] In one possible embodiment, step S401 includes: the first device responding to a user's first start command for the vehicle diagnostic application, displaying an initial interface, the initial interface including an input box and a confirmation button, the input box being used to receive identification information of the first device input by the user; the first device responding to the user triggering the confirmation button, sending a first request to the server. Figure 5 A schematic diagram of the initial interface 51 is shown, as follows: Figure 5 As shown, the initial interface 51 includes an input box 501, a confirmation button 502, and a reset button 503. The identification information of the first device includes the serial number information of the first device.

[0079] S402. The first device receives the first response sent by the server. The first response includes interface data and switch data. Similar to the first request, the first response can also be in JSON or XML format.

[0080] S403. Display the first interface based on the interface data and switch data. The first interface includes a second control, which is any one or more of the Y controls that are different from the first control. This can be understood as the first interface not including the first control among the Y controls.

[0081] Let's illustrate with a concrete example. The interface data is displayed at the first level. Figure 1The intelligent diagnostics application functions correspond to 14 controls (i.e., Y is 14, and the intelligent diagnostics application functions correspond to 14 controls from 11A to 11N) in 14 application functions of other modules. When the switch data indication does not display the first control corresponding to the intelligent diagnostics application function (i.e., the first control is control 11N) at the first level, the first device displays the interface data and the switch data on the first interface as follows: Figure 6 As shown. In Figure 6 In the example, the first interface includes a second control that is different from the first control 11N among 14 controls 11A to 11N. The second control includes controls 11A to 11M.

[0082] In this embodiment, the first device sends a first request to the server, and the received first response includes not only interface data but also switch data. The interface data indicates that Y controls from the X controls corresponding to X application functions should be displayed at the same level. This can be understood as Y representing the total number of application functions and the total number of controls for all application functions at the same level. The switch data indicates that if the first control from the X controls is not displayed at the level, the first interface displayed by combining the interface data and the switch data includes any one or more second controls from the Y controls that are different from the first control. Thus, the first device can flexibly control whether to display controls corresponding to application functions in the first interface through the switch data, and thereby flexibly control whether to provide the user with each application function in the first interface.

[0083] For example, if certain functions frequently malfunction, relevant personnel can set a toggle switch to prevent the corresponding control (i.e., the primary control) from being displayed. This avoids situations where users click on the primary control to access the corresponding function, only to find that the function is malfunctioning, resulting in a poor user experience.

[0084] For example, some newly developed vehicle diagnostic applications may release versions that only allow a small group of users to use a particular function, while others do not. In this case, relevant personnel can configure a switch to instruct the interface of some vehicle diagnostic applications to display the control for that function. Feedback from these users can then be used to check for bugs and whether the new function meets user needs. Meanwhile, the interface of the other vehicle diagnostic applications will not display the control for that function, preventing users from accessing that function while operating within the application. This ensures a smooth user experience even if the function is not yet fully developed.

[0085] The specialized nature of vehicle diagnostic applications necessitates high stability requirements from users. To meet these stability demands, these applications are updated by releasing new versions. However, releasing new versions carries drawbacks such as increased version management complexity, higher testing and fixing costs, and the potential introduction of new issues that could negatively impact user experience. With frequent updates to vehicle diagnostic applications, these version management complexities and testing and fixing costs become even more pronounced.

[0086] In the above embodiments, the first device requests interface data and switch data from the server. In one possible embodiment, after surveying user experience, relevant personnel can update the interface data and / or switch data based on user feedback to optimize the user experience.

[0087] Furthermore, according to yet another embodiment of this application, in order to improve the efficiency, flexibility, and maintainability of updating interface data and / or switch data, the interface data and / or switch data may be in the form of a configuration file.

[0088] Specifically, in one possible embodiment, the interface data is an interface configuration file, which is used to configure at least one of the following: the order of Y controls in the same layer, the size of each control, and the icon of each control. The switch data is a switch configuration file. The switch configuration file is used to configure the first control not to be displayed in the layer.

[0089] Developers of vehicle diagnostic applications can configure the first interface by modifying the interface configuration file and uploading it to the server. The first device updates the order, size, and icon of each of the Y controls in the same layer according to the interface configuration file. Developers of vehicle diagnostic applications can also configure the first control not to be displayed in the layer by modifying the switch configuration file and uploading it to the server. The first device updates the first control according to the switch configuration file.

[0090] Compared to releasing a new version of the vehicle diagnostic application to update the entire application, this embodiment allows users to flexibly and efficiently update interface and / or switch data simply by modifying the aforementioned interface configuration file and / or switch configuration file. This significantly improves the flexibility and maintainability of modifying interface and / or switch data.

[0091] To illustrate with a specific example, the interface configuration file is used to configure, for example... Figure 1 The 14 controls in the first-level interface shown are numbered 11A to 11N, and the switch configuration file is used to configure controls not listed below. Figure 1When the first control 11N is displayed in the first level shown, the first interface displayed according to the interface configuration file and the switch configuration file is as follows: Figure 6 As shown.

[0092] With the development of vehicle technology and vehicle diagnostic technology, vehicle diagnostic applications have become increasingly feature-rich, with some functions further divided into multiple sub-functions. The hierarchical structure of vehicle diagnostic application functions is best displayed through a hierarchical interface structure to enhance the user experience.

[0093] Specifically, in one possible embodiment, the interface data includes: menu interface data of at least one level, wherein the first interface includes the i-th level menu interface. For example... Figure 4 As shown, the interface display method may also include step S404.

[0094] S404. In response to the user triggering the second control of the first interface, if the second control is associated with the (i+1)th level menu interface, display the (i+1)th level menu interface; if the second control is associated with an application function, start the application function.

[0095] Still with Figure 6 Taking the first interface as an example (the first-level menu interface), the first interface includes a total of 13 second controls from 11A to 11M. Among them, the second control 11I corresponding to the diagnostic suite application function is associated as follows... Figure 2 The second-level menu interface shown is the menu interface for the diagnostic suite. Regarding the case where the second control is associated with the menu interface, the first device responds to user triggers such as... Figure 6 The second control 11I in the middle will jump to Figure 2 The second-level menu interface is shown. Regarding the case where the second control is associated with an application function, the second control 11A corresponding to the intelligent diagnostics application function is associated with the intelligent diagnostics function. The first device can activate the intelligent diagnostics function in response to the user triggering the second control 11A.

[0096] The application features include vehicle diagnostics. Combined with... Figure 6 For example, vehicle diagnostic functions may include at least one of the following: intelligent diagnostics, local diagnostics, remote diagnostics, electric vehicle diagnostics, and diagnostic kits. Figure 6 As shown, in addition to vehicle diagnostic functions, vehicle diagnostic applications may include at least one of the following auxiliary functions: special functions, toolbox, software updates, feedback, marketplace, academy, information center, and user information. These auxiliary functions can improve tool usability, enhance user stickiness, and expand service boundaries, upgrading vehicle diagnostic applications from tools providing single functions to services covering the entire lifecycle of detection, learning, repair, and consumption.

[0097] In this embodiment, based on the hierarchical structure of the vehicle diagnostic application's functions, the interface data is displayed in a hierarchical interface format. Each hierarchical menu interface's controls can trigger access to the next level menu interface or launch application functions. This hierarchical interface offers stronger functional logic, facilitates user operation, and improves the user experience.

[0098] In one possible embodiment, the switch data further indicates the target processing flow of the application function, which is one of at least one candidate processing flow. When the second control is associated with an application function, starting the application function includes: determining the target processing flow corresponding to the application function based on the switch data; and executing the target processing flow.

[0099] Some application functions can have multiple processing flows, such as a basic processing flow and a complete processing flow. The basic processing flow includes the fundamental steps to complete the application function. The complete processing flow is obtained by optimizing the application function based on the basic processing flow and adding optimization steps. The basic processing flow is suitable for scenarios where the hardware and network resources of the first device are limited. The complete processing flow is suitable for scenarios with high precision and high reliability requirements. For any application function, through this layered design of specifying the target processing flow from the above multiple candidate processing flows, the interface display method of this application embodiment can be flexibly switched in different hardware environments, network environments, and other scenarios. When the candidate processing flow includes a basic processing flow and a complete processing flow, the basic processing flow ensures the ease of use of the application function, while the complete processing flow meets the complex requirements of the application function, thereby improving the user experience.

[0100] In one possible embodiment, when the second control is associated with an application function, launching the application function includes at least one of the following: when the second control is associated with a functional module of the application function, launching the functional module; when the second control is associated with a local software package of the application function, launching the local software package of the application function; when the second control is associated with a front-end page of the application function, jumping to the front-end page; when the second control is associated with a third-party software package of the application function, launching the third-party software package of the application function.

[0101] In one specific embodiment, the functional modules of the application function include various interfaces of the function. Each functional module of the application function has a first identifier, which is pre-agreed upon by the server and the vehicle diagnostic application. Upon the user triggering the second control corresponding to the application function, the server redirects to the functional module corresponding to the first identifier to launch the application function. The local software package of the application function is stored in a local database and has a second identifier. Upon the user triggering the second control corresponding to the application function, the vehicle diagnostic application queries the local database for the local software package with the second identifier to launch the application function. The front-end page of the application function is in the form of a front-end page link. Upon the user triggering the front-end page of the application function, the first device redirects to the front-end page link to launch the application function. The front-end page may include a Hypertext Markup Language 5 (h5) page. Third-party software packages of the application function have a third identifier. Upon the user triggering the second control corresponding to the application function, the vehicle diagnostic application queries the first device based on the third identifier to see if the third-party software package is already installed. If the third-party software package is installed on the first device, the first device calls a system interface to launch the application function. The third-party software package may include an Android application package (apk).

[0102] In this embodiment, the vehicle diagnostic application utilizes multiple technology stacks to achieve diverse application functions, enabling it to efficiently provide a variety of services. For example, some functions are implemented through complete functional modules. When these modules are used for vehicle diagnostics, they possess highly complex technical logic specific to the vehicle diagnostic field, exhibiting high professionalism and reliability. Some functions are implemented using local software packages to ensure performance and offline availability. Other functions are implemented by calling front-end pages, facilitating rapid iteration and cross-platform compatibility. Finally, some functions are implemented by calling third-party software packages to integrate third-party capabilities.

[0103] There are instances where errors in the vehicle diagnostic application's data prevent users from launching it. Alternatively, if a user returns the vehicle diagnostic device, after-sales personnel may reset and format the local disk. Both of these actions will erase previously downloaded application and interface data for the vehicle diagnostic application. New users will then need to re-download the interface data when using the application again, resulting in a poor user experience.

[0104] In the above embodiments, the first device displays the first interface based on the interface data and switch data obtained from the server. According to another embodiment of this application, the first device can also store the interface data and / or switch data locally on the first device, enabling the vehicle diagnostic application of the first device to support offline access to the interface data and / or switch data. When the first device displays the first interface based on the interface data and switch data, it can also quickly obtain the interface data and switch data locally to accelerate the display speed of the first interface, etc.

[0105] Furthermore, when the first device is a vehicle diagnostic device, the vehicle diagnostic application is a native application of the vehicle diagnostic device, and its data storage permissions are more open. In this case, to avoid deleting the interface data and / or switch data along with the application data of the vehicle diagnostic application, which would require new users to re-download the interface data when using the vehicle diagnostic application again, resulting in a poor user experience, another embodiment of this application provides an interface display method that stores the interface data and / or switch data separately from the application data of the vehicle diagnostic application and persistently stores the interface data and / or switch data.

[0106] Specifically, the first device includes a vehicle diagnostic device, which includes external storage, and the external storage includes a first file directory and a second file directory. (Reference) Figure 7 This is a schematic diagram of an interface display method according to another embodiment of this application. Figure 7 As shown, the interface display method includes steps S601 to S603. Steps S601 and S602 are similar to steps S401 and S402 in the above embodiment, respectively, and will not be described again here. After step S602, the method may further include step S603.

[0107] S603. The target data is stored in the first file directory. The target data includes interface data and / or switch data. The first file directory is different from the second file directory. The first file directory has a first attribute and / or a second attribute. The first attribute indicates that the first file directory will not be deleted, and the second attribute indicates that the first file directory is hidden for third-party software packages. The second file directory is used to store application data for vehicle diagnostic applications.

[0108] External storage devices include: hard disks, solid-state drives, memory cards, etc. The first and / or second attributes of the first file directory can be preset by the developers of the vehicle diagnostic application.

[0109] In this embodiment, the vehicle diagnostic device stores target data such as interface data and / or switch data in a first file directory that is different from the second file directory. The second file directory stores the application data of the vehicle diagnostic application, which ensures that the target data in the first file directory will not be deleted when the application data of the vehicle diagnostic application is subsequently deleted.

[0110] Furthermore, even if the external storage of the vehicle diagnostic device is formatted, the target data in the first file directory will not be erased if the first file directory has the first attribute. Moreover, since the target data in the first file directory is stored in external storage, and due to the non-volatile nature of external storage after power failure, the target data can be persistently stored locally on the vehicle diagnostic device.

[0111] Furthermore, if the first file target has a second attribute, the first file directory has a hidden attribute for third-party software packages. This prevents third-party software packages in the vehicle diagnostic application device from accessing the first file directory, thus ensuring the security of the target data in the first file directory.

[0112] Of course, this embodiment takes a vehicle diagnostic device as an example, where the vehicle diagnostic device saves the target data to a first file directory. Alternatively, if the first device is a terminal device, and the terminal device includes external storage, and the external storage includes a first file directory and a second file directory, the terminal device can also save the target data to the first file directory.

[0113] In addition to the external memory described above, in one possible embodiment, the vehicle diagnostic device includes internal memory. The internal memory includes, for example, at least one of the following: random access memory (RAM) and cache memory. The target data described above can also be stored in the internal memory.

[0114] like Figure 7 As shown, according to another embodiment of the interface display method of this application, step S602 may be followed by steps S604 to S608.

[0115] S604. Save the target data to internal memory. It should be noted that... Figure 7 In this paper, step S603 is executed before step S604 for example only. This application does not limit the execution order of step S603 and step S604.

[0116] S605. In response to a second start command for vehicle diagnostic applications, a second request is sent to the server. The first start command is executed before the second start command; otherwise, the second start command is similar to the first start command and will not be described further. The second request is used to request target data.

[0117] S606. Receive the second response sent by the server, the second response including the target data. The second request and the second response are similar to the first request and the first response, respectively, and will not be described again here.

[0118] S607. Update the target data in the internal memory and / or the first file directory according to the target data corresponding to the second response.

[0119] Taking two consecutive startup commands in a vehicle diagnostic application as an example, the vehicle diagnostic device responds to the first startup command by retrieving target data from the server. The vehicle diagnostic device stores the target data in external and / or internal memory, and displays the target data on the first interface. Next, the vehicle diagnostic device responds to the second startup command by retrieving updated target data from the server. The vehicle diagnostic device uses the updated target data to update the target data in the external and / or internal memory.

[0120] Through the above operations, the external and / or internal memory of the vehicle diagnostic equipment is always updated with the target data. The updated target data is used to display the updated first interface. The updated first interface is more accurate and provides a better user experience. For example, as... Figure 7 As shown, after step S607, the first device can also execute step S608: display the updated first interface based on the updated target data.

[0121] In summary, the interface display method according to the embodiments of this application has at least one of the following technical effects: In this embodiment, the first device sends a first request to the server, and the received first response includes not only interface data but also switch data. The interface data indicates that Y controls from the X controls corresponding to X application functions should be displayed at the same level. This can be understood as Y representing the total number of application functions and the total number of controls for all application functions at the same level. The switch data indicates that if the first control from the X controls is not displayed at the level, the first interface displayed by combining the interface data and the switch data includes any one or more second controls from the Y controls that are different from the first control. Thus, the first device can flexibly control whether to display controls corresponding to application functions in the first interface through the switch data, and thereby flexibly control whether to provide the user with each application function in the first interface.

[0122] Compared to releasing a new version of the vehicle diagnostic application to update the entire application, this embodiment allows users to flexibly and efficiently update interface and / or switch data simply by modifying the aforementioned interface configuration file and / or switch configuration file. This significantly improves the flexibility and maintainability of modifying interface and / or switch data.

[0123] For any application function, the hierarchical design of specifying the target processing flow among the multiple candidate processing flows allows the interface display method of this application embodiment to be flexibly switched in different hardware environments, network environments and other scenarios.

[0124] In this embodiment, the vehicle diagnostic device stores target data such as interface data and / or switch data in a first file directory different from the second file directory. The second file directory stores the application data of the vehicle diagnostic application. This ensures that when the application data of the vehicle diagnostic application is subsequently cleared, the target data in the first file directory will not be cleared. Furthermore, even if the external storage of the vehicle diagnostic device is formatted, the target data in the first file directory will not be cleared if the first file directory has a first attribute. Moreover, since the target data in the first file directory is stored in the external storage, based on the non-volatile nature of the external storage, the target data can be persistently stored locally on the vehicle diagnostic device. Furthermore, if the first file directory has a second attribute, the first file directory has a hidden attribute for third-party software packages. This prevents third-party software packages in the vehicle diagnostic application device from accessing the first file directory, ensuring the security of the target data in the first file directory.

[0125] In this embodiment, the target data stored in external and / or internal memory is updated via the launch command of the vehicle diagnostic application, ensuring that the target data in the external and / or internal memory of the vehicle diagnostic device is always up-to-date. The updated target data is used to display the updated first interface. The updated first interface is more accurate, resulting in a better user experience.

[0126] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0127] Corresponding to the interface display method in the above embodiments, Figure 8 A structural block diagram of the interface display device provided in the embodiments of this application is shown. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0128] Reference Figure 8The device is applied to a first device, which includes a vehicle diagnostic application. The vehicle diagnostic application includes X application functions, where X is an integer greater than or equal to 1. The device includes a transceiver module 810 and a processing module 820.

[0129] The transceiver module 810 is used to send a first request to the server in response to the user's first start command for the vehicle diagnostic application. The first request is used to request the interface data and switch data of the vehicle diagnostic application. The interface data indicates that Y controls are displayed in the same layer among the X controls corresponding to X application functions, where Y ≤ X. The switch data is used to indicate that the first control in the X controls is not displayed in the layer.

[0130] The transceiver module 810 is also used to receive the first response sent by the server, which includes interface data and switch data.

[0131] The processing module 820 is used to display a first interface based on the interface data and the switch data. The first interface includes a second control, which is any one of the Y controls that is different from the first control.

[0132] In one possible embodiment, the interface data is an interface configuration file, which is used to configure at least one of the following: the order of Y controls in the same level, the size of each control, and the icon of each control; the switch data is a switch configuration file.

[0133] In one possible embodiment, the interface data includes: menu interface data at least one level, and the processing module 820 is further configured to respond to the user triggering a second control of the first interface, display the (i+1)th level menu interface if the second control is associated with the (i+1)th level menu interface, and start the application function if the second control is associated with an application function, the application function including vehicle diagnostic function.

[0134] In one possible embodiment, the switch data also indicates the target processing flow of the application function, which is one of at least one candidate processing flow; the processing module 820 is specifically used to determine the target processing flow corresponding to the application function based on the switch data when the second control is associated with the application function; and to execute the target processing flow.

[0135] In one possible embodiment, the processing module 820 is specifically used for at least one of the following: when the second control is associated with a functional module of the application function, starting the functional module; when the second control is associated with a local software package of the application function, starting the local software package of the application function; when the second control is associated with a front-end page of the application function, jumping to the front-end page; when the second control is associated with a third-party software package of the application function, starting the third-party software package of the application function.

[0136] In one possible embodiment, the first device includes a vehicle diagnostic device, which includes external storage, and the external storage includes a first file directory and a second file directory. The processing module 820 is further configured to: store target data in the first file directory. The target data includes interface data and / or switch data; the first file directory differs from the second file directory, and the first file directory has a first attribute and / or a second attribute, the first attribute indicating that the first file directory will not be deleted, and the second attribute indicating that the first file directory has a hidden attribute for third-party software packages; the second file directory is used to store application data for the vehicle diagnostic application.

[0137] In one possible embodiment, the vehicle diagnostic device includes an internal memory, and the processing module 820 is further configured to: save target data to the internal memory; in response to a second start command for vehicle diagnostic applications, send a second request to a server, the second request requesting the target data, the timing of the first start command being before the timing of the second start command; receive a second response sent by the server, the second response including the target data; and update the target data in the internal memory and / or a first file directory according to the target data corresponding to the second response.

[0138] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0139] In applications, the modules in the interface display device can be software program modules, or they can be implemented through different logic circuits integrated in the processor, or they can be implemented through multiple distributed processors.

[0140] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The functional modules in the embodiments can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules can be implemented in hardware or as software functional modules. Furthermore, the specific names of the functional modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the modules in the above-described device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0141] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0142] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to 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 embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0143] This application also provides a terminal device and a vehicle diagnostic device.

[0144] Figure 9 A schematic diagram of the terminal device is shown.

[0145] like Figure 9 As shown, the terminal device 900 includes: a memory 901, at least one processor 902, and a computer program 903 stored in the memory 901 and executable on the at least one processor 902. When the processor 902 executes the computer program 903, it implements the steps in any of the above method embodiments.

[0146] Figure 10 A schematic diagram of a vehicle diagnostic device is shown.

[0147] like Figure 10 As shown, the vehicle diagnostic device 1000 includes: a memory 1011, at least one processor 1012, and a computer program 1013 stored in the memory 1011 and executable on the at least one processor 1012. When the processor 1012 executes the computer program 1013, it implements the steps in any of the above-described method embodiments.

[0148] exist Figure 10In the example, the vehicle diagnostic device 1000 includes a diagnostic tablet 1010 and a diagnostic box 1020. The diagnostic tablet 1010 includes the aforementioned memory 1011, at least one processor 1012, and a computer program 1013 stored in the memory 1011 and executable on the at least one processor 1012.

[0149] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps described in the various method embodiments above.

[0150] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0151] If the integrated unit is implemented as 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, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / 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. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

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

[0153] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0154] In the embodiments provided in this application, it should be understood that the disclosed apparatus / device and method can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0155] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for displaying an interface, characterized in that, Applied to a first device, the first device including a vehicle diagnostic application, the vehicle diagnostic application including X application functions, where X is an integer greater than or equal to 1, the method includes: In response to a user's first launch command for the vehicle diagnostic application, a first request is sent to the server. The first request is used to request interface data and switch data of the vehicle diagnostic application. The interface data indicates that Y controls from the X controls corresponding to the X application functions are displayed at the same level, where Y ≤ X. The switch data is used to indicate that the first control from the X controls is not displayed at the same level. Receive a first response sent by the server, the first response including the interface data and the switch data; Based on the interface data and the switch data, a first interface is displayed, wherein the first interface includes a second control, and the second control is any one or more of the Y controls that are different from the first control.

2. The method according to claim 1, characterized in that, The interface data is an interface configuration file, which is used to configure at least one of the following: the order of the Y controls in the same level, the size of each control, and the icon of each control; the switch data is a switch configuration file.

3. The method according to claim 1 or 2, characterized in that, The interface data includes: menu interface data at least one level, the first interface including the i-th level menu interface, and the method further includes: In response to the user triggering the second control of the first interface, if the second control is associated with the (i+1)th level menu interface, the (i+1)th level menu interface is displayed; if the second control is associated with the application function, the application function is launched, and the application function includes vehicle diagnostic function.

4. The method according to claim 3, characterized in that, The switch data also indicates the target processing flow of the application function, which is one of at least one candidate processing flow; activating the application function when the second control is associated with the application function includes: When the second control is associated with the application function, the target processing flow corresponding to the application function is determined based on the switch data; Execute the target processing flow.

5. The method according to claim 3, characterized in that, When the application function is associated with the second control, launching the application function includes at least one of the following: When the second control is associated with a functional module of the application function, the functional module is activated; When the second control is associated with a local software package of the application function, the local software package of the application function is launched; When the second control is associated with the front-end page of the application function, the user is redirected to the front-end page; When the second control is associated with a third-party software package for the application function, the third-party software package for the application function is launched.

6. The method according to claim 1, characterized in that, The first device includes a vehicle diagnostic device, the vehicle diagnostic device includes external storage, the external storage includes a first file directory and a second file directory; after receiving the first response sent by the server, the method further includes: The target data is stored in a first file directory, which includes the interface data and / or the switch data. The first file directory is different from the second file directory. The first file directory has a first attribute and / or a second attribute. The first attribute indicates that the first file directory will not be cleared, and the second attribute indicates that the first file directory has a hidden attribute for third-party software packages. The second file directory is used to store the application data of the vehicle diagnostic application.

7. The method according to claim 6, characterized in that, The vehicle diagnostic device includes internal memory, and after receiving the first response sent by the server, the method further includes: The target data is saved to the internal memory; In response to a second start command for the vehicle diagnostic application, a second request is sent to the server, the second request being for requesting the target data, the timing of the first start command being before the timing of the second start command; Receive a second response sent by the server, the second response including the target data; Update the target data in the internal memory and / or the first file directory according to the target data corresponding to the second response.

8. An interface display device, characterized in that, Applied to a first device, the first device including a vehicle diagnostic application, the vehicle diagnostic application including X application functions, where X is an integer greater than or equal to 1, the device includes: The transceiver module is used to send a first request to the server in response to a user's first start command for the vehicle diagnostic application. The first request is used to request interface data and switch data of the vehicle diagnostic application. The interface data indicates that Y controls from the X controls corresponding to the X application functions are displayed at the same level, where Y ≤ X. The switch data is used to indicate that the first control from the X controls is not displayed at the same level. The transceiver module is also configured to receive a first response sent by the server, the first response including the interface data and the switch data; The processing module is used to display a first interface based on the interface data and the switch data, wherein the first interface includes a second control, and the second control is any one of the Y controls that is different from the first control.

9. An electronic 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, it implements the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 7.

Images