Software display method, device, equipment and storage medium

Abstract

This application provides a software display method, apparatus, device, and storage medium. These methods obtain user feature information; determine user identity information based on the user feature information; and prioritize software categories for display based on the user identity information. By prioritizing software categories based on user identity information, users of different identities can quickly and accurately find the software they need, thereby improving the user experience.

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnostic technology, and in particular to a software display method, device, equipment and storage medium. Background Art

[0002] With the increasing popularity of vehicles and the continuous development of vehicle technology, vehicle diagnostic software has also seen significant development. However, as vehicle diagnostic software becomes increasingly diverse, users are faced with the problem of not knowing which vehicle diagnostic software to use, or having to browse through multiple pages to find the right vehicle diagnostic software, resulting in poor adaptability and wasted user time. Summary of the Invention

[0003] The embodiments of the present application provide a software display method, apparatus, device and storage medium, which can solve the problem of poor adaptability of vehicle diagnostic software in the prior art, which is caused by the diversity of vehicle diagnostic software and the inability of users to quickly and accurately find the required vehicle diagnostic software.

[0004] In a first aspect, the present application provides a software display method, comprising:

[0005] Obtain user feature information;

[0006] Determining user identity information based on the user characteristic information;

[0007] The software category to be displayed first is determined according to the user identity information.

[0008] Optionally, the user characteristic information includes the number of vehicle models corresponding to the software purchased by the user; and determining the user identity information based on the user characteristic information includes:

[0009] If the number of vehicle models corresponding to the software purchased by the user is greater than a preset threshold, the user identity information is determined to be the first user;

[0010] If the number of vehicle models corresponding to the software purchased by the user is less than a preset threshold, the user identity information is determined to be the second user.

[0011] Optionally, the user characteristic information includes a frequency of software purchase by the user; and determining the user identity information based on the user characteristic information includes:

[0012] If the frequency of software purchase by the user is greater than a first preset frequency, determining that the user identity information is the first user;

[0013] If the frequency of software purchase by the user is less than the first preset frequency, the user identity information is determined to be the second user.

[0014] Optionally, the user characteristic information includes a frequency of the user using the software; and determining the user identity information based on the user characteristic information includes:

[0015] If the user's frequency of using the software is greater than a second preset frequency, determining that the user identity information is the first user;

[0016] If the frequency of the user using the software is less than a second preset frequency, the user identity information is determined to be the second user.

[0017] Optionally, determining the software category to be displayed preferentially based on the user identity information includes:

[0018] If the user identity information is the first user, determining that the software category to be displayed first is unpurchased software;

[0019] If the user identity information is that of the second user, it is determined that the software category to be displayed first is purchased software.

[0020] Optionally, after determining that the software category to be displayed preferentially is unpurchased software if the user identity information is the first user, the method further includes:

[0021] The unpurchased software is sorted according to a preset first sorting rule, and the sorted first software list is displayed on a preset software interface.

[0022] Optionally, after determining that the software category to be displayed preferentially has been purchased if the user identity information is that of the second user, the method further includes:

[0023] The purchased software is sorted according to a preset second sorting rule, and the sorted second software list is displayed on the preset software interface.

[0024] In a second aspect, an embodiment of the present application provides a software display device, comprising:

[0025] Acquisition module, used to obtain user feature information;

[0026] A first determining module, configured to determine user identity information based on the user characteristic information;

[0027] The second determining module is used to determine the software category to be displayed preferentially according to the user identity information.

[0028] Optionally, the user characteristic information includes the number of vehicle models corresponding to the software purchased by the user; the first determining module includes:

[0029] A first determining unit is configured to determine that the user identity information is a first user if the number of vehicle models corresponding to the software purchased by the user is greater than a preset threshold;

[0030] The second determining unit is configured to determine that the user identity information is a second user if the number of vehicle models corresponding to the software purchased by the user is less than a preset threshold.

[0031] Optionally, the user characteristic information includes the frequency of the user purchasing software; and the first determining module includes:

[0032] a third determining unit, configured to determine that the user identity information is the first user if the frequency of software purchase by the user is greater than a first preset frequency;

[0033] The fourth determining unit is configured to determine that the user identity information is a second user if the frequency of software purchase by the user is less than a first preset frequency.

[0034] Optionally, the user characteristic information includes a frequency of software use by the user; and the first determining module includes:

[0035] a fifth determining unit, configured to determine that the user identity information is the first user if the frequency of the user using the software is greater than a second preset frequency;

[0036] The sixth determining unit is configured to determine that the user identity information is a second user if the frequency of the user using the software is less than a second preset frequency.

[0037] Optionally, the second determining module includes:

[0038] A first display unit is configured to determine that the software category to be displayed preferentially is unpurchased software if the user identity information is the first user;

[0039] The second display unit is configured to determine the purchased software to be displayed in a priority category if the user identity information is that of a second user.

[0040] Optionally, the software display device further includes:

[0041] The first sorting module is used to sort the unpurchased software according to a preset first sorting rule, and display the sorted first software list on a preset software interface.

[0042] Optionally, the software display device further includes:

[0043] The second sorting module is used to sort the purchased software according to a preset second sorting rule, and display the sorted second software list on the preset software interface.

[0044] In a third aspect, the present application provides a software display device, comprising:

[0045] A memory, used for storing a software display program;

[0046] The processor is configured to implement the steps of the software display method described in the first aspect above when executing the software display program.

[0047] In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program product. When the computer program product runs on a software display device, the software display device executes the steps of the software display method described in the first aspect above.

[0048] The software display method provided in the first aspect of this application obtains user feature information; determines user identity information based on the user feature information; and determines the software categories to be displayed preferentially based on the user identity information. By determining the software categories to be displayed preferentially based on the user identity information, users of different identities can quickly and accurately find the software they need, thereby improving the user experience.

[0049] 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

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings to be used in support of the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0051] Figure 1 It is a flowchart of the implementation of the software display method provided in the application embodiment;

[0052] Figure 2 This is a schematic diagram of the implementation flow of a software display method provided in another embodiment of the present application;

[0053] Figure 3 is a schematic diagram of a software display device provided in an embodiment of the present application;

[0054] Figure 4 This is a schematic diagram of a software display device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In the following description, for the purpose of illustration rather than limitation, specific details such as specific system structures and technologies are provided 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 can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obstructing the description of the present application with unnecessary details. It should be understood that 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 are not to be understood as indicating or implying relative importance.

[0056] It should also be understood that references to "one embodiment" or "some embodiments" 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. It should also be noted that, for ease of description, only parts related to the present invention, not all of the content, are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the various operations (or steps) as sequential processes, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of the various operations can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0057] See also Figure 1 , Figure 1 This is a flowchart of the implementation of the software display method provided in the embodiment of the application. It should be noted that the software display method provided in the embodiment of the present application is implemented by a software display device. The software display device can be a server or a terminal. The server can be a single server or a server cluster, and the terminal can be a handheld device, a personal computer, a notebook, a robot or a wearable smart device. Figure 1 It can be seen that the software display method provided in the embodiment of the present application includes steps S101 to S103. The details are as follows:

[0058] S101: Obtain user feature information.

[0059] In this embodiment, user characteristic information includes, but is not limited to, one or a combination of the following: the number of vehicle models corresponding to the software purchased by the user, the frequency with which the user purchases the software, and the frequency with which the user uses the software. The user characteristic information can be obtained based on the information entered by the user when registering and logging into the vehicle diagnostic application app, or it can be inferred from the information entered by the user. For example, after the user installs and logs into the vehicle diagnostic application app, the user may be prompted to enter some vehicle information and information about the vehicle diagnostic software that the user is interested in. The user characteristic information can then be inferred based on the vehicle information and / or vehicle diagnostic software information entered by the user.

[0060] S102: Determine user identity information based on the user feature information.

[0061] Among them, the user identity information includes the first user and the second user. Exemplarily, in this embodiment, it is assumed that the first user is a technician and the second user is a car owner. It is understandable that under normal circumstances, car owners usually purchase vehicle diagnostic software for the car models they own, and technicians usually need to purchase vehicle diagnostic software for all car models involved in their work, and the number of car models owned by ordinary car owners is generally less than the number of car models involved in the work of technicians. Therefore, the user identity information can be determined as the car owner or technician based on the number of car models corresponding to the software purchased by the user. Specifically, if the number of car models corresponding to the software purchased by the user is greater than a preset threshold, the user identity information is determined to be the first user; if the number of car models corresponding to the software purchased by the user is less than the preset threshold, the user identity information is determined to be the second user. Among them, the preset threshold can be a value pre-statistically obtained based on the number of car models corresponding to the software purchased by the car owner and the number of car models corresponding to the software purchased by the technician, such as a preset threshold of 2 or 3.

[0062] Furthermore, once a car owner purchases vehicle diagnostic software for a specific vehicle model, they typically won't purchase other vehicle diagnostic software for the duration of the vehicle's use. However, technicians frequently purchase software for multiple vehicle models due to work needs. Therefore, user identity information can also be determined based on the frequency with which the user purchases software. Specifically, if the user's software purchase frequency is greater than a first preset frequency, the user identity information is determined to be that of the first user; if the user's software purchase frequency is less than the first preset frequency, the user identity information is determined to be that of the second user. The first preset frequency is a value pre-calculated based on the frequency of software purchases by the car owner and the frequency of software purchases by the technician. For example, the first preset frequency can be two or three months.

[0063] In addition, the frequency with which car owners and technicians use functional software is also different. Car owners usually do not use software frequently, while technicians frequently use various software. Therefore, the user identity information can also be determined based on the frequency with which the user uses the software. Specifically, if the frequency with which the user uses the software is greater than the second preset frequency, the user identity information is determined to be the first user; if the frequency with which the user uses the software is less than the second preset frequency, the user identity information is determined to be the second user. Similarly, the second preset frequency is a value pre-calculated based on the frequency with which the car owner uses the software and the frequency with which the technician uses the software. For example, the second preset frequency is 3 days or 7 days, etc.

[0064] Of course, the user's identity information can be determined by combining the number of car models corresponding to the software purchased by the user, the frequency of the user's purchase of the software, and the frequency of the user's use of the software. Specifically, there is no limitation on the combination of the number of car models corresponding to the software purchased by the user, the frequency of the user's purchase of the software, and the frequency of the user's use of the software. It can be any two combinations or a combination of three. For example, if the user only purchases vehicle diagnostic software for "BMW series" and the frequency of using the vehicle diagnostic software for "BMW series" is less than the second preset frequency, then the user's identity information is the owner of the car. For another example, if the user purchases vehicle diagnostic software for multiple models such as "BMW series", "Mercedes-Benz series", and "Porsche series", and the frequency of using the purchased vehicle diagnostic software for multiple models is greater than the second preset frequency, then the user's identity information is a technician.

[0065] S103: Determine the software category to be displayed preferentially according to the user identity information.

[0066] Since car owners purchase software less frequently than technicians, the frequency of software purchases by technicians is higher. Therefore, the categories of unpurchased software can be prioritized for technicians, while the categories of purchased software can be prioritized for car owners. Specifically, if the user identity information is that of the first user (technician), the priority displayed software category is determined to be unpurchased software; if the user identity information is that of the second user (car owner), the priority displayed software category is determined to be purchased software.

[0067] From the above analysis, it can be seen that the software display method provided in the embodiments of the present application obtains user feature information; determines user identity information based on the user feature information; and determines the software categories to be displayed preferentially based on the user identity information. By determining the software categories to be displayed preferentially based on the user identity information, users of different identities can quickly and accurately find the software they need, thereby improving the user experience.

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

[0069] See also Figure 2 As shown, Figure 2 This is a schematic diagram of the implementation flow of the vehicle software display method provided by another embodiment of the present application. Figure 2 It can be seen that this embodiment is Figure 1 Compared with the embodiment shown, the specific implementation process of S201 to S203 is the same as that of S101 to S103, except that S204 and S205 are included after S203. The details are as follows:

[0070] S201: Obtain user feature information.

[0071] S202: Determine user identity information based on the user feature information.

[0072] S203: Determine a software category to be displayed preferentially according to the user identity information.

[0073] S204: Sort the unpurchased software according to a preset first sorting rule, and display the sorted first software list on a preset software interface.

[0074] The first sorting rule may be to obtain a preset number of unpurchased software with popularity exceeding a preset value based on the popularity of each software within a preset time period, and then sort the preset number of unpurchased software from highest to lowest popularity. For example, if the preset time period is 1 month and the preset number is 10, the 10 most popular software within the month are sorted by popularity, and the remaining software can be sorted by the software's initial letter, and the sorted first software list is displayed on the preset software interface.

[0075] In addition, controls, buttons, etc. for prompting users to trigger the purchased software list can be provided on the preset software interface, such as a button engraved with "Purchased Software", which makes it easy for the first user to jump to the purchased software category list. At the same time, the purchased software can be intelligently sorted, for example, sorted by purchase status (purchased by day, buyout, buyout expired and / or purchase expired by day, etc.) and / or frequency of use, etc.

[0076] S205: Sort the purchased software according to a preset second sorting rule, and display the sorted second software list on the preset software interface.

[0077] The preset second sorting rule is to sort the purchased software according to the purchase status and / or usage frequency, and display the sorted second software list on the preset software display interface. The software button size can also be selectively increased for user convenience. In addition, a control or button is provided on the preset software interface to prompt the user to enter the list of unpurchased software, so that the user can easily make the list of unpurchased software. Correspondingly, the unpurchased software can be intelligently sorted. For example, if the popular software in the past month is "BMW", "Mercedes-Benz", "Porsche", "Volkswagen", "BYD", "Honda", "Great Wall Motors", "Hyundai", "Audi", and "Ferrari", then we will display these 10 software first, and the other software will be sorted alphabetically.

[0078] From the above analysis, it can be seen that the software display method provided in the embodiments of the present application not only obtains user feature information, determines user identity information based on the user feature information, and determines the software categories to be displayed preferentially based on the user identity information, but also enables users of different identities to quickly and accurately find the software they need, thereby improving the adaptability of the software. Furthermore, it can display different software sorting lists for users of different identities through a preset software interface, thereby improving the user experience.

[0079] Based on the software display method provided in the above embodiment, the embodiment of the present invention further provides an embodiment of a device for implementing the above method embodiment.

[0080] like Figure 3 As shown, Figure 3 Schematic diagram of the software display device provided in the embodiment of the present application. The modules included are used to execute Figure 1 or Figure 2 Each step in the corresponding embodiment. Please refer to Figure 1 or Figure 2 For the convenience of explanation, only the parts related to this embodiment are shown. Figure 3 , the software display device 300 includes:

[0081] Acquisition module 301, used to acquire user feature information;

[0082] A first determining module 302 is configured to determine user identity information based on the user characteristic information;

[0083] The second determining module 303 is configured to determine a software category to be displayed preferentially according to the user identity information.

[0084] Optionally, the user characteristic information includes the number of vehicle models corresponding to the software purchased by the user; the first determining module 302 includes:

[0085] A first determining unit is configured to determine that the user identity information is a first user if the number of vehicle models corresponding to the software purchased by the user is greater than a preset threshold;

[0086] The second determining unit is configured to determine that the user identity information is a second user if the number of vehicle models corresponding to the software purchased by the user is less than a preset threshold.

[0087] Optionally, the user characteristic information includes the frequency of the user purchasing software; the first determining module 302 includes:

[0088] a third determining unit, configured to determine that the user identity information is the first user if the frequency of software purchase by the user is greater than a first preset frequency;

[0089] The fourth determining unit is configured to determine that the user identity information is a second user if the frequency of software purchase by the user is less than a first preset frequency.

[0090] Optionally, the user characteristic information includes the frequency of the user using the software; the first determining module 302 includes:

[0091] a fifth determining unit, configured to determine that the user identity information is the first user if the frequency of the user using the software is greater than a second preset frequency;

[0092] The sixth determining unit is configured to determine that the user identity information is a second user if the frequency of the user using the software is less than a second preset frequency.

[0093] Optionally, the second determining module 303 includes:

[0094] A first display unit is configured to determine that the software category to be displayed preferentially is unpurchased software if the user identity information is the first user;

[0095] The second display unit is configured to determine the purchased software to be displayed in a priority category if the user identity information is that of a second user.

[0096] Optionally, the software display device further includes:

[0097] The first sorting module is used to sort the unpurchased software according to a preset first sorting rule, and display the sorted first software list on a preset software interface.

[0098] Optionally, the software display device further includes:

[0099] The second sorting module is used to sort the purchased software according to a preset second sorting rule, and display the sorted second software list on the preset software interface.

[0100] It should be noted that the information interaction and execution process between the above modules are not related to this application. Figure 1 or Figure 2 The method embodiments shown are based on the same concept. For their specific functions and technical effects, please refer to the method embodiment section and will not be repeated here.

[0101] Figure 4 Schematic diagram of the software display device provided in the embodiment of the present application. Figure 4 As shown, the software display device 4 of this embodiment includes: a processor 400, a memory 401, and a computer program 402 stored in the memory 401 and capable of running on the processor 400, such as a software display program. When the processor 400 executes the computer program 402, the above Figure 1 or Figure 2 Alternatively, the processor 400 implements the above when executing the computer program 402. Figure 3 Functions of each module / unit in the embodiment.

[0102] Exemplarily, the computer program 402 may be divided into one or more modules / units, which are stored in the memory 401 and executed by the processor 400 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 402 in the software display device 4. For example, the computer program 402 may be divided into an acquisition module, a first determination module, and a second determination module. For the specific functions of each module, please refer to Figure 3 The relevant descriptions in the corresponding embodiments are not repeated here.

[0103] The software display device 4 may include, but is not limited to, a processor 400 and a memory 401. Those skilled in the art will appreciate that Figure 4 It is only an example of the software display device 4 and does not constitute a limitation of the software display device 4. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the software display device may also include input and output devices, network access devices, buses, etc.

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

[0105] The memory 401 may be an internal storage unit of the software display device 4, such as a hard disk or memory of the software display device 4. The memory 401 may also be an external storage device of the software display device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the software display device 4. Furthermore, the memory 401 may include both an internal storage unit of the software display device 4 and an external storage device. The memory 401 is used to store the computer program 402 and other programs and data supported by the software display device 4. The memory 401 may also be used to temporarily store data that has been output or is about to be output.

[0106] An embodiment of the present application further provides a computer-readable storage medium storing a computer program. When the computer program product is run on a software display device, the software display device executes the steps of the above-mentioned software display method.

[0107] Those skilled in the art 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 actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a vehicle diagnostic software functional unit. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

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

[0109] Those skilled in the art will appreciate that the various exemplary units and algorithmic steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer vehicle diagnostic software and electronic hardware. Whether these functions are implemented using hardware or vehicle diagnostic software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0110] The above-described 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 various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A software display method, characterized in that: include: Obtain user feature information; The user characteristic information includes: the number of vehicle models corresponding to the vehicle diagnostic software purchased by the user, the frequency of the user purchasing the vehicle diagnostic software, and the frequency of the user using the vehicle diagnostic software; Determining user identity information based on the user characteristic information; the user identity information is the vehicle owner or the technician; Determining the software category to be displayed first based on the user identity information; determining the software category to be displayed first based on the user identity information includes: prioritizing displaying unpurchased vehicle diagnostic software for technicians, and prioritizing displaying purchased vehicle diagnostic software for vehicle owners.

2. The method according to claim 1, characterized in that The determining of user identity information based on the user characteristic information includes: If the number of vehicle models corresponding to the vehicle diagnostic software purchased by the user is greater than a preset threshold, determining that the user identity information is the first user; If the number of vehicle models corresponding to the vehicle diagnostic software purchased by the user is less than a preset threshold, the user identity information is determined to be the second user.

3. The method according to claim 1, characterized in that The determining of user identity information based on the user characteristic information includes: If the frequency of the user purchasing vehicle diagnostic software is greater than a first preset frequency, determining the user identity information as the first user; If the frequency of the user purchasing vehicle diagnostic software is less than the first preset frequency, the user identity information is determined to be the second user.

4. The method according to claim 1, wherein The determining of user identity information based on the user characteristic information includes: If the frequency of the user using the vehicle diagnostic software is greater than a second preset frequency, determining that the user identity information is the first user; If the frequency of the user using the vehicle diagnostic software is less than a second preset frequency, the user identity information is determined to be the second user.

5. The method according to any one of claims 1 to 4, characterized in that Prioritize the display of vehicle diagnostic software that has not been purchased, including: The unpurchased vehicle diagnostic software is sorted according to a preset first sorting rule, and the sorted first software list is displayed on a preset software interface.

6. The method according to any one of claims 1 to 4, characterized in that Prioritize the display of purchased vehicle diagnostic software, including: The purchased vehicle diagnostic software is sorted according to a preset second sorting rule, and the sorted second software list is displayed on a preset software interface.

7. A software display device, characterized in that: include: Acquisition module, used to obtain user feature information; The user characteristic information includes: the number of vehicle models corresponding to the vehicle diagnostic software purchased by the user, the frequency of the user purchasing the vehicle diagnostic software, and the frequency of the user using the vehicle diagnostic software; A first determining module is configured to determine user identity information based on the user characteristic information; the user identity information is a vehicle owner or a technician; The second determination module is used to determine the software category to be displayed first according to the user identity information; the software category to be displayed first according to the user identity information includes: prioritizing the display of non-purchased vehicle diagnostic software for technicians and prioritizing the display of purchased vehicle diagnostic software for vehicle owners.

8. A software display device, characterized in that: include: A memory, used for storing a software display program; A processor, configured to execute the steps of the software display method according to any one of claims 1 to 6 when executing the software display program.

9. A computer-readable storage medium storing a computer program product, characterized in that: When the computer program product is run on a software display device, the software display device is caused to execute the steps of the software display method according to any one of claims 1 to 6.

Images