Ontology-based emergency modeling method

Abstract

The invention discloses an ontology-based emergency modeling method, and relates to the technical field of data science and artificial intelligence, an emergency handling conceptual model is established, the emergency handling conceptual model is a business model, a general information model is described according to domain terms, the top-layer information demand of business is defined, and the top-layer information demand of the business is established; the main elements include place, time, subject, subject, cause, process, consequence, influence, treatment guidance, treatment mechanism, treatment strength and response action. The elements comprise three relations of entities, entities and events, and events and events. According to the ontology-based emergency modeling method, the general information model answers concerned and concerned questions of field scenes and indicates required entity concepts and key attributes.

Description

Technical Field

[0001] The present invention relates to the field of data science and artificial intelligence technology, and in particular to an ontology-based emergency event modeling method. Background Art

[0002] In the process of handling emergencies such as natural disasters, security controls, and social crises, the diversity of business scenarios poses a significant challenge to the digitalization and process-based nature of emergency response. Emergency response requires event scenario modeling and situational awareness, including the description and association of event scenario elements. A scenario model is a discrete representation of an emergency scenario, a description of the greatest common denominator of multiple similar emergencies in a specific scenario. It uses time slices to express the latest state of event scenario elements at a specific time period or point in time. This supports the description and reasoning of event scenario instances, and supports the optimization of event response decisions. Accurately modeling and representing event scenarios for intelligent computer processing and the utilization of business resources has become a crucial foundational task.

[0003] The present invention provides a method for modeling emergency scenarios based on a universal ontology model, including modeling a scenario entity concept classification system, constructing a scenario entity metamodel, constructing a scenario event metamodel, and modeling an event classification system. The method can adapt to a variety of emergency scenarios. The event scenario model formed by this method can support the emergency handling system to extract entities, behaviors, and handling information related to the emergency from various text-based business data such as real-time situation data and trend briefings after the emergency occurs, forming an event handling digital space, supporting decision makers to conduct more scientific event risk assessments and generate handling decisions, and effectively supporting the improvement of the efficiency and accuracy of emergency handling. The present invention can construct an emergency scenario model that is highly versatile, adaptable, and can cover all possible event types. Summary of the Invention

[0004] To achieve the above objectives, the present invention is implemented through the following technical solutions: an ontology-based emergency event modeling method. The model not only represents who did what, when, and where, but also represents the role played by each participant and the effective attribute constraints of the role. This method can assist personnel in quickly converting professional knowledge into emergency event scenario models through visualization, and promote the event handling system to quickly generate event scenario knowledge or conduct event scenario reasoning from business data, thereby effectively solving the problems raised in the aforementioned background technology. The method includes the following steps: S1. Define the conceptual model for emergency response. Establish a conceptual model for emergency response. This model is a business model that describes the general information model using domain terminology. It defines the top-level information requirements of the business. Key elements include location, time, agent, recipient, cause, process, consequence, impact, response guidance, response organization, response force, and response actions. Elements are connected by three types of relationships: entity-to-entity, entity-to-event, and event-to-event. The general information model answers questions of concern and interest in the domain scenario and specifies the required entity concepts and key attributes.

[0005] S2. Clarify the scenario entity concept classification system. Based on the emergency response conceptual model, construct an entity concept system and an entity meta-model to meet the needs of describing different subject event scenarios. Entity concepts are abstract descriptions of entities with common characteristics, which are used to classify entity / event types and the semantic relationship between entity concepts. The entity concept hierarchy adopts a top-down approach to define the broadest concepts in the field and gradually refine them, while clarifying the relationship between concept types. Emergency scenarios are composed of multiple types of entities. In addition to the two elements of location and time, general entity concepts usually include: event subject, event object, implementation tools, response guidance, response resources, response agencies, response forces, etc.

[0006] Time is primarily divided into two sub-ontologies: moment and time interval. Location elements can be incorporated into open-source ontology namespaces such as Geoname. These primarily cover administrative classification names, such as global regions, countries, provinces, cities, counties, and districts, as well as hydrological categories such as lakes, rivers, mountains, and peaks. These geographic concepts interact with each other through inclusion, subclassification, hierarchy, adjacency, and name dependency, facilitating the understanding of geospatial data and effective spatial analysis.

[0007] The event subject is the trigger of the event, and its classification depends on the specific event scenario, forming different entity concept classification trees.

[0008] Event objects are the affected and recipients of event actions.

[0009] Regarding incident handling, it's necessary to clarify the conceptual framework of response entities, including response guidance, response agencies, and response forces. Response guidance provides the laws, policies, and guiding principles for handling emergencies. Sub-concepts include laws and regulations, superior directives, and international practices. Response agencies are organizations or institutions responsible for leading and coordinating emergency response efforts. Sub-concepts include government agencies, emergency management departments, and command centers. Response forces refer to the personnel or resources directly involved in emergency response.

[0010] S3. Clarify the attributes of the entity metamodel. First, clarify the attributes of each entity concept. Entity concepts form the entity metamodel through attribute definitions, including base class attributes and relationship class attributes. Base class attributes reflect the inherently stable and unique properties of an entity. For example, in a reef-breaking scenario, the attribute values for a ship's tonnage, size, name, and type are text, integers, floating-point numbers, Boolean values, and other literals. Relationship class attributes reflect the relationship between an entity and other entities or concepts. For example, attributes such as a ship's country / organization, attached equipment, fleet, and ship type are all relationship class attributes. Second, clarify attribute constraints. Attributes are connected by a scope and a value range. The scope specifies which class entities possess the attribute, and the value range describes the type and threshold of the attribute value. Define rules and axioms when necessary to express complex attribute constraint logic.

[0011] S4. Define the emergency scenario event model. Real-world emergency scenarios encompass events of varying granularity, typically categorized into three levels: topic events, sub-events, and meta-events. A topic event reflects a relatively macro-level issue within a specific period, exhibiting distinct phased evolutionary characteristics. Its model components are typically general, holistic, comprehensive, and abstract. A sub-event refers to a type of activity within a topic event that triggers specific behaviors within a specific time and space. A meta-event is the finest-grained event and refers to the specific actions taken by the event subject.

[0012] S41. Construct an event concept system. Based on typical emergency scenarios, clarify the event concept system involved in the scenario. According to domain knowledge and business common sense, select the most representative and distinctive event features to form a multi-level event concept tree hierarchy, and use predicates to define the relationship between event concepts, such as hierarchical and subordinate, cause and effect, sequential, inclusive, and opposite relationships, to explain the semantic relationship between concepts in the concept system. For example, in the reef-breaking incident, the following event concept system is constructed around the emergency and the handling event. For example, for the reef-breaking incident scenario, the following handling event concept system is established.

[0013] S42. Establish an emergency event model. Each emergency event concept is considered an entity. Defining an event scenario model is to construct the necessary attributes and attribute constraints for the event concept. The emergency event scenario model contains three types of attributes: ① Basic event attributes, which are the intrinsic attributes of the event, including attributes such as event ID, event name, type, event description, as well as extended basic attributes such as level, polarity, stage, and scale. Basic attributes directly establish the connection between events and attribute values, and the attribute value domain is a specific literal quantity. ② Entity class attributes. Referencing the entity metamodel defined within the entity concept system, it mainly includes arguments such as event, subject, object, tool, time, and place, and mainly establishes the semantic relationship between events and entities. ③ Event class attributes. Mainly including four event elements such as cause, process, consequence, and impact, reflecting the event relationship between thematic event and thematic event, and thematic event and sub-event. A complete emergency event scenario model mainly includes two event models: the emergency event model and the scenario event model.

[0014] S43. Construct an emergency response model. First, clarify the conceptual system of response entities, including response guidance, response agencies, and response forces. Response guidance provides the laws, policies, and guiding principles for handling emergencies. Sub-concepts include laws and regulations, superior instructions, international practices, strategic documents, and emergency plans. Command agencies are organizations or institutions responsible for leading and coordinating emergency response efforts. Sub-concepts include government agencies, emergency management departments, command centers, and commanders. Response forces refer to the personnel or resources directly involved in emergency response.

[0015] Secondly, establish the relationship between key response elements and response events. Response events conceptually describe the response activities undertaken by response agencies and response forces in response to an emergency. Response guidance provides operational guidance for response agencies and response forces, influencing their decisions and actions. Response agencies are responsible for commanding and coordinating response forces. Response forces execute the decisions and instructions of response agencies and are the primary actors in implementing response events. Finally, based on the emergency scenario description model, define the response event model.

[0016] The present invention provides an ontology-based emergency event modeling method, which has the following beneficial effects: The emergency handling scenario model constructed by this method is intended to make the minimum semantic constraints so as to extract the data items with the greatest commonality from the business system to achieve the interoperability of event data in different scenarios in different fields, and at the same time guide the design of data structures based on ontology. Although this document shows the specific implementation methods of the present invention in detail, it is highly versatile and can adapt to different types of emergencies. It can be combined with technologies such as natural language processing and language large models to improve situational understanding and response capabilities. However, professionals and technicians in this field should be able to recognize that, under the premise of maintaining the core principles and spirit of the invention unchanged, these embodiments can undergo a variety of innovative changes, adjustments, optimizations and adaptive modifications. The scope of the present invention is defined by the appended claims and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A schematic diagram of a conceptual model of an emergency handling scenario of an ontology-based emergency modeling method of the present invention; Figure 2 This is a schematic diagram of the main conceptual system of a ship in a reef-breaking event of the present invention; Figure 3 Schematic diagram of the conceptual system of event types of reef-breaking events of the present invention; Figure 4 This is a schematic diagram of the conceptual system for handling reef-breaking incidents of the present invention; Figure 5 Schematic diagram of the emergency model of the present invention; Figure 6 Schematic diagram of the relationship between key disposal elements and disposal events of the present invention; Figure 7 This is a schematic diagram of the event handling model of the present invention; Figure 8 Schematic diagram of the event handling scenario model of the present invention. DETAILED DESCRIPTION

[0018] The present invention will be described in further detail below with reference to the accompanying drawings and specific embodiments. The embodiments of the present invention are provided for purposes of illustration and description and are not intended to be exhaustive or to limit the invention to the disclosed forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments are chosen and described to better illustrate the principles of the invention and its practical application, and to enable those skilled in the art to understand the invention and design various embodiments with various modifications suitable for specific applications.

[0019] The first embodiment, as Figures 1 to 8As shown, the present invention provides a technical solution: an ontology-based emergency event modeling method. The model not only represents who did what, when, and where, but also represents the role played by each participant and the effective attribute constraints of the role. This method can assist personnel in quickly converting professional knowledge into emergency event scenario models through visualization, and promote the event handling system to quickly generate event scenario knowledge or perform event scenario reasoning from business data, thereby effectively solving the problems raised in the aforementioned background technology. The method includes the following steps: S1. Define the conceptual model for emergency response. Establish a conceptual model for emergency response. This model is a business model that describes the general information model based on domain terminology. It defines the top-level information requirements of the business. Key elements include location, time, agent, recipient, cause, process, consequence, impact, response guidance, response organization, response force, and response actions. Elements are connected by three types of relationships: entity-to-entity, entity-to-event, and event-to-event. The general information model answers questions of concern and interest in domain scenarios and identifies required entity concepts and key attributes.

[0020] S2. Clarify the scenario entity concept classification system. Based on the emergency response conceptual model, construct an entity concept system and an entity meta-model to meet the needs of describing different subject event scenarios. Entity concepts are abstract descriptions of entities with common characteristics, which are used to classify entity types and the semantic relationship between entity concepts. The entity concept hierarchy adopts a top-down approach to define the broadest concepts in the field and gradually refine them, while clarifying the relationship between concept types. Emergency scenarios are composed of multiple types of entities. In addition to the two elements of location and time, general entity concepts usually include: event subject, event object, implementation tools, response guidance, response resources, response agencies, and response forces.

[0021] Time is primarily divided into two sub-ontologies: moment and time interval. Location features can be incorporated into open-source ontology namespaces such as Geoname. These primarily cover administrative classification names, such as global regions, countries, provinces, cities, counties, and districts, as well as hydrological categories such as lakes, rivers, mountains, and peaks. These geographic concepts share inclusion, sub-classification, hierarchy, adjacency, and name-dependency relationships, facilitating the understanding of geospatial data and effective spatial analysis.

[0022] The event subject is the trigger of the event, and its classification depends on the specific event scenario, forming different entity concept classification trees.

[0023] Event objects are the affected and recipients of event actions.

[0024] Regarding incident handling, it's necessary to clarify the conceptual framework of response guidance, response agencies, and response force entities. Response guidance provides the laws, policies, and guiding principles for handling emergencies. Sub-concepts include laws, regulations, superior directives, and international practices. Response agencies are organizations or institutions responsible for leading and coordinating emergency response efforts. Sub-concepts include government agencies, emergency management departments, and command centers. Response force refers to the personnel or resources directly involved in emergency response.

[0025] S3. Clarify the attributes of the entity metamodel. First, clarify the attributes of each entity concept. Entity concepts form the entity metamodel through attribute definitions, including base class attributes and relationship class attributes. Base class attributes reflect the inherently stable and unique properties of an entity. For example, in a reef-breaking scenario, the attribute values for a ship's tonnage, size, name, and type are text, integers, floating-point numbers, and Boolean literals. Relationship class attributes reflect the relationship between an entity and other entities or concepts. For example, a ship's attributes such as its country / organization, attached equipment, fleet, and ship type are all relationship class attributes. Second, clarify attribute constraints. The scope and value range are connected at both ends of an attribute. The scope specifies which class entities possess the attribute, and the value range describes the type and threshold of the attribute value. Define rules and axioms when necessary to express complex attribute constraint logic.

[0026] S4. Define the emergency scenario event model. Real-world emergency scenarios encompass events of varying granularity, typically categorized into three levels: topic events, sub-events, and meta-events. A topic event reflects a relatively macroscopic issue within a specific period, exhibiting distinct phased evolutionary characteristics. Its model components are typically general, holistic, comprehensive, and abstract. A sub-event refers to a type of activity within a topic event that triggers specific behaviors within a specific time and space. A meta-event is the finest-grained event and refers to the specific actions taken by the event subject.

[0027] S41. Construct an event concept system. Based on typical emergency scenarios, clarify the event concept system involved in the scenario. According to domain knowledge and business common sense, select the most representative and distinctive event features to form a multi-level event concept tree hierarchy, and use predicates to define the relationship between event concepts, such as hierarchical, causal, sequential, inclusive, and oppositional relationships, to explain the semantic relationship between concepts in the concept system. For example, in the reef-breaking incident, the following event concept system is constructed around the emergency and the handling event. For example, for the reef-breaking incident scenario, the following handling event concept system is established.

[0028] S42. Establish an emergency event model. Each emergency event concept is considered an entity. Defining an event scenario model is to construct the necessary attributes and attribute constraints for the event concept. The emergency event scenario model contains three types of attributes: ① Basic event attributes, which are the intrinsic attributes of the event, including event ID, event name, type, and event description attributes, as well as basic attributes of level, polarity, stage, and scale scalability. Basic attributes directly establish the connection between events and attribute values, and the attribute value domain is a specific literal quantity. ② Entity class attributes. Referencing the entity metamodel defined within the entity concept system, it mainly includes event, subject, object, tool, time, and location arguments, and mainly establishes the semantic relationship between events and entities. ③ Event class attributes. Mainly includes the four event elements of cause, process, consequence, and impact, reflecting the event relationship between thematic event and thematic event, and thematic event and sub-event. A complete emergency event scenario model mainly includes two event models: the emergency event model and the scenario event model.

[0029] S43. Construct an emergency response model. First, clarify the conceptual system of response guidance, response agencies, and response force entities. Response guidance provides the laws, policies, and guiding principles for handling emergencies. Subconcepts include laws and regulations, superior instructions, international practices, strategic documents, and plans and contingency plans. Command agencies are organizations or institutions responsible for leading and coordinating emergency response efforts. Subconcepts include government agencies, emergency management departments, command centers, and commanders. Response forces refer to the personnel or resources directly involved in emergency response.

[0030] Secondly, establish the relationship between key response elements and response events. Response events conceptually describe the response activities undertaken by response agencies and response forces in response to an emergency. Response guidance provides operational guidance for response agencies and response forces, influencing their decisions and actions. Response agencies are responsible for commanding and coordinating response forces. Response forces execute the decisions and instructions of response agencies and are the primary actors in implementing response events. Finally, based on the emergency scenario description model, define the response event model.

[0031] Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field and related fields without making creative efforts should fall within the scope of protection of the present invention. Structures, devices, and operating methods not specifically described and explained in the present invention shall be implemented in accordance with conventional means in the field unless otherwise specified or limited.

Claims

1. An ontology-based emergency event modeling method, characterized in that: The following steps are involved: S1. Clarify the conceptual model of emergency response events; Establish a conceptual model for emergency response, define the general information model based on domain terminology, and define the top-level information requirements of the business. The main top-level information requirements include location, time, agent, recipient, cause, process, consequence, impact, response guidance, response organization, response force, and response action. The relationships between these elements include three types of relationships: entity-entity, entity-event, and event-event. S2. Clarify the classification system of situational entity concepts; Based on the emergency response conceptual model, an entity concept system and entity meta-model are constructed to meet the needs of describing different subject event scenarios; S3. Clarify the attributes of the entity metamodel; S4. Define the emergency scenario event model; Defining an emergency scenario event model specifically includes the following steps: S41. Construct an event concept system. Based on typical emergency scenarios, clarify the event concept system involved in the scenario. By selecting event features, form a multi-level event concept tree hierarchy, define the relationship between event concepts, and explain the semantic relationship between concepts in the concept system. S42. Establish an emergency model; Each contingency concept is considered as an entity; The emergency scenario model includes three types of attributes, specifically event-based attributes, entity-class attributes, and event-class attributes; The emergency event model and the scenario event model together constitute an emergency event scenario model; S43. Construct an emergency response event model; Clarify the conceptual system of disposal guidance, disposal agencies, and disposal force disposal entities; The said handling guidance provides the laws, policies and guiding principles for handling emergencies. Its sub-concepts include laws and regulations, superior instructions, international practices, strategic documents and plans and contingency plans; The command organization is responsible for leading and coordinating the organization or institution for handling emergencies, and its sub-concepts include: government agencies, emergency management departments, command centers, and commanders; The disposal force refers to the personnel or disposal resources directly involved in the disposal of emergencies; S43. Fusion forms an emergency scenario ontology model.

2. The ontology-based emergency event modeling method according to claim 1, characterized in that: The entity concept system in step S2 is used for the classification of entity or event types, as well as the semantic relationship between entity concepts. The entity concept system architecture adopts a top-down approach to define the broadest concepts in the field and gradually refines them, while clarifying the relationship between concept types.

3. The ontology-based emergency event modeling method according to claim 2, characterized in that: The entity concept system includes location, time, event subject, event object, implementation tools and disposal events; The time is mainly divided into two sub-types: moment and time interval; The location elements can be introduced into the Geoname open source ontology namespace, covering administrative classification names; The event subject is specifically the event trigger, and its classification depends on the specific event scenario, forming different entity concept classification trees; The event object is the affected party and receiver of the event action.

4. The ontology-based emergency event modeling method according to claim 3, characterized in that: The said handling event includes a handling guidance system, a handling agency system and a handling force system; The handling guidance system provides the laws, policies and guiding principles for handling emergencies, and its sub-concepts include laws and regulations, superior instructions, and international practices; The handling agency system is used to coordinate the organizations or institutions for handling emergencies, and its sub-concepts include: government agencies, emergency management departments and command centers; The disposal force system specifically refers to the personnel or disposal resources directly involved in the disposal of emergencies.

5. The ontology-based emergency event modeling method according to claim 4, characterized in that: The step S3 specifically includes the following steps: S31, the entity meta-model is formed by entity concept definition, including basic class attributes and relationship class attributes; The basic class attributes specifically reflect the inherent stable and unique attributes of the entity; Relationship attributes specifically reflect the relationship between an entity and other entities or concepts; S32. Clarify attribute constraints. The scope and value range are connected at both ends of the attribute. The scope specifies which types of entities have the attribute, and the value range describes the type and threshold of the attribute value. Rules and axioms are defined to express complex attribute constraint logic.

Images