Intelligent combat simulation method, device, computer equipment and storage medium

By introducing entity reference relationship fields into the intelligent combat simulation system, and processing link relationships between entities during automatic initialization, the problems of insufficient initialization accuracy and simulation results in the existing technology are solved, and efficient simulation object initialization is achieved.

CN111695270BActive Publication Date: 2024-11-26NAT UNIV OF DEFENSE TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010589547.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-24
Publication Date
2024-11-26
Estimated Expiration
2040-06-24

AI Technical Summary

Technical Problem

The existing intelligent combat simulation system is difficult to effectively handle complex network link relationships between entities during initialization, resulting in poor initialization accuracy and simulation results.

Method used

By introducing entity reference relationship fields in the simulation system, the link relationship between entities is identified and streamlined during automatic initialization, and the accurate initialization assignment between entities is achieved.

Benefits of technology

It improves the initialization accuracy and simulation effect of the simulation system, reduces manual participation and error rates, and realizes the automated initialization of simulation objects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111695270B_ABST
    Figure CN111695270B_ABST
Patent Text Reader

Abstract

The present application relates to an intelligent combat simulation method, device, computer equipment and storage medium. The method includes: obtaining a formal description file of an intelligent combat simulation assumption; parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity; if the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities. By using the entity reference relationship field to identify this complex network link relationship, when the simulation is initialized, the simulation entity can be referenced to a related entity according to the reference relationship field, the network link relationship between entities can be straightened out, and the accuracy of initialization and the simulation effect can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of simulation technology, and in particular to an intelligent combat simulation method, device, computer equipment and storage medium. Background Art

[0002] Intelligent warfare is a grouping of various intelligent weapons and equipment that perform reconnaissance, mobility, strike and protection missions. Based on the mission objectives, enemy conditions, battlefield environment, and real-time changes in their own status, they can independently judge the situation, select and execute appropriate action plans, and continuously learn and improve their judgment and decision-making capabilities during the combat process. The role of scenarios is mainly to describe the scene, role, and the process of events.

[0003] The operation of intelligent combat simulation system needs to be supported by intelligent simulation scenarios. In order to support the operation of intelligent simulation system, it is urgent to study the standardized interface description of intelligent combat simulation system scenarios and related issues, and realize the conversion of traditional military scenarios to intelligent combat simulation scenarios. Summary of the invention

[0004] Based on this, it is necessary to provide an intelligent combat simulation method, device, computer equipment and storage medium that can improve the intelligent simulation effect in response to the above technical problems.

[0005] An intelligent combat simulation method, the method comprising:

[0006] Obtain the formal description file of intelligent combat simulation scenario;

[0007] Parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity;

[0008] If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0009] In one embodiment, the entity reference relationship field includes an entity sibling relationship field, and the method further includes:

[0010] Acquire the sibling relationship entity of the simulation entity according to the entity sibling relationship field;

[0011] Find the entity sibling relationship field of the sibling relationship entity to verify whether the two entities are sibling relationship entities;

[0012] If so, when the simulation system is automatically initialized, the simulation entity references the related entity according to the reference relationship field, and initializes and assigns values ​​to the simulation entity.

[0013] In one embodiment, the entity reference relationship field includes a common entity field, and the method further includes:

[0014] Determine the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the belonging relationship of the simulation entity;

[0015] According to the formal description of the simulation entity, searching whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity;

[0016] If they are the same, when the simulation system is automatically initialized, the simulation entity is referenced by the field of the related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value.

[0017] In one embodiment, the entity relationship field includes an aggregated virtual entity relationship field; when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including:

[0018] According to the aggregated virtual entity relationship field, obtaining all entities referenced by the aggregated virtual entity;

[0019] The simulation entity is initialized and assigned values ​​according to the parameters of all entities referenced by the aggregated virtual entity.

[0020] In one of the embodiments, the aggregated virtual entity relationship field includes an aggregated communication simulation entity field; based on the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained, including: based on the aggregated communication simulation entity field, communication equipment of command posts at all levels referenced by the simulated communication entity is obtained.

[0021] In one of the embodiments, the entity relationship field includes a selected reference entity field, and the reference entity field is selected from a plurality of candidate options.

[0022] In one of the embodiments, the candidate options for the command mode include: step-by-step command, skip-level command and succession command; when the simulation system is automatically initialized, the simulation entity references the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: when the simulation system is automatically initialized, the command posts at all levels establish command relationships with entities of other command posts according to the selected command mode, and initialize and assign values ​​to the simulation command post entities.

[0023] An intelligent combat simulation device, comprising:

[0024] A description file acquisition module is used to obtain a formal description file of the intelligent combat simulation scenario;

[0025] A parsing module, used for parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity;

[0026] A simulation module is used to initialize and assign values ​​to the simulation entity by referencing related entities according to the reference relationship field when the simulation system is automatically initialized if the formal description of the simulation entity includes an entity reference relationship field, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0027] 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:

[0028] Obtain the formal description file of intelligent combat simulation scenario;

[0029] Parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity;

[0030] If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities.

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

[0032] Obtain the formal description file of intelligent combat simulation scenario;

[0033] Parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity;

[0034] If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0035] The above-mentioned intelligent combat simulation method, device, computer equipment and storage medium parse the formal description file of the simulation assumption, and the entity reference relationship field is used to mark the link relationship between entities. When the formal description of the simulation entity includes the entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned. By using the entity reference relationship field to identify this complex network link relationship, when the simulation is initialized, the simulation entity can be referenced to the relevant entity according to the reference relationship field, and the network link relationship between entities can be straightened out, thereby improving the accuracy of initialization and the simulation effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An application environment diagram of an intelligent combat simulation method in an embodiment;

[0037] Figure 2 A schematic diagram of a flow chart of an intelligent combat simulation method in one embodiment;

[0038] Figure 3 A schematic diagram of common attribute description in one embodiment;

[0039] Figure 4 A schematic diagram for describing a virtual entity in another embodiment;

[0040] Figure 5 A schematic diagram of a file in one embodiment;

[0041] Figure 6 A structural block diagram of an intelligent combat simulation device in one embodiment;

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

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

[0044] The intelligent combat simulation method provided by this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the large screen 104, implements the intelligent combat simulation method, and demonstrates the simulation results on the large screen. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices.

[0045] In one embodiment, Figure 2As shown, an intelligent combat simulation method is provided, which is applied to Figure 1 The terminal in is used as an example to illustrate, including the following steps:

[0046] Step 202, obtaining a formal description file of the assumptions of the intelligent combat simulation.

[0047] The main function of the scenario is to describe the scene, roles and the process of events. The definition of the scenario in our military language is: the idea and assumption of the intentions, situation and development of the warring parties according to the training topic, which is the basic document for organizing and guiding exercises and operations. The scenario formal description file is a file that describes the scene, roles and the process of events in a specific format.

[0048] Intelligent combat simulation scenarios are composed of entities, environments, actions, tasks, events, interactions, relationships, simulation structures and rules. The combination of these elements can fully constitute intelligent simulation scenarios. The content of intelligent simulation scenarios is closely related to the scale of intelligent scenarios and the working mode of the simulation system.

[0049] Entity is an abstraction of various components in the simulation system. Each component in the simulation system can be regarded as an entity. According to the different functions of the entities, the entities in the simulation system can be divided into: decision-making entities, action entities and target entities. The environment specifies a multi-dimensional space-time framework that describes the natural, battlefield and strategic environment in which various entities within the boundaries of the simulation system act.

[0050] An action is the smallest granularity of an activity performed by an entity and has a unique meaning. A task is the execution of an action by an entity and is the instantiation of an action. The execution of a task needs to meet certain "entry conditions". During the execution process, it can receive one or more inputs and may also send one or more outputs, and its results will affect the properties of certain entities. An event is a phenomenon or activity with certain meaning and influence, and is the focus of research issues. Events are usually manifested as changes in the state set of an entity and are closely related to certain tasks.

[0051] Interaction is the interaction between an entity that performs a task or action and a target entity. The entity that actively exerts influence on other entities is called a sending entity, and the entity that receives and is affected by the interaction is called a receiving entity. Interaction is an interface that defines the events, states, entities, or workflows between two entities.

[0052] A relationship is a relationship between two entities in the same domain. Relationships include: adjacency, collaboration, command, communication, control, occupation, possession, operation, hostility, organization, possession, supply, and support. The difference between a relationship and an interaction is that a relationship lasts longer, that is, it lasts longer than the action. Interactions are conceptually between actions, and relationships are conceptually between entities. Both interactions and relationships are essentially related to entity composition, and the difference is that interactions represent processes or exchanges that last for a period of time.

[0053] The simulation structure is the overall design of the simulation system application, which specifies the basic form of the application, including simulation grouping, such as the red party, blue party, neutral party, etc.; role division refers to the allocation of entities in the simulation system to each party; the simulation time advancement mechanism stipulates how the simulation time runs during the simulation process, generally there are three modes: discrete, continuous and mixed; the decision process refers to the order in which decisions are made on a simulation problem.

[0054] Simulation rules are a series of protocol rules that manage the entire simulation process, and their purpose is to ensure the smooth operation of the simulation system. Simulation rules are divided into role rules, communication rules, etc. Role rules refer to the task rules that each entity in the simulation system must abide by; communication rules refer to the regulations for communication within the simulation system organization and between different groups.

[0055] XML documents have the characteristics of separation of description content and structure, strong interoperability, unified specifications, and strong extensibility, making the application of XML standards more and more widespread. There is no doubt that it is very correct for intelligent combat simulation to use XML language to formally describe the scenario data.

[0056] The scenario formal description file consists of scenario overview, scenario time, combat area, scenario environment, responsibility area set, formation set, combat phase set and simulation entity set.

[0057] Among them, in the formal description of the scenario overview, time and combat area, the scenario overview describes the basic information of the scenario, including the scenario name, creator, creation time, modification time, situation map name, scenario version and notes. The "situation map name" describes the situation file used when formulating the current scenario data exchange file. The scenario time describes the time span of the current simulation, which is a definition of the physical time of the simulation application. The combat area describes the rectangular geographical scope of the current simulation entity activities, which is described by the longitude and latitude and altitude range of the boundary points of the combat area. The hypothetical environmental data describes the various gradual and fast-changing environmental factors that affect the simulation effect, such as data on geography, meteorological and hydrological environment, and electromagnetic propagation.

[0058] Responsibility area, formation, and combat phase are formally described. The responsibility area set consists of all responsibility areas of the current simulation entity. Each responsibility area is described by three fields: responsibility area name, responsibility area number, and responsibility area type. According to the responsibility area type, the corresponding type of responsibility area data is attached to the responsibility area. In addition, the boundary line data can also be attached to the responsibility area.

[0059] The group set gives all the groups under the current scenario. Each group is allowed to have multiple simulation subordinate entities and multiple subordinate groups, thus forming a tree structure of the group. The group has three fields: number, group number and enemy and friend attributes. The group number is used for display and easy understanding; the group number is used to distinguish each group and is unique in the entire scenario file. The enemy and friend attributes of the group are: "red", "blue", "white" and "unknown", etc. In the hierarchical relationship of the same group, the enemy and friend attributes of all groups and the enemy and friend attributes of the simulation entity should be consistent. Subordinate groups are described by group numbers and group numbers, and subordinate simulation entities are described by simulation entity names and simulation entity numbers. Each group only briefly describes its subordinate simulation entities, and detailed information such as attribute parameters, routes, and behaviors of the simulation entities are described in the simulation entity set.

[0060] The combat phase set consists of all the combat phases in the scenario. Each combat phase is described by six fields: phase name, phase number, start time, end time, combat wave, and remarks.

[0061] Formal description of simulation entities, which are described by common attributes, responsibility area sets, attribute sets, route sets, and entity behavior sets. The attribute set gives specific parameters of the simulation entity, which is different from the common description fields of the simulation entity. The common description fields of the simulation entity include: simulation entity number, Chinese name and English name, enemy and friend attributes, mobile attributes, military standard library name and military standard code, longitude, latitude and elevation, parent simulation entity number, model entity number.

[0062] The simulation entity route is formally described. The common attributes of the simulation entity route include four fields: route name, route number, route description, and military standard number. The route name is used to display and enhance the readability of the file; the route number is used to distinguish the routes within the simulation entity. Each route consists of a sequence of waypoints, and each waypoint is described by the waypoint type, geographic coordinates, altitude, time, speed, and turn slope.

[0063] The simulation behavior is formally described. Each behavior description includes the behavior name, start time, end time, comments, and behavior parameters related to the behavior, the behavior object entity, the environmental elements where the behavior occurs, and the route associated with the behavior. The associated route gives the route that is executed synchronously with the current behavior. The route is described by the route name and route number. The description method of the behavior parameter set is consistent with the description method of the simulation entity attribute set. The behavior object entity set consists of the behavior objects of the current behavior. Each behavior object is described by the simulation entity name and simulation entity number.

[0064] Step 204: parse the formal description file to obtain the simulation entity and the formal description of the simulation entity.

[0065] Initialize and assign values ​​to the simulation entity, parse the formal description file in XML format, and obtain the simulation entity and the formal description of the simulation entity.

[0066] The simulation entity is described by common attributes, responsibility area set, attribute set, route set and entity behavior set. The attribute set gives the specific parameters of the simulation entity, which is different from the common description field of the simulation entity. The common description field of the simulation entity includes: simulation entity number, Chinese name and English name, enemy attribute, mobile attribute, military standard library name and military standard code, longitude, latitude and elevation, parent simulation entity number, model entity number.

[0067] Step 206: If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field, and the simulation entity is initialized and assigned a value.

[0068] From the perspective of data management, XML data can be regarded as semi-structured data with a hierarchical structure. Intelligent warfare is a system based on a kill network, which is a hyper-dimensional and disordered system based on network interconnection. There is an inherent mismatch between hierarchical semi-structured XML data and hyper-dimensional and disordered network system data. When using XML data to store network system data (including assumption data), we must first establish a storage model for the network system data. This leads to the problem of data mapping between two heterogeneous data models, that is, how to map network system data to XML data, especially how to map the interconnection relationship of network system data to XML data relationship.

[0069] In this regard, initializing and assigning values ​​to the simulation entity specifically includes parsing the formal description file of the simulation assumption, placing the parsed initialization data into a pre-constructed assumption data storage structure, constructing a replication function template library containing a mapping relationship between the initialization data and the attributes of the simulation object, reading the simulation object model description file, searching for the initialization data of the simulation object from the assumption data storage structure according to the assignment function template library, and initializing and assigning values ​​to the simulation object.

[0070] By storing the formal description file of the simulation scenario in the scenario data storage structure, and by building an assignment function template library, a mapping relationship between the scenario data and the attributes of the simulation object is established, the stored data is matched with the simulation system initialization variables, and the simulation object initialization code can be automatically generated to complete the automatic assignment of initial values ​​to the simulation object initialization variables, thereby avoiding manual search for initialization variables and writing simulation system initialization code, improving the development efficiency of the simulation system, reducing manual participation and the error rate caused by manual operation, and realizing automatic initialization.

[0071] In actual applications, there are complex network link relationships between simulation entities. In this embodiment, for complex network link relationships, an entity reference relationship field is used to identify such complex network link relationships. If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value.

[0072] The above-mentioned intelligent combat simulation method parses the formal description file of the simulation scenario, and the entity reference relationship field is used to mark the link relationship between entities. When the formal description of the simulation entity includes the entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to the related entity according to the reference relationship field, and the simulation entity is initialized and assigned. By using the entity reference relationship field to identify this complex network link relationship, when the simulation is initialized, the simulation entity can be referenced to the related entity according to the reference relationship field, and the network link relationship between entities can be straightened out, thereby improving the accuracy of initialization and the simulation effect.

[0073] In another embodiment, the entity reference relationship field includes an entity sibling relationship field, and the method further includes: obtaining the sibling relationship entity of the simulation entity according to the entity sibling relationship field; searching the entity sibling relationship field of the sibling relationship entity to verify whether the two are sibling relationship entities to each other; if so, when the simulation system is automatically initialized, the simulation entity is referenced to the related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value.

[0074] The entity sibling relationship field identifies the entity sibling relationship of the simulation entity.

[0075] Specifically, in intelligent combat simulation, there may be an adjacency and collaboration relationship between two entities. For example, when two companies belonging to the same battalion fight in the same area, their deployment positions are not only adjacent, but also need to collaborate during the combat process. However, this relationship is not expressed in the formal representation of simulation entities.

[0076] In this embodiment, when there is an adjacency or collaboration relationship between entities, the general description field of the simulation entity formalization needs to add a field describing the entity sibling relationship, which can be used to describe other entities that have an adjacency or collaboration relationship with the entity. For example, when multiple companies belonging to the same battalion are fighting in the same area, their deployment positions are adjacent, and they also need to collaborate during the combat. When a company in the battalion is fighting, it can obtain relevant information of other companies by using the IDs of other companies described by the entity sibling relationship, and then cooperate with other companies to jointly complete the combat missions delivered by the battalion.

[0077] In another embodiment, the entity reference relationship field includes a common entity field, and the method further includes: determining the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the belonging relationship of the simulation entity; searching whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity according to the formal description of the simulation entity; if they are the same, then when the simulation system is automatically initialized, the fields of the simulation entity that reference the related entity are referenced by the reference relationship field, and the simulation entity is initialized and assigned a value.

[0078] The common entity field is used to identify entities that share the entity attributes. There is a superior-subordinate relationship between the independent simulation entity and the subordinate simulation entity, and the subordinate simulation entity is subordinate to the independent simulation entity. The independent simulation entity has the highest authority and the largest scope. When the attributes of an entity are shared by a group of specific entities, the entities that share and have a lower-level relationship are the independent simulation entity and the subordinate simulation entity. In intelligent combat simulation, some entities have a kind of data, and the attribute is commonly referenced by multiple other entities, that is, the attribute of the entity is shared by a group of specific entities. For example, a brigade-level unit includes a brigade command post and multiple battalion-level units. When the brigade is engaged in combat, the brigade command post and multiple battalion-level units are deployed together in a combat area. After the combat area of ​​the brigade command post is set, the battalion-level unit only needs to reference the combat area attributes of the brigade command post, and no additional settings are required. Otherwise, there will be inconsistency in the combat area attributes of the brigade command post and the battalion-level units.

[0079] When the attributes of an entity are jointly owned by a group of specific entities, it is necessary to add a common entity field to the formal description of the simulation entity attributes. Other entities can achieve common ownership of the simulation entity attributes by referencing the fields of the common entity. For example, the combat area is a common entity field, the brigade command post is an independent simulation entity, and the battalion command post is its subordinate simulation entity. When the brigade command post and multiple battalion-level units are deployed together in a combat area, after setting the combat area of ​​the brigade command post and its ownership attributes (i.e., combat area attributes), the battalion-level units need to own the combat area attributes of the brigade command post, and do not need to set the combat area, thereby ensuring the consistency of the combat area attributes of the brigade command post and the battalion-level units. Figure 3 shown.

[0080] When the simulation is initialized, since the independent simulation entity and the subordinate simulation entity have common entity fields, it is necessary to verify whether the referenced entity fields between the two are the same based on the common entity fields. If they are the same, initialization is performed.

[0081] In another embodiment, the entity relationship field includes an aggregated virtual entity relationship field; when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: according to the aggregated virtual entity relationship field, obtaining all entities referenced by the aggregated virtual entity; initializing and assigning a value to the simulation entity according to the parameters of all entities referenced by the aggregated virtual entity.

[0082] Specifically, in intelligent combat simulation, there is an entity that is not a real entity, but is composed of a group of closely related entities. For example, in the command chain formed by the command post, each level of the command post is equipped with communication equipment, and these communication equipment together constitute a communication entity. When the superior command post sends a command to the subordinate command post, the communication entity first determines whether the communication connection between the superior command post and the subordinate command post can be correctly established. When the communication connection can be correctly established, the superior command post can send a command to the subordinate command post. Otherwise, the superior command post cannot send a command to the subordinate command post, and the command sending fails.

[0083] When an entity is composed of a group of closely related entities and is not a real entity, it is necessary to add a virtual entity to the formal description of the simulation entity. This entity describes the composition of the entity and references other equipment to form an aggregated virtual entity. During initialization, all entities referenced by the aggregated virtual entity are obtained according to the aggregated virtual entity relationship field; the simulation entity is initialized and assigned according to the parameters of all entities referenced by the aggregated virtual entity.

[0084] Among them, the aggregated virtual entity relationship field includes the aggregated communication simulation entity field; according to the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained, including: according to the aggregated communication simulation entity field, the communication equipment of command posts at all levels referenced by the simulation communication entity is obtained. For example, in the command chain formed by the command post, the communication equipment together constitutes a simulation communication entity. The simulation communication entity needs to reference the communication equipment of command posts at all levels, and use these communication equipment parameters to determine the communication connection problems between command posts. When the superior command post sends a command to the subordinate command post, the simulation communication entity first determines whether the communication connection between the superior command post and the subordinate command post can be correctly established. When the communication connection can be correctly established, the superior command post can send commands to the subordinate command post. Otherwise, the superior command post cannot send commands to the subordinate command post this time. Figure 4 shown.

[0085] In another embodiment. The entity relationship field includes a selected reference entity field, and the reference entity field is selected from a plurality of candidate options. In this embodiment, the entity referenced by the simulation entity can be selected from a plurality of candidate options. When the constituent entities of the entity are variable, that is, the referenced entity is variable, it is necessary to add an optional field describing the reference entity of the entity in the formal description of the simulation entity, and by setting the optional field of the reference entity, the optional change of the entity to the reference entity is realized.

[0086] Specifically, in intelligent combat simulation, facing different combat tasks and different combat objectives, command posts at all levels will adopt different command methods, such as step-by-step command, leapfrog command, succession command and other modes. When the command link is unobstructed, command posts at all levels can adopt the step-by-step command mode; when encountering an emergency or the command link is interrupted, the leapfrog command mode can be adopted; when the superior command post is damaged, in order to continue the combat command, the subordinate command post will adopt the succession command mode to complete the command of the operation. In the above case, each command post entity will have a complex link relationship with other command post entities, and one command post entity will reference multiple command post entities, including multiple layers of superior and subordinate command post entities.

[0087] To this end, further, when the simulation system is automatically initialized, the simulation entity references the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: when the simulation system is automatically initialized, the command posts at all levels establish a command relationship with the entities of other command posts according to the selected command method, and initialize and assign a value to the simulation command post entity. For example, for different combat tasks and combat objectives, command posts at all levels will adopt different command methods, such as step-by-step command, leapfrogging command, succession command, etc., so that the superior command posts and subordinate command posts of command posts at all levels will be different under different command modes. Therefore, each command post entity will establish a command relationship with other command post entities according to the reference entity field of the entity, and correctly realize the command link relationship under different command modes.

[0088] Based on the above method, a new scenario specification for intelligent combat simulation is formed. Figure 5 In the assumption file shown, the virtual simulation entity 41 references the simulation entities numbered 22 and 33 by introducing the IndexSimObject attribute. The simulation entity numbered 40 references the Background attribute of the simulation object 41 by introducing the IndexAttribute composite attribute and setting the values ​​of the attributes SimObj and Name respectively. The test results show that the assumption specification can support applications for intelligent combat simulation by introducing the above-mentioned attribute fields, and helps to realize the automatic generation of simulation entity initialization code. This research has been applied in the design and implementation of a certain type of simulation system, and has achieved good results.

[0089] It should be understood that although Figure 2 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0090] In one embodiment, Figure 6 As shown, an intelligent combat simulation device is provided, comprising:

[0091] The description file acquisition module 502 is used to obtain the formal description file of the intelligent combat simulation scenario.

[0092] The parsing module 504 is used to parse the formal description file to obtain the simulation entity and the formal description of the simulation entity.

[0093] Simulation module 506 is used to initialize and assign values ​​to simulation entities by referencing related entities according to the reference relationship field when the simulation system is automatically initialized if the formal description of the simulation entity includes an entity reference relationship field, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0094] The above-mentioned intelligent combat simulation device parses the formal description file of the simulation scenario, and the entity reference relationship field is used to mark the link relationship between entities. When the formal description of the simulation entity includes the entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to the related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value. By using the entity reference relationship field to identify this complex network link relationship, when the simulation is initialized, the simulation entity can be referenced to the related entity according to the reference relationship field, and the network link relationship between entities can be straightened out, thereby improving the accuracy of initialization and the simulation effect.

[0095] In another embodiment, the entity reference relationship field includes an entity sibling relationship field, and the intelligent combat simulation device further includes:

[0096] The sibling entity acquisition module is used to acquire the sibling relationship entities of the simulation entity according to the entity sibling relationship field.

[0097] The first verification module is used to find the entity sibling relationship field of the sibling relationship entity to verify whether the two entities are sibling relationship entities.

[0098] The simulation module is used to reference the related entity of the simulation entity according to the reference relationship field and initialize the simulation entity when the verification module verifies that the two entities are sibling entities and the simulation system is automatically initialized.

[0099] In another embodiment, the entity reference relationship field includes a common entity field. The intelligent combat simulation device also includes:

[0100] The subordinate determination module is used to determine the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the belonging relationship of the simulation entity.

[0101] The second verification module is used to find out whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity according to the formal description of the simulation entity.

[0102] In another embodiment, the entity relationship field comprises an aggregated virtual entity relationship field.

[0103] Simulation modules, including:

[0104] The entity acquisition module is used to acquire all entities referenced by the aggregated virtual entity according to the aggregated virtual entity relationship field.

[0105] The initialization module is used to initialize and assign values ​​to the simulation entity according to the parameters of all entities referenced by the aggregated virtual entity.

[0106] In another embodiment, the aggregated virtual entity relationship field includes an aggregated communication simulation entity field. The entity acquisition module is used to acquire the communication equipment of command posts at all levels referenced by the simulation communication entity according to the aggregated communication simulation entity field.

[0107] In another embodiment, the entity relationship field includes a selected reference entity field, the reference entity field being selected from a plurality of candidate options.

[0108] In another embodiment, the candidate options of the command mode include: step-by-step command, leapfrogging command and succession command. The simulation module is used to establish command relationships between the command posts at all levels and other command post entities according to the selected command mode when the simulation system is automatically initialized, and initialize the simulation command post entities.

[0109] For the specific definition of the intelligent combat simulation device, please refer to the definition of the intelligent combat simulation method above, which will not be repeated here. Each module in the above-mentioned intelligent combat simulation device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0110] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7As 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, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, an intelligent combat simulation method is implemented. 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 shell, or an external keyboard, touchpad or mouse, etc.

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

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

[0113] Obtain the formal description file of intelligent combat simulation scenario;

[0114] Parse the formal description file to obtain the simulation entity and the formal description of the simulation entity;

[0115] If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0116] In one embodiment, the entity reference relationship field includes an entity sibling relationship field, and the method further includes:

[0117] Get the sibling relationship entity of the simulation entity according to the entity sibling relationship field;

[0118] Find the entity sibling relationship field of the sibling relationship entity to verify whether the two entities are sibling relationship entities;

[0119] If so, when the simulation system is automatically initialized, the simulation entity references the related entity according to the reference relationship field and initializes the simulation entity.

[0120] In another embodiment, the entity reference relationship field includes a common entity field, and the method further includes:

[0121] Determine the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the ownership relationship of the simulation entity;

[0122] According to the formal description of the simulation entity, find out whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity;

[0123] If they are the same, when the simulation system is automatically initialized, the simulation entity is initialized and assigned values ​​according to the fields of the related entities referenced by the simulation entity according to the reference relationship fields.

[0124] In another embodiment, the entity relationship field includes an aggregated virtual entity relationship field; when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including:

[0125] According to the aggregated virtual entity relationship field, obtain all entities referenced by the aggregated virtual entity;

[0126] The simulation entity is initialized and assigned values ​​according to the parameters of all entities referenced by the aggregated virtual entity.

[0127] In another embodiment, the aggregated virtual entity relationship field includes an aggregated communication simulation entity field; based on the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained, including: based on the aggregated communication simulation entity field, communication equipment of command posts at all levels referenced by the simulated communication entity is obtained.

[0128] In another embodiment, the entity relationship field includes a selected reference entity field, the reference entity field being selected from a plurality of candidate options.

[0129] In another embodiment, candidate options for command mode include: step-by-step command, skip-level command and succession command; when the simulation system is automatically initialized, the simulation entity references the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: when the simulation system is automatically initialized, command posts at all levels establish command relationships with entities of other command posts according to the selected command mode, and initialize and assign values ​​to the simulation command post entities.

[0130] 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:

[0131] Obtain the formal description file of intelligent combat simulation scenario;

[0132] Parse the formal description file to obtain the simulation entity and the formal description of the simulation entity;

[0133] If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities.

[0134] In one embodiment, the entity reference relationship field includes an entity sibling relationship field, and the method further includes:

[0135] Get the sibling relationship entity of the simulation entity according to the entity sibling relationship field;

[0136] Find the entity sibling relationship field of the sibling relationship entity to verify whether the two entities are sibling relationship entities;

[0137] If so, when the simulation system is automatically initialized, the simulation entity references the related entity according to the reference relationship field and initializes the simulation entity.

[0138] In another embodiment, the entity reference relationship field includes a common entity field, and the method further includes:

[0139] Determine the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the ownership relationship of the simulation entity;

[0140] According to the formal description of the simulation entity, find out whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity;

[0141] If they are the same, when the simulation system is automatically initialized, the simulation entity is initialized and assigned values ​​according to the fields of the related entities referenced by the simulation entity according to the reference relationship fields.

[0142] In another embodiment, the entity relationship field includes an aggregated virtual entity relationship field; when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including:

[0143] According to the aggregated virtual entity relationship field, obtain all entities referenced by the aggregated virtual entity;

[0144] The simulation entity is initialized and assigned values ​​according to the parameters of all entities referenced by the aggregated virtual entity.

[0145] In another embodiment, the aggregated virtual entity relationship field includes an aggregated communication simulation entity field; based on the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained, including: based on the aggregated communication simulation entity field, communication equipment of command posts at all levels referenced by the simulated communication entity is obtained.

[0146] In another embodiment, the entity relationship field includes a selected reference entity field, the reference entity field being selected from a plurality of candidate options.

[0147] In another embodiment, candidate options for command mode include: step-by-step command, skip-level command and succession command; when the simulation system is automatically initialized, the simulation entity references the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: when the simulation system is automatically initialized, command posts at all levels establish command relationships with entities of other command posts according to the selected command mode, and initialize and assign values ​​to the simulation command post entities.

[0148] Those of ordinary skill 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 memory, storage, database or other media used in the embodiments provided in this 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 or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. 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).

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

[0150] The above-mentioned 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 invention patent. 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 patent of the present application shall be subject to the attached claims.

Claims

1. An intelligent combat simulation method, the method comprising: Obtain the formal description file of intelligent combat simulation scenario; Parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity; If the formal description of the simulation entity includes an entity reference relationship field, when the simulation system is automatically initialized, the simulation entity is referenced to a related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, wherein the entity reference relationship field is used to mark the link relationship between entities; Wherein, the entity reference relationship field includes an entity sibling relationship field, and the method further includes: obtaining the sibling relationship entity of the simulation entity according to the entity sibling relationship field; searching the entity sibling relationship field of the sibling relationship entity to verify whether the two are sibling relationship entities to each other; if so, when the simulation system is automatically initialized, referencing the related entity to the simulation entity according to the reference relationship field, and initializing and assigning a value to the simulation entity; The entity reference relationship field includes a common entity field, and the method further includes: determining the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the belonging relationship of the simulation entity; searching whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity according to the formal description of the simulation entity; if they are the same, then when the simulation system is automatically initialized, the simulation entity is initialized and assigned a value according to the reference relationship field to the field of the related entity referenced by the simulation entity; The entity relationship field includes an aggregated virtual entity relationship field; when the simulation system is automatically initialized, the simulation entity is referenced to related entities according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: according to the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained; according to the parameters of all entities referenced by the aggregated virtual entity, the simulation entity is initialized and assigned a value.

2. The method according to claim 1, characterized in that The aggregated virtual entity relationship field includes an aggregated communication simulation entity field; according to the aggregated virtual entity relationship field, all entities referenced by the aggregated virtual entity are obtained, including: according to the aggregated communication simulation entity field, the communication equipment of command posts at all levels referenced by the simulation communication entity is obtained.

3. The method according to claim 1, characterized in that The entity relationship field includes a selected reference entity field, and the reference entity field is selected from a plurality of candidate options.

4. The method according to claim 3, characterized in that The candidate options for the command mode include: step-by-step command, skip-level command and succession command; when the simulation system is automatically initialized, the simulation entity references the relevant entity according to the reference relationship field, and the simulation entity is initialized and assigned a value, including: when the simulation system is automatically initialized, the command posts at all levels establish command relationships with entities of other command posts according to the selected command mode, and initialize and assign values ​​to the simulation command post entities.

5. An intelligent combat simulation device, characterized in that: The device comprises: A description file acquisition module is used to obtain a formal description file of the intelligent combat simulation scenario; A parsing module, used for parsing the formal description file to obtain a simulation entity and a formal description of the simulation entity; A simulation module, for initializing and assigning values ​​to the simulation entity by referencing the simulation entity to related entities according to the reference relationship field when the simulation system is automatically initialized, if the formal description of the simulation entity includes an entity reference relationship field, wherein the entity reference relationship field is used to mark the link relationship between entities; Wherein, the entity reference relationship field includes an entity sibling relationship field, and the device is further used to obtain the sibling relationship entity of the simulation entity according to the entity sibling relationship field; search the entity sibling relationship field of the sibling relationship entity to verify whether the two are sibling relationship entities; when the verification module verifies that the two are sibling relationship entities, when the simulation system is automatically initialized, the simulation entity is referenced to the related entity according to the reference relationship field, and the simulation entity is initialized and assigned a value; The entity reference relationship field includes a common entity field, and the device is further used to determine the independent simulation entity and the subordinate simulation entity of the main simulation entity according to the belonging relationship of the simulation entity; according to the formal description of the simulation entity, find out whether the common entity field of the subordinate simulation entity is the same as the common entity field of the independent simulation entity; if they are the same, then when the simulation system is automatically initialized, the simulation entity is initialized and assigned a value according to the reference relationship field to the field of the related entity referenced by the simulation entity; The entity relationship field includes an aggregated virtual entity relationship field; the simulation module is also used to obtain all entities referenced by the aggregated virtual entity according to the aggregated virtual entity relationship field; and initialize and assign values ​​to the simulation entity according to the parameters of all entities referenced by the aggregated virtual entity.

6. The device according to claim 5, characterized in that The aggregated virtual entity relationship field includes an aggregated communication simulation entity field; the device also includes an entity acquisition module, and the entity acquisition module is also used to acquire the communication equipment of command posts at all levels referenced by the simulation communication entity based on the aggregated communication simulation entity field.

7. The device according to claim 5, characterized in that The entity relationship field includes a selected reference entity field, where the reference entity field is selected from a plurality of candidate options.

8. The device according to claim 7, characterized in that The candidate options for command mode include: step-by-step command, skip-level command and succession command; the simulation module is also used to establish command relationships with entities of other command posts at all levels according to the selected command mode when the simulation system is automatically initialized, and initialize and assign values ​​to the simulated command post entities.

9. 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 any one of claims 1 to 4 are implemented.

10. 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 any one of claims 1 to 4 are implemented.