Dual-margin device bus topology network architecture
By designing a double margin equipment bus topology network architecture, using a hot backup bus controller and extended bus bandwidth, the interruption problem and insufficient bandwidth of the 1553B bus network in the event of failure is solved, and a high reliability and high bandwidth bus network is achieved.
Patent Information
- Application Number
- CN202411802419.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-09
- Publication Date
- 2025-04-11
AI Technical Summary
The existing 1553B bus network cannot be hot backup when the bus controller fails, resulting in network interruption; at the same time, the bandwidth of a single network is not enough to meet the needs of large-scale data transmission.
A double-margin device bus topology network architecture is designed, using two bus controllers and corresponding main and backup buses, and the bus controller is realized through software, and the two BCs are managed uniformly through the upper-level equipment to expand the bus bandwidth.
It realizes high reliability and bandwidth expansion of the bus network, avoids network interruptions caused by bus controller failure, and improves system scalability.
Smart Images

Figure CN119814489A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of data transmission, and in particular, relates to a dual-redundancy device bus topology network architecture. Background Art
[0002] The 1553B bus is a bus technology with high reliability. At present, most airborne launchers use the 1553B bus as a channel for digital signal transmission. Therefore, aircraft use the 1553B bus network as the device bus. After years of engineering application, there are two obvious disadvantages. First, although the 1553B bus has high reliability, its dual redundant backup is only the bus transmission channel, and the bus controller has no hot backup. Once the bus controller fails, the entire launcher bus network cannot operate, and the launchers of the entire aircraft will not be able to be used normally. Second, the amount of data exchanged between the launcher and the aircraft is large, and the existing single network has only 1M bandwidth, which cannot meet the large amount of data transmission needs. The problem of insufficient bus bandwidth can only be solved by limiting the number of launchers used at the same time or extending the data binding time. Summary of the invention
[0003] In order to solve the above problems, the present application provides a dual-redundancy device bus topology network architecture, including:
[0004] A first part remote terminal, a second part remote terminal, a first bus controller, a second bus controller and a host computer;
[0005] The host computer is connected to the first bus controller via a first optical fiber, and is connected to the second bus controller via a second optical fiber;
[0006] The first bus controller is connected to the first part of remote terminals via the first main bus,
[0007] The first bus controller is connected to the second part of remote terminals via the first standby bus,
[0008] The second bus controller is connected to the first part of remote terminals via the second standby bus,
[0009] The second bus controller is connected to the second part of remote terminals via the second main bus;
[0010] In a non-fault state, the first bus controller establishes communication with the first part of the remote terminals via the first main bus; the second bus controller establishes communication with the second part of the remote terminals via the second main bus;
[0011] When the first optical fiber or the first bus controller fails, the second bus controller establishes communication with the second part of the remote terminals through the second main bus, and the second bus controller establishes communication with the first part of the remote terminals through the second standby bus;
[0012] When the second optical fiber or the second bus controller fails, the first bus controller establishes communication with the first part of remote terminals through the first main bus, and the first bus controller establishes communication with the second part of remote terminals through the first standby bus.
[0013] Preferably, the first part of remote terminals and the second part of remote terminals each include a plurality of remote terminals.
[0014] Preferably, when the first optical fiber or the first bus controller fails, the first bus controller sends a request for backup of the first bus controller to the second bus controller, and after the backup of the second bus controller is completed, the first bus controller stops working.
[0015] Preferably, when the second optical fiber or the second bus controller fails, the second bus controller sends a request for backup of the second bus controller to the first bus controller, and after the backup of the first bus controller is completed, the second bus controller stops working.
[0016] Preferably, both the first main bus and the second main bus are 1553B buses.
[0017] Preferably, the number of remote terminals in the first part and the number of remote terminals in the second part are the same.
[0018] The advantages of the present application include: compared with the existing engineered bus network, the present invention has obvious advantages in reliability and bandwidth expansion, which are specifically reflected in the following aspects:
[0019] 1) The existing 1553B bus network is a single bus controller, namely BC. Although the 1553B bus is a highly reliable bus technology with strong fault tolerance, once the bus controller fails, the entire network will not be able to operate. The present invention uses software to implement hot backup of the bus controller. The backup logic is complete and can effectively prevent the two bus controllers, namely BC, from grabbing power and BC from switching by mistake. The reliability of the bus network operation is greatly improved;
[0020] 2) The 1553B bus networks used in existing projects are all single networks with bandwidths that cannot exceed 1M and limited load capacity. When there is a lot of data to be transmitted on the bus, it can only be used in time-sharing according to the usage scenario. The present invention designs two 1553B bus topology networks to work simultaneously, and the upper-layer device manages the two BCs at the same time, and uniformly manages the working status of all remote terminals, i.e. RTs. For the upper-layer device, this is equivalent to doubling the bus bandwidth;
[0021] 3) The present invention has strong scalability. According to the needs of the project, the number of topological networks can be further expanded. To add a topological network, only one BC needs to be added in hardware and a set of bus cables needs to be designed. Multiple BCs can back up each other, increasing the reliability of the system. The upper layer device manages multiple BCs in a unified manner. While increasing the bandwidth, the number of controllable RT terminals also increases accordingly.
[0022] 4) The present invention is relatively easy to implement in engineering, and the core lies in the software development of the upper-layer equipment, which needs to ensure reliable switching between various BCs. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 This is a schematic diagram of a dual-redundancy device bus topology network architecture according to a preferred embodiment of the present application;
[0024] Figure 2 This is a flowchart of the processing of failure mode 1 of a preferred embodiment of the present application;
[0025] Figure 3 This is a flowchart of the processing of failure mode 2 of a preferred implementation mode of the present application;
[0026] Figure 4 This is a flowchart of fault mode 3 processing in a preferred implementation mode of the present application. DETAILED DESCRIPTION
[0027] In order to make the technical solution and advantages of the present application clearer, the technical solution of the present application will be further described in detail in detail and in detail in conjunction with the accompanying drawings. It can be understood that the specific embodiments described here are only partial embodiments of the present application, which are only used to explain the present application, not to limit the present application. It should be noted that, for the convenience of description, only the parts related to the present application are shown in the accompanying drawings, and other related parts can refer to the general design. In the absence of conflict, the embodiments in the present application and the technical features in the embodiments can be combined with each other to obtain new embodiments.
[0028] In order to solve the above problems, the present application provides a dual-redundancy device bus topology network architecture, including:
[0029] The first part of the remote terminal, the second part of the remote terminal, the first bus controller, the second bus controller and the host computer; Figure 1 As shown, the remote terminal is referred to as RT, the first part of the remote terminals includes RT1-RT5 as shown in the figure; the second part of the remote terminals includes RT6-RT10 as shown in the figure; the first bus controller is BC1, and the second bus controller is BC2;
[0030] The host computer is connected to the first bus controller via a first optical fiber, and is connected to the second bus controller via a second optical fiber;
[0031] The first bus controller is connected to the first part of remote terminals via the first main bus,
[0032] The first bus controller is connected to the second part of remote terminals via the first standby bus,
[0033] The second bus controller is connected to the first part of remote terminals via the second standby bus,
[0034] The second bus controller is connected to the second part of remote terminals via the second main bus;
[0035] In a non-fault state, the first bus controller establishes communication with the first part of the remote terminals via the first main bus; the second bus controller establishes communication with the second part of the remote terminals via the second main bus;
[0036] When the first optical fiber or the first bus controller fails, the second bus controller establishes communication with the second part of the remote terminals through the second main bus, and the second bus controller establishes communication with the first part of the remote terminals through the second standby bus;
[0037] When the second optical fiber or the second bus controller fails, the first bus controller establishes communication with the first part of remote terminals through the first main bus, and the first bus controller establishes communication with the second part of remote terminals through the first standby bus.
[0038] Based on the above design principles, three failure modes are sorted out. In each failure mode, the specific processing flow is as follows: Figure 2-Figure 4 .
[0039] Failure Mode 1:
[0040] a) The upper-layer device detects that the optical fiber communication of a certain BC hardware platform (hereinafter referred to as platform 1) is abnormal, and sends a request command to switch to the backup BC to another BC hardware platform (hereinafter referred to as platform 2);
[0041] b) Platform 2 receives the backup BC switching request command and continuously sends backup BC switching request messages to platform 1;
[0042] c) After receiving the request message for switching to the backup BC, platform 1 stops the BC function;
[0043] d) After the BC of platform 1 stops working through the BM function, platform 2 executes the BC switching function and takes over the bus data transmission control function of the faulty network;
[0044] e) Platform 2 reports to the upper-layer device that the backup BC switch is successful.
[0045] Failure Mode 2:
[0046] a) The upper-layer device detects a CPU module failure on a BC hardware platform (hereinafter referred to as platform 1) and sends a request command to switch to a backup BC to another BC hardware platform (hereinafter referred to as platform 2);
[0047] b) After receiving the request command to switch to the backup BC, platform 2 requests platform 1 to power off;
[0048] c) After the upper-layer device controls platform 1 to power off and platform 2 monitors that the BC of platform 1 stops working, it executes the BC switching function and takes over the bus data transmission control;
[0049] d) Platform 2 reports to the upper-layer device that the backup BC switch is successful.
[0050] Failure Mode 3:
[0051] a) A BC hardware platform (hereinafter referred to as platform 1) detects a 1553B module failure and reports it to the upper-layer device;
[0052] b) The upper layer device sends a 1553B module stop working instruction to platform 1, and sends a switch backup BC request command to another BC hardware platform (hereinafter referred to as platform 2);
[0053] c) Platform 1 receives the command from the upper layer device and stops the 1553B module from working;
[0054] d) Platform 2 receives the request command to switch to the backup BC, confirms the abnormality of the device bus through the backup BC, executes the BC switching function, and takes over the bus data transmission control;
[0055] e) Platform 2 reports to the upper-layer device that the backup BC switch is successful.
[0056] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A dual-redundancy device bus topology network architecture, characterized in that: include: A first part remote terminal, a second part remote terminal, a first bus controller, a second bus controller and a host computer; The host computer is connected to the first bus controller via a first optical fiber, and is connected to the second bus controller via a second optical fiber; The first bus controller is connected to the first part of remote terminals via the first main bus, The first bus controller is connected to the second part of remote terminals via the first standby bus, The second bus controller is connected to the first part of remote terminals via the second standby bus, The second bus controller is connected to the second part of remote terminals via the second main bus; In a non-fault state, the first bus controller establishes communication with the first part of remote terminals via the first main bus; The second bus controller establishes communication with the second part of remote terminals via the second main bus; When the first optical fiber or the first bus controller fails, the second bus controller establishes communication with the second part of the remote terminals through the second main bus, and the second bus controller establishes communication with the first part of the remote terminals through the second standby bus; When the second optical fiber or the second bus controller fails, the first bus controller establishes communication with the first part of remote terminals through the first main bus, and the first bus controller establishes communication with the second part of remote terminals through the first standby bus.
2. The dual-redundancy device bus topology network architecture according to claim 1, characterized in that: The first part of remote terminals and the second part of remote terminals both include multiple remote terminals.
3. The dual-redundancy device bus topology network architecture according to claim 1, characterized in that: When the first optical fiber or the first bus controller fails, the first bus controller sends a request for backup of the first bus controller to the second bus controller. After the backup of the second bus controller is completed, the first bus controller stops working.
4. The dual-redundancy device bus topology network architecture according to claim 1, characterized in that: When the second optical fiber or the second bus controller fails, the second bus controller sends a request for backup of the second bus controller to the first bus controller. After the backup of the first bus controller is completed, the second bus controller stops working.
5. The dual-redundancy device bus topology network architecture according to claim 1, characterized in that: The first main bus and the second main bus are both 1553B buses.
6. The dual-redundancy device bus topology network architecture according to claim 1, characterized in that: The number of remote terminals in the first part and the number of remote terminals in the second part are the same.
Citation Information
Patent Citations
Airborne dual channel seamless switching method and system
CN105471653A
Method for switching main BC equipment and standby BC equipment
CN115396252A
10M 1553B bus controller backup design method based on star topology
CN115550097A
Electromechanical control system based on dual-redundancy bus
CN116866107A
GJB289A bus data scheduling and redundancy management method and device
CN118101369A