CN112051997A

CN112051997A - Method, device and storage medium for building modular and parameterized model architecture

Info

Publication number: CN112051997A
Application number: CN202010841243.3A
Authority: CN
Inventors: 肖辉; 苏稳
Original assignee: Hunan Xinhang Power Information Technology Co ltd
Current assignee: Hunan Xinhang Power Information Technology Co ltd
Priority date: 2020-08-20
Filing date: 2020-08-20
Publication date: 2020-12-08

Abstract

A method, system, computer device, and readable storage medium for building a modular and parameterized model architecture, the method of one embodiment comprising: defining model basic information by adopting a model development tool, wherein the model basic information comprises: model basic data, model atom behaviors, model atom conditions, model object grouping, model message grouping and model object type messages are stored; generating a model code frame based on model basic information, and developing a model library through the model code frame and a software development toolkit, wherein the model library comprises: an entity model related to the entities of the field, a component model determined based on the same type of components related to each entity of the field, an environment model related to the environment of the field, and an atomic behavior component model related to the field; and setting model parameters of each model in the model library, and carrying out parameterized display on the models. By adopting the embodiment, the model is convenient and fast to establish, and is high in speed and efficiency.

Description

Method, device and storage medium for building modular and parameterized model architecture

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method for building a modular and parameterized model architecture, a system for building a modular and parameterized model architecture, a computer device, and a computer-readable storage medium.

Background

In some application scenarios of computer technology, a simulation application is involved, and before simulation, a simulation model of a simulation object needs to be established. In a conventional simulation application, a specific simulation model is usually established for a simulation object alone, for example, when a vehicle is simulated, the simulation model of the vehicle needs to be established, for example, basic attributes of the vehicle are established first, then the specific model of the vehicle, such as a maneuvering model and a sensor model of the vehicle, is developed, and then the model is assembled into a vehicle model for simulation. The simulation development mode has the advantages of high model development difficulty, poor reusability, low expandability and low efficiency, can be only used for single application, and can cause the problem of repeated construction of engines in order to adapt to other applications.

Disclosure of Invention

In view of the above, it is necessary to provide a building method of a componentized and parameterized model architecture, a building system of a componentized and parameterized model architecture, a computer device, and a computer-readable storage medium.

A method of building a modular and parameterized model architecture, the method comprising:

defining model basic information by adopting a model development tool, wherein the model basic information comprises: model basic data, model atom behaviors, model atom conditions, model object grouping, model message grouping and model object type messages, and storing the model basic information;

generating a model code frame based on model basic information, and developing a model library through the model code frame and a software development toolkit, wherein the model library comprises: an entity model related to the entities of the field, a component model determined based on the same type of components related to each entity of the field, an environment model related to the environment of the field, and an atomic behavior component model related to the field;

and setting model parameters of each model in the model library, and carrying out model parameterization display on each model.

In one embodiment, the solid model includes: the system comprises an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model and a squad index aggregation entity model;

the component model includes: a sensor component model, a communication device component model, an electronic jamming device component model, a weapons discharge system component model, a target indicator component model, and a warhead component model.

In one embodiment, the squad index aggregate entity model in the entity model is derived and generated based on the aggregate type physical model, and the other entity models except the squad index aggregate entity model in the entity model are derived and generated based on the non-aggregate type physical model base class.

In one embodiment, the interfaces of the entity model comprise an initialization interface, a periodic scheduling interface and an event processing interface, the initialization interface is called, the periodic scheduling interface is called to realize the relevant processing of the entity along with the time process, and the event processing interface is called to respond to the relevant processing of the model event.

In one embodiment, the model base class data of the sensor component model comprises sensor data, sensor types, sensor states and detection target information, and the model interface of the sensor component model comprises an initialization interface and a detection interface;

the model base class data of the communication equipment component model comprises communication equipment data, a communication equipment type, a communication equipment state, detection target information data, network information data and data link data, and the model interface of the communication equipment component model comprises an initialization interface and a communication interface;

the model base class data of the electronic interference equipment component model comprises electronic interference equipment data, electronic interference equipment types, electronic interference equipment states and target information data, and the model interface of the electronic interference equipment component model comprises an initialization interface and an interference interface;

the model base class data of the weapon launching system component model comprises weapon launching system data, a weapon launching system state and an operation target type, and the model interface of the weapon launching system component model comprises an initialization interface and a weapon system launch control interface;

the model base class data of the target indicator component model comprises target indicator data, target indicator states and target information data, and the model interface of the target indicator component model comprises an initialization interface and a guide interface;

the model base class data of the warhead component model comprises warhead data, and the model interface of the warhead component model comprises an initialization interface and a damage interface.

In one embodiment, the sensor component model includes a detection model, a tracking model, and a recognition model of the sensor; the communication/data link device model comprises a communication/data link model of a communication/data link; the electronic interference equipment component model comprises an interference model and a deception model of electronic warfare equipment; the weapon firing system component model comprises a fire control model of the weapon firing system equipment; the target indicator component model comprises a data fusion model and a target recognition model of the target indicating equipment; the warhead component model includes a killing model of the warhead equipment.

In one embodiment, the environmental models include an astronomical environmental model, a geographic environmental model, a meteorological environmental model, and a hydrologic environmental model.

In one embodiment, the astronomical environment model development interface comprises an interface for acquiring simulation astronomical time and an interface for setting the simulation astronomical time;

the geographic environment model development interface comprises an interface for acquiring the elevation of a specified position;

the meteorological environment model development interface comprises an interface for acquiring wind speed and wind direction at a specified position, an interface for acquiring precipitation level and precipitation amount at the specified position, an interface for acquiring temperature at the specified position, an interface for acquiring relative humidity at the specified position, an interface for acquiring visibility at the specified position, and an interface for acquiring cloud cover level, cloud height and cloud thickness at the specified position;

the hydrological environment model development interface comprises an interface for acquiring the sea state grade of a specified position, an interface for acquiring the flow velocity and the flow direction of the specified position, an interface for acquiring the wave height and the wave direction of the specified position, an interface for acquiring the tide of the specified position and an interface for acquiring the hydrological grade of the specified position.

In one embodiment, the atomic behavior component model includes an atomic behavior model and an atomic condition model, and the atomic behavior model and the atomic condition model are derived based on a base class:

the atomic behavior model binds related application entities by setting behavior parameters of categories and type names associated with the entities, generates an atomic behavior message processing interface in the entity model, and realizes related atomic behaviors of the entities through codes;

the atomic condition model binds related application entities by setting condition parameters of related categories and type names of the root entities and the components, generates an atomic condition calculation interface, and realizes related behaviors of the entities through codes.

In one embodiment, the types of atomic behaviors in the atomic behavior model include: maneuvering control, equipment control, threat assessment, target selection, weapon launch control, communication, and simulation control;

atomic conditions in the atomic condition model include: entity state conditions, threat attack conditions, target state conditions, weapon system state conditions, behavioral conditions, temporal conditions, and environmental conditions.

In one embodiment, the model parameterization display of each model comprises the following steps: model parameters of the solid model and the component model are shown.

In one embodiment, the method further comprises the steps of: model assembly is carried out based on a model library, and the method specifically comprises the following steps:

selecting and determining a solid model from a model library, and assembling the solid model for the selected solid model, wherein the assembling of the solid model comprises the following steps: the method comprises the following steps of (1) parameter configuration of an entity model, data linked list configuration of the entity model, special parameter setting of the entity model and entity model configuration verification;

selecting a component model assembled to the selected entity model from a model library, and assembling the component model to the selected component model, wherein the assembling of the component model comprises the following steps: parameter configuration of the component model, data chain table configuration of the component model, special parameter setting of the component model and configuration verification of the component model.

In one embodiment, the parameter configuration of the solid model comprises: and establishing and maintaining a one-to-one mapping relation between the parameters of the selected entity model and the relevant table fields of the entity model in the basic database.

In one embodiment, the data linked list configuration of the entity model comprises: and establishing and maintaining a mapping relation between the data linked list of the selected entity model and a corresponding related list of the entity model in a basic database, wherein the data linked list of the entity model is used for storing a complex attribute data list of the entity model.

In one embodiment, the special parameter settings of the solid model comprise: and when the base database does not have the database table structure or the table field which is mapped, dynamically increasing the corresponding field name in the entity basic attribute table corresponding to the selected entity model in the base database.

In one embodiment, configuration verification of the mockup: the method is used for realizing the unified verification of various mapping relations established during the parameter configuration of the entity model and the data linked list configuration of the entity model and the default values of the corresponding field names added during the special parameter setting of the entity model, and determining the integrity and the correctness of the entity model configuration.

In one embodiment, in the configuration verification process of the entity model, when a verification result that mapping is missing and parameters are not matched exists, prompting and positioning are performed.

In one embodiment, after the setting of the special parameters of the solid model, the method further comprises the following steps: and adding corresponding field names which are dynamically added in a corresponding data structure which corresponds to the selected entity model and is based on the basic database.

In one embodiment, the parameter configuration of the component model includes establishing and maintaining a one-to-one mapping relationship between the model parameters of the selected component model and the associated table fields of the component model in the base database.

In one embodiment, the data link list configuration of the component model comprises: establishing and maintaining a mapping relation between a data linked list of the selected component model and a corresponding related list of the component model in a basic database; the data link list is used to store a complex attribute data list of the component model.

In one embodiment, the specific parameter settings of the component model include: and when the base database does not have the mapped database table structure or table field, dynamically adding the corresponding field name in the basic component attribute table of the base database corresponding to the selected component model.

In one embodiment, the component model configuration verification is used for realizing unified verification of various mapping relations established when the parameter configuration of the component model and the component model data linked list are configured, and default values of corresponding field names added when the special parameters of the component model are set, so as to determine the integrity and the correctness of the component model configuration.

In one embodiment, in the configuration verification process of the component model, when a verification result that mapping is missing and parameters are not matched exists, prompting and positioning are performed.

In one embodiment, after the specific parameters of the component model are set, the method further comprises the following steps: and adding corresponding field names which are dynamically added in a corresponding data structure which corresponds to the selected component model and is based on the basic database.

In one embodiment, component models that fit to the selected solid model are selected from a model library, and the selected component models are assembled. The assembly of the entity model comprises complex attribute assembly and component model assembly. The complex property group is used to determine whether the complex property is valid. The component model assembly is only complex in attribute and is used for determining whether the corresponding component model is valid or not.

When the selected entity model is an airplane entity model or a naval vessel entity model, the assembly of the component model can determine whether the component models including a sensor component model, an electronic interference device component model, a communication device component model, a weapon transmitting system component model, a target indicator component model and the like are effective or not;

when the selected entity model is the submarine entity model, the assembly of the component model can determine whether the component models including a sensor component model, an electronic interference equipment component model, a communication equipment component model, a weapon transmitting system component model and the like are effective or not;

when the selected entity model is a vehicle entity model or a personnel entity model, the assembly of the component model can be whether the component models including a sensor component, an electronic interference device component, a communication device component, a weapon firing system component, a target indicator component and the like are effective or not;

when the selected entity model is a weapon entity model, the assembly of the component model can be whether the component models including a sensor component, a communication equipment component, a combat component and the like are effective or not;

when the selected entity model is the satellite entity model, the component assembly is not contained; namely, only complex attribute assembly of the user is needed;

when the selected entity model is the ground facility entity model, the assembly of the component models can comprise whether the component models such as a sensor component, an electronic interference device component, a communication device component, a weapon launching system component and the like are effective or not;

when the selected solid model is a tactical unit aggregate solid model, the assembly of component models may include whether component models such as sensor components, jammer components, communication device components, weapon firing system components, target indicator components, etc. are valid.

In one embodiment, after performing the model parameterization display on each model, the method further includes the following steps:

parameter values of model parameters of each model are set.

Based on the scheme of the embodiment of the application, the model basic information is defined by adopting the model development tool, the model code frame is generated based on the model basic information, the model base is developed through the model code frame and the software development kit, and the model parameters of each model in the model base are set, so that when the model simulation is needed, the related entity model, the component model and the like are directly selected to be assembled through the modularized and parameterized model base, and the related model parameters are set, so that the construction of the simulation model can be quickly realized, and for a model developer, the model to be simulated can be obtained by directly selecting the model from the model base to be assembled.

Drawings

FIG. 1 is a flow diagram illustrating a method for building a modular and parameterized model architecture in one embodiment;

FIG. 2 is an interface diagram of a model development tool in one embodiment;

FIG. 3 is a diagram of an embodiment of an interface for setting custom parameters for a mockup;

FIG. 4 is a diagram of an embodiment of an interface for setting custom parameters for a component model;

FIG. 5 is a diagram of an interface for setting up an atomic behavior model, according to one embodiment;

FIG. 6 is a diagram of an interface for setting an atomic condition model, according to one embodiment;

FIG. 7 is a diagram illustrating parameterization of a model according to one embodiment;

FIG. 8 is a schematic view of a mold assembled in one embodiment;

FIG. 9 is a block diagram of a system for building a modular and parameterized model architecture in one embodiment;

FIG. 10 is a diagram showing an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Referring to fig. 1, the method for building a modular and parameterized model architecture in one embodiment includes the following steps S11 to S13.

Step S11: defining model basic information by adopting a model development tool, wherein the model basic information comprises: model basic data, model atom behaviors, model atom conditions, model object grouping, model message grouping and model object class messages, and storing the model basic information. The defined model base data may include data types such as an enumeration type and a compound type.

The model development tool refers to a tool for performing model development, and is a tool for quickly constructing a model, for example, the model development tool in the embodiment of the present application may be MDT. The model development tool provides an exemplary tool, which is a development mode based on a meta model, and supports the creation of UML diagrams, and supports reverse engineering from code to UML diagrams, and the like. In this embodiment, the model development tool may define the basic data of the model (such as enumeration type, compound type), establish object grouping, message grouping, construct object class message, define atomic behavior and atomic condition, and environment model. The model development tool in one embodiment defines model base information as shown in FIG. 2, which defines enumeration types, compound types, object classes, message classes, atomic behaviors, atomic conditions, and environmental models as shown in FIG. 2.

After the work is completed, the data defined by the model development tool is saved. These data may be stored in various possible ways. In the embodiment of the present application, the data defined by the model development tool may be stored as a file with mdef as a suffix name, and the file contains various types of model and model data information defined by the model development tool.

In conjunction with the stored mdef file, a model code framework may be generated. Specifically, based on the · mdef file, a model code framework may be generated.

In a specific embodiment, when generating the model code framework, the model development tool may generate a class according to each type of model and model-related attributes described in the mdef file, and the model-related attributes generate fields of the class, and generate an initialization interface, a periodic scheduling interface, an event processing interface, and the like (only function declaration, no function body, and the function body needs to be developed continuously) of the model, thereby generating the model code framework.

Step S12: generating a model code frame based on model basic information, and developing a model library through the model code frame and a software development toolkit, wherein the model library comprises: an entity model related to the entities of the domain, a component model determined based on the same type of components to which each entity of the domain relates, an environment model related to the environment to which the domain relates, and an atomic behavior component model related to the domain. Wherein the software development kit may be a framework-based software development kit that is configured to support the generated model code framework.

The software development kit SDK is a collection of development tools, typically a collection of development tools used to build application software for a particular software package, software framework, hardware platform, operating system, etc. It may simply provide some files of application program interfaces for a certain programming language, but may also include complex hardware that can communicate with a certain embedded system.

The model library for the simulation engine platform can be developed through the SDK matched with the model code framework, and when the model library is developed through the model code framework and the software development kit, particularly when some models which can be subsequently and actually simulated are developed, the models are assembled into specific entities.

In some embodiments of the application, the method can be applied to the field of combat simulation. The following embodiments are described by way of example as applied to the field of combat simulation.

In one embodiment, the interfaces of the established entity model include 3 kinds of interfaces, such as an initialization interface, a periodic scheduling interface, and an event processing interface. The initialization interface and the periodic scheduling interface are called to realize the relevant processing of the entity along with the time process, and the event processing interface is called to respond the relevant processing of the model event.

In one embodiment, building a solid model in a model library includes: the model parameters can be customized by 10 types of entity models, such as an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model, a squad index aggregation entity model and the like. Fig. 3 is a schematic diagram of an interface for setting custom parameters of an entity model in an embodiment, in fig. 3, a ship entity model is taken as an example, and some model parameters set in the ship entity model are shown, and when model parameters need to be added, the current-level static attribute of the ship entity model is added by clicking an "add" button in the interface shown in fig. 3. It is understood that in other embodiments, different interfaces may be presented.

The squad index aggregation entity model in the entity model is derived and generated based on the aggregation physical model, and the other entity models except the squad index aggregation entity model in the entity model are derived and generated based on the non-aggregation physical model base class.

In one embodiment, building the component model in the model library includes: 6 general component models such as a sensor component model, a communication device component model, an electronic interference device component model, a weapon launching system component model, a target indicator component model, a warhead component model and the like can define model parameters by self. Fig. 4 is a schematic diagram of an interface for setting custom parameters of a component model in an embodiment, in which, in fig. 4, a radar model is taken as an example, and some model parameters set in the radar model are shown, and in a case that model parameters need to be added, the static attributes of the radar model at this stage are added by clicking an "add" button in the interface shown in fig. 4. It is understood that in other embodiments, different interfaces may be presented.

The sensor component model has the functions of detecting and identifying the target. The sensor component model comprises a detection model, a tracking model, a recognition model and the like of the sensor. The model base class data of the sensor component model comprises sensor data, sensor types, sensor states, detection target information and the like, and the model interface of the sensor component model comprises an initialization interface, a detection interface and other interfaces.

The communication/data link device model specifies the network and role of communication, allowing the number and order of data exchanged, the target direction of information flow, and the communication time, thereby enabling data sharing. The communication/data link device model includes a communication/data link model of a communication/data link. The model base class data of the communication/data link device model comprises communication device data, communication device types, communication device states, detection target information data, network information data, data link data and the like, and the model interfaces of the communication device component model comprise initialization interfaces, communication interfaces and other interfaces.

The electronic interference equipment component model carries out interference on the communication equipment and destroys a communication network, thereby achieving the task of electronic countermeasure. The electronic jamming equipment component model comprises models such as a jamming model and a cheating model of electronic warfare equipment. The model base class data of the electronic interference equipment component model comprises electronic interference equipment data, electronic interference equipment types, electronic interference equipment states, target information data and the like, and the model interface of the electronic interference equipment component model comprises an initialization interface, an interference interface and other interfaces.

The weapon launching system component model is used for launching weapons, ammunition and striking various targets in the air, on the ground, on the water surface and under the water. The weapon firing system component model includes a fire control model of the weapon firing system equipment. The model base class data of the weapon launching system component model comprises weapon launching system data, weapon launching system states, operation target types and the like, and the model interface of the weapon launching system component model comprises an initialization interface, a weapon system launch control interface and other interfaces.

The target indicator component model is used to guide the target. The target indicator component model comprises a data fusion model of the target indicating equipment, a target recognition model and the like. The model base class data of the target indicator component model comprises target indicator data, target indicator states, target information data and the like, and the model interface of the target indicator component model comprises an initialization interface, a guide interface and the like.

The warhead component model is composed of weapons ammunition and is used for killing and destroying targets. The warhead component model comprises a killing model of warhead equipment and the like. The model base class data of the warhead component model comprises warhead data, and the model interface of the warhead component model comprises an initialization interface, a damage interface and other interfaces.

In one embodiment, the environment models built in the model library include an astronomical environment model, a geographic environment model, a meteorological environment model, a hydrologic environment model and the like.

The astronomical environment model development interface comprises an interface for acquiring simulation astronomical time, an interface for setting the simulation astronomical time and the like.

The geographic environment model development interface comprises interfaces for acquiring the elevation of the specified position and the like.

The meteorological environment model development interface comprises an interface for acquiring the wind speed and the wind direction of a specified position, an interface for acquiring the precipitation level and the precipitation amount of the specified position, an interface for acquiring the temperature of the specified position, an interface for acquiring the relative humidity of the specified position, an interface for acquiring the visibility of the specified position, an interface for acquiring the cloud cover level, the cloud height and the cloud thickness of the specified position and the like. Wherein, the interface of the precipitation level and the precipitation of acquireing the assigned position can only be one interface to the precipitation level and the precipitation of acquireing the assigned position simultaneously also can be including two interfaces: one precipitation level acquisition interface for acquiring the precipitation level of the designated position, and the other precipitation level acquisition interface for acquiring the precipitation amount of the designated position. In the embodiment of the present application, only one interface is taken as an example for description. In addition, the interface for acquiring the cloud volume grade, the cloud height and the cloud thickness at the specified position may have only one interface to acquire the cloud volume grade, the cloud height and the cloud thickness at the specified position at the same time, or may include three interfaces: one interface for acquiring the cloud amount grade of the specified position, one interface for acquiring the cloud height of the specified position and one interface for acquiring the cloud thickness of the specified position. In the embodiment of the present application, only one interface is taken as an example for description.

The hydrological environment model development interface comprises an interface for acquiring the sea condition grade of a specified position, an interface for acquiring the wave direction of the wave height of the specified position, an interface for acquiring the tide of the specified position, an interface for acquiring the hydrological grade of the specified position and the like, an interface for acquiring the water temperature of the specified position, an interface for acquiring the salinity of the specified position and an interface for acquiring the density of the specified position.

In one embodiment, the atomic behavior component models built in the model library include an atomic behavior model and an atomic condition model, wherein the atomic behavior model and the atomic condition model are derived based on a base class.

The atomic behavior model binds related application entities by setting behavior parameters of categories and type names associated with the entities, generates an atomic behavior message processing interface in the entity model, and realizes related atomic behaviors of the entities through codes. The types of atomic behaviors in the atomic behavior model include: maneuvering control, equipment control, threat assessment, target selection, weapon launch control, communication, simulation control, and the like. Fig. 5 is a schematic interface diagram of setting an atomic behavior model in an embodiment, and in fig. 5, a maneuver control behavior is taken as an example for explanation, and a specific behavior name and information such as a corresponding behavior default value are set, and when the behavior name needs to be added, the behavior name, the information such as a member name, a type, a special type, a unit, a value range, and a default value of the behavior are added by clicking an "add" button in the interface shown in fig. 5. It is understood that in other embodiments, different interfaces may be presented.

The atomic condition model binds related application entities by setting condition parameters of related categories and type names of the root entities and the components, generates an atomic condition calculation interface, and realizes related behaviors of the entities through codes. Atomic conditions in the atomic condition model include: entity state conditions, threat attack conditions, target state conditions, weapon system state conditions, behavioral conditions, temporal conditions, environmental conditions, and the like. Fig. 6 is an interface schematic diagram of setting an atomic condition model in an embodiment, and fig. 6 illustrates an example of behavior conditions of a target attack, which is set with behavior conditions of specific operators, and can be selected by a checking manner. In fig. 6, all the conditions are selected as an example, that is, the conditions are considered to be satisfied in any case, and it is understood that in other embodiments, only some of the conditions may be selected, for example, only the condition shown in fig. 6 is selected to be greater than or equal to. It is understood that in other embodiments, different interfaces may be presented.

Step S13: and setting model parameters of each model in the model library, and carrying out model parameterization display on each model.

After the simulation models are set, the simulation models can be subjected to model parameterization display, wherein model parameters of entity models (an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model, a squad index aggregation entity model and the like) and component models (a sensor component model, a communication equipment component model, an electronic interference equipment component model, a weapon launching system component model, a target indicator component model, a fighting part component model and the like) are mainly displayed. A schematic diagram of the model parameterization display in one embodiment is shown in fig. 7.

As shown in fig. 7, the basic parameters of the airplane solid model are set as follows: the model parameters of the radar component model in the set sensor component model comprise: the parameters of the action distance, the peak power, the scanning interval, the radar blind time and the like, and the set model parameters of the missile weapon system component model in the weapon launching system component model comprise parameters of the hanging rack capacity, the maximum range, the preparation time, the number of launching tubes and the like.

After the model parameters of each model in the model library are set, or after each model is subjected to model parameterization display, model assembly can be further carried out based on the model library.

The model assembly is performed based on a model library, and specifically comprises a step 1 and a step 2.

Step 1: selecting and determining a solid model from a model library, and assembling the solid model for the selected solid model, wherein the assembling of the solid model comprises the following steps: the method comprises the steps of parameter configuration of an entity model, data linked list configuration of the entity model, special parameter setting of the entity model and entity model configuration verification.

From the entity types, the entity models comprise an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model, a team index aggregation entity model and the like. From the model type, a solid model generally includes a physical model, a mobility model, a damage model, etc. of the solid.

In one embodiment, the parameter configuration of the solid model is mainly used to implement the parameter configuration of the solid model, and includes: and establishing and maintaining a one-to-one mapping relation between the parameters of the selected entity model and the relevant table fields of the entity model in the basic database. And when the mapping relation is established between the model parameters of the entity model and the corresponding table fields, the automatic conversion of the table field units and the model parameter units is supported.

In one embodiment, the data chain table configuration of the entity model for implementing the data chain table configuration of the entity model includes: and establishing and maintaining the mapping relation between the data linked list of the selected entity model and the corresponding related list of the entity model in the basic database. The data link table of the solid model is used for storing a complex attribute data list of the solid model, such as data in a weapon mounting and ammunition distribution scheme table, or storing a component assembly data list of the solid model, such as a plurality of sensors, electronic warfare equipment and the like which are physically assembled. And the display of a component list and a complex attribute list of the entity corresponding to the basic database can be controlled through the configuration of the data linked list.

In one embodiment, the special parameter settings of the mockup are used to implement the setting of special parameters in the mockup, and these special parameters do not have corresponding database table structures or table fields to be mapped initially and belong to parameters necessary for model operation. The method comprises the following steps: and when the base database does not have the database table structure or the table field which is mapped, dynamically increasing the corresponding field name in the entity basic attribute table corresponding to the selected entity model in the base database.

After the special parameter setting of the entity model is completed, corresponding field names which are dynamically added can be further added in a corresponding data structure which corresponds to the selected entity model and is based on the basic database. Thereby realizing the updating of the entity model in the model library.

Then, through the setting of the special parameter, the corresponding field name can be dynamically increased in the entity basic attribute table corresponding to the basic database, and when the entity model configuration is entered again later, the special parameter is automatically attributed to the entity model parameter configuration, thereby ensuring the model updating, namely, the dynamic field increasing can be carried out on the data structure of the basic database based on the corresponding data structure of the basic database, and the flexibility and the mutual matching of the model design and the database structure design are improved.

In one embodiment, configuration verification of the mockup: the method is used for realizing the unified verification of various mapping relations established during the parameter configuration of the entity model, the data linked list configuration of the entity model, default values of corresponding field names added during the special parameter setting of the entity model and the like, and determining the integrity and the correctness of the entity model configuration.

In the configuration verification process of the entity model, when the verification result of mapping missing and parameter mismatching exists, prompting and positioning are carried out. For example, the existing problems are prompted, and particularly which configuration item has a problem, so that a user can quickly locate the problem of checking the configuration item with the problem to adjust so as to ensure the integrity and correctness of the entity model configuration.

Step 2: selecting a component model assembled to the selected entity model from a model library, and assembling the component model to the selected component model, wherein the assembling of the component model comprises the following steps: parameter configuration of the component model, data chain table configuration of the component model, special parameter setting of the component model, configuration verification of the component model and the like.

From the component types, the component models include a sensor component model, a communication/data link device model, an electronic jamming device component model, a weapons launch systems component model, a target indicator component model, a warhead component model, and the like. The sensor component model generally comprises a detection model, a tracking model, an identification model and the like of the sensor from the aspect of model type; the communication/data link device model generally includes a communication/data link model of a communication/data link, etc.; the electronic jamming equipment component model generally comprises a jamming model, a cheating model and the like of electronic warfare equipment; weapon firing system component models generally include fire control models of weapon firing system equipment, and the like; the target indicator component model generally comprises a data fusion model, a target recognition model and the like of the target indicating equipment; the warhead component models generally include a killer model of the warhead equipment, and the like.

Selecting, from a model library, a component model to assemble to the selected solid model, comprising:

when the selected solid model is an airplane solid model, the assembled component models include a sensor component model, an electronic interference device component model, a communication device component model, a weapon firing system component model, and a target indicator component model.

And when the selected entity model is a ship entity model, assembling component models including a sensor component model, an electronic interference equipment component model, a communication equipment component model, a weapon transmitting system component model and a target indicator component model.

When the selected solid model is a submarine solid model, the assembled component models comprise a sensor component model, an electronic interference device component model, a communication device component model and a weapon launching system component model.

When the selected physical model is a vehicle physical model, the assembled component models include a sensor component, an electronic jamming device component, a communication device component, a weapon firing system component, and an object indicator component.

In one embodiment, the parameter configuration of the component model, which is used to implement the parameter configuration of the component model, mainly includes establishing and maintaining a one-to-one mapping relationship between the model parameters of the selected component model and the relevant table fields of the component model in the basic database. And when the mapping relation between the model parameters and the relevant table fields is established, the automatic conversion of the table field units and the model parameter units is supported.

In one embodiment, the data chain table configuration of the component model, which is used to implement the data chain table configuration of the component model, mainly includes: and establishing and maintaining the mapping relation between the data linked list of the selected component model and the corresponding related list of the component model in the basic database. The data link list is used for storing a complex attribute data list of the component model, such as a weapon list which can be fired and is described in a weapon firing system component, or storing a component assembly data list of the component model, such as a sensor list assembled by the weapon firing system component. The display of a component list and a complex attribute list of the corresponding components of the basic database can be controlled through the configuration of the data linked list.

In one embodiment, the specific parameter settings of the component model are used to implement the setting of specific parameters in the component model, and these specific parameters initially have no corresponding database table structure or table field to be mapped and belong to parameters necessary for model operation. The method comprises the following steps: and when the base database does not have the mapped database table structure or table field, dynamically adding the corresponding field name in the basic component attribute table of the base database corresponding to the selected component model.

After the special parameter setting of the component model is completed, corresponding field names which are dynamically added can be added in a corresponding data structure which corresponds to the selected component model and is based on the basic database. Thereby realizing the update of the component model in the model library.

By setting special parameters, the corresponding field names can be dynamically increased in the basic attribute table of the corresponding components of the basic database, and the special parameters are automatically assigned to the parameter configuration of the component model when the component model configuration is entered again later.

In one embodiment, the component model configuration verification is used for uniformly verifying various mapping relations established when the parameter configuration of the component model and the component model data linked list are configured, default values of corresponding field names added when the special parameters of the component model are set, and the like, and determining the integrity and the correctness of the component model configuration.

In the configuration verification process of the component model, when the verification result of mapping missing and parameter mismatching exists, prompting and positioning are carried out. For example, the existing problems are prompted, and specifically, which configuration item has a problem, so that a user can conveniently and quickly locate the problem of the configuration item which is checked to have the problem, and the completeness and the correctness of the component model configuration are ensured.

After model componentization (such as assembly of a solid model and assembly of a component model) is completed, assembly of the simulation model can be displayed, and particularly, configuration relations among the solid model, the component model, complex attributes and the like can be displayed.

Taking the solid model as an example:

the complex attributes of the airplane entity model in the entity models comprise complex attributes of maneuvering performance, radar signal characteristics, optical signal characteristics, dock/vehicle carrier facilities, military standard and the like, and the assembled component models can comprise component models such as a sensor component model, an electronic interference device component model, a communication device component model, a weapon transmitting system component model, a target indicator component model and the like.

The complex attributes of the ship entity model in the entity model comprise complex attributes such as maneuvering performance, radar signal characteristics, acoustic signal characteristics, optical signal characteristics, aviation carrier facilities, dock/vehicle carrier facilities, personnel carrier facilities, bomb configuration schemes, military standard and the like, and the assembled component model can comprise component models such as a sensor component model, an electronic interference equipment component model, a communication equipment component model, a weapon transmitting system component model and a target indicator component model.

The complex attributes of the submarine entity model in the entity models comprise complex attributes such as maneuvering performance, radar signal characteristics, acoustic signal characteristics, optical signal characteristics, personnel carrier facilities, bullet distribution schemes, military standards and the like, and the assembled component models can comprise component models such as a sensor component model, an electronic interference equipment component model, a communication equipment component model and a weapon launching system component model.

The vehicle entity model complex attributes in the entity model comprise complex attributes such as maneuvering performance, radar signal characteristics, optical signal characteristics, dock/vehicle carrier facilities, ammunition distribution schemes, military standards, false targets and the like, and the component assembly comprises components such as a sensor component, an electronic interference device component, a communication device component, a weapon transmitting system component and a target indicator component.

The complex attributes of the personnel entity model in the entity model comprise complex attributes of maneuvering performance, radar signal characteristics, optical signal characteristics, acoustic signal characteristics, bullet distribution schemes, military standards, false targets and the like, and the components comprise sensor components, electronic interference equipment components, communication equipment components, weapon emission system components, target indicator components and the like.

The weapon entity model complex attributes in the entity model comprise complex attributes such as maneuvering performance, radar signal characteristics, optical signal characteristics, acoustic signal characteristics, a hitting target list, military marks and the like, and the component assembly comprises components such as a sensor component, a communication equipment component and a combat component.

The complex attributes of the satellite solid model in the solid model comprise radar signal characteristics, optical signal characteristics, aviation carrier facilities, dock/vehicle carrier facilities, bullet distribution schemes, personnel carrier facilities, point/line/belt/surface areas, circular areas, military marks, false targets and other complex attributes, and do not contain component assembly.

The complex attributes of the fixed facility model in the solid model comprise radar signal characteristics, optical signal characteristics, aviation carrier facilities, dock/vehicle carrier facilities, ammunition distribution schemes, personnel carrier facilities, points/lines/bands/surface areas, circular areas, military marks, decoys and other complex attributes, and the assembly of the components comprises sensor components, electronic interference equipment components, communication equipment components, weapon launching system components and other components.

The complex attributes of the entity model aggregated by the combat units in the entity model comprise maneuvering performance, radar signal characteristics, optical signal characteristics, bullet distribution schemes, point/line/band/surface areas, circular areas, military marks, false targets and other complex attributes, and component assembly comprises sensor components, electronic interference equipment components, communication equipment components, weapon launching system components, target indicator components and other components.

The complex attributes of the squad model in the entity model comprise complex attributes of maneuvering performance, radar signal characteristics, optical signal characteristics, acoustic signal characteristics, ammunition distribution schemes, organizational sources, non-organizational sources, squad distribution areas, military marks, false targets and the like, and the component assembly comprises components such as a sensor component, an electronic interference device component, a communication device component, a weapon launching system component and a target indicator component.

The complex attributes of the sensor component model in the component model comprise complex attributes such as detection target type and wave band, and do not contain component assembly.

The jammer device component model in the component model is free of complex attributes and component assemblies.

The complex attributes of the communication device components in the component model include the band, etc., and do not include component assembly.

The complex attributes of the weapon launching system component model in the component model comprise weapon type configuration and the like, and the component assembly comprises a sensor component, an electronic interference device component, a communication device component and the like.

The target indicator component model in the component model is free of complex properties and component assemblies.

The warhead component models in the component models do not contain complex attributes and component assemblies.

After the model assembly is carried out, specific parameter values can be further set for each model parameter of the assembled model. An illustration of the assembly relationship of the assembled model in one embodiment is shown in FIG. 8. In FIG. 8, the solid model is configured with basic attributes: maneuverability, maximum voyage, lift limit, aviation fuel oil and the like, and is configured with a complex attribute model: maneuvering performance, signal characteristics and the like, and AN AN/APG-66 type fire control radar component model and AN AIM-9M type sidewinder air-to-air missile component model are assembled into the entity model. The complex attribute of the maneuvering performance is specifically matched with the complex attribute of the maneuvering mode of the F-16 aircraft, the configured model parameters comprise speed types, default speeds, fuel consumption and the like, the complex attribute of the optical signal characteristics of the F-16 aircraft is specifically matched with the signal characteristics, the configured model parameters comprise parameters such as optical types, detection distances, identification distances and the like, the configured model parameters of the AN/APG-66 type fire control radar component model comprise parameters such as action distances, peak power, scanning intervals and the like, and the configured model parameters of the AIM-9M type sidewinder air-to-air missile component model comprise parameters such as rack capacity, maximum range, preparation time and the like.

It should be understood that, although the steps in the flowchart of fig. 1 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 1 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.

In one embodiment, as shown in fig. 9, a modeling system for modeling componentization and parameterization is provided, which may be a part of a computer device using software modules or hardware modules, or a combination of the two, and specifically includes:

the basic information definition module 901 defines model basic information by using a model development tool, where the model basic information includes: model basic data, model atom behaviors, model atom conditions, model object grouping, model message grouping and model object class messages, and storing the model basic information, wherein the model basic data comprises: enumerating types and composite types;

the model library development module 902 generates a model code frame based on the model basic information, and develops a model library through the model code frame and a software development kit, wherein the model library comprises: an entity model related to the entities of the field, a component model determined based on the same type of components related to each entity of the field, an environment model related to the environment of the field, and an atomic behavior component model related to the field;

and the parameterization module 903 is used for setting model parameters of each model in the model library and carrying out model parameterization display on each model.

In one embodiment, the solid model includes: the system comprises an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model and a squad index aggregation entity model.

In one embodiment, the component model includes: a sensor component model, a communication device component model, an electronic jamming device component model, a weapons discharge system component model, a target indicator component model, and a warhead component model.

In one embodiment, the model base class data of the sensor component model comprises sensor data, sensor types, sensor states and detection target information, and the model interface of the sensor component model comprises an initialization interface and a detection interface.

In one embodiment, the model base class data of the communication device component model includes communication device data, a communication device type, a communication device state, probe target information data, network information data, and data link data, and the model interface of the communication device component model includes an initialization interface and a communication interface.

In one embodiment, the model base class data of the electronic jamming device component model includes electronic jamming device data, electronic jamming device type, electronic jamming device state and target information data, and the model interface of the electronic jamming device component model includes an initialization interface and a jamming interface.

In one embodiment, the model base class data of the weapon firing system component model comprises weapon firing system data, weapon firing system state and operation target type, and the model interface of the weapon firing system component model comprises an initialization interface and a weapon system emission control interface.

In one embodiment, the model base class data of the target indicator component model includes target indicator data, target indicator states, and target information data, and the model interface of the target indicator component model includes an initialization interface and a boot interface.

In one embodiment, the model base class data of the warhead component model includes warhead data, and the model interface of the warhead component model includes an initialization interface and a damage interface.

In one embodiment, the astronomical environment model development interface comprises an interface for acquiring simulated astronomical time and an interface for setting the simulated astronomical time.

The geographic environment model development interface includes an interface to obtain elevation at a specified location.

The meteorological environment model development interface comprises an interface for acquiring wind speed and wind direction at a specified position, an interface for acquiring precipitation level and precipitation amount at the specified position, an interface for acquiring temperature at the specified position, an interface for acquiring relative humidity at the specified position, an interface for acquiring visibility at the specified position, and an interface for acquiring cloud cover level, cloud height and cloud thickness at the specified position.

The hydrological environment model development interface comprises an interface for acquiring the sea state grade of a specified position, an interface for acquiring the wave direction of the wave height of the specified position, an interface for acquiring the tide direction of the specified position, an interface for acquiring the hydrological grade of the specified position, an interface for acquiring the water temperature of the specified position, an interface for acquiring the salinity of the specified position and an interface for acquiring the density of the specified position.

In one embodiment, the types of atomic behaviors in the atomic behavior model include: maneuver control, equipment control, threat assessment, target selection, weapon launch control, communication, and simulation control.

In one embodiment, the atomic conditions in the atomic condition model include: entity state conditions, threat attack conditions, target state conditions, weapon system state conditions, behavioral conditions, temporal conditions, and environmental conditions.

In one embodiment, the method further comprises: the assembly module 904, which performs model assembly based on the model library, specifically includes:

In one embodiment, the configuration module 904 establishes and maintains a one-to-one mapping relationship between the parameters of the selected entity model and the relevant table fields of the entity model in the base database to implement the parameter configuration of the entity model.

In one embodiment, the assembly module 904 establishes and maintains a mapping relationship between the data linked list of the selected entity model and the corresponding related table of the entity model in the base database, and the data linked list of the entity model is used to store the complex attribute data list of the entity model, so as to implement the data linked list configuration of the entity model.

In one embodiment, the assembly module 904 includes: and when the base database does not have a database table structure or table fields which are mapped, dynamically adding corresponding field names in the entity basic attribute table corresponding to the selected entity model in the base database so as to realize the special parameter setting of the entity model.

In one embodiment, the configuration module 904 implements a unified verification of various mapping relationships established when configuring parameters of the entity model, configuring a data linked list of the entity model, and default values of corresponding field names added when setting special parameters of the entity model, and determines the integrity and correctness of the configuration of the entity model, so as to implement the configuration verification of the entity model.

In one embodiment, the assembly module 904 performs prompting and positioning when there is a missing mapping and a non-parameter matching verification result in the configuration verification process of the mockup.

In one embodiment, the assembly module 904, after setting the specific parameters of the entity model, further adds the corresponding field names that are dynamically added to the corresponding data structures based on the underlying database corresponding to the selected entity model.

when the selected entity model is the submarine entity model, the assembly of the assembled component model can be whether the component models including a sensor component model, an electronic interference equipment component model, a communication equipment component model, a weapon transmitting system component model and the like are effective or not;

when the selected entity model is a weapon entity model, the assembly of the assembled component model can be whether the component models including a sensor component, a communication equipment component, a combat component and the like are effective or not;

when the selected entity model is the satellite entity model, the method does not contain component assembly, namely only complex attribute assembly of the selected entity model is needed;

when the selected solid model is a ground facility solid model, the component models comprise a sensor component, an electronic interference device component, a communication device component and a weapon launching system component;

where the selected solid model is a tactical unit aggregate solid model, the assembly of the assembled component models may include whether component models of sensor components, jammer components, communication device components, weapon firing system components, target indicator components, etc. are valid.

In one embodiment, the parameterization module 903 further sets parameter values of model parameters of each model after performing model parameterization display on each model.

For specific limitations of the building system of the modular and parameterized model architecture, reference may be made to the above limitations of the building method of the modular and parameterized model architecture, which are not described in detail herein. The various modules in the modular and parameterized model architecture building system described above may be implemented in whole or in part in software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal or a server, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a method of building a modular and parameterized model architecture. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of building a modular and parameterized model architecture, the method comprising:

defining model base information by adopting a model development tool, wherein the model base information comprises: model basic data, model atom behaviors, model atom conditions, model object grouping, model message grouping and model object type messages, and storing the model basic information;

generating a model code framework based on the model basic information, and developing a model library through the model code framework and a software development kit, wherein the model library comprises: an entity model related to the entities of the field, a component model determined based on the same type of components related to each entity of the field, an environment model related to the environment of the field, and an atomic behavior component model related to the field;

2. The method of claim 1, further comprising the step of: and performing model assembly based on the model library, which specifically comprises the following steps:

selecting and determining a solid model from the model library, and assembling the solid model to the selected solid model, wherein the assembling of the solid model comprises the following steps: the method comprises the following steps of (1) parameter configuration of an entity model, data linked list configuration of the entity model, special parameter setting of the entity model and entity model configuration verification;

selecting a component model assembled to the selected entity model from the model library, and assembling the component model to the selected component model, wherein the assembling of the component model comprises the following steps: parameter configuration of the component model, data chain table configuration of the component model, special parameter setting of the component model and configuration verification of the component model.

3. The method of claim 2, comprising at least one of:

the parameter configuration of the entity model comprises the following steps: establishing and maintaining a one-to-one mapping relation between the parameters of the selected entity model and relevant table fields of the entity model in a basic database;

the data linked list configuration of the entity model comprises the following steps: establishing and maintaining a mapping relation between the data linked list of the selected entity model and a corresponding related list of the entity model in a basic database, wherein the data linked list of the entity model is used for storing a complex attribute data list of the entity model;

the special parameter setting of the entity model comprises the following steps: dynamically adding corresponding field names in an entity basic attribute table corresponding to the selected entity model in the basic database when the basic database does not have a mapped database table structure or table fields;

configuration verification of the solid model: the method is used for realizing various mapping relations established during parameter configuration of the entity model and data linked list configuration of the entity model, and the unified verification of default values of corresponding field names added during special parameter setting of the entity model, and determining the integrity and correctness of the entity model configuration;

the parameter configuration of the component model comprises the steps of establishing and maintaining a one-to-one corresponding mapping relation between the model parameters of the selected component model and relevant table fields of the component model in a basic database;

the data linked list configuration of the component model comprises the following steps: establishing and maintaining a mapping relation between a data linked list of the selected component model and a corresponding related list of the component model in a basic database; the data linked list is used for storing a complex attribute data list of the component model;

the special parameter setting of the component model comprises the following steps: when the base database does not have a database table structure or table fields which are mapped, dynamically adding corresponding field names in a basic component attribute table of the base database corresponding to the selected component model;

and the component model configuration verification is used for realizing various mapping relations established during the configuration of the parameters of the component model and the configuration of the component model data linked list, and uniformly verifying default values of corresponding field names added during the setting of special parameters of the component model to determine the integrity and the correctness of the component model configuration.

4. The method of claim 3, comprising at least one of:

after the special parameter setting of the entity model, the method further comprises the following steps: adding corresponding field names which are dynamically added to corresponding data structures which correspond to the selected entity models and are based on a basic database;

in the configuration verification process of the entity model, when a verification result of mapping deficiency and parameter mismatching exists, prompting and positioning are carried out;

after the special parameters of the component model are set, the method further comprises the following steps: adding corresponding field names which are dynamically added to corresponding data structures which correspond to the selected component models and are based on a basic database;

in the configuration verification process of the component model, when the verification result of mapping missing and parameter mismatching exists, prompting and positioning are carried out.

5. The method of claim 1, comprising at least one of:

the solid model comprises: the system comprises an airplane entity model, a naval vessel entity model, a submarine entity model, a vehicle entity model, a personnel entity model, a weapon entity model, a satellite entity model, a ground facility entity model, a combat unit aggregation entity model and a squad index aggregation entity model;

the component model includes: a sensor component model, a communication device component model, an electronic jamming device component model, a weapon launching system component model, a target indicator component model, and a warhead component model;

the environment model comprises an astronomical environment model, a geographical environment model, a meteorological environment model and a hydrological environment model;

the atomic behavior component model comprises an atomic behavior model and an atomic condition model.

6. The method of claim 5, comprising at least one of:

the squad index aggregation entity model in the entity model is derived and generated based on an aggregation physical model, and the other entity models except the squad index aggregation entity model in the entity model are derived and generated based on a non-aggregation physical model base class;

the model base class data of the sensor component model comprises sensor data, sensor types, sensor states and detection target information, and the model interface of the sensor component model comprises an initialization interface and a detection interface;

the model base class data of the communication equipment component model comprises communication equipment data, communication equipment types, communication equipment states, detection target information data, network information data and data link data, and the model interface of the communication equipment component model comprises an initialization interface and a communication interface;

the model base class data of the target indicator component model comprises target indicator data, a target indicator state and target information data, and the model interface of the target indicator component model comprises an initialization interface and a guide interface;

the model base class data of the warhead component model comprises warhead data, and the model interface of the warhead component model comprises an initialization interface and a damage interface;

the astronomical environment model development interface comprises an interface for acquiring simulation astronomical time and an interface for setting the simulation astronomical time;

the hydrological environment model development interface comprises an interface for acquiring the sea condition grade of a specified position, an interface for acquiring the wave direction of the wave height of the specified position, an interface for acquiring the tide of the specified position, an interface for acquiring the hydrological grade of the specified position, an interface for acquiring the water temperature of the specified position, an interface for acquiring the salinity of the specified position and an interface for acquiring the density of the specified position.

7. The method of claim 1, wherein the atomic behavior component model comprises an atomic behavior model and an atomic condition model, wherein the atomic behavior model and the atomic condition model are derived based on a base class:

the atomic behavior model binds related application entities by setting behavior parameters of category and type names associated with the entities, generates an atomic behavior message processing interface in the entity model, and realizes related atomic behaviors of the entities through codes;

8. The method of claim 1, comprising at least one of:

the interface of the entity model comprises an initialization interface, a periodic scheduling interface and an event processing interface, the periodic scheduling interface is called to realize the relevant processing of the entity along with the time process by calling the initialization interface, and the event processing interface is called to respond the relevant processing of the model event;

carrying out model parameterization display on each model, comprising the following steps: model parameters of the solid model and the component model are shown.

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 8.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 8.