Fault recovery methods, devices and systems
By dividing the low-voltage centralized procurement system into clusters and selecting primary and backup agent coordinators, rapid fault detection and seamless business switching are achieved, solving the problem of untimely fault detection in existing technologies and improving system reliability and business continuity.
Patent Information
- Application Number
- CN202611146239.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-30
- Publication Date
- 2026-11-17
AI Technical Summary
In existing low-voltage centralized procurement systems, routing fault recovery relies on periodic detection by the central coordinator, resulting in untimely fault detection and long service interruption times.
By dividing terminal sites into multiple clusters and selecting a primary agent coordinator and a backup agent coordinator within each cluster, proactive and rapid fault diagnosis and switching can be achieved. The backup agent coordinator can synchronize the operating status of the primary agent coordinator in real time and quickly execute the takeover strategy after fault confirmation.
It enables proactive, rapid, and accurate diagnosis of main agent coordinator failures, shortens service interruption time, improves the local autonomy and overall robustness of the network, and reduces dependence on the central node.
Smart Images

Figure CN123123249A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of communication technology, and more specifically to a fault recovery method, a fault recovery device, a fault recovery system, a machine-readable storage medium, and a program product. Background Technology
[0002] Currently, low-voltage centralized power supply systems generally employ high-speed power line communication (HPLC) and dual-mode wireless communication technologies to construct a tree-like network with a central coordinator (CCO) at its core and proxy coordinating units (PCOs) as relays, thereby achieving communication coverage for terminal devices such as electricity meters. Existing routing fault recovery mechanisms primarily adopt a centralized, periodic management approach. The Central Coordinator (CCO), as the core node of the network, is responsible for collecting communication status information of all nodes in the network, including periodic heartbeat detection messages and communication success rate statistics, thereby maintaining the network topology and node online status. When the Proximity Coordinator (PCO) fails, its subordinate child nodes (Stations, STAs) are usually unable to proactively initiate a rapid route switch. They must wait for the Central Coordinator to detect the fault and coordinate a new route path, or they must re-initiate the network access process themselves after the communication interruption.
[0003] In other words, the existing routing fault recovery of low-voltage centralized procurement systems mainly follows a technical path centered on a central coordinator, involving periodic detection and passive triggering. Therefore, existing methods cannot achieve rapid fault detection, resulting in prolonged service interruptions. Summary of the Invention
[0004] The purpose of this invention is to provide a fault recovery method, apparatus, and system to solve the problem that existing methods in low-voltage centralized procurement systems cannot achieve rapid fault detection and result in long service interruption times.
[0005] To achieve the above objectives, embodiments of the present invention provide a fault recovery method applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites communicatively connected to the central coordinator. The method includes: The central coordinator is controlled to divide all the terminal sites into multiple clusters; and the primary agent coordinator and backup agent coordinator in each cluster are determined. Control the primary agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and communicate with the central coordinator based on the service data; The backup agent coordinator in each cluster is controlled to synchronize the routing information with the primary agent coordinator of the same cluster; the routing information includes the service data and the operating status of the primary agent coordinator. If a fault is detected in the primary agent coordinator based on the operational status, the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
[0006] On the other hand, embodiments of the present invention also provide a fault recovery device applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites communicatively connected to the central coordinator; The device includes: The first control module is used to control the central coordinator to divide all the terminal sites into multiple clusters; and to determine the primary agent coordinator and the backup agent coordinator in each cluster. The second control module is used to control the main agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and to communicate with the central coordinator based on the service data. The third control module is used to control the backup agent coordinator in each cluster to synchronize the routing information with the primary agent coordinator of the cluster; the routing information includes the service data and the operating status of the primary agent coordinator; The fourth control module is used to control the backup agent coordinator to execute a takeover strategy for the main agent coordinator of the same cluster when a fault is detected in the main agent coordinator based on the operating status.
[0007] On the other hand, embodiments of the present invention also provide a fault recovery system, including: A central coordinator and multiple clusters; each cluster includes a primary agent coordinator and a backup agent coordinator that are communicatively connected to the central coordinator. The central coordinator is used to divide multiple terminal sites that are communicatively connected to the central coordinator into multiple clusters; and to determine the primary agent coordinator and the backup agent coordinator in each cluster. The primary agent coordinator is used to collect service data from backup agent coordinators and all terminal sites in the same cluster, and to communicate with the central coordinator based on the service data. The backup agent coordinator is used to synchronize the routing information of the primary agent coordinator in the same cluster; the routing information includes the service data and the operating status of the primary agent coordinator; if a fault is detected in the primary agent coordinator based on the operating status, the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator in the same cluster.
[0008] On the other hand, the present invention also provides a machine-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described fault recovery method.
[0009] On the other hand, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described fault recovery method.
[0010] Through the above technical solution, this embodiment of the invention controls the central coordinator to divide all terminal sites into multiple clusters; and determines the primary agent coordinator and backup agent coordinator in each cluster, laying the foundation for location-based fine-grained management and rapid fault recovery; by controlling the backup agent coordinator to synchronize the operating status of the primary agent coordinator in the same cluster; when a fault is detected in the primary agent coordinator based on the operating status, the backup agent coordinator executes a takeover strategy for the primary agent coordinator in the same cluster. Thus, this embodiment of the invention achieves proactive, rapid, and accurate diagnosis of primary agent coordinator faults, changing "post-event remediation" to "in-event rapid judgment." By synchronizing the operating status of the primary agent coordinator in real time through the backup agent coordinator and quickly executing the takeover strategy for the primary agent coordinator in the same cluster after fault confirmation, this invention achieves rapid fault detection and shortens service interruption time.
[0011] Other features and advantages of the embodiments of the present invention will be described in detail in the following detailed description section. Attached Figure Description
[0012] The accompanying drawings are provided to further illustrate embodiments of the present invention and form part of the specification. They are used together with the following detailed description to explain the embodiments of the present invention, but do not constitute a limitation thereof. In the drawings: Figure 1 This is one of the flowcharts illustrating the fault recovery method provided by the present invention; Figure 2 This is the second flowchart of the fault recovery method provided by the present invention; Figure 3 This is a schematic diagram of the structure for selecting and assigning roles to proxy coordinators within a cluster, as provided by the present invention. Figure 4 This is a schematic diagram of the adjustment of the communication mode of nodes within a cluster provided by the present invention; Figure 5 This is a schematic diagram of the active detection-based fault diagnosis mechanism within a cluster provided by the present invention; Figure 6 This is a schematic diagram illustrating the impact of the data acquisition frequency provided by this invention on the network maintenance overhead of the existing tree architecture and the clustering architecture of this invention; Figure 7 This is a schematic diagram illustrating the changes in network maintenance overhead between the existing tree architecture and the clustered architecture of this invention under the influence of the dual variables of network size and data acquisition frequency provided by this invention. Figure 8 This is a schematic diagram of the fault recovery device provided by the present invention; Figure 9 This is a schematic diagram of the fault recovery system provided by the present invention. Detailed Implementation
[0013] The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the scope of the present invention.
[0014] Method Implementation Examples Please refer to Figure 1 This invention provides a fault recovery method applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites communicatively connected to the central coordinator. The method includes: Step 100: Control the central coordinator to divide all the terminal sites into multiple clusters; and determine the primary agent coordinator and the backup agent coordinator in each cluster.
[0015] Please refer to Figure 2 To address the lack of physical location awareness in existing low-voltage centralized procurement systems, a clustering architecture is first constructed. The central coordinator divides all terminal sites into multiple clusters. By dividing into multiple clusters, fault detection of the main agent coordinator is performed within each cluster, facilitating rapid fault detection. The cluster division can be based on physical location information, or on the physical location information and communication quality parameters. Specifically, controlling the central coordinator to divide all terminal sites into multiple clusters includes: controlling the central coordinator to divide all terminal sites based on physical location information, or on the physical location information and communication quality parameters, to obtain multiple clusters.
[0016] For example, in one embodiment, the central coordinator divides all the terminal sites based on one dimension of physical location information, grouping terminal sites with similar physical locations (e.g., located within the same geographical area) into one cluster, resulting in multiple clusters. In another embodiment, the central coordinator divides all the terminal sites based on two dimensions: physical location information and communication quality parameters, grouping terminal sites with similar physical locations (e.g., located within the same geographical area) and whose communication quality parameters meet a set condition (excellent communication quality) into one cluster, resulting in multiple clusters. The communication quality parameters include at least one of signal strength, signal-to-noise ratio, and received bit error rate. For example, terminal sites with similar physical locations (e.g., located within the same geographical area) and whose signal strength is greater than a set threshold are grouped into one cluster, resulting in multiple clusters.
[0017] Please refer to Figure 3 Next, the selection and role allocation of intra-cluster PCOs (Proxy Coordinators) are performed. The central coordinator determines the primary proxy coordinator and at least one backup proxy coordinator in each cluster. The primary proxy coordinator (primary PCO) is responsible for forwarding service data and communication within the cluster; the backup proxy coordinator (backup PCO) synchronizes the primary PCO's routing information in real time and is ready to take over at any time. The primary and backup PCOs within each cluster are uniformly allocated and managed by the central coordinator during the network deployment phase, and each cluster is assigned a unique cluster identifier. The selection of the primary and backup PCOs is determined based on the communication status between nodes within the cluster and their superiors and subordinates. This communication status includes historical and real-time status, and specific indicators include, but are not limited to, signal strength, signal-to-noise ratio, and bit error rate. For example, the central coordinator can select the two terminal sites with the best historical communication signal strength ranking between the terminal sites within the cluster and their superiors and subordinates to be the primary and backup proxy coordinators, respectively. In other embodiments, a comprehensive analysis can be performed based on multiple factors such as signal strength, signal-to-noise ratio, and received bit error rate. The two terminal sites with the best overall ranking of signal strength, signal-to-noise ratio, and received bit error rate in historical communication between the terminal sites and their superior and subordinate nodes within the cluster can be determined as the primary agent coordinator and the backup agent coordinator, respectively.
[0018] In this embodiment of the invention, the central coordinator is controlled to divide all the terminal sites into multiple clusters; and the primary agent coordinator and backup agent coordinator in each cluster are determined, laying the foundation for location-based fine-grained management and rapid fault recovery.
[0019] Step 200: Control the primary agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and communicate with the central coordinator based on the service data.
[0020] Please refer to Figure 4 Next, the communication mode of nodes within the clusters is adjusted. In this embodiment of the invention, the primary agent coordinator in each cluster collects service data from the backup agent coordinators and all terminal sites within the same cluster, and communicates with the central coordinator based on this service data. All nodes within each cluster (excluding the primary PCO, the backup agent coordinators, and all terminal sites) aggregate information to the primary PCO and then communicate with the superior node (the central coordinator or other primary PCOs in adjacent clusters), completing the clustered architecture after the node function adjustment within the cluster. That is, the primary agent coordinator in each cluster is responsible for the communication duties of forwarding and communicating service data within the cluster.
[0021] Step 300: Control the backup agent coordinator in each cluster to synchronize the routing information with the primary agent coordinator of the cluster.
[0022] Then, dual-module hot standby of routing information is performed. In this embodiment, the backup agent coordinator in each cluster synchronizes the routing information of the primary agent coordinator with that of the same cluster. The routing information includes at least the service data of all terminal sites in the same cluster collected by the primary agent coordinator and the operating status of the primary agent coordinator. In one embodiment, the routing information of the primary agent coordinator includes, but is not limited to: receiving routing information from the primary PCO sent by the central coordinator; receiving routing information sent by the primary PCO; and the backup PCO autonomously obtaining the primary PCO's information (service data and operating status of all terminal sites) through channel monitoring. The operating status of the primary agent coordinator can be a heartbeat signal sent by the primary PCO to the backup PCO in the same cluster.
[0023] Step 400: If a fault is detected in the primary agent coordinator based on the operating status, control the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster.
[0024] This invention employs a layered heartbeat monitoring mechanism. Each cluster's primary PCO sends periodic heartbeats (first-layer heartbeats) to the central coordinator via a high-speed carrier channel. Simultaneously, the primary PCO sends high-frequency, lightweight heartbeats (second-layer heartbeats) to backup PCOs within the same cluster via high-speed wireless communication. The second-layer heartbeat frequency is higher than the first-layer heartbeat. Each cluster's backup PCO monitors the heartbeat signals sent by the primary PCO to the backup PCOs within the same cluster in real time. When a primary PCO failure is detected based on the heartbeat signals, a rapid switch to the backup PCO takes over. Specifically, the backup proxy coordinator executes a takeover strategy for the primary proxy coordinator within the same cluster. For example, upon detecting a primary PCO failure, the backup proxy coordinator broadcasts a proxy beacon to all terminal sites within the same cluster, notifying them that the backup proxy coordinator has taken over the primary proxy coordinator's communication responsibilities. It also sends a routing update message to the central coordinator, notifying it to update routing information. When a primary PCO failure is detected, the backup PCO is activated and takes over all terminal sites in the same cluster, notifying the central coordinator to update routing information, enabling services within the cluster to resume communication within a second-level timescale. In this embodiment of the invention, each backup PCO synchronizes the routing table and network status of the primary PCO in the same cluster in real time. When a primary PCO failure is confirmed through the aforementioned proactive diagnostic mechanism, the backup PCO is immediately activated and takes over all child nodes, broadcasting proxy beacons to announce the takeover; simultaneously, it updates local and network-wide routing information, achieving millisecond-level recovery of communication links and uninterrupted service switching.
[0025] This invention implements a central coordinator that divides all terminal sites into multiple clusters; and determines the primary agent coordinator and backup agent coordinator in each cluster, laying the foundation for location-based fine-grained management and rapid fault recovery; by controlling the backup agent coordinator to synchronize the operating status of the primary agent coordinator in the same cluster; and when a fault is detected in the primary agent coordinator based on the operating status, the backup agent coordinator executes a takeover strategy for the primary agent coordinator in the same cluster. Thus, this invention achieves proactive, rapid, and accurate diagnosis of primary agent coordinator faults, transforming "post-event remediation" into "rapid in-event judgment." By synchronizing the operating status of the primary agent coordinator in real time through the backup agent coordinator and quickly executing the takeover strategy for the primary agent coordinator in the same cluster after fault confirmation, this invention achieves rapid fault detection and shortens service interruption time.
[0026] In other aspects of the embodiments of the present invention, controlling the central coordinator to divide all the terminal sites based on physical location information to obtain multiple clusters includes: controlling the central coordinator to divide all the terminal sites whose physical location information belongs to the same bin into one cluster, thereby obtaining multiple clusters.
[0027] In other embodiments, the central coordinator can divide terminal sites within the same meter box into clusters, assigning each cluster a unique cluster identifier. This constructs an intelligent clustering scheme based on physical meter boxes, addressing the lack of physical location awareness in existing low-voltage centralized procurement systems. By intelligently dividing terminal sites within the same meter box into clusters, it lays the foundation for location-based fine-grained management and rapid fault recovery. Existing low-voltage centralized procurement systems have highly centralized routing management. This invention, through intelligent clustering based on meter boxes, divides the topology of the low-voltage centralized procurement system into multiple autonomous local units. Fault diagnosis and switching decisions are primarily handled by backup PCOs within each cluster, significantly reducing the processing burden on the central coordinator. This allows the network to maintain autonomy and rapid recovery even when communication with the central node is restricted or there is a local failure, enhancing the overall reliability of the system. This invention improves the local autonomy and overall robustness of the network, reducing dependence on the central node.
[0028] In other aspects of the embodiments of the present invention, controlling the central coordinator to divide all the terminal sites based on the physical location information and communication quality parameters to obtain multiple clusters includes: controlling the central coordinator to determine terminal nodes whose physical location information distance between all the terminal sites is less than or equal to a set distance threshold as candidate co-cluster terminal nodes; controlling the central coordinator to divide the candidate co-cluster terminal nodes whose communication quality parameters between them meet the set conditions into a single cluster, thereby obtaining multiple clusters.
[0029] In other embodiments, the central coordinator can also group terminal nodes that are physically close and have excellent communication quality parameters into a cluster. Communication quality parameters include at least one of signal strength, signal-to-noise ratio (SNR), and bit error rate (BER). For example, a set distance threshold is set. If the physical location distance between terminal site a and terminal site b is less than or equal to the set distance threshold; and the physical location distance between terminal site a and terminal site c is less than or equal to the set distance threshold, then terminal site a, terminal site b, and terminal site c are first identified as candidate terminal nodes in the same cluster. Specifically, if the signal strength between terminal site a and terminal site b is greater than or equal to the set signal strength threshold (meets the set condition), the SNR is greater than or equal to the set SNR threshold (meets the set condition), and the BER is less than or equal to the set BER threshold (meets the set condition), then all three communication parameters meet the set conditions, and terminal site a and terminal site b are determined to be in the same cluster. If the signal strength between terminal station A and terminal station C is greater than or equal to a set signal strength threshold (meets the set condition), the signal-to-noise ratio (SNR) is less than a set SNR threshold (does not meet the set condition), and the received bit error rate (BER) is less than or equal to a set BER threshold (meets the set condition), then if any one of the three communication parameters fails to meet the set condition, terminal station A and terminal station C are determined to be independent terminal stations. Therefore, terminal station A and terminal station B are ultimately determined to belong to the same cluster. In other embodiments, one or two of the communication quality parameters—signal strength, SNR, and BER—can be used as evaluation criteria.
[0030] Existing low-voltage centralized procurement systems lack consideration for the physical location of equipment. This invention addresses this issue by introducing a clustering method based on signal strength, signal-to-noise ratio (SNR), and received bit error rate (BER), aligning the network management unit of the low-voltage centralized procurement system with the physical meter boxes (or nearby equipment groups). This allows resource allocation, interference coordination, and fault recovery strategies to be optimized based on a more precise physical environment, improving the intelligence and precision of network management. In other words, addressing the lack of physical location awareness in existing low-voltage centralized procurement systems, this invention proposes intelligently dividing nodes within the same meter box or in close proximity into clusters based on communication quality parameters (signal strength, SNR, and BER) and physical location information, laying the foundation for location-based refined management and rapid recovery.
[0031] In other aspects of the embodiments of the present invention, the operating state of the primary agent coordinator includes a heartbeat signal sent by the primary agent coordinator to a backup agent coordinator in the same cluster and communication messages between the primary agent coordinator and the terminal site or central coordinator in the same cluster; the step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator in the same cluster when a fault is detected in the primary agent coordinator based on the operating state includes: determining that the primary agent coordinator is faulty when the heartbeat signal is not received and / or the time during which the communication message is not received within the predetermined communication window exceeds a set time threshold, and controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator in the same cluster.
[0032] In addition to the heartbeat signal, the backup agent coordinator for each cluster can also monitor communication messages sent by the primary agent coordinator to terminal sites or the central coordinator within the same cluster. In one embodiment, based on preset communication scheduling (such as beacon time slot arrangements and agent change cycles) and communication protocol specifications within the cluster, a model of the primary PCO's expected behavior is established. When the primary PCO remains silent for more than a set time threshold within its predetermined critical communication window (where it should send beacons, forward data, or respond to requests), and the backup agent coordinator fails to receive the heartbeat signal for more than a set time threshold, the backup PCO determines that the primary agent coordinator in the same cluster has an abnormal activity (fault) and controls the backup agent coordinator to execute a takeover strategy for the primary agent coordinator in the same cluster. In other embodiments, if the primary agent coordinator fails to receive the heartbeat signal or the communication message is not received within the predetermined communication window for more than a set time threshold, it is determined that the primary agent coordinator has a fault, and the backup agent coordinator executes a takeover strategy for the primary agent coordinator in the same cluster.
[0033] In this embodiment of the invention, a cascaded heartbeat monitoring mechanism is established within a cluster. In this mechanism, the primary PCO of each cluster sends a high-frequency, lightweight heartbeat to the backup PCO in the same cluster. The backup PCO operates in a listening mode and establishes an expected behavior model of the primary PCO based on a preset communication schedule to monitor its business communication status. When an anomaly is detected, the backup PCO confirms the primary PCO failure, thus achieving rapid and accurate fault determination.
[0034] In other embodiments, the step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a fault is detected based on the operating status includes: controlling the backup agent coordinator to send status query requests to all terminal stations in the same cluster when the heartbeat signal is not received and / or the time during which the communication message is not received within the predetermined communication window exceeds a set time threshold; receiving communication quality data between the terminal stations and the primary agent coordinator of the same cluster sent by all terminal stations; calculating the intra-cluster reliability score of the primary agent coordinator based on the communication quality data between all terminal stations and the primary agent coordinator of the same cluster; and determining that the primary agent coordinator is faulty when the intra-cluster reliability score is less than or equal to a set score threshold, and controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster.
[0035] Please refer to Figure 5 In another embodiment, the backup agent coordinator monitors the failure of the primary agent coordinator and can employ a dual verification mechanism. First, based on the preset communication schedule (such as beacon time slot arrangement and agent change cycle) and communication protocol specifications within the cluster, a model of the primary PCO's expected behavior is established. When the primary PCO remains silent for more than a set time threshold within its predetermined critical communication window (within the predetermined communication window) for sending beacons, forwarding data, or responding to requests, and the backup agent coordinator fails to receive the heartbeat signal for more than the set time threshold, the backup PCO sends a rapid status query request (hereinafter referred to as a status query request) to all terminal stations within the same cluster via a wireless channel, thereby collecting real-time communication quality data between all terminal stations and the primary PCO. The communication quality data can be characterized by at least one of signal strength, signal-to-noise ratio, and received bit error rate. For example, in one embodiment, the communication quality data can be characterized by signal strength. The backup PCO calculates the primary agent coordinator's intra-cluster reliability score based on the signal strength of the communication between all the terminal stations and the primary agent coordinator within the same cluster. For example, in one embodiment, the intra-cluster confidence score = a1*RSSI1 + a2*RSSI2 + ... + a n *RSSI n RSSI1 and RSSI2 represent the signal strengths of communication between the first terminal station and the primary agent coordinator of the same cluster, and the signal strengths of communication between the second terminal station and the primary agent coordinator of the same cluster, respectively. n Let a1, a2, and a be the signal strength of the communication between the nth terminal site and the main agent coordinator of the same cluster; nThe weighting coefficients are used to calculate the intra-cluster reliability score of the primary PCO based on feedback from multiple terminal sites. When the intra-cluster reliability score is less than or equal to a set score threshold, the primary PCO is deemed to have failed, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator in the same cluster.
[0036] In other embodiments, the formula for intra-cluster confidence score can also be intra-cluster confidence score = a1*RSSI1 + a2*RSSI2 + ... + a n *RSSI n +b1*SNR1+b2*SNR2+……+b n *SNR n +c1*BER1+c2*BER2+……+c n *BER n SNR1, SNR2, SNR n These represent the signal-to-noise ratios (SNRs) of communication between the first terminal station and the main agent coordinator of the same cluster, the SNR of communication between the second terminal station and the main agent coordinator of the same cluster, and the SNR of communication between the nth terminal station and the main agent coordinator of the same cluster, respectively; BER1, BER2, BER... n b1, b2, b are the received bit error rates (BER) for communication between the first terminal station and the main agent coordinator of the same cluster, the second terminal station and the main agent coordinator of the same cluster, and the nth terminal station and the main agent coordinator of the same cluster, respectively. n c1, c2, c n These are the weighting coefficients.
[0037] This invention establishes a cascaded heartbeat monitoring mechanism within a cluster. The primary PCO sends high-frequency, lightweight heartbeats to the backup PCO. The backup PCO operates in monitoring mode, establishing a pre-defined communication schedule to model the expected behavior of the primary PCO and monitoring its service communication status. When an anomaly is detected, the backup PCO broadcasts a rapid status query request to all stations (STAs) within the cluster, collects communication quality data from multiple terminal stations, and performs weighted calculations to collaboratively confirm the primary PCO's failure, achieving rapid and accurate fault determination. Existing technologies rely on periodic polling by the CCO and passive re-entry by the STAs, resulting in significant detection and recovery delays. This invention, through a proactive, probing fault diagnosis mechanism (cascaded heartbeat, service monitoring, and STA collaboration) led by the backup PCO within the cluster, enables rapid determination of faulty relay nodes and, combined with seamless switching of backup routes, greatly improves service continuity.
[0038] In other aspects of the embodiments of the present invention, the method further includes: controlling all terminal stations of each cluster to send service data to the main agent coordinator of the same cluster at a first transmission power; the first transmission power is the minimum transmission power that satisfies the requirements for reliable communication within the cluster.
[0039] In one embodiment, before step 200, all nodes within the cluster except the main PCO (Programmable Controller) aggregate information to the main PCO and then communicate with their superior nodes. Simultaneously, they reduce their signal transmission power and send service data to the main agent coordinator within the same cluster at a first transmission power. This first transmission power is the minimum transmission power required to meet the reliable communication needs within the cluster. This reduces the transmission power of each terminal station to the minimum level required for communication within the cluster, thereby minimizing interference with communication outside the cluster.
[0040] In this embodiment of the invention, all terminal stations (STAs) except the primary PCO converge their service data to the primary PCO of their respective cluster for unified uplink forwarding. Simultaneously, each STA dynamically reduces its transmission power based on the communication distance within the cluster, ensuring minimal impact on reliable communication within the cluster. The primary PCO, as the sole full-power transmitting node within the cluster, is responsible for communication with the superior CCO or neighboring cluster PCOs. This convergence and power control mechanism significantly reduces overall network energy consumption and equipment costs while substantially minimizing inter-cluster co-channel interference, thereby improving overall network spectrum reuse and communication reliability. In existing technologies, each STA is a potential routing node, resulting in a massive network routing table, severe flooding of route discovery and maintenance messages, and dense co-channel interference caused by all nodes communicating at full power. This embodiment of the invention, through a cluster-based data convergence mechanism, concentrates the responsibility for external communication onto the PCO (primary PCO or backup PCO), reducing the number of nodes that need to be managed and coordinated at the core routing layer from a massive number of STAs (e.g., hundreds) to a limited number of PCOs (primary PCO or backup PCO, e.g., dozens). This fundamentally simplifies the complexity of the network control plane, resulting in faster route convergence and a more concise routing table. Simultaneously, the reduced transmit power of terminal sites effectively confines signals within the physical enclosure, significantly reducing co-channel interference caused by signal cross-area coverage. This allows for more efficient parallel communication within different enclosures, thereby improving the overall system capacity and reliability. It also reduces the logical network size and substantially lowers routing complexity and co-channel interference.
[0041] In other aspects of the embodiments of the present invention, the embodiments of the present invention can perform clustered architecture performance evaluation. To quantitatively evaluate the improvement effect of the clustered networking scheme of the embodiments of the present invention on network performance, the following network carrying capacity evaluation model (or clustered architecture performance evaluation model) is established to compare and analyze the changes in the proportion of network maintenance overhead before and after implementing clustering optimization. The core parameters of the network carrying capacity evaluation model are defined as shown in Table 1: Table 1. Definition of core parameters of the model
[0042] The total maintenance overhead (bytes / second) can be approximated as: ; Where: the first term represents the raw control traffic generated by each of the N nodes, including discovery lists, heartbeats, and beacons; L is the average level.
[0043] The formula for business data overhead (bytes / second) is: ; The formula for the proportion of network maintenance costs is: ; Based on the above model, by substituting typical or measured network parameters, the network maintenance overhead ratio R of the clustered architecture and the existing architecture can be quantitatively calculated and compared. This network maintenance overhead ratio directly reflects the degree to which network resources are consumed by maintenance overhead; the lower the R, the higher the network's effective data transmission efficiency.
[0044] The following is a fault recovery method based on an exemplary embodiment: The system composition and initial state of this demonstration embodiment are as follows: one concentrator serves as the central coordinator (CCO); 300 smart meters serve as terminal stations (STAs), installed in 30 physical meter boxes, with 10 meters in each box; power line carrier (HPLC) and wireless dual-mode communication are adopted; the initial network forms a traditional tree structure with an average network level of 4.
[0045] The implementation process of the fault recovery method based on cluster architecture is as follows: Step 1: Intelligent Clustering. The Central Coordinator (CCO) collects the physical location information and communication quality parameters of each Terminal Station (STA), and divides the STAs in the same enclosure into clusters, forming a total of 30 clusters. Each cluster is assigned a unique cluster identifier.
[0046] Step 2, PCO Selection and Role Assignment. Within each cluster, select one STA as the primary agent coordinator (primary PCO), select one STA as the backup agent coordinator (backup PCO), and the remaining eight STAs as ordinary sites.
[0047] Step 3: Communication mode adjustment. The standby PCO and the regular STA send their service data to the primary PCO of their respective clusters. The primary PCO aggregates the data within the clusters and uploads it to the central coordinator (CCO). The standby PCO and the regular STA reduce their transmit power to the minimum level required for communication within the clusters.
[0048] Step 4: Establish hot standby mechanism. The standby PCO synchronizes the routing status of the primary PCO in real time, establishes a high-frequency heartbeat monitoring mechanism between the primary PCO and the standby PCO, and the standby PCO monitors the service communication status of the primary PCO.
[0049] Step 5, Example of Fault Recovery Process When the standby PCO detects the loss of the primary PCO's heartbeat and service silence, it sends a status query request to all STAs in the cluster. After confirming the primary PCO failure by combining feedback from each STA, the standby PCO is activated and takes over the communication responsibilities. It notifies the CCO to update the routing information, and services within the cluster resume communication within a second-level timescale.
[0050] Step 6: Assessment of network maintenance overhead for clustered architecture By substituting the typical parameters of traditional and clustered architectures into the mathematical model of the network maintenance overhead ratio R, the proportion of network maintenance overhead in all packets can be intuitively obtained, thereby accurately assessing the improvement in network performance brought by this patent proposal. Taking a typical low-voltage centralized procurement scenario as an example, the model parameter values are shown in Table 2: Table 2 Model parameter values
[0051] Calculations show that, under minute-level data collection conditions, the maintenance overhead of the existing tree network accounts for 64.3%, while the maintenance overhead of the cluster structure in the embodiment of this invention accounts for 15.3%, a significant reduction.
[0052] Further simulations were performed on the aforementioned network carrying capacity assessment model, and changes were made. (i.e., data acquisition frequency), varying the acquisition frequency between once per hour and once per minute, while keeping other parameters in Table 2 constant. Observe the change in the proportion of maintenance overhead between the tree architecture of the prior art and the clustered architecture of this embodiment. Figure 6 It is evident that, regardless of the data acquisition frequency, the network maintenance overhead of the clustered architecture in this embodiment is significantly lower than that of the traditional tree architecture.
[0053] Next, network size (number of STAs) is used as another variable, together with data acquisition frequency, to form a three-dimensional simulation space, and the maintenance overhead ratio of the two architectures under different network sizes and different service intensities is compared in a three-dimensional way. Figure 7 The three-dimensional simulation diagram reveals that the specific advantages of the clustering architecture in this embodiment of the invention are manifested in three aspects: First, the overall advantages are more obvious. The clustering architecture of this invention groups all network nodes into relatively independent and controllable clusters, so that the growth of control traffic is much lower than the linear growth of the number of nodes, thereby systematically and significantly reducing the proportion of control overhead across the entire network.
[0054] Secondly, it has low sensitivity to changes in the data acquisition frequency: as the data acquisition frequency increases, the maintenance overhead ratio of both architectures shows a downward trend because the proportion of business traffic increases. However, the curve of the cluster architecture in this embodiment of the invention decreases more gently. Third, its advantages are more prominent in high-frequency business scenarios. In scenarios with high data collection frequency, the clustering architecture of this embodiment of the invention releases more bandwidth resources to business data, which is crucial for future business scenarios with high real-time requirements and large data volumes.
[0055] Device Examples Please refer to Figure 8 On the other hand, embodiments of the present invention also provide a fault recovery device applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites communicatively connected to the central coordinator. The device includes: The first control module 801 is used to control the central coordinator to divide all the terminal sites into multiple clusters; and to determine the primary agent coordinator and the backup agent coordinator in each cluster. The second control module 802 is used to control the main agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and to communicate with the central coordinator based on the service data. The third control module 803 is used to control the backup agent coordinator in each cluster to synchronize the routing information with the primary agent coordinator of the cluster; the routing information includes the service data and the operating status of the primary agent coordinator; The fourth control module 804 is used to control the standby agent coordinator to execute a takeover strategy for the main agent coordinator of the same cluster when a fault is detected in the main agent coordinator based on the operating status.
[0056] Optionally, the central coordinator controls the division of all terminal sites into multiple clusters, including: The central coordinator controls all the terminal sites to be divided into multiple clusters based on physical location information, or based on the physical location information and communication quality parameters.
[0057] Optionally, the central coordinator controls the division of all terminal sites based on the physical location information and communication quality parameters, resulting in multiple clusters, including: The central coordinator controls all terminal nodes whose physical location information distance between them is less than or equal to a set distance threshold to identify them as candidate homo-clustered terminal nodes. The central coordinator controls the candidate co-cluster terminal nodes that meet the set conditions for communication quality parameters to be divided into a cluster, resulting in multiple clusters; The communication quality parameters include at least one of signal strength, signal-to-noise ratio, and received bit error rate.
[0058] Optionally, the central coordinator controls the division of all terminal sites based on physical location information to obtain multiple clusters, including: The central coordinator controls all terminal sites whose physical location information belongs to the same bin to divide them into a cluster, resulting in multiple clusters.
[0059] Optionally, the operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period exceeding a set time threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
[0060] Optionally, the operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period of time exceeding a set time threshold, the backup agent coordinator is controlled to send a status query request to all terminal sites in the same cluster. Receive communication quality data between all terminal sites and the main agent coordinator of the same cluster; Based on the communication quality data between all the terminal sites and the main agent coordinator of the same cluster, calculate the intra-cluster credibility score of the main agent coordinator. If the credibility score within the cluster is less than or equal to a set score threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
[0061] Optionally, controlling the standby agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster includes: The backup agent coordinator is controlled to broadcast agent beacons to all terminal sites in the same cluster, so as to notify all terminal sites in the same cluster that the backup agent coordinator has taken over the communication responsibilities of the primary agent coordinator. The backup agent coordinator is controlled to send a route update message to the central coordinator to notify the central coordinator to update the routing information.
[0062] Optionally, the device further includes: The fifth control module is used to control all terminal stations in each cluster to send service data to the main agent coordinator in the same cluster at a first transmission power; the first transmission power is the minimum transmission power that meets the requirements for reliable communication within the cluster.
[0063] The fault recovery device includes a processor and a memory. The first control module 801, second control module 802, third control module 803, and fourth control module 804 are all stored as program units in the memory. The processor executes these program units stored in the memory to achieve the corresponding functions. The processor contains a kernel, which retrieves the corresponding program units from the memory. One or more kernels may be provided. The memory may include non-permanent memory in computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. The memory includes at least one memory chip.
[0064] Please refer to Figure 9 On the other hand, the present invention also provides a fault recovery system, comprising: A central coordinator 910 and multiple clusters; the clusters include a primary agent coordinator 920 and a backup agent coordinator 930 that are communicatively connected to the central coordinator 910. The central coordinator 910 is used to divide multiple terminal sites that are communicatively connected to the central coordinator 910 into multiple clusters; and to determine the primary agent coordinator 920 and the backup agent coordinator 930 in each cluster. The primary agent coordinator 920 is used to collect service data from the backup agent coordinator 930 and all terminal sites in the same cluster, and to communicate with the central coordinator 910 based on the service data. The backup agent coordinator 930 is used to synchronize the routing information of the primary agent coordinator 920 of the same cluster; the routing information includes the service data and the operating status of the primary agent coordinator 920; if a fault is detected in the primary agent coordinator 920 based on the operating status, the backup agent coordinator 930 is controlled to execute a takeover strategy for the primary agent coordinator 920 of the same cluster.
[0065] The central coordinator 910 manages network-wide clustering, assigns PCO roles, and manages routing tables; the primary agent coordinator 920 is responsible for intra-cluster data forwarding and communication; the backup agent coordinator 930 synchronizes the primary PCO status in real time and is ready to take over; the site acts as a data acquisition node; the fault recovery system supports power line carrier and wireless dual-mode communication. The fault recovery system of this embodiment is used to execute the fault recovery method described in the above-described method embodiments. This embodiment of the invention pioneers an intelligent clustering technology based on physical meter boxes: addressing the lack of physical location awareness in existing network management, it proposes intelligently dividing nodes within the same meter box or in close proximity into a cluster based on signal strength, signal-to-noise ratio, received bit error rate, and physical location information, laying the foundation for location-based refined management and rapid recovery. This invention establishes a proactive, probing fault diagnosis mechanism within clusters, led by a backup PCO. To address the issue of high latency in centralized detection, a backup PCO is innovatively deployed within the cluster. Through its cascaded heartbeat monitoring, service status listening, and STA collaborative confirmation, proactive, rapid, and accurate fault diagnosis of the primary PCO is achieved, transforming "post-event remediation" into "rapid in-process judgment." This invention also enables rapid local self-healing and seamless handover based on hot standby within clusters. To overcome the problems of long traditional handover processes and significant service interruptions, the backup PCO synchronizes the primary PCO's status in real time and quickly takes over child nodes after fault confirmation, achieving rapid self-healing and seamless handover of communication links within the local cluster, significantly improving service continuity.
[0066] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a machine-readable storage medium. When the computer program is executed by a processor, the computer is able to execute a fault recovery method, the method comprising: controlling the central coordinator to divide all the terminal sites into multiple clusters; determining a primary agent coordinator and a backup agent coordinator in each cluster; controlling the primary agent coordinator in each cluster to collect service data from the backup agent coordinator in the same cluster and all terminal sites, and communicating with the central coordinator based on the service data; controlling the backup agent coordinator in each cluster to synchronize routing information of the primary agent coordinator in the same cluster; the routing information including the service data and the operating status of the primary agent coordinator; and controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator in the same cluster when a fault is detected in the primary agent coordinator based on the operating status.
[0067] In another aspect, the present invention also provides a machine-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform a fault recovery method, the method comprising: controlling the central coordinator to divide all the terminal sites into multiple clusters; determining a primary agent coordinator and a backup agent coordinator in each cluster; controlling the primary agent coordinator in each cluster to collect service data from the backup agent coordinator in the same cluster and all terminal sites, and communicating with the central coordinator based on the service data; controlling the backup agent coordinator in each cluster to synchronize routing information of the primary agent coordinator in the same cluster; the routing information including the service data and the operating status of the primary agent coordinator; and, in the event that a fault is detected in the primary agent coordinator based on the operating status, controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator in the same cluster.
[0068] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0069] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0070] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A fault recovery method, characterized in that, It is applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites that are communicatively connected to the central coordinator. The method includes: The central coordinator is controlled to divide all the terminal sites into multiple clusters; and the primary agent coordinator and backup agent coordinator in each cluster are determined. Control the primary agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and communicate with the central coordinator based on the service data; The backup agent coordinator in each cluster is controlled to synchronize the routing information with the primary agent coordinator of the same cluster; the routing information includes the service data and the operating status of the primary agent coordinator. If a fault is detected in the primary agent coordinator based on the operational status, the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
2. The fault recovery method according to claim 1, characterized in that, The central coordinator is controlled to divide all the terminal sites into multiple clusters, including: The central coordinator controls all the terminal sites to be divided into multiple clusters based on physical location information, or based on the physical location information and communication quality parameters.
3. The fault recovery method according to claim 2, characterized in that, The central coordinator, based on the physical location information and communication quality parameters, divides all the terminal sites into multiple clusters, including: The central coordinator controls all terminal nodes whose physical location information distance between them is less than or equal to a set distance threshold to identify them as candidate homo-clustered terminal nodes. The central coordinator controls the candidate co-cluster terminal nodes that meet the set conditions for communication quality parameters to be divided into a cluster, resulting in multiple clusters; The communication quality parameters include at least one of signal strength, signal-to-noise ratio, and received bit error rate.
4. The fault recovery method according to claim 2, characterized in that, The central coordinator controls the division of all terminal sites based on physical location information, resulting in multiple clusters, including: The central coordinator controls all terminal sites whose physical location information belongs to the same bin to divide them into a cluster, resulting in multiple clusters.
5. The fault recovery method according to claim 1, characterized in that, The operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period exceeding a set time threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
6. The fault recovery method according to claim 1, characterized in that, The operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period of time exceeding a set time threshold, the backup agent coordinator is controlled to send a status query request to all terminal sites in the same cluster. Receive communication quality data between all terminal sites and the main agent coordinator of the same cluster; Based on the communication quality data between all the terminal sites and the main agent coordinator of the same cluster, calculate the intra-cluster credibility score of the main agent coordinator. If the credibility score within the cluster is less than or equal to a set score threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
7. The fault recovery method according to claim 5 or 6, characterized in that, The strategy of controlling the backup agent coordinator to take over the primary agent coordinator for the same cluster includes: The backup agent coordinator is controlled to broadcast agent beacons to all terminal sites in the same cluster, so as to notify all terminal sites in the same cluster that the backup agent coordinator has taken over the communication responsibilities of the primary agent coordinator. The backup agent coordinator is controlled to send a route update message to the central coordinator to notify the central coordinator to update the routing information.
8. The fault recovery method according to claim 1, characterized in that, The method further includes: Control all terminal stations in each cluster to send service data to the main agent coordinator in the same cluster at a first transmission power; the first transmission power is the minimum transmission power that satisfies the requirements for reliable communication within the cluster.
9. A fault recovery device, characterized in that, It is applied to a low-voltage centralized procurement system; the low-voltage centralized procurement system includes a central coordinator and multiple terminal sites that are communicatively connected to the central coordinator. The device includes: The first control module is used to control the central coordinator to divide all the terminal sites into multiple clusters; and to determine the primary agent coordinator and the backup agent coordinator in each cluster. The second control module is used to control the main agent coordinator in each cluster to collect service data from the backup agent coordinators and all terminal sites in the same cluster, and to communicate with the central coordinator based on the service data. The third control module is used to control the backup agent coordinator in each cluster to synchronize the routing information with the primary agent coordinator of the cluster; the routing information includes the service data and the operating status of the primary agent coordinator; The fourth control module is used to control the backup agent coordinator to execute a takeover strategy for the main agent coordinator of the same cluster when a fault is detected in the main agent coordinator based on the operating status.
10. The fault recovery device according to claim 9, characterized in that, The central coordinator is controlled to divide all the terminal sites into multiple clusters, including: The central coordinator controls all the terminal sites to be divided into multiple clusters based on physical location information, or based on the physical location information and communication quality parameters.
11. The fault recovery device according to claim 10, characterized in that, The central coordinator, based on the physical location information and communication quality parameters, divides all the terminal sites into multiple clusters, including: The central coordinator controls all terminal nodes whose physical location information distance between them is less than or equal to a set distance threshold to identify them as candidate homo-clustered terminal nodes. The central coordinator controls the candidate co-cluster terminal nodes that meet the set conditions for communication quality parameters to be divided into a cluster, resulting in multiple clusters; The communication quality parameters include at least one of signal strength, signal-to-noise ratio, and received bit error rate.
12. The fault recovery device according to claim 10, characterized in that, The central coordinator controls the division of all terminal sites based on physical location information, resulting in multiple clusters, including: The central coordinator controls all terminal sites whose physical location information belongs to the same bin to divide them into a cluster, resulting in multiple clusters.
13. The fault recovery device according to claim 9, characterized in that, The operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period exceeding a set time threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
14. The fault recovery device according to claim 9, characterized in that, The operating status of the primary agent coordinator includes the heartbeat signal sent by the primary agent coordinator to the backup agent coordinator of the same cluster and the communication messages between the primary agent coordinator and the terminal site or central coordinator of the same cluster. The step of controlling the backup agent coordinator to execute a takeover strategy for the primary agent coordinator of the same cluster when a failure is detected based on the operational status includes: If the heartbeat signal is not received and / or the communication message is not received within the scheduled communication window for a period of time exceeding a set time threshold, the backup agent coordinator is controlled to send a status query request to all terminal sites in the same cluster. Receive communication quality data between all terminal sites and the main agent coordinator of the same cluster; Based on the communication quality data between all the terminal sites and the main agent coordinator of the same cluster, calculate the intra-cluster credibility score of the main agent coordinator. If the credibility score within the cluster is less than or equal to a set score threshold, it is determined that the primary agent coordinator is faulty, and the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
15. The fault recovery device according to claim 13 or 14, characterized in that, The strategy of controlling the backup agent coordinator to take over the primary agent coordinator for the same cluster includes: The backup agent coordinator is controlled to broadcast agent beacons to all terminal sites in the same cluster, so as to notify all terminal sites in the same cluster that the backup agent coordinator has taken over the communication responsibilities of the primary agent coordinator. The backup agent coordinator is controlled to send a route update message to the central coordinator to notify the central coordinator to update the routing information.
16. The fault recovery device according to claim 9, characterized in that, The device further includes: The fifth control module is used to control all terminal stations in each cluster to send service data to the main agent coordinator in the same cluster at a first transmission power; the first transmission power is the minimum transmission power that meets the requirements for reliable communication within the cluster.
17. A fault recovery system, characterized in that, include: A central coordinator and multiple clusters; each cluster includes a primary agent coordinator and a backup agent coordinator that are communicatively connected to the central coordinator. The central coordinator is used to divide multiple terminal sites that are communicatively connected to the central coordinator into multiple clusters. And determine the primary agent coordinator and the backup agent coordinator in each of the said clusters; The primary agent coordinator is used to collect service data from backup agent coordinators and all terminal sites in the same cluster, and to communicate with the central coordinator based on the service data. The backup agent coordinator is used to synchronize the routing information of the primary agent coordinator for the same cluster. The routing information includes the service data and the operating status of the main agent coordinator; If a fault is detected in the primary agent coordinator based on the operational status, the backup agent coordinator is controlled to execute a takeover strategy for the primary agent coordinator of the same cluster.
18. A machine-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the fault recovery method according to any one of claims 1 to 8.
19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the fault recovery method according to any one of claims 1 to 8.
