Normalized ontology definition method and system for model-based system engineering and equipment system

By based on the definition of top-level ontology of BFO, CCO, and IAO, the unified problem of system engineering and equipment system concepts is solved, knowledge sharing and collaborative research and development are realized across industries, and the application of MBSE in different industries and multi-equipment system design is supported.

CN118964628APending Publication Date: 2024-11-15TSINGHUA UNIVERSITY
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202410880631.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-02
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The lack of a unified top-level ontology guidance system engineering process method and equipment system concept in the existing technology has led to incompatible equipment system ontology in cross-industry fields, making it difficult to achieve collaborative research and development and knowledge sharing across industries.

Method used

Based on three top-level bodies: basic regular body BFO, core layer body CCO, and information product body IAO, we define the core concepts and relationships between system engineering and equipment systems, and form system ontology, model-based system engineering MBSE ontology and equipment field-oriented system Ontology, achieve unity and consensus across industries.

Benefits of technology

Through the unified top-level ontology definition, it promotes the knowledge sharing and mutual recognition of cross-industry fields of system engineering and equipment systems, supports the application of MBSE in different industry fields and the design and collaborative research and development of multi-equipment systems across industries, laying the foundation for MBSE intelligence The basis of

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118964628A_ABST
    Figure CN118964628A_ABST
Patent Text Reader

Abstract

The invention discloses a normalized ontology definition method and system oriented to a model-based system engineering and equipment system, and the method comprises the steps: carrying out the definition and modeling of the core concept and relation of a system related to the system engineering based on three top ontologies, namely a basic normalized ontology BFO, a core layer ontology CCO and an information product ontology IAO; forming a system body; according to the formed system ontology and based on three top ontologies of BFO, CCO and IAO, defining core concepts and relationships related to model-based system engineering practical activities to form a model-based system engineering MBSE ontology; and according to the formed system ontology and based on three top ontologies of BFO, CCO and IAO, defining and describing core common concepts and relationships of the equipment system in the specific industry field, so as to form the system ontology oriented to the equipment field. According to the method, the unification problem of the equipment system ontology in the cross-industry field, the consensus problem of the cross-industry field for the core concept of the model-based system engineering (MBSE) and the unification problem of the definition of the equipment-field-oriented system ontology and the definition of the model-based system engineering (MBSE) ontology are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of model-based system engineering, and in particular to a method and system for defining a normalized ontology for model-based system engineering and equipment systems. Background Art

[0002] In the promotion and application of model-based systems engineering (MBSE), it is necessary to formally express model-based systems engineering knowledge to achieve knowledge reuse across disciplines, professions, and application objects. Among them, the systems engineering knowledge needs to be formally expressed from the following two aspects: First, the expression of the systems engineering process method. The reuse of model-based systems engineering best practices in the development of different products and the collaborative development of cross-industry fields need to be based on a consensus on the concepts of systems and systems engineering to ensure the unity of the process methods followed; second, the expression of the concepts of systems engineering objects. When applying the model-based systems engineering process method, the knowledge concept of the application object should be based on a unified abstract classification to ensure the completeness of the object knowledge expressed by the model.

[0003] Ontology is a standardized description of shared concepts in the object domain, expressing the consensus of the group in the object domain, describing the recognized objective knowledge in the domain, and including concepts and the relationships between concepts. Based on the standard of whether the ontology is domain-specific, the ontology can be divided into top-level ontology, domain ontology and application ontology. Among them, the top-level ontology is a formalized ontology, which is a highly general representation of the categories and relationships common to all domains. The top-level ontology provides universally applicable basic concepts and relationships as the basis for building domain ontologies and specific application ontologies. For different domain ontologies, their shared unified top-level ontology ensures that these domain ontologies can interoperate and share concepts; domain ontology is an ontology built for a specific domain, used to express concepts and knowledge in the domain. By using the basic concepts and relationships provided by the top-level ontology, different domain ontologies can interoperate and realize cross-domain knowledge sharing and exchange; application ontology is an ontology designed for specific purposes or key applications. Application ontology is usually used at the intersection of cross-domains or disciplines, and generates cross-top-level, core-layer and domain ontologies for specific user groups. At present, there are many top-level ontologies, among which the typical examples are Basic Formal Ontology (BFO), Common Core Ontology (CCO), Information Artifact Ontology (IAO), etc. Among them, BFO is based on the philosophy of ontological realism, which believes that the ontology represents the universal characteristics of reality itself. CCO is a middle-level extension of the Basic Formal Ontology (BFO), which contains a total of 11 ontology sets, expressing and integrating concepts and relationships across all relevant fields. IAO is also a middle-level extension of the Basic Formal Ontology (BFO). It is a domain-neutral expression of information content entities and is suitable for the representation of various information content entities such as documents, databases, digital images, etc. Due to the connection between BFO, CCO, and IAO, they can jointly guide the establishment of domain ontologies.

[0004] In order to express the concept of system engineering, INCOSE summarized the core concepts of system engineering in the System Engineering International Body of Knowledge (SEBOK), integrated the description of systems and system engineering in ISO / IEC / IEEE 15288:2015 and the 4th edition of the INCOSE System Engineering Handbook, and proposed the System Engineering Concept Model (SECM). Bruce McNaughton et al. proposed the system concept model based on the results of the EU Comprehensive Modelling for Advanced Systems of Systems (COMPASS, grant agreement 287829) project and their research on systems and earth systems. British scholar Jon Holt proposed the MBSE ontology based on his research on system engineering, especially model-based system engineering, for many years. However, SECM and the system concept model proposed by Bruce McNaughton are mainly oriented to the concepts and relationships of the system, and lack the description of the concepts related to the process method of system engineering. The MBSE ontology proposed by JonHolt also includes the concepts and relationships of systems and system engineering, but it does not use a formal top-level ontology.

[0005] In order to express the concept of equipment system, various industries have formed their own system ontology for equipment field based on years of practical experience. The concepts and knowledge of equipment system in related industry fields have been summarized and expressed to guide the development of specific types of equipment systems, usually in the form of manuals, standards, guidelines, etc. For example, the "Aircraft Design Manual" in the aviation field, the "Missile and Space Series" in the aerospace field, the "Ship Design Practical Manual" in the ship field, and the "Radar Manual" in the radar field. However, most of the system ontologies that have been formed for equipment field are summarized based on the practical experience of the industry field to which the equipment system belongs, lacking the formal classification guidance of the top-level ontology. Different equipment system ontologies are incompatible with each other, which brings inconvenience to the system design and collaborative development of multiple equipment in cross-industry fields. At the same time, the equipment systems in various industry fields are the application objects of system engineering, and the concepts and relationships described by the system engineering ontology are also the common knowledge followed by the development of equipment systems in various industry fields. However, the current research lacks the use of a unified top-level ontology to provide common guidance for both. Summary of the invention

[0006] The present invention aims to solve one of the technical problems in the related art at least to a certain extent.

[0007] To this end, the present invention proposes a definition method and system for uniformly defining model-based systems engineering (MBSE) ontology and system ontology for equipment field based on three top-level ontologies: BFO, CCO and IAO, so as to solve the problem of unifying equipment system ontology across industries, the problem of consensus on the core concepts of model-based systems engineering (MBSE) across industries, and the problem of unifying the definition of system ontology for equipment field and model-based systems engineering (MBSE) ontology.

[0008] Another object of the present invention is to propose a formalized ontology definition system for model-based system engineering and equipment systems.

[0009] To achieve the above-mentioned object, the present invention proposes a method for defining a formalized ontology for model-based system engineering and equipment systems, comprising:

[0010] Based on the three top-level ontologies of basic formalized ontology BFO, core layer ontology CCO and information product ontology IAO, the core concepts and relationships of the system involved in system engineering are defined and modeled to form a system ontology;

[0011] According to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, the definition of core concepts and relationships related to model-based system engineering practice activities is expanded to form the MBSE ontology of model-based system engineering; and,

[0012] According to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, the core common concepts and relationships of equipment systems in specific industry fields are defined and described to form a system ontology for the equipment field.

[0013] In addition, the formalized ontology definition method for model-based system engineering and equipment system according to the above embodiment of the present invention may also have the following additional technical features:

[0014] Furthermore, in one embodiment of the present invention, the system ontology includes the following concepts:

[0015] system, element, product system, service system, port, structure, environment, life cycle, life cycle model, life cycle phase, behavior, state, event, state space, state transition, function, mode, mode transition, interface, stakeholder, purpose.

[0016] Furthermore, in one embodiment of the present invention, the model-based systems engineering ontology includes the following concepts: system, element, product system, service system, port, structure, environment, life cycle, life cycle model, life cycle stage, behavior, state, event, state space, state transition, function, mode, mode transition, interface, stakeholder, purpose, need, business mission need, stakeholder need, requirement, stakeholder need, system requirement, background environment, external system, system of interest, operation scenario, life cycle concept, support concept, operation concept, exit concept, deployment concept, acquisition concept, process, business role, artifact, activity, architecture, functional architecture, functional interface, object flow, control flow, logical architecture, logical component, logical component interface, logical component behavior, physical architecture, object flow, physical component, physical component interface, physical component behavior, view, view element, perspective, competence, knowledge, skill, talent, attitude, project, sub-project, organization, resource, modeling language and modeling tool.

[0017] Furthermore, in one embodiment of the present invention, the system ontology for the equipment field includes the following concepts:

[0018] Equipment system, equipment system function, attitude control function, chemical reaction function, communication function, communication interference function, communication reception function, communication relay function, computing function, cooling function, destruction function, deception function, detonation function, electrical function, electromagnetic induction function, electromagnetic shielding function, fluid control function, friction reduction function, fuel function, heating function, imaging function, impact shielding function, motion suppression function, life support function, lifting function, measurement function, motion function, navigation function, detection function, optical processing function, direction control function, load capacity, power supply function, reflection function, refraction function, sensor function, signal detection function, signal processing function, structural support function, thermal control function, timing function, ventilation control Function, maintenance function, vehicle, aircraft, ground vehicle, rocket, spacecraft, water vehicle, weapons, cutting weapons, explosive weapons, incendiary weapons, ammunition, launcher, engine, electric engine, thermal engine, physical power engine, reactive engine, environmental control system, cabin pressure control system, cooling system, heating system, equipment fixture, control system, generator control unit, propulsion control system, vehicle control system, communication system, intercommunication system, public broadcasting system, telecommunications network, fuel system, navigation system, power transmission system, propulsion system, vehicle frame, payload, environmental characteristics, human characteristics, geographical characteristics, equipment system role, component role, infrastructure role, part role, system role.

[0019] Further, in one embodiment of the present invention, a system ontology concept relationship definition table (Table 2) is constructed based on the concepts included in the system ontology, and the corresponding relationship classifications and relationship types;

[0020] Based on the concepts contained in the MBSE ontology, as well as the corresponding relationship classifications and relationship types, the MBSE ontology concept relationship definition table is constructed (Table 4);

[0021] Based on the concepts contained in the system ontology for the equipment field, as well as the corresponding relationship classifications and relationship types, a concept relationship definition table in the system ontology for the equipment field is constructed (Table 6).

[0022] Further, in one embodiment of the present invention, the relationship classification in the system ontology concept relationship definition table includes basic relationships, spatiotemporal relationships, and dependency relationships;

[0023] The relationship classification in the MBSE ontology concept relationship definition table includes spatiotemporal relationship, correlation relationship, dependency relationship, basic relationship, carrying relationship and realization relationship;

[0024] The relationship classification in the concept relationship definition table in the equipment field-oriented system ontology includes basic relationships.

[0025] A formalized ontology definition system for model-based system engineering and equipment systems according to an embodiment of the present invention includes:

[0026] The system ontology definition module is used to define and model the core concepts and relationships of the system involved in system engineering based on the three top-level ontologies: basic formalized ontology BFO, core layer ontology CCO, and information product ontology IAO, to form a system ontology;

[0027] MBSE ontology definition module, used to expand the definition of core concepts and relationships related to model-based system engineering practice activities based on the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, so as to form a model-based system engineering MBSE ontology; and

[0028] The system ontology definition module for the equipment field is used to define and describe the core common concepts and relationships of equipment systems in specific industry fields according to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, so as to form a system ontology for the equipment field.

[0029] The formalized ontology definition method and system for model-based systems engineering and equipment systems in the embodiments of the present invention formally describe the core concepts and relationships of the objects, methods, and application objects studied by MBSE based on the same top-level ontology, and establish interconnected system ontology, model-based systems engineering ontology, and equipment system ontology.

[0030] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0032] Figure 1 is a flow chart of a method for defining a formalized ontology for model-based systems engineering and equipment systems according to an embodiment of the present invention;

[0033] Figure 2 is a relationship diagram of a system ontology, an MBSE ontology, and a system ontology oriented to the equipment field according to an embodiment of the present invention;

[0034] Figure 3 is a structural diagram of a formalized ontology definition system for model-based systems engineering and equipment systems according to an embodiment of the present invention;

[0035] Figure 4 is an aircraft function definition structure diagram based on a system ontology oriented to the equipment field according to an embodiment of the present invention;

[0036] Figure 5 is a satellite function definition structure diagram based on a system ontology oriented to the equipment field according to an embodiment of the present invention;

[0037] Figure 6 It is a radar function definition structure diagram based on a system ontology oriented to the equipment field according to an embodiment of the present invention. DETAILED DESCRIPTION

[0038] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0039] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0040] The following describes a method and system for defining a normalized ontology for model-based system engineering and equipment systems according to an embodiment of the present invention with reference to the accompanying drawings.

[0041] Figure 1 It is a flow chart of a method for defining a normalized ontology for model-based system engineering and equipment systems according to an embodiment of the present invention.

[0042] like Figure 1 As shown, the method includes but is not limited to the following steps:

[0043] S1, based on the three top-level ontologies of basic formalized ontology BFO, core layer ontology CCO and information product ontology IAO, defines and models the core concepts and relationships of the system involved in system engineering to form a system ontology;

[0044] S2, based on the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, expand the definition of core concepts and relationships related to model-based system engineering practice activities to form a model-based system engineering MBSE ontology; and,

[0045] S3, according to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, defines and describes the core common concepts and relationships of equipment systems in specific industry fields to form a system ontology for the equipment field.

[0046] Specifically, the concepts and relationships involved in the research object of system engineering, the process method of system engineering, and the application objects of system engineering in the real industry field are defined respectively, forming three ontologies: system ontology, model-based system engineering (MBSE) ontology, and system ontology for the equipment field. Among them, the system ontology focuses on the description of the core concepts and relationships of the system involved in system engineering; the model-based system engineering ontology focuses on the description of the core concepts related to the system engineering practice activities carried out with the system as the core; the system ontology for the equipment field focuses on the description of the core common concepts and relationships of the equipment systems in different industry fields in reality.

[0047] Specifically, the definitions of the above-mentioned system ontology, model-based system engineering ontology, and system ontology for the equipment field are based on the same three top-level ontologies: BFO, CCO, and IAO, and there is the following relationship between the three ontologies: the model-based system engineering ontology contains the system ontology, and the system ontology for the equipment field inherits the system ontology. Figure 2 shown.

[0048] It can be understood that the formalized ontology definition system for model-based system engineering and equipment systems consists of three ontologies: the defined system ontology, the model-based system engineering ontology, and the system ontology for the equipment field. Each ontology contains concept composition, concept definition, and concept relationship definition.

[0049] In one embodiment of the present invention, the system is the core object of MBSE research, and the system ontology focuses on the core concepts of the system involved in system engineering. The system ontology is also an important part of the MBSE ontology, providing a basis for the definition of the MBSE ontology and the definition of the system ontology for the equipment field. The definition of the system ontology uses BFO, CCO, and IAO as the upper-level ontology.

[0050] The system ontology contains the following concepts:

[0051] system

[0052] System: Elements

[0053] System:Element:Product System

[0054] System:Element:Service System

[0055] System:Element:Port

[0056] System: Elements: Structure

[0057] System: Environment

[0058] Systems: Life CycleSystems: Life Cycle: Life Cycle ModelSystems: Life Cycle: Life Cycle PhasesSystems: Behavior

[0059] System: Status

[0060] System:State:Events

[0061] System: State: State Space

[0062] System:State:StateTransition

[0063] System: Function

[0064] System:Function:Mode

[0065] System: Function: Mode conversion

[0066] System: Function: Interface

[0067] System: Stakeholders

[0068] System: Purpose

[0069] The definitions of concepts in the system ontology are shown in Table 1.

[0070] Table 1

[0071]

[0072]

[0073]

[0074] The definition of concept relationships in the system ontology is shown in Table 2.

[0075] Table 2

[0076]

[0077]

[0078] In one embodiment of the present invention, the model-based systems engineering (MBSE) ontology focuses on the description of core concepts related to the system engineering practice activities carried out with the system as the core. It includes the system ontology and the core concepts related to the system engineering activities carried out around the system, providing a unified conceptual basis for the definition and application of model-based system engineering process methods in different fields. The MBSE ontology is defined with BFO, CCO, and IAO as the upper ontology.

[0079] MBSE ontology contains the following concepts:

[0080] system

[0081] System: Elements

[0082] System:Element:Product System

[0083] System:Element:Service System

[0084] System:Element:Port

[0085] System: Elements: Structure

[0086] System: Environment

[0087] System: Lifecycle

[0088] Systems: Lifecycle: Lifecycle Model Systems: Lifecycle: Lifecycle Phases Systems: Behavior

[0089] System: StateSystem: State: EventSystem: State: State SpaceSystem: State: State TransitionSystem: FunctionSystem: Function: ModeSystem: Function: Mode TransitionSystem: Function: InterfaceSystem: Stakeholder

[0090] System: Purpose

[0091] Needs Needs: Business Mission Needs Needs: Stakeholder Needs

[0092] Requirements Requirements: Stakeholder Requirements Requirements: System Requirements

[0093] Background Environment Background Environment: External System Background Environment: System of Interest Background Environment: Operation Scenario

[0094] Lifecycle conceptsLifecycle concepts: Support conceptsLifecycle concepts: Operation conceptsLifecycle concepts: Retirement conceptsLifecycle concepts: Deployment conceptsLifecycle concepts: Acquisition concepts

[0095] Process Flow: Business Roles

[0096] Process: Finished product

[0097] Process: Activities

[0098] Architecture Architecture: Functional Architecture Architecture: Functional Architecture: Functional Interface Architecture: Functional Architecture: Object Flow Architecture: Functional Architecture: Control Flow Architecture: Logical Architecture Architecture: Logical Architecture: Logical Components Architecture: Logical Architecture: Logical Component Interface Architecture: Logical Architecture: Logical Component Behavior Architecture: Physical Architecture Architecture: Physical Architecture: Object Flow Architecture: Physical Architecture: Physical Components Architecture: Physical Architecture: Physical Component Interface Architecture: Physical Architecture: Physical Component Behavior Architecture: View Architecture: View Elements

[0099] Architecture: Perspective

[0100] Competence

[0101] Competency: Knowledge

[0102] Competencies: Skills

[0103] Competencies: Talent

[0104] Competency: Attitude

[0105] project

[0106] Project: Sub-project

[0107] Project: Organization

[0108] Project: Resources

[0109] Modeling Language Modeling Language: Modeling Tools As shown in Table 3, the definitions of other MBSE ontology concepts other than the system ontology concepts are listed.

[0110] Table 3

[0111]

[0112]

[0113]

[0114]

[0115]

[0116] Furthermore, the definition of concept relationships in MBSE ontology is shown in Table 4.

[0117] Table 4

[0118]

[0119]

[0120]

[0121]

[0122]

[0123] In one embodiment of the present invention, the system ontology for the equipment field is oriented to the relevant concepts and relationships of the equipment systems in the actual industry field (such as aerospace vehicles, aviation vehicles, surface vehicles, etc.), and establishes a unified ontology knowledge base for different equipment systems across industries. The definition of the system ontology for the equipment field is multi-inherited. On the one hand, it is based on the top-level ontology BFO and CCO, and describes the relevant concepts of the equipment system in the industry field from the perspective of actual existence. On the other hand, it also inherits the system ontology and integrates the relevant concepts of the equipment system from the system perspective in system engineering. The definition of the system ontology for the equipment field focuses on three aspects: function, composition structure, and role.

[0124] The system ontology for the equipment field includes the following concepts:

[0125] Equipment System

[0126] Equipment system function

[0127] Posture control function

[0128] Chemical reaction function

[0129] Communication function

[0130] Communication jamming function Communication receiving function Communication relay function Computing function Cooling function Destruction function Deception function Detonation function Electrical function Electromagnetic induction function Electromagnetic shielding function Fluid control function Friction reduction function Fuel function Heating function Imaging function Shock shielding function Motion suppression function Life support function Lifting function Measurement function Motion function Navigation function Detection function Optical processing function Direction control function Load capacity Power supply function Reflection function Refraction function Sensor function Signal detection function Signal processing function Structural support function Thermal control function Timing function Ventilation control function Maintenance function Carrier

[0131] Aircraft

[0132] Ground Vehicle

[0133] Rocket

[0134] Spacecraft

[0135] Water Vehicle

[0136] arms

[0137] Cutting weapons

[0138] Explosive weapons

[0139] Burning weapons

[0140] ammunition

[0141] Transmitter

[0142] engine

[0147] Electric engine

[0148] Thermal Engine

[0149] Physical Power Engine Reaction Engine Environmental Control System

[0150] Cabin pressure control system

[0151] Cooling system

[0152] Heating system

[0153] Equipment Fixtures

[0154] Control System

[0155] Generator control unit

[0156] Propulsion control system

[0157] Vehicle Control System

[0158] Communication System

[0159] Interoperable system

[0160] Public Broadcasting System

[0161] Telecommunications Network

[0162] Fuel System

[0163] Navigation system

[0164] Power Transmission System

[0165] Propulsion system

[0166] Vehicle frame

[0167] Load

[0168] Environmental characteristics

[0169] Human characteristics

[0170] Geographical features

[0171] Equipment System Role

[0172] Component Roles

[0173] Infrastructure roles

[0174] Some roles

[0175] System Roles

[0176] The definitions of concepts in the system ontology for the equipment field are shown in Table 5.

[0177] Table 5

[0178]

[0179]

[0180]

[0181]

[0182]

[0183]

[0184]

[0185]

[0186]

[0187]

[0188]

[0189] Furthermore, the definition of concept relationships in the system ontology for the equipment field is shown in Table 6.

[0190] Table 6

[0191]

[0192]

[0193]

[0194]

[0195]

[0196]

[0197]

[0198] According to the formalized ontology definition method for model-based system engineering and equipment systems in the embodiment of the present invention, a comprehensive and formal understanding of the core concepts of the system involved in model-based system engineering and the core concepts of the engineering practice activities carried out around it is established; the mutual recognition of knowledge / concepts between different equipment system application objects in different industry fields in realizing MBSE is promoted, and the system design and collaborative development of multiple equipment across industry fields is promoted; through a formal ontology model, the consistency of conceptual understanding and cognition between people, computers and the objective world is promoted, laying the foundation for the intelligence of MBSE.

[0199] Compared with the prior art, the present invention:

[0201] a) The core concepts and relationships of the objects, methods, and application objects studied by MBSE are formally described, and an interconnected system ontology, model-based system engineering ontology, and equipment system ontology are established to support the application of MBSE in different industry fields, as well as the system design and collaborative R&D of multiple equipment across industries.

[0202] b) The three ontologies are established under the guidance of the same formalized classification provided by the three top-level ontologies BFO, CCO, and IAO. The descriptions of the established ontologies are unified, supporting broader consensus building and knowledge sharing across industry fields.

[0203] The present invention also demonstrates the guidance of the defined system ontology based on the equipment field for the definition of the functions of typical equipment systems such as aircraft, satellites, radars, etc. Figure 4 , Figure 5 and Figure 6 As shown, the definitions of aircraft functions (reference SAE AIR6110 / SAE ARP4754A), satellite functions, and radar functions based on the system ontology for the equipment field are shown. Although aircraft, satellites, and radars are different equipment systems in different industry fields, the definitions of their functions are based on the same system ontology for the equipment field, thus promoting the unification and sharing of concepts across industry fields.

[0204] Figure 3 A formalized ontology definition system 10 for model-based system engineering and equipment system according to an embodiment of the present invention is characterized by comprising:

[0205] System ontology definition module 100, used to define and model the core concepts and relationships of the system involved in system engineering based on three top-level ontologies: basic formalized ontology BFO, core layer ontology CCO, and information product ontology IAO, to form a system ontology;

[0206] MBSE ontology definition module 200, used to expand the definition of core concepts and relationships related to model-based system engineering practice activities based on the formed system ontology and the three top-level ontologies of BFO, CCO and IAO, so as to form a model-based system engineering MBSE ontology; and

[0207] The system ontology definition module 300 for the equipment field is used to define and describe the core common concepts and relationships of the equipment system in a specific industry field according to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, so as to form a system ontology for the equipment field.

[0208] According to the formalized ontology definition system for model-based system engineering and equipment systems in the embodiment of the present invention, a comprehensive and formal understanding of the core concepts of the system involved in model-based system engineering and the core concepts of the engineering practice activities carried out around it is established; the mutual recognition of knowledge / concepts between different equipment system application objects in different industry fields in realizing MBSE is promoted, and the system design and collaborative development of multiple equipment across industry fields is promoted; through a formal ontology model, the consistency of conceptual understanding and cognition between people, computers and the objective world is promoted, laying the foundation for the intelligence of MBSE.

[0209] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0210] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

Claims

1. A formalized ontology definition method for model-based systems engineering and equipment systems. It is characterized in that include: Based on the three top-level ontologies of basic formalized ontology BFO, core layer ontology CCO and information product ontology IAO, the core concepts and relationships of the system involved in system engineering are defined and modeled to form a system ontology; According to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, the definition of core concepts and relationships related to model-based system engineering practice activities is expanded to form the MBSE ontology of model-based system engineering; and, According to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, the core common concepts and relationships of equipment systems in specific industry fields are defined and described to form a system ontology for the equipment field.

2. The method according to claim 1, It is characterized in that The system ontology includes the following concepts: system, element, product system, service system, port, structure, environment, life cycle, life cycle model, life cycle phase, behavior, state, event, state space, state transition, function, mode, mode transition, interface, stakeholder, purpose.

3. The method according to claim 2, It is characterized in that The model-based systems engineering ontology includes the following concepts: system, element, product system, service system, port, structure, environment, life cycle, life cycle model, life cycle phase, behavior, state, event, state space, state transition, function, mode, mode transition, interface, stakeholder, purpose, need, business mission need, stakeholder need, requirement, stakeholder need, system requirement, context, external system, system of interest, operation scenario, life cycle concept, support concept, operation concept, exit concept, deployment concept, acquisition concept, process, business role, artifact, activity, architecture, functional architecture, functional interface, object flow, control flow, logical architecture, logical component, logical component interface, logical component behavior, physical architecture, object flow, physical component, physical component interface, physical component behavior, view, view element, perspective, competency, knowledge, skill, talent, attitude, project, subproject, organization, resources, modeling language and modeling tool.

4. The method according to claim 3, It is characterized in that The system ontology for the equipment field includes the following concepts: Equipment system, equipment system function, attitude control function, chemical reaction function, communication function, communication interference function, communication reception function, communication relay function, computing function, cooling function, destruction function, deception function, detonation function, electrical function, electromagnetic induction function, electromagnetic shielding function, fluid control function, friction reduction function, fuel function, heating function, imaging function, impact shielding function, motion suppression function, life support function, lifting function, measurement function, motion function, navigation function, detection function, optical processing function, direction control function, load capacity, power supply function, reflection function, refraction function, sensor function, signal detection function, signal processing function, structural support function, thermal control function, timing function, ventilation control Function, maintenance function, vehicle, aircraft, ground vehicle, rocket, spacecraft, water vehicle, weapons, cutting weapons, explosive weapons, incendiary weapons, ammunition, launcher, engine, electric engine, thermal engine, physical power engine, reactive engine, environmental control system, cabin pressure control system, cooling system, heating system, equipment fixture, control system, generator control unit, propulsion control system, vehicle control system, communication system, intercommunication system, public broadcasting system, telecommunications network, fuel system, navigation system, power transmission system, propulsion system, vehicle frame, payload, environmental characteristics, human characteristics, geographical characteristics, equipment system role, component role, infrastructure role, part role, system role.

5. The method according to claim 4, It is characterized in that Construct the system ontology concept relationship definition table based on the concepts contained in the system ontology, as well as the corresponding relationship classifications and relationship types; Construct the MBSE ontology concept relationship definition table based on the concepts contained in the MBSE ontology, as well as the corresponding relationship classifications and relationship types; Based on the concepts contained in the system ontology for the equipment field, as well as the corresponding relationship classifications and relationship types, a concept relationship definition table in the system ontology for the equipment field is constructed.

6. The method according to claim 5, It is characterized in that The relationship classification in the system ontology concept relationship definition table includes basic relationships, spatiotemporal relationships and dependency relationships; The relationship classification in the MBSE ontology concept relationship definition table includes spatiotemporal relationship, correlation relationship, dependency relationship, basic relationship, carrying relationship and realization relationship; The relationship classification in the concept relationship definition table in the equipment field-oriented system ontology includes basic relationships.

7. A formalized ontology definition system for model-based systems engineering and equipment systems, include: The system ontology definition module is used to define and model the core concepts and relationships of the system involved in system engineering based on the three top-level ontologies: basic formalized ontology BFO, core layer ontology CCO, and information product ontology IAO, to form a system ontology; MBSE ontology definition module, used to expand the definition of core concepts and relationships related to model-based system engineering practice activities based on the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, so as to form a model-based system engineering MBSE ontology; and The system ontology definition module for the equipment field is used to define and describe the core common concepts and relationships of equipment systems in specific industry fields according to the formed system ontology and based on the three top-level ontologies of BFO, CCO and IAO, so as to form a system ontology for the equipment field.

Citation Information

Patent Citations

  • Internet of Things domain ontology construction method based on core concept ontology

    CN114328954A

  • Unified analysis and display method based on MBSE heterogeneous model

    CN116400892A

  • System logic architecture model generation method based on domain ontology

    CN118133953A

  • Systems, methods, and apparatus to generate an integrated modular architecture model

    US20190311087A1