Simulation data updating and reflection method, device and equipment based on three-level progression

Abstract

The present application relates to a simulation data update and reflection method, device and equipment based on three-level progression. The method comprises: setting simulation data as a three-level mode of object class, object instance and instance attribute, assigning object class handle and instance attribute handle to object class and instance attribute, assigning an object instance handle to each object instance when the simulation unit registers the object instance to the simulation service; organizing each instance attribute in each object instance into attribute layer data, object instance layer data and object class layer data of the object instance according to a preset format; organizing the attribute data of all object instances to be updated in the object class into a data packet for transmission, and the simulation unit receiving the data packet performs data splitting according to the same format, and reflects to the instance attribute of the corresponding object class according to the object instance handle and the instance attribute handle. The adoption of this method can improve the transmission efficiency and analysis processing time of simulation data.

Description

Technical Field

[0001] The present application relates to the field of simulation technology, and in particular to a simulation data update and reflection method, device and equipment based on three-level progression. Background Art

[0002] In the process of joint simulation, the property changes of object instances have a key impact on the simulation results. As the scale of distributed simulation systems becomes larger and larger, the amount of simulation data is also increasing sharply, and an efficient and convenient simulation data transmission method is urgently needed. Efficient transmission of simulation data requires optimization of simulation data updates at the data sending end and high-performance expansion of data reflection at the data receiving end.

[0003] The existing technologies can be roughly divided into two categories: one is to send and receive all data in a package as a whole, and the other is to send and receive data in a package according to the simulation data elements (i.e. attributes). The former has the problem of redundant data transmission, which wastes network bandwidth resources and has a large amount of computational complexity in data parsing and processing. The latter will cause a large amount of small packet data to be transmitted in the network, which will occupy too many node computing resources. Summary of the invention

[0004] Based on this, it is necessary to provide a simulation data update and reflection method, device and equipment based on three-level progression that can improve the transmission efficiency and analysis processing time of simulation data in order to address the above technical problems.

[0005] A simulation data updating and reflection method based on three-level progression, the method comprising:

[0006] The simulation data in the simulation process is defined in the public data model file, and the simulation data is set as a three-level model of object class, object instance and instance attribute; the object class includes multiple object instances; the object instance includes multiple instance attributes;

[0007] At the beginning of the joint simulation, the simulation service allocates globally unique object class handles and instance attribute handles to the object class and instance attribute. When the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance.

[0008] When the simulation unit is used to update the attributes of the object instance during the simulation process, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, and all object instance layer data are organized into object class layer data according to a preset HNLV format;

[0009] The attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

[0010] In one embodiment, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, including:

[0011] Each instance attribute in each object instance is organized into attribute layer data of the object instance according to the HLV format of instance attribute handle, attribute data length and attribute data value.

[0012] In one embodiment, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, including:

[0013] All attribute layer data in the object instance are organized into object instance layer data of the object instance in sequence according to the HNLV format of object instance handle, object instance attribute quantity, object instance attribute length, and object instance attribute data value.

[0014] In one embodiment, all object instance layer data are organized into object class layer data according to a preset HNLV format, including:

[0015] All object instance layer data are organized into object class layer data in sequence according to the HNLV format of object class handle, object instance number, object instance data length, and object instance data value.

[0016] In one embodiment, the instance attribute handle and attribute data are both 4 bytes long.

[0017] In one embodiment, the object instance handle is fixed to 4 bytes; the number of object instance attributes is fixed to 4 bytes; and the length of the object instance attributes is fixed to 4 bytes.

[0018] In one embodiment, the object class handle, the number of object instances, and the object instance data length are all fixed at 4 bytes.

[0019] A simulation data updating and reflection device based on three-level progression, the device comprising:

[0020] A simulation data definition module is used to define simulation data in a simulation process in a public data model file, and to set the simulation data to a three-level mode of an object class, an object instance, and an instance attribute; an object class includes a plurality of object instances; an object instance includes a plurality of instance attributes;

[0021] A handle allocation module, used for the simulation service to allocate globally unique object class handles and instance attribute handles to object classes and instance attributes when the joint simulation starts, and when the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance;

[0022] A data hierarchy setting module, used for updating the attributes of the object instance by using the simulation unit during the simulation process, organizing each instance attribute in each object instance into attribute layer data of the object instance according to a preset HLV format, organizing all attribute layer data in the object instance into object instance layer data according to a preset HNLV format, and organizing all object instance layer data into object class layer data according to a preset HNLV format;

[0023] The data update and reflection module is used to organize the attribute data of all object instances to be updated in the object class into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

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

[0025] The simulation data in the simulation process is defined in the public data model file, and the simulation data is set as a three-level model of object class, object instance and instance attribute; the object class includes multiple object instances; the object instance includes multiple instance attributes;

[0026] At the beginning of the joint simulation, the simulation service allocates globally unique object class handles and instance attribute handles to the object class and instance attribute. When the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance.

[0027] When the simulation unit is used to update the attributes of the object instance during the simulation process, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, and all object instance layer data are organized into object class layer data according to a preset HNLV format;

[0028] The attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

[0029] The above-mentioned simulation data update and reflection method, device and equipment based on three-level progression, the present application sets the simulation data into a three-level mode of object class, object instance and instance attribute by setting three-level progressive simulation data. At the beginning of the joint simulation, the simulation service assigns a globally unique object class handle and instance attribute handle to the object class and instance attribute. When the simulation unit registers the object instance to the simulation service, the simulation service assigns a globally unique object instance handle to each object instance. In this way, each simulation unit reaches a consensus at the object class and object instance attribute layer and the object instance layer, and can find the corresponding object class, instance attribute and object instance through the object class handle, instance attribute handle and object instance handle, which is an important basis for data update and reflection. Finally, when the simulation unit is used to update the attributes of the object instance during the simulation advancement process, each instance attribute in each object instance is organized into the attribute layer data of the object instance according to the preset HLV format, and all attribute layer data in the object instance is organized into the object instance layer data according to the preset HNLV format, and all object instance layer data is organized into the object class layer data according to the preset HNLV format. The attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle. One network communication can update and reflect multiple object instance attribute values, reducing the pressure of network communication in joint simulation. By providing a three-level optional and combinable data packaging transmission mechanism of attributes, instances, and classes, it supports users to customize and select data transmission modes according to their own business characteristics, realizes optimal utilization of network bandwidth resources, and improves the transmission efficiency of simulation data and the timeliness of parsing processing. It can update and reflect the attribute values ​​of multiple instances at one time, which has obvious advantages in network transmission efficiency compared with the single object instance attribute value update method defined in the HLA interface specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A schematic flow chart of a simulation data update and reflection method based on three-level progression in one embodiment;

[0031] Figure 2 A schematic diagram of a software service flow in one embodiment;

[0032] Figure 3 A schematic diagram of a three-level progressive data structure in one embodiment;

[0033] Figure 4 It is a structural block diagram of a simulation data updating and reflection device based on three-level progression in one embodiment;

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

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

[0036] In one embodiment, Figure 1 As shown, a simulation data updating and reflection method based on three-level progression is provided, comprising the following steps:

[0037] Step 102, defining simulation data in the simulation process in a common data model file, and setting the simulation data as a three-level model of object class, object instance and instance attribute; the object class includes multiple object instances; the object instance includes multiple instance attributes.

[0038] Software business process such as Figure 2 As shown, the three-level mode attribute value update and reflection method under joint simulation is based on the same joint simulation. Different simulation units can transfer the attribute values ​​of batch object instances, so as to maintain the consistency of the object instance status of each simulation unit in the joint simulation. In large-scale joint simulation, simulation units are usually deployed on different computers. In order to maintain the consistency of the status of each simulation unit in the joint simulation, a large amount of network transmission is required to synchronize the status between simulation units. The update and reflection attribute value method is an important method for synchronizing the attribute values ​​of object instances in joint simulation, which runs through the entire life cycle of object instances in the joint simulation process. The performance of the update and reflection attribute value method has an important impact on the performance of the entire joint simulation. For this reason, the present application is triggered from the data protocol layer, and the simulation data is set to a three-level mode of object class, object instance and instance attribute, and the object instance and instance attribute in the same object class are synchronized according to Figure 3 The data structures shown are effectively organized together, so that one network communication can update and reflect the attribute values ​​of multiple object instances, reducing the pressure of network communication in joint simulation.

[0039] Step 104, when the joint simulation starts, the simulation service allocates globally unique object class handles and instance attribute handles to the object class and instance attributes. When the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance.

[0040] At the beginning of the joint simulation, the simulation service assigns globally unique object class handles and instance attribute handles to the object classes and instance attributes defined in the public data model file. When the simulation unit joins the joint simulation, it is notified to each simulation unit, so that each simulation unit reaches a consensus at the object class and object instance attribute layer, and can find the corresponding object class and instance attribute through the object class handle and instance attribute handle.

[0041] When a simulation unit registers an object instance with a simulation service, the simulation service assigns a globally unique object instance handle to each object instance. And notifies other simulation units, so that in the process of joint simulation, each simulation unit also reaches a consensus at the object instance layer, and can find the object instance through the object instance handle. These handles are an important basis for data update and reflection in this application, among which all handles are 4-byte unsigned int type.

[0042] Step 106, when the simulation unit is used to update the attributes of the object instance during the simulation process, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, and all object instance layer data are organized into object class layer data according to a preset HNLV format.

[0043] Step 108, organize the attribute data of all object instances to be updated in the object class into a data packet for transmission, and the simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

[0044] When the simulation unit needs to update the attributes of an object instance during the simulation process, it first organizes each instance attribute data in each object instance into attribute layer data of the object instance according to the HLV (Handle-Length-Value) format of attribute handle, attribute data length, and attribute data value.

[0045] Secondly, all attribute layer data in the object instance are organized together in sequence according to the format of object instance handle, object instance attribute number, object instance attribute length, object instance attribute data HNLV... (Handle-Number-[Length-Value...]) to form the object instance layer data of the object instance.

[0046] Finally, all object instance layer data are organized in the format of object class instance handle, object instance number, object instance data length, object instance data HNLV... to form the object class layer data, and finally the attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. Similarly, the simulation unit receiving the data packet can also split the data in the same format, and reflect it to the instance attribute of the corresponding object class according to the object instance handle and instance attribute handle, so that one network communication can update and reflect multiple object instance attribute values, reducing the pressure of network communication in joint simulation.

[0047] In the above-mentioned simulation data update and reflection method based on three-level progression, the present application sets the simulation data to a three-level mode of object class, object instance and instance attribute by setting three-level progressive simulation data. At the beginning of the joint simulation, the simulation service assigns globally unique object class handles and instance attribute handles to the object class and instance attributes. When the simulation unit registers the object instance to the simulation service, the simulation service assigns a globally unique object instance handle to each object instance. In this way, each simulation unit reaches a consensus at the object class and object instance attribute layer and the object instance layer, and can find the corresponding object class, instance attribute and object instance through the object class handle, instance attribute handle and object instance handle, which is an important basis for data update and reflection. Finally, when the simulation unit is used to update the attributes of the object instance during the simulation process, each instance attribute in each object instance is organized into the attribute layer data of the object instance according to the preset HLV format, and all attribute layer data in the object instance is organized into the object instance layer data according to the preset HNLV format, and all object instance layer data is organized into the object class layer data according to the preset HNLV format. The attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle. One network communication can update and reflect multiple object instance attribute values, reducing the pressure of network communication in joint simulation. By providing a three-level optional and combinable data packaging transmission mechanism of attributes, instances, and classes, it supports users to customize and select data transmission modes according to their own business characteristics, realizes optimal utilization of network bandwidth resources, and improves the transmission efficiency of simulation data and the timeliness of parsing processing. It can update and reflect the attribute values ​​of multiple instances at one time, which has obvious advantages in network transmission efficiency compared with the single object instance attribute value update method defined in the HLA interface specification.

[0048] In one embodiment, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, including:

[0049] Each instance attribute in each object instance is organized into attribute layer data of the object instance according to the HLV format of instance attribute handle, attribute data length and attribute data value.

[0050] In a specific embodiment, the attribute values ​​in the object class are formatted and packaged in sequence. The following formatting is performed for different data types:

[0051] Fixed-length data type: directly copy the memory according to the length of the data type.

[0052] Variable-length type: uses the LV format (8 bytes length + data value) for copying.

[0053] Fixed-length array element type: NV format (number of 8-byte array elements + element value) is used for copying.

[0054] Variable-length type of array elements: the number of 8-byte arrays + the data value of each variable-length type element are packed in sequence.

[0055] Composite data types: All elements are expanded after 1-byte alignment (all elements are tiled according to the above rules).

[0056] In a specific embodiment, the present application can support different data types, not only common data types but also complex data types. Data is serialized according to the format to form a continuous memory data. When calling the interface, only the memory address and length need to be passed in, reducing data copying.

[0057] In one embodiment, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, including:

[0058] All attribute layer data in the object instance are organized into object instance layer data of the object instance in sequence according to the HNLV format of object instance handle, object instance attribute quantity, object instance attribute length, and object instance attribute data value.

[0059] In a specific embodiment, the object instance layer data packages all attributes in sequence according to the attribute handle 4 bytes + attribute value (organized according to the attribute layer rules).

[0060] In one embodiment, all object instance layer data are organized into object class layer data according to a preset HNLV format, including:

[0061] All object instance layer data are organized into object class layer data in sequence according to the HNLV format of object class handle, object instance number, object instance data length, and object instance data value.

[0062] In a specific embodiment, the object class layer data packages all instances according to the instance data length of 4 bytes + instance data (organized according to instance layer rules).

[0063] In one embodiment, the instance attribute handle and attribute data are both 4 bytes long.

[0064] In one embodiment, the object instance handle is fixed to 4 bytes; the number of object instance attributes is fixed to 4 bytes; and the length of the object instance attributes is fixed to 4 bytes.

[0065] In one embodiment, the object class handle, the number of object instances, and the object instance data length are all fixed at 4 bytes.

[0066] In a specific embodiment, 4 bytes are the data format agreement between the update and reflection simulation units. When reflecting data, the position of the data element in the data packet can be quickly calculated according to this format, and the content of the data element can be obtained according to the position offset and data length.

[0067] Under the same hardware environment, network environment and experimental parameters, the time consumption of updating attribute values ​​of different numbers of object instances in HLA interface specification mode and JLINK three-level mode is compared and analyzed to evaluate the performance of these two modes in turn. The experimental environment is shown in Table 1.

[0068] Table 1

[0069]

[0070] The network environment is shown in Table 2:

[0071] Table 2

[0072]

[0073] The experimental parameters are shown in Table 3:

[0074] Table 3

[0075]

[0076] The experimental results are shown in Table 4:

[0077] Table 4

[0078]

[0079] From the experimental data, in the case of long connections, when updating multiple object instances, the time taken to update attribute values ​​in the JLINK three-level mode is half of that in the HLA interface specification mode, which greatly improves the efficiency of network transmission. In the case of short connections, because updating the attribute values ​​of multiple object instances in the HLA interface specification mode requires multiple network transmissions and multiple network connections, this is a very time-consuming operation, while updating the attribute values ​​in the JLINK three-level mode only requires one time, and the advantage will be more obvious.

[0080] It should be understood that although Figure 1 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 1 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0081] In one embodiment, Figure 4 As shown, a simulation data update and reflection device based on three-level progression is provided, including: a simulation data definition module 402, a handle allocation module 404, a data level setting module 406 and a data update and reflection module 408, wherein:

[0082] The simulation data definition module 402 is used to define the simulation data in the simulation process in the public data model file, and set the simulation data to a three-level mode of object class, object instance and instance attribute; the object class includes multiple object instances; the object instance includes multiple instance attributes;

[0083] A handle allocation module 404 is used for the simulation service to allocate globally unique object class handles and instance attribute handles to object classes and instance attributes when the joint simulation starts. When the simulation unit registers an object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance.

[0084] The data level setting module 406 is used to organize each instance attribute in each object instance into attribute layer data of the object instance according to a preset HLV format, organize all attribute layer data in the object instance into object instance layer data according to a preset HNLV format, and organize all object instance layer data into object class layer data according to a preset HNLV format when updating the attribute of the object instance in the process of advancing the simulation by using the simulation unit;

[0085] The data update and reflection module 408 is used to organize the attribute data of all object instances to be updated in the object class into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

[0086] For the specific definition of the simulation data update and reflection device based on three-level progression, please refer to the definition of the simulation data update and reflection method based on three-level progression above, which will not be repeated here. Each module in the above-mentioned simulation data update and reflection device based on three-level progression can be implemented in whole or in part by software, hardware and a combination thereof. Each of 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 in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0087] 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 5 As shown. The computer device includes a processor, a memory, a network 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 network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a simulation data update and reflection method based on three-level progression 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 housing, or an external keyboard, touchpad or mouse, etc.

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

[0089] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

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

[0091] 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. A simulation data updating and reflection method based on three-level progression, characterized in that: The method comprises: The simulation data in the simulation process is defined in the public data model file, and the simulation data is set as a three-level mode of object class, object instance and instance attribute; the object class includes a plurality of object instances; the object instance includes a plurality of instance attributes; At the beginning of the joint simulation, the simulation service allocates globally unique object class handles and instance attribute handles to the object class and instance attribute. When the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance. When the simulation unit is used to update the attributes of the object instance during the simulation process, each instance attribute in each object instance is organized into attribute layer data of the object instance according to a preset HLV format, all attribute layer data in the object instance are organized into object instance layer data according to a preset HNLV format, and all object instance layer data are organized into object class layer data according to a preset HNLV format; The attribute data of all object instances to be updated in the object class are organized into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

2. The method according to claim 1, characterized in that: Each instance attribute in each object instance is organized into attribute layer data of the object instance according to the preset HLV format, including: Each instance attribute in each object instance is organized into attribute layer data of the object instance according to the HLV format of instance attribute handle, attribute data length and attribute data value.

3. The method according to claim 1, characterized in that: All object instance layer data are organized into object class layer data according to the preset HNLV format, including: All object instance layer data are organized into object class layer data in sequence according to the HNLV format of object class handle, object instance number, object instance data length, and object instance data value.

4. The method according to any one of claims 1 to 3, characterized in that: All object instance layer data are organized into object class layer data according to the preset HNLV format, including: All object instance layer data are organized into object class layer data in sequence according to the HNLV format of object class handle, object instance number, object instance data length, and object instance data value.

5. The method according to claim 2, characterized in that: The instance attribute handle and attribute data are both 4 bytes long.

6. The method according to claim 3, characterized in that The object instance handle is fixed to 4 bytes; the number of object instance attributes is fixed to 4 bytes; and the length of object instance attributes is fixed to 4 bytes.

7. The method according to claim 4, characterized in that The object class handle, object instance number and object instance data length are all fixed at 4 bytes.

8. A simulation data updating and reflection device based on three-level progression, characterized in that: The device comprises: A simulation data definition module is used to define simulation data in a simulation process in a public data model file, and to set the simulation data to a three-level mode of an object class, an object instance, and an instance attribute; the object class includes a plurality of object instances; the object instance includes a plurality of instance attributes; A handle allocation module, used for the simulation service to allocate globally unique object class handles and instance attribute handles to object classes and instance attributes when the joint simulation starts, and when the simulation unit registers the object instance with the simulation service, the simulation service allocates a globally unique object instance handle to each object instance; A data hierarchy setting module, used for updating the attributes of the object instance by using the simulation unit during the simulation process, organizing each instance attribute in each object instance into attribute layer data of the object instance according to a preset HLV format, organizing all attribute layer data in the object instance into object instance layer data according to a preset HNLV format, and organizing all object instance layer data into object class layer data according to a preset HNLV format; The data update and reflection module is used to organize the attribute data of all object instances to be updated in the object class into a data packet for transmission. The simulation unit receiving the data packet splits the data in the same format and reflects it to the instance attributes of the corresponding object class according to the object instance handle and the instance attribute handle.

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 7 are implemented.

Images