OTA upgrading method, device and equipment and computer storage medium

By selecting priority upgrade nodes and broadcasting upgrade notifications from a central server, the problems of low efficiency and high cost of OTA upgrades in existing technologies are solved, achieving an efficient and stable upgrade process and reducing performance and security risks to the system.

CN121509980APending Publication Date: 2026-02-10CHINA MOBILEHANGZHOUINFORMATION TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411092358.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-08
Publication Date
2026-02-10

AI Technical Summary

Technical Problem

Existing OTA upgrade methods suffer from low upgrade efficiency and high costs. In particular, when a large number of terminal devices are upgraded simultaneously, they put computational and download pressure on the central server, affecting upgrade efficiency and increasing system security risks.

Method used

The central server randomly selects a subset of nodes as priority upgrade nodes. After the priority upgrade nodes complete the upgrade, they broadcast an upgrade notification. Other nodes in the same network segment then obtain upgrade data packets from the priority upgrade nodes to perform their upgrades. This approach distributes the load on the central server, reduces data transmission latency, and avoids network security issues.

Benefits of technology

It improves the efficiency of OTA upgrades, reduces system performance requirements and hardware and software costs, avoids high-concurrency downloads, and ensures the stability and security of the upgrade process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121509980A_ABST
    Figure CN121509980A_ABST
Patent Text Reader

Abstract

The invention discloses an OTA upgrading method, device and equipment and a computer storage medium, and belongs to the field of Internet of Things. The embodiment of the invention provides an OTA upgrading method, which is applied to a system, the system comprises a central server, a first node and a second node, and the first node and the second node are nodes in the same network segment; the method comprises the steps that a central server sends an upgrade notification to a first node, and the first node is a node randomly selected by the central server; the first node obtains an upgrade data packet from the central server according to the upgrade notification, and completes the upgrade of the first node based on the upgrade data packet; the first node broadcasts an upgrade notification; when the second node receives the upgrade notification, the second node obtains the upgrade data packet from the first node, and completes the upgrade of the second node based on the upgrade data packet, thereby improving the OTA upgrade efficiency, and reducing the OTA upgrade input cost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of Internet of Things (IoT), and in particular relates to an OTA upgrade method, apparatus, device, computer-readable storage medium, and computer program product. Background Technology

[0002] Over-the-Air (OTA) technology originated from mobile phone networks and enables remote management and updates of programs and data via mobile communication networks or other internet-connected networks. Compared to traditional firmware updates, OTA updates can be completed directly online on the device, requiring only a mobile network or Wi-Fi connection.

[0003] In existing technologies, OTA upgrades for terminal devices are mainly completed through device self-test upgrades or server-initiated upgrades. There are two main interaction schemes for the upgrade process. The first scheme involves direct interaction between the terminal device and the central server. However, when too many terminal devices are being upgraded simultaneously, it puts significant computational and download pressure on the central server, affecting upgrade efficiency and increasing system security risks. The second scheme involves introducing edge computing gateways to build an edge storage network. During upgrades, terminal devices only interact with the edge gateway, distributing the load on the central server. However, this scheme increases hardware, software, and maintenance costs significantly. Therefore, existing OTA upgrade methods suffer from low upgrade efficiency and high investment costs. Summary of the Invention

[0004] This application provides an OTA upgrade method, apparatus, device, computer-readable storage medium, and computer program product, which can improve OTA upgrade efficiency and reduce OTA upgrade investment costs.

[0005] In a first aspect, embodiments of this application provide an OTA upgrade method applied to a system, the system including a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the method includes:

[0006] The central server sends an upgrade notification to the first node, which is a node randomly selected by the central server.

[0007] The first node obtains the upgrade data packet from the central server according to the upgrade notification, and completes the upgrade of the first node based on the upgrade data packet;

[0008] The first node broadcasts an upgrade notification;

[0009] Upon receiving an upgrade notification, the second node obtains the upgrade data packet from the first node and completes the upgrade of the second node based on the upgrade data packet.

[0010] In one feasible implementation, the method further includes, before the central server sends an upgrade notification to the first node:

[0011] The central server broadcasts the first message, which is then used by the nodes that receive the first message to send a response message to the central server. The response message includes the time when the first message was received.

[0012] When the central server receives a response message, it selects the first node as the first node based on the time it received the first message.

[0013] In one feasible implementation, upon receiving an upgrade notification, the second node obtains upgrade data from the first node and completes the upgrade of the second node based on the upgrade data packet, including:

[0014] Upon receiving the upgrade notification, the second node sends a download request to the first node;

[0015] When the first node receives a download request, it prioritizes responding to the download request received first based on its capacity and sends an upgrade data packet to the second node with the required capacity. The second node that receives the upgrade data packet completes the upgrade based on the upgrade data packet.

[0016] In one feasible implementation, after the second node receives the upgrade data packet and completes the upgrade of the second node based on the upgrade data packet, the method further includes:

[0017] The first node and / or the second node that has completed the upgrade broadcast the upgrade notification;

[0018] If a second node that has not completed the upgrade receives an upgrade notification, the second node that has not completed the upgrade obtains the upgrade data packet from the first node corresponding to the received upgrade notification or from the second node that has completed the upgrade, and completes the upgrade of the second node that has not completed the upgrade based on the upgrade data packet.

[0019] In one feasible implementation, the method further includes:

[0020] Upon receiving the upgrade notification, the second node sends the upgrade progress to the central server.

[0021] Secondly, embodiments of this application provide an OTA upgrade method applied to a system, the system including a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the method includes:

[0022] The central server sends an upgrade notification to the first node;

[0023] The first node obtains the upgrade data packet from the central server based on the upgrade notification and broadcasts the upgrade notification.

[0024] Upon receiving an upgrade notification, the second node obtains the upgrade data packet from the first node, completes the upgrade of the second node based on the upgrade data packet, and sends the upgrade progress to the first node.

[0025] Once the second node upgrade is complete, the first node completes its own upgrade based on the upgrade data packet.

[0026] In one feasible implementation, the method further includes:

[0027] Within a preset time period, the first node sends the upgrade progress data received by the first node from the second node to the central server.

[0028] In one feasible implementation, before the central server sends an upgrade notification to the first node, the method includes:

[0029] The central server selects the first node according to a preset ratio, which is the ratio of the number of first nodes to the number of second nodes.

[0030] In one feasible implementation, after the first node completes its upgrade based on the upgrade data packet, once the second node upgrade is complete, the method further includes:

[0031] The central server calculates the upgrade success rate of the second node;

[0032] If the upgrade success rate is less than the target threshold, the first node is determined to be the third node. The proportion of the third node being selected as the first node by the central server is lower than that of other nodes in the same network segment.

[0033] In one feasible implementation, the method further includes:

[0034] The first node detects the status of the first node and the second node;

[0035] If the second node is in a faulty state, the first node deletes the second node;

[0036] If the first node is in a faulty state, the second node broadcasts an election message to the first node. The first node that receives the election message then sends a response message to the corresponding second node. If the number of response messages received by the second node is greater than the target value, the second node that receives more response messages than the target value becomes the first node. The first node in a faulty state becomes the second node. The target value is half the number of first nodes.

[0037] Thirdly, embodiments of this application provide an OTA upgrade device applied to a system, the system including a central server, a first node, and a second node, the first node and the second node being nodes within the same network segment; the device includes:

[0038] The sending module is used by the central server to send upgrade notifications to the first node, where the first node is a node randomly selected by the central server.

[0039] The acquisition module is used by the first node to obtain the upgrade data packet from the central server according to the upgrade notification, and to complete the upgrade of the first node based on the upgrade data packet;

[0040] The broadcast module is used by the first node to broadcast upgrade notifications.

[0041] The acquisition module is also used to enable the second node to obtain upgrade data from the first node and complete the upgrade of the second node based on the upgrade data packet when the second node receives an upgrade notification.

[0042] Fourthly, embodiments of this application provide an OTA upgrade device applied to a system, the system including a central server, a first node, and a second node, the first node and the second node being nodes within the same network segment; the device includes:

[0043] The sending module is used by the central server to send upgrade notifications to the first node.

[0044] The acquisition module is used by the first node to obtain the upgrade data packet from the central server based on the upgrade notification and broadcast the upgrade notification.

[0045] The acquisition module is also used to, when the second node receives an upgrade notification, obtain the upgrade data packet from the first node, complete the upgrade of the second node based on the upgrade data packet, and send the upgrade progress to the first node;

[0046] The acquisition module is also used to enable the first node to complete its upgrade based on the upgrade data packet when the second node has completed its upgrade.

[0047] Fifthly, embodiments of this application provide an electronic device, the device including: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the OTA upgrade method as described in any of the embodiments of the first and second aspects.

[0048] Sixthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the OTA upgrade method as described in either the first or second aspect.

[0049] In a seventh aspect, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform an OTA upgrade method as described in either the first or second aspect.

[0050] This application provides an OTA upgrade method applied to a system. The system includes a central server, a first node, and a second node, which are nodes within the same network segment. The OTA upgrade method includes: the central server sending an upgrade notification to the first node, wherein the first node is a node randomly selected by the central server; the first node obtaining an upgrade data packet from the central server according to the upgrade notification, and completing the upgrade based on the upgrade data packet. By prioritizing the upgrade of a subset of nodes (i.e., the first nodes), the pressure on the central server to connect to the upgrade device is reduced. After the first node completes its upgrade, it broadcasts an upgrade notification. Upon receiving the upgrade notification, the second node within the same network segment obtains upgrade data from the first node and completes its upgrade based on the upgrade data packet. By having multiple first nodes randomly selected by the central server simultaneously send upgrade data packets to un-upgraded second nodes within the same network segment, the pressure on the central server to connect to the upgrade device is distributed, data transmission latency is reduced, the upgrade efficiency of OTA is improved, and network security issues caused by cross-network segment transmission are avoided. Attached Figure Description

[0051] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 This is a diagram of an OTA upgrade architecture based on edge computing from a central server in existing technologies;

[0053] Figure 2 This application provides a diagram of a device self-organizing OTA upgrade system according to one embodiment;

[0054] Figure 3 This is a flowchart illustrating an embodiment of an OTA upgrade method provided in this application;

[0055] Figure 4 This application provides a diagram of a device self-organizing OTA upgrade system according to another embodiment;

[0056] Figure 5 This is a flowchart illustrating an OTA upgrade method provided in another embodiment of this application;

[0057] Figure 6This is a schematic diagram of the structure of an OTA upgrade device provided in one embodiment of this application;

[0058] Figure 7 This is a schematic diagram of the structure of an OTA upgrade device provided in another embodiment of this application;

[0059] Figure 8 This is a schematic diagram of the hardware structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0060] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0061] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0062] Over-the-Air (OTA) technology originated from mobile phone networks and enables remote management and updates of programs and data via mobile communication networks or other internet-connected networks. Compared to traditional firmware updates, OTA upgrades can be completed directly online on the terminal device, requiring only a mobile network or Wi-Fi connection. A central server is a server that provides storage, verification, transmission, monitoring, and scheduling services during the OTA upgrade process. The central server may include an OTA management platform, a task scheduling platform, an anomaly monitoring platform, a device library, and a firmware library.

[0063] In existing technologies, OTA upgrades for terminal devices are mainly completed through device self-test upgrades or server-initiated upgrades. There are two main interaction schemes for the upgrade process. The first scheme involves direct interaction between the terminal device and a central server. However, when too many terminal devices are being upgraded simultaneously, it puts significant computational and download pressure on the central server. The central server's limited bandwidth can cause some devices to download firmware upgrade packages slowly, affecting the upgrade progress and even causing the file server to crash. This can lead to devices not upgrading in a timely manner or experiencing slow progress, potentially resulting in functional and security risks, and also impacting user experience. Figure 1 As shown in the OTA upgrade architecture diagram based on central server edge computing, the second approach involves introducing an edge computing gateway to build an edge storage network, thereby distributing the load on the central server. During device upgrades, interaction is limited to the edge gateway, including exchanging upgrade commands, downloading firmware upgrade packages, and reporting upgrade progress. While this method can alleviate the load pressure during large-scale upgrades, building an edge gateway typically incurs significant hardware, software, and maintenance costs. Furthermore, ensuring consistency and synchronization between the central server and the edge side is crucial. Therefore, existing OTA upgrade methods suffer from low upgrade efficiency and high investment costs.

[0064] To address the problems of the prior art, embodiments of this application provide an OTA upgrade method, apparatus, device, computer-readable storage medium, and computer program product.

[0065] This application provides two OTA upgrade methods, such as... Figure 2 and Figure 3 ,as well as Figure 4 and Figure 5 As shown in the accompanying drawings, the OTA upgrade method provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0066] The first OTA upgrade method is as follows: Figure 2 and Figure 3 , Figure 2 This embodiment illustrates a diagram of a device self-organizing OTA upgrade system. Figure 3 A flowchart illustrating an embodiment of the OTA upgrade method provided in this application is shown.

[0067] like Figure 2 The OTA upgrade system shown includes a central server, a core network, an access network, and a cluster of OTA devices across multiple network segments, where each network segment is a local area network (LAN). Each LAN segment includes a first node and a second node, both located within the same LAN segment. The first node is randomly selected by the central server from among the nodes within the same LAN segment; it can be one, two, or more nodes. The second node is any other node within the same LAN segment as the first node.

[0068] Nodes within the same local area network segment refer to OTA devices within the same network area or geographical area; one OTA device constitutes one node. Based on... Figure 2 The OTA upgrade method of the OTA upgrade system shown is as follows: For each OTA device cluster in a local area network segment, the central server first randomly selects a priority OTA device (i.e., the first node) to be upgraded. The priority OTA device downloads the upgrade installation package from the central server and performs the upgrade. After the priority OTA device completes the upgrade, it broadcasts an upgrade notification. Other OTA devices in the local area network segment (i.e., the second node) receive the upgrade notification, download the upgrade installation package from the priority OTA device, and perform the upgrade. This method can improve the efficiency of OTA upgrades and reduce the performance requirements of the upgrade system.

[0069] based on Figure 2 For details on the OTA upgrade method of the OTA upgrade system, please refer to [link / reference]. Figure 3 The method may include the following steps: steps S310 to S340.

[0070] S310: The central server sends an upgrade notification to the first node, which is a node randomly selected by the central server.

[0071] The first node is a node randomly selected by the central server within a network segment. Both the first and second nodes are within the same network segment. The first node is designated as the priority upgrade node and undergoes priority upgrades. Other nodes within the same network segment, i.e., the second node, are not priority upgrade nodes. Therefore, the first node can be referred to as the priority upgrade node, and the second node as a non-priority upgrade node. The central server's OTA management platform sends upgrade notifications in batches to all randomly designated priority upgrade nodes within each network segment to notify devices to perform upgrades.

[0072] The message body of the upgrade notification can include upgrade type (all devices / specified devices), device number, product type, new version number, firmware download address, firmware MD5 information, etc.

[0073] In one embodiment, before step S310, the method may further include: the device manufacturer uploading the tested firmware upgrade package to the firmware library of the central server through the OTA management platform, and storing other auxiliary information (such as upgrade package name, file size, message digest algorithm (MD5) parameters, product, device type, etc.) in the database.

[0074] S320: The first node obtains the upgrade data packet from the central server according to the upgrade notification, and completes the upgrade of the first node based on the upgrade data packet.

[0075] After receiving the upgrade notification, the priority upgrade node obtains the upgrade data package from the firmware library of the central server. The upgrade data package can be a firmware upgrade package. After obtaining the firmware upgrade package, the priority upgrade node performs the upgrade based on the firmware upgrade package.

[0076] In one embodiment, before step S320, the method may further include: when the priority upgrade node receives the upgrade notification, it first compares its own version number; if the version numbers are the same, no upgrade is required; otherwise, the upgrade procedure is triggered.

[0077] In one embodiment, step S320 may further include: the priority upgrade node performing MD5 file fingerprint verification on the obtained firmware upgrade package; and the priority upgrade node completing the upgrade based on the firmware upgrade package after verifying that the firmware upgrade package has passed the verification.

[0078] S330: First node broadcasts upgrade notification.

[0079] The node that prioritizes upgrading broadcasts an upgrade notification to other nodes within the same network segment, notifying un-upgraded device nodes within the same network segment to perform the upgrade.

[0080] S340: When the second node receives an upgrade notification, the second node obtains the upgrade data packet from the first node and completes the upgrade of the second node based on the upgrade data packet.

[0081] When a non-priority upgrade node receives an upgrade notification, it downloads the firmware upgrade package from the priority upgrade node. After obtaining the firmware upgrade package, the non-priority upgrade node completes the upgrade based on the firmware upgrade package.

[0082] In one embodiment, in step S340, when the second node receives the upgrade notification, the method may further include: when a non-priority upgrade node receives the upgrade notification, it first compares its own version number; if the version numbers are the same, no upgrade is required; otherwise, the upgrade procedure is triggered.

[0083] In one embodiment, in step S340, after the second node obtains the upgrade data package from the first node, the method may further include: performing MD5 file fingerprint verification on the obtained firmware upgrade package, and completing the upgrade based on the firmware upgrade package after the non-priority upgrade node verifies the firmware upgrade package.

[0084] This embodiment provides an OTA upgrade method applied to a system including a central server, a first node, and a second node, which are nodes within the same network segment. The OTA upgrade method includes: the central server sending an upgrade notification to the first node, where the first node is a node randomly selected by the central server; the first node obtaining an upgrade data packet from the central server according to the upgrade notification and completing its upgrade based on the upgrade data packet; by prioritizing the upgrade of a subset of nodes (i.e., the first nodes), the pressure on the central server to connect to the upgrade device is reduced. After the first node completes its upgrade, it broadcasts an upgrade notification. Upon receiving the upgrade notification, the second node within the same network segment obtains upgrade data from the first node and completes its upgrade based on the upgrade data packet. By having multiple first nodes randomly selected by the central server simultaneously send upgrade data packets to un-upgraded second nodes within the same network segment, the pressure on the central server to connect to the upgrade device is distributed, data transmission latency is reduced, and the upgrade efficiency of OTA is improved; it also avoids network security issues caused by cross-network segment transmission. In addition, compared with the OTA upgrade method of building an edge storage network by introducing an edge computing gateway to distribute the load pressure of the central server, this embodiment can avoid the system facing high-concurrency download upgrades, reduce the performance requirements of the system hardware and software, and reduce the investment cost of upgrading the system.

[0085] As another implementation of this application, in step S310: before the central server sends an upgrade notification to the first node, the method may further include:

[0086] The central server broadcasts the first message, which is then used by the nodes that receive the first message to send a response message to the central server. The response message includes the time when the first message was received.

[0087] When the central server receives a response message, it selects the first node as the first node based on the time it received the first message.

[0088] The central server broadcasts a first message to all nodes within each network segment. This first message can be a notification to select a node as the first node, i.e., a node to be prioritized for upgrade. After the central server broadcasts the first message, all nodes within the network segment that received the first message send a response message to the central server. The response message includes the time when each node in the network segment received the first message. Upon receiving the response message, the central server sorts the nodes within the same network segment according to the order in which each node received the first message, and selects a first number of nodes as priority upgrade nodes from the beginning to the end. The first number can be adjusted according to the actual situation and is not limited in this embodiment.

[0089] This embodiment sorts the nodes within the same network segment according to the order in which they received the first message from the central server, and selects a certain number of nodes as priority upgrade nodes for priority upgrade. By orderly selecting a portion of the nodes for priority upgrade, the system can avoid high-concurrency download upgrade situations and reduce the requirements on system performance.

[0090] As another implementation of this application, step S340: When the second node receives an upgrade notification, the second node obtains upgrade data from the first node and completes the upgrade of the second node based on the upgrade data packet, including:

[0091] Upon receiving the upgrade notification, the second node sends a download request to the first node;

[0092] When the first node receives a download request, it prioritizes responding to the download request received first based on its capacity and sends an upgrade data packet to the second node with the required capacity. The second node that receives the upgrade data packet completes the upgrade based on the upgrade data packet.

[0093] When a non-priority upgrade node receives an upgrade notification from a priority upgrade node, each non-priority upgrade node sends a download request to the priority upgrade node to request the download of the data upgrade package. Upon receiving a download request, the priority upgrade node sorts the non-priority upgrade nodes according to the order in which the priority upgrade node received the download request. Based on its capacity, the priority upgrade node selects the required number of non-priority upgrade nodes from the sorted list and sends the firmware upgrade package to these selected nodes. After receiving the firmware upgrade package, the non-priority upgrade nodes complete the upgrade based on it. The capacity refers to the maximum number of non-priority upgrade nodes that a priority upgrade node can connect to in each batch, which can be adjusted according to actual conditions and is not limited in this embodiment.

[0094] This embodiment sets the number of data upgrade packets that priority upgrade nodes can send to non-priority upgrade nodes in each batch, thereby preventing service overload during node upgrades, reducing the risk of server downtime, and improving system reliability.

[0095] As another implementation of this application, in step S340: after the second node receives the upgrade data packet and completes the upgrade of the second node based on the upgrade data packet, the method may further include:

[0096] The first node and / or the second node that has completed the upgrade broadcast the upgrade notification;

[0097] If a second node that has not completed the upgrade receives an upgrade notification, the second node that has not completed the upgrade obtains the upgrade data packet from the first node corresponding to the received upgrade notification or from the second node that has completed the upgrade, and completes the upgrade of the second node that has not completed the upgrade based on the upgrade data packet.

[0098] After setting the carrying capacity of priority upgrade nodes, i.e. the maximum number of non-priority upgrade nodes that a priority upgrade node can connect to in each batch, the number of non-priority upgrade nodes that receive upgrade notifications broadcast by the priority upgrade nodes in the same network segment is greater than the carrying capacity of the priority upgrade nodes. Therefore, there are still non-priority upgrade nodes in the same network segment that have not completed the upgrade.

[0099] At this point, upgraded non-priority upgrade nodes can also be treated as priority upgrade nodes and continue broadcasting upgrade notifications to un-upgraded non-priority upgrade nodes within the same network segment, along with the original priority upgrade nodes. Alternatively, upgrade notifications can be broadcast to un-upgraded non-priority upgrade nodes within the same network segment solely through the original priority upgrade nodes. Or, upgrade notifications can be broadcast to un-upgraded non-priority upgrade nodes within the same network segment solely through the upgraded non-priority upgrade nodes. Upon receiving an upgrade notification, each un-upgraded non-priority upgrade node downloads the firmware upgrade package from the corresponding source node of the received upgrade notification. After obtaining the firmware upgrade package, the un-upgraded non-priority upgrade node completes the upgrade based on the firmware upgrade package. Following these methods, the upgrade of all nodes within the same network segment is completed in batches.

[0100] This embodiment upgrades all nodes in the same network segment in batches by using previously upgraded non-priority upgrade nodes as new priority upgrade nodes. Together with the original priority upgrade nodes or separately, they broadcast upgrade notifications to the non-priority upgrade nodes that have not yet been upgraded in the same network segment. This ensures that no service overload occurs during the upgrade process while improving upgrade efficiency.

[0101] As another implementation of this application, the method further includes: when the second node receives the upgrade notification, the second node sends the upgrade progress to the central server.

[0102] When a non-priority upgrade node receives an upgrade notification, it continuously sends upgrade progress information to the central server while performing the upgrade. The central server's device database can receive and update the upgrade progress information in real time. The upgrade progress information can include download progress, upgrade progress, and error information. Error information can include upgrade package download failure, verification failure, and upgrade process errors.

[0103] In one embodiment, when a priority upgrade node receives an upgrade notification, the priority upgrade node continuously sends upgrade progress updates to the central server while performing the upgrade.

[0104] In one embodiment, the task scheduling platform of the central server gateway monitors the upgrade progress and status of device nodes in real time. When an abnormality occurs during device upgrade, it generates key information and reports it to the OTA management platform, then triggers alarm emails or SMS notifications to relevant management and operation personnel, and promptly reports back to the device manufacturer for modification, optimization and upgrade.

[0105] This embodiment sends the upgrade progress of each device to a central server in real time. The central server monitors the upgrade progress and status of the device nodes, generates key information, and sends it to the management user so that the management user can manage and perform effective operations, thus ensuring the stability and efficiency of the OTA upgrade system.

[0106] To address the problems of the prior art, embodiments of this application provide an OTA upgrade method, apparatus, device, computer-readable storage medium, and computer program product. The OTA upgrade method provided in this application embodiment is described below first.

[0107] The second OTA upgrade method provided in this application embodiment is as follows: Figure 4 and Figure 5 The difference between this method and the first OTA upgrade method is that after the first node receives the upgrade notification and downloads the upgrade installation package, it does not complete the upgrade immediately, but continues to broadcast the upgrade notification to the second nodes in the local area network segment. The second nodes obtain the upgrade installation package, start the upgrade, and send the upgrade progress to the first node. The first node completes the upgrade only after all the second nodes have completed the upgrade.

[0108] The second type of OTA upgrade method uses an OTA upgrade system such as... Figure 4 As shown, the OTA upgrade system includes a central server, a core network, an access network, and an OTA device cluster across multiple network segments, where each network segment is a local area network (LAN). Each LAN segment includes a first node and a second node, both located within the same LAN segment. The first node is selected by the central server from nodes within the same LAN segment, possibly according to a certain ratio. The second node is any other node within the same LAN segment as the first node.

[0109] based on Figure 4The OTA upgrade method is as follows: For each OTA device cluster in a local area network segment, the central server first selects the master OTA device (i.e., the first node) to receive the notification first. After the master OTA device downloads the upgrade installation package from the central server, it broadcasts the upgrade notification. After receiving the upgrade notification, the other OTA devices in the local area network segment (i.e., the second nodes) download the upgrade installation package from the master OTA device and perform the upgrade. At the same time, they send the upgrade progress to the master OTA device. After all other OTA devices in the local area network segment have completed the upgrade, the master OTA device performs the upgrade. This method can improve the OTA upgrade efficiency and reduce the performance requirements of the upgrade system.

[0110] based on Figure 4 For details on the OTA upgrade method of the OTA upgrade system, please refer to [link / reference]. Figure 5 The method may include the following steps: steps S510 to S540.

[0111] S510: The central server sends an upgrade notification to the first node.

[0112] The first node is selected by the central server within a network segment. Both the first and second nodes are within the same network segment. The first node performs upgrades by interacting with the central server, while other nodes within the same segment, i.e., the second node, perform upgrades by interacting with the first node. Therefore, the first node can be referred to as the master node, and the second node as a non-master node. The central server's OTA management platform sends batch upgrade notifications to the master nodes within each network segment to inform devices to perform upgrades.

[0113] The message body of the upgrade notification can include upgrade type (all devices / specified devices), device number, product type, new version number, firmware download address, firmware MD5 information, etc.

[0114] In one embodiment, before step S510, the method may further include: the device manufacturer uploading the tested firmware upgrade package to the firmware library of the central server through the OTA management platform, and storing other auxiliary information (such as upgrade package name, file size, message digest algorithm (MD5) parameters, product, device type, etc.) in the database.

[0115] S520: The first node obtains the upgrade data packet from the central server according to the upgrade notification and broadcasts the upgrade notification.

[0116] After receiving the upgrade notification, the master node retrieves the upgrade data package from the firmware library of the central server. The upgrade data package can be a firmware upgrade package. After obtaining the firmware upgrade package, the master node broadcasts the upgrade notification to other nodes in the same network segment.

[0117] In one embodiment, in step S520, after the first node obtains the upgrade data packet from the central server according to the upgrade notification, the method may further include the master node first performing MD5 file fingerprint verification on the obtained firmware upgrade package, and after the master node verifies the firmware upgrade package, broadcasting the upgrade notification to other nodes in the same network segment.

[0118] S530: When the second node receives the upgrade notification, the second node obtains the upgrade data packet from the first node, completes the upgrade of the second node based on the upgrade data packet, and sends the upgrade progress to the first node.

[0119] When a non-master node receives an upgrade notification, it downloads the firmware upgrade package from the master node. After obtaining the firmware upgrade package, the non-master node completes the upgrade based on the firmware upgrade package. At the same time, during the upgrade process, it continuously sends upgrade progress to the master node. The upgrade progress can include download progress, upgrade progress, and error information. Error information can include upgrade package download failure, verification failure, and upgrade process error.

[0120] In one embodiment, in step S530, after the second node receives the upgrade notification and obtains the upgrade data packet from the first node, the method may further include: when the non-master node receives the upgrade notification, it first compares its own version number; if the version numbers are the same, no upgrade is required; otherwise, the upgrade procedure is triggered.

[0121] In one embodiment, in step S530, after the second node receives the upgrade notification and obtains the upgrade data package from the first node, the method may further include: the non-master node first performs MD5 file fingerprint verification on the obtained firmware upgrade package, and after the non-master node verifies the firmware upgrade package, it completes the upgrade based on the firmware upgrade package.

[0122] S540: When the second node upgrade is completed, the first node completes the upgrade of the first node based on the upgrade data packet.

[0123] After all non-master nodes have been upgraded, the master node completes the upgrade based on the firmware upgrade package.

[0124] In one embodiment, in step S540, after all non-master nodes have been upgraded, the method may further include: the master node compares its own version number according to the received upgrade notification; if the version numbers are the same, no upgrade is required; otherwise, the upgrade procedure is triggered.

[0125] This embodiment provides an OTA upgrade method applied to a system including a central server, a first node, and a second node, which are nodes within the same network segment. The OTA upgrade method includes: the central server sending an upgrade notification to the first node; the first node obtaining an upgrade data packet from the central server according to the upgrade notification and broadcasting the upgrade notification; by selecting a subset of nodes (i.e., the first node) to obtain the data upgrade packet first, and utilizing these nodes to broadcast the upgrade notification, the pressure on the central server to connect to the upgrade device is distributed, avoiding high-concurrency download upgrades, reducing the performance requirements of the system, and lowering system investment costs. After receiving the upgrade notification, the second node obtains the upgrade data packet from the first node, completes its own upgrade based on the upgrade data packet, and sends the upgrade progress to the first node; after the second node completes its upgrade, the first node completes its own upgrade based on the upgrade data packet. By having multiple master control nodes simultaneously send upgrade data packets to the second node within the same network segment, enabling the second node to upgrade simultaneously, data transmission latency is reduced, and the upgrade efficiency of OTA is improved; it also avoids network security issues caused by cross-network segment transmission. Timely aggregation of node upgrade progress facilitates device monitoring of the upgrade status and ensures the stability of the upgrade system.

[0126] As another implementation of this application, the method further includes: within a preset time period, the first node sends the upgrade progress received by the first node from the second node to the central server.

[0127] While receiving upgrade progress reports from non-master nodes, the master node periodically sends the aggregated upgrade progress reports from non-master nodes to the central server, thus updating the device upgrade process data in a timely manner.

[0128] In one embodiment, in S540: after the first node completes its upgrade based on the upgrade data packet, when the second node upgrade is completed, the method further includes: the master node sending the upgrade progress of the master node to the central server. The upgrade progress may include download progress, upgrade progress, and error information. The error information may include upgrade package download failure, verification failure, and upgrade process error.

[0129] In one embodiment, the task scheduling platform of the central server gateway monitors the upgrade progress and status of device nodes in real time. When an abnormality occurs during device upgrade, it generates key information and reports it to the OTA management platform, and then triggers alarm emails or SMS notifications to relevant management and operation personnel, and promptly feeds back to the equipment manufacturer for modification, optimization and upgrade.

[0130] This embodiment reduces the pressure on the central server to connect with the device nodes by periodically sending the device upgrade progress to the central server through the master control node. The central server monitors the upgrade progress and status of the device nodes, generates key information and sends it to the management user, so that the management user can manage and take effective actions, thus ensuring the stability and efficiency of the OTA upgrade system.

[0131] As another implementation of this application, before step S510: the central server sends an upgrade notification to the first node, the method includes:

[0132] The central server selects the first node according to a preset ratio, which is the ratio of the number of first nodes to the number of second nodes.

[0133] The central server can randomly select master control nodes from the same network area or geographical area according to a preset ratio. This preset ratio can be the ratio of master control nodes to non-master control nodes, or the ratio of master control nodes to all nodes in the same network segment. For example, the ratio can be set to 3 master control nodes out of 100 device nodes in the same network segment, which can be randomly selected by the central server before issuing a batch upgrade notification.

[0134] This embodiment ensures the number of central servers or central control nodes connected in each batch during device node upgrades by presetting the ratio of master control nodes to non-master control nodes, preventing overload of the central server or single node services, improving the stability of the upgrade system, and also helps to improve upgrade efficiency by reasonably setting the preset ratio.

[0135] As another implementation of this application, after the first node completes its upgrade based on the upgrade data packet in step S540: when the second node upgrade is complete, the method further includes:

[0136] The central server calculates the upgrade success rate of the second node;

[0137] If the upgrade success rate is less than the target threshold, the first node is determined to be the third node. The proportion of the third node being selected as the first node by the central server is lower than that of other nodes in the same network segment.

[0138] Once all nodes within the same network segment have completed the upgrade corresponding to this upgrade notification, the central server calculates the number of upgrades completed by the master node for non-master nodes and the success rate of upgrades, thus obtaining the upgrade success rate for each master node. When the upgrade success rate of a master node falls below a certain threshold, this master node is marked and can be designated as a third node. Before the central server broadcasts the next round of upgrade notifications within the same network segment, this reduces the probability that this node will be selected as the master node by the central server.

[0139] This embodiment calculates the success rate of each master node by measuring the data of each master node successfully upgrading non-master nodes after each round of device upgrades. Based on the success rate of the master node, adjustments can be made in the next round of upgrades to ensure the reliability of the master node and improve the efficiency of OTA upgrades.

[0140] As another implementation of this application, the method further includes: after a device successfully goes online, it will broadcast its online message within its network area. After receiving the broadcast message, the master control node will add the node information of the newly online device to the master control node's cluster and return an ACK message. When a device actively goes offline, it will broadcast its offline notification. At the same time, the master control node will also periodically send heartbeat detection messages. When a faulty node is detected, the online information of that node will be removed.

[0141] For example, the online message body of a broadcast may include: update time (upTime), area code (areaCode), message sequence number (msgId), message type (msgType), local IP address (localIp), product identifier (prodId), event type (event), firmware version (firmwareVersion), product type (prodType), device identifier (deviceId), software version (softwareVersion), and hardware address (MAC address). The message type may include unicast, broadcast, etc. The event type may include online, offline, upgrade (upGrade), vote, and acknowledgment (ack).

[0142] As another implementation of this application, the method may further include:

[0143] The first node detects the status of the first node and the second node;

[0144] If the second node is in a faulty state, the first node deletes the second node;

[0145] If the first node is in a faulty state, the second node broadcasts an election message to the first node. The first node that receives the election message then sends a response message to the corresponding second node. If the number of response messages received by the second node is greater than the target value, the second node that receives more response messages than the target value becomes the first node. The first node in a faulty state becomes the second node. The target value is half the number of first nodes.

[0146] The master node periodically sends heartbeat messages to monitor the status of all nodes within the same network segment. When a non-master node is found to be faulty, its online information is removed, and it is deleted from the cluster where the master node resides. When a master node is found to be faulty, the non-master node broadcasts a re-election (vote) message. All master nodes, upon receiving the election message, determine the legitimacy of the requester (i.e., the non-master node) and send a corresponding ack message. They attempt to collect the ack messages returned by the master node from the non-master node that has applied to become the master node. When the number of received ack messages exceeds half the number of master nodes, the non-master node becomes the new master node. The new master node notifies all other nodes, and the original faulty master node becomes a non-master node.

[0147] This embodiment detects the status of nodes within the network segment, deletes faulty non-master nodes, and elects a new master node to replace the original faulty master node, thereby ensuring the effectiveness of nodes within the network segment and improving OTA upgrade efficiency.

[0148] Based on the same concept, this application provides an OTA upgrade device, which is described below in conjunction with... Figure 6 The OTA upgrade device provided in the embodiments of this application will be described in detail.

[0149] Figure 6 This is a structural block diagram of an OTA upgrade device shown in an embodiment of this application.

[0150] like Figure 6 As shown, this device is applied to a system, which includes a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the device may include:

[0151] The sending module 610 is used by the central server to send an upgrade notification to the first node, wherein the first node is a node randomly selected by the central server.

[0152] The acquisition module 620 is used for the first node to obtain the upgrade data packet from the central server according to the upgrade notification, and to complete the upgrade of the first node based on the upgrade data packet;

[0153] Broadcast module 630 is used for broadcasting upgrade notifications to the first node;

[0154] The acquisition module 620 is also used to, when the second node receives an upgrade notification, obtain upgrade data from the first node and complete the upgrade of the second node based on the upgrade data packet.

[0155] In one embodiment, the sending module 610 is further configured to, before the central server sends an upgrade notification to the first node, broadcast a first message so that the node receiving the first message can send a response message to the central server, the response message including the time of receiving the first message; and if the central server receives the response message, the central server selects a first number of nodes that received the first message first as the first node according to the time of receiving the first message.

[0156] In one embodiment, the acquisition module 620 is specifically used to send a download request to the first node when the second node receives an upgrade notification; when the first node receives a download request, the first node, based on its capacity, prioritizes responding to the download request received first and sends an upgrade data packet to the second node with the required capacity; and the second node that receives the upgrade data packet completes the upgrade based on the upgrade data packet.

[0157] In one embodiment, the acquisition module 620 is further configured to broadcast an upgrade notification after the second node that has received the upgrade data packet completes the upgrade of the second node based on the upgrade data packet; if the second node that has not completed the upgrade receives the upgrade notification, the second node that has not completed the upgrade obtains the upgrade data packet from the first node corresponding to the received upgrade notification or the second node that has completed the upgrade, and completes the upgrade of the second node that has not completed the upgrade based on the upgrade data packet.

[0158] In one embodiment, the acquisition module 620 is further configured to send the upgrade progress to the central server when the second node receives the upgrade notification.

[0159] Figure 6 Each module in the illustrated device has the ability to implement Figure 2 The functions of each step in the process and their corresponding technical effects are described in detail here for the sake of brevity.

[0160] Based on the same concept, this application provides an OTA upgrade device, which is described below in conjunction with... Figure 7 The OTA upgrade device provided in the embodiments of this application will be described in detail.

[0161] Figure 7 This is a structural block diagram of an OTA upgrade device shown in an embodiment of this application.

[0162] like Figure 7 As shown, this device is applied to a system, which includes a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the device may include:

[0163] The sending module 710 is used by the central server to send upgrade notifications to the first node;

[0164] The acquisition module 720 is used by the first node to obtain the upgrade data packet from the central server according to the upgrade notification and broadcast the upgrade notification.

[0165] The acquisition module 720 is also used to, when the second node receives an upgrade notification, obtain an upgrade data packet from the first node, complete the upgrade of the second node based on the upgrade data packet, and send the upgrade progress to the first node;

[0166] The acquisition module 720 is also used to enable the first node to complete its upgrade based on the upgrade data packet when the second node has completed its upgrade.

[0167] In one embodiment, the sending module 710 is further configured to send the upgrade progress received by the first node from the second node to the central server within a preset time period.

[0168] In one embodiment, the sending module 710 is further configured to select the first node according to a preset ratio before the central server sends an upgrade notification to the first node, wherein the preset ratio is the ratio of the number of the first node to the number of the second node.

[0169] In one embodiment, the acquisition module 720 is further configured to, after the first node completes its upgrade based on the upgrade data packet, calculate the upgrade success rate of the second node when the second node upgrade is completed; and if the upgrade success rate is less than the target threshold, determine the first node as the third node, wherein the proportion of the third node selected by the central server as the first node is lower than that of other nodes in the same network segment.

[0170] In one embodiment, the sending module 710 is further configured to: detect the status of the first node and the second node; delete the second node if the status of the second node is faulty; broadcast an election message to the first node if the status of the first node is faulty, so that the first node receiving the election message can send a response message to the corresponding second node; if the number of response messages received by the second node is greater than a target value, the second node whose number of received response messages is greater than the target value becomes the first node, and the first node whose status is faulty becomes the second node, and the target value is half the number of first nodes.

[0171] Figure 7 Each module in the illustrated device has the ability to implement Figure 4 The functions of each step in the process and their corresponding technical effects are described in detail here for the sake of brevity.

[0172] Figure 8A schematic diagram of the hardware structure of an electronic device provided in one embodiment of this application is shown.

[0173] The electronic device may include a processor 810 and a memory 820 storing computer program instructions.

[0174] Specifically, the processor 810 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0175] Memory 820 may include mass storage for data or instructions. For example, and not limitingly, memory 820 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 820 may include removable or non-removable (or fixed) media. Where appropriate, memory 820 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 820 is non-volatile solid-state memory.

[0176] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to the first aspect of this disclosure.

[0177] The processor 810 implements any of the OTA upgrade methods described in the above embodiments by reading and executing computer program instructions stored in the memory 820.

[0178] In one example, the electronic device may also include a communication interface 830 and a bus 840. For example, Figure 8 As shown, the processor 810, memory 820, and communication interface 830 are connected through bus 840 and complete communication with each other.

[0179] The communication interface 830 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0180] Bus 840 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 810 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0181] The electronic device can execute the OTA upgrade method in the embodiments of this application, thereby achieving the combination Figure 2 and Figure 4 The OTA upgrade method is described.

[0182] Furthermore, in conjunction with the OTA upgrade methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement any of the OTA upgrade methods in the above embodiments.

[0183] This application also provides a computer program product, including a computer program, which, when executed, implements any of the OTA upgrade methods described in the above embodiments.

[0184] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0185] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0186] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0187] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0188] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. An OTA upgrade method, characterized in that, The system is applied to a system comprising a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the method includes: The central server sends an upgrade notification to the first node, wherein the first node is a node randomly selected by the central server. The first node obtains an upgrade data packet from the central server according to the upgrade notification, and completes the upgrade of the first node based on the upgrade data packet; The first node broadcasts the upgrade notification; Upon receiving the upgrade notification, the second node obtains the upgrade data packet from the first node and completes the upgrade of the second node based on the upgrade data packet.

2. The method according to claim 1, characterized in that, Before the central server sends an upgrade notification to the first node, the method further includes: The central server broadcasts a first message, which is used by nodes that receive the first message to send a response message to the central server. The response message includes the time when the first message was received. Upon receiving a response message, the central server selects a first number of nodes that received the first message first, based on the time of receipt of the first message, as the first node.

3. The method according to claim 1, characterized in that, When the second node receives the upgrade notification, the second node obtains the upgrade data from the first node and completes the upgrade of the second node based on the upgrade data packet, including: Upon receiving the upgrade notification, the second node sends a download request to the first node; When the first node receives a download request, it prioritizes responding to the download request received first by the first node based on the first node's capacity, and sends the upgrade data packet to the second node with the capacity. The second node that receives the upgrade data packet completes the upgrade of the second node based on the upgrade data packet.

4. The method according to any one of claims 1 to 3, characterized in that, After the second node that receives the upgrade data packet completes the upgrade of the second node based on the upgrade data packet, the method further includes: The first node and / or the second node that has completed the upgrade broadcasts the upgrade notification; If the second node that has not completed the upgrade receives the upgrade notification, the second node that has not completed the upgrade obtains the upgrade data packet from the first node corresponding to the received upgrade notification or from the second node that has completed the upgrade, and completes the upgrade of the second node that has not completed the upgrade based on the upgrade data packet.

5. The method according to claim 1, characterized in that, The method further includes: Upon receiving the upgrade notification, the second node sends the upgrade progress to the central server.

6. An OTA upgrade method, characterized in that, The system is applied to a system comprising a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the method includes: The central server sends an upgrade notification to the first node; The first node obtains an upgrade data packet from the central server based on the upgrade notification and broadcasts the upgrade notification. When the second node receives the upgrade notification, the second node obtains the upgrade data packet from the first node, completes the upgrade of the second node based on the upgrade data packet, and sends the upgrade progress to the first node; Once the second node upgrade is complete, the first node completes its own upgrade based on the upgrade data packet.

7. The method according to claim 6, characterized in that, The method further includes: Within a preset time period, the first node sends the upgrade progress it received from the second node to the central server.

8. The method according to claim 6, characterized in that, Before the central server sends an upgrade notification to the first node, the method includes: The central server selects the first node according to a preset ratio, where the preset ratio is the ratio of the number of the first node to the number of the second node.

9. The method according to claim 8, characterized in that, After the first node completes its upgrade based on the upgrade data packet, when the second node has completed its upgrade, the method further includes: The central server calculates the upgrade success rate of the second node; If the upgrade success rate is less than the target threshold, the first node is determined to be the third node, and the proportion of the third node selected by the central server as the first node is lower than that of other nodes in the same network segment.

10. The method according to claim 6, characterized in that, The method further includes: The first node detects the status of the first node and the second node; If the second node is in a faulty state, the first node deletes the second node; If the first node is in a faulty state, the second node broadcasts an election message to the first node, so that the first node receiving the election message can send a response message to the corresponding second node. If the number of response messages received by the second node is greater than a target value, the second node that receives more than the target value becomes the first node, and the first node in a faulty state becomes the second node. The target value is half the number of the first nodes.

11. An OTA upgrade device, characterized in that, The system is applied to a system comprising a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the device comprises: The sending module is used for the central server to send an upgrade notification to the first node, wherein the first node is a node randomly selected by the central server; The acquisition module is used for the first node to acquire an upgrade data packet from the central server according to the upgrade notification, and to complete the upgrade of the first node based on the upgrade data packet; The broadcast module is used by the first node to broadcast the upgrade notification; The acquisition module is further configured to, when the second node receives the upgrade notification, the second node acquires the upgrade data from the first node and completes the upgrade of the second node based on the upgrade data packet.

12. An OTA upgrade device, characterized in that, The system is applied to a system comprising a central server, a first node, and a second node, wherein the first node and the second node are nodes within the same network segment; the device comprises: The sending module is used by the central server to send an upgrade notification to the first node; The acquisition module is used for the first node to acquire an upgrade data packet from the central server according to the upgrade notification, and to broadcast the upgrade notification. The acquisition module is further configured to, when the second node receives the upgrade notification, the second node acquires the upgrade data packet from the first node, completes the upgrade of the second node based on the upgrade data packet, and sends the upgrade progress to the first node; The acquisition module is further configured to, when the second node has completed its upgrade, have the first node complete its upgrade based on the upgrade data packet.

13. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the OTA upgrade method as described in any one of claims 1-10.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the OTA upgrade method as described in any one of claims 1-10.

15. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the OTA upgrade method as described in any one of claims 1-10.