Key management system

Abstract

It makes it easy to identify who took the keys, and even when multiple keys are being searched, the person who took them can be identified smoothly. [Solution] An RFID tag 12 is attached to the key 11, and an RFID reader 23a is installed in the key storage section 21 of the key management box 2. A face information input device 6 is provided to input a face image in order to enable the removal of the key 11 from the key management box 2. A face authentication server 4 has the face image information of the authorized person that has been input and determines whether the face image input from the face information input device 6 is that of the authorized person. A key management server 5 manages the removal / return of the key based on the reading information from the RFID reader 23a. The key management server 5 has a history storage unit 53 that stores the history of key removals of the key 11, and a display unit 51 that displays the status of the managed key 11. After a predetermined display operation, the display unit 51 displays a list of information on the persons who have removed the key 11 that has not been returned.

Description

Technical Field

[0001] The present invention relates to a key management system that can collectively manage various keys at a construction site or the like.

Background Art

[0002] When collectively managing keys at a construction site or the like, the keys to be managed change according to the progress of the construction work, and the key handlers also change. Conventionally, a dedicated record note was created to record the name of the key borrower, the number of the key to be taken out, etc. By doing so, it was possible to handle problems such as loss. On the other hand, in offices and financial institutions, it is easy to manage keys, and since it is necessary to restrict the use of keys, when taking out a key from a dedicated storage unit, the information on the user's ID card is read to determine whether the person is authorized, and a management method that grasps key users and leaves a history has become widespread. For example, in Patent Document 1, keys were managed by attaching wireless tags to individual keys, and a card reader for limiting handlers was arranged in a key management machine that collectively stores keys, thereby managing borrowers, borrowing dates and times, borrowed keys, etc.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technology of the above Patent Document 1 could manage the key borrower together with the key information. However, when it was desired to grasp the status of keys that had been taken out from the key management machine and not returned, the operation of grasping the borrower or the like could not be performed smoothly. For example, it was possible to track the history by operating the control panel, but the operation involved touching the display, so it wasn't a simple operation. Also, the information that could be obtained was limited to the time of removal and the name of the person who removed it, and in places like construction sites where the person who removed the key was likely to change, the name alone was not enough to identify the person. Therefore, considering its use on construction sites and similar locations, it wasn't particularly convenient. Especially when needing to check the status of multiple keys, it required repeating the same operation for each key, which was cumbersome and time-consuming.

[0005] Therefore, in view of these problems, the present invention aims to provide a key management system that makes it easy to identify who has taken a key, and that allows for smooth identification of the person who has taken a key even when multiple keys are being searched. [Means for solving the problem]

[0006] To solve the above problems, the first configuration of the present invention is a key management system having a key storage unit that houses a plurality of keys, attaching RFID tags to the keys and providing an RFID reader in the key storage unit, and managing the keys stored in the key storage unit based on the reading information of the RFID reader, comprising: at least one key management box having a key storage unit; face information input means for inputting a face image to enable the removal of keys from the key management box; face information storage unit that registers the face image of an authorized person who has been given the authority to remove the keys, and face authentication means that determines whether the face image input from the face information input means is that of an authorized person registered in the face information storage unit; and key management means that manages the removal / return of keys based on the reading information of the RFID reader, wherein the key management means comprises a history storage unit that stores the history of keys being removed, a display unit that displays the status of the keys to be managed, and a display control unit that, upon receiving a predetermined display operation, displays a list of information on the persons who have removed keys that have not been returned to the key storage unit on the display unit based on the information in the history storage unit and the face image registered in the face authentication means or the face image of an authorized person input from the face information input means. This configuration displays a list of information about the person who took each key that is currently out, making it easy to identify who took each key, even when multiple keys are being searched.

[0007] Another aspect of the present invention is characterized in that, in the above configuration, the list of key takers displayed on the display unit includes information other than faces along with information on returned keys, and when a part of a key that has not been returned is selected in the list display by touch operation or mouse operation, information including the face image of the person who took the selected key is displayed in a pop-up. With this configuration, even if information on keys without the taker's face image is displayed in a list, selecting the display area of ​​a key that has not been returned will cause the taker's face image for that key to pop up, allowing it to be displayed in an easily viewable size and making it easier to identify the person.

[0008] Another aspect of the present invention is characterized in that, in the above configuration, there are multiple key management boxes, while the facial information input means is provided in a specific key management box, the key management boxes communicate with each other via a dedicated cable or a public communication network, and when facial recognition is performed by the facial information input means, it is possible to unlock the key management box that does not have the facial information input means. With this configuration, even if multiple key management boxes are provided, only one device is needed for facial information input.

[0009] Another aspect of the present invention is characterized in that, in the above configuration, the key management box, the facial recognition means, and the key management means communicate with each other via a public communication network, the facial information input means is a mobile terminal, and the key management means has an application to make the mobile terminal function as a facial information input means, while the key management box has a portion displaying a two-dimensional code for making the mobile terminal communicate with the key management means and install the application, and the mobile terminal functions as a facial information input means when it reads the two-dimensional code. With this configuration, for example, a smartphone can be used as a means of inputting facial information, eliminating the need to install a dedicated facial information input device. Furthermore, an application is an abbreviation of application software and is dedicated software.

Advantages of the Invention

[0010] According to the present invention, since the information of the person who has taken out the currently taken-out key is displayed in a list, even if a plurality of keys are the search targets, the person who has taken them out can be smoothly grasped.

Brief Explanation of Drawings

[0011] [Figure 1] It is a configuration diagram showing an example of a key management system according to the present invention. [Figure 2] It is an explanatory diagram of a key. [Figure 3] It is an explanatory diagram of a parent box which is a key management box. (a) is a partial explanatory diagram of a key storage part, and (b) is a perspective view of the parent box with the door removed. [Figure 4] It is a block diagram of the parent box. [Figure 5] It is a block diagram of a face information input device. [Figure 6] It is a block diagram of a face registration server. [Figure 7] It is a block diagram of a face authentication server. [Figure 8] It is a block diagram of a key management server. [Figure 9] It is a flowchart showing the flow of key management by face authentication. [Figure 10] It is an explanatory diagram showing a list of key states. [Figure 11] It is a configuration diagram showing another form of the key management system. [Figure 12] It is a screen explanatory diagram for acquiring information on keys taken out by a mobile terminal.

Modes for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a configuration diagram showing an example of a key management system according to the present invention. The key management system 1 includes two key management boxes 2 (parent box 2a and child box 2b) for housing keys, a face registration server 3, a face authentication server (face authentication means) 4, and a key management server (key management means) 5. Note that 6 is a face information input device (face information input means), and 7 is an administrator's terminal.

[0013] The key management box 2 has a lockable key storage section and can accommodate a plurality of keys. The face information input device 6 is provided in one of the two key management boxes 2, i.e., the parent box 2a, and the other key management box 2, the child box 2b, has only a key storage section. By operating the face information input device 6 attached to the parent box 2a, the child box 2b can also be locked and unlocked. Thus, even if there are a plurality of key management boxes 2, the face information input device 6 is configured to be sufficient with one unit.

[0014] Each device communicates with each other via a public communication network N such as the Internet. However, the communication between the parent box 2a and the child box 2b may be performed via a dedicated cable. Note that the number of keys managed by the child box 2b can be increased or decreased, and the key management box 2 may have only one parent box 2a or may have a plurality of child boxes 2b.

[0015] FIG. 2 is an explanatory diagram of a key, and FIG. 3 is an explanatory diagram of the parent box 2a. FIG. 3(a) is a partial explanatory diagram of the key storage section, and FIG. 3(b) is a perspective view of the parent box 2a with the door removed. As shown in FIG. 2, a key holder 12a incorporating an RFID tag 12 is attached to the key 11. FIG. 3 shows the parent box 2a with the door removed to expose the key storage section 21. The key storage section 21 is provided with a plurality of tag insertion sections 22. By inserting the key holder 12a into the tag insertion section 22, the key 11 is held and stored in the key storage section 21. Inside the tag insertion section 22, an RFID reader 23a (shown in Figure 4) is individually arranged to read the information of the RFID tag 12 attached to the inserted key holder 12a. The key storage section 21 is constructed by arranging multiple key holding blocks B, each formed by arranging multiple tag insertion sections 22 in a horizontal direction, vertically. Furthermore, child box 2b has the same configuration as parent box 2a, except that it lacks the facial information input device 6.

[0016] Figure 4 shows a block diagram of the parent box 2a. As shown in Figure 4, each key holding block B is equipped with a tag information acquisition unit 24 that transmits the RFID information read by the RFID reader 23a to the box control unit 27. The parent box 2a is also equipped with a lock control unit 26 that operates the electronic lock 25 of the door, a box control unit 27 that controls the parent box 2a, a communication unit 28 that communicates with other devices via the public communication network N, an RFID storage unit 29 that stores the association between the RFID tag 12 and the tag insertion unit 22, a face information input device 6, and the like.

[0017] The box control unit 27 communicates with the key management server 5 based on the information read by the tag information acquisition unit 24 and notifies the key management server 5 of the presence or absence of each key 11 under its management. Furthermore, the box control unit 27 recognizes that the key 11 has been removed when the RFID reader 23a can no longer read the RFID tag 12, and recognizes the return of the key 11 when the previously unreadable RFID tag 12 becomes readable again.

[0018] Figure 5 is a block diagram of the facial information input device 6. The facial information input device 6 is a device for authorizing the removal of the key 11, and includes a camera 61, a display unit 62, an operation unit 63, a facial information input device control unit 64, a communication unit 65 that communicates with other devices via the public communication network N, etc. The operation unit 63 of the face information input device 6 is a touch panel and is integrated with the display unit 62. It is activated from standby mode by touch operation on the display unit 62, and the camera 61 is activated. When the camera 61 is activated, a message such as "Please hold your face in front of the camera 61" is displayed, the camera 61 takes an image of the face held up, and the captured image is sent to the face recognition server 4 to determine whether or not the person is registered.

[0019] As shown in the block diagram of the parent box 2a in Figure 4 and the block diagram of the facial information input device 6 in Figure 5, the facial information input device 6 has no components in common with the parent box 2a and is configured to be detachable from the parent box 2a. Therefore, the facial information input device 6 can be installed independently. By making it detachable, it can be removed and stored separately on holidays or at night when the administrator is absent to prevent theft, etc.

[0020] Furthermore, the facial information input device 6 may be configured as an integral part of the main box 2a. In that case, the communication unit 65 of the facial recognition input device 6, as well as a power supply unit (not shown), etc., can be integrated with the communication unit 28, power supply unit, etc., of the main box 2a.

[0021] Figure 6 is a block diagram of the face registration server 3. The face registration server 3 is a device that registers persons (authorized persons) who are granted permission to take out the key 11, and includes a camera 31, a display unit 32, an operation unit 33, a face registration server control unit 34, a storage unit 35 for storing captured images, etc., and a communication unit 36 ​​for communicating with other devices via the public communication network N. The face registration server 3 captures and registers the face of the person to whom the key 11 is to be authorized to be taken out. This face information is linked with other information such as the name information that was also entered and registered in the storage unit 35. The registered information is also transmitted to the face recognition server 4 and registered in the face recognition server 4 as well.

[0022] Furthermore, if the face registration server 3 is not located at the construction site where the key management box 2 is located, or if multiple face recognition servers 3 are operated due to various conditions, a user terminal (not shown) consisting of a personal computer or the like can be installed at an appropriate location and connected to the face registration server 3 via the public communication network N, thereby enabling smooth face image registration regardless of the location of the face registration server 3.

[0023] Figure 7 is a block diagram of the face recognition server 4. As shown in Figure 7, the face recognition server 4 includes a person information storage unit 41 having a face information storage unit 41a, a face determination unit 42, an event history storage unit 43 that records the history of key removal, etc., a face recognition server control unit, a communication unit 45, etc. The face information storage unit 41a of the person information storage unit 41 stores and saves face image information transmitted from the face registration server 3. The face determination unit 42 compares and determines the registered face image with the face information transmitted from the face information input device 6. The event history storage unit 43 stores information about the person who took out the key 11 and the key 11 that was taken out, and saves this information along with information on whether or not it was returned.

[0024] Figure 8 is a block diagram of the key management server 5. The key management server 5 includes a display unit 51 that displays the status of keys 11 and various information related to keys 11, an operation unit 52 that operates the display, a history storage unit 53 that stores the history of each key 11, a person authority storage unit 54 that stores information limiting which key management boxes 2 can be unlocked by each authorized person, a key list storage unit 55 that stores the current status of keys 11, a key management server control unit 56 that controls the key management server 5, and a communication unit 57 that performs communication via the public communication network N. The information stored in the key list storage unit 55 is rewritten in conjunction with the update of the history information storage unit 53 under the control of the key management server control unit 56.

[0025] The key management server 5 issues an event ID authorizing unlocking if the person authenticated by the facial recognition server 4 is authorized to unlock any of the key management boxes 2. Furthermore, when information about the removed key 11 is transmitted from the key management box 2, it is recorded in the history storage unit 53 along with the information of the person who removed it. The history storage unit 53 stores the issued event ID information, command information (date and time information for removal / return and associated facial image information), and other details described later.

[0026] The administrator terminal 7, for example, is a personal computer and displays current information about the key 11 stored in the key management server 5, information about the person who took the key, and event history such as the history of key 11 being taken out.

[0027] The operation of the key management system configured as described above is as follows. First, it is assumed that the person who has been granted permission to take out key 11 (authorizer) is registered, including their facial information. Figure 9 is a flowchart illustrating the key management process. Referring to Figure 9, we will explain the process of key 11 being taken out of the key management box and then returned. The person taking out (or returning) the key 11 first activates the facial information input device 6 and holds their face up to the camera 61 that has started capturing images (S1). The camera 61 captures the face held up to it, and the acquired facial image data is sent to the facial recognition server 4, where authentication processing is performed (S2).

[0028] The authentication process involves comparing the face information registered in the face recognition server 4. If the registered face image matches the face captured by the camera 61, authentication is performed (YES in S3), and an authentication signal is sent to the face information input device 6. The facial information input device 6, having received the authentication signal, then queries the key management server 5 for permission to confirm (S5). The key management server 5 determines from the registration information in the person permission storage unit 54 whether the key management box 2 that the authenticated person can unlock is limited, and generates an event ID, which is an unlock permission signal according to the registration information, and sends it back to the facial information input device 6. Upon receiving the event ID, the facial information input device 6 sends an unlock signal to the key management box 2 (S8). The key management server 5 that issued the event ID records the event ID (S9).

[0029] Meanwhile, the key management box 2, upon receiving the unlock signal, controls the unlocking of the electronic lock 25 on the door (S10). However, if the registered authorization information of the authenticated person indicates that only a specific key management box 2 is authorized, then only that key management box 2 will be unlocked. Once unlocked, unlocking information is sent to the key management server 5 (S11), associated with an event ID, and recorded as history.

[0030] Furthermore, in S3, if no face matches the registered facial image, no unlocking instruction is issued, and the facial information input device 6 displays that the face is not registered (S4). Also, even if facial recognition is performed, if the person does not have the authority to take out the key 11, "No Authority" is displayed on the facial information input device 6 (S7).

[0031] In this way, key 11 can be retrieved using facial recognition, and once key 11 is retrieved, the facial image of the person who retrieved it and information about the retrieved key 11 are recorded in the key management server 5. Similarly, when the key is returned, information such as the facial image of the person returning it and information about the returned key 11 are also recorded.

[0032] The key management box 2 will begin the door locking operation (S14) after a certain period of time, such as 30 seconds, has elapsed since the door was unlocked. Before locking, the box control unit 27 of the key management box 2 determines whether the key 11 has been taken out or returned (S12). Takeout or return is determined by the information read by the tag information acquisition unit 24 provided in each key storage unit 21. If reading becomes impossible, it is determined that the key has been taken out, and if reading becomes possible, it is determined that the key has been returned. The retrieved / returned information detected in this way is used to generate a command that associates the key number information, time information, and facial image information of the retriever, which is then sent to the key management server 5 (S13) and recorded. After a certain period of time has elapsed since unlocking, the door of key management box 2 is locked (S14), and the locking information is transmitted to and recorded by key management server 5 (S15).

[0033] In this way, the information on the removal / return of key 11 is stored as a history along with the facial image information of the person who removed it. Therefore, it is easy to identify who took out key 11 that has not been returned, and it is also easy to identify the person who last used key 11.

[0034] Next, we will explain how to display the current status of the keys 11 stored in the key management box 2. In addition to the administrator terminal 7, the facial information input device 6 and the key management server 5 can display the list information stored in the key list storage unit 55 of the key management server 5. Each device, including the administrator terminal 7, has a display unit equipped with a touch panel, and is configured to allow various operations to be performed using touch and mouse operations. These devices allow users to see at a glance which keys have been taken out and not yet returned by displaying the list information stored in the key list storage unit 55.

[0035] Figure 10 is an explanatory diagram showing a list view. By performing a predetermined display operation on the device you wish to display, a list view M of the current status of the keys 11 stored in the key list storage unit 55 of the key management server 5 will be displayed as shown. In this list display, the display mode that primarily shows text information is the display unit M1 for keys 11 that have not been returned, and the display mode that shows an illustration of key 11 is the display unit M2 for keys 11 that have been returned. This display allows for quick identification of returned keys 11 and keys 11 that have not been returned. In addition, the time when the key 11 was last retrieved and the name of the person who retrieved it are displayed.

[0036] By touching or using a mouse on the display area of ​​any of the keys 11 that have not been returned, details including the registered face image G of the person who took the key and the date and time of taking the key will be displayed in a large pop-up window as shown in M3. Furthermore, the face image G to be displayed does not have to be a registered image; it may also be the most recent image captured by the face information input device 6.

[0037] In this way, even though the current status of key 11 is displayed in a list, the facial image G of the person who took the key 11 that has not been returned is displayed in a pop-up, making it easy to identify the person and understand their identity.

[0038] Figure 11 is a configuration diagram showing another form of the key management system 1, in which the facial information input device 6 is configured completely independently. The facial information input device 6 may be a dedicated terminal, but it can also be used as a facial information input device 6 by installing a predetermined application (hereinafter simply referred to as "app") on a mobile terminal 9 such as a tablet or smartphone. In this case, all of the multiple key management boxes 2 become the child boxes 2b described above. The app to be installed is stored, for example, on the key management server 5.

[0039] A QR code (registered trademark) 8, which is a two-dimensional code for installing a specific application on a mobile device 9, is displayed in an easily recognizable location on the front of the key management box 2. By scanning this QR code (registered trademark) 8 with the camera of the mobile device 9, communication is established between the key management server 5 and the mobile device 9. Through this communication, the application held by the key management server 5 is sent to the mobile device 9 and installed. By installing the app, the mobile device 9 functions as a facial information input device 6, and the captured facial image is sent to the facial recognition server 4 to determine if the person is authorized to take the device out. Once authenticated as the person authorized to take the device out, the key 11 can then be retrieved / returned according to the flowchart above.

[0040] Furthermore, by performing a predetermined operation on the mobile device 9, it is possible to display a list as shown in Figure 10 above, or to display only the status of a specific key 11 that has not been returned. If the mobile device 9 is a smartphone, the display area is small, making it easier to recognize and convenient to display only the status of a specific key.

[0041] Figure 12 shows the screen display when the mobile device 9 is a smartphone, and is an explanatory diagram showing a screen for searching for the person who took the key 11 that has not been returned on the display unit 91 of the smartphone, which is the mobile device 9. After installing the application based on QR code (registered trademark), the screen shown in Figure 12 will be displayed after performing the prescribed operation. As shown in this screen display, the key box number (key management box number) input section 92 and the key slot number (tag insertion section number) input section 93 are displayed. By entering the number of the key 11 you want to check, an image similar to the pop-up display shown in Figure 10 above will be displayed, along with the information of the person who took the item, accompanied by a facial image G.

[0042] In this way, for example, a smartphone can be used as a means of inputting facial information, eliminating the need to install a dedicated facial information input device.

[0043] In the above embodiment, the current status of the keys 11 is displayed in a list regardless of whether they have been returned or not. However, it is also possible to display only the keys 11 that have not been returned, and this can be easily implemented. [Explanation of Symbols]

[0044] 1. Key management system, 2. Key management box, 3. Face registration server, 4. Face authentication server (face authentication means), 5. Key management server (key management means), 6. Face information input device (face information input means), 8. 2D code, 9. Mobile terminal, 11. Key, 12. RFID tag, 21. Key storage unit, 22. Tag insertion unit, 23a. RFID reader, 24. Tag information acquisition unit, 29. RFID storage unit, 42. Face determination unit, 51. Display unit, 53. History storage unit, 55. Key list storage unit, 56. Key management server control unit (display control unit), 61. Camera, G. Face image, N. Public communication network, M. List display, M1. Display of keys that have not been returned, M3. Pop-up display of face image.

Claims

1. A key management system having a key storage section for storing multiple keys, attaching RFID tags to the keys, and providing an RFID reader in the key storage section, and managing the keys stored in the key storage section based on the reading information from the RFID reader, A key management box having the aforementioned key storage section, A facial information input means for inputting a facial image in order to enable the retrieval of the key from the aforementioned key management box, It has a facial information storage unit that stores the facial image of the authorized person who has been given the authority to take out the key, and a facial authentication means that determines whether the facial image input from the facial information input means is that of the authorized person registered in the facial information storage unit, The system includes a key management means that manages the retrieval / return of keys based on the reading information from the RFID reader, The aforementioned key management means includes a history storage unit that stores the history of key removals, A display unit that shows the status of the keys being managed, A key management system characterized by having a display control unit that, upon receiving a predetermined display operation, displays a list of information on the person who took a key that has not been returned to the key storage unit on the display unit, based on the information in the history storage unit and the face image registered in the face recognition means or the face image of the authorized person input from the face information input means.

2. The display unit shows a list of key holders, including information about returned keys, as well as information other than faces. The key management system according to claim 1, characterized in that when a part of a key that has not been returned is selected in the list display using touch or mouse operation, information including the facial image of the person who took the selected key is displayed in a pop-up window.

3. While the system is equipped with multiple key management boxes, the facial information input means is provided in a specific key management box. The aforementioned key management boxes communicate with each other via a dedicated cable or a public communication network. The key management system according to claim 2, characterized in that when facial recognition is performed by the facial information input means, it becomes possible to unlock a key management box that does not have a facial information input means.

4. The key management box, the facial recognition means, and the key management means communicate with each other via a public communication network. The facial information input means is a mobile terminal, and the key management means has an application to cause the mobile terminal to function as the facial information input means, The key management box has a section displaying a two-dimensional code for communicating the mobile terminal with the key management means to install the application, The key management system according to claim 1 or 2, characterized in that the mobile terminal functions as a facial information input means when it reads the two-dimensional code.

Images