Methods and equipment for determining the needs of emergency rescue systems

By constructing an emergency rescue mission architecture using Mission Engineering Guidelines 2.0 and the UAF framework, and combining it with simulation analysis, the problems of reliance on experience and misalignment of stakeholders in the emergency rescue system were solved, and the needs of the emergency rescue system were accurately determined and resources were accurately matched.

CN123070546APending Publication Date: 2026-11-10TSINGHUA UNIVERSITY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611175943.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-04
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

The existing emergency rescue system relies on the experience of experts in the field, lacks systematicity, and suffers from misalignment of emergency response entities, resulting in insufficient scientific rigor.

Method used

Using the Mission Engineering Guidelines 2.0 process and Unified Architecture Framework (UAF), combined with qualitative analysis and quantitative assessment, an emergency rescue mission architecture is constructed. Through simulation analysis, the final operational plan is determined, and a precise correlation is established between mission objectives, operational activities, and resource elements.

Benefits of technology

It has enabled the objective and accurate determination of the needs of the emergency rescue system, reduced the reliance on human experience, ensured the precise matching of emergency rescue activities and resources, and solved the systemic defects caused by decentralized departmental management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070546A_ABST
    Figure CN123070546A_ABST
Patent Text Reader

Abstract

This invention provides a method and apparatus for determining the requirements of an emergency rescue system, relating to the field of systems engineering technology. The method includes: determining the emergency rescue mission architecture corresponding to the emergency rescue task based on emergency rescue mission input data; the emergency rescue mission architecture characterizes the relationships between mission objectives, operational activities, operators, and resource elements throughout the entire process of executing the emergency rescue task; determining multiple operational schemes to be evaluated based on the emergency rescue mission architecture; simulating the multiple operational schemes to be evaluated to obtain simulation results for each scheme, and determining the final operational scheme based on all simulation results; updating the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue task. This invention provides an objective, accurate, and traceable method for determining the requirements of an emergency rescue system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of systems engineering technology, and in particular to a method and apparatus for determining the requirements of an emergency rescue system. Background Technology

[0002] In the face of frequent natural disasters, overlapping and compounded risks of accidents and disasters, as well as the safety hazards brought about by urbanization and industrialization and the challenges posed by climate change, building a unified command, specialized and general emergency response system that is responsive and coordinated at all levels is an essential requirement for effectively responding to various emergencies and maximizing the protection of people's lives and property.

[0003] In existing technologies, emergency response systems are typically built using a decentralized, experience-driven model with dispersed departmental management. However, this approach suffers from structural flaws such as reliance on domain experts' experience and knowledge, a lack of systematic approach, and misalignment of emergency response stakeholders. Therefore, providing an objective, accurate, and traceable method for determining the needs of an emergency response system is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This invention provides a method and apparatus for determining the needs of an emergency rescue system, which addresses the structural defects in the existing technology, such as reliance on the experience and knowledge of domain experts in the construction of emergency systems, lack of systematicity, and misalignment of emergency response entities.

[0005] This invention provides a method for determining the needs of an emergency rescue system, comprising the following steps.

[0006] Based on the emergency rescue mission input data, the emergency rescue mission architecture corresponding to the emergency rescue task is determined; the emergency rescue mission architecture is used to characterize the relationship between mission objectives, operational activities, operators and resource elements in the complete process of executing the emergency rescue task. Based on the aforementioned emergency rescue mission framework, several operational plans were identified for evaluation. Simulations are performed on the various operational schemes to be evaluated to obtain simulation results for each operational scheme to be evaluated. Based on all simulation results, the final operational scheme is determined. Based on the simulation results corresponding to the final operation scheme, the emergency rescue mission architecture is updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0007] According to the emergency rescue system requirement determination method provided by the present invention, the emergency rescue mission architecture includes a strategic layer, an operational layer, and a resource layer; The process of determining the emergency rescue mission architecture corresponding to the emergency rescue task based on the emergency rescue mission input data includes: Based on the emergency rescue mission input data, determine the mission architecture generation elements corresponding to the emergency rescue mission; Based on the mission architecture generation elements and the emergency rescue mission input data, the strategic layer is determined; the strategic layer is used to characterize the relationship between mission objectives, system capabilities, and strategic constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the strategy layer, the operation layer is determined; the operation layer is used to characterize the relationship between the operational activities and operational constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the operation layer, the resource layer is determined; the resource layer is used to characterize the relationship between the operation activities, resource objects, and resource constraints corresponding to the execution of the emergency rescue mission. Based on the system indicators in the mission architecture generation elements, the relationship between the strategic layer, the operational layer, and the resource layer is established to construct the emergency rescue mission architecture.

[0008] According to the emergency rescue system requirement determination method provided by the present invention, the mission architecture generation elements include: emergency rescue mission, mission objective, core issues, mission background, mission scenario, and system indicators; The process of determining the mission architecture generation elements corresponding to the emergency rescue mission based on the emergency rescue mission input data includes: Based on the emergency rescue mission input data, the emergency rescue task is determined; Based on the aforementioned emergency rescue mission, the mission objectives corresponding to the emergency rescue mission framework are determined; Based on the emergency rescue mission, the mission objectives, and the system construction status data in the emergency rescue mission input data, the core issues are identified; the core issues are used to characterize the different needs corresponding to completing the emergency rescue mission. Based on the emergency rescue mission, the mission objective, the core issue, and the emergency rescue mission input data, the mission background is determined; the mission background is used to characterize the scenario environment and constraints corresponding to the execution of the emergency rescue mission. Based on the aforementioned mission background, the mission scenario corresponding to the emergency rescue mission is determined; the mission scenario is used to characterize the mission execution environment corresponding to the emergency rescue mission. Based on the stated mission objectives and the stated core issues, the system indicators are determined.

[0009] According to the emergency rescue system demand determination method provided by the present invention, determining the strategic layer based on the mission architecture generation elements and the emergency rescue mission input data includes: Based on the mission objectives and the mission background, determine the system capabilities corresponding to the emergency rescue mission; Based on the mission scenario, the emergency rescue-related systems in the emergency rescue mission input data, and the success indicators in the system indicators, the strategic constraints are determined; the success indicators are used to quantify the final achievement of the mission objectives. The strategic layer is determined based on the stated mission objectives, system capabilities, and strategic constraints.

[0010] According to the emergency rescue system requirements determination method provided by the present invention, the step of determining the operational layer based on the mission architecture generation elements and the strategic layer includes: Based on the task scenario, determine the operational activities corresponding to the emergency rescue task; Based on the effectiveness indicators in the system indicators, the system capabilities corresponding to the strategic layer, and the task scenarios, the operational constraints corresponding to the operational activities are determined; the effectiveness indicators are used to quantify the effectiveness of the operational activities. The operating layer is determined based on the operating activities and the operating constraints.

[0011] According to the emergency rescue system requirements determination method provided by the present invention, the step of determining the resource layer based on the mission architecture generation elements and the operational layer includes: Based on the running activities and running constraints corresponding to the running layer, determine the resource objects corresponding to the running activities; Based on the performance indicators in the system indicators, the equipment technical parameters corresponding to the resource object, and the operational constraints, the resource constraints are determined; the performance indicators are used to quantify the support capability of the resource object for the operational activities. The resource layer is determined based on the running activity, the resource object, and the resource constraints.

[0012] According to the emergency rescue system requirements determination method provided by the present invention, the determination of multiple operational schemes to be evaluated based on the emergency rescue mission architecture includes: Determine the executor corresponding to the running activity in the emergency rescue mission architecture, and the resource configuration parameters corresponding to the executor; Based on the resource constraints in the emergency rescue mission architecture and the equipment technical parameters, the resource parameters corresponding to the resource object are determined; Based on the executor, the resource configuration parameters, and the resource parameters, a baseline operation plan is determined; Based on the baseline operating plan, at least one alternative operating plan is determined; The baseline operating plan and all alternative operating plans are identified as the multiple operating plans to be evaluated.

[0013] According to the emergency rescue system demand determination method provided by the present invention, determining at least one alternative operation plan based on the baseline operation plan includes: Randomly adjust at least one of the resource configuration parameters, resource parameters, and activity execution parameters in the baseline operation plan to obtain at least one alternative operation plan.

[0014] According to the emergency rescue system demand determination method provided by the present invention, the step of simulating the multiple operational schemes to be evaluated to obtain simulation results corresponding to each operational scheme to be evaluated includes: For each of the proposed operational schemes to be evaluated, a simulation scenario model and a simulation environment agent are determined based on the task scenario. Based on the operational layer and the resource layer, the task agent corresponding to the executor, the agent state and agent attribute parameters corresponding to the task agent and the simulation environment agent, and the simulation operational mechanism between the task agent and the simulation environment agent are determined. The simulation operational mechanism is executed to perform Monte Carlo simulation on the proposed operational scheme to be evaluated, and the simulation results corresponding to the proposed operational scheme are obtained.

[0015] According to the emergency rescue system demand determination method provided by the present invention, the step of determining the final operation plan based on all simulation results includes: For each of the proposed operational schemes to be evaluated, based on the simulation results corresponding to the proposed operational scheme, the performance index value corresponding to the proposed operational scheme is determined; based on the performance index value corresponding to the proposed operational scheme, the effectiveness index value corresponding to the proposed operational scheme is determined; based on the effectiveness index value corresponding to the proposed operational scheme, the success index value corresponding to the proposed operational scheme is determined; and candidate operational schemes that meet the constraints are determined from all proposed operational schemes to be evaluated; the constraints are that the success index value meets the strategic constraints. The candidate running scheme corresponding to the highest success index value is determined as the final running scheme.

[0016] According to the emergency rescue system requirements determination method provided by the present invention, the step of updating the emergency rescue mission architecture based on the simulation results corresponding to the final operation plan to obtain the emergency rescue system requirements corresponding to the emergency rescue task includes: Based on the simulation results corresponding to the final operation scheme, the strategic constraints, operational constraints, and resource constraints in the emergency rescue mission architecture are updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0017] The present invention also provides an emergency rescue system demand determination device, comprising the following modules.

[0018] The first determining module is used to determine the emergency rescue mission architecture corresponding to the emergency rescue mission based on the emergency rescue mission input data; the emergency rescue mission architecture is used to characterize the relationship between mission objectives, operational activities, operators and resource elements in the complete process of executing the emergency rescue mission; The second determining module is used to determine multiple operational schemes to be evaluated based on the emergency rescue mission architecture. The simulation module is used to simulate the various operating schemes to be evaluated, obtain the simulation results corresponding to each operating scheme to be evaluated, and determine the final operating scheme based on all simulation results. The update module is used to update the emergency rescue mission architecture based on the simulation results corresponding to the final operation scheme, so as to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0019] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the emergency rescue system demand determination method as described above.

[0020] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the emergency rescue system requirement determination method as described above.

[0021] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the emergency rescue system requirement determination method as described above.

[0022] The present invention provides a method and apparatus for determining the requirements of an emergency rescue system. Based on input data of the emergency rescue mission, an emergency rescue mission architecture is determined. Based on this architecture, multiple operational schemes to be evaluated are identified, and simulations of these schemes are performed to determine the final operational scheme. The emergency rescue mission architecture is then updated based on the simulation results corresponding to the final operational scheme, resulting in the emergency rescue system requirements corresponding to the emergency rescue task. In this invention, the emergency rescue mission architecture characterizes the relationships between mission objectives, operational activities, executors, and resource elements throughout the entire emergency rescue mission process. It establishes a precise and traceable structured logical link between strategic objectives and specific execution resources, addressing issues such as a lack of systematic approach and misalignment of emergency response entities due to decentralized departmental management. By identifying multiple operational schemes to be evaluated through the emergency rescue mission architecture, reliance on human experience is reduced. The final operational scheme is determined through simulations of these schemes and evaluation of the simulation results, ensuring that the selection of the final operational scheme is supported by objective data and avoiding insufficient scientific rigor due to subjective judgment. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in this 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 this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0024] Figure 1 This is a flowchart illustrating the method for determining the needs of an emergency rescue system provided in an embodiment of the present invention.

[0025] Figure 2 This is a schematic diagram of the mission thread provided in an embodiment of the present invention.

[0026] Figure 3 This is a schematic diagram illustrating the construction of a task agent provided in an embodiment of the present invention.

[0027] Figure 4 This is a flowchart illustrating the simulation operation mechanism provided in this embodiment of the invention.

[0028] Figure 5 This is a schematic diagram of the emergency rescue system demand determination device provided in an embodiment of the present invention.

[0029] Figure 6 This is a schematic diagram of the structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0031] To address the structural deficiencies in existing emergency response systems, such as reliance on domain experts' experience and knowledge, lack of systematicity, and misalignment of emergency response stakeholders, this invention provides a method for determining the needs of an emergency rescue system. Based on the Mission Engineering Guide 2.0 process, it proposes a Unified Architecture Framework (UAF) and simulation analysis model, combining qualitative analysis and quantitative assessment to systematically solve the problem of emergency rescue needs analysis. Mission Engineering is a high-level evolution of systems engineering methodology in complex task environments, aiming to address cross-domain, multi-factor coupled decision-making challenges through a structured analysis framework. The Unified Architecture Framework (UAF) is a system modeling method for complex organizations. A complete UAF architecture includes multiple views across 13 domains, including strategy, operations, services, personnel, resources, security, projects, and standards. It is a framework with strong interoperability, high operability, and open-mindedness for understanding, building, and analyzing complex systems, possessing strong versatility and representing a cutting-edge architecture framework.

[0032] In this embodiment of the invention, emergency rescue requires the construction of a systematic capability for complex disaster environments. Therefore, based on mission engineering processes, a quantifiable and traceable emergency rescue mission architecture can be constructed. Digital engineering methods can be used to dynamically optimize emergency rescue processes, ensuring precise matching of emergency rescue activities and resources to complete emergency rescue tasks. A unified architecture framework with corresponding multi-level views provides systematic support for the emergency rescue system, solving the complex integration and adaptation problems of multi-dimensional elements in emergency rescue.

[0033] Figure 1 This is a flowchart illustrating the method for determining the needs of an emergency rescue system provided in an embodiment of the present invention, as shown below. Figure 1 As shown, the method includes the following steps 110 to 140.

[0034] Step 110: Based on the emergency rescue mission input data, determine the emergency rescue mission architecture corresponding to the emergency rescue task; the emergency rescue mission architecture is used to characterize the relationship between mission objectives, operational activities, operators and resource elements in the complete process of executing the emergency rescue task.

[0035] Specifically, the input data for this emergency rescue mission consists of external data required to define the emergency rescue task and construct the emergency rescue mission architecture. This input data includes task text data, relevant emergency rescue regulations, emergency rescue capability building goals, typical disaster types, system construction status data, and geographic environment data. Specifically: the task text data is natural language text input by the user to describe the task information; the relevant emergency rescue regulations characterize the overall requirements for the construction of the emergency rescue mission architecture and task execution; the emergency rescue capability building goals characterize the overall effects expected to be achieved by the emergency rescue mission architecture (e.g., time constraint data characterizes the time requirements that need to be met during task execution); the typical disaster types characterize the potential task scenarios the emergency rescue mission architecture may face in the future; the system construction status data characterizes the current system capability level and existing problems; and the geographic environment data characterizes the spatial environment of the task area.

[0036] After acquiring the input data for the emergency rescue mission, the electronic device extracts key parameters and constraints from the input data through structured parsing and semantic analysis, thereby constructing an emergency rescue mission architecture. This emergency rescue mission architecture is used to characterize the relationships between mission objectives, operational activities, operators, and resource elements during the complete execution of the emergency rescue mission, and serves as the foundational model for subsequent mission analysis, simulation verification, and demand parameter derivation.

[0037] It should be noted that this emergency rescue mission architecture includes a mission thread and a mission engineering thread. The mission thread is used to represent the operational activities, events and their logical relationships involved in the mission execution process, while the mission engineering thread is used to represent the executors, systems, resources that support the mission execution, as well as the correspondence between operational activities.

[0038] Step 120: Based on the aforementioned emergency rescue mission architecture, identify multiple operational schemes to be evaluated.

[0039] Specifically, based on the emergency rescue mission framework, multiple operational plans to be evaluated are identified. Each operational plan to be evaluated is used to characterize the combination of operational executors, resource configurations, and resource parameters designed to complete the emergency rescue mission. For example, the operational plan to be evaluated specifies who performs each operational activity, how many resources are configured, and what level of resource performance is required.

[0040] It should be noted that at least one of the following may differ among the different operational schemes to be evaluated: the operator, resource configuration, and resource parameters.

[0041] Step 130: Simulate the various operating schemes to be evaluated to obtain the simulation results corresponding to each operating scheme to be evaluated, and determine the final operating scheme based on all simulation results.

[0042] Specifically, after identifying multiple operational plans to be evaluated, each plan is converted into an executable intelligent agent simulation model with autonomous behavior capabilities. Multiple Monte Carlo simulation experiments are then conducted on the intelligent agent simulation model to determine the simulation results corresponding to each operational plan to be evaluated. These simulation results may include the number of new deaths, total rescue time, road clearing completion time, search completion time, number of trapped people rescued, number of injured people transferred, and resource usage. Based on all simulation results, the final operational plan is determined from all operational plans to be evaluated.

[0043] Step 140: Update the emergency rescue mission architecture based on the simulation results corresponding to the final operation scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0044] Specifically, after determining the final operation plan, the constraint parameters in the emergency rescue mission architecture are updated based on the simulation results corresponding to the final operation plan, resulting in the updated emergency rescue system requirements supported by objective simulation data.

[0045] The emergency rescue system requirements determination method provided in this invention determines the emergency rescue mission architecture based on emergency rescue mission input data, identifies multiple operational schemes to be evaluated based on the emergency rescue mission architecture, simulates these multiple operational schemes to determine the final operational scheme, and updates the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme, thereby obtaining the emergency rescue system requirements corresponding to the emergency rescue task. In this invention, the emergency rescue mission architecture is used to characterize the relationships between mission objectives, operational activities, executors, and resource elements throughout the complete process of an emergency rescue task. It establishes a precise and traceable structured logical link between strategic objectives and specific execution resources, solving problems such as lack of systematicity and misalignment of emergency subjects caused by decentralized departmental management. By determining multiple operational schemes to be evaluated through the emergency rescue mission architecture, reliance on human experience is reduced. The final operational scheme is determined through simulation of multiple operational schemes and evaluation of simulation results, ensuring that the selection of the final operational scheme is supported by objective data and avoiding the problem of insufficient scientific rigor due to subjective judgment.

[0046] It should be noted that the emergency rescue mission architecture includes a strategic layer, an operational layer, and a resource layer. The strategic layer represents the relationship between mission objectives, system capabilities, and strategic constraints corresponding to the execution of the emergency rescue mission. The operational layer represents the relationship between operational activities and operational constraints corresponding to the execution of the emergency rescue mission. The resource layer represents the relationship between operational activities, resource objects, and resource constraints corresponding to the execution of the emergency rescue mission. In this embodiment of the invention, a UAF is used to formally model the emergency rescue mission architecture. Mission threads are formed based on the operational activities in the operational layer, and mission engineering threads are formed based on the executors and resource requirements in the resource layer, thereby establishing a traceable relationship between mission objectives, operational activities, and resource elements.

[0047] In one embodiment, determining the emergency rescue mission architecture corresponding to the emergency rescue mission based on the emergency rescue mission input data includes: Based on the emergency rescue mission input data, determine the mission architecture generation elements corresponding to the emergency rescue mission; Based on the mission architecture generation elements and the emergency rescue mission input data, the strategic layer is determined; Based on the mission architecture generation elements and the strategy layer, the operational layer is determined; Based on the mission architecture generation elements and the runtime layer, the resource layer is determined; Based on the system indicators in the mission architecture generation elements, the relationship between the strategic layer, the operational layer, and the resource layer is established to construct the emergency rescue mission architecture.

[0048] Specifically, based on the mission engineering methodology, the mission architecture generation elements corresponding to the emergency rescue mission are determined according to the input data. These elements include: emergency rescue mission, mission objectives, core issues, mission background, mission scenario, and system indicators. Then, based on these elements, the system capabilities corresponding to completing the emergency rescue mission are determined. For example, for a tunnel collapse rescue scenario, these capabilities could include search and rescue capabilities, road clearing capabilities, medical treatment capabilities, and coordinated command capabilities. Combining the mission architecture generation elements, the emergency rescue mission input data, and the system capabilities, a strategic layer is constructed within the emergency rescue mission architecture. This strategic layer determines the construction goals of the emergency rescue mission architecture and the required levels of each system capability. Next, based on the mission architecture generation elements, the operational activities involved in completing the emergency rescue mission and the logical relationships between these activities are identified. Based on the system capabilities, operational activities, and logical relationships in the strategic layer, an operational layer is constructed within the emergency rescue mission architecture, forming mission threads. This operational layer determines which operational activities need to be executed to complete the emergency rescue mission, the execution order of these activities, and the required efficiency for each activity. Subsequently, based on the resource objects for executing operational activities determined by the operational layer, and combined with the elements, operational activities, and resource objects generated by the mission architecture, the resource layer in the emergency rescue mission architecture is constructed, and a mission engineering thread is formed. Based on this resource layer, the resources that need to be configured to complete the corresponding operational activities and the performance that the resources need to have can be determined.

[0049] Next, success metrics are linked to system capabilities at the strategic level, effectiveness metrics to operational activities at the operational level, and performance metrics to resource objects at the resource level. This establishes the metric transfer relationships among success, effectiveness, and performance metrics, reflecting the impact between resource performance, activity execution effectiveness, and mission objective achievement. Based on these steps, the emergency response mission architecture can be constructed.

[0050] In this embodiment of the invention, the emergency rescue mission architecture is divided into three levels: strategic, operational, and resource. A mapping relationship between these levels is established through an indicator transmission chain, transforming emergency system construction from departmental planning to a systematic planning that integrates strategy, operation, and resources, and from experience-driven decision-making to data-driven decision-making. This three-layer architecture ensures the traceability of the complete logic from mission objectives to resource parameters. Adjustments to any parameter in the emergency rescue mission architecture can be tracked to track their impact on other parameters, thereby addressing structural deficiencies such as lack of systematicity, inefficient relationships, and ineffective mechanisms.

[0051] In one embodiment, determining the mission architecture generation elements corresponding to the emergency rescue mission based on the emergency rescue mission input data includes: The emergency rescue mission is determined based on the mission text data in the emergency rescue mission input data; Based on the aforementioned emergency rescue mission, the mission objectives corresponding to the emergency rescue mission framework are determined; Based on the emergency rescue mission, the mission objectives, and the system construction status data in the emergency rescue mission input data, the core issues are identified; the core issues are used to characterize the different needs corresponding to completing the emergency rescue mission. Based on the emergency rescue mission, the mission objective, the core issue, and the emergency rescue mission input data, the mission background is determined; the mission background is used to characterize the scenario environment and constraints corresponding to the execution of the emergency rescue mission. Based on the aforementioned mission background, the mission scenario corresponding to the emergency rescue mission is determined; the mission scenario is used to characterize the mission execution environment corresponding to the emergency rescue mission. Based on the stated mission objectives and the stated core issues, the system indicators are determined.

[0052] Specifically, the electronic device performs semantic parsing on the task text data in the emergency rescue mission input data to extract the emergency rescue task. This emergency rescue task is used to characterize emergency rescue tasks in natural disaster and accident scenarios and to ensure the effective implementation of rescue activities. That is, the electronic device inputs the task text data into a large language model, which extracts elements from the task text data to obtain task elements such as the task object, task action, task scope, task time limit, and task result. Then, it performs semantic matching between the extracted task elements and preset scenarios in a preset emergency rescue task type library, and identifies the matched preset rescue task as the actual emergency rescue task. It should be noted that the preset emergency rescue task type library includes the relationships between preset scenarios and preset rescue tasks.

[0053] Next, prompt words are constructed based on the emergency rescue mission, and these prompt words are input into a large language model. The large language model extracts keywords from the emergency rescue mission, such as the target object, target status, completion deadline, and degree of achievement. This generates the mission objective corresponding to the emergency rescue mission architecture. The mission objective is used to characterize the overall effect expected to be achieved by constructing the emergency rescue mission architecture. For example, the mission objective may include reducing casualties caused by disasters, shortening the completion time of rescue missions, improving the efficiency of rescue resource utilization, and improving the multi-department collaborative rescue capabilities.

[0054] Next, the emergency rescue mission and objectives are considered the desired state, while the current status of system construction data is considered the current state. A comparative analysis of the current and desired states is then conducted to identify the gaps between them. These gaps are then identified as the core issues that need to be addressed to reach the desired state from the current state. These core issues can include the capability requirements, operational requirements, and resource requirements needed to complete the emergency rescue mission. For example, when constructing the emergency rescue mission architecture, these core issues could be: under different disaster scenarios, what strategic capabilities, operational mechanisms, and resource systems are needed, and what levels of quantity and performance parameters of various emergency rescue resources should be achieved to meet the needs of the emergency rescue mission and obtain optimal rescue results?

[0055] Subsequently, prompt words are constructed by combining the emergency rescue mission, objectives, core issues, and typical disaster types, geographical environment data, and time constraints from the emergency rescue mission input data. These prompt words are then input into a large language model, which extracts disaster types, affected objects, geographical environment, road conditions, and time constraints to extract the mission background. This mission background represents the scenario environment and constraints corresponding to the execution of the emergency rescue mission. The mission background includes background setting, environmental conditions, time frame, and objective. The background setting is used to represent the overall scenario in which the emergency rescue mission occurs. Taking a tunnel collapse rescue scenario as an example, the background setting could be that disasters such as earthquakes, sudden water and mud inrushes, and landslides may cause tunnel collapse accidents, resulting in construction workers or vehicles being trapped inside the tunnel, requiring the organization of emergency rescue forces to carry out search and rescue, disaster relief, and transfer tasks. The environmental conditions are used to characterize the objective factors affecting the execution of emergency rescue missions. These environmental conditions include disaster type, impact range, geographical environment, and road access status. The disaster type can be an earthquake or landslide; the geographical environment can be a high-altitude mountainous area; and the road access status can be partial road closures. The time frame is used to characterize the time constraints for the execution of emergency rescue missions. Taking a tunnel collapse rescue scenario as an example, the time frame can be the 72-hour golden rescue period. The mission objectives can include reducing casualties, shortening rescue time, improving the utilization rate of rescue resources, and enhancing rescue coordination capabilities. The background setting and environmental conditions are used to characterize the scenario environment corresponding to the execution of emergency rescue missions, while the time frame and mission objectives are used to characterize the constraints corresponding to the execution of emergency rescue missions.

[0056] Next, based on the mission background, cue words are constructed and input into a large language model. This model then constructs a task scenario representing the mission execution environment corresponding to the emergency rescue mission. This task scenario can include disaster triggering conditions, mission execution location, affected objects, mission phases, available resources, external environmental conditions, and mission termination conditions. Taking an earthquake-induced tunnel collapse as an example, the task scenario could be a partial collapse of a highway tunnel in a high-altitude mountainous area due to an earthquake, with trapped personnel inside, varying degrees of damage to the road network, and some access roads interrupted. Emergency rescue forces need to complete search and rescue, disaster relief, and medical evacuation within the critical 72-hour window. Furthermore, the task scenario can be further divided into multiple scenario segments for different phases of the emergency rescue mission. For example, multiple scenario segments could include disaster occurrence, information reporting, road clearing, search and rescue, and medical evacuation.

[0057] Next, the mission objectives and core issues are input into a large language model, through which system indicators are extracted. These system indicators include success indicators, effectiveness indicators, and performance indicators. Each system indicator includes an indicator name, measurement object, calculation scope, unit of measurement, target direction, threshold conditions, and data source. The success indicator quantifies the final achievement of the mission objectives. For example, it may include the number of new deaths due to delayed rescue or worsening of injuries during the rescue process, and the total rescue time from the disaster's occurrence to the completion of the main search and rescue and evacuation tasks. The effectiveness indicator quantifies the effectiveness of operational activities, reflecting whether the activities are effective. For example, it may include the 24-hour road clearing completion rate, the 72-hour trapped personnel rescue rate, and the 72-hour casualty evacuation completion rate. The performance indicator quantifies the support capacity of resource objects for operational activities and is related to the executor, resource type, and equipment technical parameters of the resource objects. For example, it may include drilling speed and drone endurance. It should be noted that the success metric is obtained by weighted summation of the effectiveness metric, which in turn is obtained by weighted summation of the performance metric. In this embodiment of the invention, the success metric can be extracted from the mission objective, the effectiveness metric can be determined based on the success metric and operational activities, and the performance metric can be determined based on the effectiveness metric, core issues, executors, resource types, and equipment technical parameters of the resource objects.

[0058] In one embodiment, determining the strategic layer based on the mission architecture generation elements and the emergency response mission input data includes: Based on the mission objectives and the mission background, determine the system capabilities corresponding to the emergency rescue mission; Based on the mission scenario, the emergency rescue-related systems in the emergency rescue mission input data, and the success indicators in the system indicators, the strategic constraints are determined; the success indicators are used to quantify the final achievement of the mission objectives. The strategic layer is determined based on the stated mission objectives, system capabilities, and strategic constraints.

[0059] Specifically, the task scenario is determined based on the mission context. Then, a pre-defined capability mapping table is obtained, which includes the mapping relationships between pre-defined scenarios, pre-defined objectives, and pre-defined capabilities. Next, the task scenario and mission objectives are matched against the pre-defined capability mapping table to obtain the system capabilities required to complete the emergency rescue mission. These system capabilities may include at least one of the following: search and rescue capability, road accessibility capability, casualty rescue capability, on-site command capability, information transmission capability, and resource support capability. For example, these system capabilities may include reducing casualties corresponding to search and rescue capability and medical treatment capability; shortening rescue time corresponding to disaster awareness capability, communication capability, and support capability; and improving collaborative rescue capability corresponding to command capability and scientific decision-making capability. Then, based on the impact of the environmental conditions corresponding to the task scenario on the execution of system capabilities, the mandatory requirements stipulated in emergency rescue-related regulations, and success indicators, prompt words are constructed. These prompt words are input into a large language model to obtain the strategic constraints output by the large language model. These strategic constraints may include at least one of the following: task completion time constraint, rescue coverage constraint, minimum success level constraint, organizational response constraint, and safety compliance constraint. For example, the correspondence between each system capability and strategic constraint is shown in Table 1. Then, by establishing the correspondence between mission objectives, system capabilities, and strategic constraints, the strategic layer can be constructed.

[0060] Table 1

[0061] In this embodiment of the invention, an abstract mission objective is decomposed into specific system capabilities through a systematic strategic layer construction method, and quantifiable strategic constraints are set for each system capability, thereby realizing a structured transformation from mission objective to system capability and reducing reliance on human experience.

[0062] In one embodiment, determining the operational layer based on the mission architecture generation elements and the strategy layer includes: Based on the task scenario, determine the operational activities corresponding to the emergency rescue task; Based on the effectiveness indicators in the system indicators, the system capabilities corresponding to the strategic layer, and the task scenarios, the operational constraints corresponding to the operational activities are determined; the effectiveness indicators are used to quantify the effectiveness of the operational activities. The operating layer is determined based on the operating activities and the operating constraints.

[0063] Specifically, the task scenario is divided into scenario segments corresponding to different stages. All scenario segments are input into a large language model. The large language model generates the operational activities required to complete the emergency rescue task in each scenario segment based on the task stage, input objects, output objects, and activity triggering conditions corresponding to the scenario segment. It also determines the logical relationships between these operational activities, which can include execution sequence relationships or information interaction relationships (i.e., communication relationships). The execution sequence relationship can include preconditions, successors, parallel relationships, or cyclical relationships between operational activities. For example, in a tunnel collapse rescue scenario, operational activities could include: information reporting, initiating emergency response, command and dispatch, on-site monitoring and risk assessment, road repair, rescue and medical assistance. Figure 2 This is a schematic diagram of the mission thread provided in an embodiment of the present invention. The logical relationship between running activities (i.e., mission threads) is as follows: Figure 2 As shown in Table 2, the identified operational activities are then mapped to system capabilities at the strategic level, with each system capability corresponding to at least one operational activity.

[0064] Table 2

[0065] Next, the performance indicators, strategic constraints corresponding to each system capability, and environmental conditions and time constraints corresponding to the task scenarios are input into the large language model. The large language model then maps the input data to each operational activity, determining the operational constraints (i.e., quantification standards) for each activity. These operational constraints can include at least one of the following: activity start time constraint, activity completion time constraint, activity sequence constraint, activity coverage constraint, activity execution frequency constraint, and activity coordination constraint. Based on each operational activity and its constraints, the relationships between operational activities, operational constraints, and the correspondence between operational activities and system capabilities are determined, thus constructing the operational layer. For example, the mapping relationship between operational activities and operational constraints is shown in Table 3.

[0066] Table 3

[0067] In this embodiment of the invention, the system capabilities of the strategic layer are transformed into an executable sequence of operational activities, and quantitative standards are set for each operational activity, providing precise input for the simulation execution logic of subsequent simulation experiments.

[0068] In one embodiment, determining the resource layer based on the mission architecture generation elements and the runtime layer includes: Based on the running activities and running constraints corresponding to the running layer, determine the resource objects corresponding to the running activities; Based on the performance indicators in the system indicators, the equipment technical parameters corresponding to the resource object, and the operational constraints, the resource constraints are determined; the performance indicators are used to quantify the support capability of the resource object for the operational activities. The resource layer is determined based on the running activity, the resource object, and the resource constraints.

[0069] Specifically, a preset resource object library is obtained. This library includes preset activities, preset constraints, and the relationships between preset resource objects. Based on the running activities and constraints, resource objects required to complete each running activity according to the running constraints are matched from this preset resource object library. These resource objects may include the rescue forces executing the running activities, the equipment and facilities used by the rescue forces, and supporting resources. For example, in a tunnel collapse rescue scenario, resource objects include professional rescue teams, road repair teams, medical rescue teams, communication technology equipment, drones, life detectors, drilling rigs, and ambulances and medical equipment, etc. Then, the running activities are mapped to the resource objects. The mapping relationship between running activities and resource objects is shown in Table 4.

[0070] Table 4

[0071] Next, performance indicators, operational constraints corresponding to each operational activity, and equipment technical parameters of each resource object are mapped to the resource objects to determine the resource constraints (i.e., performance requirements) corresponding to each resource object. These resource constraints include at least one of the following: resource quantity constraints, resource performance constraints, resource availability constraints, resource deployment location constraints, resource scheduling range constraints, and resource coordination constraints. Then, based on the operational activities, resource objects, and resource constraints, the correspondence between resource objects, resource attributes, resource constraints, operational activities, and resource objects is determined, thus constructing the resource layer. For example, the mapping relationship between resource objects and resource constraints is shown in Table 5.

[0072] Table 5

[0073] In one embodiment, based on the emergency response mission architecture, multiple operational scenarios to be evaluated are identified, including: Determine the executor corresponding to the running activity in the emergency rescue mission architecture, and the resource configuration parameters corresponding to the executor; Based on the resource constraints in the emergency rescue mission architecture and the equipment technical parameters, the resource parameters corresponding to the resource object are determined; Based on the executor, the resource configuration parameters, and the resource parameters, a baseline operation plan is determined; Based on the baseline operating plan, at least one alternative operating plan is determined; The baseline operating plan and all alternative operating plans are identified as the multiple operating plans to be evaluated.

[0074] Specifically, based on the mapping relationship between runtime activities and resource objects in the resource layer, the executor for each runtime activity is determined. For example, the mapping relationship between runtime activities and executors is shown in Table 6.

[0075] Table 6

[0076] Next, based on the organization type, scope of responsibility, response time, and schedulable resources corresponding to the executor, the resource configuration parameters for each executor are determined. These resource configuration parameters may include resource type and resource quantity. For example, the resource configuration parameters for each executor are shown in Table 7.

[0077] Table 7

[0078] Subsequently, based on resource constraints and equipment technical parameters, the resource parameters (i.e. performance parameters) corresponding to each resource object in the resource configuration parameters are determined. These resource parameters may include at least one of the following: resource type, resource quantity, resource location, resource capability, resource availability time, and resource service range. For example, the resource parameters corresponding to the resource objects are shown in Table 8.

[0079] Table 8

[0080] Subsequently, by combining the executor, resource configuration parameters, and resource parameters, a baseline operating plan that satisfies strategic, operational, and resource constraints is obtained. Based on this baseline operating plan, parameter adjustments yield at least one alternative operating plan, reflecting different optimization directions based on the baseline. This baseline operating plan and all alternative operating plans constitute multiple operating plans to be evaluated.

[0081] In one embodiment, determining at least one alternative operating scheme based on the baseline operating scheme includes: Randomly adjust at least one of the resource configuration parameters, resource parameters, and activity execution parameters in the baseline operation plan to obtain at least one alternative operation plan.

[0082] Specifically, based on the baseline operation plan, key parameters within the baseline operation plan are identified. These key parameters may include at least one of resource configuration parameters, resource parameters, and activity execution parameters. Resource configuration parameters may include resource type and quantity, resource deployment location, and resource scheduling order. Activity execution parameters may include the executor, activity execution order, and coordination method. For example, resource configuration parameters may include resource quantity parameters such as the number of professional rescue teams, road repair teams, medical rescue teams, drones, drilling rigs, and ambulances. Resource parameters may include resource performance parameters such as drone endurance, life detector detection range, drilling rig drilling speed, excavator obstacle clearing efficiency, and communication system transmission latency. Activity execution parameters may include information reporting time, force dispatch time, search time, and medical transport time.

[0083] Next, determine the parameter adjustment range corresponding to the key parameter. For example, the parameter adjustment range corresponding to this key parameter is shown in Table 9.

[0084] Table 9

[0085] At least one key parameter is randomly selected and randomly adjusted within its adjustment range to obtain at least one candidate operating scheme. Each candidate operating scheme, strategic constraint, operational constraint, and resource constraint are input into a large language model. The large language model performs constraint verification on each candidate operating scheme, and the candidate operating schemes that satisfy the strategic constraint, operational constraint, and resource constraint are determined as alternative operating schemes.

[0086] For example, several operational scenarios to be evaluated are shown in Table 10. In Table 10, operational scenario A is the baseline operational scenario, and operational scenarios B1 to F are alternative operational scenarios. "√" indicates that the corresponding key parameters in the baseline operational scenario have been adjusted. That is, "√" indicates that the key parameters corresponding to the alternative operational scenario are different from those in the baseline operational scenario.

[0087] Table 10

[0088] It should be noted that after constructing the emergency rescue mission architecture using UAF, each layer is displayed in diagram form. The strategy layer includes a strategic motivation diagram, a strategic structure diagram, a strategic connection diagram, and a strategic constraint diagram. The strategic motivation diagram represents strategic objectives, the strategic structure diagram represents the system capability structure, the strategic connection diagram represents the dependencies between system capabilities, and the strategic constraint diagram quantifies the strategic constraints corresponding to system capabilities. The operation layer includes an operation classification diagram, an operation connection diagram, an operation flow diagram, an operation state diagram, and an operation constraint diagram. The operation classification diagram represents the operation executor architecture, the operation connection diagram represents the information interaction relationships between operation executors, the operation flow diagram represents the correspondence between operation activities, operation executors, and operation logic, the operation state diagram represents the state machine of the operation executors, and the operation constraint diagram represents the operation constraints corresponding to the operation executors. The resource layer includes a resource structure diagram and a resource constraint diagram. The resource structure diagram represents the resource object architecture, and the resource constraint diagram represents resource constraints.

[0089] In one embodiment, simulating the multiple operating schemes to be evaluated to obtain simulation results for each operating scheme to be evaluated includes: For each of the proposed operational schemes to be evaluated, a simulation scenario model and a simulation environment agent are determined based on the task scenario. Based on the operational layer and the resource layer, the task agent corresponding to the executor, the agent state and agent attribute parameters corresponding to the task agent and the simulation environment agent, and the simulation operational mechanism between the task agent and the simulation environment agent are determined. The simulation operational mechanism is executed to perform Monte Carlo simulation on the proposed operational scheme to be evaluated, and the simulation results corresponding to the proposed operational scheme are obtained.

[0090] Specifically, for each operational plan to be evaluated, environmental elements in the task scenario are extracted based on the background environment map. These environmental elements may include disaster type, geographical environment, road network, distribution of rescue points, and deployment locations of rescue forces. Then, a simulation scenario model and corresponding simulation environment agents are constructed based on these environmental elements. For example, for a tunnel collapse rescue scenario, the simulation scenario model may include objects such as the disaster area, road network, road interruption points, rescue points, and rescue center. The simulation environment agents may include a disaster agent, a road interruption point agent, a rescue point agent, and a trapped personnel agent.

[0091] after, Figure 3 This is a schematic diagram illustrating the construction of a task agent provided in an embodiment of the present invention, such as... Figure 3As shown, a task agent is established based on the operation classification diagram, operation connection diagram, operation flow diagram, operation state diagram, and operation constraint diagram in the operation layer, as well as the resource structure diagram and resource constraint diagram in the resource layer. Specifically, this includes: identifying the executors of the operation based on the operation classification diagram and resource structure diagram, and determining the corresponding Agent type. For example, executors include professional rescue teams, road repair teams, medical rescue teams, and emergency command organizations. Secondly, an Agent state machine is established based on the operation state diagram, including operational states such as standby, maneuver, search, disaster relief, road repair, and medical rescue. Then, Agent attribute parameters are established based on the operation constraint diagram and resource constraint diagram. These parameters may include information reporting time, force dispatch time, UAV endurance time, life detector detection distance, drilling speed, and communication system transmission latency. Finally, Agent behavioral logic and state transition relationships are established based on the operation flow diagram, enabling the task agent to execute operational activities according to the mission thread. Furthermore, by referring to the construction of the agent state, agent attribute parameters, agent behavioral logic, and state transition relationships of the task agent, it is also possible to construct the agent state, agent attribute parameters, agent behavioral logic, and state transition relationships of the simulation environment agent, as well as the simulation operation mechanism between the simulation environment agent and the task agent. This simulation operation mechanism is used to characterize the interaction process and state evolution process of various agents in the task scenario. For example, this simulation operation mechanism may include disaster triggering mechanism, information reporting mechanism, force dispatching mechanism, road clearing mechanism, search and rescue mechanism, medical rescue mechanism, and secondary disaster impact mechanism.

[0092] Then, the simulation mechanism is executed, allowing various agents to jointly simulate the execution process of emergency rescue missions through event triggering, information transmission, state transitions, and spatial movement. For example, Figure 4 This is a flowchart illustrating the simulation operation mechanism provided in this embodiment of the invention, as shown below. Figure 4As shown, the Disaster Agent, acting as the starting point of the mission, sends out a disaster signal at the beginning of the simulation. Upon receiving the disaster signal, the Road Disruption Point Agent and the Rescue Point Agent transition from normal to emergency status. The Road Disruption Point Agent reduces the movement speed of nearby agents, and once discovered, the nearest road repair team Agent will carry out repairs. The Rescue Point Agent first reports the emergency information and then sends a distress signal to nearby rescue forces. Workers within the Rescue Point Agent, upon receiving the earthquake signal, will deviate from their normal state and enter, according to probability, states of escape, uninjured, slightly injured, seriously injured, or dead. Those trapped in the uninjured, slightly injured, or seriously injured states will enter the corresponding rescue state upon rescue; if they remain unrescued for an extended period, they will enter the next trapped state, until they reach the dead state. Search and rescue team agents, including emergency rescue personnel agents, rescue equipment agents, local rescue team agents, and medical rescue agents, will proceed to the area of ​​the area awaiting rescue after receiving a distress signal from the agent at the point of need. After a period of preparation, they will proceed to conduct rescue operations. If there are still trapped individuals in the nearby area after the initial rescue, they will provide support. If no further rescue information is received within a certain period, they will return to their base. Road repair team agents, upon receiving a road interruption repair signal from the agent, will proceed to the nearest known road interruption area to carry out repair work. To avoid resource waste, if the number of repair teams in a road interruption area exceeds the limit, the road repair team agent will return to normal and wait for other road interruptions to be discovered. After successfully repairing a road interruption, if there are still unrepaired road interruptions, the road repair team agent will proceed to repair them; if no further information is received within a certain period, they will return to their base. During the simulation, secondary disaster events such as landslides and rockfalls will be triggered based on the probability of secondary disasters occurring. These events will, according to probability, lead to new road interruptions, an increase in the number of trapped individuals, or a reduction in rescue efficiency, thus affecting the progress of the rescue mission.

[0093] Monte Carlo simulations were performed for each operational plan to be evaluated. During each simulation, scenario elements such as the disaster location, distribution of rescue points, number of trapped personnel, and road closures were randomly generated to simulate the emergency rescue mission execution process under different disaster scenarios. Through repeated simulations, simulation results for each operational plan under different scenario conditions were obtained. These simulation results can include the number of new deaths, total rescue time, road reopening time, search completion time, number of trapped personnel rescued, number of injured transferred, and resource utilization.

[0094] In one embodiment, determining the final operating scheme based on all simulation results includes: For each of the proposed operational schemes to be evaluated, based on the simulation results corresponding to the proposed operational scheme, the performance index value corresponding to the proposed operational scheme is determined; based on the performance index value corresponding to the proposed operational scheme, the effectiveness index value corresponding to the proposed operational scheme is determined; based on the effectiveness index value corresponding to the proposed operational scheme, the success index value corresponding to the proposed operational scheme is determined; and candidate operational schemes that meet the constraints are determined from all proposed operational schemes to be evaluated; the constraints are that the success index value meets the strategic constraints. The candidate running scheme corresponding to the highest success index value is determined as the final running scheme.

[0095] Specifically, after determining the simulation results for each operational plan to be evaluated, the performance index values ​​are determined based on the simulation structure. These performance index values ​​are then weighted and summed to obtain the effectiveness index value. This effectiveness index value is then weighted and summed again to obtain the success index value, which reflects the final achievement of the mission objective. This success index value is compared with the strategic constraints of the operational plan to be evaluated. If the success index value meets the strategic constraints, it indicates that the success index value satisfies the constraints, and the operational plan to be evaluated can be identified as a candidate operational plan. If the success index value does not meet the strategic constraints, the key parameters are randomly adjusted, and the simulation is repeated. Repeating the above operations allows candidate operational plans to be identified from all operational plans to be evaluated. The success index values ​​corresponding to all candidate operational plans are then sorted in descending order, and the candidate operational plan with the highest success index value is determined as the final operational plan.

[0096] In one embodiment, updating the emergency rescue mission architecture based on the simulation results corresponding to the final operating scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue mission includes: Based on the simulation results corresponding to the final operation scheme, at least one of the strategic constraints, operational constraints, and resource constraints in the emergency rescue mission architecture is updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0097] Specifically, after determining the final operational plan, activity execution parameters, resource configuration parameters, and resource parameters are extracted from the simulation results of the final operational plan. Operational constraints are updated using the activity execution parameters, resource constraints are updated using the resource configuration parameters and resource parameters, and strategic constraints are updated based on the success index values, resulting in the updated emergency rescue system requirements for completing the emergency rescue mission. For example, taking a tunnel collapse rescue scenario as an example, the operational constraints for the information reporting activity in the baseline operational plan are: disaster information reporting time ≤ 30 minutes, 2 professional rescue teams, and 2 drones. Monte Carlo simulation analysis shows that when the information reporting time is shortened to 15 minutes, the number of professional rescue teams increases to 3, and the number of drones increases to 3, the 72-hour rescue rate of trapped personnel meets the strategic constraints, and the number of new deaths and total rescue time reach the expected goals. Therefore, the requirement that the disaster information reporting time be ≤15 minutes is updated to the operational constraint, and the requirement that the number of professional rescue teams be ≥3 and the number of drones be ≥3 is updated to the resource constraint. This forms an emergency rescue mission architecture consistent with the final operational plan and its corresponding emergency rescue system requirements. These emergency rescue system requirements include at least the strategic constraints, operational constraints, and resource constraints in the updated emergency rescue mission architecture, providing a basis for the planning, construction, resource allocation, and capacity building of the emergency rescue system.

[0098] It should be noted that at least one of the strategic constraints, operational constraints, and resource constraints in the emergency rescue mission architecture can be updated, but this embodiment of the invention does not limit this.

[0099] The emergency rescue system requirement determination device provided by the present invention is described below. The emergency rescue system requirement determination device described below and the emergency rescue system requirement determination method described above can be referred to in correspondence.

[0100] This invention also provides an emergency rescue system requirements determination device. Figure 5 This is a schematic diagram of the emergency rescue system demand determination device provided in an embodiment of the present invention, as shown below. Figure 5 As shown, the emergency rescue system demand determination device 500 includes: a first determination module 510, a second determination module 520, a simulation module 530, and an update module 540.

[0101] The first determining module 510 is used to determine the emergency rescue mission architecture corresponding to the emergency rescue mission based on the emergency rescue mission input data; the emergency rescue mission architecture is used to characterize the relationship between mission objectives, operational activities, operators and resource elements in the complete process of executing the emergency rescue mission.

[0102] The second determining module 520 is used to determine multiple operational schemes to be evaluated based on the emergency rescue mission architecture.

[0103] The simulation module 530 is used to simulate the various operating schemes to be evaluated, obtain the simulation results corresponding to each operating scheme to be evaluated, and determine the final operating scheme based on all simulation results.

[0104] The update module 540 is used to update the emergency rescue mission architecture based on the simulation results corresponding to the final operation scheme, so as to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0105] The emergency rescue system requirements determination device provided in this invention determines the emergency rescue mission architecture based on emergency rescue mission input data, identifies multiple operational schemes to be evaluated based on the emergency rescue mission architecture, simulates these multiple operational schemes, determines the final operational scheme, and updates the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme, thereby obtaining the emergency rescue system requirements corresponding to the emergency rescue task. In this invention, the emergency rescue mission architecture is used to characterize the relationships between mission objectives, operational activities, executors, and resource elements throughout the complete process of an emergency rescue task. It establishes a precise and traceable structured logical link between strategic objectives and specific execution resources, solving problems such as lack of systematicity and misalignment of emergency subjects caused by decentralized departmental management. By determining multiple operational schemes to be evaluated through the emergency rescue mission architecture, reliance on human experience is reduced. The final operational scheme is determined through simulation of multiple operational schemes and evaluation of simulation results, ensuring that the selection of the final operational scheme is supported by objective data and avoiding insufficient scientific rigor due to subjective judgment.

[0106] Optionally, the emergency rescue mission architecture includes a strategic layer, an operational layer, and a resource layer.

[0107] Optionally, the first determining module 510 is specifically used for: Based on the emergency rescue mission input data, determine the mission architecture generation elements corresponding to the emergency rescue mission; Based on the mission architecture generation elements and the emergency rescue mission input data, the strategic layer is determined; the strategic layer is used to characterize the relationship between mission objectives, system capabilities, and strategic constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the strategy layer, the operation layer is determined; the operation layer is used to characterize the relationship between the operational activities and operational constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the operation layer, the resource layer is determined; the resource layer is used to characterize the relationship between the operation activities, resource objects, and resource constraints corresponding to the execution of the emergency rescue mission. Based on the system indicators in the mission architecture generation elements, the relationship between the strategic layer, the operational layer, and the resource layer is established to construct the emergency rescue mission architecture.

[0108] Optionally, the mission architecture generation elements include: emergency rescue mission, mission objectives, core issues, mission background, mission scenario, and system indicators.

[0109] Optionally, the first determining module 510 is specifically used for: The emergency rescue mission is determined based on the mission text data in the emergency rescue mission input data; Based on the aforementioned emergency rescue mission, the mission objectives corresponding to the emergency rescue mission framework are determined; Based on the emergency rescue mission, the mission objectives, and the system construction status data in the emergency rescue mission input data, the core issues are identified; the core issues are used to characterize the different needs corresponding to completing the emergency rescue mission. Based on the emergency rescue mission, the mission objective, the core issue, and the emergency rescue mission input data, the mission background is determined; the mission background is used to characterize the scenario environment and constraints corresponding to the execution of the emergency rescue mission. Based on the aforementioned mission background, the mission scenario corresponding to the emergency rescue mission is determined; the mission scenario is used to characterize the mission execution environment corresponding to the emergency rescue mission. Based on the stated mission objectives and the stated core issues, the system indicators are determined.

[0110] Optionally, the first determining module 510 is specifically used for: Based on the mission objectives and the mission background, determine the system capabilities corresponding to the emergency rescue mission; Based on the mission scenario, the emergency rescue-related systems in the emergency rescue mission input data, and the success indicators in the system indicators, the strategic constraints are determined; the success indicators are used to quantify the final achievement of the mission objectives. The strategic layer is determined based on the stated mission objectives, system capabilities, and strategic constraints.

[0111] Optionally, the first determining module 510 is specifically used for: Based on the task scenario, determine the operational activities corresponding to the emergency rescue task; Based on the effectiveness indicators in the system indicators, the system capabilities corresponding to the strategic layer, and the task scenarios, the operational constraints corresponding to the operational activities are determined; the effectiveness indicators are used to quantify the effectiveness of the operational activities. The operating layer is determined based on the operating activities and the operating constraints.

[0112] Optionally, the first determining module 510 is specifically used for: Based on the running activities and running constraints corresponding to the running layer, determine the resource objects corresponding to the running activities to be executed; Based on the performance indicators in the system indicators, the equipment technical parameters corresponding to the resource object, and the operational constraints, the resource constraints are determined; the performance indicators are used to quantify the support capability of the resource object for the operational activities. The resource layer is determined based on the running activity, the resource object, and the resource constraints.

[0113] Optionally, the second determining module 520 is specifically used for: Determine the executor corresponding to the running activity in the emergency rescue mission architecture, and the resource configuration parameters corresponding to the executor; Based on the resource constraints in the emergency rescue mission architecture and the equipment technical parameters, the resource parameters corresponding to the resource object are determined; Based on the executor, the resource configuration parameters, and the resource parameters, a baseline operation plan is determined; Based on the baseline operating plan, at least one alternative operating plan is determined; The baseline operating plan and all alternative operating plans are identified as the multiple operating plans to be evaluated.

[0114] Optionally, the second determining module 520 is specifically used for: Randomly adjust at least one of the resource configuration parameters, resource parameters, and activity execution parameters in the baseline operation plan to obtain at least one alternative operation plan.

[0115] Optionally, the simulation module 530 is specifically used for: For each of the proposed operational schemes to be evaluated, a simulation scenario model and a simulation environment agent are determined based on the task scenario. Based on the operational layer and the resource layer, the task agent corresponding to the executor, the agent state and agent attribute parameters corresponding to the task agent and the simulation environment agent, and the simulation operational mechanism between the task agent and the simulation environment agent are determined. The simulation operational mechanism is executed to perform Monte Carlo simulation on the proposed operational scheme to be evaluated, and the simulation results corresponding to the proposed operational scheme are obtained.

[0116] Optionally, the simulation module 530 is specifically used for: For each of the proposed operational schemes to be evaluated, based on the simulation results corresponding to the proposed operational scheme, the performance index value corresponding to the proposed operational scheme is determined; based on the performance index value corresponding to the proposed operational scheme, the effectiveness index value corresponding to the proposed operational scheme is determined; based on the effectiveness index value corresponding to the proposed operational scheme, the success index value corresponding to the proposed operational scheme is determined; and candidate operational schemes that meet the constraints are determined from all proposed operational schemes to be evaluated; the constraints are that the success index value meets the strategic constraints. The candidate running scheme corresponding to the highest success index value is determined as the final running scheme.

[0117] Optionally, update module 540, specifically for: Based on the simulation results corresponding to the final operation scheme, the strategic constraints, operational constraints, and resource constraints in the emergency rescue mission architecture are updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

[0118] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiment of the present invention, such as... Figure 6 As shown, the electronic device may include a processor 610, a communications interface 620, a memory 630, and a communication bus 640, wherein the processor 610, communications interface 620, and memory 630 communicate with each other via the communication bus 640. The processor 610 can call logical instructions in the memory 630 to execute an emergency rescue system requirements determination method. This method includes: determining an emergency rescue mission architecture corresponding to an emergency rescue task based on emergency rescue mission input data; the emergency rescue mission architecture characterizes the relationships between mission objectives, operational activities, executors, and resource elements during the complete execution of the emergency rescue task; determining multiple operational schemes to be evaluated based on the emergency rescue mission architecture; simulating the multiple operational schemes to be evaluated to obtain simulation results for each operational scheme, and determining a final operational scheme based on all simulation results; updating the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue task.

[0119] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0120] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the emergency rescue system requirement determination method provided by the above methods. The method includes: determining an emergency rescue mission architecture corresponding to an emergency rescue task based on emergency rescue mission input data; the emergency rescue mission architecture is used to characterize the relationship between mission objectives, operational activities, operators, and resource elements during the complete execution of the emergency rescue task; determining multiple operational schemes to be evaluated based on the emergency rescue mission architecture; simulating the multiple operational schemes to be evaluated to obtain simulation results corresponding to each operational scheme to be evaluated, and determining a final operational scheme based on all simulation results; updating the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue task.

[0121] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the emergency rescue system requirement determination method provided by the above methods. This method includes: determining an emergency rescue mission architecture corresponding to an emergency rescue task based on emergency rescue mission input data; the emergency rescue mission architecture characterizes the relationships between mission objectives, operational activities, operators, and resource elements during the complete execution of the emergency rescue task; determining multiple operational schemes to be evaluated based on the emergency rescue mission architecture; simulating the multiple operational schemes to be evaluated to obtain simulation results corresponding to each operational scheme, and determining a final operational scheme based on all simulation results; updating the emergency rescue mission architecture based on the simulation results corresponding to the final operational scheme to obtain the emergency rescue system requirements corresponding to the emergency rescue task.

[0122] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0123] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0124] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for determining the needs of an emergency rescue system, characterized in that, include: Based on the emergency rescue mission input data, determine the emergency rescue mission architecture corresponding to the emergency rescue task; The emergency rescue mission architecture is used to characterize the relationships between mission objectives, operational activities, operators, and resource elements during the entire process of executing the emergency rescue mission. Based on the aforementioned emergency rescue mission framework, several operational plans were identified for evaluation. Simulations are performed on the various operational schemes to be evaluated to obtain simulation results for each operational scheme to be evaluated. Based on all simulation results, the final operational scheme is determined. Based on the simulation results corresponding to the final operation scheme, the emergency rescue mission architecture is updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

2. The method for determining the needs of an emergency rescue system according to claim 1, characterized in that, The emergency rescue mission architecture includes a strategic layer, an operational layer, and a resource layer; The process of determining the emergency rescue mission architecture corresponding to the emergency rescue task based on the emergency rescue mission input data includes: Based on the emergency rescue mission input data, determine the mission architecture generation elements corresponding to the emergency rescue mission; Based on the mission architecture generation elements and the emergency rescue mission input data, the strategic layer is determined; the strategic layer is used to characterize the relationship between mission objectives, system capabilities, and strategic constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the strategy layer, the operation layer is determined; the operation layer is used to characterize the relationship between the operational activities and operational constraints corresponding to the execution of the emergency rescue mission. Based on the mission architecture generation elements and the operation layer, the resource layer is determined; the resource layer is used to characterize the relationship between the operation activities, resource objects, and resource constraints corresponding to the execution of the emergency rescue mission. Based on the system indicators in the mission architecture generation elements, the relationship between the strategic layer, the operational layer, and the resource layer is established to construct the emergency rescue mission architecture.

3. The method for determining the needs of an emergency rescue system according to claim 2, characterized in that, The mission architecture generation elements include: emergency rescue mission, mission objectives, core issues, mission background, mission scenario, and system indicators; The process of determining the mission architecture generation elements corresponding to the emergency rescue mission based on the emergency rescue mission input data includes: The emergency rescue mission is determined based on the mission text data in the emergency rescue mission input data; Based on the aforementioned emergency rescue mission, the mission objectives corresponding to the emergency rescue mission framework are determined; Based on the emergency rescue mission, the mission objectives, and the system construction status data in the emergency rescue mission input data, the core issues are identified; the core issues are used to characterize the different needs corresponding to completing the emergency rescue mission. Based on the emergency rescue mission, the mission objective, the core issue, and the emergency rescue mission input data, the mission background is determined; the mission background is used to characterize the scenario environment and constraints corresponding to the execution of the emergency rescue mission. Based on the aforementioned mission background, the mission scenario corresponding to the emergency rescue mission is determined; the mission scenario is used to characterize the mission execution environment corresponding to the emergency rescue mission. Based on the stated mission objectives and the stated core issues, the system indicators are determined.

4. The method for determining the needs of an emergency rescue system according to claim 3, characterized in that, The determination of the strategic layer based on the mission architecture generation elements and the emergency rescue mission input data includes: Based on the mission objectives and the mission background, determine the system capabilities corresponding to the emergency rescue mission; Based on the mission scenario, the emergency rescue-related systems in the emergency rescue mission input data, and the success indicators in the system indicators, the strategic constraints are determined; the success indicators are used to quantify the final achievement of the mission objectives. The strategic layer is determined based on the stated mission objectives, system capabilities, and strategic constraints.

5. The method for determining the needs of an emergency rescue system according to claim 3, characterized in that, The determination of the operational layer based on the mission architecture generation elements and the strategic layer includes: Based on the task scenario, determine the operational activities corresponding to the emergency rescue task; Based on the effectiveness indicators in the system indicators, the system capabilities corresponding to the strategic layer, and the task scenarios, the operational constraints corresponding to the operational activities are determined; the effectiveness indicators are used to quantify the effectiveness of the operational activities. The operating layer is determined based on the operating activities and the operating constraints.

6. The method for determining the needs of an emergency rescue system according to claim 3, characterized in that, The determination of the resource layer based on the mission architecture generation elements and the runtime layer includes: Based on the running activities and running constraints corresponding to the running layer, determine the resource objects corresponding to the running activities; Based on the performance indicators in the system indicators, the equipment technical parameters corresponding to the resource object, and the operational constraints, the resource constraints are determined; the performance indicators are used to quantify the support capability of the resource object for the operational activities. The resource layer is determined based on the running activity, the resource object, and the resource constraints.

7. The method for determining the needs of an emergency rescue system according to claim 6, characterized in that, Based on the aforementioned emergency rescue mission architecture, several operational plans to be evaluated are identified, including: Determine the executor corresponding to the running activity in the emergency rescue mission architecture, and the resource configuration parameters corresponding to the executor; Based on the resource constraints in the emergency rescue mission architecture and the equipment technical parameters, the resource parameters corresponding to the resource object are determined; Based on the executor, the resource configuration parameters, and the resource parameters, a baseline operation plan is determined; Based on the baseline operating plan, at least one alternative operating plan is determined; The baseline operating plan and all alternative operating plans are identified as the multiple operating plans to be evaluated.

8. The method for determining the needs of an emergency rescue system according to claim 7, characterized in that, The step of determining at least one alternative operating plan based on the baseline operating plan includes: Randomly adjust at least one of the resource configuration parameters, resource parameters, and activity execution parameters in the baseline operation plan to obtain at least one alternative operation plan.

9. The method for determining the needs of an emergency rescue system according to claim 3, characterized in that, The simulation of the various operational schemes to be evaluated, and the resulting simulation results for each scheme, include: For each of the proposed operational schemes to be evaluated, a simulation scenario model and a simulation environment agent are determined based on the task scenario. Based on the operational layer and the resource layer, the task agent corresponding to the executor, the agent state and agent attribute parameters corresponding to the task agent and the simulation environment agent, and the simulation operational mechanism between the task agent and the simulation environment agent are determined. The simulation operational mechanism is executed to perform Monte Carlo simulation on the proposed operational scheme to be evaluated, and the simulation results corresponding to the proposed operational scheme are obtained.

10. The method for determining the needs of an emergency rescue system according to claim 1, characterized in that, The process of determining the final operating plan based on all simulation results includes: For each of the proposed operational schemes to be evaluated, based on the simulation results corresponding to the proposed operational scheme, the performance index value corresponding to the proposed operational scheme is determined; based on the performance index value corresponding to the proposed operational scheme, the effectiveness index value corresponding to the proposed operational scheme is determined; based on the effectiveness index value corresponding to the proposed operational scheme, the success index value corresponding to the proposed operational scheme is determined; and candidate operational schemes that meet the constraints are determined from all proposed operational schemes to be evaluated; the constraints are that the success index value meets the strategic constraints. The candidate running scheme corresponding to the highest success index value is determined as the final running scheme.

11. The method for determining the needs of an emergency rescue system according to claim 1, characterized in that, The process of updating the emergency rescue mission architecture based on the simulation results corresponding to the final operating scheme, and obtaining the emergency rescue system requirements corresponding to the emergency rescue mission, includes: Based on the simulation results corresponding to the final operation scheme, the strategic constraints, operational constraints, and resource constraints in the emergency rescue mission architecture are updated to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.

12. A device for determining the needs of an emergency rescue system, characterized in that, include: The first determination module is used to determine the emergency rescue mission architecture corresponding to the emergency rescue mission based on the emergency rescue mission input data; The emergency rescue mission architecture is used to characterize the relationships between mission objectives, operational activities, operators, and resource elements during the entire process of executing the emergency rescue mission. The second determining module is used to determine multiple operational schemes to be evaluated based on the emergency rescue mission architecture. The simulation module is used to simulate the various operating schemes to be evaluated, obtain the simulation results corresponding to each operating scheme to be evaluated, and determine the final operating scheme based on all simulation results. The update module is used to update the emergency rescue mission architecture based on the simulation results corresponding to the final operation scheme, so as to obtain the emergency rescue system requirements corresponding to the emergency rescue mission.