MBSE-based parameter-driven launch vehicle modeling method, device, equipment and medium

Abstract

The application discloses a parameter driving launch vehicle modeling method, device, equipment and medium based on MBSE, which comprises the following steps: demand modeling: capturing system demand, converting launch vehicle system stakeholder demand into complete specification full rocket system demand; parameter modeling: modeling physical parameters of the launch vehicle model, parameterizing the launch vehicle model, and forming a launch vehicle parameter index set; function modeling: through simulation of a function model, according to selected architecture; interface modeling; through a confirmation process of demand modeling of the launch vehicle, based on refinement and decomposition of a use case scenario of the launch vehicle, forming an interface of a launch vehicle system context model; physical modeling: describing the system architecture from the perspective of the launch vehicle physics, defining the relationship and parameters of the launch vehicle physical equipment and the interface thereof by organizing the launch vehicle physical elements, obtaining the physical architecture of the launch vehicle, and meeting the expected design attributes and technical indexes.

Description

Technical Field

[0001] This invention belongs to the field of aerospace technology, and in particular relates to a parameter-driven launch vehicle modeling method, device, equipment and medium based on MBSE. Background Technology

[0002] Launch vehicles are complex systems. The concept of a system originates from the fact that humans can build increasingly complex products. These structures and functions are no longer singular but rather a collection of interconnected elements organized in a coupled manner to achieve certain purposes, thus forming the concept of a system. A system is always greater than the sum of its elements, and it may also exhibit adaptive, dynamic, purposeful, self-sustaining, and evolutionary behavior. The MBSE model of a launch vehicle embodies the typical characteristics of a system.

[0003] In the traditional design process of launch vehicles, the overall rocket and its subsystems are designed using various documents, flowcharts, and fragmented data. Design information for each level of rocket product and subsystem, such as structure, pressurization and delivery, and engines, is typically stored in the minds of the respective rocket designers or on their personal computers. MBSE (Model-Based Design Experience) is an integrated process of design process and design result. It examines the entire process from requirements-function-logic-physical (R: Why do it?, F: What to do?, L: How to do it?, P: Product) and explicitly expresses the information traditionally stored in the designers' minds or personal computer documents, achieving transparency in the complex product development process of the entire launch vehicle system. Simultaneously, it uses an integrated launch vehicle model to express the complex system design intent of scheme demonstration, prototypes, and test samples. This allows for the complete recording of the overall design scheme from scratch, from basic to detailed, and from detailed to precise, expressing the entire lifecycle of the launch vehicle system design—from overall design to subsystems to individual units—within a unified model, thus achieving transparency in the launch vehicle development process.

[0004] The MBSE-based launch vehicle development model constructs a universal, all-element system model of the launch vehicle, encompassing the design process and results. Based on digital threads, it integrates CAD and CAE for structural, propulsion, electrical, and overall technology support, facilitating the expression and verification of the system design process. Furthermore, it integrates with traditional product models such as MCAD, ECAD, and CCAD, supporting upstream and downstream design transfer, thus forming an integrated MBSE model for launch vehicles, supporting applications across all scenarios, dimensions, and perspectives. Traditional launch vehicle MBSE modeling primarily utilizes the RFLP (Requirement-Function-Logic-Physical) approach.

[0005] (1) Requirements: Establish a requirements model for the launch vehicle system, including a requirements analysis of the system functions of the launch vehicle from the perspective of top-level requirements and usage scenarios.

[0006] (2) Function: Establish a model of the functions of each subsystem in the overall volume of the launch vehicle system.

[0007] (3) Logic: Establish a logical implementation model of the system among the various functional models of the launch vehicle.

[0008] (4) Physics: Establish the physical implementation of each system of the launch vehicle, and the specific physical model.

[0009] The digital transformation of launch vehicles emphasizes forward design and innovative design concepts. It ensures the correctness of the problem by establishing requirements and meets customer needs through functional design. By decomposing and integrating rocket functions, a functional decomposition is constructed. The abstract characteristics of models are then used to abstractly describe the operational mechanism of the launch vehicle system, forming a logical architecture layer that describes the optimal solution for the launch vehicle system. Finally, the product is realized, forming the final physical design of the launch vehicle.

[0010] See Figure 1 As shown, the traditional MBSE RFLP method establishes a confirmation and verification method for each requirement by itemizing and standardizing the expression and control of requirements, forming a requirement confirmation and evaluation system. Furthermore, during the requirement delivery process, the House of Functional Quality (QFD) is used to transform the requirements of relevant stakeholders into system requirements, defining the effectiveness evaluation indicators of the requirements. Through indicator decomposition and delivery, a quantitative and traceable system for requirements at all levels is formed. By defining a quantitative decision-making system for solution trade-offs, the traditional solution trade-offs are transformed from qualitative analysis and personal experience, and simulation verification models are integrated to conduct simulation verification of solutions, forming a data- and model-driven scientific decision-making system.

[0011] As the requirements for system development become more refined and quantitative tools become more advanced, the widespread application of quantitative, precise, and intelligent analysis methods has made system parameters increasingly important in system modeling. However, in the traditional MBSE RFLP methodology, parameters are scattered across various parts of requirements, functions, logic, and physical systems, increasing the complexity of the relationships between parameters and the complexity of modeling. This also hinders data analysis and maintenance. These problems are becoming increasingly prominent and urgently need to be addressed at the methodological level of MBSE. Summary of the Invention

[0012] The purpose of this invention is to provide a parameter-driven launch vehicle modeling method, device, equipment, and medium based on MBSE. On the basis of the classic methodological RFLP design framework, a parameter-driven MBSE modeling method, namely the RPFIP method (Requirements-Parametric-Functional-Interface-Physical), is proposed to guide the construction of the system design process model.

[0013] This invention provides a parameter-driven launch vehicle modeling method based on MBSE, comprising:

[0014] Requirements modeling: Capture system requirements and transform the needs of stakeholders in the launch vehicle system into complete and standardized system requirements for the entire rocket.

[0015] Parametric modeling: Modeling the physical parameters of the launch vehicle model, parametrically describing the launch vehicle model, forming a set of launch vehicle parameter indicators, summarizing the characteristic parameters of the launch vehicle system for closed-loop verification, and screening, refining, modifying and confirming system requirements. The parametric modeling is fully associated with the requirement model, functional model, interface model and physical model to form a parameter-driven system model.

[0016] Functional modeling: It serves as a bridge connecting top-level requirements and constraints with subsequent detailed system development and implementation. Through the simulation of the early functional model, based on the selected architecture, the detailed functions, interfaces, and timing characteristics required by the system are designed, forming a white-box functional set of the system. This enables the system to complete its predetermined task objectives and also builds requirement traceability and evidence to verify the satisfaction and traceability of requirements.

[0017] Interface modeling; through the confirmation process of launch vehicle requirements modeling, based on the refinement and decomposition of launch vehicle use case scenarios, the interface of the launch vehicle system context model is formed to ensure the correctness of the launch vehicle system composition scheme and improve the launch vehicle requirements model, functional model, parameter model and physical model.

[0018] Physical modeling: Describing the system architecture from the perspective of launch vehicle physics. By organizing the physical elements of the launch vehicle, defining the relationships and parameters between the physical devices and their interfaces, the physical architecture of the launch vehicle is obtained.

[0019] Preferably, the complete and standardized requirements for the entire rocket system include: analysis of stakeholder needs, use case scenarios throughout the launch vehicle's lifecycle, physical composition of the entire rocket system, and information related to system constraints and non-functional requirements.

[0020] Preferably, the modeling of the physical parameters of the launch vehicle model includes:

[0021] The overall system performance metrics (MOEs) are decomposed into the system design guide (MOP) and the technical performance metrics (TPMs) decomposed into each subsystem.

[0022] Preferably, the principles of the functional modeling include:

[0023] The top-down design principle of launch vehicles: functions are designed from the top-level composite functions of the launch vehicle down to the leaf node functions. The composite functions and leaf functions of the launch vehicle correspond to different levels. The composite functions of the launch vehicle correspond to the system or a series of single machines, or a series of components, forming functions that a single component or single machine does not have. Sub-functions correspond to the leaf functions of a certain component or single machine.

[0024] The principle of consistent functional granularity of launch vehicles: the functional granularity of the same level should be consistent. The functional architecture should be built layer by layer, from the top-level functions to the leaf nodes, layered composite, and finally forming the functional architecture.

[0025] The principle of mutual independence between functional modules: Each module of the launch vehicle adopts a modular structure and is independent of each other.

[0026] Preferably, the verification process through demand modeling of the launch vehicle further includes:

[0027] After determining the launch vehicle's technical specifications (TPM), establish a traceability relationship between the launch vehicle's TPM and logical units. Confirm that each logical unit of the launch vehicle has corresponding technical requirements and target measurement indicators to be met. Establish a traceability relationship between TPM and MOP, and confirm that the current specification decomposition scheme has achieved all MOP decomposition work.

[0028] Preferably, the interface modeling includes logical interfaces and physical interfaces. The logical interface is based on the logical composition of the launch vehicle system and combines the functions implemented by the launch vehicle's logical units. It sets the input-output relationships and content between logical units, including the associations between internal systems, the transmitted signals, and the associations between individual units and external systems. It clarifies the signal interface relationships and defines the transmitted signal codes, signal types, and signal transmission relationships. It is an interface reserved in the program that can realize data exchange and signal transmission functions. The launch vehicle physical interface refers to the hardware interface.

[0029] Preferably, the physical modeling is based on preset key principles, which include:

[0030] Inheritance: The inheritance of physical modeling of launch vehicle systems means that the physical architecture of launch vehicles should fully inherit the results of logical architecture design and requirements analysis, including the inheritance of system composition, functions, parameters and interfaces.

[0031] Compatibility: The compatibility of the physical architecture of a launch vehicle system refers to the fact that the parameters and interfaces in the physical architecture should match the parameters and interfaces of other systems in the context. Similarly, the parameters and interfaces between modules within the launch vehicle system should be compatible.

[0032] Layered design: The physical modeling of the launch vehicle system follows the principle of layered design, and is designed according to the launch vehicle system-individual machine-component. At each level, the scheme is weighed and selected. The selection includes selecting from the existing model library and adding new ones. Similarly, the interfaces are also divided into system interfaces, individual machine interfaces and component interfaces. The system interface is completed by a certain individual machine, and the individual machine interface is completed by a certain component.

[0033] Feasibility: The feasibility of the physical architecture of a launch vehicle system refers to the ability of the constituent modules, parameters, component selection, and interfaces in the physical architecture to be realized in the physical world, which is reflected in the fact that the architecture design results meet the system design constraints.

[0034] Satisfaction: Satisfaction of the physical architecture of a launch vehicle system means that the components, parameters, and interfaces in the physical architecture should meet the system requirements and the performance indicators after decomposition in the logical architecture, and be traceable to the system requirements and logical architecture to ensure that every design element of the launch vehicle physical architecture is traceable, rather than imagined out of thin air.

[0035] Verifiability: Verifiability of the physical architecture of a launch vehicle system means that the components and parameters in the physical architecture should be able to be verified by simulation and testing to ensure that the architecture design results can meet the system requirements.

[0036] The present invention also provides a parameter-driven launch vehicle modeling device based on MBSE, comprising:

[0037] Requirements modeling: Capture system requirements and transform the needs of stakeholders in the launch vehicle system into complete and standardized system requirements for the entire rocket.

[0038] Parametric modeling: Modeling the physical parameters of the launch vehicle model, parametrically describing the launch vehicle model, forming a set of launch vehicle parameter indicators, summarizing the characteristic parameters of the launch vehicle system for closed-loop verification, and screening, refining, modifying and confirming system requirements. The parametric modeling is fully associated with the requirement model, functional model, interface model and physical model to form a parameter-driven system model.

[0039] Functional modeling: It serves as a bridge connecting top-level requirements and constraints with subsequent detailed system development and implementation. Through the simulation of the early functional model, based on the selected architecture, the detailed functions, interfaces, and timing characteristics required by the system are designed, forming a white-box functional set of the system. This enables the system to complete its predetermined task objectives and also builds requirement traceability and evidence to verify the satisfaction and traceability of requirements.

[0040] Interface modeling; through the confirmation process of launch vehicle requirements modeling, based on the refinement and decomposition of launch vehicle use case scenarios, the interface of the launch vehicle system context model is formed to ensure the correctness of the launch vehicle system composition scheme and improve the launch vehicle requirements model, functional model, parameter model and physical model.

[0041] Physical modeling: Describing the system architecture from the perspective of launch vehicle physics. By organizing the physical elements of the launch vehicle, defining the relationships and parameters between the physical devices and their interfaces, the physical architecture of the launch vehicle is obtained.

[0042] The present invention also provides an electronic device, comprising:

[0043] The memory is used to store the processing program;

[0044] A processor, which, when executing the processing program, implements the MBSE-based parameter-driven launch vehicle modeling method as described in any one of claims 1 to 5.

[0045] Preferably, the present invention also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the MBSE-based parameter-driven launch vehicle modeling method as described in the embodiments of the present invention.

[0046] The beneficial effects of this invention compared to existing technologies are as follows: Based on the main problems existing in the current application of MBSE in modeling, and on the basis of the classic methodological RFLP design framework, a parameter-driven MBSE modeling method, namely the RPFIP method (Requirements-Parametric-Functional-Interface-Physical), is proposed to guide the construction of system design process models. Its main purpose is:

[0047] 1) Identify key requirements and key scenarios, and use parameters to drive the overall design of the launch vehicle.

[0048] Define key requirements and main scenarios, and design the overall parameters of the launch vehicle. The main task of parameter design is to decompose the overall system performance metrics (MOEs) into MOPs that can guide the system design, and technical performance metrics (TPMs) decomposed into each subsystem. That is, through small closed-loop verification of the overall design, the launch vehicle overall discipline is used to verify the initially defined system physical parameters. After iteration, other disciplines are added to carry out large closed-loop verification of the overall design.

[0049] 2) Refine key scenarios, coordinate with main scenarios, and use interface design to constrain the overall design of the launch vehicle.

[0050] This involves refining the key scenarios for launch vehicles, including flight scenarios, flight event chains, and collaborative transportation scenarios. It also includes designing flight procedures for launch vehicle flight scenarios and mechanical interfaces for protrusions on the rocket body. These findings will then constrain subsequent requirements analysis, architecture design, and other related work.

[0051] 3) Employing recursive and downstream iteration methods to enrich the overall design of launch vehicles.

[0052] The launch vehicle requirements capture and analysis adopts a recursive approach, repeatedly refining the functional requirements to more detailed and specific levels by identifying all stakeholders, scenarios, and processes across the entire rocket. Requirements development is achieved through system parameter design, overall ground design, and guidance schemes, iterating to more detailed and specific performance indicators. Launch vehicle system architecture development is achieved through downstream subsystem solutions, iterating to more specific and detailed subsystem requirements, and conducting requirements integration and allocation design to form subsystem mission specification models. Attached Figure Description

[0053] Figure 1 A schematic diagram of the traditional MBSE launch vehicle modeling method;

[0054] Figure 2 This is a schematic diagram of a parameter-driven MBSE modeling method for launch vehicles according to the present invention;

[0055] Figure 3 This is a schematic diagram of the requirement modeling in this invention;

[0056] Figure 4 This is a schematic diagram illustrating the requirement capture in this invention;

[0057] Figure 5 This is a schematic diagram of parameter modeling in this invention;

[0058] Figure 6 This is a schematic diagram of functional modeling in this invention;

[0059] Figure 7 This is a schematic diagram of the physical modeling in this invention. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0061] Example 1

[0062] like Figure 2 As shown, this invention provides a parameter-driven MBSE modeling method for launch vehicles, including the following steps:

[0063] S1: Requirements Modeling. Requirements modeling is the process of transforming the needs of launch vehicle stakeholders into complete and standardized system requirements for the entire rocket. This involves capturing system requirements by analyzing relevant information such as the needs of launch vehicle stakeholders, use case scenarios throughout the launch vehicle's lifecycle, the physical composition of the entire rocket system, system constraints, and non-functional requirements.

[0064] S2: Parametric Modeling. Modeling the physical parameters of the launch vehicle system for closed-loop verification, as well as for the selection, refinement, modification, and confirmation of system requirements. Parametric modeling is fully integrated with the requirement model, functional model, interface model, and physical model to form a parameter-driven launch vehicle system model.

[0065] S3: Functional Modeling. Launch vehicle functional modeling serves as a bridge connecting the top-level requirements and constraints of a launch vehicle with subsequent detailed system development and implementation. It helps to improve and update the requirements of the launch vehicle system. Through simulation of the early functional model, based on the selected architecture, the detailed functions, interfaces, and timing characteristics required by the launch vehicle system are designed, forming a white-box functional set of the launch vehicle system. This enables the launch vehicle system to complete its predetermined mission objectives. At the same time, it constructs requirement traceability and evidence to verify the fulfillment and traceability of requirements.

[0066] S4: Interface Modeling; Through the confirmation process of launch vehicle requirement modeling (functional requirements, performance requirements, and interface requirements), based on the refinement and decomposition of launch vehicle use case scenarios, the interface of the launch vehicle system context model is formed to ensure the correctness of the launch vehicle system composition scheme and improve the requirement model, functional model, parameter model, and physical model.

[0067] S5: Physical Modeling. Launch vehicle physical architecture describes the launch vehicle system architecture from a physical perspective. It defines the relationships and parameters between launch vehicle physical devices and their interfaces by organizing the launch vehicle's physical elements (components and interfaces). Its purpose is to describe specific, feasible launch vehicle solutions. Physical architecture provides a concrete solution for the development of launch vehicle systems that supports functional models and meets expected design attributes and technical specifications.

[0068] The specific explanation is as follows:

[0069] S1: Requirements Modeling

[0070] like Figure 3 As shown, the requirements engineering for launch vehicles is divided into two parts: requirements analysis and definition, and requirements management. Requirements analysis and definition includes requirements capture, requirements development, requirements definition, and requirements verification. Requirements management includes requirements entry into the database, requirements baseline establishment, requirements traceability, requirements release, requirements changes, and requirements change impact domain analysis.

[0071] Model-based launch vehicle systems engineering uses models to perform launch vehicle requirements analysis and definition, and then conducts various requirements management activities based on the launch vehicle requirements model. The launch vehicle requirements model expresses abstract launch vehicle requirements, requirements capture, and the development of launch vehicle requirements through concepts, symbols, mathematical models, and logic. Its expression methods include natural language, semi-formal methods such as tables and graphs, structured data, and formal expressions.

[0072] Launch vehicle requirements capture and development involves capturing the requirements of relevant stakeholders, analyzing and synthesizing this information, and verifying the feasibility and prioritization of requirements within the requirements set through the launch vehicle requirements development process. It also involves assessing errors, conflicts, and omissions in the requirements to obtain accurate and complete stakeholder requirements, launch vehicle system requirements, and a preliminary system architecture. The launch vehicle requirements development process is described in [link to relevant documentation]. Figure 4 .

[0073] Launch vehicle requirements definition is a comprehensive set of system requirements written using descriptive languages ​​and standard formats; it is also known as requirements specification and documentation. Using descriptive languages ​​and standard formats means using descriptive languages ​​such as SysML, OPL, and Capella, and writing requirements in a structured or semi-structured, itemized manner according to the requirements. The comprehensive set of requirements refers to the description of requirements at different levels during the development of complex launch vehicle products, specifically including requirements at the level of launch vehicle stakeholders, launch vehicle system level requirements, subsystem level requirements, and unit level requirements.

[0074] The set of requirements across all levels should satisfy six characteristics:

[0075] G. Completeness. Ensure that the requirements set includes all requirements for the launch vehicle and can serve as the basis for design and development at this level.

[0076] H. Consistency. There are no conflicting requirements within the same set of requirements for launch vehicles.

[0077] I. Traceability. There is a traceable correlation between the requirements of all levels of launch vehicles.

[0078] J. No redundancy. Within the same set of requirements for launch vehicles, each requirement is described only once.

[0079] K. Modularization. Requirements statements for the same problem related to launch vehicles are grouped together.

[0080] L. Structured. The launch vehicle requirements set has a clear model structure, making it quick and easy to find various requirements.

[0081] S2: Parametric Modeling

[0082] The launch vehicle model is parametrically described to form a set of launch vehicle parameter indicators. The characteristic parameters of the launch vehicle system are organized for closed-loop verification, as well as the screening, refinement, modification and confirmation of system requirements. The launch vehicle parameter modeling is fully associated with the requirement model, functional model, interface model and physical model to form a launch vehicle parameter-driven system model.

[0083] The main task of launch vehicle parameter design is to decompose the overall system performance metrics (MOEs) into Model Performance Parameters (MOPs) that guide system design, and into Technical Performance Parameters (TPMs) for each subsystem. Taking the overall launch vehicle design as an example, this involves verifying the initially defined system physical parameters through a small closed-loop verification of the overall launch vehicle design, utilizing the three disciplines of overall performance, ballistics, and aerodynamics. After iteration, other disciplines such as guidance, swaying, and attitude control are added, and combined with the dynamic characteristics, modes, swaying, and other system behaviors of the launch vehicle, a large closed-loop verification of the overall design is conducted. Figure 5 .

[0084] S3: Functional Modeling

[0085] Launch vehicle functional modeling moves from the problem domain to the solution domain, providing several possible launch vehicle solutions without involving specific physical implementations. The key principles of launch vehicle functional modeling include:

[0086] F. Top-down design principle for launch vehicles. Functional design begins with the top-level composite functions of the launch vehicle and then proceeds downwards to the leaf node functions. Composite functions and leaf functions correspond to different levels. Composite functions represent systems or a series of individual units, or a series of components, forming functions that a single component or unit cannot possess. Sub-functions correspond to the leaf functions of a specific component or unit.

[0087] G. Principle of Consistent Functional Granularity of Launch Vehicles. Functional granularity at the same level should be kept as consistent as possible. The functional architecture should be built layer by layer, from top-level functions to leaf nodes, with layered composites to finally form the functional architecture.

[0088] H. The principles of high cohesion, low coupling, and functional module independence. Interactions between different modules of the launch vehicle should be minimized. Each module of the launch vehicle should adopt a modular structural design, and the modules should be as independent as possible with minimal redundancy. Adding, removing, or modifying modules should have minimal impact on the overall system, facilitating improvements and expansions to the system's functionality, ensuring the system is constantly evolving and conducive to expansion and refinement.

[0089] I. Functional completeness refers to the fact that the launch vehicle system has complete and comprehensive functions, which can meet the needs of relevant stakeholders.

[0090] J. Functional reliability refers to the ability of the launch vehicle system to operate safely, reliably, and stably. See also Figure 6 As shown.

[0091] S4: Interface Modeling

[0092] Through the confirmation process of launch vehicle requirements modeling (functional requirements, performance requirements, and interface requirements), based on the refinement and decomposition of launch vehicle use case scenarios, the interface of the launch vehicle system context model is formed, ensuring the correctness of the launch vehicle system composition scheme and improving the requirements model, functional model, parameter model, and physical model.

[0093] After determining the technical performance indicators (TPM) of the launch vehicle, establish a traceability relationship between the launch vehicle TPM and the logical units, confirm that each logical unit of the launch vehicle has corresponding technical requirements and target measurement indicators to be met, establish a traceability relationship between TPM and MOP, and confirm that the current indicator decomposition scheme has achieved all MOP decomposition work.

[0094] This includes both logical interfaces and physical interfaces.

[0095] Launch vehicle logic architecture interface design. The launch vehicle logic interface is relative to the physical interface, which typically refers to a hardware interface such as a USB port. However, the logic interface is a reserved interface in the program that enables functions such as data exchange and signal transmission.

[0096] The logical architecture interface design is based on the logical composition of the launch vehicle system and combined with the functions implemented by the launch vehicle's logical units. It involves a detailed design of the input-output relationships and contents between logical units, including the internal connections between systems, the transmitted signals, and the connections between individual units and external systems. It clarifies the signal interface relationships and defines the transmitted signal codes, signal types, and signal transmission relationships.

[0097] After completing the design of the launch vehicle's logic interface, establish a traceability relationship between the interface and system requirements to confirm that the current interface design can meet the system requirements.

[0098] S5: Physical Modeling

[0099] The physical modeling of the launch vehicle system is based on several key principles to ensure that the design results meet the requirements of the launch vehicle system. These principles include inheritance, compatibility, hierarchical design, feasibility, satisfaction, and verifiability, such as... Figure 7 As shown.

[0100] Launch vehicle physics comprehensive analysis. Launch vehicle physics comprehensive analysis involves allocating logical elements to physical elements in a coordinated manner based on system characteristics and design experience.

[0101] Develop candidate physical architecture models for launch vehicles. For each physical synthesis analysis result, multiple candidate launch vehicle schemes should be developed.

[0102] Launch vehicle option trade-offs. For each physical element, different options should be traded off, evaluated, and the optimal option selected.

[0103] Inheritance. Inheritance in the physical modeling of a launch vehicle system means that the physical architecture of the launch vehicle should fully inherit the results of the logical architecture design and requirements analysis, including the inheritance of system composition, functions, parameters, and interfaces.

[0104] Compatibility. The compatibility of the physical architecture of a launch vehicle system refers to the requirement that the parameters and interfaces within the physical architecture match the parameters and interfaces of other systems in the context. Similarly, the parameters and interfaces between modules within the launch vehicle system should also be compatible. For example, the compatibility of the rated voltages between two individual unit interfaces.

[0105] Layered design. Physical modeling of launch vehicle systems should follow the principle of layered design, proceeding from launch vehicle system to individual unit to component. At each level, a trade-off and selection process should be conducted, including choosing from existing model libraries and developing new models. Similarly, interfaces are divided into system interfaces, individual unit interfaces, and component interfaces. A system interface can be implemented by a single unit, and a single unit interface can be implemented by a single component. For example, in a power supply and distribution system, the cable network is the system interface, used to connect various active units, while the electrical connectors in the cable network are the cable network interfaces, used to connect cables to external units.

[0106] Feasibility. The feasibility of the physical architecture of a launch vehicle system refers to the ability of the constituent modules, parameters, component selection, and interfaces within the physical architecture to be realized in the physical world. This is typically reflected in the fact that the architecture design results meet system design constraints. For example, the line current should be less than the rated current value of the cable.

[0107] Satisfaction. Satisfaction of the physical architecture of a launch vehicle system means that the components, parameters, and interfaces in the physical architecture should meet the system requirements and the performance indicators decomposed in the logical architecture. It should also be traceable to the system requirements and logical architecture to ensure that every design element of the launch vehicle's physical architecture is traceable and not just imagined out of thin air.

[0108] Verifiability. The verifiability of the physical architecture of a launch vehicle system refers to the ability of its constituent modules and parameters to be verified through simulation and testing, ensuring that the architecture design meets system requirements. For example, certain test devices should be designed within the system to monitor relevant parameter values ​​of critical components.

[0109] Based on the same concept, the present invention provides an electronic device comprising:

[0110] The memory is used to store the processing program;

[0111] The processor, when executing the processing program, implements the MBSE-based parameter-driven launch vehicle modeling method as described in the embodiments of the present invention.

[0112] The present invention provides a readable storage medium storing a processing program, which, when executed by a processor, implements the MBSE-based parameter-driven launch vehicle modeling method as described in the embodiments of the present invention.

[0113] This MBSE-based parameter-driven launch vehicle modeling device can vary significantly depending on its configuration and performance. It may include one or more central processing units (CPUs) and memory, and one or more storage media (e.g., one or more mass storage devices) for storing applications or data. The memory and storage media can be temporary or persistent storage. The program stored on the storage media may include one or more modules, each module comprising a series of instruction operations within the MBSE-based parameter-driven launch vehicle modeling device.

[0114] Furthermore, the processor can be configured to communicate with the storage medium and execute a series of instruction operations from the storage medium on the device that models the launch vehicle based on MBSE parameters.

[0115] A parameter-driven launch vehicle modeling device based on MBSE may also include one or more power supplies, one or more wired or wireless network interfaces, one or more input / output interfaces, and / or one or more operating systems, such as Windows Server, Vista, etc.

[0116] This invention also provides a computer-readable storage medium storing a computer program that, when executed by one or more processors, implements the MBSE-based parameter-driven launch vehicle modeling method as described in Embodiment 1. If the modules in Embodiment 2 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in software. The computer-readable storage medium can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of the MBSE-based parameter-driven launch vehicle modeling method in Embodiment 1.

[0117] Those skilled in the art will understand that the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in software. This computer software is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0118] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for MBSE-based parametric launch vehicle modeling, the method comprising: The method comprises the following steps: Requirement modeling: capturing system requirements, converting launch vehicle system stakeholder requirements into complete normative full-rocket system requirements, which include: analyzing stakeholder needs, launch vehicle full-life cycle use case scenarios, full-rocket system physical components, system constraints and non-functional requirement related information; Parameter modeling: modeling launch vehicle model physical parameters, parameterizing the launch vehicle model, forming a set of launch vehicle parameter indicators, summarizing launch vehicle system characteristic parameters for closed-loop verification, and screening, refining, changing and confirming system requirements, fully associating parameter modeling with requirement models, function models, interface models and physical models to form a parameter-driven system model; Function modeling: connecting top-level requirements, constraints and subsequent detailed system development and implementation, designing detailed functions, interfaces and timing characteristics required by the system through simulation of the function model, and forming a system white box function set; Interface modeling: through the confirmation process of launch vehicle requirement modeling, based on the refinement and decomposition of launch vehicle use case scenarios, forming launch vehicle system context model interfaces, ensuring the correctness of launch vehicle system composition scheme, and perfecting launch vehicle requirement model, function model and parameter model and physical model; Physical modeling: describing the system architecture from the perspective of launch vehicle physics, defining the relationship and parameters of launch vehicle physical devices and their interfaces by organizing launch vehicle physical elements, and obtaining the physical architecture of the launch vehicle.

2. The MBSE-based parameter-driven launch vehicle modeling method of claim 1, wherein, The launch vehicle model physical parameter modeling comprises: Decomposing system overall performance measure indicators MOEs into MOPs guiding system design and TPMs decomposed to each subsystem.

3. The MBSE-based parameter-driven launch vehicle modeling method of claim 1, wherein, The principles of function modeling include: Launch vehicle top-down design principle: function is set from launch vehicle top-level composite function to leaf node function, launch vehicle composite function and leaf function correspond to different levels, launch vehicle composite function corresponds to system or a series of single machines, or a series of components, forming a single component, single machine without function, sub-function corresponds to a component or single machine leaf function; Launch vehicle function granularity consistency principle: the granularity of functions at the same level is consistent, and the function architecture should be constructed layer by layer from top-level function to leaf node, hierarchical composition, and finally form a function architecture; Independence principle between function modules: each module of the launch vehicle adopts a modular structure, and the modules are independent of each other.

4. The MBSE-based parameter-driven launch vehicle modeling method of claim 1, wherein, The confirmation process of launch vehicle requirement modeling further comprises: After determining the launch vehicle technical indicators TPM, the traceability relationship between launch vehicle TPM and logical units is established, it is confirmed that each logical unit of the launch vehicle has corresponding technical requirements and target measure indicators to be met, the traceability relationship between TPM and MOP is established, and it is confirmed that the current indicator decomposition scheme realizes all MOP decomposition work.

5. The MBSE-based parameter-driven launch vehicle modeling method of claim 1, wherein, The interface modeling includes a logical interface and a physical interface, the logical interface is based on a logical composition of a launch vehicle system, and functions of a logical unit of the launch vehicle are implemented in combination, input and output relations and contents between logical units are set, including association between system internals, signals transmitted, and association between a single machine and an external system, interface relations of signals are clear, signal codes, signal types, and signal transmission relations are defined, the interface is reserved in a program, and data exchange and signal transmission functions can be implemented, and the physical interface of the launch vehicle refers to a hardware interface.

6. The MBSE-based parameter-driven launch vehicle modeling method of claim 1, wherein, The physical modeling is based on preset key principles, and the key principles include: inheritance: the inheritance of the physical modeling of the launch vehicle system refers to the fact that the physical architecture of the launch vehicle should fully inherit the design results and the demand analysis results of the logical architecture, including inheritance of system composition, inheritance of functions, inheritance of parameters, and inheritance of interfaces; matching: the matching of the physical architecture of the launch vehicle system refers to the fact that parameters and interfaces in the physical architecture should be matched with parameters and interfaces of other systems in a context environment, and parameters and interfaces between internal modules of the launch vehicle system also have matching; hierarchical design: the physical modeling of the launch vehicle system follows the hierarchical design principle, and is designed according to the launch vehicle system-single machine-component, and scheme trade-off and selection are performed in each level, the selection includes selection in an existing model library and addition, and interfaces are also divided into system interfaces, single machine interfaces, and component interfaces, the system interfaces are completed by a single machine, and the single machine interfaces are completed by a component; realizability: the realizability of the physical architecture of the launch vehicle system refers to the fact that constituent modules, parameters, component selection, and interfaces in the physical architecture should be able to be realized in the physical world, and the architecture design results meet system design constraints; satisfaction: the satisfaction of the physical architecture of the launch vehicle system refers to the fact that constituent modules, parameters, and interfaces in the physical architecture should meet system requirements and index requirements after decomposition in the logical architecture, and are traced back to the system requirements and the logical architecture; verifiability: the verifiability of the physical architecture of the launch vehicle system refers to the fact that constituent modules and parameters in the physical architecture should be able to be simulated and tested, and it is ensured that the architecture design results can meet system requirements.

7. An MBSE-based parameter-driven launch vehicle modeling apparatus, characterized by, include: demand modeling: capturing system requirements, converting launch vehicle system stakeholder requirements into complete and normative full launch vehicle system requirements, the complete and normative full launch vehicle system requirements include: analyzing stakeholder needs, launch vehicle full life cycle use case scenarios, full launch vehicle system physical composition, system constraints, and non-functional requirement related information; parameter modeling: modeling physical parameters of a launch vehicle model, parameterizing description is performed on the launch vehicle model, a parameter index set of the launch vehicle is formed, launch vehicle system characteristic parameters are summarized for closed loop verification, and system requirements are screened, refined, changed, and confirmed, the parameter modeling is associated with a demand model, a function model, an interface model, and a physical model, and a parameter driven system model is formed; Functional modeling: connecting top-level requirements, constraints and subsequent detailed system development and implementation, through the simulation of the early functional model, according to the selected architecture, the detailed functions, interfaces and timing characteristics required by the system are designed, and the white box function set of the system is formed, which is the system to complete the given task target, at the same time, the demand traceability is built to verify the satisfaction and traceability of the demand; Interface modeling: through the confirmation process of the demand modeling of the launch vehicle, based on the refinement and decomposition of the use case scenarios of the launch vehicle, the interfaces of the launch vehicle system context model are formed, which guarantees the correctness of the system composition scheme of the launch vehicle, and perfects the demand model, functional model and parameter model and physical model of the launch vehicle; Physical modeling: from the perspective of the physical of the launch vehicle, the system architecture is described, the relationship and parameters of the physical equipment of the launch vehicle and its interface are defined by organizing the physical elements of the launch vehicle, and the physical architecture of the launch vehicle is obtained.

8. An electronic device, comprising: Comprise: A memory for storing a processing program; A processor for implementing the MBSE-based parameter-driven launch vehicle modeling method according to any one of claims 1 to 6 when executing the processing program.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a processing program, and the processing program is executed by the processor to implement the MBSE-based parameter-driven launch vehicle modeling method according to any one of claims 1 to 6.

Images