CN113961224B - Android-terminal-based application program updating method and system - Google Patents
Android-terminal-based application program updating method and system Download PDFInfo
- Publication number
- CN113961224B CN113961224B CN202111584614.5A CN202111584614A CN113961224B CN 113961224 B CN113961224 B CN 113961224B CN 202111584614 A CN202111584614 A CN 202111584614A CN 113961224 B CN113961224 B CN 113961224B
- Authority
- CN
- China
- Prior art keywords
- updating
- patch
- scheme
- application program
- update
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to an application program updating method and system based on an Android terminal. The method comprises the following steps: receiving patch information fed back by the server; according to the specific field information in the patch information, one of a major updating scheme and a minor updating scheme is automatically selected for updating the application program; wherein, the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program; secondary update scheme: the application is updated using only the patch, and if updating the application using the patch fails, the update is retried or stopped. According to the embodiment of the invention, a complete and flexible Android application program updating scheme is integrated by designing the updating scheme for different scenes, and compared with the prior art, the Android application program updating scheme is more flexible, wider in coverage rate and better in timeliness.
Description
Technical Field
The invention relates to the field of application software, in particular to an application program updating method and system based on an Android terminal.
Background
At present, due to rapid development of the internet era, the requirements of business on rapid innovation and iteration of APP products are higher and higher, and more severe requirements on flexibility, coverage and timeliness of online problem processing are also provided. At present, the mainstream updating mode is mainly that an application upgrade prompt in the APP guides an Android application package (Apk) to upgrade, and in this mode, a user needs to download the whole installation package and then goes through a normal APP upgrade process. There are also further ways in the market: incremental updates implemented based on some hot update framework to implement hot repair capabilities of the partial modules.
The problem is repaired in a mode of upgrading the whole package in the application, a certain flow is consumed firstly to download the installation package to the mobile phone, and then installation and upgrading are carried out locally. If the upgrade package is large, on one hand, a large amount of network traffic of the user is consumed, and on the other hand, a large amount of waiting time of the user is occupied in the downloading and installing process, so that the user experience is seriously influenced. Although the incremental updating mode realized based on some hot updating frames can save a certain flow and optimize user experience, various customized Android systems exist in the market due to a plurality of Android equipment manufacturers, system fragmentation is serious, the mainstream hot updating frames have a certain compatibility problem, and the repair success rate of 100% cannot be realized. In severe cases even application flash back can result, which can cause immeasurable negative impact when severe on-line problems are encountered. In addition, the repair scenes of the online problems are various, and a single repair strategy cannot provide a reliable and effective support for the product.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a more flexible and more comprehensive application program updating method and system based on an Android terminal.
The invention provides an application program updating method based on an Android terminal, which comprises the following steps:
receiving patch information fed back by the server;
according to the specific field information in the patch information, one of a major updating scheme and a minor updating scheme is automatically selected for updating the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
secondary update scheme: the application is updated using only the patch, and if updating the application using the patch fails, the update is retried or stopped.
As a further improvement of the above embodiment, the major update scheme includes a major update sub-scheme one and a major update sub-scheme two, and when the major update scheme is selected, one of the major update sub-scheme one and the major update sub-scheme two is automatically selected for application update according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating the application program by the patch, if the application program is unsuccessfully updated by the patch, prompting a user to select a full quantum packet updating flow, and downloading the full quantum packet to update the application program when the user selects the full quantum packet updating flow.
As a further improvement of the above embodiment, in the major update scheme, when the downloading of the patch fails or the checking of the patch fails more than a predetermined number of times, or both the downloading of the patch and the checking of the patch succeed, but the updating of the application program using the patch is unsuccessful, it is determined that the updating of the application program using the patch fails.
As a further improvement of the above embodiment, the secondary update scheme includes a primary update sub-scheme one and a secondary update sub-scheme two, and when the secondary update scheme is selected, one of the primary update sub-scheme one and the secondary update sub-scheme two is automatically selected for application update according to specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
As a further improvement of the above embodiment, the patch information includes a new full quantum packet address field, and when the new full quantum packet address field is not empty, a major update scheme is automatically selected; when the new full packet address field is empty, the secondary update scheme is automatically selected.
As a further improvement of the foregoing embodiment, the patch information includes a forced update field and a new full packet address field, when the forced update field is yes and the new full packet address field is not empty, a first major update sub-scheme is automatically selected, when the forced update field is no and the new full packet address field is not empty, a second major update sub-scheme is automatically selected, when the forced update field is yes and the new full packet address field is empty, a first minor update sub-scheme is automatically selected, and when the forced update field is no and the new full packet address field is empty, a second minor update sub-scheme is automatically selected.
As a further improvement of the foregoing embodiment, the patch information includes a patch address field and a new full package address field, and in the major update scheme, the patch is downloaded according to the patch address field, the full package is downloaded according to the new full package address field, and in the minor update scheme, the patch is downloaded according to the patch address field.
In another aspect, an embodiment of the present invention provides an application updating system based on an Android terminal, including:
a communication module: the patch information is used for receiving the server feedback;
an update module: the system comprises a patch information module, a primary update module, a secondary update module and a server, wherein the patch information module is used for providing patch information for the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
secondary update scheme: the application is updated using only the patch, and if updating the application using the patch fails, the update is retried or stopped.
As a further improvement of the above embodiment, the major update scheme includes a major update sub-scheme one and a major update sub-scheme two, and when the major update scheme is selected, one of the major update sub-scheme one and the major update sub-scheme two is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating an application program by a patch, if the application program is unsuccessfully updated by the patch, prompting a user to select a full quantum packet updating flow, and downloading the full quantum packet to update the application program when the user selects the full quantum packet updating flow;
the secondary updating scheme comprises a primary updating sub-scheme I and a secondary updating sub-scheme II, and when the secondary updating scheme is selected, one of the primary updating sub-scheme I and the secondary updating sub-scheme II is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
As a further improvement of the foregoing embodiment, the patch information includes a forced update field and a new full packet address field, when the forced update field is yes and the new full packet address field is not empty, a first major update sub-scheme is automatically selected, when the forced update field is no and the new full packet address field is not empty, a second major update sub-scheme is automatically selected, when the forced update field is yes and the new full packet address field is empty, a first minor update sub-scheme is automatically selected, and when the forced update field is no and the new full packet address field is empty, a second minor update sub-scheme is automatically selected.
According to the embodiment of the invention, a complete and flexible Android application program updating scheme is integrated by designing the updating scheme for different scenes, and compared with the prior art, the Android application program updating scheme is more flexible, wider in coverage rate and better in timeliness.
Drawings
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings.
Fig. 1 is a flowchart of an application updating method based on an Android terminal according to an embodiment of the present invention.
FIG. 2 is a flow chart of a big update sub-scheme one.
FIG. 3 is a flowchart of the secondary update sub-scheme two.
FIG. 4 is a schematic diagram of a configuration of uploading patches on a server.
Detailed Description
The following detailed description of the present invention is provided in connection with the accompanying drawings and specific embodiments for the purpose of better understanding and enabling those skilled in the art to practice the present invention, which are not intended to limit the present invention.
Referring to fig. 1 to 3, an embodiment of the present invention provides an application program updating method based on an Android terminal, including the following steps:
receiving patch information fed back by the server;
according to the specific field information in the patch information, one of a major updating scheme and a minor updating scheme is automatically selected for updating the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
secondary update scheme: the application is updated using only the patch, and if updating the application using the patch fails, the update is retried or stopped.
In both major and minor update scenarios, patches (patch packages) are downloaded first over the network. The full package is a complete firmware package required by application program (APP) upgrading, and is the most complete and pure upgrading mode.
In a preferred embodiment, the major update scheme comprises a major update sub-scheme I and a major update sub-scheme II, when the major update scheme is selected, one of the major update sub-scheme I and the major update sub-scheme II is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating the application program by the patch, if the application program is unsuccessfully updated by the patch, prompting a user to select a full quantum packet updating flow, and downloading the full quantum packet to update the application program when the user selects the full quantum packet updating flow. The user may also choose to ignore the full package update flow. If the patch repair is omitted and the patch repair is ended in an invalid state, the APP continues to execute a normal starting process.
In the major update sub-scheme one, the patch is a mandatory popup patch, and in the major update sub-scheme two, the patch is an optional bottom-pocketed popup patch. In this embodiment, the full volume packet is a degraded repair to the application.
Referring to fig. 2, in a preferred embodiment, in a major update scheme, when a patch fails to be downloaded or a check patch fails more than a predetermined number of times (2 times in this embodiment), or when both a patch and a check patch succeed but an application is not successfully updated using the patch, it is determined that the application fails to be updated using the patch. At this point, the full package starts to be downloaded for application update.
In a preferred embodiment, the secondary update scheme comprises a first secondary update sub-scheme and a second secondary update sub-scheme, and when the secondary update scheme is selected, one of the first secondary update sub-scheme and the second secondary update sub-scheme is automatically selected for application update according to specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
In the first secondary update sub-scheme, the patch is a normal popup patch, and in the second secondary update sub-scheme, the patch is a silent patch. The silent patch means that a user does not sense when the patch is operated and installed, and the popup patch prompts the user when the patch is operated and installed.
In a preferred embodiment, the patch information includes a new full packet address field (newappl), where the new full packet address field is used to record a network address, i.e. a URL (Uniform Resource Locator), of the new full packet, and the new full packet can be downloaded by the terminal system by accessing the network address. When the address field of the new full packet is not null (namely, the address of the new full packet is recorded), automatically selecting a major updating scheme; when the new full packet address field is empty (i.e. the address of the new full packet is not recorded), the secondary update scheme is automatically selected.
In a preferred embodiment, the patch information includes a forced update field (newappforcedpupdate) and a new full packet address field (newappurrl). The forced update field is for the control patch type and may be noted as yes (1) or no (0). And automatically selecting a first major update sub-scheme when the forced update field is yes and the new full packet address field is not empty. And when the forced update field is negative and the new full packet address field is not empty, automatically selecting a second major update sub-scheme. When the forced update field is yes and the new full packet address field is empty, secondary update sub-scheme one is automatically selected. And when the forced update field is negative and the new full packet address field is empty, automatically selecting a secondary update sub-scheme two.
In a preferred embodiment, the patch information includes a patch address field (patchUrl) and a new full quantum packet address field. The patch address field is used to record the network address of the patch. In the major updating scheme, the terminal system downloads the patch according to the patch address field, downloads the full package according to the new full package address field, and downloads the patch according to the patch address field in the minor updating scheme. A null patch address field may result in a failed patch download.
In order to better understand the application updating method based on the Android terminal, the application updating method based on the Android terminal is shown below by a specific embodiment.
Referring to fig. 4, the patch configuration is first uploaded on the server.
Description of fields: the patch name and the patch description configure the Title and the content of the popup for the popup type patch; uploading the patch to configure a real patch package and generating a download url; the APP version number is the APP version suitable for the current patch; the patch state is used for controlling the on-off state of the current patch; 4 gray level environment enumerations can be configured in the visible range at present and used for gray level release of the patch, and the patch is not released when the gray level environments of the patch are not matched; the patch version number is the version number of the current patch as the name implies; the system version number (maximum) is used for providing a degradation process when the hot update framework is not compatible with the Android system of the latest version in time, if configuration exists, if the system version of the target client is larger than the configuration version, a patch downloading address is not sent, and a degradation repair process of full package downloading is carried out; the full packet uploading address is a full packet downloading address configured for the degradation processing of the full packet downloading; and if the forced updating is used for controlling the patch type, the forced updating is a popup patch, and a user cannot bypass the popup patch, otherwise, the forced updating is silent updating, and the user does not sense the whole patch flow.
After the patch is newly added and configured as described above, the client (user terminal) requests a patch service interface to provide the server with the current state information such as the patch gray environment setting, the version number, the system version number, etc., and the server controls the distribution of the patch according to the state information and feeds back the patch information (Map containing the patchInfo field) to the client, where the information details are as follows:
"patch_info": {
"PatchName" patch Title ",
patch Desc patch description,
"patchUrl": "************.zip",
"patchStatus": "1",
"patchMd5": "************",
"patchFileSize": 100,
"patchFlag": "P1",
"newAppUrl": "************.html"
"newAppForcedUpdate": 0 "(NO)" 1 "(YES)
}
And if the patch status =1& & patchUrl is not empty, bypassing the state of the patch, wherein the state is used for the condition that the maximum Android system version is configured and the current version is greater than the configured version.
Configuring different forced update fields (newAppledUpdate) and new full packet address fields (newApPurl) according to different severity of on-line problems, and executing the following different update schemes according to the information of the forced update fields and the new full packet address fields:
major update sub-scheme one (mandatory popup patch): when the newAppledUdate =1& & newApUrl is not empty, a forced popup patch is used, a full package must be upgraded when the patch fails, the method is suitable for repairing the on-line problem with the largest influence, the coverage of the full user needs to be ensured, and a degraded repairing process of loading the full package must be carried out when the patch fails. If the patchUrl is empty, then a forced full packet demotion repair procedure is performed. And when the patch Url is not empty, as shown in fig. 2, popping up a patch popup window on the APP starting page, clicking by the user to download the patch package resource file of the patch Url after determination, comparing the patch information with md5 and patchMd5 of the patch package and comparing the file volume with patchFileSize after the downloading is completed, and considering that the verification is successful if the patch information is consistent with the patch package resource file. The downloading is retried when one step of downloading and checking fails in the process until the downloading is not retried after more than two times of failure, and a full-package degradation repair flow is entered. And if the verification is successful, entering a patch repair flow (decompression, synthesis and loading) of the framework, if the application of the patch (namely updating the application program by using the patch) fails, entering a forced full package downgrade repair flow, if the verification is successful, deleting the patch package file and restarting the APP to enable the patch to take effect, and ending the patch repair flow.
Major update sub-scheme two (optional bottom pop-up patch): when the newAppledUdate =0 & & newApUrl is not empty, a popup patch is used, patch failure prompts one-time upgrading of the full pack, the method is suitable for repairing the on-line problem with the secondary influence, and when the patch fails, a user is prompted to select the full pack downgrading repairing process. The scheme is basically the same as the flow of the above-mentioned major updating sub-scheme, except that when entering the full packet degradation repair flow, the full packet is selectable, and the user can choose to execute or ignore the full packet degradation repair flow. If the patch repair is omitted and the patch repair is ended in an invalid state, the APP continues to execute a normal starting process.
Secondary update sub-scheme one (normal pop-up patch): when newAppledUpdate =1& & newApUrl is empty, a popup patch is used, silent retry can be performed when the patch fails, and the method is suitable for on-line problems with smaller influence, and a small number of users can be accepted to be incapable of being effectively repaired. The scheme is basically the same as the previous section of the flow major updating scheme, and the difference lies in the degradation processing when the patch fails, the degradation is performed to silent retry when the patch fails, and the APP continues to execute the normal starting flow.
Secondary update sub-scheme one (silent patch): when newAppledUdate =0 & & newApprUrl is null, a silent patch is used, and the patchUrl is null or the patch failure is not processed, so that the method is suitable for repairing the problems to be optimized, the main flow is not influenced, and the user does not sense. The specific process is as shown in fig. 3, and the silent patch information is obtained and cached in the startup page. After entering a home page, obtaining cached silent patch information and starting silent patch downloading, if judging that the number of patch downloading and verification in a single patch flow fails for two times, clearing the number of local patch downloading and verification failures, retrying the downloading failure for infinite times, retrying the verification for at most three times, not retrying the retrying when the number of the retrying times reaches more than three times, and ending the patch repair in an invalid state. And if the verification is successful, executing the patch repair flow (decompression, synthesis and loading) of the framework. And if the loading fails, deleting the patch package file and ending the process in an invalid state. If the loading is successful, due to the limitation of a partial patch framework, the patch needs to be restarted after being loaded to be effective. Therefore, under the condition of silent patch, the APP can not be forced to restart directly. Monitoring whether the APP is in a non-foreground state or whether the APP is turned off, if the condition is met, restarting the APP to enable the patch to take effect when the APP returns to the foreground or is on the screen next time, and ending the patch repairing process.
As described above, if the full package degradation repair process is entered, the breakpoint resume download thread is started to download the apk installation package configured in the newappll, and after the download is completed, the apk installation program of the system is directly called to perform the overlay installation on the app.
In another aspect, an embodiment of the present invention further provides an application updating system based on an Android terminal, which includes:
a communication module: the patch information is used for receiving the server feedback;
an update module: the system comprises a patch information module, a primary update module, a secondary update module and a server, wherein the patch information module is used for providing patch information for the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
secondary update scheme: the application is updated using only the patch, and if updating the application using the patch fails, the update is retried or stopped.
In a preferred embodiment, the major update scheme comprises a major update sub-scheme I and a major update sub-scheme II, when the major update scheme is selected, one of the major update sub-scheme I and the major update sub-scheme II is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating an application program by a patch, if the application program is unsuccessfully updated by the patch, prompting a user to select a full quantum packet updating flow, and downloading the full quantum packet to update the application program when the user selects the full quantum packet updating flow;
the secondary updating scheme comprises a primary updating sub-scheme I and a secondary updating sub-scheme II, and when the secondary updating scheme is selected, one of the primary updating sub-scheme I and the secondary updating sub-scheme II is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
In a preferred embodiment, the patch information includes a forced update field and a new full packet address field, when the forced update field is yes and the new full packet address field is not empty, a first major update sub-scheme is automatically selected, when the forced update field is no and the new full packet address field is not empty, a second major update sub-scheme is automatically selected, when the forced update field is yes and the new full packet address field is empty, the first minor update sub-scheme is automatically selected, and when the forced update field is no and the new full packet address field is empty, the second minor update sub-scheme is automatically selected.
The working principle of the Android-terminal-based application program updating system is the same as that of the Android-terminal-based application program updating method, and the details are not repeated here.
On the basis of the application program updating mode in the prior art, a whole set of complete and flexible Android terminal hot-repair method is integrated by designing the updating scheme for different scenes, and the defects of flexibility, coverage rate, timeliness and the like brought by the existing mode are effectively overcome.
The method is based on a general Android hot-update framework (such as WeChat Tinker, American Robust and the like) to provide basic hot-repair capability for APP, and the following mechanisms are designed on the basis, so that the method brings corresponding advantages:
(1) and patch gray release supports patch release in different gray environments.
(2) The restoration process of full package loading is used as an effective bottom-mounting process when emergency patches cannot take effect due to various abnormal conditions, and the serious online problem can be timely and comprehensively restored.
(3) And (3) performing system compatibility failure exception handling, and performing degradation repair processing as required when the system version where the current client is located is incompatible with the integrated hot update framework, so as to avoid the application flash-back problem caused by the self-compatibility problem of the hot update framework.
(4) And the patch package checking mechanism is added with a download checking exception retry mechanism, and when the retry mechanism cannot continue processing, the degradation repair processing can be carried out as required.
(5) Configurable patch policy: at present, several schemes such as a mandatory popup patch, a selectable bottom-pocketed popup patch, a common popup patch, a silent patch and the like are supported, and a more appropriate strategy can be adopted to achieve balance between user experience and problem repair according to different on-line problem emergency degrees, so that on-line problems are repaired with lower cost, and normal operation of services is effectively guaranteed.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention, and all equivalent structures or equivalent flow transformations that may be applied to the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (7)
1. An application program updating method based on an Android terminal is characterized by comprising the following steps:
receiving patch information fed back by the server;
according to the specific field information in the patch information, one of a major updating scheme and a minor updating scheme is automatically selected for updating the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
the major updating scheme comprises a major updating sub-scheme I and a major updating sub-scheme II, and when the major updating scheme is selected, one of the major updating sub-scheme I and the major updating sub-scheme II is automatically selected to update the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating the application program by the patch, if the application program is failed to be updated by the patch, prompting a user to select a full quantum package updating process, and downloading the full quantum package to update the application program when the user selects the full quantum package updating process
Secondary update scheme: updating the application program only by using the patch, and if the application program is not updated by using the patch, retrying or stopping updating;
the secondary updating scheme comprises a primary updating sub-scheme I and a secondary updating sub-scheme II, and when the secondary updating scheme is selected, one of the primary updating sub-scheme I and the secondary updating sub-scheme II is automatically selected for updating the application program according to the specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
2. The Android-side-based application program updating method of claim 1, wherein in a major updating scheme, when a patch fails to be downloaded or a patch fails to be verified more than a predetermined number of times, or when both a patch and a patch are successfully downloaded but an application program is not successfully updated by using the patch, the application program is determined to fail to be updated by using the patch.
3. The Android-terminal-based application program updating method of claim 1, wherein the patch information includes a new full quantum packet address field, and when the new full quantum packet address field is not empty, a major updating scheme is automatically selected; when the new full packet address field is empty, the secondary update scheme is automatically selected.
4. The Android-terminal-based application program updating method of claim 1, wherein the patch information includes a forced update field and a new full packet address field, when the forced update field is yes and the new full packet address field is not empty, a first major update sub-scheme is automatically selected, when the forced update field is no and the new full packet address field is not empty, a second major update sub-scheme is automatically selected, when the forced update field is yes and the new full packet address field is empty, the first minor update sub-scheme is automatically selected, and when the forced update field is no and the new full packet address field is empty, the second minor update sub-scheme is automatically selected.
5. The Android-terminal-based application program updating method of claim 1, wherein the patch information includes a patch address field and a new full package address field, in a major updating scheme, a patch is downloaded according to the patch address field, a full package is downloaded according to the new full package address field, and in a minor updating scheme, the patch is downloaded according to the patch address field.
6. An application program updating system based on an Android terminal is characterized by comprising:
a communication module: the patch information is used for receiving the server feedback;
an update module: the system comprises a patch information module, a primary update module, a secondary update module and a server, wherein the patch information module is used for providing patch information for the application program; wherein the content of the first and second substances,
the major updating scheme is as follows: firstly, updating an application program by a patch, entering a full package updating flow if the application program is failed to be updated by the patch, and downloading the full package to update the application program;
secondary update scheme: updating the application program only by using the patch, and if the application program is not updated by using the patch, retrying or stopping updating;
the major updating scheme comprises a major updating sub-scheme I and a major updating sub-scheme II, and when the major updating scheme is selected, one of the major updating sub-scheme I and the major updating sub-scheme II is automatically selected to update the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
major update sub-scheme one: firstly, updating an application program by a patch, if the application program is failed to be updated by the patch, automatically entering a full package updating flow, downloading a full package and updating the application program;
major update sub-scheme two: firstly, updating an application program by a patch, if the application program is unsuccessfully updated by the patch, prompting a user to select a full quantum packet updating flow, and downloading the full quantum packet to update the application program when the user selects the full quantum packet updating flow;
the secondary updating scheme comprises a primary updating sub-scheme I and a secondary updating sub-scheme II, and when the secondary updating scheme is selected, one of the primary updating sub-scheme I and the secondary updating sub-scheme II is automatically selected for updating the application program according to specific field information in the patch information field; wherein the content of the first and second substances,
secondary update sub-scheme one: updating the application program by using the popup patch, and when the application program is failed to be updated by using the patch, performing silent retry and normally operating the application program;
secondary update sub-scheme two: and updating the application program by using the silent patch, and finishing the updating of the application program in an invalid state when the application program is failed to be updated by using the patch, wherein the application program runs normally.
7. The Android-based application update system of claim 6, wherein the patch information includes a forced update field and a new full packet address field, and when the forced update field is yes and the new full packet address field is not empty, the first major update sub-scheme is automatically selected, when the forced update field is no and the new full packet address field is not empty, the second major update sub-scheme is automatically selected, when the forced update field is yes and the new full packet address field is empty, the first minor update sub-scheme is automatically selected, and when the forced update field is no and the new full packet address field is empty, the second minor update sub-scheme is automatically selected.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111584614.5A CN113961224B (en) | 2021-12-23 | 2021-12-23 | Android-terminal-based application program updating method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111584614.5A CN113961224B (en) | 2021-12-23 | 2021-12-23 | Android-terminal-based application program updating method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113961224A CN113961224A (en) | 2022-01-21 |
| CN113961224B true CN113961224B (en) | 2022-03-08 |
Family
ID=79473664
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111584614.5A Active CN113961224B (en) | 2021-12-23 | 2021-12-23 | Android-terminal-based application program updating method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113961224B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115914451A (en) * | 2022-10-27 | 2023-04-04 | 兴业银行股份有限公司 | Forced updating method and system for android application version |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105677363A (en) * | 2016-02-03 | 2016-06-15 | 四川长虹电器股份有限公司 | OTA (Over-the-Air Technology) upgrading system |
| CN107665135A (en) * | 2017-10-20 | 2018-02-06 | 维沃移动通信有限公司 | The method for pushing and device of a kind of ROMPaq |
| CN110825408A (en) * | 2019-10-30 | 2020-02-21 | 中国农业银行股份有限公司 | Program version updating method, self-service equipment and version control server |
| CN111708566A (en) * | 2020-06-10 | 2020-09-25 | 深圳云之家网络有限公司 | Software increment updating method, device, system and computer readable storage medium |
| CN112256296A (en) * | 2020-09-22 | 2021-01-22 | 上海东普信息科技有限公司 | Express delivery service APP updating method, device, equipment and storage medium based on Weex |
| CN113448611A (en) * | 2021-08-31 | 2021-09-28 | 中邮消费金融有限公司 | Method and system for quickly and thermally updating application program |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8200106B2 (en) * | 2009-06-11 | 2012-06-12 | Canon Kabushiki Kaisha | Image forming apparatus with image forming condition control feature based on difference in patch densities |
| US20160291940A1 (en) * | 2014-07-07 | 2016-10-06 | Symphony Teleca Corporation | Remote Embedded Device Update Platform Apparatuses, Methods and Systems |
-
2021
- 2021-12-23 CN CN202111584614.5A patent/CN113961224B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105677363A (en) * | 2016-02-03 | 2016-06-15 | 四川长虹电器股份有限公司 | OTA (Over-the-Air Technology) upgrading system |
| CN107665135A (en) * | 2017-10-20 | 2018-02-06 | 维沃移动通信有限公司 | The method for pushing and device of a kind of ROMPaq |
| CN110825408A (en) * | 2019-10-30 | 2020-02-21 | 中国农业银行股份有限公司 | Program version updating method, self-service equipment and version control server |
| CN111708566A (en) * | 2020-06-10 | 2020-09-25 | 深圳云之家网络有限公司 | Software increment updating method, device, system and computer readable storage medium |
| CN112256296A (en) * | 2020-09-22 | 2021-01-22 | 上海东普信息科技有限公司 | Express delivery service APP updating method, device, equipment and storage medium based on Weex |
| CN113448611A (en) * | 2021-08-31 | 2021-09-28 | 中邮消费金融有限公司 | Method and system for quickly and thermally updating application program |
Non-Patent Citations (2)
| Title |
|---|
| "Tedsuto: A General Framework for Testing Dynamic Software Updates";Luís Pina等;《2016 IEEE International Conference on Software Testing, Verification and Validation》;20160721;第278-288页 * |
| OTA常见方案分析（差分升级 全量升级 AB面升级 Recovery系统升级）;qlexcel;《https://blog.csdn.net/qlexcel/article/details/119874221》;20210823;第1-3页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113961224A (en) | 2022-01-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2482187A1 (en) | Software upgrading method, software upgrading system and client | |
| US10348804B2 (en) | System to automatically process components on a device | |
| US6928579B2 (en) | Crash recovery system | |
| US7937697B2 (en) | Method, system and computer program for distributing software patches | |
| US7934210B1 (en) | System and method for updating one or more programs and their environment | |
| CN105681060B (en) | virtualized network function management upgrading method, device and server | |
| US20090017812A1 (en) | Method and system for restoring user settings after over-the-air update of mobile electronic device software | |
| US9471300B2 (en) | Wireless firmware upgrades to an alarm security panel | |
| US20120117557A1 (en) | Method and system for upgrading wireless data card | |
| CN101594613A (en) | The method of terminal equipment and upgrading thereof, system | |
| CN101610604A (en) | A kind of method for upgrading software and system | |
| CN110597545B (en) | Hot patch Ding Zhineng upgrading method and system based on OTA component | |
| JP2003029997A (en) | Software upgrading method in network environment and network device by the same | |
| CN105260209A (en) | Hot-update solution of program | |
| CN1364390A (en) | Method and apparatus for downloading into radio terminal | |
| CN112698846B (en) | Method and system for automatically installing patches in Linux system | |
| CN105808278A (en) | Client version upgrading method and device | |
| CN113961224B (en) | Android-terminal-based application program updating method and system | |
| CN115202680A (en) | System and method for automatically upgrading local client on line in remote manner | |
| CN116028084A (en) | Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform | |
| CN115208761A (en) | OTA upgrading system | |
| CN111443951A (en) | System starting method and system starting device | |
| CN111190639A (en) | Automatic upgrading method, system, device and storage medium suitable for WebLogic | |
| CN115080082A (en) | Automatic upgrading method and system based on intelligent robot | |
| CN113312079A (en) | Hot patch upgrading method and device, electronic equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |