A DDS data topic mapping configuration method based on an SQLite database

Abstract

The application provides a DDS data topic mapping configuration method based on an SQLite database, and belongs to the technical field of data communication and system integration. The method constructs multiple SQLite database table structures, including a protocol table, a protocol detail table, a protocol mapping table, a protocol mapping detail table, a topic table and a topic mapping table, systematically manages protocols, protocol fields, data topics and their mapping relationships, supports data intercommunication between multiple communication protocols through field-level mapping configuration and rule definition, and realizes a flexible, configurable and extensible data topic mapping mechanism. The method can realize communication protocol field mapping and data conversion between different data topics, improves the flexibility and maintainability of data communication between systems, and is suitable for industrial Internet of Things, edge computing, micro-service architecture and other scenes.

Description

Technical Field

[0001] This invention relates to the field of data communication and system integration technology, and in particular to a method for configuring DDS (Data Distribution Service) data topic mapping based on an SQLite database. Background Technology

[0002] In distributed systems, data communication between different systems often relies on a unified data format and communication protocol. However, due to differences in protocols, data field definitions, and communication methods used by different systems, data interoperability between systems is quite challenging. Traditional data mapping configuration methods often employ hard-coding, which is complex to configure, difficult to maintain, and ill-suited to the needs of frequent changes in system protocols. Summary of the Invention

[0003] To address the aforementioned issues, this invention proposes a DDS data topic mapping configuration method based on an SQLite database. This method models and configures protocols, protocol fields, data topics, and their mapping relationships in a structured manner, enabling flexible mapping and conversion of data between systems.

[0004] The technical solution adopted in this invention is as follows:

[0005] A method for configuring DDS data topic mapping based on an SQLite database includes the following steps:

[0006] Step 1: Create a protocol table to store basic protocol information, including protocol ID, protocol name, and protocol type;

[0007] Step 2: Create a protocol details table to store detailed information about each field in the protocol, including field ID, field name, field type, field description, whether it is required, field mask, and default value;

[0008] Step 3: Create a protocol mapping table to record the mapping relationship between every two protocols in the table, including the source protocol ID, the target protocol ID, and the protocol mapping identifier;

[0009] Step 4: Create a protocol mapping details table to record the mapping relationship between fields in the source protocol details table and the target protocol details table, including source field name, target field name, mapping rules and default values;

[0010] Step 5: Create a topic table to store the basic attributes of the data topic, including topic ID, topic name, read / write support, maximum depth of message cache queue, and HTTP interface and port configuration;

[0011] Step 6: Create a topic mapping table to record the mapping relationship between every two data topics in the topic table, and associate it with the protocol mapping identifier in the protocol mapping table, including the source topic ID, target topic ID, and mapping rule dependency conditions;

[0012] Step 7: After receiving data from the source topic defined in the topic table, obtain the protocol mapping identifier according to the topic mapping table;

[0013] Step 8: Using the protocol mapping identifier obtained in Step 7, retrieve the source protocol ID and target protocol ID from the protocol mapping table, and retrieve the field conversion mapping relationship between the source protocol and the target protocol from the protocol mapping details table;

[0014] Step 9: Based on the field conversion mapping relationship between the source protocol and the target protocol obtained in Step 8, complete the conversion from the source protocol to the target protocol defined in the protocol table and the protocol details table, thereby completing the conversion from the source topic to the target topic.

[0015] Furthermore, the fields in the protocol table include protocol ID, protocol name, and protocol type, wherein the protocol ID is the primary key;

[0016] The fields in the protocol details table include Protocol ID, ID of fields contained in the protocol, name of fields contained in the protocol, type of fields contained in the protocol, and description of fields contained in the protocol; among them, the ID of fields contained in the protocol is the primary key, and Protocol ID is a foreign key associated with the protocol table;

[0017] The protocol mapping table includes fields such as protocol mapping ID, protocol mapping name, source protocol ID, and target protocol ID; wherein, the protocol mapping ID is the primary key, and the source protocol ID and target protocol ID are both foreign keys associated with the protocol table;

[0018] The fields of the protocol mapping details table include protocol mapping ID, source field ID, target field ID, and field mapping rule; wherein, protocol mapping ID is a foreign key associated with the protocol mapping table, and source field ID and target field ID are both foreign keys associated with the protocol details table;

[0019] The fields of the topic table include topic ID, topic name, read / write support, maximum message cache queue depth, and HTTP interface and port configuration; among them, topic ID is the primary key;

[0020] The fields of the topic mapping table include topic mapping ID, source topic ID, target topic ID, mapping rule dependency conditions, and protocol mapping ID; wherein, topic mapping ID is the primary key, protocol mapping ID is a foreign key associated with the protocol mapping table, and source topic ID and target topic ID are foreign keys associated with the topic table.

[0021] Compared with the prior art, the present invention has the following advantages and positive effects:

[0022] 1. Structured configuration: The protocol, protocol fields, data topics and their mapping relationships are modeled in a structured way, which facilitates system management and maintenance.

[0023] 2. Flexible mapping mechanism: Supports field-level mapping between protocols and between topics, including field value conversion, default value handling, and condition judgment.

[0024] 3. High scalability: By expanding the table structure or adding new fields, it can support more protocol types, data themes and mapping rules to adapt to different business needs.

[0025] 4. Supports multiple communication methods: Supports multiple communication methods such as DDS and HTTP to meet the data interoperability requirements of multiple protocols and topics in distributed systems.

[0026] 5. System decoupling: Decoupling communication logic from business logic is achieved through database configuration, improving the system's flexibility and maintainability. Attached Figure Description

[0027] Figure 1 This is a database structure diagram in an embodiment of the present invention. Detailed Implementation

[0028] To make the objectives, technical features, and beneficial effects of this invention clearer, specific implementations of the invention are described below with reference to the accompanying drawings. Unless otherwise defined, the following technical terms have the same meaning as commonly understood by those skilled in the art to which this invention pertains. The specific embodiments used in this specification are for illustrative purposes only and are not intended to limit the scope of protection of this invention.

[0029] A DDS data topic mapping configuration method based on SQLite database is used to realize communication protocol field mapping and data conversion between different data topics, including the following steps:

[0030] Step 1: Create a protocol table to store basic protocol information, including protocol ID, protocol name, and protocol type. This table manages basic information for all supported communication protocols, providing the foundation for subsequent protocol field definitions and mapping relationships. Specific definitions and explanations are as follows:

[0031] Table 1. Contents of the Agreement

[0032]

[0033] Step 2: Create a protocol details table to store detailed information about each field in each protocol, including field ID, field name, field type, field description, required field status, field mask, and default value. This table provides a detailed description of the data fields contained in each protocol and supports subsequent protocol mapping and data conversion operations. The specific definitions and explanations are as follows:

[0034] Table 2. Contents of the Agreement Details Table

[0035]

[0036] Step 3: Create a protocol mapping table to record the mapping relationship between the two protocols created in Step 1, including the source protocol ID, target protocol ID, and mapping relationship identifier. This table records the mapping relationship between different protocols and is the foundation for implementing data conversion between protocols. The specific definitions and explanations are as follows:

[0037] Table 3. Contents of the Protocol Mapping Table

[0038]

[0039] Step 4: Create a protocol mapping details table to record the mapping relationship between fields in the source protocol details and target protocol details created in Step 2, including source field names, target field names, mapping rules, and default values. This table describes the mapping logic between protocol fields in detail, supports the conversion and processing of field values, and is the core part of data conversion. Specific definitions and explanations are as follows:

[0040] Table 4 contains the details of the protocol mapping table.

[0041]

[0042] Step 5: Create a topic table to store the basic attributes of data topics, including topic ID, topic name, read / write support, maximum message cache queue depth, and HTTP interface and port configuration. This table defines the detailed attributes of each data topic, including read / write support, caching strategy, and HTTP configuration. It is the core table for data topic management, and its specific definition and explanation are as follows:

[0043] Table 5 Contents of the Subject Table

[0044]

[0045] Step 6: Create a topic mapping table to record the mapping relationship between the two data topics created in Step 5, and associate it with the protocol mapping identifier in the protocol mapping table created in Step 3, including the source topic ID, target topic ID, and mapping rule dependencies. This table is used to establish the mapping logic between data topics and is associated with the specific mapping rules in the protocol mapping table. It is key to achieving data interoperability between topics. Specific definitions and explanations are as follows:

[0046] Table 6 Contents of the Topic Map Table

[0047]

[0048] Figure 1 The SQLite database table structure of this method is shown, illustrating the relationships between the protocol table, protocol details table, protocol mapping table, protocol mapping details table, topic table, and topic mapping table.

[0049] Step 7: After receiving data, the source topic defined in the topic table created in step 5 obtains the protocol mapping identifier according to the topic mapping table created in step 6;

[0050] Step 8: Using the protocol mapping identifier obtained in Step 7, obtain the source protocol ID and target protocol ID from the protocol mapping table created in Step 3, and obtain the field conversion mapping relationship between the source protocol and the target protocol from the protocol mapping details table created in Step 4;

[0051] Step 9: Based on the field conversion mapping relationship between the source protocol and the destination protocol obtained in Step 8, complete the conversion from the source protocol to the destination protocol defined in the protocol table and protocol details table created in Steps 1 and 2, thereby completing the conversion from the source topic to the destination topic.

[0052] In one embodiment, the present invention is applied to an information processing system for cross-platform information synchronization. Between two platforms, the source platform sends an instruction. Using the information processing system of the present invention, based on configurable data topic mapping information, the instruction content is mapped and combined with other required topics to generate a topic conforming to the message standard, which is then sent to the destination platform. Upon receiving the instruction, the destination platform, using the information processing system of the present invention, converts the topic mapping conforming to the message standard into a source instruction based on the configurable data topic mapping information, thereby achieving cross-platform information synchronization.

[0053] As can be seen from this embodiment, the present invention can realize configurable data topic mapping and transformation between different platforms.

[0054] In summary, this invention constructs multiple SQLite database table structures, including a protocol table, a protocol details table, a protocol mapping table, a protocol mapping details table, a topic table, and a topic mapping table, to systematically manage protocols, protocol fields, data topics, and their mapping relationships. Through field-level mapping configuration and rule definition, it supports data interoperability between various communication protocols (such as DDS, HTTP, etc.), achieving a flexible, configurable, and scalable data topic mapping mechanism.

[0055] This invention enables the systematic management of protocols, protocol fields, data topics, and their mapping relationships by constructing structured database tables. It can solve the problem of flexible configuration of communication protocol field mapping and data conversion between variable data topics, thereby improving the flexibility, configurability, and maintainability of data communication between systems. It is applicable to scenarios such as industrial IoT, edge computing, and microservice architecture.

Claims

1. A method for configuring DDS data topic mapping based on an SQLite database, characterized in that, Includes the following steps: Step 1: Create a protocol table to store basic protocol information, including protocol ID, protocol name, and protocol type; Step 2: Create a protocol details table to store detailed information about each field in the protocol, including field ID, field name, field type, field description, whether it is required, field mask, and default value; Step 3: Create a protocol mapping table to record the mapping relationship between every two protocols in the table, including the source protocol ID, the target protocol ID, and the protocol mapping identifier; Step 4: Create a protocol mapping details table to record the mapping relationship between fields in the source protocol details table and the target protocol details table, including source field name, target field name, mapping rules and default values; Step 5: Create a topic table to store the basic attributes of the data topic, including topic ID, topic name, read / write support, maximum depth of message cache queue, and HTTP interface and port configuration; Step 6: Create a topic mapping table to record the mapping relationship between every two data topics in the topic table, and associate it with the protocol mapping identifier in the protocol mapping table, including the source topic ID, target topic ID, and mapping rule dependency conditions; Step 7: After receiving data from the source topic defined in the topic table, obtain the protocol mapping identifier according to the topic mapping table; Step 8: Using the protocol mapping identifier obtained in Step 7, retrieve the source protocol ID and target protocol ID from the protocol mapping table, and retrieve the field conversion mapping relationship between the source protocol and the target protocol from the protocol mapping details table; Step 9: Based on the field conversion mapping relationship between the source protocol and the target protocol obtained in Step 8, complete the conversion from the source protocol to the target protocol defined in the protocol table and the protocol details table, thereby completing the conversion from the source topic to the target topic.

2. The DDS data topic mapping configuration method based on SQLite database according to claim 1, characterized in that, The fields in the protocol table include protocol ID, protocol name, and protocol type, where protocol ID is the primary key; The fields in the protocol details table include Protocol ID, ID of fields contained in the protocol, name of fields contained in the protocol, type of fields contained in the protocol, and description of fields contained in the protocol; among them, the ID of fields contained in the protocol is the primary key, and Protocol ID is a foreign key associated with the protocol table; The protocol mapping table includes fields such as protocol mapping ID, protocol mapping name, source protocol ID, and target protocol ID; wherein, the protocol mapping ID is the primary key, and the source protocol ID and target protocol ID are both foreign keys associated with the protocol table; The fields of the protocol mapping details table include protocol mapping ID, source field ID, target field ID, and field mapping rule; wherein, protocol mapping ID is a foreign key associated with the protocol mapping table, and source field ID and target field ID are both foreign keys associated with the protocol details table; The fields of the topic table include topic ID, topic name, read / write support, maximum message cache queue depth, and HTTP interface and port configuration; among them, topic ID is the primary key; The fields of the topic mapping table include topic mapping ID, source topic ID, target topic ID, mapping rule dependency conditions, and protocol mapping ID; wherein, topic mapping ID is the primary key, protocol mapping ID is a foreign key associated with the protocol mapping table, and source topic ID and target topic ID are foreign keys associated with the topic table.

Images