Intelligent combat simulation platform and data processing method of intelligent combat simulation platform

Abstract

The present application relates to an intelligent combat simulation platform and a data processing method for the intelligent combat simulation platform. The intelligent combat simulation platform includes an algorithm provider, an intelligent combat simulation entity and a general blackboard system. The intelligent combat simulation platform separates the parameter calculation process of the intelligent combat algorithm from the application process, and separates the algorithm calculation from the data storage process. The algorithm provider calculates the parameters of the intelligent combat algorithm and publishes them to the intelligent combat simulation entity that subscribes to the algorithm. The intelligent combat simulation entity reads the entity status of other coordinated combat entities from the general blackboard system, calculates the current entity status according to the coordinated entity status and the intelligent combat algorithm parameters, and writes the current entity status into the general blackboard system, thereby reducing the calculation and communication volume of the entity status during intelligent combat and improving the simulation efficiency.

Description

Technical Field

[0001] The present application relates to the field of simulation technology, and in particular to an intelligent combat simulation platform and a data processing method for the intelligent combat simulation platform. Background Art

[0002] After experiencing the transformation from "quantity to quality", combat equipment has returned to the track of "quality to quantity". The traditional combat simulation method is based on the equipment platform and adopts the entity modeling method. The simulation platform that supports traditional combat simulation is built on the entity basis.

[0003] With the advent of the era of intelligent warfare, intelligent combat equipment has become an important part of intelligent warfare. Intelligent combat equipment is mainly composed of fragmented, numerous, single-function, heterogeneous group intelligent combat units. If traditional combat simulation platforms are used for combat simulation, a large number of entities need to be calculated and data interacted in the simulation platform, which requires large amounts of calculation and communication and takes a long time. Summary of the invention

[0004] Based on this, it is necessary to provide an intelligent combat simulation platform and a data processing method for the intelligent combat simulation platform, which can reduce the calculation and communication volume of intelligent combat simulation and improve the simulation efficiency, in response to the above technical problems.

[0005] In a first aspect, the present application provides an intelligent combat simulation platform, including an algorithm provider, an intelligent combat simulation entity, and a general blackboard system;

[0006] The algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity;

[0007] The intelligent combat simulation entity sends a subscription request to the algorithm provider. The subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity. The subscription identifier is an identifier corresponding to the target intelligent combat algorithm. The target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity.

[0008] The algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription identifier and the entity identifier to the general blackboard system;

[0009] The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier, and sends the collaborative entity status query request to the general blackboard system;

[0010] The general blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity;

[0011] The intelligent combat simulation entity calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state; sends a write request carrying the current entity state to the general blackboard system; the general blackboard system responds to the write request and writes the current entity state.

[0012] In one of the embodiments, the algorithm provider sends the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity; the intelligent combat simulation entity configures the intelligent combat algorithm interface according to the intelligent combat algorithm configuration parameters, obtains the configured intelligent combat algorithm, calls the configured intelligent combat algorithm, and calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state.

[0013] In one of the embodiments, the algorithm provider sends a historical data query request to the general blackboard system. The general blackboard system responds to the historical data query request and feeds back a historical combat status data set of the intelligent combat simulation entity to the algorithm provider. The algorithm provider trains the intelligent combat algorithm corresponding to the intelligent combat algorithm service based on the historical combat status data set to obtain the intelligent combat algorithm parameters.

[0014] In one of the embodiments, the algorithm provider obtains the current entity state from the general blackboard system; updates the intelligent combat algorithm parameters according to the current entity state to obtain the intelligent combat algorithm update parameters; and distributes the intelligent combat algorithm update parameters to the intelligent combat simulation entities that have subscribed to the intelligent combat algorithm.

[0015] In one of the embodiments, the algorithm provider is also used to calculate the entity state of the intelligent combat simulation entity based on the intelligent combat algorithm parameters to obtain the simulation entity state; based on the error between the simulation entity state and the current entity state, the intelligent combat algorithm parameters are updated to obtain the intelligent combat algorithm update parameters.

[0016] In one of the embodiments, the intelligent combat simulation entity is also used to obtain input combat requirement parameters and generate a subscription request based on the combat requirement parameters.

[0017] In one of the embodiments, the algorithm provider provides at least one intelligent combat algorithm built based on an algorithm tree.

[0018] In a second aspect, the present application provides a data processing method for an intelligent combat simulation platform, the method comprising:

[0019] Demonstrate intelligent combat algorithms available for subscription;

[0020] Responding to the subscription operation, identifying the subscription identifier corresponding to the subscribed intelligent combat algorithm;

[0021] According to the subscription identifier, query the collaborative entity status of the intelligent combat simulation entity of the collaborative combat;

[0022] Based on the collaborative entity state, the current entity state corresponding to the current intelligent combat simulation entity is determined.

[0023] In one of the embodiments, based on the collaborative entity state, determining the current entity state corresponding to the current intelligent combat simulation entity includes: obtaining intelligent combat algorithm parameters corresponding to the subscribed intelligent combat algorithm; calculating according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state corresponding to the current intelligent combat simulation entity.

[0024] In one of the embodiments, based on the collaborative entity state, the current entity state corresponding to the current intelligent combat simulation entity is determined; and the entity identifier of the current intelligent combat simulation entity is associated with the current entity state and stored.

[0025] The above-mentioned intelligent combat simulation platform and the data processing method of the intelligent combat simulation platform, the intelligent combat simulation platform includes an algorithm provider, an intelligent combat simulation entity and a general blackboard system; the algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity; the intelligent combat simulation entity sends a subscription request to the algorithm provider, the subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity, the subscription identifier is an identifier corresponding to the target intelligent combat algorithm, and the target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity; the algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier and sends the collaborative entity status query request to the general blackboard system; the general blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity; the intelligent combat simulation entity calculates according to the intelligent combat algorithm parameters and the collaborative entity status to obtain the current entity status; sends a write request carrying the current entity status to the general blackboard system; the general blackboard system responds to the write request and writes the current entity status. The whole scheme separates the parameter calculation process of the intelligent combat algorithm from the application process, and separates the algorithm calculation from the data storage process. The algorithm provider calculates the parameters of the intelligent combat algorithm and publishes it to the intelligent combat simulation entity that subscribes to the algorithm. The intelligent combat simulation entity reads the entity status of other collaborative operations from the general blackboard system, calculates the current entity status according to the collaborative entity status and the intelligent combat algorithm parameters, and writes the current entity status to the general blackboard system, which reduces the calculation and communication volume of the entity status during intelligent combat and improves the simulation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of a network architecture of an intelligent combat simulation platform in one embodiment;

[0027] Figure 2 A schematic diagram of a process flow of an intelligent combat simulation process in one embodiment;

[0028] Figure 3 A schematic diagram of a flow chart of a data processing method of an intelligent combat simulation platform in one embodiment;

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

[0030] 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.

[0031] In the era of intelligent warfare, a large number of combat equipment will enter the combat chain, forming a complex killing network. The more selectable nodes on the combat chain, the greater the flexibility, agility and sensitivity of the equipment system. The flexible grouping of different combat equipment will present a complex random network scenario to the opponent, while the equipment itself can form a fast link of various combat equipment according to the requirements of the combat mission, complete the target strike action under self-distribution, self-organization and self-control, and present intelligent characteristics of judgment, selection and adaptation in the combat process. That is, large-scale intelligent combat equipment relies on ubiquitous networks to form a group intelligence effect in a connected manner, which will become the key to success in intelligent warfare.

[0032] Intelligent warfare is different from traditional warfare, which will inevitably lead to different intelligent warfare simulation and modeling methods, and then lead to different simulation platforms that support intelligent warfare simulation and modeling. Traditional combat simulation is based on equipment platforms and adopts entity modeling, which leads to the simulation platforms that support traditional combat simulation being built on the basis of entities, while intelligent warfare divides equipment functions and adopts more fine-grained models for modeling, which will lead to the simulation platform being built on the basis of algorithms. In order to effectively support the construction of simulation platforms for intelligent warfare, studying the communication and data processing mechanisms of the simulation platform has become an urgent problem to be solved. Therefore, the communication and data processing method of the intelligent combat simulation platform provided in this application has important theoretical significance and reference value.

[0033] Communication and data processing mechanisms play a very important role in the construction of simulation platforms, and determine the structure and operating performance of the simulation platform, as well as the development and integration methods of simulation applications. In the process of simulation development, many simulation standard systems have emerged, and these standard systems are still in the process of continuous development and improvement, including ALSP (Aggregate Level Simulation Protocol), DIS (Distributed Interactive Simulation), HLA (High Level Architecture) and HLA-evolved (High Level Architecture evolved, a new generation of HLA standards), TENA (Test and Training enabling Architecture), DDS (Data Distribution Service) and other protocol standards. The communication and data processing mechanisms of simulation platforms implemented based on these standard systems mainly adopt broadcast-based communication mechanisms, process-based communication mechanisms and object-based communication mechanisms. The implementation technologies of these communication mechanisms are different and have their own characteristics. Based on the simulation platforms implemented by these communication mechanisms, many simulation applications have been developed in various countries, which have been successfully applied to the fields of aviation, aerospace, testing, training and education, and have strongly promoted the development of social economy.

[0034] The typical simulation protocol using broadcast communication mechanism is Distributed Interactive Simulation (DIS). This protocol uses consistent structure, standards and algorithms to interconnect different types of simulation models scattered in different geographical locations through the network, and establish a time-space consistent comprehensive simulation environment that people can participate in. The models in the environment are not divided into service type and client type. There is a peer-to-peer relationship between simulation models, and point-to-point connection and message broadcast transmission mechanism are used to exchange data units in real time. The advantages of the broadcast communication mechanism are simple structure and good fault tolerance, but its disadvantages are also obvious. First, when the number of simulation models increases and the amount of messages between models increases, it is difficult to ensure real-time communication between models, which is prone to data blocking or loss, and the reliability and scalability of data transmission deteriorate, making it difficult to meet the needs of large-scale distributed simulation; second, as long as the state of the simulation model changes, a complete PDU (Protocol Data Unit) message must be sent and sent to all nodes on the network, which greatly increases the communication volume; third, the state PDU of static entities must be sent in a periodic "heartbeat" manner, which lacks effective processing of static entities and wastes network bandwidth. However, since DIS can provide a real-time simulation time mechanism and meet the needs of certain specific simulation fields, it is still being continuously applied and improved.

[0035] The typical simulation protocol that adopts the process communication mechanism is the high-level architecture (HLA). HLA provides developers of simulation applications with a general framework for constructing and describing simulation applications, with the aim of solving two key problems in simulation: improving the interoperability between simulation applications and promoting the reuse of models in different fields. HLA mainly consists of three parts, namely, framework and rules, object model template and interface specification. The framework and rules define the federation members participating in the simulation and the rules that the federation must follow. The object model template describes the format and content of the objects, object attributes and information interaction between objects in the simulation. The interface specification defines the interface service set of the operation support framework RTI. The federation is a distributed simulation system used to achieve a specific simulation purpose, which consists of several mutually interacting federation members and the operation support framework RTI. All applications participating in the federation are called federation members, which are implemented by a logical process. RTI is a general distributed simulation support software used to integrate federation members, which is also implemented by a logical process. That is, the federation generally consists of multiple application processes and one service process.

[0036] The HLA interface specification defines the services that RTI provides to federation members and the responsibilities that each federation member should bear to the federation, which are implemented by the two classes of RTIambassador and FederateAmbassador. The RTIambassador class is responsible for implementing the services that federation members request from RTI. All requests to RTI made by federation members are completed by calling the RTIambassador member function. It can be seen that the RTIambassador class is the agent of RTI within the federation member, responsible for completing the communication between the federation member process and the RTI process. The FederateAmbassador class is responsible for implementing the service that RTI responds to the federation member. All messages received by the federation member from RTI are completed by calling back the member function of the FederateAmbassador class. It can be seen that the FederateAmbassador class is the agent of the federation member process within the RTI process, responsible for completing the communication between the RTI process and the federation member process. The FederateAmbassador class is only an abstract class. Each federated member must implement the functions declared in the FederateAmbassador class. When a federated member joins the federation, it must provide an instance of this class, that is, the federated member process must complete the reception of RTI messages within its own process.

[0037] A typical simulation protocol that uses an object communication mechanism is the Test and Training Enabling Architecture (TENA). The main purpose of TENA is to promote interoperability, reuse and composability between test and training resources, making simulation-based acquisition and simulation, test and evaluation processes possible. As a standard architecture for the construction and operation of logical ranges, TENA plays a vital role in the field of joint testing and training, and is the core technical standard throughout the entire life cycle of the transformation and construction of joint test and training capabilities. TENA is a complete set of architectures that are commonly followed by tests and trainings that are extended from C4ISR, including TENA middleware, TENA resource library, TENA database and various application tools. Among them, TENA middleware is responsible for the communication between all applications, and the main body of communication is the set of objects defined in the object model.

[0038] TENA applications consist of several objects, which are called state distributed objects (SDOs). SDOs are objects with non-zero lifetimes and evolving states during a task. They are the result of a combination of distributed object computing and a data-centric, anonymous, publish-and-subscribe data exchange mechanism. SDOs consist of two parts: object interface and public state. An SDO exists only in one process, which is called the server or "owner" of the SDO. At any given time, for any particular SDO instance, it belongs to only one "owner" process. The SDO instance itself is called a "server", and references to servers may exist in any process in the experimental domain, including the "server" process itself, which has a local proxy for the server's public state. The public state of an SDO can be distributed from the process that created the SDO instance to all processes that subscribe to the SDO; the subscribing process that owns the SDO proxy can activate methods in its interface to read the SDO's public state as if it were reading local data. If the public state of an SDO is changed by its publishing process, the subscribing process will receive the new value of the SDO's public state.

[0039] The intelligent combat simulation platform and the data processing method of the intelligent combat simulation platform provided in the embodiments of the present application can be applied to Figure 1In the application environment shown, the intelligent combat simulation platform includes an algorithm provider 102, an intelligent combat simulation entity 104, and a general blackboard system 106. The algorithm provider 102 displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity 104; the intelligent combat simulation entity 104 sends a subscription request to the algorithm provider 102, and the subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity 104. The subscription identifier is an identifier corresponding to the target intelligent combat algorithm, and the target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity 104; the algorithm provider 102 responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity 104, and feeds back the subscription identifier and the entity identifier to the general blackboard system 106; the intelligent combat simulation entity 104 receives the subscription request according to the subscription request. The subscription identifier generates a collaborative entity status query request, and sends the collaborative entity status query request to the general blackboard system 106; the general blackboard system 106 responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity 104 according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity 104, and feeds back the collaborative entity status to the intelligent combat simulation entity 104; the intelligent combat simulation entity 104 calculates according to the intelligent combat algorithm parameters and the collaborative entity status to obtain the current entity status; sends a write request carrying the current entity status to the general blackboard system 106; the general blackboard system 106 responds to the write request and writes the current entity status. The algorithm provider 102 and the intelligent combat simulation entity 104 can be, but are not limited to, various drones, personal computers, laptops, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The general blackboard system 106 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0040] The intelligent combat simulation platform for intelligent combat provided by the present application adopts a multi-intelligent system. The system imitates the human method of solving problems, that is, decomposing a problem into smaller sub-problems, each of which can be solved more easily by algorithms. The intelligent combat unit will be implemented as a collection of intelligent combat algorithms and attributes, and the intelligent combat algorithm is the main component. Each intelligent entity (i.e., intelligent combat simulation entity) usually performs a separate clearly defined task, i.e., an important class of algorithms, which will efficiently complete the specific functional behavior of the intelligent combat unit, and realize the common combat behavior of the intelligent group group through coordination and cooperation.

[0041] In one embodiment, Figure 2 As shown, an intelligent combat simulation platform is provided, which includes an algorithm provider, an intelligent combat simulation entity and a general blackboard system.

[0042] Specifically, the application of the intelligent combat simulation platform is realized through a number of intelligent combat algorithms. The algorithm-related functions include entity state calculation and intelligent combat algorithm parameter maintenance. The entity state calculation can obtain the state corresponding to the entity, and the intelligent combat algorithm parameters are trained based on historical entity state data. Therefore, the communication of the simulation platform includes the communication of algorithm parameters and entity state. The intelligent combat algorithm (i.e., algorithm structure parameters) can remain unchanged during the actual application process, or it can be continuously updated online according to the updated entity state. The intelligent combat simulation entity can calculate the entity state by calling the intelligent combat algorithm, and also distribute the entity state to other intelligent combat simulation entities that subscribe to the intelligent combat algorithm for collaborative combat.

[0043] The architecture of the intelligent combat simulation platform is centered on the universal blackboard system, which creates a joint data repository to separate the data of the intelligent combat algorithm and the intelligent combat simulation entity. The joint data repository contains the application data of the entire simulation system during operation, allowing the algorithm provider and the intelligent combat simulation entity to access and modify the data when necessary, and also allowing the entire system to achieve synchronous and asynchronous data operations. The algorithm provider and the intelligent combat simulation entity can access the application data at any time. The universal blackboard manager in the universal blackboard system is responsible for creating and maintaining the data warehouse on each intelligent combat simulation entity node, and is also responsible for application data publishing and data synchronization between nodes.

[0044] Algorithm providers display the intelligent combat algorithms available for subscription to intelligent combat simulation entities.

[0045] Specifically, the algorithm provider is responsible for maintaining the algorithm parameters of all intelligent combat algorithms on the intelligent combat simulation platform. The algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity, so that the intelligent combat simulation entity can subscribe to the required intelligent combat algorithms according to combat needs.

[0046] The intelligent combat simulation entity sends a subscription request to the algorithm provider.

[0047] Specifically, the intelligent combat simulation entity is the algorithm user of the intelligent combat algorithm. The intelligent combat simulation entity subscribes to the required intelligent combat algorithm according to the combat requirements and generates a subscription request. Among them, the subscription request carries the subscription identifier and the entity identifier of the intelligent combat simulation entity. The subscription identifier is the identifier corresponding to the target intelligent combat algorithm, and the target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity. When calculating the entity state, it only needs to call the intelligent combat algorithm for calculation to obtain the current entity state.

[0048] The algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription identifier and the entity identifier to the general blackboard system.

[0049] Specifically, after the algorithm provider intercepts the subscription request sent by the intelligent combat simulation entity, it parses the subscription request, obtains the subscription identifier and the entity identifier of the intelligent combat simulation entity, the subscription identifier is the identifier corresponding to the target intelligent combat algorithm, obtains the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm according to the subscription identifier, sends the intelligent combat algorithm parameters to the intelligent combat simulation entity, and the intelligent combat simulation entity receives the intelligent combat algorithm parameters. The algorithm provider sends the subscription identifier and the entity identifier of the intelligent combat simulation entity to the general blackboard system.

[0050] The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier, and sends the collaborative entity status query request to the general blackboard system.

[0051] Specifically, since the subscription identifiers of the intelligent combat simulation entities performing collaborative operations are the same, the intelligent combat simulation entity generates a collaborative entity status query request based on the subscription identifier, and sends the collaborative entity status query request to the general blackboard system to query the collaborative entity status of other intelligent combat simulation entities performing collaborative operations.

[0052] The general blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity.

[0053] Specifically, the general blackboard system stores the state data of the simulation entity applying the intelligent combat algorithm in the same data warehouse according to the identifier corresponding to the target intelligent combat algorithm. The general blackboard system responds to the collaborative entity state query request sent by the intelligent combat simulation entity, parses the collaborative entity state query request, obtains the subscription identifier, queries the collaborative intelligent combat simulation entity identifier from the data warehouse according to the subscription identifier, obtains the collaborative entity state of the collaborative intelligent combat simulation entity according to the collaborative intelligent combat simulation entity identifier, and feeds back the collaborative entity state to the intelligent combat simulation entity.

[0054] The intelligent combat simulation entity calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state; sends a write request carrying the current entity state to the general blackboard system; the general blackboard system responds to the write request and writes the current entity state.

[0055] Specifically, the intelligent combat simulation entity receives the collaborative entity state sent by the general blackboard system, and calls the intelligent combat algorithm to calculate according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state; the intelligent combat simulation entity generates a write request according to the current entity state, and sends the write request carrying the current entity state to the general blackboard system. The general blackboard system listens to and responds to the write request, writes the current entity state, and provides the current entity state for the intelligent combat simulation entity in the next round of collaborative combat.

[0056] The above-mentioned intelligent combat simulation platform includes an algorithm provider, an intelligent combat simulation entity and a general blackboard system; the algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity; the intelligent combat simulation entity sends a subscription request to the algorithm provider, the subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity, the subscription identifier is an identifier corresponding to the target intelligent combat algorithm, and the target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity; the algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription identifier and the entity identifier to the general blackboard system; the intelligent combat simulation entity generates a collaborative entity state query request according to the subscription identifier, and sends the collaborative entity state query request to the general blackboard system; the general blackboard system responds to the collaborative entity state query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity state of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity state to the intelligent combat simulation entity; the intelligent combat simulation entity calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state; sends a write request carrying the current entity state to the general blackboard system; the general blackboard system responds to the write request and writes the current entity state. The entire solution separates the parameter calculation process of the intelligent combat algorithm from the application process, and the algorithm calculation from the data storage process. The algorithm provider calculates the parameters of the intelligent combat algorithm and publishes them to the intelligent combat simulation entity that subscribes to the algorithm. The intelligent combat simulation entity reads the status of other collaborative combat entities from the general blackboard system, calculates the current entity status based on the collaborative entity status and the intelligent combat algorithm parameters, and writes the current entity status into the general blackboard system, which reduces the calculation and communication volume of the entity status during intelligent combat and improves the simulation efficiency.

[0057] In an optional embodiment, the algorithm provider sends the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity; the intelligent combat simulation entity configures the intelligent combat algorithm interface according to the intelligent combat algorithm configuration parameters, obtains the configured intelligent combat algorithm, calls the configured intelligent combat algorithm, and calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state.

[0058] Specifically, after the algorithm provider intercepts the subscription request sent by the intelligent combat simulation entity, it parses the subscription request to obtain the subscription identifier and the entity identifier of the intelligent combat simulation entity, obtains the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameter values ​​corresponding to the target intelligent combat algorithm according to the subscription identifier, sends the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters to the intelligent combat simulation entity, and the intelligent combat simulation entity receives the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters, configures the intelligent combat algorithm interface according to the intelligent combat algorithm configuration parameters (i.e., generates an algorithm instance of the intelligent combat algorithm), and obtains the configured intelligent combat algorithm. The intelligent combat simulation entity calls the configured intelligent combat algorithm for calculation according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state.

[0059] In an optional embodiment, the algorithm provider sends a historical data query request to the general blackboard system, and the general blackboard system responds to the historical data query request and feeds back the historical combat status data set of the intelligent combat simulation entity to the algorithm provider; the algorithm provider trains the intelligent combat algorithm corresponding to the intelligent combat algorithm service based on the historical combat status data set to obtain the intelligent combat algorithm parameters.

[0060] Among them, the historical combat status data set is generated based on the entity status of multiple intelligent combat simulation entities in coordinated combat within a preset time period.

[0061] Specifically, the algorithm provider generates a historical data query request and sends the historical data query request to the general blackboard system. The general blackboard system listens to and responds to the historical data query request, queries the entity status of multiple collaborative intelligent combat simulation entities within a preset time period, and feeds back the historical combat status data set of the intelligent combat simulation entity to the algorithm provider. The algorithm provider trains the intelligent combat algorithm corresponding to the intelligent combat algorithm service based on the historical combat status data set, and obtains the intelligent combat algorithm parameters after the training is completed.

[0062] In an optional embodiment, the algorithm provider obtains the current entity state from the general blackboard system; updates the intelligent combat algorithm parameters according to the current entity state to obtain the intelligent combat algorithm update parameters; and distributes the intelligent combat algorithm update parameters to the intelligent combat simulation entities that have subscribed to the intelligent combat algorithm.

[0063] Specifically, the algorithm provider generates a current data query request according to the subscription identifier, and sends the current data query request to the general blackboard system. The general blackboard system listens to and responds to the current data query request, obtains the current entity state of the intelligent combat simulation entity of the cooperative operation from the general blackboard system according to the subscription identifier, updates the intelligent combat algorithm parameters online according to the current entity state, obtains the intelligent combat algorithm update parameters, and distributes the intelligent combat algorithm update parameters to the intelligent combat simulation entities that have subscribed to the intelligent combat algorithm, so that the intelligent combat simulation entities of the cooperative operation perform state calculation according to the intelligent combat algorithm update parameters to obtain a more accurate entity state.

[0064] In an optional embodiment, the algorithm provider is also used to calculate the entity state of the intelligent combat simulation entity based on the intelligent combat algorithm parameters to obtain the simulation entity state; based on the error between the simulation entity state and the current entity state, the intelligent combat algorithm parameters are updated to obtain the intelligent combat algorithm update parameters.

[0065] Specifically, the algorithm provider calculates the entity state of the intelligent combat simulation entity according to the intelligent combat algorithm parameters to obtain the simulation entity state. The algorithm provider generates a current data query request according to the subscription identifier and sends the current data query request to the general blackboard system. The general blackboard system listens to and responds to the current data query request, obtains the current entity state of the intelligent combat simulation entity of the cooperative combat from the general blackboard system according to the subscription identifier, calculates the error between the simulation entity state and the current entity state, and updates the intelligent combat algorithm parameters according to the error between the simulation entity state and the current entity state to obtain the intelligent combat algorithm update parameters.

[0066] In an optional embodiment, the intelligent combat simulation entity is also used to obtain input combat requirement parameters and generate a subscription request based on the combat requirement parameters.

[0067] Among them, the combat requirement parameters are the task requirement parameters that the intelligent combat simulation entity needs to complete. The combat requirement parameters include parameters corresponding to learning, reconnaissance, judgment, decision-making, attack and destruction requirements.

[0068] Specifically, the user inputs combat requirement parameters to the intelligent combat simulation entity, and the intelligent combat simulation entity receives the combat requirement parameters input by the user and generates a subscription request according to the combat requirement parameters.

[0069] In an optional embodiment, the algorithm provider provides at least one intelligent combat algorithm built based on an algorithm tree.

[0070] Specifically, intelligent combat algorithms can include learning algorithms, reconnaissance algorithms, judgment algorithms, decision algorithms, strike algorithms, and damage algorithms. All intelligent combat algorithms provided by the algorithm provider are organized in a tree structure. Each node on the tree is an intelligent combat algorithm. The root node is an abstract algorithm, which mainly provides an abstract interface and is responsible for providing the intelligent combat simulation platform with the execution method of the intelligent combat algorithm. There is a hierarchy between nodes, and the hierarchy between nodes is predefined. For example, node 1 is a high-level node, node 2 is a low-level node, and the intelligent algorithm on node 1 is an abstraction of the intelligent algorithm on node 2. The intelligent algorithm on node 2 can further derive, expand, and refine the intelligent algorithm on node 1. The intelligent combat simulation entity can call all intelligent combat algorithms by calling the interface of the intelligent combat algorithm and using the object-oriented overloading feature.

[0071] Intelligent combat algorithms can exist in multiple processes, but algorithm instances only exist in one process, and the process is called the "intelligent combat simulation entity" of the algorithm instance (that is, the algorithm's user or owner). The algorithm communication mechanism process is as follows: Figure 1 As shown. At any time, for any specific algorithm instance, it belongs only to a unique "intelligent combat simulation entity" (i.e., the learner or provider of the algorithm) process. The intelligent combat algorithm itself has an "algorithm provider" who is responsible for evolving and maintaining the algorithm's own parameters. Other algorithm instances only read the intelligent combat algorithm parameters provided by the "algorithm provider". The reading of the intelligent combat algorithm parameters provided by the "algorithm provider" may exist in any process of the simulation application, including the server's own process, which has a local agent of the algorithm server. The parameters of an intelligent combat algorithm can be distributed from the process that creates the algorithm instance to all processes that subscribe to the algorithm; the subscribing process that owns the intelligent combat algorithm agent can read the intelligent combat algorithm parameters like reading local data. If a certain intelligent combat algorithm parameter is changed by its publishing process, the subscribing process will receive the updated parameters of the intelligent combat algorithm.

[0072] In an optional embodiment, the intelligent combat simulation platform is constructed based on a three-layer architecture of hardware layer, data layer and scheduling algorithm layer.

[0073] Specifically, the architecture of the intelligent combat simulation platform is divided into three layers. The first layer is the hardware layer, which is mainly the hardware environment for the operation of the simulation platform, including distributed systems and high-performance parallel systems for intelligent combat simulation entities to simulate; the second layer is the data layer, also known as the general blackboard system, which is built on the hardware layer to achieve the interconnection and sharing of intelligent combat simulation entity data; the third layer is the scheduling algorithm layer, which implements the access and modification of the simulation entity attribute data on the general blackboard system through the execution of the scheduling algorithm. As time goes on, when the intelligent algorithm is continuously scheduled for execution, the operation of the intelligent combat simulation system can be realized.

[0074] The data layer is a universal blackboard system. A joint data repository is created at the data layer. The joint data repository stores application data during the entire simulation system operation period. Based on the universal blackboard mechanism, the entity data of the intelligent combat simulation entity at the data layer can be synchronized to the corresponding heterogeneous environment at the hardware layer. The scheduling algorithm layer includes intelligent combat algorithms that implement intelligent combat behaviors. Each intelligent combat algorithm is used to implement a specific task of the intelligent combat simulation entity. Intelligent combat algorithms include learning algorithms, reconnaissance algorithms, judgment algorithms, decision algorithms, strike algorithms, and damage algorithms. The interaction between intelligent combat algorithms is achieved through the universal blackboard system.

[0075] The universal blackboard system in the data layer can realize data synchronization between entity nodes of intelligent combat simulation and ensure the accuracy of entity data.

[0076] The scheduling algorithm layer schedules the intelligent combat algorithms on each algorithm node according to the time series. In the intelligent combat simulation, the scheduling algorithm layer responds to the simulation instruction, triggers the algorithm process (such as algorithm process 1, algorithm process n, algorithm process m, etc.) according to the time series, schedules the intelligent combat algorithm corresponding to the algorithm process, and accesses the entity data of the intelligent combat simulation entity in the data layer. When the entity data of the intelligent combat simulation entity in the data layer is detected to be updated, the corresponding entity data is modified, and the modified entity data is synchronized to the heterogeneous environment associated with the entity data. Scheduling is performed sequentially based on the time series to realize simulation in the heterogeneous simulation environment.

[0077] In one embodiment, Figure 3 As shown, a data processing method for an intelligent combat simulation platform is provided, the method comprising:

[0078] Step 302, display the intelligent combat algorithms available for subscription.

[0079] Specifically, the algorithm provider of the intelligent combat simulation platform is responsible for maintaining the algorithm parameters of all intelligent combat algorithms on the intelligent combat simulation platform. The algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity, so that the intelligent combat simulation entity can subscribe to the required intelligent combat algorithms according to combat needs.

[0080] Step 304, responding to the subscription operation, identifying the subscription identifier corresponding to the subscribed intelligent combat algorithm.

[0081] Specifically, the user inputs combat requirement parameters to the intelligent combat simulation entity, and the intelligent combat simulation entity receives the combat requirement parameters input by the user, and generates a subscription request according to the combat requirement parameters. After the algorithm provider intercepts the subscription request sent by the intelligent combat simulation entity, it parses the subscription request, obtains the subscription identifier and the entity identifier of the intelligent combat simulation entity, and the subscription identifier is the identifier corresponding to the target intelligent combat algorithm. According to the subscription identifier, the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm are obtained, and the intelligent combat algorithm parameters are sent to the intelligent combat simulation entity, and the intelligent combat simulation entity receives the intelligent combat algorithm parameters. The algorithm provider sends the subscription identifier and the entity identifier of the intelligent combat simulation entity to the general blackboard system.

[0082] The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier, and sends the collaborative entity status query request to the general blackboard system to query the collaborative entity status of other collaborative intelligent combat simulation entities.

[0083] Step 306, querying the collaborative entity status of the collaborative intelligent combat simulation entity according to the subscription identifier.

[0084] Specifically, the general blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity.

[0085] Step 308, based on the collaborative entity state, determine the current entity state corresponding to the current intelligent combat simulation entity.

[0086] Specifically, the general blackboard system responds to the collaborative entity state query request sent by the intelligent combat simulation entity, parses the collaborative entity state query request, obtains the subscription identifier, queries the collaborative intelligent combat simulation entity identifier from the data warehouse according to the subscription identifier, obtains the collaborative entity state of the collaborative intelligent combat simulation entity according to the collaborative intelligent combat simulation entity identifier, and feeds back the collaborative entity state to the intelligent combat simulation entity. Based on the collaborative entity state, the intelligent combat simulation entity calculates the current entity state corresponding to the current intelligent combat simulation entity.

[0087] The data processing method of the above-mentioned intelligent combat simulation platform separates the parameter calculation process of the intelligent combat algorithm from the application process, and separates the algorithm calculation from the data storage process. The algorithm provider calculates the parameters of the intelligent combat algorithm and publishes them to the intelligent combat simulation entity that subscribes to the algorithm. The intelligent combat simulation entity reads the entity status of other collaborative combat entities from the general blackboard system, calculates the current entity status according to the collaborative entity status and the intelligent combat algorithm parameters, and writes the current entity status into the general blackboard system, thereby reducing the calculation and communication volume of the entity status during intelligent combat simulation and improving the simulation efficiency.

[0088] In an optional embodiment, based on the collaborative entity state, determining the current entity state corresponding to the current intelligent combat simulation entity includes: obtaining the intelligent combat algorithm parameters corresponding to the subscribed intelligent combat algorithm; calculating according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state corresponding to the current intelligent combat simulation entity.

[0089] Specifically, the intelligent combat simulation entity receives the collaborative entity state sent by the general blackboard system, receives the intelligent combat algorithm parameters sent by the algorithm server, and calls the intelligent combat algorithm to calculate according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state.

[0090] In an optional embodiment, based on the collaborative entity state, the current entity state corresponding to the current intelligent combat simulation entity is determined; and the entity identifier of the current intelligent combat simulation entity is associated with the current entity state and stored.

[0091] Specifically, the intelligent combat simulation entity calculates the current entity state corresponding to the current intelligent combat simulation entity based on the collaborative entity state. The intelligent combat simulation entity generates a write request according to the current entity state, and sends the write request carrying the current entity state to the general blackboard system. The general blackboard system listens to and responds to the write request, and the entity identifier of the current intelligent combat simulation entity is associated with the current entity state and stored in the data warehouse corresponding to the subscription identifier, providing the current entity state for the next round of collaborative combat intelligent combat simulation entities.

[0092] In order to facilitate the understanding of the technical solution provided in the embodiment of the present application, a complete intelligent combat simulation process is briefly described:

[0093] (1) The algorithm provider sends a historical data query request to the general blackboard system. The general blackboard system responds to the historical data query request and feeds back the historical combat status data set of the intelligent combat simulation entity to the algorithm provider. The algorithm provider trains the intelligent combat algorithm corresponding to the intelligent combat algorithm service based on the historical combat status data set to obtain the intelligent combat algorithm parameters.

[0094] (2) Algorithm providers display the intelligent combat algorithms available for subscription to intelligent combat simulation entities.

[0095] (3) The intelligent combat simulation entity obtains the input combat requirement parameters and generates a subscription request based on the combat requirement parameters; the intelligent combat simulation entity sends the subscription request to the algorithm provider, and the subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity. The subscription identifier is the identifier corresponding to the target intelligent combat algorithm, and the target intelligent combat algorithm is the intelligent combat algorithm subscribed by the intelligent combat simulation entity.

[0096] (4) The algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription identifier and entity identifier to the general blackboard system.

[0097] (5) The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier and sends the collaborative entity status query request to the general blackboard system.

[0098] (6) The general blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity.

[0099] (7) The intelligent combat simulation entity configures the intelligent combat algorithm interface according to the intelligent combat algorithm configuration parameters, obtains the configured intelligent combat algorithm, calls the configured intelligent combat algorithm, and calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state; and sends a write request carrying the current entity state to the general blackboard system.

[0100] (8) The general blackboard system responds to the write request and writes the current entity status.

[0101] (9) The algorithm provider is also used to calculate the entity state of the intelligent combat simulation entity according to the intelligent combat algorithm parameters to obtain the simulation entity state. The algorithm provider obtains the current entity state from the general blackboard system; updates the intelligent combat algorithm parameters according to the error between the simulation entity state and the current entity state to obtain the intelligent combat algorithm update parameters; and distributes the intelligent combat algorithm update parameters to the intelligent combat simulation entities that have subscribed to the intelligent combat algorithm.

[0102] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0103] In one embodiment, a computer device is provided. The computer device may be an algorithm provider or an intelligent combat simulation entity. The internal structure diagram thereof may be as follows: Figure 4 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device 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 and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, an intelligent combat simulation process is realized. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0104] Those skilled in the art will understand that Figure 4 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.

[0105] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed 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 the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0106] 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.

[0107] 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. An intelligent combat simulation platform, characterized in that: Includes algorithm providers, intelligent combat simulation entities, and general blackboard systems; The algorithm provider displays the intelligent combat algorithms available for subscription to the intelligent combat simulation entity; The intelligent combat simulation entity sends a subscription request to the algorithm provider, the subscription request carries a subscription identifier and an entity identifier of the intelligent combat simulation entity, the subscription identifier is an identifier corresponding to a target intelligent combat algorithm, and the target intelligent combat algorithm is an intelligent combat algorithm subscribed by the intelligent combat simulation entity; The algorithm provider responds to the subscription request, feeds back the intelligent combat algorithm parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity, and feeds back the subscription identifier and the entity identifier to the universal blackboard system; The intelligent combat simulation entity generates a collaborative entity status query request according to the subscription identifier, and sends the collaborative entity status query request to the general blackboard system; The universal blackboard system responds to the collaborative entity status query request, queries the collaborative intelligent combat simulation entity according to the subscription identifier, obtains the collaborative entity status of the collaborative intelligent combat simulation entity, and feeds back the collaborative entity status to the intelligent combat simulation entity; The intelligent combat simulation entity performs calculations according to the intelligent combat algorithm parameters and the collaborative entity state to obtain a current entity state; A write request carrying the current entity state is sent to the universal blackboard system; the universal blackboard system responds to the write request and writes the current entity state.

2. The intelligent combat simulation platform according to claim 1, characterized in that: The algorithm provider sends intelligent combat algorithm parameters and intelligent combat algorithm configuration parameters corresponding to the target intelligent combat algorithm to the intelligent combat simulation entity; The intelligent combat simulation entity configures the intelligent combat algorithm interface according to the intelligent combat algorithm configuration parameters, obtains the configured intelligent combat algorithm, calls the configured intelligent combat algorithm, and calculates according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state.

3. The intelligent combat simulation platform according to claim 1, characterized in that: The algorithm provider sends a historical data query request to the universal blackboard system, and the universal blackboard system responds to the historical data query request and feeds back the historical combat status data set of the intelligent combat simulation entity to the algorithm provider; The algorithm provider trains the intelligent combat algorithm corresponding to the intelligent combat algorithm service according to the historical combat status data set to obtain the intelligent combat algorithm parameters.

4. The intelligent combat simulation platform according to claim 1, characterized in that: The algorithm provider obtains the current entity state from the universal blackboard system; updates the intelligent combat algorithm parameters according to the current entity state to obtain the intelligent combat algorithm update parameters; The intelligent combat algorithm update parameters are distributed to the intelligent combat simulation entities that have subscribed to the intelligent combat algorithm.

5. The intelligent combat simulation platform according to claim 4, characterized in that: The algorithm provider is also used to calculate the entity state of the intelligent combat simulation entity according to the intelligent combat algorithm parameters to obtain the simulation entity state; update the intelligent combat algorithm parameters according to the error between the simulation entity state and the current entity state to obtain the intelligent combat algorithm update parameters.

6. The intelligent combat simulation platform according to claim 1, characterized in that: The intelligent combat simulation entity is also used to obtain input combat requirement parameters and generate a subscription request according to the combat requirement parameters.

7. The intelligent combat simulation platform according to claim 1, characterized in that: The algorithm provider provides at least one intelligent combat algorithm constructed based on an algorithm tree.

8. A data processing method for an intelligent combat simulation platform according to any one of claims 1 to 7, characterized in that: The method comprises: Demonstrate intelligent combat algorithms available for subscription; Responding to the subscription operation, identifying the subscription identifier corresponding to the subscribed intelligent combat algorithm; According to the subscription identifier, query the collaborative entity status of the intelligent combat simulation entity of the collaborative combat; Based on the collaborative entity state, a current entity state corresponding to the current intelligent combat simulation entity is determined.

9. The method according to claim 8, characterized in that The determining, based on the collaborative entity state, a current entity state corresponding to the current intelligent combat simulation entity comprises: Obtaining intelligent combat algorithm parameters corresponding to the subscribed intelligent combat algorithm; Calculation is performed according to the intelligent combat algorithm parameters and the collaborative entity state to obtain the current entity state corresponding to the current intelligent combat simulation entity.

10. The method according to claim 8, characterized in that Determining a current entity state corresponding to a current intelligent combat simulation entity based on the collaborative entity state; The entity identification of the current intelligent combat simulation entity is associated with the current entity state and stored.

Images