CN115208761A - OTA upgrading system - Google Patents
OTA upgrading system Download PDFInfo
- Publication number
- CN115208761A CN115208761A CN202210621502.0A CN202210621502A CN115208761A CN 115208761 A CN115208761 A CN 115208761A CN 202210621502 A CN202210621502 A CN 202210621502A CN 115208761 A CN115208761 A CN 115208761A
- Authority
- CN
- China
- Prior art keywords
- ota
- upgrading
- server
- upgrade
- upgrade package
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The OTA upgrading system of the invention creates a lightweight upgrading mode with low version compatibility through the communication among the APP terminal, the first server terminal, the second server terminal and the equipment terminal, and can ensure the safety, compatibility and expansibility of the robot to the maximum extent.
Description
Technical Field
The invention relates to the field of program upgrading, in particular to an OTA upgrading system.
Background
The OTA mode of the existing intelligent robot with the slave equipment generally adopts a full-scale upgrading mode, namely, the robot directly and completely downloads the upgrading package into the robot no matter the size of the upgrading package, and the robot judges according to the version of the robot and selectively upgrades the upgrading package (or completely replaces the upgrading package or ignores the version number), so that the intelligent robot can cause a plurality of problems:
1. downloading redundant programs results in increased download processes and thus increased process costs.
2. The whole quantity of installation has reduced installation rate, and has great failure risk, leads to the product to become the brick.
3. The slave devices and the master device do not form a good networking relationship, and are usually independent from each other, and each slave device is an independent master device to be upgraded respectively, so that the risk of upgrading failure is greatly increased.
4. Some incremental upgrading devices do not consider compatibility problems, so that the robots which are delivered in front cannot work compatibly due to long-time non-use or non-upgrading of the robots, and a plurality of subsequent project versions cannot work compatibly.
Disclosure of Invention
In view of the above-mentioned shortcomings of the prior art, it is an object of the present invention to provide an OTA upgrading system for solving the above technical problems in the prior art.
To achieve the above and other related objects, the present invention provides an OTA upgrade system, comprising: the system comprises an APP end, a first server end, a second server end and an equipment end; the APP terminal is in communication connection with the first server terminal and the second server terminal, and is used for acquiring device version information of the device terminal from the first server terminal, judging whether the device terminal needs to be upgraded or not, and issuing corresponding OTA (over the air) upgrade information to the device terminal through the second server terminal under the conditions that the device terminal needs to be upgraded and the upgrade is determined; wherein the device version information includes: the latest version number, the current version number and the upgrade package downloading information; the OTA upgrade information comprises: the latest version number and the upgrade package downloading information; the device end is in communication connection with the first server end and the second server end, and is used for receiving OTA upgrading information sent by the APP end through the second server end and downloading a corresponding OTA upgrading packet from the first server end based on the upgrading packet downloading information when upgrading is judged; performing internal processing and upgrading installation on the OTA upgrading packet, and feeding back an upgrading progress and a downloading progress to the APP terminal through the second server terminal in real time so as to display the upgrading progress and the downloading progress by the APP terminal; wherein, the mode of upgrading installation includes: and the method comprises the steps of installing incremental upgrade corresponding to an incremental OTA upgrade package downloaded from the first server side or installing forced upgrade corresponding to a forced intermediate version upgrade package downloaded from the first server side.
In an embodiment of the present invention, the device side includes: a master device end and at least one slave device end.
In an embodiment of the present invention, the apparatus is configured to receive OTA upgrade information sent by the APP end through the second server end; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; performing internal processing on the OTA upgrade package; when the main equipment end needs upgrading, upgrading and installing are carried out based on an OTA upgrading package which is processed internally, and corresponding upgrading progress and downloading progress are stored in real time; when the slave equipment end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the corresponding slave equipment end; the slave equipment end is used for carrying out upgrading installation when receiving the OTA upgrading packet subjected to internal processing, and sending the corresponding upgrading progress and downloading progress to the master equipment end in real time; the master equipment end is used for summarizing the upgrading progress and the downloading progress of the upgraded master equipment end and the upgraded slave equipment end, and feeding the summarized upgrading progress, the downloading progress and the upgrading result back to the APP end through the second server end so as to display the upgrading progress, the downloading progress and the upgrading result by the APP end.
In an embodiment of the present invention, when the slave device needs to be upgraded, sending the OTA upgrade package subjected to internal processing to the corresponding slave device includes: when the slave device end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the second server end through a 4G or Wifi communication mode so as to be sent to the corresponding slave device end through the second server end; or when the slave device end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the corresponding slave device end in a BT or Zigbee communication mode.
In an embodiment of the present invention, the main device is configured to receive, when an upgrade is needed, OTA upgrade information sent by the APP via the second server; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; performing internal processing and upgrading installation on the OTA upgrading packet, and feeding upgrading progress and downloading progress back to the APP end through the second server end in real time so as to be displayed by the APP end; the slave device end is used for receiving OTA upgrading information sent by the APP end through the second server end when upgrading is needed; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; and the OTA upgrading package is internally processed and upgraded and installed, and the upgrading progress and the downloading progress are fed back to the APP end in real time through the second server end so as to be displayed by the APP end.
In an embodiment of the present invention, the manner of internally processing the OTA upgrade package includes: verifying the integrity of the OTA upgrade package and decompressing the OTA upgrade package.
In an embodiment of the present invention, if the version of the current version number of the device end is not compatible with the version of the latest version number, the APP end obtains, from the first server end, upgrade package download information of the device end, which includes a latest version number corresponding to a mandatory intermediate version as the latest version, the current version number, and a mandatory intermediate version upgrade package corresponding to the mandatory intermediate version, so that the device end downloads, from the first server end, the corresponding mandatory intermediate version upgrade package based on the upgrade package download information and performs a mandatory upgrade installation to make the version of the current version number of the device end compatible with the version of the latest version number; after the forced upgrade is installed, the APP terminal acquires the latest version number and the current version number of the equipment terminal and upgrade package downloading information of the increment OTA upgrade package corresponding to the latest version from the first server terminal, so that the equipment terminal downloads the corresponding increment OTA upgrade package from the first server terminal based on the upgrade package downloading information and performs increment upgrade installation.
In an embodiment of the present invention, if the version of the current version number of the device end is compatible with the version of the latest version number, the APP end obtains the latest version number of the device end, the current version number, and upgrade patch download information of the incremental OTA upgrade patch corresponding to the latest version from the first server end, so that the device end downloads the corresponding incremental OTA upgrade patch from the first server end based on the upgrade patch download information and performs incremental upgrade installation.
In an embodiment of the present invention, the second server includes: MQTT server side or BT server side.
In an embodiment of the present invention, the upgrade package downloading information includes: upgrade package URL address and MD5 value.
As described above, the present invention is an OTA upgrade system, which has the following beneficial effects: according to the invention, through the communication among the APP terminal, the first server terminal, the second server terminal and the equipment terminal, a lightweight upgrading mode with low version compatibility is created, and the safety, compatibility and expansibility of the robot can be ensured to the maximum extent.
Drawings
Fig. 1 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Fig. 2 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Fig. 4 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Fig. 5 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Fig. 6 is a schematic diagram of version upgrade according to an embodiment of the present invention.
Fig. 7 is a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It should be noted that the features in the following embodiments and examples may be combined with each other without conflict.
It should be noted that in the following description, reference is made to the accompanying drawings which illustrate several embodiments of the invention. It is to be understood that other embodiments may be utilized and that mechanical, structural, electrical, and operational changes may be made without departing from the spirit and scope of the present invention. The following detailed description is not to be taken in a limiting sense, and the scope of embodiments of the present invention is defined only by the claims of the issued patent. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Spatially relative terms, such as "upper," "lower," "left," "right," "lower," "below," "lower," "above," "upper," and the like, may be used herein to facilitate describing one element or feature's relationship to another element or feature as illustrated in the figures.
Throughout the specification, when a part is referred to as being "connected" to another part, this includes not only a case of being "directly connected" but also a case of being "indirectly connected" with another element interposed therebetween. In addition, when a certain part is referred to as "including" a certain component, unless otherwise stated, other components are not excluded, but it means that other components may be included.
The terms first, second, third, etc. are used herein to describe various elements, components, regions, layers and/or sections, but are not limited thereto. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the scope of the present invention.
Also, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," and/or "comprising," when used in this specification, specify the presence of stated features, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, operations, elements, components, items, species, and/or groups thereof. The terms "or" and/or "as used herein are to be construed as inclusive or meaning any one or any combination. Thus, "a, B or C" or "a, B and/or C" means "any of the following: a; b; c; a and B; a and C; b and C; A. b and C ". An exception to this definition will occur only when a combination of elements, functions or operations are inherently mutually exclusive in some way.
The invention mainly aims to solve the defects in the current OTA process of the intelligent robot, and creates a lightweight upgrading mode with low version compatibility through the communication among the APP end, the first server end, the second server end and the equipment end from the aspects of cost reduction (flow reduction, downloading time reduction, installation time reduction) and efficiency enhancement (installation speed increase and upgrading risk reduction), so that the safety, compatibility and expansibility of the robot can be ensured to the maximum extent.
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings so that those skilled in the art can easily implement the embodiments of the present invention. The present invention may be embodied in many different forms and is not limited to the embodiments described herein.
Fig. 1 shows a schematic structural diagram of an OTA upgrading system in an embodiment of the present invention.
The system comprises:
the system comprises an APP end 1, a first server end 2, a second server end 3 and an equipment end 4;
the APP end 1 establishes communication connection with the first server end 2 and the second server end 3, and is configured to send a request to the first server end 2 and obtain device version information of the device end from the first server end 2; wherein the device version information includes: the latest version number, the current version number and the download information of the upgrade package; comparing the latest version number with the current version number to judge whether the equipment terminal needs to be upgraded, if so, not needing to be upgraded, and also prompting that the equipment terminal is the latest version; if not, upgrading is needed, and upgrading can be prompted; issuing corresponding OTA upgrading information to the equipment end through the second server end 3 under the condition that upgrading is needed and the upgrading is determined by a user; wherein the device version information includes: the latest version number, the current version number and the upgrade package downloading information; the OTA upgrade information comprises: the latest version number and the upgrade package downloading information;
the device end 4 establishes communication connection with the first server end 2 and the second server end 3, and is used for receiving OTA upgrade information sent by the APP end 1 through the second server end 3, and downloading a corresponding OTA upgrade package from the first server end 2 based on the upgrade package download information when upgradeable is judged; performing internal processing and upgrade installation on the OTA upgrade package, and feeding back the upgrade progress and the download progress of the upgrade package to the APP terminal 1 through the second server terminal 3 in real time so as to display the upgrade progress and the download progress by the APP terminal 1;
wherein, the mode of upgrading installation includes: the method comprises the steps of installing incremental upgrade corresponding to an incremental OTA upgrade package downloaded from the first server end 1 or installing forced upgrade corresponding to a forced intermediate version upgrade package downloaded from the first server end 1.
Optionally, the device side includes: a master device end and at least one slave device end.
Optionally, performing OTA upgrade by taking the main device end as a networking central point; the main equipment end is connected with the first server end and the second server end; the main equipment terminal realizes the following steps:
step (1): and receiving OTA upgrading information sent by the APP terminal through the second server terminal 3. Specifically, the APP end 1 sends the OTA upgrading information to the second server end 3, and then the APP end 3 sends the OTA upgrading information to the main device end 41;
step (2): when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end 2 based on the upgrade package downloading information; specifically, the latest version number in the received download information of the upgrade package is compared with the current version number of the equipment end, if the latest version number is inconsistent with the current version number of the equipment end, the equipment end can be upgraded, and if the latest version number is not upgraded all the time; and when the equipment end is judged to be upgradable, downloading the corresponding OTA upgrade package from the first server end 2 based on the upgrade package downloading information.
And (3): performing internal processing on the OTA upgrade package; preferably, the internal processing mode of the OTA upgrade package includes: verifying the integrity of the OTA upgrade package and decompressing the OTA upgrade package if verified as complete.
And (4): when the main equipment end needs upgrading, upgrading installation is carried out based on the OTA upgrading packet which is processed internally, and the corresponding upgrading progress and the downloading progress are stored in real time; when the slave equipment end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the corresponding slave equipment end, and when the slave equipment end receives the OTA upgrade package subjected to internal processing, the slave equipment end carries out upgrade installation and sends the corresponding upgrade progress and download progress to the master equipment end in real time;
and (5): summarizing the upgrading progress and the downloading progress of the upgrading master equipment end and the upgrading progress and the downloading progress of the slave equipment end, obtaining an upgrading result, and feeding the summarized upgrading progress, downloading progress and upgrading result back to the APP end 1 through the second server end 3 so as to be displayed by the APP end 1. It should be noted that the upgrade result includes an upgrade success result and an upgrade failure result; if all the upgrades are successful, the upgrade result is a successful upgrade result, and if not, the upgrade result is a failure result.
Optionally, when the slave device needs to be upgraded, sending the OTA upgrade package subjected to internal processing to the corresponding slave device includes:
as shown in fig. 2, the master device 41 is connected to the first server 2 and the second server 3; the slave device end 42 is connected to the second server end 3, and when the slave device end 42 needs to be upgraded, the internally processed OTA upgrade package is sent to the second server end 3 through a 4G or Wifi communication mode, so that the internally processed OTA upgrade package is sent to the corresponding slave device end 42 through the second server end 3;
alternatively, the first and second electrodes may be,
as shown in fig. 3, the master device side 41 is connected to the first server side 2, the second server side 3 and the slave device side 42; when the slave device 42 needs to be upgraded, the internally processed OTA upgrade package is sent to the corresponding slave device 42 through BT or Zigbee communication. In the method, the master device and the slave device form a star network, and upgrade packet data is sent to the slave device through a BT/Zigbee channel by taking the master device as a center.
Optionally, all the master device side and the slave device side have their own networking modules, or wifi or 4G modules. As shown in fig. 4, the master device 41 is connected to the first server 2 and the second server 3; the slave device 41 is connected to the first server 2 and the second server 3;
the main device terminal 41 is configured to receive, when upgrading is needed, OTA upgrading information sent by the APP terminal 1 through the second server terminal 3; the information is not received when the upgrade is not needed; comparing the latest version number in the received download information of the upgrade package with the current version number of the equipment end, if the latest version number is inconsistent with the current version number of the equipment end, the equipment end can be upgraded, and if the latest version number is not upgraded all the time; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end 2 based on the upgrade package downloading information; performing internal processing and upgrade installation on the OTA upgrade package, and feeding back an upgrade progress and a download progress to the APP terminal 1 in real time through the second server terminal 3 so as to display the upgrade progress and the download progress by the APP terminal 1; the slave device end 42 is configured to receive OTA upgrade information sent by the APP end 1 through the second server end 2 when upgrade is required, and does not receive the OTA upgrade information when upgrade is not required; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end 2 based on the upgrade package downloading information; the OTA upgrade package is subjected to internal processing and upgrade installation, and the upgrade progress and the download progress are fed back to the APP end 1 in real time through the second server end 2, so that the APP end 1 can display the upgrade progress and the download progress.
Optionally, if the version of the current version number of the device end 4 is not compatible with the version of the latest version number, the APP end 1 obtains, from the first server end 2, upgrade package download information of the device end 4, which includes the latest version number corresponding to the latest version of the mandatory intermediate version compatible with the latest version, the current version number, and a mandatory intermediate version upgrade package corresponding to the mandatory intermediate version, so that the device end 4 receives OTA upgrade information sent by the APP end 1 through the second server end 3, and downloads the corresponding mandatory intermediate version upgrade package from the first server end 2 based on the upgrade package download information when it is determined that the OTA upgrade is possible; carrying out internal processing on the forced intermediate version upgrading packet and carrying out forced upgrading installation to make the version of the current version number of the equipment end compatible with the version of the latest version number; the upgrading progress and the downloading progress are fed back to the APP terminal 1 through the second server terminal in real time so that the APP terminal 1 can display the upgrading progress and the downloading progress; the forced OTA packet is of a permanent type, namely, the pushed forced OTA can be received whenever the robot is connected with the Server at any time and any place, and the equipment judges whether to be upgraded or not according to the equipment;
after the forced upgrade is installed, the APP end 1 obtains the latest version number and the current version number of the device end and upgrade package download information of the increment OTA upgrade package corresponding to the latest version from the first server end, so that the device end 4 downloads the corresponding increment OTA upgrade package from the first server end 2 based on the upgrade package download information and performs the increment upgrade installation.
Optionally, if the version of the current version number of the device end 4 is compatible with the version of the latest version number, the APP end 1 obtains the latest version number of the device end, the current version number, and upgrade patch download information of the incremental OTA upgrade patch corresponding to the latest version from the first server end 2, so that the device end 4 downloads the corresponding incremental OTA upgrade patch from the first server end 2 based on the upgrade patch download information and performs incremental upgrade installation.
By the method, the problem of increment flow saving is solved, the problem that the increment cannot be compatible is solved, and each upgrade is lighter and is not easy to make mistakes.
Optionally, the system adopts an incremental upgrade mode, that is, which program needs to be upgraded, and the server only packs an upgrade package of the program into a fixed ota.bin form; the method comprises the steps of directly executing the OTA.bin file without operations such as decompression and the like after the device side downloads and verifies successfully, wherein the specific execution steps of the bin file are determined by a script contained in the bin file, namely the upgrade ownership of the OTA package is completely handed over to a bin file generation person (development engineer), so that the requirements of addition, deletion, replacement and the like in any modes can be met.
Optionally, the second server includes: MQTT server side or BT server side.
Optionally, the upgrade package downloading information includes: upgrade package URL address and MD5 value. Specifically, the device end downloads a corresponding OTA upgrade package from a first server end connected with the device end based on the URL address of the upgrade package; the method for judging whether the upgrade is available comprises the following steps: and detecting whether the MD5 value of the current equipment is consistent with the MD5 value in the upgrade package downloading information.
To better illustrate the OTA upgrade system described above, the present invention provides the following specific embodiments.
Example 1: an OTA upgrade system. FIG. 5 is a schematic diagram of the system;
the system comprises: APP, server, MQTT, a mower (main equipment end) and a charging pile (slave equipment end);
(1) and after the APP enters an upgrading interface, acquiring the latest version number and the current version number of the current equipment from the Server.
(2) The APP compares whether the current version and the latest version are the same, the same prompt is 'the latest version', and otherwise, the prompt can be upgraded.
(3) After the user clicks upgrading, the APP issues OTA information, including: the latest version number, md5 value of the OTA package, URL of the OTA package download, etc.
(4) The APP pushes the OTA information to main equipment to be upgraded through the MQTT, and after the main equipment receives the OTA information, upgrade judgment (secondary verification) is carried out.
(5) The main equipment downloads the OTA upgrade package from the Server through https according to the URL of the OTA information;
(6) the main device performs internal processing on the OTA upgrade package: verifying the integrity of the packet, decompressing the OTA packet, judging whether the slave equipment needs to be upgraded or not, and jumping to the step (7); otherwise, jumping to step (9).
(7) At the moment, multiple modes can be selected according to the hardware support type of the master device and the slave device;
1) 4G/Wifi, because it can connect to Server, the master device can send the upgrade package of the slave device in the form of byte stream through MQTT.
2) BT/Zigbee, the master device and the slave device form a star network, and the master device is taken as the center, and through a BT/Zigbee channel,
and transmitting the upgrade package data to the slave device.
(8) And after receiving the upgrade package, the slave equipment carries out upgrade, and feeds back progress information to the master equipment in real time in the downloading/upgrading process.
(9) And (3) informing the upgrading result to the main equipment (through MQTT/BT) when the upgrading of the slave equipment is successful/failed, and feeding back the result to the APP after the main equipment summarizes the result (namely, even if one equipment is not upgraded successfully, the success declares the failure).
And displaying the upgrading result, success or failure (displaying the failure reason) of the APP at the R (R).
The upgrade package adopts an increment form to upgrade, if the current total number of 3 programs is 3, only 1-2 programs may need to be upgraded each time, all the program upgrade packages are not required to be packaged at the moment, the flow is wasted, and the following mode is adopted for the increment upgrade:
and (4) an incremental upgrading mode is adopted, namely which program needs to be upgraded, only the upgrading packet of the program is packaged into a fixed OTA.
Bin files are directly executed after the device side succeeds in downloading and verification, operations such as decompression and the like are not needed, specific execution steps of the bin files are determined by scripts contained in the bin files, namely the upgrade ownership of the OTA package is completely handed over to a bin file generation person (development engineer), and therefore the requirements of adding, deleting, replacing and the like in any mode can be met.
Incremental upgrading, which is to say that the latest version is no longer compatible with the latest version (the default user follows the upgrading every time), but the actual user may not follow the upgrading, as shown in fig. 6, assuming that the user is in the state where the latest version of the original version is n, the middle iteration is performed on multiple generations of OTA such as 1-m, and the latest version is only added with a forced upgrading OTA packet (full packet) below the compatible line when the program B and the program C are incrementally released, i.e. the part above the compatible line is to be upgraded to the latest version, the forced OTA upgrading step must be performed first, and the upgrading is continued to the latest version after the upgrading is completed.
The incremental updating packet of the embodiment is inserted with the full-scale forced OTA packet, the forced OTA packet is in a permanent type, namely, the pushed forced OTA can be received whenever the robot is connected with the Server, and the equipment judges whether to be updated according to the equipment. The device roles are divided into a master device and a slave device, the master device is responsible for coordinating all OTA packages, processes and the like, the slave devices only act according to instructions of the master device, multiple requests to a plurality of servers are avoided, the APP is also prevented from being upgraded by clicking once for each slave device, and the compatibility and the comprehensiveness of the upgrade are improved.
Example 2: an OTA upgrade system. FIG. 6 is a schematic diagram of the system;
the system comprises: the system comprises an APP, a Server, an MQTT, a master device and a slave device end; each device is provided with its own networking module, or wifi or 4G module.
(1) And after the APP enters an upgrading interface, acquiring the latest version number and the current version number of the current equipment from the Server.
(2) Comparing whether the current version is the same as the latest version, the same prompt is 'the latest version', otherwise, the prompt can be upgraded.
(3) After the user clicks the upgrade, the APP issues OTA information, including: the latest version number, md5 value of the OTA package, URL of the OTA package download, etc.
(4) And pushing the OTA information to the equipment to be upgraded (without so-called master-slave) through the MQTT, and judging the upgrade (performing secondary verification) after the equipment to be upgraded receives the OTA information.
(5) And the equipment to be upgraded downloads the OTA upgrade package from the Server end through https according to the URL of the OTA information.
(6) Performing internal processing on the OTA upgrade package: and verifying the integrity of the package, decompressing the OTA package and upgrading.
(7) And feeding back the upgrading state in real time during/after upgrading for APP display.
In summary, the OTA upgrading system of the present invention creates a lightweight upgrading method with low version compatibility through communication among the APP end, the first server end, the second server end and the device end, and can ensure safety, compatibility and expansibility of the robot to the maximum extent. Therefore, the invention effectively overcomes various defects in the prior art and has high industrial utilization value.
The foregoing embodiments are merely illustrative of the principles of the present invention and its efficacy, and are not to be construed as limiting the invention. Those skilled in the art can modify or change the above-described embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention are covered by the claims of the present invention.
Claims (10)
1. An OTA upgrade system, the system comprising:
the system comprises an APP end, a first server end, a second server end and an equipment end;
the APP terminal is in communication connection with the first server terminal and the second server terminal, and is used for acquiring device version information of the device terminal from the first server terminal, judging whether the device terminal needs to be upgraded or not, and issuing corresponding OTA (over the air) upgrade information to the device terminal through the second server terminal under the conditions that the device terminal needs to be upgraded and the upgrade is determined; wherein the device version information includes: the latest version number, the current version number and the upgrade package downloading information; the OTA upgrading information comprises: the latest version number and the upgrade package downloading information;
the device end is in communication connection with the first server end and the second server end, and is used for receiving OTA upgrading information sent by the APP end through the second server end and downloading a corresponding OTA upgrading packet from the first server end based on the upgrading packet downloading information when upgrading is judged; performing internal processing and upgrading installation on the OTA upgrading packet, and feeding back the upgrading progress and the downloading progress to the APP end through the second server end in real time so as to display the upgrading progress and the downloading progress by the APP end;
wherein, the mode of upgrading installation includes: and the method comprises the steps of installing incremental upgrade corresponding to an incremental OTA upgrade package downloaded from the first server side or installing forced upgrade corresponding to a forced intermediate version upgrade package downloaded from the first server side.
2. The OTA upgrade system of claim 1, wherein the device side comprises: a master device end and at least one slave device end.
3. The OTA upgrade system according to claim 2, wherein the main device is configured to receive OTA upgrade information sent by the APP via the second server; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; performing internal processing on the OTA upgrade package; when the main equipment end needs upgrading, upgrading and installing are carried out based on an OTA upgrading package which is processed internally, and corresponding upgrading progress and downloading progress are stored in real time; when the slave equipment end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the corresponding slave equipment end; the slave equipment end is used for carrying out upgrading installation when receiving the OTA upgrading packet subjected to internal processing, and sending the corresponding upgrading progress and downloading progress to the master equipment end in real time; the main equipment end is used for summarizing the upgrading progress and the downloading progress of the upgrading main equipment end and the upgrading progress of the slave equipment end, and the summarized upgrading progress, the downloading progress and the upgrading result are fed back to the APP end through the second server end so that the APP end can display the result.
4. The OTA upgrade system according to claim 3, wherein the sending the internally processed OTA upgrade package to the corresponding slave device when the slave device needs to be upgraded comprises:
when the slave equipment end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the second server end in a 4G or Wifi communication mode so as to be sent to the corresponding slave equipment end through the second server end;
alternatively, the first and second electrodes may be,
when the slave equipment end needs to be upgraded, the OTA upgrade package subjected to internal processing is sent to the corresponding slave equipment end in a BT or Zigbee communication mode.
5. The OTA upgrade system according to claim 2, wherein the main device is configured to receive OTA upgrade information sent by the APP via the second server when an upgrade is required; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; performing internal processing and upgrading installation on the OTA upgrading packet, and feeding upgrading progress and downloading progress back to the APP end through the second server end in real time so as to be displayed by the APP end; the slave device end is used for receiving OTA upgrading information sent by the APP end through the second server end when upgrading is needed; when the equipment end is judged to be upgradable, downloading a corresponding OTA upgrade package from the first server end based on the upgrade package downloading information; and carrying out internal processing and upgrading installation on the OTA upgrading packet, and feeding upgrading progress and downloading progress back to the APP end in real time through the second server end so as to display the APP end.
6. An OTA upgrade system according to claim 3 or 5 wherein said means for internally processing said OTA upgrade package comprises: verifying the integrity of the OTA upgrade package and decompressing the OTA upgrade package.
7. The OTA upgrading system according to claim 1, wherein if the version of the current version number of the device end is incompatible with the version of the latest version number, the APP end obtains, from the first server end, the upgrade package download information of the device end including the latest version number corresponding to the latest version, the current version number, and the mandatory intermediate version upgrade package corresponding to the mandatory intermediate version, which is a mandatory intermediate version, so that the device end downloads the corresponding mandatory intermediate version upgrade package from the first server end based on the upgrade package download information and performs the mandatory upgrade installation to make the version of the current version number of the device end compatible with the version of the latest version number;
after the forced upgrade is installed, the APP terminal acquires the latest version number and the current version number of the equipment terminal and upgrade package downloading information of the increment OTA upgrade package corresponding to the latest version from the first server terminal, so that the equipment terminal downloads the corresponding increment OTA upgrade package from the first server terminal based on the upgrade package downloading information and performs increment upgrade installation.
8. The OTA upgrading system according to claim 1, wherein if the version of the current version number of the device side is compatible with the version of the latest version number, the APP side obtains the latest version number of the device side, the current version number, and the upgrade package download information of the incremental OTA upgrade package corresponding to the latest version from the first server side, so that the device side downloads the corresponding incremental OTA upgrade package from the first server side based on the upgrade package download information and performs incremental upgrade installation.
9. The OTA upgrading system according to claim 1, wherein the second server side comprises: MQTT server side or BT server side.
10. The OTA upgrade system of claim 1, wherein the upgrade package download information comprises: upgrade package URL address and MD5 value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210621502.0A CN115208761A (en) | 2022-06-01 | 2022-06-01 | OTA upgrading system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210621502.0A CN115208761A (en) | 2022-06-01 | 2022-06-01 | OTA upgrading system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115208761A true CN115208761A (en) | 2022-10-18 |
Family
ID=83575912
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210621502.0A Pending CN115208761A (en) | 2022-06-01 | 2022-06-01 | OTA upgrading system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115208761A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116232766A (en) * | 2023-05-06 | 2023-06-06 | 中国第一汽车股份有限公司 | OTA-based data encryption system and method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106843946A (en) * | 2017-01-04 | 2017-06-13 | 努比亚技术有限公司 | A kind of firmware update and terminal |
| CN107580071A (en) * | 2017-09-28 | 2018-01-12 | 美的智慧家居科技有限公司 | Master-slave equipment upgrade method, device and its equipment |
| CN108469960A (en) * | 2017-07-28 | 2018-08-31 | 新华三技术有限公司 | A kind of method for edition management and device |
| CN111901142A (en) * | 2020-06-17 | 2020-11-06 | 厦门亿联网络技术股份有限公司 | Firmware silent upgrading method and device for embedded equipment cluster |
| EP3982253A1 (en) * | 2020-10-09 | 2022-04-13 | Beijing Xiaomi Mobile Software Co., Ltd. | Terminal software upgrade method, terminal software upgrade apparatus and storage medium |
| CN114466098A (en) * | 2022-01-19 | 2022-05-10 | 上海黑眸智能科技有限责任公司 | OTA (over the air) upgrading method, system, equipment terminal and APP terminal based on APP interaction |
-
2022
- 2022-06-01 CN CN202210621502.0A patent/CN115208761A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106843946A (en) * | 2017-01-04 | 2017-06-13 | 努比亚技术有限公司 | A kind of firmware update and terminal |
| CN108469960A (en) * | 2017-07-28 | 2018-08-31 | 新华三技术有限公司 | A kind of method for edition management and device |
| CN107580071A (en) * | 2017-09-28 | 2018-01-12 | 美的智慧家居科技有限公司 | Master-slave equipment upgrade method, device and its equipment |
| CN111901142A (en) * | 2020-06-17 | 2020-11-06 | 厦门亿联网络技术股份有限公司 | Firmware silent upgrading method and device for embedded equipment cluster |
| EP3982253A1 (en) * | 2020-10-09 | 2022-04-13 | Beijing Xiaomi Mobile Software Co., Ltd. | Terminal software upgrade method, terminal software upgrade apparatus and storage medium |
| CN114466098A (en) * | 2022-01-19 | 2022-05-10 | 上海黑眸智能科技有限责任公司 | OTA (over the air) upgrading method, system, equipment terminal and APP terminal based on APP interaction |
Non-Patent Citations (2)
| Title |
|---|
| DAVID-SELA: "OTA Updates for Remote Devices – Different Methods Explained", Retrieved from the Internet <URL:https://jfrog.com/connect/post/ota-updates-for-remote-devices-different-methods-explained/> * |
| 王豫新;高美凤;: "一种改进的固件增量更新算法", 计算机工程, no. 10 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116232766A (en) * | 2023-05-06 | 2023-06-06 | 中国第一汽车股份有限公司 | OTA-based data encryption system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110659049A (en) | OTA (over the air) upgrading method and terminal equipment for automatic driving vehicle | |
| CN107332932B (en) | Robot system remote upgrading method based on FOTA | |
| CN1207928C (en) | Method for processing information in honeycomb base station system | |
| EP2878140B1 (en) | Wireless firmware upgrades to an alarm security panel | |
| US20070294686A1 (en) | Program upgrade system and method for ota-capable device | |
| CN105867973A (en) | Loading method and system for so file in application program | |
| CN112104501A (en) | Remote software upgrading method for agricultural machinery subsoiling Internet of things terminal equipment | |
| CN105808278A (en) | Client version upgrading method and device | |
| CN113946358A (en) | Automatic driving vehicle software remote upgrading method based on vehicle management system | |
| US20050149923A1 (en) | System update protocol | |
| CN113590164B (en) | Method and system for upgrading software of whole vehicle controller | |
| CN105260209A (en) | Hot-update solution of program | |
| CN115208761A (en) | OTA upgrading system | |
| CN105808273A (en) | Software upgrading method and software upgrading device | |
| CN109857423A (en) | Program version update method, device, server and readable storage medium storing program for executing | |
| CN106020882A (en) | Application upgrading method, intelligent terminal and upgrading system | |
| CN110647337A (en) | Internet of things MCU (microprogrammed control Unit) air firmware upgrading method | |
| CN110233906A (en) | A kind of OTA Engine Version update method and system, storage medium and OTA terminal | |
| CN113961224B (en) | Android-terminal-based application program updating method and system | |
| CN114090050A (en) | Robot software remote automatic updating method, system and related products | |
| CN114691174A (en) | Vehicle-mounted software upgrading method, device and equipment | |
| CN105511926A (en) | Vehicle-mounted remote downloading device based on CDMA and upgrade method thereof | |
| CN113434164A (en) | Method and system for updating configuration of setting item cloud of vehicle-mounted entertainment host | |
| CN104601708A (en) | Vehicle-mounted device and multi-channel loading method thereof | |
| CN113672262B (en) | Automatic upgrading method of linux terminal system |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230712 Address after: 518000 B101, B201, B301, B401, B501, B601, b701, b801, building 4, No. 7 industrial zone, heshuikou community, Matian street, Guangming District, Shenzhen, Guangdong Applicant after: SHENZHEN HUAXIN INFORMATION TECHNOLOGY CO.,LTD. Address before: Room 303, 22 Boxia Road, China (Shanghai) pilot Free Trade Zone, Pudong New Area, Shanghai, 201203 Applicant before: Shanghai black eye Intelligent Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right |