Data conversion and multiplexing method and device based on middleware

Abstract

The invention provides a data conversion and multiplexing method and device based on middleware, and the method comprises the steps: 1, generating a data conversion configuration table according to the mutual conversion characteristics between bus data and theme data; 2, according to the data conversion configuration table, initialization is carried out through conversion rules, and resource preparation in the conversion process is completed; 3, various bus data and theme data are received, data conversion is completed according to the data conversion configuration table, and converted data are obtained; and step 4, sending the converted data to a corresponding subsystem or application according to the data conversion configuration table.

Description

Technical Field

[0001] The present application relates to the field of avionics systems, and in particular to a method and device for data conversion and multiplexing based on middleware. Background Art

[0002] The data reuse method based on middleware is used to solve the current problem of multiple aircraft bus data types and difficulty in data conversion and reuse between buses. The method realizes the mutual conversion between multiple aviation bus data and a unified format of subject data through a unique data conversion method. The upper-layer application uses the subject subscription and publishing mechanism provided by the middleware to uniformly send and receive subject data. This method can realize the bus data

[0003] Current avionics use various aviation buses or networks to transmit data, and often face the problem of conversion and multiplexing between different data buses and protocols. For the conversion between different data buses and protocols, the common practice is to use a software or hardware converter to achieve protocol conversion. When facing the multiplexing problem, in order to provide data to multiple applications, it is usually necessary to divide the bandwidth into multiple independent channels, and transmit data through each independent channel separately, so as to achieve data multiplexing.

[0004] In the above common strategies, applications use various bus transceiver interfaces to send and receive data, and the application and bus type are coupled, making migration difficult. When changing or adding bus types, new converters need to be developed, and the upper-layer application needs to be changed. It is difficult to reuse data on various buses. For example, when adding new applications, the bus configuration must be changed, or the underlying logic must be changed. Summary of the invention

[0005] The present application provides a data conversion and reuse method and device based on middleware, which realizes data reuse through the subscription and publishing mechanism of the middleware.

[0006] In a first aspect, the present application provides a data conversion and reuse method based on middleware, the method comprising:

[0007] Step 1: Generate a data conversion configuration table based on the mutual conversion characteristics between bus data and subject data;

[0008] Step 2: According to the data conversion configuration table, initialize the conversion rules and complete the resource preparation for the conversion process;

[0009] Step 3: Receive various bus data and subject data, complete data conversion according to the data conversion configuration table, and obtain the converted data;

[0010] Step 4: According to the data conversion configuration table, the converted data is sent to the corresponding subsystem or application.

[0011] Specifically, bus data includes ARI NC429 data, RS422 data, A664 (avionics full-duplex switched Ethernet) data, and 1394 data;

[0012] Theme data include ARINC429 theme, RS422 theme, 1394 theme, A664 theme.

[0013] Specifically, if the conversion type is to convert 429 data into 429 subject data, the first data conversion configuration table is used to implement the mapping between the 429 data and the 429 subject data.

[0014] Specifically, the first data conversion configuration table includes the subsystem 429 data channel number, the type of data received by the subsystem, the subject configuration table corresponding to the subsystem, the number of topics of the subsystem 429, the subject ID that the subsystem 429 data can be converted, the 429 subject type, the number of FDS corresponding to the 429 subject, the 429 subject sending identifier, and the 429 subject FDS structure table.

[0015] Specifically, if the conversion type is to convert 422 data into 422 subject, or 1394 data into 1394 subject, or A664 data into A664 subject, the second data conversion configuration table is used to implement the mapping between the corresponding bus data and the corresponding subject data.

[0016] Specifically, the second data conversion configuration table includes the data sending and receiving channel, the receiving data type of the subsystem, the topic parameter configuration table, the corresponding topic quantity, the corresponding topic ID, the topic type, the topic type identifier, the topic corresponding data block number, the topic corresponding original data storage address, the topic corresponding original data length, the data corresponding conversion rule table, the data quantity to be converted, and the topic sending identifier.

[0017] Specifically, if the conversion type is to convert the subject data into 429, 422, A664, or 1394 bus data, the third data conversion configuration table is used to implement the mapping between the subject data and the corresponding bus data.

[0018] Specifically, the third data conversion configuration table includes a subject 429 data FDS structure table for 429 data configuration, a subject 422 data FDS structure table for 422 data configuration, an A664 data FDS structure table for A664 data configuration, and a 1394 data FDS structure table for 1394 data configuration.

[0019] In a second aspect, the present application provides a data conversion and multiplexing device based on middleware, the device comprising a generation unit, an initialization unit, a data conversion unit and a data sending unit, wherein:

[0020] A generating unit, used for generating a data conversion configuration table according to the mutual conversion characteristics between the bus data and the subject data;

[0021] An initialization unit, used to initialize according to the data conversion configuration table and complete resource preparation for the conversion process through conversion rules;

[0022] The data conversion unit is used to receive various types of bus data and subject data, complete data conversion according to the data conversion configuration table, and obtain the converted data;

[0023] The data sending unit is used to send the converted data to the corresponding subsystem or application according to the data conversion configuration table.

[0024] In summary, the present application provides a data conversion and reuse method and device based on middleware. The data reuse method based on middleware realizes the mutual conversion between various types of bus data and subject data in the node through configuration, has good flexibility, realizes convenient data reuse function through subject subscription and publication, and improves the compatibility of the system with different data buses and protocols. By adopting this method, the expansion capability of the entire system is greatly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A schematic diagram of the main functions provided for this application;

[0026] Figure 2 A schematic diagram of mapping subsystem 429 data to corresponding topics provided by this application;

[0027] Figure 3 A schematic diagram of mapping subsystem 422 data to corresponding topics provided by this application;

[0028] Figure 4 A schematic diagram of mapping subsystem 1394 data to corresponding themes provided in this application;

[0029] Figure 5 A schematic diagram of mapping subsystem 664 data to corresponding topics provided in this application;

[0030] Figure 6 Theme data parameter configuration table provided for this application. DETAILED DESCRIPTION

[0031] The present application is based on a data reuse method of middleware, realizes the mutual conversion between various bus and topic data through unified data conversion software, and realizes fast and convenient data reuse through the subscription and publishing functions of the topic.

[0032] The method realizes the conversion between multiple aviation bus data and topic data through flexible configuration, and realizes data reuse through the subscription and publishing mechanism of the middleware, and has the following capabilities: 1) realizes the conversion of RS422 data to topic data in the node through configuration; 2) realizes the conversion of ARI NC429 data to topic data in the node through configuration; 3) realizes the conversion of 1394 data to topic data in the node through configuration; 4) realizes the conversion of A664 data to topic data in the node through configuration; 5) realizes the conversion of topic data to RS422, ARI NC429, 1394 and A664 bus data through configuration; 6) the data conversion configuration is expandable; 6) through the transceiver interface provided by the IASE software, the topic data is published and subscribed to realize data reuse.

[0033] like Figure 1 As shown, the present application provides a data conversion and reuse method based on middleware, and the method mainly includes the following steps:

[0034] Step 1: Generate a data conversion configuration table based on the mutual conversion characteristics between bus data and subject data;

[0035] Among them, bus data includes ARI NC429 data, RS422 data, A664 (avionics full-duplex switched Ethernet) data, and 1394 data;

[0036] The subject data includes ARI NC429 subject, RS422 subject, 1394 subject, and A664 subject.

[0037] Specifically, the data conversion configuration table includes a first data conversion configuration table, a second data conversion configuration table, and a third data conversion configuration table.

[0038] Further, if the conversion type is to convert 429 data to 429 subject, the first data conversion configuration table is used to implement the mapping between 429 data and 429 subject data;

[0039] Among them, the first data conversion configuration table includes the subsystem 429 data channel number, the subsystem receiving data type, the subsystem corresponding to the subject configuration table, the subsystem 429 subject number, the subject ID that the subsystem 429 data can be converted, the 429 subject type, the 429 subject corresponding to the FDS number, the 429 subject sending identifier, and the 429 subject FDS structure table.

[0040] Furthermore, if the conversion type is to convert 422 data into 422 subject, or 1394 data into 1394 subject, or A664 data into A664 subject, the second data conversion configuration table is used to implement the mapping between the corresponding bus data and the corresponding subject data.

[0041] Among them, the second data conversion configuration table includes the data sending and receiving channel, the receiving data type of the subsystem, the topic parameter configuration table, the corresponding topic quantity, the corresponding topic ID, the topic type, the topic type identifier, the topic corresponding data block number, the topic corresponding original data storage address, the topic corresponding original data length, the data corresponding conversion rule table, the data quantity to be converted, and the topic sending identifier.

[0042] Furthermore, if the conversion type is to convert the subject data into 429, 422, A664, or 1394 bus data, the third data conversion configuration table is used to implement the mapping between the subject data and the corresponding bus data.

[0043] Among them, the third data conversion configuration table includes the subject 429 data FDS structure table configured for 429 data, the subject 422 data FDS structure table configured for 422 data, the A664 data FDS structure table configured for A664 data, and the 1394 data FDS structure table configured for 1394 data.

[0044] Step 2: According to the data conversion configuration table, initialize the conversion rules and complete the resource preparation for the conversion process;

[0045] Step 3: Receive various bus data and subject data, complete data conversion according to the data conversion configuration table, and obtain the converted data;

[0046] Step 4: According to the data conversion configuration table, the converted data is sent to the corresponding subsystem or application.

[0047] It should be noted that the corresponding subsystems or applications are the corresponding inertial navigation, communication, Beidou, electromechanical and other systems in the avionics system.

[0048] It should be noted that, in step S1 data conversion configuration, the present invention realizes 429 data to 429 subject data configuration, 422 data to 422 subject data configuration, A664 data to A664 subject data configuration, 1394 data to 1394 subject data configuration, and subject data to 429\422\A664\1394 bus data configuration.

[0049] Embodiment 1

[0050] like Figure 2 As shown, the embodiment of the present application takes the sending process of 429 data converted into 429 topic data according to the configuration as an example to explain in detail, and the method includes:

[0051] Step 1: Traverse all 429 data channels and receive 429 data;

[0052] Step 2: If data is successfully received on a 429 channel, it is necessary to continue receiving until the reception fails or the maximum number of receptions is reached;

[0053] Step 3: Get 429 data l abe l number;

[0054] Step 4: According to the 429 channel number and the label number, based on the index relationship established during the initial configuration, locate the subsystem 429 subject configuration table location, 429 subject structure configuration table location, 429 data set location and the corresponding 429 data structure corresponding to the data;

[0055] Step 5: Set the corresponding FS flag in the 429 subject of the 429 data to normal;

[0056] Step 6: Set the sending flag of the topic corresponding to the 429 data to send;

[0057] Step 7: Copy the 429 data to the specified location;

[0058] Step 8: Send all 429 topic data with the sending flag set to valid;

[0059] Step 9: After sending is completed, clear the sending flag.

[0060] Embodiment 2

[0061] like Figure 3 As shown, the embodiment of the present application takes the process of converting 422 data into 422 topic data according to the configuration as an example to explain in detail, and the method includes:

[0062] Step 1: Traverse all 422 data channels and receive 422 data;

[0063] Step 2: If data is successfully received on a 422 channel, it is necessary to continue receiving until the reception fails or the maximum number of receptions is reached;

[0064] Step 3: Obtain the corresponding 422 subsystem parameter configuration table through the subsystem 422 channel number;

[0065] Step 4: Find the corresponding topic according to the data block number of single package 422;

[0066] Step 5: Convert the single packet 422 data according to the conversion rules;

[0067] Step 6: Store the converted 422 single packet data to the configured location.

[0068] Step 7: Send all 422 topic data with the sending flag set to valid;

[0069] Step 8: After sending is completed, the sending flag is cleared.

[0070] Embodiment 3

[0071] like Figure 4 As shown, the embodiment of the present application takes the process of receiving 1394 data and converting it into 1394 subject data according to the configuration as an example to explain in detail, and the method includes:

[0072] Step 1: Traverse all 1394 data channels and receive 1394 data;

[0073] Step 2: If data is successfully received on a certain 1394 channel, it is necessary to continue receiving until the reception fails or the maximum number of receptions is reached;

[0074] Step 3: Obtain the corresponding 1394 subsystem parameter configuration table through the subsystem 1394 channel number;

[0075] Step 4: Find the corresponding topic according to the single-packet 1394 data block number;

[0076] Step 5: Convert the single-packet 1394 data according to the conversion rules;

[0077] Step 6: Store the converted 1394 single packet data to the configured location.

[0078] Step 7: Send all 1394 topic data with the sending flag set to valid;

[0079] Step 8: After sending is completed, the sending flag is cleared.

[0080] Embodiment 4

[0081] like Figure 5 As shown, the embodiment of the present application takes the process of converting A664 data into A664 topic data according to the configuration as an example to explain in detail, and the method includes:

[0082] Step 1: Traverse all A664 data channels and receive A664 data;

[0083] Step 2: If data is successfully received on a certain A664 channel, it is necessary to continue receiving until the reception fails or the maximum number of receptions is reached;

[0084] Step 3: Obtain the corresponding A664 subsystem parameter configuration table through the subsystem A664 channel number;

[0085] Step 4: Find the corresponding topic according to the single package A664 data block number;

[0086] Step 5: Convert the single package A664 data according to the conversion rules;

[0087] Step 6: Store the converted A664 single packet data to the configured location.

[0088] Step 7: Send all A664 topic data with the sending flag set to valid;

[0089] Step 8: After sending is completed, the sending flag is cleared.

[0090] Embodiment 5

[0091] like Figure 6 As shown, the embodiment of the present application takes the process of receiving subject data and converting it into bus data according to the configuration as an example to explain in detail, and the method includes:

[0092] Step 1: Poll all topic data to be received;

[0093] Step 2: Call the middleware receiving function to receive the corresponding topic data;

[0094] Step 3: If received successfully, process the corresponding topic data according to the configuration;

[0095] Step 4: If the number of receptions of the topic data is less than the maximum value, and both reception and processing are successful, continue receiving.

[0096] The key points of the present invention are:

[0097] A) Data conversion configuration between various bus data and subject data

[0098] The present invention designs unique conversion rules to realize 429 data to 429 subject, 422 data to 422 subject, 1394 data to 1394 subject, A664 data to A664 subject, as well as subject data to 429 data, subject data to 422 data, subject data to 1394 data, and subject data to A664 data.

[0099] B) Data conversion and data reuse process

[0100] The present invention designs a unique data conversion and multiplexing process. After various types of bus data are received, they are first converted into corresponding subject data, and then the subject data is published to the system through the middleware, realizing the demand that the bus data is used by each node in the system.

[0101] After the subject data is received, it is converted into corresponding bus data through conversion rules and sent to the corresponding system through the corresponding bus, realizing the need to transmit data from within the system to each bus.

[0102] In summary, the present application provides a data conversion and reuse method based on middleware. The data reuse method based on middleware realizes the mutual conversion between various types of bus data and subject data in the node through configuration, has good flexibility, realizes convenient data reuse function through subject subscription and publication, and improves the compatibility of the system with different data buses and protocols. By adopting this method, the expansion capability of the entire system is greatly improved.

[0103] At present, the technology mentioned in this patent has been tried in a certain type of helicopter avionics system, with good results. It meets the data communication needs between various devices in the avionics system and brings better application portability and scalability.

Claims

1. A data conversion and reuse method based on middleware, characterized in that: Methods include: Step 1: Generate a data conversion configuration table based on the mutual conversion characteristics between bus data and subject data; Step 2: According to the data conversion configuration table, initialize the conversion rules and complete the resource preparation for the conversion process; Step 3: Receive various bus data and subject data, complete data conversion according to the data conversion configuration table, and obtain the converted data; Step 4: According to the data conversion configuration table, the converted data is sent to the corresponding subsystem or application.

2. The method according to claim 1, characterized in that Bus data includes ARINC429 data, RS422 data, A664 data, and 1394 data; The subject data includes ARINC429 subject, RS422 subject, 1394 subject, and A664 subject.

3. The method according to claim 2, characterized in that If the conversion type is to convert 429 data to 429 subject, the first data conversion configuration table is used to implement the mapping between the 429 data and the 429 subject data.

4. The method according to claim 3, characterized in that The first data conversion configuration table includes the subsystem 429 data channel number, the subsystem receiving data type, the subsystem corresponding topic configuration table, the subsystem 429 topic quantity, the topic ID that the subsystem 429 data can be converted, the 429 topic type, the 429 topic corresponding FDS quantity, the 429 topic sending identifier, and the 429 topic FDS structure table.

5. The method according to claim 2, characterized in that: If the conversion type is to convert 422 data into 422 subject, or 1394 data into 1394 subject, or A664 data into A664 subject, the second data conversion configuration table is used to implement the mapping between the corresponding bus data and the corresponding subject data.

6. The method according to claim 5, characterized in that The second data conversion configuration table includes the data sending and receiving channel, the receiving data type of the subsystem, the topic parameter configuration table, the corresponding topic quantity, the corresponding topic ID, the topic type, the topic type identifier, the topic corresponding data block number, the topic corresponding original data storage address, the topic corresponding original data length, the data corresponding conversion rule table, the data quantity to be converted, and the topic sending identifier.

7. The method according to claim 2, characterized in that If the conversion type is to convert the subject data into 429, 422, A664, or 1394 bus data, the third data conversion configuration table is used to implement the mapping between the subject data and the corresponding bus data.

8. The method according to claim 7, characterized in that The third data conversion configuration table includes a subject 429 data FDS structure table configured for 429 data, a subject 422 data FDS structure table configured for 422 data, an A664 data FDS structure table configured for A664 data, and a 1394 data FDS structure table configured for 1394 data.

9. A data conversion and multiplexing device based on middleware, characterized in that: The device comprises a generating unit, an initializing unit, a data converting unit and a data sending unit, wherein: A generating unit, used for generating a data conversion configuration table according to the mutual conversion characteristics between the bus data and the subject data; An initialization unit, used to initialize according to the data conversion configuration table through conversion rules to complete resource preparation for the conversion process; The data conversion unit is used to receive various bus data and subject data, complete data conversion according to the data conversion configuration table, and obtain the converted data; The data sending unit is used to send the converted data to the corresponding subsystem or application according to the data conversion configuration table.

Images