CN111083214A - Method, device, client, server and system for updating application software - Google Patents
Method, device, client, server and system for updating application software Download PDFInfo
- Publication number
- CN111083214A CN111083214A CN201911252587.4A CN201911252587A CN111083214A CN 111083214 A CN111083214 A CN 111083214A CN 201911252587 A CN201911252587 A CN 201911252587A CN 111083214 A CN111083214 A CN 111083214A
- Authority
- CN
- China
- Prior art keywords
- application software
- file
- sub
- updated
- item
- 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.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a method, a device, a client, a server and a system for updating application software, wherein the method comprises the following steps: acquiring a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information; acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file; acquiring a patch file of the application software to be updated according to the summary information list and the latest application software; and transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated. Compared with the prior art, all users can update the application software by utilizing the summary information list from the client without storing the application software of each version.
Description
The application is a divisional application of Chinese patent application with the name of 'a method, a device, a client, a server and a system for updating application software' filed by Chinese patent office with the application number of 201310367633.1 on 21/8/2013.
Technical Field
The invention relates to the field of data processing, in particular to a method, a device, a client, a server and a system for updating application software.
Background
With the development of computer technology, the types and the quantity of application software are increasing day by day, meanwhile, different versions of the same type of application software are updated faster, and a user may just install one version of application software and a new version appears in a short time, so that the user faces the problem of how to update the old version of application software.
In the prior art, a patch file is generally used as an old version of application software update, and now, taking the application software installed in a mobile phone client as an example, referring to fig. 1, fig. 1 is a schematic diagram of application software update, wherein a server adds old version of application software, that is, oldversionqq.apk, and new version of application software, that is, newversionqq.apk, to a bsdiff tool at the same time, so as to finally obtain a patch file a. After the mobile phone client acquires the patch file A, the oldVersionQQ.apk and the patch file A which are stored in the client are simultaneously added into a bspatch tool, and finally the newVersionQQ.apk is obtained to finish updating the application software.
As can be seen from the above, in the software updating method in the prior art, the precondition that the server can finally obtain the patch file of any application software is that the server must have both the new version and the old version of the application software, and today that the application software is updated so quickly, it is difficult for the server to obtain each version of application software, so that the server cannot obtain all versions of application software, which limits that the application software of some users cannot be updated. Meanwhile, the algorithms of the bsdiff tool and the bspatch tool are complex, and the running speed is slow, so that the application software updating is performed by using the bsdiff tool and the bspatch tool, and the efficiency of the application software updating is reduced to a certain extent.
Disclosure of Invention
The invention provides a method, a device, a client, a server and a system for updating application software, so that the server does not need to store application software of each version, more users can update the application software, and meanwhile, a bsdiff tool and a bspatch tool are not needed, so that the updating efficiency of the application software is improved.
The invention provides a method for updating application software, which comprises the following steps:
acquiring a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information;
acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file;
acquiring a patch file of the application software to be updated according to the summary information list and the latest application software;
and transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated.
Preferably, the obtaining the patch file of the application software to be updated according to the summary information list and the latest application software includes:
determining any sub-item file in the latest application software as a target sub-item, and executing a patch file acquisition process: judging whether the target sub item exists in the summary information list, if so, acquiring a patch file according to summary information corresponding to the target sub item, wherein the summary information comprises first summary information and second summary information; if not, adding the file information corresponding to the target sub-item in the latest application software to the patch file; determining any sub-item file which does not execute the process of obtaining the patch file in the latest application software as a target sub-item, and continuing executing the process of obtaining the patch file until all sub-item files in the latest application software finish executing the process of obtaining the patch file;
and acquiring the patch file.
Preferably, the obtaining the patch file according to the summary information corresponding to the target sub-item, where the summary information includes first summary information and second summary information, includes:
acquiring first abstract information corresponding to the target sub-item in the abstract information list, and acquiring second abstract information corresponding to the target sub-item in the latest application software;
and judging whether the first summary information is the same as the second summary information, if so, marking the target sub-item as not to be updated and adding the target sub-item to a patch file, and if not, adding the file information corresponding to the target sub-item in the latest application software to the patch file.
Preferably, the transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated includes:
transmitting the patch file to the client;
and in the transmission process, the client synthesizes the patch file and the application software to be updated so as to complete the updating of the application software to be updated.
Preferably, in the process of transmitting, the synthesizing, by the client, the patch file and the application software to be updated to complete the updating of the application software to be updated includes:
in the transmission process, the client acquires any sub-item file in the patch file;
judging whether the sub-item files are marked as not to be updated, if so, adding file information corresponding to the sub-item files in the application software to be updated into the updated application software, and if not, adding file information corresponding to the sub-item files in the patch files into the updated application software;
the client side continuously acquires any sub-item file which is not executed in the patch file and is used for judging whether the sub-item file is marked as non-updated or not, and continuously executes the judgment whether the sub-item file is marked as non-updated or not until all sub-item files in the patch file are completely executed and are marked as non-updated or not;
and acquiring the updated application software to finish the updating of the application software to be updated.
The invention also includes a device for updating application software, the device comprising:
the system comprises a first acquisition module, a second acquisition module and a first updating module, wherein the first acquisition module is used for acquiring a summary information list corresponding to application software to be updated of a client, the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information;
the second acquisition module is used for acquiring the latest application software corresponding to the application software to be updated, and the latest application software comprises at least one sub-item file;
the third obtaining module is used for obtaining the patch file of the application software to be updated according to the summary information list and the latest application software;
and the synthesis module is used for transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated.
Preferably, the third obtaining module includes:
the first determining submodule is used for determining any sub-item file in the latest application software as a target sub-item;
the first judgment submodule is used for judging whether the target sub-item exists in the summary information list or not;
the first obtaining sub-module is used for obtaining the patch file according to the summary information corresponding to the target sub-item when the result of the first judging sub-module is yes, and the summary information comprises first summary information and second summary information;
the first adding sub-module is used for adding the file information corresponding to the target sub-item in the latest application software to the patch file when the result of the first judging sub-module is negative;
the first triggering sub-module is used for determining any sub-item file which does not trigger the first judging sub-module in the latest application software as a target sub-item, and continuing to trigger the first judging sub-module until all sub-item files in the latest application software trigger the first judging sub-module;
and the second obtaining sub-module is used for obtaining the patch file.
Preferably, the first obtaining sub-module includes:
the third obtaining submodule is used for obtaining first abstract information corresponding to the target sub-item in the abstract information list;
the fourth obtaining submodule is used for obtaining second abstract information corresponding to the target sub-item in the latest application software;
the second judgment submodule is used for judging whether the first abstract information is the same as the second abstract information;
the second adding sub-module is used for marking the target sub-item as not to be updated and adding the target sub-item to the patch file when the result of the second judging sub-module is yes;
and the third adding sub-module is used for adding the file information corresponding to the target sub-item in the latest application software to the patch file when the result of the second judging sub-module is negative.
Preferably, the synthesis module comprises:
the sending submodule is used for transmitting the patch file to the client;
and the first synthesis submodule is used for synthesizing the patch file and the application software to be updated by the client in the transmission process so as to finish the updating of the application software to be updated.
Preferably, the first synthesis submodule comprises:
a fifth obtaining sub-module, configured to, in the transmission process, obtain, by the client, any sub-item file in the patch file;
the third judgment submodule is used for judging whether the subitem file is marked as not to be updated or not;
a fourth adding sub-module, configured to add, when a result of the second determining sub-module is yes, file information corresponding to the sub-item file in the application software to be updated to the updated application software;
a fifth adding sub-module, configured to add, when a result of the second determining sub-module is negative, file information corresponding to the sub-item file in the patch file to the updated application software;
the second triggering sub-module is configured to continue to acquire any sub-item file in the patch file, which does not trigger the second judging sub-module, and continue to trigger the second judging sub-module until all sub-item files in the patch file complete triggering the second judging sub-module;
and the sixth obtaining submodule is used for obtaining the updated application software so as to complete the updating of the application software to be updated.
The invention also provides a client for updating the application software, which is used for sending the summary information list corresponding to the application software to be updated to a server, acquiring the patch file corresponding to the application software to be updated from the server, and synthesizing the patch file and the application software to be updated to finish the updating of the application software to be updated.
The invention also provides a server for updating the application software, which comprises a service server and a content distribution network server;
the service server is used for receiving the summary information list sent by the client and sending the summary information list to the content distribution network server;
and the content distribution network server is used for acquiring a patch file of the application software to be updated according to the summary information list and the latest application software corresponding to the application software to be updated, and transmitting the patch file to a client.
The invention also provides a system for updating the application software, which comprises a client and a server;
the client is the client;
the server is the server.
Firstly, acquiring a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information; secondly, acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file; thirdly, acquiring a patch file of the application software to be updated according to the summary information list and the latest application software; and finally, transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated, so as to complete the updating of the application software to be updated. Compared with the prior art, the server of the invention does not need to store application software of each version, and can theoretically update the application software of all users by using the summary information list from the client. Meanwhile, a bsdiff tool and a bspatch tool are not needed, and the efficiency of updating the application software is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a schematic diagram of an application software update;
FIG. 2 is a flowchart of a method for updating application software according to an embodiment of the present invention;
fig. 3 is a flowchart of a method for obtaining a patch file of application software to be updated according to an embodiment of the present invention;
fig. 4 is a flowchart of a method for synthesizing a patch file and application software to be updated according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating an apparatus for updating application software according to a second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a server according to a second embodiment of the present invention;
fig. 7 is a system configuration diagram of updating application software according to a second embodiment of the present invention;
fig. 8 is an information interaction diagram of a system for updating application software according to a fourth embodiment of the present invention;
fig. 9 is a flowchart of a method for calculating application summary information according to a fifth embodiment of the present invention;
fig. 10 is a view illustrating a file structure in a ZIP format according to a fifth embodiment of the present invention;
FIG. 11 is a flowchart illustrating a patch file generation process according to a fifth embodiment of the present invention;
fig. 12 is a flowchart of synthesizing a patch package according to a fifth embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the embodiment of the invention, application software to be updated is taken as a processing object, wherein the application software to be updated can be in a ZIP (compression and storage) file format, and a specific structure of the ZIP file format can be divided into a directory structure table and a data segment, wherein sub-item files in the directory structure table have a corresponding relation with the data segment.
Example one
Referring to fig. 2, fig. 2 is a flowchart of a method for updating application software provided in this embodiment, which specifically includes:
step 201: the method comprises the steps of obtaining a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one sub-item file, and the summary information list comprises the corresponding relation between the sub-item file and first summary information.
In this embodiment, first, the client obtains the application software to be updated, where the number of the application software to be updated is not limited, and may be one or more than one, and meanwhile, the application software to be updated may be in a ZIP (compressed and stored) file format. Secondly, the client acquires a summary information list corresponding to the application software to be updated, wherein one application software to be updated comprises at least one sub-item file, the summary information list comprises a corresponding relation between the sub-item file of the application software to be updated corresponding to the summary information list and first summary information, and specifically, the first summary information can be used for identifying the sub-item file. And finally, the client sends the acquired summary information list corresponding to the application software to be updated to the server.
In actual operation, the MD5, that is, Message-Digest Algorithm fifth version 5, may be used to obtain the first Digest information corresponding to the sub-item file, and specifically, the method for obtaining the first Digest information corresponding to the sub-item file is not limited. Wherein the first digest information may be composed of a CRC (cyclic redundancy check) and a length of the sub-entry file.
Step 202: and acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file.
In this embodiment, the server includes the latest application software of the application software to be updated, where the latest application software is the latest version of the application software to be updated. Therefore, the latest application software corresponding to the application software to be updated is obtained, wherein the latest application software comprises at least one sub-item file.
Step 203: and acquiring a patch file of the application software to be updated according to the summary information list and the latest application software.
In this embodiment, since the patch file is the difference content between the application software to be updated and the latest application software, and the summary information list may be used to identify the application software to be updated, the patch file of the application software to be updated may be obtained according to the comparison between the summary information list and the latest application software.
Specifically, referring to fig. 3, fig. 3 is a flowchart of a method for obtaining a patch file of application software to be updated, which may specifically include:
step 301: determining any sub-item file in the latest application software as a target sub-item;
in this embodiment, since the latest application software includes at least one sub-item file, any one of the sub-item files can be determined as a target sub-item as a processing object of a subsequent step.
Step 302: judging whether the target sub-item exists in the summary information list, if so, entering a step 303, and if not, entering a step 306;
in this embodiment, since the summary information list includes the sub-item file and the summary information corresponding thereto, it may be determined whether the target sub-item determined in the above step exists in the summary information list, if so, step 303 is entered, otherwise, step 306 is entered.
Step 303: acquiring first abstract information corresponding to the target sub-item in the abstract information list, and acquiring second abstract information corresponding to the target sub-item in the latest application software;
in this embodiment, when the target sub-item exists in the summary information list, first summary information corresponding to the target sub-item may be obtained in the summary information list, and second summary information corresponding to the target sub-item may be obtained in the latest application software, where an algorithm for obtaining the first summary information is the same as an algorithm for obtaining the second summary information.
Step 304: judging whether the first summary information is the same as the second summary information, if so, entering a step 305, and if not, entering a step 306;
in this embodiment, it is determined whether the obtained first summary information is the same as the second summary information, if so, it indicates that the sub-item file corresponding to the first summary information does not need to be updated, and step 305 is entered, otherwise, it indicates that the sub-item file corresponding to the first summary information needs to be updated, and step 306 is entered.
Step 305: marking the target sub-item as not updated and adding the target sub-item to a patch file;
in this embodiment, when the sub-entry file corresponding to the first summary information does not need to be updated, the target sub-entry is marked as not updated and added to the patch file.
Step 306: adding file information corresponding to the target sub-item in the latest application software to the patch file;
in this embodiment, when the sub-item file corresponding to the first summary information needs to be updated, or the target sub-item does not exist in the summary information list, the file information corresponding to the target sub-item in the latest application software is added to the patch file, so as to be used for updating the application software to be updated. And the file information is all data corresponding to the target sub-item.
Step 307: judging whether all the sub-item files in the latest application software complete the execution of the step 302, if not, entering the step 308, and if so, entering the step 309;
in this embodiment, it is determined whether all the child files in the latest application software complete execution of step 302, if yes, step 309 is performed, otherwise, step 308 is performed.
Step 308: determining any sub-item file which does not execute the step 302 in the latest application software as a target sub-item, and entering the step 302;
in this embodiment, any sub-item file in the latest application software that does not execute step 302 is determined as a target sub-item, and whether the target sub-item exists in the summary information list is continuously determined.
Step 309: and acquiring the patch file.
In this embodiment, after all the sub-item files in the latest application software complete step 302, the patch file at this time is acquired, so that the software to be updated is updated.
Step 204: and transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated.
In this embodiment, after the patch file is obtained, the patch file is transmitted to the client, and the client synthesizes the patch file and the application software with update to obtain the updated application software, and finally completes the update of the application software to be updated.
In actual operation, the patch file may be first transmitted to the client; secondly, in the transmission process, the client synthesizes the patch file and the application software to be updated so as to complete the updating of the application software to be updated.
Specifically, referring to fig. 4, fig. 4 is a flowchart of a method for synthesizing a patch file and application software to be updated, which may specifically include:
step 401: in the transmission process, the client acquires any sub-item file in the patch file;
in this embodiment, in the process that the server transmits the patch file to the client, that is, the client downloads the patch file, the client first obtains any one of the subitem files in the downloaded part of the patch file.
In the embodiment, the patch file and the application software to be updated are synthesized in the process of downloading the patch file, so that the updating time of the application software is saved, and the efficiency of updating the application software is improved.
Step 402: judging whether the sub-item file is marked as not to be updated, if so, entering a step 403, and if not, entering a step 404;
in this embodiment, it is determined whether the obtained sub-entry file is marked as not to be updated, if so, that is, the sub-entry file does not need to be updated, the process proceeds to step 403; otherwise, step 404 is entered.
Step 403: adding file information corresponding to the sub-item files in the application software to be updated into the updated application software;
in this embodiment, when the sub-entry file does not need to be updated, file information corresponding to the sub-entry file in the application software to be updated is added to the updated application software. And the file information is all data corresponding to the sub-item file in the application software to be updated.
Step 404: adding file information corresponding to the sub-item files in the patch files to the updated application software;
in this embodiment, when the sub-entry file is not marked as not to be updated, that is, the sub-entry file needs to be updated, the file information corresponding to the sub-entry file in the patch file is added to the updated application software.
In practice, the process of adding file information to the updated application software in steps 403 and 404 is a copy of the binary data stream.
Step 405: judging that all sub-item files in the patch file finish the execution step 402, if so, entering a step 407, and if not, entering a step 406;
in this embodiment, it is determined whether all the child files in the patch file have completed execution of step 402, if yes, step 407 is entered, otherwise, step 406 is entered.
Step 406: the client side continues to acquire any sub file except the sub file in the patch file, and continues to execute step 402;
in this embodiment, if all the sub-entry files in the patch file do not complete the execution of the step 402, the client acquires any other sub-entry file except the sub-entry file in the patch file, and continues to execute the step 402.
Step 407: and acquiring the updated application software to finish the updating of the application software to be updated.
In this embodiment, if all the sub-entry files in the patch file complete the execution of step 402, the obtained updated application software may be obtained to complete the update of the application software to be updated.
The embodiment first obtains a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one sub-item file, and the summary information list comprises a corresponding relation between the sub-item file and first summary information; secondly, acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file; thirdly, acquiring a patch file of the application software to be updated according to the summary information list and the latest application software; and finally, transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated, so as to complete the updating of the application software to be updated. Compared with the prior art, the server of the embodiment does not need to store application software of each version, and theoretically all users can update the application software by using the summary information list from the client. Meanwhile, a bsdiff tool and a bspatch tool are not needed, and the efficiency of updating the application software is improved.
Example two
Referring to fig. 5, fig. 5 is a structural diagram of an apparatus for updating application software according to this embodiment, where the apparatus may include:
a first obtaining module 501, configured to obtain a summary information list corresponding to application software to be updated of a client, where the application software to be updated includes at least one sub-item file, and the summary information list includes a corresponding relationship between the sub-item file and first summary information;
a second obtaining module 502, configured to obtain latest application software corresponding to the application software to be updated, where the latest application software includes at least one sub-item file;
a third obtaining module 503, configured to obtain a patch file of the application software to be updated according to the summary information list and the latest application software;
a synthesizing module 504, configured to transmit the patch file to the client, so as to synthesize the patch file and the application software to be updated, so as to complete updating of the application software to be updated.
Wherein the third obtaining module comprises:
the first determining submodule is used for determining any sub-item file in the latest application software as a target sub-item;
the first judgment submodule is used for judging whether the target sub-item exists in the summary information list or not;
the first obtaining sub-module is used for obtaining the patch file according to the summary information corresponding to the target sub-item when the result of the first judging sub-module is yes, and the summary information comprises first summary information and second summary information;
the first adding sub-module is used for adding the file information corresponding to the target sub-item in the latest application software to the patch file when the result of the first judging sub-module is negative;
the first triggering sub-module is used for determining any sub-item file which does not trigger the first judging sub-module in the latest application software as a target sub-item, and continuing to trigger the first judging sub-module until all sub-item files in the latest application software trigger the first judging sub-module;
and the second obtaining sub-module is used for obtaining the patch file.
Wherein the first obtaining sub-module includes:
the third obtaining submodule is used for obtaining first abstract information corresponding to the target sub-item in the abstract information list;
the fourth obtaining submodule is used for obtaining second abstract information corresponding to the target sub-item in the latest application software;
the second judgment submodule is used for judging whether the first abstract information is the same as the second abstract information;
the second adding sub-module is used for marking the target sub-item as not to be updated and adding the target sub-item to the patch file when the result of the second judging sub-module is yes;
and the third adding sub-module is used for adding the file information corresponding to the target sub-item in the latest application software to the patch file when the result of the second judging sub-module is negative.
Wherein the synthesis module comprises:
the sending submodule is used for transmitting the patch file to the client;
and the first synthesis submodule is used for synthesizing the patch file and the application software to be updated by the client in the transmission process so as to finish the updating of the application software to be updated.
Wherein the first synthesis submodule comprises:
a fifth obtaining sub-module, configured to, in the transmission process, obtain, by the client, any sub-item file in the patch file;
the third judgment submodule is used for judging whether the subitem file is marked as not to be updated or not;
a fourth adding sub-module, configured to add, when a result of the second determining sub-module is yes, file information corresponding to the sub-item file in the application software to be updated to the updated application software;
a fifth adding sub-module, configured to add, when a result of the second determining sub-module is negative, file information corresponding to the sub-item file in the patch file to the updated application software;
the second triggering sub-module is configured to continue to acquire any sub-item file in the patch file, which does not trigger the second judging sub-module, and continue to trigger the second judging sub-module until all sub-item files in the patch file complete triggering the second judging sub-module;
and the sixth obtaining submodule is used for obtaining the updated application software so as to complete the updating of the application software to be updated.
Referring to fig. 6, fig. 6 shows a server according to the present embodiment, where the server can be used to implement the method provided in the foregoing embodiments. Specifically, the method comprises the following steps:
the server may include components such as a memory 620 having one or more readable storage media, an input unit 630, an output unit 640 including a processor 610 having one or more processing cores, and a power supply 650. Wherein:
the memory 620 may be used to store software programs and modules, and the processor 610 executes various functional applications and data processing by operating the software programs and modules stored in the memory 620. The memory 620 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the computer, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 620 may also include a memory controller to provide the processor 610 and the input unit 630 access to the memory 620.
The input unit 630 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
The processor 610 is a control center of the server, connects the respective parts using various interfaces and lines, and performs various functions of the computer and processes data by operating or executing software programs and/or modules stored in the memory 620 and calling data stored in the memory 620, thereby integrally monitoring the mobile phone. Optionally, processor 610 may include one or more processing cores.
The server also includes a power supply 650 (e.g., a battery) for powering the various components, which may preferably be logically connected to the processor 610 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The power supply 650 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
Specifically, in this embodiment, the processor 610 loads an executable file corresponding to a process of one or more application programs into the memory 620 according to the following instructions, and the processor 610 runs the application programs stored in the memory 620, thereby implementing various functions:
acquiring a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information;
acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file;
acquiring a patch file of the application software to be updated according to the summary information list and the latest application software;
and transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated.
Preferably, the obtaining the patch file of the application software to be updated according to the summary information list and the latest application software includes:
determining any sub-item file in the latest application software as a target sub-item, and executing a patch file acquisition process: judging whether the target sub-item exists in the abstract information list, if so, acquiring first abstract information corresponding to the target sub-item in the abstract information list, and acquiring second abstract information corresponding to the target sub-item in the latest application software; when the first summary information is the same as the second summary information, marking the target sub-item as not to be updated and adding the target sub-item to a patch file; when the first summary information is different from the second summary information, or when the target sub item does not exist in the summary information list, adding file information corresponding to the target sub item in the latest application software to the patch file; determining any sub-item file which does not execute the process of obtaining the patch file in the latest application software as a target sub-item, and continuing executing the process of obtaining the patch file until all sub-item files in the latest application software finish executing the process of obtaining the patch file;
and acquiring the patch file.
Preferably, the transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated to complete the updating of the application software to be updated includes:
transmitting the patch file to the client;
and in the transmission process, the client synthesizes the patch file and the application software to be updated so as to complete the updating of the application software to be updated.
Preferably, in the process of transmitting, the synthesizing, by the client, the patch file and the application software to be updated to complete the updating of the application software to be updated includes:
in the transmission process, the client acquires any sub-item file in the patch file;
judging whether the sub-item files are marked as not to be updated, if so, adding file information corresponding to the sub-item files in the application software to be updated into the updated application software, and if not, adding file information corresponding to the sub-item files in the patch files into the updated application software;
the client side continuously acquires any sub-item file which is not executed in the patch file and is used for judging whether the sub-item file is marked as non-updated or not, and continuously executes the judgment whether the sub-item file is marked as non-updated or not until all sub-item files in the patch file are completely executed and are marked as non-updated or not;
and acquiring the updated application software to finish the updating of the application software to be updated.
The embodiment first obtains a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one sub-item file, and the summary information list comprises a corresponding relation between the sub-item file and first summary information; secondly, acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file; thirdly, acquiring a patch file of the application software to be updated according to the summary information list and the latest application software; and finally, transmitting the patch file to the client so as to synthesize the patch file and the application software to be updated, so as to complete the updating of the application software to be updated. Compared with the prior art, the server of the embodiment does not need to store application software of each version, and theoretically all users can update the application software by using the summary information list from the client. Meanwhile, a bsdiff tool and a bspatch tool are not needed, and the efficiency of updating the application software is improved.
EXAMPLE III
The embodiment of the present invention will be described from the perspective of a client for updating application software, where the method for updating application software may be specifically integrated in the client, and the client may be loaded in a terminal, where the terminal may specifically be a smart phone, a tablet computer, an electronic book reader, an MP3(Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3) player, an MP4(Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 3) player, a laptop portable computer, a desktop computer, and the like.
The present embodiment provides a client for updating application software, where the client may specifically be configured to:
firstly, sending a summary information list corresponding to application software to be updated to a server;
secondly, acquiring a patch file corresponding to the application software to be updated from the server;
and finally, synthesizing the patch file and the application software to be updated to complete the updating of the application software to be updated.
The embodiment also provides a server for updating application software, wherein the server comprises a service server and a content distribution network server;
the service server is used for receiving the summary information list sent by the client and sending the summary information list to the content distribution network server;
and the content distribution network server is used for acquiring a patch file of the application software to be updated according to the summary information list and the latest application software corresponding to the application software to be updated, and transmitting the patch file to a client.
Example four
Referring to fig. 7, fig. 7 is a system structure diagram of updating application software provided in this embodiment, where the system may include a client 701, a service server 702, and a content distribution network server 703;
the client 701 may be the client for updating the application software;
the service server 702 is configured to receive the summary information list sent by the client 701, and send the summary information list to the content distribution network server 703;
the content distribution network server 703 is configured to obtain a patch file of the application software to be updated according to the digest information list and the latest application software corresponding to the application software to be updated, and transmit the patch file to the client 701.
Referring to fig. 8, fig. 8 is an information interaction diagram of the system for updating application software provided in this embodiment, and the following details the working principle of each step in fig. 8:
A1. checking client application updates: the client reports all information of the installed applications, such as application names, package names, version numbers, etc., to the server (specifically referring to the reporting application information structure later).
A2. And returning application updating information: by comparing with the application information of the server, the scalable applications are found, the patch packages are found, and the abstracts are required to be uploaded to the server and sent to the client. These are the information of the application update (refer specifically to the following application update information structure).
A3. Judging which applications need to upload the application abstract: and after receiving the application updating information, the client analyzes an application list needing to upload the abstract to the server.
A4. And (3) reporting the abstract: and calculating summary information through old installation, and uploading the summary information to a server.
A5. And returning application updating information: and after receiving the summary information, the server returns the update information of the application.
B. And (3) generating a patch package flow:
B1. reporting an application abstract: and the logic server uploads the abstract to the CDN server.
B2. And (3) generating a patch package: after receiving the summary information, the CDN server compares the new version application to generate a patch package (specifically, refer to generation of a subsequent patch package).
C. Downloading and synthesizing a new package:
C1. downloading a patch package: and the user triggers downloading, acquires the URL address of the patch package through the updating information and downloads the patch package from the address.
C2. Returning to patch fragment 1, synthesizing: after returning part of the data, the composition can be started while downloading (refer to the composition of the following patch package).
C3. And returning to the patch segment 2, synthesizing: as with C2.
C4. And returning a patch segment n, and synthesizing: as with C2.
C5. And returning the last segment of the patch, and synthesizing: and after the last segment is received, the synthesis is completed, and the whole downloading and synthesizing process is completed.
Compared with the prior art, the server in the system provided by the embodiment does not need to store application software of each version, and theoretically all users can update the application software by using the summary information list from the client. Meanwhile, a bsdiff tool and a bspatch tool are not needed, and the efficiency of updating the application software is improved.
EXAMPLE five
In this embodiment, an APK file is taken as an example to introduce a method for updating application software, which includes the following specific steps:
first, a method for calculating application summary information of the APK file is described, referring to fig. 9, where fig. 9 is a flowchart of the method for calculating application summary information, specifically, the working principle of fig. 9 may include:
firstly, reading an APK file of an old version by using a zip tool;
and secondly, reading each item of the APK file in sequence, acquiring the file name, CRC and the uncompressed file length of each item, splicing the file name, CRC and uncompressed file length into the summary information of the sub-items, and adding the summary information into a summary information list structure.
And finally, repeating the previous step until each sub item in the APK file is traversed.
The structure of the summary information is specifically as follows:
map<string,long>apkDetail
string is the name of the file
Long: File CRC (4 bytes) + uncompressed size of the File (4 bytes)
Wherein, reporting the application information structure:
struct ClientApkDetail
{
0require string packageName; // client application Package name
1require string manifest Md 5; // client application manifest file md5
2require string version code; // version number
2optional map < string, long > apkDetail; // filename CRC + FileSize
}；
Application update information structure:
struct ApkPatchDetail
{
0require long patch Id; // delta file id for reporting
1require long pkgId4 NewVersion; novel version package id issued by server
2require string patch FileUrl; // incremental File download Path
3require int patch FileSize; // incremental File size (interface display used, Unit KB)
4require string patch field md 5; // delta file md5, usable for verification
5require string packageName; // application Package name
}；
Next, a patch file generation flow of the APK file is introduced, wherein, since the APK file is a file in a ZIP format, a file structure in the ZIP format is introduced first, with reference to fig. 10, fig. 10 is a file structure diagram in the ZIP format, and with reference to fig. 11, fig. 11 is a patch file generation flow diagram, specifically, the working principle of fig. 11 may include: and comparing each item of the summary information of the APK file with each item of the new version APK file, and finally determining the patch file of the APK file.
Finally, a process of synthesizing the patch package of the APK file is described, referring to fig. 12, fig. 12 is a process diagram of synthesizing the patch package, and it can be known from fig. 10 that the present embodiment completes synthesis of the patch package in the process of downloading the patch package, and realizes operation of synthesizing while downloading.
Specifically, the patch package file structure may be as follows:
/**
patch packet format
*
Central diritemcount number of file inner items
Central dirrcord 1+ isneedlepdate (borolean): description information of sub item 1
Central dirrcord 2+ isneedlepdate (borolean): description information of sub item 2
Central dirrcord 3+ isneedlepdate (borolean): description information of sub item 3
*......
Central dirrcordn + isneedleupdate (borolean): description information of sub-item n
File Data (Compressed): the data of the sub-items needing to be updated are in the order of 1 to n, and the sub-items needing to be updated only have the data.
Endo f central dirrecord: the directory end entry of the APK file.
*/
Description of the drawings: central dirrcord: corresponding to a sub-entry in the Central Directory (Directory structure table) in the ZIP file structure.
File Data (Compressed): corresponding to the File data segment following the Local File Header in the ZIP File structure.
EndofCentralDirRecord: end Of Central Directory corresponding to ZIP file.
The three items are directly read from the APK file of the new version to be filled, and the isNeedUpdate is obtained by calculation according to the application summary information uploaded by the client and the APK of the new version.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The method, the apparatus, the client, the server and the system for updating application software provided by the embodiment of the present invention are described in detail above, a specific example is applied in the present disclosure to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (13)
1. A method of updating application software, the method comprising:
acquiring a summary information list corresponding to application software to be updated of a client, wherein the application software to be updated comprises at least one subitem file, and the summary information list comprises the corresponding relation between the subitem file and first summary information;
acquiring the latest application software corresponding to the application software to be updated, wherein the latest application software comprises at least one sub-item file, and acquiring the file name and the second abstract information of each sub-item file in the latest application software;
obtaining a patch file of the application software to be updated through a Content Delivery Network (CDN) server according to the summary information list, file names and second summary information of all sub-item files in the latest application software, and the latest application software, wherein the patch file comprises n patch segments, and n is an integer greater than 1;
when an nth patch segment is obtained, merging the nth patch segment and the first (n-1) patch segments to obtain the patch file;
and transmitting the patch file obtained after combination to the client so as to synthesize the patch file and the application software to be updated, so as to complete the updating of the application software to be updated.
2. The method according to claim 1, wherein the obtaining a patch file of the application software to be updated according to the summary information list, the file name and the second summary information of each sub-item file in the latest application software, and the latest application software comprises:
determining any sub-item file in the latest application software as a target sub-item, and executing the following steps aiming at the target sub-item until all sub-item files in the latest application software are traversed;
judging whether the target sub-item exists in the summary information list or not according to the file name of the target sub-item;
if the target sub item exists in the summary information list, judging whether first summary information and second summary information corresponding to the target sub item are the same, if so, marking the target sub item as not to be updated and adding the target sub item to a patch file, and if not, adding file information corresponding to the target sub item to the patch file;
and if the target sub item does not exist in the summary information list, adding file information corresponding to the target sub item in the latest application software to the patch file.
3. The method according to claim 1, wherein the first summary information and the second summary information are each composed of a cyclic redundancy check CRC of the sub-entry file corresponding thereto and a length of the sub-entry file.
4. The method according to claim 1, wherein the transmitting the patch file obtained after the merging to the client to synthesize the patch file with the application software to be updated so as to complete the updating of the application software to be updated comprises:
transmitting the patch file obtained after combination to the client;
and in the transmission process, the client synthesizes the patch file and the application software to be updated so as to complete the updating of the application software to be updated.
5. The method according to claim 4, wherein during the transmitting, the client synthesizes the patch file with the application software to be updated to complete the updating of the application software to be updated, and the method comprises:
in the transmission process, the client acquires any sub-item file in the patch file;
judging whether the sub-item files are marked as not to be updated, if so, adding file information corresponding to the sub-item files in the application software to be updated into the updated application software, and if not, adding file information corresponding to the sub-item files in the patch files into the updated application software;
the client side continuously acquires any sub-item file which is not executed in the patch file and is used for judging whether the sub-item file is marked as non-updated or not, and continuously executes the judgment whether the sub-item file is marked as non-updated or not until all sub-item files in the patch file are completely executed and are marked as non-updated or not;
and acquiring the updated application software to finish the updating of the application software to be updated.
6. An apparatus for updating application software, the apparatus comprising:
the system comprises a first acquisition module, a second acquisition module and a first updating module, wherein the first acquisition module is used for acquiring a summary information list corresponding to application software to be updated of a client, the application software to be updated comprises at least one sub-item file, the summary information list comprises a corresponding relation between the sub-item file and first summary information, and the file name and second summary information of each sub-item file in the latest application software are acquired;
the second acquisition module is used for acquiring the latest application software corresponding to the application software to be updated, and the latest application software comprises at least one sub-item file;
a third obtaining module, configured to obtain, according to the summary information list, file names and second summary information of sub-item files in the latest application software, and the latest application software, a patch file of the application software to be updated through a content delivery network CDN server, where the patch file includes n patch segments, and n is an integer greater than 1;
a synthesis module, configured to, when an nth patch segment is obtained, merge the nth patch segment with a previous (n-1) patch segment to obtain the patch file;
the synthesis module is further configured to transmit the patch file obtained after the combination to the client, so as to synthesize the patch file and the application software to be updated, so as to complete the update of the application software to be updated.
7. The apparatus of claim 6, wherein the third obtaining module comprises:
the first determining submodule is used for determining any sub-item file in the latest application software as a target sub-item, and triggering the first judging submodule aiming at the target sub-item until all sub-item files in the latest application software are traversed;
the first judgment sub-module is used for judging whether the target sub-item exists in the summary information list according to the file name of the target sub-item;
the first obtaining sub-module is used for judging whether the target sub-item exists in the summary information list in the first judging sub-module, judging whether first summary information and second summary information corresponding to the target sub-item are the same, if so, marking the target sub-item as not to be updated and adding the target sub-item to a patch file, and if not, adding file information corresponding to the target sub-item to the patch file;
and the first adding sub-module is used for adding the file information corresponding to the target sub-item in the latest application software to the patch file if the first judging sub-module judges that the target sub-item does not exist in the summary information list.
8. The apparatus according to claim 7, wherein the first summary information and the second summary information are each composed of a cyclic redundancy check CRC of the sub-entry file corresponding thereto and a length of the sub-entry file.
9. The apparatus of claim 6, wherein the synthesis module comprises:
the sending submodule is used for transmitting the patch file obtained after combination to the client;
and the first synthesis submodule is used for synthesizing the patch file and the application software to be updated by the client in the transmission process so as to finish the updating of the application software to be updated.
10. The apparatus of claim 9, wherein the first synthesis submodule comprises:
a fifth obtaining sub-module, configured to, in the transmission process, obtain, by the client, any sub-item file in the patch file;
the third judgment submodule is used for judging whether the subitem file is marked as not to be updated or not;
a fourth adding sub-module, configured to add, when a result of the second determining sub-module is yes, file information corresponding to the sub-item file in the application software to be updated to the updated application software;
a fifth adding sub-module, configured to add, when a result of the second determining sub-module is negative, file information corresponding to the sub-item file in the patch file to the updated application software;
the second triggering sub-module is configured to continue to acquire any sub-item file in the patch file, which does not trigger the second judging sub-module, and continue to trigger the second judging sub-module until all sub-item files in the patch file complete triggering the second judging sub-module;
and the sixth obtaining submodule is used for obtaining the updated application software so as to complete the updating of the application software to be updated.
11. The client side is used for sending a summary information list corresponding to application software to be updated to a server, wherein the summary information list comprises a corresponding relation between file names of all sub-item files in the application software to be updated and first summary information, acquiring a patch file corresponding to the application software to be updated from the server, and synthesizing the patch file and the application software to be updated to finish updating of the application software to be updated.
12. A server for updating application software, wherein the server comprises a service server and a content distribution network server;
the service server is used for receiving the summary information list sent by the client, wherein the summary information list comprises the corresponding relation between the file name of each sub-item file in the application software to be updated and the first summary information, and the summary information list is sent to the content distribution network server;
the content distribution network server is configured to obtain a patch file of the application software to be updated according to the summary information list, the file name and the second summary information of each sub-item file in the latest application software, and the latest application software corresponding to the application software to be updated, transmit the patch file to a client, and merge the nth patch segment with the first (n-1) patch segments when the nth patch segment is obtained, so as to obtain the patch file, where the patch file includes n patch segments, and n is an integer greater than 1.
13. A system for updating application software, the system comprising a client and a server;
the client is the client of claim 11 above;
the server of claim 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911252587.4A CN111083214A (en) | 2013-08-21 | 2013-08-21 | Method, device, client, server and system for updating application software |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310367633.1A CN104426924A (en) | 2013-08-21 | 2013-08-21 | Method, apparatus, client, server and system for updating application software |
| CN201911252587.4A CN111083214A (en) | 2013-08-21 | 2013-08-21 | Method, device, client, server and system for updating application software |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310367633.1A Division CN104426924A (en) | 2013-08-21 | 2013-08-21 | Method, apparatus, client, server and system for updating application software |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111083214A true CN111083214A (en) | 2020-04-28 |
Family
ID=52974856
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310367633.1A Pending CN104426924A (en) | 2013-08-21 | 2013-08-21 | Method, apparatus, client, server and system for updating application software |
| CN201911252587.4A Pending CN111083214A (en) | 2013-08-21 | 2013-08-21 | Method, device, client, server and system for updating application software |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310367633.1A Pending CN104426924A (en) | 2013-08-21 | 2013-08-21 | Method, apparatus, client, server and system for updating application software |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN104426924A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113457148A (en) * | 2021-06-30 | 2021-10-01 | 网易（杭州）网络有限公司 | Game information processing method and device, electronic equipment and storage medium |
| CN116257278A (en) * | 2023-05-15 | 2023-06-13 | 北京阿帕科蓝科技有限公司 | Patch execution method of application software and storage medium |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015821B (en) * | 2016-01-28 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Incremental updating method and device |
| CN106775845A (en) * | 2016-11-30 | 2017-05-31 | 用友优普信息技术有限公司 | A kind of method of software installation upgrading |
| CN106599167B (en) * | 2016-12-09 | 2020-11-20 | 苏州浪潮智能科技有限公司 | System and method for supporting increment updating of database |
| CN107395770B (en) * | 2017-09-06 | 2020-08-04 | 武汉斗鱼网络科技有限公司 | Data synchronization method and device |
| CN107682436A (en) * | 2017-10-09 | 2018-02-09 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and equipment of more new file |
| CN112052020A (en) * | 2019-06-06 | 2020-12-08 | 广州市百果园信息技术有限公司 | Data updating method, device, system, computer equipment and storage medium |
| CN110413262A (en) * | 2019-07-23 | 2019-11-05 | 北京启迪区块链科技发展有限公司 | A kind of management method of business function, apparatus and system |
| CN111158722A (en) * | 2019-12-27 | 2020-05-15 | 无锡中尧网络科技有限公司 | Method for updating heat of mobile client |
| CN112394961A (en) * | 2020-11-24 | 2021-02-23 | 平安普惠企业管理有限公司 | Data updating system, method, device, equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050071839A1 (en) * | 2003-09-25 | 2005-03-31 | Curitel Communications, Inc. | Communication terminal and communication network for partially updating software, software update method, and software creation device and method therefor |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9563417B2 (en) * | 2006-12-29 | 2017-02-07 | International Business Machines Corporation | Patch management automation tool for UNIX, APARXML |
| CN102724308A (en) * | 2012-06-13 | 2012-10-10 | 腾讯科技（深圳）有限公司 | Software update method and software update system |
-
2013
- 2013-08-21 CN CN201310367633.1A patent/CN104426924A/en active Pending
- 2013-08-21 CN CN201911252587.4A patent/CN111083214A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050071839A1 (en) * | 2003-09-25 | 2005-03-31 | Curitel Communications, Inc. | Communication terminal and communication network for partially updating software, software update method, and software creation device and method therefor |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113457148A (en) * | 2021-06-30 | 2021-10-01 | 网易（杭州）网络有限公司 | Game information processing method and device, electronic equipment and storage medium |
| CN116257278A (en) * | 2023-05-15 | 2023-06-13 | 北京阿帕科蓝科技有限公司 | Patch execution method of application software and storage medium |
| CN116257278B (en) * | 2023-05-15 | 2023-10-31 | 北京阿帕科蓝科技有限公司 | Patch execution method of application software and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104426924A (en) | 2015-03-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111083214A (en) | Method, device, client, server and system for updating application software | |
| KR102042723B1 (en) | Methods for updating applications | |
| US10055216B2 (en) | Minimizing image copying during partition updates | |
| US8543543B2 (en) | Hash-based file comparison | |
| EP3488337B1 (en) | Shared software libraries for computing devices | |
| CN1641583B (en) | Self-describing software image update components | |
| US9244673B2 (en) | System and method for updating application archive files | |
| KR101735719B1 (en) | Operating system auto-update procedure | |
| US9823915B1 (en) | Software container format | |
| US9250946B2 (en) | Efficient provisioning of cloned virtual machine images using deduplication metadata | |
| WO2017157178A1 (en) | Mobile terminal application update method and device | |
| CN108874409B (en) | Information updating method, device, server and system | |
| CN102541596A (en) | Operating system upgrading method and device | |
| WO2014200541A1 (en) | App package deployment | |
| CN110532016B (en) | Version management method, version updating method and version management system | |
| US11620257B2 (en) | Data archive release in context of data object | |
| CN114461262A (en) | Data processing method, system, device, equipment and computer storage medium | |
| CN112947981A (en) | Application program resource updating method and device, terminal equipment and server | |
| CN103294742A (en) | Apparatus and method for determining duplication of content in portable terminal | |
| US20140359077A1 (en) | Method and apparatus for transmitting symbol files | |
| CN114391136A (en) | Enhanced virtual machine image management system | |
| CN109582347B (en) | Method and device for acquiring front-end codes | |
| CN115840598A (en) | Micro front-end architecture system, development method, device and medium based on application market | |
| EP2680135A1 (en) | Methods for updating applications | |
| CN114895916A (en) | Code deployment method, device, storage medium and electronic equipment |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40021697 Country of ref document: HK |
|
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200428 |
|
| RJ01 | Rejection of invention patent application after publication |