CN113312066B - Dynamic hot update method and storage medium - Google Patents
Dynamic hot update method and storage medium Download PDFInfo
- Publication number
- CN113312066B CN113312066B CN202010122796.3A CN202010122796A CN113312066B CN 113312066 B CN113312066 B CN 113312066B CN 202010122796 A CN202010122796 A CN 202010122796A CN 113312066 B CN113312066 B CN 113312066B
- Authority
- CN
- China
- Prior art keywords
- version
- client
- file
- server
- difference
- 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/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a dynamic hot update method and a storage medium, wherein the method comprises the following steps: when the client version needs to be updated, extracting a file with the difference between the latest version of the server and the client version by matching the version information file of the client version with the version information file of the latest version of the server; generating a patch compression packet according to the files with the difference; and updating the client version according to the patch compression package. The invention not only simplifies the hot updating process; the complexity of a packing stage and a package management strategy is greatly reduced, and finally, the difficulty of generating and deploying the hot update package is obviously reduced; moreover, the packaging and deployment efficiency of the client files is improved, and the packaging cost is reduced; further, the efficiency of version rollback can be improved.
Description
Technical Field
The invention relates to the field of software updating, in particular to a dynamic hot updating method and a storage medium.
Background
Because internet products are more and more competitive, user experience requirements are higher and higher, product updating iteration is faster and faster, and the mode of submitting application market review and then updating in a traditional mode cannot meet user requirements. It is therefore necessary to rely on hot-update techniques to reduce the time required for a user to obtain a new version. The traditional hot updating mode has higher requirements on client development and deployment personnel, is easy to make mistakes and is difficult to roll back versions. The invention adopts a dynamic hot update content mode to solve the problems of complex generation and deployment of the hot update package (when the version of an external client is more, the quantity of the hot update package is increased), difficult version rollback and the like.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: a dynamic hot update method and a storage medium are provided, the update difficulty is simplified, and the deployment efficiency is improved.
In order to solve the technical problems, the invention adopts the technical scheme that:
a method of dynamic thermal updating, comprising:
when the client version needs to be updated, extracting a file with the difference between the latest version of the server and the client version by matching the version information file of the client version with the version information file of the latest version of the server;
generating a patch compression packet according to the files with the difference;
and updating the client version according to the patch compression package.
The invention provides another technical scheme as follows:
a computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, is able to carry out the steps of the method for dynamic hot-updating described above.
The invention has the beneficial effects that: according to the method, historical versions do not need to be considered, and a plurality of compression packets do not need to be generated for difference strategy comparison; and the incremental update packages of each version and the latest version are not required to be generated in the packaging stage, so that the packaging stage is complicated, and the download management strategy is complicated. The invention only needs to extract the file with the difference of the latest version of the server relative to the current version of the client when the update is confirmed to be needed, and generates a patch compression packet, thus being capable of being used for rapidly upgrading the version of the client. Therefore, the invention not only simplifies the hot update process; and the complexity of a packing stage and a pack management strategy is greatly reduced, and finally, the difficulty of generating and deploying the hot update pack is obviously reduced.
Drawings
FIG. 1 is a flowchart illustrating a dynamic hot-refresh method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a dynamic hot update method according to a first embodiment of the present invention;
FIG. 3 is a schematic diagram of a packaging process according to a second embodiment of the present invention;
fig. 4 is a schematic deployment flow diagram according to a second embodiment of the present invention.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The most key concept of the invention is as follows: and extracting the file with the difference between the latest version of the server and the version of the client to generate a patch compression package.
The technical terms related to the invention are explained as follows:
referring to fig. 1 and fig. 2, the present invention provides a method for dynamic hot update, including:
when the client version needs to be updated, extracting a file with the difference between the latest version of the server and the client version by matching the version information file of the client version with the version information file of the latest version of the server;
generating a patch compression packet according to the files with the difference;
and updating the client version according to the patch compression packet.
Furthermore, the version file information includes file paths and file check values thereof; generating a patch compression package according to the file with the difference specifically comprises the following steps:
traversing each file path in the version information file of the latest version of the server;
if the current traversed file path exists in the version information file of the latest version of the server and does not exist in the version file information of the version of the client, extracting a file corresponding to the current traversed file path as a newly added differential file;
if the currently traversed file path exists in the version information files of the latest version of the server and the version of the client at the same time, but the respective corresponding file check values are not identical, extracting the file corresponding to the currently traversed file path as a changed difference file;
and combining the newly added difference file and the changed difference file to obtain the file with the difference.
According to the description, the different files are determined based on the file paths and the file check values of the file paths in the version information file, and the accuracy and comprehensiveness of target file extraction are ensured.
Further, the method also comprises the following steps:
after the client is started, the server judges whether the version number of the client is consistent with the version number of the latest version of the server;
if the version numbers are not consistent, judging whether a patch compression packet corresponding to the version from the client to the latest version of the server exists;
if the patch compression packet does not exist, starting to execute the matching step and the steps after the matching step, and storing the generated patch compression packet;
and if so, directly sending the patch compression package to the client, updating the version by the client according to the patch compression package, and ending the flow.
As can be seen from the above description, the generated patch compression package is backed up at the server, and when the update of the same version is triggered again, the generated patch compression package can be directly called without repackaging and deployment, so that the speed of the client obtaining the patch compression package can be increased.
Further, still include:
the client receives an instruction of updating to a specified version;
if the client version is lower than the specified version, updating the client version to the specified version by executing the matching step and the subsequent steps;
if the client version is higher than the specified version, matching the version information file of the client version with the version information file of the specified version, extracting the file of the specified version which is different from the client version, generating a rolling patch compression package, and rolling back the client version according to the rolling patch compression package.
The above description shows that the method is also applicable to the version rollback scene, and also has all the advantages of version update, and can obviously reduce the difficulty of hot rollback package generation and deployment.
Further, the method also comprises the following steps:
and configuring the latest version of the server to be an effective version.
As can be seen from the above description, any version can be enabled to take effect through configuration, and the packaging and deployment processes are performed fully automatically without manual intervention.
Further, the generating a patch compressed package according to the file with the difference further includes:
and pushing the patch compression packet to the oss object or the CDN.
According to the description, the client-side downloading can be accelerated, and the upgrade package can be quickly obtained under the condition that the bandwidth of the server is not occupied.
The invention provides another technical scheme as follows:
a computer-readable storage medium, on which a computer program is stored, which program, when executed by a processor, is capable of carrying out the steps of a method for dynamic hot-update comprising:
when the client version needs to be updated, extracting a file with the difference between the latest version of the server and the client version by matching the version information file of the client version with the version information file of the latest version of the server;
generating a patch compression packet according to the files with the difference;
and updating the client version according to the patch compression package.
Furthermore, the version file information includes file paths and file check values thereof; generating a patch compression package according to the file with the difference specifically comprises the following steps:
traversing each file path in the version information file of the latest version of the server;
if the current traversed file path exists in the version information file of the latest version of the server and does not exist in the version file information of the version of the client, extracting the file corresponding to the current traversed file path as a newly added difference file;
if the currently traversed file path exists in the version information files of the latest version of the server and the version of the client at the same time, but the respective corresponding file check values are not identical, extracting the file corresponding to the currently traversed file path as a changed difference file;
and combining the newly added difference file and the changed difference file to obtain the file with the difference.
Further, the method also comprises the following steps:
after the client is started, the server judges whether the version number of the client is consistent with the version number of the latest version of the server;
if the version numbers are not consistent, judging whether a patch compression packet corresponding to the latest version from the client version to the server exists;
if the patch compression packet does not exist, starting to execute the matching step and the steps after the matching step, and storing the generated patch compression packet;
if yes, the patch compression package is directly sent to the client side, the client side updates the version according to the patch compression package, and the process is ended.
Further, still include:
the client receives an instruction of updating to a specified version;
if the client version is lower than the specified version, updating the client version to the specified version by executing the matching step and the subsequent steps;
if the client version is higher than the specified version, matching the version information file of the client version with the version information file of the specified version, extracting the file of the specified version which has difference relative to the client version, generating a rolling patch compression package, and rolling back the client version according to the rolling patch compression package.
Further, still include:
and configuring the latest version of the server side as an effective version.
Further, the generating a patch compressed package according to the file with the difference further includes:
and pushing the patch compression packet to the oss object or the CDN.
Further, the method also comprises the following steps:
and storing the patch compression packet and the version information corresponding to the patch compression packet to a hot update server.
As can be understood from the above description, those skilled in the art can understand that all or part of the processes in the above technical solutions can be implemented by instructing related hardware through a computer program, where the program can be stored in a computer-readable storage medium, and when executed, the program can include the processes of the above methods. The program can also achieve the advantageous effects corresponding to the respective methods after being executed by a processor.
The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
Example one
Referring to fig. 2, the present embodiment provides a dynamic hot update method, which is suitable for hot update of client software, and is particularly suitable for updating client codes and resources such as App/games.
The method comprises the following steps:
s1: the client is started, the hot update server receives a request for processing the version information of the client, and the validity of the version is detected. Specifically, whether the version number of the client version is consistent with the version number of the latest version of the server is judged; if the two are consistent, starting the engine normally;
if the version numbers are not consistent, hot updating is required, and step S2 is executed;
s2: the hot updating server side detects whether a patch compression packet corresponding to the latest version updated from the client side version to the server side version exists;
if the patch compression package exists, the patch compression package is directly sent to the client, the client updates the version according to the patch compression package, and the process is ended.
If not, go to S3;
s3: and extracting the file with the difference between the latest version of the server and the version of the client by matching the version information file of the version of the client with the version information file of the latest version of the server.
The version information file (e.g., version. json) includes contents such as a version number, each file path, and a check value (e.g., md5) of a corresponding file. The file with the difference refers to a file which is newly added and updated relative to the version of the client side by the latest version of the server side.
The step S3 specifically includes:
s31: traversing each file path in the version information file of the latest version of the server;
s32: if the current traversed file path exists in the version information file of the latest version of the server but does not exist in the version file information of the version of the client, the file corresponding to the file path is represented as a newly-added file, and the file corresponding to the file path is extracted;
s33: if the current traversed file path exists in the version information files of the latest version of the server and the version of the client at the same time, but the check values of the files corresponding to the current traversed file path are not identical, the file corresponding to the file path is represented as a changed file, and the file corresponding to the file path is extracted;
in addition, there may be a case where the file path traversed currently does not exist in the latest version of the server but exists in the version information file of the version of the client, which indicates that the file corresponds to the deleted file of the latest version and is not embodied in the patch package.
S34: and combining the newly added file extracted in the step S32 and the changed file extracted in the step S33 to obtain a file with the difference between the latest version of the server and the version of the client.
S4: and storing the patch compression packet and the version information corresponding to the patch compression packet to a hot update server.
The version information record is a pre-upgrade version and a post-upgrade version for identifying which version the patch compression package is to be upgraded from.
When a new version needs to be deployed each time, the new version deployment can be completed only through the two steps of S3-S4, and the 2 steps are automatically executed without manual participation; therefore, the deployment efficiency is obviously improved, and the failure caused by deployment errors is reduced.
In a specific example, based on the step S4, the server can immediately return the existing corresponding patch compact when receiving the same client request (i.e. the version before upgrade and the target version are the same). The specific implementation is that the patch compression package in the server can be continuously improved, and the probability that the patch compression package is directly sent to the client for rapid upgrade in the step S2 is improved.
For example, the latest version of the server is D, and versions A, B, C and D of the client exist; if the current client is D, updating is not needed; if the number of the AD is A, generating a patch package of the AD; if the current time is B, a patch package of the BD needs to be generated; c, generating a patch package of the CD; each package has a download address. After the client side of the version A generates the AD package, the next time when another client side of the version A requests, the path of the AD package is directly good for the client side of the version A, and the client side does not need to compare the AD package generated again.
Preferably, this embodiment further includes:
s5: and pushing the patch compression packet to an object storage container such as oss or informing the CDN to refresh the file.
The os object storage containers and cdn are used for a download server that stores hot update resource packs (patch compressed packs), and are intended to increase the download speed of hot update packs and the like.
The oss object storage container is characterized by safety, stability, reliable data, mass storage and excellent performance; the function of the CDN is to cache content at different locations, and by using a load balancing technique, direct a user's request to the most appropriate cache server to obtain the content.
Therefore, through the steps, the downloading speed of the client can be improved, and the bandwidth of the server is not occupied.
S6: responding to the request of the client, and sending a download address (which can correspond to an object storage container such as oss or a CDN) of the patch compression package to the client; and the client updates the version of the client according to the patch compression packet.
Example two
In this embodiment, the first embodiment is further limited, and the method further includes:
1. configuring a packaging program at a client: the program for generating the client has the main responsibility of generating version file information corresponding to the version of the client, and enabling the client to release the version to the server.
As shown in fig. 3, the wrapper execution includes: generating a file list to be packaged; generating a version information file (including but not limited to version number, file path and file md5 value); packaging the client; and ending the flow.
By operating the client packing program, the client file and the version information file of a specific version can be automatically generated, the packing cost is reduced, and the abnormal packing deployment is reduced.
In a preferred example, the space can be simplified or optimized:
according to the scheme, the whole client package is uploaded every time in the new version, the packaging deployment program can be optimized to cache the previous version data, only changed files are uploaded every time, and the deployment efficiency is improved.
2. Deployment flow:
as shown in fig. 4, the file list and version information file generated by the packaging program may be copied to the hot update server.
According to the method and the device, automatic packing and deployment are achieved, manual participation is not needed, packing and deployment efficiency is improved remarkably, and the probability of faults caused by packing or deployment errors is reduced.
EXAMPLE III
The first embodiment is further limited, and the automatic packaging and deployment of the hot update server are further perfected without manual intervention.
The matching step of S1 is executed, before, further including:
s10: and configuring the latest version of the server to be an effective version.
When any version is required to take effect, only the currently effective version needs to be configured on the hot update server, and no matter what version is available at the external client, the hot update package of the hot update package is automatically packaged and deployed by the hot update service program without manual intervention.
Example four
In this embodiment, on the basis of the first embodiment, a version rollback scenario is further provided:
the method further comprises the following steps:
s7: the client receives an instruction of updating to a specified version;
s8: if the client version is lower than the specified version, updating the client version to the specified version by executing the step S3 and the following steps;
s9: if the client version is higher than the specified version, matching the version information file of the client version with the version information file of the specified version, extracting the file of the specified version which has difference relative to the client version, generating a rolling patch compression package, and rolling back the client version according to the rolling patch compression package.
Since the hot update package (patch compression package) for each version upgrade has already been generated during each version iterative deployment. Therefore, for the client with the low version upgraded to the high version, the hot update service program does not need to generate a new hot update package because the hot update package is already existed; and for the updated client, a rollback package needs to be generated.
EXAMPLE five
This embodiment corresponds to the first to fourth embodiments, and provides a specific application scenario:
1. client (client) first release version
a) Suppose that: the version number is v1.0, and the client program has 100 files such as resources which can be updated by heating or code word throttling. Generating version information files (with a format of version. json, such as version1.0) from the files through a packaging program;
b) deploying the resource files of the client to a server file directory in a version form, for example, establishing a directory client corresponding to the client under a server http server root directory/home/www, establishing a 1.0 folder under the client directory in a name of a version number, and placing all the resource files of the client under the 1.0 file;
c) deploying a hot update server program at a server, and assuming that the url address of the service is as follows: https:// client.game.com/version.version.version ═ timestamp, parameter version represents the version number uploaded by the client, and time represents the timestamp; at this time, the current effective version is set to be 1.0 (the configuration can be carried out through a configuration file or a database and the like);
d) when the client is started, accessing a hot update service program url, and uploading a version number of 1.0;
e) after receiving the request, the hot update service program checks that the client version is the same as the server set version, and returns { "code": 0 "," upgrade ": false", "version": 1.0 "}, wherein code is 0 to indicate that the server is successfully processed, upgrade is false to indicate that no update is needed, and version indicates the current version number of the server.
2. When the client generates an update, a second version1.1 needs to be released;
a) repeating the step 1.a to generate a second version information file, wherein the version information file is assumed to be version 1.1;
b) similar to 1.b, copy new version.1.1 and all files under 1.1 files, as:
c) modifying the configuration of the hot update server, and setting the latest version to be 1.1;
d) when a first old client is started, accessing a hot update service program url, and uploading a version number of 1.0;
after receiving the request, the hot update service program checks that the version of the client is different from the version set by the server, checks that the upgrade package files of 1.0 to 1.1 versions do not exist at present (assuming that 1.0-1.1.zip under the client/zip directory) according to the process, and enters step 2;
reading version information files of client/1.0/version.json and client/1.1/version.json by a program, comparing md5 values, and finding that 2 files of root/dir3/c.txt and root/dir3/d.png are updated;
thirdly, compressing and packaging the 2 files in the 1.1 directory into 1.0-1.1.zip files, and storing the files into client/zip/1.0-1.1. zip;
(iv) uploading client/zip/1.0-1.1.zip to oss or triggering cdn cache refresh (optional step)
Fifthly, returning client response data, such as { "code": 0 "," upgrade ": true", "version": 1.1 "," url ": https:// down.client.com/zip/1.0-1.1. zip" }, wherein the upgrade is true to indicate that updating is needed, and the url indicates the download address of the hot update package;
after receiving the response, the client side finds that the hot update exists, then starts the download module to download the 1.0-1.1.zip file, decompresses and loads the hot update file after the download is finished, sets the current version as the appointed version1.1 of the server side, and finishes the hot update of the client side version.
And the version number uploaded by the client at the next request is 1.1, and the update is not needed.
e) When the second old client is started, accessing the hot update service program url, and uploading a version number of 1.0;
firstly, after receiving a request, a hot update service program checks that the version of a client is different from the version set by a server, checks that an upgrade package file of 1.0 to 1.1 versions exists at present according to a process, can return data of the client without comparing version information at the moment, and has the same processes as 2.v and 2.vi later.
3. Similarly, when the third version 1.2 is released, as in the case of the 2 nd version, the version 1.2 is newly added in the server;
a) if the version1.0 of the old client is started, the step 2.d is performed again, and the hot update patch file 1.0-1.2.zip is newly generated.
4. If the 1.2 version has a serious problem and needs to be rolled back to the 1.1 version, only the configuration of the effective version of the hot update program needs to be modified to be 1.1, and a roll-back flag (aiming at indicating that the roll-back to the 1.1 version is needed) is set.
a) For the client with the version less than 1.1, the client can be normally upgraded to 1.1;
b) for the client of the 1.1 version, the upgrading is not needed;
c) for the client terminal which is upgraded to the 1.2 version, the version information files are compared with the version information files of the 1.2 version and the 1.1 version when the client terminal is requested to be similar to the version 2.d, the difference files of the 1.1 version are packaged into rolling back patch packages 1.2-1.1.zip, the client terminal responds to the similar information of the client terminal and the upgrading, and the client terminal is required to be decompressed after downloading the 1.2-1.1. zip.
Example six
This embodiment corresponds to the first to fifth embodiments, and provides a computer-readable storage medium, on which a computer program is stored, where the computer program is capable of implementing the steps included in the method for dynamic hot update according to any one of the first to fifth embodiments when the computer program is executed by a processor. The specific steps are not repeated here, and refer to the descriptions of the first to fifth embodiments for details.
In conclusion, the dynamic hot update method and the storage medium provided by the invention greatly simplify the generation and deployment complexity of the hot update package and improve the deployment efficiency; moreover, the efficiency of packaging and deploying the client files is improved, and the packaging cost is reduced; further, the efficiency of version rollback can be improved. The invention can improve the hot updating speed and reduce the probability of updating errors.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (7)
1.A method of dynamic thermal update, comprising:
when the client version needs to be updated, extracting a file with the difference between the latest version of the server and the client version by matching the version information file of the client version with the version information file of the latest version of the server;
generating a patch compression packet according to the files with the difference;
updating the client version according to the patch compression packet;
the version file information comprises each file path and a file check value thereof; generating a patch compression package according to the file with the difference specifically comprises:
traversing each file path in the version information file of the latest version of the server;
if the current traversed file path exists in the version information file of the latest version of the server and does not exist in the version file information of the version of the client, extracting the file corresponding to the current traversed file path as a newly added difference file;
if the currently traversed file path exists in the version information files of the latest version of the server and the version of the client at the same time, but the respective corresponding file check values are not identical, extracting the file corresponding to the currently traversed file path as a changed difference file;
and combining the newly added difference file and the changed difference file to obtain the file with the difference.
2. A method for dynamic thermal update as defined in claim 1, further comprising:
after the client is started, the server judges whether the version number of the client is consistent with the version number of the latest version of the server;
if the version numbers are not consistent, judging whether a patch compression packet corresponding to the version from the client to the latest version of the server exists;
if not, starting to execute the matching step and the subsequent steps, and storing the generated patch compression packet;
if yes, the patch compression package is directly sent to the client side, the client side updates the version according to the patch compression package, and the process is ended.
3. A method for dynamic thermal update as defined in claim 2, further comprising:
the client receives an instruction of updating to a specified version;
if the client version is lower than the specified version, updating the client version to the specified version by executing the matching step and the subsequent steps;
if the client version is higher than the specified version, matching the version information file of the client version with the version information file of the specified version, extracting the file of the specified version which is different from the client version, generating a rolling patch compression package, and rolling back the client version according to the rolling patch compression package.
4. A method for dynamic thermal update as defined in claim 1, further comprising:
and configuring the latest version of the server to be an effective version.
5. The method of claim 1, wherein the generating a patch compression package according to the file with the difference further comprises:
and pushing the patch compression packet to the oss object or the CDN.
6. A method for dynamic thermal update as defined in claim 1, further comprising:
and storing the patch compression package and the corresponding version information thereof to a hot update server.
7. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the steps of a method for dynamic thermal updating according to any of the claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010122796.3A CN113312066B (en) | 2020-02-27 | 2020-02-27 | Dynamic hot update method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010122796.3A CN113312066B (en) | 2020-02-27 | 2020-02-27 | Dynamic hot update method and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113312066A CN113312066A (en) | 2021-08-27 |
| CN113312066B true CN113312066B (en) | 2022-07-26 |
Family
ID=77370079
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010122796.3A Active CN113312066B (en) | 2020-02-27 | 2020-02-27 | Dynamic hot update method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113312066B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114465896A (en) * | 2022-03-30 | 2022-05-10 | 深信服科技股份有限公司 | Configuration information processing method, device, equipment and readable storage medium |
| CN114637527B (en) * | 2022-05-18 | 2022-08-19 | 海马云（天津）信息技术有限公司 | Hot update resource extraction and update method and device for cloud application |
| CN115712457A (en) * | 2023-01-04 | 2023-02-24 | 赤子城网络技术（北京）有限公司 | Item packaging method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103428188A (en) * | 2012-05-25 | 2013-12-04 | 北京小米科技有限责任公司 | Method and apparatus for file updating, and associated equipment |
| CN106528229A (en) * | 2016-11-03 | 2017-03-22 | 北京像素软件科技股份有限公司 | Game hot updating method and device |
| CN107346252A (en) * | 2016-05-07 | 2017-11-14 | 腾讯科技（深圳）有限公司 | Using update method and device |
| CN109656588A (en) * | 2018-11-14 | 2019-04-19 | 中国电力科学研究院有限公司 | A kind of method and system remotely fast implementing power information acquisition terminal software upgrading |
| CN110442377A (en) * | 2019-08-13 | 2019-11-12 | 网易（杭州）网络有限公司 | Service packs generation method, using update method, device and electronic equipment |
-
2020
- 2020-02-27 CN CN202010122796.3A patent/CN113312066B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103428188A (en) * | 2012-05-25 | 2013-12-04 | 北京小米科技有限责任公司 | Method and apparatus for file updating, and associated equipment |
| CN107346252A (en) * | 2016-05-07 | 2017-11-14 | 腾讯科技（深圳）有限公司 | Using update method and device |
| CN106528229A (en) * | 2016-11-03 | 2017-03-22 | 北京像素软件科技股份有限公司 | Game hot updating method and device |
| CN109656588A (en) * | 2018-11-14 | 2019-04-19 | 中国电力科学研究院有限公司 | A kind of method and system remotely fast implementing power information acquisition terminal software upgrading |
| CN110442377A (en) * | 2019-08-13 | 2019-11-12 | 网易（杭州）网络有限公司 | Service packs generation method, using update method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113312066A (en) | 2021-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113312066B (en) | Dynamic hot update method and storage medium | |
| CN106528224B (en) | Content updating method, server and system for Docker container | |
| CN101719073B (en) | Intelligent client-based on-demand downloading realization method | |
| CN110058873B (en) | Application page updating method, device, equipment and storage medium | |
| US6493871B1 (en) | Method and system for downloading updates for software installation | |
| US9733919B2 (en) | Updating web resources | |
| US20030195951A1 (en) | Method and system to dynamically detect, download and install drivers from an online service | |
| CN111381858B (en) | Application program upgrading method, server and terminal equipment | |
| CN107168730B (en) | Application program loading method, server and terminal | |
| US10360017B1 (en) | Updating program packages at distribution endpoint | |
| CN107528718B (en) | Method, device and system for acquiring resources | |
| CN113360456B (en) | Data archiving method, device, equipment and storage medium | |
| CN111263354A (en) | OTA differential upgrading method and device | |
| CN112596771A (en) | Method and system for uninterrupted service upgrade | |
| CN111314437A (en) | Resource package downloading method and device, storage medium and electronic device | |
| CN114328029B (en) | Backup method and device of application resources, electronic equipment and storage medium | |
| CN106708494B (en) | JAR upgrading method and device | |
| CN114564227A (en) | Application program updating method and device, electronic equipment and storage medium | |
| CN113190448A (en) | Test code updating method and device, electronic equipment and storage medium | |
| CN112256316A (en) | Client application updating method and client | |
| CN110673869B (en) | Library file loading method, device and system | |
| CN112256669A (en) | Data processing method and device, electronic equipment and readable storage medium | |
| US10860533B1 (en) | File size as an indicator of file properties | |
| CN110825406A (en) | Software upgrading method and related equipment | |
| CN114356245B (en) | Method and system for fast comparing and updating mass files |
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 |