Deep space exploration task system interface design method

Abstract

The invention discloses a deep space exploration task system interface design method, and belongs to the technical field of deep space exploration. The method comprises the following steps: extracting a deep space exploration field interface design knowledge ontology and extracting a semantic ontology; expanding a SysML meta-model to establish a field interface meta-model, and defining special versions and icons of electrical, mechanical, thermal, information and other ports; constructing a hierarchical domain interface model and an interface design model library, and realizing solidification and reuse of design knowledge; by configuring a packaged field interface view template, interface design in a graphical or tabular mode is supported; based on the template, an interface model is rapidly generated, coordinated and verified through drag multiplexing or form importing, and automatic verification of interface compliance, completeness, matching performance and binding performance is achieved. According to the invention, the standardization and cooperation efficiency of interface design are improved, and a systematized solution is provided for a deep space exploration task system interface.

Description

Technical Field

[0001] This invention belongs to the field of deep space exploration technology, specifically relating to a system interface design method for deep space exploration missions. Background Technology

[0002] Deep space exploration missions are characterized by complex system structures, high levels of technological integration, and tight coupling between multiple systems. Interface coordination between these systems is crucial for mission success. In traditional systems engineering practice, interface design primarily relies on Interface Control Documents (ICDs) and point-to-point coordination. This approach has several limitations: First, interface information is scattered across different documents, leading to inconsistent granularity and poor standardization in interface definitions, making ambiguity and omissions easy to occur. Second, the complex coupling relationships between interfaces lack visual representation, making it difficult to trace design changes and analyze their impact. Third, interface design knowledge is highly dependent on engineers' individual experience, making it difficult to accumulate and reuse, and ensuring design consistency across different projects or teams. Finally, interface verification often lags behind the design phase, typically only discovering compatibility and matching issues during system integration, resulting in high rework costs and significant risks of delays.

[0003] With the development of Model-Based Systems Engineering (MBSE) methods, the use of modeling languages ​​such as SysML for system design has become a trend. However, directly applying general-purpose SysML in specific fields such as deep space exploration still faces significant challenges: On the one hand, SysML language elements are general and abstract, requiring engineers to spend a lot of time learning and "translating" domain-specific knowledge into modeling elements, resulting in low modeling efficiency and a high risk of misuse; on the other hand, general-purpose modeling methods lack embedded support for domain design specifications and best practices, making it difficult to ensure that models meet the strict interface standards and constraints of the aerospace field, leading to inconsistent model quality and low reusability. In addition, existing SysML-based interface modeling often focuses on single-level or local functions, lacking a multi-level, integrated modeling framework covering the mission layer, system layer, and equipment layer, making it difficult to support global coordination and consistency management of interfaces between systems.

[0004] Therefore, there is an urgent need for a system interface design method that is tailored to the characteristics of the deep space exploration field, can integrate domain knowledge and modeling methods, and supports multi-level coordination and automated verification, so as to improve the standardization, collaborative efficiency and engineering reliability of interface design. Summary of the Invention

[0005] To address the aforementioned technical issues, this invention provides a system interface design method for deep space exploration missions. Through a hierarchical design approach, it progressively decomposes the interface design from top to bottom, refining it from the mission level to the system level. This iterative process, from requirements analysis to system design, refines the interface design and constructs a hierarchical and logically rigorous system modeling framework. This provides an efficient and scientific analysis and design path for complex deep space exploration systems engineering, contributing to improved overall system performance and reliability.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] The interface design methodology for deep space exploration mission systems includes:

[0008] Step 1: Based on the mechanism analysis of deep space exploration, extract the domain knowledge ontology from the interface control documents and project experience, and define the semantic ontology for interface design based on the domain knowledge ontology;

[0009] Step 2: Based on the semantic ontology, define the domain interface metamodel by extending the SysML basic metamodel, and establish visual icons and formal constraint rules for electrical ports, mechanical ports, thermal ports, information ports, and corresponding interfaces and connectors;

[0010] Step 3: Based on the domain interface meta-model, instantiate and generate a domain interface model, and organize it into a domain interface design model library, which includes a basic model library and a system interface model library;

[0011] Step 4: Customize the domain interface view template based on SysML. By encapsulating the underlying general primitives, the domain interface meta-model and the instance models in the domain interface design model library are presented in the form of business icons and terms on the graphical design interface, and the user is provided with a two-way conversion function between the view and the structured table.

[0012] Step 5: Quickly generate the system interface design model for the new task in the domain interface view template by dragging and dropping elements from the domain interface design model library or importing a structured form.

[0013] Furthermore, step 1 includes: Based on system interface control documents and project experience, key concepts, entities, attributes and their interrelationships in the field of deep space exploration interface design are extracted to form a domain knowledge ontology. By combining the hierarchical design process of system interfaces, the common characteristics of interfaces at different levels are abstracted and defined as key design elements and design element types, forming the semantic ontology.

[0014] Furthermore, in step 2, defining the domain interface metamodel includes: Based on the semantic ontology, elements with similar semantics in the SysML general meta-model are identified as base classes; Define templates on the base class to form a domain-related metamodel; The resulting domain-related meta-model is further described using labels and constraints to encapsulate domain specifications.

[0015] Furthermore, in step 2, establishing visual icons and formal constraint rules includes: Configure different exclusive icons for the interface metamodels of different domains for visual differentiation in the modeling environment; Based on aerospace standards and specifications, scripting languages ​​are used to describe and encapsulate these specifications, making them recognizable and analyzable by computers. The encapsulated rules are then combined with the domain interface meta-model to achieve automatic compliance checks during the modeling process.

[0016] Furthermore, step 3 includes: Based on the aforementioned domain interface meta-model, the meta-model concepts of electrical interface, mechanical interface, thermal interface, and information interface are instantiated into a state monitoring interface model, a power supply interface model, a fairing interface model, and a test docking interface model, which contain specific attributes, parameters, and constraint relationships. The instantiated interface models are organized into a domain interface design model library containing a basic model library and a system interface model library. The basic model library stores general interface type models, and the system interface model library stores specific interface configuration models extracted from historical model projects. Establish interface model import specifications based on metamodel constraints to ensure that all imported models conform to domain design standards, and establish a version management mechanism to achieve traceable and reusable models.

[0017] Furthermore, step 4 includes: In the SysML modeling environment, a dedicated graphical symbol library is created based on the model elements in the domain interface metamodel and domain interface design model library, replacing general SysML primitives with business icons that have domain semantics. Based on the different design stages and interface types of deep space exploration missions, multiple dedicated view templates are configured, with each template pre-configured with corresponding types of model elements and layout rules; Establish a two-way conversion relationship between domain interface views and structured tables to support automatic synchronization and consistency maintenance of design information across different representations.

[0018] Furthermore, step 5 includes: In the configured domain interface view, drag and drop predefined interface model elements from the domain interface design model library from the component bar, and combine them through graphical connections and attribute configuration to generate the interface design model for a new task; or, By importing structured forms that conform to a predefined format, the system automatically parses the interface definition information in the forms, generates corresponding structured interface models in batches based on the mapping relationship between the domain interface metamodel and the model library, and automatically synchronizes them to the domain interface view for visualization.

[0019] Furthermore, the method also includes: Based on the system interface design model of the generated new task, and according to the constraint rules encapsulated in the domain interface metamodel, at least one of the following is automatically verified: compliance, completeness, matching, and constraint of the interface. The verification results are fed back to the design view, and designers can modify and optimize the interface model based on the verification report, forming a closed-loop design iteration process.

[0020] In a second aspect, the present invention provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs; wherein, when the one or more programs are executed by the one or more processors, the one or more processors implement the aforementioned deep space exploration mission system interface design method.

[0021] Thirdly, the present invention provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enable the processor to implement the aforementioned deep space exploration mission system interface design method.

[0022] The beneficial effects of this invention are as follows:

[0023] First, this method extracts domain knowledge ontology and constructs a dedicated domain interface metamodel, solidifying deep space exploration interface design specifications, constraints, and best practices at the modeling language level, forming a "modeling dialect" for the aerospace field. This effectively solves the problems of high abstraction, high learning cost, and poor usability of the general-purpose SysML language in engineering applications, significantly reducing the application threshold of MBSE, enabling domain experts to directly use business terminology for accurate modeling, and ensuring the standardization and consistency of interface design.

[0024] Secondly, by building a hierarchical interface design model library and reusable view templates, design knowledge is assetized and efficiently reused. Engineers can quickly build and validate interface models by dragging and dropping predefined model elements or importing structured forms, avoiding repetitive work and human errors, improving interface design efficiency by more than 40%, while ensuring the inheritability and comparability of design results across projects and teams.

[0025] Most importantly, this method establishes an interface coordination and verification mechanism centered on a unique source of truth model. It supports automated verification of interface compliance, completeness, compatibility, and constraints in the early design stages, moving the problem discovery and resolution phase from the later integration testing stage to the design stage. This effectively reduces rework caused by interface incompatibility and is expected to reduce related engineering change costs by more than 30%, significantly improving the overall quality and reliability of deep space exploration system development. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of the interface design method for a deep space exploration mission system according to the present invention.

[0027] Figure 2 A schematic diagram illustrating the principle of meta-modeling for knowledge ontology;

[0028] Figure 3 Example of a domain interface metamodel icon;

[0029] Figure 4 A schematic diagram illustrating the definition of the domain interface metamodel;

[0030] Figure 5 A schematic diagram illustrating the rule encapsulation of the domain interface metamodel;

[0031] Figure 6 This is a structural diagram of the domain interface model;

[0032] Figure 7 This is a schematic diagram of the domain interface view template structure. Detailed Implementation

[0033] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0034] like Figure 1 As shown, this invention provides a method for designing system interfaces for deep space exploration missions, the method specifically including:

[0035] Step 1: Extraction of system interface knowledge ontology: Based on the mechanism analysis of deep space exploration, extract the domain knowledge ontology from the interface control documents and project experience, and define the semantic ontology for interface design based on the domain knowledge ontology;

[0036] Step 2, System Interface Metamodel Design: Based on the semantic ontology, the domain interface metamodel is defined by extending the SysML basic metamodel, and visual icons and formal constraint rules are established for electrical ports, mechanical ports, thermal ports, information ports, and corresponding interfaces and connectors.

[0037] Step 3: Construct a hierarchical interface design model: Based on the domain interface meta-model, instantiate and generate a domain interface model, and organize it into a domain interface design model library. The domain interface design model library includes a basic model library and a system interface model library.

[0038] Step 4: Configure Domain Interface View: Customize the domain interface view template based on SysML. By encapsulating the underlying general primitives, the domain interface meta-model and the instance models in the domain interface design model library are presented in the form of business icons and terms on the graphical design interface, and the user is provided with a two-way conversion function between the view and the structured table.

[0039] Step 5: Apply the interface design template: By dragging and dropping elements from the domain interface design model library or importing structured forms, quickly generate the system interface design model for the new task in the domain interface view template to achieve compliance, completeness, matching and constraint verification of the system interface.

[0040] Specifically, in step 1:

[0041] Knowledge ontology extraction involves abstracting common characteristics, constructing a semantic ontology based on these characteristics, and then refining the domain ontology. Based on interface control documents between systems and system modeling knowledge summarized from past project experience, combined with the domain's knowledge structure, important concepts, entities, attributes, and their interrelationships, a domain ontology is extracted. Furthermore, in conjunction with the hierarchical design process of system interfaces, common characteristics of interfaces at different levels are abstracted, and these common characteristics are defined as key design elements and design element types, forming a semantic ontology. The extraction of domain concepts and their attributes involves distinguishing three levels of concepts, which have an "is-a" relationship, meaning a lower-level concept is an instance of a higher-level concept: a) Domain concept: Represents a general concept within the domain, whose different attribute values ​​distinguish different entity types; b) Entity type: A specific entity instantiated from a domain concept, whose different attribute values ​​distinguish different entity instances; c) Entity instance: A specific instance that makes up the system, whose attributes have fixed values.

[0042] Furthermore, in deep space exploration missions, to effectively improve the design's systematicity and operability, and to align with the complexity, high reliability, and strict standardization of its design operations, the ontology content concepts at the interface level can be systematically organized from the following multi-dimensional perspectives, based on the MBSE system design methodology and combined with a hierarchical design approach.

[0043] In mission-level requirements analysis, for specific mission categories such as lunar south pole sampling and special terrain exploration, the mission boundaries are defined, and the interaction protocols that need to be pre-defined between systems to achieve specific missions are established. For example, when the probe lands, the robotic arm needs to establish precise data exchange (communication) with the control system (electrical) when performing sampling actions, while ensuring that the robotic arm's operating temperature (thermal) is within a safe range, among other interface requirements.

[0044] In the system-level requirements analysis phase, the focus is on the capabilities and performance metrics of each system, as well as the ways in which they collaborate, and clarifying how the systems work together to achieve the task objectives. Interfaces are used to describe the expected data exchange patterns, communication protocols, and service interfaces between different subsystems, as well as other abstract-level requirements.

[0045] In the process of mission-level system design, when it comes to constructing the overall system design scheme, the "electromechanical-thermal-communication interface" becomes one of the core elements to ensure the correct and error-free interaction of information, energy, and matter between various systems. Especially in the stage of verifying the interface compatibility between systems, these interfaces must be able to accurately reflect various changes under actual operating conditions, thereby ensuring the stability and reliability of the entire system.

[0046] At the system-level design level, when refining system workflows and defining system architecture, mechanical, electrical, thermal, and communication interfaces are not only physical connection points between various components within the system, but also crucial factors determining whether the entire system can operate normally. At this stage, interface design must consider not only electrical compatibility and thermal management, but also ensure that all signals arrive at the correct location at the correct time to complete the intended operation.

[0047] Taking the "Interface Control Document for a Certain Model and System" as an example, the interface requirements section can extract domain ontology, including electrical interface requirements and thermal control interface requirements. This ontology also includes specifications, indicators, and equipment, and instances of these are included in the interface file. Based on the domain ontology, the semantic ontology of the interface requirements is extracted. The interface requirements also include electrical and thermal requirements.

[0048] In step 2:

[0049] like Figure 2 As shown, the domain interface model is represented using a modeling language that employs syntax, semantics, constraints, and patterns defined by the metamodel. The mapping from the domain interface metamodel to the semantic ontology is a specialized expression of the metamodel concepts required for instantiated domain ontologies. System interfaces are represented in the domain interface view by instance interface models of the domain interface metamodel. The domain interface view allows for rapid reuse of domain interface model elements from the domain interface design model library in a graphical form.

[0050] In engineering tasks, to avoid designers performing a large amount of repetitive work defining specific, similar information, and to solidify the knowledge ontology into a model, it is necessary to model the interface design knowledge ontology. Modeling requires completing steps such as metamodel definition, model construction, model library design, and view configuration, resulting in the domain interface metamodel, domain interface model, domain interface design model library, and domain interface view, to more efficiently implement MBSE in practical work.

[0051] The domain interface metamodel aggregates metadata, schema mappings, and domain rules, representing a higher level of abstraction that shields the structural and semantic differences between model elements. Building upon the general SysML modeling language, the domain interface metamodel extends to establish a domain-specific metamodel, solidifying the domain's model representation standards at the tool level through digital means. This not only solves the problems of engineers finding it difficult and time-consuming to learn and master the SysML modeling language, but more importantly, it provides a unified and standardized modeling syntax and semantics for the aerospace field, fundamentally improving capabilities in standardized expression, modeling efficiency, reusability mechanisms, and knowledge accumulation.

[0052] Abstract concepts originate from model-based representations. After extracting the aforementioned domain knowledge, the next step is to abstractly define the domain ontology concepts expressed by its metamodel. This is basically done using basic syntax inherited from SysML, such as "port," "interface," and "connector." The domain interface metamodel discussed in this study consists of model elements that conform to the basic syntax constraints of SysML, and their basic meanings and usages are preserved.

[0053] Unlike traditional SysML modeling, metamodel modeling allows the use of "icons" within the metamodel to distinguish different metamodels. For designers, this approach is clearer, more explicit, and better suited to existing work habits. For example... Figure 3 As shown, different domain interface metamodels are distinguished by different icons.

[0054] Defining a specific syntax based on SysML involves the following three steps:

[0055] (1) For each element in the abstract syntax, it is first necessary to identify the general meta-model in SysML that is most similar to it in semantics;

[0056] (2) Then, based on this general metamodel, a stereotype is defined to form a domain-related metamodel;

[0057] (3) When necessary, labels and constraints are used to describe the newly created domain-related meta-model in more detail.

[0058] According to the interface design requirements for deep space exploration missions, such as Figure 4 The extended diagram shown represents the definition of the specific domain interface metamodel after the ontology concept was clarified and the abstract syntax was defined. For example, electrical ports, mechanical ports, information ports, and hot ports are all types of ports. For all architectures in the system, they can be classified into a corresponding metamodel. In terms of expression, this is reflected in the generalization and extension relationship of the metamodel to the basic base class metamodel. However, with only the port metamodel, it is difficult for designers to design system interfaces. Therefore, it is necessary to add interface module class metamodels such as hot interfaces, information interfaces, mechanical interfaces, and electrical interfaces as type elements of ports, and add connector class metamodels such as hot connections, information connections, mechanical connections, and electrical connections as connection elements of ports. This reflects the extensibility of the domain interface and conforms to the SysML modeling specification.

[0059] The domain interface metamodel represents specific concepts in its representation. To facilitate designers' understanding, a descriptive language can be added to the domain interface metamodel to solidify the understanding of ontology concepts. For semantic description, informal natural language or other formal languages ​​can be used. Here, we will explain the semantics of the domain interface metamodel defined above using natural language.

[0060] Based on standard specifications, scripting languages ​​are used to describe and encapsulate these specifications, making them recognizable and analyzable by computers. Combined with model specifications, the appropriate modeling specifications for different elements are customized, forming a domain interface metamodel that encapsulates rules. For example... Figure 5 As shown, taking the remote control execution status instruction as an example, the instruction field format consists of 15 bytes, with different bytes representing different parameters. The domain interface metamodel encapsulates the instruction reading rules, enabling the automatic reading of a series of parameters such as data flags, instruction code, command date, command time, execution date, and execution time from the input instruction.

[0061] In step 3:

[0062] The construction of domain interface models serves as a bridge between theory and practical applications. It involves not only concretizing abstract meta-models into operable interface designs, but more importantly, ensuring, through a series of rigorous standards, specifications, and tools, that this transformation process preserves the integrity of the original concepts while meeting the diverse needs of real-world projects. The core objective of domain interface model construction is to achieve a precise mapping from high-level meta-models to actual models, thereby providing a solid theoretical foundation and technical support for the analysis, design, and implementation of complex systems.

[0063] like Figure 6As shown, based on the domain interface metamodel, the concepts of electrical interface, mechanical interface, thermal interface, and information interface metamodels are instantiated into state monitoring interface, power supply interface, fairing interface, and test docking interface, each containing specific attributes, parameters, and constraints. After organization and management, the domain interface model can serve as a component of the domain interface design model library.

[0064] The purpose of the Domain Interface Design Model Library is to enhance the promotion and application of standards / specifications, products, and recognized knowledge and technologies by constructing a model library. This reduces the inconsistencies in the expression of repetitive elements across different models and the probability of errors, standardizes the content and process of modeling, improves model quality, and ensures the control of model content. The Domain Interface Design Model Library solidifies past MBSE experience and enables the management of model knowledge. The use of the model library allows for the summarization and classification of previous project models, providing a foundation for subsequent knowledge management. It facilitates the reuse of various types of models across different projects, reducing workload while ensuring the uniqueness of data sources and minimizing errors.

[0065] The instantiated interface models are organized into a domain interface design model library, which includes a basic model library and a system interface model library. The interface model library contains defined mechanical, electrical, thermal, and information interface models, and each interface model includes its performance requirements. The system interface model library contains model elements generated during previous model design processes. An interface model inclusion specification based on meta-model constraints is established to ensure all included models conform to domain design standards, and a version management mechanism is established to achieve traceable and reusable models. The domain interface models in the domain interface design model library will be configured in different domain interface views according to the library's organizational structure.

[0066] In step 4:

[0067] Domain interface views present interface information graphically. In actual modeling, a series of tables, matrices, and relationship maps are also used. These views, tables, and matrices all display a portion of the data information in a unique structured model, only in different forms. Sysml contains nine views, each with unique model elements. These views and model elements are often difficult to understand and learn, and inadequate understanding can lead to errors in their use. For example, standard ports, stream ports, complete ports, and proxy ports require a detailed understanding of their concepts and differences. However, by constructing a domain interface metamodel and a domain interface design model library, Sysml can be encapsulated, forming "business terminology" to describe interfaces. Business engineers can focus only on business-level matters without needing a detailed understanding of the underlying Sysml concepts. Customized domain interface views are simplified and expanded based on the nine Sysml diagrams. Elements unnecessary during design are removed from the component bar, while defined metamodel elements are added. By configuring the domain interface views, views that meet the designer's needs are obtained.

[0068] like Figure 7 As shown, in the configured domain interface view template, the component bar on the left encapsulates the metamodels and model libraries used in the interface design process. Different metamodels and different elements in the libraries are distinguished by their own identifiers. Designers can quickly design by dragging and dropping the basic model library in the component bar. In addition to supporting the display of interface designs in view form, it also supports converting the interface into a table format.

[0069] In step 5:

[0070] The application of system interface design model templates can be done in two ways: one is using domain view templates, and the other is using domain table templates. When designing in the software environment, users can drag and drop predefined model library elements from the left component panel, reusing model components that have been fixed in previous projects. This allows for the rapid generation of a complete model view with all characteristics, and the convenient viewing of various indicator items under the interface can be achieved using the view-to-table conversion function. Alternatively, users can design through forms. After completing the form, it can be imported into the software, and the system will automatically generate a structured model and corresponding views based on the information in the form. This ensures that users can efficiently and accurately build and optimize interface design models in various environments, ensuring that the design results are both compliant with standards and flexible.

[0071] Rapid design based on domain view templates:

[0072] Rapid design based on domain view templates aims to fully utilize existing resources, accelerate the model creation process, and ensure the quality and consistency of the generated interface models. In this way, users can quickly build model views, and the newly built interface models possess high consistency and reliability, ensuring that the generated interface models inherit all characteristics of elements in the library. Furthermore, it greatly simplifies the modeling process of complex systems, allowing designers to focus more on solving business logic problems rather than being bogged down in low-level technical details.

[0073] Following upstream design, it was determined that the launch vehicle system and the probe system have mechanical and electrical interfaces. Based on this, designers can select and drag model elements from the domain interface design model library in the left-hand component panel to the workspace to quickly design interface models. These model elements are standard components solidified from previous projects and are highly reusable.

[0074] Rapid design based on domain-specific table templates:

[0075] To simplify the interface model design process, lower the design threshold, and improve the efficiency of data transformation and modeling, the ability to quickly generate structured models from unstructured forms has become crucial. Traditional manual design and data transformation methods are not only time-consuming and labor-intensive but also prone to human error, affecting the quality of the final model. The ability to quickly generate models by importing domain form templates allows users to perform initial design within predefined domain form templates. Automated tools then parse, map, and reorganize the unstructured data in the forms into structured models that conform to specific modeling standards. This process significantly reduces repetitive work, improves efficiency, and ensures the consistency and accuracy of the generated models.

[0076] The designers completed the preliminary design of the status monitoring interfaces for the probe system and launch vehicle system using the domain form template. By parsing, mapping, and reorganizing unstructured tabular data into an interface model that conforms to specific modeling standards, the information in the form can be transformed into a structured model and view.

[0077] Based on the system interface design model of the generated new task, and according to the constraint rules encapsulated in the domain interface metamodel, at least one of the following is automatically verified: compliance, completeness, matching, and constraint of the interface. The verification results are fed back to the design view, and designers can modify and optimize the interface model based on the verification report, forming a closed-loop design iteration process.

[0078] In summary, based on hierarchical design, this invention delves into how to apply models to solidify the standards and specifications required for system interface design and reusable design experience. It establishes a model-based overall technical roadmap for system interface coordination. By extracting domain knowledge ontology for system interface design, it constructs a system interface model design template that includes a domain interface meta-model, a domain interface model, an interface design model library, and a domain interface view. This effectively carries the business information of system interface design, thereby supporting the overall definition, design, and coordination of system interface requirements for deep space exploration missions, ensuring the compliance, completeness, compatibility, and constraint of system interface design.

[0079] In a second aspect, the present invention provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs; wherein, when the one or more programs are executed by the one or more processors, the one or more processors implement the aforementioned deep space exploration mission system interface design method.

[0080] Thirdly, the present invention provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enable the processor to implement the aforementioned deep space exploration mission system interface design method.

[0081] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for designing a system interface for a deep space exploration mission, characterized in that, Comprise: Step 1, based on the mechanism analysis of deep space exploration field, extract the domain knowledge ontology from the interface control file and project experience, define the semantic ontology for interface design based on the domain knowledge ontology; Step 2, based on the semantic ontology, define the domain interface meta model by extending the SysML basic meta model, establish visual icons and formal constraint rules for electrical ports, mechanical ports, thermal ports, information ports and corresponding interfaces and connectors; Step 3, based on the domain interface meta model, instance generation domain interface model, and organize as domain interface design model library, the domain interface design model library includes basic model library and system interface model library; Step 4, customize the SysML based domain interface view template, encapsulate the underlying general graph element, present the domain interface meta model and instance model in the domain interface design model library in the form of business icon and term in the graphical design interface, and provide the user with the function of bidirectional conversion between view and structured table; Step 5, quickly generate the system interface design model of new task in the domain interface view template by dragging the domain interface design model library elements or importing the structured table.

2. The deep space exploration mission system interface design method of claim 1, wherein, The step 1 comprises: According to the system interface control file and project experience, extract the key concepts, entities, attributes and their mutual relations in the field of deep space exploration interface design, form the domain knowledge ontology; Abstract the common characteristics of different levels of interface, define them as key design elements and design element types, and form the semantic ontology.

3. The deep space exploration mission system interface design method of claim 1, wherein, In step 2, the definition of domain interface meta model comprises: Based on the semantic ontology, identify the elements with similar semantics in the SysML general meta model as the base class; Define the version on the base class to form the domain related meta model; Further describe the formed domain related meta model with tags and constraints to encapsulate the domain specification.

4. The deep space probe mission system interface design method of claim 1, wherein, In step 2, the establishment of visual icon and formal constraint rule comprises: Configure different exclusive icons for interface meta models of different fields to realize visual differentiation in the modeling environment; Based on the standard specification of aerospace field, describe and encapsulate the specification by using script language, so that it can be recognized and analyzed by computer; combine the encapsulated rules with the domain interface meta model to realize automatic compliance check in the modeling process.

5. The deep space probe mission system interface design method of claim 1, wherein, The step 3 comprises: Based on the domain interface meta model, instance the meta model concepts of electrical interface, mechanical interface, thermal interface and information interface into state monitoring interface model, power supply interface model, fairing interface model and trial docking interface model containing specific attributes, parameters and constraint relationships; Organize the instantiated interface model into domain interface design model library containing basic model library and system interface model library, wherein the basic model library stores general interface type model, and the system interface model library stores specific interface configuration model extracted from historical model project; Establish the interface model storage specification based on meta model constraint to ensure that all the stored models meet the domain design standard, and establish the version management mechanism to realize the traceable reuse of the model.

6. The deep space probe mission system interface design method of claim 1, wherein, The step 4 comprises: In the SysML modeling environment, based on the model elements in the domain interface meta-model and the domain interface design model library, a dedicated graphical symbol library is created, and the general SysML graph elements are replaced by business icons with domain semantics; According to different design stages and interface types of deep space exploration missions, multiple dedicated view templates are configured, each of which preloads model elements and layout rules of the corresponding type; A bidirectional conversion relationship between the domain interface view and the structured table is established to support automatic synchronization and consistency maintenance of design information between different forms.

7. The deep space probe mission system interface design method of claim 1, wherein, The step 5 comprises: In the configured domain interface view, interface model elements from the domain interface design model library are dragged from the component bar, and the interface design model of the new task is generated by graphical connection and attribute configuration; or, By importing a structured table in a predefined format, the system automatically parses the interface definition information in the table, generates corresponding structured interface models according to the mapping relationship between the domain interface meta-model and the model library, and automatically synchronizes them to the domain interface view for visual display.

8. The deep space probe mission system interface design method of claim 1, wherein, The method further comprises: Based on the generated system interface design model of the new task, at least one of compliance, completeness, matching and constraint of the interface is automatically checked according to the constraint rules encapsulated in the domain interface meta-model; The checking result is fed back to the design view, and the designer is supported to modify and optimize the interface model based on the checking report, forming a closed-loop design iteration process.

9. An electronic device, comprising: Comprise: One or more processors; Memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the deep space exploration mission system interface design method of any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, Executable instructions are stored thereon, which are executed by the processor to enable the processor to implement the deep space exploration mission system interface design method of any one of claims 1-8.

Images