JP5266633B2 - Disaster notification system, disaster notification method, and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform notification of a disaster etc. more quickly and efficiently than before. <P>SOLUTION: A disaster information notification control device 1 is provided with; a disaster report reception part 101 which receives a report of a disaster event; a notification content decision part 102 which decides a notification object person who is a target of notification of the disaster event and the notification content; a notification instruction part 104 which instructs an email server 21 etc. to perform notification of the disaster event to the decided notification object person; a disaster notification history table TD1 which stores the disaster notification log data 7D1 which indicates the disaster event which is notified and the target person of the notification; and a duplicate notification discrimination part 103 which discriminates an already notified person to whom the notification of the disaster event is already given based on other reports based on the disaster notification log data 7D1. The notification instruction part 104 is made not to perform notification about the same disaster event to the person who is discriminated by the duplicate notification discrimination part 103 as the person who is already notified. <P>COPYRIGHT: (C)2008,JPO&amp;INPIT

Description

  The present invention relates to a system and method for notifying a disaster or the like.

  When a disaster such as a fire or flood occurs, or an event such as a heavy rain or an earthquake that causes a disaster occurs, prompt notification of such information to the person in the area where the event occurred may cause damage. Important in minimizing.

  An organization such as a company or a government office may request that safety be reported at the time of notification of a disaster or the like so that the safety of the member can be quickly confirmed.

As a means for performing a notification of a disaster or the like and confirming safety, a safety confirmation device has been proposed as described in Patent Document 1. This safety confirmation device includes a disaster detection device, a processing device, and a database. The disaster detection device notifies the processing device when a disaster larger than a preset size is detected. The processing device refers to the database and issues safety confirmation information by e-mail to the response terminal in the area where the activated disaster detection device is installed. The response terminal responds that the user or the company or group is safe. The processing device posts a list of safety confirmations and response statuses for each individual, company, and group on the network, transmits confirmation information again to individuals and groups that do not respond, and updates the information in real time. The confirmation terminal is a terminal used for inquiries from a third party, browses information posted on the network by the processing device, and grasps the situation of the disaster area.
Japanese Patent Laid-Open No. 2002-312879

  By the way, it is necessary to notify disasters quickly and efficiently. If it can be done, it will be possible to collect safety information more quickly than before.

  The present invention has been made in view of such problems, and an object of the present invention is to provide notification of a disaster or the like more quickly and efficiently than in the past.

The disaster notification system according to the present invention includes a disaster event report receiving unit that receives a report indicating a disaster event that is a disaster event or an event that may cause a disaster, and the disaster event report receiving unit that receives the report Each time the report is received by the disaster event report receiving means, the notification target person determining means for determining the notification target person who is to be notified of the disaster event shown in the report, and the disaster shown in the report Notification control processing means for performing notification control processing for performing notification of an event on the notification target person of the disaster event determined by the notification target person determination means, and notification by the notification control processing means Notification log data storage means for storing notification log data indicating the disaster event performed and the other party of the notification; and Each time the event report is accepted by the event report accepting means, the already-notified person who has already been notified by the notification control process based on another report is notified to the notice log data storage means. the notification log data stored is less than or equal to the disaster event scale is shown to the report of the same similar accidents event is the disaster event are the same as or similar to disaster events indicated in the report non-global An already-notified person determining means for determining that the person is a partner shown together with a scale disaster event, and the notification target person determining means is configured to identify the notification target person of the disaster event indicated in the report as the disaster event. The already-notified person determined by the already-notified person determination means that the notification has already been performed by the notification control process based on another report is excluded from the candidates. To.

Preferably, the disaster event report accepting unit accepts, as the report, a report indicating the disaster event and a disaster location where the disaster event has occurred or has reached, and the notification log data storage unit includes: The notification log data is stored as notification log data indicating the disaster event notified by the notification control process and the other party of the notification, and indicating the disaster location of the disaster event, The same-similar disaster that has occurred or has occurred in a place within a predetermined distance from the disaster location indicated in the report in the notification log data stored in the notification log data storage means determines that the counterpart shown with the non-major disasters events of events.

  According to the present invention, notification of a disaster or the like can be performed more quickly and efficiently than before.

  FIG. 1 is a diagram illustrating an example of the overall configuration of the disaster information providing system DSY, and FIG. 2 is a diagram illustrating an example of a functional configuration of the disaster information notification control device 1.

  As shown in FIG. 1, the disaster information provision system DSY according to the present invention includes a disaster information notification control device 1, an electronic mail server 21, a message transmission device 22, a fax transmission device 23, a voice guidance device 24, and a safety information provision server 3. And disaster information input terminal 4 and the like. These can be connected to each other via the communication line NW1. As the communication line NW1, a LAN line, the Internet, a public line, a dedicated line, or the like is used.

  This disaster information provision system DSY provides information on the occurrence of disasters such as fires or floods, information on the occurrence of high-risk events (for example, earthquakes, typhoons, heavy rains, storms, tsunamis, etc.) It mainly provides information on safety. Hereinafter, an event with a high risk of causing a disaster is referred to as a “disaster risk event”. Information relating to the occurrence of a disaster and information relating to the occurrence of a hazardous disaster event are described as “disaster information”, and information relating to the safety of a person is described as “safety information”.

  The disaster information is provided by the disaster information notification control device 1 controlling the electronic mail server 21, the message transmission device 22, the FAX transmission device 23, and the voice guidance device 24. However, as will be described later, this disaster information can be obtained only by a person who has performed a predetermined procedure in advance.

  Further, according to the service of the disaster information notification control device 1, the same disaster information can be distributed to a plurality of members belonging to a specific group (for example, companies, local governments, families, relatives, neighborhood associations, etc.). it can. However, in order to use this service, it is necessary to perform a predetermined procedure relating to the group in advance, as will be described later.

  The safety information is provided by the safety information providing server 3. Safety information can be obtained by anyone without restriction.

  The hard disk of the disaster information notification control apparatus 1 includes a disaster report reception unit 101, a notification content determination unit 102, a duplicate notification determination unit 103, a notification command unit 104, a user definition table TA1, and a group definition table TA2 as shown in FIG. , Event list table TB1, similar event definition table TB2, parent-child event definition table TB3, same region definition table TB4, effective time definition table TB5, notification setting table TC1, disaster notification history table TD1, and other programs for realizing functions And data is installed. These programs and data are loaded into the RAM as required, and the programs are executed by the CPU.

  As the disaster information notification control device 1, a workstation, a so-called server machine, a personal computer, or the like is used.

  The e-mail server 21 is an existing e-mail server. In this embodiment, the e-mail server 21 transmits disaster information by e-mail according to a command given from the disaster information notification control device 1.

  The message transmission device 22 has an existing messenger function. In the present embodiment, the message transmission device 22 transmits disaster information by a message called IM (Instant Message) according to a command given from the disaster information notification control device 1.

  The FAX transmission device 23 is an existing FAX transmission device. In the present embodiment, the FAX transmission device 23 transmits disaster information according to a fax protocol such as G3 or G4 according to a command given from the disaster information notification control device 1.

  The voice guidance device 24 is a so-called existing voice guidance device that calls a partner's telephone and transmits a synthesized voice or a voice recorded in advance. In the present embodiment, in particular, disaster information is transmitted by voice in accordance with a command given from the disaster information notification control device 1.

  As described above, the safety information providing server 3 performs a process of providing safety information. Moreover, the process which collects safety information is also performed. As the safety information providing server 3, a Web server having a bulletin board CGI (Common Gateway Interface) is used. Alternatively, a disaster message board system already operated by a communication carrier or ASP (Application Service Provider) may be used. For example, the following known technique 1 may be used.

[Prior Art 1] NTT West, “Disaster Broadband Message Board (web171)”, URL http://www.ntt-west.co.jp/dengon/web171/about_web171.html
The disaster information input terminal 4 is a terminal device for inputting disaster information to the disaster information notification control device 1. As the disaster information input terminal 4, a personal computer, a workstation, a mobile phone terminal or the like is used.

  The electronic mail server 21, the message transmission device 22, the FAX transmission device 23, the voice guidance device 24, and the safety information providing server 3 can be connected to the terminal device TR via the communication line NW2. The terminal device TR is a device for receiving information related to a disaster or a disaster hazard event. As the terminal device TR, a personal computer, a PDA (Personal Digital Assistant), a mobile phone terminal, a so-called fixed telephone, a FAX terminal, or the like is used. As the communication line NW2, the Internet, a telephone line, a wireless LAN line, a power line, a cable broadcasting line, and other various lines are used.

  The disaster information notification control device 1 can be connected to the disaster event detection device DKS via the communication line NW2.

  The disaster event detection device DKS is a device that detects a disaster hazard event. For example, an earthquake sensor or a rain gauge.

  3 shows an example of the user definition table TA1, FIG. 4 shows an example of the group definition table TA2, FIG. 5 shows an example of the event list table TB1, and FIG. 6 shows an example of the notification setting table TC1. FIG. 7 is a flowchart for explaining an example of the flow of notification command processing.

  Next, processing contents and functions of each unit of the disaster information notification control apparatus 1 shown in FIG. 2 will be described in detail.

  As shown in FIG. 3, the user definition table TA1 stores user data 7A1 for each person who receives a service for providing disaster information by the disaster information providing system DSY (hereinafter referred to as “user”).

  In the user data 7A1, “user ID” is identification information for identifying a user related to the user data 7A1. “User name” is the name or name of the user.

  “Notification destination-1”, “Notification destination-2”, and “Notification destination-3” all indicate notification destinations when notifying the user of disaster information. In these fields, an electronic mail address, an IP address, a telephone number, a mobile phone number, a FAX number, or the like of the terminal device TR of the user is set. As will be described later, notification of disaster information is preferentially attempted in the order of “notification destination-1”, “notification destination-2”, and “notification destination-3”.

  The user adds his / her e-mail address, telephone number, mobile phone number, FAX number, IM IP address, and various other addresses to “notification destination-1” to “notification destination-3” of his / her user data 7A1. Alternatively, a number can be freely set as a notification destination. At least one of the notification destinations must be set.

  As shown in FIG. 4, the group definition table TA2 stores group data 7A2 for each group that receives a service for distributing disaster information to members.

  In the group data 7A2, “group ID” is identification information for identifying a group related to the group data 7A2. “Group name” is the name of the group. “Configuration user ID” indicates a user ID for each user belonging to the group.

  The event list table TB1 stores event data 7B1 for each disaster and disaster risk event as shown in FIG. Hereinafter, events such as disasters and disaster risk events are collectively referred to as “disaster events”. In the present embodiment, a disaster event is defined by combining a type of an event (event, event) such as a fire, an earthquake, or a rain and a level of the scale in principle. For example, for “fire”, disaster events of “large scale fire”, “medium scale fire”, “small scale fire”, and “small fire” are defined according to four levels.

  In the event data 7B1, “event ID” is identification information for identifying an event related to the event data 7B1. “Event name” is the name of the disaster event. “Scale” indicates the scale of the disaster event.

  In the notification setting table TC1, data regarding what kind of information should be notified to the user in accordance with a disaster event that has occurred or has occurred is set. Specifically, as shown in FIG. 6, a plurality of notification setting data 7C1 is stored in the notification setting table TC1.

  This notification setting data 7C1 belongs to the group related to the group ID shown in the “target group ID” when the disaster event related to the event ID shown in the “event ID” occurs in the area shown in the “region”. This indicates that information indicated in “notification content” is notified to the user. “Notification setting ID” is identification information for identifying the notification setting data 7C1.

  The data of each table described above is prepared by the administrator of the disaster information notification control device 1 according to the attributes and requests of each group and its members received via e-mail, FAX, or website. The It is also modified, deleted, or added as necessary.

  The disaster report receiving unit 101 performs processing for receiving a report that a disaster event has occurred or has occurred. Specifically, the report is received by receiving the disaster report data 8A from the disaster event detection device DKS or the disaster information input terminal 4.

  That is, the disaster event detection device DKS detects the disaster event when the disaster event occurs or reaches, and the contents of the disaster event (the event ID of the disaster event, the event name, the region, the point, and the event occurred or reached) Disaster report data 8A indicating the date and time) is generated. Then, the disaster report data 8A is transmitted to the disaster information notification control device 1. The disaster report receiving unit 101 receives the disaster report data 8A.

  Alternatively, when a disaster event occurs or reaches, the person in charge of disaster prevention promptly inputs the contents of the disaster event to the disaster information input terminal 4. The disaster information input terminal 4 transmits disaster report data 8A indicating the input content to the disaster information notification control device 1. The disaster report receiving unit 101 receives the disaster report data 8A.

  The “point” is a specific place where the disaster event has occurred or has occurred. For example, if the disaster event is related to a fire such as “Large-scale fire” or “Medium-scale fire”, it is desirable that the address be a detailed address, such as “1-2 prefecture CC city, CC town 1-2-3”. When the event is related to the weather such as “high rainfall”, the details may be such as “AA prefecture BB city” that can specify the range covered by the event. On the other hand, “region” means a range wider than “point”, such as “Kanto”, “Chubu”, or “Kansai”.

  The notification content etc. determination unit 102 performs processing to determine what information should be notified to the user belonging to which group regarding the disaster event reported this time. Specifically, a process for determining which of the notification setting data 7C1 stored in the notification setting table TC1 (see FIG. 6) is to be notified is performed. Such processing is performed, for example, as follows.

  The notification content etc. determination unit 102 searches the notification setting table TC1 for notification setting data 7C1 indicating the event ID and the area indicated in the disaster report data 8A received by the disaster report receiving unit 101. And it will determine, if notification is performed based on the searched notification setting data 7C1.

  Alternatively, when a measured value (for example, seismic intensity, rainfall per unit time, etc.) is shown in the disaster report data 8A instead of the event ID and the event name, the notification content etc. determining unit 102 may determine the measured value based on the measured value. It may be determined what disaster events have occurred or have occurred. Then, the notification setting data 7C1 indicating the identified event ID of the disaster event and the area indicated in the disaster report data 8A is searched from the notification setting table TC1, and the notification is determined based on the search.

  Based on the notification setting data 7C1 determined by the notification content etc. determination unit 102, the notification command unit 104 performs processing for notifying the user of information related to the disaster event related to the current report. The processing procedure is as shown in the flowchart of FIG.

  In FIG. 7, the notification command unit 104 calls the user data 7A1 of the user who should be notified of information related to the disaster event related to the current report from the user definition table TA1 (see FIG. 3) as follows (# 501).

  The group ID indicated by the “target group ID” of the notification setting data 7C1 determined by the notification content etc. determination unit 102 is checked. The group data 7A2 related to the group ID is searched from the group definition table TA2 (see FIG. 4). Then, the user data 7A1 related to each user ID indicated in the “configuration user ID” of the group data 7A2 is called from the user definition table TA1.

  Attention is paid to any one of the called user data 7A1 (# 503). Hereinafter, the user related to the noticed user data 7A1 will be referred to as “attention user”.

  The duplicate notification determination unit 103 is caused to execute a duplicate notification determination process for the user of interest (# 504). The significance and procedure of such processing will be described in detail later. As a result, when it is determined that the notice regarding the current disaster event has already been given to the noticed user (Yes in # 505), the notice to the noticed user is not performed. If it is determined that notification regarding the current disaster event has not been made (No in # 505), the following processing is continued.

  The e-mail server 21, the message transmission device 22, the FAX transmission device 23, and the voice guidance so as to notify the information about the current disaster event to the notification destination indicated by “notification destination-1” of the noticed user data 7A1. A command is given to one of the devices 24 as follows (# 507).

  If the type of the notification destination is an e-mail address, the notification command unit 104 transmits information indicated by “notification content” of the notification setting data 7C1 to the notification destination (e-mail address) by e-mail. As described above, a command is given to the electronic mail server 21.

  When the type of the notification destination is IM identification information (such as an IP address or a host name), the notification command unit 104 uses the IM to send the information indicated in the “notification content” of the notification setting data 7C1 to the notification destination ( A command is given to the message transmission device 22 so that the message is transmitted to the computer having the IP address.

  When the type of the notification destination is a FAX number, the notification command unit 104 transmits the information indicated by “notification contents” of the notification setting data 7C1 to the notification destination (FAX number FAX terminal) as FAX data. In this way, a command is given to the FAX transmitter 23.

  When the type of the notification destination is a telephone number, the notification command unit 104 gives a command to the voice guidance device 24 so as to notify the information indicated by “notification contents” of the notification setting data 7C1 by voice. .

  The e-mail server 21 or the voice guidance device 24 tries to notify the information indicated in the “notification content” of the notification setting data 7C1 by each method according to the command from the disaster information notification control device 1.

  If the notification could not be completed (No in # 508), the information on the current disaster event is addressed to the notification destination related to the user's next priority (that is, the notification destination indicated by “notification destination-2”). In response to the type of the notification destination, an instruction is given to any of the electronic mail server 21, the message transmission device 22, the FAX transmission device 23, and the voice guidance device 24 (# 507).

  If the notification could not be completed (No in # 508), the current disaster event is addressed to the notification destination related to the next priority of the user (that is, the notification destination indicated by “notification destination-3”). An instruction is given to any of the electronic mail server 21, the message transmission device 22, the FAX transmission device 23, and the voice guidance device 24 in accordance with the type of notification destination (# 507). .

  If any of the notification destinations “notification destination-1” to “notification destination-3” cannot be notified (No in # 508 and Yes in # 509), the notification to the user is suspended (# 511). Then, after a while, try to notify again.

  When the notification to any of the notification destinations “notification destination-1” to “notification destination-3” is normally completed (Yes in # 508) or when the notification is suspended, the user data called in step # 501 Of the 7A1, attention is paid to those not yet noticed (# 503), and the above-described processing of steps # 506 to # 511 is executed based on the noticed user data 7A1.

  8 shows an example of the disaster notification history table TD1, FIG. 9 shows an example of the similar event definition table TB2, FIG. 10 shows an example of the parent-child event definition table TB3, and FIG. 11 shows the same area definition table TB4. FIG. 12 is a diagram illustrating an example of the valid time definition table TB5, and FIG. 13 is a flowchart illustrating an example of the flow of duplicate notification determination processing.

  Returning to FIG. 2, the disaster notification history table TD <b> 1 is a history record regarding notifications made by the email server 21, the message transmission device 22, the FAX transmission device 23, or the voice guidance device 24 based on a command from the notification command unit 104. Store the data. Specifically, every time notification to one user is completed, disaster notification log data 7D1 related to the notification is stored in the disaster notification history table TD1, as shown in FIG. For the sake of space, the disaster notification history table TD1 is shown divided into two stages.

  In the disaster notification log data 7D1, “notification destination user ID” indicates the user ID of the user of the notification partner. “Notification destination address” indicates an e-mail address, IP address, FAX number, or telephone number used as a notification destination of the notification.

  “Notification event ID” indicates an event ID of a disaster event related to the notification. “Region”, “point”, and “date / time” respectively indicate the area, point, and date / time at which the disaster event related to the notification occurred or reached. “Notification content” indicates a message (message) notified this time. “Notification ID” is identification information for identifying the disaster notification log data 7D1.

  By the way, one user may belong to a plurality of groups. The notification content etc. determination unit 102 may determine that a plurality of notification setting data 7C1 should be used for notification based on one disaster report data 8A. In addition, a plurality of disaster information input terminals 4 or disaster event detection devices DKS may make a report about one disaster event. In addition, one disaster information input terminal 4 or disaster event detection device DKS may report a plurality of times for one disaster event.

  Therefore, one user may become a target person who receives notification several times for one disaster event. Therefore, if a notification is made without any restrictions, a single user is notified of the same disaster event, traffic is unnecessarily increased, communication resources are insufficient, and communication failure occurs. May happen. Also, it is troublesome for the user to receive notifications about a single disaster event many times.

  Therefore, when the disaster report data 8A of the disaster event to be notified is received, the duplicate notification determination unit 103 receives the similar event definition table TB2, the parent / child event definition table TB3, the same area definition table TB4, the effective time definition table TB5, In addition, in cooperation with the disaster notification history table TD1 or the like, a process (duplicate notification determination process) is performed to determine whether or not the same disaster event is being performed for the same user.

  Similar event definition table TB2 stores similar event data 7B2 for each event classification in which a plurality of similar disaster events are classified as shown in FIG.

  In the similar event data 7B2, the “classification ID” is identification information for identifying the event classification related to the similar event data 7B2. “Category name” is the name of the event classification. “Similar event” indicates an event ID of a disaster event corresponding to the event classification.

  In the parent-child event definition table TB3, as shown in FIG. 10, parent-child event data 7B3 that defines the magnitude relationship of the scales of all or some of the disaster events belonging to the same event category is stored. Specifically, in the parent-child event data 7B3, all or some of the disaster events belonging to the same event classification are set as “parent events” and the other disaster events are set as “child events”. This defines the magnitude relationship.

  In the parent-child event data 7B3, the “parent-child ID” is identification information for identifying the magnitude relationship (parent-child relationship) related to the parent-child event data 7B3. “Parent Event ID” indicates the event ID of the parent event among the disaster events related to the magnitude relationship. “Child event ID” indicates an event ID of a child event among the disaster events related to the magnitude relationship.

  In the same area definition table TB4, as shown in FIG. 11, for each disaster event, both disasters occur when the same or similar disaster event has occurred or has occurred within a predetermined period in the past. The same area data 7B4 that defines whether the event is considered to be the same event (event, event) is stored.

  In the valid time definition table TB5, as shown in FIG. 12, for each disaster event, the same or similar disaster event has occurred or has occurred within a predetermined distance within any past period. The effective time data 7B5 that defines whether both disaster events are considered to be the same event (event, incident) is stored.

  Each data of the similar event definition table TB2 to the effective time definition table TB5 is prepared in advance by the administrator of the disaster information notification control device 1 according to the characteristics of each disaster event.

  The disaster notification log data 7D1 stored in the disaster notification history table TD1 is as described above with reference to FIG.

  The duplicate notification discriminating unit 103 cooperates with these tables and duplicates the same user (the attention user in the process described in FIG. 7) for the same disaster event in the procedure shown in the flowchart of FIG. Determine the notification you are about to do.

  In FIG. 13, similar event data in which the event ID of the disaster event (hereinafter referred to as “the present disaster event”) related to the disaster report data 8 </ b> A received this time by the disaster report receiving unit 101 is indicated by “similar event ID”. 7B2 is called from the similar event definition table TB2 (# 521).

  The parent-child event data 7B3 whose event ID of the disaster event is indicated by “child event ID” is called from the parent-child event definition table TB3 (# 522). Depending on the present disaster event, no parent-child event data 7B3 may be called, only one may be called, or a plurality may be called.

  The same area data 7B4 and effective time data 7B5 related to the disaster event are called from the same area definition table TB4 and effective time definition table TB5, respectively (# 523, # 524).

Based on these called data, it is checked whether or not the disaster notification log data 7D1 that satisfies all the following requirements (Requirement 1) to (Requirement 6) is stored in the disaster notification history table TD1 (# 525). .
(Requirement 1) The disaster notification log data 7D1 related to the user ID of the user of interest. That is, the disaster notification log data 7D1 related to the notification made to the user of interest.
(Requirement 2) The disaster notification log data 7D1 related to the event ID indicated in the “similar event ID” of the similar event data 7B2. That is, it is the disaster notification log data 7D1 related to the notification regarding the same or similar disaster event as the present disaster event.
(Requirement 3) The disaster notification log data 7D1 does not indicate the event ID indicated by any “parent event ID” of the parent-child event data 7B3. That is, it is the disaster notification log data 7D1 of a disaster event that is not larger in scale than the present disaster event.
(Requirement 4) Disaster notification log data related to a disaster event that occurred or extended within the distance indicated in the “same area range” of the same area data 7B4 as the distance from the point where the disaster event occurred or extended 7D1. That is, the disaster notification log data 7D1 related to the disaster event within a predetermined range near the disaster event.
(Requirement 5) The disaster notification log data 7D1 related to the disaster event that occurred or reached within the “effective time” of the effective time data 7B5 retroactively from the date and time when the disaster event occurred or reached. That is, it is disaster notification log data 7D1 related to a disaster event that has just occurred.
(Requirement 6) The disaster notification log data 7D1 related to notification of substantially the same business as the business related to the disaster event.

  If at least one disaster notification log data 7D1 that satisfies all of these requirements is found (Yes in # 526), it is determined that notification of this disaster event has already been made to the user of interest (# 527). In other words, it is determined that the notification that the notification command unit 104 is about to give to the user of interest this time overlaps with notifications that have been made in the past.

  On the other hand, if no such disaster notification log data 7D1 is found (No in # 526), it is determined that notification of the disaster event has not been made to the user of interest (# 528). That is, it is determined that there is no duplication even if the notice user is notified this time.

  This determination result is used for determining whether or not notification of the disaster event described above in step # 505 of FIG. That is, the notification command unit 104 notifies the noticed user of the disaster event when the overlap notification determination unit 103 determines that there is no overlap. If it is determined that there is an overlap, the notification to the user of interest is canceled.

  Whether or not (Requirement 6) is satisfied can be determined by a known parsing method. For example, the keywords of the notification content related to the disaster event and the notification content of the disaster notification log data 7D1 are extracted by the method described in the document of the publicly known technology 2 below. If the extracted keywords match, it is determined that the notification contents are substantially the same, and if they do not match, it is determined that they are different.

[Prior Art 2] Japanese Patent Application Laid-Open No. 6-215035 The keyword comparison may be performed for each of the disaster event and the user's request. Then, when the events related to the disaster events of both notifications match and the requirements for the user match, it is determined that they are substantially the same, and if either of them does not match, it may be determined that they are different.

  For example, the notification content related to the disaster event includes a request that a large-scale earthquake has occurred in the Chubu region and that safety registration be performed, and the notification content of the disaster notification log data 7D1 If a local incident and a request to condemn the nearest evacuation site are included, the disaster events for both notifications are the same, but the requirements are different. Therefore, it is determined that the notification contents of both notifications are different.

  FIG. 14 is a flowchart for explaining an example of the overall processing flow of the disaster information notification control device 1 and the safety information providing server 3.

  Next, the flow of processing of the disaster information notification control device 1 and the flow of processing of the safety information providing server 3 when a disaster event occurs or has occurred will be described with reference to flowcharts.

  When the safety information providing server 3 or the disaster information input terminal 4 detects a disaster event, the disaster report data 8A of the disaster event is transmitted to the disaster information notification control device 1.

  In FIG. 14A, when the disaster information notification control device 1 receives the disaster report data 8A (Yes in # 11), it determines which group member is to be notified of what requirements (#). 12). That is, the notification setting data 7C1 is determined.

  A command is given to the e-mail server 21 or the voice guidance device 24 so as to notify each user based on the determined notification setting data 7C1 (# 13). The procedure of this process is as described above with reference to FIGS.

  Then, a log of notification made to each user, that is, disaster notification log data 7D1 is recorded (# 14).

  The user who has received the notification must register his / her safety information in the safety information providing server 3 as necessary.

  In FIG.14 (b), if the safety information provision server 3 receives the information regarding safety from the terminal device TR (Yes in # 31), it will register it in a database (# 32). This information is provided for viewing.

  When a browsing request is received from the terminal device TR (No in # 31, Yes in # 33), the safety information registered in the database is transmitted to the terminal device TR (# 34).

  According to the present embodiment, even if a single disaster event is reported multiple times, notification of the disaster event can be prevented from being repeated for the same user. Further, even when one user belongs to a plurality of groups, it is possible to prevent a single notification of a disaster event from being repeated for the same user. Therefore, the notification of the disaster event can be performed more quickly and efficiently than before.

  In this embodiment, e-mail notification is executed by the e-mail server 21, IM notification is executed by the message transmission device 22, FAX notification is executed by the FAX transmission device 23, and voice notification is made by the voice guidance device 24. However, these notifications may be executed by a single device.

  In this embodiment, the disaster information notification control device 1 has received the disaster report data 8A from the disaster information input terminal 4 or the disaster event detection device DKS, but distributes weather information, earthquake information, disaster information, crime information, or the like. You may accept from public or private institutions.

  In the present embodiment, as described with reference to FIG. 3, up to three notification destinations can be registered for one user, but more notification destinations may be registered.

  In addition, the entire disaster information providing system DSY, the disaster information notification control apparatus 1 or the configuration of each part, the processing content, the processing order, the table configuration, and the like can be appropriately changed in accordance with the spirit of the present invention.

In the embodiment described above, the following notes are also disclosed.
(Appendix 1)
A disaster event report receiving means for receiving a report of a disaster event that is a disaster event or a risk of causing a disaster;
Notification target person determination means for determining a notification target person who is a partner to be notified of the disaster event related to the report;
Each time the report is received by the disaster event report receiving unit, the notification of the disaster event related to the report is performed for the notification target person of the disaster event determined by the notification target person determining unit. Notification control processing means for executing notification control processing;
Notification log data storage means for storing the disaster event notified by the notification control process and notification log data indicating the other party of the notification;
Each time the report is accepted by the disaster event report accepting means, the notification log is used to notify a previously notified person who has already been notified by the notification control processing based on another report of the disaster event related to the report. Determining based on the notification log data stored in the data storage means;
Have
The notification target person determination means determines the notification target person of the disaster event related to the report by the already notified person determination means that the notification of the disaster event has already been performed by the notification control process based on another report. The above-mentioned notified person who has been notified is excluded from the candidates and determined.
A disaster notification system characterized by that.
(Appendix 2)
The disaster event report accepting unit accepts, as the report, a report indicating the disaster event and indicating a disaster location where the disaster event has occurred or has reached,
The notification log data storage means stores, as the notification log data, notification log data indicating the disaster event notified by the notification control process and the other party of the notification and indicating the occurrence location of the disaster event. ,
The notified person discriminating means is configured to detect the disaster event that is the same as or similar to the disaster event related to the report and that has occurred or has reached a location within a predetermined distance from the disaster location indicated in the report. Determining the notification partner indicated in the notification log data to be the already notified person,
The disaster notification system according to appendix 1.
(Appendix 3)
The disaster event report accepting unit accepts, as the report, a report indicating the disaster event and indicating a disaster date and time that is the date and time when the disaster event has occurred or has reached,
The notification log data storage means stores, as the notification log data, notification log data indicating the date and time of occurrence of the disaster event indicating the disaster event notified by the notification control process and the other party of the notification,
The already-notified person identification unit is configured to identify the disaster event that is the same as or similar to the disaster event related to the report and that has occurred or has reached within a predetermined time from the disaster date and time indicated in the report. Determining the notification partner indicated in the notification log data to be the already notified person,
The disaster notification system according to appendix 1 or appendix 2.
(Appendix 4)
A notification destination storage means for storing a plurality of notification destinations for each person who can be the notification target,
The notification control processing means performs a process for notifying one of the notification target persons, stored in the notification destination storage means, as the notification control process for the notification target person, In addition, if the notification destination cannot be notified, a process for notification to any other notification destination of the notification target person is performed.
The disaster notification system according to any one of appendix 1 to appendix 3.
(Appendix 5)
The notification control processing means, as the notification control processing, performs processing for notification of the disaster event and the business to the other party,
The notification log data storage means stores, as the notification log data, notification log data indicating the requirements together with the disaster event and the notification partner,
The already-notified person determination means indicates the same item as the one that is the same as or similar to the disaster event related to the report and that is to be notified together with the disaster event by the notification control process. Determining that the notification partner indicated in the notification log data is the notified person;
The disaster notification system according to any one of appendix 1 to appendix 4.
(Appendix 6)
A disaster notification system for notifying a disaster event that is a disaster event or an event that may cause a disaster,
Notification condition data storage means for storing notification condition data indicating what kind of disaster event should be notified to which group member;
When the disaster event has occurred or has occurred, a notification of a requirement corresponding to each group is given to a member of the group to be notified of the disaster event shown in the notification condition data, and A notification control processing means for executing a notification control process so that notification of the same message is performed only once for members belonging to a plurality of members of the group;
A disaster notification system characterized by comprising:
(Appendix 7)
Each time a disaster event report is received that is a disaster event or a risky event,
On the computer,
A notification target person determination process for determining a notification target person to be notified of the disaster event related to the report;
A notification control process for performing notification of the disaster event related to the report to the notification target person of the disaster event determined by the notification target person determination process;
A notification log data storage unit that stores the disaster event notified by the notification control process and the notification log data indicating the other party of the notification, and
Based on the notification log data stored in the notification log data storage means, the already-notified person who has already been notified by the notification control process based on another report is notified of the disaster event related to the report. The already-notified person determination process for determining is executed before the notification control process,
In the notification target person determination process, the notification target person of the disaster event related to the report is determined by the already notified person determination process that the disaster event has already been performed by the notification control process based on another report. Exclude the previously notified person and determine
A disaster notification method characterized by that.
(Appendix 8)
The notification control process is a process for instructing any one of an e-mail server, a FAX server, a messenger, or a voice guidance device so as to notify the notification target person of the disaster event related to the report. Is,
The disaster notification method described.
(Appendix 9)
Each time a disaster event report is received that is a disaster event or a risky event,
On the computer,
A notification target person determination process for determining a notification target person to be notified of the disaster event related to the report;
A notification control process for performing notification of the disaster event related to the report to the notification target person of the disaster event determined by the notification target person determination process;
A notification log data storage unit that stores the disaster event notified by the notification control process and the notification log data indicating the other party of the notification, and
Based on the notification log data stored in the notification log data storage means, the already-notified person who has already been notified by the notification control process based on another report is notified of the disaster event related to the report. The notified person determination process for determining is executed before the notification control process, and
In the computer, from the candidate for the notification target of the disaster event related to the report, the notification of the disaster event has already been determined by the notification control processing based on another report, and the notification destination determination processing has determined Excluding the already notified person and causing the notification target person determination process to be executed,
A computer program characterized by the above.

It is a figure which shows the example of the whole structure of a disaster information provision system. It is a figure which shows the example of a functional structure of a disaster information notification control apparatus. It is a figure which shows the example of a user definition table. It is a figure which shows the example of a group definition table. It is a figure which shows the example of an event list table. It is a figure which shows the example of a notification setting table. It is a flowchart explaining the example of the flow of a notification command process. It is a figure which shows the example of a disaster notification log | history table. It is a figure which shows the example of a similar event definition table. It is a figure which shows the example of a parent-child event definition table. It is a figure which shows the example of the same area definition table. It is a figure which shows the example of an effective time definition table. It is a flowchart explaining the example of the flow of a duplication notification discrimination | determination process. It is a flowchart explaining the example of the flow of the whole process of a disaster information notification control apparatus and a safety information provision server.

Explanation of symbols

1 Disaster Information Notification Control Device (Disaster Notification System)
101 Disaster Report Reception Department (Disaster Event Report Reception Unit)
8A Disaster report data 102 Notification content etc. decision part (notification target person discrimination means)
104 Notification command section (notification control processing means)
TD1 Disaster notification history table (notification log data storage means)
7D1 Disaster notification log data (notification log data)
103 Duplicate notification discriminating unit (notified person discrimination means)
TA1 user definition table (notification destination storage means)
TC1 notification setting table (notification condition data storage means)
7C1 Notification setting data (Notification condition data)

Claims (7)

A disaster event report accepting means for accepting a report indicating a disaster event that is a disaster event or an event at risk of causing a disaster;
Notification target person determination means for determining a notification target person to be notified of the disaster event shown in the report received by the disaster event report reception means;
Each time the report is received by the disaster event report receiving means, the notification of the disaster event indicated in the report is made to the notification target person of the disaster event determined by the notification target person determining means. Notification control processing means for executing the notification control processing of
Notification log data storage means for storing the disaster event notified by the notification control processing means and notification log data indicating the other party of the notification;
Each time the report is received by the disaster event report receiving means, the notification of the disaster event indicated in the report has already been notified by the notification control process based on another report. The disaster event whose magnitude is indicated in the report among the same similar disaster events that are the same or similar to the disaster event indicated in the report in the notification log data stored in the log data storage means A notified person determination means for determining that the person is a partner shown together with the following non-large-scale disaster event ;
Have
The notification target person determination unit determines that the notification target person of the disaster event indicated in the report is the notification target person determination unit that the notification of the disaster event has already been performed by the notification control process based on another report. Excluding the determined notified person from the candidates and determining,
A disaster notification system characterized by that. The disaster event report accepting unit accepts, as the report, a report indicating the disaster event and indicating a disaster location where the disaster event has occurred or has reached,
The notification log data storage means stores, as the notification log data, notification log data indicating the disaster event notified by the notification control process and the other party of the notification and indicating the disaster location of the disaster event. ,
The notified person determination means generates the notified person in a place within a predetermined distance from the disaster place indicated in the report in the notification log data stored in the notification log data storage means, or It is determined that it is a partner shown together with the non-large-scale disaster event among the same similar disaster events that have spread.
The disaster notification system according to claim 1. The disaster event report accepting unit accepts, as the report, a report indicating the disaster event and indicating a disaster date and time that is the date and time when the disaster event has occurred or has reached,
The notification log data storage means stores, as the notification log data, notification log data indicating the disaster date and time of the disaster event indicating the disaster event notified by the notification control process and the other party of the notification,
The notified person determination means generates the notified person within a predetermined time from the disaster date and time indicated in the report in the notification log data stored in the notification log data storage means, or It is determined that it is a partner shown together with the non-large-scale disaster event among the same similar disaster events that have spread.
The disaster notification system according to claim 1 or 2. A notification destination storage means for storing a plurality of notification destinations for each person who can be the notification target,
The notification control processing means performs a process for notifying one of the notification target persons, stored in the notification destination storage means, as the notification control process for the notification target person, In addition, if the notification destination cannot be notified, a process for notification to any other notification destination of the notification target person is performed.
The disaster notification system according to any one of claims 1 to 3. The notification control processing means, as the notification control processing, performs processing for notification of the disaster event and the business to the other party,
The notification log data storage means stores, as the notification log data, notification log data indicating the requirements together with the disaster event and the notification partner,
The already-notified person determination unit is configured to notify the already-notified person to the notification log data stored in the notification log data storage unit, not only the non-large-scale disaster event among the same similar disaster events, It is determined that the other party is shown together with the same business as the business to be notified together with the disaster event shown in the report.
The disaster notification system according to any one of claims 1 to 4. Every time a report is received indicating a disaster event that is a disaster event or a risky event,
On the computer,
Notification target person determination processing for determining a notification target person to be notified of the disaster event shown in the report;
A notification control process for performing notification of the disaster event shown in the report to the notification target person of the disaster event determined by the notification target person determination process;
A notification log data storage unit that stores the disaster event notified by the notification control process and the notification log data indicating the other party of the notification, and
In the notification log data stored in the notification log data storage means, the already-notified person who has already been notified by the notification control process based on another report is notified of the disaster event indicated in the report. Previous notification to determine that the disaster event shown in the report or a similar disaster event is the other party shown with a non-large-scale disaster event whose magnitude is less than or equal to the disaster event shown in the report Person determination processing is executed before the notification control processing,
In the notification target person determination process, the notification target person of the disaster event indicated in the report is determined by the already notified person determination process that the disaster event has already been performed by the notification control process based on another report. To discriminate by excluding the notified person who has been notified,
A disaster notification method characterized by that. Every time a report is received indicating a disaster event that is a disaster event or a risky event,
On the computer,
Notification target person determination processing for determining a notification target person to be notified of the disaster event shown in the report;
A notification control process for performing notification of the disaster event shown in the report to the notification target person of the disaster event determined by the notification target person determination process;
A notification log data storage unit that stores the disaster event notified by the notification control process and the notification log data indicating the other party of the notification, and
In the notification log data stored in the notification log data storage means, the already-notified person who has already been notified by the notification control process based on another report is notified of the disaster event indicated in the report. Previous notification to determine that the disaster event shown in the report or a similar disaster event is the other party shown with a non-large-scale disaster event whose magnitude is less than or equal to the disaster event shown in the report Person identification processing is executed before the notification control processing, and
It is determined by the already-notified person determination process that the notification of the disaster event has already been performed by the notification control process based on another report from the candidates for the notification target of the disaster event indicated in the report. Excluding the already notified person and causing the notification target person determination process to be executed.
A computer program characterized by the above.

Images