DDS configuration tool based on modular hierarchical configuration strategy and configuration method thereof

Abstract

The invention discloses a DDS (Direct Digital Synthesizer) configuration tool based on a modular hierarchical configuration strategy, which is characterized in that a configuration management module is responsible for receiving and managing an interface control file, software process information and equipment information, and generating a DDS configuration project and network topology and equipment communication configuration information; the check and evaluation module generates a QOS strategy matching check result according to the DDS configuration project, the network topology and the equipment communication configuration information generated by the configuration management module, and calculates the total network flow of data transmitted by each topology edge; and after receiving the modularized QOS configuration template information, the hierarchical configuration module generates a corresponding DDS theme configuration file and a QOS configuration file according to the DDS configuration project generated by the configuration management module and the DDS publishing subscription relationship list generated by the verification and evaluation module. According to the invention, the modularized hierarchical configuration of the DDS is realized, so that the combination and unified management of the publishing and subscribing mechanism, the QOS mechanism, the ICD and the data are realized.

Description

Technical Field

[0001] This invention belongs to the field of DDS configuration and relates to a DDS configuration tool and its configuration method based on a modular hierarchical configuration strategy. Background Technology

[0002] Data Distribution Service (DDS) is a decentralized peer-to-peer network transport protocol based on a publish-subscribe model, developed by the Object Management Group (OMG), and is now widely used in various fields. Existing DDS configuration tools often focus on the configuration and policy settings of DDS itself, paying less attention to network devices. Furthermore, they do not focus on the data itself or ICD configuration, and are mainly divided into two types:

[0003] 1) Configuration tools based on the DDS publish-subscribe mechanism: These tools primarily focus on the characteristics of DDS itself, publish-subscribe relationships, QoS compatibility, and other attributes, without concerning themselves with the data itself or the runtime environment. A typical example is RTI's DDS designer.

[0004] 2) Data-based DDS configuration tools: These tools primarily consider DDS applications from the perspective of the project manager, focusing mainly on data matching and ICD management, without concern for the inherent characteristics of DDS itself.

[0005] These two approaches either focus on the characteristics of DDS itself or on the analysis and management of data and ICD, lacking the ideas and means to combine the two. How to simultaneously consider the characteristics of DDS in DDS configuration design and data and ICD design has become a problem that must be solved in the field of DDS application. Summary of the Invention

[0006] The purpose of this invention is to provide a DDS configuration tool and its configuration method based on a modular and hierarchical configuration strategy. Through modular and hierarchical thinking, the DDS configuration process takes into account both the characteristics of the DDS itself and the management of ICD and data.

[0007] The objective of this invention is achieved through the following technical solution:

[0008] A DDS configuration tool based on a modular hierarchical configuration strategy, including a configuration management module;

[0009] The configuration management module is responsible for receiving and managing interface control files, software process information, and device information. The interface control file includes the Data Distribution Service (DDS) topic name, DDS data transmission and reception direction, data length corresponding to the topic name, and the proposed Quality of Service (QoS) strategy. The software process information includes the software process division and the DDS domain participants used by each configuration item. The device information includes the device name, number of devices, and device connection method.

[0010] After summarizing, matching, and organizing the interface control files, software process information, and device information, a DDS configuration project is generated, along with network topology and device communication configuration information.

[0011] Furthermore, it also includes a verification and evaluation module. Based on the DDS configuration project, network topology, and device communication configuration information generated by the configuration management module, the verification and evaluation module pairs the publishers and subscribers of the DDS configuration project according to the DDS publish-subscribe protocol, generates a DDS publish-subscribe relationship list, and iterates through and checks all the publish-subscribe relationships in the list as well as the QoS policies used by the publishers and subscribers respectively. It analyzes the matching of their QoS policies according to the DDS protocol, generates QoS policy matching verification results, and confirms the topological edges in the network topology structure through which the data of each pair of publishers and subscribers communicates, and calculates the total network traffic transmitted by the topological edge.

[0012] Furthermore, it also includes a hierarchical configuration module. After receiving the modular QoS configuration template information, the hierarchical configuration module generates the corresponding DDS topic configuration file based on the DDS configuration project generated by the configuration management module and the DDS publish-subscribe relationship list generated by the verification and evaluation module. Based on the DDS configuration project, it combines the corresponding DDS entity-level QoS template modules to generate the corresponding QoS configuration file.

[0013] The configuration management module can be used alone as needed, or in combination with the configuration management module and the verification and evaluation module, or in combination with the configuration management module, the verification and evaluation module and the hierarchical configuration module.

[0014] Furthermore, the hierarchical configuration module, based on the proposed QoS strategy and the list of data topic publish-subscribe relationships, retrieves the corresponding hierarchical template modules from its own preset hierarchical template module library, according to the DDS entity level to which each QoS strategy belongs, namely entity factory level, domain participant level, publisher / subscriber level, data reader / writer level, and data topic level. It then combines these template modules into a QoS strategy configuration template, and generates the corresponding QoS configuration file based on the values ​​assigned by the user to each template variable. The entity factory level is associated with devices, the domain participant level with software processes, and the publisher / subscriber, data reader / writer, and data topic levels are all associated with data topics.

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

[0016] 1. This invention realizes the modular and hierarchical configuration of DDS, thereby achieving the integration and unified management of publish-subscribe mechanism, QoS mechanism, ICD and data.

[0017] 2. This invention realizes QoS policy matching verification and DDS network traffic analysis.

[0018] 3. This invention allows users to write their own QOS template modules, thereby achieving high configurability. Attached Figure Description

[0019] Figure 1 This is a schematic diagram of the structure of a DDS configuration tool based on a modular hierarchical configuration strategy. Detailed Implementation

[0020] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0021] See Figure 1 As shown in this embodiment, a DDS configuration tool based on a modular hierarchical configuration strategy includes a configuration management module, a verification and evaluation module, and a hierarchical configuration module.

[0022] The configuration management module is responsible for receiving and managing Interface Control Documents (ICDs), software process information, and device information, and generating DDS configuration projects, as well as network topology and device communication configuration information based on the received information.

[0023] The ICD file contains information such as DDS topic names, DDS data transmission and reception directions, data lengths corresponding to topic names, and the proposed Quality of Service (QoS) policy. Software process information includes software process divisions and the DDS domain participants used by each configuration item. Device information includes device names, number of devices, and device connection methods. The device information, including device names, number of devices, and connection methods, reveals the specific topology of the backbone network. If devices share DDS topic names, and one device is for receiving while the other is for transmitting, and the QoS policies at both ends are compatible (no conflicts or mismatches), a publish / subscribe relationship is formed, connected by a line in the topology diagram. Of course, there may be cases of one transmitter receiving multiple receivers, multiple transmitters receiving one receiver, or multiple transmitters receiving multiple receivers, depending on the distribution of DDS topics across devices and the compatibility of QoS policies. Therefore, by summarizing, matching, and organizing the ICD file, software process information, and device information, a DDS configuration project, as well as network topology and device communication configuration information, can be generated.

[0024] The following points should be noted in the DDS configuration process:

[0025] A. The sending and receiving directions of topics on both the publisher and subscriber sides should be correct, with the sender being the publisher and the receiver being the subscriber.

[0026] B. The topic QoS strategies on both the publish and subscribe ends should be compatible.

[0027] C. Compatibility of the specific topology of the publish / subscribe ends with the backbone network. The receiving and sending ends should have network links and should not pass through devices or ports that would prevent DDS data from passing, such as firewalls, communication repeaters, modems, and network gateways.

[0028] The verification and evaluation module, based on the DDS configuration project, network topology, and device communication configuration information generated by the configuration management module, pairs the publishers and subscribers of the DDS configuration project according to the DDS publish-subscribe protocol, generates a list of DDS publish-subscribe relationships, and iterates through and checks all pairs of publish-subscribe relationships in the list, as well as the QoS policies used by the publishers and subscribers respectively. It analyzes the matching of their QoS policies according to the DDS protocol, generates QoS policy matching verification results, and confirms the topological edges in the network topology structure through which the data of each pair of publishers and subscribers communicates, and calculates the total network traffic transmitted by the topological edge.

[0029] The hierarchical configuration module receives modular QoS configuration template information and generates corresponding DDS topic configuration files based on the DDS configuration project generated by the configuration management module and the DDS publish-subscribe relationship list generated by the verification and evaluation module. It also combines the corresponding DDS entity-level QoS template modules according to the DDS configuration project to generate corresponding QoS configuration files.

[0030] Based on the proposed QoS strategy and the list of data topic publish-subscribe relationships, the system retrieves the corresponding hierarchical template modules from its pre-set hierarchical template module library, according to the DDS entity level to which each QoS strategy belongs (i.e., entity factory level, domain participant level, publisher / subscriber level, data reader / writer level, and data topic level). These modules are then combined into a QoS strategy configuration template. Finally, based on the values ​​assigned to the variables in each template by the user, a corresponding QoS configuration file is generated. The entity factory level is associated with devices, the domain participant level with software processes, and the publisher / subscriber, data reader / writer, and data topic levels are all associated with data topics.

[0031] Each device should contain multiple software (processes), and each process should have its own DDS topic configuration file and QoS file. The DDS topic configuration file contains the DDS topic name, DDS data transmission and reception direction, the data length corresponding to the topic name, and the proposed QoS policy. The QoS file contains each QoS policy and its specific QoS configuration.

[0032] This invention directly parses the input ICD file, software process information, and device information, and generates corresponding DDS topic configuration files and QoS configuration files based on a modular hierarchical configuration strategy. It can also verify and evaluate the matching of network data traffic and QoS policies at the engineering level, thereby improving engineering configuration efficiency and correctness, and guiding and supporting the development, supervision, and management of DDS projects. This invention can use the configuration management module alone, in combination with the verification and evaluation module, or all three modules together, depending on the configuration tool's running status and user operations, to suit different scenarios and needs.

[0033] The configuration method of the DDS configuration tool based on the modular hierarchical configuration strategy described above includes the following steps:

[0034] A1. The user inputs the ICD file, software process information, and device information, and issues a command to the configuration management module to generate a DDS configuration project;

[0035] After steps B1 and A1 are completed and the DDS configuration project is generated, the user issues a command to the verification and evaluation module to generate a list of DDS publish-subscribe relationships and generate QoS policy matching verification results.

[0036] After C1 and B1 complete and generate the DDS publish-subscribe relationship list, the user issues a command to the hierarchical configuration module to generate a QoS policy configuration template. Then, the user assigns values ​​to each template variable and issues a command to the hierarchical configuration module to generate the corresponding QoS configuration file.

[0037] It is understood that those skilled in the art can make equivalent substitutions or modifications to the technical solution and inventive concept of the present invention, and all such substitutions or modifications should fall within the protection scope of the appended claims.

Claims

1. A DDS configuration tool based on a modular hierarchical configuration strategy, characterized in that... Includes a configuration management module; The configuration management module is responsible for receiving and managing interface control files, software process information, and device information. The interface control file includes the Data Distribution Service (DDS) topic name, DDS data transmission and reception direction, data length corresponding to the topic name, and the proposed Quality of Service (QoS) strategy. The software process information includes the software process division and the DDS domain participants used by each configuration item. The device information includes the device name, number of devices, and device connection method. After summarizing, matching, and organizing the interface control files, software process information, and device information, a DDS configuration project is generated, along with network topology and device communication configuration information.

2. The DDS configuration tool based on a modular hierarchical configuration strategy according to claim 1, characterized in that... It also includes a verification and evaluation module. Based on the DDS configuration project, network topology, and device communication configuration information generated by the configuration management module, the verification and evaluation module pairs the publishers and subscribers of the DDS configuration project according to the DDS publish-subscribe protocol, generates a DDS publish-subscribe relationship list, and iterates through and checks all the publish-subscribe relationships in the list as well as the QoS policies used by the publishers and subscribers respectively. It analyzes the matching of their QoS policies according to the DDS protocol, generates QoS policy matching verification results, and confirms the topological edges in the network topology structure through which the data of each pair of publishers and subscribers communicates, and calculates the total network traffic transmitted by the topological edge.

3. A DDS configuration tool based on a modular hierarchical configuration strategy according to claim 2, characterized in that... It also includes a hierarchical configuration module. After receiving the modular QoS configuration template information, the hierarchical configuration module generates the corresponding DDS topic configuration file based on the DDS configuration project generated by the configuration management module and the DDS publish-subscribe relationship list generated by the verification and evaluation module. Based on the DDS configuration project, it combines the corresponding DDS entity-level QoS template modules to generate the corresponding QoS configuration file. The configuration management module can be used alone as needed, or in combination with the configuration management module and the verification and evaluation module, or in combination with the configuration management module, the verification and evaluation module and the hierarchical configuration module.

4. A DDS configuration tool based on a modular hierarchical configuration strategy according to claim 3, characterized in that... The hierarchical configuration module, based on the proposed QoS strategy and the list of data topic publish-subscribe relationships, retrieves the corresponding hierarchical template modules from its own preset hierarchical template module library. These modules are selected according to the DDS entity level to which the individual QoS strategy belongs (i.e., entity factory level, domain participant level, publisher / subscriber level, data reader / writer level, and data topic level). The module then combines these modules into a QoS strategy configuration template. Finally, based on the values ​​assigned to the variables in each template by the user, the module generates the corresponding QoS configuration file. The entity factory level is associated with devices, the domain participant level with software processes, and the publisher / subscriber, data reader / writer, and data topic levels are all associated with data topics.

Images