Notification Management Device

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

Technical Field

[0004] , ,

[0001] The present invention relates to a notification management device Place .

Background Art

[0002] The information of a fire alarm is mainly used to notify a disaster prevention center, and direct calls using a special telephone or a mobile phone are generally used to contact relevant persons outside the disaster prevention center. The general building users in the building where a fire has occurred are informed by using a bell or an emergency broadcast, but there are cases where the information cannot be accurately grasped due to missing the broadcast. In addition, it is difficult to sufficiently notify a person with hearing impairment of the occurrence of a fire. Patent Document 1 describes a fire alarm that can notify a fire by flashing lights in order to notify many people including persons with hearing impairment of the occurrence of a fire. According to this fire alarm, if a person knows in advance that the flashing means notifying the occurrence of a fire, the occurrence of a fire can be grasped according to the flashing. However, for a person who does not know that the flashing means notifying the occurrence of a fire, it is impossible to understand what the flashing conveys.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] To address the above issues, methods are being considered to notify building users of fire alarms via the internet or other means. However, many notification systems require dedicated applications, making it difficult to encourage general building users and a large number of temporary visitors to adopt these applications. Furthermore, it is desirable that fire information not be notified to users who are not in the building (general building users and those who have left), except for owners and management companies. Additionally, while it is conceivable that the system could collect contact information from users' devices for notification purposes, the collected user contact information is confidential, and from an information management perspective, it is desirable that the contact information of users who do not require notification be discarded. Moreover, from the user's perspective, it is undesirable for their contact information to remain on the system indefinitely.

[0005] Therefore, this invention is a notification management system that solves the above-mentioned problems. Place The purpose is to provide it. [Means for solving the problem]

[0006] One aspect of the present invention is a notification management device comprising: a registration unit for registering the contact information of facility users; a storage unit for storing the registered contact information; a notification unit for transmitting notification information regarding a disaster to the contact information stored in the storage unit when a disaster occurs at the facility; and a deletion unit for deleting the registered contact information from the storage unit when the user's permitted stay period at the facility ends.

[0007] Furthermore, one aspect of the present invention is a notification management system comprising: a user terminal for registering the contact information of facility users; a storage unit for storing the registered contact information; a notification unit for transmitting notification information regarding a disaster to the contact information stored in the storage unit when a disaster occurs at the facility; and a deletion unit for deleting the registered contact information from the storage unit when the user's permitted stay period at the facility ends.

[0008] Furthermore, one aspect of the present invention is a notification management method that registers the contact information of facility users, stores the registered contact information in a memory unit, transmits notification information regarding the disaster to the contact information stored in the memory unit when a disaster occurs at the facility, and deletes the registered contact information from the memory unit when the user's permitted stay period at the facility ends. [Effects of the Invention]

[0009] According to the present invention, it is possible to prevent the registration of contact information for disaster notification information for facility users from remaining in place, and due to the low risk of leakage and ease of registration, the psychological barrier to registering notification recipients is lowered, and as registrations increase, emergency information such as disasters can be notified to more users. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram of a notification management system according to a first embodiment of the present invention. [Figure 2] This is a schematic diagram showing the data structure and data examples of the database stored by the notification management device according to the first embodiment of the present invention. [Figure 3] This is an illustrative diagram showing an example of a notice prompting the registration of a contact address according to the first embodiment of the present invention. [Figure 4] This is an image diagram showing an example of a registration page according to the first embodiment of the present invention. [Figure 5] This is a sequence diagram showing the operation of the registration process of the notification management system according to the first embodiment of the present invention. [Figure 6] This is an image diagram showing an example of a registration completion message according to the first embodiment of the present invention. [Figure 7] This is an image diagram showing an example of a message for notifying disaster information according to the first embodiment of the present invention. [Figure 8] This is an image diagram showing an example of an evacuation page according to the first embodiment of the present invention. [Figure 9]It is an image diagram showing an example of a registration deletion notification message according to the first embodiment of the present invention. [Figure 10] It is a sequence diagram showing the operation of the registration extension process of the notification management system according to the first embodiment of the present invention. [Figure 11] It is a sequence diagram showing the operation of the registration deletion process over time of the notification management system according to the first embodiment of the present invention. [Figure 12] It is a sequence diagram showing the operation of the registration deletion process by the user of the notification management system according to the first embodiment of the present invention. [Figure 13] It is a schematic configuration diagram of the notification management system according to the second embodiment of the present invention.

Mode for Carrying Out the Invention

[0011] Hereinafter, a notification management device, a notification management system, and a notification management method according to an embodiment of the present invention will be described with reference to the drawings.

[0012] [First Embodiment] First, the first embodiment will be described. FIG. 1 is a schematic configuration diagram of the notification management system according to the present embodiment. The notification management system 1 is a system that notifies 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 facility (an unspecified number of people present in the facility, such as visitors to the commercial facility, inpatients in the hospital, and guests in the accommodation facility). The disaster information is, for example, a fire alarm, an earthquake early warning, or an evacuation instruction from a disaster prevention center. The notification management system 1 includes a notification management device 10 and a user terminal 20.

[0013] The notification management device 10 is a server device that comprehensively 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 that can use a message service capable of transmitting character data with a telephone number as a destination, such as a smartphone or a mobile phone, and can make voice calls. The message service may be, for example, a short message service or an automatic voice message service capable of transmitting voice messages. The notification management device 10 and the user terminal 20 are communicatively connected via a network such as the Internet or a mobile phone network.

[0014] The notification management device 10 includes an acquisition unit 101, a registration unit 102, a storage unit 103, a notification unit 104, a deletion unit 105, and an extension unit 106. The acquisition unit 101 receives and acquires registration information including the contact address of the facility user and the available stay period of the user in the facility from the user terminal 20. The contact address in this embodiment is the telephone number of the user terminal 20. The registration unit 102 writes the acquired contact address into the database of the storage unit 103 together with the available stay period of the user in the facility and registers it as the contact address of the disaster information related to the disaster occurring in the facility. The storage unit 103 has a database that stores the contact address of the disaster information related to the disaster occurring in the facility together with the available stay period of the user in the facility, and a memory for temporary storage. The available stay period may be from the registration of the user's contact on the day of using the facility to the end of the available use of the facility nearest thereto. Also, when the available stay period is specified in advance by the user, the specified available stay period may be used.

[0015] When a disaster occurs at a facility, the notification unit 104 sends disaster information related to the disaster to contact addresses stored in the database of the storage unit 103 via short message service. In facilities where users stay all day, such as hotels and hospitals, the notification unit 104 notifies disaster information as long as contact addresses are registered. On the other hand, in facilities with fixed operating hours, the notification unit 104 only notifies disaster information during operating hours, even if contact addresses are registered, and does not notify outside of operating hours. Operating hours are, for example, the business hours of commercial facilities. The disaster information includes a link to access at least one of the following: a map showing the location of the disaster at the time of the disaster, information representing evacuation routes, or congestion status along evacuation routes.

[0016] The deletion unit 105 deletes the registered contact address from the database of the storage unit 103 when the user's permitted stay period at the facility ends. At this time, the deletion unit 105 notifies the user that the contact address will be deleted before deleting the registered contact address. In addition, when the deletion unit 105 notifies the user that the address will be deleted, it also notifies the user that it is possible to extend the permitted stay period. The extension unit 106 extends the period of stay that users can have at the facility.

[0017] The user terminal 20 comprises a transmitting unit 201, a receiving unit 202, and a display unit 203. The transmission unit 201 sends the contact address of the facility user and the period of stay the user is permitted to have at the facility to the notification management device 10 for registration. The receiving unit 202 receives disaster information related to disasters occurring at the facility via the Short Message Service. The display unit 203 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display, which displays the received disaster information.

[0018] Figure 2 is a schematic diagram showing the data structure and data examples of the database stored by the notification management device according to this embodiment. The database stores information by associating it with the following items: contact address, planned length of stay, language, automatic deletion, and notifications other than disaster information. The contact address is the phone number used to contact disaster information. The planned stay period is the period during which the user can stay at the facility. The language is the language in which disaster information will be notified. Automatic deletion indicates whether the registered contact address will be automatically deleted after the facility's operating hours end. Non-disaster notifications indicate whether non-disaster notifications will be sent to the corresponding contact address. Non-disaster notifications include, for example, notifications about time sales, events, and coupons for commercial facilities, and communications from the front desk for accommodation facilities.

[0019] 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", automatic deletion is "enabled", and notifications other than disaster information are "enabled". Also, the planned stay period corresponding to the contact address "090-9876-5432" is "until 2022 / 01 / 30 21:00", the language is "English", automatic deletion is "disabled", and notifications other than disaster information are "disabled".

[0020] Next, we will explain the operation of this notification management system 1. Figure 3 is an illustrative diagram showing an example of a notice prompting the registration of a contact address according to this embodiment. This notice will be posted at the entrance of the facility or in the area where the user stays. In the illustrated example, a message A11 encouraging 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 phone number, which is the contact address, users can receive disaster information about the facility via SMS (Short Message Service), etc. 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 without making a reservation. In such cases, they can register their contact information on the day they use the facility, either upon arrival or during their stay. Message A11 also states that the registered phone number will be deleted from the notification management system 1 after the user finishes using the facility. This allows users to know that their registered phone number will be automatically deleted after they finish using the facility, giving them peace of mind when registering. Therefore, including such a message A11 can encourage the registration of phone numbers. Code A12 indicates the URL (Uniform Resource Locator) of the webpage (hereinafter referred to as the "registration page") for registering the contact addresses of users of the facility.

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

[0022] Figure 4 is an illustrative diagram showing an example of a registration page according to this embodiment. A registration page exists for each facility that will receive disaster information notifications, and a code to identify the target facility is pre-set. In the example shown in this diagram, the registration page includes an input field A21 for the telephone number, an input field A22 for the language in which disaster information will be notified, an input field A23 for the planned length of stay of the user at the facility, an input field A24 for selecting whether or not to automatically delete the telephone number after the available hours (in this example, business hours), an input field A25 for selecting whether or not to send notifications other than disaster information, and a registration button A26 for registering the contents entered in each input field (hereinafter referred to as "registration information") into the notification management system 1. The language input field A22 and the planned stay duration input field A23 may allow users to select input items from dropdown menus. The planned stay duration input field A23 may also have the facility's operating hours end pre-set as the initial value. Furthermore, the planned stay duration may be restricted depending on the facility's purpose. For example, commercial facilities may be restricted to only the period until closing time. Additionally, the input field A24, which selects whether or not to automatically delete the phone number after the operating hours end, and the input field A25, which selects whether or not to send notifications other than disaster information, may be selectable by checking "Yes" or "No" checkboxes. The length of stay can be specified by the user. Alternatively, even if not specified by the user, the length of stay may be set by default from the date the user's contact information is registered until the next available period for use of the facility, and the user may change this as needed.

[0023] Figure 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 obtains the URL of the registration page from code A12 displayed at the facility entrance, etc. (step S101). Then, in response to the user's operation, the user terminal 20 accesses the URL of the registration page and requests the registration page from the notification management device 10 (step S102). The acquisition unit 101 of the notification management device 10 sends the registration page to the user terminal 20 in response to the 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 obtain the language setting of the user terminal 20, it sends the registration page written in that language. If it is not able to obtain the language setting of the user terminal 20, it sends the registration page written in a pre-configured multilingual language. The user terminal 20 receives the registration page and displays the received registration page. Then, the user terminal 20 accepts input of registration information on the displayed registration page (step S104). The user enters the registration information on the registration page and presses the registration button A26 displayed on the registration page.

[0024] When the user terminal 20 presses the registration button A26 on the registration page, it transmits the registration information entered in each input field A21 to A25 on the registration page to the notification management device 10 (step S105). The registration information includes the telephone number, language, planned stay period, information indicating whether or not to automatically delete the telephone number after the available time ends, and information indicating whether or not to send notifications other than disaster information. When the acquisition unit 101 of the notification management device 10 receives the registration information from the user terminal 20, it generates an authentication code of any 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 entering the authentication code to the user terminal 20 (step S106). At this time, the acquisition unit 101 of the notification management device 10 transmits the authentication code setting page to the user terminal 20, written in the language included in the received registration information. The user terminal 20 displays the received authentication code setting page and accepts the input of the authentication code. Next, the acquisition unit 101 of the notification management device 10 sends the generated authentication code via short message service to the telephone number included in the received registration information (step S107). Then, the acquisition unit 101 of the notification management device 10 starts an authentication time timer (for example, 5 minutes), which is the deadline for authenticating the authentication code. The user enters the authentication code received by the user terminal 20 via short message service into the authentication code setting page. The user terminal 20 sends the authentication code entered into the authentication code setting page to the notification management device 10 (step S108).

[0025] 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 waiting time timer has elapsed before the authentication code is received, the acquisition unit 101 of the notification management device 10 sends an error page indicating that authentication has failed to the user terminal 20. On the other hand, if the authentication code received within the expiration of the authentication waiting time timer matches, the registration unit 102 of the notification management device 10 writes the received registration information to the database and registers it (step S109). The registration unit 102 of the notification management device 10 then sends a registration completion page indicating that the registration of the registration information has been 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 sends a registration completion message indicating that the registration of the registration information has been completed to the registered telephone number via short message service (step S111). The user terminal 20 receives the registration completion message via the short message service and displays the received registration completion message.

[0026] Figure 6 is an illustrative diagram showing an example of a registration completion message according to this embodiment. This figure shows an example of the screen displayed on the user terminal 20 when a registration completion message is received. In the example shown in this figure, registration completion message A30 states that the registration of the telephone number has been completed. In this way, by sending a registration completion message to the registered telephone number, the user can be informed that the telephone number has been registered correctly. In addition, registration completion message A30 contains a URL 31 to a web page for deleting the registered telephone number (hereinafter referred to as the "deletion page"). The user can delete the registered telephone number from the notification management system 1 by following the procedure on the deletion page.

[0027] Furthermore, when a fire or other disaster occurs within the facility, the notification unit 104 of the notification management device 10 sends disaster information related to the disaster to the registered telephone number via short message service or the like.

[0028] Figure 7 is an illustrative diagram showing an example of a message used to notify disaster information according to this embodiment. This figure shows an example of the screen displayed on the user terminal 20 when it receives a message notifying it of disaster information regarding a fire. In the example shown in this figure, the user terminal 20 first receives message A41, which informs it that a fire has occurred in the facility and urges it to evacuate, and then receives message A42, which indicates the location of the fire. Subsequently, the user terminal 20 receives message A43, which contains information for evacuation. Message A43 contains a URL 44, which is a link to a web page (hereinafter referred to as the "evacuation page") where evacuation information is disclosed. Depending on the user's actions, the user terminal 20 accesses the URL 44 described in message A43 and displays the evacuation page.

[0029] Figure 8 is an illustrative diagram showing an example of an evacuation page according to this embodiment. The evacuation page includes at least one piece of information: a map showing the location of the disaster, information representing evacuation routes, or information on congestion along the evacuation routes. In the example shown in this figure, the evacuation page displays a map of the facility (MP51) with evacuation exits marked, overlaid with a flame mark (MK52) indicating the location of a fire and a mark (MK53) indicating a congested area. By marking the location of the fire on the map in this way, users can easily identify the location of the fire. Furthermore, since evacuation exits and the corridors leading to those exits are displayed on the map, users can understand the evacuation route. In addition, since congested areas are marked on the map, users can understand the congestion level within the facility and evacuate while avoiding crowded areas. This allows users to evacuate quickly. The evacuation page is updated as needed according to the situation within the facility, and users can obtain the latest disaster information by refreshing the evacuation page.

[0030] Furthermore, if the facility has set operating hours (e.g., business hours), the notification unit 104 of the notification management device 10 will only notify disaster information during those operating hours. In other words, the notification unit 104 of the notification management device 10 will not notify disaster information outside of the facility's operating hours. This is because it is assumed that there are no users at the facility outside of operating hours. This prevents unnecessary notifications from being sent to users who are not at the facility.

[0031] Furthermore, if the database stored in the storage unit 103 indicates that notifications other than disaster information should be sent, the notification unit 104 of the notification management device 10 will send notifications other than disaster information to the contact address. For example, in the case of a commercial facility, the notification unit 104 of the notification management device 10 will send notifications about time sales, events, coupons, etc. Also, in the case of an accommodation facility, the notification unit 104 of the notification management device 10 will send notifications about communications from the front desk, etc. On the other hand, if the notification unit 104 of the notification management device 10 is set to "do not send notifications other than disaster information", it will not send notifications other than disaster information.

[0032] Then, when a predetermined time (for example, 10 minutes before) 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 the registered telephone number via short message service or the like, notifying that the registered telephone number has been deleted.

[0033] Figure 9 is an illustrative diagram showing an example of a registration deletion notification message according to this embodiment. This figure shows an example screen of a user terminal 20 that has received a registration deletion notification message. In the example shown in this figure, registration deletion notification message A60 states that the registered scheduled stay period has ended and the registered telephone number will be deleted from the notification management system 1. Furthermore, registration deletion notification message A60 contains a URL 61 to a web page for extending the registration (hereinafter referred to as the "time extension page"). The user can extend the scheduled stay period by following the procedure on the time extension page.

[0034] Figure 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 via short message service to the corresponding telephone number when 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, they access the URL described in the registration deletion notification message. The user terminal 20 requests the time extension page from the notification management device 10 in response to the user's operation (step S202).

[0035] When the extension unit 106 of the notification management device 10 receives a request for a time extension page from the user terminal 20, it sends 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 input for setting an extension of the scheduled stay time (step S204). The user terminal 20 then sends the extended scheduled stay period from 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 stay period registered in the database with the received scheduled stay period (step S206). The extension unit 106 of the notification management device 10 then sends a message to the user terminal 20 via short message service notifying that the scheduled stay period has been extended (step S207).

[0036] Figure 11 is a sequence diagram showing the operation of the registration deletion process based on the passage of time in the notification management system according to this embodiment. The deletion unit 105 of the notification management device 10 sends a registration deletion notification message via short message service to the corresponding telephone number when a predetermined time (for example, 10 minutes) before the end of the scheduled stay period registered in the database (step S301). Subsequently, when the scheduled stay period has elapsed, the deletion unit 105 of the notification management device 10 deletes the registration information for which the scheduled stay period has elapsed from the database (step S302).

[0037] Furthermore, the deletion unit 105 of the notification management device 10 may delete the registration information from the database even before the end of the scheduled stay period if it receives a message from the user terminal 20 approving the deletion of the registration information. Furthermore, the deletion unit 105 of the notification management device 10 deletes registered information for which automatic deletion is set to "on" from the database when the pre-set available time for the facility has elapsed. Furthermore, the deletion unit 105 of the notification management device 10 may be configured to delete all contact addresses from the database on a predetermined inventory date.

[0038] Figure 12 is a sequence diagram showing the operation of the user-initiated registration deletion process in the notification management system according to this embodiment. The user can delete their registration information on the deletion page described in the registration completion message. The user terminal 20 requests the deletion page from the notification management device 10 in response to the user's operation (step S401). The deletion unit 105 of the notification management device 10 sends the deletion page to the user terminal 20 in response to the request from the user terminal 20 (step S402). The user terminal 20 displays the received deletion page and accepts input for deletion approval (step S403). Then, the user terminal 20 sends a request to delete the registration 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). Subsequently, the deletion unit 105 of the notification management device 10 sends a message via short message service to the telephone number written to the temporary storage memory, notifying that the registered information has been deleted (step S406). Then, the deletion unit 105 of the notification management device 10 deletes the telephone number from the temporary storage memory (step S407).

[0039] Generally, it is best not to notify people who are not at the affected facility about disasters such as fires. Furthermore, for facility users, disaster information received after their visit may not be useful. Also, some users may not appreciate their contact email addresses remaining on the system after their visit. Therefore, there is a demand to promptly discard registered contact email addresses after their visit.

[0040] In contrast, according to this embodiment, the notification management system 1 includes a user terminal 20 for registering the contact addresses of facility users, a storage unit 103 for storing the registered contact addresses along with the period the user is allowed to stay at the facility, a notification unit 104 for sending notification information regarding a disaster to the contact addresses stored in the storage unit 103 when a disaster occurs at the facility, and a deletion unit 105 for deleting the registered contact addresses from the storage unit 103 when the period the user is allowed to stay at the facility ends.

[0041] This allows for the automatic deletion of registered contact addresses upon the end of a user's permitted stay at the facility. This prevents the notification of disaster information occurring at the facility to users who are not present. Furthermore, the automatic deletion of contact addresses after the permitted stay period provides a sense of security to users registering their contact addresses, making registration easier. Additionally, since the notification management system 1 does not require the management of users' personal information, it minimizes damage to users in the event of a data breach, thus lowering the barrier to registration. Moreover, because it does not require the installation and configuration of a dedicated application, the initial setup is relatively easy, simplifying the notification of disaster information to facility users (especially temporary users), contributing to safe evacuation and the prevention of secondary disasters during emergencies. These benefits can be presented to facility owners and users to encourage proactive registration. Therefore, the registration and management of contact information for disaster notification information to facility users can be operated simply and securely.

[0042] Furthermore, the notification unit 104 transmits notification information only during the facility's operating hours. This prevents the transmission of notification information regarding disasters occurring at the facility to users outside of operating hours, i.e., when users are not at the facility.

[0043] Furthermore, the notification information includes a link that provides access to at least one of the following: a map showing the location of the fire, information indicating evacuation routes, or information on congestion levels along evacuation routes. This allows users to obtain evacuation information by accessing the link, thereby contributing to a smoother evacuation process.

[0044] Furthermore, the deletion unit 105 notifies the user that the contact address will be deleted, and then deletes the registered contact address from the storage unit 103. This allows the user to know that their registered contact address will be deleted, thus providing them with a sense of security.

[0045] Furthermore, the deletion unit 105 notifies the user that the contact address will be deleted, and also notifies the user that the period of stay can be extended, and has an extension unit 106 that extends the period of stay. This allows the user to receive disaster-related notification information even if they stay at the facility longer than planned, by extending the period of deletion of their contact address.

[0046] When disaster information is notified using emergency broadcasts, there is a risk that the information may not be accurately grasped due to missed broadcasts or other reasons. In contrast, according to this embodiment, the contact address is a telephone number, and the notification unit 104 transmits the notification information via short message service. As a result, the notification information is delivered in text to the user's portable terminal 20, allowing the user to reread and confirm the notification information. Therefore, even if an emergency broadcast within the facility is missed, the user can accurately grasp the disaster that has occurred at the facility. Furthermore, disaster information can be accurately notified to people with hearing impairments.

[0047] [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 in this embodiment, the notification management device 10 obtains the user's planned stay period from an external server.

[0048] Figure 13 is a schematic diagram of the notification management system according to this embodiment. This embodiment describes a notification management system 1A that notifies users of an accommodation facility of disaster information occurring at the facility. 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 the accommodation schedule of each guest at the accommodation facility. The external server 30 stores at least the length of stay and telephone number of each guest in association with each other.

[0049] The notification management device 10A includes an acquisition unit 101A in place of the acquisition unit 101, and a registration unit 102A in place of the registration unit 102. The acquisition unit 101A acquires the user's telephone number from the user terminal 20 via a registration page. The registration page in this embodiment does not have an input field for the planned length of stay. The acquisition unit 101A then requests the external server 30 for the length of stay corresponding to the telephone number acquired from the registration page. The acquisition unit 101A receives and acquires the length of stay transmitted from the external server 30 in response to the request. The registration unit 102A registers the acquired length of stay as the planned length of stay for the accommodation facility by associating it with the acquired telephone number and writing it to the database of the storage unit 103. Other components of the notification management system 1A are the same as those of the notification management system 1 according to the first embodiment, so their description will be omitted.

[0050] Thus, according to this embodiment, the notification management system 1A has an acquisition unit 101A that obtains the user's length of stay from the accommodation facility's server, and the registration unit 102A registers the acquired length of stay as the available stay period at the accommodation facility. This eliminates the need for the user to manually enter their planned length of stay. It also prevents the registration of an incorrect length of stay due to user input errors.

[0051] In this embodiment, the phone number is obtained from the registration page, but this is not limited to this. Alternatively, the phone number and length of stay may be sent from the external server 30 to the notification management device 10A when the user checks in, provided the user consents. This allows the notification management device 10A to automatically obtain the user's phone number and length of stay when the user checks in, thus saving the user the trouble of registering their phone number on the registration page.

[0052] The notification management systems 1,1A in the above-described embodiments may be implemented in whole or in part using a computer. In this case, the program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into the computer system and executed. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. In addition, "computer-readable recording medium" may also include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside the computer system that acts as a server or client in such cases. Furthermore, the above-mentioned program may be for implementing a part of the above-mentioned function, or it may be a program that can implement the above-mentioned function in combination with a program already recorded in the computer system, or it may be implemented using a programmable logic device such as an FPGA.

[0053] In the embodiments described above, we have assumed that short messages are used as the notification method, but we are not limited to this. For example, as an audio notification to a visually impaired person, an automated voice message may be sent by telephone using the telephone number obtained as the contact address.

[0054] Furthermore, while the embodiments described above have assumed that registered contact information and the user's permitted stay period at the facility are stored together, this is not limited to this. For example, if the end of the permitted stay period is the same for all users as the end of the facility's operating hours, the permitted stay period for each user may not be stored, and the contact information may be uniformly deleted at the end of the facility's operating hours. In this case, before deleting the user's contact information, each user terminal 20 may be notified in advance that the contact information will be deleted, and if a message requesting an extension is received from the user terminal 20, the contact information of the user who sent the message may not be deleted at that time.

[0055] Although embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and includes designs and the like that do not depart from the spirit of this invention.

[0056] 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; any address that can notify users of disaster information in text format, such as an email address, is acceptable. [Explanation of Symbols]

[0057] 1. 1A... Notification Management System 10,10A...Notification management device 101,101A...Acquisition Department 102, 102A... Registration Department 103...Storage section 104... Notification Department 105...Deleted section 106...extension part 20.. User terminals 201...Transmitter 202... Receiver 203...Display section 30...External Server

Claims

1. A notification management device, A registration section for registering the contact information of facility users, A storage unit that stores the registered contact information, A notification unit that, in the event of a disaster occurring at the aforementioned facility, transmits notification information regarding the disaster to contacts stored in the storage unit, A deletion unit deletes the registered contact information from the storage unit in response to the end of the user's permitted stay period at the facility. It has, The aforementioned permitted stay period is stored in the memory unit along with the registered contact information. When the deletion unit notifies the user that the contact information will be deleted, it also notifies the user that the period of stay can be extended. The notification management device is Having an extension that extends the aforementioned period of stay Notification management device.

2. The deletion unit notifies the user that the contact information will be deleted, and then deletes the registered contact information from the storage unit. The notification management device according to claim 1.

3. A registration section for registering the contact information of facility users, A storage unit that stores the registered contact information, A notification unit that, in the event of a disaster occurring at the aforementioned facility, transmits notification information regarding the disaster to contacts stored in the storage unit, A deletion unit deletes the registered contact information from the storage unit in response to the end of the user's permitted stay period at the facility. It has, The deletion unit notifies the user that the contact information will be deleted, and then deletes the registered contact information from the storage unit. Notification management device.

4. It has an acquisition unit that retrieves the user's length of stay from the accommodation facility's server. The registration unit registers the acquired accommodation period as the available stay period for the accommodation facility. A notification management device according to any one of claims 1 to 3.

5. A registration section for registering contact information of facility users, A storage unit that stores the registered contact information, A notification unit that, in the event of a disaster occurring at the aforementioned facility, transmits notification information regarding the disaster to contacts stored in the storage unit, A deletion unit deletes the contact information from the storage unit in accordance with the end of the user's permitted stay period at the facility. It has, The deletion unit sends a message to the contact person informing them that the contact information will be deleted as a result of deleting the registered contact from the storage unit. Notification management device.

Images