A method for rapid review of system OODA loop based on custom events

Abstract

The present invention discloses a method for rapid review of a system OODA loop based on custom events, comprising the following steps: Step 1, defining events in the mission process of a ship system and defining a set of event attributes; sorting out the total number of system events according to system functions and mission processes; forming a corresponding relationship of system / device-event-message-field according to the event subject classification based on the extraction path in the event definition; Step 2, configuring different review elements according to each different mission and restoring the mission process; Step 3, determining the events occurring in the system / device to be extracted based on the review element configuration, automatically associating them with specific message data, and extracting the data corresponding to the events from the fields of the message; Step 4, displaying the review data after completing the review data preparation. The present invention can realize rapid review of the OODA loop process, view the system's working status and performance indicators in real time, and support rapid positioning of system anomalies / faults.

Description

Technical Field

[0001] The present invention relates to the field of development and post-delivery support of a certain system of a ship, and in particular to a system OODA loop rapid review method based on custom events. Background Art

[0002] The working process of a certain system on a ship is an OODA loop process, namely discovery (detection and perception of targets by multiple sensors), judgment (identification of targets, processing and generating target status), decision-making (generation of attack / defense plans), and action (control of weapons to attack / defend targets). A certain system is mainly composed of multiple sensors, command and control systems, and multiple weapons. During the development phase, the system needs to conduct performance verification tests and performance identification tests, and perform various training and exercise tasks after delivery. During testing, training, and exercise tasks, users are concerned about whether the system has achieved the expected mission objectives, whether the system is working properly, and whether the system performance indicators meet the relevant requirements. Users hope to review the system's working process as soon as possible after a mission is completed. All of this has put forward the demand for rapid review of the mission process.

[0003] System replay processes data collected during a mission to restore target movement and the system's OODA loop process, including the system's responses and results, as well as system state changes, from target discovery and identification, to situation formation and decision-making, to attacking or defending the target. System replay has the following characteristics:

[0004] First, the system is complex, consisting of multiple sensors, command and control systems, multiple weapons, as well as navigation equipment, communication equipment, network equipment and other support equipment.

[0005] Second, the OODA loop is complex. The system must complete a series of steps in a short period of time, including multiple sensors detecting the target and establishing the target track; the command and control system fusing the target track data from multiple sensors to generate a fused target situation, generating a strike / defense plan, and automatically issuing the plan or target instructions to multiple weapons; and the weapons performing calculations and launching ammunition to strike / defend the target.

[0006] Third, information exchange is complex. The system achieves integrated linkage through complex information exchange. The exchanged information includes system status, target data, attack / defense plans, target instructions, and combat intervention commands.

[0007] When a system performs a test, drill, or training task, users first focus on whether the system has achieved the intended objectives. Secondly, they focus on whether the system is functioning properly and whether its performance indicators meet requirements. Therefore, after the task is completed, it is crucial to be able to quickly review the system's working process.

[0008] After the task is completed, the task process should be automatically reviewed based on the collected data. The following technical issues need to be solved:

[0009] The first is the definition and classification of review events: review events must be defined in a unified format, and the classification of review events must be able to completely cover the system OODA loop process.

[0010] The second is the configuration of review elements: different review elements are configured according to the differences of each task.

[0011] The third is the extraction of review events: it must be able to automatically associate with specific message data based on the review element definition and review element configuration, and extract the review data to be reviewed from the message fields.

[0012] Fourth, the review data is displayed: the review elements are displayed in an appropriate form. Through the review, you can analyze or directly see whether the system is working properly and whether the system performance indicators meet the relevant requirements. Summary of the Invention

[0013] The technical problem to be solved by the present invention is to provide a system OODA loop rapid review method based on custom events in response to the defects in the existing technology.

[0014] The technical solution adopted by the present invention to solve its technical problem is:

[0015] The present invention provides a method for quickly reviewing a system OODA loop based on a custom event, the method comprising the following steps:

[0016] Step 1: Replay event definition:

[0017] Define the events in the ship system's mission process. Events refer to the system's response to the target and its results, as well as the system's state changes during the mission process. The system's response is summarized as the OODA loop process.

[0018] Define a set of event attributes, including: event subject, occurrence time, event description, target object, extraction path, and judgment conditions; the classification of event subjects can fully cover the system OODA loop process;

[0019] Organize the total number of system events based on system functions and task processes; classify the events according to the extraction path in the event definition and the subject, forming a corresponding relationship between system / device, event, message, and field;

[0020] Step 2: Re-configure the elements:

[0021] Configure different review elements according to each task to restore the task process;

[0022] Step 3: Replay event extraction:

[0023] Based on the configuration of the review elements, the system / device events to be extracted are determined, automatically associated with specific message data, and the data corresponding to the events is extracted from the message fields.

[0024] Step 4: Review the data and see:

[0025] After completing the review data preparation, perform the review data display to view the system's working status and performance indicators in real time.

[0026] Furthermore, the OODA loop process in step 1 of the present invention includes: sensor detection, track establishment, track cancellation, and track loss; the command and control system fuses multiple sensor target tracks to generate a fused target track; makes threat assessments on the target; makes strike / defense decisions and generates strike / defense plans; the command and control system issues strike / defense plans or target instructions to the weapon; the weapon solves, tracks the target, and launches ammunition to strike / defend the target.

[0027] Furthermore, the event attribute set in step 1 of the present invention specifically includes:

[0028] Event subject: the system / device that responds to the target, and all system devices related to the target;

[0029] Time of occurrence: the time when the event occurred;

[0030] Event description: used to describe the event itself;

[0031] Target object: used to mark the target object corresponding to the event, and the target object is identified by the batch number;

[0032] Extraction path: used to specify how to extract the event attribute information, and define the message, field, and specific value in the field corresponding to the event;

[0033] Judgment condition: defines the judgment condition for whether an event occurs.

[0034] Furthermore, the judgment conditions of the present invention specifically include:

[0035] For one-time messages: each time this message is received, it is considered that this event has occurred;

[0036] For periodic messages, an event is determined to occur when a field value changes.

[0037] If a certain message is received continuously, it is determined that an event occurs;

[0038] If a certain message is not received continuously, it is determined that an event occurs.

[0039] Furthermore, the review elements in step 2 of the present invention include:

[0040] If you are configuring the working status, select the status item and the corresponding message and field;

[0041] If the configuration is track data, select the data items of the target motion track, as well as the corresponding messages and fields;

[0042] If you are configuring an event, select the corresponding event name and event attributes.

[0043] Furthermore, the process of reconfiguring the elements in step 2 of the present invention includes:

[0044] Add a review plan;

[0045] Select the subsystem / equipment under the review plan;

[0046] Get all status items under each subsystem / device, and select the status items of interest under each subsystem / device;

[0047] Get all track data items under each subsystem / device, and select the data items of interest under each subsystem / device;

[0048] Obtain all key events for each subsystem / device and select the events of interest for each subsystem / device.

[0049] Furthermore, the event extraction method in step 3 of the present invention includes:

[0050] Based on the configuration of the review elements, determine which systems / devices and which events to extract, and configure the packets to be recorded. Before the task begins, connect the packet recording device to the switch mirror port or a specific port. After the task is completed, use the packet parsing program to parse the packets to be analyzed.

[0051] During event extraction, data for a specific time period is extracted by inputting a time range; target objects in the task process are associated through batch numbers; target objects are determined by fusing target batch numbers; during event extraction, extraction is performed by inputting the fused target batch numbers corresponding to one or more target objects.

[0052] Furthermore, the method for setting the batch number of the present invention is specifically as follows:

[0053] Set a target batch number for each sensor. The command and control system sets its own target batch number range for the fusion target. The command and control system fuses the target tracks of multiple sensors to generate a fusion target. The command and control system automatically maintains the correspondence between the fusion target batch number and the original target batch number of the sensor, establishes a batch number comparison table, and sends the batch number comparison relationship message online. The specific structure of the batch number comparison table is as follows:

[0054] The batch number comparison table records multiple target objects, each target object records multiple fusion batch numbers, each fusion batch number records multiple groups of target data, and each group of target data records multiple target batch numbers.

[0055] Furthermore, the data processing flow in the event extraction process in step 3 of the present invention is as follows:

[0056] a. Data parsing: Based on the replay element configuration, obtain all the messages corresponding to the elements. For each message, create a corresponding message data table in the database based on the message name and field. Parse the message corresponding to the replay element configuration from the message data file and store it in the corresponding message data table. Parse the target true value data from the target true value file, transform it into data that can be used for error analysis through coordinate system conversion, and store it in the true value data table.

[0057] b. Batch number comparison: Obtain the comparison relationship between the fusion batch number and the sensor batch number from the batch number comparison relationship and the message data table corresponding to the message. According to one or more target objects input during event extraction, establish a comparison relationship between the target object and the fusion batch number. Write the established comparison relationship between the target object, the fusion batch number and the sensor batch number into the batch number comparison table.

[0058] c. Event extraction: Based on the correspondence between system / device, event, message, and field, the event data that meets the conditions is retrieved from the corresponding message data table and stored in the event data table;

[0059] d. Track extraction: According to the configuration of the replay elements, obtain the message and field corresponding to the target motion track, query the data of the corresponding field from the message data table, and store it in the track data table;

[0060] e. Error analysis: Obtain target track data from the track data table, obtain target true value data from the true value data table, obtain the linear error, systematic error, random error, and mean square error of the target data through calculation, and store the error calculation results in the error data table.

[0061] Furthermore, the replay data display in step 4 of the present invention provides multiple data display formats:

[0062] Basic display formats include: event graphs, with time on the horizontal axis and system / device on the vertical axis; various target data graphs, including distance-time, azimuth-time, and elevation-time; and various error graphs, including distance difference-time, azimuth difference-time, and elevation difference-time.

[0063] Target data graph, used to simultaneously display the data of multiple targets; for target data graphs in various forms, a subgraph matrix is ​​used for display;

[0064] Events related to the target are displayed on the target data graph based on the time of occurrence.

[0065] The beneficial effects produced by the present invention are:

[0066] The proposed method for rapid system OODA loop review based on custom events can be used to quickly review the system's OODA loop during testing, training, and exercises. This allows for analysis or direct verification of system operation and performance indicators. This system review supports the rapid location of system anomalies and faults.

[0067] The method proposed in the present invention is applied in a certain type of onshore joint debugging test. By reviewing the test process, it can quickly determine whether the system is working normally and whether the system performance indicators meet the relevant requirements, thereby enhancing the test means.

[0068] The advantages of the present invention are:

[0069] (1) Speed: Event definition and review element configuration are completed in advance, and the review can be automatically performed after the test, training, and exercise are completed. This greatly improves the efficiency of evaluating test, training, and exercise results, and helps to quickly discover and locate problems.

[0070] (2) Completeness: Through event customization, the responses and status changes of all relevant subsystems / devices to one or more target objects can be defined as events to be reviewed, ensuring the completeness of the review content.

[0071] (3) Flexibility: Review elements can be flexibly selected based on the specific subjects and focus of each test, training, or exercise. Through the configuration of review elements, one or more target objects, subsystems / equipment to be reviewed, and corresponding events can be flexibly selected for review, ensuring the completeness of the review content. At the same time, the review format can be flexibly selected. Single review data can be displayed, or multiple review data can be superimposed and displayed. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0073] Figure 1 It is the configuration structure of the replay elements of the embodiment of the present invention;

[0074] Figure 2 This is the replay element configuration process of an embodiment of the present invention;

[0075] Figure 3 This is the data processing flow of the embodiment of the present invention;

[0076] Figure 4 This is the event extraction process of an embodiment of the present invention;

[0077] Figure 5 This is the event judgment process of an embodiment of the present invention (corresponding to a one-time message);

[0078] Figure 6 This is the event judgment process of an embodiment of the present invention (corresponding to periodic messages and field value changes);

[0079] Figure 7 This is the event judgment process of an embodiment of the present invention (corresponding to continuous reception of messages);

[0080] Figure 8 This is the event judgment process of an embodiment of the present invention (corresponding to continuous failure to receive messages);

[0081] Figure 9 This is the event attribute extraction process of the embodiment of the present invention;

[0082] Figure 10 This is the target batch number comparison table structure of an embodiment of the present invention;

[0083] Figure 11 This is the data organization of the replay in the embodiment of the present invention;

[0084] Figure 12 This is a replay display configuration structure according to an embodiment of the present invention;

[0085] Figure 13 It is a test process event of an embodiment of the present invention;

[0086] Figure 14 is the sensor track of an embodiment of the present invention;

[0087] Figure 15 is the sensor distance difference of the embodiment of the present invention;

[0088] Figure 16 is an event superimposed motion trajectory of an embodiment of the present invention;

[0089] Figure 17 It is a comprehensive display of the embodiments of the present invention. DETAILED DESCRIPTION

[0090] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0091] Example 1:

[0092] The OODA loop rapid review method based on custom events in an embodiment of the present invention is as follows:

[0093] (1) Event definition

[0094] Events specifically refer to the system's responses to targets and their outcomes, as well as changes in system state, during a mission. The system's responses can be summarized as an OODA loop process, including sensor detection (track establishment, track cancellation, and track loss); the command and control system fuses multiple sensor target tracks to generate a fused target track; threat assessment of the target; attack / defense decisions and generation of an attack / defense plan; the command and control system issues an attack / defense plan or target designation to the weapon; and the weapon solves the problem, tracks the target, and launches ammunition to attack / defend the target.

[0095] The event attribute set includes: event subject, occurrence time, event description, target object, extraction path, and judgment condition.

[0096] a. Event subject: the system / device that responds to the target, and all system devices related to the target.

[0097] b. Time of occurrence: the moment when the event occurs, such as the moment when the target is discovered.

[0098] c. Event description: Describe the event itself, such as target discovery / loss, target instruction issuance / revocation, launch conditions met, launch completed, etc.

[0099] d. Target object: used to mark the target object corresponding to the event, and the target object is identified by the batch number (sensor original batch number or fusion batch number).

[0100] e. Extraction path: specifies how to extract the event attribute information, and defines the message, field, and specific value in the field corresponding to the event.

[0101] f. Judgment conditions: define the judgment conditions for whether the event occurs. The details are as follows:

[0102] For one-time messages, each time this message is received, the event is considered to have occurred. For example, upon receiving a one-time message for a combat intervention command, the "combat intervention" event is considered to have occurred.

[0103] For periodic messages, an event is determined to have occurred when a certain field value changes. For example, if a sensor's "target track" message is periodically received and the "track status" field value is "new track", a "target established track" event is determined to have occurred.

[0104] If a certain message is received continuously, an event is determined to have occurred. For example, if a certain field value of a system status message is "channel not ready" for three consecutive times, it is determined to be "channel released".

[0105] If a certain message is not received continuously, an event is determined to have occurred. For example, if the control system does not receive target data from a sensor three times in a row, the sensor is considered "target lost".

[0106] Based on system functions and task processes, the system events are summarized. Based on the extraction path in the event definition and the event subject classification, a corresponding relationship of system / device (event subject) - event - message - field is formed.

[0107] (2) Replay element configuration

[0108] Restore the task process by displaying the status of related systems / equipment, target movement trajectory, and the sequence of events. Replay element configuration is to select replay elements based on the specific task and restore the task process. Replay elements mainly include two aspects:

[0109] First, for target trajectory, you need to select the system / device name, the message corresponding to the target trajectory data, and the specific data items. For example, you can select a sensor, select the target track message for that sensor, and select the distance, azimuth, and elevation angle. This includes selecting the system / device and its corresponding event.

[0110] The second is to extract events, you need to select the system / device name, event name, and event attributes.

[0111] The structure of the replay element configuration plan is as follows Figure 1 The flowchart of customized configuration of replay elements is as shown below. Figure 2 shown.

[0112] (3) Event extraction

[0113] Based on the replay element configuration, determine which systems / devices and events to extract and configure the packets to be recorded. Before starting the task, connect the packet recording device to a mirrored port or a specific port on the switch. After the task is complete, use a packet parser to parse the packets.

[0114] When extracting events, you can extract data for a specific time period by entering a time range.

[0115] For the target objects in the mission process, they are mainly associated through batch numbers. Each sensor has its own target batch number range. The command and control system fusion target also has its own target batch number range. After a single sensor finds a target, it may lose the target due to target maneuvering, clutter influence, etc. The target batch number will be reallocated after re-batching. The command and control system fuses the target tracks of multiple sensors to generate a fused target. The command and control system automatically maintains the correspondence between the fused target batch number and the original target batch number of the sensor (see the batch number comparison table structure). Figure 10) and send the batch number-based message online. Therefore, only the target batch number needs to be recorded. The target object is determined by the target batch number. When extracting events, the target object (or objects) can be extracted by entering the corresponding target batch number.

[0116] Data processing flow such as Figure 3 The specific processing flow is as follows:

[0117] a. Based on the replay element configuration, obtain all corresponding messages. For each message, create a corresponding message data table in the database based on the message name and fields. Parse the message corresponding to the replay element configuration from the message data file and store it in the corresponding message data table. Parse the target truth data from the target truth file and, through coordinate system conversion, generate data suitable for error analysis and store it in the truth data table.

[0118] b. Obtain the fusion batch number-sensor batch number comparison relationship from the message data table corresponding to the batch number comparison relationship message, establish the target object-fusion batch number comparison relationship based on the target object (one or more) input during event extraction, and write the established target object-fusion batch number-sensor batch number comparison relationship into the batch number comparison table.

[0119] c. According to the corresponding relationship between system / device (event subject)-event-message-field, query the event data that meets the conditions from the corresponding message data table and store it in the event data table. The event extraction process is as follows: Figure 4 shown.

[0120] For events corresponding to one-time messages, the judgment process is as follows: Figure 5 shown.

[0121] The event judgment process for periodic messages and changes in a field value is as follows: Figure 6 shown.

[0122] The event judgment process corresponding to the continuous reception of a certain message is as follows Figure 7 shown.

[0123] The event judgment process corresponding to the continuous failure to receive a certain message is as follows: Figure 8 shown.

[0124] The event attribute extraction process is as follows Figure 9 shown.

[0125] d. According to the configuration of the replay elements, obtain the message and field corresponding to the target motion trajectory, query the data of the corresponding field from the message data table, and store it in the track data table.

[0126] e. Obtain the target track data from the track data table, obtain the target true value data from the true value data table, obtain the linear error, systematic error, random error, mean square error, etc. of the target data through calculation, and store the error calculation results in the error data table.

[0127] (4) Replay data shows

[0128] It is divided into two stages: data preparation and data display. Data preparation is to extract events and other data elements (including status data items and track data items) according to the configuration of the data elements. Figure 11 .

[0129] After completing the data preparation for the replay, the replay data is displayed. First, a variety of data display formats are provided (see Figure 12 ).

[0130] Basic display formats include: event diagrams, with time on the horizontal axis and system / device on the vertical axis; various target data diagrams (distance-time diagram, azimuth-time diagram, elevation-time diagram, etc.); and various error diagrams (distance difference-time diagram, azimuth difference-time diagram, elevation difference-time diagram, etc.).

[0131] Target data graphs can display data of multiple targets simultaneously. For target data graphs of various formats, a subgraph matrix can be used to display them.

[0132] Events related to a target can be displayed on the target data graph based on the time at which they occurred.

[0133] Example 2:

[0134] In an embodiment of the present invention, according to the method proposed in the present invention, the implementation process of the system interception of aerial target test review is illustrated by taking the review event definition, review element configuration, review event extraction, and review data display as a reference example for the application of this method.

[0135] The test process involved launching a target drone (Aircraft 1) along a predetermined route toward the ship. The ship's Radars A and B activated, searching for and detecting aerial targets, finding them, establishing their flight paths, and detecting their microwave emissions. The command and control system integrated the target's flight paths and microwave emissions to generate a fused target, developing a defense strategy, and the weapon system engaged the target. The duration from launching the drone to the completion of the engagement by the various weapons systems was several minutes.

[0136] The event definition, replay element configuration, replay event extraction, and replay data display during the test are as follows:

[0137] 1. Definition of replay events

[0138] The definition of replay events includes:

[0139] Target establishment and track loss of Radar A / Radar B, fusion target and decision generation of defense plan of command and control system, and target strike of weapon system.

[0140] Taking the target navigation event of radar A as an example, the event definition is explained:

[0141] Event subject: Radar A;

[0142] Event description: Target navigation;

[0143] Target object: Aircraft 1;

[0144] Extract path: The value of the "Track Status" field of the "Target Track" message is equal to "New Track";

[0145] Judgment condition: When the "target track" message is received and the field value of "track status" is "new track", it is judged that the "target track establishment" event occurs;

[0146] Occurrence time: The "timestamp" field value of the message data that generated the event.

[0147] 2. Replay element configuration

[0148] The review elements include:

[0149] The actual movement process of aircraft 1 (with built-in GPS to record movement trajectory);

[0150] Target track of Radar A / Radar B (range, azimuth, elevation);

[0151] Target indication data (range, azimuth, elevation, whether microwave information is included);

[0152] Events generated by radar, accusations, and weapons.

[0153] 3. Replay event extraction

[0154] a. Data analysis

[0155] Extract target range, azimuth, and elevation data from target track messages from radar A / radar B;

[0156] The target true value data is parsed from the GPS data file of aircraft 1, and the target range, azimuth, and elevation angle data are extracted through coordinate system conversion.

[0157] b. Batch number comparison

[0158] Obtain the comparison relationship between the fusion batch number and the radar A / radar B batch number from the batch number comparison relationship message, input the comparison relationship between aircraft 1 and the fusion batch number, and finally establish the comparison relationship between aircraft 1, the fusion batch number, and the radar A / radar B batch number.

[0159] c. Event extraction

[0160] Extract radar target establishment and track loss events from the "target track" message;

[0161] Extract the fusion target of the command and control system from the "fusion target" message and make decisions to generate defense plan events;

[0162] Extract the target strike event of the weapon system from the "XX weapon engagement status" message.

[0163] d. Track extraction

[0164] Extract radar target track data (range, azimuth, elevation) from the "target track" message.

[0165] e. Error analysis

[0166] By calculating the target track data of radar A / radar B and the target true value data of aircraft 1, the linear difference, systematic difference, random difference, mean square error, etc. of the target data are obtained.

[0167] 4. Review data shows

[0168] The data show the results. Figures 13 to 17 .

[0169] It should be understood that those skilled in the art can make improvements or changes based on the above description, and all such improvements and changes should fall within the scope of protection of the appended claims of the present invention.

Claims

1. A system OODA loop rapid review method based on custom events, characterized by: The method comprises the following steps: Step 1: Replay event definition: Define the events in the ship system's mission process. Events refer to the system's response to the target and its results, as well as the system's state changes during the mission process. The system's response is summarized as the OODA loop process. Define a set of event attributes, including: event subject, occurrence time, event description, target object, extraction path, and judgment conditions; the classification of event subjects can fully cover the system OODA loop process; Organize the total number of system events based on system functions and task processes; classify the events according to the extraction path in the event definition and the subject, forming a corresponding relationship between system / device, event, message, and field; Step 2: Re-configure the elements: Configure different review elements according to each task to restore the task process; Step 3: Replay event extraction: Based on the configuration of the review elements, the system / device events to be extracted are determined, automatically associated with specific message data, and the data corresponding to the events is extracted from the message fields. Step 4: Review the data and see: After completing the review data preparation, perform the review data display to view the system's working status and performance indicators in real time; The data processing flow during the event extraction process in step 3 is as follows: a. Data parsing: Based on the replay element configuration, obtain all the messages corresponding to the elements. For each message, create a corresponding message data table in the database based on the message name and field. Parse the message corresponding to the replay element configuration from the message data file and store it in the corresponding message data table. Parse the target true value data from the target true value file, transform it into data that can be used for error analysis through coordinate system conversion, and store it in the true value data table. b. Batch number comparison: Obtain the comparison relationship between the fusion batch number and the sensor batch number from the batch number comparison relationship and the message data table corresponding to the message. According to one or more target objects input during event extraction, establish a comparison relationship between the target object and the fusion batch number. Write the established comparison relationship between the target object, the fusion batch number and the sensor batch number into the batch number comparison table. c. Event extraction: Based on the correspondence between system / device, event, message, and field, the event data that meets the conditions is retrieved from the corresponding message data table and stored in the event data table; d. Track extraction: According to the configuration of the replay elements, obtain the message and field corresponding to the target motion track, query the data of the corresponding field from the message data table, and store it in the track data table; e. Error analysis: Obtain target track data from the track data table, obtain target true value data from the true value data table, obtain the linear error, systematic error, random error, and mean square error of the target data through calculation, and store the error calculation results in the error data table.

2. The system OODA loop rapid review method based on custom events according to claim 1 is characterized in that: The OODA loop process in step 1 includes: sensor detection, track establishment, track cancellation, and track loss; the command and control system fuses multiple sensor target tracks to generate a fused target track; makes threat assessments on the target; makes attack / defense decisions and generates attack / defense plans; the command and control system issues attack / defense plans or target instructions to the weapon; the weapon solves, tracks the target, and launches ammunition to attack / defend the target.

3. The system OODA loop rapid review method based on custom events according to claim 1 is characterized in that: The event attribute set in step 1 specifically includes: Event subject: the system / device that responds to the target, and all system devices related to the target; Time of occurrence: the time when the event occurred; Event description: used to describe the event itself; Target object: used to mark the target object corresponding to the event, and the target object is identified by the batch number; Extraction path: used to specify how to extract the event attribute information, and define the message, field, and specific value in the field corresponding to the event; Judgment condition: defines the judgment condition for whether an event occurs.

4. The system OODA loop rapid review method based on custom events according to claim 3 is characterized in that: The judgment conditions specifically include: For one-time messages: each time this message is received, it is considered that this event has occurred; For periodic messages, an event is determined to occur when a field value changes. If a certain message is received continuously, it is determined that an event occurs; If a certain message is not received continuously, it is determined that an event occurs.

5. The system OODA loop rapid review method based on custom events according to claim 1 is characterized in that: The review elements in step 2 include: If you are configuring the working status, select the status item and the corresponding message and field; If the configuration is track data, select the data items of the target motion track, as well as the corresponding messages and fields; If you are configuring an event, select the corresponding event name and event attributes.

6. The system OODA loop rapid review method based on custom events according to claim 5 is characterized in that: The process of reconfiguring the elements in step 2 includes: Add a review plan; Select the subsystem / equipment under the review plan; Get all status items under each subsystem / device, and select the status items of interest under each subsystem / device; Get all track data items under each subsystem / device, and select the data items of interest under each subsystem / device; Obtain all key events for each subsystem / device and select the events of interest for each subsystem / device.

7. The system OODA loop rapid review method based on custom events according to claim 1 is characterized in that: The method for extracting events in step 3 includes: Based on the configuration of the review elements, determine which systems / devices and which events to extract, and configure the packets to be recorded. Before the task begins, connect the packet recording device to the switch mirror port or a specific port. After the task is completed, use the packet parsing program to parse the packets to be analyzed. During event extraction, data for a specific time period is extracted by inputting a time range; target objects in the task process are associated through batch numbers; target objects are determined by fusing target batch numbers; during event extraction, extraction is performed by inputting the fused target batch numbers corresponding to one or more target objects.

8. The system OODA loop rapid review method based on custom events according to claim 7 is characterized in that: The method for setting the batch number is specifically as follows: Set a target batch number for each sensor. The command and control system sets its own target batch number range for the fusion target. The command and control system fuses the target tracks of multiple sensors to generate a fusion target. The command and control system automatically maintains the correspondence between the fusion target batch number and the original target batch number of the sensor, establishes a batch number comparison table, and sends the batch number comparison relationship message online. The specific structure of the batch number comparison table is as follows: The batch number comparison table records multiple target objects, each target object records multiple fusion batch numbers, each fusion batch number records multiple groups of target data, and each group of target data records multiple target batch numbers.

9. The system OODA loop rapid review method based on custom events according to claim 1 is characterized in that: The data display in step 4 provides multiple data display formats: Basic display formats include: event graphs, with time on the horizontal axis and system / device on the vertical axis; various target data graphs, including distance-time, azimuth-time, and elevation-time; and various error graphs, including distance difference-time, azimuth difference-time, and elevation difference-time. Target data graph, used to simultaneously display the data of multiple targets; for target data graphs in various forms, a subgraph matrix is ​​used for display; Events related to the target are displayed on the target data graph based on the time of occurrence.

Images