Distributed middleware architecture based on data driving

Abstract

The invention provides a distributed middleware architecture based on data driving, and relates to the technical field of data processing. The distributed middleware architecture is a simulation system for realizing real-time dynamic confrontation, the simulation system is used for simulating cooperative operation among a plurality of devices, and the middleware architecture comprises a system construction layer 1, an operation environment layer 2, an application model layer 3 and a database system 5. The architecture has high modularization and parallel performance, can effectively support complex and large-scale adversarial simulation application, can realize efficient and flexible simulation operation, and provides a reliable solution for a simulation scene.

Description

Technical Field

[0001] The present disclosure relates to the technical field of data processing, and particularly to a data-driven distributed middleware architecture. Background Art

[0002] A simulation system for confrontation can simulate the cooperation among various confrontation devices in a confrontation scenario. In this way, it can provide guidance for combat scenarios.

[0003] Traditional simulation methods have deficiencies in real-time simulation of complex systems. Moreover, in the prior art, there is a lack of corresponding system architecture design for a dynamic data-driven distributed simulation system, so a reliable solution cannot be provided for simulation scenarios. Summary of the Invention

[0004] In view of this, the purpose of the present disclosure is to propose a data-driven distributed middleware architecture, which can specifically solve existing problems.

[0005] Based on the above purpose, in the first aspect, the present disclosure proposes a data-driven distributed middleware architecture, including: the distributed middleware architecture is a simulation system for realizing real-time dynamic confrontation, and the simulation system is used to simulate the cooperative operation among multiple devices. The middleware architecture includes: a system construction layer 1, a running environment layer 2, an application model layer 3, and a database system 5; the running environment layer 2 is communicatively connected to the system construction layer 1, the application model layer 3, and the database system 5 respectively, and the system construction layer 1 is communicatively connected to the database system 5; the system construction layer 1 includes at least two components, and the components include a management system and components; the running environment layer 2 communicates between the components through a communication protocol; the application model layer 3 includes multiple simulation models, and the simulation models are used to simulate the confrontation scenarios in which the multiple devices in the simulation system participate.

[0006] In the second aspect, an electronic device is further provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor runs the computer program to implement the method described in the first aspect.

[0007] In the third aspect, a computer-readable storage medium is further provided, on which a computer program is stored, and the computer program is executed by a processor to implement the method described in any item of the first aspect.

[0008] In the fourth aspect, a computer program product is further provided, including a computer program, and the computer program is executed by a processor to implement the method described in any item of the first aspect.

[0009] Generally speaking, the present disclosure has at least the following beneficial effects: The implementation scheme of the dynamic data-driven distributed simulation system is described in detail from three perspectives: architecture design, system functions, and architecture operating environment, and based on this, the overall architecture of the data-driven distributed middleware is constructed. This architecture has high modularity and parallel performance, can effectively support complex and large-scale confrontation simulation applications, can achieve efficient and flexible simulation operation, and provides a reliable solution for simulation scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In the drawings, unless otherwise specified, the same reference numerals throughout the several views denote the same or similar components or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in accordance with the present disclosure and should not be regarded as limiting the scope of the present disclosure.

[0011] Figure 1 System block diagram of the present invention;

[0012] Figure 2 System flow chart of the present invention;

[0013] Figure 3 Architecture diagram of the application system integration and management component of the present invention;

[0014] Figure 4 Architecture diagram of the data management service component of the present invention;

[0015] Figure 5 Architecture diagram of the model management system of the present invention;

[0016] Figure 6 Architecture diagram of the middleware operation management system of the present invention;

[0017] Figure 7 Architecture diagram of the operating environment layer of the present invention;

[0018] Figure 8 Architecture diagram of the application model layer of the present invention;

[0019] Figure 9 Architecture diagram of the distributed simulation engine layer of the present invention;

[0020] Figure 10 Functional flow chart of the application system construction based on the system template;

[0021] Figure 11 Functional flow chart of the architecture test;

[0022] Figure 12 System functional flow chart;

[0023] Figure 13It is a functional flowchart of the model running environment. Specific implementation manners

[0024] The present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than limiting the invention. Additionally, it should be noted that for ease of description, only the parts related to the relevant invention are shown in the drawings.

[0025] It should be noted that, without conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other. The present disclosure will be described in detail below with reference to the drawings and embodiments.

[0026] Figure 1 The distributed middleware architecture based on data - driven of the present disclosure is shown. Among them, 1. System construction layer; 11. Application system integration and management component; 111. Application system construction component; 112. Application system template database; 113. QoS test setting and test component; 12. Data management service component; 121. Model interface data management module; 122. Application system simulation data storage module; 123. Application system test data management module; 13. Model management system; 131. Model construction module; 132. Model library; 133. Model test environment; 14. Middleware operation management system; 141. System real - time inspection module; 142. System running state module; 143. System hardware topology structure management module; 2. Running environment layer; 21. DDS multi - network card communication upgrade module; 22. Simulation operation management module; 23. System loading and initialization module; 24. Display data interface module; 25. Dynamic data interface parsing module; 26. Model running management module; 27. Model running performance detection module; 28. Built - in system test module; 3. Application model layer; 31. Model description file; 32. Model data file; 33. Code execution body; 4. Distributed simulation engine layer; 41. Service layer; 42. Core layer; 43. Communication layer; 5. Database system.

[0027] The distributed middleware architecture is a simulation system for realizing real - time dynamic confrontation. The simulation system is used to simulate the collaborative operation among multiple devices. The middleware architecture includes: system construction layer 1, running environment layer 2, application model layer 3 and database system 4; the running environment layer 2 is communicatively connected to the system construction layer 1, application model layer 3 and database system 4 respectively, and the system construction layer 1 is communicatively connected to the database system 4; the system construction layer 1 includes at least two components, and the components include management systems and components; the running environment layer 2 communicates between the components through communication protocols; the application model layer 3 includes multiple simulation models, and the simulation models are used to simulate the confrontation scenarios in which the multiple devices in the simulation system participate.

[0028] Among them, multiple devices can be various countermeasure devices. For example, radars, aircraft (such as drones). Each device can correspond to an application in the application model layer. Through this simulation system, the operation coordination relationships between different devices can be obtained. For example, the startup and operation of different devices, and the relationships between the startup and operation of each device.

[0029] In the present disclosure, countermeasures can be various activities, such as competitions, battles, etc.

[0030] In some optional implementation manners of any embodiment of the present disclosure, the at least two components include an application system integration and management component 11, a data management service component 12, a model management system 13, and a middleware operation management system 14; the application system integration and management component 11 is used to integrate and manage different simulation applications, and the simulation applications correspond to each device simulated by the simulation system; the data management service component 12 is used to manage and maintain the simulation data in the simulation system, and the simulation data includes model data, application system simulation data, and application system test data; the model management system 13 is used to provide model management services; the middleware operation management system 14 is used for the management and control of middleware.

[0031] Optionally, the application system integration and management component 11 includes an application system construction component 111, an application system template database 112, and a QoS test setting and test component 113; the application system construction component 111 is used to construct different simulation application systems and integrate different simulation application systems into a unified system; the application system template database 112 is used to store different application system templates, and each application system template includes a model, data, and configuration; the QoS test setting and test component 113 is a tool for performing quality tests on the system and is used to simulate different network environments and load conditions.

[0032] Optionally, the data management service component 12 includes a model interface data management module 121, an application system simulation data storage module 122, and an application system test data management module 123; the model interface data management module 121 is used to manage and maintain various simulation models used in the simulation system; the application system simulation data storage module 122 is used to store and manage the simulation data generated by the application system; the application system test data management module 123 is used to manage and maintain the test data generated by the application system.

[0033] Optionally, the model management system 13 includes a model construction module 131, a model library 132, and a model test environment 133. The model construction module 131 is responsible for constructing and developing a simulation model according to the requirements and demands of the simulation system. The model library 132 is used to store all models. The model test environment 133 is a tool for testing and validating models.

[0034] Optionally, the middleware operation management system 14 includes a system real-time inspection module 141, a system operation status module 142, and a system hardware topology structure management module 143. The system real-time inspection module 141 is used to monitor and detect the system operation status in real time. The system operation status module 142 is used to monitor and manage the system operation status in real time. The system hardware topology structure management module 143 is used to manage and maintain the system hardware topology structure.

[0035] In some optional implementation manners of any embodiment of the present disclosure, the operation environment layer 2 includes a DDS multi-network card communication upgrade module 21, a simulation operation management module 22, a system loading and initialization module 23, a display data interface module 24, a dynamic data interface parsing module 25, a model operation management module 26, a model operation performance detection module 27, and a built-in system test module 28. The DDS multi-network card communication upgrade module 21 is used to specify a network card for communication by configuring the parameters of DDS. The simulation operation management module 22 is used to perform QoS management and Topic management. The QoS management is used to select an appropriate QoS policy for configuration according to the actual communication requirements and system resource conditions. The Topic management is used to design a suitable Topic structure according to the data types and data publishers in the system. The system loading and initialization module 23 is used to load the resources and modules required by the system and perform at least one of initialization, configuration, optimization, and adjustment on them. The display data interface module 24 is used to provide a visual data interface for users. The dynamic data interface parsing module 25 is used to parse the received data and convert the data into a format that can be processed by the application program. The model operation management module 26 is used to manage and control the simulation model. The model operation performance detection module 27 is used to monitor and evaluate the operation performance of the simulation model. The built-in system test module 28 is used to test the functions and performance of the simulation system.

[0036] In some optional implementation manners of any embodiment of the present disclosure, the application model layer 3 includes a model description file 31, a model data file 32, and a code execution body 33. The model description file 31 includes the structure and attribute information of the application model layer 3. The model data file 32 includes the data information required by the application model layer 3. The code execution body 33 is the code of the application model layer 3 regarding the platform and programming language.

[0037] In some alternative implementation manners of any embodiment of the present disclosure, the distributed middleware architecture further includes a distributed simulation engine layer 5; the distributed simulation engine layer 5 includes a service layer 51, a core layer 52, and a communication layer 53; the service layer 51 is used to provide a parallel simulation interface to enhance model reuse and interoperability in parallel simulation; the core layer 52 is used to manage the simulation progress; and the communication layer 53 is used for message passing.

[0038] Optionally, the functions of the core layer 52 include logical process management, event management, time management, rollback framework, statistical management, checkpoint recovery, framework persistence, and interaction framework.

[0039] An embodiment provided by the present invention: A data-driven based distributed middleware overall architecture includes a system construction layer 1, a running environment layer 2, an application model layer 3, a distributed simulation engine layer 5, and a database system 4. The running environment layer 2 establishes data connections with the system construction layer 1, the application model layer 3, the distributed simulation engine layer 5, and the database system 4 respectively, and the system construction layer 1 establishes a data connection with the database system 4.

[0040] The system construction layer 1 is the uppermost layer of the system, the running environment layer 2 is the middle layer of the system, and uses DDS (Data Distribution Service) as the communication protocol to be responsible for communication between components. The application model layer 3 is the bottom layer of the system and consists of corresponding simulation models, which are responsible for simulating and calculating various scenarios and situations in the simulation system, including operations such as loading, initializing, running, and outputting results of the models. Through the operations and calculations of the model layer, various scenarios and situations in the simulation system can be generated and the simulation results can be output. The distributed simulation engine layer 5 is a task separated from the simulation model and independent of specific simulation objects, forming a control program to drive the simulation to run. The distributed simulation engine layer 5 uses a distributed parallel simulation engine (Distributed Paralleled Simulation Engine, DPSE), and the database system 4 is a system composed of a database and its management software.

[0041] The system construction layer 1 includes an application system integration and management component 11, a data management service component 12, a model management system 13, and a middleware operation management system 14. The application system integration and management component 11 is used to integrate and manage different simulation applications. The data management service component 12 is responsible for managing and maintaining the data in the simulation system, including model data, application system simulation data, and application system test data. The model management system 13 is used to provide model management services, and the middleware operation management system 14 is used for the management and control of the middleware.

[0042] The application system integration and management component 11 includes an application system construction component 111, an application system template database 112, and a QoS test setting and test component 113.

[0043] The application system construction component 111 is used to construct different simulation application systems and integrate the constructed systems into a unified system. It can receive application programs from application system developers and then, through a series of processing and transformation, convert the unified system into a form suitable for running in a dynamic data-driven distributed simulation system. At the same time, the application system integration and management component 11 can also configure and manage the application system as needed, including operations such as starting, stopping, and configuring the system.

[0044] The application system template database 112 is used to store different simulation application system templates. It can store different types of templates, and each template includes models, data, configurations, etc., for use when needed. The application system integration and management component 11 can upload the templates generated by the application system construction component 111 to the database or obtain corresponding templates from the database for use in the application system integration and management process.

[0045] The QoS test setting and test component 113 is a tool for quality testing of the system. It can simulate different network environments, load conditions, etc. to evaluate the performance and stability of the system. By testing the system in different aspects, potential performance problems can be effectively discovered and solved, and the reliability and availability of the system can be improved. QoS (Quality of Service), and the application components in the application system integration and management component 11 consist of three types of resources: live resources, virtual resources, and constructed resources.

[0046] The simulation application includes interfaces for application models, application combinations, and application data.

[0047] The data management service component 12 includes a model interface data management module 121, an application system simulation data storage module 122, and an application system test data management module 123.

[0048] The model interface data management module 121 is responsible for managing and maintaining various models used in the simulation system. This module can perform operations such as classifying, storing, retrieving, and updating models, and provide corresponding interfaces for other components to call. At the same time, this module can also perform version management and control of models for rollback or upgrade when needed.

[0049] The application system simulation data storage module 122 is responsible for storing and managing the simulation data generated by the application system. This module can classify and store the simulation data according to certain rules for retrieval and query when needed. At the same time, this module can also provide data backup and recovery services to ensure the security and integrity of the data.

[0050] The application system test data management module 123 is responsible for managing and maintaining the test data generated by the application system. This module can classify, store, retrieve, and update the test data, and provide corresponding interfaces for other components to call. At the same time, this module can also analyze and process the test data to evaluate the performance and stability of the system.

[0051] The model management system 13 includes a model construction module 131, a model library 132, and a model test environment 133.

[0052] The model construction module 131 is responsible for constructing and developing simulation models according to the requirements of the simulation system. This module can receive the model requirements from the application system integration and management component 11 and convert them into executable models. At the same time, it can adjust and optimize the models as needed to meet the requirements of system simulation.

[0053] The model library 132 is a place to store all models. This library can store different types of models, including static models, dynamic models, etc. The model construction module 131 can upload models to the model library 132 and provide corresponding interfaces for other components to call for retrieval and query when needed. At the same time, this module can also manage and control the versions of the models for rollback or upgrade when needed.

[0054] The model test environment 133 is a tool for testing and validating models. In this environment, different tests can be performed on the models, including performance tests, stability tests, etc. By performing different aspects of tests on the models, potential problems can be effectively discovered and solved, and the reliability and accuracy of the models can be improved. At the same time, this environment can also provide test services and data for other components to support the construction and operation of the entire simulation system.

[0055] The middleware operation management system 14 includes a system real-time inspection module 141, a system running status module 142, and a system hardware topology structure management module 143. The system real-time inspection module 141 is used for the real-time monitoring and detection of the system operation status. This module can detect the operation status of the middleware, including the availability, stability, etc. of the middleware, and report the abnormal conditions of the middleware in a timely manner. At the same time, this module can also evaluate and predict the system operation condition to discover potential problems in advance and perform corresponding processing and optimization. The system running status module 142 is used for the real-time monitoring and management of the system operation status. This module can display the real-time data of the system operation status and provide corresponding interfaces for other components to call. At the same time, this module can also adjust and optimize the system to improve the performance and stability of the system. Through this module, the operation status and situation of the system can be grasped in a timely manner for corresponding adjustment and optimization. The system hardware topology structure management module 143 is used for the management and maintenance of the system hardware topology structure. This module can classify and store the system hardware for retrieval and query when needed. At the same time, this module can also optimize and adjust the hardware topology structure to improve the performance and stability of the system. Through this module, the hardware resources of the system can be better managed and maintained to ensure the reliability and effectiveness of the system.

[0056] The operating environment layer 2 includes the DDS multi-network card communication upgrade module 21, the simulation operation management module 22, the system loading and initialization module 23, the display data interface module 24, the dynamic data interface parsing module 25, the model operation management module 26, the model operation performance detection module 27, and the built-in system test module 28. The DDS multi-network card communication upgrade module 21 can specify which network cards to use for communication by configuring the parameters of DDS, thereby realizing communication between multiple network cards. In addition, this module can also upgrade and optimize the communication protocol to adapt to different communication requirements. The simulation operation management module 22 includes QoS and Topic management, specifically including the following aspects: QoS (Quality of Service) management: Select an appropriate QoS policy for configuration according to the actual communication requirements and system resource conditions. Common QoS parameters include reliability, real-time performance, bandwidth, latency, etc. Topic management: Design a suitable Topic structure according to the data types and data publishers in the system to achieve precise data transmission and subscription. Common Topic parameters include topic name, data type, data publisher, etc. Dynamic adjustment of QoS and Topic: Dynamically adjust the configurations of QoS and Topic according to the actual operation situation of the system to achieve the optimal performance of the system. The system loading and initialization module 23 is used to load the resources and modules required by the system and initialize and configure them. At the same time, this module can also optimize and adjust the system to improve the performance and stability of the system. The process mainly includes loading resources, loading modules, initialization and configuration, and system optimization and adjustment. During the operation of the simulation system, the system loading and initialization module 23 also needs to monitor and manage the system to ensure the normal operation of the system. The display data interface module 24 is used to provide a visual data interface for users. By visualizing the data in the DDS data stream, this module helps users more intuitively understand the status and content of the data stream, facilitating system monitoring and fault troubleshooting for users. The main functions of this module include the following aspects: data visualization display, data filtering and screening, data export and storage, and data statistics and analysis.The dynamic data interface parsing module 25 is used to parse the received data, convert the data into a format that can be processed by the application program, and pass it to the application program for further processing. The implementation method of this module generally includes the following steps: data reception, data parsing, data conversion, and data transfer. Among them, during the data parsing process, in order to ensure the correctness and security of the data, the dynamic data interface parsing module 25 needs to perform a series of data validations and security checks. The model operation management module 26 is used to manage and control the simulation model to ensure the correct operation of the simulation system. The implementation method of this module generally includes the following aspects: model loading, model operation, model data access, model performance monitoring, and model testing. The model operation performance detection module 27 is used to monitor and evaluate the operation performance of the simulation model. Its functions include the following aspects: monitoring the model operation status, evaluating the model performance, and optimizing the model performance. The built-in system testing module 28 is used to test the functions and performance of the simulation system. Its functions include the following aspects: system function testing, performance testing, and stress testing. The built-in system testing module 28 can also cooperate with other testing tools, such as JMeter, LoadRunner, etc., to perform more comprehensive testing and analysis on the simulation system.

[0057] The application model layer 3 includes a model description file 31, a model data file 32, and a code execution body 33. The model description file 31 contains the structural and attribute information of the application model layer 3. The model data file 32 contains the data information required by the application model layer 3. The code execution body 33 is the code implementation of the application model layer 3 specific to a certain platform and programming language, and is used to implement the model's operations on the data.

[0058] The distributed simulation engine layer 5 includes a service layer 51, a core layer 52, and a communication layer 53. The service layer 51 is used to provide a parallel simulation interface, enhance model reuse and interoperability in parallel simulation to meet the needs of various applications. The services provided by the service layer 51 include declaration management and object management. The service layer 51 uses the most basic function management and event management of the core layer 52 to implement, and provides a programming interface for users. On the service layer 51, communication connections are automatically established between models through publish-subscribe declarations, and messages are transmitted in the form of sending interactions. The core layer 52 integrates various functions, and the communication layer 53 is used for message transmission. The functions of the core layer 52 include logical process management, event management, time management, rollback framework, statistical management, checkpoint recovery, framework persistence, and interaction framework. Logical process management is based on various types of time sorting. The simulation engine selects and schedules logical processes (LPs) in timestamp order and processes corresponding events. Event management is based on various types of time sorting. Event management mainly includes generating, transmitting, buffering, processing, staging, and submitting events. Time management is responsible for continuously updating the local time and the global simulation time during the processing process and providing a unified interface for various time management algorithms to facilitate the addition of new time management algorithms. The rollback framework is based on management and event management. When a causality error occurs, the rollback mechanism can be used to correct it. Statistical management is used for collecting statistical information, which is beneficial to analyzing the performance of parallel event simulation. Checkpoint recovery sets checkpoints at appropriate times when the system is running normally, saves the state of the process at that time, and generates checkpoint files.

[0059] After a system failure, the relevant processes are restored to the nearest checkpoint before the failure. After the state is restored, the execution continues from this checkpoint, avoiding re-running the entire task and saving a large amount of repeated calculation time. Framework persistence refers to the persistence of simulation objects, that is, saving the objects in files, buffers, or databases, and the saved content can be used to restore the objects later. Persistence is used for checkpoint and recovery operations, load balancing, etc. in simulation. The interaction framework provides a way for users to communicate with the system, receives input from the interaction framework, and receives a list of commands. The checkpoint recovery module receives input from the interaction framework and controls the start time of checkpoints. Statistical management depends on receiving input from the interaction framework and sends information outward. The system can also display relevant information about the simulation run through the interaction framework.

[0060] Table 1 Summary of communication data of the distributed simulation system

[0061]

[0062] Table 2 Summary of communication data of the subsystem

[0063]

[0064] Table 3 QoS Settings for Different Data

[0065]

[0066]

[0067] Working Principle: In the present invention, it specifically includes the following functions:

[0068] Function of building an application system based on a system template: According to the system building template information generated by the application system integration and management component 11, download the models required for the application system to the specified physical node, and use the XML file method to decouple the application system building component 111 from the middleware and the runtime environment layer 2; The method specifically includes: building a system template using an XML file, system template generation, model download and deployment, and decoupling between the application system building component 111 and the middleware and the runtime environment layer 2. The system template generation method includes: analyzing the requirements of the application system, building a system building template, optimizing the system building template, and generating a system building report;

[0069] Function of architecture testing before application system integration: Meet the requirements in aspects such as interface compatibility, system operation efficiency, system synchronization efficiency, QoS policy, etc. during the construction process of the test application system; Interface compatibility testing refers to testing the interface compatibility between models by simulating various data situations. System synchronization efficiency testing refers to evaluating the system synchronization efficiency by conducting stress testing and performance testing on the system. QoS policy testing refers to conducting QoS policy testing by running an empty model to test whether the response time and throughput of the system meet the expectations and check whether the system meets the performance and availability requirements. System operation efficiency testing refers to evaluating the performance of the system by testing the system operation efficiency;

[0070] The system functions include data interaction detection function, multi-network and gateway function, and data interface collection and simulation data storage function; Data interaction detection function: Used to detect the self-logic time, interface data rate, data transmission delay, etc. during the operation of each model in the system; Multi-network and gateway function: Bind different domains to different network cards, and then realize the system detection data, application system demonstration data, etc.; Data interface collection and simulation data storage function: Automatically collect the input and output data interface information of each model, and display this information visually on the interface;

[0071] Model running environment functions: It can handle and solve various complex problems that may occur during the execution of the model, specifically including time management and simulation control, the encapsulation ability of the model, the ability to load and initialize external configuration parameters, the model testing ability, the performance detection function during the operation of the application model, the dynamic adjustment function of the QoS policy of the application model, the interface parsing function for converting Topic data to application model data in the running environment, the multi-network card transmission ability of the running environment, and the system-level testing ability of the running environment.

[0072] It should be noted that:

[0073] In the above text, the terms "including", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or device comprising that element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present disclosure is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0074] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on such an understanding, the technical solution of the present disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present disclosure.

[0075] The above describes the embodiments of the present disclosure in conjunction with the drawings, which are only specific embodiments of the present disclosure. However, the present disclosure is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present disclosure, those of ordinary skill in the art can also make many forms without departing from the purpose of the present disclosure and the scope protected by the claims, and all of them belong to the protection scope of the present disclosure.

Claims

1. A data-driven distributed middleware architecture, characterized in that: The distributed middleware architecture is a simulation system for realizing real-time dynamic confrontation. The simulation system is used to simulate the coordinated operation between multiple devices. The middleware architecture includes: System construction layer (1), operating environment layer (2), application model layer (3) and database system (5); The operating environment layer (2) is respectively connected to the system construction layer (1), the application model layer (3) and the database system (5) for communication, and the system construction layer (1) is connected to the database system (5) for communication; The system construction layer (1) includes at least two components, including a management system and a component; The operating environment layer (2) performs communication between components through a communication protocol; The application model layer (3) includes a plurality of simulation models, and the simulation models are used to simulate confrontation scenarios in which the plurality of devices in the simulation system participate.

2. The distributed middleware architecture according to claim 1, characterized in that: The at least two components include an application system integration and management component (11), a data management service component (12), a model management system (13) and a middleware operation management system (14); The application system integration and management component (11) is used to integrate and manage different simulation applications, wherein the simulation applications correspond to various devices simulated by the simulation system; The data management service component (12) is used to manage and maintain simulation data in the simulation system, wherein the simulation data includes model data, application system simulation data and application system test data; The model management system (13) is used to provide model management services; The middleware operation management system (14) is used for the management and control of the middleware.

3. The distributed middleware architecture according to claim 2, characterized in that: The application system integration and management component (11) includes an application system construction component (111), an application system template database (112) and a QoS test setting and testing component (113); The application system construction component (111) is used to construct different simulation application systems and integrate the different simulation application systems into a unified system; The application system template database (112) is used to store different application system templates, each application system template includes a model, data, and configuration; The QoS test setting and test component (113) is a tool for performing quality testing on the system, and is used to simulate different network environments and load conditions.

4. The distributed middleware architecture according to claim 2, characterized in that: The data management service component (12) comprises a model interface data management module (121), an application system simulation data storage module (122) and an application system test data management module (123); The model interface data management module (121) is used to manage and maintain various simulation models used in the simulation system; The application system simulation data storage module (122) is used to store and manage simulation data generated by the application system; The application system test data management module (123) is used to manage and maintain the test data generated by the application system.

5. The distributed middleware architecture according to claim 2, characterized in that: The model management system (13) includes a model building module (131), a model library (132) and a model testing environment (133); The model building module (131) is responsible for building and developing a simulation model according to the needs and requirements of the simulation system; The model library (132) is used to store all models; The model testing environment (133) is a tool for testing and verifying the model.

6. The distributed middleware architecture according to claim 2, characterized in that: The middleware operation management system (14) comprises a system real-time inspection module (141), a system operation status module (142) and a system hardware topology management module (143); The system real-time inspection module (141) is used to monitor and detect the system operation status in real time; The system operation status module (142) is used to monitor and manage the system operation status in real time; The system hardware topology structure management module (143) is used to manage and maintain the system hardware topology structure.

7. The distributed middleware architecture according to claim 1, characterized in that: The operating environment layer (2) includes a DDS multi-network card communication upgrade module (21), a simulation operation management module (22), a system loading and initialization module (23), a display data interface module (24), a dynamic data interface analysis module (25), a model operation management module (26), a model operation performance detection module (27) and a built-in system test module (28); The DDS multi-network card communication upgrade module (21) is used to configure the parameters of DDS and specify the network card for communication; The simulation operation management module (22) is used for QoS management and Topic management. The QoS management is used to select appropriate QoS strategies for configuration according to actual communication requirements and system resource conditions. The Topic management is used to design appropriate Topic structures according to data types and data publishers in the system. The system loading and initialization module (23) is used to load resources and modules required by the system, and perform at least one of initialization, configuration, optimization and adjustment on them; The display data interface module (24) is used to provide a visual data interface for the user; The dynamic data interface parsing module (25) is used to parse the received data and convert the data into a format that can be processed by the application program; The model operation management module (26) is used to manage and control the simulation model; The model operation performance detection module (27) is used to monitor and evaluate the operation performance of the simulation model; The built-in system test module (28) is used to test the function and performance of the simulation system.

8. The distributed middleware architecture according to claim 1, characterized in that: The application model layer (3) includes a model description file (31), a model data file (32) and a code execution body (33); The model description file (31) includes the structure and attribute information of the application model layer (3); The model data file (32) includes data information required by the application model layer (3); The code execution body (33) is the code of the application model layer (3) regarding the platform and programming language.

9. The distributed middleware architecture according to claim 1, characterized in that: The distributed middleware architecture also includes a distributed simulation engine layer (5); The distributed simulation engine layer (5) includes a service layer (51), a core layer (52) and a communication layer (53); The service layer (51) is used to provide a parallel simulation interface to enhance model reuse and interoperability in parallel simulation; The core layer (52) is used for simulation progress management; The communication layer (53) is used for message transmission.

10. According to the distributed middleware architecture of claim 9, the functions of the core layer (52) include logical process management, event management, time management, rollback framework, statistics management, checkpoint recovery, framework persistence and interaction framework.

Images