Low-delay data forwarding architecture between FC network and 1394B bus and forwarding method

Abstract

The invention provides a low-delay data forwarding architecture between an FC network and a 1394B bus, and relates to the technical field of comprehensive core processing systems, the low-delay data forwarding architecture comprises an IOM module and data forwarding software residing on the IOM module and used for data forwarding, the IOM module adopts a multi-core processor, the multi-core processor is configured with a horizon 3-partition multi-core operating system, and the horizon 3-partition multi-core operating system is used for performing data forwarding on the horizon 3-partition multi-core operating system. The data forwarding software is configured in an SPARE partition of a Tianpulse 3 partition multi-core operating system, and the SPARE partition is bound with an independent processor core in the multi-core processor. According to the method, the real-time performance and the certainty of data forwarding between the FC network and the 1394B bus are realized, and the use requirements of an avionics system and a flight management system are met.

Description

Technical Field

[0001] The present invention relates to the technical field of integrated core processing systems, and in particular provides a low-latency data forwarding architecture and forwarding method between an FC network and a 1394B bus. Background Art

[0002] In the integrated modular avionics system, the input and output interface module (IOM) is a key functional module, which generally has both the avionics system network interface and the flight control system bus interface. Multiple avionics application partitions reside in the module to realize the important application functions of the avionics system and the data forwarding function between the avionics system and the flight control system. The data interaction between the avionics system and the flight control system is crucial to the flight safety and mission execution of the aircraft.

[0003] Therefore, in order to meet the requirements of both the avionics system and the flight control system, the data forwarding function should be real-time and deterministic. Summary of the invention

[0004] The purpose of this application is to solve the data interaction problem between the avionics system and the flight management system to ensure that the data forwarding function does not affect the certainty of the avionics application partition, while satisfying the data forwarding delay to meet the real-time nature of the flight management system.

[0005] In order to achieve the above object, the present invention adopts the following technical solution: a low-latency data forwarding architecture between FC network and 1394B bus, including an IOM module and data forwarding software resident on the IOM module for data forwarding,

[0006] The IOM module uses a multi-core processor, and the multi-core processor is equipped with a Tianmai 3-partition multi-core operating system.

[0007] The data forwarding software is configured in the SPARE partition of the Tianmai 3-partition multi-core operating system, and the SPARE partition is bound to a separate processor core in the multi-core processor.

[0008] The low-latency data forwarding architecture between the FC network and the 1394B bus provided by the present invention also has such a technical feature that the IOM module configures the partition scheduling table to bind the resident avionics application partitions to the designated processor cores for operation.

[0009] The low-latency data forwarding architecture between the FC network and the 1394B bus provided by the present invention also has the following technical features: the data forwarding software is driven by a forwarding configuration table, and the data receiving task receives the source message through the source bus; after the configuration search task obtains the source message ID, it searches the forwarding configuration table to obtain the target message ID, and the data sending task sends the target message through the target bus.

[0010] Another object of the present invention is to provide a method for forwarding data between an FC network and a 1394B bus with low latency, wherein the forwarding method is implemented by a forwarding architecture as described in any one of the above, and comprises the following steps:

[0011] S1: The data receiving task periodically scans the FC network device and the 1394B bus device, and receives the source message from the source device by calling the driver interface;

[0012] S2: Configure the lookup task to obtain the received source message ID, and determine the corresponding target message ID by searching the forwarding configuration table;

[0013] S3: The data sending task encapsulates the source message data into a target message with a specified configuration, and sends the target message by calling the corresponding driver interface.

[0014] The low-latency data forwarding method between the FC network and the 1394B bus provided by the present invention also has such a technical feature that the forwarding delay time of the forwarding method is the sum of the source bus message acquisition time, the forwarding configuration search time, the bus scheduling time and the target bus message sending time.

[0015] The low-latency data forwarding method between the FC network and the 1394B bus provided by the present invention also has the following technical features: the bus scheduling time is the time interval between sending messages in two consecutive bus scheduling cycles;

[0016] When the target bus is an FC network, the bus scheduling time is 0;

[0017] When the target bus is a 1394B bus, the bus scheduling time is the scheduling cycle of the 1394B bus.

[0018] Beneficial Effects

[0019] The low-latency data forwarding architecture between the FC network and the 1394B bus provided by the present invention has its data forwarding function implemented by data forwarding software. The resident hardware module adopts a multi-core processor, and the multiple avionics application partitions resident in the module are bound to different processor cores by configuring the partition scheduling table; the data forwarding software resides in the SPARE partition of the Tianmai 3 core operating system, and the SPARE partition is bound to a separate processor core to ensure the uninterrupted operation of the data forwarding task; the data forwarding software adopts a forwarding configuration table drive mode, and determines whether forwarding is required and the message configuration during forwarding by searching the forwarding configuration table, thereby realizing the real-time and deterministic data forwarding between the FC network and the 1394B bus, and meeting the use requirements of the avionics system and the flight control system. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 A schematic diagram of a data forwarding architecture provided by an embodiment of the present invention;

[0022] Figure 2 A schematic diagram of the hardware architecture of the IOM module provided in an embodiment of the present invention;

[0023] Figure 3 A schematic diagram of a data forwarding software processing flow provided by an embodiment of the present invention;

[0024] Figure 4 A schematic diagram of the worst-case delay in data forwarding provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0025] The present application is further described in detail below in conjunction with the accompanying drawings and examples, but it should be noted that these implementation methods are not limitations of the present application, and equivalent changes or substitutions in functions, methods, or structures made by ordinary technicians in the field based on these implementation methods are all within the scope of protection of the present application.

[0026] In the description of the embodiments of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the creation of the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the creation of the present application.

[0027] In addition, the terms "first", "second", "third", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", etc. may explicitly or implicitly include one or more of the features. In the description of the invention of this application, unless otherwise specified, the meaning of "plurality" is two or more.

[0028] The terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the invention of this application can be understood by specific circumstances.

[0029] like Figure 1-4 As shown, a low-latency data forwarding architecture between a FC network and a 1394B bus is provided, including an IOM module and data forwarding software resident on the IOM module for performing data forwarding. The IOM module adopts a multi-core processor, and the multi-core processor is configured with a Tianmai 3-partition multi-core operating system. The data forwarding software is configured in a SPARE partition of the Tianmai 3-partition multi-core operating system, and the SPARE partition is bound to a separate processor core in the multi-core processor.

[0030] In the above embodiment, the multi-core processor uses Feiteng FT-2000 / 4, and the working main frequency is 1GHz; the processor is connected to the FC network interface through a 4-wire, 2.5Gbps PCI e bus, and is connected to the 1394B bus interface through a 1-wire, 2.5Gbps PCI e bus; the FC network adopts the FC-AE-ASM communication protocol with a communication rate of 2.125Gbps, and the 1394B bus adopts the SAE AS5643B communication protocol with a communication rate of 200Mbps; the IOM module hardware architecture is shown in the figure below Figure 2 As shown;

[0031] In some embodiments, the IOM module architecture complies with the ARI NC653 standard, is configured with the Tianmai 3-partition multi-core operating system, adopts the BMP operation mode, and by configuring the partition scheduling table, the resident avionics application partitions are bound to the specified processor cores for operation.

[0032] There are three application partitions resident in the IOM module. Application partitions 1 and 2 are bound to processor core 0, application partition 3 is bound to processor core 1, and processor core 2 is idle. The data forwarding function is implemented by the resident data forwarding software, which runs on the SPARE partition of the Tianmai 3 core operating system. The SPARE partition is bound to processor core 3; the data forwarding architecture is as follows Figure 1 As shown;

[0033] In some embodiments, the data forwarding software is driven by a forwarding configuration table, and the data receiving task receives the source message through the source bus; after the configuration search task obtains the source message ID, it searches the forwarding configuration table to obtain the target message ID, and the data sending task sends the target message through the target bus.

[0034] In some embodiments, a method for forwarding data between an FC network and a 1394B bus with low latency is provided. The forwarding method is implemented by a forwarding architecture as described in any of the above, and includes the following steps:

[0035] S1: The data receiving task periodically scans the FC network device and the 1394B bus device, and receives the source message from the source device by calling the driver interface;

[0036] S2: Configure the lookup task to obtain the received source message ID, and determine the corresponding target message ID by searching the forwarding configuration table;

[0037] S3: The data sending task encapsulates the source message data into a target message with a specified configuration, and sends the target message by calling the corresponding driver interface.

[0038] In some embodiments, the forwarding delay time of the forwarding method is the sum of the source bus message acquisition time, the forwarding configuration search time, the bus scheduling time and the target bus message sending time.

[0039] In the above embodiment, since the SPARE partition is bound to the processor core 3, the data forwarding task is guaranteed to run uninterruptedly. Therefore, the time interval for executing the data forwarding task, that is, the task scheduling time, can be ignored. The source bus message acquisition time is the time taken by the data receiving task to call the driver interface to receive the source message; the forwarding configuration search time is the time taken to find the forwarding configuration table according to the source bus message ID and determine the target bus message ID; the target bus message sending time is the time taken by the data sending task to call the driver interface to send the target message.

[0040] In some embodiments, the bus scheduling time is the time interval between sending messages in two consecutive bus scheduling cycles.

[0041] When the target bus is an FC network, the bus scheduling time is 0;

[0042] When the target bus is a 1394B bus, the bus scheduling time is the scheduling cycle of the 1394B bus.

[0043] like Figure 4 As shown in the figure, when the IOM module forwards data from the FC network to the 1394B bus, the worst forwarding delay is as follows:

[0044] Data forwarding delay = source bus message acquisition time + forwarding configuration search time + bus scheduling time + target bus message sending time. After testing, the worst forwarding delay is no more than (T+10)μs.

[0045] When the IOM module forwards data from the 1394B bus to the FC network, the worst forwarding delay is as follows:

[0046] Data forwarding delay = source bus message acquisition time + forwarding configuration search time + target bus message sending time. After testing, the worst forwarding delay is no more than 20μs.

[0047] The above is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the protection scope of the present application. The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and variations can be made without departing from the technical principles of the present application, and these improvements and variations should also be regarded as the protection scope of the present application.

Claims

1. A low-latency data forwarding architecture between an FC network and a 1394B bus, characterized in that: It includes an IOM module and data forwarding software resident on the IOM module for data forwarding. The IOM module uses a multi-core processor, and the multi-core processor is equipped with a Tianmai 3-partition multi-core operating system. The data forwarding software is configured in the SPARE partition of the Tianmai 3-partition multi-core operating system, and the SPARE partition is bound to a separate processor core in the multi-core processor.

2. The low-latency data forwarding architecture between the FC network and the 1394B bus according to claim 1, characterized in that: The IOM module configures the partition scheduling table to bind the resident avionics application partitions to the designated processor cores for operation.

3. The low-latency data forwarding architecture between FC network and 1394B bus according to claim 1, characterized in that: The data forwarding software is driven by a forwarding configuration table. The data receiving task receives the source message through the source bus. After the configuration search task obtains the source message ID, it searches the forwarding configuration table to obtain the target message ID. The data sending task sends the target message through the target bus.

4. A low-latency data forwarding method between an FC network and a 1394B bus, characterized in that: The forwarding method is implemented by the forwarding architecture according to any one of claims 1 to 3, comprising the following steps: S1: The data receiving task periodically scans the FC network device and the 1394B bus device, and receives the source message from the source device by calling the driver interface; S2: Configure the lookup task to obtain the received source message ID, and determine the corresponding target message ID by searching the forwarding configuration table; S3: The data sending task encapsulates the source message data into a target message with a specified configuration, and sends the target message by calling the corresponding driver interface.

5. The method for forwarding data between a low-latency FC network and a 1394B bus according to claim 4, characterized in that: The forwarding delay time of the forwarding method is the sum of the source bus message acquisition time, the forwarding configuration search time, the bus scheduling time and the target bus message sending time.

6. The method for forwarding data between a low-latency FC network and a 1394B bus according to claim 5, characterized in that: The bus scheduling time is the time interval between sending messages in two consecutive bus scheduling cycles. When the target bus is an FC network, the bus scheduling time is 0; When the target bus is a 1394B bus, the bus scheduling time is the scheduling cycle of the 1394B bus.

Images