Intelligent central control equipment, terminal equipment upgrading method and device, and medium

Abstract

The invention relates to an intelligent central control device, a terminal device upgrading method and device and a medium, and the method comprises the steps: requesting a server to determine a to-be-upgraded terminal device and return a corresponding firmware package needing to be upgraded according to the firmware version information of each terminal device accessed through a target communication protocol; based on the network transmission characteristics of the to-be-upgraded terminal devices, dividing the to-be-upgraded terminal devices into a plurality of to-be-upgraded groups corresponding to different upgrading times; dividing a corresponding firmware package of each to-be-upgraded terminal device into a plurality of fragmented data based on the device upgrading characteristics of each to-be-upgraded terminal device; and responding to the arrival event of the upgrading time, calling fragmented data of different terminal devices to be upgraded from the corresponding groups to be upgraded in turn, and transmitting the fragmented data to the corresponding terminals to be upgraded. According to the method and the device, the reliability, the efficiency and the success rate of firmware upgrading of equipment in large-scale low-bandwidth networks such as Zigbee can be improved.

Description

Technical Field

[0001] This application relates to the field of intelligent control, and in particular to a method, apparatus, and medium for upgrading intelligent central control equipment and terminal equipment. Background Technology

[0002] With the widespread adoption of IoT technology, smart home systems are connecting an ever-growing number of terminal devices, such as smart lighting, security sensors, temperature and humidity sensors, and smart sockets. These devices widely employ low-power short-range wireless communication protocols for networking, such as Zigbee, to build a mesh network covering the entire living space. To ensure the complete functionality and stable security of these devices, regular firmware upgrades—i.e., remote wireless upgrades—have become a fundamental maintenance requirement for smart home systems.

[0003] Traditional remote wireless upgrade methods typically involve a cloud server downloading the complete firmware package to the target device over the network, which then verifies and installs it. This method performs well in high-bandwidth and stable Wi-Fi or Ethernet environments. However, in the specific scenario of smart homes, low-power network environments based on protocols such as Zigbee have inherent characteristics. First, the design of these networks prioritizes low power consumption and low cost, resulting in significantly lower data transmission bandwidth compared to Wi-Fi networks, typically only a few hundred Kb per second. Second, the terminal devices in the network are mostly battery-powered or operate intermittently, leading to unstable network connections. Furthermore, smart home networks can contain dozens or even hundreds of devices, geographically dispersed, resulting in complex network paths.

[0004] Based on the aforementioned network characteristics, traditional whole-packet transmission upgrade methods face severe challenges in practical applications. When the firmware package is large, complete transmission over a low-bandwidth Zigbee network takes an extremely long time. During this period, even minor fluctuations in network signal, devices entering sleep mode for energy saving, or wireless interference from other devices can easily cause transmission interruptions. Once transmission is interrupted, the entire firmware package needs to be transmitted again, which not only wastes limited network bandwidth resources but also significantly increases device power consumption, potentially leading to upgrade failure for battery-powered devices. More importantly, when upgrading a large number of devices on the network simultaneously, if the traditional method is used to initiate upgrades one by one, the long transmission time of the first device will consume a large amount of network resources, causing subsequent devices to wait for a long time, resulting in extremely low overall upgrade efficiency. If concurrent upgrades are attempted, the simultaneous transmission of large amounts of data by a large number of devices will far exceed the carrying capacity of the Zigbee network, causing network congestion, which in turn makes the upgrade process of all devices slower and more prone to interruption, significantly reducing the success rate.

[0005] Therefore, there is an urgent need in this field for a firmware upgrade method that can adapt to the characteristics of low bandwidth, high concurrency, and easy interruption in smart home Zigbee networks, in order to solve the problems of low upgrade success rate, low efficiency, and high resource consumption of traditional technologies. Summary of the Invention

[0006] The primary objective of this application is to solve at least one of the above-mentioned problems by providing a method, apparatus, and medium for upgrading intelligent central control equipment and terminal equipment.

[0007] To achieve the various objectives of this application, the following technical solution is adopted: A terminal device upgrade method provided for one of the purposes of this application includes the following steps: Based on the firmware version information of each terminal device accessing via the target communication protocol, the server is requested to determine the terminal device to be upgraded and return the corresponding firmware package that needs to be upgraded. Based on the network transmission characteristics of each terminal device to be upgraded, each terminal device to be upgraded is divided into multiple upgrade groups corresponding to different upgrade times; Based on the device upgrade characteristics of each terminal device to be upgraded, the corresponding firmware package of each terminal device to be upgraded is divided into multiple data fragments; In response to the arrival of the upgrade time, the fragmented data of different terminal devices to be upgraded are called from the corresponding upgrade group in turn and sent to the corresponding upgrade terminal.

[0008] A terminal device upgrade apparatus, proposed for one of the purposes of this application, includes: The upgrade query module is configured to request the server to determine the terminal device to be upgraded and return the corresponding firmware package to be upgraded based on the firmware version information of each terminal device accessed by the target communication protocol. The upgrade grouping module is configured to divide each terminal device to be upgraded into multiple upgrade groups corresponding to different upgrade times based on the network transmission characteristics of each terminal device to be upgraded. The upgrade sharding module is configured to divide the corresponding firmware package of each terminal device to be upgraded into multiple shards based on the device upgrade characteristics of each terminal device to be upgraded. The upgrade scheduling module is configured to respond to the arrival event of the upgrade time by taking turns calling the fragmented data transmission of different terminal devices to be upgraded from the corresponding upgrade group and sending it to the corresponding terminal to be upgraded.

[0009] On another front, an intelligent central control device provided for one of the purposes of this application includes a controller, the controller including a processor and a memory, the processor calling and running a computer program in the memory to perform the steps of the terminal device upgrade method.

[0010] On another aspect, a computer-readable storage medium is provided to suit another purpose of this application, which stores in the form of computer-readable instructions a computer program implemented according to the terminal device upgrade method, which, when called by a computer, executes the steps included in the corresponding method.

[0011] Compared to traditional technologies, this application brings many significant benefits, including but not limited to: First, this application effectively reduces the amount of data transmitted in a single transmission by dividing the complete firmware package into multiple data fragments for transmission. This significantly shortens the transmission time of each fragment in low-bandwidth network environments such as Zigbee, thereby greatly reducing the probability of transmission interruption due to network fluctuations or device sleep mode. Even if the transmission of individual fragments fails, only that specific fragment needs to be retransmitted, avoiding the huge overhead of retransmitting the entire package if it fails, as is the case with traditional whole-packet transmission methods. This fundamentally improves the reliability and success rate of single-device upgrades.

[0012] Secondly, by grouping the terminal devices to be upgraded based on network transmission characteristics and allocating different upgrade times to different groups, this application achieves staggered scheduling of upgrade tasks in the time dimension. This design effectively avoids network channel congestion caused by a large number of devices simultaneously initiating upgrade requests, enabling network resources to be allocated and utilized in an orderly and reasonable manner. The grouping and time-based strategy transforms high-concurrency scenarios into low-concurrency or serial scenarios, thereby ensuring the overall stability and smoothness of the large-scale device upgrade process at the system level.

[0013] Furthermore, by combining firmware fragmentation transmission with device packet time-sharing scheduling, an organic whole is formed. Fragmentation processing solves the reliability problem at the transmission layer, while the packet time-sharing strategy solves the efficiency problem at the network resource allocation layer. Their synergistic effect enables this application to efficiently and reliably complete firmware upgrades for massive numbers of terminal devices in smart home scenarios under limited network bandwidth. This not only significantly shortens the overall upgrade cycle but also reduces excessive consumption of network resources and the impact on device power consumption, which is particularly beneficial for the long-term stable operation of battery-powered devices. Attached Figure Description

[0014] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart illustrating a typical embodiment of the terminal device upgrade method of this application; Figure 2 This is a schematic block diagram of the terminal equipment upgrade device of this application; Figure 3This is a schematic diagram of the structure of a computer device used in this application. Detailed Implementation

[0015] The terminal device upgrade method provided in this application can be deployed in a smart home network centered on a smart gateway. Such networks are typically built on low-power wireless communication protocols such as Zigbee and Bluetooth Mesh, forming a star or mesh-type local communication domain with the gateway as the control center. Numerous terminal devices are connected within this domain, such as smart lighting fixtures, door magnetic sensors, infrared or laser sensors to detect the presence of a human body, smart curtain motors, smart sockets, and various security sensors. In this architecture, the smart gateway acts as a bridge connecting cloud services and local terminal devices. It is not only a central hub for network protocol conversion but also carries local computing and control logic, collaborating with the cloud to complete complex device management tasks.

[0016] In a typical embodiment, a smart gateway or other smart device, acting as a central control unit, can serve as the key physical carrier for deploying the technical solution of this application. Physically, this device integrates a Zigbee coordinator, processor, memory, and non-volatile storage. Logically, the core control logic of this application is executed by a software system running on the smart central control device. This software system is provided by running a computer program implemented according to the method of this application, and can exist in the form of a firmware module, a standalone application, or a containerized service. The smart gateway is responsible for maintaining a list, status information, and firmware packages to be upgraded for all Zigbee terminal devices under its jurisdiction, and acts as a local upgrade server, directly communicating with the terminal devices via the Zigbee network for upgrade-related interactions.

[0017] In one embodiment, the smart gateway uses the Zigbee protocol as the target communication protocol to establish and maintain connections with terminal devices within the smart home network. During firmware upgrades, the smart central control device acts as a scheduler, retrieving firmware packages from a cloud server and, based on the method of this application, locally deciding on upgrade strategies and managing the entire process of data transmission of fragmented data generated from firmware package fragments. This ensures efficient transmission of firmware packages to multiple terminal devices within the smart home network, enabling the corresponding terminal devices to successfully complete firmware upgrades.

[0018] It should be noted that although the technical solution of this application can achieve unexpected technical effects in smart home networks built with Zigbee as the target communication protocol, the technical solution can also be applied to private networks built with other protocols such as Bluetooth.

[0019] Having clarified the aforementioned network architecture, core equipment, and basic concepts, the following section will further elaborate on the implementation details of the technical solution of this application in conjunction with specific embodiments.

[0020] Please see Figure 1 In some embodiments, the terminal device upgrade method of this application can be implemented as an application running in the processor of the intelligent central control device. The method includes: Step S3100: Based on the firmware version information of each terminal device accessing the target communication protocol, request the server to determine the terminal device to be upgraded and return the corresponding firmware package that needs to be upgraded. Intelligent central control devices can initiate firmware upgrade processes for numerous terminal devices in a smart home network by interacting with a server, such as triggering scheduled tasks or responding to user control operations. To do this, it is necessary to first identify the terminal devices requiring upgrades and obtain the corresponding firmware resources.

[0021] The intelligent central control device first joins a private network built using a target communication protocol to obtain firmware version information from all terminal devices under its jurisdiction that are connected to that private network. The target communication protocol can be a set of rules followed by the terminal devices to establish communication connections with the intelligent central control device, such as Zigbee, Bluetooth Mesh, or other low-power wireless communication protocols suitable for IoT devices. Firmware version information is data that uniquely identifies the firmware currently running on the terminal device, typically including version number, compilation timestamp, or checksum.

[0022] There are various ways to obtain firmware version information. In one embodiment, the intelligent central control device can proactively broadcast a query request to all terminal devices within the private network. Upon receiving the request, each terminal device encapsulates its own firmware version information in a response message and returns it. In another embodiment, terminal devices can proactively report their firmware version information to the intelligent central control device during power-on initialization, periodic heartbeat messages, or changes in network status. The intelligent central control device then persistently stores this information in a local database for direct retrieval when needed.

[0023] After aggregating firmware version information from all terminal devices, the smart central control device can send a request to the server. The server then identifies the terminal device to be upgraded and returns the corresponding firmware package. The server plays the role of version management and resource distribution. The request sent by the smart central control device to the server should at least include the terminal device's identification information and its current firmware version. The server's determination logic can be based on a preset upgrade strategy. For example, it can compare the current firmware version reported by the terminal device with the latest firmware version stored on the server; if the current version is lower than the latest version, the terminal device is determined to be the one to be upgraded. Furthermore, the upgrade strategy can be more granular, such as upgrading only devices with specific hardware versions, or triggering an upgrade only when the new firmware fixes a critical security vulnerability.

[0024] The server's response includes not only a list of terminal devices to be upgraded, but more importantly, access information for the corresponding firmware package. The firmware package is a file containing all the data for the new firmware version. In one embodiment, the server can directly send the complete firmware package file to the smart central control device. In another embodiment, to save bandwidth, the server can return only a download link or Uniform Resource Locator (URL) for the firmware package, which the smart central control device can then download automatically. After obtaining the firmware package or its access path, the smart central control device can cache it in its local storage space, preparing for subsequent fragmentation and transmission stages. This avoids frequently fetching data from a remote server during the upgrade process, improving upgrade efficiency and reducing reliance on cloud connections.

[0025] Step S3200: Based on the network transmission characteristics of each terminal device to be upgraded, divide each terminal device to be upgraded into multiple upgrade groups corresponding to different upgrade times; After completing the preparation of the terminal devices to be upgraded and the corresponding firmware packages, the intelligent central control device can continue to execute the grouping strategy to transform the large-scale concurrent upgrade tasks into orderly, manageable serialized or low-concurrency tasks to adapt to the carrying capacity of low-bandwidth networks. Specifically, it can classify each terminal device to be upgraded based on the network transmission characteristics that reflect the data transmission quality and stability, which are obtained in real time or accumulated historically from the private network.

[0026] Network transmission characteristics are a set of indicators characterizing the quality of the communication link between terminal devices and intelligent central control devices. In one embodiment, network transmission characteristics can be quantified into specific network status indicators, such as received signal strength indication, whose value directly reflects the strength of the signal; data packet round-trip delay, whose length reflects the real-time performance of communication; and data packet loss rate, whose level indicates the stability of the link. Intelligent central control devices can acquire these indicators in various ways, either by actively sending probe messages to the target terminal device and collecting responses, or by passively analyzing link quality data during daily communication processes.

[0027] Based on the aforementioned network transmission characteristics, the intelligent central control device divides the terminal devices to be upgraded into different upgrade groups and allocates different upgrade times to each group. The upgrade time can be implemented in various ways. In one typical embodiment, the upgrade time is represented as an upgrade time window with a clear start and end point allocated to each upgrade group as a whole. For example, the group assigned to terminal devices with high signal strength and stable link quality is scheduled for upgrades during the early morning hours when network traffic is low; while the group assigned to signal edge devices is scheduled during off-peak hours when the overall network load is relatively light. In another embodiment, the upgrade time can be represented as the time interval controlling the switching frequency between devices when performing round-robin calls within a group. For example, when network conditions are good, a shorter time interval is set to achieve rapid round-robin; when network congestion is detected, the time interval is dynamically lengthened to reduce the data transmission density per unit time, leaving room for network recovery. In more complex embodiments, the upgrade time can be a combination of upgrade time windows and time intervals. That is, different time windows are allocated to different groups on a macro level, and the time interval for devices in the group to take turns calling each other is dynamically adjusted within each window based on the real-time network conditions on a micro level.

[0028] The grouping strategy can be flexibly implemented based on different optimization objectives. In one embodiment, the intelligent central control device can calculate a comprehensive upgrade difficulty factor and group terminal devices with similar factors into the same group, thereby achieving batch processing of devices with similar difficulty. In another embodiment, grouping can be simply based on a threshold indicating the received signal strength. For example, devices with signal strength higher than a first threshold can be classified as a priority group, devices with signal strength between the first and second thresholds as a standard group, and devices with signal strength lower than the second threshold as an edge group. Furthermore, the location of the terminal devices to be upgraded in the network topology can also be considered; for example, terminal devices that communicate directly with the intelligent central control device and terminal devices requiring multi-hop relays can be classified into different groups.

[0029] Through this grouping and time-sharing mechanism, the intelligent central control device staggers the time of a massive number of devices that might otherwise initiate upgrade requests simultaneously. This not only effectively avoids instantaneous network channel congestion but also allows the intelligent central control device to concentrate resources to process specific groups of devices sequentially, thereby ensuring the stability and overall efficiency of the entire large-scale upgrade process at the system level.

[0030] Step S3300: Based on the device upgrade characteristics of each terminal device to be upgraded, divide the corresponding firmware package of each terminal device to be upgraded into multiple data fragments. After identifying the terminal devices to be upgraded and their grouping strategies, the intelligent central control device can perform firmware package fragmentation based on the device upgrade characteristics of each terminal device to be upgraded. This allows the large, complete firmware package to be divided into a series of smaller fragments to adapt to low-bandwidth networks and the transmission characteristics of the terminal devices to be upgraded, and to lay the foundation for subsequent round-robin calling and reliable transmission.

[0031] Device upgrade characteristics refer to the terminal device's own attributes that affect the execution method of the firmware upgrade process, and they determine the specific parameters of the fragmentation strategy. Device upgrade characteristics can be specified as one or more device characteristic parameters. In one embodiment, key device characteristic parameters include the available memory size of the terminal device. For devices with limited memory resources, the size of the fragmented data must be small enough to ensure it can be fully accommodated by the device's receive buffer, thereby enabling a streaming upgrade mode that processes data while receiving it. In another embodiment, the device characteristic parameter can be the device's power supply mode, such as distinguishing between battery power and constant power supply. For battery-powered devices, smaller fragment sizes and lower transmission rates can be used to minimize the active time of the radio frequency unit, thereby reducing the impact of the upgrade process on the device's battery life. In yet another embodiment, device characteristic parameters may also include the type of firmware verification algorithm supported by the device or the maximum allowed fragment size, which ensures that the fragmentation strategy is compatible with the device's processing capabilities.

[0032] Based on the acquired device characteristic parameters, the intelligent central control device can determine the transmission constraints when performing firmware upgrades on the corresponding terminal devices to be upgraded. These transmission constraints are rules that must be followed to ensure a successful upgrade, and they are directly derived from the device characteristic parameters. For example, the maximum allowable size of a single data fragment can be derived from the parameter of available memory size. The intelligent central control device then generates a corresponding fragmentation strategy based on the transmission constraints determined individually for each terminal device to be upgraded. The fragmentation strategy is a set of specific rules guiding how to segment the firmware package, and it at least defines the maximum allowable size of the data fragments. In more complex embodiments, the fragmentation strategy can also define the checksum generation algorithm for the data fragments, the method for calculating the starting offset of the fragments, etc.

[0033] Finally, the intelligent central control device, based on a fragmentation strategy generated individually for each terminal device to be upgraded, divides the corresponding cached local firmware package into multiple fragments conforming to the fragmentation strategy. These fragments are arranged in a specific order to form fragmented data sequences for subsequent transmission. Each fragment, in addition to containing the firmware data itself, can also include necessary control information, such as a sequence number identifying its position within the entire firmware package, and a checksum, such as a cyclic redundancy check (CRC), used to verify the integrity of the fragment.

[0034] Step S3400: In response to the arrival of the upgrade time, the fragmented data of different terminal devices to be upgraded are called in turn from the corresponding upgrade group and transmitted to the corresponding upgrade terminal.

[0035] Because the intelligent central control device sets an upgrade time for each group to be upgraded, it can execute the transmission of fragmented data in response to the arrival of the upgrade time. When the intelligent central control device detects that the preset upgrade time conditions are met, such as when the upgrade time window for a certain group to be upgraded opens, or when the dynamically adjusted time interval timer expires, it triggers the transmission operation of fragmented data for the corresponding group to be upgraded.

[0036] The intelligent central control device, following a specific scheduling mechanism, takes turns calling different terminal devices from the currently pending upgrade group to perform segmented data transmission. "Take turns" means that within a certain period, the intelligent central control device does not interact with all devices simultaneously, but rather follows a sequential access strategy, focusing on establishing communication connections and transmitting data with one or a limited number of target terminal devices at a time. In one embodiment, this scheduling can be based on a simple polling mechanism, proceeding sequentially according to a fixed order in the sequence. In another embodiment, priorities can be introduced, for example, prioritizing devices with better network transmission characteristics or more urgent upgrade tasks.

[0037] For each call, the goal of the intelligent central control device is to reliably transmit fragmented data to the target terminal device to be upgraded. This process includes establishing or reusing a communication connection with the target terminal device, retrieving the specific fragment to be transmitted from the prepared fragmented data sequence for that device, and sending it via a wireless link. To ensure transmission reliability, the intelligent central control device can monitor and record the transmission result status of each fragmented data transmission. For example, after sending a fragmented data, the intelligent central control device waits to receive the transmission result status from the device. If a transmission result status indicating successful reception is received within a predetermined time, the fragmented data transmission is marked as successful, and the device's transmission progress status is updated. If no transmission result status indicating successful reception is received, or a transmission result status indicating failure is received, the transmission is marked as failed, and a retransmission mechanism may be triggered.

[0038] Throughout the transmission process, the intelligent central control device continuously maintains the transmission status of each terminal device to be upgraded, such as the identifiers of successfully received fragmented data and the number of transmission failures. Based on this status information, in some embodiments, the intelligent central control device can make intelligent decisions. For example, when a fragmented data transmission fails, the intelligent central control device can re-enqueue it into the transmission sequence for retransmission. When all fragmented data of a terminal device to be upgraded has been successfully received, the intelligent central control device can remove it from the currently active device scheduling queue, thereby concentrating resources on devices that have not yet completed their upgrades. Furthermore, the intelligent central control device can also dynamically adjust parameters such as the time interval for round-robin calls based on real-time network conditions to achieve adaptive balancing of network load.

[0039] As can be seen from the above embodiments, the terminal device upgrade method provided in this application, through systematic and multi-level technological innovation, has achieved significant and multifaceted technical advantages compared to traditional firmware upgrade technologies, such as: The primary advantage lies in the fundamental improvement in transmission reliability. With traditional whole-packet transmission, any network fluctuation can cause the entire firmware package to fail, requiring a complete restart and resulting in a significant waste of time and network resources. This application refines the transmission granularity to the fragment level by dividing the firmware package into multiple data segments. The transmission time of a single fragment is extremely short, significantly reducing the probability of transmission failure due to network instability or device dormancy. Even if an individual fragment fails to transmit, only that specific fragment needs to be retransmitted, without affecting other successfully transmitted fragments. This greatly improves the success rate of a single upgrade attempt and significantly reduces the additional overhead caused by retransmissions.

[0040] Secondly, this application achieves a breakthrough in system-level efficiency optimization. In smart home networks where dozens or even hundreds of devices may need simultaneous upgrades, traditional methods either consume excessive time due to sequential upgrades or fail entirely due to network congestion caused by concurrent upgrades. This application introduces an intelligent grouping and time-sharing scheduling mechanism based on network transmission characteristics. By dividing devices into different upgrade groups and allocating independent upgrade time windows to each group, high-concurrency scenarios are successfully transformed into ordered low-concurrency or serial processing modes. This off-peak scheduling strategy avoids instantaneous overload of network channels at the system level, allowing network bandwidth resources to be utilized smoothly and efficiently, thus ensuring that large-scale device upgrade tasks can be carried out smoothly and stably, significantly shortening the overall upgrade cycle.

[0041] Furthermore, this application achieves refined and optimized resource utilization by introducing a personalized sharding strategy based on device upgrade characteristics. Traditional methods use uniform transmission parameters for all devices, which cannot adapt to the heterogeneity of IoT terminal devices in terms of memory, power consumption, and processing power. This application dynamically generates the most suitable sharding strategy for each terminal device to be upgraded, based on specific constraints such as available memory size and power supply mode. For example, smaller shards are set for devices with less memory, and a more energy-efficient transmission mode is adopted for battery-powered devices. This personalized approach not only ensures that all types of devices can be upgraded smoothly, but also minimizes the consumption of the devices' own resources, which is particularly beneficial to the long-term stable operation of battery-powered devices.

[0042] Furthermore, this application possesses a high degree of adaptability and intelligent management. The entire upgrade process is not statically executed, but rather forms a closed-loop system encompassing status monitoring, dynamic scheduling, and decision feedback. The intelligent central control device can track the transmission status of each segment in real time, achieving precise breakpoint resumption. Simultaneously, through real-time network health assessment, it can dynamically adjust the group size or the turnaround interval, achieving adaptive response to network conditions. This intelligent management capability enables this application to readily cope with complex and ever-changing real-world network environments, further enhancing its robustness and practicality.

[0043] Based on any embodiment of the method in this application, according to the firmware version information of each terminal device accessed via the target communication protocol, a request is made to the server to determine the terminal device to be upgraded and return the corresponding firmware to be upgraded, including: Step S3110: Collect device attribute information of all terminal devices that access the network using Zigbee as the target communication protocol, and generate a device list. The device attribute information includes the unique identifier of the terminal device and its current firmware version number. Before initiating the upgrade process, the intelligent central control device first identifies the terminal devices to be upgraded and obtains the corresponding firmware resources. To this end, the intelligent central control device first generates a device list, collecting device attribute information from all terminal devices under its jurisdiction that are connected to a private network using Zigbee as the target communication protocol. Device attribute information is a set of data describing the identity and current software state of the terminal devices, including at least a unique identifier that can uniquely distinguish different terminal devices, and the current firmware version number that identifies the firmware version currently running on the terminal device.

[0044] Intelligent central control devices can acquire this information actively or passively in various ways. For example, they can periodically broadcast query requests and collect responses from each device, or continuously monitor information proactively reported by terminal devices when they come online, have a heartbeat, or experience status changes. After acquiring this information, the collected device attribute information is summarized and organized into a structured device list for provision to the server.

[0045] Step S3120: Send an upgrade strategy request to the server. The request includes the device list. The server determines the terminal devices to be upgraded in the device list and their upgrade tasks containing target firmware information based on the unique identifier and the current firmware version number. After generating a local device list, the intelligent central control device sends an upgrade policy request to a remote server to leverage the server's superior computing and storage capabilities for upgrade decisions. The upgrade policy request sent by the intelligent central control device to the server includes the device list generated in the aforementioned steps.

[0046] Upon receiving a request, the server executes its pre-defined upgrade logic. The server typically maintains a knowledge base containing the latest firmware for different terminal devices and their applicable conditions. The server compares the unique identifier and current firmware version number of each terminal device in the device list with the information in the server's knowledge base. In one embodiment, the server determines the device model and its applicable latest firmware version based on the unique identifier. If the current firmware version number is lower than this latest version, the terminal device is determined to be the one requiring upgrade.

[0047] Then, based on the target firmware information, including the version number of the corresponding latest firmware version, an upgrade task is constructed for each corresponding terminal device to be upgraded. This upgrade task clarifies which terminal devices need to be upgraded. The target firmware information indicates the specific source of the required firmware package. In one embodiment, this information can be the binary data of the firmware package itself, directly distributed by the server along with the upgrade task. In another embodiment, the target firmware information is essentially an access credential pointing to the storage location of the firmware package, such as an encrypted download link or a token. The intelligent central control device can use this access credential to initiate a download request to the server or a designated file server, transferring the complete firmware package to its local machine. Furthermore, in the latter embodiment, the target firmware information may also include information such as the firmware size, hash checksum, or applicable hardware version range of the corresponding firmware package.

[0048] Step S3130: Download the firmware package corresponding to the terminal device to be upgraded from the server according to the target firmware information specified in the upgrade task.

[0049] After receiving the upgrade task from the server, the intelligent central control device parses it to obtain the target firmware information. If the target firmware information contains binary data of the firmware package, the binary data can be obtained directly. If the target firmware information is an access credential, the firmware package can be downloaded based on the access credential. Regardless of the method used, after successfully obtaining the firmware package, the intelligent central control device properly caches it on local non-volatile storage media. This ensures that during the potentially time-consuming segmented transmission phase, the intelligent central control device does not need to rely on a stable connection to the cloud server. All data transmission is completed within the local private network, thereby greatly improving the independence, efficiency, and reliability of the upgrade process.

[0050] Through the above embodiments, this application achieves accurate identification of the terminal device to be upgraded and reliable preparation of firmware resources by leveraging the collaborative division of labor between the intelligent central control device and the server. The intelligent central control device is responsible for collecting local information and final execution, while the server focuses on version management and policy decisions. This architecture fully utilizes the advantages of each component. In particular, the design of pre-caching the firmware package locally confines a large amount of subsequent network transmission activities to a low-bandwidth private network, effectively reducing reliance on wide area network connections and the risks associated with potential fluctuations, thus facilitating the smooth and reliable execution of the entire large-scale upgrade task.

[0051] Based on any embodiment of the method in this application, and based on the network transmission characteristics of each terminal device to be upgraded, the terminal devices to be upgraded are divided into multiple groups corresponding to different upgrade times, including: Step S3210: For each terminal device to be upgraded corresponding to the upgrade task, collect network status indicators to define its network transmission characteristics. The network status indicators include any one or more of the following: signal strength, packet loss rate, and data packet round-trip time between the terminal device to be upgraded and the current device. To perform intelligent grouping, the intelligent central control device first needs to collect objective and quantifiable network status indicators for each terminal device to be upgraded in the upgrade task. These indicators collectively define the network transmission characteristics of the communication link between the device and the central control device.

[0052] The network status indicators collected by intelligent central control devices are diverse, aiming to characterize link status from different dimensions. These indicators include, but are not limited to, the following: signal strength, which directly reflects the strength of the wireless signal; a higher value (smaller absolute value) indicates better signal quality; packet loss rate, which is the proportion of continuously transmitted probes or packets lost, directly revealing the stability and reliability of the link; and packet round-trip time, which is the time elapsed from sending a request to receiving a response, reflecting the real-time nature of communication and the degree of link congestion. Intelligent central control devices can collect one or more of these indicators for each terminal device to be upgraded, thereby obtaining a more comprehensive network profile corresponding to that specific terminal device.

[0053] The specific implementation methods for collecting these network status indicators are flexible and diverse. In one embodiment, the intelligent central control device can adopt an active probing approach. In another embodiment, the intelligent central control device can perform passive analysis based on historical communication data. A communication quality database can be maintained to record information such as signal strength, number of data packet retransmissions (which can indirectly reflect packet loss rate), and response time during recent interactions with each terminal device. When packet processing is required, statistical values ​​of these historical data, such as average values ​​or sliding window average values, can be directly called as an estimate of the current network status indicators. This method eliminates the need to send additional probe packets, reducing network overhead. Step S3220: Determine the upgrade difficulty factor of the corresponding terminal device to be upgraded based on the network status indicators; After successfully collecting network status indicators reflecting the network transmission characteristics of each terminal device to be upgraded, the intelligent central control device integrates these multi-dimensional and potentially different units of raw data into a single quantitative value that comprehensively characterizes the expected ease or resource consumption of firmware upgrades for the terminal device—the upgrade difficulty factor. The upgrade difficulty factor can be implemented so that its value directly indicates the expected challenge of the upgrade process; a higher value generally indicates a greater upgrade difficulty.

[0054] The specific algorithm for determining the upgrade difficulty factor can be flexibly designed based on different optimization objectives and network models. In one embodiment, the upgrade difficulty factor can simply be the value of a key network status indicator itself or its linear transformation. For example, the percentage value of packet loss rate or the result of normalizing the millisecond value of packet round-trip time can be defined as the upgrade difficulty factor of the device. This method is simple to calculate, but it only considers the impact of a single dimension.

[0055] In another embodiment, the upgrade difficulty factor can be calculated by weighted fusion of multiple network status indicators. The intelligent central control device can preset a weight configuration model, which assigns a weight coefficient to each selected network status indicator. This coefficient reflects the importance of the indicator to the success of the upgrade. For example, in a typical weight configuration, packet loss rate may be given the highest weight because it is the most direct manifestation of link stability and has the greatest impact on transmission success rate; secondly, packet round-trip delay affects transmission efficiency and the timeliness of control response; signal strength may be given a relatively low weight, or given a basic weight because it is already implicitly included by packet loss rate and delay to some extent. During calculation, the intelligent central control device first standardizes the values ​​of each indicator to eliminate the influence of dimensions, and then calculates according to the formula Upgrade Difficulty Factor = W1 * Standardized Packet Loss Rate + W2 * Standardized Round-Trip Delay + W3 * Standardized Signal Strength, where W1, W2, and W3 are preset weight coefficients, and usually satisfy the relationship W1 > W2 > W3.

[0056] In more complex embodiments, the model determining the upgrade difficulty factor can be non-linear, such as using a machine learning model trained on historical upgrade success data. This model takes multiple network state metrics as input features and outputs a predicted upgrade difficulty factor or a directly predicted success probability, the reciprocal or complement of which can be considered the upgrade difficulty factor. This approach can capture the complex interactions between metrics.

[0057] Step S3230: Determine the difficulty frequency band to which each terminal device to be upgraded belongs based on the upgrade difficulty factor and assign it to the same upgrade group corresponding to that difficulty frequency band; After obtaining the upgrade difficulty factor for each terminal device to be upgraded, the intelligent central control device can categorize all terminal devices to be upgraded based on these factors, so as to process devices with similar upgrade difficulties together. First, the difficulty frequency band to which each terminal device to be upgraded belongs can be determined based on the upgrade difficulty factor, and devices belonging to the same difficulty frequency band can be grouped into the same upgrade group. The difficulty frequency band can be defined by a numerical range, dividing the continuous range of upgrade difficulty factor values ​​into several discrete segments with clear boundaries, each segment representing a specific upgrade difficulty level.

[0058] The specific strategy for determining the difficulty frequency bands can be flexibly implemented based on the distribution of upgrade difficulty factors of the device group and the optimization objectives. In one embodiment, the equal-width binning method can be used. The intelligent central control device first determines the number K of difficulty frequency bands to be divided, and then finds the minimum value Min and the maximum value Max among the upgrade difficulty factors of all terminal devices to be upgraded. Subsequently, the entire numerical range [Min, Max] is divided into K consecutive intervals, and the width of each interval is (Max-Min) / K. For example, if K=3, then three difficulty frequency bands of low, medium and high difficulty are naturally formed.

[0059] In another embodiment, the equal-frequency binning method, also known as the quantile binning method, can be used. The intelligent central control device first determines the number K of difficulty frequency bands, aiming to ensure that the number of terminal devices to be upgraded within each difficulty frequency band is approximately equal. Specifically, the intelligent central control device sorts all terminal devices to be upgraded according to their upgrade difficulty factor values ​​from smallest to largest, and then finds the corresponding quantile points. For example, if K=3, then the 33.3% and 66.6% quantile points are found, roughly dividing the sorted device list into three equal parts, thus defining three difficulty frequency bands. This method ensures a balanced number of devices within each group, which is more conducive to subsequent load balancing scheduling.

[0060] In more complex implementations, the division of difficulty frequency bands can be based on clustering algorithms, such as K-Means clustering. The intelligent central control device uses the upgrade difficulty factor values ​​of all terminal devices to be upgraded as input features, and automatically aggregates them into K categories using a clustering algorithm. Devices within each category have high similarity in upgrade difficulty factors, while there are significant differences between different categories. The algorithm's final output—the center value and boundary of each category—naturally forms the K difficulty frequency bands. This method can adaptively group data according to its inherent distribution characteristics without requiring pre-defined fixed division rules.

[0061] Once the difficulty frequency bands are determined, whether through equal width, equal frequency, or clustering methods, the intelligent central control device performs a partitioning operation. It compares the upgrade difficulty factor value of each terminal device to be upgraded with the numerical range of each difficulty frequency band, and assigns it to the corresponding difficulty frequency band based on the range it falls into. Subsequently, the intelligent central control device groups all terminal devices to be upgraded belonging to the same difficulty frequency band into the same upgrade group. This completes the device grouping based on the upgrade difficulty factor.

[0062] Step S3240: Assign different upgrade time windows to different groups to be upgraded, wherein the upgrade difficulty factor indicates that the upgrade difficulty of the group to be upgraded is assigned a higher priority or earlier time upgrade time window.

[0063] After successfully classifying the terminal devices to be upgraded into different upgrade groups based on their upgrade difficulty factor, the intelligent central control device needs to allocate different upgrade time windows to these groups to achieve peak scheduling in the time dimension. An upgrade time window refers to a time period allocated to an upgrade group, with a clear start and end time. During this time period, the intelligent central control device will focus on executing firmware fragment transmission tasks for the devices within that group.

[0064] In one embodiment, the intelligent central control device can allocate higher priority or earlier upgrade time windows to the upgrade group containing devices with lower upgrade difficulty factors. Higher priority here can be reflected in an earlier start time window, such as scheduling it during the earlier part of the network's off-peak hours at night; while earlier timing directly refers to the start time of the upgrade time window being ahead of other groups in sequence. The optimization goal of this strategy is to prioritize and quickly complete the upgrades of devices expected to upgrade smoothly and quickly, thereby releasing network resources as early as possible and allowing more time and a more stable network environment for subsequent upgrade groups with higher difficulty factors. For example, the upgrade time window for the upgrade group consisting of devices in frequency bands with lower upgrade difficulty factors can be scheduled between midnight and 2 AM when network load is lightest; the window for the medium-difficulty frequency band group can be between 2 AM and 4 AM; and the window for the high-difficulty frequency band group can be between 4 AM and 6 AM.

[0065] The specific strategy for allocating upgrade time windows can be flexibly implemented. In one embodiment, the intelligent central control device can adopt a static pre-allocation method. Based on a preset scheduling strategy and historical network load patterns, the intelligent central control device allocates a fixed upgrade time window to each group to be upgraded. For example, the low-difficulty group is always scheduled for the earliest fixed time slot each day. In another embodiment, the allocation can be somewhat dynamic. Before each upgrade task is executed, the intelligent central control device dynamically calculates and allocates the upgrade time window for each group based on factors such as the overall task load of the current system and the estimated total upgrade time. For example, if the number of devices to be upgraded is small, the intelligent central control device can tightly schedule the windows for all groups on the same night; if the number of devices is large, it may be necessary to distribute the upgrade task across multiple consecutive nights.

[0066] When allocating upgrade time windows, the intelligent central control device can also consider the duration of the upgrade time window. The window length can be associated with the estimated total upgrade time for the corresponding group to be upgraded. In one embodiment, a fixed-length window can be allocated to each group, for example, two hours. In another embodiment, the window length can be dynamically determined based on the number of devices in the group, the total size of the firmware package, and the average upgrade difficulty factor of the group. For example, a longer window can be allocated to groups with a large number of devices and large firmware packages to ensure that they have sufficient time to complete the upgrade.

[0067] Through the above embodiments, this application achieves significant technical advantages in system-level resource optimization and reliability improvement when addressing network congestion and inefficiency caused by large-scale terminal device upgrades. This embodiment enables the intelligent central control device to automatically classify heterogeneous device groups based on objective network condition data and schedule them for processing at the most suitable time slots, effectively avoiding peak periods and preventing low-quality link devices from hindering the overall upgrade process. It prioritizes the rapid release and utilization of high-quality link resources, thereby maximizing the throughput of upgrade tasks and ensuring a robust overall success rate in complex network environments.

[0068] Based on any embodiment of the method in this application, and based on the device upgrade characteristics of each terminal device to be upgraded, the corresponding firmware package of each terminal device to be upgraded is divided into multiple data fragments, including: Step S3310: For each terminal device to be upgraded in the upgrade task, obtain the device characteristic parameters corresponding to one or more device upgrade characteristics. To implement personalized segmentation strategies for different terminal devices, the intelligent central control device first needs to obtain specific device characteristic parameters corresponding to one or more device upgrade features for each terminal device to be upgraded in the upgrade task. Device upgrade features are the inherent attributes of the terminal device that affect the firmware upgrade execution method, and these features need to be specifically characterized by quantified device characteristic parameters so that they can be identified and processed by the intelligent central control device.

[0069] Device characteristic parameters are numerical or categorical identifiers describing the key capabilities and limitations of a terminal device during firmware upgrades. These parameters are diverse and designed to characterize the constraints of the device's upgrade behavior from different dimensions. One device characteristic parameter is the available memory size of the terminal device. This parameter directly determines the device's buffering capacity when receiving firmware fragment data. For devices with limited memory resources, the size of the fragment data must be strictly controlled to ensure that it can be received and processed completely. Another optional device characteristic parameter is the device's power supply mode, such as explicitly distinguishing between battery power and continuous power supply. This parameter affects the device's energy consumption requirements during the upgrade process. For battery-powered devices, more energy-efficient transmission strategies are required. In addition, device characteristic parameters may also include the specific firmware verification algorithm type supported by the device, such as whether cyclic redundancy check or a more complex hash algorithm is used, which relates to the integrity verification method of fragment data; or the maximum allowed fragment size specified by the device manufacturer, which directly limits the upper limit of the amount of data transmitted in a single transmission.

[0070] The specific methods by which intelligent central control devices obtain these device characteristic parameters are flexible and diverse. In one embodiment, the intelligent central control device can obtain them through active querying. In another embodiment, the parameter information can be obtained through passive reception.

[0071] In another implementation, the intelligent central control device can maintain a local device information database. For terminal devices of known models, their typical device characteristic parameters (such as standard memory size, power supply mode, etc.) can be pre-stored in the local database. When it is necessary to obtain the parameters of a certain device, the intelligent central control device can directly query the local database based on the device's unique identifier or model information. This method is efficient and does not increase real-time network communication overhead.

[0072] Step S3320: Based on the device characteristic parameters, determine at least one transmission constraint condition when performing firmware upgrade on the corresponding terminal device to be upgraded; After successfully acquiring the device characteristic parameters of each terminal device to be upgraded, the intelligent central control device can deduce the operational constraints that must be followed when performing firmware upgrades based on these specific parameters. In other words, it determines the transmission constraints when performing firmware upgrades on the corresponding terminal devices. Transmission constraints are hard rules or boundary conditions set to ensure the successful completion of the upgrade process, and they are directly derived from the physical characteristics and functional limitations of the device.

[0073] The process of determining transmission constraints essentially involves translating device characteristic parameters into explicit engineering rules. In one embodiment, transmission constraints can be directly mapped to a key device characteristic parameter. For example, from the device characteristic parameter of the available memory size of the terminal device, the crucial transmission constraint of the maximum allowable size of a single data fragment can be directly derived. This transmission constraint stipulates that the size of any data fragment generated by the intelligent central control device must not exceed the available memory size of the terminal device, ensuring that the device has sufficient buffer space to receive and temporarily store the data fragment, thereby enabling streaming processing and avoiding reception failures due to insufficient memory.

[0074] In another embodiment, the transmission constraints can be the result of a comprehensive judgment based on multiple device characteristic parameters. For example, combining the device's power supply mode (battery powered) and available memory size, the intelligent central control device may, in addition to determining the maximum allowable size of the fragmented data, also derive additional constraints, such as limiting the maximum number of fragmented data transmitted continuously or specifying the minimum length of the transmission interval, in order to control the active time of the radio frequency unit, reduce overall power consumption, and meet the battery life requirements of battery-powered devices.

[0075] The specific content and stringency of transmission constraints depend entirely on the acquired device characteristic parameters. For readily available, constantly powered equipment with ample resources, transmission constraints can be relatively lenient, focusing primarily on transmission efficiency. However, for battery-powered equipment with limited resources, transmission constraints can be more stringent and complex, requiring a delicate balance between reliability, efficiency, and energy consumption.

[0076] Step S3330: Generate a corresponding fragmentation strategy based on the transmission constraints determined for each terminal device to be upgraded. The fragmentation strategy defines the maximum allowed size of fragmented data. After defining the transmission constraints for each terminal device to be upgraded, the intelligent central control device tailors a unique fragmentation strategy for each device based on these constraints. The fragmentation strategy is a specific, executable set of rules that directly guides how to securely and efficiently divide the complete firmware package into fragments suitable for the device's reception. The most crucial element of the fragmentation strategy is defining the maximum allowable size of the fragmented data. This value is directly determined by the limitations on the size of individual fragments in the transmission constraints, such as strictly adhering to the upper limit derived from the available memory size of the terminal device.

[0077] The intelligent central control device independently generates a corresponding fragmentation strategy for each terminal device to be upgraded. In one embodiment, the generated fragmentation strategy can be relatively simple, with its main content, or even its only hard requirement, being the maximum allowed size of the fragmented data. The intelligent central control device directly sets the maximum allowed size value specified in the device's transmission constraints as the maximum allowed size parameter for the fragmented data in the fragmentation strategy. For example, if a device has 4KB of available memory, the generated fragmentation strategy stipulates that the size of each subsequently divided fragment of data must not exceed 4KB.

[0078] In more comprehensive and optimized embodiments, the generated fragmentation strategy can include more configuration parameters beyond the maximum allowed size to finely control the fragmentation and transmission process. These parameters can also stem from in-depth analysis of device characteristic parameters and their derived transmission constraints. In one embodiment, the fragmentation strategy can specify the checksum generation algorithm for the fragmented data. For example, if device characteristic parameters indicate that the device only supports simple cyclic redundancy check (CRC), the fragmentation strategy specifies that this algorithm is used to generate checksums for each fragment; if the device supports more secure hash algorithms, the strategy can specify the use of SHA-256, etc. In another embodiment, the fragmentation strategy can define special fragment sequence arrangement rules. For example, for battery-powered devices, their transmission constraints may implicitly include specific requirements for transmission efficiency. The fragmentation strategy can include instructions to interleave the fragmented data sequence or add redundant fragments to improve transmission robustness on unreliable links, reduce the overall number of retransmissions, and thus indirectly achieve energy savings.

[0079] The specific implementation of generating a sharding strategy can be based on predefined strategy templates and a rule engine. The intelligent central control device can maintain a strategy rule base, which defines the mapping relationship between different combinations of device characteristic parameters and sharding strategy parameters. When a sharding strategy needs to be generated for a device, the intelligent central control device takes its device characteristic parameters or transmission constraints as input, queries the rule base, matches and instantiates the corresponding strategy template, thereby outputting a complete sharding strategy object.

[0080] Step S3340: According to the fragmentation strategy generated individually for each terminal device to be upgraded, the corresponding firmware package is divided into multiple fragmented data sequences that conform to the fragmentation strategy for transmission.

[0081] After the intelligent central control device generates a corresponding fragmentation strategy for each terminal device to be upgraded, it enters the actual firmware package partitioning stage. Based on the fragmentation strategy tailored for each terminal device to be upgraded, the intelligent central control device divides the corresponding complete firmware package, which is already cached locally, into a series of fragment data that conform to the fragmentation strategy specification.

[0082] The partitioning operation is based on the key parameter of the maximum allowed size of the partitioned data defined in the partitioning strategy. The intelligent central control device reads the target firmware package and, according to the maximum allowed size specified in the partitioning strategy, sequentially cuts the binary data stream of the firmware package into multiple data blocks. In one embodiment, except for the last partitioned data, the size of the remaining partitioned data is strictly equal to the maximum allowed size, and the last partitioned data contains the remaining data that is less than the size of a complete block.

[0083] For each data segment, the intelligent central control device can append necessary control information to form a complete data segment unit. The addition of this control information also follows the segmentation strategy. In one embodiment, the intelligent central control device assigns a consecutive sequence number to each data segment, which identifies the segment's order within the original firmware package. In another embodiment, the intelligent central control device can calculate a checksum for the data segment content, such as a cyclic redundancy check (CRC) or a hash value, according to a checksum generation algorithm specified by the segmentation strategy, and append this checksum to the data segment. This allows the device to verify the integrity of the received data segment.

[0084] All data fragments allocated to the same terminal device to be upgraded are arranged in sequence according to their serial numbers, forming a data fragment sequence unique to that device. This data fragment sequence represents an ordered, manageable, and device-received transformation of the original firmware package. The intelligent central control device stores this data fragment sequence in local memory or non-volatile storage, associates it with the corresponding terminal device to be upgraded, marks it as ready for transmission, and waits for the upgrade time window of its respective upgrade group to arrive before transmission.

[0085] The embodiments described above in this application further achieve technical advantages in refined management and optimal resource allocation in solving the firmware upgrade compatibility problem. This embodiment enables the intelligent central control device to deeply perceive and respect the individual differences and inherent limitations of each terminal device, thereby generating and executing a segmented data transmission scheme that truly matches the actual receiving capabilities and energy consumption of the device to be upgraded. This fundamentally avoids problems such as device-side reception failure, resource waste, or shortened battery life caused by a one-size-fits-all approach to transmission parameters, significantly improving the universal applicability, success rate, and energy efficiency of the upgrade process for heterogeneous device groups.

[0086] Based on any embodiment of the method in this application, in response to the arrival event of the upgrade time, the fragmented data of different terminal devices to be upgraded from the corresponding upgrade group is called in turn and transmitted to the corresponding upgrade terminal, including: Step S3410: Respond to the arrival event of the upgrade time window of any upgrade group and generate a device scheduling sequence for all terminal devices to be upgraded in the upgrade group; When the intelligent central control device detects that the preset upgrade time window for a certain upgrade group has arrived, it triggers the specific upgrade operation for the devices in that group. In response to this event, the intelligent central control device first generates a device scheduling sequence for all terminal devices in the upgrade group. The device scheduling sequence is implemented as a list defining the order in which devices within the group are processed. The strategy for generating this sequence can be varied. In one embodiment, a simple round-robin order can be used, i.e., arranged according to the lexicographical order or the order in which the unique identifiers of the terminal devices to be upgraded are entered into the database. In another embodiment, a priority mechanism can be introduced, for example, placing devices with better network transmission characteristics and lower upgrade difficulty factors at the front of the sequence, in order to prioritize the completion of upgrade tasks that are expected to be smoother, thereby quickly releasing network resources.

[0087] Step S3420: According to the device scheduling sequence, the target terminal device to be upgraded is determined in turn in the device scheduling sequence. The fragmented data to be transmitted is taken out from the fragmented data sequence prepared by the target terminal device to be upgraded and sent to the target terminal device to be upgraded. The transmission result status of the fragmented data is monitored and recorded accordingly. After generating the device scheduling sequence, the intelligent central control device begins executing round-robin calling and data transmission operations. Following the order defined in the device scheduling sequence, the intelligent central control device sequentially determines the target terminal device to be upgraded that needs to be processed. Round-robin calling means that within a certain period, the intelligent central control device does not process all devices in the sequence simultaneously, but rather follows the principle of sequential access, focusing on communicating and interacting with one target terminal device at a time.

[0088] After identifying the target terminal device to be upgraded, the intelligent central control device establishes or reuses a stable communication connection with it. Next, the intelligent central control device extracts the specific data fragment to be transmitted from a pre-prepared data fragment sequence for the target terminal device. This fragment is typically the one with the smallest sequence number in the device's data fragment sequence that has not yet been marked as successfully transmitted. The intelligent central control device then sends the extracted data fragment to the target terminal device via its private network.

[0089] Simultaneously or subsequently, the intelligent central control device can initiate a monitoring process for this transmission and record its transmission result status accordingly. The transmission result status is information used to characterize the final result of this fragmented data transmission attempt. In one embodiment, after sending the fragmented data, the intelligent central control device starts a timer and waits to receive an acknowledgment signal from the target terminal device to be upgraded. If an acknowledgment signal is successfully received within the timeout period corresponding to the fragmented data, the intelligent central control device records the transmission result status as successful. In another embodiment, if no acknowledgment signal is received within the timeout period, or if a negative acknowledgment signal is received from the device, the transmission result status is recorded as failed. The intelligent central control device closely associates and records this transmission result status with the specific fragmented data and the target terminal device to be upgraded, providing a basis for subsequent judgment and decision-making.

[0090] After completing the transmission and status recording of a segment of data for the current target terminal device to be upgraded, the intelligent central control device does not immediately wait for the device to complete its response. Instead, it switches to the next target terminal device to be upgraded according to the device scheduling sequence, repeating the same process of identifying the device, retrieving data, sending data, and recording its status. This segmented, round-robin scheduling mechanism allows network bandwidth resources to be rapidly rotated among multiple devices, effectively preventing a single device from monopolizing the channel for an extended period due to poor link quality or slow processing. This improves the fairness of network utilization and the efficiency of the overall upgrade process at a micro level.

[0091] Step S3430: Determine whether the corresponding fragmented data has been received by the corresponding target terminal device to be upgraded based on the transmission result status. If it has not been successfully received, add the fragmented data back into the corresponding fragmented data sequence for retransmission. The intelligent central control device determines whether the corresponding data fragment has been successfully received by the target terminal device to be upgraded based on the recorded transmission result status. If the transmission result status indicates successful transmission, such as receiving an acknowledgment signal, the intelligent central control device marks the data fragment as successfully transmitted and updates the device's progress status. If the transmission result status indicates unsuccessful reception, such as timeout without acknowledgment or receiving a negative acknowledgment, the transmission is considered a failure. For data fragments that fail to transmit, the intelligent central control device does not discard them but executes a retransmission mechanism, that is, re-adding the data fragment to its corresponding data fragment sequence, usually placing it at the end of the sequence or inserting it at a specific position according to a strategy, so that it can be retried in subsequent round-robin calls.

[0092] Step S3440: When all fragmented data in any fragmented data sequence is successfully received, remove it from the device scheduling sequence of the corresponding terminal device to be upgraded.

[0093] As the upgrade process progresses, the intelligent central control device continuously tracks the data reception status of each terminal device to be upgraded. When it detects that all data fragments in the data fragment sequence corresponding to a terminal device to be upgraded have been successfully received, it indicates that the entire firmware package for that device has been delivered completely. At this point, the intelligent central control device determines that the upgrade data transmission phase for that device is complete. Subsequently, the intelligent central control device removes the terminal device to be upgraded from the currently active device scheduling sequence. This removal operation means that the device will no longer be selected in subsequent round-robin scheduling processes, allowing the intelligent central control device to concentrate its computing and communication resources on other devices in the sequence that have not yet completed their upgrades, optimizing resource utilization and improving overall scheduling efficiency.

[0094] Through the above embodiments, this application achieves highly automated and intelligent scheduling management at the core execution level. This embodiment transforms large-scale upgrade tasks into refined, device-level controllable operations, avoids network congestion through orderly round-robin calls, ensures complete data delivery through a reliable retransmission mechanism, and optimizes resource allocation through dynamic sequence management. As a result, it significantly improves the overall execution efficiency, success reliability, and system resource utilization of upgrade tasks in complex network environments.

[0095] Based on any embodiment of the method in this application, in response to the arrival event of the upgrade time, the fragmented data of different terminal devices to be upgraded from the corresponding upgrade group is called in turn and transmitted to the corresponding upgrade terminal, including: Step S4100: During the process of performing fragmented data transmission, continuously monitor the real-time performance indicators of the current network constructed by the target communication protocol. The real-time performance indicators include the average packet loss rate and / or the average round-trip time of data packets. During the execution of fragmented data transmission, the intelligent central control device can simultaneously and continuously monitor and evaluate the network status in real time. The intelligent central control device continuously monitors the real-time performance indicators of the current private network constructed by the target communication protocol. These real-time performance indicators are key parameters reflecting the immediate operational status of the network, and include at least one or more of the following: average packet loss rate and average round-trip time (RTT). The average packet loss rate can be calculated by statistically analyzing the proportion of data packets sent to multiple devices within a recent time window without receiving acknowledgments, directly reflecting the network's reliability. The average RTT measures the average time required from sending a request to receiving a response, reflecting the network's congestion level and transmission efficiency. By periodically sampling and calculating these indicators, the intelligent central control device gains continuous awareness of the network's health.

[0096] Step S4200: Determine the network health score based on the real-time performance indicators. When the network health score is lower than the first preset threshold, split the currently executing transmission into multiple subgroups and generate a new device scheduling sequence and upgrade time window for each subgroup. Based on the collected real-time performance metrics, the intelligent central control device further determines a comprehensive network health score. This score is a quantitative value that integrates multiple real-time performance metrics, used to intuitively represent the overall condition of the network. In one embodiment, the network health score can be calculated by weighted averaging of the various real-time performance metrics.

[0097] The intelligent control device compares the calculated network health score with a preset first threshold. This first threshold, which can be pre-set, defines a critical point where the network condition has deteriorated to the point requiring aggressive adjustment measures. When the network health score falls below the first preset threshold, it indicates that the network may be experiencing severe congestion or interference, and the current transmission group size is too large. At this time, the intelligent control device performs dynamic group adjustment, that is, splitting the currently transmitting group to be upgraded into multiple smaller subgroups. For example, splitting a group containing 20 devices into two subgroups each containing 10 devices. Simultaneously, the intelligent control device allocates a new upgrade time window to each newly generated subgroup, such as evenly distributing the remaining upgrade time of the original group between the two subgroups, or rescheduling their subsequent upgrade periods. This group splitting strategy fundamentally alleviates network pressure by reducing concurrency.

[0098] Step S4300: Compare the network health score with a second preset threshold, and dynamically adjust the time interval of the round-robin calls based on the comparison result; wherein, when the network health score decreases, the upgrade time interval for switching different terminal devices to be upgraded in the device scheduling sequence is increased accordingly.

[0099] Simultaneously, the intelligent central control device compares the network health score with a second preset threshold, which can also be preset to be higher than the first preset threshold, to trigger more refined traffic control. Based on the comparison results, the intelligent central control device dynamically adjusts the time interval for rotating calls, that is, controlling how long to wait after the previous target terminal device to be upgraded finishes transmitting before switching to the next device in the device scheduling sequence.

[0100] A specific adjustment strategy could be to increase the upgrade interval between different terminal devices in the device scheduling sequence when the network health score decreases. For example, when the network health score drops from good to average, the intelligent central control device will increase the turnaround time interval from 100 milliseconds to 200 milliseconds. When the score further decreases to near a first preset threshold, the time interval may increase to 500 milliseconds. This adaptive interval adjustment is equivalent to intelligently throttling the data flow, proactively reducing the transmission rate when network conditions are poor, leaving room for network recovery, thereby smoothing network load and preventing further deterioration.

[0101] The above embodiments enable intelligent central control devices to transcend static preset strategies, proactively perceive changes in network status, and intelligently adopt hierarchical response measures ranging from macro-level packet splitting to micro-level traffic throttling when performance degradation is detected. This ensures that the upgrade task can continue even when network conditions fluctuate or deteriorate, effectively avoiding upgrade process stagnation or large-scale failures caused by network congestion. This greatly enhances the system's robustness, survivability, and overall task completion rate in real, uncontrollable network environments.

[0102] Based on any embodiment of the method in this application, the method further includes: Step S5100: Respond to the progress tracking command, generate and display the upgrade progress viewing panel, which provides summary information on the transmission progress of the terminal device to be upgraded; In addition to monitoring and managing the upgrade process, the intelligent central control device also responds to received progress tracking commands, which can originate from user interaction or system scheduled tasks. Upon response, the intelligent central control device generates and displays an upgrade progress view panel. This panel provides administrators or users with a summary of the transmission progress of the ongoing large-scale upgrade task, which involves a large number of terminal devices to be upgraded, transforming the upgrade process from a black box to a white box and improving observability.

[0103] Step S5200: Continuously collect and aggregate real-time status data from each terminal device to be upgraded. The real-time status data includes: the number of fragmented data that each terminal device to be upgraded has successfully received, determined based on the transmission result status of the fragmented data. To provide accurate data to the upgrade progress monitoring panel, the intelligent central control device continuously collects and aggregates real-time status data from each terminal device to be upgraded. Key real-time status data includes the number of data segments successfully received by each terminal device, determined based on the transmission results of the segmented data. For example, the intelligent central control device records that device A has successfully received 50 data segments, and device B has successfully received 30 data segments. This data is collected by continuously monitoring communication interactions with each device and obtaining transmission result statuses, and is continuously updated over time.

[0104] Step S5300: Based on the collected real-time status data, dynamically calculate at least one of the following progress information as transmission progress summary information and update it to the upgrade progress viewing panel: the transmission completion percentage of a single terminal device to be upgraded, the overall transmission completion rate of the group to be upgraded, and the estimated remaining upgrade time. After obtaining the raw real-time status data, the intelligent central control device further dynamically calculates more business-meaning progress information based on the collected real-time status data, and updates this information as a summary of transmission progress in the upgrade progress viewing panel. The calculated progress information includes, but is not limited to, at least one of the following: the transmission completion percentage of a single terminal device to be upgraded, which is calculated by the ratio of the number of fragmented data successfully received by the device to its total number of fragmented data, intuitively displaying the completion rate of a single device; the overall transmission completion rate of the upgrade group to which it belongs, which is obtained by calculating the ratio of the total number of fragmented data successfully received by all devices in the group to the total number of fragmented data of these devices, reflecting the macro-level progress at the group level; and the estimated remaining upgrade time, which can be predicted and estimated based on the historical average transmission rate, the total amount of data to be transmitted, and the current network health status, providing time expectations for management.

[0105] Step S5400: Monitor the real-time status data, and when a predefined abnormal state is identified, generate and report abnormal alarm information.

[0106] Furthermore, the intelligent central control device also performs proactive anomaly monitoring. It continuously monitors the aggregated real-time status data and identifies abnormal states based on predefined rules. These predefined abnormal states are clearly defined conditions that indicate the upgrade process may deviate from its normal trajectory. In one embodiment, an abnormal state could be that a specific terminal device to be upgraded experiences more than a set threshold of consecutive fragment transmission failures, indicating that the device may be disconnected or that there is a serious problem with the link. In another embodiment, an abnormal state could be that the upgrade progress of a device remains unchanged for an extended period, i.e., the progress is stalled. When the intelligent central control device detects any predefined abnormal state being triggered, it immediately generates a structured anomaly alarm message, which includes the abnormal device identifier, anomaly type, and timestamp, and reports it to the upper-level management system or notifies relevant personnel, thus achieving an upgrade from passive monitoring to proactive alarming.

[0107] Through the above embodiments, this application has achieved significant technical advantages in improving the management efficiency and controllability of large-scale upgrade tasks. This embodiment transforms the complex underlying transmission process into intuitive and quantifiable business insights, possessing the ability to proactively discover potential problems. It greatly enhances the perception, intervention, and decision support capabilities of operations and maintenance personnel regarding the upgrade process, thereby ultimately translating the reliability of the technical solution into high efficiency and trustworthiness at the operations and maintenance level.

[0108] Please see Figure 2 This application provides a terminal device upgrade apparatus to meet one of its objectives. It is a functional embodiment of the terminal device upgrade method of this application. The apparatus includes an upgrade query module 3100, an upgrade grouping module 3200, an upgrade fragmentation module 3300, and an upgrade scheduling module 3400. The upgrade query module 3100 is configured to request a server to determine the terminal device to be upgraded and return the corresponding firmware package to be upgraded based on the firmware version information of each terminal device accessed via a target communication protocol. The upgrade grouping module 3200 is configured to divide each terminal device to be upgraded into multiple upgrade groups corresponding to different upgrade times based on the network transmission characteristics with each terminal device to be upgraded. The upgrade fragmentation module 3300 is configured to divide the corresponding firmware package of each terminal device to be upgraded into multiple fragmented data based on the device upgrade characteristics of each terminal device to be upgraded. The upgrade scheduling module 3400 is configured to, in response to the arrival event of the upgrade time, sequentially call the fragmented data of different terminal devices to be upgraded from the corresponding upgrade groups and transmit it to the corresponding terminal device to be upgraded.

[0109] Based on any embodiment of the device in this application, the upgrade query module 3100 includes: a list generation module, configured to collect device attribute information of all terminal devices accessing the network using Zigbee as the target communication protocol, and generate a device list, wherein the device attribute information includes the unique identifier of the terminal device and its current firmware version number; a policy request module, configured to send an upgrade policy request to a server, wherein the request includes the device list, and the server determines the terminal devices to be upgraded in the device list and their upgrade tasks containing target firmware information based on the unique identifier and the current firmware version number; and a firmware download module, configured to download the firmware package corresponding to the terminal device to be upgraded from the server according to the target firmware information specified in the upgrade task.

[0110] Based on any embodiment of the device in this application, the upgrade grouping module 3200 includes: an indicator acquisition module, configured to acquire network status indicators corresponding to the network transmission characteristics of each terminal device to be upgraded corresponding to the upgrade task, the network status indicators including any one or more of the signal strength, packet loss rate, and data packet round-trip delay between the terminal device to be upgraded and the current device; a difficulty assessment module, configured to determine the upgrade difficulty factor of the corresponding terminal device to be upgraded based on the network status indicators; a division execution module, configured to determine the difficulty frequency band to which each terminal device to be upgraded belongs based on the upgrade difficulty factor and divide it into the same upgrade group corresponding to the difficulty frequency band; and a time window allocation module, configured to allocate different upgrade time windows to different upgrade groups, wherein a higher priority or earlier time upgrade time window is allocated to the upgrade group where the upgrade difficulty factor indicates a lower upgrade difficulty.

[0111] Based on any embodiment of the device in this application, the upgrade fragmentation module 3300 includes: a parameter acquisition module, configured to acquire one or more device characteristic parameters corresponding to one or more device upgrade characteristics for each terminal device to be upgraded in the upgrade task; a condition determination module, configured to determine at least one transmission constraint condition for firmware upgrade of the corresponding terminal device to be upgraded based on the device characteristic parameters; a strategy determination module, configured to generate a corresponding fragmentation strategy according to the transmission constraint condition determined for each terminal device to be upgraded, wherein the fragmentation strategy defines the maximum allowable size of fragmented data; and a firmware fragmentation module, configured to divide the corresponding firmware package into multiple fragmented data sequences conforming to the fragmentation strategy for transmission according to the fragmentation strategy generated separately for each terminal device to be upgraded.

[0112] Based on any embodiment of the device in this application, the upgrade scheduling module 3400 includes: a device queuing module, configured to generate a device scheduling sequence for all terminal devices to be upgraded within the upgrade group in response to the arrival event of the upgrade time window of any upgrade group; a fragmented transmission module, configured to determine the target terminal device to be upgraded in turn according to the device scheduling sequence, extract the fragmented data to be transmitted from the fragmented data sequence prepared by the target terminal device to be upgraded, and send it to the target terminal device to be upgraded, and correspondingly monitor and record the transmission result status of the fragmented data; an abnormal reordering module, configured to determine whether the corresponding fragmented data has been received by the corresponding target terminal device to be upgraded according to the transmission result status, and when it has not been successfully received, add the fragmented data back to the corresponding fragmented data sequence for retransmission; and a completion removal module, configured to remove the corresponding terminal device from the device scheduling sequence when all fragmented data in any fragmented data sequence has been successfully received.

[0113] Based on any embodiment of the device in this application, the upgrade scheduling module 3400 includes: a performance monitoring module, configured to continuously monitor the real-time performance indicators of the current network constructed by the target communication protocol during the execution of fragmented data transmission, the real-time performance indicators including the average packet loss rate and / or the average round-trip time of data packets; a group splitting module, configured to determine a network health score based on the real-time performance indicators, and when the network health score is lower than a first preset threshold, split the currently executing transmission of the upgrade group into multiple subgroups, and generate a new device scheduling sequence and upgrade time window for each subgroup; and an interval adjustment module, configured to compare the network health score with a second preset threshold, and dynamically adjust the time interval of the round-robin call based on the comparison result; wherein, when the network health score decreases, the upgrade time interval for switching different upgrade terminal devices in the device scheduling sequence is increased accordingly.

[0114] Based on any embodiment of the device in this application, the device further includes: a tracking response module, configured to respond to progress tracking instructions, generate and display an upgrade progress viewing panel, the upgrade progress viewing panel providing summary information on the transmission progress of the terminal devices to be upgraded; a data acquisition module, configured to continuously acquire and aggregate real-time status data from each terminal device to be upgraded, the real-time status data including: the number of fragmented data successfully received by each terminal device to be upgraded, determined based on the transmission result status of the fragmented data; a data processing module, configured to dynamically calculate at least one of the following progress information as transmission progress summary information and update it to the upgrade progress viewing panel based on the acquired real-time status data: the transmission completion percentage of a single terminal device to be upgraded, the overall transmission completion rate of the group to be upgraded, and the estimated remaining upgrade time; and an anomaly identification module, configured to monitor the real-time status data, and generate and report an anomaly alarm when a predefined anomaly is identified.

[0115] To address the aforementioned technical problems, embodiments of this application also provide a computer device for implementing the intelligent central control device of this application. For example... Figure 3 The diagram shows the internal structure of a computer device. This computer device includes a processor, a computer-readable storage medium, a memory, a network interface, and various communication components connected via a system bus. The computer-readable storage medium stores an operating system, a database, and computer-readable instructions. The database may store control information sequences. When the computer-readable instructions are executed by the processor, they enable the processor to implement a terminal device upgrade method. The processor of this computer device provides computing and control capabilities, supporting the operation of the entire computer device. The memory of this computer device may store computer-readable instructions. When these computer-readable instructions are executed by the processor, they enable the processor to execute the terminal device upgrade method of this application. The network interface of this computer device is used for communication with a terminal. Those skilled in the art will understand that… Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0116] In this embodiment, the processor is used to execute... Figure 2 The system defines the specific functions of each module and its sub-modules. The memory stores the program code and various data required to execute these modules or sub-modules. The network interface is used for data transmission between the user terminal and the server. In this embodiment, the memory stores the program code and data required to execute all modules / sub-modules in the terminal device upgrade apparatus of this application. The server can call the server's program code and data to execute the functions of all sub-modules.

[0117] This application also provides a storage medium storing computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the terminal device upgrade method of any embodiment of this application.

[0118] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. This computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0119] Those skilled in the art will understand that the steps, measures, and solutions in the various operations, methods, and processes discussed in this application can be alternated, modified, combined, or deleted. Furthermore, other steps, measures, and solutions in the various operations, methods, and processes discussed in this application can also be alternated, modified, rearranged, decomposed, combined, or deleted. Furthermore, steps, measures, and solutions in the prior art that are similar to those in the open-source operations, methods, and processes of this application can also be alternated, modified, rearranged, decomposed, combined, or deleted.

[0120] The above description is only a partial embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A terminal device upgrading method, characterized by, The method comprises the following steps: According to the firmware version information of each terminal device accessing the target communication protocol, the request server determines the terminal devices to be upgraded and returns the corresponding firmware package required for upgrading; Based on the network transmission characteristics of each terminal device to be upgraded, each terminal device to be upgraded is divided into a plurality of groups to be upgraded corresponding to different upgrade times; Based on the device upgrade characteristics of each terminal device to be upgraded, the corresponding firmware package of each terminal device to be upgraded is divided into a plurality of fragmented data; In response to the arrival of the upgrade time event, the fragmented data of different terminal devices to be upgraded are transmitted to the corresponding terminal devices to be upgraded in turn from the corresponding groups to be upgraded.

2. The method of claim 1, wherein, According to the firmware version information of each terminal device accessing the target communication protocol, the request server determines the terminal devices to be upgraded and returns the corresponding firmware, comprising: Collecting the device attribute information of all terminal devices accessing the Zigbee protocol as the target communication protocol, generating a device list, the device attribute information including the unique identifier of the terminal device and its current firmware version number; Sending an upgrade strategy request to the server, the request containing the device list, the server determining the terminal devices to be upgraded in the device list and their upgrade tasks containing target firmware information according to the unique identifier and the current firmware version number; According to the target firmware information specified in the upgrade task, downloading the firmware package corresponding to the terminal devices to be upgraded from the server.

3. The method of claim 1, wherein, Based on the network transmission characteristics of each terminal device to be upgraded, each terminal device to be upgraded is divided into a plurality of groups to be upgraded corresponding to different upgrade times, comprising: For each terminal device to be upgraded corresponding to the upgrade task, collect network state indicators for defining its network transmission characteristics, including any one or more of the signal strength, packet loss rate, and data packet round-trip delay between the terminal device and the current device; Determine the upgrade difficulty factor of the corresponding terminal device to be upgraded according to the network state indicators; According to the upgrade difficulty factor, determine the difficulty frequency band to which each terminal device to be upgraded belongs and divide it into the same upgrade group corresponding to the difficulty frequency band; Different upgrade time windows are allocated to different upgrade groups, and the upgrade group in which the device with a lower upgrade difficulty factor is indicated by the upgrade difficulty factor is allocated a higher priority or earlier upgrade time window.

4. The method of claim 3, wherein, Based on the device upgrade characteristics of each terminal device to be upgraded, the corresponding firmware package of each terminal device to be upgraded is divided into a plurality of fragmented data, comprising: For each terminal device to be upgraded in the upgrade task, obtain one or more device upgrade characteristics corresponding to the device characteristic parameters; Based on the device characteristic parameters, determine at least one transmission constraint condition when upgrading the firmware of the corresponding terminal device to be upgraded; According to the transmission constraint condition determined for each terminal device to be upgraded, generate a corresponding fragmentation strategy, which defines the maximum allowed size of the fragmented data; According to the fragmentation strategy generated for each terminal device to be upgraded, the corresponding firmware package is divided into a plurality of fragmented data sequences conforming to the fragmentation strategy for transmission.

5. The method of claim 1, wherein, in response to the arrival of the upgrade time, the transmission of the shard data of different terminal devices in the corresponding group is called in turn to the corresponding terminal device, including: in response to the arrival of the upgrade time window of any upgrade group, a device scheduling sequence is generated for all terminal devices in the upgrade group; according to the device scheduling sequence, the target terminal device is determined in the device scheduling sequence in turn, the current transmission shard data is taken out from the shard data sequence prepared by the target terminal device, and the transmission result state of the shard data is recorded correspondingly; according to the transmission result state, it is judged whether the corresponding shard data is received by the corresponding target terminal device, and when it is not successfully received, the shard data is re-added to the corresponding shard data sequence for retransmission; when all shard data in any shard data sequence is successfully received, the device scheduling sequence in the corresponding terminal device is removed.

6. The method of claim 1 to 5, wherein, in response to the arrival of the upgrade time, the transmission of the shard data of different terminal devices in the corresponding group is called in turn to the corresponding terminal device, including: during the execution of the shard data transmission, the real-time performance index of the current network constructed by the target communication protocol is continuously monitored, and the real-time performance index includes the network average packet loss rate and / or the average round-trip delay of the data packet; based on the real-time performance index, the network health score is determined, and when the network health score is lower than the first preset threshold, the upgrade group currently performing the transmission is split into multiple subgroups, and a new device scheduling sequence and an upgrade time window are generated for each subgroup; the network health score is compared with the second preset threshold, and the time interval of the round-robin calling is dynamically adjusted based on the comparison result; wherein when the network health score decreases, the upgrade time interval of switching different terminal devices in the device scheduling sequence is correspondingly increased.

7. The method of claim 1 to 5, wherein, The method further comprises: in response to the progress tracking instruction, an upgrade progress viewing panel is generated and displayed, and the upgrade progress viewing panel is provided with transmission progress summary information of the terminal device to be upgraded; real-time state data from each terminal device to be upgraded is continuously collected and aggregated, including the number of shard data successfully received by each terminal device to be upgraded based on the transmission result state of the shard data; based on the collected real-time state data, at least one of the following progress information is dynamically calculated as transmission progress summary information and updated to the upgrade progress viewing panel: transmission completion percentage of a single terminal device to be upgraded, overall transmission completion rate of the corresponding upgrade group, and estimated remaining upgrade time; the real-time state data is monitored, and when a predefined abnormal state is identified, abnormal alarm information is generated and reported.

8. A terminal device upgrading apparatus characterized by comprising: including: an upgrade query module is set to request the server to determine the terminal device to be upgraded according to the firmware version information of each terminal device accessed by the target communication protocol, and return the corresponding firmware package to be upgraded; The upgrading grouping module is configured to group the terminal devices to be upgraded into a plurality of groups to be upgraded corresponding to different upgrading times based on network transmission characteristics of the terminal devices to be upgraded; The upgrading fragmentation module is configured to fragment the firmware package corresponding to each terminal device to be upgraded into a plurality of fragmented data based on device upgrading characteristics of the terminal devices to be upgraded; The upgrading scheduling module is configured to, in response to an arrival event of the upgrading time, transmit the fragmented data of different terminal devices to be upgraded from the corresponding groups to be upgraded to the corresponding terminal devices to be upgraded in turn.

9. A smart central control device comprising a controller, the controller comprising a processor and a memory, characterized in that, The processor invokes a computer program in the memory to execute the steps of the terminal device upgrading method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer program is stored in the form of computer readable instructions and is implemented according to the method of any one of claims 1 to 7, and when the computer program is invoked and run by a computer, the steps included in the corresponding method are executed.

Images