MBSE-based satellite digital simulation model design method and system

Abstract

The invention provides a satellite digital simulation model design method and system based on MBSE. The satellite digital simulation model design method based on MBSE comprises the steps that overall preliminary design is carried out, sub-system model division of a satellite digital simulation model is determined, key problems existing in the model design process are recognized, special item division is carried out according to the key problems, and the relation between each special item and each sub-system model is analyzed; carrying out special design, carrying out multidisciplinary parallel special argumentation aiming at the whole satellite, and determining subsystem model composition, information flow and work flow of each special item; carrying out overall summary design, planning the requirements of each special item for each subsystem model, carrying out demand integration, constructing a subsystem model demand system, and defining main functions and interfaces; detailed design of a subsystem: implementing and developing detailed design of a model; and carrying out overall integration design, integrating each subsystem model into a whole satellite, and comprehensively judging the coverage to form a whole satellite digital model. The system has the characteristics of high flexibility, strong expansibility, full-life-cycle management and the like.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of simulation model design, in particular to a satellite digital simulation model design method and system based on MBSE. BACKGROUND

[0002] The current aerospace field is in a key stage of digital transformation. The satellite digital simulation model is an important content of the aerospace digital transformation. With the development of modeling and simulation applications at home and abroad in recent years, the satellite digital simulation model plays an important role in satellite system demonstration, satellite on-orbit test, satellite large system joint application and the like. The satellite digital simulation model development involves aerospace, control, communication and other disciplines, including overall design, subsystem design, system integration and the like, and has the characteristics of wide discipline involvement, complex process and strong coupling at the engineering level, and the characteristics of multiple levels, dynamic state change and complex calculation of discrete event dynamic simulation at the technical level. The design process needs to integrate the characteristics of the satellite engineering field and the modeling and simulation field, and therefore requires multi-disciplinary joint, cross-departmental collaboration and multi-application design methods. The MBSE-based methodology can comprehensively describe system requirements, functions, behaviors and the like by building and maintaining a unified and shared system model, and departments can carry out collaborative work based on the unified framework, so that comprehensive and systematic description and management of complex systems can be realized. The method has the characteristics of model-driven, full life cycle management, efficient collaboration and strong reusability, and is suitable for solving complex system engineering problems and meets the engineering requirements of satellite digital simulation model design. SUMMARY

[0003] In view of the defects in the prior art, the application aims to provide a satellite digital simulation model design method and system based on MBSE.

[0004] The satellite digital simulation model design method based on MBSE provided by the application comprises the following steps:

[0005] Step 1, overall preliminary design, defining the subsystem model division of the satellite digital simulation model, identifying the key problems existing in the model design process and performing special division accordingly, and analyzing the relationship between each special item and each subsystem model;

[0006] Step 2, special item design, carrying out multi-disciplinary parallel special item demonstration for the whole satellite, defining the subsystem model composition, information flow and work flow of each special item;

[0007] Step 3, overall summary design, coordinating the requirements of each special item for each subsystem model, carrying out requirement integration, constructing a subsystem model requirement system, and defining the main functions and interfaces;

[0008] Step 4, subsystem detailed design, model detailed design is carried out for implementation, including composition, interface, information flow, workflow and data structure;

[0009] Step 5, overall integrated design, integrating each subsystem model to the whole satellite, and comprehensively judging coverage to form the whole satellite digital model.

[0010] Preferably, the subsystem model division in step 1 refers to completing the subsystem division based on the field driving idea according to the overall function requirement, performance requirement and technical index of the satellite digital simulation model, analyzing the general requirement of each subsystem model to form the general subsystem model base class, and drawing the block definition diagram according to the general subsystem model base class; the general subsystem model base class encapsulates the properties or methods common to the default initialization file, configuration file and running component of the sub-model;

[0011] The special item division in step 1 refers to analyzing the key capabilities involved in the model design process from the three dimensions of physical simulation, information simulation and simulation control, drawing the capability requirement diagram according to the simulation basic requirement of the satellite digital simulation model; the physical simulation level is around the simulation capabilities of satellite machine, electricity, heat, motion, perception, task chain, time chain and precision chain; the information simulation level is around the simulation capabilities of telemetry, remote control, data transmission, inter-satellite, on-board task planning, on-board information processing and virtual-real interaction; the simulation control is around the model calling and running capability; according to the key capability division, the corresponding special item is divided, and the special item subsystem model base class is designed, which inherits from the general subsystem model base class;

[0012] The analysis of the relationship between each special item and each subsystem model in step 1 refers to analyzing the subsystem models related to each capability of the satellite digital simulation model, designing the related subsystem model base class under each special item, which inherits from the subsystem model base class of the special item, and drawing the block definition diagram accordingly.

[0013] Preferably, the step 2 of specifying the composition of the subsystem model of each special item refers to analyzing the subsystem models involved in the implementation of the simulation capability corresponding to the special item, further dividing the composition of each subsystem model from the simulation and business two angles, completing the function description of each composition, and drawing the block definition diagram;

[0014] The step 2 of specifying the information flow of each special item refers to analyzing the information flow transmitted between the related subsystem models, specifying the interface and data item, including the interface type, data item name, signal source and signal sink, and drawing the internal block diagram;

[0015] The step 2 of specifying the workflow of each special item refers to the workflow around the function implementation of each special item, specifying the working mode and switching condition, drawing the state machine diagram; specifying the work items, execution order and information transmitted between different work items between each sub-model in the function implementation process, and drawing the activity diagram.

[0016] Preferably, the requirement integration in step 3 refers to organizing the requirements of each subsystem model of each special item, abstractly classifying, analyzing the dependency relationship and conflict points between the requirements, and solving the contradictions between the requirements, and clarifying the priority of the requirements, constructing a complete, consistent and traceable requirement system for each subsystem model, completing the black box design of each subsystem model, including the function and interface design, forming the subsystem model base class in the overall conceptual design stage, the subsystem model base class in this stage inherits the subsystem model base class in all related special item designs, and the block definition diagram is drawn according to the subsystem model base class.

[0017] Preferably, the composition and interface design of the model in step 4 refers to inheriting the subsystem model base class in the overall conceptual design stage, completing the function module division and interface sorting of the implementation-oriented subsystem model, drawing the BDD diagram, and at the same time, completing the function description of each module from the simulation implementation point of view, including the input, output and mathematical principle of each function;

[0018] The information flow design of the model in step 4 refers to the data processing flow and information transmission path of the subsystem, clarifying the data input, processing, output and storage links of each module, and analyzing the source, destination and processing method of data in each key link, so as to clarify the flow direction of data between the modules in the subsystem model and between the internal modules and external models, and draw the internal block diagram according to the flow direction of data between the modules in the subsystem model and between the internal modules and external models;

[0019] The workflow design of the model in step 4 refers to the flow around the function implementation of the subsystem, clarifying the working mode and switching condition, and drawing the state machine diagram; at the same time, analyzing the physical principle of the subsystem work, clarifying the main business activities and the data flow and control flow between the activities, and drawing the activity diagram;

[0020] The data structure design of the model in step 4 refers to designing one or more classes for each function or module according to the results of the function composition analysis, clarifying the attributes, methods and relationships between the classes according to the function requirements, information flow and activity analysis, and drawing the class diagram, and clarifying the data structure of the transmitted information between the modules in this stage, which is used to guide the development of the subsystem model.

[0021] Preferably, the integration of each subsystem model into the whole satellite in step 5 refers to collecting the detailed design models of each subsystem, integrating the technical route and detailed scheme of each sub-model into the whole satellite model, and drawing the BDD diagram;

[0022] The comprehensive judgment coverage in step 5 refers to establishing a demand satisfaction matrix of the subsystem detailed model to the overall summary design model, the special design model and the overall preliminary design model, verifying whether the function module composition, interface, information flow, work flow and data structure in the collected subsystem detailed model can cover the subsystem function composition and interface requirements proposed in the overall summary design stage; whether the subsystem function composition, interface, information flow and work flow requirements proposed in each special design can be covered, and whether each subsystem can be organically matched to realize each special capability; whether the simulation requirements of the whole satellite simulation control layer, the physical layer and the information layer proposed in the overall preliminary design can be covered, and finally forming a demand satisfaction table.

[0023] According to the satellite digital simulation model design system based on MBSE provided by the application, the system comprises:

[0024] Module M1, overall preliminary design, clearly divides the subsystem model of the satellite digital simulation model, identifies the key problems existing in the model design process and performs special division accordingly, and analyzes the relationship between each special item and each subsystem model;

[0025] Module M2, special design, carries out multidisciplinary parallel special argumentation for the whole satellite, clearly divides the subsystem model composition, information flow and work flow of each special item;

[0026] Module M3, overall summary design, coordinates the requirements of each special item to each subsystem model, carries out demand integration, constructs a subsystem model demand system, and clearly divides the main function and interface;

[0027] Module M4, subsystem detailed design, carries out detailed design of the model for implementation, including composition, interface, information flow, work flow and data structure;

[0028] Module M5, overall integrated design, integrates each subsystem model to the whole satellite, and comprehensively judges the coverage to form a whole satellite digital model.

[0029] Preferably, the subsystem model division in module M1 refers to completing the subsystem division based on the field-driven thought according to the overall function requirements, performance requirements and technical indexes of the satellite digital simulation model, analyzing the general requirements of each subsystem model to form a general subsystem model base class, and drawing a block definition diagram accordingly; the general subsystem model base class encapsulates the properties or methods common to the default initialization file, configuration file and running component of the submodel;

[0030] The module M1 is used for analyzing the key capabilities involved in the model design process from the three dimensions of physical simulation, information simulation and simulation control, and drawing a capability requirement diagram, wherein the physical simulation dimension is around the simulation capabilities of satellite machine, electricity, heat, motion, perception, task chain, time chain and precision chain; the information simulation dimension is around the simulation capabilities of telemetry, remote control, data transmission, inter-satellite, on-board task planning, on-board information processing and virtual-real interaction; the simulation control is around the model calling and running capabilities; the corresponding special item is divided according to the key capabilities, and the sub-system model base class of each special item is designed, which is inherited from the general sub-system model base class;

[0031] The module M1 is used for analyzing the key capabilities involved in the model design process from the three dimensions of physical simulation, information simulation and simulation control, and drawing a capability requirement diagram, wherein the physical simulation dimension is around the simulation capabilities of satellite machine, electricity, heat, motion, perception, task chain, time chain and precision chain; the information simulation dimension is around the simulation capabilities of telemetry, remote control, data transmission, inter-satellite, on-board task planning, on-board information processing and virtual-real interaction; the simulation control is around the model calling and running capabilities; the corresponding special item is divided according to the key capabilities, and the sub-system model base class of each special item is designed, which is inherited from the general sub-system model base class;

[0032] Preferably, the module M2 is used for defining the composition of the sub-system model of each special item, analyzing the sub-system models involved in the implementation of the simulation capabilities corresponding to the special item, and further dividing the composition of each sub-system model from the simulation and business angles, completing the function description of each composition, and drawing a block definition diagram;

[0033] The module M2 is used for defining the information flow of each special item, analyzing the information flow transmitted between the related sub-system models, and defining the interface and data items, including the interface type, data item name, signal source and signal sink, and drawing an internal block diagram;

[0034] The module M2 is used for defining the workflow of each special item, defining the working mode and switching condition around the function implementation process of each special item, drawing a state machine diagram, and defining the work items, execution sequence and information transmitted between different work items between the sub-models in the function implementation process, and drawing an activity diagram;

[0035] The module M3 is used for integrating the requirements of each special item on each sub-system model, abstractly classifying, analyzing the dependency relationship and conflict points between the requirements, and solving the contradictions between the requirements, defining the requirement priority, constructing a complete, consistent and traceable requirement system for each sub-system model, completing the black box design of each sub-system model, including the function and interface design, forming the sub-system model base class in the overall outline design stage, the sub-system model base class in this stage inherits the sub-system model base class in the design of all related special items, and a block definition diagram is drawn accordingly;

[0036] In module M4, the model composition and interface design for implementation refers to inheriting the subsystem model base class from the overall preliminary design stage, completing the functional module division and interface sorting of the subsystem model for implementation, drawing BDD diagrams, and completing the functional description of each module from the perspective of simulation implementation, including the input, output and mathematical principles of each function.

[0037] The information flow design of the implementation model in module M4 refers to the process of clarifying the data input, processing, output and storage links of each module based on the data processing flow and information transmission path of the subsystem, and analyzing the source, destination and processing method of data in each key link, so as to clarify the flow direction of data between modules within the subsystem model and between internal modules and external models, and draw the internal block diagram accordingly.

[0038] The workflow design of the implementation-oriented model in module M4 refers to the process around the implementation of subsystem functions, clarifying the working mode and switching conditions, and drawing state machine diagrams; at the same time, it analyzes the physical principles of subsystem operation, clarifies the main business activities and the data flow and control flow between activities, and draws activity diagrams.

[0039] In module M4, the data structure design for implementation-oriented model development refers to designing one or more classes for each function or module based on the results of functional composition analysis. According to the functional requirements, information flow, and activity analysis of the classes, the attributes, methods, and relationships between classes are clarified, and class diagrams are drawn. At this stage, the data structure for transmitting information between modules is clarified to guide the development of subsystem models.

[0040] Preferably, in module M5, the integration of each subsystem model into the whole satellite refers to collecting the detailed design models of each subsystem, integrating the technical routes and detailed schemes of each sub-model into the whole satellite model, and drawing a BDD diagram;

[0041] In module M5, the comprehensive assessment of coverage refers to establishing a requirement satisfaction matrix for the detailed subsystem models against the overall outline design model, specialized design models, and overall preliminary design models. This verifies whether the functional module composition, interfaces, information flow, workflow, and data structure in the collected detailed subsystem models can cover the functional composition and interface requirements of the subsystems proposed in the overall outline design phase; whether they can cover the functional composition, interfaces, information flow, and workflow requirements of the subsystems proposed in each specialized design, and whether the subsystems can organically cooperate to achieve the capabilities of each specialized design; and whether they can cover the simulation requirements of the whole-satellite simulation control layer, physical layer, and information layer proposed in the overall preliminary design, ultimately forming a requirement satisfaction table.

[0042] Compared with the prior art, the present invention has the following beneficial effects:

[0043] The satellite digital simulation model design method based on MBSE has parallel engineering and collaborative design working modes in each stage, meets the multidisciplinary and cross-department joint simulation requirements, carries out comprehensive decision and hierarchical verification at the overall level, ensures the system and integrity of the model, comprehensively considers the coupling elements and fully demonstrates the working principle at the special demonstration level, ensures the scientificity of the model, adopts modularization and interface standardization design at the subsystem level, and improves the scalability of the model, so that the method has good flexibility, standardization and scalability, and can meet the technical and application requirements of the current multi-purpose engagement level and engineering level satellite simulation model development. BRIEF DESCRIPTION OF DRAWINGS

[0044] Other characteristics, objects and advantages of the present application will become more apparent from the following detailed description of non-restrictive embodiments, made with reference to the attached drawings:

[0045] Figure 1 The design method step diagram of the present application is shown in the figure;

[0046] Figure 2 The internal block diagram of the TT&C subsystem is shown in the figure;

[0047] Figure 3 The state machine diagram of the power supply and distribution subsystem is shown in the figure;

[0048] Figure 4 The requirement satisfaction matrix of the overall preliminary design to the development requirements is shown in the figure;

[0049] Figure 5 The requirement satisfaction matrix of the special design to the overall preliminary design is shown in the figure;

[0050] Figure 6 The requirement satisfaction matrix of the overall summary design to the special design is shown in the figure;

[0051] Figure 7 The requirement satisfaction matrix of the subsystem detailed design to the overall summary design is shown in the figure. DETAILED DESCRIPTION

[0052] The present application will be described in detail below with reference to specific embodiments. The following embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any form. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present application. These all belong to the protection scope of the present application.

[0053] EMBODIMENT

[0054] The application comprehensively considers the professional technical complexity and engineering complexity characteristics of the satellite simulation model, carries out overall preliminary design through the Agent-based modeling method, divides the subsystem model composition, and divides the special item according to the typical satellite system professional composition; combined with the professional background of each special item, the MAGICGRID modeling method is used to carry out special item design, and the grid demand of the special item to each subsystem is clarified; the subsystem demand proposed by each special item is overall planned, the overall summary design is carried out, and a complete, consistent and traceable subsystem demand system is constructed; based on the modularization and interface standardization idea, the subsystem detailed design is carried out; the subsystem scheme is integrated, and the hierarchical verification of the overall summary design model to the overall preliminary design model, the overall summary design model to the special item design model, the special item design model to the overall preliminary design model and the overall preliminary design model to the satellite digital simulation model development requirement is carried out through the establishment of the subsystem detailed design model, and the coverage and rationality of the overall digital model design scheme of the satellite are analyzed.

[0055] As shown in Figure 1 The application provides a satellite digital simulation model design method based on MBSE, which includes five steps of overall preliminary design, special item design, overall summary design, subsystem detailed design and overall integration design.

[0056] The overall preliminary design indicates the subsystem model division of the satellite digital simulation model, identifies the key problems existing in the model design process and carries out special item division accordingly, and analyzes the relationship between each special item and each subsystem model. The subsystem model division refers to completing the subsystem division based on the field-driven idea according to the overall function requirement, performance requirement and technical index of the satellite digital simulation model. At the same time, the general requirements of each subsystem model are analyzed, the general subsystem model base class is formed, and the block definition diagram (BDD) is drawn accordingly. The base class usually encapsulates the properties or methods shared by the default initialization file, configuration file and running component of the submodel. The special item division refers to analyzing the key capabilities involved in the model design process from the three dimensions of physical simulation, information simulation and simulation control, and drawing the capability requirement diagram (RD) according to the simulation basic requirements of the satellite digital simulation model. The physical simulation level mainly focuses on the simulation capabilities of satellite machine, electricity, heat, motion, perception, task chain, time chain and precision chain; the information simulation level mainly focuses on the information simulation capabilities of telemetry, remote control, data transmission, inter-satellite, on-board task planning, on-board information processing and virtual-real interaction; and the simulation control mainly focuses on the model calling and running capabilities.

[0057] According to the key capability division, the subsystem model base class of each special item is designed, and the base class inherits from the general subsystem model base class. Analyzing the relationship between each special item and each subsystem model refers to analyzing the subsystem models related to each capability of the satellite digital simulation model, designing the related subsystem model base class under each special item, and drawing the block definition diagram (BDD) accordingly, such as:

[0058] (1) For the model call and running special item, each subsystem is required to have the ability of initialization, time control, simulation step, information interaction and data collection, covering all subsystems of satellite general electric, attitude and orbit control, power supply and distribution, thermal control, TT&C, data transmission, etc. Therefore, the base class of all subsystems under this special item should be designed.

[0059] (2) For the telemetry and telecontrol information interaction special item, the general electric model is required to have the ability of telecontrol frame analysis and distribution and telemetry frame generation and collection. Each subsystem is required to have the ability of telecontrol command execution and telemetry data generation and collection, covering all subsystems of satellite general electric, attitude and orbit control, power supply and distribution, thermal control, TT&C, data transmission, etc. Therefore, the base class of all subsystems under this special item should be designed.

[0060] (3) For the platform and component simulation special item, the attitude and orbit control model is required to have the ability of platform on-orbit flight and orbit maneuver dynamics simulation, platform attitude control and dynamics simulation, rotating component control simulation and space pointing calculation. The power supply and distribution model is required to have the ability of solar panel control simulation and space pointing calculation. The data transmission model is required to have the ability of data transmission antenna control simulation and space pointing calculation, covering the attitude and orbit control, power supply and distribution, data transmission subsystems of satellite. Therefore, the base class of attitude and orbit control, power supply and distribution, data transmission subsystems under this special item should be designed.

[0061] Special item design refers to the development of multidisciplinary parallel special item demonstration for the whole satellite, which clarifies the model composition, information flow and work flow of each subsystem of each special item. Clarifying the model composition of each subsystem of each special item refers to analyzing the simulation capability implementation involved in the model of each subsystem corresponding to the special item, and further dividing the composition of each subsystem model from the simulation and business angles, completing the function description of each composition, and drawing the block definition diagram (BDD). Clarifying the information flow of each special item refers to analyzing the information flow transmitted between related subsystem models, clarifying the interface and data items, including interface type, data item name, signal source, signal sink, etc., and drawing the internal block diagram (IBD). Clarifying the work flow of each special item refers to the flow around the function implementation of each special item, clarifying the work mode and switching conditions, and drawing the state machine diagram (SMD). Clarifying the work items, execution order and information transmission between different work items among each sub-model in the function implementation process, and drawing the activity diagram (AD).

[0062] The overall summary design refers to the requirements of each special item to each subsystem model, carries out demand integration, constructs the demand system of the subsystem model, and makes clear the main functions and interfaces. The demand integration refers to the compatibility, commonality, dependency, conflict and other relationships of the demand, takes appropriate measures, constructs the complete, consistent and traceable demand system of each subsystem model, and draws the requirement diagram (RD). At the same time, the black box design of each subsystem model is completed, including the function and interface design, the subsystem model base class of the overall summary design stage is formed, and the block definition diagram (BDD) is drawn.

[0063] The corresponding processing measures for the compatibility, commonality, dependency, conflict and other relationships of the demand are as follows:

[0064] (1) Compatibility relationship: collect and integrate the compatibility requirements of each special item to the subsystem model to form the maximum demand envelope;

[0065] (2) Commonality relationship: abstract and induce the commonality requirements to form a unified demand set;

[0066] (3) Dependency relationship: identify and define which requirements are the prerequisites of other requirements, and make the dependency relationship explicit;

[0067] (4) Conflict relationship: weigh the importance, urgency and feasibility of each requirement, and propose a compromise solution;

[0068] (5) Priority relationship: evaluate the value and importance of each requirement to the implementation of digital satellite capabilities, as well as the implementation cost and risk of the requirement, make a comprehensive decision, and sort the requirements by priority.

[0069] The subsystem detailed design refers to the model detailed design for implementation, including composition, interface, information flow, workflow, data structure, etc. The model composition and interface design for implementation refers to inheriting the subsystem model base class in the overall summary design stage, completing the subsystem model function module division and interface sorting for implementation, and drawing the BDD graph. Meanwhile, the function description of each module is completed from the simulation implementation perspective, including the input, output and mathematical principle of each function. The information flow design of the model for implementation refers to the data processing flow and information transmission path of the subsystem, and the data input, processing, output and storage of each module are clarified, and the source, destination and processing mode of the data in each key link are analyzed, so as to clarify the flow direction of the data between the internal modules of the subsystem model and between the internal modules and external models, and draw the internal block diagram (IBD). Taking the TT&C subsystem as an example, the external interaction data items include initialization data input, environment input, simulation state output, running log output, model event output, analog quantity output, energy input / output, uplink remote control data input / output and downlink telemetry data input / output, etc., wherein the uplink remote control data comes from the ground station and is received by the TT&C subsystem and forwarded to the integrated power subsystem; the downlink telemetry data comes from the integrated power subsystem and is received by the TT&C subsystem and forwarded to the ground station; the rest of the data are the interaction data between the TT&C subsystem and the simulation engine. After receiving the uplink remote control data or the downlink telemetry data, the TT&C subsystem performs visibility calculation and link calculation processing based on the ground station and the star state data in the environment data, and if the star-ground is visible and the link margin is greater than 0, the link is successfully established, the uplink remote control data is forwarded to the integrated power subsystem or the downlink telemetry data is forwarded to the ground station. According to the analyzed data source, destination and processing mode, the IBD of the TT&C subsystem is drawn as shown in Figure 2 .

[0070] The workflow design of the model for implementation refers to the flow around the function implementation of the subsystem, and the working mode and switching condition are clarified, and the state machine diagram (SMD) is drawn. Taking the power supply model as an example, the working state is divided into normal state and energy crisis state, the working mode in the normal state includes charging mode, discharging mode and shunt mode, the working mode in the energy crisis state includes charging mode and discharging mode, and the switching between the modes is shown in Figure 3 .

[0071] Meanwhile, the physical principle of the subsystem work is analyzed, and the data flow and control flow between the main business activities are clarified, and the activity diagram (AD) is drawn. The data structure design of the model for implementation refers to designing one or more classes for each main function or module according to the analysis result of the functional composition, and clarifying the attributes, methods and relationships between the classes according to the function demand, information flow and activity analysis of the classes, and drawing the class diagram (CD). In this stage, the data structure of the transmitted information between the modules should be clarified, which is used to guide the development of the subsystem model.

[0072] The overall integrated design refers to integrating each subsystem model to the whole satellite, and comprehensively judging the coverage to form the whole satellite digital model. Integrating each subsystem model to the whole satellite refers to collecting each subsystem detailed design model, integrating the technical route and detailed scheme of each sub-model to the whole satellite model, and drawing a BDD graph. The comprehensive judgment of the coverage refers to establishing the hierarchical verification relationship of the satellite digital simulation model development requirements for the overall preliminary design model, the overall preliminary design model for the special design model, the special design model for the overall summary design model, and the overall summary design model for the subsystem detailed design model, to form four demand satisfaction matrices (SRT), which are as follows:

[0073] (1) verifying whether each special development requirement proposed in the overall preliminary design stage can cover the satellite digital simulation model development requirements, if not, the missing items need to be checked and the design needs to be supplemented. The demand satisfaction matrix is shown in Figure 4 .

[0074] (2) verifying whether each subsystem requirement proposed in the special design can cover the special development requirement proposed in the overall preliminary design, if not, the missing items need to be checked and the design needs to be supplemented. Taking the special a (simulation control flow design) as an example, the demand satisfaction matrix is shown in Figure 5 .

[0075] (3) verifying whether the subsystem requirements formed in the overall summary design stage can cover the subsystem requirements proposed in each special design, if not, the missing items need to be checked and the design needs to be supplemented. Taking the integrated electrical subsystem as an example, the demand satisfaction matrix is shown in Figure 6 .

[0076] (4) verifying whether the function module composition, information flow, work flow, interface, etc. in the collected subsystem detailed design model can cover the subsystem function, performance and interface requirements proposed in the overall summary design stage, if yes, it provides the basis for subsequent software design, if not, the missing items need to be checked and the design needs to be supplemented. Taking the integrated electrical subsystem as an example, the demand satisfaction matrix is shown in Figure 7 .

[0077] Those skilled in the art know that in addition to implementing the system, device and each module thereof provided by the present application in a pure computer readable program code manner, the same program can be realized in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, the system, device and each module thereof provided by the present application can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing methods and structures within hardware components.

[0078] The specific embodiments of the present application have been described. It is to be understood that the application is not limited to particular details described herein and that various modifications can be made therein without departing from the scope of the claimed application. Embodiments and features disclosed in this document, including in the examples, can be combined with each other, unless specifically contradicted by or inconsistent with each other.

Claims

1. A satellite digital simulation model design method based on MBSE, characterized in that, include: Step 1: Overall preliminary design, clarify the subsystem model division of the satellite digital simulation model, identify key issues in the model design process and make special divisions accordingly, and analyze the relationship between each special division and each subsystem model; Step 2, Specialized Design: Conduct multidisciplinary parallel specialized demonstrations for the entire satellite, clarifying the subsystem model composition, information flow, and workflow of each specialized project; Step 3: Overall outline design, coordinate the requirements of each project for each subsystem model, carry out requirements integration, build the subsystem model requirements system, and clarify the main functions and interfaces; Step 4: Detailed design of subsystems. This involves detailed model design for implementation purposes, including components, interfaces, information flow, workflow, and data structure. Step 5: Overall integration design, integrating the models of each subsystem into the whole satellite, and comprehensively judging the coverage to form the whole satellite digital model.

2. The satellite digital simulation model design method based on MBSE according to claim 1, characterized in that, In step 1, the subsystem model partitioning refers to completing the subsystem partitioning based on the overall functional requirements, performance requirements, and technical indicators of the satellite digital simulation model, using the domain-driven approach. At the same time, the general requirements of each subsystem model are analyzed to form a general subsystem model base class, and a block definition diagram is drawn accordingly. The general subsystem model base class encapsulates the default initialization files, configuration files, and common attributes or methods of the running components of the sub-models. In step 1, the specialization refers to combining the basic simulation requirements of the satellite digital simulation model, analyzing the key capabilities involved in the model design process from three dimensions: physical simulation, information simulation, and simulation control, and drawing a capability requirement diagram. The physical simulation level focuses on the simulation capabilities of satellite mechanics, electronics, heat, motion, sensing, mission chains, time chains, and accuracy chains; the information simulation level focuses on the simulation capabilities of telemetry, remote control, data transmission, inter-satellite and on-board mission planning, on-board information processing, and virtual-real interaction; and the simulation control level focuses on the model invocation and operation capabilities. Based on the key capabilities, corresponding specializations are divided, and a subsystem model base class for each specialization is designed. This base class inherits from the general subsystem model base class. In step 1, analyzing the relationship between each project and each subsystem model refers to analyzing the subsystem models related to realizing the various capabilities of the satellite digital simulation model, designing the relevant subsystem model base classes under each project, which inherit from the subsystem model base class of the project, and drawing the block definition diagram accordingly.

3. The satellite digital simulation model design method based on MBSE according to claim 1, characterized in that, Step 2 clarifies the composition of the subsystem model for each special project, which means analyzing the subsystem model involved in the simulation capability implementation corresponding to the special project, and further dividing the composition of each subsystem model from both simulation and business perspectives, completing the functional description of each component, and drawing a block definition diagram. In step 2, the information flow of each special project is defined, which refers to the information flow transmitted between the relevant subsystem models. The interfaces and data items are defined, including the interface type, data item name, information source and information destination, and an internal block diagram is drawn. In step 2, the workflow of each project is defined as the process around which the functions of each project are realized. The working mode and switching conditions are defined, and a state machine diagram is drawn. During the function realization process, the work items, execution order and information transmitted between different work items of each sub-model are defined, and an activity diagram is drawn.

4. The satellite digital simulation model design method based on MBSE according to claim 1, characterized in that, Step 3, which involves requirements integration, refers to coordinating the requirements of each project for each subsystem model, abstracting and classifying them, analyzing the dependencies and conflict points between requirements, resolving contradictions between requirements, clarifying requirement priorities, constructing a complete, consistent, and traceable requirements system for each subsystem model, completing the black-box design of each subsystem model, including functional and interface design, and forming the subsystem model base class in the overall preliminary design stage. The subsystem model base class in this stage inherits the subsystem model base class in all related project designs, and a block definition diagram is drawn accordingly.

5. The satellite digital simulation model design method based on MBSE according to claim 1, characterized in that, In step 4, the model composition and interface design for implementation refers to inheriting the subsystem model base class from the overall preliminary design stage, completing the functional module division and interface sorting of the subsystem model for implementation, drawing the BDD diagram, and completing the functional description of each module from the perspective of simulation implementation, including the input, output and mathematical principles of each function. In step 4, the information flow design of the model for implementation refers to clarifying the data input, processing, output and storage links of each module based on the data processing flow and information transmission path of the subsystem, and analyzing the source, destination and processing method of data in each key link, so as to clarify the flow direction of data between modules within the subsystem model and between internal modules and external models, and draw the internal block diagram accordingly. In step 4, the workflow design for implementing the model refers to the process surrounding the implementation of subsystem functions, clarifying the working modes and switching conditions, and drawing state machine diagrams; at the same time, it involves analyzing the physical principles of subsystem operation, clarifying the main business activities and the data flow and control flow between activities, and drawing activity diagrams. In step 4, the data structure design for implementation-oriented model refers to designing one or more classes for each function or module based on the results of functional composition analysis. According to the functional requirements, information flow and activity analysis of the classes, the attributes, methods and relationships between classes are clarified, and class diagrams are drawn. At this stage, the data structure for transmitting information between modules is clarified to guide the development of subsystem models.

6. The satellite digital simulation model design method based on MBSE according to claim 1, characterized in that, In step 5, integrating the models of each subsystem into the whole satellite means collecting the detailed design models of each subsystem, integrating the technical routes and detailed schemes of each sub-model into the whole satellite model, and drawing the BDD diagram. In step 5, the comprehensive assessment of coverage refers to establishing a requirement satisfaction matrix for the detailed subsystem models on the overall outline design model, the specialized design model, and the overall preliminary design model. This verifies whether the functional module composition, interfaces, information flow, workflow, and data structure in the collected detailed subsystem models can cover the functional composition and interface requirements of the subsystems proposed in the overall outline design stage; whether they can cover the functional composition, interfaces, information flow, and workflow requirements of the subsystems proposed in each specialized design; and whether the subsystems can organically cooperate to achieve the capabilities of each specialized design. Finally, it verifies whether they can cover the simulation requirements of the whole-satellite simulation control layer, physical layer, and information layer proposed in the overall preliminary design, ultimately forming a requirement satisfaction table.

7. A satellite digital simulation model design system based on MBSE, characterized in that, include: Module M1, overall preliminary design, clarifies the subsystem model division of the satellite digital simulation model, identifies key issues in the model design process and makes specific divisions accordingly, and analyzes the relationship between each specific division and each subsystem model; Module M2, a specialized design, involves conducting multidisciplinary parallel special demonstrations for the entire satellite, clarifying the subsystem model composition, information flow, and workflow of each special project; Module M3, overall overview design, coordinates the requirements of various special projects for each subsystem model, carries out requirement integration, constructs the subsystem model requirement system, and clarifies the main functions and interfaces; Module M4, subsystem detailed design, conducts detailed model design for implementation, including composition, interfaces, information flow, workflow and data structure; Module M5 is an overall integrated design that integrates the models of each subsystem into the whole satellite and comprehensively judges the coverage to form the whole satellite digital model.

8. The satellite digital simulation model design system based on MBSE according to claim 7, characterized in that, The subsystem model partitioning in module M1 refers to the partitioning of subsystems based on the overall functional requirements, performance requirements, and technical indicators of the satellite digital simulation model, using the domain-driven approach. Simultaneously, it involves analyzing the common requirements of each subsystem model to form a common subsystem model base class, upon which a block definition diagram is drawn. This common subsystem model base class encapsulates the default initialization files, configuration files, and common attributes or methods of the running components of the sub-models. The specific division in module M1 refers to analyzing the key capabilities involved in the model design process from three dimensions—physical simulation, information simulation, and simulation control—based on the basic simulation requirements of the satellite digital simulation model, and drawing a capability requirement diagram. Specifically, the physical simulation level focuses on the simulation capabilities of satellite mechanics, electronics, heat, motion, sensing, mission chains, time chains, and accuracy chains; the information simulation level focuses on the simulation capabilities of telemetry, remote control, data transmission, inter-satellite and on-board mission planning, on-board information processing, and virtual-real interaction; and the simulation control level focuses on the model invocation and operation capabilities. Based on the key capabilities, corresponding sub-projects are divided, and a subsystem model base class for each sub-project is designed. This base class inherits from the general subsystem model base class. The relationship between each project and each subsystem model in module M1 refers to analyzing the subsystem models related to realizing the various capabilities of the satellite digital simulation model, designing the relevant subsystem model base classes under each project, which inherit from the subsystem model base class of the project, and drawing the block definition diagram accordingly.

9. The satellite digital simulation model design system based on MBSE according to claim 7, characterized in that, The module M2 clarifies the subsystem model composition of each special project, analyzes the subsystem models involved in the simulation capability implementation of the corresponding special project, and further divides the composition of each subsystem model from both simulation and business perspectives, completes the functional description of each component, and draws the block definition diagram. The module M2 clarifies the information flow of each special project, analyzes the information flow transmitted between related subsystem models, clarifies the interfaces and data items, including interface type, data item name, information source and information destination, and draws internal block diagrams; The module M2 clarifies the workflow of each special project, which refers to the process around the implementation of the function of each special project, clarifies the working mode and switching conditions, and draws a state machine diagram; it also clarifies the work items, execution order and information passed between different work items among the sub-models during the function implementation process, and draws an activity diagram. In module M3, the requirement integration refers to coordinating the requirements of various special projects for each subsystem model, abstracting and classifying them, analyzing the dependencies and conflict points between requirements, resolving contradictions between requirements, clarifying requirement priorities, constructing a complete, consistent, and traceable requirement system for each subsystem model, completing the black-box design of each subsystem model, including functional and interface design, forming the subsystem model base class in the overall preliminary design stage. The subsystem model base class in this stage inherits the subsystem model base class in all related special project designs, and block definition diagrams are drawn accordingly. In module M4, the model composition and interface design for implementation refers to inheriting the subsystem model base class from the overall preliminary design stage, completing the functional module division and interface sorting of the subsystem model for implementation, drawing BDD diagrams, and completing the functional description of each module from the perspective of simulation implementation, including the input, output and mathematical principles of each function. The information flow design of the implementation model in module M4 refers to the process of clarifying the data input, processing, output and storage links of each module based on the data processing flow and information transmission path of the subsystem, and analyzing the source, destination and processing method of data in each key link, so as to clarify the flow direction of data between modules within the subsystem model and between internal modules and external models, and draw the internal block diagram accordingly. The workflow design of the implementation-oriented model in module M4 refers to the process around the implementation of subsystem functions, clarifying the working mode and switching conditions, and drawing state machine diagrams; at the same time, it analyzes the physical principles of subsystem operation, clarifies the main business activities and the data flow and control flow between activities, and draws activity diagrams. In module M4, the data structure design for implementation-oriented model development refers to designing one or more classes for each function or module based on the results of functional composition analysis. According to the functional requirements, information flow, and activity analysis of the classes, the attributes, methods, and relationships between classes are clarified, and class diagrams are drawn. At this stage, the data structure for transmitting information between modules is clarified to guide the development of subsystem models.

10. The satellite digital simulation model design system based on MBSE according to claim 7, characterized in that, In module M5, the models of each subsystem are integrated into the whole satellite model, which collects the detailed design models of each subsystem, integrates the technical routes and detailed schemes of each sub-model into the whole satellite model, and draws the BDD diagram. In module M5, the comprehensive assessment of coverage refers to establishing a requirement satisfaction matrix for the detailed subsystem models against the overall outline design model, specialized design models, and overall preliminary design models. This verifies whether the functional module composition, interfaces, information flow, workflow, and data structure in the collected detailed subsystem models can cover the functional composition and interface requirements of the subsystems proposed in the overall outline design phase; whether they can cover the functional composition, interfaces, information flow, and workflow requirements of the subsystems proposed in each specialized design, and whether the subsystems can organically cooperate to achieve the capabilities of each specialized design; and whether they can cover the simulation requirements of the whole-satellite simulation control layer, physical layer, and information layer proposed in the overall preliminary design, ultimately forming a requirement satisfaction table.

Images