Joint simulation method for driving other models through MBSE model based on FMI protocol

Abstract

The invention discloses a joint simulation method for driving other models through an MBSE model based on an FMI protocol, and particularly relates to the field of multi-model joint simulation, and the method comprises a general layer model management module which is established on an MBSE system so as to drive other models which originally run on the MBSE system to carry out joint simulation; and the FMU file management module is used for converting the other models into FMU files, importing the FMU files into the joint simulation module in the MBSE modeling tool, driving the other FMU models to dynamically simulate in real time by using the MBSE model, and displaying simulation results. According to the method, firstly, a general layer model is established based on an MBSE system modeling tool, secondly, other models are packaged into an FMU file, then the FMU file is imported into an FMU file module, and finally, multi-model joint simulation is carried out, so that the purpose that the MBSE model drives other models to carry out simulation based on an FMI protocol, and multi-model joint simulation is completed is achieved.

Description

Technical Field

[0001] The present invention relates to the field of multi-model joint simulation, and in particular to a joint simulation method for driving other models with an MBSE model based on an FMI protocol. Background Art

[0002] The simulation tools used by different units and departments are incompatible with each other, resulting in the fragmentation of simulation tools. This makes it difficult to reuse models and increases the workload of repeated modeling in different software. At the same time, universality and consistency cannot be guaranteed, which requires frequent switching of software platforms in forward design, and the workload of developing customized interfaces is too large, increasing manpower and material costs.

[0003] Therefore, a more effective way is needed to achieve effective data interaction among simulation models built in different fields, with different modeling methods and different modeling tools. Summary of the invention

[0004] The purpose of the present invention is to provide a joint simulation method based on the FMI protocol in which the MBSE model drives other models, so as to solve the above problems.

[0005] In order to achieve the above object, the present invention provides the following technical solutions:

[0006] A joint simulation method based on FMI protocol using MBSE model to drive other models, including:

[0007] An overall model management module is established on the MBSE system to drive other models running on the original MBSE system modeling to perform joint simulation;

[0008] FMU file management module, which is used to convert the other models into FMU files and import the FMU files into the MBSE modeling tool

[0009] The joint simulation module uses the MBSE model to drive other FMU models to perform real-time dynamic simulation and display the simulation results.

[0010] Preferably, the overall layer model management module constructs the MBSE model of the system, and the constructed MBSE model includes at least the following types: requirement model, architecture model, behavior model and constraint model, and the construction process will reserve data interfaces for interaction with other models.

[0011] Preferably, the MBSE modeling tool parses the imported FMU file, and the parsing includes parsing the file structure, attributes and interfaces to correctly understand and use the model information to construct a suitable MBSE model type.

[0012] Preferably, the FMU file management module encapsulates different simulation models of other different simulation platforms into standard FMU files based on the FMI protocol.

[0013] Preferably, the FMU file management module includes a file format parsing unit, a model mapping unit and a model conversion unit, and with the assistance of the above three units, other FMU files are converted into SysML models recognized by the MBSE modeling tool platform.

[0014] Preferably, the model mapping unit maps the elements in the parsed FMU file to corresponding elements in the SysML model, wherein the elements include functions, variables and interfaces.

[0015] Preferably, the model conversion unit constructs corresponding SysML model elements based on the model mapping relationship and retains the original logic and behavior.

[0016] Preferably, the joint simulation module uses the MBSE model to drive other simulation models for joint simulation, and its operation steps include:

[0017] S01, initializing the simulation of the MBSE model;

[0018] S02, confirming the start of simulation, and displaying the simulation data in the form of a curve graph or numerical value during the simulation process;

[0019] S03, simulation stops, joint simulation ends, and occupied cache is cleared.

[0020] In the above technical solution, the present invention provides a joint simulation method based on the FMI protocol to drive other models with the MBSE model, which has the following beneficial effects: it realizes the reuse of models, enables models from different fields to be integrated into a unified simulation environment in a standard manner for interaction, and improves the work efficiency of the R&D team. In addition, the above embodiment supports interdisciplinary simulation, and can integrate various parts of the system for comprehensive analysis, which helps to discover the mutual influence and potential problems between different parts. This can fully cover the life cycle of the system and further improve the quality and efficiency of system design. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0022] Figure 1 A module diagram provided for an embodiment of the present invention;

[0023] Figure 2 A flowchart provided for an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] like Figure 2 As shown, a joint simulation method based on the FMI protocol using an MBSE model to drive other models includes:

[0026] The overall model management module is built on the MBSE system to drive other models running on the original MBSE system modeling for joint simulation;

[0027] FMU file management module, which is used to convert other models into FMU files and import FMU files into MBSE modeling tools

[0028] The joint simulation module uses the MBSE model to drive other FMU models to perform real-time dynamic simulation and display the simulation results.

[0029] As an embodiment further provided by the present invention, the MBSE model of the system is constructed based on the overall layer model management module, and the constructed MBSE model includes at least the following types: requirement model, architecture model, behavior model and constraint model, and the construction process will reserve data interfaces for interacting with other models.

[0030] As another embodiment further provided by the present invention, the MBSE modeling tool parses the imported FMU file, and the parsing includes parsing the file structure, attributes and interfaces to correctly understand and use the model information to construct a suitable MBSE model type.

[0031] As another embodiment further provided by the present invention, the MU file management module encapsulates different simulation models of other different simulation platforms into standard FMU files based on the FMI protocol.

[0032] As another embodiment further provided by the present invention, the FMU file management module includes a file format parsing unit, a model mapping unit and a model conversion unit, and the above three units assist in converting other FMU files into SysML models recognized by the MBSE modeling tool platform.

[0033] The model mapping unit maps the elements in the parsed FMU file to the corresponding elements in the SysML model. The elements include functions, variables and interfaces.

[0034] The model conversion unit constructs the corresponding SysML model elements based on the model mapping relationship and retains the original logic and behavior.

[0035] As another embodiment further provided by the present invention, the joint simulation module uses the MBSE model to drive other simulation models for joint simulation, and its operation steps include:

[0036] S01, initializing the simulation of the MBSE model;

[0037] S02, confirming the start of simulation, and displaying the simulation data in the form of a curve graph or numerical value during the simulation process;

[0038] S03, simulation stops, joint simulation ends, and occupied cache is cleared.

[0039] In the above technology, the reuse of models is realized, so that models in different fields can be integrated into a unified simulation environment in a standard and standardized manner for interaction, thereby improving the work efficiency of the R&D team. In addition, the above embodiment supports interdisciplinary simulation, which can integrate various parts of the system for comprehensive analysis, and helps to discover the mutual influence and potential problems between different parts. This can fully cover the life cycle of the system and further improve the quality and efficiency of system design.

[0040] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0041] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1A device that provides the functions specified in a block or multiple blocks.

[0042] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0043] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0044] The present invention uses specific embodiments to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

[0045] The embodiments of the present application also provide a specific implementation of an electronic device capable of implementing all steps of the method in the above embodiments, and the electronic device specifically includes the following contents:

[0046] Processor, memory, communications interface and bus;

[0047] Wherein, the processor, memory, and communication interface communicate with each other via the bus;

[0048] The processor is used to call the computer program in the memory, and when the processor executes the computer program, all the steps in the method in the above embodiment are implemented.

[0049] The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps of the method in the above embodiments, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, all of the methods in the above embodiments are implemented.

[0050] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. Although the embodiment of this specification provides the method operation steps described in the embodiment or flow chart, more or less operation steps can be included based on conventional or non-creative means. The order of steps listed in the embodiment is only one way of executing the order of many steps, and does not represent the only execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. For the convenience of description, the above device is described by dividing it into various modules according to its functions. Of course, when implementing the embodiments of this specification, the functions of each module can be implemented in the same one or more software and / or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The present invention is described with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the process and / or box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0051] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may be in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts refer to the partial description of the method embodiment. In the description of this specification, the description of the reference term "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification.

[0052] In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradicting each other. The above is only an embodiment of the embodiment of this specification and is not intended to limit the embodiment of this specification. For those skilled in the art, the embodiment of this specification may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiment of this specification shall be included in the scope of the claims of the embodiment of this specification.

Claims

1. A joint simulation method based on FMI protocol using MBSE model to drive other models, characterized in that: include: An overall model management module is established on the MBSE system to drive other models running on the original MBSE system modeling to perform joint simulation; FMU file management module, which is used to convert the other models into FMU files and import the FMU files into the MBSE modeling tool The joint simulation module uses the MBSE model to drive other FMU models to perform real-time dynamic simulation and display the simulation results.

2. According to claim 1, a joint simulation method for driving other models with an MBSE model based on the FMI protocol, characterized in that: The overall layer model management module constructs the MBSE model of the system. The constructed MBSE model includes at least the following types: requirement model, architecture model, behavior model and constraint model, and the construction process will reserve data interfaces for interacting with other models.

3. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 1, characterized in that: The MBSE modeling tool parses the imported FMU file, and the parsing includes parsing the file structure, attributes and interfaces to correctly understand and use the model information to build a suitable MBSE model type.

4. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 1, characterized in that: The FMU file management module encapsulates different simulation models of other different simulation platforms into standard FMU files based on the FMI protocol.

5. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 1, characterized in that: The FMU file management module includes a file format parsing unit, a model mapping unit and a model conversion unit, and through the assistance of the above three units, other FMU files are converted into SysML models recognized by the MBSE modeling tool platform.

6. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 5, characterized in that: The model mapping unit maps the elements in the parsed FMU file to corresponding elements in the SysML model, wherein the elements include functions, variables and interfaces.

7. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 5, characterized in that: The model conversion unit constructs corresponding SysML model elements based on the model mapping relationship and retains the original logic and behavior.

8. The joint simulation method of using an MBSE model to drive other models based on the FMI protocol according to claim 1, characterized in that: The joint simulation module uses the MBSE model to drive other simulation models for joint simulation, and its operation steps include: S01, initializing the simulation of the MBSE model; S02, confirming the start of simulation, and displaying the simulation data in the form of a curve graph or numerical value during the simulation process; S03, simulation stops, joint simulation ends, and occupied cache is cleared.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the joint simulation method of using an MBSE model to drive other models based on the FMI protocol as described in any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the joint simulation method of using an MBSE model to drive other models based on the FMI protocol as described in any one of claims 1 to 6 are implemented.

Images