An emergency inversion system based on a historical case library

Abstract

The application discloses an emergency inversion system based on a historical case library, comprising: a historical case library and a function module; the historical case library is used for storing historical cases, the historical cases are based on the early warning response or the emergency response that has occurred, and the historical cases are used for creating the cases of the whole process of emergency management, realizing the whole process recording from the monitoring and early warning to the starting of the early warning or the emergency response, to the power grid fault, disaster damage and the input of various emergency resources; the function module comprises: an event interceptor module, an event recording module, an event processing module, a data synchronization module, a data slicing module and a case display module; and the application provides the support for the key scene of the historical inversion and the historical data review analysis of the emergency command.

Description

Technical Field

[0001] This invention relates to the field of emergency command technology, and specifically to an emergency inversion system based on a historical case database. Background Technology

[0002] To ensure the stable and safe power supply capacity of the power grid and reduce the impact of emergencies and the losses to the power grid, it is necessary to conduct retrospective analysis of historical emergency cases to support the post-event analysis of emergency operations. This is of great significance for effectively preventing and responding to various emergencies, controlling and reducing accident and disaster losses, ensuring social stability and the safety of people's lives and property, and maintaining the company's normal production and operation order.

[0003] Currently, the display of emergency events throughout the entire emergency management process is not seamless, and the massive amount of data makes it impossible to comprehensively store all historical emergency event data. The inversion based on emergency event handling lacks the ability to switch between macro and micro scenarios at any time, is inconvenient to operate, and can only display the results of emergency event handling, lacking dynamic data display based on event reproduction. Summary of the Invention

[0004] Purpose of the invention: The purpose of this invention is to provide an emergency inversion system based on a historical case database, which standardizes the way events are recorded in the entire process of emergency management (including monitoring, early warning, emergency response, emergency handling, and emergency assessment), forms a unified historical case database, and dynamically plays the historical events recorded in the historical case database on the power grid GIS map based on a timeline, so as to solve the problems existing in the background technology.

[0005] Technical Solution: The present invention discloses an emergency inversion system based on a historical case library, comprising: a historical case library and functional modules; the historical case library stores historical cases, which are cases of the entire emergency management process based on existing early warning responses or emergency responses, realizing the full-process recording from the start of monitoring and early warning to the activation of early warning or emergency response, to the occurrence of power grid failures, disasters, and the deployment of various emergency resources; the functional modules consist of: an event interceptor module, an event recording module, an event processing module, a data synchronization module, a data slicing module, and a case display module; the event processing module includes: a historical case creation module, a timeline generation module, and an indicator statistics module; the case display module includes a situation playback module and a micro-slicing module.

[0006] Furthermore, the specific presentation formats of historical cases include: visualizing the changes in data on the input of the four elements of power grid failure, teams, vehicles, equipment, and material resources, as well as emergency response tasks, using bar charts and line graphs; displaying the changes in temperature, wind speed, and rainfall and their impact range using GIS layers; and displaying the status of power grid equipment, the location of teams and vehicles, and the feedback on task execution at a specific moment using GIS layers.

[0007] Furthermore, the event interceptor module is used to obtain SQL scripts for CRUD operations on specified related tables and send them to the message queue; the event logging module is responsible for real-time monitoring of the message queue, processing and recording the SQL scripts in the message queue; the event processing module is used to collect key indicator data for display from related data tables according to the event processing strategy, save the real-time status data of all layers, and record the event time points, displaying them on the playback timeline.

[0008] Furthermore, the case study module is used to sequentially play all map layers and key statistical data based on the time points recorded on the timeline; the playback supports shortcuts, dragging, and pausing.

[0009] Furthermore, the event interceptor module is used to monitor, warn, and respond to database table operations throughout the entire emergency management process in the production environment: it intercepts SQL statements for insert, update, and delete operations and sends the obtained SQL scripts to the message queue; the event logging module is used to listen to the message queue in real time, retrieve the SQL scripts from the message queue, execute the SQL scripts in the historical case database, and assign values ​​to three additional fields: operate_date, operate_type, and chain_date.

[0010] Further data processing includes: data synchronization, timeline generation, indicator statistics, and data slicing.

[0011] Furthermore, the data synchronization module is used to synchronize relevant meteorological data from the business platform to the historical case library based on the time range of the case; and to synchronize detailed data viewed from a low angle on the map from the production library to the historical case library based on the event ID and the time range of the case. The timeline generation module is used to generate the timeline of the entire case based on the case's time range, and to generate playback time points on the timeline according to the minimum playback interval minTime. At the same time, based on the SQL script recorded by the event logging module, the time points of operation_type 0-insert and 2-delete are also recorded on the timeline. After the timeline is generated, the metrics are statistically analyzed based on each time point on the timeline.

[0012] Furthermore, the data slicing module is used to retrieve relevant data from the historical case library for all lines and surfaces that need to be displayed from the high-view map based on time points with an interval of minTime on the time axis, generate sliced ​​images and store them in the OSS image library, thereby improving the smoothness of the inversion playback by pre-generating layer images for each time point.

[0013] Furthermore, the situation playback module is used to sequentially play the changes of each layer on the map, as well as the changes of event history, announcement messages, and various statistical indicators in the floating window, at each time point on the timeline from a high-angle view of the map.

[0014] Furthermore, micro-slicing is used to view detailed data at any point in time by drilling down the map layer or clicking the details button when playback is paused, thus restoring the instantaneous state of various events at that historical moment.

[0015] Beneficial effects: Compared with the prior art, the present invention has the following significant advantages: The present invention forms a unified historical case library by standardizing the way of recording events throughout the entire process of emergency management. This is conducive to the inheritance, solidification and reuse of effective typical emergency event handling experience. At the same time, it also provides tools for playing back the situation of historical cases and playing back micro-slices, which can realistically restore the handling measures and on-site situation of the entire emergency event process. This provides key scenario support for the historical reversal of emergency command and the review and analysis of historical data, and provides optimization solutions for subsequent emergency event handling. Attached Figure Description

[0016] Figure 1 This is a system functional diagram of the present invention; Figure 2 This is a schematic diagram of the emergency inversion system of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0018] like Figure 1As shown, this embodiment of the invention provides an emergency inversion system based on a historical case library, including: a historical case library and functional modules; the historical case library stores historical cases, which are cases created based on existing early warning responses or emergency responses, covering the entire emergency management process, from the start of monitoring and early warning to the activation of early warning or emergency response, to the occurrence of power grid failures, disasters, and the deployment of various emergency resources; the functional modules include: an event interceptor module, an event recording module, an event processing module, a data synchronization module, a data slicing module, and a case display module; the event processing module includes: a historical case creation module, a timeline generation module, and an indicator statistics module; the case display module includes a situational playback module and a micro-slicing module. Details are as follows: S1 defines a historical case library. Historical case studies create a complete record of the entire emergency management process, based on past early warning or emergency responses. This record covers the entire process from monitoring and early warning to the activation of the early warning or emergency response, the occurrence of power grid failures and damage, and the deployment of various emergency resources. The content of historical case studies encompasses monitoring, early warning, emergency response, emergency handling, resource allocation, and power grid restoration. Specific display formats include: visualizing trends in power grid failures, resource input (teams, vehicles, equipment, and materials), and emergency response tasks using bar charts and line graphs; displaying meteorological changes and their impact range using GIS layers; and displaying information such as power grid equipment status, team and vehicle locations, and task execution feedback at a specific moment using GIS layers.

[0019] The historical case library stores individual historical cases. Its table structure is based on the production database, with additional fields `operate_date` (operation time), `operate_type` (operation type: insert, update, delete), and `chain_date` (chain operation time) added to the relevant detail tables involved in the entire emergency management process. The historical case library supports both a situational awareness playback mode and a micro-slice mode for the entire emergency management process: the situational awareness playback mode presents the event response process in animated form, comprehensively, clearly, and efficiently highlighting changes in key data during emergency response; the micro-slice mode allows for frame-by-frame analysis of the response process, displaying various data in visual and list formats, providing detailed information on the status of power grid equipment, power grid faults, and resource elements.

[0020] S11 Daily Routine - Data Recording Throughout the entire process of emergency management in the production environment, database table operations generated by monitoring, early warning, and emergency response services are intercepted by an event interceptor module. The SQL statements for insert, update, and delete operations are then intercepted and sent to a message queue.

[0021] The event logging module listens to the message queue in real time. After retrieving the SQL script from the message queue, it executes the SQL script on the historical case database and assigns values ​​to three additional fields: `operate_date` (operation time: current time), `operate_type` (operation type: 0-insert, 1-update, 2-delete), and `chain_date` (chain operation time). The rule for assigning the `chain_date` field is as follows: before the SQL execution is inserted into the database, the historical case database is queried for records with the same ID and `operate_type`. If the record exists in the database, the `chain_date` of the duplicate record is updated to the current time before the SQL insertion operation is executed. If the record does not exist in the database, the SQL insertion operation is executed directly, and the `chain_date` field of the inserted record is set to null, indicating that it is the latest record.

[0022] S12 Inverse State - Historical Case Creation After an emergency warning event concludes, historical cases can be created. When creating a historical case, you can filter eligible historical warning or emergency response events from the past month based on the issuing unit and hazard category, set associated meteorological warning information, and determine the entire time range of the case and the minimum playback interval (minTime) (default is 5 minutes). After successful creation, the case can be published, simultaneously triggering the data synchronization module to synchronize relevant data within the case's time range and the event processing module to process the relevant data.

[0023] S13 Inversion-Data Processing When publishing case studies, relevant data needs to be processed. Data processing includes four aspects: data synchronization, timeline generation, indicator statistics, and data slicing.

[0024] The data synchronization module synchronizes relevant meteorological data from the business platform to the historical case database based on the time range of the case; and synchronizes detailed data viewed from a low angle on the map to the historical case database based on the event ID and the time range of the case.

[0025] The event handling module generates a timeline for the entire case based on the case's time range, and generates playback time points on the timeline according to the minimum playback interval minTime (large dots can be used to mark these points on the timeline during display). At the same time, based on the SQL script recorded by the event logging module, the time points of operation_type 0-insert and 2-delete are also recorded on the timeline (small dots can be used to mark these points on the timeline during display).

[0026] After the timeline is generated, metric statistics can be performed based on each time point on the timeline. First, for each time point on the timeline, find the record with the most recent chain_date value from the corresponding table in the historical case database as the instantaneous value of the metric at that time point. Then, count the changes in all records with operation_type of 1-update between the two time points as the change value of the metric within that time period. Finally, store the instantaneous value and change value of the metric in the historical case database according to the time points on the timeline.

[0027] The data slicing module retrieves relevant data from the historical case library for all line and surface layers (such as weather layers and trajectory layers) that need to be displayed from a high-angle view of the map, based on time points at intervals of minTime on the timeline, and generates sliced ​​images which are then stored in the OSS image library. Pre-generating layer images for each time point improves the smoothness of the inversion playback.

[0028] S14 Inversion State - Situation Playback The situational playback feature displays changes to various map layers sequentially on the page at each time point along the timeline, along with event histories, announcements, and statistical indicators displayed in floating windows, all from a high-angle view of the map. Playback speed is customizable, with a default 5-second display time for each time point. The timeline can be freely dragged, allowing direct jumps to any time point. Layers support custom configuration for overlaying various layers (e.g., weather, trajectory, power grid, equipment, resource layers). For line and polygon layers, the system retrieves the relevant layer images from the OSS image library based on the current time point. For point-based layers (e.g., equipment and resource layers), the system retrieves detailed information including coordinates from the historical case library based on the current time point and aggregates or displays the data directly based on map layers. For statistical indicators, the system retrieves the instantaneous and changing values ​​from the historical case library based on the current time point and displays them using visualizations such as bar charts and line graphs.

[0029] S15 Inverse State - Microscopic Slice Micro-tiles allow you to view detailed data for the current time point or any point in time by drilling down the map layer or clicking the details button while playback is paused. This reconstructs the instantaneous state of various events at that historical moment. Clicking the marker icon on the map layer enters a low-view view, displaying content similar to the low-view view in the production environment. Micro-tile mode also allows for various display and playback mode configurations, and playback will start with the latest configuration in the current state of play.

[0030] S2 defines functional modules The functional modules consist of an event interceptor module, an event logging module, an event handling module, a data synchronization module, a data slicing module, and a case demonstration module.

[0031] The event interceptor module is a MyBatis interceptor that can retrieve SQL scripts for CRUD operations on specified tables and send them to a message queue.

[0032] The event logging module is responsible for real-time monitoring of the message queue, processing the SQL scripts in the message queue for database entry and recording.

[0033] The event handling module, based on the event handling strategy, collects key indicator data for display from relevant data tables, saves real-time status data of all layers, and records event time points for display on the playback timeline.

[0034] The data synchronization module is responsible for synchronizing all relevant data from the production database and the business middle platform (which stores unstructured meteorological data) for the entire time period of the relevant event, including meteorological data and detailed data viewed from a low angle on the map, to the historical case database.

[0035] The data tiling module retrieves data from the historical case library based on all layers that need to be displayed from the high-angle view of the map, generates tiling images, stores them in the image library, and records the tiling time points for display on the playback timeline.

[0036] The case study module sequentially plays all map layers and key statistical indicators based on the time points recorded on the timeline. Playback supports shortcuts, dragging, and pausing. When paused, users can click on relevant data points on a layer to view detailed data.

[0037] like Figure 2 As shown in the figure, an emergency response inversion method based on a historical case database according to an embodiment of the present invention includes the following steps: (1) SQL scripts that generate changes in database table data (such as insert, delete, update operations) for services such as production environment monitoring, early warning, emergency response, resources, and power grid are intercepted and obtained through event interceptors, and the obtained SQL scripts are sent to the message queue; (2) The event logging module listens to the message queue in real time, retrieves the SQL script from the message queue, inserts the SQL script into the historical case database, and assigns values ​​to the fields operate_date, operate_type and chain_date.

[0038] (3) After the emergency warning event ends, create historical cases through the visualization page. After successful creation, publish the case and complete steps (4) to (7); (4) The data synchronization module synchronizes relevant meteorological data from the business middle platform to the historical case database according to the time range of the case; and synchronizes detailed data viewed from a low angle on the map from the production database to the historical case database according to the event ID and the time range of the case. (5) After data synchronization is completed, the event processing module generates the timeline of the entire case according to the time range of the case, and generates the playback time point on the timeline according to the minimum playback interval time minTime. At the same time, according to the SQL script recorded by the event recording module, the time points of operation_type 0-insert and 2-delete are also recorded on the timeline.

[0039] (6) After the timeline is generated, the event handling module performs statistical analysis on the metrics at each time point on the timeline: (a) For each time point on the timeline, find the record whose chain_date value is closest to that time point from the corresponding table in the historical case database and use it as the instantaneous value of the indicator at that time point; (b) Statistically analyze the changes in all records with operation_type of 1-update between two time points as the change value of the indicator within that time period; (c) Store the instantaneous values ​​and changes of the indicators into the historical case library according to the time points on the time axis.

[0040] (7) After the timeline is generated, the data slicing module retrieves relevant data from the historical case library for all the lines and surfaces that need to be displayed from the high-angle view of the map based on the time points with an interval of minTime on the timeline, generates slices and stores them in the OSS image library.

[0041] (8) Successfully published historical cases can be played back. When a historical case is selected for playback, the changes of each layer on the map and the event history, announcement messages and various statistical indicators in the floating window are played sequentially at each time point on the timeline. (9) When playback is paused, you can view detailed data for the current time point by drilling down the map layer or clicking the details button. You can also drag the timeline to view detailed data for any time point.

Claims

1. An emergency response inversion system based on a historical case database, characterized in that, include: The system includes a historical case library and functional modules. The historical case library stores a series of historical cases, which are based on actual early warning or emergency responses. It creates cases documenting the entire emergency management process, from monitoring and early warning to the activation of the early warning or emergency response, the occurrence of power grid failures and disasters, and the deployment of various emergency resources. The functional modules include: an event interceptor module, an event logging module, an event processing module, a data synchronization module, a data slicing module, and a case display module. The event interceptor module is a MyBatis interceptor used to intercept database table operations generated during monitoring, early warning, and emergency response throughout the emergency management process, including SQL operations such as insert, update, and delete. The script is retrieved and the retrieved SQL script is sent to a message queue. The event logging module is used to monitor the message queue in real time. After retrieving the SQL script from the message queue, the SQL script is executed in the historical case database, and values ​​are assigned to the three fields: operate_date, operate_type, and chain_date. The assignment rule for the chain_date field is as follows: before the SQL execution is inserted into the database, records with the same ID and the same operate_type in the historical case database are queried. If duplicate records exist, the chain_date of the duplicate records is updated to the current time before the SQL insertion operation is executed. If no duplicate records exist, then... The SQL insertion operation is executed directly, and the chain_date field of the inserted record is set to empty to indicate that the record is the latest record. The event processing module includes a historical case creation module, a timeline generation module, and an indicator statistics module. The historical case creation module is used to filter early warning responses or emergency response events that meet the conditions according to the issuing unit and the hazard category, and set the associated meteorological early warning information to determine the time range and minimum playback interval of the entire case process. The timeline generation module is used to generate the timeline of the entire case according to the time range of the case, and generate playback time points on the timeline according to the minimum playback interval. At the same time, according to the SQL script recorded by the event recording module, the operator_type is set to insert. The time points of t and delete are also recorded on the timeline; the indicator statistics module is used to find the record with the chain_date value closest to that time point from the historical case library for each time point on the timeline as the instantaneous value of the indicator at that time point, and to count the changes of all records with operation_type of update between two time points as the change value of the indicator within that time period. The instantaneous value and change value of the indicator are stored in the historical case library according to the time points on the timeline; the data synchronization module is used to synchronize meteorological data from the business middle platform to the historical case library according to the time range of the case, and to synchronize the detailed data of the low-view map view from the production library to the historical case library according to the event ID and the time range of the case.The data slicing module retrieves relevant data from the historical case library for all line and polygon layers to be displayed from the map's high-view perspective, based on the minimum playback interval on the timeline, and generates sliced ​​images which are then stored in the OSS image library. The case display module includes a situational playback module and a micro-slicing module. The situational playback module, from the map's high-view perspective, sequentially plays the changes in each map layer on the page at each time point on the timeline, along with the event history, announcement message changes, and statistical indicator changes in the floating window. The micro-slicing module, when playback is paused, allows users to drill down into map layers, click the details button to view the current time point, or drag the timeline to view detailed data for any time point, reconstructing the instantaneous state of various events at historical moments.

2. The emergency inversion system based on a historical case database according to claim 1, characterized in that, The specific presentation formats of historical cases include: visualizing the changes in the input of the four elements of power grid failure, teams, vehicles, equipment, and material resources, as well as emergency response task data, using bar charts and line graphs; displaying the changes in temperature, wind speed, and rainfall and their impact range using GIS layers; and displaying the status of power grid equipment, the location of teams and vehicles, and the task execution feedback at a certain moment using GIS layers.

3. The emergency response inversion system based on a historical case database according to claim 1, characterized in that, The situation playback module is specifically used to: play the changes of each layer on the map, as well as the changes of event history, announcement messages, and various statistical indicators in the floating window, sequentially at each time point on the timeline from a high-angle view of the map; the playback supports shortcut keys, dragging, and pausing.

Images