JP6655363B2 - Electronic lock management device and electronic lock management program - Google Patents

Description

  The present invention relates to an electronic lock management device and an electronic lock management program.

There is known an electric lock unlocking system that forcibly unlocks an electric lock to be managed based on the emergency earthquake early warning when the emergency earthquake early warning is received (for example, see Patent Document 1).
Patent Document 1 JP-A-10-025935

  Even when the emergency earthquake early warning is a false alarm (an earthquake has never occurred, or the actual magnitude of the earthquake is small, etc.), there has been a problem that the electric lock is always unlocked. In other words, there is a problem that the electronic lock is always unlocked even when the input signal relating to the disaster has an error.

  An electronic lock management device according to a first aspect of the present invention includes an information obtaining unit that obtains disaster information on a disaster, a receiving unit that receives an unlock request for unlocking an electronic lock installed in a specific area, A providing unit that provides unlocking information for unlocking the electronic lock when the receiving unit receives the unlock request after the obtaining unit obtains the disaster information.

  An electronic lock management program according to a second aspect of the present invention includes: an information obtaining step of obtaining disaster information relating to a disaster; a receiving step of receiving an unlock request for unlocking an electronic lock installed in a specific area; And a providing step of providing unlocking information for unlocking the electronic lock when the unlocking request is received by the receiving step after the disaster information is obtained by the obtaining step.

  The above summary of the present invention is not an exhaustive listing of all features of the present invention. Further, a sub-combination of these feature groups can also be an invention.

It is a schematic diagram explaining the outline of the electronic lock management system according to the first embodiment. FIG. 3 is a block diagram illustrating a configuration of a server device. FIG. 3 is a block diagram illustrating a configuration of an administrator terminal. FIG. 2 is a block diagram illustrating a configuration of a mobile terminal. It is a block diagram explaining the composition of an electronic lock device. It is a flowchart explaining operation | movement of the electronic lock management system which concerns on 1st Embodiment. It is a flowchart explaining the modification of the electronic lock management system concerning 1st Embodiment. It is a schematic diagram explaining the outline | summary of the electronic lock management system which concerns on 2nd Embodiment.

  Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. In addition, not all combinations of the features described in the embodiments are necessarily essential to the solution of the invention.

  FIG. 1 is a schematic diagram illustrating an overview of an electronic lock management system according to the first embodiment. The electronic lock management system 10 is constructed by using a server device 100, an administrator terminal 200, a portable terminal 300, and an electronic lock device 400 (400a to 400g in the figure) as main components. The administrator terminal 200 is connected to the server device 100 via a LAN. Further, the mobile terminal 300 can be connected to the server device 100 via the Internet. On the other hand, the electronic lock device 400 is a stand-alone electronic lock device that is not connected to a network.

  The server device 100 plays a role as an electronic lock management device that manages unlocking of the electronic lock device 400. It is preferable that the server device 100 be installed in an area remote from any management area. If the server device 100 is installed at a remote location with respect to the electronic lock device 400 to be managed, even if a disaster occurs in the management area, it is possible to prevent the server device 100 from being damaged and damaged. .

  The server device 100 collectively manages unlock information for unlocking an electronic lock, which is a lock mechanism of an electronic lock device 400 attached to doors of properties installed in a plurality of specific areas. In the present embodiment, the unlock information is an emergency key ID for unlocking an electronic lock device 400 described later. Here, the “specific area” is an area preset as an area managed by the server device 100. In the following description, a specific area may be referred to as a “managed area”, and a property managed by the server device 100 may be referred to as a “managed property” in the managed area.

  In the present embodiment, the managed property is a building related to a disaster. The building related to the disaster is, for example, a disaster prevention storage warehouse that stores water and food, or a gymnasium of a school that is an evacuation site. In addition, buildings related to disasters include evacuation routes such as gates on evacuation routes that are prohibited during normal times.

  The server device 100 manages the unlocking time of the electronic lock device 400. Specifically, the server device 100 manages the unlocking time of the electronic lock device 400 in a history list described later.

  The server device 100 acquires disaster information regarding a disaster. In the present embodiment, the disaster information is, for example, an emergency signal transmitted from an administrative organization. In the present embodiment, the emergency signal is an emergency earthquake bulletin transmitted from the Meteorological Agency. In addition, the server device 100 can acquire, as an emergency signal, a signal including various information issued from a public organization in an emergency. The emergency signal may be, for example, a signal including a warning and a forecast regarding a natural disaster such as a tsunami, an eruption, a pyroclastic flow, or a debris flow. Alternatively, the signal may include information on an evacuation order and evacuation advisory issued by the local government.

  Further, the disaster information may be an input signal from the administrator terminal 200 by an authorized administrator. In the present embodiment, the administrator is, for example, a disaster prevention person in a building where the server device 100 is installed. In the present embodiment, when the administrator obtains information on the occurrence of a disaster from an information source such as a television or a radio, the administrator operates the administrator terminal 200 to transmit a disaster occurrence notification signal for notifying the occurrence of the disaster to the server apparatus 100. Send to The disaster occurrence notification signal includes information on a management area estimated by the manager as having a disaster. The server device 100 acquires a disaster occurrence notification signal as disaster information.

  In the present embodiment, the server device 100 targets a managed property installed in a managed area included in the disaster area specified from the disaster information. In the following description, the affected area specified from the disaster information may be referred to as a “predicted area”. In the Earthquake Early Warning, the damage prediction area is an area predicted to have a seismic intensity of 4 or more, for example. When the server device 100 receives an unlock request for unlocking the managed property included in the predicted disaster area from the user's mobile terminal 300 after acquiring the disaster information, the server 100 attaches the electronic lock attached to the managed property. Unlock information for unlocking the device 400 is transmitted to the mobile terminal 300. The details will be described later.

  An electronic lock device 400 is attached to each of the managed properties. The electronic lock device 400 is a non-contact type electronic lock device that unlocks by short-range wireless communication with an electronic key terminal. Note that the electronic lock device 400 may be a contact-type electronic lock device that directly inputs authentication data by operating a numeric keypad.

  The mobile terminal 300 is, for example, a smartphone. In the present embodiment, the portable terminal 300 functions as an electronic key terminal for unlocking the electronic lock device 400 by installing application software described later. Note that the mobile terminal 300 may be a wireless communication terminal such as a tablet terminal or a dedicated terminal as an electronic key terminal.

  In the example of the figure, a region A, a region B, and a region C are shown as different management regions. In the present embodiment, it is desirable that the management area be set as an area that is assumed to be commonly damaged when a certain disaster occurs. For simplicity, the management area may be set in units of municipalities. Further, the management areas may be adjacent to each other or may be apart from each other.

  Each managed area has multiple managed properties. In the example shown in the figure, two managed properties are installed in the area A, and management doors A1 and A2 are built in each area. In the area B, three managed properties are installed, and properties B1, B2, and B3 are built. In the area C, two managed properties are installed, and management doors C1 and C2 are installed in each area.

  Electronic lock devices 400a and 400b are attached to the management doors A1 and A2, respectively. Electronic lock devices 400c, 400d, and 400e are attached to the management doors B1, B2, and B3, respectively. Electronic lock devices 400f and 400g are attached to the properties C1 and C2, respectively.

  In the present embodiment, the server device 100 stores information on the management area, information on the managed property, and information on the electronic lock device 400 attached to the managed property, in association with each other. The management area information is, for example, a local government code. The information on the managed property is, for example, information on the position of the property represented by latitude and longitude. The information of the electronic lock device is, for example, a serial number and emergency authentication data described later.

  In the present embodiment, in the vicinity of the electronic lock device 400, a notice 500 (500a to 500g in the figure) in which information for acquiring unlock information of the electronic lock device 400 in an emergency is posted. ing. In the present embodiment, the notice 500 is a panel on which a two-dimensional code such as a QR code (registered trademark) is described. The notice 500 may be a poster with an NFC tag capable of acquiring stored information by holding the smartphone over, for example, or a paper on which information such as an access destination e-mail address and a URL is written. And so on.

  In the example of the figure, notices 500a and 500b are posted near the electronic lock devices 400a and 400b, respectively. Announcements 500c, 500d, and 500e are posted near the electronic lock devices 400c, 400d, and 400e, respectively. Announcements 500f and 500g are displayed near the electronic lock devices 400f and 400g, respectively.

  Hereinafter, processing of the electronic lock management system 10 according to the present embodiment will be briefly described with reference to FIG. In the following description of FIG. 1, it is assumed that the server device 100 has already received disaster information. Further, it is assumed that the area A is included in the disaster prediction area.

  FIG. 1 shows an unlocking applicant in the area A. In the example of the figure, the unlocking candidate is a victim who wants to unlock the electronic lock device 400a of the management key A1. The unlocking candidate can acquire the unlocking information of the electronic lock device 400a by reading the two-dimensional code of the notice 500a with the portable terminal 300 owned by the user.

  In the present embodiment, when the portable terminal 300 reads the two-dimensional code of the notice 500a, the mailer of the portable terminal 300 is activated, and an unlock request mail requesting the unlock information to the server device 100 is automatically created. Is done. In the unlock request mail, the mail address of the server device 100 is input as a transmission destination. In the body of the unlock request mail, information on the ID of the electronic lock device 400a is described. The identification ID is, for example, a serial number of the electronic lock device 400a. The automatically generated unlock request mail is transmitted from the portable terminal 300 to the server device 100 by the unlocking applicant.

  The server device 100 accepts the unlock request email received from the mobile terminal 300 as an unlock request for the electronic lock device 400. The server device 100 specifies the electronic lock device that is the target of the unlock request from the identification ID included in the unlock request email. In FIG. 1, the server device 100 specifies that the electronic lock device 400a is the target of the unlock request. Then, the server device 100 attaches the unlock information for unlocking the electronic lock device 400a to the unlock request mail, and returns it to the portable terminal 300 that is the transmission source. In the present embodiment, the unlock information is a file in which an emergency key ID as an unlock signal is described, and an application program file.

  Here, the “emergency key ID” is an authentication ID used only in an emergency. In the present embodiment, the electronic lock device 400 stores in advance two types of authentication data: authentication data used for authentication in normal times and emergency authentication data used for authentication in emergency. The emergency key ID is an authentication ID associated with the emergency authentication data.

  In the present embodiment, the application program file is, for example, a file for distributing an application program in an apk format. In order to use the portable terminal 300 as an electronic key terminal of the electronic lock device 400, it is necessary to install an application program in advance. However, the mobile terminal 300 is used as an electronic key terminal temporarily in an emergency, and it is assumed that the application program is not installed. By installing the application program on the mobile terminal 300, a person who wants to unlock can use the mobile terminal 300 as an electronic key terminal. In the following description, the application program may be referred to as a “key application”. The key application distribution file may be referred to as a “key application file”.

  The unlocking candidate installs the key application on the portable terminal 300 using the key application file attached to the mail received from the server device 100. Next, the unlocking applicant stores the emergency key ID similarly attached to the mail in the storage area of the portable terminal 300. The portable terminal 300 functions as an electronic key terminal of the electronic lock device 400 by performing these operations by an unlocking applicant. Then, the unlocking applicant can unlock the electronic lock device 400 using the portable terminal 300.

  Here, it should be noted that the disaster information includes misinformation. Emergency signals are warning signals related to life, so they are often sent aggressively if any danger is predicted.For example, an emergency earthquake warning is sent even though no earthquake actually occurs. May be done. In addition, the disaster occurrence notification signal is transmitted based on the judgment made by the administrator based on information obtained on a television or the like. However, since the manager is in a remote place away from the management area, the scale of damage at the site cannot be sufficiently grasped. For this reason, it may actually be transmitted even though the damage scale is relatively small.

  The electronic lock device often has a function of protecting the property. For example, if the electronic lock device in the storage warehouse is unlocked without permission even in the case of a false alarm, there is a risk of being exposed to looting or the like. Therefore, regarding “unlocking”, it is necessary to more carefully judge the occurrence of an actual disaster and execute it. Therefore, in the present embodiment, the unlocking information of the electronic lock device is not automatically unlocked based on only the disaster information, but in response to a request from a person who determines that unlocking is required at the installation location of the managed property. Adopt the configuration provided. In this way, by intervening the judgment of the user at the site where the managed property is installed, it is possible to prevent the electronic lock device 400 from being unlocked even though no disaster has occurred. . Hereinafter, the electronic lock management system 10 according to the present embodiment will be described in detail with reference to the drawings.

  FIG. 2 is a block diagram illustrating the configuration of the server device. The server device 100 includes a control unit 102 including, for example, a CPU, a network connection unit 104 that is a network interface, and a storage unit 106 including, for example, a hard disk drive. Further, the control unit 102 has a memory 103 composed of a nonvolatile memory such as a flash memory.

  The control unit 102 controls the operation of the components of the server device 100 in a centralized manner. The memory 103 stores an electronic lock management program as an application program for controlling the operation of the server device 100 in order to manage the electronic lock in the electronic lock management system 10. The control unit 102 calls and executes an electronic lock management program from the memory 103.

  The network connection unit 104 connects to the LAN to enable the server device 100 to communicate with the administrator terminal 200. The network connection unit 104 connects to the Internet and enables the server device 100 to communicate with the mobile terminal 300.

  The storage unit 106 is a non-volatile storage medium that can read and write data, and stores a management list in advance. The management list includes the information on the management area, the information on the managed property, and the information on the electronic lock device 400 attached to the managed property described with reference to FIG. In the management list, the management area information, the managed property information, and the information of the electronic lock device 400 are associated with each other. The management list is stored in the storage unit 106 from the administrator terminal 200 via the LAN.

  In addition, the storage unit 106 stores a history list including the history of unlocking of the electronic lock device 400 installed in the managed property. The history list includes information on the time at which the electronic lock device 400 executed unlocking. Further, the storage unit 106 stores a key application file which is a program file of a key application which is installed in the mobile terminal 300 and causes the mobile terminal 300 to function as an electronic key terminal of the electronic lock device 400.

  The operation of the server device 100 will now be described by taking, as an example, a case where an emergency earthquake bulletin from the Meteorological Agency is received as disaster information. The control unit 102 acquires, via the network connection unit 104, an emergency earthquake flash report that is input from outside via a network. As described above, in the present embodiment, the control unit 102 and the network connection unit 104 function together and play a role as an information acquisition unit that acquires disaster information regarding a disaster.

  The control unit 102 recognizes a disaster prediction area from the acquired emergency earthquake flash report. The control unit 102 specifies a management area included in the recognized disaster prediction area. In the following description, the management area included in the damage prediction area may be referred to as a “damage prediction management area”.

  As described with reference to FIG. 1, after acquiring the disaster information, the control unit 102 transmits the unlock request mail as the unlock request of the electronic lock device from the portable terminal 300 to the server via the network connection unit 104. It is received by the device 100. As described above, in the present embodiment, it plays a role as a receiving unit that receives an unlock request for unlocking an electronic lock device of a managed property installed in a managed area.

  Next, the control unit 102 determines whether the target electronic lock device is included in the disaster prediction management area. First, the control unit 102 analyzes the received unlock request mail and specifies the target electronic lock device. Specifically, the control unit 102 searches the management list for the serial number of the electronic lock device attached to the received unlock request email. Then, the control unit 102 specifies the management area associated with the searched serial number.

  The control unit 102 determines whether the management area specified above is included in the damage prediction management area. When the control unit 102 determines that the management area is included in the disaster management area, the control unit 102 extracts the emergency key ID of the target electronic lock device from the management list stored in the storage unit 106.

  In this embodiment, a predetermined expiration date is set for the emergency key ID. In the present embodiment, the control unit 102 creates a file describing the emergency key ID extracted from the storage unit 106. Then, the control unit 102 writes the file creation time (year / month / day / minute / second) and the validity period in the header information of the file. In the following description, the created file may be referred to as a “key file”.

  In the present embodiment, the expiration date of the emergency key ID is managed by the key application. For example, the unlocking applicant who has acquired the emergency key ID whose validity period is set to 3 hours, when three hours have elapsed from the file creation time written in the key file, unlocks the electronic lock device 400 with the emergency key ID. It cannot be unlocked. As described above, by setting the expiration date for the emergency key ID, it is possible to limit the time during which the key can be unlocked freely, so that the security of the managed property can be ensured.

  Next, the control unit 102 creates a reply message to which the key application file stored in the storage unit 106 and the above-described key file are attached. The control unit 102 transmits the created reply message to the mobile terminal 300 via the network connection unit 104 as an unlock information notification mail for notifying unlock information. As described above, in the present embodiment, the control unit 102 and the network connection unit 104 function together and play a role as a providing unit that provides unlocking information for unlocking the target electronic lock device.

  The control unit 102 and the network connection unit 104 function together, and serve as a receiving unit that receives an unlock notification described below that is transmitted when the mobile terminal 300 in which the key application is installed unlocks the electronic lock device 400. Carry. The control unit 102 updates the history list stored in the storage unit 106 according to the information included in the unlock notification. Thereby, the unlocking execution time and the unlocking state of the electronic lock device 400 can be managed.

  FIG. 3 is a block diagram illustrating the configuration of the administrator terminal. The administrator terminal 200 includes a control unit 202 including, for example, a CPU, a network connection unit 204 that is a network interface, a display unit 206 including, for example, a liquid crystal display, and an operation unit 208 including, for example, a keyboard and a mouse. . The control unit 202 has a memory 203 composed of a nonvolatile memory such as a flash memory.

  The control unit 202 totally controls the operation of the components of the administrator terminal 200. The memory 203 stores a disaster occurrence notification program, which is an application program for notifying the server apparatus 100 by designating a management area in which it is estimated that a disaster has occurred.

  The network connection unit 204 connects to the LAN to enable the administrator terminal 200 to communicate with the server device 100. The display unit 206 displays a setting screen and a selection screen. The operation unit 208 receives inputs of various information from the administrator.

  When the administrator obtains information on the occurrence of an earthquake from an information source such as a television or a radio, the administrator activates the disaster occurrence notification program on the administrator terminal 200. When receiving a start instruction of the disaster occurrence notification program from the administrator, the control unit 202 calls up and executes the disaster occurrence notification program from the memory 203. The control unit 202 displays a designation operation screen for controlling the disaster occurrence notification program stored in the memory 203 on the display unit 206.

  The administrator operates the operation unit 208 to specify a management area where a disaster is presumed to have occurred on the designation operation screen displayed on the display unit 206. The control unit 202 receives a designated input of the management area from the manager, and transmits a disaster occurrence notification signal to the server device 100 according to the designated content.

  Further, in the present embodiment, every time the server device 100 acquires disaster information, the emergency key ID stored in advance in the server device 100 is updated using the administrator terminal 200. For example, three days after a disaster occurs, the administrator updates the emergency key ID with a new emergency key ID.

  Then, the control unit 202 transmits the new emergency key ID to the server device 100 via the LAN. The server device 100 overwrites the emergency key ID previously stored in the storage unit 106 with the new emergency key ID received from the administrator terminal 200. At the same time, the administrator changes the emergency authentication data stored in the electronic lock device installed in the managed property so as to correspond to the new emergency key ID. Thereby, every time disaster information is received, the emergency key ID is updated. Therefore, it is possible to prevent one emergency key ID from being reused for one managed property, thereby improving security. it can.

  FIG. 4 is a block diagram illustrating a configuration of the mobile terminal. The mobile terminal 300 includes, for example, a control unit 302 including a CPU, a network connection unit 304 as a network interface, and a communication unit 305 including an NFC interface using short-range wireless communication. The control unit 302 has a memory 303 configured from a nonvolatile memory such as a flash memory. In addition, the communication unit 305 may employ a communication standard other than NFC. For example, an infrared communication interface based on the Bluetooth (registered trademark) standard may be used. In addition to these, the mobile terminal 300 includes a display unit 306 configured by a liquid crystal display, for example, and an operation unit 308 configured by a touch panel, for example.

  An OS program and the like are stored in the memory 303 in advance. In addition, in the present embodiment, a key application for causing the portable terminal 300 to function as an electronic key terminal is stored in the memory 303.

  The unlocking applicant installs the key application on the mobile terminal 300 using the key application file attached to the unlocking information notification mail from the server device 100. The mobile terminal 300 stores the key file attached to the unlock information notification mail in a predetermined storage area. By performing the above processing, the portable terminal 300 functions as an electronic key terminal of the electronic lock device 400 and issues an unlock instruction to the electronic lock device 400.

  Further, after performing the unlocking operation, the portable terminal 300 receives an unlock notification signal indicating that the unlock described below has been performed from the electronic lock device 400. Then, the mobile terminal 300 generates log information including information such as the unlocking execution time from the received unlock notification signal, and transmits the log information to the server device 100.

  FIG. 5 is a block diagram illustrating the configuration of the electronic lock device. The electronic lock device 400 includes a control unit 402 including, for example, a CPU, a storage unit 403 including, for example, a hard disk drive, and a communication unit 404 including, for example, an NFC interface using short-range wireless communication. Note that the communication unit 404 may employ a communication standard other than NFC. For example, an infrared communication interface based on the Bluetooth (registered trademark) standard may be used. In addition, the electronic lock device 400 includes a drive unit 406 configured by, for example, a solenoid, and a lock unit 408 configured by, for example, a deadbolt that is displaced by driving of the drive unit 406.

  The communication unit 404 is arranged at the door of the managed property. When the mobile terminal 300 on which the key application is installed approaches the communication unit 404, the control unit 402 performs short-range wireless communication with the mobile terminal 300 via the communication unit 404, and performs emergency communication stored in the mobile terminal 300. Read the key ID.

  The control unit 402 determines whether the emergency key ID read from the mobile terminal 300 matches the emergency authentication data stored in the storage unit 403 in advance. If it is determined that the emergency key ID matches the emergency authentication data, the control unit 402 drives the drive unit 406 to unlock the lock unit 408.

  In addition, the electronic lock device 400 according to the present embodiment automatically performs locking when a predetermined time has elapsed after unlocking. The predetermined time is, for example, three hours.

  Note that the electronic lock device 400 is a device that is responsible for locking and unlocking a managed property that is a building related to a disaster. For example, a secondary battery or a solar power generator may be provided as a backup power supply, or a power supply terminal for connecting an external power supply may be provided. The power supply terminal is connected to, for example, a mobile battery that is also used for a smartphone, a portable generator that is generated by turning a steering wheel of a user, and the like. Further, the electronic lock device 400 may receive power supply from a smartphone via a USB cable or the like, for example. If application software for power supply is installed in the smartphone in advance, the electronic lock device 400 can receive power supply from the smartphone via a USB cable.

  FIG. 6 is a flowchart illustrating the operation of the electronic lock management system according to the first embodiment. Each column represents processing executed by the control unit 102 of the server device 100, the control unit 302 of the portable terminal 300, and the control unit 402 of the electronic lock device 400, respectively, in order from the left. Here, in the following description, each process is simply expressed as "the server device 100", "the portable terminal 300", "the electronic lock device 400" executes, and the like.

  The server device 100 stores the emergency key ID in the storage unit 106 (Step S101). As described above, the emergency key ID is stored in the storage unit 106 as a management list in association with the electronic lock device, the managed property, and the managed area. The administrator stores the emergency key ID associated with the electronic lock device installed in each of the managed properties in the storage unit 106. Further, the administrator sets emergency authentication data corresponding to the emergency key ID in the electronic lock device 400 (step S301). After completing the above introduction work, the electronic lock management system 10 shifts to the use state.

  The server device 100 determines whether disaster information has been acquired from the outside (step S102). If it is determined that disaster information has not been acquired (NO in step S102), server device 100 waits until disaster information is input from outside.

  If it is determined that disaster information has been acquired (YES in step S102), the server device 100 shifts to an unlock request waiting state (step S103). Specifically, the server device 100 starts timing and accepts the unlock request until a certain time has elapsed. Here, the certain time is, for example, three hours.

  An unlocking candidate who is the owner of the mobile terminal 300 desires to unlock a managed property to which the electronic lock device 400 is attached. Therefore, the unlocking candidate causes the portable terminal 300 to read the two-dimensional code presented on the notice 500 provided near the electronic lock device 400 (step S201). As described with reference to FIG. 4, when the two-dimensional code is read, the mailer of the mobile terminal 300 is automatically activated. Then, the mail address of server device 100 is input as the destination, and a new mail in which the serial number of electronic lock device 400 is described in the body is created. By the operation of the unlocking applicant, the portable terminal 300 transmits the created new mail to the server apparatus 100 as an unlocking request mail via the Internet (step S202).

  In step S104, server device 100 determines whether or not an unlock request has been made based on whether or not an unlock request email has been received. In step 104, the server device 100 also determines whether or not the electronic lock device 400 that is the target of the unlock request is included in the disaster-predicted area in the disaster information. In this flow, an explanation will be given assuming that the electronic lock device 400 to be unlocked is included in the disaster-predicted area. Note that, when the server device 100 determines that the electronic lock device 400 that is the target of the unlock request is not included in the disaster-predicted area, the server device 100 receives another unlock request without responding to the unlock request. Wait for.

  When the unlock request mail is received, that is, when it is determined that there is an unlock request (YES in step S104), the server device 100 specifies the target electronic lock device from the information of the received unlock request mail. The corresponding emergency key ID is extracted from the storage unit 106, and information on the file creation time and the validity period is added. Further, the server device 100 extracts the key application file from the storage unit 106. The server device 100 creates an unlock information notification mail to which the extracted key application file and the key file are attached, and transmits the unlock information notification mail to the mobile terminal 300 (step S107).

  It is preferable that the text of the unlock information notification mail describes a procedure necessary for the received unlocking applicant to unlock the target electronic lock device. In this embodiment, since the expiration date is set for the emergency key ID, the expiration date information is preferably described in the body of the unlock information notification mail. An example of the body of the unlock information notification mail is "Please install the key application from the attached key application file (key.apk)."

  On the other hand, when it is determined that the unlock request mail has not been received, that is, there is no unlock request (NO in step S104), the server device 100 determines whether a predetermined time has elapsed (step S105). ). If it is determined that the certain time has not elapsed (NO in step S105), server device 100 continues the waiting state for the unlock request. On the other hand, if it is determined that the predetermined time has elapsed (YES in step S105), server device 100 releases the waiting state for the unlock request (step S106), and shifts to the disaster information input waiting state. Specifically, the server device 100 does not accept the unlocking request until the end of the time measurement and further input of disaster information.

  Upon receiving the unlock information notification mail from the server device 100, the mobile terminal 300 displays the reception information of the unlock information notification mail on the display unit 306 (Step S203). It is preferable to display the notification information notification mail on the display unit 306 by an interrupt process in order to promptly notify the unlocking information notification mail to the unlocking applicant. Also, a ringtone may be generated at the same time.

  The mobile terminal 300 receives the operation of the unlocking applicant, and installs the key application from the key application file attached to the unlocking information notification mail (step S204). When the installation of the key application is completed, the portable terminal 300 starts measuring time (step S205). Next, the mobile terminal 300 stores the key file attached to the unlock information notification mail in a specific storage area (Step S206). After the process of step S206, the portable terminal 300 functions as an electronic key terminal of the electronic lock device 400. The following processing in the mobile terminal 300 is performed by executing the key application.

  The mobile terminal 300 determines whether the set time has elapsed (step S207). Here, the set time is the expiration date of the emergency key ID specified from the file creation time and the expiration date described in the key file. If it is determined that the set time has not elapsed (NO in step S207), portable terminal 300 determines whether or not it has approached electronic lock device 400 (step S209). If it is determined that the electronic lock device 400 has been approached (YES in step S209), the portable terminal 300 transmits the emergency key ID to the electronic lock device 400 (step S210). At this time, the mobile terminal 300 performs short-range wireless communication by entering the communication range of the electronic lock device 400 and transfers the emergency key ID.

  On the other hand, if it is determined in step S209 that it is not close to the electronic lock device 400 (NO in step S209), the portable terminal 300 returns to step S207 and returns to the electronic lock device 400 until the set time has elapsed. Wait for proximity detection.

  If it is determined in step 207 that the set time has elapsed (YES in step S207), portable terminal 300 displays on display unit 306 that the expiration date of the emergency key ID has elapsed (step S208). The portable terminal 300 displays, for example, a message “The expiration date has passed. The emergency storage warehouse XX cannot be unlocked.” On the display unit 306. The portable terminal 300 may notify the unlocking candidate of the expiration date by vibration, sound, or the like. After performing the processing in step S208, the portable terminal 300 proceeds to step S211.

  In step S302, electronic lock device 400 determines whether or not an unlock operation has been performed. Specifically, it is determined whether or not an emergency key ID has been received from mobile terminal 300. When it is determined that the unlocking operation has been performed (YES in step S302), the electronic lock device 400 executes an unlocking process of the electronic lock (step S303). The unlocking process in step S303 includes a process of transmitting an unlock notification signal indicating that unlocking has been performed to the mobile terminal 300. The unlock notification signal includes information on the unlock execution time.

  The electronic lock device 400 executes a locking process after the unlocking process of the electronic lock in step S303 (step S304). In the present embodiment, the electronic lock device 400 is set so as to automatically execute a locking process when a predetermined time has elapsed after the unlocking process.

  After executing the processing of step S208 or step S210, the portable terminal 300 performs processing of the unlock information (step S211). Here, the “unlock information” is log information including information on the unlocking execution time of the electronic lock device 400. When determining that the set time has elapsed in step S207, the mobile terminal 300 generates a log file in which unlock log information indicating that unlocking has not been performed is written. The log information includes information on the emergency key ID.

  On the other hand, the portable terminal 300 transmits the emergency key ID to the electronic lock device 400 in step S210, and when the unlock notification signal is received from the electronic lock device 400, the unlock indicating that the unlock has been executed. Generate a log file that contains log information. The unlock log information includes information on the unlock execution time and the emergency key ID.

  When step S211 is executed, the mobile terminal 300 activates the mailer and creates new mail data to which the log file generated in step S211 is attached. Then, portable terminal 300 transmits the created mail to server device 100. Thereafter, the mobile terminal 300 deletes the key application and the emergency key ID from the memory 303 (Step S212). At this time, the key file and the data of the unlock information notification mail are also deleted. After the above processing, the portable terminal 300 shifts to a standby state for an operation input such as reading of a two-dimensional code.

  Upon receiving the mail to which the log file is attached from the mobile terminal 300, the server device 100 executes a process of the history information (Step S108). Specifically, in the history list stored in the storage unit 106, the unlock history of the managed property in which the electronic lock device 400 is installed is updated.

  After executing step S108, the server device 100 resets the emergency key ID (S109). In the present embodiment, the server device 100 resets the emergency key ID by overwriting the emergency key ID stored in the storage unit 106 with the new emergency key ID received from the administrator terminal 200. After executing step S109, the server device 100 proceeds to step S102 and continues waiting for receiving disaster information.

  Further, the electronic lock device 400 receives resetting of the emergency authentication data (step S305). In the present embodiment, the administrator operates the electronic lock device 400 to update the emergency authentication data. When the above processing is completed, the electronic lock device 400 shifts to a standby state for an unlock operation.

  When the server device 100 updates the history list from the log file received from the mobile terminal 300, the server device 100 may transmit the updated history list to the administrator terminal 200. Thus, the manager can manage the time at which the emergency storage warehouse in the management area is unlocked and the mobile terminal that has performed the unlocking operation.

  FIG. 7 is a flowchart illustrating a modification of the electronic lock management system according to the first embodiment. Note that the description of the processing overlapping with the flow described with reference to FIG. 6 will be omitted.

  In this modification, the electronic lock device 400 is a ten-key input type electronic lock device. In this modification, the unlocking applicant performs the unlocking operation by directly inputting the emergency authentication data for unlocking from the numeric keypad of the electronic lock device 400.

  The server device 100 is the same as the flow described with reference to FIG. 6 up to step S104. If it is determined in step S104 that there is no unlock request (NO in step S104), server device 100 performs the same processing as the flow of FIG. 6 in the subsequent processing.

  On the other hand, if it is determined in step S104 that the unlock request mail has been received, that is, it has been determined that the unlock request has been made (YES in step S104), server device 100 distributes the emergency authentication data and the key application file by mail. In the present modified example, the server device 100 creates, as a key file, a file in which urgent authentication data, a file creation time, a validity period, and a code indicating a type of the electronic lock device are described. Here, the “code indicating the type of the electronic lock device” is a code associated with the authentication method of the electronic lock device. For example, the non-contact type is “11” and the numeric keypad type is “22”.

  The server device 100 transmits an unlock information notification mail to which the key application file and the key file are attached to the mobile terminal 300. Note that the example described with reference to FIG. 6 can be applied to the description of the body of the unlock information notification mail.

  The processing of the mobile terminal 300 is the same as the flow described using FIG. 6 up to step S206. The processing after step S206 is performed by the mobile terminal 300 executing the key application. After storing the key file in the specific storage area in step S206, portable terminal 300 displays emergency authentication data on display unit 306 (step S506). The unlocking applicant can perform the unlocking operation by directly inputting the displayed emergency authentication data into the numeric keypad of the electronic lock device 400.

  The mobile terminal 300 determines whether the set time has elapsed (step S207). If it is determined that the set time has not elapsed (NO in step S207), portable terminal 300 determines whether or not an unlocking request has been issued by an unlocking applicant (step S507).

  The display unit 306 of the mobile terminal 300 displays an “unlock notification” button for notifying the server device 100 that the unlocking operation of the electronic lock device 400 has been executed, in addition to the emergency authentication data. The unlocking applicant taps the “unlock notification” button on the display unit 306. When detecting that the “unlock notification” button has been tapped by the unlocking applicant, the portable terminal 300 determines that an unlock notification instruction has been issued (YES in step S507), and proceeds to step S508.

  On the other hand, when it is not detected that the “unlock notification” button has been tapped by the unlocking applicant, and it is determined that there is no unlock notification instruction (NO in step S507), the mobile terminal 300 proceeds to step S207. It returns and waits for an unlocking notification instruction from an unlocking applicant until the set time has elapsed.

  If it is determined in step S207 that the set time has elapsed (YES in step S207), portable terminal 300 displays on display unit 306 that the expiration date of the emergency authentication data has elapsed (step S208). Then, the mobile terminal 300 moves to step S508.

  After executing the processing of step S208 or S507, the mobile terminal 300 performs processing of the unlock information (step S508). When determining that the set time has elapsed in step S207, the mobile terminal 300 generates a log file in which log information indicating that unlocking has not been performed is written. The log information includes information on emergency authentication data.

  On the other hand, when it is determined in step S507 that the unlocking request has been issued by the unlocking requester, the mobile terminal 300 generates a log file in which log information indicating that unlocking has been executed is written. In the present modification, the time at which the tap of the “unlock notification” button on the display unit 306 by the unlocking candidate is detected is recorded as the time at which the unlocking is executed. The log information includes information on the unlocking execution time and the emergency authentication data.

  After executing step S508, the mobile terminal 300 activates the mailer and creates new mail data to which the log file generated in step S508 is attached. Then, portable terminal 300 transmits the created mail to server device 100. Thereafter, the mobile terminal 300 deletes the key application and the unlock information notification mail (Step S509). At this time, the key file is also deleted. When the above processing is completed, the portable terminal 300 shifts to a standby state such as an instruction to read a two-dimensional code.

  FIG. 8 is a schematic diagram illustrating an overview of an electronic lock management system according to the second embodiment. In FIG. 8, only the main components of the electronic lock management system 20 according to the present embodiment are extracted and shown.

  The electronic lock management system 20 is a system in which the unlocking of the electronic lock device 400 attached to the target managed property can be executed by another user instead of the unlocking applicant himself. Note that the management area A is one of a plurality of different management areas managed by the server device 100. Then, it is assumed that the management area A is included in the disaster prediction area of the disaster information.

  In FIG. 8, the management area A includes a district a. In the area "a", a managed property on which a management door D is built is installed. An electronic lock device 400 is attached to the management door D. In the district a, the managed property is managed by, for example, a chief of disaster prevention, a staff member a, and a staff member b.

  In this figure, the chief of disaster prevention is a person who unlocks the management door D when a disaster occurs in the area a. However, for example, when a disaster occurs, if the user is located far away from the vehicle, the management door D cannot be unlocked immediately. In such a case, in the present embodiment, the disaster prevention manager issues a request to unlock the electronic lock device 400 of the management door D from the terminal 600 to the server device 100, and carries the unlock information of another employee as the transmission destination of the unlock information. Terminal can be specified.

  In the present embodiment, the disaster prevention manager knows in advance the mail address of the server device 100 and the serial number of the electronic lock device 400 attached to the management door D. Then, when a disaster occurs in the area a, the disaster prevention manager sends an unlock request email from the terminal 600 to the server device 100. At this time, for example, the disaster prevention manager describes the terminal information of the transmission destination of the unlock information notification mail in the mail text. In FIG. 8, the chief of disaster prevention designates the portable terminal 300a of the staff member a and the portable terminal 300b of the staff member b as transmission destinations of the unlock information. In the present embodiment, the terminal information specified as the transmission destination is, for example, the mail address of the mobile terminals 300a and 300b.

  The server device 100 transmits the unlock information of the electronic lock device 400 to the designated mobile terminals 300a and 300b. Thereby, even if the disaster prevention chief who is the unlocking candidate cannot immediately unlock the door in the event of a disaster, another unlocking person can unlock the management door D. Therefore, for example, a property that needs to be unlocked as soon as possible at the time of a disaster such as an emergency shelter can be unlocked as soon as possible.

  Note that the server device 100 may further limit the transmission destination of the unlock information from among the plurality of transmission targets designated as the transmission destination of the unlock information, according to the status of the transmission target. As the state of the transmission target person, for example, the distance to the managed property, availability of correspondence, and the like are determined.

  The server device 100 may transmit the unlock information to a staff member near the managed property among the staff members a and b. For example, the server device 100 acquires the GPS information of each of the portable terminals of the staff member a and the staff member b, and specifies the staff member at a closer position from the position information of the managed property stored in advance. Then, the server device 100 transmits the unlock information to the specified staff. As described above, the unlock information is not transmitted to all transmission targets, but is transmitted only to transmission targets located closer to the managed property, whereby the security of the electronic lock management system 20 is improved. Can be enhanced.

  The server device 100 may transmit the unlock information to an employee who can perform unlocking among the staff members a and b. For example, the server device 100 transmits a correspondence confirmation mail to the staff members a and b as to whether or not the correspondence is possible. Then, when the server device 100 receives the reply mail indicating that the response is possible, the server device 100 may transmit the unlock information to the staff member who is the sender of the reply mail. In this way, by transmitting the unlock information to the transmission target who can immediately proceed to the unlocking operation to the managed property, instead of transmitting the unlock information to all the transmission targets, The security of the electronic lock management system 20 can be improved.

  In the above description, the embodiment in which the server device 100 transmits the unlock information for unlocking the electronic lock device 400 of the target property to the mobile terminal 300 has been described. The server device 100 may further transmit lock information for locking the electronic lock device 400 to the portable terminal 300 that has transmitted the unlock information. Thus, the unlocking candidate can lock the unlocked managed property using the mobile terminal 300. For this reason, security for preventing intrusion of a third party or the like can be enhanced.

  In the above-described embodiment, the server device 100 provides the unlocking information to the unlocking candidate or the like by directly attaching it to the electronic mail. However, when the server apparatus 100 receives the disaster information, the server apparatus 100 establishes a homepage including information on the unlocking method of the target electronic lock apparatus as content, and notifies the unlocking applicant of the URL of the homepage. Good.

  In the present embodiment, upon receiving any of the disaster information, the server device 100 opens a homepage for providing unlock information for unlocking an electronic lock of a managed property in the managed area. In the present embodiment, the electronic lock device 400 is a ten-key type electronic lock device in which a user inputs an authentication code for unlocking the electronic lock from the ten keys. The emergency authentication data for unlocking the electronic lock device 400 is disclosed on the emergency HP which is a homepage established by the server device 100.

  In the present embodiment, upon receiving the unlock request mail from the portable terminal 300 of the unlocking applicant, the server device 100 returns an unlock information notification mail in which the URL of the emergency HP is described as unlock information. The unlocking applicant accesses the emergency HP from the portable terminal 300 from the URL described in the unlocking information notification mail. Then, the unlocking applicant can perform the unlocking operation by directly inputting the emergency authentication data disclosed in the emergency HP to the numeric keypad of the electronic lock device 400.

  In this embodiment, the emergency HP is provided with an “unlock notification” button for notifying the server device 100 that the unlock has been performed. After performing the unlocking operation of the electronic lock device 400, the unlocking applicant taps the “unlock notification” button on the display unit 306. With this operation, the server device 100 detects that the unlock operation has been performed. Then, the server device 100 updates the history list stored in the storage unit 106 with the time at which the execution of the unlocking operation is detected as the unlocking time. Thereby, the server device 100 can manage the unlocking time of the electronic lock device 400.

  In the emergency HP, the server device 100 may be configured to be able to download a key application and obtain an emergency key ID. Thus, in the present embodiment, a non-contact authentication type electronic lock device can be applied to the electronic lock device 400.

  Further, when the server device 100 receives the disaster information, the server device 100 sets up an emergency dial which is a telephone guide for guiding the unlocking method of the electronic lock device 400 and notifies the emergency dialer of the unlocking request. Good. For example, upon receiving the unlock request mail from the portable terminal 300 of the unlocking applicant, the server device 100 returns an unlock information notification mail describing the emergency dial telephone number as unlock information. The person who wants to unlock can call the emergency dial from the portable terminal 300 or the like and acquire the unlocking method from the voice guidance.

  In this embodiment, access rights may be provided for the emergency HP and the emergency dial. For example, a password for browsing the emergency HP is provided in advance as accompanying information accompanying the unlock request, and when the unlocking applicant accesses the emergency HP, an input of the browsing password is separately requested. Similarly, a voice reproduction password for reproducing the voice guidance by the emergency dial is provided in advance, and when the unlocking candidate reproduces the voice guidance, transmission of the voice reproduction password is separately requested. In this case, only the user having the unlocking authority is notified of the password. Thus, the unlocking method of the electronic lock device 400 can be disclosed only to the unlocking applicant having the unlocking authority, so that the security of the managed property can be improved.

  In the present embodiment, an example has been described in which the URL of the emergency HP and the telephone number of the emergency dial established by the server apparatus 100 are transmitted as unlocking information to the portable terminal 300 of the unlocking applicant. However, the URL of the emergency HP and the telephone number of the emergency dial may be notified in advance. For example, the URL of the emergency HP or the telephone number of the emergency dial may be described in the notification 500. When the unlocking candidate accesses the emergency HP and the emergency dial, the server device 100 may request the browsing password of the emergency HP and the voice reproduction password of the emergency dial as described above. Then, the server apparatus 100 receives the input of the password from the unlocking applicant as an unlocking request, and displays an emergency HP or reproduces a voice from the emergency dial when a predetermined password is input. Alternatively, the unlock information may be provided to the unlocking applicant.

  In the above description, the example has been described in which the electronic lock management device is configured by one server. However, the electronic lock management device may be composed of a plurality of servers, and each server may have a different role. For example, the server that acquires the disaster information and the server that transmits the unlock information to the mobile terminal 300 may be different server devices.

  In the above description, the server device 100 requests unlocking when acquiring an emergency signal such as an emergency earthquake bulletin transmitted from an administrative organization or a disaster occurrence notification signal from the administrator terminal 200. This has been described using the example of transmitting the unlock information to the portable terminal 300 of the unlocking applicant. However, when both the emergency signal and the disaster occurrence notification signal are acquired, the server device 100 may transmit the unlock information to the portable terminal 300 of the unlocking applicant who requests unlocking. By using the reception of the two signals, the emergency signal and the disaster occurrence notification signal, as a trigger to start the operation of transmitting the unlock information, the credibility of the disaster information can be increased. Further, when the server device 100 acquires the emergency signal, the server device 100 transmits a signal notifying that the emergency signal has been acquired to the administrator terminal 200 to urge the administrator to transmit the disaster occurrence notification signal. Good. In this case, the disaster occurrence notification signal transmitted from the administrator terminal 200 is used as an approval signal for the server device 100 to transmit the unlock information to the portable terminal 300 of one of the registrants. Has the meaning of When receiving the approval signal, the server device 100 transmits the unlock information to the portable terminal 300 of the unlocking applicant. On the other hand, when the server device 100 does not receive the approval signal, the server device 100 does not have to transmit the unlock information to the portable terminal 300 of the unlocking applicant. Further, the approval signal may include information on whether or not to approve the transmission of the unlock information. The server device 100 determines whether to transmit the unlock information to the portable terminal 300 of the unlocking candidate based on the information on whether or not to approve the transmission of the unlock information included in the approval signal. You may.

  In the above description, the embodiment has been described in which the server apparatus 100 limits the management area that receives the unlock request from the damage prediction area included in the acquired disaster information. However, the server device 100 may receive the unlock request for all the management areas without limiting the management area for receiving the unlock request according to the disaster information. Further, the server device 100 may receive the unlock request by extending the range to the management area adjacent to the limited management area. Thus, for example, if the actual stricken area is wider than the range of the stricken area in the disaster information, the managed property can be unlocked as needed even in the stricken area not included in the stricken area.

  In the above description, an emergency signal such as an emergency earthquake flash report transmitted from an administrative agency and a disaster occurrence notification signal from the administrator terminal 200 of the administrator who has obtained information on the occurrence of a disaster have been described as examples of disaster information. . However, the server device 100 may use other inputs as disaster information. For example, a detection unit that detects the occurrence of a disaster is installed near the server device 100 and connected to the server device 100. Then, the server device 100 may acquire the result of the disaster detection by the detection unit as disaster information. The detection result of the disaster by the detection unit is not one detected in the management area. Although the detection result cannot accurately grasp the occurrence state of the disaster in the management area, it is a result of the detection unit detecting that the disaster has occurred, and thus can be treated as disaster information.

  In the above description, the unlock information transmitted to the portable terminal 300 of the unlocking applicant has been described as the information for unlocking the managed property. However, the server device 100 may change the unlock information transmitted to the unlocking applicant's mobile terminal 300 according to the characteristics of each managed property. For example, when the managed property is a disaster prevention storage warehouse, it is preferable that the property be locked for the purpose of preventing the intrusion of a third party except in the case of taking out supplies even in an emergency. On the other hand, when the managed property is an evacuation site, it is preferable that evacuees can enter and leave at any time. For this reason, for example, when the managed property is a disaster prevention storage warehouse, the server device 100 may transmit locking / unlocking information for locking / unlocking. Further, when the managed property is an evacuation site, the server device 100 may transmit unlock information that allows only unlocking.

  In the above description, the embodiment in which the expiration date is set for the emergency key ID transmitted from the server device 100 and the unlockable time is limited has been described. However, the emergency key ID may be set not with the expiration date but with the number of unlockable times, or the expiration date and the number of unlockable times may be set together.

  In the above description, an example in which the administrator changes the emergency key ID stored in the server device 100 and the emergency authentication data stored in the electronic lock device 400 every time the server device 100 acquires the disaster information. Was explained. However, each time disaster information is acquired, the server device 100 may generate and issue an emergency key ID. In this case, for example, a password generation program using a hash function or the like is installed in the electronic lock device 400 in advance, and the server device 100 uses the program to generate the emergency key ID based on the generation time (year / month / day / minute / second). Generate Then, server device 100 transmits the emergency key ID to mobile terminal 300 together with the information on the generation time. The electronic lock device 400 reads the information on the emergency key ID and the generation time from the portable terminal 300, and unlocks the password when the password generated using the program from the generation time matches the emergency key ID. It may be configured as follows. By employing such a configuration, it is possible to save the administrator from having to reset the emergency key ID and the emergency authentication data.

  In the above description, an example in which the electronic lock device 400 is not connected to an external network has been described. However, the electronic lock device 400 may be connected to an external network, or may be able to communicate with the server device 100 via the network. Thus, the administrator can update the emergency authentication data of the electronic lock device 400 at the timing of updating the emergency key ID by remote operation from the administrator terminal 200 via the network.

  In the above description, an example has been described in which the lock installed in the management target is an electronic lock. However, the lock attached to the managed property may be, for example, a lock that is unlocked using a physical key or a safe lock. In the case of a lock that is unlocked using a physical key, the server device 100 may transmit information on the management location of the key for unlocking the lock to the mobile terminal 300 as unlock information. . Further, in the case of a safe lock, the server device 100 may transmit information of an operation procedure for unlocking the safe lock to the portable terminal 300 as unlock information.

  As described above, the present invention has been described using the embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments. It is apparent to those skilled in the art that various changes or improvements can be made to the above embodiment. It is apparent from the description of the appended claims that embodiments with such changes or improvements can be included in the technical scope of the present invention.

  The execution order of each processing such as operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, the description, and the drawings is particularly “before”, “before”. It should be noted that they can be realized in any order as long as the output of the previous process is not used in the subsequent process. Even if the operation flow in the claims, the specification, and the drawings is described using “first,” “second,” or the like for convenience, it means that it is essential to perform the operation in this order. Not something.

10, 20 electronic lock management system, 100 server device, 102 control unit, 103 memory, 104 network connection unit, 106 storage unit, 200 administrator terminal, 202 control unit, 203 memory, 204 network connection unit, 206 display unit, 208 Operation unit, 300 mobile terminal, 302 control unit, 303 memory, 304 network connection unit, 305 communication unit, 306 display unit, 308 operation unit, 400 electronic lock device, 402 control unit, 403 storage unit, 404 communication unit, 406 drive Part, 408 lock part, 500 notice, 600 terminal, A1, A2, B1, B2, B3, C1, C2, D management door

Claims (4)

An information acquisition unit for acquiring disaster information relating to the disaster,
A reception unit that receives an unlock request for unlocking an electronic lock installed in a specific area,
If the information acquisition unit is the receiving unit after obtaining the disaster information is accepted the unlocking request, Bei example a providing unit for providing the unlocking information for unlocking the electronic lock,
The receiving unit receives the unlock request and terminal information of a mobile terminal specified as a transmission destination of the unlock information from a terminal device via a network,
The electronic lock management device , wherein the providing unit transmits the unlock information to the designated portable terminal based on the terminal information .   The electronic lock management device according to claim 1, wherein the information acquisition unit acquires an emergency signal transmitted from a government agency as the disaster information.   The electronic lock management device according to claim 1, wherein the information acquisition unit acquires an input from an authorized administrator as the disaster information. An information acquisition step for acquiring disaster information relating to the disaster;
A receiving step of receiving an unlock request for unlocking an electronic lock installed in a specific area;
And providing the unlock information for unlocking the electronic lock when the unlock request is received by the receiving step after obtaining the disaster information by the information obtaining step. Let it run ,
In the receiving step, receiving the unlock request and terminal information of the mobile terminal specified as a transmission destination of the unlock information from a terminal device via a network,
In the providing step, an electronic lock management program for transmitting the unlock information to the designated portable terminal based on the terminal information .

Images