A model-based approach to avionics design

Abstract

A model-based avionics design method includes: analyzing the data interface from the avionics system level to the physical level, establishing a top-down hierarchical model of the data interface based on the scenario, behavior, function and architecture of the avionics system; and verifying the interface control file according to the hierarchical model. The data interface is designed in a hierarchical structure to achieve the mapping of interface traceability and integrity of the scenario-behavior-function-architecture, verify the transitivity of the system function and the consistency of the connection, and realize rapid interface test verification and interface requirement confirmation. According to the hierarchical construction, the system function and behavior model are hierarchically mapped, the system architecture design interface is output, and then the actual bus interface data corresponding to the EICD physical level is formed.

Description

Technical Field

[0001] The present invention relates to the technical field of avionics system design, and in particular to an avionics system design method based on a model. Background Art

[0002] Avionics system refers to a complex that uses distributed computers to interconnect multiple airborne electronic subsystems through a multi-channel data bus. It takes into account the existing single-function decentralized systems, such as communication radio stations, radars, and navigation equipment, and makes overall arrangements to form a multifunctional integrated system. It can realize the measurement, collection, transmission, processing, monitoring and display functions of information, and complete tasks such as flight control, engine control, navigation, and performance management.

[0003] Avionics system signals are numerous and complex. In the process of avionics system design, it is necessary to clearly define the data interfaces of various bus protocols between subsystems and transmit interface data according to the interface protocol requirements. Data interface is an important design basis for driver software development, and the application of data interface runs through the entire process of avionics system design cycle.

[0004] However, in the current data interface design of avionics systems, the description forms of various data interfaces are not unified, and most of them are maintained and stored in paper documents. This is not conducive to the traceability and unified management of various data, and it is not convenient to view, retrieve and use various data formats, making it difficult to provide services for subsequent airborne software development, data collection and related simulation tool development. Summary of the invention

[0005] (I) Purpose of the invention

[0006] The purpose of the present invention is to provide a model-based avionics system design method, which verifies the transitivity and connection consistency of avionics system functions by realizing interface tracing and mapping of scenarios, behaviors, functions, and architectures, and quickly realizes interface test verification and interface requirement confirmation.

[0007] (II) Technical solution

[0008] To solve the above problems, according to one aspect of the present invention, a model-based avionics design method is provided, comprising: analyzing the data interface from the avionics system level to the physical level, establishing a top-down hierarchical model of the data interface based on the scenario, behavior, function and architecture of the avionics system; and verifying the interface control file (ICD) according to the hierarchical model.

[0009] Furthermore, establishing a top-down hierarchical model of the data interface includes: writing the avionics system and its internal hardware and software component interfaces through the interface control file (ICD), establishing a scenario interface control file (SICD), describing the overall functions implemented by the avionics system, establishing a functional interface control file (FICD) based on the overall functions, and dividing the avionics system into systems and subsystems; generating a logical interface control file (LICD) based on the relationship between the system and the subsystem, defining the system interface and connection relationship at the logical level; generating a physical interface control file (EICD) based on the system interface at the logical level.

[0010] Furthermore, the scenario interface control file (SICD) includes: a function definition module, which is used to define the overall function of the system; an activity diagram modeling module, which establishes a scenario-based activity diagram according to the overall function of the system to be implemented; a function decomposition module, which subdivides the system and subsystem functions and services according to the activity diagram, forms an activity information flow, and generates the function interface control file; a function verification module: based on the activity diagram simulation, verifies the correctness of the information flow and the activity diagram.

[0011] Furthermore, the functional interface control file (FICD) includes: a structure diagram modeling module: based on the relationship between each system and subsystem, using IBD (Internal Block Diagram, graphical modeling view) to generate a logical level system structure diagram; an ICD definition module: based on the active information flow and the cross-linking relationship between systems, defining the system interface and connection relationship at the logical level; an information flow binding module: binding the information flow at the system analysis level to the system interface and connection relationship at the logical level; an XML generation module: generating an LICD XML format file containing the system logical architecture, logical interface, interface connection relationship, and interface binding information.

[0012] Furthermore, the logical interface control file includes: a structure diagram modeling module: based on the system structure diagram of the logical level, using IBD (Internal Block Diagram, graphical modeling view) to generate the system structure diagram of the physical level; a data interface definition module: based on the interface of the logical level, combined with the actual bus data protocol of the avionics system, defining the physical level interface type, and establishing a physical interface control file; an ICD binding module: binding the actual physical level bus data to the physical interface control file; an XML generation module: generating an EICD XML format file containing system physical architecture, component interface, component connection relationship, and interface binding bus data protocol information.

[0013] (III) Beneficial effects

[0014] The above technical solution of the present invention has the following beneficial technical effects:

[0015] Design data interface in hierarchical structure based on XML language to realize unified hierarchical avionics system ICD management;

[0016] By applying model-based language modeling, a hierarchical model of the data interface is abstractly established to design and verify the ICD, and the correct description and tracking representation of the ICD is achieved;

[0017] Establish a mapping of the interface traceability and integrity of scenario-behavior-function-architecture to verify the transitivity of system functions and the consistency of connections. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a structural diagram of the hierarchical model provided by the present invention;

[0019] Figure 2 It is a structural diagram of the scene interface control file provided by the present invention;

[0020] Figure 3 It is a structural diagram of the functional interface control file provided by the present invention;

[0021] Figure 4 It is a structural diagram of the logical interface control file provided by the present invention;

[0022] Figure 5 is an application diagram of a scene interface control file provided by an embodiment of the present invention;

[0023] Figure 6 is an application diagram of a functional interface control file provided by an embodiment of the present invention;

[0024] Figure 7 is an application diagram of a logical interface control file provided by an embodiment of the present invention;

[0025] Figure 8 It is an application diagram of the physical interface control file provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with specific implementation methods and with reference to the accompanying drawings. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. In addition, in the following description, the description of well-known architectures and technologies is omitted to avoid unnecessary confusion of the concept of the present invention.

[0027] The present invention is described in detail below with reference to the accompanying drawings and embodiments.

[0028] Avionics systems and their internal hardware and software component interfaces must be defined and specified (e.g., unambiguous, complete, verifiable, consistent, and traceable specifications). Such specifications are typically written in the form of an Interface Control Document (ICD) and represent the basis for avionics system integration activities.

[0029] The present invention focuses on analyzing the data interface from the avionics system level to the logical level, applies model-based language modeling abstraction to establish a hierarchical model of the data interface, applies model-based advantages to design and verify ICDs, and ensures the correct description and traceability of the interface and ICD.

[0030] Based on this, the present invention provides a model-based avionics system design method, comprising:

[0031] S1: Design the data interface of ICD (interface control document) of avionics system in a hierarchical manner based on XML (eXtensible Markup Language); including:

[0032] S11: The ICD of the avionics system is layered, which includes: SICD (Service interface control document), FICD (Functional interface control document), LICD (Logical interface control document), and EICD (Electric interface control document).

[0033] S12: Generate data interface files in XML format in each level of avionics system;

[0034] S13: Establish interface mapping from top to bottom in the order of scenario, behavior, function, and architecture.

[0035] Specifically, the data can be expressed and stored based on XML language, which can ensure the real-time performance of the data, and XML language is compatible with a variety of systems, including Windows and Linux avionics systems. At the same time, XML is a plain text meta-language based on Unicode, which is used to define markup languages. It does not depend on any programming language, operating system or software vendor. XML language defines markup languages ​​such as elements and attributes, which can be used to describe the relationship, characteristics and requirements of objects.

[0036] SICD is the operation scenario analysis layer. According to the overall system functions to be achieved by the avionics system, an activity diagram based on the system operation scenario is established. The functions and services of the system and subsystems are divided according to the activity diagram to form an activity information flow and obtain FICD. At the same time, based on the activity diagram simulation, the correctness of the information flow and activity diagram is verified.

[0037] Verifying the correctness of information flow and activity diagrams includes: executing activity diagrams, verifying the correctness of inputs and outputs, and whether control flow (driving the sequential progress between activities) and information flow (data transmission between activities) run correctly between activities.

[0038] Therefore, this layer mainly describes the service model that constitutes the behavior and usage scenarios of the avionics system. The usage scenarios are the operating scenarios that define the functional activities between activity participants (people and systems, systems and systems). For example, one of the necessary scenarios of the onboard maintenance system is "performing ground inspections."

[0039] The interface description of this layer focuses on the interconnection and information flow between black boxes, and is used to illustrate the system application scenarios and outline behaviors.

[0040] The FICD obtained from the operation scenario analysis layer is the system analysis layer. After splitting the system, multiple subsystems will be obtained. FICD can generate a system structure diagram at the logical level according to the relationship between each system and subsystem; and define the system interface and connection relationship at the logical level according to the cross-linking relationship between the active information flow and the system, and bind the information flow of FICD to the system interface at the logical level, and also bind the information flow of FICD to the connection relationship at the logical level. Finally, a LICD XML format file containing the system logical architecture, logical interface, interface connection relationship, and interface binding information is generated.

[0041] Specifically, an operation scenario will include multiple systems. For example, performing ground inspections requires an "onboard maintenance system", "display system", "system under test" and "system users" (i.e. people). Establishing a system structure diagram requires the input and output information between systems in the activity diagram, the relationships between systems and possible cross-linking interface forms.

[0042] The system will be divided into subsystems according to different functional modules. The subsystems can be interconnected with each other and with other systems. For example, a system can have two subsystems, "data processing system" and "data storage system", based on functional division.

[0043] The logical level LICD will generate the physical level system structure diagram according to the logical level system structure diagram. Based on the logical level interface, combined with the actual bus data protocol of the avionics system, the physical level interface type is defined and the EICD is established.

[0044] LICD can bind the actual physical layer bus data to EICD and generate an EICD XML format file containing system physical architecture, component interfaces, component connection relationships, and interface binding bus data protocol information.

[0045] Specifically, for each module in the logical architecture, by identifying the corresponding physical components, the allocation of each component in the logical architecture to the physical hardware is realized, and the interface definition is detailed, including the detailed encoding of the physical interface and the specific definition of the transmission bus, and finally the generation of the physical architecture is realized.

[0046] S2: Establish a hierarchical model of the data interface, design and verify the ICD of the avionics system based on the hierarchical model, and describe and track the ICD of the avionics system.

[0047] The electrical interface definition model mainly includes the common properties of the device, electrical connection relationships, and signal electrical characteristics. Electrical interface documents based on XML format can easily realize the interaction of electrical interface data between different platform software applications and different design entities. However, the query, storage, change, and output of electrical characteristics in electrical interface documents need to be implemented by building a relational data table mapped with XML data in a relational database.

[0048] Example:

[0049] Figure 5 is an application diagram of a scene interface control file provided by an embodiment of the present invention, Figure 6 is an application diagram of a functional interface control file provided by an embodiment of the present invention, Figure 7 is an application diagram of a logical interface control file provided by an embodiment of the present invention, Figure 8 is an application diagram of the physical interface control file provided by the embodiment of the present invention, combined with Figure 1 From the overall hierarchical model architecture diagram, we can see that Figures 5 to 8 It is a flowchart of a specific implementation of the model-based avionics system design method in this embodiment.

[0050] The present invention aims to protect a model-based avionics design method, including: analyzing the data interface from the avionics system level to the physical level, establishing a top-down hierarchical model of the data interface based on the scenario, behavior, function and architecture of the avionics system; and verifying the interface control file according to the hierarchical model. The data interface is designed in a hierarchical manner to achieve interface traceability and integrity mapping of the scenario-behavior-function-architecture, verify the transitivity of the system function and the consistency of the connection, and achieve rapid interface test verification and interface requirement confirmation. According to the hierarchical construction, the system function and behavior model are hierarchically mapped, the system architecture design interface is output, and then the actual bus interface data corresponding to the EICD level is formed.

[0051] It should be understood that the above specific embodiments of the present invention are only used to illustrate or explain the principles of the present invention, and do not constitute a limitation of the present invention. Therefore, any modifications, equivalent substitutions, improvements, etc. made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. In addition, the appended claims of the present invention are intended to cover all changes and modifications that fall within the scope and boundaries of the appended claims, or the equivalent forms of such scope and boundaries.

Claims

1. A model-based avionics design method, characterized in that: include: Designing a hierarchical data interface for the ICD of the avionics system based on XML language; including: S11: hierarchical ICD of the avionics system, including SICD, FICD, LICD, and EICD in sequence; S12: generating a data interface file in XML format in each level of the avionics system; S13: establishing a top-down interface mapping of scenarios, behaviors, functions, and architectures in sequence; Analyze the data interface from the avionics system level to the logical level, and establish a top-down hierarchical model of the data interface based on the scenarios, behaviors, functions, and architecture of the avionics system; Verifying the interface control document according to the hierarchical model; The hierarchical model for building a top-down data interface includes: Programming the avionics system and its internal hardware and software component interfaces through interface control files, Establish a scenario interface control file to describe the overall functions implemented by the avionics system. Establishing a functional interface control file based on the overall functions, dividing the avionics system into systems and subsystems; Generate a logical interface control file based on the relationship between the system and the subsystem, and define the system interface and connection relationship at the logical level; Generate a physical interface control file according to the system interface of the logical level; The scene interface control file includes: Function definition module, used to define the overall function of the system; Activity diagram modeling module, which establishes scenario-based activity diagrams according to the overall system functions to be achieved; A function decomposition module, which subdivides system and subsystem functions and services according to the activity diagram, forms an activity information flow, and generates the function interface control file; Functional verification module: Based on activity diagram simulation, verify the correctness of information flow and activity diagram; Verifying the correctness of information flow and activity diagrams involves executing the activity diagrams, verifying the correctness of the inputs and outputs, and that control and information flows operate correctly between activities.

2. The model-based avionics design method according to claim 1, characterized in that: The functional interface control file includes: Structure diagram modeling module: Based on the relationship between each system and subsystem, IBD is used to generate a system structure diagram at the logical level; ICD definition module: defines the system interface and connection relationship at the logical level according to the active information flow and the cross-link relationship between systems; Information flow binding module: binds the information flow at the system analysis level to the system interface and connection relationship at the logic level; XML generation module: Generates a LICDXML format file containing system logical architecture, logical interface, interface connection relationship, and interface binding information.

3. The model-based avionics design method according to claim 1, characterized in that: The logical interface control file includes: Physical structure generation module: Based on the system structure diagram at the logical level, use IBD to generate the system structure diagram at the physical level; Data interface definition module: Based on the interface at the logical level and combined with the actual bus data protocol of the avionics system, define the physical level interface type and establish the physical interface control file; ICD binding module: binds the actual physical layer bus data to the physical interface control file; XML generation module: Generates an EICD XML format file containing system physical architecture, component interfaces, component connection relationships, and interface binding bus data protocol information.

Images