CN114036769A

CN114036769A - Avionics system physical architecture-oriented function deployment scheme generation method and device

Info

Publication number: CN114036769A
Application number: CN202111367366.9A
Authority: CN
Inventors: 刘畅; 王金岩; 王智宇
Original assignee: China Aeronautical Radio Electronics Research Institute
Current assignee: China Aeronautical Radio Electronics Research Institute
Priority date: 2021-11-18
Filing date: 2021-11-18
Publication date: 2022-02-11
Anticipated expiration: 2041-11-18
Also published as: CN114036769B

Abstract

The application provides a method and a device for generating a function deployment scheme oriented to an avionics system physical architecture, belonging to the technical field of avionics systems, and the method comprises the following steps: acquiring description information of a functional architecture of an avionic system, wherein the description information comprises non-functional attributes of each function and interaction attributes among the functions; analyzing the relation between functional logics of the avionic system; according to the relationship between the description information of the avionic system functional architecture and the avionic system functional logic, functional configuration is carried out on the avionic system physical architecture to obtain an avionic system physical architecture configuration scheme, the problem of binding functions and physical entities can be solved, and the avionic system functional architecture is used for an avionic system.

Description

Avionics system physical architecture-oriented function deployment scheme generation method and device

Technical Field

The application belongs to the technical field of avionics systems, and particularly relates to a method and a device for generating a functional deployment scheme oriented to an avionics system physical architecture.

Background

Compared with the traditional combined avionics system design, the avionics system introduces the system comprehensive design from the physical field to the logic field, and a large amount of work is designed in the logic field based on a universal hardware module, including system application design, scheduling design, communication design and the like. A typical integrated modular avionics system includes a plurality of computing platforms, each having a plurality of application software (APP) resident thereon, and further having a plurality of specific processing components, connected by a real-time fault tolerant network system. Although this architecture saves hardware resources, it also introduces a variety of decision optimization problems in system design, such as how to allocate multiple application software to the hardware processor, how to make the processor meet the time requirements for the application, and how to allocate network bandwidth to communication messages to meet the delay requirements.

Aiming at the development requirements of avionic systems, a comprehensive method and a comprehensive approach are adopted, and the effective improvement of the comprehensive capability and the effectiveness of the system is the core problem of deep comprehensive avionic system research. In the model-based system design, the model-driven digital aided design tool is utilized to effectively support the architecture design of the avionics system. However, the digital design tool, which utilizes the powerful processing capability of the computer, needs to be designed in various system fields for analyzing the intrinsic mechanism of the system. In the process of converting the functional architecture into the physical architecture design, the combination of the functions and the physical resources, or the process of binding software and hardware, the reasonable configuration binding can ensure that the result of the functional design is correctly inherited to the physical architecture, and simultaneously ensure that the avionic system platform architecture can effectively support the function realization and the task completion. On the other hand, if the system configuration cannot be developed directly according to the functional architecture and the system design requirements and design constraints, a massive configuration scheme appears in the binding process of the functions and the physical entities, and difficulty is brought to subsequent architecture evaluation and optimization.

Therefore, there is a need for an efficient method for function deployment on a physical architecture in the system architecture design activity.

Disclosure of Invention

In order to solve the problem of binding between functions and physical entities in the related art, the application provides a method and a device for generating a function deployment scheme oriented to an avionics system physical architecture, and the technical scheme is as follows:

in a first aspect, a method for generating a function deployment scenario for an avionics system physical architecture is provided, where the method includes:

acquiring description information of a functional architecture of an avionic system, wherein the description information comprises non-functional attributes of each function and interaction attributes among the functions;

analyzing the relation between functional logics of the avionic system;

and performing function configuration on the avionics system physical architecture according to the relationship between the description information of the avionics system functional architecture and the avionics system functional logic to obtain an avionics system physical architecture configuration scheme.

Wherein, the analysis of the relationship between the avionics system functional logics comprises:

designing a dependency relationship mapping between avionics system functions, wherein the dependency relationship comprises three types of dependence based on reference, composition structure dependence and data integrity dependence, and the constraint condition of each type of dependency relationship comprises coexistence constraint and mutual exclusion constraint;

determining a dependency strength value between the functions according to the dependency relationship mapping between the functions;

constructing a function dependency relationship matrix of the avionic system according to the dependency relationship mapping between the functions and the dependency strength values between the functions;

and performing system function aggregation processing on the function dependency relationship matrix to obtain a target dependency relationship matrix.

The performing system function aggregation processing on the function dependency relationship matrix to obtain a target dependency relationship matrix includes:

and combining the functions of which the dependency strength values are higher than a preset threshold value in the functional dependency relationship matrix, and reducing the dimension of the functional dependency relationship matrix to obtain the target dependency relationship matrix.

Wherein, according to the description information of the avionics system functional architecture and the relationship between the avionics system functional logics, the functional configuration is carried out on the avionics system physical architecture, and the method comprises the following steps:

according to the relationship between the description information of the avionic system functional architecture and the avionic system functional logic, modeling the avionic system physical architecture to obtain a physical architecture model of the avionic system, wherein the physical architecture model is used for describing physical carriers with functions to be configured and the connection relationship among the physical carriers;

and establishing a corresponding relation between the functions in the target dependency relation matrix and the physical carriers in the physical architecture model.

Wherein the non-functional attributes comprise: time class attributes, reliability attributes, information quality, demand for resources, and functional design constraints.

Wherein the interaction attribute between the functions comprises: interface name, sending mode, transmission mode, data type, data block length and data word definition.

Wherein, the relationship between the functional logics comprises: logic sequence in the process of realizing each function, requirements for resources, information interaction mode and the position of subsystem module in the airplane layout.

Further, the method further comprises:

and (4) checking the functional logic interaction consistency of the avionics system physical architecture after function configuration.

Further, the method further comprises:

and generating a file with a preset format by the verified avionics system physical architecture configuration scheme.

In a second aspect, a functional deployment scenario generation apparatus for an avionics system physical architecture is provided, the apparatus including:

the acquiring module is used for acquiring description information of the avionics system functional architecture, wherein the description information comprises non-functional attributes of each function and interaction attributes among the functions;

the analysis module is used for analyzing the relation between the functional logics of the avionic system;

and the configuration module is used for performing functional configuration on the avionics system physical architecture according to the relationship between the description information of the avionics system functional architecture and the avionics system functional logic to obtain an avionics system physical architecture configuration scheme.

According to the method and the device for generating the functional deployment scheme for the avionic system physical architecture, the design result of the avionic system functional architecture can be inherited and utilized, the design constraint conditions and the design requirements are fully considered through the analysis of the relationship among system functions, the interaction relationship among the functions is optimized, an effective and reasonable avionic system function and physical resource configuration scheme is generated, and high-quality input is provided for the detailed design, simulation and evaluation of the avionic system physical architecture. By the method and the device, the relationship between the system functions can be mapped with the description of the system platform architecture, and a quantitative relationship matrix is established, so that an effective means is provided for function aggregation and recombination. According to the analysis result, a design principle of binding platform architecture resources and functions/function groups is established, a designer is helped to establish a configuration scheme model, and the design accuracy and the design efficiency are improved. Meanwhile, the consistency of the functional interaction after the configuration scheme is generated is checked, so that the accuracy of the preorder design result can be ensured to be inherited, and a basis is provided for design feedback and problem positioning in subsequent design.

Drawings

Fig. 1 is a flowchart of a method for generating a function deployment scenario for an avionics system physical architecture provided in the present application;

FIG. 2 is a functional description diagram of the functional architecture converted into a physical architecture according to the present application;

FIG. 3 is a schematic diagram of a functional logic relationship matrix provided herein;

FIG. 4 is a schematic diagram of a relationship matrix after function aggregation provided herein;

FIG. 5 is a schematic view of a relational hierarchy corresponding to an avionics system architecture level provided in the present application;

fig. 6 is a binding diagram of a functional architecture and a physical architecture provided in the present application.

Detailed Description

The present application will now be described in further detail with reference to specific embodiments and the accompanying drawings.

According to the method for generating the functional deployment scheme for the avionics system physical architecture, the method can be effectively combined with a modeling design process in model-based system design activities, and accuracy and efficiency of the architecture design activities are improved.

The application provides a method for generating a function deployment scheme oriented to an avionics system physical architecture, as shown in fig. 1, the method includes:

step 110, obtaining description information of the avionics system functional architecture, wherein the description information comprises non-functional attributes of each function and interaction attributes among the functions;

step 120, analyzing the relation between functional logics of the avionics system;

and step 130, performing function configuration on the avionics system physical architecture according to the relationship between the description information of the avionics system functional architecture and the avionics system functional logic to obtain an avionics system physical architecture configuration scheme.

The application provides a method for generating a function deployment scheme for an avionics system physical architecture, which aims to solve the problem of effective conversion from a functional architecture design to a physical architecture design in the model-based avionics system architecture design process. The method comprises the steps of obtaining avionic system function architecture information, analyzing the relation between system function logics, carrying out quantitative processing, then carrying out system function aggregation, further finishing the binding of system functions and physical resources, and generating a required target physical architecture configuration scheme after function interaction consistency check.

The application also provides another function deployment scheme generation method for the avionics system physical architecture, and the method comprises the following steps:

step 210, obtaining description information of the avionics system functional architecture, wherein the description information comprises non-functional attributes of each function and interaction attributes among the functions.

Wherein the non-functional attributes include: time class attributes, reliability attributes, information quality, requirements for resources, functional design constraints, and the like.

Interaction attributes between functions, including: interface name, sending mode, transmission mode, data type, data block length, data word definition and the like.

After modeling of the avionics system functional architecture is completed, system information is transferred through the model, usually in a UML, XML or document manner. In the physical architecture modeling link, the transmission of the architecture information is completed through model conversion. In the method, a physical architecture model adopts an AADL model form, and related information of a logic function is established in a physical architecture. The modeling work of the functional logic elements is to establish a system functional architecture by using AADL according to the division of functions, the definition of interfaces and the type of interactive information. The basic logic is as in fig. 2.

1) Non-functional attributes: after the avionics system functional architecture design is finished, information such as each function, topology, interactive connection, interface and the like of the whole system can be expressed through formal model expression, and besides, an important part of information needs to be described through model codes, namely non-functional attributes contained in each architecture element. These information are all transferred to the physical architecture design through the model, and are also important factors influencing the function aggregation (as described in step 250), and the specific transfer process is determined according to the model description selected in the design activity, in the method, the model is transferred as SysML model → XML description → AADL model.

2) Interaction attributes between functions: in the avionics system functional architecture, the description between interfaces is a logical interface control file (ICD), which describes various attributes of information interaction between functions. The port description for the functional architecture model may be selected based on transmission information characteristics, with port-to-port connections defining port communications between active components of a system. Such port communication includes a directional transmission interface for input and output of inter-component data, events or event data; and the port-to-port connections are paths for directed transmission of data and events between components. The components in the AADL model are described by selecting Port components. For the connection description of the functional architecture model, the logic of the functional organization is reflected on one hand and a binding carrier of the architecture resource is provided from a port to a port (information transfer) on the other hand through the modes of data connection, delay data connection, event data connection and event connection.

In this embodiment, after step 210, the relationship between the functional logics of the avionics system is analyzed, where the relationship between the functional logics may include: logic sequence in the process of realizing each function, requirements on resources, information interaction modes, positions of subsystem modules in the airplane layout and the like.

For example: avionics system functionality, in the form of platform-supported software, may present its own set of constraints when deployed to a module or chassis. For example, if some functions belong to the same subsystem and are required to meet frequent and real-time communication requirements, the software is suitable for being deployed in the same module. While some functions may have the same or similar higher security level, they should not be deployed within the same module or chassis.

Step 220, designing a dependency relationship mapping between the avionics system functions, wherein the dependency relationship comprises three types of dependency based on reference, composition structure dependency and data integrity dependency, and the constraint condition of each type of dependency relationship comprises coexistence constraint and mutual exclusion constraint.

In addition, the constraint conditions of each dependency relationship can also comprise extensible constraints, the constraints refer to newly added constraints of developers in specific avionic designs, and for the constraints, the scheme provides a constraint expansion module, namely extensible constraints, and the new constraint relationships are expressed through constraint strength analysis levels and quantization strengths.

And step 230, determining a dependency strength value between the functions according to the dependency relationship mapping between the functions.

The invention provides a mathematical quantization relation mapping method, which quantizes the relation strength between two functions of an avionic system, and divides the relation strength into Level-M, Level-D, Level-1, Level-2, Level-3 and 5 levels according to strength levels, wherein Level-M represents mutual exclusion relation, the Level-1 to Level-3 are increased progressively according to coexistence dependence strength, and the Level-D represents that the functions are mutually independent and are not influenced by each other. The quantized intensity values corresponding to the 5 intensity levels are-1, 0, 1, 2, 3, respectively. The specific description relationship can be shown in table 1.

Table 1 functional relationship strength description

And 240, constructing a function dependency relationship matrix of the avionic system according to the dependency relationship mapping between the functions and the dependency strength values between the functions.

And after the relation between the functions is analyzed, generating a corresponding avionics system function logic relation matrix according to the analysis result. Let the avionics system consist of M functions, denoted Fm, where 0 < M < M. Function logic relationship matrix as shown in fig. 3, each space in the table has a number representing the strength of the relationship between two functions, and the meaning of the specific numerical value is shown in table 1. Taking the example shown in fig. 3, R (2, 1) — 2, indicating that the relationship between function F2 and function F1 is Level-2, and R (3, 2) — 1, indicating that the relationship between function F3 and function F2 is Level-M, which is a mutually exclusive relationship.

In the method described in the invention, the blank can default to 0, and the relationship matrix can be updated if the relationship is subsequently confirmed.

And 250, combining the functions of which the dependency strength values are higher than a preset threshold value in the functional dependency relationship matrix, and reducing the dimension of the functional dependency relationship matrix to obtain a target dependency relationship matrix.

After obtaining the initial functional relationship matrix (including all the functions inherited from the functional architecture), aggregation of system functions is required next, because the aggregated functions may be divided as much as possible in the same cabinet, the same module, the same processing resource, or even the same partition, and such division is very important depending on further processing of the functional logic relationship matrix and also depending on understanding and decision of the system designer.

For the generated relationship matrix, from the mathematical point of view, functions with higher relationship strength are combined, and the combination scheme combines functions corresponding to 3/2/1 strength to generate a new matrix with reduced matrix latitude, for example, combining the matrices in fig. 3 to generate a new matrix shown in fig. 4.

Wherein N is less than or equal to M.

From the perspective of avionics system design, aggregation also needs to consider the hierarchy of the system architecture, which can be considered according to the hierarchy of partition level, module level, system level, etc. (a specific avionics system may have a certain difference in architecture). Mapping is carried out according to the levels of the architecture elements and the functional relationship, and aggregation of the matrix of the mathematical layer is guided, and the mapping relationship is shown in figure 5.

It should be noted that the mapping relationship is not an absolute relationship on the boundary, the specific division needs to be determined according to the system requirements, and due to the presence of Level-D levels (i.e. the value of 0 in the matrix), in the function aggregation, many division schemes are generated, which may make the finally generated relationship matrix not be divided in many. On one hand, the proper division needs to be finally judged by performing simulation analysis and evaluation of the architecture in the subsequent design; on the other hand, the system configuration scheme itself does not have a unique correct solution, or the system designer comprehensively evaluates through factors such as system reuse, team configuration, production relationship, and the like. The method provided by the patent can converge the configurations forward from the perspective of system architecture design and approach the most feasible architecture design scheme.

And step 260, according to the relationship between the description information of the avionic system functional architecture and the avionic system functional logic, modeling the avionic system physical architecture to obtain a physical architecture model of the avionic system, wherein the physical architecture model is used for describing physical carriers to be configured with functions and the connection relationship among the physical carriers.

In step 210, each function puts initial requirements on processing resources, storage resources and interface resources, and the requirements are inherited from the functional architecture model. However, to deploy the functionality onto a physical platform, a more specific physical platform description is required. This requires both architectural features of the physical platform and dimensioning of physical resources that conform to the architectural features. For avionics systems, their physical platform architecture features have undergone an evolution from split, federated to today's integrated modular avionics systems (IMA). Different architectural features are selected, so that the types and forms of physical platform entity resources are basically defined.

Taking an integrated modular avionics system as an example, according to the hierarchy of system domains, systems, modules, processors (under the condition of multi-core), and partitions, the hierarchy corresponds to different function aggregation modes, and the lower the hierarchy, the higher the corresponding function association degree.

Corresponding to the above description, a physical architecture model (only including a platform) based on AADL is established, the architecture features require a corresponding model mapping relationship, and the architecture scale confirms the model and scale by model selection for the standard physical entity specification according to the requirement of the aggregated functions on resources. Still taking the IMA system as an example, it is to confirm the configuration and number of IMA modules and the form (topology, bus type, etc.) they are organized together.

And 270, establishing a corresponding relation between the functions in the target dependency relation matrix and the physical carriers in the physical architecture model.

Binding the function/function group with the physical resource of the corresponding hierarchy according to the relationship matrix after function aggregation generated in step 250, wherein the binding includes two types:

1) binding of functions/groups of functions to physical entities

Through the binding relationship, a function/group of functions must be mapped into an execution platform model (a class of components of the AADL) that represents a physical entity. In a system, these bindings define where code executes and where data and executable code is stored. Likewise, connections between components within a system must be tied to the appropriate execution platform components (e.g., a simple link to a separate bus or a connection in a complex distributed system must be tied to bus sequencing and intermediate processors and peripherals). The execution platform components can represent resources of the computer system as well as elements of the external physical environment. The physical resources of a computer system are represented by processor, memory, and bus classes.

After the functional logic and the physical entity of the avionics system are established, important design contents are that the two models are subjected to system association, and the model is reflected in the AADL model and is designed by using Binding (Binding), and a schematic diagram of the design is shown in fig. 6.

2) Binding of interactions between functions/groups of functions to actual system paths

In the avionics system physical architecture AADL model, interaction between function groups is realized through direct Connection (Connection) between interfaces (ports) of functional components, but an actual physical channel is reflected by using a system Flow (Flow), and finally Flow information set in the model is bound with logical Connection information to realize the binding of the interaction between the function groups and the actual system channel.

The system flow can reflect the use condition of the system and is the basis of system analysis. The logical paths of the system architecture and the important system characteristics can be described and analyzed through the system flow. The system flow can be described in three ways: flow specification, flow implementation, and end-to-end flow. The three modes are described differently and the following table summarizes the three types of flow descriptions.

TABLE 2 description of the model element streams

The Flow form is adopted, and the purpose is to reflect the application interaction of functional logic on a physical architecture AADL model after software and hardware are bound, for example, in an avionics system, a radio frequency signal is acquired from a sensor, and the settlement and execution of a task are finished by a back-end task system according to the result after information processing, and the complete Flow, the experienced path, the involved scheduling, the used bus and interface and the like embodied in the application process are used, so that the subsequent analysis of the architecture design is finished.

The system flow establishment can be realized in various sequences, and can be carried out in a top-down index estimation decomposition mode based on a forward design flow of an avionics system architecture. The End-to-End Flow can be established layer by layer, relating to the interaction of basic physical entities. Thus forming the desired application stream via programming.

And step 280, checking functional logic interaction consistency of the avionics system physical architecture after function configuration.

From the system architecture forward design flow, the interactive verification of the functional logic should be completed in the functional architecture design link. However, after the design activities of function aggregation and function and physical entity binding, whether the realization of function interaction is still reasonable or not and whether the task of the avionic system can still be effectively completed or not needs to be checked for the consistency of the next part of interaction.

The consistency check is completed by checking the model bound with the configured physical architecture scheme, and the main contents of the consistency check comprise:

1) it is checked whether the function and the path between the functions are all bound to the established physical path.

By checking whether all functional connections (connections) are bound to a certain path in the (Binding) physical architecture, such physical path may be a thread interface connection, a bus Binding, a partition connection. This check can be done automatically using AADL modeling analysis tools.

2) Checking whether the output interface (Port) attribute of the aggregated function group meets the requirements of each function before aggregation.

And for a new function generated after the combination of the plurality of functions, checking whether the content of a new interface of the new function meets the information requirement required by the operation of the new function. This check can be performed using model functional unit testing.

3) It is checked whether there are free resources and for configuration to the corresponding function.

For the configured physical architecture model, the system flow is established in step 270 for traversal, and the AADL modeling analysis tool detects that the physical resource model is not used, so as to detect idle resources (except system redundancy resources) for subsequent system optimization.

And 290, generating a file with a preset format according to the checked avionics system physical architecture configuration scheme.

After the interactive consistency is checked, the formed avionics system architecture physical architecture scheme (scheme pool) with well configured functions needs to perform subsequent physical architecture simulation, analysis and evaluation work, so that an AADL (architecture analysis and design language) model corresponding to each scheme needs to be converted into a preset format file, such as an XML (extensible markup language) format file, and is transmitted to a simulation evaluation environment at the design downstream to analyze and evaluate the non-functional attributes of the physical architecture.

The application also provides a device for generating a function deployment scheme for the avionics system physical architecture, which comprises:

the acquisition module is used for acquiring the description information of the avionics system functional architecture, and the description information comprises the non-functional attributes of each function and the interaction attributes among the functions.

And the analysis module is used for analyzing the relation between the functional logics of the avionic system.

The foregoing merely represents embodiments of the present application, which are described in greater detail and detail, and therefore should not be construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application.

Claims

1. A method for generating a function deployment scheme oriented to an avionics system physical architecture is characterized by comprising the following steps:

analyzing the relation between functional logics of the avionic system;

2. The method of claim 1, wherein analyzing relationships between avionics system functional logic comprises:

3. The method according to claim 2, wherein the performing system function aggregation processing on the function dependency relationship matrix to obtain a target dependency relationship matrix comprises:

4. The method according to claim 3, wherein the functional configuration is performed on the avionics system physical architecture according to the relationship between the description information of the avionics system functional architecture and the avionics system functional logic, and comprises:

5. The method of claim 1, wherein the non-functional attributes comprise: time class attributes, reliability attributes, information quality, demand for resources, and functional design constraints.

6. The method of claim 1, wherein the interaction attribute between the functions comprises: interface name, sending mode, transmission mode, data type, data block length and data word definition.

7. The method of claim 1, wherein the relationship between the functional logics comprises: logic sequence in the process of realizing each function, requirements for resources, information interaction mode and the position of subsystem module in the airplane layout.

8. The method of claim 1, further comprising:

9. The method of claim 8, further comprising:

10. An avionics system physical architecture-oriented function deployment scenario generation apparatus, the apparatus comprising: