Satellite simulation running process control system and method

Abstract

The invention provides a satellite simulation running process control system and method. The system comprises a simulation running process control instruction protocol, a simulation running state feedback instruction protocol and a simulation running scene control instruction protocol. The simulation running process control instruction is used for room control, the simulation running state feedback instruction is used for simulation state confirmation, and the simulation running scene control instruction is used for space target control. According to the method and the system, a universal control instruction can be generated for objects such as scenes and entities running in the simulation system, an instruction control result is fed back according to an instruction execution state, and various forms of simulation system guide and control requirements can be met.

Description

Technical Field

[0001] The present invention relates to the technical field of satellite simulation systems, and in particular to a satellite simulation operation process control system and method. Background Art

[0002] Satellite simulation is a modern emerging discipline that conducts in-depth research on satellite systems by building satellite models. Simulation technology is not only economical and safe, but also can better solve the problems of the inability to repeat the scenes in the satellite system and the limitation of training time or space by actual environmental factors.

[0003] However, there are still some problems to be solved in the guidance and control layer of the satellite simulation system. Due to the different focuses during system construction, the guidance and control command forms and structures of various satellite simulation systems are diverse, and the control methods for simulation scenes and simulation entities are also different, resulting in poor compatibility between systems and low module reuse rates, which wastes a lot of construction costs. Therefore, a more universal guidance and control command protocol is needed to make it the construction standard of the guidance and control layer of the satellite simulation system, so as to avoid researchers from all over the world designing a large number of repeated and overly customized guidance and control command protocols. Summary of the invention

[0004] In view of the defects in the prior art, the object of the present invention is to provide a satellite simulation operation process control system and method.

[0005] The satellite simulation operation process control system provided by the present invention comprises: a simulation operation process control module, a simulation operation state feedback module and a simulation operation scene control module;

[0006] The simulation operation process control module is implemented by simulation operation process control instructions, and the simulation operation process control instructions are composed of a JSON string, including instruction ID, instruction type, operation mode, scenario ID, scenario start time, scenario end time, jump time, scenario instance name, simulation instance ID, room ID, room mode, room status, current room time and operation magnification;

[0007] The simulation operation status feedback module is implemented by a simulation operation status feedback instruction, and the simulation operation status feedback instruction consists of a JSON string, including a simulation ID, a simulation time, a simulation status, and a simulation magnification;

[0008] The simulation operation scenario control module is implemented through the simulation operation scenario control instruction, and the simulation operation scenario control instruction consists of an instruction header JSON string and an instruction body JSON string; the instruction header includes an instruction ID, an instruction type, an instruction execution type, a creator ID, a creator name, a creation time, a hypothetical start time, an instruction execution time, an instruction response path, and remarks; the instruction body includes an entity number, a component number, a Chinese name, an English name, a model, a fault type, orbit information, missile trajectory information, track information, and position information.

[0009] Preferably, the instruction fields of the simulation running process control instructions, simulation running status feedback instructions and simulation running scenario control instructions include the following naming rules: length is not more than 64 characters; consists of letters or numbers; uses camel case naming; and is not a keyword defined by C / C++ or the simulation system.

[0010] Preferably, the time jumping and speed changing behaviors are controlled by the envSkipTime and roomRate fields in the simulation running process control instructions; when the time jumping and speed changing requirements arise, they are set in the guidance and control software, and the guidance and control software generates the simulation running process control instructions in JSON format and sends them to the simulation engine; after the simulation engine receives and parses them, it executes the corresponding time jumping and speed changing behaviors, and feeds back the execution status to the guidance and control software.

[0011] Preferably, the simulation status is provided by the simulation engine and sent to the guide control software. Every preset time period, the simulation engine records the status of the simulation scene, generates a simulation operation status feedback instruction in JSON format, and sends it to the guide control software; after receiving and parsing, the guide control software displays the real-time status of the simulation scene.

[0012] Preferably, the simulation running scene control instructions are divided into an instruction header and an instruction body to control the intervention behavior of the simulation scene; after setting the instructions for adding and deleting entities and changing posture and trajectory, the guidance and control software assembles the instruction header and the instruction body to generate the simulation running scene control instructions in JSON format, and sends it to the simulation engine; after receiving and parsing, the simulation engine executes the corresponding intervention behavior and feeds back the execution status to the guidance and control software.

[0013] The satellite simulation operation process control method provided by the present invention includes:

[0014] The simulation operation process control step is implemented by the simulation operation process control instruction, which consists of a JSON string, including instruction ID, instruction type, operation mode, scenario ID, scenario start time, scenario end time, jump time, scenario instance name, simulation instance ID, room ID, room mode, room status, current room time and operation magnification;

[0015] The simulation running status feedback step is implemented by a simulation running status feedback instruction, wherein the simulation running status feedback instruction is composed of a JSON string, including a simulation ID, a simulation time, a simulation status, and a simulation magnification;

[0016] Simulation operation scenario control step: It is implemented through simulation operation scenario control instructions, and the simulation operation scenario control instructions are composed of an instruction header JSON string and an instruction body JSON string; the instruction header includes instruction ID, instruction type, instruction execution type, creator ID, creator name, creation time, assumed start time, instruction execution time, instruction response path and remarks; the instruction body includes entity number, component number, Chinese name, English name, model, fault type, orbit information, missile trajectory information, trajectory information and position information.

[0017] Preferably, the instruction fields of the simulation running process control instructions, simulation running status feedback instructions and simulation running scenario control instructions include the following naming rules: length is not more than 64 characters; consists of letters or numbers; uses camel case naming; and is not a keyword defined by C / C++ or the simulation system.

[0018] Preferably, the time jumping and speed changing behaviors are controlled by the envSkipTime and roomRate fields in the simulation running process control instructions; when the time jumping and speed changing requirements arise, they are set in the guidance and control software, and the guidance and control software generates the simulation running process control instructions in JSON format and sends them to the simulation engine; after the simulation engine receives and parses them, it executes the corresponding time jumping and speed changing behaviors, and feeds back the execution status to the guidance and control software.

[0019] Preferably, the simulation status is provided by the simulation engine and sent to the guide control software. Every preset time period, the simulation engine records the status of the simulation scene, generates a simulation operation status feedback instruction in JSON format, and sends it to the guide control software; after receiving and parsing, the guide control software displays the real-time status of the simulation scene.

[0020] Preferably, the simulation running scene control instructions are divided into an instruction header and an instruction body to control the intervention behavior of the simulation scene; after setting the instructions for adding and deleting entities and changing posture and trajectory, the guidance and control software assembles the instruction header and the instruction body to generate the simulation running scene control instructions in JSON format, and sends it to the simulation engine; after receiving and parsing, the simulation engine executes the corresponding intervention behavior and feeds back the execution status to the guidance and control software.

[0021] Compared with the prior art, the present invention has the following beneficial effects:

[0022] The present invention has high versatility, controllability and scalability; first, it can flexibly control the simulation process, and can jump time and change speed; second, it can obtain the simulation status in real time, and can listen and monitor; third, it can quickly intervene in the simulation scene, and can add or delete entities, change attitude and orbit; it can meet various forms of simulation system control requirements and provide protocol support for the construction of the satellite simulation system control layer. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0024] Figure 1 This is a diagram of the satellite simulation system guidance and control command protocol composition. DETAILED DESCRIPTION

[0025] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0026] Example 1

[0027] The satellite simulation system control command protocol provided by the present invention has high versatility, controllability and scalability.

[0028] First, the simulation process can be flexibly controlled, with time jumps and speed changes;

[0029] The time jump and speed change behavior are controlled by the "envSkipTime" and "roomRate" fields in the simulation process control instructions. When the time jump and speed change requirements are generated, they can be set in the control software. The control software will generate the simulation process control instructions in JSON format according to the instruction protocol and send them to the simulation engine. After receiving and parsing the simulation engine, it will execute the corresponding time jump and speed change behavior and feedback the execution status to the control software.

[0030] For example, the current simulation time of the simulation room with room ID 1 is 20:0:00 on July 1, 2023. The simulation process control instructions to set the time jump to 0:0:00 on July 2, 2023 and continue running at 32 times the speed are as follows:

[0031]

[0032] Second, it can obtain the simulation status in real time, and can monitor and control it;

[0033] The simulation status is provided by the simulation engine and sent to the control software. At regular intervals, the simulation engine records the status of the simulation scene, generates simulation running status feedback instructions in JSON format, and sends them to the control software. After receiving and parsing, the control software displays the real-time status of the simulation scene, i.e., listening and monitoring.

[0034] For example, the simulation scene with scene ID 1 is running at 2 times the speed, and its simulation running status feedback instruction at 14:0:00 on October 19, 2023 is as follows:

[0035]

[0036]

[0037] Third, it is possible to quickly intervene in the simulation scene by adding or deleting entities, and changing postures and trajectories.

[0038] The simulation running scene control instructions are divided into instruction header "head" and instruction body "body", which can control the intervention behavior of the simulation scene. The instruction type, execution time and other attributes are included in the instruction header, and the execution parameters are included in the instruction body. After setting instructions such as adding and deleting entities, changing posture and trajectory, the guidance and control software will assemble the instruction header and instruction body according to the instruction protocol, generate the simulation running scene control instructions in JSON format, and send it to the simulation engine. After receiving and parsing, the simulation engine executes the corresponding intervention behavior and feeds back the execution status to the guidance and control software.

[0039] For example, the simulation running scene control instructions for adding a satellite entity to the simulation scene with scene ID 1 are as follows:

[0040]

[0041]

[0042] For example, in the simulation scenario with scenario ID 1, the simulation running scenario control instructions for controlling the satellite with satellite ID Satellite-100 to change orbit are as follows:

[0043]

[0044]

[0045] The present invention provides a simulation running process control instruction protocol, which consists of a JSON string, including fields such as instruction ID, instruction type, running mode, assumption ID, scene start time, scene end time, jump time, assumption instance name, simulation instance ID, room ID, room mode, room status, current room time and running ratio.

[0046] The simulation running status feedback instruction consists of a JSON string, including fields such as simulation ID, simulation time, simulation status, and simulation ratio.

[0047] The simulation running scenario control command consists of a command header JSON string and a command body JSON string. The command header includes fields such as command ID, command type, command execution type, creator ID, creator name, creation time, assumption start time, command execution time, command response path, and remarks; the command body includes fields such as entity number, component number, Chinese name, English name, model, fault type, orbit information, missile trajectory information, trajectory information, and position information.

[0048] The types of control instructions for the simulation process include start, start, speed change, time jump, end, pause, time synchronization, forward (playback mode) and backward (playback mode). Start, start, end and pause will change the state of the simulation process; speed change and time jump will change the time of the simulation process.

[0049] The command fields follow the following naming conventions:

[0050] a. The length shall not exceed 64 characters;

[0051] b. composed of letters or numbers;

[0052] c. Use "camel case";

[0053] d. It is not a keyword defined by C / C++ or simulation system.

[0054] The command fields follow the following naming conventions:

[0055] a. The length shall not exceed 64 characters;

[0056] b. composed of letters or numbers;

[0057] c. Use "camel case";

[0058] d. It is not a keyword defined by C / C++ or simulation system.

[0059] The types of control instructions for simulation operation scenarios include adding space targets, adding ground mobile targets, adding ground fixed targets, adding components, changing the orbit of space targets, setting faults, and self-destruction of targets. Space targets include satellites, rockets, missiles, orbiters, and space debris; ground mobile targets include tanks, self-propelled artillery, and armored vehicles; and ground fixed targets include tracking and control stations, airports, and bridges.

[0060] The command fields follow the following naming conventions:

[0061] a. The length shall not exceed 64 characters;

[0062] b. composed of letters or numbers;

[0063] c. Use camelCase;

[0064] d. It is not a keyword defined by C / C++ or simulation system.

[0065] The simulation running process control instruction is identified by the "runCtrlInstruction" field, which is described as follows:

[0066] The instruction ID is identified by "insId" and its type is int;

[0067] The instruction type is identified by "insType", the type is int, and the options are start, start, speed change, time jump, end, pause, time synchronization, forward (playback mode) and backward (playback mode), etc.

[0068] The running mode is identified by "runMode", the type is int, and the application mode can be selected;

[0069] The scenario ID is identified by "envId" and its type is int;

[0070] The scene start time is marked with "envStartTime" and its type is string;

[0071] The scene end time is marked with "envEndTime" and its type is string;

[0072] The skip time is identified by "envSkipTime" and its type is string;

[0073] The scenario instance name is identified by "scenarioName" and the type is string;

[0074] The simulation instance ID is identified by "scenarioId" and its type is int;

[0075] The room ID is identified by "roomId" and its type is int;

[0076] The room mode is identified by "roomMode" and its type is int. You can choose normal mode, reconstruction mode, recovery mode, and playback mode.

[0077] The room status is identified by "roomState" and is of type int. You can select Idle, Configuring a Configuration File, Configuring a Position, Configuring a Quantity, Waiting for Initialization, Initialization Success, Initialization Failure, Running, Paused, or Ended.

[0078] The current room time is identified by "roomTime" and its type is string;

[0079] The operating rate is identified by "roomRate" and its type is double.

[0080] The simulation running status feedback instruction is identified by the "runCtrlInstructionFeedback" field, which is described as follows:

[0081] The simulation ID is identified by "scenarioId" and its type is int;

[0082] The simulation time is marked with "simCurrentTime" and its type is string;

[0083] The simulation state is marked with "simRunState" and its type is int. It can be selected from waiting for startup, initializing, initialization failure, initialization success, running, and paused.

[0084] The simulation rate is identified by "simRate" and its type is double.

[0085] The simulation running scenario control instruction, the instruction header is identified by the "head" field, which is described as follows:

[0086] The instruction ID is identified by "index" and its type is int;

[0087] The command type is identified by "cmdId" and its type is string;

[0088] The command execution type is marked with "cmdType", the type is int, and can be delayed, immediate, etc.

[0089] The creator ID is identified by "creatorId" and its type is string;

[0090] The creator name is identified by "creatorName" and the type is string;

[0091] The creation time is marked with "createTime" and its type is string;

[0092] The assumed start time is marked with "envStartTime" and its type is string;

[0093] The instruction execution time is marked with "insExecuteTime" and is of string type. It is determined by the instruction execution type. It is empty in delayed mode and a time string in immediate mode.

[0094] The instruction response path is identified by "objPath", of type string, determined according to the simulation model, and called by the simulation main program;

[0095] Remarks are marked with "remark" and are of string type.

[0096] The simulation running scene control instruction, the instruction body is marked with the "body" field, which is described as follows:

[0097] The entity number is identified by "entityNum", of type string, and is unique in a simulation instance;

[0098] The component number is identified by "componentNum", of type string, and is unique in a solid model component;

[0099] The Chinese name is identified by "nameCn" and the type is string;

[0100] The English name is identified by "nameEn" and the type is string;

[0101] The model is identified by "model" and its type is string;

[0102] The fault type is identified by "malfunctionType", of type int, and can be orbit maneuver fault, attitude fault, sensor fault, communication fault, object disability, etc.

[0103] Orbit information is marked with "orbit" and is of type json, including orbit type, time epoch, position velocity, double-row root number, Kepler root number, Kepler LAN root number, longitude and latitude, etc.

[0104] Missile trajectory information is marked with "trajectory" and is of type json, including trajectory model, launch point location, landing point location, launch time, and landing time, etc.

[0105] The trajectory information is identified by "route" and is of type JSON array. Each array element includes the time epoch, instantaneous position, etc.

[0106] The location information is identified by "location" and is of json type, including longitude, latitude, and altitude.

[0107] The track information is described as follows:

[0108] The orbit type is identified by "orbitType", which is of type int. It can be selected from position velocity, double row root number, Kepler root number, Kepler LAN root number, longitude and latitude, etc.

[0109] The time epoch is marked with "gregTime" and is of json type, including year, month, day, hour, minute, and second;

[0110] Position and speed are marked with "posVel" and are of json type, including X-direction position, Y-direction position, Z-direction position, X-direction speed, Y-direction speed, and Z-direction speed, etc. They are determined according to the track type and are required in position and speed mode.

[0111] The double-line root number is marked with "tle" and is of type json, including the first line, the second line, etc. It is determined by the track type and is required in the double-line root number mode;

[0112] Kepler roots are marked with "kepler" and are of type json. They include semi-major axis, eccentricity, orbital inclination, right ascension of ascending node, argument of perigee, and mean anomaly. They are determined by the orbit type and are required in Kepler root mode.

[0113] The Kepler LAN elements are marked with "keplerLan" and are of type json. They include the semi-major axis, eccentricity, orbital inclination, ascending node longitude, argument of perigee, and mean anomaly. They are determined by the orbit type and are required in Kepler LAN mode.

[0114] The longitude, latitude and altitude are marked with "lla" and are of json type. They include longitude, latitude, altitude, longitude change rate, latitude change rate and altitude change rate. They are determined according to the orbit type and are required in longitude, latitude and altitude mode.

[0115] The missile trajectory information is described as follows:

[0116] The trajectory model is identified by "trajectoryType" and its type is int;

[0117] The launch point is identified by "launchPoint" and is of type json, including longitude, latitude, and altitude. The impact point is identified by "impactPoint" and is of type json, including longitude, latitude, and altitude.

[0118] The launch time is identified by "launchTime" and its type is string;

[0119] The impact time is identified by "impactTime" and its type is string.

[0120] The trajectory information is described as follows:

[0121] The time epoch is marked with "gregTime" and is of type json, including year, month, day, hour, minute, and second, etc. The instantaneous position is marked with "location" and is of type json, including longitude, latitude, and altitude, etc.

[0122] The position information, launch point position, landing point position and instantaneous position are described as follows:

[0123] Longitude is marked with "longitude", of type double, with a range of [0,360), and in units of °;

[0124] Latitude is marked with "latitude", the type is double, the value range is [-90,90], and the unit is °;

[0125] The altitude is marked with "altitude", the type is double, the value range is [-12, +∞), and the unit is km.

[0126] The time epoch is described as follows:

[0127] Year is identified by "year", of type int, with a value range of [1697,2331];

[0128] Month is identified by "mon", of type int, with a value range of [1,12];

[0129] Day is identified by "day", the type is int, and the value range is [1,31];

[0130] The hour is marked with "hour", the type is int, and the value range is [0,23];

[0131] The points are marked with "min", the type is int, and the value range is [0,59];

[0132] Seconds are identified by "sec", of type double, and in the range [0,60).

[0133] The position speed is described as follows:

[0134] The X-direction position is marked with "x", of type double, with a range of [0,+∞), and in km;

[0135] The Y-direction position is marked with "y", of type double, with a range of [0,+∞), and in km;

[0136] The Z-direction position is marked with "z", of type double, with a range of [0,+∞), and in km; the X-direction velocity is marked with "vx", of type double, with a range of [0,+∞), and in km / s;

[0137] The Y-direction speed is marked with "vy", of type double, with a range of [0,+∞), and in units of km / s;

[0138] The speed in the Z direction is marked with "vz", of type double, with a range of [0,+∞), and in units of km / s.

[0139] The double row root number is described as follows:

[0140] The first line is identified by "tleLine1" and is of type string;

[0141] The second line is identified by "tleLine2" and is of type string.

[0142] The Kepler root number is described as follows:

[0143] The semi-major axis is marked with "sma", of type double, with a range of [0,+∞), and in km;

[0144] The eccentricity is marked with "ecc", the type is double, and the value range is [0,1);

[0145] The orbital inclination is marked with "inc", the type is double, the value range is [0,180), and the unit is °;

[0146] The right ascension of the ascending node is marked with "raan", of type double, with a range of [0,360), and in degrees;

[0147] The argument of perigee is marked with "w", of type double, with a range of [0,360), and in degrees;

[0148] The mean anomaly angle is marked with "ma", of type double, with a range of [0,360), and in degrees.

[0149] The Kepler LAN root number is described as follows:

[0150] The semi-major axis is marked with "sma", of type double, with a range of [0,+∞), and in km;

[0151] The eccentricity is marked with "ecc", the type is double, and the value range is [0,1);

[0152] The orbital inclination is marked with "inc", the type is double, the value range is [0,180), and the unit is °;

[0153] The longitude of the ascending node is marked with "lan", the type is double, the value range is [0,360), and the unit is °;

[0154] The perigee argument is marked with "w", the type is double, the value range is [0,360), and the unit is °;

[0155] The mean anomaly angle is marked with "ma", of type double, with a range of [0,360), and in degrees.

[0156] The longitude and latitude are described as follows:

[0157] Longitude is marked with "longitude", of type double, with a range of [0,360), and in units of °;

[0158] Latitude is marked with "latitude", of type double, with a range of [-90,90], and in units of °;

[0159] The altitude is marked with "altitude", the type is double, the value range is [-12, +∞), and the unit is km;

[0160] The longitude change rate is marked with "longitudeDot", the type is double, the value range is [0, +∞), and the unit is ° / s;

[0161] The latitude change rate is marked with "latitudeDot", the type is double, the value range is [0, +∞), and the unit is ° / s;

[0162] The altitude change rate is marked with "altitudeDot", the type is double, the value range is [0,+∞), and the unit is km / s.

[0163] Example 2

[0164] Embodiment 2 is a preferred example of Embodiment 1.

[0165] like Figure 1 As shown, the satellite simulation system guidance and control command protocol includes a simulation operation process control command protocol, a simulation operation state feedback command protocol and a simulation operation scene control command protocol.

[0166] The simulation running process control instructions are composed of a JSON string, including instruction ID, instruction type, running mode, scenario ID, scenario start time, scenario end time, jump time, scenario instance name, simulation instance ID, room ID, room mode, room status, current room time, and running magnification.

[0167] For example, if you need to start a simulation process with room ID 101, room mode normal mode, running mode application mode, scenario start time 0:0:00 on July 1, 2023, scenario name SISE_1, simulation instance ID 12, and scenario ID 5, the corresponding simulation process control instruction should be:

[0168]

[0169] The simulation operation state feedback instruction protocol disclosed in the present invention is characterized by:

[0170] The simulation running status feedback instruction consists of a JSON string, including fields such as simulation ID, simulation time, simulation status, and simulation ratio.

[0171] For example, for a simulation process with a simulation ID of 12, a simulation time of 14:18:45 on October 19, 2023, a simulation status of successful initialization, and a simulation magnification of 2.0, the corresponding simulation running status feedback instruction should be:

[0172]

[0173] The simulation operation scene control instruction protocol disclosed in the present invention is characterized by:

[0174] The simulation running scenario control command consists of a command header JSON string and a command body JSON string. The command header includes fields such as command ID, command type, command execution type, creator ID, creator name, creation time, assumption start time, command execution time, command response path, and remarks; the command body includes fields such as entity number, component number, Chinese name, English name, model, fault type, orbit information, missile trajectory information, trajectory information, and position information.

[0175] For example, if you need to add a satellite entity to the simulation running scene with simulation ID 12, the corresponding simulation running scene control instruction should be:

[0176]

[0177]

[0178] Those skilled in the art know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.

[0179] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A satellite simulation operation process control system, characterized in that: include: Simulation operation process control module, simulation operation status feedback module and simulation operation scenario control module; The simulation operation process control module is implemented by simulation operation process control instructions, and the simulation operation process control instructions are composed of a JSON string, including instruction ID, instruction type, operation mode, scenario ID, scenario start time, scenario end time, jump time, scenario instance name, simulation instance ID, room ID, room mode, room status, current room time and operation magnification; The simulation operation status feedback module is implemented by a simulation operation status feedback instruction, and the simulation operation status feedback instruction consists of a JSON string, including a simulation ID, a simulation time, a simulation status, and a simulation magnification; The simulation operation scenario control module is implemented through the simulation operation scenario control instruction, and the simulation operation scenario control instruction consists of an instruction header JSON string and an instruction body JSON string; the instruction header includes an instruction ID, an instruction type, an instruction execution type, a creator ID, a creator name, a creation time, a hypothetical start time, an instruction execution time, an instruction response path, and remarks; the instruction body includes an entity number, a component number, a Chinese name, an English name, a model, a fault type, orbit information, missile trajectory information, track information, and position information.

2. The satellite simulation operation process control system according to claim 1, characterized in that: The instruction fields of the simulation running process control instruction, simulation running state feedback instruction and simulation running scenario control instruction include the following naming rules: the length is not more than 64 characters; it is composed of letters or numbers; it uses camel case naming method; Not a C / C++ or emulation system-defined keyword.

3. The satellite simulation operation process control system according to claim 1, characterized in that: The time jump and speed change behaviors are controlled by the envSkipTime and roomRate fields in the simulation running process control instructions. When the time jump and speed change requirements are generated, they are set in the control software. The control software generates the simulation running process control instructions in JSON format and sends them to the simulation engine. After receiving and parsing, the simulation engine executes the corresponding time jump and speed change behaviors, and feeds back the execution status to the control software.

4. The satellite simulation operation process control system according to claim 1, characterized in that: The simulation status is provided by the simulation engine and sent to the control software. Every preset time period, the simulation engine records the status of the simulation scene, generates simulation operation status feedback instructions in JSON format, and sends them to the control software; after receiving and parsing, the control software displays the real-time status of the simulation scene.

5. The satellite simulation operation process control system according to claim 1, characterized in that: The simulation running scene control instructions are divided into an instruction header and an instruction body, which control the intervention behavior of the simulation scene; after setting the instructions for adding and deleting entities and changing posture and trajectory, the guidance and control software assembles the instruction header and the instruction body, generates the simulation running scene control instructions in JSON format, and sends it to the simulation engine; after receiving and parsing, the simulation engine executes the corresponding intervention behavior and feeds back the execution status to the guidance and control software.

6. A satellite simulation operation process control method, characterized in that: include: The simulation operation process control step is implemented by the simulation operation process control instruction, which consists of a JSON string, including instruction ID, instruction type, operation mode, scenario ID, scenario start time, scenario end time, jump time, scenario instance name, simulation instance ID, room ID, room mode, room status, current room time and operation magnification; The simulation running status feedback step is implemented by a simulation running status feedback instruction, wherein the simulation running status feedback instruction is composed of a JSON string, including a simulation ID, a simulation time, a simulation status, and a simulation magnification; Simulation operation scenario control step: It is implemented through simulation operation scenario control instructions, and the simulation operation scenario control instructions are composed of an instruction header JSON string and an instruction body JSON string; the instruction header includes instruction ID, instruction type, instruction execution type, creator ID, creator name, creation time, assumed start time, instruction execution time, instruction response path and remarks; the instruction body includes entity number, component number, Chinese name, English name, model, fault type, orbit information, missile trajectory information, trajectory information and position information.

7. The satellite simulation operation process control method according to claim 6, characterized in that: The instruction fields of the simulation running process control instruction, simulation running state feedback instruction and simulation running scenario control instruction include the following naming rules: the length is not more than 64 characters; it is composed of letters or numbers; it uses camel case naming method; Not a C / C++ or emulation system-defined keyword.

8. The satellite simulation operation process control method according to claim 6, characterized in that: The time jump and speed change behaviors are controlled by the envSkipTime and roomRate fields in the simulation running process control instructions. When the time jump and speed change requirements are generated, they are set in the control software. The control software generates the simulation running process control instructions in JSON format and sends them to the simulation engine. After receiving and parsing, the simulation engine executes the corresponding time jump and speed change behaviors, and feeds back the execution status to the control software.

9. The satellite simulation operation process control method according to claim 6, characterized in that: The simulation status is provided by the simulation engine and sent to the control software. Every preset time period, the simulation engine records the status of the simulation scene, generates simulation operation status feedback instructions in JSON format, and sends them to the control software; after receiving and parsing, the control software displays the real-time status of the simulation scene.

10. The satellite simulation operation process control method according to claim 6, characterized in that: The simulation running scene control instructions are divided into an instruction header and an instruction body, which control the intervention behavior of the simulation scene; after setting the instructions for adding and deleting entities and changing posture and trajectory, the guidance and control software assembles the instruction header and the instruction body, generates the simulation running scene control instructions in JSON format, and sends it to the simulation engine; after receiving and parsing, the simulation engine executes the corresponding intervention behavior and feeds back the execution status to the guidance and control software.

Images