A software reconstruction method based on static configuration of FC optical fiber network

Abstract

The application belongs to airborne software fault tolerance technology, and particularly relates to a software reconstruction method based on FC optical fiber network static configuration, which comprises the following steps: FC optical fiber network is established through switches to realize interconnection and intercommunication of all nodes of a system, wherein the F port of the physical connection switch and the N port of the node are set with the same value; all nodes of the system load static configuration information, confirm network roles and run an initial network operation scheme; all communication nodes monitor faults in real time and report fault information to a network management node; after receiving the fault information, the network management node matches a new scheme number according to a preset network operation scheme table and sends the scheme number to the switch; the switch switches the mapping relationship between the logical port and the physical port according to the scheme number; and all communication nodes start the software function of the fault node on the reconstruction node according to the new scheme number.

Description

Technical Field

[0001] This application pertains to airborne software fault tolerance technology, and specifically relates to a software reconfiguration method based on static configuration of FC fiber optic networks. Background Technology

[0002] In avionics systems, the integrated processor, as the core computer processing platform for avionics system control and management, possesses high-speed information processing and data computation capabilities. The integrated processor mainly consists of multiple data processing nodes interconnected via an FC bus, providing a high-speed switching network for various application software. As the computer system responsible for handling various avionics tasks on the aircraft, the integrated processor plays the role of the information hub, influencing flight safety, management, and control; therefore, any failure can have serious consequences. With increasing mission complexity and safety standards, traditional fault-tolerant technologies face challenges, prompting the development of emerging technologies to address these complex requirements. Traditional methods for handling node failures include analyzing and verifying system behavior through mathematical models during the system design phase to improve system correctness and reduce potential failure points and the probability of failure. However, these methods are complex and costly to implement and cannot dynamically adjust in the event of component failure. Hardware redundancy involves equipping each node with an identical backup node, allowing restarting on the backup node after a communication node failure. However, too many backup nodes increase system weight and cost and are not effective enough for software error control. Virtualization and isolation technologies allow different tasks to be isolated on the same hardware, which helps with resource optimization and fault isolation. However, virtualization may introduce additional overhead and affect real-time performance, especially in emergency situations where real-time response is not possible. Summary of the Invention

[0003] To address the aforementioned issues, this application provides a software reconfiguration method based on static configuration of an FC fiber optic network, comprising the following steps:

[0004] An FC fiber optic network is constructed using switches to achieve interconnection between nodes in the system. The F port of the physically connected switch and the N port of the node are set to the same value.

[0005] Each node in the system loads static configuration information, confirms network roles, and runs the initial network operation plan.

[0006] Each communication node monitors its own faults in real time and reports fault information to the network management node;

[0007] After receiving the fault information, the network management node matches a new scheme number according to the preset network operation scheme table and sends the scheme number to the switch.

[0008] The switch switches the mapping relationship between logical ports and physical ports based on the scheme number;

[0009] Each communication node activates the software functions of the faulty node on the reconstructed node according to the new scheme number.

[0010] Preferably, the N port includes multiple nodes, including: a network management node, communication node 1, communication node 2, reconfiguration node 1, communication node 3, communication node 4, communication node 5, and reconfiguration node 2.

[0011] Preferably, the software runs on the communication node. When the communication node fails, it runs on the reconstruction node. The switch's F port and the node's N port are connected one by one, and the physically connected N port number and F port number are set to the same value.

[0012] Preferably, the software refactoring steps specifically include:

[0013] When a single communication node fails, a reconstruction node is selected based on the location of the failed node:

[0014] If the faulty node is a network management node, communication node 1, or communication node 2, then reconstructing node 2 should be used first.

[0015] If the faulty node is communication node 3, communication node 4 or communication node 5, then reconstructed node 1 shall be used first.

[0016] When two nodes fail, the remaining free space is used to reconstruct the nodes;

[0017] When three or more nodes fail, the reconstruction is terminated.

[0018] Preferably, the activation of the reconstruction node requires the fulfillment of an idle state condition: if the priority reconstruction node is occupied, another idle reconstruction node is activated; if both are occupied, no reconstruction is performed.

[0019] Preferably, when the switch switches port mapping, it selects the corresponding physical port to send data based on the destination port number in the frame.

[0020] Preferably, fault monitoring is achieved through the operating system health monitoring mechanism, including: hardware fault reports, application software health status, and middleware self-test results.

[0021] Preferably, the software refactoring process specifically includes the following steps:

[0022] After receiving the fault information, the network management node selects the target reconstruction node according to the fault node type and the preset reconstruction rules, and matches the corresponding new network operation scheme number;

[0023] Send the new network operation scheme number to the switch;

[0024] The switch looks up the corresponding logical port and physical port mapping relationship in the preset port mapping table based on the received scheme number;

[0025] The switch switches the current port mapping relationship to the found mapping relationship, so that messages sent to the logical port of the faulty node are forwarded to the physical port of the target reconstruction node;

[0026] Each communication node receives the new scheme number, and the target reconstruction node starts the software functions of the faulty node according to the scheme number.

[0027] This application can effectively solve the problems of traditional airborne software fault tolerance technology, such as the inability to dynamically adjust faulty components, high system weight and cost, and poor real-time performance, thereby improving the reliability and availability of the system. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the FC fiber optic network connection before reconstruction.

[0029] Figure 2 This is a schematic diagram of the reconstructed FC fiber optic network connection. Detailed Implementation

[0030] To make the technical solution and advantages of this application clearer, the technical solution of this application will be described in a clearer and more complete manner below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only some embodiments of this application, and are only used to explain this application, not to limit this application. It should be noted that, for ease of description, only the parts related to this application are shown in the accompanying drawings. Other related parts can be referred to the general design. In the absence of conflict, the embodiments and technical features in the embodiments of this application can be combined with each other to obtain new embodiments.

[0031] In avionics systems, traditional methods for handling node failures include analyzing and verifying system behavior through mathematical models during the system design phase to reduce the probability of failure, as well as hardware redundancy, virtualization, and isolation technologies. However, these methods suffer from drawbacks such as the inability to dynamically adjust faulty components, high system weight and cost, and poor real-time performance. To address these issues, this invention proposes a software reconfiguration method based on static configuration of an FC fiber optic network. Multiple data processing nodes of the integrated processor are interconnected via switches and an FC fiber optic bus. The FC fiber optic network initializes static configuration information and executes an initial network operation plan. Each communication node collects its own fault information in real time and reports it to the network management node. The network management node finds the corresponding reconfiguration network operation plan based on the fault situation and publishes it to all nodes in the network. The software functions of the faulty node are promptly restarted on the reconfiguration node, ensuring the normal operation of the system. This method can dynamically adjust the network operation plan according to different fault situations. Based on static configuration, it reduces the time for switching reconfiguration plans and improves real-time performance. Compared to a solution that requires a backup node for each node, this method only requires two reconfiguration nodes, reducing system weight and cost.

[0032] The software reconfiguration method based on static configuration of FC fiber optic network requires the support of network operation scheme table and port mapping table.

[0033] Network Operation Plan Table: Records the network operation plan number and the software deployment relationship information corresponding to each plan.

[0034] Port mapping table: Records the mapping relationship between logical ports and physical ports of the switch according to the network operation scheme number.

[0035] Taking the integrated processor of an avionics system as an example (this can be extrapolated to other application scenarios), the operating scheme is as follows:

[0036] 1. FC Fiber Optic Network Setup

[0037] The integrated processor consists of multiple data processing nodes, including a network management node, a communication node, and two reconfiguration nodes. The software runs normally on the communication node; if the communication node fails, it runs on the reconfiguration node. Each node is connected to the switch via fiber optic cable for information exchange. The FC fiber optic network connection scheme is as follows: Figure 1 As shown. Connect the switch's F port to the node's N port one by one, and set the physically connected N port number and F port number to the same value.

[0038] Two roles are configured on the integrated processor: Network Manager (Network Management Node) and Network Remote Terminal (Communication Node) to perform FC network management functions. The Network Management Node is responsible for centralized control and management of network operation status, centralized control of network access status, and periodic publication. The Communication Nodes are the various terminal nodes in the network, responsible for the network management of their local nodes. The node with system management functions in the integrated processor is selected as the Network Management Node, and all other nodes are Communication Nodes. The node role information is recorded in the FC fiber optic network static configuration information.

[0039] The switch maintains its own port mapping table (see Table 1) and network operation scheme (see Table 2; the table provides an example to illustrate the software refactoring process, and adjustments can be made based on different situations in actual applications). The port mapping table records the mapping relationship between the logical port number and the physical F port number for each scheme, and the network operation scheme records the relationship between the scheme number and the software operation deployment. All network operation schemes under software refactoring and normal conditions are coded with a "scheme number," where scheme number 1 is the network operation scheme under the initial default normal operation condition, and the other schemes are the refactored operation schemes.

[0040] The format of the transmitted frames is shown in Table 3. The switch can determine which port F to send the message to port N through based on the destination port number (logical port number) in the frame. The format of the received frames is shown in Table 4. Each node can determine which node the message came from based on the source port number (logical port number) in the frame.

[0041] 2. FC Fiber Optic Network Initialization

[0042] After the FC fiber optic network is established, the network management node and communication node perform initialization. First, static configuration data is loaded, the FC fiber optic network static configuration information assigned to the current module is obtained and parsed, the assigned role of the current node is confirmed as either a network management node or a communication node, and then a virtual interrupt callback function is set to receive faults reported through the operating system's health monitoring mechanism. The initialization of the network management node and communication node is then complete.

[0043] 3. Nodes apply for network access and execute the initial network operation plan.

[0044] After initialization, the communication node monitors its own network status. If the node is not on the network, it requests internet access from the network management node. If the request fails, it will request it periodically until it succeeds.

[0045] The network management node sends the initial network operation plan number (Plan 1 in Table 1) to the switch. After receiving the network operation plan number from the network management node, the communication node executes the initial network operation plan and runs the corresponding software functions.

[0046] 4. Fault monitoring

[0047] The network management node and each communication node receive fault information reported by the operating system health monitoring, including fault reports collected through the callback mechanism provided by the operating system health monitoring, application software faults obtained from the health status of each application software, and self-test results obtained by calling the middleware interface.

[0048] After collecting fault information, the communication node reports the fault to the network management node.

[0049] 5. Software Refactoring

[0050] After receiving fault information from a communication node or detecting its own fault information, the network management node performs software refactoring, enabling the software of the faulty node to start running on refactoring node 1 or refactoring node 2. The refactoring principles are as follows:

[0051] a) When only one node fails, if the failed node is the network management node, communication node 1 or communication node 2, use reconstructed node 2 for reconstruction; if the failed node is communication node 3, communication node 4 or communication node 5, use reconstructed node 1 for reconstruction.

[0052] b) When a second node fails, the remaining reconstructed nodes are used for reconstruction;

[0053] c) When a third or more node fails, no further reconstruction will be performed.

[0054] The reconstruction process is as follows:

[0055] a) When the network management node detects a fault in the application or module of the network management node, communication node 1, or communication node 2:

[0056] 1) If the reconstructed node 2 is idle, start the application of the network management node, communication node 1, or communication node 2 on the reconstructed node 2;

[0057] 2) If reconstruction node 2 is occupied, check if reconstruction node 1 is idle. If reconstruction node 1 is idle, then use reconstruction node 1 for reconstruction. If reconstruction node 1 is already occupied, then do not perform reconstruction.

[0058] 3) The new network operation scheme number is sent to the switch. The switch switches the current port mapping table according to the reconstructed network operation scheme, and switches the mapping relationship between the destination port number (logical port number) in the frame and the physical port. After switching, the physical port number is selected to send data according to the destination port number in the frame.

[0059] b) If the network management node detects an application or module failure in communication node 3, communication node 4, or communication node 5:

[0060] 1) If reconstructing node 1 is idle, start the application of communication node 3, communication node 4 or communication node 5 on reconstructing node 1;

[0061] 2) If reconstruction node 1 is occupied, check if reconstruction node 2 is idle. If reconstruction node 2 is idle, then use reconstruction node 2 for reconstruction. If reconstruction node 2 is already occupied, then do not perform reconstruction.

[0062] 3) The new network operation scheme number is sent to the switch. The switch switches the current port mapping table according to the reconstructed network operation scheme, and switches the mapping relationship between the destination port number (logical port number) in the frame and the physical port. After switching, the physical port number is selected to send data according to the destination port number in the frame.

[0063] like Figure 2 As shown, taking the case where communication node 1 fails while all other nodes are functioning normally as an example, the reconstruction process is as follows:

[0064] a) If the reconstructed node 2 is idle, start the application of the communication node 1 on the reconstructed node 2;

[0065] b) The network management node sends network operation scheme 3 to the switch. The switch switches the mapping relationship between logical ports and physical ports according to the new scheme number. Port 8 contains two lines, a black line and an orange line. That is, messages sent to communication node 1 are sent through port 8, and messages sent to reconstructing node 2 are also sent through port 8.

[0066] The following is the table used in this example:

[0067] Table 1 Network Operation Scheme

[0068]

[0069]

[0070]

[0071] Table 2 Port Mapping Table

[0072]

[0073]

[0074]

[0075]

[0076]

[0077]

[0078]

[0079] Table 3 Transmitted Frame Format

[0080]

[0081]

[0082] Table 4 Received Frame Format

[0083] msg_name Message Name 8 bytes msg_id Send Message ID 8 bytes msg_max_len Maximum message length 8 bytes msg_type Message Type 8 bytes msg_src_id Message source port number 8 bytes

[0084] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A software reconfiguration method based on static configuration of FC optical fiber networks, characterized in that, Includes the following steps: An FC fiber optic network is constructed using switches to achieve interconnection between nodes in the system. The F port of the physically connected switch and the N port of the node are set to the same value. Each node in the system loads static configuration information, confirms network roles, and runs the initial network operation plan. Each communication node monitors its own faults in real time and reports fault information to the network management node; After receiving the fault information, the network management node matches a new scheme number according to the preset network operation scheme table and sends the scheme number to the switch. The switch switches the mapping relationship between logical ports and physical ports based on the scheme number; Each communication node activates the software functions of the faulty node on the reconstructing node according to the new scheme number; The specific steps of software refactoring include: When a single communication node fails, a reconstruction node is selected based on the location of the failed node: If the faulty node is a network management node, communication node 1, or communication node 2, then reconstructing node 2 should be used first. If the faulty node is communication node 3, communication node 4 or communication node 5, then reconstructed node 1 shall be used first. When two nodes fail, the remaining free space is used to reconstruct the nodes; When three or more nodes fail, the refactoring process is terminated. The activation of a reconstruction node requires meeting the idle state condition: if the priority reconstruction node is occupied, another idle reconstruction node is activated; if both are occupied, no reconstruction is performed. The software refactoring process specifically includes the following steps: After receiving the fault information, the network management node selects the target reconstruction node according to the fault node type and the preset reconstruction rules, and matches the corresponding new network operation scheme number; Send the new network operation scheme number to the switch; The switch looks up the corresponding logical port and physical port mapping relationship in the preset port mapping table based on the received scheme number; The switch switches the current port mapping relationship to the found mapping relationship, so that messages sent to the logical port of the faulty node are forwarded to the physical port of the target reconstruction node; Each communication node receives the new scheme number, and the target reconstruction node starts the software functions of the faulty node according to the scheme number.

2. The software reconfiguration method based on static configuration of FC optical fiber network as described in claim 1, characterized in that, The N port includes multiple nodes, including: network management node, communication node 1, communication node 2, reconfiguration node 1, communication node 3, communication node 4, communication node 5, and reconfiguration node 2.

3. The software reconfiguration method based on static configuration of FC optical fiber network as described in claim 2, characterized in that, The software runs on the communication node. When the communication node fails, it runs on the reconstruction node. The switch's F port and the node's N port are connected one by one, and the physically connected N port number and F port number are set to the same value.

4. The software reconfiguration method based on static configuration of FC optical fiber network as described in claim 1, characterized in that, When a switch switches port mappings, it selects the corresponding physical port to send data based on the destination port number in the frame.

5. The software reconfiguration method based on static configuration of FC optical fiber network as described in claim 1, characterized in that, Fault monitoring is achieved through the operating system health monitoring mechanism, including: hardware fault reports, application software health status, and middleware self-test results.

Images