Automobile entering diagnosis method and device and terminal equipment
By obtaining the vehicle models frequently diagnosed by users and their diagnostic software data, generating interactive controls, and directly entering the homepage of the diagnostic menu, it solves the cumbersomeness and inefficiency of the existing automotive diagnostics entering mode, and improves user experience and diagnostic efficiency.
Patent Information
- Application Number
- CN202410949595.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-08
AI Technical Summary
The existing automotive diagnostics entry mode is cumbersome, inefficient, poor user experience, and difficult to meet the needs of modern users for convenient and efficient services.
By obtaining the model with the highest diagnosis frequency of the user within a specified time period, obtaining the corresponding diagnostic software data, and generating interactive controls on the terminal device, directly entering the homepage of the vehicle's diagnostic menu, using the diagnostic software data for diagnosis, simplifying the operation process.
It improves the efficiency and experience of users entering the car diagnosis, reduces the operational complexity and the risk of wrong choices, and realizes a convenient diagnostic process.
Smart Images

Figure CN118915686A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of automobile diagnosis technology, and in particular, relates to an automobile diagnosis entry method, device and terminal equipment. Background Art
[0002] The current automobile diagnostic entry mode exposes certain limitations and cumbersomeness in terms of user experience. This process not only tests the user's patience, but also indirectly reflects the gap between technology and user needs.
[0003] First of all, when users open traditional applications designed for automotive diagnosis, since such applications often carry outdated interface designs and unintuitive navigation logic, the user's learning cost and operation difficulty are increased.
[0004] Secondly, after entering the application, users need to find the diagnostic software icon that matches their vehicle in the dazzling list of models. This process not only requires users to have certain automotive knowledge, but also increases the risk of wrong selection, which may lead to inaccurate subsequent diagnosis. Each click and confirmation is a challenge to the user's patience, which runs counter to the current social trend of pursuing efficiency.
[0005] Obviously, the market urgently needs a more intelligent, simple and automated automotive diagnostic entry solution to meet the expectations of modern users for convenient and efficient services. Summary of the invention
[0006] In view of this, the embodiments of the present application provide a vehicle diagnostic entry method, apparatus and terminal device to solve the technical problems of cumbersome operation, low efficiency and poor user experience when entering vehicle diagnostics using traditional vehicle diagnostic entry methods.
[0007] A first aspect of an embodiment of the present application provides a method for entering automobile diagnosis, which is applied to a terminal device, and the method includes:
[0008] Obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period;
[0009] Obtaining diagnostic software data corresponding to the vehicle model;
[0010] Connects to the car's diagnostic connector;
[0011] Generate and display one or more interactive controls, each of which is used for the user to trigger entry into the diagnostic menu homepage of the corresponding vehicle type, and the diagnostic menu homepage is used for the user to trigger execution of diagnostic operations for the vehicle type, and the diagnostic operations for the vehicle type include diagnosing the vehicle type using diagnostic software data corresponding to the vehicle type.
[0012] A second aspect of an embodiment of the present application provides an automobile diagnostic entry device, comprising:
[0013] An analysis module, used to obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period;
[0014] A download module, used to obtain diagnostic software data corresponding to the vehicle model;
[0015] a connection module, used to connect the terminal device to a diagnostic connector of a vehicle;
[0016] An output module is used to generate one or more interactive controls on the display screen of the terminal device, each of the interactive controls is used to trigger entry into the diagnostic menu homepage of the corresponding vehicle model, and the diagnostic menu homepage is used to trigger entry into the diagnosis of the vehicle model. The diagnosis of the vehicle model includes diagnosing the vehicle model using the diagnostic software data corresponding to the vehicle model.
[0017] The third aspect of an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the automobile diagnostic entry method provided in the first aspect of the embodiment of the present application are implemented.
[0018] The fourth aspect of the embodiments 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 steps of the automobile diagnostic entry method provided in the first aspect of the embodiments of the present application.
[0019] The first aspect of the embodiment of the present application provides a method for entering automobile diagnostics by obtaining one or more vehicle models that are diagnosed most frequently by the user within a specified time period; obtaining diagnostic software data corresponding to the vehicle models; connecting to the diagnostic connector of the automobile; generating and displaying one or more interactive controls, each of which is used for the user to trigger entry into the diagnostic menu homepage of the corresponding vehicle model, and the diagnostic menu homepage is used for the user to trigger execution of diagnostic operations for the vehicle model, and the diagnostic operations for the vehicle model include diagnosing the vehicle model using the diagnostic software data corresponding to the vehicle model. The interactive controls obtained by the above method can directly perform automobile diagnosis of the vehicle model required by the user without complicated operations, thereby improving the efficiency of the user entering automobile diagnosis and improving the user experience.
[0020] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. 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 paying any creative work.
[0022] Figure 1 This is a flow chart of a method for entering a vehicle diagnostics system provided by an embodiment of the present application;
[0023] Figure 2 is a flow chart of a method for entering vehicle diagnostics provided by another embodiment of the present application;
[0024] Figure 3 is a flow chart of a method for entering vehicle diagnostics provided by another embodiment of the present application;
[0025] Figure 4 is a flow chart of a method for entering vehicle diagnostics provided by another embodiment of the present application;
[0026] Figure 5 is a flow chart of a method for entering vehicle diagnostics provided by another embodiment of the present application;
[0027] Figure 6 is a flow chart of a method for entering vehicle diagnostics provided by another embodiment of the present application;
[0028] Figure 7 This is a structural schematic diagram of a vehicle diagnostic entry device provided by an embodiment of the present application;
[0029] Figure 8 It is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0030] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0031] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.
[0032] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0033] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" 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 "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.
[0034] 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.
[0035] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0036] The automobile diagnostic entry method provided in the embodiment of the present application can be executed by the processor of the terminal device when running a computer program with corresponding functions, by obtaining one or more vehicle models that are diagnosed most frequently by the user within a specified time period; obtaining diagnostic software data corresponding to the vehicle model; connecting to the diagnostic connector of the automobile; generating and displaying one or more interactive controls, each of which is used for the user to trigger entry into the diagnostic menu homepage of the corresponding vehicle model, and the diagnostic menu homepage is used for the user to trigger execution of the diagnostic operation of the vehicle model, and the diagnostic operation of the vehicle model includes diagnosing the vehicle model using the diagnostic software data corresponding to the vehicle model. The interactive controls obtained by the above method can directly perform automobile diagnosis of the vehicle model required by the user without performing tedious operations, thereby improving the efficiency of the user entering the automobile diagnosis and improving the user experience.
[0037] In the application, the terminal device can be a smartphone and tablet computer installed with automobile diagnostic software, which can implement automobile diagnostics through the automobile diagnostic software, a professional automobile diagnostic instrument, a smart watch, an in-vehicle intelligent central control system, a personal computer (PC) or a laptop computer, a cloud diagnostic platform, etc. The embodiments of the present application do not impose any restrictions on the specific type of the terminal device.
[0038] like Figure 1 As shown, the automobile diagnostic entry method provided in the embodiment of the present application includes the following steps S1 to S4:
[0039] Step S1: Obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period.
[0040] In the application, when starting the car diagnostic software, it is usually necessary to download the client, register and log in before entering the car diagnostic software homepage. When the user starts the car diagnostic software (or enters the car diagnostic software homepage), this step can be triggered. The specified time period can be set to any time from one day to one month as needed, such as three days, one week, ten days, two weeks, etc. The car models obtained in this step can be one or more, such as 1, 2, 3, 4, 5 or even more. When users frequently diagnose one or several car models, this indicates that these car models may have performance problems, require regular maintenance, or the user has a high degree of attention and maintenance awareness for such car models. By analyzing the frequency of diagnosis, it can be indirectly understood that the user's current diagnosis needs for these car models are most urgent. In this way, intelligent screening of a large number of car models is realized, and the car models that users are most concerned about are directly displayed, which reduces the trouble of users looking for them among many car models and makes the diagnostic process faster and more intuitive. Only high-frequency diagnosis models are displayed to avoid invalid clicks and browsing by users on irrelevant models, making the diagnostic operation more focused, saving users' time and energy, and improving the completion speed of each diagnostic task.
[0041] Step S2: Obtain diagnostic software data corresponding to the vehicle model.
[0042] In the application, due to the different communication protocols adopted by different automobile manufacturers, these protocols are responsible for the data exchange between the vehicle and the diagnostic equipment to ensure the accuracy and safety of the diagnosis. The design and function of the electronic control units (ECUs) of different models are different. The number, type and internal software of the ECUs of each brand and even different models of the same brand may be different, and special software is required to interpret the data of these systems. In addition, the fault code library (DTCs) of each model is unique, and the error range and meaning covered are also different. Therefore, when diagnosing each model, the diagnostic software adapted to the model is required to achieve a more accurate diagnosis. Here, all the diagnostic software data of one or more models with the highest diagnosis frequency are obtained to facilitate the subsequent rapid entry into the diagnostic process and improve efficiency. Among them, the diagnostic software data can be directly obtained from the local through the diagnostic software package ID, version number, package name, local software path, etc., or downloaded from the cloud to the local and then obtained from the local.
[0043] Step S3: Connect to the car's diagnostic connector.
[0044] In the application, the terminal device can be connected to the diagnostic connector by automatically turning on the Bluetooth of the terminal device. In addition, wireless local area network (Wi-Fi), Zigbee, radio frequency identification (RFID), light fidelity communication (LIFI), long-term evolution technology (LTE), dedicated short-range communication (DSRC), and cellular vehicle-to-everything (C-V2X) can all be applied to this step as long as they can be controlled by the terminal device and realize the automatic connection between the terminal device and the diagnostic connector.
[0045] Step S4, generate and display one or more interactive controls, each of which is used for the user to trigger entering the diagnostic menu homepage of the corresponding vehicle model, and the diagnostic menu homepage is used for the user to trigger the execution of the diagnostic operation of the vehicle model, and the diagnostic operation of the vehicle model includes diagnosing the vehicle model using the diagnostic software data corresponding to the vehicle model.
[0046] In the application, in order to meet the habits of different users, these interactive controls are not limited to traditional click buttons, but can also include modern interactive methods such as sliding selection and voice command recognition. When an interactive control is triggered by the user, it can respond and jump to the diagnostic menu homepage of the vehicle model associated with the interactive control. When the user triggers the execution of the diagnostic operation on the diagnostic menu homepage, the diagnostic software data of the vehicle model is called to perform vehicle diagnosis.
[0047] like Figure 2 As shown, in one embodiment, step S1 includes the following steps S11 and S12:
[0048] Step S11: Obtain the user's automobile diagnosis history data within a specified time period.
[0049] In the application, the vehicle diagnostic history data includes the activity log of the user performing vehicle diagnostics through the vehicle diagnostic application or device, including but not limited to key data such as diagnosis time, vehicle model information, user ID, etc. Set a specific time range, such as the past week, month, or a custom date range.
[0050] Step S12: Analyze the automobile diagnosis history data to obtain one or more vehicle models with the highest diagnosis frequency.
[0051] In the application, the diagnosis frequency analysis can be realized through big data analysis. Specifically, by using tools such as SQL query, Spark SQL or Pandas DataFrame, the number of diagnoses in a specified time period can be counted by car model group. Then the diagnosis frequency of each car model is sorted in descending order to find the top few models with the most diagnosis times. In this way, the user's car diagnosis history data in a specified time period can be filtered out from massive data.
[0052] This embodiment displays the vehicle model in a targeted manner, which helps users locate problems more quickly. At the same time, reducing unnecessary data loading and rendering of the system can reduce server burden, optimize system performance, and reduce memory usage and power consumption of user devices.
[0053] like Figure 3 As shown, in one embodiment, step S2 includes the following steps S21 and S22:
[0054] Step S21: When the local database of the terminal device stores diagnostic software data corresponding to the vehicle model, the diagnostic software data is obtained from the local database.
[0055] Step S22: When the diagnostic software data corresponding to the vehicle model is not stored in the local database of the terminal device, the diagnostic software data is downloaded from the cloud to the local database, and the diagnostic software data is obtained from the local database.
[0056] In the application, by giving priority to the use of local data, diagnosis can be started quickly without network delay, improving user experience and diagnostic efficiency. In the second-gear terminal device, if there is no diagnostic software data for the target vehicle model in the local database, the device will automatically connect to the cloud server and download the required diagnostic software data from the cloud to the local database. After the download is complete, the data is read from the local database to perform the diagnosis. This process ensures that even if there is no data for a specific vehicle model stored locally, the latest or missing information can be obtained and used for diagnostic work in real time, maintaining the accuracy and compatibility of the diagnosis.
[0057] This embodiment uses the above method to enable the diagnostic tool to flexibly respond to the needs of various vehicle models. Even for the diagnosis of new or rare models, as long as there is data support in the cloud, the diagnosis can be performed, which increases the service scope and adaptability of the device. It also reduces the dependence on continuous network connection as a whole, so that the diagnostic tool can also serve the vehicle model with stored data in an offline state.
[0058] like Figure 4 As shown, in one embodiment, after step S2, the following step S23 is also included:
[0059] Step S23: start the diagnostic interface and run the diagnostic interface in the background.
[0060] This embodiment starts the diagnostic interface and runs it in the background. Users can start the diagnostic program immediately without waiting for data to be loaded from the cloud, which greatly shortens the waiting time before diagnosis and improves diagnostic efficiency. In addition, when there is no network connection or the network is unstable, the locally running diagnostic software can still work normally, which is particularly important for vehicle diagnosis in remote areas or in environments with poor signals, ensuring the continuity and reliability of diagnostic services.
[0061] like Figure 5 As shown, in one embodiment, step S3 includes the following steps S31 and S32:
[0062] Step S31: When the Bluetooth function is turned on, pair with the diagnostic connector of the car and establish a connection.
[0063] In the application, if the Bluetooth function of the user's terminal device (such as a smartphone) is already turned on, the device will automatically search for available Bluetooth devices nearby, identify the car's diagnostic connector and request pairing. Once the pairing is successful, a stable Bluetooth connection will be established between the two, allowing the diagnostic software to start reading vehicle data, performing diagnostic tasks, etc.
[0064] Step S32: When the Bluetooth function is turned off, the Bluetooth function is automatically turned on to pair with the diagnostic connector of the car and establish a connection.
[0065] In the application, if the Bluetooth function of the user's terminal device is initially turned off, the system will automatically activate the Bluetooth function and perform the same pairing and connection process as step S31. This means that the user does not need to manually intervene to turn on Bluetooth or perform pairing operations, and the system will automatically process these steps until it successfully connects to the vehicle diagnostic connector.
[0066] The method of this embodiment eliminates the need for users to understand complicated pairing steps or manually search for devices, greatly reducing the technical threshold, so that even users with poor technical skills can easily complete the connection. The automated connection process speeds up the time from launching the application to starting the diagnosis, reduces the user's waiting and operation time, and increases the convenience and comfort of use.
[0067] like Figure 6 As shown, in one embodiment, step S4 includes the following steps S41 and S42:
[0068] Step S41: Generate an interactive control for each vehicle type.
[0069] In an application, an interactive control may refer to an element such as a button, slider, input box, etc. on the interface, which is designed for users to interact with specific vehicle model data, such as displaying corresponding diagnostic options and parameter adjustment interfaces after selecting a vehicle model.
[0070] Step S42: display the interactive controls corresponding to each of the vehicle models, and arrange the interactive controls in order of the diagnosis frequency.
[0071] In the app, more frequently used models are placed in more prominent and accessible positions, while less frequently diagnosed models are placed at the back. This arrangement logic helps improve the user experience and allows users to find the relevant controls for the models they need to diagnose most frequently more quickly.
[0072] This embodiment uses the above method to put the frequently used vehicle model interaction controls in front, which reduces the user's search time and makes daily operations smoother and faster.
[0073] In one embodiment, the interactive control is used to move to a corresponding position in response to a dragging operation of the user.
[0074] In the application, the user can directly click and hold the control with the mouse (in desktop applications) or the finger (on a touch screen device), and then move it to any allowed position on the screen and release it, and the control will remain in this new position. This design allows users to customize the interface layout according to personal habits or current task requirements, increasing the intuitiveness and flexibility of interaction.
[0075] In one embodiment, the method is configured to be executed when a car diagnostic APP is started.
[0076] like Figure 7 As shown, the vehicle diagnostic entry device 100 provided in the embodiment of the present application includes:
[0077] Analysis module 101, used to obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period;
[0078] A download module 102 is used to obtain diagnostic software data corresponding to the vehicle model;
[0079] A connection module 103 for connecting to a diagnostic connector of a vehicle;
[0080] The output module 104 is used to generate and display one or more interactive controls, each of which is used for the user to trigger entering the diagnostic menu homepage of the corresponding vehicle model, and the diagnostic menu homepage is used for the user to trigger the execution of the diagnostic operation of the vehicle model, and the diagnostic operation of the vehicle model includes diagnosing the vehicle model using the diagnostic software data corresponding to the vehicle model.
[0081] In one embodiment, a startup module is further included, which is used to start the diagnostic interface and run the diagnostic interface in the background after the download module 102 obtains the diagnostic software data corresponding to the vehicle model.
[0082] In one embodiment, the analysis module 101 is further used for:
[0083] Get the user's car diagnostic history data within a specified time period;
[0084] The automobile diagnosis history data is analyzed to obtain one or more vehicle models with the highest diagnosis frequency.
[0085] In one embodiment, the download module 102 is further used for:
[0086] When the local database of the terminal device stores the diagnostic software data corresponding to the vehicle model, acquiring the diagnostic software data from the local database;
[0087] When the diagnostic software data corresponding to the vehicle model is not stored in the local database of the terminal device, the diagnostic software data is downloaded from the cloud to the local database, and the diagnostic software data is obtained from the local database.
[0088] In one embodiment, the connection module 103 is further configured to:
[0089] When the Bluetooth function is turned on, pair with the car's diagnostic connector and establish a connection;
[0090] When the Bluetooth function is turned off, it automatically turns on the Bluetooth function, pairs with the car's diagnostic connector, and establishes a connection.
[0091] In one embodiment, the output module 104 is further configured to:
[0092] Generating one interactive control for each vehicle type;
[0093] The interactive controls corresponding to each vehicle model are displayed, and the interactive controls are arranged in order of the diagnostic frequency.
[0094] In one embodiment, the output module 104 is further configured to move a corresponding position in response to a dragging operation by the user.
[0095] like Figure 8 As shown, the embodiment of the present application further provides a terminal device 200, including: at least one processor 201 ( Figure 8 Only one processor is shown in the figure), a memory 202, and a computer program 203 stored in the memory 202 and executable on at least one processor 201, wherein the processor 201 implements the steps in the above-mentioned various method embodiments when executing the computer program 203.
[0096] In the application, the terminal device may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that Figure 8 It is only an example of a terminal device and does not constitute a limitation on the terminal device. It 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.
[0097] In applications, the processor 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, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0098] In applications, the memory may be an internal storage unit of a terminal device in some embodiments, such as a hard disk or memory of the terminal device. In other embodiments, the memory may also be an external storage device of the terminal device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the terminal device. Further, the memory may also include both an internal storage unit of the terminal device and an external storage device. The memory is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as program codes of a computer program. The memory may also be used to temporarily store data that has been output or is to be output.
[0099] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.
[0100] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be 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 in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in 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, which will not be repeated here.
[0101] An embodiment of the present application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on at least one processor, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.
[0102] The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.
[0103] An embodiment of the present application provides a computer program product. When the computer program product runs on a terminal device, the terminal device can implement the steps in the above-mentioned method embodiments when executing the computer program product.
[0104] If the integrated 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 processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.
[0105] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0106] Those of ordinary skill 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 to be beyond the scope of this application.
[0107] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, 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.
[0108] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0109] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A method for entering automobile diagnosis, characterized in that: Applied to a terminal device, the method comprises: Obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period; Obtaining diagnostic software data corresponding to the vehicle model; Connects to the car's diagnostic connector; Generate and display one or more interactive controls, each of which is used for the user to trigger entry into the diagnostic menu homepage of the corresponding vehicle type, and the diagnostic menu homepage is used for the user to trigger execution of diagnostic operations for the vehicle type, and the diagnostic operations for the vehicle type include diagnosing the vehicle type using diagnostic software data corresponding to the vehicle type.
2. The vehicle diagnostic entry method according to claim 1, characterized in that: The step of obtaining one or more vehicle models with the highest diagnosis frequency within a time period specified by a user includes: Get the user's car diagnostic history data within a specified time period; The automobile diagnosis history data is analyzed to obtain one or more vehicle models with the highest diagnosis frequency.
3. The vehicle diagnostic entry method according to claim 1, characterized in that: The step of obtaining the diagnostic software data corresponding to the vehicle model includes: When the local database of the terminal device stores the diagnostic software data corresponding to the vehicle model, acquiring the diagnostic software data from the local database; When the diagnostic software data corresponding to the vehicle model is not stored in the local database of the terminal device, the diagnostic software data is downloaded from the cloud to the local database, and the diagnostic software data is obtained from the local database.
4. The vehicle diagnostic entry method according to claim 1, characterized in that: After obtaining the diagnostic software data corresponding to the vehicle model, the method further includes: A diagnostic interface is launched and runs in the background.
5. The vehicle diagnostic entry method according to claim 1, characterized in that: The diagnostic connector connected to the vehicle includes: When the Bluetooth function is turned on, pair with the car's diagnostic connector and establish a connection; When the Bluetooth function is turned off, it automatically turns on the Bluetooth function, pairs with the car's diagnostic connector, and establishes a connection.
6. The vehicle diagnostic entry method as claimed in claim 1, characterized in that: The generating and displaying one or more interactive controls includes: Generating one interactive control for each vehicle type; The interactive controls corresponding to each vehicle model are displayed, and the interactive controls are arranged in order of the diagnostic frequency.
7. The vehicle diagnostic entry method as claimed in claim 1, characterized in that: The interactive control is used to move to a corresponding position in response to a user's dragging operation.
8. The vehicle diagnostic entry method as claimed in claim 1, characterized in that: The method is used to be executed when the automobile diagnosis APP is started.
9. An automobile diagnostic entry device, characterized in that: include: An analysis module, used to obtain one or more vehicle models with the highest diagnosis frequency by the user within a specified time period; A download module, used to obtain diagnostic software data corresponding to the vehicle model; a connection module for connecting to the vehicle's diagnostic connector; An output module is used to generate and display one or more interactive controls, each of which is used for a user to trigger entry into a diagnostic menu homepage of a corresponding vehicle type, and the diagnostic menu homepage is used for a user to trigger execution of a diagnostic operation of the vehicle type, and the diagnostic operation of the vehicle type includes diagnosing the vehicle type using diagnostic software data corresponding to the vehicle type.
10. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the vehicle diagnostic entry method according to any one of claims 1 to 8 are implemented.
Citation Information
Patent Citations
Intelligent sorting method applied to automobile diagnosis equipment and automobile diagnosis equipment
CN103076801A
Vehicle diagnosis method, vehicle diagnosis device, computer equipment and storage medium
CN112519704A
Vehicle diagnosis method, device, equipment and medium
CN112729868A
Vehicle rapid diagnosis method based on historical vehicle types and related device
CN118012016A
Automobile failure diagnosing device, automobile data center and automobile failure diagnosing system
JP2003114943A
