An airborne universal logic soft bus system

Abstract

The present application provides an airborne universal logic soft bus system, which belongs to the field of airborne bus systems. Specifically, it includes a normalized adapter that abstracts a unified data interface and operation interface, a unified logic soft bus interface that integrates the interfaces of each bus adapter, and integrates the corresponding interfaces of each adapter into the corresponding interface of the unified logic software bus according to the communication type; the bus interface provides a unified calling interface to the outside world; the decision center ensures that data is transmitted by selecting the corresponding communication protocol during the calling process of the logic soft bus; the bus configuration abstracts some parameters that change during use into configurations, and the bus configuration changes the configuration information in the configuration file to change some characteristics of the airborne universal logic soft bus transmission process. Through the processing solution of the present application, communication between application software such as tasks, processes, partitions, and CPUs is supported, and a unified transmission interface is provided.

Description

Technical Field

[0001] The present application relates to the field of airborne buses, and in particular to an airborne universal logic soft bus system. Background Art

[0002] Common airborne data buses, such as the 1553B bus protocol, feature bidirectional output, high real-time performance, and high reliability. Widely used on military aircraft, it consists of three main components: a bus controller (BC), a remote terminal (RT), and a bus monitor (BM). The ARINC 429 bus protocol was developed by the Aeronautical Radio Corporation and approved and published by the U.S. Aviation Electronics Engineering Council in 1977. The RS422 bus is a full-duplex serial data interface standard developed and published by the Electronic Industries Association. The FC bus, short for Fibre Channel, is a high-speed serial transmission protocol developed by the American National Standards Institute (ANSI) in 1988. SRIO is a high-speed serial communication interface for board- and chip-level communication. The SRIO interconnect specification was unanimously approved by the International Standards Organization (ISO) and the International Electrotechnical Commission (IEC) in 2004. All of these communication buses are commonly used on airborne data buses, but they differ significantly in their communication methods, data formats, and communication speeds. Airborne software incorporates multiple bus communication protocols, making software design and implementation complex. Communication methods between airborne devices with different data interfaces vary widely and are complex, making data link integration, sharing, conflict resolution, and security difficult to ensure. Summary of the Invention

[0003] In view of this, the present application provides an airborne universal logic soft bus system, which solves the problems in the prior art, supports communication between application software such as between tasks, processes, partitions, and CPUs, and provides a unified transmission interface.

[0004] The present application provides an airborne universal logic soft bus system that adopts the following technical solutions:

[0005] An airborne universal logic soft bus system, including a normalized adapter, a bus interface, a decision center, and bus configuration design and implementation;

[0006] The normalized adapter abstracts a unified data interface and operation interface, integrates the interfaces of each bus adapter through a unified logical soft bus interface, and integrates the corresponding interfaces of each adapter into the corresponding interfaces of the unified logical software bus according to the communication type;

[0007] The bus interface provides a unified calling interface to the outside world;

[0008] The decision center ensures data transmission by selecting a route and using a corresponding communication protocol during the calling process of the logic soft bus;

[0009] The bus configuration abstracts some parameters that change during use into configurations. The bus configuration changes the configuration information in the configuration file to change some characteristics of the airborne universal logic soft bus during transmission.

[0010] Optionally, the normalized adapter includes an abstract bus operation handle, an operation interface of the abstract bus adapter, and integration of the bus adapter interface.

[0011] Optionally, the bus interface design includes an initialization interface design, a transmission parameter setting interface design, a transmission parameter acquisition interface design, a data sending interface design, and a data receiving interface design.

[0012] Optionally, the decision center decides to select the underlying connection of the corresponding communication protocol to transmit data to the correct data node using the correct protocol.

[0013] Optionally, the bus interface includes a local call interface.

[0014] Optionally, the bus interface includes a distributed remote service calling interface.

[0015] Optionally, when the bus interface is called remotely as a service, an open source RPC framework is used to perform service encapsulation on the interface.

[0016] Optionally, the bus adapter types include: FC bus adapter, 1553B bus adapter, 422 bus adapter, 429 bus adapter, shared memory adapter, message queue adapter, ZeroMQ adapter and partition port adapter.

[0017] In summary, this application has the following beneficial technical effects:

[0018] To address the issues of large interface differences and cumbersome usage in the use of common airborne buses, the airborne universal logical softbus system was designed and developed by combining Huawei's distributed logical softbus and the FACE standard for data transmission. This system supports communication between application software, such as between tasks, processes, partitions, and CPUs, and provides a unified transmission interface. Experimental verification shows that this logical software bus can significantly simplify the use of software communication and improve communication flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 Shown is the schematic diagram of the general logic soft bus system;

[0021] Figure 2 Shown is a diagram of the normalized adaptation abstract model;

[0022] Figure 3 Shown is the communication adapter interface integration diagram;

[0023] Figure 4 Shown is the initialization interface logic flow chart;

[0024] Figure 5 Shown is a logic flow chart of the transmission parameter setting interface;

[0025] Figure 6 The figure shows the logic flow chart of the transmission parameter acquisition interface;

[0026] Figure 7 Shown is a logic flow chart of the data receiving interface;

[0027] Figure 8 Shown is a logic flow chart of the data transmission interface;

[0028] Figure 9 Shown is a data transfer decision diagram. DETAILED DESCRIPTION

[0029] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0030] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that, in the absence of conflict, the features in the following embodiments and embodiments can be combined with each other. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without making creative work are within the scope of protection of this application.

[0031] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on this application, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement an apparatus and / or practice a method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this apparatus and / or practice this method.

[0032] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application. The illustrations only show components related to the present application and are not drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component can be changed at will, and the component layout type may also be more complicated.

[0033] Additionally, in the following description, specific details are provided to provide a thorough understanding of the examples. However, one skilled in the art will appreciate that the aspects described can be practiced without these specific details.

[0034] An embodiment of the present application provides an airborne universal logic soft bus system.

[0035] like Figure 1 and Figure 2 As shown, an airborne universal logic soft bus system includes a normalized adapter, a bus interface, a decision center, and bus configuration design and implementation;

[0036] In order to shield the differences in the use of various communication driver interfaces, the normalized adapter abstracts a unified data interface and operation interface, and integrates the interfaces of various bus adapters into a unified logical soft bus interface. According to the communication type, the corresponding interface of each adapter is integrated into the corresponding interface of the unified logical software bus.

[0037] The bus interface provides a unified calling interface to the outside world; it mainly includes: transmission service initialization interface, transmission parameter setting interface, transmission parameter acquisition interface, data sending interface, data receiving interface, and transmission handle destruction interface. These interfaces support both local interface calls and remote RPC service calls. When performing RPC remote service calls, the open source RPC framework is used to encapsulate these interfaces for service.

[0038] During the calling process of the logical soft bus, the decision center ensures that data is transmitted by selecting the corresponding communication protocol; when the upper-level application uses the logical soft bus interface, for local interface calls, the decision center will decide based on the specific configuration information when the application is initialized, and for RPC remote service calls, the decision center will decide based on the specific request information contained in the service request to select the underlying connection of the corresponding communication protocol, ensuring that the correct protocol is used to transmit data to the correct data node.

[0039] The bus configuration abstracts some parameters that change during use into configurations. The bus configuration changes the configuration information in the configuration file to change some characteristics of the onboard universal logic soft bus transmission process, making the software more portable.

[0040] The normalized adapter includes an abstract bus operation handle, an operation interface of the abstract bus adapter and integrates the bus adapter interface.

[0041] The bus interface design includes initialization interface design, transmission parameter setting interface design, transmission parameter acquisition interface design, data sending interface design and data receiving interface design.

[0042] The decision center decides to select the underlying connection of the corresponding communication protocol to transmit data to the correct data node using the correct protocol.

[0043] The bus interface includes a local call interface.

[0044] The bus interface includes a distributed remote service calling interface. When the bus interface is called remotely, the open source RPC framework is used to perform service encapsulation on the interface.

[0045] The bus adapter types include: FC bus adapter, 1553B bus adapter, 422 bus adapter, 429 bus adapter, shared memory adapter, message queue adapter, ZeroMQ adapter and partition port adapter.

[0046] The airborne universal logic soft bus of the present application supports communication between application software such as between tasks, between processes, between partitions, and between CPUs, and provides a unified transmission interface.

[0047] In one embodiment, the above-mentioned normalized adapter abstract model is combined, and FC bus normalized adaptation is taken as an example.

[0048] According to the FC driver interface, the operation handle of the FC bus is abstracted as shown in Table 1.

[0049] Table 1 FC bus operation handle

[0050]

[0051] Based on the FC driver interface, the operation interface of the FC bus adapter is abstracted as shown in Table 2.

[0052] Table 2 FC bus adapter operation interface information

[0053]

[0054] The unified logic soft bus interface integrates the FC bus adapter interface. According to the communication type, the corresponding interface of the FC adapter is integrated into the corresponding interface of the unified logic software bus. The integration process is as follows: Figure 3 shown.

[0055] 2) Bus interface design. This includes initialization interface design, transmission parameter setting interface design, transmission parameter acquisition interface design, data sending interface design, and data receiving interface design.

[0056] Combine Figure 4 Implement the initialization interface design. The detailed design description of the initialization interface is shown in Table 3.

[0057] Table 3 Initialization interface description

[0058]

[0059] Combine Figure 5 Implement the transmission parameter interface design. The detailed design description of the transmission parameter setting interface is shown in Table 4.

[0060] Table 4 Transmission parameter setting interface description

[0061]

[0062] Combine Figure 6 Implement the design of the interface for obtaining transmission parameters. The detailed design description of the interface for obtaining transmission parameters is shown in Table 5.

[0063] Table 5 Description of the interface for obtaining transmission parameters

[0064]

[0065] Combine Figure 7 Implement the data sending interface design. The detailed design description of the data sending interface is shown in Table 6.

[0066] Table 6 Data transmission interface description

[0067]

[0068] Combine Figure 8 Implement the data receiving interface design. The detailed design description of the data receiving interface is shown in Table 7.

[0069] Table 7 Data receiving interface description

[0070]

[0071] 3) Combination Figure 9 Implement the design of the decision-making center.

[0072] 4) Implement bus configuration design. The information that needs to be configured for the onboard general logic soft bus according to different communication methods is shown in Table 8.

[0073] Table 8 Soft bus configuration information table

[0074]

[0075] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An airborne universal logic soft bus system, characterized in that: Including normalization adapter, bus interface, decision center, bus configuration design and implementation; The normalized adapter abstracts a unified data interface and operation interface, integrates the interfaces of each bus adapter through a unified logical soft bus interface, and integrates the corresponding interfaces of each adapter into the corresponding interfaces of the unified logical software bus according to the communication type; The bus interface provides a unified calling interface to the outside world; During the call process of the logical soft bus, when the upper-layer application uses the logical soft bus interface, the decision center will decide to select the underlying connection of the corresponding communication protocol based on the specific configuration information when the application is initialized for local interface calls, and based on the specific request information contained in the service request for RPC remote service calls, to ensure that data is transmitted through the corresponding communication protocol through routing; The bus configuration abstracts some parameters that change during use into configurations, and the bus configuration changes the configuration information in the configuration file to change some characteristics of the airborne universal logic soft bus transmission process; Bus adapter types include: FC bus adapter, 1553B bus adapter, 422 bus adapter, 429 bus adapter, shared memory adapter, message queue adapter, ZeroMQ adapter, and partition port adapter.

2. The airborne universal logic soft bus system according to claim 1, characterized in that: The normalized adapter includes an abstract bus operation handle, an operation interface of the abstract bus adapter and integrates the bus adapter interface.

3. The airborne universal logic soft bus system according to claim 1, characterized in that: The bus interface design includes initialization interface design, transmission parameter setting interface design, transmission parameter acquisition interface design, data sending interface design and data receiving interface design.

4. The airborne universal logic soft bus system according to claim 1, characterized in that: The decision center decides to select the underlying connection of the corresponding communication protocol to transmit data to the correct data node using the correct protocol.

5. The airborne universal logic soft bus system according to claim 1, characterized in that: The bus interface includes a local call interface.

6. The airborne universal logic soft bus system according to claim 1, characterized in that: The bus interface includes a distributed remote service calling interface.

7. The airborne universal logic soft bus system according to claim 6, characterized in that: When the bus interface is called remotely as a service, the open source RPC framework is used to encapsulate the interface as a service.

Images