Disaster event processing method and apparatus, electronic device, and storage medium

Abstract

Embodiments of the present application disclose a disaster event processing method and device, electronic equipment and a storage medium, wherein the method comprises: obtaining one disaster event in a disaster event list as a main event; determining other disaster events in the disaster event list that satisfy a preset association relationship with the main event as associated events of the main event; and processing the main event in combination with the associated events of the main event. The technical scheme provided by the embodiments of the present application is suitable for a disaster event monitoring system in a disaster tracking scenario, and can improve the response and disposal efficiency of disaster events.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of emergency disposal, in particular to a disaster event processing method and device, an electronic device and a storage medium. BACKGROUND

[0002] Natural disaster monitoring refers to observing and monitoring the dynamic changes of factors related to the whole process of natural disaster gestation, occurrence, development and disaster-causing and hazard-causing by using various observation and measurement means. In order to accelerate the construction of natural disaster monitoring informatization engineering, a natural disaster monitoring system is developed. The system monitors and analyzes natural disasters in a digital manner, thereby playing a role in disaster early warning, disaster tracking, disaster assessment and providing disaster reduction decision-making schemes. Among them, disaster prediction refers to predicting potential disasters, including occurrence time, range, scale and the like, to prepare for effective disaster prevention; disaster monitoring refers to real-time monitoring of various disasters, and quickly and accurately providing major disaster information such as flood, drought and earthquake to provide help for emergency rescue; disaster assessment mainly analyzes various disaster data to provide decision-making basis for post-disaster recovery and reconstruction.

[0003] At present, when the natural disaster monitoring system is tracking disasters, it is isolated to deal with each disaster event reported by the monitoring device, regardless of the relationship between the disaster events or whether they are repeated, and the efficiency is very low. SUMMARY

[0004] Therefore, the embodiments of the present application provide a disaster event processing method, device, electronic device and storage medium to improve the efficiency of disaster event disposal.

[0005] In a first aspect, the embodiments of the present application provide a disaster event processing method, which comprises:

[0006] obtaining one disaster event in a disaster event list as a main event;

[0007] determining other disaster events in the disaster event list that meet a preset association relationship with the main event as associated events of the main event;

[0008] processing the main event in combination with the associated events of the main event.

[0009] As an implementation manner, determining other disaster events in the disaster event list that meet a preset association relationship with the main event as associated events of the main event comprises:

[0010] determining other disaster events in the disaster event list that meet a preset repetition condition with the main event as associated events of the main event;

[0011] Processing the main event in combination with the associated events of the main event, comprising:

[0012] Canceling the processing of the associated events of the main event;

[0013] Performing information deduplication on the main event and its associated events, and updating the information of the main event based on the information deduplication result;

[0014] Processing the main event after information update.

[0015] Further, determining other disaster events in the disaster event list that meet the preset repetition condition with the main event as the associated events of the main event, comprising:

[0016] Screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event;

[0017] Determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated events of the main event.

[0018] Further, determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated events of the main event, comprising:

[0019] Displaying the main event and the screened other disaster events;

[0020] According to a first selection operation on the displayed other disaster events, determining other disaster events that meet the preset repetition condition with the main event as the associated events of the main event;

[0021] Performing information deduplication on the main event and its associated events, and updating the information of the main event based on the information deduplication result, comprising:

[0022] According to a second selection operation on the information field of the displayed associated event, updating the content of the corresponding information field in the main event, wherein the second selection operation includes a preset information difference selection operation and / or an information covering selection operation.

[0023] Further, the method further comprises:

[0024] Receiving the disaster events reported by the monitoring devices in the jurisdiction region and recording to the disaster event list;

[0025] Processing the main event after information update, comprising: reporting the main event after information update to the background server, so that the background server processes the received main event.

[0026] Further, the method further comprises:

[0027] receive the response and disposal result of the disaster event reported by the local background server, and count the response and disposal result of the main event after the information is updated to determine whether to switch to a preset simple disaster event processing mode.

[0028] As another implementation, the other disaster event in the disaster event list that meets a preset correlation relationship with the main event is determined as the correlation event of the main event, including:

[0029] The other disaster event in the disaster event list that meets a preset secondary derivative relationship with the main event is determined as the correlation event of the main event.

[0030] Further, the other disaster event in the disaster event list that meets a preset secondary derivative relationship with the main event is determined as the correlation event of the main event, including:

[0031] The other disaster event in the disaster event list that meets a preset secondary derivative relationship with the main event is determined as the correlation event of the main event.

[0032] Further, the other disaster event in the disaster event list that meets a preset secondary derivative relationship with the main event is determined as the correlation event of the main event, including:

[0033] The main event and the other disaster event screened out are displayed.

[0034] According to a third selection operation on the displayed other disaster event, the other disaster event that meets a preset secondary derivative relationship with the main event is determined.

[0035] Further, the method further includes:

[0036] The disaster event reported by the monitoring device in the jurisdiction is received and recorded to the disaster event list.

[0037] The main event is processed in combination with the correlation event of the main event, including:

[0038] The correlation event identifier of the main event is added to the information field content of the main event.

[0039] The main event after the addition operation is reported to the background server, so that the background server disposes the main event according to the response and disposal scheme of the correlation event.

[0040] 5In a second aspect, an embodiment of the present application provides a disaster event processing device, the device comprising:

[0041] a main event acquisition unit configured to acquire one disaster event in a disaster event list as a main event;

[0042] an associated event determination unit configured to determine other disaster events in the disaster event list that satisfy a preset association relationship with the main event as associated events of the main event;

[0043] a main event processing unit configured to process the main event in combination with the associated events of the main event.

[0044] As an implementation form, the associated event determination unit comprises a repeated event determination unit configured to:

[0045] determine other disaster events in the disaster event list that satisfy a preset repeated condition with the main event as the associated events of the main event;

[0046] the main event processing unit comprises:

[0047] an event cancellation subunit configured to cancel processing of the associated events of the main event;

[0048] an event update subunit configured to perform information deduplication on the main event and the associated events thereof, and update information of the main event based on a result of the information deduplication;

[0049] an event processing subunit configured to process the main event after the information update.

[0050] Further, the repeated event determination unit is configured to determine other disaster events in the disaster event list that satisfy a preset repeated condition with the main event as the associated events of the main event, and specifically comprises:

[0051] screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event;

[0052] determining other disaster events that satisfy a preset repeated condition with the main event from the screened disaster events as the associated events of the main event.

[0053] Further, the repeated event determination unit is configured to determine other disaster events that satisfy a preset repeated condition with the main event from the screened disaster events as the associated events of the main event, and specifically comprises:

[0054] displaying the main event and the screened other disaster events;

[0055] According to a first selection operation on the displayed other disaster event, other disaster events meeting a preset repetition condition with the main event are determined as associated events of the main event;

[0056] The event updating subunit is configured to perform information deduplication on the main event and its associated events, update information of the main event based on a result of the information deduplication, and include the following steps:

[0057] According to a second selection operation on an information field of the displayed associated event, content of a corresponding information field in the main event is updated, wherein the second selection operation includes a preset information difference selection operation and / or an information covering selection operation.

[0058] Further, the device further includes an event receiving unit configured to receive a disaster event reported by a monitoring device in a jurisdictional region and record the disaster event to a disaster event list.

[0059] The event processing subunit is configured to process the main event after information updating, and includes the following step: reporting the main event after information updating to a background server, so that the background server performs response and disposal on the received main event.

[0060] Further, the device further includes:

[0061] A response and disposal result receiving unit configured to receive a response and disposal result of a disaster event reported by the local device and issued by the background server.

[0062] A mode switching judging unit configured to count a response and disposal result of the main event after information updating in the response and disposal results received by the response and disposal result receiving unit, so as to judge whether to switch to a preset simple disaster event processing mode.

[0063] As another implementation manner, the associated event determining unit includes a secondary derivative event determining unit configured to:

[0064] Determine other disaster events in the disaster event list meeting a preset secondary derivative relationship with the main event as associated events of the main event.

[0065] Further, the secondary derivative event determining unit is configured to determine other disaster events in the disaster event list meeting a preset secondary derivative relationship with the main event as associated events of the main event, and specifically includes the following steps:

[0066] Screen other disaster events in the disaster event list having the same region, the same time period and different types as the main event;

[0067] Determine other disaster events meeting a preset secondary derivative relationship with the main event from the screened disaster events as associated events of the main event.

[0068] Further, the secondary derivative event determining unit is configured to determine, from the screened disaster events, other disaster events satisfying a preset secondary derivative relationship with the main event as the associated events of the main event, and specifically includes:

[0069] displaying the main event and the screened other disaster events;

[0070] According to a third selection operation on the displayed other disaster events, determining other disaster events satisfying a preset secondary derivative relationship with the main event.

[0071] Further, the device further includes an event receiving unit configured to receive disaster events reported by monitoring devices in the jurisdiction area and record the disaster events to a disaster event list.

[0072] The main event processing unit is configured to process the main event in combination with the associated events of the main event, and specifically includes:

[0073] adding an associated event identifier of the main event in the information field content of the main event;

[0074] reporting the main event after the adding operation to a background server, so that the background server performs coping and disposal on the main event according to a coping and disposal scheme of the associated event.

[0075] In a third aspect, an electronic device is provided, which includes a housing, a processor, a memory, a circuit board and a power supply circuit, wherein the circuit board is arranged inside a space enclosed by the housing, the processor and the memory are arranged on the circuit board; the power supply circuit is configured to supply power to each circuit or device of the electronic device; the memory is configured to store executable program codes; the processor is configured to run programs corresponding to the executable program codes by reading the executable program codes stored in the memory, and execute the disaster event processing method of the first aspect.

[0076] In a fourth aspect, a computer readable storage medium is provided, which stores one or more programs executable by one or more central processing units to implement the disaster event processing method of the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0077] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0078] Figure 1 A disaster event monitoring network architecture applicable to the embodiments of the present application;

[0079] Figure 2 Another disaster event monitoring network architecture applicable to the embodiments of the present application;

[0080] Figure 3 A disaster event processing method flowchart provided by the first embodiment of the present application;

[0081] Figure 4 A disaster event processing method flowchart provided by the second embodiment of the present application;

[0082] Figure 5 A disaster event processing method flowchart provided by the third embodiment of the present application;

[0083] Figure 6 A disaster event processing method flowchart provided by the fourth embodiment of the present application;

[0084] Figure 7 A disaster event processing device structure diagram provided by the fifth embodiment of the present application;

[0085] Figure 8 A disaster event processing device structure diagram provided by the sixth embodiment of the present application;

[0086] Figure 9 A disaster event processing device structure diagram provided by the seventh embodiment of the present application;

[0087] Figure 10 A disaster event processing device structure diagram provided by the eighth embodiment of the present application;

[0088] Figure 11 A structure diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0089] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0090] It should be clear that the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0091] First, the network architecture applicable to the embodiments of the present application is introduced.

[0092] Figure 1is a disaster event monitoring network architecture applicable to the embodiments of the present application, see Figure 1 This architecture includes a background server 101 and a plurality of monitoring devices 102 Figure 1 , of which monitoring devices 1, 2, …, n are exemplified, wherein the monitoring devices 102 collect data to generate disaster events and report to the background server 101 for response and disposal.

[0093] Figure 2 is another disaster event monitoring network architecture applicable to the embodiments of the present application, see Figure 2 This architecture includes a background server 201 and a plurality of front-end management devices 202 Figure 2 , of which front-end management devices 1, 2, …, m are exemplified, wherein each front-end management device 202 manages a plurality of monitoring devices 203 Figure 2 , of which monitoring devices 11, 12, …, mk are exemplified. For example, one front-end management device 202 can be deployed for each region to manage the monitoring devices 203 installed in the region. The monitoring devices 203 collect data to generate disaster events and report to the corresponding front-end management device 202, which processes the disaster events and sends them to the background server 201 for response and disposal.

[0094] Embodiment one

[0095] The present embodiment provides a disaster event processing method, which is executed by a corresponding disaster event processing device implemented by software and / or hardware and can be integrated in the background server in the network architecture as shown in Figure 1 or Figure 2 . See Figure 3 , the method comprises the following steps 301-303.

[0096] Step 301, obtain one disaster event in a disaster event list as a main event.

[0097] In this step 301, the disaster event list records a plurality of disaster events, wherein the disaster events can be generated by the monitoring devices by analyzing the collected data and need to be reported to the background server for early warning. Of course, the disaster events can also be provided by a third-party event management system, or entered by the background server management personnel, or obtained by the background server reading an external storage device. Each disaster event in the disaster event list contains a plurality of information fields for describing the specific circumstances of the event, such as event identification, event name, occurrence time, occurrence location, event type, event level, casualty situation, event status, report source, reporter, reporter contact information, and event description. Among them, if the event name can uniquely identify the disaster event, the event identification information field can be omitted.

[0098] In the disaster event list, each disaster event can be specially marked after being handled or canceled, so any disaster event in the disaster event list that is not specially marked can be selected as the main event. Of course, each disaster event can also be deleted in the disaster event list after being handled or canceled, and in this way, any disaster event in the current disaster event list can be selected as the main event. Optionally, the disaster event list can be backed up before step 301, and the disaster event list is not processed by the special marking and deletion of the disaster event, to facilitate subsequent review.

[0099] Step 302, determining other disaster events in the disaster event list that meet the preset repetition condition with the main event as the associated event of the main event.

[0100] In this step 302, the preset association relationship with the main event is specifically embodied as meeting the preset repetition condition with the main event. Correspondingly, the process of determining the associated event can include:

[0101] Screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event;

[0102] Determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated event of the main event.

[0103] Specifically, other disaster events that are likely to be repeated with the main event can be initially screened through the occurrence time, occurrence location, event type and other information fields of the disaster event, such as the same or adjacent region in the same or adjacent time period, and the same type of disaster event can be used as such an event, because the disaster event that meets the above three conditions is very likely to be the same disaster event reported by different personnel.

[0104] Subsequently, other disaster events that meet the repetition condition with the main event and can be information-merged can be further screened from the initial screening results as the associated event of the main event. As an implementation manner, the content matching of the set information fields of the main event and the other disaster events in the initial screening results is performed, and when the matching degree reaches a set threshold, it is determined that the other disaster event meets the preset repetition condition with the main event, and can be used as the associated event of the main event. The set information fields can include at least one of the following information fields: event name, occurrence location and event level; the content matching can be realized by using the existing semantic matching technology. When the set information fields are multiple, the matching degree reaching the set threshold can be understood as: the content matching degree of each set information field reaches the set threshold.

[0105] As another implementation, the operation can also be completed by a person in a human-computer interaction manner, specifically including: displaying the main event and the screened other disaster events; and according to a first selection operation on the displayed other disaster events, determining other disaster events that meet the preset repetition condition with the main event as the associated events of the main event. In the display of the main event and the screened other disaster events, all information field contents of the events can be displayed simultaneously. Preferably, the screened other disaster events can be displayed page by page, different other disaster events are displayed on different pages, and the main event is displayed on each page, and for the information field contents of the main event and the other disaster events on the same page, the common part and the different part of the two can be displayed separately. In this way, the similarities and differences between the two disaster events can be very intuitively displayed, and the person can compare and select the other disaster event selected by the person as the associated event of the main event.

[0106] Of course, in some specific application scenarios, the other disaster event in the preliminary screening result can also be directly selected as the associated event of the main event. It should be noted that if the associated event of the main event does not exist in the disaster event list, the main event is directly disposed.

[0107] Step 303, disposing the main event in combination with the associated event of the main event.

[0108] In the implementation, the disposal operation in step 303 as a specific processing operation includes:

[0109] ① canceling the disposal of the associated event of the main event;

[0110] ② performing information deduplication on the main event and the associated event, and updating the information of the main event based on the information deduplication result;

[0111] ③ disposing the main event after the information update.

[0112] In the operation ②, the information of the main event and the associated event can be deduplicated according to the information field. If the corresponding contents of the main event and the associated event are completely matched in semantics for the same information field (except the event identifier field), the information field contents are repeated, and the contents of the main event for the information field are not updated and remain unchanged. If the corresponding contents of the main event and the associated event are only partially matched in semantics for the same information field (except the event identifier field), the corresponding contents of the associated event that are different in semantics need to be supplemented to the corresponding contents of the main event.

[0113] Of course, the above-mentioned ② operation can also be completed by a person through human-computer interaction, specifically including: according to a second selection operation on the displayed information field of the associated event, updating the content of the corresponding information field in the main event. The second selection operation includes a preset information difference selection operation and / or an information coverage selection operation. When the second selection operation is the information difference selection operation, the specific updating process can include: supplementing the information field content of the selected associated event into the content of the corresponding information field in the main event, which requires the relevant personnel to select the specific content in the information field of the associated event that is different from the corresponding information field in the main event. When the second selection operation is the information coverage selection operation, the content of the corresponding information field in the main event is directly overwritten by the information field content of the selected associated event, which requires the relevant personnel to determine that the information field content of the associated event completely contains the content of the corresponding information field in the main event. For the information field of the associated event without the second selection operation, the content updating operation of the corresponding information field in the main event is not performed.

[0114] At present, most of the disaster events are reported by setting monitoring devices at monitoring points to collect data, and then handed over to the background server for disposal. When a disaster occurs, the monitoring device will always report the event, so the same disaster event is reported multiple times, generating multiple records, and the background server will have two problems when processing these records: 1. If multiple records are processed at the same time, the disposal work intensity will increase; 2. If only one reported record is processed, some important information will be ignored, increasing the difficulty of disposal.

[0115] Unlike the prior art, in the embodiment, the background server combines the main event and its associated events together for information integration, removes duplicate information, and then merges them into a new main event for disposal, which not only greatly reduces the event disposal work intensity, but also avoids the omission of disaster-related effective information or too much dispersion, making the disaster situation not comprehensive, and making the rescue work more clear and focused, efficient and orderly.

[0116] Embodiment Two

[0117] The embodiment provides a disaster event processing method, which is executed by a corresponding disaster event processing device. The device is realized by software and / or hardware, and can be integrated in a background server in a network architecture as shown in Figure 1 or Figure 2 . Referring to Figure 4 , the method includes the following steps 401-403.

[0118] Step 401, obtaining one disaster event in a disaster event list as a main event.

[0119] The step 401 is the same as the step 301 in the above embodiment one, and thus will not be repeated here.

[0120] The step 402 is to determine other disaster events in the disaster event list that meet the preset secondary derivative relationship with the main event as the associated event of the main event.

[0121] In the step 402, the preset association relationship with the main event is specifically the preset secondary derivative relationship with the main event. Accordingly, the process of determining the associated event can include:

[0122] The sub-step 4021 is to screen other disaster events in the disaster event list that have the same region, the same time period and different types as the main event.

[0123] The sub-step 4022 is to determine other disaster events that meet the preset secondary derivative relationship with the main event from the screened disaster events as the associated event of the main event.

[0124] The sub-step 4022 can specifically include: displaying the main event and the screened other disaster events; and determining, according to a third selection operation on the displayed other disaster events, the other disaster events that meet the preset secondary derivative relationship with the main event. For example, the other disaster event selected in the display interface of the main event and the screened other disaster events is determined as the other disaster event that meets the preset secondary derivative relationship with the main event.

[0125] Preferably, the screened other disaster events can be displayed page by page, different other disaster events are displayed on different pages, and each page displays the main event, and the common part and the difference part of the information field content of the main event and the other disaster events in the same page can be displayed separately. In this way, the similarities and differences between two disaster events can be very intuitively displayed, and it is convenient for relevant personnel to compare and select the other disaster event selected by the relevant personnel as the associated event of the main event.

[0126] It should be noted that if the disaster event list does not have the associated event of the main event, the main event is directly disposed.

[0127] The step 403 is to dispose the main event in combination with the associated event of the main event.

[0128] Specifically, the associated event of the main event can be output when the main event is disposed, and if the associated event has been disposed, the key event and the disposal scheme thereof can also be output.

[0129] The embodiment can find other disaster events having secondary derivative relationship with the main event from different types of disaster events occurring in the same region (county) and in the same time period (such as within a week), so as to cope with the main event in combination with these other disaster events, which can not only perfect the information and disaster impact of the main event, but also provide experience and reasonable scheme support for the rescue work of the main event. For example, if a ground collapse occurs in a certain place, the nearby other places can be known to have small earthquake events in the previous period of time through the embodiment, and all detailed information of the earthquake events can be consulted to provide information support for the rescue scheme of the ground collapse event.

[0130] Embodiment three

[0131] The embodiment provides a disaster event processing method, which is executed by a corresponding disaster event processing device, and the device is realized by software and / or hardware and integrated in a front-end management equipment in a network architecture as shown in Figure 1 or Figure 2 . Referring to Figure 5 , the method comprises the following steps 500-503.

[0132] Step 500, receiving a disaster event reported by a monitoring device in a jurisdictional region and recording to a disaster event list.

[0133] In this step 500, the disaster event list records a plurality of disaster events reported by each monitoring device in the jurisdictional region of the front-end management equipment. Each disaster event in the disaster event list contains a plurality of information fields for describing the specific circumstances of the event, such as: event identification, event name, occurrence time, occurrence place, event type, event level, casualty situation, event status, report source, reporter, reporter contact information, event description and the like. Among them, if the event name can uniquely identify the disaster event, the event identification information field can be omitted.

[0134] Step 501, obtaining a disaster event in the disaster event list as a main event.

[0135] In this step 501, each disaster event in the disaster event list can be specially marked after being reported and processed or canceled by the front-end management equipment, so that any one of the disaster events in the disaster event list which is not specially marked can be selected as the main event. Of course, each disaster event can also be deleted in the disaster event list after being reported and processed or canceled by the front-end management equipment, and any one of the disaster events in the current disaster event list can be selected as the main event in this way. Optionally, the disaster event list can also be backed up before step 501 is executed, and the disaster event list for backup does not perform the special marking and deletion processing of the disaster events, so as to facilitate subsequent consultation.

[0136] Step 502, determining other disaster events in the disaster event list that meet a preset repetition condition with the main event as the associated events of the main event.

[0137] In this step 502, the preset association relationship meeting with the main event is specifically a preset repetition condition meeting with the main event. Correspondingly, the process of determining the associated events can include:

[0138] screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event;

[0139] determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated events of the main event.

[0140] Specifically, other disaster events that are likely to be repeated with the main event can be initially screened out through the information fields of the disaster events such as the occurrence time, the occurrence place and the event type. For example, a disaster event of the same type occurring in the same or adjacent region within the same or similar time can be used as such an event, because a disaster event meeting the above three conditions is very likely to be the same disaster event reported by different personnel.

[0141] Subsequently, other disaster events that meet a certain repetition condition with the main event and can be information-merged can be further screened out from the initial screening results as the associated events of the main event. As an implementation manner, the content matching of the set information fields of the main event and other disaster events in the initial screening results is performed, and when the matching degree reaches a set threshold, it is determined that the other disaster event meets the preset repetition condition with the main event.

[0142] The disaster event can be the associated event of the main event. The set information fields can include at least one of the following information fields: the event name, the occurrence place and the event level. The content matching can be realized by using the existing semantic matching technology. When the set information fields are multiple, the matching degree reaching the set threshold can be understood as the content matching degree of each set information field reaching the set threshold.

[0143] As another implementation manner, the related personnel can also assist in completing the matching of the set information fields of the main event and other disaster events in the initial screening results by the man-machine interaction manner.

[0144] Specifically, the method comprises: displaying a main event and other disaster events screened out; and determining, according to a first selection operation on the displayed other disaster event 0, other disaster events meeting a preset repetition condition with the main event as associated events of the main event. When the main event and the screened other disaster events are displayed, all information field contents of the events can be displayed simultaneously. Preferably, the screened other disaster events can be displayed page by page, different other disaster events are displayed on different pages, and the main event is displayed on each page, and for the main event and the information field contents of the other disaster events on the same page, the common part and the different part 5 of the two can be displayed separately. In this way, the similarities and differences between the two disaster events can be intuitively displayed, and the selected other disaster event by the relevant personnel is taken as the associated event of the main event.

[0145] The similarities and differences between the two disaster events can be intuitively displayed, and the selected other disaster event by the relevant personnel is taken as the associated event of the main event.

[0146] Of course, in some specific application scenarios, the other disaster events in the preliminary screening result can also be directly taken as the associated events of the main event. It should be noted that if there is no associated event of the main event in the disaster event list, the main event is directly reported to the background server, so that the background server can deal with the received main event.

[0147] Step 503, reporting and processing the main event in combination with the associated events of the main event.

[0148] The processing operation in this step 503 is specifically reporting and processing, which comprises:

[0149] ① canceling the reporting and processing of the associated events of the main event;

[0150] ② performing information deduplication on the main event and the associated events, and updating the information of the main event based on the information deduplication result;

[0151] ③ reporting and processing the main event after the information is updated.

[0152] In specific implementation, the reporting and processing is reporting to the background server. In the operation ②, the information of the main event and the associated events can be deduplicated according to the information field. If for the same information field (except the event identifier field), the semantic matching of the corresponding content of the main event and the corresponding content of the associated event is complete, the information field content is repeated, and the content of the main event for the information field is not updated and remains unchanged; if for the same information field (except the event identifier field), the semantic matching of the corresponding content of the main event and the corresponding content of the associated event is only partial, then the corresponding content of the associated event with different semantics needs to be supplemented to the corresponding content of the main event.

[0153] Of course, the above-mentioned operation ② can also be completed by a person through human-computer interaction, specifically including: according to a second selection operation on the displayed information field of the associated event, updating the content of the corresponding information field in the main event. The second selection operation includes a preset information difference selection operation and / or an information coverage selection operation. When the second selection operation is the information difference selection operation, the specific updating process can include: supplementing the information field content of the selected associated event into the content of the corresponding information field in the main event. This updating method requires the relevant personnel to select the specific content in the information field of the associated event that is different from the corresponding information field in the main event. When the second selection operation is the information coverage selection operation, the content of the corresponding information field in the main event is directly overwritten by the information field content of the selected associated event. This updating method requires the relevant personnel to determine that the information field content of the associated event completely contains the content of the corresponding information field in the main event. For the information field of the associated event without the second selection operation, the content updating operation of the corresponding information field in the main event is not performed.

[0154] In the above-mentioned operation ③, the main event with updated information is reported to the background server, so that the background server can deal with the received main event.

[0155] On the basis of the above scheme of the embodiment, the disaster event processing method in the embodiment can further include:

[0156] Receiving the response and disposal results of the local reported disaster event from the background server; and counting the response and disposal results of the main event with updated information to determine whether to switch to a preset simple disaster event processing mode.

[0157] As a specific embodiment, the maintenance manner of the disaster event list is: after each disaster event is reported and processed, the event still exists in the table, but is specially marked to show that it has been reported, and the reporting time of the event by the front-end management device is recorded in the table optionally; if the event has associated events and has been processed through the information updating operation, the event merging mark is made to the event in the table; subsequently, the main event reported to the background server after the information updating is screened by querying the disaster event list. As another specific embodiment, the maintenance manner of the disaster event list is: after each disaster event is reported and processed, the event is deleted from the table, and relevant marks, records and queries of the event can be made in the backup disaster event list. The coping result can be coping success or failure. For example, if the number of disaster events with coping failure in each disaster event reported to the background server after the information updating within a statistical period exceeds a preset failure threshold or accounts for more than a preset percentage, it is judged to switch to a preset simple disaster event processing mode. In the simple mode, the steps 501-503 are no longer executed, and each disaster event in the disaster event list is simply reported.

[0158] It should be noted that the above step 500 in the embodiment is not necessarily executed, for example, the disaster event list can be generated and stored before the embodiment is executed.

[0159] Unlike the prior art, in the embodiment, the front-end management device does not simply and directly forward the disaster events sent by each monitoring device, but integrates the main event and its associated events together for information integration, removes and strips repeated information, and merges a new main event before reporting to the background server, which greatly reduces the number of reported disaster events, thereby preventing the background server from being occupied by too many storage resources, reducing the work intensity of the background server in disposing disaster events, and avoiding incomplete understanding of the disaster situation due to too scattered effective information related to the disaster, so that the rescue work can be more clearly focused and efficient and orderly.

[0160] Embodiment Four

[0161] The embodiment provides a disaster event processing method, which is executed by a corresponding disaster event processing device. Figure 1 or Figure 2 The device is realized by software and / or hardware and is integrated in a front-end management device in a network architecture as shown in Figure 6 . Referring to

[0162] Step 600, receiving a disaster event reported by a monitoring device in a jurisdictional region and recording to a disaster event list.

[0163] The step 600 is the same as the step 500 in the above-mentioned embodiment three, and will not be repeated here.

[0164] The step 601 acquires one disaster event in the disaster event list as a main event.

[0165] The step 601 is the same as the step 501 in the above-mentioned embodiment three, and will not be repeated here.

[0166] The step 602 determines other disaster events in the disaster event list that satisfy a preset secondary derivative relationship with the main event as the associated events of the main event.

[0167] In the step 602, the preset association relationship satisfied by the main event is specifically the preset secondary derivative relationship. Correspondingly, the process of determining the associated events can include:

[0168] The sub-step 6021 screens other disaster events in the disaster event list that have the same region, the same time period and different types as the main event.

[0169] The sub-step 6022 determines other disaster events that satisfy the preset secondary derivative relationship with the main event from the screened disaster events as the associated events of the main event.

[0170] The sub-step 6022 can specifically include: displaying the main event and the screened other disaster events; and determining, according to a third selection operation on the displayed other disaster events, other disaster events that satisfy the preset secondary derivative relationship with the main event. For example, the selected other disaster event in the display interface of the main event and the screened other disaster events is determined as the other disaster event that satisfies the preset secondary derivative relationship with the main event.

[0171] Preferably, the screened other disaster events can be displayed page by page, different other disaster events are displayed on different pages, and each page displays the main event, and the common part and the difference part of the information field content of the main event and the other disaster events in the same page can be displayed separately. In this way, the similarities and differences between two disaster events can be very intuitively displayed, and the selected other disaster event of the relevant personnel is determined as the associated event of the main event.

[0172] It should be noted that if the associated event of the main event does not exist in the disaster event list, the main event is directly reported to the background server, so that the background server can deal with the received main event.

[0173] The step 603 reports and processes the main event in combination with the associated events of the main event.

[0174] The processing operation in the step 603 is embodied as a reporting processing, which can include:

[0175] adding the associated event identifier of the main event in the information field content of the main event;

[0176] reporting the main event after the adding operation to the background server, so that the background server performs response treatment on the main event according to the response treatment scheme of the associated event.

[0177] The associated event identifier can be added in the event description information field of the main event. After receiving the main event sent by the front-end management device, the background server can determine other disaster events having secondary derivative relationship through the associated event identifier carried by the main event, and can also refer to the response treatment scheme of other disaster events having completed response treatment to perform response treatment on the main event, so that the information and disaster impact of the main event can be more perfect, and experience and reasonable scheme support can be provided for the rescue work of the main event.

[0178] Embodiment five

[0179] The embodiment provides a disaster event processing device, which is realized by software and / or hardware, and is integrated in the background server in the network architecture as shown in Figure 1 or Figure 2 . Referring to Figure 7 , the device comprises:

[0180] a main event acquisition unit 701, configured to acquire one disaster event in a disaster event list as a main event;

[0181] a repeated event determination unit 702, configured to determine other disaster events in the disaster event list meeting a preset repeated condition with the main event as associated events of the main event;

[0182] a main event processing unit 703, configured to perform response treatment on the main event in combination with the associated events of the main event.

[0183] The main event processing unit 703 comprises:

[0184] an event canceling sub-unit 7031, configured to cancel the response treatment on the associated events of the main event;

[0185] an event updating sub-unit 7032, configured to perform information deduplication on the main event and the associated events, and update the information of the main event based on the information deduplication result;

[0186] an event processing sub-unit 7033, configured to perform response treatment on the main event after the information update.

[0187] Furthermore, the repeating event determination unit 702 is used to determine other disaster events in the disaster event list that meet preset repeating conditions with the main event, as related events of the main event, specifically including:

[0188] Filter the list of disaster events that have the same geographical location, time period, and type as the main event;

[0189] From the selected disaster events, identify other disaster events that meet the preset repetition conditions with the main event, and treat them as related events of the main event.

[0190] Furthermore, the repeating event determination unit 702 is used to determine other disaster events from the selected disaster events that meet preset repeating conditions with the main event, as related events of the main event, specifically including:

[0191] Displays the main event and other filtered disaster events;

[0192] Based on the first selection operation on the other disaster events displayed, other disaster events that meet the preset repetition conditions with the main event are identified as related events of the main event;

[0193] Event update subunit 7032 is used to deduplicate information about the main event and its associated events, and update the information of the main event based on the deduplication result, including:

[0194] Based on the second selection operation on the information field of the displayed associated event, update the content of the corresponding information field in the main event, wherein the second selection operation includes a preset information difference selection operation and / or an information overwrite selection operation.

[0195] The disaster event handling device provided in this embodiment belongs to the same inventive concept as the aforementioned method embodiment one. Technical details not described in this device embodiment can be found in the relevant descriptions in the aforementioned method embodiment one, and will not be repeated here.

[0196] Example 6

[0197] This embodiment provides a disaster event handling device, which is implemented by software and / or hardware and integrated into a device such as... Figure 1 or Figure 2 In the backend server of the network architecture shown. See also Figure 8 The device includes:

[0198] The main event acquisition unit 801 is used to acquire a disaster event from the disaster event list as the main event;

[0199] Secondary derivative event determination unit 802 is used to determine other disaster events in the disaster event list that satisfy a preset secondary derivative relationship with the main event, as related events of the main event;

[0200] The main event processing unit 803 is configured to deal with the main event in combination with the associated event of the main event.

[0201] The secondary derivative event determination unit 802 is configured to determine other disaster events in the disaster event list that meet a preset secondary derivative relationship with the main event as the associated event of the main event, and specifically includes the following steps.

[0202] Screening other disaster events in the disaster event list that have the same region, the same time period, and different types as the main event.

[0203] Determining other disaster events that meet a preset secondary derivative relationship with the main event from the screened disaster events as the associated event of the main event.

[0204] For example, the secondary derivative event determination unit 802 is configured to determine other disaster events that meet a preset secondary derivative relationship with the main event from the screened disaster events as the associated event of the main event, and specifically includes the following steps.

[0205] Displaying the main event and the screened other disaster events.

[0206] According to a third selection operation on the displayed other disaster events, determining other disaster events that meet a preset secondary derivative relationship with the main event.

[0207] The disaster event processing device provided in this embodiment belongs to the same inventive concept as the second method embodiment, and the technical details not described in this device embodiment can be referred to the related description in the second method embodiment, which will not be described here.

[0208] Embodiment Seven

[0209] This embodiment provides a disaster event processing device, which is realized by software and / or hardware and integrated in a front-end management device in a network architecture as shown in Figure 1 or Figure 2 The device receives disaster events reported by monitoring devices in a jurisdictional region and records the disaster events to a disaster event list. Figure 9 The device includes:

[0210] The event receiving unit 900 is configured to receive disaster events reported by monitoring devices in a jurisdictional region and record the disaster events to a disaster event list.

[0211] The main event acquisition unit 901 is configured to acquire one disaster event in the disaster event list as a main event.

[0212] The repeated event determination unit 902 is configured to determine other disaster events in the disaster event list that meet a preset repeated condition with the main event as the associated event of the main event.

[0213] The main event processing unit 903 is configured to report the main event in combination with the associated event of the main event.

[0214] The main event processing unit 903 includes:

[0215] The event canceling sub-unit 9031 is configured to cancel the reporting processing of the associated event of the main event.

[0216] The event updating sub-unit 9032 is configured to perform information deduplication on the main event and the associated event, and update the information of the main event based on the information deduplication result.

[0217] The event processing sub-unit 9033 is configured to report the main event after information updating.

[0218] The event processing sub-unit 9033 is configured to process the main event after information updating, including: reporting the main event after information updating to a background server, so that the background server performs response and disposal on the received main event.

[0219] For example, the repeated event determining unit 902 is configured to determine other disaster events in the disaster event list that meet a preset repetition condition with the main event as the associated event of the main event, including:

[0220] Screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event.

[0221] Determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated event of the main event.

[0222] Further, the repeated event determining unit 902 is configured to determine other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated event of the main event, including:

[0223] Displaying the main event and the screened other disaster events.

[0224] According to a first selection operation on the displayed other disaster events, determining other disaster events that meet the preset repetition condition with the main event as the associated event of the main event.

[0225] The event updating sub-unit is configured to perform information deduplication on the main event and the associated event, and update the information of the main event based on the information deduplication result, including:

[0226] According to a second selection operation on the information field of the displayed associated event, updating the content of the corresponding information field in the main event, wherein the second selection operation includes a preset information difference selection operation and / or an information covering selection operation.

[0227] Based on the above solutions in this embodiment, the device further includes:

[0228] The response and handling result receiving unit 904 is used to receive the response and handling results of the disaster events that have been reported locally from the background server;

[0229] The mode switching judgment unit 905 is used to statistically analyze the response and handling results of the main event after the information update in the response and handling results received by the response and handling result receiving unit 904, so as to determine whether to switch to the preset simplified disaster event handling mode.

[0230] The disaster event handling device provided in this embodiment belongs to the same inventive concept as the aforementioned method embodiment three. Technical details not described in this device embodiment can be found in the relevant descriptions in the aforementioned method embodiment three, and will not be repeated here.

[0231] Example 8

[0232] This embodiment provides a disaster event handling device, which is implemented by software and / or hardware and integrated into a device such as... Figure 1 or Figure 2 In the front-end management device of the network architecture shown. See also Figure 10 The device includes:

[0233] The event receiving unit 1000 is used to receive disaster events reported by monitoring equipment within its jurisdiction and record them in the disaster event list.

[0234] The main event acquisition unit 1001 is used to acquire a disaster event from the disaster event list as the main event;

[0235] Secondary derivative event determination unit 1002 is used to determine other disaster events in the disaster event list that satisfy a preset secondary derivative relationship with the main event, as related events of the main event;

[0236] The main event processing unit 1003 is used to report the main event by combining the associated events of the main event.

[0237] The main event processing unit 1003 is used to process the main event by combining its associated events, specifically including:

[0238] Add the associated event identifier of the main event to the information field of the main event;

[0239] The main event after the addition operation is reported to the backend server so that the backend server can handle the main event according to the handling plan for the related events.

[0240] For example, the secondary derivative event determination unit 1002 is used to determine other disaster events in the disaster event list that satisfy a preset secondary derivative relationship with the main event, as related events of the main event, specifically including:

[0241] Filter the list of disaster events that have the same geographical location, time period, and type as the main event;

[0242] Other disaster events that satisfy a preset secondary derivative relationship with the main event are identified from the selected disaster events and are considered as related events of the main event.

[0243] The secondary derivative event determination unit 1002 is used to determine other disaster events from the selected disaster events that satisfy a preset secondary derivative relationship with the main event, as related events of the main event, specifically including:

[0244] Displays the main event and other filtered disaster events;

[0245] Based on the third selected operation on the other disaster events displayed, other disaster events that satisfy the preset secondary derivative relationship with the main event are identified.

[0246] The disaster event handling device provided in this embodiment belongs to the same inventive concept as the aforementioned method embodiment four. Technical details not described in this device embodiment can be found in the relevant descriptions in the aforementioned method embodiment four, and will not be repeated here.

[0247] also, Figure 11 This is a schematic diagram of the structure of an embodiment of the electronic device of the present invention, which can implement the process of any method embodiment of the present invention, such as... Figure 11 As shown, the aforementioned electronic device may include: a housing 1101, a processor 1102, a memory 1103, a circuit board 1104, and a power supply circuit 1105. The circuit board 1104 is disposed within the space enclosed by the housing 1101, and the processor 1102 and memory 1103 are disposed on the circuit board 1104. The power supply circuit 1105 is used to supply power to various circuits or devices of the aforementioned electronic device. The memory 1103 is used to store executable program code. The processor 1102 runs a program corresponding to the executable program code by reading the executable program code stored in the memory 1103, for executing the disaster event handling method described in any of the foregoing embodiments.

[0248] For details on the specific execution process of the above steps by processor 1102, and the steps further executed by processor 1102 through running executable program code, please refer to the present invention. Figures 3-10 The description of the illustrated embodiments will not be repeated here.

[0249] The electronic device has a disaster event processing method function, and exists in various forms, including but not limited to:

[0250] (1) Mobile communication device: The feature of this kind of device is to have mobile communication function, and to provide voice and data communication as the main target; this kind of terminal includes: smart phone (such as iPhone), multimedia phone, functional phone, and low-end phone, etc.;

[0251] (2) Ultra-mobile personal computer device: This kind of device belongs to the category of personal computer, has computing and processing function, and generally has mobile Internet feature; this kind of terminal includes: PDA, MID and UMPC device, such as iPad;

[0252] (3) Portable entertainment device: This kind of device can display and play multimedia content; this kind of device includes: audio and video player (such as iPod), palm game machine, electronic book, and smart toy and portable car navigation device;

[0253] (4) Server: The device providing computing service, the server structure includes processor, hard disk, memory, system bus, etc., the server and the general computer architecture are similar, but due to the need to provide high reliable service, therefore, in the processing capacity, stability, reliability, security, scalability, manageability, etc. Higher requirements;

[0254] (5) Other electronic devices with data communication and processing function.

[0255] Further, the embodiment of the present application also provides a computer readable storage medium, the computer readable storage medium stores one or more programs, the one or or more programs can be executed by one or more central processing units, so as to realize the disaster event processing method of any one of the foregoing method embodiments.

[0256] In the embodiment of the present application, the disaster event type division can be specifically as follows:

[0257] Natural disaster event: water and drought disaster event, meteorological disaster event, earthquake disaster event, geological disaster event, marine disaster event, forest disaster event, biological disaster event, and other natural disaster events;

[0258] Water and drought disaster event: waterlogging, reservoir major danger, embankment major danger, ice flood, mountain torrent, agricultural drought, urban water shortage, ecological drought, rural human and livestock drinking water difficulty, and other water and drought disasters;

[0259] Meteorological disaster events: typhoon, tornado, rainstorm, snow disaster, east tide, gale, sandstorm, low temperature frost disaster, freezing rain, high temperature weather, heat wave, dry hot wind, downburst, snow avalanche, lightning, hail, frost, heavy fog, haze, low-level wind shear, other meteorological disasters;

[0260] Earthquake disaster events: artificial earthquake, natural earthquake, other earthquake disasters;

[0261] Geological disaster events: landslide, debris flow, collapse, subsidence, ground fissure, ground subsidence, volcanic eruption, sea (water) intrusion, other geological disasters;

[0262] Marine disaster events: tsunami, storm surge, sea ice, giant wave, red tide, green tide, other marine disaster events;

[0263] Forest disaster events: domestic forest fire, cross-border forest fire, foreign threat to domestic forest fire, other forest fires, grassland fire, domestic grassland fire, cross-border grassland fire, foreign threat to domestic grassland fire, other grassland fires;

[0264] Biological disaster events: agricultural diseases, agricultural insect pests, agricultural grass damage, agricultural rat damage, forest diseases, forest insect pests, forest rat damage, forestry harmful plant events, foreign harmful animal and plant threats to agricultural production events, foreign harmful animal and plant threats to forestry production events, other biological disasters.

[0265] It should be noted that the relationship terms such as first and second in the present text are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the term "include", "contain" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or equipment. Without more limitation, the element defined by the statement "including a" does not exclude the existence of other identical elements in the process, method, article or equipment including the element.

[0266] The term "and / or" in the embodiments of the present application describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship.

[0267] The various embodiments in the specification are described in a related manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the difference from other embodiments.

[0268] Especially, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiments.

[0269] For the convenience of description, the above device is described in various units / modules respectively according to functions. Of course, the functions of each unit / module can be implemented in the same or multiple software and / or hardware when implementing the present application.

[0270] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by a computer program instructing relevant hardware. The program can be stored in a computer readable storage medium, and when the program is executed, it can include the processes of the above-mentioned embodiments. The storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM) or a random access memory (RAM), etc.

[0271] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A disaster event handling method characterized by comprising: The method comprises: acquiring one disaster event in a disaster event list as a main event, wherein the disaster event list records a plurality of disaster events generated by a monitoring device by analyzing collected data, and the disaster event needs to be reported to a background server for early warning; determining other disaster events in the disaster event list that meet a preset association relationship with the main event as associated events of the main event, wherein the preset association relationship includes a repetition condition or a secondary derivative relationship; processing the main event in combination with the associated events of the main event; when the preset association relationship is the repetition condition, the processing comprises: canceling the reporting processing of the associated events of the main event; performing information deduplication on the main event and its associated events, updating the information of the main event based on the information deduplication result; reporting the main event with updated information to the background server, so that the background server deals with the received main event; when the preset association relationship is the secondary derivative relationship, the processing comprises: adding an associated event identifier of the main event in the information field content of the main event; reporting the main event after the adding operation to the background server, so that the background server deals with the main event according to the response and disposal scheme of the associated event.

2. The method of claim 1, wherein, determining other disaster events in the disaster event list that meet a preset repetition condition with the main event as associated events of the main event, comprising: screening other disaster events in the disaster event list that have the same region, the same time period and the same type as the main event; determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated events of the main event.

3. The method of claim 2, wherein, determining other disaster events that meet the preset repetition condition with the main event from the screened disaster events as the associated events of the main event, comprising: displaying the main event and the screened other disaster events; determining other disaster events that meet the preset repetition condition with the main event as the associated events of the main event according to a first selection operation on the displayed other disaster events; performing information deduplication on the main event and its associated events, updating the information of the main event based on the information deduplication result, comprising: updating the content of the corresponding information field in the main event according to a second selection operation on the information field of the displayed associated event, wherein the second selection operation comprises a preset information difference selection operation and / or an information covering selection operation.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving a disaster event reported by a monitoring device in a jurisdictional region and recording it to a disaster event list.

5. The method of claim 4, wherein, The method further comprises: receiving a response and disposal result of a local reported disaster event issued by a background server; and counting the response and disposal result of the main event after the information update to determine whether to switch to a preset simple disaster event processing mode.

6. The method of claim 1, wherein, determining other disaster events in the disaster event list that meet a preset secondary derivative relationship with the main event as associated events of the main event, comprising: screening other disaster events in the disaster event list from the main event, which have the same region, the same time period and different types; determining other disaster events from the screened disaster events, which meet the preset secondary derivative relationship with the main event, as the associated events of the main event.

7. The method of claim 6, wherein, determining other disaster events from the screened disaster events, which meet the preset secondary derivative relationship with the main event, as the associated events of the main event, comprising: displaying the main event and the screened other disaster events; determining other disaster events from the displayed other disaster events, which meet the preset secondary derivative relationship with the main event, according to a third selection operation on the displayed other disaster events.

8. A disaster event processing apparatus characterized by comprising: The device comprises: a main event acquisition unit configured to acquire one disaster event in a disaster event list as a main event, wherein the disaster event list records a plurality of disaster events, and the disaster event is a disaster event generated by a monitoring device through analysis of collected data and needs to be reported to a background server for early warning; an associated event determination unit configured to determine other disaster events in the disaster event list, which meet a preset association relationship with the main event, as associated events of the main event, wherein the preset association relationship includes a repetition condition or a secondary derivative relationship; a main event processing unit configured to process the main event in combination with the associated events of the main event; when the preset association relationship is the repetition condition, the processing includes: canceling the reporting processing of the associated events of the main event; performing information deduplication on the main event and its associated events, updating the information of the main event based on the information deduplication result; and reporting the main event with updated information to the background server, so that the background server performs response and disposal on the received main event; when the preset association relationship is the secondary derivative relationship, the processing includes: adding an associated event identifier of the main event in the information field content of the main event; and reporting the main event after the adding operation to the background server, so that the background server performs response and disposal on the main event according to the response and disposal scheme of the associated event.

9. The apparatus of claim 8, wherein, The associated event determination unit is configured to determine other disaster events in the disaster event list, which meet a preset repetition condition with the main event, as the associated events of the main event, and specifically comprises: screening other disaster events in the disaster event list from the main event, which have the same region, the same time period and the same type; determining other disaster events from the screened disaster events, which meet the preset repetition condition with the main event, as the associated events of the main event.

10. The apparatus of claim 9, wherein, The associated event determination unit is configured to determine other disaster events from the screened disaster events, which meet the preset repetition condition with the main event, as the associated events of the main event, and specifically comprises: displaying the main event and the screened other disaster events; determining other disaster events from the displayed other disaster events, which meet the preset repetition condition with the main event, as the associated events of the main event, according to a first selection operation on the displayed other disaster events; The main event processing unit is configured to perform information deduplication on the main event and its associated events, update information of the main event based on a result of the information deduplication, and include the following: According to a second selection operation on an information field of the displayed associated event, the content of the corresponding information field in the main event is updated, wherein the second selection operation includes a preset information difference selection operation and / or an information overlay selection operation.

11. The apparatus of claim 8, wherein, The device further includes an event receiving unit configured to receive a disaster event reported by a monitoring device in a jurisdiction and record the disaster event to a disaster event list.

12. The apparatus of claim 11, wherein, The device further includes: A response and disposal result receiving unit configured to receive a response and disposal result of a disaster event reported by the local device from a background server; A mode switching judging unit configured to count the response and disposal result of the main event after the information update in the response and disposal result received by the response and disposal result receiving unit, and judge whether to switch to a preset simple disaster event processing mode.

13. The apparatus of claim 8, wherein, The associated event determining unit is configured to determine other disaster events in the disaster event list that satisfy a preset secondary derivative relationship with the main event as the associated events of the main event, and specifically includes: Screening other disaster events in the disaster event list that have the same region, the same time period and different types as the main event; Determining other disaster events that satisfy the preset secondary derivative relationship with the main event from the screened disaster events as the associated events of the main event.

14. The apparatus of claim 13, wherein, The associated event determining unit is configured to determine other disaster events that satisfy the preset secondary derivative relationship with the main event from the screened disaster events as the associated events of the main event, and specifically includes: Displaying the main event and the screened other disaster events; Determining other disaster events that satisfy the preset secondary derivative relationship with the main event according to a third selection operation on the displayed other disaster events.

15. An electronic device, comprising: The electronic device includes a housing, a processor, a memory, a circuit board and a power supply circuit, wherein the circuit board is arranged inside a space enclosed by the housing, the processor and the memory are arranged on the circuit board; the power supply circuit is configured to supply power to each circuit or device of the electronic device; the memory is configured to store executable program codes; the processor is configured to run programs corresponding to the executable program codes by reading the executable program codes stored in the memory, and execute the method of any one of claims 1-7.

16. A computer-readable storage medium, characterized in that, The computer readable storage medium stores one or more programs, which can be executed by one or more central processing units to implement the method of any one of claims 1-7.

Images