Implementation method for realizing OTA program self-upgrading of Android system

Abstract

The invention belongs to the technical field of OTA program remote upgrading, and particularly relates to a method for realizing OTA program upgrading of an Android system, which comprises the following steps: step 1, an OTA cloud platform configures an OTA upgrading strategy and synchronizes an upgrading package to a CDN server; 2, the client serves as a daemon process resident system, the client monitors system startup broadcast, and the client monitors system network information; 3, the client side collects system information (IMEI identity code, Serial Number and the like), OTA version information and the like, an AES algorithm is used for encryption, and the client side securely transmits encrypted data to the server through HTTPS; according to the method, user intervention is not needed in the whole process, silent upgrading is achieved, a safe and efficient remote wireless upgrading solution is provided for the Android device by guaranteeing upgradeability and expandability of the OTA application, and the operation and maintenance cost of suppliers is greatly saved.

Description

Technical Field

[0001] The present invention belongs to the technical field of remote upgrading of OTA's own programs, and specifically relates to a method for implementing OTA program self-upgrading in an Android system. Background Art

[0002] The present invention is a method for implementing "OTA program self-upgrading" in an Android system, and is a technology for remotely upgrading "OTA's own program" for terminal devices of the Android system. It is a wireless firmware update technology that allows devices to receive and install system or application updates via a wireless network without connecting to a computer.

[0003] This technology involves wireless communication, data encryption, differential update algorithms, and error recovery mechanisms, aiming to ensure that devices can safely and efficiently self-upgrade, enhance the user experience, and quickly fix security vulnerabilities.

[0004] Existing Technologies: In the technical field of the Android platform, OTA program self-upgrading usually refers to the ability of application programs or system firmware to be automatically updated via a wireless network. This technology allows OTA programs to be integrated into the Android system and can be automatically updated as the entire system is upgraded. The key advantage of OTA technology is that it can ensure that devices always stay up-to-date, while providing a better user experience and security.

[0005] Disadvantages of Existing Technologies: 1. Storage space consumption: To implement OTA self-program upgrading, the system may require additional storage space to store OTA upgrade packages. Especially in non-A / B system updates, after the OTA package is downloaded, it occupies the cache partition space, which may affect the storage of other applications or data.

[0006] 2. Timeliness of updates: OTA upgrades rely on network connections and users' active update behaviors, which means that not all users will immediately receive the latest system updates, and the time for users to obtain security patches and new features may be delayed.

[0007] 3. Security issues: OTA programs do not have the ability to self-upgrade. When problems such as bugs occur in OTA programs, the entire Android system may not be able to be upgraded, and the OTA function cannot be used.

[0008] 4. System compatibility issues: OTA programs do not have the ability to self-upgrade. When different versions of the Android system are upgraded and compatibility issues occur, the entire OTA function cannot be used.

[0009] User experience problem: The OTA program frequently relies on the entire system upgrade, and the whole process is cumbersome and heavy, which greatly affects the user experience. Summary of the Invention

[0010] To solve the problems raised in the above background technology, the present invention provides a method for implementing the self-upgrade of the OTA program in the Android system, including the following steps: Step 1: The OTA cloud platform configures the OTA upgrade policy and synchronizes the upgrade package to the CDN server; Step 2: The client resides in the system as a daemon process. The client listens to the system startup broadcast and the system network information; Step 3: The client collects system information (IMEI identity code, SerialNumber serial number, etc.), OTA self-version information, etc., and encrypts them using the AES algorithm. The client securely transmits the encrypted data to the server via HTTPS; Step 4: The server receives the client request, performs server policy verification and matching, and issues the self-upgrade policy to the client; Step 5: After receiving the upgrade instruction from the server, the client securely downloads the upgrade package through the CDN service; Step 6: The client performs RSA decryption and verification to ensure the security and reliability of the upgrade package; Step 7: The client calls the system interface to perform a self-upgrade operation on the OTA program itself; Step 8: The Android system returns information such as the OTA program upgrade progress and upgrade result; Step 9: Finally, the client reports the upgrade progress and result to the server.

[0011] As a method for implementing the self-upgrade of the OTA program in the Android system according to the present invention, preferably, in the above Step 1: 1) In the OTA cloud platform, first configure the OTA upgrade policy, configure the specific clients to be upgraded, and single-device configuration and batch device import are supported here; 2) Configure the original version and target version of the OTAAPP corresponding to the device. Multiple initial versions for upgrade can be configured to the same target version here; 3) After the version is configured, upload the corresponding OTA upgrade package to the OTA cloud platform and synchronize it to the CDN server.

[0012] As a method for implementing the self-upgrade of the OTA program in the Android system according to the present invention, preferably, in the above Step 2: 1) The client configuration process resides, and the system startup broadcast and network switch broadcast are registered; 2) The client performs Android system signing and integrates it into the device.

[0013] As an implementation method for the Android system of the present invention to achieve self-upgrade of the OTA program, preferably, in step 3: 1) After the client OTAAPP starts, it collects Android system information through the system interface, including (IMEI identity code, SerialNumber serial number, etc.), and collects version information such as the versionCode and versionName of the OTAAPP itself; 2) The client OTAAPP performs AES algorithm encryption and encapsulation processing on the version information; 3) The client OTAAPP synchronizes the data to the OTA cloud server through HTTPS two-way authentication for version matching.

[0014] As an implementation method for the Android system of the present invention to achieve self-upgrade of the OTA program, preferably, in step 5: 1) After the client receives the server response, it decrypts and parses the stored json policy using RSA; 2) The client parses the json policy in the cloud, obtains the download URL of the upgrade package file, downloads the upgrade package file from the cdn through https, and stores it in the device directory; 3) The client parses the json policy in the cloud, obtains the download URL of the signature file, downloads the signature file from the cdn through https, and stores it in the device directory.

[0015] As an implementation method for the Android system of the present invention to achieve self-upgrade of the OTA program, preferably, in step 6: 1) The client parses the json policy in the cloud to obtain the hash value of the upgrade package; 2) The client uses the hash value and the signature file to verify the security and reliability of the upgrade package.

[0016] As an implementation method for the Android system of the present invention to achieve self-upgrade of the OTA program, preferably, in step 9: 1) Finally, the client reports the upgrade progress and result of the OTAAPP to the OTA cloud server; 2) The OTA cloud stores the self-upgrade result and updates the policy.

[0017] Compared with the prior art, the beneficial effects of the present invention are: The entire process of the present invention requires no user intervention and realizes silent upgrade. This method provides a safe and efficient remote wireless upgrade solution for Android devices by ensuring the upgradability and expandability of the OTA itself, greatly saving the operation and maintenance costs of the supplier. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation to the present invention. In the drawings: Figure 1 is the architecture diagram of the present invention; Figure 2 is the process timing diagram of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] 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. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. Embodiment

[0020] As Figure 1-2 shown; A method for implementing the self-upgrade of the OTA program in an Android system.

[0021] In this embodiment: To solve the technical problems existing in this prior art, as disclosed in the background art above, "1. Storage space consumption: To implement the self-upgrade of the OTA program, the system may require additional storage space to store the OTA upgrade package. Especially in non-A / B system updates, after the OTA package is downloaded, it occupies the cache partition space, which may affect the storage of other applications or data.

[0022] 2. Timeliness of update: OTA upgrade depends on network connection and the user's active update behavior, which means that not all users will immediately obtain the latest system update, and it may delay the time for users to obtain security patches and new features.

[0023] 3. Security issues: The OTA program has no self-upgrade ability. When problems such as bugs occur in the OTA program, it will cause the entire Android system to be unable to upgrade and the OTA function to be unavailable.

[0024] 4. System compatibility issues. The OTA program has no self-upgrade ability. When different versions of the Android system are upgraded and compatibility issues occur, it will cause the entire OTA function to be unavailable.

[0025] User experience problem: The OTA program frequently relies on the entire system upgrade, and the whole process is cumbersome and heavy, which greatly affects the user experience. In view of the actual use, this problem obviously exists and is relatively difficult to solve. Therefore, to solve this technical problem, a method for implementing the self-upgrade of the OTA program in the Android system is provided.

[0026] As Figure 1-2 shown; Combined with the above content, it includes the following steps: The first step: 1. On the OTA cloud platform, first configure the OTA upgrade policy, and configure the specific clients to be upgraded. Here, single-device configuration and batch device import are supported.

[0027] 2. Configure the original version and target version of the OTAAPP corresponding to the device. Here, multiple initial versions for upgrade can be configured to the same target version.

[0028] 3. After the version is configured, upload the corresponding OTA upgrade package to the OTA cloud platform and synchronize it to the CDN server.

[0029] The second step: 1. The client configuration process runs permanently, and the system startup broadcast and network switching broadcast are registered. 2. The client performs Android system signing and integrates it into the device.

[0030] The third step: 1. After the client OTAAPP starts, collect Android system information through the system interface, including (IMEI identity code, SerialNumber serial number, etc.), and collect version information such as the versionCode and versionName of the OTAAPP itself.

[0031] 2. The client OTAAPP encapsulates and processes the version information through the AES algorithm.

[0032] 3. The client OTAAPP synchronizes the data to the OTA cloud server through HTTPS two-way authentication for version matching.

[0033] The fourth step: 1. When the server receives the client request, it performs server policy verification and matching. If there is a new version, it sends the self-upgrade json policy to the client.

[0034] The fifth step: 1. After the client receives the server response, it decrypts and parses the stored json policy using RSA.

[0035] 2. The client parses the JSON policy from the cloud, obtains the download URL of the upgrade package file, downloads the upgrade package file from the CDN via HTTPS, and stores it in the device directory. 3. The client parses the JSON policy from the cloud, obtains the download URL of the signature file, downloads the signature file from the CDN via HTTPS, and stores it in the device directory. Sixth step: 1. The client parses the JSON policy from the cloud to obtain the hash value of the upgrade package; 2. The client uses the hash value and the signature file to verify the security and reliability of the upgrade package.

[0036] Seventh step: 1. The client calls the system interface to perform the self-upgrade operation on the OTAAPP itself.

[0037] Eighth step: 1. The Android system returns information such as the upgrade progress and upgrade result of OTAAPP to the client.

[0038] Ninth step: 1. Finally, the client reports the upgrade progress and result of OTAAPP to the OTA cloud server.

[0039] 2. The OTA cloud stores the self-upgrade result and updates the policy.

[0040] The technical problems solved by the present invention are: 1. Storage space consumption: Only the upgrade package or patch package of the OTA itself needs to be downloaded, without downloading the entire Android system package, significantly reducing the size of the OTA upgrade package and greatly reducing the consumption of the device's storage space.

[0041] 2. Timeliness of updates The OTA itself can provide background automatic download and incremental update functions, ensuring that users automatically download updates when connected to Wi-Fi, reducing waiting time and improving the timeliness of updates.

[0042] 3. Security issues The OTA program has the ability of self-upgrade. If it has bugs for some reason, it can fix the problems through self-upgrade, thus ensuring the upgrade ability of the entire Android system.

[0043] 4. System compatibility issues The OTA program has the ability of self-upgrade, which can be carried out along with the upgrade of the Android system, provides backward-compatible APIs and functions, ensures that old-version applications can adapt to the changes of the new system, and reduces compatibility problems caused by system upgrades.

[0044] 5. User experience issues The self-upgrade of the OTA program can achieve automatic download and seamless upgrade of applications, etc. Compared with the existing solutions, it does not rely on the upgrade of the entire Android system, does not require users to manually authorize, and does not require repeated device restarts, etc.

[0045] Finally, it should be noted that the above are only the preferred embodiments of the present invention and are not used to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A method for implementing the self-upgrade of an OTA program in the Android system, characterized in that: It includes the following steps: Step 1: The OTA cloud platform configures the OTA upgrade policy and synchronizes the upgrade package to the CDN server; Step 2: The client runs as a daemon process in the system. The client listens for the system startup broadcast and the system network information; Step 3: The client collects system information (such as IMEI identification code, SerialNumber serial number, etc.), OTA's own version information, etc., and encrypts them using the AES algorithm. The client securely transmits the encrypted data to the server via HTTPS; Step 4: After receiving the client request, the server performs server policy verification and matching, and sends the self-upgrade policy to the client; Step 5: After receiving the upgrade instruction from the server, the client securely downloads the upgrade package through the CDN service; Step 6: The client performs RSA decryption and verification to ensure the security and reliability of the upgrade package; Step 7: The client calls the system interface to perform a self-upgrade operation on the OTA program itself; Step 8: The Android system returns information such as the OTA program upgrade progress and upgrade results; Step 9: Finally, the client reports the upgrade progress and results to the server.

2. The implementation method for the OTA program of an Android system to perform self-upgrade according to claim 1, characterized in that: In the said Step 1: 1) In the OTA cloud platform, first configure the OTA upgrade policy, configure the specific clients to be upgraded. Here, single-device configuration and batch device import are supported; 2) Configure the original version and target version of the OTAAPP corresponding to the device. Here, multiple initial versions for upgrade can be configured to the same target version; 3) After the version is configured, upload the corresponding OTA upgrade package to the OTA cloud platform and synchronize it to the CDN server.

3. The implementation method for the OTA program of an Android system to achieve self-upgrade according to claim 1, characterized in that: In the said Step 2: 1) The client configuration process runs permanently, registering for the system startup broadcast and network switch broadcast; 2) The client performs Android system signing and integrates it into the device.

4. The implementation method of an OTA program for self-upgrade in an Android system according to claim 1, characterized in that: In the said Step 3: 1) After the client OTAAPP starts, collect Android system information through the system interface, including (IMEI identification code, SerialNumber serial number, etc.), and collect version information such as the versionCode and versionName of the OTAAPP itself; 2) The client OTAAPP encapsulates and processes the version information through the AES algorithm; 3) The client OTAAPP synchronizes the data to the OTA cloud server through HTTPS two-way authentication for version matching.

5. The implementation method for the OTA program of an Android system to upgrade itself according to claim 1, characterized in that: In the said Step 5: 1) After receiving the server response, the client decrypts and parses the stored json policy using RSA; 2) The client parses the json policy in the cloud, obtains the download URL of the upgrade package file, downloads the upgrade package file from the cdn via https, and stores it in the device directory; 3) The client parses the json policy in the cloud, obtains the download URL of the signature file, downloads the signature file from the cdn via https, and stores it in the device directory.

6. The implementation method for the OTA program itself to be upgraded in an Android system according to claim 1, characterized in that: In the said Step 6: 1) The client parses the json policy in the cloud to obtain the hash value of the upgrade package; 2) The client uses the hash value and the signature file to verify the security and reliability of the upgrade package.

7. The implementation method of an OTA program for self-upgrade in an Android system according to claim 1, characterized in that: In the said Step 9: 1) Finally, the client reports the OTA APP upgrade progress and results to the OTA cloud server; 2) The OTA cloud storage stores the upgrade results and updates the policies.

Images