Ontology-based emergency handling scene modeling tool construction method

Abstract

The invention discloses an ontology-based emergency handling scenario modeling tool construction method, which is characterized in that an emergency type management module, an event element management module and an event scenario model construction module are included, and the emergency type management module is electrically connected with the event element management module; the event element management module is electrically connected with the event scene model construction module; the event element management module comprises an entity model management module, a behavior model management module and a relation management module, and the entity model management module is electrically connected with the behavior model management module. According to the ontology-based emergency event handling scene modeling tool construction method, rapid compilation of various event elements and behavior strategies involved in different event scenes can be supported according to event types and properties, and an event scene description model is formed.

Description

Technical Field

[0001] The present invention relates to the field of artificial intelligence technology, and in particular to a method for constructing an ontology-based emergency event handling scenario modeling tool. Background Art

[0002] In the process of handling emergencies such as natural disasters, maritime rescue, and social crises, the complexity of business scenarios, the variability of event elements, and the diversity of handling strategies pose major challenges. Emergency handling is inseparable from event digital scenario modeling, which is used to describe: which entities appear in the event scenario, how they participate in the evolution of the event; what behaviors occur in the scenario, and whether these behaviors have temporal and spatial correlations. To this end, the command organization urgently needs an event scenario modeling tool that can convert expert experience or historical data into a typical event scenario model. After an emergency occurs, it can extract key entities, behaviors, and handling strategies from various text-based event data such as real-time situation data and trend briefings, build an event handling digital space, and support the generation of emergency handling capabilities based on event scenario models.

[0003] Therefore, the present invention provides an ontology-based emergency response scenario modeling tool and its application method. By describing the entity knowledge, behavioral knowledge, and decision-making knowledge involved in the emergency through the ontology, it can support the rapid allocation of various event elements and behavioral strategies involved in different event scenarios according to the type and nature of the event, thereby forming an event scenario description model. Summary of the invention

[0004] To achieve the above objectives, the present invention is implemented through the following technical solutions: a method for constructing an emergency event handling scenario modeling tool based on ontology, characterized in that it includes an emergency event type management module, an event element management module and an event scenario model construction module, wherein the emergency event type management module is electrically connected to the event element management module, and the event element management module is electrically connected to the event scenario model construction module; The event element management module includes an entity model management module, a behavior model management module and a relationship management module, wherein the entity model management module is electrically connected to the behavior model management module, and the behavior model management module is electrically connected to the relationship management module; The event scenario model construction module includes a scenario entity element module, a scenario behavior module and a disposal association module. The scenario entity element module is electrically connected to the scenario behavior module, and the scenario behavior module is electrically connected to the disposal association module.

[0005] Preferably, the emergency event type management module defines two levels of event types: domain events and subject events, to achieve classification and management of emergency events.

[0006] Preferably, the event element management module classifies and manages event entity models, behavior models, relationship models, etc. such as people, equipment, objects, and environment involved in domain events according to the ontology system to support event scenario construction.

[0007] Preferably, the event scenario model construction module adopts a "building blocks" approach to drag basic models such as event entity elements, behavior elements, relationship models, etc. from the event element management module to the event scenario customization panel to complete the construction of the theme event scenario.

[0008] Preferably, the entity model management function is carefully classified and managed through an entity classification table to meet the needs of building scenarios for different subject events, and each entity column contains several entity models.

[0009] Preferably, the behavior model management module is a subordinate event module of the theme event, which is various behaviors or strategies involved in the theme event.

[0010] Preferably, the relationship management module is used to identify and express potential semantic connections between entities in a scenario, providing key information for in-depth understanding and analysis of event scenarios.

[0011] Preferably, the scenario entity element module selects entity blocks from the entity model list of the entity model management module by dragging and dropping to embed the entity element module in the scenario customization panel, and configures entity classification nodes according to scenario requirements.

[0012] Preferably, the situational behavior module has two classification nodes: target behavior and disposal behavior.

[0013] Preferably, the handling association module is selectively configured with behavior and entity models by business experts. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a schematic diagram of the ontology-based emergency handling scenario modeling tool of the present invention. DETAILED DESCRIPTION

[0015] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0016] See also Figure 1 The present invention provides a technical solution: an ontology-based emergency response scenario modeling tool, which consists of the following three main modules: Emergency type management module, which defines two levels of event types: domain events and subject events, to achieve the classification and management of emergencies. Domain events mainly define the type domain of emergencies and are used for the classification and management of emergencies, such as air emergencies, maritime emergencies, land emergencies, natural disaster emergencies, etc. Its nodes only need to set three attributes: domain event name, description information, and type internal code.

[0017] A themed event refers to a variety of typical emergencies that include specific scenarios. For example, a natural disaster emergency can be divided into fire emergencies, mudslide emergencies, earthquake emergencies and other themed events. The theme emergency event node needs to set basic attributes such as event name and basic description, and set description attributes such as event internal code, event scenario model internal code, and domain event type internal code in the background.

[0018] The event element management module classifies and manages the event entity models, behavior models, relationship models, etc. of people, equipment, objects, and environment involved in domain events according to the ontology system to support the construction of event scenarios.

[0019] Entity model management module, entity model refers to various elements such as people, equipment, objects and environment involved in the theme event. The default element classification of the present invention includes different entity types such as location, time, agent, object, disposal subject, disposal resource, etc. The entity model is carefully classified and managed through the entity classification table to meet the needs of different theme event scenario construction. Each entity column contains several entity models. The classification name of the entity model can be further flexibly modified according to different theme events. For example, in a fire emergency, the agent class can be named arsonist, specifically including lightning, personnel and other entities, and the object includes forests, buildings and other entities. The disposal subject refers to various entities that intervene, contain or eliminate the emergency, such as fire brigades, governments, etc. The element classification table sets two basic attributes: classification name and element classification internal code. The entity model management function supports operations such as entity model access and entity model editing. The meta-attributes of each entity model include model name, model internal code, model description, model data type, classification internal code and other basic description information.

[0020] Behavior model management module, behavior is a subordinate event of the theme event, and is all kinds of behaviors or strategies involved in the theme event. Behavior includes two types: target behavior and disposal behavior. Behavior, as a fine-grained sub-event in the theme event, is a high-order knowledge model, which contains five basic elements such as type, place, time, agent, and recipient. The elements can also be expanded according to the needs of specific scenarios. The elements that constitute the behavior model come from the entity model. The elements can be connected in series through some character words to form a more complete formal representation. The basic descriptive attributes of each behavior model include behavior internal code, behavior description, behavior name, behavior classification internal code, and related theme event internal code.

[0021] Relationship management module, relationships are used to identify and express potential semantic connections between entities in scenarios, providing key information for in-depth understanding and analysis of event scenarios. The present invention only defines entity-to-entity relationships for entity extraction constraints, and does not involve relationships between behaviors. The relationship model structure includes relationship type, head entity and tail entity. The head entity and tail entity can be connected in series through some character words to form a better semantic logical expression. The basic description information of the relationship model includes: relationship name, relationship description, relationship internal code, associated subject event internal code, etc.

[0022] The event scenario model construction module is essentially a visual control. It uses a "building blocks" approach to drag basic models such as event entity elements, behavior elements, relationship models, etc. from the event element management module to the event scenario customization panel to complete the construction of the theme event scenario. The emergency event scenario model constructed by the present invention is mainly a static scenario description model, that is, it describes the total set of scenario elements such as entities and behaviors involved in the event scenario, and does not reflect the dynamic evolution of the emergency event scenario. The basic description attributes of each theme event scenario model include model name, model internal code, model description, associated theme event internal code, etc. The scenario model includes scenario entities, scenario behaviors, disposal associations, etc.

[0023] Scenario entity element module: Select the entity block from the entity model list of the entity model management module by dragging and dropping to embed it into the entity element module in the scenario customization panel, and configure the entity classification node according to the scenario needs. Considering that each entity may come from multiple definition sources, the source can be linked to the type in the online database, such as Wikidata, or other ontology model sources can be specified.

[0024] Scenario behavior module: The scenario behavior module has two classification nodes: target behavior and disposal behavior. The target behavior node enumerates the behavior models involved in the target of the triggering event in the subject event scenario. The model is displayed as a behavior block in the scenario modeling panel. You can place the mouse on the behavior block to display the basic description of the behavior. The type of the behavior model can be modified by double-clicking it without modifying the underlying data type. The information slot of the behavior block is filled with entities. The entity model in the information slot is also predefined in the behavior model, but can be modified. The entities involved in the behavior block may appear in other behavior blocks, indicating that these entities are the same. Under the target behavior node, it can be further divided into: cause-type behavior, process-type behavior, influence (effect) type behavior and other nodes.

[0025] Disposal association module, the disposal association module is selectively configured by business experts with behavior and entity models, also known as scenario feature ontology. Scenario feature ontology mainly includes: target entity and target behavior. During the event handling process, these scenario feature ontologies will be materialized as the event evolves to form scenario feature words, which can support the association and matching of various disposal data resources required for emergency disposal through semantic retrieval, such as disposal process plans, disposal plans, historical similar cases, last instruction documents, policies and regulations, disposal strategy libraries, etc. During the emergency handling process, scenario feature words will be gradually iterated as the event progresses to achieve accurate matching and optimal configuration of scenario resources.

[0026] Based on the tool, the present invention provides a visual emergency scenario modeling method, which includes the following steps: constructing a classification system of domain events and subject events; constructing entity models and behavior models related to domain events; constructing an event scenario model for each subject event in the event scenario model customization panel; exporting the scenario model to an XML or JSON document after completing the scenario model compilation, or directly storing the defined data structure in a data table. The specific process is as follows: Step S1: Use the emergency type classification management module to realize the hierarchical construction and setting of domain events and theme events, laying a classification foundation for scenario modeling. You can fill in or modify the event name and basic description information for the two-layer event by double-clicking; Step S2: Build entity models and behavior models related to domain events through entity model management function and behavior model management function. Entity models mainly involve various entities involved in domain events. You can check the existing entity models in the system through the resource search function at the top of the entity model management function, or edit the entity model under the entity model management module. The behavior model is mainly composed of information slots filled by the entity model and the information slots are connected in series through strings. The constructed behavior model can be modified by double-clicking the model attributes, such as name, connection characters, etc. Step S3: In the event scenario model customization panel, the event scenario model of each subject event is constructed through intuitive dragging and detailed configuration operations. The panel is an expandable tree-like distribution structure, and the root node is the subject event name. The root node is initially regarded as three classification nodes, namely event entity, event behavior, and disposal response; The event entity has entity classification nodes, and each node can be arranged according to the role in the scenario. The scenario entity element module can be further defined as classification nodes such as time, place, environment, agent, and disposal resources. Click the entity model in the entity classification management module and drag it to the corresponding event entity classification node. Set a relationship node under the event entity node and drag the entity relationship model link from the relationship management function to the node. Double-click the left button to modify the relationship name of the relationship model, the entity name in the entity slot, and the serialized entity words; The behavior element has two sub-nodes: target behavior and disposal behavior. You can drag the behavior model from the behavior management module to link it to the corresponding behavior type node. You can modify the basic elements of the behavior model by double-clicking the left button. In the event response module, you can use the node add button to preset the response resource association nodes such as policies and regulations, superior instructions, historical cases, response plans, and response process plans. Each response resource association node can drag entity models and behavior models from the entity model management and behavior model management modules as the associated scenario feature ontology to provide scenario feature words for the feedback of the associated services in the instantiated scenario. Step S4: After the scenario model is orchestrated, it is exported as an XML or JSON document, or converted into the data structure of the backend database to support further data processing and analysis. After the scenario model is orchestrated, it can be exported as an XML document or a JSON document for use by other systems. The data structure defined by the relevant model can also be directly converted into a table of the backend relational database or an ontology model of the graph database to support the extraction of event knowledge from event dynamic data, provide basic support for downstream entity linking / disambiguation, as well as event warning, event correlation analysis, and event comprehensive report generation at the business level.

[0027] Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field and related fields without creative work should fall within the scope of protection of the present invention. The structures, devices and operating methods not specifically described and explained in the present invention are implemented according to the conventional means in the field unless otherwise specified and limited.

Claims

1. A method for constructing an ontology-based emergency response scenario modeling tool, characterized in that: It includes an emergency event type management module, an event element management module and an event scenario model construction module, wherein the emergency event type management module is electrically connected to the event element management module, and the event element management module is electrically connected to the event scenario model construction module; The event element management module includes an entity model management module, a behavior model management module and a relationship management module, wherein the entity model management module is electrically connected to the behavior model management module, and the behavior model management module is electrically connected to the relationship management module; The event scenario model construction module includes a scenario entity element module, a scenario behavior module and a disposal association module. The scenario entity element module is electrically connected to the scenario behavior module, and the scenario behavior module is electrically connected to the disposal association module.

2. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The emergency event type management module defines two levels of event types: domain events and subject events, to achieve classification and management of emergency events.

3. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The event element management module classifies and manages event entity models, behavior models, relationship models, etc. such as people, equipment, objects, and environment involved in domain events according to the ontology system to support event scenario construction.

4. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The event scenario model construction module adopts a "building blocks" approach to drag basic models such as event entity elements, behavior elements, relationship models, etc. from the event element management module to the event scenario customization panel to complete the construction of the theme event scenario.

5. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The entity model management function is carefully classified and managed through an entity classification table to meet the needs of building scenarios for different subject events. Each entity column contains several entity models.

6. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The behavior model management module is a subordinate event module of the theme event, and is various behaviors or strategies involved in the theme event.

7. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The relationship management module is used to identify and express the potential semantic connections between entities in the scenario, providing key information for in-depth understanding and analysis of event scenarios.

8. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The scenario entity element module selects entity blocks from the entity model list of the entity model management module by dragging and embedding them into the entity element module in the scenario customization panel, and configures entity classification nodes according to scenario requirements.

9. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The scenario behavior module has two classification nodes: target behavior and disposal behavior.

10. The method for constructing an ontology-based emergency response scenario modeling tool according to claim 1, characterized in that: The handling association module is selectively configured with behavior and entity models by business experts.

Images