Simulation cascade device, method, equipment and medium based on global agent

Abstract

The present application relates to a simulation cascade device, method, equipment and medium based on a global agent. The device is applied to a distributed simulation system cluster, including a client and several simulation clusters. Each simulation cluster performs cascade access and synchronous message reception and transmission between simulation clusters based on an internally deployed global agent. The global agent is divided into an entry agent and an exit agent according to the message reception and transmission type; the entry agent is used to receive messages sent by the exit agent of other external simulation clusters, and synchronously forward them to the client as the message consumer for message consumption; the exit agent is used to receive messages produced and sent by the client as the message producer for storage, and synchronously forward them to the entry agent of other external simulation clusters for message distribution. This device can ensure data consistency between regions of distributed simulation system clusters, and ensure that the distributed simulation system cluster can still operate efficiently and stably in complex scenarios.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a simulation cascade device, method, equipment and medium based on a global agent. Background Art

[0002] In the distributed simulation system cluster mode, the simulation process is usually accompanied by dynamic changes, which requires building connection paths between simulation clusters to ensure that messages can be smoothly transmitted and processed between clusters. In actual applications, there are business needs for cross-regional message transmission and consumption. For example, business system A is deployed in the south as a message producer, and business system B is deployed in the north as a message consumer. When A generates a message, it needs to send the message to B for processing and consumption in a cross-regional manner.

[0003] The existing method is to synchronize all messages to other servers through the server synchronization strategy to publish and subscribe messages between simulation clusters. However, the server synchronization strategy has some significant disadvantages. First, there is often a large delay in the message synchronization process, which makes it impossible to respond to dynamic changes in the simulation process in a timely manner. Secondly, the server synchronization strategy lacks sufficient flexibility in the process of message transmission and is difficult to adapt to complex and changing simulation scenarios. In addition, this method also consumes a lot of network bandwidth resources, thereby reducing the overall operating efficiency. With the advancement of science and technology and the continuous development of business needs, the existing server synchronization strategy is increasingly difficult to meet the high performance, flexibility and other requirements of simulation clusters. To this end, a new solution is urgently needed to effectively solve the above problems to ensure that the distributed simulation system cluster can still operate efficiently and stably in complex scenarios. Summary of the invention

[0004] Based on this, it is necessary to provide a simulation cascade device, method, equipment and medium based on a global agent to address the above technical problems.

[0005] A simulation cascade device based on a global agent, which is applied to a distributed simulation system cluster, including a client and several simulation clusters, wherein each simulation cluster performs cascade access and synchronous message reception and transmission between simulation clusters based on an internally deployed global agent, and the global agent is divided into an ingress agent and an egress agent according to the message reception and transmission type;

[0006] As a message producer, the client is used to connect to the egress proxy of any simulation cluster to produce and send messages, and as a message consumer, it is used to connect to the ingress proxy of any simulation cluster to receive and consume messages;

[0007] The ingress proxy deployed inside each simulation cluster serves as an external message synchronization transfer station, which is used to receive messages sent by the egress proxy of other external simulation clusters and synchronously forward them to the client for message consumption;

[0008] The export agent deployed inside each simulation cluster serves as an internal message synchronization transit station, which is used to receive messages sent by the client for storage and synchronously forward them to the import agents of other external simulation clusters for message distribution.

[0009] Furthermore, the global agent deployed inside each simulation cluster performs synchronous message sending and receiving based on two threads;

[0010] The first thread of the global proxy is used to periodically write data into the hash table and store it persistently when the consumer of the client registers; the data written into the hash table includes the subject, consumer and subject type of the message;

[0011] The second thread of the global proxy classifies message topics and pulls and stores messages according to the consumer initialization cycle and the message pulling cycle.

[0012] The consumer initialization loop process includes: first traversing the topics of all messages in the hash table to obtain a topic list; then performing consumer initialization on any topic in the topic list according to the buff mode and obtaining a buff message. If the buff message is successfully obtained, it means that the topic is a buff topic, and the consumer and topic type corresponding to the topic are stored in the hash table; otherwise, destroying the consumer corresponding to the topic, and re-initializing the consumer for the topic according to the file mode and obtaining a file message. If the file message is successfully obtained, it means that the topic is a file topic, and the consumer and topic type corresponding to the topic are stored in the hash table; if both the buff message and the file message fail to be obtained, it means that the type of the topic is unknown, and this cycle does not process the topic, and continues to perform consumer initialization on the next topic in the topic list;

[0013] The message pulling loop process includes: according to the topic type saved in the hash table, different consumer function interfaces are called to obtain messages, and the offset value of the message in the hash table is updated; when the topic is of buff type, the buff message consumer function interface is called to pull the buff message, and the pulled buff message is stored in the commitlog; when the topic is of file type, the file message is first pulled locally, and then stored in the local temporary file path according to the file name and file attribute information. After the file message is pulled, it is stored in the local file path, and the file message consumer function interface is called to store the file attribute information in the commitlog.

[0014] Furthermore, during the simulation process, the global agent deployed inside each simulation cluster starts a plurality of second threads according to the number of simulation clusters in the device, and each simulation cluster corresponds to one second thread.

[0015] Furthermore, the client as the message producer sends the message to the message queue of the egress agent of the simulation cluster connected to it, and the ingress agents of other simulation clusters obtain the message from the message queue of the egress agent of the simulation cluster and cache it in the local message queue;

[0016] The client, as a message consumer, pulls messages from the message queue of the entry agent of the simulation cluster connected to it to the local computer, and performs message parsing and business processing.

[0017] Furthermore, a backup ingress proxy and a backup egress proxy are deployed inside each simulation cluster to automatically switch to the backup when a global proxy fails, ensuring that messages between simulation clusters are continuously and synchronously sent and received.

[0018] Furthermore, during the simulation process, each simulation cluster routes and filters messages by using wildcards.

[0019] A simulation cascade method based on a global agent, the method is implemented based on the above-mentioned simulation cascade device based on a global agent, and comprises the following steps:

[0020] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0021] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0022] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0023] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0024] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0025] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0026] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0027] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0028] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0029] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0030] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0031] The above-mentioned simulation cascade device, method, equipment and medium based on the global agent, in order to realize the synchronous sending, receiving and subscription of messages in the distributed simulation system cluster, deploys a global agent inside each simulation cluster to perform cascade access and synchronous sending and receiving of messages between simulation clusters. At the same time, in order to avoid repeated consumption of messages, on the basis of the global agent, it is further divided into entry agent and exit agent according to the message sending and receiving type. The entry agent is used to realize the synchronous transfer and consumption of messages from other external simulation clusters, and the exit agent is used to realize the synchronous transfer and outbound sending of messages within the simulation cluster, thereby realizing message intercommunication between simulation clusters in multiple different regions. When processing a large amount of real-time message data during the simulation process, the messages can be accurately synchronized from the source simulation cluster to the target simulation cluster. All simulation clusters have the same understanding and use of shared message data, and efficiently realize the synchronous replication of messages between simulation clusters in different regions, thereby improving the flexibility of the message sending and receiving transmission process and the efficiency of simulation operation, saving network bandwidth resources, ensuring the data consistency between regions of the distributed simulation system cluster, and ensuring that the distributed simulation system cluster can still operate efficiently and stably in complex scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a structural schematic diagram of a simulation cascade device based on a global agent in one embodiment;

[0033] Figure 2 It is a schematic diagram of the process of globally proxying two threads in one embodiment;

[0034] Figure 3 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0036] In one embodiment, Figure 1 As shown, a simulation cascade device based on a global agent is provided, which is applied to a distributed simulation system cluster, including a client and several simulation clusters, wherein each simulation cluster performs cascade access and synchronous message reception and transmission between simulation clusters based on an internally deployed global agent, and the global agent is divided into an ingress agent and an egress agent according to the message reception and transmission type;

[0037] As a message producer, the client is used to connect to the egress proxy of any simulation cluster to produce and send messages, and as a message consumer, it is used to connect to the ingress proxy of any simulation cluster to receive and consume messages;

[0038] The ingress proxy deployed inside each simulation cluster serves as an external message synchronization transfer station, which is used to receive messages sent by the egress proxy of other external simulation clusters and synchronously forward them to the client for message consumption;

[0039] The export agent deployed inside each simulation cluster serves as an internal message synchronization transit station, which is used to receive messages sent by the client for storage and synchronously forward them to the import agents of other external simulation clusters for message distribution.

[0040] Furthermore, if Figure 2 As shown, the global agent deployed inside each simulation cluster sends and receives messages synchronously based on two threads.

[0041] The first thread of the global proxy (also called the persistence thread) is used to periodically write data into the hash table and store it persistently when the client's consumer registers. The data written into the hash table includes the subject, consumer, and subject type of the message. Specifically, the persistent storage is in a disk file.

[0042] The second thread of the global agent performs message topic classification and message pulling and storage according to the consumer initialization cycle process and the message pulling cycle process respectively.

[0043] The consumer initialization cycle process includes:

[0044] (1) First, traverse the topics of all messages in the hash table and obtain the topic list.

[0045] (2) Since the topic type is unknown, first initialize the consumer of any topic in the topic list according to the buff mode and obtain the buff message. If the buff message is obtained successfully, it means that the topic is a buff topic, and the consumer and topic type corresponding to the topic are stored in the hash table; otherwise, destroy the consumer corresponding to the topic, and re-initialize the consumer of the topic according to the file mode and obtain the file message. If the file message is obtained successfully, it means that the topic is a file topic, and the consumer and topic type corresponding to the topic are stored in the hash table; if both the buff message and the file message fail to be obtained, it means that the type of the topic is unknown. This cycle does not process the topic and continues to initialize the consumer for the next topic in the topic list.

[0046] (3) The consumer initialization loop ends and enters the message pulling loop.

[0047] The message pulling cycle process includes:

[0048] (4) Determine the subject type in the hash table.

[0049] (5) When the topic is of buff type, call the buff message consumer function interface to pull the buff message, and store the pulled buff message in commitlog. Commitlog is a message storage file.

[0050] (6) When the topic is of file type, the file message is first pulled locally, and then stored in the local temporary file path according to the file name and file attribute information. After the file message is pulled, it is stored in the local file path, and the file message consumer function interface is called to store the file attribute information in the commitlog.

[0051] (7) Finally, update the offset value of the message in the hash table stored by the first thread. The offset is the unique identifier of each message, which is used to locate and record the location and consumption record of the message.

[0052] Furthermore, during the simulation process, the global agent deployed inside each simulation cluster starts a plurality of second threads according to the number of simulation clusters in the device, and each simulation cluster corresponds to one second thread.

[0053] Furthermore, the client, as the message producer, sends the message to the message queue of the export agent of the simulation cluster connected to it. The import agents of other simulation clusters obtain the message from the message queue of the export agent of the simulation cluster and cache it in the local message queue. The client, as the message consumer, pulls the message from the message queue of the import agent of the simulation cluster connected to it to the local, and performs message parsing and business processing.

[0054] This method of replicating messages between multiple message queues ensures high availability and persistence of messages, and helps with redundant storage of data. Even if a simulation cluster fails, messages will not be lost and can be recovered from other nodes.

[0055] Furthermore, if Figure 1 As shown in the figure, each simulation cluster is also deployed with a backup inlet proxy and a backup outlet proxy, which are used to automatically switch to the backup when the global proxy fails, ensuring that messages between simulation clusters are continuously sent and received synchronously. This can avoid interruptions in message processing and reduce the impact of single point failures. In addition, in the structure of multiple simulation clusters cascaded, message requests can be dispersed to multiple simulation clusters to avoid overloading a single simulation cluster. At the same time, it also provides the ability of failover. When a simulation cluster fails, its tasks can be reallocated to other healthy simulation clusters.

[0056] Furthermore, during the simulation process, each simulation cluster routes and filters messages by using wildcards. Wildcards provide flexible message routing capabilities, allowing message producers to send messages with specific keywords, and message consumers can subscribe to matching topics according to their needs. Specifically, the keywords bound in the topic pattern of the message are composed of zero or more tags, and each tag is separated by a "." character. The binding keyword supports wildcards: "*" matches a phrase, and "#" matches zero or more phrases. When using the topic pattern, if the match is successful, the message will be sent to the corresponding queue. If * or # is not used in the topic keyword, an exact match is performed.

[0057] Ensuring that messages are sent to relevant processing program queues improves the efficiency of simulation operation, reduces the consumption of bandwidth resources, and improves the quality of simulation services.

[0058] In one embodiment, a simulation cascade method based on a global agent is provided. The method is implemented based on the above-mentioned simulation cascade device based on a global agent, and includes the following steps:

[0059] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0060] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0061] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0062] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 3 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a simulation cascade method based on a global agent is implemented.

[0063] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0064] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0065] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0066] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0067] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0068] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0069] A global proxy is deployed inside each simulation cluster to perform cascade access and synchronous message transmission and reception with other simulation clusters, and the global proxy is divided into ingress proxy and egress proxy according to the message transmission and reception type.

[0070] The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption.

[0071] The export agent deployed inside each simulation cluster is used as an internal message synchronization transit station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

[0072] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may 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 many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0073] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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.

[0074] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A simulation cascade device based on a global agent, applied to a distributed simulation system cluster, characterized in that: The device includes a client and several simulation clusters, wherein each simulation cluster performs cascade access and synchronous message reception and transmission between simulation clusters based on an internally deployed global proxy, and the global proxy is divided into an ingress proxy and an egress proxy according to the message reception and transmission type; The client acts as a message producer, connected to an egress proxy of any simulation cluster to produce and send messages, and acts as a message consumer, connected to an ingress proxy of any simulation cluster to receive and consume messages; The ingress proxy deployed inside each simulation cluster serves as an external message synchronization transfer station, which is used to receive messages sent by the egress proxy of other external simulation clusters and synchronously forward them to the client for message consumption; The export agent deployed inside each simulation cluster serves as an internal message synchronization transit station, which is used to receive messages sent by the client for storage and synchronously forward them to the import agents of other external simulation clusters for message distribution.

2. The global proxy-based simulation cascade device according to claim 1, characterized in that: The global agent deployed inside each simulation cluster sends and receives messages synchronously based on two threads; The first thread of the global proxy is used to periodically write data into the hash table and store it persistently when the consumer of the client registers; the data written into the hash table includes the subject, consumer and subject type of the message; The second thread of the global proxy classifies message topics and pulls and stores messages according to the consumer initialization cycle and the message pulling cycle. The consumer initialization loop process includes: first traversing the topics of all messages in the hash table to obtain a topic list; then performing consumer initialization on any topic in the topic list according to the buff mode and obtaining a buff message. If the buff message is successfully obtained, it means that the topic is a buff topic, and the consumer and topic type corresponding to the topic are stored in the hash table; otherwise, destroying the consumer corresponding to the topic, and re-initializing the consumer for the topic according to the file mode and obtaining a file message. If the file message is successfully obtained, it means that the topic is a file topic, and the consumer and topic type corresponding to the topic are stored in the hash table; if both the buff message and the file message fail to be obtained, it means that the type of the topic is unknown, and this cycle does not process the topic, and continues to perform consumer initialization on the next topic in the topic list; The message pulling loop process includes: according to the topic type stored in the hash table, calling different consumer function interfaces to obtain messages, and updating the offset value of the message in the hash table; when the topic is of buff type, calling the buff message consumer function interface to pull the buff message, and storing the pulled buff message in commitlog; when the topic is of file type, first pull the file message to the local, and then store it in the local temporary file path according to the file name and file attribute information. After the file message is pulled, store it in the local file path, and call the file message consumer function interface to store the file attribute information in commitlog.

3. The global proxy-based simulation cascade device according to claim 2, characterized in that: During the simulation process, the global agent deployed inside each simulation cluster starts multiple second threads according to the number of simulation clusters in the device, and each simulation cluster corresponds to one second thread.

4. The global proxy-based simulation cascade device according to claim 1, characterized in that: The client, as the message producer, sends the message to the message queue of the egress agent of the simulation cluster connected to it. The ingress agents of other simulation clusters obtain the message from the message queue of the egress agent of the simulation cluster and cache it in the local message queue. The client, as a message consumer, pulls messages from the message queue of the entry agent of the simulation cluster connected to it to the local computer, and performs message parsing and business processing.

5. The global proxy-based simulation cascade device according to claim 1, characterized in that: Each simulation cluster is also deployed with a backup ingress proxy and a backup egress proxy to automatically switch to the backup when the global proxy fails, ensuring that messages between simulation clusters are continuously sent and received synchronously.

6. The global proxy-based simulation cascade device according to claim 1, characterized in that: During the simulation, each simulation cluster routes and filters messages by using wildcards.

7. A simulation cascade method based on global agent, characterized in that: The method is implemented based on the global agent-based simulation cascade device according to any one of claims 1 to 6, and comprises the following steps: A global proxy is deployed inside each simulation cluster, and cascade access and synchronous message reception and transmission are performed with other simulation clusters through the global proxy, and the global proxy is divided into an ingress proxy and an egress proxy according to the message reception and transmission type; The ingress proxy deployed inside each simulation cluster is used as an external message synchronization transfer station. The ingress proxy receives messages sent by the egress proxy of other external simulation clusters and synchronously forwards them to the client as the message consumer for message consumption. The export agent deployed inside each simulation cluster is used as an internal message synchronization transfer station. The export agent receives messages sent by the client as the message producer, stores them, and synchronously forwards them to the entry agents of other external simulation clusters for message distribution.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to claim 7 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to claim 7 are implemented.

Images