A breakpoint saving method and device of a combat simulation system

Abstract

The application discloses a kind of combat simulation system breakpoint saving method and device, the method includes: defining combat simulation system breakpoint saving parameter information and breakpoint recovery parameter information;Define the breakpoint saving interface and breakpoint recovery interface of combat simulation system;User sends breakpoint saving request to combat simulation system;Combat simulation system receives the breakpoint saving request, calls breakpoint saving interface, carries out breakpoint saving processing according to breakpoint saving parameter information, obtains breakpoint storage parameter information;User sends breakpoint recovery request to combat simulation system;Combat simulation system receives breakpoint recovery request, calls breakpoint recovery interface according to breakpoint recovery parameter information and processes breakpoint recovery request, recovers combat simulation system.This method saves the situation of a moment in the form of breakpoint in the simulation process, can be recovered from breakpoint in later period Run, shorten the time of starting from the beginning, improve the efficiency and system stability of activity such as drill, debugging.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of combat simulation, and in particular to a breakpoint saving method and device of a combat simulation system. BACKGROUND

[0002] In the process of combat simulation, a kind of simulation training activities is mostly real-time exercise, and if the simulation system is closed due to unexpected interruption such as power failure, the exercise needs to be restarted and started again, resulting in low exercise efficiency. In the process of debugging complex scenarios, the problem can only be reproduced at the critical moment, and it takes a long time to run to the critical moment and track at the critical breakpoint each time, resulting in low debugging efficiency. SUMMARY

[0003] The present application aims to provide a breakpoint saving method and device of a combat simulation system, which is applied to the simulation deduction link in the combat simulation system, supports saving the simulation data of important moments in the deduction process, so that the system can be recovered and run from the breakpoint when an unexpected event occurs (such as system power failure leading to simulation system shutdown or a specific problem needing to be debugged), without starting from the beginning, thereby improving the execution and debugging efficiency of the system.

[0004] To solve the above technical problems, the first aspect of the embodiment of the present application discloses a breakpoint saving method of a combat simulation system, which comprises:

[0005] S1, defining breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system;

[0006] S2, defining a breakpoint saving interface and a breakpoint recovery interface of the combat simulation system;

[0007] S3, the user sends a breakpoint saving request to the combat simulation system;

[0008] S4, the combat simulation system receives the breakpoint saving request, calls the breakpoint saving interface, performs breakpoint saving processing according to the breakpoint saving parameter information, and obtains breakpoint storage parameter information;

[0009] S5, the user sends a breakpoint recovery request to the combat simulation system;

[0010] S6, the combat simulation system receives the breakpoint recovery request, calls the breakpoint recovery interface, processes the breakpoint recovery request according to the breakpoint recovery parameter information, and recovers the combat simulation system.

[0011] As an optional implementation, in the first aspect of the embodiment of the present application, the definition of the breakpoint saving parameter information and the breakpoint recovery parameter information of the combat simulation system comprises:

[0012] S11, define breakpoint save parameter information of the combat simulation system, the breakpoint save parameter information including a message of breakpoint save and a flag bit indicating that the system is in a breakpoint save state;

[0013] S12, define breakpoint recovery parameter information of the combat simulation system, the breakpoint recovery parameter information including a message of breakpoint recovery and a flag bit indicating that the system is in a breakpoint recovery state.

[0014] As an optional implementation, in the first aspect of the embodiment of the application, the breakpoint save interface and the breakpoint recovery interface of the combat simulation system are used to determine whether the system is in a breakpoint save state or a breakpoint recovery state according to a system flag bit of the combat simulation system, if the system is in the breakpoint save state, perform the breakpoint save processing, and if the system is in the breakpoint recovery state, perform the breakpoint recovery processing.

[0015] As an optional implementation, in the first aspect of the embodiment of the application, the user sends a breakpoint save request to the combat simulation system, including:

[0016] The user sends a breakpoint save request to the combat simulation system according to the needs of the simulation system business implementation;

[0017] The sending of the breakpoint save request to the combat simulation system includes periodic sending or random triggering according to a breakpoint save time.

[0018] As an optional implementation, in the first aspect of the embodiment of the application, the combat simulation system receives the breakpoint save request, calls the breakpoint save interface, performs the breakpoint save processing according to the breakpoint save parameter information, and obtains breakpoint storage parameter information, including:

[0019] S41, the combat simulation system receives the breakpoint save request and completes execution of all events at a current simulation time;

[0020] S42, the combat simulation system performs persistent storage on a simulation object type, an attribute type contained in the simulation object, and an attribute value, and obtains first breakpoint storage parameter information;

[0021] S43, the combat simulation system performs persistent storage on an event function name submitted by the simulation object, an event execution time, an event parameter type, and an event parameter value, and obtains second breakpoint storage parameter information;

[0022] The first breakpoint storage parameter information and the second breakpoint storage parameter information constitute the breakpoint storage parameter information.

[0023] As an optional implementation, in the first aspect of the embodiment of the application, the combat simulation system receives the breakpoint recovery request, calls the breakpoint recovery interface, processes the breakpoint recovery request according to the breakpoint recovery parameter information, and recovers the combat simulation system, comprising:

[0024] S61, the combat simulation system receives the breakpoint recovery request, and acquires breakpoint storage parameter information;

[0025] S62, according to the breakpoint storage parameter information, the simulation element type, the contained attribute type and the attribute value saved at the breakpoint time are acquired;

[0026] S63, according to the breakpoint storage parameter information, the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event was submitted before the breakpoint time are acquired;

[0027] S64, the combat simulation system, according to the simulation element type, the contained attribute type, the attribute value saved at the breakpoint time, the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event was submitted before the breakpoint time, re-constructs the simulation object in the memory and initializes the member variable, so that the attribute value of each simulation element is restored to the state at the breakpoint; according to the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event was submitted before the breakpoint time, the event that has not started at the breakpoint but is planned to be executed in the future is constructed, the re-creation and submission of the event are performed, so that after the continuation of the deduction from the breakpoint, the previously planned event can be called and executed by the simulation engine as scheduled, thereby more comprehensively recovering the combat simulation system.

[0028] As an optional implementation, in the first aspect of the embodiment of the application, the method further comprises:

[0029] The combat simulation system saves all necessary data in the simulation process to the disk or the memory; the all necessary data includes the attribute data and the state data of all simulation elements, which are used to accurately restore to the previous state when recovered;

[0030] The combat simulation system records the event that needs to be executed at the current simulation time, which is used to continue the previous simulation process by re-submitting the event for execution when recovered;

[0031] The combat simulation system reads the saved data and event mark to recover after the simulation is stopped, and continues the simulation from the last saved state.

[0032] The second aspect of the embodiment of the application discloses a breakpoint saving device of a combat simulation system, the device comprising:

[0033] a parameter definition module, configured to define breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system;

[0034] an interface definition module, configured to define a breakpoint saving interface and a breakpoint recovery interface of the combat simulation system;

[0035] a breakpoint saving request sending module, configured to send a breakpoint saving request to the combat simulation system by a user;

[0036] a breakpoint saving request processing module, configured to receive the breakpoint saving request by the combat simulation system, call the breakpoint saving interface, and perform breakpoint saving processing according to the breakpoint saving parameter information to obtain breakpoint storage parameter information;

[0037] a breakpoint recovery request sending module, configured to send a breakpoint recovery request to the combat simulation system by a user;

[0038] a breakpoint recovery request processing module, configured to receive the breakpoint recovery request by the combat simulation system, call the breakpoint recovery interface, and perform processing on the breakpoint recovery request according to the breakpoint recovery parameter information to recover the combat simulation system.

[0039] As an optional implementation, in the second aspect of the embodiment of the present application, the definition of the breakpoint saving parameter information and the breakpoint recovery parameter information of the combat simulation system comprises:

[0040] S11, defining the breakpoint saving parameter information of the combat simulation system, wherein the breakpoint saving parameter information comprises a message of breakpoint saving and a flag bit indicating that the system is in a breakpoint saving state;

[0041] S12, defining the breakpoint recovery parameter information of the combat simulation system, wherein the breakpoint recovery parameter information comprises a message of breakpoint recovery and a flag bit indicating that the system is in a breakpoint recovery state.

[0042] As an optional implementation, in the second aspect of the embodiment of the present application, the breakpoint saving interface and the breakpoint recovery interface of the combat simulation system are configured to judge whether the system is in a breakpoint saving state or a breakpoint recovery state according to a system flag bit of the combat simulation system, perform breakpoint saving processing if the system is in the breakpoint saving state, and perform breakpoint recovery processing if the system is in the breakpoint recovery state.

[0043] As an optional implementation, in the first aspect of the embodiment of the present application, the sending of the breakpoint saving request to the combat simulation system by the user comprises:

[0044] sending the breakpoint saving request to the combat simulation system by the user according to a need of a service implemented by the simulation system;

[0045] The sending of the breakpoint saving request to the combat simulation system comprises periodic sending or random triggering according to a breakpoint saving opportunity.

[0046] As an optional implementation, in the second aspect of the embodiment of the present application, the combat simulation system receives the breakpoint saving request, calls the breakpoint saving interface, performs breakpoint saving processing according to the breakpoint saving parameter information, and obtains breakpoint storage parameter information, which comprises:

[0047] S41, the combat simulation system receives the breakpoint saving request and executes all events at the current simulation time;

[0048] S42, the combat simulation system performs persistent storage on the simulation object type, the attribute type contained in the simulation object and the attribute value, and obtains first breakpoint storage parameter information;

[0049] S43, the combat simulation system performs persistent storage on the event function name submitted by the simulation object, the event execution time, the parameter type and the parameter value of the event, and obtains second breakpoint storage parameter information;

[0050] The first breakpoint storage parameter information and the second breakpoint storage parameter information constitute the breakpoint storage parameter information.

[0051] As an optional implementation, in the second aspect of the embodiment of the present application, the combat simulation system receives the breakpoint saving request, calls the breakpoint saving interface, performs breakpoint saving processing according to the breakpoint saving parameter information, and obtains breakpoint storage parameter information, which comprises:

[0052] S61, the combat simulation system receives the breakpoint saving request and obtains breakpoint storage parameter information;

[0053] S62, according to the breakpoint storage parameter information, the simulation element type, the attribute type contained therein and the attribute value saved at the breakpoint time are obtained;

[0054] S63, according to the breakpoint storage parameter information, the function name of the unexecuted event, the event execution time, the parameter type of the event and the parameter value passed when the event was submitted before the breakpoint time are obtained;

[0055] S64, the combat simulation system, according to the simulation element type, the contained attribute type, the attribute value saved at the breakpoint time, the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event is submitted before the breakpoint time, re-constructs the simulation object in the memory and performs the initialization of the member variable, so that the attribute value of each simulation element is restored to the state at the breakpoint; according to the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event is submitted before the breakpoint time, constructs the event which is not started at the breakpoint but is planned to be executed in the future, performs the re-creation and submission of the event, so that after the deduction is continued from the breakpoint, the previously planned event can be called and executed by the simulation engine as scheduled, thereby more comprehensively restoring the combat simulation system.

[0056] As an optional implementation, in the second aspect of the embodiment of the present application, the method further comprises:

[0057] The combat simulation system saves all necessary data in the simulation process to the disk or the memory; the all necessary data comprises attribute data and state data of all simulation elements, so as to accurately restore to the previous state when the data is restored;

[0058] The combat simulation system records the event to be executed at the current simulation time, so as to continue the previous simulation process by re-submitting and executing the event when the data is restored;

[0059] The combat simulation system reads the saved data and event mark to continue the execution after the simulation is stopped.

[0060] The third aspect of the present application discloses another kind of combat simulation system's breakpoint saving device, the device comprises:

[0061] Memory storing executable program code;

[0062] Processor coupled with the memory;

[0063] The processor calls the executable program code stored in the memory, and executes part or all steps of the breakpoint saving method of the combat simulation system disclosed in the first aspect of the embodiment of the present application.

[0064] The fourth aspect of the present application discloses a computer storage medium, the computer storage medium stores computer instructions, the computer instructions are called to execute part or all steps of the breakpoint saving method of the combat simulation system disclosed in the first aspect of the embodiment of the present application.

[0065] Compared with the prior art, the embodiment of the present application has the following beneficial effects:

[0066] (1) Improve efficiency: During the simulation process, the state at a specific point in time may be very important to the simulation result, while the simulation process before this point in time does not need to be concerned too much. With the breakpoint save and restore function, only the state after the specific point in time can be saved, thereby improving simulation efficiency.

[0067] (2) Convenient debugging: When problems occur during the simulation, the breakpoint saving function can be used to pause the simulation and view the current status for debugging. Moreover, when resuming, you can return to the state before the problem occurred, which helps to quickly locate the problem.

[0068] (3) Improve system stability: Since the breakpoint save and restore function of the simulation system can save the simulation state periodically, even if the simulator crashes or loses power due to an unexpected situation, the simulation can be restarted through the restore mechanism and continue to execute from the last saved state.

[0069] (4) Optimize simulation results: Users can use the saved state to compare the differences between different simulation results, the changes in different stages of the experiment, etc., and select the best option according to the model parameter settings at different stages, providing material for the optimization of the target.

[0070] (5) Data backup and recovery: In combat simulation systems, data loss or corruption sometimes occurs. By using breakpoint save and restore, users can regularly back up simulation data to reduce the risk of data loss or corruption and restore data when needed. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 This is a flowchart illustrating a breakpoint saving method for a combat simulation system disclosed in an embodiment of the present invention.

[0073] Figure 2 This is a schematic diagram of a breakpoint saving device for a combat simulation system disclosed in an embodiment of the present invention;

[0074] Figure 3 This is a schematic diagram of a breakpoint saving device for another combat simulation system disclosed in an embodiment of the present invention. Detailed Implementation

[0075] In the following, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0076] The terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish different objects, rather than to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product, or equipment including a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed or can optionally include other steps or units inherent to the process, method, product, or equipment.

[0077] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears at various places in the specification does not necessarily all refer to the same embodiment, nor is it necessarily mutually exclusive of other embodiments. It is explicitly and implicitly understood that the embodiments described herein can be combined with other embodiments.

[0078] Embodiment one

[0079] Please refer to Figure 1 , Figure 1 is a flowchart of a breakpoint saving method of a combat simulation system according to an embodiment of the present application. Wherein, Figure 1 The described breakpoint saving method of the combat simulation system is applied to the technical field of combat simulation, such as the XSimStudio V5 series simulation platform software product of the extensible simulation platform, and the present application is not limited to the embodiments. As shown in Figure 1 The breakpoint saving method of the combat simulation system can include the following operations:

[0080] S1, defining breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system;

[0081] S2, defining a breakpoint saving interface and a breakpoint recovery interface of the combat simulation system;

[0082] S3, the user sends a breakpoint saving request to the combat simulation system;

[0083] S4, the combat simulation system receives the breakpoint saving request, calls the breakpoint saving interface, and performs breakpoint saving processing according to the breakpoint saving parameter information, to obtain breakpoint storage parameter information;

[0084] S5, the user sends a breakpoint recovery request to the combat simulation system;

[0085] S6, the combat simulation system receives the breakpoint recovery request, calls the breakpoint recovery interface, and performs processing on the breakpoint recovery request according to the breakpoint recovery parameter information, to recover the combat simulation system.

[0086] Optionally, the definition of the breakpoint saving parameter information and the breakpoint recovery parameter information of the combat simulation system comprises:

[0087] S11, the breakpoint saving parameter information of the combat simulation system is defined, and the breakpoint saving parameter information comprises a message of breakpoint saving and a flag bit indicating that the system is in a breakpoint saving state;

[0088] S12, the breakpoint recovery parameter information of the combat simulation system is defined, and the breakpoint recovery parameter information comprises a message of breakpoint recovery and a flag bit indicating that the system is in a breakpoint recovery state.

[0089] Optionally, the breakpoint saving interface and the breakpoint recovery interface of the combat simulation system are used to determine whether the current state is a breakpoint saving state or a breakpoint recovery state according to a system flag bit of the combat simulation system, perform breakpoint saving processing if the state is the breakpoint saving state, or perform breakpoint recovery processing if the state is the breakpoint recovery state.

[0090] Optionally, the user sending the breakpoint saving request to the combat simulation system comprises:

[0091] The user sends the breakpoint saving request to the combat simulation system according to the needs of business implementation of the simulation system;

[0092] The sending of the breakpoint saving request to the combat simulation system comprises periodic sending or random triggering according to a breakpoint saving time.

[0093] Optionally, the combat simulation system receiving the breakpoint saving request, calling the breakpoint saving interface, and performing breakpoint saving processing according to the breakpoint saving parameter information to obtain breakpoint storage parameter information comprises:

[0094] S41, the combat simulation system receives the breakpoint saving request, and completes execution of all events at a current simulation time;

[0095] S42, the combat simulation system performs persistent storage on a simulation object type, an attribute type contained in the simulation object, and an attribute value, to obtain first breakpoint storage parameter information;

[0096] S43, the combat simulation system persistently stores the event function name submitted by the simulation object, the time of event execution, the parameter type of the event, and the parameter value, to obtain second breakpoint storage parameter information;

[0097] The first breakpoint storage parameter information and the second breakpoint storage parameter information constitute breakpoint storage parameter information.

[0098] Optionally, the combat simulation system receives the breakpoint recovery request, calls the breakpoint recovery interface, processes the breakpoint recovery request according to the breakpoint recovery parameter information, and recovers the combat simulation system, including:

[0099] S61, the combat simulation system receives the breakpoint recovery request, and acquires the breakpoint storage parameter information;

[0100] S62, according to the breakpoint storage parameter information, the simulation element type, the contained attribute type, and the attribute value saved at the breakpoint time are acquired;

[0101] S63, according to the breakpoint storage parameter information, the function name of the unexecuted event, the time of event execution, the parameter type of the event, and the parameter value passed when the event was submitted before the breakpoint time are acquired;

[0102] S64, the combat simulation system, according to the simulation element type, the contained attribute type, the attribute value saved at the breakpoint time, the function name of the unexecuted event, the time of event execution, the parameter type of the event, and the parameter value passed when the event was submitted before the breakpoint time, re-constructs the simulation object in the memory and initializes the member variable, so that the attribute value of each simulation element is restored to the state at the breakpoint time. Then, according to the function name of the unexecuted event, the time of event execution, the parameter type of the event, and the parameter value passed when the event was submitted before the breakpoint time, the event that has not started at the breakpoint time but is planned to be executed in the future is constructed, the re-creation and submission of the event are performed, so that after the deduction from the breakpoint is continued, the events planned before can be called and executed by the simulation engine as scheduled, thereby more comprehensively recovering the combat simulation system.

[0103] Optionally, the method further includes:

[0104] The combat simulation system saves all necessary data in the simulation process to the disk or the memory; the all necessary data includes attribute data and state data of all simulation elements, which are used to accurately restore to the previous state when recovered;

[0105] The combat simulation system records the event that needs to be executed at the current simulation time, which is used to continue the previous simulation process by re-submitting the event for execution when recovered;

[0106] The combat simulation system reads the saved data and event markers to resume and continue the simulation from the last saved state after the simulation is stopped.

[0107] Embodiment two

[0108] The abbreviations and key terms of the embodiments of the present application are defined as follows:

[0109] Simulation scenario: In the military field, a scenario is a hypothesis and assumption of a combat area and environment, deployment of forces of both sides, and planning of a combat task, which is prepared by military researchers according to certain military purposes. The simulation scenario is a description of the virtual initial battlefield combat environment, which includes not only natural environment such as terrain and weather, but also man-made environment such as deployment and formation of forces of both sides, weapons and equipment, combat scheme, and tasks.

[0110] Simulation event: A discrete event simulation system (DES) is a computer simulation technology for simulating discrete events. In such a simulation system, an event refers to a discrete, sudden, and time-sequential behavior or activity occurring in the simulation process. The simulation deduction process is a process of continuous generation and execution of events.

[0111] Event queue: A container for storing events, all events generated in the simulation system are maintained in the event queue, and operations such as insertion, sorting, and deletion of events are performed through the event queue.

[0112] Object serialization technology: A technology for converting object data into another persistent data form, that is, a process of converting the state information of an object into a form that can be stored or transmitted. During serialization, an object writes its current state to a temporary or persistent storage area.

[0113] Object deserialization technology: In the serialization process, in order to make the data stored and transmitted into an object in the memory again, the conversion of object data into persistent data must be reversible. The object state can be read from the storage area or deserialized to recreate the object.

[0114] In a combat simulation system, the design of breakpoint saving and recovery is very necessary, and the present application proposes a breakpoint saving method for a combat simulation system, which is mainly considered from the following aspects:

[0115] Time and resource saving: Combat simulation systems can be very complex and require a lot of computation and resources to run. If the system fails or needs to be stopped during running, it needs to restart the entire simulation process. However, with breakpoint saving and restoring, users can stop and save the current state in the middle of the system, so that they can start the simulation process again later, restore the state at the time when the process stopped and continue to execute.

[0116] Enhanced interactivity: In combat simulation systems, decisions and adjustments are often needed, which may require repeated testing and experimentation. With breakpoint saving and restoring, users can more easily conduct multiple tests and attempts, and return to the previously saved state to start over when needed.

[0117] Optimized simulation results: Breakpoint saving and restoring not only save time and resources, but also help users better analyze simulation results. Users can use saved state data to compare differences between different simulation results, changes in different stages of experiments, etc.

[0118] Backup and restore data: In combat simulation systems, data loss or damage sometimes occurs. With breakpoint saving and restoring, users can regularly backup simulation data and restore data when needed to reduce the impact of data loss or damage and reduce risk.

[0119] By saving the state of simulation objects at a specific time during the simulation process and saving events that have been submitted but have not reached the execution time before that time, we can ensure that the simulation object can be restored according to the saved simulation object state data, and the event queue can be restored according to the saved event information, so that all subsequent simulation events can be executed through the simulation engine from the specific time. Thus, the entire simulation system at a specific time is restored.

[0120] To implement the breakpoint saving and restoring function of the simulation system, the following aspects need to be considered:

[0121] Data storage: Save all necessary data during the simulation process to disk or memory, including the attributes and states of all simulation elements, so that the previous state can be accurately restored when restoring.

[0122] Event marking: Record which events need to be executed at the current simulation time, so that the previous simulation process can be continued and the events can be re-submitted for execution when restoring.

[0123] Restoration mechanism: After the simulation stops, read the saved data and marked events to restore and continue the simulation from the last saved state.

[0124] The specific implementation steps are as follows:

[0125] 1. Define the message of breakpoint save and breakpoint recovery, the flag bit of identifying the system in the state of breakpoint save / recovery, facilitate the simulation system to quickly identify the behavior of breakpoint save and breakpoint recovery when the user initiates the request, modify the system state flag bit for other modules of the system to obtain and identify.

[0126] 2. Define the interface of breakpoint save and recovery, the simulation engine calls the interface of breakpoint save and recovery of all models when the simulation is started or interrupted, each model judges whether it is in the state of breakpoint save or breakpoint recovery by identifying the system flag bit modified in the first step in the interface implementation, if it is in the state of breakpoint save, the breakpoint save processing is performed, if it is in the state of breakpoint recovery, the breakpoint recovery processing is performed. The interface is allowed to be overwritten, facilitating secondary development, and the model developer can save and restore the custom variables and functions at the time of breakpoint save and recovery.

[0127] 3. Send the breakpoint save request. The user sends the breakpoint save request according to the needs of the business implementation of the simulation system. The request can be sent periodically, or triggered randomly by the user when the user judges the time of breakpoint save.

[0128] 4. Process the breakpoint save request.

[0129] After receiving the breakpoint save request, the simulation system completes the execution of all events at the current simulation time, and after all simulation objects complete the state data update at the current time, the interface of breakpoint save and recovery of all models is called to perform the breakpoint save processing, which includes two aspects:

[0130] 1) Serialization of all attribute data, persistently stores the simulation object type, the attribute type contained in the simulation object and the attribute value;

[0131] 2) Serialization of all event information, persistently stores the event function name submitted by the simulation object, the time of event execution, the parameter type of the event and the parameter value at the time of event submission.

[0132] 5. Process the breakpoint recovery request.

[0133] After receiving the breakpoint recovery request, the simulation system calls the interface of breakpoint save and recovery of all models to obtain the necessary information for recovery from the persistent data saved in the fourth step, which includes two aspects of information:

[0134] 1) Simulation element type, contained attribute type and attribute value saved at the breakpoint time;

[0135] 2) Unexecuted events, including event function name, time of event execution, parameter type of the event and parameter value passed when the event was submitted before the breakpoint time.

[0136] According to the simulation element type, the contained attribute type, the attribute value saved at the breakpoint time, the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event is submitted before the breakpoint time, the simulation object is reconstructed in the memory and the member variable is initialized, so that the attribute value of each simulation element is restored to the state at the breakpoint. Then, according to the function name of the unexecuted event, the time of event execution, the parameter type of the event and the parameter value passed when the event is submitted before the breakpoint time, the event which is not started at the breakpoint but planned to be executed in the future is constructed, the re-creation and submission of the event are performed, so that after the deduction is continued from the breakpoint, the previously planned event can be called and executed by the simulation engine as scheduled, so that the simulation system is restored to the initial state.

[0137] Embodiment three

[0138] Please refer to Figure 2 , Figure 2 is a flowchart of a breakpoint saving device of a combat simulation system according to an embodiment of the present application. Wherein, Figure 2 The breakpoint saving device of the combat simulation system described in the present application is applied to the technical field of combat simulation, and is not limited to the XSimStudio V5 series simulation platform software product of the expandable simulation platform XSimStudio. As shown in Figure 2 The breakpoint saving device of the combat simulation system can include the following operations:

[0139] S301, a parameter definition module, configured to define breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system;

[0140] S302, an interface definition module, configured to define a breakpoint saving interface and a breakpoint recovery interface of the combat simulation system;

[0141] S303, a breakpoint saving request sending module, configured to send a breakpoint saving request to the combat simulation system by a user;

[0142] S304, a breakpoint saving request processing module, configured to receive the breakpoint saving request by the combat simulation system, call the breakpoint saving interface, perform breakpoint saving processing according to the breakpoint saving parameter information, and obtain breakpoint storage parameter information;

[0143] S305, a breakpoint recovery request sending module, configured to send a breakpoint recovery request to the combat simulation system by a user;

[0144] S306, a breakpoint recovery request processing module, configured to receive the breakpoint recovery request by the combat simulation system, call the breakpoint recovery interface, perform processing on the breakpoint recovery request according to the breakpoint recovery parameter information, and recover the combat simulation system.

[0145] Embodiment four

[0146] Please refer to Figure 3 , Figure 3 is another flow diagram of the breakpoint saving device of the combat simulation system according to an embodiment of the present application. Wherein, Figure 3 The breakpoint saving device of the combat simulation system described in the present application is applied to the field of combat simulation technology, such as the XSimStudio V5 series simulation platform software product of the expandable simulation platform, and the present application is not limited to this. As shown in Figure 3 The breakpoint saving device of the combat simulation system can include the following operations:

[0147] The memory 401 stores executable program codes;

[0148] The processor 402 is coupled to the memory 401;

[0149] The processor 402 calls the executable program codes stored in the memory 401 to execute the breakpoint saving method of the combat simulation system as described in Embodiment One and Embodiment Two.

[0150] Embodiment Five

[0151] The present application discloses a computer storage medium which stores computer instructions for electronic data exchange, wherein the computer instructions are called to execute the breakpoint saving method of the combat simulation system as described in Embodiment One and Embodiment Two.

[0152] The device embodiments described above are only schematic, wherein the modules illustrated as separate components can or can not be physically separated, and the components illustrated as modules can or can not be physical modules, i.e. they can be located in one place or distributed on multiple network modules. Part or all of the modules can be selected to achieve the purpose of the present embodiment according to actual needs. Those skilled in the art can understand and implement it without creative labor.

[0153] Those skilled in the art can clearly understand the implementation of the various embodiments by means of software and necessary general hardware platforms through the above specific description of the embodiments, and of course, the embodiments can also be implemented by hardware. Based on such understanding, the above technical solutions, essentially or in other words, the part of the prior art that contributes to the present application can be embodied in the form of a software product. The computer software product can be stored in a computer readable storage medium, including a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage, a magnetic tape storage, or any other computer readable medium that can be used to carry or store data.

[0154] Finally, it should be noted that: the disclosed breakpoint saving method and device of the combat simulation system disclosed by the embodiments of the present application are only the preferred embodiments of the present application, and are used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: the technical solutions recorded in the foregoing embodiments can still be modified, or some technical features can be replaced by equivalents; and these modifications or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for saving breakpoints in a combat simulation system, characterized in that, The method includes: S1 defines the breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system, including: S11, Define the breakpoint saving parameter information of the combat simulation system. The breakpoint saving parameter information includes the breakpoint saving message and a flag indicating that the system is in the breakpoint saving state. S12, Define the breakpoint recovery parameter information of the combat simulation system. The breakpoint recovery parameter information includes a breakpoint recovery message and a flag indicating that the system is in a breakpoint recovery state. S2 defines the breakpoint saving interface and breakpoint recovery interface of the combat simulation system; In the interface implementation, each model determines whether it is in a breakpoint save state or a breakpoint restore state by identifying the modified system flag in S1. If it is in a breakpoint save state, breakpoint save processing is performed; if it is in a breakpoint restore state, breakpoint restore processing is performed. The interface can be overridden to facilitate secondary development. Model developers can save and restore custom variables and functions when saving and restoring breakpoints. S3, the user sends a breakpoint save request to the combat simulation system, including: Users send breakpoint save requests to the combat simulation system according to the needs of the simulation system's business implementation; Sending a breakpoint save request to the combat simulation system may be done periodically or randomly based on the breakpoint save timing. S4, the combat simulation system receives the breakpoint save request, calls the breakpoint save interface, performs breakpoint save processing according to the breakpoint save parameter information, and obtains the breakpoint storage parameter information, including: S41, the combat simulation system receives the breakpoint save request and completes the execution of all events at the current simulation moment; S42, the combat simulation system persistently stores the simulation object type, the attribute types and attribute values ​​contained in the simulation object, and obtains the first breakpoint storage parameter information; S43, the combat simulation system persistently stores the event function name, event execution time, event parameter type and parameter value submitted by the simulation object, and obtains the second breakpoint storage parameter information; The first breakpoint storage parameter information and the second breakpoint storage parameter information constitute the breakpoint storage parameter information; S5, the user sends a breakpoint recovery request to the combat simulation system; S6, the combat simulation system receives the breakpoint recovery request, calls the breakpoint recovery interface, processes the breakpoint recovery request according to the breakpoint recovery parameter information, and recovers the combat simulation system, including: S61, the combat simulation system receives the breakpoint recovery request and obtains the breakpoint storage parameter information; S62, based on the breakpoint storage parameter information, obtain the simulation element type, the attribute types it contains, and the attribute values ​​saved at the breakpoint time; S63, based on the breakpoint storage parameter information, obtain the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter value passed when submitting the event before the breakpoint time; S64, the combat simulation system, based on the simulation element type, the included attribute type, the attribute values ​​saved at the breakpoint, the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter values ​​passed when submitting the event before the breakpoint, reconstructs the simulation object in memory and initializes its member variables, restoring the attribute values ​​of each simulation element to the state at the breakpoint; based on the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter values ​​passed when submitting the event before the breakpoint, it constructs events that did not start at the breakpoint but are planned to be executed in the future, and recreates and submits these events, so that after continuing the simulation from the breakpoint, the previously planned events can be called and executed by the simulation engine as scheduled, thereby more comprehensively restoring the combat simulation system.

2. The breakpoint saving method of the combat simulation system according to claim 1, characterized in that, The method further includes: The combat simulation system saves all necessary data during the simulation process to a disk or memory; all necessary data includes attribute data and status data of all simulation elements, so that the system can accurately restore the system to its previous state during recovery. The combat simulation system records the events that need to be executed at the current simulation moment, so that the previous simulation process can continue when the simulation is resumed and the events are resubmitted for execution. The combat simulation system, after the simulation stops, reads the saved data and event markers to restore the simulation and allows the simulation to continue from the last saved state.

3. A breakpoint saving device for a combat simulation system, characterized in that, The device includes: The parameter definition module is used to define the breakpoint saving parameter information and breakpoint recovery parameter information of the combat simulation system, including: S11, Define the breakpoint saving parameter information of the combat simulation system. The breakpoint saving parameter information includes the breakpoint saving message and a flag indicating that the system is in the breakpoint saving state. S12, Define the breakpoint recovery parameter information of the combat simulation system. The breakpoint recovery parameter information includes a breakpoint recovery message and a flag indicating that the system is in a breakpoint recovery state. The interface definition module is used to define the breakpoint saving interface and breakpoint recovery interface of the combat simulation system. In the interface implementation, each model determines whether it is in a breakpoint save state or a breakpoint restore state by identifying the modified system flag in S1. If it is in a breakpoint save state, breakpoint save processing is performed; if it is in a breakpoint restore state, breakpoint restore processing is performed. The interface can be overridden to facilitate secondary development. Model developers can save and restore custom variables and functions when saving and restoring breakpoints. The breakpoint save request sending module is used by users to send breakpoint save requests to the combat simulation system, including: Users send breakpoint save requests to the combat simulation system according to the needs of the simulation system's business implementation; Sending a breakpoint save request to the combat simulation system may be done periodically or randomly based on the breakpoint save timing. A breakpoint save request processing module is used by the combat simulation system to receive the breakpoint save request, call the breakpoint save interface, perform breakpoint save processing according to the breakpoint save parameter information, and obtain the breakpoint storage parameter information, including: S41, the combat simulation system receives the breakpoint save request and completes the execution of all events at the current simulation moment; S42, the combat simulation system persistently stores the simulation object type, the attribute types and attribute values ​​contained in the simulation object, and obtains the first breakpoint storage parameter information; S43, the combat simulation system persistently stores the event function name, event execution time, event parameter type and parameter value submitted by the simulation object, and obtains the second breakpoint storage parameter information; The first breakpoint storage parameter information and the second breakpoint storage parameter information constitute the breakpoint storage parameter information; The breakpoint recovery request sending module is used by users to send breakpoint recovery requests to the combat simulation system. A breakpoint recovery request processing module is used by the combat simulation system to receive the breakpoint recovery request, call the breakpoint recovery interface, process the breakpoint recovery request according to the breakpoint recovery parameter information, and restore the combat simulation system, including: S61, the combat simulation system receives the breakpoint recovery request and obtains the breakpoint storage parameter information; S62, based on the breakpoint storage parameter information, obtain the simulation element type, the attribute types it contains, and the attribute values ​​saved at the breakpoint time; S63, based on the breakpoint storage parameter information, obtain the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter value passed when submitting the event before the breakpoint time; S64, the combat simulation system, based on the simulation element type, the included attribute type, the attribute values ​​saved at the breakpoint, the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter values ​​passed when submitting the event before the breakpoint, reconstructs the simulation object in memory and initializes its member variables, restoring the attribute values ​​of each simulation element to the state at the breakpoint; based on the function name of the unexecuted event, the event execution time, the event parameter type, and the parameter values ​​passed when submitting the event before the breakpoint, it constructs events that did not start at the breakpoint but are planned to be executed in the future, and recreates and submits these events, so that after continuing the simulation from the breakpoint, the previously planned events can be called and executed by the simulation engine as scheduled, thereby more comprehensively restoring the combat simulation system.

4. A breakpoint saving device for a combat simulation system, characterized in that, The device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the breakpoint saving method of the combat simulation system as described in any one of claims 1-2.

5. A computer-storable medium, characterized in that, The computer storage medium stores computer instructions, which, when invoked, are used for the breakpoint saving method of the combat simulation system as described in any one of claims 1-2.

Images