Network middleware of distributed simulation data exchange system

Abstract

The invention discloses network middleware of a distributed simulation data exchange system, and relates to the technical field of computers, and the network middleware comprises a network data management module which is used for converting network data into a standard data format, obtaining standard data and managing the standard data; the data distribution module is used for generating a configuration file of the standard data by utilizing an interface definition file automatic generation technology; the data subscription and release service module is used for establishing a global data space in a memory by adopting a data distribution service protocol, and the global data space is used for real-time data exchange among distributed application nodes; the node management module is used for querying operation states and online and offline states of the application nodes and the application components; the communication configuration management module is used for generating a communication configuration file of the distributed node; and the application data exchange module is used for managing data interaction among different application components. According to the method, the communication efficiency among the nodes in the distributed simulation data exchange system can be effectively improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and particularly to a network middleware for a distributed simulation data exchange system. Background Art

[0002] With the rapid development of computer technology, more application software is required to run on many different network protocols, different hardware manufacturers, and different network platforms and environments. Among them, for hardware-in-the-loop docking, the network connection is mainly established through a bus. Due to different types of shielded buses, it is necessary to unify the driver interface: first, load the bus configuration information, establish a communication connection, call the sending interfaces of different drivers according to the data information when sending data, and when receiving data, parse the data according to the data protocol and send the data payload to the transport layer. For virtual environments, the network connections established with other nodes through the Data Distribution Service (DDS) or the ZeroMQ (ZMQ) messaging library also require loading communication configurations and initializing different entities according to the configurations, which results in poor communication efficiency between nodes. Summary of the Invention

[0003] The purpose of the present application is to provide a network middleware for a distributed simulation data exchange system, which can effectively improve the communication efficiency between nodes in the distributed simulation data exchange system.

[0004] To achieve the above purpose, the present application provides the following solutions:

[0005] The present application provides a network middleware for a distributed simulation data exchange system, including:

[0006] A network data management module, configured to convert network data into a standard data format, obtain standard data, and manage it;

[0007] A data distribution module, configured to generate a configuration file for standard data by using the interface definition file automatic generation technology;

[0008] A data subscription and publication service module, configured to establish a global data space in memory by using the data distribution service protocol, where the global data space is used for real-time data exchange between distributed nodes;

[0009] A node management module, configured to query the running status and online / offline status of application nodes and application components;

[0010] A communication configuration management module, configured to generate a communication configuration file for distributed nodes;

[0011] An application data exchange module, configured to manage data interaction between different application components.

[0012] Optionally, the standard data format is Extensible Markup Language.

[0013] Optionally, the network data management module specifically includes:

[0014] A template import unit for importing a standard data format template;

[0015] An editing unit for visually editing the standard data format according to the imported standard data format template.

[0016] Optionally, the configuration file includes a data sender, a data receiver, a data transmission protocol, and a data body structure.

[0017] Optionally, the data distribution module includes one or more of 1553, 429, 422, AFDX, and FC bus interfaces.

[0018] Optionally, the data subscription and publishing service module adopts a data distribution service protocol with a decentralized architecture.

[0019] Optionally, the data subscription and publishing service module stores QoS quality policies.

[0020] Optionally, the node management module is further configured to automatically detect and identify node information manually added by a user according to a communication configuration file and manage it.

[0021] Optionally, the application data exchange module is used to manage data interaction between different application components on the same host, data interaction between multiple application components between different hosts, and data interaction between multiple application components between different distributed nodes.

[0022] Optionally, the application data exchange module performs data interaction by configuring communication parameters in QoS quality policies.

[0023] According to the specific embodiments provided by the present application, the present application discloses the following technical effects:

[0024] The present application provides a network middleware for a distributed simulation data exchange system. The network middleware for the distributed simulation data exchange system constructed through the design of a network data management module, a data distribution module, a data subscription and publishing service module, a node management module, a communication configuration management module, and an application data exchange module can effectively improve the communication efficiency among nodes in the distributed simulation data exchange system. Through the network middleware for the distributed simulation data exchange system of the present application, a distributed simulation data exchange network can be built. The distributed simulation data exchange network is used to construct the communication network among nodes in the software integration debugging environment. By adopting the network middleware for the distributed simulation data exchange system, a global data sharing and distribution resource pool can be provided, and a standardized data transmission service can be provided, so that each node in the integration debugging environment does not need to pay attention to the differences in the underlying platforms, and the deployment and transplantation are more convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0026] Figure 1 It is a schematic structural diagram of the network middleware for the distributed simulation data exchange system provided by the present application;

[0027] Figure 2 It is a working process diagram of the XML configuration file automatic generation tool provided by the present application;

[0028] Figure 3 It is a schematic process diagram for querying the running status of application nodes and application components provided by the present application;

[0029] Figure 4 It is a schematic process diagram for communication through the distributed simulation data exchange network provided by the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0030] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0031] In order to make the above objects, features, and advantages of the present application more obvious and understandable, the present application will be further described in detail below with reference to the drawings and specific embodiments.

[0032] The network middleware of the distributed simulation data exchange system in this application (hereinafter referred to as middleware) is based on DDS network communication. DDS network communication uses the "subscribe-publish" method to achieve one-to-many communication, with a flexible and simple usage method, which is convenient for monitoring data transmission. In addition, DDS network communication also has rich QoS (Quality of Service) strategies, which can effectively ensure the reliability of data transmission. Therefore, DDS network communication is suitable as the network communication method for the virtual test environment. As Figure 1 shown, the network middleware of the distributed simulation data exchange system in this application mainly includes a network data management module, a data distribution module, a data subscription and publication service module, a node management module, a communication configuration management module, and an application data exchange module. Each module is called successively according to the data transmission process. The specific settings of each module are as follows.

[0033] 1. Network Data Management Module

[0034] The network data management module in this application is used to convert network data into a standard data format, obtain standard data, and perform data management. Among them, the standard data format is Extensible Markup Language (XML), that is, the network data management module stores network data using Extensible Markup Language.

[0035] The network data management module specifically includes: a template import unit for importing a standard data format template; an editing unit for visually editing the standard data format according to the imported standard data format template. Specifically, the network data management module supports the management of the standard data format, supports the import of the standard data format template, and supports the visual editing of the standard data format. Table 1 is the storage structure of the standard data, that is, the standard data format node table, Table 2 is the standard data format node attribute table, which describes the standard data format node attribute structure, and Table 3 is the standard data format node-attribute association relationship table, which describes the standard data format node-attribute association relationship structure.

[0036] Table 1 Standard Data Format Node Table

[0037]

[0038]

[0039] Table 2 Standard Data Format Node Attribute Table

[0040] Attribute ID Attribute Name Attribute Value

[0041] Table 3 Standard Data Format Node-Attribute Association Relationship Table

[0042] ID Node ID Attribute ID

[0043] The network data management module supports the management of ICD data format, and supports importing the ICD data format template through the ICD description file, and uniformly converting the designed ICD text file,.h file or.C file into an XML file. It supports the visual editing of the ICD data format, and creates, edits, and modifies the ICD file by adding keywords and modifying the values of keywords.

[0044] 2. Data distribution module

[0045] The data distribution module of this application is used to generate a configuration file of standard data by using the interface definition file automatic generation technology. Among them, the configuration file includes the data sender, data receiver, data transmission protocol, and data body structure (data assembled according to a certain structure). Specifically, the data distribution module supports data communication between multiple application nodes through configuration, and the data distribution module needs to configure information such as the data sender, data receiver, data transmission protocol, and data body structure. The function implemented by the data distribution module of this application uses the interface definition file automatic generation technology to generate a configuration file of standard data (XML format data) for the DDS network middleware (distributed simulation data exchange system network middleware), also known as the XML configuration file, to achieve the consistency of the sending and receiving logic of the DDS network nodes and the ICD description.

[0046] The data distribution module parses the data according to the read ICD file and generates the corresponding XML configuration file, and then calls the DDS data forwarding interface for data sending and receiving. Its working process is as Figure 2 shown.

[0047] In addition, the data distribution module of this application also includes one or more of the 1553, 429, 422, AFDX, and FC bus interfaces, and supports the simulation of the 1553, 429, 422, AFDX, and FC bus interfaces.

[0048] 3. Data subscription and publication service module

[0049] The data subscription and publication service module of this application is used to establish a global data space in memory by using the data distribution service protocol, and the global data space is used for real-time data exchange between distributed nodes.

[0050] The data subscription and publishing service module supports data communication based on the subscription and publishing mode; the Data-Centric Publish-Subscribe (DCPS) model of DDS constructs a concept of a shared "global data space", just like opening up a shared memory. The publisher stores all data objects in this space, and the subscriber only needs to obtain the data objects corresponding to the topic words according to the topic words in the global data space, that is, distributed nodes (distributed nodes refer to computers, network devices, digital models, application programs distributed in different geographical locations or network topologies), and these data objects can be accessed through simple read and write operations. DDS provides four message modes: publish-subscribe, point-to-point (the message sender and the message receiver correspond one by one), point-to-multiple (one message sender and multiple message receivers), and multiple-to-multiple (multiple message senders and multiple message receivers). In the data subscription and publishing service module of this application, the publish-subscribe and message queue message modes are mainly used.

[0051] The data subscription and publishing service module adopts the Real-Time Innovations Data Distribution Service (RTIDDS), a real-time messaging middleware of the data distribution service protocol with a decentralized architecture. RTIDDS is a type of DDS and is designed with a decentralized architecture. Having a center means there is a performance limit, and the center determines the performance limit of the entire architecture.

[0052] The data subscription and publishing service module stores QoS quality policies to support the setting of data transmission service quality. The DDS specification lists and formally defines a comprehensive set of QoS policies, which can configure the reliability of data transmission, system transmission load, security, etc., and can use QoS for system control. Each DCPS entity has its own QoS quality policy, and an independent QoS agreement can be established between each pair of publishers and subscribers. This enables DDS to well configure and utilize system resources, coordinate the balance between predictability and execution efficiency, and support complex and changing data flow requirements.

[0053] 4. Node Management Module

[0054] The node management module of this application is used to query the running status and online / offline status of application nodes and application components. Specifically, the node management module supports querying the online / offline status of application nodes and application components.

[0055] The node management module supports querying the running status of application nodes and application components. The status of application nodes and application components is updated by sending status messages to the distributed simulation data exchange system network middleware at regular intervals by application nodes and application components, specifically as Figure 3As shown. Different nodes will regularly send the status information of their own nodes to the distributed simulation data exchange system network middleware. Any object that subscribes to the status information of a certain node will receive an update of the corresponding node status information.

[0056] The node management module of the distributed simulation data exchange system network middleware is also used to automatically detect and identify the node information manually added by the user according to the configuration, query in real time the node information added in the DDS domain, and manage the newly added nodes.

[0057] 5. Communication Configuration Management Module

[0058] The communication configuration management module of this application is used to generate communication configuration files for distributed nodes. Specifically, the communication configuration management module of this application supports the mapping configuration of ICD data IDs and topic IDs, and each node corresponds to its own communication configuration file. Each node communicates through the distributed simulation data exchange network, and each node is mounted on the distributed simulation data exchange network, specifically as Figure 4 shown.

[0059] The communication configuration file corresponding to Node 1 is:

[0060]

[0061]

[0062]

[0063]

[0064] Among them, the IP of the other party that needs to communicate is filled in the element tag.

[0065] The type tag defines the format of the transmitted data.

[0066] The const tag defines the minimum and maximum lengths of the data fields.

[0067] The struct tag defines the member fields of the transmitted data.

[0068] The member tag defines the field name, data type, and whether it is a unique identifier of the data member. The domain tag defines the ID of the domain.

[0069] The register_type tag defines the data type referenced by the domain ID. The topic defines the topic of the transmitted data.

[0070] The topic_qos defines the configuration policy referenced by the topic.

[0071] The domain_participant defines the participant.

[0072] The publisher defines the list of publishers.

[0073] The data_writer defines the publisher information.

[0074] The topic_ref defines the topic information referenced by the publisher. The subscriber defines the list of subscribers.

[0075] The data_reader defines the subscriber information.

[0076] The topic_ref defines the topic information referenced by the subscriber.

[0077] The communication configuration file corresponding to Node 2 is:

[0078]

[0079]

[0080]

[0081]

[0082]

[0083]

[0084]

[0085] Among them, the IP of the other party that needs to communicate is filled in the element tag.

[0086] The type tag defines the format of the transmitted data.

[0087] The const tag defines the minimum and maximum lengths of the data fields.

[0088] The struct tag defines the member fields of the transmitted data.

[0089] The member tag defines the field name, data type, and whether it is a unique identifier of the data member. The domain tag defines the domain ID.

[0090] The register_type tag defines the data type referenced by the domain ID.

[0091] The topic defines the theme of the transmitted data.

[0092] The topic_qos defines the configuration policy for topic references.

[0093] The domain_participant defines the participant.

[0094] The publisher defines the list of publishers.

[0095] The data_writer defines the publisher information.

[0096] The topic_ref defines the topic information referenced by the publisher.

[0097] The subscriber defines the list of subscribers.

[0098] The data_reader defines the subscriber information.

[0099] The topic_ref defines the topic information referenced by the subscriber.

[0100] 6. Application Data Exchange Module

[0101] The application data exchange module of this application is used to manage data interaction between different application components. This module can: support data interaction between multiple application components in a single PC; support data interaction between multiple application components in multiple PCs; support data interaction between multiple application components in multiple distributed nodes; support IP address configuration and communication port configuration of multiple application components in multiple distributed application nodes.

[0102] The functions of the data exchange module are implemented by configuring the corresponding communication parameters in the QoS quality policy.

[0103] The network middleware of the distributed simulation data exchange system of this application is used to build the communication network between nodes in the software integration debugging environment. By adopting the distributed data interaction middleware, it provides a global data sharing and distribution resource pool, provides a standardized data transmission service, supports the management of standard data formats, supports importing standard data format templates, supports visual editing of standard data formats; supports automatic conversion between standard format data and ICD format data; data communication adopts the subscription / publish mode of DDS, and realizes data communication between multiple application nodes through configuration; provides query of the running status of application nodes and components.

[0104] The network middleware of the distributed simulation data exchange system in this application provides a unified and open data access interface for the application layer, enabling network communication programming to shift from connection-oriented to data-oriented. Applications can obtain data without operating the underlying transmission, eliminating the design and implementation process of the transport layer interface for application software. In addition, by introducing the DDS network middleware that supports multiple general-purpose and special-purpose operating systems and platforms in the distributed simulation data exchange system, the network middleware of this application encapsulates the underlying hardware, operating system, and transport protocol, achieving decoupling between the application layer, physical layer, and transport layer, and improving the portability of application software. Through the clear hierarchical structure and flexible configuration interface of the DDS network middleware, the network middleware of the distributed simulation data exchange system in this application enables the distributed simulation data exchange system to obtain configurable capabilities in multiple aspects such as configurable data interfaces, configurable communication service quality, configurable entity discovery methods, and configurable transport protocols.

[0105] In summary, the network middleware of the distributed simulation data exchange system is a network middleware product for building a virtual test network. It can build a virtual platform network that conforms to the DDS standard, realize communication between various model nodes, simulation nodes, and semi-physical nodes in the network, and support semi-physical verification and physical verification of the avionics system by expanding physical interfaces. The network middleware of the distributed simulation data exchange system in this application constructs a communication network based on the DDS data distribution service protocol of the Ethernet network, breaking through key technologies such as transmission service dynamic loading technology, network entity automatic discovery technology, interface definition file automatic generation technology, communication service quality configuration technology, and reliability assurance strategies. It transforms the end-to-end and end-to-server system network configuration into a topic-based and data-centric system network configuration, decoupling communication nodes within the system, overcoming single-point failures, ensuring its scalability and reliability, and realizing the rapid dynamic construction of the system.

[0106] A specific usage scenario of the network middleware of the distributed simulation data exchange system can be as follows: After the airborne display and control node subscribes to the threat target location information according to the ICD ID in the distributed simulation data exchange system network, the radar node sends the corresponding scanned threat target location information ICD data to the distributed simulation data exchange system network through the 1553B bus, and the airborne display and control node can obtain the threat target location information ICD data in real time.

[0107] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as within the scope described in this specification.

[0108] In this text, specific examples are used to illustrate the principle and implementation of this application. The description of the above embodiments is only for helping to understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A distributed simulation data exchange system network middleware, characterized in that: include: The network data management module is used to convert network data into a standard data format, obtain standard data and manage it; A data distribution module, used to generate a configuration file of standard data by using an interface definition file automatic generation technology; A data subscription and publishing service module is used to establish a global data space in the memory using a data distribution service protocol, and the global data space is used for real-time data exchange between distributed nodes; The node management module is used to query the running status and online and offline status of application nodes and application components; A communication configuration management module, used to generate communication configuration files for distributed nodes; The application data exchange module is used to manage data interaction between different application components.

2. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The standard data format is Extensible Markup Language.

3. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The network data management module specifically includes: Template import unit, used to import standard data format templates; The editing unit is used to visually edit the standard data format according to the imported standard data format template.

4. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The configuration file includes a data sender, a data receiver, a data transmission protocol and a data body structure.

5. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The data distribution module includes one or more of 1553, 429, 422, AFDX and FC bus interfaces.

6. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The data subscription and publishing service module adopts a data distribution service protocol with a decentralized architecture.

7. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The data subscription and publishing service module stores a QoS quality policy.

8. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The node management module is also used to automatically detect and identify node information manually added by the user according to the communication configuration file and manage it.

9. The distributed simulation data exchange system network middleware according to claim 1, characterized in that: The application data exchange module is used to manage data interaction between different application components on the same host, data interaction between multiple application components on different hosts, and data interaction between multiple application components on different distributed nodes.

10. The distributed simulation data exchange system network middleware according to claim 7, characterized in that: The application data exchange module performs data interaction by configuring the communication parameters in the QoS quality policy.

Images