An integrated aircraft design method and system based on MBSE

Abstract

The present invention proposes an integrated aircraft design method and system based on MBSE. First, an integrated aircraft mission requirement analysis is carried out, then the logical architecture of the launch segment and the orbital segment is constructed, and the flow relationship between different subsystems is established; the subsystem structure, parameters and behavior are refined, and the flow relationship between each physical component is improved; a model library of alternative physical components is constructed, the domain model is integrated into the system architecture model, dynamic simulation is carried out to verify the system operation indicators, the functions, structural models and parameters in the design scheme are adjusted to improve the system performance, and finally the system design and selection scheme is frozen; the present invention reasonably reduces equipment redundancy to improve the load-to-mass ratio and load ratio of the aircraft under the premise of meeting reliability, and at the same time constructs the composition, parameters and behavior of each subsystem under complex states, which is convenient for design and optimization personnel to implement quantitative and qualitative evaluation, statistical analysis, demand change and management, and domain design of the system, thereby improving overall design capabilities.

Description

Technical Field

[0001] The present invention belongs to the technical field of systems engineering, and in particular, relates to an integrated aircraft design method and system based on MBSE. Background Art

[0002] The integrated satellite-rocket vehicle realizes the integrated design of rockets, satellites and payloads. It is composed of a multi-stage power system and an autonomous orbit-entry spacecraft system. It can realize satellite control and transportation directly into orbit according to the mission. Compared with traditional designs, it can significantly increase the payload ratio. At the same time, it adopts a multi-stage solid power system, which can be stored for a long time and has rapid deployment capabilities, greatly improving the rapid response capability in space at a lower cost.

[0003] The integrated spacecraft is a complex system, and the integrated design does not clearly distinguish between the payload, platform, and the final stage of the launch vehicle. This can reduce excessive redundancy in system resources, making the system design more complex. The complexity of system design is reflected in the following aspects: there are more numerous and multidisciplinary requirements in the system design phase, and the system design must ensure that all requirements are met; the system composition structure is more complex, and the division of labor between the system payload, platform, etc. is no longer clear. How to design a structure that meets the requirements while reducing excessive redundancy is also a problem that needs to be solved in the design phase; the system has many usage scenarios, and different systems must work in multiple system phases. The system scheduling behavior is complex, and ensuring reasonable system behavior in the design phase is also one of the difficulties that traditional systems engineering cannot solve; there are many inconsistencies in the interfaces between systems. The integrated system has a larger number of cross-system interfaces. Ensuring the consistency of the transmission types of many system interfaces can reduce system design errors and save costs.

[0004] To address these common challenges in complex system design, advanced model-based systems engineering (MBSE) has been developed internationally. MBSE follows the traditional systems engineering process: requirements, functions, logic, and physics, and incorporates a unified model throughout, constructing system models in a format that is easily understood by designers and stakeholders. MBSE encompasses three key components: modeling language, modeling tools, and modeling methods. SysML is typically used as the modeling language. Combining the advantages of object-oriented and process-oriented approaches, MBSE designs and displays system requirements, scenarios, behavior, components, and parameters in a visual model format to meet the needs of all stakeholders. Its executable nature enables simulations of varying degrees at all stages of system design for early verification and design iteration, reducing system costs. MBSE's specialized behavioral and state simulations verify that system behavior meets requirements. It also incorporates a degree of parametric simulation, enabling early verification of parameters such as quality, power, cost, and reliability. A single model ensures consistent interfaces between systems, reducing interface errors in traditional designs.

[0005] Combining the advantages of MBSE, an integrated design theory and method are proposed, providing a new approach for integrated complex system design. Model-based integrated design fully leverages the advantages of MBSE design, fully implementing integrated design concepts in system design. Behavioral coupling analysis is performed within behaviors, and functional redundancy is implemented in the structure. This allows for early reliability design to avoid insufficient system reliability due to excessive redundancy. System-level simulation is conducted, and design trade-offs are analyzed based on the simulation results to improve the system's mass-to-load ratio and load-to-load ratio. The complex system behavior and diverse system states of the integrated aircraft can also be verified using SysML model simulation to clarify the interactions and interfaces between complex systems. Ultimately, a system model is constructed that reflects the actual structure and behavior of the integrated aircraft.

[0006] Existing aircraft design methods mainly focus on structural parameter modeling of the system, or structural and behavioral modeling under a single subsystem. Although these methods meet the system engineering process, they rarely study the interactions between different subsystems, and rarely involve the entire process from the launch of the aircraft to its mission execution in orbit. Summary of the Invention

[0007] In response to the shortcomings of the existing technology, the present invention proposes an integrated aircraft design method and system based on MBSE to construct a complex integrated satellite-rocket aircraft to deal with the problems of complex aircraft system structure, multiple interactions between components, and system behavior switching in different flight phases.

[0008] The present invention is achieved through the following technical solutions:

[0009] An integrated MBSE-based aircraft design, optimization, and evaluation method:

[0010] The method specifically comprises the following steps:

[0011] Step A: After obtaining the mission requirements, conduct integrated aircraft mission requirements analysis;

[0012] Conduct integrated aircraft mission requirement analysis, build operational scenarios in SysML based on mission concepts to clarify system design requirements, decompose and cluster the functional requirements of the integrated aircraft component systems, merge the same functions of different components, analyze the functions of each subsystem under the MBSE process, and design behaviors and test cases;

[0013] Step B: Build the logical architecture;

[0014] Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages, and build the flow relationships and interfaces between different subsystems based on the interaction between behaviors.

[0015] Step C: Design the physical architecture;

[0016] Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft; improve parameter modeling and construct parameter diagrams to verify system indicators; establish the status and behavior of each subsystem, improve the flow relationship between each physical component, and define the interface in detail;

[0017] Step D: Design and selection of spectral library;

[0018] Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators.

[0019] Step E: Joint simulation verification;

[0020] Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators;

[0021] Step F: Optimize the system design scheme. According to the simulation results, adjust the functions, structural models and parameters in the design scheme, and finally freeze the system design and selection scheme.

[0022] Furthermore,

[0023] In step A, the following steps are specifically included:

[0024] Step A1: Determine the integrated aircraft mission requirements and build a model-based requirements library using the MBSE modeling language;

[0025] Step A2: Construct an integrated aircraft terminology glossary;

[0026] Step A3: Conduct system requirements analysis and refinement, deriving system design requirements from the system mission scenarios designed in the Concept of Operations (ConOps), and then deriving requirements for each level of aircraft systems, constructing a requirements diagram, and generating a requirements matrix.

[0027] Step A4: Construct the behaviors of each aircraft system, perform functional clustering on the behaviors and component mappings, and obtain the system requirements after redundancy optimization that meets the integrated design requirements;

[0028] Furthermore,

[0029] The logical architecture design specifically includes: designing a white box model of functions and structures that meet the requirements;

[0030] In step B, the following steps are specifically included:

[0031] Step B1: Construct the top-level model of the orbital insertion segment and the launch segment, define the interaction between them, and define the parameters;

[0032] Step B2: Construct the next-level logical architecture structural model for the orbital insertion segment and the carrier segment respectively;

[0033] Step B3: Assign behavioral requirements to each subsystem and define the composition, state, and behavior of different subsystems;

[0034] Step B4: Define the interaction between different subsystems based on behavioral requirements.

[0035] Furthermore,

[0036] The physical architecture is specifically: a white box model corresponding to the logical architecture in step B, which enables the system to implement a physical model of its functions, including physical components, mechanisms, and equipment;

[0037] In step C, the following steps are specifically included:

[0038] Step C1: Refine each subsystem to a physical component model, allocate requirements, and verify requirement coverage;

[0039] Step C2: Completely design the behavior of each subsystem;

[0040] Step C3: Define the interactions of the physical components within the subsystem, distribute the interactions between subsystems to the physical components, and fully define the flows and ports of the interactions.

[0041] Furthermore,

[0042] In step D, the following steps are specifically included:

[0043] Step D1: defining the required parameters of the physical components that can be used to construct the spectral library;

[0044] Step D2: define an instance of each physical component according to the existing model, assign parameters and store them;

[0045] Step D3: Generate an instance table of the spectrum;

[0046] Step D4: Based on the specified task requirements, select a model instance and perform parameter simulation to verify whether the selected model set can meet the requirements;

[0047] Specifically, the model library models available commercial off-the-shelf (COTS) or existing models of physical components and integrates them into the system model, uses them as part of the model in the form of instances, selects them during system verification, and then performs parameter calculations.

[0048] Furthermore,

[0049] In step E, the following steps are specifically included:

[0050] Step E1: Build models for each domain and perform transformations to meet integration requirements according to the MBSE model specifications.

[0051] Step E2: Perform model integration based on the characteristics of different models;

[0052] Step E3: Perform joint simulation to verify the system dynamic performance indicators;

[0053] The domain model specifically includes: non-MBSE models that meet various simulation requirements for aircraft operation, including trajectory solution models, structural analysis models, and controller models;

[0054] Furthermore,

[0055] In step F, the following steps are specifically included:

[0056] Step F1: By adjusting the parameters of the physical components, find a parameter set that can improve the system's load-to-mass ratio, load ratio and other indicators while meeting the requirements, as system parameter optimization;

[0057] Step F2: Optimize the processes involved in the system's behavior and perform behavior optimization based on the sequence diagram and timeline diagram obtained from the simulation to increase the system's responsiveness.

[0058] Step F3: After obtaining an optimization solution that meets expectations in the feasible interval, freeze the system design and selection plan.

[0059] An integrated aircraft design, optimization and evaluation system based on MBSE:

[0060] The system includes: a task requirement analysis subsystem, a logical architecture subsystem, a physical architecture subsystem, a spectrum library design and analysis subsystem, a simulation verification subsystem and a result output subsystem;

[0061] The mission requirement analysis subsystem is used to perform integrated aircraft mission requirement analysis after obtaining the mission requirement;

[0062] Conduct integrated aircraft mission requirement analysis, decompose and cluster the functional requirements of the integrated aircraft component systems, analyze the functions of subsystems at all levels under the MBSE process, and design behaviors and test cases;

[0063] The logical architecture subsystem is used to design the logical architecture;

[0064] Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages and build the flow relationship between different subsystems.

[0065] The physical architecture subsystem is used to design the physical architecture;

[0066] Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft; improve parameter modeling and construct parameter diagrams to verify system indicators; establish the status and behavior of each subsystem and improve the flow relationship between each physical component;

[0067] The type spectrum library design and analysis subsystem is used for designing and selecting type spectrum libraries;

[0068] Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators.

[0069] The simulation verification subsystem is used to perform joint simulation verification;

[0070] Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators;

[0071] The result output subsystem is used to optimize the system design scheme, adjust the functions, structural models and parameters in the design scheme according to the simulation results, and finally freeze the system design and selection scheme.

[0072] An electronic device includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program.

[0073] A computer-readable storage medium is used to store computer instructions, which implement the steps of any of the above methods when executed by a processor.

[0074] Beneficial effects of the present invention

[0075] The present invention solves the problem of lack of implementation process and technical solutions for joint design in the overall design stage of large-scale, complex, integrated aircraft. Functional design and coupling analysis are carried out during the overall design of the system, and early verification is carried out to discover system design defects, ensuring the consistency of a large number of system interfaces. Parameter iteration and optimization are carried out at the same time, thereby optimizing the performance of the system and greatly reducing the system iteration cost and R&D cycle.

[0076] This invention combines the advantages of MBSE to construct a comprehensive and standardized model of an integrated aircraft. While ensuring reliability, it rationally reduces equipment redundancy to improve the aircraft's mass-to-load ratio and payload ratio. It also analyzes the composition, parameters, and behavior of each subsystem under complex conditions, and performs simulations to verify various indicators. This creates a complete integrated aircraft architecture model, facilitating quantitative and qualitative system evaluation, statistical analysis, requirement change management, and domain design for designers and optimizers, thereby enhancing overall design capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1 Flowchart of the present invention;

[0078] Figure 2 It is the overall task requirement diagram;

[0079] Figure 3 A SysML glossary that defines some professional terms;

[0080] Figure 4 A SysML glossary for expressing some parameter relationships;

[0081] Figure 5 Schematic diagram of automatic conversion of requirements into constraints;

[0082] Figure 6 Assign system behavior requirements and merge functional flow charts;

[0083] Figure 7 An allocation matrix diagram to describe the allocation of some behaviors to system components;

[0084] Figure 8 Use case diagram to describe the rapid response domain;

[0085] Figure 9 To describe the top structural module definition diagram of the integrated aircraft;

[0086] Figure 10 To describe the module definition diagram of the logical structure of the orbiting spacecraft;

[0087] Figure 11 State machine diagram for executing satellite control for an orbiting spacecraft or controlling the orbiting spacecraft itself;

[0088] Figure 12 Define diagrams for the physical architecture modules of the control system;

[0089] Figure 13 Provides examples and tables of thruster component types;

[0090] Figure 14 Schematic diagram of the integration of multi-domain physical models and system architecture models. DETAILED DESCRIPTION

[0091] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0092] This paper proposes an integrated aircraft design method and system based on MBSE. This method constructs a model of an integrated aircraft, including both the launch and orbital stages. MBSE is applied according to the systems engineering process, conducting behavioral analysis and clustering based on requirements. A logical model is established to reduce excessive redundancy, which is then refined into a physical model. A physical component model library and a domain system model are constructed to perform system simulations to verify various system specifications, and parameter optimization is performed to improve system performance. Ultimately, an integrated aircraft model is generated that meets all system specifications. Designers at each stage can verifiably obtain the required design information from their respective perspectives.

[0093] An integrated MBSE-based aircraft design, optimization, and evaluation method:

[0094] The method specifically comprises the following steps:

[0095] Step A: After obtaining the mission requirements, conduct integrated aircraft mission requirements analysis;

[0096] Conduct integrated aircraft mission requirement analysis and build operational scenarios (ConOps) in SysML to clarify system design requirements. Decompose and cluster the functional requirements of the integrated aircraft component systems, analyze the functions of each subsystem under the MBSE process, and design behaviors and test cases.

[0097] Step B: Design the logical architecture;

[0098] Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages and build the flow relationship between different subsystems.

[0099] Step C: Design the physical architecture;

[0100] Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft; improve parameter modeling and construct parameter diagrams to verify system indicators; establish the status and behavior of each subsystem and improve the flow relationship between each physical component;

[0101] Step D: Design and selection of spectral library;

[0102] Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators.

[0103] Step E: Joint simulation verification;

[0104] Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators;

[0105] Step F: Optimize the system design scheme. According to the simulation results, adjust the functions, structural models and parameters in the design scheme, and finally freeze the system design and selection scheme.

[0106] In step A,

[0107] The system design requirements are specifically as follows: the detailed performance requirements of the system are derived from the load-to-mass ratio and load ratio constraints specified in the mission design indicators, as well as the performance indicators of the system's rapidity; the functional sequence that the aircraft system must have to meet the mission, that is, the functional requirements that the system should have.

[0108] Functional decomposition is specifically to obtain the functional requirements that make the system meet the indicators and the functional requirements of each level of subsystems obtained by functional process design;

[0109] Functional clustering is specifically as follows: according to the traditional design method, the functions of each system and subsystem are initially obtained, and then according to the integrated design concept, the same functions of different systems are located and the functions are merged to reduce functional overlap;

[0110] The MBSE process is based on the model-based system function idea, building the requirement model and design use case in the system model, and is part of the system model.

[0111] In step A, the following steps are specifically included:

[0112] Step A1: Determine the integrated aircraft mission requirements and build a model-based requirements library using the MBSE modeling language;

[0113] The task requirements agreed upon by the overall design department are created into a table document and divided into strips. Using the import method provided by the SysML tool, an MBSE requirement diagram is constructed to incorporate the task requirements in the form of a text model as part of the system model.

[0114] The load-to-mass ratio, load ratio, and rapid response requirements of the system's overall mission requirements should be considered as top-level requirements. The MBSE modeling language is SysML.

[0115] like Figure 2Build an overall mission requirement diagram (REQ), construct the most concerned mission requirements including load-to-mass ratio, load ratio and rapid response, define its ID value and text content. The top-level requirement usually has a large integer or letter ID such as "1". Subsequent derived and refined requirements usually have an ID set to "1.1" to indicate their classification. At the same time, the requirement ID ensures the uniqueness of the requirement.

[0116] Step A2: Construct an integrated aircraft terminology glossary;

[0117] Build a glossary in the SysML language; such as Figure 3 A SysML glossary representing specialized terminology was constructed to avoid linguistic ambiguity between the overall and subsystem designers. "Load ratio" was defined as load mass, and various terms, including integrated aircraft, were defined. The benefit of the terminology is that it is highlighted during modeling and its meaning is displayed when the mouse is hovered over it. Furthermore, the complete glossary can be verified for spelling errors using the confirmation function.

[0118] like Figure 4 Build a glossary of terms that represent mathematical relationships, and construct mathematical terms such as "not more than" so that it has the mathematical meaning of "≤". Requirements are written and assigned in the specified format, so that requirements can be automatically converted into constraints and automatically verified.

[0119] For example, the indicator is written as the requirement of "mass less than 100kg" in the format, and the parameter load-to-mass ratio of the system model is established to satisfy this requirement.

[0120] like Figure 5 In SysML, the mathematical constraint of "quality <100" is automatically generated, which enables automatic verification of requirements and synchronous changes to the model when requirements change.

[0121] Step A3: Analyze and refine system requirements, obtain system design requirements from the system mission scenarios designed in the Operational Concept (ConOps), and then obtain the requirements of each level of aircraft systems, build a requirements map and generate a requirements matrix; combine Figure 6 The specific steps of step A3 are as follows:

[0122] Using the mission requirements obtained in step A1 as the input starting point, construct the system operation concept (ConOps), focusing on the interaction analysis between the aircraft system and external systems such as the remote control and telemetry center, system task switching, and system task process design to perform task analysis and define functional requirements; comprehensively utilize use case diagrams, activity diagrams, module definition diagrams, and sequence diagrams to refine the task process, and then conduct process analysis to obtain a series of system and subsystem function and performance requirements, such as the functional requirement that the control system should be able to control the launch segment and the orbit insertion segment. Gradually refine the requirements to the subsystem level, and then derive the requirements of each subsystem, especially the functional requirements; construct a system use case diagram, build an integrated aircraft usage scenario use case according to the mission requirements, and design system test cases at the same time.

[0123] Use SysML use case diagrams to build use cases for the integrated aircraft system, including launch, orbit entry, mission execution, and other usage scenarios, and build interactive relationships with operators. Build test cases to verify rapidity indicators.

[0124] like Figure 8 Build integrated aircraft rapid response use cases. Rapid response tasks include rapid testing, rapid benchmarking, rapid launch, and rapid deployment sub-use cases. The system boundary for these use cases is designed to be the integrated aircraft, and the operators associated with each use case are the command center, remote control and telemetry system, and launch maintenance personnel. Through the design of use cases, clarify the externally visible services provided by the system and the executors who trigger and participate in the tasks.

[0125] Step A4: Construct the behaviors of each aircraft system, perform functional clustering on the requirements, behaviors, and component mappings, and obtain the system requirements after redundancy optimization that meets the requirements of the integrated design;

[0126] The redundant optimization that conforms to the integrated design is specifically as follows: the spacecraft with an integrated satellite-rocket design controls the carrier segment by the orbital insertion segment, and by merging the same functions of different systems, especially the electrical and control systems of the last stage of the carrier segment as the core, the structural redundancy of repeated functions is reduced while meeting system requirements.

[0127] Design system behaviors based on subsystem requirements and establish the relationship between requirements and behaviors. For example, the control system has the function of controlling the launch segment and the orbital insertion segment, so it has states in the launch and orbital insertion phase and the mission phase. Build a state machine diagram and the corresponding behaviors under each state, such as controlling the ignition and separation of the launch segment during the orbital insertion phase and controlling the attitude and orbit control system during the mission phase. At the same time, allocate requirements to behaviors.

[0128] Conduct design synthesis iterations, preliminarily define system components, and allocate functional requirements to obtain functional architecture, such as Figure 7Use system modeling language and tools to generate behavior-design matrix, carry out subsystem function merger and structural redundancy removal, carry out new system function analysis and allocation for iterative design, and finally obtain an integrated logical functional architecture design plan that reduces excessive redundancy and meets system functional requirements.

[0129] For example, the composition of the control system is defined according to the control system behavior, and the control actuators of the launch segment and the orbital segment are defined using the module definition diagram. Then, the interaction relationship between them is defined using the internal module diagram. Therefore, the onboard computer required for interaction of the launch segment control system is merged into the onboard computer to construct the structure and interaction of the control system and the onboard data management system.

[0130] In step B, the following steps are specifically included:

[0131] Step B1: Construct the top-level model of the orbital insertion segment and the launch segment, define the interaction between them, and define the parameters;

[0132] Specifically, the top-level model uses SysML's block definition diagram (BDD) to construct system and subsystem structural blocks. The corresponding locations do not need to be fully defined. By leveraging the advantages of MBSE modeling, only the name of the structure or behavior needs to be defined to perform white-box structure and behavior definition. The definition of interaction mainly includes flows and ports, and its specific type and content can also be left unspecified when undetermined.

[0133] The specific methods for defining interactions and parameters are as follows: Figure 9 The top-level structure model of the system is constructed using the block definition diagram (BDD), including the integrated spacecraft and its lower orbital segment and carrier segment. The internal block diagram is constructed to define the interaction between the orbital segment and the carrier segment; other properties of the orbital segment and the carrier segment are defined, such as the value properties of parameters such as mass and power, as well as the status of the orbital segment.

[0134] The logical architecture design specifically involves: designing a white-box model of the required functionality and structure, enabling it to describe the implemented system. The white-box model constructed here focuses on the system's subsystems, the interactions between them, and the behaviors that the subsystems can implement. Step B2: Constructing the next-level logical architecture structural model for both the orbital insertion segment and the launch segment.

[0135] According to the overall design knowledge and demand analysis, such as Figure 10 Construct a module definition diagram to define the control systems of different sections, as well as the data management system, payload system, and other related subsystems of the carrier section. Construct an internal module diagram to define the interaction between the control system and the data management system, and assign the interactions in step A1 to the corresponding defined interactions.

[0136] Define the flow information corresponding to the interaction, including port names, information flows or physical flows transmitted by the interaction, and so on. For example, the sensor components in the control systems of the launch and orbital segments transmit measurement data to the launch segment's data management system, which in turn transmits control instructions to the corresponding control system's actuators. Flow and interface definitions here do not need to be specified with specific details. Instead, they can simply be replaced with block interfaces or flow types, specifying the content through naming.

[0137] Step B3: Assign behavioral requirements to each subsystem and define the states and behaviors of different subsystems;

[0138] By utilizing the allocation relationship of SysML, requirements and functions are allocated to the system structure model to achieve requirement coverage. At the same time, the defined system behavior is specifically modeled, including the system states and behaviors in different states, as well as the interactive joint behaviors between multiple subsystems represented by "signals".

[0139] like Figure 11 The constructed state machine diagram of the orbital spacecraft is responsible for controlling the carrier segment during orbital entry, controlling the orbital entry during the orbit period, and meeting the payload work requirements during the mission execution.

[0140] Based on this, different states and execution behaviors of different systems are constructed, with the focus on states and switching. The behavior process may not need to be detailed to how the behavior is implemented. For example, the measurement perception behavior of the sensitive element is defined as the basic activity of the activity diagram, and there is no need to further define the detailed behavior of the star sensor power-on measurement. Usually, such detailed behavior is designed in the physical stage.

[0141] Step B4: Define the interaction between different subsystems based on behavioral requirements.

[0142] Based on the cross-subsystem behaviors, the interactions between different subsystems are determined, and the ports and flows of the related subsystems are modeled to realize the interactions between different subsystems. At the same time, the activities of the subsystems are refined, including specifying the ports through which signals are sent and received in the activity diagram.

[0143] For example, the control system controls the detachment of the carrier segment, so that the state of the carrier segment changes from working to detached. The change of state is triggered by the signal on the different state lines of the state machine diagram. The signal is given by the control system, and it is necessary to specify which port of the carrier segment and the orbital segment the signal is transmitted through.

[0144] By continuously building the system's behavioral state and interactions, we can obtain the complete activities of the system at this level, that is, the system's behavioral logic architecture.

[0145] The physical architecture is specifically: a white box model corresponding to the logical architecture in step B, which enables the system to implement a physical model of its functions, including physical components, mechanisms, and equipment, etc. These physical models constitute the actual system;

[0146] In step C, the following steps are specifically included:

[0147] Step C1: Refine each subsystem to a physical component model, allocate requirements, and verify requirement coverage;

[0148] like Figure 12 The control system structure is refined. The control system includes sensitive elements and actuators. Sensitive elements include star sensors, gyroscopes, etc.; physical component structural blocks and parameter relationships are constructed, and the requirements of the subsystems are further allocated so that the system requirements can be verified by the actual components. The MBSE tool is used to generate a requirement relationship matrix to verify whether all system requirements are verified.

[0149] Step C2: Completely design the behavior of each subsystem;

[0150] The behavior of the subsystem is assigned to the physical components, and the basic behavior of the physical components realizes the behavior of the system execution according to different states and interaction relationships. For example, the sensitive components and actuators of the control system have standby, working and failure states, and the behavior of executing standby or working in different states, the corresponding system behavior such as executing orbit change, and detailed design such as controlling the power on and off of the orbit actuator, controlling the attitude execution system to adjust the attitude, and data transmission between the corresponding components and the onboard computer.

[0151] At the same time, it is necessary to define how to switch to backup components when certain components fail to ensure the normal operation of the system. This is also the key consideration of MBSE regarding the normal operation of the system, and it is also an advantage over traditional system engineering.

[0152] Step C3: Define the interactions between physical components within the subsystem, allocate the interactions between subsystems to physical components, and fully define the flows and ports of the interactions.

[0153] The complete definition of flows and ports specifically includes: defining the complete pattern of flows and ports in SysML, including port types and transmission flow types, and avoiding the common port definition inconsistency errors in traditional system engineering by modeling and defining each port in detail.

[0154] The specific method for step C3 is as follows: Based on the behavioral interactions of the physical components within the subsystem, define the interaction relationships between the physical components, including the relationship between ports and flows, and fully define the ports and flows of the physical components. For example, if the attitude-sensitive component is connected to the onboard computer via a cable, it should be composed of bilateral ports and information flows in the SysML model. Define the port type as a proxy port, define the transferred attitude measurement value attribute, define the information flow as an "item flow" type, and specify the transferred information type as the corresponding attitude measurement value attribute, ensuring consistency between ports and between corresponding flows. In addition, the type of value attributes, such as attitude measurement value attributes, should be stored in a dedicated SysML package for value attribute management.

[0155] In step D, the model library specifically models available commercial off-the-shelf (COTS) or existing models of physical components and integrates them into the system model, uses them as part of the model in the form of instances, selects them in system verification, and then performs parameter calculations.

[0156] The specific steps include:

[0157] Step D1: defining the required parameters of the physical components that can be used to construct the spectral library;

[0158] Step D2: define an instance of each physical component according to the existing model, assign parameters and store them;

[0159] According to the comparison between the physical components and the models they have, the parameter set required by the corresponding model in the system architecture model is obtained, and the corresponding SysML instance is constructed, such as Figure 13 Define the parameters of mass, power and thrust of a certain model of thruster, obtain the physical instance of the corresponding model, and define instances of other physical components with models to obtain the SysML type library.

[0160] Step D3: Generate a table of instances of the spectrum for easy query, and also allow modification, addition and deletion of instances in the table;

[0161] Step D4: Based on the specified task requirements, select a model instance and perform parameter simulation to verify whether the selected model set can meet the requirements;

[0162] Based on the indicator requirements, such as quality, the relationship between the system quality parameters and the quality parameters of the physical components has been realized in the system modeling. The physical component instances are selected for parameter assignment. The simulation calculation function of the MBSE modeling tool is used to automatically calculate the system parameters and perform indicator verification at the same time.

[0163] For example, verify the quality indicators of the aircraft, define the estimated mass of the structure and other systems, select the models of optional components including the load spectrum, simulate and calculate the total mass of the aircraft under the current spectrum set and the corresponding load ratio, and verify whether it meets the requirements.

[0164] In step E, the domain model specifically includes: non-MBSE language models that meet the various simulation requirements of aircraft operation, including trajectory calculation models, structural analysis models, attitude and trajectory control models, etc.; and models built in other software. Figure 14 The specific steps include:

[0165] Step E1: Build models for each domain and transform them to meet the requirements of integration according to the MBSE model specifications, and make them have interfaces for integration with the system architecture model;

[0166] For some software that supports FMI, FMU files can be generated and the FMI interface of the MBSE modeling tool can be used to integrate the system model and the domain model. For customized domain models, the interface form can be customized according to software requirements to enable the system architecture model to call the domain model and achieve model integrability.

[0167] Step E2: Perform model integration based on the characteristics of different models;

[0168] For parametric models, Matlab function scripts are generally integrated into the parametric diagram; control models generally use Simulink models, which can usually be directly integrated into SysML models;

[0169] For FMU models, they can be imported as blocks and the corresponding parameter relationships can be constructed for integration; for behavioral models, they need to be modified in the behavioral diagram for model integration.

[0170] In addition, non-SysML language models such as Java models can be used by calling opaque attributes in parameter diagrams or behavioral diagrams. For rapidity index verification, it is necessary to evaluate the launch segment carrier, such as Figure 14 It shows the multi-domain models that can be integrated in SysML, including aircraft domain models that support FMI interfaces, such as Ansys models. The orbit change strategy for orbit entry can be obtained through Matlab files, integrated into the corresponding parameter and behavior models, and then the Simulink model of the control system can be integrated to realize the verification of the control system during the orbit change.

[0171] Furthermore, for self-developed domain models, integrated simulation verification can be performed through customized FMI interfaces or behavioral diagram communication. Integrated models can be connected to parameter diagrams, module definition diagrams, behavioral diagrams, and other SysML diagrams, obtaining corresponding parameters from the SysML model and returning calculation results to the system model.

[0172] Step E3: Perform joint simulation to verify the system dynamic performance indicators;

[0173] For rapid dynamic multidisciplinary simulation, MBSE joint domain model simulation is carried out. Combined with the designed test cases, a simulation GUI is first built to facilitate manual operation of the control system behavior and status. The physical component spectrum is selected or the initial simulation value is manually assigned to perform simulation. The curves, timeline graphs and sequence diagrams output by the simulation are used to verify the various indicators of the system, focusing on the time required to enter orbit and reach the mission point, whether the corresponding indicators such as mass power under the time meet the requirements, and whether the selection of control system components is reasonable.

[0174] If it is unreasonable, you need to reselect the model or re-assign values ​​to other systems for simulation.

[0175] If no suitable results are obtained, we will return to the previous steps to redesign the system, look for any unreasonable or improved aspects in the design phase, or negotiate to modify system indicators and conduct iterative design.

[0176] In step F, the following steps are specifically included:

[0177] Step F1: By adjusting the parameters of the physical components, find a parameter set that can improve the system's load-to-mass ratio, load ratio and other indicators while meeting the requirements, as system parameter optimization;

[0178] Step F2: Optimize the processes involved in the system's behavior. Based on the sequence diagram and timeline diagram obtained from the simulation, optimize the behavior and adjust any unreasonable areas. The goal of optimizing the behavior is to increase the system's responsiveness.

[0179] Step F3: After obtaining an optimization solution that meets expectations in the feasible interval, freeze the system design and selection plan.

[0180] The overall system design is an iterative process. By taking advantage of MBSE, simulation verification can be continuously performed during the modeling process, and step iteration can be carried out in a timely and convenient manner if the verification fails.

[0181] Therefore, the design process is not completely followed Figure 1 In the linear design shown, different steps may have parallel, incremental and iterative designs according to the actual design situation. Figure 1 Only theoretical linear steps are shown, without indicating possible iterative processes. The characteristics of MBSE modeling ensure flexibility in system design, so iterations can occur at any stage.

[0182] An integrated aircraft design, optimization and evaluation system based on MBSE:

[0183] The system includes: a task requirement analysis subsystem, a logical architecture subsystem, a physical architecture subsystem, a spectrum library design and analysis subsystem, a simulation verification subsystem and a result output subsystem;

[0184] The mission requirement analysis subsystem is used to perform integrated aircraft mission requirement analysis after obtaining the mission requirement;

[0185] Conduct integrated aircraft mission requirement analysis, decompose and cluster the functional requirements of the integrated aircraft component systems, analyze the functions of subsystems at all levels under the MBSE process, and design behaviors and test cases;

[0186] The logical architecture subsystem is used to design the logical architecture;

[0187] Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages and build the flow relationship between different subsystems.

[0188] The physical architecture subsystem is used to design the physical architecture;

[0189] Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft, and allocate requirements to this level to achieve full coverage of requirements; improve parameter modeling and construct parameter diagrams to verify system indicators, such as load-to-mass ratio and power indicators; establish the status and behavior of each subsystem and improve the flow relationship between each physical component;

[0190] The type spectrum library design and analysis subsystem is used for designing and selecting type spectrum libraries;

[0191] Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators.

[0192] The simulation verification subsystem is used to perform joint simulation verification;

[0193] Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators;

[0194] The result output subsystem is used to optimize the system design scheme. According to the simulation results, the functions, structural models and parameters in the design scheme are adjusted to improve the system performance, and finally the system design and selection scheme is frozen.

[0195] An electronic device includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program.

[0196] A computer-readable storage medium is used to store computer instructions, which implement the steps of any of the above methods when executed by a processor.

[0197] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0198] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disc (SSD)).

[0199] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0200] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0201] The above describes in detail the MBSE-based integrated aircraft design method and system proposed in the present invention, and explains the principles and implementation methods of the present invention. The description of the above embodiments is only intended to help understand the method and core concept of the present invention. At the same time, for those skilled in the art, according to the concept of the present invention, there may be changes in the specific implementation method and application scope. In summary, the contents of this specification should not be understood as limiting the present invention.

Claims

1. An integrated aircraft design method based on MBSE, characterized by: The method specifically comprises the following steps: Step A: After obtaining the mission requirements, conduct integrated aircraft mission requirements analysis; Conduct integrated aircraft mission requirement analysis, build operational scenarios in SysML based on mission concepts to clarify system design requirements, decompose and cluster the functional requirements of the integrated aircraft component systems, merge the same functions of different components, analyze the functions of each subsystem under the MBSE process, and design behaviors and test cases; Step B: Build the logical architecture; Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages, and build the flow relationships and interfaces between different subsystems based on the interaction between behaviors. Step C: Design the physical architecture; Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft; improve parameter modeling and construct parameter diagrams to verify system indicators; establish the status and behavior of each subsystem, improve the flow relationship between each physical component, and define the interface in detail; Step D: Design and selection of spectral library; Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators. Step E: Joint simulation verification; Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators; Step F: Optimize the system design scheme. According to the simulation results, adjust the functions, structural models and parameters in the design scheme, and finally freeze the system design and selection scheme.

2. The method according to claim 1, wherein: In step A, the following steps are specifically included: Step A1: Determine the integrated aircraft mission requirements and build a model-based requirements library using the MBSE modeling language; Step A2: Construct an integrated aircraft terminology glossary; Step A3: Analyze and refine system requirements. Develop system design requirements from the system mission scenarios designed in the ConOps. Further, develop requirements for each level of the aircraft system, construct a requirements diagram, and generate a requirements matrix. Step A4: Construct the behaviors of each system of the aircraft, perform functional clustering by mapping the behaviors to components, and obtain the system requirements after redundancy optimization that meets the integrated design.

3. The method according to claim 2, wherein: The logical architecture specifically includes: designing a white box model of functions and structures that meet the requirements; In step B, the following steps are specifically included: Step B1: Construct the top-level model of the orbital insertion segment and the launch segment, define the interaction between them, and define the parameters; Step B2: Construct the next-level logical architecture structural model for the orbital insertion segment and the carrier segment respectively; Step B3: Assign behavioral requirements to each subsystem and define the composition, state, and behavior of different subsystems; Step B4: Define the interaction between different subsystems based on behavioral requirements.

4. The method according to claim 3, wherein: The physical architecture is specifically: a white box model corresponding to the logical architecture in step B, which enables the system to implement a physical model of its functions, including physical components, mechanisms, and equipment; In step C, the following steps are specifically included: Step C1: Refine each subsystem to a physical component model, allocate requirements, and verify requirement coverage; Step C2: Completely design the behavior of each subsystem; Step C3: Define the interactions between physical components within the subsystem, allocate the interactions between subsystems to physical components, and fully define the flows and ports of the interactions.

5. The method according to claim 4, characterized in that: In step D, the following steps are specifically included: Step D1: defining the required parameters of the physical components that can be used to construct the spectral library; Step D2: define an instance of each physical component according to the existing model, assign parameters and store them; Step D3: Generate an instance table of the spectrum; Step D4: Based on the specified task requirements, select a model instance and perform parameter simulation to verify whether the selected model set can meet the requirements; Specifically, the model library is to model available commercial off-the-shelf COTS or existing models of physical components and integrate them into the system model, use them as part of the model in the form of instances, select them in system verification, and then perform parameter calculations.

6. The method according to claim 5, characterized in that: In step E, the following steps are specifically included: Step E1: Build models for each domain and perform transformations to meet integration requirements according to the MBSE model specifications. Step E2: Perform model integration based on the characteristics of different models; Step E3: Perform joint simulation to verify the system dynamic performance indicators; The domain model specifically refers to a non-MBSE model that satisfies various simulations of aircraft operation, including a trajectory solution model, a structural analysis model, and a controller model.

7. The method according to claim 6, characterized in that: In step F, the following steps are specifically included: Step F1: By adjusting the parameters of the physical components, find a parameter set that can improve the system's load-to-mass ratio and load ratio indicators while meeting the requirements, as system parameter optimization; Step F2: Optimize the processes involved in the system's behavior and perform behavior optimization based on the sequence diagram and timeline diagram obtained from the simulation to increase the system's responsiveness. Step F3: After obtaining an optimization solution that meets expectations in the feasible interval, freeze the system design and selection plan.

8. An integrated aircraft design, optimization, and evaluation system based on MBSE, characterized by: The system is implemented based on the method according to any one of claims 1 to 7; The system includes: a task requirement analysis subsystem, a logical architecture subsystem, a physical architecture subsystem, a spectrum library design and analysis subsystem, a simulation verification subsystem and a result output subsystem; The mission requirement analysis subsystem is used to perform integrated aircraft mission requirement analysis after obtaining the mission requirement; Conduct integrated aircraft mission requirement analysis, decompose and cluster the functional requirements of the integrated aircraft component systems, analyze the functions of subsystems at all levels under the MBSE process, and design behaviors and test cases; The logical architecture subsystem is used to design the logical architecture; Build the logical architecture of the launch and orbital segments, decompose and allocate functions and behaviors, and define the top-level subsystems based on the requirements of the subsystems at all levels of the integrated spacecraft. At the same time, define the parameter library into the corresponding packages and build the flow relationship between different subsystems. The physical architecture subsystem is used to design the physical architecture; Refine the subsystem structure, parameters and behavior, and physical architecture of the integrated aircraft; improve parameter modeling and construct parameter diagrams to verify system indicators; establish the status and behavior of each subsystem and improve the flow relationship between each physical component; The type spectrum library design and analysis subsystem is used for designing and selecting type spectrum libraries; Build a library of candidate physical component models and integrate them into the model package corresponding to the system architecture in the form of instances. For given indicators, select the corresponding model components and verify the system static indicators. The simulation verification subsystem is used to perform joint simulation verification; Integrate domain models into system architecture models and conduct dynamic simulations to verify system operation indicators; The result output subsystem is used to optimize the system design scheme, adjust the functions, structural models and parameters in the design scheme according to the simulation results, and finally freeze the system design and selection scheme.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium for storing computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images