Automatic over-the-air upgrading method and system

Abstract

The invention discloses an automatic air upgrading method and system, and belongs to the technical field of air upgrading of ultrasonic equipment. Comprising the following steps: S1, acquiring an equipment log of an equipment end and analyzing a keyword frequency in the equipment log until the keyword frequency exceeds a first set threshold value, and sending an upgrading request to a server end; s2, the server side sends an update packet to the equipment side according to the received upgrade request; s3, the device end receives the update packet and performs integrity verification; and S4, monitoring the power supply state of the equipment end through a power supply state monitoring algorithm, judging whether the power supply state of the equipment end is higher than a second set threshold value or not, if so, installing the update package at the equipment end, and if not, pausing the installation of the update package and feeding back the current update state. The technical scheme has the beneficial effects that the user is allowed to update the version of the ultrasonic equipment according to the actual situation without the intervention of professionals, and the updating flexibility and safety are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of over-the-air (OTA) upgrade for ultrasonic devices, and particularly to an OTA upgrade method and system. Background Art

[0002] With the wide application of intelligent devices, from smartphones, tablets to intelligent vehicles, smart home devices, etc., users' requirements for device functions and performance are constantly increasing. The OTA (Over-The-Air) update technology has emerged accordingly. It allows devices to automatically obtain and install software or firmware updates through a wireless network, without the need for users to manually connect external devices such as computers for update operations.

[0003] Traditional updates for handheld ultrasound software and firmware usually require the intervention of professionals. In different medical departments and primary medical institutions, due to different device usage frequencies and requirements, it is necessary to flexibly update handheld ultrasound devices according to actual situations, resulting in a complex and time-consuming update process and unable to meet the requirements of rapid deployment and flexible updates. Summary of the Invention

[0004] The purpose of the present invention is to provide an automated OTA upgrade method to solve the above technical problems;

[0005] The purpose of the present invention is also to provide an automated OTA upgrade system to solve the above technical problems;

[0006] An automated OTA upgrade method includes:

[0007] Step S1: By obtaining the device log of the device end and analyzing the keyword frequency in the device log, until the keyword frequency exceeds a first set threshold, send an upgrade request to the server end;

[0008] Step S2: The server end sends an update package to the device end according to the received upgrade request;

[0009] Step S3: The device end receives the update package and performs integrity verification;

[0010] Step S4: Monitor the power state of the device end through a power state monitoring algorithm, and determine whether the power state of the device end is higher than a second set threshold. If so, the device end installs the update package. If not, suspend installing the update package and feedback the current update status.

[0011] Preferably, step S3 includes: after backing up the current version of the device end, receiving the update package sent by the server end, and performing integrity verification on the update package by embedding a version verification data structure and combining with a blockchain.

[0012] Preferably, step S4 includes step S41 of initializing the power supply state, setting the second set threshold, and obtaining the power supply data of the device end in real time;

[0013] Step S42 of collecting the power supply data of the device end at the first sampling frequency, filtering and preprocessing it to obtain processed data;

[0014] Step S43 of comparing the processed data with the second set threshold to determine whether the power supply state of the device end is normal. If so, install the update package on the device end. If not, suspend the installation of the update package, identify the abnormal state of the device end, and feedback the current update status.

[0015] Preferably, it further includes step S0 of initializing the device end and detecting the current versions of the device end and the server end.

[0016] Preferably, it further includes step S5 of determining whether the update package on the device end is installed successfully. If so, clean up the temporary files generated during the update process of the device end. If not, perform a rollback operation according to the backup data of the device end, and display the reason for the update failure and the rollback result to the user.

[0017] An automated over-the-air upgrade system includes

[0018] A server-side management module for managing and distributing update packages;

[0019] A device-side update module for receiving and installing the update package;

[0020] A communication module connecting the server-side management module and the device-side update module for transmitting the update package distributed by the server-side management module to the device-side update module;

[0021] A user interface module connecting the device-side update module for displaying the update status and progress according to the update mode.

[0022] Preferably, the server-side management module includes

[0023] A version comparison unit for obtaining and comparing the current version information sent by the device-side update module to determine the update package to be sent to the device end;

[0024] An update package sending unit connected to the version comparison unit for distributing the corresponding update package to the device end according to the upgrade request of the device end.

[0025] Preferably, the device-side update module includes

[0026] The current version detection unit is used to detect the current version of the device end. By obtaining the device log of the device end and analyzing the keyword frequency in the device log, when the keyword frequency exceeds the first set threshold, an upgrade request is sent to the server end;

[0027] The integrity verification unit is connected to the server end management module. By embedding a version verification data structure in the update package, the integrity of the update package is verified in combination with the blockchain.

[0028] Preferably, the communication module includes a data encryption transmission sub-module, and the data encryption transmission sub-module includes,

[0029] The key expansion unit is used to expand the initial key to obtain the round keys required for different rounds;

[0030] The encryption initial unit is connected to the key expansion unit and is used to perform an exclusive OR operation on the plaintext data and the first round key to obtain the first state matrix;

[0031] The main encryption unit is connected to the encryption initial unit and is used to perform byte substitution, row shift, column mixing, and round key addition processing on the first state matrix in sequence to obtain the second state matrix;

[0032] The final encryption unit is connected to the main encryption unit and is used to perform byte substitution and row shift on the second state matrix to obtain the ciphertext data;

[0033] The decryption initial unit is connected to the final encryption unit and is used to perform an exclusive OR operation on the received ciphertext data and the last round key to obtain the third state matrix;

[0034] The main decryption unit is connected to the decryption initial unit and is used to perform reverse row shift, inverse byte substitution, inverse column mixing, and round key addition processing on the third state matrix in sequence to obtain the original state data;

[0035] The final decryption unit is connected to the main decryption unit and is used to perform reverse row shift and inverse byte substitution on the original state data to obtain the decrypted plaintext data.

[0036] Preferably, it further includes a power status monitoring module, which is connected to the server end management module and the device end update module, and is used to monitor the power status of the device end, determine whether the power status of the device end is higher than the second set threshold. If so, the device end installs the update package. If not, the installation of the update package is suspended, and the current update status is feedback.

[0037] The beneficial effects of the present invention are as follows: It allows users to update the version of the ultrasonic device according to the actual situation without the intervention of professionals, improving the flexibility and security of the update. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 is a step diagram of the automated over-the-air upgrade method of the present invention;

[0039] Figure 2 is a schematic diagram of step S4 of the present invention;

[0040] Figure 3 is a connection block diagram of the automated over-the-air upgrade system of the present invention;

[0041] Figure 4 is a schematic diagram of the server-side management module of the present invention;

[0042] Figure 5 is a schematic diagram of the device-side update module of the present invention;

[0043] Figure 6 is a schematic diagram of the data encryption transmission sub-module of the present invention;

[0044] Figure 7 is an encryption transmission flow chart of the communication module of the present invention;

[0045] Figure 8 is a flow chart of update package verification and installation of the present invention;

[0046] Figure 9 is a flow chart of device-side power status monitoring of the present invention;

[0047] Figure 10 is a flow chart of the automated over-the-air upgrade of the present invention.

[0048] In the drawings: 1. Server-side management module; 11. Version comparison unit; 12. Update package sending unit; 2. Device-side update module; 21. Current version detection unit; 22. Integrity verification unit; 3. Communication module; 31. Data encryption transmission sub-module; 311. Key expansion unit; 312. Encryption initial unit; 313. Encryption main unit; 314. Encryption final unit; 315. Decryption initial unit; 316. Decryption main unit; 317. Decryption final unit; 4. User interface module; 5. Power status monitoring module. DETAILED DESCRIPTION OF THE INVENTION

[0049] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying 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 belong to the scope of protection of the present invention.

[0050] It should be noted that, without conflict, the embodiments in the present invention and the features in the embodiments may be combined with each other.

[0051] The present invention will be further described below with reference to the accompanying drawings and specific embodiments, but it is not limited to the present invention.

[0052] An automated over-the-air upgrade method, as Figure 1 shown, includes

[0053] Step S1: By obtaining the device log of the device end and analyzing the keyword frequency in the device log until the keyword frequency exceeds the first set threshold, send an upgrade request to the server end;

[0054] Step S2: The server end sends an update package to the device end according to the received upgrade request;

[0055] Step S3: The device end receives the update package and performs integrity verification;

[0056] Step S4: Monitor the power state of the device end through the power state monitoring algorithm, and judge whether the power state of the device end is higher than the second set threshold. If so, the device end installs the update package. If not, suspend the installation of the update package and feedback the current update state.

[0057] Specifically, the present invention provides an automated over-the-air upgrade method for upgrading ultrasonic devices. Through multi-step collaboration, it ensures the intelligence, safety, and stability of device upgrades. From the intelligent triggering of upgrade requests to the secure verification of update packages and then to the reasonable operation based on the power state, each link is closely coordinated, providing strong support for the device to complete the upgrade efficiently and reliably. It allows users to update the version of ultrasonic devices according to the actual situation without the intervention of professional personnel, improving the flexibility and safety of updates.

[0058] In a preferred embodiment, step S3 includes backing up the current version of the device end, receiving the update package sent by the server end, and performing integrity verification on the update package by embedding a version verification data structure and combining with the blockchain.

[0059] Specifically, save the data of the current version. When a problem occurs during the upgrade, the data can be restored from the backup to return the device to the state before the upgrade. The blockchain has the characteristics of being tamper-proof and distributed storage. The version verification data structure (such as a hash value) can uniquely identify the content of the update package. By comparing the verification data with the blockchain record, the integrity of the update package and the credibility of the source can be verified.

[0060] More specifically, referring to Figure 8 , when it is analyzed that the log failure frequency is relatively high, download and verify the update package, embed the version verification data structure (such as a hash value) in the upgrade package, record it in the blockchain, distribute the upgrade package, and the device side receives and verifies it before installation.

[0061] In a preferred embodiment, referring to Figure 2 , step S4 includes step S41, initializing the power state, setting a second set threshold, and obtaining the power data of the device side in real time;

[0062] Step S42, collecting the power data of the device side at the first sampling frequency, and performing filtering and preprocessing to obtain the processed data;

[0063] Step S43, comparing the processed data with the second set threshold to determine whether the power state of the device side is normal. If so, the device side installs the update package. If not, the installation of the update package is suspended, the abnormal state of the device side is identified, and the current update state is fed back.

[0064] Specifically, initializing the power state and setting the second set threshold in step S41 provide a basis for subsequent power state judgment. The power state of the device changes continuously. The set threshold is to define a reasonable power standard. Only when the power state is higher than this threshold does the device have sufficient power to complete the upgrade operation. Obtaining the power data of the device side in real time enables the system to dynamically grasp the power situation of the device.

[0065] Collecting the power data at the first sampling frequency in step S42 can ensure the timeliness and accuracy of the data. Since the collected data contains noise and interference information, filtering and preprocessing it can remove this useless information, obtain more reliable processed data, which can more truly reflect the power state of the device and provide a more accurate basis for subsequent judgment.

[0066] Step S43 compares the processed data with a second set threshold to determine whether the device power status is normal. If the power status is normal, it indicates that the device has sufficient power to support the installation of the update package. At this time, performing the installation operation can ensure the smooth completion of the upgrade. If the power status is abnormal, the installation of the update package is paused and the abnormal status is identified, which can avoid upgrade failures and device damage caused by insufficient power. At the same time, the current update status is promptly fed back so that users can take corresponding measures according to the situation, ensuring the controllability of the upgrade process.

[0067] Among them, the power consumption of different devices varies greatly during the upgrade process. For example, for small devices, the upgrade operation is relatively simple and the power consumption is low. A second set threshold of 20%-30% of the battery threshold is sufficient to complete the upgrade. While when upgrading the system, a large amount of data reading and writing and complex operations are involved, and the power consumption is high, and the second set threshold is 50%-60%.

[0068] Devices with strong performance can quickly process the collected power data. Therefore, a higher sampling frequency can be set. The first sampling frequency is 5-10 times per second to obtain the power status change more timely. While for devices with weaker performance, if the sampling frequency is too high, it will cause excessive system resource occupation and affect the normal operation of other functions of the device. The first sampling frequency is 1-2 times per second.

[0069] In a preferred embodiment, it further includes step S0 to initialize the device side and perform a version detection on the current versions of the device side and the server side.

[0070] Specifically, the current version of the device side is compared with the latest version of the server side, and it is determined whether an upgrade is required according to the preset rules. When the server side version is higher than the device side version, it is determined that the device needs to be upgraded.

[0071] In a preferred embodiment, it further includes step S5 to determine whether the update package of the device side is installed successfully. If so, the temporary files generated during the update process of the device side are cleaned up. If not, a rollback operation is performed according to the backup data of the device side, and the update failure reason and rollback result are displayed to the user.

[0072] Specifically, the temporary files are used to temporarily store data during the upgrade process and are no longer needed after the upgrade is completed. Cleaning them up can save storage space. Using the previously backed-up version data, the device is restored to the state before the upgrade to ensure the normal operation of the device. By presenting relevant information to the user, the user can understand the upgrade situation and facilitate the user to take further measures.

[0073] More specifically, by detecting and comparing the versions at both ends, it is possible to accurately determine whether the device end lags behind the server end version. Only when there is a version difference and an upgrade is required, will the subsequent upgrade process be triggered, reducing the waste of system resources and the consumption of network traffic. Ensure that before the upgrade operation starts, clearly understand the version status of the device end and the server end, providing a basis for accurately judging whether an upgrade is needed and selecting the appropriate update package later, avoiding unnecessary upgrade operations and improving the upgrade efficiency.

[0074] An automated over-the-air upgrade system, referring to Figure 3 , includes,

[0075] Server-side management module 1, used for managing and distributing update packages;

[0076] Device-side update module 2, used for receiving and installing update packages;

[0077] Communication module 3, connecting the server-side management module 1 and the device-side update module 2, used for transmitting the update packages distributed by the server-side management module 1 to the device-side update module 2;

[0078] User interface module 4, connecting the device-side update module 2, used for displaying the update status and progress according to the update mode.

[0079] Specifically, the present invention also provides an automated over-the-air upgrade system. The user interface module 4 provides an intuitive user interface, displays the update status and progress, and also allows users to select automatic or manual update modes, supports multiple devices and operating systems, and can be extended to different application scenarios and industry requirements.

[0080] The server-side management module 1 is responsible for managing and distributing update packages, can centrally store and maintain update resources, and uniformly allocate the update requirements of different devices. Reduces the cumbersome process of performing update operations on each device one by one.

[0081] The communication module 3 connects the server-side management module 1 and the device-side update module 2, and undertakes the important task of securely transmitting update packages. Using encryption technology, effectively prevents update packages from being stolen, tampered with, or damaged during transmission.

[0082] The device-side update module 2 performs integrity verification after receiving the update package, further ensuring the accuracy and reliability of the update package, guaranteeing the smooth progress of the device upgrade process, and avoiding device failures caused by incorrect updates.

[0083] The user interface module 4 is connected to the device - side update module 2, which displays the update status and progress according to the update mode, enabling the user to understand the upgrade process in real - time. The user can intuitively see information such as the download progress and installation status of the update package, eliminating the uncertainty during the upgrade process. Moreover, the user can also select the automatic or manual update mode through this module to flexibly control the upgrade operation according to their own needs and usage scenarios.

[0084] In a preferred embodiment, referring to Figure 4 , the server - side management module 1 includes

[0085] a version comparison unit 11, which is used to obtain and compare the current version information sent by the device - side update module 2 to determine the update package to be sent to the device - side;

[0086] an update - package sending unit 12, connected to the version comparison unit 11, which is used to distribute the corresponding update package to the device - side according to the upgrade request of the device - side.

[0087] Specifically, the server - side serves as the management and distribution center of the update package. After receiving the upgrade request from the device - side, it accurately finds the corresponding update package according to the request information and sends it to the device - side, realizing the directional transmission of the update package. An upgrade communication mechanism is established between the device - side and the server - side, enabling the device - side to obtain the required update package in a timely manner and ensuring the smooth progress of the upgrade process.

[0088] In a preferred embodiment, referring to Figure 5 , the device - side update module 2 includes

[0089] a current - version detection unit 21, which is used to detect the current version of the device - side. By obtaining the device log of the device - side and analyzing the keyword frequency in the device log until the keyword frequency exceeds the first set threshold, it sends an upgrade request to the server - side;

[0090] a integrity verification unit 22, connected to the server - side management module 1, which verifies the integrity of the update package by embedding a version verification data structure in the update package and combining it with the blockchain.

[0091] Specifically, the device log records various information during the operation of the device, and the keyword frequency can reflect the operation status of certain aspects of the device. When the keyword frequency exceeds the threshold, it indicates that there are performance problems with the device, and these problems are repaired through upgrading, so an upgrade request is triggered. The keywords include errors, lags, and power consumption, realizing the intelligent triggering of upgrade requests according to the actual operation status of the device.

[0092] When the device has frequent problems such as errors, lags, and power consumption (corresponding to an increase in keyword frequency), a timely upgrade request can be made to solve these problems and improve the performance and stability of the device.

[0093] For keywords such as "system crash" and "hardware failure" that seriously affect the normal use of the device, since the device will not be able to work properly once such problems occur, the first set threshold should be set very low. As long as they occur 1-2 times, an upgrade request can be sent.

[0094] Keywords that slightly affect the device experience, such as "slight heating" and "brief black screen", have a certain impact on the device use experience but do not affect the core functions. The first set threshold can be appropriately increased. For example, when the frequency of the keyword "slight heating" exceeds 20 times in a day, an upgrade request can be considered for sending.

[0095] In a preferred embodiment, referring to Figure 6 , the communication module 3 includes a data encryption and transmission sub-module 31, and the data encryption and transmission sub-module 31 includes,

[0096] A key expansion unit 311 for expanding the initial key to obtain the round keys required for different rounds;

[0097] An encryption initial unit 312 connected to the key expansion unit 311 for performing an exclusive OR operation on the plaintext data and the first round key to obtain a first state matrix;

[0098] An encryption main unit 313 connected to the encryption initial unit 312 for sequentially performing byte substitution, row shift, column mixing, and round key addition processing on the first state matrix to obtain a second state matrix;

[0099] An encryption final unit 314 connected to the encryption main unit 313 for performing byte substitution and row shift on the second state matrix to obtain ciphertext data;

[0100] A decryption initial unit 315 connected to the encryption final unit 314 for performing an exclusive OR operation on the received ciphertext data and the last round key to obtain a third state matrix;

[0101] A decryption main unit 316 connected to the decryption initial unit 315 for sequentially performing reverse row shift, inverse byte substitution, inverse column mixing, and round key addition processing on the third state matrix to obtain the original state data;

[0102] A decryption final unit 317 connected to the decryption main unit 316 for performing reverse row shift and inverse byte substitution on the original state data to obtain the decrypted plaintext data.

[0103] Specifically, an encryption protocol is used to ensure the security of data transmission, and a backup is made before the update to prevent data loss.

[0104] Referring to Figure 7, the content of the file is encrypted using AES - 256 - GCM (Advanced Encryption Standard) symmetric encryption. The encryption key is encrypted with the server's public key using the RSA - OAEP algorithm and then transmitted. The data is encrypted twice with the TLS session key. First, the initial key is expanded to obtain the round keys required for different rounds;

[0105] The encryption initial round is used to perform an exclusive - OR operation on the plaintext data and the first round key to obtain the first state matrix;

[0106] In the encryption main rounds, the SubBytes (byte substitution) is to substitute each byte in the state using the s - box.

[0107] The ShiftRows (row shift) is to circularly shift the rows of the state matrix. The MixColumns (column mixing) is to perform a linear transformation on the columns of the state matrix.

[0108] The AddRoundKey (round key addition) is to perform an exclusive - OR operation on the state and the round key of the current round.

[0109] The encryption final round is to perform byte substitution and row shift, skip column mixing, and perform round key addition. The decryption initial round is to perform an exclusive - OR operation with the last round key.

[0110] The decryption main rounds include InvShiftRows (inverse row shift) which circularly shifts the rows of the state matrix in the reverse direction, InvSubBytes (inverse byte substitution) which substitutes each byte in the state using the inverse s - box, AddRoundKey (round key addition) which performs an exclusive - OR operation on the state and the round key of the current round, and InvMixColumns (inverse column mixing) which performs an inverse linear transformation on the columns of the state matrix. The decryption final round is to perform inverse row shift and inverse byte substitution, skip inverse column mixing, and perform round key addition.

[0111] More specifically, AES - 256 - GCM, namely the Advanced Encryption Standard, is a symmetric encryption algorithm that is widely used in various fields to protect data confidentiality. 256 represents that the key length is 256 bits. Generally, the longer the key length, the higher the encryption security. GCM (Galois / Counter Mode) is an authenticated encryption mode that can provide data integrity and authentication functions while encrypting. During the encryption process, AES - 256 adopts a block cipher system, and the plaintext data is divided into blocks of a fixed size (usually 128 bits) for encryption. The encryption process includes multiple rounds of operations such as byte substitution, row shift, column mixing, and round key addition. The GCM mode combines the counter mode (CTR) for encryption and Galois field multiplication for authentication. During the encryption process, an authentication tag is generated to verify whether the data has been tampered with during transmission.

[0112] The decryption process is the inverse of encryption. The ciphertext is restored to plaintext through operations such as reverse shift, inverse byte substitution, inverse column mixing, and round key addition. At the same time, the authentication tag is verified to ensure the integrity of the data.

[0113] The RSA-OAEP algorithm is an asymmetric encryption algorithm that combines the RSA algorithm and OAEP padding, used for encrypting data and generating digital signatures. The RSA algorithm is based on the difficulty of factoring large integers, generating a pair of keys, namely the public key and the private key. The public key can be made public and is used to encrypt data; the private key needs to be kept secret and is used to decrypt data.

[0114] When using RSA-OAEP for encryption, first perform OAEP padding on the plaintext data, and then use the recipient's public key to encrypt the padded data. The purpose of OAEP padding is to increase the randomness and security of encryption and prevent some attacks against the RSA algorithm. The recipient uses their own private key to decrypt the ciphertext and then removes the OAEP padding to obtain the original plaintext data.

[0115] In a preferred embodiment, it further includes a power status monitoring module 5, connected to the server-side management module 1 and the device-side update module 2, for monitoring the power status of the device side, determining whether the power status of the device side is higher than a second set threshold. If so, the device side installs the update package; if not, the installation of the update package is suspended, and the current update status is fed back.

[0116] Specifically, the upgrade process consumes a certain amount of power. If the device's power is too low, it will cause the upgrade to be interrupted and damage the device's software system. By monitoring the power status, it is ensured that the device has sufficient power to complete the upgrade, improving the success rate of the upgrade. Avoid performing upgrade operations when the device's power is insufficient to prevent upgrade failure or even damage to the device due to power exhaustion during the upgrade process. At the same time, the update status is promptly fed back to let the user know the upgrade progress.

[0117] More specifically, referring to Figure 9, initialize the device, set the initial parameters of the power state, such as voltage, current, and power thresholds, and initialize the data acquisition module for obtaining real-time power data, regularly collecting voltage, current, and power data from sensors or power management chips. Set the sampling frequency, which is adjusted according to the device type and requirements. Filter the collected data for noise (such as using moving average filtering), check the data integrity, and handle missing data. Compare the collected data with the set thresholds, and use rules or machine learning models to judge the power state (such as normal, low power, overload, power-off). Identify abnormal states (such as too low or too high voltage), record the timestamp and data details of the abnormal events, generate a power state report, and send it to the monitoring system or user interface. Trigger corresponding responses according to the abnormal type (such as alarms, automatic shutdown, switching to backup power). Optimize the thresholds and detection algorithms through historical data analysis to adapt to the usage patterns and environmental changes of the device.

[0118] Refer to Figure 10 , the update process of the present invention includes, first, initializing the device-side system, checking the device connection, and making the device enter the state of preparing for upgrade.

[0119] At the same time, check the network connection of the device and other situations to ensure that the device can communicate with the server normally, providing a basic condition for subsequent operations such as obtaining update packages.

[0120] Then, the device-side checks the current software version and compares it with the server-side: the device-side will read the information of the currently installed software version on itself and then send this information to the server-side. The server-side stores the latest software version data. By comparing the two, it is judged whether the software on the device-side is the latest version. If there is a new version, notify the user or continue automatically: when the version comparison result shows that there is a new version, the system will take two methods. One is to send a notice to the user, informing that there is a new version available for update, and the user decides whether to perform the update operation. Commonly, such as a mobile phone popping up a system update prompt box; the other is that when the user sets it to automatic update, the system directly continues the subsequent update process automatically.

[0121] Secondly, the device downloads the update package from the server, supporting resume from breakpoint. After determining to perform the update, the device downloads the corresponding update package from the server through the network. Considering that the network environment may be unstable, this process supports the resume from breakpoint function. If the network is interrupted during the download, it can continue to download from the breakpoint after the network resumes, without having to start over, saving time and traffic.

[0122] Then, check the integrity and security of the update package (such as checksum verification). After the download is complete, the device will verify the update package. Check whether data loss, corruption, or tampering occurred during the transmission of the update package to ensure the integrity and security of the update package. Only the update package that passes the verification can be used for subsequent installation to prevent installing an unavailable or security-risky version.

[0123] Next, before installing the update package, to avoid data loss or the system being unable to run properly due to problems during the update process, the system will back up the current software and important data. The backed-up data can be stored locally on the device or in the cloud to restore to the state before the update in case of an update failure.

[0124] Then, start installing the update package, and at the same time, the system will monitor the installation progress and status in real time. For example, display the installation percentage and whether there are error messages, etc., so that the user or the system can timely understand the installation situation. If an abnormality occurs during the installation, corresponding measures can be taken in a timely manner.

[0125] Finally, verify the installation: confirm that the update is successful. If it fails, perform a rollback. After the installation is complete, verify again to determine whether the update is successful. If successful, the system can run the new version normally; if it fails, perform a rollback operation, using the previously backed-up data and software to restore the system to the state before the update to prevent the device from being unable to be used normally due to an update failure.

[0126] After the installation is complete, notify the user that the update is complete. To free up storage space on the device, temporary files generated during the update process will be cleaned up, such as the temporary copy of the downloaded update package, etc. The system restarts, loads, and runs the updated new version software to complete the entire automated over-the-air upgrade process, and the device is put into use with new functions or performance states.

[0127] The above are only the preferred embodiments of the present invention, and do not limit the implementation manners and protection scope of the present invention accordingly. For those skilled in the art, it should be realized that any equivalent replacement and obvious changes made by using the description and illustrations of the present invention should be included within the protection scope of the present invention.

Claims

1. An automated over-the-air upgrade method, characterized in that, including Step S1: Obtain the device log of the device end and analyze the keyword frequency in the device log. When the keyword frequency exceeds the first set threshold, send an upgrade request to the server end. Step S2: The server end sends an update package to the device end according to the received upgrade request. Step S3: The device end receives the update package and performs integrity verification. Step S4: Monitor the power state of the device end through the power state monitoring algorithm, and determine whether the power state of the device end is higher than the second set threshold. If so, the device end installs the update package; if not, suspend the installation of the update package and feedback the current update status.

2. The automated over-the-air upgrade method according to claim 1, wherein Step S3 includes: After backing up the current version of the device end, receive the update package sent by the server end, and perform integrity verification on the update package by embedding a version verification data structure and combining with the blockchain.

3. The automated over-the-air upgrade method according to claim 1, characterized in that Step S4 includes: Step S41: Initialize the power state, set the second set threshold, and obtain the power data of the device end in real time. Step S42: Collect the power data of the device end at the first sampling frequency, and perform filtering and preprocessing to obtain the processed data. Step S43: Compare the processed data with the second set threshold, and determine whether the power state of the device end is normal. If so, the device end installs the update package; if not, suspend the installation of the update package, identify the abnormal state of the device end, and feedback the current update status.

4. The automated over-the-air upgrade method according to claim 1, wherein It also includes Step S0: Initialize the device end and perform version detection on the current versions of the device end and the server end.

5. The automated over-the-air upgrade method according to claim 4, wherein It also includes Step S5: Determine whether the update package of the device end is installed successfully. If so, clean up the temporary files generated during the update process of the device end; if not, perform a rollback operation according to the backup data of the device end, and display the update failure reason and rollback result to the user.

6. An automated over-the-air upgrade system, characterized in that, including Server end management module, used to manage and distribute update packages. Device end update module, used to receive and install the update package. Communication module, connecting the server end management module and the device end update module, used to transmit the update package distributed by the server end management module to the device end update module. User interface module, connecting the device end update module, used to display the update status and progress according to the update mode.

7. The automated over-the-air upgrade system according to claim 6, wherein The server end management module includes Version comparison unit, used to obtain and compare the current version information sent by the device end update module to determine the update package to be sent to the device end. Update package sending unit, connecting to the version comparison unit, used to distribute the corresponding update package to the device end according to the upgrade request of the device end.

8. The automated over-the-air upgrade system according to claim 7, characterized in that The device end update module includes Current version detection unit, used to detect the current version of the device end. By obtaining the device log of the device end and analyzing the keyword frequency in the device log, when the keyword frequency exceeds the first set threshold, send an upgrade request to the server end. The integrity verification unit is connected to the server - side management module and verifies the integrity of the update package by embedding a version verification data structure in the update package and combining with the blockchain.

9. The automated over-the-air upgrade system according to claim 6, wherein The communication module includes a data encryption and transmission sub - module, and the data encryption and transmission sub - module includes a key expansion unit for expanding the initial key to obtain the round keys required for different rounds; an encryption initial unit connected to the key expansion unit for performing an exclusive - OR operation on the plaintext data and the first round key to obtain a first state matrix; a main encryption unit connected to the encryption initial unit for sequentially performing byte substitution, row shift, column mixing, and round key addition operations on the first state matrix to obtain a second state matrix; a final encryption unit connected to the main encryption unit for performing byte substitution and row shift on the second state matrix to obtain ciphertext data; a decryption initial unit connected to the final encryption unit for performing an exclusive - OR operation on the received ciphertext data and the last round key to obtain a third state matrix; a main decryption unit connected to the decryption initial unit for sequentially performing reverse row shift, inverse byte substitution, inverse column mixing, and round key addition operations on the third state matrix to obtain the original state data; a final decryption unit connected to the main decryption unit for performing reverse row shift and inverse byte substitution on the original state data to obtain the decrypted plaintext data.

10. The automated over-the-air upgrade system according to claim 7, wherein It further includes a power state monitoring module connected to the server - side management module and the device - side update module for monitoring the power state of the device - side, determining whether the power state of the device - side is higher than a second set threshold. If so, the device - side installs the update package; if not, it pauses the installation of the update package and feedbacks the current update status.

Images