Software-defined satellite network fault detection and migration method and system

Abstract

The application discloses a software-defined satellite network fault detection and migration method and system, which comprises the following steps: periodically sending heartbeat packets by a main controller (including a ground main controller and a ground backup main controller) and a domain controller; periodically updating the node state and the routing table in the domain by the domain controller, and notifying the main controller; regularly synchronizing data between the ground main controller and the ground backup main controller. When the ground main controller is detected to be faulty, the ground backup main controller will execute the corresponding migration strategy. If the domain controller does not receive the heartbeat packet of the main controller for three consecutive periods, it is determined that the main controller is out of connection, and the migration strategy is started. Similarly, if the node in the domain does not receive the heartbeat packet of the domain controller for three consecutive periods or detects link fault information, it is determined that the domain controller is faulty, and the corresponding migration strategy is executed; the stability and reliability of the satellite network are improved, and the network function can be quickly recovered when a fault occurs.

Description

Technical Field

[0001] The present invention belongs to the technical field of satellite networks and relates to a software-defined satellite network fault detection and migration method and system. Background Art

[0002] With the rapid development of satellite internet technology, the number of satellites in space-based networks is growing at an unprecedented rate, aiming to provide more timely, detailed, and comprehensive services to users around the world. This trend has not only greatly expanded the coverage of satellite networks but also significantly improved their service quality and efficiency. However, large-scale constellation networking also brings many technical challenges, particularly in satellite management and control and routing calculations.

[0003] In traditional satellite network architectures, each satellite typically needs to independently handle control functions such as routing decisions. This not only leads to a significant consumption of onboard storage and computing resources, but also limits the network's flexibility and programmability. This problem becomes increasingly prominent as the number of satellites continues to increase, posing unprecedented challenges to network management and routing mechanisms based on virtual topologies.

[0004] To address this challenge, Software-Defined Networking (SDN) technology emerged and is becoming a viable research direction for addressing satellite network management and control. SDN decouples control functions like routing decisions from forwarding devices and places them under the unified management of a centralized controller, thereby centralizing the logic of the network control plane and managing resources. This transformation not only enhances network flexibility and programmability but also facilitates the integration of heterogeneous network architectures.

[0005] In a software-defined satellite network architecture, the control and data planes are completely decoupled. The data plane, primarily composed of low-Earth orbit (LEO) satellites and intersatellite links, is responsible for data packet storage and forwarding. The control plane, on the other hand, is responsible for key network functions such as topology management, routing table distribution, and network status information collection, as well as basic functions such as global clock synchronization and control message transmission and reception. Through logically centralized control, the control plane enables efficient management and control of the entire satellite network and functional updates.

[0006] A typical satellite network architecture consists of a space segment, a ground segment, a control and management segment, and a user segment. These segments work together to implement functions such as user access, data transmission, network interconnection, system management, and user services. However, existing satellite network architectures still have many shortcomings when it comes to large-scale constellation networking, such as slow controller failure recovery, inadequate resource utilization, and poor network flexibility. Summary of the Invention

[0007] The application aims to solve the technical problems of slow recovery speed, insufficient resource utilization and limited network flexibility of low-orbit satellite networks in the prior art when a controller fails, and provides a software-defined satellite network fault detection and migration method and system.

[0008] To achieve the above-mentioned purpose, the application adopts the following technical solutions:

[0009] The application provides a software-defined satellite network fault detection and migration method in the first aspect, which comprises the following steps:

[0010] The master controller and the domain controller periodically send heartbeat packets; the master controller is a ground master controller or a ground backup master controller;

[0011] The domain controller periodically updates the node state and the routing table in the domain, and notifies the master controller;

[0012] The ground master controller periodically synchronizes its own data to the ground backup master controller; if the ground backup master controller senses that the ground master controller fails, it determines that the ground master controller fails and performs the migration strategy corresponding to the ground master controller failure;

[0013] If any domain controller does not receive the heartbeat packet of the master controller within 3 cycles, it determines that the master controller is lost, and performs the migration strategy corresponding to the master controller loss;

[0014] If any node in the domain does not receive the heartbeat packet of the domain controller for 3 consecutive cycles, or detects link failure information in the received heartbeat packet of the domain controller, it determines that the domain controller fails, and enters the migration strategy of the domain controller failure.

[0015] Further, the migration strategy of the ground master controller failure is specifically:

[0016] The ground backup master controller sends an identity packet to the failed master controller, indicating that it has assumed the function of the master controller;

[0017] The ground backup master controller takes over the management and control of the whole network, switches to the master controller, sends an identity packet to all domain controllers to announce its own identity, and then periodically broadcasts a heartbeat packet;

[0018] All domain controllers update the local master controller information after receiving the identity packet, and immediately send the network state in the domain and the inter-domain network topology information to the master controller;

[0019] The ground master controller switches to the ground backup master controller after the ground master controller failure is recovered, and periodically synchronizes the master controller information.

[0020] Further, the migration strategy of the master controller loss is specifically:

[0021] If any domain controller detects that it has not received a heartbeat packet from the master controller within three cycles, it will send a connection loss notification to other domain controllers.

[0022] When any domain controller receives loss of connection notifications from more than half of the domain controllers within three cycles, the domain controller with the least number of satellites in the domain is selected as the on-board temporary master controller;

[0023] The temporary master controller on board takes over the control of the entire network, sends an identity packet to announce its own identity, and then periodically broadcasts heartbeat packets;

[0024] After receiving the identity packet, all domain controllers update the local master controller information and immediately send the intra-domain network status and inter-domain network topology information to the onboard temporary master controller;

[0025] If any domain controller receives a heartbeat packet from the ground within three consecutive cycles, it means that the connection between the domain controller and the main controller has been restored, and the domain controller sends a recovery notification to the temporary main controller on the satellite;

[0026] When the temporary main controller on the satellite receives the recovery notification message from all domain controllers, it returns control to the main controller and synchronizes the management and control data during the loss of connection.

[0027] Furthermore, the migration strategy for the domain controller failure is specifically as follows:

[0028] If any node in the domain fails to receive a heartbeat packet from the domain controller for three consecutive cycles, or detects a link failure in the received heartbeat packet, it sends a domain controller failure message to the master controller.

[0029] The master controller receives the domain controller failure information and determines whether the failed node is a normal domain controller or a temporary master controller on the satellite;

[0030] If the failed node is a common domain controller, the master controller elects a new domain controller and sends the new domain controller information to other domain controller nodes; the new domain controller sends an identity packet to the satellite in the domain and performs the domain controller function;

[0031] If the failed node is the temporary master controller on the satellite, the domain controller with the least satellites in the domain will be elected as the new temporary master controller on the satellite.

[0032] Furthermore, the master controller selects a new domain controller using a dynamic re-election algorithm.

[0033] Furthermore, the ground backup main controller senses a ground main controller failure, specifically:

[0034] The ground master controller periodically synchronizes its own data to the ground backup master controller; the self-data includes global topology and routing table information;

[0035] The ground backup main controller did not receive the main controller synchronization data within one cycle, and determined that the ground main controller was completely faulty.

[0036] A second aspect of the present invention provides a software-defined satellite network fault detection and migration method, which is applied to a ground master controller and includes the following steps:

[0037] Send heartbeat packets periodically;

[0038] Periodically receive domain node status and domain routing table information from the domain controller;

[0039] Periodically synchronize its own data to the ground backup main controller;

[0040] If the data of the backup main controller is not synchronized with the main controller in one cycle, it is considered a complete failure and an activation packet is sent to switch the main controller to the main controller.

[0041] After the ground main controller recovers from the fault, it switches to the backup main controller and periodically receives its own data from the main controller.

[0042] A third aspect of the present invention provides a software-defined satellite network fault detection and migration method, which is applied to a domain controller and includes the following steps:

[0043] Send heartbeat packets periodically;

[0044] Periodically receive heartbeat packets from the master controller and other domain controllers;

[0045] Periodically sends domain node status and domain routing table information to the main controller;

[0046] If no heartbeat packet is received from the master controller within three cycles, a connection loss notification is sent to other domain controllers;

[0047] If a loss of connection notification is received from more than half of the domain controllers, the domain controller with the least satellites in the domain will be elected as the temporary master controller on board;

[0048] The onboard temporary master controller sends an identity packet and then periodically broadcasts a heartbeat packet;

[0049] After receiving the identity packet of the temporary master controller on the satellite, all domain controllers update the local master controller information;

[0050] After the domain controller receives heartbeat packets from the master controller for three consecutive cycles, it sends a recovery notification to the temporary master controller on board. After the temporary master controller on board receives the recovery notification messages from all domain controllers, it returns control to the master controller and synchronizes the management and control data during the loss of connection.

[0051] If any node in the domain does not receive the heartbeat packet from the domain controller for three consecutive cycles, or detects link failure information in the received heartbeat packet, it sends the domain controller failure information to the main controller;

[0052] The domain controller receives fault node type information and fault migration information; the fault node type includes an ordinary domain controller or an on-board temporary master controller; the fault migration information includes new domain controller information corresponding to the ordinary domain controller or new on-board temporary master controller information corresponding to the on-board temporary master controller.

[0053] A fourth aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the software-defined satellite network fault detection and migration method is implemented.

[0054] A fifth aspect of the present invention provides a software-defined satellite network fault detection and migration system, comprising:

[0055] Heartbeat broadcast module, the main controller and the domain controller both periodically send heartbeat packets; the main controller is a ground main controller or a ground backup main controller;

[0056] In the domain information synchronization module, the domain controller periodically updates the node status and routing table within the domain and notifies the main controller;

[0057] The main control backup module, if the ground backup main controller senses the failure of the ground main controller, determines that the ground main controller has failed and implements the corresponding migration strategy for the ground main controller failure;

[0058] The master controller migration module determines that the master controller is disconnected if any domain controller does not receive the heartbeat packet from the master controller within three cycles, and implements the corresponding master controller disconnection migration strategy;

[0059] The domain controller migration module determines that the domain controller is faulty and enters the migration strategy for domain controller failure if any node in the domain fails to receive the heartbeat packet from the domain controller for three consecutive cycles, or detects link failure information in the received heartbeat packet from the domain controller.

[0060] Compared with the prior art, the present invention has the following beneficial effects:

[0061] This invention discloses a software-defined satellite network fault detection and migration method. This method implements real-time monitoring of network status through periodic heartbeat packet transmission between the main controller (including the ground-based main controller and the ground-based backup main controller) and the domain controller. This mechanism rapidly detects and responds to network anomalies, significantly improving the stability and reliability of the entire satellite network. Clear fault detection rules are established, such as when the ground-based backup main controller detects a ground-based main controller failure, when the domain controller fails to receive the main controller's heartbeat packet for more than three cycles, when a node within the domain fails to receive a domain controller heartbeat packet, or when a link failure is detected. The method also provides migration strategies for different types of faults (such as ground-based main controller failure, main controller loss of connection, and domain controller failure). These strategies are designed to minimize the impact of faults on network operations, ensuring rapid restoration of network functionality and ensuring service continuity when a fault occurs. By dynamically updating node status and routing tables within the domain and notifying the main controller, the method enables the satellite network to flexibly adjust its network structure and routing strategies based on actual operating conditions. This adaptability helps improve network performance and efficiency while also facilitating response to network emergencies. This approach reduces the need for manual intervention through automated fault detection and mitigation, thereby lowering operational costs. Furthermore, because faults can be quickly detected and addressed, prolonged service interruptions and losses caused by these faults are avoided.

[0062] Furthermore, the method of the present invention enables a rapid response when a ground-based master controller fails, sending an identity packet to take over network-wide control and switch to the master controller role. This process ensures seamless handover, ensuring network control continuity and avoiding network interruptions caused by master controller failures. After switching to master control, the ground-based backup master controller sends an identity packet to all domain controllers to announce its identity and periodically broadcasts heartbeat packets to maintain real-time network status updates. Upon receiving the identity packet, the domain controller immediately updates the local master controller information and sends intra-domain network status and inter-domain network topology information to the new master controller, ensuring the accuracy and consistency of network information. If the ground-based master controller recovers, it automatically switches back to the ground-based backup master controller role and periodically synchronizes master controller information. This mechanism ensures a smooth transition after failure recovery and avoids network issues caused by inconsistent master controller status. By implementing a migration strategy for ground-based master controller failures, the entire satellite network maintains high reliability and stability in the face of master controller failures. This capability is crucial for ensuring the continuous operation of critical services and minimizing service interruptions.

[0063] Further, the method of the present application can detect the absence of heartbeat packets and trigger the migration strategy when the master controller is lost. By sending a loss of connection announcement to other domain controllers and collecting feedback, the system can autonomously select a temporary master controller on the satellite to take over the network management. This process achieves a quick response and reduces the network downtime caused by the loss of the master controller. The domain controller with the fewest satellites in the domain is selected as the temporary master controller on the satellite, which is based on the principle of resource optimization. It ensures that the temporary master controller does not over-consume network resources during the takeover process, while efficiently completing the network management task. After the temporary master controller on the satellite takes over, it sends an identity package to announce its identity and periodically broadcasts heartbeat packets to maintain real-time updates of the network status. All domain controllers update the local master controller information after receiving the identity package and send the domain network status and inter-domain network topology information to the temporary master controller. This process achieves seamless switching and ensures the accuracy and consistency of network information. When the connection between the master controller and the domain controller is restored, the temporary master controller on the satellite can synchronize the management data during the loss of connection and return the control to the master controller, achieving a smooth transition. The implementation of the migration strategy makes the satellite network highly robust in the face of sudden events such as the loss of the master controller. Through distributed decision-making and fast response mechanisms, the network can quickly recover its functions and ensure the continuous operation of critical services.

[0064] Further, the method of the present application can continuously monitor the heartbeat packets of the domain controller by any node in the domain, and timely send fault information to the master controller when the heartbeat packet is missing or link failure information is detected. This mechanism ensures accurate detection of faults and provides a prerequisite for rapid response. The master controller can quickly determine the type of faulty node after receiving the fault information and take appropriate migration strategies, thereby effectively reducing the impact of faults on network operation. When a normal domain controller fails, the master controller can automatically elect a new domain controller to take over its responsibilities. This process achieves seamless switching and ensures the continuity of network control. The new domain controller will send an identity package to the satellites in the domain after taking over and perform the domain controller function, thereby maintaining the normal operation of the network. If the temporary master controller on the satellite fails, the master controller can elect a domain controller with the fewest satellites as a new temporary master controller on the satellite. This decision is based on the principle of resource optimization, ensuring that the new temporary master controller does not over-consume network resources during the takeover process. At the same time, since the election process is automated, the need for human intervention is reduced, improving the reliability and stability of the network. The implementation of the migration strategy makes the satellite network highly robust in the face of sudden events such as domain controller failure. Through automatic election and seamless switching mechanisms, the network can quickly recover its functions and ensure the continuous operation of critical services. In addition, this strategy also enhances the self-healing ability of the network, allowing it to repair itself when facing faults, reducing the burden on the maintenance personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0066] Figure 1 A diagram of the hierarchical and domain-based multi-controller management and control architecture for software-defined low-orbit satellite networks;

[0067] Figure 2 This is a flow chart of the ground master controller failure migration method;

[0068] Figure 3 Migration method and process for the ground master controller lost contact;

[0069] Figure 4 This is a block diagram of the software-defined satellite network fault detection and migration method of the present invention. DETAILED DESCRIPTION

[0070] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Generally, the components of the embodiments of the present invention described and marked in the drawings herein can be arranged and designed in various different configurations.

[0071] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention as claimed, but rather merely represents selected embodiments of the present invention. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without creative effort are intended to fall within the scope of protection of the present invention.

[0072] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings.

[0073] The present invention is described in further detail below with reference to the accompanying drawings:

[0074] See also Figure 1, an embodiment of the present invention adopts a hierarchical and domain-based multi-controller management and control architecture for software-defined low-orbit satellite networks to achieve global and efficient control of satellite networks. A ground master controller (MC) and domain controllers (DC) in multiple satellite domains are deployed in the entire hierarchical and domain-based multi-controller management and control architecture. The ground master controller controls multiple domain controllers by simultaneously controlling multiple ground stations. The domain controllers are located in the satellite airspace, and one domain controller can communicate with multiple satellites to achieve control of multiple satellites. This hierarchical and domain-based multi-controller management and control architecture reduces the pressure and overhead of a single controller processing multiple nodes simultaneously through the hierarchical deployment of multiple domain controllers.

[0075] The ground-based master controller (GMC) is the top layer of the hierarchical, domain-based control architecture. Located on the ground, it features a hot backup. The centralized GMC configuration takes into account the complexity and dynamic nature of satellite networks. Using a single GMC allows for a centralized controller, simplifies network management, and avoids overhead such as information synchronization in distributed control systems. Secondly, the GMC maintains global information about the entire network, facilitating understanding of network status and topology, enabling effective coordination and optimization of network resources. Third, centralized decision-making enables timely response to satellite network emergencies or failures. Fourth, ground-based deployment allows for the utilization of high-performance servers or specialized hardware to enhance the ability to handle complex situations and ensure effective network control. Finally, ground-based deployment simplifies GMC maintenance and upgrades, reduces satellite network energy consumption, and improves reliability.

[0076] Domain controllers form the middle layer of the hierarchical, domain-based management and control architecture. A single domain consists of a domain controller and its satellites. Domain controller deployment offers high flexibility, facilitating efficient domain management, particularly in satellite constellations with relatively stable topologies. Domain controllers continuously monitor the location, fault status, and network topology of satellites within their domains and forward this information to the master controller, which uses this data for global optimization, including routing calculation, resource allocation, and monitoring.

[0077] Ordinary satellites form the foundation of a hierarchical and domain-based management and control architecture, are interconnected through two intra-orbit inter-satellite links and two inter-orbit inter-satellite links, and process data packets according to the commands of the domain controller.

[0078] To improve the network performance of the hierarchical and domain-based multi-controller management and control architecture in fault-prone scenarios and avoid network crashes caused by node or link failures, the present invention provides a software-defined satellite network fault detection and migration method, including the following steps:

[0079] S1, initialize the control architecture:

[0080] S101, the ground master controller broadcasts an identity package to announce its own identity;

[0081] S102, all domain controllers receive the identity package and save the master controller information;

[0082] S103, the domain controllers collect the initial states of the nodes in the domain and construct the intra-domain routing table, and the ground master controller collects the initial states of all satellite nodes and constructs a global routing table.

[0083] S2, topology discovery and node state update are performed:

[0084] S201, all domain controllers periodically count and update the intra-domain node information, failed node information, and intra-domain routing table, and periodically notify the master controller;

[0085] S202, the ground master controller collects real-time state information of all satellite nodes and periodically updates the global routing table.

[0086] S3, the master controller / domain controller judges the fault type:

[0087] S301, if the ground backup master controller senses the failure of the ground master controller, the migration strategy for the failure of the ground master controller is entered;

[0088] S302, if any domain controller in the network does not receive the heartbeat package sent by the master controller within 3 periods, the domain controller determines that the master controller has been disconnected, and the domain controller sends a disconnection notification to other domain controllers. If any domain controller receives disconnection notifications from more than half of the domain controllers within 3 periods, the migration strategy for the disconnection of the ground master controller is entered;

[0089] S303, if any node in the domain does not receive the heartbeat package of the domain controller for 3 consecutive periods, or detects link failure information in the received heartbeat package, the node sends domain controller failure information to the master controller and enters the migration strategy for the failure of the domain controller.

[0090] S4, the master controller / domain controller performs the corresponding fault migration strategy according to the fault type judgment:

[0091] S401, migration strategy for the failure of the ground master controller: the backup master controller sends an identity package to the failed master controller, actively takes over the management of the entire network, and broadcasts an identity package to announce its own identity. After all domain controllers receive the identity package, they immediately send the intra-domain network state and inter-domain network topology information to the new ground master controller. The failed master controller automatically becomes a backup controller after the failure is recovered, and synchronizes the backup data of the master controller.

[0092] As Figure 2As shown, the primary controller periodically sends heartbeat packets to the domain controllers and periodically sends backup data to the backup controller via the ground network. The ground primary controller can sense its own status and, upon detecting a fault, proactively sends an activation packet to the backup primary controller. Upon receiving the activation packet from the primary controller, the backup controller takes over network control and broadcasts an identity packet to all domain controllers, announcing its new status as the primary controller. After receiving the identity packet, all domain controllers immediately send information about their intra-domain network status and inter-domain network topology to the new ground primary controller. Upon recovery, the failed primary controller automatically becomes the backup controller and synchronizes the primary controller's backup data.

[0093] S402, migration strategy for the loss of connection of the ground master controller: select the domain controller with the least number of satellites in the domain as the temporary master controller on the satellite. All domain controllers continue to receive heartbeat packets from the ground master controller. If the domain controller receives a heartbeat packet from the ground master controller within three consecutive cycles, it indicates that the connection between the domain controller and the ground controller has been restored, and a recovery notification is sent to the temporary master controller on the satellite. If the temporary master controller on the satellite receives the recovery notification message from all domain controllers, it returns control to the ground and sends the network control data during the loss of connection to the ground master controller.

[0094] like Figure 3 As shown, the master controller periodically sends heartbeat packets to the domain controllers. If any domain controller in the network fails to receive a heartbeat packet from the master controller within three cycles, it determines that the master controller has lost connection and sends a notification to the other domain controllers, indicating that it has lost connection with the master controller. If any domain controller receives a loss of connection notification from more than half of the domain controllers within three cycles, it indicates that the master controller has lost connection, and the domain controller with the fewest satellites in the domain is elected as the onboard temporary master controller. All domain controllers continue to receive heartbeat packets from the ground master controller. If a domain controller receives a heartbeat packet from the ground master controller within three consecutive cycles, it indicates that the connection between the domain controller and the ground controller has been restored, and a recovery notification is sent to the onboard temporary master controller. If the onboard temporary master controller receives recovery notification messages from all domain controllers, it returns the master controller to the ground and sends network control data during the loss of connection to the ground master controller.

[0095] S403, Migration Strategy for Domain Controller Failure: If the failed domain controller is a standard domain controller, the master controller uses a dynamic re-election algorithm to calculate a new domain controller and sends the new controller ID and other information to other domain controllers in the network. The new domain controller sends an identity packet to other satellites in the domain and performs domain controller functions. If the failed domain controller is a temporary master controller on board, the domain controller with the fewest satellites in the domain is elected as the new temporary master controller on board. All domain controllers continue to receive heartbeat packets from the ground master controller.

[0096] Specifically, if the faulty domain controller is a normal domain controller, a new domain controller is elected based on the dynamic re-election algorithm, and then the domain controller migration is performed. Specifically, the domain controller periodically sends heartbeat packets to all satellites in the domain. If any node in the domain fails to receive the domain controller's heartbeat packet for three consecutive cycles, or detects link failure information in the received heartbeat packet, the domain controller failure information is sent to the main controller. After receiving the failure information from all satellites in the domain, the main controller calls the dynamic re-election algorithm to calculate the new cluster head, designates the new cluster head satellite in the domain as the new domain controller, and sends the new controller ID and other information to other domain controllers in the network. The new domain controller in the domain sends an identity packet to other satellites in the domain to perform the functions of the domain controller. At this time, the destination domain controller ID of the heartbeat packet and identity packet needs to be updated to the new destination domain controller ID. If the failed domain controller is a temporary master controller on board, meaning it has failed, the temporary master controller on board will periodically send heartbeat packets to the domain controllers, similar to the migration method for a ground-based master controller. If any domain controller in the network fails to receive a heartbeat packet from the temporary master controller on board within three cycles, the domain controller will determine that the temporary master controller on board has lost connection and send a notification to the other domain controllers, indicating that the domain controller has lost connection with the temporary master controller on board. If any domain controller receives loss of connection notifications from more than half of the domain controllers within one cycle, it indicates that the temporary master controller on board has failed, and the domain controller with the fewest satellites in the domain will be elected as the new temporary master controller on board. All domain controllers will continue to receive heartbeat packets from the ground-based master controller, regardless of the recovery of the temporary master controller on board. The election mechanism for new domain controllers within the domain is the same as the mechanism for normal domain controller failures.

[0097] The software-defined satellite network fault detection and migration method of the present invention mainly uses fault messages to realize fault detection between controllers. The main controller periodically broadcasts heartbeat packets to the domain controllers. If a domain controller fails to receive the heartbeat packet of the main controller after a continuous timeout, it enters the fault judgment program and sends query packets to other domain controllers, requesting other domain controllers to return the status of the main controller. The domain controller determines whether the main controller is in a complete failure or disconnected state based on the status information returned by the main controller. If the main controller is in a complete failure state, the main controller is migrated to the ground backup controller; if the main controller is in a disconnected state, the domain controller is elected as the temporary main controller on the satellite. The domain controller and the satellite nodes in the domain will also transmit heartbeat packets. If the domain controller fails, it will migrate to a new domain controller according to the dynamic re-election mechanism.

[0098] The fault message primarily includes heartbeat packets between the master controller and domain controller, and between the domain controller and nodes within the domain, identity packets, and activation packets. The heartbeat packet contains a controller identifier, a destination domain controller ID, a timestamp, a sequence number, and status information. The controller identifier uniquely identifies the controller sending the heartbeat packet and can be the ID of either the master or backup master controller. The timestamp records the exact time the heartbeat packet was sent, which is used to detect delays and verify the real-time nature of the heartbeat. The sequence number is a serialized number for the heartbeat packet, used to track the order of heartbeat packets and prevent packet loss or duplication. Status information is an optional field containing current controller status information, such as CPU usage and memory usage, to help monitor controller status. The identity packet contains a type identifier, a new master controller ID, a destination domain controller ID, a timestamp, and a validity period. The type identifier clearly identifies this as an identity packet. The new master controller ID uniquely identifies the new master controller. The timestamp records the time the identity packet was sent, confirming the timeliness of the data. The validity period records the validity window within which the destination domain controller must process the identity packet. The activation packet contains a type identifier, the sending domain controller ID, the destination controller ID, a timestamp, and fault information. The type identifier clearly identifies the data packet as an activation packet, and the destination controller ID is the ID of the backup controller that is expected to receive the activation packet. The timestamp is used to record the time the packet was sent, detect delays, and determine the timeliness of the activation request. The fault information contains relevant information related to the detection of a primary controller failure, such as the time the last heartbeat packet was received.

[0099] In order to reduce the storage overhead of the main controller, the domain controller only stores the local topology information, the main controller stores the global information, and the satellite invisible to the main controller is reported to the main controller by the domain controller. Each satellite node needs to statistically perform the performance of the traffic, packet loss and the like of each port in the node, then encapsulates all the interface statistical information and data information in the node, and sends the information to the domain controller. After the domain controller constructs the local topology, the local topology is periodically notified to the main controller.

[0100] In collecting the real-time state information of each node in the satellite network, in order to judge the survival state of each node and link, each domain controller needs to periodically check the node state information in the domain. The domain controller notifies the main controller of the fault node information.

[0101] One embodiment of the application discloses a software-defined satellite network fault detection and migration system, comprising:

[0102] The heartbeat broadcast module, the main controller and the domain controller periodically send heartbeat packets; the main controller is a ground main controller or a ground backup main controller;

[0103] The domain information synchronization module, the domain controller periodically updates the node state and the routing table in the domain, and notifies the main controller;

[0104] The main control backup module, if the ground backup main controller senses the failure of the ground main controller, judges the failure of the ground main controller, and carries out the migration strategy corresponding to the failure of the ground main controller;

[0105] The main control migration module, if any domain controller does not receive the heartbeat packet of the main controller within 3 periods, judges that the main controller is out of connection, and carries out the migration strategy corresponding to the out-of-connection of the main controller;

[0106] The domain controller migration module, if any node in the domain does not receive the heartbeat packet of the domain controller for 3 consecutive periods, or detects the link failure information in the received heartbeat packet of the domain controller, judges that the domain controller is faulty, and enters the migration strategy of the domain controller failure.

[0107] One embodiment of the present application provides a storage medium, specifically a computer readable storage medium (Memory), which is a memory device in a terminal device, used for storing programs and data. It can be understood that the computer readable storage medium herein can include a built-in storage medium in the terminal device, and of course can also include an expansion storage medium supported by the terminal device, and can be any tangible medium containing or storing programs, which can be used by or in combination with an instruction execution system, device or apparatus. The computer readable storage medium provides a storage space, which stores an operating system of the terminal. Moreover, one or more instructions suitable for being loaded and executed by the processor are also stored in the storage space, and the instructions can be one or more computer programs (including program codes). It should be noted that more specific examples (non-exhaustive list) of the computer readable storage medium herein include an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0108] The computer readable storage medium also includes a data signal carrying the readable program code in a baseband or as a part of a carrier wave. Such a propagated data signal can take any of a variety of forms, including but not limited to electro-magnetic, optical, or any suitable combination thereof. The computer readable storage medium can also be any medium that can be read by the instruction execution system, device or apparatus, or any medium that can convey or store a program for use by or in connection with the instruction execution system, device or apparatus. The program code contained on the computer readable storage medium can be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber cable, RF, or any suitable combination thereof.

[0109] The program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider.

[0110] The processor may load and execute one or more instructions stored in the computer-readable storage medium to implement the corresponding steps of the software-defined satellite network fault detection and migration method in the above embodiment.

[0111] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A software-defined satellite network fault detection and migration method, characterized in that: The following steps are involved: Both the master controller and the domain controller periodically send heartbeat packets; The main controller is a ground main controller or a ground backup main controller; The domain controller periodically updates the node status and routing table within the domain and notifies the master controller; The ground master controller periodically synchronizes its own data with the ground backup master controller; if the ground backup master controller senses a fault in the ground master controller, it determines that the ground master controller has failed and implements the corresponding migration strategy for the ground master controller failure; If any domain controller does not receive the heartbeat packet from the master controller within three cycles, it determines that the master controller is disconnected and implements the corresponding migration strategy for the master controller disconnection; If any node in the domain does not receive the heartbeat packet from the domain controller for three consecutive cycles, or detects link failure information in the heartbeat packet received from the domain controller, it is determined that the domain controller is faulty and the migration strategy for domain controller failure is implemented.

2. The software-defined satellite network fault detection and migration method according to claim 1, characterized in that: The migration strategy for the ground master controller failure is specifically as follows: The ground backup master controller sends an identity packet to the failed master controller, indicating that it has assumed the master controller function; The ground backup master controller takes over the entire network control, switches to the master controller, sends an identity packet to all domain controllers to announce its identity, and then periodically broadcasts heartbeat packets; After receiving the identity packet, all domain controllers update the local master controller information and immediately send the intra-domain network status and inter-domain network topology information to the master controller; After the ground main controller recovers from the fault, it switches to the ground backup main controller and periodically synchronizes the main controller information.

3. The software-defined satellite network fault detection and migration method according to claim 1, characterized in that: The migration strategy for the main controller loss of connection is specifically as follows: If any domain controller detects that it has not received a heartbeat packet from the master controller within three cycles, it will send a connection loss notification to other domain controllers. When any domain controller receives loss of connection notifications from more than half of the domain controllers within three cycles, the domain controller with the least number of satellites in the domain is selected as the on-board temporary master controller; The temporary master controller on board takes over the control of the entire network, sends an identity packet to announce its own identity, and then periodically broadcasts heartbeat packets; After receiving the identity packet, all domain controllers update the local master controller information and immediately send the intra-domain network status and inter-domain network topology information to the onboard temporary master controller; If any domain controller receives a heartbeat packet from the ground within three consecutive cycles, it means that the connection between the domain controller and the main controller has been restored, and the domain controller sends a recovery notification to the temporary main controller on the satellite; When the temporary main controller on the satellite receives the recovery notification message from all domain controllers, it returns control to the main controller and synchronizes the management and control data during the loss of connection.

4. The software-defined satellite network fault detection and migration method according to claim 1, characterized in that: The migration strategy for the domain controller failure is specifically as follows: If any node in the domain fails to receive a heartbeat packet from the domain controller for three consecutive cycles, or detects a link failure in the received heartbeat packet, it sends a domain controller failure message to the master controller. The master controller receives the domain controller failure information and determines whether the failed node is a normal domain controller or a temporary master controller on the satellite; If the failed node is a common domain controller, the master controller elects a new domain controller and sends the new domain controller information to other domain controller nodes; the new domain controller sends an identity packet to the satellite in the domain and performs the domain controller function; If the failed node is the temporary master controller on the satellite, the domain controller with the least satellites in the domain will be elected as the new temporary master controller on the satellite.

5. The software-defined satellite network fault detection and migration method according to claim 4, characterized in that: The master controller elects a new domain controller using a dynamic re-election algorithm.

6. The software-defined satellite network fault detection and migration method according to claim 1, characterized in that: The ground backup main controller senses a ground main controller failure, specifically: The ground master controller periodically synchronizes its own data to the ground backup master controller; the self-data includes global topology and routing table information; The ground backup main controller did not receive the main controller synchronization data within one cycle, and determined that the ground main controller was completely faulty.

7. A software-defined satellite network fault detection and migration method, applied to a domain controller, characterized in that: The following steps are involved: Send heartbeat packets periodically; Periodically receive heartbeat packets from the master controller and other domain controllers; Periodically sends domain node status and domain routing table information to the main controller; If no heartbeat packet is received from the master controller within three cycles, a connection loss notification is sent to other domain controllers; If a loss of connection notification is received from more than half of the domain controllers, the domain controller with the least satellites in the domain will be elected as the temporary master controller on board; The onboard temporary master controller sends an identity packet and then periodically broadcasts a heartbeat packet; After receiving the identity packet of the temporary master controller on the satellite, all domain controllers update the local master controller information; After the domain controller receives heartbeat packets from the master controller for three consecutive cycles, it sends a recovery notification to the temporary master controller on board. After the temporary master controller on board receives the recovery notification messages from all domain controllers, it returns control to the master controller and synchronizes the management and control data during the loss of connection. If any node in the domain does not receive the heartbeat packet from the domain controller for three consecutive cycles, or detects link failure information in the received heartbeat packet, it sends the domain controller failure information to the main controller; The domain controller receives the fault node type information and fault migration information; The fault node type includes a common domain controller or an on-board temporary master controller; the fault migration information includes new domain controller information corresponding to the common domain controller or new on-board temporary master controller information corresponding to the on-board temporary master controller.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the software-defined satellite network fault detection and migration method according to any one of claims 1 to 7 is implemented.

9. A software-defined satellite network fault detection and migration system, characterized in that: include: Heartbeat broadcast module, the main controller and domain controller both periodically send heartbeat packets; The main controller is a ground main controller or a ground backup main controller; In the domain information synchronization module, the domain controller periodically updates the node status and routing table within the domain and notifies the main controller; The main control backup module, if the ground backup main controller senses the failure of the ground main controller, determines that the ground main controller has failed and implements the corresponding migration strategy for the ground main controller failure; The master controller migration module determines that the master controller is disconnected if any domain controller does not receive the heartbeat packet from the master controller within three cycles, and implements the corresponding master controller disconnection migration strategy; The domain controller migration module determines that the domain controller is faulty and enters the migration strategy for domain controller failure if any node in the domain fails to receive the heartbeat packet from the domain controller for three consecutive cycles, or detects link failure information in the received heartbeat packet from the domain controller.

Images