JP2023135830A - Notification management device, notification management system, and notification management method - Google Patents

Abstract

To easily and safely operate the registration and management of contact information for disaster notification information for a facility user.SOLUTION: A notification management system includes a registration portion that registers contact information of a facility user, a storage portion that stores registered contacts, a notification portion that sends notification information regarding the disaster to contacts stored in the storage portion when a disaster occurs at the facility, and a deletion portion that deletes registered contact information from the storage portion in response to the end of the user's period of stay at the facility.SELECTED DRAWING: Figure 1

Description

The present invention relates to a notification management device, a notification management system, and a notification management method.

Fire alarm information systems are constructed with the main purpose of notifying the disaster prevention center, and direct calls using emergency telephones or mobile phones are generally used to contact related parties outside the disaster prevention center. . General building users inside the building where the fire has occurred are informed using bells and emergency broadcasts, but information may not be accurately grasped due to people missing the broadcasts, etc. Furthermore, it is difficult to make hearing-impaired people fully aware of the occurrence of a fire.
Patent Document 1 describes a fire alarm that can notify many people, including hearing-impaired people, of the occurrence of a fire by flashing a light. According to this fire alarm, if a person knows in advance that the blinking means that a fire has occurred, the person can understand the occurrence of a fire in response to the blinking. However, people who do not know that flashing signals the occurrence of a fire will not be able to understand what the flashing signals.

Japanese Patent Application Publication No. 2006-302203

In order to solve the above problems, methods are being considered for notifying building users of fire information from fire alarms via the Internet or the like. However, many notifications use dedicated applications, and it is particularly difficult to encourage general building users and temporary visitors to adopt applications. Furthermore, except for the owner, management company, etc., it is desirable that fire information not be notified to users who are not in the building (general building users and people who have left the building). Additionally, it is conceivable that the system may collect the contact information of terminals, etc. owned by the user in order to notify the user, but the collected contact information of the user is confidential information, and from the perspective of information management, the system may collect the contact information of the terminal etc. It is desirable to discard contact information of users who do not need it. Also, from the user's perspective, it is undesirable for contact information to remain on the system.

Therefore, an object of the present invention is to provide a notification management device, a notification management system, and a notification management method that solve the above-mentioned problems.

One aspect of the present invention includes a registration unit that registers contact information of facility users, a storage unit that stores the registered contact information, and a storage unit that stores notification information regarding the disaster when a disaster occurs at the facility. a notification unit that sends the notification to the contact information stored in the storage unit; and a deletion unit that deletes the registered contact information from the storage unit in response to the end of the period of stay of the user at the facility. A notification management device having:

Further, one aspect of the present invention provides a user terminal that registers contact information of facility users, a storage unit that stores the registered contact information, and a user terminal that stores information about the disaster when a disaster occurs at the facility. a notification unit that sends notification information to a contact stored in the storage unit; and a notification unit that deletes the registered contact from the storage unit in response to the end of the period of stay of the user at the facility. A notification management system having a deletion unit.

Further, one aspect of the present invention is to register contact information of users of a facility, store the registered contact information in a storage unit, and, when a disaster occurs at the facility, notify information regarding the disaster to the The notification management method includes transmitting the notification to a contact stored in a storage and deleting the registered contact from the storage when the user's allowed stay period at the facility ends.

According to the present invention, it is possible to prevent the contact information of disaster-related notification information for facility users from remaining registered, and because of the low risk of leakage and the ease of registration, the notification information By lowering psychological barriers and increasing registration, more users can be notified of emergency information such as disasters.

1 is a schematic configuration diagram of a notification management system according to a first embodiment of the present invention. FIG. 2 is a schematic diagram showing a data structure and data example of a database stored in the notification management device according to the first embodiment of the present invention. FIG. 2 is an image diagram showing an example of a bulletin board prompting registration of a contact address according to the first embodiment of the present invention. FIG. 2 is an image diagram showing an example of a registration page according to the first embodiment of the present invention. FIG. 2 is a sequence diagram showing the operation of registration processing of the notification management system according to the first embodiment of the present invention. FIG. 3 is an image diagram showing an example of a registration completion message according to the first embodiment of the present invention. It is an image diagram showing an example of a message notifying disaster information according to the first embodiment of the present invention. It is an image diagram showing an example of an evacuation page according to the first embodiment of the present invention. FIG. 3 is an image diagram showing an example of a registration deletion notification message according to the first embodiment of the present invention. FIG. 2 is a sequence diagram showing the operation of registration extension processing of the notification management system according to the first embodiment of the present invention. FIG. 2 is a sequence diagram showing the operation of registration deletion processing over time in the notification management system according to the first embodiment of the present invention. FIG. 2 is a sequence diagram showing the operation of registration deletion processing by a user in the notification management system according to the first embodiment of the present invention. FIG. 2 is a schematic configuration diagram of a notification management system according to a second embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS A notification management device, a notification management system, and a notification management method according to an embodiment of the present invention will be described below with reference to the drawings.

[First embodiment]
First, a first embodiment will be described.
FIG. 1 is a schematic configuration diagram of a notification management system according to this embodiment.
The notification management system 1 provides disaster information (notification information) regarding disasters such as fires and earthquakes that occur in commercial facilities such as shopping malls and theme parks, hospitals, and accommodation facilities to users of the facilities (visitors to the commercial facilities). This is a system that notifies an unspecified number of people present at the facility, such as inpatients at hospitals, guests at accommodation facilities, etc. The disaster information is, for example, a fire alarm, an earthquake early warning, or an evacuation order from a disaster prevention center.
The notification management system 1 includes a notification management device 10 and a user terminal 20.

The notification management device 10 is a server device that centrally controls the notification management system 1.
The user terminal 20 is a mobile terminal carried by a user of the facility. The user terminal 20 is a terminal such as a smartphone or a mobile phone that can use a message service that can send text data to a phone number and can use voice calls. The message service may be, for example, a short message service, an automated voice message service capable of sending voice messages.
The notification management device 10 and the user terminal 20 are connected for communication via a network such as the Internet or a mobile phone network.

The notification management device 10 includes an acquisition section 101 , a registration section 102 , a storage section 103 , a notification section 104 , a deletion section 105 , and an extension section 106 .
The acquisition unit 101 receives from the user terminal 20 and acquires registration information including the contact address of the user of the facility and the length of time the user is allowed to stay at the facility. The contact address in this embodiment is the telephone number of the user terminal 20.
The registration unit 102 writes and registers the acquired contact address in the database of the storage unit 103 as the contact address for disaster information regarding a disaster that has occurred at the facility, together with the user's allowable stay period at the facility.
The storage unit 103 includes a database that stores contact addresses for disaster information related to disasters that occur at the facility, together with the user's allowable stay period at the facility, and a memory for temporary storage.
The period of stay may be from the time when the user's contact information is registered on the day the user uses the facility until the most recent end of the facility's availability. Furthermore, if the user specifies a possible stay period in advance, the specified possible stay period may be used as the possible stay period.

When a disaster occurs at a facility, the notification unit 104 transmits disaster information regarding the disaster to a contact address stored in the database of the storage unit 103 using a short message service. The notification unit 104 notifies disaster information in facilities where users stay all day long, such as accommodation facilities and hospitals, as long as contact addresses are registered. On the other hand, in a facility where the facility's available hours are fixed, even if a contact address is registered, the notification unit 104 notifies the disaster information only during the available hours, and notifies the disaster information outside the available hours. No notification. The available hours are, for example, business hours of commercial facilities. The disaster information describes a link destination that allows access to at least one of the following: a map showing the location of the disaster at the time of the disaster, information showing the evacuation route, and information on the congestion situation on the evacuation route.

The deletion unit 105 deletes the registered contact address from the database of the storage unit 103 in response to the end of the user's stay period at the facility. At this time, the deletion unit 105 notifies the user that the contact address will be deleted, and then deletes the registered contact address. Furthermore, when notifying the user that the address is to be deleted, the deletion unit 105 also notifies the user that the length of stay can be extended.
The extension unit 106 extends the period of stay of the user at the facility.

The user terminal 20 includes a transmitting section 201, a receiving section 202, and a display section 203.
The transmitting unit 201 transmits and registers the contact address of the facility user and the user's permitted stay period at the facility to the notification management device 10 .
The receiving unit 202 receives disaster information regarding a disaster that has occurred at a facility using a short message service.
The display unit 203 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display, and displays the received disaster information.

FIG. 2 is a schematic diagram showing a data structure and data example of a database stored in the notification management device according to the present embodiment.
The database stores the following items in correspondence: contact address, scheduled length of stay, language, automatic deletion, and notifications other than disaster information.
The contact address is a telephone number to be contacted for disaster information. The planned stay period is the period during which the user is allowed to stay at the facility. The language is the language in which disaster information is notified. Automatic deletion indicates whether or not the registered contact address is automatically deleted after the available time of the facility ends. Notification other than disaster information indicates whether or not notification other than disaster information is to be sent to the corresponding contact address. Notifications other than disaster information include, for example, in the case of a commercial facility, notices of time sales, events, coupons, etc., and in the case of accommodation facilities, notifications from the front desk, etc.

In the illustrated example, the planned stay period corresponding to the contact address "080-1234-5678" is "until 2022/01/29 17:00", the language is "Japanese", and the automatic deletion is "Yes". ", and for notifications other than disaster information, "do". In addition, the planned stay period corresponding to the contact address "090-9876-5432" is "until 2022/01/30 21:00", the language is "English", and automatic deletion is "no", Notifications other than disaster information are “no”.

Next, the operation of the notification management system 1 will be explained.
FIG. 3 is an image diagram showing an example of a bulletin board prompting the user to register a contact address according to the present embodiment.
This notice will be posted at the entrance of the facility, the place of stay, etc. In the illustrated example, a message A11 urging registration and a two-dimensional code A12 such as a QR (Quick Response) code (registered trademark) are posted. Message A11 states that by simply registering a telephone number as a contact address, it is possible to receive disaster information for the facility by SMS (Short Message Service) or the like. This allows users to know that they can receive disaster information by simply registering their phone number when they visit the facility. If the facility is a commercial facility, users may be able to visit the facility without making a reservation to use the facility. In such cases, you can register your contact information on the day you use the facility, at the time you arrive, or during your stay at the facility. The message A11 also states that the registered telephone number will be deleted from the notification management system 1 after the end of use of the facility. This allows the user to know that the registered phone number will be automatically deleted after the end of using the facility, and can register with a sense of security. Therefore, by writing such a message A11, registration of a telephone number can be promoted. Code A12 indicates the URL (Uniform Resource Locator) of a web page (hereinafter referred to as "registration page") for registering the contact address of the user of the facility.

The user can display the registration page on the user terminal 20 by having the user terminal 20 read the code A12. The user terminal 20 reads the URL of the registration page from the posted code A12, accesses the read URL, and displays the registration page.

FIG. 4 is an image diagram showing an example of a registration page according to this embodiment.
A registration page exists for each facility for which disaster information is to be notified, and a code that specifies the target facility is set in advance. In the example shown in this figure, the registration page includes an input field A21 for a telephone number, an input field A22 for the language in which disaster information will be notified, and an input field A23 for the expected length of stay for the user at the facility. Input field A24 for selecting whether to automatically delete the phone number after the end of the time (business hours in this example), input field A25 for selecting whether to send notifications other than disaster information, and each input field. A registration button A26 for registering the input contents (hereinafter referred to as "registration information") in the notification management system 1 is provided.
The input field A22 for the language and the input field A23 for the planned length of stay may be configured so that input items can be selected from pull-down menus. Furthermore, the end time of the facility's usable time may be preset as an initial value in the input field A23 for the planned stay period. Further, the planned stay period may be limited depending on the purpose of the facility. For example, in a commercial facility, the planned length of stay may be set only until the end of business hours. In addition, input field A24 for selecting whether to automatically delete the phone number after the available time ends, and input field A25 for selecting whether to send notifications other than disaster information, are set to "Yes" or "No". The selection may be made by checking a checkbox.
The length of stay can be specified by the user. In addition, even if the user does not specify a period of stay, the initial value is from the time the user's contact information is registered on the day the facility is used until the most recent end of the facility's availability. may be set and changed by the user as necessary.

FIG. 5 is a sequence diagram showing the operation of the registration process of the notification management system according to this embodiment.
First, the user terminal 20 acquires the URL of the registration page from the code A12 posted at the entrance of the facility (step S101). Then, the user terminal 20 accesses the URL of the registration page and requests the registration page from the notification management device 10 in response to the user's operation (step S102). The acquisition unit 101 of the notification management device 10 transmits a registration page to the user terminal 20 in response to a request from the user terminal 20 (step S103). At this time, if the acquisition unit 101 of the notification management device 10 is able to acquire the language settings of the user terminal 20, it transmits a registration page written in that language, and If the settings cannot be obtained, a registration page written in a preset multi-language will be sent. The user terminal 20 receives the registration page and displays the received registration page. The user terminal 20 then accepts input of registration information on the displayed registration page (step S104). The user inputs registration information into the registration page and presses the registration button A26 displayed on the registration page.

When the registration button A26 on the registration page is pressed, the user terminal 20 transmits the registration information input in each of the input fields A21 to A25 on the registration page to the notification management device 10 (step S105). The registered information includes the phone number, language, expected length of stay, information indicating whether the phone number will be automatically deleted after the available time ends, and information indicating whether notifications other than disaster information will be sent. is included. Upon receiving the registration information from the user terminal 20, the acquisition unit 101 of the notification management device 10 generates an authentication code with an arbitrary number of digits (for example, 4 digits). Then, the acquisition unit 101 of the notification management device 10 transmits an authentication code setting page for inputting an authentication code to the user terminal 20 (step S106). At this time, the acquisition unit 101 of the notification management device 10 transmits to the user terminal 20 an authentication code setting page written in the language included in the received registration information. The user terminal 20 displays the received authentication code setting page and accepts input of the authentication code. Subsequently, the acquisition unit 101 of the notification management device 10 transmits the generated authentication code to the telephone number included in the received registration information using the short message service (step S107). Then, the acquisition unit 101 of the notification management device 10 starts an authentication time timer (for example, 5 minutes) that is a deadline for authenticating the authentication code. The user inputs the authentication code received by the user terminal 20 through the short message service into the authentication code setting page. The user terminal 20 transmits the authentication code input on the authentication code setting page to the notification management device 10 (step S108).

The acquisition unit 101 of the notification management device 10 determines whether the authentication code received from the user terminal 20 matches the generated authentication code. If the authentication codes do not match, or if the authentication time timer elapses before receiving the authentication code, the acquisition unit 101 of the notification management device 10 sends an error page indicating that authentication has failed to the user terminal. Send to 20. On the other hand, if the authentication codes received within the time limit of the authentication margin timer match, the registration unit 102 of the notification management device 10 writes and registers the received registration information in the database (step S109). Then, the registration unit 102 of the notification management device 10 transmits a registration completion page indicating that registration of registration information is completed to the user terminal 20 (step S110). The user terminal 20 receives the registration completion page and displays the received registration completion page. Subsequently, the registration unit 102 of the notification management device 10 transmits a registration completion message indicating that the registration of registration information has been completed to the registered telephone number using the short message service (step S111). The user terminal 20 receives the registration completion message using the short message service, and displays the received registration completion message.

FIG. 6 is an image diagram showing an example of a registration completion message according to this embodiment.
This figure shows an example of a screen displayed on the user terminal 20 when the registration completion message is received. In the example shown in the figure, the registration completion message A30 describes that the registration of the telephone number has been completed. In this way, by sending a registration completion message to the registered phone number, the user can know that the phone number has been correctly registered. Further, the registration completion message A30 describes a link destination URL 31 of a web page (hereinafter referred to as "deletion page") for deleting the registration of a telephone number. The user can delete the registered telephone number from the notification management system 1 by performing the procedure from the deletion page.

When a disaster such as a fire occurs in a facility, the notification unit 104 of the notification management device 10 transmits disaster information regarding the disaster to a registered telephone number using a short message service or the like.

FIG. 7 is an image diagram showing an example of a message notifying disaster information according to this embodiment.
This figure shows an example of a screen displayed on the user terminal 20 when a message notifying disaster information regarding a fire outbreak is received. In the example shown in this figure, the user terminal 20 first receives a message A41 informing that a fire has occurred in the facility and urging evacuation, and then receives a message A42 informing the location of the fire. Thereafter, the user terminal 20 receives a message A43 containing information for evacuation. Message A43 describes a link URL 44 of a web page (hereinafter referred to as "evacuation page") that discloses information for evacuation. The user terminal 20 accesses the URL 44 described in the message A43 in response to the user's operation, and displays the evacuation page.

FIG. 8 is an image diagram showing an example of an evacuation page according to this embodiment.
The evacuation page includes at least one of a map showing the location of the disaster at the time of the disaster, information showing the evacuation route, and information on the congestion situation on the evacuation route. In the example shown in this figure, the evacuation page includes a flame mark MK52 indicating the place where the fire occurred and a mark MK53 indicating the crowded place on the map MP51 of the facility where the evacuation exit is marked. are displayed superimposed. In this way, by indicating the location of the fire on the map with a mark, the user can easily understand the location of the fire. Additionally, since evacuation exits and corridors connected to the evacuation exits are displayed on the map, users can understand the evacuation route. In addition, since crowded places are marked on the map, users can understand the congestion situation within the facility and can evacuate to avoid crowded places. This allows users to evacuate quickly. Note that the evacuation page is updated at any time according to the situation within the facility, and users can obtain the latest disaster information by reloading the evacuation page.

Note that if the available hours (for example, business hours) of the facility are determined, the notification unit 104 of the notification management device 10 notifies the disaster information only during the available hours. In other words, the notification unit 104 of the notification management device 10 does not notify disaster information outside of facility usage hours. This is because it is thought that there are no users of the facility outside of available hours. This can prevent unnecessary notifications from being sent to users who are not at the facility.

In addition, if the registration information stored in the database of the storage unit 103 indicates that notifications other than disaster information are “Yes”, the notification unit 104 of the notification management device 10 sends notifications other than disaster information to the contact address. Implemented against. For example, in the case of a commercial facility, the notification unit 104 of the notification management device 10 provides notifications of time sales, events, coupons, etc. In addition, in the case of an accommodation facility, the notification unit 104 of the notification management device 10 notifies the user of a contact from the front desk, etc. On the other hand, the notification unit 104 of the notification management device 10 does not perform notifications other than disaster information when notifications other than disaster information are set to "no".

Then, at a predetermined time (for example, 10 minutes) before the end of the registered scheduled stay period, the deletion unit 105 of the notification management device 10 sends a registration deletion notification message to notify deletion of the registered telephone number. The message will be sent to the specified phone number using short message service, etc.

FIG. 9 is an image diagram showing an example of a registration deletion notification message according to this embodiment.
This figure shows an example of the screen of the user terminal 20 that has received the registration deletion notification message. In the example shown in the figure, the registration deletion notification message A60 states that the registered planned stay period has ended and that the registered telephone number is to be deleted from the notification management system 1. Further, the registration deletion notification message A60 describes a link destination URL 61 of a web page for extending the registration (hereinafter referred to as "time extension page"). Users can extend their planned length of stay by completing the procedures on the time extension page.

FIG. 10 is a sequence diagram showing the operation of the registration extension process of the notification management system according to this embodiment.
The deletion unit 105 of the notification management device 10 sends a registration deletion notification message to the corresponding phone number using a short message service at a predetermined time (for example, 10 minutes) before the end of the scheduled stay period registered in the database. (Step S201). The user terminal 20 displays the received registration deletion notification message. If the user wishes to extend the stay time, the user accesses the URL written in the registration deletion notification message. The user terminal 20 requests the notification management device 10 for a time extension page in response to the user's operation (step S202).

When the time extension page is requested from the user terminal 20, the extension unit 106 of the notification management device 10 transmits the time extension page to the user terminal 20 (step S203). The user terminal 20 receives the time extension page, displays the received time extension page, and accepts setting input for extending the scheduled stay time (step S204). Then, the user terminal 20 transmits the extended scheduled stay period on the time extension page to the notification management device 10 (step S205). The extension unit 106 of the notification management device 10 updates the scheduled length of stay registered in the database to the received scheduled length of stay (step S206). Then, the extension unit 106 of the notification management device 10 transmits a message notifying that the scheduled period of stay has been extended to the user terminal 20 using the short message service (step S207).

FIG. 11 is a sequence diagram showing the operation of the registration deletion process over time in the notification management system according to the present embodiment.
The deletion unit 105 of the notification management device 10 sends a registration deletion notification message to the corresponding phone number using a short message service at a predetermined time (for example, 10 minutes) before the end of the scheduled stay period registered in the database. (Step S301). Thereafter, when the scheduled stay period has elapsed, the deletion unit 105 of the notification management device 10 deletes the registered information for which the scheduled stay period has elapsed from the database (step S302).

Note that even before the scheduled stay period ends, the deletion unit 105 of the notification management device 10 deletes the registered information from the database if it receives a message approving deletion of the registered information from the user terminal 20. Good too.
Further, the deletion unit 105 of the notification management device 10 deletes the registered information for which automatic deletion is set to "Yes" from the database when the preset available time of the facility has elapsed.
Further, the deletion unit 105 of the notification management device 10 may delete all contact addresses from the database on a preset inventory date.

FIG. 12 is a sequence diagram showing the operation of registration deletion processing by a user in the notification management system according to this embodiment.
The user can perform procedures to delete registered information on the deletion page described in the registration completion message. The user terminal 20 requests the notification management device 10 for a deletion page in response to the user's operation (step S401). The deletion unit 105 of the notification management device 10 transmits a deletion page to the user terminal 20 in response to a request from the user terminal 20 (step S402). The user terminal 20 displays the received deletion page and accepts an input for deletion approval (step S403). The user terminal 20 then transmits a request to delete the registered information to the notification management device 10 in response to the user's operation (step S404). The deletion request includes the telephone number to be deleted. The deletion unit 105 of the notification management device 10 writes the registration information of the telephone number included in the received deletion request to a temporary storage memory and deletes it from the database (step S405). Thereafter, the deletion unit 105 of the notification management device 10 sends a message notifying that the registered information has been deleted to the phone number written in the temporary storage memory using the short message service (step S406). Thereafter, the deletion unit 105 of the notification management device 10 deletes the telephone number from the temporary storage memory (step S407).

Generally, it is better not to notify people who are not in the facility where the disaster occurred regarding disaster information such as fire. Furthermore, even if disaster information about the facility is received after the facility user has used the facility, it may not be useful information. Furthermore, some users do not like it if their contact address remains on the system after using the facility. Therefore, there is a desire to promptly destroy the registered contact address after using the facility.

On the other hand, according to the present embodiment, the notification management system 1 uses the user terminal 20 for registering the contact address of the facility user, and the registered contact address for the user's possible stay period at the facility. a notification unit 104 that sends notification information regarding the disaster to the contact address stored in the storage unit 103 when a disaster occurs at the facility; and a notification unit 104 that sends notification information regarding the disaster to the contact address stored in the storage unit 103. and a deletion unit 105 that deletes the registered contact address from the storage unit 103 in response to the request.

Thereby, the registered contact address can be automatically deleted according to the end of the user's period of stay at the facility. Therefore, it is possible to prevent users who are not present at the facility from being notified of disaster information that has occurred at the facility. Furthermore, since the contact address is automatically deleted after the allowed stay period has elapsed, it is possible to give a sense of security to the user who registers the contact address, making it easier to register. In addition, since the notification management system 1 does not need to manage users' personal information, it is possible to lower the registration hurdle by minimizing damage to users in the unlikely event of leakage. In addition, since there is no need to install and configure a dedicated application, installation time is relatively low, and disaster information can be easily notified to facility users (especially temporary users), making it possible to ensure safety in the event of a disaster. It can contribute to evacuation and prevention of secondary disasters. By presenting these benefits to facility owners and users, it is possible to actively encourage registration. Therefore, registration and management of contact information for disaster-related notification information for facility users can be easily and safely operated.

Furthermore, the notification unit 104 transmits notification information only during the facility's available hours. Thereby, it is possible to prevent notification information regarding a disaster that has occurred at the facility from being sent to the user outside of available hours, that is, when the user is not at the facility.

The notification information also describes a link destination that allows access to at least one of the following: a map showing the location of a disaster in the event of a fire, information showing an evacuation route, or information about congestion on the evacuation route. Thereby, the user can obtain information for evacuation by accessing the link destination, thereby contributing to the smooth evacuation of the user.

Further, the deletion unit 105 deletes the registered contact address from the storage unit 103 after notifying the user that the contact address is to be deleted. This allows the user to know that the registered contact address will be deleted. Therefore, it is possible to give the user a sense of security.

Furthermore, the deletion unit 105 includes an extension unit 106 that notifies the user that the possible stay period can be extended when notifying the user that the contact address is to be deleted, and extends the possible stay period. As a result, even if the user stays at the facility longer than planned, it is possible to notify the user of notification information regarding the disaster by extending the deletion of the contact address.

When disaster information is notified using emergency broadcasts, the information may not be accurately grasped due to missed broadcasts, etc. On the other hand, according to the present embodiment, the contact address is a telephone number, and the notification unit 104 transmits the notification information using a short message service. As a result, the notification information is delivered in text to the user terminal 20 carried by the user, so that the user can read back and confirm the notification information. Therefore, even if the user misses the emergency broadcast etc. within the facility, the user can accurately understand the disaster that has occurred at the facility. Furthermore, it is possible to accurately notify disaster information even to hearing-impaired people.

[Second embodiment]
Next, a second embodiment of the present invention will be described. In the first embodiment, the planned stay period is registered on the registration page, but this embodiment differs in that the notification management device 10 acquires the user's planned stay period from an external server.

FIG. 13 is a schematic configuration diagram of the notification management system according to this embodiment.
In this embodiment, a notification management system 1A that notifies users of the accommodation facility of disaster information that has occurred at the accommodation facility will be described. The notification management system 1A includes a notification management device 10A instead of the notification management device 10, and further includes an external server 30.
The external server 30 is a server device that stores accommodation schedules of each user at an accommodation facility. The external server 30 stores at least the accommodation period and telephone number of each user in association with each other.

The notification management device 10A includes an acquisition section 101A instead of the acquisition section 101, and a registration section 102A instead of the registration section 102. The acquisition unit 101A acquires the user's telephone number from the user terminal 20 using the registration page. The registration page according to this embodiment does not include an entry field for the planned length of stay. The acquisition unit 101A then requests the external server 30 for the accommodation period corresponding to the telephone number acquired from the registration page. The acquisition unit 101A receives and acquires the accommodation period transmitted from the external server 30 in response to the request. The registration unit 102A writes and registers the acquired accommodation period in the database of the storage unit 103 in association with the acquired telephone number as the planned stay period of the accommodation facility.
The other configuration of the notification management system 1A is the same as that of the notification management system 1 according to the first embodiment, so a description thereof will be omitted.

As described above, according to the present embodiment, the notification management system 1A includes the acquisition unit 101A that acquires the accommodation period of the user from the server of the accommodation facility, and the registration unit 102A stores the acquired accommodation period at the accommodation facility. Register as a valid period of stay. This saves the user the trouble of inputting the planned length of stay. Furthermore, it is possible to prevent an incorrect planned stay period from being registered due to a user's input error.

Note that in this embodiment, the phone number is acquired from the registration page, but the phone number and the length of stay are not limited to this, and if the user's consent is obtained at the time of check-in, the phone number and the length of stay are acquired from the external server 30. may be sent to the notification management device 10A. As a result, the notification management device 10A can automatically acquire the user's phone number and length of stay when the user checks in, thereby saving the user the trouble of registering the phone number from the registration page. It can be omitted.

All or part of the notification management systems 1 and 1A in the embodiments described above may be realized by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Note that the "computer system" herein includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems. Furthermore, a "computer-readable recording medium" refers to a storage medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include a device that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. It may also be realized using a programmable logic device such as an FPGA.

In the embodiment described above, the notification method is described as using a short message, but the notification method is not limited to this. For example, as a voice notification to a visually impaired person, an automatic voice message may be sent by telephone using the telephone number obtained as a contact address.

Further, in the embodiment described above, it has been described that the registered contact information and the length of stay of the user at the facility are stored together, but the present invention is not limited to this. For example, if the end of the available period of stay is the same as the end of the available time of the facility for all users, the available period of stay for each user will not be memorized, and the end of the available period of use of the facility will be the same. Contacts may be uniformly deleted at the end of the time period. In this case, before deleting the user's contact information, each user terminal 20 is notified in advance of the deletion of the contact information, and a message is received from the user terminal 20 to the effect that an extension is desired. In this case, the contact information of the sender user may not be deleted at that timing.

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and includes designs within the scope of the gist of the present invention.

For example, in the embodiment described above, a telephone number was used as an example of a contact address, but the contact address is not limited to this, and the contact address may be any address that can notify users of disaster information in text, such as an email address. Bye.

1, 1A... Notification management system 10, 10A... Notification management device 101, 101A... Acquisition unit 102, 102A... Registration unit 103... Storage unit 104... Notification unit 105... Deleting section 106... Extension section 20... User terminal 201... Transmitting section 202... Receiving section 203... Display section 30... External server

Claims (11)

a registration department that registers contact information of facility users;
a storage unit that stores the registered contact information;
a notification unit that, when a disaster occurs at the facility, sends notification information regarding the disaster to the contact information stored in the storage unit;
a deletion unit that deletes the registered contact information from the storage unit in response to the end of the period of stay of the user at the facility;
A notification management device having: The notification management device according to claim 1, wherein the allowable stay period is stored in a storage unit together with the registered contact information. When notifying the user that the contact information is to be deleted, the deletion unit notifies the user that the possible stay period can be extended;
The notification management device according to claim 2, further comprising an extension section that extends the available period of stay. The period of stay is from the time when the user's contact information is registered on the day of using the facility until the most recent end of the facility's availability.
The notification management device according to claim 1 or claim 3. The notification management device according to any one of claims 1 to 4, wherein the notification unit transmits the notification information only during available hours of the facility. The notification information describes a link destination that allows access to at least one of the following information: a map showing the disaster location at the time of a disaster, information showing an evacuation route, or congestion status on the evacuation route. 6. The notification management device according to claim 1 or claim 5. The notification management according to any one of claims 1 to 6, wherein the deletion unit deletes the registered contact from the storage unit after notifying the user that the contact is to be deleted. Device. It has an acquisition unit that acquires the user's accommodation period from the server of the accommodation facility,
The notification management device according to claim 2, wherein the registration unit registers the acquired accommodation period as the available stay period of the accommodation facility. The contact information is a phone number;
The notification management device according to any one of claims 1 to 8, wherein the notification unit transmits the notification information using a message service that can send character data to a telephone number. A user terminal for registering contact information of facility users;
a storage unit that stores the registered contact information;
a notification unit that, when a disaster occurs at the facility, sends notification information regarding the disaster to the contact information stored in the storage unit;
a deletion unit that deletes the registered contact information from the storage unit in response to the end of the period of stay of the user at the facility;
A notification management system with. Register the contact information of facility users,
storing the registered contact information in a storage unit;
When a disaster occurs at the facility, transmitting notification information regarding the disaster to the contact information stored in the storage unit;
A notification management method, wherein the registered contact information is deleted from the storage unit in response to the end of the user's permitted stay period at the facility.

Images