System and method compatible with ARINC739 and ARINC661

Abstract

The invention discloses a system and method compatible with ARINC 739 and ARINC 661, and the system employs an MVC mode, and divides an airborne system function into an airborne system model, a view, and a controller. The model is used for realizing the service logic of the airborne system function and providing the underlying implementation of an external interface of the airborne system function; the view is used for realizing a user interface by adopting interface elements compatible with an ARINC 739 protocol and an ARINC 661 protocol; the controller is used for processing the user request and forwarding the user request to the model; meanwhile, forwarding data returned by the model to the view for display; wherein the controller comprises a universal interface layer, and the universal interface layer is used for shielding the difference between an ARINC 739 protocol and an ARINC 661 protocol and providing a uniform access interface for the view. The method can adapt to different avionics system architectures.

Description

Technical Field

[0001] The present invention relates to the technical field of avionics systems, and in particular to a system and method compatible with ARINC 739 and ARINC 661. Background Art

[0002] In the traditional joint avionics system architecture (such as Figure 1 As shown in Figure 1, each airborne system function has its own independent hardware device (such as the flight management system FMS and other aircraft functions) as a carrier. The multi-control function display unit (MCDU) based on the ARINC 739 specification consists of a keyboard and a display with row selection keys. It is a more common airborne embedded display and control device. The main function of the MCDU is to interconnect with the hardware devices of the airborne system functions and provide a human-computer interaction interface for the airborne system functions.

[0003] With the rapid development of electronic technology in the aviation field, the integration of avionics is becoming increasingly higher. Airborne system functions can also reside in a universal integrated modular avionics system (IMA) in a pure software manner, instead of having independent hardware-exclusive devices. Multiple airborne system functions reside in the IMA, eliminating their own independent hardware devices, and achieving a higher degree of avionics integration. The avionics system architecture is also developing in an integrated and distributed direction.

[0004] In the integrated avionics system architecture (such as Figure 2 In the ARINC 661 specification (cockpit display and control system and user system interface protocol), the human-machine interaction interface of the airborne system function and the system function resident software are usually connected. The ARINC 661 specification divides the airborne system functions into two main functional modules: user application (UA) and cockpit display system (CDS). The UA and CDS transmit commands and events through the standard communication protocol defined by the ARINC 661 specification. The biggest feature of the display and control system based on the ARINC 661 specification is that it completely isolates the human-machine interaction interface and the logic processing function, improves the openness and portability of the system, and has gradually become an industry standard.

[0005] However, due to objective factors such as adapting to various new and old aircraft models and architecture evolution, there is an objective reality that multiple avionics system architectures coexist in a certain period of time. Airborne system function suppliers often repeat or even independently design the same airborne system function to cope with different avionics system architectures. This reduces the reusability of airborne system functions in different avionics system architectures and greatly increases the development cycle and cost.

[0006] In view of this, this application is hereby filed. Summary of the invention

[0007] The present invention aims to provide a system and method compatible with ARINC 739 and ARINC 661, so as to isolate the human-machine interaction interface and logic processing functions of the airborne system functions, increase software reusability, and cope with different avionics system architectures.

[0008] The present invention is achieved through the following technical solutions:

[0009] In a first aspect, the present invention provides a system compatible with ARINC 739 and ARINC 661, the system adopts the MVC mode to divide the airborne system functions into an airborne system model, an airborne system view and an airborne system controller;

[0010] The airborne system model is used to implement the business logic of the airborne system functions and provide the underlying implementation of the external interface of the airborne system functions;

[0011] An onboard system view for implementing a user interface using interface elements compatible with the ARINC 739 protocol and the ARINC 661 protocol;

[0012] The airborne system controller, as the coordinator between the airborne system model and the airborne system view, is used to process user requests and forward user requests to the airborne system model; at the same time, it forwards the data returned by the airborne system model to the airborne system view for display;

[0013] The airborne system controller includes a general interface layer, which is used to shield the differences between the ARINC 739 protocol and the ARINC 661 protocol and provide a unified access interface for the airborne system view.

[0014] Furthermore, the airborne system controller also includes an ARINC 739 component and an ARINC 661 component, and the ARINC 739 component and the ARINC 661 component respectively implement the interface defined by the general interface layer according to their respective protocols to adapt to different avionics system architectures;

[0015] ARINC 739 component is used to realize the interaction between the multi-control function display unit MCDU and the airborne system functions defined in the ARINC 739 protocol. The ARINC 739 component can establish a connection with the MCDU, respond to MCDU buttons, and transmit MCDU page information by calling the transport layer communication service provided by the ARINC 429 component in the airborne system model, thereby realizing the interface of the general interface layer;

[0016] The ARINC 661 component is used to implement the interaction between the A661 server and the user application defined in the ARINC 661 protocol. The ARINC 661 component calls the transport layer communication service provided by the AFDX component in the airborne system model to implement functions such as handshake with the A661 server, respond to ARINC 661 events, and send ARINC 661 commands, thereby realizing the interface of the general interface layer.

[0017] Furthermore, the general interface layer is implemented as an interface or a base class, and the ARINC 739 component and the ARINC 661 component inherit the general interface layer and implement the interface.

[0018] Further, the interface types of the general interface layer include a first interface, a second interface, a third interface and a fourth interface;

[0019] The first interface is a registration interface element interface, which is used for the onboard system view to register interface elements with the onboard system controller according to the design of the interface;

[0020] The second interface is an initialization interface, which is used for the airborne system view to select and initialize the corresponding type of interface according to the configuration of the avionics system architecture, and to set the initial page content;

[0021] The third interface is the interface for registering the response processing operation of the interface element, which is used by the onboard system view to register the response processing operation of the interface element with the onboard system controller; when the onboard system controller detects that the interface element is operated by the user, it will call the corresponding operation for processing according to the registered interface element response processing operation; for example, when the onboard system controller detects that a certain button on the interface is clicked, it will call the button click processing operation registered by the onboard system view. The response processing operation of the interface element is implemented by the onboard system view.

[0022] The fourth interface is the interface parameter setting interface, which is used when the airborne system function needs to actively refresh the interface display. The airborne system view will call the interface parameter setting interface to set a certain display parameter of the interface element. For example, the airborne system view refreshes the display of a certain label.

[0023] Further, the second interface initialization process based on the general interface layer includes initialization based on ARINC 739 components or initialization based on ARINC 661 components;

[0024] Initialization based on ARINC 739 components, including:

[0025] The onboard system view calls the registration interface element interface provided by the general interface layer;

[0026] In the first avionics architecture, the registration of the interface elements of the ARINC 739 components is then implemented; the first avionics architecture is a joint avionics system architecture;

[0027] The airborne system view calls the interface initialization interface provided by the general interface layer;

[0028] In the first avionics architecture, the interface initialization operation of the ARINC 739 component is then called;

[0029] The ARINC 739 component completes the initialization process with the multi-control function display unit MCDU according to the communication process defined by the ARINC 739 protocol;

[0030] Initialization based on ARINC 661 components, including:

[0031] The onboard system view calls the registration interface element interface provided by the general interface layer;

[0032] In the second avionics architecture, the registration of the interface elements of the ARINC 661 components is then realized; the second avionics architecture is an integrated avionics system architecture;

[0033] The airborne system view calls the interface initialization interface provided by the general interface layer;

[0034] In the second avionics architecture, an interface initialization operation of the ARINC 661 component is then called;

[0035] The ARINC 661 component completes the initialization process with the multi-control function display unit MCDU according to the communication process defined by the ARINC 661 protocol.

[0036] Further, the third interface element response process based on the universal interface layer includes an interface element response based on an ARINC 739 component or an interface element response based on an ARINC 661 component;

[0037] Interface element responses based on ARINC 739 components, including:

[0038] The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to register the interface element response processing operation;

[0039] In the first avionics architecture, the registration of the interface element response processing operation of the ARINC 739 component is then realized; the first avionics architecture is a joint avionics system architecture;

[0040] The user clicks a button on the multi-control display unit MCDU, and the MCDU sends a push word to the ARINC 739 component;

[0041] After receiving the key word, the ARINC 739 component replies with a confirmation message to the MCDU;

[0042] The ARINC 739 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation;

[0043] Then call the interface element response processing of the onboard system view;

[0044] Interface element responses based on ARINC 661 components, including:

[0045] The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to register the interface element response processing operation;

[0046] In the second avionics architecture, the registration of the interface element response processing operation of the ARINC 661 component is then realized; the second avionics architecture is an integrated avionics system architecture;

[0047] When the user clicks a button on the multi-control function display unit MCDU, the MCDU generates a NOTIFY_WIDGET_EVENT event (control notification event) to the ARINC 661 component to notify the ARINC 661 component;

[0048] After receiving the event information, the ARINC 661 component replies to the MCDU with confirmation information;

[0049] The ARINC 661 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation;

[0050] Then call the interface element response processing of the onboard system view.

[0051] Further, the process of setting interface element parameters based on the fourth interface of the general interface layer includes setting interface element parameters based on ARINC739 components or setting interface element parameters based on ARINC 661 components;

[0052] ARINC 739 component-based setting interface element parameters, including:

[0053] The airborne system view calls the interface for setting interface element parameters provided by the general interface layer;

[0054] In the first avionics architecture, the operation of setting parameters of interface elements of the ARINC 739 component is then implemented; the first avionics architecture is a joint avionics system architecture;

[0055] The ARINC 739 component performs parameter setting operations on the interface elements of the multi-control function display unit MCDU according to the communication process defined by the ARINC 739 protocol;

[0056] ARINC 661 component-based setting interface element parameters, including:

[0057] The airborne system view calls the interface for setting interface element parameters provided by the general interface layer;

[0058] In the second avionics architecture, the operation of setting parameters of interface elements of the ARINC 661 component is then implemented; the second avionics architecture is an integrated avionics system architecture;

[0059] The ARINC 661 component performs parameter setting operations on the interface elements of the multi-control function display unit MCDU according to the communication process defined by the ARINC 661 protocol.

[0060] Furthermore, the first interface is based on the mapping relationship between ARINC 739 protocol panel elements and ARINC 661 protocol controls, and guides the use of ARINC 661 protocol controls when designing a unified interface display effect.

[0061] In a second aspect, the present invention further provides a design method compatible with ARINC 739 and ARINC 661, the design method being used to implement the above-mentioned system compatible with ARINC 739 and ARINC 661; the design method comprising:

[0062] The MVC mode is used to divide the airborne system functions into airborne system model, airborne system view and airborne system controller, so as to realize the isolation of logic processing function and human-computer interaction interface function.

[0063] A universal interface layer that is independent of the human-machine interaction interface protocol is designed in the airborne system controller. The differences between the ARINC 739 protocol and the ARINC 661 protocol are shielded through the universal interface layer, and a unified access interface is provided to the airborne system view.

[0064] Four types of interfaces of the general interface layer are implemented based on ARINC 739 protocol and ARINC661 protocol respectively; among them,

[0065] The interface types of the general interface layer include the first interface, the second interface, the third interface and the fourth interface; the first interface is the registration interface element interface; the second interface is the initialization interface; the third interface is the registration interface element response processing operation interface; and the fourth interface is the interface element parameter setting interface.

[0066] Furthermore, the design method also includes:

[0067] Based on the mapping relationship between ARINC 739 protocol panel elements and ARINC 661 protocol controls, it provides guidance on the use of ARINC 661 protocol controls when designing a unified interface display effect.

[0068] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0069] 1. The system and method of the present invention are compatible with ARINC 739 and ARINC 661, and adopt the MVC mode to isolate the human-machine interaction interface and logic processing function of the airborne system function, increase software reusability, and be able to cope with different avionics system architectures.

[0070] 2. The system and method of the present invention are compatible with ARINC 739 and ARINC 661. A universal interface layer that is independent of the human-machine interaction interface protocol is designed in the airborne system controller, and the differences between the ARINC 739 protocol and the ARINC 661 protocol are shielded from the airborne system view.

[0071] 3. The present invention implements a method for implementing a general interface layer based on the ARINC 739 protocol and the ARINC 661 protocol respectively; in addition, based on the elements of the MCDU control panel defined by the ARINC 739 protocol, a mapping relationship between the ARINC 739 specification panel elements and the ARINC 661 specification controls is proposed to guide the use constraints of the ARINC 661 protocol controls when designing a unified interface display effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] The drawings described herein are used to provide a further understanding of the embodiments of the present invention, constitute a part of this application, and do not constitute a limitation of the embodiments of the present invention. In the drawings:

[0073] Figure 1 This is a schematic diagram of the joint avionics system architecture;

[0074] Figure 2 This is a schematic diagram of the integrated avionics system architecture;

[0075] Figure 3 A schematic diagram of the system architecture of the present invention being compatible with ARINC 739 and ARINC 661;

[0076] Figure 4 Implementing the interface of the general interface layer for the components of the present invention;

[0077] Figure 5 This is a flow chart of initializing the second interface based on the universal interface layer of the present invention;

[0078] Figure 6 This is a flow chart of the response of the third interface element based on the universal interface layer of the present invention;

[0079] Figure 7 This is a flow chart of setting interface element parameters for the fourth interface based on the universal interface layer of the present invention. DETAILED DESCRIPTION

[0080] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with embodiments and drawings. The exemplary embodiments of the present invention and their description are only used to explain the present invention and are not intended to limit the present invention.

[0081] The present invention designs a system and method compatible with ARINC 739 and ARINC 661, so as to isolate the human-machine interaction interface and logic processing function of the airborne system function, increase software reusability, and cope with different avionics system architectures.

[0082] The design of the present invention includes the following levels:

[0083] 1. The top-level architecture design of the airborne system adopts the MVC (Model-View-Controller) mode, which divides the airborne system functions into the airborne system model, the airborne system view and the airborne system controller; and then isolates the logic processing function from the human-computer interaction interface function, so that the logic processing function is independent of the avionics system architecture;

[0084] 2. A general interface layer that is independent of the human-machine interaction interface protocol is designed in the airborne system controller to shield the differences between the ARINC 739 protocol and the ARINC 661 protocol from the airborne system view;

[0085] 3. Methods for implementing the general interface layer based on ARINC 739 protocol and ARINC 661 protocol respectively;

[0086] 4. Based on the elements of the MCDU control panel defined by the ARINC739 protocol, the mapping relationship between the ARINC 739 specification panel elements and the ARINC 661 specification controls is proposed to guide the use constraints of the ARINC 661 protocol controls when designing a unified interface display effect.

[0087] Example 1

[0088] like Figure 3 As shown, the present invention is compatible with ARINC 739 and ARINC 661 systems, and the system adopts the MVC mode to divide the airborne system functions into an airborne system model, an airborne system view, and an airborne system controller;

[0089] The airborne system model is used to implement the business logic of the airborne system functions. For specific airborne system functions, this part of the implementation is determined and does not depend on the specific avionics system architecture. At the same time, the model also provides the underlying implementation of the external interface of the airborne system function (including the ARINC 429 protocol that carries the ARINC 739 protocol, and the AFDX layer that carries the ARINC 661 protocol). Good design and division of the functions belonging to the model can achieve the maximum reusability of airborne system development;

[0090] The airborne system view is used to implement the user interface using interface elements compatible with the ARINC 739 protocol and the ARINC 661 protocol; the design of the user interface should reflect good human-computer interaction habits. In terms of implementation, the user interface should be implemented using interface elements (push buttons, labels, etc.) compatible with ARINC 739 and ARINC 661. The interface design constraints to achieve compatibility are described below.

[0091] The airborne system controller, as the coordinator between the airborne system model and the airborne system view, is used to process user requests and forward user requests to the airborne system model; at the same time, it forwards the data returned by the airborne system model to the airborne system view for display;

[0092] The airborne system controller includes a universal interface layer (WDI), which is independent of ARINC 739 and ARINC 661. The universal interface layer is used to shield the differences between the ARINC 739 protocol and the ARINC 661 protocol, and provide a unified access interface for the airborne system view.

[0093] The following describes in detail the introduction of the universal interface layer of the present invention:

[0094] The general interface layer can be implemented as an interface or base class, and the ARINC 739 component and the ARINC 661 component inherit the general interface layer and implement the interface, such as Figure 4 shown.

[0095] The interface design must be able to achieve two-way interaction between the human-computer interface and the onboard system functions. The interface types of the general interface layer include the first interface, the second interface, the third interface and the fourth interface;

[0096] (1) The first interface is a registration interface element interface, which is used by the airborne system view to register interface elements with the airborne system controller according to the interface design;

[0097] (2) The second interface is an initialization interface, which is used by the airborne system view to select and initialize the corresponding type of interface according to the configuration of the avionics system architecture, and to set the initial page content;

[0098] (3) The third interface is the interface for registering the response processing operation of the interface element, which is used by the onboard system view to register the response processing operation of the interface element with the onboard system controller; when the onboard system controller detects that the interface element is operated by the user, it will call the corresponding operation for processing according to the registered interface element response processing operation; for example, when the onboard system controller detects that a certain button on the interface is clicked, it will call the button click processing operation registered by the onboard system view. The response processing operation of the interface element is implemented by the onboard system view.

[0099] (4) The fourth interface is the parameter setting interface of the interface element, which is used when the airborne system function needs to actively refresh the interface display. The airborne system view will call the parameter setting interface of the interface element to set a certain display parameter of the interface element. For example, the airborne system view refreshes the display of a certain label.

[0100] ARINC 739 components and ARINC 661 components, ARINC 739 components and ARINC 661 components implement the interfaces defined in the common interface layer according to their respective protocols to adapt to different avionics system architectures;

[0101] ARINC 739 component is used to realize the interaction between the multi-control function display unit MCDU defined in the ARINC 739 protocol and the airborne system function (running in an independent hardware dedicated device). The ARINC 739 component calls the transport layer communication service provided by the ARINC 429 component in the airborne system model to realize functions such as establishing a connection with the MCDU, responding to MCDU buttons, and transmitting MCDU page information, thereby realizing the interface of the general interface layer;

[0102] The ARINC 661 component is used to implement the interaction between the A661 server and the user application (UA) defined in the ARINC 661 protocol. The ARINC 661 component calls the transport layer communication service provided by the AFDX component in the airborne system model to implement functions such as handshake with the A661 server, respond to ARINC 661 events, and send ARINC 661 commands, thereby realizing the interface of the general interface layer.

[0103] In the joint avionics system architecture, ARINC 739 components implement the interfaces defined by the common interface layer; in the integrated avionics architecture, ARINC 661 components implement the interfaces defined by the common interface layer.

[0104] like Figure 5 As shown, Figure 5 The second interface initialization process based on the general interface layer includes initialization based on ARINC 739 components or initialization based on ARINC 661 components;

[0105] Initialization based on ARINC 739 components, including:

[0106] Step 1: The onboard system view calls the registration interface element interface provided by the general interface layer;

[0107] Step 2: In the first avionics architecture, registering the interface elements of the ARINC 739 components is then implemented; the first avionics architecture is a joint avionics system architecture;

[0108] Step 3: The airborne system view calls the interface initialization interface provided by the general interface layer;

[0109] Step 4: In the first avionics architecture, the interface initialization operation of the ARINC 739 component is then called;

[0110] Step 5: The ARINC 739 component completes the initialization process with the multi-control function display unit MCDU according to the communication process defined by the ARINC 739 protocol;

[0111] Initialization based on ARINC 661 components, including:

[0112] Step 6: The onboard system view calls the registration interface element interface provided by the general interface layer;

[0113] Step 7: In the second avionics architecture, the interface elements of the ARINC 661 components are registered; the second avionics architecture is an integrated avionics system architecture;

[0114] Step 8: The airborne system view calls the interface initialization interface provided by the general interface layer;

[0115] Step 9: In the second avionics architecture, the interface initialization operation of the ARINC 661 component is then called;

[0116] Step 10: The ARINC 661 component completes the initialization process with the multi-control function display unit MCDU according to the communication process defined by the ARINC 661 protocol.

[0117] like Figure 6 As shown, Figure 6 A third interface element response process based on the general interface layer, including an interface element response based on an ARINC739 component or an interface element response based on an ARINC 661 component;

[0118] Interface element responses based on ARINC 739 components, including:

[0119] Step 1: The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to register the interface element response processing operation;

[0120] Step 2: In the first avionics architecture, registering the interface element response processing operation of the ARINC 739 component is then implemented; the first avionics architecture is a joint avionics system architecture;

[0121] Step 3: The user clicks a button on the multi-control function display unit MCDU, and the MCDU sends a push word to the ARINC 739 component;

[0122] Step 4: After receiving the key word, the ARINC 739 component replies with MCDU confirmation information;

[0123] Step 5: The ARINC 739 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation;

[0124] Step 6: Then call the interface element response processing of the onboard system view;

[0125] Interface element responses based on ARINC 661 components, including:

[0126] Step 7: The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to register the interface element response processing operation;

[0127] Step 8: In the second avionics architecture, the registration of the interface element response processing operation of the ARINC 661 component is then implemented; the second avionics architecture is an integrated avionics system architecture;

[0128] Step 9: The user clicks a button on the multi-control function display unit MCDU, and the MCDU generates a NOTIFY_WIDGET_EVENT event (control notification event) to the ARINC 661 component to notify the ARINC 661 component;

[0129] Step 10: After receiving the event information, the ARINC 661 component replies to the MCDU with confirmation information;

[0130] Step 11: the ARINC 661 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation;

[0131] Step 12: Then call the interface element response processing of the onboard system view.

[0132] like Figure 7 As shown, Figure 7A process for setting interface element parameters for a fourth interface based on the general interface layer, including setting interface element parameters based on an ARINC 739 component or setting interface element parameters based on an ARINC 661 component;

[0133] ARINC 739 component-based setting interface element parameters, including:

[0134] Step 1: The airborne system view calls the interface for setting interface element parameters provided by the general interface layer;

[0135] Step 2: in the first avionics architecture, the operation of setting parameters of interface elements of the ARINC 739 component is then implemented; the first avionics architecture is a joint avionics system architecture;

[0136] Step 3: The ARINC 739 component sets the parameters of the interface elements of the multi-control function display unit MCDU according to the communication process defined by the ARINC 739 protocol;

[0137] ARINC 661 component-based setting interface element parameters, including:

[0138] Step 4: The airborne system view calls the interface for setting interface element parameters provided by the general interface layer;

[0139] Step 5: In the second avionics architecture, the operation of setting parameters of interface elements of the ARINC 661 component is then implemented; the second avionics architecture is an integrated avionics system architecture;

[0140] Step 6: The ARINC 661 component sets the parameters of the interface elements of the multi-control function display unit MCDU according to the communication process defined by the ARINC 661 protocol.

[0141] As a further implementation, the MCDU interface that complies with the ARINC 739 protocol contains only limited elements, while the ARINC 661 protocol defines a wide variety of controls to achieve various human-computer interaction interface effects. The registered interface element interface provided by the general interface layer provides a unified interface element type. In order to achieve the unification of interface elements, the ARINC 661 controls are specially implemented to correspond to the ARINC 739 interface elements as shown in Table 1.

[0142] Table 1 ARINC 661 controls implement ARINC 739 interface elements

[0143]

[0144] The present invention proposes to use the MVC design pattern to decouple interface display and logic processing, and clarifies the functions of the model, controller, and view. The system and design method can achieve software reuse (logic processing function) of different avionics system architectures as much as possible;

[0145] The present invention has universality, introduces a universal interface layer in the controller, and clarifies the interfaces included in the universal interface layer. The universal interface layer provides Figure 1 The universal interface layer is not only compatible with ARINC 739 and ARINC 661 protocols, but in fact any display-related protocol can be integrated into the system architecture as long as it implements the interface included in the universal interface layer, and is suitable for different avionics system architectures to the greatest extent.

[0146] Example 2

[0147] The difference between this embodiment and embodiment 1 is that this embodiment provides a design method compatible with ARINC 739 and ARINC 661, and the design method is used to implement the system compatible with ARINC 739 and ARINC 661 of embodiment 1; the design method includes:

[0148] The MVC mode is used to divide the airborne system functions into airborne system model, airborne system view and airborne system controller, so as to realize the isolation of logic processing function and human-computer interaction interface function.

[0149] A universal interface layer that is independent of the human-machine interaction interface protocol is designed in the airborne system controller. The differences between the ARINC 739 protocol and the ARINC 661 protocol are shielded through the universal interface layer, and a unified access interface is provided to the airborne system view.

[0150] Four types of interfaces of the general interface layer are implemented based on ARINC 739 protocol and ARINC661 protocol respectively; among them,

[0151] The interface types of the general interface layer include the first interface, the second interface, the third interface and the fourth interface; the first interface is the registration interface element interface; the second interface is the initialization interface; the third interface is the registration interface element response processing operation interface; and the fourth interface is the interface element parameter setting interface.

[0152] As a further implementation, the design method also includes:

[0153] Based on the mapping relationship between ARINC 739 protocol panel elements and ARINC 661 protocol controls, it provides guidance on the use of ARINC 661 protocol controls when designing a unified interface display effect.

[0154] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A system compatible with ARINC 739 and ARINC 661, characterized in that: The system adopts the MVC mode, dividing the airborne system functions into airborne system model, airborne system view and airborne system controller; The airborne system model is used to implement the business logic of the airborne system function and provide the underlying implementation of the external interface of the airborne system function; The airborne system view is used to implement a user interface using interface elements compatible with the ARINC 739 protocol and the ARINC 661 protocol; The onboard system controller, as a coordinator between the onboard system model and the onboard system view, is used to process user requests and forward the user requests to the onboard system model; and at the same time forward the data returned by the onboard system model to the onboard system view for display; The airborne system controller includes a universal interface layer, which is used to shield the differences between the ARINC 739 protocol and the ARINC 661 protocol and provide a unified access interface for the airborne system view.

2. The system compatible with ARINC 739 and ARINC 661 according to claim 1, characterized in that: The airborne system controller further includes an ARINC 739 component and an ARINC 661 component, wherein the ARINC 739 component and the ARINC 661 component respectively implement the interface defined by the general interface layer according to their respective protocols to adapt to different avionics system architectures; The ARINC 739 component is used to implement the interaction between the multi-control function display unit MCDU in the ARINC 739 protocol and the airborne system function. The ARINC 739 component implements the functions of establishing a connection with the MCDU, responding to MCDU buttons, and transmitting MCDU page information by calling the transport layer communication service provided by the ARINC 429 component in the airborne system model, thereby implementing the interface of the general interface layer; The ARINC 661 component is used to implement the interaction between the A661 server and the user application in the ARINC 661 protocol. The ARINC 661 component implements the handshake with the A661 server, responds to ARINC 661 events, and sends ARINC 661 commands by calling the transport layer communication service provided by the AFDX component in the airborne system model, thereby realizing the interface of the general interface layer.

3. The system compatible with ARINC 739 and ARINC 661 according to claim 2, characterized in that: The general interface layer is implemented as an interface or a base class, and the ARINC 739 component and the ARINC 661 component inherit the general interface layer and implement the interface.

4. The system compatible with ARINC 739 and ARINC 661 according to claim 1, characterized in that: The interface types of the universal interface layer include a first interface, a second interface, a third interface and a fourth interface; The first interface is a registration interface element interface, which is used for the onboard system view to register interface elements with the onboard system controller according to the design of the interface; The second interface is an initialization interface, which is used for the airborne system view to select and initialize the corresponding type of interface according to the configuration of the avionics system architecture, and to set the initial page content; The third interface is a registration interface element response processing operation interface, which is used for the onboard system view to register the response processing operation of the interface element with the onboard system controller; When the onboard system controller detects that an interface element is operated by a user, it will respond to the operation according to the registered interface element and call the corresponding operation for processing; The fourth interface is a parameter setting interface for interface elements, which is used for the onboard system view to call the parameter setting interface for interface elements to set a certain display parameter of the interface elements when the onboard system function needs to actively refresh the interface display.

5. The system compatible with ARINC 739 and ARINC 661 according to claim 4, characterized in that: The second interface initialization process based on the general interface layer includes initialization based on the ARINC 739 component or initialization based on the ARINC 661 component; Initialization based on ARINC 739 components, including: The onboard system view calls the registration interface element interface provided by the general interface layer; In the first avionics architecture, the registration of the interface elements of the ARINC 739 components is then implemented; the first avionics architecture is a joint avionics system architecture; The airborne system view calls the interface initialization interface provided by the general interface layer; In the first avionics architecture, the interface initialization operation of the ARINC 739 component is then called; The ARINC 739 component completes the initialization process with the multi-control function display unit MCDU according to the communication process of the ARINC 739 protocol; Initialization based on ARINC 661 components, including: The onboard system view calls the registration interface element interface provided by the general interface layer; In the second avionics architecture, the registration of the interface elements of the ARINC 661 components is then implemented; the second avionics architecture is an integrated avionics system architecture; The airborne system view calls the interface initialization interface provided by the general interface layer; In the second avionics architecture, an interface initialization operation of the ARINC 661 component is then called; The ARINC 661 component completes the initialization process with the multi-control function display unit MCDU according to the communication process of the ARINC 661 protocol.

6. The system compatible with ARINC 739 and ARINC 661 according to claim 4, characterized in that: The third interface element response process based on the general interface layer includes an interface element response based on an ARINC 739 component or an interface element response based on an ARINC 661 component; Interface element responses based on ARINC 739 components, including: The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to perform the registration interface element response processing operation; In the first avionics architecture, the registration of the interface element response processing operation of the ARINC 739 component is then implemented; the first avionics architecture is a joint avionics system architecture; The user clicks a button on the multi-control display unit MCDU, and the MCDU sends a key word to the ARINC 739 component; After receiving the key word, the ARINC 739 component replies with a confirmation message to the MCDU; The ARINC 739 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation; Then call the interface element response processing of the onboard system view; Interface element responses based on ARINC 661 components, including: The onboard system view calls the registration interface element response processing operation interface provided by the general interface layer to perform the registration interface element response processing operation; In the second avionics architecture, the registration of the interface element response processing operation of the ARINC 661 component is then implemented; the second avionics architecture is an integrated avionics system architecture; When the user clicks a button on the multi-control function display unit MCDU, the MCDU generates a control notification event NOTIFY_WIDGET_EVENT to the ARINC 661 component to notify the ARINC 661 component; After receiving the event information, the ARINC 661 component replies to the MCDU with confirmation information; The ARINC 661 component calls the corresponding interface element response processing operation according to the interface element registration information and the registered interface element response processing operation; Then call the interface element response processing of the onboard system view.

7. The system compatible with ARINC 739 and ARINC 661 according to claim 4, characterized in that: The fourth interface setting interface element parameter process based on the general interface layer includes setting interface element parameters based on ARINC 739 components or setting interface element parameters based on ARINC 661 components; ARINC 739 component-based setting interface element parameters, including: The onboard system view calls the interface for setting interface element parameters provided by the general interface layer; In the first avionics architecture, the operation of setting the parameters of the interface elements of the ARINC 739 component is then implemented; the first avionics architecture is a joint avionics system architecture; The ARINC 739 component performs parameter setting operations on the interface elements of the multi-control function display unit MCDU according to the communication process of the ARINC 739 protocol; ARINC 661 component-based setting interface element parameters, including: The onboard system view calls the interface for setting interface element parameters provided by the general interface layer; In the second avionics architecture, the operation of setting parameters of interface elements of the ARINC 661 component is then implemented; the second avionics architecture is an integrated avionics system architecture; The ARINC 661 component performs parameter setting operations on the interface elements of the multi-control function display unit MCDU according to the communication process of the ARINC 661 protocol.

8. The system compatible with ARINC 739 and ARINC 661 according to claim 4, characterized in that: The first interface is based on the mapping relationship between ARINC 739 protocol panel elements and ARINC 661 protocol controls, and guides the use of ARINC 661 protocol controls when designing a unified interface display effect.

9. A design method compatible with ARINC 739 and ARINC 661, characterized in that: The design method is used to implement the system compatible with ARINC 739 and ARINC 661 as described in any one of claims 1 to 8; the design method comprises: The MVC mode is used to divide the airborne system functions into airborne system model, airborne system view and airborne system controller, so as to realize the isolation of logic processing function and human-computer interaction interface function. A universal interface layer that is independent of the human-machine interaction interface protocol is designed in the airborne system controller, and the differences between the ARINC 739 protocol and the ARINC 661 protocol are shielded by the universal interface layer, so as to provide a unified access interface for the airborne system view; The four types of interfaces of the general interface layer are implemented based on the ARINC 739 protocol and the ARINC 661 protocol respectively; wherein, The interface types of the universal interface layer include a first interface, a second interface, a third interface and a fourth interface; the first interface is a registration interface element interface; the second interface is an initialization interface; the third interface is a registration interface element response processing operation interface; and the fourth interface is an interface element parameter setting interface.

10. The method for compatibility with ARINC 739 and ARINC 661 according to claim 9, characterized in that: The design approach also includes: Based on the mapping relationship between ARINC 739 protocol panel elements and ARINC 661 protocol controls, it provides guidance on the use of ARINC 661 protocol controls when designing a unified interface display effect.

Images