CN111158719A - Application software upgrading method and device - Google Patents
Application software upgrading method and device Download PDFInfo
- Publication number
- CN111158719A CN111158719A CN201911369464.9A CN201911369464A CN111158719A CN 111158719 A CN111158719 A CN 111158719A CN 201911369464 A CN201911369464 A CN 201911369464A CN 111158719 A CN111158719 A CN 111158719A
- Authority
- CN
- China
- Prior art keywords
- installation package
- installation
- upgrading
- application
- file
- 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.)
- Granted
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/60—Software deployment
- G06F8/61—Installation
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides an application software upgrading method and device, wherein the method comprises the following steps: when a batch upgrading task is received, obtaining upgrading strategy information and a plurality of installation packages; determining the installation sequence of each installation package, calling an installation management service to sequentially install each installation package, and recording the installation result of each installation package; judging whether an installation package with installation failure exists according to the installation result of each installation package; if the target installation package exists, determining the installation package with the installation failure as the target installation package, and judging whether the target installation package has the associated installation package; and if so, acquiring the corresponding application version before upgrading, and restoring the target installation package and the application version corresponding to the associated installation package to the application version before upgrading. By applying the method, when any installation package fails to be installed, the installation package and the application version of the application software corresponding to the associated installation package can be restored to the application version before upgrading, and the consistency of the versions of the application software with the linkage relation is ensured.
Description
Technical Field
The invention relates to the technical field of software upgrading, in particular to an application software upgrading method and device.
Background
With the development of computer and internet technologies, various application software is also emerging. In the process of using each application software, in order to meet the requirements of users on each application software, each application software needs to be updated and upgraded.
In the prior art, when a client needs to upgrade a plurality of application software, an application upgrade list needs to be sent to a server to obtain an installation package of each application software to be upgraded in the application upgrade list. When the application software is upgraded in batches, the application software with the linkage relationship can be synchronously upgraded, and if any one application software fails to be upgraded in the process of upgrading the application software with the linkage relationship, the application software linked with the application software cannot be normally used even if the application software is successfully upgraded. Therefore, in the prior art, in the process of upgrading the application software, the consistency of the versions of the application software with the linkage relationship cannot be ensured, and the application software can not be used normally after being upgraded successfully.
Disclosure of Invention
In view of this, the present invention provides an application software upgrading method, by which, when any installation package fails to be installed and an associated installation package exists in the installation package, the installation package and an application version of application software corresponding to the associated installation package can be restored to an application version before upgrading, so as to ensure consistency of versions between application software having a linkage relationship.
The invention also provides an application software upgrading device which is used for ensuring the realization and the application of the method in practice.
An application software upgrade method, comprising:
when a batch upgrading task which is sent by a server and corresponds to each application software to be upgraded is received, obtaining upgrading strategy information and a plurality of installation packages which correspond to the batch upgrading task, wherein each installation package and each application software to be upgraded are in a one-to-one correspondence relationship;
determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
judging whether an installation package with installation failure exists according to the installation result of each installation package;
if the installation package with the installation failure exists, determining that the installation package with the installation failure is a target installation package, and judging whether an installation package associated with the target installation package exists in all installation packages except the target installation package;
if the installation package associated with the target installation package exists, acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrading corresponding to the target installation package.
Optionally, the obtaining of the upgrade policy information and the plurality of installation packages corresponding to the batch upgrade tasks includes:
downloading batch upgrading files corresponding to the batch upgrading tasks, and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, secret key information and upgrading file verification information;
decrypting the batch upgrading files by applying the key information, and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
decompressing the compressed packet, obtaining upgrading strategy information and a plurality of application files corresponding to the batch upgrading tasks contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
and when the verification of each application file passes, acquiring the installation package contained in each application file.
Optionally, the method for verifying each application file by applying the upgrade file verification information and the upgrade policy information includes:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
Optionally, the method further includes, before the installation of each installation package in sequence:
obtaining an upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information;
judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded;
and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
The above method, optionally, further includes:
and if the installation packages with failed installation do not exist, deleting the backed-up application version before upgrading corresponding to each installation package.
Optionally, in the method, the restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the corresponding application version before upgrade includes:
judging whether the installation package associated with the target installation package is successfully installed;
and if the installation package associated with the target installation package is successfully installed, the application software corresponding to the installation package associated with the target installation package is uninstalled, and the application version corresponding to the target installation package and the application version corresponding to the associated installation package are restored to the corresponding application version before upgrading.
An application software upgrade apparatus comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring upgrading strategy information and a plurality of installation packages corresponding to batch upgrading tasks when the batch upgrading tasks corresponding to application software to be upgraded and sent by a server are received, and each installation package and each application software to be upgraded are in one-to-one correspondence;
the installation unit is used for determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
the first judgment unit is used for judging whether the installation packages with installation failure exist according to the installation results of the installation packages;
a second determination unit, configured to determine, if an installation package that fails to be installed exists, that the installation package that fails to be installed is a target installation package, and determine, in each installation package other than the target installation package, whether an installation package associated with the target installation package exists;
and the restoring unit is used for acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package if the installation package associated with the target installation package exists, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the corresponding application version before upgrading.
The above apparatus, optionally, the obtaining unit includes:
the downloading subunit is used for downloading batch upgrading files corresponding to the batch upgrading tasks and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, key information and upgrading file verification information;
the decryption subunit is used for decrypting the batch upgrading files by applying the key information and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
the verification subunit is used for decompressing the compressed packet, acquiring the upgrading strategy information and a plurality of application files contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
and the obtaining subunit is used for obtaining the installation package contained in each application file when the application files pass the verification.
The above apparatus, optionally, the verifying subunit is configured to:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
The above apparatus, optionally, further comprises:
the backup unit is used for acquiring the upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information; judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded; and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
A storage medium, the storage medium comprising stored instructions, wherein when the instructions are executed, the apparatus on which the storage medium is located is controlled to execute the above-mentioned application software upgrading method.
An electronic device comprising a memory, and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by the one or more processors to perform the above-described application software upgrade method.
Compared with the prior art, the invention has the following advantages:
the invention provides an application software upgrading method, which comprises the following steps: when a batch upgrading task which is sent by a server and corresponds to each application software to be upgraded is received, obtaining upgrading strategy information and a plurality of installation packages which correspond to the batch upgrading task, wherein each installation package and each application software to be upgraded are in a one-to-one correspondence relationship; determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package; judging whether an installation package with installation failure exists according to the installation result of each installation package; if the installation package with the installation failure exists, determining that the installation package with the installation failure is a target installation package, and judging whether an installation package associated with the target installation package exists in all installation packages except the target installation package; if the installation package associated with the target installation package exists, acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrading corresponding to the target installation package. By applying the method, when any installation package fails to be installed and the installation package has the associated installation package, the application version of the application software corresponding to the installation package and the associated installation package can be restored to the application version before upgrading, and the consistency of the versions of the application software with the linkage relation is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for upgrading application software according to an embodiment of the present invention;
fig. 2 is a flowchart of another method of an application software upgrading method according to an embodiment of the present invention;
fig. 3 is a flowchart of another method of an application software upgrading method according to an embodiment of the present invention;
fig. 4 is a device structure diagram of an application software upgrading device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
In this application, relational terms such as first and second, and the like are 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, and 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 invention is operational with numerous general purpose or special purpose computing device environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multi-processor apparatus, distributed computing environments that include any of the above devices or equipment, and the like.
An embodiment of the present invention provides an application software upgrading method, which may be applied to multiple system platforms, where an execution main body of the method may be an application management and control service of a computer terminal or various mobile devices, where the application management and control service is a system service integrated in a terminal, and may specifically be a system process, used for installation, download, uninstallation, and the like of application software, and a flowchart of the method is shown in fig. 1, and specifically includes:
s101: when a batch upgrading task which is sent by a server and corresponds to each application software to be upgraded is received, obtaining upgrading strategy information and a plurality of installation packages which correspond to the batch upgrading task, wherein each installation package and each application software to be upgraded are in a one-to-one correspondence relationship;
in the embodiment of the invention, the application management and control service is arranged in the client, and the application management and control service can send the upgrading inquiry request corresponding to each application software to the server in real time so as to determine whether the current version of each application software needs to be upgraded and updated. And if a plurality of application software in the client needs to be upgraded, the server sends batch upgrading tasks corresponding to the application software to be upgraded to the client. Obtaining upgrading strategy information and a plurality of installation packages corresponding to the batch upgrading tasks, wherein the upgrading strategy information comprises an upgrading strategy of each application software to be upgraded, and each installation package corresponds to one application software to be upgraded respectively.
It should be noted that the upgrade policy of each application software to be upgraded may be an upgrade policy for upgrading a single application software, may also be an upgrade policy for upgrading a plurality of application software in a linkage manner at the same time, and may also be an upgrade policy for upgrading a plurality of application software in batch.
S102: determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
in the embodiment of the invention, in the process of installing each installation package, the application management and control service can only install one installation package at a time, and before installing each installation package, the installation sequence of each installation package needs to be determined. And after the installation sequence of each installation package is determined, calling preset installation management service to install each installation package according to the installation sequence. The installation management service is an installation program which is arranged in the client and used for installing the installation package. And recording the installation result of each installation package in the process of sequentially installing each installation package by the installation management service.
It should be noted that the installation management service in the present invention may specifically be a PackageManager service, and when the PackageManager service is applied to install each installation package, the installation management service may be a pm command applied to the PackageManager service to install the installation package corresponding to each application software. The pm command may specifically be a pminstall + install file path command, and may be used to monitor an installation result of each installation package.
S103: judging whether an installation package with installation failure exists according to the installation result of each installation package;
in the embodiment of the invention, the installation result of each installation package is recorded in the process of installing each installation package, and when the last installation package finishes installation, the last installation result is recorded no matter whether the installation result of the last installation package is successfully installed or not. And judging whether the installation packages with installation failure exist in the process of installing the installation packages according to the installation sequence according to the installation result of each installation package.
It should be noted that, in the present invention, the installation package with failed installation specifically includes an application version corresponding to the installation package that is not supported by the client, and the installation package is tampered or replaced in the installation process, which results in the installation of the installation package failing, so that the corresponding application software fails to be upgraded.
S104: if the installation package with the installation failure exists, determining that the installation package with the installation failure is a target installation package, and judging whether an installation package associated with the target installation package exists in all installation packages except the target installation package;
in the embodiment of the invention, if the installation package with the installation failure exists, the upgrade failure of the application software corresponding to the installation package with the installation failure is represented, and the installation package with the installation failure is determined as the target installation package. In the process of upgrading application software to be upgraded in batches, a plurality of installation packages may fail to be installed, and each installation package which fails to be installed is determined as a target installation package. For each target installation package, judging whether an installation package associated with the target installation package exists, namely judging whether the application software corresponding to the installation package with failed installation has linkage application software.
S105: if the installation package associated with the target installation package exists, acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrading corresponding to the target installation package.
In the embodiment of the invention, if the installation package which fails to be installed has the associated installation package, the corresponding application software is characterized to have the linked application software.
It can be understood that if the installation package fails to be installed, the corresponding application software fails to be upgraded and cannot be applied to the client, and if the application software is linked with other application software, the application software linked with the application software cannot be normally used even if the application software is upgraded successfully.
Specifically, when the installation package fails to be installed, if the installation package has an associated installation package, the installation package and the pre-upgrade application version corresponding to the associated installation package are obtained, wherein before the installation of each installation package, the pre-upgrade application version of the corresponding application software is backed up, and after any installation package fails to be installed, the pre-upgrade application version can be recovered. For each associated installation package, if one installation package fails to be installed, the application version corresponding to the associated installation package is also restored to the application version before upgrading. For example, installation package A, installation package B, and installation package C are associated. And when the installation package A fails to be installed, the application versions of the application software corresponding to the installation package A, the installation package B and the installation package C are all required to be restored to the application versions before upgrading.
In the application software upgrading method provided by the embodiment of the invention, the application management and control service is set in the client and is used for monitoring whether the server has application software needing to be upgraded in batches or not currently. When the server is detected to send the batch upgrading tasks, the fact that a plurality of application software in the client needs to be upgraded is represented, and upgrading strategy information and a plurality of installation packages corresponding to the batch upgrading tasks are obtained. And determining the installation sequence of each installation package, realizing the installation process of each installation package through the installation management service, and simultaneously recording the installation result of each installation package. And after the last installation package finishes installation and records the installation result, judging whether the installation package with installation failure exists according to the installation result of each installation package. If the installation package is associated with other installation packages, representing that the corresponding application software is in linkage relation with other application software, and restoring the installation package failed in installation and the application version of the application software corresponding to the associated installation package to the application version before the upgrade, which is backed up in advance.
It should be noted that, in the embodiment of the present invention, there may be a plurality of installation packages that have failed to be installed, and for each installation package that has failed to be installed, it is determined whether the installation package has an associated installation package. If one installation package fails to be installed among the related installation packages, the related other installation packages cannot be normally used even if the installation is successful.
Specifically, for an installation package that is successfully installed, if the installation package associated with the installation package fails to be installed, the current application version of the application software corresponding to the installation package that is successfully installed is uninstalled, and the application version corresponding to the installation package that is successfully installed is restored to the backed-up application version before upgrade. When the current application version of the application software is uninstalled, the file can be uninstalled through pmuninstantall + of the pm commands.
Optionally, in the present invention, if the installation package that fails to be installed does not have the associated installation package, it is characterized that the corresponding application software does not have a linkage relationship with other application software, and at this time, the application version of the application software corresponding to the installation package may be restored to the application version before upgrade.
Based on the method provided by the above embodiment, in each application software of the client, there are usually mutually linked application software, and generally, there is a mutual dependency relationship between each linked application software, for example, in the payment software, it is necessary to be mutually linked with the security software, and in the payment process of the payment software, the security software provides a secure payment environment for the payment software, so as to complete the payment process of the payment software. If the payment software and the security software are upgraded successfully and the linked security software is upgraded unsuccessfully, the payment software cannot be paid or personal information is stolen in the payment process. If the payment software is upgraded successfully, the linkage security software is upgraded unsuccessfully and is restored to the application version before upgrading, and the payment software may fail in the payment process due to the problems of version mismatch and the like. Therefore, when the payment software fails to be upgraded or the safety software fails to be upgraded, the application versions of the payment software and the safety software are both restored to the application version before the upgrade, and the next linkage upgrade is waited.
By applying the method provided by the embodiment of the invention, when any installation package fails to be installed and the installation package has the associated installation package, the application version of the application software corresponding to the installation package and the associated installation package can be restored to the application version before upgrading, so that the consistency of the versions of the application software with the linkage relation is ensured.
In the method provided in the embodiment of the present invention, based on the content of step S101, a process of obtaining the upgrade policy information and the plurality of installation packages corresponding to the batch upgrade tasks is shown in fig. 2, and may specifically include:
s201: downloading batch upgrading files corresponding to the batch upgrading tasks, and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, secret key information and upgrading file verification information;
in the embodiment of the invention, before sending the batch upgrading task, the server stores the installation package and the upgrading strategy information corresponding to the application software to be upgraded into the batch upgrading file, and in order to prevent the installation package from being replaced or tampered, the server encrypts the batch upgrading file and stores the encrypted related information in the file header of the batch upgrading file. When a batch upgrading task sent by a server is received, a batch upgrading file corresponding to the batch upgrading task is downloaded, and file header information of the batch upgrading file is obtained, so that compression package position parameters, key information and upgrading file verification information contained in the file header information are obtained.
It should be noted that the header information of the batch upgrade file may specifically include information such as a file type, a file format, a file size, and a file saving location.
Further, the batch upgrade file may be a binary file with a custom format, and the header information may be a start-stop position of the binary file.
S202: decrypting the batch upgrading files by applying the key information, and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
in the embodiment of the invention, the key information in the file header information is obtained, the key information is applied to decrypt the batch upgrading files, and the compressed packets in the batch upgrading files can be obtained after decryption.
And determining the position of the compressed package stored in the batch upgrading file according to the position parameter of the compressed package in the file header information so as to obtain the compressed package contained in the batch upgrading file.
It should be noted that, when the server determines that the client needs to upgrade multiple pieces of application software, after determining the installation packages corresponding to the application software, each installation package is compressed, so as to reduce traffic consumption when downloading batch upgrade files.
Further, the location parameter of the compression package may specifically be a storage path of the compression package stored in the batch upgrade file.
S203: decompressing the compressed packet to obtain upgrading strategy information and a plurality of application files contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
in the embodiment of the present invention, after obtaining the compressed packets included in the batch of upgrade files, the compressed packets are decompressed to obtain upgrade policy information and a plurality of application files included in the compressed packets, where one application file correspondingly stores an installation package corresponding to application software to be upgraded. And in order to ensure the accuracy of the installation package in each application file, verifying each application file according to the upgrade verification information and the upgrade strategy information in the file header information.
S204: and when the verification of each application file passes, acquiring the installation package contained in each application file.
In the embodiment of the present invention, before downloading a batch of upgrade files, each application file in the compressed package may also have a possibility of being tampered or replaced, and in order to ensure that the application file in the compressed package is an application file of the application software to be upgraded, and also to ensure that the installation package in the application file is correct, each application file needs to be verified. When the application files pass the verification, it can be determined that the application files are not tampered or replaced, the installation package contained in each application file is obtained, and the process of installing the installation package is started.
In the application software upgrading method provided by the embodiment of the invention, after the batch upgrading files are downloaded and obtained, the batch upgrading files need to be decrypted because the batch upgrading files are sent in an encrypted manner. According to the file header information in the batch upgrading file, acquiring a compressed package position parameter, key information and upgrading file verification information in the file header information, decrypting the batch upgrading file according to the key information to obtain a decrypted batch upgrading file, and acquiring a compressed package in the decrypted batch upgrading file according to the compressed package position parameter. And after the verification of each application file is passed, obtaining an installation package contained in each application file.
The process of decompressing the compressed packet may be decompressing through a preset decompressing tool.
By applying the method provided by the embodiment of the invention, after decryption and decompression, the application files and the upgrade strategy information in the batch of upgrade files are obtained, and each installation package is obtained after verification of each application file, so that each installation package is not tampered and replaced before each installation package is installed.
In the method provided in the embodiment of the present invention, based on the content in step S204, after obtaining each application file in the compressed package, the update file verification information and the update policy information need to be applied to verify each application file, and a specific verification process may include:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
In the application software upgrading method provided by the embodiment of the invention, the upgrade file verification information includes the file name of each application file, the file MD5 value and the upgrading strategy of the installation package corresponding to each application file. Similarly, the upgrade policy information also includes an upgrade policy for each installation package, and each upgrade policy includes an MD5 value. In the process of verifying each application file, the file name, the file MD5 value and the upgrading strategy of the application file contained in the upgrading file verification information are obtained, and the target upgrading strategy matched with the file name and the upgrading strategy of the application file is searched in the upgrading strategy information. Each upgrading strategy in the upgrading strategy information corresponds to an installation package of the application software, so that the upgrading strategy comprises the file name of the application file where the corresponding installation package is located. And after the target upgrading strategy matched with the application file is found, acquiring a target MD5 value contained in the target upgrading strategy, checking the target MD5 value and the file MD5 value, and determining whether the file MD5 value of the application file is consistent with the target MD5 value in the upgrading strategy information. If the application files are consistent, the verification of the application files is passed; and if the application files are not consistent, the verification of the application files is not passed. And when each application file in the batch upgrading files passes the verification, acquiring an installation package contained in each application file.
It is understood that the upgrade file verification information includes a file name of each application file, a file MD5 value, an upgrade policy, and an installation package. The upgrade policy information includes an upgrade policy corresponding to each application software, each upgrade policy corresponds to a file name of an application file, and includes an MD5 value for verifying the application file.
By applying the method provided by the embodiment of the invention, the verification of each application file is realized through the file name of the application file, the MD5 value of the file and the upgrading strategy, and the existence of the tampered or replaced application file is prevented.
In the method provided in the embodiment of the present invention, when a plurality of application software needs to be upgraded, an installation package corresponding to each application software needs to be obtained, and an installation process is performed on each installation package, before the installation package is installed, an application version before upgrading corresponding to each installation package needs to be backed up, and the backup process is shown in fig. 3, and may specifically include:
s301: obtaining an upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information;
in the embodiment of the present invention, the upgrade policy information includes the upgrade policy of each application software to be upgraded, where the upgrade policy may include single application software upgrade, batch linkage upgrade of multiple application software, batch upgrade of multiple application software, and the like. After obtaining the upgrade strategy information and each installation package corresponding to the batch upgrade tasks, obtaining each upgrade strategy contained in the upgrade strategy information. Wherein, each upgrading strategy is in one-to-one correspondence with each application software to be upgraded.
It should be noted that, in each upgrade policy, only one application software upgrade representation needs to be upgraded, and the batch linkage upgrade of the multiple application software and the batch upgrade of the multiple application software represent that at least two application software need to be upgraded. The batch linkage upgrading of the plurality of application software can be specifically realized in such a way that at least two pieces of application software have linkage relation, each linkage application software is required to be successfully upgraded when upgrading, and if one piece of application software in each linkage application software fails to be upgraded, the use of other linkage application software can be influenced; the batch upgrading of the plurality of applications may specifically be that no linkage relationship exists between the application software to be upgraded, and even if any application software fails to be upgraded, the use of other successfully upgraded application software is not affected.
S302: judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded;
in the embodiment of the present invention, after determining the upgrade policy of each application software to be upgraded, it may be determined whether each installation package that needs to be installed has a certain association relationship with other installation packages.
It should be noted that each associated installation package represents that the application software corresponding to each installation package has a linkage relationship, that is, the normal operation of one application software needs to be performed in linkage with another application software, so that the normal operation between the linked application software can be realized.
S303: and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
In the embodiment of the invention, if the associated installation packages exist among the installation packages, the linkage application software exists in the application software to be upgraded. In order to prevent the linked application software from failing to be upgraded, the pre-upgrade application versions of the application software corresponding to each installation package need to be backed up. For example, if the application version of the application software to be upgraded is V2.0 before upgrading and becomes V3.0 after upgrading, the application version of V2.0 is backed up.
In the method provided by the embodiment of the invention, the upgrading strategy of each application software to be upgraded is determined through the upgrading strategy information, and whether linked application software exists in each application software to be upgraded is further determined. When the linked application software is determined to exist, the fact that the related installation packages exist in the installation packages to be installed can be determined, and the application version before upgrading corresponding to each installation package is backed up.
Optionally, in the embodiment of the present invention, after determining that the associated installation packages exist, only the pre-upgrade application version corresponding to the application software corresponding to each associated installation package may be backed up, and when the installation of the installation package fails, only the application software having the linkage relationship is restored to the pre-upgrade application version.
By applying the method provided by the embodiment of the invention, before each installation package is installed, the application version before upgrading of the application software corresponding to each installation package is backed up, so that the application version before upgrading can be recovered after each application software with linkage relation fails to be upgraded, and the consistency of the versions among the linkage application software is maintained.
Specifically, in the method provided in the embodiment of the present invention, when all installation packages are successfully installed in the process of installing each installation package, the method may further include:
and if the installation packages with failed installation do not exist, deleting the backed-up application version before upgrading corresponding to each installation package.
In the method provided by the embodiment of the invention, when each installation package is successfully installed, each backed-up application version before upgrading is deleted, and when the application software corresponding to each installation package is upgraded next time, the current application version corresponding to each installation package is backed up. Therefore, the application version before upgrading is deleted, the surplus of the content amount of the client can be ensured, and unnecessary content can be removed.
In the method provided in the embodiment of the present invention, based on the content in step S105, after determining that the target installation package has the associated installation package, the application version corresponding to the target installation package and the application version corresponding to the associated installation package are restored to the application version before the update corresponding to the application version, which may specifically include:
judging whether the installation package associated with the target installation package is successfully installed;
and if the installation package associated with the target installation package is successfully installed, the application software corresponding to the installation package associated with the target installation package is uninstalled, and the application version corresponding to the target installation package and the application version corresponding to the associated installation package are restored to the corresponding application version before upgrading.
In the application software upgrading method provided by the embodiment of the invention, in the process of installing each installation package according to the installation sequence, the installation result of each installation package needs to be recorded, and if the installation result of the target installation package is installation failure and the target installation package has the associated installation package, whether the associated installation package is installed successfully needs to be judged, that is, whether the application software corresponding to the associated installation package is upgraded successfully is judged. And if the installation package associated with the target installation package is successfully installed, the corresponding application software is proved to be successfully upgraded. In order to ensure consistency of versions among linked application software, it is necessary to uninstall the application software corresponding to the installation package associated with the target installation package that has been successfully installed, and restore the application version corresponding to the target installation package and the application version corresponding to the installation package associated with the target installation package to the application version before upgrade.
By applying the method provided by the embodiment of the invention, even if the installation package associated with the target installation package is successfully installed, the corresponding application software cannot be normally used, so that the application software is unloaded and restored into the application version before upgrading, and the version consistency of the application software with the linkage relation can be ensured.
The specific implementation procedures and derivatives thereof of the above embodiments are within the scope of the present invention.
Corresponding to the method described in fig. 1, an embodiment of the present invention further provides an application software upgrading apparatus, which is used for implementing the method in fig. 1 specifically, the application software upgrading apparatus provided in the embodiment of the present invention may be applied to a computer terminal or various mobile devices, and a schematic structural diagram of the application software upgrading apparatus is shown in fig. 4, and specifically includes:
an obtaining unit 401, configured to obtain, when a batch upgrade task corresponding to each application software to be upgraded and sent by a server is received, upgrade policy information and a plurality of installation packages corresponding to the batch upgrade task, where each installation package and each application software to be upgraded correspond to each other one to one;
an installation unit 402, configured to determine an installation order of each installation package, invoke a preset installation management service to sequentially install each installation package according to the installation order, and record an installation result of each installation package;
a first judging unit 403, configured to judge whether an installation package with an installation failure exists according to an installation result of each installation package;
a second determining unit 404, configured to determine, if there is an installation package with a failed installation, that the installation package with the failed installation is a target installation package, and determine, in each installation package except for the target installation package, whether there is an installation package associated with the target installation package;
a restoring unit 405, configured to, if an installation package associated with the target installation package exists, obtain a pre-backed up target installation package and an application version before upgrade corresponding to the associated installation package, and restore the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrade corresponding to the application version before upgrade.
In the application software upgrading device provided by the embodiment of the invention, the obtaining unit obtains the installation packages of the application software to be upgraded, and the installation unit installs the installation packages according to the installation sequence. After each installation package is installed, the first judgment unit judges whether an installation package with installation failure exists. If the target installation package exists, the installation package with the installation failure is determined to be the target installation package, and the second judging unit judges whether the installation package related to the target installation package exists or not. If the target installation package exists, the pre-backup target installation package and the application version before the upgrade corresponding to the related packaging package are obtained, and the application version corresponding to the target installation package and the application version of the related installation package are restored to the corresponding application version before the upgrade through the restoring unit.
By applying the device provided by the invention, when any installation package fails to be installed and the installation package has the associated installation package, the installation package and the application version corresponding to the associated installation package can be restored to the application version before upgrading, and the consistency of the versions of the application software with the linkage relation is ensured.
In the apparatus provided in the embodiment of the present invention, the obtaining unit 401 includes:
the downloading subunit is used for downloading batch upgrading files corresponding to the batch upgrading tasks and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, key information and upgrading file verification information;
the decryption subunit is used for decrypting the batch upgrading files by applying the key information and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
the verification subunit is used for decompressing the compressed packet, acquiring the upgrading strategy information and a plurality of application files contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
and the obtaining subunit is used for obtaining the installation package contained in each application file when the application files pass the verification.
In the apparatus provided in the embodiment of the present invention, the verifying subunit is configured to:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
The device provided by the embodiment of the invention further comprises:
the backup unit is used for acquiring the upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information; judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded; and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
The device provided by the embodiment of the invention further comprises:
and the deleting unit is used for deleting the backed-up application version before upgrade corresponding to each installation package if the installation package with failed installation does not exist.
In the apparatus provided in the embodiment of the present invention, the recovery unit 405 includes:
the judging subunit is used for judging whether the installation package associated with the target installation package is successfully installed;
and the recovery subunit is configured to, if the installation package associated with the target installation package is successfully installed, uninstall the application software corresponding to the installation package associated with the target installation package, and recover the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrade corresponding to the application version.
The specific working processes of each unit and sub-unit in the application software upgrading device disclosed in the above embodiment of the present invention can refer to the corresponding contents in the application software upgrading method disclosed in the above embodiment of the present invention, and are not described herein again.
The embodiment of the invention also provides a storage medium, which comprises a stored instruction, wherein when the instruction runs, the device where the storage medium is located is controlled to execute the application software upgrading method.
An electronic device is provided in an embodiment of the present invention, and the structural diagram of the electronic device is shown in fig. 5, which specifically includes a memory 501 and one or more instructions 502, where the one or more instructions 502 are stored in the memory 501, and are configured to be executed by one or more processors 503 to perform the following operations according to the one or more instructions 502:
when a batch upgrading task which is sent by a server and corresponds to each application software to be upgraded is received, obtaining upgrading strategy information and a plurality of installation packages which correspond to the batch upgrading task, wherein each installation package and each application software to be upgraded are in a one-to-one correspondence relationship;
determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
judging whether an installation package with installation failure exists according to the installation result of each installation package;
if the installation package with the installation failure exists, determining that the installation package with the installation failure is a target installation package, and judging whether an installation package associated with the target installation package exists in all installation packages except the target installation package;
if the installation package associated with the target installation package exists, acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrading corresponding to the target installation package.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the 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.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.
To clearly illustrate this interchangeability of hardware and software, various illustrative components and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An application software upgrading method, comprising:
when a batch upgrading task which is sent by a server and corresponds to each application software to be upgraded is received, obtaining upgrading strategy information and a plurality of installation packages which correspond to the batch upgrading task, wherein each installation package and each application software to be upgraded are in a one-to-one correspondence relationship;
determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
judging whether an installation package with installation failure exists according to the installation result of each installation package;
if the installation package with the installation failure exists, determining that the installation package with the installation failure is a target installation package, and judging whether an installation package associated with the target installation package exists in all installation packages except the target installation package;
if the installation package associated with the target installation package exists, acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the application version before upgrading corresponding to the target installation package.
2. The method of claim 1, wherein the obtaining of the upgrade policy information and the plurality of installation packages corresponding to the batch upgrade tasks comprises:
downloading batch upgrading files corresponding to the batch upgrading tasks, and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, secret key information and upgrading file verification information;
decrypting the batch upgrading files by applying the key information, and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
decompressing the compressed packet, obtaining upgrading strategy information and a plurality of application files corresponding to the batch upgrading tasks contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
and when the verification of each application file passes, acquiring the installation package contained in each application file.
3. The method of claim 2, wherein the applying the upgrade file verification information and the upgrade policy information to verify each of the application files comprises:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
4. The method of claim 1, wherein before installing each installation package in sequence, further comprising:
obtaining an upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information;
judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded;
and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
5. The method of claim 4, further comprising:
and if the installation packages with failed installation do not exist, deleting the backed-up application version before upgrading corresponding to each installation package.
6. The method according to claim 1, wherein the restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to their corresponding pre-upgrade application versions comprises:
judging whether the installation package associated with the target installation package is successfully installed;
and if the installation package associated with the target installation package is successfully installed, the application software corresponding to the installation package associated with the target installation package is uninstalled, and the application version corresponding to the target installation package and the application version corresponding to the associated installation package are restored to the corresponding application version before upgrading.
7. An application software upgrading apparatus, comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring upgrading strategy information and a plurality of installation packages corresponding to batch upgrading tasks when the batch upgrading tasks corresponding to application software to be upgraded and sent by a server are received, and each installation package and each application software to be upgraded are in one-to-one correspondence;
the installation unit is used for determining the installation sequence of each installation package, calling a preset installation management service to sequentially install each installation package according to the installation sequence, and recording the installation result of each installation package;
the first judgment unit is used for judging whether the installation packages with installation failure exist according to the installation results of the installation packages;
a second determination unit, configured to determine, if an installation package that fails to be installed exists, that the installation package that fails to be installed is a target installation package, and determine, in each installation package other than the target installation package, whether an installation package associated with the target installation package exists;
and the restoring unit is used for acquiring the target installation package which is backed up in advance and the application version before upgrading corresponding to the associated installation package if the installation package associated with the target installation package exists, and restoring the application version corresponding to the target installation package and the application version corresponding to the associated installation package to the corresponding application version before upgrading.
8. The apparatus of claim 7, wherein the obtaining unit comprises:
the downloading subunit is used for downloading batch upgrading files corresponding to the batch upgrading tasks and acquiring file header information of the batch upgrading files, wherein the file header information comprises compression package position parameters, key information and upgrading file verification information;
the decryption subunit is used for decrypting the batch upgrading files by applying the key information and acquiring the compression packages contained in the decrypted batch upgrading files according to the position parameters of the compression packages;
the verification subunit is used for decompressing the compressed packet, acquiring the upgrading strategy information and a plurality of application files contained in the compressed packet, and verifying each application file by applying the upgrading file verification information and the upgrading strategy information;
and the obtaining subunit is used for obtaining the installation package contained in each application file when the application files pass the verification.
9. The apparatus of claim 8, wherein the syndrome unit is configured to:
acquiring the file name, the file message digest algorithm MD5 value and the upgrading strategy of each application file contained in the upgrading file verification information;
for each application file, searching a target upgrading strategy matched with the file name and the upgrading strategy of the application file in the upgrading strategy information;
acquiring a target MD5 value contained in the target upgrading strategy, and checking whether a file MD5 value of the application file is consistent with the target MD5 value;
if the file MD5 value of the application file is consistent with the target MD5 value, the application file passes the verification;
if the file MD5 value of the application file is inconsistent with the target MD5 value, the application file is not verified.
10. The apparatus of claim 7, further comprising:
the backup unit is used for acquiring the upgrading strategy of the application software to be upgraded corresponding to each installation package contained in the upgrading strategy information; judging whether a relevant installation package exists according to the upgrading strategy of each application software to be upgraded; and if the associated installation packages exist, backing up the application version before upgrading corresponding to each installation package.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911369464.9A CN111158719B (en) | 2019-12-26 | 2019-12-26 | Application software upgrading method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911369464.9A CN111158719B (en) | 2019-12-26 | 2019-12-26 | Application software upgrading method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111158719A true CN111158719A (en) | 2020-05-15 |
| CN111158719B CN111158719B (en) | 2023-06-16 |
Family
ID=70556879
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911369464.9A Active CN111158719B (en) | 2019-12-26 | 2019-12-26 | Application software upgrading method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111158719B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111596943A (en) * | 2020-05-25 | 2020-08-28 | 湖北亿咖通科技有限公司 | Upgrading method for multiple electronic control units of vehicle and electronic equipment |
| CN112114853A (en) * | 2020-09-28 | 2020-12-22 | 杭州安恒信息技术股份有限公司 | OTA-based software upgrading method, system and related device |
| CN112925549A (en) * | 2021-03-09 | 2021-06-08 | 浙江合众新能源汽车有限公司 | System application upgrading system based on android frame |
| WO2022247496A1 (en) * | 2021-05-28 | 2022-12-01 | 中兴通讯股份有限公司 | Software upgrading method and system, and terminal device and computer-readable storage medium |
| CN116775365A (en) * | 2023-08-17 | 2023-09-19 | 紫光同芯微电子有限公司 | Lossless upgrading method for loadable execution file, security chip and storage medium |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050210124A1 (en) * | 2004-03-19 | 2005-09-22 | International Business Machines Corporation | J2EE application versioning strategy |
| CN1834913A (en) * | 2005-03-18 | 2006-09-20 | 联想(北京)有限公司 | Method of managing software installation and unloading |
| CN101038549A (en) * | 2007-03-28 | 2007-09-19 | 北京启明星辰信息技术有限公司 | A software updating method capable of crossing system |
| CN102023881A (en) * | 2010-12-14 | 2011-04-20 | 福建星网锐捷网络有限公司 | Method and device for upgrading software as well as embedded device |
| CN102855419A (en) * | 2012-07-20 | 2013-01-02 | 北京亿赛通科技发展有限责任公司 | Copyright protection method for data files of intelligent terminals |
| CN103647816A (en) * | 2013-12-03 | 2014-03-19 | 北京奇虎科技有限公司 | Method and device for upgrading application software |
| US20140101644A1 (en) * | 2012-09-28 | 2014-04-10 | Oracle International Corporation | Using a data dictionary to determine an upgrade edition of a relational database table |
| US20140304697A1 (en) * | 2011-12-01 | 2014-10-09 | Tencent Technology (Shenzhen) Company Limited | Method and system for upgrading software |
| US20150277897A1 (en) * | 2013-09-13 | 2015-10-01 | Huizhou Tcl Mobile Communication Co., Ltd. | Software upgrade method and system for mobile terminal |
| CN105204909A (en) * | 2015-10-12 | 2015-12-30 | Tcl集团股份有限公司 | Method and system for upgrading strongly correlated apks based on mobile terminal |
| CN105653262A (en) * | 2015-12-21 | 2016-06-08 | Tcl集团股份有限公司 | Application program upgrade method, device and system |
| CN106339248A (en) * | 2016-10-09 | 2017-01-18 | 大道网络（上海）股份有限公司 | Remote software upgrading method and remote software upgrading system |
| CN106502747A (en) * | 2016-11-02 | 2017-03-15 | 武汉斗鱼网络科技有限公司 | A kind of method of application upgrade and mobile terminal |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN107562434A (en) * | 2016-06-30 | 2018-01-09 | 中兴通讯股份有限公司 | Preparation method, upgrade method, device and the equipment of upgrade file |
| CN107577478A (en) * | 2017-09-08 | 2018-01-12 | 湖南快乐阳光互动娱乐传媒有限公司 | A kind of cell phone software loading method and system |
| CN107943502A (en) * | 2017-12-01 | 2018-04-20 | 天津麒麟信息技术有限公司 | A kind of upgrade method based on the detection of fine granularity system mode under linux system |
| CN108509211A (en) * | 2018-02-07 | 2018-09-07 | 深圳壹账通智能科技有限公司 | Application program updating method, apparatus, mobile terminal and storage medium |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110209405A (en) * | 2019-06-04 | 2019-09-06 | 杭州安恒信息技术股份有限公司 | The automatic updating method and device of distributed system |
-
2019
- 2019-12-26 CN CN201911369464.9A patent/CN111158719B/en active Active
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050210124A1 (en) * | 2004-03-19 | 2005-09-22 | International Business Machines Corporation | J2EE application versioning strategy |
| CN1834913A (en) * | 2005-03-18 | 2006-09-20 | 联想(北京)有限公司 | Method of managing software installation and unloading |
| CN101038549A (en) * | 2007-03-28 | 2007-09-19 | 北京启明星辰信息技术有限公司 | A software updating method capable of crossing system |
| CN102023881A (en) * | 2010-12-14 | 2011-04-20 | 福建星网锐捷网络有限公司 | Method and device for upgrading software as well as embedded device |
| US20140304697A1 (en) * | 2011-12-01 | 2014-10-09 | Tencent Technology (Shenzhen) Company Limited | Method and system for upgrading software |
| CN102855419A (en) * | 2012-07-20 | 2013-01-02 | 北京亿赛通科技发展有限责任公司 | Copyright protection method for data files of intelligent terminals |
| US20140101644A1 (en) * | 2012-09-28 | 2014-04-10 | Oracle International Corporation | Using a data dictionary to determine an upgrade edition of a relational database table |
| US20150277897A1 (en) * | 2013-09-13 | 2015-10-01 | Huizhou Tcl Mobile Communication Co., Ltd. | Software upgrade method and system for mobile terminal |
| CN103647816A (en) * | 2013-12-03 | 2014-03-19 | 北京奇虎科技有限公司 | Method and device for upgrading application software |
| CN105204909A (en) * | 2015-10-12 | 2015-12-30 | Tcl集团股份有限公司 | Method and system for upgrading strongly correlated apks based on mobile terminal |
| CN105653262A (en) * | 2015-12-21 | 2016-06-08 | Tcl集团股份有限公司 | Application program upgrade method, device and system |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN107562434A (en) * | 2016-06-30 | 2018-01-09 | 中兴通讯股份有限公司 | Preparation method, upgrade method, device and the equipment of upgrade file |
| CN106339248A (en) * | 2016-10-09 | 2017-01-18 | 大道网络（上海）股份有限公司 | Remote software upgrading method and remote software upgrading system |
| CN106502747A (en) * | 2016-11-02 | 2017-03-15 | 武汉斗鱼网络科技有限公司 | A kind of method of application upgrade and mobile terminal |
| CN107577478A (en) * | 2017-09-08 | 2018-01-12 | 湖南快乐阳光互动娱乐传媒有限公司 | A kind of cell phone software loading method and system |
| CN107943502A (en) * | 2017-12-01 | 2018-04-20 | 天津麒麟信息技术有限公司 | A kind of upgrade method based on the detection of fine granularity system mode under linux system |
| CN108509211A (en) * | 2018-02-07 | 2018-09-07 | 深圳壹账通智能科技有限公司 | Application program updating method, apparatus, mobile terminal and storage medium |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110209405A (en) * | 2019-06-04 | 2019-09-06 | 杭州安恒信息技术股份有限公司 | The automatic updating method and device of distributed system |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111596943A (en) * | 2020-05-25 | 2020-08-28 | 湖北亿咖通科技有限公司 | Upgrading method for multiple electronic control units of vehicle and electronic equipment |
| CN112114853A (en) * | 2020-09-28 | 2020-12-22 | 杭州安恒信息技术股份有限公司 | OTA-based software upgrading method, system and related device |
| CN112925549A (en) * | 2021-03-09 | 2021-06-08 | 浙江合众新能源汽车有限公司 | System application upgrading system based on android frame |
| WO2022247496A1 (en) * | 2021-05-28 | 2022-12-01 | 中兴通讯股份有限公司 | Software upgrading method and system, and terminal device and computer-readable storage medium |
| CN116775365A (en) * | 2023-08-17 | 2023-09-19 | 紫光同芯微电子有限公司 | Lossless upgrading method for loadable execution file, security chip and storage medium |
| CN116775365B (en) * | 2023-08-17 | 2023-12-22 | 紫光同芯微电子有限公司 | Lossless upgrading method for loadable execution file, security chip and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111158719B (en) | 2023-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111158719B (en) | Application software upgrading method and device | |
| US7350205B2 (en) | Upgrading electronic files of a mobile device upgrade client | |
| TWI359597B (en) | Method,computer system ,and computer-readable medi | |
| US7480907B1 (en) | Mobile services network for update of firmware/software in mobile handsets | |
| US6256668B1 (en) | Method for identifying and obtaining computer software from a network computer using a tag | |
| CN109491698B (en) | System updating method and device based on hot patch | |
| CN110058867B (en) | Application program mirror image packaging and installing method, computer device and storage medium | |
| WO2004086168A2 (en) | Non-invasive automatic offsite patch fingerprinting and updating system and method | |
| CN106201607A (en) | The upgrade method of a kind of software version and equipment | |
| WO2011143852A1 (en) | Managing method, device and terminal for application program | |
| CN107623735B (en) | Accurate updating and upgrading system and method based on openssl in credit investigation machine system | |
| CN107239299B (en) | Plug-in upgrading method and device | |
| CN110069266B (en) | Application upgrading method and device, computer equipment and storage medium | |
| CN112860645A (en) | Processing method and device for offline compressed file, computer equipment and medium | |
| US20080222043A1 (en) | System and method for trans-vendor license registration and recovery | |
| CN110362333A (en) | A kind of quick solution, device and electronic equipment that client upgrading hinders | |
| CN106155723B (en) | Method and device for upgrading service application program, terminal and computer storage medium | |
| CN112328284A (en) | Application program upgrading method, system, equipment and storage medium | |
| CN109933351B (en) | Method and device for repairing and upgrading Linux system | |
| CN111046389A (en) | Method for securely updating firmware components and portable computer station for implementation | |
| CN112711430B (en) | ADB-based non-network equipment upgrading method, system and readable storage medium | |
| CN114143197B (en) | OTA (over the air) upgrading method, device and equipment for Internet of things equipment and readable storage medium | |
| US20050015697A1 (en) | Platform independent file manipulation | |
| CN114356855A (en) | File management method, file management device, electronic device and readable storage medium | |
| CN112416407A (en) | Software upgrading method, device, equipment and computer readable storage medium |
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 | ||
| CB03 | Change of inventor or designer information |
Inventor after: Chen Bifeng Inventor after: Liu Guangbin Inventor before: Chen Bifeng Inventor before: Liu Guangbin |
|
| CB03 | Change of inventor or designer information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |