A method for processing entity activity data, computer equipment and storage medium

Abstract

The present invention relates to a method for processing entity activity data, a computer device and a storage medium. The present invention reads the verification data area of ​​a UDP message according to the entity data acquisition requirements of a receiving end to identify the entity activity message, reads and parses the entity data area of ​​the entity activity message, and obtains the current entity data of a first entity; calculates the prior fluctuation value and the subsequent fluctuation value based on the current entity data, the prior entity data, and the subsequent entity data; determines the first parameter fluctuation value of the first entity according to the simulation entity attribute information of the first entity and the simulation environment attribute information; when the prior fluctuation value and / or the subsequent fluctuation value are greater than the first parameter fluctuation value, the receiving end is triggered to generate a data abnormality signal. The present invention can quickly acquire and abnormally check entity data, reduce the load, optimize the real-time, reliability and accuracy of entity activity data in the process of accelerating simulation interaction, and improve the accuracy of combat simulation and the effectiveness of decision-making.

Description

Technical Field

[0001] The present invention relates to the field of combat simulation, and in particular to a method for processing entity activity data, a computer device and a storage medium. Background Art

[0002] Combat simulation is a decision support tool that simulates and predicts combat operations through computer simulation technology. It builds a virtual battlefield environment, simulates various combat operations and tactics, evaluates the effectiveness of different strategic and tactical plans, and provides decision support for commanders. It can also simulate the real combat environment and confrontation conditions to examine the commander's on-the-spot analysis and judgment and emergency response capabilities. In combat simulation, a complex battlefield environment is simulated, including factors such as terrain, weather, and electromagnetic environment, as well as the actions of various combat equipment and personnel. It is necessary to transmit a large amount of data in high real-time to update data such as battlefield situation and weapon system status.

[0003] For example, the invention patent application with the patent application publication number CN104317809A discloses a data exchange converter between a command information system and a combat simulation system, which automatically converts various forms of command information into formatted data that can be understood by computers, so that real soldiers can interact with virtual forces in real time through the command information generated by the real-mounted command and control software. At the same time, the combat simulation system feeds back the corresponding command response information to the real-mounted command and control information system, so that commanders can control and command the combat actions of troops in real time in a realistic battlefield environment and rely on the real-mounted command and control system, and achieve command and combat effects close to actual combat. For example, the invention patent application with the patent application publication number CN112052608A discloses an integrated method for combat simulation and effectiveness evaluation, which establishes combat scenarios and capability indicators, conducts combat task analysis and simulation operation, completes effectiveness analysis and evaluation of simulation data, and realizes data integration between the combat simulation subsystem and the effectiveness analysis and evaluation subsystem. The combat simulation subsystem sends simulation control messages and simulation data messages to the effectiveness analysis and evaluation subsystem through the data bus. For example, the invention patent application with patent application publication number CN114239228A discloses a performance evaluation method based on modeling and analysis of massive adversarial simulation data. It covers the uncertainty of situation, uncertainty of equipment performance, uncertainty of strategy, diversity of environment and diversity of information through game simulation of massive data to improve the accuracy and confidence of performance evaluation and realize more effective evaluation means in adversarial scenarios.

[0004] The input of massive data will lead to an increase in software load, and a large amount of transmitted data may cause network congestion or instability, which will make it difficult to ensure the accuracy of combat simulation and the effectiveness of decision-making. Summary of the invention

[0005] The main purpose of the present invention is to provide a method for processing entity activity data, a computer device and a storage medium. By performing multi-level low-sensitivity associated data collaborative verification on entity activity data stored in serialized fields and transmitted in differentiated partitions, the accuracy of entity activity data in the process of accelerating simulation interaction is optimized while taking into account load balancing.

[0006] In order to solve the above-mentioned technical problems, the present invention specifically adopts the following technical solutions:

[0007] A first aspect of the present invention is to provide a method for processing entity activity data, the method comprising:

[0008] S101 reads a verification data area of ​​a UDP message according to a physical data acquisition requirement of a receiving end, wherein the UDP message includes a verification data area and a physical data area, and the verification data area is generated based on message feature information preset by the receiving end;

[0009] S102: identifying whether the UDP message is an entity activity message according to the message characteristic information, and when the UDP message is the entity activity message, reading and parsing the entity data area to obtain current entity data of the first entity;

[0010] S103: obtaining the previous entity data and the subsequent entity data corresponding to the first entity within a preset time period, and respectively calculating the previous fluctuation value between the previous entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data;

[0011] S104: Analyze the simulation entity attribute information of the first entity and the simulation environment attribute information of the first entity to obtain the parameter fluctuation capability of the first entity; determine the first parameter fluctuation value of the first entity according to the parameter fluctuation capability of the first entity;

[0012] S105: When the prior fluctuation value and / or the subsequent fluctuation value is greater than the first parameter fluctuation value, trigger the receiving end to generate a data anomaly signal.

[0013] In some embodiments, the message feature information in the verification data area includes: software configuration information and data type information; the entity data area includes: at least one field group independently stored for recording the value of a specific operating state of the corresponding entity during combat, and the specific operating state is described by at least one indicator; correspondingly, the step of reading and parsing the entity data area includes: reading at least one of the field groups corresponding to the specific operating state pointed to by the entity data acquisition requirement; the receiving end adopts the set field definition rules to parse the field group and the storage location of the field to obtain the current entity data of the first entity; wherein, the field definition rules are used to describe the mapping relationship between the field and the indicator.

[0014] In some embodiments, the steps are also included: when the prior fluctuation value and / or the subsequent fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value, obtaining current entity data of at least one second entity, and there is a linkage change relationship between the entity data of the first entity and the entity data of the second entity; performing abnormal verification on the current entity data of the first entity according to the current entity data of the at least one second entity, and when the difference between the current entity data of the first entity and the current entity data of the at least one second entity exceeds a preset threshold, triggering the receiving end to generate a data abnormality signal.

[0015] In some embodiments, identifying whether the UDP message is an entity activity message based on the message characteristic information includes: obtaining software configuration information in the verification data area; verifying the software configuration information in the verification data area based on the software configuration information of the receiving end, if the verification fails, the UDP message is not the entity activity message.

[0016] In some embodiments, the identifying whether the UDP message is an entity activity message based on the message characteristic information further includes: obtaining the data type information in the verification data area; identifying the data type information in the verification data area, if the identification fails, the UDP message is not the entity activity message.

[0017] In some embodiments, the steps are also included: based on the field definition rule, determining the name field group in the entity data area for recording the entity name indicator; reading and parsing the name field groups of several received entity activity messages to filter out the entity activity messages updated by the first entity; reading and parsing the entity data area of ​​the entity activity message updated by the first entity to obtain the subsequent entity data of the first entity.

[0018] In some embodiments, the message characteristic information also includes data length information, and the data length information is the sum of the length of the verification data area and the length of the entity data area. The method also includes: reading the UDP message based on the data length information to obtain the verification data area and the entity data area.

[0019] In some embodiments, the data in the verification data area is byte data of an unsigned long integer data type.

[0020] The second aspect of the present invention is to provide a computer device, comprising: the memory for storing a computer program; the processor for executing the computer program and implementing the steps of the method for processing entity activity data as described in any of the above embodiments when executing the computer program.

[0021] The third aspect of the present invention is to provide a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the steps of the method for processing entity activity data as described in any of the above embodiments.

[0022] Beneficial technical effects:

[0023] In order to improve the accuracy of combat simulation and the effectiveness of decision-making, the present invention provides a dual verification mechanism for low-sensitivity evaluation of the fast transmission mode of specific data (such as entity data area). Therefore, in combat scenarios involving massive entity data simulation, the load generated at the interface when massive data is input can be reduced by means of the differential format design of specific data areas, and at the same time, the low-sensitivity dual verification mechanism can be used to quickly verify the massive access data without affecting the computing pressure at the interface.

[0024] In other words, the present invention provides a method for processing entity activity data, which optimizes and accelerates the accuracy of entity activity data in the simulation interaction process while taking load balancing into consideration by performing multi-level low-sensitivity associated data collaborative verification on entity activity data stored in serialized fields and transmitted in differentiated partitions.

[0025] Specifically, multiple interactive terminals of combat simulation pre-customize the message data area according to the characteristic information of the entity activity message, so that the receiving terminal can quickly and accurately obtain the required entity data from a large number of unknown messages, while reducing the software load, improving the processing efficiency of the receiving terminal for the message, thereby improving the interaction speed between the simulation interactive terminals. In addition, for the specific data area of ​​the entity data area, a restrictive transmission format of pure data fields is adopted, which is matched with the verification data area with a specific data type, so that the interface can quickly find the associated pure field data when a large number of messages are influx, and the restrictive transmission format can be used to efficiently download the message to the interface end.

[0026] Furthermore, for the pure field data obtained by the restrictive transmission format, the present invention preferably adopts a double verification mechanism to verify its accuracy and reliability. Specifically, the first-level verification mechanism can be to verify the current entity data based on the previous entity data and the subsequent entity data of the same entity to identify abnormal entity data, thereby improving the real-time, reliability and accuracy of the entity data, and then accurately understanding the entity activities in the combat simulation, improving the combat training effect, decision-making quality, and accuracy of combat operations.

[0027] At the same time, the message feature information in the verification data area includes: software configuration information and data type information. According to the software configuration information and data type information, the entity activity message can be quickly and accurately identified, and the data serialization of the combat simulation information is realized. The combat information is transmitted with less data volume to meet the transmission requirements of massive data, shorten the length of the transmitted message, and realize the comprehensive and extremely simple transmission of combat simulation information. It can effectively improve the transmission speed between simulation interaction ends, reduce the risk of network congestion, and improve the confidentiality of sensitive information in the combat simulation scene during the transmission process. At the same time, based on the data serialization of combat simulation information, the receiving end can quickly locate and read the corresponding entity data when it needs to obtain a certain operating state or a certain indicator. It can read the required data from a large number of related messages without processing all the message data, while reducing the software load and improving the real-time performance of the entity data.

[0028] Furthermore, the current entity data is verified based on the previous entity data and the subsequent entity data of the same entity to perform vertical verification on the entity data and identify abnormal entity data. On this basis, the entity data suspected of being abnormal is secondarily verified, and the accuracy of the current data is determined based on the synchronization of the first entity data and the second entity data associated at the same time to achieve horizontal verification. Multi-level verification can effectively avoid excessive sensitivity in identifying abnormal entity data, while improving the reliability and accuracy of entity data. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, each element or part is not necessarily drawn according to the actual scale. Obviously, the drawings described below are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without paying creative labor.

[0030] Figure 1 is a schematic flow chart of a method for processing entity activity data provided by an embodiment of the present invention;

[0031] Figure 2 It is a schematic diagram of a message data partition provided by an embodiment of the present invention;

[0032] Figure 3 is a schematic flow chart of identifying entity activity messages provided by an embodiment of the present invention;

[0033] Figure 4 This is a data storage schematic diagram of a physical data area provided by an embodiment of the present invention;

[0034] Figure 5 is a schematic flow chart of another method for processing entity activity data provided by an embodiment of the present invention;

[0035] Figure 6 A schematic block diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0037] Herein, suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present invention, and have no specific meanings by themselves. Therefore, "module", "component" or "unit" can be used mixedly.

[0038] In this document, the directions or positional relationships indicated by the terms "upper", "lower", "inner", "outer", "front", "rear", "one end", "the other end", etc. are based on the directions or positional relationships shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific direction, be constructed and operate in a specific direction, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance.

[0039] In this document, unless otherwise clearly specified and limited, the terms "installed", "provided with", "connected", etc. should be understood in a broad sense. For example, "connected" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection, a direct connection, or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0040] Herein "and / or" includes any and all combinations of one or more of the associated listed items.

[0041] Herein, "plurality" means two or more than two, ie, it includes two, three, four, five, etc.

[0042] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0043] Combat simulation is a decision support tool that simulates and predicts combat operations through computer simulation technology. It can not only help commanders predict the results of different tactical plans, but also examine commanders' on-the-spot analysis, judgment and emergency response capabilities by simulating real combat environments and confrontation conditions. This kind of simulation training is crucial to improving commanders' decision-making quality and their ability to deal with complex battlefield situations.

[0044] In order to achieve a high degree of authenticity, it is necessary to simulate a complex battlefield environment, including but not limited to the ups and downs of the terrain, the impact of weather changes on combat operations, and the interference of the electromagnetic environment on communication and radar systems. In addition, it is also necessary to simulate the actions of various combat equipment, such as tanks, aircraft, ships, etc., as well as the actions of personnel, such as infantry and special forces. In order to achieve these simulations, a large amount of data needs to be transmitted in real time to achieve real-time updates of battlefield situations, status monitoring of weapon systems, simulation of enemy actions, etc. The real-time transmission of these data is crucial to the accuracy of combat simulations, because they can provide commanders with the latest battlefield information and help them make timely decisions.

[0045] Real-time processing of massive amounts of data will increase software load, which may affect the response speed and stability of the system. Secondly, large amounts of data transmission may cause network congestion or instability. Such network problems may cause data transmission delays or loss, or disorder, which will seriously affect the accuracy of combat simulation.

[0046] Therefore, the real-time processing of massive data has put forward many high requirements on software load and network quality, such as requiring the software to have efficient data processing capabilities, which includes fast reading, writing, analysis and storage of data. However, the improvement of hardware resources is often accompanied by extremely high costs. For example, high-performance hardware devices are usually expensive, and as the performance of hardware devices improves, their energy consumption will also increase accordingly.

[0047] In a combat simulation environment that requires high real-time, reliability and accuracy, these technical challenges must be addressed. Therefore, the present invention proposes a more efficient method for processing entity activity data, which can achieve combat action simulation and prediction in a more cost-effective manner based on improving the efficiency and accuracy of entity data processing.

[0048] In this regard, the present invention provides a dual verification mechanism for low-sensitivity evaluation of the fast transmission mode of specific data (such as physical data area). Therefore, in combat scenarios involving massive physical data simulation, the load generated at the interface when massive data is input can be reduced by means of the differential format design of specific data areas, and at the same time, the low-sensitivity dual verification mechanism can be used to quickly verify the massive access data without affecting the computing pressure at the interface.

[0049] The multiple interactive terminals of the combat simulation in the present invention pre-customize the message data area according to the characteristic information of the entity activity message, so that the receiving terminal can quickly and accurately obtain the required entity data from a large number of unknown messages, and then verify the current entity data according to the previous entity data and the subsequent entity data of the same entity, so as to verify the entity data vertically and identify abnormal entity data, while reducing the software load, improving the processing efficiency of the receiving terminal for the message and the interaction speed between the simulation interactive terminals, achieving a high degree of real-time, reliability and accuracy of the entity data, thereby improving the accuracy of the combat simulation and the effectiveness of the decision. The present invention can quickly obtain and check the entity data for abnormalities, while reducing the software load, improving the real-time, reliability and accuracy of the entity data, thereby improving the accuracy of the combat simulation and the effectiveness of the decision.

[0050] The entity activity message is a message that records combat simulation information. By parsing the entity data area of ​​the entity activity message, the entity data of a certain entity currently updated in the combat simulation can be obtained.

[0051] In combat simulation, entities refer to the various elements involved in the simulation. They can be fixed entities, such as environmental entities such as roads, bridges, basin terrain, command posts, radar stations, etc. on the ground, or moving entities, such as combat activity entities such as soldiers, tanks, aircraft, ships, etc., which can move and perform various actions in the simulation environment. These entities have specific properties and behaviors in the simulation environment, and can interact according to preset rules and algorithms, thereby simulating a combat scenario close to reality.

[0052] Correspondingly, the entity data in the present invention includes the static attributes and dynamic behaviors of the entity. It should be understood that the static attributes include data descriptions that describe the entity itself and its attributes, such as location positioning and bullet inventory; dynamic behaviors include data descriptions that simulate actions in the real world, such as tank movement direction, radar interference, missile attacks, etc.

[0053] Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. The following embodiments and features of the embodiments can be combined with each other without conflict. Figure 1 , Figure 1 FIG. 1 is a schematic flow chart of a method for processing entity activity data provided by an embodiment of the present invention. Figure 1 As shown, the method for processing entity activity data may include steps S101 to S105.

[0054] S101 reads the verification data area of ​​the UDP message according to the entity data acquisition requirement of the receiving end, the UDP message includes a verification data area and an entity data area, and the verification data area is generated based on the message feature information preset by the receiving end.

[0055] Among them, the entity data acquisition requirement refers to the need for any simulation interaction end to obtain data corresponding to the static attributes and dynamic behaviors of an entity during the combat simulation process. It should be understood that commanders need to obtain entity data to understand the battlefield situation and weapon system status in order to make accurate and effective decisions.

[0056] Among them, the message characteristic information is determined in advance by multiple interactive terminals based on the common attributes of the entity activity messages and / or multiple interactive terminals. For example, the entity activity messages in this combat simulation will all transmit an identity authentication stamp, which is the common attribute of the entity activity messages. The digital string corresponding to the identity authentication stamp can be used as the message characteristic information.

[0057] In some embodiments, the message feature information in the verification data area includes: software configuration information and data type information. Among them, software configuration information refers to the software attributes configured by the simulation interaction terminal, including software version information and protocol version information; data type information refers to the data type of the data transmitted in the entity activity message. IDs can be defined for different data types in advance, and the IDs can be transmitted as data of the data type information to realize the minimization of verification data, which can effectively reduce the impact on the amount of entity data transmitted.

[0058] It should be noted that the User Datagram Protocol (UDP) is a connectionless, datagram-transmitted transport layer protocol that plays an important role in realizing data interaction. Its high efficiency, low latency, and broadcast capabilities can provide timely transmission, fast updates, and responses to entity data. The UDP message includes a UDP header area and a UDP data area, wherein the UDP header area contains control information for network transmission, and the UDP data area contains the actual application layer data to be transmitted, such as the entity activity data in the present invention.

[0059] In some embodiments, the UDP data area is split into a verification data area and an entity data area. The verification data area is used to enable the receiving end to quickly and accurately identify the entity activity message from a large number of unknown messages, and the entity data area is used to record the actual combat simulation information to be transmitted. By personalizing the message data area and transmitting the entity activity data with a differentiated partitioning strategy, it is possible to quickly verify and identify the entity activity message while transmitting the combat simulation information, thereby improving the efficiency of obtaining the entity data and thus improving the real-time nature of the entity data.

[0060] In some embodiments, the message characteristic information also includes data length information, and the data length information is the sum of the length of the verification data area and the length of the entity data area. The method includes: reading the UDP message based on the data length information to obtain the verification data area and the entity data area.

[0061] Specifically, according to the data length information, the verification data area and the entity data area can be accurately read from the UDP message, which can effectively prevent the reading of out-of-bounds when reading information, improve the data reading speed and accuracy, and thus improve the recognition efficiency of entity activity messages and the efficiency of obtaining entity data, improve the processing efficiency of the receiving end for messages and the interaction speed between the simulation interaction ends, so as to improve the real-time nature of entity data. It should be noted that the data length information does not include the length of the UDP header area.

[0062] See also Figure 2 , Figure 2 It is a schematic diagram of a message data partition provided by an embodiment of the present invention. The UDP message includes a UDP header area, a check data area, and an entity data area, wherein the check data area includes software configuration information, data type information, and data length information.

[0063] In some embodiments, the verification data area in the UDP data area is set before the entity data area. When receiving the message, the receiving end can preferentially obtain the data in the verification data area to advance the verification process and reduce the software resources consumed by the receiving end to process non-entity activity messages.

[0064] In some embodiments, the data in the verification data area is byte data of an unsigned long integer data type to reduce the number of bytes occupied by the verification data area, and the remaining bytes that the message can carry can be used to store entity data corresponding to the combat simulation information.

[0065] Exemplarily, the message header area occupies 8 bytes, the check data area occupies 12 bytes in total, the software configuration information, data type information, and data length information each occupy 4 bytes, and the software version information and protocol version information in the software configuration information each occupy 2 bytes. Since UDP has a maximum load of 64KB, after removing the above 20 bytes, the remaining part can be used to transmit combat simulation information. It should be understood that based on the rapid verification and identification of entity activity messages, the number of bytes occupied by the check data area is reduced, which can effectively reduce the impact on the amount of entity data transmitted.

[0066] S102 identifies whether the UDP message is an entity activity message according to the message characteristic information, and when the UDP message is the entity activity message, reads and parses the entity data area to obtain current entity data of the first entity.

[0067] Specifically, the receiving end reads the verification data area of ​​the received message, and uses the message feature information to verify the read data content. If the verification passes, the UDP message currently being processed is identified as an entity activity message. If the verification fails, the UDP message currently being processed is identified as not an entity activity message. The entity data area of ​​the entity activity message is read and parsed to obtain the current entity data of the first entity.

[0068] Exemplarily, when the message characteristic information is a digital string corresponding to the identity authentication stamp, the verification data area of ​​the received message is read to verify whether the read data content contains the corresponding digital string to determine whether the currently processed UDP message is an entity activity message. The verification process is pre-placed. When it is determined to be an entity activity message, the entity data area is read and parsed to obtain the current entity data of the first entity. This can effectively avoid the waste of software resources, reduce software load, and speed up the processing efficiency of the message at the receiving end.

[0069] In some embodiments, identifying whether the UDP message is an entity activity message based on the message characteristic information includes: obtaining software configuration information in the verification data area; verifying the software configuration information in the verification data area based on the software configuration information of the receiving end, if the verification fails, the UDP message is not the entity activity message.

[0070] Specifically, when the receiving end receives a message, the software configuration information in the message verification data area is verified based on the software configuration information predetermined by the receiving end. If the software configuration information does not match, the verification fails and no processing is performed on the message.

[0071] Exemplarily, the software configuration information is predetermined based on the common attributes of multiple interactive terminals. When the software configuration information of the message sending terminal is adapted to the software configuration information of the receiving terminal, the receiving terminal has more advantages in processing and obtaining the entity data of the message sending terminal. Flexible use of the common attributes to verify the message can effectively improve the accuracy of the receiving terminal in obtaining the entity data.

[0072] In some embodiments, the identifying whether the UDP message is an entity activity message based on the message characteristic information further includes: obtaining the data type information in the verification data area; identifying the data type information in the verification data area, if the identification fails, the UDP message is not the entity activity message.

[0073] Specifically, when the receiving end receives a message, the receiving end identifies the data type information in the message verification data area to determine whether the receiving end has the ability to process data messages of the data type. If not, the identification fails.

[0074] Exemplarily, the data type information is predetermined based on the common attributes of the entity activity message, and IDs are defined for different data types in advance, and the IDs are transmitted as data of the data type information. The receiving end identifies the data type ID in the message verification data area based on the internally stored processable data type IDs. If there is an unrecognizable ID, an exception is thrown to confirm that the UDP message is not an entity activity message; if the IDs are all recognizable, the identification is successful, confirming that the UDP message is an entity activity message, triggering the function body corresponding to the parsing data type ID, and performing special parsing on the entity activity message. The common attributes are flexibly used to verify the message, which can effectively improve the accuracy of the receiving end in obtaining entity data, and realize the rapid call of the corresponding function body to process the message, thereby improving the processing efficiency of the message on the receiving end.

[0075] In some embodiments, after confirming that the UDP message is an entity activity message according to the data type information, subsequent processing of the message can be performed through a callback function.

[0076] See also Figure 3 , Figure 3 FIG. 1 is a schematic flow chart of an embodiment of the present invention for identifying entity activity messages. Figure 3 As shown, the software configuration information in the verification data area is verified based on the software configuration information of the receiving end. After the verification is passed, the data type information in the verification data area is identified. If the identification is successful, the UDP message is confirmed to be an entity activity message. At the same time, if the verification fails or the identification fails, it will be confirmed that the UDP message is not an entity activity message. The UDP message is verified multiple times through the software configuration information and data type information, and the adapted interactive end is quickly screened out. At the same time, the corresponding function body is quickly called to process the message, which improves the accuracy and real-time performance of obtaining entity data.

[0077] In some embodiments, in order to realize serialized field storage of entity activity data, the entity data area includes: at least one field group independently stored for recording the value of the specific operating state of the corresponding entity during the combat process, and the specific operating state is described by at least one indicator; correspondingly, the step of reading and parsing the entity data area includes: reading at least one of the field groups corresponding to the specific operating state pointed to by the entity data acquisition requirement; the receiving end adopts the set field definition rules to parse the field group and the storage location of the field to obtain the current entity data of the first entity; wherein, the field definition rules are used to describe the mapping relationship between the field and the indicator.

[0078] Among them, combat simulation information is reflected in the specific operating states of several entities during the combat process. Different operating states can be described by different indicators, and the values ​​of these indicators represent the values ​​of the entities in specific states. In order to efficiently transmit these data, these values ​​are stored in corresponding fields according to predefined field definition rules, thereby forming at least one independently stored field group in the entity data area. The specific operating state and the indicators used can be determined according to actual needs and are not limited here.

[0079] For example, the specific operating state is the moving state of the entity, and the corresponding indicators may be the latitude and longitude, posture, speed, etc. of the entity. The numerical value reflecting the longitude and latitude indicators may be the longitude and latitude values; the numerical value reflecting the posture indicator may be the pitch angle value, the roll angle value, and the yaw angle value; the numerical value reflecting the speed indicator may be the speed value and the acceleration value. Furthermore, the values ​​of the specific operating state include the longitude and latitude values, the pitch angle value, the roll angle value, the yaw angle value, the speed value, the acceleration value, etc.

[0080] In some embodiments, the mapping relationship between the field and the indicator can be determined according to the corresponding relationship between the data type of the indicator value and the field, see Figure 4 , Figure 4 is a schematic diagram of data storage in a physical data area provided by an embodiment of the present invention, such as Figure 4 As shown in the figure, the interaction ends specify the name and data type for each field according to the pre-defined field definition rules, thus forming the format of the entity data area, such as the names key1, key2, key3, etc.; define the data type of each key, such as string, int, float, etc.; set the value "Value" corresponding to the data type of each name, for example, the data type of the name key1 is "string", and the corresponding value is "Value:16". The sending end follows these rules to process the combat simulation information and generate message transmission data containing only numerical values. These data do not contain any data type information and are finally stored in the entity data area.

[0081] In some embodiments, all indicator values ​​of an indicator are stored in the same field group, and the values ​​are sorted in the same field group according to the following formula: Figure 4 The format of the entity data area shown stores indicator values ​​separately to achieve independent storage of each indicator and independent storage of each indicator value. While transmitting combat information with a smaller amount of data to meet the transmission needs of massive data, it improves the efficiency of obtaining entity data.

[0082] That is to say, this embodiment adopts a restrictive transmission mode for the specific area of ​​entity data to complete the efficient access and download process of entity data. And the use of this specific restrictive transmission mode combined with a low-sensitivity double verification mechanism can ensure that the received data has high reliability on the basis of significantly reducing the content of the transmitted data (specifically, only the fields describing the numerical values ​​can be transmitted, avoiding the synchronous transmission of specific operating states and indicator types), that is, the double verification mechanism can quickly identify data anomalies that may occur under pure word transmission.

[0083] Therefore, data with high abnormal fluctuations can be acquired for a second time. In addition, due to the combination of restrictive transmission mode and low-sensitivity double verification mechanism, it can limit the frequency of message errors to a certain extent and control the communication resources consumed by secondary transmission, which makes the resources consumed by this abnormal feedback mechanism relatively controllable and easier to implement in the application process.

[0084] Moreover, the low-sensitivity double verification mechanism proposed by the present invention is also easier to cooperate with the simulation system. That is, the present invention divides the filtering process (or exception handling) of entity data into two major stages: 1) the receiving end performs secondary transmission of highly abnormal data; 2) the abnormal data that may exist after the filtering process is coordinated with the help of the filtering process in the simulation process (such as using the simulation algorithm to smooth the abnormal data). Therefore, although the double verification mechanism of the present invention limits the sensitivity of the error report to a certain extent, by splitting the exception handling tasks, the double verification mechanism can ensure the effectiveness and reliability of the final simulation process without generating excessive transmission load in the process of coordinating with the simulation system (the first filtering process at the receiving end can reduce the exception handling pressure of the simulation algorithm).

[0085] Specifically, according to the entity data acquisition requirements, the specific operating state it points to is determined, and at least one field group storing the indicator value of the specific operating state is read. The receiving end parses the value stored in the field group according to the storage location of the field group and the field and the data type and name of the location in the field definition rule to obtain the current entity data of the first entity.

[0086] Exemplarily, the entity data acquisition requirement points to a specific operating state of speed, reads the field group storing the numerical value of the speed indicator, and parses the numerical value stored in the field group according to the data type and name of the position corresponding to the field group and the field definition rules to obtain the speed of the first entity.

[0087] It should be understood that the field definition rules realize the data serialization of combat simulation information. When transmitting the entity data area, only the data value needs to be transmitted without transmitting the data type. The combat information is transmitted with a smaller amount of data to meet the transmission needs of massive data, shorten the length of the transmitted message, and realize the comprehensive and minimalist transmission of combat simulation information. It can effectively improve the transmission speed between simulation interaction ends, reduce the risk of network congestion, and at the same time improve the confidentiality of sensitive information in combat simulation scenarios during transmission.

[0088] Furthermore, based on the data serialization of combat simulation information, when the receiving end needs to obtain a specific operating state or a certain indicator, it can quickly locate and read the corresponding entity data, and can read the required data from a large number of related messages without processing all message data, thereby reducing the software load and improving the real-time performance of entity data. For example, when the interactive end needs to quickly generate the location distribution and movement trajectory of multiple entities, and the 4th to 6th fields are defined as double data recording longitude and latitude in the field definition rules, the above three fields can be read specifically and quickly parsed according to the field definition rules.

[0089] In some embodiments, the UDP data area is split into a verification data area and an entity data area. Different data transmission methods are used for the two areas according to the functions of the areas and the transmission contents. Since the verification data area contains less data, the data transmission in the verification data area includes the data type and data value. The receiving end can quickly verify the message without parsing it in accordance with the field definition rules. The entity data area contains more data content, and only the data value is transmitted without transmitting the data type, so as to transmit the combat simulation information comprehensively and minimally.

[0090] The message characteristic information in the UDP data area includes: software configuration information and data type information; the entity data area includes: at least one field group for independently storing the value of a specific operating state of the corresponding entity during the combat process, and the specific operating state is described by at least one indicator;

[0091] S103: Acquire the previous entity data and the subsequent entity data corresponding to the first entity within a preset time period, and respectively calculate the previous fluctuation value between the previous entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data.

[0092] Specifically, the prior entity data acquired within a preset period before the current entity data acquisition time is traced back, and the subsequent entity data acquired within a preset period after the current entity data acquisition time is updated to acquire the associated data of the current entity data, and the prior fluctuation value between the prior entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data are calculated respectively to determine the fluctuation of the entity data at that time, so as to collaboratively verify whether the fluctuation of the current entity data is reasonable.

[0093] Exemplarily, when the entity data is location positioning, the prior fluctuation value and the subsequent fluctuation value are determined by calculating the longitude and latitude changes between the prior entity data, the current entity data, and the subsequent entity data, respectively.

[0094] It should be noted that the preset time period can be determined according to time requirements. The shorter the preset time period, the higher the accuracy of subsequent data anomaly verification. The preset time periods corresponding to the prior entity data and the subsequent entity data may be different, which is not limited here.

[0095] In some embodiments, in order to improve the efficiency of acquiring entity data, based on the field definition rule, a name field group for recording entity name indicators in the entity data area is determined; the name field groups of several received entity activity messages are read and parsed to filter out the entity activity messages updated by the first entity; the entity data area of ​​the entity activity message updated by the first entity is read and parsed to obtain the subsequent entity data of the first entity.

[0096] Based on the data serialization of combat simulation information, the previous entity data and the subsequent entity data corresponding to the first entity can be quickly captured. The required data can be read from a large number of related messages without processing all the message data. While reducing the software load, the real-time performance of the entity data is improved.

[0097] S104: Analyze the simulation entity attribute information of the first entity and the simulation environment attribute information of the first entity to obtain the parameter fluctuation capability of the first entity; and determine the first parameter fluctuation value of the first entity according to the parameter fluctuation capability of the first entity.

[0098] Among them, the simulation entity attribute information refers to the information that describes and defines the characteristics and behaviors of the simulation entity, such as the behavioral capabilities of the entity, such as movement speed, field of view distance, equipment configuration, etc. The simulation environment attribute information refers to the characteristic information of the environment in which the entity is located, such as topography, climate conditions, battlefield situation, etc.

[0099] The parameter fluctuation capability is used to characterize the ability of the first entity to change entity data. The stronger the parameter fluctuation capability is per unit time, the larger the range of entity data changes, and the larger the corresponding first parameter fluctuation value.

[0100] The first parameter fluctuation value is determined according to the parameter fluctuation capability of the first entity, and the fluctuation value in the interval greater than the first parameter fluctuation value is a data fluctuation that is difficult to produce even if the first entity continues to exert its maximum parameter fluctuation capability. The first parameter fluctuation value can be the maximum value of a parameter (such as firepower, mobility, defense, etc.) of the first entity in the simulation environment within the normal fluctuation range or appropriately greater than the maximum value, which can be determined according to actual needs and is not limited here.

[0101] Specifically, the environment in which the simulation entity is located will affect the behavioral capabilities of the simulation entity, and the variation range and adaptability of its attribute parameters under different environments and conditions are different. Therefore, analyzing the simulation entity attribute information of the first entity and the attribute information of the simulation environment in which the first entity is located can flexibly determine the parameter fluctuation capability of the first entity in the simulation environment, and then determine the first parameter fluctuation value of the first entity based on the parameter fluctuation capability, which can effectively improve the accuracy of entity data anomaly verification.

[0102] For example, the first entity is a tank, and its parameter fluctuation capabilities may include firepower output, movement speed, and armor protection. By analyzing the performance of the tank in different terrains (such as plains, mountains, and cities) and different climates (such as sunny days, rainy days, and snowy days), its parameter fluctuation values ​​under these conditions can be determined. For example, the road speed of a tank is usually between 50-70km / h, and when the tank travels off-road in the mountains, the speed will drop to 20-30km / h.

[0103] S105: When the prior fluctuation value and / or the subsequent fluctuation value is greater than the first parameter fluctuation value, trigger the receiving end to generate a data anomaly signal.

[0104] Specifically, in order to improve the reliability and accuracy of entity data, when the prior fluctuation value and / or the subsequent fluctuation value is greater than the first parameter fluctuation value, the fluctuation between the current entity data and its adjacent data is too large, and is not a data fluctuation that can be generated by the parameter fluctuation capability of the simulation entity. It may be a data mutation during the calculation or transmission process, which triggers the receiving end to generate a data anomaly signal, thereby improving the accuracy of the entity data.

[0105] For example, when a tank is traveling off-road in mountainous terrain, its speed will drop to 20-30 km / h, and the corresponding first parameter fluctuation value may be 32 km / hour. By calculating the longitude and latitude changes of the prior entity data, the current entity data, and the subsequent entity data, the prior fluctuation value is determined to be 40 km / hour and the subsequent fluctuation value is 38 km / hour, respectively. At this time, the prior fluctuation value and the subsequent fluctuation value are both greater than the first parameter fluctuation value. The current entity data is likely to be a position positioning mutation, triggering the receiving end to generate a data anomaly signal.

[0106] In some embodiments, when the prior fluctuation value and / or the subsequent fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value, current entity data of at least one second entity is obtained, and there is a linkage change relationship between the entity data of the first entity and the entity data of the second entity; the current entity data of the first entity is abnormally verified based on the current entity data of the at least one second entity, and when the difference between the current entity data of the first entity and the current entity data of the at least one second entity exceeds a preset threshold, the receiving end is triggered to generate a data abnormality signal.

[0107] Among them, the second parameter fluctuation value is determined according to the parameter fluctuation ability of the first entity. The fluctuation value in the interval that is less than the first parameter fluctuation value and greater than the second parameter fluctuation value is the data fluctuation that can only be generated when the first entity continues to exert a larger parameter fluctuation ability. The specific interval setting can be determined according to actual needs and is not limited here.

[0108] Specifically, in order to further improve the reliability and accuracy of entity data, abnormal verification is performed on suspected abnormal entity data in the interval less than the first parameter fluctuation value and greater than the second parameter fluctuation value, and the current entity data of at least one second entity is obtained as the associated data of the current entity data. Whether the current entity data is abnormal is collaboratively verified based on whether the data of the first entity data and the second entity data associated at the same time meet the associated relationship. If the difference between the current entity data of the first entity and the current entity data of at least one second entity exceeds a preset threshold, it may be a data mutation during the operation or transmission process, triggering the receiving end to generate a data abnormality signal. The secondary verification of suspected abnormal data can effectively avoid the excessive sensitivity of identifying abnormal entity data, while improving the reliability and accuracy of entity data.

[0109] A linkage change relationship means that the data changes of the first entity and the second entity are synchronized. For example, if the first entity is a tank and the second entity can be the operating soldier inside the tank and the gun carried by the soldier, the position changes of the first entity and the second entity have a linkage change relationship. At this time, the position information of the tank can be verified for abnormality based on the position information of the operating soldier inside the tank.

[0110] See also Figure 5 , Figure 5 is a schematic flow chart of another method for processing entity activity data provided by an embodiment of the present invention; Figure 5 As shown, the method for processing entity activity data may include steps S201 to S205.

[0111] S201 reads a verification data area of ​​a UDP message according to a physical data acquisition requirement of a receiving end, wherein the UDP message includes a verification data area and a physical data area, and the verification data area is generated based on message feature information preset by the receiving end;

[0112] S202: identifying whether the UDP message is an entity activity message according to the message characteristic information, and when the UDP message is the entity activity message, reading and parsing the entity data area to obtain current entity data of the first entity;

[0113] S203: obtaining the previous entity data and the subsequent entity data corresponding to the first entity within a preset time period, and respectively calculating the previous fluctuation value between the previous entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data;

[0114] S204: Analyze the simulation entity attribute information of the first entity and the simulation environment attribute information of the first entity to obtain the parameter fluctuation capability of the first entity; determine the first parameter fluctuation value of the first entity according to the parameter fluctuation capability of the first entity;

[0115] S205: when the prior fluctuation value and / or the subsequent fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value, obtaining current entity data of at least one second entity, the entity data of the first entity and the entity data of the second entity having a linkage change relationship;

[0116] S206 performs anomaly verification on the current entity data of the first entity according to the current entity data of the at least one second entity, and triggers the receiving end to generate a data anomaly signal when the difference between the current entity data of the first entity and the current entity data of the at least one second entity exceeds a preset threshold.

[0117] Specifically, multiple interactive terminals of the combat simulation pre-customize the message data area according to the characteristic information of the entity activity message, so that the receiving end can quickly and accurately obtain the required entity data from a large number of unknown messages, and then verify the current entity data according to the previous entity data and subsequent entity data of the same entity, so as to verify the entity data vertically and identify abnormal entity data. On this basis, the entity data suspected of being abnormal is verified twice, and the accuracy of the current data is determined according to the synchronization of the first entity data and the second entity data associated at the same time, so as to achieve horizontal verification.

[0118] In the process of combat simulation, there is a high degree of interrelationship between entity activities. For example, in the time series, there is continuity between the data of the same entity at different time points. For example, in the spatial and logical level, the data between different entities may affect each other due to a common combat environment or logical relationship. According to the different correlation attributes between entity activity data, collaborative verification can more quickly identify abnormal data, improve the verification speed of a single entity activity data, and provide more comprehensive and in-depth analysis at the level of the entire data set, thereby improving the response speed and accuracy of the entire simulation system.

[0119] Multi-level low-sensitivity verification can effectively avoid excessive sensitivity in identifying abnormal entity data. While taking load balancing into consideration, it can also optimize and accelerate the reliability and accuracy of entity activity data during simulation interaction.

[0120] In some embodiments, the trigger conditions are adjusted according to the sensitivity requirements of the abnormal entity data. When high sensitivity is required, the first parameter fluctuation value and the second parameter fluctuation value can be lowered, or it can be set to trigger the generation of a data abnormality signal when the first fluctuation value or the second fluctuation value is greater than the first parameter fluctuation value. It can also be set to trigger secondary verification when the first fluctuation value or the second fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value. When low sensitivity is required, the first parameter fluctuation value and the second parameter fluctuation value can be increased, or it can be set to trigger the generation of a data abnormality signal when the first fluctuation value and the second fluctuation value are greater than the first parameter fluctuation value. It can also be set to trigger secondary verification when both the first fluctuation value and the second fluctuation value are less than the first parameter fluctuation value and greater than the second parameter fluctuation value.

[0121] In some embodiments, the data anomaly signal can alert the commander to the fact that the accuracy of the entity data is in doubt, and can also be fed back to the data sending end to reacquire the data, thereby improving the accuracy of combat simulation and the effectiveness of decision-making.

[0122] The method for processing entity activity data provided by the embodiment of the present invention can also be used in simulation scenarios where there is a high degree of correlation between entity activities and there is a high demand for real-time transmission of massive entity data, such as traffic simulation, disaster response simulation, etc.

[0123] See also Figure 6 , Figure 6 A schematic block diagram of the structure of a computer device provided by an embodiment of the present invention. The computer device can be any simulation interaction terminal participating in the simulation.

[0124] See also Figure 6 The computer device includes a processor, a memory and a network interface connected through a system bus, wherein the memory may include a non-volatile storage medium and an internal memory.

[0125] The non-volatile storage medium can store an operating system and a computer program. The computer program includes program instructions, and when the program instructions are executed, the processor can execute any method for processing entity activity data.

[0126] The processor is used to provide computing and control capabilities and support the operation of the entire computer equipment.

[0127] The internal memory provides an environment for the operation of the computer program in the non-volatile storage medium. When the computer program is executed by the processor, the processor can execute any method for processing entity activity data.

[0128] The network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present invention, and does not constitute a limitation on the computer device to which the solution of the present invention 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.

[0129] It should be understood that the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0130] In one embodiment, the processor is used to run a computer program stored in the memory to implement the following steps: S101 reads a check data area of ​​a UDP message according to a physical data acquisition requirement of a receiving end, the UDP message includes a check data area and a physical data area, and the check data area is generated based on message feature information preset by the receiving end;

[0131] S102: identifying whether the UDP message is an entity activity message according to the message characteristic information, and when the UDP message is the entity activity message, reading and parsing the entity data area to obtain current entity data of the first entity;

[0132] S103: obtaining the previous entity data and the subsequent entity data corresponding to the first entity within a preset time period, and respectively calculating the previous fluctuation value between the previous entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data;

[0133] S104: Analyze the simulation entity attribute information of the first entity and the simulation environment attribute information of the first entity to obtain the parameter fluctuation capability of the first entity; determine the first parameter fluctuation value of the first entity according to the parameter fluctuation capability of the first entity;

[0134] S105: When the prior fluctuation value and / or the subsequent fluctuation value is greater than the first parameter fluctuation value, trigger the receiving end to generate a data anomaly signal.

[0135] In one embodiment, the message feature information in the verification data area includes: software configuration information and data type information; the entity data area includes: at least one field group for independently storing values ​​of a specific operating state of the corresponding entity during combat, and the specific operating state is described by at least one indicator;

[0136] When implementing the step of reading and parsing the entity data area, the processor is also used to implement: reading at least one of the field groups corresponding to the specific operating state pointed to by the entity data acquisition requirement; the receiving end adopts the set field definition rules to parse the field group and the storage location of the field to obtain the current entity data of the first entity; wherein the field definition rules are used to describe the mapping relationship between the field and the indicator.

[0137] In one embodiment, the processor is also used to implement: when the prior fluctuation value and / or the subsequent fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value, obtaining current entity data of at least one second entity, and there is a linkage change relationship between the entity data of the first entity and the entity data of the second entity; performing abnormal verification on the current entity data of the first entity based on the current entity data of the at least one second entity, and when the difference between the current entity data of the first entity and the current entity data of the at least one second entity exceeds a preset threshold, triggering the receiving end to generate a data abnormality signal.

[0138] In one embodiment, when the processor is implemented to identify whether the UDP message is an entity activity message based on the message feature information, it is also used to implement: obtaining software configuration information in the verification data area; verifying the software configuration information in the verification data area based on the software configuration information of the receiving end, if the verification fails, the UDP message is not the entity activity message.

[0139] In one embodiment, when the processor implements the step of identifying whether the UDP message is an entity activity message according to the message feature information, it is further used to implement:

[0140] In one embodiment, when implemented, the processor is further used to: obtain the data type information in the verification data area; identify the data type information in the verification data area, and if the identification fails, the UDP message is not the entity activity message.

[0141] In one embodiment, the processor is also used to implement: based on the field definition rule, determine the name field group in the entity data area for recording the entity name indicator; read and parse the name field groups of several received entity activity messages to filter out the entity activity messages updated by the first entity; read and parse the entity data area of ​​the entity activity message updated by the first entity to obtain the subsequent entity data of the first entity.

[0142] In one embodiment, the message characteristic information also includes data length information, and the data length information is the sum of the length of the verification data area and the length of the entity data area. The processor is also used to implement: reading the UDP message based on the data length information to obtain the verification data area and the entity data area.

[0143] In one embodiment, the data in the verification data area is byte data of an unsigned long integer data type.

[0144] A computer-readable storage medium is also provided in an embodiment of the present invention. The computer-readable storage medium stores a computer program. The computer program includes program instructions. The processor executes the program instructions to implement any one of the entity activity data processing methods provided in the embodiments of the present invention.

[0145] The computer-readable storage medium may be an internal storage unit of the computer device described in the above embodiment, such as a hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the computer device.

[0146] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for processing entity activity data, characterized in that: The method comprises: S101 reads the verification data area of ​​the UDP message according to the entity data acquisition requirement of the receiving end, the UDP message includes a verification data area and an entity data area, the verification data area is generated based on the message feature information preset by the receiving end, wherein the entity data acquisition requirement refers to the acquisition requirement of the static attributes and dynamic behavior corresponding data of a certain entity by any simulation interaction end during the combat simulation process; S102 identifies whether the UDP message is an entity activity message according to the message characteristic information, and when the UDP message is the entity activity message, reads and parses the entity data area to obtain current entity data of the first entity, wherein the message characteristic information is determined in advance by multiple simulation interaction terminals according to the common attributes of the entity activity message and / or multiple simulation interaction terminals; S103: obtaining the previous entity data and the subsequent entity data corresponding to the first entity within a preset time period, and respectively calculating the previous fluctuation value between the previous entity data and the current entity data, and the subsequent fluctuation value between the subsequent entity data and the current entity data; S104: Analyze the simulation entity attribute information of the first entity and the simulation environment attribute information of the first entity to obtain the parameter fluctuation capability of the first entity; determine a first parameter fluctuation value of the first entity according to the parameter fluctuation capability of the first entity, wherein the parameter fluctuation capability is used to characterize the ability of the first entity to cause entity data to change, and the first parameter fluctuation value is determined according to the parameter fluctuation capability of the first entity; S105: When the prior fluctuation value and / or the subsequent fluctuation value is greater than the first parameter fluctuation value, trigger the receiving end to generate a data anomaly signal.

2. The method according to claim 1, characterized in that The message characteristic information in the verification data area includes: software configuration information and data type information; the entity data area includes: at least one field group for independently storing the value of a specific operating state of the corresponding entity during combat, and the specific operating state is described by at least one indicator; Correspondingly, the step of reading and parsing the physical data area includes: Read at least one of the field groups corresponding to the specific running state pointed to by the entity data acquisition requirement; The receiving end adopts the set field definition rule to parse the field group and the storage location of the field to obtain the current entity data of the first entity; wherein the field definition rule is used to describe the mapping relationship between the field and the indicator.

3. The method according to claim 1, characterized in that The method further comprises: When the prior fluctuation value and / or the subsequent fluctuation value is less than the first parameter fluctuation value and greater than the second parameter fluctuation value, obtaining current entity data of at least one second entity, the entity data of the first entity and the entity data of the second entity having a linkage change relationship; The current entity data of the first entity is verified for abnormality based on the current entity data of the at least one second entity, and when the difference between the current entity data of the first entity and the current entity data of the at least one second entity exceeds a preset threshold, the receiving end is triggered to generate a data abnormality signal.

4. The method according to claim 2, characterized in that: The step of identifying whether the UDP message is an entity activity message according to the message characteristic information includes: Obtaining software configuration information in the verification data area; The software configuration information in the verification data area is verified based on the software configuration information of the receiving end. If the verification fails, the UDP message is not the entity activity message.

5. The method according to claim 4, characterized in that The step of identifying whether the UDP message is an entity activity message according to the message characteristic information further includes: Obtaining data type information in the verification data area; The data type information in the verification data area is identified. If the identification fails, the UDP message is not the entity activity message.

6. The method according to claim 2, characterized in that The method further comprises: Based on the field definition rule, determining a name field group in the entity data area for recording entity name indicators; Reading and parsing the name field groups of the received entity activity messages to filter out the entity activity messages updated by the first entity; The entity data area of ​​the entity activity message updated by the first entity is read and parsed to obtain subsequent entity data of the first entity.

7. The method according to claim 1, characterized in that The message characteristic information also includes data length information, where the data length information is the sum of the length of the verification data area and the length of the entity data area. The method also includes: The UDP message is read based on the data length information to obtain the verification data area and the entity data area.

8. The method according to claim 1, characterized in that The data in the verification data area is byte data of an unsigned long integer data type.

9. A computer device, characterized in that: The computer device includes a memory and a processor; The memory is used to store computer programs; The processor is used to execute the computer program and implement the method for processing entity activity data as described in any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the method for processing entity activity data according to any one of claims 1 to 8.

Images