JP6660158B2 - 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 if 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. Not only in the case of emergency earthquake bulletin, there is a problem that when information about a disaster is received, the electric lock is automatically unlocked even if the information is incorrect.

  An electronic lock management device according to a first aspect of the present invention includes a registration unit in which one or more mobile terminals associated with an electronic lock installed in a specific area are registered, and an information acquisition unit that acquires disaster information regarding a disaster. And a transmission unit that transmits unlock information for unlocking the electronic lock to at least one of the mobile terminals registered in the registration unit when the information acquisition unit acquires the disaster information.

  An electronic lock management program according to a second aspect of the present invention includes a registration step of registering one or more mobile terminals associated with an electronic lock installed in a specific area, an information acquisition step of acquiring disaster information relating to a disaster. And transmitting the unlock information for unlocking the electronic lock to at least one of the mobile terminals registered in the registration 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. It is a figure showing an example of a registration list. 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 schematic diagram explaining the outline | summary of the electronic lock management system which concerns on 2nd Embodiment. It is a flowchart explaining operation | movement 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 configured with a server device 100, an administrator terminal 200, a mobile terminal 300 (300a to i in the figure), and an electronic lock device 400 (400A to 400C 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 electronic lock management system 10 can be applied to, for example, a disaster prevention storage warehouse, an evacuation center, and the like. In the present embodiment, a case where the electronic lock management system 10 is applied to a disaster prevention storage warehouse will be described as an example.

  The server device 100 plays a role as an electronic lock management device that manages locking and unlocking of the electronic lock device 400. The server device 100 collectively manages unlock information for unlocking a lock mechanism of an electronic lock device attached to a door of a disaster prevention storage warehouse installed in a plurality of specific areas. 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”.

  FIG. 1 shows a region A, a region B, and a region C as management regions different from each other. In the present embodiment, each of the management areas is, for example, an area of a unit of municipalities. Each of the managed areas includes a plurality of disaster-prevention storage warehouses, which are properties to be managed. In the following description, a property that is installed in a management area and that is subject to lock / unlock management may be referred to as a “managed property”.

  In FIG. 1, in the area A, a disaster prevention storage warehouse A1 is shown as a representative of a plurality of management properties installed. An electronic lock device 400A is installed on the door of the emergency storage warehouse A1. In the area B, a disaster prevention storage warehouse B1 is shown as a representative of a plurality of installed managed properties. An electronic lock device 400B is installed on the door of the disaster prevention storage warehouse B1. In the area C, a disaster prevention storage warehouse C1 is shown as a representative of a plurality of installed managed properties. An electronic lock device 400C is installed on the door of the disaster prevention storage warehouse C1.

  In the server device 100, one or more mobile terminals associated with the electronic lock device of the managed property installed in the managed area are registered in advance. In other words, the server device 100 stores a plurality of mobile terminals in association with the electronic lock devices installed in the respective emergency storage warehouses. These mobile terminals are used as electronic key terminals in an emergency. In FIG. 1, portable terminals 300a, 300b, and 300c are associated with the electronic lock device 400A. In addition, portable terminals 300d, 300e, and 300f are associated with the electronic lock device 400B. The portable terminals 300g, 300h, and 300i are associated with the electronic lock device 400C.

  In FIG. 1, a registrant a who is the owner of the portable terminal 300a, a registrant b who is the owner of the portable terminal 300b, and a registrant c who is the owner of the portable terminal 300c are shown in the area A. . In the area B, a registrant d who is the owner of the mobile terminal 300d, a registrant e who is the owner of the mobile terminal 300e, and a registrant f who is the owner of the mobile terminal 300f are shown. In the area C, a registrant g who is the owner of the portable terminal 300g, a registrant h who is the owner of the portable terminal 300h, and a registrant i who is the owner of the portable terminal 300i are shown. In the present embodiment, the registrants a to i are, for example, local government officials in each area.

  The server device 100 stores in advance the information of the management area, the managed property, and the mobile terminal associated with each other as a registration list as described above. Details of the registration list will be described later.

  It is preferable that the server device 100 be installed in a place that is not included in any management area. The server device 100 receives disaster information regarding a disaster. 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, upon receiving any of the above disaster information, the server device 100 transmits an emergency key ID for unlocking the electronic lock of the managed property in the managed area to the specific portable terminal. Here, the “emergency key ID” is an authentication ID for unlocking the electronic lock used in an emergency such as a disaster. In the present embodiment, the expiration date is determined in advance for the emergency key ID. For this reason, the registrant cannot unlock the emergency storage with the emergency key ID after a predetermined time has elapsed after receiving the emergency key ID transmitted from the server device 100.

  Electronic lock device 400 reads the authentication ID from mobile terminal 300. The electronic lock device 400 collates the read authentication ID with authentication data stored in advance. As a result of the comparison, when the authentication ID and the authentication data match, the electronic lock device 400 releases the lock.

  In the electronic lock device 400 according to the present embodiment, emergency authentication data for authenticating the electronic key in an emergency is stored in advance in addition to authentication data for authenticating the electronic key in a normal state.

  In the present embodiment, the emergency key ID and the emergency authentication data are updated by the administrator every time the server device 100 receives the disaster information. In the present embodiment, the emergency key ID stored in advance in the storage unit of the server device 100 is rewritten from the administrator terminal 200 to a new emergency key ID via the network. Further, in the present embodiment, the emergency authentication data stored in advance in the electronic lock devices installed in the respective managed properties is updated by a direct input operation by the administrator.

  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 emergency key ID is transmitted to the registrant associated with the managed property, instead of automatically unlocking only based on the disaster information, and the registrant determines the disaster status at the site. A configuration that can determine whether or not unlocking is necessary. In this way, by intervening the judgment of the registrant 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. it can. 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. 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 control unit 102 and the network connection unit 104 function together and play a role as an information acquisition unit for acquiring disaster information on a disaster.

  The storage unit 106 plays a role as a registration unit in the present embodiment. The storage unit 106 stores a registration list in advance. The registration list includes managed area information, which is information on the managed area, managed property information, which is information on managed properties included in the managed area, and registered terminal information, which is information on mobile terminals associated with each of the managed properties. Have been. In the registration list, the managed area information, the managed property information, and the registered terminal information are associated with each other. The registration 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 and locking of the electronic lock of the electronic lock device installed in the managed property. In the history list, information on the execution time of locking and unlocking of each electronic lock device, information on the mobile terminal that has executed unlocking, and the like are recorded.

  The control unit 102 and the network connection unit 104 function together and play a role as a state acquisition unit that acquires the state of the mobile terminal. In the present embodiment, the state acquisition unit acquires, as the state of the mobile terminal, location information on the location of the mobile terminal. In the following description, the location information of the mobile terminal may be referred to as “terminal location information”. In the present embodiment, the terminal location information is a value of latitude and longitude.

  The control unit 102 and the network connection unit 104 function together and play a role as a transmission unit. The transmitting unit transmits the emergency key ID for unlocking the target disaster prevention storage warehouse to at least one of the mobile terminals registered in the registration unit when the information obtaining unit obtains the disaster information.

  Further, the control unit 102 plays a role as a determination unit. The deciding unit compares the terminal position information acquired by the state acquiring unit with the installation position of the target disaster prevention storage warehouse, and decides to which portable terminal the emergency key ID is to be transmitted. In the present embodiment, the determination unit determines the mobile terminal closest to the installation position of the target disaster prevention storage warehouse as the transmission destination of the emergency key ID.

  Specifically, the determining unit calculates the distance between the disaster prevention storage warehouse and the mobile terminal using a known calculation method from the latitude and longitude values of the target disaster prevention storage warehouse and the latitude and longitude values of the mobile terminal. I do. The determination unit calculates the distance for each of the mobile terminals associated with the target disaster prevention storage warehouse. Then, the determining unit compares the calculated distances with each other to identify the mobile terminal closest to the disaster prevention storage warehouse, and determines the mobile terminal as the transmission destination of the emergency key ID.

  The transmitting unit transmits the emergency key ID to the portable terminal determined as the destination of the emergency key ID by the determining unit. Specifically, the transmission unit transmits an emergency key ID for unlocking the electronic lock of the target disaster prevention storage warehouse to the portable terminal by e-mail.

  Upon receiving the disaster information, the server device 100 starts an emergency key ID transmission processing operation for unlocking the electronic lock installed in the managed property. Hereinafter, the transmission processing operation of the emergency key ID by the server device 100 when receiving the earthquake early warning from the Meteorological Agency will be described more specifically.

  The control unit 102 analyzes the emergency earthquake bulletin obtained from the Meteorological Agency, and certifies the disaster prediction area included in the emergency earthquake bulletin. Here, the “disaster predicted area” is an area where, for example, a seismic intensity of 4 or more is predicted in the emergency earthquake bulletin. The control unit 102 determines whether or not the recognized disaster-predicted area includes a management area registered in the registration list.

  When the control unit 102 determines that the management area registered in the registration list is included in the disaster-predicted area, the control unit 102 deletes the mobile terminal registered in association with the disaster prevention storage warehouse installed in the management area. The emergency key ID is a candidate for transmission. In the following description, the management area included in the damage prediction area may be referred to as a “damage prediction management area”.

  The server device 100 requests all mobile terminals in the disaster management area to transmit terminal position information via the Internet. Each of the mobile terminals that has received the request for the terminal location information from the server device 100 transmits its own terminal location information to the server device 100. The control unit 102 stores the terminal position information acquired from each mobile terminal in the storage unit 106 in association with the identification ID of the mobile terminal. Here, the “identification ID” is an ID unique to the mobile terminal, such as a device ID.

  The control unit 102 specifies the mobile terminal closest to the target disaster prevention storage warehouse from the position information of the disaster prevention storage warehouse installed in the management area registered in the registration list and the terminal position information. Then, the control unit 102 transmits the emergency key ID of the disaster prevention storage warehouse to the specified portable terminal. More specifically, with reference to FIG. 1, the control unit 102 determines, based on the position information of the disaster prevention storage warehouse A1 and the terminal position information of each of the mobile terminals 300a, 300b, and 300c, the disaster prevention storage warehouse A1 Calculate the distance of the mobile terminal. Then, the control unit 102 compares the calculated distances with each other and specifies the mobile terminal closest to the emergency storage warehouse A1. In FIG. 1, the control unit 102 specifies the mobile terminal 300a as the mobile terminal closest to the emergency storage warehouse A1. The control unit 102 transmits the emergency key ID of the emergency storage warehouse A1 to the portable terminal 300a via the network connection unit 104.

  The registrant a of the portable terminal 300a that has received the emergency key ID from the server device 100 grasps the magnitude of the disaster at the site where the disaster prevention storage warehouse A1 is installed, and determines whether to unlock the disaster prevention storage warehouse A1. decide. That is, when the registrant a determines that the damage caused by the disaster is minor, the registrant a does not perform the unlocking operation of the disaster prevention storage warehouse A1. On the other hand, when the registrant a determines that the damage caused by the disaster is enormous, the registrant a unlocks the disaster prevention storage warehouse A1. As described above, the registrant at the site confirms the scale of damage around the managed property and determines whether or not to unlock the managed property, whereby the disaster information received by the server apparatus 100 is a false report. Even if it does, unnecessary unlocking can be prevented.

  FIG. 3 is a diagram illustrating an example of the registration list. Specifically, this figure shows a registration list stored in advance in the server device 100 described with reference to FIG.

  A plurality of management areas are registered in the server device 100. One or more managed properties are registered in each of the plurality of managed areas. One or more mobile terminals are associated with each managed property and registered in the server device 100. In the example of the registration list shown in this figure, managed property information and registered terminal information are grouped and listed for each management area.

  FIG. 3 shows a registration list of three management areas, “Area A”, “Area B”, and “Area C”, as management area information that is information of the registered management areas. In addition, it is shown that three managed properties are registered in each of the managed areas “Area A”, “Area B”, and “Area C”. For example, as the managed property information of “Area A”, “disaster prevention storage warehouse A1”, “disaster prevention storage warehouse A2”, and “disaster prevention storage warehouse A3” are indicated.

  As the position information of the managed property “disaster prevention storage warehouse A1”, “longitude xx.xxxx latitude yyy.yyy” is indicated. “Longitude yy.yyy latitude zzz.zzz” is indicated as position information of the managed property “disaster prevention storage warehouse A2”. Then, "longitude zz.zzz, latitude xxx.xxxx" is indicated as position information of the managed property "disaster prevention storage warehouse A3".

  FIG. 3 shows that a plurality of mobile terminals are registered in association with each of the three managed properties. As the registered terminal information, the identification ID and the mail address of the mobile terminal are shown. In this drawing, for example, the identification IDs of the mobile terminals registered in association with “Disaster Prevention Storage Warehouse A1” are “XXXXXXXX”, “□□□□□□□□”, and “△”. Δ △△△△△△ ”is shown. Then, the mail address of each mobile terminal is shown.

  FIG. 4 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, the administrator updates the emergency key ID stored in advance in the server device 100 using the administrator terminal 200 every time the server device 100 receives the disaster information. For example, the administrator updates the emergency key ID to a new emergency key ID three days after the occurrence of the disaster.

  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. 5 is a block diagram illustrating the configuration of the mobile terminal. The mobile terminal 300 is, for example, a smartphone. 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.

  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.

  In the portable terminal 300, application software for performing a locking / unlocking operation by performing short-range wireless communication with the electronic lock device 400 is installed in advance and stored in the memory 303. When the portable terminal 300 receives an unlocking state signal indicating that unlocking has been performed from the electronic lock device 400 after executing the locking / unlocking operation, the mobile terminal 300 transmits log information indicating that unlocking has been performed to the server device. Send to 100. Although details will be described later, the log information transmitted from the mobile terminal 300 to the server device 100 includes information on the identification ID of the mobile terminal and the unlock time.

  FIG. 6 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 driven by the drive unit 406.

  The communication unit 404 is arranged at the door of the managed property. When the mobile terminal 300 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 reads the emergency key ID stored in the mobile terminal 300.

  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.

  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. 7 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 according to the present embodiment manages a plurality of managed properties in each of a plurality of managed areas. In this figure, the operation of the mobile terminal 300 registered in association with one managed property in one managed area is shown as a representative. The operation of the electronic lock device 400 installed in the managed property is shown as a representative.

  First, in step S101, the server device 100 stores a registration list including management area information, management property information, and registration terminal information in the storage unit 106 (step S101). Then, 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 the disaster information has been acquired (YES in step S102), the server device 100 certifies the estimated disaster area included in the acquired disaster information (step S103). Next, the server device 100 determines whether or not the management area registered in the registration list is included in the disaster-predicted area recognized in Step S103 (Step S104).

  If it is determined that the registered management area is not included in the recognized disaster prediction area (NO in step S104), the server device 100 returns to step S102 and receives disaster information from outside. Wait until. On the other hand, if it is determined that the registered management area is included in the recognized disaster prediction area (YES in step S104), the server apparatus 100 determines whether the disaster management area is the management area included in the damage prediction area. In the predicted management area, a position information request signal for requesting terminal position information is transmitted to mobile terminals registered in the registration list (step S105).

  The mobile terminal 300 receives a GPS signal transmitted from a GPS satellite at a predetermined time interval. The mobile terminal 300 calculates and acquires GPS information that is its own terminal position information from the received GPS signal (step S201). Upon receiving the position information request signal transmitted from server device 100 in step 105, portable terminal 300 transmits a terminal position signal including its own identification ID information and terminal position information to server device 100.

  Server device 100 determines whether or not there is a response from the mobile terminal that transmitted the position information request signal in step S105 (step S106). Specifically, server device 100 determines whether or not a terminal position signal has been received from the mobile terminal. When it is determined that there is no response (NO in step S106), server device 100 determines all terminals that have transmitted the position information request signal as targets for transmitting the emergency key ID (step S107).

  On the other hand, if it is determined in step S105 that there has been a response from the mobile terminal that transmitted the position information request signal (YES in step S106), server device 100 determines the emergency key ID from the information included in the received terminal position signal. Is determined as the mobile terminal to be transmitted (step S108). Specifically, as described with reference to FIG. 2, the server device 100 specifies the mobile terminal closest to the managed property from the location information of the managed property and the terminal location information included in the received terminal location signal. . Then, server device 100 determines the specified portable terminal as a target to which the emergency key ID is transmitted.

  Next, the server device 100 transmits the emergency key ID to the mobile terminal determined to be transmitted in step S107 or S108 (step S109). Specifically, as described with reference to FIG. 2, the server device 100 transmits the emergency key ID by e-mail to the mail address of the target portable terminal. In the present embodiment, the expiration date is set for the emergency key ID. The server device 100 transmits an e-mail in which the information of the expiration date of the emergency key ID is described in the text. The server apparatus 100 may, for example, say, "The expiration date of the emergency key ID is aaa / bb / cc / dd / dd / ee. When unlocking the emergency storage warehouse A1, the emergency operation must be performed before this expiration date. Please do this. "To the mobile terminal.

  The mobile terminal 300 determines whether or not the emergency key ID has been received from the server device 100 (Step S203). If it is determined that the emergency key ID has not been received (NO in step S203), the mobile terminal 300 shifts to step S201 and waits.

  On the other hand, if it is determined that the emergency key ID has been received (YES in step S203), portable terminal 300 starts timing (step S204). The reception of the emergency key ID from the server device 100 is detected by receiving an e-mail from the server device 100 in step S109.

  The mobile terminal 300 displays the e-mail received from the server device 100 on the display unit 306 as reception information (Step S205). The registrant who owns the mobile terminal that has received the electronic mail from the server device 100 can know the expiration date of the emergency key ID from the mail text described in step S109.

  The mobile terminal 300 determines whether the set time that is the expiration date of the emergency key ID has elapsed (step S206). When determining that the set time has elapsed (YES in step S206), portable terminal 300 shifts to step S209.

  On the other hand, when determining that the set time has elapsed (NO in step S206), portable terminal 300 shifts to step S207 and waits until proximity to electronic lock device 400 is detected. The mobile terminal 300 determines whether or not the mobile terminal 300 has approached the electronic lock device 400 installed in the target disaster prevention storage warehouse (step S207).

  The registrant who owns the portable terminal 300 determines whether or not unlocking is necessary based on the damage situation at the site where the target disaster prevention storage warehouse is installed. Then, if it is determined that the unlocking is necessary, the registrant performs the unlocking operation by bringing the portable terminal 300 close to the electronic lock device 400. On the other hand, if it is determined that the unlocking is unnecessary, the registrant does not perform the unlocking operation.

  When determining that the mobile terminal 300 has approached the electronic lock device 400 (YES in step S207), the mobile terminal 300 requests the electronic lock device 400 to unlock the electronic lock (step S208). Specifically, the portable terminal 300 transmits an emergency key ID to the electronic lock device 400 together with an unlock request signal requesting unlocking of the electronic lock. On the other hand, when the portable terminal 300 determines that it is not close to the electronic lock device 400 (NO in step S207), the process proceeds to step S206.

  The electronic lock device 400 determines whether or not there has been an unlock request from the mobile terminal 300 (step S302). Specifically, it is determined whether or not an unlock request signal and an emergency key ID have been received from portable terminal 300. If it is determined that there is an unlock request from the mobile terminal 300 (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). Note that the locking process in step S304 includes a process of transmitting a locking notification signal indicating that locking has been performed to the mobile terminal 300. The lock notification signal includes information on the lock execution time.

  In step S209, the mobile terminal 300 performs processing of the unlock information (step S209). Here, the “unlock information” is log information including information on an unlock execution time and a lock execution time of the electronic lock device 400. When determining that the set time has elapsed in step S206, the mobile terminal 300 generates log information indicating that unlocking has not been performed. The log information includes information of the identification ID of the mobile terminal 300.

  On the other hand, in step S208, the portable terminal 300 issues an unlock request to the electronic lock device 400, and upon receiving an unlock notification signal from the electronic lock device 400, generates log information indicating that unlocking has been performed. I do. The log information includes information on the identification ID of the mobile terminal 300 and the unlocking execution time.

  After executing step S209, the mobile terminal 300 deletes the emergency key ID received from the server device 100 from the memory 303 (step S210). Then, the mobile terminal 300 transmits the log information generated in step S209 to the server device 100. When the above process is completed, the portable terminal 300 proceeds to step S201 and continues to acquire GPS information.

  Upon receiving the log information from the mobile terminal 300, the server device 100 executes a process of the history information (Step S110). Specifically, in the history list stored in the storage unit 106, the history of unlocking in the emergency storage warehouse where the electronic lock device 400 is installed is updated.

  After executing step S110, the server device 100 resets the emergency key ID (S111). 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 S110, server device 100 shifts to a state of accepting the update of the registration list (step S112). In the state of step S112, the administrator can update the registration list. Then, 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 continues to wait for reception of the unlock request signal from the mobile terminal.

  When updating the history list from the unlock information 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.

  In the above description, the server device 100 has transmitted the unlock information to the mobile terminal closest to the target disaster prevention storage warehouse among the registered mobile terminals. However, for example, there may be a situation in which the registrant owning the portable terminal closest to the target disaster prevention storage warehouse is damaged and cannot move. Therefore, the server device 100 may determine whether or not the registrant is moving as a condition for transmitting the unlock information. In this case, the server device 100 acquires the terminal location information of each registered mobile terminal at predetermined time intervals. Then, when there is a change in the terminal location information acquired at each timing, the server device 100 determines that the registrant is moving, and transmits the unlock information to the portable terminal of the registrant. Thereby, the server device 100 can transmit the unlock information to the registrant who is close to the target disaster prevention storage warehouse and can move, thereby increasing the certainty that the disaster prevention storage warehouse is unlocked. it can.

  FIG. 8 is a schematic diagram illustrating 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. 8, elements common to those of the electronic lock management system according to the first embodiment described with reference to FIG. 1 are denoted by the same reference numerals, and redundant description will be omitted.

  The electronic lock management system 20 according to the present embodiment has the same configuration as the electronic lock management system 10 according to the first embodiment. In the present embodiment, the state obtaining unit obtains, as the state of the mobile terminal, whether the mobile terminal 300 has transmitted a request signal requesting unlock information of the electronic lock. In the present embodiment, upon receiving the disaster information, the server device 100 determines whether the mobile terminal registered in the management area included in the disaster-predicted area included in the disaster information can respond to the unlocking operation of the disaster prevention storage warehouse. Contact For example, the server device 100 transmits a supportability confirmation signal to the mobile terminal 300.

  In the present embodiment, a compatibility notification program, which is an application program for notifying the server device 100 of the compatibility, is installed in the memory 303 of the mobile terminal 300. Upon receiving the supportability confirmation signal from the server device 100, the control unit 302 activates the supportability notification program stored in the memory 303. Then, the control unit 302 causes the display unit 306 to display an operation screen for controlling the correspondence availability notification program on the display unit 306.

  The registrant who owns the mobile terminal 300 inputs a response on the operation screen displayed on the display unit 306. Upon receiving an instruction from the registrant that support is possible, control unit 302 transmits an unlock information request signal, which is a request signal for requesting unlock information, to server device 100. On the other hand, when receiving an instruction indicating that correspondence is not possible from the registrant, control unit 302 does not transmit the unlock information request signal to server device 100.

  In the present embodiment, when the state acquisition unit receives the unlock information request signal from the mobile terminal 300, the determination unit determines the mobile terminal 300 as a target for transmitting the emergency key ID. Then, the transmitting unit transmits the emergency key ID to portable terminal 300. On the other hand, when the state acquisition unit does not receive the unlock information request signal from the mobile terminal 300, the determination unit excludes the mobile terminal 300 from the target for transmitting the emergency key ID.

  In addition, if the registrant determines that unlocking of the disaster prevention storage warehouse is unnecessary because the scale of damage is relatively small, the registrant may give an instruction to the portable terminal that it cannot respond. As a result, the unlock information request signal is not transmitted to the server device 100 from the portable terminal. The server device 100 does not transmit the emergency key ID to a mobile terminal that does not receive the unlock information request signal. Then, when the unlock information request signal is not received from any of the mobile terminals, the server device 100 does not transmit the emergency key ID to any of the mobile terminals. Therefore, when all the registrants determine that the unlocking is unnecessary, the server device 100 can avoid unnecessary transmission processing of the emergency key ID.

  In the present embodiment, when receiving the unlock information request signal from a plurality of mobile terminals, the server device 100 transmits the emergency key ID to the mobile terminal that has transmitted the unlock information request signal. However, when the server device 100 receives the unlock information request signal from a plurality of mobile terminals, the server device 100 may transmit the emergency key ID to the mobile terminal closest to the target disaster prevention storage warehouse. In this case, the server device 100 acquires the terminal position information of each of the mobile terminals that have transmitted the unlock information request signal. Then, the server device 100 specifies the mobile terminal closest to the target disaster prevention storage warehouse from among the mobile terminals transmitting the unlock information request signal by using the same method as in the first embodiment, The emergency key ID may be transmitted.

  After acquiring the terminal position information from all the mobile terminals associated with the target disaster prevention storage warehouse, the server device 100 may inquire the mobile terminals in the order of the proximity to the target disaster prevention storage warehouse. Then, when the unlock information request signal is received from the inquired mobile terminal, the server device 100 may transmit the emergency key ID to the mobile terminal.

  FIG. 9 is a flowchart illustrating the operation of the electronic lock management system according to the second embodiment. Note that a description of a process that is the same as the flow according to the first embodiment described with reference to FIG. 7 will be omitted.

  The processing up to step S104 is the same as the processing of the electronic lock management system 10 according to the first embodiment described with reference to FIG. If the server device 100 determines that the management area registered in step S104 is included in the recognized disaster prediction area (YES in step S104), all mobile phones associated with the damage prediction management area are determined. An inquiry is made to the terminal as to whether or not the emergency storage warehouse can be unlocked (step S405). In the present embodiment, the server device 100 transmits a supportability confirmation signal to the mobile terminal.

  Upon receiving the supportability confirmation signal from server device 100, portable terminal 300 causes display unit 306 to display an operation screen for controlling the supportability notification program, as described with reference to FIG. Then, the mobile terminal 300 determines whether or not the instruction from the registrant is an available instruction (step S501).

  If it is determined that the instruction from the registrant is an available instruction (YES in step S501), portable terminal 300 requests unlock information from server device 100 (step S502). The terminal 300 transmits an unlock information request signal to the server device 100. On the other hand, if it is determined that the instruction from the registrant is not an available instruction (NO in step S501), portable terminal 300 continues to wait for an availability confirmation signal.

  In step S406, server device 100 determines whether or not there is a response from the mobile terminal that has transmitted the supportability confirmation signal (step S406). If it is determined that a response has been received from the mobile terminal that has transmitted the supportability confirmation signal (YES in step S406), server device 100 specifies the mobile terminal that is the source of the unlock information request signal (step S408). . Then, server device 100 determines the specified portable terminal as a target to which the emergency key ID is transmitted. The server device 100 transmits the emergency key ID to the portable terminal determined to be transmitted in step S408.

  On the other hand, when it is determined that there is no response from the mobile terminal that has transmitted the supportability confirmation signal (NO in step S406), server device 100 continues to wait for the reception of disaster information. In this case, the server device 100 does not transmit the emergency key ID to any mobile terminal.

  The mobile terminal 300 receives the emergency key ID from the server device 100 (Step S503). Next, the mobile terminal 300 moves to step S204 and executes the subsequent processing.

  As described above, in the present embodiment, the registrant notifies the server apparatus 100 that the unlocking operation of the target disaster prevention storage warehouse is possible by transmitting the unlocking information request signal. Thereby, the server device 100 can specify the registrant who has not been injured or has been relatively injured by the disaster that has occurred, and efficiently specifies the portable terminal to which the emergency key ID is to be transmitted. be able to.

  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, when the server device 100 acquires an emergency signal such as an emergency earthquake bulletin transmitted from an administrative agency or a disaster occurrence notification signal from the administrator terminal 200, the server device 100 The description has been made using the example in which the unlock information is transmitted to the mobile terminal 300. 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 any registrant. 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. Note that, even when the server device 100 acquires the emergency signal, the server device 100 transmits a signal notifying the acquisition of the emergency signal to the administrator terminal 200, and prompts the administrator to transmit the disaster occurrence notification signal. Good. In this case, the disaster occurrence notification signal has a meaning as an approval signal approved by the administrator for transmitting the unlock information to the portable terminal 300 of any of the registrants. When receiving the approval signal, server device 100 transmits the unlock information to mobile terminal 300. On the other hand, when the server device 100 does not receive the approval signal, the server device 100 may not transmit the unlock information to the mobile terminal 300. Further, the approval signal may include information on whether or not to approve the transmission of the unlock information. The server device 100 may determine whether or not to transmit the unlock information to the mobile terminal 300 based on whether or not to approve the transmission of the unlock information included in the approval signal.

  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 embodiment has been described in which the server device 100 transmits the unlock information for unlocking the electronic lock of the target emergency storage warehouse to the registrant's mobile terminal. The server device 100 may further transmit locking information for locking the electronic lock to the mobile terminal. Thereby, the registrant can lock the unlocked emergency storage warehouse using the mobile terminal that has received the locking information, thereby preventing intrusion of a third party or the like. In addition, the server device 100 may transmit the lock information to a mobile terminal other than the mobile terminal that has transmitted the unlock information. For example, the server device 100 may transmit the locking information to the mobile terminals of all registrants associated with the target disaster prevention storage warehouse. This allows all registrants to lock the disaster prevention storage warehouse, thereby increasing the certainty that the disaster prevention storage warehouse is locked to prevent intrusion of a third party or the like.

  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, the method of changing the emergency key ID and the emergency authentication data is not limited to this example. For example, 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 determines the emergency key ID from the generation time (year / month / day / minute / second) using the program. 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 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, the disaster prevention storage warehouse has been described as an example of the managed property. However, various buildings related to disasters can be managed. For example, the managed property may be a gymnasium of a school serving as an evacuation site, or a gate of an evacuation route going up to a hill where entry is prohibited in normal times. Then, the server device 100 may change the unlock information transmitted to the registrant associated with each managed property according to the characteristics of the managed property. For example, in the case where the managed property is a disaster prevention storage warehouse, it is preferable that the property is locked in order to prevent a third party from intruding except when taking out supplies in an emergency. On the other hand, in the case of evacuation facilities and gates on evacuation routes, it is preferable that evacuees can enter or pass at any time in an emergency. 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 to the target portable terminal. 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, 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, a non-contact type electronic lock device has been described as an example of the electronic lock device 400. However, the electronic lock device 400 may be, for example, a contact-type electronic lock device in which authentication data is directly input using a numeric keypad. In this case, the server device 100 transmits the information of the authentication data to be input to the numeric keypad to the portable terminal of the target registrant instead of the emergency key ID.

  In the above description, the case where the lock installed in the management target is an electronic lock has been described, but the lock is not limited to the electronic lock. For example, it may be a lock or a safe that is unlocked using a physical key. In the case of a lock that is unlocked using a physical key, the server device 100 transmits, as unlocking information related to unlocking, information on a management location of a key for unlocking the lock to the mobile terminal. You may. In the case of a safe lock, the server device 100 may transmit, to the portable terminal, information on an operation procedure for unlocking the safe lock as unlock information regarding unlocking.

  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, 206a Management area display, 206b radio button, 206c transmission button, 208 operation unit, 300 portable terminal, 302 control unit, 303 memory, 304 network connection unit, 305 communication unit, 306 display unit, 306a, 306b selection button, 308 operation unit, 400 electronic lock device, 402 control unit, 403 storage unit, 404 communication unit, 406 drive unit, 408 lock unit, A1, B1, C1 disaster prevention storage warehouse

Claims (5)

A registration unit in which one or more mobile terminals associated with an electronic lock installed in a specific area are registered;
An information acquisition unit for acquiring disaster information relating to the disaster,
When the information acquisition unit acquires the disaster information, at least one of the portable terminals registered in the registration unit transmits an inquiry about whether the electronic lock can be unlocked, and transmits the electronic lock. A transmitting unit for transmitting unlock information for unlocking,
A state acquisition unit that acquires a state as to whether the mobile terminal has transmitted a request signal requesting the unlock information in response to the inquiry transmitted by the transmission unit,
An electronic lock management device comprising: a determination unit that determines a mobile terminal that has acquired the state in which the state acquisition unit is transmitting the request signal as a portable terminal that transmits the unlock information from the transmission unit.   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. The state obtaining unit further obtains location information on a location of the mobile terminal,
The determination unit, of the mobile terminals that have acquired the state in which the state acquisition unit is transmitting the request signal, comparing the location information acquired by the state acquisition unit and the installation position of the electronic lock, The electronic lock management device according to any one of claims 1 to 3, wherein it is determined whether to transmit the unlock information to the mobile terminal. A registration step of registering one or more mobile terminals associated with an electronic lock installed in a specific area;
An information acquisition step of acquiring disaster information relating to the disaster,
An inquiry step of, when acquiring the disaster information, transmitting, to at least one of the mobile terminals registered in the registration step, an inquiry as to whether or not the electronic lock can be unlocked;
A state acquisition step of acquiring a state as to whether or not the portable terminal has transmitted a request signal requesting unlock information for unlocking the electronic lock in response to the inquiry,
A determination step of determining the mobile terminal that has acquired the state transmitting the request signal in the state acquisition step as a mobile terminal that transmits the unlock information,
An electronic lock management program for causing an electronic lock management device to execute a transmission step of transmitting the unlock information to the portable terminal determined in the determination step.

Images