An improved joint simulation object model development method, device and equipment

Abstract

The present application relates to an improved method, device and equipment for developing a joint simulation object model. The method includes: constructing an object-oriented multi-level combinable joint simulation system, which is composed of a number of freely accessible simulation units, and the simulation units are composed of a number of objects that interact with each other; developing and defining each simulation unit in the joint simulation system and the joint simulation system as a whole based on the HLA object model template, including developing and defining the object class and interaction class in which each simulation unit participates in the interaction based on the object model template, and standardizing the joint simulation data exchange files and exchange formats between each simulation unit in the joint simulation system. The use of this method can realize the standardization and standardized transmission and exchange of public data in the joint simulation system, improve the interoperability and reusability of the joint simulation, reduce the complexity of development and maintenance, and realize the rapid and standardized development of the joint simulation system.

Description

Technical Field

[0001] The present application relates to the field of computer simulation technology, and in particular to an improved method, device and equipment for developing a joint simulation object model. Background Art

[0002] Computer simulation technology is a comprehensive technology that uses computers as tools, based on similarity principles, information technology and basic theories and technologies in various related application fields, to build system models according to the purpose of system experiments, and dynamically operate the models under different conditions. At present, computer simulation has become an important means of analysis, research, testing, evaluation, development and skill training for large and particularly complex systems, and has been widely used in important fields of various industries.

[0003] With the development of simulation methodology and computer technology, simulation applications have made great progress in breadth and depth. In order to cope with different computing problems and different simulation occasions, especially the development of open complex giant system simulation, modeling and simulation technology, it has developed towards distributed, interactive, open, standardized, componentized and integrated trends to solve the problems of interoperability and reusability between various simulation models and simulation systems. Distributed simulation systems need to define a common data exchange model for multiple simulation nodes to describe the key information such as the name, composition, and type of the transmitted data, and based on this, all simulation nodes can achieve consistent understanding and unified and standardized processing of the transmitted data.

[0004] However, most existing methods use custom structures or arrays to define the exchanged data, which have poor interoperability and reusability, are time-consuming and costly to develop and maintain, and lack standardized construction guidance and data verification mechanisms. Summary of the invention

[0005] Based on this, it is necessary to provide an improved joint simulation object model development method, device and equipment to address the above technical problems.

[0006] An improved joint simulation object model development method, the method comprising:

[0007] Construct an object-oriented multi-level combinable joint simulation system. The joint simulation system consists of several freely accessible simulation units. The simulation units are connected to the joint simulation system through specific simulation proxy interfaces and communicate with other connected simulation units. The simulation units are composed of several objects that interact with each other.

[0008] Develop and define each simulation unit in the joint simulation system and the entire joint simulation system based on the HLA object model template;

[0009] The development and definition of each simulation unit in the joint simulation system includes: developing and defining the object class and interaction class of each simulation unit participating in the interaction based on the object model template, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class;

[0010] The overall development definition of the joint simulation system includes: constructing the simulation unit object model corresponding to each simulation unit based on the multi-level definition of object classes and the multi-level definition of interaction classes, and developing and defining the joint simulation data exchange files and exchange formats between each simulation unit according to the object model template, and stipulating that the simulation unit object model shall store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange files and standard exchange formats.

[0011] In one embodiment, the joint simulation system as a whole can join other joint simulation systems as a member, or be combined with other joint simulation systems to participate in a larger joint simulation, and when joining or combining, the public data model files of the joint simulation system and the public data model files of other joint simulation systems are combined into a larger public data model file.

[0012] In one embodiment, the object class and the interaction class of each simulation unit participating in the interaction are developed and defined based on the object model template, and a multi-level definition of the object class and a multi-level definition of the interaction class are obtained, including:

[0013] Based on the object model template, the object classes of each simulation unit participating in the interaction are developed and defined, and a multi-level definition of the object class described by the object class structure table is obtained; wherein the object class structure table includes the object class name, the inheritance relationship between each object class, and the ordering and publishing capability attributes of the object class;

[0014] Based on the object model template, the interaction class of each simulation unit participating in the interaction is developed and defined, and a multi-level definition of the interaction class described by the interaction class structure table is obtained; wherein the interaction class structure table includes the interaction class name, the inheritance relationship between each interaction class, and the initiation and perception capability attributes of the interaction class.

[0015] In one of the embodiments, in the object class structure table and the interaction class structure table, the root class is recorded in the leftmost column of the structure table, and the columns from left to right record the subclasses in sequence until the leaf class, and the number of columns in the structure table is equal to the number of layers of the object class or interaction class structure.

[0016] In one embodiment, both the object class name and the interaction class name are composed of letters, numbers and underscores, and both start with letters. In the entire object model template, each object class name and each interaction class name are globally unique.

[0017] In one embodiment, in the object class structure table, the subscription and publication capability attributes of each object class are represented by P, S, and N, respectively; wherein P indicates that the simulation unit that publishes the object class has the ability to simulate the behavior of the object class, S indicates that the simulation unit that subscribes to the object class has the ability to use the information of the object class, and N indicates that the object class can neither be published nor subscribed by the simulation unit;

[0018] In the interaction class structure table, the initiation and perception capability attributes of each interaction class are represented by I and Indicated; where I means initiatable, which means that the simulation unit has the ability to initialize and issue interaction instances; It is perceptible, which means that the simulation unit has the ability to subscribe to the interaction class and utilize the information of the interaction instance, but does not have the ability to operate on the objects affected by the interaction instance.

[0019] In one embodiment, a simulation unit object model corresponding to each simulation unit is constructed based on the multi-level definition of the object class and the multi-level definition of the interaction class, and the joint simulation data exchange file and exchange format between each simulation unit are developed and defined according to the object model template, and the simulation unit object model is specified to store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format, including:

[0020] Based on the multi-level definition of object classes and the multi-level definition of interaction classes, a simulation unit object model corresponding to each simulation unit is constructed. The simulation unit object model is used to describe the object classes, object class attributes, interaction classes, and interaction class parameter information that the simulation unit publishes or needs to order.

[0021] According to the object model template, the joint simulation data exchange file and exchange format between each simulation unit are developed and defined to obtain the joint simulation data standard exchange file and exchange format, and it is stipulated that the simulation unit object model shall store and transmit data in the joint simulation system according to the joint simulation data standard exchange file and standard exchange format; wherein, the joint simulation data standard exchange file is composed of user-defined data types, interest spaces, object classes, interaction classes and simulation units, and the joint simulation data standard exchange format is the extensible markup language xml format.

[0022] An improved joint simulation object model development device, the device comprising:

[0023] The joint simulation system building module is used to build an object-oriented multi-level combinable joint simulation system. The joint simulation system consists of several freely accessible simulation units. The simulation units are connected to the joint simulation system through specific simulation proxy interfaces and communicate with other connected simulation units. The simulation units are composed of several objects that interact with each other.

[0024] The object model development definition module is used to develop and define each simulation unit in the joint simulation system and the joint simulation system as a whole based on the object model template of HLA; wherein, the development definition of each simulation unit in the joint simulation system includes: based on the object model template, developing and defining the object class and interaction class in which each simulation unit participates in the interaction, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class; the development definition of the joint simulation system as a whole includes: constructing the simulation unit object model corresponding to each simulation unit based on the multi-level definition of the object class and the multi-level definition of the interaction class, and developing and defining the joint simulation data exchange file and exchange format between each simulation unit according to the object model template, stipulating that the simulation unit object model shall be stored and transmitted in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format.

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

[0026] Construct an object-oriented multi-level combinable joint simulation system. The joint simulation system consists of several freely accessible simulation units. The simulation units are connected to the joint simulation system through specific simulation proxy interfaces and communicate with other connected simulation units. The simulation units are composed of several objects that interact with each other.

[0027] Develop and define each simulation unit in the joint simulation system and the entire joint simulation system based on the HLA object model template;

[0028] The development and definition of each simulation unit in the joint simulation system includes: developing and defining the object class and interaction class of each simulation unit participating in the interaction based on the object model template, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class;

[0029] The overall development definition of the joint simulation system includes: constructing the simulation unit object model corresponding to each simulation unit based on the multi-level definition of object classes and the multi-level definition of interaction classes, and developing and defining the joint simulation data exchange files and exchange formats between each simulation unit according to the object model template, and stipulating that the simulation unit object model shall store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange files and standard exchange formats.

[0030] The above-mentioned improved joint simulation object model development method, device and equipment, under the hierarchical structure of an object-oriented multi-level combinable joint simulation system, uses object model templates to develop and define each simulation unit in the joint simulation system and the joint simulation system as a whole. Among them, by developing and defining the object classes and interaction classes participating in the interaction of each simulation unit, a multi-level definition of the object class and a multi-level definition of the interaction class are obtained. The hierarchical object class structure and interaction class structure can improve the flexibility of the simulation unit to participate in other joint simulations in the future. In addition, by developing and defining the joint simulation data exchange files and exchange formats between the simulation units in the overall joint simulation system, the standardized and normalized transmission and exchange of public data in the joint simulation system can be realized, the interoperability and reusability of the joint simulation are improved, the complexity of development and maintenance is reduced, and the rapid and standardized development of the joint simulation system can be realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A schematic diagram of a flow chart of an improved joint simulation object model development method in an embodiment;

[0032] Figure 2 A schematic diagram of the structure of a joint simulation system in one embodiment;

[0033] Figure 3 A schematic diagram of a joint simulation data standard exchange format in an embodiment;

[0034] Figure 4 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, an improved joint simulation object model development method is provided, comprising the following steps:

[0037] Step S1, construct an object-oriented multi-level combinable joint simulation system, the joint simulation system consists of a number of freely accessible simulation units, the simulation units access the joint simulation system through a specific simulation proxy interface and communicate with other connected simulation units, and the simulation units consist of a number of objects that interact with each other.

[0038] Among them, object-oriented multi-level combinable joint simulation system Figure 2As shown, the joint simulation system is a distributed simulation system based on achieving a specific simulation purpose, in which a simulation unit can be defined as a simulation application or other application participating in the joint simulation, which can be of various types, such as a simulation simulator. The objects contained in the simulation unit are the basic elements of the joint simulation system.

[0039] Specifically, the simulation unit contains the following information:

[0040] Basic information of simulation unit: including the name, version, description of the simulation unit, whether interest management is used, and the settings used by interest management;

[0041] Time control information: includes the advancement mode, which can be selected based on time step and event. If it is the time step advancement mode, there are settings for time advancement step and look-ahead amount, and the unit time strategy selection has four modes: time control time-limited mode, time control non-time-limited mode, non-time control time-limited mode and non-time control non-time-limited mode.

[0042] QoS (Quality of Service) management information: used to set various thresholds for simulation units to participate in the joint simulation process, mainly including robustness, consistency, responsiveness and efficiency. Robustness has three parameters: maximum crash times, heartbeat frequency failure times, and heartbeat delay failure times. Consistency mainly includes three parameters: warning level inconsistencies, critical level inconsistencies, and over-limit level inconsistencies. Responsiveness mainly includes three parameters: warning level delay times, critical level delay times, and over-limit level delay times. Efficiency mainly includes six parameters: simulation advancement time, reflection execution time, update execution time, warning level failure times, critical level failure times, and over-limit level failure times.

[0043] Furthermore, the joint simulation system as a whole can join other joint simulation systems as a member, or be combined with other joint simulation systems to participate in a larger joint simulation, and when joining or combining, the public data model files of the joint simulation system and the public data model files of other joint simulation systems are combined into a larger public data model file.

[0044] Step S2, developing and defining each simulation unit in the joint simulation system and the joint simulation system as a whole based on the HLA object model template.

[0045] Among them, the object model template of HLA (High Level Architecture) is an important part of the simulation architecture, which defines a set of components that describe the joint simulation object model. In order to achieve interoperability between joint simulation systems and improve the reuse capability of simulation systems and their components, this application uses the object model template to describe the joint simulation system and each simulation unit in the system, as well as various data and related information that need to be exchanged during the operation of the simulation system.

[0046] The object model template is designed to focus only on the requirements and capabilities necessary for information exchange between the joint simulation system and the simulation units. For the simulation unit, it only describes the external public interface, that is, the object class and interaction class that participate in the interaction in the joint simulation system. For the entire joint simulation system, it describes the information exchange between simulation units.

[0047] In a joint simulation system, an object usually represents an entity in the real world and is completely defined by attributes that identify its characteristics. During the operation of the joint simulation system, information exchange is achieved by transmitting these attribute values ​​between simulation units.

[0048] The specific implementation process of step S2 is as follows:

[0049] First, each simulation unit in the joint simulation system is developed and defined, including: based on the object model template, the object class and interaction class of each simulation unit participating in the interaction are developed and defined to obtain a multi-level definition of the object class and a multi-level definition of the interaction class.

[0050] Specifically, based on the object model template, the object classes participating in the interaction of each simulation unit are developed and defined, and a multi-level definition of the object class described by the object class structure table is obtained; wherein the object class structure table includes the object class name, the inheritance relationship between each object class, and the ordering and publishing capability attributes of the object class.

[0051] Among them, the object class structure table is used to describe the inheritance relationship between each object class in the joint simulation system or simulation unit. Among them, the direct relationship between the class and the subclass is represented by the method of containing the relevant class names in the adjacent columns of the structure table. The indirect relationship between the class and the subclass is obtained from the direct relationship through the transitivity of inheritance. For example, A is the superclass of B, B is the superclass of C, and A is also the superclass of C. In addition, the superclass and the subclass are also inverse relationships. For example, if A is the superclass of B, then B is the subclass of A. The subclass is the concretization of the superclass, inheriting the attributes of the superclass, and some additional attributes can be added according to the specific situation. An object is declared as an instance of a certain object class, and it also becomes a derived instance of all superclasses of the object class. An object class has at most one direct superclass and can have no subclasses.

[0052] In the object class structure table, the root class is recorded in the leftmost column of the object class structure table. The columns from left to right sequentially record the subclasses of the object class until the leaf class, and the number of columns in the object class structure table is equal to the number of layers of the object class structure. The object class name consists of letters, numbers and underscores, and starts with a letter. The object class name is globally unique in the full joint simulation, and it and its superclass connected by a dot symbol must also be globally unique. The object class name must be followed by a bracket to indicate the subscription and publication capability attributes of each object class. The subscription and publication capability attributes of each object class are represented by P, S, and N respectively; among them, P means that the simulation unit that publishes the object class has the ability to simulate the behavior of the object class, S means that the simulation unit that subscribes to the object class has the ability to use the information of the object class, and N means that the object class can neither be published nor subscribed by the simulation unit.

[0053] The object class identified as N is generally used to represent several abstract classes with common characteristics. It cannot be instantiated and is usually not published. When objects of several specific object classes have common attributes, setting up an abstract class helps to simplify the ordering of objects.

[0054] The simulation unit can subscribe to classes at any level in the object class hierarchy. By subscribing to all attributes of a specified object class, the simulation unit will receive updated values ​​of the attributes of all instances of that object class and its subclasses. The object class hierarchy provides a convenient means for the simulation unit to subscribe to multiple objects. It also simplifies the description of attributes. Attributes common to several classes can be defined once in the superclass, making attribute management simple.

[0055] For joint simulation, the object class structure is the agreement on object class division in the entire joint simulation system, reflecting the object classes and their hierarchical structures determined between simulation units to achieve the execution goal of joint simulation. The object class structure table of the simulation unit is a notice of the object classes that this simulation member can support, telling developers what the unit can publish and what it can order.

[0056] The hierarchical object class structure can provide flexibility for the simulation unit to participate in other joint simulations in the future, but for joint simulation, the structure and hierarchy of the object class should be determined according to the subscription requirements of all simulation units participating in the joint simulation. If a series of specific entity object classes are included in the object model of joint simulation, it can well meet the subscription requirements of simulation units in certain simulation systems, but if the simulation unit needs to subscribe to object information at a higher level of abstraction, then some object classes must be added to the object class structure table. Therefore, if a simulation unit has the ability to subscribe to object information at a certain level of abstraction, then the object class at that level of abstraction must be added to the object class structure table of joint simulation.

[0057] Specifically, based on the object model template, the interaction classes in which each simulation unit participates in the interaction are developed and defined, and a multi-level definition of the interaction class described by an interaction class structure table is obtained; wherein the interaction class structure table includes the interaction class name, the inheritance relationship between each interaction class, and the initiation and perception capability attributes of the interaction class.

[0058] Among them, in the joint simulation system, the interaction class refers to a clear action generated by one or some objects in a simulation unit that can affect the objects in the simulation unit. And just as the object class structure table describes the hierarchical relationship of the object class, the interaction class structure table describes the class and subclass relationship of the interaction instance. In the interaction class structure table, the interaction class hierarchy consists of the inheritance relationship of different interaction classes.

[0059] In the interaction class structure table, the root class is recorded in the leftmost column of the interaction class structure table. The columns from left to right sequentially record the subclasses of the interaction class until the leaf class, and the number of columns in the interaction class structure table is equal to the number of layers of the interaction class structure. The interaction class name is also composed of letters, numbers, and underscores, and starts with a letter. In the entire object model template, each interaction class name is globally unique. In addition, each interaction class in the interaction class structure table must also indicate its initiation and perception capability attributes. The initiation and perception capability attributes of each interaction class are represented by I and Indicated; where I means initiatable, which means that the simulation unit has the ability to initialize and issue interaction instances; Perceivable means that the simulation unit has the ability to subscribe to the interaction class and utilize the information of the interaction instance, but does not have the ability to operate on the objects affected by the interaction instance. In a co-simulation system, each interaction class should have at least one simulation unit that can initialize and send it, and at least one simulation unit that can perceive it.

[0060] In the joint simulation system, the hierarchy of interaction classes is mainly used to support the subscription of interaction classes with inheritance relationships. When a simulation unit subscribes to an interaction class, it will receive all interaction instances belonging to the interaction class and its subclasses during the execution of the joint simulation.

[0061] Interaction parameters can be used to record various information that reflects the characteristics of the interaction instance, such as the name of the object class, object attributes, etc. The object that receives the interaction instance will determine the impact of the interaction instance on it based on these interaction parameters. The identifier of the interaction parameter and some related details are recorded in the parameter table of the object model template. Just as the attributes of the object class can be inherited downward, the parameters of the interaction class can also be inherited downward through the hierarchy of the interaction class. The inheritance mechanism and principles are consistent with the inheritance mechanism and principles of the object class attributes.

[0062] Interaction instances are an important factor in the interoperability of simulation systems. Different simulation units that receive interaction instances should handle interaction instances in a consistent manner to ensure the interoperability between different simulation systems. In addition, in the system simulation process, in order to support the subscription of interaction classes, all interaction classes that may appear during the joint simulation execution must be recorded in the object model template.

[0063] Secondly, the overall development definition of the joint simulation system includes: building a simulation unit object model corresponding to each simulation unit based on the multi-level definition of object classes and the multi-level definition of interaction classes, and developing and defining the joint simulation data exchange files and exchange formats between each simulation unit according to the object model template, and stipulating that the simulation unit object model shall store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange files and standard exchange formats.

[0064] Specifically, the simulation unit object model corresponding to each simulation unit is first constructed based on the multi-level definition of object classes and the multi-level definition of interaction classes. The simulation unit object model is used to describe the object classes, object class attributes, interaction classes, and interaction class parameter information that the simulation unit publishes or needs to subscribe to. It reflects the capabilities of the simulation unit when participating in the joint simulation operation.

[0065] Then, according to the object model template, the joint simulation data exchange files and exchange formats between each simulation unit are developed and defined to obtain the joint simulation data standard exchange files and exchange formats, and it is stipulated that the simulation unit object model shall store and transmit data in the joint simulation system according to the joint simulation data standard exchange files and standard exchange formats; among which, the joint simulation data standard exchange files are composed of user-defined data types, interest spaces, object classes, interaction classes and simulation units, and the joint simulation data standard exchange format is the extensible markup language xml format.

[0066] Among them, joint simulation requires that each simulation unit has a simulation unit object model, which describes the object classes, object class attributes and interaction classes published or subscribed by the simulation unit in the joint simulation, but does not require the description of specific interaction data. Joint simulation requires that the simulation unit must also be standardized in the format specified by the joint simulation object model template.

[0067] The data exchange format of the joint simulation object model template is a standard file exchange format for storage and transmission between different joint simulation developers. Compared with the current mainstream definition using extended BNF (Backus-Naur Form), some structures are added to handle repeated and optional elements. This format is highly professional, difficult to learn, and has certain limitations in application. Whether it is the organizational structure or parsing or modification, it is quite complicated and extremely inconvenient. Based on this, in order to ensure the unambiguity of the definition of the data exchange format, this application defines the standard exchange format of joint simulation data between various simulation units as the extensible markup language xml format according to the object model template, providing simulation developers with a standard and widely accepted format that can be transmitted and used in different systems.

[0068] Specifically, the joint simulation data standard exchange format is as follows: Figure 3 As shown in the figure, the joint simulation data standard exchange file consists of UserDefineDataTypeList (user-defined data type), InterestingDefineList (interest space), ExerciseUnit (simulation unit), ClassList (object class) and InteractionList (interaction class), among which the simulation unit is also composed of sub-nodes such as time advancement type (TimeAdvanceType), simulation unit service quality strategy (UnitQos), object class list and interaction class list.

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

[0070] In one embodiment, an improved joint simulation object model development apparatus is provided, comprising:

[0071] The joint simulation system building module is used to build an object-oriented multi-level combinable joint simulation system. The joint simulation system consists of several freely accessible simulation units. The simulation units are connected to the joint simulation system through specific simulation proxy interfaces and communicate with other connected simulation units. The simulation units are composed of several objects that interact with each other.

[0072] The object model development definition module is used to develop and define each simulation unit in the joint simulation system and the joint simulation system as a whole based on the object model template of HLA; wherein, the development definition of each simulation unit in the joint simulation system includes: based on the object model template, developing and defining the object class and interaction class in which each simulation unit participates in the interaction, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class; the development definition of the joint simulation system as a whole includes: constructing the simulation unit object model corresponding to each simulation unit based on the multi-level definition of the object class and the multi-level definition of the interaction class, and developing and defining the joint simulation data exchange file and exchange format between each simulation unit according to the object model template, stipulating that the simulation unit object model shall be stored and transmitted in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format.

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

[0074] 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 4As 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, an improved joint simulation object model development method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

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

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

[0077] Construct an object-oriented multi-level combinable joint simulation system. The joint simulation system consists of several freely accessible simulation units. The simulation units are connected to the joint simulation system through specific simulation proxy interfaces and communicate with other connected simulation units. The simulation units are composed of several objects that interact with each other.

[0078] Develop and define each simulation unit in the joint simulation system and the entire joint simulation system based on the HLA object model template;

[0079] The development and definition of each simulation unit in the joint simulation system includes: developing and defining the object class and interaction class of each simulation unit participating in the interaction based on the object model template, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class;

[0080] The overall development definition of the joint simulation system includes: constructing the simulation unit object model corresponding to each simulation unit based on the multi-level definition of object classes and the multi-level definition of interaction classes, and developing and defining the joint simulation data exchange files and exchange formats between each simulation unit according to the object model template, and stipulating that the simulation unit object model shall store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange files and standard exchange formats.

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

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

Claims

1. An improved joint simulation object model development method, characterized in that: The method comprises: Construct an object-oriented multi-level combinable joint simulation system, wherein the joint simulation system is composed of a number of freely accessible simulation units, wherein the simulation unit is connected to the joint simulation system through a specific simulation proxy interface and communicates with other connected simulation units, and the simulation unit is composed of a number of objects that interact with each other; Develop and define each simulation unit in the joint simulation system and the joint simulation system as a whole based on the HLA object model template; The developing and defining each simulation unit in the joint simulation system includes: developing and defining the object class and the interaction class of each simulation unit participating in the interaction based on the object model template, and obtaining the multi-level definition of the object class and the multi-level definition of the interaction class; The development definition of the joint simulation system as a whole includes: constructing a simulation unit object model corresponding to each simulation unit based on the multi-level definition of the object class and the multi-level definition of the interaction class, and developing and defining the joint simulation data exchange file and exchange format between the various simulation units according to the object model template, stipulating that the simulation unit object model is stored and transmitted in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format; Among them, the simulation unit object model corresponding to each simulation unit is constructed based on the multi-level definition of the object class and the multi-level definition of the interaction class, and the joint simulation data exchange file and exchange format between each simulation unit are developed and defined according to the object model template, and the simulation unit object model is specified to store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format, including: Based on the multi-level definition of object classes and the multi-level definition of interaction classes, a simulation unit object model corresponding to each simulation unit is constructed, wherein the simulation unit object model is used to describe the object classes, object class attributes, interaction classes, and interaction class parameter information that the simulation unit publishes or needs to subscribe to; The joint simulation data exchange file and exchange format between each simulation unit are developed and defined according to the object model template to obtain the joint simulation data standard exchange file and exchange format, and it is stipulated that the simulation unit object model is stored and transmitted in the joint simulation system according to the joint simulation data standard exchange file and standard exchange format; wherein the joint simulation data standard exchange file is composed of user-defined data types, interest spaces, object classes, interaction classes and simulation units, and the joint simulation data standard exchange format is in the extensible markup language xml format; The simulation unit is composed of a time advancement type (TimeAdvanceType), a simulation unit service quality policy (UnitQos), an object class list and an interaction class list; The simulation unit also contains the following information: Basic information of simulation unit: including the name, version, description of the simulation unit, whether interest management is used, and the settings used by interest management; Time control information: including the advancement mode, there are the options of time-step-based advancement and event-based advancement mode, the time-step advancement mode has the settings of time advancement step and forward-looking amount, and the selection of unit time strategy has four options: time control time-limited mode, time control non-time-limited mode, non-time control time-limited mode and non-time control non-time-limited mode; QoS (Quality of Service) management information; used to set various thresholds for simulation units participating in the joint simulation process, including settings for four aspects: robustness, consistency, responsiveness, and efficiency; robustness includes three parameters: maximum number of crashes, number of heartbeat frequency failures, and number of heartbeat delay failures; consistency includes three parameters: warning level inconsistencies, critical level inconsistencies, and over-limit level inconsistencies; responsiveness includes three parameters: warning level delays, critical level delays, and over-limit level delays; efficiency includes six parameters: simulation advancement time, reflection execution time, update execution time, warning level failures, critical level failures, and over-limit level failures.

2. The method according to claim 1, characterized in that The joint simulation system as a whole can join other joint simulation systems as a member, or be combined with other joint simulation systems to participate in a larger joint simulation, and when joining or combining, the public data model files of the joint simulation system and the public data model files of other joint simulation systems are combined into a larger public data model file.

3. The method according to claim 1, characterized in that: Based on the object model template, the object class and interaction class of each simulation unit participating in the interaction are developed and defined, and the multi-level definition of the object class and the multi-level definition of the interaction class are obtained, including: Based on the object model template, the object classes of each simulation unit participating in the interaction are developed and defined, and a multi-level definition of the object class described by an object class structure table is obtained; wherein the object class structure table includes the object class name, the inheritance relationship between each object class, and the ordering and publishing capability attributes of the object class; Based on the object model template, the interaction class in which each simulation unit participates in the interaction is developed and defined, and a multi-level definition of the interaction class described by an interaction class structure table is obtained; wherein the interaction class structure table includes the interaction class name, the inheritance relationship between each interaction class, and the initiation and perception capability attributes of the interaction class.

4. The method according to claim 3, characterized in that: In the object class structure table and the interaction class structure table, the root class is recorded in the leftmost column of the structure table, and the columns from left to right sequentially record the subclasses until the leaf class, and the number of columns in the structure table is equal to the number of layers of the object class or interaction class structure.

5. The method according to claim 3, characterized in that: The object class name and the interaction class name are both composed of letters, numbers and underscores, and both start with letters. In the entire object model template, each object class name and each interaction class name are globally unique.

6. The method according to claim 3, characterized in that In the object class structure table, the subscription and publication capability attributes of each object class are represented by P, S, and N respectively; wherein P indicates that the simulation unit that publishes the object class has the ability to simulate the behavior of the object class, S indicates that the simulation unit that subscribes to the object class has the ability to use the information of the object class, and N indicates that the object class can neither be published nor subscribed by the simulation unit; In the interaction class structure table, the initiation and perception capability attributes of each interaction class are respectively represented by I and Indicated; where I means initiatable, which means that the simulation unit has the ability to initialize and issue interaction instances; It is perceptible, which means that the simulation unit has the ability to subscribe to the interaction class and utilize the information of the interaction instance, but does not have the ability to operate on the objects affected by the interaction instance.

7. An improved joint simulation object model development device, characterized in that: The device comprises: A joint simulation system construction module is used to construct an object-oriented multi-level combinable joint simulation system, wherein the joint simulation system is composed of a number of freely accessible simulation units, wherein the simulation units are connected to the joint simulation system through a specific simulation proxy interface and communicate with other connected simulation units, and the simulation units are composed of a number of objects that interact with each other; An object model development definition module is used to develop and define each simulation unit in the joint simulation system and the joint simulation system as a whole based on the object model template of HLA; wherein, developing and defining each simulation unit in the joint simulation system includes: developing and defining the object class and interaction class in which each simulation unit participates in the interaction based on the object model template, and obtaining a multi-level definition of the object class and a multi-level definition of the interaction class; developing and defining the joint simulation system as a whole includes: constructing a simulation unit object model corresponding to each simulation unit based on the multi-level definition of the object class and the multi-level definition of the interaction class, and developing and defining the joint simulation data exchange file and exchange format between each simulation unit according to the object model template, and stipulating that the simulation unit object model is stored and transmitted in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format; Among them, the simulation unit object model corresponding to each simulation unit is constructed based on the multi-level definition of the object class and the multi-level definition of the interaction class, and the joint simulation data exchange file and exchange format between each simulation unit are developed and defined according to the object model template, and the simulation unit object model is specified to store and transmit data in the joint simulation system according to the defined joint simulation data standard exchange file and standard exchange format, including: Based on the multi-level definition of object classes and the multi-level definition of interaction classes, a simulation unit object model corresponding to each simulation unit is constructed, wherein the simulation unit object model is used to describe the object classes, object class attributes, interaction classes, and interaction class parameter information that the simulation unit publishes or needs to subscribe to; The joint simulation data exchange file and exchange format between each simulation unit are developed and defined according to the object model template to obtain the joint simulation data standard exchange file and exchange format, and it is stipulated that the simulation unit object model is stored and transmitted in the joint simulation system according to the joint simulation data standard exchange file and standard exchange format; wherein the joint simulation data standard exchange file is composed of user-defined data types, interest spaces, object classes, interaction classes and simulation units, and the joint simulation data standard exchange format is in the extensible markup language xml format; The simulation unit is composed of a time advancement type (TimeAdvanceType), a simulation unit service quality policy (UnitQos), an object class list and an interaction class list; The simulation unit also contains the following information: Basic information of simulation unit: including the name, version, description of the simulation unit, whether interest management is used, and the settings used by interest management; Time control information: including the advancement mode, there are the options of time-step-based advancement and event-based advancement mode, the time-step advancement mode has the settings of time advancement step and forward-looking amount, and the selection of unit time strategy has four options: time control time-limited mode, time control non-time-limited mode, non-time control time-limited mode and non-time control non-time-limited mode; QoS (Quality of Service) management information; used to set various thresholds for simulation units participating in the joint simulation process, including settings for four aspects: robustness, consistency, responsiveness, and efficiency; robustness includes three parameters: maximum number of crashes, number of heartbeat frequency failures, and number of heartbeat delay failures; consistency includes three parameters: warning level inconsistencies, critical level inconsistencies, and over-limit level inconsistencies; responsiveness includes three parameters: warning level delays, critical level delays, and over-limit level delays; efficiency includes six parameters: simulation advancement time, reflection execution time, update execution time, warning level failures, critical level failures, and over-limit level failures.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

Images