Spacecraft System Design and Analysis and Verification Method Based on MBSE and SpaceSim

Abstract

A method for designing, analyzing, and verifying a space system based on MBSE and SpaceSim relates to the field of space system engineering technology. To solve the technical problems existing in the prior art, in the existing space system engineering technology, there is a lack of the ability of system-level simulation, and the methods, processes, and criteria for the interoperability of tools to perform joint simulation of MBSE and discipline models are not clear. The technical solution provided by the present invention includes: defining a SpaceSim metamodel in a SysML model, and instantiating the metamodel to obtain a space system design model; converting the information required in the space system model into a form that can be transmitted through an interface and recognized by an external discipline tool, SpaceSim; storing the information calculated by SpaceSim into the space system model; and verifying other requirements of the space system SysML model according to the calculated data content stored in the space system model. A space system is obtained according to this model. It can be applied to the design, analysis, and verification work of a spacecraft system.

Description

Technical Field

[0001] It relates to the field of aerospace system engineering technology. Background Art

[0002] Space missions are a type of multidisciplinary complex missions, which are characterized by high risks and high costs at the same time. In the design of space missions and spacecraft, design teams will adopt systems engineering (SE) techniques to handle the complexity of the system itself. With the development of technology, the complexity and variability of the system are increasing day by day. Therefore, systems engineering must be continuously updated and the developed systems must be evaluated. Traditional systems engineering is based on a large number of scattered documents and can no longer meet the changes of the system. At present, SE is moving towards digital transformation and has formed model-based systems engineering (MBSE), which provides the possibility to address the challenges of SE and is gradually becoming the paradigm and principle of SE.

[0003] System analysis is a supporting process of systems engineering, aiming to confirm the system design scheme and support design decisions. Through system analysis, system engineers can select the most effective scheme under current conditions. Simulation is a means of quantitative system analysis and can predict the operation of the system in a real environment. In the aerospace field, modeling and simulation have long been applied to the detailed design of subsystems, such as specific disciplines like navigation, guidance, and control systems (GNC), thermal control systems, etc., but lack the ability to simulate at the system level. Simulation plays an important role in the design stage, especially when considering the complexity and high risk in the aerospace field.

[0004] As system design becomes more and more complex, design details are also discovered. System models are usually oriented towards top-level description and analysis and lack more detailed details. Specific discipline models are used for detailed design. These models correspond to different abstraction levels or different discipline perspectives respectively and are often heterogeneous. Therefore, building a tool chain for simulation to ensure the interoperability of data or models will become an important content in MBSE. Although current commercial MBSE software supports certain software integration capabilities, and there is currently a Functional Mock-up Interface (FMI) specification in the industry, for teams with the need to integrate self-developed discipline software, the methods, processes, and guidelines for strengthening the interoperability of tools to perform joint simulation of MBSE and discipline models are not clear. Through mapping, transformation, and interoperability technologies between heterogeneous model information, system engineers can connect these models, manage the consistency of information, and can perform high-fidelity joint analysis. This requires considering simulation capabilities as part of the architecture. Summary of the Invention

[0005] To solve the technical problems existing in the prior art, namely, in the existing aerospace system engineering technology, there is a lack of the ability of system-level simulation, and the methods, processes, and criteria for the interoperability of tools to perform co-simulation of MBSE and discipline models are not clear, the technical solution provided by the present invention is as follows:

[0006] A method for establishing the design and analysis verification of an aerospace system model based on MBSE and SpaceSim, the method comprising:

[0007] Defining a SpaceSim metamodel in a SysML model and instantiating the metamodel to obtain an aerospace system design model;

[0008] Converting the information required in the aerospace system model into a form that can be transmitted through an interface and recognized by an external discipline tool SpaceSim;

[0009] Storing the information calculated by SpaceSim into the aerospace system model;

[0010] Verifying other requirements of the aerospace system SysML model according to the calculated data content stored in the aerospace system model.

[0011] Furthermore, a preferred embodiment is provided, in which a SysML system model is written using the system modeling language SysML.

[0012] Furthermore, a preferred embodiment is provided, wherein the SysML model includes a system of interest model (SOI), a co-simulation module, and a UDP interface.

[0013] Furthermore, a preferred embodiment is provided, in which data interaction between the SysML model and SpaceSim is realized through the UDP interface.

[0014] Furthermore, a preferred embodiment is provided, which further includes: realizing the consistent transmission of the information through a preset data interaction interface and data stream.

[0015] Based on the same inventive concept, the present invention also provides an apparatus for establishing the design and analysis verification of an aerospace system model based on MBSE and SpaceSim, the apparatus comprising:

[0016] A module for defining a SpaceSim metamodel in the SysML model and instantiating the metamodel to obtain an aerospace system design model;

[0017] A module for converting the information required in the aerospace system model into a form that can be transmitted through an interface and recognized by an external discipline tool SpaceSim;

[0018] A module for storing the information calculated by SpaceSim into the aerospace system model;

[0019] A module for verifying other requirements of the aerospace system SysML model according to the calculated data content stored in the aerospace system model.

[0020] Based on the same inventive concept, the present invention also provides an aerospace system design and analysis verification method based on MBSE and SpaceSim, including:

[0021] A step of collecting aerospace system information;

[0022] A step of obtaining an aerospace system according to the aerospace system information through the obtained design model.

[0023] Based on the same inventive concept, the present invention also provides an aerospace system design and analysis verification device based on MBSE and SpaceSim, including:

[0024] A module for collecting aerospace system information;

[0025] A module for obtaining an aerospace system according to the aerospace system information through the obtained design model.

[0026] Based on the same inventive concept, the present invention also provides a computer storage medium for storing a computer program, and when the computer program is read by a computer, the computer executes the method.

[0027] Based on the same inventive concept, the present invention also provides a computer, including a processor and a storage medium, and when the processor reads the computer program stored in the storage medium, the computer executes the method.

[0028] The aerospace system design and analysis verification method based on MBSE and SpaceSim provided by the present invention realizes the transfer and interaction between the information required in the system model and external discipline tools by defining the data interaction interface and data flow. This can ensure that the parameters in the system model can be recognized and calculated by external tools, and the calculation results are passed back to the system model for further analysis. This way improves the accuracy and efficiency of system analysis.

[0029] The aerospace system design and analysis verification method based on MBSE and SpaceSim provided by the present invention standardizes the format and software information of the co-simulation module by defining a meta-model. This allows system engineers to quickly build co-simulation scenarios and obtain the required results without fully mastering external tools. This way improves the work efficiency of system engineers and the repeatability of co-simulation.

[0030] The aerospace system design, analysis and verification method based on MBSE and SpaceSim provided by the present invention enables system engineers to visually view and modify objects and parameters related to the current simulation through the GUI interface. Meanwhile, the GUI interface contains instructions for controlling the simulation, enabling system engineers to conveniently control operations such as the start, pause, and end of the co-simulation. This approach improves the interaction effect between system engineers and the co-simulation and the convenience of operation.

[0031] The aerospace system design, analysis and verification method based on MBSE and SpaceSim provided by the present invention realizes the connection and model conversion between the system model and external tools by defining the interfaces and data streams for data interaction. Compared with traditional system engineering methods, this solution provides a more efficient and accurate data transfer method, which can better support system analysis and decision-making.

[0032] The aerospace system design, analysis and verification method based on MBSE and SpaceSim provided by the present invention standardizes the formats and software information of the co-simulation modules by defining meta-models. Compared with other studies, this solution provides a more specific and reusable module library, enabling system engineers to more quickly construct co-simulation scenarios and obtain the desired results.

[0033] The aerospace system design, analysis and verification method based on MBSE and SpaceSim provided by the present invention provides an intuitive and user-friendly interface through the GUI interface, enabling system engineers to conveniently control and operate the co-simulation. Compared with other studies, this solution provides a more friendly and consistent user interface and can display all results in an integrated environment, improving the interaction effect between system engineers and the co-simulation and the convenience of operation.

[0034] The aerospace system design, analysis and verification method based on MBSE and SpaceSim provided by the present invention can be applied to the design, analysis and verification work of spacecraft systems. Brief Description of the Drawings

[0035] Figure 1 It is a schematic diagram of data flow and interfaces;

[0036] Figure 2 It is a schematic diagram of the data interaction sequence;

[0037] Figure 3 It is a schematic diagram of the SysML meta-model defining the SpaceSim co-simulation;

[0038] Figure 4 It is a schematic diagram of the co-simulation interface with a GUI. Detailed Implementation Manner

[0039] To make the advantages and benefits of the technical solution provided by the present invention more clearly reflected, the technical solution provided by the present invention will be further described in detail with reference to the accompanying drawings. Specifically:

[0040] Embodiment 1. This embodiment provides a method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim. The method includes:

[0041] Defining the SpaceSim metamodel in the SysML model and instantiating the metamodel to obtain the space system design model;

[0042] Converting the information required in the space system model into a form that can be transmitted through the interface and recognized by the external disciplinary tool SpaceSim;

[0043] Storing the information calculated by SpaceSim into the space system model;

[0044] Verifying other requirements of the space system SysML model according to the calculated data content stored in the space system model.

[0045] Embodiment 2. This embodiment further limits the method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim provided in Embodiment 1, and uses the system modeling language SysML to write the SysML system model.

[0046] Embodiment 3. This embodiment further limits the method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim provided in Embodiment 2. The SysML model includes the System of Interest (SOI) model, the co-simulation module, and the UDP interface.

[0047] Embodiment 4. This embodiment further limits the method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim provided in Embodiment 3, and realizes the data interaction between the SysML model and SpaceSim through the UDP interface.

[0048] Embodiment 5. This embodiment further limits the method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim provided in Embodiment 1, and further includes: realizing the consistent transmission of the information through a preset data interaction interface and data stream.

[0049] Embodiment 6. This embodiment provides a device for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim. The device includes:

[0050] Define the SpaceSim metamodel in the SysML model and instantiate the metamodel to obtain the modules of the aerospace system design model;

[0051] A module that converts the information required in the aerospace system model into a form that can be transmitted through the interface and recognized by the external disciplinary tool SpaceSim;

[0052] A module that stores the information calculated by SpaceSim into the aerospace system model;

[0053] A module that verifies other requirements of the aerospace system SysML model according to the calculated data content stored in the aerospace system model.

[0054] Embodiment 7. This embodiment provides an aerospace system design and analysis verification method based on MBSE and SpaceSim, including:

[0055] Steps to collect aerospace system information;

[0056] Steps to obtain the aerospace system according to the aerospace system information through the design model obtained in Embodiment 1.

[0057] Furthermore, steps to analyze and verify the aerospace system.

[0058] Specifically, this embodiment aims to integrate the team's self-developed orbital analysis tool SpaceSim with MBSE and conduct joint simulation, propose the interface and information flow of data processing and transmission, standardize the metamodel of joint simulation, control the model level of information interaction, the graphical user interface (GUI) of data control and display, and ensure that the user's operations are concentrated in the system modeling environment without the need to operate external analysis tools.

[0059] The method includes:

[0060] Interface and data flow of data processing and transmission: - Convert the information required in the system model into a form that can be transmitted through the interface and recognized by external disciplinary tools. - Transmit, store, and display the high-precision calculation results of external disciplinary tools in the MBSE tool. - Use the SysML model to define the system architecture, including requirements, structure, behavior, parameters, etc. - Use the joint simulation module to set the joint simulation scenario and process the data into appropriate instructions. - Use the UDP interface to transmit the instructions to SpaceSim and receive the results calculated by SpaceSim.

[0061] Meta-model for Specification Simulation: - Define the SpaceSim meta-model in the SysML model to support domain-specific modeling. - The meta-model follows the principles of hierarchical and loose coupling, encapsulating functions as reusable modules stored in a module library. - Define the attributes of the co-simulation scenario module, such as instructions, communication interfaces, software versions, etc. - Define the structure of the scenario module, including setting time, controlling data interaction, setting SpaceSim outputs, receiving data, etc. - Define the next layer of the scenario module, including defining the SpaceSim scenario and the SpaceSim function modules stored in the model library.

[0062] GUI Interface for Interaction with System Engineers: - Define the GUI interface in MBSE to automatically maintain consistency with the data in the SysML model. - The GUI interface contains instructions for controlling the SpaceSim co-simulation, such as start, pause, end, reset, etc. - Through the GUI interface, objects and parameters related to the current simulation can be visually viewed and modified. - The GUI interface includes predefined curve windows for plotting required data curves.

[0063] Through the above steps, the integration and co-simulation of MBSE and SpaceSim are achieved, unifying the model library and database, simplifying the co-simulation scenario, and providing a unified GUI interface for system engineers and other stakeholders to use.

[0064] Embodiment Eight. This embodiment provides a space system design and analysis verification device based on MBSE and SpaceSim, including:

[0065] A module for collecting space system information;

[0066] The design model obtained through Embodiment Six, and according to the space system information, obtain the modules of the space system.

[0067] Furthermore, modules for other requirements of the SysML model.

[0068] Embodiment Nine. This embodiment provides a computer storage medium for storing a computer program, and when the computer program is read by a computer, the computer executes the method provided in Embodiment One.

[0069] Embodiment Ten. This embodiment provides a computer, including a processor and a storage medium, and when the processor reads the computer program stored in the storage medium, the computer executes the method provided in Embodiment One.

[0070] Embodiment Eleven. Combining Figures 1-4 To illustrate this embodiment, this embodiment further describes the above-provided technical solutions in detail and completely through specific embodiments. Specifically:

[0071] Interface and data flow for data processing and transfer

[0072] In co-simulation, it is necessary to convert the information required in the system model into a form that can be transmitted through the interface and recognized by external disciplinary tools. At the same time, it is also necessary to transmit, store, and display the high-precision calculation results of external disciplinary tools in the system model.

[0073] The interface for data interaction is as Figure 1 shown, and the interaction sequence is as Figure 2 shown. Specifically, since the entire task architecture model is written in the System Modeling Language (SysML), it is called the SysML model. The SysML model includes the System of Interest (SOI) model - usually describing a specific space mission or aircraft system, a co-simulation module, and a UDP interface. The SOI model defines the architecture of the system, which usually includes requirements, structure, behavior, parameters, etc. In the system analysis of co-simulation, the parameters, as the required data, are transmitted to the co-simulation module. The co-simulation module mainly includes a series of modules for setting co-simulation scenarios, an instruction processing module for processing data into appropriate instructions, and a data receiving module for receiving data from SpaceSim. The more specific structure of the co-simulation module is described by the meta-model in the next section. The UDP interface in the SysML model is usually implemented in other languages supported by the MBSE modeling tool call tool, such as Java, Python, etc. The processed instructions are transmitted to SpaceSim through the UDP interface. SpaceSim generates a scenario model consistent with the SysML model according to the format defined by the instructions and calculates the corresponding results, which are transmitted to the data receiving module in the form of an array through the UDP interface. Depending on whether synchronous simulation or individual simulation is selected, the results calculated by SpaceSim can directly interact with the SOI model, or be stored in a table file and interact with the SOI model by reading the table. These calculation results can be used to specify some parameters of the SOI model, such as the satellite position at different times, or to specify the state of the satellite. Subsequently, the SOI model performs other co-analysis according to these results and its own defined behavior and parameters inside, such as: flow balance verification. These co-simulation-related data settings and simulation result displays are all shown through the GUI defined in the SysML model and interact with system engineers or other stakeholders, and are consistent with the entire SysML model.

[0074] Meta-model for standardizing simulation

[0075] Since co-simulation itself is also regarded as a system, the SpaceSim metamodel is defined in the SysML model to support domain-specific modeling. The metamodel follows the criteria of being hierarchical and loosely coupled. Additionally, functions are encapsulated as reusable modules stored in a module library. As Figure 3 shown. These features enable system engineers to quickly define or modify co-simulation modules in the SysML model and obtain the required results without being proficient in SpaceSim. Each co-simulation scenario module can be regarded as an instantiation of the metamodel. These metamodels and internal attributes usually do not directly interact with the attributes within the SysML model. The purpose of the metamodel is to guide how to construct co-simulation modules and standardize model information, such as model hierarchy, software version, and interfaces.

[0076] Figure 3 In , each co-simulation scenario module is given the 《SpaceSimAnalysis》 stereotype, and its attributes include formatted instructions to be sent, communication interfaces to ensure a consistent simulation environment, and software version information, etc. The co-simulation module mainly includes four structures and is defined at the second level, including the 《SpaceSimSetTime》 module for setting time, the 《ctrlDataInteractionActivity》 activity for controlling data interaction, the 《SpaceSimSetOutput》 module for setting SpaceSim output, and the 《receiveData》 module for receiving data. The next level below setting the output is the 《SpaceSimSetScene》 module for defining the SpaceSim scene. The 《SpaceSimSetScene》 module includes a directly reusable scene time module 《sceneTime》, a possible link time module 《chainTime》, and manually specified scene objects (SOIs, scene objects such as ground stations). In addition, 《SpaceSimSetOutput》 and 《SpaceSimSetScene》 also have a series of SpaceSim functional modules 《ssFunctionalBlock》 stored in the model library. These modules encapsulate each function into a directly usable module using constraint attributes and value attributes. System engineers only need to connect the corresponding parameters to implement the function. Additionally, a series of stereotypes for defining attributes are defined, and these attributes complete the co-simulation scenario. The basic functional modules and the ontology of the basic structure modules are all support reuse and are stored in the module library. The relevant constraint blocks are also stored in the constraint library.

[0077] The GUI interface for interacting with system engineers

[0078] Figure 4Displays the interface for the co - simulation of MBSE and SpaceSim. Among them, the MBSE model is exactly the same as the GUI data of SysML, and modifying either end can change the entire executing model. In the GUI, system engineers or other stakeholders can intuitively view and modify the objects and parameters related to the current simulation. The GUI should contain instructions for controlling the simulation, including starting, pausing, ending, resetting, etc. Inside the 《ctrlDataInteractionActivity》 activity, there is an activity diagram that further controls the simulation of the SpaceSim software according to the control instructions, including starting and generating scenarios, pausing, stopping, etc. These instructions are received by SpaceSim and displayed in the instruction window, while the calculation results are passed to the 《receiveData》 module to receive data. The GUI interface includes a predefined curve window that can plot the required data curves. Figure 4 Displays the timing curves of sun visibility and ground station visibility. In this way, the co - simulation of MBSE and SpaceSim can be achieved, and all operations are executed in the GUI.

[0079] The advantages of this method are:

[0080] A spacecraft system design, analysis, and verification method based on MBSE and SpaceSim, including defining the interfaces and data streams for data processing and transfer, standardizing the meta - model of the simulation and the GUI, and realizing the issues related to the co - simulation of MBSE and SpaceSim. Specifically, it includes:

[0081] The interfaces and data streams for data processing and transfer indicate how to convert the parameters of interest in the system model into an instruction format that meets the requirements of SpaceSim and can receive the calculation results of SpaceSim. These results can be further received by the system model in MBSE to perform other analyses, realizing a unified model library and database, and forming a single information source for model - centered systems engineering activities.

[0082] Standardizing the meta - model of the simulation enables the consistent definition of SpaceSim co - simulation modules in MBSE. This meta - model standardizes the module format and software information and encapsulates functions into a module library. This allows system engineers to quickly build a co - simulation scenario under MBSE and obtain the required results without fully mastering the SpaceSim tool.

[0083] The GUI interface based on SysML simplifies the co - simulation scenario and enables any participant to understand and control the co - simulation. This allows systems engineering analysis to be consistently understood and accepted. At the same time, unifying all information under one interface forms a systems engineering environment centered on MBSE.

[0084] The above further describes the technical solutions provided by the present invention through several specific embodiments to highlight the advantages and beneficial effects of the technical solutions provided by the present invention. However, the above several specific embodiments are not used as a limitation to the present invention. Any reasonable modifications and improvements to the present invention, combinations of embodiments, and equivalent replacements within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

[0085] In the description of this specification, it is only a preferred embodiment of the present invention and cannot be used to limit the scope of rights of the present invention; in addition, the description with reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic descriptions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or N embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples. In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In the description of the present invention, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined. Any process or method description shown in the flowchart or described in other ways herein can be understood to represent a module, segment, or part of code including one or more N executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of the present invention includes additional implementations, where the functions may be executed in a substantially simultaneous manner or in the reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present invention pertain. The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a sequenced list of executable instructions for implementing a logical function, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or in connection with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection part (electronic device) having one or N wirings, a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM).In addition, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation or, if necessary, other appropriate processing, and then stored in a computer memory. It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0086] Those of ordinary skill in the art can understand that all or part of the steps carried out in implementing the methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments. In addition, in each of the embodiments of the present invention, the functional units can be integrated into one processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. When the above integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

Claims

1. A method for establishing the design, analysis and verification of a space system model based on MBSE and SpaceSim, characterized in that The method includes: Defining the SpaceSim metamodel in the SysML model and instantiating the metamodel to obtain a space system design model; Converting the information required in the space system model into a form that can be transmitted through an interface and recognized by the external disciplinary tool SpaceSim; Storing the information calculated by SpaceSim into the space system model; Verifying other requirements of the space system SysML model according to the calculated data content stored in the space system model; The method of defining the SpaceSim metamodel in the SysML model lies in: Each co-simulation scenario module is given the stereotype "SpaceSimAnalysis", and its attributes include instructions in compliance with the format to be sent, communication interfaces and software version information to ensure the consistency of the simulation environment; The co-simulation module includes four structures and is defined as the second level, including the "SpaceSimSetTime" module for setting time, the "ctrlDataInteractionActivity" activity for controlling data interaction, the "SpaceSimSetOutput" module for setting SpaceSim output, and the "receiveData" module for receiving data; "SpaceSimSetOutput" and "SpaceSimSetScene" also include the SpaceSim functional module "ssFunctionalBlock" stored in the model library. The "ssFunctionalBlock" module encapsulates each function into a directly usable module using constraint attributes and value attributes; It also includes defining stereotypes of attributes, which are used to improve the co-simulation scenario. The basic functional modules and the basic structure module ontology both support reuse and are stored in the module library; the relevant constraint blocks are also stored in the constraint library.

2. The method for establishing the design, analysis and verification of a space system model based on MBSE and SpaceSim according to claim 1, wherein Writing the SysML system model using the system modeling language SysML.

3. The method for establishing the design, analysis, and verification of a space system model based on MBSE and SpaceSim according to claim 2, characterized in that The SysML model includes the system of interest model SOI, co-simulation module and UDP interface.

4. The method for establishing the design, analysis and verification of a space system model based on MBSE and SpaceSim according to claim 3, wherein Realizing the data interaction between the SysML model and spaceSim through the UDP interface.

5. The method for establishing the design, analysis and verification of the aerospace system model based on MBSE and SpaceSim according to claim 1, wherein It also includes: Realizing the step of keeping the transmission of the information consistent through a preset data interaction interface and data stream.

6. An apparatus for designing, analyzing, and verifying a space system model based on MBSE and SpaceSim, characterized in that, The device includes: A module for defining the SpaceSim metamodel in the SysML model and instantiating the metamodel to obtain a space system design model; A module for converting the information required in the space system model into a form that can be transmitted through an interface and recognized by the external disciplinary tool SpaceSim; A module for storing the information calculated by SpaceSim into the space system model; A module for verifying other requirements of the space system SysML model according to the calculated data content stored in the space system model; The method of defining the SpaceSim metamodel in the SysML model lies in: Each co-simulation scenario module is assigned the stereotype "SpaceSimAnalysis", which has attributes including formatted instructions to be sent, communication interfaces to ensure consistent simulation environments, and software version information; The co-simulation module consists of four structures and is defined at the second level, including the "SpaceSimSetTime" module for setting time, the "ctrlDataInteractionActivity" activity for controlling data interaction, the "SpaceSimSetOutput" module for setting SpaceSim output, and the "receiveData" module for receiving data; "SpaceSimSetOutput" and "SpaceSimSetScene" also include the SpaceSim functional module "ssFunctionalBlock" stored in the model library. The "ssFunctionalBlock" module encapsulates each function into a directly usable module using constraint attributes and value attributes; It also includes stereotypes for defining attributes, which are used to refine co-simulation scenarios. The basic functional modules and the basic structure module ontology both support reuse and are stored in the module library; the relevant constraint blocks are also stored in the constraint library.

7. A method for designing, analyzing, and validating a space system based on MBSE and SpaceSim, characterized in that, It includes: Steps for collecting space system information; Steps for obtaining a space system based on the design model obtained from claim 1 and the space system information.

8. An aerospace system design, analysis, and verification device based on MBSE and SpaceSim, characterized in that It includes: Modules for collecting space system information; Modules for obtaining a space system based on the design model obtained from claim 6 and the space system information.

9. A computer storage medium for storing a computer program, characterized in that, When the computer program is read by a computer, the computer executes the method described in claim 1.

10. A computer, comprising a processor and a storage medium, characterized in that, When the processor reads the computer program stored in the storage medium, the computer executes the method described in claim 1.

Images