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]

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

[0002] Patent document 1 describes a key management device that has a key management unit that manages keys, and that includes a key holder that has identification information and is connected to a key, an acquisition unit that acquires the identification information of the key holder, and a registration unit that registers the key holder that has the identification information acquired by the acquisition unit as a key holder to be managed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-122312 Summary of the Invention [Problem to be solved by the invention]

[0004] There is a demand for more holders to be managed by the key management device than can be accommodated in the storage unit of the key management device. An object of the present invention is to enable a key management device to manage more holders than can be accommodated in a storage unit of the key management device. [Means for solving the problem]

[0005] With this objective in mind, the present invention provides a key management device comprising a plurality of storage units, each capable of storing a holder that holds a key; an acquisition unit that acquires identification information of the holder; and a registration unit that registers the holder to be managed by registering the identification information acquired by the acquisition unit as identification information of the holder to be managed by the device, wherein the registration unit is capable of registering a greater number of holders as holders to be managed than the number of storage units. The key management device may include a setting unit that sets, for a holder to be managed registered by the registration unit, storage target information indicating that the holder is a first holder to be stored by the storage unit. In this case, the setting unit may be capable of setting storage target information indicating that the holder is the first holder for a first number of holders, of the holders to be managed registered by the registration unit, the first number being equal to or less than the number of storage units. In this case, the device may also include a communication unit that communicates with another device, the communication unit transmits the first number to the other device, and the setting unit sets storage target information indicating that the holder is the first holder for the first number of holders or less based on information received by the communication unit from the other device. The key management device may include a setting unit that sets, for a holder to be managed registered by the registration unit, storage target information indicating that the holder is a second holder that is not a storage target of the storage unit. In this case, the setting unit may be capable of setting, among the holders to be managed registered by the registration unit, storage target information indicating that the holder is a second holder, for a second number of holders that is equal to or greater than the number of holders to be managed minus the number of storage units. In these cases, the setting unit may set the storage target information for the holder of the management target 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 the storage target information for the holder of the management target registered by the registration unit at predetermined intervals based on information received by the communication unit from the other devices.

[0006] The present invention also provides a key management system comprising: a key management device having a plurality of storage units each capable of storing a holder that holds a key; an acquisition unit that acquires identification information of the holder; and a memory unit that stores information of the holders that are to be managed by the key management device by storing the identification information acquired by the acquisition unit as identification information of the holders that are to be managed by the key management device, wherein the memory unit is capable of storing information of a greater number of holders than the number of storage units as information of the holders that are to be managed.

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

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

[0009] [Figure 1] 1 shows an example of the overall configuration of a key management system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating an example of the external configuration of a key management device according to an embodiment of the present invention. [Figure 3] 1A and 1B are diagrams illustrating examples of the external configuration of a holder and a key used in an embodiment of the present invention. [Figure 4] 2 is a block diagram illustrating an example of a functional configuration of a key management device according to an embodiment of the present invention. FIG. [Figure 5] FIG. 10 is a diagram showing an example of storage information according to an embodiment of the present invention. [Figure 6] FIG. 2 is a block diagram illustrating an example of a functional configuration of a server device according to an embodiment of the present invention. [Figure 7] FIG. 3 is a diagram showing an example of key information according to an embodiment of the present invention. [Figure 8] FIG. 3 is a diagram showing an example of reservation information according to the embodiment of the present invention. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of an operation when registering a key in the key management system according to the embodiment of the present invention. [Figure 10]10 is a flowchart illustrating an example of an operation performed when reserving a key for a server device in the key management system according to the embodiment of the present invention. [Figure 11] FIG. 10 is a sequence diagram showing an example of the operation when a key reserved for the next day is loaded in the key management system according to the embodiment of the present invention. [Figure 12] FIG. 10 is a sequence diagram showing an example of the operation when a key reserved for the same day is lent in the key management system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. [Overall configuration of key management system] 1 is a diagram showing an example of the overall configuration of a key management system 1 according to this embodiment. As shown in the figure, the key management system 1 includes 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 holders for holding keys. This key management device 10 is operated by an administrator or a user. The administrator is a user who manages 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 a user who borrows and uses keys, and performs operations such as borrowing a key reserved for the day from the key management device 10 and returning a key to the key management device 10 after use. The server device 40 is a device that manages keys and holders. The server device 40 also accepts reservations for keys and manages the reservation status. The terminal device 50 is a terminal device used by a user, and examples thereof include a PC (Personal Computer), a tablet terminal, a smartphone, etc. The user may be a key manager or a key user. The network 80 is a communication means used for information communication between the key management device 10, the server device 40, and the terminal device 50, and is, for example, the Internet, a public line, a LAN (Local Area Network), or the like.

[0012] [External configuration of key management device] Fig. 2 is a diagram showing an example of the external configuration of key management device 10 according to the present embodiment. As shown in Fig. 2, key management device 10 has a first door 21 and a second door 22, each of which can be opened and closed, provided on the front of the device, and is also provided with a key storage cabinet 23 that can be opened and closed by first door 21, and a printer 25 and a key exchange unit 26 that can be opened and closed by second door 22. Key management device 10 also has a display operation unit 27 and a card reader 28 on the front of the device.

[0013] The key storage 23 is provided with a plurality of storage sections 24. Each storage section 24 detachably stores a holder 31 for holding a key. Each storage unit 24 is provided with a locking mechanism 241 that allows or prohibits removal of the holder 31. The key management device 10 controls the locking mechanism 241 for each storage unit 24, thereby controlling whether or not removal of each holder 31 is permitted. Each storage section 24 is provided with a light emitting section 242 for informing the user of a lendable holder 31 or a holder to be collected 31. The light emitting section 242 is, for example, an LED (Light Emitting Diode). Furthermore, each storage section 24 is provided with a reading section 243 that reads information from a wireless tag 34 (described later) of the holder 31. The reading section 243 is provided adjacent to the storage section 24 or inside the storage section 24. The reading section 243 is, for example, an RFID (Radio Frequency IDentifier) ​​reader. Note that to prevent the reading section 243 of a certain storage section 24 from erroneously acquiring radio waves from the wireless tag 34 of a holder 31 inserted into an adjacent storage section 24, a shielding plate or the like that blocks radio waves may be provided between adjacent storage sections 24.

[0014] The printer 25 prints the history of the key management device 10, including key replacement, insertion, removal, etc., on 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 an authorized person authorized to exchange keys, such as an administrator. 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 engagement between the holder 31 body and the ring locking body when the holder 31 is inserted up to a predetermined unlocking position in the insertion opening 261, thereby allowing the ring 32 (described below) to be removed, and a key exchange restriction unit that allows the administrator to unlock the holder 31 but prohibits anyone other than the administrator from unlocking the holder 31. The key exchange restriction unit may, for example, be a stopper mechanism that uses an electrical drive unit such as a solenoid to move a stopper forward and backward into the insertion opening 261. In this case, the key exchange restriction unit normally advances the stopper into the insertion opening 261 to restrict the holder 31 from being inserted up to the predetermined unlocking position of the insertion opening 261. On the other hand, the key exchange restriction unit retracts the stopper from the insertion slot 261 only when operated by the administrator, allowing the holder 31 to be inserted into the insertion slot 261 up to a predetermined unlocked position. Furthermore, key exchange unit 26 is provided with a reading unit 263 that reads information from wireless tag 34 of holder 31. Reading unit 263 is provided in the vicinity of key exchange unit 26 or within key exchange unit 26. Reading unit 263 is, for example, an RFID reader.

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

[0016] [Holder and key configuration] 3 is a diagram showing an example of the external configuration of the holder 31 and the key 33 used in this embodiment. As shown in FIG. A wireless tag 34 is provided on the holder 31. The wireless tag 34 is, for example, an RFID tag. The wireless tag 34 has identification information for identifying the holder 31. To provide the wireless tag 34 on the holder 31, for example, a sticker-type wireless tag 34 may be attached to the holder 31, or the wireless tag 34 may be embedded in the holder 31. A sticker 35 is attached to the key 33. A key number, which is a number for identifying the key 33, is written on the sticker 35 by, for example, an administrator.

[0017] [Background of the embodiment] Some businesses that install such key management devices 10 desire to manage more keys 33 than the number of storage units 24 of the key management device 10. In such cases, it is common to increase the number of keys 33 that can be managed by installing multiple key management devices 10, but this has cost disadvantages. In addition, there is also the disadvantage of space required to install multiple key management devices 10. Furthermore, such businesses may have a large total number of keys to manage, but do not use all of the keys every day, and may use different keys depending on the day, so they may simply need to change the keys stored in the key management device 10 depending on the day. Therefore, in this embodiment, it is possible to set at least one of the following for a holder to be managed by the key management device 10: a holder that should be stored in the key management device 10, and a holder that 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 units in the key management device 10.

[0018] [Functional configuration of the key management device] 4 is a block diagram showing an example of the functional configuration of key management device 10 according to the present embodiment. As shown in the figure, key management device 10 includes control unit 11, storage unit 12, communication unit 13, door locking mechanism 14, locking mechanism 241, light emitting unit 242, reading unit 243, printer 25, reading unit 263, display operation unit 27, and 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, locking mechanism 241, light-emitting unit 242, reading unit 243, printer 25, reading unit 263, display operation unit 27, card reader 28, etc.) in accordance with the operating program stored in the memory unit 12. The storage unit 12 includes a ROM (Read Only Memory), a RAM (Random Access Memory), etc., and stores the operation program of the control unit 11 and 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 processing described below. The communication unit 13 communicates information with the server device 40 via a communication line. The door locking mechanism 14 is a mechanism that locks 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 lock mechanism 241, the light emitting unit 242, the reading unit 243, the printer 25, the reading unit 263, the display operation unit 27, and the card reader 28 have already been described using FIG. 2, and therefore will not be described here.

[0019] Here, we will specifically explain the configuration of the control unit 11. The control unit 11 includes an RFID acquisition unit 111, a key number acquisition unit 112, a user ID acquisition unit 113, a memory 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 reconciliation processing unit 119. When the reading unit 243 or the reading unit 263 acquires an RFID from the wireless tag 34 of the holder 31, the RFID acquisition unit 111 acquires this RFID from the reading unit 243 or the reading unit 263. In this case, information other than RFID may be used as long as it is information that identifies the holder 31, but the following description will be given assuming that RFID is used. In this embodiment, the RFID acquisition unit 111 is provided as an example of an acquisition unit that acquires identification information of the holder. When the display operation unit 27 accepts an operation to input a key number, the key number acquisition unit 112 acquires this key number from the display operation unit 27 .

[0020] When the card reader 28 reads the user ID from the user's card, the user ID acquisition unit 113 acquires this user ID from the card reader 28. The user ID acquisition unit 113 may also perform user authentication using this user ID. Alternatively, the following means for user authentication may be provided. First, user authentication is performed by reading a QR code (registered trademark) with a reader. In this case, the QR code may be assigned to the user in an open-ended manner or in a one-time format with a limited period of time. Second, user authentication is performed by biometric user authentication such as finger vein or face authentication, or by personal identification using a driver's license or the like, to prevent impersonation during user authentication when receiving the key 33. The storage control unit 114 controls writing of data to the storage unit 12 and reading of data from the storage unit 12 . Specifically, the memory control unit 114 stores in the memory unit 12 storage information indicating which holder 31 is loaded in which storage unit 24, and reads out 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 to the server device 40 the key number that the key number acquisition unit 112 acquires from the display operation unit 27 and the RFID that the RFID acquisition unit 111 acquires from the reading unit 263. Here, the RFID acquired from the reading unit 263 is the RFID of the holder 31 for which the key has been exchanged by the key exchange unit 26, and is transmitted to the server device 40 as identification information of the holder 31 that holds the key 33 managed by the key management device 10. In this embodiment, the number of pairs of key numbers and RFIDs 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 key management device 10. 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 identification information of the holder to be managed. Furthermore, in this embodiment, this function is provided in communication control section 115 as an example of a registration section that can register a greater number of holders than the number of storage sections as holders to be managed.

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

[0023] Furthermore, at any timing, such as when loading a key 33 reserved for the next day, when collecting a key 33 not reserved for the next day, or when performing an inspection process at the end of business hours for a certain day, the communication control unit 115 transmits to the server device 40 the RFID acquired by the RFID acquisition unit 111 from the reading unit 243 of the storage unit 24 in which the holder 31 is stored. The communication control unit 115 also receives from the server device 40 information on the difference between the RFID transmitted to the server device 40 and the RFID of the holder 31 holding the key 33 that is managed by the server device 40 as being reserved for the next day. Note that, although the following description will be given assuming that the key 33 is reserved on a daily basis, the period may be hours, weeks, or months as long as the key 33 is reserved on a periodic basis. If the communication control unit 115 determines at any time, such as when performing a reconciliation process at the end of business hours on a certain day, that the difference information indicates that there is a key 33 that is not loaded in the storage unit 24 among the keys 33 reserved for the next day, the communication control unit 115 may transmit information to, for example, the terminal device 50, indicating that the key 33 that is not loaded in the storage unit 24 should be additionally loaded. In this embodiment, one day is used as an example of a predetermined period, the reconciliation process is used as an example of a predetermined process executed every 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. This function of the communication control unit 115 is provided as an example of an alarm unit that alarms, during the predetermined process executed every predetermined period, difference information indicating a 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, if the communication control unit 115 determines at any time, such as when the reconciliation process is performed at the end of business hours on a certain day, that the difference information indicates that there are keys 33 stored in the storage unit 24 that are not reserved for the next day, the communication control unit 115 may transmit information to, for example, the terminal device 50, indicating that the additional keys 33 that are not reserved for the next day should be collected. In this embodiment, one day is used as an example of a predetermined period, the reconciliation process is used as an example of a predetermined process performed every 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. This function of the communication control unit 115 is provided as an example of an alarm unit that alarms, during the predetermined process performed every predetermined period, difference information indicating a 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.

[0024] Furthermore, when lending out a key 33 reserved for the same 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 acquired from the card reader 28, to the server device 40. Then, the communication control unit 115 receives from the server device 40 the RFID of the holder 31 holding the key 33 that is managed by the server device 40 as having been reserved for that user on the same 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 a predetermined condition. Specifically, when loading 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 among the keys 33 reserved for the next day, there are keys 33 that have not been loaded in the storage unit 24. When collecting keys 33 that are not 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 are keys 33 that are not reserved for the next day among the keys 33 loaded in the storage unit 24. In the following, the difference information determination unit 116 will be described as performing the loading operation when a key 33 reserved for the next day is loaded, and performing the recovery operation when a key 33 not reserved for the next day is recovered, but it may also be configured to perform both operations at a predetermined timing.

[0026] The display control unit 117 controls the display of information on the display operation unit 27 . Specifically, the display control unit 117 controls the display of information on the display operation unit 27 when a key 33 reserved for the next day is loaded at a predetermined time on a certain day. If the display control unit 117 determines that the difference information indicates that there is a key 33 that is not loaded in the storage unit 24 among the keys 33 reserved for the next day, the display control unit 117 controls the display operation unit 27 to display the key numbers of the keys 33 that are not loaded in the storage unit 24. In this embodiment, 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. This function of the display control unit 117 serves as an example of a notification unit that notifies, at a predetermined time within the first predetermined period, of difference information indicating a 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 following the first predetermined period. In addition, in this embodiment, this function of the display control unit 117 is provided as an example of an alarm unit that notifies difference information, which is information that any of the holders that should be stored in the storage unit during the second specified period are not present among the holders that are stored in the storage unit during the first specified period.

[0027] Furthermore, the display control unit 117 may control the display of information on the display operation unit 27 at any timing, such as when a reconciliation process is performed at the end of business hours for a certain day. In this case, if the display control unit 117 determines that the difference information indicates that there is a key 33 that is not loaded in the storage unit 24 among the keys 33 reserved for the next day, the display control unit 117 controls the display operation unit 27 to display the key numbers of the keys 33 that are not loaded in the storage unit 24. In this embodiment, one day is used as an example of a predetermined period, the reconciliation process is used as an example of a predetermined process executed every 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. This function of the display control unit 117 is provided as an example of an informing unit that notifies the user of difference information indicating a 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 every predetermined period.

[0028] The light emission control unit 118 controls the light emission of the light emitting unit 242 of the storage unit 24 . Specifically, the light-emission control unit 118 controls the light-emission unit 242 of the storage unit 24 to emit light when collecting a key 33 that is not reserved for the next day at a predetermined time on a certain day. If the light-emission control unit 118 determines that the difference information indicates that there is a key 33 that is not reserved for the next day among the keys 33 loaded in the storage unit 24, the light-emission control unit 118 controls the light-emission unit 242 of the storage unit 24 that stores the holder 31 holding the key 33 that is not reserved for the next day to emit light. In this embodiment, 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. This function of the light-emission control unit 118 serves as an example of an alarm unit that, at a predetermined time within the first predetermined period, notifies the user of difference information indicating a 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 following the first predetermined period. In addition, in this embodiment, this function of the light emission control unit 118 is provided as an example of an alarm unit that notifies difference information, which is information that any of the holders stored in the storage unit during the first specified period is not among the holders that should be stored in the storage unit during the second specified period.

[0029] Furthermore, the light-emission control unit 118 may control the light emission of the light-emitting unit 242 of the storage unit 24 at any timing, such as when a reconciliation process is performed at the end of business hours on a certain day. In this case, if the light-emission control unit 118 determines that the difference information indicates that there is a key 33 that is not reserved for the next day among the keys 33 loaded in the storage unit 24, the light-emission control unit 118 controls the light-emission unit 242 of the storage unit 24 that stores the holder 31 holding the key 33 that is not reserved for the next day to emit light. In this embodiment, one day is used as an example of a predetermined period, the reconciliation process is used as an example of a predetermined process executed every 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. This function of the light-emission control unit 118 is provided as an example of an alarm unit that alarms, during the predetermined process executed every predetermined period, difference information indicating a 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.

[0030] The reconciliation processing unit 119 performs a reconciliation process at the end of each business day. The reconciliation process includes, for example, checking the usage history of the key management device 10 for the day. In this reconciliation process, the reconciliation processing unit 119 updates information about holders 31 that should or should not be loaded into the storage unit 24 on a certain day to information about 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, the reconciliation process is used as an example of a predetermined process executed every predetermined period, a certain day is used as an example of a first predetermined period, and the following day is used as an example of a second predetermined period. Information about holders 31 that should or should not be loaded into the storage unit 24 is used as an example of storage target information. This function of the reconciliation processing unit 119 is provided as an example of an update unit that updates storage target information set for a first predetermined period to storage target information set for a second predetermined period following the first predetermined period during the predetermined process executed every predetermined period.

[0031] In addition, the reconciliation processing unit 119 instructs the communication control unit 115 to obtain difference information between the storage unit 24 in which the holder 31 is loaded that day and the storage unit 24 in which the holder 31 should be loaded the next day, and instructs the difference information determination unit 116 to determine the difference information. If the difference information determination unit 116 determines that the difference information indicates that there is a key 33 that is not loaded in the storage unit 24 among the keys 33 reserved for the next day, the reconciliation processing unit 119 instructs the communication control unit 115 to transmit the information to, for example, the terminal device 50. Here, the terminal device 50 may be used by a manager at headquarters or by a manager at the site where the key management device 10 is installed. The transmitted information indicates that an additional key 33 needs to be loaded and may include the key number of the key 33 to be loaded. If the information does not include the key number, the manager can simply confirm the key number on the display / operation unit 27 of the key management device 10. In this embodiment, the reconciliation processing unit 119 is provided as an example of an update unit that performs processing to store, in a predetermined process, holders that are not included in the holders stored in the storage unit during the first predetermined period, among the holders that should be stored in the storage unit during the second predetermined period. On the other hand, if the difference information determination unit 116 determines that the difference information indicates that there is a key 33 that is not reserved for the next day among the keys 33 loaded in the storage unit 24, the reconciliation processing unit 119 instructs the communication control unit 115 to transmit information to, for example, the terminal device 50. Here, the terminal device 50 may be used by a manager at headquarters or by a manager at the site where the key management device 10 is installed. The transmitted information indicates that an additional key 33 needs to be collected and may include the storage unit number of the storage unit 24 in which the key 33 to be collected is stored. If the information does not include the storage unit number, the manager can simply confirm the storage unit number using the light-emitting unit 242 of the storage unit 24. In this embodiment, this function of the reconciliation processing unit 119 is provided as an example of an update unit that performs processing to collect, within a predetermined process, 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.

[0032] Next, a specific description will be given of the information stored in the storage unit 12. The storage unit 12 stores storage information 121. The storage information 121 is information for managing the RFIDs of the holders 31 stored in each storage section 24 of the key storage 23. The specific contents of the storage information 121 will be described later.

[0033] [Specific details of storage information] 5 is a diagram showing an example of the storage information 121. As shown in the figure, the storage information 121 associates a storage unit number with an RFID. The storage unit number is a number that identifies the storage unit 24. Here, the number of storage units 24 is 10, and the storage unit numbers 1 to 10 are stored. The RFID is the RFID read from the holder 31 stored in the corresponding storage unit 24. In the figure, for example, it is shown that the holder 31 with RFID "01234927" is stored in the storage unit 24 with storage unit number "1." Note that, taking as an example a case where the holder 31 is not stored in the storage unit 24 with storage unit number "2," the RFID column for storage unit number "2" is left blank.

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

[0035] Here, a specific description will be given of the configuration of the control unit 41. The control unit 41 includes a memory control unit 411, a communication control unit 412, a reservation availability determination unit 413, and a difference information generation unit 414. The storage control unit 411 controls writing of data to the storage unit 42 and reading of data from the storage unit 42 . Specifically, the storage control unit 411 stores key information for managing the key 33 in the storage unit 42, and reads out the key information from the storage unit 42.

[0036] Furthermore, the storage control unit 411 stores reservation information of the holder 31 that holds the key 33 in the storage unit 42, and reads out the reservation information from the storage unit 42. Here, the reservation information may be information that sets the reserved key 33 for a day. As will be described later, in the key information, the key 33 is linked to the holder 31 that holds the key 33. Therefore, the reservation information can be said to be information that sets the holder 31 that holds the reserved key 33 for a day. In this case, in the present embodiment, the holder 31 that holds the reserved key 33 is used as an example of a first holder to be stored by the storage unit, and the reservation information is used as an example of storage target information indicating that the holder is the first holder. The memory control unit 411 is provided as an example of a setting unit that sets storage target information for the holder to be managed. Furthermore, in the present 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 holder to be managed for each predetermined period. In this case, the number of holders 31 holding reserved keys 33 may be equal to or less than the upper limit number received from the key management device 10. In this case, in this embodiment, the upper limit number is used as an example of a first number that is equal to or less than the number of storage units, and the reservation information is used as an example of storage target information that indicates that the holder is the first holder. Then, a memory control unit 411 is provided as an example of a setting unit that can set storage target information for the first number of holders among the holders to be managed.

[0037] The reservation information may also be information in which an unreserved key 33 is set for a day. As will be described later, in the key information, a key 33 is linked to a holder 31 that holds that key 33. Therefore, the reservation information can be said to be information in which a holder 31 that holds an unreserved key 33 is set for a day. In this case, in this embodiment, the holder 31 that holds the unreserved key 33 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 indicating that the holder is a second holder. The memory control unit 411 is provided as an example of a setting unit that sets storage target information for a holder to be managed. In this embodiment, a 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 a holder to be managed for each predetermined period. In this case, the number of holders 31 holding unreserved keys 33 may be equal to or greater than the number of holders 31 to be managed minus the upper limit number received from the key management device 10. In this case, in the present embodiment, the number obtained by subtracting the upper limit number received from the key management device 10 from the number of holders 31 to be managed is used as an example of the second number that is equal to or greater than the number of holders to be managed minus the number of storage units, and reservation information is used as an example of storage target information indicating that a holder is the second holder. Then, 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 to be managed.

[0038] Furthermore, the reservation information may be information that sets reserved keys 33 and unreserved keys 33 for each day. As will be described later, in the key information, the holder 31 that holds the key 33 is linked to the key 33. Therefore, the reservation information can be said to be information that sets the holder 31 that holds the reserved key 33 and the 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 that the holder is a first holder and that the holder is a second holder. The storage control unit 411 is provided as an example of a setting unit that sets the storage target information. In this embodiment, the storage control unit 411 is provided as an example of a setting unit that sets the storage target information for the folder to be managed for each predetermined period.

[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, communication control unit 412 receives from key management device 10 the key number input to display operation unit 27 and the RFID read by reading unit 263 of key exchange unit 26. Furthermore, when reserving a key, the communication control unit 412 receives in advance from the key management device 10 the upper limit number of storage units 24 that can store holders 31 for lending keys 33 from the key management device 10. Furthermore, when loading a key 33 reserved for the next day or collecting a key 33 not reserved for the next day, the communication control unit 412 receives from the key management device 10 the RFID read by the reading unit 243 of the storage unit 24 in which the holder 31 is stored.The communication control unit 412 then transmits to the key management device 10 information indicating the difference between the RFID received from the key management device 10 and the RFID of the holder 31 holding the key 33 that is managed by the server device 40 as being reserved for the next day. Furthermore, when lending out a key 33 reserved for the same day, the communication control unit 412 receives the user ID of the user who wishes to borrow the key 33, read by the card reader 28, from the key management device 10. Then, the communication control unit 412 transmits to the key management device 10 the RFID of the holder 31 holding the key 33, which is managed by the server device 40 as having been reserved by that user for the same day.

[0040] The reservation availability determination unit 413 determines whether a reservation is possible in response to a reservation request from a user for a specified period of time for a specified key 33. Specifically, the reservation availability determination unit 413 determines whether the number of already reserved keys 33 is less than the upper limit number received from the key management device 10 for each day within the specified period. The difference information generating 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 holding the key 33 reserved for the next day.

[0041] Next, a specific description will be given of the information stored in the storage unit 42. The storage unit 42 stores key information 421 and reservation information 422. The key information 421 is information that links the key number of the key 33 with the RFID of the wireless tag 34 attached to the holder 31 that holds the key 33. The specific contents of the key information 421 will be described later. In this embodiment, the key information 421 is used as an example of information on a holder that is to be managed by the key management device. The reservation information 422 is information indicating the reservation status of the user for the key 33. The specific contents of the reservation information 422 will also be described later.

[0042] 7 is a diagram showing an example of the key information 421. As shown in the figure, the key information 421 associates a key number, a key name, and an RFID. The key number is a number that identifies the key 33. Here, the number of keys 33 to be managed is 30, which is more than the number of storage units 24 (10), and key numbers 1 to 30 are stored. The key name is a name given to the key 33 to make it easier for humans to identify it. Here, the key name stores identification information for the object to be locked and unlocked with the key 33. The object to be locked and unlocked is, for example, a car, a room, etc. The RFID is an RFID carried by a wireless tag 34 attached to the holder 31 that holds the key 33. In the figure, for example, the key name of the key 33 with key number "1" is "Object 1" and the RFID of the holder 31 that holds the key 33 is "12345426".

[0043] 8 is a diagram showing an example of the reservation information 422. As shown in the diagram, the reservation information 422 associates a date, a user ID, and a key number. The date is the date for reserving the key 33. The user ID is identification information that identifies the user who reserved the key 33 on the corresponding date. The key number is the number of the key 33 reserved by the corresponding user on the corresponding date. The figure shows, for example, that a user with user ID "A" has reserved key 33 with key number "1" on "October 1, 2021" and "October 3, 2021." It also shows that a user with user ID "B" has reserved key 33 with key number "3" from "October 1, 2021" to "October 3, 2021."

[0044] [Key management system operation] 9 is a sequence diagram showing an example of the operation when registering a key in the key management system 1 of this embodiment. It is assumed that, prior to this example of operation, the administrator associates a key number with a key name and registers them in the key information 421. This example of operation then starts when the administrator selects an item for key registration on the administrator menu displayed on the display operation unit 27. First, the administrator performs key exchange in the key exchange unit 26. That is, the administrator performs an operation to newly link 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 operates the administrator menu displayed on the display operation unit 27 to input the key number of the key 33 linked to the holder 31 by the key exchange unit 26. Note that the administrator may have previously affixed a sticker bearing the key number to the key 33, and may input the key number written on the sticker. Then, in the key management device 10, the display operation unit 27 accepts the operation to input the key number, and the key number acquisition unit 112 acquires the key number from the display operation unit 27 (step 132). Thereafter, 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 server device 40, communication control unit 412 controls communication unit 43 to receive the key number and RFID from key management device 10 (step 431). Thereafter, in server device 40, storage control unit 411 associates the RFID with the key number received in step 431 and stores the associated RFID in key information 421 (step 432). At this time, server device 40 determines an error if the key number is not registered in key information 421 or if another RFID is already associated with the key number in key information 421.

[0046] 10 is a flowchart showing an example of the operation of the server device 40 when reserving a key in the key management system 1 of this embodiment. Note that, prior to this example of operation, it is assumed that the key management device 10 has transmitted to the server device 40 the upper limit number of storage units 24 that can store holders 31 for lending keys 33. First, a user who wishes to reserve a key 33 operates, for example, terminal device 50 to send a reservation request to server device 40, including the user's user ID, the key number of the key 33 to be reserved, and the period for which the key 33 is to be reserved. Note that the reservation request may specify the key 33 to be reserved by key name instead of key number, but in this operation example, the key 33 to be reserved is specified by key number. In response to this, in server device 40, communication control unit 412 controls communication unit 43 to receive the reservation request including the user ID, key number, and period (step 441).

[0047] Next, in server device 40, reservation availability determination unit 413 focuses on the days within the period included in the reservation request received in step 441 (step 442). Then, the reservation possibility determination unit 413 determines whether the number of pairs of user ID and key number already stored for the day focused on in step 442 in the reservation information 422 stored in the memory unit 42 is less than the upper limit number received from the key management device 10 (step 443). As a result, if it is determined that the number of pairs of user IDs and key numbers already stored is less than the upper limit, the reservation availability determination unit 413 stores the fact that reservations are possible on the day selected in step 442 (step 444). On the other hand, if it is determined that the number of pairs of user IDs and key numbers already stored is not less than the upper limit, i.e., the upper limit has been reached, the reservation possibility determination unit 413 stores the fact that reservations are not possible on the day selected in step 442 (step 445). Thereafter, the reservation acceptance / rejection determination unit 413 determines whether there are still any days within the period included in the reservation request received in step 441 (step 446). As a result, if it is determined that there are still days within the period included in the reservation request, the reservation availability 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 availability determination unit 413 determines whether there is even one day for which reservation is not possible (step 447).

[0048] If it is determined that there is not even one day for which reservation is not possible, the storage control unit 411 stores the user ID and key number included in the reservation request received in step 441 for all days within the period included in the reservation request in the reservation information 422 stored in the storage unit 42 (step 448). On the other hand, if it is determined that there is at least one day for which reservation is unavailable, the communication control unit 412 controls the communication unit 43 to notify, for example, the terminal device 50, of an error indicating that the key 33 cannot be reserved (step 449). In this case, the user must check the period during which the key 33 can be reserved and send the reservation request again.

[0049] 11 is a sequence diagram showing an example of the operation of the key management system 1 of this embodiment when loading a key 33 reserved for the next day. Prior to this example of operation, the administrator selects an option 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 backyard, 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 an alarm may be sounded when this deadline has passed to prompt the administrator to load the key 33. When the key 33 is loaded into the storage unit 24, the key management device 10 associates the RFID tag of the holder 31 holding the key 33 with the storage unit number of the storage unit 24 in the storage information 121, and then starts this example of operation.

[0050] First, in the key management device 10, the reading units 243 of all storage units 24 in which holders 31 are loaded read the RFIDs from the holders 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 server device 40, memory control unit 411 acquires the set of key numbers stored for the next day from reservation information 422 stored in memory unit 42 (step 452). Then, memory control unit 411 acquires the sets of RFIDs linked to these sets of key numbers from key information 421 stored in memory unit 42 (step 453). Next, in the server device 40, the difference information generating unit 414 generates difference information between the RFID set received in step 451 and the RFID set acquired in step 452 (step 454). Thereafter, in server device 40, communication control unit 412 controls communication unit 43 to transmit the difference information generated in step 453 to 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 the 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 are keys 33 reserved for the next day that have not been loaded into the storage unit 24 (step 154). As a result, if it is determined that the difference information indicates that there are keys 33 that are not loaded in the storage unit 24 among the keys 33 reserved for the next day, the display control unit 117 displays the key numbers of the keys 33 that are not loaded in the storage unit 24 on the display operation unit 27 (step 155). This allows the manager to retrieve the keys 33 that are reserved for the next day but are not loaded in the storage unit 24 from the back yard and load them into the storage unit 24. Then, suppose that an additional key 33 reserved for the next day is loaded into the storage unit 24. In the key management device 10, the storage control unit 114 associates the RFID of the holder 31 holding the loaded key 33 with the storage unit number in the storage information 121 and stores the associated information (step 156). On the other hand, if it is determined that the difference information does not indicate that there is a key 33 that is not loaded in the storage unit 24 among the keys 33 reserved for the next day, the display control unit 117 does not display the key number on the display operation unit 27. In addition, since there will be no additional keys 33 reserved for the next day loaded in the storage unit 24, the storage control unit 114 does not store the RFID in the storage information 121.

[0053] In the above description, when the administrator retrieves keys 33 from the backroom and loads them into the storage unit 24, a check is made to see if all keys 33 reserved for the next day are loaded into the storage unit 24. However, this is not limited to this. For example, such processing may be performed at any time, such as when a detailed inspection process is performed at the end of the day's business. In this case, since it is possible that the administrator is not near the key management device 10, in step 155, the communication control unit 115 may transmit the key numbers of keys 33 that are not loaded into the storage unit 24 to, for example, the administrator's terminal device 50.

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

[0055] As a result, in server device 40, communication control unit 412 controls communication unit 43 to receive the user ID from key management device 10 (step 461). Next, in server device 40, memory control unit 411 acquires the key number stored together with the user ID received in step 461 for today from reservation information 422 stored in memory unit 42 (step 462). Then, memory control unit 411 acquires the RFID linked to the key number acquired in step 462 from key information 421 stored in memory unit 42 (step 463). Thereafter, 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 the RFID from the server device 40 (step 164). Next, in the key management device 10, the storage control unit 114 acquires the storage unit number linked to the RFID received in step 164 from the storage information 121 stored in the storage unit 12 (step 165). Next, in the key management device 10, the light emission control unit 118 causes the light emission unit 242 of the storage unit 24 having the storage unit number acquired in step 165 to emit light (step 166). At this time, the locking mechanism 241 is released so that the holder 31 can be removed. This allows the user to know which storage unit 24 contains the holder 31 holding the key 33 reserved for that day, and the user can then remove the key 33 from that storage unit 24 to borrow it. In the key management device 10, the storage control unit 114 then deletes the RFID tag linked to the storage unit number of that storage unit 24 from the storage information 121 (step 167).

[0057] Although not mentioned above, if there is no key number stored together with the user ID in step 462, the server device 40 may notify the key management device 10 of an error. Furthermore, if it is found in the above operation that there is a key 33 whose reserved period has expired, the key management device 10 may display a message to that effect on the display operation unit 27.

[0058] Next, we will explain an example of the operation of the key management system 1 of this embodiment when returning a key 33 that has been reserved for that day. This operation example begins when the user selects an option for returning the key 33 that has been reserved for that day on the standby menu displayed on the display operation unit 27. This operation example is obtained by extracting and partially modifying steps 161, 162, and 167 from the flowchart of FIG. That is, when a user swipes a card through card reader 28, user ID acquisition unit 113 in key management device 10 acquires the user ID from card reader 28 and performs user authentication. If user authentication is successful, the user inserts key 33 into an empty storage unit 24 to return it. Then, in key management device 10, storage control unit 114 stores in storage information 121 the storage unit number of that storage unit 24, linking it to the RFID of holder 31 holding the returned key 33. Although not mentioned above, the key management device 10 may be configured to control the door locking mechanism 14 so that the last user to return the key 33 reserved on the day can open and close the first door 21 even outside the reservation period.

[0059] Next, we will explain an example of the operation of the key management system 1 of this embodiment when collecting keys 33 that are not reserved for the next day. This example of operation begins when the administrator selects an item for collecting keys 33 that are not reserved for the next day on the administrator menu displayed on the display operation unit 27, and collects the keys 33 that are not reserved for the next day in the backyard. This operation example is a partial modification of the operation in the flowchart of FIG. That is, steps 151 to 153 are the same as those in FIG. In step 154, the difference information determination unit 116 determines whether the difference information received in step 153 indicates that there are keys 33 loaded in the storage unit 24 that are not reserved for the next day. In step 155, if it is determined that the difference information indicates that there is a key 33 that is not reserved for the next day among the keys 33 loaded in the storage unit 24, the light emission control unit 118 causes the light emission unit 242 of the storage unit 24 that stores the holder 31 holding the key 33 that is not reserved for the next day to emit light. This allows the manager to collect the keys 33 that are loaded in the storage unit 24 but are not reserved for the next day to the back yard. Suppose that an additional key 33 that is not reserved for the next day is subsequently collected from the storage unit 24. In this case, in step 156, the memory control unit 114 deletes the RFID tag linked to the storage unit number in which the holder 31 holding the collected key 33 was stored in the storage information 121. On the other hand, if it is determined that the difference information does not indicate that there are any keys 33 that are not reserved for the next day among the keys 33 loaded in the storage unit 24, the light emission control unit 118 does not emit light from the light emission unit 242. Furthermore, since no additional keys 33 that are not reserved for the next day will be collected from the storage unit 24, the memory control unit 114 does not delete the RFID from the storage information 121.

[0060] In the above description, when the administrator retrieves the keys 33 in the backyard, the administrator checks whether all keys 33 not reserved for the next day have been removed from the storage units 24. However, this is not limited to this. For example, such processing may be performed at any time, such as when a detailed inspection process is performed at the end of the day's business. In this case, since it is possible that the administrator is not near the key management device 10, in step 155, the communication control unit 115 may transmit the storage unit number of the storage unit 24 in which keys 33 not reserved for the next day are stored to, for example, the administrator's terminal device 50.

[0061] [Variations] Although not mentioned above, the key exchange in the key exchange unit 26 may be configured so that it can be performed only for holders 31 that are to be stored in the storage unit 24, and not for holders 31 that do not need to be stored in the storage unit 24.

[0062] In the above description, it is assumed that the key 33 reserved for the next day is stored in the storage unit 24 at the end of the day's business. This means that even if the key 33 is loaned for several consecutive days, the key 33 must be returned to the key management device 10 at the end of each day's business. However, the key 33 loaned for a long period of time may not need to be returned to the key management device 10 at the end of each day's business. In this case, it is preferable to check whether the key 33 reserved for the next day is stored in the storage unit 24 at the end of each day's business, excluding the key 33 loaned for a long period of time. On the other hand, suppose that during a check at the end of the day's work, a key 33 that has been rented for a long period of time is found to be stored in the key management device 10 even though it should not be. This key 33 may have been rented for a long period of time but was returned early. In such a case, a notification may be made that a key 33 has been returned early. Such a notification may be made in a manner different from the manner in which other information is notified. Alternatively, the key 33 may be configured to be considered to have ceased use upon its return. In such a configuration, the user can enjoy the benefits of keeping rental costs low by shortening the usage period and being relieved of the responsibility of managing the key 33, which is an important item.

[0063] In the above description, 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 next day, the key management device 10 may also hold the reservation information 422. That is, an embodiment may be adopted in which the server device 40 transmits the reservation information 422 to the key management device 10, and in the key management device 10, 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. Also in this embodiment, the server device 40 may generate the reservation information 422 by accepting reservation requests for keys 33 for each day from the key management device 10 within a range not exceeding the upper limit number received. In this case, server device 40 is an example of another device, the upper limit number is an example of a first number, folder 31 reserved for the next day is an example of a first folder to be stored by the storage unit, and reservation information 422 is an example of storage target information indicating that the folder is the first folder. Memory control unit 114 is an example of a setting unit that sets storage target information indicating that the folder is the first folder for folders equal to or less than the first number based on information received from another device. Furthermore, a day is an example of a predetermined period, and reservation information 422 is an example of storage target information indicating at least one of whether the holder is a first holder to be stored by the storage unit or whether the holder is a second holder not to be stored by the storage unit. Memory control unit 114 is an example of a setting unit that sets storage target information for a managed holder for each predetermined period based on information received from another device.

[0064] Although the storage unit 24 has been described above as a type in which the holder 31 is inserted and stored, this is not limited thereto. The storage unit 24 may be of a type in which the holder 31 is stored by being housed in a housing, as shown in, for example, Japanese Patent Application Laid-Open No. 2021-75852. In the above description, the key 33 is assumed to be a physical key, but it is not limited to a physical key and may be a card key or a digital key.

[0065] Although the above description has been given of the key management device 10 that manages the key 33, the present invention can also be applied to an item management device that manages items such as seals, USB memory sticks, etc. In that case, the invention can be understood by replacing "keys" in all documents with "items." In other words, the present invention can be understood as "an item management device comprising a plurality of storage units each capable of storing holders for holding items, a registration unit that registers holders to be managed by the device itself, and a setting unit that sets storage target information for the managed holders 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 may be understood as "an item management system comprising: an item management device having a plurality of storage units each capable of storing holders for holding items; a memory unit that stores information about holders to be managed by the item management device; and a setting unit that sets storage target information for the information about the holders to be managed stored in the memory unit to indicate 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 may be understood as "an item management method including: a registration step in which a computer registers holders to be managed by an item management device having a plurality of storage units, each capable of storing holders for holding items; and a setting step in which the computer sets storage target information for the managed holders 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 unit, and that the holder is a second holder not to be stored by the storage unit."

[0066] [Effects of the embodiment] In this embodiment, it is possible to set at least one of the following for a holder to be managed by the key management device 10: a holder that should be stored in the key management device 10, and a holder that 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 units 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...Memory control unit, 115...Communication control unit, 116...Difference information determination unit, 117...Display control unit, 118...Light emission control unit, 119...Scrutiny processing unit, 12...Memory 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 possibility determination unit, 414...difference information generation unit, 42...storage unit, 421...key information, 422...reservation information, 43...communication unit, 50...terminal device

Claims

1. a plurality of storage sections each capable of storing a holder for holding a key; an acquisition unit that acquires identification information of the holder; a registration unit that registers the identification information acquired by the acquisition unit as identification information of a folder that is a management target of the device itself, thereby registering the folder that is a management target; Equipped with The registration unit is capable of registering a greater number of holders as the holders to be managed than the number of storage units.

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

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

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

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

6. The key management device of claim 5, wherein the setting unit is capable of setting the storage target information indicating that a second number of holders among the holders to be managed registered by the registration unit is the second holder, the second number being equal to or greater than the number of holders to be managed minus the number of storage units.

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 is registered by the registration unit, at predetermined intervals.

8. a communication unit for communicating with other devices; The key management device according to claim 7, wherein the setting unit sets the storage target information for the managed holder registered by the registration unit for each predetermined period based on information received by the communication unit from the other device.

9. a key management device having a plurality of storage units each capable of storing a holder for holding a key; an acquisition unit that acquires identification information of the holder; a storage unit that stores the identification information acquired by the acquisition unit as identification information of a holder that is a management target of the key management device, thereby storing information of the holder that is a management target of the key management device; Equipped with A key management system, wherein the storage unit is capable of storing information on a greater number of holders than the number of storage units as information on the holders to be managed.

10. an acquisition step in which a computer acquires identification information of a holder who holds a 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 a plurality of storage units each capable of storing the holder, thereby registering the holder to be managed; Including, In the registration step, a number of holders to be managed that is greater than the number of storage units can be registered.

Images