A collaborative simulation operation system

Abstract

This invention relates to a collaborative simulation operation system, belonging to the field of collaborative simulation technology, and solves the problem of high complexity in existing collaborative simulation operation methods. A collaborative simulation operation system includes: an experimental information processing subsystem, used to construct a task mode for the simulation task by parsing the simulation task; the task mode is used to record the configuration information and stored data information of the simulation nodes corresponding to each task behavior in the simulation task; an operation control subsystem, used to implement timeline management during the simulation operation, and also used to control the simulation nodes to execute corresponding simulation actions at specified action times, and record the node status of the simulation nodes during the simulation task operation; and a visualization display subsystem, used to provide a visual interface for the construction process of the task mode, and also used to visualize the changes in the node status of the simulation nodes during the simulation operation, and also used to provide simulation operation.

Description

Technical Field

[0001] This invention relates to the field of collaborative simulation technology, and in particular to a collaborative simulation operation system. Background Technology

[0002] In the process of collaborative simulation, it is necessary to decompose the simulation task, present it in a specific form, and record the execution status of the simulation task during the collaborative simulation process.

[0003] Therefore, the way simulation tasks are decomposed and the simulation process itself directly affect the simulation results. How to construct a collaborative simulation system that can simply, quickly, and effectively achieve collaborative simulation is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] Based on the above analysis, the embodiments of the present invention aim to provide a collaborative simulation operation system to solve the problem of high complexity in existing collaborative simulation operation methods.

[0005] This invention provides a collaborative simulation system, comprising:

[0006] The experimental information processing subsystem is used to construct the task mode of the simulation task by parsing the simulation task; the task mode is used to record the configuration information and stored data information of the simulation node corresponding to each task behavior in the simulation task.

[0007] The running control subsystem is used to manage the timeline during the simulation process, control the simulation nodes to perform corresponding simulation actions at specified action times, and record the node status of the simulation nodes during the simulation task.

[0008] The visualization display subsystem is used to provide a visual interface for the construction process of the task mode, to visualize the changes in the node state of the simulation node during the simulation operation, and to provide simulation operation.

[0009] Based on the above solution, the present invention also proposes the following improvements:

[0010] Furthermore, the simulation node includes one or more of the following: entity simulation node, target simulation node, and event simulation node;

[0011] The configuration information of the simulation node includes basic attribute information and execution action information; wherein, the basic attribute information includes node name and node type;

[0012] The storage data information of the simulation node includes the memory address and memory data structure corresponding to the simulation node.

[0013] Furthermore, the test information processing subsystem includes:

[0014] The simulation node information registration module is used to determine the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task according to the simulation task; it also configures the basic attribute information and stored data information of the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task.

[0015] The task mode generation module is used to visualize the relationships between simulation nodes according to the execution order of simulation tasks; the relationships include parallel relationships, serial relationships, and conditional judgment relationships.

[0016] The simulation task parsing module is used to determine the execution action information of the corresponding simulation node based on the functional settings of each simulation node in the simulation task and the association relationship between the simulation nodes, and to map the association relationship and execution action information to the configuration information of the corresponding simulation node in the simulation node information registration module.

[0017] Furthermore, the test information processing subsystem also includes a reflection memory management module;

[0018] The reflection memory management module is used to retrieve and configure memory allocation for the simulation nodes, and is also used to dynamically control the memory address settings of the interaction commands between the system and each simulation node and the data generated during the interaction commands during the simulation operation; it is also used to perform overlap verification on the memory allocation between simulation nodes.

[0019] Furthermore, the task mode generation module executes:

[0020] Create a task mode template and fill in the configuration information and stored data information of the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task;

[0021] The entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task, as well as the relationships between the simulation nodes, are graphically drawn to form the task mode of the simulation task.

[0022] Furthermore, in the task mode generation module, the drawn graphics include: node style graphics, event style graphics, condition style graphics, target style graphics, and connection style graphics;

[0023] Each entity simulation node is mapped one-to-one with a node style graphic;

[0024] Each event simulation node is mapped one-to-one with an event style graphic;

[0025] Each target simulation node is mapped one-to-one to a target pattern image;

[0026] Select the conditional graphic style based on the conditional relationships between simulation nodes;

[0027] Based on the execution order and relationships of the simulation nodes, the connection between node style graphics, event style graphics, condition style graphics, and target style graphics is achieved through connection style graphics.

[0028] Furthermore, the relationships between the simulation nodes include:

[0029] Parallelism: Simulation nodes with parallelism start running simultaneously when running simulation tasks;

[0030] Serial relationship: When simulation nodes with a serial relationship are running simulation tasks, the simulation node acting as the parent node starts running after the parent node finishes running.

[0031] Conditional relationships: By judging the conditional relationships, it is determined which simulation node to start and the branching path of the subsequent process is determined.

[0032] Furthermore, the operating control subsystem is also used for:

[0033] After configuring the simulation nodes based on task mode, execute:

[0034] Determine if the configuration of the simulation nodes is valid;

[0035] Determine whether the communication between the simulation node and the simulation device it is connected to is normal;

[0036] If the configuration is valid and communication is normal, the check passes and the simulation task will run.

[0037] Furthermore, the operating control subsystem executes:

[0038] During the simulation task execution, the corresponding simulation nodes are started according to the execution order of the simulation tasks;

[0039] The simulation node requests node memory from the reflective memory card based on the stored data information in order to obtain node memory;

[0040] The simulation node executes the corresponding simulation action based on the execution action information.

[0041] Furthermore, the operating control subsystem also performs:

[0042] After the simulation task starts running, the main thread starts and controls the start time of each simulation node, the running order of the simulation nodes, memory address passing, memory changes, simulation node status monitoring, simulation node error monitoring, information exchange between simulation nodes, and the termination time.

[0043] Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:

[0044] The collaborative simulation system provided by this invention can obtain corresponding task modes by decomposing simulation tasks. Each task mode records the configuration information and stored data of the simulation nodes corresponding to each task behavior. Therefore, after configuring each simulation node, a task queue can be constructed based on the simulation task. The task queue records the action time and simulation parameters of each simulation node. Then, the simulation task is run, and based on the simulation queue, the simulation nodes are controlled to execute corresponding simulation actions at specified action times, and the node status of the simulation nodes is recorded during the simulation task execution. Furthermore, this system provides a visual interface to visualize the construction of task modes before simulation execution, the visualization of simulation node status during simulation execution, and the visualization of backtracking data after simulation execution, facilitating a more intuitive understanding of the entire implementation process of the simulation task by those skilled in the art. This system can achieve collaborative simulation execution simply, quickly, and effectively, effectively solving the problem of high difficulty in existing collaborative simulation execution methods.

[0045] In this invention, the above-described technical solutions can be combined with each other to achieve more preferred combinations. Other features and advantages of this invention will be set forth in the following description, and some advantages may become apparent from the description or be learned by practicing the invention. The objects and other advantages of this invention can be realized and obtained from what is particularly pointed out in the description and drawings. Attached Figure Description

[0046] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts.

[0047] Figure 1 This is a schematic diagram of the structure of the collaborative simulation system provided in an embodiment of the present invention;

[0048] Figure 2 A flowchart of the collaborative simulation operation method provided in this embodiment of the invention;

[0049] Figure 3 This is a schematic diagram illustrating the relationship between simulation nodes provided in an embodiment of the present invention;

[0050] Figure 4A conceptual diagram of the task mode display module provided in an embodiment of the present invention;

[0051] Figure 5 This is an example of a task mode provided in an embodiment of the present invention;

[0052] Figures 6-8 These are schematic diagrams showing the basic information, memory data, and associated node configuration interface of the simulation node in this embodiment of the invention.

[0053] Figure 9 A diagram illustrating memory allocation using unallocated memory addresses;

[0054] Figure 10 A diagram illustrating memory allocation using previously allocated memory;

[0055] Figure 11 A flowchart illustrating the process of controlling simulation nodes to execute corresponding simulation actions based on configuration information and stored data.

[0056] Figure 12 A flowchart of another collaborative simulation operation method provided in an embodiment of the present invention.

[0057] Figure 13 Example diagram of co-simulation operation;

[0058] Figure 14 This is a schematic diagram of the processing logic during the co-simulation process. Detailed Implementation

[0059] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not intended to limit the scope of the present invention.

[0060] Example 1

[0061] Specific embodiment 1 of the present invention discloses a collaborative simulation operation system, the structural schematic diagram of which is shown below. Figure 1 As shown, it includes:

[0062] The experimental information processing subsystem is used to construct the task mode of the simulation task by parsing the simulation task; the task mode is used to record the configuration information and stored data information of the simulation node corresponding to each task behavior in the simulation task.

[0063] The running control subsystem is used to manage the timeline during the simulation process, control the simulation nodes to perform corresponding simulation actions at specified action times, and record the node status of the simulation nodes during the simulation task.

[0064] The visualization display subsystem is used to provide a visual interface for the construction process of the task mode, to visualize the changes in the node state of the simulation node during the simulation operation, and to provide simulation operation.

[0065] Specifically, in this embodiment, the simulation node includes one or more of the following: entity simulation node, target simulation node, and event simulation node; the configuration information of the simulation node includes basic attribute information and execution action information; wherein, the basic attribute information includes node name and node type; the storage data information of the simulation node includes the memory address and memory data structure corresponding to the simulation node.

[0066] Preferably, in this embodiment, the experimental information processing subsystem includes a simulation node information registration module, a task mode generation module, and a simulation task parsing module; wherein,

[0067] The simulation node information registration module is used to determine the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task according to the simulation task; it also configures the basic attribute information and stored data information of the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task.

[0068] The task mode generation module is used to visualize the relationships between simulation nodes according to the execution order of simulation tasks; the relationships include parallel relationships, serial relationships, and conditional judgment relationships.

[0069] The simulation task parsing module is used to determine the execution action information of the corresponding simulation node based on the functional settings of each simulation node in the simulation task and the association relationship between the simulation nodes, and to map the association relationship and execution action information to the configuration information of the corresponding simulation node in the simulation node information registration module.

[0070] In addition, the experimental information processing subsystem may also include a reflection memory management module, which is used to retrieve and configure memory allocation for the simulation nodes, dynamically control the interaction commands between the system and each simulation node during simulation operation, and set the memory address of the data generated during the interaction commands; it is also used to perform overlap verification on the memory allocation between simulation nodes.

[0071] In this embodiment, the task mode generation module generates a task mode by performing the following operations:

[0072] Create a task mode template and fill in the configuration information and stored data information of the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task;

[0073] The entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task, as well as the relationships between the simulation nodes, are graphically drawn to form the task mode of the simulation task.

[0074] In the specific implementation process, the graphics drawn in the task mode generation module include: node style graphics, event style graphics, condition style graphics, target style graphics, and connection style graphics;

[0075] Each entity simulation node is mapped one-to-one with a node style graphic;

[0076] Each event simulation node is mapped one-to-one with an event style graphic;

[0077] Each target simulation node is mapped one-to-one to a target pattern image;

[0078] Select the conditional graphic style based on the conditional relationships between simulation nodes;

[0079] Based on the execution order and relationships of the simulation nodes, the connection between node style graphics, event style graphics, condition style graphics, and target style graphics is achieved through connection style graphics.

[0080] In this embodiment, the operating control subsystem is further used for:

[0081] After configuring the simulation node based on task mode, the following steps are executed: determine whether the configuration of the simulation node is valid; determine whether the communication between the simulation node and its connected simulation device is normal; if the configuration is valid and the communication is normal, the check passes and the simulation task is ready to run.

[0082] Specifically, the operating control subsystem executes:

[0083] During the simulation task execution, the corresponding simulation nodes are started according to the execution order of the simulation tasks;

[0084] The simulation node requests node memory from the reflective memory card based on the stored data information in order to obtain node memory;

[0085] The simulation node executes the corresponding simulation action based on the execution action information.

[0086] In addition, the running control subsystem can also perform the following operations: after the simulation task starts running, the main thread starts and controls the start time of each simulation node, the running order of the simulation nodes, memory address passing, memory changes, simulation node status monitoring, simulation node error monitoring, information interaction between simulation nodes, and the timing of running termination.

[0087] Example 2

[0088] Specific embodiment 2 of the present invention discloses a collaborative simulation operation method, the flowchart of which is shown below. Figure 2 As shown, it includes the following steps:

[0089] Step S1: Obtain the task mode of the simulation task. The task mode is used to record the configuration information and stored data information of the simulation node corresponding to each task behavior in the simulation task.

[0090] Since simulation tasks generally involve interactions between entities (such as vehicles and ships), targets, and events, in this embodiment, simulation nodes include one or more of the following: entity simulation nodes, target simulation nodes, and event simulation nodes.

[0091] The configuration information of the simulation node describes the relevant attributes of the simulation node, including:

[0092] (1) Basic attribute information: General information of the nodes, including node name and node type; specifically, the node type of the entity simulation node is entity node, the node type of the target simulation node is target node, and the node type of the event simulation node is event node.

[0093] (2) Execution action information, including one or more of the following: calling the simulation program, calling the external script, issuing event commands, modifying memory, and binding data;

[0094] The storage data information of the simulation node includes the memory address and memory data structure corresponding to the simulation node.

[0095] In this embodiment, based on the memory data structure configured on the node, a corresponding storage space can be dynamically generated, recording the starting address and memory size of the storage space. The functions include:

[0096] 1) It can read memory data in real time and supports modifying memory through the interface;

[0097] 2) After the process is complete, export the memory data to a text file;

[0098] 3) Check if the length of the modified memory exceeds the specified boundary.

[0099] In this embodiment, before execution, the task mode can be converted into a visual interface, displaying the relationships between simulation nodes. Specifically, the diagram illustrating the relationships between simulation nodes is as follows: Figure 3 As shown, there are three types of relationships: parallel relationship, serial relationship, and conditional relationship. Specifically,

[0100] Parallelism: Simulation nodes with parallelism start running simultaneously when running simulation tasks;

[0101] Serial relationship: When simulation nodes with a serial relationship are running simulation tasks, the simulation node acting as the parent node starts running after the parent node finishes running.

[0102] Conditional relationships: By judging the conditional relationships, it is determined which simulation node to start and the branching path of the subsequent process is determined.

[0103] In step S1, the following operations are performed to obtain the task mode of the simulation task:

[0104] Step S11: Based on the simulation task, determine the entity simulation node, target simulation node, and / or event simulation node participating in the simulation task;

[0105] Step S12: Configure the basic attribute information and stored data information of the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task;

[0106] Step S13: Determine the relationships between simulation nodes according to the execution order of the simulation tasks; the relationships include parallel relationships, serial relationships, and conditional judgment relationships;

[0107] Step S14: Determine the execution action information of the corresponding simulation node based on the functional settings of each simulation node in the simulation task and the relationship between the simulation nodes.

[0108] In practice, the task mode can be graphically drawn using the task mode display module, as described below:

[0109] Step S15: Create a task mode template and fill in the configuration information and storage data information of the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task;

[0110] Step S16: Graphically draw the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task, as well as the relationships between the simulation nodes, to form the task mode of the simulation task.

[0111] The task mode display module is used to graphically display the overall structure of the task mode, including drawing nodes, showing the execution flow, and node running status. Users can create task modes using the system or import existing task modes created by the system.

[0112] In the task creation mode, users can drag and drop nodes from the "Node Menu" to the display area, and different styles will be displayed on the interface depending on the node type.

[0113] Import an existing task pattern. Following the interface wizard, import the task pattern file, obtain the task pattern's data structure through the "Task Pattern Parsing Module," and draw the graphical interface. The drawn graphics include:

[0114] Node style graphics

[0115] Event Style Graphics

[0116] Conditional style graphics

[0117] Target style graphics

[0118] Connect-line style graphics

[0119] Clicking on a node allows you to display and edit different interface information based on its style.

[0120] A node can be associated with a single simulator, or multiple child nodes can be placed in a node. Each child node then shuts down its corresponding simulator, forming a node simulation set. When a node runs, the child nodes run concurrently. For example, multiple simulation nodes can be placed in a node as child nodes. This placed node can be called a wave.

[0121] You can add, delete, adjust the position of nodes, and modify the relationships between nodes.

[0122] Figure 4 This is a conceptual diagram representing the task mode display module. Figure 5 This is an example of a task mode.

[0123] In practice, users can modify task modes through the interface, including adding, modifying, deleting, and changing the relationships between nodes; by clicking on a node, users can view the node's configuration information and stored data information, and modify the node information.

[0124] During operation, the system provides real-time feedback on the node's running status and memory data, and allows for manual modification of memory or issuance of commands.

[0125] After running, it collects data such as node status and instruction information during the operation process to form a log.

[0126] Users can add, modify, and configure nodes through the interface. The general interface display includes:

[0127] (1) Node memory starting address: Displayed after memory allocation, or can be set manually;

[0128] (2) Memory length: User-configured or automatically calculated;

[0129] (3) Node data display: The data interaction area between the system and the simulation equipment allows for data modification via the interface;

[0130] Figures 6-8 These are schematic diagrams showing the basic information of the simulation node, memory data, and the configuration interface of the associated node.

[0131] It should be noted that, in this embodiment, special processing is applied to the event simulation node:

[0132] (1) The event triggering mechanism can be used in conjunction with judgment condition nodes:

[0133] 1) Triggered by user click on the interface;

[0134] 2) Triggered when memory conditions are met;

[0135] (2) Event sending object and processing mechanism: Write the sending command to the agreed memory of all subsequent simulation nodes.

[0136] Special handling for conditional simulation nodes:

[0137] 1) Methods for editing conditions;

[0138] 2) When the conditions are met, what action should be performed?

[0139] Complex conditions can be addressed by calling an "external calling module," which includes:

[0140] And / Or: The relationship between conditions;

[0141] Field: The comparison object, which can specify the node and the node's variables, as well as the memory address and data type;

[0142] Operator: Compares the relationships between objects;

[0143] Value: The object being compared.

[0144] Step S2: Configure the simulation node based on the task mode;

[0145] During the specific testing process, according to the task mode, the configuration information and stored data information of each simulation node participating in the simulation task are sent to the corresponding simulation node. The corresponding simulation node completes its own configuration based on the received configuration information and stored data information.

[0146] Step S3: Construct a task queue based on the simulation task. The task queue records the action time and simulation parameters of each simulation node. Run the simulation task. Based on the simulation queue, control the simulation node to perform the corresponding simulation action at the specified action time, and record the node state of the simulation node during the execution of the simulation task.

[0147] After the simulation task starts running, the main thread starts and controls the start time of each simulation node, the running order of the simulation nodes, memory address passing, memory changes, simulation node status monitoring, simulation node error monitoring, information exchange between simulation nodes, and the termination time.

[0148] Step S31: During the simulation task execution, control the startup of the corresponding simulation nodes according to the execution order of the simulation tasks;

[0149] Step S32: The simulation node requests node memory from the reflective memory card based on the stored data information to obtain node memory;

[0150] It should be noted that a reflective memory card is installed on the system motherboard, forming a reflective memory network with the reflective memory card on the simulation device. Based on the memory length configured for the simulation nodes, the memory space on the memory card is statically or dynamically allocated, and the starting address of the allocated memory for each simulation node is recorded in the "Node Memory Address Dynamic Allocation List". Specifically, static allocation means that the user pre-enters the starting memory address for the node through the interface; dynamic allocation means that the system automatically allocates the starting memory address according to the simulation process.

[0151] The initialization and post-use processing of node memory can be controlled through the interface:

[0152] Before running a node, should the node's memory be cleared?

[0153] Can the memory be reused by other nodes?

[0154] Before the simulator finishes running, memory addresses cannot be allocated to other devices; after the simulator finishes running, if the memory can be reused, this memory space should be cleared so that subsequent simulation nodes can reuse this memory.

[0155] like Figure 9 As shown, in the absence of a simulation device finishing its run, the simulation node requests memory and uses unallocated memory addresses; for example... Figure 10 As shown, in cases where the simulation device finishes running, the simulation node requests memory and uses the allocated memory.

[0156] When a simulation node runs, its memory space is first initialized. The starting address of the node's memory is dynamically generated by the memory management module. The node's memory structure includes an instruction transfer area and a simulation memory area; among which,

[0157] (1) Command Transmission Area: The area where the system and simulation equipment interact with each other. It displays the system's default data structure. In the structure, each variable represents a certain meaning, such as: simulation start, simulation end, etc.

[0158] After the system modifies the variables, the simulation equipment can read the variable values ​​and control the equipment.

[0159] After the tested equipment modifies the variables, the system reads the variables and changes the node status.

[0160] (2) Simulation memory area: The memory used by the simulation device itself. The memory length is set in the node interface, or the user provides the data structure of the simulation node and the system automatically calculates the memory length.

[0161] The length of the simulation node memory is the sum of the lengths of the instruction transfer area and the simulation memory area.

[0162] Step S33: The simulation node executes the corresponding simulation action according to the execution action information.

[0163] The node states of the simulation nodes are divided into stateless and running.

[0164] A flowchart illustrating the process of controlling simulation nodes to execute corresponding simulation actions based on configuration and stored data is shown below. Figure 11 As shown.

[0165] In addition, the following judgment operation can be added between step S2 and step S3:

[0166] Determine if the configuration of the simulation nodes is valid;

[0167] Determine whether the communication between the simulation node and the simulation device it is connected to is normal;

[0168] If the configuration is valid and communication is normal, the check passes and the simulation task will run.

[0169] In this embodiment Figure 12 A flowchart of another co-simulation operation method is also provided to provide a more detailed understanding of the execution process of this embodiment.

[0170] like Figure 13 This is an example diagram of a collaborative simulation run. Figure 13 In the process, after the operation begins, "Node A" is run first. After "Node A" finishes running, "Node B" and "Node C" are run synchronously. After "Node C" finishes running, "Node D" is run.

[0171] Figure 14 This is a schematic diagram of the processing logic during the co-simulation process.

[0172] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware, and the program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0173] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

Claims

1. A collaborative simulation operation system, characterized in that, include: The experimental information processing subsystem is used to construct the task mode of the simulation task by analyzing the simulation task; The task mode is used to record the configuration information and stored data information of the simulation node corresponding to each task behavior in the simulation task; The running control subsystem is used to manage the timeline during the simulation process, control the simulation nodes to perform corresponding simulation actions at specified action times, and record the node status of the simulation nodes during the simulation task. The visualization display subsystem is used to provide a visualization interface for the construction process of the task mode, to visualize the node state changes of the simulation nodes during the simulation operation, and to provide simulation operation. The simulation node includes one or more of the following: entity simulation node, target simulation node, and event simulation node; The configuration information of the simulation node includes basic attribute information and execution action information; wherein, the basic attribute information includes node name and node type; The storage data information of the simulation node includes the memory address and memory data structure corresponding to the simulation node; The test information processing subsystem includes: The simulation node information registration module is used to determine the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task according to the simulation task; it also configures the basic attribute information and stored data information of the entity simulation nodes, target simulation nodes, and / or event simulation nodes participating in the simulation task. The task mode generation module is used to visualize the relationships between simulation nodes according to the execution order of simulation tasks; the relationships include parallel relationships, serial relationships, and conditional judgment relationships. The simulation task parsing module is used to determine the execution action information of the corresponding simulation node based on the functional settings of each simulation node in the simulation task and the association relationship between the simulation nodes, and to map the association relationship and execution action information to the configuration information of the corresponding simulation node in the simulation node information registration module.

2. The collaborative simulation operation system according to claim 1, characterized in that, The test information processing subsystem also includes a reflection memory management module; The reflection memory management module is used to retrieve and configure memory allocation for the simulation nodes, and is also used to dynamically control the memory address settings of the interaction commands between the system and each simulation node and the data generated during the interaction commands during the simulation operation; it is also used to perform overlap verification on the memory allocation between simulation nodes.

3. The collaborative simulation operation system according to claim 2, characterized in that, The task mode generation module executes: Create a task mode template and fill in the configuration information and stored data information of the entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task; The entity simulation nodes, target simulation nodes and / or event simulation nodes participating in the simulation task, as well as the relationships between the simulation nodes, are graphically drawn to form the task mode of the simulation task.

4. The collaborative simulation operation system according to claim 3, characterized in that, In the task mode generation module, the drawn graphics include: node style graphics, event style graphics, condition style graphics, target style graphics, and connection style graphics; Each entity simulation node is mapped one-to-one with a node style graphic; Each event simulation node is mapped one-to-one with an event style graphic; Each target simulation node is mapped one-to-one to a target pattern image; Select the conditional graphic style based on the conditional relationships between simulation nodes; Based on the execution order and relationships of the simulation nodes, the connection between node style graphics, event style graphics, condition style graphics, and target style graphics is achieved through connection style graphics.

5. The collaborative simulation operation system according to claim 4, characterized in that, The relationships between the simulation nodes include: Parallelism: Simulation nodes with parallelism start running simultaneously when running simulation tasks; Serial relationship: When simulation nodes with a serial relationship are running simulation tasks, the simulation node acting as the parent node starts running after the parent node finishes running. Conditional relationships: By judging the conditional relationships, it is determined which simulation node to start and the branching path of the subsequent process is determined.

6. The collaborative simulation operation system according to claim 5, characterized in that, The operating control subsystem is also used for: After configuring the simulation nodes based on task mode, execute: Determine if the configuration of the simulation nodes is valid; Determine whether the communication between the simulation node and the simulation device it is connected to is normal; If the configuration is valid and communication is normal, the check passes and the simulation task will run.

7. The collaborative simulation operation system according to claim 6, characterized in that, The operating control subsystem executes: During the simulation task execution, the corresponding simulation nodes are started according to the execution order of the simulation tasks; The simulation node requests node memory from the reflective memory card based on the stored data information in order to obtain node memory; The simulation node executes the corresponding simulation action based on the execution action information.

8. The collaborative simulation operation system according to claim 7, characterized in that, The operating control subsystem also performs: After the simulation task starts running, the main thread starts and controls the start time of each simulation node, the running order of the simulation nodes, memory address passing, memory changes, simulation node status monitoring, simulation node error monitoring, information exchange between simulation nodes, and the termination time.

Images