Key management device, key management system, and key management method

Abstract

To enable more holders than the number of holders that can be stored in a storage part of a key management device to be managed by the key management device.SOLUTION: The key management device comprises: a plurality of storage parts, each of which can store the holder holding a key; a registration part that registers the holder to be managed by the own device; and a setting part that sets storage target information indicating at least either of the following with respect to the holder to be managed registered by the registration part: the holder is a first holder to be stored by the storage part, or the holder is a second holder which is not stored by the storage part.SELECTED DRAWING: Figure 4

Description

Technical Field

[0005] ,

[0001] The present invention relates to a key management device, a key management system, and a key management method.

Background Art

[0002] Patent Document 1 describes a key management machine including a key management unit for managing keys, having identification information, a key holder linked to the key, an acquisition unit for acquiring the identification information of the key holder, and a registration unit for registering the key holder having the identification information acquired by the acquisition unit as a key holder to be managed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a desire to make more holders than those that can be stored in the storage unit of the key management device subject to management by the key management device. An object of the present invention is to make more holders than those that can be stored in the storage unit of the key management device subject to management by the key management device.

Means for Solving the Problems

[0005] To achieve such an object, the present invention provides a key management device including a plurality of storage units each capable of storing a holder holding a key, an acquisition unit for acquiring identification information of the holder, and a registration unit for registering the identification information acquired by the acquisition unit as identification information of a holder to be managed by the self-device, and the registration unit can register a number of holders greater than the number of storage units as holders to be managed. The key management device may include a setting unit that sets storage target information indicating that a holder is a first holder to be stored by a storage unit for a holder to be managed that has been registered by a registration unit. In this case, the setting unit may be able to set storage target information indicating that a holder is a first holder for a first number of holders, which is less than or equal to the number of storage units, among the holders to be managed that have been registered by the registration unit. In this case, the device may also include a communication unit that communicates with other devices, the communication unit transmits the first number to the other devices, and the setting unit sets storage target information indicating that a holder is a first holder for the first number of holders or less, based on the information received by the communication unit from the other devices. The key management device may include a setting unit that sets storage target information indicating that a holder is a second holder that is not subject to storage by the storage unit, for a holder that has been registered by the registration unit. In this case, the setting unit may be able to set storage target information indicating that a holder is a second holder for a second number of holders, which is equal to or greater than the number obtained by subtracting the number of storage units from the number of holders that have been registered by the registration unit. In such cases, the setting unit may set storage target information for the managed holders registered by the registration unit at predetermined intervals. In this case, the key management device may include a communication unit that communicates with other devices, and the setting unit may set storage target information for the managed holders registered by the registration unit at predetermined intervals based on information received by the communication unit from other devices.

[0006] Furthermore, the present invention also provides a key management system comprising: a key management device having a plurality of storage compartments, each capable of housing a key holder; an acquisition unit for acquiring identification information of holders; and a storage unit for storing information of holders managed by the key management device by storing the identification information acquired by the acquisition unit as identification information of holders managed by the key management device, wherein the storage unit is capable of storing information of a number of holders greater than the number of storage compartments as information of holders managed.

[0007] Furthermore, the present invention also provides a key management method that includes an acquisition step in which a computer acquires identification information of a holder that holds keys, and a registration step in which the computer registers the identification information acquired in the acquisition step as identification information of a holder to be managed by a key management device having a plurality of storage compartments, each capable of storing a holder, wherein in the registration step, a number of holders greater than the number of storage compartments can be registered as holders to be managed. [Effects of the Invention]

[0008] According to the present invention, more holders than can be stored in the storage compartment of the key management device can be managed by the key management device. [Brief explanation of the drawing]

[0009] [Figure 1] This shows an example of the overall configuration of a key management system in an embodiment of the present invention. [Figure 2] This figure shows an example of the external configuration of a key management device according to an embodiment of the present invention. [Figure 3] This figure shows an example of the external configuration of the holder and key used in an embodiment of the present invention. [Figure 4] This is a block diagram showing an example of the functional configuration of a key management device according to an embodiment of the present invention. [Figure 5] This figure shows an example of stored information in an embodiment of the present invention. [Figure 6] This is a block diagram showing an example of the functional configuration of a server device in an embodiment of the present invention. [Figure 7] This figure shows an example of key information in an embodiment of the present invention. [Figure 8] This figure shows an example of reservation information in an embodiment of the present invention. [Figure 9] This sequence diagram shows an example of the operation during key registration in a key management system according to an embodiment of the present invention. [Figure 10]This flowchart shows an example of the operation of a server device during key reservation in a key management system according to an embodiment of the present invention. [Figure 11] This is a sequence diagram showing an example of the operation when loading a key reserved for the next day in a key management system according to an embodiment of the present invention. [Figure 12] This is a sequence diagram showing an example of the operation when a key reserved for the same day is lent out in a key management system according to an embodiment of the present invention. [Modes for carrying out the invention]

[0010] Embodiments of the present invention will be described in detail below with reference to the attached drawings. [Overall configuration of the key management system] Figure 1 shows an example of the overall configuration of the key management system 1 in this embodiment. As shown in the figure, the key management system 1 comprises a key management device 10, a server device 40, and a terminal device 50. The key management device 10, the server device 40, and the terminal device 50 are connected via a network 80.

[0011] The key management device 10 is a device that detachably houses a holder for holding keys. This key management device 10 is operated by an administrator or a user. The administrator is the user who manages the keys and performs operations such as loading keys reserved for the next day into the key management device 10 and retrieving keys not reserved for the next day from the key management device 10. The user is the user who borrows and uses the keys and performs operations such as borrowing keys reserved for the day from the key management device 10 and returning keys to the key management device 10 after use. Server device 40 is a device that manages keys and holders. Server device 40 also accepts key reservations and manages the status of those reservations. The terminal device 50 is a terminal device used by the user, and examples include a PC (Personal Computer), a tablet device, a smartphone, etc. The user may be the key administrator or the key user. The network 80 is a communication means used for information communication among the key management device 10, the server device 40, and the terminal device 50, and for example, it is the Internet, a public line, a LAN (Local Area Network), etc.

[0012] [External configuration of the key management device] FIG. 2 is a diagram showing an example of the external configuration of the key management device 10 in the present embodiment. As shown in FIG. 2, on the front surface of the key management device 10, a first door 21 and a second door 22 are respectively provided so as to be openable and closable, and a key storage 23 opened and closed by the first door 21, and a printer 25 and a key exchange unit 26 opened and closed by the second door 22 are provided. Further, the key management device 10 has a display operation unit 27 and a card reader 28 on the front surface of the device.

[0013] The key storage 23 is provided with a plurality of storage units 24. The storage unit 24 removably stores a holder 31 that holds a key. Each storage unit 24 is provided with a locking mechanism 241 that can permit or prohibit the removal of the holder 31. The key management device 10 controls the permission or prohibition of the extraction of each holder 31 by controlling the locking mechanism 241 for each storage unit 24. In addition, each storage unit 24 is provided with a light emitting unit 242 for notifying the user of a lendable holder 31 or a holder 31 to be recovered. The light emitting unit 242 is, for example, an LED (Light Emitting Diode). Furthermore, each storage unit 24 is provided with a reading unit 243 that reads information from a wireless tag 34 (described later) of the holder 31. The reading unit 243 is provided adjacent to or inside the storage unit 24. The reading unit 243 is, for example, an RFID (Radio Frequency IDentifier) reader. In order to prevent the reading unit 243 of a certain storage unit 24 from erroneously acquiring the radio wave from the wireless tag 34 of the holder 31 inserted into the adjacent storage unit 24, a shielding plate or the like for shielding the radio wave may be provided between the storage units 24 adjacent to each other.

[0014] The printer 25 prints the history of the key management device 10, including key replacement, insertion, and removal, onto paper such as roll paper. The paper printed by the printer 25 is ejected, for example, from the front of the device. The key exchange unit 26 releases the connection between the holder 31 and the key, and can only be used by authorized personnel, such as administrators, who have the authority to exchange keys. The key exchange unit 26 has an insertion opening 261 into which the holder 31 is inserted, and a cover 262 that opens and closes the insertion opening 261. The key exchange unit 26 also has a release member that releases the lock between the holder 31 body and the ring locking body when the holder 31 is inserted to a predetermined release position in the insertion opening 261, allowing the ring 32 (described later) to be removed, and a key exchange restriction unit that allows the administrator to release the lock on the holder 31, while preventing anyone other than the administrator from releasing the lock on the holder 31. As the key exchange restriction unit, for example, a stopper mechanism that moves a stopper forward and backward in the insertion opening 261 using an electrically driven unit such as a solenoid is preferable. In this case, the key exchange restriction unit normally has the stopper advance into the insertion opening 261, restricting the holder 31 from being inserted to a predetermined release position in the insertion opening 261. On the other hand, the key exchange control unit retracts the stopper from inside the insertion opening 261 only when operated by the administrator, allowing the holder 31 to be inserted to a predetermined unlocked position in the insertion opening 261. Furthermore, the key exchange unit 26 is provided with a reading unit 263 that reads information from the wireless tag 34 of the holder 31. The reading unit 263 is located adjacent to or inside the key exchange unit 26. The reading unit 263 is, for example, an RFID reader.

[0015] The display and operation unit 27 is, for example, a touch panel display, which accepts user operations and displays various information. The card reader 28 is a reading device that reads information from a card carried by the user. Examples of cards include magnetic cards and IC (Integrated Circuit) cards. When a user passes a card through the card reader 28, the card reader 28 reads the user ID from the card and performs user authentication based on the read user ID. If, as a result of this authentication, the user is granted permission to remove the holder 31, the first door 21 of the key storage cabinet 23 is unlocked and the first door 21 can be opened, and the holder 31 corresponding to the permission can be removed.

[0016] [Holder and key configuration] Figure 3 shows an example of the external configuration of the holder 31 and key 33 used in this embodiment. As shown in Figure 3, the key 33 is connected to the holder 31 by a ring 32. The holder 31 is equipped with a wireless tag 34. The wireless tag 34 is, for example, an RFID tag. The wireless tag 34 has identification information that identifies the holder 31. To equip the holder 31 with the wireless tag 34, for example, a sticker-type wireless tag 34 may be attached to the holder 31, or the wireless tag 34 may be embedded inside the holder 31. A sticker 35 is attached to key 33. The sticker 35 has a key number written on it, for example, by the administrator, which is a number used to identify key 33.

[0017] [Background of the Embodiment] Some businesses that introduce such a key management device 10 may want to manage more keys 33 than the number of storage compartments 24 in the key management device 10. In such cases, it is common to increase the number of keys 33 that can be managed by introducing multiple key management devices 10, but this has cost disadvantages. In addition, there are space disadvantages for installing multiple key management devices 10. Furthermore, some such businesses may have a situation where, although they want to manage a large total number of keys, they do not use all of them every day, and use different keys on different days, so they can simply change the keys stored in the key management device 10 on a daily basis. Therefore, in this embodiment, it is possible to set at least one of the following for a holder managed by the key management device 10: that it should be stored in the key management device 10, or that it should not be stored in the key management device 10. This makes it possible for the key management device 10 to manage more holders than the number of storage compartments in the key management device 10.

[0018] [Key Management System Functional Configuration] Figure 4 is a block diagram showing an example of the functional configuration of the key management device 10 in this embodiment. As shown in the figure, the key management device 10 includes a control unit 11, a storage unit 12, a communication unit 13, a door locking mechanism 14, a locking mechanism 241, a light-emitting unit 242, a reading unit 243, a printer 25, a reading unit 263, a display operation unit 27, and a card reader 28. The control unit 11 is equipped with an arithmetic circuit such as a CPU (Central Processing Unit) and controls each part of the key management device 10 (communication unit 13, door locking mechanism 14, lock mechanism 241, light-emitting unit 242, reading unit 243, printer 25, reading unit 263, display operation unit 27, card reader 28, etc.) according to the operation program stored in the memory unit 12. The memory unit 12 includes ROM (Read Only Memory), RAM (Random Access Memory), etc., and stores the operation program of the control unit 11. It is also used as a work area during the control processing of the control unit 11. The operation program includes a program for the control unit 11 to execute the processes described later. The communications unit 13 communicates information with the server device 40 via a communication line. The door locking mechanism 14 is a mechanism for locking the first door 21 and the second door 22. The door locking mechanism 14 may lock and unlock the first door 21 and the second door 22 using different conditions. The locking mechanism 241, light-emitting unit 242, reading unit 243, printer 25, reading unit 263, display operation unit 27, and card reader 28 have already been explained using Figure 2, so their explanation will be omitted here.

[0019] Here, the configuration of the control unit 11 will be described in detail. The control unit 11 comprises an RFID acquisition unit 111, a key number acquisition unit 112, a user ID acquisition unit 113, a storage control unit 114, a communication control unit 115, a difference information determination unit 116, a display control unit 117, a light emission control unit 118, and a detail processing unit 119. When the reader unit 243 or reader unit 263 acquires the RFID from the wireless tag 34 of the holder 31, the RFID acquisition unit 111 acquires this RFID from the reader unit 243 or reader unit 263. In this case, information other than RFID may be used as long as it identifies the holder 31, but the following explanation will assume that RFID is used. In this embodiment, the RFID acquisition unit 111 is provided as an example of an acquisition unit that acquires the identification information of the holder. When the display operation unit 27 receives an input operation for a key number, the key number acquisition unit 112 acquires this key number from the display operation unit 27.

[0020] The user ID acquisition unit 113 acquires the user ID from the card reader 28 when the card reader 28 reads the user ID from the user's card. The user ID acquisition unit 113 may also use this user ID to perform user authentication. Alternatively, the following means of user authentication may be provided. Firstly, user authentication by reading a QR code (registered trademark) with a reader. In this case, the QR code may be provided to the user indefinitely, or it may be provided in a one-time format with a time limit. Secondly, to prevent impersonation during user authentication when receiving the key 33, biometric user authentication such as finger vein recognition or facial recognition, or user authentication by verifying identity with a driver's license, etc. The memory control unit 114 controls the writing of data to the memory unit 12 and the reading of data from the memory unit 12. Specifically, the memory control unit 114 stores storage information in the memory unit 12 indicating which holder 31 is loaded into which storage unit 24, and reads the storage information from the memory unit 12.

[0021] The communication control unit 115 receives information from the server device 40 via the communication unit 13 and transmits information to the server device 40 via the communication unit 13. Specifically, during key registration, the communication control unit 115 transmits the key number acquired by the key number acquisition unit 112 from the display operation unit 27 and the RFID acquired by the RFID acquisition unit 111 from the reading unit 263 to the server device 40. Here, the RFID acquired from the reading unit 263 is the RFID of the holder 31 whose key was exchanged by the key exchange unit 26, and is transmitted to the server device 40 as identification information for the holder 31 that holds the key 33 managed by the key management device 10. In this embodiment, the number of key number and RFID pairs transmitted to the server device 40 may be greater than the number of storage units 24. In this embodiment, this function of the communication control unit 115 is provided as an example of a registration unit that registers holders to be managed by the device. Furthermore, RFID is used as an example of identification information, and this function of the communication control unit 115 is provided as an example of a registration unit that registers the identification information acquired by the acquisition unit as the identification information of the holder to be managed. Furthermore, in this embodiment, the communication control unit 115 is provided with this function as an example of a registration unit that can register a number of holders greater than the number of storage units as the holders to be managed.

[0022] Furthermore, when a key is reserved, the communication control unit 115 transmits to the server device 40 in advance the maximum number of storage units 24 in which the key management device 10 can store the holder 31 for lending out the key 33. Here, the maximum number can be any number less than or equal to the number of storage units 24. In this embodiment, the maximum number is used as an example of a first number less than or equal to the number of storage units, the server device 40 is used as another device, and the communication control unit 115 is provided as an example of a communication unit that communicates with other devices.

[0023] Furthermore, at any time, such as when loading a key 33 reserved for the next day, when retrieving a key 33 not reserved for the next day, or when performing a review process at the end of business for a given day, the communication control unit 115 transmits the RFID acquired by the RFID acquisition unit 111 from the reading unit 243 of the storage unit 24 where the holder 31 is housed to the server device 40. The communication control unit 115 also receives information from the server device 40 regarding the difference between the RFID transmitted to the server device 40 and the RFID of the holder 31 that holds the key 33 which is managed by the server device 40 as being reserved for the next day. In the following explanation, the key 33 is reserved on a daily basis, but if it is reserved on a period of time, that period may be hours, weeks, or months. Furthermore, at any time, such as when performing a review process at the end of business on a given day, if the communication control unit 115 determines that the difference information indicates that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24, it may transmit information to, for example, the terminal device 50, indicating that the key 33 not loaded in the storage unit 24 should be loaded. In this embodiment, one day is used as an example of a predetermined period, a review process is used as an example of a predetermined process executed at each predetermined period, a certain day is used as an example of a first predetermined period, and the next day is used as an example of a second predetermined period. Furthermore, within the predetermined process executed at each predetermined period, the communication control unit 115 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between the holders stored in the storage unit during the first predetermined period and the holders that should be stored in the storage unit during the second predetermined period. On the other hand, the communication control unit 115 may, at any time such as when performing a review process at the end of business on a given day, send information to, for example, the terminal device 50 indicating that the keys 33 loaded in the storage unit 24 should be collected in addition to the keys 33 that are not reserved for the next day, if the difference information indicates that there are keys 33 that are not reserved for the next day among the keys 33 loaded in the storage unit 24. In this embodiment, one day is used as an example of a predetermined period, a review process is used as an example of a predetermined process that is executed at each predetermined period, a certain day is used as an example of a first predetermined period, and the next day is used as an example of a second predetermined period. The communication control unit 115 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between the holders stored in the storage unit during the first predetermined period and the holders that should be stored in the storage unit during the second predetermined period, within the predetermined process that is executed at each predetermined period.

[0024] Furthermore, when lending out a key 33 that has been reserved for the day, the communication control unit 115 transmits the user ID of the user who wishes to borrow the key 33, which the user ID acquisition unit 113 has obtained from the card reader 28, to the server device 40. The communication control unit 115 then receives from the server device 40 the RFID of the holder 31 that holds the key 33, which is managed by the server device 40 to be reserved by that user for the day.

[0025] The difference information determination unit 116 determines whether the difference information received by the communication control unit 115 from the server device 40 via the communication unit 13 satisfies predetermined conditions. Specifically, when loading the keys 33 reserved for the next day, the difference information determination unit 116 determines whether the difference information received by the communication control unit 115 from the server device 40 indicates that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24. Furthermore, when retrieving a key 33 that has not been reserved for the following day, the difference information determination unit 116 determines whether the difference information received by the communication control unit 115 from the server device 40 indicates that there is a key 33 among the keys 33 loaded in the storage unit 24 that has not been reserved for the following day. In the following description, the difference information determination unit 116 will perform the loading operation when a key 33 reserved for the next day is loaded, and the retrieval operation when a key 33 not reserved for the next day is retrieved. However, both operations may be performed at a predetermined timing.

[0026] The display control unit 117 controls the display of information to the display operation unit 27. Specifically, the display control unit 117 controls the display operation unit 27 to display information when a key 33 reserved for the next day is loaded at a predetermined time on a given day. At that time, if the display control unit 117 determines that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24, it controls the display operation unit 27 to display the key number of the key 33 that is not loaded in the storage unit 24. In this embodiment, a certain day is used as an example of the first predetermined period, and the next day is used as an example of the second predetermined period. The display control unit 117 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between a holder stored in the storage unit during the first predetermined period and a holder that should be stored in the storage unit during the second predetermined period following the first predetermined period, at a predetermined time within the first predetermined period. Furthermore, in this embodiment, the display control unit 117 is provided with this function as an example of a notification unit that notifies difference information, which is information indicating that none of the holders that should be stored in the storage unit during the second predetermined period are present in the holders stored in the storage unit during the first predetermined period.

[0027] Furthermore, the display control unit 117 may control the display of information to the display operation unit 27 at any time, such as when performing a review process at the end of business on a given day. In this case, if the display control unit 117 determines that the difference information indicates that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24, it controls the display operation unit 27 to display the key number of the key 33 that is not loaded in the storage unit 24. In this embodiment, one day is used as an example of a predetermined period, a review process is used as an example of a predetermined process executed at each predetermined period, a certain day is used as an example of a first predetermined period, and the next day is used as an example of a second predetermined period. The display control unit 117 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between the holders stored in the storage unit during the first predetermined period and the holders that should be stored in the storage unit during the second predetermined period, within the predetermined process executed at each predetermined period.

[0028] The light emission control unit 118 controls the light emission of the light emission unit 242 of the storage unit 24. Specifically, the light emission control unit 118 controls the illumination of the light-emitting unit 242 of the storage unit 24 when retrieving a key 33 that is not reserved for the next day at a predetermined time on a given day. At that time, if the light emission control unit 118 determines that there is a key 33 among the keys 33 loaded in the storage unit 24 that is not reserved for the next day, it controls the light-emitting unit 242 of the storage unit 24, which houses the holder 31 that holds the key 33 that is not reserved for the next day, to illuminate. In this embodiment, a certain day is used as an example of the first predetermined period, and the next day is used as an example of the second predetermined period. The light emission control unit 118 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between the holder stored in the storage unit during the first predetermined period and the holder that should be stored in the storage unit during the second predetermined period following the first predetermined period, at a predetermined time within the first predetermined period. Furthermore, in this embodiment, the light emission control unit 118 is provided with this function as an example of a notification unit that notifies difference information, which is information that any of the holders stored in the storage unit during a first predetermined period is not among the holders that should be stored in the storage unit during a second predetermined period.

[0029] Furthermore, the light emission control unit 118 may control the illumination of the light emission unit 242 of the storage unit 24 at any timing, such as when performing a review process at the end of business on a given day. In this case, if the light emission control unit 118 determines that there is a key 33 among the keys 33 loaded in the storage unit 24 that is not reserved for the next day, it controls the light emission unit 242 of the storage unit 24, which houses the holder 31 that holds the key 33 that is not reserved for the next day, to illuminate. In this embodiment, one day is used as an example of a predetermined period, a review process is used as an example of a predetermined process executed at each predetermined period, a certain day is used as an example of a first predetermined period, and the next day is used as an example of a second predetermined period. The light emission control unit 118 is provided with this function as an example of a notification unit that notifies difference information indicating the difference between the holder stored in the storage unit during the first predetermined period and the holder that should be stored in the storage unit during the second predetermined period, within the predetermined process executed at each predetermined period.

[0030] The scrutiny processing unit 119 performs scrutiny processing at the end of each business day. This scrutiny processing includes, for example, checking the usage history of the key management device 10 for the day. In this scrutiny processing, the scrutiny processing unit 119 updates the information of the holders 31 that should or should not be loaded into the storage unit 24 on a given day to the information of the holders 31 that should or should not be loaded into the storage unit 24 on the following day. In this embodiment, one day is used as an example of a predetermined period, scrutiny processing is used as an example of a predetermined process executed at each predetermined period, one day is used as an example of a first predetermined period, the following day is used as an example of a second predetermined period, and information of the holders 31 that should or should not be loaded into the storage unit 24 is used as an example of storage target information. The scrutiny processing unit 119 is provided with this function as an example of an update unit that updates the storage target information set for the first predetermined period to the storage target information set for the second predetermined period following the first predetermined period, within the predetermined process executed at each predetermined period.

[0031] Furthermore, the inspection processing unit 119 instructs the communication control unit 115 to acquire difference information between the storage unit 24 in which the holder 31 is loaded on that day and the storage unit 24 in which the holder 31 should be loaded the following day, and instructs the difference information determination unit 116 to determine the difference information. Then, if the difference information determination unit 116 determines that the difference information indicates that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24, the scrutiny processing unit 119 instructs the communication control unit 115 to transmit the information to, for example, a terminal device 50. Here, the terminal device 50 may be used by the head office administrator or by the site administrator where the key management device 10 is installed. The information to be transmitted is information indicating that it is necessary to load an additional key 33, and may include the key number of the key 33 to be loaded. If the information does not include the key number, the administrator can check the key number on the display operation unit 27 of the key management device 10. In this embodiment, the scrutiny processing unit 119 is provided as an example of an update unit that performs processing to load holders that are to be stored in the storage unit during a second predetermined period but are not included in the holders stored in the storage unit during a first predetermined period. On the other hand, if the difference information determination unit 116 determines that there is a key 33 among the keys 33 loaded in the storage unit 24 that is not reserved for the next day, the scrutiny processing unit 119 instructs the communication control unit 115 to transmit the information to, for example, a terminal device 50. Here, the terminal device 50 may be used by the head office administrator or by the site administrator where the key management device 10 is installed. The information to be transmitted is information indicating that it is necessary to retrieve an additional key 33, and may include the storage unit number of the storage unit 24 in which the key 33 to be retrieved is stored. If the information does not include the storage unit number, the administrator can check the storage unit number using the light-emitting unit 242 of the storage unit 24. In this embodiment, this function of the scrutiny processing unit 119 is provided as an example of an update unit that performs processing to retrieve holders that are stored in the storage unit during a first predetermined period but are not included in the holders that should be stored in the storage unit during a second predetermined period, within a predetermined processing.

[0032] Next, we will explain in detail the information that the memory unit 12 stores. The memory unit 12 stores the storage information 121. The storage information 121 is information for managing the RFID tags of the holders 31 stored in each storage compartment 24 of the key storage cabinet 23. The specific contents of the storage information 121 will be described later.

[0033] [Specific details of storage information] Figure 5 shows an example of storage information 121. As shown in the figure, storage information 121 associates the storage unit number with the RFID. The storage unit number is a number that identifies storage unit 24. Here, the number of storage units 24 is set to 10, and storage unit numbers from 1 to 10 are stored. The RFID is the RFID read from the holder 31 stored in the corresponding storage unit 24. The diagram shows, for example, that holder 31 with RFID "01234927" is stored in storage compartment 24 of storage compartment number "1". Note that, as an example, storage compartment 24 of storage compartment number "2" does not contain holder 31, and the RFID field for storage compartment number "2" is left blank.

[0034] [Server device functional configuration] Figure 6 is a block diagram showing an example of the functional configuration of the server device 40 in this embodiment. As shown in the figure, the server device 40 includes a control unit 41, a storage unit 42, and a communication unit 43. The control unit 41 is equipped with an arithmetic circuit such as a CPU and controls each part of the server device 40 (such as the communication unit 43) according to the operation program stored in the memory unit 42. The memory unit 42 includes ROM, RAM, etc., and stores the operation program of the control unit 41. It is also used as a work area during the control processing of the control unit 41. The operation program includes a program for the control unit 41 to execute the processing described later. The communication unit 43 communicates information with the key management device 10 and the terminal device 50 via a communication line.

[0035] Here, the configuration of the control unit 41 will be described in detail. The control unit 41 comprises a memory control unit 411, a communication control unit 412, a reservation feasibility determination unit 413, and a difference information generation unit 414. The memory control unit 411 controls the writing of data to the memory unit 42 and the reading of data from the memory unit 42. Specifically, the memory control unit 411 stores key information for managing the key 33 in the memory unit 42, and reads the key information from the memory unit 42.

[0036] Furthermore, the memory control unit 411 stores reservation information for the holder 31 that holds the key 33 in the memory unit 42, and reads the reservation information from the memory unit 42. Here, the reservation information may be information that sets a reserved key 33 for a given day. As will be described later, in the key information, the holder 31 that holds the key 33 is associated with the key 33, so the reservation information can be said to be information that sets a holder 31 that holds the reserved key 33 for a given day. In this embodiment, the holder 31 that holds the reserved key 33 is used as an example of the first holder to be stored by the storage unit, and the reservation information is used as an example of storage target information that indicates that the holder is the first holder. Furthermore, the memory control unit 411 is provided as an example of a setting unit that sets storage target information for the managed holder. In addition, in this embodiment, one day is used as an example of a predetermined period, and the memory control unit 411 is provided as an example of a setting unit that sets storage target information for the managed holder at predetermined intervals. In this case, the number of holders 31 that hold the reserved keys 33 may be less than or equal to the upper limit received from the key management device 10. In this embodiment, the upper limit is used as an example of a first number less than or equal to the number of storage units, and reservation information is used as an example of storage target information indicating that a holder is a first holder. A memory control unit 411 is provided as an example of a setting unit that can set storage target information for a first number of holders among the managed holders.

[0037] Furthermore, the reservation information may also be information that sets a key 33 that is not reserved for a given day. As will be described later, in the key information, a holder 31 that holds the key 33 is associated with the key 33, so the reservation information can be said to be information that sets a holder 31 that holds a key 33 that is not reserved for a given day. In this case, in this embodiment, a holder 31 that holds a key 33 that is not reserved is used as an example of a second holder that is not subject to storage by the storage unit, and the reservation information is used as an example of storage target information that indicates that the holder is a second holder. Furthermore, a memory control unit 411 is provided as an example of a setting unit that sets storage target information for the managed holder. Furthermore, in this embodiment, one day is used as an example of a predetermined period, and a memory control unit 411 is provided as an example of a setting unit that sets storage target information for the managed holder at predetermined intervals. In this case, the number of holders 31 that hold keys 33 that are not reserved may be greater than or equal to the number obtained by subtracting the upper limit received from the key management device 10 from the number of holders 31 under management. In this embodiment, as an example of a second number greater than or equal to the number obtained by subtracting the number of storage units from the number of holders under management, the number obtained by subtracting the upper limit received from the key management device 10 from the number of holders 31 under management is used, and reservation information is used as an example of storage target information indicating that a holder is a second holder. A memory control unit 411 is provided as an example of a setting unit that sets storage target information for the second number of holders among the holders under management.

[0038] Furthermore, the reservation information may also be information that sets reserved keys 33 and unreserved keys 33 for each day. As will be described later, in the key information, a holder 31 that holds the key 33 is associated with the key 33, so the reservation information can be said to be information that sets a holder 31 that holds the reserved key 33 and a holder 31 that holds the unreserved key 33 for each day. In this case, in this embodiment, the reservation information is used as an example of storage target information that indicates whether a holder is a first holder or a second holder. A memory control unit 411 is provided as an example of a setting unit that sets storage target information for the managed holders at predetermined intervals.

[0039] The communication control unit 412 receives information from the key management device 10 via the communication unit 43, and transmits information to the key management device 10 via the communication unit 43. Specifically, when registering a key, the communication control unit 412 receives the key number entered into the display operation unit 27 and the RFID read by the reading unit 263 of the key exchange unit 26 from the key management device 10. Furthermore, when a key is reserved, the communication control unit 412 receives in advance from the key management device 10 the maximum number of storage units 24 that can accommodate the holder 31 for lending out the key 33. Furthermore, when loading a key 33 that is reserved for the next day, or when retrieving a key 33 that is not reserved for the next day, the communication control unit 412 receives the RFID read by the reader unit 243 of the storage unit 24 in which the holder 31 is housed from the key management device 10. The communication control unit 412 then transmits to the key management device 10 the difference information between the RFID received from the key management device 10 and the RFID of the holder 31 that holds the key 33 which is managed by the server device 40 as being reserved for the next day. Furthermore, when lending out a key 33 that has been reserved for that day, the communication control unit 412 receives the user ID of the user who wishes to borrow the key 33, which has been read by the card reader 28, from the key management device 10. The communication control unit 412 then transmits the RFID of the holder 31 that holds the key 33, which is managed by the server device 40 as being reserved by that user for that day, to the key management device 10.

[0040] The reservation eligibility determination unit 413 determines whether a reservation is possible for a specified key 33 within a specified period, in response to a reservation request from a user. Specifically, the reservation eligibility determination unit 413 determines, on a daily basis within the specified period, whether the number of keys 33 already reserved is less than the upper limit received from the key management device 10. The difference information generation unit 414 generates difference information between the RFID of the holder 31 loaded in the storage unit 24 and the RFID of the holder 31 that holds the key 33 reserved for the next day.

[0041] Next, we will explain in detail the information stored in the memory unit 42. The memory unit 42 stores key information 421 and reservation information 422. Key information 421 is information that links the key number of key 33 with the RFID of a wireless tag 34 provided on the holder 31 that holds key 33. The specific contents of key information 421 will be described later. In this embodiment, key information 421 is used as an example of information about a holder managed by the key management device. Reservation information 422 indicates the reservation status of key 33 by the user. The specific contents of reservation information 422 will be described later.

[0042] Figure 7 shows an example of key information 421. As shown in the figure, key information 421 associates the key number, key name, and RFID. The key number is a number that identifies key 33. Here, the number of keys 33 to be managed is set to 30, which is more than the number of keys in the storage unit 24, which is 10, and the key numbers from 1 to 30 are stored. The key name is a name assigned to key 33 to make it easier for humans to identify. Here, the key name stores identification information of the object to be locked and unlocked with key 33. The object to be locked and unlocked is, for example, a car or a room. The RFID is the RFID of the wireless tag 34 attached to the holder 31 that holds key 33. The diagram shows, for example, that the key name of key 33 with key number "1" is "Target 1", and the RFID of the holder 31 that holds key 33 is "12345426".

[0043] Figure 8 shows an example of reservation information 422. As shown in the figure, reservation information 422 associates the date, user ID, and key number. The date is the day on which key 33 is reserved. The User ID is identification information that identifies the user who reserved key 33 on the corresponding day. The Key Number is the number of key 33 reserved by the corresponding user on the corresponding day. The diagram shows, for example, that user ID "A" reserved key 33 with key number "1" on "October 1, 2021" and "October 3, 2021". It also shows that user ID "B" reserved key 33 with key number "3" between "October 1, 2021" and "October 3, 2021".

[0044] [Key Management System Operation] Figure 9 is a sequence diagram showing an example of key registration in the key management system 1 of this embodiment. Prior to this example, the administrator must register the key number and key name in the key information 421. Then, the administrator starts this example by selecting the key registration item on the administrator menu displayed on the display operation unit 27. First, the administrator performs a key exchange at the key exchange unit 26. That is, they perform the operation of newly connecting the holder 31 and the key 33. Then, in the key management device 10, the reading unit 263 of the key exchange unit 26 reads the RFID from the holder 31, and the RFID acquisition unit 111 acquires the RFID from the reading unit 263 (step 131). Next, the administrator enters the key number of the key 33 connected to the holder 31 by the key exchange unit 26 on the administrator menu displayed on the display operation unit 27. The administrator should have previously attached a sticker with the key number written on it to the key 33, and here they should enter the key number written on that sticker. The key management device 10 then receives the key number input operation from the display operation unit 27, and the key number acquisition unit 112 acquires the key number from the display operation unit 27 (step 132). Subsequently, in the key management device 10, the communication control unit 115 controls the communication unit 13 to transmit the RFID acquired in step 131 and the key number acquired in step 132 to the server device 40 (step 133).

[0045] As a result, in the server device 40, the communication control unit 412 controls the communication unit 43 to receive the key number and RFID from the key management device 10 (step 431). Subsequently, in the server device 40, the memory control unit 411 associates the RFID with the key number received in step 431 and stores it in the key information 421 (step 432). At this time, the server device 40 generates an error if the key number is not registered in the key information 421 or if another RFID is already associated with the key number in the key information 421.

[0046] Figure 10 is a flowchart showing an example of the operation of the server device 40 in the key management system 1 of this embodiment when a key is reserved. Prior to this example of operation, the key management device 10 is assumed to have transmitted to the server device 40 the maximum number of storage units 24 that can accommodate the holder 31 for lending out the key 33. First, a user who wishes to reserve key 33 operates, for example, terminal device 50 to send a reservation request to server device 40 that includes the user's user ID, the key number of the key 33 to be reserved, and the period for which key 33 is to be reserved. Note that in the reservation request, the key 33 to be reserved may be identified by its key name instead of its key number, but in this example, the key 33 to be reserved will be identified by its key number. As a result, the communication control unit 412 in server device 40 controls the communication unit 43 to receive the reservation request including the user ID, key number, and period (step 441).

[0047] Next, in the server device 40, the reservation feasibility determination unit 413 focuses on the days within the period included in the reservation request received in step 441 (step 442). Then, the reservation feasibility determination unit 413 determines, based on the reservation information 422 stored in the storage unit 42, whether the number of user ID and key number pairs already stored for the date focused on in step 442 is less than the upper limit received from the key management device 10 (step 443). As a result, if the number of user ID and key number pairs already stored is determined to be less than the upper limit, the reservation feasibility determination unit 413 stores that a reservation is possible on the day focused on in step 442 (step 444). On the other hand, if the number of user ID and key number pairs already stored is not less than the upper limit, that is, if it is determined that the upper limit has been reached, the reservation feasibility determination unit 413 stores that a reservation is not possible on the day focused on in step 442 (step 445). Subsequently, the reservation eligibility determination unit 413 determines whether there are still days within the period included in the reservation request received in step 441 (step 446). As a result, if it determines that there are still days available within the period included in the reservation request, the reservation feasibility determination unit 413 returns the process to step 442. On the other hand, if it is determined that there are no more days within the period included in the reservation request, the reservation feasibility determination unit 413 determines whether there was at least one day for which it was recorded that a reservation was not possible (step 447).

[0048] Suppose it is determined that there is no day for which a reservation is not possible. Then, the memory control unit 411 stores the user ID and key number included in the reservation request for all days within the period included in the reservation request received in step 441 in the reservation information 422 stored in the memory unit 42 (step 448). On the other hand, suppose it is determined that there is at least one day on which it is recorded that a reservation is not possible. In that case, the communication control unit 412 controls the communication unit 43 to notify, for example, the terminal device 50 of an error that the key 33 cannot be reserved (step 449). In this case, the user will need to check the period during which the key 33 they wish to reserve is available and send a reservation request again.

[0049] Figure 11 is a sequence diagram showing an example of the operation when loading a key 33 reserved for the next day in the key management system 1 of this embodiment. Prior to this operation example, the administrator selects the item for loading the key 33 reserved for the next day on the administrator menu displayed on the display operation unit 27, retrieves the key 33 reserved for the next day from the back room, and loads it into the storage unit 24. In this case, for example, a deadline for loading the key 33 reserved for the next day may be set in advance, and if this deadline has passed, an alarm may sound to prompt the administrator to load the key 33. Once the key 33 is loaded into the storage unit 24, the key management device 10 stores the RFID of the holder 31 that holds the key 33 in the storage information 121, associating it with the storage unit number of the storage unit 24, and starts this operation example.

[0050] First, in the key management device 10, the reading units 243 of all storage units 24 in which the holder 31 is loaded read the RFID from the holder 31, and the RFID acquisition unit 111 acquires the RFID set from the reading units 243 (step 151). Next, the communication control unit 115 controls the communication unit 13 to transmit the RFID set acquired in step 151 to the server device 40 (step 152).

[0051] As a result, in the server device 40, the communication control unit 412 controls the communication unit 43 to receive the RFID set from the key management device 10 (step 451). Next, in the server device 40, the memory control unit 411 retrieves the set of key numbers stored for the following day from the reservation information 422 stored in the memory unit 42 (step 452). Then, the memory control unit 411 retrieves the set of RFIDs associated with each of these key number sets from the key information 421 stored in the memory unit 42 (step 453). Next, in the server device 40, the difference information generation unit 414 generates difference information between the set of RFIDs received in step 451 and the set of RFIDs acquired in step 452 (step 454). Subsequently, in the server device 40, the communication control unit 412 controls the communication unit 43 to transmit the difference information generated in step 453 to the key management device 10 (step 455).

[0052] As a result, in the key management device 10, the communication control unit 115 controls the communication unit 13 to receive difference information from the server device 40 (step 153). Next, in the key management device 10, the difference information determination unit 116 determines whether the difference information received in step 153 indicates that there is a key 33 among the keys reserved for the next day that is not loaded in the storage unit 24 (step 154). As a result, if the difference information indicates that there is a key 33 among the keys 33 reserved for the next day that is not loaded in the storage unit 24, the display control unit 117 displays the key number of the key 33 that is not loaded in the storage unit 24 on the display operation unit 27 (step 155). This allows the administrator to retrieve the key 33 that is reserved for the next day but not loaded in the storage unit 24 from the back room and load it into the storage unit 24. Suppose that the next day, a reserved key 33 is added to the storage unit 24. Then, in the key management device 10, the memory control unit 114 stores the RFID of the holder 31 that holds the loaded key 33 in the storage information 121, associating it with the storage unit number (step 156). On the other hand, if the difference information does not indicate that there is a key 33 among the keys reserved for the next day that is not loaded into the storage unit 24, the display control unit 117 will not display the key number on the display operation unit 27. Also, since no additional keys 33 reserved for the next day will be loaded into the storage unit 24, the memory control unit 114 will not store the RFID in the storage information 121.

[0053] Furthermore, while the above describes a check being performed to ensure that all keys 33 reserved for the next day are loaded into the storage unit 24 when the administrator retrieves the keys 33 from the back room and loads them into the storage unit 24, this is not the only option. For example, this process may be performed at any time, such as when performing the final check at the end of the workday. In that case, since the administrator may not be near the key management device 10, in step 155, the communication control unit 115 may send the key numbers of the keys 33 not loaded into the storage unit 24 to, for example, the administrator's terminal device 50.

[0054] Figure 12 is a sequence diagram showing an example of the operation when a key 33 reserved for the day is lent out in the key management system 1 of this embodiment. This example of operation starts when the user selects the item to receive the key 33 reserved for the day on the standby menu displayed on the display operation unit 27. First, when a user inserts their card into the card reader 28, the key management device 10's user ID acquisition unit 113 acquires the user ID from the card reader 28 (step 161) and performs user authentication (step 162). If user authentication is successful, the communication control unit 115 of the key management device 10 controls the communication unit 13 to send the user ID obtained in step 161 to the server device 40 (step 163).

[0055] As a result, in the server device 40, the communication control unit 412 controls the communication unit 43 to receive the user ID from the key management device 10 (step 461). Next, in the server device 40, the memory control unit 411 retrieves the key number stored in the reservation information 422 stored in the memory unit 42 for today, along with the user ID received in step 461 (step 462). Then, the memory control unit 411 retrieves the RFID associated with the key number retrieved in step 462 from the key information 421 stored in the memory unit 42 (step 463). Subsequently, in the server device 40, the communication control unit 412 controls the communication unit 43 to transmit the RFID acquired in step 463 to the key management device 10 (step 464).

[0056] As a result, in the key management device 10, the communication control unit 115 controls the communication unit 13 to receive RFID from the server device 40 (step 164). Next, in the key management device 10, the memory control unit 114 obtains the storage unit number associated with the RFID received in step 164 from the storage information 121 stored in the memory unit 12 (step 165). Next, in the key management device 10, the light emission control unit 118 illuminates the light emission unit 242 of the storage unit 24 corresponding to the storage unit number acquired in step 165 (step 166). At this time, the lock mechanism 241 is released so that the holder 31 can be removed. As a result, the user can identify the storage unit 24 that houses the holder 31 holding the key 33 reserved for that day, and then removes the key 33 from the storage unit 24 to borrow it. Then, the key management device 10, specifically the memory control unit 114, deletes the RFID that was associated with the storage unit number of the storage unit 24 in the storage information 121 (step 167).

[0057] Although not mentioned above, if the key number stored along with the user ID in step 462 does not exist, the server device 40 should notify the key management device 10 of the error. Furthermore, if it is discovered during the above operation that there is a key 33 that has exceeded the reserved period, the key management device 10 may display a message to that effect on the display operation unit 27.

[0058] Next, an example of the operation when a key 33 reserved for the same day is returned in the key management system 1 of this embodiment will be described. This example of operation starts when the user selects the item for returning the key 33 reserved for the same day on the standby menu displayed on the display operation unit 27. This example of operation is a modified version of steps 161, 162, and 167 from the flowchart in Figure 12. In other words, when a user inserts their card into the card reader 28, the key management device 10's user ID acquisition unit 113 acquires the user ID from the card reader 28 and performs user authentication. If user authentication is successful, the user inserts the key 33 into an empty storage compartment 24 to return it. Then, the key management device 10's memory control unit 114 stores the RFID of the holder 31 that holds the returned key 33, associating it with the storage compartment number of the storage compartment 24 in the storage information 121. Although not mentioned above, the key management device 10 may also control the door locking mechanism 14 so that the last user to return the key 33 reserved for that day can open and close the first door 21 even outside the reservation period.

[0059] Next, an example of the operation when retrieving a key 33 that is not reserved for the next day in the key management system 1 of this embodiment will be described. This example of operation starts when the administrator selects an item for retrieving a key 33 that is not reserved for the next day on the administrator menu displayed on the display operation unit 27 and retrieves the key 33 that is not reserved for the next day to the back room. This example of operation is a modified version of the flowchart in Figure 11. In other words, steps 151 through 153 are the same as in Figure 11. In step 154, the difference information determination unit 116 determines whether the difference information received in step 153 indicates that there is a key 33 among the keys 33 loaded in the storage unit 24 that is not reserved for the next day. In step 155, if the discrepancy information indicates that there is a key 33 in the storage unit 24 that is not reserved for the next day, the light emission control unit 118 illuminates the light emission unit 242 of the storage unit 24, which houses the holder 31 that holds the key 33 that is not reserved for the next day. This allows the administrator to retrieve the key 33 that is not reserved for the next day but is loaded in the storage unit 24 to the back room. Suppose that the following day, an additional key 33 that was not reserved is retrieved from the storage unit 24. Then, in step 156, the memory control unit 114 deletes the RFID associated with the storage unit number where the holder 31 holding the retrieved key 33 was stored in the storage information 121. On the other hand, if the difference information does not indicate that there is a key 33 among the keys 33 loaded in the storage unit 24 that is not reserved for the next day, the light emission control unit 118 will not illuminate the light emission unit 242. Also, since no additional keys 33 that are not reserved for the next day will be retrieved from the storage unit 24, the memory control unit 114 will not delete the RFID from the storage information 121.

[0060] Furthermore, while the above describes a check being performed by the administrator to ensure that all keys 33 not reserved for the next day have been removed from the storage unit 24 when the administrator retrieves the keys 33 to the back room, this is not the only option. For example, such a check could be performed at any time, such as when the final review process is executed at the end of the workday. In that case, since the administrator may not be near the key management device 10, in step 155, the communication control unit 115 may send the storage unit number of the storage unit 24 containing the keys 33 not reserved for the next day to, for example, the administrator's terminal device 50.

[0061] [Differentiation] Although not mentioned above, the key exchange in the key exchange unit 26 may be configured to only perform key exchange on holders 31 that are to be stored in the storage unit 24, and not on holders 31 that do not need to be stored in the storage unit 24.

[0062] In the above, it was assumed that at the end of each business day, the key 33 reserved for the following day is stored in the storage unit 24. This means that even if the key 33 is borrowed for several consecutive days, it is necessary to return the key 33 to the key management device 10 at the end of each business day. However, it is also possible to operate in a way that does not require the key 33 borrowed for a long period of time to be returned to the key management device 10 at the end of each business day. In that case, when checking at the end of each business day whether the key 33 reserved for the following day is stored in the storage unit 24, it is best to check excluding the key 33 borrowed for a long period of time. On the other hand, suppose that during the check at the end of the day's work, a key 33 that was on long-term loan and should not be stored in the key management device 10 is found to be stored there. This could be a key 33 that was on long-term loan but returned early. In such a case, it may be possible to notify the user that there is a key 33 that has been returned early. Furthermore, such notification may be made in a manner different from that used to notify other information. Alternatively, the key 33 could be configured to be considered out of use once it is returned. In such a configuration, the user can benefit from being able to keep rental costs low by shortening the usage period, and from being relieved of the responsibility for managing the key 33, which is an important item.

[0063] In the above configuration, only the server device 40 holds the reservation information 422. However, in order to quickly compare the holders 31 stored in the storage unit 24 with the holders 31 reserved for the following day, the key management device 10 may also hold the reservation information 422. In other words, the server device 40 may transmit the reservation information 422 to the key management device 10, the key management device 10 may adopt a configuration in which the communication control unit 115 receives the reservation information 422 using the communication unit 13, and the storage control unit 114 stores the reservation information 422 in the storage unit 12. In this configuration as well, the server device 40 may generate the reservation information 422 by accepting reservation requests for keys 33 on a daily basis, within a limit not exceeding the upper limit received from the key management device 10. In this case, the server device 40 is an example of another device, the upper limit is an example of the first number, the holder 31 reserved for the next day is an example of the first holder to be stored by the storage unit, and the reservation information 422 is an example of storage target information indicating that the holder is the first holder. The memory control unit 114 is an example of a setting unit that sets storage target information indicating that the holder is the first holder for holders up to the first number based on information received from other devices. Furthermore, the day is an example of a predetermined period, and the reservation information 422 is an example of storage target information indicating at least one of the following: that the holder is a first holder to be stored by the storage unit, or that the holder is a second holder not to be stored by the storage unit.The memory control unit 114 is an example of a setting unit that sets storage target information for the managed holders at predetermined intervals based on information received from other devices.

[0064] In the above description, the storage section 24 was described as a type in which the holder 31 is stored by inserting it, but it is not limited to this. The storage section 24 may also be of a type in which the holder 31 is housed inside the housing, as shown in Japanese Patent Application Publication No. 2021-75852. In the above explanation, key 33 was described assuming a physical key, but it is not limited to physical keys; it could also be a card key or a digital key.

[0065] The above describes a key management device 10 for managing keys 33, but the present invention is also applicable to an item management device for managing items such as seals and USB memory sticks. In that case, all instances of "keys" in the documents should be read as "items" and the invention should be understood accordingly. In other words, the present invention can be understood as "an article management device comprising: a plurality of storage units, each capable of housing a holder for holding articles; a registration unit for registering holders to be managed by the device; and a setting unit for setting storage target information for the holders to be managed registered by the registration unit, indicating at least one of the following: that the holder is a first holder to be stored by the storage unit, and that the holder is a second holder not to be stored by the storage unit." Furthermore, the present invention can be understood as "an article management device having a plurality of storage compartments, each capable of storing a holder for holding articles; a storage unit for storing information on holders to be managed by the article management device; and a setting unit for setting storage target information for the information on the managed holders stored in the storage unit, indicating at least one of the following: that the holder is a first holder to be stored by the storage compartments, and that the holder is a second holder not to be stored by the storage compartments." Furthermore, the present invention can be understood as "an article management method comprising: a registration step in which a computer registers holders to be managed by an article management device having a plurality of storage compartments, each capable of housing holders for holding articles; and a setting step in which the computer sets storage target information for the holders to be managed registered in the registration step, indicating at least one of the following: that the holder is a first holder to be stored by the storage compartments, and that the holder is a second holder not to be stored by the storage compartments."

[0066] [Effects of the embodiment] In this embodiment, it is possible to set at least one of the following for a holder managed by the key management device 10: that it should be stored in the key management device 10, or that it should not be stored in the key management device 10. This makes it possible for the key management device 10 to manage more holders than the number of storage compartments in the key management device 10. [Explanation of symbols]

[0067] 1...Key management system, 10...Key management device, 11...Control unit, 111...RFID acquisition unit, 112...Key number acquisition unit, 113...User ID acquisition unit, 114...Storage control unit, 115...Communication control unit, 116...Difference information determination unit, 117...Display control unit, 118...Light emission control unit, 119...Verification processing unit, 12...Storage unit, 121...Storage information, 13...Communication unit, 14...Door locking mechanism, 24...Storage unit, 2 41...Lock mechanism, 242...Light-emitting unit, 243...Reading unit, 25...Printer, 26...Key exchange unit, 263...Reading unit, 27...Display operation unit, 28...Card reader, 40...Server device, 41...Control unit, 411...Storage control unit, 412...Communication control unit, 413...Reservation feasibility determination unit, 414...Difference information generation unit, 42...Storage unit, 421...Key information, 422...Reservation information, 43...Communication unit, 50...Terminal device

Claims

1. Multiple storage compartments, each capable of housing a holder for holding keys, An acquisition unit that acquires the identification information of the holder, The registration unit registers the identification information acquired by the acquisition unit as the identification information of the holder to be managed by the device, thereby registering the holder to be managed. Equipped with, The registration unit is capable of registering a number of holders greater than the number of holders in the storage unit as holders to be managed, in this key management device.

2. The key management device according to claim 1, further comprising a setting unit for setting storage target information indicating that the holder to be managed registered by the registration unit is a first holder to be stored by the storage unit.

3. The key management device according to claim 2, wherein the setting unit can set the storage target information indicating that a holder is the first holder for a first number of holders, which are less than or equal to the number of storage units, among the holders to be managed that have been registered by the registration unit.

4. It is equipped with a communication unit that communicates with other devices, The communication unit transmits the first number to the other device. The key management device according to claim 3, wherein the setting unit sets the storage target information indicating that a holder is the first holder for a first number or less of holders based on the information received by the communication unit from the other device.

5. The key management device according to claim 1, further comprising a setting unit for setting storage target information indicating that the holder to be managed registered by the registration unit is a second holder that is not to be stored by the storage unit.

6. The key management device according to claim 5, wherein the setting unit can set the storage target information indicating that a holder is a second holder for a second number of holders, which is equal to or greater than the number obtained by subtracting the number of storage units from the number of holders to be managed, among the holders to be managed registered by the registration unit.

7. The key management device according to claim 2 or 5, wherein the setting unit sets the storage target information for the holder to be managed, which has been registered by the registration unit, at predetermined intervals.

8. It is equipped with a communication unit that communicates with other devices, The key management device according to claim 7, wherein the setting unit sets the storage target information for the managed holders registered by the registration unit at predetermined intervals based on the information received by the communication unit from the other device.

9. A key management device having multiple storage compartments, each capable of housing a holder for holding keys, An acquisition unit that acquires the identification information of the holder, A storage unit that stores information about holders managed by the key management device, by storing the identification information acquired by the acquisition unit as identification information of holders managed by the key management device, Equipped with, The storage unit is capable of storing information on a number of holders greater than the number of holders in the storage unit as information on the holders to be managed, in a key management system.

10. The computer obtains identification information of the holder that holds the key, A registration step in which a computer registers the identification information acquired in the acquisition step as identification information of a holder to be managed by a key management device having multiple storage compartments, each capable of accommodating the holder, thereby registering the holder to be managed; Includes, A key management method in which, in the registration step, a number of holders greater than the number of storage compartments can be registered as holders to be managed.

Images