A simulation verification method of a model-based avionics system

Abstract

The application discloses a simulation verification method of a model-based avionics system, and contains the following steps: step 1, constructing a bottom simulation protocol transmission network by using a DDS communication protocol; step 2, providing simulation configuration distributed management functions by using a GEF graphical modeling method through various network transmission modes of the transmission network; and step 3, configuring each simulation event and message data between the simulation events according to the cross-linking relationship of the simulation events in step 2 based on the transmission network constructed in step 1. The technical scheme provided by the embodiment of the application solves the problem of mismatching between logic verification and algorithm data in the case of collaborative simulation of each subsystem model of the avionics system.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of complex system simulation verification, in particular to a simulation verification method of avionics system based on model. BACKGROUND

[0002] With the iterative application of aircraft platform, the avionics system tends to be more complex in the design process, and more emphasis is placed on the coordinated and efficient operation of each subsystem.

[0003] In the forward design process of avionics system, the current simulation verification method cannot fully meet the use requirements of the multi-model coordinated simulation of avionics system. Among them, the multi-model joint simulation of each subsystem in the avionics system needs to verify the rationality of the avionics system model design; for the joint operation of the avionics system and the aircraft / system model, it is necessary to verify that the avionics system model can meet the demand of the upper model; for the joint operation of the avionics system and other system models on the aircraft, it is necessary to verify the rationality of the avionics system model allocation requirement. In view of the above verification requirements of the avionics system, in the face of each subsystem in the avionics system involving complex algorithm model, the logical verification of the high-level avionics system by the algorithm model alone has certain deficiency.

[0004] Therefore, it is necessary to provide a simulation verification method of avionics system based on model to be suitable for the verification of avionics system model. SUMMARY

[0005] The purpose of the present application is to provide a simulation verification method of avionics system based on model to solve the problem of mismatching between logical verification and algorithm data in the case of coordinated simulation of each subsystem model of avionics system.

[0006] The technical scheme of the present application is to provide a simulation verification method of avionics system based on model, comprising:

[0007] Step 1: using DDS communication protocol to build a bottom layer simulation protocol transmission network;

[0008] Step 2: using GEF graphical modeling method to provide simulation configuration distributed management function through multiple network transmission modes of the transmission network;

[0009] Step 3: based on the transmission network built in step 1, according to the cross-linking relationship of simulation events in step 2, configuring each simulation event and the message data between simulation events.

[0010] Optionally, in the simulation verification method of avionics system based on model as described above, the step 2 comprises:

[0011] Step 21, selecting an algorithm model required for simulation verification of each object subsystem, and adaptively modifying the algorithm model according to a hierarchy to which each object subsystem belongs;

[0012] Step 22, providing the tool plug-in in the form of a tool plug-in according to an integration tool of different object subsystem-algorithm models to the collaborative simulation platform, so that the collaborative simulation platform configures the tool plug-in selected by each object subsystem in the avionics system;

[0013] Step 23, displaying a dependency view of each object subsystem by a GEF graphical modeling method, so as to match simulation events and obtain cross-linking relationships of the simulation events.

[0014] Optionally, in the simulation verification method of the model-based avionics system, the step 2 further includes:

[0015] Step 24, if a new tool plug-in is generated based on a new object subsystem-algorithm model, identifying the new tool plug-in, calling an interface function provided by the new tool plug-in, and connecting the new tool plug-in to the collaborative simulation platform.

[0016] Optionally, in the simulation verification method of the model-based avionics system, the adaptive modification method of the algorithm model in the step 21 includes:

[0017] Step 21a, modifying a tree structure of an engineering package of the algorithm model selected by each object subsystem;

[0018] Step 21b, creating a state diagram of a functional module in each object subsystem, and completing analysis of simulation events by searching the state diagram of each functional module.

[0019] Optionally, in the simulation verification method of the model-based avionics system, the step 22 includes:

[0020] Each functional module in each object subsystem is encapsulated into a functional plug-in, and integrated data, reading and analysis of data, and event configuration operations are performed in each functional plug-in.

[0021] Optionally, in the simulation verification method of the model-based avionics system, the matching of the simulation events in the step 23 includes:

[0022] Matching cross-linking relationships of each simulation event in each object subsystem;

[0023] Matching cross-linking relationships of simulation events between different object subsystems.

[0024] Optionally, in the model-based avionics system simulation verification method described above, step 3 includes:

[0025] Step 31: Each object subsystem on the transmission network configures the simulation events through the interconnection relationship of the simulation events, including stimulus configuration, event subscription configuration, and simulation event query.

[0026] Step 32: Configure the structure, interface, and services of message data through the adaptation interface of the transmission network, thereby providing a configuration that meets the requirements of avionics system co-simulation.

[0027] Optionally, in the model-based avionics system simulation verification method described above, step 31, configuring simulation events, includes:

[0028] Configuration 1: The master node of the collaborative simulation platform collects simulation events from the adapter nodes that need to participate in the simulation.

[0029] Configuration 2: In the simulation run configuration interface of the master control node, configure the trigger conditions of each object subsystem-algorithm model in the avionics system through connection, and send the trigger conditions to each adapter node;

[0030] Configuration 3: After receiving the triggering conditions sent by the master control node, each adapter node executes the trigger simulation event; wherein, the adapter node is each object subsystem in the avionics system.

[0031] Optionally, in the model-based avionics system simulation verification method described above, step 32, configuring the message data, includes:

[0032] On top of the message sending and receiving service interface, another layer is encapsulated, adding different logic judgment code.

[0033] The beneficial effects of this invention are as follows: This invention proposes a model-based simulation verification method for avionics systems. Based on specific avionics system design scenarios and considering the collaborative simulation characteristics of avionics systems, this method constructs a low-level simulation protocol transmission network using the DDS communication protocol. Through various network transmission methods of the transmission network, it utilizes the GEF graphical modeling method to provide distributed management functions for simulation configuration. Based on the transmission network constructed in step 1, and according to the interconnection relationships of simulation events in step 2, it configures each simulation event and the message data between simulation events, thereby forming a simulation event publish-subscribe standard and decoupling the mutual incentive configurations between multiple tools and models. Compared with the prior art, the technical solution provided by this invention has the following beneficial effects:

[0034] (1), the application utilizes GEF graphical modeling technology and OSGi framework technology on the Eclipse RCP platform framework, adopts the MBSE methodology to analyze and verify each simulation node element of the avionics system, and has the beneficial effects of realizing the joint simulation verification of the avionics system model and the algorithm software across layers and between models.

[0035] (2), the application selects the interaction relationship between each subsystem and the internal function structure through the simulation demand analysis of the avionics system, and has the beneficial effects of realizing the configuration requirements combined with the actual design scene and considering the task demand.

[0036] (3), the application uses the model-based avionics system algorithm software simulation verification method, and faces each avionics subsystem involving complex algorithm models, makes up for the lack of high-level system logic verification of pure algorithm models, and enhances the width and depth of system model verification. BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings are used to provide a further understanding of the technical scheme of the application, and constitute a part of the specification, and are used to explain the technical scheme of the application together with the embodiments of the application, and do not constitute a limitation on the technical scheme of the application.

[0038] Figure 1 A flowchart of a model-based avionics system simulation verification method provided by the embodiment of the application is shown in the figure.

[0039] Figure 2 A process schematic diagram of simulation configuration distributed management function provided by the GEF graphical modeling method in the embodiment of the application is shown in the figure.

[0040] Figure 3 A schematic diagram of the OSGi technical framework used by the model-based avionics system algorithm software simulation verification method in the embodiment of the application is shown in the figure.

[0041] Figure 4 A schematic diagram of the model-based avionics system algorithm software simulation verification control function in the embodiment of the application is shown in the figure. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical scheme and advantages of the application more clear, the embodiments of the application will be described in detail below with reference to the drawings. It should be noted that the embodiments and features in the embodiments in the application can be combined with each other in any way without conflict.

[0043] The steps shown in the flowchart of the drawings can be executed in a computer system such as a group of computer executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0044] In view of the verification limitation in the current model-based avionics system design process, the embodiment of the present application provides a simulation verification method of an avionics system supporting corresponding algorithm software, which is used to solve the problem of logic verification and algorithm data mismatch in the case of collaborative simulation of each subsystem model of the avionics system, so as to be suitable for actual subsystem design, and further obtain the collaborative simulation verification result and specification of each model between subsystems.

[0045] The following specific embodiments provided by the present application can be combined with each other, and the same or similar concepts or processes can not be described in some embodiments.

[0046] Figure 1 A flowchart of a simulation verification method of a model-based avionics system provided by the embodiment of the present application. The simulation verification method of the model-based avionics system provided by the embodiment of the present application can include the following steps:

[0047] Step 1, a DDS communication protocol is used to construct a bottom layer simulation protocol transmission network, and the construction of the bottom layer simulation protocol transmission network in this step includes the following contents, for example:

[0048] A DDS communication interface is built, and a DDS transmission mode is configured, for example, a publish-subscribe mode.

[0049] Step 2, a simulation configuration distributed management function is provided by using a GEF graphical modeling method through various network transmission modes of the transmission network.

[0050] In an implementation manner of the embodiment of the present application, the specific implementation process of step 2 can include the following steps:

[0051] Step 21, an algorithm model required for simulation verification of each object subsystem is selected, and the algorithm model is adaptively modified according to the level to which each object subsystem belongs;

[0052] Step 22, an integration tool plug-in of different object subsystem-algorithm models is provided in the form of a tool plug-in to a collaborative simulation platform, so that the collaborative simulation platform is configured with the tool plug-in selected by each object subsystem in the avionics system.

[0053] Step 23, a GEF graphical modeling method is used to display a dependency view of each object subsystem, match simulation events, and obtain the cross-linking relationship of each simulation event.

[0054] The specific implementation manner of matching simulation events in step 23 can include: matching the cross-linking relationship of each simulation event in each object subsystem; and matching the cross-linking relationship of simulation events between different object subsystems.

[0055] For example, Figure 2As shown in the figure, it is a process diagram for providing simulation configuration distributed management function by using GEF graphical modeling mode in the embodiment of the application, Figure 2 Specifically, the resource interlinking in the modeling process of step 2 includes simulation event interlinking and data message interlinking.

[0056] In another implementation manner of the embodiment of the application, step 2 further includes an optional step. If there is a new object subsystem, a new tool plug-in is generated by the newly created algorithm model. The new tool plug-in can be identified by using OSGi technology, and an interface function provided by the tool plug-in is called, so that the new tool plug-in is connected to the collaborative simulation platform.

[0057] Step 3: Based on the transmission network constructed in step 1, the simulation events and the message data between the simulation events are configured according to the interlinking relationship of the simulation events in step 2.

[0058] The specific implementation manner of step 3 includes the following steps.

[0059] Step 31: The object subsystems distributed on the transmission network perform excitation configuration, event subscription configuration, event query and the like on the simulation events through the network topology relationship (i.e. the interlinking relationship of the simulation events).

[0060] Step 32: The structure, interface and service of the message data are configured through the adaptation interface of the transmission network, and the configuration (for example, adaptation service) meeting the demand of the avionics system collaborative simulation is provided.

[0061] Preferably, in one implementation manner of the embodiment of the application, the specific implementation manner of the adaptation modification of the algorithm model in step 21 can include:

[0062] Firstly, the engineering package structure of the selected algorithm model of each object subsystem is modified to ensure that the model can be accurately parsed. Secondly, the parsing of the simulation events in the algorithm model is searched through the state diagram of each functional module. In the engineering, each functional module needs to create a state diagram except the upper system. This step is to create a state diagram for each functional module in the object subsystem, and the simulation events are parsed by searching the state diagram of each functional module.

[0063] According to the interlinking relationship between the object subsystems, the engineering package corresponding to each object subsystem needs to define the simulation events sent to the Socket (Socket is a calling function of an interface in DDS). The specific implementation manner of defining the engineering package to send the simulation events to the Socket is to add event simulation definition code in the state entry operation of sending the simulation events to the external subsystem. On the simulation event receiving mode, the trigger (Trigger) form needs to exist on the state transition (Transition).

[0064] Preferably, in an implementation manner of the embodiment of the present application, the implementation process of the step 22 can include:

[0065] Each functional module in each object subsystem is encapsulated into a functional plug-in, and integrated data, reading and parsing data, event configuration and other operations are performed in each functional plug-in.

[0066] In the implementation, the implementation manner of encapsulating the functional module into the functional plug-in is that the plug-in manner is designed based on the Eclipse RCP platform framework, the plug-in mechanism of Eclipse is a light software componentization architecture, and in the patent, the functional plug-in is used to provide all functions.

[0067] In the use process of the functional plug-in, the plug-in interface needs to be implemented, the plug-in is placed into the simulation verification environment of the avionics system, the imported functional plug-in can be used immediately, and additional configuration is not needed, and the multi-model simulation efficiency is improved.

[0068] The integration of the functional plug-in is assisted by the OSGI framework, when a new tool plug-in is integrated, the implemented plug-in interface is an implementation under the OSGI framework, and the interface can be acquired and the method therein can be called without relying on the package manner through the OSGI framework.

[0069] Preferably, in an implementation manner of the embodiment of the present application, the matching of the simulation events in the step 23 includes matching the cross-linking relationship of each simulation event in each object subsystem and matching the cross-linking relationship of the simulation events between different object subsystems. The implementation process of the step 23 can include:

[0070] In order to facilitate the expansion of the plug-in participating in the simulation, the Eclipse RCP platform framework is selected as the overall framework of the collaborative simulation platform, the plug-in mechanism of Eclipse is a light software componentization architecture. On the client platform, Eclipse uses the functional plug-in to provide all functions, for example, Rhapsody 8.2 is adapted at present, and in the subsequent use process, it is found that Rhapsody 8.3 also participates in the collaborative simulation scenario, and then the Rhapsody 8.3 is encapsulated into a plug-in to implement the adaptation interface.

[0071] Preferably, in one implementation of the embodiment of the present application, before the simulation events are configured in step 31, all object subsystems participating in the simulation run are displayed in the interface of the collaborative simulation platform, and the connection state of the main control node (the control node of the collaborative simulation platform) and the adaptation node (the object subsystem of the avionics system) is displayed on the connection line. When the main control node and the adaptation node are being connected, the connection line displays connection. When the main control node and the adaptation node are disconnected, the connection line displays disconnection. When the main control node and the adaptation node are not connected, the simulation run cannot be executed, and a disconnection notification of the adaptation node is popped up.

[0072] Preferably, in one implementation of the embodiment of the present application, in steps 31 and 32, based on the above display form of the cross-linking relationship of the object subsystems displayed in the interface of the collaborative simulation platform, the simulation events and the configuration of the message data in the simulation events are configured in the following manner:

[0073] During the configuration and running of the collaborative simulation, simulation event triggering and data transmission need to be interacted between the main control node and the adaptation node through the message sending mode. When the message receiving and sending service is designed, a set of core classes based on the message receiving and sending need to be defined. The role of the core classes is to uniformly define the interface of the receiving and sending service. Different transmission services need to implement the core classes. When different transmission service modes are switched, the software only needs to load the corresponding transmission service through OSGI at the start time, and the message receiving and sending function can be performed without changing any code.

[0074] The simulation verification method for the avionics system based on the model provided by the embodiment of the present application constructs a bottom simulation protocol transmission network by using the DDS communication protocol according to the specific avionics system design scene and considering the collaborative simulation characteristics of the avionics system; provides simulation configuration distributed management functions by using the GEF graphical modeling mode through various network transmission modes of the transmission network; configures the simulation events and the message data between the simulation events according to the cross-linking relationship of the simulation events in step 2, so as to form a simulation event publishing and subscribing standard and decouple the mutual excitation configuration between multiple tools and models. Compared with the prior art, the technical scheme provided by the present application has the following beneficial effects:

[0075] (1) The present application uses the GEF graphical modeling technology and the OSGI framework technology on the Eclipse RCP platform framework, adopts the MBSE method to analyze and verify the simulation node elements of the avionics system, and has the beneficial effect of realizing the joint simulation verification of the avionics system model and the algorithm software across layers and across models.

[0076] (2), the application selects the interaction between each subsystem and the internal function structure through the avionics system simulation demand analysis, and has the beneficial effects of realizing the configuration requirements of the actual design scene and considering the task demand.

[0077] (3), the application based on the model of the avionics system algorithm software simulation verification method, in the face of each avionics subsystem involving complex algorithm model, makes up for the lack of high-level system logic verification of pure algorithm model, and enhances the width and depth of system model verification.

[0078] Further, with the iterative application of the aircraft platform, the avionics system tends to be complex in the design process, and more emphasis is placed on the collaborative and efficient operation of each system. The embodiment of the application can be practically applied to the forward design process of the avionics system, and meet the use demand of the current avionics system multi-model collaborative simulation. For the joint operation of the system multi-model, the rationality of the system model design is verified; for the joint operation of the system and the aircraft / system model, the system model is verified to meet the demand of the upper model; for the joint operation of the system and the subsystem model, the rationality of the system model distribution demand is verified. In the face of each avionics subsystem involving complex algorithm model, the model-based avionics system algorithm software simulation verification method makes up for the lack of high-level system logic verification of pure algorithm model, and enhances the width and depth of system model verification. Therefore, the technical scheme provided by the embodiment of the application is very necessary and meaningful, and the technical scheme of the application has broad market prospect and obvious economic benefit.

[0079] The implementation of the simulation verification method of the model-based avionics system provided by the embodiment of the application is described in detail below through some specific embodiments.

[0080] The simulation verification method of the model-based avionics system provided by the specific embodiment obtains the optimal configuration method of the collaborative simulation between the avionics system model and the algorithm software through task demand analysis. The method specifically specifies the task scene, considers the function interaction of the subsystems under the avionics system, and obtains the logic-algorithm collaborative simulation result of the final avionics system through the GEF graphical modeling technology.

[0081] Specifically, the model-based avionics system algorithm software simulation verification method provided by the specific embodiment includes the following steps:

[0082] Step 1, select the simulation verification model required by the object aircraft avionics system / subsystem, and adaptively modify the model according to the different levels (system model / subsystem model).

[0083] Step 2, the integration tool plug-in for the avionics system / Matlab algorithm model is provided to the collaborative simulation platform in the form of a service, and the tool plug-in participating in the simulation is configured. This includes the basic information of the tool with the function of displaying the simulation, the running parameters, and the provision of each node capable of configuring one or more simulation tools, and the events can be configured below the node.

[0084] Step 3, the dependency relationship view of each sub-node model under the avionics system is displayed through the GEF graphical modeling technology, and the simulation events are matched. The newly developed adaptive plug-in is identified by using the OSGi technology, and the interface function provided by the adaptive plug-in is called. The algorithm software result in Matlab is bound with the transmission event of the HarmonySE model.

[0085] Step 4, each node of the avionics system distributed on the network configures, subscribes, and queries events through network topology. At the same time, the simulation control engine triggers the corresponding events according to the event triggering call relationship.

[0086] Step 5, the avionics system simulation verification calls the message transmission service core class implementation by calling the service interface class, obtaining the service interface class and the event class method.

[0087] In the specific embodiment, the avionics system level model in step 1 is generally designed in a decoupled manner. Taking the Harmony-SE method as an example, the scenes that the system may use are divided into use cases, forming each segment in the use process of the system, and the segment is described. The decoupled manner can greatly improve the simplicity of system analysis, and can cover the functions of the system to part of the requirements. However, for a complex system, on the one hand, if the model engineering is comprehensively structured, the workload is very large, and in the implementation process, it is impossible to avoid retaining the white box expansion form of each module of the system in each use case, and the function of the module is integrated by manual combing to obtain the comprehensive body; on the other hand, it is difficult for use cases to be completely decoupled, in other words, there is still a situation of mutual use of resources between use cases, and it is impossible to directly integrate the system architecture under the condition that the resource scheduling design between use cases is normal, so as to expose the possible resource design risks, such as Figure 2 as shown.

[0088] The algorithm software and use case model collaborative simulation work at the avionics system level can complete the rationality of resource scheduling between use cases before the system is integrated, ensure the integrity and accuracy of the system module design in each use case, and ensure that the system has defined accurate and complete elements when integrated.

[0089] Step 2 In order to be able to configure the graphical dependency relationship of the algorithm software and engineering participating in the simulation and the nodes participating in the simulation, provide the entire topology relationship view, and display the input-output relationship structure diagram between various nodes. This step uses GEF graphical modeling technology to display the node dependency relationship view. In the graphical configuration interface, you only need to manually drag the corresponding model icon to create a model, and manually drag the connection line to associate different models. This greatly facilitates the user experience during use.

[0090] (1) Model layer

[0091] The model class function of GEF can be divided into figure drawing, attribute modification, data storage, node control, and canvas constraint, and abstract classes are created to separately implement these functions. Then, these abstract classes are inherited in the above order, and finally the implementation entity only needs to configure the parameters to be configured. A model class is ready. The corresponding abstract classes are as follows:

[0092] a. Figure drawing: FigureModel, mainly for setting some properties of figure display;

[0093] b. Attribute modification: PropertyModel, implements the display and modification functions of attributes, and can reflect the changes of attributes;

[0094] c. Element object: ElementModel, mainly for setting the position and size information of the figure;

[0095] d. Node object: NodeModel, can have child nodes, can be the end of the connection line, and provides search function;

[0096] e. Connection object: ConnectionModel, setting of source node, destination node, connection node position, etc. of connection line;

[0097] f. Data node object: DbNodeModel, data can be stored in the node object in the database, data storage and reading are controlled by DataModel class, and node constraint information storage and reading are controlled by ConstraintModel;

[0098] g. Data connection object: DbConnectionModel, data can be stored in the connection object in the database, data storage and reading are controlled by DataModel class, and line constraint information storage and reading are controlled by LineConstraint.

[0099] (2) Control layer

[0100] The most important layer is EditPart, as the Model layer, we also create a set of abstract classes EditPart for different Model.

[0101] These EditPart classes deal with the business logic in the corresponding model class, FigureModel class corresponds to AbstractFigureEditPart class, PropertyModel corresponds to AbstractPropertyEditPart class, ElementModel class corresponds to AbstractElementEditPart class, NodeModel class corresponds to AbstractNodeEditPart class, DbNodeModel class corresponds to AbstractDbNodeEditPart.

[0102] (3)View layer

[0103] View layer is mainly using Draw2d technology, the data of model layer is displayed, we define an interface "InodeFigure", to control the anchor position and loading position of the figure, for example:

[0104] "getNodeContainer()" method controls the position of the child element to be drawn;

[0105] "getNodeHeader()" method is used to control the calculation of the carrier of the figure;

[0106] "getFigureAnchor()" and "setFigureAnchor()" are control node object anchor point.

[0107] All figure classes implement this interface, which can facilitate figure control display, achieve the desired effect. Through the technical framework, in the avionics system algorithm software simulation verification, the error rate of basic GEF operation can be reduced.

[0108] As Figure 3 The figure shows the OSGi technical framework used in the model-based avionics system algorithm software simulation verification method in the embodiment of the application.

[0109] In OSGi system, services cannot exist in isolation, each service is subordinate and runs on the Bundle that provides the service. In order to provide services for other modules, the Bundle first registers the service in a service registry (Service Registry) provided by the OSGi framework, which is shared by all Bundles. When other Bundles use services, they only need to find the required services from the registry without directly interacting with the Bundle that provides the service, so they do not need to care about the source Bundle of the service, nor need to import the Bundle that provides the service or the Package it publishes.

[0110] In the model-based avionics system algorithm software simulation verification method, each model / algorithm software plug-in has an integratecomponent, and when the integratecomponent is loaded, the service registration interface is called to register with the execution platform service pool through an integratecomponent.xml file in XML format. Through the acquisition service interface, the calling service interface and the data interaction interface provided by the execution platform service pool, the tool integratecomponent is opened and closed, and the information of the tool software provided by the service provider is acquired. Among them:

[0111] BundleBase: as the common basis of the Bundle that provides services and uses services, it provides the interface class IIntegrationService;

[0112] BundleServiceUser: as a service consumer, it applies for the service of IIntegrationService from the OSGi framework at startup, and calls the methods therein;

[0113] BundleService: as a service provider, it can register and provide a service that implements the interface class IIntegrationService;

[0114] Service registry: saves all registered service objects and related information of BundleService in the system.

[0115] Step 3 of the embodiment includes:

[0116] On the basis of the configuration of each object subsystem of the avionics system, the graphical editing environment is used to parse the simulation tool data and operate through the event model. Mainly includes: attribute configuration, detection configuration.

[0117] The attribute configuration mainly selects the attributes of the corresponding entity through the tree structure generated by parsing the entity.

[0118] The detection configuration mainly configures the display state of the entity, for example, the object entity in a certain area is set to be displayed in a visible state when the object enters the specified area along the track, and becomes invisible after leaving the area.

[0119] When the simulation event configuration is completed, the data of the configured event is automatically saved to an xml file. The published event information is sent to the master node through the transmission module, and the master node receives the event configuration information transmitted by the adaptation node.

[0120] The event subscription configuration view design display model content is composed of a node model, a simulation tool model and an event model.

[0121] a, the node model: the node participating in the simulation is taken as the node model, and the node model displays the node type and node number;

[0122] b, the simulation tool model: the tool participating in the simulation is taken as the tool model, and the tool model displays the configuration information of the tool, mainly including the tool version and tool name;

[0123] c, the event model: the data parsed by the collaborative simulation tool is taken as the event model.

[0124] The avionics system model event in node 1 and the algorithm software event in node 2 in the event subscription configuration view can be triggered. The events are associated through the connection. The association of the events is divided into two kinds:

[0125] 1) one-to-one, the simulation event of the function model is connected to the Matlab algorithm event in a one-to-one manner.

[0126] 2) one-to-many, the simulation event of the function model is connected in a one-to-many manner. For example, in the event subscription configuration view, the connection trigger mode of event 1 in the navigation subsystem model of the avionics system and event 3 and event 4 in the Matlab navigation algorithm.

[0127] Preferably, step 4 of the embodiment comprises:

[0128] The main control adaptation node mainly sends the simulation process control instructions in the simulation running process. Figure 4 As shown in the figure, it is a schematic diagram of the control function of the model-based avionics system algorithm software simulation verification in the embodiment of the application.

[0129] The master node sends a control message (the control message mainly has message types such as start, pause and stop), and the adaptation node receives the control message sent by the master node, parses the control content according to the message, and controls the corresponding object subsystem-algorithm model of the adaptation node to perform start, pause and stop operations.

[0130] The simulation event trigger flow of the simulation control engine (i.e. the configuration mode of the simulation event) is as follows:

[0131] 1. The master node collects simulation events that need to participate in simulation running on the adaptation node through the control engine;

[0132] 2. In the simulation running configuration interface of the master node, the user configures the trigger condition of each object subsystem-algorithm model in the avionics system through the connection;

[0133] 3. After the master node completes the simulation event trigger relationship configuration, the master node then sends the trigger condition of each object subsystem-algorithm model in the avionics system to the adaptation node through the control engine;

[0134] 4. The adaptation node receives the event trigger condition sent by the master node and prepares to execute the triggered simulation event.

[0135] Preferably, step 5 of the embodiment includes:

[0136] During the avionics system simulation configuration and running process, event triggering, data transmission, etc. all need to be interacted between the master node and the adaptation node through the message sending mode. In order to ensure the correctness of the data received between different nodes, the message data format needs to be followed according to the needs of the simulation event:

[0137] The composition of a message data is as follows:

[0138] 1) Start symbol

[0139] The identifier of the start of the message;

[0140] 2) Check bit

[0141] The check bit of the message, used to judge whether the message format is correct;

[0142] 3) Length

[0143] The total length of the message;

[0144] 4) Message type

[0145] Represent the type of the message:

[0146] 5) Data

[0147] Different message types store different data, and the message types include the following messages:

[0148] 5.1 Heartbeat message;

[0149] 5.2 Network connection message;

[0150] 5.3 Avionics system model event message;

[0151] 5.4 Avionics system model simulation data message;

[0152] 5.5 Matlab event message;

[0153] 5.6 Matlab simulation data message;

[0154] 5.7 End character.

[0155] In order to enable the message data of the encapsulated simulation event to be transmitted between subsystems, a layer needs to be encapsulated again on the basis of the message transceiving service interface, different functions add different logical judgment codes when implementing the network adaptation interface, direct operation of the message transceiving interface is prevented, and the coupling of logical judgment and message transceiving is reduced. The network adaptation interface realizes the sending and receiving of messages by calling the TCP and UDP type transmission modules of the message transceiving service through OSGI.

[0156] Although the embodiments of the present application are disclosed as above, the content described is only the embodiments adopted for the purpose of facilitating the understanding of the present application, and is not intended to limit the present application. Any modification and change in the form and details can be made by any person skilled in the art without departing from the spirit and scope of the present application, and the patent protection scope of the present application shall be subject to the scope defined by the appended claims.

Claims

1. A method for simulation verification of a model-based avionics system, characterized in that, The application comprises the following steps: Step 1, constructing a bottom simulation protocol transmission network by using a DDS communication protocol; Step 2, providing a simulation configuration distributed management function by using a GEF graphical modeling method through various network transmission modes of the transmission network; Step 3, configuring each simulation event and the message data between the simulation events according to the cross-linking relationship of the simulation events based on the transmission network constructed in step 1 and according to step 2. The step 2 comprises the following steps: Step 21, selecting an algorithm model required for simulation verification of each object subsystem, and adaptively modifying the algorithm model according to the level to which each object subsystem belongs; Step 22, providing the tool plug-in in the form of a tool plug-in to the collaborative simulation platform according to the integration tool plug-in of different object subsystem-algorithm models, so that the collaborative simulation platform configures the tool plug-in selected by each object subsystem in the avionics system; Step 23, displaying the dependency relationship view of each object subsystem by using the GEF graphical modeling method, thereby matching the simulation events and obtaining the cross-linking relationship of the simulation events; Step 24, if a new tool plug-in is generated based on a new object subsystem-algorithm model, identifying the new tool plug-in, calling the interface function provided by the new tool plug-in, and connecting the new tool plug-in to the collaborative simulation platform; The step 3 comprises the following steps: Step 31, configuring the simulation events by each object subsystem on the transmission network through the cross-linking relationship of the simulation events, including excitation configuration, event subscription configuration and simulation event query; Step 32, configuring the structure, interface and service of the message data through the adaptive interface of the transmission network, thereby providing the configuration meeting the collaborative simulation demand of the avionics system; The step 31 of configuring the simulation events comprises the following configurations: Configuration 1, the master node of the collaborative simulation platform collects the simulation events required for participating in the simulation running on the adaptive node; Configuration 2, the trigger condition of each object subsystem-algorithm model in the avionics system is configured through the simulation running configuration interface of the master node, and the trigger condition is sent to each adaptive node; Configuration 3, after each adaptive node receives the trigger condition sent by the master node, the trigger simulation event is executed; wherein the adaptive node is each object subsystem in the avionics system.

2. The method of claim 1, wherein, The method of adaptively modifying the algorithm model in the step 21 comprises the following steps: Step 21a, modifying the tree structure of the engineering package of the algorithm model selected by each object subsystem; Step 21b, creating a state diagram of each functional module in each object subsystem, and completing the analysis of the simulation events by searching the state diagram of each functional module.

3. The method of claim 1, wherein, The step 22 comprises the following steps: Each functional module in each object subsystem is encapsulated into a functional plug-in, and integrated data, reading and analysis data and event configuration operations are performed in each functional plug-in.

4. The method of claim 1, wherein, The step 23 of matching the simulation events comprises the following steps: Matching the cross-linking relationship of each simulation event in each object subsystem; Matching the cross-linking relationship of the simulation events between different object subsystems.

5. The model-based simulation verification method for avionics system according to any one of claims 1-4, characterized in that, The step 32 of configuring the message data comprises the following steps: Encapsulate a layer on the basis of the messaging service interface, and add different logical judgment codes.

Images