CN106020915B - Driver installation method and device - Google Patents
Driver installation method and device Download PDFInfo
- Publication number
- CN106020915B CN106020915B CN201610409439.9A CN201610409439A CN106020915B CN 106020915 B CN106020915 B CN 106020915B CN 201610409439 A CN201610409439 A CN 201610409439A CN 106020915 B CN106020915 B CN 106020915B
- Authority
- CN
- China
- Prior art keywords
- driver
- identifier
- determining
- terminal equipment
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a driver installation method and a driver installation device, wherein the method comprises the following steps: determining an identifier of a driver to be installed; determining the storage position of the driver to be installed according to the identifier of the driver to be installed; and acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed. The method effectively reduces the volume of the off-line driving program driving package, reduces the upgrading time of the off-line driving program driving package and improves the upgrading efficiency of the driving package on the premise of ensuring the normal use of the off-line driving program.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for installing a driver.
Background
Currently, a system maintenance person usually uses a driver package of an off-line driver to reinstall or restore a system of a terminal device (e.g., a personal computer) so as to make a related hardware device work normally. This makes the drive package of the offline driver itself very bulky, which makes the offline driver time-consuming and inefficient when upgrading the drive package.
Disclosure of Invention
The object of the present application is to solve at least to some extent one of the technical problems described above.
Therefore, a first objective of the present application is to provide a driver installation method, which effectively reduces the volume of an offline driver package, reduces the upgrade time of the offline driver package on the premise of ensuring normal use of the offline driver, and improves the upgrade efficiency of the driver package.
A second object of the present application is to provide a driver installation apparatus.
To achieve the above object, an offline driver installation method according to an embodiment of the first aspect of the present application includes: determining an identifier of a driver to be installed; determining the storage position of the driver to be installed according to the identifier of the driver to be installed; and acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed.
The method for installing the driver program comprises the steps of firstly determining the identifier of the driver program to be installed, then determining the storage position of the driver program to be installed according to the identifier of the driver program to be installed, and then obtaining the driver program corresponding to the identifier of the driver program to be installed according to the storage position of the driver program to be installed. According to the method, different drivers to be installed are obtained from different positions according to the identifiers of the drivers to be installed, so that the driver packages of the offline drivers can be classified and stored, the size of the driver packages of the offline drivers is effectively reduced, the upgrading time of the driver packages of the offline drivers is reduced on the premise of ensuring the normal use of the offline drivers, and the upgrading efficiency of the driver packages is improved.
In addition, the installation method of the driver in the embodiment of the application has the following additional technical features:
in an embodiment of the application, the determining an identifier of a driver to be installed includes: receiving a driver installation request, wherein the installation request comprises an identifier of a driver to be installed; determining the identifier of the driver to be installed according to the driver installation request; or, acquiring an operating system version and a hardware identifier of the terminal device; and determining the identifier of the driver to be installed according to the operating system version and the hardware identifier of the terminal equipment.
In an embodiment of the application, the determining, according to the identifier of the driver to be installed, a storage location of the driver to be installed includes: judging whether the identifier of the driver to be installed is in a preset driver list or is marked; and if so, determining that the driver corresponding to the identifier of the driver to be installed is stored in the terminal equipment.
In one embodiment of the present application, the method further comprises: the storage location according to the respective driver.
In one embodiment of the present application, determining the storage location of each driver according to the update frequency and/or user feedback of each driver includes: judging whether the updating frequency of any one drive program is smaller than a preset value or not, and if so, storing the any one drive program in the terminal equipment;
and/or judging whether the user feedback corresponding to any one of the driving programs meets a preset condition, and if so, storing the any one of the driving programs in the terminal equipment.
In an embodiment of the application, after determining the storage location of each driver according to the update frequency and/or the user feedback of each driver, the method further includes: receiving a driver program updating request, wherein the updating request carries a driver program identifier to be updated; judging whether the driver identifier to be updated is in the preset driver list or is marked; and if not, updating the driver program to be updated.
In one embodiment of the present application, further comprising: if the driver corresponding to the identifier of the driver to be installed is not found, sending an inquiry message to the user; and acquiring the driver corresponding to the identifier of the driver to be installed according to the search catalog input by the user.
To achieve the above object, an offline driver installing apparatus according to an embodiment of the second aspect of the present application includes: the first determining module is used for determining the identifier of the driver to be installed; the second determining module is used for determining the storage position of the driver to be installed according to the identifier of the driver to be installed; and the first acquisition module is used for acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed.
The driver installation device of the embodiment of the application determines the identifier of the driver to be installed, determines the storage position of the driver to be installed according to the identifier of the driver to be installed, and acquires the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed. The device acquires different drivers to be installed from different positions according to the identifiers of the drivers to be installed, so that the driver packages of the offline drivers can be classified and stored, the size of the driver packages of the offline drivers is effectively reduced, the upgrading time of the driver packages of the offline drivers is shortened on the premise of ensuring the normal use of the offline drivers, and the upgrading efficiency of the driver packages is improved.
In addition, in the driver installation apparatus according to an embodiment of the present application, the first determining module includes: the device comprises a receiving unit, a judging unit and a processing unit, wherein the receiving unit is used for receiving a driver installation request which comprises an identifier of a driver to be installed; the first determining unit is used for determining the identifier of the driver to be installed according to the driver installation request; or, the obtaining unit is used for obtaining the operating system version and the hardware identifier of the terminal device; and the second determining unit is used for determining the identifier of the driver to be installed according to the operating system version and the hardware identifier of the terminal equipment.
In one embodiment of the present application, the second determining module is configured to: judging whether the identifier of the driver to be installed is in a preset driver list or is marked; and if so, determining that the driver corresponding to the identifier of the driver to be installed is stored in the terminal equipment.
In an embodiment of the application, the second determining module is further configured to: and determining the storage position of each driver according to the update frequency and/or user feedback of each driver.
In an embodiment of the application, the second determining module is specifically configured to: judging whether the updating frequency of any one of the driving programs is smaller than a preset value or not; when the updating frequency of any one of the driving programs is smaller than a preset value, the driving program is stored in the terminal equipment; and/or the determining module is further configured to determine whether the user feedback corresponding to any one of the drivers meets a preset condition; and when the user feedback corresponding to any one of the driving programs meets the preset condition, storing the any one of the driving programs in the terminal equipment.
In one embodiment of the present application, the second determining module further includes: the driver updating device further comprises a second receiving unit, which is used for receiving a driver updating request, wherein the updating request carries a driver identifier to be updated; the judging unit is used for judging whether the driver identifier to be updated is in the preset driver list or is marked; and the updating unit is used for updating the driver to be updated if the driver identifier to be updated is not in the preset driver list or is not marked.
In one embodiment of the present application, the apparatus further comprises: the sending module is used for sending an inquiry message to a user when the scanning module does not find the driver corresponding to the identifier of the driver to be installed; and the second acquisition module is used for acquiring the driving program corresponding to the identifier of the driving program to be installed according to the search catalog input by the user.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flow diagram of a driver installation method according to one embodiment of the present application;
FIGS. 2(a) - (b) are exemplary diagrams of a driver installation method according to a specific embodiment of the present application;
FIG. 3 is a flow diagram of a driver installation method according to one embodiment of the present application;
FIG. 4 is a schematic diagram of a driver installation apparatus according to an embodiment of the present application;
FIG. 5 is a block diagram of a driver installation apparatus according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a driver installation apparatus according to another embodiment of the present application;
FIG. 7 is a schematic structural diagram of a driver installation apparatus according to yet another embodiment of the present application; and
fig. 8 is a schematic structural diagram of a driver installation apparatus according to still another embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
The following describes a driver installation method and apparatus according to an embodiment of the present application with reference to the drawings.
FIG. 1 is a flow diagram of a driver installation method according to one embodiment of the present application.
As shown in fig. 1, the driver installation method includes:
and S110, determining the identification of the driver to be installed.
Specifically, the main execution body of the driver installation method provided by the embodiment of the present application is the driver installation device provided by the embodiment of the present application, and the device can be configured in any terminal having hardware requiring program driving.
It should be noted that the type of the terminal can be in various forms, such as a mobile phone or a computer device.
In general, a driver refers to a special program that enables a computer to communicate with a device. The hardware device is equivalent to a hardware interface, an operating system can control the work of the related hardware device only through the interface, and when a driver of one hardware device cannot be installed correctly, the hardware device cannot work normally.
The offline driver is a device with a general driver library, which can enumerate hardware devices of the terminal device and install the driver without a network.
Specifically, the terminal device may determine the identity of the driver to be installed in a variety of ways as follows.
Example one:
receiving a driver installation request, wherein the installation request comprises an identifier of a driver to be installed;
and determining the identifier of the driver to be installed according to the driver installation request.
The offline driver installation request may be sent by a user, or may be automatically triggered during the upgrade process of the terminal system. The embodiments of the present application do not limit this.
The identifier of the driver to be installed may be a name of the driver to be installed, an icon of the driver to be installed, or any other identifier that uniquely identifies the driver to be installed.
Example two:
acquiring an operating system version and a hardware identifier of terminal equipment;
and determining the identifier of the driver to be installed according to the operating system version and the hardware identifier of the terminal equipment.
Specifically, the driver installation apparatus may determine the operating system version and the hardware identifier of the terminal device by querying the attribute of the terminal device, and then determine the identifier of the driver matching the terminal device according to the operating system version and the hardware identifier.
And S120, determining the storage position of the driver to be installed according to the identifier of the driver to be installed.
Specifically, in the embodiment of the present application, the drivers are classified and stored according to the update frequency of the drivers and/or user feedback, for example, the drivers with low update frequency are stored in a fixed position in the terminal device, and the drivers with high update frequency are still stored in the driver package of the offline driver, so that the volume of the driver package of the offline driver is reduced, and the time for upgrading the offline driver is reduced.
In a specific implementation, the identifier of the driver at the fixed location stored in the terminal device may be put into a preset driver list, so as to determine whether the driver to be installed is stored at the fixed location of the terminal device by determining whether the identifier of the driver to be installed is in the preset driver list, or the identifier of the driver at the fixed location stored in the terminal device may be marked, so as to determine whether the driver to be installed is stored in the terminal device by determining whether the identifier of the driver to be installed is already marked.
Correspondingly, the method further comprises the following steps:
and determining the storage position of each driver according to the update frequency and/or user feedback of each driver.
Specifically, it is possible to determine whether a driver is frequently updated by determining whether the update frequency of any one driver is less than a preset value, and if the update frequency of the driver is less than the preset value, it is indicated that the driver belongs to a driver that does not need to be frequently updated, thereby storing the driver in the terminal device.
Or, it may be determined whether the user feedback corresponding to any one of the drivers meets a preset condition, for example, whether the score of the driver by the user is higher than a preset score or whether the satisfaction score of the user on the driver reaches a preset star level, and if the user feedback meets the preset condition, the driver is stored in the terminal device.
Accordingly, a driver with a high update frequency or poor user feedback may be stored in a driver package of the offline driver to reduce the volume of the driver package.
And S130, acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed.
Specifically, the driver installing device may obtain the driver corresponding to the identifier of the driver to be installed after determining the storage location of the driver to be installed according to the identifier of the driver to be installed, and then operate the driver.
For example, if the identifier of the driver to be installed is in the preset driver list, it indicates that the driver to be installed is stored in a certain directory of the terminal device, so that the driver corresponding to the driver to be installed can be obtained by scanning the terminal device.
In order to more clearly describe the driver installation method according to the embodiment of the present application, the following description is made with reference to fig. 2(a) -2 (b):
as shown in fig. 2(a), according to the update frequency of the driver, the driver id issued by a vendor in windows 764, such as sony, hewlett packard, etc. that is not updated frequently may be stored in a preset driver list, and the driver is stored in the computer/local disk (F)/drivers-plus/win7x 64/directory of the terminal device, so that when the driver installation request of any driver is received, it is determined by judgment that the driver id is in the preset driver list, and thus the display interface shown in fig. 2(B) can be obtained by scanning on the terminal device, and the path F where the driver to be installed is displayed in the B area in fig. 2(B) is obtained: and/drivers-plus/win 7x64/, so that the driver corresponding to the identifier of the driver to be installed can be obtained according to the path.
To sum up, in the driver installation method according to the embodiment of the present application, an identifier of a driver to be installed is first determined, then a storage location of the driver to be installed is determined according to the identifier of the driver to be installed, and then the driver corresponding to the identifier of the driver to be installed is obtained according to the storage location of the driver to be installed. According to the method, different drivers to be installed are obtained from different positions according to the identifiers of the drivers to be installed, so that the driver packages of the offline drivers can be classified and stored, the size of the driver packages of the offline drivers is effectively reduced, the upgrading time of the driver packages of the offline drivers is reduced on the premise of ensuring the normal use of the offline drivers, and the upgrading efficiency of the driver packages is improved.
As can be seen from the above analysis, the offline driver installation apparatus may classify, identify and store the drivers according to the update frequency of the drivers or user feedback, so as to reduce the volume and update time of the driver package in the offline driver, and the offline driver installation method provided in this embodiment further includes:
receiving a driver program updating request, wherein the updating request carries a driver program identifier to be updated;
judging whether the driver identifier to be updated is in the preset driver list or is marked;
and if not, updating the driver program to be updated.
Specifically, after determining drivers storable in the terminal device according to the update frequency and/or user feedback of each driver, when determining that there is an updatable version in the driver, only drivers whose driver identification is not in the preset driver list or is not marked may be updated, thereby greatly reducing the time for updating the driver package by the offline driver.
It should be noted that some drivers stored in the terminal device may issue a driver of an upgraded version with more comprehensive functions from a manufacturer, or an upgrade version with better user feedback appears, and in this case, the driver corresponding to the identifier of the driver stored in the driver list may also be updated and upgraded.
Based on the above embodiment, in practical applications, when a user stores a driver corresponding to an identifier of a driver to be installed in a certain storage location in a usb disk or a terminal device, the driver may not be scanned within a certain time, and therefore, in order to ensure normal installation of an offline driver, when the terminal device does not scan the driver to be installed, the user needs to manually input storage path information of the driver.
FIG. 3 is a flow diagram of a driver installation method according to a specific embodiment of the present application. As shown in fig. 3, the offline driver installation method includes:
s310, determining the identification of the driver to be installed.
S320, judging whether the identifier of the driver to be installed is in a preset driver list or marked.
And S330, if yes, determining that the driver corresponding to the identifier of the driver to be installed is stored in the terminal equipment.
And S340, if the driver corresponding to the identifier of the driver to be installed is not found in the terminal equipment, sending an inquiry message to the user.
Specifically, if the identifier of the driver to be installed is in a preset driver list or is already marked, the driver corresponding to the identifier is stored in a certain directory of the terminal device, so that the terminal device is scanned to obtain the driver to be installed.
And if the driver corresponding to the identifier of the driver to be installed is not found within a certain time, sending an inquiry message to the user. For example, a popup as shown in fig. 2(B) may be sent to the user, and the user may manually enter the search directory in the driver storage path input box B as shown in fig. 2(B) after receiving the popup message.
Among them, it should be understood that there may be various ways of sending the query message, and the above-described way of sending the query message to the user, which is illustrated in connection with fig. 2(b), is merely exemplary in order to make the technical features more apparent to those skilled in the art.
And S350, acquiring the driver corresponding to the identifier of the driver to be installed according to the search catalog input by the user.
Specifically, when the directory is searched by using the input, the driver corresponding to the identifier of the driver to be installed is searched according to the search directory.
To sum up, in the driver installation method according to the embodiment of the present application, after the terminal device does not scan the driver corresponding to the identifier of the driver to be installed, an inquiry message is sent to the user, and the driver corresponding to the identifier of the driver to be installed is obtained according to the search directory input by the user. The method further ensures the normal installation of the off-line driver and improves the practicability of the off-line driver.
In order to implement the above embodiments, the present application further provides an offline driver installing apparatus.
Fig. 4 is a schematic structural diagram of a driver installation apparatus according to an embodiment of the present application, and as shown in fig. 4, the driver installation apparatus includes: a first determination module 410, a second determination module 420, and a first acquisition module 430.
The first determining module 410 is configured to determine an identifier of a driver to be installed.
Specifically, the first determining module 410 may determine the identity of the driver to be installed in a number of ways.
Example one:
fig. 5 is a schematic structural diagram of a driver installation apparatus according to an embodiment of the present application, and as shown in fig. 5, based on fig. 4, the first determining module 410 includes: a receiving unit 411 and a first determining unit 412.
The receiving unit 411 is configured to receive a driver installation request, where the installation request includes an identifier of a driver to be installed;
the first determining unit 412 is configured to determine an identifier of a driver to be installed according to the driver installation request.
The offline driver installation request may be sent by a user, or may be automatically triggered during the upgrade process of the terminal system. The embodiments of the present application do not limit this.
The identifier of the driver to be installed may be a name of the driver to be installed, an icon of the driver to be installed, or any other identifier that uniquely identifies the driver to be installed.
Example two:
fig. 6 is a schematic structural diagram of a driver installation apparatus according to another embodiment of the present application, and as shown in fig. 6, on the basis of fig. 4, the first determining module 410 includes: an acquisition unit 413 and a second determination unit 414.
The obtaining unit 413 is configured to obtain an operating system version and a hardware identifier of the terminal device;
the second determining unit 414 is configured to determine an identifier of the driver to be installed according to the os version and the hardware identifier of the terminal device.
Specifically, the first determining module 410 may determine the operating system version and the hardware identifier of the terminal device by querying the attribute of the terminal device, and then determine the identifier of the driver matched with the terminal device according to the operating system version and the hardware identifier.
The second determining module 420 is configured to determine a storage location of the driver to be installed according to the identifier of the driver to be installed.
Specifically, in this embodiment of the application, the second determining module 420 stores the drivers in a classified manner according to the update frequency of the drivers and/or the user feedback, for example, the drivers with low update frequency are stored in a fixed position in the terminal device, and the drivers with high update frequency are still stored in the driver package of the offline driver, so that the volume of the driver package of the offline driver is reduced, and the time for upgrading the offline driver is reduced.
In a specific implementation, the identifier of the driver at the fixed location stored in the terminal device may be put into a preset driver list, so that the second determining module 420 determines whether the driver to be installed is stored at the fixed location of the terminal device by determining whether the identifier of the driver to be installed is in the preset driver list, or the identifier of the driver at the fixed location stored in the terminal device may be marked, so that the second determining module 420 determines whether the driver to be installed is stored in the terminal device by determining whether the identifier of the driver to be installed is already marked.
Further, the second determining module 420 is further configured to:
and determining the storage position of each driver according to the update frequency and/or user feedback of each driver.
Specifically, the second determining module 420 determines whether any one driver is frequently updated by determining whether the update frequency of the driver is less than a preset value, and if the update frequency of the driver is less than the preset value, it indicates that the driver belongs to a driver that does not need to be frequently installed, so as to store the driver in the terminal device.
Or the second determining module 420 determines whether the user feedback corresponding to any one of the drivers meets a preset condition, for example, determines whether the score of the driver by the user is higher than a preset score, or determines whether the satisfaction score of the user on the driver reaches a preset star level, and if the user feedback meets the preset condition, stores the driver in the terminal device.
Accordingly, the second determination module 420 may store a driver with a high update frequency or poor user feedback in the driver package of the offline driver to reduce the volume of the driver package.
The first obtaining module 430 is configured to obtain a driver corresponding to an identifier of the driver to be installed according to a storage location of the driver to be installed.
Specifically, the first obtaining module 430 may obtain the driver corresponding to the identifier of the driver to be installed after determining the storage location of the driver to be installed according to the identifier of the driver to be installed, and then operate the driver.
To sum up, the driver installation apparatus according to the embodiment of the present application first determines an identifier of a driver to be installed, then determines a storage location of the driver to be installed according to the identifier of the driver to be installed, and then obtains the driver corresponding to the identifier of the driver to be installed according to the storage location of the driver to be installed. The device acquires different drivers to be installed from different positions according to the identifiers of the drivers to be installed, so that the driver packages of the offline drivers can be classified and stored, the size of the driver packages of the offline drivers is effectively reduced, the upgrading time of the driver packages of the offline drivers is shortened on the premise of ensuring the normal use of the offline drivers, and the upgrading efficiency of the driver packages is improved.
As can be seen from the above analysis, the offline driver installation apparatus may classify, identify and store the drivers according to the update frequency or user feedback of the drivers, so as to reduce the volume and update time of the driver package in the offline driver, and accordingly fig. 7 is a schematic structural diagram of a driver installation apparatus according to another embodiment of the present application, as shown in fig. 7, based on fig. 4, the second determining module 420 provided in the embodiment of the present application further includes:
a second receiving unit 421, configured to receive a driver update request, where the update request carries a driver identifier to be updated;
a determining unit 422, configured to determine whether the driver identifier to be updated is in a preset driver list or is marked;
the updating unit 423 is configured to perform an update process on the driver to be updated if the driver identifier to be updated is not in the preset driver list or is not marked.
Specifically, after the second determining module 420 determines the drivers that can be stored in the terminal device according to the update frequency and/or user feedback of each driver, when determining that there is an updateable version in the driver, only the drivers whose driver identifications are not in the preset driver list or are not marked may be updated, thereby greatly reducing the time for updating the driver package by the offline driver.
It should be noted that some drivers stored in the terminal device may issue a driver of an upgraded version with more comprehensive functions from a manufacturer, or an upgrade version with better user feedback appears, and in this case, the driver corresponding to the identifier of the driver stored in the driver list may also be updated and upgraded.
Based on the above embodiment, in practical applications, when a user stores a driver corresponding to an identifier of a driver to be installed in a certain storage location in a usb disk or a terminal device, the driver may not be scanned within a certain time, and therefore, in order to ensure normal installation of an offline driver, when the terminal device does not scan the driver to be installed, the user needs to manually input storage path information of the driver.
Fig. 8 is a schematic structural diagram of a driver installation apparatus according to still another embodiment of the present application, and as shown in fig. 8, on the basis of fig. 4, the driver installation apparatus further includes a sending module 440 and a second obtaining module 450.
Specifically, if the second determining module 420 determines that the identifier of the driver to be installed is in the preset driver list, it indicates that the driver corresponding to the identifier is stored in a certain directory of the terminal device, so as to scan the terminal device to obtain the application to be installed.
If the driver corresponding to the identifier of the driver to be installed is not found within a certain time, the sending module 440 sends an inquiry message to the user.
Further, when the second obtaining module 450 searches the directory by using the input, the driver corresponding to the identifier of the driver to be installed is searched according to the directory.
It should be noted that the driver installation apparatus in the embodiment of the present application corresponds to the driver installation method described above with reference to fig. 1 to 3, and details that are not disclosed in the apparatus embodiment refer to the description of the method embodiment, and are not described herein again.
To sum up, the driver installation apparatus according to the embodiment of the present application sends an inquiry message to a user after the terminal device does not scan the driver corresponding to the identifier of the driver to be installed, and obtains the driver corresponding to the identifier of the driver to be installed according to the search directory input by the user. The device further ensures the normal installation of the off-line driver, and improves the practicability of the off-line driver installation device.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one first processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (8)
1. A driver installation method, comprising the steps of:
judging whether the updating frequency of each driving program is smaller than a preset value or not;
storing the driver with the update frequency smaller than a preset value in terminal equipment, storing any one of the drivers with the update frequency smaller than the preset value in a fixed position of the terminal equipment, putting an identifier of the driver stored in the fixed position of the terminal equipment into a preset driver list, receiving a driver update request, wherein the update request carries the identifier of the driver to be updated, judging whether the identifier of the driver to be updated is in the preset driver list or is marked, and if not, updating the driver to be updated;
storing the driving program with the updating frequency being more than or equal to a preset value in the terminal equipment, and storing any one of the driving programs with the updating frequency being more than or equal to the preset value in a driving package of an offline driving program;
determining an identifier of a driver to be installed;
determining the storage position of the driver to be installed according to the identifier of the driver to be installed;
and acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed.
2. The method of claim 1, wherein the determining an identity of a driver to install comprises:
receiving a driver installation request, wherein the installation request comprises an identifier of a driver to be installed;
determining the identifier of the driver to be installed according to the driver installation request;
or, acquiring an operating system version and a hardware identifier of the terminal device;
and determining the identifier of the driver to be installed according to the operating system version and the hardware identifier of the terminal equipment.
3. The method of claim 1, wherein determining a storage location of the driver to be installed based on the identification of the driver to be installed comprises:
judging whether the identifier of the driver to be installed is in a preset driver list or is marked;
and if so, determining that the driver corresponding to the identifier of the driver to be installed is stored in the terminal equipment.
4. The method of claim 3, further comprising:
if the driver corresponding to the identifier of the driver to be installed is not found in the terminal equipment, sending an inquiry message to a user;
and acquiring the driver corresponding to the identifier of the driver to be installed according to the search catalog input by the user.
5. A driver installation apparatus, comprising:
the judging module is used for judging whether the updating frequency of each driving program is smaller than a preset value or not;
the storage module is used for storing the driver with the updating frequency smaller than a preset value in the terminal equipment, storing any one of the drivers with the updating frequency smaller than the preset value in a fixed position of the terminal equipment, putting the identifier of the driver stored in the fixed position of the terminal equipment into a preset driver list, receiving a driver updating request, wherein the updating request carries the identifier of the driver to be updated, judging whether the identifier of the driver to be updated is in the preset driver list or is marked, and if not, updating the driver to be updated;
the storage module is further configured to store the driver with the update frequency greater than or equal to a preset value in the terminal device, and store any one of the drivers with the update frequency greater than or equal to the preset value in a driver package of an offline driver;
the determining module is used for determining the identifier of the driver to be installed and determining the storage position of the driver to be installed according to the identifier of the driver to be installed;
and the first acquisition module is used for acquiring the driver corresponding to the identifier of the driver to be installed according to the storage position of the driver to be installed.
6. The apparatus of claim 5, wherein the determining module comprises:
the device comprises a receiving unit, a judging unit and a processing unit, wherein the receiving unit is used for receiving a driver installation request which comprises an identifier of a driver to be installed;
the first determining unit is used for determining the identifier of the driver to be installed according to the driver installation request;
or, the obtaining unit is used for obtaining the operating system version and the hardware identifier of the terminal device;
and the second determining unit is used for determining the identifier of the driver to be installed according to the operating system version and the hardware identifier of the terminal equipment.
7. The apparatus of claim 5, wherein the determination module is to:
judging whether the identifier of the driver to be installed is in a preset driver list or is marked;
and if so, determining that the driver corresponding to the identifier of the driver to be installed is stored in the terminal equipment.
8. The apparatus of claim 7, further comprising:
the sending module is used for sending an inquiry message to a user when the scanning module does not find the driver corresponding to the identifier of the driver to be installed;
and the second acquisition module is used for acquiring the driving program corresponding to the identifier of the driving program to be installed according to the search catalog input by the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610409439.9A CN106020915B (en) | 2016-06-12 | 2016-06-12 | Driver installation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610409439.9A CN106020915B (en) | 2016-06-12 | 2016-06-12 | Driver installation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106020915A CN106020915A (en) | 2016-10-12 |
| CN106020915B true CN106020915B (en) | 2020-06-26 |
Family
ID=57091131
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610409439.9A Active CN106020915B (en) | 2016-06-12 | 2016-06-12 | Driver installation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106020915B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108089885A (en) * | 2017-12-28 | 2018-05-29 | Tcl移动通信科技（宁波）有限公司 | A kind of USB driving installation processes method, mobile terminal and storage medium |
| CN109766105A (en) * | 2018-12-24 | 2019-05-17 | 新华三技术有限公司 | Drive programe installation method, device, server and computer readable storage medium |
| CN113961253B (en) * | 2021-09-29 | 2024-04-09 | 阿里巴巴（中国）有限公司 | Driving program calling method, device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102147754A (en) * | 2011-04-01 | 2011-08-10 | 奇智软件（北京）有限公司 | Automatic backup method and device for driver |
| CN104881314A (en) * | 2015-06-29 | 2015-09-02 | 北京金山安全软件有限公司 | Method for installing driver and driver installation device |
| CN105204912A (en) * | 2015-10-15 | 2015-12-30 | 北京金山安全软件有限公司 | Driver matching method and device |
-
2016
- 2016-06-12 CN CN201610409439.9A patent/CN106020915B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102147754A (en) * | 2011-04-01 | 2011-08-10 | 奇智软件（北京）有限公司 | Automatic backup method and device for driver |
| CN104881314A (en) * | 2015-06-29 | 2015-09-02 | 北京金山安全软件有限公司 | Method for installing driver and driver installation device |
| CN105204912A (en) * | 2015-10-15 | 2015-12-30 | 北京金山安全软件有限公司 | Driver matching method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106020915A (en) | 2016-10-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7685322B2 (en) | Port number emulation for wireless USB connections | |
| US10346481B2 (en) | Customizing operating system based on detected carrier | |
| US9097528B2 (en) | Managing a datacenter using mobile devices | |
| CN109947482B (en) | Loading method of USB (universal serial bus) equipment, storage medium and smart television | |
| CN107015807B (en) | Device driver management method | |
| CN106020915B (en) | Driver installation method and device | |
| CN103377094A (en) | Abnormity monitoring method and abnormity monitoring device | |
| WO2018040746A1 (en) | Driver installation method, device, and electronic apparatus | |
| CN112105009A (en) | Device discovery and Bluetooth broadcasting method, device, electronic device and storage medium | |
| CN105049502A (en) | Method of upgrading equipment software in cloud network management system and device | |
| CN113220290A (en) | Method, device, equipment and storage medium for realizing business function of application | |
| CN110109706B (en) | System and method for component inventory and compliance in a platform | |
| CN110139326B (en) | Method, device and terminal equipment for automatically switching network modes in private network system | |
| US20160378553A1 (en) | Resource Management Method and Device for Terminal System | |
| CN107831887B (en) | Application starting method and device | |
| CN104079432A (en) | Method and device for processing abnormity of network equipment | |
| CN112035129A (en) | Method and device for driver installation and upgrade and computer equipment | |
| US8683460B2 (en) | Grandfathering configurations in a distributed environment | |
| CN103823871A (en) | Method and device for searching for software | |
| CN108595292B (en) | System optimization method, mobile terminal and computer storage medium | |
| CN113377610B (en) | Performance monitoring method, device, computer equipment and storage medium | |
| CN103207789B (en) | Application server constant value dynamic updating method and system | |
| CN112953754B (en) | Configuration method and device of differentiated service, electronic equipment and storage medium | |
| CN111092765B (en) | Intelligent driving method, system, electronic device and readable storage medium | |
| CN110321251B (en) | Data backup method, device, equipment and storage medium based on network block equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |