Twin data integrated management method for digital twins of ship operations
By constructing a global ontology knowledge base and a local ontology knowledge base, the problem of integrated management of digital twin data of ship operation was solved, realizing unified storage and management of data and improving the convenience of querying and using data.
Patent Information
- Application Number
- CN202210659248.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-13
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-06-13
AI Technical Summary
Existing technologies make it difficult to achieve integrated management of digital twin data of ship operations, resulting in inconvenience in querying and using the data.
We construct an integrated management method for digital twin data of ship operations. This method involves building a global ontology knowledge base and a local ontology knowledge base through ontology modeling, defining concept mappings and relationships, and persistently storing the data in a relational database using triples. This solves the semantic heterogeneity problem and enables unified data description and management.
It enables unified storage and management of ship operation twin data, improves the convenience of data query and use, and provides an integrated data foundation for ship digital twin-related applications.
Smart Images

Figure CN114936257B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of ship operation management, and more specifically, to a twin data integrated management method for a digital twin of ship operation. Background Art
[0002] In recent years, digital twin technology has a very wide range of application needs and market prospects in the field of ships. By establishing a digital twin for ship operation, a dynamic virtual model of the ship's physical entity with multiple dimensions, multiple time and space scales, multiple disciplines, and multiple physical quantities can be established in a digital way to simulate and characterize the attributes, behaviors, rules, etc. of the real ship in the real operating environment. It is of great significance in real-time tracking of ship operation status, operation status prediction, and fault analysis. During the operation of the ship, the physical entity, virtual model, and service system of the ship portrayed by the digital twin technology will generate twin data with characteristics such as multi-source, heterogeneous, and large data volume. These twin data are the core of promoting the operation of various parts of the digital twin ship and related applications of the ship's digital twin. The twin data of the operating ship's digital twin is multi-source, heterogeneous, and large in data volume, and it is difficult to achieve integrated management with existing technologies. Summary of the invention
[0003] The technical problem to be solved by the present invention is to provide an integrated twin data management method for ship operation digital twins, which can make the query, use and control of ship operation twin data more intuitive and convenient, and provide an integrated data foundation for ship digital twin related applications.
[0004] The technical solution adopted by the present invention to solve the technical problem is: constructing a twin data integrated management method for a digital twin of ship operation, comprising the following steps:
[0005] S1. Collect and analyze the twin data data sources of the digital twin of the ship operation, and on this basis, perform ontology modeling on the twin data to build an ontology knowledge base, that is, a global ontology knowledge base and a local ontology knowledge base for the twin data of the digital twin of the ship operation; the ontology knowledge base includes the following four parts:
[0006] (1) Classes representing concepts and relationships of twin data sources for ship operation;
[0007] (2) The attributes of the classes that support the construction of the global ontology and local ontology of ship operation twin data;
[0008] (3) Attribute constraints between classes contained in the global ontology and the local ontology;
[0009] (4) Describe the data instances of the classes contained in the global ontology and local ontology of the ship operation twin data;
[0010] S2. Define the mapping and relationship between the concepts of the global ontology and local ontology of the digital twin data of ship operation, solve the semantic heterogeneity problem between data by defining object attributes between classes, and realize the construction of a unified data description model;
[0011] S3. According to the established unified description model of ship operation twin data, the ship operation twin data ontology model is persistently stored in the relational database in the form of triples to realize the unified storage and management of ship twin data.
[0012] According to the above scheme, in step S1, the specific process of analyzing all twin data sources of the ship operation digital twin is as follows:
[0013] (1) Determine the specific construction areas of the ship operation twin data ontology;
[0014] (2) Select concepts in the ontology construction domain that should be written into the ontology knowledge base;
[0015] (3) Analyze the concepts and relationships within the ontology construction domain, confirm the source, type and regular relationship of the data stored in the source with other data, and extract the data features as follows:
[0016] C i ={S i ,T i ,R i}
[0017] Where i is the number of the twin data, C i is the set of twin data i attributes, S i ,T i ,R i is the attribute of the data numbered i, S i Indicates the source of the twin data, T i Indicates the type of the twin data, R i is the regular relationship between the twin data and other data.
[0018] According to the above scheme, in step S1, the steps of constructing the local ontology and the global ontology representing the concepts and relationships of the ship operation twin data are as follows:
[0019] (1) Define classes and hierarchical structures: Establish the basic relationship between concepts based on the data attribute set, and adopt a top-down development method to establish the global ontology of ship operation twin data and the class hierarchy of five local ontologies: ship basic information, sensor data, subsystem data, geometric model data, and ship operation status data. Establish the corresponding ontology categories and the refined subcategories in the protégé;
[0020] (2) Define class attributes: define the object attributes and data attributes of the classes under the global ontology of ship operation twin data and the five local ontologies; the object attributes are used to describe the association between classes, and the data attributes are used to further describe the class itself in the form of data;
[0021] (3) Define attribute constraints: After the object attributes and data attributes of the ontology class are defined, attribute constraints are defined for the attributes of the classes under the global ontology of ship operation twin data and the five local ontologies to add constraints and restrictions to the attributes;
[0022] (4) Create instances: After the object attributes and data attributes of the concept are determined, the Cellfie language in Protégé is used to import the collected twin data of the ship operation digital twin as instances in batches into the corresponding class.
[0023] According to the above scheme, in step S2, the method for solving the semantic heterogeneity problem is as follows:
[0024] (1) The heterogeneity of included element types in the extension heterogeneity is solved through rdfs:subClassof and rdfs:subpropertyof in the ontology definition syntax;
[0025] (2) Heterogeneity in naming heterogeneity, where the same entity uses different names, and heterogeneity in extension heterogeneity, where equivalent element types are used, are resolved through the owl:equivalentClass and owl:equivalentProperty syntaxes;
[0026] (3) Property heterogeneity can be solved by using the rdfs:subPropertyof syntax in the ontology;
[0027] (4) Format heterogeneity is solved by class axioms or functions and by looking up conversion tables. According to the different precisions of temperature data, the problem of format heterogeneity is solved by defining a mapping table between temperature values and grade values.
[0028] (5) Confusion is resolved by specifying a standard for confusing terms.
[0029] According to the above scheme, in step S3, the unified storage and management implementation method of ship twin data is as follows:
[0030] (1) In the Protégé tool, the established global ontology model of ship operation twin data and the five local ontologies are exported as .owl files, i.e. ontology information files;
[0031] (2) Use the relational database MySQL to persistently store the established ship operation process ontology data in the form of triples, and use the Navicat for MySQL database visualization tool to create a database to store the established ontology;
[0032] (3) The connection between the ontology model and the database is established through the Jena2 toolkit. In Eclipse, the ontology persistence model is created through the Jena2 database engine interface to achieve the connection between the ontology information file in (1) and the database established in (2). Then, the ontology model is persistently stored in MySQL to achieve unified storage and management of twin data. This includes the following five steps:
[0033] ① Load the database JDBC driver;
[0034] ② Create a connection between the database for storing the ship operation twin data entity established in (2) and the programming IDE;
[0035] ③ Create a ModelMaker object for the database, which is responsible for creating the specific operations of the ontology model and also associates the model with the database;
[0036] ④ Create a semantic model based on a relational database for the ship operation twin data ontology;
[0037] ⑤ Read the ontology data and convert it into triples and store them in the MySQL database.
[0038] The implementation of the twin data integrated management method for the digital twin of ship operation of the present invention has the following beneficial effects:
[0039] 1. The present invention provides an analysis method for the twin data source of ship operation, which provides a basis for the establishment of a unified description ontology model of twin data during the operation of digital twin ships.
[0040] 2. In view of the characteristics of multi-source, heterogeneous and large data volume of ship operation twin data, the present invention establishes a global ontology knowledge base and a local ontology knowledge base for the twin data of ship operation digital twins, solves the semantic heterogeneity problem between twin data related concepts, and realizes the construction of a unified data description model.
[0041] 3. The present invention persistently stores the ontology model in a relational database to realize the unified storage and management of ship twin data, making the query and use of ship operation twin data more intuitive and convenient, and providing an integrated data foundation for ship digital twin related applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:
[0043] Figure 1 It is a flow chart of the integrated management method of twin data of digital twin of ship operation according to an embodiment of the present invention;
[0044] Figure 2 A schematic diagram of the connection between some concepts in the local ontology of basic information of a ship according to an embodiment of the present invention;
[0045] Figure 3 A schematic diagram of the connection between some concepts in the local ontology of geometric model data according to an embodiment of the present invention;
[0046] Figure 4 A schematic diagram of the connection between some concepts in the local ontology of ship operation status data according to an embodiment of the present invention;
[0047] Figure 5 A schematic diagram of the connection between some concepts in the local ontology of subsystem data in an embodiment of the present invention;
[0048] Figure 6 Schematic diagram of the process flow for unified storage and management of digital twin data for ship operation. DETAILED DESCRIPTION
[0049] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described in detail with reference to the accompanying drawings.
[0050] The typical application scenarios of the present invention are as follows: for the multi-source heterogeneous twin data generated by the digital twin of ship operation, the ontology technology is used to build a unified description model of twin data, on this basis, the integrated management of the twin data of the digital twin of ship operation is realized, which is convenient for the real-time query of twin data and related applications of ship digital twin. Figure 1 As shown, the method mainly includes the following steps:
[0051] 1) Collect and analyze the twin data data sources of the ship operation digital twin, use ontology technology to model the twin data, and build an ontology knowledge base, that is, a global ontology knowledge base and a local ontology knowledge base for the twin data of the ship operation digital twin. The ontology knowledge base includes the following four parts:
[0052] ① A class representing the concepts and relationships of twin data sources of the ship operation digital twin
[0053] ② The attributes of the classes that support the construction of the global ontology and local ontology of the digital twin data of the ship operation
[0054] ③ Attribute constraints between classes contained in the global ontology and the local ontology
[0055] ④Describe the data instances of the classes contained in the global ontology and local ontology of the twin data of the ship operation digital twin;
[0056] 2) Define the mapping and relationship between the concepts of the global ontology and local ontology of the twin data of the ship operation digital twin, solve the semantic heterogeneity problem between the twin data by defining the object attributes between classes, and realize the construction of a unified description model for the twin data;
[0057] 3) According to the established unified description model of twin data of the digital twin of ship operation, the ship operation twin data ontology model is persistently stored in the relational database in the form of triples to achieve unified storage and management of ship twin data. In the process of establishing the ontology knowledge base model in step 1), firstly, a complete analysis of all twin data sources of ship operation under the control of digital twin is carried out. The specific steps include:
[0058] (1) Determine the domain of the ontology: The domain of the ontology is mainly all types of ship operation twin data, including the relevant data of the ship's physical entity, virtual model, and service system;
[0059] (2) Select the concepts that should be written into the ontology knowledge base: The basic concepts determined include engine, lifeboat, liquid cargo tank, sensor, digital twin geometric model, GIS, etc.;
[0060] (3) Confirm the source, type and regular relationship of the data stored in the source with other data, and extract and summarize the data features as follows:
[0061] C i ={S i ,T i ,R i}
[0062] Where i is the number of the twin data, C i is the set of twin data i attributes, S i ,T i ,R i is the attribute of the data numbered i, S i Indicates the source of the twin data, T i Indicates the type of the twin data, R i is the regular relationship between the twin data and other data.
[0063] Taking the engine power in the ship operation engine data source as an example, its data characteristics are as follows:
[0064] C = {engine, int, [belongs to the ship status data
[0065] Determined by the engine speed,
[0066] Affects the speed of ships]}
[0067] According to different data sources, the twin data data source categories of the ship operation digital twin are mainly divided into five categories: basic ship information, sensor data, subsystem data, geometric model data, and ship operation status data. Five local ontologies are constructed respectively to facilitate adding, reducing data sources and modifying data source structures. Taking the ship basic information ontology as an example, the connection diagram between some of its concepts is as follows Figure 2 As shown, the steps for constructing the local ontology knowledge base in step 1) are as follows:
[0068] (1) Define classes and hierarchical structures: Based on the twin data source feature S in the data feature i , Type T i and rule relation R i Classify the concepts, use Protégé ontology modeling software to establish the secondary concept "basic ship information" under the system root concept "Thing", establish the basic relationship between concepts according to the data attribute set, adopt a top-down development method to establish the class hierarchy structure of the local ontology of basic ship information, and establish the corresponding major categories and subcategories in protégé; divide the basic ship information ontology model into three major categories: "power system", "life-saving system" and "transportation system", and further subdivide the major categories into subcategories, such as "power system category" is further subdivided into "engine", "bow thruster", "main turbine", etc.; "transportation system category" is further subdivided into "liquid cargo tank", "maintenance system", "hull", etc.;
[0069] (2) Define the attributes of the class: The attributes of a class mainly include object attributes and data attributes. Object attributes describe the relationship between classes, while data attributes further describe the class itself in the form of data. i The relationship between the basic ship information systems is sorted out, and the object attributes between classes are defined. The attributes that support the construction of the ontology include conceptual, spatial, functional, temporal and physical related attributes; for example, the engine is conceptually connected to the power system through the attribute of "includes", and is spatially connected to the hull through the relationship of "loaded on". Data attributes are more detailed descriptions of each subclass, for example, the description of the engine includes "rated power", "model", "size", etc.
[0070] (3) Define attribute constraints: After the object attributes and data attributes are defined, you need to add constraints and restrictions to the attributes. For example, the "loaded on" relationship attribute in the object attributes needs to add the engine class as its definition domain and the hull class as its value range; for the data attributes, the "model" attribute in the "engine" class needs to add the engine class as its definition domain and "String" as its data type restriction;
[0071] (4) Create an instance: After the object attributes and data attributes of the concept are determined, it is necessary to add an instance to the class. Due to the large amount of data in twin data, the present invention uses the Cellfie language in Protégé to batch import the data as instances into the corresponding class. At this point, a complete local ontology of basic ship information is successfully constructed.
[0072] The schematic diagrams of the connections between the concepts of the geometric model data ontology, ship operation status data ontology, and subsystem data ontology are shown in the following figure. Figure 3 , Figure 4 , Figure 5 Shown
[0073] The specific creation process of the global ontology of ship operation twin data is consistent with the creation process of the local ontology. i , Type T i and the rule relation R i The concepts are classified, and the ship operation twin data ontology is created. The basic relationships are established according to the data attribute sets. The class hierarchy structure of the global ontology of ship operation twin data is established using a top-down development method. From the perspective of data composition, it is divided into two subcategories: ship static data and ship dynamic data. The dynamic data includes sensor data, GIS data, engine temperature and power, obstacle location, and cargo hold temperature data, etc. The static data mainly includes attributes such as weight and size of entities such as engines, twin model information, etc.
[0074] According to 2), the semantic heterogeneity problem is solved by defining object attributes between classes. The process of solving the semantic heterogeneity problem is as follows:
[0075] (1) The heterogeneity of the included element types in the extension heterogeneity is solved through rdfs:subClassof and rdfs:subpropertyof in the ontology definition syntax. For example, the power system is a subclass of both the ship basic information class and the subsystem data class, which belongs to this type of heterogeneity.
[0076] (2) Naming heterogeneity, i.e., the same entity uses different names, which is solved in this method by using the owl:equivalentClass and owl:equivalentProperty syntax;
[0077] (3) Attribute heterogeneity means that different data sources adopt different definition methods for the attributes of the same entity. For example, the size attribute of a model class is defined as three attributes: length, width, and height in another class. This can be solved by using the rdfs:subPropertyof syntax in the ontology.
[0078] (4) Format heterogeneity is solved by class axioms or functions, and by looking up conversion tables. For example, according to the different precisions of temperature data, the problem of format heterogeneity can be solved by defining a mapping table between temperature values and level values (high, medium, and low);
[0079] (5) Confusion heterogeneity can be resolved by specifying a standard for the terms that cause confusion, such as "recent" can be specified as "five minutes" in the field of data source integration.
[0080] After the ontology is built, the consistency and class hierarchy of the ontology are verified by the reasoning engine Racer. One of its main functions is to detect whether a class is a subclass of another class, thereby establishing the class hierarchy of the ontology. Based on the conditional description, the reasoning engine can also check whether a class has an instance, and can also check the execution conditions of each class to determine whether a certain data meets the conditions for becoming a member of a certain type.
[0081] In step 3), the unified storage and management of ship twin data is implemented as follows:
[0082] (1) In the Protégé tool, the established global ontology model of ship operation twin data and the five local ontologies are exported as .owl files, i.e. ontology information files;
[0083] (2) Use the relational database MySQL to persistently store the established ship operation process ontology data in the form of triples, and use the Navicat for MySQL database visualization tool to create a database to store the established ontology. In MySQL, the unified storage and management of the ontology model data is realized, and the database is created using the Navicat for MySQL database visualization tool;
[0084] (3) The connection between the ontology model and the database is established through the Jena2 toolkit. In Eclipse, the ontology persistence model is created through the Jena2 database engine interface to achieve the connection between the ontology information file in (1) and the database established in (2). Then, the ontology model is persistently stored in MySQL to achieve unified storage and management of twin data. It mainly includes the following five steps:
[0085] ① Load the database JDBC driver
[0086] ② Create a connection between the database for storing the ship operation twin data entity established in (2) and the programming IDE
[0087] ③ Create a ModelMaker object for the database, which is responsible for creating the specific operations of the ontology model and also associates the model with the database
[0088] ④ Use ModelMaker to create a temporary, default semantic model based on a relational database for the ship operation twin data ontology.
[0089] ⑤Convert the temporary model into an ontology model (OWL format), read the ontology data and convert it into triples and store them in the MySQL database
[0090] (4) This method converts the global ontology and local ontology files of the ship operation twin data into triples and stores them in the MySQL database in the form of URI. The stored ontology data can be obtained from the MySQL database, which is convenient for the use and management of the ship operation twin data. Jena uses seven tables to implement the storage of the ontology, which are divided into two categories: Statement Tables and System Tables. The database table names and corresponding storage functions for data storage are shown in Table 1.
[0091] Table 1 Database table names and functions
[0092]
[0093] Taking Jena_GiTj_Stmt as an example, the contents of the generated data table are shown in Table 2 below:
[0094] Table 2 Specific contents and meanings of database tables
[0095]
[0096]
[0097] Jena2 uses a non-normalized ternary storage method to store RDF statements, which is a hybrid of standard ternary storage and normalized ternary storage. This solution uses statement tables, text tables, and resource tables for storage. Short URIs are directly stored in the statement table, while long URIs are stored in the resource table. In this method, non-normalized storage is used to save storage space and improve retrieval efficiency, considering the multi-source, heterogeneous, and large-volume characteristics of twin data of ship operation digital twins.
[0098] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.
Claims
1. A twin data integrated management method for digital twins of ship operation, characterized in that: The following steps are involved: S1. Collect and analyze the twin data data sources of the digital twin of the ship operation, and on this basis, perform ontology modeling on the twin data to build an ontology knowledge base, that is, a global ontology knowledge base and a local ontology knowledge base for the twin data of the digital twin of the ship operation; the ontology knowledge base includes the following four parts: (1) Classes representing concepts and relationships of twin data sources for ship operation; (2) The attributes of the classes that support the construction of the global ontology and local ontology of ship operation twin data; (3) Attribute constraints between classes contained in the global ontology and the local ontology; (4) Describe the data instances of the classes contained in the global ontology and local ontology of the ship operation twin data; S2. Define the mapping and relationship between the concepts of the global ontology and local ontology of the digital twin data of ship operation, solve the semantic heterogeneity problem between data by defining object attributes between classes, and realize the construction of a unified data description model; S3. According to the established unified description model of ship operation twin data, the ship operation twin data ontology model is persistently stored in the relational database in the form of triples to realize the unified storage and management of ship twin data; In step S1, the specific process of analyzing all twin data sources of the ship operation digital twin is as follows: (1) Determine the specific construction areas of the ship operation twin data ontology; (2) Select concepts in the ontology construction field that should be written into the ontology knowledge base; (3) Analyze the concepts and relationships within the ontology construction domain, confirm the source, type and regular relationship of the data stored in the source and other data, and extract the data features as follows: in is the number of the twin data, is the set of twin data i attributes, , , Is numbered The properties of the data, Indicates the source of the twin data, Indicates the type of the twin data. is the regular relationship between the twin data and other data; In step S2, the method for solving the semantic heterogeneity problem is as follows: (1) The heterogeneity of included element types in the extension heterogeneity is solved through rdfs:subClassof and rdfs:subpropertyof in the ontology definition syntax; (2) Heterogeneity in naming heterogeneity where the same entity uses different names and heterogeneity in extension heterogeneity where equivalent element types are used are resolved through the owl:equivalentClass and owl:equivalentProperty syntaxes; (3) Property heterogeneity is solved by using the rdfs:subPropertyof syntax in the ontology; (4) Format heterogeneity is solved by class axioms or functions, and by looking up conversion tables. According to the different precisions of temperature data, the problem of format heterogeneity is solved by defining a mapping table between temperature values and grade values; (5) Confusion is resolved by specifying a standard for the terms that cause confusion.
2. The twin data integrated management method for ship operation digital twin according to claim 1 is characterized in that: In step S1, the steps of constructing the local ontology and the global ontology representing the concepts and relationships of the ship operation twin data are as follows: (1) Define classes and hierarchical structures: Establish the basic relationship between concepts based on the data attribute set, and use a top-down development method to establish the global ontology of ship operation twin data and the class hierarchy of five local ontologies: ship basic information, sensor data, subsystem data, geometric model data, and ship operation status data. Establish the corresponding ontology categories and the refined subcategories in the protégé; (2) Define class attributes: define the object attributes and data attributes of the classes under the global ontology of ship operation twin data and the five local ontologies; the object attributes are used to describe the association between classes, and the data attributes are used to further describe the class itself in the form of data; (3) Define attribute constraints: After the object attributes and data attributes of the ontology class are defined, attribute constraints are defined for the global ontology of the ship operation twin data and the attributes of the classes under the five local ontologies to add constraints and restrictions to the attributes; (4) Create an instance: After the object attributes and data attributes of the concept are determined, use the Cellfie language in Protégé to batch import the collected twin data of the ship operation digital twin as instances into the corresponding class.
3. The twin data integrated management method for ship operation digital twin according to claim 1 is characterized in that: In step S3, the unified storage and management implementation method of ship twin data is as follows: (1) In the Protégé tool, export the established global ontology model of ship operation twin data and the five local ontologies as .owl files, i.e. ontology information files; (2) Use the relational database MySQL to persistently store the established ship operation process ontology data in the form of triples, and use the Navicat for MySQL database visualization tool to create a database to store the established ontology; (3) The connection between the ontology model and the database is established through the Jena2 toolkit. In Eclipse, the ontology persistence model is created through the Jena2 database engine interface to achieve the connection between the ontology information file in (1) and the database established in (2). Then, the ontology model is persistently stored in MySQL to achieve unified storage and management of twin data. This includes the following five steps: ① Load the database JDBC driver; ② Create a connection between the database for storing the ship operation twin data entity established in (2) and the programming IDE; ③ Create a ModelMaker object for the database, which is responsible for creating the specific operations of the ontology model and also associates the model with the database; ④ Create a semantic model based on a relational database for the ship operation twin data ontology; ⑤ Read the ontology data and convert it into triples and store them in the MySQL database.
