Cooperative management method and system for multi-domain fc-ae-1553 network

Abstract

The application discloses a kind of multi-domain FC-AE-1553 network's cooperative management method and system, it is related to communication technical field, method includes: for each network controller and network terminal configuration address, and in each FC-AE-1553 subnet switch implementation security partition strategy, realize default state each subnet independent operation and prohibit cross subnet communication;Each subnet network controller state is monitored and fault is judged;When first FC-AE-1553 subnet network controller fault is confirmed, by authorization configuration, allow the subnet switch to cross subnet communication, by second FC-AE-1553 subnet takeover its network terminal service;When fault network controller recovers, execute recovery operation and restore management authority and switch strategy to default state.The application can greatly reduce the number of redundant controllers, reduce cost, and break through single network redundancy limit, realize fault-tolerant backup, improve the reliability and scalability of multi-domain system.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a method and system for cooperative management of a multi-domain FC-AE-1553 network. BACKGROUND

[0002] With the increasing complexity of avionics, spacecraft and high-performance shipboard vehicle systems, multi-domain cooperative systems composed of multiple FC-AE-1553 networks (Fiber Channel-Avinonics Environment-Upper Layer Protocl, where FC: Fiber Channel) interconnected have gradually become the norm. As a new generation of avionics standard, FC-AE-1553 network realizes a huge leap in data throughput by transplanting the command / response mechanism of MIL-STD-1553B bus to fiber channel infrastructure while inheriting determinism and reliability. FC-AE-1553 network is mainly composed of network controller, network terminal and switch, as shown in Figure 1 FC-AE-1553 network includes a network controller responsible for traffic management, multiple distributed network terminals and a switch as a communication hub. All nodes are directly connected to different physical ports of the switch through independent fiber links, thus forming a star-shaped switched fiber network topology centered on the switch. This architecture ensures that the network controller and each network terminal can establish a high-bandwidth, full-duplex point-to-point dedicated communication channel through the switch. The network controller is responsible for initiating and controlling all communication traffic according to the FC-AE-1553 protocol in the entire FC-AE-1553 network, while each network terminal responds to the instructions of the network controller to complete specific data transmission or reception tasks. The switch plays a key role in unblocking data exchange and provides a deterministic low-latency transmission path for data flow between all nodes. This basic network architecture is the physical and logical basis for implementing more complex multi-domain FC-AE-1553 network cooperative management.

[0003] FC-AE-1553 networks are widely used in military and civilian avionics systems, spacecraft, and integrated electronic systems for ships and ground vehicles where performance and reliability requirements are extremely high. In such complex systems, traditional reliability assurance schemes are limited to the individual FC-AE-1553 network, such as configuring primary and backup network controllers for each independent FC-AE-1553 network or using fiber optic interface hot redundancy backup. This approach has inherent drawbacks: the backup network controller for each network remains idle for extended periods, resulting in low hardware resource utilization, high system costs, and limited scalability. More importantly, it cannot handle the extreme situation where both the primary and backup network controllers of a network fail, and backup resources cannot cross network boundaries to provide redundant support to other FC-AE-1553 networks. When both primary and backup network controllers fail, communication services for the failed network are completely interrupted, and network controllers in other networks cannot cross network boundaries to take over the equipment of the failed network. This significantly reduces the overall mission reliability and survivability of large multi-domain network systems.

[0004] To address the issue of fixed functionality in single nodes and enhance hardware flexibility, existing technologies have introduced node hardware solutions with reconfigurable roles. For example, Chinese patent CN103905281A, entitled "FC-AE-1553 Bus Node Card for Interchangeable Network Controller and Network Terminal Functions," proposes a specific hardware design. This node card integrates an FC-AE protocol processing unit, a programmable logic controller, and different application interfaces. By selecting different configurations at the physical level, it can function as both a network controller connecting to a host computer for remote monitoring and a network terminal connecting to peripherals for data exchange. This achieves dual node functions in a single card, improving the flexibility and versatility of a single node.

[0005] However, such hardware-level node reconfiguration solutions still focus on function switching within a single device and do not address the collaborative management issues between multi-domain FC-AE-1553 networks at the system architecture level. They cannot achieve dynamic resource sharing and unified scheduling across FC-AE-1553 subnets, nor can they establish a system-level management mechanism capable of rapid and orderly fault takeover and service recovery across network boundaries in the event of a failure. For multi-domain systems composed of multiple FC-AE-1553 networks, the network controller resources of each subnet still cannot achieve efficient mutual backup and cross-domain sharing. Therefore, even if individual nodes have role-swapping capabilities, without corresponding cross-network collaborative management methods, the resource waste, high costs, and systemic reliability bottlenecks faced by multi-domain FC-AE-1553 networks as a whole remain fundamentally unresolved.

[0006] Therefore, for a complex system of a multi-domain FC-AE-1553 network, a system-level collaborative management method is urgently needed, which can realize resource backup and fault takeover across networks while keeping each FC-AE-1553 subnet running independently by default, thereby fundamentally improving the reliability, resource utilization and scalability at the system level. The present application is proposed based on this purpose. SUMMARY

[0007] The technical problem to be solved by the present application is to overcome the deficiencies of the prior art, and specifically to provide a collaborative management method and system for a multi-domain FC-AE-1553 network, as follows:

[0008] 1) In a first aspect, the present application provides a collaborative management method for a multi-domain FC-AE-1553 network, and the specific technical solutions are as follows:

[0009] The multi-domain FC-AE-1553 network includes a plurality of FC-AE-1553 subnets interconnected by switches, each FC-AE-1553 subnet includes a network controller, a network terminal and a switch, and the method includes:

[0010] Each network controller and each network terminal is configured with an address, and a security partition strategy is implemented on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet runs independently by default and cross-subnet communication is prohibited;

[0011] The running state of the network controller of each FC-AE-1553 subnet is monitored and fault judgment is performed;

[0012] When the network controller of the first FC-AE-1553 subnet is confirmed to have failed, an authorized configuration operation is performed to allow cross-subnet communication by the switch of the first FC-AE-1553 subnet, and the second FC-AE-1553 subnet takes over the service of the network terminal of the first FC-AE-1553 subnet;

[0013] When the network controller of the first FC-AE-1553 subnet recovers, a recovery operation is performed to restore the management authority of the network controller of the second FC-AE-1553 subnet and the communication strategy of the related switch to the default state;

[0014] Wherein, the first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in the multi-domain FC-AE-1553 network.

[0015] The collaborative management method for a multi-domain FC-AE-1553 network provided by the present application has the following advantages:

[0016] By constructing the cooperative management mechanism across the FC-AE-1553 subnets, the network controller resources of each subnet can provide backup capability for other subnets, the resource sharing mode of 'one backup for multiple' is realized, thereby the hardware quantity of the redundant network controller is reduced, the overall cost, weight and power consumption of the system are directly reduced, and the utilization rate of the hardware resources is greatly improved. The method breaks through the limitation of the traditional single-network internal redundancy, realizes the system-level fault backup across the subnets through dynamic authorization configuration, when the network controller of a subnet fails, the system can quickly take over the functions of the network controller of the other healthy subnet, effectively avoids the serious consequences of the communication service interruption of the whole subnet caused by the failure of a single node, and fundamentally improves the overall task reliability and survivability of the multi-domain system. In addition, the architecture design of the method is independent of the number of subnets, and the newly added FC-AE-1553 subnet only needs to be connected to the existing interconnection architecture to obtain the cooperative management capability, without changing the hardware connection and management logic of the existing subnet, and has good scalability and deployment flexibility.

[0017] On the basis of the above scheme, a cooperative management method of a multi-domain FC-AE-1553 network of the application can be further improved as follows.

[0018] Further, an address is configured for each network controller and each network terminal, comprising:

[0019] A globally unique 24-bit FC address is allocated for each network controller and each network terminal, and the 24-bit FC address comprises domain identification, area identification and port identification, wherein the domain identification is used to uniquely identify the FC-AE-1553 subnet to which the network controller and the network terminal belong.

[0020] The beneficial effects of the above further scheme are that a globally unique 24-bit FC address containing domain identification, area identification and port identification is allocated for each network controller and network terminal, and a unified cross-network addressing system is established. The domain identification ensures that each node can be uniquely identified as the FC-AE-1553 subnet to which it belongs, which provides a fundamental basis for the switch to accurately judge whether the data frame is an internal communication of the subnet or needs to be forwarded across the subnet, thereby laying a reliable addressing foundation for subsequent implementation of logical isolation and on-demand cross-network communication under the security partition strategy, and ensuring the accuracy and reliability of data routing in the cross-network fault takeover process.

[0021] Further, the method further comprises:

[0022] The service traffic scheduled by the network controller of the second FC-AE-1553 subnet is classified and configured with a quality of service priority, and the critical management traffic from the network terminal of the taken-over first FC-AE-1553 subnet is configured with a higher forwarding priority than the regular task data.

[0023] The beneficial effect of the above further scheme is that the traffic flow scheduled by the network controller of the second FC-AE-1553 subnet is classified and configured with a quality of service priority, ensuring that in the cross-network takeover scenario, critical management traffic from the network terminal of the first FC-AE-1553 subnet being taken over can be forwarded in priority to regular task data. This effectively guarantees the transmission timeliness and reliability of management messages such as heartbeats and status instructions with high real-time requirements during fault takeover, avoids critical communication congestion due to traffic surge, and thus maintains the stability of the basic control link of the taken-over network, which is an important guarantee for improving the task continuity of the entire system in a collaborative management state.

[0024] Further, the running state of the network controller of each FC-AE-1553 subnet is monitored and fault judgment is performed, including:

[0025] The running state of the network controller of each FC-AE-1553 subnet is monitored and fault judgment is performed through heartbeat telemetry information.

[0026] The beneficial effect of the above further scheme is that by continuously monitoring the heartbeat telemetry information from the network controllers of the FC-AE-1553 subnets, real-time and reliable fault awareness capability is provided. This monitoring mechanism based on periodic status reporting can timely discover abnormal states of the network controllers and serve as an accurate basis for triggering subsequent cross-network collaborative management processes, thereby ensuring the timeliness and accuracy of fault judgment, laying a key foundation for rapid and automatic fault takeover and recovery of the entire multi-domain FC-AE-1553 network, and effectively improving the overall survivability.

[0027] 2) In a second aspect, the present application also provides a collaborative management system for a multi-domain FC-AE-1553 network, and the specific technical scheme is as follows:

[0028] The multi-domain FC-AE-1553 network includes a plurality of FC-AE-1553 subnets interconnected by switches, each FC-AE-1553 subnet including a network controller, a network terminal, and a switch, and the system includes a configuration implementation module, a monitoring fault judgment module, an authorization configuration module, and an execution recovery module;

[0029] The configuration implementation module is configured to configure an address for each network controller and each network terminal, and implement a security partitioning strategy on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet runs independently in a default state and cross-subnet communication is prohibited;

[0030] The monitoring fault judgment module is configured to monitor the running state of the network controller of each FC-AE-1553 subnet and perform fault judgment;

[0031] The authorization configuration module is configured to: when the network controller of the first FC-AE-1553 subnet is confirmed to fail, through an authorization configuration operation, allow the switch of the first FC-AE-1553 subnet to communicate across the subnet, and allow the second FC-AE-1553 subnet to take over the service of the network terminal of the first FC-AE-1553 subnet.

[0032] The execution recovery module is configured to: when the network controller of the first FC-AE-1553 subnet recovers, perform a recovery operation to restore the management authority of the network controller of the second FC-AE-1553 subnet and the communication strategy of the related switch to a default state.

[0033] The first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in the multi-domain FC-AE-1553 network.

[0034] On the basis of the above scheme, the multi-domain FC-AE-1553 network cooperative management system of the application can be further improved as follows.

[0035] Further, the configuration implementation module is further configured to: assign each network controller and each network terminal a globally unique 24-bit FC address, and the 24-bit FC address includes a domain identifier, a region identifier and a port identifier, wherein the domain identifier is used to uniquely identify the FC-AE-1553 subnet to which the network controller and the network terminal belong.

[0036] Further, the priority configuration module is further configured to: classify and configure the quality of service priority for the service traffic scheduled by the network controller of the second FC-AE-1553 subnet, and configure the forwarding priority of the critical management traffic from the network terminal of the taken-over first FC-AE-1553 subnet to be higher than that of the regular task data.

[0037] Further, the monitoring failure judgment module is further configured to: monitor the running state of each network controller of each FC-AE-1553 subnet through heartbeat telemetry information and make a failure judgment.

[0038] 3) In a third aspect, the application further provides an electronic device, which comprises a processor and a memory coupled with the processor, and the memory stores at least one computer program, the at least one computer program is loaded and executed by the processor, so that the electronic device realizes any one of the above multi-domain FC-AE-1553 network cooperative management methods.

[0039] 4) In a fourth aspect, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-mentioned collaborative management methods for multi-domain FC-AE-1553 networks.

[0040] It should be noted that the beneficial effects of the technical solutions of the second to fourth aspects of the present invention and their corresponding possible implementations can be found in the above description of the technical effects of the first aspect and its corresponding possible implementations, and will not be repeated here. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments of the present invention will be briefly introduced below:

[0042] Figure 1 This is a schematic diagram of the FC-AE-1553 network structure;

[0043] Figure 2 This is a flowchart illustrating a collaborative management method for a multi-domain FC-AE-1553 network according to an embodiment of the present invention.

[0044] Figure 3 A schematic diagram of the interconnection architecture of a multi-domain FC-AE-1553 network;

[0045] Figure 4 A diagram illustrating the allocation of FC addresses;

[0046] Figure 5 This is a schematic diagram of the data flow in cross-network communication;

[0047] Figure 6 This is a schematic diagram of the structure of a collaborative management system for a multi-domain FC-AE-1553 network according to an embodiment of the present invention. Detailed Implementation

[0048] The principles and features of the present invention are described below. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0049] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0050] like Figure 2 As shown in the figure, a collaborative management method for a multi-domain FC-AE-1553 network according to an embodiment of the present invention includes the following steps:

[0051] S1, configure addresses for each network controller and each network terminal respectively, and implement security partitioning strategy on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet runs independently in the default state and cross-subnet communication is prohibited;

[0052] The multi-domain FC-AE-1553 network comprises a plurality of FC-AE-1553 subnets interconnected by switches, and each FC-AE-1553 subnet comprises a network controller, a network terminal and a switch.

[0053] Each independent FC-AE-1553 subnet is a functionally complete standard FC-AE-1553 network, and comprises one or more network controllers, a plurality of network terminals and one or more switches. When the network is deployed, each network terminal and network controller is directly connected to a specific physical port of the switch through an optical fiber cable, thereby forming a star-shaped switched fiber network topology. In the FC-AE-1553 subnet, the network controller assumes a management role and is responsible for initiating and controlling all communication tasks according to the command response mechanism specified in the FC-AE-1553 protocol. The network terminal is a controlled node that responds to the instructions issued by the network controller to complete data transmission tasks or reception tasks. The switch serves as the communication hub of the subnet and provides high-bandwidth, full-duplex and non-blocking point-to-point data exchange channels for all devices connected to the switch, ensuring the determinism and low latency of communication within the FC-AE-1553 subnet.

[0054] After successfully constructing a plurality of independent FC-AE-1553 subnets, the FC-AE-1553 subnets are interconnected to form a multi-domain FC-AE-1553 network. The specific implementation method of interconnection is to connect the switches in different FC-AE-1553 subnets through cross-network fiber links. These interconnection links are usually configured on the designated high-speed ports of the switches and are specifically used to handle data flow between different FC-AE-1553 subnets. This cascading method physically realizes the fusion of multiple FC-AE-1553 subnets and constitutes a unified network infrastructure with a wider coverage and more nodes.

[0055] In the operation logic of the multi-domain FC-AE-1553 network, a strict security partition strategy is adopted. Although the FC-AE-1553 subnets have been interconnected, each FC-AE-1553 subnet is still logically isolated and independent by default. The security partition strategy of the switch is set to ensure that the network controller and the network terminal of each FC-AE-1553 subnet can only communicate freely within the FC-AE-1553 subnet to which they belong. Any communication request from one FC-AE-1553 subnet to another FC-AE-1553 subnet will be discarded by the switch by default. This design ensures the inherent independence, security and determinacy of communication behavior of each FC-AE-1553 subnet in daily operation, avoiding unauthorized cross-network access and potential problems.

[0056] The cooperative management capability of the entire multi-domain FC-AE-1553 network is realized based on this "physical interconnection, logical isolation" architecture. When cross-network fault takeover or global task scheduling is required, authorized instructions are issued to specific network controllers and switches to dynamically modify their configurations. The network controller updates its communication management object list accordingly, and the switch temporarily opens the cross-subnet communication path. This design enables the network to maintain stable and independent operation of each subnet in normal state, and to quickly integrate resources when necessary to realize cross-domain cooperative management and high reliability guarantee, thus constituting a comprehensive network solution with flexibility, scalability and high survivability.

[0057] Among them, an address is configured for each network controller and each network terminal, including:

[0058] A globally unique 24-bit FC address is allocated for each network controller and each network terminal, and the 24-bit FC address includes domain identification, area identification and port identification, wherein the domain identification is used to uniquely identify the FC-AE-1553 subnet to which the network controller and the network terminal belong.

[0059] In constructing a multi-domain FC-AE-1553 network, first, a globally unique 24-bit FC address needs to be assigned to each network controller and each network terminal in the multi-domain FC-AE-1553 network. This address assignment process is the fundamental basis for realizing cross-network collaborative management. In implementation, the globally addressing scheme can be pre-prepared by the designer, and the FC addresses can be statically or dynamically configured through a network management configuration tool or directly in the firmware of each network controller and each network terminal. In the power-on initialization process of each network controller and network terminal, the assigned FC address is written into the fiber channel hardware register of the device, and serves as the unique identity of the network controller or network terminal in all subsequent fiber channel communication processes. The switch opportunities in the multi-domain FC-AE-1553 network automatically discover and maintain the mapping relationship between the FC addresses and the switch physical ports through the learning mechanism of the fiber channel protocol, thereby establishing accurate data forwarding paths in the network. This complete global addressing scheme logically ensures that any network controller in any FC-AE-1553 subnet in the entire multi-domain FC-AE-1553 network can uniquely and accurately address the target device through the FC address of the target device, even if the target network controller or network terminal is located in another different FC-AE-1553 subnet. This addressing capability is the technical prerequisite for realizing the cross-subnet fault takeover function of the network controller.

[0060] In the present application, the FC address refers to a digital code with a length of 24 bits for uniquely identifying each network controller and each network terminal at the network layer. The FC address strictly follows the definition of the fiber channel protocol standard and is carried in the frame header of each FC network frame to explicitly indicate the originating node and the receiving destination node of the data frame. Its role is to provide a precise addressing system for the entire fiber channel network and ensure that data can be correctly routed and delivered by network devices. The 24-bit FC address space is not randomly assigned, but is organized into three fields with specific functions, and the three fields together constitute a hierarchical, easy-to-manage and expandable addressing structure.

[0061] Wherein, the domain identifier is the highest part of the three fields constituting the 24-bit FC address, occupying 8 bits. It is the highest level identifier in the entire address structure, covering the widest range. In the address planning of the present application for multi-domain FC-AE-1553 network, each physically independent and logically autonomous FC-AE-1553 subnet is assigned a unique domain identifier code that is not repeated with all other subnets. When processing each data frame passing through it, the first step of the routing decision of the switch in the network is to parse the domain identifier information contained in the destination FC address of the data frame. By comparing the domain identifier of the data frame with the subnet identifier served by the switch itself, the switch can immediately judge whether the target of the data frame is located in the subnet or needs to be sent to other subnets. This judgment result is the fundamental basis for determining the subsequent flow direction of the data frame and is the key to realizing the logical isolation and controllable communication between subnets.

[0062] Wherein, the area identifier is an 8-bit field next to the domain identifier, which provides a secondary hierarchical logical structure within the subnet range defined by the domain identifier. The area identifier is used to group the network controllers and network terminals within the same FC-AE-1553 subnet in a more fine-grained manner. This division is not based on physical location, but on logical factors such as function, service type or management strategy. By introducing this level of area identifier, network administrators can more finely plan the traffic path within the subnet, implement access control strategies and optimize broadcast domains, thereby improving the manageability and operating efficiency of the network. Based on the known target subnet, the switch can further use the area identifier to narrow the addressing range and achieve faster and more accurate data frame switching.

[0063] Wherein, the port identifier is the lowest 8-bit field in the 24-bit FC address, representing the most terminal positioning information in the entire addressing system. The port identifier usually has a direct or indirect mapping relationship with a specific physical port number on the switch, and its main function is to uniquely identify the final network controller or network terminal device within a logical group determined by the domain identifier and the area identifier. When the data frame has passed through the routing and finally reaches the target area within the target subnet, the switch will perform the last step of operation, i.e. according to the port identifier in the lowest 8 bits of the FC address, the data frame is accurately forwarded to the target device connected to the corresponding physical port. The port identifier ensures that each network node has a unique identification code within the smallest logical unit, thereby perfectly realizing the end-to-end precise positioning from the macroscopic subnet, to the mesoscopic area, to the microscopic specific device.

[0064] Wherein, a security partitioning strategy is implemented on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet runs independently and prohibits cross-subnet communication in the default state, and the specific implementation process is as follows:

[0065] Each FC-AE-1553 subnet needs to be assigned a domain identifier range according to the pre-planned global addressing scheme. Then, a dedicated logical zoning is created for each independent FC-AE-1553 subnet by configuring the switch. When creating the zoning, all globally unique FC addresses of the network controllers and network terminals belonging to the FC-AE-1553 subnet are added to the member list of the zoning. The policy enforcement engine inside the switch checks each data frame passing through according to the zoning configuration. In the default running state, the switch is configured with a strict zoning policy. When the switch receives a data frame, it extracts the destination FC address and checks its domain identifier. If the domain identifier does not match the domain identifier of the zoning that the port receiving the data frame belongs to, it is determined that this is a cross-subnet communication request. According to the pre-set security zoning policy, the switch directly discards the data frame without forwarding it from the cross-network interconnection port. This mechanism enforces logical isolation from the data link layer, ensuring the communication boundary of each FC-AE-1553 subnet. In order to realize dynamic switching during fault takeover, both the switch and the network controller need to support dynamic reconfiguration capability. When it is confirmed that cross-network takeover is needed, an authorization instruction is sent to the switch of the relevant subnet. After receiving the authorization instruction, the switch dynamically adjusts its zoning policy and temporarily modifies the rules for specific cross-network interconnection ports, so that the communication data originally prohibited, which is sent to or comes from the specified fault subnet, can pass through. Similarly, after the fault is recovered, the switch receives an instruction again to restore the zoning policy to the default isolation state, thereby realizing flexible and reliable switching between the independent running and collaborative management modes of the network.

[0066] The security zoning policy is an access control mechanism in a fiber channel network, which restricts the communication ability between nodes by establishing a logical isolation boundary on the switch. In the multi-domain FC-AE-1553 network of the present application, the security zoning policy is used to divide each physically interconnected FC-AE-1553 subnet into an independent logical zoning. The rule is to allow unimpeded communication between the network controllers and network terminals within the zoning, but to prohibit any data frame exchange between different zoning by default. The basis for implementing this policy is the global FC address of the nodes, and the switch determines the zoning to which the data frame belongs according to the domain identifier in the source and destination addresses of the data frame and performs the action of allowing or discarding. This policy not only realizes the logical isolation and safe autonomy of each subnet, preventing unauthorized cross-network access and broadcast storm spreading, but more importantly, it provides a controllable communication basis for cross-network fault takeover. By dynamically adjusting the zoning members or rules, specific cross-subnet communication paths can be opened on demand under the premise of ensuring safety.

[0067] S2, monitoring the running state of the network controller of each FC-AE-1553 subnet and making fault judgment, specifically, monitoring the running state of the network controller of each FC-AE-1553 subnet through heartbeat telemetry information and making fault judgment, the specific implementation process is as follows:

[0068] ①The network controller of each FC-AE-1553 subnet will periodically generate and broadcast heartbeat telemetry information. These information are encapsulated in specific fiber channel frames, transmitted within the subnet through the switch connected thereto, and delivered to the monitoring module in the entire multi-domain FC-AE-1553 network via cross-network interconnection link. The monitoring module can usually be an independent ground monitoring station or a centralized network management unit, which continuously listens to and receives these periodic heartbeat signals from the network controllers of all FC-AE-1553 subnets.

[0069] ②The monitoring module maintains a state table and a timer corresponding to each network controller inside. When an effective heartbeat frame is received, the state record of the corresponding network controller is updated, and its timer is reset. The heartbeat telemetry information contains a series of key state parameters, which together reflect the health of the network controller. The fault diagnosis logic of the monitoring module performs two tasks in parallel: one is to strictly monitor whether the heartbeat signal is overdue, that is, if the heartbeat signal of any network controller is not received within the preset time window, an overdue alarm is triggered immediately; the second is to analyze the key state parameters carried in the heartbeat frame, and check whether the values are within the preset normal working range.

[0070] ③Fault judgment is a multi-step confirmation process. When the monitoring module first detects potential fault signs, such as heartbeat timeout or abnormal key parameters, it does not immediately determine the fault, but starts a short confirmation period during which it attempts to reestablish communication with the target network controller or waits for the subsequent heartbeat frame. If the heartbeat state of the target network controller has not returned to normal at the end of the confirmation period, or the ground operator receives key telemetry information through the downlink channel that also proves abnormal state, the monitoring module finally confirms that the network controller has failed. Once the fault is confirmed, the monitoring module or the ground operator will generate and send uplink the corresponding fault confirmation instruction and subsequent authorized configuration instruction, thereby triggering the cross-network takeover process.

[0071] Heartbeat telemetry information is a kind of state message periodically and actively sent by the network controller to announce its survival state and report key operating parameters. The information is encapsulated in a specific fiber channel data frame, which usually contains a unique controller identifier, a sequence number to detect packet loss, timestamp information, and a series of key parameters reflecting the internal working state of the controller, such as processor load, memory usage, temperature, power state, and connection state with key network terminals. The purpose is to provide a real-time, lightweight operating condition indication channel for the upper monitoring module, so that the monitoring module can continuously and efficiently evaluate the health status of the network controllers distributed in the multi-domain network without frequent large-scale polling, and provide decisive basis for fast and accurate fault detection and judgment.

[0072] S3, when the network controller of the first FC-AE-1553 subnet is confirmed to have failed, the switch of the first FC-AE-1553 subnet is allowed to communicate across the subnet by authorization configuration operation, and the second FC-AE-1553 subnet takes over the service of the network terminal of the first FC-AE-1553 subnet, specifically:

[0073] ① When the network controller of the first FC-AE-1553 subnet is confirmed to have failed, the monitoring module or the ground control station generates and sends up specific authorization configuration instructions. These instructions are respectively sent to the switch of the first FC-AE-1553 subnet and the network controller of the second FC-AE-1553 subnet through a dedicated control channel.

[0074] ② After receiving the authorization instruction, the switch of the first FC-AE-1553 subnet performs configuration switching operation. The switch will dynamically adjust its security partition strategy, which is specifically manifested as: enabling its cross-network interconnection port, modifying the port forwarding rule, and allowing the cross-subnet communication data that was originally prohibited to pass. This means that the data frames sent to or from other FC-AE-1553 subnets and destined for network terminals within the first FC-AE-1553 subnet will be allowed to be transmitted through the interconnection port. At the same time, the switch may improve the quality of service priority of specific management traffic according to the instruction to ensure that critical instructions during the takeover process can be preferentially and low-delay forwarded.

[0075] The authorization configuration operation of the switch of the second FC-AE-1553 subnet during cross-network takeover is as follows:

[0076] When the monitoring system or ground control station confirms that the network controller of the first FC-AE-1553 subnet has failed, it will generate a specific authorization configuration instruction and issue it to the switch of the second FC-AE-1553 subnet through a dedicated control channel. After receiving the authorization instruction, the switch first performs instruction verification to ensure its legality and validity, and then starts the dynamic reconfiguration process. The core configuration operation of the switch is to adjust its security partition strategy, which is specifically to enable its cross-network interconnection port, modify the access control rules of the port, allow communication data from the first FC-AE-1553 subnet to pass through, and configure the cross-network transmission authority of the broadcast message according to the instruction requirements. In terms of quality of service configuration, the switch will enable service level-based priority scheduling mechanism on its port, configure higher forwarding priority for critical management traffic from the taken-over subnet, and ensure that these traffic can be processed in priority to regular task data. In addition, the switch will also update its routing and forwarding table to direct data frames destined for network terminals in the first FC-AE-1553 subnet to the cross-network interconnection port for forwarding. These configuration changes enable the switch of the second FC-AE-1553 subnet to correctly identify and forward all FC-AE-1553 protocol command frames sent by its network controller to network terminals in the first FC-AE-1553 subnet, while also reliably receive response data from these network terminals, thereby providing stable and reliable underlying communication guarantee for cross-network service takeover. The entire configuration process ensures that while maintaining normal communication of the subnet, a dedicated high-quality transmission channel is established for cross-domain management traffic.

[0077] ③The network controller of the second FC-AE-1553 subnet also receives the corresponding authorization instruction. The instruction triggers the network controller to update its communication management strategy, and the operation is to dynamically switch its communication white list. Under the default configuration, the white list only contains the network terminal addresses within the second FC-AE-1553 subnet. After receiving the authorization, the network controller adds the globally unique FC addresses of all network terminals in the first FC-AE-1553 subnet to its valid communication object list. This step logically greatly expands the management authority and communication range of the network controller of the second FC-AE-1553 subnet, giving it a legal identity to establish a communication session with network terminals in the failed subnet.

[0078] ④After the above key authorization configuration operations are completed, the service takeover phase begins. Based on the updated communication white list, the network controller of the second FC-AE-1553 subnet begins to send FC-AE-1553 protocol specified command frames to the network terminals of the first FC-AE-1553 subnet. These command frames are sent from the network controller of the second FC-AE-1553 subnet, enter the switch of the first FC-AE-1553 subnet via the cross-network interconnection port of the subnet switch, and are finally routed to the target network terminal. After receiving the valid commands from the new network controller, the network terminal will respond according to the protocol specification, thereby completing the sending and receiving of service data. During the entire takeover process, the switches of the two subnets cooperate to ensure that the cross-network data flow can be accurately and reliably routed according to the global addressing scheme and the updated forwarding strategy, and finally realize the full and seamless takeover of the network terminals of the first FC-AE-1553 subnet by the network controller of the second FC-AE-1553 subnet.

[0079] In the formula, the first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in a multi-domain FC-AE-1553 network.

[0080] S4, when the network controller of the first FC-AE-1553 subnet recovers, a recovery operation is performed to restore the management authority of the network controller of the second FC-AE-1553 subnet and the communication strategy of the related switch to the default state, specifically:

[0081] The ground monitoring module or centralized management unit generates and sends uplink a recovery instruction sequence after confirming that the original faulty network controller has stabilized and returned to a normal working state. These instructions are first sent to the network controller of the second FC-AE-1553 subnet, ordering it to restore the communication white list from the extended list in the takeover state to the default configuration, i.e., removing all network terminal addresses belonging to the first FC-AE-1553 subnet from its valid communication object list. This operation logically removes the management right of the network controller of the second FC-AE-1553 subnet over the network terminals of the first FC-AE-1553 subnet. The recovery instruction is sent synchronously to the related switches, i.e., the switches of the first FC-AE-1553 subnet and the switches of the second FC-AE-1553 subnet. After receiving the instruction, these switches will immediately perform a rollback operation of the communication strategy. They will disable the advanced forwarding right of the cross-network interconnection port temporarily opened for cross-network takeover and reactivate the strict default security partition strategy. This strategy forces the switches to restore the domain identification-based filtering check, and all FC data frames with source or destination addresses whose domain identification does not belong to the subnet will be prohibited from passing through and discarded. At the same time, the network controller of the first FC-AE-1553 subnet that has returned to normal begins to reinitialize, loads its default configuration, and its communication white list only contains the network terminal addresses within the subnet, and it starts to send heartbeat telemetry information again, declaring itself as the legitimate controller of the network. The entire recovery operation ensures that the network controller of the second FC-AE-1553 subnet releases the temporary external management right, and the data plane of all related switches returns to the strict intra-domain communication mode, so that both FC-AE-1553 subnets exit the cooperative management state and completely return to the initial, isolated independent operation mode.

[0082] Among them, the management right of the network controller of the second FC-AE-1553 subnet refers to the legitimate qualification that the network controller has to communicate and control the network terminals in the first FC-AE-1553 subnet during the authorized cross-network takeover. This right is specifically manifested in that its communication white list contains the globally unique FC addresses of all network terminals in the first FC-AE-1553 subnet, enabling it to send command frames to these network terminals and receive responses according to the FC-AE-1553 protocol specification, thereby scheduling and managing their communication traffic. In the default state, the network controller does not have this cross-subnet management right.

[0083] The communication policy of the relevant switches refers to the set of forwarding and filtering rules applied by the switches of the first FC-AE-1553 subnet and the switches of the second FC-AE-1553 subnet during the period of co-management, which allows specific cross-subnet communication data to pass. This includes temporary modification of the security partition policy to enable cross-network communication, special allowed rules set for cross-network interconnection ports, and quality of service priority settings that may be adjusted to ensure takeover traffic. The restoration operation is to cancel these temporary changes in policy to support cross-network takeover.

[0084] The default state refers to the baseline running configuration of the multi-domain FC-AE-1553 network when no co-management mechanism is triggered. In this state, each FC-AE-1553 subnet is a logically self-consistent and closed independent system. Specifically, the communication white list of the network controller of each subnet only contains the network terminal addresses within its own subnet, and each subnet's switch strictly enforces a security partition policy that prohibits any FC data frame with a domain identifier that does not belong to the subnet from passing through, thereby achieving complete isolation between subnets at the communication level and ensuring the independence and determinism of each network.

[0085] Optionally, in the above technical solution, further comprising:

[0086] The service traffic scheduled by the network controller of the second FC-AE-1553 subnet is classified and configured with quality of service priority, and the critical management traffic from the network terminals of the first FC-AE-1553 subnet being taken over is configured with higher forwarding priority than regular task data, and the specific implementation process is as follows:

[0087] ① The network controller of the second FC-AE-1553 subnet identifies and classifies all service traffic that needs to be scheduled. When the network controller of the second FC-AE-1553 subnet takes over the network terminal service of the first FC-AE-1553 subnet, the data stream it schedules will contain both its original subnet's service and the service from the taken-over subnet. According to the pre-defined policy, based on the content, source or type of the data frame, these service traffic is divided into different categories. Specifically, the heartbeat information, status confirmation messages, control instruction responses, etc. from the network terminals of the first FC-AE-1553 subnet being taken over are identified as critical management traffic. Non-critical bulk data transmission, regular file exchange or application data with low real-time requirements from both subnets are classified as regular task data.

[0088] After the traffic classification is completed, the network controller and switches will work together to perform the quality of service priority configuration. When the network controller generates or forwards data frames, it will write the corresponding priority label in the service type or priority field in the fibre channel frame header according to the classification result. For data frames identified as critical management traffic, the label is the highest priority; for regular task data, the label is the standard priority. Then, the switches carrying these data streams, especially the switches of the second FC-AE-1553 subnet and the switches of the first FC-AE-1553 subnet, will enable the service level-based priority scheduling mechanism on their ports. The switch hardware will detect the priority label of the inbound data frame and put it into the output queue of the corresponding priority. When network congestion occurs, the scheduling algorithm of the switch will ensure that the critical management traffic queue labeled as the highest priority is scheduled and forwarded first, and the regular task data queue is processed thereafter. This complete mechanism from traffic identification, frame labeling to queue scheduling ensures that during the cross-network takeover period, critical management instructions can be transmitted in a low-delay and high-reliability manner, thereby maintaining the basic control and stability of the entire network being taken over.

[0089] The critical management traffic refers to a series of communication data necessary for maintaining the basic control function of the subnet being taken over during the cross-network takeover process. This type of traffic usually has the characteristics of small data volume, short interval period, but high requirements for transmission timeliness and reliability, and specifically includes heartbeat messages for continuously monitoring the survival status of network terminals, response messages for confirming whether control instructions are correctly received and executed, reconfiguration instructions for emergency situations, and state synchronization data for maintaining basic management functions. Smooth transmission of these data is directly related to the effectiveness and stability of control during fault recovery.

[0090] The regular task data refers to application layer business data generated by each network terminal during normal network operation to perform its intended function. This type of data usually constitutes the main part of network load, and its characteristics are that the data volume may be large, but the sensitivity to transmission delay and jitter is relatively low, and it can tolerate a certain degree of queuing and waiting and bandwidth fluctuation. Specifically, it can include batch record data collected from sensors, log files for executing non-real-time tasks, pre-loaded task parameter packages, and non-critical periodic telemetry data, etc. During resource shortage, the transmission of this type of data can be delayed to ensure the immediacy of critical management traffic.

[0091] Through another embodiment, a collaborative management method of a multi-domain FC-AE-1553 network of the application is explained and described again.

[0092] For the complex system of multi-domain FC-AE-1553 network composed of multiple FC-AE-1553 subnets interconnected through switches, the application provides a collaborative management method of multi-domain FC-AE-1553 network, the core of which is to propose a complete collaborative management scheme between multi-domain FC-AE-1553 networks. The scheme specifically covers the establishment of the interconnection architecture of multi-domain FC-AE-1553 network, the network configuration strategy of cross-network collaborative management, the complete process of network controller taking over network terminals in fault subnets across networks and exiting the takeover after fault recovery. By constructing a physical basis based on dedicated optical interconnection, implementing network configuration with global addressing and logical security partitioning as the core, and defining clear operation sequences of fault monitoring, confirmation, configuration switching, service takeover and state recovery, the scheme realizes the cross-domain sharing and mutual backup of network controller resources of each FC-AE-1553 subnet. This method effectively overcomes the limitations of low resource utilization and inability to cope with cross-network faults of traditional independent redundancy scheme, thereby achieving the comprehensive goal of low cost, high resource utilization and high reliability at the system level. Specifically:

[0093] (1) Establishment of the interconnection architecture of multi-domain FC-AE-1553 network:

[0094] In the multi-domain FC-AE-1553 network, each FC-AE-1553 subnet is a standard and functionally complete FC-AE-1553 network, and all network components of FC-AE-1553 subnets are the same, including network controllers, network terminals and switches in each network. Each independent FC-AE-1553 subnet is interconnected through dedicated cross-network optical fibers between its switches, thereby realizing the physical cross-connection of multiple FC-AE-1553 subnets. The switches of each FC-AE-1553 subnet identify and forward cross-network communication data as needed according to the configured strategy, providing underlying communication support for cross-network collaborative management. For example, Figure 3As shown, three independent FC-AE-1553 subnets are shown, respectively identified as FC subnet 1, FC subnet 2 and FC subnet 3, each FC-AE-1553 subnet internally contains a network controller as a control core, a plurality of network terminals as a business execution unit and a switch as a communication hub, all network controllers and network terminals in the subnet are connected to the switch in the subnet through fiber link, and the key to cross-subnet interconnection lies in the interconnection between the switches of each subnet through dedicated cross-network fiber links, these interconnection links connect the switches of FC subnet 1, FC subnet 2 and FC subnet 3 together to form a unified physical network infrastructure, which ensures that each FC-AE-1553 subnet can run independently under the default logical isolation strategy, and at the same time provides a stable and reliable data transmission channel for the network controller to take over the network terminal business of the fault subnet across the network when collaborative management is needed.

[0095] The multi-domain FC-AE-1553 network is physically connected through the dedicated cross-network fiber interconnection links between the switches of each FC-AE-1553 subnet, but needs to be kept isolated in design logic, each FC-AE-1553 subnet maintains its inherent independence and certainty through the logical isolation and security partition strategy implemented on its switch during routine operation, and only in specific demand scenarios such as fault takeover or global task scheduling, controlled cross-network communication is performed through authorized configuration operations. The dedicated interconnection links between the switches used to cascade each FC-AE-1553 subnet in the multi-domain FC-AE-1553 network must have sufficient bandwidth and deterministic low delay characteristics to meet the real-time requirements of fault takeover instructions and other critical management information during cross-network transmission. The interconnection architecture of the multi-domain FC-AE-1553 network has good scalability and can support flexible increase in the number of FC-AE-1553 subnets, adding a FC-AE-1553 subnet only needs to connect its switch to the existing interconnection architecture through dedicated cross-network fiber, without changing the core interconnection and collaborative management principles such as network controller cross-network redundancy backup and takeover, switch routing based on domain identification and dynamic reconfiguration capabilities.

[0096] (2) Cross-network collaborative management network configuration:

[0097] To realize the network controller's cross-network fault takeover in the multi-domain FC-AE-1553 network, a complete set of logical management strategy is needed to realize network configuration on the basis of the special cross-network fiber interconnection of the switches in each FC-AE-1553 subnet. The core idea of the design of the strategy is default isolation and on-demand connectivity. Specifically, in the default state, strict logical isolation and security partitioning strategy is configured on the switches in each FC-AE-1553 subnet to ensure that each subnet runs independently and prohibits any cross-subnet communication; when it is confirmed that fault takeover or global task scheduling is needed, the communication whitelist of the network controller and the communication strategy of the related switches are dynamically adjusted through authorized configuration operation to temporarily and controllably open the cross-network communication path, thereby realizing the network controller's takeover of the network terminal service in the fault subnet, which specifically includes:

[0098] 1) Logical isolation and security partitioning strategy:

[0099] ① Default configuration (isolated state): In the configuration of the switches in each FC-AE-1553 subnet, strict security partitioning strategy needs to be established and implemented. Each independent FC-AE-1553 subnet is logically divided into its own exclusive partition, and the partition rule ensures that the communication between the network controller and the network terminal in the subnet is not blocked, while strictly prohibiting any cross-FC-AE-1553 subnet communication. The network controller of each FC-AE-1553 subnet can freely communicate with all network terminals in the subnet through the switch of the subnet; any communication request that attempts to access a device in another FC-AE-1553 subnet from one FC-AE-1553 subnet, such as accessing a network terminal in subnet 2 from subnet 1, will be directly discarded by the switch of the source subnet according to the security partitioning strategy, thereby effectively preventing unauthorized cross-network access and potential broadcast storm, and ensuring the security boundary of each FC-AE-1553 subnet. The globally unique FC address of each FC-AE-1553 subnet's network controller and network terminal should be configured in its own exclusive partition planned by the switch of the subnet, and the communication whitelist configured internally by the network controller of each FC-AE-1553 subnet in the default state only contains the network terminal addresses in its own exclusive partition, and this set of configuration works together to ensure the determinism and real-time performance of the FC-AE-1553 subnet to which it belongs when running independently.

[0100] ②Synergic management configuration (connected state): under the condition of synergic management function enabled, the switch of the FC-AE-1553 subnet will receive the authorized instruction from the management system, and the cross-subnet communication request identified will be transmitted from the cross-network interconnection port to the other FC-AE-1553 subnet. When the switch of the FC-AE-1553 subnet does not receive the takeover authorization, only the point-to-point cross-network access communication request is allowed to pass, and the broadcast message is prohibited from passing through the cross-network interconnection port. When the switch of the FC-AE-1553 subnet receives the takeover authorization, the broadcast message can also be transmitted cross-network. When the network controller of the FC-AE-1553 subnet does not receive the takeover authorization, its communication white list only contains the network terminal addresses in the exclusive partition of the subnet. When the network controller of the FC-AE-1553 subnet receives the takeover authorization, its communication white list will increase the network terminal addresses in the exclusive partition of the takeover subnet in addition to the network terminal addresses in the exclusive partition of the subnet, so as to realize the network controller takeover of all network terminal services in the fault subnet cross-network and synergic management of the multi-domain FC-AE-1553 network. Both the switch and the network controller need to have the dynamic reconfiguration capability, which can enter the synergic management state to realize the takeover function according to the authorized instruction, and can also exit the synergic management state to restore the independent operation of the subnet after the fault is recovered.

[0101] 2) Global addressing scheme:

[0102] In order to ensure that the messages cross-network can be correctly routed, a set of global unified address planning scheme needs to be implemented for the multi-domain FC-AE-1553 network. The FC address of each network controller or network terminal node in the global network must be unique. The FC address in the fiber channel standard is a 24-bit address, which can be structuredly split into three core fields and given specific meanings in this scheme, and the three fields are domain identification, area identification and port identification, each identification field is represented by 8-bit, and the three fields are combined to form a 24-bit global address conforming to the FC standard and having clear hierarchical semantics, as shown in Figure 4

[0103] ​In the globally unified address planning scheme, domain identifier is assigned a specific code, for example, 00H is assigned to subnet 1, 01H is assigned to subnet 2, and 02H is assigned to subnet 3. Domain identifier is the highest bit and the most core component in FC address, which uniquely identifies the FC-AE-1553 subnet information of the node, and is also the key judgment identifier for the switch to first check and distinguish whether it is an intranet message or a cross-network message when making a routing decision. The area identifier can be flexibly defined according to the actual network topology and management requirements. For example, the address range of 00H to 0FH can be assigned to backbone network devices, and the address range of 10H to 1FH can be assigned to access network devices. The port identifier is usually associated with or directly mapped to the physical port number of the switch. According to the above division strategy of FC-AE-1553 subnet node address, the switch of each FC-AE-1553 subnet can correctly route the messages within the subnet according to the domain identifier field in the FC address. In the default configuration of the isolation state, once the switch identifies that the domain identifier of the data frame does not belong to the FC-AE-1553 subnet, it will directly discard it according to the security partitioning strategy. Table 1 illustrates the application of this addressing and naming method with specific examples.

[0104] Table 1:

[0105]

[0106] This hierarchical addressing scheme composed of domain identifier, area identifier, and port identifier, combined with the management mechanism of the switch making routing decisions based on domain identifier, constitutes the core foundation of the FC-AE-1553 network that can efficiently and reliably expand to a large-scale multi-domain system management architecture, and also provides the most basic and reliable global addressing and accurate routing guarantee for the scheme of network controller taking over the business of network terminals in the fault subnet across the network.

[0107] 3) Quality of Service (QoS, Quality of Service) configuration:

[0108] When the network controller takes over all network terminal nodes of the fault subnetwork across the network, the traffic volume uniformly scheduled by the network controller will increase. To ensure the real-time performance of the key management traffic during the takeover process, all traffic flowing through the network controller needs to be reclassified and configured with quality of service priority. On the basis of the original default traffic classification of the network, the traffic demand generated by the network terminals from the subnetwork being taken over needs to be specially identified and included. For example, the key short messages such as heartbeat information and state confirmation messages from the subnetwork being taken over must ensure the real-time performance of their transmission, and need to be marked as the highest priority; while the regular task data of the subnetwork being taken over has relatively low requirements for real-time performance, and can be marked as the standard priority. In conjunction with this, the priority scheduling mechanism based on the service level must be enabled and configured on the physical ports of the related switches, the priority marking of the data frame is detected, and the corresponding output queue is sent, to ensure that when the network is congested, the cross-domain management traffic of high priority can absolutely be scheduled and forwarded in priority to the regular task data of low priority.

[0109] (3) Cross-network communication data flow:

[0110] Taking the network controller of the FC subnetwork 1 that needs to send a message to the network terminal NTx_2 of the FC subnetwork 2 as an example, the specific data flow process is as follows: the network controller NC_1 encapsulates the generated service data in an FC frame, and sets the destination address of the FC frame to the globally unique FC address of the target network terminal NTx_2; then the network controller NC_1 sends the FC frame to the FC subnetwork switch SW_1 directly connected thereto; after the switch SW_1 receives the FC frame, it parses the domain identifier field in the destination FC address, finds that the domain identifier does not belong to the FC subnetwork 1, and then forwards the FC frame to the FC subnetwork 2 switch SW_2 interconnected thereto through the pre-configured cross-network routing port; after the FC frame is routed to the FC subnetwork 2 switch SW_2 where the target domain identifier is located via the interconnected link, the switch SW_2 further performs accurate routing lookup within the FC subnetwork 2 according to the area identifier and port identifier contained in the internal destination address of the FC frame, and finally accurately sends the FC frame to the target network terminal NTx_2. After the target network terminal NTx_2 successfully receives the FC frame, its reply message will follow the reverse path back to the network controller NC_1 that initiates the request. Figure 5 This complete process is depicted, Figure 5The figure shows the network controller NC_1 in the left FC subnet 1 as the initiator of the communication, the FC frame generated by it is forwarded through the switch SW_1 of the FC subnet, the switch recognizes the destination address as a cross-FC-subnet address and forwards the FC frame through the cross-network interlink to the switch SW_2 of the right FC subnet 2, the switch SW_2 finally delivers the frame to the target network terminal NTx_2, and the figure explicitly marks the arrow flow direction of the FC frame from NC_1 to SW_1, then to SW_2 and finally to NTx_2, and the reverse path of the response frame from NTx_2 through SW_2 and SW_1 back to NC_1, intuitively showing the bidirectional data flow of the cross-FC-subnet end-to-end communication.

[0111] (4) Takeover process of cross-network cooperative management:

[0112] Based on the above multi-domain FC-AE-1553 network interconnection architecture and technical solutions, the complete takeover and recovery process of cross-network cooperative management is as follows. First, a state monitoring step is performed. The running state of each independently running FC-AE-1553 subnet is monitored by continuously receiving and analyzing the key telemetry information such as heartbeat periodically transmitted by the network controller of each FC-AE-1553 subnet. Then, a fault confirmation step is performed. When the ground monitoring system comprehensively judges and confirms that the network controller of a certain FC-AE-1553 subnet has failed and the network service managed by the network controller has been interrupted based on the received key telemetry information. A network configuration switching step is started. The ground system sends an uplink instruction to the network controller of the faulty network to power off the network controller, and simultaneously sends an uplink instruction to the switch of the faulty network to authorize the switch to enable the cross-network takeover function. After being authorized, the switch of the faulty network enables its cross-network interconnection port and configures the cross-network data transmission and broadcast messages required for takeover to be executed at the same time. Meanwhile, the ground system sends an uplink instruction to the network controller of the healthy network that is planned to execute the takeover to authorize the network controller to switch the communication white list, so that the communication white list of the network controller includes the addresses of all network terminals in the fault subnet in addition to the addresses of the network terminals in the subnet managed by the network controller. The ground system also sends an uplink instruction to the switch of the healthy network to authorize the switch to enable the cross-network interconnection port and the takeover configuration, and to allow broadcast messages to be transmitted across networks. Then, a service takeover step is entered. After the communication white list is switched, the network controller of the takeover can establish communication with all network terminals in the faulty subnet through the cross-network path formed by the switch of the healthy subnet and the switch of the faulty subnet, and can ensure high-priority transmission of critical management traffic according to the pre-set quality of service policy. Finally, when the faulty network controller is repaired, a state recovery step is performed. The ground system sends an uplink instruction to the network controller of the takeover to exit the takeover mode, switches the communication white list of the network controller back to the default configuration that only includes the addresses of the network terminals in the subnet managed by the network controller, and instructs the switches of the faulty subnet and the takeover subnet to recover to the default configuration that prohibits cross-subnet communication. After the faulty network controller is powered on, the faulty network controller is reinitialized and returns to the normal working mode, and the faulty network controller returns to its role as the network controller of the subnet and as a potential backup node of other subnets in the system, thereby completing the management cycle of the entire cross-network fault takeover and recovery.

[0113] In another implementation, a dedicated backup network controller is configured for each FC-AE-1553 subnet. When the primary network controller of the subnet fails, the dedicated backup network controller configured in the subnet immediately takes over the control function. In this scheme, the backup network controller of each subnet is idle for a long time during the normal operation of the primary network controller, resulting in waste of hardware resources. This scheme can only cope with the failure of a single network controller and cannot effectively cope with the overall failure of the subnet level or the extreme scenario of the failure of the primary and backup network controllers. The reliability of the system has not been fundamentally improved. At the same time, the backup network controller resources of each subnet cannot be shared and coordinated across subnets, and lack the ability to optimize the global resource configuration.

[0114] In another implementation, a separate and powerful global backup network controller is provided. When the network controller of any FC-AE-1553 subnet fails, the centralized global backup network controller takes over. The global backup network controller itself is a separate physical node and also has a single point of failure risk. If the central node fails, the redundancy backup function of the entire multi-domain FC-AE-1553 network will be completely disabled, which introduces a new critical vulnerability in the architecture. The dedicated global backup network controller resource in this scheme also increases the hardware cost, and to achieve its connection and control with all subnets makes the system architecture of the entire multi-domain FC-AE-1553 network more complex.

[0115] In the traditional scheme, each FC-AE-1553 subnet needs to be independently configured with a master and a backup or even multiple sets of network controllers, resulting in long-term idle of backup resources, causing huge hardware cost and waste of space resources. With the increase of complexity, when the single FC-AE-1553 network develops into a multi-domain FC-AE-1553 network interconnected by multiple FC-AE-1553 subnets, the application innovatively adopts a "one backup for multiple" resource sharing mode, so that the network controller resources of each FC-AE-1553 subnet can provide backup capabilities for other FC-AE-1553 subnets, thereby reducing the hardware quantity of redundant network controllers. This directly reduces the overall cost, weight and power consumption of the multi-domain FC-AE-1553 network, realizing the unification of resource optimization configuration and cost control. At the same time, this scheme breaks through the limitations of traditional single network internal redundancy, realizes cross-FC-AE-1553 subnet fault tolerance backup, and when the network controller of a certain FC-AE-1553 subnet fails, it can quickly be taken over by the network controller of other healthy FC-AE-1553 subnet, thereby avoiding the serious consequences of communication service interruption of the entire subnet caused by single node failure. The architecture design of the application is independent of the number of FC-AE-1553 subnets, and the addition of a FC-AE-1553 subnet only needs to be interconnected and accessed to the existing architecture through a switch, without the need to change the hardware connection of the existing FC-AE-1553 subnet, and has good scalability and deployment flexibility. Finally, the technical scheme of the application essentially improves the task continuity and survivability of a complex large system composed of multiple FC-AE-1553 networks, and is especially suitable for the fields of aviation, aerospace, military industry and the like which have extremely high reliability requirements. Through the innovative architecture of distributed, cross-network and resource sharing, the application successfully avoids the shortcomings of resource waste, reliability defects and high implementation complexity, and improves the overall performance, providing a relatively optimal technical path.

[0116] In the above embodiments, although the steps are numbered, the execution order of the steps can be adjusted according to the actual situation by those skilled in the art, and this is also within the protection scope of the application. It can be understood that in some embodiments, some or all of the above embodiments can be included.

[0117] As Figure 6As shown, the cooperative management system 200 of the multi-domain FC-AE-1553 network according to the embodiment of the present application comprises a configuration implementation module 201, a monitoring and fault judgment module 202, an authorization configuration module 203 and a recovery execution module 204.

[0118] The configuration implementation module 201 is configured to configure an address for each network controller and each network terminal respectively, and implement a security zoning policy on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet runs independently in a default state and cross-subnet communication is prohibited.

[0119] The monitoring and fault judgment module 202 is configured to monitor the running state of the network controller of each FC-AE-1553 subnet and perform fault judgment.

[0120] The authorization configuration module 203 is configured to, when the network controller of the first FC-AE-1553 subnet is confirmed to have a fault, perform an authorization configuration operation to allow the switch of the first FC-AE-1553 subnet to allow cross-subnet communication, and allow the second FC-AE-1553 subnet to take over the service of the network terminal of the first FC-AE-1553 subnet.

[0121] The recovery execution module 204 is configured to, when the network controller of the first FC-AE-1553 subnet recovers, perform a recovery operation to restore the management authority of the network controller of the second FC-AE-1553 subnet and the communication policy of the related switch to the default state.

[0122] The first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in the multi-domain FC-AE-1553 network.

[0123] Optionally, in the above technical solution, the configuration implementation module 201 is further configured to assign a globally unique 24-bit FC address to each network controller and each network terminal, and the 24-bit FC address comprises a domain identifier, a region identifier and a port identifier, wherein the domain identifier is used to uniquely identify the FC-AE-1553 subnet to which the network controller and the network terminal belong.

[0124] Optionally, in the above technical solution, the priority configuration module is further configured to: classify and configure the quality of service priority for the service traffic scheduled by the network controller of the second FC-AE-1553 subnet, and configure a forwarding priority higher than that of the regular task data for the critical management traffic from the network terminal of the first FC-AE-1553 subnet.

[0125] Optionally, in the above technical solution, the monitoring and fault judgment module 202 is specifically configured to: monitor the running state of the network controller of each FC-AE-1553 subnet and perform fault judgment through the heartbeat telemetry information.

[0126] It should be noted that the beneficial effects of the multi-domain FC-AE-1553 network cooperative management system 200 provided by the above embodiments are the same as those of the multi-domain FC-AE-1553 network cooperative management method, which will not be repeated here. In addition, when the system realizes its functions, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to the needs, that is, the system is divided into different functional modules according to the actual situation to complete all or part of the above described functions. In addition, the system and method embodiments provided by the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0127] An electronic device of an embodiment of the present application includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements any one of the above multi-domain FC-AE-1553 network cooperative management methods when executing the computer program. The electronic device can also be a terminal device, which can be any device that can install an application, including at least one of a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a smart television, and a smart vehicle device.

[0128] A computer readable storage medium of an embodiment of the present application, the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement any one of the above multi-domain FC-AE-1553 network cooperative management methods.

[0129] It should be understood that the flow diagrams and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of various embodiments of the present application. In this regard, each block in the flow diagrams and block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each of the blocks of the block diagrams and / or flowchart illustrations, and combinations thereof, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or combinations of hardware and software.

[0130] The above description is only preferred embodiments of the present application and the technical principles used. Those skilled in the art should understand that the disclosed range of the present application is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or equivalent features without departing from the disclosed concept. For example, the above features are replaced with the technical features disclosed in the present application (but not limited to) having similar functions to form technical solutions.

[0131] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and represent a specific order or sequence. The order of use of similar objects can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described.

[0132] Although the embodiments of the present application have been shown and described above, it should be understood that the above embodiments are exemplary and should not be construed as limiting the present application, and those skilled in the art can make changes, modifications, replacements and variations to the above embodiments within the scope of the present application.

Claims

1. A collaborative management method for a multi-domain FC-AE-1553 network, characterized in that, A multi-domain FC-AE-1553 network comprises multiple FC-AE-1553 subnets interconnected by switches. Each FC-AE-1553 subnet includes a network controller, network terminals, and switches. The method includes: Configure addresses for each network controller and each network terminal separately, and implement a security partitioning policy on the switch of each FC-AE-1553 subnet so that each FC-AE-1553 subnet can operate independently by default and cross-subnet communication is prohibited. Monitor the operating status of the network controller of each FC-AE-1553 subnet and perform fault diagnosis; When the network controller of the first FC-AE-1553 subnet is confirmed to have failed, an authorized configuration operation is performed to enable the switches of the first FC-AE-1553 subnet to allow cross-subnet communication, and to enable the second FC-AE-1553 subnet to take over the services of the network terminals of the first FC-AE-1553 subnet. After the network controller of the first FC-AE-1553 subnet is restored, a restoration operation is performed to restore the management permissions of the network controller of the second FC-AE-1553 subnet and the communication policies of the relevant switches to the default state. Wherein, the first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in the multi-domain FC-AE-1553 network; Configure addresses for each network controller and each network terminal separately, including: Each network controller and each network terminal are assigned a globally unique 24-bit FC address. The 24-bit FC address includes a domain identifier, a region identifier, and a port identifier. The domain identifier is used to uniquely identify the FC-AE-1553 subnet to which the network controller and network terminal belong. When the network controller of the first FC-AE-1553 subnet is confirmed to have failed, a specific authorization configuration command is generated and sent upstream. This authorization configuration command is distributed via a dedicated control channel to the switches of the first FC-AE-1553 subnet and the network controller of the second FC-AE-1553 subnet. The switches of the first FC-AE-1553 subnet perform a configuration switching operation, dynamically adjusting their security partitioning policy, and sending commands to or from other FC-AE-1553 subnets with the destination being the first FC-AE-1553 subnet. Data frames from network terminals within the C-AE-1553 subnet are allowed to be transmitted through the corresponding interconnection ports; the switches of the second FC-AE-1553 subnet adjust their security partitioning policies, modify the access control rules of the ports, allow communication data from the first FC-AE-1553 subnet to pass through, configure cross-network transmission permissions for broadcast messages according to instructions, the switches of the second FC-AE-1553 subnet also update their routing tables, and the network controller of the second FC-AE-1553 subnet updates its communication management policies and dynamically switches its communication whitelist.

2. The collaborative management method for a multi-domain FC-AE-1553 network according to claim 1, characterized in that, Also includes: The service traffic scheduled by the network controller of the second FC-AE-1553 subnet is classified and service quality priority is configured. The critical management traffic from the network terminals of the first FC-AE-1553 subnet that is being taken over is configured with a higher forwarding priority than regular task data.

3. A collaborative management method for a multi-domain FC-AE-1553 network according to claim 1 or 2, characterized in that, Monitor the operating status of the network controller of each FC-AE-1553 subnet and perform fault diagnosis, including: The operating status of the network controller of each FC-AE-1553 subnet is monitored and fault diagnosis is performed using heartbeat telemetry information.

4. A collaborative management system for a multi-domain FC-AE-1553 network, characterized in that, The multi-domain FC-AE-1553 network includes multiple FC-AE-1553 subnets interconnected by switches. Each FC-AE-1553 subnet contains a network controller, network terminals, and switches. The system includes a configuration implementation module, a monitoring and fault diagnosis module, an authorization configuration module, and an execution recovery module. The configuration implementation module is used to: configure addresses for each network controller and each network terminal respectively, and implement a security partitioning policy on the switch of each FC-AE-1553 subnet, so that each FC-AE-1553 subnet can operate independently by default and cross-subnet communication is prohibited; The monitoring and fault judgment module is used to: monitor the operating status of the network controller of each FC-AE-1553 subnet and perform fault judgment; The authorization configuration module is used to: when the network controller of the first FC-AE-1553 subnet is confirmed to have failed, through authorization configuration operation, enable the switch of the first FC-AE-1553 subnet to allow cross-subnet communication, and enable the second FC-AE-1553 subnet to take over the services of the network terminals of the first FC-AE-1553 subnet; The execution recovery module is used to: when the network controller of the first FC-AE-1553 subnet recovers, perform a recovery operation to restore the management authority of the network controller of the second FC-AE-1553 subnet and the communication policy of the relevant switches to the default state; Wherein, the first FC-AE-1553 subnet and the second FC-AE-1553 subnet are two different FC-AE-1553 subnets in the multi-domain FC-AE-1553 network; The configuration implementation module is further specifically used to: allocate a globally unique 24-bit FC address to each network controller and each network terminal, wherein the 24-bit FC address includes a domain identifier, a region identifier, and a port identifier, wherein the domain identifier is used to uniquely identify the FC-AE-1553 subnet to which the network controller and network terminal belong; When the network controller of the first FC-AE-1553 subnet is confirmed to have failed, a specific authorization configuration command is generated and sent upstream. This authorization configuration command is distributed via a dedicated control channel to the switches of the first FC-AE-1553 subnet and the network controller of the second FC-AE-1553 subnet. The switches of the first FC-AE-1553 subnet perform a configuration switching operation, dynamically adjusting their security partitioning policy, and sending commands to or from other FC-AE-1553 subnets with the destination being the first FC-AE-1553 subnet. Data frames from network terminals within the C-AE-1553 subnet are allowed to be transmitted through the corresponding interconnection ports; the switches of the second FC-AE-1553 subnet adjust their security partitioning policies, modify the access control rules of the ports, allow communication data from the first FC-AE-1553 subnet to pass through, configure cross-network transmission permissions for broadcast messages according to instructions, the switches of the second FC-AE-1553 subnet also update their routing tables, and the network controller of the second FC-AE-1553 subnet updates its communication management policies and dynamically switches its communication whitelist.

5. The collaborative management system for a multi-domain FC-AE-1553 network according to claim 4, characterized in that, It also includes a priority configuration module, which is used to: classify and configure quality of service priorities for service traffic scheduled by the network controller of the second FC-AE-1553 subnet, and configure a higher forwarding priority for critical management traffic from network terminals of the first FC-AE-1553 subnet that has been taken over than for regular task data.

6. A collaborative management system for a multi-domain FC-AE-1553 network according to claim 4 or 5, characterized in that, The monitoring and fault judgment module is specifically used to: monitor the operating status of the network controller of each FC-AE-1553 subnet through heartbeat telemetry information and make fault judgments.

7. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the collaborative management method for a multi-domain FC-AE-1553 network as described in any one of claims 1 to 3.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements a collaborative management method for a multi-domain FC-AE-1553 network as described in any one of claims 1 to 3.

Images