Distributed simulation RTI design method, device and equipment for heterogeneous network environment

Abstract

The application relates to a distributed simulation RTI design method, device and equipment for a heterogeneous network environment. The method comprises the following steps: in the distributed simulation RTI, a Protobuf client is configured for each federation member, a Protobuf server end is configured for a local RTI component storing an RTI ambassador and a federation member ambassador, and mutual conversion between RTI ambassador API interface functions, federation member ambassador API interface functions and corresponding structured message data is realized according to a Protobuf-based protocol file. The method can improve the adaptability of the distributed simulation RTI to the heterogeneous network environment, and can encapsulate the distributed simulation RTI call by using the unified binary structured message data provided by the Protobuf, so that efficient data transmission and rapid response of the distributed simulation in the heterogeneous network environment are realized.

Description

Technical Field

[0001] This application relates to the field of distributed simulation technology, and in particular to a distributed simulation RTI design method, apparatus and equipment for heterogeneous network environments. Background Technology

[0002] High-Level Architecture (HLA) is one of the core distributed simulation standards in the field of modeling and simulation. Its main goal is to achieve interconnection, interoperability, and communication between geographically distributed heterogeneous simulation systems. The HLA standard is an API (Application Programming Interface) standard that defines a series of function calls and callback interfaces that heterogeneous simulation systems, as federation members, can use to achieve interoperability within the same federation. Each simulation system parses the content of network exchange messages through a developer-defined Federation Object Model (FOM). These function calls are divided into services such as federation management, declaration management, object management, ownership management, time management, and data distribution management, which together constitute the standard service and interface framework of the HLA Runtime Infrastructure (RTI). It is worth noting that although the HLA standard describes the interface forms of these services in the "Federation Member Interface Specification," it does not specify the specific implementation form of the RTI or the specific format of messages transmitted over the network. This leads to multiple RTI implementations for the same version of the HLA standard, with differences in communication protocol support and network adaptability.

[0003] Generally, federation members access HLA services through local API interface libraries (referred to as local RTI components or LRCs) with the support of network transport protocols, and interact with the central RTI component (CRC) deployed on the RTI server. Currently, most mainstream RTI implementations are based on TCP / IP (Transmission Control / Internet Protocol), some support UDP (User Datagram Protocol) and multicast, and a few support shared or reflected memory mechanisms. In network environments restricted by firewalls, NAT (Network Address Translation), and other restrictions, different mechanisms exist, such as HTTP (Hypertext Transfer Protocol) proxy relay and HTTP message-based mechanisms. Especially with the introduction of the HLA Evolved standard, Web Services APIs were introduced to implement all HLA service functions, supporting operation via HTTP / HTTPS protocols. This means that different RTI implementations use different network protocols, and the same RTI may also be implemented in different versions to support different types of network environments. Therefore, within the same federation, each federation member is typically required to install and use the same version of the RTI library.

[0004] However, heterogeneous network environments may simultaneously contain interconnected networks of various types, such as LANs, WANs, mobile communication networks, and wireless networks; terminal devices may run different operating systems. This can lead to the need for different versions of the RTI library within the same federation. Therefore, traditional API-based distributed simulation RTI implementations are insufficient to meet the interoperability requirements of simulation systems in heterogeneous network environments within the same federation. Summary of the Invention

[0005] Therefore, it is necessary to provide a distributed simulation RTI design method, apparatus, and equipment for heterogeneous network environments to address the aforementioned technical problems.

[0006] A distributed simulation RTI design method for heterogeneous network environments, the method comprising: In the distributed simulation RTI, a Protobuf client is configured for each federation member, a Protobuf server is configured for the local RTI component that stores RTI ambassadors and federation member ambassadors, and the RTI ambassador API interface functions and federation member ambassador API interface functions are defined as Protobuf-based protocol files. The Protobuf client responds to the call request for the RTI Ambassador API interface function from the corresponding federation member, and performs serialization processing according to the protocol file to obtain the RTI Ambassador structured message data. This data is then sent to the Protobuf server in a heterogeneous network environment. The Protobuf server performs deserialization processing according to the protocol file to restore the call request for the RTI Ambassador API interface function, and submits it to the local RTI component to call the corresponding RTI Ambassador API interface function. At the same time, the call result is returned to the corresponding federation member. The Protobuf server responds to the callback request of the Federation Member Ambassador API interface function initiated by the Federation Member Ambassador in the local RTI component through the RTI component, and performs serialization processing according to the protocol file to obtain the Federation Member Ambassador structured message data, which is then sent to the Protobuf client in a heterogeneous network environment. The Protobuf client performs deserialization processing according to the protocol file to restore the callback request of the Federation Member Ambassador API interface function, and calls the callback function of the corresponding Federation Member to obtain the callback return value.

[0007] In one embodiment, the protocol files include an RTI Ambassador API interface protocol file and a Federal Member Ambassador API interface protocol file; Serialization / deserialization is performed according to the protocol file, including: Based on the target development language type corresponding to each federation member in a heterogeneous network environment, the RTI Ambassador API interface protocol file is compiled using the Protobuf compiler and serialized / deserialized to achieve mutual conversion between RTI Ambassador API interface functions and RTI Ambassador structured message data; similarly, the federation member ambassador API interface protocol file is compiled using the Protobuf compiler and serialized / deserialized to achieve mutual conversion between federation member ambassador API interface functions and federation member ambassador structured message data.

[0008] In one embodiment, the method further includes: An adaptive selection algorithm for network transmission protocols is used to maintain bidirectional communication between the Protobuf client and the Protobuf server in a heterogeneous network environment.

[0009] In one embodiment, the network transport protocol adaptive selection algorithm includes: Initialization was successful; the number of probes and total round-trip time were both 0. Perform a preset number of ICMP probes on the bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment, record the number of successful probes, and add the round-trip time of communication during successful probes to the total round-trip time. After the detection is completed, the average round-trip time is calculated based on the ratio of the total round-trip time to the number of successful detections, and the packet loss rate is calculated based on the ratio of the number of failed detections to the total number of detections. When the average round-trip time is below a preset threshold and the packet loss rate is 0, the current heterogeneous network environment is determined to be stable, and a low-latency, high-throughput network transmission protocol is selected first; otherwise, the current heterogeneous network environment is determined to be unstable, and a high-fault-tolerant, jitter-resistant network transmission protocol is selected first.

[0010] A distributed simulation RTI device for heterogeneous network environments, designed based on the above-mentioned distributed simulation RTI design method for heterogeneous network environments, includes: a protocol file, a Protobuf client configured for each federation member, and a Protobuf server configured for the local RTI component; wherein, the local RTI component stores RTI ambassadors and federation member ambassadors. The protocol file is used to define the structured message definition file used by Protobuf and to describe the message structure corresponding to the RTI Ambassador API interface function, Federation Member Ambassador API interface function, function parameter values ​​and return value data in the distributed simulation RTI. The Protobuf client is used to respond to the call requests of the corresponding federation member to the RTI Ambassador API interface function, and to perform serialization processing according to the protocol file to obtain the RTI Ambassador structured message data and send it to the Protobuf server in a heterogeneous network environment; and to receive the federation member ambassador structured message data sent by the Protobuf server, and to perform deserialization processing according to the protocol file to restore the callback request of the federation member ambassador API interface function, and to call the callback function of the corresponding federation member to obtain the callback return value. The Protobuf server is used to respond to callback requests for Federation Member Ambassador API interface functions initiated by the Federation Member Ambassador in the local RTI component, and to serialize the data according to the protocol file to obtain the Federation Member Ambassador structured message data and send it to the Protobuf client in a heterogeneous network environment; and to receive the RTI Ambassador structured message data sent by the Protobuf client, and to deserialize the data according to the protocol file to restore the RTI Ambassador API interface function call request, and submit it to the local RTI component to call the corresponding RTI Ambassador API interface function, while returning the call result to the corresponding Federation Member.

[0011] In one embodiment, the Protobuf client and Protobuf server include a data converter unit for performing serialization / deserialization processing according to a protocol file; wherein the protocol file includes an RTI Ambassador API interface protocol file and a Federal Member Ambassador API interface protocol file; In the Protobuf client, the data converter unit is used to compile the RTI Ambassador API interface protocol file and the Federation Member Ambassador API interface protocol file with the Protobuf compiler based on the target development language type corresponding to each Federation Member in the heterogeneous network environment. The serialization and deserialization processes are performed respectively to realize the conversion of RTI Ambassador API interface functions to RTI Ambassador structured message data, and to realize the conversion of Federation Member Ambassador structured message data to Federation Member Ambassador API interface functions. In the Protobuf server, the data converter unit is used to compile the ambassador API interface protocol file and the RTI ambassador API interface protocol file of each federation member in a heterogeneous network environment based on the target development language type. The Protobuf compiler is used to perform serialization and deserialization processing on the ambassador API interface function of the federation member to the structured message data of the federation member, and to perform the conversion of the structured message data of the RTI ambassador to the API interface function of the RTI ambassador.

[0012] In one embodiment, the Protobuf server includes a session manager unit for managing the creation, initiation, resumption, and termination of all sessions in a heterogeneous network environment, and maintaining session states and associated state listeners.

[0013] In one embodiment, the Protobuf server includes an adaptive session unit for maintaining a bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment using an adaptive network transport protocol selection algorithm.

[0014] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program performing the following steps: In the distributed simulation RTI, a Protobuf client is configured for each federation member, a Protobuf server is configured for the local RTI component that stores RTI ambassadors and federation member ambassadors, and the RTI ambassador API interface functions and federation member ambassador API interface functions are defined as Protobuf-based protocol files. The Protobuf client responds to the call request for the RTI Ambassador API interface function from the corresponding federation member, and performs serialization processing according to the protocol file to obtain the RTI Ambassador structured message data. This data is then sent to the Protobuf server in a heterogeneous network environment. The Protobuf server performs deserialization processing according to the protocol file to restore the call request for the RTI Ambassador API interface function, and submits it to the local RTI component to call the corresponding RTI Ambassador API interface function. At the same time, the call result is returned to the corresponding federation member. The Protobuf server responds to the callback request of the Federation Member Ambassador API interface function initiated by the Federation Member Ambassador in the local RTI component through the RTI component, and performs serialization processing according to the protocol file to obtain the Federation Member Ambassador structured message data, which is then sent to the Protobuf client in a heterogeneous network environment. The Protobuf client performs deserialization processing according to the protocol file to restore the callback request of the Federation Member Ambassador API interface function, and calls the callback function of the corresponding Federation Member to obtain the callback return value.

[0015] The aforementioned distributed simulation RTI design method, apparatus, and equipment for heterogeneous network environments, by configuring a Protobuf client for each federation member and a Protobuf server for the local RTI component, enables the isolation of the original API call method of the HLA standard based on the Protobuf client-server architecture. This reduces the impact of heterogeneous network environments on the efficiency of distributed simulation RTI service calls and callbacks, meets the interoperability requirements of simulation systems in heterogeneous network environments within the same federation, and thus improves the adaptability of distributed simulation RTI to heterogeneous network environments. Furthermore, by defining a Protobuf-based protocol file and performing serialization / deserialization processing based on the protocol file to achieve mutual conversion between RTI ambassador API interface functions, federation member ambassador API interface functions, and corresponding structured message data, distributed simulation RTI calls can be encapsulated using the unified binary structured message data provided by Protobuf, achieving efficient data transmission and rapid response in distributed simulation in heterogeneous network environments. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a distributed simulation RTI design method for heterogeneous network environments in one embodiment. Figure 2 This is a schematic diagram of a distributed simulation RTI device for heterogeneous network environments in one embodiment. Figure 3 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0018] In one embodiment, such as Figure 1 As shown, a distributed simulation RTI design method for heterogeneous network environments is provided, including the following steps: Step 1: In the distributed simulation RTI, configure a Protobuf client for each federation member, configure a Protobuf server for the local RTI component that stores RTI ambassadors and federation member ambassadors, and define the RTI ambassador API interface functions and federation member ambassador API interface functions as Protobuf-based protocol files.

[0019] Among them, Protobuf is a data exchange format that has compact and efficient binary representation capabilities. It is characterized by small size and fast transmission, which can significantly improve the processing speed of serialization and deserialization, and better meet the high-frequency and low-latency simulation communication requirements of heterogeneous cloud simulation.

[0020] The RTI Ambassador is the interface used by federated members to invoke RTI services, representing the federated member's request to RTI. The Federated Member Ambassador is the interface used by RTI to call back to federated members, representing the RTI's notification to federated members.

[0021] Step 2: The Protobuf client responds to the call request for the RTI Ambassador API interface function from the corresponding federation member, and performs serialization processing according to the protocol file to obtain the RTI Ambassador structured message data. This data is then sent to the Protobuf server in a heterogeneous network environment. The Protobuf server performs deserialization processing according to the protocol file to restore the call request for the RTI Ambassador API interface function, and submits it to the local RTI component to call the corresponding RTI Ambassador API interface function. At the same time, the call result is returned to the corresponding federation member.

[0022] Step 3: The Protobuf server responds to the callback request of the Federation Member Ambassador API interface function initiated by the Federation Member Ambassador in the local RTI component through the RTI component, and performs serialization processing according to the protocol file to obtain the Federation Member Ambassador structured message data. This data is then sent to the Protobuf client in a heterogeneous network environment. The Protobuf client performs deserialization processing according to the protocol file to restore the callback request of the Federation Member Ambassador API interface function, and calls the callback function of the corresponding Federation Member to obtain the callback return value.

[0023] In the aforementioned distributed simulation RTI design method for heterogeneous network environments, by configuring a Protobuf client for each federation member and a Protobuf server for the local RTI component, the original API call method of the HLA standard can be isolated based on the Protobuf client-server architecture. This reduces the impact of heterogeneous network environments on the efficiency of distributed simulation RTI service calls and callbacks, meets the interoperability requirements of simulation systems in heterogeneous network environments within the same federation, and thus improves the adaptability of distributed simulation RTI to heterogeneous network environments. Furthermore, by defining a Protobuf-based protocol file and performing serialization / deserialization processing based on the protocol file to achieve mutual conversion between RTI ambassador API interface functions, federation member ambassador API interface functions, and corresponding structured message data, distributed simulation RTI calls can be encapsulated using the unified binary structured message data provided by Protobuf, enabling efficient data transmission and rapid response in distributed simulation in heterogeneous network environments.

[0024] In one embodiment, the protocol files include an RTI Ambassador API interface protocol file and a Federal Member Ambassador API interface protocol file. Serialization / deserialization processing based on the protocol files includes: Based on the target development language type corresponding to each federation member in a heterogeneous network environment, the RTI Ambassador API interface protocol file is compiled using the Protobuf compiler and serialized / deserialized to achieve mutual conversion between RTI Ambassador API interface functions and RTI Ambassador structured message data; similarly, the federation member ambassador API interface protocol file is compiled using the Protobuf compiler and serialized / deserialized to achieve mutual conversion between federation member ambassador API interface functions and federation member ambassador structured message data.

[0025] In one embodiment, the method further includes: maintaining a bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment using a network transport protocol adaptive selection algorithm. The network transport protocol adaptive selection algorithm includes: (1) Initialize the number of successful probes and the total round-trip time to 0.

[0026] (2) Perform ICMP (Internet Control Message Protocol) probes a preset number of times (e.g., 10 times) on the bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment, record the number of successful probes, and add the communication round-trip delay of successful probes to the total round-trip delay.

[0027] (3) After the detection is completed, the average round-trip time is calculated based on the ratio of the total round-trip time to the number of successful detections, and the packet loss rate is calculated based on the ratio of the number of failed detections to the total number of detections. Specifically, the average round-trip time... ,in, For the number of successful probes, Total round-trip time; packet loss rate .

[0028] (4) When the average round-trip time is lower than the preset threshold (e.g., 10ms) and the packet loss rate is 0, the current heterogeneous network environment is determined to be stable, and a low-latency, high-throughput network transmission protocol, such as a local area network optimization protocol, is preferred; otherwise, the current heterogeneous network environment is determined to be unstable, and a high-fault-tolerant, jitter-resistant network transmission protocol, such as a wide area network compatible protocol, is preferred.

[0029] This algorithm enables Protobuf clients and servers to establish persistent, bidirectional communication connections in heterogeneous network environments. It automatically switches network transmission protocols when the heterogeneous network environment changes, thus meeting the dynamic requirements of distributed simulation data processing and transmission efficiency. Furthermore, the algorithm can also adaptively select network transmission protocols based on throughput.

[0030] In one embodiment, such as Figure 2 As shown, a distributed simulation RTI device for heterogeneous network environments is provided. The device is designed based on the above-mentioned distributed simulation RTI design method for heterogeneous network environments and includes a protocol file, a Protobuf client configured for each federation member, and a Protobuf server configured for the local RTI component; wherein, the local RTI component stores RTI ambassadors and federation member ambassadors.

[0031] The protocol file is used to define the structured message definition file used by Protobuf and to describe the message structure corresponding to the RTI Ambassador API interface function, Federation Member Ambassador API interface function, function parameter values, and return value data in the distributed simulation RTI.

[0032] The Protobuf client is used to respond to the call requests of the corresponding federation member to the RTI Ambassador API interface function, and to perform serialization processing according to the protocol file to obtain the RTI Ambassador structured message data and send it to the Protobuf server in a heterogeneous network environment; and to receive the federation member ambassador structured message data sent by the Protobuf server, and to perform deserialization processing according to the protocol file to restore the callback request of the federation member ambassador API interface function, and to call the callback function of the corresponding federation member to obtain the callback return value.

[0033] The Protobuf server is used to respond to callback requests for Federation Member Ambassador API interface functions initiated by the Federation Member Ambassador in the local RTI component, and to serialize the data according to the protocol file to obtain the Federation Member Ambassador structured message data and send it to the Protobuf client in a heterogeneous network environment; and to receive the RTI Ambassador structured message data sent by the Protobuf client, and to deserialize the data according to the protocol file to restore the RTI Ambassador API interface function call request, and submit it to the local RTI component to call the corresponding RTI Ambassador API interface function, while returning the call result to the corresponding Federation Member.

[0034] In one embodiment, the Protobuf client and Protobuf server include a data converter unit for serialization / deserialization processing according to a protocol file; wherein the protocol file includes an RTI Ambassador API interface protocol file and a Federal Member Ambassador API interface protocol file.

[0035] In the Protobuf client, the data converter unit, based on the target development language type corresponding to each federation member in the heterogeneous network environment, compiles the RTI Ambassador API interface protocol file and the federation member ambassador API interface protocol file using the Protobuf compiler, and performs serialization and deserialization processing respectively to convert RTI Ambassador API interface functions to RTI Ambassador structured message data, and also to convert federation member ambassador structured message data to federation member ambassador API interface functions. In the Protobuf server, the data converter unit, based on the target development language type corresponding to each federation member in the heterogeneous network environment, compiles the federation member ambassador API interface protocol file and the RTI Ambassador API interface protocol file using the Protobuf compiler, and performs serialization and deserialization processing respectively to convert federation member ambassador API interface functions to federation member ambassador structured message data, and also to convert RTI Ambassador structured message data to RTI Ambassador API interface functions.

[0036] In one embodiment, the Protobuf server includes a session manager unit for managing operations such as the creation, initiation, resumption, and termination of all sessions in a heterogeneous network environment, and maintaining session states and related state listeners.

[0037] In one embodiment, the Protobuf server includes an adaptive session unit for maintaining a bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment using an adaptive network transport protocol selection algorithm.

[0038] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 3 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a distributed simulation RTI design method for heterogeneous network environments. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0039] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0040] In one embodiment, a computer device is provided, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to perform the following steps: In the distributed simulation RTI, a Protobuf client is configured for each federation member, a Protobuf server is configured for the local RTI component that stores RTI ambassadors and federation member ambassadors, and the RTI ambassador API interface functions and federation member ambassador API interface functions are defined as Protobuf-based protocol files. The Protobuf client responds to the call request for the RTI Ambassador API interface function from the corresponding federation member, and performs serialization processing according to the protocol file to obtain the RTI Ambassador structured message data. This data is then sent to the Protobuf server in a heterogeneous network environment. The Protobuf server performs deserialization processing according to the protocol file to restore the call request for the RTI Ambassador API interface function, and submits it to the local RTI component to call the corresponding RTI Ambassador API interface function. At the same time, the call result is returned to the corresponding federation member. The Protobuf server responds to the callback request of the Federation Member Ambassador API interface function initiated by the Federation Member Ambassador in the local RTI component through the RTI component, and performs serialization processing according to the protocol file to obtain the Federation Member Ambassador structured message data, which is then sent to the Protobuf client in a heterogeneous network environment. The Protobuf client performs deserialization processing according to the protocol file to restore the callback request of the Federation Member Ambassador API interface function, and calls the callback function of the corresponding Federation Member to obtain the callback return value.

[0041] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0042] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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, they should be considered to be within the scope of this specification.

[0043] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application.

Claims

1. A distributed simulation RTI design method for heterogeneous network environments, characterized in that, The method includes: In the distributed simulation RTI, a Protobuf client is configured for each federation member, a Protobuf server is configured for the local RTI component that stores RTI ambassadors and federation member ambassadors, and the RTI ambassador API interface functions and federation member ambassador API interface functions are defined as Protobuf-based protocol files. The Protobuf client responds to the call request for the RTI Ambassador API interface function from the corresponding federation member, and performs serialization processing according to the protocol file to obtain RTI Ambassador structured message data, which is then sent to the Protobuf server in a heterogeneous network environment. The Protobuf server performs deserialization processing according to the protocol file to restore the call request for the RTI Ambassador API interface function, and submits it to the local RTI component to call the corresponding RTI Ambassador API interface function, while returning the call result to the corresponding federation member. The Protobuf server responds to the callback request of the Federal Member Ambassador API interface function initiated by the Federal Member Ambassador in the local RTI component through the RTI component, and performs serialization processing according to the protocol file to obtain the Federal Member Ambassador structured message data, which is then sent to the Protobuf client in a heterogeneous network environment. The Protobuf client performs deserialization processing according to the protocol file to restore the callback request of the Federal Member Ambassador API interface function, and calls the callback function of the corresponding Federal Member to obtain the callback return value.

2. The distributed simulation RTI design method for heterogeneous network environments according to claim 1, characterized in that, The protocol documents include the RTI Ambassador API interface protocol document and the Federal Member Ambassador API interface protocol document; Serialization / deserialization processing is performed according to the protocol file, including: Based on the target development language type corresponding to each federation member in a heterogeneous network environment, the RTI Ambassador API interface protocol file is compiled using the Protobuf compiler for serialization / deserialization processing, realizing the mutual conversion between RTI Ambassador API interface functions and RTI Ambassador structured message data; and the federation member ambassador API interface protocol file is compiled using the Protobuf compiler for serialization / deserialization processing, realizing the mutual conversion between federation member ambassador API interface functions and federation member ambassador structured message data.

3. The distributed simulation RTI design method for heterogeneous network environments according to claim 1, characterized in that, The method further includes: An adaptive network transmission protocol selection algorithm is used to maintain the bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment.

4. The distributed simulation RTI design method for heterogeneous network environments according to claim 3, characterized in that, The network transmission protocol adaptive selection algorithm includes: Initialization was successful; the number of probes and total round-trip time were both 0. Perform a preset number of ICMP probes on the bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment, record the number of successful probes, and add the round-trip time of communication during successful probes to the total round-trip time. After the detection is completed, the average round-trip time is calculated based on the ratio of the total round-trip time to the number of successful detections, and the packet loss rate is calculated based on the ratio of the number of failed detections to the total number of detections. When the average round-trip time is lower than a preset threshold and the packet loss rate is 0, the current heterogeneous network environment is determined to be stable, and a low-latency, high-throughput network transmission protocol is selected first; otherwise, the current heterogeneous network environment is determined to be unstable, and a high-fault-tolerant, jitter-resistant network transmission protocol is selected first.

5. A distributed simulation RTI device for heterogeneous network environments designed based on the method described in any one of claims 1 to 4, characterized in that, The device includes: a protocol file, a Protobuf client configured for each federation member, and a Protobuf server configured for a local RTI component; wherein the local RTI component stores RTI ambassadors and federation member ambassadors; The protocol file is used to define the structured message definition file used by Protobuf and to describe the message structure corresponding to the RTI Ambassador API interface function, Federation Member Ambassador API interface function, function parameter values ​​and return value data in the distributed simulation RTI. The Protobuf client is used to respond to the call request of the corresponding federation member to the RTI ambassador API interface function, and to perform serialization processing according to the protocol file to obtain RTI ambassador structured message data and send it to the Protobuf server in a heterogeneous network environment; and to receive the federation member ambassador structured message data sent by the Protobuf server, and to perform deserialization processing according to the protocol file to restore the callback request of the federation member ambassador API interface function, and to call the callback function of the corresponding federation member to obtain the callback return value. The Protobuf server is used to respond to callback requests for the Federation Member Ambassador API interface functions initiated by the Federation Member Ambassador in the local RTI component, and to perform serialization processing according to the protocol file to obtain the Federation Member Ambassador structured message data and send it to the Protobuf client in a heterogeneous network environment; and to receive the RTI Ambassador structured message data sent by the Protobuf client, and to perform deserialization processing according to the protocol file to restore the RTI Ambassador API interface function call request, and submit it to the local RTI component to call the corresponding RTI Ambassador API interface function, while returning the call result to the corresponding Federation Member.

6. The distributed simulation RTI device for heterogeneous network environments according to claim 5, characterized in that, The Protobuf client and Protobuf server include a data converter unit for performing serialization / deserialization processing according to the protocol file; wherein, the protocol file includes the RTI Ambassador API interface protocol file and the Federal Member Ambassador API interface protocol file; In the Protobuf client, the data converter unit is used to compile the RTI Ambassador API interface protocol file and the Federation Member Ambassador API interface protocol file through the Protobuf compiler based on the target development language type corresponding to each Federation Member in the heterogeneous network environment, and perform serialization and deserialization processing respectively, so as to realize the conversion of RTI Ambassador API interface functions to RTI Ambassador structured message data, and realize the conversion of Federation Member Ambassador structured message data to Federation Member Ambassador API interface functions; In the Protobuf server, the data converter unit is used to compile the ambassador API interface protocol file and the RTI ambassador API interface protocol file of the federation member according to the target development language type of each federation member in the heterogeneous network environment, and perform serialization and deserialization processing respectively through the Protobuf compiler, so as to realize the conversion of the ambassador API interface function of the federation member to the structured message data of the federation member, and the conversion of the structured message data of the RTI ambassador to the API interface function of the RTI ambassador.

7. The distributed simulation RTI device for heterogeneous network environments according to claim 6, characterized in that, The Protobuf server includes a session manager unit, which manages the creation, startup, recovery, and termination of all sessions in a heterogeneous network environment, and maintains session states and related state listeners.

8. The distributed simulation RTI device for heterogeneous network environments according to claim 7, characterized in that, The Protobuf server includes an adaptive session unit, which uses an adaptive selection algorithm for network transmission protocols to maintain a bidirectional communication connection between the Protobuf client and the Protobuf server in a heterogeneous network environment.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

Images