Resource level grouping-based LVC simulation resource management method

Abstract

An LVC simulation resource management method based on resource level grouping comprises the following steps: performing hierarchical registration management on various LVC simulation resources according to three levels of an object model, an application program and a physical host to obtain LVC test resource components of different levels; according to the requirement of a simulation object unit in a simulation scene, assembling the LVC test resource components of different levels into an LVC resource unit deployment package, and forming a configuration scheme for the LVC test; according to the configuration scheme of the LVC test, the LVC resource unit deployment package is distributed to a specified physical host, starting preparation of LVC simulation resources is completed by starting an LVC test application program, and LVC simulation resource management is completed.

Description

Technical Field

[0001] This invention relates to an LVC simulation resource management method based on resource hierarchy grouping, belonging to the field of LVC simulation technology. Background Technology

[0002] LVC simulation refers to simulation that combines live, virtual, and construct elements. Implementing LVC simulation requires a distributed simulation support architecture for underlying communication and the use of technologies such as gateways, adapters, and wrappers to encapsulate and integrate heterogeneous simulation resources. LVC simulation systems involve a large number of hardware and software resources, necessitating dynamic and flexible management of these resources to ensure the reliability of large-scale distributed systems and prevent system failures or shortages due to resource outages.

[0003] Traditional LVC simulation systems typically manage objects or sets of objects within the simulation scene, such as a mobile device equipped with state acquisition hardware, a human-in-the-loop VR simulation system for driving simulation, or a computational generation system for generating object information. This approach limits the penetration of LVC resource management and, due to the restriction on the deployment of simulation models, hinders the online reconstruction of various virtual and physical LVC simulation resources. Summary of the Invention

[0004] The technical problem solved by this invention is to overcome the shortcomings of the prior art and provide an LVC simulation resource management method based on resource hierarchical grouping, which can significantly improve the penetration of resource management, enhance the composability of LVC resources, and improve utilization efficiency.

[0005] The technical solution of this invention is: an LVC simulation resource management method based on resource hierarchy grouping, comprising:

[0006] Various LVC simulation resources are registered and managed hierarchically according to three levels: object model, application program, and physical host, resulting in LVC experimental resource components at different levels;

[0007] According to the needs of the simulation object units in the simulation scenario, LVC test resource components at different levels are assembled into LVC resource unit deployment packages to form a configuration scheme for LVC tests;

[0008] According to the configuration scheme of the LVC experiment, the LVC resource unit deployment package is distributed to the designated physical host. The LVC simulation resource is activated and managed by launching the LVC experiment application.

[0009] Preferably, the object model, application, and physical host are as follows:

[0010] The object model is a state object model and a method object model developed based on the standard of TENA middleware, and exists in the form of dynamic link libraries. The state object model is used to describe the data model of the simulation object corresponding to the LVC simulation resource in the LVC simulation scenario, that is, to describe the values ​​of various parameters of the simulation object. The method object model is used to describe the state evolution of the simulation object or the interaction process between two simulation objects in the LVC scenario.

[0011] An application refers to an executable program developed based on the TENA middleware standard that can load and run the corresponding object model; it can implement state object model publishing / subscription, state object model query / assignment operations, method object model invocation, operation of specific hardware functions, and configure logical time progression, method object model invocation order and conditions, publish / subscribe / relationship, and specific hardware operation parameters based on the Lua scripting language;

[0012] A physical host is a computer required for an application to run. It has TCP / IP protocol communication capabilities, the ability to run Windows / Linux operating systems, and can be bound to specific hardware interfaces or simulated devices as needed. It can also be installed on specific physical equipment as needed.

[0013] Preferably, various LVC simulation resources are registered and managed hierarchically according to three levels: object model, application program, and physical host, as follows:

[0014] Based on the hierarchy of object model, application, and physical host, the dynamic link library of the object model is mapped and registered with its corresponding state object model instance and method object model;

[0015] Map and register the application's executable file with its required configuration script template files and hardware interface plugin dynamic link libraries;

[0016] Map and register the physical host's name, network configuration information, and physical hardware.

[0017] Preferably, the simulation objects include physical object units, simulator object units, and constructed simulation object units;

[0018] A physical object unit refers to a simulation object unit that is completely bound to the physical host, application program, and object model. In the LVC simulation scenario, it can only represent a specific physical equipment object.

[0019] A simulator object unit refers to a simulation object unit that is completely bound to the application and the physical host. The application contains dedicated programs and interfaces that operate on specific hardware resources. In the LVC simulation scenario, it represents a certain type of equipment object and can represent multiple equipment objects of the same type as needed according to the principle of time-division multiplexing.

[0020] Constructing a simulation model object unit refers to a simulation object unit where there is no complete binding relationship between the object model, application, and physical host. Any object model is randomly combined with an application and deployed to any physical host, representing all mathematical simulation objects in the LVC simulation scenario.

[0021] Preferably, the resource component configuration includes three steps: simulation object unit assembly, LVC resource unit configuration, and LVC resource unit packaging.

[0022] Preferably, the simulation object unit assembly includes:

[0023] For physical equipment objects, it is necessary to bind the object model, application, and physical host, establish a mapping relationship between the state object model and the physical host through the physical equipment state data collected by the application, establish a mapping relationship between the interaction methods in the method object model and the hardware interface plug-in in the application, and establish a mapping relationship between the hardware interface plug-in of the application and the hardware devices installed on the physical host.

[0024] For simulator objects, it is necessary to bind the application to the physical host, establish a mapping between the application's hardware interface plugins and the hardware devices installed on the physical host, and establish a many-to-one mapping between a set of state object model instances and the accessible parameters in the application.

[0025] For constructing simulation objects, multiple physical hosts are specified, with each physical host having at least one application deployed as the runnable application for the constructed simulation object. In actual operation, the running position of the constructed simulation object is dynamically adjusted by comprehensively considering network load and computing power balance.

[0026] Preferably, the LVC resource unit configuration requires configuring the initial values ​​of the state object model, whether to publish the state object model, and the list of state object models that the method object model needs to subscribe to for the object model of the LVC resource unit; for the application of the LVC resource unit, it requires configuring the logical time progression mode, the method object model call order and conditions, publish-subscribe / relationship, the required hardware interface plugin dynamic libraries, and the corresponding specific hardware running parameters in the application script configuration file; and for the host of the LVC resource unit, it requires configuring its host's TCP / IP communication address information.

[0027] Preferably, LVC resource unit packaging refers to packaging the object model, application, application script configuration file, hardware interface plug-in, and host configuration file into a compressed file to form an LVC resource unit deployment package that maps to a specific simulation object unit.

[0028] Preferably, according to the LVC experiment configuration scheme, the LVC resource unit deployment package is distributed to the designated physical host, and the LVC simulation resource activation preparation is completed by launching the LVC experiment application, including the following steps:

[0029] The LVC resource unit deployment package is distributed to the designated physical host via the file transfer protocol;

[0030] On the specified physical host, extract the LVC resource unit deployment package to the specified runtime directory;

[0031] Remotely launch applications within an LVC resource unit via SSH;

[0032] After the application starts, it initializes the state object model based on the application script configuration file and adds it to the LVC simulation test system.

[0033] Compared with the prior art, the present invention has the following advantages:

[0034] (1) Based on the vertical management of simulation objects, a horizontal hierarchical management is established based on the resource composition characteristics of simulation objects, which makes it easier to extract the common characteristics of different simulation objects.

[0035] (2) Based on the different binding degrees of object models, applications and hosts, LVC is classified and managed to release the reconfigurability of simulators and construction simulation models as much as possible.

[0036] (3) Based on the resource hierarchical management model, the virtual and real interaction are separated, the virtual interaction is unified into the interaction of the object model, and the virtual and real interaction is unified into the mode of calling specific hardware resources based on the method object model, which facilitates the standardization of the LVC system interaction interface and the encapsulation and reuse of heterogeneous resources. Attached Figure Description

[0037] Figure 1 This is a schematic diagram of the LVC resource hierarchy management model of the present invention;

[0038] Figure 2 This is a flowchart of the LVC simulation resource management process for resource hierarchical grouping in this invention. Detailed Implementation

[0039] The purpose of this invention is to propose a resource management method for LVC simulation based on resource hierarchical grouping.

[0040] The LVC simulation resources targeted by this method consist of an object model, an application program, and a physical host, wherein:

[0041] The object model consists of a state object model and a method object model developed based on the TENA middleware standard, and exists as a dynamic link library. The state object model describes the data model of the simulation object corresponding to the LVC simulation resource in the LVC simulation scenario, that is, it describes the values ​​of various parameters of the simulation object; the method object model describes the state evolution of the simulation object or the interaction process between two simulation objects in the LVC scenario.

[0042] An application refers to an executable program developed based on the TENA middleware standard that can load and run the corresponding object model. It can implement basic functions such as publishing / subscribing to state object models, querying / assigning state object models, calling method object models, and operating specific hardware. It can also configure elements such as logical time progression, method object model call order and conditions, publish / subscribe / relationships, and operating parameters of specific hardware based on scripting languages ​​such as Lua.

[0043] A physical host is a computer required for an application to run. It has TCP / IP protocol communication capabilities and the ability to run operating systems such as Windows / Linux. It can be bound to specific hardware interfaces or simulated devices as needed, or it can be installed on specific physical equipment as required.

[0044] The LVC simulation resources managed by this method include three categories: physical objects (L), simulators (V), and constructed simulation models (C). Physical objects (L) refer to simulation object units where the physical host, application program, and object model are completely bound and inseparable; in the LVC simulation scenario, they can only represent specific physical equipment objects. Simulators (V) refer to simulation object units where the application program and physical host are completely bound; the application program contains dedicated programs and interfaces for operating specific hardware resources, representing a certain type of equipment object in the LVC simulation scenario, and can represent multiple equipment objects of that type according to the principle of time-division multiplexing as needed. Constructed simulation models (C) refer to simulation object units where there is no complete binding relationship between the object model, application program, and physical host; any object model can be randomly combined with the application program and deployed to any physical host, representing all mathematical simulation objects in the LVC simulation scenario.

[0045] This method consists of the following three steps:

[0046] 1. Hierarchical resource registration: Various LVC simulation resources are registered and managed in a component-based manner according to three layers: object model, application, and physical host. Specifically, this includes three parts: First, mapping and registering the dynamic link libraries of the object model to their corresponding state object model instances and method object models according to the object model, application, and physical host layers; Second, mapping and registering the executable files of the application to their required configuration script template files and hardware interface plugin dynamic link libraries; Third, mapping and registering the names, network configuration information, and physical hardware of the physical host.

[0047] 2. Resource component configuration is divided into three steps: simulation object unit assembly, LVC resource unit configuration, and LVC resource unit packaging. According to the needs of the simulation object units in the simulation scenario, LVC experimental resource components at different levels are assembled into LVC resource unit deployment packages containing object models, applications, application script configuration files, hardware interface plugins, and host configuration files. These packages represent specific simulation object units in the simulation application scenario, forming a complete configuration scheme required for LVC experiments.

[0048] For assembling simulation object units, for physical equipment objects, it is necessary to bind the object model, application, and physical host. This involves establishing a mapping relationship between the state object model and the physical host's state data collected by the application, a mapping relationship between the interaction methods in the method object model and the hardware interface plugins in the application, and a mapping relationship between the application's hardware interface plugins and the hardware devices installed on the physical host. For simulator objects, it is necessary to bind the application and physical host, establish a mapping relationship between the application's hardware interface plugins and the hardware devices installed on the physical host, and establish a many-to-one mapping between a set of state object model instances and accessible parameters in the application. For constructing simulation objects, multiple physical hosts are specified, with at least one application deployed on each physical host as the runnable application for that constructed simulation object. During actual operation, the running position of the constructed simulation object is dynamically adjusted, taking into account network load and computing power balancing.

[0049] LVC resource unit configuration involves configuring the following: For the object model of the LVC resource unit, the initial values ​​of the state object model, whether to publish the state object model, and the list of state object models that the method object model needs to subscribe to; For the application of the LVC resource unit, the logical time progression mode, the method object model call order and conditions, publish-subscribe / relationships, the required hardware interface plugin dynamic libraries, and the corresponding specific hardware operating parameters in the application script configuration file; For the host of the LVC resource unit, its TCP / IP communication address and other information need to be configured.

[0050] LVC resource unit packaging refers to packaging the object model, application, application script configuration file, hardware interface plug-in, and host configuration file into a compressed file to form an LVC resource unit deployment package that maps to a specific simulation object unit.

[0051] 3. Resource service deployment: Following the LVC experiment configuration scheme, distribute the LVC resource unit deployment package to the designated physical host. Prepare for the activation of LVC simulation resources by launching the LVC experiment application, including the following steps:

[0052] The LVC resource unit deployment package is distributed to the designated physical host via file transfer protocols such as FTP and peer-to-peer sending and receiving.

[0053] On the specified physical host, extract the LVC resource unit deployment package to the specified runtime directory;

[0054] Remotely launch applications within an LVC resource unit using mechanisms such as SSH;

[0055] After the application starts, it initializes the state object model based on the application script configuration file and adds it to the LVC simulation test system.

[0056] Example:

[0057] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments:

[0058] The contents not described in detail in this specification are common knowledge to those skilled in the art.

[0059] like Figure 1 As shown, the LVC system comprises three categories: physical objects (L), simulators (V), and constructed simulation models (C). Physical objects (L) are simulation object units where the physical host, application program, and object model are completely bound and inseparable, representing specific physical equipment objects in the LVC simulation scenario. Simulators (V) are simulation object units where the application program and physical host are completely bound, representing a certain type of equipment object in the LVC simulation scenario; multiple such equipment objects can be represented as needed according to the principle of time-division multiplexing. Constructed simulation models (C) are simulation object units where there is no complete binding relationship between the object model, application program, and physical host; any object model can be randomly combined with the application program and deployed to any physical host, representing all mathematical simulation objects in the LVC simulation scenario.

[0060] according to Figure 2 The process involves hierarchical registration of resources within the system, managing various LVC simulation resources as components according to three levels: object model, application, and physical host.

[0061] The first step is to map and register the dynamic link libraries of all object models, such as C1 to Ci, V1 to Vj, and L, with their corresponding state object model instances and method object models. This means clarifying the mapping relationship between each method object model function, each state object model instance, and each object model dynamic link library.

[0062] The second step is to map and register the executable files of applications 1 to m with their required configuration script template files, map and register applications L and R with their accompanying simulator and hardware interface plugin dynamic link libraries, and map and register applications L and R with their required configuration script template files.

[0063] The third step is to map and register the names, network configuration information, and physical hardware of physical hosts 1 to m, V, and L.

[0064] Resource components are configured based on registration information.

[0065] The first step is to assemble the simulation object units:

[0066] Assemble the physical equipment object L, bind the object model L, application L, and physical host L, establish the mapping relationship between the state object model and the physical host through the physical equipment state data collected by the application, establish the mapping relationship between the interaction methods in the method object model and the hardware interface plug-in in the application, and establish the mapping between the hardware interface plug-in of the application and the hardware devices installed on the physical host.

[0067] Assembling the simulator object V requires binding the application V to the physical host V, establishing a mapping between the application's hardware interface plugins and the hardware devices installed on the physical host, and establishing a many-to-one mapping between a set of state object model instances V1 to Vj and the accessible parameters in the application.

[0068] Assemble all the simulated objects, using object models C1 to Ci to represent the simulated object units as units, specify physical hosts 1 to n, and applications 1 to m can be arbitrarily deployed to hosts 1 to n as runnable applications for the simulated object. In actual operation, the running position of the simulated object is dynamically adjusted by comprehensively considering network load and computing power balance.

[0069] The second step involves configuring LVC resource units based on the assembled simulation object units. This includes configuring the initial values ​​for all state object models, publishing all state object models by default, and specifying the list of state object models that each method object model needs to subscribe to. It also involves configuring the logical time progression mode, method object model call order and conditions, and publish / subscribe / relationships in all application script configuration files. For applications V and L, it's also necessary to configure the hardware interface plugin dynamic libraries to be loaded and the corresponding specific hardware runtime parameters. Finally, it involves configuring the IP addresses, ports, and hostnames of all hosts.

[0070] The LVC resource units are packaged into a single unit, using the simulation object unit as the unit. The comic object model, application, application script configuration file, hardware interface plugin, and host configuration file are packaged into a compressed file to form multiple LVC resource unit packages, such as the construction model objects C1 to Ci, the simulator object V, and the implementation object L.

[0071] Based on the obtained multiple LVC resource unit packages, resource service deployment is carried out, including the following steps:

[0072] First, using file transfer protocols such as FTP and peer-to-peer, and based on factors such as network load balancing and computing power allocation, the LVC resource unit packages of the model objects C1 to Ci are deployed to physical hosts 1 to n, the LVC resource unit package of the simulator object V is deployed to physical host V, and the LVC resource unit package of the implemented object L is deployed to physical host L.

[0073] Extract all LVC resource unit deployment packages to the specified physical host's runtime directory.

[0074] Remotely launch applications on all physical hosts via SSH.

[0075] After the application starts, it initializes the state object model based on the application script configuration file and adds it to the LVC simulation test system.

[0076] The object model consists of a state object model and a method object model developed based on the TENA middleware standard, and exists as a dynamic link library. The state object model describes the data model of the simulation object corresponding to the LVC simulation resource in the LVC simulation scenario, that is, it describes the values ​​of various parameters of the simulation object; the method object model describes the state evolution of the simulation object or the interaction process between two simulation objects in the LVC scenario.

[0077] An application refers to an executable program developed based on the TENA middleware standard that can load and run the corresponding object model. It can implement basic functions such as publishing / subscribing to state object models, querying / assigning state object models, calling method object models, and operating specific hardware. It can also configure elements such as logical time progression, method object model call order and conditions, publish / subscribe / relationships, and operating parameters of specific hardware based on scripting languages ​​such as Lua.

[0078] A physical host is a computer required for an application to run. It has TCP / IP protocol communication capabilities and the ability to run operating systems such as Windows / Linux. It can be bound to specific hardware interfaces or simulated devices as needed, or it can be installed on specific physical equipment as required.

[0079] The LVC simulation resources managed by this method divide the runtime slice of each prototype into two parts: an active time slice and a passive time slice. The active time slice is the period during which prototype A begins executing its current step control command, but prototype B connected to it has not yet begun executing its control command. The passive time slice is the period during which prototype B begins executing its current step control command, but prototype A has not yet begun executing its next step control command.

[0080] like Figure 2 As shown, the remote single-step strong real-time simulation system includes two physical prototypes, A and B, participating in the joint simulation. Each prototype consists of a physical entity and a simulation object. The two prototypes are connected to each other via a non-real-time simulation network.

[0081] The simulation object is the mapping of the prototype physical entity in the data space. The mapping content includes two parts: first, the state parameters necessary for prototype simulation, which can be parameters such as position, speed, and operating conditions; second, the interaction methods required to change the state parameters, which are functions that change the parameters.

[0082] Each prototype's simulation object is connected to the physical entity via a physical state measurement device, a data bus, and a physical feedback device. The physical state measurement device measures the prototype's physical state and converts it into state parameters for the simulation object; it can be a thermometer, goniometer, torque meter, or similar equipment. The data bus is an integral part of the prototype itself, used to transmit control commands, state parameters, and other data. The physical feedback device applies physical feedback to the prototype; it can be a force feedback device, a thermal environment simulation device, or similar.

[0083] The remote single-step strong real-time simulation method divides the operating state of the prototype physical entity and the prototype simulation entity into two parts: active time period operation and passive time period operation. The two jointly simulated prototypes alternate between active time period operation and passive time period operation. Multiple state frames of prototype physical parameters can be collected in each time period. When each prototype simulation object switches between active time period operation and passive time period operation states, physical state recovery parameters need to be calculated. When each prototype physical entity switches between active time period operation and passive time period operation states, physical state recovery needs to be performed.

[0084] Physical state recovery parameters refer to the control commands that a prototype physical entity needs to execute to restore its state parameters from a stopped state to the state before shutdown, which are issued to the prototype via the data bus. Physical state recovery steps refer to the process by which the prototype physical entity executes the physical state recovery parameters; after recovery is completed, the prototype's active or passive time period operation begins immediately.

[0085] The active operation steps of the prototype A physical entity are as follows: First, execute the instructions of the current control cycle; second, move according to its own control instructions; third, complete the active shutdown for the predetermined duration.

[0086] The active time period operation steps of prototype A simulation object are as follows: First, initialize the proxy model of the other prototype participating in the co-simulation, whose state value comes from the last frame data of the active time period state of the prototype received in the previous simulation step; Second, call the passive time period data proxy model of the other prototype participating in the co-simulation to calculate the interaction feedback, and feed back the interaction effect to the current prototype through the data bus and physical interaction feedback device; Third, record and forward the state parameter frames of the current prototype's active time period and feed them all back to the simulation object of the other prototype participating in the co-simulation.

[0087] The passive time period data proxy model is a proxy model built based on the historical data of the prototype's operating status. It uses historical data to describe the changing patterns between the interaction method and the state parameters.

[0088] While prototype A is running during the active period, prototype B is running during the passive period.

[0089] The passive operation steps of prototype B physical entity are as follows: First, passively respond to the continuous change process of the active period state data frame of another prototype participating in the joint simulation, and perform control command calculation for the current control cycle; Second, complete the passive period shutdown according to the predetermined duration.

[0090] The passive time period operation steps of prototype B are as follows: First, receive the active time period state parameter frame sequence of another prototype participating in the co-simulation; Second, play the active time period state parameter frame sequence of another prototype participating in the co-simulation.

[0091] After completing the above simulation steps, prototype A switched from active operation to passive operation; prototype B switched from passive operation to active operation.

[0092] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A resource management method for LVC simulation based on resource hierarchical grouping, characterized in that... include: Various LVC simulation resources are registered and managed hierarchically according to three levels: object model, application program, and physical host, resulting in LVC experimental resource components at different levels; According to the needs of the simulation object units in the simulation scenario, LVC test resource components at different levels are assembled into LVC resource unit deployment packages to form a configuration scheme for LVC tests; According to the configuration scheme of the LVC experiment, the LVC resource unit deployment package is distributed to the designated physical host. The LVC simulation resource is activated and managed by launching the LVC experiment application.

2. The LVC simulation resource management method based on resource hierarchy grouping according to claim 1, characterized in that: The object model, application, and physical host are specifically: The object model is a state object model and a method object model developed based on the standard of TENA middleware, and exists in the form of dynamic link libraries. The state object model is used to describe the data model of the simulation object corresponding to the LVC simulation resource in the LVC simulation scenario, that is, to describe the values ​​of various parameters of the simulation object. The method object model is used to describe the state evolution of the simulation object or the interaction process between two simulation objects in the LVC scenario. An application refers to an executable program developed based on the TENA middleware standard that can load and run the corresponding object model; it can implement state object model publishing / subscription, state object model query / assignment operations, method object model invocation, operation of specific hardware functions, and configure logical time progression, method object model invocation order and conditions, publish / subscribe / relationship, and specific hardware operation parameters based on the Lua scripting language; A physical host is a computer required for an application to run. It has TCP / IP protocol communication capabilities, the ability to run Windows / Linux operating systems, and can be bound to specific hardware interfaces or simulated devices as needed. It can also be installed on specific physical equipment as needed.

3. The LVC simulation resource management method based on resource hierarchy grouping according to claim 1, characterized in that: Various LVC simulation resources are registered and managed hierarchically according to three levels: object model, application program, and physical host. Specifically: Based on the hierarchy of object model, application, and physical host, the dynamic link library of the object model is mapped and registered with its corresponding state object model instance and method object model; Map and register the application's executable file with its required configuration script template files and hardware interface plugin dynamic link libraries; Map and register the physical host's name, network configuration information, and physical hardware.

4. The LVC simulation resource management method based on resource hierarchy grouping according to claim 1, characterized in that: The simulation objects include physical object units, simulator object units, and constructed simulation object units; A physical object unit refers to a simulation object unit that is completely bound to the physical host, application program, and object model. In the LVC simulation scenario, it can only represent a specific physical equipment object. A simulator object unit refers to a simulation object unit that is completely bound to the application and the physical host. The application contains dedicated programs and interfaces that operate on specific hardware resources. In the LVC simulation scenario, it represents a certain type of equipment object and can represent multiple equipment objects of the same type as needed according to the principle of time-division multiplexing. Constructing a simulation model object unit refers to a simulation object unit where there is no complete binding relationship between the object model, application, and physical host. Any object model is randomly combined with an application and deployed to any physical host, representing all mathematical simulation objects in the LVC simulation scenario.

5. The LVC simulation resource management method based on resource hierarchy grouping according to claim 1, characterized in that: Resource component configuration includes three steps: simulation object unit assembly, LVC resource unit configuration, and LVC resource unit packaging.

6. The LVC simulation resource management method based on resource hierarchy grouping according to claim 5, characterized in that: The assembly of the simulation object unit includes: For physical equipment objects, it is necessary to bind the object model, application, and physical host, establish a mapping relationship between the state object model and the physical host through the physical equipment state data collected by the application, establish a mapping relationship between the interaction methods in the method object model and the hardware interface plug-in in the application, and establish a mapping relationship between the hardware interface plug-in of the application and the hardware devices installed on the physical host. For simulator objects, it is necessary to bind the application to the physical host, establish a mapping between the application's hardware interface plugins and the hardware devices installed on the physical host, and establish a many-to-one mapping between a set of state object model instances and the accessible parameters in the application. For constructing simulation objects, multiple physical hosts are specified, with each physical host having at least one application deployed as the runnable application for the constructed simulation object. In actual operation, the running position of the constructed simulation object is dynamically adjusted by comprehensively considering network load and computing power balance.

7. The LVC simulation resource management method based on resource hierarchy grouping according to claim 5, characterized in that: LVC resource unit configuration involves configuring the initial values ​​of the state object model, whether to publish the state object model, and the list of state object models that the method object model needs to subscribe to in the object model's configuration file. For the application of the LVC resource unit, it is necessary to configure the logical time progression mode, the method object model call order and conditions, publish-subscribe / relationships, the required hardware interface plugin dynamic libraries, and the corresponding specific hardware runtime parameters in the application script configuration file. For the host of the LVC resource unit, it is necessary to configure its host's TCP / IP communication address information.

8. The LVC simulation resource management method based on resource hierarchy grouping according to claim 5, characterized in that: LVC resource unit packaging refers to packaging the object model, application, application script configuration file, hardware interface plug-in, and host configuration file into a compressed file to form an LVC resource unit deployment package that maps to a specific simulation object unit.

9. The LVC simulation resource management method based on resource hierarchy grouping according to claim 1, characterized in that: According to the LVC experiment configuration scheme, the LVC resource unit deployment package is distributed to the designated physical host. The LVC simulation resource activation preparation is completed by launching the LVC experiment application, including the following steps: The LVC resource unit deployment package is distributed to the designated physical host via the file transfer protocol; On the specified physical host, extract the LVC resource unit deployment package to the specified runtime directory; Remotely launch applications within an LVC resource unit via SSH; After the application starts, it initializes the state object model based on the application script configuration file and adds it to the LVC simulation test system.

Images