Emergency response full-period management method, system and device and storage medium
By automatically determining the event level through machine learning and geofencing technology, combined with real-time resource allocation and security encryption, the problem of lagging manual judgment and resource waste in existing emergency response systems has been solved, achieving efficient and secure emergency response management.
Patent Information
- Application Number
- CN202511474814.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-15
- Publication Date
- 2026-01-09
AI Technical Summary
Existing emergency response systems lack automated event level determination mechanisms, have inaccurate resource allocation, rely on manual analysis for decision-making, face difficulties in system expansion, have insufficient data security, and struggle to meet real-time and security compliance requirements.
It uses machine learning algorithms to automatically determine event levels, combines geofencing technology and path planning algorithms for resource allocation, monitors event indicators in real time, uses token verification and AES encryption to protect operation logs, builds a multi-dimensional resource efficiency assessment and report generation mechanism, and supports cross-departmental collaboration processes.
It achieves second-level event-level judgment, improves resource scheduling efficiency by 30%, ensures data security and system scalability, supports high-concurrency access and cross-departmental collaborative operations, and improves the timeliness and accuracy of emergency response.
Smart Images
Figure CN121300943A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of emergency response technology, and in particular relates to a method, system, device and storage medium for full-cycle emergency response management. Background Technology
[0002] An emergency response mechanism refers to a systematic and standardized set of response procedures and measures pre-established by an organization or institution to deal with emergencies (such as natural disasters, accidents, public health emergencies, and social security incidents). Its core objective is to minimize the losses caused by the event, ensure the safety of personnel, and restore order and normal operation as quickly as possible.
[0003] In current technology, many organizations still rely primarily on human experience to make initial assessments of the severity of emergencies. Emergency managers typically evaluate the severity of an event based on information such as the event type, scope of impact, development trend, historical data, and on-site feedback, combined with the grading standards in the emergency plan (e.g., four levels of response: general, significant, major, and extremely major), and initiate the corresponding level of emergency response accordingly. Resource allocation (such as dispatching rescue teams, transporting supplies, providing medical support, and ensuring communication) is also mostly carried out by the command center issuing instructions via telephone, conferences, or information systems, relying on manual coordination and dispatch.
[0004] The existing technology has the following technical problems: 1. In existing technologies, the determination of emergency response levels is mostly based on human experience, lacking an automatic correlation mechanism between event type and response level, resulting in delayed response decisions and difficulty in adapting to the dynamic changes of emergencies.
[0005] 2. Traditional resource pool management technology cannot match the dynamic needs of the area affected by the event in real time, and lacks deep integration of geofencing technology with resource allocation, resulting in resource waste or local resource shortages.
[0006] 3. Existing large-screen visualization systems mainly rely on static displays and lack real-time early warning threshold linkage mechanisms. Decision-making depends on manual analysis, resulting in poor response timeliness.
[0007] 4. The existing review system only records basic operation logs and lacks multi-dimensional resource efficiency assessment and automated report generation capabilities, making it difficult to support subsequent optimization decisions.
[0008] 5. Cross-departmental and cross-platform data integration relies on customized interfaces and lacks a unified process engine and plug-in architecture, making system expansion difficult and hindering the rapid integration of new functions or third-party services.
[0009] 6. Existing systems are prone to query delays under high concurrency access, especially in scenarios such as resource status tracking and site failure rate statistics, where traditional database architectures are difficult to meet real-time requirements.
[0010] 7. The transmission and storage of sensitive data lack strong encryption protection, posing a risk of leakage and failing to meet security and compliance requirements in emergency scenarios. Summary of the Invention
[0011] This invention provides a method, system, device, and storage medium for full-cycle emergency response management, aiming to solve the technical problems in the prior art, such as low efficiency due to reliance on manual intervention for response level adjustment, insufficient accuracy of resource allocation, and weak intelligent decision support capabilities.
[0012] The technical solution of this invention to solve the above-mentioned technical problems is as follows: A method for full-cycle emergency response management, comprising: Acquire event information about the emergency, input the event information into the response judgment model for processing, and obtain the initial response level and event type; The system obtains the dispatch request generated by the command personnel on the command terminal based on the initial response level and the event type, matches the dispatch request with the emergency resource data in the resource pool, obtains the dispatch instruction, and sends it to the mobile APP of the execution personnel to instruct the execution personnel to handle the event. Real-time monitoring of event response indicators, and when the event response indicators reach a preset alarm threshold, generating alarm information and pushing it to the command terminal, using the command terminal to respond to the alarm information to generate an upgrade dispatch instruction and send it to the mobile APP of the execution personnel; After the event is processed, a full lifecycle operation log is generated and encrypted.
[0013] Furthermore, the mobile app that receives the dispatch instructions and sends them to the personnel responsible for execution is specifically as follows: Obtain the command personnel's dispatch request regarding the initial response level and the event type; Based on the scheduling request, the microservice architecture automatically queries the emergency resource data in the resource pool and matches it with the emergency resource data to obtain the schedulable resources; Based on GIS map services, geofences are constructed with the location of the emergency as the center and the influence radius preset according to the event type as the range. Spatial query engines are then used to filter out schedulable resources located within the geofences. The resource allocation scheme is obtained by calculating the schedulable resource allocation scheme using the path planning method. The resource allocation plan is converted into scheduling instructions and sent to the mobile APP of the executors.
[0014] Furthermore, the aforementioned event response indicators include: service outage rate and resource shortage; the specific real-time monitoring of event response indicators are as follows: The basic indicators of the affected area are monitored, and the event response indicators are obtained by analyzing the basic indicators. The basic indicators include: site failure rate, resource distribution heat map, and response progress.
[0015] Furthermore, the specific details of the entire lifecycle operation log for the aforementioned generated event are as follows: Record the operational actions throughout the entire process of an emergency, from its occurrence to its resolution, to obtain the original operation log; All the original operation logs are collected and preprocessed to obtain the full lifecycle operation log of the event; The token verification is used to verify the legitimacy of the received event lifecycle operation logs, and the symmetric encryption method is used to encrypt the event lifecycle operation logs after the legitimacy verification is passed. Logstash is used to write encrypted event lifecycle operation logs to the Elasticsearch cluster and create an index.
[0016] Furthermore, the above also includes: analyzing the entire lifecycle operation log of the event to obtain an optimization suggestion report, generating a three-dimensional backtracking analysis result based on the event backtracking initiated by the user, and obtaining event experience data based on the optimization suggestion report and the three-dimensional backtracking analysis result, specifically: Obtain the full lifecycle operation log of the event, and calculate the core performance indicators based on the full lifecycle operation log; wherein, the core performance indicators include: resource utilization rate, average response time, task completion rate and resource idle rate; An optimization suggestion report was obtained by analyzing the core performance indicators. Get the sudden event that the user initiated the replay, call the Cesium engine to build a 3D scene of the sudden event, control the replay progress with the timeline, and restore the development process of the sudden event by minute or event node; Obtain the key markers that the user marks on the nodes during the backtracking process, and perform in-depth analysis based on the key markers to obtain the three-dimensional backtracking analysis results; The optimization suggestion report and the three-dimensional backtracking analysis results are integrated to obtain event experience data.
[0017] Furthermore, the above also includes: retrieving and structuredly outputting the entire lifecycle operation logs of the event based on the user's review needs, specifically as follows: Obtain the user's event retrieval statement, and retrieve the target event ID based on the event retrieval statement; Based on the target event ID, the corresponding event lifecycle operation logs are integrated to obtain multi-source event data, and the corresponding report template is matched according to the event type in the multi-source event data; wherein, the report template is pre-stored in the template library; The multi-source event data is populated into the report template using the template engine to generate a preliminary structured report; The user's customized requirements are obtained, and the preliminary structured report is rendered to obtain the debriefing report.
[0018] Furthermore, the above also includes: acquiring disaster early warning data from external systems and generating cross-departmental collaborative workflow tasks based on the disaster early warning data to enable collaborative operations among departments, specifically: Create an interface configuration task for external systems and configure the interface information of external systems through a RESTful API; the external systems include the meteorological bureau system and the seismic network system. It receives disaster early warning data transmitted from the external system in real time, and transforms the structure of the disaster early warning data into an internal data structure based on data mapping rules; Based on the system's built-in visual process designer, cross-departmental collaborative process tasks are generated from the transformed disaster early warning data, and these tasks are then distributed to the corresponding personnel.
[0019] Secondly, to solve the above-mentioned technical problems, the present invention also provides an emergency response full-cycle management system, comprising: The event type determination module is used to obtain event information of sudden events, input the event information into the response determination model for processing, and obtain the initial response level and event type. The dispatch strategy module is used to obtain the dispatch request generated by the commander on the command terminal based on the initial response level and the event type, match the dispatch request with the emergency resource data in the resource pool, obtain the dispatch instruction and send it to the mobile APP of the executor to instruct the executor to handle the event; The real-time monitoring module is used to monitor event response indicators in real time, and when the event response indicators reach a preset alarm threshold, generate alarm information and push it to the command terminal. The command terminal responds to the alarm information to generate an upgrade dispatch instruction and sends it to the mobile APP of the execution personnel. The operation log module is used to generate a full lifecycle operation log of the event after the event is processed, and to encrypt the full lifecycle operation log of the event.
[0020] Thirdly, in order to solve the above-mentioned technical problems, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the emergency response full-cycle management method of the present application.
[0021] Fourthly, in order to solve the above-mentioned technical problems, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the emergency response full-cycle management method of the present application.
[0022] Compared with the prior art, the present invention has the following advantages: 1. This invention integrates a rule engine and machine learning algorithms to automatically analyze event information and quickly output the initial response level and event type when an emergency occurs, avoiding the subjectivity and delays of manual judgment. Command personnel can make fine adjustments based on the system's recommendations, achieving "human-machine collaboration and second-level level determination." This mechanism reduces the response initiation time from tens of minutes in the traditional model to minutes or even seconds, significantly improving the timeliness and accuracy of emergency response.
[0023] 2. This invention deeply integrates geofencing technology, spatial query engines, and path planning algorithms. The system can automatically identify available resources within the affected area and generate the optimal allocation plan based on real-time traffic conditions, avoiding "remote dispatching" or "resource idleness." Dispatch instructions are delivered directly to frontline personnel via a mobile app. This mechanism reduces resource arrival time by an average of over 30%, significantly improving on-site handling efficiency.
[0024] 3. This invention achieves dynamic awareness of the emergency situation by comprehensively analyzing key indicators such as service outage rate and resource shortage in real time, combined with basic data such as site failure rate, resource distribution heatmap, and response progress. When the indicators reach preset thresholds, the system automatically pushes alarms to the command terminal and prompts process upgrade suggestions, supporting commanders to make rapid upgrade decisions.
[0025] 4. This invention employs a triple mechanism of token verification, AES encryption, and digital signature to protect the integrity and security of operation logs throughout the entire event lifecycle. All operations are recorded and encrypted and stored in an Elasticsearch cluster, supporting fast retrieval and replay by event ID.
[0026] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description
[0027] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0028] Figure 1 A flowchart illustrating a full-cycle emergency response management method according to an embodiment of the present invention is shown. Figure 2 A schematic diagram of the structure of an emergency response full-cycle management system according to an embodiment of the present invention is shown; Figure 3 A schematic diagram of an electronic device structure according to an embodiment of the present invention is shown. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0030] Figure 1 A flowchart illustrating a full-cycle emergency response management method according to an embodiment of the present invention is shown, such as... Figure 1 As shown in the figure, an emergency response full-cycle management method according to an embodiment of the present invention includes: Acquire event information about the emergency, input the event information into the response judgment model for processing, and obtain the initial response level and event type; The system obtains the dispatch request generated by the command personnel on the command terminal based on the initial response level and the event type, matches the dispatch request with the emergency resource data in the resource pool, obtains the dispatch instruction, and sends it to the mobile APP of the execution personnel to instruct the execution personnel to handle the event. Real-time monitoring of event response indicators, and when the event response indicators reach a preset alarm threshold, generating alarm information and pushing it to the command terminal, using the command terminal to respond to the alarm information to generate an upgrade dispatch instruction and send it to the mobile APP of the execution personnel; In this embodiment, the Flink stream processing engine is used to calculate real-time metrics and trigger alert threshold linkage.
[0031] After the event is processed, a full lifecycle operation log is generated and encrypted.
[0032] In this embodiment, emergency resource data includes resources such as vehicles, generators, and satellite phones. During the incident handling process, a real-time monitoring dashboard is built based on ECharts / Grafana to dynamically display key indicators such as site failure rate in the affected area, resource distribution heatmap, and response progress.
[0033] Optionally, the mobile app that receives the dispatch instructions and sends them to the personnel responsible for execution will specifically do the following: Obtain the command personnel's dispatch request regarding the initial response level and the event type; Based on the scheduling request, the microservice architecture automatically queries the emergency resource data in the resource pool and matches it with the emergency resource data to obtain the schedulable resources; Based on GIS map services, geofences are constructed with the location of the emergency as the center and the influence radius preset according to the event type as the range. Spatial query engines are then used to filter out schedulable resources located within the geofences. The resource allocation scheme is obtained by calculating the schedulable resource allocation scheme using the path planning method. The resource allocation plan is converted into scheduling instructions and sent to the mobile APP of the executors.
[0034] In this embodiment, on the GIS map service interface, the system can automatically identify or the command personnel can select the area affected by the event and quickly match the site and resources within the fence.
[0035] In this embodiment, GeoHash encoding is used to quickly retrieve station addresses within the fence, and R-tree indexing is combined to improve spatial query efficiency.
[0036] Optionally, the event response metrics include: service outage rate and resource shortage; the specific real-time monitoring of event response metrics is as follows: The basic indicators of the affected area are monitored, and the event response indicators are obtained by analyzing the basic indicators. The basic indicators include: site failure rate, resource distribution heat map, and response progress.
[0037] In this embodiment, the CEP engine is used to monitor the indicator stream in real time and trigger multi-condition combination alarms.
[0038] In this embodiment, after the alarm information is pushed to the command terminal, the command personnel can call the pre-set standardized emergency procedure plan library in the system according to the event type to obtain detailed response strategies and operation guidelines to assist in decision-making.
[0039] Optionally, generating a full lifecycle operation log for the event specifically involves: Record the operational actions throughout the entire process of an emergency, from its occurrence to its resolution, to obtain the original operation log; All the original operation logs are collected and preprocessed to obtain the full lifecycle operation log of the event; The token verification is used to verify the legitimacy of the received event lifecycle operation logs, and the symmetric encryption method is used to encrypt the event lifecycle operation logs after the legitimacy verification is passed. Logstash is used to write encrypted event lifecycle operation logs to the Elasticsearch cluster and create an index.
[0040] In this embodiment, the preprocessing of the original operation logs includes: cleaning, parsing, tagging, and unifying the timestamp. An index is created based on fields such as event ID, time range, and operation type, allowing relevant personnel to retrieve data by time.
[0041] In this embodiment, transmission security is ensured by enabling TLS 1.3 encrypted communication across the entire link to prevent man-in-the-middle attacks. Storage security is achieved by storing sensitive data using AES-256 encryption, with keys managed via HSM.
[0042] In this embodiment, the data storage layer consists of an Elasticsearch cluster storing unstructured data, supporting full-text search and aggregation analysis. A Redis cluster caches frequently accessed data, reducing database query pressure and improving response speed.
[0043] In this embodiment, the caching and sharding strategies are as follows: The Redis cluster employs master-slave replication and sharded storage to support real-time resource status queries at the 100,000 QPS level. Elasticsearch uses time and region sharding to optimize the retrieval efficiency of petabyte-scale log data. Asynchronous processing is implemented: Time-consuming operations such as resource allocation and report generation are executed asynchronously through message queues to avoid blocking core processes.
[0044] Optionally, it also includes: analyzing the full lifecycle operation log of the event to obtain an optimization suggestion report, generating a three-dimensional backtracking analysis result based on the event backtracking initiated by the user, and obtaining event experience data based on the optimization suggestion report and the three-dimensional backtracking analysis result, specifically: Obtain the full lifecycle operation log of the event, and calculate the core performance indicators based on the full lifecycle operation log; wherein, the core performance indicators include: resource utilization rate, average response time, task completion rate and resource idle rate; An optimization suggestion report was obtained by analyzing the core performance indicators. Get the sudden event that the user initiated the replay, call the Cesium engine to build a 3D scene of the sudden event, control the replay progress with the timeline, and restore the development process of the sudden event by minute or event node; Obtain the key markers that the user marks on the nodes during the backtracking process, and perform in-depth analysis based on the key markers to obtain the three-dimensional backtracking analysis results; The optimization suggestion report and the three-dimensional backtracking analysis results are integrated to obtain event experience data.
[0045] In this embodiment, the 3D GIS backtracking function built on the Cesium engine allows users to select the event to be backtracked in the system interface, realize event backtracking, and obtain 3D backtracking analysis results by marking and analyzing key nodes. WebGL rendering technology is used to dynamically load spatiotemporal data, enabling visualization and deduction of the event's impact range.
[0046] Optionally, it also includes: retrieving and structuredly outputting the entire lifecycle operation logs of the event according to the user's review needs, specifically: Obtain the user's event retrieval statement, and retrieve the target event ID based on the event retrieval statement; Based on the target event ID, the corresponding event lifecycle operation logs are integrated to obtain multi-source event data, and the corresponding report template is matched according to the event type in the multi-source event data; wherein, the report template is pre-stored in the template library; The multi-source event data is populated into the report template using the template engine to generate a preliminary structured report; The user's customized requirements are obtained, and the preliminary structured report is rendered to obtain the debriefing report.
[0047] In this embodiment, users (such as commanders, system administrators, or debriefing analysts) log in to the management platform, select the target event to be debriefed from the event list, and click the "Generate Report with One Click" button. The system then triggers the report generation task and enters the data preparation phase. Multi-source event data includes: basic event information, response process data, operation log data, situation monitoring data, and external related data. After the initial structured report is generated, users can insert custom fields and charts to meet their specific needs, ultimately generating a debriefing report tailored to their requirements.
[0048] Optionally, it also includes: acquiring disaster early warning data from external systems and generating cross-departmental collaborative workflow tasks based on the disaster early warning data to enable collaborative operations among departments, specifically: Create an interface configuration task for external systems and configure the interface information of external systems through a RESTful API; the external systems include the meteorological bureau system and the seismic network system. It receives disaster early warning data transmitted from the external system in real time, and transforms the structure of the disaster early warning data into an internal data structure based on data mapping rules; Based on the system's built-in visual process designer, cross-departmental collaborative process tasks are generated from the transformed disaster early warning data, and these tasks are then distributed to the corresponding personnel.
[0049] In this embodiment, to enhance the foresight and coordination of emergency response, the system provides unified cross-system integration capabilities, supporting integration with external early warning systems to obtain real-time disaster information, while simultaneously enabling standardized modeling and automated execution of internal cross-departmental emergency procedures. This process is divided into two main modules: external system integration and internal collaborative process configuration, both of which are configured by the system administrator in the management platform to ensure bidirectional data and process connectivity.
[0050] In this embodiment, to address the diversity of emergency business scenarios and the rapid evolution of the technology ecosystem, the system adopts a "plug-in architecture + progressive release" mechanism. This supports the dynamic expansion of functional modules without service interruption and ensures the security and stability of new feature deployments. It achieves controllable evolution throughout the entire lifecycle from development to deployment.
[0051] Optionally, when new features are required or third-party services need to be integrated, developers can customize resource models and response level types within the system and quickly integrate third-party services through Feign's declarative interface. Dynamic plugin loading is implemented using the OSGi framework, allowing for the expansion of functional modules without restarting the system. When new features are launched, system administrators, based on Nginx load balancing and A / B testing strategies, select a subset of users as test subjects, gradually releasing the new features, monitoring stability and performance metrics, and ensuring a smooth transition to all users.
[0052] In this embodiment, a loosely coupled service cluster is built based on Spring Cloud, enabling modular development and independent deployment. Service interfaces are managed uniformly through an API gateway, supporting dynamic routing, rate limiting, and circuit breaking mechanisms to ensure high availability. Kafka / RabbitMQ message queues are used to achieve real-time asynchronous transmission of event data, ensuring system throughput and fault tolerance.
[0053] Based on and Figure 1 Using the same principle as the method shown, this embodiment of the invention also provides an emergency response full-cycle management system, such as... Figure 2 As shown, it includes: The event type determination module is used to obtain event information of sudden events, input the event information into the response determination model for processing, and obtain the initial response level and event type. The dispatch strategy module is used to obtain the dispatch request generated by the commander on the command terminal based on the initial response level and the event type, match the dispatch request with the emergency resource data in the resource pool, obtain the dispatch instruction and send it to the mobile APP of the executor to instruct the executor to handle the event; The real-time monitoring module is used to monitor event response indicators in real time, and when the event response indicators reach a preset alarm threshold, generate alarm information and push it to the command terminal. The command terminal responds to the alarm information to generate an upgrade dispatch instruction and sends it to the mobile APP of the execution personnel. The operation log module is used to generate a full lifecycle operation log of the event after the event is processed, and to encrypt the full lifecycle operation log of the event.
[0054] Also includes: The experience summary module is used to analyze the operation log of the entire life cycle of the event to obtain an optimization suggestion report, and generate a three-dimensional backtracking analysis result based on the event backtracking initiated by the user. Event experience data is obtained based on the optimization suggestion report and the three-dimensional backtracking analysis result. The debriefing module is used to retrieve and structure the operation logs of the entire lifecycle of an event according to the user's debriefing needs, and generate a debriefing report.
[0055] The external collaboration module is used to acquire disaster early warning data from external systems and generate cross-departmental collaborative workflow tasks based on the disaster early warning data, so as to realize collaborative operations among various departments.
[0056] like Figure 2 As shown, in this embodiment, the system consists of a user interaction layer, a core business logic layer, and a basic technical support layer: 1. User interaction layer, located at the top of the architecture, is the interface entry point for information interaction between the system and various users, directly facing end users with different roles: Command terminal: A dedicated terminal device for emergency command personnel to receive alarm information, issue dispatch instructions, monitor event progress, etc., and has high visibility and operation permissions.
[0057] Large screen: Used to display information such as the overall situation, key indicators, resource distribution heat map, and event development sequence in the emergency command center. It supports multi-dimensional data visualization and facilitates high-level decision-making.
[0058] Management Platform: A web-based system for administrators, providing functions such as event management, resource configuration, process configuration, access control, and report generation.
[0059] Mobile App: An application deployed on the mobile phones of personnel (such as repairmen and rescue team members) to receive dispatch instructions, report on-site conditions, track location and check in, and provide task feedback, thereby realizing "digitalization of front-line operations".
[0060] 2. The core business logic layer, located in the middle layer, is the core processing hub of the system, carrying the key business logic and intelligent modules throughout the entire emergency response process: Multi-level response mechanism: Automatically or manually trigger different levels of response processes based on the severity of the event, supporting hierarchical response strategies from level one to level four, and achieving dynamic matching of response intensity.
[0061] Dynamic resource allocation: Based on GIS geofencing, resource availability, path planning algorithms, etc., the optimal resource scheduling scheme is calculated in real time to improve resource utilization efficiency.
[0062] Emergency Response Dynamic Adjustment Module: During the event evolution, the response status is automatically assessed based on real-time monitoring indicators (such as service outage rate and resource shortage), and suggestions are made on whether to upgrade or downgrade the response level.
[0063] Intelligent decision support module: Integrates AI models, rule engines and historical experience data to provide commanders with auxiliary decision-making suggestions, such as optimal scheduling plans, risk prediction, and impact range estimation.
[0064] Event review system module: Supports full-process retrospective analysis of completed events, and generates optimization suggestion reports by combining 3D visualization, key node marking and other functions to promote the accumulation of experience.
[0065] 3. The basic technical support layer, located at the bottom layer, provides a stable and efficient technical foundation for upper-layer applications, mainly including: Microservice architecture: The system adopts a microservice architecture design, with each functional module deployed independently and elastically scalable, improving the system's flexibility, maintainability, and fault tolerance.
[0066] Data platform support: Construct a unified data aggregation, governance and sharing platform, open up data channels between internal and external systems, and realize cross-departmental and cross-system data integration and service output.
[0067] Data storage layer: Responsible for the persistent storage of various structured and unstructured data, including event logs, resource information, operation records, and early warning data. It usually adopts a combination of relational databases (such as MySQL) and non-relational databases (such as Elasticsearch and MongoDB).
[0068] Data processing layer: It undertakes tasks such as data cleaning, transformation, aggregation, and real-time computing, supports streaming processing (such as Kafka + Flink) and batch processing (such as Hadoop), and ensures the timeliness and accuracy of data.
[0069] The emergency response full-cycle management system of this invention can execute the emergency response full-cycle management method provided in this invention. The implementation principle is similar. The actions performed by each module and unit in the emergency response full-cycle management system in each embodiment of this invention correspond to the steps in the emergency response full-cycle management method in each embodiment of this invention. For detailed functional descriptions of each module of the emergency response full-cycle management system, please refer to the descriptions in the corresponding emergency response full-cycle management methods shown above, which will not be repeated here.
[0070] The aforementioned emergency response full-cycle management system can be a computer program (including program code) running on a computer device, such as an application software; the application software can be used to execute the corresponding steps in the method provided in the embodiments of the present invention.
[0071] The modules described in the embodiments of the present invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.
[0072] Based on the same principles as the methods shown in the embodiments of the present invention, the embodiments of the present invention also provide an electronic device, which may include, but is not limited to: a processor and a memory; the memory for storing computer programs; and the processor for executing the methods shown in any embodiment of the present invention by invoking the computer programs.
[0073] In one alternative embodiment, an electronic device is provided, such as Figure 3 As shown, Figure 3 The illustrated electronic device includes a processor and a memory. The processor and memory are connected, for example, via a bus. Optionally, the electronic device may also include a transceiver, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver is not limited to one unit, and the structure of this electronic device does not constitute a limitation on the embodiments of the present invention.
[0074] The memory stores application code (computer program) that executes the present invention, and its execution is controlled by a processor. The processor executes the application code stored in the memory to implement the content shown in the foregoing method embodiments.
[0075] Among these, electronic devices can also be terminal devices. Figure 3 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.
[0076] This invention provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.
[0077] According to another aspect of the present invention, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various embodiments described above.
[0078] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.
[0079] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.
Claims
1. A method for full-cycle emergency response management, characterized in that, The method includes: Acquire event information about the emergency, input the event information into the response judgment model for processing, and obtain the initial response level and event type; The system obtains the dispatch request generated by the command personnel on the command terminal based on the initial response level and the event type, matches the dispatch request with the emergency resource data in the resource pool, obtains the dispatch instruction, and sends it to the mobile APP of the execution personnel to instruct the execution personnel to handle the event. Real-time monitoring of event response indicators, and when the event response indicators reach a preset alarm threshold, generating alarm information and pushing it to the command terminal, using the command terminal to respond to the alarm information to generate an upgrade dispatch instruction and send it to the mobile APP of the execution personnel; After the event is processed, a full lifecycle operation log is generated and encrypted.
2. The emergency response full-cycle management method according to claim 1, characterized in that, The mobile app that receives and sends dispatch instructions to the personnel involved in the execution process is as follows: Obtain the command personnel's dispatch request regarding the initial response level and the event type; Based on the scheduling request, the microservice architecture automatically queries the emergency resource data in the resource pool and matches it with the emergency resource data to obtain the schedulable resources; Based on GIS map services, geofences are constructed with the location of the emergency as the center and the influence radius preset according to the event type as the range. Spatial query engines are then used to filter out schedulable resources located within the geofences. The resource allocation scheme is obtained by calculating the schedulable resource allocation scheme using the path planning method. The resource allocation plan is converted into scheduling instructions and sent to the mobile APP of the executors.
3. The emergency response full-cycle management method according to claim 1, characterized in that, The event response metrics include: service outage rate and resource shortage; the specific real-time monitoring of event response metrics is as follows: The basic indicators of the affected area are monitored, and the event response indicators are obtained by analyzing the basic indicators. The basic indicators include: site failure rate, resource distribution heat map, and response progress.
4. The emergency response full-cycle management method according to claim 1, characterized in that, The specific steps for generating a full lifecycle operation log for an event are as follows: Record the operational actions throughout the entire process of an emergency, from its occurrence to its resolution, to obtain the original operation log; All the original operation logs are collected and preprocessed to obtain the full lifecycle operation log of the event; The token verification is used to verify the legitimacy of the received event lifecycle operation logs, and the symmetric encryption method is used to encrypt the event lifecycle operation logs after the legitimacy verification is passed. Logstash is used to write encrypted event lifecycle operation logs to the Elasticsearch cluster and create an index.
5. The emergency response full-cycle management method according to claim 1, characterized in that, Also includes: An optimization suggestion report is obtained by analyzing the entire lifecycle operation log of the event. Based on the event backtracking initiated by the user, a three-dimensional backtracking analysis result is generated. Event experience data is obtained based on the optimization suggestion report and the three-dimensional backtracking analysis result, specifically: Obtain the full lifecycle operation log of the event, and calculate the core performance indicators based on the full lifecycle operation log; wherein, the core performance indicators include: resource utilization rate, average response time, task completion rate and resource idle rate; An optimization suggestion report was obtained by analyzing the core performance indicators. Get the sudden event that the user initiated the replay, call the Cesium engine to build a 3D scene of the sudden event, control the replay progress with the timeline, and restore the development process of the sudden event by minute or event node; Obtain the key markers that the user marks on the nodes during the backtracking process, and perform in-depth analysis based on the key markers to obtain the three-dimensional backtracking analysis results; The optimization suggestion report and the three-dimensional backtracking analysis results are integrated to obtain event experience data.
6. The emergency response full-cycle management method according to claim 1, characterized in that, Also includes: Based on the user's review requirements, the entire lifecycle of the event's operation logs are retrieved and structured for output, resulting in a review report, specifically: Obtain the user's event retrieval statement, and retrieve the target event ID based on the event retrieval statement; Based on the target event ID, the corresponding event lifecycle operation logs are integrated to obtain multi-source event data, and the corresponding report template is matched according to the event type in the multi-source event data; wherein, the report template is pre-stored in the template library; The multi-source event data is populated into the report template using the template engine to generate a preliminary structured report; The user's customized requirements are obtained, and the preliminary structured report is rendered to obtain the debriefing report.
7. The emergency response full-cycle management method according to claim 1, characterized in that, Also includes: Acquire disaster early warning data from external systems and generate cross-departmental collaborative workflow tasks based on this data to enable collaborative operations among departments. Specifically: Create an interface configuration task for external systems and configure the interface information of external systems through a RESTful API; the external systems include the meteorological bureau system and the seismic network system. It receives disaster early warning data transmitted from the external system in real time, and transforms the structure of the disaster early warning data into an internal data structure based on data mapping rules; Based on the system's built-in visual process designer, cross-departmental collaborative process tasks are generated from the transformed disaster early warning data, and these tasks are then distributed to the corresponding personnel.
8. An emergency response full-cycle management system, characterized in that, include: The event type determination module is used to obtain event information of sudden events, input the event information into the response determination model for processing, and obtain the initial response level and event type. The dispatch strategy module is used to obtain the dispatch request generated by the commander on the command terminal based on the initial response level and the event type, match the dispatch request with the emergency resource data in the resource pool, obtain the dispatch instruction and send it to the mobile APP of the executor to instruct the executor to handle the event; The real-time monitoring module is used to monitor event response indicators in real time, and when the event response indicators reach a preset alarm threshold, generate alarm information and push it to the command terminal. The command terminal responds to the alarm information to generate an upgrade dispatch instruction and sends it to the mobile APP of the execution personnel. The operation log module is used to generate a full lifecycle operation log of the event after the event is processed, and to encrypt the full lifecycle operation log of the event.
9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-7.
10. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1-7.