CN108845812B - Plug-in updating method, device, computer equipment and storage medium - Google Patents
Plug-in updating method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN108845812B CN108845812B CN201810548115.2A CN201810548115A CN108845812B CN 108845812 B CN108845812 B CN 108845812B CN 201810548115 A CN201810548115 A CN 201810548115A CN 108845812 B CN108845812 B CN 108845812B
- Authority
- CN
- China
- Prior art keywords
- plug
- updated
- server
- host version
- local host
- 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
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000013475 authorization Methods 0.000 claims description 58
- 238000009434 installation Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 24
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 description 11
- 238000011161 development Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000002155 anti-virotic effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a plug-in updating method, a plug-in updating device, computer equipment and a storage medium. The method comprises the following steps: receiving an application program starting instruction, and opening a corresponding application program according to the application program starting instruction; acquiring a first plug-in list from a server, and reading a second plug-in list from a local storage preset position; detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list; when the plug-in to be updated exists, a local host version is acquired; and detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server. By adopting the method, the plug-in updating operation can be executed each time the program is started, and the normal operation of the application program is ensured.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for updating a plug-in unit, a computer device, and a storage medium.
Background
With the development of network technology, mobile terminals such as mobile phones are increasingly widely applied, and application programs on the mobile terminals are increasingly diversified. In order to meet the requirement of users on realizing diversified functions at the terminal, various plug-ins are often required to be installed on the terminal and updated in time.
The traditional plug-in updating mode is that a server actively transmits a new version of an installed plug-in to a terminal, and when the server transmits, the server needs to aim at all terminals with application programs installed, the data volume is large, the data volume is chaotic, and the situation that the update of the application programs fails, namely the situation that the update of the plug-in fails exists.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a plug-in updating method, apparatus, computer device, and storage medium capable of ensuring normal operation of an application.
A method of plug-in update, the method comprising:
acquiring an application program starting instruction, and opening a corresponding application program according to the application program starting instruction;
acquiring a first plug-in list from a server, and reading a second plug-in list from a local storage preset position;
detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list;
when the plug-in to be updated exists, a local host version is obtained;
and detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server.
In one embodiment, the detecting whether the local host version supports the running of the plug-in to be updated includes:
Reading the lowest host version number supported by the plug-in to be updated;
acquiring a version number of the local host version;
when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated;
and when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated.
In one embodiment, before the opening of the corresponding application according to the application start instruction, the method further includes:
sending an authorization request to the server;
receiving a message of successful authorization corresponding to the authorization request sent by the server;
and continuing to acquire the first plug-in list from the server.
In one embodiment, after the sending the authorization request to the server, the method further includes:
receiving an authorization failure message corresponding to the authorization request sent by the server;
displaying the message of the authorization failure;
acquiring registration information corresponding to the authorization failure message;
generating a registration request according to the registration information, and sending the registration request to the server;
And when the server passes the registration request, continuing to acquire the first plug-in list from the server.
In one embodiment, the method further comprises:
when the local host version does not support the plug-in to be updated, an upgrade instruction for the local host version is received;
and updating the local host version according to the upgrading instruction.
In one embodiment, the downloading and installing the plug-in to be updated from the server includes:
downloading an installation package of the plug-in to be updated from the server;
verifying signature information of the installation package;
and after the signature information is successfully verified, installing the plug-in to be updated according to the installation package.
In one embodiment, after the server downloads and installs the plug-in to be updated, the method further includes:
obtaining update data from the server;
positioning a plug-in corresponding to the update data in the application program;
opening the plug-in.
A plug-in updating apparatus, the apparatus comprising:
the application program starting instruction acquisition module is used for acquiring an application program starting instruction and opening a corresponding application program according to the application program starting instruction;
The plug-in list acquisition module is used for acquiring a first plug-in list from the server and reading a second plug-in list from a preset local storage position;
the plug-in updating monitoring module is used for detecting whether plug-ins to be updated exist according to the first plug-in list and the second plug-in list;
the host version reading module is used for acquiring a local host version when the plug-in to be updated exists;
and the plug-in updating module is used for detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server.
A computer device comprising a memory storing a computer program and a processor implementing the steps of any one of the methods described above when the processor executes the computer program.
A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of any of the preceding claims.
The plug-in updating method, the device, the computer equipment and the storage medium detect whether the plug-in to be updated exists on the server by comparing the first plug-in list acquired from the server with the second plug-in list stored in the local preset position when the application program starting instruction for starting the application program is acquired, if so, verify whether the local host version can support the operation of the plug-in to be updated, if so, download and install the plug-in to be updated from the server, and then operate the application program after the plug-in is updated. According to the plug-in updating method, whether the plug-in the application program needs to be updated is comprehensively detected by comparing the first plug-in list acquired from the server with the second plug-in list stored in the local preset position, the operation of the plug-in to be updated can be supported by the local host version, and the operation is executed when each program is started, so that the normal operation of the application program is guaranteed.
Drawings
FIG. 1 is an application scenario diagram of a plug-in update method in one embodiment;
FIG. 2 is a flow diagram of a plug-in update method in one embodiment;
FIG. 3 is a flowchart illustrating step S210 in FIG. 2 according to an embodiment;
FIG. 4 is a block diagram of a plug-in update apparatus in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The plug-in updating method provided by the application can be applied to an application environment shown in fig. 1. The terminal and the server communicate through a network. After receiving an application program starting instruction, the terminal detects whether a plug-in to be updated exists on the server or not by comparing a first plug-in list acquired from the server with a second plug-in list stored in a local preset position, if so, the plug-in to be updated is downloaded and installed from the server under the condition that the local host version supports the operation of the plug-in to be updated, and the application program is operated after the plug-in to be updated is completed. The terminal may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers and portable wearable devices, and the server may be implemented by a separate server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a plug-in updating method is provided, and the method is applied to the terminal in fig. 1 for illustration, and includes the following steps:
s202, receiving an application program starting instruction, and opening a corresponding application program according to the application program starting instruction.
The application program starting instruction is an instruction for opening an application program, which is acquired by the terminal; the user may click on an icon, notification bar, or other instruction corresponding to the application program through the input device to open the application program, or may open the application program through a connection system such as a network.
Specifically, after the terminal acquires an application program starting instruction for starting an application program, the terminal starts to run the application program.
S204, acquiring a first plug-in list from the server, and reading a second plug-in list from a local storage preset position.
The first plug-in list is a list of all plug-ins and versions of plug-ins for statistical release on the server; when a developer issues a new plug-in or plug-in version on a server, the first plug-in list is updated, so that the first plug-in list can always reflect the real-time situation of the plug-in on the server.
The locally stored preset location is a location for storing a second plug-in list on the terminal, such as a corresponding folder in the application, etc.
The second plug-in list is a list used for counting plug-ins and plug-in versions which are installed locally on the terminal; and after the terminal downloads and installs the application program from the server, synchronizing the plug-in list on the server to a preset local storage position of the terminal, and correspondingly updating a second plug-in list on the terminal after updating the local plug-in or plug-in version each time, so that the second plug-in list can always reflect the real-time condition of the plug-in on the terminal.
Specifically, after the application program is opened according to the application program starting instruction, the terminal detects whether the plug-in installed in the local application program needs to be updated by comparing the first plug-in list on the server with the locally stored second plug-in list, so that the terminal firstly acquires the first plug-in list from the server and then reads the second plug-in list from the locally stored preset position.
S206, detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list.
The plug-in to be updated is a part of the first plug-in list which is different from the second plug-in list, namely, a plug-in newly released on the server after the plug-in on the last terminal is updated. The plug-in can be a plug-in which is not installed on the terminal, or can be the latest version of the plug-in which is installed on the terminal.
Specifically, after obtaining the first plug-in list and the second plug-in list according to step S204, the terminal compares whether the first plug-in list and the second plug-in list are the same, if so, there is no plug-in to be updated; if the terminal is different, the plug-in to be updated of the terminal can be considered to exist on the server.
Optionally, the first plug-in list and the second plug-in list are different, which may be that the number of plug-in items in the first plug-in list exceeds that in the second plug-in list, and then a new plug-in may be released on the server, and the new plug-in may be installed on the terminal through subsequent steps; the number of items in the first plug-in list is the same as that of items in the second plug-in list, but the names of the plug-ins are different, so that a new version of some plug-ins installed on the terminal can be released on the server, and the plug-ins can be upgraded through subsequent steps. When a developer issues a plug-in and a plug-in version at a server, a plug-in list can be updated according to a unified naming format, different version names of the same plug-in can form a corresponding incremental array according to the sequence of development time, and after the latest version of a certain plug-in is issued, a historical version of the plug-in is covered in the plug-in list, so that a terminal can conveniently compare a first plug-in list with a second plug-in list.
S208, when the plug-in to be updated exists, the local host version is acquired.
The local host version is a host version in an application program installed on the terminal and is used for supporting the operation of a plug-in installed on the terminal. The plug-in released on the server is developed based on a host, when the terminal downloads the application program from the server, the plug-in a host capable of supporting the plug-in operation is downloaded, and when the terminal downloads the application program, the plug-in the latest plug-in list on the server is downloaded, and then the plug-in updated by the plug-in updating method in the application is operated based on a local host version every time the terminal executes.
Specifically, when the terminal detects that there is a plug-in to be updated in the server through the application, it is necessary to read a local host version in the application currently installed on the terminal.
S210, detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server.
Specifically, since the plug-ins all run on the terminal based on the local host version, before the terminal updates the local plug-ins, it is necessary to detect whether the plug-ins to be updated can run under the local host version, if so, the terminal downloads the plug-ins to be updated from the server, installs the downloaded plug-ins to be updated, and completes the plug-in updating process on the terminal.
Optionally, before the terminal downloads and installs the plug-in to be updated from the server or in the downloading and installing processes, if the terminal acquires the instruction for intercepting update or installation, the terminal does not continue to execute the corresponding step of downloading or installing the plug-in to be updated. The instruction for intercepting the update or intercepting the installation can be a forced stop instruction input by a user into the terminal, or can be an update interception instruction sent by other applications (such as antivirus software and the like).
According to the plug-in updating method, when an application program starting instruction for starting an application program is received, whether a plug-in to be updated exists on a server or not is detected by comparing a first plug-in list acquired from the server with a second plug-in list stored in a local preset position, if so, whether the local host version can support operation of the plug-in to be updated is verified, if so, the plug-in to be updated is downloaded and installed from the server, and the application program is operated after the plug-in to be updated is completed. According to the plug-in updating method, whether the plug-in the application program needs to be updated is comprehensively detected by comparing the first plug-in list acquired from the server with the second plug-in list stored in the local preset position, the operation of the plug-in to be updated can be supported by the local host version, and the operation is executed when each program is started, so that the normal operation of the application program is guaranteed.
In one embodiment, referring to fig. 3, step S210 in the above-mentioned plug-in updating method for detecting whether the local host version supports the operation of the plug-in to be updated may include:
s302, the lowest host version number supported by the plug-in to be updated is read.
The lowest host version number is the lowest host version number which ensures that the plug-in to be updated can run; in order to better support the running of the plug-in, a developer can update the host version of the application program, and the host version number changes along with each update of the host version, so that the host version numbers are sequentially increased according to the update sequence of the host version, and hosts with high version numbers can inherit the functions of hosts with low version numbers.
Specifically, when a developer issues a new plug-in or plug-in version on a server, the developer needs to issue the lowest host version number supported by the new plug-in or plug-in version, and after detecting that a plug-in to be updated exists on the server, the terminal reads the lowest host version number supported by the plug-in to be updated.
S304, a version number of the local host version is obtained.
The version number of the local host version is the host version number currently installed in the application program of the terminal.
Specifically, the terminal may obtain a local host version number currently installed on the terminal through an application. Alternatively, the terminal may read attribute information of the application program, and acquire the local host version number therefrom.
S306, when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated.
Specifically, when the development team develops the host version in the background, the host version numbers are named according to a certain logic sequence, so that when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated.
S308, when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated.
Specifically, when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated, i.e. the plug-in to be updated is installed on the terminal, and the terminal cannot run the plug-in.
In the above embodiment, a method for detecting whether the local host version supports the operation of the plug-in to be updated is provided, and the terminal is ensured to support the operation of the plug-in to be updated through naming and developing modes of the host version number.
In one embodiment, step S202 in the above plug-in updating method may further include, before opening the corresponding application according to the application start instruction: sending an authorization request to a server; receiving a message of successful authorization corresponding to the authorization request sent by a server; the first plug-in list continues to be obtained from the server.
Wherein the authorization request is a request sent by the terminal to the server to request access to data on the server; data request messages or login messages, etc.
Specifically, before the terminal opens the application program according to the application program starting instruction, an authorization request needs to be sent to the server, after the authentication of the server is passed, the server returns a message that authorization corresponding to the authorization request is successful, the terminal has permission to access the server, and the first plug-in list is continuously acquired from the server.
In the embodiment, the terminal which must be successfully authorized is introduced to access the server, so that the security of the data interaction between the server and the terminal is improved.
In one embodiment, after sending the authorization request to the server in the above plug-in updating method, the method further includes: receiving an authorization failure message corresponding to the authorization request sent by a server; displaying a message of authorization failure; acquiring registration information corresponding to the authorization failure message; generating a registration request according to the registration information, and sending the registration request to a server; when the server passes the registration request, the first plug-in list continues to be acquired from the server.
The registration information is information which is generated by the terminal according to the message of authorization failure and used for acquiring the authorization of the server. For example, the registration information may be a user name and a password or the like input by a user operating the terminal.
The registration request is a request message generated by the terminal according to the registration information, for example, the terminal may encrypt the registration information such as the user name and the password to form the registration request.
Specifically, in the above embodiment, after the terminal sends the authorization request to the server, if the authentication of the server is not passed. The server returns an authorization failure message corresponding to the authorization request to the terminal, and the terminal displays the message on a display interface of the terminal after receiving the authorization failure message; and after the registration information is acquired, generating a registration request according to the registration information, sending the registration request to the server, requesting authorization from the server again, and when the server passes the registration request, continuing to acquire the first plug-in list from the server by the terminal through the authorization of the server.
Alternatively, when the terminal runs the application program for the first time, the server may require the user to register by a user name and a password, and after the registration, the terminal obtains the right to access the server.
In addition, the authority of the terminal to access the server can have timeliness, for example, a plurality of registration types with different timeliness are defined, each registration type corresponds to different effective time, and the server can identify the registration type of the terminal according to the user name sent by the terminal. The server monitors the access authority of the user name through the registration type corresponding to the user name; if the user name exceeds the corresponding effective time, the terminal is not allowed to access the server through the user name; if access is to be continued, the terminal is required to resend the authorization request.
In the above embodiment, after the terminal fails to request the authorization of the server, a method for requesting the authorization again is provided, which improves the security of the data interaction between the server and the terminal together with the previous embodiment.
In one embodiment, the above plug-in updating method may further include: when the local host version does not support the plug-in to be updated, an upgrade instruction for the local host version is received; and updating the local host version according to the upgrading instruction.
Wherein the upgrade instruction is an instruction for upgrading the local host version; a command to start upgrading the host version using user input of the terminal, etc.
Specifically, when the terminal identifies that a plug-in to be updated exists on the server, but the local host version does not support the plug-in to be updated, displaying the reason of the failure of updating the plug-in on the display interface, informing the user that the local host version needs to be updated, inputting an updating instruction if the user agrees to update, acquiring an installation package of a new host version from the server by the terminal, and installing the new host version locally.
In the above embodiment, by means of upgrading the local host version, the plug-in to be updated on the server can run on the terminal.
In one embodiment, the downloading and installing the plug-in to be updated from the server in step S210 in the plug-in updating method may include: downloading an installation package of the plug-in to be updated from a server; verifying signature information of the installation package; and after the signature information is verified successfully, installing the plug-in to be updated according to the installation package.
The signature information is a basis for checking whether the installation package of the plug-in to be updated is tampered, and may be a hash value of the installation package signature of the plug-in to be updated.
Specifically, after the terminal downloads the installation package of the plug-in unit to be updated from the server, whether the installation package is tampered or not is detected by verifying the front information of the installation package, if the signature information is verified successfully, the installation package is not tampered, the risk is avoided, and the plug-in unit to be updated can be continuously installed on the terminal.
Optionally, the terminal may obtain a signature of an installation package of the plug-in to be updated from the server, calculate a hash value of the signature according to a hash value calculation manner, and compare the hash value with a hash value extracted from the installation package, and if a quantity of hash values are the same, the signature information verification is successful.
In the above embodiment, the security of the plug-in to be updated installed on the terminal is ensured by verifying the signature information of the installation package of the plug-in to be updated downloaded from the server.
In one embodiment, after the server downloads and installs the plug-in to be updated in step S210 in the plug-in updating method, the method may further include: obtaining updated data from a server; positioning a plug-in corresponding to the update data in the application program; the plug-in is opened.
The updating data are data corresponding to the plug-ins, which are published on the server, and the terminal connected with the server can display the corresponding plug-in pages on the terminal interface through the updating data; the developer can edit the corresponding identifier for each plug-in the process of developing the plug-in, and the update data can be the identifier corresponding to the plug-in.
Specifically, after updating the plug-in to be updated on the terminal, the terminal can enter the homepage of the application program, at this time, if the server side has update data, the terminal enters the plug-in corresponding to the update data, and displays the page corresponding to the update data to the user using the terminal, so as to achieve the effect of popularizing the function of the plug-in corresponding to the update data.
In the above embodiment, the server issues the update data, so that the terminal connected with the server at this time can display the corresponding page to the user according to the update data, and the terminal connected with the server is better managed, thereby realizing the effect of promoting the plug-in function in real time.
And correspondingly, the developer shall develop the plug-in based on the host version corresponding to the terminal, and then issue the developed plug-in to the server for downloading by the terminal. The method comprises the following steps: establishing a host base, and generating a base packet according to the host base; importing a base package, and creating a plug-in application project on a server according to the base package; developing a plug-in to be updated in plug-in application engineering, and publishing the plug-in to be updated to a server.
In one embodiment, a plug-in development method for a terminal installed with an android system through java (a computer development language) is provided, and the method includes:
in the virtual machine, inheriting the Intent class (Intent is the class for transferring messages among three components (activities, broadcasting, services) in the android system), and creating a DLIntent class (DL, plug-in dynamic loading framework) for loading plug-in packages; reading a plug-in package information interface through an android system standard, and obtaining information of a plug-in package; and loading interface classes of the plug-ins according to class paths in the plug-in packages through a java reflection mechanism, and generating a host base. Defining an Activity (one of four components of the android system can provide a screen, and a user can interact to complete a task, wherein the Activity has periodicity; the Activity is a periodic execution class) in the host base, so that the Activity proxy function of the android system is realized; defining an execution class for executing android system Service (Service is another component of four components of an android system, is a Service program with long life cycle and no visual interface and running in a background) declaration period in the host base, and realizing the proxy function of the android system Service; the above-described host base was used to create a base pack.
Importing a base packet, and creating an Activity and a Service of the plugin, wherein the Activity and the Service are inherited to an execution class of an Activity declaration period and an execution class of a Service declaration period in a host base; and creating a plug-in application project, and declaring the Activity and Service of the plug-in the plug-in project.
And compiling a plug-in for realizing a specific function in the plug-in engineering to generate a plug-in package. And uploading the plug-in package to a set position on a server through a release mechanism, wherein the set position on the server can be accessed by a terminal through a preset access path, and the plug-in package can be downloaded.
In the embodiment, by creating the unified standard host base and the plug-in application engineering established according to the host base, the plug-in development tasks can be dispersed to different teams for development, so that a plurality of development teams can cooperatively develop at the same time, and the development pressure is relieved.
It should be understood that, although the steps in the flowcharts of fig. 2 to 3 are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided a plug-in updating apparatus, including: an application startup instruction acquisition module 100, a plug-in list acquisition module 200, a plug-in update monitoring module 300, a host version reading module 400, and a plug-in update module 500, wherein:
the application program starting instruction obtaining module 100 is configured to obtain an application program starting instruction, and open a corresponding application program according to the application program starting instruction.
The plug-in list obtaining module 200 is configured to obtain a first plug-in list from a server, and read a second plug-in list from a local storage preset location.
The plug-in update monitoring module 300 is configured to detect whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list.
The host version reading module 400 is configured to obtain a local host version when there is a plug-in to be updated.
The plug-in updating module 500 is configured to detect whether the local host version supports the operation of the plug-in to be updated, and if so, download and install the plug-in to be updated from the server.
In one embodiment, the plug-in update module 500 in the plug-in update apparatus may include:
and the lowest host version unit is used for reading the lowest host version number supported by the plug-in to be updated.
And the local host version unit is used for acquiring the version number of the local host version.
And the supporting unit is used for supporting the plug-in to be updated by the local host version when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated.
And the unsupported unit is used for enabling the local host version not to support the plug-in to be updated when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated.
In one embodiment, the above-mentioned plug-in updating device may further include:
and the authorization request module is used for sending an authorization request to the server.
And the authorization message receiving module is used for receiving the successful authorization message corresponding to the authorization request sent by the server.
And the continuing execution module is used for continuing to acquire the first plug-in list from the server.
In one embodiment, the above-mentioned plug-in updating device may further include:
and the failure message module is used for receiving the message of authorization failure corresponding to the authorization request sent by the server.
And the failure notification module is used for displaying the message of authorization failure.
And the registration information acquisition module is used for acquiring registration information corresponding to the authorization failure message.
And the sending registration module is used for generating a registration request according to the registration information and sending the registration request to the server.
And the registration passing module is used for continuing to acquire the first plug-in list from the server when the server passes the registration request.
In one embodiment, the above-mentioned plug-in updating device may further include:
and the host upgrading module is used for receiving an upgrading instruction aiming at the local host version when the local host version does not support the plug-in to be updated.
And the host updating module is used for updating the local host version according to the upgrading instruction.
In one embodiment, the plug-in update module 500 in the plug-in update apparatus may include:
and the installation package downloading unit is used for downloading the installation package of the plug-in to be updated from the server.
And the signature verification unit is used for verifying the signature information of the installation package.
And the plug-in updating unit is used for installing the plug-in to be updated according to the installation package after the signature information is verified successfully.
In one embodiment, the above-mentioned plug-in updating device may further include:
and the updating data acquisition module is used for acquiring the updating data from the server.
And the plug-in positioning module is used for positioning the plug-in corresponding to the update data in the application program.
And the plug-in starting module is used for opening the functional partition.
For specific limitations of the plug-in updating means, reference may be made to the above limitation of the plug-in updating method, and no further description is given here. The respective modules in the above-described plug-in updating apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a plug-in update method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory storing a computer program and a processor that when executing the computer program performs the steps of: receiving an application program starting instruction, and opening a corresponding application program according to the application program starting instruction; acquiring a first plug-in list from a server, and reading a second plug-in list from a local storage preset position; detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list; when the plug-in to be updated exists, a local host version is acquired; and detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server.
In one embodiment, detecting whether the local host version supports the running of the plug-in to be updated implemented when the processor executes the computer program may include: reading the lowest host version number supported by the plug-in to be updated; acquiring a version number of a local host version; when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated; when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated.
In one embodiment, after sending the authorization request to the server, which is implemented when the processor executes the computer program, the method may further include: receiving an authorization failure message corresponding to the authorization request sent by a server; displaying a message of authorization failure; acquiring registration information corresponding to the authorization failure message; generating a registration request according to the registration information, and sending the registration request to a server; when the server passes the registration request, the first plug-in list continues to be acquired from the server.
In one embodiment, the processor when executing the computer program further performs the steps of: when the local host version does not support the plug-in to be updated, an upgrade instruction for the local host version is received; and updating the local host version according to the upgrading instruction.
In one embodiment, downloading and installing plug-ins to be updated from a server, which is implemented when a processor executes a computer program, may include: downloading an installation package of the plug-in to be updated from a server; verifying signature information of the installation package; and after the signature information is verified successfully, installing the plug-in to be updated according to the installation package.
In one embodiment, after the server implemented when the processor executes the computer program downloads and installs the plug-in to be updated, the method may further include: obtaining updated data from a server; positioning a plug-in corresponding to the update data in the application program; the plug-in is opened.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving an application program starting instruction, and opening a corresponding application program according to the application program starting instruction; acquiring a first plug-in list from a server, and reading a second plug-in list from a local storage preset position; detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list; when the plug-in to be updated exists, a local host version is acquired; and detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server.
In one embodiment, detecting whether the local host version supports the running of the plug-in to be updated, which is implemented when the computer program is executed by the processor, may include: reading the lowest host version number supported by the plug-in to be updated; acquiring a version number of a local host version; when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated; when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated.
In one embodiment, after sending the authorization request to the server, the computer program when executed by the processor may further include: receiving an authorization failure message corresponding to the authorization request sent by a server; displaying a message of authorization failure; acquiring registration information corresponding to the authorization failure message; generating a registration request according to the registration information, and sending the registration request to a server; when the server passes the registration request, the first plug-in list continues to be acquired from the server.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the local host version does not support the plug-in to be updated, an upgrade instruction for the local host version is received; and updating the local host version according to the upgrading instruction.
In one embodiment, downloading and installing a plug-in to be updated from a server, which is implemented when a computer program is executed by a processor, may include: downloading an installation package of the plug-in to be updated from a server; verifying signature information of the installation package; and after the signature information is verified successfully, installing the plug-in to be updated according to the installation package.
In one embodiment, after the server implemented when the computer program is executed by the processor downloads and installs the plug-in to be updated, the method may further include: obtaining updated data from a server; positioning a plug-in corresponding to the update data in the application program; the plug-in is opened.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples represent only a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (9)
1. A method of plug-in update, the method comprising:
receiving an application program starting instruction, and opening a corresponding application program according to the application program starting instruction;
acquiring a first plug-in list from a server, and reading a second plug-in list from a local storage preset position;
detecting whether a plug-in to be updated exists according to the first plug-in list and the second plug-in list;
When the plug-in to be updated exists, a local host version is obtained;
detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server;
when the local host version does not support the plug-in to be updated, an upgrade instruction for the local host version is received;
updating the local host version according to the upgrading instruction;
obtaining update data from the server;
positioning a plug-in corresponding to the update data in the application program;
and opening the plug-in and displaying a corresponding plug-in page on a terminal interface.
2. The method of claim 1, wherein the detecting whether the local host version supports operation of the plug-in to be updated comprises:
reading the lowest host version number supported by the plug-in to be updated;
acquiring a version number of the local host version;
when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated, the local host version supports the plug-in to be updated;
and when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated, the local host version does not support the plug-in to be updated.
3. The method of claim 1, further comprising, prior to opening the corresponding application according to the application start instruction:
sending an authorization request to the server;
receiving a message of successful authorization corresponding to the authorization request sent by the server;
and continuing to acquire the first plug-in list from the server.
4. A method according to claim 3, wherein after said sending an authorization request to said server, further comprising:
receiving an authorization failure message corresponding to the authorization request sent by the server;
displaying the message of the authorization failure;
acquiring registration information corresponding to the authorization failure message;
generating a registration request according to the registration information, and sending the registration request to the server;
and when the server passes the registration request, continuing to acquire the first plug-in list from the server.
5. The method of claim 1, wherein said downloading and installing the plug-in to be updated from the server comprises:
downloading an installation package of the plug-in to be updated from the server;
verifying signature information of the installation package;
And after the signature information is successfully verified, installing the plug-in to be updated according to the installation package.
6. A plug-in updating device, the device comprising:
the application program starting instruction acquisition module is used for acquiring an application program starting instruction and opening a corresponding application program according to the application program starting instruction;
the plug-in list acquisition module is used for acquiring a first plug-in list from the server and reading a second plug-in list from a preset local storage position;
the plug-in updating monitoring module is used for detecting whether plug-ins to be updated exist according to the first plug-in list and the second plug-in list;
the host version reading module is used for acquiring a local host version when the plug-in to be updated exists;
the plug-in updating module is used for detecting whether the local host version supports the operation of the plug-in to be updated, and if so, downloading and installing the plug-in to be updated from the server;
the host upgrading module is used for receiving an upgrading instruction aiming at the local host version when the local host version does not support the plug-in to be updated;
the host updating module is used for updating the local host version according to the upgrading instruction;
The update data acquisition module is used for acquiring update data from the server;
the plug-in positioning module is used for positioning a plug-in corresponding to the update data in the application program;
and the plug-in starting module opens the plug-in and displays a corresponding plug-in page on a terminal interface.
7. The apparatus of claim 6, wherein the plug-in update module comprises:
the lowest host version unit is used for reading the lowest host version number supported by the plug-in to be updated;
a local host version unit, configured to obtain a version number of the local host version;
the support unit is used for supporting the plug-in to be updated by the local host version when the version number of the local host version is greater than or equal to the lowest host version number supported by the plug-in to be updated;
and the unsupported unit is used for enabling the local host version not to support the plug-in to be updated when the version number of the local host version is smaller than the lowest host version number supported by the plug-in to be updated.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 5 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810548115.2A CN108845812B (en) | 2018-05-31 | 2018-05-31 | Plug-in updating method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810548115.2A CN108845812B (en) | 2018-05-31 | 2018-05-31 | Plug-in updating method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108845812A CN108845812A (en) | 2018-11-20 |
| CN108845812B true CN108845812B (en) | 2024-04-05 |
Family
ID=64210183
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810548115.2A Active CN108845812B (en) | 2018-05-31 | 2018-05-31 | Plug-in updating method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108845812B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558148B (en) * | 2018-11-29 | 2020-01-14 | 网易（杭州）网络有限公司 | Router plug-in installation method, device, equipment and storage medium |
| CN111459514B (en) * | 2019-01-18 | 2023-06-23 | 普天信息技术有限公司 | Terminal upgrading processing method, server and base station |
| CN110209416A (en) * | 2019-05-31 | 2019-09-06 | 彩讯科技股份有限公司 | Application software update method, device, terminal and storage medium |
| CN110543324B (en) * | 2019-08-27 | 2024-02-23 | 贝壳技术有限公司 | Plug-in increment updating method and device for application program |
| CN113568629A (en) * | 2020-04-28 | 2021-10-29 | 中车株洲电力机车研究所有限公司 | Software upgrading method and device based on CAN, computer equipment and storage medium |
| CN112416384A (en) * | 2020-06-11 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Software upgrading method and device and computer equipment |
| CN112256295A (en) * | 2020-09-21 | 2021-01-22 | 北京达佳互联信息技术有限公司 | Application program updating method, device, equipment and storage medium |
| CN112148332B (en) * | 2020-09-30 | 2023-09-05 | 亮风台（上海）信息科技有限公司 | Tool system, updating method thereof, terminal device and storage medium |
| CN112162795B (en) * | 2020-10-09 | 2023-12-12 | 广州博冠信息科技有限公司 | Plug-in starting method and device, computer equipment and storage medium |
| CN112667996A (en) * | 2020-12-28 | 2021-04-16 | 南方电网数字电网研究院有限公司 | Transformer substation trusted management system, method and device and computer equipment |
| CN112783515B (en) * | 2021-02-08 | 2023-08-25 | 腾讯科技（深圳）有限公司 | Plug-in control method and device and storage medium |
| CN113055451B (en) * | 2021-03-08 | 2023-01-06 | Oppo广东移动通信有限公司 | Resource downloading method and device, electronic equipment and storage medium |
| CN113238785B (en) * | 2021-06-18 | 2023-10-20 | 腾讯科技（深圳）有限公司 | Application program updating method, related device, equipment and storage medium |
| CN113590179B (en) * | 2021-08-02 | 2024-03-12 | 上海米哈游璃月科技有限公司 | Plug-in detection method and device, electronic equipment and storage medium |
| WO2023123018A1 (en) * | 2021-12-29 | 2023-07-06 | 深圳晶泰科技有限公司 | Method and apparatus for acquiring information of plug-in throughout full life cycle, and storage medium |
| CN114528048A (en) * | 2022-02-18 | 2022-05-24 | Oppo广东移动通信有限公司 | Application execution method, application execution architecture, electronic device and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104391690A (en) * | 2014-11-04 | 2015-03-04 | 中国石油天然气股份有限公司 | Application development system and method |
| CN104699511A (en) * | 2015-03-27 | 2015-06-10 | 北京奇虎科技有限公司 | Plug-in upgrading method and plug-in upgrading device |
| CN104714827A (en) * | 2015-03-31 | 2015-06-17 | 北京奇虎科技有限公司 | Plug-in update method and device |
| CN104951322A (en) * | 2014-03-27 | 2015-09-30 | 腾讯科技（深圳）有限公司 | Plug-in management method, device and system |
| CN105204879A (en) * | 2014-06-23 | 2015-12-30 | 小米科技有限责任公司 | Application updating method and device |
| CN106375567A (en) * | 2016-08-31 | 2017-02-01 | 广州品唯软件有限公司 | Plug-in release method and system, client and server |
| CN107656750A (en) * | 2017-10-16 | 2018-02-02 | 深圳大宇无限科技有限公司 | Update of plug-in method and device |
-
2018
- 2018-05-31 CN CN201810548115.2A patent/CN108845812B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104951322A (en) * | 2014-03-27 | 2015-09-30 | 腾讯科技（深圳）有限公司 | Plug-in management method, device and system |
| CN105204879A (en) * | 2014-06-23 | 2015-12-30 | 小米科技有限责任公司 | Application updating method and device |
| CN104391690A (en) * | 2014-11-04 | 2015-03-04 | 中国石油天然气股份有限公司 | Application development system and method |
| CN104699511A (en) * | 2015-03-27 | 2015-06-10 | 北京奇虎科技有限公司 | Plug-in upgrading method and plug-in upgrading device |
| CN104714827A (en) * | 2015-03-31 | 2015-06-17 | 北京奇虎科技有限公司 | Plug-in update method and device |
| CN106375567A (en) * | 2016-08-31 | 2017-02-01 | 广州品唯软件有限公司 | Plug-in release method and system, client and server |
| CN107656750A (en) * | 2017-10-16 | 2018-02-02 | 深圳大宇无限科技有限公司 | Update of plug-in method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108845812A (en) | 2018-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108845812B (en) | Plug-in updating method, device, computer equipment and storage medium | |
| US20210271472A1 (en) | Application Wrapping for Application Management Framework | |
| Holla et al. | Android based mobile application development and its security | |
| US10073966B2 (en) | Operating system-independent integrity verification | |
| CN113238850B (en) | RPA realization method, device, equipment and medium based on browser | |
| CN106295255B (en) | Application program reinforcing method and device | |
| CN110333868B (en) | Method and system for generating installation packages of sub-applications | |
| EP3163489B1 (en) | Token-based control of software installation and operation | |
| CN112558946A (en) | Method, device and equipment for generating code and computer readable storage medium | |
| US11520604B2 (en) | Accessing conflicting frameworks and classes | |
| CN102034058A (en) | Method for controlling safety of application software and terminal | |
| US10771462B2 (en) | User terminal using cloud service, integrated security management server for user terminal, and integrated security management method for user terminal | |
| JP2017146967A (en) | Method and system for improving loading speed of intermediate language file | |
| US9354849B2 (en) | Modification of compiled applications and application management using retrievable policies | |
| CN110806935B (en) | Application program construction method, device and system | |
| JP2022502769A (en) | File system verification and installation | |
| KR20150030047A (en) | Method and system for application authentication | |
| US10924280B1 (en) | Digital notary use in distributed ledger technology (DLT) for block construction and verification | |
| Villegas et al. | OTA updates mechanisms: a taxonomy and techniques catalog | |
| CN112527377A (en) | Application program generation processing method and device, computer equipment and storage medium | |
| JP6781126B2 (en) | Virtual machine setting input system, virtual machine setting input method, and program | |
| CN104484198A (en) | Method and device for setting up application | |
| US20230153093A1 (en) | Systems and methods for managing workspaces in a heterogeneous workspace environment | |
| CN113259320A (en) | Verification mode dynamic installation method, system, electronic device and storage medium | |
| Heinl et al. | Android security |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |